Sponsored Content
Operating Systems AIX Back up a client NIM from nim master Post 302339554 by balaji_prk on Thursday 30th of July 2009 09:21:32 PM
Old 07-30-2009
Hey

Seems like NIM master is not able to establish a shell to execute its command

I assume you are using communication protocol as "nimsh". you can check that by running the following @ client

grep -i nim_shell /etc/niminfo

Check the status of nimsh daemon @ NIM master & client

# lssrc -s nimsh (if inoperative start it)

Note: If everything if active, I would just delet the /etc/niminfo file from the CLIENT and register the server back..

Hope that helps

Bala
 

10 More Discussions You Might Find Interesting

1. AIX

Nim Master Problem

All, I'm testing NIM on a 7026-m80 machine. But everytime i want to setup the master, i get this error message... Anyone who knows how to solve this issue? google doesn't seem to know much about it # nim_master_setup ############################## NIM master setup... (1 Reply)
Discussion started by: kvanelshocht
1 Replies

2. AIX

nim master

Hi, I want to know what are steps required to create nim master in aix? Regards, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. AIX

nim master

Hi, I want to know how to create nim master in AIX 5.3. Regards, Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies

4. 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... (3 Replies)
Discussion started by: solaix14
3 Replies

5. 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 (2 Replies)
Discussion started by: stephnane
2 Replies

6. AIX

Nim client with different subnet to Master

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

7. AIX

NIM Master hostname

hi Admins, How can I check the NIM master hostname/IP name from NIM client ? I don't see any option that I can try with nimclient command. Let me know.. Thanks, (5 Replies)
Discussion started by: snchaudhari2
5 Replies

8. AIX

NIM master with multiple client subnets

Hi Guys, I'm building a new NIM environment with clients on 3 different subnets. I want to get some advise on what is the best approach for this kind of setup. This is the sample network for my new NIM. Master IP: 10.20.1.20 Client IP subnet_1: 10.20.1.21 Client IP subnet_1: 10.30.1.21... (5 Replies)
Discussion started by: kaelu26
5 Replies

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... (0 Replies)
Discussion started by: omonoiatis9
0 Replies

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 (2 Replies)
Discussion started by: thisissouvik
2 Replies
timed(8)						      System Manager's Manual							  timed(8)

NAME
timed - The network time daemon SYNOPSIS
timed [-tME] [-n | -i network] FLAGS
Specifies the names of the networks (as defined in the /etc/networks file) to be excluded from clock synchronization. Each network name that is an argument to the -i flag is added to the list of networks that the timed daemon will ignore. If the -i flag is used, timed accesses all networks to which the host is connected except for the specified networks. If neither the -i flag nor the -n flag is used, timed tries to access all the network devices connected to the local host. Do not use the -i and -n flags together. Specifies that a machine can become the time server if the master time server becomes inoperative. See the Restrictions section for more information. Overrides the input of slaves. Use the -E flag in conjunction with the -M flag. It specifies that a master timed system will not average the times of the slaves to calculate the network time. Instead, it distributes the time of its local host as the network time. This flag allows a master timed system to distribute time to a network while the network time is controlled by an outside agent (such as the Network Time Protocol (NTP)). Specifies the names of the networks (as defined in the /etc/networks file) to be included in clock synchronization. When timed is started, it gathers information about all the network devices connected to the local host. The network argument to the -n flag is the name of the network that timed should access. If the -n flag is used, only the specified networks are accessed. If neither the -n flag nor the -i flag is used, timed tries to access all the network devices connected to the local host. Do not use the -n and -i flags together. Enables tracing of messages received in /usr/adm/timed.log. DESCRIPTION
The timed daemon is not invoked at boot time by default. You can use /usr/sbin/timedsetup to configure the timed daemon. The timed daemon synchronizes the host's clock with those of other machines on the local area network that are also running the timed dae- mon. The timed daemon slows the clocks of some machines and speeds up the clocks on other machines to create an average network time. The average network time is computed from measurements of clock differences using the Internet Control Message Protocol ICMP timestamp request message. The service provided by timed is based on a master/slave (client/server) scheme. When timed is started on a machine, it asks the master timed daemon for the network time and sets the host's clock to that time. After that, the host accepts synchronization messages periodi- cally sent by the master and calls the adjtime system call to perform the needed corrections on the host's clock. The timed daemon also communicates with the date command to set the date globally, and with timedc, the timed control program. If the machine running the master ceases to function, a machine that is running the timed daemon with the -M flag becomes the new master timed daemon. Note The timed daemon is provided for compatibility. Tru64 UNIX also provides support for the Network Time Protocol through the xntpd daemon. You should use NTP for time synchronization. If you need to run both NTP and the timed daemon, you must run the timed daemon with the -E flag. If you plan to run both the timed daemon and NTP, you should also configure NTP first. RESTRICTIONS
In configurations with two or more hosts each connected to the same two or more subnetworks, only one of the host can run the timed with the -M option. FILES
Specifies the command path Contains messages traced for the timed command Contains information about the known networks RELATED INFORMATION
Commands: date(1), timedc(8), timedsetup(8) Daemons: xntpd(8) Functions: adjtime(2), gettimeofday(2) delim off timed(8)
All times are GMT -4. The time now is 01:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy