09-14-2009
Hi again,
I think you should focus on getting this working before adding more sources to youre NIM server.
As faruk mentions there are a lot of things that can go wrong.
Not sure what he means with "run this command in client.". This is used to allocate resources to a client for a BOS installation on the NIM master.
These protocols are typical to NIM
1 ping
2 bootpd/dhcp
3 tftp
4 nfs
5 nimsh
6 nimaux
You can find a lot of info on NIM is this document
IBM Redbooks | NIM from A to Z in AIX 5L
But sumathi.k please post more info on the error so we can help you ;-)
Last edited by DogHeaD; 09-15-2009 at 12:33 PM..
Reason: double entry
10 More Discussions You Might Find Interesting
1. IP Networking
I use DHCP on my AIX box at home . I want to connect to my Cable ISP as a
DHCP Client . the thing I did was this :
smit
Communications Applications and Services
TCP/IP
Use DHCP for TCPIP Configuration and Startup
"Select the interface you want to use"
en0
"Enter a hostname"
OK
after... (3 Replies)
Discussion started by: zumbi
3 Replies
2. AIX
Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies
3. AIX
Hello everyone
I would like to hear your opinions about this procedure to backup a client to my nim master
1.-I got a cron that make a mksysb from x machine
2.-This mksysb I send by ftp to my nim master.
3.-When I got it in the nim master machine. I create a mksysb resource from this... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
4. 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
5. AIX
Hi all,
I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50.
From one lpar I installed and set up NIM master server called testAIX1.
I have created client and allocated resources to it:
testAIX1:/ > lsnim -l test_lpar
test_lpar:
class = machines
... (4 Replies)
Discussion started by: phobus
4 Replies
6. AIX
Hello everyone
I was looking for the filesets to install a nim client on a linux box. (red hat 5 for power)
I have the nim master on aix box and I have different nim client with aix.
I download some filesets fron aix cd to linux box, but Im still hang up.
Some one know where I can find... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
7. 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
8. AIX
Iam attempting to add a client to NIM however the new client has a different subnet than master 10... & 193... , I've established from redbooks that it should be possible but can't find anything that states how?
Does anyone use nim in this way? (5 Replies)
Discussion started by: gefa
5 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)