Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

can not access to WiSM

Hi,

I have one WiSM and the OS version is 3.2.150.6. Everything is fine before upgrade to 4.0.219.0.

 

After upgrade to 4.0.219.0, I ping to service IP is ok, but can not ping management IP. I try to clear config and reload then reconfig it, but I still not able to ping management IP.

 

The WiSM have 2 controllers, I fall back one of the controller to 3.2.150.6, it work fine again. For another one controller, primary image is 4.0.219.0, for secondary image, I tried to use bootloader menu to update image manually, but it failed and cause the secondary image empty.

 

Please help to mention me how to resolve my two problem :

1. why upgrade from 3.2.150.6 to 4.0.219 cause not access to WiSM?

2. how to recover the secondary image?

 

Best Regards

 

Jackson Ku

10 REPLIES
Cisco Employee

what version of code is the

what version of code is the host 6500 running?

 

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn402190.html#wp54499

 

The Cisco WiSM requires software release SWISMK9-32 or later. The Supervisor 720 12.2(18)SXF2 supports the Cisco WiSM software release 3.2.78.4 or above, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release 4.0.155.5 (with Cisco IOS Software Modularity).

New Member

Hi, The IOS version of

Hi, The IOS version of Catalyst 6509 is 12.2(33)SXJ6...

Cisco Employee

Hi, that 6500 code should be

Hi, that 6500 code should be fine.

 

What is your intended target version of code?  4.0 code is ancient.

 

Are you attempting to ultimately migrate your wisms to 7.0 code?

New Member

Hi,1. 3.x upgrade to 7.x

Hi,

1. 3.x upgrade to 7.x directly is not support.

2. I cannot access to the management IP of the controller that already upgrade to 4.0.219, and the secondary image was empty.

 

Where can I download the image file that I can use it at bootloader menu to update image?

 

Best Regards,

Cisco Employee

Hi, i'll test this in the lab

Hi,

 

i'll test this in the lab.  is suspect that this is an old bug.

 

potentially using an image different than 4.0.219 would help work around it.

 

i'll let you know what i find out

Cisco Employee

i couldn't find 3.2.150.6.3.2

i couldn't find 3.2.150.6.

3.2.215.0 is the only 3.2 version available for download

 

i upgraded from 3.2.215.0 to 4.0.219.0, and it's still able to ping it's default gateway

 

try loading 3.2.215.0 first, then upgrade to 4.0.219.0

 

 

(WiSM-slot3-1) >ping 192.168.5.1

Send count=3, Receive count=3 from 192.168.5.1

(WiSM-slot3-1) >show boot
Primary Boot Image............................... Code 4.0.219.0 (active)
Backup Boot Image................................ Code 3.2.215.0

(WiSM-slot3-1) >show interface detailed management

Interface Name................................... management
MAC Address...................................... 00:1d:45:ef:a1:a0
IP Address....................................... 192.168.5.24
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.5.1

 

 

New Member

Hi,I will try to upgrade from

Hi,

I will try to upgrade from 3.2.215.0 to 4.0.219.0 again for one of the WiSM controller.

But another WiSM controller have primary boot image ( 4.0.219.0 ) only, secondary boot image was empty, and I cannot ping and access management IP of this WiSM controller. How can I recover this issue?

I also tried to remove CF card ( boot image is 7.0.220.0 ) at another WiSM and install to the WiSM with ping issue, it can bootup but I still not ping and access management IP of this WiSM controller? Is it the WiSM hardware issue or I still need to follow the correct procedure to upgrade the WiSM?

Best Regards,

Hall of Fame Super Gold

After upgrade to 4.0.219.0, I

After upgrade to 4.0.219.0, I ping to service IP is ok, but can not ping management IP.

Check your switch logs.  


There is an existing bug with WiSM-1 where the allowed-VLANs get "locked" out after a reboot or a power on.  

 

You may need to remove the "native vlan" and put it back in.  Like the following: 

 

config t

no wism module  <number> controller <number> native-vlan <number>

!  Wait for 5 seconds

wism module  <number> controller <number> native-vlan <number>

end

 

New Member

Hi,I tried to remove "native

Hi,

I tried to remove "native-vlan" and "allowed-vlan" config and re-add it, it still not work.

Is there RTOS file for WiSM? We lost both primary and secondary boot image for one of WiSM controller...

Best Regards,

 

Hall of Fame Super Gold

We lost both primary and

We lost both primary and secondary boot image for one of WiSM controller...

If you've lost the image and the WiSM is in "grub" mode, then contact Cisco TAC and they'll give you the step-by-step process on how to recover the WiSM card.

436
Views
0
Helpful
10
Replies
CreatePlease to create content