10-26-2011
Right the good news is the NIM server knows that the LPAR is there and ready to be installed. It also knows that certain resources are allocated to it.
Please excuse me if I am "Teaching my Granny how to suck eggs".
How did you try to boot the LPAR, from the NIM server? Or have you started the LPAR to SMS and setup the network boot configuration. This as you well know includes the IP address of the server, its subnet mask, and the IP address of the gateway. You can then PING the NIM master to make sure the network between the NIM master and client is open with no firewall in the way, which often happens.
Again if I am telling you things you already know please excuse me. The things I have outlined above are the usual reasons a NIM client will not boot from the NIM master.
10 More Discussions You Might Find Interesting
1. 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
2. AIX
Hello All,
While trying to add NIM client to the NIM environment from NIM client machine, I get the following error:
1800-109
There are currently no additional SMIT screen entries available for this item. This may require installation of additional software before it can be accessed.
... (1 Reply)
Discussion started by: solaix14
1 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
:b:Hi...
I need help to configure nim client on nim server..
can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not..
Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 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
TIMED(8) System Manager's Manual TIMED(8)
NAME
timed - time server daemon
SYNOPSIS
timed [ -t ] [ -M ] [ -n network ] [ -i network ]
DESCRIPTION
Timed is the time server daemon and is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with the time of
other machines in a local area network running timed(8). These time servers will slow down the clocks of some machines and speed up the
clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences
using the ICMP timestamp request message.
The service provided by timed is based on a master-slave scheme. When timed(8) is started on a machine, it asks the master for the net-
work time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and
calls adjtime(2) to perform the needed corrections on the host's clock.
It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control program. If the machine running
the master crashes, then the slaves will elect a new master from among slaves running with the -M flag. A timed running without the -M
flag will remain a slave. The -t flag enables timed to trace the messages it receives in the file /usr/adm/timed.log. Tracing can be
turned on or off by the program timedc(8). Timed normally checks for a master time server on each network to which it is connected, except
as modified by the options described below. It will request synchronization service from the first master server located. If permitted by
the -M flag, it will provide synchronization service on any attached networks on which no current master server was detected. Such a
server propagates the time computed by the top-level master. The -n flag, followed by the name of a network which the host is connected to
(see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -n flag appears, that network
name is added to a list of valid networks. All other networks are ignored. The -i flag, followed by the name of a network to which the
host is connected (see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -i flag
appears, that network name is added to a list of networks to ignore. All other networks are used by the time daemon. The -n and -i flags
are meaningless if used together.
FILES
/usr/adm/timed.log tracing file for timed
/usr/adm/timed.masterlog log file for master timed
SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4P), timedc(8),
TSP: The Time Synchronization Protocol for UNIX 4.3BSD, R. Gusella and S. Zatti
4.3 Berkeley Distribution November 17, 1996 TIMED(8)