I am assuming the tru64 v4.0f systems are running networker v6.1.4 as
this is the highest version of networker that v4.0f can use, other than
that, you shouldn't have any issues creating the client using backup
interface. As long as the networker server has the backup interface as
the primary NIC and that its actual name is the backup interface also,
there shouldn't be many issues at all, otherwise try setting the "server
interface" name param on the client-backup definition as the backup
interface name of the networker server.
I hope that made sense..haha if dns is not being used, ensure the
/etc/hosts are fully populated with the system names.
Although i do agree that there is always a good chance that the reverse
name lookup will return with the primary nic system name and complain,
but you can try getting around this by just adding the primary nic name
to the client alias, and still verify that the backup lan is being used.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of _richard_
Sent: Thursday, 28 January 2010 8:00 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker Client Authentication Tru64 Unix
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
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
|
