cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
17211
Views
5
Helpful
3
Replies

Vlan Interface state constantly disabled

andrewdmorton
Level 1
Level 1

Hi.

 

I have a SF500 in layer 3 mode. I have 5 vlans (10,100,200,201,202)

Of these 5 vlans, each one has a vlan interface configured.

However, vlan 10 and 202 don't have an IPv4 route (which is created automatically I believe).

 

I had a look and the vlan interface state is set to 'Disabled' (yes I'm using the GUI...)

Whenever I click 'Edit', it brings up the new window, but it has a tick in the Enabled box. Unchecking and applying and then checking and applying makes no difference.  I just can't seem to change the state of the vlan interface.

 

Am I missing something weird?

 

Cheers.

 

Andy

1 Accepted Solution

Accepted Solutions

Mehdi Boukraa
Cisco Employee
Cisco Employee

Hi Andrew,

After when you create the SVI (Vlan interface) for each vlan for Layer 3, the Vlan remain down until you assign at least one port to Vlan and it should be UP (Connect a physical device in to Port assigned to a vlan)

Please let us know after your test and if the problem persist share with us config file

Please rate this post or marked as answer to help other Cisco Customers

 

Greetings

Mehdi

 

View solution in original post

3 Replies 3

phibertron
Level 1
Level 1

It probably the same as on the SG300, in that the vlan has to be assigned to an interface

 

Mehdi Boukraa
Cisco Employee
Cisco Employee

Hi Andrew,

After when you create the SVI (Vlan interface) for each vlan for Layer 3, the Vlan remain down until you assign at least one port to Vlan and it should be UP (Connect a physical device in to Port assigned to a vlan)

Please let us know after your test and if the problem persist share with us config file

Please rate this post or marked as answer to help other Cisco Customers

 

Greetings

Mehdi

 

Hi.

 

Thanks forumers!! 

Turns out that even thought it was assigned to an interface, the static route never appeared until the end device was connected (even if you tried to access that vlan from a different vlan).

For example, the internal interface vlan 1 (192.168.1.254) would never have a route added until a device appeared on a vlan1 port - even if a device on a vlan2 port had access to vlan1,  it didn't recognise it as being valid.

 

Many thanks for your help!

 

Andrew