Windows Server 2003
1833750 Members
2710 Online
110063 Solutions
New Discussion

Re: COQTeamMP event id 434

 
Lai Siew Yuen
Frequent Advisor

COQTeamMP event id 434

Hi,
I have a HP Proliant G3 server running Windows 2003 with SP2. Thre are numerous system event log (id=434) when the system reboot. The description is "HP Network Team #1: PROBLEM: A non-Primary Network Link is not receiving. Receive-path validation Heartbeat setting. ACTION: Please check your cabling to the link partner....". This server is a mutihomed machine and all the NIC are teamed. The driver for network cards - model NC7781 IS 10.42, & model NC7170 is 8.10.1.0. HP PSP version is 7.9.1 & HP Network Configuration Utility version is 8.80.0.12. The problem with this server is that it can't ping its neighbour's IP (vice versa) but it can ping some other nodes on a different subnet. Occassionally I can't connect to this node via Terminal service too (although my current TS session stay connected). May I know anyone has any idea to resolve this problem. I've attached some screenshots for your investigation.
Some additional info: There is another server with similar setup (in terms of network & OS) that do not display such symptom. Both servers are connected to the same switches.
Thanks in advance for any help in this matter.
7 REPLIES 7
KarloChacon
Honored Contributor

Re: COQTeamMP event id 434

hi

have you swapped cables and ports between the server that has the issue and the one that does not and it is working fine??

apply latest PSP 8.0 in order to update drivers and NCU

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=316529&prodNameId=3288130&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=MTX-6f78c741679b4ec7a6ff1198ba

also apply latest Firmware CD 8.0
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=MTX-6e09964448994337ad23016691&jumpid=reg_R1002_USEN

regards
Didn't your momma teach you to say thanks!
Lai Siew Yuen
Frequent Advisor

Re: COQTeamMP event id 434

Hi Karlo,
Thanks for your kind advice. In fact I have break the team and have noticed that the problem is only observed on the card "NC7170". I wonder could it be the card's fault? Do let me know if you think otherwise. Also I have quite a number of DL380 G3 which have the same PSP installed but do not show such symptom.
At the mean time, pls allow me more time to download and try out the patches as your advice.
Best Regards.
KarloChacon
Honored Contributor

Re: COQTeamMP event id 434

hi Lai

"I wonder could it be the card's fault?"

it can be you know but first update everything and also if you have the chance to try that card in another server would be great

regards
Didn't your momma teach you to say thanks!
Pieter 't Hart
Honored Contributor

Re: COQTeamMP event id 434

Are the NIC's connected to the same network device?
Is this the same brand/type as the correctly working servers?
Are both ports configured the same?

The HP-teaming when configured as "auto" tries to negotiate with the connected switch (ieee 802.3ad).
It should be investigated if this negotiation is succfull.

please look at the team details.
like in attached example
Pieter 't Hart
Honored Contributor

Re: COQTeamMP event id 434

here the example
Pieter
Lai Siew Yuen
Frequent Advisor

Re: COQTeamMP event id 434

Hi Pieter,
Thanks for your reply. The NICs are connected to different switches for redundancy. It is connected in the same manner as another server (with similar setup) that doesn't exhibit such symptom. Both NIC cards port speed is also set to 100 Full Duplex (as in the switch).
I've noticed one strange behavious on the problematic server. The status of the team becomes 'Failed' or 'Degraded' intermittently. Kindly see my attached screen shot.
Best Regards.
Pieter 't Hart
Honored Contributor

Re: COQTeamMP event id 434

from your screenshots you can see the teaming is configured as automatic.
The server with similar setup also has two different nic models ? if so apart from a possible faulty nic I would guess the cause outside this server.
can you check the config of the switchports?

To check the nic :
- You have two unteamed NIC's, you can try to swap one with the current 7170 and see if the problem remains.
- another option is to switch to NFT (just redundant, no load balancing) and connect the nic's one at a time.
- or as the suggestion from the reported eventlog entry: unteam and check the NIC as single connection)?