Alcatel-Lucent 5620 - Page 156

3 — Troubleshooting using network alarms
3-114 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 3-64 Domain: service
Name: ClientDelegateServerMaxUIExceeded
Type: resourceAlarm (28)
Probable cause:
clientDelegateServerMaxUIExceeded (508)
Severity: Warning
Object Type (class):
ClientDelegateServer
Domain: server
Implicitly cleared (self-clearing): Yes
The alarm is raised when the total
number of client GUI sessions on a
client delegate server reaches or
exceeds the configured maximum
value.
Name: ClientDelegateServerStatus
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
Severity: Critical
Object Type (class):
ClientDelegateServer
Domain: server
Implicitly cleared (self-clearing): Yes
The alarm is raised when a client
delegate server is unreachable.
Name: HostnameMismatch
Type: configurationAlarm (11)
Probable cause: hostnameMismatch (509)
Severity: Critical
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): No
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.
Name: OneWayCommunication
Type: communicationsAlarm (4)
Probable cause: routingConfiguration (510)
Severity: Major
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): Yes
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.
Name: TimeMismatch
Type: configurationAlarm (11)
Probable cause: timeMismatch (344)
Severity: Major
Object Type (class): AuxiliaryServer
Domain: server
Implicitly cleared (self-clearing): No
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.
Alarm Attributes Additional information
Name: AccessInterfaceDown
Type: AccessInterfaceAlarm (32)
Probable cause: interfaceDown (32)
Severity: Critical
Object Type (class): AccessInterface
Domain: service
Implicitly cleared (self-clearing): Yes
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.
Name: AddressMisconfiguration
Type: configurationAlarm (11)
Probable causes:
• EpipeBackboneMacAddressMismatch
(444)
• BVplsSourceMacAddressDuplicate (445)
Severity: Major
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
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.
(1 of 3)
Alarm Attributes Additional information
(2 of 2)
Aug 2010
AAAD
8.0 R4