HP 6125XLG R2306-HP 6125XLG Blade Switch MCE Configuration Guide - Page 32

Configuring RIPng between an IPv6 MCE and a VPN site, Configuring OSPFv3 between an IPv6 MCE and

Page 32 highlights

Step Command ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type 2. Configure an IPv6 static route interface-number [ next-hop-address ] | for an IPv6 VPN instance. nexthop-address [ public ] | vpn-instance d-vpn-instance-name nexthop-address } [ permanent ] [ preference preference-value ] [ tag tag-value ] [ description description-text ] 3. (Optional.) Configure the default precedence for IPv6 static routes. ipv6 route-static default-preference default-preference-value Remarks By default, no IPv6 static route is configured. Perform this configuration on the IPv6 MCE. On the VPN site, configure normal IPv6 static routes. If you do not specify a default preference value, the default preference value is 60. Configuring RIPng between an IPv6 MCE and a VPN site A RIPng process belongs to the public network or a single IPv6 VPN instance. If you create a RIPng process without binding it to an IPv6 VPN instance, the process belongs to the public network. By configuring RIPng process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of different VPNs to be exchanged between the IPv6 MCE and the sites through different RIPng processes, ensuring the separation and security of IPv6 VPN routes. For more information about RIPng, see Layer 3-IP Routing Configuration Guide. To configure RIPng between an MCE and a VPN site: Step Command Remarks 1. Enter system view. system-view N/A 2. Create a RIPng process for a VPN instance and enter RIPng ripng [ process-id ] vpn-instance view. vpn-instance-name Perform this configuration on the IPv6 MCE. On the VPN site, configure normal RIPng. 3. Redistribute remote site routes import-route protocol [ process-id ] By default, no route of any other advertised by the PE. [ allow-ibgp ] [ cost cost | routing protocol is redistributed route-policy route-policy-name ] * into RIPng. 4. (Optional.) Configure the default cost value for the redistributed routes. default cost value If you do not specify a default cost value, the default cost value is 60. 5. Return to system view. quit N/A 6. Enter interface view. interface interface-type interface-number N/A 7. Enable RIPng on the interface. ripng process-id enable By default, RIPng is disabled. Configuring OSPFv3 between an IPv6 MCE and a VPN site An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an OSPFv3 process without binding it to an IPv6 VPN instance, the process belongs to the public network. By configuring OSPFv3 process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different OSPFv3 processes, ensuring the separation and security of IPv6 VPN routes. 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52

29
Step
Command
Remarks
2.
Configure an IPv6 static route
for an IPv6 VPN instance.
ipv6 route-static vpn-instance
s-vpn-instance-name
ipv6-address
prefix-length
{
interface-type
interface-number
[
next-hop-address
] |
nexthop-address
[
public
] |
vpn-instance
d-vpn-instance-name nexthop-address
}
[
permanent
] [
preference
preference-value
] [
tag
tag-value
]
[
description
description-text
]
By default, no IPv6 static
route is configured.
Perform this configuration
on the IPv6 MCE. On the
VPN site, configure
normal IPv6 static routes.
3.
(Optional.) Configure the
default precedence for IPv6
static routes.
ipv6 route-static default-preference
default-preference-value
If you do not specify a
default preference value,
the default preference
value is 60.
Configuring RIPng between an IPv6 MCE and a VPN site
A RIPng process belongs to the public network or a single IPv6 VPN instance. If you create a RIPng
process without binding it to an IPv6 VPN instance, the process belongs to the public network. By
configuring RIPng process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of different
VPNs to be exchanged between the IPv6 MCE and the sites through different RIPng processes, ensuring
the separation and security of IPv6 VPN routes.
For more information about RIPng, see
Layer 3—IP Routing Configuration Guide
.
To configure RIPng between an MCE and a VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a RIPng process for a
VPN instance and enter RIPng
view.
ripng
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
IPv6 MCE. On the VPN site,
configure normal RIPng.
3.
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
]
[
allow-ibgp
] [
cost
cost
|
route-policy
route-policy-name
] *
By default, no route of any other
routing protocol is redistributed
into RIPng.
4.
(Optional.) Configure the
default cost value for the
redistributed routes.
default cost
value
If you do not specify a default cost
value, the default cost value is 60.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable RIPng on the interface.
ripng
process-id
enable
By default, RIPng is disabled.
Configuring OSPFv3 between an IPv6 MCE and a VPN site
An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an
OSPFv3 process without binding it to an IPv6 VPN instance, the process belongs to the public network.
By configuring OSPFv3 process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of
different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different OSPFv3
processes, ensuring the separation and security of IPv6 VPN routes.