Cisco WAE 6.4 Server Installation Guide

CLI

To start the license server daemon ( lmgrd) and specify the lmgrd log file name and location, enter the following from /opt/cariden/software/flexlm/current/bin.

Example: /lmg rd -c /opt/cariden/etc/MATE_Floating.lic -l /opt/cariden/logs/lmgrd.log

Web UI

Step 1 Create a backup of the Cisco daemon file so that it can be easily restored in case of failure.

Step 2 Copy the Cisco daemon files to the flexlm/web directory.

Step 3 To start the license server using the web UI, first configure the following parameters from the /opt/cariden/software/flexlm/web directory. For more information, see lmadmin -help.

a. By default, the lmadmin server has a user named “admin” with a password of “admin.” If needed, add another user to this lmadmin server.

./lmadmin -useradd <username> - pass <password>

b. Import the WAE Design license file that was installed.

./lmadmin -import <path>/<license_filename>

Example: l madmin -import ~/.cariden/etc/MATE_Floating.lic

c. Start the lmadmin process with its default settings.

Step 4 Start the license server web UI, which by default uses a non-secure port of 8090. By entering the following in a web browser, you are redirected to the secure port.

Step 5 Click the Administration link, and log in using the an administrative username and password. Both have a default of “admin.”

Step 6 Click the Vendor Daemon Configuration tab, click the Administer link, and then click Start.

Log Files

By default, the lmadmin logs are in /opt/cariden/software/flexlm/web/logs.

The lmgrd log files are located wherever you specified the <log_path_filename>.log when starting the lmgrd daemon ( lmgrd -l <log_path_filename>.log).

Port Verification

To verify the ports, you can use any of several methods, as follows.

• Verify the license server daemon port is running. For example, you can telnet to this port to verify that it is running.

telnet <license_server_IP_address> <license_server_daemon_port>

Example: te lnet 127.0.0.1 27000

• Verify the license server is listening to the specified port.

Example: nets tat -a | egrep '27000[0-9]'

• View the lmgrd log file, which indicates on which ports the license server and Cisco daemons are listening.

Example:

• For lmadmin, go to the admin page.

– To verify the server daemon’s port, select Administration->Server Configuration->License Server Configuration.

– To verify the Cisco daemon's port, select Administration->Server Configuration->Vendor Daemon Configuration.

Distribute Information to Clients

Either distribute the same floating.lic file that you installed to all WAE Design users who need it, or give them both the MAC address and hostname for the license server. Having users install licenses via the MAC address and port is the recommended practice since it eases administration.

After end users install the floating license once, the license is automatically validated from the server each time the user opens the WAE Design GUI or runs the CLI tools.

Set Up Access Control List for Web Server

If you are using the web server to administer licenses, you can set up an access control list. This is optional, but doing so can improve the security of who can access the web server, as well as give you an easily maintainable list of license users. To do this, you need to know the user ID for all users who are checking out licenses from the license server. The user ID is what they use to log in to their operating systems.

Step 1 Create and open a file named cisco.opt in /opt/cariden/software/flexlm/current/bin.

Step 2 Create groups to make it easier and faster to configure inclusions and exclusions. You can then use these groups, rather than specifying individual users.

Example: The group name is akdevops, and each name following it is a user.

Step 3 For each user or group that you want to grant license access, add an INCLUDEALL line.

INCLUDEALL type {user_name | group_name}

Example:

Step 4 For each user or group you want to exclude from accessing the license server, add an EXCLUDEALL USER line.

Example:

Step 5 Save the file.

Configure Borrowing Parameters

Note If you have a floating license that was generated before May 2015, you must acquire a new one.

Step 1 Configure the /opt/cariden/bin/cisco.opt file to define who is permitted to borrow licenses.

Anyone not in an INCLUDE_BORROW statement is not permitted to borrow licenses. Thus, it is easier to use groups that user names.

The inclusion format is as follows. You must specify a line item for each feature. For a list of these features, use the license_check tool.

Example:

Step 2 You can refine this INCLUDE_BORROW list by excluding users. The EXCLUDE_BORROW has precedence over the INCLUDE_BORROW statements such that if a user or group is identified in both lists, that user or group will be excluded as specified.

Example:

Step 3 Optional: Specify the number of licenses for a feature that cannot be borrowed. This is useful for ensuring that users who need to check out licenses will have them available.

Example: Save 23 MD_Sim licenses for use by those who are not borrowing licenses

Verify Licenses in Use

Use the lmstat command to summarize how many licenses are in the original license file and how many are in use.

The results show how many licenses are checked out and borrowed. The output contains *_Users entries and entries for each feature. The *_Users is determined by the users who have access to the license. Each feature lists a set of licenses checked out for that feature.

Example Output:

Checked-out licenses are only displayed for *_Users, whereas borrowed licenses are shown for *_Users, as well as for individual features.

The output uses the following format, where <time> is the time at which the license was checked out or borrowed. The <license_handle> is a unique ID for the license. If a user has the same license checked out twice, for example, each instance has a unique <license_handle>.

Example Checked-Out License:

Licenses that are borrowed are listed with a (linger: #) notation, where # is the number of seconds for which the license is borrowed.

Example Borrowed License:

Reclaim Unused Licenses

You can reclaim licenses that have been checked out or borrowed. This feature is useful when a license remains idle, such as when an employee is on vacation or accidentally has the license running on two devices.

Reclaiming licenses is only valid through the CLI lmremove command.

Use the lmstat -a command described in the Verify Licenses in Use section to identify the required inputs to the lmremove command.

lmstat -a Output for Examples

In the next two sections, examples use the following lmstat -a output as their starting point. Compare the results of these examples to this output to see the differences between the two.

Reclaim All Licenses for Specific User

To reclaim all licenses for a specific user, enter this command.

Example: This example reclaims all licenses for the user named “dusan.”

The lmstat -a command now shows dusan removed as a user.

Reclaim License for a Specific Feature

To reclaim a license for a specific feature, enter this command.

Example: This example reclaims a single license from the user named “dusan.”

The lmstat -a command now shows the license 37337 removed for the user named dusan, though dusan still has use of license 42295.