HP/Compaq ILO and check_http

[Jens Kruse]

Hi Karl!

Karl DeBisschop wrote:
 > On Tue, 2003-06-10 at 02:40, Jens Kruse wrote:


 > I have only just scanned it, but it looks to me like the ILO is
 > streaming the data...
 >
 > Could that be true?

As far as I understand the White Paper
(http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?countrycode=1000&prodid=510|Remote+Insight+Board+Lights-Out+Edition&source=TC020404TB.xml&dt=21) 


it is streaming ...

 > If so, you need to be able put a size and/or time limit on it. You would
 > probably like to be able to say 'report an error if in n seconds less
 > than j bytes are delivered.'

Where would I get these parameters? I'd probably have to measure the
data (i.e. with wget)?

 > Does that make any sense for your context? (I admit I'm doing alot of
 > guessing here still, as I still don't know much [anything, actually]
 > about the device -- I've heard of a 'Lights Out' card for campaq, I
 > think - is that what this is? Are there any technical specs available
 > for the device? Do they say anything about a streaming mode or something
 > similar?)

Yes, it's the actual version of the former RILO-Card (Remote Insight
Lights Out), which we are also monitoring (with check_http -H HOST -p
PORT), because the httpd-Server of the device crashed sometimes in the past.
The actual Version is called iLO and is an onboard Chip, the old RILO is
a PCI-Card.

Actual Tech Specs for iLO are available here:
http://h18013.www1.hp.com/products/servers/management/ilo/index.html

 > I don't think you can set a max on bytes delivered with check_http
 > presently, tyhough you can with check_tcp from CVS. But it's a feature
 > that could and probably should be added.

I won't go that way, because I don't know anything on streams.
If this feature seems interesting for you and/or the community, I'd like
to help as much as possible ...

Pls. keep me informed if can help in any way!

Regards, Jens



 >><------------------------ schnipp ------------------------------>
 >>monitor2-lx:~ # tcpdump -i eth0 host 10.35.178.154
 >>tcpdump: listening on eth0
 >>08:33:48.382982 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: S 307329410:307329410(0) win 5840 <mss
 >>1460,sackOK,timestamp 196131746 0,nop,wscale 0> (DF)
 >>08:33:48.383782 arp who-has monitor2-lx.mobilcom.de (0:50:8b:e2:2e:b3)
 >>tell mccg-lx-rilo.mobilcom.de
 >>08:33:48.383798 arp reply monitor2-lx.mobilcom.de is-at 0:50:8b:e2:2e:b3
 >>08:33:48.384202 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: S 693572000:693572000(0) ack 307329411
 >>win 5840 <mss 1460>
 >>08:33:48.384223 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 1 win 5840 (DF)
 >>08:33:48.384364 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: P 1:99(98) ack 1 win 5840 (DF)
 >>08:33:48.387907 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 1:16(15) ack 99 win 5840
 >>08:33:48.387921 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 16 win 5840 (DF)
 >>08:33:48.388731 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 16:18(2) ack 99 win 5840
 >>08:33:48.388741 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 18 win 5840 (DF)
 >>08:33:48.389579 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 18:41(23) ack 99 win 5840
 >>08:33:48.389590 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 41 win 5840 (DF)
 >>08:33:48.390244 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 41:43(2) ack 99 win 5840
 >>08:33:48.390254 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 43 win 5840 (DF)
 >>08:33:48.391103 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 43:81(38) ack 99 win 5840
 >>08:33:48.391113 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 81 win 5840 (DF)
 >>08:33:48.391732 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 81:83(2) ack 99 win 5840
 >>08:33:48.391749 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 83 win 5840 (DF)
 >>08:33:48.392648 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 83:106(23) ack 99 win 5840
 >>08:33:48.392672 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 106 win 5840 (DF)
 >>08:33:48.393500 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 106:125(19) ack 99 win 5840
 >>08:33:48.393518 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 125 win 5840 (DF)
 >>08:33:48.394156 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 125:127(2) ack 99 win 5840
 >>08:33:48.394175 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 127 win 5840 (DF)
 >>08:33:48.395005 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 127:153(26) ack 99 win 5840
 >>08:33:48.395024 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 153 win 5840 (DF)
 >>08:33:48.395649 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 153:155(2) ack 99 win 5840
 >>08:33:48.395667 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 155 win 5840 (DF)
 >>08:33:48.396511 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 155:157(2) ack 99 win 5840
 >>08:33:48.396531 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 157 win 5840 (DF)
 >>08:33:48.398632 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 157:160(3) ack 99 win 5840
 >>08:33:48.398668 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 160 win 5840 (DF)
 >>08:33:48.400319 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 160:696(536) ack 99 win 5840
 >>08:33:48.400335 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 696 win 6432 (DF)
 >>08:33:48.400323 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: . 696:1232(536) ack 99 win 5840
 >>08:33:48.400349 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 1232 win 7504 (DF)
 >>08:33:48.402360 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 1232:1464(232) ack 99 win 5840
 >>08:33:48.402376 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 1464 win 8576 (DF)
 >>08:33:48.404361 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57059: P 1464:1936(472) ack 99 win 5840
 >>08:33:48.404371 monitor2-lx.mobilcom.de.57059 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 1936 win 9648 (DF)
 >>
 >>
 >>
 >>40 packets received by filter
 >>0 packets dropped by kernel
 >><------------------------ schnipp ------------------------------>
 >>
 >>And here for the check_http ...
 >>
 >><------------------------ schnipp ------------------------------>
 >>monitor2-lx:/usr/local/nagios/libexec # ./check_http -H 10.35.178.154
 >>Socket timeout after 10 seconds
 >>monitor2-lx:~ # tcpdump -i eth0 host 10.35.178.154
 >>tcpdump: listening on eth0
 >>08:37:08.065489 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de:
 >>icmp: echo request (DF)
 >>08:37:08.066027 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de:
 >>icmp: echo reply
 >>08:37:08.280371 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: S 521852342:521852342(0) win 5840 <mss
 >>1460,sackOK,timestamp 196151735 0,nop,wscale 0> (DF)
 >>08:37:08.281148 arp who-has monitor2-lx.mobilcom.de (0:50:8b:e2:2e:b3)
 >>tell mccg-lx-rilo.mobilcom.de
 >>08:37:08.281171 arp reply monitor2-lx.mobilcom.de is-at 0:50:8b:e2:2e:b3
 >>08:37:08.281564 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: S 693771910:693771910(0) ack 521852343
 >>win 5840 <mss 1460>
 >>08:37:08.281620 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 1 win 5840 (DF)
 >>08:37:08.281827 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: P 1:92(91) ack 1 win 5840 (DF)
 >>08:37:08.285304 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 1:16(15) ack 92 win 5840
 >>08:37:08.285322 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 16 win 5840 (DF)
 >>08:37:08.285995 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 16:18(2) ack 92 win 5840
 >>08:37:08.286007 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 18 win 5840 (DF)
 >>08:37:08.286883 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 18:41(23) ack 92 win 5840
 >>08:37:08.286896 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 41 win 5840 (DF)
 >>08:37:08.287544 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 41:43(2) ack 92 win 5840
 >>08:37:08.287556 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 43 win 5840 (DF)
 >>08:37:08.288390 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 43:81(38) ack 92 win 5840
 >>08:37:08.288411 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http: . ack 81 win 5840 (DF)
 >>08:37:08.289048 mccg-lx-rilo.mobilcom.de.http >
 >>monitor2-lx.mobilcom.de.57412: P 81:83(2) ack 92 win 5840
 >>08:37:08.289211 monitor2-lx.mobilcom.de.57412 >
 >>mccg-lx-rilo.mobilcom.de.http:



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null