Virtual Link Extension Commands
vle-create
This command creates virtual link extension tracking. You can execute this command from any fabric node to create a virtual link extension between any two switches in the fabric, and ports on the same switch.
Syntax vle-create
name name-string |
Specify the name of the vLE. |
vnet vnet-name |
Specify the vNET name. |
node-1 fabric-node name |
Specify the name of vLE node 1. |
node-2 fabric-node name |
Specify the name of vLE node 2. |
node-1-port node-1-port-number |
Specify the name of the node-1 port that is part of vLE. |
node-2-port node-2-port-number |
Specify the name of the node-2 port that is part of vLE. |
node-1-port-desc node-1-port-desc-string |
Specify a description for the vLE node-1 port. |
node-2-port-desc node-2-port-desc-string |
Specify a description for the vLE node-2 port. |
[tracking|no-tracking] |
Enable or disable tracking between vLE ports. |
ports-state override|enable|disable |
Specify the port state. Use this option to enable or disable vLE ports at the same time. override is the default setting which means that each individual port state configuration takes precedence. disable means that both vLE ports get disabled together, and this option takes precedence over each individual port state. enable means that both vLE ports get enabled, and this option takes precedence over each individual port state. |
tunnel-name tunnel name |
Specifies the tunnel name to transport to other vLE EP. |
vxlan vlan vxlan |
Specifies the VNI to transport the vLE. |
Defaults None.
Access CLI
History
Version 2.5.4 |
Command introduced. |
Version 6.0.0 |
The parameter ports-state added. |
Version 6.1.0 |
The parameter vnet added. |
Version 7.0.0 |
The parameters node-1-port-desc, and node-2-port-desc added. |
Version 7.0.1 |
The parameters tunnel-name and vxlan added. |
Usage Provides a mechanism for link state tracking between two ports of two switches in the same fabric for Virtual Link Extension (vLE). When a vLE is created between two physical ports of two switches, the vLE remains up as long as both physical ports are in the state link up.
When vLE tracking is created on a trunk port, the vLE stays up as long as at least one port in the trunk is link up, and the remote port is also up. When the last trunk member goes link down, the vLE is brought down. When you configure vLE tracking on a trunk port, you cannot configure tracking on individual trunk members.
vLE tracking helps achieve vLE high availability on NetVisor OS nodes, and avoid the need on the client side to run LACP for link up/down detection.
Examples This example shows how create virtual link extension tracking between two ports of two switches with tracking enabled.
CLI (network-admin@switch) > vle-create name myvle node-1 myfabric node-1-port 56 node-2 yourfabric node-2-port 66 tracking