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

Configuring routing on an IPv6 MCE device

Page 31 highlights

Step Command 7. (Optional.) Apply an export routing policy. export route-policy route-policy Remarks By default, routes to be advertised are not filtered. Make sure the routing policy already exists. Otherwise, the device does not filter routes to be advertised. NOTE: • Route related attributes configured in VPN instance view are applicable to both IPv4 VPNs and IPv6 VPNs. • You can configure route related attributes for IPv6 VPNs in both VPN instance view and IPv6 VPN view. Those configured in IPv6 VPN view take precedence. Configuring routing on an IPv6 MCE device An IPv6 MCE implements service isolation through route isolation. IPv6 MCE routing configuration includes the following: • IPv6 MCE-VPN site routing configuration. • IPv6 MCE-PE routing configuration. Before you configure routing on an IPv6 MCE, complete the following tasks: • On the IPv6 MCE, configuring VPN instances, and binding the VPN instances with the interfaces connected to the VPN sites and those connected to the PE. • Configuring the link layer and network layer protocols on related interfaces to ensure IP connectivity. Configuring routing between an IPv6 MCE and a VPN site You can configure IPv6 static routing, RIPng, OSPFv3, IPv6 IS-IS, or EBGP between the MCE and a VPN site. Configuring IPv6 static routing between an IPv6 MCE and a VPN site An IPv6 MCE can reach a VPN site through an IPv6 static route. IPv6 static routing on a traditional CE is globally effective and does not support address overlapping among VPNs. An IPv6 MCE supports binding an IPv6 static route with an IPv6 VPN instance, so that the IPv6 static routes of different IPv6 VPN instances can be isolated from each other. To configure IPv6 static routing between IPv6 MCE and VPN site: Step 1. Enter system view. Command system-view Remarks N/A 28

  • 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

28
Step
Command
Remarks
7.
(Optional.) Apply an export
routing policy.
export route-policy
route-policy
By default, routes to be advertised
are not filtered.
Make sure the routing policy
already exists. Otherwise, the
device does not filter routes to be
advertised.
NOTE:
Route related attributes configured in VPN instance view are applicable to both IPv4 VPNs and IPv6
VPNs.
You can configure route related attributes for IPv6 VPNs in both VPN instance view and IPv6 VPN view.
Those configured in IPv6 VPN view take precedence.
Configuring routing on an IPv6 MCE device
An IPv6 MCE implements service isolation through route isolation. IPv6 MCE routing configuration
includes the following:
IPv6 MCE-VPN site routing configuration.
IPv6 MCE-PE routing configuration.
Before you configure routing on an IPv6 MCE, complete the following tasks:
On the IPv6 MCE, configuring VPN instances, and binding the VPN instances with the interfaces
connected to the VPN sites and those connected to the PE.
Configuring the link layer and network layer protocols on related interfaces to ensure IP
connectivity.
Configuring routing between an IPv6 MCE and a VPN site
You can configure IPv6 static routing, RIPng, OSPFv3, IPv6 IS-IS, or EBGP between the MCE and a VPN
site.
Configuring IPv6 static routing between an IPv6 MCE and a VPN site
An IPv6 MCE can reach a VPN site through an IPv6 static route. IPv6 static routing on a traditional CE
is globally effective and does not support address overlapping among VPNs. An IPv6 MCE supports
binding an IPv6 static route with an IPv6 VPN instance, so that the IPv6 static routes of different IPv6 VPN
instances can be isolated from each other.
To configure IPv6 static routing between IPv6 MCE and VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A