Enabling and Disabling a Virtual Link Extension End-to-End
At times, whether in the CLI or in the Pluribus UNUM GUI, it can be convenient to manage vLE ports in pairs as a single entity (instead of doing so individually). Starting from Netvisor ONE release 6.0.0, a new end-to-end vLE configuration option can be used to enable or disable both vLE ports at the same time as part of the vle-create command.
The new ports-state option can have three values:
- override is the default setting which means that, as usual, 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.
For example:
CLI (network-admin@swi01) > vle-create name vle-test node-1 swi01 node-2 swi02 node-1-port 13 node-2-port 13 no-tracking ports-state disable
Note: If node-1 and node-2 are the same switch, then it becomes a local vLE configuration.
The vle-modify command can be used to further change the end-to-end vLE configuration after the initial vle-create.
For example, after setting ports-state to disable in vle-create, the user can revert to the default behavior in which local port configuration takes prececence with the following command:
CLI (network-admin@swi01) > vle-modify name vle-test ports-state override
In case of responsibility conflict in the CLI a message is printed out to explain what is taking precedence and to suggest a possible course of action.
For example, when a user tries to disable a vLE port when ports-state is set to enable, the following message is printed:
CLI (network-admin@swi01) > vle-show layout vertical
name: vle-test
vnet:
node-1: swi01
node-2: swi02
node-1-port: 13
node-2-port: 13
status: up
tracking: enabled
ports-state: enable
create-time: 08:47:56
CLI (network-admin@swi01) > port-config-modify port 13 disable
port-config-modify: could not disable port 13 as it is VLE vle-test administratively enabled port. Use the following cli to override: vle-modify name vle-test ports-state override
Similarly, when a user tries to enable a vLE port when ports-state is disable:
CLI (network-admin@swi01) > vle-show layout vertical
name: vle-test
vnet:
node-1: swi01
node-2: swi02
node-1-port: 13
node-2-port: 13
status: disabled
tracking: enabled
ports-state: disable
create-time: 08:47:56
CLI (network-admin@swi01) > port-config-modify port 13 enable
port-config-modify: could not enable port 13 as it is VLE vle-test administratively disabled port. Use the following cli to override: vle-modify name vle-test ports-state override
Even when the user configuration intent is the same (both in the local configuration and the vLE configuration), but there is still a responsibility conflict, a message is also printed out. For example, when a user tries to disable a vLE port when ports-state is disable:
CLI (network-admin@swi01) > vle-show layout vertical
name: vle-test
vnet:
node-1: swi01
node-2: swi02
node-1-port: 13
node-2-port: 13
status: disabled
tracking: enabled
ports-state: disable
create-time: 08:47:56
CLI (network-admin@swi01) > port-config-modify port 13 disable
port-config-modify: could not disable port 13 as it is VLE vle-test administratively disabled port. Use the following cli to override: vle-modify name vle-test ports-state override
Or when a user tries to enable a vLE port when ports-state is enable:
CLI (network-admin@swi01) > vle-show layout vertical
name: vle-test
vnet:
node-1: swi01
node-2: swi02
node-1-port: 13
node-2-port: 13
status: up
tracking: enabled
ports-state: enable
create-time: 08:47:56
CLI (network-admin@swi01) > port-config-modify port 13 enable
port-config-modify: could not enable port 13 as it is VLE vle-test administratively enabled port. Use the following cli to override: vle-modify name vle-test ports-state override