Before initiating failover, you must consider the following prerequisites and limitations:
You must have the hardware identical to the primary Prime Infrastructure to run a standby instance of Prime Infrastructure.
Prime Infrastructure supports HA on both the physical and virtual appliance deployment models.
A reliable high-speed wired network must exist between the primary Prime Infrastructure and its backup Prime Infrastructure.
The primary and secondary Prime Infrastructure must be running the same Prime Infrastructure software release.
The OVA file size in both primary and secondary Prime Infrastructure must be the same.
Both primary and secondary Prime Infrastructure must be reachable on both sides.
The health monitor process for the secondary Prime Infrastructure must be running during the HA registration.
High reliable network must exist between the primary and secondary Prime Infrastructure.
For primary Prime Infrastructure to initiate HA with a secondary Prime Infrastructure, the secondary Prime Infrastructure services must be running and reachable from the primary Prime Infrastructure. You must boot the secondary Prime Infrastructure first, and then boot the primary Prime Infrastructure to initiate HA registration.
Failover should be considered temporary. The failed primary Prime Infrastructure should be restored to normal as soon as possible, and failback is initiated. The longer it takes to restore the failed primary Prime Infrastructure, the longer Prime Infrastructure runs without HA support.
The latest controller software must be used.
The primary and secondary host are not required to share the same subnet. They can be geographically separated.
The ports over which the primary and secondary Prime Infrastructure communicate must be open (not blocked by firewalls, application fireways, gateways, and so on). The Tomcat port is configurable during installation. Reserve 1522 for solid database port.
Any access control lists imposed between the primary and secondary Prime Infrastructure must allow traffic to go between the primary and secondary Prime Infrastructure.
The primary Prime Infrastructure must have a sufficient number of licenses for the devices. When failover occurs, the secondary Prime Infrastructure uses the licenses of the primary Prime Infrastructure for the devices.
A secondary Prime Infrastructure can only support one primary Prime Infrastructure.
When HA is enabled for the first time, synchronizing the servers takes a considerable amount of time. The time it would take would be in the order of 30 minutes or more depending on the size of the database.
During the HA registration, ensure that the bandwidth between the primary Prime Infrastructure and the secondary Prime Infrastructure is 1Gbps. If the bandwidth is too low, HA registration and failover will fail.
Ensure that you remove HA from the Prime Infrastructure server before you being an upgrade to a newer version of Prime Infrastructure.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...