HP Network Team #1: PROBLEM

[msworld]

I just installed Windows 2003 R2 on HP DL380 G5. After I create NIC teaming, the server receives the following Event ID 434. I have called the HP tech support and upgrade all BIOS and drivers. I also upgraded the Windows SP1 and 2. I have changed the cables and tried different ports. I read one post in the internet states “enabling FastPort on a Cisco switch resolves this warning”. The below is the switch configuration. Do I need to make any changes on my switch? The reason I ask is that I have other 3 HP servers running teaming on the same switch with the same configuration without problem. Any suggestions?

interface GigabitEthernet0/27
!
interface GigabitEthernet0/28

Event Type: Warning
Event Source: CPQTeamMP
Event Category: None
Event ID: 434
Date: 7/31/2007
Time: 5:37:26 PM
User: N/A
Computer: CBGDATA2
Description:
HP Network Team #1: PROBLEM: A non-Primary Network Link is not receiving. Receive-path validation has been enabled for this Team by selecting the Enable receive-path validation Heartbeat Setting. ACTION: Please check your cabling to the link partner. Check the switch port status, including verifying that the switch port is not configured as a Switch-assist Channel. Generate Broadcast traffic on the network to test whether these are being received. Also make sure all teamed NICs are on the same broadcast domain. Run diagnostics to test card. Drop the NIC from the team, determine whether it is receiving broadcast traffic in that configuration.
Data:
0000: 00 00 00 00 02 00 58 00 ......X.
0008: 00 00 00 00 b2 01 04 80 ....²..?
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

 

[burtsbees]

Try a sniffer---can you unteam the NICs and see what kind of speeds you are getting? Portfast on a Cisco switch is usually beneficial for a switchport to come right up in an STP environment---it looks like the dl380 is complaining about excessive traffic, perhaps broadcasts. Without more info on the topology and protocols, like routing protocols, VTP, VTP pruning, etc., it is hard to say. A sniffer will immediately let you know about any excessive broadcast traffic---though other dl380's are teamed and going to the same switch without problems, if the one with problems is on a separate VLAN (if configured), then this separates the broadcast domain from the other VLANs, and hence the problem server can get broadcast traffic that the other servers won't see, like I said, if they are on different VLANs.

Burt

 

[jdeisenm]

Presuming you are not doing trunking. Add these commands to your cisco switch. As burtb suggested, I'd check the speed and duplex settings on each nic on the server and the switch. I've seen problems recently where one of the server nics was bad but would not fail over. So, without the team, make sure that each nic can operate independently. Check each switch port and each server nic for errors also.

interface GigabitEthernet0/27
spanning-tree portfast
!
interface GigabitEthernet0/28
spanning-tree portfast