0% found this document useful (0 votes)

53 views74 pages

Licenseserver Usage Guide

Uploaded by

narendrabalu1989

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

53 views74 pages

Licenseserver Usage Guide

Uploaded by

narendrabalu1989

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 74

MSC Licensing User’s Guide

MSC Licensing Lithium

User’s Guide
Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: [email protected]
Email: [email protected]

Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: [email protected]
Email: [email protected]

Worldwide Web
www.mscsoftware.com

Disclaimer
MSC Software Corporation reserves the right to make changes in specifications and other information contained in this
document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are
not intended to be exhaustive or to apply to any particular engineering problem or design. MSC Software Corporation
assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of
any information contained herein.

User Documentation: Copyright  2020 MSC Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or
distribution of this document, in whole or in part, without the prior written consent of MSC Software Corporation is
prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC Software
suppliers. Additional terms and conditions and/or notices may apply for certain third party software. Such additional third
party software terms and conditions and/or notices may be set forth in documentation and/or at
http://www.mscsoftware.com/thirdpartysoftware (or successor website designated by MSC from time to time).
The MSC Software Logo, MSC, Actran, Adams, MSC Apex, MSC One, Digimat, Dytran, Easy5, MSC Fatigue, Marc,
MSC Nastran, Patran, SimDesigner, Simufact, SimXpert, Sinda, and Simulating Reality are trademarks or registered
trademarks of the MSC Software Corporation and/or its subsidiaries in the United States and/or other countries. Hexagon
and the Hexagon logo are trademarks or registered trademarks of Hexagon AB and/or its subsidiaries.
NASTRAN is a registered trademark of NASA. FlexNet Manager is a trademark or registered trademark of Flexera
Software, Inc. All other trademarks are the property of their respective owners.
December 8, 2020

ZZ:LI:LIC:Z:DC-INFO-PDF
Contents
Licensing User’s Guide

Contents
Preface
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Purpose of This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Contents of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Typographical Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Internet Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Section 1
Windows Operating System

1 Installing MSC Licensing

Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
License Server Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
License Server Diagnostics (MSC Nastran Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Upgrade/Uninstall the Existing Windows Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 FLEXlm/FlexNet and Licensing Management

Introduction to FLEXlm/FlexNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Types of Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
FLEXlm Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Determining Hostid of License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
License Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Manual Configuration of License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4 MSC Licensing User’s Guide

Getting Started Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Testing Your TCP/IP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Internet Domain Name Server (DNS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Manual Installation of MSC Licensing Using a New Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Obtain a License File for Your Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Edit/Update Your License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Place the License File on the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Use of lmtools.exe to Configure FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Set Up Clients to Access the Floating License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Using a Renewed/Changed License on an Existing Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Update Your License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Edit The New Licens e File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Replace License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Stop and Restart the License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Uninstalling FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Reinstalling FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Section 2
Linux Operating System

3 Installing MSC Licensing

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
License Server Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
License Server Diagnostics (MSC Nastran Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Installation on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Terminal/Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Upgrade/Uninstall the Existing Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4 FLEXlm/FlexNet and Licensing Management

Introduction to FLEXlm/FlexNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Types of Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
FLEXlm Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Determining Hostid of License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
License Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Manual Configuration of License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Contents 5

Getting Started Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Testing Your TCP/IP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Internet Domain Name Server (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Manual Installation of MSC License Server Using a New LINUX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Obtain a License File for Your Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Edit/Update Your License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Place the License File on the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Check Paths and Server Names in the license.dat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Start the Manager Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Set Up Clients to Access the Floating License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Using a Renewed/Changed License on an Existing LINUX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Edit the New Licens e File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Replace License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Restart Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Restarting MSC Licensing Server on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Stop the FLEXlm Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Restart the FLEXlm Service with MSCLIC_INI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Uninstalling FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Uninstall the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Remove the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Additional Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Section 3
General

5 Usage Reporting Tool

Usage Reporting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Usage Reporting Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Daily Detailed Usage (DDU) Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Daily Summary Usage (DSU) Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Automatic Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Off Network Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
NODATA Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
GLIC Value in NODATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
BURST POOL Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Triad Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Flexera Debug Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
License Server Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Manual Usage Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 MSC Licensing User’s Guide

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Platform Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Preface

Preface


Purpose of This Guide

Contents of This Guide
 Typographical Conventions

About This Guide

Technical Support

Internet Resources
8 MSC Licensing User’s Guide
About This Guide

About This Guide

This Guide is MSC Licensing Guide. It contains information about installing and running license manager
and its components.

Purpose of This Guide

This guide explains the procedure for installing MSC Licensing server on Windows and Linux systems. It
also describes how to install the associated components. This purpose of this guide is to:
 Help you install the licensing server on Windows and Linux platforms.
 Identify and ensure that the installation is successful.
 Provide you with basic troubleshooting.
 Provide you information about files, directories, and their location in the installed folders.

Contents of This Guide

The principal categories of information are found under the following titles:

Chapter Title Description

SECTION 1: MICROSOFT WINDOWS
Chapter 1 Installing MSC Licensing Pre-requisites and installation procedure is
described in this chapter
Chapter 2 FLEXlm/FlexNet and Licensing Management Server setup related and general
troubleshooting is discussed in this chapter.
SECTION 2: LINUX
Chapter 3 Installing MSC Licensing Pre-requisites and installation procedure is
described in this chapter
Chapter 4 FLEXlm/FlexNet and Licensing Management Server setup related and general
troubleshooting is discussed in this chapter.
SECTION 3: GENERAL
Chapter 5 Usage Reporting Tool Information regarding usage and reporting is
discussed in this chapter

The information in this manual is both descriptive and theoretical. You will find some techniques discussed
detail. You will also find specific instructions for operating the various options offered by Marc and Mentat.

Typographical Conventions
The section provides a brief overview of the typographical conventions used in the document to help the user
better follow the MSC Nastran documentation.
Preface 9

This section describes some syntax that will help you in understanding text in the various chapters and thus
in facilitating your learning process. It contains stylistic conventions to denote user action, to emphasize
particular aspects of Marc and Mentat to signal other differences within the text.
Adobe Body and general text
Garamond Pro
Courier New  Represents command-line options of Marc and .
 Directory names and paths
 File names and Paths
 Linux terminal script
Example: lmreread -c
<parent>/msc/MSC.Licensing/licenses/license.dat
Bold Text  Highlights
 Dialog box names
 Buttons
 Menus
 User inputs
 The commands/user inputs for all descriptions related to terminal commands.
 Default values
Example: [root@vm-tmrhel73 MSC]# ./msc_licensing_lithium_linux64.bin
HelveticaNeueL  Hyperlinks
T Pro Cn 57  Weblinks
Example: Chapter 5: Usage Reporting Tool
Italic Text Represents references to books.

Example: Volume A:Theory and User Information

10 MSC Licensing User’s Guide
Technical Support

Technical Support
For technical support phone numbers and contact information, please visit:
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

Support Center
http://simcompanion.mscsoftware.com
Support Online. The Support Center provides technical articles, frequently asked questions, and
documentation from a single location.

Internet Resources
MSC Software (www.mscsoftware.com)
MSC Software corporate site with information on the latest events, products, and services for the
CAD/CAE/CAM marketplace.

MSC Software Download Center

https://mscsoftware.subscribenet.com
Section 1: Windows Operating System

Section 1

Windows Operating System

Chapter 1: Installing MSC Licensing

1 Installing MSC Licensing


Installation Prerequisites

Operating System Requirements

Installation on Windows

Upgrade/Uninstall the Existing Windows Installation
14 MSC Licensing User’s Guide
Installation Prerequisites

Installation Prerequisites
 Before installing the latest MSC License Server, uninstall all the older versions of the MSC License
Server. The installer will try to detect the old installation and inform the user to uninstall/remove
the old server.
 Download the MSC Licensing installation package from the MSC Software Download Center. This
installer supports 64-bit versions of Windows.
 Run the installation executable with the option Run as Administrator. Certain features of the
licensing installation require administrator privileges even though the license server does not require
Administrator privileges for normal operation.
 To complete the installation of MSC licensing you will need a valid MSC license file.

Operating System Requirements

The minimum operating system version required to run the MSC license server and related tools are listed
in the following table:

Platform Hardware Supported Operating Systems

win64 x64 Windows 7 Professional, Enterprise, Ultimate
Windows 10 Professional, Enterprise
Windows Server 2016

License Server Specifications

All MSC applications support use of the standard FLEXlm environment variables for specifying the license
servers to be used for license requests.
For each method, the actual license specification can consist of one or more strings containing either a license
server or the fully qualified path name of a license file.
The environment variable MSC_LICENSE_FILE is the preferred way to set a license server specification. All
MSC applications also support use of the LM_LICENSE_FILE environment variable. If both of these are set,
the value of MSC_LICENSE_FILE is used.
Some MSC applications also support other methods for setting the license specification. For example, MSC
Nastran uses the AUTH keyword (on either the command line or in an RC file) for setting the license
specification. If AUTH is used, it overrides the values on MSC_LICENSE_FILE and/or LM_LICENSE_FILE.
CHAPTER 1 15
Installing MSC Licensing

License Server Diagnostics (MSC Nastran Only)

MSC Nastran users can set the AUTHINFO keyword to enable licensing diagnostics. The value of AUTHINFO
can be a whole number from 0 (no diagnostics) to 9 (very detailed diagnostics). The diagnostics are printed
to the MSC Nastran.log file.

Note: Older versions of MSC Nastran can have problems with AUTHINFO settings greater than 6.

Installation on Windows
This section demonstrates the procedure to install the MSC License Server on Windows system.
The installation video demonstrates the licensing installation procedure with the available license.

 Click to play the video Online.

 Click to download the video.

The detailed installation procedure is available as follows:

1. Run the installation executable with the option Run as Administrator. If your system already has the
older version of the MSC Licensing Server then it shows the following message.

2. Click Yes to continue.

3. The MSC Licensing Lithium window appears.
16 MSC Licensing User’s Guide
Installation on Windows

4. Read the information and click Next to continue.

The Installer Requirements window appears
.
CHAPTER 1 17
Installing MSC Licensing

5. Review the installer requirements and click Next to continue

Note: You must have a valid, unexpired MSC license file before the MSC License Server
can be installed.

If you do not have an MSC license file, contact your MSC representative before
continuing with the installation.

This screen provides the HostID that MSC uses to generate the license file. It also provides a list of
HostIDs identified by the ipconfig/all command and labels them in the Installer screen. The
preferred HostID is displayed for you on this screen.
The Choose Destination Folders window appears.

6. Specify paths for License Manager Executable Folder and License Manager Log File Folder. It is
recommended to accept the default folder locations.
To change the locations, click Browse and choose the directories to install the MSC License Server
executables and store the MSC Licensing Log Files.
 The default destination for the License Manager Executable folder:
C:\Program Files\MSC.Software\MSC Licensing\Lithium
 The default destination for License Manager Log File folder:
C:\MSC.Software\MSC Licensing\Lithium\LOG
Use Browse to select an alternate destination folder. You must have permission to write to the
selected folder.
7. Click Next to continue.
18 MSC Licensing User’s Guide
Installation on Windows

The Select the License File window appears.

8. Click Browse and select the license file that was provided by MSC Software.

The License files details are given bellow:

Fields Details
License File Reference ID Unique Reference Number for the specified
license file. This number may be helpful for
support requests.
Product Type  MSC One
 MasterKey Plus
 Seat Based License
License Type  Lease
 Perpetual
Usage Reporting Requirement  Automatic
 Manual
 No Reporting Required

The following error message appears if one or more feature entries in the license file expired.
CHAPTER 1 19
Installing MSC Licensing

9. Click OK to continue.
The Automatic Reporting of Usage Data appears.

Note: The data reporting scheme is different for different types of licenses. Contact
customer support for more details.

The MSC Licensing program includes a Usage Reporting Tool that provides valuable usage summary
information to MSC to improve our products. A full description if the usage data sent to MSC is
provided in Chapter 5: Usage Reporting Tool of this User Guide. No personal data is collected as part of
this program. To participate,
10. Click Next to continue the installation.
In cases where the customer is required to report usage and deactivates the Automatic Usage
Reporting option, the following screen will appear to inform the user of the Manual Reporting
Requirement.
20 MSC Licensing User’s Guide
Installation on Windows

11. Read the Information and click Next to continue the installation.
The Licensing Server Settings window appears.

12. Specify the License Server Settings and click Next to continue the installation.
Specify the License Server Settings as follows:
a. Specify an alternate lmgrd port number (the default value is 27500; any number from 1 to 64000
is acceptable).
b. Specify an alternate MSC daemon port number (the default value is blank; any number from 1
to 64000 is acceptable).
c. Specify an alternate hostname (For example, fully qualified hostname or IP address).
d. Optional: Browse and select the option file and path.
e. Specify the privilege level for license manager access.
CHAPTER 1 21
Installing MSC Licensing

f. The license manager will start automatically. Uncheck this box to install the license manager
without the automatic starting.
A window about the files are being copied appears.

13. Review the installation settings and click Next to complete the installation.
The MSC Licensing-InstallShield Wizard appears.

14. Click OK to finish the installation of the MSC License Server.

The installer creates a program group on the Start menu containing the lmtools utility. This utility
can be used to start, stop, and restart the license server, and make other changes to the license server
configuration.
22 MSC Licensing User’s Guide
Upgrade/Uninstall the Existing Windows Installation

The Installation Complete window appears.

15. Select the desktop icons to be created and click Finish to complete the installation.

Note: The MSC_LICENSE_FILE environment variable setting is displayed on the screen. Use this
setting on the client machines to access the MSC License Manager.

Upgrade/Uninstall the Existing Windows Installation

Upgrade/uninstall can be done using the control panel. This allows the user to modify, repair or remove the
current installation.
1. Click Start  Control Panel  Uninstall a Program.
The MSC Licensing Lithium (Maintenance) window appears.
CHAPTER 1 23
Installing MSC Licensing

You will see two choices:

• Repair
• Remove
Depending upon what option you select, different windows will appear. The procedure for
bothoptions are explained in the following subsections.

Repair
To repair the current installation, select repair and do the following:
1. Click Next.
The maintenance operations complete and the Maintenance Complete window appears.

It is recommended that you select the first option to restart your computer to apply the changes.
2. Click Finish.

Remove
To remove the current installation, select remove and do the following:
1. Select Remove.
2. Click Next.
The MSC Licensing - InstallShield Wizard message appears.
24 MSC Licensing User’s Guide
Upgrade/Uninstall the Existing Windows Installation

3. Click Yes.
The Setup Status window followed by the InstallShield Wizard finishes the uninstall operations and
the Maintenance Complete window appears.

It is recommended that you select the first option to restart your computer to apply the changes.
4. Click Finish.
Chapter 2: FLEXlm/FlexNet and Licensing Management

2 FLEXlm/FlexNet and
Licensing Management

Introduction to FLEXlm/FlexNet

License Request Process

Manual Configuration of License Server

Getting Started Checklist

Determining Hostid of License Server

Testing Your TCP/IP Connection

Internet Domain Name Server (DNS)

Manual Installation of MSC Licensing Using a New Windows Server

Using a Renewed/Changed License on an Existing Windows Server
 Uninstalling FLEXlm

Additional Documentation
26 MSC Licensing User’s Guide
Introduction to FLEXlm/FlexNet

Introduction to FLEXlm/FlexNet
FLEXlm is a network license manager which is used to control the use of software products. FLEXlm allows
software licenses to be available (float) anywhere on a network, instead of being tied to specific machines.
Floating licensing benefits both users and system administrators. Users can make more efficient use of fewer
licenses by sharing them on the network. You can control who uses the licensed application and the node or
nodes where the licenses are available.
MSC Licensing Lithium is based on FlexNet, details of which are as follows:

Version: 11.16.3.0
Build: 246884_x64_n6

Types of Licenses
MSC Software provides you with two license options:
 Concurrent License
 Node-locked License

Concurrent License
A concurrent license limits the maximum number of simultaneous users of a given set of license features
within a given site. A token based (eg. MasterKey Plus and MSC One) license is essentially the same, but
allows access to all included license features, which is limited only by a maximum token count that can be
used at any one time. Both of these licenses are referred to as floating. Please contact your MSC Software sales
representative for more details on licensing options.
Typically, an MSC License Server (a separate program from the product installer) is installed on a network
server to administer the licenses. The program files are then either loaded on individual computers or on the
network server.

Node-locked License
A node-locked license is used to run a product on a given computer. The number of product applications
running at any given moment is limited by the number of seats licensed.
Both types of licenses use the license management software, which is designed to prevent tampering with the
system date. If the system date is modified after product has been installed, the product license will be
invalidated. Furthermore, a new license will not fix this problem. See the troubleshooting section in the
Release Guide for further information.

Caution: Do NOT reset the system date after the installation. This can invalidate the license. Re-
validation can be a difficult and cumbersome process.

FLEXlm Components
The four main components of FLEXlm are:
CHAPTER 2 27
General Information - MSC Licensing

 License File (the product license file is called license.dat).

 Application Program (<product>).
 License Server (MSC).
 Vendor Daemon (MSC).

License File
Licensing data is stored in a text file named license.dat. The license file is created by the MSC Software
licensing staff and sent via email to the system administrator. It contains information about the server nodes
and vendor daemons, and one line of data (called a FEATURE line) for each licensed feature. A feature line
contains an encryption code based on the data in that line, the hostids (“host-id”, or a unique
identifier for a computer) specified in the server lines, and other vendor-specific data.
Multiple License Servers: Set the MSC_LICENSE_FILE variable to reference multiple servers using a
separator character between file names; on Linux this character is a colon (“:”) and on Windows it is a
semicolon (“;”). The order of the license servers in the MSC_LICENSE_FILE variable is the order that license
servers will be checked for a license request.

Application Program
The application that employs FLEXlm licensing is linked with the program module that provides the
communication with the license daemons. During execution, the application program communicates with
the vendor daemon to request a license.

License Server
An MSC License Server is installed on a network server to administer the floating licenses within a local area
network. Then, the program files are either loaded on individual computers or on the network server. For a
single or standalone installation, the server and the application are installed on the same machine. The server
manages the License Manager and Vendor daemons.

Note: The FLEXlm version of the MSC License Server must be greater than or equal to the
FLEXlm version linked into the application programs.

License Manager Daemon

lmgrd, the license daemon, handles the initial contact with the client application programs. It passes the
connection on to the vendor daemon. It also starts and restarts the vendor daemons. FLEXlm permits
multiple redundant license manager daemons on different server nodes. It allows you to make your license
available if any two out of three server nodes are running. You do not have to split your licenses among
multiple servers or rely on any one machine.

daemon keeps track of how many licenses are checked out and who has them. Note that the MSC daemon
serves many other MSC Software products, including MSC Nastran, Patran, and Adams, among others. All
users would lose their licenses, if the MSC daemon terminates for any reason. Users regain their license when
the daemon restarts.
Client programs communicate with the vendor daemon through TCP/IP sockets. This enables client
programs and daemon processes to be on separate nodes in a network. The traffic between the client and the
daemon is machine independent, which means that any process can run on any machine type or operating
system, allowing a heterogeneous network.

Determining Hostid of License Server

Before running any FLEXlm-licensed program using floating licenses, you must set up your license server
node or nodes. You must select which node or nodes to run your license servers on and provide the hostid
of those machines for installation.
To obtain a license file from MSC, you need to determine the hostid of the machine that will function as
your license server.
1. Execute the lmhostid command from the command:
<flexlm install folder> ./lmutil lmhostid
2. This will list the possible 'hostid's' of the machine.
3. Choose the Ethernet adapter local area connection hostid. Wireless is not preferred.
(Using command ifconfig you could check the adapter type)
After sending the hostid of your server machines to MSC Software support, the support staff will
send you a license file that enables the application software.
4. Once you receive a license file, you must install it on your system and start up the license server.

License Request Process

When the application program calls the FLEXlm client library to request a license, the following process
occurs:
1. The license module in the client application finds the license file, which includes the host name and
port number of the license manager daemon (lmgrd).
2. The client establishes a connection with the license manager daemon and tells it what vendor it needs
to talk to.
3. The license manager daemon determines which machine and port correspond to the master vendor
daemon (if multiple redundant daemons are running) and sends that information back to the client.
4. The client establishes a connection with the specified vendor daemon (MSC) and sends its request for
a license.
5. The vendor daemon checks to see if any licenses are available and sends a grant or denial back to the
client.
CHAPTER 2 29
General Information - MSC Licensing

6. The license module in the client returns to its caller with the grant or denial, and the application takes
the appropriate action.

Manual Configuration of License Server

You can configure most FLEXlm parameters by setting:
 The location of the license file.
 The location of all executables.
 The location of all log files.
 The TCP/IP port number of clients looking for the license manager.
In addition, you can reserve licenses for specific users, nodes, or groups and control other license-related
options.

Getting Started Checklist

As system administrator, you are responsible for setting up licensing on your system or network. If you are
an end user of the application and you are not involved in installing it, then you can skip this section.
In general, installing FLEXlm licensing requires the following steps:
1. Select your license server nodes and get their hostids.
2. Send the host ids to your MSC license administrator and obtain a license file (or the data to enter in
the license file) in return.
3. Determine how the new license file relates to any other license files that may already be on your
system, and install it appropriately.
4. Start lmgrd (the license daemon) manually, or set it up to run automatically at startup, using the
separately installed software (MSC Licensing FLEXlm) on the server.

Testing Your TCP/IP Connection

The concurrent license management require that you are able to establish a TCP/IP network connection
between your computer and the License Server.
1. Find the hostname of the License Server.
2. To determine the appropriate hostname, examine the existing concurrent license file and look for
the SERVER command line.
The first argument is the hostname.
3. You can test if your computer can communicate with the license server by entering the command
ping hostname
If you get a return reply, then you have a TCP/IP connection established.
30 MSC Licensing User’s Guide
Internet Domain Name Server (DNS)

Internet Domain Name Server (DNS)

In addition to establishing a TCP/IP network connection between your computer and the License Server, the
License Server host (computer name) needs to be found by your internet domain name server (DNS). If the
host computer is inside a local-area-network (LAN) this is often automatic. If the host is not registered, you
may need to add it to your /etc/hosts or equivalent file.

Manual Installation of MSC Licensing Using a New

Windows Server

Obtain a License File for Your Server

To obtain a license file from MSC:
1. Determine the hostid of the machine that will function as your license server.
2. Execute the MSC_Licensing_FLEXlm_Lithium_windows64.exe available and
3. Select manual option to extract the required utilities.
https://mscsoftware.subscribenet.com/control/mnsc/product?child_plneID=593623
4. Execute the lmhostid command from the command prompt:
c:\Program Files\MSC.Software\MSC Licensing\Lithium\lmutil lmhostid
This will list the possible hostids of the machine.
5. Choose the Ethernet adapter local area connection hostid, wireless is not preferred.
(Using command ipconfig /all you could check the adapter type)

Edit/Update Your License

The License Server must be updated with the new license before it is used.
1. Verify that the license has a valid path for the DAEMON line, and a valid SERVER hostname in the
license file. The DAEMON line should have a path to the installed MSC.exe vendor daemon, normally
found in folder:
C:\Program Files\MSC.Software\MSC Licensing\Lithium
The DAEMON line should look similar to the following:
DAEMON MSC C:\Program Files\MSC.Software\MSC
Licensing\Lithium\MSC.exe
2. If the path to the daemon is incorrect, edit the license file and correct the path. The SERVER line
should look similar to:
SERVER <hostname> <value> <port>
For example:
SERVER server1 123465 27500
CHAPTER 2 31
General Information - MSC Licensing

Place the License File on the Server

3. Locate the license file in: c:\Program Files\MSC.Software\MSC
Licensing\Lithium\license.dat
The license file may be located anywhere on your license server.

Use of lmtools.exe to Configure FLEXlm

4. Use the lmtools.exe utility to start/stop, configure, and diagnose your FLEXlm license server.
You can access the Lmtools utility from the shortcut in the Start menu at:
Start  Programs  MSC.Software  lmtools

Start/Stop/Reread Advanced Settings

On the LMTOOLS dialog, by clicking the Edit Advanced settings button Start/Stop/Reread tab, you can:

 Restrict lmdown: So that it only works logged into the system hosting the license server. This
prevents the license server from being shutdown from a remote machine.
 Disable lmdown utility: Use of task manager prevents the lmdown utility from running on the
machine hosting the license server. The license server can only be shutdown using the task manager.
 Disable lmremove of license file: By selecting this, licenses checked out by users cannot be removed
from the license server.
 Start Server: This starts the license server on the host machine.
 Stop Server: This asks the license server to stop on the host machine.
32 MSC Licensing User’s Guide
Using a Renewed/Changed License on an Existing Windows Server

• Force Server Shutdown: By selecting this button, the license server will be forced to stop
regardless of what the server is doing.
 ReRead License File: Forces the license server to reread the license file. This can be used when you
get a new license file and do not want to stop and restart the license server.

Note: MSC does not support re-reads involving change of license type (for example, seat based to
GROUP).

Set Up Clients to Access the Floating License

The MSC_LICENSE_FILE environment variable provides the location of licenses. It can be set in Control
Panel\System\Environment to <port>@<hostname>.

Using a Renewed/Changed License on an Existing

Windows Server
Follow these steps if you have an existing installation and have received new codes (as a renewal, change, etc.).

Update Your License

The License Server must be updated with the new license before it is used.
1. Do not overwrite the existing license file.
2. Verify that the license has a valid path for the DAEMON line, and a valid SERVER hostname in the
license file. The DAEMON line should have a path to the installed MSC.exe vendor daemon, normally
found in folder:
C:\Program Files\MSC.Software\MSC Licensing\Lithium
The DAEMON line should look similar to the following:
DAEMON MSC C:\Program Files\MSC.Software\MSC
Licensing\Lithium\MSC.exe
3. If the path to the daemon is incorrect, edit the license file and correct the path. The SERVER line
should look similar to:
SERVER <hostname> <value> <port>
For example:
SERVER server1 123465 27500

Edit The New License File

1. Place the new codes as a license file in the same directory as the existing license.dat file.
2. Name it license_new.dat.
CHAPTER 2 33
General Information - MSC Licensing

3. Change the SERVER and DAEMON lines in the new license file to include the same port number, server
name, and paths as the existing file. For example:
SERVER server1 123465 27500
DAEMON MSC “c:\Program Files\MSC.Software\MSC
Licensing\Lithium\msc.exe”

Replace License File

4. Use Windows Explorer to rename the existing license.dat file to license_old.dat, and the new
file to the current license file name (i.e. license.dat).

Stop and Restart the License Server

5. launch LMTOOLS using lmtools.exe, available at: c:\Program
Files\MSC.Software\MSC Licensing\Lithium\
The LMTOOLS dialog appears.

a. Click on Service/License file and select Configuration using Services.

b. Select appropriate license server in box below (if you have more than one).
34 MSC Licensing User’s Guide
Using a Renewed/Changed License on an Existing Windows Server

c. Click Start/Stop/Reread tab.

d. Select Stop Server.
The server starts after a minute and the license.dat file path appears at the bottom.

This restarts the FLEXlm server to use the new file.

CHAPTER 2 35
General Information - MSC Licensing

Uninstalling FLEXlm
To uninstall FLEXlm on Windows, follow either one of the following procedures.
 Execute same MSC Licensing installer (which was used to install it) and then select Remove.
 Go to Control Panel  Programs and Features MSC Licensing Lithium and then click
Uninstall.
 Click one of the option Modify/Repair/Remove.

Reinstalling FLEXlm
If you do not wish to remove the FLEXlm, you can instead reinstall the FLEXlm server.
In order to override the previous installation, execute same MSC Licensing installer (which was used to install
it). This program allows the user to Modify/Repair/Remove.

Additional Documentation
To obtain additional information on the FLEXlm license manager, visit the Flexera Software website at
http://www.flexerasoftware.com/
36 MSC Licensing User’s Guide
Additional Documentation
Section 2: Linux Operating System

Section 2

Linux Operating System

Chapter 3: Installing MSC Licensing

3 Installing MSC Licensing


Installation Prerequisites

Operating System Requirements

Installation on Linux

Upgrade/Uninstall the Existing Linux Installation
40 MSC Licensing User’s Guide
Installation Prerequisites

Installation Prerequisites
 Verify that a Java runtime environment is installed on the system. Java can be downloaded from
www.java.com.
 Download the MSC Licensing installation package for your platform from MSC’s Software
Download Center.
 The installer package for Linux platform supports both GUI and terminal-mode installations. MSC
recommends that the installer be run in a GUI environment.
 Run the installer to begin the installation. Use of a root account or sudo is not required. However,
running the installation as root allows the installer to use system resources that require root
privileges.

Operating System Requirements

The following table lists the minimum operating system version required to run the MSC license server and
related tools:

Platform Hardware Supported Operating Systems

linux64 x64 RHEL 6.7, 7.1, and 7.3
SUSE ES 11 SP4 and 12 SP1

License Server Specifications

License Server Diagnostics (MSC Nastran Only)

Note: Older versions of MSC Nastran can have problems with AUTHINFO settings greater than 6.
CHAPTER 3 41
Installing MSC Licensing

Installation on Linux
This section demonstrates the procedure to install the MSC License Server on your Linux system.
The installation video demonstrates the licensing installation procedure with the available license.

 Click to play the video online.

 Click to download the video.

The detailed installation procedure is available as follows:

1. Start the installation procedure by using the command as follows:
[root@vm-tmrhel73 MSC]# ls
license.dat msc_licensing_lithium_linux64.bin
[root@vm-tmrhel73 MSC]# ./msc_licensing_lithium_linux64.bin
The following prompt appears on the screen.

An MSC Licensing Lithium Setup window appears.

2. Review the information and click Next to continue the installation

42 MSC Licensing User’s Guide
Installation on Linux

3. If your system already has the older version of the MSC Licensing Server then it will show the
following message:

4. Click Yes to continue.

The Installer Requirements window appears.

Note: You must have a valid, unexpired MSC license file before the MSC License Server
can be installed.

If you do not have an MSC license file, contact your MSC representative before
continuing with the installation.

This screen provides the HostID that MSC uses to generate the license file. It also provides a list of
HostIDs identified by the ipconfig/all command and labels them in the Installer screen. The preferred
HostID is displayed for you on this screen.
5. Review the installer requirements and click Next to continue.
CHAPTER 3 43
Installing MSC Licensing

The Choose Destination Folders dialog appears.

It is recommended to accept the default folder locations. To change the locations:

6. Click Browse and choose the directories to install the MSC License Server executables and store the
MSC Licensing log files.You must have permission to write to the selected folder.
The default destination for License Manager Executable folder:
/msc/MSC.Software/MSC Licensing
The default destination for License Manager Log File folder:
/msc/MSC.Software/MSC Licensing/LOG
This is appropriate for most installations.
7. Click Next to continue.
A window to select license file appears.

8. Click Browse and select the license file that was provided by MSC Software.
44 MSC Licensing User’s Guide
Installation on Linux

The following error message appears if one or more feature entries in the license file expired.

9. Click OK to continue.
10. Click Next.
The Details of the License File Selected window appears.

11. Click Next to continue the installation.

The License files details are given bellow:

The Automatic Reporting of Usage Data appears.

Note: The data reporting scheme is different for different types of licenses. Contact
customer support for more details.

The MSC Licensing program includes a Usage Reporting Tool that provides valuable usage summary
information to MSC to improve our products. A full description if the usage data sent to MSC is
provided in Chapter 4: FLEXlm/FlexNet and Licensing Management of this User Guide in the Linux section.
No personal data is collected as part of this program. To disagree, uncheck the I agree to the
automatic reporting of usage data option.
12. Click Next to continue the installation
In cases where the customer is required to report usage and deactivates the Automatic Usage
Reporting option, to inform the user of the Manual Reporting Requirement, the following screen
will appear.
46 MSC Licensing User’s Guide
Installation on Linux

13. Read the Information and click Next to continue with the installation.
The License Server Setting options appears.

Specify the License Server Setting as follows:

a. Specify an alternate lmgrd port number (default value is 27500 and it has a limit from 1-64000).
b. Specify an alternate MSC daemon port number (the default value is blank; any number from 1
to 64000 is acceptable).
c. Specify an alternate hostname (For example, fully qualified hostname or IP address).
d. Optional: Browse and select the option file path.
e. Specify the privilege level for license manager access.
f. The license manager will start automatically. Uncheck this box to install the license manager
without the automatic starting.
14. Specify the License Server Setting and click Next to continue the installation.
CHAPTER 3 47
Installing MSC Licensing

The Start Copying Files window appears.

15. Review the installation settings and click Next to complete the installation.
An MSC Licensing Installation Program prompt appears.

The installer creates a sample script that can be used to start the license server after a system reboot.
This script and a README file with important details are written to a directory named
startup_script under the installation directory you selected.
16. Click OK
This finishes the installation of MSC License Server.
48 MSC Licensing User’s Guide
Upgrade/Uninstall the Existing Linux Installation

17. Click Finish to complete the installation.

Terminal/Console Mode
If you do not have access to a GUI environment, you can run the installer in a standard terminal window by
adding the arguments –-mode console to the installer command line.
Console mode is similar to GUI mode, with these important differences:
 In console mode, file and directory browsing is not available. You must manually enter these items.
 To select an option from a list, enter the text found between the brackets for that option.

Upgrade/Uninstall the Existing Linux Installation

This allows the user to Upgrade/Uninstall the current installation.
1. Execute the file msc_licensing_lithium_linux64.bin
2. Select Yes and repeat the process same as installation until the following screen appears.
CHAPTER 3 49
Installing MSC Licensing

3. Click one of the option as shown below and click Next to continue.
4. Repeat the procedure same as installation.
50 MSC Licensing User’s Guide
Upgrade/Uninstall the Existing Linux Installation
Chapter 4: FLEXlm/FlexNet and Licensing Management

4 FLEXlm/FlexNet and
Licensing Management

Introduction to FLEXlm/FlexNet

License Request Process

Manual Configuration of License Server

Getting Started Checklist

Determining Hostid of License Server

Testing Your TCP/IP Connection

Internet Domain Name Server (DNS)

Manual Installation of MSC License Server Using a New LINUX Server

Using a Renewed/Changed License on an Existing LINUX Server
 Restarting MSC Licensing Server on Linux

Uninstalling FLEXlm

Additional Documentation
52 MSC Licensing User’s Guide
Introduction to FLEXlm/FlexNet

Types of Licenses
MSC Software provides you with two license options:
 Concurrent license
 Node-locked license

Concurrent License
A concurrent license limits the maximum number of simultaneous users of a given set of license features
within a given site. A token based (eg. MasterKey Plus and MSC One) license is essentially the same, but
allows access to all included license features, which is limited only by a maximum token count that can be
used at any one time. Both of these licenses are referred to as floating. For details on licensing options, contact
your MSC Software sales representative.
Typically, an MSC License Server (a separate program from the product installer) is installed on a network
server to administer the licenses. The program files are then either loaded on individual computers or on the
network server.

Caution: Do NOT reset the system date after the installation. This can invalidate the license. Re-
validation can be a difficult and cumbersome process.

FLEXlm Components
The four main components of FLEXlm are:
CHAPTER 4 53
General Information - MSC Licensing

 License File (the product license file is called license.dat).

 Application Program (<product>).
 License Server (MSC).
 Vendor Daemon (MSC).

License File
Licensing data is stored in a text file called the license file. The name of the license file is license.dat. The
license file is created by the MSC Software licensing staff and sent via email to the system administrator. It
contains information about the server nodes and vendor daemons, and one line of data (called a FEATURE
line) for each licensed feature. A feature line contains an encryption code based on the data in that line, the
hostids (“host-id”, or a unique identifier for a computer) specified in the server lines,
and other vendor-specific data.
Multiple License Servers: Set the MSC_LICENSE_FILE variable to reference multiple servers using a
separator character between file names. On Linux this character is a colon (“:”).The order of the license
servers in the MSC_LICENSE_FILE variable is the order that license servers will be checked for a license
request.

Note: The FLEXlm version of the MSC License Server must be greater than or equal to the
FLEXlm version linked into the application programs.

License Manager Daemon

Vendor Daemon
In FLEXlm, licenses are handled by running processes. Vendor daemon is the process, for each vendor that
has a FLEXlm-licensed product on the network. The MSC Software vendor daemon is called MSC. The MSC
daemon keeps track of how many licenses are checked out and who has them. Note that the MSC daemon
serves many other MSC Software products, including MSC Nastran, Patran, and Adams, among others. All
users would lose their licenses, if the MSC daemon terminates for any reason. Users regain their license when
the daemon restarts.
Client programs communicate with the vendor daemon through TCP/IP sockets. This enables client
programs and daemon processes to be on separate nodes in a network. Any process can run on any machine
type or operating system, allowing a heterogeneous network. The traffic between the client and the daemon
is machine independent.

Determining Hostid of License Server

You must set up your license server node or nodes, before running any FLEXlm-licensed program using
floating licenses. You must select what node or nodes to run your license servers on and provide the hostid
of those machines for installation.
To obtain a license file from MSC, you need to determine the hostid of the machine that will function as
your license server.
1. Execute the lmhostid command from the command:
<flexlm install folder> ./lmutil lmhostid
2. This will list the possible 'hostid's' of the machine.
3. Choose the Ethernet adapter local area connection hostid. Wireless is not preferred.
(Using command ifconfig you could check the adapter type)
After sending the hostid of your server machines to MSC Software support, the support staff will
send you a license file that enables the application software.
4. Once you receive a license file, you must install it on your system and start up the license server.

License Request Process

5. The vendor daemon checks to see if any licenses are available and sends a grant or denial back to the
client.
6. The license module in the client returns to its caller with the grant or denial, and the application takes
the appropriate action.

Manual Configuration of License Server

You can configure most FLEXlm parameters by setting:
 The location of the license file.
 The location of all executable files.
 The location of all log files.
 The TCP/IP port number of clients looking for the license manager.
In addition, you can reserve licenses for specific users, nodes, or groups and control other license-related
options.

Getting Started Checklist

Testing Your TCP/IP Connection

The concurrent license management require that you are able to establish a TCP/IP network connection
between your computer and the License Server.
1. Find the hostname of the License Server.
2. To determine the appropriate hostname, examine the existing concurrent license file and look for
the SERVER command line.
The first argument is the hostname.
3. You can test if your computer can communicate with the license server by entering the command
ping hostname
If you get a return reply, then you have a TCP/IP connection established.
56 MSC Licensing User’s Guide
Internet Domain Name Server (DNS)

Internet Domain Name Server (DNS)

Manual Installation of MSC License Server Using a New

LINUX Server

Obtain a License File for Your Server

Obtain a license file as follows:
1. Use the command
# /MSC.Software/MSC Licensing/Lithium/lmutil lmhostid
2. Send the hostid to your MSC Software Corporation sales representative to obtain your permanent
license.
Flexlm utilities are available at:
https://mscsoftware.subscribenet.com/control/mnsc/product?child_plneID=593623

Edit/Update Your License

The License Server must be updated with the new license before it is used.
3. Verify that the license has a valid path for the DAEMON line, and a valid SERVER hostname in the
license file. The DAEMON line should have a path to the installed MSC vendor daemon, normally found
in folder:
/msc/MSC.Software/MSC Licensing/Lithium
The DAEMON line should look similar to the following:
DAEMON MSC /msc/MSC.Software/MSC Licensing/Lithium/MSC
4. If the path to the daemon is incorrect, edit the license file and correct the path. The SERVER line
should look similar to:
SERVER <hostname> <value> <port>
For example:
SERVER server1 123465 27500

Place the License File on the Server

The msc setup utility automatically installs the license.dat file if you provide it during installation.
5. The license file may be located anywhere on your license server. MSC Software recommends locating
it in /MSC.Software/MSC Licensing/Lithium/license.dat.
CHAPTER 4 57
General Information - MSC Licensing

6. Clients with network-licensed MSC software installations are encouraged to employ the most recent
versions of the FLEXlm and MSC licensing daemons (lmgrd,lmutil,msc). These binaries
maintain downward compatibility, and regular upgrades are recommended, regardless of whether or
not the current software application level requires the upgrade. Updates are available at:
https://mscsoftware.subscribenet.com/control/mnsc/product?child_plneID=593623

Check Paths and Server Names in the license.dat File

7. Check that the license.dat file for your installation contains the correct server and port settings.
An example of a license file supplied by MSC is as follows:
SERVER this_host 12345678 27500
DAEMON MSC /your_path/msc
#
# MSC License Reference ID: 59TG
#
#-#
#-# This license file is restricted to use by clients in the same location as the
license server
#-#
#
# MSC Nastran
#
FEATURE NASTRAN MSC 2017.0628 28-jun-2017 1 ED97453C93A6 \
VENDOR_STRING=PID:10652 ISSUED=29-jun-2016 ck=141 \
SN=1203862-a6382ca550b364f60e0f-2c2f
FEATURE NA_Thermal MSC 2017.0628 28-jun-2017 1 BB8A3B089AF1 \
VENDOR_STRING=PID:3002,3003 ISSUED=29-jun-2016 ck=189 \
SN=1138845-f6205ec4fbe7329339be-3b30
FEATURE NA_DMAP MSC 2017.0628 28-jun-2017 1 FD652933FAC7 \
ISSUED=29-jun-2016 ck=139 SN=1164504-093d6d6ae7ef8dd13594-a859
FEATURE NA_Dynamics MSC 2017.0628 28-jun-2017 1 CC25C4107563 \
ISSUED=29-jun-2016 ck=101 SN=915407-253bbea2e116836e48d0-da03
FEATURE NA_Nonlinear MSC 2017.0628 28-jun-2017 1 E16DB1DC662A \
VENDOR_STRING=PID:3003,10464 ISSUED=29-jun-2016 ck=149 \
SN=1110362-157249f70365b7a14431-7704
8. SERVER must be in all caps followed by:
a. the hostname
b. the lmhostid
c. the port the daemon will run on
9. The hostname can be determined by typing hostname on the machine you wish to be your license
server. Replace UNKNOWN on the SERVER line with this hostname.
10. Verify the lmhostid listed on the SERVER line by running 'lmutil lmhostid' command. If the
lmhostid is not correct, new codes must be generated. For more assistance, contact your local MSC
sales office.
11. The default port is defaulted to 27500 but can be any free port. If you do not know what ports are
free, use the default.
12. DAEMON must be in all caps, followed by MSC which also must be in all caps. This is followed by the
path to the msc vendor daemon executable.
13. The executable is found in the ‘/MSC.Software/MSC Licensing/Lithium/’directory.
58 MSC Licensing User’s Guide
Using a Renewed/Changed License on an Existing LINUX Server

Here is an example of the changes needed to be made for the above file. In the example, the server
name is ind-Ashu and the default installation directory was used.
SERVER ind-Ashu 12345678 27500
DAEMON MSC C:\MSC.Software\MSC Licensing\Lithium\msc.exe
#
# MSC License Reference ID: 59TG
#
#-#
#-# This license file is restricted to use by clients in the same location as the
license server
#-#
#
# MSC Nastran
#
FEATURE NASTRAN MSC 2017.0628 28-jun-2017 1 ED97453C93A6 \
VENDOR_STRING=PID:10652 ISSUED=29-jun-2016 ck=141 \
SN=1203862-a6382ca550b364f60e0f-2c2f
FEATURE NA_Thermal MSC 2017.0628 28-jun-2017 1 BB8A3B089AF1 \
VENDOR_STRING=PID:3002,3003 ISSUED=29-jun-2016 ck=189 \
SN=1138845-f6205ec4fbe7329339be-3b30
FEATURE NA_DMAP MSC 2017.0628 28-jun-2017 1 FD652933FAC7 \
ISSUED=29-jun-2016 ck=139 SN=1164504-093d6d6ae7ef8dd13594-a859
FEATURE NA_Dynamics MSC 2017.0628 28-jun-2017 1 CC25C4107563 \
ISSUED=29-jun-2016 ck=101 SN=915407-253bbea2e116836e48d0-da03
FEATURE NA_Nonlinear MSC 2017.0628 28-jun-2017 1 E16DB1DC662A \
VENDOR_STRING=PID:3003,10464 ISSUED=29-jun-2016 ck=149 \
SN=1110362-157249f70365b7a14431-7704

Start the Manager Daemons

14. On the license server, start the license manager daemon with the FLEXlm script.
15. Do not execute this as root since it may create a security risk on your network.
% /MSC.Software/MSC Licensing/Lithium/lmgrd -c license.dat -l lmgrd.log
16. If the license.dat file is located in /MSC.Software/MSC Licensing/Lithium, this script
will start the following daemons:
• lmgrd: server daemon
• msc: vendor daemon

Set Up Clients to Access the Floating License

17. For setting the file location on clients, set the MSC_LICENSE_FILE environment variable to:
<port>@<hostname>

Using a Renewed/Changed License on an Existing

LINUX Server
Follow these steps if you have an existing installation and have received new codes (as a renewal, change, etc.).
CHAPTER 4 59
General Information - MSC Licensing

Edit the New License File

1. Do not overwrite the existing license file.
2. Place the new codes as a license file in the same directory as the existing license.dat file.
3. Name it license_new.dat.
4. Change the SERVER and DAEMON lines in the new license file to include the same port number, server
name, and paths as the existing file. For example:
SERVER server1 123465 27500
DAEMON MSC “/msc/MSC.Software/MSC Licensing/Lithium/msc.exe”

Replace License File

5. Rename the existing license.dat file to license_old.dat, and rename the new file to the
current license file name (i.e. license.dat):
# mv license.dat license_old.dat
# mv license_new.dat license.dat

Restart Daemon
Restart the daemons as follows:
# msc/MSC.Software/MSC Licensing/Lithium/lmutil lmdown -c <path>/license.dat
# MSC.Software/MSC Licensing/Lithium/lmgrd -c <path>/license.dat

Restarting MSC Licensing Server on Linux

Follow these steps to restart the MSC Licensing Server on Linux:

Stop the FLEXlm Service

1. Use the command ./lmutil lmdown -q -c cu12f03.dat
The following will appear on your terminal screen:
[user@machine:Lithium]./lmutil lmdown -q -c cu12f03.dat
lmutil - Copyright (c) 1989-2015 Flexera Software LLC. All Rights
Reserved.
Port@Host Vendors
1) 1700@cu12f03 MSC
1 FlexNet License Server shut down

Restart the FLEXlm Service with MSCLIC_INI file

2. Use the commands:
60 MSC Licensing User’s Guide
Uninstalling FLEXlm

a. export MSCLIC_INI=msclic.ini
b. ./lmgrd -c license.dat -l lmgrd.log

Uninstalling FLEXlm
To uninstall FLEXlm on Linux, follow the procedure as follows.

Uninstall the License Server

To uninstall the server run this command:
/MSC.Software/MSC Licensing/Lithium/uninstall

Remove the Server

To manually uninstall the FLEXlm server remove the following files:
 /MSC.Software/MSC Licensing/Lithium/uninstall
 /MSC.Software/MSC Licensing/Lithium/MSC
 /MSC.Software/MSC Licensing/Lithium/lmgrd
You will also need to remove the entry for the msc deamon from /etc/inittab.
The FLEXlm installation is now completely removed.

Reinstalling FLEXlm
You can reinstall the FLEXlm server, if you do not want to remove the FLEXlm files manually. In order to
override the previous installation you must install FLEXlm in the same location with the same options as your
previous installation. This program allows the user to Modify/Repair/Remove.

Section 3

General
Chapter 5: Usage Reporting Tool

5 Usage Reporting Tool


Usage Reporting Overview

Usage Reporting Details

Manual Usage Reporting
Usage Reporting Overview
The MSC Licensing installer includes a Usage Reporting Tool.
Where applicable, the Usage Reporting Tool logs information about each check-in in a Daily Detailed
Usage (DDU) log file on the license server. Each day after midnight (local time), the DDU log file is
converted to a Daily Summary Usage (DSU) file. If the automatic reporting option is enabled, the DSU file
is automatically transmitted via the internet to an MSC-designated data repository. If you choose the manual
reporting option, you should follow the instructions in this guide to manually upload the DSU files to the
MSC-designated data repository.
The DDU and DSU files are ASCII text files that you can view. The format of the files and descriptions of
the contents are described in more detail below.
For customers using the Burst token pools for on-demand capacity, additional data will be included in the
usage reporting to record the number of burst tokens used for the reporting period. See the BURST POOL
Reporting section for more details.

Usage Reporting Details

Daily Detailed Usage (DDU) Log File

During the course of the day, all license feature check-ins are recorded in sequence in the Daily Detailed
Usage (DDU) log file. This file is located in the “MSC Licensing/Lithium/LOG” directory. The
standard file name of the Daily Detailed Usage log file is:
“mscusage_YYYY-MM-DD.ddu”
Below is a sample of the format for the DDU file.
D,171129,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,H
H,YYMMDD,HHMMSS,DURATION,MSCID,CID,SEQ,USERH,FEAT,NLIC,LICINUSE,BASEMAX,LICM
AX,CHWM,HWM,BCHWM,BHWM,CK1,CK2,VERS
T,171129,112022,I
Q,171129,112404,,0026b98999609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,0,3520808a,MSC
ONE:FFT_Actran_Acoustics,28,78,1,80,8,78,1,28,df997ff8d4f7b30ca3af939c07ac49
9a,,H
Q,171129,112404,,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,1,3520808a,MSCONE
:FFT_Actran_Acoustics,28,78,1,80,8,78,1,28,df997ff8d4f7b30ca3af939c07ac499a,
,H
U,171129,112507,64,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,8,3520808a,FFT_
Actran_Python,1,1,0,30,1,1,0,0,410df0bc,d6d98ef6,H
U,171129,112507,65,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,9,3520808a,MSCO
NE:FFT_Actran_VA,14,78,1,80:30,8,78,4,56,9f3e10fc,b7e9266,H
U,171129,112515,64,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,10,3520808a,FFT
_Actran_Sequential,1,1,0,30,1,1,0,0,efff4751,68a6621a,H
U,171129,112515,68,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,11,3520808a,FFT
_Actran_PreProcess,1,1,0,30,1,1,0,0,e6a8bcc5,2c848e69,H
U,171129,112515,72,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,12,3520808a,MSC
ONE:FFT_Actran_VI,7,64,1,80:30,8,78,1,7,12f9f954,27fd5772,H
CHAPTER 5 65
Usage Reporting Tool

U,171129,112515,73,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,13,3520808a,MSC
ONE:FFT_Actran_VA,14,57,1,80:30,8,78,4,56,c8bcf0ee,85e84001,H
P,171129,112637,,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,2,3520808a,MSCONE
:FFT_Actran_Acoustics,28,43,1,80,8,78,1,28,df997ff8d4f7b30ca3af939c07ac499a,
,H
U,171129,112637,155,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,14,3520808a,MS
CONE:FFT_Actran_VA,14,43,1,80:30,8,78,4,56,997d7014,a7ab7335,H
P,171129,112807,,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,3,3520808a,MSCONE
:FFT_Actran_Acoustics,28,29,1,80,8,78,1,28,df997ff8d4f7b30ca3af939c07ac499a,
,H
U,171129,112807,245,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,15,3520808a,MS
CONE:FFT_Actran_VA,14,29,1,80:30,8,78,4,56,bfebe11b,920eb039,H
66 MSC Licensing User’s Guide
Usage Reporting Details

The format of the DDU file, excluding the header, is described in the following table:

Table 5-1 Daily Detailed Usage (DDU) File Format

Daily Detailed Usage (DDU) File Format

First Field = Entry Tag
Field D = Date T = Time G = Group R= U = Usage Q = Queue P = Processed
Number Stamp Stamp Record Reread Record Record Queue Record
Record
2 Date Date Group Date Date Date Date
Feature
3 Host ID Time Max Token Time Time Time Time
4 OS ID Type Base Token Checkout Checkout Checkout
Duration Duration* Duration*
5 Data Data Host ID Host ID Host ID
Version ID Version ID
6 OS ID OS ID OS ID
7 Sequence Sequence Sequence
Number Number* Number*
8 User Hash User Hash User Hash
9 Group:Feature Group:Feature Group:Feature
10 Feature Token Feature Token Feature Token
Draw Draw Draw
11 Tokens in Use Tokens in Use Tokens in Use
12 Token Tag Token Tag Token Tag
13 Token Pool Size Token Pool Size Token Pool Size
[:Base Pool Size]
14 Token Pool Token Pool Token Pool
CHWM CHWM CHWM
15 Token Pool Token Pool Token Pool
HWM HWM HWM
16 Feature CHWM Feature CHWM Feature CHWM
17 Feature HWM Feature HWM Feature HWM
18 Check Sum 1 Check Sum 1* Check Sum 1*
19 Check Sum 2 Check Sum 2* Check Sum 2*
20 Data Version ID Data Version ID Data Version ID
CHAPTER 5 67
Usage Reporting Tool

The first field of each line will commonly be either H (Header Entry), D (Date Stamp), T (Time Stamp), U
(Usage Record), Q (Queue Record), P (Processed Queue Record), G (GROUP features) and R (REREAD
event).
The fields for the Date Stamp entry are:

Date = Date using the YYMMDD format.

Host ID = Host ID of the license server.
OS ID = Internal MSC ID to assign usage to specific agreement.
Data Version ID = Version of Usage Reporting Tool.

The fields for the Time Stamp entry are:

Date = Date using the YYMMDD format.

Time = Time using the HHMMSS format. The hours use 24-Hr format.
Type = Initial Time Stamp (I=Initial) or Periodic Time Stamp (P=Periodic).

The field entries for the Usage Record, Queue Record, and Processed Queue Record are:

Date = Date using the YYMMDD format.

Time = Time using the HHMMSS format. The hours use 24-Hr format.
Checkout Duration = Duration of the feature checkout in seconds.
Host ID = Host ID of the license server.
OS ID = Internal MSC ID to assign usage to specific agreement.
Sequence Number = Sequence number to the usage record in the daily Log.
User Hash = One-way hash of the user name. No personally identifiable information is
stored.
Group:Feature = The name of the token pool (MSCONE) and feature that is checked in.
Feature Token Draw = The token draw of the feature.
Tokens in Use = The number of tokens checked out before the feature was checked in.
Token Tag = Tag to signify whether a feature draws tokens (1) or is a standalone seat (0).
Token Pool Size [:Base = Number of total MSC One tokens on the license server [: The Base Pool
Pool Size] Size]
Token Pool CHWM = Maximum number of all features checked out of the token pool.
Token Pool HWM = Maximum number of tokens checked out of the token pool.
Feature CHWM = Maximum number of the specific feature checked out of the token pool.
Feature HWM = Maximum number of tokens checked out of the token pool for the feature.
68 MSC Licensing User’s Guide
Usage Reporting Details

Check Sum 1 = Check Sum # 1 to test for file tampering.

Check Sum 2 = Check Sum # 2 to test for file tampering.
Data Version ID = Version of Usage Reporting Tool.

Note: For P and Q records that the duration field is empty, the sequence number is incremented
differently than Q records, check field sum 1 field uses longer format, and check field sum
2 field is empty.

 When the DDU file is processed by the summarizer routine, the filename extension will be changed
to DDP. The P stands for processed.
 The fields for the G line entry are:
G,gfeature,max_users,base,dataver
where

Fields Description
gfeature = Group feature [ MSC One / CAMPUS }
max_users = Total token pool size
base = Base token size
dataver = Version of Usage Reporting Tool

Note: 1. Burst and/or growth token values are not included on G lines;
2. If a license file contains more than one GROUP target feature, such as both MSCONE
and CAMPUS, then one G line is written for each GROUP target. (This can occur if
an end-user manually combines an MSC One license file with a MasterKey+ license
file; this combination is not officially supported by MSC Software, but there's no
technical way to prevent it from occurring.)
3. GROUP targets that are referenced less than two times do not result in G lines. Seat-
based licenses that include Nastran and/or Adams features contain MD-based features
that use a GROUP entry targeting the non-MD feature; this is done so that use of
either the MD or non-MD feature pulls from the same seat pool. (For example, the
NASTRAN feature has a companion 1-seat MD_NASTRAN feature definition that uses a
GROUP:NASTRAN,1 entry; when MD_NASTRAN is checked out, it pulls from the
NASTRAN feature's license pool.
4. The summarizer uses G lines only for NODATA situations. G lines in the DDU are used
to construct the U NODATA lines for each GROUP when a NODATA reporting period
is processed.
5. G lines are written only for GROUPs that are referenced by two or more FEATUREs
which include IDENT lines.
CHAPTER 5 69
Usage Reporting Tool

 R lines indicate the time and date of a REREAD event

 The fields for the R line entry are:
R,ts,ur
where

Fields Description
ts YYMMDD - see the section "Fields common to multiple entries” for complete details
ur HHMMSS - see the section "Fields common to multiple entries" for complete details.

Daily Summary Usage (DSU) Log File

At the end of each day, the Daily Detailed Usage Log File is summarized with the results written to the Daily
Summary Usage (DSU) log file. The DSU log file is also located in the “MSC Licensing/ Lithium/
LOG” directory. The standard file name of the Daily Summary Usage log is:
“mscusage_YYYY-MM-DD.dsu”
Below is a sample of the format for the DSU file.
H,yymmdd,mscid,osid,feature,count,smins,uniqusers,usermaxcnt,usermaxsmin,lic
cnt,glic,hwm,chwm,bhwm,bchwm,blv,ck1,ck2,vers
S,171129,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,FFT_Actran_Python,2,3,1,2
,3,0,30,1,1,0,0,1,4f59c4cf,4e890a70,H
S,171129,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,MSCONE:FFT_Actran_Acousti
cs,3,216,1,11,350,1,80,78,8,28,1,28,605e6bd1,ffbcd54,H
S,171129,0026b98609df,2CCOD_1UI95_24ENF8WV_1I6ARTD,MSCONE:Overall,12,407,1,1
2,407,1,80,78,8,30,50,48,c8372ae2,6450b022,H
70 MSC Licensing User’s Guide
Usage Reporting Details

The format of the DSU file, excluding the header, is described in the following table:

Daily Summary Usage (DSU) File Format

First Field = Entry Tag
Field Number S = Usage Summary T = Time Stamp
2 Date (YYMMDD) Date
3 Host ID Time
4 OS ID Check Sum
5 Group:Feature
6 Count
7 Token-Minutes
8 Unique Users
9 MaxUser Count
10 MaxUser Minutes
11 Token Tag
12 Token Pool Size
13 Token Pool HWM
14 Token Pool CHWM
15 Feature HWM
16 Feature CHWM
17 Feature Token Draw
18 Check Sum 1
19 Check Sum 2
20 Data version ID

The first field of each line will be either an H (Header Entry), S (Usage Summary), or T (Time Stamp).
CHAPTER 5 71
Usage Reporting Tool

The fields for the Usage Summary entry are:

Date = Date using the YYMMDD format.

Host ID = Host ID of the license server.
OS ID = Internal MSC ID to assign usage to specific agreement.
Group:Feature = The name of the token pool (MSCONE) and feature that is checked in.
Count = The total number of features check-ins during the reporting period.
Token Minutes = The total token-minutes the feature was used during the reporting period.
Unique Users = The number of unique users of the feature.
MaxUser Count = Number of Checkouts for User with Maximum Checkouts.
MaxUser Minutes = Number of Token-minutes for User with Maximum Token-Minutes.
Token Tag = Tag to signify whether a feature draws tokens (1) or standalone seats (0).
Token Pool Size = Number of total MSC One tokens on the license server.
Token Pool HWM = Maximum number of tokens checked out of the token pool.
Token Pool CHWM = Maximum number of all features checked out of the token pool.
Feature HWM = Maximum number of tokens checked out of the token pool for the feature.
Feature CHWM = Maximum number of the specific feature checked out of the token pool.
Feature Token Draw = The token draw of the feature.
Check Sum 1 = Check Sum # 1 to test for file tampering.
Check Sum 2 = Check Sum # 2 to test for file tampering.
Data version ID = Version of Usage Reporting Tools.

The fields for the Time Stamp entry are:

Date = Date using the YYMMDD format.

Time = Time using the HHMMSS format. The hours use 24-Hr format.
Check Sum = Check Sum to test for file tampering.

When the DSU file is processed by the uploading routine, the filename extension will be changed to DSP.
The P stands for processed.

Automatic Upload
If the Usage Reporting Tool is enabled for automatic usage reporting, the DSU log file will be transmitted
daily to the MSC-designated data repository. Standard HTTPS web encryption technology is used for the
transmission of the data.
72 MSC Licensing User’s Guide
Usage Reporting Details

The DDP and DSP files will be retained on your license server after the transmission and may be used by the
customer to understand usage.
For manual uploading, please see the Manual Usage Reporting section of this document.

Off Network Scenarios

If the license server is temporarily off-line during the time that the transmission is scheduled to happen, the
files will be saved until the license server is back on-line. The summary files that have not been transmitted
will be automatically processed at that time.

NODATA Reporting
In some cases, for a given reporting period such as on a weekend or holiday period, there will be no usage
data to report. In such cases, the license server will still report, but the usage will be a ‘NODATA’ report. An
example of the “NODATA” report is shown below.
H,yymmdd,mscid,osid,feature,count,smins,uniqusers,usermaxcnt,usermaxs
min,liccnt,glic,hwm,chwm,bhwm,bchwm,blv,ck1,ck2,vers
S,190528,a44cc86fa245,38N55_2TIGX_1S19BJJF45_17OK433-641N-
MAN,MSCONE:NODATA,0,0,0,0,0,0,80,0,0,30,50,0,0,0,He
T,190528,200030,d41d8cd98f00b204e9800998ecf8427e
It is important to still report during a period of no usage so that the non-usage period will not be mistaken
for failure to report.

GLIC Value in NODATA

To support this task, a new data line is added to the DDU file, to provide details on the size of GROUP target
pools.
When a license file contains a GROUP target feature (such as MSCONE for MSC One licenses, or
CAMPUS for MasterKey+ licenses), additional G line is written in the DDU file when the vendor daemon
is initialized. For more information please refer G line section - Daily Detailed Usage (DDU) File Format.

BURST POOL Reporting

MSC Software supports a special licensing method known as BURST POOL licensing. With BURST POOL
licensing, your license contains details about the number of BASE tokens and the number of BURST POOL
tokens. When you use more than the BASE number of tokens, the excess usage is reported to MSC as BURST
POOL usage.
Customers using MSC Software’s BURST POOL licensing will have some minor differences in certain usage
data files, specific to the BURST POOL. The following sections describe these differences.
CHAPTER 5 73
Usage Reporting Tool

DDU Files - BURST POOL

For BURST POOL users, the LICMAX field in the DDU file contains a sub-field with the BASE token
value, shown in bold:
U,170905,200402,121,00505696c16d,K_K_4EIHX8BX_T4V3B2,4,b886258,MSCONE:FFT_Ac
tran_Acoustics,28,84,1,100:50,3,84,3,84,ed58ccc9,3e9f881f,H
where the 100 represents the total size of the combined pool (BASE + BURST) and the 50 represents the
BASE pool amount. This change applies to the U, P, and Q entries in the DDU file.

DSU Files - BURST POOL

For BURST POOL users, the MSCONE:Overall line contains details about the BURST POOL and its
usage for the reporting period:
S,171019,00505696c16d,K_K_4EIHX8BX_T4V3B2,MSCONE:Overall,1,27,0,1,27,1,460,1
3,1,10,450,3,75bf5b5,182388ac,H
The Token Pool Size field (shown as 460 in the example) contains the combined pool size (BASE +
BURST). The Token Pool HWM field (shows as 13 in the example, just after the 460) contains the number
of BURST POOL tokens used during the reporting period. The Feature HWM field (shown as 10 in the
example) contains the size of the BASE POOL. The Feature CHWM field (shown as 450 in the example)
contains the size of the BURST POOL.

Triad Servers
The Usage Reporting Tool supports the triad server environment. In a triad server, all three servers will report
the usage. In some cases, there will be no usage to report from one or more servers in the triad. For triad
servers that do not have any usage data, the NODATA report discussed in the previous section will be sent.
Note that in the GUI mode of the installer, the SERVER lines in the license.dat file will be incorrect when
a TRIAD license file is provided. The host names for all three servers will be set to the fqdn of the installation
system. These must be manually corrected for the case of a TRIAD license file. For Linux, the console mode
will set the three license SERVER lines correctly.

Flexera Debug Log Files

While the Usage Reporting Tool creates additional log files (e.g., the DDU and DSU files), the traditional
Flexera debug log files are still available. The Flexera debug log files are not used by the Usage Reporting Tool.

License Server Product Updates

Occasionally, MSC will release updates to the MSC Licensing software. You may be notified of these updates
through the standard e-mail notifications from the MSC Solutions Download Center. The MSC Licensing
software does not use automatic product updates. All product updates will need to be downloaded and
installed manually by the customer when made available by MSC.
74 MSC Licensing User’s Guide
Manual Usage Reporting

Manual Usage Reporting

For customers whose internal or external security requirements prevent the license server system from
accessing internet sites directly, an alternate method is available. Below are the instructions for performing
manual usage reporting on the same machine as the license server or from a secondary machine.

Windows
1. To run the Uploader, enter these commands:
cd C:\MSC.Software\MSC Licensing\Lithium
uploader -p %LOGDIR%
where %LOGDIR% is the folder that contains the DSU files to be uploaded.

Note: Write permissions to the %LOGDIR% folder are required. The mscusage.mpl file contains the
Uploader execution status.

Linux
1. To run the Uploader, enter these commands:
cd /msc/MSC.Software/MSC Licensing/Lithium
./uploader –p %LOGDIR%
where,
%LOGDIR% is the directory that contains the DSU files to be uploaded.

Note: Write permissions to the %LOGDIR% directory are required.

Platform Notes
SuSE Linux
On SuSE Linux systems, the Uploader works in IPv4 and dual-stack IPv4/IPv6 network environments.
However, the Uploader cannot be used on systems running in an IPv6-only network configuration.

MSC Licensing Helium Doc User PDF
No ratings yet
MSC Licensing Helium Doc User PDF
58 pages
Autodesk Education Suites 2012 Installation Guide
No ratings yet
Autodesk Education Suites 2012 Installation Guide
70 pages
MGC Licen
No ratings yet
MGC Licen
95 pages
SLM 71 Sys
No ratings yet
SLM 71 Sys
136 pages
LicensingEndUserGuide PDF
No ratings yet
LicensingEndUserGuide PDF
158 pages
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
No ratings yet
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
86 pages
Autodesk Licensing Guide: Autocad 2013
No ratings yet
Autodesk Licensing Guide: Autocad 2013
68 pages
Adsk Lic
No ratings yet
Adsk Lic
60 pages
Ansoft Maxwell Guide
100% (1)
Ansoft Maxwell Guide
70 pages
Autocad 2012 Licensing Guide
No ratings yet
Autocad 2012 Licensing Guide
68 pages
BMC Remedy Action Request System 7.5.00 Configuration Guide
No ratings yet
BMC Remedy Action Request System 7.5.00 Configuration Guide
414 pages
MGC Licen
No ratings yet
MGC Licen
104 pages
Marc Install Instruct
No ratings yet
Marc Install Instruct
104 pages
User Guide
No ratings yet
User Guide
97 pages
FLT 7.0v2 UserGuide
No ratings yet
FLT 7.0v2 UserGuide
97 pages
MSC Nastran 2023.1 Installation and Operations Guide
No ratings yet
MSC Nastran 2023.1 Installation and Operations Guide
240 pages
2014sflm Users1
No ratings yet
2014sflm Users1
89 pages
Modelsim Se Install
No ratings yet
Modelsim Se Install
30 pages
Backup Exec 12.5 Pricing and Licencing
No ratings yet
Backup Exec 12.5 Pricing and Licencing
32 pages
Manage SW Ie3d
No ratings yet
Manage SW Ie3d
89 pages
OpenScape Xpressions V7, Server Installation, Installation Guide, Issue 24
No ratings yet
OpenScape Xpressions V7, Server Installation, Installation Guide, Issue 24
572 pages
Patran 2021.3 Doc Install
No ratings yet
Patran 2021.3 Doc Install
148 pages
02sflm6 Install Users
No ratings yet
02sflm6 Install Users
42 pages
OpenScape Xpressions V7, Server Installation, Installation Guide
67% (3)
OpenScape Xpressions V7, Server Installation, Installation Guide
610 pages
FNP PR-LF
No ratings yet
FNP PR-LF
224 pages
FNP PR-LF
No ratings yet
FNP PR-LF
232 pages
SAP SySAM Users Guide en
No ratings yet
SAP SySAM Users Guide en
72 pages
BMC Blade Logic Client Automation Application Packager User Guide
100% (1)
BMC Blade Logic Client Automation Application Packager User Guide
454 pages
Libero Installation Licensing Userguide
No ratings yet
Libero Installation Licensing Userguide
44 pages
Flexlm
No ratings yet
Flexlm
81 pages
Flexman Installation and Configuration Guide
No ratings yet
Flexman Installation and Configuration Guide
38 pages
Flexman 5 - 2 Installation and Configuration Guide PDF
No ratings yet
Flexman 5 - 2 Installation and Configuration Guide PDF
38 pages
Xpress Install Guide
No ratings yet
Xpress Install Guide
44 pages
Flexman 4 - 1 Installation and Configuration Guide
No ratings yet
Flexman 4 - 1 Installation and Configuration Guide
32 pages
OICore
No ratings yet
OICore
122 pages
Network Administrator's Guide: Autodesk 3 9 Ds Max
No ratings yet
Network Administrator's Guide: Autodesk 3 9 Ds Max
54 pages
Leica XPro 6.2 Manual
No ratings yet
Leica XPro 6.2 Manual
196 pages
Telelogic Licensing Guide 1.5 PDF
No ratings yet
Telelogic Licensing Guide 1.5 PDF
72 pages
KofaxEquitracClientSetupGuide612 EN SecurityFramework
No ratings yet
KofaxEquitracClientSetupGuide612 EN SecurityFramework
35 pages
Maya Installation Licensing Guide
No ratings yet
Maya Installation Licensing Guide
144 pages
PDF 40
No ratings yet
PDF 40
55 pages
LAM Guide: Linux, Solaris, and Windows
No ratings yet
LAM Guide: Linux, Solaris, and Windows
50 pages
Cadence Allegro and Orcad 17.4-2019 Release Installation Guide For Windows
No ratings yet
Cadence Allegro and Orcad 17.4-2019 Release Installation Guide For Windows
77 pages
DLMUserGuide PDF
No ratings yet
DLMUserGuide PDF
90 pages
Fico Fico Xpress Optimization Xpress Optimization: Installation Guide
No ratings yet
Fico Fico Xpress Optimization Xpress Optimization: Installation Guide
40 pages
AutoCAD 2000 Migration Guide
No ratings yet
AutoCAD 2000 Migration Guide
268 pages
Vitrea Workstation Install Guide
No ratings yet
Vitrea Workstation Install Guide
192 pages
Mx800 Reference Manual v2
No ratings yet
Mx800 Reference Manual v2
74 pages
Autodesk Navisworks Installation Guide
No ratings yet
Autodesk Navisworks Installation Guide
120 pages
Libero Installation Licensing Setup User Guide PDF
No ratings yet
Libero Installation Licensing Setup User Guide PDF
46 pages
RV Administration
No ratings yet
RV Administration
320 pages
Nastran 2020 Doc Install PDF
No ratings yet
Nastran 2020 Doc Install PDF
252 pages
Working With Windows and DOS Systems
100% (1)
Working With Windows and DOS Systems
24 pages
Readme First - Guide
No ratings yet
Readme First - Guide
4 pages
Introduction To Computing ICT TEXTBOOK
No ratings yet
Introduction To Computing ICT TEXTBOOK
345 pages
GPH Editor en v01.13
50% (2)
GPH Editor en v01.13
35 pages
MegaStat FAQ
No ratings yet
MegaStat FAQ
7 pages
Oracle DB Basic Commands
75% (4)
Oracle DB Basic Commands
1 page
Export Tags
No ratings yet
Export Tags
60 pages
Counter-Forensic Tools Analysis and Data Recovery
No ratings yet
Counter-Forensic Tools Analysis and Data Recovery
22 pages
Tankdesigner
No ratings yet
Tankdesigner
94 pages
FANUC Educational Cell Manual
No ratings yet
FANUC Educational Cell Manual
66 pages
Chapter4-Cloud Storage
No ratings yet
Chapter4-Cloud Storage
29 pages
IT Lab Manual for FOSS Beginners
No ratings yet
IT Lab Manual for FOSS Beginners
51 pages
PBE2
No ratings yet
PBE2
420 pages
Rulesules of Conduct For Members 250717
No ratings yet
Rulesules of Conduct For Members 250717
50 pages
Nx510 Steer Ready User Manual
No ratings yet
Nx510 Steer Ready User Manual
89 pages
RXH1300 Series Fast User Manual
No ratings yet
RXH1300 Series Fast User Manual
24 pages
WinAudit Computer Audit
100% (1)
WinAudit Computer Audit
237 pages
RHEL Disk Quota Implementation Guide
No ratings yet
RHEL Disk Quota Implementation Guide
9 pages
AS - Level - Chap1 - Data - Processing
No ratings yet
AS - Level - Chap1 - Data - Processing
25 pages
Win Ultra Star LFM
No ratings yet
Win Ultra Star LFM
86 pages
Data Domain Fundamentals Student Guide
100% (1)
Data Domain Fundamentals Student Guide
70 pages
Microsoft Exchange Load Generator
No ratings yet
Microsoft Exchange Load Generator
101 pages
ECE2544 Digital Systems Lab Manual
No ratings yet
ECE2544 Digital Systems Lab Manual
61 pages
DiskGenius User Guide
100% (1)
DiskGenius User Guide
193 pages
DBA Notes
No ratings yet
DBA Notes
24 pages
Programming Games Java Swing Tutorial
100% (4)
Programming Games Java Swing Tutorial
998 pages
At Grade Junction Design Assignment
No ratings yet
At Grade Junction Design Assignment
8 pages
Itraxr PRX Module: Customer Product Manual Part 1078355-05
No ratings yet
Itraxr PRX Module: Customer Product Manual Part 1078355-05
49 pages
LAB 13 - Data Leak Prevention (DLP) PDF
No ratings yet
LAB 13 - Data Leak Prevention (DLP) PDF
14 pages
CalWIN507 User Manual for Wavetek 9100
100% (1)
CalWIN507 User Manual for Wavetek 9100
13 pages