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

Unanswered Question
May 9th, 2008
User Badges:

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Scott Fella Sun, 05/11/2008 - 17:42
User Badges:
  • Super Silver, 17500 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 Wireless

Post the show run-config.


Did you create the mobility group so that the ap's would know of the new WLC's. If not, you can't just drop the WiSM#1 and hope that the AP's will connect to WiSM#2. You can use DNS or DHCP option if you want the AP's to find the new WLC's. Also verify that the configuration on the second core is good and that the show wism status shows the WLC's up.

mbroberson1 Mon, 05/12/2008 - 02:57
User Badges:

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

Scott Fella Mon, 05/12/2008 - 03:55
User Badges:
  • Super Silver, 17500 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 Wireless

Sounds like its a routing issue. It almost seems that it is an issues with your core 2 switch. The ap's being on a different subnet shouldn't make a difference. Double check the configuration again.

mbroberson1 Mon, 05/12/2008 - 06:16
User Badges:

It just doesn't make much sence since I can ping the server that has the database from a wireless client just fine? Really weird senario. I'll double check the config on our core switch #2.

Scott Fella Mon, 05/12/2008 - 06:40
User Badges:
  • Super Silver, 17500 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 Wireless

Verify your port channel and also make sure you are load balancing using src-dst-ip. Make sure your service port ip's are not routable past your core. I have seen issues even when you can ping one service port from one core to the other core. You can use a different vlan and then prune that vlan off on both core switches. Also make sure your service port isn't 0.0.0.0.

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