Alcatel-Lucent 5620 - Page 72

3 — Troubleshooting using network alarms
3-30 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: PrimaryDatabaseWasDown
Type: databaseAlarm (29)
Probable cause: primaryDatabaseWasDown
(193)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when the primary
database returns to service after
being unavailable for at least one
poll.
Name: RealignmentOfDatabase
Type: configurationAlarm (11)
Probable cause: databaseRealignment (455)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when the primary
5620 SAM main server realigns itself
with the preferred database by
performing a database switchover to
connect to the primary database.
Name: RealignmentOfDatabaseFailed
Type: configurationAlarm (11)
Probable cause:
databaseRealignmentFailed (456)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a database
switchover to realign the primary
main server and primary database
fails. The primary main server is not
connected to the preferred
database.
Name: ReinstantiateStandbyDatabase
Type: configurationAlarm (11)
Probable cause:
reinstantiateStandbyDatabase (191)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a standby
database reinstantiation occurs.
Name: ReinstantiateStandbyDatabaseFailed
Type: configurationAlarm (11)
Probable cause:
reinstantiateStandbyDatabaseFailed (192)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a standby
database reinstantiation fails.
Name: RowThresholdConstraintViolated
Type: configurationAlarm (11)
Probable cause:
partialConstraintEnforcement (218)
Severity: Major
Object Type (class):
SizeConstraintPolicy
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the number
of records in a database table
exceeds the number specified in a
size constraint policy.
Name: StagingDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
or standalone database staging disk
space threshold specified in the
nms-server.xml file is reached.
Name:
StandbyDataFileDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the standby
data file disk space threshold
specified in the nms-server.xml file
is reached.
Name:
StandbyInstallDirectoryDiskSpaceBelowThre
shold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the standby
database installation disk space
threshold specified in the
nms-server.xml file is reached.
Alarm Attributes Additional information
(4 of 5)
Aug 2010
AAAD
8.0 R4