How to Configure Enterprise Survivable Server (ESS) using Avaya S8700-Series Media Servers Issue 1.0

Transcription

1 Avaya Solution and Interoperability Test Lab How to Configure Enterprise Survivable Server (ESS) using Avaya S8700-Series Media Servers Issue 1.0 Abstract These Application Notes describe how to configure Enterprise Survivable Server (ESS) using Avaya S8700-Series Media Servers. The Enterprise Survivable Server (ESS) provides survivability by allowing backup servers to be placed in remote locations in the customer network. The backup servers provide service to port networks in the case where the Avaya S8500-Series Media Server, or the Avaya S8700-Series Media Server pair fails, or connectivity to the main media server or media server pair is lost. These Application Notes were written at the request of a customer. 1 of 31

2 1. Introduction These Application Notes describe how to configure Enterprise Survivable Server (ESS) using Avaya S8700-Series Media Servers. The Enterprise Survivable Server (ESS) provides survivability by allowing backup servers to be placed in remote locations in the customer network. The backup servers provide service to port networks in the case where the Avaya S8500-Series Media Server, or the Avaya S8700-Series Media Server pair fails, or connectivity to the main media server or media server pair is lost. There can only be one main server in an ESS environment, either one Avaya S8500-Series Media Server, or one pair of Avaya S8700-Series Media Servers. If the main server is an Avaya S8500-Series Media Server, all ESS servers in the configuration must also be Avaya S8500- Series Media Servers. During normal operation, the main server communicates with and controls all the port networks. The following were tested using the configuration in these Application Notes: Failure of the main media server resulting in the ESS server controlling port networks Recovery of the main media server resulting in the main server regaining control of port networks Figure 1 illustrates the Credit Card and Banking Configuration used to verify these Application Notes. The reference configuration represents a typical financial customer. It is a hub and spoke architecture where the Main Office consists of Avaya S8710 Media Servers with two Avaya G650 Media Gateway carriers in an IP Connect High Reliability configuration as described in [4] of Section 9. Each Avaya S8710 Media Server in the Main Office is configured to use the Corporate LAN interface in addition to being able to access the IPSIs located in the port network at the Main Office using separate Control Networks. The Branch Offices register to C-LANs in the Avaya G650 Media Gateway carriers at the Main Office. The Branch Offices also have local survivability options. This includes an Avaya S8300 Media Server licensed as a Local Survivable Processor (LSP) in an Avaya G700 Media Gateway at Branch 3, an Avaya S8500 Media Server also licensed as an LSP at Branch 4, and Standard Local Survivability Mode configured for the Avaya G250 Media Gateway at Branch 5. Each office has trunks to the Public Switched Telephone Network (PSTN). The Main Office also has the Avaya Call Management System, which is used for contact center administration and reporting for all offices. All IP Telephones at all offices register to Avaya Communication Manager running on the Avaya S8710 Media Servers at the Main Office. Only the ESS configuration will be covered in these Application Notes. Note: The administration of the network infrastructure shown in Figure 1 is not the focus of these Application Notes and will not be covered. Instead, the focus of these Application Notes is to configure ESS at the Branch 2 location to backup the Avaya S8700-Series Media Servers at the Main Office location in Figure 1. 2 of 31

3 Figure 1 Network Configuration Diagram 3 of 31

4 Table 1 lists the IP address assignment for the equipment shown in Figure 1 at the Main Office. Equipment S8710 Main Media Server 1 Ethernet 0 Active Server Ethernet 1 Ethernet 2 Ethernet 3 Active Server Ethernet 4 Active Server Gateway S8710 Main Media Server 2 Ethernet 0 Active Server Ethernet 1 Ethernet 2 Ethernet 3 Active Server Ethernet 4 Active Server Gateway IPSI Main A Gateway IPSI Main B Gateway MedPro Main A Shared Virtual Gateway MedPro Main B Shared Virtual Gateway IP Network/Mask / / / / / / / / / / / / / / / / / / / / / / / / / / / /24 Description Control Network A Active server address for Control Network A Services Port Server Duplication Link Control Network B Active server address for Control Network B Corporate LAN Active server address for CorporateNetwork Gateway address Control Network A Active server address for Control Network A Services Port Server Duplication Link Control Network B Active server address for Control Network B Corporate LAN Active server address for Corporate Network Gateway address IPSI connected to Control Network A Gateway address IPSI connected to Control Network B Gateway address Media Processor in Avaya G650 A Virtual address of Media Processor Gateway address Media Processor in Avaya G650 B Virtual address of Media Processor Gateway address Table 1 IP Address Assignment at the Main Office 4 of 31

5 Table 2 lists the IP address assignment for the equipment shown in Figure 1 at Branch 2. Equipment S8710 ESS Media Server 1 Ethernet 1 Ethernet 2 Ethernet 4 Active Server Gateway S8710 ESS Media Server 2 Ethernet 1 Ethernet 2 Ethernet 4 Active Server Gateway IPSI ESS Gateway MedPro Branch 2 Gateway IP Network/Mask / / / / / / / / / / / / / /24 Description Services Port Server Duplication Link Corporate LAN Active server address for Corporate Network Gateway address Services Port Server Duplication Link Corporate LAN Active server address for Corporate Network Gateway address IPSI connected to ESS Gateway address Media Processor in Avaya G650 Branch 2 Gateway address Table 2 IP Address Assignment at Branch 2 5 of 31

6 2. Equipment and Software Validated The following hardware and software versions were used for this configuration: Equipment Version Avaya S8710 Media Server 3.1 Load and Service Pack Avaya G650 Media Gateway Avaya TN2312BP IPSI Avaya TN799DP C-LAN Avaya TN2602AP MEDPRO HW12 FW030 HW01 FW017 HW02 FW21 Avaya 4610SW IP Telephone 2.3 Avaya 4620SW IP Telephone 2.3 Avaya 4621SW IP Telephone 2.3 Avaya 4622SW IP Telephone 2.3 Avaya 4625SW IP Telephone 2.5 Table 3 Equipment and Version Validated 6 of 31

7 3. ESS Requirements The following are the requirements for ESS: The main and each ESS server must be running Avaya Communication Manager 3.0 or later. The main server can be either an Avaya S8700-Series or an Avaya S8500-Series Media Server. If the main server is an Avaya S8500-Series Media Server, all ESS servers must be Avaya S8500-Series Media Servers. Firmware on the IPSI circuit packs must support the ESS option. Firmware vintage 30 is the IPSI vintage released with Avaya Communication Manager 3.1. A separate license file must be used for each main and ESS server. Each license file must contain a unique serial number of a reference IPSI, a unique Module ID (MID) and a common System Identifier (SID). IP network connectivity for all IPSIs and media servers. In a Center Stage Switch (CSS) environment: a. There must be an IPSI and IP Media Processor boards for each survivable CSS port network. b. In all survivable port networks, the TN570 (Expansion Interface) board must be upgraded to the TN570D board. Any port networks that contain one or more IPSIs must have the TN570D. Port networks that do not have IPSIs, and therefore are not survivable, may use the TN570B version 7 or later. For duplex IPSI control, the Avaya S8500-Series Media Server must be equipped with a dual NIC card. In an ATM environment, all Port Network Connectivity (PNC) and Circuit Emulation Service (CES) circuit packs must be upgraded to TN2305B or TN2306B (ATM Expansion Interface) circuit packs. 7 of 31

8 4. Avaya Media Server Configuration (Main) This section shows how to configure the Avaya S8710 Media Servers. The assumption is that the appropriate license and authentication files have been installed on the servers and that login and password credentials are available. Configure the IP address of a laptop to with a subnet mask of and connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of one of the Avaya S8710 Media Servers using an Ethernet crossover cable. The Services port uses the preconfigured IP address with a subnet mask of of 31

9 Step Description 1. Launch a web browser and connect to URL with proxies turned off. Supply the appropriate login and password credentials when prompted. 2. Click Launch Maintenance Web Interface on the main menu. Click Configure Server under the Server Configuration category in the lower left pane. Figure 2 Maintenance Web Interface 9 of 31

10 Step Description 3. Click Continue on the Review Notices page. Click Continue on the Back Up Data page. Click the Configure individual services radio button. Check the The Corporate LAN interface of both servers is on the same subnet and The Control Network interface of both servers is on the same subnet boxes. In this configuration separate control networks are used for the IPSIs located in the Avaya G650 Media Gateway carriers at the Main Office. Click Continue. Figure 3 Copy Settings (Main Server 1) 10 of 31

11 Step Description 4. Click Set Identities on the left pane to set the hostname or identity of each Server. Select 1 for the This is server number field. Assign the Ethernet ports based on the information in Table 1. Enter the server ID (SVID) in the ID field located to the right of the Host Name field. Each server in an Avaya S8700-Series Media Server pair requires a unique server ID. Click Continue. Figure 4 Set Identities (Main Server 1) 11 of 31

12 Step Description 5. Click Configure Interfaces on the left pane to assign the IP address for each Ethernet port using the information provided in Table 1. Check the Enable VLAN 802.1q priority tagging box to globally enable tagging on the Avaya S8710 Media Server if VLANs are used. Figure 5 Configure Interfaces (Main Sever 1) 12 of 31

13 Step Description 6. Figure 6 shows the lower half of the Configure Interfaces page. Click Change to save the settings. Figure 6 Configure Interfaces (Main Server 1 Continued) 13 of 31

14 Step Description 7. Click Configure ESS on the left pane to specify whether this is an ESS. Since this is a main server, select This is NOT an enterprise survivable server and click Change. Figure 7 Configure ESS (Main Server 1) 14 of 31

15 Step Description 8. Connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of the other main Avaya S8710 Media Server using an Ethernet crossover cable. Repeat Steps 1 through 7 to configure the identity and Ethernet ports and ESS role of the second main media server. The only difference is that 2 is selected in the This is server number field in Step 4 as shown in Figure 8. Figure 8 Set Identities (Main Server 2) 15 of 31

16 5. Avaya Media Server Configuration (ESS) Connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of one of the ESS Avaya S8710 Media Servers using an Ethernet crossover cable. Step Description 1. Repeat Steps 1 through 2 in Section Click Continue on the Review Notices page. Click Continue on the Back Up Data page. Click the Configure individual services radio button. Check the The Corporate LAN interface of both servers is on the same subnet box. The The Control Network interface of both servers is on the same subnet box was not selected because separate control networks were not used for the ESS media servers. Click Continue. Figure 9 Copy Settings (ESS Server 1) 16 of 31

17 Step Description 3. Click Set Identities on the left pane to set the hostname or identity of each Server. Select 1 for the This is server number field. Assign the Ethernet ports based on the information in Table 2. Figure 10 Set Identities (ESS Server 1) 17 of 31

18 Step Description 4. Click Configure Interfaces on the left pane to assign the IP address for each Ethernet port using the information provided in Table 2. Check the Enable VLAN 802.1q priority tagging box to globally enable tagging on the Avaya S8710 Media Server if VLANs are used. Click Change. Figure 11 Configure Interfaces (ESS Server 1) 18 of 31

19 Step Description 5. Click Configure ESS on the left pane to specify whether this is an ESS. Since this is an ESS, select This is an enterprise survivable server (ESS) and click Change. The Registration address at the main server is the IP address of the C-LAN located in the port network at Branch 2 because this C-LAN is local to the ESS server. During the initial registration to the main server, the ESS server does not contain translations and therefore has no knowledge of other C-LAN boards in the configuration. If the ESS server cannot communicate with the configured C-LAN board it will be unable to register with the main server. Specify the IP address of the main servers in the File Synchronization address at the main cluster fields. Figure 12 Configure ESS (ESS Server 1) 19 of 31

20 Step Description 6. Connect the Ethernet port of the laptop to the Services port (Ethernet port 1) of the other ESS Avaya S8710 Media Server using an Ethernet crossover cable. Repeat Steps 1 through 5 to configure the identity, Ethernet ports, and ESS role of the second ESS media server. The only difference is that 2 is selected in the This is server number field in Step 3 as shown in Figure 13. Figure 13 Set Identities (ESS Server 2) 20 of 31

21 6. Avaya Communication Manager Configuration The following configuration was entered via the System Access Terminal (SAT) Verify Licenses In order to configure ESS, Avaya Communication licenses must be obtained and activated for the main and ESS servers. The following steps can be used to verify whether Avaya Communication Manager has the appropriate licenses to configure ESS. Contact an Avaya representative if the highlighted features shown in the following screens are not enabled. Step Description 1. From the Avaya Communication Manager SAT screen on the main server, use the display system-parameters customer-options command. Go to Page 4 to verify that the Enterprise Survivable Server is set to n and the ESS Administration field is set to y. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? n ISDN Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? n Malicious Call Trace? y External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? y Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? y IP Trunks? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.) Figure 14 Optional Features (Main Server) 21 of 31

22 Step Description 2. From the Avaya Communication Manager SAT screen on the ESS server(s), use the display system-parameters customer-options command. Go to Page 4 to verify that the Enterprise Survivable Server is set to y and the ESS Administration field is set to y. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? n ISDN Network Call Redirection? y Enterprise Survivable Server? y ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? n Malicious Call Trace? y External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? y Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? y IP Trunks? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.) Figure 15 Optional Features (ESS Server) 22 of 31

23 6.2. ESS Configuration The following steps are used to configure ESS from the Avaya Communication Manager SAT screen on the main server(s). Step Description 1. Use the change node-names ip command to add new node names for each ESS server. Figure 16 displays the node names and IP addresses assigned to the ESS servers. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address BO G250-BR aesserver br3-lsp br4-elsp br4-lsp br cc-ess cc-ess ccaesbr cf-1a cf-1b clan-1a clan-1a clan-1b clan-2a ( 16 of 28 administered node-names were displayed ) Use 'list node-names' command to see all the administered node-names Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name Figure 16 IP Node Names 2. Use the change system-parameter ess command and enter the following data: Cl ID Enter the cluster ID (the RFA Module ID) for the ESS server. The bash command statuslicense v can be used to determine the Module ID (MID) of the ESS server. Figure 17 shows the output of the command. init@cc-ess1> statuslicense -v CommunicaMgr License Mode: Normal checking application CommunicaMgr version R013x Network used for License: Carrier 01a License Serial Number is 05J on Carrier 01a RFA Module ID is 2 RFA System ID is 1 init@cc-ess1> F Figure 17 Statuslicense (ESS Server) 23 of 31

24 Step Description Plat Type (Platform Type) Enter duplex for the Avaya S8710 Media Servers. Server ID Enter the SVID of the ESS Avaya S8710 Media Servers. This is the SVID that was entered on the Set Server Identities web page in Step 3 in Section 5. Node Name Enter the node name assigned to each ESS server in Step 1. Pri Scr (Priority Score) Enter the priority score (1-100, with 1 being the lowest) for the ESS server(s). The value of the priority score and the selected preference determine the position of the ESS server in the priority list of the IPSI. The IPSI will failover to the ESS with the highest priority score. The value of the priority score and the selected preference determine the position of the ESS server on the priority list of the IPSI. Com (Community) Enter the community number (on Page 6 of system-parameters ess form). The community is a virtual group consisting of an ESS server and one or more port networks. The ESS server will be associated with the port networks for that community. This association affects how the IPSI prioritizes the ESS server in a community if the ESS is administered with a Local Preferred or Local Only preference. Sys Prf (System Preferred) This option is used when the goal is to allow one ESS server to replace the main server and keep as much of the system intact as possible. System Preferred servers have a higher priority value than any Local Preferred server independent of community or administered priority score. If multiple System Preferred servers are administered, the server with the highest priority score has the top priority in the priority list of the IPSI. Loc Prf (Local Preferred) This option is used when the goal is to for the ESS server to accept service requests from IPSIs co-located in the same geographic region. After the System Preferred preference, the Local Preferred preference has the second highest priority within an IPSI community. When multiple Local Preferred servers are administered with the same community, the priority score is used to determine which server has the top priority in the priority list of the IPSI. Loc Only (Local Only) This option is used when the goal is for the ESS server is to accept service requests from an IPSI only if it the IPSIs are located in the same community as the ESS server. A Local Only server only advertises to an IPSI in the same community. The Priority score of each server would determine its ranking on the priority list of the IPSI if a Local Preferred server (outside the community) advertises to an IPSI in the same community as a Local Only server. Servers set to Local Only have the option of also using the Local Preferred setting to increase its priority on the priority list of a local IPSI. Note: An ESS server cannot be administered as both Local Only and System Preferred. 24 of 31

25 Step Description change system-parameters ess Page 1 of 7 ENTERPRISE SURVIVABLE SERVER INFORMATION Cl Plat Server A Server B Pri Com Sys Loc Loc ID Type ID Node Name ID Node Name Scr Prf Prf Only MAIN SERVERS 1 Duplex ENTERPRISE SURVIVABLE SERVERS 2 Duplex 3 cc-ess1 4 cc-ess2 1 1 y n n 1 1 y n n 1 1 y n n 1 1 y n n 1 1 y n n 1 1 y n n 1 1 y n n 1 1 y n n Figure 18 System Parameters ESS (Page 1) 3. Go to Page 6 and assign a community to the port networks. Assigning a port network to a community associates the port network with an ESS server administered with the Local Preferred or Local Only preference. The community assignment feature was not used in these Application Notes since the System Preferred preference was selected. change system-parameters ess Page 6 of 7 COMMUNITY ASSIGNMENTS FOR PORT NETWORKS PN Community PN Community PN Community PN Community PN Community : 1 14: 1 27: 1 40: 1 53: 1 2: 1 15: 1 28: 1 41: 1 54: 1 3: 1 16: 1 29: 1 42: 1 55: 1 4: 1 17: 1 30: 1 43: 1 56: 1 5: 1 18: 1 31: 1 44: 1 57: 1 6: 1 19: 1 32: 1 45: 1 58: 1 7: 1 20: 1 33: 1 46: 1 59: 1 8: 1 21: 1 34: 1 47: 1 60: 1 9: 1 22: 1 35: 1 48: 1 61: 1 10: 1 23: 1 36: 1 49: 1 62: 1 11: 1 24: 1 37: 1 50: 1 63: 1 12: 1 25: 1 38: 1 51: 1 64: 1 13: 1 26: 1 39: 1 52: 1 Figure 19 System-Parameters ESS (Page 6) 25 of 31

26 Step Description 4. Go to Page 7 and assign the Auto Return and No Service Time Out Interval fields. The Auto Return field can be used to schedule a time for all port networks to return to the control of the main server after a failover occurs. The Auto Return feature is set to no in this configuration. The No Service Time Out Interval (range of 3 to 15 minutes) is the amount of time the IPSIs will wait before requesting service from the highest ESS server on its priority list. change system-parameters ess Page 7 of 7 ENTERPRISE SURVIVABLE SERVER OPTIONAL FEATURES Auto Return: no No Service Time Out Interval: 3 Figure 20 System-Parameters ESS (Page 7) 6.3. Save Configuration Use the save translation ess or save translation all command to save the Avaya Communication Manager configuration. The ESS resets after receiving translations. Scheduled backups can be administered using the change system-parameters maintenance command. save translation all SAVE TRANSLATION Command Completion Status Error Code Success 0 Figure 21 Save Translation 26 of 31

27 7. Verification Steps The main sever sends a copy of its translations to the ESS server when each ESS server registers with the main server. The ESS server resets and re-registers with the main servers after receiving the translations. The following steps can be performed to verify that the ESS configuration is working: Step Description 1. From the Avaya Communication Manager SAT screen on the main server, use the status ess clusters command to verify the following fields: Cluster ID This is the same value as the Cluster ID that was assigned in Step 2 of Section 6.2 and matches the RFA Module ID returned by the bash command statuslicense v. Active Server ID Server ID of the active server in the cluster. This is the same value as the SVID that was administered in the Set Identities web page. Registered The server is registered if this field is set to y. If this field is set to n, the server is not registered and no data will appear in the Translations Updated or Software Version fields. status ess clusters Cluster ID 1 ESS CLUSTER INFORMATION Active Cluster Server Translations Software ID Enabled? ID Registered? Updated Version 1 y 1 y 0:26 2/21/2006 R013x y 3 y 0:26 2/21/2006 R013x Figure 22 ESS Cluster Information before ESS failover 27 of 31

28 Step Description 2. From the Avaya Communication Manager SAT screen on the main server, use the status ess port-networks command to verify that all port networks are in service as indicated by up in the Port Ntwk Ste column. The port networks are under the control of the main server (i.e., Cluster 1) as indicated in the Cntl Clus ID column. status ess port-networks Cluster ID 1 ESS PORT NETWORK INFORMATION Port IPSI Pri/ Pri/ Cntl Connected Com Intf Intf Ntwk Gtway Sec Sec Clus Clus(ter) PN Num Loc Type Ste Loc Loc State ID IDs 1 1 1A01 IPSI up 1A01 1A01 actv-aa B01 standby A01 IPSI up 2A01 2A01 actv-aa Figure 23 ESS Port Network Information before ESS Failover 3. From the Avaya Communication Manager SAT screen on the main server, use the list survivable-processor command to determine which survivable processor processors are registered and whether translations are synchronized by looking at the Reg and Translations Updated columns. list survivable-processor SURVIVABLE PROCESSORS Name Type IP Address Reg LSP Translations Net Act Updated Rgn br3-lsp LSP y n 0:26 2/21/ cc-ess1 ESS y 0:26 2/21/ cc-ess2 ESS n 0:26 2/21/ br4-elsp LSP y n 0:26 2/21/ Figure 24 Survivable-Processors 4. If the ESS server is not registered with the main server or the port networks are down, use the SAT ping ip-address board command and specify the board location of the C-LAN in the main server to verify connectivity to the ESS server. The SAT display events command can also be used to display ESS registration denial events (e.g., in the 36xx range). The SAT list trace ras ip-address command can be used to monitor registration requests from the ESS server. 28 of 31

29 Step Description 5. Disconnect the Ethernet cables of the main server or issue the get forced-takeover ipserverinterface all command from the SAT of the ESS server to manually fail the port networks to the ESS server. Verify that the port networks successfully failover to the ESS servers by issuing the status ess port-networks command from the SAT of the ESS server. The port networks are now under the control of the ESS server (i.e., Cluster 2) as indicated in the Cntl Clus ID column. status ess port-networks Cluster ID 2 ESS PORT NETWORK INFORMATION Port IPSI Pri/ Pri/ Cntl Connected Com Intf Intf Ntwk Gtway Sec Sec Clus Clus(ter) PN Num Loc Type Ste Loc Loc State ID IDs 1 1 1A01 IPSI up 1A01 1A01 actv-aa B01 standby A01 IPSI up 2A01 2A01 actv-aa Figure 25 ESS Port Network Information after ESS failover 6. From the Avaya Communication Manager SAT screen on the ESS server, use the status ess clusters command to verify that the ESS server (i.e., Cluster 2) is no longer registered. status ess clusters Cluster ID 2 ESS CLUSTER INFORMATION Active Cluster Server Translations Software ID Enabled? ID Registered? Updated Version 2 y 3 n 0:26 2/21/2006 R013x Figure 26 ESS Cluster Information after ESS failover 7. Reconnect the Ethernet cables of the main server and issue the get forced-takeover ipserverinterface all command from the SAT of the main server to manually switch the control of the port networks back to the main server. 29 of 31

30 8. Conclusion These Application Notes describe how to configure Enterprise Survivable Servers (ESS) using Avaya S8700-Series Media Servers. The ability of the ESS servers to provide service to port networks if the main media server pair fails, or connectivity to the main media server pair is lost was verified using these Application Notes. The steps provided do not address all possible configuration scenarios. 9. Additional References The following Avaya product documentation can be found at [1] Installing and Configuring the Avaya S8700-Series Media Server, Release 3.1, Issue 5, February 2006, Document ID: [2] Installing the Avaya G650 Media Gateway, Release 3.1, Issue 1, February 2006, Document ID: [3] Using the Avaya Enterprise Survivable Servers (ESS), Issue 2, February 2006, Document ID: [4] How to Configure an IP Connect High Reliability Configuration using Avaya S8700-Series Media Servers, IPSI and Media Processor Duplication, Avaya Solution and Interoperability Test Lab. 30 of 31

31 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 31 of 31