Troubleshooting guide

7 — 5620 SAM system redundancy
Alcatel-Lucent 5620 Service Aware Manager 7-9
5620 SAM
System Administrator Guide
When a database failover fails, the primary server tries again to communicate with
the primary database. If the primary database remains unavailable, the primary
server tries again to initiate a failover.
Re-establishing database redundancy
After a failover, the former primary database is no longer part of the redundant
configuration. To re-establish database redundancy, you must reinstantiate the
former primary database as the new standby database. You can do this only when the
failed database station is restored to full operation and has a functional proxy port.
See Procedures 7-8 and 7-9 for information about how to reinstantiate a database.
Figure 7-10 shows a former primary database serving as the new standby database.
Figure 7-10 Server and database roles after database reinstantiation
Automatic database reinstantiation
You can configure the 5620 SAM to automatically reinstantiate the former primary
database as the new standby database. Automatic database reinstantiation occurs
only in the event of a database failover. When the function is enabled, the 5620 SAM
attempts an automatic reinstantiation every 60 minutes by default. You can enable
automatic database reinstantiation during a 5620 SAM main server installation or
upgrade. See the 5620 SAM | 5650 CPAM Installation and Upgrade Guide for
information about enabling and configuring automatic database reinstantiation.
Automatic database realignment
In a redundant 5620 SAM system that is geographically dispersed, the primary
server and database may be in separate LANs or WANs after an activity switch or
failover. The network latency that this introduces can affect 5620 SAM system
performance. Automatic database realignment is an optional mechanism that
attempts to ensure that each main server uses the local database.
Note — After a successful failover, database redundancy is not
available. See “Re-establishing database redundancy” in this section.
13463
Primary database
Read/writes
to primary
Standby
server
Primary
server
18562
Standby
database
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01