Alcatel-Lucent 5620 - Page 143

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-101
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-59 Domain: rules
Table 3-60 Domain: sas
Alarm Attributes Additional information
Name: RuleRegistrationError
Type: ConfigurationAlarm (15)
Probable cause: ruleContentsError (261)
Severity: Warning
Object Type (class): RuleSet
Domain: rules
Implicitly cleared (self-clearing): Yes
The alarm is raised when one or more
internal 5620 SAM server rule-engine
rules fails to compile. The cause is
typically a rule syntax error or a
system error.
Alarm Attributes Additional information
Name: SasAccountingAlarm
Type: oamAlarm (18)
Probable cause: noAccountingPolicy (506)
Severity: Minor
Object Type (class): TestSuite
Domain: sas
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM cannot find an SAA
Accounting Policy.
Name: SasSlaAlarm
Type: oamAlarm (18)
Probable cause: networkDegradation (204)
Severity: Minor
Object Type (class): TestSuite
Domain: sas
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects a lightweight test
execution failure.
Name: SasThresholdExceededAlarm
Type: oamAlarm (18)
Probable cause: networkDegradation (204)
Severity: Major
Object Type (class): Test
Domain: sas
Implicitly cleared (self-clearing): Yes
The alarm is raised when a rising or
falling threshold is crossed by a
jitter, latency, or loss value. The
alarm is raised only against a
scheduled test. The alarm
information includes the threshold
type, the threshold setting, and the
current rising or falling value.
Name: SasTooManyTestsOnNodeAlarm
Type: oamAlarm (18)
Probable cause:
tooManyTestsDeployedOnNode (220)
Severity: Major
Object Type (class): NeAgent
Domain: sas
Implicitly cleared (self-clearing): Yes
The alarm is raised when an NE
reaches 60 percent of the allowed
number of created or simultaneously
executed OAM tests. An attempt to
create or execute an NE schedulable
test on an NE fails when the number
of tests reaches 95 percent of the NE
capacity. The alarm information
includes the following:
• the NE ID
• the number of deployed tests on
the NE
• the allowed number of deployed
tests on the NE
Name: STMSystemMultiAuxAvailable
Type: misConfiguration (53)
Probable cause:
multiAuxiliaryServersAvailable (399)
Severity: Critical
Object Type (class): TestManager
Domain: sas
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM detects multiple available
auxiliary servers for test execution.
Name: STMSystemNotAvailable
Type: communicationsAlarm (4)
Probable cause: noAuxiliaryServersAvailable
(256)
Severity: Critical
Object Type (class): TestManager
Domain: sas
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM detects no available
auxiliary servers for test execution.
(1 of 2)
Aug 2010
AAAD
8.0 R4