that happens to me all the time..we hard set the switches to
100/full, the server guys bring up the ports in auto, we get the
issue you got...usually on sun's...In most places we run auto/auto.

Larry Letterman
Network Engineer
Cisco Systems


  ----- Original Message -----
  From: John Neiberger
  To: [EMAIL PROTECTED]
  Sent: Wednesday, March 12, 2003 8:02 AM
  Subject: Re: 10 half or 100 full [7:64931]


  Interestingly, just now I fixed a problem with a Sun Netra server that was
  set to autonegotiate.  It was connected to a 6500 that was hard-set to
  100/Full.  Since manually setting the speed on a 6500 disables
participation
  in autonegotiation, the server was choosing 100/Half instead of 100/Full.

  Setting both sides to auto fixed the problem and I'm no longer seeing
errors
  on the switch.

  John

  Sam Sneed wrote:
  >
  > I see interesting, most of my sun servers are over 2 years old.
  > You say
  > newer cisco switches should be set to auto first then manual if
  > you have
  > problems. Do you mean newer as in version of IOS, OS or newer
  > physical
  > hardware?
  >
  > ""John Neiberger""  wrote in
  > message
  > news:[EMAIL PROTECTED]
  > > We have quite a mix of NT/Novell/Sun servers.  As for the Sun
  > servers,
  > over
  > > half are set to auto.  With those, we've only changed the
  > settings when we
  > > had an issue.  With the Intel-based servers and workstations
  > we've moved
  > > most of them to auto.
  > >
  > > We've had a few machines with older NICs where auto just
  > wasn't working
  > > right, but if your NICs are relatively new and you have
  > updated drivers
  > you
  > > shouldn't have a problem, at least with autonegotiation.
  > We've had other
  > > issues, primarily with 3COM NICs on Dell workstations, but
  > those have been
  > > resolved.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=65203&t=64931
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to