3524XL replaced old and 1200 Aironet live w/out DHCP 1

[brettums]

On Friday I replaced a 3524 switch (old one crapped out) New one was put in place over the weekend...... I have a config file I uploaded to the switch which has EXACT settings from old box to new box. This switch houses 4 cisco 1200 AP's The ports which the AP's are hooked up to are set for trunking and full duplex settings to allow clients to connect etc......
I don't understand what the heck is goin on here, but settings have been cross referenced w/ another switch (3548) which houses 8 AP's and all settings match. Note all AP's are using POE (not thatshould matter..... therefore the AP is functioning.

As for clients trying to connect the client box makes a connection to ANY three SSID's but is unable to grab an IP address.

I'f also rebooted DHCP server and cross referenced settings . Still nothing. I'm at a point where I'm lost.... It's obvious I'm missing one small step. Any assistance would be helpful.

thanks

 

[vipergg]

If you have multiple vlans on the 3524 then you probably did not recreate the vlan database on the 3500 . You can verifiy with the "show vlan" command and see if they are there . My guess is they are not . Go into vlan database mode and recreate the vlans you need on the box .

 

[brettums]

that did it!

thank you!!!!
-Brett

 

[vipergg]

Remember the vlan database is a separate file (vlan.dat) and this does not get recreated by just copying the running config back in .

 

[brettums]

lemmy ask you this this.... even for other switches on my network, I must make sure the VLAN database is loaded on them as well? Campus wide I'm using VLANs.... I never knew this. I thank you for the tip! How do you pory the vlan.dat just do the same via tftp? "copy vlan.dat tftp://server" ?

thanks agaon!

 

[vipergg]

To be honest we have same vulnerability . If you want to save it you would have save it to a tftp server with a name that would identify which switch it belongs to such switchname.dat and then change it back to vlan.dat when you loaded it onto a switch. This applies to IOS switches only you don't have this issue with catos which is why I have always like catos , just easier to use once you know the commands.