lmdiag
lmdiag enables you to diagnose problems when you cannot check out a license.
Usage
lmdiag [-c license_file_list] [-n] [feature[:keyword=value]]
where:
|
Argument |
Description |
|
-c license_file_list |
Diagnose the specified files. |
|
-n |
Run in non-interactive mode; lmdiag does not prompt for any input in this mode. In this mode, extended connection diagnostics are not available. |
|
feature |
Diagnose this feature only. |
|
keyword=value |
If a license file contains multiple lines for a particular feature, select a particular line for lmdiag to report on. For example: lmdiag f1:HOSTID=12345678 attempts a checkout on the line with the hostid “12345678.” keyword is one of the following: VERSION, HOSTID, EXPDATE, KEY, VENDOR_STRING, ISSUER |
If no feature is specified, lmdiag operates on all features in the license files in your list. lmdiag first prints information about the license, then attempts to check out each license. If the checkout succeeds, lmdiag indicates this. If the checkout fails, lmdiag gives you the reason for the failure. If the checkout fails because lmdiag cannot connect to the license server, then you have the option of running extended connection diagnostics.
These extended diagnostics attempt to connect to each TCP/IP port on the license server, and detects if the port number in the license file is incorrect. lmdiag indicates each TCP/IP port number that is listening, and if it is an lmadmin or lmgrd process, lmdiag indicates this as well. If lmdiag finds the vendor daemon for the feature being tested, then it indicates the correct port number for the license file to correct the problem.
See Also