|
|
 |
The Avaya Enterprise Survivable Server (ESS) solution allows a business that is using an Avaya Communication Manager 3.0 driven solution to have greater flexibility of consolidation by providing new survivability options. The ESS solution allows a customer to place ESS (backup) servers at key locations throughout their enterprise. An ESS server is capable of taking over for the entire enterprise or, if needed, just a portion of the enterprise in the event that some type of outage has occurred. |
 |
The ESS solution allows a customer to place ESS (backup) servers at key locations throughout their enterprise. Beginning with Avaya Communication Manager 3.0, an ESS server is capable of taking over for the entire enterprise or, if needed, just a portion of the enterprise in the event that some type of outage has occurred. An enterprise typically involves multiple locations that are equipped with Avaya port network gateways (MCC1, SCC1, CMC, G600 and G650) and/or H.248 media gateways (G700, G350 and G250). These gateways use the Wide Area Network (WAN) in order to communicate with the Main Communication Manager Server. A port network gateway uses a board called the Internet Protocol Server Interface (IPSI) to establish connectivity to the Main server. The IPSI has the ability to "ask for help" if connectivity to the mains server cannot be restored in a defined timeframe. Each IPSI keeps a list of all the available ESS servers in the enterprise. The IPSI will reach out to the ESS server that has the highest priority rating and request service. If that request for service fails, then the IPSI will make a request of the next highest priority server. |
 |
• Enterprises can enhance the survivability of communications by deploying Enterprise Survivable Servers at appropriate points in their network.
• Provides flexibility in how the system to failover. Choose to protect against network failures or catastrophic main server failures or both.
• Easy administration for the customer. Administer translations at one central point with automatic synchronization to all ESS servers.
• Ease of use as ESS provides automatic failover and ability to control system agglomeration.
• Provides survivability for S8500 Media Server.
Enterprise Survivable Server (ESS) provides survivability to an Avaya configuration by allowing backup servers to be placed in various locations in the customer's network. The ESS servers are given administered values that are advertised to each IPSI in the configuration. The IPSI places the ESS server on a priority list based on the administered values. If for any reason, the IPSI can no longer communicate with the Main Server, the IPSI request service from the next highest priority ESS server on its list. The ESS server accepts the request and assumes control of the IPSI controlled Port Network.
In an ESS environment, there is one Main server. The Main server can be a simplex server (S8500/B Media Server) or a duplex server (S87XX series Media Server). If the Main Server is a S8500/B Media Server, all ESS servers in the configuration must also be a S8500/B Media Servers.
Through careful planning and consideration, the S87XX and/or S8500/B Media Servers are placed in various locations in the customer's network. Each ESS server is administered on the Main server. During administration, values are assigned to the ESS server(s). After administration, system translations are synchronized between the Main server and the ESS server(s). Once the ESS server(s) receive the translations, it advertises its values to every IPSI in the configuration, unless it was administered as a Local Only server. Local Only servers only advertise to the IPSIs in their same community.
The IPSIs in the configuration contain a list (called a priority list) of ESS servers. The Main server is always the highest ranking server on an IPSI's priority list. The IPSI prioritizes the ESS servers on its list using the administered values advertised by the ESS server. The priority list is advertised value(s), or loss of communication with an ESS server.
At times, the ESS servers can lose IP connectivity with the IPSIs, which is perfectly normal. An example of when this might occur is during a filesync of updated translations from the Main server to the ESS server. During this period, the IPSIs will adjust their priority list of servers to request service from in the event of an outage. When any ESS server regains IP connectivity to the IPSIs, the IPSIs will again reorder the ESS list as appropriate.
Need Advice? Contact us now to discuss your application requirements. |
|
|
|
