Alcatel-Lucent 5620 Troubleshooting Manual page 72

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