Troubleshooting guide

7 — 5620 SAM system redundancy
7-12 Alcatel-Lucent 5620 Service Aware Manager
5620 SAM
System Administrator Guide
7.4 Redundancy failure scenarios
The following describe the 5620 SAM actions in response to various types of
redundancy failures.
• Primary server loses contact with primary database
If the standby server can communicate with the primary database and the
managed NEs, the primary server performs a server activity switch. No database
failover occurs.
If automatic database realignment is enabled, the new primary server performs a
database switchover.
• Primary server loses contact with managed NEs
If the standby server can communicate with the primary database and the
managed NEs, the primary server performs a server activity switch.
If automatic database realignment is enabled, the new primary server performs a
database switchover.
• Primary server loses contact with primary database and managed NEs
If the standby server can communicate with the primary database and the
managed NEs, the primary server performs a server activity switch. No database
failover occurs.
If automatic database realignment is enabled, the new primary server performs a
database switchover.
• Primary server loses contact with primary database, managed NEs, and
standby server
The standby server activates to become the new primary server, and if automatic
database realignment is enabled, initiates a database switchover.
• Both servers lose contact with primary database
The primary server initiates a database failover, and if automatic database
realignment is enabled, also initiates a server activity switch.
• Both servers lose contact, primary server and database can communicate
The primary server and database remain the primary server and database. The
5620 SAM raises an alarm about the server communication failure.
• Both servers lose contact with managed NEs
If the primary and standby servers can each communicate with the preferred
database, no server activity switch or database failover occurs. The 5620 SAM
raises a reachability alarm against each NE in the network.
• Both servers lose contact with primary database and managed NEs
If the primary and standby servers can communicate with each other, no server
activity switch or database failover occurs. However, the 5620 SAM system is
unavailable; manual intervention such as a database failover is required.
• Both servers fail, primary database isolated, standby database operational
When both servers return to operation, the servers cannot connect to the primary
database. Because the state of the standby database is unknown, no database
failover occurs; manual intervention such as a database switchover is required.
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01