Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1150 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
8. On the Maintenance WEB Interface Configure Server pages:
● Verify on the Set Identities page that the correct Server ID (SVID) is entered.
This should be a unique value for each server. The SVID must be between 1 and 99.
Gaps in the SVIDs for a configuration are allowed (10, 20, 30,...) but the servers may
be consecutively numbered if desired. Each server in the system, duplex or simplex,
Main or ESS, requires a unique SVID.
● Verify on the Configure ESS page that the correct platform type (8700/8710 or
8500) is selected and the correct CLAN and Main IP addresses are entered. The ESS
server will use these addresses to establish a connection with the Main and register.
See step 1
above.
● On the Status Summary page verify that the Cluster ID is correct. Verify that the
individual server IDs are correct.
Note:
Note: Note: The individual server IDs should be the same as entered on the Set
Identities page of the Configure Server procedure.
9. On the SAT execute the display system-parameters customer-options
command.
● Verify that the ESS Administration field is set to y.
● Verify that the Enterprise Survivable Server field is set to y.
Tip:
Tip: Customer options may only be set with the Avaya license file. If the fields above
are incorrect obtain a new license file with corrected data.
10. From the Maintenance Web Interface:
● Click on the License File command. Verify that the license mode is normal.
11. Use the SAT command status ess clusters to verify that a translation file has been
sent to this ESS. The translation file is only sent after a successful registration. If a
translation file has never been sent it is an indication of either serious network
connectivity issues or Avaya Communication Manager administration and/or
configuration errors. See above.
Note:
Note: It may take several minutes for the ESS server to register with the Main.
c. Error Type 513: This error only applies to an ESS.
When a socket connection can not be established between the ESS server and an IPSI, this
error is generated and logged.
Follow these steps to investigate and attempt to retire the alarm:
1. On the Maintenance Web Interface use the ipsiversion command to verify that all
IPSIs have the current hardware and firmware. See the Minimum Firmware/Hardware
Vintages document found at: http://support.avaya.com .