Alcatel-Lucent 5620 - Page 173

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-131
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-77 Domain: trapmapper
Table 3-78 Domain: tunnelmgmt
Name: TooManyCpaaPerOspfArea
Type: configurationAlarm (11)
Probable cause: tooManyCpaaPerOspfArea
(287)
Severity: Critical
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
The alarm is raised when there are
too many 7701 CPAAs for an OSPF
area.
Name: TopologyIsisSystemError
Type: topologyAlarm (34)
Probable cause:
isisSystemNotAdvertisingTeRouterId (272)
Severity: Major
Object Type (class):
AutonomousSystem
Domain: topology
Implicitly cleared (self-clearing): Yes
The alarm is raised when an IS-IS
topology system error is detected.
Alarm Attributes Additional information
Name: TrapMapperQueueFull
Type: queueFull (73)
Probable cause: trapRateTooHigh (564)
Severity: Critical
Object Type (class):
TrapMapperManager
Domain: trapmapper
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM detects that the queue for
traps that are to be mapped to
alarms is full. Until queue space is
available, the 5620 SAM drops traps
that are to be mapped to alarms.
Alarm Attributes Additional information
Name: PacingInProgressWarning
Type: configurationAlarm (11)
Probable cause:
noUpdatesDueToPacingInProgress (514)
Severity: Warning
Object Type (class): TopologyRule
Domain: tunnelmgmt
Implicitly cleared (self-clearing): Yes
The alarm is raised when tunnel
creation or deletion is not performed
after a member is added or removed
from a rule group because topology
rule pacing is in progress. When this
occurs, the Reapply and Delete
Unused operations must be
performed manually when the pacing
is complete. The alarm clears after a
Reapply operation is performed.
Name: TopologyRuleExecutionError
Type: configurationAlarm (11)
Probable cause: ruleErrorOrRuleEngineError
(262)
Severity: Major
Object Type (class): TopologyRule
Domain: tunnelmgmt
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM cannot execute a topology
rule or when rule execution
generates an error. Rule execution is
the process that determines which
tunnel elements require creation,
modification, or deletion. The alarm
typically indicates that the rule is
misconfigured.
Name: TunnelElementCreationError
Type: configurationAlarm (11)
Probable cause:
unableToCreateTunnelElement (263)
Severity: Major
Object Type (class): TopologyRule
Domain: tunnelmgmt
Implicitly cleared (self-clearing): No
The alarm is raised when the
creation of a missing tunnel element
fails.
(1 of 2)
Alarm Attributes Additional information
(4 of 4)
Aug 2010
AAAD
8.0 R4