deploying avaya aura® applications from system manager

Deploying Avaya Aura® applications fromSystem Manager

Release 7.0.1Issue 3

February 2017

© 2015-2017, Avaya, Inc.All Rights Reserved.

NoticeWhile 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 reservesthe right to make changes and corrections to the information in thisdocument without the obligation to notify any person or organizationof such changes.

Documentation disclaimer“Documentation” means information published in varying mediumswhich may include product information, operating instructions andperformance specifications that are generally made available to usersof products. Documentation does not include marketing materials.Avaya shall not be responsible for any modifications, additions, ordeletions to the original published version of Documentation unlesssuch modifications, additions, or deletions were performed by or onthe express behalf of Avaya. End User agrees to indemnify and holdharmless Avaya, Avaya's agents, servants and employees against allclaims, lawsuits, demands and judgments arising out of, or inconnection with, subsequent modifications, additions or deletions tothis documentation, to the extent made by End User.

Link disclaimerAvaya is not responsible for the contents or reliability of any linkedwebsites referenced within this site or Documentation provided byAvaya. Avaya is not responsible for the accuracy of any information,statement or content provided on these sites and does notnecessarily endorse the products, services, or information describedor offered within them. Avaya does not guarantee that these links willwork all the time and has no control over the availability of the linkedpages.

WarrantyAvaya provides a limited warranty on Avaya hardware and software.Refer to your sales agreement to establish the terms of the limitedwarranty. In addition, Avaya’s standard warranty language, as well asinformation regarding support for this product while under warranty isavailable to Avaya customers and other parties through the AvayaSupport website: https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010 under the link“Warranty & Product Lifecycle” or such successor site as designatedby Avaya. Please note that if You acquired the product(s) from anauthorized Avaya Channel Partner outside of the United States andCanada, the warranty is provided to You by said Avaya ChannelPartner and not by Avaya.

“Hosted Service” means an Avaya hosted service subscription thatYou acquire from either Avaya or an authorized Avaya ChannelPartner (as applicable) and which is described further in Hosted SASor other service description documentation regarding the applicablehosted service. If You purchase a Hosted Service subscription, theforegoing limited warranty may not apply but You may be entitled tosupport services in connection with the Hosted Service as describedfurther in your service description documents for the applicableHosted Service. Contact Avaya or Avaya Channel Partner (asapplicable) for more information.

Hosted ServiceTHE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYAHOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYACHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USEFOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYAWEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFOUNDER THE LINK “Avaya Terms of Use for Hosted Services” ORSUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND AREAPPLICABLE TO ANYONE WHO ACCESSES OR USES THEHOSTED SERVICE. BY ACCESSING OR USING THE HOSTEDSERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ONBEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU AREDOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLYAS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IFYOU ARE ACCEPTING THE TERMS OF USE ON BEHALF ACOMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THATYOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESETERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR

IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOUMUST NOT ACCESS OR USE THE HOSTED SERVICE ORAUTHORIZE ANYONE TO ACCESS OR USE THE HOSTEDSERVICE.

LicensesTHE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (AvayaProducts)” OR SUCH SUCCESSOR SITE AS DESIGNATED BYAVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASEDFROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYACHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIALAGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWAREWAS OBTAINED FROM ANYONE OTHER THAN AVAYA, ANAVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYARESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOUAND ANYONE ELSE USING OR SELLING THE SOFTWAREWITHOUT A LICENSE. BY INSTALLING, DOWNLOADING ORUSING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOMYOU ARE INSTALLING, DOWNLOADING OR USING THESOFTWARE (HEREINAFTER REFERRED TOINTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TOTHESE TERMS AND CONDITIONS AND CREATE A BINDINGCONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants You a license within the scope of the license typesdescribed below, with the exception of Heritage Nortel Software, forwhich the scope of the license is detailed below. Where the orderdocumentation does not expressly identify a license type, theapplicable license will be a Designated System License. Theapplicable number of licenses and units of capacity for which thelicense is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the documentation or othermaterials available to You. “Software” means computer programs inobject code, provided by Avaya or an Avaya Channel Partner,whether as stand-alone products, pre-installed on hardware products,and any upgrades, updates, patches, bug fixes, or modified versionsthereto. “Designated Processor” means a single stand-alonecomputing device. “Server” means a Designated Processor thathosts a software application to be accessed by multiple users.“Instance” means a single copy of the Software executing at aparticular time: (i) on one physical machine; or (ii) on one deployedsoftware virtual machine (“VM”) or similar deployment.

License type(s)Designated System(s) License (DS). End User may install and useeach copy or an Instance of the Software only on a number ofDesignated Processors up to the number indicated in the order.Avaya may require the Designated Processor(s) to be identified inthe order by type, serial number, feature key, Instance, location orother specific designation, or to be provided by End User to Avayathrough electronic means established by Avaya specifically for thispurpose.

Concurrent User License (CU). End User may install and use theSoftware on multiple Designated Processors or one or more Servers,so long as only the licensed number of Units are accessing and usingthe Software at any given time. A “Unit” means the unit on whichAvaya, at its sole discretion, bases the pricing of its licenses and canbe, without limitation, an agent, port or user, an e-mail or voice mailaccount in the name of a person or corporate function (e.g.,webmaster or helpdesk), or a directory entry in the administrativedatabase utilized by the Software that permits one user to interfacewith the Software. Units may be linked to a specific, identified Serveror an Instance of the Software.

Database License (DL). End User may install and use each copy oran Instance of the Software on one Server or on multiple Serversprovided that each of the Servers on which the Software is installedcommunicates with no more than one Instance of the samedatabase.

CPU License (CP). End User may install and use each copy orInstance of the Software on a number of Servers up to the number

https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010

https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010

https://support.avaya.com/LicenseInfo


indicated in the order provided that the performance capacity of theServer(s) does not exceed the performance capacity specified for theSoftware. End User may not re-install or operate the Software onServer(s) with a larger performance capacity without Avaya’s priorconsent and payment of an upgrade fee.

Named User License (NU). You may: (i) install and use each copy orInstance of the Software on a single Designated Processor or Serverper authorized Named User (defined below); or (ii) install and useeach copy or Instance of the Software on a Server so long as onlyauthorized Named Users access and use the Software. “NamedUser”, means a user or device that has been expressly authorized byAvaya 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 voicemail account in the name of a person or corporate function, or adirectory entry in the administrative database utilized by the Softwarethat permits one user to interface with the Software.

Shrinkwrap License (SR). You may install and use the Software inaccordance with the terms and conditions of the applicable licenseagreements, such as “shrinkwrap” or “clickthrough” licenseaccompanying or applicable to the Software (“Shrinkwrap License”).

Heritage Nortel Software“Heritage Nortel Software” means the software that was acquired byAvaya as part of its purchase of the Nortel Enterprise SolutionsBusiness in December 2009. The Heritage Nortel Software is thesoftware contained within the list of Heritage Nortel Products locatedat https://support.avaya.com/LicenseInfo under the link “HeritageNortel Products” or such successor site as designated by Avaya. ForHeritage Nortel Software, Avaya grants Customer a license to useHeritage Nortel Software provided hereunder solely to the extent ofthe authorized activation or authorized usage level, solely for thepurpose specified in the Documentation, and solely as embedded in,for execution on, or for communication with Avaya equipment.Charges for Heritage Nortel Software may be based on extent ofactivation or use authorized as specified in an order or invoice.

CopyrightExcept where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, Hosted Service,or hardware provided by Avaya. All content on this site, thedocumentation, Hosted Service, and the product provided by Avayaincluding the selection, arrangement and design of the content isowned either by Avaya or its licensors and is protected by copyrightand other intellectual property laws including the sui generis rightsrelating to the protection of databases. You may not modify, copy,reproduce, republish, upload, post, transmit or distribute in any wayany content, in whole or in part, including any code and softwareunless expressly authorized by Avaya. Unauthorized reproduction,transmission, dissemination, storage, and or use without the expresswritten consent of Avaya can be a criminal, as well as a civil offenseunder the applicable law.

VirtualizationThe following applies if the product is deployed on a virtual machine.Each product has its own ordering code and license types. Note thateach Instance of a product must be separately licensed and ordered.For example, if the end user customer or Avaya Channel Partnerwould like to install two Instances of the same type of products, thentwo products of that type must be ordered.

Third Party Components“Third Party Components” mean certain software programs orportions thereof included in the Software or Hosted Service maycontain software (including open source software) distributed underthird party agreements (“Third Party Components”), which containterms regarding the rights to use certain portions of the Software(“Third Party Terms”). As required, information regarding distributedLinux OS source code (for those products that have distributed LinuxOS source code) and identifying the copyright holders of the ThirdParty Components and the Third Party Terms that apply is availablein the products, Documentation or on Avaya’s website at: https://support.avaya.com/Copyright or such successor site as designatedby Avaya. The open source software license terms provided as ThirdParty Terms are consistent with the license rights granted in theseSoftware License Terms, and may contain additional rights benefitingYou, such as modification and distribution of the open source

software. The Third Party Terms shall take precedence over theseSoftware License Terms, solely with respect to the applicable ThirdParty Components to the extent that these Software License Termsimpose greater restrictions on You than the applicable Third PartyTerms.

The following applies only if the H.264 (AVC) codec is distributed withthe product. THIS PRODUCT IS LICENSED UNDER THE AVCPATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF ACONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVEREMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITHTHE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVCVIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN APERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEOPROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE ISGRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEGLA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Service ProviderTHE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’SHOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCTOR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTSSUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICEPROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLYFROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNELPARTNER’S HOSTING OF AVAYA PRODUCTS MUST BEAUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTEDPRODUCTS USE OR EMBED CERTAIN THIRD PARTYSOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFTSOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER ISREQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLELICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’SEXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTYSUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAYA CHANNELPARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBEDTHE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THEAVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREESTHE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANYAND ALL RELATED FEES AND/OR ROYALTIES. THE G.729CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC ISLICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FORTHE PERSONAL USE OF A CONSUMER OR OTHER USES INWHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD(“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WASENCODED BY A CONSUMER ENGAGED IN A PERSONALACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDERLICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTEDOR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONALINFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECSMAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Compliance with LawsYou acknowledge and agree that it is Your responsibility forcomplying with any applicable laws and regulations, including, but notlimited to laws and regulations related to call recording, data privacy,intellectual property, trade secret, fraud, and music performancerights, in the country or territory where the Avaya product is used.

Preventing Toll Fraud“Toll Fraud” is the unauthorized use of your telecommunicationssystem by an unauthorized party (for example, a person who is not acorporate employee, agent, subcontractor, or is not working on yourcompany's behalf). Be aware that there can be a risk of Toll Fraudassociated with your system and that, if Toll Fraud occurs, it canresult in substantial additional charges for your telecommunicationsservices.

Avaya Toll Fraud interventionIf You suspect that You are being victimized by Toll Fraud and Youneed technical assistance or support, call Technical Service CenterToll Fraud Intervention Hotline at +1-800-643-2353 for the UnitedStates and Canada. For additional support telephone numbers, see


https://support.avaya.com/Copyright

https://support.avaya.com/Copyright

HTTP://WWW.MPEGLA.COM

http://www.sipro.com/contact.html



the Avaya Support website: https://support.avaya.com or suchsuccessor site as designated by Avaya.

Security VulnerabilitiesInformation about Avaya’s security support policies can be found inthe Security Policies and Support section of https://support.avaya.com/security.

Suspected Avaya product security vulnerabilities are handled per theAvaya Product Security Support Flow (https://support.avaya.com/css/P8/documents/100161515).

Downloading DocumentationFor the most current versions of Documentation, see the AvayaSupport website: https://support.avaya.com, or such successor siteas designated by Avaya.

Contact Avaya SupportSee the Avaya Support website: https://support.avaya.com forproduct or Hosted Service notices and articles, or to report a problemwith your Avaya product or Hosted Service. For a list of supporttelephone numbers and contact addresses, go to the Avaya Supportwebsite: https://support.avaya.com (or such successor site asdesignated by Avaya), scroll to the bottom of the page, and selectContact Avaya Support.

TrademarksThe trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation, Hosted Service(s), and product(s) providedby Avaya are the registered or unregistered Marks of Avaya, itsaffiliates, its licensors, its suppliers, or other third parties. Users arenot permitted to use such Marks without prior written consent fromAvaya or such third party which may own the Mark. Nothingcontained in this site, the Documentation, Hosted Service(s) andproduct(s) should be construed as granting, by implication, estoppel,or otherwise, any license or right in and to the Marks without theexpress written permission of Avaya or the applicable third party.

Avaya and Avaya Aura® are registered trademarks of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners.Linux® is the registered trademark of Linus Torvalds in the U.S. andother countries.

https://support.avaya.com

https://support.avaya.com/security

https://support.avaya.com/security

https://support.avaya.com/css/P8/documents/100161515

https://support.avaya.com/css/P8/documents/100161515




Contents

Chapter 1: Introduction............................................................................................................ 9Purpose.................................................................................................................................. 9Prerequisites........................................................................................................................... 9Change history........................................................................................................................ 9

Chapter 2: Avaya Aura® overview......................................................................................... 11Avaya Aura® Virtualized offers................................................................................................ 11

Appliance Virtualization Platform overview......................................................................... 11Fresh deployment of Avaya Aura® applications........................................................................ 13Solution Deployment Manager................................................................................................ 13

Solution Deployment Manager overview............................................................................ 13Solution Deployment Manager client................................................................................. 14Solution Deployment Manager.......................................................................................... 20

Virtual machine management................................................................................................. 22Utility Services in the Avaya Aura® Virtualized Appliance offer................................................... 23

Chapter 3: Planning and configuration................................................................................. 25Supported servers................................................................................................................. 25Software requirements........................................................................................................... 25

Chapter 4: Preinstallation tasks............................................................................................ 27Deployment checklist............................................................................................................. 27Accessing Solution Deployment Manager................................................................................ 29Installing Appliance Virtualization Platform............................................................................... 30Configuring servers preinstalled with Appliance Virtualization Platform...................................... 32Uploading a file to the software library..................................................................................... 35Downloading the OVA file to System Manager......................................................................... 36

Chapter 5: Deploying Avaya Aura® applications................................................................. 37Managing the location............................................................................................................ 37

Viewing a location........................................................................................................... 37Adding a location............................................................................................................. 37Editing the location.......................................................................................................... 38Deleting a location........................................................................................................... 38VM Management field descriptions................................................................................... 38New and Edit location field descriptions............................................................................. 43

Managing the host................................................................................................................. 44Adding an ESXi host........................................................................................................ 44Editing an ESXi host........................................................................................................ 45Installing the Appliance Virtualization Platform patch from Solution Deployment Manager .... 45Changing the network parameters for an Appliance Virtualization Platform host................... 47Changing the network settings for an Appliance Virtualization Platform host from SolutionDeployment Manager...................................................................................................... 48

February 2017 Deploying Avaya Aura® applications 5Comments on this document? [email protected]

mailto:[email protected]?subject=Deploying Avaya Aura® applications

Changing the password for an Appliance Virtualization Platform host.................................. 51Enabling and disabling SSH on Appliance Virtualization Platform from SolutionDeployment Manager...................................................................................................... 52Enabling and disabling SSH on Appliance Virtualization Platform from System ManagerCLI................................................................................................................................. 52Changing the IP address and default gateway of the host................................................... 53Shutting down the Appliance Virtualization Platform host.................................................... 54Restarting the Appliance Virtualization Platform host.......................................................... 55Deleting an ESXi host...................................................................................................... 55Mapping the ESXi host to an unknown location.................................................................. 55New and Edit host field descriptions.................................................................................. 56Change Network Parameters field descriptions.................................................................. 56Host Network / IP Settings field descriptions...................................................................... 57Change Password field descriptions................................................................................. 58Update field descriptions.................................................................................................. 59

Managing the virtual machine................................................................................................. 59Deploying the System Manager OVA file by using the Solution Deployment Manager client...................................................................................................................................... 59VM Deployment field descriptions..................................................................................... 61Installing service packs and software patches on System Manager by using the SolutionDeployment Manager client.............................................................................................. 64

Managing the virtual machine................................................................................................. 65Deploying the Utility Services OVA file ............................................................................. 65Deploying an OVA file for an Avaya Aura® application........................................................ 67Installing software patches............................................................................................... 69Editing a virtual machine.................................................................................................. 71Deleting a virtual machine................................................................................................ 72Changing the network parameters of Appliance Virtualization Platform and Avaya Aura®

applications..................................................................................................................... 73Updating Services Port Static Routing on an Avaya Aura® application................................. 74Starting a virtual machine from Solution Deployment Manager............................................ 75Stopping a virtual machine from Solution Deployment Manager.......................................... 75Restarting a virtual machine from Solution Deployment Manager........................................ 76VM Deployment field descriptions..................................................................................... 76VM Deployment Configuration and Network Parameters field descriptions........................... 80Update Static Routing field descriptions............................................................................ 82Installed Patches field descriptions................................................................................... 83Update VM field descriptions............................................................................................ 83Reestablish Connection field descriptions.......................................................................... 84Network parameter update for Avaya Aura® applications.................................................... 84

Certificate validation.............................................................................................................. 85Certification validation...................................................................................................... 85Generating and accepting certificates............................................................................... 87Updating the certificate on the ESXi host from VMware...................................................... 88

Contents



Managing certificates for existing hosts............................................................................. 89Generating new self-signed certificates for the ESXi host................................................... 90

Managing vCenter................................................................................................................. 91Adding a vCenter to Solution Deployment Manager........................................................... 91Editing vCenter............................................................................................................... 92Deleting vCenter from Solution Deployment Manager......................................................... 92Map vCenter field descriptions.......................................................................................... 93New vCentre and Edit vCentre field descriptions................................................................ 94

Monitoring a host and virtual machine..................................................................................... 95Monitoring a host ............................................................................................................ 95Monitoring a virtual machine............................................................................................. 95

Chapter 6: Installing software patches, service packs, and feature packs forapplications............................................................................................................................. 96

Installing software patches..................................................................................................... 96Installed Patches field descriptions......................................................................................... 98

Chapter 7: Out of Band Management configuration.......................................................... 100Avaya Aura® Out of Band Management................................................................................. 100Appliance Virtualization Platform Out of Band Management.................................................... 101Out of Band Management in Virtualized Environment............................................................. 103Utility Services Out of Band Management.............................................................................. 103System Manager Out of Band Management.......................................................................... 104

Out of Band Management in System Manager................................................................. 104Configuring Out of Band Management on System Manager.............................................. 105Configuring Out of Band Management on System Manager in the Geographic Redundancysetup............................................................................................................................ 106

Communication Manager Out of Band Management.............................................................. 108Detailed description of Out of Band Management............................................................. 108Out of Band Management management administration..................................................... 108Screens for administering Out-of-Band management....................................................... 108Administering the Out of Band Management of management data..................................... 109Adding a static route between the Out-of-Band management interface and the enterprisenetwork........................................................................................................................ 110

Session Manager Out of Band Management ports................................................................. 111Application Enablement Services Out of Band Management................................................... 111Out of Band Management in Avaya Breeze™......................................................................... 112Out of Band Management in SAL.......................................................................................... 113

Chapter 8: Post Installation Verification............................................................................. 114Verifying the installation of System Manager.......................................................................... 114Post installation checklist..................................................................................................... 114Verifying the connections..................................................................................................... 115

Chapter 9: Postinstallation tasks........................................................................................ 116Loading a customer-specific authentication file...................................................................... 116Downloading and installing an authentication file on the Avaya Aura® application..................... 117

Contents



Chapter 10: Resources......................................................................................................... 119Documentation.................................................................................................................... 119

Finding documents on the Avaya Support website........................................................... 120Training.............................................................................................................................. 120Viewing Avaya Mentor videos............................................................................................... 122Support.............................................................................................................................. 122

Glossary................................................................................................................................. 123

Contents



Chapter 1: Introduction

PurposeThis document contains installation, configuration, initial administration, and basic maintenancechecklist and procedures for deploying applications in Avaya Aura® Virtualized Appliance onAppliance Virtualization Platform by using Avaya Aura® System Manager Solution DeploymentManager.

This document is intended for people who install and configure a verified Avaya Aura® applicationreference configuration at a customer site.

PrerequisitesBefore you deploy the product, ensure that you have the following knowledge, skills, and tools:

Knowledge• Avaya Aura® releases• Linux® operating system• VMware® and virtualized environment

Skills• VMware® and virtualized environment

Tools• Avaya supported servers or VMware® supported servers• Solution Deployment Manager client if System Manager is unavailable or unreachable• System Manager virtual machine resource requirements for each profile.• Configuration tools and utilities

Change historyThe following changes have been made to this document since the last issue:



Issue Date Summary of changes3.0 February 2017 Added the reference of the Avaya Aura® Release Notes document in the

“Deployment checklist” section for deploying Avaya Aura® applications.2.0 May 2016 • Added procedures for installing the Release 7.0.1 feature pack on

Release 7.0.

• Added procedures for the following in VM Management:

- Enabling and disabling SSH on Appliance Virtualization Platform.

- Changing network settings that includes, changing VLAN ID, NICspeed, and NIC team and unteaming for an Appliance VirtualizationPlatform host.

- Restarting the Appliance Virtualization Platform host.

- Shutting down the Appliance Virtualization Platform host.

- Viewing the job history of all operations that are performed on VMManagement.

- Updating the license status of hosts and virtual machines state.

- Removing the Appliance Virtualization Platform patch.

- Changing the IP address and default gateway of the host.

- Validating the certificates.

• Cleaning up the current pending or pause state of applications duringupgrade.

• Added procedure for installing custom patches for Avaya Aura®

applications.

• Added flexibility to select application and data port numbers during theSolution Deployment Manager client installation.

• Added support for Dell™ PowerEdge™ R630 and HP ProLiant DL360G9 common servers.

• Added Out of Band Management configuration chapter.

Introduction



Chapter 2: Avaya Aura® overview

Avaya Aura® Virtualized offersStarting with Release 7.0, Avaya Aura® supports the following two Avaya virtualization offers basedon VMware:

• Avaya Aura® Virtualized Appliance (VA) - Avaya-provided server, Avaya ApplianceVirtualization Platform, based on the customized OEM version of VMware® ESXi 5.5.

• Avaya Aura® Virtualized Environment (VE) - Customer-provided VMware infrastructure

The virtualization offers, provides the following benefits:

• Simplifies IT management using common software administration and maintenance.• Requires fewer servers and racks which reduces the footprint.• Lowers power consumption and cooling requirements.• Enables capital equipment cost savings.• Lowers operational expenses.• Uses standard operating procedures for both Avaya and non-Avaya products.• Deploys Avaya Aura® virtual products in a virtualized environment on Avaya provided servers

or customer-specified servers and hardware.• Business can scale rapidly to accommodate growth and to respond to changing business

requirements

Related linksAppliance Virtualization Platform overview on page 11

Appliance Virtualization Platform overviewFrom Release 7.0, Avaya uses the VMware®-based Avaya Appliance Virtualization Platform toprovide virtualization for Avaya Aura® applications in Avaya Aura® Virtualized Appliance offer.

Avaya Aura® Virtualized Appliance offer includes:

• Common Servers: Dell™ PowerEdge™ R610, Dell™ PowerEdge™ R620, HP ProLiant DL360 G7,HP ProLiant DL360p G8, Dell™ PowerEdge™ R630, and HP ProLiant DL360 G9

• S8300D and S8300E

Appliance Virtualization Platform is the customized OEM version of VMware® ESXi 5.5. WithAppliance Virtualization Platform, customers can run any combination of supported applications on



Avaya-supplied servers. Appliance Virtualization Platform provides greater flexibility in scalingcustomer solutions to individual requirements.

From Release 7.0, Appliance Virtualization Platform replaces System Platform.

Avaya Aura® Release 7.0.1 supports the following applications on Appliance Virtualization Platform:

• Utility Services 7.0.1• System Manager 7.0.1• Session Manager 7.0.1• Branch Session Manager 7.0.1• Communication Manager 7.0.1• Application Enablement Services 7.0.1• WebLM 7.0.1• Avaya Breeze™ 3.1.1• SAL 2.5• Communication Manager Messaging 7.0• Avaya Aura® Media Server 7.7.0.292 (SP3)• Avaya Scopia® 8.3.5

Avaya Aura® overview



• Avaya Proactive Contact 5.1.2

For more information about installing Avaya Proactive Contact and administering ApplianceVirtualization Platform with Avaya Proactive Contact, see the Avaya Proactive Contactdocumentation.

Related linksAvaya Aura Virtualized offers on page 11

Fresh deployment of Avaya Aura® applicationsIn Avaya Aura® Virtualized Appliance model, for fresh deployments, Avaya Aura® is available to end-users through a set of Avaya-supplied common servers. Avaya Aura® Virtualized Applianceisprepackaged with the virtualization software, and delivered to customers in a ready-to-run state.

In a customer-provided environment, VMware user can install Avaya Aura® applications by usingvCenter that VMware provides.

Solution Deployment Manager

Solution Deployment Manager overviewSolution Deployment Manager is a centralized software management solution in System Managerthat provides deployments, upgrades, migrations, and updates to Avaya Aura® 7.0 applications.Solution Deployment Manager supports the operations on customer Virtualized Environment andAvaya Aura® Virtualized Appliance model.

Solution Deployment Manager provides the combined capabilities that Software Management,Avaya Virtual Application Manager, and System Platform provided in earlier releases.

Note:In Release 7.0.1, Solution Deployment Manager does not support migration of VirtualizedEnvironment-based 6.x applications to Release 7.0.1 in customer Virtualized Environment. UsevSphere Client to migrate to customer Virtualized Environment.

Release 7.0 and later supports a standalone version of Solution Deployment Manager, the SolutionDeployment Manager client. For more information, see Using the Solution Deployment Managerclient.

System Manager is the primary management solution for Avaya Aura® 7.0 and later applications.

System Manager with the Solution Deployment Manager runs on:

• Avaya Aura® Virtualized Appliance: Contains a server, Appliance Virtualization Platform, andAvaya Aura® application OVA. Appliance Virtualization Platform includes a VMware ESXi 5.5hypervisor.

Fresh deployment of Avaya Aura® applications



From Release 7.0, Appliance Virtualization Platform replaces System Platform.• Customer-provided Virtualized Environment solution: Avaya Aura® applications are deployed

on customer-provided, VMware® certified hardware.

With Solution Deployment Manager, you can perform the following operations in VirtualizedEnvironment and Avaya Aura® Virtualized Appliance models:

• Deploy Avaya Aura® applications.• Upgrade and migrate Avaya Aura® applications.• Download Avaya Aura® applications.• Install service packs, feature packs, and software patches for the following Avaya Aura®

applications:

- Communication Manager and associated devices, such as gateways, media modules, andTN boards.

- Session Manager- Branch Session Manager- Utility Services- Appliance Virtualization Platform, the ESXi host that is running on the Avaya Aura®

Virtualized Appliance.

The upgrade process from Solution Deployment Manager involves the following key tasks:

• Discover the Avaya Aura® applications.• Refresh applications and associated devices, and download the necessary software

components.• Run the preupgrade check to ensure successful upgrade environment.• Upgrade Avaya Aura® applications.• Install software patch, service pack, or feature pack on Avaya Aura® applications.

For more information about the setup of the Solution Deployment Manager functionality that is partof System Manager 7.x, see Avaya Aura® System Manager Solution Deployment Manager Job-Aid.

Solution Deployment Manager clientFor the initial System Manager deployment or when System Manager is inaccessible, you can usethe Solution Deployment Manager client. The client can reside on the computer of the technician.The Solution Deployment Manager client provides the functionality to install the OVAs on an Avaya-provided server or customer-provided Virtualized Environment.

A technician can gain access to the user interface of the Solution Deployment Manager client fromthe computer or web browser.

The Solution Deployment Manager client runs on Windows 7 64-bit, Windows 8 64-bit, andWindows 10 64-bit.




Use the Solution Deployment Manager client to:

• Deploy System Manager and Avaya Aura® applications on Avaya appliances and VirtualizedEnvironment.

• Upgrade System Platform-based System Manager.• Install System Manager software patches, service packs, and feature packs.• Install Appliance Virtualization Platform patches.• Restart and shutdown the Appliance Virtualization Platform host.• Start, stop, and restart a virtual machine.• Change the footprint of Avaya Aura® applications that support dynamic resizing. For example,

Session Manager and Avaya Breeze™.

Note:You can deploy or upgrade the System Manager virtual machine only by using the SolutionDeployment Manager client.

Figure 1: Solution Deployment Manager client dashboard

Related linksCapability comparison between System Manager Solution Deployment Manager and the SolutionDeployment Manager client on page 15Installing the Solution Deployment Manager client on your computer on page 16Accessing the Solution Deployment Manager client dashboard on page 19Solution Deployment Manager client capabilities on page 19

Capability comparison between System Manager Solution DeploymentManager and the Solution Deployment Manager client

Centralized Solution Deployment Manager Solution Deployment Manager clientManage virtual machine lifecycle Manage virtual machine lifecycleDeploy Avaya Aura® applications Deploy Avaya Aura® applications

Table continues…




Centralized Solution Deployment Manager Solution Deployment Manager clientDeploy hypervisor patches only for ApplianceVirtualization Platform

Deploy hypervisor patches only for ApplianceVirtualization Platform

Upgrade Avaya Aura® applications

Release 7.x supports upgrades from Linux-based orSystem Platform-based to Virtualized Environment orAppliance Virtualization Platform. Release 7.0.1does not support Virtualized Environment toVirtualized Environment upgrades.

Upgrade System Platform-based System Manager

Install software patches for Avaya Aura® applicationsexcluding System Manager application

Install System Manager patches

Discover Avaya Aura® applications Deploy System ManagerAnalyze Avaya Aura® applications -Create and use the software library -

Related linksSolution Deployment Manager client on page 14

Installing the Solution Deployment Manager client on your computerAbout this taskIn Avaya Aura® Virtualized Appliance offer, when the centralized Solution Deployment Manager onSystem Manager is unavailable, use the Solution Deployment Manager client to deploy the AvayaAura® applications.

You can use the Solution Deployment Manager client to install software patches and hypervisorpatches.

Use the Solution Deployment Manager client to deploy, upgrade, and update System Manager.

Note:Click Next only once, and wait for the installer to load the next screen.

Before you begin1. If an earlier version of the Solution Deployment Manager client is running on the computer,

remove the older version from Control Panel > Programs > Programs and Features.

If you are unable to uninstall, see Uninstalling the Solution Deployment Manager client.2. Ensure that Windows 7, Windows 8.1 64-bit, or Windows 10 64-bit operating system is

installed on the computer.

Tip:On Computer, right-click properties, and ensure that Windows edition section displaysthe version of Windows operating system.

3. Ensure that at least 5 GB of disk space is available at the location where you want to installthe client.




Tip:Using the Windows file explorer, click Computer, and verify that the Hard Disk Drivessection displays the available disk space available.

4. To avoid port conflict, stop any application server that is running on your computer.

Tip:From the system tray, open the application service monitor, select the application serverthat you want to stop, and click Stop.

5. Ensure that the firewall allows the ports that are required to install the Solution DeploymentManager client installation and use the Solution Deployment Manager functionality.

6. Ensure that ports support Avaya Aura® 7.0.1 supported browsers.7. Close all applications that are running on your computer.8. Do not set CATALINA_HOME as environment variable on the computer where you install the

Solution Deployment Manager client.

Tip:On Computer, right-click properties, and perform the following:

a. In the left navigation pane, click Advanced system settings.b. On the System Properties dialog box, click Advanced tab, and click Environment

Variables.c. Verify the system variables.

9. Ensure that the computer on which the Solution Deployment Manager client is running isconnected to the network.

Operations that you perform might fail if the computer is not connected to the network.

Procedure1. Download the Avaya_SDMClient_win64_7.0.1.0.0620319_44.zip file from the

Avaya PLDS website at https://plds.avaya.com/.

On the Avaya PLDS website, at https://plds.avaya.com/, click Support by Products >Downloads, and provide the product System Manager, and version as 7.0.x.

2. Copy the zip file, and extract to a location on your computer by using the WinZip application.

You can also copy the zip file to your software library directory, for example, c:/tmp/Aura.

3. Right click on the executable, and select Run as administrator to run theAvaya_SDMClient_win64_7.0.1.0.0620319_44.exe file.

The system displays the Avaya Solution Deployment Manager screen.

4. On the Welcome page, click Next.

5. On the License Agreement page, read the License Agreement, and if you agree to its terms,click I accept the terms of the license agreement and click Next.



https://plds.avaya.com/

https://plds.avaya.com/


6. On the Install Location page, perform one of the following:

• To install the Solution Deployment Manager client in the system-defined folder, clickRestore Default Folder.

• To specify a different location for installation, click Choose and browse to an empty folder.

7. Click Next.

8. On the Preinstallation Summary page, review the information, and click Next.

9. On the User Input page, perform the following:

a. To start the Solution Deployment Manager client at the start of the system, select theAutomatically start SDM service at startup check box.

b. To change the default directory, in Select Location of Software Library Directory, clickChoose and select a directory.

The system saves the artifacts in the specified directory. During deployments, you canselect the OVA file from the directory.

c. In Data Port No, select the appropriate port from the range 1527 through 1627.

d. In Application Port No, select the appropriate port from the range 443 through 543.

e. (Optional) Click Reset All to Default.

10. On the Summary and Validation page, verify the product information and the systemrequirements.

The system performs the feasibility checks, such as disk space and memory. If therequirements are not met, the system displays an error message. To continue with theinstallation, make the disk space, memory, and the ports available.

11. Click Install.

12. To exit the installer, on the Install Complete page, click Done.

The installer creates a shortcut on the desktop.

13. To start the client, click the Solution Deployment Manager client icon, .

Next steps• Configure the laptop to get connected to the services port if you are using the services port to

install.• Connect the Solution Deployment Manager client to Appliance Virtualization Platform through

the customer network or services port.

For more information, see “Methods to connect Solution Deployment Manager client toAppliance Virtualization Platform”.





Accessing the Solution Deployment Manager client dashboardAbout this task

Note:If you perform deploy, upgrade, and update operations from the Solution Deployment Managerclient, ignore the steps that instruct you to access System Manager Solution DeploymentManager and the related navigation links.

ProcedureTo start the Solution Deployment Manager client, perform one of the following:

• Click Start > All Programs > Avaya, and click SDM Client > Avaya SDM Client.

•Click .


Solution Deployment Manager client capabilitiesThe Solution Deployment Manager client provides the following capabilities and functionality:

• Runs on the technician computer on the following operating systems:

- Windows 7, 64-bit Professional or Enterprise

- Windows 8.1, 64-bit Professional or Enterprise

• Supports the same web browsers as System Manager Release 7.0.1.

• Provides the user interface with similar look and feel as the central Solution DeploymentManager in System Manager Release 7.0.1.

• Supports deploying the System Manager OVA. The Solution Deployment Manager client is theonly option to deploy System Manager.

• Supports Flexible footprint feature. The size of the virtual resources depends on the capacityrequirements of the Avaya Aura® applications.

• Defines the physical location, Appliance Virtualization Platform or ESXi host, and discoversvirtual machines that are required for application deployments and virtual machine life cyclemanagement.

• Manages lifecycle of the OVA applications that are deployed on the ESXi host. The lifecycleincludes start, stop, reset virtual machines, and establishing trust for virtual machines.

• Deploys the Avaya Aura® applications that can be deployed from the central SolutionDeployment Manager for Avaya Aura® Virtualized Appliance and customer VirtualizedEnvironment. You can deploy one application at a time.

• Configures application and networking parameters required for application deployments.

• Supports the local computer or an HTTP URL to select the application OVA file for deployment.You do not need access to PLDS.




• Supports changing the hypervisor IP address on Appliance Virtualization Platform.

• Supports installing patches for the hypervisor on Appliance Virtualization Platform.

• Supports installing software patches, service packs, and feature packs only for SystemManager.

Avaya Aura® applications must use centralized Solution Deployment Manager from SystemManager to install software patches, service packs, and feature packs.


Solution Deployment ManagerThe Solution Deployment Manager capability simplifies and automates the deployment and upgradeprocess.

With Solution Deployment Manager, you can deploy the following Avaya Aura® applications inRelease 7.0.1:

• Utility Services 7.0.1• System Manager 7.0.1• Session Manager 7.0.1• Branch Session Manager 7.0.1• Communication Manager 7.0.1• Application Enablement Services 7.0.1• WebLM 7.0.1• Avaya Breeze™ 3.1.1• SAL 2.5• Communication Manager Messaging 7.0• Avaya Aura® Media Server 7.7.0.292 (SP3)• Avaya Scopia® 8.3.5• Avaya Proactive Contact 5.1.2

For more information about installing Avaya Proactive Contact and administering ApplianceVirtualization Platform with Avaya Proactive Contact, see the Avaya Proactive Contactdocumentation.

Note:You must deploy the Release 7.0 OVA, and then install the Release 7.0.1 file on the AvayaAura® Release 7.0 application.




With Solution Deployment Manager, you can migrate, upgrade, and update the followingapplications:

• Linux-based Communication Manager 5.x and the associated devices, such as Gateways, TNboards, and media modules.

Note:In bare metal Linux-based deployments, the applications are directly installed on the serverand not as a virtual machine.

• Linux-based Session Manager 6.x• System Platform-based Communication Manager

- Duplex CM Main / Survivable Core with Communication Manager- Simplex CM Main / Survivable Core with Communication Manager, Communication

Manager Messaging, and Utility Services- Simplex Survivable Remote with Communication Manager, Branch Session Manager, and

Utility Services- Embedded CM Main with Communication Manager, Communication Manager Messaging,

and Utility Services- Embedded Survivable Remote with Communication Manager, Branch Session Manager,

and Utility Services• System Platform-based Branch Session Manager

- Simplex Survivable Remote with Communication Manager, Branch Session Manager, andUtility Services

- Embedded Survivable Remote with Communication Manager, Branch Session Manager,and Utility Services

Note:However, you must manually migrate Services virtual machine that is part of the template.

The centralized deployment and upgrade process provide better support to customers who want toupgrade their systems to Avaya Aura® Release 7.0.1. The process reduces the upgrade time anderror rate.

Solution Deployment Manager dashboardYou can gain access to the Solution Deployment Manager dashboard from the System Managerweb console or by installing the Solution Deployment Manager client.




Solution Deployment Manager capabilitiesWith Solution Deployment Manager, you can perform deployment and upgrade-related tasks byusing the following links:

• Upgrade Release Setting: To select Release 7.0 or 6.3.8 as the target upgrade. Release7.0.1 is the default upgrade target.

• Manage Software: To upgrade IP Office.• VM Management: To deploy OVA files for the supported Avaya Aura® application.• Upgrade Management: To upgrade Communication Manager that includes TN boards, media

gateways and media modules, Session Manager, Communication Manager Messaging, UtilityServices, Branch Session Manager to Release 7.0.1.

• User Settings: To configure the location from where System Manager displays informationabout the latest software and firmware releases.

• Download Management: To download the OVA files and firmware to which the customer isentitled. The download source can be the Avaya PLDS or an alternate source.

• Software Library Management: To configure the local or remote software library for storingthe downloaded software and firmware files.

• Upload Version XML: To save the version.xml file to System Manager. You require theversion.xml file to perform upgrades.

Virtual machine managementThe VM Management link from Solution Deployment Manager provides the virtual machinemanagement.

VM Management provides the following capabilities:

• Defines the physical location, Appliance Virtualization Platform or ESXi host, and discoversvirtual machines that are required for application deployments and virtual machine life cyclemanagement.




• Supports password change, patch installation, restart, shutdown, and certificate validation ofhost. Also, enables and disables SSH on the host.

• Manages lifecycle of the OVA applications that are deployed on the ESXi host. The lifecycleincludes start, stop, reset virtual machines, and establishing trust for virtual machines.

• Deploys Avaya Aura® application OVAs on customer-provided Virtualized Environment andAvaya Aura® Virtualized Appliance environments.

• Removes the Avaya Aura® application OVAs that are deployed on a virtual machine.

• Configures application and networking parameters required for application deployments.

• Supports flexible footprint definition based on capacity required for the deployment of theAvaya Aura® application OVA.

You can deploy the OVA file on the virtual machine by using the System Manager SolutionDeployment Manager and the Solution Deployment Manager client.

Related linksCertification validation on page 85

Utility Services in the Avaya Aura® Virtualized Applianceoffer

From Avaya Aura® Release 7.0, Utility Services replaces the console domain (C-dom). UtilityServices runs the Services Port connection that was previously run through Dom-0 on SystemPlatform. Therefore, Utility Services with the Services Port is a key component of the Avaya Aura®

Virtualized Appliance offer in Release 7.0, You must deploy Utility Services on each ApplianceVirtualization Platform.

With Services Port, you can connect a laptop directly to Ethernet 1 on an Avaya-supported server,and connect the laptop to any of management interface of applications that run on an ApplianceVirtualization Platform host. On the S8300D and S8300E servers, Services Port is on the front plate.The Services Port virtual machine also supports ASG logins and install of a customer ASG file on tothe system. By default, a generic ASG file is available on the system.

The Services Port virtual machine incorporates the Serviceability Agent for alarming and logcollection from System Manager.

From Avaya Aura® Release 7.0, Utility Services does not include IP Phone firmware. Theadministrator must download the latest version of the firmware from PLDS and install on UtilityServices.

Utility Services migrationIn the Avaya Aura® Virtualized Appliance offer on Appliance Virtualization Platform, you requireUtility Services for services static routing. Therefore, you must deploy Utility Services if UtilityServices is part of the solution.

Utility Services in the Avaya Aura® Virtualized Appliance offer



In the following two use cases, you might require to deploy Utility Services.

1. Migration of Communication Manager or Session Manager on the Linux® server: UtilityServices is mandatory for migration of systems running on the Linux® server. In this case,before you migrate, you must deploy Utility Services from VM Management.

2. Migration of Communication Manager or Session Manager on System Platform: In this case,the template already contains Utility Services. In this case, the process migrates UtilityServices, and you do not require to deploy Utility Services separately.




Chapter 3: Planning and configuration

Supported serversIn the Avaya appliance model, the customer can deploy or upgrade to Avaya Aura® Release 7.0.1applications on the following Avaya-provided servers:

• Dell™ PowerEdge™ R610 2CPU MID2• HP ProLiant DL360 G7 2CPU MID4• Dell™ PowerEdge™ R620 2CPU MID3• HP ProLiant DL360p G8• Dell™ PowerEdge™ R630• HP ProLiant DL360 G9• S8300D, for Communication Manager and Branch Session Manager• S8300E, for Communication Manager and Branch Session Manager• Intel 1006r server. Only to deploy Utility Services and Avaya Aura® Messaging OVA files.

Software requirementsAvaya Aura® supports the following software versions:

• Avaya Aura® Virtualized Appliance offer: Appliance Virtualization Platform 7.0.x on acustomized version of VMware® ESXi 5.5

• Customer-provided Virtualized Environment offer: Supports the following software versions:

- VMware® vSphere ESXi 5.0- VMware® vSphere ESXi 5.1- VMware®vSphere ESXi 5.5- VMware® vSphere ESXi 6.0- VMware® vCenter Server 5.0- VMware® vCenter Server 5.1- VMware® vCenter Server 5.5- VMware® vCenter Server 6.0



To view compatibility with other solution releases, see VMware Product Interoperability Matrixat http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php.

Note:Avaya Aura® Release 7.0 and later does not support ESXi releases earlier than 5.0.

Planning and configuration


http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php


Chapter 4: Preinstallation tasks

Deployment checklistUse the following checklist for the initial deployment of Appliance Virtualization Platform, UtilityServices and System Manager by using the Solution Deployment Manager client.

# Action Link/Notes

1 Download theAvaya_SDMClient_win64_7.0.1.0.0620319_44.zip file from the AvayaSupport website at http://support.avaya.com.

Perform the task if System Manager isunavailable.

2 Install theAvaya_SDMClient_win64_7.0.1.0.0620319_44.exe file.

Installing the Solution DeploymentManager client on your computer onpage 16

3 From the Avaya Support website at http://support.avaya.com, download OVA filesfor Utility Services and System Manager,and Release 7.0.1 feature pack files forUtility Services, System Manager, andAppliance Virtualization Platform.

-

4 Ensure that the following is accessible:

• Hostnames

• Out of Band Managementconsiderations

• Network configuration data such asnaming conventions, IP address,netmask and gateway

-

5 For Avaya Aura® Virtualized Appliancedeployments, install the supported server.

Supported servers on page 25

6 Install Appliance Virtualization Platform onthe server for applications such asCommunication Manager and BranchSession Manager that use S8300D orS8300E.

Installing Appliance VirtualizationPlatform on page 30

Table continues…


http://support.avaya.com





# Action Link/Notes

Appliance Virtualization Platform ispreinstalled on Common Release 2 and 3servers.

7 Using the Solution Deployment Managerclient, add a location.

Adding a location on page 37

8 Using the Solution Deployment Managerclient, add the Appliance VirtualizationPlatform host, 192.168.13.6, to thelocation.

Adding an ESXi host on page 44

9 Deploy Utility Services OVA, and selectthe appropriate footprint size and theservice mode.

While deploying OVA, provide the IPaddress of System Manager that youwant to deploy.

Deploying the Utility Services OVA file on page 65

10 Install the Utility Services 7.0.1 featurepack.

Installing software patches on page 69

11 Using the Solution Deployment Managerclient, deploy System Manager virtualmachine.

Deploying the System Manager OVA fileby using the Solution DeploymentManager client on page 59

12 Install the System Manager Release 7.0.1bin file.

Installing service packs and softwarepatches on System Manager by usingthe Solution Deployment Managerclient on page 64

13 To activate the serviceability agentregistration, reset the Utility Servicesvirtual machine.

-

14 Verify the installation of the SystemManager virtual machine.

Verifying the installation of SystemManager on page 114

Use the following checklist to deploy all other Avaya Aura® applications by using the SolutionDeployment Manager client or from System Manager Solution Deployment Manager.

# Action Link/Notes

1 Download the OVA files and feature packfiles of Avaya Aura® applications that youwant to deploy or upgrade from the AvayaSupport website at http://support.avaya.com.

Note:

For information about the upgradesequence and the required patches,

-

Table continues…

Preinstallation tasks





# Action Link/Notes

see the latest Avaya Aura® ReleaseNotes for the specific release on theAvaya Support website.

2 Ensure that the following is accessible:

• Hostnames

• Out of Band Managementconsiderations

• Network configuration data such asnaming conventions, IP address,netmask and gateway

-

3 For Avaya Aura® Virtualized Appliancedeployments, install the supported server.

Supported servers on page 25

4 Install Appliance Virtualization Platform onthe server for applications such asCommunication Manager and BranchSession Manager that use S8300D orS8300E.

Appliance Virtualization Platform ispreinstalled on Common Release 2 and 3servers.

Installing Appliance VirtualizationPlatform on page 30

5 Add a location. Adding a location on page 376 Add an Appliance Virtualization Platform

host as 192.168.13.6.Adding an ESXi host on page 44

7 Deploy Utility Services virtual machine,and install the Release 7.0.1 feature pack.

Deploying the Utility Services OVA file on page 65

Installing software patches on page 698 Deploy Avaya Aura® applications one at a

time, and then install the Release 7.0.1feature pack for each application.

Deploying an OVA file for an Avaya Auraapplication on page 67

Installing software patches on page 699 Verify the installation of all applications. Post installation checklist on page 114

Accessing Solution Deployment ManagerAbout this taskYou require to start Solution Deployment Manager to deploy and upgrade virtual machines, andinstall service packs or patches.

Accessing Solution Deployment Manager



ProcedurePerform one of the following:

• If System Manager is not already deployed, double-click the Solution Deployment Manager client.

• If System Manager is available, on the web console, click Services > Solution DeploymentManager.

Installing Appliance Virtualization PlatformAbout this task

Warning:You can obtain the root password for the Appliance Virtualization Platform system from the USBconfiguration file. The file must be kept secure. After installation, you must change the rootpassword for the Appliance Virtualization Platform host to a different value with the passwordchange option from Solution Deployment Manager.

Install Appliance Virtualization Platform on one of the following servers:

• Dell™ PowerEdge™ R610• HP ProLiant DL360 G7• Dell™ PowerEdge™ R620• HP ProLiant DL360p G8• Dell™ PowerEdge™ R630• HP ProLiant DL360 G9• S8300D for Communication Manager• S8300E for Communication Manager

Release 7.0 and later does not support S8510 and S8800 servers.

Before you begin• Configure the USB drive.• Ensure that the backup file is saved on a different server because after the Appliance

Virtualization Platform installation, server restarts, and all data is lost.• To use the Solution Deployment Manager client for deploying the virtual machines, install the

Solution Deployment Manager client on your computer.

Note:To install Appliance Virtualization Platform server while connected to the customer network,ensure that the IP address used for Appliance Virtualization Platform is not in use by anothersystem. If the configured IP address is already in use on the network during installation, theinstallation process stops. You must remove the duplicate IP address, and restart theinstallation.




Procedure1. Insert the USB drive and the Appliance Virtualization Platform CD-ROM into the server.

Use an external Avaya-approved USB and CD-ROM drives for installing ApplianceVirtualization Platform on S8300D or S8300E. The only supported USB CD-ROM drive isDigistor DIG73322, comcode 700406267.

2. Log on to the System Platform web console, and click Server Management > ServerReboot/Shutdown > Reboot to restart the server.

Warning:

When the server restarts, Appliance Virtualization Platform is installed, and all existingdata on the server is lost.

The system installs Appliance Virtualization Platform and ejects CD-ROM. The installationprocess might takes about 30 minutes to complete.

Note:

If using a monitor, the screen changes to black before the installation is complete. Amessage in red text might briefly display, which is an expected behavior. Do not takeany action.

3. Remove the USB drive and CD-ROM.

Note:

When installing Appliance Virtualization Platform on an HP server, you must remove theUSB drive when the server ejects CD-ROM. Otherwise, the server might becomenonoperational on reboot. If the server becomes nonoperational, remove the USB drive,and restart the server.

4. Using an SSH client, connect to the server through the eth1 services port by using thefollowing network parameters for your system:

• IP address: 192.168.13.5

• Netmask: 255.255.255.248

• Gateway: 192.168.13.1

The SSH client must use UTF-8. Alternatively, you can connect to the public networkaddress that was configured during the installation from a computer on the customernetwork.

5. Log in to Appliance Virtualization Platform as root and provide the password that isconfigured in the spreadsheet.

The system displays the End user license agreement (EULA) screen.

6. Read the EULA, and type Y to accept the terms.

You can press any key to read EULA, and use the space bar to scroll down.

Installing Appliance Virtualization Platform



Warning:

Accept EULA before you deploy virtual machines. If deployments are attempted beforeyou accept EULA, deployments fail.

7. On the System Manager web console, click Services > Solution Deployment Manager,and then click VM Management.

8. Install the Appliance Virtualization Platform patch.

For more information, see Installing the Appliance Virtualization Platform patch from SolutionDeployment Manager.

9. Deploy the Utility Services virtual machine, and then all other virtual machines with the datathat you noted in “System Platform and Template values”.

For instructions to deploy Utility Services and other virtual machines, see Deploying AvayaAura® applications from System Manager.

10. From System Manager Solution Deployment Manager, install the required software patchesfor the virtual machines.

Configuring servers preinstalled with ApplianceVirtualization Platform

About this taskYou can obtain the root password for the Appliance Virtualization Platform system from the USBconfiguration file. The file must be kept secure. After installation, you must change the rootpassword for the Appliance Virtualization Platform host to a different value with the passwordchange option from Solution Deployment Manager.

For newly purchased common servers, Appliance Virtualization Platform is preinstalled. This doesnot apply for migration. You must configure the customer network settings through the SolutionDeployment Manager client that is installed on a computer that is running Windows. The mediacomes with the server. The new S8300D and S8300E servers require an installation at the customersite.

Note:When possible, perform the deployment from the System Manager Solution DeploymentManager. Only when System Manager is unreachable, use the Solution Deployment Managerclient that is installed on the computer.

Procedure1. Turn on the server.

2. Install the Solution Deployment Manager client on the computer.




3. Configure the computer with the following:

• IP address: 192.168.13.5• Netmask: 255.255.255.248• Gateway: 192.168.13.1

4. Connect to NIC2 with a network cable.

5. Start an SSH session, log in to 192.168.13.6 as root, and type Avaya123$ as password.

The system prompts to change the password immediately.

6. To change the root password, perform the following:

a. At the prompt, type the current UNIX password.b. Type the new password.

For more information about password rules, see “Password policy”.c. Type the password again.

The system changes the host password.

7. Read and accept the license terms.

8. Type cd /opt/avaya/bin.

Not all commands are available in the /opt/avaya/bin location, and must be run with ./.For example, ./nic_port. The system only runs the commands that are specified in theprocedure from /opt/avaya/bin or as directed by Avaya Services. The system might getincorrectly configured if you run commands that are not specified in the procedure.

Most systems do not enable Out of Band Management. Use the set_oobm command onlyto enable Out of Band Management for the host and all virtual machines.

9. (Optional) To enable Out of Band Management on the Appliance Virtualization Platformhost, type # ./set_oobm on.

The system displays Host Out of Band Management set up is complete.

10. At the prompt, do the following:

a. Type ./serverInitialNetworkConfig.

The host IP address details are mandatory. Though DNS and NTP values are optional,you must provide the values.

b. At the prompt, provide the following host details:System is not in a default setup, please use SDM to change IP addressesDo you wish to setup networking? (y/n) yPlease enter IP addres for the AVP host in the format x.x.x.xFor example 172.16.5.1Please enter value 172.16.107.21Please enter subnet mask for the AVP host in the format x.x.x.xFor example 255.255.255.0Please enter value 255.255.255.0Please enter a default gateway for the AVP host in the format x.x.x.xFor example 172.16.5.254

Configuring servers preinstalled with Appliance Virtualization Platform



Please enter value 172.16.107.1Please enter a hostname for the AVP host.For example myhostPlease enter value avphostPlease enter a domain for the AVP host.For example mydomain.comPlease enter value mydomain.comPlease enter a main DNS server for the AVP host.For example 172.16.10.54Please enter value 172.16.107.1Please enter a secondary DNS server for the AVP host.For example 172.16.10.54Please enter value 172.16.107.2Please enter a NTP server for the AVP hostFor example 172.16.10.55Please enter value 172.16.107.50Stopping ntpdwatchdog-ntpd: Terminating watchdog process with PID 33560Starting ntpd

11. To verify the vmk0 settings, type # esxcli network ip interface ipv4 get.

Note:

Do not change the vmk1s address. vmk1s is fixed for the services port.

The system displays the following details:Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type DHCP DNS---- ------------- --------------- -------------- ------------ --------vmk1 192.168.13.6 255.255.255.248 192.168.13.7 STATIC falsevmk0 172.16.107.21 255.255.255.0 172.16.107.255 STATIC false

12. While connected to the services port, start the Solution Deployment Manager client.

13. Add a location.

14. Add the Appliance Virtualization Platform host as 192.168.13.6.

15. Check the version, and install the Release 7.0.1 feature pack on Appliance VirtualizationPlatform if required.

Note:

The common Release 3 servers require you to install the Appliance VirtualizationPlatformRelease 7.0.1 feature pack.

16. Deploy Utility Services.

17. Deploy other Avaya Aura® applications that will reside on this Appliance VirtualizationPlatform host.

18. Install the Release 7.0.1 patch files for all Avaya Aura® applications.




Uploading a file to the software libraryAbout this taskUse the procedure to upload software files such as OVA, images, and firmware that are requiredduring the deployment, migration, upgrade, and update of Avaya Aura® applications.

Before you begin• Start an SSH session.• On Download Management page, click Refresh Families.• When you add or update details in the versions.xml file, click Refresh Families again to

get the updated information.

Procedure1. On the System Manager web console, click Services > Solution Deployment Manager.

2. In the left navigation pane, click Software Library Management.

3. Click Manage Files.

4. From System Manager command line interface, copy the required OVA file to the /swlibrary/staging/sync/ location that you had created in System Manager.

Note:

You require admin privileges to the /swlibrary/staging/sync/ location.

The system displays the file that you copied in the Sync Files from directory section.

5. Provide the following information:

• MD5 Checksum: The value mentioned in the source or original location of the file.• Software Library: The local or remote software library.• Product Family

Note:

For SAL, in Product Family, Device Type, and Software Type fields, select Others.• Device Type• Software Type

If the file is already in versions.xml, the system populates the information.

If the file does not already exist in versions.xml, the system does not display the filedetails. You cannot use the file for upgrade in Upgrade Management. You can use the fileonly for new deployment from VM Management.

6. Select the file.

7. Click Sync.

In File Sync Started Message, the system displays a message about the status of theschedule of the job.

Uploading a file to the software library



8. Click OK.

When the job completes, the system displays the file in the Software Library Files section.

9. To check the status of the job, click Services > Scheduler > Pending Jobs.

When the job is complete, the system displays the file in the Software Library Files andremoves from Sync Files from directory.

Downloading the OVA file to System ManagerAbout this taskYou can download the software from Avaya PLDS or from an alternate source to System Manager.Use the procedure to download the OVA files to your computer and upload the file to SystemManager.

Before you beginSet the local software library.

Procedure1. Download the OVA file on your computer.

2. On the System Manager web console, click Services > Solution Deployment Manager.

3. In the navigation pane, click Download Management.

4. On the Download Management page, perform the following:

a. In the Select Software/Hardware Types section, select the family name, and click ShowFiles.

b. In the Select Files Download Details section, in the Source field, select My Computer.

c. Click Download.

The system displays the Upload File page.

5. In the Software Library field, select a local System Manager software library.

6. Complete the details for the product family, device type, and the software type.

7. Click Browse and select the OVA file from the location on the system.

This system uploads the OVA file from local computer to the designated software library onSystem Manager.




Chapter 5: Deploying Avaya Aura®applications

Managing the location

Viewing a locationProcedure


2. Click the Locations tab.

The Locations section lists all locations.

Adding a locationAbout this taskYou can define the physical location of the host and configure the location specific information. Youcan update the information later.

Procedure1. On the System Manager web console, click Services > Solution Deployment Manager,

and then click VM Management.

2. On the Location tab, in the Locations section, click New.

3. In the New Location section, perform the following:

a. In the Required Location Information section, type the location information.

b. In the Optional Location Information section, type the network parameters for the virtualmachine.

4. Click Save.

The system displays the new location in the VM Management Tree section.



Related linksNew and Edit location field descriptions on page 43

Editing the locationProcedure


2. On the Location tab, in the Locations section, select a location that you want to edit.

3. Click Edit.

4. In the Edit Location section, make the required changes.

5. Click Save.

Related linksNew and Edit location field descriptions on page 43

Deleting a locationProcedure


2. On the Location tab, in the Locations section, select one or more locations that you want todelete.

3. Click Delete.

4. On the Delete confirmation dialog box, click Yes.

The system does not delete the virtual machines that are running on the host, and moves thehost to Unknown location host mapping > Unknown location.

VM Management field descriptionsName DescriptionAuto-Reload VM Management Tree The option to automatically reload the VM

Management Tree after the completion of operationssuch as refreshing virtual machines.

Deploying Avaya Aura® applications



Locations

Name DescriptionLocation Name The location name.City The city where the host is located.Country The country where the host is located.

Button DescriptionNew Displays the New Location section where you can

provide the details of the location that you want toadd.

Edit Displays the Edit Location section where you canchange the details of an existing location.

Delete Deletes the locations that you select.

The system moves the hosts associated with thedeleted locations to unknown location.

Hosts

Name DescriptionHost Name The name of the ESXi host.Host IP The IP address of the ESXi host.Host FQDN FQDN of the ESXi host.vCenter IP/FQDN The IP address or FQDN of vCentre.Current Action The operation that is currently being performed on

the ESXi host.Last Action The last completed operation on the ESXi host.License Status The status of the license.Host Version The ESXi host version. The options are 5.5, 5.1, and

5.0. 6.0 only for VMware ESXi host.Offer Type The ESXi host type. The options are:

• AVP: Appliance Virtualization Platform host

• Customer VE: customer-provided VMware ESXihost

SSH Status The SSH service status. The values are:

• enabled

• disabledTable continues…




Name DescriptionHost Certificate The certificate status of the Appliance Virtualization

Platform host. The values are:

• : The certificate is added in Solution DeploymentManager and correct.

• : The certificate is not accepted or invalid.

You can click View for details of the certificatestatus.

vCenter Certificate The certificate status of the ESXi host. The valuesare:

• : The certificate is correct.

The system enables all the options in MoreActions that apply to VMware ESXi host.


You can click View for details of the certificatestatus.

Note:Depending on the Appliance Virtualization Platform host and vCenter certificate status, thesystem enables the options in More Actions.

Button DescriptionAuto Refresh The option to automatically refresh the page with the

latest changes. For example, the page updates:

• The VM state when a virtual machine changes

• The license status or certificate status of host whenhost changes

The system refreshes the data every minute.Add Displays the New Host section where you can

provide the details of the host that you want to add.Edit Displays the Host Information section where you can

change the details of an existing host.Remove Removes the hosts that you select.

The system moves the hosts associated with thedeleted locations to unknown location.

Change Network Params > Change Host IPSettings

Displays the Host Network/IP Settings section whereyou can change the host IP settings for theAppliance Virtualization Platform host.

Table continues…




Button DescriptionChange Network Params > Change NetworkSettings

Displays the Host Network Setting section where youcan change the network settings for the ApplianceVirtualization Platform host.

Refresh Refreshes the status of the hosts.More Actions > Change Password Displays the Change Password section where you

can change the password for the ApplianceVirtualization Platform host.

More Actions > Update Displays the Update host page where you can selectthe file for updating the Appliance VirtualizationPlatform host.

More Actions > Enable SSH Enables SSH for the Appliance VirtualizationPlatform host.

When SSH for the Appliance Virtualization Platformhost is enabled, the system displays SSH enabledsuccessfully.

More Actions > Disable SSH Disables SSH on the Appliance VirtualizationPlatform host.

When SSH for Appliance Virtualization Platform isdisabled, the system displays Disabling SSH forAVP host with <IP address> <FQDN>,<username>.

More Actions > Host Restart Restarts the host and virtual machines that arerunning on the Appliance Virtualization Platform host.

More Actions > Host Shutdown Shuts down the host and virtual machines that arerunning on the Appliance Virtualization Platform host.

More Actions > Generate/Accept Certificate Displays the Certificate dialog box where you canmanage certificates for the host.

Depending on the host type, the options are:

• Generate Certificate: To generate certificate forAppliance Virtualization Platform host only.

• Accept Certificate: To accept a valid certificate forthe host or vCenter.

• Decline Certificate: To decline the certificate forAppliance Virtualization Platform host only. Youmust regenerate the certificate and accept if youdecline a host certificate.

Virtual Machines

Name DescriptionVM Name The name of the virtual machine.

Table continues…




Name DescriptionVM IP The IP address of the virtual machine.VM FQDN FQDN of the virtual machine.VM App Name The name of the application virtual machine . For

example, Session Manager.VM App Version The version of the application virtual machine. For

example, 7.0.0.0.VM State The state of the virtual machine. The states are

Started and Stopped.Current Action Status The status of the current operation. The statuses

are:

• Deploying

• Starting

• Stopping

The Status Details link provides the details of theoperation in progress.

Last Action The last action performed on the virtual machine.Host Name The hostname of the VMware host or Appliance

Virtualization Platform hostTrust Status The status of the connection between System

Manager and the virtual machine.

The status can be Success or Failed.

When the connection between System Manager andthe virtual machine establishes, Trust Statuschanges to Success.

Only when the trust status is Success, you canperform other operations.

Data Store The data store with the available size.

Button DescriptionNew Displays the VM Deployment section where you can

provide the host and deploy an application.Edit Displays the VM Deployment section where you can

change the details of a virtual machine.Delete Turns off the virtual machines and deletes the

selected virtual machines.Start Starts the selected virtual machines.Stop Stops the selected virtual machines.Show Selected Displays only the selected virtual machines.

Table continues…




Button DescriptionMore Actions > Restart Starts the selected virtual machines that were

stopped earlier.More Actions > Refresh VM Updates the status of the virtual machines.More Actions > Reestablish Connection Establishes the connection between System

Manager and the virtual machine.

When the connection between System Manager andthe virtual machine establishes, the Trust Statuschanges to Success.

More Actions > Update Static Routing Displays the VM Update Static Routing sectionwhere you can update the IP address of UtilityServices for static routing.

New and Edit location field descriptionsRequired Location Information

Name DescriptionName The location name.Avaya Sold-To # The customer contact number.

Administrators use the field to check entitlements.Address The address where the host is located.City The city where the host is located.State/Province/Region The state, province, or region where the host is

located.Zip/Postal Code The zip code of the host location.Country The country where the host is located.

Optional Location Information

Name DescriptionDefault Gateway The IP address of the virtual machine gateway. For

example, 172.16.1.1.DNS Search List The search list of domain names.DNS Server 1 The DNS IP address of the primary virtual machine.

For example, 172.16.1.2.DNS Server 2 The DNS IP address of the secondary virtual

machine. For example, 172.16.1.4.NetMask The subnetwork mask of the virtual machine.NTP Server The IP address or FQDN of the NTP server.

Separate the IP addresses with commas (,).




Button DescriptionSave Saves the location information and returns to the

Locations section.Edit Updates the location information and returns to the

Locations section.Delete Deletes the location information, and moves the host

to the Unknown location section.Cancel Cancels the add or edit operation, and returns to the

Locations section.

Managing the host

Adding an ESXi hostAbout this taskUse the procedure to add an Appliance Virtualization Platform or ESXi host. You can associate anESXi host with an existing location.

Before you beginA location must be available.



2. In VM Management Tree, select a location.

3. On the Host tab, in the Hosts for Selected Location <location name> section, click New.

4. In the New Host section, provide the following:

Host name, IP address, user name, and password.

5. Click Save.

6. On the Certificate dialog box, click Accept Certificate.

The system generates the certificate and adds the Appliance Virtualization Platform host. Forthe ESXi host, you can only accept the certificate. If the certificate is invalid, to generatecertificate, see the VMware documentation.

In the VM Management Tree section, the system displays the new host in the specifiedlocation. The system also discovers applications.




7. To view the discovered application details, such as name and version, establish trustbetween the application and System Manager using the following:

a. Click More Actions > Re-establish connection.

b. Click Refresh VM.

Important:

When you change the IP address or FQDN of the Appliance Virtualization Platform hostfrom the local inventory, you require Utility Services. To get the Utility Servicesapplication name during the IP address or FQDN change, refresh Utility Services toensure that Utility Services is available.

Related linksNew and Edit host field descriptions on page 56Generating and accepting certificates on page 87

Editing an ESXi hostProcedure



3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXihost that you want to update.

4. Change the ESXi host information.

5. Click Save.

The system updates the ESXi host information.

Related linksNew and Edit host field descriptions on page 56

Installing the Appliance Virtualization Platform patch fromSolution Deployment Manager

About this taskInstall the Release 7.0.1 feature pack on the existing Appliance Virtualization Platform Release 7.0by using the Solution Deployment Manager client or System Manager Solution DeploymentManager.

Managing the host



Note:From System Manager Solution Deployment Manager, you cannot update an ApplianceVirtualization Platform that hosts this System Manager.

Do not use this procedure for installing the Appliance Virtualization Platform patch on anS8300D server.

Before you begin1. Add a location.2. Add a host.3. Enable the SSH service on the Appliance Virtualization Platform host.4. Stop all virtual machines that are running on the Appliance Virtualization Platform host.

Note:Install only Avaya-approved service packs or software patches on Appliance VirtualizationPlatform. Do not install the software patches that are downloaded directly from VMware®.




3. On the Host tab, in the Hosts for Selected Location <location name> section, select theAppliance Virtualization Platform host, and click More Actions > Update.

4. On the Update Host page, click Select patch from local SDM client machine.

5. In Select patch file, provide the absolute path to the patch file of the host, and click UpdateHost.

For example, the absolute path on your computer can be /tmp/avp/avaya-avp-7.0.0.1.0.5.zip.

In the Hosts for Selected Location <location name> section, the system displays the updatestatus in the Current Action column.

6. To view the details, in the Current Action column, click Patching.

Host Patching Status window displays the details. The patch installation takes some time.When the patch installation is complete, the Current Action column displays the status.

Next stepsIf virtual machines that were running on the Appliance Virtualization Platform host does notautomatically start, manually start the machines.

Related linksUpdate field descriptions on page 59




Changing the network parameters for an Appliance VirtualizationPlatform host

About this taskUse this procedure to change the network parameters of Appliance Virtualization Platform afterdeployment. You can change network parameters only for the Appliance Virtualization Platformhost.

Note:If you are connecting to Appliance Virtualization Platform through the public managementinterface, you might lose connection during the process. Therefore, after the IP addresschanges, close Solution Deployment Manager, and restart Solution Deployment Manager byusing the new IP address to reconnect.




3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXihost and click Change Network Params > Change Host IP Settings.

4. In the Host Network/ IP Settings section, change the IP address, subnetmask, and otherparameters as appropriate.

Note:

An Appliance Virtualization Platform host and all virtual machines running on the hostmust be on the same subnet mask.

If Out of Band Management is configured in an Appliance Virtualization Platformdeployment, you need two subnet masks, one for each of the following:

• Public or signaling traffic, Appliance Virtualization Platform, and all virtual machinespublic traffic.

• Management, Appliance Virtualization Platform, and all virtual machine managementports.

5. To change the gateway IP address, perform the following:

a. Click Change Gateway.

The Gateway field becomes available for providing the IP address.

b. In Gateway, change the IP address.

c. Click Save Gateway.

6. Click Save.

The system updates the Appliance Virtualization Platform host information.

Managing the host



Related linksChange Network Parameters field descriptions on page 56

Changing the network settings for an Appliance VirtualizationPlatform host from Solution Deployment Manager

About this taskWith Appliance Virtualization Platform, you can team NICs together to provide a backup connectionwhen the server NIC or the Ethernet switch fails. You can also perform NIC teaming from thecommand line on Appliance Virtualization Platform.

Appliance Virtualization Platform supports Active-Standby and Active-Active modes of NIC teaming.For more information, see “NIC teaming modes”.

Note:• If you add a host with service port IP address in Solution Deployment Manager and change

the IP address of the host to the public IP address by using Host Network/ IP Settings, thesystem updates the public IP address in the database. Any further operations that youperform on the host fails because public IP address cannot be reached with the serviceport. To avoid this error, edit the host with the service port IP address again.

• If FQDN of the Appliance Virtualization Platform host is updated by using Host Network/IPsetting for domain name, refresh the host to get the FQDN changes reflect in SolutionDeployment Manager.

Use this procedure to change network settings, such as changing VLAN ID, NIC speed, and NICteam and unteaming for an Appliance Virtualization Platform host.




3. On the Host tab, in the Host for Selected Location <location name>, select an ApplianceVirtualization Platform host.




4. Click Change Network params > Change Network Settings.

The Host Network/ IP Settings page displays the number of switches as 4.

You can configure port groups for the following switches:

• vSwitch0, reserved for the Public and Management traffic.

• vSwitch1, reserved for services port. You cannot change the values.

• vSwitch2, reserved for Out of Band Management.

• vSwitch3. No reservations.

5. To change VLAN ID, perform the following:

a. To expand the Standard Switch: vSwitch<n> section, click .

The section displays the vSwitch details.

b. Click on the VLANID link or the edit icon ( ).

The system displays the Port Group Properties page where you can edit the VLAN IDport group property.

c. In VLAN ID, select an ID from the available values.

For more information about the value, see NIC teaming.

d. Click OK.

The system displays the new VLAN ID.

Note:

You can change the services port VLAN ID for S8300D servers only through SolutionDeployment Manager.

Managing the host



6. To change the NIC speed, perform the following:

a. Ensure that the system displays a vmnic in the NIC Name column.

b. Click Change NIC speed.

The system displays the selected vmnic dialog box.

c. In Configured speed, Duplex, click a value.

d. Click OK.

For more information, see VLAN ID assignment.

The system displays the updated NIC speed in the Speed column.

If the NIC is connected, the system displays in Link Status.

Note:

You can change the speed only for common servers. You cannot change the speed forS8300D and S8300E servers.

7. To change the NIC teaming, perform the following:

a. Select a vmnic.

b. Click NIC team/unteam.

The system displays the Out of Band Management Properties page.

c. To perform NIC teaming or unteaming, select the vmnic and click Move Up or MoveDown to move the vmnic from Active Adapters, Standby Adapters, or UnusedAdapters.

For more information, see NIC teaming modes.

d. Click OK.

The vmnic teams or unteams with Active Adapters, Standby Adapters, or UnusedAdapters as required.

e. To check the status of the vmnic, click NIC team/ unteam.

8. To get the latest data on host network IP settings, click Refresh .

The system displays the current status of the vmnic.

Note:

You cannot perform NIC teaming for S8300D and S8300E servers.

Related linksHost Network / IP Settings field descriptions on page 57




Changing the password for an Appliance Virtualization Platformhost

About this taskYou can change the password only for the Appliance Virtualization Platform host. This is thepassword for the user that you provide when adding the Appliance Virtualization Platform host.




3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXihost and click More Actions > Change Password.

4. In the Change Password section, enter the current password and the new password.

For more information about password rules, see “Password policy”.

5. Click Change Password.

The system updates the password of the Appliance Virtualization Platform host.

Related linksPassword policy on page 51Change Password field descriptions on page 58

Password policyThe password must meet the following requirements:

• Must contain at least eight characters.• Must contain at least one of each: an uppercase letter, a lowercase letter, a numerical, and a

special character.• Must not contain an uppercase letter at the beginning and a digit or a special character at the

end.

Examples of invalid passwords:

• Password1: Invalid. Uppercase in the beginning and a digit at the end.• Password1!: Uppercase in the beginning and a special character at the end.

Example of a valid password: myPassword!1ok

If the password does not meet the requirements, the system prompts you to enter a new password.Enter the existing password and the new password in the correct fields.

Ensure that you keep the root password safe. You need the password while adding the host toSolution Deployment Manager and for troubleshooting.

Managing the host



Related linksChanging the password for an Appliance Virtualization Platform host on page 51

Enabling and disabling SSH on Appliance Virtualization Platformfrom Solution Deployment Manager

About this taskFor security purpose, SSH access to Appliance Virtualization Platform shuts down in the normaloperation. You must enable the SSH service on Appliance Virtualization Platform from SolutionDeployment Manager.




3. Select an Appliance Virtualization Platform host.

4. To enable SSH, click More Actions > Enable SSH.

The system displays enabled in the SSH status column.

5. To disable SSH, click More Actions > Disable SSH.

The system displays disabled in the SSH status column.

Enabling and disabling SSH on Appliance Virtualization Platformfrom System Manager CLI

About this taskFor security purpose, SSH access to Appliance Virtualization Platform shuts down in the normaloperation. You must enable the SSH service on Appliance Virtualization Platform.

You can enable SSH, disable SSH, and check the SSH status on the Appliance VirtualizationPlatform host.

Before you beginStart an SSH session.

Procedure1. Log in to the System Manager command line interface as root.

2. Navigate to the $MGMT_HOME/infra/bin/avpSSHUtility location.

3. Type ./enableDisableSSHOnAVP.sh.




The system displays the following options:

• Enable SSH on the Appliance Virtualization Platform host.

• Disable SSH on the Appliance Virtualization Platform host.

• Check the SSH status on the Appliance Virtualization Platform host.

4. To enable SSH, perform the following:

a. At the prompt, type 1 and press Enter.

b. Type the IP address of the Appliance Virtualization Platform host.

c. Type the time in minutes.

The time is the duration after which the system blocks any new SSH connections. Thevalid range 10 to 120 minutes.

The system displays the message and enables SSH on Appliance VirtualizationPlatform host.

For example, if you set the time to 50 minutes, after 50 minutes, the system blocks any newSSH connections. If you reenable SSH before completion of 50 minutes, the system adds 50minutes to the initial 50 minutes to reenable connections.

5. To disable SSH, perform the following:



If SSH is already disabled, the system displays False and the message SSH is alreadydisabled. No operation performed. Exiting.

6. (Optional) To view the status of SSH, perform the following:



If SSH is enabled, the system displays Is SSH enable — false.

If SSH is disabled, the system displays Is SSH disable — true.

Changing the IP address and default gateway of the hostAbout this taskWhen you change the default gateway and IP address from the vSphere, the change might beunsuccessful.

You cannot remotely change the IP address of the Appliance Virtualization Platform host to adifferent network. You can change the IP address remotely only within the same network.

To change the Appliance Virtualization Platform host to a different network, perform Step 2 or Step3.

Managing the host



Before you beginConnect the computer to the services port.

Procedure1. Using an SSH client, log in to the Appliance Virtualization Platform host.

2. Connect the Solution Deployment Manager client to services port on the ApplianceVirtualization Platform host, and do the following:

a. To change the IP address, at the command prompt of the host, type the following:esxcli network ip interface ipv4 set -i vmk0 -I <old IP address of the host> -N <new IP address of the host> -t static

For example:esxcli network ip interface ipv4 set -i vmk0 -I 135.27.162.121 -N 255.255.25 5.0 -t static

b. To change the default gateway, type esxcfg-route <new gateway IP address>.

For example:esxcfg-route 135.27.162.1

3. Enable SSH on the Appliance Virtualization Platform host and run the ./serverInitialNetworkConfig command.

For more information, see Configuring servers preinstalled with Appliance VirtualizationPlatform.

Shutting down the Appliance Virtualization Platform hostAbout this taskYou can perform the shutdown operation on one Appliance Virtualization Platform host at a time.You cannot schedule the operation.





4. Click More Actions > Host Shutdown.

The Appliance Virtualization Platform host and virtual machines shut down.




Restarting the Appliance Virtualization Platform hostProcedure




4. Click More Actions > Host Restart.

The system restarts the Appliance Virtualization Platform host and virtual machines.

Deleting an ESXi hostProcedure


2. On the Host tab, in the Hosts for Selected Location <location name> section, select one ormore hosts that you want to delete.

3. Click Delete.

4. On the Delete confirmation page, click Yes.

Mapping the ESXi host to an unknown locationAbout this taskWhen you delete a location, the system does not delete the virtual machines running on the host,and moves the host to Unknown location host mapping > Unknown location. You can configurethe location of an ESXi host again.



2. In the left navigation pane, click the Unknown location host mapping link.

3. In the Host Location Mapping section, select an ESXi host and click Edit.

The system displays the Host Information page.

4. Select a location to which you want to map the ESXi host.

5. Click Submit.

Managing the host



The system displays the ESXi host in the selected location.

New and Edit host field descriptionsName DescriptionLocation The location where the host is availabe. The field is

read only.Host Name The hostname of Appliance Virtualization Platform or

the ESXi host. For example, smgrdev.Host FQDN or IP The IP address or FQDN of Appliance Virtualization

Platform or the ESXi host.User Name The user name to log in to Appliance Virtualization

Platform or the ESXi host.

Note:

For Appliance Virtualization Platform, providethe root login and password that you configuredin the spreadsheet.

Password The password to log in to Appliance VirtualizationPlatform or the ESXi host.

Button DescriptionSave Saves the host information and returns to the Hosts

for Selected Location <location name> section.

Change Network Parameters field descriptionsNetwork Parameters

Name DescriptionName The name of the Appliance Virtualization Platform

host. The field is display-only.IP The IP address of the Appliance Virtualization

Platform hostSubnet Mask The subnet mask the Appliance Virtualization

Platform hostHost Name The host name the Appliance Virtualization Platform

hostDomain Name The domain name the Appliance Virtualization

Platform hostPreferred DNS Server The preferred DNS server

Table continues…




Name DescriptionAlternate DNS Server The alternate DNS serverGateway The gateway IP address.

The field is available only when you click ChangeGateway.

Button DescriptionChange Gateway Makes the Gateway field available, and displays

Save Gateway and Cancel Gateway Changebuttons.

Save Gateway Saves the gateway IP address value that youprovide.

Cancel Gateway Change Cancels the changes made to the gateway.

Button DescriptionSave Saves the changes that you made to network

parameters.

Host Network / IP Settings field descriptionsPort GroupsStandard Switch vSwitch <n> displays the Port Groups and NICs sections.

Name Description

or VLAN ID link Displays the Port Group Properties page where youconfigure VLAN ID.

VLAN ID Displays the VLAN ID. The options are:

• None (0)

• 1 to 4093

The field displays only unused IDs.OK Saves the changes.

NIC speedButton DescriptionChange NIC speed Displays the vmnic<n> dialog box.

Name DescriptionConfigured speed, Duplex Displays the NIC speed. The options are:

• AutonegotiateTable continues…

Managing the host



Name Description• 10,Half

• 10,Full

• 100,Half

• 100,Full

• 1000,FullOK Saves the changes.

NIC teamingButton DescriptionNIC team/unteam Displays the Out of Band Management Properties

vSwitch<n> dialog box.

Button DescriptionMove Up Moves the VMNIC from unused adapters to standby

or active adapters or from standby to active adapter.Move Down Moves the VMNIC from active to standby adapter or

from standby to unused adapter.Refresh Refreshes the page.OK Saves the changes.

Change Password field descriptionsName DescriptionCurrent Password The password for the user you input when adding

the host.New Password The new passwordConfirm New Password The new password

Button DescriptionChange Password Saves the new password.




Update field descriptionsName DescriptionPatch location The location where the Appliance Virtualization

Platform patch is available. The options are:

• Select Patch from Local SMGR: To use theAppliance Virtualization Platform patch that isavailable on the local System Manager.

• Select Patch from software library: To use theAppliance Virtualization Platform patch that isavailable in the software library.

Select patch file The absolute path to the Appliance VirtualizationPlatform patch file.

Button DescriptionUpdate Host Installs the patch on the Appliance Virtualization

Platform host.

Managing the virtual machine

Deploying the System Manager OVA file by using the SolutionDeployment Manager client

About this taskUse the procedure to create a virtual machine on Appliance Virtualization Platform or ESXi host, anddeploy OVA for System Manager virtual machine by using the Solution Deployment Manager client.

Before you begin• Install the Solution Deployment Manager client on your computer.• Add a location.• Add Appliance Virtualization Platform or an ESXi host to the location.• Deploy Utility Services.

Procedure1. To start the Solution Deployment Manager client, click Start > All Programs > Avaya >

Avaya SDM Client or the SDM icon ( ) on the desktop.

2. In VM Management Tree, select a host.




3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, clickNew.

The system displays the VM Deployment section.

4. In the Select Location and Host section, do the following:

a. In Select Location, select a location.

b. In Select Host, select a host.

c. In Host FQDN, type the virtual machine name.

5. In Data Store, select a data store.

The page displays the capacity details.

6. Click Next.

7. In the Deploy OVA section, do the following:

a. In Select Software Library, select the local or remote library where the OVA file isavailable.

To deploy the OVA by using the Solution Deployment Manager client, you can use thedefault software library that is set during the client installation.

b. In Select OVAs, select the OVA file that you want to deploy.

c. In Flexi Footprint, select one of the following:

• SMGR Profile 2 Max User 250K: To support 250000 users. This configurationrequires 6 vCPUs and 12 GB memory.

• SMGR Profile 1 Max User 35K: To support 35000 users. This configuration requires4 vCPUs and 9 GB memory.

8. Click Next.

In Configuration Parameters and Network Parameters sections, the system displays thefields that are specific to the application that you deploy.

9. In the Network Parameters section, ensure that page displays the following preconfiguredfields:

• Public• Out of Band Management: When Out of Band Management is enabled.

10. In the Configuration Parameters section, complete the fields.

For more information, see “VM Deployment field descriptions”.

For each application that you deploy, fill the appropriate fields.

11. Click Deploy.

12. Click Accept the license terms.

In the Hosts for Selected Location <location name> section, the system displays thedeployment status in the Current Action Status column.




The system displays the virtual machine on the VMs for Selected Location <location name>page.

13. To view details, click the Status Details link.

Next steps• Install the System Manager Release 7.0.1 patch file.• Update the user password for the system to synchronize the data from applications.

When System Manager is operational, you can use Solution Deployment Manager from SystemManager to deploy all other Avaya Aura® applications or continue to use the Solution DeploymentManager client.

Related linksUploading a file to the software library on page 35VM Deployment field descriptions on page 61

VM Deployment field descriptionsSelect Location and Host

Name DescriptionSelect Location The location name. The field is display-only.Select Host The hostname of the Appliance Virtualization

Platform that you must select. For example,smgrdev.

Host FQDN FQDN of the Appliance Virtualization Platform host.The field is display-only.

VM Name The name of the virtual machine.ME Deployment The option to perform the Midsize Enterprise

deployment.

The option is available only while deployingCommunication Manager simplex OVA.

Deploy OVA

Name DescriptionProvide OVA path The option to specify the location from where you

can get the OVA file.Select OVA File The absolute path to the .ova file of the virtual

machine that you must provide. For example, C:\Program Files\SDM\smgr_7.ovaThe field is available only when you click ProvideOVA path.

Table continues…




Name DescriptionSubmit Selects the .ova file of the virtual machine that you

want to deploy.

The field is available only when you click ProvideOVA path.

OVA from SW Library The option to specify the software library where theOVA file is saved.

Software Library The default path provided during the installation ofthe Solution Deployment Manager client. The defaultpath is C:\Program Files\Avaya\SDMClient\Default_Artifacts.

The field is available only when you click OVA fromSW Library

File Name The .ova file that you want to deploy.

The field is available only when you click OVA fromSW Library.

Select Flexi Footprint The footprint size supported for the selected host.The options are:

• System Manager Profile 2 Max User 250K: Tosupport 250000 users. This configuration requires6 vCPUs and 12 GB memory.

• System Manager Profile 1 Max User 35K: Tosupport 35000 users. This configuration requires 4vCPUs and 9 GB memory.

Important:

Ensure that the required memory is available forthe footprint sizes that you selected. Theupgrade operation might fail due to insufficientmemory.

Configuration ParametersThe system populates most of the fields depending on the OVA file.

Name DescriptionManagement IP Address (Out of BandManagement IP Address)

The IP address of the System Manager virtualmachine for out of band management.

The field is optional network interface to isolatemanagement traffic on a separate interface from theinbound signaling network.

Management Netmask The Out of Band Management subnetwork mask toassign to the System Manager virtual machine.

Table continues…




Name DescriptionManagement Gateway The gateway IP address to assign to the System

Manager virtual machine. For example, 172.16.1.1.IP Address of DNS Server The DNS IP addresses to assign to the primary,

secondary, and other System Manager virtualmachines. Separate the IP addresses with commas(,). For example, 172.16.1.2, 172.16.1.4.

Management Hostname The hostname to assign to the System Managervirtual machine. For example, bouldervm2.

Default Search List The search list of domain names. The field isoptional.

NTP Server IP or FQDN The IP address or FQDN of the NTP server. Thefield is optional. Separate the IP addresses withcommas (,).

Time Zone The timezone where the System Manager virtualmachine is located. A list is available where youselect the name of the continent and the name of thecountry.

Network Parameters

Name DescriptionPublic The port number that is mapped to public port group.

You must configure Public network configurationparameters only when you configure Out of BandManagement. Otherwise, Public networkconfiguration is optional.

Out of Band Management The port number that is mapped to the out of bandmanagement port group.

Virtual FQDN

Name DescriptionVirtual Hostname The virtual hostname of the System Manager virtual

machine. For example, grsmgr.Virtual Domain The virtual domain name of the System Manager

virtual machine. For example, dev.com.

SNMPv3 Parameters

Name DescriptionSNMPv3 User Name Prefix The prefix for SNMPv3 user.SNMPv3 User Authentication Protocol Password The password for SNMPv3 user authentication.

Table continues…




Name DescriptionConfirm Password The password that you retype to confirm the

SNMPv3 user authentication protocol.SNMPv3 User Privacy Protocol Password The password for SNMPv3 user privacy.Confirm Password The password that you must provide to confirm the

SNMPv3 user privacy protocol.

Public Network Settings

Name DescriptionPublic IP Address The IP address to enable public access to different

interfaces.Public Netmask The subnetwork mask to assign to System Manager

virtual machine.Public Gateway The gateway IP address to assign to the System

Manager virtual machine. For example, 172.16.1.1.Public Hostname The hostname to assign to the System Manager

virtual machine. For example, bouldervm2.

Button DescriptionDeploy Displays the EULA acceptance screen where you

must click Accept to start the deployment process.

Installing service packs and software patches on System Managerby using the Solution Deployment Manager client

About this taskUse the procedure to install service packs, feature packs, or software patches on System Managerby using Solution Deployment Manager client.

Before you beginInstall the Solution Deployment Manager client.



2. Click VM Management.


4. On the Virtual Machines tab, in the VMs for Selected Location <location name> section,select System Manager on which you want to install the patch.




5. (Optional) If updating from a different client, perform the following:

a. Click More Actions > Re-establish connection.b. Click on Refresh VM.c. To view the status, in the Current Action column, click Status Details.d. Proceed with the next step.

6. Click More Actions > Update VM.

The system displays the System Manager Update dialog box.

7. In Select bin file from Local SDM Client, provide the absolute path to the software patch orservice pack.

Note:

The absolute path is the path on the computer on which the Solution DeploymentManager client is running. The patch is uploaded to System Manager.

8. (Optional) Click the Auto commit the patch check box.

9. Click Install.

In the VMs for Selected Location <location name> section, the system displays the status.

10. To view the details, in the Current Action column, click Status Details.

SMGR Patching Status window displays the details. The system displays the InstalledPatches page. The patch installation takes some time.

11. On the Installed Patches page, perform the following:

a. In Action to be performed, click Commit.

The system installs the patch, service pack or feature pack that you selected.b. Click Get Info.c. Select the patch, service pack or feature pack, and click Commit.


Deploying the Utility Services OVA fileAbout this taskUse the procedure to create a virtual machine on the ESXi host, and deploy Utility Services OVA onthe Avaya-provided server.

To deploy Utility Services, you can use Solution Deployment Manager from System Manager or theSolution Deployment Manager client, when System Manager is unavailable. Deploy Utility Servicesfirst, install the Release 7.0.1 feature pack, and then deploy all other applications one at a time.




Before you begin• Complete the deployment checklist.

For information about the deployment checklist, see Deploying Avaya Aura® applications fromSystem Manager.

• Add a location.• Add Appliance Virtualization Platform or an ESXi host to the location.• Download the required OVA file to System Manager.












6. Click Next.

7. In the Deploy OVA section, perform the following:


If you are deploying the OVA from the Solution Deployment Manager client, you canuse the default software library that is set during the client installation.


c. In Flexi Footprint, select the footprint size that the application supports.

• S8300D: Due to the limited resources available on S8300D, the only footprint optionis minimal

• Default: For all other server platforms.

8. Click Next.





9. In the Network Parameters section, ensure that the following fields are preconfigured:

• Public

• Services: Only for Utility Services

• Duplicate Link: Only for duplex Communication Manager

• Out of Band Management: Only if Out of Band Management is enabled



For more information about Configuration Parameters, see Network Parameters andConfiguration Parameters field descriptions.

11. Click Deploy.




13. To view details, click the Status Details link.

For information about VM Management field descriptions, see Deploying Avaya Aura®

applications from System Manager.

14. Install the Release 7.0.1 feature pack.

15. Reboot the Utility Services virtual machine.

Next steps1. Deploy System Manager and install the Release 7.0.1 feature pack.2. To activate the serviceability agent registration, reset the Utility Services virtual machine.3. Deploy all other Avaya Aura® applications one at a time.

Related linksVM Deployment field descriptions on page 76Network Parameters and Configuration Parameters field descriptionsVM Deployment field descriptions on page 76Network Parameters and Configuration Parameters field descriptions

Deploying an OVA file for an Avaya Aura® applicationAbout this taskUse the procedure to create a virtual machine on the ESXi host, and deploy OVA for an AvayaAura® application on the virtual machine.




To deploy an Avaya Aura® application, you can use Solution Deployment Manager from SystemManager or the Solution Deployment Manager client if System Manager is unavailable.

Deploy Utility Services first, and then deploy all other applications one at a time.

Before you begin• Add a location.• Add Appliance Virtualization Platform or an ESXi host to the location.• Ensure that the certificate is valid on the Appliance Virtualization Platform host or vCentre if

used.• Download the required OVA file to System Manager.












6. Click Next.

7. In the Deploy OVA section, do the following:


To deploy the OVA by using the Solution Deployment Manager client, you can use thedefault software library that is set during the client installation.


c. In Flexi Footprint, select the footprint size that the application supports.

8. Click Next.


9. In the Network Parameters section, ensure that the following fields are preconfigured:

• Public




• Services: Only for Utility Services• Duplicate Link: Only for duplex Communication Manager• Out of Band Management: Only if Out of Band Management is enabled



For each application that you deploy, fill the appropriate fields. For more information, see“VM Deployment field descriptions”.

11. Click Deploy.




13. To view details, click Status Details.

Next stepsInstall the Release 7.0.1 patch file for the Avaya Aura® application.

Perform the following:

1. From the Manage Elements link on System Manager, update the username password.2. Before the synchronization and after deployment, add an SMNP profile on Communication

Manager.

Note:If you fail to update the password, the synchronization operation fails.

Related linksInstalling software patches on page 69VM Deployment field descriptions on page 76

Installing software patchesAbout this taskUse the procedure to install software patches, service packs, and feature packs that are entitled foran Avaya Aura® application, and commit the patches that you installed.

Before you begin• Perform the preupgrade check.• If you upgrade an application that was not deployed from Solution Deployment Manager:

1. Select the virtual machine.2. To establish trust, click More Actions > Re-establish Connection.




3. Click Refresh VM.


2. In the left navigation pane, click Upgrade Management.

3. Select an Avaya Aura® application on which you want to install the patch.

4. Click Upgrade Actions > Upgrade/Update.

5. On the Upgrade Configuration page, click Edit.

6. In the General Configuration Details section, in the Operation field, click Update.

7. In Upgrade Source, select the software library where you have downloaded the patch.

8. (Optional) Click the Auto Commit check box, if you want the system to automaticallycommit the patch.

Note:

If an application is unreachable, the auto commit operation might fail and the UpdatePatch Status window displays a warning message. You must wait for some time, selectthe same patch in the Installed Patches section, and perform the commit operationagain.

9. In the Upgrade Configuration Details section, in the Select patches for update table, selectthe software patch that you want to install.

10. Click Save.

11. On the Upgrade Configuration page, ensure that the Configuration Status field displays .

If the field displays , review the information on the Edit Upgrade Configuration page.

12. Click Upgrade.

13. On the Job Schedule page, click one of the following:

• Run Immediately: To perform the job.• Schedule later: To perform the job at a scheduled time.

14. Click Schedule.

On the Upgrade Management page, the Update status and Last Action Status fieldsdisplay .

15. To view the update status, click .

The Upgrade Job Details page displays the detailed update checks that are in progress.Click Done to close the window.

When the update is complete, the Update status and Last Action Status fields displays .

16. Click Upgrade Actions > Installed Patches.

17. On the Installed Patches page, in the Patch Operation section, click Commit.




The page displays all software patches that you can commit.

You can use Rollback and Uninstall options if you must rollback and uninstall the softwarepatch.

18. Select the patch that you installed, in the Job Schedule section, click Run Immediately.

You can schedule to commit the patch at a later time by using the Schedule later option.

19. Click Schedule.

The Upgrade Management page displays the last action as Commit.

20. Ensure that Update status and Last Action Status fields display .

Editing a virtual machineBefore you begin

• Install the Solution Deployment Manager client.• An ESXi host must be available.• When you change the IP address or FQDN:

- Utility Services must be available and must be discovered.- If Utility Services is discovered, the system must display Utility Services in the VM App

Name column. If the application name in VM App Name is empty, perform the following toestablish trust between the application and System Manager:

• Click More Actions > Re-establish connection.• Click More Actions > Refresh VM.




3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section,select a virtual machine, and click Edit.

The system displays the Edit VMs section.

4. (Optional) Click Change Flexi Footprint and do the following:

a. Click Change flexi foot print value.

b. In Flexi Footprint, select a foot print that the application supports.

Important:

Each application must ensure that only the supported flexible footprint is selected.




5. To update the IP address and FQDN of the virtual machine, perform the following:


Note:

To update IP address or FQDN for Utility Services, establish trust on all virtualmachines that are running on the host on which Utility Services resides.

b. Click More Actions > Refresh VM.

Note:

To update IP address or FQDN for Utility Services, refresh all virtual machines thatare running on the host on which Utility Services resides.

c. Click Update IP/FQDN in Local Inventory.

d. Click Update VM IP/FQDN.

e. Provide the IP address and FQDN of the virtual machine.

Update IPFQDN in Local Inventory updates the IP address or FQDN only in the localdatabase in System Manager. The actual IP address or FQDN of the host does notchange. Use Update Network Params in the Host tab to update the IP address orFQDN of the host.

6. Click Save.

Deleting a virtual machineProcedure



3. On the right navigation pane, click Virtual Machines.

4. On the Virtual Machines page, select one or more virtual machines.

5. On the Delete page, click Delete, and click Yes to confirm the deletion.

The system turns off the virtual machines, and deletes the selected virtual machines from thehost.




Changing the network parameters of Appliance VirtualizationPlatform and Avaya Aura® applications

About this taskChange the network parameters for Appliance Virtualization Platform and each Avaya Aura®

application from the application, and then change the IP address and FQDN of Avaya Aura®

applications and Appliance Virtualization Platform from Solution Deployment Manager.

Before you begin• Connect the system on which Solution Deployment Manager is running to the new network for

changing network parameters.• When many Avaya Aura® applications are running on an Appliance Virtualization Platform host,

ensure that you change the network parameter in the following order:

1. Appliance Virtualization Platform2. Avaya Aura® applications that are running on the host except Utility Services.3. Utility Services

Note:If you fail to follow the order, Utility Services network parameter update might fail.




3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXihost and click Change Network Params > Change Host IP Settings.

4. In the Network Parameters section, change the following as appropriate, and click Save:

• IP address, subnetmask, and other parameters

• Gateway IP address

For more information, see “Change Network Parameters field descriptions”.

5. Change the network parameters first for each Avaya Aura® application on the host, and thenfor Utility Services.

For more information, see Administering Avaya Aura® application available for eachapplication. Also, see “Network Parameters for Avaya Aura® applications”.

6. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, dothe following first for all Avaya Aura® applications except Utility Services, and then for UtilityServices:

a. In the Edit VMs section, select a virtual machine and click Edit.b. Click Update IP/FQDN in Local Inventory.




c. Click Update VM IP/FQDN.

d. Provide the IP address and FQDN of the virtual machine.

Update IPFQDN in Local Inventory updates the IP address or FQDN only in the localdatabase in System Manager. The actual IP address or FQDN of the host does notchange. Use Update Network Params in the Host tab to update the IP address orFQDN of the host.

7. Click Save.

8. Do the following first for all Avaya Aura® applications except Utility Services, and then forUtility Services:


Note:

To update IP address or FQDN for Utility Services, establish trust on all virtualmachines that are running on the host on which Utility Services resides.

b. Click More Actions > Refresh VM.

Note:

To update IP address or FQDN for Utility Services, refresh all virtual machines thatare running on the host where Utility Services resides.

When you update the IP address and FQDN for Utility Services, the system also updates theServices Port static route for each application.

Related linksChange Network Parameters field descriptions on page 56Changing the network parameters for an Appliance Virtualization Platform host on page 47Network parameter update for Avaya Aura applications on page 84

Updating Services Port Static Routing on an Avaya Aura®

applicationAbout this taskYou might have to change the static routing if the Avaya Aura® application that is running on theAppliance Virtualization Platform host is:

• Deployed by using the vSphere client and does not have the route.• Non-operational or unreachable when you start the Avaya Aura® application update.

Before you begin• Update network parameters of Utility Services if applicable.• Ensure that the Avaya Aura® application resides on the same subnetwork as Utility Services.






2. On the Virtual Machines tab, in the VMs for Selected Location <location name> section,select an Avaya Aura® application.

3. Click More Actions > Update Static Routing.

The VM Update Static Routing page displays the details of Avaya Aura® application andUtility Services. The fields are read-only.

4. Click Update.

5. On the Success dialog box, click OK.

The system updates the Avaya Aura® application with the new IP address of Utility Servicesfor Services Port static routing.

Related linksUpdate Static Routing field descriptions on page 82

Starting a virtual machine from Solution Deployment ManagerProcedure


2. From the virtual management tree, select a host to which you added virtual machines.

3. On the Virtual Machines tab, select one or more virtual machines that you want to start.

4. Click Start.

In VM State, the system displays Started.

Stopping a virtual machine from Solution Deployment ManagerAbout this taskSystem Manager is operational and ESXi or vCenter is added to the VM Management page todeploy Avaya Aura® Application OVA on ESXi virtual machines.



2. From the virtual management tree, select a ESXi or vCentre host to which you added virtualmachines.

3. On the Virtual Machines tab, select one or more virtual machines that you want to stop.




4. Click Stop.

In VM State, the system displays Stopped.

Restarting a virtual machine from Solution Deployment ManagerBefore you begin

• System Manager is operational, and ESXi or vCenter is added to the VM Management page todeploy Avaya Aura® Application OVA on ESXi virtual machines.

• Virtual machines must be in the running state.



2. From the virtual management tree, select a host to which you added virtual machines.

3. On the Virtual Machines tab, select one or more virtual machines that you want to restart.

4. Click Restart.

In VM State, the system displays Stopped and then Started.

VM Deployment field descriptionsSelect Location and Host

Name DescriptionSelect Location The location name. The field is display-only.Select Host The hostname of the ESXi host. For example,

smgrdev. The field is display-only.Host FQDN FQDN of the ESXi host.Data Store The data store with the available size.

The page populates the Capacity Details section.Next Displays the Deploy OVA section in the Location &

Host Details screen where you provide the detailsrequired for deployment.

Capacity DetailsThe system displays the CPU and memory details of the host. The fields are read-only.

Note:If the host is in a cluster, the system does not display the capacity details of CPU and memory.Ensure that the host resource requirements are met before you deploy the virtual machine.




Name DescriptionName The nameFull Capacity The maximum capacityFree Capacity The available capacityReserved Capacity The reserved capacityStatus The configuration status

Deploy OVA on System Manager Solution Deployment Manager

Name DescriptionSelect Software Library The software library where the .ova file is available.

Select OVAs The .ova file that you want to deploy.

Flexi Footprint The footprint size supported for the selected host.

Important:

• Ensure that the required memory is availablefor the footprint sizes that you selected. Theupgrade operation might fail due to insufficientmemory.

• Ensure that the application contains thefootprint size values that are supported.

Next Displays the Configuration Parameters tab in theOVA Details screen where you provide the OVAdetails.

Deploy OVA on the Solution Deployment Manager client

Name DescriptionProvide OVA path The option to select a .ova file of the virtual

machine that is available on the system that hoststhe Solution Deployment Manager client.

OVA File The absolute path to the .ova file on the system thathosts the Solution Deployment Manager client.

The field is available only when you click Select theOVA from Local SMGR.

Submit File Selects the .ova file of System Manager that youwant to deploy.

Flexi Footprint The footprint size supported for the selected host.

Important:

Ensure that the required memory is available forthe footprint sizes that you selected. The

Table continues…




Name Description

upgrade operation might fail due to insufficientmemory.

Next Displays the Configuration Parameters tab in theOVA Details screen where you provide the OVAdetails.

Configuration ParametersThe system populates most of the fields depending on the OVA file.

Note:For configuration parameter fields, for Communication Manager Messaging and Utility Services,see VM Deployment Configuration and Network Parameters field descriptions on page 80.

Name DescriptionVM Name The name of the virtual machine.Product The name of the Avaya Aura® application that is

being deployed.

The field is read-only.Version Release number of the Avaya Aura® application that

is being deployed.

The field is read-only.ME Deployment The option to perform the Midsize Enterprise

deployment.

The option is available only while deployingCommunication Manager simplex OVA.

Table 1: Configuration Parameters for Communication Manager simplex OVA deployment

Name DescriptionCM IPv4 Address The IP address of the Communication Manager virtual machine.CM IPv4 Netmask The network mask of the Communication Manager virtual

machine.CM IPv4 Gateway The default gateway of the Communication Manager virtual

machine.Out of Band Management IPv4Address

The IP address of the Communication Manager virtual machinefor out of band management.

The field is optional network interface to isolate managementtraffic on a separate interface from the inband signaling network.

Out of Band Management Netmask The subnetwork mask of the Communication Manager virtualmachine for out of band management.

CM Hostname The hostname of the Communication Manager virtual machine.

Table continues…




Name DescriptionNTP Servers The IP address or FQDN of the NTP server.

Separate the IP addresses with commas (,).DNS Servers The DNS IP address of the Communication Manager virtual

machine.Search Domain List The search list of domain names. For example, mydomain.com.

Separate the search list names with commas (,).WebLM Server IPv4 Address The IP address of WebLM. The field is mandatory.CM Privileged Administrator UserLogin

The login name for the privileged administrator. You can changethe value at any point of time.

CM Privileged Administrator UserPassword

The password for the privileged administrator. You can changethe value at any point of time.

Confirm Password The password required to be confirmed.

Network Parameters

Name DescriptionPublic The port number that is mapped to public port group.

You must configure Public network configurationparameters only when you configure Out of BandManagement. Otherwise, Public networkconfiguration is optional.

Services The port number that is mapped to the services portgroup when Utility Services is deployed in thesolution.

Utility Services provides routing from the servicesport to the virtual machines and additional functions,such as alarm conversion.

Duplication Link The connection for server duplication.

The field is available only when you deploy duplexCommunication Manager.

Out of Band Management The port number that is mapped to the out of bandmanagement port group.

Button DescriptionDeploy Displays the EULA acceptance screen where you

must click Accept to start the deployment process.

Related linksVM Deployment Configuration and Network Parameters field descriptions on page 80




VM Deployment Configuration and Network Parameters fielddescriptions

Table 2: Configuration Parameters for Communication Manager Messaging deployment

Name DescriptionMessaging IPv4 address The IP address of the Communication Manager Messaging

virtual machine.Messaging IPv4 Netmask The network mask of the Communication Manager Messaging

virtual machine.Messaging IPv4 Gateway The default gateway of the Communication Manager Messaging

virtual machine. For example, 172.16.1.1.Out of Band Management IPv4Address

The IP address of the Communication Manager Messagingvirtual machine for out of band management.

The field is optional network interface to isolate managementtraffic on a separate interface from the inbound signalingnetwork.

Out of Band Management IPv4Netmask

The subnetwork mask of the Communication ManagerMessaging virtual machine for out of band management.

Messaging Hostname The hostname of the Communication Manager Messaging virtualmachine.

NTP Servers The IP address or FQDN of the NTP server.

Separate the IP addresses with commas (,). The field is optional.DNS Server(s) The DNS IP address of the Communication Manager Messaging

virtual machine. Separate the IP addresses with commas(,). Thefield is optional.

Search Domain List The search list of domain names. For example,

mydomain.com. Separate the search list names with commas (,).WebLM Server IPv4 Address The IP address of WebLM. The field is mandatory.Messaging Privileged AdministratorUser Login

The login name for the privileged administrator.

You can change the value at any point of time.Messaging Privileged AdministratorUser Password

The password for the privileged administrator.

You can change the value at any point of time.Confirm Password The password required to be confirmed.

Configuration and Network Parameters for Utility Services deploymentName DescriptionConfiguration Parameters

Table continues…




Name DescriptionCommunication Manager IP IP address of Communication Manager.

Note:

A unique Communication Manager IP address is required foreach Utility Services. If you are not associated with aCommunication Manager server, specify a static IP that is inyour network range.

Hostname Linux hostname or fully qualified domain name for Utility Servicesvirtual machine.

TImezone setting The selected timezone setting for the Utility Services virtual machine.NTP Server IP IP address of a server running Network Time Protocol that

Communication Manager can use for time synchronization.Out of Band Management Mode The Out of Band Management mode in which you want to deploy.

The options are as follows:

• OOBM_Enabled: To enable Out of Band Management.

• OOBM_Disabled: To disable Out of Band Management.

Note:

OOBM_Disabled is the default setting. If the mode is set toOOBM_Disabled, then you do not need to configure Out ofBand Management.

Utility Services Mode The mode in which you want to deploy Utility Services. The optionsare:

• Services Port Only: Deploys Services Port only. Use when thecustomer already has Utility Services running on another virtualmachine and providing the services.

With the services port feature, through a laptop connected to theservices port of Appliance Virtualization Platform, you can gainaccess to Avaya virtual machines and the hypervisor that aredeployed.

• Utility Servers Only: Use to disable routing. Set this mode only forVirtualized Environment. If you set this mode for an Avayaappliance, the services port becomes non-operational.

• Full Functionality: Utility Services and services port enabled. Thedefault mode for Appliance Virtualization Platform.

You can set the mode only during the deployment. You cannotchange the mode after the virtual machine is deployed.

Note:

For the Solution Deployment Manager client to connect to theservices port features of Utility Services, change the IP addressto 192.11.13.5 on the computer of the technician

Table continues…




Name Description

Utility Services can gain access to the hypervisor and all virtualmachines. Utility Services provides application routing betweenthe physical port and virtual applications.

Primary System Manager IPaddress for applicationregistration

The IP address of System Manager that is required for applicationregistration.

Enrollment Password The enrollment password.Confirmation password The confirmation password.Network ParametersDefault Gateway The IP address of the default gateway.

Required field unless you use DHCP.DNS The IP address of domain name servers for the Utility Services virtual

machine. Separate each IP address by a comma.

Required field unless you use DHCP.Public IP address The IP address for this interface.

Required field unless you use DHCP.Public Netmask The netmask for this interface.

Required field unless you use DHCP.Out of Band Management IPAddress

The IP address for this interface.

Out of Band ManagementNetmask

The netmask for this interface.

Update Static Routing field descriptionsName DescriptionVM Name The virtual machine nameVM IP/FQDN The IP address or FQDN of the virtual machineUtility Services IP The IP address of Utility Services

Button DescriptionUpdate Updates the static IP address for routing.




Installed Patches field descriptionsButton DescriptionAction to be performed The operation that you want to perform on the

software patch, service pack, or feature pack thatyou installed. The options are:

• All: Displays all the software patches.

• Commit: Displays the software patches that youcan commit.

• Rollback: Displays the software patches that youcan rollback.

Get Info Displays software patches, service packs, andfeature packs that you installed.

Commit Commits the selected software patch.Rollback Rolls back the selected software patch.

Name DescriptionVM Name The name of the System Manager virtual machine on

which you want to install the patch.VM IP The IP address of System Manager on which you

want to install the patch.Patch Name The software patch name that you want to install.Patch Type The patch type. The options are service pack and

software patch.Patch Version The software patch version.Patch State The software patch state. The states are:

• Activated

• Deactivated

• Removed

• InstalledPatch Status The software patch status.

Update VM field descriptionsName DescriptionVM Name The System Manager virtual machine nameVM IP The IP address of System Manager

Table continues…




Name DescriptionVM FQDN FQDN of System ManagerHost Name The host nameSelect bin file from Local SMGR The option to select the software patch or service

pack for System Manager.

The absolute path is the path on the computer onwhich the Solution Deployment Manager client isrunning. The patch is uploaded to System Manager.

This option is available only on the SolutionDeployment Manager client.

Auto commit the patch The option to commit the software patch or servicepack automatically.

If the check box is clear, you must commit the patchfrom More Actions > Installed Patches.

Button DescriptionInstall Installs the software patch or service pack on

System Manager.

Reestablish Connection field descriptionsName DescriptionVM Name The virtual machine nameVM IP/FQDN The IP address or FQDN of the virtual machineUser Name The user namePassword The password

Button DescriptionReestablish Connection Establishes connection between System Manager

and the virtual machine.

Network parameter update for Avaya Aura® applicationsYou can change the network parameters for Avaya Aura® applications that run on an ApplianceVirtualization Platform server.

The commands listed might change. Therefore, from the Avaya Support website at https://support.avaya.com, get the latest command update for an Avaya Aura® application from theappropriate document.



https://support.avaya.com/

https://support.avaya.com/


Tip:On the Avaya Support website navigate to Support by Product > Documents > <Avaya Auraapplication>, type the release number, click Installation, Upgrades & Config, click Enter, andsearch for the updates.

Avaya Aura® application Command Interface where you perform thetask

Appliance Virtualization Platform serverInitialNetworkConfig

CLI

System Manager changeIPFQDN -IP <IPaddress> –FQDN <FQDN> -GATEWAY <Gateway address>-NETMASK <Netmaskaddress> -DNS <DNSaddress> -SEARCH <searchlist of domain names>

CLI or vSphere client

Communication Manager - The Network Configuration pagefrom Administration >server(Maintenance) >ServerConfiguration onCommunication Manager SMI.

Session Manager SMnetSetup vSphere clientAvaya Breeze™ and all installedsnap-ins

- vSphere client

Utility Services VMware_conf.sh CLIAvaya Aura® Media Server - See the Avaya support website.SAL Gateway - Currently, you cannot change

Network Parameters for SALGateway

Certificate validation

Certification validationWith System Manager Solution Deployment Manager and Solution Deployment Manager client, youcan enable a certificate-based TLS connection between the Solution Deployment Manager serviceand a host that is running Avaya Aura® 7.x applications. This enables to establish securecommunications between System Manager Solution Deployment Manager or the SolutionDeployment Manager client and Appliance Virtualization Platform or ESXi hosts.




The certificate-based sessions apply to the Avaya Aura® Virtualized Appliance offer using host self-signed certificates and the customer-provided Virtualization Environment using host self-signed orthird party certificates.

You can check the following with certificate based TLS sessions:

• Certificate valid dates• Origin of Certificate Authority• Chain of Trust• CRL or OCSP state• Log Certificate Validation Events

Solution Deployment Manager checks the certificate status of hosts. If the certificate is incorrect,Solution Deployment Manager does not connect to the host.

For the correct certificate:

• The fully qualified domain or IP address of the host to which you are connecting must matchthe value in the certificate and the certificate must be in date.

• Appliance Virtualization Platform and VMware ESXi hosts do not automatically regenerate theircertificates when host details such as IP address or hostname and domain changes. Thecertificate might become incorrect for the host.

If the certificate is incorrect:

• For the Appliance Virtualization Platform host, Solution Deployment Manager regenerates thecertificate on the host and then uses the corrected certificate for the connection.

• For the VMware ESXi host or vCenter, the system denies connection. The customer mustupdate or correct the certificate on the host or vCenter.

For more information about updating the certificate, see “Updating the certificate on the ESXihost from VMware”.

Note:Solution Deployment Manager:

• Validates certificate of vCenter• Does not validate certificates for hosts that vCenter manages

With Solution Deployment Manager, you can only accept certificate while adding vCenter. If acertificate changes, the system gives a warning that the certificate does not match the certificate inthe trust store on Solution Deployment Manager. You must get a new certificate, accept thecertificate as valid, and save the certificate on the system.

To validate certificates, you can directly log on to the host and confirm that the details in the /etc/vmware/ssl/rui.crt file match the details displayed on the screen.




Generating and accepting certificatesAbout this taskWith Solution Deployment Manager, you can generate certificates only for Appliance VirtualizationPlatform hosts.

For the VMware ESXi hosts, if the certificate is invalid:

• Get a correct certificate for the host and add the certificate.• Regenerate a self-signed certificate on the host.

For more information, see “Generating new self-signed certificates for the ESXi host”.

Before you beginRequire permissions to add a host to generate certificates.





4. Click More Actions > Generate/Accept Certificate.

5. On the Certificate window, do the following:

a. Click Generate Certificate.

Note:

You can generate certificate only for the Appliance Virtualization Platform host.

b. Click Accept Certificate.

In the Hosts for Selected Location <location name> section, the Host Certificate columnmust display .

Next stepsIf the system displays an SSL verification error when you gain access to the Appliance VirtualizationPlatform host from the vSphere client, restart the Appliance Virtualization Platform host.

Related linksAdding an ESXi host on page 44Generating new self-signed certificates for the ESXi host on page 90




Updating the certificate on the ESXi host from VMwareAbout this taskUse the procedure to update the ESXi host certificate.

For information about updating vCenter certificates, see the VMware documentation.

Before you beginStart an SSH session on the ESXi host.

Procedure1. Start vSphere client, and log in to the ESXi host as admin or root user.

2. Ensure that the domain name and the hostname of the ESXi host is set correctly andmatches the FQDN that is present on the DNS servers, correct the entries to match ifrequired.

For security reason, the common name in the certificate must match the hostname to whichyou connect.

3. To generate new certificates, type /sbin/generate-certificates.

The system generates and installs the certificate.

4. Restart the ESXi host.

5. (Optional) Do the following:

a. Move the ESXi host to the maintenance mode.

b. Install the new certificate.

c. From the Direct Console User Interface (DCUI), restart management agents.

Note:

The host certificate must now match the fully qualified domain name of the host.

VMware places only FQDN in certificates that are generated on the host. Therefore,use a fully qualified domain name to connect to ESXi hosts and vCenter fromSolution Deployment Manager.

Appliance Virtualization Platform places an IP address and FQDN in generatedcertificates. Therefore, from Solution Deployment Manager, you can connect toAppliance Virtualization Platform hosts through IP address or FQDN.

The connection from Solution Deployment Manager 7.0.1 to a vCenter or ESXi hostby using an IP address fails because the IP address is absent in the certificate andthe connection is not sufficiently secure.

Related linksGenerating new self-signed certificates for the ESXi host on page 90




Managing certificates for existing hostsAbout this taskBy default, the certificate status of the host or vCenter that is migrated from earlier release is invalid.To perform any operation on the host from Solution Deployment Manager, you require a validcertificate. Therefore, you must get the valid certificate and accept the certificate.

Depending on the host type and the validity of the certificate, use appropriate steps to generate thecertificate, and then accept the certificate.

Before you beginRequire permissions to add a host to generate certificates.




3. On the Host tab, in the Host for Selected Location <location name>, select a host.

4. (Optional) On an Appliance Virtualization Platform host, click More Actions > Generate/Accept Certificate, and on the Certificate dialog box, do one of the following:

• If the certificate is valid, click Accept Certificate.

• If the certificate is invalid, click Generate Certificate, and then click Accept Certificate.

5. For the ESXi host, do one of the following:

• If the certificate is valid, on the Certificate dialog box, click More Actions > Generate/Accept Certificate, and click Accept Certificate.

• If the certificate is invalid, log in to the ESXi host, validate the certificate, and then fromSolution Deployment Manager, accept the certificate.

For more information, see “Generating new self-signed certificates for the ESXi host”.

6. For vCenter, do the following:

a. Click Map vCenter, select the vCenter server, and click Edit.

b. In the Certificate dialog box, accept certificate, and click Save.

Related linksGenerating new self-signed certificates for the ESXi host on page 90Generating and accepting certificates on page 87




Generating new self-signed certificates for the ESXi hostAbout this taskGenerate new certificates only if you change the host name or accidentally delete the certificate.Under certain circumstances, you must force the host to generate new certificates.

To receive the full benefit of certificate checking, particularly if you want to use encrypted remoteconnections externally, do not use a self-signed certificate. Instead, install new certificates that aresigned by a valid internal certificate authority or purchase a certificate from a trusted securityauthority.

Before you beginStart an SSH session on the ESXi host.

Procedure1. Log in to the ESXi host as an admin user.

2. To create a backup of any existing certificates, in the /etc/vmware/ssl directory, renamethe certificates by using the following commands:mv rui.crt orig.rui.crtmv rui.key orig.rui.key

Note:

Do not perform the step if you are regenerating certificates because you deleted thecertificates.

3. To generate new certificates, type /sbin/generate-certificates.

4. Restart the ESXi host.

The generation process places the certificates places in the correct location.

5. (Optional) Do the following:

a. Move the ESXi host to the maintenance mode.

b. Install the new certificate.

c. Restart management agents from Direct Console User Interface (DCUI).

6. Do the following to confirm that the host successfully generated new certificates:

a. Type ls -la.

b. Compare the time stamps of the new certificate files with orig.rui.crt andorig.rui.key.

Next stepsReplace the self-signed certificate and the key with a trusted certificate and key.




Managing vCenter

Adding a vCenter to Solution Deployment ManagerAbout this taskSystem Manager Solution Deployment Manager supports virtual machine management in vCenter5.0, 5.1, 5.5, and 6.0. When you add vCenter, System Manager discovers the ESXi hosts that thisvCenter manages, adds to the repository, and displays in the Managed Hosts section. Also, SystemManager discovers virtual machines running on the ESXi host and adds to the repository.

System Manager displays vCenter, ESXi host, and virtual machines on the Manage Elements page.

Before you beginEnsure that you have the required permissions.



2. In the lower pane, click Map vCenter.

3. On the Map vCenter page, click Add.

4. In the New vCenter section, provide the following vCenter information:

• vCenter FQDN

For increased security when using a vCenter with Solution Deployment Manager, use anFQDN for the vCenter. vCenter does not put IP addresses in its certificates. Therefore,you need FQDN to confirm the server identity through the certificate in SolutionDeployment Manager.

• User Name

• Password

• Authentication Type

5. Click Save.

6. On the certificate dialog box, click Accept Certificate.

The system generates the certificate and adds vCenter.

In the Managed Hosts section, the system displays the ESXi hosts that this vCentermanages.

Related linksEditing vCenter on page 92Map vCenter field descriptions on page 93New vCentre and Edit vCentre field descriptions on page 94

Managing vCenter



Editing vCenterBefore you beginEnsure that you have the required permissions.




3. On the Map vCenter page, select a vCenter server and click Edit.

4. In the Edit vCenter section, change the vCenter information as appropriate.

5. If vCenter is migrated from earlier release, on the Certificate page, click Accept Certificate,and click Save.

6. To edit the location of ESXi hosts, in the Managed Hosts section, do one of the following:

• Select an ESXi host and click the edit icon ( ).

• Select one or more ESXi hosts, select the location, and click Bulk Update and clickUpdate.

If you do not click Commit after you move the host from Managed Hosts to UnmanagedHosts or vice versa, and you refresh the table, the page displays the same host in both thetables. Click Commit to get an updated list of managed and unmanaged hosts.

Deleting vCenter from Solution Deployment ManagerBefore you beginEnsure that you have the required permissions.




3. On the Map vCenter page, select one or more vCenter servers and click Delete.

4. Click Yes to confirm the deletion of servers.

The system deletes the vCenter from the inventory.




Map vCenter field descriptionsName DescriptionName The name of the vCenter server.IP The IP address of the vCenter server.FQDN The FQDN of the vCenter server.

Note:

Use FQDN to successfully map and log in tovCenter from Solution Deployment Manager.With IP address, the system displays an errormessage about the incorrect certificate anddenies connection.

License The license type of the vCenter server.Status The license status of the vCenter server.Certificate Status The certificate status of the vCenter server. The

values are:

• : The certificate is correct.


Button DescriptionView Displays the certificate status details of the vCenter

server.Generate/Accept Certificate Displays the certificate dialog box where you can

generate and accept certificate for vCenter.

For vCenter, you can only accept certificate. Youcannot generate certificate.

Button DescriptionAdd Displays the New vCenter page, where you can add

a new ESXi host.Edit Displays the Edit vCenter page, where you can

update the details and location of ESXi hosts.Delete Deletes the ESXi host.Refresh Updates the list of ESXi hosts in the Map vCenter

section.

Managing vCenter



New vCentre and Edit vCentre field descriptionsName DescriptionvCenter FQDN FQDN of vCenter.User Name The user name to log in to vCenter.Password The password that you use to log in to vCenter.Authentication Type The authentication type that defines how Solution

Deployment Manager performs user authentication.The options are:

• SSO: Global username used to log in to vCenter toauthenticate to an external Active Directoryauthentication server.

• LOCAL: User created in vCenter

Button DescriptionSave Saves any changes you make to FQDN, username,

and authentication type of vCenter.Refresh Refreshes the vCenter details.

Managed Hosts

Name DescriptionHost IP/FQDN The name of the ESXi host.Host Name The IP address of the ESXi host.Location The physical location of the ESXi host.Edit The option to edit the location and host.Bulk Update Provides an option to change the location of more

than one ESXi hosts.

Note:

You must select a location before you click BulkUpdate.

Update Saves the changes that you make to the location orhostname of the ESXi host.

Commit Commits the changes that you make to the ESXihost with location that is managed by vCenter.

Unmanaged Hosts

Name DescriptionHost IP/FQDN The name of the ESXi host.

Table continues…




Name DescriptionESXi Version The version of the ESXi host. The options are: 5.0,

5.1, 5.5, and 6.0.

Button DescriptionCommit Saves all changes that you made to vCenter on the

Map vCenter page.

Monitoring a host and virtual machine

Monitoring a hostProcedure


2. Click the Monitor Hosts tab.

3. In the Monitor Hosts page, do the following:

a. In Hosts, click a host.

b. Click Generate Graph.

The system displays the graph regarding the CPU/memory usage of the host that youselected.

Monitoring a virtual machineProcedure


2. Click the Monitor VMs tab.

3. In the Monitor VMs page, do the following:

a. In Hosts, click a host.

b. In Virtual machines, click a virtual machine on the host that you selected.

4. Click Generate Graph.

The system displays the graph regarding the CPU/memory usage of the virtual machine thatyou selected.

Monitoring a host and virtual machine



Chapter 6: Installing software patches,service packs, and feature packsfor applications

Installing software patchesAbout this taskUse the procedure to install software patches, service packs, and feature packs that are entitled foran Avaya Aura® application, and commit the patches that you installed.

Before you begin• Perform the preupgrade check.• If you upgrade an application that was not deployed from Solution Deployment Manager:

1. Select the virtual machine.2. To establish trust, click More Actions > Re-establish Connection.3. Click Refresh VM.


2. In the left navigation pane, click Upgrade Management.

3. Select an Avaya Aura® application on which you want to install the patch.

4. Click Upgrade Actions > Upgrade/Update.

5. On the Upgrade Configuration page, click Edit.

6. In the General Configuration Details section, in the Operation field, click Update.

7. In Upgrade Source, select the software library where you have downloaded the patch.

8. (Optional) Click the Auto Commit check box, if you want the system to automaticallycommit the patch.

Note:

If an application is unreachable, the auto commit operation might fail and the UpdatePatch Status window displays a warning message. You must wait for some time, select



the same patch in the Installed Patches section, and perform the commit operationagain.

9. In the Upgrade Configuration Details section, in the Select patches for update table, selectthe software patch that you want to install.

10. Click Save.

11. On the Upgrade Configuration page, ensure that the Configuration Status field displays .

If the field displays , review the information on the Edit Upgrade Configuration page.

12. Click Upgrade.

13. On the Job Schedule page, click one of the following:

• Run Immediately: To perform the job.

• Schedule later: To perform the job at a scheduled time.

14. Click Schedule.

On the Upgrade Management page, the Update status and Last Action Status fieldsdisplay .

15. To view the update status, click .

The Upgrade Job Details page displays the detailed update checks that are in progress.Click Done to close the window.

When the update is complete, the Update status and Last Action Status fields displays .

16. Click Upgrade Actions > Installed Patches.

17. On the Installed Patches page, in the Patch Operation section, click Commit.

The page displays all software patches that you can commit.

You can use Rollback and Uninstall options if you must rollback and uninstall the softwarepatch.

18. Select the patch that you installed, in the Job Schedule section, click Run Immediately.

You can schedule to commit the patch at a later time by using the Schedule later option.

19. Click Schedule.

The Upgrade Management page displays the last action as Commit.

20. Ensure that Update status and Last Action Status fields display .

Installing software patches



Installed Patches field descriptionsName DescriptionCommit The option to select the patches that you can

commit.Uninstall The option to select the patches that you can

uninstall.Rollback The option to select the patches that you can

rollback.Show All The option to display all the available options.

Name DescriptionName The name of the software patch.Element Name The element on which the software patch is installed.Patch Version The version of the software patch.Patch Type The type of the software patch. The options are:

• service pack or software patch

• KernelPatch State The state of the software patch. The options are:

• Installed

• Activated

• Deactivated

• Removed

• Uninstall

• Pending

Name DescriptionSchedule Job The option to schedule a job:

• Run immediately: To run the upgrade jobimmediately.

• Schedule later: To run the upgrade job at thespecified date and time.

Date The date on which you want to run the job. The dateformat is mm:dd:yyyy. Use the calendar icon tochoose a date.

This field is available when you select the Schedulelater option for scheduling a job.

Table continues…

Installing software patches, service packs, and feature packs for applications



Name DescriptionTime The time when you want to run the job. The time

format is hh:mm:ss and 12 (AM or PM) or 24-hourformat.


Time Zone The time zone of your region.


Name DescriptionSchedule Runs the job or schedules to run at the time that you

configured in Job Schedule.

Installed Patches field descriptions



Chapter 7: Out of Band Managementconfiguration

Avaya Aura® Out of Band ManagementOut of Band Management is defined as a physical or logical separation of user and managementtraffic, either to different VLANs or different physical interfaces on the server for increased securityof the system. Only administrator can gain access to the management interfaces from a specificnetwork, users of the system cannot gain access. This prevents unauthorized login from the usernetwork to applications.

Only the ports and servers that are required for user functions are provided to the user network.Management interfaces are provided to the management network. In Out of Band Managementsetup, an administrator username and password is not sufficient to gain access to the system. Thelogin attempt must also be able to access the Out of Band Management network.

When out of band management is enabled, Avaya Aura® applications run:

• User services on one network interface. For example, IP phone registration, user configuration,and media traffic

• Management services on another network interface. For example, administration webpages,SSH connections, and management traffic from System Manager.



The following Avaya Aura® applications support Out of Band Management starting in Release 7.0:

• Communication Manager• Session Manager• System Manager• Application Enablement Services• Avaya Breeze™ with Presence• Appliance Virtualization Platform• SAL• Utility Services• Branch Session Manager• WebLM

Avaya Aura® Media Server and Avaya Diagnostic Server does not support the Out of BandManagement feature.

Appliance Virtualization Platform Out of BandManagement

OverviewWhen you install Appliance Virtualization Platform, the public network of virtual machines isassigned to vmnic0 or Server Ethernet port 1 of the server.

In the installation spreadsheet, if Out of Band Management is:

• Disabled: The public and management interfaces of virtual machines are assigned on thepublic network. Assign public and management interfaces of virtual machines on the samenetwork.

• Enabled: The public interfaces of virtual machines are assigned to vmnic0 or Server Ethernetport 1, and the Out of Band Management interfaces are assigned to vmnic2 or Server Ethernetport 3. Assign separate network ranges to the public and management interfaces of virtualmachines. The management port must be given an appropriate IP address of the public andOut of Band Management network.

Note:All virtual machines on an Out of Band Management enabled Appliance VirtualizationPlatform host must support and implement Out of Band Management.

When Out of Band Management is:

• Disabled: The management port of Appliance Virtualization Platform is assigned to the publicinterface.

• Enabled: The management port of Appliance Virtualization Platform is assigned to the Out ofBand Management network.

Appliance Virtualization Platform Out of Band Management



The vmnic1 or Server Ethernet port 2 of the server is assigned to the services port.

The hypervisor is 192.168.13.6 on the services port network (VMNIC1 or eth1).

After Utility Services OVA is deployed, from your computer by using an SSH client, gain access tothe Utility Services shell from the services port with the following:

• IP Address: 192.11.13.5 or 192.11.13.30• Gateway: 192.11.13.6

You can access the Utility Services shell by using the IP Address 192.11.13.6.

Note:An Appliance Virtualization Platform host and all virtual machines running on the host must beon the same subnet mask.

If Out of Band Management is configured in an Appliance Virtualization Platform deployment,you need two subnet masks, one for each of the following:

• Public or signaling traffic, Appliance Virtualization Platform, and all virtual machines publictraffic.

• Management, Appliance Virtualization Platform, and all virtual machine management ports.

Common serversWhen Appliance Virtualization Platform is installed, VMNIC0 is assigned to the public interface ofvirtual machines.

When deploying or reconfiguring Appliance Virtualization Platform, if Out of Band Management is:

• Disabled: VMNIC0 is used for both network and management traffic.• Enabled: VMNIC2 is used for management by all the virtual machines on that hypervisor.

S8300DWhen you install the connection through the media gateway using Appliance Virtualization Platform ,Ethernet ports are assigned to the public interface of the virtual machines. When you install theconnection through the media gateway backplane using Appliance Virtualization Platform, the LANport on the G4x0 Gateway is assigned to the public interface of virtual machines.

If Out of Band Management is enabled, the Out of Band Management network is assigned to aseparate VLAN on the public interface. Otherwise all virtual machine interfaces are on the samenetwork.

The Appliance Virtualization Platform management interface is assigned to:

• The public VLAN if Out of Band Management is disabled• The Out of Band Management VLAN if Out of Band Management is enabled

Note:To support Out of Band Management on S8300D, you require specific versions of gatewayfirmware. To ensure that you are running the correct version, see the gateway documentation.

S8300EWhen Appliance Virtualization Platform installs the connection through the media gateway, Ethernetports are assigned to the public interface of virtual machines. When Appliance Virtualization

Out of Band Management configuration



Platform installs the connection through the media gateway backplane, the LAN port on the G4x0Gateway is assigned to the public interface of virtual machines.

If Out of Band Management is enabled, the Out of Band Management network is on the LAN2interface on the S8300E faceplate.

The Appliance Virtualization Platform management interface is assigned to:

• The public VLAN if Out of Band Management is disabled• The Out of Band Management network if Out of Band Management is enabled

Out of Band Management in Virtualized EnvironmentIn the Virtualized Environment offer where the customer has control of the hypervisor network setup,the customer creates the desired networking and assigns the virtual Ethernet port of the applicationson deployment. Public interfaces are assigned to the user network port groups and Out of BandManagement ports are assigned to the management network port group.

Utility Services Out of Band ManagementOut of Band Management is a physically and logically separate network connection. It connects to acustomer’s private IT management network and provides for secure management andadministration of Avaya products.

From Utility Services Release 7.0.1, you can activate out-of-band management even afterdeployment.

Utility Services Release 7.0.1 and later support a full out of band management configuration.Therefore, you can deploy Utility Services with two IP addresses and split the user andmanagement traffic to different Ethernet interfaces on different IP networks.

When Utility Services is set for out of band management, the following services are allocated for fullor Utility Services-only mode:

Application Interfaces for trafficPhone firmware download PublicPhone settings file PublicGateway firmware download PublicDHCP Server PublicMyphone User PublicSSH Out of Band Management / Services

Table continues…

Out of Band Management in Virtualized Environment



Application Interfaces for trafficMyphone Admin Out of Band ManagementCDR connection to CM Out of Band ManagementMain admin web pages Out of Band Management / ServicesAlarm source Out of Band ManagementSAL connection (SSH, HTTP) Out of Band Management

When Utility Services is set for out of band management, the following services are allocated forservices port-only mode:

Application Interfaces for trafficSSH Out of Band Management / ServicesAlarm source Out of Band ManagementSAL connection (SSH, HTTP) Out of Band ManagementMain admin web pages DisabledPhone firmware download DisabledGateway firmware download DisabledPhone settings DisabledGateway firmware download DisabledDHCP Server DisabledMyphone Server DisabledCDR connection to CM DisabledMyphone admin Disabled

Note:

If a network is not mentioned for service when Out of Band Management is enabled, the servicemust be disabled on that interface.

System Manager Out of Band Management

Out of Band Management in System ManagerSystem Manager provides the following network interfaces:

• The regular eth0 interface that was present in releases earlier than System Manager Release7.0, is called the Management interface or Out of Band Management interface. The IP addressis called as the Management IP address. The Management interface is mandatory forconfiguration.




The following are the examples of System Manager Management network traffic:

- Database replication with Session Manager- Element management. For example, Session Manager, Communication Manager, and

Avaya Breeze™.- User management- Solution deployment, upgrades, and software patch install

• If Out of Band Management is enabled, then the public interface is configured with Public IPaddress and used for the nonmanagement traffic. This is an optional configuration.

The following are the examples of System Manager nonmanagement or public network traffic:

- End-user self-provisioning- Client devices getting certificates through SCEP- Tenant Management

Out of Band Management configuration persists across System Manager upgrades, updates, andrestarts.

For configuring Out of Band Management in System Manager, System Manager must be installedon an Appliance Virtualization Platform host that is configured with Out of Band Management. Out ofBand Management is enabled during the deployment of Appliance Virtualization Platform.

Out of Band Management in a Geographic Redundancy setupWhen you configure Geographic Redundancy, provide Management network details only. Validationfails if you configure Geographic Redundancy with Public network details. In GeographicRedundancy setup, you do not disable or enable Out of Band Management on both primary andsecondary System Manager virtual machine. You can enable Out of Band Management on theprimary System Manager virtual machine and disable Out of Band Management on the secondarySystem Manager virtual machine, and vice versa.

Restoring System Manager backupWhile restoring backup on System Manager with different Out of Band Management network details,the restore operation fails at validation phase.

Tenant Management on Out of Band Management-enabled System ManagerBy default, the Multi Tenancy feature is disabled on System Manager when Out of BandManagement is enabled. You must enable Multi Tenancy on Out of Band Management-enabledSystem Manager for the Tenant Management administrator to manage tenant users.

Configuring Out of Band Management on System ManagerAbout this taskIf you do not configure Out of Band Management during the deployment of System Manager OVAfrom Solution Deployment Manager on an Avaya-provided server, you can use theconfigureOOBM command to configure Out of Band Management anytime after the deployment.

Before you begin• Enable Out of Band Management on Appliance Virtualization Platform.




• Install System Manager on the Appliance Virtualization Platform host on which Out of BandManagement is installed.

• Ensure that IP address or hostname of Public network and Management network are different.

If both are in the same network, Out of Band Management configuration might not function asexpected.

• Log in to System Manager by using an SSH client utility.

When you enable Out of Band Management configuration, you might lose the connection asthe system does a network restart. You can login to System Manager from the Console ofVMware vSphere Client. that is configured to connect to the Appliance Virtualization Platformhost server.

Procedure1. To enable Out of Band Management, type configureOOBM -EnableOOBM.

The system enables Out of Band Management on the System Manager virtual machine.With EnableOOBM, the system configures the additional Ethernet interface, updates networkconfiguration, and sets the firewall rules.

2. To disable Out of Band Management, type configureOOBM -DisableOOBM.

The system disables Out of Band Management on the System Manager virtual machine.With DisableOOBM, the system disables the additional Ethernet interface that youconfigured earlier and sets the firewall rules to default.

3. To add the IP address and subnet ranges in the Management IP range, typeconfigureOOBM -AddIPtoManagementIPRange.

You can now gain access to System Manager from the network.

Configuring Out of Band Management on System Manager in theGeographic Redundancy setup

About this taskNote:You cannot enable Out of Band Management on secondary System Manager server when Outof Band Management on primary System Manager server is disabled.

Before you beginIdentify one of the following:

• Enable Out of Band Management on both the primary and secondary System Manager server.• Enable Out of Band Management on the primary System Manager server and not enable Out

of Band Management on the secondary System Manager server.• Disable Out of Band Management on secondary System Manager server.• Disable Out of Band Management on both the primary and secondary System Manager server.




Procedure1. To enable Out of Band Management on both primary and secondary System Manager

server, perform the following:

a. Disable Geographic Redundancy replication on primary System Manager server.

b. Convert primary System Manager server to standalone System Manager server andactivate the secondary System Manager server.

c. Enable Out of Band Management on both primary and secondary System Managerserver.

d. Reconfigure the Geographic Redundancy on the secondary System Manager server.

e. Enable Geographic Redundancy replication on primary System Manager server.

2. To enable Out of Band Management on the primary System Manager server and not enableOut of Band Management on secondary System Manager server, perform the following:


b. Convert primary System Manager server to standalone System Manager server.

c. Enable Out of Band Management on primary System Manager server.

d. Once Out of Band Management on primary System Manager server is enabled,reconfigure Geographic Redundancy on secondary System Manager server.


3. To disable Out of Band Management on secondary server, perform the following:


b. Convert primary System Manager server to standalone System Manager server.

c. Activate secondary System Manager server and disable Out of Band Management.

d. Reconfigure primary System Manager server from the web console of the secondarySystem Manager server.


4. To disable Out of Band Management on both servers, perform the following:


b. Convert primary System Manager server to standalone System Manager server anddisable Out of Band Management.

c. Activate secondary System Manager server and disable Out of Band Management.

d. Reconfigure Geographic Redundancy on secondary System Manager server with oldprimary System Manager server which is now standalone.





Communication Manager Out of Band ManagementWith the Out of Band Management feature, you can set up a dedicated network connection tosecurely manage Communication Manager. The network connection can be physical or virtual.

Detailed description of Out of Band ManagementCommunication Manager has a virtual NIC for a dedicated Ethernet connection for managementfunctions. You can use System Management Interface (SMI) to manage the Avaya products usingthis dedicated Ethernet connection. The dedicated network connection administration persists aftera Communication Manager upgrade.

With the dedicated network connection, you can create separate channels for the user functions andthe management functions. You can use the dedicated network connection for the managementfunctions to manage the system, perform IA scans, and update the firmware. You can also use thenetwork connection for other network services such as system logging, backup, NTP, and WebLMlicensing. For the user functions, you can set up more specific user access controls. You can alsohave more specific auditing processes to detect insider threats.

Out of Band Management management administrationTo configure the Out of Band Management of management data on Communication Manager, youmust do the following:

• Depending on your Communication Manager configuration, assign an IP address and asubnetwork mask to the eth1 or eth2 Ethernet connection.

• Select Out of Band Management as the functional assignment.• Enable Out of Band Management of management data.• Add a static route between the Out of Band Management interface and the enterprise network.

Screens for administering Out-of-Band managementScreen name Purpose FieldsNetwork Configuration Configure the IP address and the

subnetwork mask to administerthe Ethernet connection.

• IPv4 Address

• Mask

• Functional Assignment

• Restrict Management traffic toOut-of-Band interface iscurrently

Table continues…




Screen name Purpose FieldsStatus Routes Create a static route between the

Out-of-Band managementinterface and the enterprisenetwork to route all managementfunction data through the Out-of-Band management interface.

• IP Address

• Mask / Prefix

• Gateway

• Interface

Administering the Out of Band Management of management dataProcedure

1. Log in to Communication Manager SMI.

2. Click Administration > Server (Maintenance).

3. In the navigation pane, click Server Configuration > Network Configuration.

4. Configure the following eth1 fields:

• IPv4 Address: The IP address of the Ethernet connection

• Mask: The subnetwork mask of the IP address

• Functional Assignment: Out-of-Band Management

If the Communication Manager instance is a duplex configuration, configure the eth2 fields.

5. Verify that you can gain access to Communication Manager using the Out-of-Band Ethernetinterface.

Important:

You must be able to gain access to Communication Manager using the Out of BandManagement Ethernet interface before you perform the next step.

6. Add a static route between the Out of Band Management interface and the enterprisenetwork.

You must ensure that you add a static route between the Out of Band Management interfaceand the enterprise network to restrict access. For more information, see “Add a static routebetween the Out of Band Management interface and the enterprise network”.

7. From the Restrict Management traffic to Out-of-Band interface is currently drop-downlist, select enabled.

Note:

Restrict Management traffic to Out-of-Band interface is set to enabled. RestrictManagement traffic to Out-of-Band will restrict traffic on ports 80, 443, 22, 2222, 5022,23, 5023, 161, and 162 to the management interface only.

Communication Manager Out of Band Management



Port restrictionWhen the Restrict Management traffic to Out-of-Band field is set to enable, the system restrictstraffic on the following ports:

Port Use22 ssh23 telnet80 http161 snmp162 snmp trap443 https2222 high priority ssh5022 sat over ssh5023 sat over telnet

Adding a static route between the Out-of-Band managementinterface and the enterprise network

About this taskCreate a static route between the Out-of-Band management interface and the enterprise network toroute all management functions data through the Out-of-Band management interface.

Procedure1. Log in to Communication Manager SMI.

2. Click Administration > Server (Maintenance).

3. In the navigation pane, click Server Configuration > Static Routes.

4. Configure the following fields:

• IP Address: Enter the enterprise network IP address.

• Mask / Prefix: Enter the subnetwork mask of the network IP address.

• Gateway: Enter the gateway address.

• Interface: Select eth1. If the Communication Manager instance is a duplex configuration,select eth2.

5. Click Add Route.




Session Manager Out of Band Management portsComponent Interface DescriptionSecurity Module (secmod) th1(public IP) The interface that manages SIP

and HTTP traffic to and from theWebSphere Application Server(WAS) traffic. Security Module isthe front-end of Session Managerrunning Linux operating system6.5 with Avaya proprietaryapplications providing SIPprotection, TLS termination, andfirewall.

WebSphere (WAS) eth0 (public IP) A converged JSR289 containerthat processes SIP messagesreceived from SIP entities orendpoints.

Management Agent (MGMT) eth0 (public IP) A management console that isused to listen on port 8643 for anHTTPS connection to add,remove, restart, or monitorSession Manager.

SAL-Agent eth0 (public IP) A Java application that receivesevents and collects inventoryinformation from the product andconverts them to its own internalformat. It then encapsulates themessage into HTTPS and sendsthe information to an EnterpriseServer, usually at Avaya.

Data Replication Service (DRS) eth0 (public IP) A service that synchronizesdatabase changes betweenSystem Manager and SessionManager. DRS uses HTTPS forreplication messages. JMX is usedfrom remote management.

For information on Management Port and Security Port, see Session Manager Port Matrix.

Application Enablement Services Out of BandManagement

Out of Band Management provides the ability to move the AE Services Management Console Webbased management and configuration traffic of the server to a dedicated subnetwork.

Session Manager Out of Band Management ports



Table 3: Application Enablement Services Out of Band Management

Component Interface DescriptionDMCC Service Eth0 (public IP) The Device, Media, and Call Control (DMCC) service provides

both, first-party and third-party call control features using a JavaAPI. It also provides XML and .NET interfaces. Additionally,DMCC provides the integration for Microsoft LCS 2005, OCS2007, LYNC, and Sametime. TCP/IP, TLS and SIP protocolsmay used to connect a DMCC Client to DMCC.

DLG Service Eth0 (public IP) The DEFINITY LAN Gateway (DLG) service tunnels messagesover TCP/IP. That is, the DLG service supports a set of TCP/IPconnections for the communications channel between AvayaAura® Communication Manager and AE Services. The DLGservice is also used for transporting ASAI/Q.931 messages.

CVLAN Service Eth0 (public IP) The CallVisor LAN (CVLAN) service is a C/C++ based API thatenables applications to exchange ASAI messages with the AEServices Server. CVLAN provides a full complement of third-party call control capabilities such as controlling specific calls orstations, completing routing of incoming calls, receivingnotifications of events, invoking features, and querying AvayaAura® Communication Manager for information.

TSAPI Service Eth0 (public IP) The Telephony Services API (TSAPI) is a C/C++ based API thatprovides a full complement of third party call control capabilities.The Java Telephony API (JTAPI) is a client side interface to theTSAPI service. It provides third party call control.

Transport Service Eth0 (public IP) A Transport link is a secure TCP/IP connection between the AEServices server and a CLAN or Processor Ethernet board onAvaya Aura® Communication Manager.

SystemManagementService

Eth0 (public IP) Listens on port 443 for HTTPS connection to provide users aweb interface to enable SOAP-based access to Avaya Aura®

Communication Manager administration functions.Telephony WebService

Eth0 (public IP) Listens on port 8443 and 443 for HTTPS connection to provideusers a web interface that enables high level call controlfunctionality over standard web services interfaces (SOAP/XML).

AES ManagementConsole

Eth0 (public IP)

or

Eth2 (Out of BandMgmt IP)

The Application Enablement Services Management Consolelistens on port 443 for HTTPS connections, and provides anOperations, Administration and Management interface formaintenance of the AE Services server. The default interface iseth0, unless Out-of-Band Management has been configured.

Out of Band Management in Avaya Breeze™

Avaya Breeze™ always has two IP addresses that reside on the same or different IP networksdepending on the Out of Band Management network.




The IP addresses for the security and management interface must be on:

• Same IP address network if Out of Band Management is disabled

• Different IP address networks if Out of Band Management is enabled

Out of Band Management in SALFrom Release 2.5, SAL supports Out of Band Management setups, but runs management interfaceson both public and SAL interfaces.

No.

DefaultDestinationPort

(Configurable Range)

Network /Application

Protocol

Optionally

Enabled/

Disabled?

DefaultPortState

ExternalDevice

Description Notes

INGRESS CONNECTIONS1 22 TCP/SSH No Open Admin

terminalSystem managementrequiring shell access.

INGRESS CONNECTIONS (LOAD BALANCER TO SAL STC)1 9443

(1-65535)

TCP/HTTPS No Open LoadBalancer

The port on which theSTC listens for incomingremote connectionrequests.

EGRESS CONNECTIONS1 443

(1-65535)

TCP/HTTPS No N/A SAL CoreServer

The port on which theSAL Core server listensfor requests. Hence,configure the value mustaccordingly in the stc-config.propertiesfile.

1,2

These ports run against both interfaces.

Note:

Avaya Diagnostic Server does not support Out of Band Management.

Out of Band Management in SAL



Chapter 8: Post Installation Verification

Verifying the installation of System ManagerAbout this taskPerform the following verification procedure after you install System Manager Release 7.0.1 andconfigure System Manager.

Procedure1. On the web browser, type https:// <fully qualified domain name of System

Manager>, and ensure that the system displays the System Manager web console.

2. On the upper-right corner, click and click About.

The system displays the About SMGR window with the build details.

3. Verify the System Manager version number.

Post installation checklistPerform the following steps to verify the Session Manager OVA installation.

No. Task Description1 Verify the connections of the deployed

Session Manager.2 Upgrade Session Manager to the latest

release.Deploying Session Manager on VMWare

3 Run the maintenance tests on thedeployed Session Manager. Administering Avaya Aura® Session Manager

4 Verify data replication.5 Upgrade the Session Manager VMware

tools.Deploying Session Manager on VMWare



Verifying the connectionsAbout this taskVerify the connections of the deployed Session Manager and Branch Session Manager.

ProcedureOn the home page of the System Manager Web Console, in Elements, click Session Manager.

Verifying the connections



Chapter 9: Postinstallation tasks

Loading a customer-specific authentication fileAbout this taskAvaya provides the default authentication file for Appliance Virtualization Platform. You mustdownload the customer-specific authentication file from the Authentication File System website.

Procedure1. To gain access to the Avaya RFA Home page, type http://rfa.avaya.com in the web browser.

2. Log on to the RFA Home page.

3. Click Start the AFS Application.

4. On the license page, click I Agree.

5. In the Product field, select Appliance Virtualization Platform.

6. In the Release field, click 7.x.

7. Click Next.

8. On the Deliver an Authentication File page, perform one of the following:

• To create an authentication file for a new system, click New System - Product:<Appliance Virtualization Platform Release: 7.x>.

• To create an authentication file for an upgrade or re-delivery for an existing system, clickUpgrade or Re-deliver for Existing System or re-deliver for existing system -Product: <Appliance Virtualization Platform Release: 7.x>, and type the authenticationfile ID.

9. Click Next.

10. Ensure that SSH is enabled on the Appliance Virtualization Platform host, and if required,enable SSH through Utility Services.

For more information, see “Activating SSH” to Appliance Virtualization Platform.

11. Click Download file to my PC.

12. Using WinSCP or a similar application, copy the authentication file on to the ApplianceVirtualization Platform system by using the root account and the password set at installation.

13. Using PuTTy or a similar SSH client, log in to Appliance Virtualization Platform by using theroot account and the password set at installation.


http://rfa.avaya.com


14. Type /opt/avaya/bin/loadauth -l AF-7001064472-150430-131707.xml -o /etc/asg/lacfile.

Where AF-7001064472-150430-131707.xml, is the authentication file name and –l.isthe location where the system downloaded the xml file. Always include the -o option as –o /etc/asg/lacfile.

15. Using the SSH client, log in to Appliance Virtualization Platform as sroot, and view theupdated product ID displayed with the ASG challenge.

Downloading and installing an authentication file on theAvaya Aura® application

About this taskAvaya provides the default authentication file for an application. You must download the customer-specific authentication file from the AFS website.

Each Avaya Aura® application has a unique method to install an authentication file. For example,for:

• Communication Manager by using System Management Interface.• Utility Services by using the web interface.• Session Manager by using shell, log in to Session Manager with customer login account that is

defined during deployment, and use command loadpwd.

Therefore, use an appropriate procedure that applies to an Avaya Aura® application.

This is an example procedure for downloading the authentication file.

Note:Do not use this procedure to download the authentication file for Utility Services.

Procedure1. To gain access to the Avaya RFA Home page, type http://rfa.avaya.com in the web browser.

2. Log on to the RFA Home page.

3. Click Start the AFS Application.

4. On the license page, click I Agree.

5. In the Product field, click <Avaya Aura application name>.

Where <Avaya application> is the application that you want to deploy or upgrade.

6. In the Release field, click 7.x.

7. Perform one of the following:

• To create new authentication file for new installation, click New System - Product:<Avaya Aura application name Release: 7.x>.

Downloading and installing an authentication file on the Avaya Aura® application


http://rfa.avaya.com


• To create new authentication file for an upgrades system, click Upgrade or Re-deliver forExisting System or re-deliver for existing system - Product: <Avaya Auraapplication name Release: 7.x>, and type the authentication file ID.

8. In the Enter the fully qualified domain name field, type FQDN or retain the default value.

9. Click Download file to my PC or Download file via email.

Depending on the selection, the system downloads the authentication file on your computeror sends the file through email.

10. Using an appropriate procedure, copy the authentication file to the Avaya Aura® application.

11. Using an appropriate procedure that applies to an Avaya Aura® application, get theauthentication file.

For example, for Appliance Virtualization Platform type ./opt/avaya/bin/loadauth -lAF-7001064472-150430-131707.xml -o /etc/asg/lacfile.

Where AF-7001064472-150430-131707.xml is the authentication file name –l is thelocation where the system downloaded the xml file. Always include –o option as –o /etc/asg/lacfile.

12. Using the SSH client, log in to the application, and view the updated product ID displayedwith the ASG challenge.

Postinstallation tasks



Chapter 10: Resources

DocumentationThe following table lists the documents related to this product. Download the documents from theAvaya Support website at http://support.avaya.com.

Title Use this document to: AudienceOverviewAvaya Aura® Virtualized EnvironmentSolution Description

Understand the high-level solution featuresand functionality

Customers and sales,services, and supportpersonnel

Avaya Aura® System ManagerOverview and Specification

Understand the high-level solution featuresand functionality

Customers and sales,services, and supportpersonnel

AdministeringAdministering Avaya Aura® SystemManager for Release 7.0.1

Perform administration tasks Systemadministrators

Administering Network Connectivityon Avaya Aura® CommunicationManager, 555-233-504

Administer the network components ofCommunication Manager.

Systemadministrators

Administering Avaya Aura®

Communication Manager, 03-300509Administer CommunicationManagercomponents, such as trunks,signalling groups, and dial plans. Set uptelephony features, such as conferencing,transfer, and messaging.CommunicationManager.


UsingUsing the Solution DeploymentManager client

Deploy Avaya Aura® applications and installpatches on Avaya Aura® applications.


ImplementingUpgrading Avaya Aura® SystemManager to Release 7.0.1

Install and configure Avaya applications Implementationpersonnel

Migrating and Installing AvayaAppliance Virtualization Platform

Install Appliance Virtualization Platform onAvaya-provided servers, and migrate thedata from System Platform to ApplianceVirtualization Platform.

Implementationpersonnel

Table continues…




Title Use this document to: AudienceTroubleshootingTroubleshooting Avaya Aura®

System ManagerPerform troubleshooting tasks System

administrators and ITpersonnel

Related linksFinding documents on the Avaya Support website on page 120

Finding documents on the Avaya Support websiteAbout this taskUse this procedure to find product documentation on the Avaya Support website.

Procedure1. Use a browser to navigate to the Avaya Support website at http://support.avaya.com/.

2. At the top of the screen, enter your username and password and click Login.

3. Put your cursor over Support by Product.

4. Click Documents.

5. In the Enter your Product Here search box, type the product name and then select theproduct from the drop-down list.

6. If there is more than one release, select the appropriate release number from the ChooseRelease drop-down list.

7. Use the Content Type filter on the left to select the type of document you are looking for, orclick Select All to see a list of all available documents.

For example, if you are looking for user guides, select User Guides in the Content Typefilter. Only documents in the selected category will appear in the list of documents.

8. Click Enter.

Related linksDocumentation on page 119

TrainingThe following courses are available on the Avaya Learning website at www.avaya-learning.com.After logging into the website, enter the course code or the course title in the Search field and clickGo to search for the course.

Resources


http://support.avaya.com/

http://www.avaya-learning.com


Course code Course titleAvaya Aura® core implementation1A00234E Avaya Aura® Fundamental Technology4U00040E Avaya Aura® Session Manager and System Manager Implementation4U00030E Avaya Aura® Communication Manager and Communication Manager Messaging

Implementation10U00030E Avaya Aura® Application Enablement Services Implementation8U00170E Avaya Aura® Presence Services Implement and SupportAVA00838H00 Avaya Aura® Media Server and Media Gateways Implementation WorkshopATC00838VEN Avaya Aura® Media Server and Gateways Implementation Workshop LabsAvaya Aura® core support5U00050E Session Manager and System Manager Support5U00060E ACSS - Avaya Aura® Communication Manager and CM Messaging Support4U00115I

4U00115V

Avaya Aura® Communication Manager Implementation Upgrade (R5.x to R6.x)

1A00236E Avaya Aura® Session Manager and System Manager Fundamentals2008W What is New in Avaya Aura® Application Enablement Services 7.02008T What is New in Avaya Aura® Application Enablement Services 7.0 Online Test2009W What is New in Avaya Aura® Communication Manager 72009T What is New in Avaya Aura® Communication Manager 7.0 Online Test2010W What is New in Avaya Aura® Presence Services 7.02010T What is New in Avaya Aura® Presence Services 7.0 Online Test2011W What is New in Avaya Aura® Session Manager and Avaya Aura® System Manager

7.02011T What is New in Avaya Aura® Session Manager and Avaya Aura® System Manager

7.0 Online Test2013V Avaya Aura® 7 AdministrationAvaya Aura® core administration and maintenance9U00160E Avaya Aura® Session Manager for System Administrators1A00236E Avaya Aura® Session Manager and Avaya Aura® System Manager Fundamentals5U00051E Avaya Aura® Communication Manager Administration5M00050A Avaya Aura® Communication Manager Messaging Embedded Administration,

Maintenance & Troubleshooting2012V Migrating and Upgrading to Avaya Aura® 7.02012I Migrating and Upgrading to Avaya Aura® 72017 Avaya Aura® 7 Administration Delta2017V Avaya Aura® 7 Administration Delta

Training



Viewing Avaya Mentor videosAvaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avayaproducts.

About this taskVideos are available on the Avaya Support website, listed under the video document type, and onthe Avaya-run channel on YouTube.

Procedure• To find videos on the Avaya Support website, go to http://support.avaya.com and perform one

of the following actions:

- In Search, type Avaya Mentor Videos to see a list of the available videos.

- In Search, type the product name. On the Search Results page, select Video in theContent Type column on the left.

• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor andperform one of the following actions:

- Enter a key word or key words in the Search Channel to search for a specific product ortopic.

- Scroll down Playlists, and click the name of a topic to see the available list of videos postedon the website.

Note:

Videos are not available for all products.

SupportGo to the Avaya Support website at http://support.avaya.com for the most up-to-datedocumentation, product notices, and knowledge articles. You can also search for release notes,downloads, and resolutions to issues. Use the online service request system to create a servicerequest. Chat with live agents to get answers to questions, or request an agent to connect you to asupport team if an issue requires additional expertise.

Resources


http://support.avaya.com/

http://www.youtube.com/AvayaMentor



Glossary

ApplianceVirtualizationPlatform

Appliance Virtualization Platform is the customized OEM version ofVMware® ESXi 5.5. With Appliance Virtualization Platform, customers canrun any combination of supported applications on Avaya-supplied servers.Appliance Virtualization Platform provides greater flexibility in scalingcustomer solutions to individual requirements.

Appliance Virtualization Platform is available only in an Avaya-applianceoffer. Avaya-appliance offer does not support VMware® tools, such asvCenter and vSphere Client. You can configure and manage ApplianceVirtualization Platform by using Solution Deployment Manager that is part ofSystem Manager, or by installing the Solution Deployment Manager client.

Migration The migration process includes changing the server hardware, change theoperating system, and reinstallation of software that includes hypervisor.

During migration, you might need to perform backup and restore operationsoutside the normal upgrade process. You cannot rollback the upgradeeasily.

Update The update process includes installing patches of an application. Forexample, kernel patches, security patches, hotfixes, service packs, andfeature packs.

Upgrade The upgrade process includes upgrading a product from earlier release tothe latest release without the need to change the server hardware orhypervisor.

The process is triggered through the normal process without requiringadditional backup and restore operations. You can rollback an upgrade.



Index

Special Characters/sbin/generate-certificates ....................................................90

Aaccess Solution Deployment Manager ................................ 29access Solution Deployment Manager client .......................19add

virtual machine ................................................. 61, 76, 80adding

Appliance Virtualization Platform host .......................... 44AVP host .......................................................................44ESXi host ......................................................................44location ......................................................................... 37vCenter to SDM ............................................................ 91

adding certificatesavailable hosts ..............................................................89existing hosts ................................................................89migrated hosts .............................................................. 89

adding ESXi host ................................................................. 44adding location .....................................................................37adding location to host .........................................................92adding vCenter to SDM ....................................................... 91add virtual machine ..................................................61, 76, 80administering

Out-of-Band management .......................................... 109Out-of-Band management static route ....................... 110

administrationOut-of-Band management .......................................... 108

Appliance Virtualization Platform ......... 11, 32, 48, 52, 57, 116change password ......................................................... 51install ............................................................................ 30networking .................................................................. 101restarting .......................................................................55shutting down ............................................................... 54update .....................................................................45, 59

Appliance Virtualization Platform and Utility Services ......... 23Appliance Virtualization Platform host Gateway

change ..........................................................................47edit ................................................................................47

Appliance Virtualization Platform host IP addresschange ..........................................................................47edit ................................................................................47

Appliance Virtualization Platform host passwordchanging ....................................................................... 51

Appliance Virtualization Platform network parameters ........ 47Appliance Virtualization Platform overview ..........................11ASG file ..............................................................................116ASG file installation on Appliance Virtualization Platform ..116ASG file installation on Avaya Aura application .................117authentication file

ASG file ...................................................................... 117

download ............................................................ 116, 117install .................................................................. 116, 117

Avaya Aura applicationdeploy ........................................................................... 20Services Port static routing update ...............................74upgrade ........................................................................ 20

Avaya Aura application deployment .................................... 13Avaya Aura applications

Network Parameters change ........................................ 84Avaya Aura Virtualized Appliance offer ............................... 11Avaya virtualization platform ................................................11Avaya Virtualized offers ....................................................... 11

Ccapabilities

Solution Deployment Manager client ......................15, 19certificates

accepting ...................................................................... 87generating .....................................................................87

certificate updateESXi host ......................................................................88vCenter ......................................................................... 88VMware documentation ................................................88

Certification validation ..........................................................85change

Appliance Virtualization Platform host IP address ........47Host/ IP Settings ...........................................................48network settings ............................................................57Network Settings .......................................................... 48

Change Gateway ................................................................. 56change IP address for AVP host ..........................................47Change IP FQDN .................................................................71change Netmask for Appliance Virtualization Platform host 47Change Network Params .....................................................47changing

IP address and default gateway ................................... 53changing Appliance Virtualization Platform host password . 51changing Network Parameters for Avaya Aura ....................84checklist

Avaya Aura applications deployment ........................... 27client Solution Deployment Manager ................................... 13Communication Manager deployment using SolutionDeployment Manager .......................................................... 27Communication Manager update ...................................69, 96Configuration Parameters ..............................................76, 80configure server preinstalled with Appliance VirtualizationPlatform ............................................................................... 32configuring

Out of Band Management .................................. 100, 113configuring Out of Band Management on System Manager....................................................................................105, 106connections



connections (continued)verifying ...................................................................... 115

correcting ESXi host certificate ............................................88create

virtual machine ....................................................... 59, 67creating authentication file ................................................. 116

Ddeleting

ESXi host ......................................................................55location ......................................................................... 38virtual machine ............................................................. 72

deleting ESXi host ............................................................... 55deleting location ...................................................................38deleting vCenter ...................................................................92delivering authentication file .............................................. 116deploy

Branch Session Manager ....................................... 27, 67Communication Manager ....................................... 27, 67product knowledge ......................................................... 9Session Manager ....................................................27, 67skills ................................................................................9System Manager .................................................... 59, 67tools ................................................................................ 9Utility Services ........................................................ 27, 67

deploy application ................................................................ 22deploy Avaya Aura 7.0 application ...................................... 67deploy Avaya Aura applications

checklist ........................................................................27Deploying an OVA file

utility services ............................................................... 65deployment

Avaya Aura application .................................................13deploy OVA ....................................................................59, 67detailed description

Out-of-Band management .......................................... 108disabling

SSH on Appliance Virtualization Platform .................... 52disabling SSH ...................................................................... 52documentation ................................................................... 119download

ASG file ...................................................................... 116authentication file ........................................................116

download software ...............................................................36

Eedit

virtual machine ....................................................... 71, 73Edit Host .............................................................................. 56editing

ESXi host ......................................................................45location ......................................................................... 38vCenter ......................................................................... 92

editing ESXi host ................................................................. 45editing location .....................................................................38

editing vCenter .....................................................................92Edit Location ........................................................................ 43Edit vCenter ......................................................................... 94edit virtual machine ..............................................................71enabling

SSH on Appliance Virtualization Platform .................... 52enabling SSH .......................................................................52esxcfg-route ......................................................................... 53esxcli network ip interface ipv4 set -i vmk0 -I ...................... 53ESXi host

adding ...........................................................................44deleting ......................................................................... 55editing ........................................................................... 45

ESXi host certificate addition ............................................... 89ESXi host certificate update .................................................88ESXi host map to unknown location .................................... 55existing hosts

managing certificates ....................................................89existing vCenter

managing certificates ....................................................89

Ffield descriptions

change password ......................................................... 58Edit Host ....................................................................... 56Edit Location .................................................................43Hosts ............................................................................ 38Locations ...................................................................... 38Map vCenter ................................................................. 93New Host ...................................................................... 56New Location ................................................................43Virtual Machines ........................................................... 38VM Deployment ................................................ 61, 76, 80

fresh deploymentAvaya Aura application .................................................13

Ggenerating

certificates .................................................................... 87new self-signed certificates for ESXi host .................... 90

Hhardware supported .............................................................25host ................................................................................ 48, 57

monitoring .....................................................................95Host

update ...........................................................................59Hosts ....................................................................................38

Iinstall

Application Enablement Services ................................. 16

Index



install (continued)ASG file .............................................................. 116, 117authentication file ................................................116, 117Avaya Aura applications ............................................... 16Avaya Aura Media Server .............................................16Avaya Breeze ............................................................... 16Branch Session Manager ............................................. 16Communication Manager ............................................. 16SAL ...............................................................................16SDM ..............................................................................16Session Manager ..........................................................16Solution Deployment manager client ............................16System Manager .......................................................... 16WebLM ......................................................................... 16

install Appliance Virtualization Platform ...............................30install AVP host patch

Solution Deployment Manager ..................................... 45Installed Patches ................................................................. 98Installed Patches field descriptions ......................................83install patches ................................................................ 69, 96install services packs ..................................................... 69, 96install software patches ................................................. 69, 96Install System Manager patch ............................................. 83IP address and default gateway

changing ....................................................................... 53

Llegal notice ...............................................................................Life cycle management ........................................................22location

adding ...........................................................................37deleting ......................................................................... 38editing ........................................................................... 38view .............................................................................. 37

Locations ............................................................................. 38

MManagement interface ....................................................... 104managing certificates migrated hosts .................................. 89map ESXi host to unknown location .................................... 55Map vCenter .................................................................. 91–94migrated hosts

managing certificates ....................................................89monitoring

host ...............................................................................95virtual machine ............................................................. 95VM ................................................................................ 95

Nnetworking

Appliance Virtualization Platform ................................101network parameters

change ..........................................................................56

Network Parameters change ............................................... 84network parameters for AVP and virtual machines

change ..........................................................................73New Host ............................................................................. 56New Location ....................................................................... 43New vCenter ........................................................................ 94

Ooffer

Avaya appliance ........................................................... 11Virtualized Environment ................................................11

out of band management ...................................................103Out of Band management ..................................................108Out of Band Management ..........................................100, 104

Application Enablement Services ............................... 111Avaya Breeze ............................................................. 112disable ........................................................................ 105enable .........................................................................105Geographic Redundancy ............................................106Network interface configurations ........................ 103, 111ports ............................................................................111SAL .............................................................................113Virtualized Environment ..............................................103

Out-of-Band managementadding a static route ................................................... 110administering .............................................................. 109administration overview .............................................. 108administration screens ................................................108description .................................................................. 108

Ppassword

change ..........................................................................58password change

Appliance Virtualization Platform host .......................... 51password policy ................................................................... 51password rules .....................................................................51perform System Manager tests ..........................................114port restriction .................................................................... 110Post Installation Checklist ..................................................114preinstall Appliance Virtualization Platform ..........................32product knowledge .................................................................9Public interface .................................................................. 104

Rreestablish

connection .................................................................... 84Reestablish Connection .......................................................38related documentation ....................................................... 119removing location from host .................................................92removing vCenter ................................................................ 92restart

virtual machine ............................................................. 76

Index



restarting, AVP .....................................................................55restart virtual machine from SDM ........................................ 76

Sscreens

Out-of-Band management .......................................... 108SDM

installation .....................................................................16SDM client ........................................................................... 14SDM client capabilities .........................................................19SDM client dashboard ......................................................... 19Select Flexi Footprint ........................................................... 71self-signed certificates for ESXi host

generate ....................................................................... 90servers supported ................................................................ 25Services Port static route update .........................................74Session Manager

Out of Band Management ports ................................. 111Session Manager update ...............................................69, 96shutting down

AVP .............................................................................. 54skills to deploy ....................................................................... 9software

download ...................................................................... 36software library

software library management ....................................... 35viewing a file ................................................................. 35

software requirements ......................................................... 25Solution Deployment Manager .......................... 13, 20, 51, 52

access .......................................................................... 29restart virtual machine .................................................. 76start ...............................................................................29start virtual machine ..................................................... 75stop virtual machine ......................................................75update Appliance Virtualization Platform host .............. 45

Solution Deployment Manager client ............................. 13, 14install ............................................................................ 16

Solution Deployment Manager client capabilities .......... 15, 19Solution Deployment Manager client dashboard ................. 19start

virtual machine ............................................................. 75start Solution Deployment Manager .................................... 29start virtual machine from SDM ........................................... 75static routing

changing ....................................................................... 74updating ........................................................................74

stopvirtual machine ............................................................. 75

stop virtual machine from SDM ............................................75support ...............................................................................122supported servers ................................................................ 25System Manager

deploy ........................................................................... 59installing patches .......................................................... 64Solution Deployment Manager ..................................... 64Virtual Machines ........................................................... 64

VM Management .......................................................... 64System Manager documentation ....................................... 119System Manager installation

verify ........................................................................... 114System Manager Solution Deployment Manager and clientcapabilities ........................................................................... 15System Manager VM management ..................................... 83System Manager VM update ............................................... 83

Ttools to deploy ........................................................................9training ............................................................................... 120

UUnknown location host mapping ..........................................55update

Appliance Virtualization Platform ..................................59Appliance Virtualization Platform host .......................... 45Communication Manager ....................................... 69, 96Session Manager ....................................................69, 96

update software ............................................................. 69, 96update static routing ............................................................ 82Update Static Routing ..........................................................38update System Manager VM ............................................... 83Update VM IP/FQDN ........................................................... 73updating ESXi host or vCenter certificate ............................ 88updating Services Port static routing ................................... 74upgrade

elements ....................................................................... 98upgrade Avaya Aura application ..........................................20Utility Services

Avaya Aura virtualized appliance offer ......................... 23Utility Services and Appliance Virtualization Platform ......... 23

VvCenter

add ................................................................................94adding ...........................................................................91add location .................................................................. 92deleting ......................................................................... 92edit ................................................................................94editing ........................................................................... 92manage .........................................................................92remove location ............................................................ 92removing .......................................................................92unmanage .....................................................................92

vCenter certificate update ....................................................88vCentre ................................................................................ 93verify

System Manager installation ...................................... 114verifying

connections ................................................................ 115videos ................................................................................ 122

Index



viewlocation ......................................................................... 37

view location ........................................................................ 37virtual machine

create ......................................................................59, 67deleting ......................................................................... 72edit ................................................................................71monitoring .....................................................................95restart ........................................................................... 76start ...............................................................................75stop ...............................................................................75

Virtual machine management .............................................. 22Virtual Machines .................................................................. 38VM connection reestablish ...................................................84VM Deployment ....................................................... 61, 76, 80VMware software requirements ........................................... 25

Index

