Alcatel-Lucent 5620 Troubleshooting Manual page 81

Service aware manager release 8.0
Hide thumbs Also See for 5620:
Table of Contents

Advertisement

Alarm
Name: DDMTxOutputPowerLowAlarm
Type: thresholdAlarm (49)
Probable cause: txOutputPowerLowAlarm
(371)
Name: DDMTxOutputPowerLowWarning
Type: thresholdAlarm (49)
Probable cause: txOutputPowerLowWarning
(370)
Name: Degrade
Type: communicationsAlarm (4)
Probable cause: degrade (462)
Name: DiskCapacityProblem
Type: storageAlarm (25)
Probable cause: diskCapacityProblem (115)
Name: downgradedCardAlarm
Type: softwareAlarm (19)
Probable cause: downgradedCard (195)
Name: DryContactAlarm
Type: dryContactAlarm (47)
Probable cause:
dryContactExternalAlarmRaised (351)
Name: DuplicateRole
Type: configurationAlarm (11)
Probable cause: twoElementsWithSameRole
(356)
Name: DuplicateSlot
Type: configurationAlarm (11)
Probable cause: duplicateSlotNINumber
(354)
(8 of 14)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723
AAAD
TQZZA Edition 01
Attributes
Severity: Major
Object Type (class):
DigitalDiagnosticMonitoring
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
DigitalDiagnosticMonitoring
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): PhysicalPort
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Variable or indeterminate
Object Type (class): FlashMemory
Domain: equipment
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Card
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Variable or indeterminate
Object Type (class): DryContact
Domain: equipment
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
StackConfiguration
Domain: equipment
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
StackConfiguration
Domain: equipment
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 output
power of an SFP or XFP reaches the
maximum threshold value.
The alarm is raised when the output
power of an SFP or XFP approaches
the maximum threshold value.
The alarm is raised when a degraded
signal is detected.
The alarm is raised when a compact
flash capacity threshold value on an
NE is reached or exceeded. The
alarm condition is detected during
resynchronization or when a
tnmxEqFlashDiskFull trap is
received. The threshold value is not
configurable.The severity of the
alarm depends on the percentage of
disk capacity used, as listed below:
75 percent, Minor
90 percent, Major
100 percent, Critical
The alarm is raised when an IOM is
not upgraded or reset after a device
software upgrade of both CPMs. A
device resets an IOM automatically
after 120 minutes if the IOM is not
manually reset after a CPM upgrade.
The alarm is raised when a device
detects a dry contact alarm
condition.
The alarm is raised when a slot has
the same primary or secondary role
as another slot in the stack. The slot
subsequently enters pass-through
mode.
The alarm is raised when a slot has
the same slot number as another
stack element. The slot must
relinquish its operational status
because it has a higher election key,
based on the up time, slot number,
and MAC address. Both slots
subsequently enter pass-through
mode.
3-39

Advertisement

Table of Contents
loading

Table of Contents