Preview Tool

Cisco Bug: CSCut14540 - MSE HA states are not meaningful enough

Last Modified

Sep 14, 2018

Products (1)

  • Cisco Mobility Services Engine

Known Affected Releases


Description (partial)

For example ?FAILOVER_ACTIVE? is shown on both MSEs and it means that they failed over to the secondary successfully and is the final state of the failover. However ?FAILBACK_ACTIVE? means that the failback is currently in progress and is not the final state of the failback.
Similarly ?PRIMARY_ACTIVE? and ?SECONDARY_ACTIVE? is extremely confusing for networking engineers which think that boths MSEs are in a active/active state while it should make more sense to have ?PRIMARY_ACTIVE? and ?SECONDARY_STANDBY? and when you failover ?PRIMARY_STANDBY? and ?SECONDARY_ACTIVE?. Another one that confuses everyone is ?TERMINATED? when the primary is up but the active one is the secondary ... terminated implies that it's completely down or dead, not that it's ready to failback ...

normal MSE HA setup
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.