ILO2 Disabled and Can't enable on DL380-G6 - anyone else?

[Wallace H Wyeth]

Please post your case number so I can share it with the engineers working our case.

Thanks,

[JPM79]

My case # is 4614588237. I ended up speaking with a supervisor and they agreed to elevate the case, but since they believe it is a network issue they promised nothing. Thanks.

[Kedd Guyton]

I noticed that you've tried updating the iLO 2 firmware to v1.82, but have you tried also updating the iLO 2 Management Controller driver to v1.12.0.0 (or later)?

The Event ID 57 is also mentioned in the HP advisory:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01802766&dimid=1053525778&dicid=alr_apr10&jumpid=em_alerts/us/apr10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts

[JPM79]

On our DL360 G6's I have upgraded the system BIOS to 2010.03.30, the iLO2 firmware to 1.82, the HP ProLiant Integrated Lights-Out Management Interface Driver to 1.15.0.0B, and the HP ProLiant iLO 2 Management Controller Driver to 1.13.0.0, with no luck. The issue also affects our VMWare vSphere 4 servers, for which no driver updates are available/applicable.

[JPM79]

We managed to resolve our issue by tracing the problem down to a bad Cisco SD2005 unmanaged switch plugged in to a port on our core Cisco 6513 on the native VLAN.  We only found this by methodically isolating components of our network.  We began by isolating our access switches from our core switch to rule them out one by one.  We then went through and began disabling groups of ports on the 6513 until we identified the port range that the problem was coming from.  From there, we identified each device on the problem range and went about disabling each port one by one until we found the culprit.  The port on the core switch gave no indiciations that there were any troubles and the devices on the SD2005 were functioning fine.

GigabitEthernet5/17 is up, line protocol is up (connected)
  Hardware is C6k 1000Mb 802.3, address is 001e.be89.5368 (bia 001e.be89.5368)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
  input flow-control is off, output flow-control is on
  Clock mode is auto
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:26, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 6000 bits/sec, 9 packets/sec
     190225 packets input, 15654604 bytes, 0 no buffer
     Received 168431 broadcasts (5370 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 2 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     1427293 packets output, 136340580 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

[Wallace H Wyeth]

That is very interesting.  I will look for possible correlations in our network.

We can avoid the issue by movling the ILO connections to an older HP switch rather than plugging them directly to the 5412.