07-31-2010
Quote:
Originally Posted by
ross.mather
Is the bootp port blcoked on the NIM server? Its port 67, check the /etc/inetd.conf on the NIM Server.
Also check if their is a firewall between NIM server and client that may block the port.
Thanks but it is not blocked, I have checked /etc/services file also.
10 More Discussions You Might Find Interesting
1. AIX
Hi Guys..
Got a NIM issue.. Am trying to pull a image of a client from NIM server.
am getting the following error... in standard error output..
0042-001 nim: processing error encountered on "master":
Usage: rm File...
Am using the same script to pull image and it works fine..... (1 Reply)
Discussion started by: balaji_prk
1 Replies
2. AIX
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? (1 Reply)
Discussion started by: yanzhang
1 Replies
3. AIX
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 Replies)
Discussion started by: KeesH
3 Replies
4. AIX
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? (2 Replies)
Discussion started by: solaix14
2 Replies
5. AIX
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. (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
6. AIX
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... (3 Replies)
Discussion started by: solaix14
3 Replies
7. AIX
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:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
8. AIX
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 (2 Replies)
Discussion started by: stephnane
2 Replies
9. AIX
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... (0 Replies)
Discussion started by: omonoiatis9
0 Replies
10. AIX
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 (2 Replies)
Discussion started by: thisissouvik
2 Replies
bootpd(8) System Manager's Manual bootpd(8)
NAME
bootpd - Internet Boot Protocol (BOOTP) server
SYNOPSIS
/usr/opt/obsolete/usr/sbin/bootpd [-c chdir-path] [-ttimeout] [-d debug-level] [configfile [dumpfile]]
OPTIONS
Sets the current directory used by a bootpd process while checking the existence and size of client boot files. This is useful when client
boot files are specified as relative pathnames and the bootpd process needs to use the same current directory as the TFTP server (typically
/tftpboot). Sets the debug-level variable that controls the number of debugging messages generated. For example, -d 4 sets the debugging
level to 4. Valid entries are 1 to 4, where 1 specifies lower level of messages and 4 the highest. Specifies the timeout value (in min-
utes) that a bootpd process waits for a BOOTP packet before exiting. If no packets are received for timeout minutes, the program exits. A
timeout value of zero means that a bootpd process will wait forever. When the bootpd daemon is not started using the inetd daemon, this
option is forced to zero.
DESCRIPTION
The bootpd daemon implements an Internet Boot Protocol server as defined in RFC 951, RFC 1532, and RFC 1533. In order to use the bootpd
daemon, you must install the Obsolete Commands and Utilities subset (OSFOBSOLETExxx). It can be started by the /usr/sbin/inetd daemon by
including the following line in the /etc/inetd.conf file: bootps dgram udp wait root /usr/sbin/bootpd bootpd
This causes bootpd to be started only when a boot request arrives. If bootpd does not receive another boot request within fifteen minutes
of the last one it received, it exits to conserve system resources. The -t option can be used to specify a different timeout value in min-
utes (for example, -t20). A timeout value of zero means forever.
To run the bootpd daemon, you must also run the tftpd daemon.
Upon startup, bootpd first reads its configuration file, /etc/bootptab, and then begins listening for BOOTREQUEST packets. See bootptab(4)
for a description of the configuration file. The bootpd daemon looks in /etc/services to find the port numbers it should use. Two entries
are extracted: The bootp server listening port The destination port used to reply to clients
If the port numbers cannot be determined this way, they are assumed to be 67 for the server and 68 for the client.
The bootpd daemon rereads its configuration file when it receives a hangup signal, SIGHUP, or when it receives a bootp request packet and
detects that the file has been updated. Hosts can be added, deleted, or modified when the configuration file is reread. If bootpd is com-
piled with the -DDEBUG option, receipt of a SIGUSR1 signal causes it to dump its memory-resident database to the /usr/adm/bootpd.dump file
or dumpfile specified in the command line.
RESTRICTIONS
Individual host entries must not exceed 1024 characters.
You cannot run bootpd and joind on the same system at the same time.
FILES
Internet Boot Protocol server. The bootpd daemon dump file. Defines the sockets and protocols used for Internet services.
SEE ALSO
Commands: bootpgw(8), bprelay(8), inetd(8), joind(8), tftpd(8)
Files: bootptab(4)
DARPA Internet Request For Comments:
Bootstrap Protocol (RFC 951)
Clarifications and Extensions for the Bootpstrap Protocol (RFC 1532)
DHCP Options and BOOTP Vendor Extensions (RFC 1533)
bootpd(8)