19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CAUTION: In<br />

Follow these steps to investigate <strong>and</strong> attempt to retire the alarm:<br />

On the Main server:<br />

1. Enter display survivable-processor <strong>and</strong> display system-parameters<br />

port-networks to verify that the ESS server is properly administered. An ESS<br />

server must be administered on the Main server before it can register with the Main<br />

server. Record these values for troubleshooting the ESS server.<br />

2. On the SAT, enter ping ip-address board nnn.nnn.nnn.nnn to<br />

verify connectivity between the Main server <strong>and</strong> the ESS, where board is the location<br />

of the C-LAN circuit pack the ESS server is trying to register with <strong>and</strong><br />

nnn.nnn.nnn.nnn is the IP address of the ESS server.<br />

3. Use the display events comm<strong>and</strong> with a category of denial to display denial<br />

events related to ESS. The ESS registration denial events are in the 36xx range. See<br />

ESS Denial Events in <strong>Avaya</strong> Aura Communication Manager Denial Events<br />

(03-602793) for <strong>descriptions</strong> of individual ESS denial events.<br />

4. Use the list trace ras ip-address comm<strong>and</strong> to monitor registration requests<br />

from the ESS. This comm<strong>and</strong> displays registration requests from the ESS server <strong>and</strong><br />

the associated response from the Main server. Note that under normal operation a<br />

Keep-Alive (KA) message is periodically sent from the ESS server to the Main server.<br />

This should not be confused with a registration failure.<br />

5. Firewalls or other security measures may prevent the Main server <strong>and</strong> ESS server<br />

from communicating. Verify that these ports are open through the network between the<br />

Main server <strong>and</strong> the ESS:<br />

● 1719 Registration between the ESS server <strong>and</strong> the Main.<br />

● 21874 Filesync (rsync) between the Main server <strong>and</strong> ESS.<br />

On the ESS server that is not registered:<br />

! CAUTION:<br />

the next steps, be careful to use the Close Window button to cancel out of the<br />

Configure Server page to avoid a reboot of the ESS. Do not Update the<br />

system.<br />

6. Use the bash ping nnn.nnn.nnn.nnn comm<strong>and</strong> to verify connectivity between the<br />

ESS server <strong>and</strong> Main servers, where nnn.nnn.nnn.nnn is the IP address of the<br />

C-LAN in the Main server that the ESS server is trying to register with. To determine<br />

which IP address the ESS server is attempting to register with, enter the Configure<br />

Server comm<strong>and</strong> from the Maintenance Web Interface on the ESS server to display<br />

the configure ESS screen.<br />

7. Firewalls or other security measures may prevent the Main server <strong>and</strong> ESS server<br />

from communicating. Verify that these ports are open through the network between the<br />

Main <strong>and</strong> the ESS:<br />

● 1719 Registration between the ESS server <strong>and</strong> the Main server.<br />

● 21874 Filesync (rsync) between the Main server <strong>and</strong> ESS.<br />

414 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!