Networker

Re: [Networker] Problem backing up a server with multiple IP addresses

2008-03-28 15:20:05
Subject: Re: [Networker] Problem backing up a server with multiple IP addresses
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 28 Mar 2008 14:17:22 -0500
Hello,
Add a PTR  ( reverse look-up ) in your DNS server ( dns server specified 
on  client IP settings).
Typically you will see Forward look-up zones( in the dns server config) 
where your primary server adders name is specified
and 
Reverse look-up zones --This is where you need PTR record.
go to
155.247.X.X subnet and add .
Most DNS server are configured for Forward and Reverse look-up but not 
nassasarily, in that case you may have to request Network admins to create 
reverse look-up zone for you.
HTH




Stan Horwitz <stan AT TEMPLE DOT EDU> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
03/28/2008 01:57 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Stan Horwitz <stan AT TEMPLE DOT EDU>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] Problem backing up a server with multiple IP addresses






Actually, I take that back. Reverse DNS does not work for the client 
on the NSR server, but how do I fix that?

On Mar 28, 2008, at 2:41 PM, Stan Horwitz wrote:
> On Mar 28, 2008, at 2:25 PM, Tim Mooney wrote:
>>
>> Nearly the same way you would on Solaris.  netstat -rn to show 
>> routes,
>> "route add" with some additional bits to add them.  To make the route
>> change survive reboots, you'll need to add the arguments to the 
>> "route
>> add" command to a file in /etc/sysconfig/network-scripts -- probably
>> something like "/etc/sysconfig-network-scripts/route-backupserver".
>>
>> I doubt it's a routing issue, though.
>>
>> Stan, can you post what error messages or symptoms you're actually 
>> seeing?
>
> The client is Temple's main web server. I would think that if a 
> routing problem occurred there, our help desk would be swamped with 
> calls.
>
> Here's what I get when I try a recover on this Linux client ...
>
> [root@albatross logs]$ recover
> Reverse DNS lookup failed for address 155.247.166.60
> 53362:recover: Cannot start session with server 
> xxxx.ocis.temple.edu: RPC receive operation failed.  A network 
> connection could not be established with the host.
>
> The 155.247.166.60 IP number is not the client's primary address. 
> This client's primary address is 155.247.166.94.
>
> Here's what happens with a server initiated backup ...
>
> NetWorker savegroup: (alert) test2 completed, Total 1 client(s), 1 
> Failed. Please see group completion details for more information.
>
> Failed: albatross
>
> Start time:   Fri Mar 28 13:01:18 2008
> End time:     Fri Mar 28 13:02:02 2008
>
>
> --- Unsuccessful Save Sets ---
>
> * albatross:All 5 retries attempted
> * albatross:All 39078:savefs: SYSTEM error: Host name verification 
> failed - unknown host: 155.247.166.60
> * albatross:All
> * albatross:All 7183:savefs: Cannot access nsr server `xxxx'
> * albatross:All savefs albatross: failed.
>    * <ERROR> :  Failed with error(s)
>
> All the usual network tests (traceroute, nslookup, reverse dns, all 
> work fine between the NSR server and this client).
>
> On the client, ifconfig -a looks like ...
>
> eth0      Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.94  Bcast:155.247.167.255  Mask: 
> 255.255.254.0
>          inet6 addr: fe80::214:22ff:fe22:708e/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:348737173 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:414493435 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:3190179819 (2.9 GiB)  TX bytes:2294059543 (2.1 GiB)
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:1    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.60  Bcast:155.247.166.255  Mask: 
> 255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:2    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.167.14  Bcast:155.247.166.255  Mask: 
> 255.255.254.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:3    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.90  Bcast:155.247.166.255  Mask: 
> 255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:4    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.226  Bcast:155.247.166.255  Mask: 
> 255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:5    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.19  Bcast:155.247.166.255  Mask: 
> 255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth0:6    Link encap:Ethernet  HWaddr 00:14:22:22:70:8E
>          inet addr:155.247.166.96  Bcast:155.247.166.255  Mask: 
> 255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
> eth1      Link encap:Ethernet  HWaddr 00:14:22:22:70:8F
>          BROADCAST MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>          Base address:0xdcc0 Memory:fe4e0000-fe500000
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:470115 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:470115 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:48204556 (45.9 MiB)  TX bytes:48204556 (45.9 MiB)
>
> sit0      Link encap:IPv6-in-IPv4
>          NOARP  MTU:1480  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> 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

--
Stan Horwitz
Temple University
Enterprise Systems Group
stan AT temple DOT edu

CONFIDENTIALITY STATEMENT: The information contained in this e-mail, 
including attachments, is the confidential information of, and/or is 
the property of, Temple University. The information is intended for 
use solely by the individual or entity named in the e-mail. If you are 
not an intended recipient or you received this in error, then any 
review, printing, copying, or distribution of any such information is 
prohibited. Please notify the sender immediately by reply e-mail and 
then delete this e-mail from your system.

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

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