09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

IPSI Interchange (Duplicated IPSIs)<br />

IPSV-CTL (IP <strong>Server</strong> Interface Control)<br />

Software will take action upon any fault that affects the IPSI and attempt to interchange to the<br />

healthier IPSI. In addition, when neither IPSI is completely healthy to provide clock, packet<br />

interface and archangel, one IPSI will be chosen to be the clock, and the archangel will move to<br />

the EI. Moving the archangel’s functionality to the EI requires another port network to have a<br />

healthy IPSI, and this port network to have an EI. The exact order of action taken will vary<br />

depending on the fault being processed, as well as the existing state of health (SOH) of the<br />

IPSIs in the PN. An IPSI interchange (if necessary) will always happen before a control change<br />

(moving of the archangel to/from IPSI/EI). If both IPSIs are equally healthy, software<br />

preferentially migrates to the A-side IPSI. However, this preferential migration is not done if craft<br />

has set to a B-side IPSI.<br />

Craft can also demand an interchange of IPSIs in one or every PN. The command set<br />

ipserver-interface Uc interchanges a specific IPSI. In addition, set<br />

ipserver-interface a-all | b-all can be used to interchange every IPSI in the<br />

system to the A-side or B-side respectively. This is particularly useful if preparing for a<br />

control-network outage. For a planned interchange of IPSIs, the following steps occur. The:<br />

1. Going active IPSI is marked as active, the going standby is marked as standby.<br />

2. Tone-Clock is migrated. This includes tone generation as well as TDM clock.<br />

3. Archangel is migrated to the newly active IPSI.<br />

4. PKT-INT on the newly active IPSI is made active. Every link is migrated between IPSIs.<br />

See Table 247: Error codes for set ipserver-interface for ABORT/FAIL codes associated with<br />

set ipserver-interface:<br />

Table 247: Error codes for set ipserver-interface<br />

Error<br />

Code<br />

Command<br />

Result<br />

Description<br />

2343 ABORT Interchange not permitted. The anti-thrashing timer has not yet<br />

expired.<br />

1. Retry command in 30 seconds.<br />

2338 FAIL The SOH of the set-to IPSI is bad. Use list ipserver-interface<br />

to display the current IPSI’s SOH.<br />

2341 FAIL An error occurred during the interchange. This indicates an internal<br />

problem. Use list ipserver-interface to see if the interchange<br />

actually occurred.<br />

2342 FAIL The set-to IPSI has been busied out.<br />

1. Run release ipserver-interface Uc.<br />

PASS The interchange was successful, or the set to IPSI was already active.<br />

If set to a B-side IPSI, it will be marked as “craft set” and will not<br />

preference switch back to the A-side by software.<br />

Communication Manager Release 5.0 Issue 4 January 2008 905

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

Saved successfully!

Ooh no, something went wrong!