This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C40C5C.D0B1E320
Content-Type: text/plain
Cheryl,
I second this. We always force our 100mbit clients to 100 fdx, otherwise
small backups WILL take forever. I don't have any experience with HP, but I
would look into why you can't run fdx on those machines . . . Hdx eeeewww!
It is my understanding that with 100mbit ethernet, autonegotiate is NOT
built into the definition. So even though manufacturers say they support
autonegotiate, it is up to them how to define how it will work; thus
manufacturer A's network card doesn't really autoneg with manufacturer B's
switch. That said, it is also my understanding that with gig, autoneg is
built into the definition, so manufacturers have to work to a specific
standard . . . At least this is what I have been told . . .
Hope this helps.
_____
Scott Chapman
Enterprise Computing Technical Support
ICBC - Victoria
Phone: 250.414.7650 Fax: 250.978.8003 Cel: 250.213.9295
-----Original Message-----
From: bryan_bahnmiller AT agilent DOT com [mailto:bryan_bahnmiller AT agilent
DOT com]
Sent: Wednesday, March 17, 2004 11:55 AM
To: cheryl.king AT intrado DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Is there an official document of client and server
NIC and switch settings
Cheryl,
<sarcasm>NetBackup is the most complete network trouble-shooting tool we
have found!
</sarcasm>
Unfortunately this is true. Network backups seem to tax network
infrastructure more than almost any other application - NFS, CIFS, Oracle
replication,... As such, any small network problem that is normally overcome
by re-transmission of packets, becomes much more visible with NetBackup.
We have set up standards with our network, Unix and Windows organizations.
We have explicitly told them that all backup network ports are to be fixed
to the maximum setting. That is, the server has to be fixed to 10 or 100,
half or full duplex. And the switch port has to be fixed to the same
setting.
Auto-negotiation seems to work about 20% of the time. So about 80% of the
time you will have backup problems. The only sure method of preventing
problems is to have organizational standards to explicitly set the NICs and
ports.
Bryan
Bryan Bahnmiller
IT Specialist - Storage
Agilent Technologies
-----Original Message-----
From: King, Cheryl [mailto:cheryl.king AT intrado DOT com]
Sent: Wednesday, March 17, 2004 12:03 PM
To: Veritas-Bu (E-mail)
Subject: [Veritas-bu] Is there an official document of client and server NIC
and switch settings
Over and over again we have problems with poor performance with new client
backups and restores. Is there a document that says what the NIC settings
should be for each client type? For example we have highest speed possible
for all of them, half duplex for HP, and full duplex for everything else, I
think (I haven't checked every system and wasn't here when some were
implemented). Setting Auto detect on the switch seems to not work correctly
(causes slow performance). I think the switches are set to match the
server, but have no way to verify that. I'd like to be able to present an
official document to the System Administrators and the Network Engineers
that states the correct configuration requirements. Does Veritas have such
a document or statement?
Is this a problem in other environments? Is this just an issue in Veritas
Backup environments? Are my SAs and Network Engineers not following some
industry, standard, best-practices? I've been in IT for many years but
working with Veritas NBU for 1 year. I don't recall ever having network
issues like this before.
NBU 4.5 FP5 Solaris 8 Master/Media
Clients OSF1_V5, HP-UX 11.00, HP-UX10.20, Windows2000, WindowsNT, RedHat2.4,
RedHat 2.2, Solaris8, Solaris7.
Thanks in advance.
Cheryl King
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C40C5C.D0B1E320
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Is there an official document of client and =
server NIC and switch settings</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Cheryl,</FONT>
</P>
<P><FONT SIZE=3D2>I second this. We always force our 100mbit =
clients to 100 fdx, otherwise small backups WILL take forever. I =
don't have any experience with HP, but I would look into why you can't =
run fdx on those machines . . . Hdx eeeewww!</FONT></P>
<P><FONT SIZE=3D2>It is my understanding that with 100mbit ethernet, =
autonegotiate is NOT built into the definition. So even though =
manufacturers say they support autonegotiate, it is up to them how to =
define how it will work; thus manufacturer A's network card doesn't =
really autoneg with manufacturer B's switch. That said, it is =
also my understanding that with gig, autoneg is built into the =
definition, so manufacturers have to work to a specific standard . . . =
At least this is what I have been told . . .</FONT></P>
<P><FONT SIZE=3D2>Hope this helps.</FONT>
</P>
<P><FONT SIZE=3D2> _____ </FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Scott Chapman</FONT>
<BR><FONT SIZE=3D2>Enterprise Computing Technical Support</FONT>
<BR><FONT SIZE=3D2>ICBC - Victoria</FONT>
<BR><FONT SIZE=3D2>Phone: 250.414.7650 Fax: 250.978.8003 =
Cel: 250.213.9295</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: bryan_bahnmiller AT agilent DOT com [<A =
HREF=3D"mailto:bryan_bahnmiller AT agilent DOT com">mailto:bryan_bahnmiller@agi=
lent.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 17, 2004 11:55 AM</FONT>
<BR><FONT SIZE=3D2>To: cheryl.king AT intrado DOT com; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Is there an official =
document of client and server NIC and switch settings</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Cheryl,</FONT>
</P>
<P><FONT SIZE=3D2> <sarcasm>NetBackup is the most complete =
network trouble-shooting tool we have found!</FONT>
<BR><FONT SIZE=3D2> </sarcasm></FONT>
</P>
<P><FONT SIZE=3D2> Unfortunately this is true. Network backups =
seem to tax network infrastructure more than almost any other =
application - NFS, CIFS, Oracle replication,... As such, any small =
network problem that is normally overcome by re-transmission of =
packets, becomes much more visible with NetBackup.</FONT></P>
<P><FONT SIZE=3D2> We have set up standards with our network, =
Unix and Windows organizations. We have explicitly told them that all =
backup network ports are to be fixed to the maximum setting. That is, =
the server has to be fixed to 10 or 100, half or full duplex. And the =
switch port has to be fixed to the same setting.</FONT></P>
<P><FONT SIZE=3D2> Auto-negotiation seems to work about 20% of =
the time. So about 80% of the time you will have backup problems. The =
only sure method of preventing problems is to have organizational =
standards to explicitly set the NICs and ports.</FONT></P>
<P><FONT SIZE=3D2> Bryan</FONT>
</P>
<P><FONT SIZE=3D2>Bryan Bahnmiller</FONT>
<BR><FONT SIZE=3D2>IT Specialist - Storage</FONT>
<BR><FONT SIZE=3D2>Agilent Technologies</FONT>
<BR><FONT SIZE=3D2> </FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: King, Cheryl [<A =
HREF=3D"mailto:cheryl.king AT intrado DOT com">mailto:cheryl.king AT intrado
DOT com</=
A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 17, 2004 12:03 PM</FONT>
<BR><FONT SIZE=3D2>To: Veritas-Bu (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Is there an official document =
of client and server NIC and switch settings</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Over and over again we have problems with poor =
performance with new client backups and restores. Is there a =
document that says what the NIC settings should be for each client =
type? For example we have highest speed possible for all of them, =
half duplex for HP, and full duplex for everything else, I think (I =
haven't checked every system and wasn't here when some were =
implemented). Setting Auto detect on the switch seems to not work =
correctly (causes slow performance). I think the switches =
are set to match the server, but have no way to verify that. I'd =
like to be able to present an official document to the System =
Administrators and the Network Engineers that states the correct =
configuration requirements. Does Veritas have such a document or =
statement?</FONT></P>
<P><FONT SIZE=3D2>Is this a problem in other environments? Is =
this just an issue in Veritas Backup environments? Are my SAs and =
Network Engineers not following some industry, standard, =
best-practices? I've been in IT for many years but =
working with Veritas NBU for 1 year. I don't recall ever having =
network issues like this before.</FONT></P>
<P><FONT SIZE=3D2>NBU 4.5 FP5 Solaris 8 Master/Media</FONT>
<BR><FONT SIZE=3D2>Clients OSF1_V5, HP-UX 11.00, HP-UX10.20, =
Windows2000, WindowsNT, RedHat2.4, RedHat 2.2, Solaris8, =
Solaris7.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks in advance.</FONT>
</P>
<P><FONT SIZE=3D2>Cheryl King</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C40C5C.D0B1E320--
|
