Alcatel-Lucent 5620 Troubleshooting Manual page 111

Alarm name, ID, type, and probable
cause(s)
Alarm name: RuleRegistrationError
Alarm ID: 364
Type: ConfigurationAlarm (15)
Probable cause: ruleContentsError (261)
Alarm name, ID, type, and probable
cause(s)
Alarm name: SasSlaAlarm
Alarm ID: 568
Type: oamAlarm (18)
Probable cause: networkDegradation (204)
Alarm name: SasThresholdExceededAlarm
Alarm ID: 272
Type: oamAlarm (18)
Probable cause: networkDegradation (204)
Alarm name:
SasTooManyTestsOnNodeAlarm
Alarm ID: 287
Type: oamAlarm (18)
Probable cause:
tooManyTestsDeployedOnNode (220)
(1 of 2)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Table 3-46 Domain: rules
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): RuleSet
Domain: rules
Self-clearing alarm raised: Yes
Table 3-47 Domain: sas
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Minor
Object Type (class): TestSuite
Domain: sas
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Test
Domain: sas
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): NeAgent
Domain: sas
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
Additional information
—
Alarms are raised when a rising or
falling threshold is crossed due to
rising or falling values, based on
jitter, latency, or loss. Alarms are
raised against scheduled tests only.
You can also view the alarm
information from the Faults tab.
Click on the Alarms on Related
Objects tab button for the
appropriate tested object against
which the threshold was exceeded.
Details of the alarm include:
•
threshold-crossing type
•
current data on the threshold
•
current threshold parameter
setting, which was exceeded or
dropped below, causing the
alarm to be raised
The alarm displays additional
information:
•
node ID of the managed device
with too many tests
•
the number of deployed tests of
the managed device
•
the maximum number of
deployed tests of the managed
device
When 60% of a node limit for creating
or performing OAM tests is reached,
the alarm is raised.
For individual OAM tests, an attempt
to create or perform an NE
schedulable test is rejected on a
node when the limit of tests reaches
95% of device capacity.
November 2008 3-73