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
|
