cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
47030
Views
16
Helpful
9
Replies

Vlan shows down/down

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?

1 Accepted Solution

Accepted Solutions

Interface vlan attaches a L3 svi to an already existing L2 vlan. Vlan database is being deprecated and you can create the L2 vlan with "vlan 7 " in global config. You will still need a L2 vlan configured for your L3 svi.

HTH,

John

HTH, John *** Please rate all useful posts ***

View solution in original post

9 Replies 9

glen.grant
VIP Alumni
VIP Alumni

Please post config  along with "show vlan"  , show ip int brief and show int trunk .

Leo Laohoo
Hall of Fame
Hall of Fame
Traffic flows properly across Vlan 4, but Vlan 7 shows it is in a down state and cannot be pinged from the local switch.

What appliance is doing your inter-VLAN routing?

Glen -  I've attached zipped txt files with the requested information. Thanks for your help.

Leo -  It's a 3750 switch.

From what I'm seeing, the vlan doesn't exist on the switch at all which would cause the down/down state. If you're not running vtp, manually create vlan 7 and it should come up.

HTH,

John

HTH, John *** Please rate all useful posts ***

I've seen creating Vlans two ways, through vlan database and through interface vlan. It was my understanding that vlan database was being phased out and that interface vlan should be the method used. In the running config, Vlan 7 does exist, though in the show vlan, it doesn't. I believe that's because it isn't active. Which is what I'm trying to correct.

At another site, this exact configuration works as needed, but if I remove the AP form the network (and thus any vlan 7 connections), Vlan 7 goes down in sh ip int brief, and does not appear in a show vlan.

Interface vlan attaches a L3 svi to an already existing L2 vlan. Vlan database is being deprecated and you can create the L2 vlan with "vlan 7 " in global config. You will still need a L2 vlan configured for your L3 svi.

HTH,

John

HTH, John *** Please rate all useful posts ***

  Simply put ,  conf t , vlan 7 , exit ...

You have your layer 2 vlan which is created as shown above.  And you have your layer 3 definition (SVI) which allows you to route packets off that vlan. You were missing the layer 2 definition so the L3  SVI could never come up .   Also as an fyi if you are not running vtp client/server then change your vtp mode to tranparent and all your layer 2 definitions will also show up in your running config instead of just with a show vlan command.

Yep, I can see the Vlan now showing as active. I'll test later today when I have the free time and supply the correct answer when it works out.

Thanks!

Edit - That did the trick! Tested and traffic is flowing as needed. Thanks for the help and quick replies!

123456789ali
Level 1
Level 1

probably if you have configured a vpc so it need to be created in all switches in vpc domain and it will comes up 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: