I just got AWAY from HOSTS files.  Thankfully I manage DNS too! :)  IMO
DNS is just as critical to day to day operations as Power, Cooling and
the Network.  Try turning your DNS servers off for 10 minutes and see if
the outage isn't as critical as one of those others.
 
We use AUTO here for everything... I worked for 5 years at another
corporation and we had problems getting 3COM nics to auto negotiate with
Cisco switches, so our standard for all servers was 100/FULL but that
was some time ago.  Unless you have an issue, why change it?  Further, I
don't think the Gigabit Ethernet standard supports static duplex.  Sure
you CAN do it (drivers and switches give you the option) but the
standard was written if I'm not mistaken with a built in function for
negotiating speed so anything current shouldn't have this as an issue.
 
-Jonathan

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Adams,
Dwayne
Sent: Thursday, April 12, 2007 12:28 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] clients in hosts files and forcing NICs to
FULL



Hello,

 

I have managed a few backup environments and always put the backup
servers in the hosts file of the clients and the clients in the backup
server's hosts file.  I always like to control name resolution myself.
Do most backup administrator do that or am I a relic from the past?
Also, do most backup admins use AUTO negotiate or set the switch port
and the host to FULL DUPLEX? My practices are being questioned and I
would like to check to see if what I am doing is in line with what most
backup admins are doing.

 

 

Thanks in advance,

 

Dwayne Adams

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070412/3df8454e/attachment.html