WISM and AP homing

Hi
We have just deployed approx 290 AP's and we have three WISM's (A,B,C) with 150 primary to A (secondary is B), 150 primary to B (secondary is A).
Ignoring the fact that there are two controllers per WISM, when we shut WISM A down we get approx 250+ on B and the rest on WISM C.
This number varies but we never manage to get all 290 AP's on WISM B. Its as if WISM B is so busy that numerous AP's give up and try something else.
The interesting thing is we have NOT coded WISM C into any AP configs.
So my questions are:
1. Why haven't all 300 AP's managed to register with WISM B (as coded).
2. If WISM C has been learnt by some other means is this expected behaviour to register to any WISM even if its not in your primary/secondary/tertiary settings.
This is not how I understood it should work from Cisco. I do not want these particular AP's to register to WISM C. On the flipside, I could understand the rationale of wanting an AP to register to any controller if possible rather than be isolated.
Has any one had similar experiences ?
Are there any plans to prioritise which AP's can register to a controller i.e. If I had 310 AP's but only the backup capacity for 300 it would be nice to have a feature to predict which of the 300 register rather than the unpredicatable method of present.
regards
Paul

I have deployed aprox 350 aps, since they are divided up among three different campuses, we never had one with more that 120 aps, recently we added 50 more aps, but one of the controller maxed out at 150, the other controller has failed to respond to the aps even though dhcp option 43 has its ip address configured.
how were you able to have the aps load balance or fail over to the secondary controller.

Similar Messages

After adding 2nd WiSM and failing over AP's some apps don't work

We have a dual core made up of 2 6513's. In 6513#1 we have WiSM#1 which we have had for sometime now. We have added a 2nd WiSM in 6513#2 for redundancy purposes also we are going to be re-configuring the WiSM in 6513#1 to more match that of the new WiSM in 6513#2. We have installed the new WiSM and failed over the AP's from 6513#1 so we can re-configure it's WiSM. The failover went great and no issues, with the exception that a web application or two didn't function from wireless clients and users were having issues getting to some mapped drives. The only difference from the new WiSM config vs the old WiSM is that on the old WiSM the AP's were in the same VLAN as the controller management interfaces. Now with the new WiSM it's configuration has the controllers AP mgt interfaces ip addresses in a different VLAN from the AP's, we are doing this based on Cisco best practices. If we revert the AP's back to the original WiSM/controllers the PC's where they are on the same vlan/subnet the applications and shares that were having issues the other way work. We have placed a call with Cisco TAC and they say our configs look good and we even sent them some packet captures and they said everything looks normal. The wireless clients can ping and resolve the server hosting the application database just fine.
Thanks

We did create the mobility groups, and we are using DHCP opt 43. The AP's find the 2nd WiSM#2 just fine and associate to the controllers and all the WLAN's work just fine. The only issue is that after the AP's are on the new WiSM and controllers there is an application or 2 that is having trouble locating it's database server and that some share's are not working. Again the only difference in this new setup in that now the AP's are on a different subnet/vlan from the controller mgt addresses where as before they were in the same subnet/vlan and the application and shares worked fine. It's almost like it is a bit of a routing issue?
Thanks

Adding a secure WLAN - WISM and WCS

I have a setup including a WISM and WCS which currently only runs a guest service using webauth to get online. The service (by request) is not secured over the air. I would like to implement a second SSID with security but before going the whole way with 802.1x I wanted to implement a half way house. Service will still only be a guest service but I want the air traffic secured.
So I guess my options are WEP (forget it) or WPA/WPA2.
My question is do I have to run this service with a shared secret that I then need to inform all users of in order for them to be able to connect to the service or is there a way to implement a WPA service that uses some kind of credential check against the already configured RADIUS (ACS) servers?
And if this is possible I assume there is no longer need for a webauth as this just seems to duplicate the login process.
Thanks for any pointers in advance
Paul

The best thing you can do is start with the Configuration Guides. If you don't have a test environment and have SMARTNET on the WiSMs/ WCS, utilize TAC to help you get up and going. I would also suggest utilizing a Cisco Partner to help with the initial implementation as well.
I would recommend upgrading your WiSMs and WCS to the latest versions and making sure configurations are the same across modules. I upgraded our WiSMs from 4.x to 7.0.98.0 and WCS to 7.x. Ran into a bug here and there but that is expected. Just make sure the wireless devices support those versions. If you are unsure, you can always work towards the AssureWave tested code. WCS 7.x should be backwards compatible (check the release notes just to verify). The Design Zone and Release Notes are your friend too.
-Rick

Configuration details of WS-C6504-E-WISM and WS-C6509-E-WISM bundle

Hi,
I can't find anywhere the list of product include in the 6500 wireless bundle WS-C6504-E-WISM and WS-C6509-E-WISM. Does someone now ?
Thanks in advance.

Hi Gael,
I'm not sure if this is what you are looking for;
Cisco Catalyst 6500 Series Wireless Services Module
From this doc;
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_qanda_item0900aecd8036434e.shtml
Configuring a Cisco Wireless Services Module and Wireless Control System
From this doc;
http://www.cisco.com/en/US/products/ps6305/prod_technical_reference09186a00806053bf.html
Catalyst 6500 Series Switch Wireless Services Module Installation and Configuration Note
From this doc;
http://www.cisco.com/en/US/products/hw/modules/ps2797/prod_installation_guide09186a0080514536.html
Hope this helps!
Rob
Please remember to rate helpful posts.........

802.11 n support in Wism and WCS

Is the new wless standard 802.11n is supported in current shipments of Cisco WLC 44XX and WiSM ( 6500 wireless controller card) ?
Also I need to know whether is is supported in WCS 4.1 ?

Hi Nalaka,
Yes, 802.11n is supported on the WISM and WCS starting with the following releases in the 4.2 train;
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn4200.html#wp302677
The following new features are available in WCS 4.2.62.0
802.11n support-The introduction of the Cisco Aironet 1250 series access point, a business-class access point based on the IEEE 802.11n draft 2.0 standard. The access point offers combined data rates of up to 600 Mbps to meet bandwidth requirements. Cisco WCS display screens include a listing for configuring, managing, and monitoring 802.11n access points and their associated wireless LAN controllers.
The newest WLC and WCS 5.0 trains are now released as well :)
Hope this helps!
Rob

WiSM and GUEST web authentication

I have a WiSM and we use Cisco open web
authentication with a user email address.
When performing this command via CLI:
>config network secureweb disable
>save config
> reset system
Will this make the web authentication come up HTTP instead of HTTPS ?

That command is in order that you manage the unit.
However there used to be a workaround that when you disable HTTPS and SSH and you reboot the WLC the web authentication will be showed as http and no https.
Let me know if it works for you

Wism and RF Group Problem

We have on Wism version 4.0.155.5. We configured one RF group name for two controllers in the wism and use auto-RF. The problem is each controller can only see itself in the RF group and consider itself as the RF group leader. My understanding is each one should see two controllers in the RF group and only one should be the RF group leader. Where could be wrong?

I posted the following in your other thread:
Do you have APs on both WiSMs yet? They will only see other RF group members that have APs associated to them. I had the same issue, but when I moved 1 AP to each WiSM the RF group came up as expected.

WISM and RF Group

We have on Wism version 4.0.155.5. We configured one RF group name for two controllers in the wism and use auto-RF. The problem is each controller can only see itself in the RF group and consider itself as the RF group leader. My understanding is each one should see two controllers in the RF group and only one should be the RF group leader. Where could be wrong?

I may be wrong on this, but I believe the RF groups are actually determined based on what the radios can hear. So an RF group is created for each group of isolated cells (i.e. group of AP's that hear each other within a coverage area).

WiSM and 4404 problem

Have a Wism configured to be the primary controller however all LAP's seem to register to a seperate 4404 on the newtork. HAve rtied many things to rectify but to no sucess. Any ideas anyone
cheers

A couple of things, one build the mobility group between the two devices, and once they join, set the Primary and Secondary Controller addresses on the AP's individually, or through a template in WCS if you have it.
If you are providing the management address via Option 43/DNS, the AP learns about all the controllers in the mobility group, so if you already have the mobility group built, the AP is learning about the WiSM and the 4404. It then will unicast each controller with discovery request, and the AP will decide on which controller to join.
Generally if I want all my AP's to join a specific controller I will set that one as Master Controller Mode to on, and when they have joined set the Primary and Secondary. If you do not set these variables, then the next time you set a different controller to Master Controller Mode, your AP's could move to that controller.

IronPort ESA - HA and Dual Homing

Hello, i have a customer that want to do HA and Dual Homing implementation. I want to ask what is the best way to implement HA for IronPort ESA? As i know the cluster configuration only used so the policy can be distributed equally. And what about dual-homing scenario? Is it supported with IronPort, and how do it works ?
Regards
Alkuin Melvin

What exactly do you mean by multi-homing? Ironport email appliances support configuration of multiple interfaces (physical or vlan) , to which you can then attach Listeners (SMTP processes). You could thus configure your servers to receive or send email on multiple IP addresses, depending on your network config.
Sent from Cisco Technical Support iPad App

How to create guest access in wireless by WISM and WCS and ACS?

dear sir
i neeed to know the steps of how we can make guest access to our network like hotels by using our WISM v 7.0.220 and wireless control system and ACS ?

You need to define your requirements a little bit. The WLC can do WebAuth and an employee can access either the WLC or WCS to put in the username and password credentials, but you would need to figure out what's best for you.
Here is a support doc that you can reference.
https://supportforums.cisco.com/docs/DOC-13954
Sent from Cisco Technical Support iPhone App

Wireless WISM and 4402 DMZ controller mobility issue

Hi all,
I have a really weird wireless mobility issue I need help with. I have a Wism installed in our cat 6 with version 7.0.98.0 of software. I also have a 4402 controller in the DMZ acting as an anchor controller to terminate guest traffic, also running the same version of software. The mobility anchor is setup on 4 SSID's and most of the time I don't have an issue with it.
However every week or so the data path or control path will randomly go down, so no guest traffic. Timers are configured as 10 seconds for the keep alive count and 20 seconds for the keep alive interval. I have found the following syslog information from our NMS. Not sure what these errors are and if its anything to do with this random mobility issue.
Any thoughts ??

A traceback is a device producing a trace of where it was in the software code when the problem occured.
Most often it's when a function fails/crashes. Although that is not always true.
If you have the syslog to the deepest level of debug, you will see harmless tracebacks (functions that returned no result but that might be expected). On higher level of debugs only "crashing" tracebacks are shown. In this case, the fact that you have mobility issues and tracebacks related to mobility is highly suspicious.
TAC can decrypt the traceback hex and find the exact part of code that created the problem. From there, they can link it to an existing bug (or a new one maybe ?).
Hope this clarifies !
Nicolas
===
Please rate answers that you find useful

WISM and NAC OOB/ Client in a different WLC problem

Guys,
I am using two WiSM modules in 6513 Chassi.
We have 3 SSID configured but on each WLC are using APGroups making a Layer 3 roaming.
Well, Everything is work out fine and we have hundreds of the connections per day but each day appear two or three clients that still on Quarantine mode and the WLC does not change Auth_vlan to Access_Vlan.
NAC appear that client as ONLINE on WLC 3 but that client isn't there, he is on WLC 2 in Quarantine mode.
anyone know can help me?
thanks a lot

I think the jndi service can be accessed froma remote m/c, you can initialize the context with the appropriate paramters, so the lookups on the topic and connection factories and continue with your work.

Wism and aaa server communication

Hi
How a wism talking to aaa server .? The wism will talk on behalf of the user ?
What i mean if there is an acl on the interface vlan ( switch) , Do we need to allow the aaa server in the access list ?
Thanks

Yes you should AAA server on the ACL. Client data reaches in a CAPWAP tunnel between AP and WLC from where it is sent to wired network, so communication is done by WLC on behalf of client.
Usually, high level topology is like this :
-Thanks
Vinod
**Encourage Contributors. RATE Them.**

Config Guide for WiSM And AP 1130

Hi!!
Im looking for Sample config or Config guide for Implimenting WiSM on Catalyst 6500 and 20 AP's 1130 accross mulitple buildings.

Hi Ivan,
Here is some info for the WISM,
Cisco Catalyst 6500 Series Wireless Services Module (WiSM) Introduction
http://www.cisco.com/en/US/products/ps6526/index.html
Configuring a Cisco Wireless Services Module
From this excellent doc;
http://www.cisco.com/en/US/products/hw/modules/ps2706/prod_technical_reference09186a0080702fe2.html
WiSM Troubleshooting FAQ
http://www.cisco.com/en/US/products/hw/switches/ps708/products_qanda_item09186a00806e39b7.shtml
Cisco Catalyst 6500 Series Wireless Services Module Q & A
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_qanda_item0900aecd8036434e.shtml
Hope this helps!
Rob

WISM and AP homing

Similar Messages

Maybe you are looking for