Server Alarms - Avaya Support

Table 5: ARB Alarms 5 of 10
Event
ID
9
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
ARB (Arbiter)
WRN The following is a sample string pair generated by ARB Event #9. Within
this sample, four pairs of digits in each string have special meaning, and
are labeled “aa” through “dd.”
aa bb cc dd
↓↓ ↓↓ ↓↓ ↓↓
●
gmm 0700, pcd 00/00, dup 270, wd 81, actv 004
gmm 0700, pcd 06/06, dup 370, wd 01, actv 014
For “aa,” any value other than “00” indicates a hardware problem.
(For example, the value “20” is common for a power failure.)
In the above example, neither server had hardware trouble.
● “bb” and “cc”: Here, "bb" indicates the number of IPSI’d PNs that the
server in question controls (if active) or is prepared to control (if
standby), and "cc" indicates the number of connections to PNs with
IPSIs. For non-ESS servers, different values within the same string
indicate a problem with controlling one or more IPSI-connected PNs.
A PN reset can cause both server’s strings to reflect equally degraded
health, but that event (in itself) should not trigger a server interchange.
● For “dd,” any value other than “01” indicates a failed software
process. (More precisely, a certain value indicates a problem with a
discrete portion of the platform’s process set, including:
- “21” for a Linux daemon (for example, “atd”, “httpd”, “inetd”, or
“xntpd”)
- “41” for a platform service (for example, “dbgserv”, “prune”, or
“syslog”)
- “81” for reloaded Communication Manager software, as in the
previous sample
5 of 10
Communication Manager Release 5.0 Issue 4 January 2008 45