Onboard Administrator 2.20 Looses connectivity

[Deon Roos]

I am currently running OA version 2.20 with all my blades running ilo version 1.50.

I keep having to reset the OA as the system becomes unreachable.

I am having this problem with 2 enclosure's.

Anyone else experienced this problem? If so is it a bug in OA Firmware or something else?

[JKytsi]

Hi,
If You have reduntant OAa try to run with only one.

[Deon Roos]

Hi Jarkko

I am only using one OA.

Thanks

[JKytsi]

and no network issues between your managament computer and the OA ? does it disconnect if You attach your laptop directly to OA

[Deon Roos]

It seems like it disconnects over night.

Im going to see if there is network errors on the port. Usually this happens with Speed / Duplex negotiation on the switches.

I will check and let you know. I know with the new Firmware you can force this to 100MB/Full.

Will check and let you know.

Tx

[Deon Roos]

I did some basic troubleshooting and discovered the following -

Jun 4 13:30:48 Kernel: Network link is up at 100Mbps - Half Duplex
Jun 4 13:30:48 OA: Time zone changed to CDT+5
Jun 4 13:30:50 OA: LCD Status is: OK.
Jun 4 13:30:52 Enclosure-Link: Service started
Jun 4 13:30:52 OA: Onboard Administrator booted successfully
Jun 4 13:30:54 OA: Blade 1 is reporting nominal health status.
Jun 4 13:30:55 OA: Blade in bay #1 status changed to OK
Jun 4 13:30:58 OA: Blade 2 is reporting nominal health status.
Jun 4 13:30:59 OA: Blade in bay #2 status changed to OK
Jun 4 13:31:00 OA: Blade 3 is reporting nominal health status.
Jun 4 13:31:01 Enclosure-Link: Initial topology scan completed successfully
Jun 4 13:31:03 OA: Blade in bay #3 status changed to OK
Jun 4 13:31:03 OA: Blade 4 is reporting nominal health status.
Jun 4 13:31:04 OA: Blade in bay #4 status changed to OK
Jun 4 13:31:08 OA: Blade 5 is reporting nominal health status.
Jun 4 13:31:08 OA: Blade in bay #5 status changed to OK
Jun 4 13:31:12 Redundancy: Service started (ACTIVE)
Jun 4 13:31:12 OA: Blade 6 is reporting nominal health status.
Jun 4 13:31:12 OA: Blade in bay #6 status changed to OK
Jun 4 13:31:15 OA: Blade 7 is reporting nominal health status.
Jun 4 13:31:16 OA: Blade in bay #7 status changed to OK
Jun 4 13:31:19 OA: Blade 8 is reporting nominal health status.
Jun 4 13:31:20 OA: Blade in bay #8 status changed to OK
Jun 4 13:31:23 OA: Blade 9 is reporting nominal health status.
Jun 4 13:31:24 OA: Blade in bay #9 status changed to OK
Jun 4 13:31:25 OA: Blade 10 is reporting nominal health status.
Jun 4 13:31:26 OA: Blade in bay #10 status changed to OK
Jun 4 13:31:28 OA: Blade 11 is reporting nominal health status.
Jun 4 13:31:28 OA: Blade in bay #11 status changed to OK
Jun 4 13:31:30 OA: Blade 12 is reporting nominal health status.
Jun 4 13:31:30 OA: Blade in bay #12 status changed to OK
Jun 4 13:31:31 OA: Blade 13 is reporting nominal health status.
Jun 4 13:31:32 OA: Blade in bay #13 status changed to OK
Jun 4 13:31:36 OA: Blade 14 is reporting nominal health status.
Jun 4 13:31:37 OA: Blade in bay #14 status changed to OK
Jun 4 13:31:41 OA: Blade 15 is reporting nominal health status.
Jun 4 13:31:41 OA: Blade in bay #15 status changed to OK
Jun 4 13:31:45 OA: Blade 16 is reporting nominal health status.
Jun 4 13:31:46 OA: Blade in bay #16 status changed to OK
Jun 4 13:32:50 OA: Administrator logged into the Onboard Administrator
Jun 4 13:33:00 OA: Administrator logged into the Onboard Administrator
Jun 4 13:43:08 OA: Administrator logged out of the Onboard Administrator
Jun 4 14:12:12 Kernel: Network packet flooding detected.
Jun 4 14:12:13 Kernel: Network packet flooding detected.
Jun 4 14:12:17 Kernel: Network packet flooding detected.
Jun 4 14:12:26 Kernel: Network packet flooding detected.
Jun 4 14:12:41 OA: Administrator logged into the Onboard Administrator
Jun 4 14:12:41 Kernel: Network packet flooding detected.
Jun 4 14:13:11 Kernel: Network packet flooding detected.
Jun 4 14:13:41 Kernel: Network packet flooding detected.
Jun 4 14:15:06 OA: Network Interface link forced to 100Mbps - Full Duplex by u
ser Administrator.
Jun 4 14:15:09 Kernel: Network link is up at 100Mbps - Full Duplex

It seems like the OA Automatically Sets the Network Card to 100 Half Duplex. For some reason i find this very strange as the port on the switch is set to 100 Full Duplex Forced.

I will monitor this and let you know if this was the problem.

[Raghuarch]

Is the OA connected to 1GB Switch or is it connected through the Hub.
If it is through the HUB. I suggest you to change it to Switch.

When you have large amount of Network activity OA showws that "Network packet flooding" is there any big file downloaded from the network it may cause that behaviour.

[Deon Roos]

The Onboard Administrator can only handle up to 100Mb its connected straight to the switch. There should be nothing besides SNMP traps and GUI Administration going across this link.

[Lawrance Lee_1]

I do not know the technical reason why but the Onboard Administrator port works best at 100 Mbit HALF duplex.

You should check the switch that the OA is connected to, and ensure that it is also set to 100 Mbit half dup.

[Deon Roos]

Thanks for the info.

Seems like the new firmware + all the ilo's update and forcing the speed to 100MB/Full works fine.

Its just very weird that it works better on 100/Half. Very good for people to know.