3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: ReceivedHigherBridgePriority
Alarm ID: 504
Type: SdpBindingAlarm (30)
Probable cause:
customerDeviceMisconfigured (332)
Alarm name: sapReceivedProtSrcMac
Alarm ID: 393
Type: accessInterfaceAlarm (40)
Probable cause:
ProtectedSourceMacLearned (294)
Alarm name: StpExceptionCondition
Alarm ID: 297
Type: AccessInterfaceAlarm (32)
Probable cause: StpException (228)
Alarm name: StpRootGuardViolation
Alarm ID: 503
Type: AccessInterfaceAlarm (32)
Probable cause:
spanningTreeTopologyChanged (331)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name: DuplicateVrfPolicy
Alarm ID: 229
Type: configurationAlarm (11)
Probable cause: duplicateVrfPolicyExists
(177)
Alarm name: DuplicateVrfTarget
Alarm ID: 230
Type: configurationAlarm (11)
Probable cause: duplicateVrfTargetExists
(178)
(1 of 2)
3-42
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): CircuitStp
Domain: l2fwd
Self-clearing alarm raised: No
Severity: Minor
Object Type (class):
AccessInterfaceFib
Domain: l2fwd
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
AccessInterfaceStp
Domain: l2fwd
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
AccessInterfaceStp
Domain: l2fwd
Self-clearing alarm raised: Yes
Table 3-22 Domain: l3fwd
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
ServiceSiteImportPolicy
Domain: l3fwd
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): ServiceSite
Domain: l3fwd
Self-clearing alarm raised: Yes
November 2008
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
The alarm is raised when a customer
NE is configured with a bridge
priority equal to zero. The SDP
binding that connects to the
customer device is blocked as a
result. Remove the customer device
or reconfigure the customer bridge
priority with a value greater than
zero.
A relearn request for a protected
MAC is received on a restricted SAP
The alarm is raised when an STP
exception condition is present on a
SAP. The node sends a trap to the
5620 SAM when the STP condition has
changed. Conditions that can cause
the alarm include, one way
communication or the detection of a
downstream loop.
The alarm is raised when there is an
STP root-guard violation. This can
occur only when root guard is
enabled for the access interface.
Additional information
Review the alarm details for
additional information about the
alarm, including:
•
the policy number and type
•
the site Alarm ID and service
Alarm ID of the duplicate VRF
policy or target
Troubleshooting Guide
3HE 04244 AAAB Ed. 01