Maintenance
170 Avaya Enterprise Survivable Servers (ESS) Users Guide
4. Now, suppose the ESS server is incorrectly administered on the Main server. In this
example, the ESS server is configured (via the Configure Identities page of Configure
Server) to have Server ID 98, but it is administered (via the SAT command change
system-parameters ess) to have Server ID 97 on the Main server.
From the Main server:
Figure 53: Troubleshooting - mis-administration - Main server perspective
Notice that on the Main server a denial event occurs when the ESS server attempts to register.
Denial events can be displayed using the display events command. Briefly, the denial
events associated with ESS server are:
● 3600: IP RRJ-ESS not admin - The ESS server attempting to register does not match any
of the administered ESS servers in translations.
● 3601: IP RRJ-ESS obj not init - The FEAT_ESS feature bit is not turned on in the license
file.
● 3602: IP RRJ-ESS bad SID sent - The ESS server sent a SID that does not match that of
the Main server. The SID is set by the license file.
From the ESS server:
Figure 54: Troubleshooting - mis-administration - ESS server perspective
Notice that the ESS server sends a Registration Request (RRQ) but only receives a
Registration Rejection (RRJ) from the Main server.
list trace ras ip-address 135.9.78.143 Page 1
LIST TRACE
time data
12:47:42 rcv RRQ endpt 135.9.78.143:1719 switch 135.9.72.168:1719 ext
12:47:42 denial event 3600: IP RRJ-ESS not admin endpt 135.9.78.143 data0:0x0
12:47:42 snd RRJ endpt 135.9.78.143:1719 switch 135.9.72.168:1719 ext
list trace ras ip-address 135.9.72.168 Page 1
LIST TRACE
time data
12:47:42 snd RRQ endpt 135.9.72.168:1719 switch 135.9.78.143:1719 ext
12:47:42 rcv RRJ endpt 135.9.72.168:1719 switch 135.9.78.143:1719 ext
To Next Page
Loading...
Need help?
General
