1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Server
  5. ESS
  6. User manual

Avaya ESS User Manual

Enterprise survivable servers
Hide thumbs
Table of Contents

Advertisement

Quick Links

Avaya Enterprise Survivable
Servers (ESS) User Guide
03-300428
Issue 1.1
June 2005

Advertisement

Table of Contents
loading

Related Manuals for Avaya ESS

Summary of Contents for Avaya ESS

  • Page 1 Avaya Enterprise Survivable Servers (ESS) User Guide 03-300428 Issue 1.1 June 2005...
  • Page 2 • System administration documents Warranty • Security documents Avaya Inc. provides a limited warranty on this product. Refer to your • Hardware-/software-based security tools sales agreement to establish the terms of the limited warranty. In • Shared information between you and your peers addition, Avaya’s standard warranty language as well as information...
  • Page 3 • A reorder tone is received. 04DU9-IKN 6.0Y RJ48C Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use of 04DU9-ISN 6.0Y RJ48C access codes. Modification of this equipment by call aggregators to block...
  • Page 4 Contact the state public utility commission, public service E-mail: totalware@gwsmail.com commission or corporation commission for information. For the most current versions of documentation, go to the Avaya support This equipment, if it uses a telephone receiver, is hearing aid compatible. Web site: http://www.avaya.com/support.

  • Page 5: Table Of Contents

    Failover to an ESS server ......LSP and ESS ........

  • Page 6: Synchronization

    Chapter 2: ESS Design and Planning ....ESS design strategy ........

  • Page 7: Serial Numbers

    After the ESS server is configured ......Administering ESS........

  • Page 8: Alarming

    Error Codes..status ess clusters ....... .
  • Page 9 Acceptance criteria ....... . Enable an ESS server from the Main server .....
  • Page 10 Contents 10 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 11: About This Book

    Downloading this book and updates from the Web You can download the latest version of this book from the Avaya web site. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.

  • Page 12: Downloading This Book

    Survivable Servers in the search box and hit enter. A list of documents appear matching the search. 3. Look for the Avaya Enterprise Survivable Servers User Guide on the list. Click on the title of the book to download. Conventions This section describes the conventions used in this book.

  • Page 13: User Input

    Trademarks All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Trademarks and Service Marks The following are trademarks or registered trademarks of Avaya: ®...
  • Page 14 ● ® PictureTel (registered trademark of PictureTel Corporation) ● ® ProShare (registered trademark of Intel Corporation) ● ® UNIX (trademark of the Novell Corporation) ● Zydacron (registration pending for Zydacron Corporation) ● 14 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 15: Technical Assistance

    Maintenance and repair, call the Avaya National Customer Care Support Line at ● 1-800-242-2121 Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353 ● International For all international resources, contact your local Avaya authorized dealer for additional help. Issue 1.1 June 2005...

  • Page 16: Sending Us Comments

    E-mail: send your comments to: ● document@avaya.com Fax: send your comments to: ● 1-303-538-1741 Be sure that you mention the name, number, and issue of this book, Avaya Enterprise Survivable Server (ESS) User Guide, 03-300428. 16 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 17: Chapter 1: Ess Overview

    (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 requests service from the next highest priority ESS server on its list.

  • Page 18: Detailed Ess Overview

    Main server, or the controlling ESS server. The interval from when the no service timer actives, to the time the IPSI requests service of an ESS server, is called the no service time out interval. The value for the no service timer is administrable from three to 15 minutes, with a default of five minutes.

  • Page 19: Failover To An Ess Server

    Existing Communication Manager recovery mechanisms still occur prior to any failover to an ESS server. For example, if a Main server loses control of a majority of Port Networks it may attempt to switch to its standby server. This would happen before an IPSI would request service from an ESS server.
  • Page 20 ESS Overview As part of a failover, the ESS resets the Port Networks that it now controls. The Port Network preforms a restart. During a restart: Every call is dropped ● Administrative sessions are dropped ● Every application and system link is dropped and re-established ●...

  • Page 21: Lsp And Ess

    CMC1, G600, and G650 Media Gateways and has less capacity then an ESS server. In an ESS environment, the IPSI contains a priority list of ESS servers. If for any reason, the communication between the IPSI and the Main server is lost, the IPSI requests service from the highest ranking ESS server on its list.

  • Page 22: Ess Requirements

    The Main server(s) can either be an S8500 Media Server, or an S8700 series media ● server. If the Main server is an S8500 Media Server, all ESS servers must be S8500 Media Servers. Minimum vintage IPSI firmware: To identify the firmware needed for an IPSI in an ESS ●...

  • Page 23: Ess Failover Examples

    Main server, an S8700 Media Server has been selected as the primary backup to the Main server. An S8500 Media Server is acting as a secondary backup in case of an S8700 ESS server failure or WAN fragmentation. The intent of the ESS configuration for Example 1 is to keep all Port Networks under the control of a single server.
  • Page 24 ESS Overview Figure 1: S8710 Media Server with ESS servers in normal operation S8710 Media Server (Main Server) disc COMPACT disc COMPACT S8700 ESS Server (1st Alternative) S8500 ESS Server (2nd Alternative) disc PN #1 PN #4 PN #5 PN #8...
  • Page 25 S8500 ESS server. The administered values of the ESS servers were advertised to the IPSIs in the configuration. Based on the values of the ESS servers, the IPSI places the S8700 ESS server higher on its priority list then the S8500 ESS server.
  • Page 26 Figure 3), the IPSIs request service from the highest ESS server on its list (S8700 ESS server). The S8700 ESS server acknowledges the request and takes control of the IPSI controlled Port Networks. Figure 3: Main servers fail- ESS recovery of failure...

  • Page 27: Example 2: Network Failure

    S8500 ESS server, but can no longer communicate with the Main server or the S8700 ESS server. Port Networks 5 through 8 can still communicate with the S8700 ESS server but can no longer communicate with the S8500 ESS server.
  • Page 28 Port Network Control Link (EAL) CSS / EI (Fiber) IP Connection into Control Network ATM / ATM-EI (Fiber) Server or Network Failure Dup Link VoIP Path Out of Service DSIC LInk cycmnff KLC 031505 28 Avaya Enterprise Survivable Servers (ESS) Users Guide...
  • Page 29 Because the IPSIs in Port Networks 1 through 4 cannot communicate with the Main server or the S8700 ESS server, they adjust their priority list and move the S8500 ESS server to the top of the list. The no service timer activates for Port Networks 1 through 4. When the no service timer expires, the IPSIs in Port Networks 1 through 4 request service from the S8500 ESS server.
  • Page 30 6). As the network failure is fixed, the IPSIs in Port Network 1 through 4 can now communicate with the S8700 ESS server. The IPSI priority list adjusts to reflect the S8700 ESS server as the highest priority ESS server. Even though the IPSI priority list now shows the S8700 ESS server as its highest priority ESS server, the Port Networks do not automatically return to the control of the S8700 ESS server.
  • Page 31 ESS failover examples Figure 6: Network fragmentation recovery S8710 Media Server (Main Server) disc COMPACT disc COMPACT S8700 ESS Server (1st Alternative) S8500 ESS Server (2nd Alternative) disc PN #1 PN #4 PN #5 PN #8 PN #2 PN #3...
  • Page 32 The Main server has been restored (see Figure 7). All IPSIs in each Port Network can now communicate with the Main server and each ESS server. The Main server is always the highest priority on any IPSI priority list. Figure 7: Main server recovery...
  • Page 33 ESS failover examples The customer is now ready to have the Main server control the configuration (see Figure Moving the Port Networks back to the control of the Main server can be accomplished by: Moving each Port Network individually using the get forced-takeover ●...
  • Page 34 Port Network Control Link (EAL) CSS / EI (Fiber) IP Connection into Control Network ATM / ATM-EI (Fiber) Server or Network Failure Dup Link VoIP Path Out of Service DSIC LInk cycmsrv3 KLC 031505 34 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 35: Example 3: Combined Ip Connected Port Networks With Css Or Atm Connected Port Networks

    ESS failover examples Example 3: Combined IP connected Port Networks with CSS or ATM connected Port Networks In Communication Manager 3.0 and later releases, mixed configurations that combine IP-connected Port Networks with CSS-connected, or ATM-connected Port Networks are supported. Additionally, Communication Manager 3.0 and later releases allow media servers to support both single control networks and duplicated control networks in the same configuration, as well as single bearer networks and duplicated bearer networks.
  • Page 36 10). Port Networks 4 and 5 can no longer communicate with the Main server but can still communicate with the S8500 ESS server. The no service timer activates for IPSIs in Port Networks 4 and 5. After the no service timer expires, the IPSIs in Port Networks 4 and 5 request service from the S8500 ESS server.
  • Page 37 ESS failover examples The system is now fragmented between two controlling servers. Some functionality provided by adjuncts may be missing for users in Port Networks 4 and ● 5. See Feature considerations on page 88 for more information on adjuncts.

  • Page 38: Example 4: Ess With Center Stage Switch (Css)

    Example 4: ESS with Center Stage Switch (CSS) ESS requires that all survivable Port Networks in a CSS environment, connect to the network using an IP Media Processor board. The following must be considered for an ESS in a CSS environment: ESS requires that all Port Networks within a CSS environment must have the ability to ●...
  • Page 39 ESS failover examples Figure 11: Normal operation CSS with single ESS server S8710 Media Server (Main Server) disc COMPACT S8500 ESS Server (1st Alternative) disc COMPACT disc PN #5 PN #4 PN #1 PN #2 PN #3 PN #2 does not...
  • Page 40 Networks can no longer communicate with the Main server. The IPSIs in Port Networks 1, 3, 4, and 5, request service from the S8500 ESS server after the no service timer expires. ESS does not utilize CSS, therefore Port Network 2 and the CCS located in Port Network 3 is out-of-service.

  • Page 41: Example 5: Css With Ds1C

    ESS failover examples Example 5: CSS with DS1C In example 5, Port Network 4 is remotely connected to the CSS using a DS1C. Port Network 4 is equipped with Public Switched Telephone Network resources. There is an IPSI board in each Port Network.
  • Page 42 (see Figure 14). Note: If only the DS1C link was lost, Port Network 4 would not transition to the ESS Note: server. Communication between the DS1C location and the main location would be disrupted since there is no bearer path.
  • Page 43 ESS failover examples Figure 14: CSS with DS1C - remote takeover S8710 Media Server (Main Server) disc COMPACT S8500 ESS Server (1st Alternative) disc COMPACT disc Remote site becomes isolated PN #1 PN #4 PSTN resources in Remote PN provides service...

  • Page 44: Example 6: Css With Multiple Nodes

    Port Network Control Link (EAL) CSS / EI (Fiber) IP Connection into Control Network ATM / ATM-EI (Fiber) Server or Network Failure Dup Link VoIP Path Out of Service DSIC LInk cycmcss5 KLC 031505 44 Avaya Enterprise Survivable Servers (ESS) Users Guide...
  • Page 45 IPSI in Port Network 4 and Port Network 6 request, and receive service from the S8700 ESS server. The ESS server cannot take control of the CSS node in Port Network 4. The CSS node in Port Network 4 is not utilized. Port Network 5 is also not utilized as it does not have an IPSI and can no longer communicate with the CSS node in Port Network 4.
  • Page 46 Port Network Control Link (EAL) CSS / EI (Fiber) IP Connection into Control Network ATM / ATM-EI (Fiber) Server or Network Failure Dup Link VoIP Path Out of Service DSIC LInk cycmcss6 KLC 031505 46 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 47: Example 7: Ess With Atm

    17), there is a single ESS server in an ATM configuration. The S8710 is the Main server with the S8500 Media Server as the ESS server. IPSIs are installed in all Port Networks except for Port Network 2 and Port Network 5.
  • Page 48 ESS Overview Figure 17: ATM with a single ESS server in normal operation S8710 Media Server (Main Server) disc COMPACT S8500 ESS Server (1st Alternative) disc COMPACT disc PN #1 PN #6 PN #2 PN #5 PN #3 PN #4...

  • Page 49: Atm - Single Ess Takeover Examples

    The IPSIs request service of the S8500 Media Server after the no service timer expires. The S8500 Media Server assumes control of Port Network 1, 3, 4, and 5. Once the S8500 ESS server assumes control of the Port Network, it will attempt to take over all other Port Networks in the system through the ATM Expansion Interface (EI) board (TN2305B or TN2306B).
  • Page 50 The IPSIs in Port Network 4 and Port Network 5 can no longer communicate with the Main server. The no service timer activates. When the no service timer expires the IPSIs in Port Networks 4 and 5 request service from the S8500 ESS server. 50 Avaya Enterprise Survivable Servers (ESS) Users Guide...
  • Page 51 ESS failover examples In order for an ESS server to control a PN without an IPSI, such as PN5, the ESS server must first control a PN with an IPSI. Once the ESS server controls a Port Network with an IPSI the ESS server may then attempt to communicate with and possibly control a non-IPSI PN through the ATM network.

  • Page 52: Example 8: Distributed Atm Switches

    In example 8 (see Figure 20), there is a single ESS server with multiple ATM nodes. Port Network 2 connects using an ATM Expansion Interface board, to the ATM node on the left side of the following figure and does not have an IPSI. Port Network 5 connects using an ATM EI board, to the ATM node on the right side of the following figure and also does not have an IPSI.
  • Page 53 Main server continues to provide service to Port Networks 1 through 3 with no service interruption. The IPSIs in Port Network 4 and 6 requests service of the S8700 ESS server after the no service timer expires. The S8700 ESS server assumes control of Port Network 4 first.
  • Page 54 ESS Overview Once in control on Port Network 4, the ESS server assumes control of Port Network 5 through the EI board. Figure 21: ATM, single ESS server, multiple nodes in a takeover scenario S8710 Media Server S8700 ESS Server...

  • Page 55: Example 9: Lsps Working In An Ess Environment

    There are two ESS servers administered. The S8700 ESS server has the highest priority and is the first ESS the IPSI’s request service from if they can no longer communicate with the Main server. If the IPSI can no longer communicate with either the Main server or the S8700 ESS server, they will request service from the S8500 ESS server.
  • Page 56 ESS Overview Figure 22: LSP working in an ESS environment - normal operation S8710 Media Server S8700 ESS Server (Main Server) (1st Alternative) disc COMPACT S8500 ESS Server (2nd Alternative) disc COMPACT disc S8300 LSP G350 PN #1 PN #4...
  • Page 57 ESS failover examples In an ESS environment, a no service timer activates when the IPSI can no longer communicate with the Main server or controlling ESS server. The no service timer is administrable and can be set from 3 to 15 minutes.
  • Page 58 ESS Overview Figure 23: LSP working in an ESS environment - ESS timer before Link Recovery timer S8710 Media Server S8700 ESS Server (Main Server) (1st Alternative) disc COMPACT S8500 ESS Server (2nd Alternative) disc COMPACT disc S8300 LSP G350...
  • Page 59 Using a different scenario, in Figure 24 the Link Recovery timers expired before the ESS no service timer. The IP telephones and G350 Media Gateway connect with the alternate gatekeeper, in this case the LSP. The no service timer expires and the IPSIs in Port Networks 1 through 8 request service from the S8700 ESS server.
  • Page 60 ESS Overview Figure 24: LSP working in an ESS environment - Link Recovery timer before ESS timer S8710 Media Server S8700 ESS Server (Main Server) (1st Alternative) disc COMPACT S8500 ESS Server (2nd Alternative) disc COMPACT disc S8300 LSP G350...
  • Page 61 Primary feature is not being used (as shown in Figure 25), a manual reset must be performed on the G350. Figure 25: LSP working in an ESS environment - fall-back to the Main server S8710 Media Server S8700 ESS Server (Main Server)
  • Page 62 ESS Overview 62 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 63: Chapter 2: Ess Design And Planning

    During initial design, and whenever additional capacity is added, these priorities should be taken into account. Once a plan is developed to allow an ESS server to take control of a configuration, or parts of a configuration, priority parameters are administered implementing the strategy.

  • Page 64: Ess Prerequisites

    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.

  • Page 65: Clan Access For Ess Registration

    In this case, the ESS server accepts the translation download but does not reset until it no longer controls any Port Networks. The CLAN reboots or fails: If the CLAN that the ESS server used to register to the Main ●...

  • Page 66: Network Port Considerations

    The Port Network containing the CLAN reboots or fails: If the Port Network containing ● the CLAN, used by the ESS server to register to the Main server, reboots or fails the Keep-Alive messages from the ESS server to the Main server stops. The Main server shows the status of the ESS server as unregistered in the status ess cluster window.

  • Page 67: Main Server(S) And Ess Server Differences

    2 of 2 Main server(s) and ESS server differences For the most part, capabilities of the Main server(s) and the ESS server will be the same if both are of the same platform type.There are some important differences between the Main server(s)

  • Page 68: Trunking Considerations

    In the event of a failover, if a different ESS server controls the primary and the backup D channels, each ESS server will think the D channel it does not control is out of service and will try to bring the D channel that it controls into service. The Service Provider will only use one of the D channels for signaling.

  • Page 69: Synchronization

    Port Networks 1 through 4 failover to ESS server 1. Port Networks 5 through 8 failover to Local Only ESS servers. ESS server 1 uses IGAR to establish inter-port network bearer between Port Networks 1 through 4. Each Local Only ESS server controls one Port Network (5 through 8).

  • Page 70: Personal Central Office Line (Pcol)

    During a failover, SBS calls will fail unless the CLAN for the signaling call and the bearer trunks are under the control of the same ESS server. Alternate routes may be used if under the control of the same ESS server as the originator.

  • Page 71: Css Considerations When Using Ess

    IPSI controlled Port Network, and then through the TN2305B or TN2306B ATM EI board. Port Networks in an ATM environment do not transition to IP during a failover to an ESS server. IPSI Priority List In an ESS environment, every IPSI has a priority list that contains up to eight servers, one Main server(s) and seven ESS servers.
  • Page 72 Based on the administered community of a particular IPSI Port Network, each IPSI may have a different list of available ESS servers. Since the Main server defaults to the highest priority in a system, the Main server holds the highest position on any IPSI’s list. The value for the Main server is not administrable and can never be changed.
  • Page 73 ESS server’s priority but does limit which IPSI list will contain the Local Only server. A priority value, entered in the Pri Scr column, is used to distinguish between ESS servers with the same preference settings, ESS servers with no preference setting, or ESS servers that are not in the same community as the IPSI.

  • Page 74: Advertising Priority To An Ipsi

    Advertising priority to an IPSI An ESS server advertises its priority to an IPSI: Every time it disconnects and reconnects to the Main server, such as resets after the ESS ● server receives translations from the Main server, network outages, etc.
  • Page 75 Main server’s SAT. The IPSI’s priority list can be found under the Connected Cluster heading. The list is in priority order, from left to right, using the ESS server’s Cluster ID. The Cluster ID is always the same as the Module ID found in the license file and is used to identify the server.

  • Page 76: Examples Of How The Priority List Works

    - The Main server will control Port Networks 1 and 2 - ESS server 2 will control Port Networks 3, 4, 5, and 6. If LAN 3 fails where Port Network 3 can no longer communicate to LAN 2, ESS server 3 ●...

  • Page 77: Local Only

    Examples of how the priority list works Figure 28: Customer’s configuration ESS server 3 Community 2 PN #3 Local preferred Community 2 disc Main Server or Main Server pair disc COMPACT ESS server 2 Community 1 disc COMPACT System preferred...
  • Page 78 ESS Design and Planning To administer ESS, it is helpful to start with a data collection worksheet, as shown in Table Table 3: ESS worksheet Server Preference System S8700 192.9.13.10 Preferred 192.9.13.11 (highest value preference) S8500 192.9.44.11 Local S8500 192.9.33.22...

  • Page 79: Priority List

    Priority Score. In this example, ESS server 3 would be the third choice for Port Network 3, Port Network 4, and Port Network 5, which are all in Community 2. ESS server 3 would also be the third choice for Port Network 1 and Port Network 2 following ESS server 1 and ESS server 2.

  • Page 80: Multi-Connected Configuration Using Atm Pnc

    Main server(s) fail, the administrator wants ESS server 1 to provide service to the entire system. If the IPSIs loses communication with ESS server 1, then ESS server 2 will take over the entire system. Port Networks 6 and 7 connect to the Main server(s) over the ATM network and do not have a direct IPSI connectivity to the Main server(s).
  • Page 81 Examples of how the priority list works Figure 29: Multi-Connected using ATM PNC ESS server 3 Community 2 PN #3 Local preferred Community 2 disc Main Server or Main Server pair disc COMPACT ESS server 2 Community 1 disc COMPACT...
  • Page 82 In the case of an IP Network failure, if PN6 and PN7 cannot communicate with the Main server(s), they will fall under control of one of the other ESS servers. In order for an ESS server to control a Port Network without an IPSI, such as PN6 or PN7, the ESS server must first control a Port Network with an IPSI.

  • Page 83: Timing Considerations

    PN4 and PN5 through the ATM network. ESS server 2 takes control of PN3. Main server(s) fails, WAN PN3, PN4, and PN5 failover to ESS server 2 as it is now connection fails, and ESS the first ESS server on their priority lists. ESS server 2 is...

  • Page 84: Ess No Service Timer

    The time from when the no service timer actives, to the time the IPSI requests service of an ESS server, is called the no service time out interval. If the communication to the Main server is restored before the no service time out interval expires, normal system recovery occurs.
  • Page 85 Timing considerations Conditions that trigger Link Recovery Link Recovery begins with detection of either: A TCP socket failure on the H.248 link ● Loss of the H.248 link within 40-60 seconds ● H.248 Link Recovery processes Link Recovery design incorporates three separate timers that monitor the period of time that the server or gateway spends in specific Link Recovery processes.
  • Page 86 If the link failure continues for several minutes, expect inaccuracies in BCMS, CMS, call ● attendants, and other time-related statistical reports. 86 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 87: H.323 Gateway-To-Endpoint Link Recovery

    Phone buttons (including feature access buttons) do not work. ● H.323 gateway-to-endpoint Link Recovery The H.323 link between an Avaya Media Gateway and an H.323-compliant IP endpoint provides the signaling protocol for Call setup ●...

  • Page 88: Feature Considerations

    CVLAN links on page 90 ● Facility Busy Indication on page 90 ● Hunt Groups on page 90 ● Leave Word Calling on page 90 ● Music on Hold on page 91 ● 88 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 89: Announcements

    ESS server will be affected by the deactivation of the Night Service mode. The ESS server assumes that any console that it cannot control is out of service. Best Service Routing (BSR) BSR polling works if the facility used for routing the polling call is under the control of that ESS server. Call Classification Call Classification will work only if there are one or more Call Classification resources under the control of the ESS server.

  • Page 90: Centralized Attendant Service (Cas)

    For a CAS Branch, calls are routed as if Night Service mode was activated. Calls are routed only if the trunks to the CAS Main are under control of the ESS server controlling the Port Network where attendant seeking calls arrive for service.

  • Page 91: Music On Hold

    Adjunct considerations Music on Hold The ESS server can provide Music on Hold only if the music source is in control of the ESS server. Calls to an ESS server without a music source hears silence. Adjunct considerations When a failover occurs, an ESS server may or may not have connectivity to various adjuncts.

  • Page 92: Call Management System (Cms)

    Port Network that contains the CLAN. In this case only the events that are under control of that ESS server will be sent to the CMS. All other related system data will be lost. This occurs in the event of a fragmented system resulting from a control network failure.

  • Page 93: Chapter 3: Ess Installation

    ● Overview In general, performing an ESS installation requires the following high-level steps: 1. Design the system and determine the ESS administration factors. For information on how to design and plan the system see, ESS Design and Planning on page 63.

  • Page 94: Installing Ess With Existing Servers

    ESS Installation 4. Administer ESS (Administering ESS on page 122) 5. Verify ESS server registration to the Main server (Check the administration on the Main server on page 127) 6. Acceptance testing (Enterprise Survivable Server Acceptance Testing on page 181)
  • Page 95 ESS Installation Checklist Table 10: Installing ESS with existing servers (continued) Task Information Documentation 3a. ESS with CSS-Port Install an IP Media For instructions on how to install Network Connectivity Processor and an IPSI an IP Media Processor, an IPSI...
  • Page 96 ESS Installation Table 10: Installing ESS with existing servers (continued) Task Information Documentation 5. ESS server: Upgrade Each ESS server must be For instructions on how to each ESS server to running Communication upgrade a server to a Communication Manager Manger 3.0 or later.
  • Page 97 ESS Installation Checklist Table 10: Installing ESS with existing servers (continued) Task Information Documentation 6. ESS server: Install a If the license file contains a To install the license and RFA license and new module ID or if the authentication file see:...
  • Page 98 ESS Installation Table 10: Installing ESS with existing servers (continued) Task Information Documentation 8. ESS server: Verify You entered an IP address For information on how to use communication with the of a CLAN when you the ping command, see: customer’s LAN interface...
  • Page 99 ESS Installation Checklist Table 10: Installing ESS with existing servers (continued) Task Information Documentation 10. Main Server: Upgrade Upgrade the Main server to To use the standard process to the server. Communication Manger upgrade the Main server to 3.0 or later.
  • Page 100 ESS Installation Table 10: Installing ESS with existing servers (continued) Task Information Documentation 11. Main server: Install the If the license file contains a To install the license and RFA license and new module ID or if the authentication file see: authentication file.
  • Page 101 ESS Installation Checklist Table 10: Installing ESS with existing servers (continued) Task Information Documentation 13. Main server: Configure The server’s web interface To configure a server for ESS the Main server is used to configure the that is already running Main server.
  • Page 102 ESS Installation Table 10: Installing ESS with existing servers (continued) Task Information Documentation 15. Main server: Verify Verify communication For information on how to use LAN/WAN connectivity between each ESS server the ping command, see: and the Main server over Installing and Configuring ●...

  • Page 103: Save Translations

    ESS Installation Checklist Table 10: Installing ESS with existing servers (continued) Task Information Documentation 18. Main server: Distribute If changes are made to For more information on the the translations to the ESS translations, they must be save translations servers...

  • Page 104: Installing Ess With New Servers

    ESS Installation Installing ESS With New Servers Use the information in Table 11 as a reference when installing ESS with new servers. Table 11: Installing ESS with new servers Task Information Documentation 1. All servers: Obtain Obtain RFA license files...
  • Page 105 ESS Installation Checklist Table 11: Installing ESS with new servers (continued) Task Information Documentation 3. ESS server: Install To install the server hardware, see: the hardware and Quick Start for load ● Hardware Installation: Communication Avaya S8500 Media Manager 3.0 or...
  • Page 106 ESS Installation Table 11: Installing ESS with new servers (continued) Task Information Documentation 5. ESS server: Install Install a RFA license file To install the license and and an authentication file authentication file see: the license and on each ESS server.
  • Page 107 ESS Installation Checklist Table 11: Installing ESS with new servers (continued) Task Information Documentation 7. ESS server: Verify An IP address of a CLAN For information on how to was entered when you use the ping command, that the ESS configured the ESS server.
  • Page 108 ESS Installation Table 11: Installing ESS with new servers (continued) Task Information Documentation 9. Main server: In an ESS environment, To install the server you must use static IP hardware, see: Install the Main addresses for the IPSIs in Quick Start for server hardware ●...
  • Page 109 ESS Installation Checklist Table 11: Installing ESS with new servers (continued) Task Information Documentation 11. Main server: Verify Verify communication For information on how to between each ESS server use the ping command, LAN/WAN and the Main server over see: connectivity the LAN/WAN.

  • Page 110: Ess Server License Files

    This chapter provides information on RFA license files for an ESS environment. It Important: does not contain information on how to load a license file on an Avaya server. For license file installation, refer to the installation documentation of the product you are installing.

  • Page 111: Module Ids And Cluster Ids

    The remaining 249 MIDs are assigned to each ESS server, and LSP, in sequence. For the ESS server to register with the Main server, the ESS server’s MID must match its administered CLID. The CLID is administered in the system-parameters ess screen. For more information on administering the system-parameters ess screen see, on page 122.

  • Page 112: Serial Numbers

    IPSI serial number. This implies that there cannot be more ESS servers than there are IPSI boards in the system. However, for high availability systems, that have duplex IPSIs, both IPSIs in a Port Network may be used to generate license files.

  • Page 113: Activating Ess Through The Rfa License File

    In Communication Manager 3.0 and later releases, both ESS Feature Keywords are turned off by default. Important: When loading a license file on an ESS server for the first time, or when loading a Important: license file where changes have been made to the status of an ESS Feature Keyword, a reset system 4 is required.

  • Page 114: Creating The License File

    ESS Installation Creating the license file Detailed instructions on how to create a license file can be found in the Avaya Remote Feature Activation (RFA) User Guide at, http://support.avaya.com. Important: You must be registered and authenticated for the Communication Manager...

  • Page 115: License Files For Replacement Servers

    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.

  • Page 116: Configuring The Servers

    Complete the following steps before configuring the Main server and each ESS server: 1. Communication Manager release 3.0 or later must be installed on each server. An ESS server: An ESS server can run a release of Communication Manager that is ●...

  • Page 117: Platform Numbers And Server Types

    Configuring the Servers 3. Upgrade the firmware on the IPSIs: To identify the firmware needed for an IPSI in an ESS environment see the Minimum Firmware/Hardware Vintages document found at: http:// support.avaya.com 4. A new license file with ESS enabled installed on each server: The license file enables the ESS feature and sets the platform type.
  • Page 118 Administration. The ESS features can be found on page 4 of the system-parameters customer-options screen. - Main server: Verify the ESS Administration field is set to yes while the Enterprise Survivable Server field is set to no. - Each ESS server: Verify that both the Enterprise Survivable Server and ESS Administration fields are set to yes.

  • Page 119: Configuring The Main Server And Each Ess Server

    This chapter outlines the fields that are unique when administering a Main server Note: in an ESS environment, or a server used as an ESS server in an ESS environment. It does not contain detailed information on how to load and configure the Avaya S8000 series servers.
  • Page 120 ● - This is NOT an enterprise survivable server, and select Change. b. For the ESS server, complete the following fields under the section you selected in the previous step (step a): Enter the CLAN IP address that will be used when the ESS server registers with the ●...

  • Page 121: After The Ess Server Is Configured

    After the ESS server is configured After the ESS server is configured it attempts to register with the Main server. If the ESS server is unable to register with the Main server within 10 minutes after being configured, an alarm is generated.

  • Page 122: Administering Ess

    Administer the no service timer and schedule the Auto Return feature on page seven. ● Each section of the system-parameters ess form is described in more detail in this chapter. Administering ESS server on the Main server System-parameters ess form - pages one through five On the Main server, use the following steps to translate each ESS server: 1.

  • Page 123: Platform Type

    2. For each ESS server enter data into the following fields: a. CLID: Enter the Cluster ID (the MID from the RFA license file) for the ESS server. The MID was assigned by RFA and appears in the license file. Use the following Bash...

  • Page 124: Priority Score

    For more information on preferences see, IPSI Priority List on page 71. j. Local Preferred: Use this option when you want the ESS server to accept the request for service from IPSIs co-located in the same geographical region, WAN/LAN segment, district, business unit, etc.

  • Page 125: System-Parameters Ess Form - Page Six: Assigning Port Networks To Communities

    Administering ESS k. Local Only: Use this option when you want the ESS server to accept the request for service from an IPSI, only if the IPSI is located in the ESS server’s same community. Enter a ’y’ or a ’n’ in this field. The default for this field is ’n’.

  • Page 126: System-Parameters Ess Form - Page Seven

    2. No Service Time Out Interval (default 5 minutes): Enter the time, in minutes, that the IPSIs will wait before requesting service from the highest ESS server on its priority list. Allowed entry for this field is three to 15 minutes.

  • Page 127: After Administering The Ess Servers

    3. The ESS server receives the translations, resets, and re-registers with the Main server. The above process is automatic. After the ESS server receives the initial translation download, any translation changes are sent to the ESS by executing the save translations all, or save translations ess command (see, Saving translations on page 130).
  • Page 128 ID is active for the pair of servers. c. The Registered? field is ’y’. If there is a ’n’ in this column, the ESS server is not registered and no data will appear in the Translation Updated or Software Version columns.
  • Page 129 All Port Networks are shown. This report may span several pages. ● All Port Networks come into service as indicated by the ’up’ in the Port Ntwk Ste ● column. Figure 40 for an example of the output of the status ess port-networks command. Issue 1.1 June 2005...

  • Page 130: Saving Translations

    Translations are saved on the Main server by executing the save translations command. You cannot save translations on an ESS server. When logging into an ESS server you receive a message stating that this server is an ESS server and translations cannot be saved.
  • Page 131 Saving translations Figure 41: system-parameters maintenance On the Main server verify that the ESS has received the translations by executing the status ess cluster command. The Translations Updated column contains the day and time (timestamp) of the last successful translation download to each ESS server. After the save translations command executes, the Translations Updated column may take several minutes to update, depending on the size of the translations and network congestion.
  • Page 132 ESS Installation 132 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 133: Chapter 4: Enterprise Survivable Server Conversions

    Main server before the new Main server comes online. 4. When converting media servers, ESS server to Main server, or Main server to ESS server, a new license file is required. There are no exceptions and no way to turn on the required features without a new license file.

  • Page 134: Existing Ess Server To Main Server

    6. All conversion options including the Main server(s) (non ESS server to Main server, ESS server to Main server, and Main server to ESS server) will be service affecting. When Port Networks are controlled by a new media server (Main server or ESS server), they preform a restart which resets every board in the Port Network.
  • Page 135 ESS Administration set to Y. ● A Module ID (MID) of 1: The MID is referred to as the Cluster ID (CLID) by the ESS ● feature. This value is set by the license file and cannot be administered in Communication Manager.
  • Page 136 The IP address of a CLAN controlled by the new Main server. b. The IP address(es) of the new Main server. Changing the address of the Main server on the ESS server does not require a reset system 4, nor does it do one automatically.

  • Page 137: Existing Media Server To Ess Server

    Existing media server to ESS server Note: An active Main server knows its own state and that of any ESS servers that have Note: registered with it. For some period of time (minutes), after all servers are installed and configured, there may be a discrepancy between the state displayed by the Main server and the ESS servers.
  • Page 138 A Module ID (MID) greater than 1: A MID is also referred to as the Cluster ID (CLID) by ● the ESS feature. This value is set by the license file and cannot be administered in Communication Manager. Each server in a duplex pair (S8700/S8710) will have the same CLID.
  • Page 139 Module ID. 10. Verify that the Main server has the latest translations available. 11. Translate the new ESS server on the Main server: From the Main server execute the change system-parameters ess command. See...

  • Page 140: Manual Backup Server To Ess Server

    ESS Administration set to y. ● A unique Module ID (MID): The MID is referred to as the Cluster ID (CLID) by the ESS ● feature. The MID of a Main server is always 1 (CLID 1). This value is set by the license file and cannot be administered in Communication Manager.
  • Page 141 ESS Administration set to y. ● A unique Module ID (MID): The MID is referred to as the Cluster ID (CLID) by the ESS ● feature. The MID is set by the license file and cannot be administered in Communication Manager.

  • Page 142: Ess Server To Manual Backup Server

    4 10. Re-connect the new ESS server(s) to the LAN/WAN. 11. On the Main server, verify that the new ESS server(s) register and that translations are updated. Periodically repeat this command until each server registers. status ess clusters ●...

  • Page 143: Chapter 5: Running In Ess Mode

    You can administer translations but you cannot save translations on an ESS server. The Main server can only distribute translations to an ESS server if the ESS server is registered with the Main server. The ESS server registers with the Main server through a CLAN board.

  • Page 144: User Enabled Telephone Features

    An ESS server alarms when it looses communication with an IPSI unless the ESS server was rejected by the IPSI. The following is a partial list of the types of alarms generated by the ESS server when it obtains control of a Port Network: ESS server alarm: A major alarm is generated when the ESS server controls a Port ●...

  • Page 145: Unplanned Fall-Back Or Failover

    Executing the disable ess command: This command allows an ESS server or Main ● server to be disabled (taken out of service). An ESS server or Main server may be disabled only if it is not controlling any Port Networks. A disabled ESS server or Main server will not connect to any IPSIs.

  • Page 146: Unplanned Failover To Another Ess Server

    After a fall-back to the Main server After the Port Networks fall-back to the control of the Main server, and the ESS server no longer controls any Port Networks, the ESS server resets. The reset system 4 is used to clear alarms and busyouts and allow any pending translations to be loaded.

  • Page 147: Chapter 6: Maintenance

    Use disable ess from either a Main server or an ESS server. An ESS server may disable only its own cluster ID. When disable ess is run from the Main server, any and all cluster IDs may be disabled including the Main server itself.
  • Page 148 The complete operation for disable ess on a Main server may take several minutes. The request is first sent in a message from the Main server to the ESS server. Once the ESS server receives the message, it changes to the ESS disabled state and performs a reset system 4 operation.

  • Page 149: Disable Ess Command Error Codes

    Use enable ess from either a Main server or an ESS server. An ESS server may enable only its own cluster ID. When enable ess is run from the Main server, any and all cluster IDs may be enabled including the Main server itself.
  • Page 150 When enable ess cluster <main cluster n> is run, the Main server: Does nothing, if it is the ESS cluster is already enabled. The TEST RESULTS screen ● indicates that Test 1606 passed for the Main server. See...

  • Page 151: Enable Ess Command Error Codes

    Description 1991 ESS cluster not administered 1992 ESS cluster not registered 1993 ESS cluster controlling IPSIs (Port Networks) 1994 ESS cluster (non-main) may not disable other clusters (ESS server or Main server) 2500 Internal operation failed Issue 1.1 June 2005...

  • Page 152: Get Forced-Takeover Ipserver-Interface

    Main server or ESS server where the command is issued, Test #1605 will immediately PASS. If the Port Network is not controlled by the Main server or ESS server where get ● forced-takeover ipserver-interface is issued the ESS server shows the test result as IN PROGRESS.

  • Page 153: Get Forced-Takeover Ipserver-Interface Command Error Codes

    Command successfully completed get forced-takeover ipserver-interface command Error Codes get forced-takeover ipserver-interface command Error Codes Error Code Description 1995 ESS cluster is disabled 1996 Port network does not exist 1997 Not an IPSI port network status ess clusters S8700 | 8710...
  • Page 154 Main server (Cluster ID 1). The Main server knows the identities of all of its associated ESS servers from the translations input to the Main server. The Main server knows the state of all of the ESS servers that have successfully registered with it. When status ess clusters is run on the Main server it shows its own state.

  • Page 155: Status Ess Clusters Field Descriptions

    The detail lines are shown in cluster ID order. When status ess is issued on a Main server there is one detail line for the Main server itself and a detail line for every ESS server that is registered with the Main server.
  • Page 156 Software The software version of Avaya Communication Manager running on the Version server. For an ESS server, this is reported to the Main server over the registration link. 2 of 2 156 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 157: Status Ess Port-Networks

    ESS server controlling all five Port Networks. In addition to the Main server, seven other ESS servers are connected to each IPSI in every Port Network. Each IPSI may be connected to the same, some of the same, or completely different servers.

  • Page 158: Status Ess Port-Networks Field Descriptions

    158 shows a cluster identifier of one (1). The number that identifies the Port Network (PN). This is the same number that identifies the Port Network in the list cabinet command. 1 of 4 158 Avaya Enterprise Survivable Servers (ESS) Users Guide...
  • Page 159 Enterprise Survivable Servers - Maintenance Commands status ess port-networks field descriptions (continued) Field Description Com Num The community number of the Port Network (1 - 64) assigned to the Port Network on display system-paramters. Port networks have a natural attraction for local preferred media servers in the same community.
  • Page 160 Cluster ID (1 - 999) ● * (asterisk) ● - The media server where status ess port-networks is run cannot connect to the IP Server Interface in this Port Network. This may be because: the IPSI is being reset the IPSI rejected the connection request from the media server, perhaps because it is already connected to its limit (8) of media servers.

  • Page 161: Cnc [On | Off | Status]

    Cluster ID (1 - 999) ● * (asterisk) ● - The Cluster ID reported by the IPSI is not known to the media server (in its translations) where status ess port-network was executed. blank ● - There is no IPSI in this Port Network.

  • Page 162: Ess Maintenance Procedures

    PNC. On duplicated CSS PNC configurations, depending on the exact order and timing with which the faults are reported, the CSS fault recovery processes in the Main server may tear down calls on other PNs. ESS server processes try to mitigate this action but it is impossible to eliminate it entirely.

  • Page 163: Removing An Ess

    ESS Maintenance Procedures Removing an ESS It may be necessary to remove an ESS server from service. The following steps can be used to do this. 1. At the Main server issue the status ess port-networks command to verify that the ESS server is not controlling any Port Networks.

  • Page 164: Enterprise Survivable Server - Troubleshooting

    Main server and ESS servers are are running. The ESS servers can be on a later release than the Main server but the Main server should never be on a later release than the ESS servers. The software release should only be different when upgrades are being performed, ESS servers first and then the Main server.

  • Page 165: Registration

    Configure Server > configure ess: Used to specify whether the server is a Main ● server or an ESS server. If it is an ESS server specify an address for a CLAN and the Main server(s). Configure Server > Set Identities: Used to set the Server IDs of the individual ●...
  • Page 166 Maintenance At the ESS server that is not registering with the Main server, use the following commands to troubleshoot: ! CAUTION: In the next steps be careful to use the Close Window button to cancel out of the CAUTION: Configure Server page to avoid a reboot of the ESS server. Do not Update the system.

  • Page 167: List Trace Ras Command Example

    6. Use the SAT command status ess clusters to verify that a translation file has been sent to this ESS server. 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.
  • Page 168 2. Execute the trace command from the Main server. From the Main server, enter a list trace ras ip-address x.x.x.x command for the IP address that is to be monitored. In this example it is the IP address of the ESS server (135.9.78.143) The first message exchange is the ESS server sending a Registration Request (RRQ) to the Main server.
  • Page 169 3. Execute the trace command from the ESS server. Use the IP Address obtained from the Configure ESS screen with the list trace ras command. The same ESS / Main message exchange takes place. From this perspective the ESS server sends a Registration Request (these appear as KARRQ messages at the Main server) and the Main server responds with Registration Confirmation (RCF) messages.
  • Page 170 3601: IP RRJ-ESS obj not init - The FEAT_ESS feature bit is not turned on in the license ● file. 3602: IP RRJ-ESS bad SID sent - The ESS server sent a SID that does not match that of ● the Main server. The SID is set by the license file.

  • Page 171: Ipsi Is Not Connected To A Server

    IPSI has established a connection with. Under normal operation (no network or server failures) a IPSI will establish connections to all ESS servers but only the eight servers that have the highest priority will be shown by the status ess port-networks command.
  • Page 172 Command successfully completed Command: 5. Resolve network fragmentation and outage issues per local practice. 6. Use the SAT command status ess port-network to verify that all Port Networks (IPSIs) are communicating with media servers. 172 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 173: Chapter 7: Ess Maintenance Object

    ESS servers is initially checked approximately ten minutes after the Main server boots up. Subsequent to this, the registration status for all ESS servers is monitored each time an ESS server registration status change is received at the Main server.

  • Page 174: Error Log Entries And Test To Clear Values

    Notes: a. Error Type 1: This error only applies to an ESS server. When an ESS server assumes control of an IPSI Port Network, this error is generated and logged. The following steps may be followed to investigate and attempt to retire the alarm: 1.
  • Page 175 Issuing the commands below causes a service interruption. When Port Networks CAUTION: switch to either a Main server or ESS server, a level 2 restart is initiated on the Port Network. Service will be interrupted to the entire Port Network. Note that shuffled IP to IP calls will not be dropped but during the restart they will not have any access to features (Hold, Transfer, Conference, etc.).
  • Page 176 ESS Maintenance Object b. Error Type 257: This error applies to a Main server or ESS server. This error is generated when an ESS server is translated on the Main server but is NOT registered with the Main server. For detailed information on maintenance commands see Maintenance Commands for Avaya Communication Manager 3.0, Media Gateways and Servers.
  • Page 177 ESS server and Main servers. Where nnn.nnn.nnn.nnn is IP address of the CLAN in the Main server that the ESS server is trying to register with. To determine which IP address the ESS server is attempting to register with, use the Configure Server command from the Maintenance Web Interface on the ESS server to display the configure ESS screen.
  • Page 178 11. Use the SAT command status ess clusters to verify that a translation file has been sent to this ESS server. 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.

  • Page 179: System Technician-Demanded Tests: Descriptions And Error Codes

    Command successfully completed Command: 5. Resolve network fragmentation and outage issues per local practice. 6. Use the SAT command status ess port-network to verify that all Port Networks (IPSIs) are communicating with the servers. System Technician-Demanded Tests: Descriptions and Error Codes There are no system technician demanded tests for the ESS maintenance object.
  • Page 180 ESS Maintenance Object 180 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 181: Chapter 8: Enterprise Survivable Server Acceptance Testing

    Shuffled IP calls do not have access to features during Port Network resets. Use this procedure to test the ability of an ESS server to take control of one or more Port Networks. 1. Identify the Port Network(s) that will be used for the test.

  • Page 182: Acceptance Criteria

    Testing transfer of control from ESS server to Main server What to expect The ESS server loses control of all Port Networks currently under its control as the Port Networks restart. Communication Manager on the Main server reboots. This test takes several minutes.

  • Page 183: What This Test Is Used For

    Use this test to verify that the Main server can assume control of the Port Networks under control of the ESS server. 1. Verify that the ESS server is currently in control of the Port Network(s) under test by executing the status ess port-network command from the Main server. The status of the Port Network(s) under test is shown as down.

  • Page 184: Disable An Ess Server From The Main Server

    Verify that the selected ESS server is now disabled: 1. On the Main server: a. After the ESS server comes back up from the reset and re-registers with the Main server, execute the status ess clusters command from the Main server SAT. Verify that: - The enabled state under the Enabled? column, shows n.

  • Page 185: Enable An Ess Server From The Main Server

    Verify that the selected ESS server is now enabled: 1. On the Main server: a. After the ESS server comes back up from the reset and re-registers with the Main server, execute the status ess clusters command from the Main server SAT. Verify that: - The enabled state under the Enabled? column, shows y.
  • Page 186 Enterprise Survivable Server Acceptance Testing 186 Avaya Enterprise Survivable Servers (ESS) Users Guide...

  • Page 187: Glossary

    Community A virtual group consisting of one ESS server and one or more Port Networks. Enterprise Survivable Servers: The Avaya option that provides survivability by allowing backup servers to be placed in various locations in the customer’s network.

  • Page 188: Maintenance Object

    Avaya’s ordering system for products and services. Serial numbers A serial number of the Avaya hardware is used to create a valid license file. The hardware serial number and the serial number within the license file must match.

  • Page 189: Index

    ....Attendant Console Existing ESS media server to Main server ....
  • Page 190 IPSI maintenance replacement ....ATM with a single ESS server in a takeover IPSI version ....
  • Page 191 ... Updating the Main server ..Main server and ESS differences ..User enabled telephone features Maintenance Object .
  • Page 192 Index 192 Avaya Enterprise Survivable Servers (ESS) Users Guide...

Table of Contents