Two WLC 5508 Anchor High Availability

Hello.
It's possible use 2 WLC 5508 en ANCHOR MODE in a Active-Active scenario?.
For example, if one WLC get down of service, the other one keep provide service to the anchor clients?.
In this moment we have just one WLC 5508 in Anchor Mode. What i need to configure a ANCHOR high Availability.
Thanks A lot!!!

This is confusing to me:
If we install a second Anchor WLC, what you recommend about the DHCP server in a failover event, because this second ANCHOR WLC will have the same configuration of the firts anchor wlc.
What do you mean the two will have the same configuration? The hostname and ip should be different.... or are you just stating that the WLAN and DHCP will be the same? I don't want to tell you something and break your environment, so just trying to clear things up.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Similar Messages

Upgrade two WLC 5508 with HA SSO from 7.5.102.0 to 7.6.130.0 combined with FUS 1.9

The running config is:
- Two WLC5508's in HA SSO setup running version 7.5.102.0
- about 130 x 2602i APs
I need to upgrade to 7.6.130.0 using the pre-download feature to minimize the network downtime.
Is it possible to transfer the 7.6 to the controllers and pre-download 7.6 to all APs, then do the FUS 1.9 upgrade and finally start the actual controller upgrade to 7.6.
So the steps would be:
1. Transfer 7.6 image to primary controller (do not reboot!), so still running 7.4 as active image.
2. Start pre-download of 7.6 image to all APs and wait till all APs have the new image (do not know how long it takes for 130 APs).
3. Upgrade both controllers with FUS 1.9 (HA should upgrade both controllers automatically) (takes about 45 minutes?)
4. Make 7.6 image the active/primary image on controllers and APs and reset controllers.
If the steps above will not work, I would need to upgrade FUS 1.9 which means 1 hour downtime and then start the pre-download to all APs. The pre-download can take a long time I heard, so I need to wait and wait before I can start the 7.6 upgrade, which means another 1 hour downtime.
This way I need two maintenance windows instead of one. So would it be possible to combine the pre-download and FUS?
Regards,
Bjorn

>Do I need to upgrade the FUS 1.9 before the 7.6 image or can I do the FUS afterwards? If I can do it afterwards, I can do the upgrades in the same maintenance window. This way I can start the pre-download the day before, so I am pretty sure the APs have the image at the time of the maintenance window.
>I cannot find any remarks about the required order of installation (FUS -> image or image -> FUS).
Release Notes for Wireless LAN Controller Field Upgrade Software for Release 1.9.0.0 - p2 :
* This release of the Field Upgrade Software is applicable to CISCO WLC's that are installed with the controller software release 6.0 and later.
So strict reading implies that you have to run 7.6 first.
M.

Two SAP Instances in High Availability cluster - SGeSAP - HPUX

Dear All
We want to install 2 SAP instances in single host with DB and CI separately. DB and CI will be on High Availabilty Cluster using SGeSAP for HP - Unix. The database is Oracle 10g.
Does SAP support multiple instance on the same hosts(DB and CI) for HA option.
Kindly inform
Regards
Lakshmi

Yes it is possible to run two SAP systems on same cluster using SGeSAP. Normally If there is only one system on the cluster DB is configured on one node and CI is configured on the second node, with fail over in case of a node failure. In your case if a node fails one node will be running two DB and two CI instances. You have to size the hardware accordingly. Just FYI, SGeSAP is licensed per SAP System.

High Availability with two 5508 WLAN controllers?

Dear all,
we are considerung to implement a new wireless solution based on Cisco WLC 5508 and 1262N Access Points. We are planning to purchase about 30 access points and have two options: Either purchase one WLC 5508-50 or, for redundacy, two 5508-25 controllers.
Is it possible to configure two WLC 5508 as a high availability solution so all Access Pointes are distributed over both WLCs and in the case one WLC breaks the other one manages all APs?
If we have 30 access points and one of two WLC 5508-25 breaks of course not all 30 but only 25 access points can be managed by the remaining one. Is there some sort of control to choose which access points shall be managed and which not?
How does such a configuration look like in general, is the implementation of a two controller setup rather complex or straight forward?
Thanks!
Michael

Dear Nicloas,
thanks for your reply. We have an offer where two 5508-25 are only a little more expensive than one 5508-50. So I think it's better so spend a little more money and have a backup WLC. Otherwise, if the one and only WLC breaks, all APs are unusable which would not be acceptable for us.
Regarding roaming - not all access points will distribute the same WLAN. Actually we will have one wireless network with 18 access points for our warehouse and 12 access points for the internal and guests network.Therefore no roaming will happen between those APs. In this case I could use one WLC for the 18 warehouse access points and 12 for the internal network. In the case one controller breaks, I could use the remaining one for the important warehouse systems (i.e. by using the priority system).
Regarding the configuration: If I understand correctly I configure both controllers exactly the same (except for the name and IP address of course) and put both controllers in the same mobility group - and that's really it? Sounds great!
I have one general question regarding the new WLC controllers: Is it true that communication between the WLC and the APs is now done on Layer 3 only so all APs need an IP address? I'm asking because currently we are still using an Cisco 4112 WLC which operates in Layer 2 mode. So I guess with the new WLC, I have to configure DHCP option 43 with the management IP address of the WLC, right? I also guess I can manually move APs from one to another WLC once they have joined a controller for the first time?
I'm ordering the book "Deploying and Troubleshooting Cisco Wireless LAN Controllers" now and guess this will answer most of my upcoming questions. Can I come back to you here in case I run into trouble with the configuration?
Thanks a lot for your help
Michael
Nachricht geändert durch michaelbs

Converged Access Design Help (Catalyst 3850 and WLC 5508...Mobility Oracle)

Hello,
I am an engineer working with a Cisco Gold Partner in Saudi Arabia. We have a large university as our client where they are constructing a new
building and require our services to build the network infrastructure. Therefore, we are to implement the routing and switching infrastructure as
well as the Wireless solution.
At present, I have no issues in implementing the R&S infrastructure as it is very straight forward but it has implications on the deployment of
the wireless solution which I explain further below. The R&S infrastructure comprises of the typical Core, Distribution, and Access layers and we
are focusing on the local distribution and access switches with regards to the new building. The client has a converged Layer 3 network spanning
from distribution layer to core layer and they are running EIGRP for this convergence. This is not a problem and has already been implemented.
Yet, the challenge arises in deploying the WLAN infrastructure. The client already has a Cisco WLAN infrastructure in place where they have a
large number of LAPs that are registered with their controllers in the Data Center. They have two WLC 5508 where one is the Primary and the other
the Secondary. The local distribution switch to which the WLC are connected also is the gateway for the SVIs for the SSIDs that are configured on
the controllers. This means that once the packets from the AP come in to the WLC, they are tagged with the correct VLAN and sent to the directly
connected distribution switch which then routes it into the rest of the Layer 3 network. Interestingly, the WLC 5508 are running AireOS 7.6 and
support the "New Mobility" feature. The two controllers have formed a Mobility Group (MG) between each other.
Now, the new building will have two Catalyst 3850 switches installed where each one has a total of 40 AP licenses pre-installed and activated
i.e. a total of 80 APs can be supported by the two switches. A total of 67 LAPs will be deployed in the new building which can be accommodated
between the two switches and their integrated controller.
Yet, based on my understanding and research about Converged Access is that, ideally, the Catalyst 3850 will only run the Mobility Agent (MA)
feature while a central controller would provide the Mobility Controller (MC) service. unfortunately, there are not enough licenses on the
existing WLC 5508 nor can we migrate the new licenses that will facilitate such a split deployment.
This means that I would need to configure the two Catalyst 3850 as independent MC and form a MG between them. I have done this and tested this
already and the mobility is working fine. But my concern is not about getting the Catalyst 3850 to work as this is simple but rather it is
focused on creating a common Mobility Domain (MD) so that clients can roam from this new building to the rest of the campus while maintaining the
state of their connections to the WLAN infrastructure.
To make things more complicated, since the new building will have its own Layer 3 distribution switch and the Catalyst 3850 switches will connect
to this distribution switch, it means that new VLANs and SVIs need to be created for the SSIDs broadcast in the new building. This means that new
subnets need to be assigned to the SSIDs.
As such, I have the following questions:
Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means
that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG
as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to
the solution as per the next question. Please advise which is a better option?
Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can
then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD).
Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
Please advise at your earliest. To assist further, I have attached a topology diagram which may aid in explaining the situation with more
clarity. If these things are clarified, I will be better able to wrap my head around the technology and in turn service my clients better.
Regards,
Amir

Hi Amir,
Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to the solution as per the next question. Please advise which is a better option?
I would configure them in the same mobility group. Also configure same SPG for those two 3850 stacks if users are frequently roaming within these two buildings.
Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD). Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
MO is not required (it is only for very large scale deployments)
Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
Yes, documents are hard to find :(
These notes may be useful to you based on my experience. I am running IOS-XE 3.6.1 in my production.
http://mrncciew.com/2014/05/06/configuring-new-mobility/
http://mrncciew.com/2013/12/14/3850ma-with-5760mc/
HTH
Rasika
*** Pls rate all useful responses ****

WLC 5508 running 7.4.110.0 unable to tftp upload config from controller

Hi,
Two WLC 5508 running identical code version. One is 50 license Primary, the second is HA. Identical config on both. HA WLC can upload its config to the TFTP or FTP server but Primary cannot. The operation fails for both CLI and GUI and for different protocols i.e. TFTP, FTP.
#### Primary Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7309
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.30.210
Last Reset....................................... Power on reset
System Up Time................................... 18 days 18 hrs 51 mins 35 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 8
Number of Active Clients......................... 138
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:52:20
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 50
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. TFTP
TFTP Server IP................................... 10.1.22.2
TFTP Path........................................ /
TFTP Filename.................................... PRODWC7309-tmp.cfg
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) Y
*TransferTask: Jun 02 10:41:15.183: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:41:15.183: RESULT_STRING: TFTP Config transfer starting.
TFTP Config transfer starting.
*TransferTask: Jun 02 10:41:15.183: RESULT_CODE:1
*TransferTask: Jun 02 10:41:24.309: Locking tftp semaphore, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore locked, now unlocking, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore successfully unlocked, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.394: tftp rc=-1, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
pLocalFilename=/mnt/application/xml/clis/clifile
*TransferTask: Jun 02 10:41:24.394: RESULT_STRING: % Error: Config file transfer failed - Unknown error - refer to log
*TransferTask: Jun 02 10:41:24.394: RESULT_CODE:12
*TransferTask: Jun 02 10:41:24.394: Memory overcommit policy restored from 1 to 0
% Error: Config file transfer failed - Unknown error - refer to log
(Cisco Controller) >show logging
*TransferTask: Jun 02 10:41:24.393: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:41:24.315: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=142 ulk=1621944 lk=1621802 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
*TransferTask: Jun 02 10:39:01.789: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:39:01.713: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=5598 ulk=1621801 lk=1616203 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
#### HA Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7310
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.31.210
Last Reset....................................... Software reset
System Up Time................................... 18 days 19 hrs 1 mins 27 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 4
Number of Active Clients......................... 0
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:53:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 500
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. FTP
FTP Server IP.................................... 10.1.22.2
FTP Server Port.................................. 21
FTP Path......................................... /
FTP Filename..................................... 10_1_31_210_140602_1050.cfg
FTP Username..................................... ftpuser
FTP Password..................................... *********
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) y
*TransferTask: Jun 02 10:51:31.278: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:51:31.278: RESULT_STRING: FTP Config transfer starting.
FTP Config transfer starting.
*TransferTask: Jun 02 10:51:31.278: RESULT_CODE:1
*TransferTask: Jun 02 10:52:05.468: ftp operation returns 0
*TransferTask: Jun 02 10:52:05.477: RESULT_STRING: File transfer operation completed successfully.
*TransferTask: Jun 02 10:52:05.477: RESULT_CODE:11
File transfer operation completed successfully.
Not upgrading to 7.4.121.0 because of bug CSCuo63103. Have not restarted the controller yet.
Any one else had this issue ? Is there a workaround ?
Thanks,
Rick.

Thanks Stephen, In my deployments of 7.4.110.0 version I have not seen this issue so may be controller reboot will fix it (we do have HA to minimize the impact). I will keep the thread updated with findings and may request TAC for the special release 7.4.121.0 if the still not happy with 7.4.110.0
Rick.

2 Cisco WLC 5508 controllers and software upgrade 7.6.130 + FUS 1.9

Hi
I have two WLC 5508 controllers that need 7.6.130 and FUS 1.9 installed. (Current version 7.3 and FUS 1.7)
Configuration: One controller is at Site A and the other controller is at Site B (two different states..)
They're configured so that if Site A goes down, Site A AP's will failover to Site B and vice versa ..
- What would be the recommended approach for upgrading the software to 7.6.130.0 (from 7.3) and also upgrading FUS 1.9 (from 1.7)?
My plan was to download 7.6.130.0 to both controllers and pre-download the software to all AP's (about 100 total between both sites) and then reboot the controllers at night at the same time? Or one before the other?
Step 2. Install FUS 1.9 to each controller.
I'm concerned over what might happen during the upgrade and AP failover etc..
Thanks

This is what I would do:
Upload v7.6.130.0 to all WLCs and then use the pre image download to push the image to all access points.
Dont reboot the wlc
Image swap in the access points so that v7.6.130.0 is primary
Move all access point to one of the WLCs (A)
Enable ap AAA authentication on the WLC that has no access points and the one you will work on first. This prevents access points from joining
Reboot the WLC (A)
Upload the FUS 1.9.0.0
Reboot WLC (A) this takes up to 45 minutes
When the WLC (A) comes back online, uncheck ap AAA authentication
Move access points from WLC (B) to WLC (A)
Enable ap AAA authentication on WLC (B)
Perform all the other task you did earlier on WLC (A)
That's it.
-Scott

WLC 5508 HA Problem Soft.ver 7.4.100

Dear Support,
we are using two WLC 5508 software ver.7.4.100 with first 50AP license and in the next day we add 50AP license again to the primary WLC. when we activate HA base in the following guiden http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html but when we doing test the failover we found a couple log message on the Secondary WLC like below and not for long time all AP on the Secondary WLC was drop off.
1. DP Critical Error
2. *RRM-DCLNT-2_4: May 23 07:43:53.204: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:34:db:fd:dd:3e:20,Key SlotId:0
*RRM-DCLNT-2_4: May 23 07:43:53.164: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:34:db:fd:dd:3e:20,Key SlotId:0
*RRM-DCLNT-2_4: May 23 07:43:52.854: #RRM-3-RRM_LOGMSG: rrmTables.c:682 RRM LOG: Could not retrieve RRM Coverage Measurement DataKey BSSID:2c:36:f8:72:fc:c0,Key SlotId:0
I also send a complete log for both problem above and enclose it with pdf file. need you advice and assistance,
regard, afriansyah

I agree go to version 7.4.121.0 I has some strange issues on prior releases. Personally I am running 7.6.120.0 right now but that's mainly due to support for the 3702 access points.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-74573
that's a good guide just to double check yourself just in case. -

WLC 5508 v6.0.202.0 reboot randomly.

Dear all,
I have two WLCs 5508 on version 6.0.202.0 and it reboot randomly in the last time, I have the following crash log information and I cannot interpret the information, so somebody has had experience with this crash
Beginning of Crash File: mwar_dump2.crash
Dumping registers
CPU Registers:
$ 0   : 00000000 8112be70 2ac30339 00004004
$ 4   : 0600ca00 00000000 00000004 2ac2c341
$ 8   : 00000000 7a3fefc1 00020000 7a3fefec
$12   : 00000000 50617369 81125650 00000000
$16   : 2ac2c33d 2ac30341 00000000 0000c00c
$20   : 00000040 00000004 7a3fefe8 12333c18
$24   : 81490000 114fad10
$28   : 12323c18 7a3fee80 00000007 108a9748
Hi    : 0000001f
Lo    : 33333362
Status: 00000000
Cause : 00000000
BadAddr : 00000000
Stack :
        0600ca00 00000000 00000000 00000000
        165f417c 00000000 00000000 80005002
        00000000 00000027 00000000 2ac2c321
        00000000 00000028 00000000 0000005e
        00000000 12323c18 00000000 165f417c
        00000000 00000000 00000000 00000001
        00000000 12323c18 00000000 7a3fefe8
        00000000 108ad670 00000000 108ad4cc
        00000000 00000001 00000000 12323c18
        7a3fefc0 7a3fefd0 7a3fefc1 7a3fefec
        00000000 1cd441fc 00000000 1a133d80
        00000000 165f4140 00000000 1a133d80
        00000000 165f4140 00000000 165f417c
        00000000 00000000 00000000 12323c18
        00000000 12323c18 00000000 0a31600a
        00000000 10273fe0 00000000 10274174
*             Start Cisco Crash Handler                *
Sys Name:           WLC
Model:              AIR-CT5508-K9
Version:            6.0.202.0
Timestamp:          Sat Aug 3 20:35:58 2013
SystemUpTime:           2 days 6 hrs 2 mins 37 secs
signal:             11
pid:                346
TID:                704556
Task Name:          spamApTask
Reason:           System Crash
si_signo:           11
si_errno:           0
si_code:            1
si_addr:            0xc
timer tcb:            0x221
timer cb:             0x1030e450 ('rrmTimerInit+352')
timer arg1:           0x1d07c728
timer arg2:           0x0
Long time taken timer call back inforamtion:
Time Stamp:           Thu Aug 1 23:01:39 2013
timer cb :           0x10296400 ('fmcSendNmspOneSecResponse+704')
Duration : 1000000 usecs, cbCount= 2
Analysis of Failure:
Software Failed on instruction at :
pc = 0x108a95c4 (acDecodeChangeStateEventRequest+1648), ra = 0x108a9748 (acDecodeChangeStateEventRequest+1648)
System Stack
    Frame 0: 0x10012fd8: create_crash_dump+7244
    Frame 1: 0x10011cc8: create_crash_dump+2364
    Frame 2: 0x1000768c: sigsegv_handler+5960
    Frame 3: 0x114b15c0: SHA1Final+1494592
    Frame 4: 0x7a3feb70: SHA1Final+1762370544
    Frame 5: 0x108a95c4: acDecodeChangeStateEventRequest+1260
    Frame 6: 0x108ad670: acDecodeDiscoveryRequest+672
    Frame 7: 0x10273fe0: acCapwapSmInit+31256
    Frame 8: 0x1026b3c4: acPostDecodeConfigRequest+4988
    Frame 9: 0x10276c7c: capwapAcStatemachine+3004
    Frame 10: 0x108a4d8c: spamApReceiveTask+692
    Frame 11: 0x10640b70: debug_heartbeat+392
    Frame 12: 0x114a9f10: SHA1Final+1464208
    Frame 13: 0x1150a494: SHA1Final+1858836
Semaphore and Mutex Usage
(Caller IP(instruction pointer of caller) Gives one more level
of depth in stack to track the Semaphore and Mutex operation)
   Mutex 'pgrp->groupingSem' @ 0x1d02b9d4 Created fp_main_task(rrmgroup.c:917)
      Locked by grouping Task(rrmgroup.c:978), Caller IP = 0x10640b70 (debug_heartbeat+392)
      1 tasks waiting for resource.
Stackdump from grouping Task
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x755fef80: SHA1Final+1680582656
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x102f1cf0: groupCalcEntry+160
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
          grouping Task, rrmgroup.c:978, Caller IP = 0x10640b70 (debug_heartbeat+392)
Stackdump from grouping Task
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x755fef80: SHA1Final+1680582656
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x102f1cf0: groupCalcEntry+160
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
   Mutex 'pgrp->groupingSem' @ 0x1d02be1c Created fp_main_task(rrmgroup.c:917)
      Locked by grouping Task(rrmgroup.c:978), Caller IP = 0x10640b70 (debug_heartbeat+392)
      1 tasks waiting for resource.
Stackdump from grouping Task
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x75ffef80: SHA1Final+1691068416
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x102f1cf0: groupCalcEntry+160
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
          grouping Task, rrmgroup.c:978, Caller IP = 0x10640b70 (debug_heartbeat+392)
Stackdump from grouping Task
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x75ffef80: SHA1Final+1691068416
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x102f1cf0: groupCalcEntry+160
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
   Mutex 'rcb->semId' @ 0x1cd3679c Created spamReceiveTask(spam_list.c:336)
      Locked by spamApTask(spam_api.c:500), Caller IP = 0x1026b0f4 (acPostDecodeConfigRequest+4268)
      2 tasks waiting for resource.
Stackdump from spamApTask
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x7a3fe330: SHA1Final+1762368432
    Frame 2: 0x114db504: SHA1Final+1666436
          dot11b, spam_api.c:500, Caller IP = 0x101aa3e0 (spamGetNextLrad+296)
          dot11a, spam_api.c:500, Caller IP = 0x101aa3e0 (spamGetNextLrad+296)
Stackdump from dot11b
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x763feb60: SHA1Final+1695261664
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab690: SHA1Final+1470224
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x101962bc: spamGetLCBFromMacTemp+396
    Frame 9: 0x101aa3e0: spamGetNextLrad+296
    Frame 10: 0x102e49a4: rrmClientBuildLradList+188
    Frame 11: 0x102e9c5c: rrmClientProcessPacket+556
    Frame 12: 0x102ddce8: rrmClientStateMachine+864
    Frame 13: 0x1030cec0: rrmClientTaskEntry+96
    Frame 14: 0x10640b70: debug_heartbeat+392
    Frame 15: 0x114a9f10: SHA1Final+1464208
    Frame 16: 0x1150a494: SHA1Final+1858836
Stackdump from dot11a
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x759feb60: SHA1Final+1684775904
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab690: SHA1Final+1470224
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x101962bc: spamGetLCBFromMacTemp+396
    Frame 9: 0x101aa3e0: spamGetNextLrad+296
    Frame 10: 0x102e49a4: rrmClientBuildLradList+188
    Frame 11: 0x102e9c5c: rrmClientProcessPacket+556
    Frame 12: 0x102ddce8: rrmClientStateMachine+864
    Frame 13: 0x1030cec0: rrmClientTaskEntry+96
    Frame 14: 0x10640b70: debug_heartbeat+392
    Frame 15: 0x114a9f10: SHA1Final+1464208
    Frame 16: 0x1150a494: SHA1Final+1858836
   Mutex 'sshpmTftpRuleSemaphorePtr' @ 0x1cc911b4 Created fp_main_task(sshpm.c:509)
      Locked by sshpmReceiveTask(sshpmrecv.c:1566), Caller IP = 0x10640b70 (debug_heartbeat+392)
      0 tasks waiting for resource.
Stackdump from sshpmReceiveTask
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x7b7ff4b0: SHA1Final+1783344432
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114a8aac: SHA1Final+1458988
    Frame 6: 0x1129f790: d_async_queue_pop+132
    Frame 7: 0x1062d888: osapiMessageReceive+472
    Frame 8: 0x103a209c: sshpmReceiveTaskEntry+932
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
   Mutex 'L7_transferSem' @ 0x1cb5d1bc Created TransferTask(updcode.c:3781)
      Locked by TransferTask(updcode.c:3787), Caller IP = 0x10640b70 (debug_heartbeat+392)
      1 tasks waiting for resource.
Stackdump from TransferTask
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x7e7ff380: SHA1Final+1833675776
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x10024430: L7_transfer_task+300
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
          TransferTask, updcode.c:3787, Caller IP = 0x10640b70 (debug_heartbeat+392)
Stackdump from TransferTask
    Frame 0: 0x10007af4: sighup_handler+116
    Frame 1: 0x114b15c0: SHA1Final+1494592
    Frame 2: 0x7e7ff380: SHA1Final+1833675776
    Frame 3: 0x114ad1bc: SHA1Final+1477180
    Frame 4: 0x114abd9c: SHA1Final+1472028
    Frame 5: 0x114afd28: SHA1Final+1488296
    Frame 6: 0x114ab744: SHA1Final+1470404
    Frame 7: 0x10634b20: osapiMutexTake+1008
    Frame 8: 0x10024430: L7_transfer_task+300
    Frame 9: 0x10640b70: debug_heartbeat+392
    Frame 10: 0x114a9f10: SHA1Final+1464208
    Frame 11: 0x1150a494: SHA1Final+1858836
   Memory Information
System Memory Information:
             Total System Memory: 929660928 bytes (886.65 Mb)
              Used System Memory: 341839872 bytes (326.02 Mb)
              Free System Memory: 587821056 bytes (560.63 Mb)
Heap information:
         Bytes alloced from RTOS: 8298496 bytes (7.91 Mb)
                     Chunks free: 15 bytes
       Number of mmapped regions: 40
Total space in mmapped regions: 114208768 bytes (108.92 Mb)
           Total allocated space: 8153400 bytes (7.77 Mb)
           Total non-inuse space: 145096 bytes (141.69 Kb)
      Top-most, releasable space: 55416 bytes (54.11 Kb)
     Total allocated (incl mmap): 122507264 bytes (116.84 Mb)
          Total used (incl mmap): 122362168 bytes (116.70 Mb)
          Total free (incl mmap): 145096 bytes (141.69 Kb)

I stand corrected. The code is still not deferred. I am still curios to find out why. The reason i am asking that is most likely you are hitting a bug which. The bug fix will be on different code and if you are upgrading then might as well upgrade to a more recent code train.
Sent from Cisco Technical Support iPhone App

WLC 5508 authorization issue

Hello,
I have an issue with two wlc 5508 in the same mobility group. We use TACACS to authenticate admins, with maximum privileges.
When I want to configure cleanair, or some security functions (such as ACL, or password policies), I have an error message saying that my privileges are not enough.
When I use local account, it works well.
At the begining, I thought it was a TACACS issue, but I have the same problem with WCS and SNMP. Cleanair doesn't appears in config menu, and I have an error message for security function.
Do you have any idea ?
Thanks for your help.
FW : 7.0.116.0

Show sysinfo results :
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

WLC 5508 - WGBs & HREAP on LAN

So, I really have two questions here. For some background information, I have a wireless network with two WLC 5508 controllers and 220 LWAPs in the same location as the controllers. All APs are currently in local mode. I run a few guest networks as well as some other client networks. One client in particular uses their network to connect mobile machines to their VLAN. The only issue is that the machines do not have wireless adapters. Instead, the manufacturer put inside the chassis, a D-Link WGB, which has an ethernet cable, you then have to plug into the ethernet port. These devices cannot seem to connect to the network. I have found, the WGBs do associate on the network, but the wired client behind it cannot pass traffic onto the VLAN. I have also tried connecting PCs with different SOHO style WGBs from different manufacturers with the same result.
After going through Cisco's documentation, I found that using 1230s in WGB mode can resolve this issue since they use IAPP to communicate the MAC table of the wired side clients they service back to the controller. I have configured a 1230, and used it as the WGB for the client machine instead of the D-Link and it does seem to work, but this would mean configuring a considerable number of 1230s to hand over to the client.
The first question would be, Is there something I am missing that I would need to do in order to allow SOHO style WGBs to forward wired side client traffic onto the network while LWAPs are in local mode? Or would the WGB NEED to support IAPP?
The second question is that, I may have found another solution to this already, but would like some input prior to committing.
This client also uses these same machines with the same WGBs inside the chassis at another location where the client operates the network themselves. They also use the same WLC model with the same version, and same APs. The only difference is that they use H-REAP mode with local switching.
I also tested this idea, and it seemed to work. With the AP in H-REAP mode, and the client's WLAN set to local switching, the machine and WGB connected with no problem.
So the question with this, would be; would there be any disadvantages in running all 220 APs at this location in H-REAP mode? What would I be losing if anything? Also, I would like to keep all other WLANs centrally switched.
I understand what the difference would be for this client's WLAN if I ran in H-REAP mode with local switching, but what would the difference be in the other guest WLANs if I set them to be centrally switched? (Is there any difference between running APs in local mode vs running APs in H-REAP with central switching?)

Hey,
I read your quesiton quickly so I might miss some points, but I think you need to do some more configuraiton for your passive clients behind the WGB:
'''snip'''
Passive Clients Behind a WGB
The controller might not be able to see passive clients behind a WGB. Clients (such as cameras and programmable logic devices) do not initiate a traffic stream unless they are connected. Complete these steps in order avoid this issue:
Add a static MAC filter entry for the passive WGB device and MAC filter entry for the devices that are behind it.
Use this command in order to enable MAC filtering on the WLAN along with aaa override:config macfilter ipaddress MAC_address IP_address
Add a static entry on the WGB IOS-based device: bridge 1 addressxxxx.xxxx.xxxx forward FastEthernet0Note: In addition, increase the dot11 activity timer.
Add a static ARP entry on the L3 router:
hostname(config)#arp
arpa
'''snip'''
Reference: http://tiny.cc/cjsxu
Also, know please that WGB is not supported with hybrid REAP (H-REAP).
Even if it worked with you sometimes, it is not supported and cisco did not design it to work with HREAP.
http://bit.ly/yLn9D1
I am only aware about one difference between central switching HREAP and local mode; which is that any limitation applied to HREAP will be applied if it is central switching. just like our situation with WGB with HREAP.

WLC 5508 and associated AP's

Hi,
I have a problem with a poor signal. I have two WLC 5508 and 10 ap's 3502. So, that I have two wlc on the network I decided to divide this 10 ap's.
WLC 5508 has 7.0.98 software version.
The 5 first ap was associated to one wlc and the other 5 to second controller.
Two problems was observed, first that some clients which try connect to AP associated to second controller have problem to obtain IP address from DHCP pool on first wlc.
The second problem is that on this two WLC was configured two DHCP pool. One controller assigns address for a dedicated WLAN and the second wlc assigns address for a second WLAN.
This two WLAN's is broadcast on two wlc.
Kamil

Hi Nicolas,
The APs are 3502I model and now are located on the lower ceiling.
From Thursday all APs are associated to only one WLC the second one is just only as a backup and from this time there are not any problems with a signal. This information is directly from clients.
The DHCP pool is located on the first WLC now.
Also, I considered to use switch or other machine as a DHCP pool but it's problematic to deploy now.
Kamil

How to make WLC 5508-HA controller mantainance mode to HA mode

Hi,
I have two wlc 5508 with HA mode, If unfortunally redudndent link disconnected and standby wlc goes to mantainance mode.
then again I connected redundent link but second wlc does not come in ha, it still remain in mantainance mode.
What is the configuration that device goes to mantainance mode to HA Mode automatically. withought reboot mantainance controller.
Pleasde help....

HA Pairing is possible only between the same type of hardware and software versions. Mismatch may result in Maintenance Mode.
Refer
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html

NAC Manager High Availability Peer CAM DEAD

Hi,
I have two NAC Managers with High Availability and i have used both sides eth1 interface as a Heartbit link.
I have done following Steps for High Availability.
1) Synchronize the times between two CAMs.
2) Generate a Temporary SSL certificate in both CAMs and done export-import procedure in each other.
3) Make One CAM as a Primary and another as Seconday.
But after all this configuration done i can see the status in Monitoring> Reports as--------Primary CAM is up in both the servers and Redundant CAM is down.
Also in Failover Tab i can see ------Local CAM - OK [Active] and Peer CAM :- DEAD.
I have also attached some screenshots so you can find out the same.
Your help will highly appreciated.
Thanks

Try the following steps and verify that all the steps were followed :
http://www.cisco.com/c/en/us/support/docs/security/nac-appliance-clean-access/99945-NAC-CAM-HA.html

WLC 5508 reboots itself after upgrading to 7.5.102.0

Hello all.
We have two WLC 5508 and we upgraded both to software release 7.5.102.0 two weeks ago. We also upgrade the FUS to version 1.7.
Since then both WLC reboot randomly once or twice a day with no obvious reason.
Is anyone else facing the same issue?
Many thanks.

Ok, in that case it is very difficult to pin-point the cause for these sorts reboots. It may be due to a unknown bug. Go through below 7.5.102.0 release notes and see any unresolved caveats related to your issue
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html#wp1030058
Have you configure syslog on your WLC ? If so see what is the last syslog message sent by WLC before reloading, it may indicate something.
Do more observation & see whetehr controller reboot every time it hit 1k client limit. Try to narrow down the criteria to identify under what conditions this will trigger.
In my controller I do not have that many clients & cannot comment if it is related.
HTH
Rasika

Two WLC 5508 Anchor High Availability

Similar Messages

Maybe you are looking for