License Files For Replacement Servers - Avaya ESS User Manual

The Main server was out-of-service and upon reboot, cannot communicate with its
●
reference ISPI: Thirty minutes after any system restart, Communication Manager starts
the first License File audit by attempting to retrieve the previous license file state. If the
previous state cannot be retrieved because of errors, such as, 'Reference IPSI Not
Responding', then the system enters into No-License mode. In No-License mode
administration is denied. Once communication with the reference IPSI is re-established,
the Main server enters into License-Normal mode when:
- The license audit runs (this may take up to one hour).
- A test license command is executed on the Main server's SAT and is completed
successfully.

License files for replacement servers

A new RFA license file is required in the following scenarios:
The Main server has a non-recoverable error and is replaced by an ESS server:
●
- The license files for a Main server and an ESS server are different. The license file for an
ESS server has both the FEAT_ESS and FEAT_ESS_SRV keywords turned on. The
FEAT_ESS keyword identifies this server as an ESS server. To change the ESS server to
a Main server, you must obtain a new RFA license file with the FEAT_ESS_SRV keyword
turned off and the FEAT_ESS keyword turned on.
An existing RFA license must be installed in the following scenario:
The ESS server or Main server has a non-recoverable error and must be replaced with
●
another server of the same type.
- If the same reference IPSI is used for the new server, you do not have to generate a new
RFA license file.The existing RFA license file can be used.
ESS Server License Files
Issue 1.1 June 2005 115