Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Careers | About Us | Contact Us|

Bob Lin Photography services

Real Estate Photography services 


Event ID 434 - HP Network Team #1: PROBLEM

Situation: 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


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.


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   ........

Resolution: Yes, add enabling FastPort fixes it. These are the steps:

1. Conf t.

2. interface FE 0/##

3. spanning-tree portfast

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics


Bob Lin Photography services

Real Estate Photography services 


  This web is provided "AS IS" with no warranties.
Copyright © 2002-2017 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.