Troubleshooting guide

8 — 5620 SAM system redundancy
Alcatel-Lucent 5620 Service Aware Manager 8-11
5620 SAM
System Administrator Guide
Table 8-2 summarizes the 5620 SAM database redundancy functions.
Table 8-2 5620 SAM database redundancy functions
Function Notes
Database switchover
A database switchover is a manual operation that reverses the
primary and standby database roles, for example, for primary
database maintenance, or to realign database roles with database
stations after a server activity switch.
A switchover can occur only when the primary and standby databases
are functioning correctly and can communicate with each other.
A database switchover involves the following sequence of events.
• A 5620 SAM administrator initiates the switchover on a primary or
standby server.
• The main server asks each auxiliary server to release all database
connections. The switchover fails if all database connections are
not released within 15 minutes.
• The main server directs the standby database to become the
primary database.
• The main server fully synchronizes information with the new
primary database.
See Procedure 8-5 for information about performing a database
switchover.
No automatic database realignment occurs after a
database switchover.
Database failover
A database failover is an automatic operation that changes the
standby database into a primary database when the original primary
database is unreachable, for example, because of a power disruption
on the primary database station.
A database failover involves the following sequence of events.
• No main server can communicate with the primary database
within a period that is 2 min by default.
• The currently active main server directs the standby database to
become the primary database.
• If automatic database realignment is enabled and the primary
server and database are not aligned, the primary server performs
an activity switch.
• The primary server directs each auxiliary server to connect to the
new primary database.
• The main server restarts after a failover.
When the primary server detects a communication
failure with the primary or standby database, the
GUI clients are informed that the database is not
reachable.
After the cause of the communication failure is
resolved, the GUI clients are notified that the
database is reachable.
After a failover, you must reinstantiate the former
primary database as the new standby database.
Database redundancy is not restored until
reinstantiation is complete.
The 5620 SAM attempts to automatically
reinstantiate the former primary database when
automatic database reinstantiation is enabled.
Re-establishing database redundancy
Re-establishing database redundancy after a database failure
requires database reinstantiation to replicate the current primary
database as the standby database.
After a failover, the former primary database is not available for
redundancy until an operator or the automatic database
reinstantiation function reinstantiates it as the new standby
database.
See Procedures 8-8 and 8-9 for information about re-establishing
database redundancy after a failover.
The following conditions must be met before you
can re-establish database redundancy.
• The failover completes successfully.
• The station that contains the primary
database is operational.
• The former primary database proxy port is
configured and in service.
Release 13.0 R2 | May 2015 | 3HE 09815 AAAB TQZZA Edition 01