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.

If the Expansion Archangel Link (EAL) is recovered quickly, the PN Warm Restart returns the<br />

PN to service with minimal effects on user service. If the EAL cot be recovered quickly, the PN is<br />

taken out of service <strong>and</strong> a PN Reset Level 2 (PN Cold Restart) is required to return it to service.<br />

PN Cold Restarts<br />

If the server-to-PN link has failed <strong>and</strong> has not been recovered within 30 seconds, the PN is<br />

taken out of service <strong>and</strong> can be brought back into service only with a PN Reset Level 2 (PN<br />

Cold Restart). Effects of a PN Cold Restart include a reset of every circuit pack in the PN <strong>and</strong><br />

the disconnection of every call to or from the PN. Calls with both endpoints within the PN are<br />

dropped upon recovery.<br />

PN Restart Escalation<br />

PN restarts follow an escalation strategy controlled by maintenance software. Whenever a<br />

request for a PN Reset Level 1 (PN Warm Restart) is made, software checks to see if the restart<br />

should be escalated to a PN Reset Level 2 (PN Cold Restart). If any of the following are true,<br />

the restart is escalated:<br />

● At least two level 1 restarts have occurred <strong>and</strong> less than 30 minutes has elapsed since the<br />

last occurrence.<br />

● Current PN conditions do not allow a level 1 restart, such as when the PN is out of service.<br />

● Less than 3 minutes has elapsed since the last PN Cold Restart, indicating that the PN is<br />

unstable.<br />

If two PN Cold Restarts have been executed in less than an hour <strong>and</strong> the link is functional, but<br />

the PN has not recovered to an in-service state, a MAJOR alarm is raised against EXP-PN, <strong>and</strong><br />

the PN is put into Emergency Transfer by system software. (Software can invoke PN<br />

Emergency Transfer only when the link to the PN is up. If the link is down, the hardware<br />

automatically invokes Emergency Transfer 1 minute after it detects a link failure).<br />

Connectivity Alarming<br />

When a PN is out of service, a MAJOR EXP-PN alarm is raised against that PN. A PN can only<br />

be alarmed if it is out of service <strong>and</strong> the fiber between the server <strong>and</strong> the PN is up.<br />

For ATM, a Port Network can only be alarmed if it is out of service <strong>and</strong> the connections to the<br />

server, the ATM switch, <strong>and</strong> the EPN are up. If the connection from the server to the ATM switch<br />

is down (by removing it from administration, for example), every Port Network is lost but not<br />

alarmed, since they are not the cause of the problem.<br />

452 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!