24
Tasks at a glance
(Required.)
Configuring routing between an MCE and a PE
Configuring VPN instances
By configuring VPN instances on a PE, you isolate not only VPN routes from public network routes,
but also routes between VPNs. This feature allows VPN instances to be used in network scenarios in
addition to MPLS L3VPNs.
All VPN instance configurations are performed on PEs or MCEs.
Creating a VPN instance
A VPN instance is a collection of the VPN membership and routing rules of its associated site. A VPN
instance might correspond to more than one 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 instances
exist.
3.
Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
By default, no RD is configured for
a VPN instance.
4.
(Optional.) Configure a
description for the VPN
instance.
description text
By default, no description is
configured for a VPN instance.
The description should contain
the VPN instance's related
information, such as its
relationship with a certain VPN.
5.
(Optional.) Set an ID for the
VPN instance.
vpn-id vpn-id
By default, no ID is configured for
a VPN instance.
Associating a VPN instance with an interface
After creating and configuring a VPN instance, associate the VPN instance with the interface
connected to the CE.
To associate a VPN instance with an interface:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface interface-type
interface-number
N/A
3.
Associate a VPN instance
with the interface.
ip binding vpn-instance
vpn-instance-name
By default, an interface is not
associated with a VPN instance
and belongs to the public network.
The
ip binding vpn-instance
command clears the IP address of
the interface. Therefore,
reconfigure an IP address for the
