Expert Reference Series of White Papers
Avaya Aura Communications
Manager Survivability Simplified
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 2
Avaya Aura Communications Manager Survivability SimplifiedMartha Wightman, Global Knowledge Instructor, AA CM, CMM, SM, SMGR ACSS
IntroductionThe Avaya Aura product line offers many opportunities for communications to survive failures of the IP network or the Avaya equipment. We will focus on the Communication Manager Survivability explanation, implementa-tion, verification, “good to know facts,” and troubleshooting commands.
Survivability ExplanationThe main office CM server hosts the entire customer database of all phones and trunks for the main office and all survivable branch offices on the customer-defined network. All phones and gateways at all the branch locations are actually programmed and controlled by the main office Communications Manager. During main-tenance routines, the main office database changes are saved to the main office and then pushed out to all the branch offices. If the main office becomes “unreachable,” then the branch offices are able to continue to func-tion since they have a complete copy of the main office database.
Figure 1. Figure 1. Survivability Remote Server Failover Scenario – Sunny Day
1 The S8800 server controls the entre system in normal operation (Main and Branch locations)
2 The S8800 server controls the entre system in normal operation (Main and Branch locations)
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 3
Survivability ImplementationIt is important to know the correct installation procedure and nomenclature to be able to install or troubleshoot Survivability. Installation of the Local Survivable Processor (LSP) and Enterprise Survivable Servers (ESS) are covered in the lectures and labs of the following courses Avaya Aura® Communication Manager Implementa-tion (ATI02348IEN), and Avaya Aura® Communication Manager Maintenance and Troubleshooting (5U00040) (see Learn More section below). It is impossible to know everything, so knowing where to get more informa-tion is crucial! Avaya Technical Documentation is available to everyone at support.avaya.com. This white-paper is based on my experience teaching Avaya Communications Manager courses, and the Avaya documentation Avaya Aura Communication Manager Survivability Options, 03-603633, Issue 1, Release 6.0, June 2010.
1 The WAN connection to Branch location 2 fails. The S8800 main server can therefore no longer control this Branch gateway.
2 The G450 in Branch 2 has its own S8300D server configured as an alternate gatekeeper and tries to connect to it and searches for an alternative controller. The S8300D server takes over local control of the gateway in Branch 2.
Figure 2. Survivability Remote Server Failover Scenario – Rainy Day
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 4
Summary of CM Survivability Implementation and Verification 1. Define the S8300D server as a Survivable Remote Server (LSP or ESS)
a. Load System Platform (Linux operating system)
b. Load Solution Template (either Survivable remote or Survivable remote embedded
c. Define System ID, Server ID, and Module ID of survivable server and of the main server through the System Management Interface (server role and network configuration tabs)
- Survivable will register to the main server and get database replication from the main server (Figure 4)
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 5
2. Via putty to H248 gateways
a. Create multi-entry MGC list for H248 gateways
b. Set the transition point in the MGC list
c. Set gateway primary search timer
3. Via ASA through advanced Emulation in Main Server
a. Define the Survivable Remote Server in the main server
b. Set gateway and endpoint timers in relation to the gateway primary search timer
c. Set system parameters maintenance to include sav tran to LSP and ESS
4. Verify Survivable Server is programmed correctly in Main via these commands
a. Display node-names (find out node name of survivable processor and IP)
b. Display survivable-processor _____ (use case-sensitive node name from a)
c. Display system-parameters maintenance (ensure that main saves translations to ESS and LSP during maintenance routines)
d. List survivable-processor (verify that survivable server is registered to main)
e. Save translation all (wait for ok)
f. List survivable-processor (verify that survivable server “save translation” date stamp updates to prove that the main database has been pushed to LSP or ESS)
Good to Know Facts• AnactiveSurvivableRemoteServerfunctionsin“license-errormode,”whichgivestheuser30daysfor
repair and reconnection to the main server.
• Ifthenetworkcomesbackonlinebyitself,andthemainserverbecomesavailable,thegatewayauto-matically connects back to the main server (normal license mode)
• Inpriorreleases,themainserverandtheLSPcouldrundifferentsoftwareversionsbecausebothserv-ers had separate license files. In Release 6.0, the CM_onlyEmbed template and/or CM_SurvRemote template must be of the same software version or later than the software on the main server; therefore, Branches should always be upgraded before upgrading the main server.
• Themainserver’sdateandtimeandtheSurvivableRemoteServershouldnotdifferbymorethanaboutfive minutes. Otherwise, the translation synchronization might fail because of memory requirements.
Useful Troubleshooting Commands in ASA List trace RAS ip-address _____________ (insert LSP or ESS ip-address)
Get forced (ipsi recovery)
For more details of these commands, please see Maintenance Commands for AA™ CM Media Gateway and Servers, AA™ CM Survivability Options, and Administering AA™ CM
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 6
Copyright ©2013 Global Knowledge Training LLC. All rights reserved. 7
Survivability Troubleshooting and MaintenanceThe most important books to get from support.avaya.com to get the job done are listed in Table 1 below.
Document Number Document and File Name555-245-205 AA™ CM Feature Description and Implementation
03-602793 Avaya Aura™ Communication Manager Denial Events
03-603633 AA™ CM Survivability Options
03-300509 Administering AA™ CM
555-245-207 AA™ CM Hardware Description and Reference
03-603444 Installing the Avaya S8800 Server for AA™ CM
03-300430 Maintenance Alarms for Avaya Aura™ Communication Manager,
Media Gateways and Servers03-300431 Maintenance Commands for AA™ CM Media Gateway and Servers
In conclusion, we have covered the Communication Manager Survivability explanation, implementation, verifi-cation, “good to know facts,” and troubleshooting commands. We have covered the documentation and Avaya Communications Manager courses that will help you better understand the Avaya Aura survivability solution.
Learn MoreTo learn more about how you can improve productivity, enhance efficiency, and sharpen your competitive edge, Global Knowledge suggests the following courses:
Avaya Aura® Communication Manager Administration (5U00041)
Avaya Aura® Communication Manager Implementation (ATI02348IEN)
Avaya Aura® Communication Manager Maintenance and Troubleshooting (5U00040)
Visit www.globalknowledge.com or call 1-800-COURSES (1-800-268-7737) to speak with a Global Knowledge training advisor.
About the AuthorI have been in the Telecom Industry since 1994. I love to teach Avaya CS 1000, Communications Manager, System Manager, and Session Manager courses for Global Knowledge. My certifications include Avaya Aura Communication Manager, Communication Server 1000, Communication Manager Messaging, Session Manager, and System Manager.