cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
948
Views
30
Helpful
7
Replies

VLAN ADDITION DID NOT GO INTO CURRENT LIST

HHUBS
Level 1
Level 1

Hello,

We have C3850 24ports and we are adding vlans on the 10G trunk port. The command use were:

(config-if)#switchport trunk allowed vlan add 429
(config-if)#switchport trunk allowed vlan add 430
(config-if)#switchport trunk allowed vlan add 431
(config-if)#switchport trunk allowed vlan add 432

But then when we check, instead of adding into the current line of allowed vlan, it creates another line like in the image below:

RRPedrigal_0-1669006018113.png

We expect it to be like this:

RRPedrigal_1-1669006158549.png

The trunking is ok and the data is flowing. We're just really puzzled why it is like that. You know, it's not usually what we see. Did you experience it before? 

1 Accepted Solution

Accepted Solutions

I agree with @Kasun Bandara that what you are experiencing is expected behavior. It is how the parser works as it builds the output of show run. There is a limit on the length of a line of output. When the number of vlans on a trunk is greater than will fit on a single line then the second (and following) lines appear and use the vlan add form of the command.

HTH

Rick

View solution in original post

7 Replies 7

Leo Laohoo
Hall of Fame
Hall of Fame

There is nothing wrong with that config.  The VLANs are there.  The allowed VLANs are from 429 to 432.

Gone were the days where the VLANs were listed down individually and making the configuration look very long.


@HHUBS wrote:

(config-if)#switchport trunk allowed vlan add 429
(config-if)#switchport trunk allowed vlan add 430
(config-if)#switchport trunk allowed vlan add 431
(config-if)#switchport trunk allowed vlan add 432


And this can be expressed in a single line:  switchport trunk allowed vlan add 429-432

its ok. it happens when list of VLANs, is over the limitation of single line

Please rate this and mark as solution/answer, if this resolved your issue
Good luck
KB

I agree with @Kasun Bandara that what you are experiencing is expected behavior. It is how the parser works as it builds the output of show run. There is a limit on the length of a line of output. When the number of vlans on a trunk is greater than will fit on a single line then the second (and following) lines appear and use the vlan add form of the command.

HTH

Rick

Hello
Its by default, after 12 entries, it will parse onto an additional allowed line


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

HHUBS
Level 1
Level 1

Thanks all for your comments. Last question, @paul driver can you refer me to the doc that states that 12 entry limit?

Hello
Don’t believe there is one tbh- The value i stated seems to be a default  as i’ve tested this on to both IOS and XE software and checked older ios running on live production hardware and 12 vlan statements (not vlans) seems to be a recurring value per line even in your OP 12 looks like the limit.

However the basic answer to your question was already answered by @Richard Burts and @Leo Laohoo which is what you see is expected behaviour when pruning trunk interfaces with multiple vlans


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

I am glad that our explanations have been helpful.  Thank you for marking this question as solved. This will help other participants in the community to identify discussions which have helpful information. This community is an excellent place to ask questions and to learn about networking. I hope to see you continue to be active in the community.

HTH

Rick