Avaya 555-245-600 사용자 설명서
Reliability and Recovery
270 Avaya Application Solutions IP Telephony Deployment Guide
ESS System Capacities
ESS can be administered as “local only” or as an “enterprise-wide” survivable server(s). When
administered as “Local only”, which indicates it will act as the survivable server for a community
or a subset of port networks, up to 63 ESS server clusters can be configured as ESS. This way
the customer may configure some ESSs to serve only a few port networks in order to enable
localization of failover where desired.
For enterprise-wide fail-over coverage, up to 7 ESS server clusters can be administered. The
ESS which acts as a main server is called System Preferred ESS, and it must have the same
capacity as the original main. For example when an S8500 Server is the System Preferred ESS
to S8700/S8710 main server, it will be configured to have the same capacities as the S8700/
S8710 Servers. This can be done based on its license files.
Depending on the type of failure and how the ESS servers are configured, an individual ESS
server may accept control of all port networks, several port networks, a single port network, or
no port networks. When a LAN or WAN failure occurs in configurations where port networks are
widely dispersed, multiple ESS servers may be required to collectively accept control with each
ESS server controlling some portion of the set of port networks.
When an ESS server accepts control, it communicates directly with each MCC1, CMC1, SCC1,
G600, or G650 Media Gateway through the gateway’s IPSI board. In ATM PNC configuration,
the ESS server can also control non-IPSI controlled port networks through an Expansion
Interface board. The ESS server communicates indirectly with each G250, G350, or G700
Media Gateway through CLAN connections in the port networks.
Stable calls remain up in the same state as they were before the outage occurred. The stable
calls do not have access to any features such as hold, conference, etc. The state of the stable
call cannot be changed.
administered as “Local only”, which indicates it will act as the survivable server for a community
or a subset of port networks, up to 63 ESS server clusters can be configured as ESS. This way
the customer may configure some ESSs to serve only a few port networks in order to enable
localization of failover where desired.
For enterprise-wide fail-over coverage, up to 7 ESS server clusters can be administered. The
ESS which acts as a main server is called System Preferred ESS, and it must have the same
capacity as the original main. For example when an S8500 Server is the System Preferred ESS
to S8700/S8710 main server, it will be configured to have the same capacities as the S8700/
S8710 Servers. This can be done based on its license files.
Depending on the type of failure and how the ESS servers are configured, an individual ESS
server may accept control of all port networks, several port networks, a single port network, or
no port networks. When a LAN or WAN failure occurs in configurations where port networks are
widely dispersed, multiple ESS servers may be required to collectively accept control with each
ESS server controlling some portion of the set of port networks.
When an ESS server accepts control, it communicates directly with each MCC1, CMC1, SCC1,
G600, or G650 Media Gateway through the gateway’s IPSI board. In ATM PNC configuration,
the ESS server can also control non-IPSI controlled port networks through an Expansion
Interface board. The ESS server communicates indirectly with each G250, G350, or G700
Media Gateway through CLAN connections in the port networks.
Stable calls remain up in the same state as they were before the outage occurred. The stable
calls do not have access to any features such as hold, conference, etc. The state of the stable
call cannot be changed.
ESS and H.248 Media Gateways
The H.248 G700/G350/G250/G150 Media Gateways are not directly supported by the ESS
feature. In the event of a failure they may re-register to ESS(s) through CLAN contained in port
network which has requested an ESS, or they have the option of re-registering to an LSP.
feature. In the event of a failure they may re-register to ESS(s) through CLAN contained in port
network which has requested an ESS, or they have the option of re-registering to an LSP.
ESS and Adjunct Survivability
Most adjuncts register with CLAN, which in the event of failure will follow the port network IPSI
to an ESS. If the port network containing the CLAN cannot get service from an ESS, then the
adjunct will not be survivable. Having CLAN in IPSI connected port networks will give the
adjunct higher probability of survival.
to an ESS. If the port network containing the CLAN cannot get service from an ESS, then the
adjunct will not be survivable. Having CLAN in IPSI connected port networks will give the
adjunct higher probability of survival.