Avaya Call Management System High Availability User Guide

Transcription

1 Avaya Call Management System High Availability User Guide March 2013

2 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support website: Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products or pre-installed on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants you a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to you. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. License type(s) Designated System(s) License (DS). End User may install and use each copy of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Named User License (NU). You may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software currently available for license from Avaya is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or (in the event the applicable Documentation permits installation on non-avaya equipment) for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Software may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Software ( Third Party Terms ). Information regarding distributed Linux OS source code (for those product that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya s website at: You agree to the Third Party Terms for any such Third Party Components. Preventing Toll Fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com.

3 Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support website: Contact Avaya Support See the Avaya Support website: for product notices and articles, or to report a problem with your Avaya product. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: scroll to the bottom of the page, and select Contact Avaya Support.

4

5 Contents Preface Purpose Intended users Overview Conventions and terminology Reasons for reissue Documentation Web sites Support Introduction HA server switch-over after a failure event Dual ACD links Increased data availability Primary and secondary CMS servers CMS HA server maintenance CMS recovery kit Recovery kit contents Recovery kit software components Connectivity considerations for CMS server switch-overs Administration operations auto-synchronized by the communication server.. 22 Administration operations requiring manual synchronization Administration operations synchronized by backups and restores Operations requiring data collection to be turned off User scenarios Modifying agent trace Upgrading the CMS base load Modifying call work codes Modifying agent skills Creating custom reports Creating designer reports Modifying the Dictionary Administering exceptions Turning External Call History on and off Administering forecast data storage allocation Administering Forecasting report data Synchronizing main menu additions Avaya CMS High Availability User Guide March

6 Contents Administering printers Scripting Interactive scripts Automatic scripts Administering shortcuts Setting up the split/skill call profile Synchronizing after data collection is turned on/off Worksheet for synchronizing the CMS servers after turning data collection on/off37 Diagram of synchronizing CMS servers after data collection is turned on/off 40 Running timetables only on the primary server Running timetables on both primary and secondary servers Globally editing timetables to change server ownership Adding or modifying users Removing users Setting user passwords Administering the VDN call profile Administering Avaya Visual Vectors High Availability backup and restore strategy Synchronizing after an unscheduled outage of the primary CMS server Synchronizing after an unscheduled outage of the secondary CMS server Appendix A: CMS backups and restores Backup and restore procedures Avaya CMS backup strategy Labeling the backup volume Backup information format How to interpret backup information Appendix B: Items excluded from a CMSADM backup Appendix C: Items backed up during a full maintenance backup Appendix D: Restore characteristics of different data types Appendix E: What to do if an Avaya CMS server fails Primary CMS server Secondary CMS server Both CMS servers Avaya CMS High Availability User Guide March 2013

7 Contents Appendix F: Frequently asked questions Appendix G: Avaya CMS base load upgrade procedure for High Availability systems 67 Index Avaya CMS High Availability User Guide March

8 Contents 8 Avaya CMS High Availability User Guide March 2013

9 Preface Avaya Call Management System (CMS) is an application for businesses and organizations that use Avaya communication servers to process large volumes of telephone calls using the Automatic Call Distribution (ACD) feature. Avaya CMS supports solutions for routing and agent selection, multi-site contact centers, remote agents, reporting, interfaces to other systems, workforce management, desktop applications, system recovery, and quality monitoring. Avaya CMS is part of the Operational Effectiveness solution of the Avaya Customer Interaction Suite. This section includes the following topics: Purpose on page 9 Intended users on page 9 Overview on page 10 Conventions and terminology on page 10 Reasons for reissue on page 11 Documentation Web sites on page 11 Support on page 12 Purpose The purpose of this document is to describe how to install and maintain your CMS High Availability (HA) system. Intended users This document is written for: Avaya support personnel Avaya factory personnel Contact center administrators Avaya CMS High Availability User Guide March

10 Preface Users of this document must be familiar with Avaya CMS, the Solaris operating system, and the RHEL(Linux ) operating system. Overview This document includes the following topics: Introduction on page 15 Provides an overview of an Avaya HA system. Primary and secondary CMS servers on page 19 Outlines the Avaya HA maintenance procedures. User scenarios on page 27 Describes how to perform normal CMS tasks in a HA configuration. High Availability backup and restore strategy on page 49 Describes how to recover a HA system after an unscheduled outage. Conventions and terminology If you see any of the following safety labels in this document, take careful note of the information presented. 10 Avaya CMS High Availability User Guide March 2013

11 Reasons for reissue CAUTION:! CAUTION: Caution statements call attention to situations that can result in harm to software, loss of data, or an interruption in service. WARNING: DANGER:! WARNING: Warning statements call attention to situations that can result in harm to hardware or equipment.! DANGER: Danger statements call attention to situations that can result in harm to personnel.! SECURITY ALERT: SECURITY ALERT: Security alert statements call attention to situations that can increase the potential for unauthorized use of a telecommunications system. Unless otherwise specified, all information and procedures in this document apply to the Sun SPARC T4-1, Sun SPARC Enterprise T5120, Sun SPARC Enterprise T5220, Sun Netra X4270, and the Dell R620 hardware platforms. Unless specified otherwise, the term CMS always implies Avaya Call Management System.The term communication server refers to an Avaya switch. Reasons for reissue This document includes the following update: Support for the new Sun SPARC Enterprise T4-1 hardware platform and the new Dell R620 hardware platform for new installations. Documentation Web sites All CMS documentation can be found at New issues of CMS documentation will be placed on this Web site when available. Use the following Web sites to view related support documentation: Information about Avaya products and service Sun hardware documentation Avaya CMS High Availability User Guide March

12 Preface Dell hardware documentation Support Contacting Avaya technical support Avaya provides support telephone numbers for you to report problems or ask questions about your product. For United States support: For international support: See the Support Directory listings on the Avaya Web site. Escalating a technical support issue Avaya Global Services Escalation Management provides the means to escalate urgent service issues. Information required for High Availability technical support Identify yourself as a Avaya CMS High Availability customer and be prepared to give the following information: Your full name, your organization, and a phone number where an Avaya representative can contact you about the problem The installation location (IL) number The IL number is a 10-digit number that helps identify the details of your Avaya CMS High Availability installation and environment Your ACD and CMS release information Whether the problem is with the primary CMS server or the secondary CMS server CPU type and speed Microsoft Windows operating system version (if using Avaya CMS Supervisor) A description of the problem The type of service contract your organization has with Avaya, if any 12 Avaya CMS High Availability User Guide March 2013

13 Support Whether you have a Business Communication Solutions and Integration (APS) contract related to the High Availability option If your system is not covered by warranty or a service contract, you will be charged for the Helpline troubleshooting. If you are uncertain about the details or expiration date of your service contract, contact your Avaya sales representative. Avaya CMS High Availability User Guide March

14 Preface 14 Avaya CMS High Availability User Guide March 2013

15 Introduction The primary purpose of the Avaya CMS High Availability (HA) option is to ensure an uninterrupted data stream between the communication server and the CMS server. With HA, two CMS servers are connected to one communication server, thereby eliminating the traditional single point of failure between the CMS and the communication server. Refer to the product documentation for your CMS load for more information about supported communication server releases. Both CMS servers collect data independently from the communication server. With few exceptions, both CMS servers provide full CMS capabilities. If either server fails, loses connection to the communication server, or must be brought down for maintenance, the alternate server can carry the entire CMS activity load. You must administer both CMS servers with an identical CMS setup including number of ACDs in the configuration, data storage allocation, users, and features. The Avaya Professional Services (APS) organization offers a package that automates the synchronization between the two CMS servers. The auto-sync offer reduces the amount of time needed to maintain the HA servers and is required for most installations. For more information, contact APS at: In the United States Outside the United States As an alternative to the auto-sync offer, the HA option relies heavily on manual data synchronization between the two CMS servers, as well as on manual administration synchronization. This document provides detailed descriptions of procedures needed to maintain synchronization between the two CMS servers. This section includes the following topics: HA server switch-over after a failure event on page 16 Dual ACD links on page 16 Increased data availability on page 17 Avaya CMS High Availability User Guide March

16 Introduction HA server switch-over after a failure event For customers who require continuous access to their CMS data, HA systems allow for the redirection of LAN traffic related to CMS clients and peripheral devices from the primary server to the secondary server. Switch-over from the primary server to the secondary server can be performed when the primary server experiences a major failure event. However, an HA switch-over should be performed only when the anticipated down time for the primary server is expected to be significant. Each call center network is configured according to its own unique specifications. Therefore, each HA customer must develop their own customized criteria and plans for server switch-over events. The CMS HA option allows the following server switch-over options: No switch-over If you do not require continuous access to your CMS data, you can elect not to switch-over to the secondary server after the primary server experiences a major failure event. When the primary server goes down, uninterrupted collection of call data will continue on the secondary server, but you may not be able to access that data until the primary server is restored. Manual server switch-over If you require uninterrupted access to CMS data, server switch-over can be performed manually. At a minimum, manual switch-over entails the individual editing of CMS supervisor clients by their individual users in order to redirect them from the primary to the secondary server. Also, if the primary server is connected to one or more NTS servers, significant effort may be required to manually switch the NTS devices over to the secondary server. For more information about manual server switch-overs, see Appendix E: What to do if an Avaya CMS server fails on page 63. Dual ACD links Duplicate hardware is a key component of the High Availability system. The function of the duplicate hardware is to eliminate a single point of failure in order to prevent data loss due to hardware failures. The dual ACD link feature addresses ACD link failures and builds on the increased ACD link reliability provided by TCP/IP. A C-LAN circuit pack or an ethernet port provides TCP/IP connectivity between the communication server and the CMS server. Each ACD link requires a separate C-LAN circuit pack or ethernet port which supports different network routes to eliminate as many single points of failure as possible. 16 Avaya CMS High Availability User Guide March 2013

17 Increased data availability The ACD Call Processing software sends duplicate data to both CMS servers simultaneously. Thus, both CMS servers will collect identical real-time, historical, and call record data. Furthermore, both CMS servers are able to perform call center and agent administration, and the results are communicated from the communication server back to both CMS servers. However, we strongly recommend performing administrative functions at only the primary CMS server. An idealized schematic of the network links between each of the dual ACD CLAN cards on a communication server and their respective CMS HA servers is shown in the following figure. CMS primary To network CMS secondary Increased data availability The CMS High Availability option increases the availability of your CMS data by means of the following functions and features: ACD link failures In the recommended HA configuration, ACD data is transmitted across different C-LAN circuit packs or ethernet ports within the communication server and across different network subnets, thereby reducing the number of potential single points of failure. If one ACD link fails, data collection continues on the second CMS server. You will use the maintenance backup and restore process to recover the missing data onto the CMS server that was connected to the down ACD link. Avaya CMS High Availability User Guide March

18 Introduction CMS hardware failures The CMS High Availability option provides a duplicate CMS server. If a hardware failure occurs on one CMS server, data collection continues on the second CMS server. You can use the maintenance backup and restore process to recover the missing data onto the server that failed. If the CMS system fails, you may need to restore the CMSADM backup. Since you can perform a CMSADM backup with data collection on, you can expect a good CMSADM backup and the system can be recovered more quickly. Power failures The primary and secondary servers should be separately connected to individual uninterruptible power supplies (UPS) on separate protected power circuits. This configuration ensures that both servers will not be simultaneously disabled due to a localized power failure. However, in the event of an extended power outage, impacted servers should be shut down in order to prevent UPS failure and consequent possible data corruption on the server. CMS software failures The CMS software application is duplicated. If the CMS application fails or a CMS data collection process fails on one CMS server, data collection continues on the second server. The maintenance backup and restore process is used to recover the missing data onto the CMS server that experienced the software failure event. CMS maintenance Data is not lost during either a CMSADM backup or a maintenance backup. Also, data is also not lost when restoring a maintenance backup, as long as local system administration data is not being restored. CMS full version upgrades In a High Availability configuration, one CMS server continues to collect data while the other CMS server is upgraded to the new CMS version. After the first CMS server is upgraded, data collection is turned on for the upgraded CMS server. The second CMS server is then upgraded while the upgraded CMS server continues with data collection turned on. After the second CMS server is upgraded, data collection is turned on for the second CMS server and the data is restored between the two CMS servers. If you upgrade the communication server with a new release, the interval of data loss is limited to the amount of time it takes to administer the latest contact center release on the communication server, and pump-up the ACD link. For more information, see Upgrading the CMS base load on page Avaya CMS High Availability User Guide March 2013

19 Primary and secondary CMS servers When the Avaya CMS High Availability offer is installed, one CMS server is designated as the primary server, and the other is designated as the secondary server. It is highly recommended that you perform administration only on the primary CMS server, and administer the secondary CMS server only when the primary is not functioning. In order to avoid possible confusion, the two servers should be clearly labeled as primary or secondary. The primary and secondary servers are identical, with the following exceptions: Primary CMS server Might have Internet Call Center installed Timetables turned on Secondary CMS server Does not ever have Internet Call Center installed Timetables turned off, except for incremental and full backup timetables and any others you want to run on both CMS servers. For more information about running timetables, see Running timetables only on the primary server on page 41. Both CMS servers collect data from the communication server, but operate independently from each other. Both servers provide full CMS capabilities except for the differences listed above. Should either server fail, lose connection to the communication server, or need to be shut down for maintenance, the alternate server can carry the entire CMS activity load. The following operational practices are strongly recommended: Always perform administration functions on the primary CMS server. Performing administration on both servers could lead to synchronization problems and loss of historical and/or administration data. No users should be logged into the secondary CMS server while the primary CMS server is operational. If the primary CMS server experiences a failure event, your ability to switch CMS users over to the secondary server will depend on your site-specific switch-over strategy, as discussed in HA server switch-over after a failure event on page 16. The benefit to creating and following a routine where you always perform administration on the primary CMS server and transfer (synchronize) the data to the secondary CMS server is that you will be more likely to synchronize your data correctly. This section includes the following topics: CMS HA server maintenance on page 20 CMS recovery kit on page 21 Avaya CMS High Availability User Guide March

20 Primary and secondary CMS servers Connectivity considerations for CMS server switch-overs on page 21 Administration operations auto-synchronized by the communication server on page 22 Administration operations requiring manual synchronization on page 22 Administration operations synchronized by backups and restores on page 24 Operations requiring data collection to be turned off on page 25 CMS HA server maintenance In order to assure that both CMS servers are able to accept and process data correctly from the communication server, the administrator must perform the following functions on a daily basis for both CMS servers: 1. Verify that all links to both CMS servers are up. 2. Verify that archiving is occurring on both CMS servers. a. Select Maintenance > Archiving Status from the CMS menu. b. Press Enter to access the action list in the top right corner of the Maintenance: Archiving Status window. c. Press Enter again to view archive status information for all ACDs. 3. Verify that daily backups have run by selecting Maintenance > Backup Data from the CMS menu. At the top of the Maintenance: Backup Data window, information similar to the following example is displayed: Backups completed today: 1 Status: Last backup finished at 10/02/00 00:23:41 4. Check the customer error log on both CMS servers for unusual errors. The maintenance procedures listed above are not unique to the CMS High Availability offer. Therefore, you are probably already accustomed to performing these maintenance procedures on your previous CMS installation. CAUTION:! CAUTION: Failure to adhere to the maintenance practices listed above may result in: - Unnecessary loss of CMS data - Additional administrative charges from Avaya technical support 20 Avaya CMS High Availability User Guide March 2013

21 CMS recovery kit CMS recovery kit The recovery kit consists of the backup media and original software that the Avaya service organization needs to restore service to your system when problems occur. Store this kit in a secure location to minimize the time your system is out of service. This section includes the following topics: Recovery kit contents on page 21 Recovery kit software components on page 21 Recovery kit contents Your CMS recovery kit should include the following: The latest CMSADM file system backup tapes The latest full maintenance backup tapes The patch CD-ROMs and tapes Recovery kit software components A number of software media are shipped with CMS. You must store this software with the recovery kit. Refer to the product software installation guide for your specific CMS release for more information about the specific software and software versions required for system recovery. CMS requires the following software media: Operating System DVD Avaya Call Management System DVD (for specific OS) Connectivity considerations for CMS server switch-overs For customers who require continuous access to their CMS data, HA systems allow for the re-direction of LAN traffic related to CMS clients and other peripheral devices. Switch-over from the primary server to the backup server can be performed when the primary server experiences a major failure event and the anticipated down time is expected to be significant. Avaya CMS High Availability User Guide March

22 Primary and secondary CMS servers The switch-over from primary to secondary server must be done manually. The amount of effort required for the switch-over will depend on the nature of your network configuration and the type and number of CMS client and peripheral devices to be re-directed to the secondary server. For issues and procedures associated with the switch-over from the primary to the secondary HA server, see Appendix E: What to do if an Avaya CMS server fails on page 63. Administration operations auto-synchronized by the communication server Some of the CMS administration changes made on either of the HA servers will be automatically synchronized on the other server via the communication server. Call center administration changes that are auto-synchronized via the communication server include: Changes to VDN Skill Preferences VDN assignments Vector contents Agent Administration changes that are auto-synchronized via the communication server include: Multi-agent skill change Change Agent skills Administration operations requiring manual synchronization You cannot synchronize the following operations between the two CMS servers using the backup and restore process. Instead, you must perform these operations manually on each CMS server. Agent administration Agent trace administration Activate agent trace 22 Avaya CMS High Availability User Guide March 2013

23 Administration operations requiring manual synchronization Administration (other) Agent exceptions Split/Skill exceptions Trunk group exceptions VDN exceptions Vector exceptions UNIX administration Administering passwords Scripting and Timetables Create Supervisor scripts (from a supervisor login) Scheduling of time tables Note: Note: The timetable window includes the following run options: This timetable will run on this or another CMS server < > Run only on this CMS server* < > Run on this or another CMS server* System setup In some cases, running timetables on both servers is not desirable. For example, when a timetable specifies printing of very large reports, running the timetables on both servers would result in duplicate printings. If an administered timetable should be run only on the current server, select the Run only on this server* option. However, be aware that any timetables set up to run only on the primary server must be manually revised before they will run on the secondary server. Changing the CMS state Data storage allocation External application state External Call History state Load Pseudo ACD data Pseudo ACD setup Storage intervals Turning data collection on and off Avaya CMS High Availability User Guide March

24 Primary and secondary CMS servers Maintenance Data summarizing Call center administration Call work codes User permissions Removing CMS users Call center administration VDN Call Profile Call Work Codes Split/Skill Call Profile Administration operations synchronized by backups and restores The following CMS administration operations can be synchronized between the two HA servers by backing up the CMS server on which the operation was performed and restoring the backup to the other server. Custom reports - additions or modifications to existing reports Avaya CMS Supervisor designer reports - additions or modifications to existing reports Dictionary operations, including: - ACDs - Agent groups - Agent string values - Announcements - AUX reason codes - Calculations - Call work codes - Constants - Custom items - Generic string values - Location IDs 24 Avaya CMS High Availability User Guide March 2013

25 Operations requiring data collection to be turned off - Log in identifications - Log out reason codes - Split/skill string values - Split/skills - Trunk groups - Trunk string values - VDNs - Vectors Main menu additions (additional steps may be required) Timetables - additions or modifications to existing timetables Shortcuts - additions or modifications to existing shortcuts User permissions - ACD access - Feature access - Main menu addition access - Split/skill access - Trunk group access - User data - Vector access - VDN access Operations requiring data collection to be turned off The ability of the CMS High Availability offer to back up, restore, and migrate data with data collection turned on significantly increases system availability. However, a limited number of operations do require data collection to be turned off while they are being performed. You must turn data collection off before performing any of the following procedures: Changing data storage allocation Restoring local system administration data Changing the storage intervals Changing the master ACD For information on performing any of these operations, see Synchronizing after data collection is turned on/off on page 37. Avaya CMS High Availability User Guide March

26 Primary and secondary CMS servers 26 Avaya CMS High Availability User Guide March 2013

27 User scenarios The following user scenarios refer to the Avaya CMS servers as primary and secondary. You should perform your day-to-day administrative functions on the primary CMS server and use the secondary CMS server only when the primary is not operational. The following user scenarios describe how to perform normal CMS tasks in your High Availability configuration so that the CMS servers are kept synchronized. This section includes the following topics: Modifying agent trace on page 28 Upgrading the CMS base load on page 28 Modifying call work codes on page 28 Modifying agent skills on page 29 Creating custom reports on page 29 Creating designer reports on page 29 Modifying the Dictionary on page 30 Administering exceptions on page 33 Turning External Call History on and off on page 33 Administering forecast data storage allocation on page 34 Administering Forecasting report data on page 34 Synchronizing main menu additions on page 35 Administering printers on page 35 Scripting on page 35 Administering shortcuts on page 36 Setting up the split/skill call profile on page 36 Synchronizing after data collection is turned on/off on page 37 Running timetables only on the primary server on page 41 Running timetables on both primary and secondary servers on page 42 Globally editing timetables to change server ownership on page 43 Adding or modifying users on page 45 Removing users on page 45 Setting user passwords on page 46 Administering the VDN call profile on page 46 Avaya CMS High Availability User Guide March

28 User scenarios Administering Avaya Visual Vectors on page 47 Modifying agent trace For maximum reliability, it is recommended that you initiate all agent traces on both the primary and secondary CMS servers. This will ensure that there is a backup for the Agent Trace information in case one of the servers goes down. To modify agent trace: 1. Access the Agent Administration: Activate Agent Trace window on the primary CMS server. 2. Modify the trace on the primary CMS server. 3. Access the Agent Administration: Activate Agent Trace window on the secondary CMS server. 4. Modify the trace on the secondary CMS server. Upgrading the CMS base load When a CMS base load upgrade is performed on High Availability (HA) systems, the upgrade procedure can be performed in a manner that avoids system downtime and synchronizes data between the two HA servers. For a description of the procedure used to perform a base load upgrade on CMS HA systems, see Appendix G: Avaya CMS base load upgrade procedure for High Availability systems on page 67. Modifying call work codes Call work code changes are specific to a CMS server, so any changes made on the primary CMS server must be duplicated on the secondary CMS server. To update call work code items, do the following: 1. Perform the call work code changes you require on the primary CMS server. 2. Perform the call work code changes on the secondary CMS server. 28 Avaya CMS High Availability User Guide March 2013

29 Modifying agent skills Modifying agent skills To change agent skills: 1. Access the Agent Administration: Change Agent Skills window on the primary CMS server. 2. Make the desired skill changes. Note: Note: The skill changes are written to the communication server and subsequently displayed on either CMS server. Creating custom reports CMS High Availability requires custom reports to exist on each CMS server in order to be run on each CMS server. To copy custom reports from the primary server to the secondary server: 1. Create custom report on the primary CMS server. 2. Back up CMS system administration data on the primary CMS server. 3. Put the secondary CMS server in single-user mode. 4. Restore CMS system administration data onto the secondary CMS server. 5. Put the secondary CMS server in multi-user mode. Creating designer reports CMS High Availability requires that designer reports exist on each CMS server in order to be run on each CMS server. Use one of the following three procedures to create designer reports on the secondary server. Method 1: 1. Back up CMS system administration data on the primary CMS server. 2. Put the secondary CMS server in single-user mode. 3. Restore CMS system administration data onto the secondary CMS server. 4. Put the secondary CMS server in multi-user mode. Avaya CMS High Availability User Guide March

30 User scenarios Method 2: 1. On the primary CMS server, copy the designer report to a file on PC or diskette. To copy a designer report from the primary server, perform the following steps: a. From the Supervisor console, either click on the Reports icon, or open the Commands menu and select the Reports option. The Select a Report window is displayed. b. Select the report you wish to copy from the tabbed display of lists (real-time, historical or integrated). c. Click the Copy button located near the bottom of the window. The Copy a Report screen is displayed. d. Select a location to which the report will be saved. 2. On the secondary CMS server, use the Avaya CMS Supervisor Copy function to add the designer report. To copy a designer report onto the secondary server, repeat steps 1a through 1c; when the Copy a Report screen is displayed, select the From a PC file to the CMS Server option. Method 3: Recreate the same designer report on the secondary CMS server. Modifying the Dictionary Dictionary changes are specific to a CMS, so that any changes that are made on the primary CMS server must be duplicated on the secondary CMS server. Choose one of the following procedures: Method 1: on page 30 - Synchronizing Dictionary changes by back up and restore of ACD-specific administration data Method 2: on page 31 - Synchronizing Dictionary changes by backup and restore of specific tables Method 3: on page 33 - Administering the same Dictionary changes on both the primary and secondary CMS servers Method 1: Important:! Important: This procedure is for Dictionary operations made on a single ACD. If you will perform dictionary operations on multiple ACDs, perform the backup for all ACDs and restore for all ACDs. 30 Avaya CMS High Availability User Guide March 2013

31 Modifying the Dictionary 1. Perform the Dictionary operation(s) on the primary CMS server. 2. On the primary CMS server, perform ACD specific administration data backup for the ACD on which you made the changes. Note: Note: There are two Dictionary components that are not backed up using the ACD specific administration data backup: calculations and constants. They are backed up using CMS system administration. 3. Ensure you back up and restore CMS system administration data if you change these Dictionary components. 4. Put the secondary CMS server in single-user mode. 5. Perform ACD specific data restore for that same ACD on the secondary CMS server. 6. Return the secondary CMS server back to multi-user mode. 7. For releases prior to CMS R17, if the Visual Vectors server software is installed on the system, stop and re-start Visual Vectors on the server software in order to activate the new synonym(s) in Visual Vectors. To stop and restart the Visual Vectors software on the server, perform the following steps: a. At the command prompt, enter: setupaas b. Select the run_vvs option from the displayed menu. c. Select option 2 from the turn on/stop menu to stop the Visual Vectors server software. d. To restart the Visual Vectors server software, select option 1. Method 2: Important:! Important: This procedure duplicates Dictionary synonyms and dictionary agent groups using the specific table backup and restore process. The specific table backup and restore process takes less time than using Method 1: on page 30. This process will manually synchronize the two CMS servers using the specific table backup and restore process. 1. Update Dictionary synonyms on the primary CMS server. 2. Perform specific table backup for the synonyms table on the primary CMS server. To select specific tables for backup, use the following procedure: a. Open the CMS main menu and select Maintenance > Backup Data. b. In the Maintenance: Backup data window, select the Specific tables option; all other data options must be de-selected. c. Press Enter to access the action list in the upper right corner of the window. Avaya CMS High Availability User Guide March

32 User scenarios d. Move the cursor to the Select tables option and press Enter once again. e. Select the synonyms and then press Enter to access the Action List in the top right corner of the screen. f. From the action list, select the Modify option, then the Run option. 3. Perform specific table restore for the synonyms table on the secondary CMS server. To select specific tables for backup, use the following procedure: a. Open the CMS main menu, and select Maintenance > Restore Data. b. In the Maintenance: Restore data window, select the Specific tables option. c. Press Enter to access the action list in the upper right corner of the window. d. Move the cursor to the Select tables option and press Enter once again. e. Select the synonyms and then press Enter to access the Action List in the top right corner of the screen. f. From the action list, select the Modify option, then the Run option. 4. For releases prior to CMS R17, if the Visual Vectors server software is installed on the system, stop and re-start Visual Vectors on the server software in order to activate the new synonym(s) in Visual Vectors. To stop and restart the Visual Vectors software on the server, perform the following steps: a. At the command prompt, enter: setupaas b. Select the run_vvs option from the displayed menu. c. Select option 2 from the turn on/stop menu to stop the Visual Vectors server software. d. To restart the Visual Vectors server software, select option Update agent groups on the primary CMS server. 6. Perform specific table backup for the synonyms table (synonyms) and agent groups table (groups) on the primary CMS server. 7. Perform specific table restore for the synonyms and agent groups table on the secondary CMS server. 8. If the Visual Vectors server software is installed on the system, stop and re-start Visual Vectors on the server software in order to activate the new synonym(s) in Visual Vectors. To stop and restart the Visual Vectors software on the server, perform the following steps: a. At the command prompt, enter: setupaas b. Select the run_vvs option from the displayed menu. c. Select option 2 from the turn on/stop menu to stop the Visual Vectors server software. d. To restart the Visual Vectors server software, select option Avaya CMS High Availability User Guide March 2013