10-02-2018
AIX NIM issues are typically resolved by examination of the error messages:
Information about Network Installation Management (NIM) error and warning messages is provided, with suggestions for resolving specific problems.
Quote:
If an error condition is detected when a NIM command is executed, the command returns an error message. If a NIM command returns a warning message, this indicates that either a less severe problem was encountered by NIM, or a problem was encountered in a command called by NIM, and the severity of the problem cannot be readily determined by NIM. In the latter case, additional messages or output from the command often reveal the nature of the problem.
All NIM error messages begin with 0042 and are followed by a three-digit error code.
Did you find or examine any NIM error messages?
Reference:
IBM Knowledge Center Error - Information about Network Installation Management (NIM) error and warning messages is provided, with suggestions for resolving specific problems.
9 More Discussions You Might Find Interesting
1. AIX
HI folks,
Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 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
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
4. What is on Your Mind?
I've read about BITNET, CompuServe... CompuServe was probably not a network but an online service. Are (were) there any other networks alternative to Internet? Does anyone have experience with them? Do they still exist, is it possible to access them over Internet? There seems not to be another way... (13 Replies)
Discussion started by: Action
13 Replies
5. Solaris
If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies
6. Solaris
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 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
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
9. 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)