Alcatel-Lucent 5620 - Page 73

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-31
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-12 Domain: dhcp
Name:
StandbyOracleHomeDiskSpaceBelowThresh
old
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 Oracle disk space threshold
specified in the nms-server.xml file
is reached.
Name:
StandbyStagingDiskSpaceBelowThreshold
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 staging disk space
threshold specified in the
nms-server.xml file is reached.
Name: SwitchOverDatabase
Type: configurationAlarm (11)
Probable cause: switchOverDatabase (157)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a database
switchover occurs.
Name: SwitchOverDatabaseFailed
Type: configurationAlarm (11)
Probable cause: switchOverDatabaseFailed
(158)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a database
switchover fails.
Name: TableSpaceAboveThreshold
Type: databaseAlarm (29)
Probable cause:
HighStatisticsCollectionRate (349)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when the
database table space becomes too
full, which may indicate that the
performance statistics collection
rate or the statistics retention time
is too high.
Name: TwoPrimaryDatabase
Type: configurationAlarm (11)
Probable cause: twoPrimaryDatabase (156)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the standby
database initializes as a primary
database because of a database
failover. The alarm clears when the
original primary database is
operational as the new standby
database.
Name: UnableDeleteArchivedLogs
Type: databaseAlarm (29)
Probable cause: archivedLogsIssue (154)
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when database
disk space is low and the 5620 SAM is
unable to delete the archive logs.
Alarm Attributes Additional information
Name: SubnetMinFreeExc
Type: configurationAlarm (11)
Probable cause:
actualFreeAddrBelowSubnetMin (391)
Severity: Warning
Object Type (class): Subnet
Domain: dhcp
Implicitly cleared (self-clearing): No
The alarm is raised when the actual
number of free addresses in a subnet
falls below the desired minimum
number specified in the subnet
configuration
Alarm Attributes Additional information
(5 of 5)
Aug 2010
AAAD
8.0 R4