If you elect to use ioscan for checking for claimed hardware (using the -f
option), then recommend you put in a chunk of timeout logic and send an
appropriate error message if a timeout condition occurs. The HPUX ioscan
command is not terribly robust (as we discovered after implementing a BB
module using it).
The ioscan command can hang for the sort of adverse hardware conditions you
are trying to check for.
This is commonly known as a "feature". - to be spoken aloud as either Eric
Idle or John Cleese.
To T. Yang: I never bothered putting together a tarball for www.deadcat.net;
lack of energy to write up a usage document. It supports table and group
files for defining classes of hardware components to be checked for (number
of HBAs, tape drives, etc). If you want a tarball to play with or use as a
starting point for development, let me know. The module does not have a
timeout control - knocking down a hung ioscan is problematic. Will not post
tarball here as Mr. Storner would probably hunt me down and toss a holy hand
grenade and/or taunt me mercilessly. (What can I say, it's a Monty Python
kind of day).
-----Original Message-----
From: T.J. Yang [mailto:user-8e841282cda5@xymon.invalid]
Sent: Friday, September 14, 2007 9:04 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] HP PA-RISC Hardware monitoring ?
Hi, Thomas
But ioscan is jus a scan of existing hardwares, it doesn't tell if each
component
is ok or not. following is an example of a C3600.
root at 8519> uname -a
HP-UX ilad8519 B.11.11 U 9000/785 2013140223 unlimited-user license
root at 8519> model
9000/785/C3600
root at 8519> ioscan -k
H/W Path Class Description
====================================================
bc
10 ioa System Bus Adapter (582)
10/0 ba Local PCI Bus Adapter (782)
10/0/12/0 lan HP PCI 10/100Base-TX Core
10/0/13/0 audio Built-in Audio
10/0/14/0 ext_bus IDE Primary Channel
10/0/14/0.0 target
10/0/14/0.0.0 disk TEAC CD-532E-B
10/0/14/0.7 target
10/0/14/0.7.0 ctl Initiator
10/0/14/1 ba PCI Core I/O Adapter
10/0/14/1/1 tty Built-in RS-232C
10/0/14/1/2 tty Built-in RS-232C
10/0/14/1/3 ext_bus Built-in Parallel Interface
10/0/14/1/4 siopc Built-in Floppy Drive
10/0/14/1/4.1 floppy HP_PC_FDC_FLOPPY
10/0/14/2 usb Built-in USB Interface
10/0/14/2.1 usbhub USB Root Hub
10/0/15/0 ext_bus SCSI C896 Ultra Narrow Single-Ended
10/0/15/0.7 target
10/0/15/0.7.0 ctl Initiator
10/0/15/1 ext_bus SCSI C896 Ultra2 Wide LVD
10/0/15/1.5 target
10/0/15/1.5.0 disk QUANTUM ATLAS10K-9LVD
10/0/15/1.6 target
10/0/15/1.6.0 disk QUANTUM ATLAS10K-9LVD
10/0/15/1.7 target
10/0/15/1.7.0 ctl Initiator
10/1 ba Local PCI Bus Adapter (782)
10/1/4/0 lan PCI Ethernet (11484320)
10/4 ba Local PCI Bus Adapter (782)
10/6 ba Local PCI Bus Adapter (782)
10/6/2/0 graphics PCI Display (103c108b)
32 processor Processor
49 memory Memory
root at 8519>
T.J. Yang
Date: Fri, 14 Sep 2007 10:26:49 +0200
From: user-5195ec0973aa@xymon.invalid
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] HP PA-RISC Hardware monitoring ?
Hi !
the magical command on HP-UX (PA-RISC) is 'ioscan' on HP-UX (IA64) it's
'machinfo'. For example, if you want information on processors or fc
hba, you could make :
# ioscan -fknC processor | grep -i processor
# ioscan -fknC fc | grep -i fc
or simply :
# ioscan -fknC
to see all possibilities. Hobbit runs just fine on this kind of
hardware, I've tested it for months on HP-UX 10.20, 11.00, 11i. You just
need 'gcc' and GNU 'make' to build clients and that's all.
Sincerly,
ThomaS
T.J. Yang a écrit :
Anyone know is there a module (bb or hb) to monitor HP hardware ?
May be better question is what is the similar command for ipmitool or
prtdiage in HP-UX ?
T.J. Yang
Capture your memories in an online journal!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
Kick back and relax with hot games and cool activities at the Messenger
Café.
http://www.cafemessenger.com?ocid=TXT_TAGLM_SeptWLtagline