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.

Note: Note:<br />

Tip: Customer<br />

Note: It<br />

8. On the Maintenance Web Interface Configure Server pages:<br />

ESS (Enterprise Survivable Server)<br />

● On the Set Identities page, verify that the correct Server ID (SVID) is<br />

entered. This should be a unique value for each server. The SVID must be<br />

between 1 <strong>and</strong> 99. Gaps in the SVIDs for a configuration are allowed (10, 20,<br />

30,...) but the servers may be consecutively numbered if desired. Each server in<br />

the system, duplex or simplex, Main or ESS, requires a unique SVID.<br />

● On the Configure ESS page, verify that the correct platform type is selected <strong>and</strong><br />

the correct C-LAN <strong>and</strong> Main server IP addresses are entered. The ESS server will<br />

use these addresses to establish a connection with the Main server <strong>and</strong> register.<br />

On the Main server, enter display survivable-processor <strong>and</strong> display<br />

system-parameters port-networks to verify that the ESS server is properly<br />

administered. An ESS server must be administered on the Main server before it<br />

can register with the Main server. Record these values for troubleshooting the ESS<br />

server.<br />

● On the Status Summary page, verify that the Cluster ID is correct. Verify that the<br />

individual server IDs are correct.<br />

Note:<br />

The individual server IDs should be the same as those entered on the<br />

Set Identities page of the Configure Server procedure.<br />

9. On the SAT, enter display system-parameters customer-options.<br />

● Verify that the ESS Administration field is set to y.<br />

● Verify that the Enterprise Survivable Server field is set to y.<br />

Tip:<br />

options may only be set with the Communication Manager license file.<br />

If the fields above are incorrect, obtain a new license file with corrected data.<br />

10. From the Maintenance Web Interface, click on the License File comm<strong>and</strong>. Verify<br />

that the license mode is normal.<br />

11. Use the SAT comm<strong>and</strong> status ess clusters to verify that a translation file has<br />

been sent to this ESS. The translation file is only sent after a successful registration. If<br />

a translation file has never been sent, it is an indication of either serious network<br />

connectivity issues or Communication Manager administration <strong>and</strong>/or configuration<br />

<strong>error</strong>s. See above.<br />

Note:<br />

may take several minutes for the ESS server to register with the Main server.<br />

c. Error Type 513: This <strong>error</strong> only applies to an ESS. A socket connection cot be established<br />

between the ESS server <strong>and</strong> an IPSI.<br />

1. On the Maintenance Web Interface, use the ipsiversion comm<strong>and</strong> to verify that all<br />

IPSIs have the current hardware <strong>and</strong> firmware. See the Minimum Firmware/Hardware<br />

Vintages document found at: http://support.avaya.com<br />

Issue 5 May 2009 415

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

Saved successfully!

Ooh no, something went wrong!