Alcatel-Lucent 5620 Troubleshooting Manual page 121

Alarm
Name:
PersistentIndexParametersMisconfigured
Type: configurationAlarm (11)
Probable cause:
persistentIndexConfigurationMismatch
(136)
Name: PhysicalLinkPortsMisconfigured
Type: configurationAlarm (11)
Probable cause:
physicalLinkPortsMisconfigured (181)
Name: PollDeadlineMissed
Type: configurationAlarm (11)
Probable cause: tooManyItemsToPoll (183)
Name: PollerProblem
Type: communicationsAlarm (4)
Probable cause: resyncFailed (24)
Name: RamFreeSpaceExceeded
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Name: RedAlarmThresholdReached
Type: communicationsAlarm (4)
Probable cause: tooManyAlarms (182)
Name: RedundancySwitchover
Type: equipmentAlarm (3)
Probable cause: redundancySwitchover
(143)
Name: RedundantRadioLink
Type: configurationAlarm (11)
Probable cause:
redundantRadioLinkConfigured (819)
Name: SnmpAuthenticationFailure
Type: authenticationAlarm (14)
Probable cause: authFailure (46)
(7 of 11)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class):
AbstractPhysicalLink
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Minor
Object Type (class):
RadioPhysicalLink
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when persistence
is set to Off in the NE BOF.
The alarm is raised when there is an
MTU size mismatch between a link
endpoint and a port. The alarm
clears when the MTUs match.
The alarm is raised when a 5620 SAM
server cannot finish browsing a
statistics MIB before a polling
interval expires.
The alarm is raised when the
5620 SAM is unable to poll a network
object, for example, because of
intermittent or no IP connectivity to
an NE, incorrect SNMP security
parameters, or disabled SNMP on the
NE.
The alarm is raised when a 7250 SAS
sends the
BATM-SYS-MON-MIB.ramFreeSpaceEx
ceeded trap to indicate that a
configurable RAM utilization
threshold is reached.
The alarm is raised when the number
of outstanding 5620 SAM alarms
reaches the critical threshold. When
this happens, the 5620 SAM discards
alarms to keep the number below the
threshold.
The alarm is raised when a 5620 SAM
main server receives a
ssiRedSwitchover trap from an NE,
which indicates that the standby CPM
detects an active CPM failure and is
preparing to take over as the new
active CPM.
The alarm is raised when a radio link
is discovered between two nodes
when there is already a physical
link(s) between the same nodes.
The alarm is raised when an NE SNMP
agent has received an SNMP message
that is not properly authenticated.
An NE typically does not, by default,
send the notification that generates
the alarm; the notification must be
manually enabled through CLI.
3-79