Implementing Avaya Aura Session Manager

Implementing Avaya Aura Session Manager Release 6.2 03-603473 March 2013

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: http://support.avaya.com. 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, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO 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 e-mail 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: http:// 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. 2 Implementing Avaya Aura Session Manager Release 6.2 Comments? infodev@avaya.com

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: http://support.avaya.com. Hardware Support For full hardware support, please see Avaya Support Notices for Hardware Documentation, document number 03 600759 on the Avaya Support Web site, http://support.avaya.com. Contact Avaya Support See the Avaya Support website: http://support.avaya.com 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: http://support.avaya.com, scroll to the bottom of the page, and select Contact Avaya Support. Implementing Avaya Aura Session Manager Release 6.2

4 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Contents Chapter 1: Session Manager installation overview... 7 Remote access... 7 Installed OS-level logins for Session Manager... 8 Upgrades to Session Manager... 9 Related documents... 9 Support... 10 Chapter 2: Session Manager Preinstallation... 11 Prerequisites of installing Session Manager... 11 Registering for PLDS... 11 Downloading software from PLDS... 12 Writing the ISO image to DVD or CD... 13 Chapter 3: Installing Session Manager... 15 Ethernet port labels by server type... 15 Session Manager installation checklist... 15 Configuring the laptop for direct connection to the server... 17 Disabling proxy servers in Microsoft Internet Explorer... 18 Disabling proxy servers in Mozilla Firefox... 19 Connecting a laptop to the server... 20 Activating entitlements... 20 Enrolling a password (Enrollment Password)... 21 Authentication files for Session Manager... 22 Starting the AFS application... 23 Creating an authentication file for a new system... 23 Installing an authentication file... 24 Configuring Session Manager with SMnetSetup... 24 Alarming Configuration... 26 Network Management Systems Destinations... 26 Adding Network Management Systems Destination... 26 Chapter 4: Session Manager Administration... 27 Introduction... 27 Session Manager administration checklist... 27 Adding Domain Names for Session Manager... 28 Adding Session Manager as a SIP entity... 28 Administering Session Manager... 29 Chapter 5: Testing the installation... 31 Checking the Session Manager service state... 31 Testing the System Manager and Session Manager installation... 31 Generating a Test Alarm... 33 Verifying Data Replication to Session Manager... 33 Branch Session Manager fails to completely install... 33 Chapter 6: Session Manager Redundancy... 35 Configuring Session Manager redundancy on the same System Manager... 35 Chapter 7: Survivable Remote Session Manager... 37 Prerequisites... 37 Implementing Avaya Aura Session Manager Release 6.2 March 2013 5

Survivable Remote Session Manager... 37 Installation overview... 38 Survivable remote installation checklist... 38 Survivable Remote SAT administration checklist... 41 Adding a Survivable Remote Server... 41 Validating Minimum time of network stability... 42 Validating Gateway recovery rule... 42 Survivable Remote Session Manager administration checklist... 43 Adding a survivable remote server as a SIP entity... 44 Creating entity links... 44 Checking the connections... 45 Administering a survivable remote server... 46 Verifying survivable remote information... 47 Verifying the avaya-lsp address... 47 Verifying remote server security module IP address... 48 Verifying avaya-lsp-fs administration... 49 Verifying survivable server registration... 49 Testing calls... 50 Chapter 8: Troubleshooting... 51 Server has no power... 51 Unable to access Service State... 51 Issues with replica group state... 52 Troubleshooting steps... 52 Survivable server fails to sync with main server... 53 Troubleshooting steps... 53 Appendix A: Worksheets... 55 Session Manager configuration information worksheet... 55 Session Manager Entity information worksheet... 56 Survivable Remote configuration information worksheet... 57 Appendix B: Available media... 59 Appendix C: Interoperability with Avaya products... 61 Appendix D: Supported Hardware and Port Matrix... 63 Appendix E: CDR record format... 65 Index... 71 6 Implementing Avaya Aura Session Manager Release 6.2 March 2013

Chapter 1: Session Manager installation overview This guide contains the installation and initial administration information for Avaya Aura Session Manager Release 6.2. Avaya Aura System Manager Release 6.2 manages up to 10 coresession Manager instances. You can set up and administer the Session Managers concurrently. The Session Manager application is installed on the following servers: Avaya S8800, S8510 (upgrades only), HP DL360G7, and Dell R610. The servers HP DL360G7 or Dell R610 are shipped with all of the required components and software applications installed. The server connects to the customer network and the System Manager server using CAT5 Ethernet cables provided by the customer. Remote access is through the network only. The system does not support modem access. Starting with Session Manager Release 6.0, the PCI hardware version of the SM100 security module was converted to a software module running on the Session Manager server. The SM100 PCI hardware version is no longer used. The software version of the Security Module uses the Eth2 network interface for SIP traffic. Note: Ensure that customers have the Linux operating system Kickstart DVD and the Session Manager Software CD onsite for advanced installation issues or catastrophic failure or both. Download the software from PLDS. Ensure that System Manager is installed and operating on the customer network prior to starting Session Manager installation. Mid-size Enterprise Session Manager can be installed and configured using the Midsize Enterprise Template 6.2. See the document Installing and Configuring Avaya Aura Solution for Midsize Enterprise on the support site for details. Remote access Secure Access Link (SAL) uses the customer's existing Internet connectivity for remote support and alarming. All communication is outbound from the customer environment using encapsulated Hypertext Transfer Protocol Secure (HTTPS). The SAL requires upload bandwidth, for example, customer to Avaya or Avaya Partner, of at least 90 kb/s (720 kb/s) with latency no greater than 150 ms (round trip). Implementing Avaya Aura Session Manager Release 6.2 March 2013 7

Session Manager installation overview Business Partners without a SAL Concentrator must provide their own IP-based connectivity, for example, B2B VPN connection, to deliver remote services. 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 log-in 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. 8 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Upgrades to Session Manager Upgrades to Session Manager To upgrade to a new software release for Session Manager, see Upgrading Avaya Aura Session Manager on the Avaya support Web site at http://www.avaya.com/support. This document also contains the information for adding memory to the Avaya S8510 and S8800 servers for upgrading from previous releases to Release 6.0 and later. To install service packs for Session Manager, see Installing Service Packs on Avaya Aura Session Manager on the Avaya support Web site at http://www.avaya.com/support. Branch Session Manager (BSM) upgrade involves upgrading of the Communication Manager Survivable Remote templates as outlined in the document Upgrading to Avaya Aura Communication Manager Release 6.0.1. Note: Upgrade System Manager before starting the upgrade process on Session Managers. Related documents The following list contains additional documentation related to Session Manager that is available on the Avaya support Web site. Some documents are referenced within this book. Avaya Aura Session Manager Overview (03 603323): Provides overview information on Session Manager and its various components and features. Administering Avaya Aura Session Manager (03 603324): Describes how to administer Session Manager using System Manager. Implementing Avaya Aura Session Manager (03-603473): Provides the installation and initial administration information for Avaya Aura Session Manager Release 6.2. Maintaining and Troubleshooting Avaya Aura Session Manager (03 603325): Contains information for troubleshooting Session Manager, resolving alarms, replacing hardware, and alarm codes and event ID descriptions. Administering Avaya Aura Communication Manager Server Options (03 603479): Provides information for administering Communication Manager as a Feature Server or Evolution Server and the associated Session Manager administration. Installing and Configuring Avaya Aura Communication Manager (03-603558): Provides information on installing the appropriate Communication Manager template on the server including that of Branch Session Manager. Upgrading Avaya Aura Session Manager (03 603518): Describes how to upgrade Session Manager to a new software release. Implementing Avaya Aura Session Manager Release 6.2 March 2013 9

Session Manager installation overview Installing Service Packs For Avaya Aura Session Manager (03-603863): Describes how to install service packs on Session Manager. Security Design for Avaya Aura Session Manager: Contains information on making Session Manager secure on the network. Avaya Aura Session Manager Case Studies (03-603479): Provides case studies that walk users through common administration scenarios. Installing the Avaya S8800 Server for Avaya Aura Communication Manager (03 602918). Installing the Avaya S8510 Server Family and Its Components (03 602918). Installing the Dell PowerEdge R610 Server (03-603739). Installing the HP ProLiant DL360 G7 Server (03-603799). Support Visit the Avaya Support website at http://support.avaya.com for the most up-to-date documentation, product notices, and knowledge articles. On the Avaya Support website at http://support.avaya.com, 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. 10 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Chapter 2: Session Manager Preinstallation Prerequisites of installing Session Manager Before you install Session Manager, ensure you meet the following prerequisites: The System Manager template must be installed and operating. To install the System Manager template, see Implementing Avaya Aura System Manager on the Avaya support Web site, http://www.avaya.com/support License activation code: You must have a license activation code (LAC) before you install Session Manager. The LAC email recipients are identified during the order placement process. Network ports: The document Avaya Aura Session Manager: Port Matrix identifies which network ports must be open in firewalls. This document is available to Avaya customers, associates, and business partners using the InSite Knowledge Management Database at http://www.avaya.com/support Access to the PLDS Web site: If you do not have access to the Product License Delivery System (PLDS) Web site, see Avaya Access FAQ for details. Register for PLDS Download software from PLDS Write the ISO image to DVD or CD Registering for PLDS 1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site at https:// plds.avaya.com. The PLDS Web site redirects you to the Avaya single sign-on (SSO) Web page. 2. Log in to SSO with your SSO ID and password. The PLDS registration page is displayed. 3. If you are registering: Implementing Avaya Aura Session Manager Release 6.2 March 2013 11

Session Manager Preinstallation as an Avaya Partner, enter the Partner Link ID. If you do not know your Partner Link ID, send an e-mail to prmadmin@avaya.com. as a customer, enter one of the following: - Company Sold-To - Ship-To number - License authorization code (LAC) 4. Click Submit. Avaya will send you the PLDS access confirmation within one business day. Downloading software from PLDS About this task Note: You can download product software from http://support.avaya.com also. 1. Type http://plds.avaya.com 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. 12 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Writing the ISO image to DVD or CD Writing the ISO image to DVD or CD Before you begin 1. Download any required software from PLDS. 2. Verify that the md5 checksum of the downloaded ISO image matches the md5 checksum that is displayed for the ISO image on the PLDS Web site. About this task If you are writing to a DVD, this procedure requires a computer or server that has a DVD writer and software that is capable of writing ISO images to DVD. If you are writing to a CD, this procedure requires a computer or server that has a CD writer and software that is capable of writing ISO images to CD. Important: When the ISO image is being written to the DVD, do not run other resource-intensive applications on the computer. Any application that uses the hard disk intensively can cause a buffer underrun or other errors, which can render the DVD useless. Write the ISO image of the installer to a DVD or CD. Implementing Avaya Aura Session Manager Release 6.2 March 2013 13

Session Manager Preinstallation 14 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Chapter 3: Installing Session Manager About this task To install Session Manager, perform the following steps: Enter networking and related information. For more information, see Worksheets on page 55. Install the Session Manager server. Administer Session Manager. Test the installation. The Session Manager application is installed on the HP DL360G7 and Dell R610 servers. These servers are shipped with all of the required components and software applications. Ethernet port labels by server type The supported servers do not label the Ethernet ports in the same manner. Server Eth0 (Management Interface) Eth2 (Security Module) S8800 1 3 HP DL360 G7 1 3 Dell R160 Gb1 Gb3 S8510 GB1 GB3 Session Manager installation checklist You need a copy of this checklist for each Session Manager that will be installed. The customer must have the Linux operating system Kickstart DVD and the Session Manager Software CD on-site for advanced installation issues and/or catastrophic failures. The software is available for download from PLDS. See the section Session Manager Preinstallation for details. Note: Session Manager and System Manager host names may contain letters, numbers, and hyphens. Underscores are not allowed. Implementing Avaya Aura Session Manager Release 6.2 March 2013 15

Installing Session Manager # Installation action Link to installation description 1 Complete the Session Manager configuration information worksheet and verify the information is correct. 2 Complete the Session Manager entity information worksheet and verify the information is correct. 3 Configure the laptop for direct connection to the server which is required for the initial configuration. Session Manager configuration information worksheet on page 55 Session Manager Entity information worksheet on page 56 Configuring the laptop for direct connection to the server on page 17 4 Disable proxy servers. If using Internet Explorer, see Disabling proxy servers in Microsoft Internet Explorer on page 18 If using Firefox, see Disabling proxy servers in Mozilla Firefox on page 19 5 Connect the laptop to the server. Connecting a laptop to the server on page 20 6 Install the Session Manager server. If you are installing an Avaya S8800 server, see Installing the Avaya S8800 Server for Avaya Aura Communication Manager (03 602918) If you are installing an Avaya S8510 server, see Installing the Avaya S8510 Server Family and Its Components (03 602918) If you are installing a Dell R610 server, see Installing the Dell PowerEdge R610 Server, 03-603793 If you are installing an HP DL360 server, see Installing the HP DL360 G7 Server, 03-603799 7 Install the Session Manager license file. Note: Step 3: Configure the laptop for direct connection to the server provides a convenient means of gaining access to Session Manager for initial configuration. Activating entitlements on page 20 16 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Configuring the laptop for direct connection to the server # Installation action Link to installation description 8 Ping the System Manager from the Session Manager server to ensure it is connected to your network. 9 Log in to System Manager associated with Session Manager. 10 Establish the Session Manager enrollment password on System Manager. 11 Create and install an authentication file for Session Manager. 12 Configure Session Manager using the SMnetSetup command. Enrolling a password (Enrollment Password) on page 21 Authentication files for Session Manager on page 22 Configuring Session Manager with SMnetSetup on page 24 13 Administer Session Manager. Session Manager administration checklist on page 27 14 Configure the Alarming setup. Network Management Systems Destinations on page 26 15 Test the installation. Checking the Session Manager service state on page 31 Note: Change the service state of the new installed Session Manager to Accept New Service using Session Manager Dashboard. Note: The purpose of step 3: Configure the laptop for direct connection to the server is to provide a convenient means of gaining access to Session Managerfor initial configuration. Configuring the laptop for direct connection to the server About this task Before you connect the laptop to the server, you must manually configure the following: IP address Subnet mask Default gateway Implementing Avaya Aura Session Manager Release 6.2 March 2013 17

Installing Session Manager Note: 1. Make a note of the changes you make on your laptop for restoring back later to the standard configuration. 2. The following procedure is for Windows XP. The procedure may differ for other versions of Windows. 1. To configure the laptop to connect to the server, right-click My Network Places. 2. Click Properties. 3. In the Local Area Connection Properties dialog box, under the General tab, click Properties. 4. Click Internet Protocol (TCP/IP) from the list of items. 5. Click Properties. 6. In the Internet Protocol (TCP/IP) Properties dialog box, under the General tab, select Use the following IP address. Warning: Do not click the Alternate Configuration tab. 7. In the IP address field, enter 192.11.13.5. 8. In the Subnet mask field, enter 255.255.255.252. 9. In the Default gateway field, enter 192.11.13.6. 10. Click OK. Disabling proxy servers in Microsoft Internet Explorer About this task To connect directly to the services port, you must disable the proxy servers in Internet Explorer. 1. Start Internet Explorer. 2. Click Tools > Internet Options. 3. Click the Connections tab. 4. Click LAN Settings. 18 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Disabling proxy servers in Mozilla Firefox 5. Clear the Use a proxy server for your LAN option. Tip: To reenable the proxy server, select the Use a proxy server for your LAN option again. 6. Click OK to close each dialog box. Disabling proxy servers in Mozilla Firefox About this task To connect directly to the services port, you must disable the proxy servers in Firefox. Note: This procedure is for Firefox on a Windows-based computer. The steps can vary slightly if you are running Linux or another operating system on your laptop. 1. Start Firefox. 2. Click Tools > Options. 3. Select the Advanced option. 4. Click the Network tab. 5. Click Settings. 6. Select the No proxy option. Tip: To reenable the proxy server, select the appropriate option again. 7. Click OK to close each dialog box. Implementing Avaya Aura Session Manager Release 6.2 March 2013 19

Installing Session Manager Connecting a laptop to the server Before you begin Ensure that you have an SSH application, such as PuTTY installed on your laptop. Configure the IP settings of the laptop for direct connection to the server. See the earlier topics. Disable the use of proxy servers. See the earlier topics. The remote services laptop is only for SSH access to Session Manager. Web access is not supported by Session Manager. 1. Connect the laptop to the services port Eth1 with a standard or crossover Ethernet cable. See Ethernet port labels by server type on page 15 for the services port label on a particular server. 2. Start an SSH client application, that is PuTTY, session. 3. In the Host Name (or IP Address) field, enter 192.11.13.6. The system assigns the IP address 192.11.13.6 to the services port. 4. Verify that the protocol is SSH. 5. Verify that the Port is 22. 6. Click Open. Note: When you connect to the server for the first time, the system displays the PuTTY Security Alert window. 7. Click Yes to accept the server host key and display the PuTTY window. 8. Log in using craft on Session Manager or admin on System Platform or System Manager. 9. To close PuTTY, type exit. Activating entitlements When entitlements are activated, PLDS sends an Activation Record to the registered customer e-mail address. This e-mail contains the entitlement details and the license file. To use the 20 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Enrolling a password (Enrollment Password) license file, you must install the license on the System Manager server, which is the License Host WebLM server, to use the licenses. Before you begin To install a license on a server, you must have license activation codes (LAC) and the Host ID of the System Manager server, which is the WebLM server. 1. Enter http://plds.avaya.com in the address bar of 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. Enter LAC, which you have received through an e-mail, in the LAC(s) field in the Quick Activation section. 4. Enter the host information. 5. Click Next to validate the registration detail. 6. Enter the System Manager or other WebLM server information. The Host ID is the MAC address from the machine hosting the WebLM server. For more information on how to obtain MAC address, click Help. 7. Enter the number of licenses you want to activate. 8. Read and accept the Avaya Legal Agreement. 9. Send a confirmation e-mail: a. Enter any additional certificate recipient e-mail addresses in the E-mail to: field. b. (Optional) Enter Comments. c. Click Finish. 10. Click View Activation Record and verify the information. Enrolling a password (Enrollment Password) About this task When you enroll a password, the System Manager and Session Manager servers form a bond of trust. You need the Trust Management Enrollment Password to install and configure the Session Manager software. 1. On the System Manager Web console, in the Services column, click Security > Certificates > Enrollment Password. Implementing Avaya Aura Session Manager Release 6.2 March 2013 21

Installing Session Manager 2. If a password already exists and the Time Remaining is not 0, skip the remaining steps. The enrollment password is already valid. Make note of the password displayed on the screen for future reference. 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 a password already exists, copy it to the Password box. 5. If a password does not exist, do one of the following: Click Generate to use a randomly generated string as a password. Enter a password in the Password field and click 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 must enter the password when you install the Session Manager server. 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 HTTP://RFA.AVAYA.COM. 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. 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. 22 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Starting the AFS application 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 http://rfa.avaya.com. About this task 1. Type http://rfa.avaya.com 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 email. 1. 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. 5. If you want to download the authentication file directly from AFS to your computer: a. Click Download file to my PC. Implementing Avaya Aura Session Manager Release 6.2 March 2013 23

Installing Session Manager 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 e-mail message: a. Enter the e-mail address in the Email Address field. b. Click Download file via email. AFS sends the e-mail 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 e-mail 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 Manager using 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. Configuring Session Manager with SMnetSetup About this task Session Manager has the following configuration as shipped from the factory: 24 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Configuring Session Manager with SMnetSetup System Name: avaya-asm Eth0: 192.168.0.2/24 Eth1: 192.11.13.6/30 DNS Domain: localdomain DNS Server: 127.0.0.1 1. Cable the Ethernet Ports to the customer Local Area Network according to the server type. See Ethernet port labels by server type on page 15 for the port labels for the different servers. 2. Install the cables to access the Session Manager server using a laptop or USB keyboard, mouse, and monitor. 3. Log in to the Linux console of the Session Manager server using the craft login. 4. Enter the command./smnetsetup 5. For the information required by SMnetSetup, see Session Manager configuration information worksheet on page 55. a. Enter the Session Manager server hostname. b. Enter the Session Manager IP address (Mgmt). c. Enter the Netmask. d. Enter the Gateway IP address. e. Enter the Network Domain. f. Enter the Primary DNS server IP address. g. Enter the Secondary DNS (if applicable). h. Enter the Tertiary DNS (if applicable). i. At the prompt, press Enter. j. Configure the local time zone. k. Enter y to continue. l. When prompted for Disable NTP?, enter no. m. Enter the NTP server. n. Enter the Secondary NTP server (if applicable). o. Enter the Tertiary NTP server (if applicable). p. When prompted, create a customer account with a password. q. Enter the System Manager IP Address. r. Enter the System Manager FQDN. s. Verify your settings. t. Enter the enrollment password. 6. At this point, the system configures itself. The configuration takes approximately 15 minutes to complete. Implementing Avaya Aura Session Manager Release 6.2 March 2013 25

Installing Session Manager 7. When prompted to reboot, enter y and press Enter. The reboot takes about 10 minutes to complete. 8. When you see the log-in screen, continue with the next step in the Session Manager installation checklist. 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. 26 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Chapter 4: Session Manager Administration Introduction After Session Manager installation, perform the following basic administrative steps at the customer site: 1. Add SIP Domains. 2. Add Session Manager as SIP entities. 3. Administer Session Manager instances. For details on the following, see Administering Avaya Aura Session Manager, 03 603324: Routing settings Security default settings User account setup Session Manager administration checklist Use the following checklist for the initial administration of a newly-installed Session Manager. # Administration action Link to administration action 1 Log into the System Manager associated with this Session Manager. 2 Add Domain Names. Adding Domain Names for Session Manager on page 28 3 Add the installed Session Manager as a SIP Entity. Adding Session Manager as a SIP entity on page 28 4 Administer the Session Manager. Administering Session Manager on page 29 Implementing Avaya Aura Session Manager Release 6.2 March 2013 27

Session Manager Administration Adding Domain Names for Session Manager 1. On the System Manager Web console, click Elements > > Routing > Domains. 2. Click New. 3. In the Name field, enter the Network Domain Name of Session Manager. 4. Ensure that the Type is SIP. 5. (Optional) Enter a description in the Notes field. 6. Click Commit. Adding Session Manager as a SIP entity 1. On the System Manager Web console, Elements > Routing > SIP Entities. 2. Select New 3. In the Name field, enter the name of Session Manager. 4. In the FQDN or IP Address field, enter the IP address of the Session Manager Security Module. Note that this IP address is not the management IP address. 5. In the Type field, set the type to Session Manager. 6. In the Port section of the screen, click Add to add all port, protocol, and default domain entries for each port and protocol on which the Session Manager will listen for SIP traffic. Add Failover ports if the SIP entity is a failover group member. See Failover Groups section in the Administering Avaya Aura Session Manager, 03-603324 book for details. 7. Click Commit. 28 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Administering Session Manager Administering Session Manager 1. On the System Manager Web console, Elements > Session Manager > Session Manager Administration. 2. In the Session Manager Instances, select New. 3. In the SIP Entity Name field, enter the name of Session Manager. 4. (Optional) In the Description field, enter a description for Session Manager. 5. In the Management Access Point Host Name/IP field, enter the IP address of the host on which the Session Manager is installed. 6. In the Network Mask field, enter the network mask of the Session Manager Security Module. 7. In the Default Gateway field, enter the default gateway of the Session Manager Security Module. 8. Ensure that the Enable Monitoring box is checked by default. For more information regarding SIP monitoring, see Administering Avaya Aura Session Manager. 9. Click Commit. NOTE: After you administer the Session Manager instance, the configuration changes may take several minutes to replicate down to the Session Manager servers. Wait a few minutes before you continue with validation of the configuration. Implementing Avaya Aura Session Manager Release 6.2 March 2013 29

Session Manager Administration 30 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Chapter 5: Testing the installation Checking the Session Manager service state 1. Log in to the System Manager as an administrator using the admin login. 2. In Elements, select Session Manager. The service state for the new Session Manager should be Deny New Service. 3. If the system displays dashes as Service State for the installed Session Manager, see Unable to access Service State on page 51 for troubleshooting information. Testing the System Manager and Session Manager installation About this task Perform the following steps to verify that the software of System Manager and Session Manager are installed and configured properly and that the servers and applications are communicating. 1. On the System Manager Web console, click Elements > Session Manager > System Tools > Maintenance Tests 2. Select System Manager from the Select Target drop-down list. 3. Click Execute All Tests. 4. Verify all tests show Success status. 5. On the System Manager Web console, click Elements > Session Manager > System Status > Security Module Status. 6. Verify that the status is Up for all Session Managers. 7. Verify that the IP address is correct. Implementing Avaya Aura Session Manager Release 6.2 March 2013 31

Testing the installation 8. If the status is Down, reset the security module: Select the appropriate Session Manager from the table. Click Reset. Warning: The Session Manager cannot process calls while the security module is being reset. 9. On the System Manager Web console, click Elements > Session Manager. 10. Verify the installed software versions of all Session Managers are the same 11. Verify all Session Manager servers are in the Management Enabled state under Service State. 12. On the System Manager Web console, click Elements > Session Manager > System Tools > Maintenance Tests. 13. Select the appropriate Session Manager instance. 14. Select Execute All Tests. 15. Verify all tests ran successfully. 16. Check the replication status of the Session Managers: a. On the System Manager Web console, click Services > Replication. The Synchronization Status should be green and the status should be Synchronized. b. If the status is not Synchronized, select the check box next to SessionManagers_6.2 and click View Replica Nodes to determine which Session Manager is not synchronized with System Manager. 17. Verify there are no active alarms for the Session Manager. Alarms can be viewed on the System Manager web console, in Services, select Events > Alarms. 18. If alarm forwarding is configured to System Manager and customer NMS, generate a test alarm to verify alarm forwarding. See Generating a Test Alarm on page 33. Note: You can also use Session Manager Dashboard to verify that the installed Session Manager is ready for service. 32 Implementing Avaya Aura Session Manager Release 6.2 March 2013 Comments? infodev@avaya.com

Generating a Test Alarm 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. Verifying Data Replication to Session Manager 1. On the System Manager Web console, click Services > Replication. 2. Verify that the status for the appropriate replica group is Synchronized. 3. If the replica group is not in a Synchronized, Queued for Repair, or Repairing state, refer to Branch Session Manager fails to completely install on page 33. See Unable to access Service State on page 51 for an example of the information that should be contained in the /etc/hosts file. Branch Session Manager fails to completely install CM_SurvRemote and CM_SurvRemoteEmbed templates include Branch Session Manager. After the template installation is finished, allow 20 additional minutes for the Branch Session Manager virtual machine to install and initialize. The Virtual Machine Management page on Implementing Avaya Aura Session Manager Release 6.2 March 2013 33