09-23-2009
It's not the best way to do it, but you can reboot it from the HMC.
10 More Discussions You Might Find Interesting
1. AIX
Anyone faced this?
I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r)
The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies
2. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
3. AIX
Hi,
I am having single p series blade with Single Physcial CPU with dual core,
on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor,
My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. AIX
Hi
I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct.
i have rebooted and reconfigured the ip address, but issue is persists.
Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
5. AIX
Hi
im logged in to the vio servers now.
when i give
# lspv | wc -l
i get the count as 6246
how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies
6. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
8. AIX
need to confirm:
we have a system with two VIOs each serving a partition on a local disk to a client LPAR. That client LPAR has them both in a VG which is mirrored (exact). So each disk has a copy of the client LV that the client VG supports. This is the setup that was bequeathed to us by the... (3 Replies)
Discussion started by: maraixadm
3 Replies
9. AIX
I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO.
Currently a big push to manage all our *nix... (4 Replies)
Discussion started by: RecoveryOne
4 Replies
10. AIX
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
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)