Alcatel-Lucent 5620 Troubleshooting Manual page 156

3 — Troubleshooting using network alarms
Alarm
Name: ClientDelegateServerMaxUIExceeded
Type: resourceAlarm (28)
Probable cause:
clientDelegateServerMaxUIExceeded (508)
Name: ClientDelegateServerStatus
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
Name: HostnameMismatch
Type: configurationAlarm (11)
Probable cause: hostnameMismatch (509)
Name: OneWayCommunication
Type: communicationsAlarm (4)
Probable cause: routingConfiguration (510)
Name: TimeMismatch
Type: configurationAlarm (11)
Probable cause: timeMismatch (344)
(2 of 2)
Alarm
Name: AccessInterfaceDown
Type: AccessInterfaceAlarm (32)
Probable cause: interfaceDown (32)
Name: AddressMisconfiguration
Type: configurationAlarm (11)
Probable causes:
•
EpipeBackboneMacAddressMismatch
(444)
•
BVplsSourceMacAddressDuplicate (445)
(1 of 3)
3-114
Attributes
Severity: Warning
Object Type (class):
ClientDelegateServer
Domain: server
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
ClientDelegateServer
Domain: server
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): No
Table 3-64 Domain: service
Attributes
Severity: Critical
Object Type (class): AccessInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the total
number of client GUI sessions on a
client delegate server reaches or
exceeds the configured maximum
value.
The alarm is raised when a client
delegate server is unreachable.
The alarm is raised when an auxiliary
server host name in a 5620 SAM main
server configuration does not match
the host name of the auxiliary server
in the local /etc/hosts file.
The alarm is raised when a 5620 SAM
main server cannot communicate
with an auxiliary server, but the
auxiliary server can communicate
with the main server.
The alarm is raised when the system
time on a 5620 SAM auxiliary server
station differs from the system time
on a main server station.
Additional information
The alarm is raised when an L2 or L3
interface operational state is Down
and the administrative state of the
associated site is Up.
The alarm is not raised against an L2
access interface that is associated
with an MC ring or MC LAG in the
standby state.
The alarm is raised when B-VPLS site
addresses are misconfigured. The
EpipeBackboneMacAddressMismatch
probable cause indicates that the
backbone destination MAC address
does not match the backbone source
MAC address of the site on the
destination NE. The
BVplsSourceMacAddressDuplicate
probable cause indicates that there
are duplicate backbone source MAC
addresses.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4