Hi Daniel,
the customers, I know, don't use network maps, so far.
So at first they have to create and manage these for the entire network.
By selecting a VLAN and editing the ports you have to choose from all ports of the entire network map!
In my example, the map inclued 2 XOS Stacks. By clicking "Edit Port" it takes about aprox. 35 seconds until the "Edit VLAN Ports" window opens, which is not satisfying. and then you have to choose from all 192 Ports of the 2 stacks.
And what if you want to create a new trunk port with all, let's say, 20 VLANs tagged?... You have to do this procedure 20 times?!
Changing VLANs within a table would be much better.
For example, via Interface summary > select a port > edit VLAN xy (un)tagged > done!
Changing Port-VLANs is daily business for the customer and should be possible to do in no time.
On EOS it was just like: select a switch from the tree > got to VLAN > Basic Ports > select the port > show table editor > select the VLAN from the drop-down menu > apply!
And for Uplinks you could create a Template and just push it to the desired Uplink Port.
I hope I could explain why the customers are not pleased how VLANs are managable on XOS Switches compared with EOS Switches!
Is there a chance, this will be improved in NetSight v7?
Cheers,
Martin