Upgrading Avaya Aura Session Manager

Transcription

1 Upgrading Avaya Aura Session Manager Release 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. 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. Concurrent User License 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. 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 Third Party Components mean certain software programs or portions thereof included in the Software that 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 ). 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 Documentation or on Avaya s website at: support.avaya.com/copyright. 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. 2 Upgrading Avaya Aura Session Manager Release 6.2 Comments? infodev@avaya.com

3 Trademarks Avaya, Avaya Aura, Avaya, and Avaya Aura are registered trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: Hardware Support For full hardware support, please see Avaya Support Notices for Hardware Documentation, document number on the Avaya Support Web site, 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. Upgrading Avaya Aura Session Manager Release 6.2

4 4 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments?

5 Contents Chapter 1: Upgrading Session Manager... 7 Avaya Aura Session Manager software upgrade... 7 Assumptions... 8 Prerequisites... 8 Upgrade sequence... 8 Support... 9 Chapter 2: Release 6.2 Upgrade overview Available media Supported servers System component upgrade sequence Chapter 3: Upgrading Session Manager to Release Upgrade checklist Copying ISO images Downloading software from PLDS Verifying Enrollment Password status Denying new service Verifying the Active Call Count Viewing Session Manager Entity Link Connection Status Upgrading the operating system Upgrading Session Manager software Using Network transfer Using USB Thumb Drive Using a CD or DVD Testing the Session Manager instance Authentication files for Session Manager Starting the AFS application Creating an authentication file for a new system Installing an authentication file Verifying Data Replication Viewing Security Module status Accepting new service Alarming Configuration Network Management Systems Destinations Adding Network Management Systems Destination Adding a Session Manager to the SAL Gateway Generating a Test Alarm Appendix A: Troubleshooting Data Replication Appendix B: Troubleshooting Security Module Sanity failure Appendix C: Installed OS-level logins for Session Manager Index Upgrading Avaya Aura Session Manager Release 6.2 March

6 6 Upgrading Avaya Aura Session Manager Release 6.2 March 2013

7 Chapter 1: Upgrading Session Manager Avaya Aura Session Manager software upgrade The Upgrading Avaya Aura Session Manager guide describes the procedures for upgrading the software of a Session Manager server to Release 6.2. Session Manager Releases 6.0.x and 6.1 can be upgraded to Session Manager Release 6.2. However, Session Manager releases preceding 6.0 service pack 1 (SP1) cannot be directly upgraded to Session Manager Release 6.2 and must first be upgraded to Session Manager 6.0 SP1. To install a new Session Manager server, see Implementing Avaya Aura Session Manager, on the Avaya support Web site. It is highly recommended that the upgrade be scheduled during hours of little or no system activity. The active call count of Session Manager determines when the upgrade should occur. Ideally, the active call count should be zero. During an upgrade, the call processing traffic of one Session Manager is handled by the other Session Managers. Calls that are active when the upgrade takes place will remain up. However, any changes to the SIP session (for example, transfer) are denied and the call could be dropped. Branch Session Manager (BSM) Upgrade: BSM upgrade involves upgrading of the Communication Manager Survivable Remote templates as outlined in the document Upgrading to Avaya Aura Communication Manager Release Communication Manager Survivable Remote template category contains the following templates: Simplex Survivable Remote/CM_SurvRemoteEmbed - for use on the 8300D Embedded Survivable Remote/CM_SurvRemote - for use on all other BSM platforms Note: If you are upgrading an active BSM, make sure it has been administered on System Manager and that an Enrollment password is active. Before install or upgrade of BSM, ensure that all the BSMs are in DNS or added to the/etc/hosts file on System Manager. Also make sure that the date and time is in sync between System Manager and System Platform. A clock shift can cause certificate and DRS replication problems. For upgrades of Mid-size Enterprise Session Manager, see Avaya Aura Solution for Midsize Enterprise documentation available on the support site. Upgrading Avaya Aura Session Manager Release 6.2 March

8 Upgrading Session Manager Related topics: Assumptions on page 8 Prerequisites on page 8 Upgrade sequence on page 8 Assumptions A Session Manager installation exists which includes an Avaya Aura System Manager and one or more Session Manager instances. The release of Session Manager should be 6.0 Service Pack 1 or later for upgrading to Session Manager 6.2. System Manager associated with Session Managers has been upgraded to Release 6.2. The procedures for upgrading System Manager are described in Installing and Upgrading Avaya Aura System Manager on Prerequisites The System Manager server is running System Platform Release 6.2 and System Manager Release 6.2. Burn the following Session Manager ISO images from PLDS or support.avaya.com to a DVD: Session Manager 6.2 Linux 5.6 operating system. Session Manager 6.2 software. Upgrade sequence Perform the upgrade of Session Manager by the following steps: 1. Change the service state to Deny New Service for Session Manager. 2. Upgrade the operating system of Session Manager. 3. Upgrade the Session Manager software. 4. Install an Authentication file. 5. Verify that replication is working between System Manager and the Session Manager. 6. Test the Session Manager server. 7. Change the service state of the upgraded Session Manager to Accept New Service. 8 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

9 Support The Session Manager upgrade procedure, including operating system and Session Manager software, requires approximately 90 minutes to complete. Support Visit the Avaya Support website at for the most up-to-date documentation, product notices, and knowledge articles. On the Avaya Support website at search for notices, release notes, downloads, user guides, and resolutions to issues. Use the Web service request system to create a service request. Chat with live agents to help answer questions. If an issue requires additional expertise, agents can quickly connect you to a support team. Upgrading Avaya Aura Session Manager Release 6.2 March

10 Upgrading Session Manager 10 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments?

11 Chapter 2: Release 6.2 Upgrade overview For Release 6.2, you must first upgrade Session Manager to the Linux 5.6 operating system (OS). Note: You must burn the OS upgrade ISO image to a DVD in order to upgrade the operating system. Available media Avaya provides the following media for Release 6.2: Session Manager Release 6.2 software DVD Comcode Session Manager Release 6.2 Linux 5.6 operating system kickstart DVD Comcode Session Manager Release 6.2 Linux 5.6 kickstart upgrade DVD Comcode Session Manager Release 6.2 ISO image (asm-6.2.0*installer.iso). Session Manager Release 6.2 Linux 5.6 OS upgrade ISO image (asm-linux56-x86_64- upgrade.iso). Supported servers Session Manager Release 6.2 supports the following servers: Avaya S8800 Avaya S8510 HP DL360 G7 Dell R610 Upgrading Avaya Aura Session Manager Release 6.2 March

12 Release 6.2 Upgrade overview System component upgrade sequence You can upgrade the system components in the following sequence: 1. Endpoints. 2. System Manager. 3. Session Managers in the core. 4. Survivable Remote Session Managers (Branch Session Managers) in the branches and Core Survivable Processors (formerly known as local survivable processors). 5. Presence servers. 6. Communication Server (CS) (Optional) Service Providers. 8. Decommissioned NRS servers. 9. Media gateways. 10. Avaya Aura Communication Manager enterprise survivable servers (ESS). 11. Avaya Aura Communication Manager feature servers and evolution servers. Communication Manager upgrades, including the feature servers, evolution servers, ESSs, and core survival processors, follow the existing Communication Manager upgrade procedures. Administration to add a secondary Session Manager or Survivable Remote Session Manager should be done after all of the above upgrades to system components are complete. 12 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

13 Chapter 3: Upgrading Session Manager to Release 6.2 About this task Important: Upgrade the Session Manager servers one at a time to limit service degradation and outages. Scheduled the upgrade during hours of little or no system activity. All SIP users assigned to the Session Manager that is being upgraded lose service for the duration of the upgrade. See the Port Matrix documentation at the following location to verify firewall settings when performing any system installation or upgrade: Session Manager Port Matrix documents Upgrade checklist # Action Link/Notes 1 Copy the ISO images. Copying ISO images on page Verify that the Enrollment Password is still active. Change the state of Session Manager to Deny New Service. Verify that the Active Call Count is zero. View the Entity Links and note any links that are down. Important: Make sure that entity link for this Session Manager is UP Attach a monitor and keyboard to Session Manager that is being upgraded. Verifying Enrollment Password status on page 16. See Denying new service on page 17. Verifying the Active Call Count on page 18. Viewing Session Manager Entity Link Connection Status on page 18. Note: This is an optional step for monitoring the upgrade process. Upgrading Avaya Aura Session Manager Release 6.2 March

14 Upgrading Session Manager to Release 6.2 # Action Upgrade the operating system. Upgrade the Session Manager software. The upgrade takes about 30 minutes to complete. The server reboots automatically when the upgrade script is complete. After the server has rebooted, log in to the server. Enter the swversion command and verify that the upgrade has completed successfully. If the upgrade was not successful, contact Avaya Technical Support. On the System Manager Web console, click Elements > Session Manager. Create and install authentication file for Session Manager. Test Session Manager to verify its sanity. Verify data replication between System Manager and Session Manager. Data gets synchronized in about minutes. Verify the Security Module is active for Session Manager. If SIP monitoring is provisioned for the Session Manager, verify that the links are active for that Session Manager. Data gets updated in Link/Notes Upgrading the operating system on page 19. If upgrading using Network transfer, see Using Network transfer on page 20 If upgrading using USB drive, see Using USB Thumb Drive on page 20. If upgrading using a CD or DVD, see Using a CD or DVD on page 21. After the Session Manager upgrade, craft login will be ASG challenged and available only to Avaya Services. The Release should start with 6.2. In the Session Manager Dashboard page, wait for the Data Replication status as GREEN and then the Security Module status to be UP for the upgraded instance. Refresh the screen as necessary. Authentication files for Session Manager on page 22 Testing the Session Manager instance on page 22. Verifying Data Replication on page 25. Viewing Security Module status on page 25. Viewing Session Manager Entity Link Connection Status on page Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

15 Copying ISO images # Action approximately 15 minutes. Refresh the screen as necessary. Change the state to Accept New Service for the upgraded Session Managerserver. Make test calls to ensure Session Manager is processing calls properly. Configure the Alarming setup. Repeat steps 1 to 19 to upgrade each additional Session Manager to Release 6.2. Link/Notes Accepting new service on page Network Management Systems Destinations on page Copying ISO images About this task Download the following ISO images: Session Manager Release 6.2 ISO image (asm-6.2.0*installer.iso). Session Manager Release 6.2 Linux 5.6 OS Upgrade ISO image (asm-linux56-x86_64- upgrade.iso). 1. Download the ISO images from PLDS or the Avaya support Web site to a machine (other than the Session Manager server) capable of making DVDs. See Downloading software from PLDS on page Burn the Linux 5.6 OS upgrade ISO image to a DVD. You will need this DVD to upgrade the operating system on Session Manager. 3. (Optional) Copy the Session Manager Release 6.2 ISO image to a USB thumb drive (minimum 4 GB) or burn the Session Manager Release 6.2 ISO image to a DVD. Upgrading Avaya Aura Session Manager Release 6.2 March

16 Upgrading Session Manager to Release 6.2 Downloading software from PLDS About this task Note: You can download product software from also. 1. Type in your Web browser to access the Avaya PLDS Web site. 2. Enter your Login ID and password to log on to the PLDS Web site. 3. Select Assets from the Home page and select View Downloads. 4. Search for the downloads available using one of the following methods: By Actual Download name By selecting an Application type from the drop-down list By Download type By clicking Search Downloads 5. Click the download icon from the appropriate download. 6. When the confirmation box displays, select Click to download your file now. 7. If you receive an error message, click on the message, install Active X, and continue with the download. 8. When the security warning displays, click Install. When the install is complete, PLDS displays the downloads again with a checkmark next to the downloads that have been completed successfully. Verifying Enrollment Password status About this task If the password has expired, ask the customer for a password, make one up, or generate a random password. 1. On the System Manager Web console, click Services > Security > Certificates > Enrollment Password. 16 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

17 Denying new service 2. If the value of Time Remaining field is not zero, the Enrollment Password is valid. Make a note of the password and skip the remaining steps. Continue with the following steps only if the value of Time Remaining field is zero. 3. In the Password expires in box, select a value from the drop-down menu for the time when the password should expire. 4. If the password exists, copy it to the Password box. 5. If a password does not exist, do one of the following: Select Generate to use a randomly generated string as a password. In the Password field, enter a password and select Commit. Note: The system updates the time displayed next to the Time remaining label with the value selected in the Password expires in field. You must remember this password. You need to provide this password as input when you upgrade the Session Manager software. Denying new service About this task When you change the state of the selected Session Manager to Deny New Service, any new call attempts and service requests are denied. Existing calls remain in effect until the users terminate the calls. 1. On the System Manager Web console, click Elements > Session Manager. 2. On the Session Manager Dashboard page, select the appropriate Session Manager check box in the Session Manager Instances table. 3. Click Service State. 4. From the drop-down list box, select Deny New Service. 5. On the confirmation page, click Confirm. Upgrading Avaya Aura Session Manager Release 6.2 March

18 Upgrading Session Manager to Release 6.2 Verifying the Active Call Count About this task The Active Call Count indicates the number of active calls on Session Manager. These are calls that were already up before the Session Manager was placed in the denial state. Changing the state to Deny New Service does not drop calls that are currently being processed. To avoid negatively impacting calls that are active, the Active Call Count should be zero before proceeding with the Session Manager upgrade. At the administrator's discretion, the upgrade may continue if active call count is not zero with the understanding that the active calls are dropped. 1. On the System Manager Web console, click Elements > Session Manager. 2. Wait until the Active Call Count is zero for Session Manager being upgraded. Refresh the screen to update the count. Viewing Session Manager Entity Link Connection Status About this task An entity link consists of one or more physical connections between a Session Manager server and a SIP entity. If all of the connections are up, then the Entity Link status is up. If one or more connections are down but there is at least one connection up, the link status is partially down. If all of the connections are down, the Entity Link status is down. 1. On the System Manager Web console, click Elements > Session Manager > Session Manager Dashboard. The number of up and down links are shown in the Entity Monitoring column. The values have the format # of Down links / # of Total links. 2. If the values are red, there is at least one entity link that is down. Click the red numbers for Session Manager. The Session Manager Entity Link Connection Status page displays the details for each link that is currently down, including the reason code. 18 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

19 Upgrading the operating system 3. To view the SIP Entity Link Monitoring Status Summary page, click Summary View. Upgrading the operating system About this task Use a DVD to upgrade the operating system. 1. Insert the operating system (OS) upgrade DVD into the DVD drive of the Session Manager server. 2. Restart the Session Manager server by using the System Manager web console as per the following steps: a. On the System Manager Web console, click Elements > Session Manager. b. On the Session Manager Dashboard page, select the appropriate Session Manager check box in the Session Manager Instances table. c. From the Shutdown System drop-down box, select Reboot. d. On the confirmation page, click Confirm. The Session Manager reboots and the OS upgrade begins and proceeds automatically. 3. After the OS upgrade is complete, the Session Manager server reboots again. Note: Wait for the reboot to complete. 4. Login to the Session Manager server using sroot, craft, or customer login. 5. Verify the operating system version by using the command cat /etc/redhatrelease. Upgrading Avaya Aura Session Manager Release 6.2 March

20 Upgrading Session Manager to Release 6.2 Upgrading Session Manager software Using Network transfer About this task Transfer the downloaded Session Manager ISO image from the services machine to the Session Manager server and run the upgrade script using the following procedure: 1. Log in as craft or customer to a console on the Session Manager server or use SSH. Note: Services Laptop can be directly connected to the Service Port of the server. 2. Enter rm f $HOME/asm*installer.iso. 3. Enter echo $HOME. 4. Transfer the ISO file to the Session Manager server into the directory represented by $HOME over the network using WinSCP or some other file transfer applications. 5. Enter cd $HOME. 6. Enter./upgradeSM asm*installer.iso to mount the ISO image and run the upgrade script. The script takes about 30 minutes to complete. The Session Manager server automatically ejects the DVD and reboots when the script completes. Using USB Thumb Drive About this task Install the Session Manager ISO image that has been copied to a USB thumb drive using the following procedure: Important: Installing ISO image using USB drive does not work on HP DL 360 server. You can use USB drive with the following servers: 20 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

21 Upgrading Session Manager software Avaya S8800 server. Avaya S8510 server Dell R610 server. 1. Log in as craft or customer to a console on the Session Manager server or use SSH. Note: Services Laptop can be directly connected to the Service Port of the server. 2. Copy the Session Manager ISO image from a USB thumb drive to Session Manager, as shown below: a. Insert the USB drive into the USB port of the Session Manager server. b. Enter mount /usbthumb/. c. Enter cd /usbthumb/. d. rm f $HOME/asm*installer.iso. e. Enter cp asm*installer.iso $HOME. f. When the copy is complete, enter cd /. g. Enter umount /usbthumb. h. Remove the USB drive from the server. 3. Enter cd $HOME. 4. Enter./upgradeSM asm*installer.iso to mount the ISO image and run the upgrade script. The script takes about 30 minutes to complete. The Session Manager server automatically ejects the DVD and reboots when the script completes. Using a CD or DVD About this task To install the Session Manager software using the CD or the DVD that contains the ISO image, by the following steps: 1. Log in as craft or customer to a console on the Session Manager server or use SSH. Note: Services laptop can be directly connected to the Service Port of the server. Upgrading Avaya Aura Session Manager Release 6.2 March

22 Upgrading Session Manager to Release Insert the DVD into the CD or DVD drive of Session Manager. 3. Enter $HOME/upgradeSM to start the upgrade script. The upgrade takes approximately 30 minutes to run. The Session Manager server automatically ejects the DVD and reboots when the script completes. Testing the Session Manager instance 1. On the System Manager Web console, click Elements > Session Manager > System Tools > Maintenance Tests. 2. From the Select System Manager or a Session Manager to test list box, select Session Manager instance from the drop-down list box. 3. Select Execute all Tests. 4. Verify that in the Test Result field, the system displays Success. If any of the tests fail, see Maintaining and Troubleshooting Avaya Aura Session Manager, Authentication files for Session Manager The authentication file contains Access Security Gateway (ASG) keys and the server certificate for Session Manager. With the ASG keys, Avaya Services can securely gain access to the customer system. A default authentication file is installed with Session Manager. However, the default file must be replaced with a unique file. Authentication File System (AFS) creates unique authentication files. AFS is an online application available at Follow the procedures in the steps below to install the authentication file. AFS authentication files have a plain text XML header with encrypted authentication data and an encrypted server certificate. Each authentication file contains an authentication file ID (AFID) to identify the file. You need this AFID to create a new authentication file for an upgrade or to replace the current authentication file on the server. 22 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

23 Authentication files for Session Manager Note: Installation of the unique authentication file is essential. Failure to install the unique authentication file results in receiving an alarm that re-transmits once a day till you install this file. Starting the AFS application Before you begin AFS is available only to Avaya service personnel and Avaya Partners. If you are a customer and need an authentication file, contact Avaya or your authorized Avaya Partner. You must have a login ID and password to start the AFS application. You can sign up for a login at About this task 1. Type in your Web browser. 2. Enter your login information and click Submit. 3. Click Start the AFS Application. A security message is displayed. 4. Click I agree. The AFS application starts. Creating an authentication file for a new system About this task To acquire an authentication file, use one of the following options: Download the authentication file directly from AFS. Receive the authentication file in an Start and log in to AFS. 2. In the Product field, select SM Session Manager. 3. In the Release field, select the release number of the software, and then click Next. 4. Select New System, and then click Next. Upgrading Avaya Aura Session Manager Release 6.2 March

24 Upgrading Session Manager to Release If you want to download the authentication file directly from AFS to your computer: a. Click Download file to my PC. b. Click Save in the File Download dialog box. c. Select the location where you want to save the authentication file, and then click Save. d. Click Close in the Download completedialog box to complete the download. After the authentication file is created, AFS displays a confirmation message that contains the system type, release, and authentication file ID (AFID). 6. To receive the authentication file in an message: a. Enter the address in the Address field. b. Click Download file via . AFS sends the message that includes the authentication file as an attachment and the AFID, system type, and release in the message text. c. Save the authentication file to a location on the recipient's computer. After the authentication file is created, AFS displays a confirmation message that contains the system type, release, and authentication file ID (AFID). 7. To view the header information in the authentication file, go to the location where you saved the file and open the file with WordPad. The header includes the AFID, product name and release number, and the date and time that the authentication file was generated. Installing an authentication file 1. Log in to Session Managerusing putty or other ssh tool. 2. Load the authentication file manually using loadpwd command as shown below: loadpwd -l <path to the auth file> using craft or the customer account. Next steps Use the displaypwd command to display information about the currently loaded authentication file. 24 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

25 Verifying Data Replication Verifying Data Replication 1. On the System Manager Web console, click Services > Replication. 2. The status for the appropriate replica group should be Synchronized. If the status for the replica group is not Synchronized, see Troubleshooting Data Replication on page 29. Viewing Security Module status 1. On the System Manager Web console, click Elements > Session Manager. The Session Manager Dashboard page displays the details and Security Module status for all the administered Session Manager servers and Survivable Remote Session Manager servers (BSM). 2. If the Security Module state of a particular Session Manager is not selected as Up, see Troubleshooting Security Module Sanity failure on page 31. Accepting new service About this task Note: Even though the Security Module displays the status as Up, the security module may take 5 to 10 minutes before it can begin routing calls. 1. On the System Manager Web console, click Elements > Session Manager. 2. On the Session Manager Dashboard page, select the Session Manager instance by selecting the check box in front of the Session Manager name in the Session Manager Instances table. Upgrading Avaya Aura Session Manager Release 6.2 March

26 Upgrading Session Manager to Release From the Service State drop-down box, select Accept New Service. 4. On the confirmation page, click Confirm. Alarming Configuration Network Management Systems Destinations The Session Manager serviceability agent can send SNMPv2c/v3 traps or Informs for alarms to multiple destinations. SAL Gateway is a mandatory trap destination for traps sent to Avaya Services for system maintenance. SAL Gateway converts the traps as alarms and forwards the traps to the Avaya Data Centre for ticketing purposes. Therefore, after you install or upgrade to Session Manager release 6.2, you must configure the serviceability agent with the SAL Gateway as a trap destination. The serviceability agent configuration is performed using the System Manager web console. You must also configure Session Manager as a managed device on the SAL Gateway. Optionally, you can configure any third-party Network Management Systems (NMS) as a trap destination. Based on customer requirements, Avaya technicians can also configure Avaya SIG server as another trap destination. Adding Network Management Systems Destination About this task You can add an NMS destination through the System Manager web console. To add an NMS destination, you must create a target profile for the NMS destination and then attach the target profile to a serviceability agent. For more information on activating agents and attaching target profiles, see Chapter 7, SNMP Support for Session Manager in the Maintaining and Troubleshooting Avaya Aura Session Manager guide. Adding a Session Manager to the SAL Gateway Before you begin The Secure Access Link (SAL) Gateway should already be set up for System Manager Release Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

27 Adding a Session Manager to the SAL Gateway 1. Log in to the System Platform Web console. 2. Click Server Management > SAL Gateway Management. 3. On the SAL Gateway Management page, click Launch SAL Gateway Management Portal. 4. When the SAL Gateway logon page appears, enter the same user ID and password that you used to log in to the System Platform Web console. 5. In the navigation pane of the SAL Gateway user interface, select Secure Access Link Gateway > Managed Element. 6. On the Managed Element page, click Add new. 7. Enter information in the following fields: Host Name Host Name of the Session Manager. IP Address IP Address of the Session Manager. In the Model field, select SessionMgr_x.x.x.x from the drop-down menu. The Product field is filled in automatically after the selection has been made. Solution element ID The Solution Element ID (SE ID) of Session Manager. The format of the ID is (NNN)NNN-NNNN where N is any digit from 0 to 9. Product ID The Product ID of Session Manager. Select the Provide remote access to this device check box. Select the Transport alarms from this device check box. 8. Click Add. Important: The SAL Gateway can forward alarms for this Session Manager only after you select Provide remote access to this device and Transport alarms from this device check boxes. 9. Click Apply to apply the changes. 10. Restart the SAL Gateway for the configuration changes to take effect: a. In the navigation pane of the SAL Gateway user interface, select Administration > Apply Configuration Changes. b. Click Apply next to Configuration Changes. The system restarts the SAL Gateway and updates it with the newly configured values. Upgrading Avaya Aura Session Manager Release 6.2 March

28 Upgrading Session Manager to Release 6.2 Generating a Test Alarm About this task The generatetestalarmsm.sh command generates a test alarm and sends it to the System Manager and NMS (if configured). It also sends the test alarm to SAL Gateway to be forwarded to ADC for end-to-end testing. 1. On the Session Manager console, enter generatetestalarmsm.sh command. 2. Verify that System Managerreceived the test alarm message: a. On the System Manager Web console, click Services > Events > Alarms. b. Verify the following text is displayed under the Description column: Test alarm for testing only, no recovery action necessary. 3. If the customer has an NMS in their network, verify that the NMS also received this alarm. 28 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

29 Appendix A: Troubleshooting Data Replication 1. On the System Manager Web console, click Services > Replication. 2. If the status for the replica group is not Synchronized, perform the following steps: a. Select the check box in front of the affected replica group. b. Click View Replica Nodes. c. Verify that an entry for the upgraded Session Manager exists. d. Select the check box next to the upgraded Session Manager. e. Click View Details. f. Under the Synchronization Status section, wait until the Pending Batches number is zero. Refresh the page as necessary. 3. If the Pending Batches number does not change to zero, perform the following steps: a. Click Done. b. On the Replica Nodes page, click Repair. 4. Wait until the status of Session Manager is Synchronized. Refresh the page as necessary. Upgrading Avaya Aura Session Manager Release 6.2 March

30 Troubleshooting Data Replication 30 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments?

31 Appendix B: Troubleshooting Security Module Sanity failure 1. On the System Manager Web console, click Elements > Session Manager > System Status > Security Module Status. 2. Select Refresh to display the current status. 3. Verify that the Status for the indicated Session Manager is Up. 4. Verify that the IP address is correct. 5. If the status is selected as Down, reset the security module: a. Select the appropriate Session Manager from the table. b. Click Reset. Warning: Session Manager cannot process calls while the security module is being reset. 6. Select Refresh to display the current status. Upgrading Avaya Aura Session Manager Release 6.2 March

32 Troubleshooting Security Module Sanity failure 32 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments?

33 Appendix C: Installed OS-level logins for Session Manager For security purposes, the root login has been disabled on the Session Manager. The following is a list of logins which are created during the Session Manager software installation: craft: An Avaya services login that you can use to gain access to the system remotely for troubleshooting purposes. sroot: An Avaya services root permission login that you can use to gain access to the system remotely for troubleshooting purposes. You cannot gain access to the sroot login directly from a login prompt except at the server console. customer: A login that the SMnetSetup script creates. During the execution of SMnetSetup, the customer can gain access to log-in defaults to cust. The customer must ensure the security of this login-in account. The system permits the customerlogin to run tools on the Session Manager server which do not require root access. CDR_User: A restricted shell login for the Call Detail Recording (CDR) feature that collects call data from the Session Manager server. This login is restricted to sftp access only. asset : A login created during the installation of the Security Module software. By default, access to the system using this login is disabled. spirit: A login created by the Secure Access Link remote alarming and remote access module for Avaya services. postgres: A login created by the installation of the Session Manager software PostgresSQL database system. Access to the system using this login is disabled. init : An Avaya services login that accesses the system remotely for troubleshooting purposes. inads: An Avaya services login that accesses the system remotely for troubleshooting purposes. rasaccess: An Avaya services login that accesses the system remotely for troubleshooting purposes. Warning: As of Session Manager 6.2 release, the sroot and craft logins are secured using Access Security Gateway challenge and response mechanisms in order to prevent unauthorized access to Session Manager servers by non-avaya services personnel. Using the customer login account, you can execute most of the maintenance and troubleshooting commands and root access is not required for standard maintenance and support purposes. For details, see PSN. Upgrading Avaya Aura Session Manager Release 6.2 March

34 Installed OS-level logins for Session Manager 34 Upgrading Avaya Aura Session Manager Release 6.2 March 2013 Comments?

35 Index A about accepting new service adding NMS Destination...26 AFS starting alarm test...28 assumptions... 8 C copying ISO images creating Authentication File D data replication denying new service...17 downloading software...16 E Enrollment password status I installing an authentication file L legal notice... 2 logins installed...33 M managed element...26 configuring in SAL Gateway...26 media...11 N Network Management Systems Destinations...26 Network transfer NMS destinations O operating system upgrade...19 overview P PLDS downloading software R replication verification...25 S SAL Gateway configuring a managed element...26 Security Module sanity failure troubleshooting support... 9 contact... 9 supported servers...11 system component upgrade sequence T testing Session Manager instance troubleshooting... 29, 31 Security Module sanity failure Alarms...31 U upgrade assumptions...8 upgrade checklist upgrade sequence... 8 upgrading to Release USB Thumb Drive using a CD or DVD...21 using physical media Upgrading Avaya Aura Session Manager Release 6.2 March

36 V verify alarm configuration verifying Active Call Count viewing Entity Link Connection Status viewing security module status Upgrading Avaya Aura Session Manager Release 6.2 March 2013