Alcatel-Lucent 5620 Troubleshooting Manual page 158

3 — Troubleshooting using network alarms
Alarm
Name: TodSuiteAssignmentFailure
Type: todSuiteAlarm (35)
Probable cause:
configConflictOrResourceFull (274)
Name: TopologyMisconfigured
Type: configurationAlarm (11)
Probable cause: topologyMisconfigured (81)
Name: TypeMismatch
Type: configurationAlarm (11)
Probable cause:
serviceSiteTypeMisconfigured (82)
Name: VideoInterfaceDown
Type: VideoInterfaceAlarm (72)
Probable cause: interfaceDown (32)
Name: VLanUplinkDown
Type: VLanUplinkAlarm (89)
Probable cause: VLanUplinkDown (852)
Name: VLanUplinkNotCreated
Type: VLanUplinkAlarm (89)
Probable cause: VLanUplinkNotCreated
(853)
(3 of 3)
Alarm
Name:
ManagementAccessFilterMisconfigured
Type: configurationAlarm (11)
Probable cause: invalidSourcePortIdentifier
(61)
Name:
ManagementAccessFilterMisconfiguredIpv6
Type: configurationAlarm (11)
Probable cause: invalidSourcePortIdentifier
(61)
3-116
Attributes
Severity: Minor
Object Type (class): AccessInterface
Domain: service
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): VideoInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): VlanUplink
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
Table 3-65 Domain: sitesec
Attributes
Severity: Warning
Object Type (class): MacMafEntry,
MafEntry
Domain: sitesec
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): MafIPv6Entry
Domain: sitesec
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when a Time of
Day suite cannot be assigned to an
aggregation scheduler, or to an L2 or
L3 access interface, because of a
configuration conflict or a lack of
resources. The alarm is not raised
against a SAP.
The alarm is raised when the same
service ID on two NEs is associated
with a different service type on each
NE, or when a 7250 SAS or Telco
VLAN is configured using a port that
is not in Network mode.
The alarm is raised when one
5620 SAM service ID is associated
with service sites that belong to
different service types.
The alarm is raised when a video
interface is operationally down. The
alarm clears when the video
interface is operationally up.
The alarm is raised when a VLAN
uplink is operationally down.
The alarm is raised when an
expected VLAN uplink does not exist.
Additional information
The alarm is raised when a MAF is
misconfigured.
The alarm is raised when an IPv6 MAF
is misconfigured.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4