Networker

Re: [Networker] Second IP on Server

2005-08-26 13:24:56
Subject: Re: [Networker] Second IP on Server
From: "Skinner,Alan C(Contractor)" <alan.skinner AT DIX.ARMY DOT MIL>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 26 Aug 2005 13:22:16 -0400
I registered the same Networker fully qualified domain name with both IP's.
Basically 2 nic's 2 different ip's same FQDN for both.  Because every
Networker configuration setting is by FQDN. Can I put the second IP in the
"Server network interface" attribute on the client config?

                               

                         

                        Alan Skinner 
                        Network Administrator 
                        Research, Analysis & Maintenance, Inc. 
                        609-562-6039 

                        <alan.skinner AT dix.army DOT mil> 



-----Original Message-----
From: Darren Dunham [mailto:ddunham AT TAOS DOT COM] 
Sent: Friday, August 26, 2005 1:12 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: Second IP on Server


> 
> I am on a 100mb network.  Trying to make my back ups faster. My hp 
> server
> has a single network interface card with two ports. I have a library with
2 
> sdlt 320's rated at 16MB per second per driver. I am averaging 6 or 7 MB 
> per second per drive. What I thought I could do is assign a second ip to 
> the other nic.  Then go around and change half my host files so that
> half 

Host files on the clients, right?

> my servers would backup on the other ip, basically increase my input 
> to the
> backup server. I did the experiment but networker is giving me a
connection 
> refused. The client recognises the fully qualified domain name and the 
> second ip. I am a windows environment. Is there any configuration on the 
> networker server that needs to done.

Requests will still probably appear to come from the primary interface on
the server.  Do the clients still authorize that interface (you changed it's
name in the host file).

Easier than changing the hostfile on the client might be changing the
'server network interface' attribute in the client config.  Put a name in
there that the client will resolve to the other server IP and you should be
good.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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

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

<Prev in Thread] Current Thread [Next in Thread>