Re: [Networker] Backup server with 2 IP address

To utilize two adapters without any trunking software you will have to
have each adapter on different subnet.
Otherwise (as in your example) the Linux host will accept packets on any
of the two addresses but will communicate with the outside world only on
the adapter with the lower ip address.
Itzik

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Terry Lemons
Sent: Monday, April 10, 2006 20:11
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Backup server with 2 IP address

Hi Librado

I believe that all IP entities that NetWorker touches, including client
names, server names, and even alternate server network interface names,
must be registered in your DNS server.

Hope this help.
tl 

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Librado Pamintuan
Sent: Monday, April 10, 2006 10:38 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Backup server with 2 IP address

Good morning to all,
I'm trying to utilize the 2nd port of my NIC and somehow the clients
cannot talk to the server when I change the setting 'server network
interface' to this new address.


99.2.2.4 linux2.regina (eth0)



then in configured the 2nd port
99.2.2.2 linux2_eth1 (eth1)


Tried to make some clients to send data to the 2nd port, but they cannot
see the backups server, here's the error message.


FS1:vol1:data RPC error, Name to address translation failure
FS1:vol1:data Cannot access nsr server 99.2.2.2


What seems to be I'm doing wrong here? or missing?


thanks in advance,


Librado Pamintuan
Technical Support Analyst II
Information Systems Dep.
Operations Group
City of Regina


Phone:          (306) 777-7573
General Fax: (306) 777-6804
eFax:             (306) 546-6002
eMail:            lpamintuan AT regina DOT ca



<html><body><font face = "arial" size = "1">
DISCLAIMER: The information transmitted is intended only for the
addressee and may contain confidential, proprietary and/or privileged
material. Any unauthorized review, distribution or other use of or the
taking of any action in reliance upon this information is prohibited. If
you received this in error, please contact the sender and

delete or destroy this message and any copies.
</font><body></html>

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

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