+ All Categories
Home > Documents > Installing and Upgrading Avaya Aura Session Manager

Installing and Upgrading Avaya Aura Session Manager

Date post: 04-Apr-2018
Category:
Upload: bdlpfo
View: 260 times
Download: 1 times
Share this document with a friend

of 76

Transcript
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    1/76

    Installing and Upgrading Avaya Aura

    System Manager

    Release 6.0

    June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    2/76

    2010 Avaya Inc.

    All Rights Reserved.

    Notice

    While reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reserves theright to make changes and corrections to the information in thisdocument without the obligation to notify any person or organization ofsuch changes.

    Documentation disclaimerAvaya shall not be responsible for any modifications, additions, ordeletions to the original published version of this documentation unlesssuch modifications, additions, or deletions were performed by Avaya.End User agree 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, subsequentmodifications, additions or deletions to this documentation, to theextent made by End User.

    Link disclaimer

    Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation(s) provided by Avaya.

    Avaya is not responsible for the accuracy of any information, statementor content provided on these sites and does not necessarily endorsethe products, services, or information described or offered within them.

    Avaya does not guarantee that these links will work all the time and hasno control over the availability of the linked pages.

    Warranty

    Avaya provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition,

    Avayas standard warranty language, as well as information regardingsupport for this product, while under warranty, is available to Avayacustomers and other parties through the Avaya Support Web site:http://www.avaya.com/support . Please note that if you acquired theproduct from an authorized Avaya reseller outside of the United Statesand Canada, the warranty is provided to you by said Avaya reseller andnot by Avaya.

    Licenses

    THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE

    APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS 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. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINEDFROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN

    AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THERIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONEELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR

    AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OFYOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,DOWNLOADING OR USING THE SOFTWARE (HEREINAFTERREFERRED TO INTERCHANGEABLY AS YOU AND END USER),

    AGREE TO THESE TERMS AND CONDITIONS AND CREATE A

    BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (AVAYA).

    Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units ofcapacity for which the license is granted will be one (1), unless adifferent number of licenses or units of capacity is specified in theDocumentation or other materials available to End User. DesignatedProcessor means a single stand-alone computing device. Servermeans a Designated Processor that hosts a software application to be

    accessed by multiple users. Software means the computer programsin object code, originally licensed by Avaya and ultimately utilized byEnd User, whether as stand-alone products or pre-installed onHardware. Hardware means the standard hardware originally sold by

    Avaya and ultimately utilized by End User.

    Copyright

    Except where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation(s) and Product(s) providedby Avaya. All content on this site, the documentation(s) and theproduct(s) provided by Avaya including the selection, arrangement anddesign of the content is owned either by Avaya or its licensors and is

    protected by copyright and other intellectual property laws including thesui generis rights relating to the protection of databases. You may notmodify, copy, reproduce, republish, upload, post, transmit or distributein any way any content, in whole or in part, including any code andsoftware. Unauthorized reproduction, transmission, dissemination,storage, and or use without the express written consent of Avaya canbe a criminal, as well as a civil, offense under the applicable law.

    Third-party components

    Certain software programs or portions thereof included in the Productmay contain software distributed under third party agreements (ThirdParty Components), which may contain terms that expand or limitrights to use certain portions of the Product (Third Party Terms).Information regarding distributed Linux OS source code (for thoseProducts that have distributed the Linux OS source code), andidentifying the copyright holders of the Third Party Components and theThird Party Terms that apply to them is available on the Avaya Support

    Web site: http://www.avaya.com/support/Copyright/.

    Preventing toll fraud

    Toll fraud is the unauthorized use of your telecommunications systemby an unauthorized party (for example, a person who is not a corporateemployee, agent, subcontractor, or is not working on your company'sbehalf). Be aware that there can be a risk of toll fraud associated withyour system and that, if toll fraud occurs, it can result in substantialadditional charges for your telecommunications services.

    Avaya fraud intervention

    If you suspect that you are being victimized by toll fraud and you needtechnical assistance or support, call Technical Service Center TollFraud Intervention Hotline at +1-800-643-2353 for the United Statesand Canada. For additional support telephone numbers, see the AvayaSupport Web site: http://www.avaya.com/support/ . Suspected security

    vulnerabilities with Avaya products should be reported to Avaya bysending mail to: [email protected].

    Trademarks

    Avaya, the Avaya logo, Avaya Aura System Manager are eitherregistered trademarks or trademarks of Avaya Inc. in the United Statesof America and/or other jurisdictions.

    All other trademarks are the property of their respective owners.

    Downloading documents

    For the most current versions of documentation, see the Avaya SupportWeb site: http://www.avaya.com/support

    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 numberis 1-800-242-2121 in the United States. For additional supporttelephone numbers, see the Avaya Web site: http://www.avaya.com/support

    2 Installing and Upgrading Avaya Aura System Manager June 2010

    http://www.avaya.com/support/LicenseInfohttp://www.avaya.com/support/LicenseInfohttp://www.avaya.com/supporthttp://www.avaya.com/support/LicenseInfohttp://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/support/http://www.avaya.com/support/Copyright/http://www.avaya.com/support/LicenseInfohttp://www.avaya.com/support
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    3/76

    Contents

    Chapter 1: System Manager - installation requirements.......................................................5Introduction.......................................................................................................................................................5

    Hardware requirements.....................................................................................................................................5

    Chapter 2: Checklists and Worksheets...................................................................................7System Manager installation checklist..............................................................................................................7

    System Manager information worksheet...........................................................................................................7

    Chapter 3: Installing System Platform.....................................................................................9Preinstallation tasks for System Platform..........................................................................................................9

    Preinstallation checklist for System Platform............................................................................................9

    Registering the system...........................................................................................................................10

    Registering for PLDS..............................................................................................................................11

    Downloading software in PLDS..............................................................................................................12

    Verifying the downloaded ISO image.....................................................................................................12

    Writing the downloaded software to DVD...............................................................................................14

    Installing System Platform...............................................................................................................................15Installation checklist for System Platform...............................................................................................15

    Installation methods................................................................................................................................18

    Connecting your laptop to the server......................................................................................................18

    Starting the installation...........................................................................................................................20

    Selecting the type of keyboard...............................................................................................................22

    Verifying the System Platform image on the DVD..................................................................................23

    Configuring network settings for System Domain (Domain-0)................................................................24

    Configuring network settings for Console Domain.................................................................................26

    Configuring the time zone for the System Platform server.....................................................................28

    Configuring the date and time for the System Platform server...............................................................28

    Configuring System Platform passwords................................................................................................29

    Verifying installation of System Platform................................................................................................31

    Accessing System Platform....................................................................................................................32Installing a solution template...........................................................................................................................36

    Search Local and Remote Template field descriptions...........................................................................37

    Configuring the SAL gateway..........................................................................................................................39

    SAL.........................................................................................................................................................39

    Registering the system...........................................................................................................................39

    Configuring the SAL Gateway................................................................................................................40

    System Platform High Availability Failover......................................................................................................41

    High Availability Failover overview.........................................................................................................41

    Requirements for High Availability Failover............................................................................................42

    Prerequisites for configuring High Availability Failover...........................................................................43

    Configuring High Availability Failover.....................................................................................................43

    Configure Failover field descriptions......................................................................................................44

    Chapter 4: Upgrading System Platform................................................................................45Platform upgrade.............................................................................................................................................45

    Upgrading System Platform............................................................................................................................46

    Commit and Rollback......................................................................................................................................47

    Committing an upgrade...................................................................................................................................49

    Rolling back an upgrade.................................................................................................................................49

    Installing and Upgrading Avaya Aura System Manager June 2010 3

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    4/76

    Platform Upgrade field descriptions................................................................................................................49

    Upgrading System Platform on High Availability Systems..............................................................................51

    Methods for upgrading High Availability systems...................................................................................51

    Stop and start of High Availability for platform upgrades........................................................................51

    Stopping High Availability.......................................................................................................................51

    Starting High Availability Failover...........................................................................................................52

    Upgrading System Platform on both servers..........................................................................................52Upgrading System Platform on the preferred server only......................................................................53

    Chapter 5: Installing System Manager..................................................................................55Downloading System Manager from PLDS.....................................................................................................55

    Installing the System Manager template.........................................................................................................56

    Default Credentials.................................................................................................................................58

    Chapter 6: System Manager Upgrades..................................................................................59..................................................................................................................................................................... 0

    Performing load to load upgrade............................................................................................................59

    Performing System Manager Upgrade from Release 1.0 to 5.2.............................................................60

    Performing System Manager upgrade from Release 5.2 to 6.0.............................................................61

    Default credentials..................................................................................................................................62

    Chapter 7: Modifying Alarm ID and Managed Element ID...................................................63..................................................................................................................................................................... 0

    Modifying an Alarm ID............................................................................................................................63

    Modifying a Managed Element ID..........................................................................................................64

    Chapter 8: Generating Test Alarms........................................................................................65..................................................................................................................................................................... 0

    Generating a test alarm..........................................................................................................................66

    Chapter 9: Removing the System Manager template...........................................................67..................................................................................................................................................................... 0

    Chapter 10: High Availability support for System Manager................................................69..................................................................................................................................................................... 0

    Start and stop of High Availability Failover.............................................................................................70

    Prerequisites for configuring High Availability Failover...........................................................................70

    Configuring High Availability Failover.....................................................................................................71

    Configure Failover field descriptions......................................................................................................71

    Starting High Availability Failover...........................................................................................................72

    Stopping High Availability Failover.........................................................................................................72

    Index.........................................................................................................................................73

    4 Installing and Upgrading Avaya Aura System Manager June 2010

    http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    5/76

    Chapter 1: System Manager - installationrequirements

    Introduction

    The Avaya Aura System Manager delivers a set of shared management services which you

    can access using the System Manager common console.

    The System Manager Template is packaged and delivered in an ISO file. This template

    contains Red Hat Enterprise Linux 5.3 and System Manager installed on RHEL 5.3. Installingthe System Manager virtual appliance requires you to perform the following steps:

    1. Install System Platform.

    2. Install the System Manager virtual appliance on System Platform.

    Hardware requirements

    Install System Manager on either an Avaya S8510 server or an Avaya S8800 server, dependingon what you ordered. These servers arrive at the customers site with all the requiredcomponents and memory. Prior to installing System Manager on the server you have to installSystem Platform product on the hardware.

    Installing and Upgrading Avaya Aura System Manager June 2010 5

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    6/76

    System Manager - installation requirements

    6 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    7/76

    Chapter 2: Checklists and Worksheets

    System Manager installation checklist

    # Action Notes

    1 Download the System Platform 6build 11 ISO image and applicable

    patch from the Avaya PLDS Web site.

    Verify that the md5sum for the

    downloaded ISO matches the

    number mentioned on theAvaya PLDS Web site.

    2 Download the System Manager template

    present in the

    System_Manager_06_00_00.isofile from the Avaya PLDS Web site.

    Verify that the md5sum for the

    downloaded template matches

    the number mentioned on the

    PLDS site.

    3 Set up a DVD or USB flash drive to

    perform the System Platform installation

    from a DVD or USB flash drive.

    For more information on

    installing System Platform, see

    Chapter 3, Installing System

    Platform.

    4 Deploy the System Manager template on

    System Platform. For more information,see Installing System Manager template

    in Chapter 5, Installing System

    Manager.

    System Manager information worksheet

    The System Manager template deployment using the System Platform Console requires youto fill in several fields. Having the information available at the time of installation expedites the

    System Manager deployment and ensures accuracy. Print out the following tables and workwith your network administrator to fill in the appropriate value for each field displayed in thetables.

    Installing and Upgrading Avaya Aura System Manager June 2010 7

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    8/76

    For the System Manager Virtual Appliance

    Field Value Notes

    IP address Enter the IP address that is to be assigned to the

    System Manager virtual appliance on System

    Platform.

    Short

    Hostname

    Enter the short host name for the System Manager.

    Non-root User This is an optional field. Enter a non-root ID if you

    want to install using a non-root ID.

    Domain

    Name

    Enter the domain name for your setup. For example:

    production.mydomain.com

    For the Network Configurations

    Field Value Notes

    Gateway

    Address

    Enter the IP address of the server that has been set

    up as the gateway in your enterprise environment.

    Network Mask Enter the network mask value.

    DNS Enter the IP address of the Domain Name Server.

    Search String Enter the search string. The system uses this search

    string to resolve the domain names.

    Checklists and Worksheets

    8 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    9/76

    Chapter 3: Installing System Platform

    Preinstallation tasks for System Platform

    Preinstallation checklist for System Platform

    The preinstallation checklist given below will help to ensure that the installation is carried outefficiently. Before starting the installation, make sure that you complete the tasks from thepreinstallation checklist.

    No. Task Notes

    1 Complete and submit the Universal Install/

    SAL Product Registration Request form.

    When opening the Excel based form, click

    Enable Macros; otherwise, the form

    automation will not work. Submit the

    completed form using the built in e-mail

    button. See Registering the system on

    page 10.

    Note:

    Allow 48 business hours for a reply.

    Important:

    Make sure that you performthis task at least 48 hoursbefore installing SystemPlatform and any solutiontemplate.

    2 Gather the required information relating to

    installation, such as IP configuration

    information, DNS addresses, and NTP

    server addresses.

    See Installation worksheet for System

    Platform.

    3 Download the System Platform installer

    ISO image file from PLDS.See Downloading software in PLDS on

    page 12.

    4 Download the appropriate solution

    template and licenses from PLDS.

    Installing and Upgrading Avaya Aura System Manager June 2010 9

    http://-/?-http://-/?-http://-/?-
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    10/76

    No. Task Notes

    See Downloading software in PLDS on

    page 12.

    5 Verify that the downloaded ISO images

    match the images on the PLDS Web site.See Verifying the ISO image on a Linux-

    based computeron page 12 and Verifying

    the ISO image on a Windows-based

    computeron page 13.

    6 Write the ISO images to separate DVDs.

    See Writing the ISO image to DVD on

    page 14.

    Registering the systemRegistering System Platform and applications in the solution template ensures that Avaya hasa record of the system and it is ready for remote support if needed.

    Avaya assigns a Solution Element ID (SE ID) and Product ID to each SAL Gateway andmanaged device that is registered. In the context of System Platform, managed devices arethe applications that are included in a specific solution template. The SE ID makes it possiblefor Avaya Services or Avaya Partners to connect to the managed applications remotely. TheProduct ID is included in alarms that are sent to alarm receivers from the managed device.The Product ID identifies the device that generated the alarm. This data is critical for correctexecution of various Avaya business functions and tools.

    Registrations are performed in two stages: before installation of System Platform, the solutiontemplate, and SAL Gateway and after installation. The first stage of registration provides youwith the SE IDs and Product Identifications that you will need to install the products. For solutiontemplates that include Communication Manager, the first stage of registration also providesyou with the System ID (SID). The second stage of the registration makes alarming and remoteaccess possible.

    1. Download and follow the instructions in the registration form. This form is available

    at http://support.avaya.com. In the navigation pane, click More Resources >

    Equipment Registration (Partners only). At the bottom of the page, under Non-

    Regional (Product) Specific Documentation, click Universal Install/SAL Product

    Registration Request Form, or search Universal Install/SAL Product RegistrationRequest Form.

    The registration form consists of two pages.

    2. Complete the first page and submit it at least two business days before the planned

    installation date to avoid delays.

    Installing System Platform

    10 Installing and Upgrading Avaya Aura System Manager June 2010

    http://support.avaya.com/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    11/76

    You need to provide the following:

    Customer name

    Avaya Sold-to Number (customer number) where the products will be installed

    Contact information for the person to whom the registration information should

    be sent and whom Avaya can contact if any questions arise Products that are included in the solution template and supporting information

    as prompted by the form

    Avaya uses this information to register your system. When processing of the

    registration request is complete, Avaya sends you an e-mail with the SE IDs and

    Product ID numbers that you must enter in SAL Gateway to add managed devices.

    3. Complete and submit the second page after the installation is complete.

    Registering for PLDS

    1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site (https://

    plds.avaya.com).

    You will be redirected to the Single sign-on (SSO) Web site.

    2. Log in to SSO using SSO ID and Password.

    You will be redirected to the PLDS registration page.

    3. If you are registering: as anAvaya Partner, enter the Partner Link ID. If you do not know your Link

    ID, send an e-mail to [email protected].

    as a customer, enter one of the following:

    - Company Sold-To

    - Ship-To number

    - License Authorization Code (LAC)

    4. Click Submit.

    Avaya will send you the PLDS access confirmation within one business day.

    Preinstallation tasks for System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 11

    https://plds.avaya.com/https://plds.avaya.com/https://plds.avaya.com/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    12/76

    Downloading software in PLDS

    1. Type http://plds.avaya.com in your Web browser to access the Avaya PLDSWeb site.

    2. Enter your Login ID and password to log on to the PLDS Web site.

    3. Select Assets from the Home page and select View Downloads.

    4. Search for the downloads available using one of the following methods:

    By Actual Download name

    By selecting an Application type from the drop-down list

    By Download type

    By clicking Search Downloads

    5. Click the download icon from the appropriate download.

    6. When the confirmation box displays, select Click to download your file now.

    7. If you receive an error message, click on the message, install Active X, and continue

    with the download.

    8. When the security warning displays, click Install.

    When the install is complete, PLDS displays the downloads again with a checkmark

    next to the downloads which have been completed successfully.

    Verifying the downloaded ISO image

    Verifying the ISO image on a Linux-based computer

    Prerequisites

    Download any required software from PLDS.

    Use this procedure to verify that the md5 checksum of the downloaded ISO image matchesthe md5 checksum that is displayed for the ISO image on the PLDS Web site.

    Use this procedure if you downloaded ISO images to a Linux-based computer.

    Installing System Platform

    12 Installing and Upgrading Avaya Aura System Manager June 2010

    http://plds.avaya.com/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    13/76

    1. Entermd5sum filename, where filename is the name of the ISO image. Include

    the .iso file extension in the filename.

    2. 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.

    3. Ensure that both numbers are the same.

    4. If the numbers are different, download the ISO image again and reverify the md5

    checksum.

    Verifying the ISO image on a Windows-based computer

    Prerequisites

    Download any required software from PLDS.

    Use this procedure to verify that the md5 checksum of the downloaded ISO image matchesthe md5 checksum that is displayed for the ISO image on the PLDS Web site.

    Use this procedure if you downloaded ISO images to a Windows-computer.

    1. Download a tool to compute md5 checksums from one of the following Web sites:

    http://www.md5summer.org/

    http://zero-sys.net/portal/index.php?kat=70

    http://code.kliu.org/hashcheck/

    Note:

    Avaya has no control over the content published on these external sites. Pleaseuse the content only as reference.

    2. Run the tool on the downloaded ISO image and note the md5 checksum.

    3. 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.

    4. Ensure that both numbers are the same.

    5. If the numbers are different, download the ISO image again and reverify the md5

    checksum.

    Preinstallation tasks for System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 13

    http://zero-sys.net/portal/index.php?kat=70http://www.md5summer.org/http://code.kliu.org/hashcheck/http://zero-sys.net/portal/index.php?kat=70http://www.md5summer.org/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    14/76

    Writing the downloaded software to DVD

    DVD recommendations

    Avaya recommends use of high quality, write-once, blank DVDs, such as Verbatim DVD-R orDVD+R. Multiple rewrite DVDs are prone to error and should not be used.

    When writing the data to the DVD, Avaya recommends a slower write speed of 4X or at amaximum 8X. Attempting to write to the DVD at higher or the maximum speed rated on thedisc is likely to result in write errors.

    Note:

    If the software files you want to write on media are less than 680 Mb in size, you can usea CD instead of a DVD.

    Writing the ISO image to DVD

    Prerequisites

    1. Download any required software from PLDS.

    2. Verify that the md5 checksum of the downloaded ISO image matches the md5

    checksum that is displayed for the ISO image on the PLDS Web site.

    This procedure requires a computer or server that has a DVD writer and software that iscapable of writing ISO images to DVD.

    Important:

    When the ISO image is being written to the DVD, do not run other resource-intensiveapplications on the computer. Any application that uses the hard disk intensively can cause abuffer underrun or other errors, which can render the DVD useless.

    Write the ISO image of the installer to a DVD.

    Installing System Platform

    14 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    15/76

    Installing System Platform

    Installation checklist for System Platform

    Use this checklist to install System Platform.

    Important:

    If you are using the High Availability Failover option, install the same version of SystemPlatform on both servers.

    No. Task Notes

    1 If you are installing System Platform from a

    laptop, perform the following tasks:

    Ensure that a Telnet and Secure Shell

    application are installed on the laptop.

    Avaya supports use of the open source

    Telnet/SSH client application PuTTY.

    Configure the IP settings of the laptop for

    direct connection to the server.

    See Configuring the laptop for direct

    connection to the serveron page 18.

    Disable use of proxy servers in the Webbrowser on the laptop.

    See Disabling proxy servers in Internet

    Exploreron page 19 orDisabling proxy

    servers in Firefox on page 19 .

    2 Connect your laptop to the services port

    with an Ethernet crossover cable.

    If you do not have a crossover

    cable, you can use an IP hub.

    Note:

    Depending on the capabilitiesof the network interface card inyour laptop, you might be ableto use a straight-through cablefor this connection. See thedocumentation for your laptop.

    3 Turn on the server.

    4 Place the DVD into the DVD drive on the

    server.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 15

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    16/76

    No. Task Notes

    See Starting the installation from your

    laptop on page 20 orStarting the

    installation from the server console on

    page 21 depending on your selection of

    installation method.

    5 If using your laptop to install System

    Platform, verify the media within the

    System Platform installation wizard.

    If using the server console to install System

    Platform,

    enter the vspmediacheck command

    and press Enter.

    The vspmediacheck command verifies

    that the image on the System Platform DVD

    is not corrupt.

    See Starting the installation from your

    laptop on page 20 orStarting theinstallation from the server console on

    page 21 depending on your selection of

    installation method.

    6 If using your laptop to install System

    Platform, establish a Telnet connection to

    the server.

    See Starting the installation from your

    laptop on page 20.

    7 Select the required keyboard type.

    See Selecting the type of keyboard on

    page 22.

    8 Verify that the image on the System

    Platform DVD is not corrupt.

    See Verifying the System Platform image

    on the DVD on page 23.

    9 Configure the network settings for the

    System Domain (Domain-0).

    See Configuring network settings for

    System Domain (Domain-0) on page 24.

    10 Configure the network settings for the

    Console Domain.

    See Configuring network settings forConsole Domain on page 26.

    11 Configure the time zone for the System

    Platform server.

    See Configuring the time zone for the

    System Platform serveron page 28.

    Installing System Platform

    16 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    17/76

    No. Task Notes

    12 Configure the date and time or set up NTP

    server for the System Platform server.

    See Configuring the date and time for the

    System Platform serveron page 28.

    13 Configure the System Platform passwords.

    See Configuring System Platform

    passwords on page 29.

    14 Verify access to the System Platform Web

    Console.

    See Verifying installation of System

    Platform on page 31.

    15 Check for System Platform patches at

    http://support.avaya.com. Install any

    patches that are available.

    16 Install a solution template.See Installing a solution template on

    page 36.Important:

    If you are using the HighAvailability Failover option, donot install a solution templateon the server that will serve asstandby. If you do, you will notbe able to start High

    Availability Failover. If you areusing a bundled SystemPlatform installation (with asolution template), disable thetemplate installation on thestandby server. The solutiontemplate is propagated fromthe active node to the standbynode when you start High

    Availability Failover.

    17 Configure the SAL gateway for remote

    access and alarming.

    See SAL Gateway.

    18 If applicable, configure System Platform

    High Availability Failover.

    See Configuring High Availability

    Failoveron page 43.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 17

    http://-/?-http://support.avaya.com/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    18/76

    Installation methods

    You can install the System Platform software by using either a:

    Laptop connected to the services port on the server. Video monitor, keyboard, and mouse connected to the appropriate ports on the server.

    This option does not apply to the S8300D. To install to the S8300D, you must use a laptopconnected to the services port.

    Note:

    It is possible to complete the installation by using only a keyboard and monitor. If youdo not have a mouse, use the Tab key to navigate between fields.

    If you use a laptop to install the software, you must have a PuTTY SSH client and Telnetapplication installed on the laptop and Telnet must be enabled to load System Platform ISOfile. Make sure that you change the network settings on the laptop before connecting to the

    server.

    Connecting your laptop to the server

    Configuring the laptop for direct connection to the server

    You must manually configure the IP address, subnet mask, and default gateway of the laptopbefore you connect the laptop to the server.

    Note:

    The following procedure is for Windows XP. The procedure may differ slightly for otherversions of Windows.

    1. Click Start > Control Panel.

    2. Double click Network Connections > Local Area Connection.

    3. In the Local Area Connection Status dialog box, click Properties.

    4. In the This connection uses the following items box, click Internet Protocol

    (TCP/IP).

    5. Click Properties.

    6. In the Internet Protocol (TCP/IP) Properties dialog box, select Use the following

    IP address on the General tab.

    Installing System Platform

    18 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    19/76

    Warning:

    Do not click the Alternate Configuration tab.

    7. In the IP address field, type 192.11.13.5.

    8. In the Subnet mask field, type 255.255.255.252.

    9. In the Default gateway field, type 192.11.13.6.

    10. Click OK.

    Disabling proxy servers in Internet Explorer

    To connect directly to the services port, you must disable the proxy servers in your InternetExplorer Web browser.

    1. Open your Internet browser.

    2. Click Tools > Internet Options.

    3. Click the Connections tab.

    4. Click LAN Settings.

    5. Clear the Use a proxy server for your LAN option. Select the option when you

    have to enable the proxy server.

    6. Click OK to close each dialog box.

    Disabling proxy servers in Firefox

    To connect directly to the services port, you must disable the proxy servers in your Firefox Webbrowser.

    Note:

    This procedure is for Firefox on a Windows-based laptop. The procedure may differ slightly ifyour laptop is running Linux or another operating system.

    1. Open your Internet browser.

    2. Click Tools > Options.

    3. Select the Advanced option.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 19

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    20/76

    4. Click the Network tab.

    5. Click Settings.

    6. Select the No proxy option.

    7. Click OK to close each dialog box.

    Starting the installation

    Starting the installation from your laptop

    Prerequisites

    A Telnet/SSH application such as, PuTTY is installed on your laptop.

    IP settings of the laptop are configured for direct connection to the server.

    Use of proxy servers is disabled.

    Note:

    On S8510 and S8800 servers, eth1 is the services port. On S8300D server, eth0 is theservices port, which is on the front of the server face plate and is marked as 'SERVICES'.

    On S8800, eth1 is labelled as '2' as the IBM S8800 servers do not follow the traditionalnetwork port numbering convention.

    1. Connect your laptop to the services port with an Ethernet crossover cable.

    If you do not have a crossover cable, you can use an IP hub.

    Note:

    Depending on the capabilities of the network interface card in your laptop, youmight be able to use a straight-through cable for this connection. See thedocumentation for your laptop.

    2. Turn on the server.

    3. Insert the System Platform DVD in the server's DVD drive.

    The server boots from the DVD.

    4. Verify that the laptop can ping the service port by performing the following steps:

    a. Click Start > Run.

    b. Type ping -t 192.11.13.6

    Installing System Platform

    20 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    21/76

    Note:

    Allow sufficient time for the ping command to return continuous responsesbefore proceeding to the next step.

    5. Open a PuTTY session by performing the following steps:

    Important:

    If you use a Telnet client other than PuTTY, or if you forget to set the properterminal emulation for the PuTTY client, the system might not display theKeyboard Type screen correctly. This screen problem does not affect theinstallation.

    a. Open the PuTTY application.

    b. In the Host Name field, enter192.11.13.6.

    c. UnderConnection type, select Telnet.

    d. UnderWindow in the left navigation pane, select Translation.

    e. UnderReceived data assumed to be in which character set , select UTF-8from the list.

    f. Click Open to open a PuTTY session.

    The system displays the Keyboard Type screen.

    Next steps

    Select the required keyboard type. See Selecting the type of keyboard on page 22.

    Related topics:

    Connecting to the server through the services port on page 32

    Starting the installation from the server console

    Note:

    This procedure does not apply to embedded servers such as S8300D.

    Prerequisites

    Connect a USB keyboard, USB mouse, and video monitor to the server.

    1. Turn on the server.

    2. Insert the System Platform DVD in the server's DVD drive.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 21

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    22/76

    The server boots up from the System Platform DVD and displays the Avaya screen.

    3. Within 30 seconds of the system displaying the Avaya screen, type

    vspmediacheck at the boot prompt and press Enter.

    The vspmediacheck command verifies that the image on the System Platform

    DVD is not corrupt.

    Important:

    If you do not press Enteror type vspmediacheck within 30 seconds of thesystem displaying the Avaya screen, the system disables installation through theserver console and enables installation through the services port. The systemthen displays the Waiting for Telnet connection screen, so you can connect to theserver through Telnet. At this point, if you want to install through the serverconsole, reset the server to restart the installation.

    The system displays the Keyboard Type screen.

    Next stepsSelect the required keyboard type. See Selecting the type of keyboard on page 22.

    Selecting the type of keyboard

    On the Keyboard Type screen, select the type of keyboard that you have.

    Note:The supported keyboard types are sg-latin1, sk-qwerty, slovene, sv-latin1, trq, ua-utf, uk, and us.

    The CD Found screen is displayed if you:

    - are installing System Platform from the server console and entered the

    vspmediacheck command at the boot prompt, or

    - are installing System Platform from a laptop

    See Verifying the System Platform image on the DVD on page 23.

    The System Domain Network Configuration screen is displayed if you are

    installing System Platform from the server console and did not enter thevspmediacheckcommand at the boot prompt. See Configuring network settings

    for System Domain (Domain-0) on page 24.

    Installing System Platform

    22 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    23/76

    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 23.

    OR

    Configure the network settings for System Domain (Domain-0). See Configuring network

    settings for System Domain (Domain-0) on page 24

    Verifying the System Platform image on the DVD

    Use this procedure to verify that the System Platform image was copied correctly to the DVD.

    The CD Found screen is displayed if you:

    are installing System Platform from the server console and entered thevspmediacheckcommand at the boot prompt, or

    are installing System Platform from a laptop

    On the CD Found screen, use the Tab key to select OK to test the DVD, or select Skip

    to skip the test and begin the installation immediately.

    If you choose to test the DVD, the system displays another screen with a progress bar

    and the percentage of completion. After the test is complete, the system displays

    whether the image passed the test.

    Note:

    If the DVD you are using is corrupt, you must write a new DVD with the SystemPlatform image. Before using the new DVD, make sure that you restart the server.

    The System Domain Network Configuration screen is displayed.

    Next steps

    Configure the network settings for System Domain (Domain-0). See Configuring network

    settings for System Domain (Domain-0) on page 24.

    Configure the network settings for System Domain (Domain-0). See Configuring network

    settings for System Domain.

    Related topics:

    Writing the ISO image to DVD on page 14

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 23

    http://-/?-http://-/?-http://-/?-http://-/?-
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    24/76

    Configuring network settings for System Domain (Domain-0)

    1. On the System Domain Network Configuration screen, complete the following fields:

    Hostname. Enter a fully qualified domain name (FQDN), for example,

    SPDom0.mydomainname.com.

    Primary DNS

    (Optional) Secondary DNS

    2. Perform the following steps to configure the interface that is connected to thecustomer network:

    a. Use the Tab key to highlight the Physical Devices field.

    b. Complete the Static IP field.

    c. Modify the subnet mask if necessary. The server displays a default value of

    255.255.255.0.

    3. Complete the Default gateway IP field.

    4. Use the Tab key to highlight the IPv6 Enabled field. Press the Space bar to either

    enable or disable entering IP addresses in IPv6 format.

    Note:

    Messaging does not support IPv6. Make sure that it is disabled.

    5. If you have enabled IPv6, fill in the following fields:

    IPv6 Address

    Installing System Platform

    24 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    25/76

    IPv6 Prefix

    IPv6 Gateway

    6. Use the Tab key to highlight the Enable IP Forwarding field. 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).

    7. Use the Tab key to highlight OK and press Enterto accept the configuration.

    8. If IP forwarding is enabled, a confirmation message is displayed. Use the Tab key

    to highlight OK and press Enter.

    The System Platform Console Domain Network Configuration screen is displayed.

    Next steps

    Configure network settings for Console Domain. See Configuring network settings for Console

    Domain on page 26.

    Related topics:

    System Domain Network Configuration field descriptions on page 25

    System Domain Network Configuration field descriptions

    Name Description

    Hostname The host name for System Domain (Dom-0). This must be a fully

    qualified domain name (FQDN), for example,SPDom0.mydomainname.com.

    Primary DNS The primary DNS server address.

    Secondary DNS (Optional) The secondary DNS server address.

    Physical

    Devices

    This field displays the physical Ethernet interface (NIC) that connects

    to the customer network. You must configure this interface for IP.

    The specific Ethernet interface number depends on the server model

    being used.

    Static IP The static IP address for the Ethernet interface that connects to the

    customer network.

    Subnet Mask The subnet mask for the Ethernet interface that connects to thecustomer network.

    Default gateway

    IP

    The default gateway IP address.

    This default gateway IP address will be used for all the virtual machines

    if you do not specify gateway IP addresses for them.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 25

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    26/76

    Name Description

    IPv6 Enabled The indicator whether or not the IP addresses required by System

    Platform needs to be IPv6-compliant.

    Messaging does not support IPv6. Make sure that it is disabled.

    Application Enablement Services 5.2.2 does not support IPv6.

    IPv6 Address The IPv6compliant IP address of System Domain.Messaging does not support IPv6.

    IPv6 Prefix The IPv6 prefix forIPv6 Address.

    Messaging does not support IPv6.

    IPv6 Gateway The IPv6compliant gateway IP address of System Domain.

    Messaging does not support IPv6.

    Enable IP

    Forwarding

    The indicator whether or not IP forwarding is enabled.

    An asterisk on the left of the field denotes that IP forwarding is enabled.

    IP forwarding enables access to System Platform through the services

    port.

    Configuring network settings for Console Domain

    1. On the VSP Console Domain Network Configuration screen, complete the following

    fields to set up the Console Domain network:

    Hostname. Enter a fully qualified domain name (FQDN), for example,

    SPCdom.mydomainname.com.

    Static IP

    Installing System Platform

    26 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    27/76

    2. Select OK and press Enterto accept the configuration and display the Time Zone

    Selection screen.

    Next steps

    Configure the time zone for the System Platform server. See Configuring the time zone for the

    System Platform serveron page 28.

    Related topics:

    System Platform Console Domain Network Configuration field descriptions on page 27

    System Platform Console Domain Network Configuration field descriptions

    Name Description

    Hostname The host name for the Console Domain. This must be a fully qualified domain

    name (FQDN), for example, SPCdom.mydomainname.com.

    Static IP The IP address for the Console Domain.

    Note:

    The Console Domain does not have a physical interface. It has a virtualinterface that uses the physical interface in System Domain (Domain-0). AsSystem Domain acts like a bridge, the IP address that you enter here must

    be a valid IP address. Further, the Console Domain must be on the samenetwork as System Domain (Domain-0).

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 27

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    28/76

    Configuring the time zone for the System Platform server

    1. On the Time Zone Selection screen, select the time zone in which the server islocated.

    Note:

    On the main server, you need to select the time zone relevant to the serverlocation. In the case of ESS or LSP, you must set up the time zone, which is sameas that of the main server. In a failover situation, the ESS or the LSP provide thecorrect time information to display on the phones with the help of the time zoneand the translation information.

    2. Select OK and press Enterto accept the configuration and display the Date/Time

    and NTP setup screen.

    Next steps

    Configure date and time for the System Platform server. See Configuring the date and time for

    the System Platform serveron page 28.

    Configuring the date and time for the System Platform server

    1. If you are not using an NTP server, set the current date and time on the Date/Time and NTP setup screen.

    Tip:

    Avaya recommends that you use an NTP server within your network tosynchronize the time of the System Platform server.

    Note:

    Ensure that the time set here is correct. Changing the time in a virtual machineenvironment requires rebooting the virtual machines. Therefore, Avayarecommends setting the time correctly on this screen during the installation

    2. If you are using an NTP server, perform the following steps on the Date/Time andNTP setup screen:

    a. Select Use NTP if you are using one or more NTP (Network Time Protocol)

    servers.

    Installing System Platform

    28 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    29/76

    b. In the NTP serverfields, enter the DNS name or the IP address of your

    preferred NTP server(s).

    3. Select OK and press Enterto accept the configuration and display the Passwords

    screen.

    Next steps

    Configure System Platform passwords. See Configuring System Platform passwords on

    page 29.

    Configuring System Platform passwords

    Prerequisites

    Configure the date and time for the System Platform server.

    1. On the Passwords screen, enter new passwords for all logins. You must enter each

    password twice to ensure that you are not making any mistakes in typing.

    If you do not enter new passwords, the defaults are used. The following table shows

    the default password for each login.

    Login Default password Capability

    root root01 Advanced administrator

    admin admin01 Advanced administrator

    cust cust01 Normal administrator

    manager (for ldap) root01 Administrator for the

    System Platform local

    LDAP directory.

    System Platform uses a

    local LDAP directory to

    store login and password

    details. Use this login and

    password to log in to the

    local LDAP directory.

    This login does not have

    permissions to access

    the System Platform Web

    Console.

    Important:

    Avaya highly recommends that you enter new passwords instead of using thedefault passwords. Make a careful note of the passwords that you set for all

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 29

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    30/76

    logins. Passwords must be at least six characters long. Avaya recommends usinguppercase and lowercase alphabetic characters and at least one numeral orspecial character.

    Note:

    The Avaya Services craft login uses Access Security Gateway (ASG) forauthentication. If you are using the craft login, you must have an ASG tool togenerate a response for the challenge that is generated by the login page. Many

    ASG tools are available such as Avaya Token Mobile, Avaya Web Mobile, andSite Manager. The first two ASG tools must be able to reach the ASG managerservers behind the Avaya firewall. An Avaya Services representative will use SiteManager to pull the keys specific to a site before visiting that site. At the site, the

    Avaya Services representative will use those keys to generate the response forthe challenge generated by the login page.

    2. Select OK and press Enterto accept the passwords and continue the installation.

    Result

    The installation takes approximately 5 minutes. During this time, you can see the Package

    Installation page with progress bars, followed by the Running page, as the system completes

    the post-install scripts. After the installation is completed, the system ejects the DVD and

    reboots the server. If you are installing from server console, the system displays the Linux login

    page for System Domain (Domain-0) after the reboot.

    Important:

    If the DVD does not eject automatically, eject if manually. The system restarts the installationif the DVD is not ejected.

    Next steps

    Verify System Platform installation. See Verifying installation of System Platform on page

    31.

    Related topics:

    Passwords field descriptions on page 30

    Passwords field descriptions

    Note:

    Passwords must be at least six characters long. Avaya recommends using uppercase andlowercase alphabetic characters and at least one numeral or special character.

    Name Description

    root Password The password for the root login.

    admin Password The password for the admin login.

    Installing System Platform

    30 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    31/76

    Name Description

    cust Password The password for the cust login.

    ldap Password The password for the ldap login.

    System Platform uses a local LDAP directory to store login and

    password details. Use this login and password to log in to the local

    LDAP directory. This login does not have permissions to access theSystem Platform Web Console.

    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.

    Important:

    You must wait approximately 15 to 20 minutes after the installation finishes to perform thisprocedure. The first boot process for Console Domain can take up to 20 minutes. You cannotaccess Console Domain until the first boot process is finished.

    After completing installation of System Platform, perform this procedure to check for problemswith the installation.

    1. Access the System Platform Web Console. SeeAccessing the System Platform

    Web Console on page 33.

    2. Perform the following steps to log in to Console Domain as admin:

    a. Start PuTTY from your computer.

    b. In the Host Name (or IP Address) field, type the IP address of Console

    Domain.

    c. In the Connection type field, select SSH, and then click Open.

    d. When prompted, log in as admin, and type the password that you entered for

    the admin login during System Platform installation.

    e. Type exit to exit Console Domain.

    3. Perform the following steps to log in to Console Domain as cust:

    a. Start PuTTY from your computer.

    b. In the Host Name (or IP Address) field, type the IP address of Console

    Domain.

    c. In the Connection type field, select SSH, and then click Open.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 31

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    32/76

    d. When prompted, log in as cust, and type the password that you entered for

    the cust login during System Platform installation.

    e. Type exit to exit Console Domain.

    Important:

    If you cannot log in to Console Domain as admin orcust or access the SystemPlatform Web Console, contact Tier 3 Engineering.

    Accessing System Platform

    Connecting to the server through the services port

    Prerequisites

    A Telnet/SSH application such as, PuTTY is installed on your laptop.

    IP settings of the laptop are configured for direct connection to the server.

    Use of proxy servers is disabled.

    1. Connect your laptop to the services port with an Ethernet crossover cable.

    If you do not have a crossover cable, you can use an IP hub.

    Note:Depending on the capabilities of the network interface card in your laptop, youmight be able to use a straight-through cable for this connection. See thedocumentation for your laptop.

    2. Start a PuTTY session.

    3. In the Host Name (or IP Address) field, type 192.11.13.6.

    The system assigns the IP address 192.11.13.6 to the services port.

    4. For Connection type, select SSH.

    5. In the Port field, type 22.

    6. Click Open.

    Note:

    The system displays the PuTTY Security Alert window the first time you connectto the server.

    7. ClickYes to accept the server's host key and display the PuTTY window.

    Installing System Platform

    32 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    33/76

    8. Log in as craft.

    9. When you finish the session, type exit and press Enterto close PuTTY.

    Enabling IP forwarding to access System Platform through the services port

    To access System Platform Web Console through the services port, you must enable IPforwarding on System Domain (Dom-0) . You can set the IP forwarding status as enabled ordisabled during installation of System Platform. If you disable IP forwarding during installationand later want to enable it, perform the following procedure. For security reasons, alwaysdisable IP forwarding after finishing your task.

    1. To enable IP forwarding:

    a. Start an SSH session.b. Log in to System Domain (Domain-0) as admin.

    c. In the command line, typeservice_port_access enable and press Enter.

    2. For security reasons, always disable IP forwarding after finishing your task. Perform

    the following tasks to disable IP forwarding:

    a. Start an SSH session.

    b. Log in to System Domain (Domain-0) as admin.

    c. In the command line, type ip_forwarding disable and press Enter.

    Accessing the System Platform Web Console

    Prerequisites

    If you are performing this task from a laptop that is connected to the services port, enable IP

    forwarding.

    You can access the System Platform Web Console from a Web browser on your laptop oranother computer connected to the same network as the System Platform server.

    1. Open a compatible Internet browser on your computer.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 33

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    34/76

    Currently, System Platform supports Microsoft Internet Explorer 7 and Firefox 2 and

    3.

    2. Type the URL: https://ipaddress, where ipaddress is the IP address of the

    Console Domain that you configured during installation of System Platform.

    Note:This is a secure site. If you get a certificate error, then follow the instructions inyour browser to install a valid certificate on your computer.

    3. Enter a valid User ID.

    Note:

    If you use an Avaya services login that is Access Security Gateway (ASG)-protected, you must have an ASG tool to generate a response for the challengethat is generated by the login page. Many ASG tools are available such as AvayaToken Mobile, Avaya Web Mobile, and Site Manager. The first two ASG toolsmust be able to reach the ASG manager servers behind the Avaya firewall. An

    Avaya Services representative will use Site Manager to pull the keys specific to

    a site before visiting that site. At the site, the Avaya Services representative willuse those keys to generate the response for the challenge generated by the loginpage.

    4. Click Continue.

    5. Enter a valid Password.

    6. Click Log On.

    The system displays the License Terms page when you log in for the first time.

    7. Click I Accept to accept the end user license agreement.

    The system displays the Virtual Machine List page in the System Platform Web

    Console.

    Installing System Platform

    34 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    35/76

    Related topics:

    Enabling IP forwarding to access System Platform through the services port on page 33

    Accessing the command line for System Domain

    If you have physical access to the system, you can log in to the system directly. When youconnect to the services port, you are connected to System Domain. Alternatively, use an SSH(Secure Shell) client such as PuTTY to set up a remote connection from your computer. Afterlogging in, the system prompts you with the Linux command prompt.

    1. Start PuTTY from your computer.

    2. In the Host Name (or IP Address) field, type the IP address of Console Domain.

    Tip:

    You can obtain the IP address of Console Domain by typing one of the followingcommands:

    grep cdom.vsp /etc/hosts

    ping cdom.vsp

    3. In the Connection type field, select SSH, and then click Open.

    4. When prompted, log in as admin.

    5. Once logged in, type the following command to log in as the root user: su root

    6. Enter the password for the rootuser.

    Tip:

    To access Console Domain from System Domain, type xm list, note the ID forudom, and then type xm consoleudom-id. When prompted, login as admin.Then type su root and enter the root password to log in as root.

    To exit Console Domain and return to System Domain, press Control+].

    7. After performing the necessary tasks, type exit to exit root login.

    8. Type exit again to exit System Domain.

    Accessing the command line for Console Domain

    1. Start PuTTY from your computer.

    2. In the Host Name (or IP Address) field, type the IP address of Console Domain.

    Installing System Platform

    Installing and Upgrading Avaya Aura System Manager June 2010 35

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    36/76

    Tip:

    You can obtain the IP address of Console Domain (cdom) from the VirtualMachine Management page of the Web Console. In the navigation pane of theWeb Console, click Virtual Machine Management > Manage.

    3. In the Connection type field, select SSH, and then click Open.

    4. When prompted, log in as admin.

    5. Once logged in, type the following command to log in as the root user: su root

    6. Enter the password for the rootuser.

    7. After performing the necessary tasks, type exit to exit root login.

    8. Type exit again to exit Console Domain.

    Installing a solution template

    Important:

    If you are using the High Availability Failover option, do not install a solution template on theserver that will serve as standby. If you do, you will not be able to start High AvailabilityFailover. If you are using a bundled System Platform installation (with a solution template),disable the template installation on the standby server. The solution template is propagatedfrom the active node to the standby node when you start High Availability Failover.

    1. Log in to the System Platform Web Console as admin.

    2. Click Virtual Machine Management > Solution template.

    The system displays the Search Local and Remote Template page. Use this page

    to select a template that you want to run on System Platform.

    3. Select a location from the list in the Install Templates From box.

    Note:

    If the template installation files are located on a different server (for example,Avaya PLDS or HTTP), you may be required to configure a proxy depending on

    your network.4. Click Search to display a list of template descriptor files (each available template

    has one template descriptor file).

    5. On the Select Template page, click the required template, and then click Select to

    continue.

    Installing System Platform

    36 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    37/76

    The system displays the Template Details page with information on the selected

    template and its Virtual Appliances.

    6. Click Install to start the template installation.

    If the template you selected supports an Electronic Pre-installation Worksheet

    (EPW), the system prompts you to continue without an EPW or to provide an EPW

    file. The system also prompts you with pages that require your input such as IPaddresses for the applications that are included in the template. These pages vary

    depending on the template that you are installing. If you provided an EPW file, some

    of these pages may be pre-populated with data from the EPW.

    See the respective template documentation for detailed instructions.

    If you are installing a Communication Manager template, make sure that you

    remove the CD/DVD from the CD-ROM/DVD tray after the template installation

    completes.

    Here are the approximate installation durations for the Communication Manager

    templates:

    CM_Duplex: 15 minutes

    CM_Simplex: 25 minutes

    CM_onlyEmbed: 50 minutes

    CM_SurvRemote: 30 minutes

    CM_SurvRemoteEmbed: 65 minutes

    Next steps

    If you are following this document as part of upgrading your Communication Manager template,

    refer to Upgrading to Avaya AuraTM

    Communication Managerfor further instructions.

    Search Local and Remote Template field descriptions

    Name Description

    Install

    Template

    From

    Lets you select from the available options to locate a template and install

    it on System Platform. The 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 must enter an Avaya SSO login and

    password. The list will contain all the templates to which your company is

    entitled. 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. You

    may hold the mouse pointer over the selection to view more information

    about the sold-to number.

    HTTP

    Installing a solution template

    Installing and Upgrading Avaya Aura System Manager June 2010 37

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    38/76

    Name Description

    The template files are located in a HTTP server. You must enter the

    template URL information.

    SP Server

    The template files are located in the /vsp-template file system in the

    Console Domain of the System Platform server.SP CD/DVD

    The template files are located on a CD or DVD in the CD/DVD drive on the

    server..

    SP USB Disk

    The template files are located on a USB flash drive connected to the server.

    SSO Login Active only when you select the Avaya Downloads (PLDS) option to

    search for a template.

    Login id for logging on to Single Sign On.

    SSO

    Password

    Active only when you select the Avaya Downloads (PLDS) option to

    search for a template.

    Password for Single Sign On.

    Button descriptions

    Name Description

    Upgrade Upgrades the installed solution templates from the selected template

    location option.

    Configure Proxy Active only when you select the HTTP option to search for a solution

    template.

    Lets you configure a proxy for the HTTP address.

    A proxy may also be required in order for Secure Access Link (SAL)

    and alarming to access the internet.

    Install Installs the solution template.

    Delete Installed

    Template

    Deletes the currently installed template.

    Installing System Platform

    38 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    39/76

    Configuring the SAL gateway

    SAL

    System Platform includes Avaya's Secure Access Link (SAL) Gateway to manage servicedelivery (alarming and remote access). SAL Gateway is a software application that:

    Facilitates remote access to support personnel and tools that are needed to accesssupported devices

    Collects and sends alarm information to a Secure Access Concentrator Core Server, onbehalf of the managed devices

    Provides a user interface to configure its interfaces to managed devices, ConcentratorRemote and Core Servers, and other settings

    SAL requires an upload bandwidth (customer to Avaya) of at least 90 kB/s (720 kb/s) withlatency no greater than 150 ms (round trip.)

    During the installation of System Platform, you must register the system (System Platform,solution templates, and SAL Gateway) and configure SAL for the customer's network.

    Important:

    For Avaya to provide support, Avaya Partners or their customers must ensure that SAL isregistered and configured properly. Avaya support will be delayed or not possible if SAL isnot properly implemented.

    Avaya Partners must provide their own B2B VPN connection (or other IP-based connectivity) todeliver remote services. SAL does not support modem connections.

    You can launch the SAL Gateway management portal from within System Platform.

    Registering the system

    Registering System Platform and applications in the solution template ensures that Avaya hasa record of the system and it is ready for remote support if needed.

    Avaya assigns a Solution Element ID (SE ID) and Product ID to each SAL Gateway and

    managed device that is registered. In the context of System Platform, managed devices arethe applications that are included in a specific solution template. The SE ID makes it possiblefor Avaya Services or Avaya Partners to connect to the managed applications remotely. TheProduct ID is included in alarms that are sent to alarm receivers from the managed device.The Product ID identifies the device that generated the alarm. This data is critical for correctexecution of various Avaya business functions and tools.

    Registrations are performed in two stages: before installation of System Platform, the solutiontemplate, and SAL Gateway and after installation. The first stage of registration provides you

    Configuring the SAL gateway

    Installing and Upgrading Avaya Aura System Manager June 2010 39

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    40/76

    with the SE IDs and Product Identifications that you will need to install the products. For solutiontemplates that include Communication Manager, the first stage of registration also providesyou with the System ID (SID). The second stage of the registration makes alarming and remoteaccess possible.

    1. Download and follow the instructions in the registration form. This form is availableat http://support.avaya.com. In the navigation pane, click More Resources >

    Equipment Registration (Partners only). At the bottom of the page, under Non-

    Regional (Product) Specific Documentation, click Universal Install/SAL Product

    Registration Request Form, or search Universal Install/SAL Product Registration

    Request Form.

    The registration form consists of two pages.

    2. Complete the first page and submit it at least two business days before the planned

    installation date to avoid delays.

    You need to provide the following:

    Customer name

    Avaya Sold-to Number (customer number) where the products will be installed

    Contact information for the person to whom the registration information should

    be sent and whom Avaya can contact if any questions arise

    Products that are included in the solution template and supporting information

    as prompted by the form

    Avaya uses this information to register your system. When processing of the

    registration request is complete, Avaya sends you an e-mail with the SE IDs and

    Product ID numbers that you must enter in SAL Gateway to add managed devices.

    3. Complete and submit the second page after the installation is complete.

    Configuring the SAL Gateway

    To configure the SAL Gateway for the customer's network and System Platform, follow

    the instructions that are provided inAdministering SAL on Avaya AuraTMSystem

    Platform. This document is available on http://support.avaya.com/css/P8/documents/100069101.

    Note:

    For an understanding of how to administer the customer's network to support SAL,follow the instructions provided in Secure Access Link 1.8 SAL Gateway

    Installing System Platform

    40 Installing and Upgrading Avaya Aura System Manager June 2010

    http://support.avaya.com/css/P8/documents/100069101http://support.avaya.com/css/P8/documents/100069101http://support.avaya.com/css/P8/documents/100069101http://support.avaya.com/css/P8/documents/100069101http://support.avaya.com/
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    41/76

    Implementation Guide. This document is available on http://www.avaya.com/support.

    System Platform High Availability Failover

    High Availability Failover overview

    The System Platform High Availability Failover is an optional feature aimed at providing service

    continuity. However, it does not support critical reliability. Moreover, certain solution templates

    (Communication Manager is one such template) do not support this feature.

    Note:

    System Platform High Availability Failover does not support IPv6 and cannot be configuredwith IPv6 addresses.

    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 theresources and determine which node runs the resources. If the system has no issues, andresources could run on either node, both machines have the same score. Thus SystemPlatform uses the term preferred node for the machine that should run the resources whenthe system has no issues. The preferred node has a small score benefit. So if both machines

    are booted at the same time, the preferred node will run resources. The node from which youconfigure High Availability Failover is designated the preferred node. If you stop High

    Availability Failover, the currently active node becomes the preferred node.

    No auto-failback

    High Availability Failover does not use auto-failback to migrate resources back to the preferrednode when the resources are running on the standby node and the preferred node becomesavailable again. Switching servers disrupts service, and if both servers are healthy, thenrunning on the preferred node offers no increased benefit. If you want to migrate resourcesback to the preferred node after a failover or a switchover, you can do so by using the ManualSwitchoveroption in the Failover menu at the most suitable time.

    Expected failover/switchover times

    High Availability Failover uses 30 seconds as a timeout interval after which the standby nodewill declare the active node dead and start resources (even though the active node may benot accessible, not running or blocked). Note that System Platform does not provide any Webinterface to modify this interval.

    System Platform High Availability Failover

    Installing and Upgrading Avaya Aura System Manager June 2010 41

    http://www.avaya.com/supporthttp://www.avaya.com/support
  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    42/76

    For manual switchover or when the system initiates a preemptive failover, the total timebetween the start of the command and activating the standby node includes a gracefulshutdown and restart of all resources:

    Stop of resources Up to 5 minutes.

    Start of resourcesUp to 5 minutes.

    Resulting longest switchover timeUp to 10 minutes.

    For failover due to total failure of the active node, the total time between the start of the outageand the time when all resources are running on the standby node includes a detection intervaltimeout and the start of all resources:

    Detect active node failure30 seconds.

    Start of resourcesUp to 5 minutes.

    Resulting longest switchover timeUp to 5.5 minutes.

    Note:

    The switchover time is approximate and varies depending on the hardware running SystemPlatform with no templates. The switchover is further delayed by the following factors:

    The system runs complex templates.

    The system shutdown was not proper. Therefore, the system performs an FSCK (FileSystem Check) as it boots up and starts the virtual machines.

    Requirements for High Availability Failover

    The requirements for High Availability Failover are as follows:

    Two servers with exactly the same hardware configuration. The standby server cannothave less memory, number of processors, total disk space or free disk space than theprimary server.

    The hardware must be supported by System Platform.

    The servers must have a spare Gigabit network interface to be dedicated exclusively toHigh Availability Failover services. The servers must be connected on the same ports onboth machines.

    Both the servers must be in the same subnet.

    Both servers must be in close proximity so that they can be connected with the crossovercable. The Ethernet specification limit for this distance is 100 meters.

    The same version of System Platform must be installed on the active and standby nodes.

    Do not install a template on the standby node. If you do so, you will not be able to startHigh Availability Failover. If you are using a bundled System Platform installation (with asolution template), disable the template installation on the standby server. The solutiontemplate is propagated from the active node to the standby node when you start High

    Availability Failover.

    Installing System Platform

    42 Installing and Upgrading Avaya Aura System Manager June 2010

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    43/76

    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 onboth machines.

    Ensure that your network gateway replies to ICMP requests from the System Platformnodes. The default network gateway is the ping target of the High Availability Failoverheartbeat. 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 > Failoverto 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 speedof the synchronization with a slider bar on the console. The default value of thisrate is 30 MB/s. If you set the value too high, it may affect the performance of thevirtual machines running on the active server.

    System Platform High Availability Failover

    Installing and Upgrading Avaya Aura System Manager June 2010 43

  • 7/30/2019 Installing and Upgrading Avaya Aura Session Manager

    44/76

    Configure Failover field descriptions

    Name Description

    Remote cdom IP address IP Address of Console Domain on the standby node.

    Remote cdom user name User name for Console Domain on the standby node.

    Remote cdom password Password for Console Domain on the standby node.

    Primary network interface Network interf


Recommended