topic Re: FlexLM client issue in Operating System - HP-UX

FlexLM client issue

SRoth — Fri, 07 Jan 2005 07:19:26 GMT

We recently changed the IP addresses on two of our HP C3700 workstations due to network changes. Since we did that we cannot access an application (modelsim) that is license managed using FlexLM. We've checked the obvious things like firewall, etc., but cannot get this resolved.

We've been successful using lmstat and lmdiag to communicate with the license server but the application refuses to start.

I know this forum is populated by some very knowledgable people and hope that somebody might have run into this before.

Thanks in advance!

Re: FlexLM client issue

Eric Antunes — Fri, 07 Jan 2005 07:41:37 GMT

Hi,

Did you search the forum by "FlexLM": there is a lot of threads...:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=505933

...

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=8434

And with "modelsim"??

Regards,

Eric

Re: FlexLM client issue

SRoth — Fri, 07 Jan 2005 07:49:05 GMT

That is a very good idea and I will try it now. Of the two posts you listed, the first one might be somewhat applicable so I will check that out.

The user was using the software right up to the time the IP address was changed. Afterwards he could not get a license anymore. Everybody immediately blamed the firewall, probably because that guy wasn't available at the time.

Re: FlexLM client issue

PVR — Fri, 07 Jan 2005 08:01:25 GMT

If you are able to get correct answer for your lmstat queries, application also should work.

It seems to be a name resolution related issue. Pl try putting hostname and Ip address of server and client in both machine's /etc/hosts and try.

Re: FlexLM client issue

SRoth — Mon, 10 Jan 2005 07:39:12 GMT

The problem ended up being the nsswitch.conf file. I hadn't tried getting licenses using the IP address and that worked. For some reason, the system had been reconfigured when the IP address had been changed to not progress to DNS after searching files.

What threw me off was that we could resolve the name via nslookup and that lmdiag worked fine and resolved the name somehow.

Thanks for your help!