VOSS 8600 config so fractured its hard to read

[Anonymous]

Hi,

I’m finding the configuration on the VSP8600 very fractured and hard to read, and thereby hard to configure and fault find, on top of that there is no pipe command.

Here is an example below…. if I need to configure an interface / port it is referenced in so many places, which when you have a large configuration its near impossible to find efficiently. Only way I’ve found to manage it is export the config and use Notepad++ to filter and scroll the information.

#
# PORT CONFIGURATION - PHASE I
#

interface GigabitEthernet 2/1
encapsulation dot1q

# MLT CONFIGURATION
#

mlt 411 member 1/1
mlt 411 encapsulation dot1q
mlt 412 enable


#
# VLAN CONFIGURATION
#

vlan mlt 2 401
vlan members 2 2/23-2/24,3/24,4/23-4/24,5/24,6/23-6/24 portmember


#
# PORT CONFIGURATION - PHASE II
#

interface GigabitEthernet 6/13
default-vlan-id 0
name "Port-Name"
lacp key 32 aggregation enable timeout-time short
lacp enable
exit

With that in mind I just wondered if I’m missing something, or there is an easy way for example to see all the configuration for a given port  without having to route for it all over the configuration.

Appreciate that maybe this is all meant to be driven by EDM, and maybe the reason it is the way it is but CLI would typically be how I set something up from scratch. 

Obviously a pipe command would be good.

Many thanks in advance

[Anonymous]

Hi Ludovico,

Thank you for posting back….

Interesting you mention this as a was sitting in the back of the room on a recent POC and observing you using these commands, and was making notes.

I’ve tried to query this a couple of times through various channels but did not lead anywhere, so its been great that you have been able to reply, and now know what it is.

Will certainly take a look, as sure it will help.

Many thanks,

Martin

[Ludovico_Steven · Accepted solution]

The pipe “|” include/exclude CLI capability will be in VSP8600 software 8.0 due out Sept/Oct.

That said, it usually does not help much for doing grep of a configuration which has configuration contexts. To give you an example, you will get the same you already get today with other VOSS VSP platforms:

VSP8200-1:1#show running-config | include 2/1

************************************************************************************

                Command Execution Time: Thu Jul 09 09:35:38 2020 BST

************************************************************************************

interface GigabitEthernet 2/10

interface GigabitEthernet 2/13

interface GigabitEthernet 2/14

mlt 1 member 2/1

vlan members remove 1 1/1-1/3,1/5-1/7,1/10,1/17-1/18,1/23,1/39,1/41-1/42,2/1-2/4,2/9,2/12-2/14,2/23,2/34,2/41

interface GigabitEthernet 2/1

interface GigabitEthernet 2/10

interface GigabitEthernet 2/12

interface GigabitEthernet 2/13

interface GigabitEthernet 2/14

interface GigabitEthernet 2/15

interface GigabitEthernet 2/16

interface GigabitEthernet 2/17

interface GigabitEthernet 2/18

interface GigabitEthernet 2/19

qos queue-profile 1 member add 1/1-1/42,2/1-2/42

VSP8200-1:1#

Which is not hugely useful, as you cannot see anything which is actually configured under port 2/1 and it matches other ports matching “2/1”

I shall take the opportunity to promote my own home-made ACLI terminal, which handles grep on the terminal itself and has a bunch of other features designed for Extreme switches.

With it you can then see the config for a given port, here an example on one of our lab VSP8600s:

VSP8600-1:1#% cfg||1/3

       alias% show running-config  -ib ||1/3

config terminal

interface GigabitEthernet 1/3

   encapsulation dot1q

exit

vlan members remove 1 1/1-1/6,2/1-2/2,2/7,2/10-2/14,2/24,3/1-3/2,3/5-3/6

interface GigabitEthernet 1/3

   default-vlan-id 0

   no shutdown

   isis

   isis spbm 1

   isis spbm 1 l1-metric 20

   isis enable

   no spanning-tree mstp  force-port-state enable

   no spanning-tree mstp msti 62 force-port-state enable

exit

qos queue-profile 1 member add 1/1-1/6,2/1-2/24,3/1-3/16

end

VSP8600-1:1#%

Note that you get even lines where port 1/3 is part of a range, like the qos queue-profile config line.

You can get the ACLI terminal here:

http://www.oranda.fr/ACLI-terminal/

[Anonymous]

Hi,

Thanks for post back and for the information, that is useful.

Having said that, its still pretty challenging, just doesn’t look like the cli is really designed or optimised for large configurations or general use i.e why have two sections for same the interface phase 1 and phase 2?

Why have other elements of the config that then refer to the port rather than the interface?

Why can’t I for example just show the running config for an interface and get all the information for it instead of running all over the config trying to collate it all together.

Its really hard when configuring the switch to see where a configuration might be wrong or missing or compare to say another interface that you know is working.

Seems more its taken second place to the EDM which is great, but can’t compete with a good cli.

Probably just me needing to get used to it, but be interesting to see how others are getting around these challenges.

Cheers.

[jnowakowski]

Hi Martin,

Have you tried looking at the running config on the switch?

show running-config module port

I’m very new to VOSS and this has helped me with figuring out what is set for various modules in the config file.