Alcatel-Lucent 5620 Troubleshooting Manual page 159

Service aware manager release 8.0
Hide thumbs Also See for 5620:
Table of Contents

Advertisement

Alarm
Name: MediationAuthenticationFailure
Type: communicationsAlarm (4)
Probable cause: noMediationPolicyFound
(62)
Alarm
Name: AllTimingReferencesNotQualified
Type: communicationsAlarm (4)
Probable cause:
allTimingReferencesNotQualified (419)
Name: BITSNotQualified
Type: communicationsAlarm (4)
Probable cause:
timingReferenceNotQualified (418)
Name:
ExternalTimingReferenceNotQualified
Type: communicationsAlarm (4)
Probable cause:
timingReferenceNotQualified (418)
Name: SiteSyncDeploymentFailure
Type: equipmentAlarm (3)
Probable cause: siteSyncFailure (441)
Name: TimingHoldover
Type: communicationsAlarm (4)
Probable cause: timingHoldover (511)
Name: TimingReferenceOneNotQualified
Type: communicationsAlarm (4)
Probable cause:
timingReferenceNotQualified (418)
Name: TimingReferenceTwoNotQualified
Type: communicationsAlarm (4)
Probable cause:
timingReferenceNotQualified (418)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723
AAAD
TQZZA Edition 01
Table 3-66 Domain: snmp
Attributes
Severity: Critical
Object Type (class): PollerManager
Domain: snmp
Implicitly cleared (self-clearing): No
Table 3-67 Domain: sonet
Attributes
Severity: Major
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class): SiteSync
Domain: sonet
Implicitly cleared (self-clearing): Yes
8.0 R4
Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when an NE has
no associated 5620 SAM mediation
policy.
Additional information
The alarm is raised when no timing
references on an NE are in the
Qualified state.
The alarm is raised when the BITS
timing reference on an NE is not in
the Qualified state.
The alarm is raised when the
External timing reference on an NE is
not in the Qualified state.
The alarm is raised when the
5620 SAM tries to deploy a value for
an object when a transaction that
involves the object is in progress
from a different context.
The alarm is raised when the timing
of an NE is in the Holdover state.
The alarm is raised when Timing
Reference One on an NE is not in the
Qualified state.
The alarm is raised when Timing
Reference Two on an NE is not in the
Qualified state.
3-117

Advertisement

Table of Contents
loading

Table of Contents