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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 104: ESS Error Log Entries 2 of 2<br />

Notes:<br />

a. Error Type 1: This <strong>error</strong> only applies to an ESS. An ESS server has become the master of<br />

an IPSI Port Network.<br />

Investigate <strong>and</strong> attempt to retire the alarm with the following steps:<br />

1. <strong>Avaya</strong> Fault <strong>and</strong> Performance Management can be used to obtain a network view of<br />

the Enterprise Survivable Server configuration. Note any network fragmentation or<br />

server outages (Main or ESS).<br />

2. Use the SAT comm<strong>and</strong> status ess port-network to identify which ESS Cluster<br />

IDs each Port Network (IPSI) is connected to. This comm<strong>and</strong> may be executed on<br />

either a Main server or ESS. With a fragmented network, it may be necessary to<br />

execute this comm<strong>and</strong> on each server in the system configuration to acquire a<br />

complete view of IPSI connectivity.<br />

3. Using either <strong>Avaya</strong> Fault <strong>and</strong> Performance Management or SAT sessions to each<br />

server, determine the extent of any server or network outages.<br />

4. Resolve any server outages. If possible, bring the Main server(s) back online first.<br />

Note: Bringing<br />

Error<br />

Type<br />

Aux<br />

Data<br />

Associated Test Alarm<br />

Level<br />

On/Off<br />

Board<br />

Recommended Action<br />

513 (c) None MIN OFF Connection not established between<br />

ESS server <strong>and</strong> IPSI. Resolve any<br />

ESS server <strong>and</strong>/or network problems.<br />

Use the PING comm<strong>and</strong> to verify<br />

connectivity to IPSI circuit packs.<br />

769 (d) None MIN OFF This alarm is raised when a main<br />

server has administration for a<br />

duplicated ESS that is missing the<br />

Server A IP address.<br />

Typically, this alarm is raised after an<br />

upgrade from a pre-CM 5.2 Release<br />

to a CM 5.2 or later Release.<br />

To retire the alarm, use the change<br />

survivable-processor comm<strong>and</strong><br />

to administer the Server A IP address<br />

for each Duplicated ESS.<br />

Note:<br />

a Main server back online will not cause Port Networks to immediately<br />

switch back to it. Restoring Port Network control to a Main server in a stable<br />

network requires proactive interaction. See step 7 below.<br />

5. Resolve network fragmentation <strong>and</strong> outage issues per local practice.<br />

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

2 of 2

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

Saved successfully!

Ooh no, something went wrong!