Alcatel-Lucent 5620 - Page 174

3 — Troubleshooting using network alarms
3-132 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 3-79 Domain: vlan
Name: TunnelElementDeleteError
Type: configurationAlarm (11)
Probable cause: tunnelElementInUse (264)
Severity: Major
Object Type (class): TopologyRule
Domain: tunnelmgmt
Implicitly cleared (self-clearing): No
The alarm is raised when the
deletion of an obsolete or unused
tunnel element fails.
Name: TunnelElementInUseWarning
Type: configurationAlarm (11)
Probable cause: tunnelElementInUse (264)
Severity: Warning
Object Type (class): TopologyRule
Domain: tunnelmgmt
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM does not attempt to delete
an obsolete or unused tunnel
element because the element is in
use by another object.
Alarm Attributes Additional information
Name: IfVlanSubTypeConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Major
Object Type (class):
L2AccessInterface
Domain: vlan
Implicitly cleared (self-clearing): Yes
The alarm is raised when more than
one type of VLAN service is
configured with the same VLAN ID.
The alarm is raised against an L2
access interface.
Name: ManagementVlanConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Warning
Object Type (class): Vlan
Domain: vlan
Implicitly cleared (self-clearing): Yes
The alarm is raised when a
management VLAN ID is in use by
another service type.
Name: SapVlanSubTypeConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Warning
Object Type (class): Site
Domain: vlan
Implicitly cleared (self-clearing): No
The alarm is raised when a SAP
resynchronization indicates that the
VLAN subtype of the SAP is different
from the site subtype. The alarm
information includes the ID of the
associated port.
Name: SiteManagementVlanConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Warning
Object Type (class): Site
Domain: vlan
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
management VLAN ID is used for
another type of service.
Name: SiteVlanSubTypeConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Major
Object Type (class): Site
Domain: vlan
Implicitly cleared (self-clearing): Yes
The alarm is raised when more than
one type of VLAN service has the
same VLAN ID. The alarm is raised
against a site.
Name: VlanSubTypeConflict
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Severity: Major
Object Type (class): Vlan
Domain: vlan
Implicitly cleared (self-clearing): Yes
The alarm is raised when more than
one type of VLAN service has the
same VLAN ID. The alarm is raised
against a service.
Alarm Attributes Additional information
(2 of 2)
Aug 2010
AAAD
8.0 R4