Avaya Call Management System CMS Upgrade Express and Platform Upgrades

Transcription

1 Avaya Call Management System CMS Upgrade Express and Platform Upgrades Release 18 September 2017

2 2017 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 in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of 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 or on the express behalf of 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 Avaya hardware and software. 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: under the link "Warranty & Product Lifecycle" or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. "Hosted Service" means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK "Avaya Terms of Use for Hosted Services" OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLEON THE AVAYA WEBSITE, UNDER THE LINK "AVAYA SOFTWARE LICENSE TERMS (Avaya Products)" OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. 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 CHANNEL PARTNER; 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. " Software" means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. "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. "Instance" means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ("VM") or similar deployment. License type(s) Designated System(s) License (DS). End User may install and use each copy or an Instance 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, Instance, 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 or an Instance of the Software. Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of 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 is the software contained within the list of Heritage Nortel Products located at under the link "Heritage Nortel Products," or such successor site as designated by Avaya. 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 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, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, 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

3 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. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third party components "Third Party Components" mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ("Third Party Components"), which contain terms regarding the rights to use certain portions of the Software ("Third Party Terms"). As required, information regarding distributed Linux OS source code (for those products 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 products, Documentation or on Avaya's website at: or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components, to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER'S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. 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: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya's security support policies can be found in the Security Policies and Support section of Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( Trademarks The trademarks, logos and service marks ("Marks") displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, 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, Hosted Service(s) 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. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support.

4

5 Contents Chapter 1: Introduction Purpose Intended audience Related resources Documentation Avaya Mentor videos Documentation websites Support Chapter 2: Preparing for the upgrade High-level upgrade process Supported platform upgrades Supported upgrade paths Software-only upgrades Platform upgrades with new hardware Platform upgrades with a VMware deployment Who must perform upgrades Backing up the old system Overview Cleaning the tape drive Backing up system data Performing a CMSADM backup to tape Backing up CMS data Performing a full maintenance backup to tape Backing up new CMS data Performing an incremental maintenance backup Required customer-provided hardware Remote support Troubleshooting and escalation Switch software and link compatibility Software considerations Customization issues Parts list Checking for ACD Recording information about the old system Switch information Authorizations Data storage allocation parameters Storage interval size Avaya CMS Upgrade Express and Platform Upgrades September

6 Contents Data storage allocation for Forecasting Recording Master ACD for clock synchronization Printer administration Storage interval data Preserving the CMS authentication file Chapter 3: Extracting data from the old system Preparing to extract data to tape Preparing to extract data to a USB storage device Verifying the USB storage device is recognized by CMS on Linux Preparing to extract data to a network mount point Configuring an NFS server Linux NFS server configuration Extracting customer data Chapter 4: Implementing the new system Installing and provisioning the new system Installing Avaya OA software (optional) Installing and administering unpreserved third-party and custom software Chapter 5: Replacing disk drives Prerequisites Replacement procedures Disk drive diagrams Dell R620 front panel Dell R720 front panel HP 380P G8 front panel Labeling the old disk drives Removing the disk drives Installing new disk drives Installing the CUE flash image Installing the CUE kickstart image on Dell or HPE platforms Mounting an extract device Mounting a USB storage device on Linux Mounting an NFS mount point on Linux Checking the status of the extract device Performing a manual boot to the CUE Bootable disc Chapter 6: Copying and activating the customer s administration and options Upgrading the CMS load (optional) Avaya CMS Upgrade Express and Platform Upgrades September

7 Contents Removing the current CMS load (optional) Installing CMS on Linux (optional) Authorizing new hardware Upgrading Avaya CMS Supervisor Web for Linux (optional) Copying customer data Activating customer options Recovering from failed installation scripts Scripts that can be skipped and installed later Failures that require escalation to support Failures that occur when adding features Removing temporary ACD 1 (optional) Turning on CMS Starting the CMS Supervisor Web client Web client certificate management Testing access to the Supervisor Web client Configuring Access Security Gateway Verifying that CMS is operating Updating the ECH public key file Updating the switch setup Updating unmeasured trunks Updating storage interval data Checking manual merge discrepancies Removing the upgrade files Authorizing ODBC Connections Migrating customer data Copying the full maintenance backup with the RTC or RTM tools Copying the full maintenance backup with the RTC tool Copying the full maintenance backup with the RTM tool Migrating system administration data Migrating agent and call center administration data Verifying auto-boot is set to true Replacing the customer s media Configuring alarming options Turning the upgraded system over to the customer Appendix A: Blank data forms General information CMS authorizations Avaya CMS Upgrade Express and Platform Upgrades September

8 Contents ACD configuration setup Data storage allocation Storage intervals Backup device Appendix B: Data migration tables All tables combined System administration tables Agent/call center administration tables Historical tables Tables not migrated Index Avaya CMS Upgrade Express and Platform Upgrades September

9 Chapter 1: Introduction Purpose This document describes how to upgrade an Avaya Call Management System (CMS) Release R15 or later deployment to a CMS Release 18 (R18) deployment. The upgrade uses the CMS Upgrade Express (CUE) feature of CMS. CMS R18 supports the following upgrade scenarios: Software-only upgrade re-using the same hardware or VMware deployment. Upgrading old hardware with current hardware being sold with CMS R18 preinstalled. Upgrading old hardware with a CMS R18 VMware deployment. Intended audience This document is intended for implementation engineers and system administrators. Related resources Documentation Table 1: Related documents Title Use this document to: Audience Planning Avaya Call Management System Capacities Determine system capacities when planning to upgrade to a larger server. Sales, implementation engineers Avaya CMS Upgrade Express and Platform Upgrades September

10 Chapter 1: Introduction Table 1: Related documents Title Use this document to: Audience Avaya Call Management System CMS Upgrade Express Customer Requirements Implementing Deploying Avaya Call Management System in an Avaya Customer Experience Virtualized Environment Avaya Call Management System Dell R220, R630, and R730 Hardware Installation, Maintenance, and Troubleshooting Avaya Call Management System HP DL 380P G8 and G9 Hardware Installation, Maintenance, and Troubleshooting Avaya Call Management System Software Installation, Maintenance, and Troubleshooting for Linux Plan the upgrade to new software and hardware. Deploy a new CMS VMware installation. Deploy a new CMS installation on Dell hardware. Deploy a new CMS installation on HPE hardware. Install, maintain, and troubleshoot CMS software on a Linux platform. Implementation engineers and system administrators Implementation engineers and system administrators Implementation engineers and system administrators Implementation engineers and system administrators Implementation engineers and system administrators Avaya Mentor videos Avaya Mentor is an Avaya-run channel on YouTube that includes technical content on how to install, configure, and troubleshoot Avaya products. Go to and perform one of the following actions: Enter a key word in the Search Channel to search for a specific product or topic. Scroll down Playlists, and click the name of a topic to see the available list of videos posted on the site. Avaya CMS Upgrade Express and Platform Upgrades September

11 Documentation websites Documentation websites All CMS documentation can be found at New issues of CMS documentation will be placed on this website when available. Support Visit the Avaya website at for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise. Avaya CMS Upgrade Express and Platform Upgrades September

12 Chapter 1: Introduction Avaya CMS Upgrade Express and Platform Upgrades September

13 Chapter 2: Preparing for the upgrade Before you start a CUE upgrade, use the following checklist of topics to prepare for the upgrade: Topic High-level upgrade process on page 13 Who must perform upgrades on page 16 Required customer-provided hardware on page 22 Remote support on page 23 Troubleshooting and escalation on page 23 Switch software and link compatibility on page 23 Software considerations on page 24 Customization issues on page 24 Parts list on page 24 Checking for ACD 1 on page 25 Storage interval data on page 30 Preserving the CMS authentication file on page 30 High-level upgrade process CMS R18 supports the following upgrade scenarios: Software-only upgrade re-using the same hardware or importing a new OVA for the VMware deployment. Platform upgrades: - Replacing old hardware with new hardware that has CMS R18 preinstalled. - Replacing old hardware with a CMS R18 VMware deployment. Whether you do a software-only upgrade or a platform upgrade, both processes use the CMS Upgrade Express tools to perform the upgrade. Avaya CMS Upgrade Express and Platform Upgrades September

14 Chapter 2: Preparing for the upgrade Supported platform upgrades CMS R18 supports upgrades to the following CMS R18 platforms: Dell R630 with Linux Dell R730 with Linux HPE DL20 G9 with Linux HPE DL380 G9 with Linux VMware with Linux Amazon Web Services CMS R18 does not support upgrades on the Sun SPARC T5120 and Sun SPARC T5220 platforms. The only way to upgrade a T5120 or T5220 system is to upgrade to one of the supported CMS R18 platforms. Supported upgrade paths R18 Supported platforms Existing platforms Dell HPE Vendor Model Release Dell R220 1 Dell R620 Dell R720 DL 380P G8 Currently orderable platforms (see list below) VM Oracle T4 R16.x, R17 X4270 T5120 T5220 R16.x, R17 R16.x, R17 R16.x, R17 NA NA NA NA Platform Upgrade NA NA NA NA Platform Upgrade NA NA NA NA Platform Upgrade NA NA NA NA Platform Upgrade Dell R620 R17 NA CUE NA NA Platform Upgrade R720 R17 NA NA CUE NA Platform Upgrade Platform Upgrade Platform Upgrade Platform Upgrade Platform Upgrade Platform Upgrade Platform Upgrade Avaya CMS Upgrade Express and Platform Upgrades September

15 High-level upgrade process HPE DL 380P G8 Currently orderable R18 platforms available for new sales or platform upgrade HPE DL20 G9 HPE DL380 G9 Dell R630 Dell R730 VM (R18) Amazon Web Services (AWS) R17 NA NA NA CUE Platform Upgrade NA VM R17 NA NA NA NA Platform Upgrade 1. The Dell R220 server is a supported platform in R18 but is not available for new sales after July 11, Though supported in R18, R220 does not have any upgrade paths from the other existing R18 platforms. The EOS link for R220 is Platform Upgrade CUE Software-only upgrades The process for software-only upgrades is as follows: 1. Extract administrative and customer data from the system. 2. Do one of the following: In a non-vmware deployment, replace the disk drives on the server, boot up the system from DVD, and install the CMS software. In a VMware deployment, install the CMS OVA. 3. Copy the administrative and customer data to the new software. 4. Activate the new system. Platform upgrades with new hardware The process for upgrading old hardware with new hardware is as follows: 1. Extract administrative and customer data from the old system. 2. Install the new system that has CMS R18 preinstalled at the factory. 3. Boot up the new system. Avaya CMS Upgrade Express and Platform Upgrades September

16 Chapter 2: Preparing for the upgrade 4. Copy the administrative and customer data to the new system. 5. Activate the new system. Platform upgrades with a VMware deployment The process for upgrading old hardware to a VMware deployment is as follows: 1. Extract administrative and customer data from the old system. 2. Install the CMS OVA on a VMware deployment. 3. Boot up the new system. 4. Copy the administrative and customer data to the new system. 5. Activate the new system. Who must perform upgrades Avaya-approved business partners, with Avaya Support Professional Specialist (ASPS) certification, are authorized to perform CMS implementations and upgrades. Only Avaya-authorized personnel can enable CMS licenses. Important:! Important: If these procedures are performed by nonauthorized personnel, the following consequences might occur: - You might permanently lose data. - The CMS system might be put in a nonfunctioning state for some time. - You might be billed additional time and material expenses by Avaya. Backing up the old system This section includes the following topics: Overview on page 17 Cleaning the tape drive on page 17 Performing a CMSADM backup to tape on page 18 Performing a full maintenance backup to tape on page 20 Avaya CMS Upgrade Express and Platform Upgrades September

17 Backing up the old system Performing an incremental maintenance backup on page 21 Overview To move data from the old system to the new system, the customer must either back up the old system on tape or use NFS backup. NFS backup is supported on CMS R16.2 or later. When backing up to tape on a current platform in preparation for an upgrade to a platform that does not support tape backups, to VMware for example, you will use the Remote Tape Copy (RTC) or Remote Tape Migration (RTM) tools mentioned later in this document. Important:! Important: All tape backups must be completed before calling CMS provisioning. LAN backups cannot be used for data migration in this procedure. This section includes the following topics: Cleaning the tape drive on page 17 Performing a CMSADM backup to tape on page 18 The CMSADM backup is usually done the night before the upgrade. Performing a full maintenance backup to tape on page 20 The full maintenance backup is usually scheduled to run overnight the night before the upgrade. However, if an incremental backup is not being done, run the full maintenance backup just before the upgrade. Performing an incremental maintenance backup on page 21 The incremental backup, if required, is done just prior to the old system being turned over to the technician and remote engineering support personnel. Any data collected after this incremental backup will not be migrated to the new system. Cleaning the tape drive See your computer documentation for instructions on how to clean the tape drive if you are using a tape drive for backup. Backing up system data A backup of the system data must be performed approximately one day before the CMS upgrade. To take a back up of your current system files, choose one of the following procedures: Avaya CMS Upgrade Express and Platform Upgrades September

18 Chapter 2: Preparing for the upgrade If you back up your data directly to a tape device, continue with Performing a CMSADM backup to tape on page 18. If you back up your data to a USB storage device, refer to the section Performing a CMSADM backup to a USB storage device of the Avaya CMS Software Installation, Maintenance, and Troubleshooting for Linux document for information on how to perform CMSADM backups to a USB storage device. If you back up your data to a network mount point, refer to the section Performing a CMSADM backup to a network mount point in the Avaya CMS Software Installation, Maintenance, and Troubleshooting for Linux document for information on how to perform CMSADM backups to a network mount point. Performing a CMSADM backup to tape The CMSADM backup is not service affecting. However, CMS users who are not logged in when the backup starts must wait for the backup to complete before logging in to CMS. To do a CMSADM backup: WARNING:! WARNING: If you are backing up using tape, verify that you are using the correct tape for the tape drive on your system. Many of the tape cartridges look alike, and using the wrong tape can damage the tape drive mechanism and tape heads. 1. Log in as root. 2. Enter: cmsadm The system displays the CMS Administration menu. 3. Enter: 3 Depending on the configuration of your system, the system displays one of the following options. a. If only one tape drive is available on the system, the system displays the following message: Please insert the first cartridge tape into <device name>. Press ENTER when ready or Del to quit: Continue with Step 5. b. If more than one tape drive is available for use by the system, the system displays a list of the tape drives. Avaya CMS Upgrade Express and Platform Upgrades September

19 Backing up the old system 4. Enter a tape drive selection from the displayed list. The system displays the following message: Please insert the first cartridge tape into <device name>. Press ENTER when ready or Del to quit: 5. Press Enter. The backup process starts. If more than one tape is required, the system displays the following message: End of medium on "output". Please remove the current tape, number it, insert tape number x, and press Enter 6. If the system displays the message in Step 5, insert the next tape and allow it to rewind. When it is properly positioned, press Enter. 7. When the backup is completed, the system displays information according to the number of tapes that are required for the backup: If the number of tapes required is one, the system displays the following message: xxxxxxx blocks Tape Verification xxxxxxx blocks WARNING: A CMS Full Maintenance Backup in addition to this cmsadm backup must be done to have a complete backup of the system..... Please label the backup tape(s) with the date and the current CMS version (R3VXxx.x) Continue with Step 10. If the number of tapes required is more than one, the system displays the following message: xxxxxxx blocks Tape Verification Insert the first tape Press Return to proceed : 8. Insert the first tape to be used in the backup and press Enter. Wait for the LED on the tape drive to stop blinking before you remove the tape. 9. When prompted, repeat Step 8 for any additional tapes generated by the backup process. When the final tape is verified, the program displays the following message: xxxxxxx blocks Tape Verification xxxxxxx blocks WARNING: A CMS Full Maintenance Backup in addition to this cmsadm backup must be done to have a complete backup of the system..... Please label the backup tape(s) with the date and the current CMS version (R3VXxx.x) Avaya CMS Upgrade Express and Platform Upgrades September

20 Chapter 2: Preparing for the upgrade 10. Label all tapes with the: Tape number Date of backup Current version of CMS 11. Set the tape write-protect switch to read-only. Backing up CMS data Your CMS data must be backed up approximately one day before the CMS base load upgrade is performed. Use one of the following procedures to perform a full maintenance backup: If you back up your data directly to a tape device, continue with Performing a full maintenance backup to tape on page 20. If you back up your data to a USB storage device, refer to the section Performing a CMS Maintenance Back Up of data to a USB storage device of the Avaya CMS Software Installation, Maintenance, and Troubleshooting for Linux document for information on how to perform CMS data backups to a USB storage device. If you back up your data to a network mount point, refer to the section Performing a CMS Maintenance Back Up of data to a network mount point of the Avaya CMS Software Installation, Maintenance, and Troubleshooting for Linux document for information on how to perform CMS data backups to a network mount point. If you use a CMS LAN backup feature in a non-vmware deployment, refer to the Avaya Call Management System LAN Backup User Guide for information on how to perform CMS data backups using a CMS LAN backup feature. CMS LAN backup is not supported in a VMware deployment. Performing a full maintenance backup to tape A full maintenance backup provides the majority of migration data for the new system. The full maintenance backup is usually scheduled to run overnight the night before the upgrade. However, if an incremental backup is not being done, run the full maintenance backup just before you start the upgrade. To do a full maintenance backup: 1. Log on to CMS. 2. Select Maintenance > Back Up Data from the CMS main menu. The Maintenance: Backup Data window is displayed. Avaya CMS Upgrade Express and Platform Upgrades September

21 Backing up the old system 3. In the Backup Data window, enter the values and select the options that are indicated in the following table: Field Device name Verify tape can be read after backup? ACD(s) to back up Data to back up Value to enter or option to select The device name y All ACDs Local system administration data CMS system administration data ACD-specific administration data Historical data - Full Non-CMS data (if needed) 4. Press Enter to access the action list, and select Run. 5. Label all tapes with the tape number and the date of the backup. Backing up new CMS data You must back up any new CMS data that has been generated since your last CMS data backup. If no new CMS data was collected from the switch since the full maintenance backup was performed, an incremental backup is not required. If no new CMS data has been generated since your last CMS data backup, continue with Required customer-provided hardware on page 22. If new CMS data has been generated since your last CMS data backup, continue with Performing an incremental maintenance backup on page 21. Performing an incremental maintenance backup Perform the incremental maintenance backup just prior to the old system being turned over to the technician and remote engineering support personnel. Any data collected after this incremental backup will not be migrated to the new system. Perform an incremental maintenance backup, using one of the following procedures: If you back up your data directly to a tape device, continue with Step 1. If you use a CMS LAN backup feature, refer to the Avaya Call Management System LAN Backup User Guide for information on how to perform CMS data backups using a CMS LAN backup feature. Avaya CMS Upgrade Express and Platform Upgrades September

22 Chapter 2: Preparing for the upgrade To perform an incremental maintenance backup: 1. Log on to CMS. 2. Select Maintenance > Back Up Data from the CMS main menu. The Maintenance: Backup Data window is displayed. 3. In the Backup Data window, enter the values and select the options that are indicated in the following table: Field Device name Verify tape can be read after backup? ACD(s) to back up Data to back up Value to enter or option to select The device name y All ACDs Local system administration data CMS system administration data ACD-specific administration data Historical data - Incremental Non-CMS data (if needed) 4. Press Enter to access the action list, and select Run. 5. Label all tapes with the tape number and the date of the backup. Required customer-provided hardware You must connect the following hardware to the system and make it operational before you start the upgrade: Monitor Keyboard Mouse Remote access device (Modem, SAL) Avaya CMS Upgrade Express and Platform Upgrades September

23 Remote support Remote support All upgrade procedures are done at the customer site. However, when remote personnel such as CMS Provisioning are supporting the upgrade, the system commands used in this document are done by the remote personnel so they can monitor the progress of the upgrade. Run the commands from the local console only when there is no remote support or when you are instructed to run the commands. Troubleshooting and escalation If problems occur during the upgrade procedure: 1. Escalate the problem through normal channels. 2. Inspect the upgrade log file that is located at /var/log/cvuelog. 3. If the problem persists, shut down the virtual system, reconnect the switch links to the old system, and bring the old system back up under the old CMS load. Switch software and link compatibility CMS R18 supports Communication Manager switch releases 5.2, 6.x, and 7.x. The CUE extract tool recognizes any incompatibility with the switch releases during the upgrade process. The tool requires you to enter a host name or IP address and TCP port before the upgrade can continue. Determine the host name or IP address and TCP port before you start the upgrade. Important:! Important: If the host name or IP address and TCP port information is not known during the CUE upgrade, you can enter fictitious information to get through the upgrade. The switch links do not become active until you update the switch setup information with accurate information. Avaya CMS Upgrade Express and Platform Upgrades September

24 Chapter 2: Preparing for the upgrade Software considerations The Expanded AUX software, at one time separate purchasable items, are now part of the standard CMS package. All features that require authorization will need to be reauthorized as part of the upgrade. You must also go through authorization to adjust any capacity values. Customization issues The upgrade process does not preserve third-party software packages and customizations, such as pseudo-acds. The customer or Avaya Professional services must collect, reinstall, recompile, and reconfigure any nonstandard CMS software after the upgrade is completed and approved. CAUTION:! CAUTION: If Operational Analyst (OA) is installed, you must engage an Avaya resource for reinstallation. OA is a custom application that must be reinstalled after a CUE upgrade. The customer data that the administrator copies during the upgrade procedure includes the following information: License information User login IDs and passwords System name and IP address Printer administration CMS administration, setup, and authorizations For a complete list of the files copied during the upgrade, see the /var/log/cvuelog file after the upgrade is complete. A copy of the old system s /etc/fstab (Linux) is saved in the cvuelog file. Parts list For software-only upgrades where you are reusing the existing hardware, the following parts are delivered to the customer s site: Avaya CMS Upgrade Express and Platform Upgrades September

25 Checking for ACD 1 Upgrade software disc labeled r18cue1x.n Disk replacement media kit with the correct number of blank disks that match the existing hardware. For upgrades where you are installing new hardware, the following parts are delivered to the customer s site: Upgrade software disc labeled r18cue1x.n For upgrades where you are installing CMS on VMware, you do not receive any new hardware or software. You must download and install the software on your VMware deployment as described in Deploying Avaya Call Management System in an Avaya Customer Experience Virtualized Environment. Checking for ACD 1 You cannot upgrade a system when the administrator does not administer ACD 1. To determine whether the system has ACD 1 administered: 1. Log on to CMS. 2. Select System Setup > Switch Setup > List All to display a list of the administered ACDs. This list shows whether ACD 1 is administered. If ACD1 exists, continue with Storage interval data on page 30. If ACD1 does not exist, continue with Step To add temporary ACD 1: a. Enter: cmsadm b. Select the number that corresponds to the acd_create option. This command adds the first unassigned ACD, which is ACD 1. c. Enter the switch name and switch model. Enable vectoring and disconnect supervision. Enter 1 for the local port and enter 1 for the remote port. d. Select TCP/IP for the link device and use an invalid IP address, it is acceptable to assign an invalid IP address since the temporary ACD will be deleted after the upgrade. e. For the remaining options, use the defaults or minimum values. Avaya CMS Upgrade Express and Platform Upgrades September

26 Chapter 2: Preparing for the upgrade Recording information about the old system You must record the following information from the old system to use when you provision the new system: Switch information on page 26 Authorizations on page 27 Data storage allocation parameters on page 27 Storage interval size on page 28 Data storage allocation for Forecasting on page 28 /etc/sysconfig/network-scripts/ifcfg-eth* on page 29 Printer administration on page 29 Storage interval data on page 30 Use the blank forms provided at the end of this document to record this information. See Appendix A: Blank data forms on page 93. Switch information To display switch information about each ACD on the old system: 1. Log on as root. 2. Enter: cmssvc The system displays the CMS Services menu. 3. Enter the option number for swinfo. The system displays a list of the administered ACDs, similar to the following display: Select an ACD 1)acd_number_1 2)acd_number_2 Enter choice (1-2) or q to quit: Avaya CMS Upgrade Express and Platform Upgrades September

27 Recording information about the old system 4. Enter the number that corresponds to the ACD for which you want information. The system displays the switch administration data for the selected ACD. For example: Switch administration for acd 1: Switch name: acd_number_1 Switch model: Communication Mgr R3 Vectoring: y Expert Agent Selection: y Central office disconnect supervision: y Local port: 1 Remote port: 1 Link: TCP/IP acd_number_ Repeat this procedure for each ACD that was administered on the old system. Authorizations The auth_display option allows you to display current CMS authorizations. To display the current CMS authorizations: 1. Enter: cmssvc The system displays the CMS Services menu. 2. Select the auth_display option. The system displays current authorizations for CMS features and capacities. The options for authorization status are as follows: Authorized The feature is purchased, and authorization is turned on. Not authorized The feature is not purchased, or authorization is not turned on. Installed The feature is authorized, and the software to support the feature is installed. For External Call History, the display notes if the feature is on or off. 3. Use the blank form CMS authorizations on page 94 to record the current authorizations. Data storage allocation parameters To check the data storage allocation parameters for each ACD on the old system: 1. Log on to CMS. The system displays the CMS main menu. Avaya CMS Upgrade Express and Platform Upgrades September

28 Chapter 2: Preparing for the upgrade 2. Select the System Setup option. The system displays the System Setup menu. 3. Select the Data Storage Allocation option. The system displays the Data Storage Allocation window. 4. Press F3 (Commands) to display the print menu. Print the window and save the printout. If you cannot print the record, use the blank form Data storage allocation on page 97 to record the information. 5. Press F3, Options > Current ACD, to select another ACD. 6. Repeat this procedure for each ACD. Storage interval size To check the storage interval size for each ACD on the old system: 1. Return to the CMS main menu. If you are already in CMS, press F8 (Main Menu) to display the menu. The system displays the CMS main menu. 2. Select the System Setup option. The system displays the System Setup menu. 3. Select the Storage Intervals option. The system displays the Storage Intervals window. 4. Press F3 (Commands) to display the print menu. Print the window and save the printout. If you cannot print the record, use the blank form Storage intervals on page 98 to record the information. 5. Press F3, Options > Current ACD, to select another ACD. 6. Repeat this procedure for each ACD. Data storage allocation for Forecasting You must check the data storage allocation for the Forecasting package if it is installed on the old system. To check the data storage allocation for the Forecasting package on the old system: 1. Return to the CMS main menu. If you are already in CMS, press F8 (Main Menu) to display the menu. The system displays the CMS main menu. Avaya CMS Upgrade Express and Platform Upgrades September

29 Recording information about the old system 2. Select the Forecast option. The system displays the Forecast menu. 3. Select the Administration option. The system displays the Administration menu. 4. Select the Data Storage Allocation option. The system displays the Data Storage Allocation window. 5. Press F3 (Commands) to display the print menu. Print the window and save the printout. 6. Press F3, Options > Current ACD, to select another ACD. 7. Repeat this procedure for each ACD. Recording Master ACD for clock synchronization You must preserve the master clock ACD information so that you can readminister it after the upgrade: 1. Log on to CMS. 2. Select System Setup > CMS State to display the Master ACD clock information. 3. Record the ACD displayed in the Master ACD for clock synchronization field. /etc/sysconfig/network-scripts/ifcfg-eth* If the old system uses NIS or NISplus, record the networking information for those features. Printer administration Customers moving to Linux who require printers need custom work to set up a printer using Linux cups. Avaya Professional Services can help with setting up a printer on Linux. To check the current printer administration: 1. Use the following command to display a list of administered printers: lpstat -t more 2. Based on the displayed printer names, use the following command to display the printer type and speed for each of the printers: lpstat -p <name> -l more 3. Use Maintenance > Backup/Restore Devices to display the current default printer device. Record that information to administer on the new system. Avaya CMS Upgrade Express and Platform Upgrades September

30 Chapter 2: Preparing for the upgrade If the old system is using network printers, contact Avaya Professional Services for assistance recording information about those printers. Avaya Professional Services reinstalls network printers on the new system. Storage interval data During an upgrade, not all storage interval data is preserved. The majority of the storage interval data is preserved in the storage.def file. However, the information for the data summarizing time, switch time zone offset, and master clock ACD are not part of the storage.def file. To record this information so you can readminister it after the upgrade: 1. Log on to CMS. 2. Select System Setup > CMS State to display the Master ACD clock information. 3. Record the ACD displayed in the Master ACD for clock synchronization field. 4. For each ACD, Select System Setup > Storage Intervals to display the storage interval data for the ACD. 5. Record the Data summarizing time and the Switch time zone offset. You can print the screens to record the data. 6. Repeat Steps 4 and 5 for each ACD. Preserving the CMS authentication file The upgrade process does not preserve the Avaya Access Security Gateway (ASG) Authentication File System (AFS) file. Avaya recommends that you obtain a new AFS authentication file. To obtain an AFS authentication file, refer to the section Installing Access Security Gateway and the CMS Authentication File in the Avaya CMS Software Installation, Maintenance, and Troubleshooting for Linux document. If you obtain a new AFS authentication file prior to the upgrade, then save it to a non-cms destination. If the customer currently uses ASG, perform the steps below to preserve the current AFS authentication file from the original CMS system. However, Avaya recommends that you obtain a new AFS authentication file. If the customer does not currently use ASG but plans to use ASG after the upgrade, you must obtain an AFS authentication file prior to configuring ASG. Do not save the AFS authentication file on the current CMS system of the customer. Save the AFS authentication file to a non-cms destination that is accessible after the cvue_activate procedure is executed. Make a note of the destination path where the AFS authentication file is saved. Avaya CMS Upgrade Express and Platform Upgrades September

31 Preserving the CMS authentication file Note: Note: ASG can be installed and configured independent of the upgrade. If the customer does not currently use ASG and does not plan to use ASG after the upgrade, continue with Extracting data from the old system on page 33. To preserve the CMS authentication file: 1. Verify that you are logged in to the system as root. 2. Copy the AFS authentication file to a destination path that is accessible after the cvue_activate procedure has been executed. Enter: cp -p /etc/asg/lacfile <destination_path>/afs_file.xml Note: Note: The destination path can be a USB device, a network mount point, or another computer that is accessible from the CMS computer. Depending on the destination path, you may require a secure copy. For example, you may need to use scp instead of cp. 3. Verify that the AFS authentication file was copied to the destination directory. 4. Verify that the AFS authentication file properties are consistent with the original file. 5. Continue with Extracting data from the old system on page 33. Avaya CMS Upgrade Express and Platform Upgrades September

32 Chapter 2: Preparing for the upgrade Avaya CMS Upgrade Express and Platform Upgrades September

33 Chapter 3: Extracting data from the old system To minimize the time that CMS is out of service during the upgrade, you can extract the customer s administration and options while the CMS is operating. Important:! Important: Do not allow the customer to make any administration changes once the extract process starts. Important:! Important: When remote personnel such as CMS Provisioning support the upgrade, stop here and contact the provisioning group. When remote personnel support the upgrade, the remote personnel use the system commands in this section to monitor the progress of the upgrade. Run the commands from the local console only when instructed or when there is no remote support. Perform one of the following procedures: If the extract device is a tape drive, continue with Preparing to extract data to tape on page 33. If the extract device is a USB storage device, continue with Preparing to extract data to a USB storage device on page 34. If the extract device is a network mount point, continue with Preparing to extract data to a network mount point on page 37. Preparing to extract data to tape CMS supports backups to tape on any Dell (Linux), or HPE (Linux) deployments. CMS does not support backups to tape on VMware deployments. To extract the customer's administration and options to tape: 1. For the tape being used with the upgrade, check for the following requirements: Ensure that you are using the correct tape. Ensure that the tape is not write-protected. 2. You must read the following Important note before running the command in this step: Avaya CMS Upgrade Express and Platform Upgrades September

34 Chapter 3: Extracting data from the old system Important:! Important: If the system has more than one tape drive, the upgrade program defaults to the tape drive that has a tape installed and that has the lowest SaS ID. To prevent using the wrong tape drive, remove the tapes from any other tape drives. Label the blank tape Upgrade Extract, and insert the tape into the tape drive. 3. Continue with Extracting customer data on page 40. Preparing to extract data to a USB storage device CMS supports backups to USB storage devices on a Dell (Linux), or HPE (Linux) deployments. CMS does not support backups to USB storage devices on VMware deployments. The customer is responsible for the proper configuration of the USB storage device and connectivity to the CMS server. For Dell deployments, the USB storage device must be formatted as ext4. USB storage devices used to extract data must be readable on the new deployment hardware if you are upgrading to new hardware. If you are upgrading on the same hardware, compatibility is not an issue. Important:! Important: It is the responsibility of the customer to ensure that the CMS system detects the USB storage device and users can perform read and write operations to and from the USB storage device. This document provides information as a reference to aid in troubleshooting USB storage device recognition issues but the customer should NOT contact Avaya to resolve any issues with USB storage devices. Instead, the customer system administrator must resolve any USB storage device issues. Ensure you can write to and read from the installed USB storage devices before performing any Maintenance or CMSADM backups. Verifying the USB storage device is recognized by CMS on Linux 1. Insert the USB storage device. Avaya CMS Upgrade Express and Platform Upgrades September

35 Preparing to extract data to a USB storage device 2. Enter: fdisk -l The system displays information similar to the following: Disk /dev/sda: GB, bytes 255 heads, 63 sectors/track, cylinders Units = cylinders of * 512 = bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000537a2 Device Boot Start End Blocks Id System /dev/sda1 * Linux Partition 1 does not end on cylinder boundary. /dev/sda Linux /dev/sda Linux /dev/sda f W95 Ext'd (LBA) /dev/sda Linux swap /dev/sda Linux /dev/sda Linux /dev/sda Linux /dev/sda Linux /dev/sda Linux /dev/sda Linux Disk /dev/sdb: 64.7 GB, bytes 64 heads, 32 sectors/track, cylinders Units = cylinders of 2048 * 512 = bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x The USB device is shown as /dev/sdb. 3. Determine the file system type of the USB storage device. Enter: blkid DevicePath Where DevicePath is the path to the USB device, for example, /dev/sdb. The system displays information similar to the following: /dev/sdb: UUID="40e1a52d-cf6e c4d-f357a8f5eb69" TYPE="ext4" 4. Do one of the following: If the TYPE value is blank, continue with Step 5. If the TYPE value is ext2, ext3, or ext4, continue with Step 6. Avaya CMS Upgrade Express and Platform Upgrades September

36 Chapter 3: Extracting data from the old system 5. Create the ext4 file system on the USB storage device: Enter: mkfs -t ext4 DevicePath Where DevicePath is the path to the USB device, for example, /dev/sdb. CAUTION:! CAUTION: Creating a file system on the USB storage device will overwrite all data on the USB storage device and all data will be lost. Be sure you are certain you want to remove all data on the USB storage device. If you do not want to remove the data on the USB storage device, replace the USB storage device with a different USB device that can be formatted, and restart this procedure from Step 1. Note: Note: Formatting the USB device may take a long time depending on the speed and size of the USB device. The system displays information similar to the following: mke2fs (17-May-2010) /dev/sdb is entire device, not just one partition! Proceed anyway? (y,n) y Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks inodes, blocks blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks= block groups blocks per group, fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, , , , , , , , , , Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done Note: Note: This filesystem will be automatically checked every 28 mounts or 180 days, whichever comes first. Use tune2fs -c or tune2fs -i to override. 6. Mount the USB storage device. a. On the CMS server, create the mount point if the mount point does not exist. Enter: mkdir /CUE_extract_dir Avaya CMS Upgrade Express and Platform Upgrades September

37 Preparing to extract data to a network mount point b. To mount the USB storage device, enter: mount DevicePath /CUE_extract_dir Where DevicePath is the path to the USB device, for example, /dev/sdb. c. To verify USB storage device is mounted, enter: ls -l /CUE_extract_dir The USB storage device directory should display a message similar to the following: drwx root root 8192 Oct 8 15:33 lost+found 7. Continue with Extracting customer data on page 40. Preparing to extract data to a network mount point CMS supports backups to network mount points on all deployments. The customer is responsible for the proper configuration of network mount points and connectivity to the CMS system. Important:! Important: Contact your system administrator before creating any shared mount points or network mount points. It is the responsibility of the customer to determine if any security violations will be made by creating share points and allowing other systems on the network to access the share points. Creating and sharing mount points should only be performed by experienced personnel. It is the responsibility of the customer to ensure that the CMS system detects the network mount point and users can perform read and write operations to and from the network mount point. This document provides information as a reference to aid in troubleshooting network mount point recognition issues but you should NOT contact Avaya to resolve any issues with your network mount points. Instead, contact your system administrator to resolve any network mount point issues. Be sure you can write to and read from network mount points before performing an extract to the mount point. Configuring an NFS server The customer is responsible for the correct configuration and connectivity between the NFS server and CMS system. Keep in mind the following points when you use NFS mounted directories: Avaya CMS Upgrade Express and Platform Upgrades September

38 Chapter 3: Extracting data from the old system The NFS mount point must be accessible from the CMS system. The NFS server must have sufficient disk space for the backup of data. The directory path used when administering an NFS Back Up Device must exist on the NFS server. The following procedures provide basic information about configuring a NFS server and CMS system to support CUE extracts to NFS servers: If the network server is Linux, continue with Linux NFS server configuration on page 38. Linux NFS server configuration Perform the following steps on the Linux network server. Note: Note: Note: These steps are not performed on the CMS system. These steps are performed on the NFS server which must be a separate, non-cms, customer provided Linux computer. 1. On the NFS server, create the network mount point, enter: mkdir /network_server_mt_pt_dir 2. Set the permissions for the network_server_mt_pt_dir, enter: chmod 755 /network_server_mt_pt_dir chown nobody:nobody /network_server_mt_pt_dir Example: chmod 755 /CUE_NFS_dir chown nobody:nobody /CUE_NFS_dir Note: Later, if you are unable to write to the network mount point on the CMS server indicated by a Permission denied message on the CMS server, you will need to set the owner and group to nfsnobody. Enter: chown nfsnobody:nfsnobody /network_server_mt_pt_dir 3. To allow other systems to access the network_server_mt_pt_dir: a. vi /etc/exports b. Append the Linux network mount point information to the bottom of the file: /network_server_mt_pt_dir <CMS_FQDN>(rw,sync) Example: /CUE_NFS_dir trapper1.dr.avaya.com(rw,sync) c. Write and save the file. 4. To configure NFS and portmap to start on reboot: Avaya CMS Upgrade Express and Platform Upgrades September

39 Preparing to extract data to a network mount point Note: a. Log in as root. b. At the command line, enter: ntsysv c. The system starts a GUI interface. Scroll through the list provided and verify that the nfs and portmap options are selected. These two options should be marked with an x. d. Enter TAB to highlight OK. e. Click OK. 5. Starting the NFS service: Note: When the /etc/exports file is changed, you must stop and start the NFS server. a. If the NFS service is not running, enter: /etc/init.d/nfs start b. If the NFS service is running, enter: /etc/init.d/nfs restart 6. To verify the network service is running, enter: service nfs status Perform the following steps on the CMS system. 7. On the CMS system, create the network mount point directory, enter: mkdir /CUE_extract_dir 8. To mount the Linux NFS server, enter the following command on a single line: mount -F nfs -o vers=3 <network_server_ip_address>: /network_server_mt_pt_dir /CUE_extract_dir Example: mount -F nfs -o vers=3 xxx.xxx.xxx.xxx:/cue_nfs_dir /CUE_extract_dir 9. To change to the network server mount point directory, enter: cd /CUE_extract_dir 10. To list the contents of the network server mount point directory, enter: ls -l Note: Note: There should be adequate space on the NFS server to extract the CUE data. The cvue_extract process displays a message showing the amount of space needed for the extracted data after all the extract information has been collected. If there is an insufficient amount of space the available space value will be displayed along with the needed space value. Avaya CMS Upgrade Express and Platform Upgrades September

40 Chapter 3: Extracting data from the old system 11. To unmount a network server mount point directory, enter: umount /CUE_extract_dir 12. Continue with Extracting customer data on page 40. Extracting customer data 1. To begin the extract process, perform one of the following actions: If doing the upgrade from the local console, log in as root. If doing the upgrade remotely: a. Log in as cmssvc. b. Enter the appropriate password. c. Enter: su - root d. Enter the appropriate password. 2. Enter: cd / 3. Insert the upgrade software disc labeled r18cue1x.n. 4. Do the following: On Linux, enter the following commands: mount /dev/dvd /mnt cd /mnt./cvue_extract The extract process starts. The system displays a message similar to the following example: Beginning cvue_extract pre-check. Please wait Pre-check completed. Using /var/tmp/new as temporary directory, space needed is XXXXX blocks. CUE VERSION: r18cue1x.n Current CMS Version is: ryyxx.x 5. The extract process first verifies whether CMS R18 supports the platform you are upgrading. One of the following conditions occur: Avaya CMS Upgrade Express and Platform Upgrades September

41 Extracting customer data If the platform is supported for CUE upgrades, the system displays the following message and the process continues with Step 7. Checking for valid platform (get_server_platform) Your system is a(n) Platform_Type. If the platform is not supported, the system displays a message similar to the following example. You cannot continue with the CUE upgrade: ***WARNING*** You are upgrading from a hardware platform that is not supported by CMS R18. To upgrade to CMS R18, you must install on a new CMS R18 platform that is sized for your capacities, which could include the Dell R730, R630, R220, HP DL380P G9, or VMware. Do not continue if you do not have the proper platform for upgrade available. Do you want to continue? (y or n) : 6. Enter y to continue with the upgrade or n to stop the upgrade until you have the correct hardware ready for the upgrade. 7. The extract process next runs the CMS converter tool. The system displays messages similar to the following example: Continuing with CMS Upgrade Express... Admin data will be saved /var/tmp/new/adminsave/cmsadmin.saved Converter completed successfully. 8. The extract process determines if ACD 1 is administered. One of the following conditions occur: If the system does not display error messages, ACD 1 is administered, and the extract continues with Step 9. If the system displays the following error messages, ACD 1 is not administered, and you must temporarily add ACD 1: ERROR: ACD 1 is currently administered as a skipped ACD. CUE cannot upgrade when ACD 1 is a skipped ACD. Please run cmsadm, add a temporary ACD 1, then run./cvue_extract again. # To add temporary ACD 1: a. Enter: cmsadm b. Select the number that corresponds to the acd_create option. This option adds the first unassigned ACD, which is ACD 1 in this example. Avaya CMS Upgrade Express and Platform Upgrades September

42 Chapter 3: Extracting data from the old system c. Enter the switch name and switch model. Enable vectoring and disconnect supervision. Enter 1 for the local port and enter 1 for the remote port. d. When you select a link device, use TCP/IP with an invalid IP address, Since the ACD is deleted after the upgrade, it is acceptable to assign an invalid IP address. e. For the remaining options, use the defaults or minimum values. f. Return to Step 4 and start the extract process again. 9. CMS R15 or later supports switch releases Communication Manager 5.2 and later. You might need to upgrade the ACDs when you upgrade CMS. The extract process checks each ACD to determine if any of the ACDs are administered with a switch model of Communication Manager 5.0 or earlier. One of the following conditions occur: If this release of CMS supports all the ACDs, the extract continues with Step 16. If any ACD is administered using an unsupported switch model, the system displays messages shown in the following example: The switch release <product><release> administered for <acd_name> (ACD <acd_number>) is no longer supported. Select the model of switch for this ACD: 1) Communication Mgr 5.2 2) Communication Mgr 6.x 3) Communication Mgr 7.x Enter choice (1-3, or q to quit): 10. Enter the upgraded switch model for the ACD. One of the following conditions occur: If another ACD is administered using an unsupported switch model, the extract returns to Step 9. If no other ACDs are administered using an unsupported switch model, the extract continues with Step Enter the host name or IP address of the switch. The system displays messages similar to the following example: You have entered the following TCP/IP information for <acd_name> (ACD <acd number>): ************************************* Host name or IP address: <host_name or IP_address> ************************************* If you would like to make changes to the entry above, enter choice (y or n) (default: n): 12. Perform one of the following actions: Avaya CMS Upgrade Express and Platform Upgrades September

43 Extracting customer data If the assignment is correct, press Enter. The extract continues with Step 16. If the assignment is not correct, enter y. The following messages are displayed and the extract returns to Step 11. CMS Upgrade Express is now returning to TCP/IP information prompts... Revising TCP/IP Host Name <host_name or IP_address> per user request... Enter switch host name or IP Address or q to quit: 13. The system displays the following message: Enter switch TCP port number ( or q to quit): (default: 5001) 14. Enter the switch TCP port number. The system displays messages similar to the following example: You have entered the following TCP/IP information for <acd_name> (ACD <acd number>): ************************************* TCP Port Number: <port_number> ************************************* If you would like to make changes to the entry above, enter choice (y or n) (default: n): 15. Perform one of the following actions: If the assignment is correct, press Enter. The system displays the following message....cms Upgrade Express is updating <acd_name> (ACD <acd number>) with TCP/IP switch information. One of the following conditions occur: - If there are more ACDs that must be converted to TCP/IP, the extract returns to Step If there are no more ACDs that must be converted to TCP/IP, the extract continues with Step 16. Avaya CMS Upgrade Express and Platform Upgrades September

44 Chapter 3: Extracting data from the old system If the assignment is not correct, enter y. The system displays the following messages and the extract returns to Step 14. CMS Upgrade Express is now returning to TCP/IP information prompts... Revising TCP Port Number <port_number> per user request... Enter switch TCP port number ( or q to quit): (default: 5001) 16. Extracting the administration files takes several minutes. When extraction is complete, the system displays the following message: NOTE: Be sure to review the cvuelog for any files to be merged manually in the upgraded system. The extract process determines if Visual Vectors server software is currently installed on the old system. If Visual Vectors server software is detected, the system displays the following message: INFORMATION: CUE has detected the existence of the Visual Vectors package. Visual Vectors is no longer supported for CMS. Files under the /opt/cc/aas/vector directory will NOT be preserved during this upgrade. CAUTION:! CAUTION: CMS does not support Visual Vectors. Inform the customer that they can not use Visual Vectors with the new release of CMS. 17. The extract process determines if alarm administration data needs to be migrated. If the customer has custom alarms, the administration data is preserved. The system displays the following message: Alarm admin data will be migrated. Alarm logs will be preserved. 18. The extract process continues and the system displays the following message: NN blocks NNNNN blocks Avaya CMS Upgrade Express and Platform Upgrades September

45 Extracting customer data 19. The extract process continues and the system displays the following messages:... CMS default backup device will be checked. Serial printers will be administered 20. The extract process continues and the system displays the following messages: Merging cvue_file_properties with cvuelog Copying admin data. Need XXXXX blocks to save admin data Important:! Important: The above message displays the amount of available space needed on the extract device for the extract process to successfully write the extract file to the extract device. The extract process fails If there is not sufficient space on the extract device. Verify that the extract device has the amount of space that displayed in the above message. 21. The extract process prompts you to select an extract device type: Choose an extract device: 1) Tape 2) Other Enter choice (1-2): If the extract device is a tape drive, enter the number associated with the Tape option and continue with Step 22. If the extract device is a USB storage device or a network mount point, enter the number associated with the option Other and continue with Step The system displays the following message about supported tape drives: ##### WARNING ##### Only the following tape drives will be supported in CMS 18: 40+ GB Tape drive You must use a supported tape drive to continue with the CUE upgrade. Enter (q) to quit, any other key to continue: 23. Perform one of the following actions: Avaya CMS Upgrade Express and Platform Upgrades September

46 Chapter 3: Extracting data from the old system Tip: If the tape drive you are using is not supported, press q. You cannot do a CUE upgrade. Escalate through Avaya support. If the tape drive you are using is supported, press Enter to continue. Tip: To track the progress of the extract from a different XTERM window, from a remote terminal, or from a local terminal, use the following command: tail -f /var/tmp/new/var/log/cvuelog 24. The extract process checks the tape and the tape drive to determine if the tape is defective, write-protected, or not compatible with the tape drive. The system displays a message similar to the following: Testing tape on /dev/rmt/n.. Note: Note: For Linux, the tape device is /dev/stn, where N is the device number. 25. One of the following conditions occur: If the tape and tape drive are operational, the system does not display any error messages and the extract continues with Step 27. If the tape or tape drive are not operational, the system displays messages similar to the following example: tar: /dev/rmt/n: Permission denied Tape test failed!! Could not write and then read a file from the tape at /dev/rmt/n. Check the following items for possible problems: Verify the tape is not write-protected Verify the correct type of tape is in the tape drive Verify the tape is not defective /cvue_extract[982]:tapetestfailed:not found Ensure that the tape is not write-protected and the tape is the correct tape for the tape drive. Clean the tape drive or using a different tape and start over with Step Enter the extract device path. Avaya CMS Upgrade Express and Platform Upgrades September

47 Extracting customer data CAUTION:! CAUTION: When using a USB storage device or a network mount point, the extract device path must exist on the CMS server and must be mounted. If the USB storage device or network mount point do not exist or not mounted, the extract will fail. 27. The extract process writes the Administration data to the extract device. The system displays messages similar to the following example: Admin data will be saved to /dev/rmt/n Extract complete. 28. The extract process determines if the OpenBoot PROM (OBP) must be patched. The system displays the following messages: Now checking for the need to update the OBP. If the OBP is found to be in need of patching, the patch will be installed and the system WILL be rebooted. You can continue your CUE upgrade after the reboot. Pausing briefly The system displays the following message when extract process completes: The cvue_extract process is complete. Warning: you must close all applications before running this script Patch configuration started: <time stamp> 30. No action is required for this step, but depending on your software version and platform, the system displays one of the following messages: If OBP is up-to-date, the system displays messages similar to the following example: There are no Linux patches to install. Avaya CMS Upgrade Express and Platform Upgrades September

48 Chapter 3: Extracting data from the old system Tip: Tip: If the extract device is tape and the system needs to be powered on manually, perform Step 31. Spooled <patch number> Linux patches have been spooled to your machine. The patches will be installed after rebooting. During the installation of patches your server will not be available. The estimated time to install all patches is: xx minutes Ready to install Patches. Please leave the CD in the drive. Rebooting... Patch configuration completed: <time stamp> Shutdown started. <time stamp> Changing to init state 6 - please wait Broadcast Message from root (pts/4) on <hostname> <time stamp>... THE SYSTEM <hostname> IS BEING SHUT DOWN NOW!!! Log off now or risk your files being damaged 31. If the extract device was a tape drive, remove the tape, set the write-protect switch on the tape to read-only, and reinsert the tape. 32. If an OBP update was performed, log into the system as root. 33. Enter the following commands: cd /var/tmp/new/adminsave/init.d ls -l Verify that the directory contains upgrade scripts. If the scripts do not exist, check for free space on the server. Reboot the server and retry the extract. You can run the extract locally instead of remotely. If the scripts do not exist again after rebooting and retrying the extract, escalate to Avaya support. 34. Enter: more /var/tmp/new/var/log/cvuelog The system displays the temporary upgrade log file. Check for failure messages (FAIL) or other indications that the extract process did not successfully complete. This file also contains a list of files that are copied to the new system. The list of files can be useful for later troubleshooting. Avaya CMS Upgrade Express and Platform Upgrades September

49 Extracting customer data Important: 35. Enter: ls -l /var/tmp/new/adminsave/cmsadmin.saved If the files setup.out, fp.install, and stor.def do not exist or have a file size of zero, escalate though normal channels. 36. If the CMS configuration includes data collection by Avaya Operational Analyst (OA), the data forwarders must be turned off. Use one of the following command to determine if OA is installed: On a Linux deployment, enter: rpm -q AOA! Important: If OA is present, verify that an engineer is engaged to reinstall OA. If an engineer is not engaged to reinstall OA, abort the upgrade and contact the customer and the project manager. 37. If the system displays OA processes, enter the following commands to turn off the data forwarders:. /opt/bi/.profile pa stop all For more information about Avaya OA forwarders, see Avaya OA Maintenance and Troubleshooting. 38. Continue with one of the following procedures: If you are implementing new hardware or VMware as part of the upgrade, continue with Implementing the new system on page 51. If you are implementing new hardware or VMware as part of the upgrade, or if the new system is already implemented, continue with Replacing disk drives on page 53. Avaya CMS Upgrade Express and Platform Upgrades September

50 Chapter 3: Extracting data from the old system Avaya CMS Upgrade Express and Platform Upgrades September

51 Chapter 4: Implementing the new system This section contains the procedures used to implement the new system when you are replacing the old hardware or deploying CMS on VMware. Skip this section if you are not replacing hardware or deploying VMware. Installing and provisioning the new system Avaya field technicians or authorized representatives install the new system during normal business hours using one of the following documents: Deploying Avaya Call Management System in an Avaya Customer Experience Virtualized Environment Avaya Call Management System Dell R220, R630, and R730 Hardware Installation, Maintenance, and Troubleshooting Avaya Call Management System HP DL 380P G8 and G9 Hardware Installation, Maintenance, and Troubleshooting While the technicians are installing the new system, the customer can run backups on the old system. See Backing up the old system on page 16 for more information. Installing Avaya OA software (optional) If the CMS configuration includes data collection for Avaya OA, you must install an R18-compatible version of the Avaya OA data collection software. Contact your Avaya account team or Avaya Sales to get the latest OA software that supports CMS R18. See Avaya OA Installation and Configuration for more information. Avaya CMS Upgrade Express and Platform Upgrades September

52 Chapter 4: Implementing the new system Installing and administering unpreserved third-party and custom software After the upgrade, you must contract with Avaya to install any third-party software and administer any new features or services. The following table lists several of these features and services and the Avaya organizations that are responsible for completing the work. Feature or service Responsible 1 Operational Analyst, including restarting forwarders Network information names service, such as NIS or NISplus Network printers Pseudo-ACDs. Pseudo-ACDs must be added and data must be migrated from the old system. Applications such as workforce management software. Wallboards Mounted file systems that were in the customer s /etc/fstab (Linux) before the upgrade. See the copy of the file that is saved in / var/log/cvuelog. Have your administrator verify that your new configuration is correct. Common Desktop Environment options such as screen layout and password protection Add, change, or remove ACDs Add Supervisor logins Install new feature packages (if purchased) Change authorizations Update security options such as rsh and rlogin. Access Security Gateway (ASG) Avaya Professional Services Avaya Professional Services Avaya Professional Services Avaya Professional Services Avaya Professional Services Avaya Professional Services Provisioning Provisioning Provisioning Provisioning Provisioning Provisioning Avaya Professional Services or Customer Provisioning 1. Outside the United States, Avaya distributors are responsible for these items, with assistance from the COE. Avaya CMS Upgrade Express and Platform Upgrades September

53 Chapter 5: Replacing disk drives This section contains procedures required when re-using existing hardware to upgrade to CMS R18. Using these procedures, you label and remove the old disk drives in the computer and replace the disk drives with new blank disk drives that will be upgraded with new CMS R18 software during the upgrade process. CAUTION:! CAUTION: Customers must not reuse their old disk drives as part of the upgrade procedure. Customers must save the old labeled disk drives to use them for system recovery in case any problems occur during the upgrade procedure. Prerequisites Obtain an Electrostatic discharge (ESD) wrist strap before starting this procedure. Replacement procedures To replace the disks, use the following procedures. Procedure Disk drive diagrams on page 54 Labeling the old disk drives on page 55 Removing the disk drives on page 55 Installing new disk drives on page 56 Installing the CUE flash image on page 57 Checking the status of the extract device on page 61 Avaya CMS Upgrade Express and Platform Upgrades September

54 Chapter 5: Replacing disk drives Disk drive diagrams Refer to the following diagrams for information about where the disk drives are located for the different platforms: Dell R620 front panel on page 54 Dell R720 front panel on page 54 HP 380P G8 front panel on page 55 Dell R620 front panel Dell R720 front panel Avaya CMS Upgrade Express and Platform Upgrades September

55 Replacement procedures HP 380P G8 front panel Labeling the old disk drives 1. Do one of the following to shut down the system: For the Dell R620, Dell R720, or HP 380P G8, enter: /sbin/shutdown -P -g0 2. For ESD isolation, verify that the AC power cord remains plugged in after you shut down the system. 3. While the original disk drives are still in the computer, use the colored labels from the upgrade kit to label each disk drive with the slot number where the disk was installed. Important:! Important: You must save the old disk drives in case you have to reinstall the original configuration. 4. Continue with Removing the disk drives on page 55 Removing the disk drives This procedure describes how to remove a disk drive. Make sure the original disks have been labeled before removing the disks. Avaya CMS Upgrade Express and Platform Upgrades September