Oscar,

We have EMC NetWorker support (Jeanette & Oscar) saying the auth code
should be the same as entered into the LLM and the expire date should
say never or..
I think they're wrong as that's not our experience.

But we have v7.0 running with an Enterprise Enabler installed locally.
And now we are deleting that base enabler and aiming the v7.0 NetWorker
servers at our v7.3 server that is running LM and we see with the
command
        lgtolic -s "::1" -l 
that it has checked out a NetWorker license and a UNIX clientpak license
but sometimes it's asking for an update enabler and we haven't upgraded
- been running v7.0 for literally years.  It's just that we are going
from a local license(Enterprise Enabler) to the LM.

Anyone else have some thoughts/experience on this ?

Thanks - John 

-----Original Message-----
From: Oscar Olsson [mailto:spam1 AT qbranch DOT se] 
Sent: Thursday, March 30, 2006 12:41 PM
To: Legato NetWorker discussion; Ballinger, John M
Subject: Re: [Networker] V7.3 with LLM checked and installed with
another NetWorker server running v7.0 pointed at the LLM

On Thu, 30 Mar 2006, Ballinger, John M wrote:

BJM> Is it normal to look at the licenses under "Register" on the non 
BJM> LLM systems and have the enabler be listed as EXT-GEMS-... With 
BJM> auth field blank and an expire date of ~45 days in the future 
BJM> instead of forever etc.?

Yep. The LM server will issue a 45-day license to the server in
question, and I think its refreshed every hour or so. If the LM server
goes offline, you have thus 45 days to get it to come online again.

//Oscar

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER