10-11-2018
Well, guys, thanks for your advices.
I'd rather not share internal network informations here fully open to the internet. I also contacted IBM support personnel and no luck there either.
I will keep on experimenting, but for now I had to have a solution, so I installed my hosts out of mksysb images from the VIO server.
Even though I will need NIM config later.
So, thanks for you help!
--Trifo
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
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)