Switch not remote manageable after adding VLAN

Unanswered Question
Jan 28th, 2008
User Badges:


I have a cisco 2960.

I've added a VLAN with a different subnet after I gave the switch it's initial IP.

Now, I can't remote manage the switch from any client on the new VLAN/subnet.

Do I have to add a route or something to the old VLAN/initial switch IP?

Thanks in advance

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Jon Marshall Mon, 01/28/2008 - 16:39
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN


Do you have the default-gateway set on your 2960 ?.

So the client will have a default-gateway of the L3 interface for the new vlan. To communicate with the switch IP the switch needs to be able to route packets back to the client so the switch needs it's default-gateway as well eg.

switch is in vlan 1

vlan 1 =

switch IP =

L3 interface for vlan 1 =

so default-gateway on switch needs to be


dongdongliu Mon, 01/28/2008 - 18:08
User Badges:


If you want to use a new Vlan as a mgmt Vlan, you need turn off Vlan 1 first.

Make sure the SW is working on VTP SERVER mode .

last, set up a default route .

Fraser Reid Tue, 02/05/2008 - 06:08
User Badges:


a 2960 is a L2 switch.

That means that there can only ever be 1 IP address configured at any 1 time after a "interface vlan x" command. the other vlans do not need IP addresses on a L2 switch to work. ie just

vlan x

name test-vlan

and that should activate the vlan on that switch if it is in VTP transparent or Server mode.

otherwise if in VTP Client mode just so

show vlan

to see if it has already that VLAN configured in the VLAN database.

The switch will only then be manageable from the VLAN with the IP address.




This Discussion