Networker

Re: [Networker] Networker Client Authentication Tru64 Unix

2010-02-04 11:14:35
Subject: Re: [Networker] Networker Client Authentication Tru64 Unix
From: Thomas Wicks <thomasthunder AT GMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 4 Feb 2010 21:32:12 +0530
There is a server interface option in networker 7.4.4 and latest 7.6 .
Suggest an upgrade .



On Thu, Jan 28, 2010 at 2:29 PM, _richard_ <
networker-forum AT backupcentral DOT com> wrote:

> Hi,
>
> unfortunately in our environment, hardware to test air-traffic-control
> software, we have to deal with non-unique hostnames and sometimes
> ip-adresses as well. That is because the software must be tested on a
> hardware environment absolutely identical to the operative systems, before
> it is verified to go to the operative systems. Because of these
> circumstances, we have to deal with clients (tru64 4.0f) which are connected
> to a Networker Backup-Server on Tru64 5.1b. Networker Software is 7.2, using
> th same hostname and sometimes even same ip-adresses. To get around this
> problem, we introduced a backup-network, meaning that we put in extra
> network card in each client giving it a unique interface name and an address
> out of the backup-network. The problem is that i am having problems
> registering the client in the networker server in a way that the client ist
> not authenticated by its hostname but by the name of the backup-interface.
> What i wanted to do, if possible, is that i wanted!
>  to introduce the client to the server with its ip-address or the name of
> the backup network interface, rather then the hostname. But tru64 clients
> always seem to authenticate themselves with their hostname.
> Anybody got a hint, how i can get around this problem?
> I have a dirty solution, that i am changing the hostname prior to a manual
> backup, with "rcmgr set hostname" and an "inet restart", but that is not
> practical in an scheduled automatic environment, because if unattended, the
> proceudre does not know if it is critical to that because important
> test-procedures are running and you cannot change the hostname in runtime or
> mess around with restarting inet.
>
> Thanks in advance...
>
> Richard
>
> +----------------------------------------------------------------------
> |This was sent by richard.zoller AT t-online DOT de via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
>
> 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
>



-- 
The only permanent thing in this world is Change .

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>