Nim Issue Post: 302087090

10 More Discussions You Might Find Interesting

1. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion?

2. AIX

NIM Server Issue

Hi, I'm getting the above error while trying to take a MKSYSB image via NIM. I've only just started getting this and don't know why it is failing. Any one got any suggestions? Thanks Kees

3. AIX

Nim

Hello guys, what is a sure-shot single command to find out if the NIM environment is working properly from both master as well as client side?

4. AIX

Nim

Hello everyone I have two questions. 1.-The NIM and EZNIM are the same. 2.-If I have in one partition NIM installed I need to install EZNIM or I need to unistall NIM and then install EZNIM. Thanks for your comments.

5. AIX

NIM master-client connectivity issue

Hello All, I believe my NIM master is fine. lsnim and cat /etc/niminfo gives me the right output. While doing "lsnim" on a client machine, I get ksh:lsnim:"not found". Please someone be nice enough to explain what are the steps to verify the master and client connectivity to do all the NIM...

6. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:...

7. AIX

NIM Issue

I have configured the NIM Master using AIX 5.3.7, I am getting below message bootp:bootp request fail:0 while booting nim client. Though both system are able to ping each other. Regards Manoj

8. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks

9. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client...

10. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik

LEARN ABOUT OSF1

named-xfer

named-xfer(8)						      System Manager's Manual						     named-xfer(8)

NAME

       named-xfer - Pulls BIND zones from another server

SYNOPSIS

       /usr/sbin/named-xfer  -z  zone_to_transfer  -f  db_file	-s  serial_no  [-d debug_level] [-l debug_log_file] [-t trace_file] [-p port] [-S]
       servers...

OPTIONS

       Specifies the name of the BIND zone for the named-xfer daemon to transfer, for example, dec.com. This option is required to  pull  a  zone.
       Specifies  the  name  of the file into which the pulled zone information is placed. This option is  required to pull a zone.  Specifies the
       current serial number of the SOA record for the zone zone_to_transfer.  If serial_no is set to 0, the zone is always pulled. This option is
       required  to  pull  a  zone.  Sets the debug level and determines the amount of debug information to be displayed.  Specifies the file that
       will contain any debug messages from the zone pull.  Specifies the file that will contain a trace from the zone pull.  Specifies  the  port
       that  will  be  used  instead  of the default name server port listed in /etc/services.	Performs a restricted transfer of only the SOA, NS
       records and glue A records for the zone. The SOA record is not loaded by named, but is used to determine when to  verify  the  NS  records.
       See named(8) for more information.  Specifies a list of Internet addresses, in dotted-quad format, from which to pull a zone.  If the first
       host cannot be reached, the named transfer daemon tries to pull the zone from the next host listed.

DESCRIPTION

       The named transfer daemon, /usr/sbin/named-xfer, is a server that is usually run by the named daemon, /usr/sbin/named, but it can  also	be
       run  manually  with  the  given	arguments.   The named transfer daemon runs on a BIND secondary server and pulls BIND zones from a primary
       server. This daemon is not run by default, nor can it be started up from inetd(8).

SEE ALSO

       Commands: named(8)

       Files: resolver(4), services(4)

																     named-xfer(8)