Alcatel-Lucent 5620 Troubleshooting Manual page 108

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: peerSetConfigurationIssue
Alarm ID: 267
Type: configurationAlarm (11)
Probable cause: mismatchPeerSets (199)
Alarm name: PimDown
Alarm ID: 184
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name: DefaultInstanceInconsistency
Alarm ID: 211
Type: ConfigurationAlarm (15)
Probable cause:
multipleDefaultInstancesEncountered (54)
Alarm name: TemplateInconsistency
Alarm ID: 189
Type: ConfigurationAlarm (15)
Probable cause: templatePolicyMismatch
(149)
Alarm name, ID, type, and probable
cause(s)
Alarm name: PppLoopbackDetected
Alarm ID: 362
Type: configurationAlarm (11)
Probable cause: PppLoopbackDetected
(259)
3-70
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class):
VirtualAnyCastRP
Domain: pim
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Site
Domain: pim
Self-clearing alarm raised: Yes
Table 3-38 Domain: policy
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): Manager
Domain: policy
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): PolicyDefinition
Domain: policy
Self-clearing alarm raised: Yes
Table 3-39 Domain: ppp
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Interface
Domain: ppp
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
—
Additional information
The alarm is raised if an accounting
policy is the default for more then
one service type or more then one
network type.
The alarm is raised if there is a
mismatch of data or properties
between a global policy and a local
policy.
Additional information
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01