Networker

Re: [Networker] AW: [Networker] --- TCP/IP crash with GIGABIT ---

2002-08-06 14:43:22
Subject: Re: [Networker] AW: [Networker] --- TCP/IP crash with GIGABIT ---
From: Charles Walther <CWalther AT SAROFIM DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 6 Aug 2002 13:28:23 -0500
In order to remain supportable via Compaq, I would take their recommended
course of action first,  if it does not resolve the issue, then try the
INTEL driver.


My two cents !

Charlie Walther


-----Original Message-----
From: Gudz, Roman (CAP, PTL) [mailto:Roman.Gudz AT penske DOT com]
Sent: Tuesday, August 06, 2002 1:23 PM
To: 'Legato NetWorker discussion'; 'Charles Walther'
Subject: RE: [Networker] AW: [Networker] --- TCP/IP crash with GIGABIT ---


Two weeks ago, we migrated one of our NetWorker Servers to a Compaq DL580
with the NC7131.  We are running Windows 2000 and NetWorker 6.1.2 and are
experiencing the same symptoms.  I have read the Compaq advisory
CO010308_CW04, should we follow the resolution pointed out there or should
we use the Intel driver?

Thanks, Roman Gudz

-----Original Message-----
From: Charles Walther [mailto:CWalther AT SAROFIM DOT COM]
Sent: Tuesday, August 06, 2002 1:49 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] AW: [Networker] --- TCP/IP crash with GIGABIT
---


Same here,   we upgraded in January to 6.1.1 under W2K on the Compaq
Proliant 570.  The Fiber GB cards would drop out after any substantial load
was placed on them.  Our solution was the same,  use the INTEL drivers.   We
lost our capability to use copper as a teaming pair, but Legato now moves
pretty good.

Charlie Walther


-----Original Message-----
From: Fowler, Carter [mailto:CFowler AT CITY.LONDON.ON DOT CA]
Sent: Tuesday, August 06, 2002 11:48 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] AW: [Networker] --- TCP/IP crash with GIGABIT ---


Ivan;

We have a Proliant ML370G2 and were using the NC6134.  We discovered a very
similar behavior to what you describe.  We uninstalled the Compaq drivers
and installed the Intel drivers and this resolved the issue.   When we
reported this behavior to Compaq, they eventually came up with a single
registry entry that Intel uses but Compaq does not.  I believe that Compaq
now has this problem resolved.  We were the first to bring this behavior to
Compaq's attention about 5 months ago, at least in this area.  The created a
new driver set which should address this issue, however, we are still using
the Intel drivers.

Good luck,

Carter Fowler
Hardware Service Technician
The City Of London
600 - 380 Wellington Street
London, ON, CA, N6A 5B5
Off: 519.661.5711
Cel: 519.870.4956
Em: cfowler AT city.london.on DOT ca

-----Original Message-----
From: ivan.mason AT OTAGO.AC DOT NZ
Sent: Tuesday, August 06, 2002 8:43 AM
To: ivan.mason AT OTAGO.AC DOT NZ; NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: AW: [Networker] --- TCP/IP crash with GIGABIT ---

We have a simuler problem, I posted the following on a Compaq forum... (I
don't understand why I only have the problem when running backups on the
Networker server?)

Compaq ML530G2 running Legato NetWorker 6.1.1 losing network connectivity
with NC7131 Gigabit NIC

Both the internal NC3163 Fast Ethernet NIC and the NC7131 report a high
*Receive Overrun* count when under load, when using the Gigabit NIC the
network interface will sometimes go dead (escalating *Receive
Overruns*) and then recover, this may last for seconds at a time. It will
eventually stop all together again only reporting escalating *Receive
Overruns*.

When this happens the interface goes completely dead (continuous pinging
confirms this along with performance monitoring of the interface traffic)

This is a new installation of the server Compaq Smart Start 5.40 + Windows
2000 + SP2 + Legato NetWorker 6.1.1

I have tested this system configuration on a DL360 G2 which we had available
and we have been able to process the same volume of traffic with no reported
*Receive Overruns* on its Gigabit NIC.

I noted the advisory (co010308_cw04) where the NC7131 may lock up ProLiant
6500/7000 servers. Is there an interaction problem with the new DL530 G2
hardware and heavily loaded NIC*s?

I can only reproduce this using our backup software in anger, file copies
(run either client or server side) etc do not expose the problem.

Suggestions, Did any one get to the bottom of this?
Regards Ivan.

--
Note: To sign off this list, send a "signoff" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=