Deploying Avaya Aura Communication Manager in Virtual Appliance

Transcription

1 Deploying Avaya Aura Communication Manager in Virtual Appliance Release 8.0 Issue 2 August 2018

2 Contents Chapter 1: Introduction... 5 Purpose... 5 Prerequisites... 5 Change history... 6 Chapter 2: Architecture overview... 7 Avaya Aura Virtualized Appliance overview... 7 Appliance Virtualization Platform overview... 7 Virtual Appliance components... 9 Chapter 3: Planning and preconfiguration Planning checklist Configuration tools and utilities Supported servers Latest software updates and patch information Downloading software from PLDS Supported footprints of Communication Manager in virtual appliance Chapter 4: Predeployment tasks Installing the Solution Deployment Manager client on your computer Accessing the Solution Deployment Manager client dashboard Accessing Solution Deployment Manager Uploading a file to the software library Managing the location Viewing a location Adding a location Editing the location Deleting a location New and Edit location field descriptions Managing the host Adding an Appliance Virtualization Platform or ESXi host Appliance Virtualization Platform license Shutting down the Appliance Virtualization Platform host Restarting Appliance Virtualization Platform or an ESXi host Removing an Appliance Virtualization Platform or ESXi host Add and Edit platform field descriptions Chapter 5: Deploying Communication Manager on the Avaya-provided server Deployment checklist Deploying the Communication Manager OVA file by using Solution Deployment Manager Application Deployment field descriptions Managing the application Editing an application August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 2

3 Contents Starting an application from Solution Deployment Manager Stopping an application from Solution Deployment Manager Restarting an application from Solution Deployment Manager Common causes for application deployment failure Update Static Routing field descriptions Reestablish Connection field descriptions Virtual machine report Applying the Communication Manager patch using SMI Chapter 6: Configuring Communication Manager IPv6 configuration Enabling IPv Disabling IPv SAL Gateway Chapter 7: Postdeployment verification Installation tests Verifying the license status Accessing Communication Manager System Management Interface Viewing the license status License Status field descriptions Verifying the software version Verifying the survivable virtual machine registration Support for Enhanced Access Security Gateway Enabling or disabling EASG through the CLI interface Enabling or disabling EASG through the SMI interface Viewing the EASG certificate information EASG product certificate expiration EASG site certificate Chapter 8: Maintenance Viewing the job history of virtual machine operations Job History field descriptions Monitoring a host and virtual machine Monitoring a platform Monitoring an application Deleting the virtual machine snapshot from the Appliance Virtualization Platform host Chapter 9: Resources Communication Manager documentation Finding documents on the Avaya Support website Avaya Documentation Portal navigation Training Viewing Avaya Mentor videos Support Using the Avaya InSite Knowledge Base Appendix A: PCN and PSN notifications August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 3

4 Contents PCN and PSN notifications Viewing PCNs and PSNs Signing up for PCNs and PSNs August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 4

5 Chapter 1: Introduction Purpose This document: describes the procedures for deploying the Avaya Aura Communication Manager virtual application on Appliance Virtualization Platform in Virtual Appliance. includes deployment, configuration, deployment verification, troubleshooting, and basic maintenance checklists and procedures. does not include optional or customized aspects of a configuration. The primary audience for this document is anyone who deploys, configures, and verifies Avaya Aura Communication Manager at a customer site. Prerequisites Before deploying Communication Manager, ensure that you have the following knowledge, skills, and tools. Knowledge Skills Linux Operating System Communication Manager To administer the Communication Manager System Management interface. Tools For information about tools and utilities, see Configuration tools and utilities. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 5

6 Introduction Change history Issue Date Summary of changes 2 August 2018 Updated the CPU speed in the Supported footprints of Communication Manager in virtual appliance section. 1 July 2018 Initial version. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 6

7 Chapter 2: Architecture overview Avaya Aura Virtualized Appliance overview Avaya Aura Virtualized Appliance is a turnkey solution. Avaya provides the hardware, all the software including the VMware hypervisor and might also offer the customer support of the setup. Virtualized Appliance offer is different from Avaya Aura Virtualized Environment, where Avaya provides the Avaya Aura application software and the customer provides and supports the VMware hypervisor and the hardware on which the hypervisor runs. Deployment considerations Deployment on the Appliance Virtualization Platform server is performed from the System Manager Solution Deployment Manager or the Solution Deployment Manager standalone Windows client. Avaya provides the servers, Appliance Virtualization Platform, which includes the VMware ESXi hypervisor. Appliance Virtualization Platform overview From Release 7.0, Avaya provides the VMware -based Avaya Aura Appliance Virtualization Platform to provide virtualization for Avaya Aura applications. Avaya Aura Virtualized Appliance offer includes: Common Servers: Dell PowerEdge R620, Dell PowerEdge R630, HP ProLiant DL360p G8, and HP ProLiant DL360 G9 Avaya S8300E Note: - With WebLM Release 7.x and later, you cannot deploy WebLM on S8300E Server running on Appliance Virtualization Platform. - Common Servers using ESXi 6.0 can require more memory than System Platform or ESXi 5.5. For memory validation process, see PSN027060u or the Release Notes. Appliance Virtualization Platform is the customized OEM version of VMware ESXi 6.0. With Appliance Virtualization Platform, customers can run any combination of supported applications on Avaya-supplied servers. Appliance Virtualization Platform provides greater flexibility in scaling customer solutions to individual requirements. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 7

8 Architecture overview From Avaya Aura Release 7.0 and later, Appliance Virtualization Platform replaces System Platform. You can deploy the following applications on Appliance Virtualization Platform: AVP Utilities 8.0 System Manager 8.0 Session Manager 8.0 Branch Session Manager 8.0 Communication Manager 8.0 Application Enablement Services 8.0 WebLM 8.0 Communication Manager Messaging 7.0 For information about other Avaya product compatibility information, go to support.avaya.com/compatibilitymatrix/index.aspx. Note: For deploying Avaya Aura applications on Appliance Virtualization Platform only use Solution Deployment Manager. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 8

9 Virtual Appliance components Virtual Appliance components Software component ESXi Host Appliance Virtualization Platform Solution Deployment Manager Open Virtualization Appliance (OVA) Description The physical machine running the ESXi Hypervisor software. Avaya-provided virtualization turnkey solution that includes the hardware and all the software including the VMware hypervisor. Centralized software management solution of Avaya that provides deployment, upgrade, migration, and update capabilities for the Avaya Aura virtual applications. The virtualized OS and application packaged in a single file that is used to deploy a virtual machine. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 9

10 Chapter 3: Planning and preconfiguration Planning checklist Complete the following tasks before deploying the Avaya Aura application OVA on Appliance Virtualization Platform: No. Task Link/Notes 1. Download the required software and patches. 2. Purchase and obtain the required licenses. 3. Register for PLDS, and activate license entitlements. Downloading software from PLDS on page 11 Latest software updates and patch information on page 11 Go to the Avaya Product Licensing and Delivery System at plds.avaya.com/. 4. Verify the server compatibility. Supported servers on page Keep the following information handy to create a backup on the remote server: IP address Directory User Name Password Configuration tools and utilities To deploy and configure the Communication Manager Open Virtualization Application (OVA), you need the following tools and utilities: A remote computer running the vsphere client. A browser for accessing the Communication Manager System Management Interface pages. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 10

11 Supported servers Communication Manager SMI supports Internet Explorer 11 and later and Mozilla Firefox 45.0 and later. Communication Manager KVM OVA, see Release version of Communication Manager OVAs. An SFTP client for Windows. For example, WinSCP. An SSH client. For example, PuTTy, PuTTYgen. MobaXterm Supported servers In the Avaya Aura Virtualized Appliance model, Solution Deployment Manager supports the following servers for deployments and upgrades to Release 8.0 and later: Dell PowerEdge R620 HP ProLiant DL360p G8 Dell PowerEdge R630 HP ProLiant DL360 G9 S8300E, for Communication Manager and Branch Session Manager For fresh installations, use Dell PowerEdge R630 or HP ProLiant DL360 G9. Latest software updates and patch information Before you start the deployment or upgrade of an Avaya product or solution, download the latest software updates or patches for the product or solution. For more information, see the latest release notes, Product Support Notices (PSNs), and Product Correction Notices (PCNs) for the product or solution on the Avaya Support web site at After deploying or upgrading a product or solution, use the instructions in the release notes, PSNs, or PCNs to install any required software updates or patches. For third-party products used with an Avaya product or solution, see the latest release notes for the third-party products to determine if you need to download and install any updates or patches. Downloading software from PLDS When you place an order for an Avaya PLDS-licensed software product, PLDS creates the license entitlements of the order and sends an notification to you. The includes a license August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 11

12 Planning and preconfiguration activation code (LAC) and instructions for accessing and logging into PLDS. Use the LAC to locate and download the purchased license entitlements. In addition to PLDS, you can download the product software from using the Downloads and Documents tab at the top of the page. Note: Only the latest service pack for each release is posted on the support site. Previous service packs are available only through PLDS. 1. Enter in your Web browser to access the Avaya PLDS website. 2. Enter your login ID and password. 3. On the PLDS home page, select Assets. 4. Click View Downloads. 5. Click on the search icon (magnifying glass) for Company Name. 6. In the %Name field, enter Avaya or the Partner company name. 7. Click Search Companies. 8. Locate the correct entry and click the Select link. 9. Enter the Download Pub ID. 10. Click Search Downloads. 11. Scroll down to the entry for the download file and click the Download link. 12. In the Download Manager box, click the appropriate download link. Note: The first link, Click to download your file now, uses the Download Manager to download the file. The Download Manager provides features to manage the download (stop, resume, auto checksum). The click here link uses your standard browser download and does not provide the download integrity features. 13. If you use Internet Explorer and get an error message, click the install ActiveX message at the top of the page and continue with the download. 14. Select a location where you want to save the file and click Save. 15. If you used the Download Manager, click Details to view the download progress. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 12

13 Supported footprints of Communication Manager in virtual appliance Supported footprints of Communication Manager in virtual appliance Product name Communication Manager Simplex small Communication Manager Simplex medium Communication Manager Simplex large Communication Manager Duplex Communication Manager Hi Duplex Footprint (Max users) Release CPU (GHz) Haswell or equivalent Number of vcpus RAM (GB) HDD (GB) NICs (* with OOBM) S8300E or 2* or 2* or 2* or 3* or 3* August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 13

14 Chapter 4: Predeployment tasks Installing the Solution Deployment Manager client on your computer About this task In Avaya Aura Virtualized Appliance offer, when the centralized Solution Deployment Manager on System Manager is unavailable, use the Solution Deployment Manager client to deploy the Avaya Aura applications. You can use the Solution Deployment Manager client to install software patches of only System Manager and hypervisor patches of Appliance Virtualization Platform. Use the Solution Deployment Manager client to deploy, upgrade, and update System Manager. From Avaya Aura Appliance Virtualization Platform Release 7.0, Solution Deployment Manager is mandatory to upgrade or deploy the Avaya Aura applications. 1. Download the Avaya_SDMClient_win64_ _6.zip file from the Avaya Support website at or from the Avaya PLDS website, at 2. On the Avaya Support website, click Support by Products > Downloads, and type the product name as System Manager, and Release as 8.0.x. 3. Click the Avaya Aura System Manager Release 8.0.x SDM Client Downloads, 8.0.x link. Save 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. 4. Right click on the executable, and select Run as administrator to run the Avaya_SDMClient_win64_ _6.exe file. The system displays the Avaya Solution Deployment Manager screen. 5. On the Welcome page, click Next. 6. 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. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 14

15 Installing the Solution Deployment Manager client on your computer 7. On the Install Location page, perform one of the following: To install the Solution Deployment Manager client in the system-defined folder, leave the default settings, and click Next. To specify a different location for installing the Solution Deployment Manager client, click Choose, and browse to an empty folder. Click Next. To restore the path of the default directory, click Restore Default Folder. The default installation directory of the Solution Deployment Manager client is C: \Program Files\Avaya\AvayaSDMClient. 8. On the Pre-Installation 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 the Automatically start SDM service at startup check box. b. To change the default software library directory on windows, in Select Location of Software Library Directory, click Choose and select a directory. The default software library of the Solution Deployment Manager client is C: \Program Files\Avaya\AvayaSDMClient\Default_Artifacts. You can save the artifacts in the specified directory. c. In Data Port No, select the appropriate data port. The default data port is The data port range is from 1527 through d. In Application Port No, select the appropriate application port. The default application port is 443. If this port is already in use by any of your application on your system, then the system does not allow you to continue the installation. You must assign a different port number from the defined range. The application port range is from 443 through 543. Note: After installing the Solution Deployment Manager client in the defined range of ports, you cannot change the port after the installation. e. (Optional) Click Reset All to Default to reset all values to default. 10. Click Next. 11. On the Summary and Validation page, verify the product information and the system requirements. The system performs the feasibility checks, such as disk space and memory. If the requirements are not met, the user must make the required disk space, memory, and the ports available to start the installation process again. 12. Click Install. 13. On the Install Complete page, click Done to complete the installation of Solution Deployment Manager Client. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 15

16 Predeployment tasks Once the installation is complete, the installer automatically opens the Solution Deployment Manager client in the default web browser and creates a shortcut on the desktop. 14. 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 information about Methods to connect the Solution Deployment Manager client to Appliance Virtualization Platform, see Using the Solution Deployment Manager client. Accessing the Solution Deployment Manager client dashboard About this task Note: If you perform deploy, upgrade, and update operations from the Solution Deployment Manager client, ignore the steps that instruct you to access System Manager Solution Deployment Manager and the related navigation links. To start the Solution Deployment Manager client, do one of the following: On your computer, click Start > All Programs > Avaya > Avaya SDM Client. On your desktop, click. Accessing Solution Deployment Manager About this task You require to start Solution Deployment Manager to deploy and upgrade virtual machines, and install service packs or patches. Perform one of the following: If System Manager is not already deployed, double-click the Solution Deployment Manager client. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 16

17 Uploading a file to the software library Note: All the management operation related to System Manager, such as, deployment, patching, or upgrade can only be done by using Solution Deployment Manager Client. If System Manager is available, on the web console, click Services > Solution Deployment Manager. Uploading a file to the software library About this task Use the procedure to upload software files, such as OVA, images, and firmware that are required during the deployment, migration, upgrade, and update of Avaya Aura applications. Before you begin On the 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. 1. 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 the 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 access 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: SHA256 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. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 17

18 Predeployment tasks If the file does not exist in versions.xml, the system does not display the file details. Therefore, you cannot use the file for upgrade in Upgrade Management. You can use the file only for new deployment from Application Management. 6. Select the file. 7. Click Sync. In File Sync Started Message, the system displays the status of the schedule of the job. 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 area and removes from Sync Files from directory. Managing the location Viewing a location 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. Click the Locations tab. The Locations section lists all locations. Adding a location About this task You can define the physical location of the host and configure the location specific information. You can update the information later. 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. On the Locations 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. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 18

19 Managing the location b. In the Optional Location Information section, type the network parameters for the virtual machine. 4. Click Save. The system displays the new location in the Application Management Tree section. Related links New and Edit location field descriptions on page 20 Editing the location 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. On the Locations 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 links New and Edit location field descriptions on page 20 Deleting a location 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. On the Locations tab, in the Locations section, select one or more locations that you want to delete. 3. Click Delete. 4. In the Delete confirmation dialog box, click Yes. The system does not delete the applications that are running on the platform and moves the platform to Unknown location Platform mapping. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 19

20 Predeployment tasks New and Edit location field descriptions Required Location Information Name Name Avaya Sold-To # Address City State/Province/Region Zip/Postal Code Country Description The location name. The customer contact number. Administrators use the field to check entitlements. The address where the host is located. The city where the host is located. The state, province, or region where the host is located. The zip code of the host location. The country where the host is located. Optional Location Information Name Default Gateway DNS Search List DNS Server 1 DNS Server 2 NetMask NTP Server Button Save Edit Delete Cancel Description The IP address of the virtual machine gateway. For example, The search list of domain names. The DNS IP address of the primary virtual machine. For example, The DNS IP address of the secondary virtual machine. For example, The subnetwork mask of the virtual machine. The IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). Description Saves the location information and returns to the Locations section. Updates the location information and returns to the Locations section. Deletes the location information, and moves the host to the Unknown location section. Cancels the add or edit operations, and returns to the Locations section. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 20

21 Managing the host Managing the host Adding an Appliance Virtualization Platform or ESXi host About this task Use the procedure to add an Appliance Virtualization Platform or ESXi host. You can associate an ESXi host with an existing location. If you are adding a standalone ESXi host to System Manager Solution Deployment Manager or to the Solution Deployment Manager client, add the standalone ESXi host using its FQDN only. Solution Deployment Manager only supports the Avaya Aura Appliance Virtualization Platform and VMware ESXi hosts. If you try to add a host other than the Appliance Virtualization Platform and VMware ESXi hosts, the system displays the following error message: Retrieving host certificate info is failed: Unable to communicate with host. Connection timed out: connect. Solution Deployment Manager only supports host management of VMware-based hosts and Avaya Appliance Virtualization Platform (AVP). Before you begin Add a location. 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. Click Application Management. 3. In Application Management Tree, select a location. 4. On the Platforms tab, in the Platforms for Selected Location <location name> section, click Add. 5. In the New Platform section, provide the following: a. Platform name, Platform FQDN or IP address, user name, and password. For Appliance Virtualization Platform and VMware ESXi deployment, you can also provide the root user name. b. In Platform Type, select AVP/ESXi. c. If you are connected through the services port, set the Platform IP address of Appliance Virtualization Platform to Click Save. 7. On the Certificate dialog box, click Accept Certificate. The system generates the certificate and adds the Appliance Virtualization Platform host. For the ESXi host, you can only accept the certificate. If the certificate is invalid, Solution August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 21

22 Predeployment tasks Deployment Manager displays the error. To generate certificate, see VMware documentation. In the Application Management Tree section, the system displays the new host in the specified location. The system also discovers applications. 8. To view the discovered application details, such as name and version, establish trust between the application and System Manager using the following: a. On the Applications tab, in the Applications for Selected Location <location name> section, select the required application. b. Click More Actions > Re-establish connection. For more information, see Re-establishing trust for Solution Deployment Manager elements. c. Click More Actions > Refresh App. Important: When you change the IP address or FQDN of the Appliance Virtualization Platform host from the local inventory, you require AVP Utilities. To get the AVP Utilities application name during the IP address or FQDN change, refresh AVP Utilities to ensure that AVP Utilities is available. 9. On the Platforms tab, select the required platform and click Refresh. Next steps After adding a new host under Application Management Tree, the Refresh Platform operation might fail to add the virtual machine entry under Manage Element > Inventory. This is due to the absence of Application Name and Application Version for the virtual machines discovered as part of the host addition. After adding the host, do the following: 1. Under Application Management Tree, establish trust for all the virtual machines that are deployed on the host. 2. Ensure that the system populates the Application Name and Application Version for each virtual machine. Appliance Virtualization Platform license From Appliance Virtualization Platform Release 7.1.2, you must install an applicable Appliance Virtualization Platform host license file on an associated Avaya WebLM server and configure Appliance Virtualization Platform to obtain its license from the WebLM server. WebLM Server can be either embedded System Manager WebLM Server or standalone WebLM Server. Appliance Virtualization Platform licenses are according to the supported server types. The following table describes the applicable Appliance Virtualization Platform license type according to the supported server types. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 22

23 Managing the host Server type Avaya S8300E Common Server Release 2 HP ProLiant DL360p G8 Dell PowerEdge R620 Common Server Release 3 Dell PowerEdge R630 HP ProLiant DL360 G9 Common Server Release 3 Dell PowerEdge R630 HP ProLiant DL360 G9 Appliance Virtualization Platform license feature keyword VALUE_AVP_1CPU_EMBD_SRV R VALUE_AVP_1CPU_CMN_SR VR VALUE_AVP_2CPU_CMN_SR VR VALUE_AVP_XL_SRVR Appliance Virtualization Platform license feature display name Maximum AVP single CPU Embedded Servers Maximum AVP single CPU Common Servers Maximum AVP dual CPU Common Servers Maximum AVP XL Server To configure the Appliance Virtualization Platform license file: 1. Obtain the applicable license file from the Avaya PLDS website. 2. Install the license file on the System Manager WebLM Server or Standalone WebLM Server. Note: The Appliance Virtualization Platform license file can contain multiple Appliance Virtualization Platform licenses that is for four different server types. One Appliance Virtualization Platform license file contains all the necessary licenses for the complete solution. 3. Configure the applicable WebLM IP Address/FQDN field for each Appliance Virtualization Platform host by using either System Manager Solution Deployment Manager, Solution Deployment Manager Client, or Appliance Virtualization Platform host command line interface. You can view the license status of the Appliance Virtualization Platform host on the Platforms tab of the System Manager Solution Deployment Manager or Solution Deployment Manager Client interfaces. The Appliance Virtualization Platform license statuses on the Platforms tab are: Normal: If the Appliance Virtualization Platform host has acquired a license, the License Status column displays Normal. Error: If the Appliance Virtualization Platform host has not acquired a license. In this case, the Appliance Virtualization Platform enters the License Error mode and starts a 30-day grace period. The License Status column displays Error - Grace period expires: <DD/MM/YY> <HH:MM>. Restricted: If the 30-day grace period of the Appliance Virtualization Platform license expires, Appliance Virtualization Platform enters the License Restricted mode and restricts the administrative actions on the host and associated virtual machines. The License Status August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 23

24 Predeployment tasks column displays Restricted. After you install a valid Appliance Virtualization Platform license on the configured WebLM Server, the system restores the full administrative functionality. Note: Restricted administrative actions for: - AVP Host: AVP Update/Upgrade Management, Change Password, Host Shutdown, and AVP Cert. Management. - Application: New, Delete, Start, Stop, and Update. Appliance Virtualization Platform licensing alarms If the Appliance Virtualization Platform license enters either License Error Mode or License Restricted Mode, the system generates a corresponding Appliance Virtualization Platform licensing alarm. You must configure the Appliance Virtualization Platform alarming. For information about how to configure the Appliance Virtualization Platform alarming feature, see Administering Avaya Aura AVP Utilities. Configuring WebLM Server for an Appliance Virtualization Platform host using Solution Deployment Manager Before you begin 1. Add an Appliance Virtualization Platform host. For information about adding a host, see Administering Avaya Aura System Manager. 2. Obtain the license file from the Avaya PLDS website. 3. Install the license file on the System Manager WebLM Server or Standalone WebLM Server. 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. In Application Management Tree, select a location. 3. On the Platforms tab, in the Platforms for Selected Location <location name> section: a. Select the Appliance Virtualization Platform host. b. Click More Actions > WebLM Configuration. The system displays the WebLM Configuration dialog box. 4. In WebLM IP Address/FQDN, type the IP address or FQDN of WebLM Server. For WebLM configuration, if you select: Only one host then WebLM IP Address/FQDN displays the existing WebLM Server IP Address. Multiple hosts then WebLM IP Address/FQDN will be blank to assign the same WebLM Server IP Address for all the selected Appliance Virtualization Platform hosts. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 24

25 Managing the host 5. In Port Number, type the port number of WebLM Server. Embedded System Manager WebLM Server supports both 443 and ports. 6. Click Submit. The system displays the status in the Current Action column. The system takes approximately 9 minutes to acquire the Appliance Virtualization Platform host license file from the configured WebLM Server. On the Platforms tab, click Refresh. When the Appliance Virtualization Platform host acquires the license, on the Platforms tab, the License Status column displays Normal. WebLM Configuration field descriptions Name WebLM IP Address/FQDN Description The IP Address or FQDN of WebLM Server. Port Number The port number of WebLM Server. The default port is Button Submit Cancel Description Saves the WebLM Server configuration. Closes the WebLM Configuration dialog box. Viewing the Appliance Virtualization Platform host license status using Solution Deployment Manager 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. In Application Management Tree, select a location. 3. On the Platforms tab, in the Platforms for Selected Location <location name> section, view the Appliance Virtualization Platform host license status in the License Status column. Shutting down the Appliance Virtualization Platform host About this task You can perform the shutdown operation on one Appliance Virtualization Platform host at a time. You cannot schedule the operation. 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. In Application Management Tree, select a location. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 25

26 Predeployment tasks 3. On the Platforms tab, in the Platforms for Selected Location <location name> area, select an Appliance Virtualization Platform host. 4. Click More Actions > Lifecycle Action > Host Shutdown. The Appliance Virtualization Platform host and virtual machines shut down. Restarting Appliance Virtualization Platform or an ESXi host About this task The restart operation fails, if you restart the host on which System Manager itself is running. If you want to restart the host, you can do this either through vsphere Client or through the Solution Deployment Manager client. 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. In Application Management Tree, select a location. 3. On the Platforms tab, in the Platforms for Selected Location <location name> area, select a platform. 4. Click More Actions > Lifecycle Action > Host Restart. 5. On the confirmation dialog box, click Yes. The system restarts the host and virtual machines running on the host. Removing an Appliance Virtualization Platform or ESXi host 1. On the System Manager web console, click Services > Solution Deployment Manager > Application Management. 2. On the Platforms tab, in the Platforms for Selected Location <location name> section, select one or more platforms that you want to delete. 3. Click Remove. 4. On the Delete page, click Yes. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 26

27 Managing the host Add and Edit platform field descriptions Name Location Platform Name Platform FQDN or IP User Name Password Button Save Description The location where the platform is available. The field is read only. The platform name of OS, Appliance Virtualization Platform or ESXi. The IP address or FQDN of OS, Appliance Virtualization Platform or ESXi. The user name to log in to OS, Appliance Virtualization Platform or ESXi. Note: For Appliance Virtualization Platform, provide the admin credentials that you configured while generating the Kickstart file. The password to log in to OS, Appliance Virtualization Platform or ESXi. Description Saves the host information and returns to the Platforms for Selected Location <location name> section. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 27

28 Chapter 5: Deploying Communication Manager on the Avaya-provided server Deployment checklist Use the following checklist to deploy the Communication Manager Release 8.0 application by using Solution Deployment Manager. # Action Link/Notes 1 Download the following software from the Avaya Support website at support.avaya.com: OVA files for AVP Utilities and Communication Manager The Communication Manager patch file The Solution Deployment Manager client, if System Manager Solution Deployment Manager is not available. 2 Upload the software that is required for deployment on the computer on which the Solution Deployment Manager client is installed. For example, OVA file, firmware, software patches, service packs, and images. 3 For Avaya Aura Virtualized Appliance deployments, install the supported server. Appliance Virtualization Platform is preinstalled on the server. 4 Keep a copy of the license files for the Avaya Aura products so you can replicate with the new Host ID after the OVA file installation. Ensure that the license file copies are accessible Table continues August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 28

29 Deploying the Communication Manager OVA file by using Solution Deployment Manager # Action Link/Notes 5 Ensure that the following information is handy: FQDN/IP address, netmask, and gateway Out of Band Management configuration details. 6 Install the Avaya_SDMClient_win64_ _6.exe file. - If System Manager Solution Deployment Manager is not available, install the Solution Deployment Manager client. 7 Add a location. Adding a location on page 18 8 Add the Appliance Virtualization Platform host. 9 Deploy AVP Utilities OVA, and select the appropriate footprint size and the service mode. 10 Deploy the Communication Manager OVA file and provide the network parameters and configuration parameters. 11 Install the latest Communication Manager patch file. 12 To activate the serviceability agent registration, reset the AVP Utilities application. 13 Verify the deployment of the Communication Manager application. Adding an Appliance Virtualization Platform or ESXi host on page 21 While deploying OVA, provide the IP address of the application that you want to deploy. Deploying the Communication Manager OVA file by using Solution Deployment Manager on page 29 Applying the Communication Manager patch using SMI on page Deploying the Communication Manager OVA file by using Solution Deployment Manager About this task Use this procedure to deploy Communication Manager by using Solution Deployment Manager. Before you begin If System Manager Solution Deployment Manager is not available, install the Solution Deployment Manager client. Add a location. Add the Appliance Virtualization Platform host. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 29

30 Deploying Communication Manager on the Avaya-provided server Deploy AVP Utilities. 1. To access Solution Deployment Manager, do one of the following: On the System Manager web console, click Services > Solution Deployment Manager. On the desktop, click the Solution Deployment Manager icon ( ). 2. In Application Management Tree, select a platform. 3. On the Applications tab, in the Applications for Selected Location <location name> section, click New. The system displays the Applications Deployment section. 4. In the Select Location and Platform section, do the following: a. In Select Location, select a location. b. In Select Platform, select a platform. The system displays the host name in the Platform FQDN field. 5. In Data Store, select a data store, if not displayed upon host selection. The page displays the capacity details. 6. Click Next. 7. To get the OVA file, select the OVA tab, and click one of the following: URL, in OVA File, type the absolute path to the application OVA file, and click Submit. S/W Library, in File Name, select the application OVA file. Browse, select the required application OVA file from a location on the computer, and click Submit File. If the OVA file does not contain a valid Avaya certificate, then the system does not parse the OVA and displays the message: Invalid file content. Avaya Certificate not found or invalid. 8. In Flexi Footprint, select the footprint size that the application supports. 9. (Optional) To install the patch file, click Service or Feature Pack, and enter the appropriate parameters. URL, and provide the absolute path to the latest service or feature pack. S/W Library, and select the latest service or feature pack. Browse, and select the latest service or feature pack. You can install the patch file now or after completing the Communication Manager OVA deployment. 10. Click Next. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 30

31 Application Deployment field descriptions In Configuration Parameters and Network Parameters sections, the system displays the fields that are specific to the application that you deploy. 11. In the Network Parameters section, ensure that page displays the following preconfigured fields when Out of Band Management is enabled: Public Out of Band Management 12. For Duplex configuration, in the Network Parameters section, select the port group from Duplication Link. If you want to create new port group, perform the following: a. Select the Create Port Group check box. b. In the Duplication Link field, select the VMNIC on which you want to create the new port group. Once the deployment is complete, the system will display the port group created and assigned to Network Adapter2. The Port group name is in the format: vmname_duplication Link. 13. In the Configuration Parameters section, complete the fields. For more information, see Application Deployment field descriptions. For each application that you deploy, fill the appropriate fields. 14. Click Deploy. 15. Click Accept the license terms. In the Platforms for Selected Location <location name> section, the system displays the deployment status in the Current Action Status column. The system displays the virtual machine on the Applications for Selected Location <location name> page. 16. To view details, click the Status Details link. Application Deployment field descriptions Select Location and Platform Name Select Location Select Platform Platform FQDN Description The location name. The platform name that you must select. The platform FQDN. Table continues August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 31

32 Deploying Communication Manager on the Avaya-provided server Name Data Store Description The data store for the application. The page populates the capacity details in the Capacity Details section. Capacity Details The system displays the CPU and memory details of the Appliance Virtualization Platform or ESXi 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 Name Full Capacity Free Capacity Reserved Capacity Status Description The name The maximum capacity The available capacity The reserved capacity The configuration status Provide admin and root Credentials The system displays the Provide admin and root Credentials section for OS. Name Platform IP Platform FQDN Admin User of OS Admin Password of OS Root User of OS Description The platform IP. The platform FQDN The admin user name of OS. The admin password of OS. The root user of OS. OVA/ISO Details Name Application Name ME Deployment Enable enhanced security URL Browse Description The name of the application. The option to perform the Midsize Enterprise deployment. The option is available only while deploying Communication Manager simplex OVA. The option to enable JITC mode deployment. The option to specify the URL or absolute path from where you can get the OVA or ISO file. The option to specify the location from where you can get the OVA or ISO file. Table continues August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 32

33 Application Deployment field descriptions Name Select OVA Submit File OVA from software library Select Software Library Flexi Footprint Description The URL or absolute path to the OVA or ISO file of the application that you must provide. For example, C:\Program Files\SDM \<Application OVA_8.0.ova> The field is available only when you click Browse. Note: System Manager validates any file that you upload during deployment, and accepts only the OVA or ISO file type. System Manager filters uploaded files based on file extension and mime types or bytes in the file. When you select OVA from software library, you can select the OVA or ISO file of the application that you want to deploy. The field is available only when you click Browse. Selects the OVA or ISO file of the application that you want to deploy. The option to specify the software library where the OVA or ISO file is saved. The default path provided during the installation of the Solution Deployment Manager client. The default path is C:\Program Files \Avaya\SDMClient\Default_Artifacts. The field is available only when you click OVA from software library The footprint size supported for the selected application. Important: Communication Manager Configuration Parameters Ensure that the required memory is available for the footprint sizes that you selected. The upgrade operation might fail due to insufficient memory. Name CM IPv4 Address CM IPv4 Netmask CM IPv4 Gateway CM IPv6 Address CM IPv6 Network Prefix CM IPv6 Gateway Description The IPv4 address of the Communication Manager virtual machine. The IPv4 network mask of the Communication Manager virtual machine. The IPv4 default gateway of the Communication Manager virtual machine. The IPv6 address of the Communication Manager virtual machine. The field is optional. The IPv6 network prefix of the Communication Manager virtual machine. The field is optional. The IPv6 gateway of the Communication Manager virtual machine. The field is optional. Table continues August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 33

34 Deploying Communication Manager on the Avaya-provided server Name Out of Band Management IPv4 Address Out of Band Management IPv4 Netmask Out of Band Management IPv6 Address Out of Band Management IPv6 Network Prefix CM Hostname NTP Server(s) DNS Server(s) Search Domain List WebLM Server IPv4 Address EASG User Access CM Privileged Administrator User Login CM Privileged Administrator User Password Confirm Password Description The IPv4 address of the Communication Manager virtual machine for out of band management. The field is optional network interface to isolate management traffic on a separate interface from the inband signaling network. The IPv4 subnetwork mask of the Communication Manager virtual machine for out of band management. The IPv6 address of the Communication Manager virtual machine for out of band management. The field is optional network interface to isolate management traffic on a separate interface from the inband signaling network. The IPv4 subnetwork mask of the Communication Manager virtual machine for out of band management. The hostname of the Communication Manager virtual machine. The IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). You can type up to three NTP servers. The DNS IP address of the Communication Manager virtual machine. The search list of domain names. For example, mydomain.com. Separate the search list names with commas (,). The IPv4 address of WebLM. The field is mandatory. Enables or disables Avaya Logins for Avaya Services to perform the required maintenance tasks. The options are: 1: To enable EASG. 2: To disable EASG. Avaya recommends to enable EASG. You can also enable EASG after deploying or upgrading the application by using the command: EASGManage --enableeasg. The login name for the privileged administrator. You can change the value at any point of time. The field is mandatory. The password for the privileged administrator. You can change the value at any point of time. The field is mandatory. The password required to be confirmed. The field is mandatory. August 2018 Deploying Avaya Aura Communication Manager in Virtual Appliance 34