1-23
Task
Remarks
Configuring BGP AS Number Substitution
Optional
Configure it as needed
igure MPLS L3VPN:
Configuring VPN Instances
VPN instances are used to isolate VPN routes from public network routes. Configuring VPN instances is
required in all MPLS L3VPN networking schemes.
In addition, routes of a VPN instance are isolated from those of another. This feature allows VPN
instances to be used in networking schemes other than MPLS L3VPNs.
All VPN instance configurations are on PEs.
This section includes the following configurations:
z
Creating a VPN Instance
z
Associating a VPN Instance with an Interface
z
Configuring Route Related Attributes of a VPN Instance
z
Configuring a Tunneling Policy of a VPN Instance
Creating a VPN Instance
A VPN instance is associated with a site, rather than a VPN. It is a collection of the VPN membership
and routing rules of its associated site.
A VPN instance takes effect only after you configure an RD for it. Before configuring an RD for a VPN
instance, you can configure no parameters for the instance other than a description.
A VPN instance description is a piece of descriptive information about the VPN instance. You can use it
to keep information such as the relationship of the VPN instance with a VPN.
Follow these steps to create and configure a VPN instance:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a VPN instance and
enter VPN instance view
ip vpn-instance
vpn-instance-name
Required
Configure an RD for the VPN
instance
route-distinguisher
route-distinguisher
Required
Configure a description for the
VPN instance
description text
Optional
Associating a VPN Instance with an Interface
After creating and configuring a VPN instance, you associate the VPN instance with the interface for
connecting CEs. Any interface supporting MPLS LDP capability can be associated with a VPN instance.
For interfaces supporting MPLS LDP capability, refer to
MPLS Basics Configuration
in the
MPLS
Volume
.
Summary of Contents for S7906E - Switch
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist...
Page 598: ...ii...
Page 1757: ...4 9...
Page 1770: ...6 4...
Page 2017: ...2 11 Figure 2 3 SFTP client interface...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002...