Setting Up Licensing on Cloud

This section describes how to complete the setup and installation for running license server on Amazon Elastic Compute Cloud (Amazon EC2), Google Compute Engine (GCE), and Microsoft Azure. 

It includes the following topics:

Software Requirements (on Linux)

• lsb-core is required to run Flexera utilities, like lmutil and lmstat, as well as the server (lmgrd). On Red Hat instances, you can use redhat-lsb-core
• Update glibc to version 2.14 or above
• Latest version of the License Server is SftShrTools 22.01-s002

Cloud License Server Use Model

• The following image illustrates the cloud license server use model on Amazon EC2:

• The following image illustrates the cloud license server use model on Google Compute Engine:

• The following image illustrates the cloud license server use model on Microsoft Azure:
  
  

Setting Up VPC and ENI on Amazon EC2

Cadence requires a MAC address from an elastic network interface (ENI) to generate a License File.

Perform  the following steps to set up the ENI:

1. Set up the virtual private cloud (VPC) for the cloud environment within which the license server and clients will reside. Refer to Getting Started with Amazon VPC and Default VPC and Default Subnets on the Amazon documentation website for more information. 
2. Create an ENI and attach it to the Amazon web services (AWS) instance that will be used as the server within this VPC. Refer to Elastic Network Interfaces on the Amazon documentation website for more information.

Generating a License for Amazon EC2

Perform the following steps:

1.  Once the ENI is created, run the mfp tool with the -cl aws option to determine the MAC address to use as host ID, as shown below:

   [ec2-user@ip-172-17-33-91 ~]$ ./mfp -cl aws Host name: ip-172-17-33-91.us-west-2.compute.internal Domain name: us-west-2.compute.internal Running mfp with Amazon EC2 cloud option 2 hostids found for this machine Please pick which of the following macs you would like to use. Enter a n umber from 1 to 2 1. 0a:3e:a3:f9:80:7e 2. 0a:d5:e1:5b:10:16 1 Generating text file: mfp_out.txt with this information Generating XML file: mfp_out.xml with this information Please forward these files to Cadence Design Systems.

   Following is an example of the mfp output generated on an Amazon EC2 instance:

   HostName=ip-172-17-33-91.us-west-2.compute.internal DomainName=us-west-2.compute.internal IPAddress=172.17.33.91 CloudType=Amazon EC2 UniqueID=eni-54f24455 MAC=0a:3e:a3:f9:80:7e ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ "mfp_out.txt" 6L, 178C

2. Send the mfp_out.txt and mfp_out.xml files that are generated to a Cadence representative to generate the license.

Migrating Amazon ENI Instances

Once license file is created with the ENI mac address, it works as a regular license file created with MAC addresses during the lifetime of the instance which uses the ENI.  If the server needs to be hosted on a different Amazon instance, detach the ENI from the old instance and attach it to the new instance. Methods to detach and attach ENI are described on the following pages on the Amazon documentation website:

• Detaching a Network Interface from an Instance

• Attaching a Network Interface When Launching an Instance
• Attaching a Network Interface to a Stopped or Running Instance

Generating a License for GCE

On Google Compute Engine, Cadence uses the instance ID for secondary verification. Hence, license server can be run only on the instance for which the license file is generated.

Perform the following steps on the GCE instance that will be used to run the server:

1. Run the lmhostid command to get the host ID or MAC address that will be used to generate license file.

2. Run the mfp tool with the cloud option of GCE, as shown below:

   [hprachi@redhatgcplic01 ~]$ ./mfp -cl gce Multiple IP Addresses detected. **Use an IP adress that will not change over time. IP Addresse(s) are: 1) 10.17.192.4 2) 10.17.200.4 Pick an IP Address to use (Type in a number between 1 and 2):1 Host name: redhatgcplic01 Domain name: c.cdns-licensing.internal Running mfp with Google Compute Engine option Found instance id Generating text file: mfp_out.txt with this information Generating XML file: mfp_out.xml with this information Please forward these files to Cadence Design Systems.

   Following is an example of the mfp output generated for GCE:

   HostName=redhatgcplic01 DomainName=c.cdns-licensing.internal IPAddress=10.17.192.4 CloudType=Google GCE UniqueID=1379392967683858313 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ "mfp_out.txt" 5L, 133C

3. Provide the lmhostid information and mfp files generated to Cadence for license file generation. 

Generating a License for Microsoft Azure

Cadence uses the instance ID for secondary verification. Therefore, the license server can be run only on the instance for which the license file has been generated.

Perform the following steps on the Microsoft Azure instance that will be used to run the server:

1. Run the lmhostid command to get the host ID or MAC address that will be used to generate license file.

2. Run the mfp tool with the azure cloud option of Microsoft Azure, as shown below:

   [user@LicenseLinTest02 64bit]$ ./mfp -cl azure mfp, 12.12-p001 Copyright © 2012-2018 Cadence Design Systems, Inc. All rights reserved worldwide. Host name: LicenseLinTest02 Domain name: lqjzxlatawcutbr4xiwkpfvhxf.dx.internal.cloudapp.net IPAddress: 10.17.31.135 CloudType: Microsoft Azure UniqueID: f8202b22-3fa2-42ec-b816-4463a2761ed2 Generating text file: mfp_out.txt with this information Generating XML file: mfp_out.xml with this information Please forward these files to Cadence Design Systems.

   Following is an example of the mfp output generated for Microsoft Azure:

   [user@LicenseLinTest02 64bit]$ cat mfp_out.txt HostName=LicenseLinTest02 DomainName=lqjzxlatawcutbr4xiwkpfvhxf.dx.internal.cloudapp.net IPAddress=10.17.31.135 CloudType=Microsoft Azure UniqueID=f8202b22-3fa2-42ec-b816-4463a2761ed2

3. Provide the lmhostid information and mfp files generated to Cadence for license file generation.