AIR-CT5508-K9-HA SKU-HA?

[rsagredog]

Helo Comunity
We purchased a "AIR-CT5508-HA-K9" to be a HA backup. in the Cisco box appears the following part-number: AIR-CT5508-K9-HA, however in command "show redundancy summary and show inventory" no reference appears to SKU-HA. We charge a license SKU-HA on this WLC?

(Cisco Controller)> show redundancy summary
  SSO Redundancy Mode = DISABLED
      Local State = ACTIVE
       Peer State = N / A
             Unit = Primary                     ------¿SKU-HA?---
          Unit ID = 18: E7: 28: BF: DD: C0
Redundancy State = N / A
     Mobility MAC = 18: E7: 28: BF: DD: C0

(Cisco Controller) >show inventory

Burned-in MAC Address............................ XXXXXXXXXXXXX
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 0
NAME: "Chassis"    , DESCR: "Cisco 5500 Series Wireless LAN Controller"
PID: AIR-CT5508-K9,  VID: V03,  SN: XXXXXXXXXXX

Tranks

[Sandeep Choudhary]

Hi, This is the right part. AIR-CT5508-HA-K9- Cisco 5508 Series Wireless Controller for High Availability. Did you setup Primary WLC(with AP license) and secondary WLC (with HA license) in redudency mode ? Check this link to setup and check the status of WLCs. http://networkguy.de/?p=558 ---------------------------------------------------- (Cisco Controller)> show redundancy summary SSO Redundancy Mode = DISABLED Local State = ACTIVE Peer State = N / A Unit = Primary ------¿SKU-HA?--- nO its not HA-SKU(Its the WLC with right AP license) Unit ID = 18: E7: 28: BF: DD: C0 Redundancy State = N / A Mobility MAC = 18: E7: 28: BF: DD: C0 Regards Dont forget to rate helpful posts

[mohanak]

Licensing for HA Pair

A HA Pair can be established between two WLCs running in these combinations:

• One WLC has a valid AP Count license and the other WLC has a HA SKU UDI
• Both the WLCs have a valid AP Count license
• One WLC has an Evaluation license and the other WLC has a HA SKU UDI or Permanent license

One WLC has a valid AP Count license and the other WLC has a HA SKU UDI

• HA SKU is a new SKU with a Zero AP Count License.
• The device with HA SKU becomes Standby the first time it pairs up.
• AP-count license info will be pushed from Active to Standby.
• On event of Active failure, HA SKU will let APs join with AP-count obtained and will start 90-day countdown. The granularity of this is in days.
• After 90-days, it starts nagging messages. It will not disconnect connected APs.
• With new WLC coming up, HA SKU at the time of paring will get the AP Count:

– If the new WLC has a higher AP count than the previous, the 90-day counter is reset.

– If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.

– In order to lower AP count after switchover, the WLC offset timer will continue and nagging messages will be displayed after time expiry.

• Elapsed time and AP-count will be remembered on reboot.
• The factory default HA-SKU controller should not allow any APs to join.

Both the WLCs have a valid AP Count license

• The CLI should be used to configure one WLC as the Standby WLC (as mentioned in the configuration section) provided it satisfies the requirement of minimum permanent license count. This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500, and 8500.
• AP-count license information will be pushed from Active to Standby.
• In the event of a switchover, the new Active WLC will operate with the license count of the previous Active WLC and will start the 90-day countdown.
• The WLC configured as Secondary will not use its own installed license, and only the inherited license from the active will be utilized.
• After 90-days, it starts nagging messages. It will not disconnect connected APs.
• With the new WLC coming up, HA SKU at the time of paring will get the AP Count:

– If the new WLC has a higher AP count than the previous, the 90-day counter is reset.

– If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.

– After switchover to a lower AP count, the WLC offset timer will continue and nagging messages will be displayed after time expiry.

One WLC has an Evaluation license and the other WLC has a HA SKU UDI or Permanent license

• The device with HA SKU becomes the Standby WLC the first time it pairs up with an existing Active WLC running Evaluation License. Or, any WLC running a permanent license count can be configured as the Secondary unit using the CLI configuration provided if it satisfies the requirement of minimum permanent license count. This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500, and 8500.
• AP-count license information will be pushed from Active to Standby.
• In the event of a switchover, the new Active WLC will operate with the license count of the previous Active WLC and start the 90-day countdown.
• After 90-days, it starts nagging messages. It will not disconnect connected APs.
• With new the WLC coming up, HA SKU at the time of paring will get the AP Count:

– If the new WLC has a higher AP count than the previous, the 90-day counter is reset.

– If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.

– After switchover to a lower AP count, the WLC offset timer will continue and nagging messages will be displayed after time expiry.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-44069

[barryfowles]

Hi,

I have set up two 5760 Controllers, one WLC has a valid AP Count license and the other WLC is a HA SKU UDI. I have configured the HA SKU Controller to be the N+1 controller within the same mobility group as the AP count license Controller. All of the APs have been configured with their primary controller as the AP count license Controller and the secondary Controller as the HA SHU Controller. I believe that this a valid design. Can you confirm this.I am hitting fail-over issues but believe that this is due to 3.3.3 code bugs.

Thanks