> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Tim Mooney
> Sent: Thursday, September 25, 2008 3:28 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Renumbered network addresses
>
> In regard to: Re: [Networker] Renumbered network addresses,
> Clark, Patti...:
>
> > <Sigh> That's what I thought. The real issue seems to be the server
> > can't find itself. It's complaining that it can't find the
> old address
> > which has been completely removed from DNS and /etc/hosts.
> I am also
> > getting the same from NMC.
>
> That has me wondering if maybe I'm incorrect -- maybe you *do* need to
> do something on the NetWorker server.
>
> > both RH and Windows. I use FQDN throughout the Networker configs.
> > Version is 7.3.3. We use DNS, but my configs use files
> first, then DNS.
>
> Same for us.
>
> One thing you might want to check on is the hostid. On at least RHEL,
> the hostid is just the hex representation of the four octets of the IP
> address.
Yep, already found it. Surprised the heck out of me. I'd thought that
hostid was hardcoded. Obviously not. I also found the notices sent via
email about the licenses being disabled. One big surprise that was
really pleasant, PowerLink has been upgraded and now provides an easy
interface to request a move of the licensed components for a single
hostid. It generates the new enablers and everything. This is really,
really cool! I've never really had much to cheer me on PowerLink, but
it is actually getting useful beyond doco and software downloads.
>
> Since your IP address changed, your Linux hostid changed.
> That shouldn't
> impact the clients, but it might impact the server.
>
> You indicate that it's complaining that it can't find the old address.
> Where are the complaints showing up, and are they in response
> to something
> (like running a savegrp) or are they just spontaneous messages in some
> log file? What's the exact message?
It seems that whenever I start any networker-related process, it's
checking the resources. The old IP is still showing up in the resource
files. At this point, I think it's just a nag since the new IP is also
present.
>
> Are you running nscd or a caching nameserver on the NetWorker
> server? Is
> there any possibility that it's cached the old IP and hasn't
> yet expired
> it from the cache?
No, none of that. Also, the box has been rebooted.
Because of other issues inhouse, I'm going ahead with an upgrade to
v7.4.3. I know this goes against any recommendations given the current
situation, but there are 2 issues driving this, a need to backup a
different client type that I don't have a client pak license for which
went away with 7.4.2 and a new server/tape library/LTO-4 w/encryption
which will happen in about 6 weeks. Nothing like practice to keep
everything sharp.
>
> Tim
> --
> Tim Mooney
> Tim.Mooney AT ndsu DOT edu
> Enterprise Computing & Infrastructure
> 701-231-1076 (Voice)
> Room 242-J6, IACC Building
> 701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
>
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 with 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
|
