cancel
Showing results for 
Search instead for 
Did you mean: 

NIC Teaming

 
Aravind Sri
Occasional Advisor

NIC Teaming

Server Configration:

HPDL380,Windows 2003 R2 SP2

Network Cards:
NC380T Dual port Mutlifuntional NIC.
NC373I Dual Port.
NIC Driver: Broad COm 3.7.19.0 Relased 04/10/2007.

Problem:

Created one Team .

Team1: NC380T port 1 and NC373i port 2
Teaming Mode: Automatic.

Both the ports Oscillate between degraded(RX Path) to No Fault Status.

I am able to ping the team at all times.

Solutions Tried:

Upgraded NCU from 8.60 to 9.0
Updated NIC driver from 3.07.0 to 3.7.19.0
Tried different combinations of teams.
Uninstalled NIC and reinstalled NIC from the device manager.
Disolved and formed teams again.
Check cables and switch configgration.
Used NCU diagnostic tools. Nothing reported.

How can I solve this? Thank you for your replies
11 REPLIES
KarloChacon
Honored Contributor

Re: NIC Teaming

Hi

I suppose that a DL380 G5? Am I right?

so your teaming one port for the embedded card and another port for a PCI Card right?

and the error you having is
"Both the ports Oscillate between degraded(RX Path) to No Fault Status"

where are you getting that from NCU diagnostics test?

any error on Windows Event viewer?

regards

Didn't your momma teach you to say thanks!
KarloChacon
Honored Contributor

Re: NIC Teaming

hi

let me ask you something else

do you get the same errors if you team both ports for the same NIC CARD NC373i or NC380T?

regards
Didn't your momma teach you to say thanks!
Aravind Sri
Occasional Advisor

Re: NIC Teaming

This is DL380G5.


"so your teaming one port for the embedded card and another port for a PCI Card right?"
Yes

'and the error you having is
"Both the ports Oscillate between degraded(RX Path) to No Fault Status"'
Yes

where are you getting that from NCU diagnostics test?
The Diagnostic test is for every port on each adapter. It's tab on the adpater properties window.
The checks the following"
Control Registers
MII registers
Memory
Interrupt
LoopBack CPU.



any error on Windows Event viewer?
Yes. The event viewer reports.

"TS: PROBLEM: A Failover occurred: The Primary Network Link is down. ACTION: Please check your cabling or switch port status, or run diagnostics to test card. Also make sure all teamed NICs are on the same network."

I have tried all the recommeded solutions suggested by the event viewer none seems to have solved the problem.

Thanks for your assitance.
Phil.Howell
Honored Contributor

Re: NIC Teaming

There seems to be a problem with windows server 2003 sp2 and the NC373i adapters.
see
http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1153566

Phil
KarloChacon
Honored Contributor

Re: NIC Teaming

hi

can you add source and event Id for those errors in order to get information abhout the issue.

---

what about teaming same NIC cards each other? I mean same ports for same NIC CARD, same issue?
just for test purposes


regards
Didn't your momma teach you to say thanks!
Aravind Sri
Occasional Advisor

Re: NIC Teaming

I forgot to add it in my last response, my bad: 434. Thanks Karlo and Phil
Aravind Sri
Occasional Advisor

Re: NIC Teaming

I forgot to add it in my last response, my bad.

EVENT ID:434.
SOURCE: CPQTEAMMP


Thanks Karlo and Phil
KarloChacon
Honored Contributor

Re: NIC Teaming

hi

Enable Fast-port On switch(es) port to resolve the issue.

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

Re: NIC Teaming

Hi,

Just in case, if Karlo's suggestion is not the answer :
1. Dissolve the team.
2. Stop Tcp Offload Engine & Receive Side Scaling from the NCU for each NIC and recreate the team.
3. Stop RSS & TOE for the team.

Pac
Aravind Sri
Occasional Advisor

Re: NIC Teaming

Karlo, I have it connected to an Extreme Summit24e series switch.I have checked all port configrations. I have enabled fast port forwarding.

But I still have the problem.

I will definitely try your suggestion Pac

Re: NIC Teaming

we have had this problem alot lately , try using old drivers for the nc3731 we roled back to cp007290.exe which is 3.0.5.0 and this solved the problem we are currently working on a fix for the new drivers.

hope this works