06-25-2012 12:51 PM - edited 03-07-2019 07:27 AM
Looking for a little help in why a newly created Vlan shows down/down when I issue a sh ip int brief command.
My setup is an AP with two SSIDs on two different Vlans (4 and 7). Traffic flows properly across Vlan 4, but Vlan 7 shows it is in a down state and cannot be pinged from the local switch. From documentation I've read, the Vlan should become active when a port, trunked or attached to the Vlan, connects to the Vlan. I have at least two ports trunked on the switch, (including the one the AP is connected to) but Vlan 7 does not appear to recognize them. Spanning-tree information comes back back with no instances for the Vlan. I presume this is due to the Vlan not being active.
What am I missing? Why will the Vlan not see the trunked ports, create the spanning tree instances, and activate so traffic can flow?
Solved! Go to Solution.