Implementing Avaya Aura® Application Enablement Services on Avaya Aura® System Platform

Release 6.1 Issue 3 February 2011

© 2011 Avaya Inc. All Rights Reserved. Notices 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 Web sites 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 Web site: 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. 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 AVAYAAFFILIATE 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 End User a license within the scope of the license types described below. 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 End User. “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. “Software” means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. “Hardware” means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an 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. Database License (DL). End User may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Named User License (NU). End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. “Named User”, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a “Named User” may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as “shrinkwrap” or “clickthrough” license accompanying or applicable to the Software (“Shrinkwrap License”). (see “Third-party Components” for more information). 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

2

Implementing Application Enablement Services on System Platform R6.1

February 2011

the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (“Third Party Components”), which may contain terms that expand or limit rights to use certain portions of the Product (“Third Party Terms”). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/Copyright. 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 Web site: http://support.avaya.com. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks Avaya Aura is a registered trademark of Avaya. All non-Avaya trademarks are the property of their respective owners. PuTTY is copyright 1997-2009 Simon Tatham. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: http://support.avaya.com. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com.

Implementing Application Enablement Services on System Platform R6.1

February 2011

3

1 February 2011 .4 Implementing Application Enablement Services on System Platform R6.

...................................................................................................................................................................................................................................................................................16 Chapter 2: Installation prerequisites...................................................................36 Starting the installation from your laptop.....41 Configuring network settings for Console Domain..........................................................................................................................40 System Domain Network Configuration field descriptions...........................................................29 Chapter 4: Installing System Platform....................................................................................................................................................................................14 Network latency requirements..............................................................................................................................................................................16 Communication Manager and media server requirements.....................................................................................................................................................36 Starting the installation from the server console..........................38 Verifying the System Platform image on the DVD..........................................................................................................31 Installation methods.............................................44 Configuring System Platform passwords........................13 Network interface (NIC) settings..........................16 Downloading the AE Services release notes......................34 Disabling proxy servers in Microsoft Internet Explorer......................................................................................39 Configuring network settings for System Domain (Domain-0)........................11 Application Enablement Services Ethernet interfaces...........................................................................................................................................................................................................................................................................................................................46 Verifying installation of System Platform..............................................................................................................................................27 Chapter 3: Installing the Dell R610 server........................................................................35 Starting the installation...............................34 Connecting your laptop to the server.......................................................................................................................24 Registering for PLDS..........................................................................................................................................................................................................23 Software download......................................................................................19 Application Enablement Services on System Platform installation overview................................................................................................................................................................................................................42 System Platform Console Domain Network Configuration field descriptions......................................47 Implementing Application Enablement Services on System Platform R6.......................37 Selecting the type of keyboard...........................................................................10 Network interfaces for the server...................................................................................9 About the Application Enablement Services on System Platform offer................................................1 February 2011 5 ...............................9 Application Enablement Services on System Platform High Availability Failover.................................................................................................................................24 Required software................................................................................................................................................................................................................25 Verifying the downloaded ISO image........................................................22 What customer provides................................................43 Configuring the time zone for the System Platform server..............................................................44 Configuring the date and time for the System Platform server..........................................................................................................19 Installation worksheet for AES on System Platform.....................................................................15 Client workstation provisioning..........................................................................................9 Requirements for High Availability Failover..........................................34 Configuring the laptop for direct connection to the server....................................Contents Chapter 1: Installation overview...................................31 Installation checklist for System Platform.....................................................................................................................................................24 Downloading software in PLDS........................................................................................................................................................................................................................................................20 What Avaya provides.................................................................................................................................................................................................13 Dual NIC configuration......................................................25 Writing the downloaded software to DVD....12 Single NIC configuration...............45 Passwords field descriptions........35 Disabling proxy servers in Mozilla Firefox.......................................................................................

............................................................................................................................................53 Downloading patches...........................................63 Search Local and Remote Template field descriptions........................................................................52 Chapter 5: Installing patches...............................75 Applying configuration changes..........................................................................................................................................................................................................................................................................79 Gateway Configuration field descriptions.....................................................................................55 Patch List field descriptions.............................................................................................................................................................................................................................76 Adding a managed element..............................................................80 Remote Access field descriptions........................................................................70 Configuring the SAL Gateway.....................................................................................................................................................................................................................................................................82 6 Implementing Application Enablement Services on System Platform R6...................................................53 Patch management......................................................................80 SAL Enterprise field descriptions......................................................................81 Managed Element field descriptions.............................54 Installing patches.......................................................................................77 Using a stand-alone SAL Gateway.........................................................................................Accessing System Platform.................................51 Accessing the command line for Console Domain..................................................................53 Configuring a proxy................................................................................................................61 Configure Failover field descriptions...........................................................................................................................................................................................................................................................................69 System and browser requirements for accessing the SAL Gateway user interface..........................67 Configuration prerequisites....................................................................................................81 Network Management Systems field descriptions.....57 Chapter 6: System Platform High Availability Failover............................................................................................................74 Configuring NMS....................................................................................50 Accessing the command line for System Domain..............................................................................73 Configuring SAL Gateway communication with a Secure Access Concentrator Remote Server.....................................................................................................................................63 Installing Application Enablement Services template.................................................................................................................................................................................................78 Disabling SAL Gateway..............................................................................62 Chapter 7: Installing Application Enablement Services.65 Chapter 8: Administering SAL on System Platform................................................49 Accessing the System Platform Web Console.........................................................................48 Connecting to the server through the services port...................................................................................................................................................79 Proxy server field descriptions..............................................................................................................................71 Configuring a proxy server................................78 Adding an SNMP trap receiver.......................................70 Starting the SAL Gateway user interface.......................................................................................................................................................61 Configuring High Availability Failover............72 Configuring SAL Gateway communication with a Secure Access Concentrator Core Server..........................................................................................................................................................................................................................................................................................................................................................................................................67 SAL Gateway................................59 Requirements for High Availability Failover...................................................................................................................................78 Field descriptions......................................59 High Availability Failover overview.............................................................................................................................................................................75 Managing service control......................................................................................................................................................................68 Changing the Product ID for System Platform...............54 Search Local and Remote Patch field descriptions..................................................................................63 Prerequisites for installing the AES template.............................................................................56 Patch Detail field descriptions....................60 Prerequisites for configuring High Availability Failover....48 Enabling IP forwarding to access System Platform through the services port........................1 February 2011 .......................................................................................................................

..........................................................115 Appendix C: Installing and connecting the S8800 server..............................................................................................................................................................99 Appendix A: Managing license entitlements from PLDS.......115 Verifying the license allocations on the Local WebLM Server...................................89 Platform Upgrade field descriptions............................................................97 Troubleshooting steps................................................1 February 2011 7 ......................................................91 Methods for upgrading High Availability systems...................................................................................................................91 Starting High Availability Failover....113 Setting up the Local WebLM Server in your configuration............................................................................................................................................................................................................................117 Introduction..........................................................................................................................................................109 Enterprise-wide licensing — pointing to a master license on a remote server................................................................................................................................................................................................................................104 Regenerating a license file..........85 Upgrading System Platform............................................................................89 Upgrading System Platform on High Availability Systems........121 Implementing Application Enablement Services on System Platform R6.....................................................................................................Chapter 9: Upgrading System Platform...........................108 Standard licensing..................................................................................................................................................................................................................................................................................................................................................................................................................................99 Multiple reinstallations can result in an out of memory error.................................................................................................................................................................................................................92 Upgrading System Platform on both servers............................86 Commit and Rollback................................................................................................................................................................87 Committing an upgrade...................................................................108 Enterprise-wide licensing — allocating licenses or features............101 Activating license entitlements....................................................................................................................102 Moving activated license entitlements................................................................................................................................119 Server specifications...............................................................................................................................92 Upgrading System Platform on the preferred server only....................................................................................................117 Overview of the Avaya S8800 Server...............................97 SAL does not work........................................................................................................107 Licensing configuration examples.......................................105 Appendix B: Enterprise-wide licensing.....................................................97 Template DVD does not mount...........................................................120 Server components...........................................111 Installing the license file and configuring the master WebLM server.............................................95 Chapter 11: Troubleshooting the installation............................................................................................................................................................................................114 Changing the allocations of a license file.................................................................117 Back of server.................................................................................................................................................................................101 Searching for license entitlements...................................95 Upgrading Application Enablement Services template...........................91 Stopping High Availability......................................................................................................97 Cannot ping Console Domain or access the Web Console..91 Stop and start of High Availability for platform upgrades.................................................................................................................................89 Rolling back an upgrade..................................................................................111 Adding a local WebLM server...............................................................................................................93 Chapter 10: Upgrading Application Enablement Services...................................................................................................117 Front of server...................................................................................................................................................................................................................................................................107 Overview of enterprise-wide licensing..................................................................85 Platform upgrade.......................110 Setting up a configuration for allocating licenses.................................107 Comparison of standard licensing and enterprise-wide licensing................................................................................................................

........125 Installing the Avaya S8800 Server...................................................................127 Installing the server in the rack.........................................................................................................................................................................................................................................................................................131 Turning on the server........................................................................................................................................................122 Safety instructions...............................................................................................................................................134 Connecting the server to the network...........1 February 2011 ............................................................................................................................................................................................................124 Customer-provided equipment.......................................................................................137 8 Implementing Application Enablement Services on System Platform R6.....................................................................126 Attaching the rails to the rack........................................................................................135 Index..................................................................................................S8800 Server environmental requirements.....................................................................................................................................................................124 Clearance requirements..................................................................................................125 Server installation checklist.....................................................123 Avaya-provided equipment.............................129 Installing the cable management arm.................................................................................126 Rack installation components....

If one server fails. With the High Availability Failover feature. The interchange will appear to applications as a brief loss of the network connection. and the Application Enablement Services software. (See Application Enablement Services on System Platform High Availability Failover on page 9). When an interchange occurs. Application Enablement Services on System Platform High Availability Failover To use the Application Enablement Services on System Platform High Availability Failover (High Availability Failover) feature. a High Availability Failover configuration consists of a dual server platform. Only the active server provides service. Implementing Application Enablement Services on System Platform R6. At a high level.1. the second server quickly and automatically becomes available to client applications.1 offer includes a hardware platform (Dell™ PowerEdge™ R610). The Application Enablement Services on System Platform 6. The DMCC service preserves its associations when an interchange occurs. Application Enablement Services on System Platform provides the High Availability Failover feature for customers who want to take advantage of the high availability failover capability. the Red Hat Linux operating system. There will be a single license file for the Dell R610 pair.Chapter 1: Installation overview About the Application Enablement Services on System Platform offer Avaya Aura® Application Enablement Services (AE Services) on System Platform was first offered in Release 5. This option requires two Dell R610 servers and an Ethernet crossover cable. The standby server monitors the active server and then quickly takes over when a failure in the active server occurs. you can install two identical servers that can be addressed and administered as a single entity. CVLAN. the Avaya Aura® System Platform (System Platform) software.1 February 2011 9 . the TSAPI. which includes an active server and a standby Server.2. and DLG services lose all existing associations and data in transit. you must have purchased the high availability option when ordering Application Enablement Services 6.

For information about configuring High Availability Failover.Installation overview Requirements for High Availability Failover To take advantage of the Application Enablement Services on System Platform High Availability Failover (High Availability Failover) feature you will need the following components. 10 Implementing Application Enablement Services on System Platform R6. see the Avaya Aura® Application Enablement Services Administration and Maintenance Guide. 02-300357. The Avaya Aura® Application Enablement Services on System Platform offer includes one Dell R610 server. • For new installations. two dedicated Dell R610 servers or for upgrade installations. two dedicated S8800 servers. • Dedicated gigabit-link crossover connection for high availability pings and distributed replicated block device (DRBD) data transfer between active and standby servers.1 February 2011 . you will need to acquire an additional Dell R610 server. If you want to take advantage of the High Availability Failover feature.

02-300357. The installation program maps these virtual ethernet IP addresses to physical Ethernet interface ports. High Availability Failover can be configured on any free physical port through the System Platform web console. eth1. • If your configuration uses two network interfaces (referred to as a dual NIC configuration). From System Platform 6. Virtual eth1 maps to physical eth2 by default and can be configured to any other available port through the System Platform web console. you need to provide an IP address for eth0 and eth1. and the application bridge (virtual eth1) was assigned to physical eth3. you will need to provide the network configuration for the virtual Ethernet interfaces (eth0 and eth1 ). • If your configuration uses only one network interface (referred to as a single NIC configuration). Implementing Application Enablement Services on System Platform R6.0 and on. As a guest domain. when you install the Application Enablement Services software. eth2. which are designated in the software as eth0. you only need to provide an IP address for eth0. Keep in mind that these “eth” settings refer to virtual Ethernet interfaces. All network configuration can be performed from the Avaya Aura® System Platform web console. That is. For more information.1 February 2011 11 . AE Services is responsible for configuring its virtual Ethernet interfaces. physical eth2 was reserved for High Availability Failover.Network interfaces for the server Network interfaces for the server Network interfaces are also referred to as Ethernet interfaces or NICs (a term derived from network interface cards). Virtual eth0 maps to physical eth0. Note: In previous System Platform versions. see the Avaya Aura® Application Enablement Services Administration and Maintenance Guide. AE Services runs on System Platform as a guest domain. eth3.

Installation overview Application Enablement Services Ethernet interfaces 12 Implementing Application Enablement Services on System Platform R6.1 February 2011 .

The NICs must be on separate networks or network segments. The eth1 interface is reserved for Avaya technicians to use for remote access. the client network is referred to as the production (or public) network. One network segment is used for the AE Services server and Communication Manager and another network segment for is used for client and media connectivity (LAN. AE Services recommends a single NIC configuration for connectivity to most S8300. you use two network interfaces for connectivity to two separate network segments. and S8500c Communication Manager media servers. switch. AE Services supports using a dual NIC configuration for S8400. you must configure the IP interface for the AE Services server to be accessible over the public Internet for the registration of IP endpoints. and the client application computer must reside on a private LAN. • Use eth1 for the IP address of the private network. or WAN). a virtual LAN (VLAN). always use the following settings for a dual NIC configuration: • Use eth0 for the IP address of the AE Services server (production network). In a dual NIC configuration. and eth3. Implementing Application Enablement Services on System Platform R6. or a WAN. and the Communication Manager segment is referred to as the private network segment. The AE Services server. S8500c. Important: When you install the AE Services software. See Network interface (NIC) settings on page 14 for more information. the AE Services server uses one NIC for client. Dual NIC configuration In a dual NIC configuration. VLAN. Important: When you install the AE Services software. That is. and media connectivity.Single NIC configuration Single NIC configuration In a single NIC configuration. Communication Manager. and S8800 Communication Manager media servers.1 February 2011 13 . S8700. eth1. The Dell R610 server and S8800 server have four physical network interfaces: eth0. you use one network interface. S8400. eth2. In a single NIC configuration. always use eth0 for a single NIC configuration.

you must administer 100-Mbps / full / Lockdown at each end of the Ethernet link. See Network interface (NIC) settings on page 14 for more information. The eth1 interface is reserved for Avaya technicians to use for remote access. • Lockdown for Gigabit links is highly discouraged.1 February 2011 . it negotiates the network speed and duplex mode with the Ethernet switch. eth2. • 10-Megabit and/or half-duplex operation is never acceptable and should be corrected.com/css/P8/documents/100121639. eth2. • Lockdown: 100-Mbps interfaces 100-Mbps interfaces: Lockdown (auto-neg) . you must administer 1000-Mbps / full / auto-neg at each end of the Ethernet link. Keep in mind the following: • Auto-neg is highly desired for Gigabit links. a duplex mismatch will occur. you must administer 100-Mbps / full / auto-neg at each end of the Ethernet link. or eth3).Installation overview The Dell R610 server and the S8800 server have four physical network interfaces: eth0. Otherwise. see Ethernet Link Guidelines at https://support.Gigabit interfaces: Auto-negotiation (auto-neg) . 14 Implementing Application Enablement Services on System Platform R6.on In this case.on In this case. eth1.avaya. . Verify that both ends of the Ethernet link operate at the same desired speed and duplex settings. • Auto-neg or Lockdown is acceptable for 100-Megabit links.100-Mbps interfaces: Auto-negotiation (auto-neg) . You can choose two of the three available network interfaces (eth0.off In this case. Both ends of the Ethernet link must be set to the same mode. Network interface (NIC) settings The NIC choices for all network interfaces are as follows: • Auto-Negotiate: . and eth3. Important: AE Services defaults to auto-negotiation mode. For detailed information about using auto-negotiation and Lockdown. AE Services recommends that you use eth0 and eth2.

Network latency requirements See “Editing the NIC configuration (optional)” in the Avaya Aura® Application Enablement Services Administration and Maintenance Guide. the wait step must be greater than 2 seconds. set up the TCP/IP links (CTI links) between the AE Services server and Communication Manager with the following network latency characteristics: • No more than a 200 ms average round-trip packet delivery time. • If the switch receives no response to a route select. as measured with ping over every one-hour time period These requirements are necessary to maintain the AE Services communication channel with each Communication Manager C-LAN over a LAN/VLAN or WAN.1 February 2011 15 . Considerations include: • If the CTI application issues route requests.Dropped during a long network outage Note: The communication channel between the AE Services server and the Communication Manager requires a hub or data switch. as measured with ping over every one-hour time period • Periodic spiked delays of no more than 2 seconds while maintaining the 200 ms average round-trip delivery time. the NIC speed 1000. Implementing Application Enablement Services on System Platform R6. With a maximum delay of 2 seconds. you can reduce the wait step time-out accordingly. Network latency requirements Regardless of the type of network used (LAN.1 and later. the associated vector “wait” step must have a value greater than the largest “periodic spiked delay”. or . so you must program the vector to deal with this condition. 02-300357. VLAN or WAN). If you encounter “periodic spiked delays” greater than 2 seconds. If you can guarantee “periodic spiked delays” of less than 2 seconds.Stored and retransmitted after recovering from a short network outage. Avaya does not support the use of a crossover cable. Note: In AE Services 6. messages are either: . the call will follow the remaining steps in this specific vector. full duplex with auto-negotiate is supported if AE Services is connected to Communication Manager Processor Ethernet that has the same NIC settings. to set up the NICs with the recommended settings.

Standard Edition (J2SE) 1.1.x or later provides link bounce resiliency for the Application Enablement Protocol (AEP) transport links that AE Services uses. These features are available only on Communication Manager 5. • AE Services DMCC applications that use the High Availability Failover feature require the Communication Manager H. you will need to provide workstations for the AE Services client applications.x .2 or later.x software running on an IP-enabled media server.1 supports both CLAN interfaces and Processor Ethernet connections when implementing Enterprise Survivable Server (ESS) and Local Survivable Processor (LSP) configurations.x . or 6. 5.1 February 2011 . Media. 16 Implementing Application Enablement Services on System Platform R6.x . or 6. 5.6 client. and Call Control (DMCC) clients: You can develop and run Device.Installation overview Client workstation provisioning Although client workstations are not a requirement for installing the AE Services software. • TSAPI and CVLAN clients: See the Avaya Aura®Application Enablement Services TSAPI and CVLAN Client and SDK Installation Guide (02-300543) for hardware and software requirements.NET client API for Windows. and an XML client API. • Device. a . Note: Communication Manager 4. Media. Communication Manager and media server requirements To use AE Services 6. and Call Control applications on any computer that is capable of running the Java 2 Platform. Downloading the AE Services release notes Make sure you read the AE Services release notes before you install the software.x. • AE Services 6.323 Time-to-Service registration feature. you must have the official Communication Manager Release 4.x. • AE Services supports all media servers and gateways that support Communication Manager Release 4.

PDF document. From the main menu on the Welcome to Avaya Support page. Implementing Application Enablement Services on System Platform R6.com. Click the letter A in the alphabet listing. which defaults to the current release. 6. select Documentation > Release Notes & Software Update Notes. 2. From the Application Enablement Services Release Notes & Software Update Notes page. Make sure you have the Adobe Acrobat Reader installed on your computer. 5. 1.PDF document to your computer. 3. 4. select the title of the release notes you want to download. type https://support. (Optional) Save the . Click Avaya Aura® Application Enablement Services. Your browser displays the release notes as a . In the address bar of your browser.1 February 2011 17 .avaya.PDF documents.Downloading the AE Services release notes Note: AE Services provides release notes as .

1 February 2011 .Installation overview 18 Implementing Application Enablement Services on System Platform R6.

Nothing needs to be added to the server on site.Chapter 2: Installation prerequisites Application Enablement Services on System Platform installation overview The Avaya Aura® Application Enablement Services on System Platform installation has many parts to it. The server (or servers) require CAT5 Ethernet cables to connect to the customer's network and to each other for High Availability Failover. keyboard. The server arrives at the customer's site with all the appropriate components and memory.1 February 2011 19 . Access the System Platform installer and the Application Enablement Services installer through DVDs. Implementing Application Enablement Services on System Platform R6. It requires: • installing the server (or servers) hardware • connecting the server to the customer's network • connecting two servers if using the high availability failover option • Installing the System Platform software on the server • installing the Application Enablement Services software on the server • configuring the Secure Access Link (SAL) gateway included in System Platform for remote support and alarming Server hardware installation and connectivity Application Enablement Services on System Platform is installed on a Dell R610 server. You must burn the ISO images to blank DVDs. Application Enablement Services on System Platform software You can install Application Enablement Services on System Platform using two different methods: • A laptop connected to the Services port on the server (this port is identified as eth1 in the server). and mouse connected to the appropriate ports on the server. • A video monitor. Avaya recommends that you verify that the ISO images are not corrupted before starting each installation. Both servers must be connected with a gigabitcrossover cable on the ports identified as the High Availability Failover configured port on the operating system.

Installation worksheet for AES on System Platform The Application Enablement Services installer and System Platform installer require you to fill in several fields. Product Licensing and Delivery System (PLDS) The Application Enablement Services on System Platform downloadable software and the licenses for installing Application Enablement Services on System Platform are available in the PLDS Web site (https://plds. Business Partners without a SAL Concentrator must provide their own B2B VPN connection (or other IP-based connectivity) to deliver remote services. Value Notes 20 Implementing Application Enablement Services on System Platform R6. Business Partners and/or their customers need to ensure that SAL is configured and registered properly. Secure Access Link (SAL) Application Enablement Services on System Platform includes the Avaya Secure Access Link (SAL) gateway to manage service delivery (alarming and remote access).) You must configure SAL with the customer's network and register during the installation process. System Domain (Dom-0) network Field IP address Hostname This is the hostname for System Domain (Dom 0). This address is not known until after AE Services is installed.1 February 2011 .avaya. SAL requires upload bandwidth (customer to Avaya) of at least 90kB/s (720kb) with latency no greater than 150 ms (round trip. Complete this worksheet prior to installation. Print out the following tables and work with your network administrator to fill in the rows. For Avaya to provide support.Installation prerequisites A worksheet that identifies information required at time of installation is provided. SAL does not support modem connections. Avaya support will be delayed or not possible if SAL is not properly implemented. See Installation worksheet for AES on System Platform on page 20. Having the information available at the time of installation makes it go faster and ensures accuracy. Note: A license can not be generated for Application Enablement Services on System Platform until the MAC address on the Console domain (Cdom) is determined.com).

It has a virtual interface that uses the physical interface in System Domain (Domain-0). if you do not configure gateways for them.1 February 2011 21 . Field Static IP Value/requirement Notes The static IP address for the Ethernet interface that Implementing Application Enablement Services on System Platform R6. Optional Optional NTP Server 2 NTP Server 3 Ethernet interface that connects to the customer network This field displays the physical Ethernet interface (NIC) that connects to the customer network. Because System Domain acts like a bridge. This is the hostname for Console Domain. You must configure this interface for IP. The specific Ethernet interface number depends on the server model being used. Value/requirement Notes Primary DNS Secondary DNS NTP Server 1 Optional Use of NTP server is optional. Avaya recommends its use. the IP address that you enter here must be a valid IP address. However.Installation worksheet for AES on System Platform Console Domain network Field IP address Value/requirement Notes The Console Domain does not have a physical interface. Hostname General network settings Field Network mask Default gateway This will be the default gateway for all the virtual machines. Further. the Console Domain must be on the same network as System Domain (Domain-0).

Field root admin cust ldap Value/requirement Notes Application Enablement Services template installation These fields are on the Template Details page. • Other hardware as ordered.1 February 2011 .avaya.255. UPS is a required component. You should change these default passwords. • Slide rails to mount the servers in a standard 19-inch. such as an uninterruptible power supply (UPS). The form is available on http://support. and two are for High Availability Failover configuration. Click More Resources > Equipment Registration (Partners only). Field AES hostname ETH0 IP address of the AES ETH1 IP address of the AES ETH1 network mask Value/requirement Notes What Avaya provides Avaya provides the following items for installing System Platform: • One or two servers. • System Platform installation software. • Product registration form.com. Click Universal Install/SAL 22 Implementing Application Enablement Services on System Platform R6.Installation prerequisites Field Value/requirement Notes connects to the customer network. One is for a standard configuration.255. Subnet mask Default gateway IP 255. 4-post rack that have square holes.0 (default) Passwords Default passwords are provided.

and us. • USB keyboard. see Registering the system. Modem connectivity is not supported. Note: Depending on the capabilities of the network interface card (NIC) in your laptop. What customer provides The customer must provide the following items for installing System Platform. Implementing Application Enablement Services on System Platform R6. Note: Avaya provides the System Platform installation software. • DVDs written with the software for installing. sv-latin1. uk. • Gigabit-certified Ethernet cable for High Availability Failover. • Filled-out worksheets with the system and network information needed for installation and configuration. Note: Avaya Partners must arrange for their own IP-based connectivity (for example.What customer provides Product Registration Request Form under Non-Regional (Product) Specific Documentation. The supported keyboard types are sg-latin1. • Standard equipment rack properly installed and solidly secured. • Access to the customer network. For more information. slovene. See the documentation for your laptop. and VGA monitor or laptop with an Ethernet crossover cable. • A computer that can route to the System Platform server that has Internet Explorer 7 or Firefox 2 or Firefox 3 installed on it. sk-qwerty. USB mouse. The customer must either purchase the System Platform CD or download the ISO image and write that image to a CD or DVD. • (Optional) Electronic preinstallation worksheet (EPW) and Avaya Bulk Import Tool (ABIT) files. you might be able to use a straight-through cable for this connection. • (Optional) VPN Gateway for providing remote access to Avaya Partners. trq. uautf. B2B VPN) to provide remote services.1 February 2011 23 .

enter the Partner Link ID. You will be redirected to the PLDS registration page.iso. If you are registering: • as an Avaya Partner. and then write the ISO image to a DVD.avaya. send an e-mail to prmadmin@avaya. or you can use a stand-alone SAL Gateway.iso where X is the release. System Platform includes an embedded SALGateway. • AE Services software: AES template. You will be redirected to the Single sign-on (SSO) Web site. verify the ISO image. 3. you must download the application from the Product Licensing and Delivery System (PLDS) Web site.1 February 2011 . Log in to SSO using your SSO ID and Password. Registering for PLDS 1. • as a customer. Software download Required software Application Enablement Services on System Platform installation requires that you install the following software: • System Platform software: System Platform X.com.Installation prerequisites Note: Secure Access Link (SAL) Gateway is required for remote service and alarming. System Platform 6.com). Go to the Avaya Product Licensing and Delivery System (PLDS) Web site (https:// plds. For each software application. If you do not know your Link ID.Company Sold-To .0. for example.Ship-To number 24 Implementing Application Enablement Services on System Platform R6. 2. enter one of the following: .

7. Implementing Application Enablement Services on System Platform R6. 2.avaya. select Click to download your file now. Enter your Login ID and password to log on to the PLDS Web site.1 February 2011 25 . Avaya will send you the PLDS access confirmation within one business day. install Active X. 3. click Install. Click Submit. PLDS displays the downloads again with a checkmark next to the downloads that have been completed successfully. When the confirmation box displays. Downloading software in PLDS 1.com in your Web browser to access the Avaya PLDS Web site. 8. 4. 6. Select Assets from the Home page and select View Downloads. and continue with the download. Click the download icon from the appropriate download. Use this procedure if you downloaded ISO images to a Linux-based computer. 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. Type http://plds. When the security warning displays. If you receive an error message.Software download . Verifying the downloaded ISO image Verifying the ISO image on a Linux-based computer Use this procedure to 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. click on the message.License Authorization Code (LAC) 4. When the install is complete.

md5summer. download the ISO image again and reverify the md5 checksum. If the numbers are different.Installation prerequisites 1. where filename is the name of the ISO image. If the numbers are different.iso file extension in the filename. 5.org/hashcheck/ Note: Avaya has no control over the content published on these external sites. 26 Implementing Application Enablement Services on System Platform R6. Include the . Use this procedure if you downloaded ISO images to a Windows-computer.php?kat=70 • http://code. 4.org/ • http://zero-sys. Ensure that both numbers are the same.net/portal/index. 2.kliu. Ensure that both numbers are the same. Run the tool on the downloaded ISO image and note the md5 checksum. 3. 3.1 February 2011 . Verifying the ISO image on a Windows-based computer Use this procedure to 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. Download a tool to compute md5 checksums from one of the following Web sites: • http://www. 4. Please use the content only as reference. Compare the md5 checksum of the ISO image to be used for installation with the md5 checksum that is displayed for the ISO image on the PLDS Web site. 2. Enter md5sum filename. download the ISO image again and reverify the md5 checksum. Compare the md5 checksum of the ISO image to be used for installation with the md5 checksum that is displayed for the ISO image on the PLDS Web site. 1.

Important: When the ISO image is being written to the DVD. If you are writing to a CD. 2. Avaya recommends a slower write speed of 4X or at a maximum 8X. which can render the DVD useless. 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. you can use a CD instead of a DVD. When writing the data to the DVD. If you are writing to a DVD. write-once. this procedure requires a computer or server that has a CD writer and software that is capable of writing ISO images to CD. do not run other resource-intensive applications on the computer. Implementing Application Enablement Services on System Platform R6. this procedure requires a computer or server that has a DVD writer and software that is capable of writing ISO images to DVD. Multiple rewrite DVDs are prone to error and should not be used. Note: If the software files you want to write on media are less than 680 Mb in size.1 February 2011 27 . Writing the ISO image to DVD or CD Prerequisites 1. Any application that uses the hard disk intensively can cause a buffer underrun or other errors.Software download Writing the downloaded software to DVD DVD recommendations Avaya recommends use of high quality. Write the ISO image of the installer to a DVD or CD. Attempting to write to the DVD at higher or the maximum speed rated on the disc is likely to result in write errors. Download any required software from PLDS. blank DVDs.

Installation prerequisites 28 Implementing Application Enablement Services on System Platform R6.1 February 2011 .

Implementing Application Enablement Services on System Platform R6. Hardware Owner's Manual • Dell™ PowerEdge™ R610 Systems. In the address bar of your browser. See the following documents to install and configure the Dell R610 server. Migrations. type support. From the menu on the left side of the Welcome to Avaya Support page. Accessing the Avaya support web site To access the Dell R610 server documents on the Avaya support web site. 3. • Installing the Dell™ PowerEdge™ R610. Getting Started with Your System These documents are available on the Avaya support web site.Chapter 3: Installing the Dell R610 server The Dell R610 server supports several Avaya software solutions. 4.com 2.1 February 2011 29 . select Documentation > Installation. Upgrades & Configurations. document number 03-603793 • Dell™ PowerEdge™ R610 Systems. Select Common Servers. Cable Management Arm Installation • Dell™ PowerEdge™ R610 Systems. Rack Installation • Dell™ PowerEdge™ R610 Systems.avaya. do the following: 1. Click the letter C in the alphabet listing.

1 February 2011 .Installing the Dell R610 server 30 Implementing Application Enablement Services on System Platform R6.

you can use an IP hub. Avaya supports use of the open source Telnet/SSH client application PuTTY. 1 Task If you are installing System Platform from a laptop. you might be able to use a straightthrough cable for this connection. perform the following tasks: • Ensure that a Telnet and Secure Shell application are installed on the laptop. • Disable use of proxy servers in the Web browser on the laptop. See Disabling proxy servers in Microsoft Internet Explorer on page 35 or Disabling proxy servers in Mozilla Firefox on page 35 . See the documentation for your laptop.Chapter 4: Installing System Platform Installation checklist for System Platform Use this checklist to install System Platform. Note: Depending on the capabilities of the network interface card (NIC) in your laptop. 2 Connect your laptop to the services port with an Ethernet crossover cable.1 February 2011 31 . If you do not have a crossover cable. Important: If you are using the High Availability Failover option. See Configuring the laptop for direct connection to the server on page 34. • Configure the IP settings of the laptop for direct connection to the server. No. install the same version of System Platform on both servers. Notes Implementing Application Enablement Services on System Platform R6.

Installing System Platform No. Verify that the image on the System Platform DVD is not corrupt. If using the server console to install System Platform.1 February 2011 . See Configuring network settings for Console Domain on page 42. Configure the network settings for the System Domain (Domain-0). See Configuring network settings for System Domain (Domain-0) on page 40. See Starting the installation from your laptop on page 36. Configure the network settings for the Console Domain. See #unique_34. See Starting the installation from your laptop on page 36 or Starting the installation from the server console on page 37 depending on your selection of installation method. If using your laptop to install System Platform. enter the vspmediacheck command and press Enter. establish a Telnet connection to the server. The vspmediacheck command verifies that the image on the System Platform DVD is not corrupt. If using your laptop to install System Platform. See Selecting the type of keyboard on page 38. Notes 5 6 7 8 9 10 32 Implementing Application Enablement Services on System Platform R6. Select the required keyboard type. 3 4 Task Turn on the server. See Starting the installation from your laptop on page 36 or Starting the installation from the server console on page 37 depending on your selection of installation method. verify the media within the System Platform installation wizard. Place the DVD into the DVD drive on the server.

See Verifying installation of System Platform on page 47. If applicable. See Configuring High Availability Failover on page 61. Configure the date and time or set up NTP server for the System Platform server. do not install a solution template on the server that will serve as standby. See Configuring the SAL Gateway.com.Installation checklist for System Platform No. Notes 12 13 14 15 16 Important: If you are using the High Availability Failover option.1 February 2011 33 . 17 Configure the SAL gateway for remote access and alarming. The solution template is propagated from the active node to the standby node when you start High Availability Failover. If you do. Verify access to the System Platform Web Console. See Configuring the time zone for the System Platform server on page 44. If you are using a bundled System Platform installation (with a solution template). See Installing Application Enablement Services template on page 63. Install any patches that are available.avaya. See Configuring System Platform passwords on page 45. Check for System Platform patches at http://support. See “Chapter 5: Installing patches. disable the template installation on the standby server.” Install the AES template. 18 Implementing Application Enablement Services on System Platform R6. Configure the System Platform passwords. configure System Platform High Availability Failover. 11 Task Configure the time zone for the System Platform server. you will not be able to start High Availability Failover. See Configuring the date and time for the System Platform server on page 44.

Click Properties. Note: The following procedure is for Microsoft Windows XP. Make sure that you change the network settings on the laptop before connecting to the server.1 February 2011 . 4. The procedure may differ slightly for other versions of Windows. If you do not have a mouse. keyboard. If you use a laptop to install the software. 1.Installing System Platform Installation methods Use one of the following methods to install System Platform: • Laptop connected to the services port on the server. use the Tab key to navigate between fields. In the This connection uses the following items box. and default gateway of the laptop before you connect the laptop to the server. See Configuring the laptop for direct connection to the server on page 34. Double-click Network Connections > Local Area Connection. 5. In the Local Area Connection Status dialog box. Note: You can complete the installation by using only a keyboard and monitor. and mouse connected to the appropriate ports on the server. 3. 2. 34 Implementing Application Enablement Services on System Platform R6. Connecting your laptop to the server Configuring the laptop for direct connection to the server You must manually configure the IP address. subnet mask. you must have an SSH and Telnet client application such as PuTTY installed on the laptop and Telnet must be enabled to install System Platform. • Video monitor. Click Start > Control Panel. click Properties. click Internet Protocol (TCP/IP).

7. 10. 2.13. Implementing Application Enablement Services on System Platform R6. In the IP address field. type 255.11.5.Connecting your laptop to the server 6. Clear the Use a proxy server for your LAN option. Click the Connections tab. Click OK.6.252.11. Tip: When you need to reenable the proxy server. select the Use a proxy server for your LAN option again. 8. 6. The procedure may differ slightly if your laptop is running Linux or another operating system. 9.255. 4. Click Tools > Internet Options. you must disable the proxy servers in Internet Explorer. Caution: Do not click the Alternate Configuration tab.255. 5. you must disable the proxy servers in Firefox. Disabling proxy servers in Mozilla Firefox To connect directly to the services port. type 192. Start Internet Explorer.13.1 February 2011 35 . Click LAN Settings. Disabling proxy servers in Microsoft Internet Explorer To connect directly to the services port. 3. Click OK to close each dialog box. select Use the following IP address on the General tab. In the Internet Protocol (TCP/IP) Properties dialog box. In the Subnet mask field. In the Default gateway field. 1. Note: This procedure is for Firefox on a Windows-based laptop. type 192.

3.Installing System Platform 1. Turn on the server. 5. 6. 2. Insert the System Platform DVD in the server DVD drive. you might be able to use a straight-through cable for this connection. 36 Implementing Application Enablement Services on System Platform R6. 4. 1. The server boots from the DVD. 3. you can use an IP hub. If you do not have a crossover cable. See the documentation for your laptop. Tip: When you need to reenable the proxy server. Start Firefox.1 February 2011 . such as PuTTY. is installed on your laptop. Click OK to close each dialog box. Starting the installation Starting the installation from your laptop Prerequisites • A Telnet/SSH application. 7. Click the Network tab. • IP settings of the laptop are configured for direct connection to the server. Connect your laptop to the services port with an Ethernet crossover cable. 2. Select the Advanced option. • Use of proxy servers is disabled. Click Tools > Options. select the appropriate option again. Click Settings. Note: Depending on the capabilities of the network interface card (NIC) in your laptop. Select the No proxy option.

the system might not display the Keyboard Type screen correctly. b. USB mouse. Insert the System Platform DVD in the server DVD drive. Related topics: Connecting to the server through the services port on page 48 Starting the installation from the server console Prerequisites Connect a USB keyboard.13. Implementing Application Enablement Services on System Platform R6.13. 1. See Selecting the type of keyboard on page 38. Turn on the server.6. Under Received data assumed to be in which character set . b. This screen problem does not affect the installation. Verify that the laptop can ping the service port by performing the following steps: a. and video monitor to the server. Click Start > Run. c. Type ping -t 192.1 February 2011 37 . Open an SSH session by performing the following steps: Important: If you use a Telnet client other than PuTTY. Click Open to open a PuTTY session. select Telnet. 2. The system displays the Keyboard Type screen. Under Connection type. d. f. e. Next steps Select the required keyboard type. a.Starting the installation 4. 5. Under Window in the left navigation pane. select Translation.6 Note: Allow sufficient time for the ping command to return continuous responses before proceeding to the next step.11. or if you forget to set the proper terminal emulation for the PuTTY client. Open the PuTTY application. select UTF-8 from the list. enter 192. In the Host Name field.11.

The system then displays the Waiting for Telnet connection screen. The vspmediacheck command verifies that the image on the System Platform DVD is not corrupt. Important: If you do not press Enter or type vspmediacheck within 30 seconds of the system displaying the Avaya screen. so you can connect to the server through Telnet. sk-qwerty. At this point. See Verifying the System Platform image on the DVD on page 39. 2. sv-latin1. slovene. The supported keyboard types are sg-latin1. Use the Tab key to highlight OK and press Enter. Selecting the type of keyboard 1. • The system displays the CD Found screen if you are installing System Platform from a laptop. reset the server to restart the installation. trq. if you want to install through the server console. Next steps Select the required keyboard type. uk. or if you are installing System Platform from the server console and entered the vspmediacheck command at the boot prompt on the Avaya screen. select the type of keyboard that you have. Within 30 seconds of the system displaying the Avaya screen. • The system displays the System Domain Network Configuration screen if you are installing System Platform from the server console and did not enter the vspmediacheck command at the boot prompt on the Avaya screen. The system displays the Keyboard Type screen.1 February 2011 . 38 Implementing Application Enablement Services on System Platform R6. and us. On the Keyboard Type screen.Installing System Platform The server boots up from the System Platform DVD and displays the Avaya screen. 3. See Selecting the type of keyboard on page 38. the system disables installation through the server console and enables installation through the services port. and press Enter. uautf. type vspmediacheck at the boot prompt on the Avaya screen. See Configuring network settings for System Domain (Domain-0) on page 40.

or if you are installing System Platform from the server console and entered the vspmediacheck command at the boot prompt on the Avaya screen. Next steps Configure the network settings for System Domain (Domain-0).1 February 2011 39 . make sure that you restart the server. On the CD Found screen. See Configuring network settings for System Domain (Domain-0) on page 40 Verifying the System Platform image on the DVD Use this procedure to verify that the System Platform image was copied correctly to the DVD. Note: If the DVD you are using is corrupt. you must write a new DVD with the System Platform image. perform one of the following actions: • To test the DVD.Verifying the System Platform image on the DVD Next steps • Verify that the System Platform image was copied correctly to the DVD. See Verifying the System Platform image on the DVD on page 39. After the test is complete. Before using the new DVD. The system displays the CD Found screen if you are installing System Platform from a laptop. If you choose to test the DVD. the system displays another screen with a progress bar and the percentage of completion. select Skip. See Configuring network settings for System Domain (Domain-0) on page 40. use the Tab key to select OK. The system displays the System Domain Network Configuration screen. OR • Configure the network settings for System Domain (Domain-0). • To skip the test and begin the installation immediately. the system displays whether the image passed the test. Related topics: Writing the ISO image to DVD or CD on page 27 Implementing Application Enablement Services on System Platform R6.

mydomainname.255. 40 Implementing Application Enablement Services on System Platform R6.0. The server displays a default value of 255. Modify the subnet mask if necessary. for example. b. On the System Domain Network Configuration screen.com. 4. 2.255. SPDom0. c. see System Domain Network Configuration field descriptions on page 41.Installing System Platform Configuring network settings for System Domain (Domain-0) 1. 3. Perform the following steps to configure the interface that is connected to the customer network: a. Complete the Default gateway IP field. complete the following fields: • Hostname. Enter a fully qualified domain name (FQDN). Complete the Static IP field. Press the Spacebar to either enable or disable entering IP addresses in IPv6 format. Use the Tab key to highlight the IPv6 Enabled field.1 February 2011 . Use the Tab key to highlight the Physical Devices field. • Primary DNS • (Optional) Secondary DNS For descriptions of the fields on this page.

See Configuring network settings for Console Domain on page 42. The default gateway IP address.mydomainname. This field displays the physical Ethernet interface (NIC) that connects to the customer network. (Optional) The secondary DNS server address. Next steps Configure network settings for Console Domain. a confirmation message is displayed.1 February 2011 41 . If you have enabled IPv6. Use the Tab key to highlight OK and press Enter to accept the configuration.Configuring network settings for System Domain (Domain-0) 5. 7. SPDom0. fill in the following fields: • IPv6 Address • IPv6 Prefix • IPv6 Gateway 6. You must configure this interface for IP. 8. Use the Tab key to highlight OK and press Enter. for example. Primary DNS Secondary DNS Physical Devices Static IP Subnet Mask Default gateway IP Implementing Application Enablement Services on System Platform R6. If IP forwarding is enabled. Use the Tab key to highlight the Enable IP Forwarding field. System Domain Network Configuration field descriptions Name Hostname Description The host name for System Domain (Domain-0). The specific Ethernet interface number depends on the server model being used. The subnet mask for the Ethernet interface that connects to the customer network. Press the Space bar to either enable or disable the IP forwarding as desired. Note: IP forwarding is enabled by default and is denoted by an asterisk (* character). The system displays the System Platform Console Domain Network Configuration screen.com. The primary Domain Name System (DNS) server address. This must be a fully qualified domain name (FQDN). The static IP address for the Ethernet interface that connects to the customer network.

1 February 2011 .Installing System Platform Name Description This default gateway IP address will be used for all the virtual machines if you do not specify gateway IP addresses for them. IPv6 Enabled The indicator to show whether the IP addresses required by System Platform need to be IPv6-compliant. for example. The indicator to show whether IP forwarding is enabled. IP forwarding enables access through the services port to virtual machines on System Platform. IP forwarding must be enabled for both SSH and Web Console access. including System Domain and Console Domain.mydomainname.2. complete the following fields to set up the Console Domain network: • Hostname. The IPv6 prefix for IPv6 Address. Enter an FQDN. An asterisk on the left of the field denotes that IP forwarding is enabled. On the VSP Console Domain Network Configuration screen. Application Enablement Services 5. The IP address of the default gateway for IPv6 traffic. IPv6 Address IPv6 Prefix IPv6 Gateway Enable IP Forwarding Configuring network settings for Console Domain 1.2 does not support IPv6. The IPv6-compliant IP address of System Domain. SPCdom. • Static IP 42 Implementing Application Enablement Services on System Platform R6.com.

Next steps Configure the time zone for the System Platform server. the IP address that you enter here must be a valid IP address. the Console Domain must be on the same network as System Domain (Domain-0). Static IP The IP address for the Console Domain.com. It has a virtual interface that uses the physical interface in System Domain (Domain-0).mydomainname. Note: The Console Domain does not have a physical interface. System Platform Console Domain Network Configuration field descriptions Name Description Hostname The host name for the Console Domain. Further. Select OK and press Enter to accept the configuration and display the Time Zone Selection screen. This must be an FQDN. See Configuring the time zone for the System Platform server on page 44. Because System Domain acts like a bridge. SPCdom.1 February 2011 43 . for example.Configuring network settings for Console Domain 2. Implementing Application Enablement Services on System Platform R6.

enter the DNS name or the IP address of your preferred NTP servers. b. See Configuring the date and time for the System Platform server on page 44. Avaya recommends setting the time correctly on this screen during the installation 2. If you are using an NTP server. Select Use NTP if you are using one or more NTP servers. Select OK and press Enter to accept the configuration and display the Date/Time and NTP setup screen. Select OK and press Enter to accept the configuration and display the Passwords screen. Configuring the date and time for the System Platform server Avaya recommends that you use a Network Time Protocol (NTP) server within your network to synchronize the time of the System Platform server. In the NTP server fields. 3. 2. Note: Ensure that the time set here is correct. Next steps Configure date and time for the System Platform server. On the Time Zone Selection screen. Therefore.Installing System Platform Configuring the time zone for the System Platform server 1. Set the current date and time on the Date/Time and NTP setup screen. perform the following steps on the Date/Time and NTP setup screen: a. select the time zone in which the server is located. Changing the time in a virtual machine environment requires rebooting the virtual machines. 44 Implementing Application Enablement Services on System Platform R6. 1.1 February 2011 .

Configuring System Platform passwords Prerequisites Configure the date and time for the System Platform server. See Configuring System Platform passwords on page 45. Implementing Application Enablement Services on System Platform R6. If you do not enter new passwords. Customers are responsible for managing their passwords. Use this login and password to log in to the local LDAP directory. enter new passwords for all logins. System Platform uses a local LDAP directory to store login and password details.1 February 2011 45 . Make a careful note of the passwords that you set for all logins. 1.Configuring System Platform passwords Next steps Configure System Platform passwords. You must enter each password twice to ensure that you are not making any mistakes in typing. Login root admin cust manager (for ldap) Default password root01 admin01 cust01 root01 Capability Advanced administrator Advanced administrator Normal administrator Administrator for the System Platform local Lightweight Directory Access Protocol (LDAP) directory. This login does not have permissions to access the System Platform Web Console. On the Passwords screen. The following table shows the default password for each login. Important: Avaya highly recommends that you enter new passwords instead of using the default passwords. the defaults are used.

If you are using the craft login. Next steps Verify System Platform installation. and Site Manager. the system displays the Linux login page for System Domain (Domain-0) after the reboot. you must have an ASG tool to generate a response for the challenge that is generated by the login page. Passwords field descriptions Note: Passwords must be at least six characters long. The first two ASG tools must be able to reach the ASG manager servers behind the Avaya firewall. The Avaya Services representative uses Site Manager to pull the keys specific to a site before visiting that site.Installing System Platform Passwords must be at least six characters long. you can see the Package Installation page with progress bars. 2. Important: If the DVD does not eject automatically. Result The installation takes approximately 5 minutes. Select OK and press Enter to accept the passwords and continue the installation. See Accessing the System Platform Web Console on page 50. the system ejects the DVD and reboots the server. 46 Implementing Application Enablement Services on System Platform R6. the Avaya Services representative uses those keys to generate a response for the challenge generated by the Logon page. followed by the Running page. Avaya recommends using uppercase and lowercase alphabetic characters and at least one numeral or special character. System Platform will not function correctly and will have to be reinstalled. This process can take up to 20 minutes. eject it manually. as the system completes the post-install scripts. After the installation is completed. Caution: Do not shut down or reboot the server during the first boot process of Console Domain. At the site. If you are installing from server console. See Verifying installation of System Platform on page 47. Many ASG tools are available such as Avaya Token Mobile. During this time.1 February 2011 . The system restarts the installation if the DVD is not ejected. attempt to access the Web Console. To determine if Console Domain has booted. Note: The Avaya Services craft login uses Access Security Gateway (ASG) for authentication. Avaya recommends using uppercase and lowercase alphabetic characters and at least one numeral or special character. Avaya Web Mobile. If you shutdown or reboot the server during the first boot of Console Domain.

1 February 2011 47 . Important: You must wait for the first boot process to finish before you can perform this procedure. You cannot access Console Domain until the first boot process is finished. 3. e. and then click Open. Use this login and password to log in to the local LDAP directory. and type the password that you entered for the admin login during System Platform installation. type the IP address of Console Domain.Verifying installation of System Platform Name root Password Description The password for the root login. cust Password ldap Password The password for the cust login. Type exit to exit Console Domain. 1. Verifying installation of System Platform Prerequisites If you are performing this task from a laptop that is connected to the services port. enable IP forwarding. d. Perform the following steps to log in to Console Domain as cust: Implementing Application Enablement Services on System Platform R6. The first boot process for Console Domain can take up to 20 minutes. This login does not have permissions to access the System Platform Web Console. 2. In the Connection type field. After completing installation of System Platform. Start PuTTY from your computer. c. log in as admin. b. Access the System Platform Web Console. admin Password The password for the admin login. See Accessing the System Platform Web Console on page 50. System Platform uses a local LDAP directory to store login and password details. In the Host Name (or IP Address) field. select SSH. See Enabling IP forwarding to access System Platform through the services port on page 49. When prompted. Perform the following steps to log in to Console Domain as admin: a. perform this procedure to check for problems with the installation. The password for the ldap login.

select SSH. 3.13. d. type the IP address of Console Domain.6. b. For Connection type. type 192. 1. select SSH. e. In the Host Name (or IP Address) field. See the documentation for your laptop. and type the password that you entered for the cust login during System Platform installation.6 to the services port. When prompted. contact Tier 3 Engineering.1 February 2011 . you can use an IP hub. Accessing System Platform Connecting to the server through the services port Prerequisites • A Telnet/SSH application. Type exit to exit Console Domain. In the Host Name (or IP Address) field. The system assigns the IP address 192. 2. and then click Open. 4. is installed on your laptop. In the Connection type field. Note: Depending on the capabilities of the network interface card (NIC) in your laptop. Important: If you cannot log in to Console Domain as admin or cust or access the System Platform Web Console.13.Installing System Platform a. c. • IP settings of the laptop are configured for direct connection to the server. such as PuTTY. 48 Implementing Application Enablement Services on System Platform R6.11. • Use of proxy servers is disabled. Connect your laptop to the services port with an Ethernet crossover cable. Start PuTTY from your computer. you might be able to use a straight-through cable for this connection. Start a PuTTY session. log in as cust. If you do not have a crossover cable.11.

Start an SSH session. 9. If you disabled IP forwarding during installation and later want to enable it. always disable IP forwarding after finishing your task. type 22. b. You can set the IP forwarding status as enabled or disabled during installation of System Platform. Start an SSH session. For security reasons. Click Open. Log in as admin or another valid user. Related topics: Configuring the laptop for direct connection to the server on page 34 Disabling proxy servers in Microsoft Internet Explorer on page 35 Disabling proxy servers in Mozilla Firefox on page 35 Enabling IP forwarding to access System Platform through the services port To access virtual machines on System Platform by connecting a laptop to the services port. Implementing Application Enablement Services on System Platform R6. In the command line. 2. IP forwarding must be enabled for both SSH and Web Console access. To enable IP forwarding: a. b. 1. 6. Log in to System Domain (Domain-0) as admin. Click Yes to accept the server's host key and display the PuTTY window. When you finish the session. In the Port field. type exit and press Enter to close PuTTY. you must enable IP forwarding on System Domain (Domain-0) .1 February 2011 49 . perform the following procedure. IP forwarding is enabled by default.Accessing System Platform 5. c. In the command line. To disable IP forwarding: a. Note: The system displays the PuTTY Security Alert window the first time you connect to the server. 7. type service_port_access enable and press Enter. c. type ip_forwarding disable and press Enter. 8. Log in to System Domain (Domain-0) as admin.

Click I Accept to accept the end-user license agreement. Open a compatible Internet browser on your computer. 6. If you get a certificate error. 50 Implementing Application Enablement Services on System Platform R6. 2. Click Continue. 1. See Enabling IP forwarding to access System Platform through the services port on page 49. then follow the instructions in your browser to install a valid certificate on your computer. You cannot access Console Domain until the first boot process is finished. You can access the System Platform Web Console from a Web browser on your laptop or another computer connected to the same network as the System Platform server. Currently. System Platform supports Microsoft Internet Explorer 7 and Firefox 2 and 3. Note: This is a secure site. Enter a valid user ID. enable IP forwarding. 3. Type the URL: https://ipaddress. 4.Installing System Platform Accessing the System Platform Web Console Prerequisites If you are performing this task from a laptop that is connected to the services port. 7. The system displays the Virtual Machine List page in the System Platform Web Console. The first boot process for Console Domain can take up to 20 minutes. Enter a valid password. Click Log On. The system displays the License Terms page when you log in for the first time. where ipaddress is the IP address of the Console Domain that you configured during installation of System Platform. Important: You must wait for the first boot process to finish before you can perform this procedure.1 February 2011 . 5.

To exit Console Domain and return to System Domain. you are connected to System Domain.1 February 2011 51 . login as admin. and then type xm console udom-id. Alternatively. Then type su — root and enter the root password to log in as root. In the Connection type field. 1. When prompted. In the Host Name (or IP Address) field. type xm list. type the following command to log in as the root user: su — root 6. When prompted. click Virtual Machine Management > Manage. Tip: You can obtain the IP address of System Domain (Domain-0) from the Virtual Machine Management page of the Web Console. In the navigation pane of the Web Console. 3. select SSH. Implementing Application Enablement Services on System Platform R6. 4.Accessing System Platform Related topics: Enabling IP forwarding to access System Platform through the services port on page 49 Accessing the command line for System Domain If you have physical access to the system. press Control+]. note the ID for udom. 5. type the IP address of System Domain. When you connect to the services port. Once logged in. use an SSH (Secure Shell) client such as PuTTY to set up a remote connection from your computer. 2. After logging in. the system prompts you with the Linux command prompt. Tip: To access Console Domain from System Domain. log in as admin. Enter the password for the root user. and then click Open. you can log in to the system directly. Start PuTTY from your computer.

In the Host Name (or IP Address) field. You cannot access Console Domain until the first boot process is finished. select SSH. 8. Start PuTTY from your computer. type exit to exit root login. Enter the password for the root user. After performing the necessary tasks. Type exit again to exit System Domain. 3. Type exit again to exit Console Domain. 1. type the IP address of Console Domain. 52 Implementing Application Enablement Services on System Platform R6. type the following command to log in as the root user: su — root 6. After performing the necessary tasks. When prompted. type exit to exit root login. 2. In the Connection type field. The first boot process for Console Domain can take up to 20 minutes. 8. Once logged in. 7. Accessing the command line for Console Domain Important: You must wait for the first boot process to finish before you can perform this procedure.1 February 2011 . 5.Installing System Platform 7. 4. Tip: The IP address of Console Domain (cdom) is the same as the IP address of the System Platform Web Console. log in as admin. and then click Open.

download.com. Go to http://support.Chapter 5: Installing patches Patch management You can install. click Add to locate the service pack file on your computer and then upload. choose a location to search for a patch.avaya.com and see the latest Release Notes for information about the latest patches. 6.1 February 2011 53 . If you selected HTTP. Downloading patches 1. 2. You can install or download the patches from the Avaya Product Licensing and Delivery System (PLDS) Web site at http://plds. 3. Implementing Application Enablement Services on System Platform R6.avaya. and manage the regular updates and patches for System Platform and the various templates provided by Avaya. Click Server Management > Patch Management . On the Search Local and Remote Patch page. 5. If you selected HTTP or SP Server. click Configure Proxy to specify a proxy server if required. Click Download/Upload. specify the Patch URL. If you selected Local File System. Options are: • Avaya Downloads (PLDS) • HTTP • SP Server • SP CD/DVD • SP USB Disk • Local File System 4.

Related topics: Configuring a proxy on page 54 Search Local and Remote Patch field descriptions on page 55 Configuring a proxy If the patches are located in a different server (for example. Enable or disable statistics collection. click Configure Proxy. make sure that all applications (virtual machines) are fully installed and running. Click Save to save the settings and configure the proxy. Choose the patch and click Select. 9. 4. 8. 6. you may need to configure a proxy depending on your network. Specify the proxy port. Select the appropriate keyboard layout. 5. 54 Implementing Application Enablement Services on System Platform R6. 2.1 February 2011 . On the System Configuration page. Avaya PLDS or HTTP). Specify the proxy address. Click Server Management > Patch Management. 8.Installing patches 7. Click Search to search for the required patch. 7. select Enabled for the Proxy Status field. 1. On the Search Local and Remote Patch page. Related topics: Downloading patches on page 53 Search Local and Remote Patch field descriptions on page 55 Installing patches Prerequisites If installing a service pack as part of an installation. 3. Click Upload/Download.

1. For example.tar.jar.*.bz.*. *.tar. you may encounter some errors. click Install.Search Local and Remote Patch field descriptions Use this task to install all service packs and other patches (that is. You may hold the mouse pointer over the selection to view more information about the “sold-to” number. 3.patch. Each line in the list begins with the “soldto” number to allow you to select the appropriate template for the site where you are installing. Make sure that you do not use the patch installers provided by your solution templates. 2.zip. You must enter an Avaya SSO login and password. System Platform and solution template patches) through System Platform Web Console. as System Domain Implementing Application Enablement Services on System Platform R6. You must specify the Patch URL for the server.bz. Displays the available location options for searching a patch. Name Supported Patch File Extensions Choose Media Description The patch that you are installing should match the extensions in this list.*.tar. Tip: When you want to move files from your laptop to the System Platform Server. Click Manage.gz. The list will contain all the templates to which your company is entitled. click on a patch ID to see the details. The Patch List page displays the list of patches and the current status of the patches. On the Patch Detail page.rpm.*. Related topics: Patch List field descriptions on page 56 Patch Detail field descriptions on page 57 Search Local and Remote Patch field descriptions Use the Search Local and Remote Patch page to search for available patches and to upload or download a patch.gz.*. On the Patch List page. 4. Click Server Management > Patch Management . • SP Server: Files are located in the vsp-template file system in the System Platform server. You must specify the Patch URL for the server. • HTTP: Files are located in a different server.*. Options are: • Avaya Downloads (PLDS): The template files are located in the Avaya Product Licensing and Delivery System (PLDS) Web site.*.*.1 February 2011 55 .

you may be required to configure a proxy depending on your network. • SP USB Disk: Files are located in a USB flash drive. Name System Platform Description Lists the patches available for System Platform under this heading. URL of the server where the patch files are located. but most laptops do not come with SCP support. You can download the following two programs to enable SCP (Search the Internet for detailed procedures to download them): . • Local File System: Files are located in a local computer. Downloads a patch file. 56 Implementing Application Enablement Services on System Platform R6. Appears when Local File System is selected and uploads a patch file from the local file system. If the patches are located in a different server. Button descriptions Button Search Configure Proxy Description Searches for the available patches in the media location you specify.Installing patches Name Description (Domain-0) and Console Domain support only SCP.exe . Patch URL Active only when you select HTTP or SP Server as the media location. Add Upload Download Related topics: Downloading patches on page 53 Configuring a proxy on page 54 Patch List field descriptions The Patch List page displays the patches on the System Platform server for installing or removing. Opens the System Configuration page and lets you configure a proxy based on your specifications.1 February 2011 . Active only when you select HTTP as the media location option.Pscp. Use this page to view the details of patch file by clicking on the file name.WinSCP • SP CD/DVD: Files are located in a System Platform CD or DVD. Appears when Local File System is selected and adds a patch file to the local file system.

Console Domain (cdom patch). Service effecting when Shows the action (if any) that causes the selected patch to restart the System Platform Web Console. Not Installed. if the patch is available for System Platform the description is shown as SP patch. Name of the virtual machine. Service Effecting Button descriptions Button Refresh Description Refreshes the patch list. Use this page to view details of a patch or to install or remove a patch. Shows if the patch file has any dependency on any other file.1 February 2011 57 . Shows the status of a patch. Patch ID Description Status File name of a patch. Active.Patch Detail field descriptions Name Description Solution Template Lists the patches available for the respective solution templates under respective solution template headings. Implementing Application Enablement Services on System Platform R6. Disable sanity when Shows at what stage the sanity is set to disable. For example. Information of a patch. and Not Activated. Related topics: Installing patches on page 54 Patch Detail field descriptions The Patch Detail page provides detailed information about a patch. Shows if installing the patch causes the respective virtual machine to reboot. for example. Possible values of Status are Installed. Virtual machine name for which the patch is applicable. Shows the software load for which the patch is applicable. Version of the patch file. Name ID Version Product ID Description Detail Dependency Applicable for Description File name of the patch file. Virtual machine name for which the patch is applicable.

Installs the respective patch. On removing the patch file. Removes the respective patch. Deactivates the installed patch of a solution template. Shows the URL for the patch file. Button descriptions Button Refresh Patch List Install Activate Deactivate Remove Description Refreshes the Patch Details page. Related topics: Installing patches on page 54 58 Implementing Application Enablement Services on System Platform R6. that displays the list of patches. Opens the Patch List page. Remove Patch File Removes the respective patch file. The button appears only if the patch file is still present in the system.1 February 2011 . the button does not appear. Activates the installed patch of a solution template.Installing patches Name Status Patch File Description Shows if the patch is available for installing or already installed.

However.1 February 2011 59 . then running on the preferred node offers no increased benefit. Note: System Platform High Availability Failover does not support IPv6 and cannot be configured with IPv6 addresses. The preferred node has a small score benefit. The node from which you configure High Availability Failover is designated the preferred node. So if both machines are booted at the same time. Implementing Application Enablement Services on System Platform R6.Chapter 6: System Platform High Availability Failover High Availability Failover overview The System Platform High Availability Failover is an optional feature aimed at providing service continuity. it does not support critical reliability. No auto-failback High Availability Failover does not use auto-failback to migrate resources back to the preferred node when the resources are running on the standby node and the preferred node becomes available again. the currently active node becomes the preferred node. not running or blocked). If you want to migrate resources back to the preferred node after a failover or a switchover. Note that System Platform does not provide any Web interface to modify this interval. The System Platform High Availability Failover feature offers the following capabilities: Node scores High Availability Failover uses node scores to compute the ability of each machine to run the resources and determine which node runs the resources. the preferred node will run resources. both machines have the same score. certain solution templates (Communication Manager is one such template) do not support this feature. and resources could run on either node. Moreover. Expected failover/switchover times High Availability Failover uses 30 seconds as a timeout interval after which the standby node will declare the active node dead and start resources (even though the active node may be not accessible. and if both servers are healthy. If you stop High Availability Failover. If the system has no issues. Thus System Platform uses the term “preferred node” for the machine that should run the resources when the system has no issues. Switching servers disrupts service. you can do so by using the Manual Switchover option in the Failover menu at the most suitable time.

The servers must be connected on the same ports on both machines. Note: The switchover time is approximate and varies depending on the hardware running System Platform with no templates. • The same version of System Platform must be installed on the active and standby nodes.1 February 2011 . • Start of resources–Up to 5 minutes. number of processors. • Both the servers must be in the same subnet. Therefore.5 minutes. you will not be able to start High Availability Failover. • Start of resources–Up to 5 minutes. • Both servers must be in close proximity so that they can be connected with the crossover cable. • The system shutdown was not proper.System Platform High Availability Failover For manual switchover or when the system initiates a preemptive failover. If you do so. the total time between the start of the outage and the time when all resources are running on the standby node includes a detection interval timeout and the start of all resources: • Detect active node failure–30 seconds. the total time between the start of the command and activating the standby node includes a graceful shutdown and restart of all resources: • Stop of resources– Up to 5 minutes. The standby server cannot have less memory. For failover due to total failure of the active node. Requirements for High Availability Failover The requirements for High Availability Failover are as follows: • Two servers with exactly the same hardware configuration. • Do not install a template on the standby node. total disk space or free disk space than the primary server. • Resulting longest switchover time–Up to 5. the system performs an FSCK (File System Check) as it boots up and starts the virtual machines. If you are using a bundled System Platform installation (with a solution template). The Ethernet specification limit for this distance is 100 meters. • Resulting longest switchover time–Up to 10 minutes. The solution 60 Implementing Application Enablement Services on System Platform R6. disable the template installation on the standby server. • The servers must have a spare Gigabit network interface to be dedicated exclusively to High Availability Failover services. The switchover is further delayed by the following factors: • The system runs complex templates. • The hardware must be supported by System Platform.

Prerequisites for configuring High Availability Failover

template is propagated from the active node to the standby node when you start High Availability Failover.

Prerequisites for configuring High Availability Failover
The prerequisites for configuring High Availability Failover are as follows: • Connect both the servers with a Gigabit-certified Ethernet cable on the same ports on both machines. • Ensure that your network gateway replies to ICMP requests from the System Platform nodes. The default network gateway is the ping target of the High Availability Failover heartbeat. This target cannot be configured differently.

Configuring High Availability Failover
You must have a user role of Advanced Administrator to perform this task.

1. Log in to the Web Console of the server that you want to be the preferred node. 2. Click Server Management > Failover to display the Failover page. The Failover page displays the current status of High Availability Failover. 3. Click Configure Failover. 4. On the Configure failover page, enter the appropriate information to configure High Availability Failover. 5. Click Create. 6. After the system completes creation of the High Availability Failover configuration, click Start Failover Mode and confirm the warning that is displayed. System Platform Web Console redirects to the Reboot page and after a few minutes redirects to the Login page. 7. Log in to the System Platform Web Console. 8. Click Server Management > Failover. You can check the status of the failover components on the Failover page and ensure that Distributed Replicated Block Device (DRBD) is synchronizing the hard disks of the two servers. Tip: During the disk synchronization process, you can increase or decrease the speed of the synchronization with a slider bar on the console. The default value of this

Implementing Application Enablement Services on System Platform R6.1

February 2011

61

System Platform High Availability Failover

rate is 30 MB/s. If you set the value too high, it may affect the performance of the virtual machines running on the active server.

Configure Failover field descriptions
Name Remote cdom IP address Remote cdom user name Remote cdom password Primary network interface Crossover network interface Description IP Address of Console Domain on the standby node. User name for Console Domain on the standby node. Password for Console Domain on the standby node. Network interface connected to the customer network. Network interface connected to the standby server.

62

Implementing Application Enablement Services on System Platform R6.1

February 2011

Chapter 7: Installing Application Enablement Services

Prerequisites for installing the AES template
• Stop High Availability Failover if it is running. You cannot install the AES template if High Availability Failover is running. • Make sure that the IP addresses for the avprivate bridge do not conflict with any other IP addresses in your network. Go to the Network Configuration page on the System Platform Web Console (Server Management > Network Configuration) to view the addresses that are allocated to avprivate. The range of IP addresses starts with System Domain's (Domain-0) interface on avprivate. Console Domain automatically receives the consecutive IP address. If any conflicts exist, resolve them by assigning System Domain an IP address on a subnet that you know is not used in your network. Keep in mind that the template you install may take additional addresses on the private bridge. The avprivate bridge is an internal, private bridge that allows virtual machines to communicate with each other. This private bridge does not have any connection to your LAN. During installation, System Platform runs an algorithm to find a set of IP addresses that do not conflict with the addresses configured on the System Domain Network Configuration page. However, it is still possible that the addresses selected conflict with other addresses in your network. Since this private bridge is not connected to your LAN, this address conflict could result in the failure of System Platform or an installed template to route packets correctly.

Installing Application Enablement Services template
1. On a Web browser, type the following URL: https://ipaddress/ webconsole, where ipaddress is the IP address of the Console Domain that you configured during installation of System Platform.

Implementing Application Enablement Services on System Platform R6.1

February 2011

63

On the Select EPW File page. Click Search to display a list of template descriptor files (each available template has one template descriptor file). Once pop-ups are allowed. In the User ID box. 10.Installing Application Enablement Services Note: This is a secure site. Note: Make sure the web browser is set to temporarily allow pop-ups. 2. click the AES template. • If you have not completed the AE Services Electronic Pre-installation Worksheet (EPW). 64 Implementing Application Enablement Services on System Platform R6. then follow the instructions in your browser to install a valid certificate on your computer. Click Browse EPW File. 7. enter admin. On the Select Template page. 11. iii. Click Upload EPW file. The system displays the Template Details page with information on the AES template and its Virtual Appliances. do one of the following: • If you have completed the AE Services Electronic Pre-installation Worksheet (EPW). Enter the password for this account. 9. you may be required to configure a proxy depending on your network. The Template Installation page shows the status of the installation. Avaya PLDS or HTTP). The system displays the Template Details page with information on the AES template and its Virtual Appliances. Click Virtual Machine Management > Solution Template.1 February 2011 . and click Open. click Continue without EPW file. 8. 5. If you get a certificate error. select a location from the list in the Install Template From box. 4. select the EPW file. Click Log On. From the Choose File to Upload dialog box. ii. Click Continue. the Network Settings page appears. On the Search Local and Remote Template page. and then click Select. 3. Click Install. 6. Note: If the template installation files are located on a different server (for example. do the following: i.

Available options are as follows: Avaya Downloads (PLDS) The template files are located in the Avaya Product Licensing and Delivery System (PLDS) Web site. You can log out. 19.Search Local and Remote Template field descriptions 12. the message "Template Installation Completed Successfully" appears. On the Confirm Installation page. click Previous Step. The Template Installation page shows the status of the installation. to upgrade an installed template. When the installation is complete. the default password will be used.1 February 2011 65 . click Next Step. 20. click Accept. Re-enter the root login password in the Re-type password box. Name Install Template From Description Locations from which you can select a template and install it on System Platform. Re-enter the cust login password in the Re-type password box. or to delete an installed template. 14. The list will contain all the templates to which your company is Implementing Application Enablement Services on System Platform R6. If you need to make any changes. 17. enter the following network settings • ETH0 IP address of the AES • ETH1 IP address of the AES (optional) • ETH1 network mask (optional) • AES hostname 13. verify the information displayed. Click Install. If you do not enter the password. Click Next Step. When you are finished. You must enter an Avaya SSO login and password. 16. 15. enter the password for the root login in the Password box (optional). enter the AES Alarm ID and click Next Step. On the Alarming page. On the Network Settings page. On the Summary page. Enter the password for the cust login in the Password box (optional). On the Customer Login page. Click Next Step. 22. the default password will be used. Search Local and Remote Template field descriptions Use the Search Local and Remote Template page to select the template that you want to install on System Platform. If you do not enter the password. 21. 18.

1 February 2011 . This button is displayed only if a template is installed on System Platform. Lets you configure a proxy for the HTTP address. Each line in the list begins with the “sold-to” number to allow you to select the appropriate template for the site where you are installing. Upgrade Delete Installed Deletes the currently installed and active template. A proxy may also be required for Secure Access Link (SAL) and alarming to access the internet.Installing Application Enablement Services Name Description entitled. HTTP The template files are located on an HTTP server. SP Server The template files are located in the /vsp-template file system in the Console Domain of the System Platform server. You may hold the mouse pointer over the selection to view more information about the “sold-to” number. This button is Template displayed only if a template is installed on System Platform. 66 Implementing Application Enablement Services on System Platform R6. Upgrades the installed solution template from the selected template location option. SP USB Disk The template files are located on a USB flash drive connected to the server. SSO Password Search Local and Remote Template button descriptions Name Install Configure Proxy Description Installs the solution template. Active only when you select the Avaya Downloads (PLDS) option to search for a template. Login id for logging on to Single Sign On. You must enter the template URL information. SSO Login Active only when you select the Avaya Downloads (PLDS) option to search for a template. This button is displayed only if no template is currently installed on System Platform. SP CD/DVD The template files are located on a CD or DVD in the CD/DVD drive on the server. Password for Single Sign On. Active only when you select the HTTP option to search for a solution template.

Stand-alone SAL Gateway You can choose to use a stand-alone SAL Gateway instead of the SAL Gateway that is embedded in System Platform. System Platform includes an embedded SAL Gateway. The stand-alone gateway makes it possible to consolidate alarms from many Avaya devices and send those alarms from one SAL Gateway rather than multiple SAL Gateways sending alarms. B2B VPN connection) to deliver remote services. potentially eliminating the need for a service technician to visit the customer site. SAL Gateway can also forward alarms to the customer's Network Management System (NMS) if configured to do so. System Platform uses the customer’s existing Internet connectivity to facilitate remote support. Avaya support will be delayed or not possible if SAL is improperly implemented or not operational. Business Partners without a SAL Core Concentrator Server must provide their own IP-based connectivity (for example. System Platform and SAL do not support modem connections. Implementing Application Enablement Services on System Platform R6.Chapter 8: Administering SAL on System Platform SAL Gateway Secure Access Link (SAL) Gateway provides Avaya support engineers and Avaya Partners with alarming and remote access to the applications on System Platform. System Platform can be serviced remotely. Note: Avaya Partners and customers must ensure that SAL is always configured and registered with Avaya during System Platform installation. All communication is outbound from the customer’s environment using encapsulated Hypertext Transfer Protocol Secure (HTTPS). SAL requires upload bandwidth (customer to Avaya or Avaya Partner) of at least 90 KB/s with latency no greater than 150 ms (round trip).com for more information on stand-alone SAL Gateway. The SAL Gateway application on System Platform receives alarms from applications in the solution template and forwards them to Secure Access Core Concentrator Servers at Avaya and applicable Avaya Partners.1 February 2011 67 .avaya. You might prefer a stand-alone gateway if you have a large network with many Avaya devices. The SAL gateway application also polls designated service providers for connection requests. SAL Gateway software is also available separately for stand-alone deployments. Remote Serviceability System Platform utilizes SAL as Avaya’s exclusive method for remote delivery of services. See Secure Access Link on http:// support.

perform these high-level steps: 1. and other products that are included in the solution template that is installed. See Disabling SAL Gateway on page 78. In the context of System Platform. You can also disable the SAL Gateway that is embedded in System Platform so that it does not send duplicate heart beat messages to Avaya. managed devices are the components of System Platform and of the applications that are included in the solution template. logging information. You must submit the Universal Install/SAL Registration Request form to obtain from Avaya the information that you must enter in SAL Gateway. Avaya assigns a Solution Element ID (SE ID) and Product ID to each SAL Gateway and managed device that is registered. 68 Implementing Application Enablement Services on System Platform R6. and configuration interfaces. configure the SAL Gateway only on the primary server. You must configure the SAL Gateway and other devices for alarming and remote access. you must start the registration process and receive product registration information from Avaya.1 February 2011 . Register the system. This data is critical for correct execution of various Avaya business functions and tools. The Product ID is included in alarms that are sent to alarm receivers from the managed device. virtual machines might include Communication Manager. and other applications that are included in the template. The SE ID makes it possible for Avaya Services or Avaya Partners to connect to the managed applications remotely.Administering SAL on System Platform If you use a stand-alone SAL Gateway. Configure the SAL Gateway. SAL Gateway configuration The SAL Gateway includes a Web-based user interface that provides status information. you must add it as an SNMP trap receiver for System Platform. The Product ID identifies the device that generated the alarm. 2. Note: On High Availability Failover systems. See Adding an SNMP trap receiver on page 78. SIP Enablement Services. SAL Gateway will propagate to the standby server. For example. and verifies certificates for authentication. The SAL Gateway provides remote access to those devices that are configured for remote access within it. Console Domain (cdom). Communication Manager Messaging. The devices include System Platform’s System Domain (dom 0). When you enable High Availability Failover. Related topics: Registering the system Configuration prerequisites Before configuring the SAL Gateway. It controls connections to managed elements. To configure SAL. new or updated models.

click Server Management > SNMP Trap Receiver Configuration. When you install System Platform.avaya. This form is available at http://support. This data is critical for correct execution of various Avaya business functions and tools.Changing the Product ID for System Platform To register a product. 2. The Product ID identifies the device that generated the alarm. click Universal Install/SAL Product Registration Request Form. 3. Implementing Application Enablement Services on System Platform R6. Note: Submit the registration form three weeks before the planned installation date. Open the Microsoft Excel form with macros enabled. The Product ID is included in alarms that System Platform sends to alarm receivers.com. 1. click More Resources > Equipment Registration. or search Universal Install/SAL Product Registration Request Form. delete the ID that is displayed in the Product ID field and enter the unique Product ID for System Platform Console Domain. Under Non-Regional (Product) Specific Documentation. Related topics: Registering the system Changing the Product ID for System Platform Prerequisites You must have registered the system and obtained a Product ID for System Platform from Avaya.1 February 2011 69 . On the SNMP Trap Receiver Configuration page. The form includes complete instructions. Click Save. In the navigation pane. download and complete the Universal Install/SAL Registration Request form and submit the form to Avaya. In the navigation pane of the System Platform Web Console. Note: VSPU is the model name for Console Domain. a default Product ID of 100111999 is set. You must change this default ID to the unique Product ID that Avaya provides.

5 System requirements: A computer with access to the System Platform network. Log in to the System Platform Web Console. Users that have an administrator role can only view configuration of the SAL Gateway.x and 7. enter the same user ID and password that you used for the System Platform Web Console. On the SAL Gateway Management page. To configure SAL Gateway. 2.x • Firefox 3. the system displays two messages at the top of the page: • SAL Agent is running • Remote Access Agent is running 70 Implementing Application Enablement Services on System Platform R6. 3. When you are successfully logged in. In the navigation pane of the System Platform Web Console . When the SAL Gateway displays its Log on page.Administering SAL on System Platform System and browser requirements for accessing the SAL Gateway user interface Browser requirements for SAL Gateway: • Internet Explorer 6. click Launch SAL Gateway Management Portal. click Server Management > SAL Gateway Management. 4. the Managed Element page of the SAL Gateway user interface is displayed.1 February 2011 . Starting the SAL Gateway user interface 1. If the SAL Gateway is up and running. you must log in as admin or another user that has an advanced administrator role.

In the navigation pane of the SAL Gateway user interface. The changes take effect after you apply configuration changes on the Apply Configuration Changes page. 4.1 February 2011 71 . click Undo Edit. This information is required for the SAL Gateway to communicate with the Secure Access Concentrator Core Server (SACCS) and Secure Access Concentrator Remote Server (SACRS) at Avaya.8 Implementation Guide for more information. If you want to cancel your changes. The system restores the configuration before you clicked the Edit button. click Edit. complete the following fields: • Gateway IP Address • Solution Element ID • Gateway Alarm ID • Alarm Enabled For field descriptions. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway. To minimize disruption of services and alarms. On the Gateway Configuration page. see Gateway Configuration field descriptions on page 79. On the Gateway Configuration (edit) page.com. 1. 6. Note: The configuration changes do not take effect immediately. Click Apply. Implementing Application Enablement Services on System Platform R6. This document is available at http://support.avaya. (Optional) Complete the following fields if the template supports inventory collection: • Inventory Collection • Inventory collection schedule 5. 3. you must apply configuration changes for the configuration to take effect. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway.Configuring the SAL Gateway Configuring the SAL Gateway Use this procedure to configure the identity of the SAL Gateway. See the Secure Access Link Gateway 1. click Administration > Gateway Configuration. 2. Next steps After completing configuration of SAL Gateway.

2. Next steps After completing configuration of SAL Gateway. This document is available at http://support. you can use the Test button to test connectivity to the proxy server. (Optional) Once you complete configuration of SAL Gateway. To minimize disruption of services and alarms. complete the following fields: • Use Proxy • Proxy Type • Host • Port 3. See the Secure Access Link Gateway 1.com.8 Implementation Guide for more information. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway. On the Proxy Server page.Administering SAL on System Platform Related topics: Applying configuration changes on page 76 Gateway Configuration field descriptions on page 79 Configuring a proxy server Use the Proxy Server page to configure proxy settings if required for SAL Gateway to communicate with the Secure Access Concentrator Remote Server and the Secure Access Concentrator Core Server. 4. Click Apply. In the navigation pane of the SAL Gateway user interface. click Administration > Proxy.avaya.1 February 2011 . 1. you must apply configuration changes for the configuration to take effect. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway. Related topics: Applying configuration changes on page 76 Proxy server field descriptions on page 80 72 Implementing Application Enablement Services on System Platform R6.

Do not change the default settings on this page. To minimize disruption of services and alarms.Configuring SAL Gateway communication with a Secure Access Concentrator Core Server Configuring SAL Gateway communication with a Secure Access Concentrator Core Server Use the SAL Enterprise page to review settings for communication between SAL Gateway and a Secure Access Concentrator Core Server (SACCS) at Avaya Data Center. (Optional) Once you complete configuration of SAL Gateway. The SAL Enterprise page is displayed. you must apply configuration changes for the configuration to take effect. you can use the Test button to test connectivity to the defined Secure Access Concentrator Core Servers. 3. Do not change the default settings unless you are explicitly instructed to do so.com. This document is available at http://support. Related topics: Applying configuration changes on page 76 SAL Enterprise field descriptions on page 80 Implementing Application Enablement Services on System Platform R6. See the Secure Access Link Gateway 1.8 Implementation Guide for more information.avaya. 1. Next steps After completing configuration of SAL Gateway. click Administration > SAL Enterprise.avaya.1 February 2011 73 . This document is available at http://support. The SACCS handles alarming and inventory.com.8 Implementation Guide for more information. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway. The system does not connect to the new Secure Access Concentrator Core Server until you restart the SAL Gateway. See the Secure Access Link Gateway 1. 2. In the navigation pane of the SAL Gateway user interface.

Do not change the default settings on this page unless you are explicitly instructed to do so. the system terminates all active connections.Administering SAL on System Platform Configuring SAL Gateway communication with a Secure Access Concentrator Remote Server Use the Remote Access page to review settings for communication between SAL Gateway and a Secure Access Concentrator Remote Server (SACRS) at Avaya Data Center. 1. In the navigation pane of the SAL Gateway user interface. The SACRS handles remote access. click Administration > Remote Access.com. When you restart the SAL Gateway. The system does not connect to the new Secure Access Concentrator Remote Servers until you restart the SAL Gateway. Next steps After completing configuration of SAL Gateway. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway. Do not change the default settings unless you are explicitly instructed to do so. See the Secure Access Link Gateway 1. Related topics: Applying configuration changes on page 76 Remote Access field descriptions on page 81 74 Implementing Application Enablement Services on System Platform R6. you must apply configuration changes for the configuration to take effect. 3. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway. you can use the Test button to test connectivity to the defined Secure Access Concentrator Remote Servers.1 February 2011 . The Remote Access page is displayed. and updates models and configuration. 2. This document is available at http://support.avaya. To minimize disruption of services and alarms.8 Implementation Guide for more information. (Optional) Once you complete configuration of SAL Gateway.

Related topics: Applying configuration changes on page 76 Network Management Systems field descriptions on page 81 Managing service control Use this procedure to view the status of a service. To minimize disruption of services and alarms.8 Implementation Guide for more information.com. This document is available at http://support. Implementing Application Enablement Services on System Platform R6. the SAL Gateway copies traps and alarms (encapsulated in traps) to each NMS that you configure. 2. or test a service that the SAL Gateway manages. In the navigation pane of the SAL Gateway user interface.Configuring NMS Configuring NMS Use this procedure to specify SNMP trap destinations. 1. stop a service. you must apply configuration changes for the configuration to take effect.avaya. Click Apply. 4. (Optional) Use the Add button to add multiple NMSs. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway. See the Secure Access Link Gateway 1.1 February 2011 75 . Next steps After completing configuration of SAL Gateway. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway. When you configure Network Management Systems (NMSs). click Administration > NMS. complete the following fields: • NMS Host Name/ IP Address • Trap port • Community 3. On the Network Management Systems page.

76 Implementing Application Enablement Services on System Platform R6. Click the Apply next to Configuration Changes.8 Implementation Guide for more information. Click one of the following buttons: • Stop to stop a service. • Start to start a service that is stopped. • Test to send a test alarm to the Secure Access Concentrator Core Server. In the navigation pane of the SAL Gateway user interface. This document is available at http://support. In the navigation pane of the SAL Gateway user interface. 2. The page lists the following services: • Inventory • Alarming • Remote Access • Health Monitor The Gateway Service Control page also displays the status of each service as: • Stopped • Running 2. the system restarts the SAL Gateway and updates the Gateway with the new values you configured.1 February 2011 . When you click Apply.avaya. See the Secure Access Link Gateway 1. The system displays the Gateway Service Control page. Applying configuration changes 1.com. Doing so will block you from accessing SAL Gateway remotely. Important: Use caution if stopping the Remote Access service. click Administration > Apply Configuration. The system displays the Apply Configuration Changes page. click Administration > Service Control.Administering SAL on System Platform 1.

On the Managed Element page. 2. Adding a managed element Prerequisites Complete the Managed Element Worksheet for SAL Gateway. 3. click Secure Access Link Gateway > Managed Element. Next steps After completing configuration of SAL Gateway. In the navigation pane of the SAL Gateway user interface. click Add new. 4. Click Add. To minimize disruption of services and alarms. See Managed element worksheet for SAL Gateway. you must apply configuration changes for the configuration to take effect. This task is performed on the Apply Configuration Changes page and restarts the SAL Gateway.Adding a managed element The SAL Gateway misses any alarms that are sent while it restarts. Perform this procedure for each Solution Element ID (SE ID) that is provided in the registration information from Avaya. Complete the fields on the page as appropriate. Avaya recommends that you apply configuration changes only after you finish configuration of SAL Gateway. 1. 5. Click Apply to apply the changes.1 February 2011 77 . Related topics: Applying configuration changes on page 76 Managed Element field descriptions on page 82 Implementing Application Enablement Services on System Platform R6.

Disable the embedded SAL Gateway if you are using a stand-alone SAL Gateway to send alarms to Avaya.1 February 2011 . In the navigation pane of the System Platform Web Console.Administering SAL on System Platform Using a stand-alone SAL Gateway Adding an SNMP trap receiver Use this procedure to add an SNMP trap receiver for System Platform. On the SNMP Trap Receiver Configuration page. In the navigation pane of the System Platform Web Console . 2. If you are using a standalone SAL Gateway. Click Add SNMP Trap Receiver. click Server Management > SNMP Trap Receiver Configuration. you must add it as an SNMP trap receiver. Disabling SAL Gateway Use this procedure to disable the SAL Gateway that is embedded in System Platform. 2. 78 Implementing Application Enablement Services on System Platform R6. 1. On the SAL Gateway Management page. click Server Management > SAL Gateway Management. complete the following fields: • IP Address • Port • Community 3. click Disable SAL Gateway. 1.

Enables inventory collection for the SAL Gateway.8 Implementation Guide.avaya.com Interval in hours at which you want inventory collected. Gateway Alarm ID Alarm Enabled Inventory Collection Inventory collection schedule Implementing Application Enablement Services on System Platform R6. This check box must be selected for the SAL Gateway to send alarms. SAL Gateway collects inventory information about the supported managed devices and sends it to the Secure Access Concentrator Core Server for Avaya reference.Field descriptions Field descriptions Gateway Configuration field descriptions Name Gateway Hostname Description A host name for the SAL Gateway. This ID should start with a 5 and include ten digits. The system uses the value in the Gateway Alarm ID field to uniquely identify the source of Gateway alarms in the Secure Access Concentrator Core Server. When this check box is selected. This feature is intended for services personnel who are working on tickets and want to review the configuration of managed devices. Format is (000)123-4567. If you have not obtained Solution Element IDs for the system. For more information on this feature. The Product ID (also called Alarm ID) for the SAL Gateway. Enables the alarming component of the SAL Gateway. This document is available at http:// support. start the registration process as described in Registering the system. see the Secure Access Link Gateway 1. Warning: Do not edit this field as the SAL Gateway inherits the same hostname as the CentOS operating system that hosts both the System Platform Web Console and the SAL Gateway. This IP address is the same as that of cdom (also called VSPU).1 February 2011 79 . The system uses the SAL Gateway Solution Element ID to authenticate the SAL Gateway and its devices with the Secure Access Concentrator Remote Server. Gateway IP Address Solution Element ID The IP address of the SAL Gateway. The Solution Element ID that uniquely identifies the SAL Gateway.

alarming. IP Address or the host name of the primary Secure Access Concentrator Core Server.avaya. Login if authentication is required. The default value is secure. Port number of the primary Secure Access Concentrator Core Server. Options are: • SOCKS 5 • HTTP Host Port Login The IP address or the host name of the proxy server. Primary Enterprise Port 80 Implementing Application Enablement Services on System Platform R6. Important: SAL Gateway in System Platform does not support authenticating proxy servers. Password Password for login if authentication is required. Do not change the default unless you are explicitly instructed to do so. Related topics: Configuring a proxy server on page 72 SAL Enterprise field descriptions Name Passphrase Description Default passphrase is Enterprise-production. Proxy Type Type of proxy server that is used. The port number of the Proxy server.1 February 2011 .com. Important: SAL Gateway in System Platform does not support authenticating proxy servers. This passphrase is used to establish a channel for communication between the SAL Gateway and the Secure Access Concentrator Core Server.Administering SAL on System Platform Related topics: Configuring the SAL Gateway on page 71 Proxy server field descriptions Name Use Proxy Description Check box to enable use of a proxy server.

The default value is sl1. The port number of the NMS server.avaya. This value must match the value in the Port field for the primary server.1 February 2011 81 . This value must match the value in the Primary Server Host Name / IP Address field. Secondary Enterprise Port This value must match the value in the Primary Enterprise field. Port The port number of the primary Secure Access Concentrator Remote Server. Secondary Server Host Name / IP address Port Related topics: Configuring SAL Gateway communication with a Secure Access Concentrator Remote Server on page 74 Network Management Systems field descriptions Name NMS Host Name/ IP Address Trap port Community Description The IP address or host name of the NMS server. Related topics: Configuring SAL Gateway communication with a Secure Access Concentrator Core Server on page 73 Remote Access field descriptions Name Description Primary Server Host The IP address or host name of the primary Secure Access Name / IP Address Concentrator Remote Server.sal. Implementing Application Enablement Services on System Platform R6.com. The community string of the NMS server. The default value is 443.Field descriptions Name Description The default value is 443. This value must match the value in the Port field for the primary server.

8 Implementation Guide. This document is available at http:// support.avaya.com 82 Implementing Application Enablement Services on System Platform R6. Check box to allow remote connectivity to the managed device. The Product ID identifies the device that generated the alarm. SAL Gateway collects inventory information about the managed device and sends it to the Secure Access Concentrator Core Server for Avaya reference. Not applicable for applications that are installed on System Platform. This feature is intended for services personnel who are working on tickets and want to review the configuration of managed devices.Administering SAL on System Platform Name Description Use public as the Community. The Product ID (also called Alarm ID). Related topics: Configuring NMS on page 75 Managed Element field descriptions Name Host Name Description Host name for the managed device. as SAL agents support only public as community at present. For more information on this feature. Leave this field clear (not selected).1 February 2011 . IP Address NIU Model Solution Element ID Product ID Provide Remote Access to this device Transport alarms from this device Collect Inventory for this device (Optional) Check box to enable alarms from this device to be sent to the Secure Access Concentrator Core Server. IP address of the managed device. Check box to enable inventory collection for the managed device. The Solution Element ID (SE ID) of the device. The model that is applicable for the managed device. see the Secure Access Link Gateway 1. The Product ID is included in alarms that are sent to alarm receivers from the managed device. When this check box is selected. This must match the host name on the Network Configuration page of the System Platform Web Console (Server Management > Network Configuration in the navigation pane). The SE ID makes it possible for Avaya Services or Avaya Partners to connect to the managed applications remotely.

Field descriptions Name Inventory collection schedule Description Interval in hours at which you want inventory collected from the managed device. SAL Gateway uses heartbeats to monitor health. Check box to suspend health monitoring for the managed device. Related topics: Adding a managed element on page 77 Implementing Application Enablement Services on System Platform R6. SAL Gateway starts monitoring heartbeats from the device after the restart and generates alarms if it does not receive a heartbeat within the configured interval.1 February 2011 83 . You must restart the SAL Gateway for the configuration changes to take effect. SAL Gateway resumes monitoring the device after the configured time elapses. Suspend health monitoring for this device Suspend for Number of minutes for which you want health monitoring suspended for the managed device. Heartbeats must be configured on the device. Monitor health for Check box to enable health monitoring of the managed device by SAL this device Gateway. Generate Health Status missed alarm every Interval in minutes at which SAL Gateway generates an alarm if it does not receive a heartbeat from the managed device.

Administering SAL on System Platform

84

Implementing Application Enablement Services on System Platform R6.1

February 2011

Chapter 9:

Upgrading System Platform

Platform upgrade
Use the Platform Upgrade option to upgrade Avaya Aura® System Platform software for one or all of the following: • System Domain (Domain-0) • Console Domain Note: Before proceeding with the System Platform upgrade, check the relevant template documentation to ensure that the template is qualified for the System Platform version to which you want to upgrade. Also check for any System Platform patches that are required. If System Platform High Availability is enabled and you are upgrading System Domain (Domain-0) and Console Domain, you must stop High Availability before performing the upgrade. Upgrade each server separately before restarting High Availability. See Methods for upgrading High Availability systems on page 91. Caution: To minimize service disruption, perform platform upgrades during a planned maintenance window. The upgrade procedure is service affecting and includes a reboot of the entire system. The platform upgrade software is distributed as an ISO file (the file type in which System Platform software is distributed for new installations) or platform upgrade files. If you are using the ISO file, you can copy it to a CD or DVD and use the SP CD/DVD option to upgrade. Alternately, you can decompress the ISO file and copy the decompressed contents to a USB drive. You can use the SP USB Disk option to upgrade. If you are using the platform upgrade files to install, you can use any of the available options: Avaya Downloads (PLDS), HTTP, SP Server, SP CD/DVD, or SP USB Disk. Note: On Windows, use WinZip release 12 or higher to decompress the ISO file.

Implementing Application Enablement Services on System Platform R6.1

February 2011

85

Upgrading System Platform

Upgrading System Platform
1. Log in to System Platform Web Console. 2. Click Server Management > Platform Upgrade. 3. In the Upgrade Platform From field, select a location from where to download the System Platform image files for the platform upgrade. Options are: • Avaya Downloads (PLDS) • HTTP • SP Server • SP CD/DVD • SP USB Device 4. If you selected HTTP or SP Server in the Upgrade Platform From field, enter the platform upgrade URL. 5. Click Search. The system searches for an upgrade description file that has an .ovf extension. 6. Select the appropriate description file for the platform upgrade, and then click Select. The system displays the version and additional information for the current and the new platform (System Domain (Domain-0) or Console Domain, or both) on the Platform Upgrade Details page. 7. On the Platform Upgrade Details page, click Upgrade. Important: As part of the upgrade process, the System Domain (Domain-0) and Console Domain are rebooted, and as a result, all other virtual machines will be rebooted. During the platform upgrade process, all operations on the System Platform Web Console are blocked and all links (including menu items) are disabled until the system is booted up into the new platform for you to commit or rollback the upgrade. 8. Click OK in the dialog box that appears to confirm that the template has been qualified for the platform version to which you are upgrading and that both System Platform Web Console and Console Domain will reboot on completing the upgrade . 9. Click OK in the dialog box prompting you to confirm the upgrade. At this stage, the upgrade process starts and the system displays the Platform Upgrade workflow status page.

86

Implementing Application Enablement Services on System Platform R6.1

February 2011

the user is required to commit or rollback the upgrade. 10. the system will reboot using the previous release of System Platform. Avaya advises not to perform any of the following operations: • Delete a template • Install a template • Upgrade a template • Reboot the System Platform Web Console Implementing Application Enablement Services on System Platform R6. You can also check the Web Console to make sure that the upgrade process is running alright. At this stage. On the Commit or Rollback platform upgrade page. Log in to the System Platform Web Console. 11. While the system is waiting for the user to either commit or rollback. you can view the time remaining for Auto Rollback of the platform upgrade on the Commit or Rollback platform upgrade page. it is assumed that System Platform is reachable and the timer is cancelled. after the system boots in the new platform release. Commit and Rollback System Platform upgrades should be committed before performing other operations. See Committing an upgrade on page 89 Note: You are allowed a 4-hour period to log in to the System Platform Web Console. the system automatically redirects you to the login page. However. So the Platform Upgrade workflow status page does not show any updates until it reboots in the new Console Domain. During an upgrade. • Click Rollback to cancel the upgrade process and go back to the previous version of the software. you still need to verify and commit the upgrade. If you do not login during this period. This can take approximately 20 minutes. See Rolling back an upgrade on page 89. After the Web Console is up. do one of the following: • Click Commit to continue the upgrade process by committing to the newly upgraded platform.Commit and Rollback Note: The System Domain (Domain-0) and Console Domain are rebooted at this stage.1 February 2011 87 . If a user logs in to System Platform Web Console within the 4-hour period.

removing state files and so on). on the other hand. the new changes will be visible in the rolled back system. If the template-related operations are performed and you want to recover after committing or rolling back the upgrade. Commit You can execute a commit operation when you are satisfied that the new System Platform software is working without any issues. is unaffected by the changes that you make prior to committing the System Platform upgrade. if rollback is performed. removing state files and so on). • Performs a clean up operation (such as. Rollback You can execute a rollback operation if you find any errors or issues with the new System Platform software and want to go back to the older version of the software. The upgrade rollback operation will not be able to roll the system back. • Start High Availability Failover Note: System Platform does not prevent you from performing the above operations prior to selecting commit or rollback. • Commits boot loader (grub) to boot up into the old platform. • Marks the Workflow as complete and indicates that on the Platform Upgrade Status page.Upgrading System Platform Note: Rebooting System Platform Web Console before committing will roll back the system back to the previous release. Rollback can reboot the server. 88 Implementing Application Enablement Services on System Platform R6. The system performs the following when you roll back an upgrade: • Disables the four hour timer that automatically performs a rollback. If you perform the above operations. A commit of the upgrade. you need to manually rollback the changes through System Platform Web Console. The system performs the following when you commit an upgrade: • Disables the four hour timer that automatically performs a rollback. you cannot go back to the older version of the System Platform software. Committing an upgrade is unaffected by the changes made prior to committing the upgrade.1 February 2011 . • Performs a clean up operation (such as. Thereafter. After executing a commit operation. the system performs an automatic rollback. the operations will actually take effect on the system. • Commits boot loader (grub) to boot up into the new platform from now on. If you do not log in to System Platform Web Console within 4 hours after the upgrade.

click Commit to continue the platform upgrade process. Platform Upgrade field descriptions Name Upgrade Location Description Lets you specify the location from where to download or upload the template image files for the platform upgrade. Rolling back an upgrade On the Commit or Rollback platform upgrade page. click Rollback to cancel the upgrade process and go back to the previous version of the software.Committing an upgrade • Prepares the system to notify the user of the reason for rollback after rebooting into the old platform. Note: After a rollback. Options are: • Avaya Downloads (PLDS) Implementing Application Enablement Services on System Platform R6. when you log on to the System Platform Web Console. • Reboots the platform to boot up into the old platform and restores access to System Platform Web Console. or if the upgrade failed and the system rebooted to an older version of System Platform as part of fail-safe fallback mechanism.1 February 2011 89 . Committing an upgrade On the Commit or Rollback platform upgrade page. the system displays the Rollback Acknowledge page that specifies the reason for rollback (either user initiated rollback or deadmans switch) based Auto rollback.

ovf (Open Virtualization Format) extension at the location that you specify. 90 Implementing Application Enablement Services on System Platform R6. Button descriptions Button Search Description Searches for a template description file that has an .Upgrading System Platform Name Description The files are located in the Avaya Product Licensing and Delivery System (PLDS) Web site. • SP USB Device The files are located in a USB flash drive. • HTTP The files are located on an HTTP server.1 February 2011 . You will need to copy the platform upgrade files in this directory using a file transfer program and change their permissions as follows: chmod 644 <files-copied> • SP CD/DVD The files are located in a CD or DVD. You must enter an Avaya SSO login and password. Acknowledge Lets you confirm the reason for the rollback operation. Upgrades the system with the template description file. and the system goes back to the previous version of System Platform software. Opens the Platform Upgrade Details page with the search results. You must specify the URL of the platform upgrade if you select this option. Commits an upgrade operation and upgrades the System Platform software to the latest version. Note: Open virtualization format (OVF) is an open standard for packaging and distributing software that runs on virtual machines. • SP Server The platform upgrade files are located in the /vsp-template directory in the System Platform Console Domain. the system performs an automatic rollback. If you do not execute a commit operation within 4 hours after the upgrade. you cannot go back to the older version of the System Platform software. Note: After executing a commit operation. Rollback Cancels an upgrade operation. Select Upgrade Commit Selects the required template description file.

you do not need direct access to the servers. Upgrading System Platform on both servers With this method. you can start High Availability from the Failover page. 2. To proceed. If you attempt an upgrade while High Availability is running. the benefit is that you can perform both upgrades from the System Platform Web Console. This task requires direct access to the standby server. However. Click Stop Failover Mode and confirm the warning that is displayed. You do not upgrade the standby server. However. you must reinstall the standby server with the same version of System Platform as the preferred server was upgraded to. Starting High Availability after platform upgrades Once you have finished the platform upgrade procedure on both servers. Click Server Management > Failover. first stop High Availability. Upgrading System Platform on the preferred server only With this method. Implementing Application Enablement Services on System Platform R6. a warning message is displayed and the system will prevent you from performing the upgrade. This procedure synchronizes all required configuration settings from the preferred node to the standby node so that the standby node can assume the role of active node if required.Upgrading System Platform on High Availability Systems Upgrading System Platform on High Availability Systems Methods for upgrading High Availability systems You can upgrade System Platform either on both servers or on the preferred server only. 1.1 February 2011 91 . you must upgrade System Platform on each server. Therefore. Stopping High Availability This procedure restarts the console domain and all template virtual machines. you upgrade System Platform on the preferred server only. Stop and start of High Availability for platform upgrades Stopping High Availability for platform upgrades System Platform does not support platform upgrades while High Availability is running.

Log in to the System Platform Web Console. System Platform Web Console redirects to the Reboot page and after a few minutes redirects to the Login page. Starting High Availability Failover Prerequisites High Availability Failover is configured on the system. Click Server Management > Failover and check the disc synchronization progress.Upgrading System Platform System Platform Web Console redirects to the Reboot page and after a few minutes redirects to the Login page. 3.1 February 2011 . Log in to the System Platform Web Console. 3. This procedure synchronizes all required configuration settings from the preferred node to the standby node so that the standby node can assume the role of active node if required. 1. Important: If you are performing a platform upgrade. 4. do not start High Availability Failover until after you commit the platform upgrade on both machines. 4. Upgrading System Platform on both servers Prerequisites Stop High Availability. 1. This procedure restarts the console domain and all template virtual machines. 2. 92 Implementing Application Enablement Services on System Platform R6. Login to the System Platform Web Console on the standby node. Click Start Failover Mode and confirm the warning that is displayed. Click Server Management > Failover. Click Server Management > Failover and check the status of the High Availability Failover.

2. This is only a suggested order of the upgrades. The System Platform Web Console displays the failover status in the right upper corner. 3.Upgrading System Platform on High Availability Systems The System Platform Web Console of the standby node displays the failover status in the upper right corner. The System Platform Web Console of the preferred node displays the failover status in the upper right corner. A difference of version between the servers will prevent System Platform High Availability from starting after the upgrade is complete.1 February 2011 93 . Click Server Management > Failover. Go to the Platform Upgrade page and proceed with the upgrade procedure of the standby node. Log in to the System Platform Web Console on the preferred node. Note: The order of upgrades of the servers is not really important. 2. Log in to the System Platform Web Console for the preferred node. 3. 1. 4. Click Remove Failover and confirm the warning. Implementing Application Enablement Services on System Platform R6. Go to the Platform Upgrade page and proceed with the upgrade procedure of the preferred node. 4. 5. Go to Platform Upgrade page and proceed with the upgrade procedure of the preferred node. start System Platform High Availability from the Failover page of the preferred node. Once finished. Platform upgrade must be performed on each server separately. Related topics: Upgrading System Platform on page 86 Stopping High Availability on page 91 Starting High Availability Failover on page 92 Upgrading System Platform on the preferred server only Prerequisites Stop High Availability.

Note: Both servers must be running the same version of System Platform. Reinstall the standby node with the same version of System Platform as the preferred node was upgraded to. Once finished. configure and start High Availability from the Failover page of the preferred node. A difference of version between the servers will prevent you from starting System Platform High Availability after the upgrade is complete.Upgrading System Platform 5.1 February 2011 . 6. Related topics: Upgrading System Platform on page 86 Stopping High Availability on page 91 Starting High Availability Failover on page 92 94 Implementing Application Enablement Services on System Platform R6.

go to step 7. On the Search Local and Remote Template page. you must stop High Availability Failover before upgrading the AE Services template. 5. type the following URL: https://ipaddress/ webconsole. On a Web browser. Implementing Application Enablement Services on System Platform R6. If the High Availability Failover feature is not configured.Chapter 10: Upgrading Application Enablement Services Upgrading Application Enablement Services template 1. 8. 2.1 February 2011 95 . 4. select a location from the list in the Install Template From box. Enter the password for this account. then follow the instructions in your browser to install a valid certificate on your computer. 7. If you are upgrading the AE Services template in the High Availability Failover configuration. If your system is configured with the High Availability Failover feature. 6. b. Click the Stop Failover Mode button. Do the following: a. Click Virtual Machine Management > Solution Template. Click Server Management > Failover. enter admin. If you get a certificate error. Note: This is a secure site. go to step 6. Click Log On. In the User ID box. 3. Click Continue. where ipaddress is the IP address of the Console Domain that you configured during installation of System Platform.

click the AES template. go to Step 12. Click Browse EPW File. Click Upload EPW file. do one of the following: • Click Commit Installation to continue the upgrade process by committing to the newly upgraded template. • Click Rollback Installation to cancel the upgrade process and go back to the previous version of the software. Do one of the following: • If you have completed the AE Services Electronic Pre-installation Worksheet (EPW). The system displays the Template Details page with information on the AES template and its Virtual Appliances. you may be required to configure a proxy depending on your network. and then click Select. click Upgrade. do the following: a. 10. Avaya PLDS or HTTP). c. The system displays the Template Details page with information on the AES template and its Virtual Appliances. Click Upgrade. If you have completed the AE Services Electronic Pre-installation Worksheet (EPW). and click Open. On the Template Details page. 96 Implementing Application Enablement Services on System Platform R6. From the Choose File to Upload dialog box. b. 14. When Commit Installation and Rollback Installation buttons appear at the bottom of the page. select the EPW file. 11. The Template Installation page shows the status of the installation. On the Select Template page. The system displays the current template installed. Click OK to confirm that you want to upgrade the template. • If you have not completed the AE Services Electronic Pre-installation Worksheet (EPW). Go to Step 13. click Continue without EPW file .Upgrading Application Enablement Services Note: If the template installation files are located on a different server (for example. 13.1 February 2011 . 12. 9.

Enter su . Run the following commands: > ssh dom0. Type su 3. 2. Enter the root password.to log in as root. Log in to the Console Domain as admin. Implementing Application Enablement Services on System Platform R6. At the prompt. Troubleshooting steps 1. Log in to the System Domain (Dom-0) as admin. 2.1 February 2011 97 .vsp /opt/avaya/vsp/template/scripts/udomAttachCd > mount /dev/xvde /cdrom/ Cannot ping Console Domain or access the Web Console Troubleshooting steps 1.Chapter 11: Troubleshooting the installation Template DVD does not mount The template DVD does not mount automatically. 3. 4. type xm list.

type exit to log off as root.0 2714.6 If High Availability Failover is enabled.4 9071.8 12674.Troubleshooting the installation The xm list command shows information about the running virtual machines in a Linux screen. A state of b indicates that the virtual machine blocked.2 2786. The output for the active server is similar to that shown above.1 February 2011 . Type exit again to log off from System Domain (Domain-0). Example xm list output: Name Domain-0 aes udom ID 0 15 16 Mem VCPUs 512 1024 1024 2 1 1 State r-----b----b---Time(s) 60227. xm list output for the standby server: If High Availability Failover is enabled. 4. It only means that the virtual machine is currently not using any CPU time. You should see two virtual machines running at this time: System Domain (shown as Domain-0) and Console Domain (shown as udom in xm list).1 98 Implementing Application Enablement Services on System Platform R6. the output for the standby is similar to the following: Name Domain-0 aes udom ID 0 Mem VCPUs 512 1024 1024 2 1 1 State r----Time(s) 21730. A state of r indicates that the virtual machine is running. the output of the xm list command differs for the active server and the standby server. Note: The blocked state does not mean that there is a problem with the virtual machine. see the Linux manual page for the xm command. On the Linux screen. Other possible virtual machine states are: • p: paused • s: shutdown • c: crashed For more information on the information displayed.

avaya..com to check DNS is working. Restart Tomcat by performing the following steps: Implementing Application Enablement Services on System Platform R6. Ping the proxy server in the customer network. 200 OK Multiple reinstallations can result in an out of memory error If an installation wizard is used to install a template and you reinstall the template by deleting and installing it multiple times. 3. Example Type a command such as wget http://support.. Ping support. 4. Delete the template. Troubleshooting steps Perform the troubleshooting steps given here to ensure that a PermGen error does not occur. 2. 2.1 February 2011 99 .SAL does not work SAL does not work Troubleshooting steps 1. Ping the DNS server in the customer network. 1.avaya. Try a wget using the proxy from the command line to check that the proxy is working. awaiting response. an out of permanent generation memory space (PermGen) error can occur.com You should get an output similar to the following: HTTP request sent.

Type su c. b. Install the template. Type /sbin/service tomcat restart 3. 4. Log in to Console Domain as admin.1 February 2011 .Troubleshooting the installation a. Start the pre-installation Web application. 100 Implementing Application Enablement Services on System Platform R6.

2. Enter the License Host information. Note: If you do not have an e-mail message with your LAC. enter the LAC that you received in an e-mail message. 4. The license file can be accessed on the License/Keys tab of the Activation Record in PLDS and is also an attachment to the Activation Notification e-mail message. The Activation Record and Activation Notification provide details on the number of activated licenses and the License Host. You need to install the license file on WebLM to use the licenses. Note: The Quick Activation automatically assumes that you want to activate all license entitlements on LAC and gives the option to remove line items and enter the amount of each license to activate (full or partial amount). Enter your Login ID and password to log on to the PLDS Web site. follow the steps in the Searching for Entitlements section and make a note of the appropriate LAC from the LAC column. Use the License Activation Code (LAC) to activate one or more license entitlements. You may choose to activate all of the licenses or specify the number of licenses that you want to activate from the quantity available.Appendix A: Managing license entitlements from PLDS Activating license entitlements Prerequisites Host ID of the License Host if you are activating license entitlements on a new License Host. Upon successful activation of the license entitlements.1 February 2011 101 .com in your Web browser to access the Avaya PLDS Web site. PLDS creates an Activation Record and sends an Activation Notification e-mail message to the customer that is registered with the entitlements. In the LAC(s) field of the Quick Activation section. Type http://plds. Implementing Application Enablement Services on System Platform R6.avaya. 3. You can either create a new license host or use an existing license host. 1.

10. Searching for license entitlements Use this functionality to search for an entitlement by using any one or all of the following search criteria: • Company name • Group name • Group ID • License activation code In addition to these search criteria. In general. 9. enter e-mail addresses for any additional activation notification recipients. b. 7. • The Ownership tab displays the registration information.Managing license entitlements from PLDS 5. Click Next to validate the registration detail. c. From License/Key tab. PLDS also provides other additional advanced search criteria for searching license entitlements. Review the Avaya License Agreement and accept the agreement if you agree. Enter any comments or special instructions in the Comments field. • The License/Key tab displays the license files resulting from the license activation. In the E-mail to field. Click Finish. Enter the number of licenses you want to activate. Enter the License Host Information. you can view and download the license file. The Host ID is obtained from the Server Properties page of the WebLM server where the license file will be installed.1 February 2011 . 6. Perform the following steps to send an activation notification e-mail message: a. • The Overview tab displays a summary of the license activation information. The Host ID is the MAC address of the server hosting the WebLM server. Note: Avaya associate or Avaya Partners can only search license entitlements by company name. Each license file must installed on the WebLM server associated with the License Host. 8. 102 Implementing Application Enablement Services on System Platform R6. a single license file will be generated for each application. Click View Activation Record.

The system displays Search Entitlements page. do the following: a. Enter the name or several characters of the name and a wildcard (%) character. For example. see Downloading software in PLDS on page 25. Click the magnifying glass icon. Implementing Application Enablement Services on System Platform R6.com in your Web browser to access the Avaya PLDS Web site. Enter your Login ID and password to log on to the PLDS Web site. Tip: You can use a wildcard (%) character if you do not know the exact LAC you are searching for. Tip: You can use a wildcard (%) character if you do not know the exact name of the group you are searching for. enter the specific LAC in the %LAC: field. the system searches for all the LACs starting with AS0. if you enter AS0%.avaya. the system searches for all the company names starting with the letter Av. enter the appropriate information in the %Group name: or %Group ID: fields. the system searches for all the groups starting with the characters Gr. 6. 5. For example. You can enter a wildcard character (%) at any position in the search criteria. if you enter Gr%. You can enter a wildcard character (%) at any position in the search criteria. 3.Searching for license entitlements For more information on downloading license entitlements. You can enter a wildcard character (%) at any position in the search criteria. 1. enter the company name in the %Company: field. Group Names or IDs are specific to Functional Locations and Sold-To’s that define the actual location of equipment and software. If you want to search license entitlements by company name. 4. b. If you want to search license entitlements by group name.1 February 2011 103 . Click Assets > View Entitlements. If you want to search license entitlements by LAC. Select the desired company name from the list of options. For example. If you would like to see a complete list of possible companies before searching for their corresponding entitlements. if you enter Av%. Click Search Companies. c. Type http://plds. d. 2. Tip: You can use a wildcard (%) character if you do not know the exact name of the company you are searching for.

Use this functionality to move activated license entitlements from one License Host to another. you will need to search using one of the other search criteria. 8. 2. 4. 7. license host. product. You must install both of these license files to successfully complete the move operation. and/or status from the field. 104 Implementing Application Enablement Services on System Platform R6.com in your Web browser to access the Avaya PLDS Web site. Enter your Login ID and password to log on to the PLDS Web site.Managing license entitlements from PLDS You will receive LACs in an e-mail if you have supplied the e-mail address to your sales order. Type http://plds. 3. 5. You may chose to move all or specified quantities of license entitlements. Select Rehost/Move for the appropriate 'move from' License Host. Note: If you are an Avaya associate or Avaya Partner. Moving activated license entitlements Prerequisites Host ID or License Host name of the move from/to License Host. If you do not have this code. Result All corresponding entitlement records appear at the bottom of the page. select the appropriate application. 1. You can search the activation records by the Company name. Click View Activation Record information to find and select Licenses to rehost or move. product and/or license status.avaya. Note: For license moves. there are two license files that result: one license file for the “move from” license host and one license file for the “move to” license host.1 February 2011 . If you want to search license entitlements by application. enter the search criteria and click Search Activation Records. Click Activation > Rehost/Move from the Home page. Click Search Entitlements. Group name or ID using the Search Activation Records functionality.

8. 9. a single license file will be generated for each application. 12. Accept the Avaya Legal Agreement. Type http://plds. • The Ownership tab displays the registration information. you can click Add a License Host to select an existing License Host. Enter the License Host Information. Enter the number of Licenses to move in the QTY column field and click Next.avaya. Implementing Application Enablement Services on System Platform R6. The Host ID is the MAC address of the server hosting the WebLM server. 11. In general. 2. 10. • The License/Key tab displays the license files resulting from the license activation. Click Activation > Regeneration from the Home page. Validate the Registration Detail and click Next. Enter any comments or special instructions in the Comments field. b.Regenerating a license file The License Host from which you want to move license entitlements 6. Perform the following steps to send an activation notification e-mail message: a. Each license file must installed on the WebLM server associated with the License Host. Alternatively. The Host ID is obtained from the Server Properties page of the WebLM server where the license file will be installed. Click View Activation Record. Click Finish. • The Overview tab displays a summary of the license activation information. 4. From License/Key tab. 3. Enter your Login ID and password to log on to the PLDS Web site. Enter the move to License Host in the Search License Hosts field. In the E-mail to field. enter e-mail addresses for any additional activation notification recipients. 7.com in your Web browser to access the Avaya PLDS Web site. Search License Activations to Regenerate. c.1 February 2011 105 . Regenerating a license file 1. you can view and download the license file.

106 Implementing Application Enablement Services on System Platform R6. 9. 8. Each license file must installed on the WebLM server associated with the License Host. Enter any comments or special instructions in the Comments field. Click Regenerate from the appropriate record. 5. Validate the items that will regenerate and click Next. b. • The Ownership tab displays the registration information. • The Overview tab displays a summary of the license activation information. Click View Activation Record. Group name or ID using the Search Activation Records functionality. From License/Key tab. 6. In general. Perform the following steps to send an activation notification e-mail message: a.1 February 2011 . c. 10. enter e-mail addresses for any additional activation notification recipients. license host. 7. you can view and download the license file.Managing license entitlements from PLDS You can search the activation records by the Company name. Validate the Registration Detail and click Next. Accept the Avaya Legal Agreement. • The License/Key tab displays the license files resulting from the license activation. In the E-mail to field. a single license file will be generated for each application. Click Finish.

• To compare standard licensing with enterprise-wide licensing. The standard license file continues to be used for standalone AE server licensing. • For examples of licensing configurations.0). see Licensing configuration examples on page 108. see Comparison of standard licensing and enterprise-wide licensing on page 107. This means that AE Services customers are able to pool or share all AE Services features and Rights To Use (RTU) among AE Services.2. • For the procedures required to set up an AE Services configuration that uses enterprisewide licensing.1 February 2011 107 . Enterprise-wide licensing AE Services introduced support for enterprise-wide licensing with Release 4. This applies only to AE Services features licensed in the AE Services license file and not those licensed in the Communication Manager license file. AE Services customers are able to purchase any number of licenses and then allocate those licenses to various AE Services at their own discretion. Note: Enterprise-wide licensing is not supported in System Platform High Availability Failover configurations.Appendix B: Enterprise-wide licensing Overview of enterprise-wide licensing Starting with Release 4.2. With enterprisewide licensing. Implementing Application Enablement Services on System Platform R6. Comparison of standard licensing and enterprise-wide licensing Standard licensing AE Services has used the standard license file since the introduction of the platform (Release 3. see Setting up a configuration for allocating licenses on page 111. AE Services supports enterprise-wide licensing.

Enterprise-wide licensing

Standard licensing A standard license is generated by the Product Licensing and Delivery System (PLDS) from the system record for an AE Server.

Enterprise-wide licensing Enterprise-wide licensing includes a master enterprise license file (ELF) and an allocation license file (ALF). • The master enterprise license file (ELF) is generated by the PLDS from the system record from the enterprise. The master license file can reside on an AE Server or a dedicated WebLM server. • The allocation license file (ALF) is generated by WebLM based on features in the master license file and user allocations on the AE Server. The ALF or ALFs can reside on one or more AE Servers.

The standard license file is installed on the AE Server. In a standard licensing arrangement, AE Services and the WebLM server must be co-resident.

With enterprise wide licensing, WebLM does not have to be co-resident with AE Services.

With standard licensing, a license can not be With enterprise-wide licensing, you can moved from one server to another, and reallocate enterprise capacities and features capacities can not be reallocated. as desired.

Licensing configuration examples
To understand how licensing configurations work, this section provides a description of standard licensing and enterprise-wide licensing.

Standard licensing
In a standard licensing configuration, the standard license file (SLF) is installed on the AE Server and is controlled by the WebLM server running on the AE Server. The following figure illustrates the standard licensing configuration. Note: If you use the standalone configuration, use the default settings on the WebLM Server Address page in the AE Services Management Console.

108

Implementing Application Enablement Services on System Platform R6.1

February 2011

Licensing configuration examples

Standalone configuration (without enterprise-wide licensing)

Enterprise-wide licensing — allocating licenses or features
Starting with Release 4.2, AE Services expanded its licensing capabilities to include enterprisewide licensing. Enterprise-wide licensing provides the flexibility to move capacities and features from one AE Sever to another. For example, prior to AE Services 4.2, if you had purchased 3 AE Servers with different licensing capacities, you could not move capacity purchased for one AE Server to another AE Server. With enterprise-wide licensing, you can move capacities or features from one server to another by using a master WebLM server to allocate license features to different AE Servers. Because this configuration relies on a master enterprise license file (ELF), which generates allocation license files (ALF), it is referred to as an ELF/ALF configuration. Each ALF will reside on an AE Server with a Local WebLM Server. This is the recommended model for AE Services enterprise configurations. If you use the ELF/ALF model, you do not need to change the default settings on the WebLM Server Address page. For this configuration you must use WebLM Administration to configure the local WebLM so the master WebLM server can allocate licenses to the AE Server. (In the WebLM Administration, select Licensed Products > Application Enablement (CTI) > Configure Local WebLMs > Add Local WebLM.) The following figure illustrates an ELF/ALF configuration.

Implementing Application Enablement Services on System Platform R6.1

February 2011

109

Enterprise-wide licensing

Enterprise-wide licensing — allocating licenses or features

For information about setting up this type of configuration, see Setting up a configuration for allocating licenses on page 111.

Enterprise-wide licensing — pointing to a master license on a remote server
Another type of enterprise licensing configuration is an enterprise license file (ELF)-only configuration. In an ELF-only configuration, the enterprise license file resides on a master WebLM server, and one or more AE Servers point to the IP address of the master WebLM server. No allocation license files (ALFs) reside on AE servers. If you use the ELF-only configuration, you must administer the WebLM Server Address page in the AE Services Management Console with the WebLM IP address and WebLM port number for the master WebLM server that hosts the ELF. The following figure illustrates an ELF-only configuration.

110

Implementing Application Enablement Services on System Platform R6.1

February 2011

Setting up a configuration for allocating licenses Use the following procedures to set up a configuration for allocating licenses. You will need to use this procedure to install the master enterprise license file (ELF) on the master WebLM server. Implementing Application Enablement Services on System Platform R6. Installing the license file and configuring the master WebLM server This procedure applies to a configuration where the master WebLM server allocates licenses to local AE servers (see Enterprise-wide licensing — allocating licenses or features on page 109).Setting up a configuration for allocating licenses Enterprise-wide licensing – pointing to a master license on a remote server Caution: Using the ELF-only configuration is not recommended because network latency and outages can affect the ability of the AE Server to acquire licenses. and it creates a single point of failure for licensing.1 February 2011 111 . This server can be an AE server or a computer dedicated to WebLM. Follow these steps to install the enterprise license file (ELF) on the server that hosts the enterprise license file (ELF).

example. the user ID of the administrator (Admin Account). d.17. for example https://aserver. 5. accept the defaults. • Name: Master WebLM Server • Description: leave blank • IP Address: 127. Press Enter. email notification is disabled (off). In terms of this configuration example. For the Email Notification Settings for Periodic Operation. On the WebLM main menu.1 (by default. click Browse. Locate the license file and click Open. 6. When the process is complete. complete the settings (Email Notification and Email Addresses) based on your operational requirements. e. click Licensing > WebLM Server Access. accept the defaults. 7. For the Master WebLM Configuration settings. WebLM uploads the license file to the WebLM server. From the WebLM main menu. From a web browser. 8. 9. 3. For the SMTP Server Settings. the IP address would be 135. select the day and time.8.0. 2. Click Install. it is set to the loopback address). which are optional. Log in to the computer that has the license file stored on it. which are required.1 February 2011 . c. On the Web License Manager Log on screen. Notice that the WebLM main menu now displays Application_Enablement under Licensed Products.com. the server displays the message: License file installed successfully.0.Enterprise-wide licensing 1.122. select Application_Enablement > Configure Enterprise. 112 Implementing Application Enablement Services on System Platform R6. type the fully qualified domain name or IP address of the AE Services server. 4. and click the arrow. provide the name of the SMTP Server (Server Name). These are the authentication settings for the SMTP server that sends email notifications for periodic operation failures. which are required. enter your WebLM user name and password. b. For the Default Periodic License Allocation Schedule. For the Default Periodic Operation Settings settings. and the password of the administrator (Admin Password). 10. based on your operational requirements. On the Application Enablement Services welcome page. Complete the Configure Enterprise page as follows: a. By default.

Name: the <name of the local AE Server>. Note that the default settings refer to the settings that you administered on the Master WebLM Server. follow this procedure to add a local WebLM server. Implementing Application Enablement Services on System Platform R6. From the WebLM main menu.Description: a descriptive term for the local AE Server (optional) . select the day and time. • Periodic Usage Query Schedule: Accept the defaults. it can be any name you choose. For the Default Period Usage Query Schedule. Next steps Continue with Adding a local WebLM server on page 113. Click Configure and Validate. Note: You can allocate feature licenses only if the connection between the master WebLM server and the local WebLM server is validated and established. Click Submit. Complete the Add Local WebLM page as follows: • Local WebLM Settings: . (Although this name is required. lzbundled05. 1.123. Note that the default settings refer to the settings that you administered on the Master WebLM Server. For purposes of this example. select Application Enablement > Add Local WebLM. g.IP Address: <IP address of the Local AE Server>. Adding a local WebLM server From the Master WebLM Server Web page.Port: 443 (the default) • Periodic License Allocation Schedule: Accept the defaults.1 February 2011 113 . the IP address is 135.8. for example. 3. based on your operational requirements. 2.17. .Setting up a configuration for allocating licenses f.) . Next steps Continue with Setting up the Local WebLM Server in your configuration on page 114.

click Yes to accept the SSL certificate. Verify that the WebLM Server address page displays the following settings: • WebLM IP Address: 127. 5. 4. From a web browser. The password must contain 6 to 14 characters. 2.com.8. and the password itself must not be blank. From the AE Services Management Console main menu. select Logout to log out of WebLM. log in as admin with the new password. the IP address would be 135. White spaces are not permitted in the password. type the fully qualified domain name or IP address of the AE Server. 7. On the Web License Manager log on screen.123.Enterprise-wide licensing Setting up the Local WebLM Server in your configuration Use the following procedure to change the default WebLM password and to verify the settings on the WebLM Server Address page in the AE Services Management Console. 114 Implementing Application Enablement Services on System Platform R6.1 February 2011 . The first time you log in to WebLM. 11.1 • WebLM Port: 8080 Next steps Continue with Changing the allocations of a license file on page 115.0. 1. Log on to the AE Services server (local WebLM server) again. On the Web License Manager log on screen. From the WebLM main menu. 6. Press Enter. the WebLM server displays the Change Password page. log in to WebLM with the default user name and password. In terms of this configuration example. The default user name is admin. On the Change Password page. select Licensing > WebLM Server Address. 8. From the Application Enablement Services Welcome page. for example https://aserver. 3.17. 9. At the Security Alert. click Licensing > WebLM Server Access. complete the fields and click Submit. 10.0.example. and the default password is weblmadmin.

enter an appropriate value in the New Allocation box and click Submit Allocations. From a web browser. Implementing Application Enablement Services on System Platform R6. enter your WebLM user name and password. and click the arrow.17. From the Master WebLM Server web page. On the Web License Manager log on screen. 3. click Yes to accept the SSL certificate. WebLM processes the allocation request.1 February 2011 115 .Setting up a configuration for allocating licenses Changing the allocations of a license file The master WebLM server provides you with the ability to change license file allocations for your local WebLM servers. select Application Enablement > Allocations.example. Next steps Continue with Verifying the license allocations on the Local WebLM Server on page 115. click Licensing > WebLM Server Access. From the WebLM main menu.com. assume that you want to allocate 20 TSAPI Simultaneous User licenses to the local WebLM server. 2.example. follow this procedure to change the license allocations. 5.123. On the Change Allocations page. and click Submit Allocations. On the Application Enablement Services welcome page. 1. the IP address would be 135. for example https://aserver. 8. Verifying the license allocations on the Local WebLM Server Follow these steps to verify that the license allocations that you administered are in effect. type the fully qualified domain name or IP address of the AE Server. 7.8. 4. 1. In terms of this configuration example. for example https://aserver. type the fully qualified domain name or IP address of the AE Server. click Change Allocations. Enter 20 in the New Allocations text box.com. For example. From a web browser. On the Allocations by Features page. and displays the updated Allocations by Features page. 6. At the Security Alert. Press Enter.

From the Application Enablement Services Welcome page.Enterprise-wide licensing In terms of this configuration example.123. 7. 2. 3. 116 Implementing Application Enablement Services on System Platform R6. 5. Press Enter.8. Verify that the licensed features on the local WebLM server are consistent with the settings you administered on the master WebLM server. and click the arrow. enter your WebLM user name and password. From the WebLM main menu. The master WebLM will push the ALF to the local WebLM based on the administered schedule (Periodic License Allocation Schedule).1 February 2011 .17. 6. select Licensed Products > Application Enablement. click Yes to accept the SSL certificate. On the Web License Manager log on screen. Note: The Allocation license is valid for up to 30 days. At the Security Alert. click Licensing > WebLM Server Access. the IP address would be 135. 4.

The server model and specific hardware components in your server depend on the requirements of the software application that will run on the server.Appendix C: Installing and connecting the S8800 server Overview of the Avaya S8800 Server Introduction The Avaya S8800 Server supports several Avaya software applications.1 February 2011 117 . Front of server 1 2 3 Hard disk drive activity LED (green) Hard disk drive status LED (amber) Drive bay 0 Implementing Application Enablement Services on System Platform R6. The server is available in a 1U model or 2U model and with various hardware components.

8 9 10 11 12 13 14 15 16 17 18 19 Operator information panel release latch Video connector USB connector 1 Rack release latch USB connector 2 DVD eject button DVD drive activity LED DVD drive Drive bay 5 Drive bay 3 Drive bay 1 Rack release latch 118 Implementing Application Enablement Services on System Platform R6.Installing and connecting the S8800 server 4 5 6 7 Drive bay 2 Drive bay 4 Power control button and LED Operator information panel Note: The operator information panel is shown in the pushed in position.1 February 2011 .

Overview of the Avaya S8800 Server Back of server 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 PCIe slot 1 (used for optional Ethernet connectors 5 and 6) Ethernet activity LED Ethernet link LED Video connector PCIe slot 2 USB connector 4 AC power LED (green) DC power LED (green) Power supply error LED (amber) Power supply 2 (redundant power supply) Power supply 1 (primary power supply) USB connector 3 Serial connector System error LED (amber) System locator LED (blue) Power LED (green) Ethernet connector 2 Ethernet connector 1 Implementing Application Enablement Services on System Platform R6.1 February 2011 119 .

1 February 2011 . Approximate heat output: • Minimum configuration: 662 Btu per hour (194 watts) • Maximum configuration: 1400 Btu per hour (400 watts) Heat output varies depending on the number and type of optional features that are installed and the power-management optional features that are in use. Actual sound-pressure levels in a given location might exceed the average values stated because of room reflections and other nearby noise sources.Maximum: 240 V AC • Input kilovolt-amperes (kVA).3 inches) Maximum weight: 15.69 inches. • Sine-wave input (47–63 Hz) required • Input voltage low range: . below which a large number of computers will operate.10 and ISO 7779 and are reported in accordance with ISO 9296.194 kVA Weight Heat output Electrical input requirements 120 Implementing Application Enablement Services on System Platform R6.Minimum: 0. 20 System management Ethernet connector (IMM) Server specifications Type Dimensions Description Height: 43 mm (1. operating: 6.Maximum: 127 V AC • Input voltage high range: .Minimum: 200 V AC .1 bel The sound levels were measured in controlled acoustical environments according to the procedures specified by the American National Standards Institute (ANSI) S12. 1U) Depth: 711 mm (28 inches) Width: 440 mm (17. approximately: . Acoustic noise emissions Declared sound power.Installing and connecting the S8800 server 19 Ethernet connectors 3 and 4 (with optional 2-port Ethernet daughter card) Note: The optional 2-port daughter card is not applicable to Application Enablement Services on System Platform.4 kg (34 lb.Minimum: 100 V AC .) when fully configured. The declared sound-power levels indicate an upper limit.

2. Optionally. fully-buffered Up to 32 GB with specified 2GB DDR-3 RDIMMs (Two 2GB DIMMs (16 GB per processor) DIMMs): • ECC registered • Slots: 16 dual inline Media drive Hard disk drive expansion bays Hard disk drive DVD-R/W SATA slimline No additional options Six 2.Maximum: 0. • Serial • Two USB • Video • Systems management Ethernet (IMM) Server components Component Microprocessor Minimum specification One Intel E5520 quad core. Memory 4 GB of 1333 Mhz.5" 10K RPM hard drives • Additional 146-GB 10K RPM drives • High performance 146-GB 15K RPM drives RAID controllers ServeRAID-MR10i RAID SAS ServeRAID-BR10i SAS RAID adapter that provides RAID level adapter that provides RAID level 1 or 5.700 kVA Front connectors • Two USB • Video Back connectors Description • Two Ethernet (RJ 45).Overview of the Avaya S8800 Server Type .93 Ghz. Includes 256 MB cache 1 (used for AES) Implementing Application Enablement Services on System Platform R6. two or four additional Ethernet.5-inch hot-swap SAS hard No additional options disk drive bays Two 146 GB SAS 2.1 February 2011 121 .26 GHZ processor Upgrade options based on product requirements • One additional E5520 processor for a total of two processors • Higher speed E5570 processor that runs at 2.

half-length cards No additional options Hot-swap fans Power supply Video controller Six One 675W. • SVGA compatible video controller • DDR2 250 MHz SDRAM video memory controller • Avocent Digital Video Compression • Video memory is not expandable No additional options Redundant 675W.000 feet) 122 Implementing Application Enablement Services on System Platform R6. 12V AC power supply Integrated Matrox G200 (two analog ports.000 feet) 10º C to 32º C (50º F to 90º F) at altitude of 914.000 feet) 914. 12V AC power supply No additional options S8800 Server environmental requirements Server status Server on Air temperature Maximum Altitude Relative humidity 8% to 80% 10º C to 35º C (50º F to 2.133 m (3. that can be connected at the same time) The maximum video resolution is 1280 x 1024 at 75 Hz.4 m to 2.Installing and connecting the S8800 server Component Minimum specification module and battery for write cache Upgrade options based on product requirements PCI expansion slots Two PCI Express x16 Gen 2 slots: • Slot 1 supports half-height. half-length cards • Slot 2 supports full-height.4 m (3.1 February 2011 .133 m 95º F) at altitude of up to (7.000 to 7. one front and one back.

• After installing components in a rack.133 m 109. Important: • Always load the rack from the bottom up. Danger: • Before installing systems in a rack. • Do not overload the AC supply branch circuit that provides power to the rack. It is your responsibility to ensure that the final combination of system and rack complies with all applicable safety standards and local electric code requirements. never pull more than one component out of the rack on its slide assemblies at one time. The total rack load should not exceed 80 percent of the branch circuit rating. Failure to install stabilizers before installing systems in a rack could cause the rack to tip over. Systems are considered to be components in a rack. • System rack kits are intended to be installed in a rack by trained service technicians.000 feet) Safety instructions Use the following safety guidelines to ensure your own personal safety and to help protect your system and working environment from potential damage. Also refer to the rack installation documentation accompanying the rack for specific caution statements and procedures. and load the heaviest item in the rack first.1 February 2011 123 . • Use caution when pressing the component rail release latches and sliding a component into or out of a rack because the slide rails can pinch your fingers. The weight of more than one extended component could cause the rack to tip over and may result in serious injury. potentially resulting in bodily injury. Note: • Your system is safety-certified as a free-standing unit and as a component for use in a rack cabinet using the customer rack kit. Implementing Application Enablement Services on System Platform R6. install front and side stabilizers on stand-alone racks or the front stabilizer on racks that are joined to other racks.0°F to 2. Observe the following precautions for rack stability and safety. Thus. • Make sure that the rack is level and stable before extending a component from the rack.Safety instructions Server status Server off Air temperature Maximum Altitude Relative humidity 8% to 80% 10°C to 43°C (50.4°F) (7. component refers to any system as well as to various peripherals or supporting hardware.

• Do not place any object on top of rack-mounted components. Avaya-provided equipment Avaya provides the following equipment: • Server and power cord or cords • Slide rails • Cable management arm assembly • Cable management arm stop bracket • Cable management arm mounting bracket • Cable management support arm • Two 10–32 screws • Four M6 screws • Five small cable ties • One large cable tie • Compact flash reader. Included when required by the product ordered.Do not leave open spaces above or below an installed server in your rack cabinet. . USB cable. Customer-provided equipment The customer must provide the following equipment: • Standard 19-inch four-post equipment rack that is properly installed and solidly secured. To help prevent damage to server components. Usually 15 cm (6 in.Install the server only in a rack cabinet with perforated doors. and flashcard (for backing up files. . The rack must meet the following standards: 124 Implementing Application Enablement Services on System Platform R6.Installing and connecting the S8800 server • Ensure that proper airflow is provided to components in the rack: . such as uninterruptible power source (UPS). always install a blank filler panel to cover the open space and to help ensure proper air circulation. Included when required by the product ordered.1 February 2011 .Do not block any air vents.) • Modem and USB or serial cable (for remote maintenance.) of space provides proper airflow.) • Other hardware as ordered. • Do not step on or stand on any component when servicing other components in a rack.

1 Task Verify that all equipment is on site. .International Electrotechnical Commission standard IEC 297 .Clearance requirements . Notes Compare the list of items that were ordered to the contents of the boxes.Deutsche Industrie Norm standard DIN 41494 • Screws that come with the racks for installing the rails • #2 cross-point (Phillips) screwdriver or 3/8 inch flathead screwdriver • USB keyboard. • Power from a nonswitched electrical outlet • Access to the network Clearance requirements Install the server in a rack that meets the following requirements: • Minimum depth of 70 mm (2.18 inches) between the rear mounting flange and inside of the rear door if the server is installed in a cabinet. Do not rely on the packing slips inside the boxes for the correct information.American National Standards Institute and Electronic Industries Association standard ANSI/EIA-310–D-92. 2 Verify that the rack is installed according to the manufacturer's instructions and in accordance with all local codes and laws. • Minimum depth of 718 mm (28. Implementing Application Enablement Services on System Platform R6. • Minimum depth of 157 mm (6.76 inches) between the front mounting flange and inside of the front door if the server is installed in a cabinet. and monitor must be available on the site for advanced installation or troubleshooting. USB mouse. Use the inventory list provided by your project manager.1 February 2011 125 . Server installation checklist No.27 inches) and maximum depth of 762 mm (30 inches) between the front and rear mounting flanges to support the use of the cable-management arm.

See the cabinet manufacturer's documentation. 4 7 8 9 10 11 Replace the cabinet doors.avaya. Attaching the rails to the rack on page 127 Installing the server in the rack on page 129 Installing the cable management arm on page 131 (optional) See the cabinet manufacturer's documentation. Remove the cabinet doors.Installing and connecting the S8800 server No. if necessary.com. accordance with local electrical available at http://support. Installing the Avaya S8800 Server Rack installation components The following figure shows the items that you need to install the server in the rack cabinet. 126 Implementing Application Enablement Services on System Platform R6. code.1 February 2011 . if necessary. 3 Task Notes Verify that the rack is grounded in See Approved Grounds (555–245–772). Turning on the server on page 134 Troubleshoot the installation.

Each slide rail is marked with either an R (right) or an L (left). remove them before you begin the following installation procedure.Installing the Avaya S8800 Server 1 2 3 4 5 6 7 8 9 10 11 Cable-management arm stop bracket (1) Cable-management arm assembly Slide rail (left) Slide rail (right) Large cable tie (1) Cable ties (5) M6 screws (4) 10–32 screws (2) Cable-management support arm Front of rails Cable-management arm mounting bracket (1) Attaching the rails to the rack Prerequisites If the slide rails in your rack installation kit came with thumbscrews installed. Implementing Application Enablement Services on System Platform R6.1 February 2011 127 .

This slide rail kit or a shelf would replace the Avaya-supplied slide rail kit that ships with the server . Drop the rail into place until it clicks. See the following figure. 4. See the following figure. and insert the two pins (5) on the front of the rail into the two lower holes in the U on the front of the rack. See the following figure. 128 Implementing Application Enablement Services on System Platform R6. 2. 3. Avaya requires that the customer provide the appropriate rails or shelf for their rack.Installing and connecting the S8800 server Important: The slide rails that come with the server are compatible with standard 19-inch.innovationfirst. 1.1 February 2011 .com/ibm-x3x50-m2slide-rail-kit. Pull out the front latch (2) to slide out the front side rail. Drop the slide rail down (4) until it latches into place.shtml. From the front of the rack. If you are installing the server in any other type of rack. Rack Solutions has numerous rail kits and shelf options. 4-post racks that have square holes. 5. Push the rails so that the pins go into the holes (3). See the preceding figure. Pull the slide rail forward. Select one of the slide rails and push up on the front moveable tab (1). line up the three pins on the rear of the slide rail with the three holes in the selected U on the rear of the rack. See http://rs. See the preceding figure.

Next steps Install the server in the rack. Push the front latch (6) in all the way. Repeat this procedure to install the other rail onto the rack.Installing the Avaya S8800 Server 6. Implementing Application Enablement Services on System Platform R6. 7. Installing the server in the rack Prerequisites Attach rails to the rack. See the following figure. two times. Make sure that each front latch is fully engaged. Pull the slide rails forward (1) until they click. 1.1 February 2011 129 . 8. into place. See the preceding figure.

See the preceding figure. See the preceding figure. Push the server (7) all the way into the rack until it clicks into place. Make sure that the front latch (5) slides over the nail heads. Slide the server down until the rear nail heads slip into the two rear slots. 6. 5. Slowly lower the front of the server (4) until the other nail heads slip into the other slots on the slide rails. 7. 130 Implementing Application Enablement Services on System Platform R6. See the following figure. Insert the optional M6 screws (8) in the front of the server when you move the rack cabinet or if you install the rack cabinet in a vibration-prone area. Lift the locking levers (6) on the slide rails. Carefully lift the server and tilt it into position over the slide rails so that the rear nail heads (2) on the server line up with the rear slots (3) on the slide rails. 4. See the preceding figure.Installing and connecting the S8800 server 2. See the following figure. 8. 3.1 February 2011 . See the preceding figure.

To install the cable-management arm on the right side.Installing the Avaya S8800 Server Next steps Install the cable management arm if desired. Connect one end of the support arm (1) to the same slide rail to which you plan to attach the cable-management arm so that you can swing the other end of the support arm (2) toward the rack. 1. This procedure shows it being installed on the left side.1 February 2011 131 . Implementing Application Enablement Services on System Platform R6. follow the instructions and install the hardware on the opposite side. The cable-management arm can be installed on either side of the server. See the following figure. Installing the cable management arm Prerequisites Attach rails to the rack and install the server in the rack.

pull the pin out (5).1 February 2011 . 4. 132 Implementing Application Enablement Services on System Platform R6. Install the L-shaped cable-management stop bracket (3) on the unattached end of the support arm. To attach the other side of the support arm to the backside of the slide rail. See the following figure 3. See the following figure. See the preceding figure. and then slide the bracket (6) into the slide rail.Installing and connecting the S8800 server 2. Turn the bracket (4) to secure it to the support arm.

See the following figure. 11. 12. See the following figure. and then slide that cable management arm tab into the slot (12) on the outside of the slide rail. 10. 9. if required). 7. See the following figure. See the preceding figure. Push the tab until it snaps into place.Installing the Avaya S8800 Server 5. Implementing Application Enablement Services on System Platform R6. Pull out the mounting bracket pin (7) and slide the mounting bracket (8) into the slide rail onto which you are installing the cable-management arm. 8. Push the bracket into the slide rail until the spring-loaded pin snaps into place. 6. Attach the power cords and other cables to the rear of the server (including keyboard. 13. Pull out the cable-management arm pin (9). Route the cables and power cords on the cable-management arm (13) and secure them with cable ties or hook-and-loop fasteners. Push the tab until it snaps into place. Place the cable-management arm on the support arm. Pull out the other cable-management arm pin (11). and then slide the cable-management arm tab (10) into the slot on the inside of the slide rail. and mouse cables.1 February 2011 133 . monitor.

turn on the server to make sure that it powers up properly.1 February 2011 . turn it off before you start any software installation procedure. Insert the optional M6 screws in the front of the server when you move the rack cabinet or if you install the rack cabinet in a vibration-prone area. See the following figure. Once you determine that it powers up properly. Slide the server into the rack until it snaps into place. 134 Implementing Application Enablement Services on System Platform R6. 14. Turning on the server After the server is installed in the rack.Installing and connecting the S8800 server Note: Allow slack in all cables to avoid tension in the cables as the cable-management arm moves. 15.

Plug one end of the power cord into the server power supply and the other end into a UPS or nonswitched outlet. and one or more fans might start running. the server will not turn on. For High Availability Failover. If you press the power button while the power-on LED is blinking quickly (three flashes per second). To connect a monitor and a keyboard to the server. Approximately 3 minutes after the server is connected to power. press the power button on the front of the server. 2. 1. To connect the servers to the customer's network. connect the cable to Ethernet connector port (eth0). The Ethernet specification limit for this distance is 100 meters. See Front of server on page 117. use the video connector and USB ports in the server. After you press the power button. one or more fans might start running to provide cooling. Once the power-on LED begins to blink slowly.Connecting the server to the network Important: You must wait for the power-on LED to blink slowly (one flash per second) before pressing the power button.1 February 2011 135 . the power-on LED will blink slowly (one flash per second). both servers must be in close proximity so that they can be connected with the crossover cable. the server takes approximately 5 minutes to initialize. and the power-on LED will blink quickly (three flashes per second). Approximately 5 seconds after the server is connected to power. Next steps See the specific product documentation for information on installing the operating system and software. 2. The power-on LED will stop blinking and stay lit. To connect the server for High Availability Failover. Implementing Application Enablement Services on System Platform R6. See Back of server on page 119. See Back of server on page 119. Connecting the server to the network 1. connect the eth cables to the Dual NIC High Availability Failover configured port. 3.

1 February 2011 .Installing and connecting the S8800 server 136 Implementing Application Enablement Services on System Platform R6.

.....46 AES Ethernet interface .............................................................................................125 client application computer requirements ...............46 CTI link requirements ................51 Commit ......................56 Platform Upgrade page ..............................................................22 customer provided .......................15..............................89 Search Local and Remote Patch page ................27 writing ISO image .........................................................................................................52 Console Domain Network Configuration screen configuring ..................25 Dual NIC configuration guidelines .....15 Dell R610 server ...........................................................................82 Patch Detail page .....................107 environmental specifications ....13 duplex settings for AES .................................35 G Gateway Configuration Implementing Application Enablement Services on System Platform R6.............................................................................................................................9 AES template prerequisites for installing ...........................................................15 cust password ............................................................................................23 F failover configuring ..............44 Date/Time and NTP setup screen configuring .................................31 clearance requirements ..................9 Application Enablement Services on System Platform installation overview .....27 C cable management arm installing .........................16 command line accessing Console Domain ....42 craft password ....................62 console domain configuring network settings ................................................................................................................................120 enterprise-wide licensing ...............131 Change Password page in WebLM ................................................55 Firefox disabling proxy servers ..............................................................................................................................................................................................................................14 DVD does not mount automatically ......................................................................................................................124 customer-provided ..............................................29 downloading software ........113 admin password ................42 Console Domain accessing command line .......................... 16 comparison of standard licensing and enterprise-wide licensing .................16 Configure Failover page field descriptions .................57 Patch List page .................................................................1 February 2011 137 .........................................101 adding a local WebLM server ............................................................................61 fan specifications ......107 computer requirements ..............................124 Avaya-provided ....19 D date configuring .63 altitude requirements ................121 field descriptions Managed Element page ..................................52 accessing System Domain ....................Index A activating license entitlements ...97 recommendations .......................12 AES on System Platform offer ..............................................................44 delays on communications channel ................................................115 checklist installation ........122 Application Enablement Services on System Platform High Availability Failover (High Availability Failover) .......................................................................................................................87 Communication Manager requirements ..................................122 equipment Avaya provided ...............................................................................................46 E electric input requirements ............................................................................................................114 changing the allocations of a license file ...................

..........................................14 NMS configuring for SAL Gateway ........81 network settings configuring for console domain ................................................... recommended settings .......14 Internet Explorer disabling proxy servers ......................122 L laptop configuring to connect to server ................................14 Network Management Systems page field descriptions ...31 using laptop .................................................................... 16 memory specifications .........................49 enabling .......................61 requirements ...........................................................................................................................................101 searching for .................................................................................................................60 starting .....42 configuring for system domain (domain-0) ...................1 February 2011 ............121 heat output ................81 noise emissions ................... 93 humidity requirements ..........................................................................121 media server requirements ......................................................................2 K keyboard selecting type .2 license entitlements activating .................................................................35 IP forwarding disabling ..........................................91 stopping .......................34 connecting to server .............................................14 latency requirements ......................................34 ISO image verifying on DVD ....................27 N network interface speed and duplex settings .......................107 configuration examples .............................................59 prerequisites for configuring .... required settings ...........39 verifying on Linux-based computer ...11 Network interfaces.....................111 interface speed for AES ...............91 High Availability Failover configuring .....................................................................................................40 NIC......25 verifying on Windows-based computer .................................................................................................................................field descriptions .....................................................91 upgrading System Platform ..............................................................................................26 writing to DVD or CD ......................................................................................................................................... 110 enterprise-wide ...................121 I installation checklist ..............63 installing the license file ...........................61 overview ...........120 High Availability about start and stop for upgrades ................................................................................................................................................82 media drive specifications ...................................................38 138 Implementing Application Enablement Services on System Platform R6...............................120 notices.............................................102 licensing comparison of standard licensing and enterprisewide licensing ..........15...........................................36 ldap password .........................................121 microprocessor specifications .......79 H hard disk drive specifications ............46 legal notices ......................................75 field descriptions ....36 using server console ...........48 using to install System Platform ...................................................................................................................................................................................................................20 installation checklist server ........49 IP settings configuring on laptop .......................................................92 High Availability systems about platform upgrades ............................................................... legal ...37 worksheet .....................................................................108..................125 installing AES template ..............109 standard ..................................................................................108 M managed element adding in SAL Gateway ...........92...........................................................15 Network interfaces ...........77 Managed Element page field descriptions ................................................38 Keyboard Type screen ................

........................78 managing service control ..........................................................................35 disabling in Internet Explorer ................................................................. 68..................................89 PLDS ..............................................81 remote access server configuring ........................................22.......................................................24 rehosting ................80 Proxy Server page field descriptions .......................................................105 registering .............................................................................................................. measure round-trip packet delivery time ...............75 configuring NMS servers ................................ 80 configuring Secure Access Concentrator Core Server ...................................67 server back view .....80 SAL Gateway ...................................................................................71 configuring a proxy server ....77 applying configuration changes .......121 connecting laptop ..76 browser requirements ......................85 Platform Upgrade page field descriptions ................................................................................................................46 Patch Detail page field descriptions ..............73 field descriptions ...............................45 default .....................54 proxy server configuring for SAL Gateway .....................65 searching for license entitlements ............ 16 Rollback .....................68 starting user interface .........................102 Secure Access Gateway Server .........................................................................................................................72 configuring network management system .......................................................................67..............................................................60 for System Platform installation ......NTP server configuring in System Platform ...................................................87 root password .....................................57 Patch List page field descriptions ........................................68 proxy configuring ............... 25 downloading software .75 prerequisites for configuration ........................................................... 70–78................................................74.......................................15 ping.........16 for High Availability Failover ...... 80...........................................................55 Search Local and Remote Template page field descriptions ......................15 passwords configuring in System Platform ................54 PCI slot specifications ...............................................70 configuring ............24 requirements client application computer ......................45 Passwords screen configuring ......................127 regenerating a license file ................................................................................... 23 media server ...................70 Search Local and Remote Patch page field descriptions ...............................1 February 2011 139 ...............................................................................74 field descriptions .......44 P packet delivery time ....................................................48 R rack attaching rails ...................................15 platform upgrade .....................80 proxy servers disabling in Firefox ..........................................56 patches downloading .....................35 rails attaching to rack ...........................................................15.............25 power supply specifications ..............................................................................121 Product ID changing for System Platform .........................45 field descriptions ................................121 periodic spiked delays .................................121 Implementing Application Enablement Services on System Platform R6................73........................................................... 81 configuring SAL Enterprise ..............................123 SAL Enterprise configuring ............................................53 installing ....................................................................................................................................................................................................................104 Remote Access field descriptions ................................................................................................... 81 adding a managed element ..129 RAID controller specifications ..72 field descriptions .....................................................81 configuring remote access server ..................24...............................................69 product registration ...........................................73 disabling .................................46 S safety instructions .....127 installing server .........119 components .................................................................................81 required software ..........................

...................63 time configuring ....92.........40 System Domain Network Configuration screen field descriptions .....43 vspmediacheck ..................................................................................................................51 system domain (domain-0) configuring network settings ..............................134 U upgrades about stop and start of High Availability ......39 T Telnet opening session from laptop to System Platform server .........................................41 System Platform upgrading ..........................................................................................................................................44 troubleshooting DVD does not mount ....................................................44 time zone configuring .....44 Time Zone Selection screen W Web Console accessing ........ 93 on preferred server .............................................................................................................93 V verifying the license allocations on the local WebLM server ..................................42 field descriptions .............99 SAL not working ......................................................................................86 upgrading AES template ...........................................................................................121 Virtual Machine Management page field descriptions ....................78 System Domain accessing command line .91 upgrading System Platform ..............................................................................120 server console using to install System Platform ......................................................120 turning on ...................................................50 configuring ....97 failure to access Web console ...........................................................................................................................................................97 multiple reinstallations can result in an out of memory error ...............................................122 template prerequisites for installing ....dimensions .....................65 VSP Console Domain Network Configuration screen configuring .......................................................................................................99 turning on server ...................................................37 services port accessing System Platform through .........................13 SNMP trap receivers adding ..............................86 System Platform Web Console accessing ..............................36 temperature requirements ..115 video controller specifications ....................................................................................................................................................1 February 2011 ..............................50 worksheet installation .......................20 140 Implementing Application Enablement Services on System Platform R6..............49 Single NIC configuration guidelines ....................................................................................................95 upgrading System Platform on High Availability systems ..................................117 installing in rack ................134 weight ..120 front view ..........................................129 specifications ........................................97 failure to ping Console Domain ..............................................

Sign up to vote on this title
UsefulNot useful