Alcatel-Lucent 5620 Troubleshooting Manual page 118

3 — Troubleshooting using network alarms
Alarm
Name: GneTransportAlarm
Type: TransportAlarm (71)
Probable cause: User_Defined (558)
Name: InBandManagementConnectionDown
Type: communicationsAlarm (4)
Probable cause:
managementConnectionDown (111)
Name: InconsistenciesOnNode
Type: integrityViolation (85)
Probable cause: inconsistenciesOnNode
(813)
Name: InterfaceDown
Type: InterfaceAlarm (13)
Probable cause: interfaceDown (32)
Name: InvalidBOFAddress
Type: communicationsAlarm (4)
Probable cause: invalidBOF (847)
Name: JMSServerDown
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
Name:
ManagementInterfaceProtectionSwitch
Type: communicationsAlarm (4)
Probable causes:
•
switchToInband (814)
•
switchToOutband (815)
Name: ManagementIPSwitchUnsupported
Type: communicationsAlarm (4)
Probable cause: managementAddressInvalid
(812)
(4 of 11)
3-76
Attributes
Severity: Variable or indeterminate
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class):
NodeDiscoveryControl
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
StatefullConnectableInterface
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
NodeDiscoveryControl
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: Warning
Object Type (class):
NodeDiscoveryControl
Domain: netw
Implicitly cleared (self-clearing): No
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
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.
The alarm is raised when the
5620 SAM cannot reach a managed
NE using the ping function over an
in-band connection.
The alarm is raised when a device
detects one or more configuration
inconsistencies. On a 9500 MPR, this
can be caused by cross-connect
creation failure during service
creation.
The alarm is raised when an
interface or underlying resource
fails, as indicated by an interface
compositeState attribute value of
failed or underlyingResourceFailed.
The alarm is raised during a network
topology rescan in which the 5620
SAM does not find a previously
configured NE BOF address, and the
Management IP Selection of the NE is
set to one of the following:
•
Out Of Band Preferred
•
In Band Preferred
The alarm is raised when JMS
communication fails.
The alarm is raised when an NE has
in-band and out-of-band
management interfaces and switches
from one type of management to the
other.
The alarm is raised when an attempt
is made to switch the management
address of an NE from one IP version
to another.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4