Licensing by Management Console

[brackovic]

We have installed NW Server with lot of modules, Legato License Manager and Management Console. For some time the system was running with temporary licenses. Recently we have issued permanent enablers and authorization codes and following LLM and MC user guide we issued enablers and auth codes through MC.
The result was that in MC GUI I can see all products licensed for permanent use without expiration date. But in NW Server GUI these licenses have expiration date. The enablers are in the form GEMS-xxx… so I suppose they have been updated from LLM.
After then I deleted all licenses: locally in NW Server, together with deleting base enabler by nsradmin command and all licenses in LLM through MC. After then I stopped all NW, LLM and MC services and restart them. On the end of this process no one license will be listed in NW GUI and MC GUI.
In the next step I put permanent enablers and authorization codes in LLM through MC GUI. The final result was same: NW Server GUI shows just few of licenses that are issued through MC and all of them have expiration date.
All other licenses in MC GUI are OK and do not have expiration date.

I did forced synchronization of NW Server and LLM several time, but without any result.
Now I leave the system to run scheduled backups.
I hope that something will change in the schedule process or on the beginning of backup process, i.e. that in that moments NW Server will take right licenses from LLM.

What’s going on here?
Why the synchronization doesn’t work properly?
Is there any additional procedure to recheck or to resynchronize licenses?

S

 

[605]

I have never looked at that behaviour but i think it is expected.

NW picks the licenses from LLM and stored them locally, where they in fact have an expiration date, the usual 45 days period.
The reson is simple: In this way, a failing LM would not cause the data zones to be stopped as well.

 

[brackovic]

Correctly, expiration date is today + 45 days.
And what are you thinking that will happen after 45 days??
Will NW continue to work, or it will pick licenses again in the meantime and again “postpone” expiration date?

 

[605]

What do you want ... aren't 45 days enough to repair you LM computer? ;-)

 

[brackovic]

It is more than enough, but in my opinion it is a little bit strange concept: if I design the software I’d pick the right licenses from LLM and show them exactly as they are shown in MC GUI.
In present state, ones can be very confused if starts only NW GUI, because he can see that only temporary enablers and auth codes are present, even he has valid license certificate!!??

I didn’t try, but I think that this problem wouldn’t occur if nsrlic command has been used for issue enablers and auth codes in LLM. I think this is only MC problem (why term GEMS occurs in license format, if GEMS is retired for long time??).

However, this should be the comment and discussion, not any more question,
I’ll keep what’s going on with customer’s production and try to understand the interaction between these three components.

 

[605]

I think this is just due to the fact that NW today still has to serve both license 'manager' methods.

Right now the Admin program does not talk to the LM - it only deals with the resource files. But for that purpose, the licenses must be copied over from LM. To my knowledge, this is done everx 12 hours. Obviously this is done for the licenses only but not for the auth-codes.

As long as you know about it, this should be fine. Maybe LM will be embedded in the future. This of course would change the scenario.