08-26-2008
10 More Discussions You Might Find Interesting
1. AIX
I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level
My understanding is creating mksysb nim on NIM server is for new installation of LPARS
Then;
How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network.
I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows
Resource Name : gmt_fail_mksysb
Server of... (1 Reply)
Discussion started by: KeesH
1 Replies
3. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
4. AIX
Hello,
I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5).
How to install it from a nim mksysb of an another partition ?
Thank you (3 Replies)
Discussion started by: astjen
3 Replies
5. 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
6. AIX
Hi All,
Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like?
Does it even remotely resemble something like
nim -o... (1 Reply)
Discussion started by: combustables
1 Replies
7. AIX
Hi,
I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies
8. AIX
I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root.
Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies
9. 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
10. 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
statd(1M) statd(1M)
NAME
statd, rpc.statd - network status monitor
SYNOPSIS
DESCRIPTION
is an RPC server. It interacts with to provide the crash and recovery functions for the locking services on NFS (see lockd(1M)).
keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, sends a message to the on
each client indicating that the server has rebooted. The client processes then informs the on the client that the server has rebooted.
The client then attempts to reclaim the lock(s) from the server.
on the client host also informs the on the server(s) holding locks for the client when the client has rebooted. In this case, the on the
server informs its that all locks held by the rebooting client should be released, allowing other processes to lock those files.
Options
recognizes the following options and command-line arguments:
This is an obsolete option. All messages and errors are logged to
WARNINGS
The crash of a server is only detected upon its recovery.
FILES
lists hosts and network addresses to be contacted after a reboot
lists hosts and network addresses that could not be contacted after last reboot
includes a number which changes during a reboot
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
lockd(1M), fcntl(2), lockf(2), signal(2), sm(4).
statd(1M)