Binding EVPN Instances and VSIs to BDs

To implement interconnection between an enterprise campus network and a DC, bind an EVPN instance and a VSI to the same BD created on each of PE1 and PE2.

Procedure

Configure PE1 and PE2.
1. Run bridge-domain bd-id
  The BD view is displayed.
2. Run vxlan vni vni-id split-horizon-mode
  A VNI is created and bound to a BD, and split horizon is configured for packet forwarding.
3. Run evpn binding vpn-instance vpn-instance-name [ bd-tag bd-tag ]
  A specified EVPN instance is bound to the BD. By specifying different bd-tag values, you can bind multiple BDs with different VLANs to the same EVPN instance and isolate services in the BDs.
4. Run l2 binding vsi vsi-name
  A specified VSI is bound to the BD.
  
  On a node that provides interworking between VXLAN and VPLS, the BD-bound VSI does not support pw-tag, and the PW configured in the VSI must be in Raw mode rather than in Tag mode.
5. Run quit
  Return to the system view.
6. Run commit
  The configuration is committed.
  - On a stitching point, the VSIs and EVPN instances bound to BDs have a 1:1 mapping relationship, but multiple VSIs and EVPN instances cannot be bound to the same BD, and multiple VSIs or EVPN instances cannot access the same BD.
Bind the AC interface to the BD on PE3.
1. Run system-view
  The system view is displayed.
2. Run bridge-domain bd-id
  The BD view is displayed.
3. Run l2 binding vsi vsi-name [ pw-tag pw-tag-value ]
  A specified VSI is bound to the BD.
4. Run quit
  Exit from the BD view.
5. Run interface interface-type interface-number.subnum mode l2
  A Layer 2 sub-interface is created, and the sub-interface view is displayed.
6. Run bridge-domain bd-id
  The Layer 2 sub-interface is bound to the BD.
  
  The Layer 2 sub-interface and the vsi are bound to the same BD.
7. Run quit
  Exit from the sub-interface view.
8. Run commit
  The configuration is committed.