EXOS: give more feedback on CLI

[jeronimo]

Hey,

I've been playing with EXOS and I noticed the following.

"configure vlan x delete port 2" does not throw an error when the port was not a member of the vlan in the first place.

Also, "configure vlan x add port 2" does not give a warning when the port was already a member before issuing the command

For the sake of transparency, I would find it useful if the switch gave some feedback in scenarios like these. Giving warnings in those cases can reduce the risk of administrative errors IMHO.

[Alexandr_P]

Hello!

First of all you have to check:
# sh por 2 vlan

""configure vlan x add port 2" does not give a warning when the port was already a member before issuing the command" port 2 was member of vlan as tagged or untagged port?

Because, if port 2 was in vlan X as untagged - so you have to receive error
Error: Protocol conflict when adding untagged port 2. Port 2 is already
untagged in vlan "Default".
Either add this port as tagged or assign another protocol to this VLAN.
configure vlan x add port 2 - default adding port as untagged

Thank you!

[jeronimo]

# configure vlan 11 add port 2
VLAN 11 xxx: Port 2 untagged has been auto-moved ....

So far, so good.

# configure vlan 11 add port 2
< no message here >
Better would be: Info: Port 2 already untagged member of VLAN 11
#

Similar thing for this:
# configure vlan 11 delete port 3
# configure vlan 11 add port 3 tagged
# configure vlan 11 add port 3 tagged
< no message here>
Better would be: Info: Port 3 already tagged member of VLAN 11
#

Or this:
# configure vlan 11 delete port 3
# configure vlan 11 delete port 3
< no message here>
Better would be: Info: Port 3 not a member of VLAN 11
#