Alcatel-Lucent 5620 Troubleshooting Manual page 177

Alarm
Name: IsidMisconfiguration
Type: configurationAlarm (11)
Probable cause: isidInconsistent (446)
Name: MacPinningViolation
Type: serviceAlarm (16)
Probable cause: macAddressPinned (348)
Name: McacPolicyDropped
Type: communicationsAlarm (4)
Probable cause: igmpGroupOnSapDropped
(246)
Name: MFibTableSizeLimitReached
Type: resourceAlarm (28)
Probable cause: resourceLimitReached
(131)
Name: MissSpokeConfiguration
Type: configurationAlarm (11)
Probable cause: missSpokeConfiguration
(172)
Name: MldSnpgGrpDroppedLimitExceeded
Type: AccessInterfaceAlarm (32)
Probable cause:
mldSnpgGrpMaxNbrGrpsReached (406)
Name: msapCreationFailure
Type: ConfigurationAlarm (15)
Probable causes:
•
creationFailure (515)
•
radiusAuthFailed (516)
Name: MvrConfiguredFromVplsNotExist
Type: configurationAlarm (11)
Probable cause:
MvrConfiguredFromVplsNotExist (164)
Name: MvrConfiguredProxySapNotExist
Type: configurationAlarm (11)
Probable cause:
MvrConfiguredProxySapNotExist (165)
(2 of 3)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Warning
Object Type (class): AbstractVpls
Domain: vpls
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): AbstractSite
Domain: vpls
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
L2AccessInterfaceIgmpSnpgCfg
Domain: vpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): AbstractBSite,
AbstractTlsSite
Domain: vpls
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): AbstractVpls
Domain: vpls
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
L2AccessInterfaceMldSnpgCfg
Domain: vpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
L2AccessInterface
Domain: vpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
L2AccessInterfaceMldMvrCfg,
L2AccessInterfaceMvrCfg
Domain: vpls
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
L2AccessInterfaceMvrCfg,
L2AccessInterfaceMldMvrCfg
Domain: vpls
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when service
sites use inconsistent I-SID values for
a PBB backbone. The alarm is raised
against a VPLS or M-VPLS service.
The alarm is raised when an attempt
is made to assign a pinned MAC
address to another L2 access
interface or spoke SDP binding in an
M-VPLS or VPLS.
The alarm is raised when an IGMP
group is removed from a SAP because
a multicast CAC policy is applied.
The alarm is raised when the
5620 SAM receives a
svcTlsMfibTableFullAlarmRaised trap
for a VPLS site. The alarm clears
when the 5620 SAM receives a
svcTlsMfibTableFullAlarmCleared
trap for the site.
The alarm is raised when the
5620 SAM detects a spoke SDP
binding between two sites in one
M-VPLS or VPLS. The alarm is not
raised by the 5620 SAM, Release 4.0
or later.
The alarm is raised when a SAP drops
an MLD group because the
configurable maximum number of
MLD groups on the SAP is reached.
The alarm is raised when an NE
notifies the 5620 SAM that it cannot
create an MSAP.
The alarm is raised when an MVR
source is an MVR VPLS that does not
exist. The alarm clears when the MVR
VPLS is created.
The alarm is raised when a
configured MVR proxy SAP does not
exist. The alarm clears when the
proxy SAP is created.
3-135