09-25-2009
Hi Padow,
Thanks for your timely help but I am not using HMC I am using blade server on which vio server is installed I am getting only putty of vio server and even I am not getting the vio server via browser.
I am able to login on vio server using putty, is that any command which will help me to reboot vio client.
Regards
Manoj
Quote:
Originally Posted by
Padow
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
LEARN ABOUT DEBIAN
xnbd-watchdog
XNBD-WATCHDOG(1) General Commands Manual XNBD-WATCHDOG(1)
NAME
xnbd-watchdog -- Watch a NBD device as started by xnbd-client(1)
SYNOPSIS
xnbd-watchdog [--timeout SECONDS] [--interval SECONDS] [--recovery-command COMMAND] [--recovery-command-reboot] [NBD_DEVICE]
DESCRIPTION
With the xnbd-watchdog, you can monitor a running nbd-client and trigger actions on failure.
OPTIONS
The following options are supported:
--timeout SECONDS
Triggers the recovery command action if the watchdog process is unable to connect to the NBD_DEVICE within the given timeout. If
not given, this defaults to 10 seconds.
--interval SECONDS
Specifies the polling interval between probes. If not given, this defaults to 10 seconds.
--recovery-command COMMAND
If given, the COMMAND is executed if the watchdog is unable to connect the NBD device after timeout exceeded.
--recovery-command-reboot
This argument is a shortcut for --recovery-command 'reboot now'. That is, it will reboot the server upon failure.
POSITIONAL ARGUMENTS
The following positional options are supported:
NBD_SERVER
The local nbd-device to be associated with the remote xnbd-server.
SEE ALSO
xnbd-server (8).
AUTHOR
The NBD kernel module and the NBD tools have been written by Pavel Macheck (pavel@ucw.cz) and is now maintained by Paul Clements.
(Paul.Clements@steeleye.com).
The xNBD userland (client and server) have been written by Takahiro Hirofuchi (t.hirofuchi@aist.go.jp)
This manual page was written by Arno Toell (debian@toell.net) for the Debian GNU/Linux system (but may be used by others). Permission is
granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, version 2, as published by the
Free Software Foundation.
XNBD-WATCHDOG(1)