Binding Interfaces to a VPN Instance

After an interface is bound to a VPN instance, the interface becomes a part of the VPN. Packets entering the interface will be forwarded based on the VRF table of the VPN.

Context

After a VPN instance is configured on a PE, an interface that belongs to the VPN must be bound to the VPN instance. Otherwise, the interface functions as a public network interface and cannot forward VPN data.

Perform the following steps on the PEs that are connected to CEs:

Procedure

Run system-view
The system view is displayed.
Run interface interface-type interface-number
The interface view is displayed.
Run ip binding vpn-instance vpn-instance-name
The interface is bound to the VPN instance.

Using the ip binding vpn-instance command will delete Layer 3 (including IPv4 and IPv6) configurations, such as the IP address and routing protocol, on the interface. Reconfigure them after using the ip binding vpn-instance command if needed.
Run ipv6 enable
IPv6 is enabled on the interface.
Run ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length }
An IPv6 address is configured for the interface. After this command is run, some Layer 3 features, such as route exchange between the PE and CE, can be configured only after an IPv6 address is configured for the VPN interface on the PE.
Run commit
The configuration is committed.