Skip navigation
All Places > Licensing and Installation > Blog > 2014 > February

Network latency is of great concern when using Mentor Graphics software, particularly the releases that have an underlying iCDB architecture. The ping utility is often used to get an idea of how the network is performing. However, the ping results are sometimes not granular enough, and the data can be difficult to analyze if you run ping for long periods of time.


In this tip of the week, I'll tell you about one of my favorite tools for getting good network latency data: psping.


To get useful network latency measurements you should use a larger packet size that closely represents the packets created by the application you are verifying, and you need to do it over time. You can do that with the standard ping command, but then you'd have to post process the data to get the information you want. Doable, but not desirable. One thing that you can't do with the standard ping that is sometimes useful is ask it to use a specific port number so you can verify that the port you want to communicate with is open. Psping does all that, and provides a tidy summary report.


Psping works in client/server mode for the network latency test. In this example, I'll start a psping server on a machine called 'kvmw7x64', and ask it to listen for pings on port 9001 using TCP protocol. I've also specifed IPv4:




Now on a client machine, I'll start psping and ask it to transmit 1200 byte packets to kvmw7x64 on port 9001 for 3600 seconds (1 hour):




When the hour is up, I can view the results as a summary. This provides a pretty good indicator of what my actual network latency is over time.



I'd suggest you fire this up during the time of the day when your network is the most heavily utilized and again when it's the least heavily utilized. Save these numbers as a baseline. It might not hurt to run it every so often to see if things are changing. Then, any time you suspect problems you are having are related to a slow network, run it and compare the results to your baseline. That should either incriminate your network exonerate it.



It is sometimes helpful to do a status of the license server by feature name. This is done by using the lmstat command with the '-f' option. Here's the syntax:

lmutil lmstat -f [feature] -c [path to license file]


*Specifying the path to license file is not necessary if the path is set in LM_LICENSE_FILE


For example, this command will show if the feature 'pwrshell' is in use, and by whom:

C:\MentorGraphics\Licensing>lmutil lmstat -f pwrshell -c c:\flexlm\test.txt

lmutil - Copyright (c) 1989-2013 Flexera Software LLC. All Rights Reserved.

Flexible License Manager status on Fri 2/14/2014 12:24


[Detecting lmgrd processes...]

License server status: 1717@ORW-6YNPBZ2

License file(s) on ORW-6YNPBZ2: C:\flexlm\test.txt:


ORW-6YNPBZ2: license server UP (MASTER) v11.11


Vendor daemon status (on ORW-6YNPBZ2):


mgcld: UP v11.11

Feature usage info:


Users of pwrshell: (Total of 1 license issued; Total of 1 license in use)

"pwrshell" v2014.020, vendor: mgcld

floating license


jasper ORW-6YNPBZ2 (v2012.06) (ORW-6YNPBZ2/1717 101), start

Fri 2/14 12:23

Describing a problem (or a solution) is often much easier using a picture.


Windows 7 contains a screenshot tool I use almost every day.  "Snipping Tool" is now available in the Accessories program group:




In the picture above, I have highlighted what I want the reader to look at using a "red pen" before copying and pasting the picture into my document or e-mail.


How to capture a screenshot of a menu


If you want a picture of a menu (like the one above), select "New":


Then press ESC, open the menu and then press CTRL+PrtSc (Ctrl, then Print Screen).  Then drag around the area you want to capture.



Finally, if you like a challenge, how did I generate a screenshot of the Snipping Tool menu?

For those of you who are new to Linux, or maybe looking to add some new commands to your system admin toolbox, check out the following article from our friends at, filled with examples and more!


50 Most Frequently Used UNIX/Linux Commands (With Examples)