Alcatel-Lucent 5620 Troubleshooting Manual page 116

3 — Troubleshooting using network alarms
Alarm
Name: CpuUtilizationExceeded
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Name: DiscoveredPhysicalLinkMismatch
Type: configurationAlarm (11)
Probable cause:
endPointUsedByNumerousLinks (488)
Name: DuplicatePhysicalLinks
Type: configurationAlarm (11)
Probable cause:
duplicatePhysicalLinkConfigured (489)
Name: DuplicateRouterIdProblem
Type: configurationAlarm (11)
Probable cause: duplicateRouterId (168)
Name: EventsThrottled
Type: communicationsAlarm (4)
Probable cause: snmpDaemonOverloaded
(141)
Name:
FailureToSwitchManagementProtocol
Type: communicationsAlarm (4)
Probable cause: managementAddressInvalid
(812)
Name: FrameSizeProblem
Type: configurationAlarm (11)
Probable cause: frameSizeProblem (33)
Name: FtpClientFailure
Type: communicationsAlarm (4)
Probable cause: ftpClientFailure (257)
Name: GneCommunicationAlarm
Type: CommunicationAlarm (64)
Probable cause: User_Defined (558)
(2 of 11)
3-74
Attributes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
AbstractPhysicalLink
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class):
AbstractPhysicalLink
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
NodeDiscoveryControl
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class):
StatefullConnectableInterface
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Variable or indeterminate
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the
7250 SAS CPU utilization exceeds the
configured threshold and the NE
sends the
BATM-SYS-MON-MIB.cpuUtilizationEx
ceeded trap.
The alarm is raised when one
endpoint of a physical link is used as
an endpoint in another physical link.
The alarm is raised when there is
more then one physical link
configured between two endpoints.
The alarm is raised when the
5620 SAM detects that the same
address is being used by multiple
NEs. To prevent 5620 SAM database
corruption, the 5620 SAM does not
discover the NE with the duplicate
address.
The alarm is raised when an NE
throttles events because the event
rate exceeds the configured
maximum.
The alarm is raised when the
5620 SAM cannot switch the
management address of an NE from
one IP version to another.
The alarm is raised when a
provisioned MTU size value is greater
than the supported MTU size value.
The alarm is raised when an NE sends
notification that an FTP operation
initiated by the FTP client fails
because of file unavailability,
interruption during the file transfer,
or a lack of available storage space.
This user-definable alarm is raised
against a generic NE when the
5620 SAM receives a trap from the
generic NE that is mapped to the
alarm in a generic NE alarm
catalogue. The alarm mapping
defines the Probable cause, Severity,
and Implicitly cleared values, and
optionally contains an extension that
is appended to the Name value.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4