I'm coming across something weird. I'm trying to config a new VLAN on a Cisco 4507 running IOS 12.2.
I can create the VLAN just fine. I can put ports into the VLAN just fine. The ports do show up and passing some traffic. Only problem is that the VLAN itself does not come up. If I do a sho int for the VLAN, it shows that it is down and line proto is down.
In config I am making sure the int for the VLAN is not in shutdown mode.
I do see a couple of lines in the running config:
vlan internal allocation policy ascending
I am thinking this is limiting the VLANs that are in use. Should I add my new VLAN to this list?
Ah, I think i better understand the situation now.
This line defines the existing vlans on the switch. This is separate from the "Interface Vlan" which defines the layer 3 Switched Virtual Interface associated with a vlan.
So, with the vlans as created in the config above, if you were to create, for example, an interface Vlan5, it would not be up/up until you create the vlan in global config mode using the command "vlan 5" and then associating a connected port to vlan 5.
Adding a new vlan should not affect the existing running vlans. When you create a new vlan, a new instance of spanning-tree protocol will be spawned for that vlan, and the vlan will be added to the database in memory.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...