Networker

Re: [Networker] Renumbered network addresses

2008-09-25 08:01:09
Subject: Re: [Networker] Renumbered network addresses
From: "Clark, Patti" <clarkp AT OSTI DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 25 Sep 2008 07:52:11 -0400
 <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.  The server is Red Hat Linux, clients are
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.
I've checked forward and backward lookups.  This may seem like a dumb
thing to do, but we wanted to upgrade to 7.4.3 anyway.  Since I'm going
to be doing configuration, may as well start at the beginning.

Patt

> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Tim Mooney
> Sent: Wednesday, September 24, 2008 5:29 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Renumbered network addresses
> 
> In regard to: [Networker] Renumbered network addresses, 
> Clark, Patti said...:
> 
> > We have a small network that is becoming part of a large 
> network.  We
> > are not going to use NAT, so we have to renumber our IP 
> addresses.  So,
> > my server and all of my clients will retain the same names, 
> but get new
> > IP addresses.  Is this a D&R exercise?
> 
> If you mean disaster & recovery (rather than duck & run), 
> then no, I don't
> think so.
> 
> You don't make any mention of how your clients are actually configured
> within NetWorker (like were the clients created using the 
> fully qualified
> domain name?), what version of the server or clients you're using, or
> what you're using for a naming service (DNS, hosts files, NIS, LDAP,
> etc.).
> 
> If the clients are all configured within NetWorker using 
> fully qualified
> domain names, then assuming the naming service (e.g. DNS, NIS, or
> whatever) is correctly updated with the new IPs, it "should 
> just work".
> You shouldn't need to do anything on the NetWorker server or clients.
> 
> 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
> 

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