--0-356195159-1079578334=:58613
Content-Type: text/plain; charset=us-ascii
this is starting to get a bit OT, but...
weve got cisco gear and windows, unix, vms, etc.. and i can say NONE of them
work well if the switch port doesnt match the client settings. for that
matter, weve seen nothing but problems with auto<-->auto on all clients.
windows may appear to work, but at least for us, we see errors on the switch
port, and the perf diff when you hard set the speed is noticable... a perfect
example is openvms... the cisco folks changed the switch port and the vms
netbackup job was running at 4kb/sec!!!!! once i changed to 10/full, 1.1mb/sec
(its an old alpha...)
"Brzozowski, Dwayne" <Dwayne.Brzozowski AT mail.va DOT gov> wrote:
hate to say it, but Windows is the only OS that auto negotiates like it is
suppose to. Sun says it does, but it doesn't. I agree, a cheap switch is not
the way to go. Spend the money on a Cisco and the results will be worth it.
-Dwayne
-----Original Message-----
From: Jim Horalek [mailto:jimh AT federaledge DOT com]
Sent: Wednesday, March 17, 2004 5:46 PM
To: Brzozowski, Dwayne; 'Veritas-Bu (E-mail)'
Subject: RE: [Veritas-bu] Is there an official document of client and
server NIC and switch settings
This is one reason not to cut costs on your networking infustructure.
The weakest link is probably that cheap switch you though you would cut
costs with.
jim
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Brzozowski,
Dwayne
Sent: Wednesday, March 17, 2004 3:35 PM
To: Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] Is there an official document of client and server
NIC and switch settings
I try to make sure all clients, no matter what NIC is present, eri, ce,
ge,qfe,hme, that autoneg is always off, 100/1000 fdx always on, everything
else, 100/1000hdx is always off. If port on switch is set to autoneg on,
link might sync to 100/1000fdx, but at some point, it will drop and sync and
a different rate, and that causes problems. It also helps to hard code these
settings so when you client/server is rebooted, the same settings return. I
have to deal with all types of cards/settings and just an fyi, the Sun CE is
one of the quirkiest. I have the settings that work if anyone wants them.
Dwayne J. Brzozowski
Department of Veterans Affairs
Austin Automation center
(512)326-6728 work
dwayne.brzozowski AT mail.va DOT gov
-----Original Message-----
From: King, Cheryl [mailto:cheryl.king AT intrado DOT com]
Sent: Wednesday, March 17, 2004 1: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
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
aaarrrggghhh!!!!
FreeBSD rocks
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
--0-356195159-1079578334=:58613
Content-Type: text/html; charset=us-ascii
<DIV>this is starting to get a bit OT, but...</DIV>
<DIV>weve got cisco gear and windows, unix, vms, etc.. and i can say NONE
of them work well if the switch port doesnt match the client settings.
for that matter, weve seen nothing but problems with auto<-->auto on all
clients. windows may appear to work, but at least for us, we see errors
on the switch port, and the perf diff when you hard set the speed is
noticable... a perfect example is openvms... the cisco folks
changed the switch port and the vms netbackup job was running at
4kb/sec!!!!! once i changed to 10/full, 1.1mb/sec (its an old
alpha...)<BR><BR><B><I>"Brzozowski, Dwayne" <Dwayne.Brzozowski AT mail.va
DOT gov></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #1010ff 2px solid">hate to say it, but Windows is the only OS that
auto negotiates like it is<BR>suppose to. Sun says it does, but it doesn't. I
agree, a cheap switch is not<BR>the way to go. Spend the money on a Cisco and
the results will be worth it. <BR><BR>-Dwayne<BR><BR>-----Original
Message-----<BR>From: Jim Horalek [mailto:jimh AT federaledge DOT com]<BR>Sent:
Wednesday, March 17, 2004 5:46 PM<BR>To: Brzozowski, Dwayne; 'Veritas-Bu
(E-mail)'<BR>Subject: RE: [Veritas-bu] Is there an official document of client
and<BR>server NIC and switch settings<BR><BR><BR>This is one reason not to cut
costs on your networking infustructure.<BR>The weakest link is probably that
cheap switch you though you would cut<BR>costs
with.<BR><BR>jim<BR><BR>-----Original Message-----<BR>From: veritas-bu-admin AT
mailman.eng.auburn DOT edu<BR>[mailto:veritas-bu-admin AT mailman.eng.auburn
DOT edu] On Behalf Of Brzozowski,<BR>Dwayne<BR>Sent:
Wednesday, March 17, 2004 3:35 PM<BR>To: Veritas-Bu (E-mail)<BR>Subject: RE:
[Veritas-bu] Is there an official document of client and server<BR>NIC and
switch settings<BR><BR><BR>I try to make sure all clients, no matter what NIC
is present, eri, ce,<BR>ge,qfe,hme, that autoneg is always off, 100/1000 fdx
always on, everything<BR>else, 100/1000hdx is always off. If port on switch is
set to autoneg on,<BR>link might sync to 100/1000fdx, but at some point, it
will drop and sync and<BR>a different rate, and that causes problems. It also
helps to hard code these<BR>settings so when you client/server is rebooted, the
same settings return. I<BR>have to deal with all types of cards/settings and
just an fyi, the Sun CE is<BR>one of the quirkiest. I have the settings that
work if anyone wants them. <BR><BR>Dwayne J. Brzozowski<BR>Department of
Veterans Affairs<BR>Austin Automation center<BR>(512)326-6728
work<BR>dwayne.brzozowski AT mail.va DOT gov<BR><BR><BR>-----Original
Message-----<BR>From:
King, Cheryl [mailto:cheryl.king AT intrado DOT com]<BR>Sent: Wednesday, March
17, 2004 1:03 PM<BR>To: Veritas-Bu (E-mail)<BR>Subject: [Veritas-bu] Is there
an official document of client and server NIC<BR>and switch
settings<BR><BR><BR>Over and over again we have problems with poor performance
with new client<BR>backups and restores. Is there a document that says what the
NIC settings<BR>should be for each client type? For example we have highest
speed possible<BR>for all of them, half duplex for HP, and full duplex for
everything else, I<BR>think (I haven't checked every system and wasn't here
when some were<BR>implemented). Setting Auto detect on the switch seems to not
work correctly<BR>(causes slow performance). I think the switches are set to
match the<BR>server, but have no way to verify that. I'd like to be able to
present an<BR>official document to the System Administrators and the Network
Engineers<BR>that states the correct configuration requirements. Does Veritas
have such<BR>a
document or statement?<BR><BR>Is this a problem in other environments? Is this
just an issue in Veritas<BR>Backup environments? Are my SAs and Network
Engineers not following some<BR>industry, standard, best-practices? I've been
in IT for many years but<BR>working with Veritas NBU for 1 year. I don't recall
ever having network<BR>issues like this before.<BR><BR>NBU 4.5 FP5 Solaris 8
Master/Media<BR>Clients OSF1_V5, HP-UX 11.00, HP-UX10.20, Windows2000,
WindowsNT, RedHat2.4,<BR>RedHat 2.2, Solaris8, Solaris7.<BR><BR>Thanks in
advance.<BR><BR>Cheryl
King<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>_______________________________________________<BR>Veritas-bu
maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<BR>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<BR><BR>_______________________________________________<BR>Veritas-bu
maillist -
Veritas-bu AT mailman.eng.auburn DOT
edu<BR>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</BLOCKQUOTE><BR><BR>aaarrrggghhh!!!!<br>FreeBSD
rocks<p><font face=arial size=-1>Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/mailtag_us/*http://mail.yahoo.com";
target="_blank"><b>Yahoo! Mail</a></b> - More reliable, more storage, less spam
--0-356195159-1079578334=:58613--
|
