Alcatel-Lucent 5620 Troubleshooting Manual page 113

Alarm name, ID, type, and probable
cause(s)
Alarm name: JMSDurableClientReset
Alarm ID: 530
Type: communicationsAlarm (4)
Probable cause: jmsServerRestart (401)
Alarm name: JMSDurableClientUnsubscribed
Alarm ID: 531
Type: communicationsAlarm (4)
Probable cause:
maximumExceededMessages (297)
Alarm name: KeyChainAuthFailure
Alarm ID: 421
Type: communicationsAlarm (4)
Probable cause: keyChainAuthFailure (314)
Alarm name: Licensed6400LimitExceeded
Alarm ID: 586
Type: licensingAlarm (23)
Probable cause: licensedLimitExceeded
(106)
Alarm name: Licensed6400LimitNearing
Alarm ID: 584
Type: licensingAlarm (23)
Probable cause: licensedLimitNearing (132)
Alarm name:
Licensed6400LimitNearlyExceeded
Alarm ID: 585
Type: licensingAlarm (23)
Probable cause:
licensedLimitNearlyExceeded (133)
(2 of 9)
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: Variable or indeterminate
Object Type (class): User
Domain: security
Self-clearing alarm raised: Yes
Severity: Variable or indeterminate
Object Type (class): User
Domain: security
Self-clearing alarm raised: No
Severity: Major
Object Type (class): KeyChain
Domain: security
Self-clearing alarm raised: No
Severity: Critical
Object Type (class): License
Domain: security
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): License
Domain: security
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): License
Domain: security
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
—
The alarm is raised when the
incoming packet is dropped due to
key chain authentication failure.
Failure could be due to the
following:
•
A send packet did not authorize
the keychain but the receive side
had enabled the keychain.
•
Keychain key ID's did not match.
•
Keychain key digest mismatch.
•
A packet was received with an
invalid enhanced authentication
option length.
•
For other causes of failure refer
to draft-bonica-tcp-auth-05.txt
Choose Help→5620 SAM License
Information to display the 5620 SAM
licence information.
November 2008 3-75