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.

Resolution:<br />

1. Log on to the System Management Interface.<br />

2. Click the Administration tab <strong>and</strong> select Server (Maintenance).<br />

3. On the left navigation menu, click Status Summary. The Status Summary screen<br />

appears.<br />

4. Verify that the other server in the duplicated server pair is running <strong>and</strong> that the Processor<br />

Ethernet status is not Down.<br />

● If the other server in the duplicated server pair is not running, the status of Mode is Not<br />

Ready <strong>and</strong> the display of items such as "Alarms" are blank.<br />

● If he Processor Ethernet status is not Down, run the troubleshooting procedures for<br />

the alarms on the other server.<br />

For more information about the troubleshooting procedures, see <strong>Avaya</strong> Aura<br />

Communication Manager Server Alarms, (03-602798).<br />

5. Execute the Ping diagnostic <strong>test</strong> to verify that the other server responds to a ping <strong>test</strong>. If it<br />

does not, execute the Ping diagnostics <strong>test</strong> from the other server to verify that it is<br />

connected to the corporate LAN.<br />

_PE 3 Major alarm - Processor Ethernet service is down<br />

MO name in log Alarm level Alarm text Description<br />

_PE 3 MAJ Can't ping the<br />

device used<br />

for the PE<br />

Health Check<br />

or the IP<br />

interface used<br />

for the PE on<br />

the other<br />

server.<br />

Resolution:<br />

1. Run the <strong>test</strong>s listed for the alarms associated with _PE 1 <strong>and</strong> _PE 2.<br />

2. Verify if that the server is connected to the corporate LAN.<br />

3. If NIC alarms are present, follow the troubleshooting procedures for those alarms. For<br />

more information, see Verify NIC Options Test (#1511) on page 1679.<br />

4. Verify that the corporate LAN is working.<br />

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

Processor Ethernet<br />

service is down.<br />

Cannot ping the PE<br />

Health Check<br />

device <strong>and</strong> the IP<br />

interface used for<br />

the PE on the other<br />

server.

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

Saved successfully!

Ooh no, something went wrong!