Skip navigation
All Places > Licensing and Installation > Blog > Authors guy_wettstein

Mentor Graphics applications using floating licenses depend on a license server running a version of FlexNet that is equal to or greater than the version of FlexNet the client application was built with. Also, our vendor daemon (mgcld) requires a FlexNet License Manager daemon (lmgrd) that is equal to or greater than the version of FlexNet our vendor daemon was built on. Failing to follow these requirements in your environment can lead strange behavior and a loss of productivity. Some symptoms may include:

 

  • Error "Vendor daemon is too old."
  • Checkout failures without a specific error message.
  • Failure of the license server to start.
  • Failure to write the report log.
  • Incorrect license counts.

 

What this boils down to is the importance of keeping your license server one step ahead of your applications. You can check the release notes for the Mentor Graphics applications you're running to determine license server version requirements. Furthermore, when updating your license server, you must ensure that you update both the lmgrd and mgcld.

 

 

Download the latest release of Mentor Standard Licensing, including verifying your daemon versions and updating your server:

 

http://supportnet.mentor.com/reference/technotes/public/technote.cfm?id=MG66951

Updating Your Licensing Manager (Server) on Windows (Video)

Setting up license servers, RSCM servers, DMS servers, etc..., they all require you to select an available port. Guessing just leads to frustration but fortunately, determining which ports are available is fairly simple. The netstat command works on both Windows and Linux and will show you which ports are in use and the processes that are using them. For example:

 

On Windows:

 

C:\>netstat -anu|more


Active Connections

 

 

 

  Proto  Local Address          Foreign Address        State           PID

 

  TCP    0.0.0.0:111            0.0.0.0:0              LISTENING       2856

 

  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       856

 

  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4

 

  TCP    0.0.0.0:902            0.0.0.0:0              LISTENING       2968

 

  TCP    0.0.0.0:912            0.0.0.0:0              LISTENING       2968

 

  TCP    0.0.0.0:1158           0.0.0.0:0              LISTENING       17196

 

-- More  --

 

 

More specifically, you can check if a particular port is in use:


 

C:\>netstat -ano | find /i "1718"

 

 

 

TCP    0.0.0.0:1718           0.0.0.0:0              LISTENING       2528

 

 

On Linux:

 

$ netstat -tulpn | grep 1717

tcp        0      0 0.0.0.0:1717                0.0.0.0:*                   LISTEN      21066/lmgrd       

$

 

Note: You'll need to be root to run netstat effectively.

 

 

Once you have this port usage information, you can make decisions about which ports you want your server processes to use.

 

Feel free to share your tips and ideas on this topic in the comments.

In case you didn't install all your SDD Flows into C:\MentorGraphics, you can follow the procedure defined in How to switch between SDD Flow releases when they are installed to different target locations to switch between them.

You might find yourself with a license file that has the Ethernet address of your license server but you have no idea which of your network hosts that Ethernet address resolves to. You could labor through a manual verification of every system on your network by loggin in remotely and checking the Ethernet address. On Windows, you might use a network utility like Wireshark (http://www.wireshark.org), which might actually work very well. But what if you're on Linux or Solaris? Fortunately, the ARP table can help you solve this problem.

 

ARP stands for Address Resolution Protocol (http://en.wikipedia.org/wiki/Address_Resolution_Protocol) and is the means of address resolution on your network. As network communication between hosts occur, ARP populates a table that contains the physical addresses of the hosts your system is communicating with. While not all hosts are cached in the table at a given time, you can populate the ARP table using ping or arping. Using one of these utilities in a loop can quickly move through all the IP adresses in a subnet and therby populate the ARP table for you.

 

Once this is done, it rather trivial to grep the ARP table for the Ethernet address you're looking for:

 

guyw@guyshost$ arp | grep 00:50:56:AB:4D:6E

netsrv-lic-o3.wv.me  ether   00:50:56:AB:4D:6E   C                     eth0

guyw@guyshost$

 

So in this case, I now know that 00:50:56:AB:4D:6E resolves to netsrv-lic-o3 and I can proceed with configuring my license server on that system.

 

There are likely numerous ways to address this problem. Feel free to share your tips with other users in the comments.

Many of your licensing environments are simple enough for you to "set it and forget it". Some may be more complex, involving local license files and pointers to floating servers on the network. Changes may occur over time that require you to point to new license files/servers or reorder them to improve performance and editing your licensing variables on Windows can be difficult. Fortunately, we have two utilities that makes this much easier.

 

Using the Advanced Environment Editor for Licensing (video)

 

Using the Mentor License Utility to query and edit the licensing environment (video)

As your licenses approach their expiry date, you may see warnings when   you start an application. These warnings are simply to alert you to take   action soon regarding updating your license file.

 

The Warning message: "The following product options expire in fewer than 30 days" (video) doc contains a video and some advice for how to clear these warnings and continue using your application successfully.

Have you ever wondered what each field in your license is for? The Anatomy of a License File doc explains what each field does and will give you a better understanding of how your license environment works.

The Mentor Standard Licensing (MSL) involves multiple components and processes that can be confusing to the uninitiated.

 

Please take a look at our Glossary of Licensing Terminology.

The Mentor Standard Licensing (MSL) v2012_1 release based on  FlexNet  v11.10 is now available and applications are shipping that  require  license servers running this latest version of licensing.

 

See how easy it is to update your license server by watching a video on Updating Your Licensing Manager (Server) on Windows (Video).

If you get a licensing error from one of your applications, aside from ensuring licenses are available and searching SupportNet for the error message, you can use our Mentor License Utility (MLU) to    generate a detailed diagnostic report that may help you or one of our    CAEs determine the root cause.

 

Please take a moment to watch the video demonstration for Generating a Run-time Diagnostic Report with the Mentor License Utility (video).

New releases are shipping and may  require updates to hardware key (dongle) drivers. The hardware key  drivers are now included in the current release of the Mentor Install  Program and there is a video that demonstrates how to update them.

 

Using the Mentor Install Program (MIP) to Update Your Hardware Key Driver (Video)

Mentor Graphics Licensing (MSL) is a 32-bit application and requires the 32-bit libraries on 64-bit Linux systems as well as the Linux Standard Base package, which may not be loaded by default on RedHat 6.

 

 

The following command will install the required 32-bit compatibility package:

 

yum install glibc.i686

 

 

On RedHat 6, load the LSB package with the following command:

 

yum install redhat-lsb.i686

In case you didn't install all your SDD Flows into C:\MentorGraphics, you can follow the procedure defined in How to switch between SDD Flow releases when they are installed to different target locations to switch between them.

New product releases based on Mentor Standard Licensing (MSL) v2012_1 are now shipping and support for some dongles has been discontinued. Please see the Hardware Key (Dongle) Discontinuations and Replacement FAQ to find out if your dongle is affected.

Learn some of the best practices and pitfalls to avoid that will help your installation of the PADS Flow go smoothly.

 

Best practices for a successful PADS Flow installation