Ess Prerequisites; License Files; Module Id; Server Id - Avaya ESS User Manual

ESS Design and Planning

ESS prerequisites

Detailed planning for the ESS is mandatory. Certain information must be gathered to facilitate
the implementation of this feature:
IP address(es): Obtain the following IP address(es):
●
- Main server(s)
- ESS server(s)
- CLAN board(s)
- Default gateway(s)
- Control network
- NIC card(s)
- IPSI(s)
- Subnet mask(s)
Note:
For a more complete list of addresses, see
Note:
page 93.
The IP addresses listed above are used when configuring the Main server(s) and the ESS
server(s). For more information on configuring and administering the Main server(s) and the
ESS server(s) see,
Server ID: The system administrator assigns a unique Server Identification number (SVID)
●
to each server. The SVID must be in the range of 1 to 99. Each server in a server pair
(S8700 series media servers) requires a different SVID. Each SVID must be unique within
the enterprise. The administrator can assign the SVID sequentially or allow gaps in the
numbering such as 10, 20, 30, etc.
License files: The Main server and each ESS server requires its own license file. For
●
security purposes, RFA requires that each license file have a unique serial number. Prior
to ESS, the serial number of one reference IPSI was used for the entire enterprise. For an
ESS implementation, each license file for an ESS server and a Main server(s) must have a
unique serial number from a separate reference IPSI. For more information on ESS
license files see,
Module Identification Number (MID): This is a unique value assigned by RFA and found
●
in each license file. The MID is administered as the Cluster Identification Number (CLID) in
the system-parameters ess form. To find the MID for an ESS server use the
instructions in step 2 of,
64 Avaya Enterprise Survivable Servers (ESS) Users Guide
Administering ESS
ESS Server License Files
Administering ESS
ESS Installation Checklist
on page 122.
on page 110.
on page 122.
on