Configuring a DCI Scenario with a VLAN Layer 3 Sub-interface Accessing a Common L3VPN

The DCI Scenario with a VLAN Layer 3 Sub-interface Accessing a Common L3VPN uses different cloud management platforms, and a Layer 3 Ethernet sub-interface is associated with a VLAN to access an L3VPN.

Context

An underlay VLAN can access a DCI network through a Layer 3 gateway when traditional DCs are connected through the DCI network.

GWs and DCI-PEs are separately deployed. Each DCI-PE considers the GW of a data center as a CE, uses a Layer 3 VPN routing protocol to receive VM host routes from the data center, and saves and maintains the routes.

If VXLAN is deployed in the data center, the solution of Underlay VLAN Layer 3 access to DCI can be used. In Figure 1, VXLAN tunnels are established within data centers to allow intra-DC VM communication. To allow inter-data center VM communication, BGP/MPLS IP VPN functions are deployed on the DCI backbone network, and a Layer 3 Ethernet sub-interface is configured on each DCI-PE, added to the same VLAN, and bound to the VPN instance of each DCI-PE.

Figure 1 Configuring a DCI Scenario with a VLAN Layer 3 Sub-interface Accessing a Common L3VPN

Procedure

Configure basic L3VPN functions on the DCI backbone network. For configuration details, see Configuring a Basic BGP/MPLS IP VPN.
Configure a dot1q VLAN tag termination sub-interface and bind the sub-interface to a VPN instance.
1. Run interface interface-type interface-number.subinterface-number
  An Ethernet sub-interface is created, and its view is displayed.
2. Run vlan-type dot1q vlan-id
  A VLAN is bound to the sub-interface, and a VLAN encapsulation mode is specified.
3. Run ip binding vpn-instance vpn-instance-name
  The sub-interface is bound to a VPN instance.
4. Run ip address ip-address { mask | mask-length }
  An IP address is configured for the sub-interface.
Run commit
The configuration is committed.