"network adapter link down"

[Network Administrator_15]

I have a Proliant ML350 running Windows 2000 Server.

I keep getting the following message every day few days in my Compaq Integrated Management Log Viewer:
"Network Adapter Link Down (Slot 0, Port 1)
Severity: Repaired"

The Repaired update comes through about 2 minutes after the "link down" alert.

Additionally, every time this happens I get the following messages in my Windows System Log:

Server event log:

Event Type: Information
Event Source: q57w2k
Event Category: None
Event ID: 4
Description:
Compaq NC7760 Gigabit Server Adapter: The network link is down. Check to make sure the network cable is properly connected.
~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Error
Event Source: NIC Agents
Event Category: Service
Event ID: 1285
Description:
Compaq NIC Agent: Connectivity has been lost for the NIC in slot 0, port 1. [SNMP TRAP: 18006 in CPQNIC.MIB]
~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4202
Description:
The system detected that network adapter Compaq NC7760 Gigabit Server Adapter was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers.
~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: q57w2k
Event Category: None
Event ID: 9
Description:
Compaq NC7760 Gigabit Server Adapter: Network controller configured for 100Mb full-duplex link.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Description:
The system detected that network adapter Compaq NC7760 Gigabit Server Adapter was connected to the network, and has initiated normal operation over the network adapter.
~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: NIC Agents
Event Category: Service
Event ID: 1284
Description:
Compaq NIC Agent: Connectivity has been restored for the NIC in slot 0, port 1. [SNMP TRAP: 18005 in CPQNIC.MIB]

Any suggestions for what this might be and how to solve it would be appreciated.

Thanks,
Kellie

[Yaniv Amrami]

Hi,

I've got the same issue as well.
My HP DL360 G3 is rebooting w/o any notification.
I can see the same error messsages in my Event Viewer and inside the Compaq Integrated Management Log Viewer...

Any info??

[Ernest Ford]

Yaniv,

Sounds like you have a different issue - I don't see Kellie mention that her server is rebooting.

Kellie's problem is related to the NIC possibly a defective cable, possibly someone unplugging/replugging the cable somewhere. In fact it reminds of one I had with a workstation in my home office - my daschund sleeps under my desk, behind my PC and everytime she shifts position I would get a disconnect/reconnect message. Problem was a bad cable.

Look in your event log for messages related to the reboot. 2KServer usually logs messages relating to the startup and stopping of the event log service - as well as messages that tell you when an unexpected shutdown occurs - if you're not seeing this last one, then you server is being shutdown in a controlled fashion.

If you are seeing it - then start looking at the hardware - it ranges from something as simple as unreliable power to memory or processor problems.

If you want help troubleshooting the reboot problem I suggest you repost your question in the ProLiant Server forum rather than this "communications, wireless" forum.

If you are in fact seeing the same messages in your event log, correct your reboot problem and then start by checking your physical cable plant.

Repost the question rather than revive a six month old dead question.

[Andre Fontes]

Try the following:
Start > Control Panel > HP Management Agents and deactivate "NIC Information" Agent that may have be enabled by default... Once you disable you may not see any difference, so start the agent again.. You will see the network link recovering its connection..Once the connection is up, disable the "NIC Information" Agent and the connection will stop bouncing. It worked for me.. Until now I have 4 days of persistent network connection without any bouncing.. :]
Andre Fontes