HP NC7761 NIC card disconnecting for no reason

[rick jones]

How many people have physical access to the switch(es) and/or NICs in the servers?

If it were part of a regularly scheduled thing in a server or switch I'd expect a much tigher time range.

I wouldn't _expect_ spanning tree to cause a link to show down, but am wondering if perhaps there is someone who arrives each day in that timeframe who say powers-up a switch or something?

[Kimberly Joyner]

There are no other switches besides those in the locked network closet. No one has access besides me. There are two or three people who come in that early, one has been here every time the network has blimped off. She says it happened the last time about 20 minutes after she arrived when she was printing documents. She uses two printers and she prints to them and they wake up from being on "sleep" mode. She did not come in early this morning but she did print to the same two computers and they were fine and the network did not blip off.

[rick jones]

Anyone have a switch in their office/cubicle?

[Kimberly Joyner]

No other switches on the network besides the three in the network room.

[rick jones]

Looks like there was a gap longer than a weekend in that series of entries you posted. Anything "special" about that timeframe?

It may come down to starting to packet trace during the timeframe in question.

[Kimberly Joyner]

Nothing special I can think of, and it did not happen this morning.

[Joshua Small_2]

Three different brands of switches never makes things easy.

If only one person is usually in that early, you could try..

Ensuring the servers and that person are on one switch. I would probably suggest the Linksys would be the better of them.

Disconnect your uplink cable. Have someone manually plug it in at the time people all start working.

See if you experience any issues at this point, and you can rule out the 3Com and Netgears.

Whilst doing this, I would also check the firmware on the Linksys and check what logging options it has.

[Kimberly Joyner]

Ther server crashed on Sunday morning and I found this error:

Event Type: Error
Event Source: HP Ethernet
Event Category: Network Device
Event ID: 2
Date: 3/9/2008
Time: 11:22:29 AM
User: N/A
Computer: POS-SBS
Description:
A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state.

User Action
Check the network cables, switches, and hubs for the cause of the failure.

WBEM Indication Properties
AlertingElementFormat: 2 0x2 (CIMObjectPath)
AlertingManagedElement: "\\POS-SBS\ROOT\HPQ:HP_WinEthernetPort.DeviceID="{8FE0B141-72EE-45C6-815D-2F507A07EA74}",CreationClassName="HP_WinEthernetPort",SystemCreationClassName="HP_WinComputerSystem",SystemName="POS-SBS.pos.local""
AlertType: 2 0x2 (Communications Alert)
Description: "A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state."
EventCategory: 9 0x9 (Network Device)
EventID: "2"
EventSubCategory: 11 0xb (Ethernet Port)
ImpactedDomain: 4 0x4 (System)
IndicationIdentifier: "{46C61C67-63D1-47BC-A92B-69D975B30536}"
IndicationTime: "20080309112220.359000-240"
NetworkAddresses[0]: "192.168.207.1"
NetworkAddresses[1]: "192.168.207.118"
OSType: 69 0x45 (Microsoft Windows Server 2003)
OSVersion: "5.2.3790"
PerceivedSeverity: 6 0x6 (Critical)
ProbableCause: 7 0x7 (Communications Subsystem Failure)
ProbableCauseDescription: "Network Interface Lost Connectivity"
ProviderName: "HP Ethernet"
ProviderVersion: "2.1.0.0"
RecommendedActions[0]: "Check the network cables, switches, and hubs for the cause of the failure."
Summary: "Network interface lost connectivity"
SystemCreationClassName: "HP_WinComputerSystem"
SystemFirmwareVersion[0]: "2005.08.19"
SystemFirmwareVersion[1]: "2005.08.19"
SystemGUID: "31303833-3337-5355-4d36-303530323154"
SystemModel: "ProLiant ML350 G4p"
SystemName: "POS-SBS.pos.local"
SystemProductID: "380173-001"
SystemSerialNumber: "USM605021T"
TIME_CREATED: 128495497490312500 0x1c881f96325ad34
UserComment: "2"

For more information, please contact HP Support.


I ran a diagnostic on the card and the server locked up. I rebooted and ran the diagnostic again and it came out fine.

Now I'm even more confused.

[Kimberly Joyner]

This is the reboot message I received:

Event Type: Error
Event Source: HP System
Event Category: System Power
Event ID: 1
Date: 3/9/2008
Time: 11:05:10 AM
User: N/A
Computer: POS-SBS
Description:
The system has rebooted from a Automatic Server Recovery (ASR) event.

User Action
Determine the nature of the Automatic Server Recovery (ASR) event, and take corrective action.

WBEM Indication Properties
AlertingElementFormat: 0 0 (Unknown)
AlertType: 5 0x5 (Device Alert)
Description: "The system has rebooted from a Automatic Server Recovery (ASR) event."
EventCategory: 16 0x10 (System Power)
EventID: "1"
ImpactedDomain: 4 0x4 (System)
IndicationIdentifier: "{A220DD2E-7B44-48C2-8E03-945EF327BDEB}"
IndicationTime: "20080309110506.281000-240"
NetworkAddresses[0]: "192.168.207.1"
OSType: 69 0x45 (Microsoft Windows Server 2003)
OSVersion: "5.2.3790"
PerceivedSeverity: 5 0x5 (Major)
ProbableCause: 111 0x6f (Timeout)
ProbableCauseDescription: "ASR Reboot Occurred"
ProviderName: "HP Recovery"
ProviderVersion: "2.1.0.0"
RecommendedActions[0]: "Determine the nature of the Automatic Server Recovery (ASR) event, and take corrective action."
Summary: "ASR reboot occurred"
SystemCreationClassName: "HP_WinComputerSystem"
SystemFirmwareVersion[0]: "2005.08.19"
SystemFirmwareVersion[1]: "2005.08.19"
SystemGUID: "31303833-3337-5355-4d36-303530323154"
SystemModel: "ProLiant ML350 G4p"
SystemName: "POS-SBS.pos.local"
SystemProductID: "380173-001"
SystemSerialNumber: "USM605021T"
TIME_CREATED: 128495487102343751 0x1c881f6f7f9da47

For more information, please contact HP Support.

[tonym_2]

I am experiencing the same problem with a NIC card on Proliant ML350 G4p.It seems to happen late at night and early morning according to event viewer logs.
So far we have done the following with the help of HP Support.
1. Updated firmware for both BIOS and Network
2. Updated drivers
3. Removed the second Processor and PPM to see whether this has an effect.
I will update ehat happens next as problem bot yet resolved.