How to set the management VLAN / Interface for a 2940

hgru · ‎03-12-2004

Hi,

We have some 2940 switches taht we occasionally use for temp shortage of wall outlets.

Now we use Vlan 2 as management Vlan however sometimes i have trouble to get to to work.

Here is what i do

- I shut down interface VLAN1

- I create interface vlan2

- I set an ip address of VLAN2-subnet on vlan2 interface with teh correct subnetmask

- I do a no shutdown on the VLAN2 interface

- I configure the default gateway of vlan2

- I set vtp to server

- I create vlan2

All users on the ports via VLAN1 can use the connection without problems

Any ideas?

Hans

pmpesha · ‎03-12-2004

By default, I thought vlan1 is the management vlan. Use vlan1(management), and create additional vlans for your needs.

hgru · ‎03-17-2004

Yep vlan1 is the default for management but also for all ports so some companies start out with everything in vlan 1. Then later on they want to chnage that. Staring a new management vlan is than easier than moving all users and servers.

If I want to change it I have to to to four lacation and adjust 200 devices.

Not really an option.

pmpesha · ‎03-17-2004

I see your point!

milan.kulik · ‎03-12-2004

Hans,

if you are able to connect to the 2940 console, do following steps:

1) set VTP to transparent (it's safer, with server you could change VLAN databases in the rest of your network, 2940 support only 4 VLANs and are switched to transparent mode automatically when received a VTP adertisement containing more than 4 VLANs)

2) create VLAN2

3) configure IP address and mask on int VLAN2

4) shutdown on int VLAN1

5) no shutdown on the VLAN2 interface (some platforms support also "management " command)

6) configure the default gateway of vlan2

If not able to connect locally to console, do just steps 1) - 2).

Prepare a startup config file off-line, load it to 2940 flash via tftp and reload the machine.

Regards,

Milan

hgru · ‎03-17-2004

Hi,

Done that and it didn't work.

Did you use that methode on a 2940?

Hans

ziutek · ‎03-17-2004

Try removing the IP address from int VLAN 1 first, that is of course if you are connected via console.

Joe

milan.kulik · ‎03-18-2004

Yes, I used that on 2940.

What exactly didn't work?

Were you able to ping to the switch mgmt IP address locally (i.e. put an int to VLAN 2, connect a PC addressed in VLAN2 IP range to it and ping to the switch IP address)?

Regards,

Milan

Report Inappropriate Content · ‎03-19-2004

My solution is based on the assumption that VLAN 2 (management VLAN) is configured on all switching devices. Also, that a VTP domain exists and that it dynamically supplies VLAN information to all of your layer 2 switches. On your VTP server, create a user VLAN (such as VLAN 123,etc.). On that user VLAN, configure it with the user IP address range being utilized on your network. If you configure each port on the 2940 with "switchport access VLAN 123 (user VLAN)" commands, then you can shut VLAN 1. VLAN 2 is configured with the IP address of the management VLAN and should be configured with "no shut". The port connecting 2940 to the VTP server should be a trunked port so that both user and management traffic can pass to the 2940. The default gateway should point to the management VLAN interface on the router.

Hope this helps.