nanog mailing list archives

Re: Super slow HP ILO 2 web interface


From: Jay Ashworth <jra () baylink com>
Date: Thu, 24 Jan 2013 12:20:28 -0500 (EST)

This assumes that your ILOs aren't on their own VLAN, which they 
really ought to be; mine were...

Cheers,
-- jra

----- Original Message -----
From: "Michael Loftis" <mloftis () wgops com>
To: "Erik Levinson" <erik.levinson () uberflip com>
Cc: "nanog" <nanog () nanog org>
Sent: Thursday, January 24, 2013 2:34:14 AM
Subject: Re: Super slow HP ILO 2 web interface
I've had issues with HP, Dell, and Super micro in any higher amounts
of
broadcast traffic, especially ARP requests. The iDRAC 5 and 6 behave
very
badly in high broadcast environments, failing to respond to http and
local
ipmi (ipmitool via the smbus or whatever) interface. That's probably
where
I would start personally...anything over a couple hundred hosts in the
same
broadcast domain, especially if those are windows or osx hosts that
love to
jibber about CIFS and mDNS.

--------------------

Sent from my Motorola Xoom
On Jan 23, 2013 6:25 PM, "Erik Levinson" <erik.levinson () uberflip com>
wrote:

Hi everyone,

This is probably an OT question for this list, but I thought someone
here
may have encountered this.

I've been having a really annoying super slow web interface access
to ILO
2 on our DL360 G5s and G6s, since day one, on all of them. SSH to
ILO is
perfectly fine. IPMI is fine. VSP is fine. Everything to do with ILO
is
fine except the damn web interface, which is slow to load pages
intermittently. It kind of works in bursts for a few seconds when it
works,
so I try to do things quickly. It's hard to characterize exactly
what's
happening beyond my vague description, but I've looked at the dev
tools in
Chrome, tried FF, etc. with no luck.

One thing I haven't tried in a while is a packet capture of an ILO
port to
see if it's doing something weird, like trying to do rDNS on the
client's
IP or on itself, etc.

If it helps, our config doesn't use DHCP and otherwise all the boxes
are
reset to defaults, then have their IP/SM/GW configured and local
users
configured...nothing fancy. We do use our own SSL certs, but the
problem
happens without them as well, so I've already ruled that out.


Does anyone have any ideas on what obvious thing I could have
missed?


Thanks

Erik





-- 
Jay R. Ashworth                  Baylink                       jra () baylink com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274


Current thread: