Unsolved
This post is more than 5 years old
13 Posts
0
1715
Tandom NIC Indicator Code on PE1950
I have a PowerEdge 1950. Though the course of trying to troubleshoot some network issues after a physical move, I found that one of the PE1950's has one NIC that blinks both the green link and orange status codes in tandom about 12 (maybe 11) times, slower than a traffic indicator would blink. It pauses then starts again.
The other NIC on the same server is showing normal status lights.
I can ping to another server attached to the same VLAN it's on.
I've searched, but can't find anything referencing this type of indicator code.
Thanks in advance for any ideas.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
July 19th, 2016 14:00
Hello.
What Operating System and model of the Network cards? Ensure the NIC drivers and firmware is up to date and speed/duplex on the NIC and switch are set to the same parameters.
CFJSGeek
13 Posts
0
July 20th, 2016 16:00
I'm not seeing where you can enable that in OMSA, but it says it's not TOE Capable - so I don't think I'd be able to enable it anyway since it'd have to be capable.
theflash1932
9 Legend
9 Legend
•
16.3K Posts
0
July 20th, 2016 16:00
Each port can have TOE enabled/disabled independently in the BIOS (or through OMSA with a reboot).
CFJSGeek
13 Posts
0
July 20th, 2016 16:00
I did find the firmware versions in OMSA though:
#0 b8c2 7.4.0, UMP 1.1.9, ipmi 1.06, iSCSI v7.10.4
#1 b8c2 7.4.0, b8c2 7.4.0, ipmi 1.06 (missing the iSCSI like we see on #0)
CFJSGeek
13 Posts
0
July 20th, 2016 16:00
The operating system is Windows Server 2008 R2 Standard.
The NIC cards are on-board Broadcom BCM5708C NetXtreme II Gige (LOM).. Device manager reports Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) (drive 7.10.6.0)
They are connected via Gigabyte connection at the moment, but the interface will blink that even when the cable is not connected. So this doesn't appear to be any sort of link/switch issue.
According to OME, everything checks out and System Updates don't ask for updates.
I do notice however, even though they are the exact same onboard NIC, OME reports that NIC #0 has TOE capability, and is enabled, while NIC #1 (that is blinking) doesn't have TOE capability.
CFJSGeek
13 Posts
0
July 20th, 2016 18:00
I'm not familiar with a TOE key, but it's the same machine, same motherboard, side-by-side interface.
theflash1932
9 Legend
9 Legend
•
16.3K Posts
0
July 20th, 2016 18:00
Yeah, the TOE key would have to be installed ... I thought you said TOE was enabled on one port but not the other. On one machine but not the other maybe?
theflash1932
9 Legend
9 Legend
•
16.3K Posts
0
July 20th, 2016 19:00
Might check the BIOS on the next reboot if it isn't showing correctly in OMSA (I'm assuming). Are you using CLI or the GUI?
CFJSGeek
13 Posts
0
July 21st, 2016 10:00
I'm using the GUI. Do you think the TOE being off has to do with the blink status it's showing?