WiSM in Catalyst 6509 need assistance resetting to factory from Sup if possible?

Unanswered Question
Mar 8th, 2012
User Badges:

Good morning all,

I have been having some issues trying to stand up an older WiSM that has been incorrectly configured by my predecesssor and has a bad Mgt IP so I am unable to telnet or SSH into it, nor can I console or session into it.

What I would like to do is to change the Mgt address for the WiSM controllers (1 and 2) by way of the Sup (not sure that is possible) because as it stands they are set to and are unreachable even when directly consoled into them.

Core-A#sh wism status

Service Vlan : 52, Service IP Subnet :


Slot  Controller  Service IP       Management IP    SW Version  Status


3           1    Oper-Up

3           2    Oper-Up

Core-B#sh wism status

Service Vlan : 52, Service IP Subnet :


Slot  Controller  Service IP       Management IP    SW Version  Status


3          1    Oper-Up

3          2    Oper-Up

If anyone has any advice, tips or tricks I would be grateful for the information. I hope to get this WiSM setup on Core A and get it configured like I have my Core B and then run them in a dual failover design with load balancing between the two. So all ideas are welcome.

Thanks in advance for the assistance, if more information is needed please ask for it and I will provide what I can.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Stephen Rodriguez Thu, 03/08/2012 - 09:30
User Badges:
  • Purple, 4500 points or more

The service port VLAN should be contained to the chassis that WiSM is in, and not be passing between both Sups, the way it is.

you could try to change the service-port VLAN on Chassis A, and configure a new DHCP scope there.  You may need to trigger a reset of the module from the Sup, to get it to grab a new IP on the service port.  After it comes up, you should be able to get access.


Lewis Applequist Thu, 03/08/2012 - 10:09
User Badges:

I will give that a shot and will let you know how it goes.

Thanks for the info Steve.


Lewis Applequist Tue, 03/13/2012 - 10:12
User Badges:

Even with a new DHCP scope I cannot session or telnet into the service port to config the WiSM, simply times out. Very frustrating, so I'm open to any other ideas.

Thanks again Steve.


Stephen Rodriguez Tue, 03/13/2012 - 10:18
User Badges:
  • Purple, 4500 points or more

cn you share the config of the switch of the WiSM you can't access?


Leo Laohoo Tue, 03/13/2012 - 14:35
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

You may need to erase the config and start all over again. 

Amjad Abdullah Wed, 03/14/2012 - 01:08
User Badges:
  • Red, 2250 points or more


You mentioned that you are not able to console to the WiSM WLCs? Is this correct or I undrestood wronlgy?
Consoel should be available anyway regardless of your config on WLC so if you can't consle to it it is either your terminal software config are not matching needed config to console correctly to WLC OR that you have some kind of weird problem gonig on.

You can try console from different programs and different laptops. Make sure you apply the correct settings for the program you use. The correct settings can be found here: http://tiny.cc/x3h5aw

From console (if you get it to work) you can just configure management IP's.

If you have a backup you can consider reset the WLC config and configure it from scratch in case changing config from console did not work.

Good luck.


This Discussion

Related Content



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode