cancel
Showing results for 
Search instead for 
Did you mean: 

Strange configuration behavior

Sydney_N
New Contributor III

I've noticed this recently with a couple different ICX 8200 switches - when I do a show vlan brief for a port, it's not accurate. Here's an example:

SWITCH#sh vlan br e 3/1/16
Port 3/1/16 is a member of 2 VLANs
VLANs 451 to 452
Untagged VLAN :
Tagged VLANs : 451 to 452
!
SWITCH#sh run vlan 452
vlan 452 name Students by port
tagged ethe 1/2/2 ethe 1/2/4 ethe 2/2/2 ethe 2/2/4 ethe 3/2/2
untagged ethe 1/1/22 to 1/1/23 ethe 1/1/29 to 1/1/32 ethe 1/1/34 to 1/1/35 ethe 1/1/40 ethe 2/1/25 ethe 3/1/1 to 3/1/31
spanning-tree 802-1w
!
SWITCH(config-vlan-452)#no untag e 3/1/16
Error - Port 3/1/16 is not a dual-mode port
SWITCH(config-vlan-452)#no tag e 3/1/16
Error - Port(s) ethe 3/1/16 are not tagged members of vlan 452
SWITCH(config-vlan-452)#untag e 3/1/16
Port(s) ethe 3/1/16 are already a member of VLAN 452
!

The vlan brief says the port is tagged on v452, the vlan itself says it's untagged, and then when I tried untagging/tagging/removing from vlan, the config says it's not dual-mode, it's not tagged, and it's already a member of v452. It just seems unusual and I don't know what to do about it aside from a reload (which I did). I tried untagging the port to a different vlan, but I would prefer it was on the 452 vlan. 

1 ACCEPTED SOLUTION

Mayank
RUCKUS Team Member

Hi Sydney,

Thank you for reaching us.

As the issue remains after the upgrade. I would advise you to open a case with us.

Please log a ticket with the below link so that we will help you further.

https://support.ruckuswireless.com/contact-us

I hope this information helps you

Please feel free to leave us a message if any concerns

Note: Please feel free to mark the post as ACCEPTED SOLUTIONS if its addressed your query.

Thanks

View solution in original post

7 REPLIES 7

Chandini
RUCKUS Team Member

Hi Sydney_N

Ack and Thanks for reverting. Noted on the problem. After reload was the issue fixed or did it remain ?

Thanks 

Sydney_N
New Contributor III

The issue remains after the upgrade to cd2. 

Mayank
RUCKUS Team Member

Hi Sydney,

Thank you for reaching us.

As the issue remains after the upgrade. I would advise you to open a case with us.

Please log a ticket with the below link so that we will help you further.

https://support.ruckuswireless.com/contact-us

I hope this information helps you

Please feel free to leave us a message if any concerns

Note: Please feel free to mark the post as ACCEPTED SOLUTIONS if its addressed your query.

Thanks