Solved: N+1 5508 WLC failover test - Page 4

edwardzeng · ‎08-01-2013

Good day all,

I have a question about the N+1 5508 failover test:

Should I shutdown one of the primary WLC to test failover?

I just setup the N+1 bakcup WLC (5508). B

Based on: http://www.cisco.com/en/US/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide.pdf

We have two production WLCs both 5508 and one 4405.

We just purchased another HA-SKU WLC 5508.

All our four WLCs had been setup into one mobility group in version 7.4.100.6.

.

Their neighbors are all up.

But our test AP could not register to the Backup N+1 WLC. ( We are using option 43 in our DHCP server for all the AP boot.)

Here are the log screen:

================ From test Access Point============

*Mar 1 00:00:53.099: %CDP_PD-4-POWER_OK: Full power - INJECTOR_CONFIGURED_ON_SOURCE inline power source

*Mar 1 00:00:53.842: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.255.1.3, mask 255.255.255.0, hostname wo11-test-ap1

*Mar 1 00:00:54.188: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar 1 00:00:55.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar 1 00:00:55.279: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Mar 1 00:00:56.280: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Mar 1 00:01:03.820: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.254.240.5 obtained through DHCP

*Mar 1 00:01:03.820: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar 1 00:01:13.823: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Aug 2 02:30:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.254.240.5 peer_port: 5246

*Aug 2 02:31:25.003: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!

*Aug 2 02:31:55.001: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.254.240.5:5246

*Aug 2 02:31:55.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Aug 2 02:30:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.254.240.23 peer_port: 5246

*Aug 2 02:30:55.490: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.254.240.23 peer_port: 5246

*Aug 2 02:30:55.493: %CAPWAP-5-SENDJOIN: sending Join Request to 10.254.240.23

*Aug 2 02:30:55.493: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Aug 2 02:30:55.493: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Aug 2 02:30:55.493: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Aug 2 02:30:55.493: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.254.240.23

*Aug 2 02:30:55.874: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 2 02:30:55.931: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 2 02:30:55.987: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WG-WLC1

*Aug 2 02:30:56.041: ac_first_hop_mac - IP:10.255.1.1 Hop IP:10.255.1.1 IDB:BVI1

*Aug 2 02:30:56.041: Setting AC first hop MAC: ccef.481f.14bf

-test-ap1#sh int bvI 1

BVI1 is up, line protocol is up

Hardware is BVI, address is e8b7.489e.4645 (bia e8b7.489e.4645)

Internet address is 10.255.1.3/24

===================From backup N+1 WLC===

*spamApTask4: Aug 02 11:41:09.842: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58470).

*spamApTask4: Aug 02 11:41:01.889: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58470).

*spamApTask4: Aug 02 11:40:57.912: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58470).

*spamApTask4: Aug 02 11:40:55.924: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58470).

*spamApTask4: Aug 02 11:18:50.553: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58469).

*spamApTask4: Aug 02 11:18:42.600: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58469).

*spamApTask4: Aug 02 11:18:38.623: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58469).

*spamApTask4: Aug 02 11:18:36.636: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP 10:255:1:3 (58469).

.

*mmListen: Aug 02 10:43:38.637: #LOG-3-Q_IND: spam_lrad.c:1676 Ignoring discovery request from AP e8:b7:48:9e:46:45 - maximum number of downloads (0) exceeded

*spamApTask0: Aug 02 10:43:38.500: #LWAPP-3-DISC_MAX_DOWNLOAD: spam_lrad.c:1676 Ignoring discovery request from AP e8:b7:48:9e:46:45 - maximum number of downloads (0) exceeded

==================== From one of our Primary WLC=====================

(WLC-5500) >show advanced backup-controller

AP primary Backup Controller .................... ODC-WLC1 10.254.240.5

AP secondary Backup Controller .................. 0.0.0.0

(WLC-5500) >show redundancy summary

Redundancy Mode = SSO DISABLED

Local State = ACTIVE

Peer State = N/A

Unit = Primary

Unit ID = 54:75:D0:DE:DE:40

Redundancy State = N/A

Mobility MAC = 54:75:D0:DE:DE:40

Redundancy Management IP Address................. 0.0.0.0

Peer Redundancy Management IP Address............ 0.0.0.0

Redundancy Port IP Address....................... 0.0.0.0

Peer Redundancy Port IP Address.................. 169.254.0.0

(WLC-5500) >show license capacity

Licensed Feature Max Count Current Count Remaining Count

-----------------------------------------------------------------------

AP Count 250 203 47

==============From the Backup N+1 WLC in DR =====================

(Cisco Controller) >show redundancy summary

Redundancy Mode = SSO DISABLED

Local State = ACTIVE

Peer State = N/A

Unit = Secondary - HA SKU

Unit ID = 6C:41:6A:5F:4C:80

Redundancy State = N/A

Mobility MAC = 6C:41:6A:5F:4C:80

Redundancy Management IP Address................. 10.254.240.3

Peer Redundancy Management IP Address............ 0.0.0.0

Redundancy Port IP Address....................... 169.254.240.3

Peer Redundancy Port IP Address.................. 169.254.0.0

(Cisco Controller) >show license capacity

Licensed Feature Max Count Current Count Remaining Count

-----------------------------------------------------------------------

AP Count 500 0 500

ajc · ‎01-16-2014

Hi Edward,

I have not tried/tested yet Apple TV on the wired side including LSS. I will answer your questions later on this post.

thanks

edwardzeng · ‎01-23-2014

Hi Abraham,

Thank you very much!

Would you mind past the link of your post to me?

I found this document form Cisco, it is very useful.

Hope it will give some help for your labs.

http://www.cisco.com/en/US/docs/wireless/technology/bonjour/7.5/Bonjour_Gateway_Phase-2_WLC_software_release_7.5.html

Cheers,

Edward

ajc · ‎01-24-2014

Hi Edward,

Thanks, I am precisely following that Bonjour Configuration Guide from Cisco.

Preliminary tests did not work and I assume is because I am using Multicast-Unicast instead of Multicast-Multicast. We do not want to activate multicast in the Wired Network yet.

On the other hand, I took first a lot of screenshots for every step I follow and once it works perfectly, I create the post with the details including those pictures. I will let you know once I am done with the tests.

regards

ajc · ‎01-15-2014

Once the HA SKU WLC, I got the following:

(Cisco Controller) >show license all

License Store: Primary License Storage

StoreIndex: 0 Feature: base Version: 1.0

License Type: Permanent

License State: Active, Not in Use

License Count: Non-Counted

License Priority: Medium

License Store: Evaluation License Storage

StoreIndex: 0 Feature: base-ap-count Version: 1.0

License Type: Evaluation

License State: Active, Not in Use, EULA accepted --------------- > EVALUATION LICENSE STATUS CHANGED

Evaluation total period: 8 weeks 4 days

Evaluation period left: 8 weeks 3 days

License Count: 500 / 0 (Active/In-use)

License Priority: High

(Cisco Controller) >

***Proceeding to test Redundancy Operation***, I will post the results.

Scott Fella · ‎01-15-2014

You should be fine...

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

-Scott
*** Please rate helpful posts ***

ajc · ‎01-15-2014

First Step, AP connected to Primary WLC (not HA SKU WLC):

*Dec 12 00:04:18.615: %CAPWAP-5-DHCP_OPTION_43: Controller address 172.23.111.20 obtained through DHCP

*Dec 12 00:04:18.615: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Dec 12 00:04:18.615: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.tdsb.on.ca

*Dec 12 00:04:28.619: %CAPWAP-3-ERRORLOG: Selected MWAR 'DC-WiFi-WLC1-3'(index 0).

*Dec 12 00:04:28.619: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jan 14 21:59:32.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.111.23 peer_port: 5246

*Jan 14 21:59:32.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.23.111.23 peer_port: 5246

*Jan 14 21:59:32.471: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.111.23

*Jan 14 21:59:32.471: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Jan 14 21:59:32.471: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Jan 14 21:59:32.471: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Jan 14 21:59:32.471: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.23.111.23

*Jan 14 21:59:32.927: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jan 14 21:59:32.995: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jan 14 21:59:33.603: ac_first_hop_mac - IP:10.219.96.1 Hop IP:10.219.96.1 IDB:BVI1

*Jan 14 21:59:33.607: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 14 21:59:33.679: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller DC-WiFi-WLC1-3

*Jan 14 21:59:33.843: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

*Jan 14 21:59:33.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 14 21:59:33.963: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Jan 14 21:59:33.971: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jan 14 21:59:34.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Jan 14 21:59:34.955: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jan 14 21:59:34.987: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5560 MHz for 60 seconds.

*Jan 14 21:59:34.991: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jan 14 21:59:34.999: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jan 14 21:59:35.007: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jan 14 21:59:35.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Jan 14 21:59:35.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 14 21:59:36.027: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 14 21:59:37.027: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jan 14 22:00:05.187: %CLEANAIR-6-STATE: Slot 0 enabled

*Jan 14 22:00:06.967: %CLEANAIR-6-STATE: Slot 1 enabled

*Jan 14 22:00:07.671: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Jan 14 22:00:07.739: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jan 14 22:00:08.671: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Jan 14 22:00:08.707: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jan 14 22:00:09.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Jan 14 22:00:26.967: %CLEANAIR-6-STATE: Slot 1 down

*Jan 14 22:00:54.131: %CLEANAIR-6-STATE: Slot 1 enabled

APe4d3.f11e.a8e1#

ajc · ‎01-15-2014

Current AP High Availability Configuration:

2nd Step, shutdown the LAN Switch ports on which the Primary WLC is connected so I force the AP going to HA SKU WLC.

DC-WiFi-SVC1-LAB(config)#inter

DC-WiFi-SVC1-LAB(config)#interface por

DC-WiFi-SVC1-LAB(config)#interface port-

DC-WiFi-SVC1-LAB(config)#interface port-channel 3

DC-WiFi-SVC1-LAB(config-if)#shut

DC-WiFi-SVC1-LAB(config-if)#

Log in the AP after shutdown:

Jan 15 15:52:15.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 2)

*Jan 15 15:52:15.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:18.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 2)

*Jan 15 15:52:18.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:21.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 3)

*Jan 15 15:52:21.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:24.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:24.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:27.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:27.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:30.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:30.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:33.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:33.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:36.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:36.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:39.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 4)

*Jan 15 15:52:39.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:42.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 7)

*Jan 15 15:52:42.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded

*Jan 15 15:52:45.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 8)

*Jan 15 15:52:45.307: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Jan 15 15:52:45.307: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.23.111.23:5246

*Jan 15 15:52:45.371: %WIDS-6-DISABLED: IDS Signature is removed and disabled.

*Jan 15 15:52:45.371: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Jan 15 15:52:45.383: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Jan 15 15:52:45.383: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Jan 15 15:52:45.395: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 15 15:52:46.015: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jan 15 15:52:46.383: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 15 15:52:46.423: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Jan 15 15:52:46.431: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jan 15 15:52:47.167: %CLEANAIR-6-STATE: Slot 0 down

*Jan 15 15:52:47.167: %CLEANAIR-6-STATE: Slot 1 down

*Jan 15 15:52:47.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jan 15 15:52:47.423: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Jan 15 15:52:47.451: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jan 15 15:52:47.459: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jan 15 15:52:47.467: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jan 15 15:52:48.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Jan 15 15:52:48.459: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 15 15:52:48.487: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 15 15:52:49.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jan 15 15:52:56.011: %CAPWAP-3-ERRORLOG: Selected MWAR 'DC-WiFi-WLC1-0'(index 1).

*Jan 15 15:52:56.011: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jan 15 15:52:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.111.20 peer_port: 5246

*Jan 15 15:52:44.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.23.111.20 peer_port: 5246

*Jan 15 15:52:44.471: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.111.20

*Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.23.111.20

*Jan 15 15:52:44.927: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jan 15 15:52:44.995: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jan 15 15:52:45.003: ac_first_hop_mac - IP:10.219.96.1 Hop IP:10.219.96.1 IDB:BVI1

*Jan 15 15:52:45.007: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 15 15:52:45.075: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller DC-WiFi-WLC1-0

*Jan 15 15:52:45.223: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

*Jan 15 15:52:45.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 15 15:52:45.971: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Jan 15 15:52:45.979: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jan 15 15:52:46.007: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Jan 15 15:52:46.959: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jan 15 15:52:46.999: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5520 MHz for 60 seconds.

*Jan 15 15:52:47.003: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jan 15 15:52:47.015: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jan 15 15:52:47.023: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jan 15 15:52:48.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Jan 15 15:52:48.015: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jan 15 15:52:48.047: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jan 15 15:52:49.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

APe4d3.f11e.a8e1#

3rd Step, verifying the LOG on the AP and check if it can connect to the HA SKU WLC

*Jan 15 15:52:45.075: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller DC-WiFi-WLC1-0

*Jan 15 15:52:45.223: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

CONCLUSION:

I needed to activate the EVALUATION LICENSE in the HA SKU WLC which had status = EULA NOT ACCEPTED. I will test the SSID's in order to confirm that redundancy using HA SKU WLC works fine.

ajc · ‎01-15-2014

Hi Scott,

I found that N+1 High Availability works on version 7.3.112.0. Could you give a try?

Important to add that everything worked fine on that version including URL Redirect for Web Auth. Unfortunately, on version 7.5.102.0 URL Redirect does not work.

thanks

ajc · ‎01-17-2014

INFORMATION OF INTEREST:

I found the issue on the URL REDIRECT on version 7.5.102.0 for Authentication using External Login Page (in our case the ISE Device is acting like Web Server + AAA Server for Web Authentication).

The post that I opened is the following:

https://supportforums.cisco.com/message/4114736#4114736

ajc · ‎01-15-2014

Hi Edward, take a look on the case. I put additional information and now is working. thanks