Alcatel-Lucent 5620 Troubleshooting Manual page 112

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

Advertisement

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: STMSystemMultiAuxAvailable
Alarm ID: 527
Type: misConfiguration (53)
Probable cause:
multiAuxiliaryServersAvailable (399)
Alarm name: STMSystemNotAvailable
Alarm ID: 526
Type: communicationsAlarm (4)
Probable cause: noAuxiliaryServersAvailable
(256)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name:
scheduledTaskCompletionStatus
Alarm ID: 528
Type: taskCompletionAlarm (45)
Probable cause: scheduledTaskCompleted
(400)
Alarm name, ID, type, and probable
cause(s)
Alarm name: AuthenticationFailure
Alarm ID: 128
Type: communicationsAlarm (4)
Probable cause: multipleSecurityViolations
(336)
Alarm name: AuthorizationFailure
Alarm ID: 529
Type: communicationsAlarm (4)
Probable cause: multipleSecurityViolations
(336)
Alarm name: JMSClientMessagesRemoved
Alarm ID: 532
Type: communicationsAlarm (4)
Probable cause:
maximumExceededMessages (297)
(1 of 9)
3-74
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class): TestManager
Domain: sas
Self-clearing alarm raised: No
Severity: Critical
Object Type (class): TestManager
Domain: sas
Self-clearing alarm raised: No
Table 3-48 Domain: schedule
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Info
Object Type (class): ScheduledTask
Domain: schedule
Self-clearing alarm raised: No
Table 3-49 Domain: security
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
TSecurityManager
Domain: security
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
TSecurityManager
Domain: security
Self-clearing alarm raised: No
Severity: Variable or indeterminate
Object Type (class): User
Domain: security
Self-clearing alarm raised: No
November 2008
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
Additional information
Additional information
At lease five attempts to log in to a
5620 SAM client have failed. The
alarm contains the name of the user
attempting authentication.
When the user account of the user is
deleted, the alarm is deleted.
Troubleshooting Guide
3HE 04244 AAAB Ed. 01

Advertisement

Table of Contents
loading

Table of Contents