Showing results for 
Search instead for 
Did you mean: 

Cisco Wireless Services Module 2 (WiSM2) on Release not forming High Availability (HA) Pair





In this document Cisco TAC engineer "Siddharth Vij" has explained about Cisco Wireless Services Module 2 (WiSM2) on Release not forming High Availability (HA) Pair.


Problem Category

Cisco Wireless Services Module 2 (WS-SVC-WISM2)


Software Version


Problem Details

User was trying to configure a new installation of WiSM-2 (, using HA in Non-VSS pair of 6506 with Sup-720/3C running 15.1(1)SY1) IOS). 


He had them up as both "primary", and when tried to put one as secondary, and put them into an HA cluster, both rebooted into maintenance mode. I logged into the console, disabled the HA, and now, I am unable to get to either of the WiSM-2's via HTTP/S, and ping fails as well. Neither controller appears to be reachable, except via console.



The issue was that the licenses on Both the Primary and Secondary controller software version were not activated, the end-user license agreement (EULA) was not accepted, therefore both the controllers were coming up in Maintenance Mode.


Took Both Primary and Secondary Controllers out of HA mode, executed the command "config port adminmode all enable" and rebooted the controllers.


When the controllers came up after the reboot, I went to the GUI of the controllers to activate the Licenses on each of the controllers and accepted the EULA agreement on both the controllers.


Rebooted the controllers and after they came up post reboot, I enabled Primary and Secondary mode on the controller and enabled High Availability SSO on both the controllers.


Both the controllers were able to form the HA pair and were able to come up in Primary and Secondary Mode respectively.


Command Explanation - config port adminmode

To enable or disable the administrative mode for a specific controller port or for all ports, use the config port adminmode command.


config port adminmode { all | port} { enable | disable}


Syntax Description


Configures all ports


Number of the port


Enables the specified ports


Disables the specified ports


Information About High Availability

High availability (HA) in controllers allows you to reduce the downtime of the wireless networks that occurs due to the failover of controllers.


A 1:1 (Active:Standby-Hot) stateful switchover of access points (AP SSO) is supported. In an HA architecture, one controller is configured as the primary controller and another controller as the secondary controller.


After you enable HA, the primary and secondary controllers are rebooted. During the boot process, the role of the primary controller is negotiated as active and the role of the secondary controller as standby-hot. After a switchover, the secondary controller becomes the active controller and the primary controller becomes the standby-hot controller. After subsequent switchovers, the roles are interchanged between the primary and the secondary controllers. The reason for switchovers are either because of manual trigger or a controller or network failure.


During an AP SSO, all the AP sessions statefully switch over and all the clients are deauthenticated and reassociated with the new active controller except for the locally switched clients in the FlexConnect mode.


The standby-hot controller continuously monitors the health of the active controller through a direct wired connection over a dedicated redundancy port. Both the controllers share the same configurations, including the IP address of the management interface.


Before you enable HA, ensure that both the controllers are physically connected through the redundant port using an Ethernet cable. Also, ensure that the uplink is connected to an infrastructure switch and that the gateway is reachable from both the controllers.


In HA architecture, the redundancy port and redundant management interfaces have been newly introduced.


A seamless transition of clients from the active controller to the standby controller is also supported. Clients that are not in the Run state are removed after the switchover. During the stateful switchover of a client (Client SSO), the information of the client is synchronized with the standby controller when the client is associated with the controller or is configured. Clients that are fully authenticated, that is, clients that are in the Run state, are synchronized with the peer controller. The data structures of clients are synchronized based on the client state. Clients that are in the transient state are dissociated after a switchover.


More Information

config port adminmode

Users cannot access the WLAN controller (WLC) through the Web GUI

Cisco 5500 Series Wireless Controllers - High Availability (SSO) Deployment Guide

Cisco Wireless LAN Controller Configuration Guide, Release 7.5 - Configuring High Availability

Release Notes for Cisco Wireless LAN Controllers 5500 and Lightweight Access Points for Release

Recognize Your Peers
Content for Community-Ad