Alcatel-Lucent 5620 Troubleshooting Manual page 73

Alarm
Name:
StandbyOracleHomeDiskSpaceBelowThresh
old
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Name:
StandbyStagingDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Name: SwitchOverDatabase
Type: configurationAlarm (11)
Probable cause: switchOverDatabase (157)
Name: SwitchOverDatabaseFailed
Type: configurationAlarm (11)
Probable cause: switchOverDatabaseFailed
(158)
Name: TableSpaceAboveThreshold
Type: databaseAlarm (29)
Probable cause:
HighStatisticsCollectionRate (349)
Name: TwoPrimaryDatabase
Type: configurationAlarm (11)
Probable cause: twoPrimaryDatabase (156)
Name: UnableDeleteArchivedLogs
Type: databaseAlarm (29)
Probable cause: archivedLogsIssue (154)
(5 of 5)
Alarm
Name: SubnetMinFreeExc
Type: configurationAlarm (11)
Probable cause:
actualFreeAddrBelowSubnetMin (391)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
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: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
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): No
Table 3-12 Domain: dhcp
Attributes
Severity: Warning
Object Type (class): Subnet
Domain: dhcp
Implicitly cleared (self-clearing): No
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when the standby
database Oracle disk space threshold
specified in the nms-server.xml file
is reached.
The alarm is raised when the standby
database staging disk space
threshold specified in the
nms-server.xml file is reached.
The alarm is raised when a database
switchover occurs.
The alarm is raised when a database
switchover fails.
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.
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.
The alarm is raised when database
disk space is low and the 5620 SAM is
unable to delete the archive logs.
Additional information
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
3-31