The l2 binding vsi command binds a VSI to an interface.
The undo l2 binding vsi command restores the default configuration.
The l2 binding vsi multi-homing-site command binds a multi-homing site to an AC interface.
The undo l2 binding vsi multi-homing-site command unbinds a multi-homing site from an AC interface.
By default, a VSI instance is not bound to an interface.
By default, a multi-homing site is not bound to any AC interface.
| Parameter | Description | Value |
|---|---|---|
| multi-homing-site site-name |
Specifies a multi-homing site name. |
The value is a string of 1 to 19 case-sensitive characters, spaces not supported. The string can contain only letters, digits, underscores (_), and hyphens (-) and must start with letters. |
| vsi vsi-name |
Specifies the name of the VSI to be bound to an interface. The VSI name specified here must be consistent with that specified in the vsi vsi-name command. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
100ge sub-interface view, 100GE interface view, 10GE sub-interface view, 10GE interface view, 200GE sub-interface view, 25GE sub-interface view, 25GE interface view, 400GE sub-interface view, 400GE interface view, 40GE sub-interface view, 40GE interface view, 50GE sub-interface view, 50GE interface view, Eth-Trunk sub-interface view, Eth-Trunk interface view, GE optical interface view, GE sub-interface view, GE interface view, GE electrical interface view, Global VE sub-interface view, VE sub-interface view, VLANIF interface view, XGE sub-interface view, XGE interface view
Usage Scenario
After a VSI is created and configured, you must run the l2 binding command on an AC interface to bind the AC interface to the VSI.
In VPLS multi-homing scenarios, after a multi-homing site is configured, run the l2 binding vsi multi-homing-site command to bind the multi-homing site to an AC interface. This configuration allows PEs to determine the master/backup status of the AC interfaces based on the bound multi-homing sites so that the backup AC interface can be blocked and traffic is forwarded only through the preferred AC interface.Prerequisites
A VSI has been created and configured. For example, the VSI ID and peer IP address have been configured.
A multi-homing site ID has been configured using the site-id site-id command.Configuration Impact
After an interface is bound to a VSI, the interface can no longer be configured with Layer 3 services, such as the IP address. The VPWS or L3VPN cannot be configured either.
After multi-homing sites are bound to AC interfaces, the PE calculates the master/backup status of the AC interfaces again based on the bound multi-homing sites. If the calculation result changes, the PE instructs the remote PE on the PW to converge routes.Follow-up Procedure
After an interface is bound to a VSI, you can run the display vsi command to view whether the VSI status is Up, according to which you can find whether the PW is set up successfully for the VSI.
Precautions
The IP addresses of CE interfaces connected to the AC interfaces on both ends must be different.
VXLAN and VPLS are mutually exclusive. If VXLAN is configured on an AC interface, you cannot run the l2 binding command to bind the AC interface to a VSI. If the user-queue, qos-profile, car, or qos hard-pipe bandwidth command is run on an interface, the l2 binding command cannot be run to bind the interface to a VSI for which hard pipe is enabled. If the l2 binding command is run, an error message is displayed. A local VSI in P2P mode does not allow QinQ/dot1q VLAN tag termination sub-interfaces, QinQ stacking sub-interfaces, QinQ mapping sub-interfaces, flexible sub-interfaces, or VE interfaces to function as AC interfaces. VPLS multi-homing blocks data packets on the AC interface of the backup PE to prevent loops. Therefore, you do not need to deploy other loop avoidance protocols, such as STP/MAC Flapping. If STP/MAC Flapping is deployed, the AC interfaces of both the master and backup PEs may be blocked, because the AC interface of the backup PE does not block Layer 2 protocol packets. As a result, traffic is interrupted.Only the NetEngine 8000 F1A supports hard pipe.
<HUAWEI> system-view [~HUAWEI] mpls [*HUAWEI-mpls] quit [*HUAWEI] mpls l2vpn [*HUAWEI-l2vpn] quit [*HUAWEI] vsi company1 [*HUAWEI-vsi-company1] quit [*HUAWEI] interface GigabitEthernet 0/1/9.1 [*HUAWEI-GigabitEthernet0/1/9.1] vlan-type dot1q 10 [*HUAWEI-GigabitEthernet0/1/9.1] l2 binding vsi company1
<HUAWEI> system-view [~HUAWEI] mpls [*HUAWEI-mpls] quit [*HUAWEI] mpls l2vpn [*HUAWEI-l2vpn] quit [*HUAWEI] vsi vsi1 [*HUAWEI-vsi-vsi1] pwsignal bgp multi-homing [*HUAWEI-vsi-vsi1-bgp] route-distinguisher 192.168.1.1:1 [*HUAWEI-vsi-vsi1-bgp] site name company1 [*HUAWEI-vsi-vsi1-bgp-site-company1] site-id 20 [*HUAWEI-vsi-vsi1-bgp-site-company1] quit [*HUAWEI-vsi-vsi1-bgp] quit [*HUAWEI-vsi-vsi1] quit [*HUAWEI] interface GigabitEthernet 0/1/0 [*HUAWEI-GigabitEthernet0/1/0] l2 binding vsi vsi1 multi-homing-site company1