ExtremeSwitching (EXOS)

Expand all | Collapse all

EXOS: give more feedback on CLI

  • 1.  EXOS: give more feedback on CLI

    Posted 10-17-2018 05:38
    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.



  • 2.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 05:47
    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!


  • 3.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 14:45
    Hi everyone, I contacted engineering and they've created a CR for this enhancement. There were a few questions posted that we would like to get your input on.

    One problem that can arise is that the user canspecify a port range or list of ports. What is returned when a subset ofports in the range/list fail the command? Would you want to see these informational messages for every port in the range/list?


  • 4.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    Hi,

    To Jeronimo :

    The configuration command is the target you want to achieve.

    If this target was already in place, is there any need to display some error or warning message ?

    Please, can you describe what should be the usage of this message ?

    Thanks



  • 5.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 05:47
    # 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
    #



  • 6.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    I like to know when I input a command that doesn't make sense.

    Any number of things could cause this: I am on the wrong switch, I issued the command for the wrong port, etc. The earlier I get a message that the actual outcome is probably not the expected outcome, it is always great to know. The earlier, the better.

    Mainly it's about minimizing human error.



  • 7.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    Hi Jeronimo,

    What is your EXOS version?
    Please take a look at this command and its completion:
    configure vlan untagged-ports auto-move[/code]It might be set to 'on' and I thing thats the case.
    It might be set to informational or turned off, the latter will induce an error when you try to move a port untagged from one VLAN to another VLAN as untagged.

    There is no such thing as moving ports between VLANs when they are tagged, as port can be a member of many VLANs when tagged. I doubt should it ask you "are you sure", as you're the expert to know what's going on. 😉 And an output that is exactly the same what you have issued in CLI is not useful at all - it doesn't make sure you're on the correct switch, that you will be sure of when phones begin to call. ;)
    On the other hand, feature like commit/rollback would be awesome.

    HTH,
    Tomasz


  • 8.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    I've tried EXOS 22.6.
    I disagree that the output should be the same (in this case none) when the preconditions are different (port already assigned to that VLAN vs. port not already assigned to the VLAN).
    Maybe no output would be ok on the latter but not on the former. When you try to assign a port to a VLAN it is already a member of, there should be some message, as what you're trying to do makes no sense.
    Yes, the human should be the expert, but if it is easy for the machine to give suggestions, that can't hurt.


  • 9.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    I try to name each switch too, so the command line reflects which switch I'm on. Helps keep mistakes to a minimum.


  • 10.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 06:02
    Well, perhaps it would be enough to have such event in EMS that last issued command does not influence the running configuration (like removing port from vlan in which it is not defined). I'm not sure if it is there but It should be much easier for Extreme to apply. Then you would see those if you had 'enable log display' or 'enable log target session' commad issued.


  • 11.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 14:45
    Hi,

    I'd say it is important that the messages are clearly informational, and not warnings. I would prefer to get one message giving the list of ports that were already part of the VLAN, if a message is given.

    In general, I think it is important that a command that is already part of the configuration can still be issued without problems (idempotence). In fact I would prefer to have a way to disable messages about not changing anything by issuing a command.

    I do think that jeronimo's idea has merit, but there are situations where no messages are preferred, e.g. applying a configuration script a second time after adding (instead of changing) something.

    Thanks,
    Erik


  • 12.  RE: EXOS: give more feedback on CLI

    Posted 10-17-2018 14:45
    Maybe configuration difficulty levels should be introduced: when you first boot the switch, you get to choose between infant, normal and Extreme mode. Infant mode displays graphical wizards for everything. Normal would be more or less what we have now. Extreme difficulty displays no output whatsoever, not even an echo of what you type. That last one is what real experts are craving.

    Now getting back to your question =)

    First, I believe whatever information you choose to display, it should be clear from the output that all ports were set, while some could not be set. (So that people don't think there was an error and need to repeat the command. I am sometimes lazy myself and just set ranges even though I know it will fail for some ports.)

    Now we can have ranges specified for the VLAN as well as the ports, and there are additional settings like specifying an STP domain and such. Setting any of these could go wrong.

    My first approach would have been to display conflicts in one summary line of output like "Ports configured, however ports already were tagged members of VLAN