This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C2D93D.C90BC760
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
We found 128 kilobytes of Net Buffer works very well on all the HP_UX &
Sun Solaris clients but not the windows clients. We have tried 64 but 32
kilobyte is faster for the Multiplex Mode.
Tommy Wu
-----Original Message-----
From: scott.kendall AT abbott DOT com [mailto:scott.kendall AT abbott DOT com]
Sent: Thursday, February 20, 2003 11:07 PM
To: Tommy Wu
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Gigabit NIC & Win2K SP3 Network Shutdown
"Communications Buffer Size" for Windows clients in the GUI and
"Buffer_Size" in the Registry are the same value. This buffer size
value and the NET_BUFFER_SZ file both control network communications. I
have seen/heard several conflicting things from veritas as to what they
actually control and which one to use on a Windows client. The most
recent was a paper that said one was for transmit and the other for
receive (I think the buffer size was for tx and NET_BUFFER_SZ was rcv).
I kind of buy this, because when I did some testing a while back, I
noticed that changing the NET_BUFFER_SZ changed the value as it appeared
in the logs I was looking at, but changing the buffer size value never
showed any changes in the logs. I think I was looking at the bptm logs
at the media server, so this would make sense. The paper said that
while the buffers don't have to match, they recommended it.
did you have to go down to 32 to fix your problem? It seems like a low
number. Have you tried 129? That is what veritas recommends on Windows
from all the papers I have seen.
- Scott
"Tommy Wu" <tommywu AT infospacenetwork DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
02/20/2003 11:12 AM
To: "'Len Boyle'" <Len.Boyle AT sas DOT com>,
<anthony.t.li AT census DOT gov>
cc: "'Tanber, Todd N'" <tanber AT intel DOT com>,
<Quarantine AT GSCCCA DOT ORG>, <ssesar AT mitre DOT org>,
<veritas-bu AT mailman.eng.auburn DOT edu>
Subject: RE: [Veritas-bu] Gigabit NIC & Win2K SP3 Network
Shutdown
Gentleman,
Here is the fix for the Gigabit NIC. We are getting 5-11Mb/Sec for each
network clients. The Switch is set to use Fast Ether Channel (FEC) Full
Duplex, and Both Broadcom Gigabit NIC is set to use TEAM.
Buffer_Size set to use 32 kilobytes
NET_BUFFER_SZ set to use 32768 (32x1024)
Both Buffers have to match.
Good Luck
Tommy Wu
-----Original Message-----
From: Len Boyle [mailto:Len.Boyle AT sas DOT com]
Sent: Tuesday, February 18, 2003 8:44 PM
To: Tommy Wu; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Gigabit NIC & Win2K SP3 Network Shutdown
Good evening Tommy
Tracking tcp/ip errors always seems hard.
Did you see any errors in the windows event logs, either system or
application?
When we were looking at an ms exchange problem, the veritas tech support
folks said that some drivers for interface cards could cause problems.
You might want to check with tech support and dell tech support. Our
problem was not that, but a problem with the motherboard.
Like others, I would ask for a little more info on what you mean by
shutdown. Does all tcpip traffic stop, or just new connections?
Almost everything netbackup does, seems to have a socket connection in
the middle of the action. If you can you might check with the netstat
command and see if you have a large number of socket connections in a
time-wait state.
If so you might want to look at changing the tcp_wait interval. At least
it was a problem/fix on unix.
Good luck and let us know the final fix.
len
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------=_NextPart_000_0005_01C2D93D.C90BC760
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:[email protected]">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;
mso-font-alt:"Times New Roman";
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:auto;
mso-font-signature:0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>We found 128 kilobytes of Net =
Buffer works
very well on all the HP_UX & Sun Solaris clients but not the windows
clients. We have tried 64 but 32 kilobyte is faster for the Multiplex =
Mode.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Tommy =
Wu<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
scott.kendall AT abbott DOT com
[mailto:scott.kendall AT abbott DOT com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, February =
20, 2003
11:07 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Tommy Wu<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b>
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Veritas-bu] =
Gigabit
NIC & Win2K SP3 Network Shutdown</span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial'>"Communications Buffer Size" for Windows clients in the =
GUI
and "Buffer_Size" in the Registry are the same value. =
This
buffer size value and the NET_BUFFER_SZ file both control network
communications. I have seen/heard several conflicting things from =
veritas
as to what they actually control and which one to use on a Windows =
client.
The most recent was a paper that said one was for transmit and the =
other
for receive (I think the buffer size was for tx and NET_BUFFER_SZ was =
rcv).
I kind of buy this, because when I did some testing a while back, =
I
noticed that changing the NET_BUFFER_SZ changed the value as it appeared =
in the
logs I was looking at, but changing the buffer size value never showed =
any
changes in the logs. I think I was looking at the bptm logs at the =
media
server, so this would make sense. The paper said that while the =
buffers
don't have to match, they recommended it.</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>did
you have to go down to 32 to fix your problem? It seems like a low
number. Have you tried 129? That is what veritas recommends =
on
Windows from all the papers I have seen.</span></font> <br>
<br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>-
Scott</span></font> <br>
<br style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></p>
<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
style=3D'width:100.0%;mso-cellspacing:1.5pt;margin-left:.5in'>
<tr style=3D'mso-yfti-irow:0;mso-yfti-lastrow:yes'>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p> </o:p></span></font></p>
</td>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><b><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
7.5pt;font-family:sans-serif;font-weight:bold'>"Tommy Wu"
<tommywu AT infospacenetwork DOT com></span></font></b> <br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>Sent
by: veritas-bu-admin AT mailman.eng.auburn DOT edu</span></font> =
<o:p></o:p></p>
<p><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:
sans-serif'>02/20/2003 11:12 AM</span></font> <o:p></o:p></p>
</td>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:7.5pt;
font-family:Arial'> </span></font><br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
To: "'Len =
Boyle'"
<Len.Boyle AT sas DOT com>, =
<anthony.t.li AT census DOT gov></span></font> <br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
cc: "'Tanber, =
Todd
N'" <tanber AT intel DOT com>, <Quarantine AT GSCCCA DOT
ORG>,
<ssesar AT mitre DOT org>, =
<veritas-bu AT mailman.eng.auburn DOT edu></span></font>
<br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
Subject: RE: =
[Veritas-bu]
Gigabit NIC & Win2K SP3 Network =
Shutdown</span></font><o:p></o:p></p>
</td>
</tr>
</table>
<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
<br>
<br>
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Gentleman,<br>
Here is the fix for the Gigabit NIC. We are getting 5-11Mb/Sec for =
each<br>
network clients. The Switch is set to use Fast Ether Channel (FEC) =
Full<br>
Duplex, and Both Broadcom Gigabit NIC is set to use TEAM.<br>
<br>
Buffer_Size set to use 32 kilobytes<br>
NET_BUFFER_SZ set to use 32768 (32x1024)<br>
Both Buffers have to match.<br>
<br>
Good Luck<br>
Tommy Wu<br>
<br>
-----Original Message-----<br>
From: Len Boyle [mailto:Len.Boyle AT sas DOT com] <br>
Sent: Tuesday, February 18, 2003 8:44 PM<br>
To: Tommy Wu; veritas-bu AT mailman.eng.auburn DOT edu<br>
Subject: RE: [Veritas-bu] Gigabit NIC & Win2K SP3 Network =
Shutdown<br>
<br>
Good evening Tommy <br>
<br>
Tracking tcp/ip errors always seems hard. <br>
Did you see any errors in the windows event logs, either system or<br>
application?<br>
<br>
When we were looking at an ms exchange problem, the veritas tech =
support<br>
folks said that some drivers for interface cards could cause =
problems.<br>
You might want to check with tech support and dell tech support. =
Our<br>
problem was not that, but a problem with the motherboard. <br>
<br>
Like others, I would ask for a little more info on what you mean by<br>
shutdown. Does all tcpip traffic stop, or just new connections? <br>
<br>
Almost everything netbackup does, seems to have a socket connection =
in<br>
the middle of the action. If you can you might check with the =
netstat<br>
command and see if you have a large number of socket connections in =
a<br>
time-wait state. <br>
If so you might want to look at changing the tcp_wait interval. At =
least<br>
it was a problem/fix on unix. <br>
<br>
Good luck and let us know the final fix. <br>
<br>
len<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]></span></font><o:p></o:p></p>
</div>
</body>
</html>
------=_NextPart_000_0005_01C2D93D.C90BC760--
|
