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

Configuring IPv6 MCE, Overview, Configuring VPN instances on an IPv6 MCE device

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Configuring IPv6 MCE This chapter describes how to configure the IPv6 MCE function. Overview In MPLS L3VPN networks, MCE uses static routes or dynamic routing protocols to advertise IPv4 routes between internal networks and PEs and forwards IPv4 packets. In IPv6 MPLS L3VPN networks, IPv6 MCE uses IPv6 static routes and dynamic routing protocols to advertise IPv6 routes between internal networks and PEs and forwards IPv6 packets. The fundamentals of IPv6 MCE are the same as those of MCE. For more information, see "How MCE works." Configuring VPN instances on an IPv6 MCE device Configuring VPN instances is required in all MCE networking schemes. VPN instances isolate not only VPN routes from public network routes, but also routes among VPNs. Creating a VPN instance You can configure a description for a VPN instance to record its related information, such as its relationship with a certain VPN. To create and configure a VPN instance: Step 1. Enter system view. 2. Create a VPN instance and enter VPN instance view. 3. Configure an RD for the VPN instance. 4. (Optional.) Configure a description for the VPN instance. Command system-view ip vpn-instance vpn-instance-name route-distinguisher route-distinguisher description text Remarks N/A By default, no VPN instance is created. By default, no RD is specified for the VPN instance. By default, no description is configured for the VPN instance. NOTE: To configure BGP for a VPN instance on the MCE, you must configure an RD for the VPN instance. Associating a VPN instance with an interface After configuring a VPN instance, you must associate the VPN instance with the interfaces connected to the VPN site and the PE. To associate a VPN instance with an interface: 26

  • 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
26
Configuring IPv6 MCE
This chapter describes how to configure the IPv6 MCE function.
Overview
In MPLS L3VPN networks, MCE uses static routes or dynamic routing protocols to advertise IPv4 routes
between internal networks and PEs and forwards IPv4 packets.
In IPv6 MPLS L3VPN networks, IPv6 MCE uses IPv6 static routes and dynamic routing protocols to
advertise IPv6 routes between internal networks and PEs and forwards IPv6 packets. The fundamentals
of IPv6 MCE are the same as those of MCE. For more information, see "
How MCE works
."
Configuring VPN instances on an IPv6 MCE device
Configuring VPN instances is required in all MCE networking schemes.
VPN instances isolate not only VPN routes from public network routes, but also routes among VPNs.
Creating a VPN instance
You can configure a description for a VPN instance to record its related information, such as its
relationship with a certain VPN.
To create and configure a VPN instance:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a VPN instance and
enter VPN instance view.
ip vpn-instance
vpn-instance-name
By default, no VPN instance is
created.
3.
Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
By default, no RD is specified for
the VPN instance.
4.
(Optional.) Configure a
description for the VPN
instance.
description
text
By default, no description is
configured for the VPN instance.
NOTE:
To configure BGP for a VPN instance on the MCE, you must configure an RD for the VPN instance.
Associating a VPN instance with an interface
After configuring a VPN instance, you must associate the VPN instance with the interfaces connected to
the VPN site and the PE.
To associate a VPN instance with an interface: