WiSM Service Vlan Issues

Unanswered Question
Oct 14th, 2009

Folks,

I have seen strange problem in WiSM, while configuring as service vlan, I could see the status of one of the service vlan's as Oper-Up. Second one is mentioned as -- , whereas I could access both wism by means of html. Through CLI i could access only one WisM.

Apart from that, I could see in log files lost hearbeat with supervisor. Is this log related with the missing service vlan's . How can I solve this issue? Will it be due to WiSM/Core Switch IOS incompatibility?

Regards,

SIDdarth

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ciscokid7181 Tue, 10/20/2009 - 08:06

Folks,

1. Could you please advise regarding strange issue which happens on my wism

When I type show wism module, I see one of the controller is mentioned with service vlan ip and controller ip and status as 'Oper-Up' , whereas second wism controller does show any ip and is mentioned as -- with status mentioned as 'Service-Up'. But remotely i can access both controllers through WiSM.

Why does it come so? I am having controller firmware version 5.0. How can I solve this issue.

2. Secondly as I have heard from other users that 5.0 is buggy firmware, will I lose my configuration if i upgrade firmware to 5.2/6.0

Please provide me ur experiences.

Thanks a lot

-SIDdarth

dmuralis Fri, 10/30/2009 - 17:20

Siddarth,

If the code you are mentioning is 5.0.148 , then there are two well known bugs about the service-vlan on the wisms. You will be able to access via GUI, but you cannot session into it.

Yes, 5.0.148 has several issues. Upgrading to 5.2 will ix the service port issue.

If the issue is indeed one of the bugs, then rebooting the controller will temporarily bring the service port up

The part of your config that will change if you are currently using apgroups and /or wlan override feature.It's configured a little differently on 5.2 and higher.

Thanks,

Dhivya

Actions

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