Troubleshooting guide

7 — 5620 SAM system redundancy
Alcatel-Lucent 5620 Service Aware Manager 7-5
5620 SAM
System Administrator Guide
When an auxiliary server cannot connect to the primary main server or database, it
re-initializes and continues trying to connect until it succeeds or, in the case of a
database failover, until the main server directs it to the peer database.
An auxiliary server does not cause, perform, or initiate redundancy activities such as
failovers; only a main server controls auxiliary server redundancy functions and
decides which auxiliary servers to use after a failure.
After startup, an auxiliary server waits for initialization information from a main
server. An auxiliary server restarts if it does not receive all required initialization
information within five minutes.
When an auxiliary server fails to respond to a primary main server, the main server
tries repeatedly to establish communication before it generates an alarm. The alarm
clears when the two servers re-establish communication.
7.3 Redundancy functions
Figure 7-3 shows the 5620 SAM system redundancy role-change functions.
Figure 7-3 5620 SAM redundancy role-change functions
Note — 5620 SAM system performance may degrade when a main
server loses contact with a number of auxiliary servers that exceeds
the number of Preferred auxiliary servers in the server cluster.
Primary
database 1
Standby
database 2
Primary
server 1
Standby
server 2
OSS or GUI
client
Activity Switch
1) Server 1 goes down
2) Server 2 comes up
3) Server 2 connects to database 1
A) Database switchover
Can be initiated by the server
during an activity switch
B) Database failover
Can be initiated by the server when
primary database connectivity is lost
No automatic recovery
Managed
network
17701
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01