Binding a VPN Instance to an Interface

A VPN instance has been created and the IPv4 address family has been enabled for the VPN instance.

After configuring a VPN instance on a PE device, bind the VPN instance to the interface that belongs to the VPN. Otherwise, the interface functions as a public network interface and cannot forward VPN data.
An interface becomes a private network interface after a VPN instance is bound to it. You must configure an IP address for the interface so that the PE device can exchange routing information with its attached CE device.
After a VPN instance is bound to an interface, configuration of the Layer 3 features (IPv4 and IPv6 features) including IP addresses and routing protocols is deleted from the interface.
When you disable an address family (IPv4 or IPv6 address family) in a VPN instance, configuration of the address family is deleted from the interface. No interface is bound to a VPN instance if no address family configuration exists in the VPN instance.

Perform the following steps on the PE devices.

Run system-view
The system view is displayed.
Run interface interface-type interface-number
The interface view is displayed.
(Optional) On an Ethernet interface, run undo portswitch
The interface is switched to Layer 3 mode.

By default, an Ethernet interface works in Layer 2 mode.

Only the S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6720-EI, S6720-HI, S6720S-EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support switching between Layer 2 and Layer 3 modes.
Run ip binding vpn-instance vpn-instance-name
A VPN instance is bound to the interface.

By default, an interface is a public network interface and is not associated with any VPN instance.
Run ip address ip-address { mask | mask-length }
An IP address is configured for the interface.