can not connect to WiSM controller 2

Unanswered Question
Mar 10th, 2008

we reset the WiSM controller 2 to defaults using the web interface. Now when we try to use "session slot 7 processor 2" we get connection refused.

Show wism status reveals that proc 2 has a 169.254.x.x address. dhcp is setup and the wism has been assigned the vlan so I'm a little lost as to whats wrong.

Any ideas?

Also is it possible to copy the config from processor 1 to processor 2. We would like to manually load balance our AP's.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
sabhasin Mon, 03/10/2008 - 20:23

for some reason, it appears that the service port couldn't grab a dhcp lease. perhaps you could try setting it to static and then back to dhcp and see if it grabs an ip address.

as far as copying configs across controllers, no, it's not possible today. However, you could use WCS (and templates) to push same parameters to multiple controllers.

CLIFFORD BECKER Thu, 03/13/2008 - 19:07


Thanks for the response.

I should have been more clear. Its not the Service IP.

I hope the following shows up correctly.


Slot Controller Service IP Management IP SW Version Status


7 1 Oper-Up

7 2 Oper-Up

#sess slot 7 processor 2

The default escape character is Ctrl-^, then x.

You can also type 'exit' at the remote prompt to end the session

Trying ...

% Connection refused by remote host

Any ideas?

Scott Fella Thu, 03/13/2008 - 19:38

I think you have to setup your other service IP Address before you can try to connect using the session slot... The Service Port is on a vlan you configured on the chassis... as you can see, one is on the 10.120.1.x and the other is getting a default like if it was set to dhcp. Change that and you will be good to go...

I Hope!

sabhasin Thu, 03/13/2008 - 23:31

right on, fella5. But looks like his service vlan (and therefore, the service port ip address is configured correctly). It appears to be the management interface that's got an incorrect address. Perhaps changing that will help but we'll have to see...

Scott Fella Fri, 03/14/2008 - 04:54

You are right... I looked at the address and looked at the words right above.

Console into WLC 2 and makes changes to your Management IP. Also make sure your Service Port IP Address isn't routable. This service port vlan should be local to the chassis.


This Discussion



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