Alcatel-Lucent 5620 Troubleshooting Manual page 61

Alarm name, ID, type, and probable
cause(s)
Alarm name: BatmPWVcJtrBfrOverruns
Alarm ID: 319
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Alarm name: BatmPWVcJtrBfrUnderruns
Alarm ID: 317
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Alarm name: BatmPWVcMalformedPkt
Alarm ID: 321
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Alarm name: BatmPWVcNearEndFC
Alarm ID: 323
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Alarm name: BatmPWVcPktsOoseq
Alarm ID: 315
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name: AllArchiveLogsDeleted
Alarm ID: 199
Type: databaseAlarm (29)
Probable cause: archivedLogsIssue (154)
Alarm name:
ArchiveLogDiskSpaceBelowThreshold
Alarm ID: 197
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Alarm name:
BackupDiskSpaceBelowThreshold
Alarm ID: 195
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
(1 of 4)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): Interface
Domain: circem
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: circem
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: circem
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: circem
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: circem
Self-clearing alarm raised: No
Table 3-9 Domain: db
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
The alarm is raised when the
threshold is crossed for the number
of packets detected out of range, as
indicated by the TDM header
sequence numbers, and could not be
re-ordered, or could not fit in the
jitter buffer.
The alarm is raised when the
threshold is crossed for the number
of times a packet needed to be
played out and the jitter buffer was
empty.
The alarm is raised when the
threshold is crossed for the number
of packets detected by the
unexpected size or bad headers
stack.
The alarm is raised when the
threshold is crossed for the number
of local packet failures.
The alarm is raised when the
threshold is crossed for the number
of packets detected out of sequence,
as indicated by the TDM header
sequence numbers, but successfully
re-ordered.
Additional information
—
One or more filesystem thresholds
for the 5620 SAM database have been
reached, as specified in the
nms-server.xml file.
November 2008 3-23