Deploying standalone Avaya WebLM on Cloud Services

Transcription

1 Deploying standalone Avaya WebLM on Cloud Services Release Issue 1 December 2017

2 Contents Chapter 1: Introduction... 4 Purpose... 4 Prerequisites... 4 Chapter 2: Avaya Aura on Amazon Web Services overview... 5 Topology... 6 Networking considerations for connecting Avaya applications... 7 Connection types... 8 Chapter 3: Planning and configuration... 9 Planning checklist... 9 Configuration tools and utilities... 9 Release details of the Avaya WebLM AWS OVA Supported footprints for WebLM on AWS Downloading software from PLDS System capacities for Avaya WebLM Supported browsers for Amazon Web Console Signing in to the Amazon Web Services Management console Creating a key pair Chapter 4: Converting WebLM OVA to AMI Checklist for converting standalone Avaya WebLM OVA to an Amazon Machine Image Creating a bucket for uploading the OVAs for AMI conversion Uploading Avaya WebLM OVA Creating a Linux Amazon EC2 virtual server instance Creating a user access key Obtaining the virtual server instance user ID Importing the OVA for AMI conversion Chapter 5: Deploying the standalone Avaya WebLM AMI Deploying standalone Avaya WebLM AMI Installing a WebLM patch, feature pack, or service pack Amazon Web Services instance management Starting an AWS instance Stopping an AWS instance Rebooting an AWS instance Chapter 6: Configuring the Avaya WebLM instance Configuring the Avaya WebLM instance Dual data center configuration Chapter 7: Post-installation Verification Logging on to the WebLM web console Rehosting license files Verifying the WebLM software version December 2017 Deploying standalone Avaya WebLM on Cloud Services 2

3 Contents Enhanced Access Security Gateway (EASG) overview Managing EASG from CLI Viewing the EASG certificate information EASG site certificate Chapter 8: Maintenance Changing the IP, FQDN, DNS, Gateway, or Netmask addresses Configuring multiple DNS IP addresses Configuring the time zone Configuring the NTP server Resetting the WebLM password through CLI Performing WebLM backup Performing WebLM restore WebLM CLI operations Chapter 9: Resources Documentation Finding documents on the Avaya Support website Amazon Web Services documentation Training Viewing Avaya Mentor videos Support Using the Avaya InSite Knowledge Base Appendix A: Configuring PuTTY Converting the *.pem file to the *.ppk format Configuring PuTTY for an SSH session Signing in to the Amazon EC2 virtual server instance Glossary December 2017 Deploying standalone Avaya WebLM on Cloud Services 3

4 Chapter 1: Introduction Purpose This document describes the procedures: To convert the standalone Avaya WebLM OVA to Amazon Machine Image (AMI). To deploy the standalone Avaya WebLM AMI by using the Amazon Web Services Management console. This document is intended for people who install and configure standalone Avaya WebLM AMI at a customer site. Prerequisites Before deploying Avaya WebLM, ensure that you have the following knowledge, skills and tools. Knowledge Amazon Web Services setup Linux Operating System Standalone Avaya WebLM Skills To administer the AWS Management console and Avaya Aura applications. Tools For information about tools and utilities, see Configuration tools and utilities. December 2017 Deploying standalone Avaya WebLM on Cloud Services 4

5 Chapter 2: Avaya Aura on Amazon Web Services overview Amazon Web Services (AWS) is a cloud services platform that enables enterprises to securely run applications on the virtual cloud. The key components of AWS are Amazon Elastic Compute Cloud (EC2) and Amazon Simple Storage Service (S3). Supporting the Avaya applications on the AWS Infrastructure as a service (IaaS) platform provides the following benefits: Minimizes the capital expenditure (CAPEX) on infrastructure. The customers can move from CAPEX to operational expense (OPEX). Reduces the maintenance cost of running the data centers. Provides a common platform for deploying the applications. Provides a flexible environment to accommodate the changing business requirements of customers. You can deploy the following Avaya Aura applications on Amazon Web Services: Avaya Aura System Manager Avaya Aura Session Manager Avaya Aura Communication Manager Avaya Aura Utility Services Avaya WebLM Presence Services using Avaya Breeze Avaya Session Border Controller for Enterprise Avaya Aura Device Services Avaya Aura Application Enablement Services (Software only) Avaya Aura Media Server (Software only) Avaya Diagnostic Server (Software only) The supported Avaya Aura AWS applications can also be deployed on-premises. December 2017 Deploying standalone Avaya WebLM on Cloud Services 5

6 Avaya Aura on Amazon Web Services overview You can connect the following applications to the Avaya Aura AWS instances from the customer premises: Avaya Aura Conferencing Release 8.0 and later Avaya Aura Messaging Release 6.3 and later G430 Branch Gateway, G450 Branch Gateway, and G650 Media Gateway Topology The following diagram depicts the architecture of the Avaya applications on the Amazon Web Services platform. This diagram is an example setup of possible configuration offered by Avaya. The setup must follow the AWS deployment guidelines, but does not need to include all the applications. December 2017 Deploying standalone Avaya WebLM on Cloud Services 6

7 Topology Figure 1: Avaya Aura applications on Amazon Web Services Networking considerations for connecting Avaya applications When you deploy an Avaya application at main location or at a branch location on AWS, ensure that you follow the networking requirements, such as, the WAN network topology, bandwidth and latency of the Avaya applications. You must adhere to the Avaya network recommendations and AWS networking rules. December 2017 Deploying standalone Avaya WebLM on Cloud Services 7

8 Avaya Aura on Amazon Web Services overview AWS has some limitations for establishing public internet VPNs and direct connections into AWS. For more information about Amazon VPC Limits, see the AWS documentation at docs.aws.amazon.com/amazonvpc/latest/userguide/vpc_appendix_limits.html. Important: Avaya recommends the use of direct connection in combination of a private WAN connection with Service Level Agreement (SLA) measures to ensure that the network quality is appropriate for signaling and voice traffic. Avaya is not responsible for network connections between AWS and customer premises. Connection types You can connect applications in a hybrid network on the Virtual Private Cloud (VPC) in the following ways: Connection type VPN connection Direct connection Resource For information about VPN connections, see AmazonVPC/latest/UserGuide/vpn-connections.html. For information about AWS direct connections, see directconnect/. December 2017 Deploying standalone Avaya WebLM on Cloud Services 8

9 Chapter 3: Planning and configuration Planning checklist Ensure that you complete the following before deploying the standalone Avaya WebLM on Amazon Web Services Management console: No. Task Link/Notes 1. Download the required software. Configuration tools and utilities on page 9 2. Purchase the required licenses. Register for PLDS and perform the following Obtain the license file. Activate license entitlements in PLDS. 3. Log on to the Amazon Web Services Management console. Downloading software from PLDS on page 10 Go to the Avaya Product Licensing and Delivery System at Signing in to the Amazon Web Services Management console on page Create a key pair. Creating a key pair on page 12 Configuration tools and utilities Avaya WebLM OVA A browser for accessing the Amazon Web Services Management Console. A browser for accessing the Avaya WebLM web interface An SFTP client for Windows, for example WinSCP An SSH client, for example, PuTTY and PuTTYgen December 2017 Deploying standalone Avaya WebLM on Cloud Services 9

10 Planning and configuration Release details of the Avaya WebLM AWS OVA You can download the following OVAs from the Avaya PLDS website at Product name Avaya WebLM Release: 7.1 Release version and Service pack Service pack: AWS OVA Profile 1 and Profile 2: WebLM aws-17.ova Supported footprints for WebLM on AWS Product name Footprint AWS instance type AWS vcpu AWS RAM (GB) HDD (GB) WebLM Profile 1 t2.medium WebLM Profile 2 t2.medium NICs 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 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. December 2017 Deploying standalone Avaya WebLM on Cloud Services 10

11 System capacities for Avaya WebLM 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. System capacities for Avaya WebLM For information about the system capacities, such as, number of users, gateways, and endpoints, see the product specific documentation on the Avaya Support website at Supported browsers for Amazon Web Console For information about supported browser list and version, see faqs/#browser_support on the AWS website. Signing in to the Amazon Web Services Management console Before you begin Ensure that you have an AWS account. December 2017 Deploying standalone Avaya WebLM on Cloud Services 11

12 Planning and configuration 1. In your web browser, type the URL 2. Click Sign In to the Console. The system displays the Amazon Web Service page and auto-populates the Account field. 3. In the User Name field, type the user name or registered ID. 4. In the Password field, type the password. 5. Click Sign In. The system displays the AWS Management Console page. Creating a key pair About this task A key pair is a set of public and private keys. The public key is used to encrypt data, such as the login password. The private key is used to decrypt the encrypted data. You provide this key pair when you create a CloudFormation stack, and use it for SSH access to the Amazon Machine Instances. 1. Sign in to the Amazon Web Services Management console. 2. In the left navigation pane, go to NETWORK & SECURITY, and click Key Pairs. 3. Click Create Key Pair. 4. In the Create Key Pair dialog box, in the Key pair name field, type a name for the key pair. 5. Click Create. The system generates a *.pem file and prompts you to save the file on your computer. You can also view the created key pair name in the Key pair name column. 6. Save the *.pem file. Important: When you create a key pair, save it. If you lose the key, you cannot retrieve it and you will not be able to access the instance. December 2017 Deploying standalone Avaya WebLM on Cloud Services 12

13 Chapter 4: Converting WebLM OVA to AMI Checklist for converting standalone Avaya WebLM OVA to an Amazon Machine Image No. Task Link/Notes 1. Create a bucket for uploading the OVA. Creating a bucket for uploading the OVAs for AMI conversion on page Upload the Avaya WebLM OVA. Upload the standalone Avaya WebLM OVA. 3. Create an Amazon EC2 virtual server instance. Creating a Linux Amazon EC2 virtual server instance on page Create an access key. Creating a user access key on page Obtain the virtual server instance user id. 6. Import the OVA for AMI conversion. Obtaining the virtual server instance user ID on page 16 Importing the OVA for AMI conversion on page 17 Creating a bucket for uploading the OVAs for AMI conversion 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Storage, and click S3. The system displays the S3 Management Console page. 3. Click Create bucket. The system displays the Create bucket dialog box. 4. In Bucket name, type a unique bucket name. Only use lowercase letters for the name. 5. In the Region field, click a region for your bucket. December 2017 Deploying standalone Avaya WebLM on Cloud Services 13

14 Converting WebLM OVA to AMI For more information about creating a bucket and selecting a region, see Amazon S3 Documentation. 6. Click Create. Uploading Avaya WebLM OVA Before you begin Create a bucket, see Creating a bucket for uploading the OVAs for AMI conversion on page Sign in to the Amazon Web Services Management console. 2. Go to Services > Storage, and click S3. The system displays the S3 Management Console page. 3. From the All Buckets section, select a bucket. 4. Click Upload. The system displays the Upload - Select Files and Folders dialog box. 5. Click Add Files. 6. On the Choose File to Upload dialog box, select the Avaya WebLM OVA file from your local system, and click Open. 7. Click Start Upload. Creating a Linux Amazon EC2 virtual server instance 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. Click Launch Instance. 4. On the Choose an Amazon Machine Image (AMI) page, search for a Linux AMI, and click Select. You must select an image that includes the AWS command line tools. 5. On the Choose an Instance Type page, select an instance type, and click Next: Configure Instance Details. December 2017 Deploying standalone Avaya WebLM on Cloud Services 14

15 Creating a Linux Amazon EC2 virtual server instance 6. On the Configure Instance Details page, do the following: a. In the Network field, click a VPC network. b. In the Network interfaces section, assign an IP address. 7. Click Next: Add Storage. 8. On the Add Storage page, leave the default settings, and click Next: Add Tags. 9. On the Add Tags page, add a tag, and click Next: Configure Security Group. 10. On the Configure Security Group page, create a new security group or select an existing security group, and click Review and Launch. 11. On the Review Instance Launch page, review the details of each configuration, and then click Launch. 12. On the Select an existing key pair or create a new key pair dialog box, select one of the following options: Choose an existing key pair: If you select this option, perform the following: a. From the Select a key pair drop-down list, select a key pair. b. Select the I acknowledge that I have access to the selected private key file (<example.pem>), and that without this file, I won't be able to log into my instance check box. Create a new key pair: If you select this option, perform the following: a. In the Key pair name field, type a name for the private key file. The extension of the private key file is.pem. b. Click Download Key Pair. c. Save the file in a secure and accessible location. Note: You will not be able to download the file again. Proceed without a key pair: If you select this option, select the I acknowledge that I will not be able to connect to this instance unless I already know the password built into this AMI check box. 13. Click Launch Instances. The system creates the virtual server instance. 14. Click Launch Status, and click View instance. Next steps When the system creates an instance, the Status Checks column displays the message: 2/2 checks passed. Import the OVA for AMI conversion. December 2017 Deploying standalone Avaya WebLM on Cloud Services 15

16 Converting WebLM OVA to AMI Creating a user access key 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Security, Identity & Compliance, and click IAM. The system displays the Welcome to Identity and Access Management page. 3. In the left navigation pane, click Users. 4. Click on a user name. 5. On the Summary page, click the Security Credentials tab. 6. In the Access Keys section, click Create Access Key. The system displays the message: Your access key has been created successfully. Important: When you create a security access key, you must save it. If you lose the security access key, you cannot retrieve it. Obtaining the virtual server instance user ID 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. In the left navigation pane, click Instances. 4. Select a server instance, and click Connect. 5. On the Connect To your Instance page, view the user ID. Example: ssh -i "example.pem" ec2-user@<ip address> The user name is ec2-user. Use this user ID to connect to the Linux server. December 2017 Deploying standalone Avaya WebLM on Cloud Services 16

17 Importing the OVA for AMI conversion Importing the OVA for AMI conversion Before you begin Create an access key. For more information, see Creating an access key. Obtain the user id. For more information, see Obtaining the virtual server instance user id. Converting the *.pem file to the *.ppk format and configure PuTTY for establishing an SSH connection. For more information, see Configuring PuTTY. 1. Open an SSH session. 2. In Host Name (or IP address), type the IP Address of the virtual server instance, and click Open. 3. Log in to the Linux server, and run the command: aws. 4. To configure the AWS details, run the command: aws configure, and do the following: a. In AWS Access Key ID, type the AWS access key ID. b. In AWS Secret Access Key, type the AWS secret access key ID. c. In Default region name, type the region name. For example: us-west-2. d. In Default output format, type text or json. 5. To check whether the EC2 instance is ready to use, run the command: aws s3 ls. The system displays the S3 bucket that you created. 6. To view the content of the S3 bucket, run the command: aws s3 ls s3:// <nameofbucket>. 7. To allow importing files into the EC2 instance, create a vmimport role, and associate the following trust policies: AmazonEC2FullAccess IAMFullAccess AmazonS3FullAccess AWSConfigRole AWSOpsWorksInstanceRegistration a. Create a file role-policy.json with the following content and run the command: aws iam create-role --role-name vmimport --assume-role-policydocument file://role-policy.json. For example: { "Version":" ", "Statement":[ December 2017 Deploying standalone Avaya WebLM on Cloud Services 17

18 Converting WebLM OVA to AMI { "Effect":"Allow", "Action":[ "s3:listbucket", "s3:getbucketlocation" ], "Resource":[ "arn:aws:s3:::<your_bucket_name>" ] }, { "Effect":"Allow", "Action":[ "s3:getobject" ], "Resource":[ "arn:aws:s3:::<your_bucket_name>/*" ] }, { "Effect":"Allow", "Action":[ "ec2:modifysnapshotattribute", "ec2:copysnapshot", "ec2:registerimage", "ec2:describe*" ], "Resource":"*" } ] } b. Create a file called trust-policy.json with the following content and run the command: aws iam create-role --role-name vmimport --assume-rolepolicy-document file://trust-policy.json. For example: { "Version":" ", "Statement":[ { "Sid":"", "Effect":"Allow", "Principal":{ "Service":"vmie.amazonaws.com" }, "Action":"sts:AssumeRole", "Condition":{ "StringEquals":{ "sts:externalid":"vmimport" } } } ] } 8. To import the ova for conversion, run the command: aws ec2 import-image --cliinput-json "{ \"Description\": \"<Server OVA>\", \"DiskContainers \": [ { \"Description\": \"<text description of task>\", \"UserBucket\": { \"S3Bucket\": \"<your_bucket_name>\", \"S3Key\" : \"<server.ova>\" } } ]}" The system displays the Status and the ImportTaskId parameters. 9. To check the status of the import image, run the command: aws ec2 describeimport-image-tasks --cli-input-json "{ \"ImportTaskIds\": [\"<Your_ImportTaskId>\"], \"NextToken\": \"abc\", \"MaxResults\": 10 } " The output format varies depending on the selection of the text or JSON format on the aws CLI configuration. For more details, see AWS Import your VM as an image on the AWS website at docs.aws.amazon.com/vm-import/latest/userguide/import-vm-image.html. December 2017 Deploying standalone Avaya WebLM on Cloud Services 18

19 Importing the OVA for AMI conversion 10. Sign in to the Amazon Web Services Management console. 11. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 12. In the left navigation pane, click IMAGES > AMIs. You can search the converted AMI with ImageId. The system displays the newly converted AMI ImageId in the AMI ID column. You can give an appropriate name for the AMI ImageId. December 2017 Deploying standalone Avaya WebLM on Cloud Services 19

20 Chapter 5: Deploying the standalone Avaya WebLM AMI Deploying standalone Avaya WebLM AMI Before you begin Convert the Avaya WebLM AWS OVA to AMI. See Checklist for converting OVA to an Amazon Machine Image. 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. In the left navigation pane, click IMAGES > AMIs. The system displays the list of AMIs. 4. Select the Avaya WebLM AMI, and click Launch. 5. On the Choose an Instance Type page, select an instance type, and click Next: Configure Instance Details. You must select the correct instance type for deploying the AMI. If you select an incorrect instance type, usability of the system might be impacted. For information about the instance type, see Supported footprints for the Avaya WebLM on AWS. 6. On the Configure Instance Details page, do the following: a. In the Network field, click a VPC network. b. In the Network interfaces section, assign an IP address. 7. Click Next: Add Storage. 8. On the Add Storage page, leave the default settings, and click Next: Add Tags. 9. On the Add Tags page, add a tag, and click Next: Configure Security Group. 10. On the Configure Security Group page, create a new security group or select an existing security group, and click Review and Launch. You must select the security group that has the required ports enabled. For information about ports, see port matrix on the Avaya Support website at December 2017 Deploying standalone Avaya WebLM on Cloud Services 20

21 Installing a WebLM patch, feature pack, or service pack 11. On the Select an existing key pair or create a new key pair dialog box, select one of the following options: Choose an existing key pair: If you select this option, perform the following: a. From the Select a key pair drop-down list, select a key pair. b. Select the I acknowledge that I have access to the selected private key file (<example.pem>), and that without this file, I won't be able to log into my instance check box. Create a new key pair: If you select this option, perform the following: a. In the Key pair name field, type a name for the private key file. The extension of the private key file is.pem. b. Click Download Key Pair. c. Save the file in a secure and accessible location. Note: You will not be able to download the file again. Proceed without a key pair: If you select this option, select the I acknowledge that I will not be able to connect to this instance unless I already know the password built into this AMI check box. 12. Click Launch Instances. The system creates the instance and displays it on the Instances page. When the system creates an instance, the Status Checks column displays the message: 2/2 checks passed. Installing a WebLM patch, feature pack, or service pack Before you begin Create backup of WebLM. Copy the patch file, feature pack file, or the service pack file to the WebLM virtual machine. Verify the installed WebLM version. 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Verify that the MD5 checksum of the patch that you install is MD5Sum - bf940aa02d1e641c2117cf173a8be1a1. 3. Type WebLMPatchdeploy <absolute path to the WebLM feature pack file>. December 2017 Deploying standalone Avaya WebLM on Cloud Services 21

22 Deploying the standalone Avaya WebLM AMI For example, WebLMPatchdeploy /home/avaya/veweblm_ _xxx.bin. The system installs the patch file. 4. To accept the license terms, read the End User License Agreement carefully, and type Y. The patch installation takes about minutes to complete. You can view to monitor the WebLM patch progress status from the /var/log/avaya/weblm_patch.log file. If the installation is successful, the system displays a warning message on the web console and on the command line interface to restart WebLM if kernel is updated. 5. After patch installation is successful, relogin to CLI to check if the updated kernel is running. 6. Restart the standalone WebLM. Next steps If the patch or service pack installation fails, perform a snapshot restore to go to the previous version of WebLM. Note: Modifying the network or management configuration is not recommended before the patch deployment. Amazon Web Services instance management Using EC2 Management Console, you can start, stop, reboot, and terminate an instance. Note: With the stop and start operations, the instance might move to a different host that might change the IP Address and MAC Address if not statically allocated. Rebooting the instance will not change the host, IP Address, and MAC Address in AWS. Starting an AWS instance 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. In the left navigation pane, click Instances. 4. Select one or more instance, click Actions > Instance State > Start. The system displays a message to start the instances. December 2017 Deploying standalone Avaya WebLM on Cloud Services 22

23 Amazon Web Services instance management 5. Click Yes, Start. When the system starts the instance, the Instance State column displays the state as running. Stopping an AWS instance 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. In the left navigation pane, click Instances. 4. Select one or more instance, click Actions > Instance State > Stop. The system displays a message to stop the instances. 5. Click Yes, Stop. When the system stops the instance, the Instance State column displays the state as stopped. Rebooting an AWS instance 1. Sign in to the Amazon Web Services Management console. 2. Go to Services > Compute, and click EC2. The system displays the EC2 Management Console page. 3. In the left navigation pane, click Instances. 4. Select one or more instance, click Actions > Instance State > Reboot. The system displays a message to reboot the instances. 5. Click Yes, Reboot. December 2017 Deploying standalone Avaya WebLM on Cloud Services 23

24 Chapter 6: Configuring the Avaya WebLM instance Configuring the Avaya WebLM instance About this task Use the following procedure for the WebLM first boot configuration. Before you begin Download and install the WebLM license file. 1. Log in to the WebLM command line interface as admin. For example: ssh Address> At your first login, the system prompts you to change your admin password. 2. To configure the WebLM network and other parameters, run the command: WebLMsetup. 3. Read the End User License Agreement (EULA). 4. To accept the EULA, in Do you accept the Avaya Software License Terms? (Y)es/(N)o, type Y. The system displays the message: Starting WebLM post-install first boot. 5. To specify configuration details, type y. 6. In IP Address, type the IP address of the WebLM instance. 7. In Gateway, type the gateway IP address of the WebLM instance. 8. In IP Address of DNS Server, type the domain name of the primary, secondary, and WebLM instances. Separate the IP addresses with commas (,). 9. In Short Hostname, type the host name of the WebLM instance. The value of the WebLM hostname is case-sensitive. The restriction applies only during the upgrade of WebLM. 10. In Domain Name, type the domain name of the WebLM instance. 11. (Optional) In Default Search List, type the search list of domain names. December 2017 Deploying standalone Avaya WebLM on Cloud Services 24

25 Configuring the Avaya WebLM instance 12. (Optional) In NTP Server IP or FQDN, type the IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). 13. In Time Zone Detail, select the timezone where the WebLM instance is located. The system displays a list of available continents and countries. 14. At the WebLM CLI USER prompt, perform the following: a. In WebLM command line user name, type the user name of the WebLM CLI user. Do not provide the common user names, such as, admin, csaadmin, postgres, root, bin, daemon, adm, sync, dbus, vcsa, ntp, saslauth, sshd, tcpdump, xfs, rpc, rpcuser, nfsnobody, craft, inads, init, rasaccess, sroot, postgres, smgr, and nortel. b. In WebLM command line user password, type the password for the WebLM CLI user. c. In Confirm Password, retype the password to confirm the WebLM CLI user authentication. 15. At the WebLM UI Password for User - admin prompt, perform the following: a. In WebLM UI admin user password, type the password for the WebLM UI user. b. In Confirm Password, retype the password to confirm the WebLM UI user authentication. 16. At the Enhanced Access Security Gateway (EASG) prompt, read the following messages, and type one of the following: Enable: (Recommended) By enabling Avaya Logins you are granting Avaya access to your system. This is necessary to maximize the performance and value of your Avaya support entitlements, allowing Avaya to resolve product issues in a timely manner. In addition to enabling the Avaya Logins, this product should be registered with Avaya and technically onboarded for remote connectivity and alarming. Please see the Avaya support site (support.avaya.com/registration) for additional information for registering products and establishing remote access and alarming. Disable: By disabling Avaya Logins you are preventing Avaya access to your system. This is not recommended, as it impacts Avaya s ability to provide support for the product. Unless the customer is well versed in managing the product themselves, Avaya Logins should not be disabled. a. 1: To enable EASG. Avaya recommends to enable EASG. December 2017 Deploying standalone Avaya WebLM on Cloud Services 25

26 Configuring the Avaya WebLM instance You can also enable EASG after deploying or upgrading the application by using the command: EASGManage --enableeasg. b. 2: To disable EASG. 17. To confirm the WebLM Configuration parameters, in Do you want to continue, type Y. The system starts the configuration of the network parameters. The deployment process takes about minutes to be completed. Do not reboot the system until the configuration is complete. Dual data center configuration For configuring the applications in a dual data center environment, the instances must be configured in the same network region in two zones on the same Virtual Private Cloud (VPC). December 2017 Deploying standalone Avaya WebLM on Cloud Services 26

27 Chapter 7: Post-installation Verification Logging on to the WebLM web console Before you begin Obtain a user account to log on to the WebLM web console. If you do not have a user account, go to the Avaya Support website at to create your account. About this task The WebLM web console is the main interface of Avaya WebLM. You must log on to WebLM web console to perform any task. The WebLM home page displays the navigation menu that provides access to shared services to perform various operations that WebLM supports. 1. On the web browser, type Qualified Domain Name>>:52233/ WebLM, the WebLM URL. 2. In the User Name field, type the user name. 3. In the Password field, type the password. 4. Click Log On. The system validates the user name and password with the WebLM user account. If the user name and password match, the system displays the WebLM home page with the WebLM <version_number>. If the user name and password does not match, WebLM displays an error message and prompts you to enter the user name and password again. Rehosting license files 1. On the WebLM console, click Server Properties. 2. On the Server Properties page, note the WebLM server host ID. 3. Go to the PLDS website regenerate the license file for your product using the same host ID. December 2017 Deploying standalone Avaya WebLM on Cloud Services 27

28 Post-installation Verification 4. Install the license file that you generated on the WebLM server. For more information on installing a license file, see Installing the license file in Administering Avaya WebLM. Verifying the WebLM software version About this task You must perform the following verification procedure after you install or upgrade the WebLM OVA file and configure WebLM. To verify the WebLM version on the WebLM console, perform the following: 1. Log in to the WebLM console with administrator privilege credentials. 2. On the home page, click About. The system displays the About WebLM window with the build details. 3. Verify the version number of WebLM. To verify the WebLM version on the WebLM command line interface, perform the following: 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Type swversion. ************************************************ StandAlone WebLM Software Information ************************************************ Standalone WebLM 7.1.x Build Number 7.1.x.xxxx Patch 7.1. Build Number 7.1.x.x.xxxxx Enhanced Access Security Gateway (EASG) overview EASG provides a secure method for Avaya services personnel to access the Avaya Aura application remotely and onsite. Access is under the control of the customer and can be enabled or disabled at any time. EASG must be enabled for Avaya Services to perform tasks necessary for the ongoing support, management and optimization of the solution. EASG is also required to enable remote proactive support tools such as Avaya Expert Systems and Avaya Healthcheck. December 2017 Deploying standalone Avaya WebLM on Cloud Services 28

29 Enhanced Access Security Gateway (EASG) overview Managing EASG from CLI About this task After deploying or upgrading an Avaya Aura application, you can enable, disable, or view the status of EASG. Before you begin Log in to the application CLI interface. 1. To view the status of EASG, run the command: EASGStatus. The system displays the status of EASG. 2. To enable EASG, do the following: a. Run the command: EASGManage --enableeasg. The system displays the following message. By enabling Avaya Services Logins you are granting Avaya access to your system. This is required to maximize the performance and value of your Avaya support entitlements, allowing Avaya to resolve product issues in a timely manner. The product must be registered using the Avaya Global Registration Tool (GRT, see to be eligible for Avaya remote connectivity. Please see the Avaya support site ( registration) for additional information for registering products and establishing remote access and alarming. b. When the system prompts, type yes. The system displays the message: EASG Access is enabled. 3. To disable EASG, do the following: a. Run the command: EASGManage --disableeasg. The system displays the following message. By disabling Avaya Services Logins you are denying Avaya access to your system. This is not recommended, as it can impact Avaya's ability to provide support for the product. Unless the customer is well versed in managing the product themselves, Avaya Services Logins should not be disabled. b. When the system prompts, type yes. The system displays the message: EASG Access is disabled. December 2017 Deploying standalone Avaya WebLM on Cloud Services 29

30 Post-installation Verification Viewing the EASG certificate information Log in to the application CLI interface. EASG site certificate EASG site certificates are used by the onsite Avaya technicians who do not have access to the Avaya network to generate a response to the EASG challenge. The technician will generate and provide the EASG site certificate to the customer. The customer loads this EASG site certificate on each server to which the customer has granted the technician access. The EASG site certificate will only allow access to systems on which it has been installed, and will only allow access to the given Avaya technician and cannot be used by anyone else to access the system including other Avaya technicians. Once this is done, the technician logs in with the EASG challenge/response. Managing site certificates Before you begin 1. Obtain the site certificate from the Avaya support technician. 2. You must load this site certificate on each server that the technician needs to access. Use a file transfer tool, such as WinSCP to copy the site certificate to /home/cust directory, where cust is the login ID. The directory might vary depending on the file transfer tool used. 3. Note the location of this certificate and use in place of installed_pkcs7_name in the commands. 4. You must have the following before loading the site certificate: Login ID and password Secure file transfer tool, such as WinSCP Site Authentication Factor 1. To install the site certificate: a. Run the following command: sudo EASGSiteCertManage --add <installed_pkcs7_name>. b. Save the Site Authentication Factor to share with the technician once on site. 2. To view information about a particular certificate: run the following command: sudo EASGSiteCertManage --list: To list all the site certificates that are currently installed on the system. sudo EASGSiteCertManage --show <installed_pkcs7_name>: To display detailed information about the specified site certificate. December 2017 Deploying standalone Avaya WebLM on Cloud Services 30

31 Enhanced Access Security Gateway (EASG) overview 3. To delete the site certificate, run the following command: sudo EASGSiteCertManage --delete <installed_pkcs7_name>: To delete the specified site certificate. sudo EASGSiteCertManage --delete all: To delete all the site certificates that are currently installed on the system. December 2017 Deploying standalone Avaya WebLM on Cloud Services 31

32 Chapter 8: Maintenance This chapter describes the procedures to change the WebLM IP address, FQDN, and other parameters from Command Line Interface (CLI). This chapter also provides information about performing backup and restore of WebLM. Note: The existing license files become invalid when you: change the WebLM IP address perform a WebLM update When you redeploy the WebLM, then you must reinstall a new license file to match the new Host ID generated in the WebLM server. Changing the IP, FQDN, DNS, Gateway, or Netmask addresses Before you begin Log in to the WebLM command line interface with administrator privilege CLI user credentials. Important: Ensure that WebLM maintenance is not in progress. 1. Type changeipfqdn IP <IP Address> FQDN <FQDN> GATEWAY <Gateway address> NETMASK <Netmask address> DNS <DNS address> SEARCH <search list for DNS>. Note: After a WebLM IP/FQDN change, the licenses become invalid. You must re-host the licenses. The license data varies based on the installed license as part of the license re-host. 2. To add more than one IP address for the DNS server, type changeipfqdn DNS primary_dns_ipaddress, secondary_dns_ipaddress, DNS_N_IPadress... December 2017 Deploying standalone Avaya WebLM on Cloud Services 32

33 Configuring multiple DNS IP addresses to changeipfqdn DNS primary_dns_ipaddress, secondary_dns_ipaddress,..., DNS_N_IPadress. You must separate each DNS IP address by a comma (,). For example, changeipfqdn - DNS , The system takes a few seconds to apply the DNS changes to the network. Note: The command to configure multiple DNS IP addresses overrides all the previous DNS IP address entries. Related links Rehosting license files on page 27 WebLM CLI operations on page 36 Updating network parameters for cloned WebLM VMWare cloning Configuring multiple DNS IP addresses Before you begin Deploy the WebLM OVA file. Start the WebLM virtual machine. When you turn on WebLM for the first time after you deploy the OVA file, the system applies the network configurations that you provided during the deployment of the WebLM OVA file. Note: The command to configure multiple DNS IP addresses overrides all the previous DNS IP address entries. 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. Important: Ensure that WebLM maintenance is not in progress. 2. Check the existing DNS IP address of WebLM. 3. To add more than one IP address for the DNS server, type changeipfqdn DNS primary_dns_ipaddress, secondary_dns_ipaddress, DNS_N_IPadress... to changeipfqdn DNS primary_dns_ipaddress, secondary_dns_ipaddress,..., DNS_N_IPadress. December 2017 Deploying standalone Avaya WebLM on Cloud Services 33

34 Maintenance You must separate each DNS IP address by a comma (,). For example, changeipfqdn - DNS , The system takes a few seconds to apply the DNS changes to the network. 4. Log in to the WebLM console with administrator privilege credentials. 5. Ensure that the system displays the multiple DNS IP addresses. Related links WebLM CLI operations on page 36 Configuring the time zone 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Type configuretimezone. 3. Select the time zone from the list. For example, America/Denver. Related links WebLM CLI operations on page 36 Configuring the NTP server 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Type configurentp <IP address of the NTP server>. The system configures the NTP server. Related links WebLM CLI operations on page 36 December 2017 Deploying standalone Avaya WebLM on Cloud Services 34

35 Resetting the WebLM password through CLI Resetting the WebLM password through CLI 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Type the weblm_password <reset restore> command. Using password reset you can back up the existing user configuration and apply the predefined password. By resetting the password, you can restore the backed up configuration. Performing WebLM backup 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Perform one of the following: Type WebLMBackup <backup_location> and provide the backup location as a parameter. In this case, the WebLM backup is stored at the location you specify as a parameter. Type WebLMBackup. In this case, the backup location is not provided, and the WebLM backup is stored at the default location. You can edit the default location using the conf.properties file. Copy the backup files to a remote computer or to an external storage device. Performing WebLM restore 1. Log in to the WebLM command line interface with administrator privilege CLI user credentials. 2. Depending on your restore requirement, perform one of the following: Type WebLMRestore full <backup_location> to restore all the WebLM files by picking up the backup file at the specified location. Type WebLMRestore full to restore all the WebLM files by picking up the backup file at the default location specified in conf.properties. Type WebLMRestore selective <backup_location> to restore a set of files necessary for the functionality of the WebLM server from the specified backup location. December 2017 Deploying standalone Avaya WebLM on Cloud Services 35

36 Maintenance Type WebLMRestore selective to restore a set of files necessary for the functionality of the WebLM server from the default location specified in conf.properties. Note: The conf.properties file is located at /opt/vsp/conf.properties. You can modify the default location of the backup files through the conf.properties file. WebLM CLI operations # Command Parameters Description Usage 1. changeipfqdn IP < new IP address for WebLM > FQDN < new fully qualified domain name of WebLM > GATEWAY < new gateway address for WebLM > NETMASK < new netmask address for WebLM > DNS < new DNS address for WebLM > SEARCH < new search list for DNS addresses > 2. configurentp < IP address of the NTP server > 3. configuretim ezone 4. WebLMPatchde ploy < Time zone that you want to select > < absolute path to the WebLM service pack, feature pack, or the software patch > Updates the IP address, FQDN, Gateway, Netmask, DNS, and the search list with the new value. Configures the NTP server details. Configures the time zone with the value that you select. Installs the software patch, the service pack, or the feature pack for WebLM. changeipfqdn -IP < new IP address > changeipfqdn - FQDN < new fully qualified domain name > changeipfqdn -IP < new IP address > - GATEWAY < new gateway address for WebLM > -SEARCH < new search list for DNS addresses > configurentp < IP address of the NTP server > Separate the IP addresses or the host names of the NTP servers with commas (,). configuretimezone Select a time zone. For example, America/ Denver WebLMPatchdeploy <absolute path to home/ admin/< WebLM FeaturepackName > Table continues December 2017 Deploying standalone Avaya WebLM on Cloud Services 36

37 WebLM CLI operations # Command Parameters Description Usage 5. weblm_passwo rd <reset> <restore> 6. configuretls <TLSv1.2> <TLSv1.1> <TLSv1> Reset option backs up the existing user configuration and applies the predefined password. Restore option restores the backed-up user configuration. The utility also supports the nonroot user, such as admin. Configures the TLS support. Note: Copy the WebLM feature pack or patches that you install to /home/ admin/. weblm_password reset weblm_password restore Type one of the following option: enable TLSv1.2 enable TLSv1.2 and TLSv1.1 enable TLSv1.2, TLSv1.1 and TLSv1.0 December 2017 Deploying standalone Avaya WebLM on Cloud Services 37

38 Chapter 9: Resources Documentation The following table lists the documents related to this product. Download the documents from the Avaya Support website at Title Use this document to: Audience Overview Avaya Aura Virtualized Environment Solution Description Implementing Deploying Avaya Aura applications from System Manager Upgrading and Migrating Avaya Aura applications from System Manager Administering Administering standalone Avaya WebLM Administering Avaya Aura System Manager Using Using the Solution Deployment Manager client Understand the high-level solution features and functionality Deploy the Avaya Aura applications with Solution Deployment Manager Upgrade the Avaya Aura applications with Solution Deployment Manager Perform administration tasks Perform administration tasks Deploy Avaya Aura applications and install patches on Avaya Aura applications. Customers and sales, services, and support personnel Implementation personnel Implementation personnel System administrators System administrators System administrators Finding documents on the Avaya Support website 1. Navigate to 2. At the top of the screen, type your username and password and click Login. 3. Click Support by Product > Documents. 4. In Enter your Product Here, type the product name and then select the product from the list. December 2017 Deploying standalone Avaya WebLM on Cloud Services 38

39 Amazon Web Services documentation 5. In Choose Release, select an appropriate release number. 6. In the Content Type filter, click a document type, or click Select All to see a list of all available documents. For example, for user guides, click User Guides in the Content Type filter. The list displays the documents only from the selected category. 7. Click Enter. Amazon Web Services documentation For information about the Amazon Web Services documentation, go to the AWS documentation website at Training The following courses are available on the Avaya Learning website at After you log into the website, enter the course code or the course title in the Search field and click Go to search for the course. Course code Course title Type 2007V/W What is New in Avaya Aura Release AvayaLive Engage Theory 2008V/W 2009V/W 2010V/W 2011/V/W What is New in Avaya Aura Application Enablement Services 7.0 What is New in Avaya Aura Communication Manager 7.0 What is New in Avaya Aura Presence Services 7.0 What is New in Avaya Aura Session Manager Release and Avaya Aura System Manager Release V Migrating and Upgrading to Avaya Aura Platform V Avaya Aura Release Solution Management AvayaLive Engage Theory AvayaLive Engage Theory AvayaLive Engage Theory AvayaLive Engage Theory AvayaLive Engage Theory AvayaLive Engage Theory 1A00234E Avaya Aura Fundamental Technology AvayaLive Engage Theory 1A00236E Knowledge Access: Avaya Aura Session Manager and Avaya Aura System Manager Fundamentals AvayaLive Engage Theory Table continues December 2017 Deploying standalone Avaya WebLM on Cloud Services 39