Errors on Ethernet Ports on 6500?!?!?! [7:32853]
This is wild stuff, so I thought I'd run it by GroupStudy to see if anyone had seen this before or knew what caused it. We're currently migrating connections from a 5513+RSM to a new 6509+Sup2/MSFC2. There were three ethernet connections, that upon being moved from the 5500 to the 6500, starting showing input errors and CRC errors. When these connections were moved, the port on the 6500 was configured identically to the same port on the 5500 as far as speed, duplex, VLAN assignment, and spanning tree settings. These same devices (same patch cables and all) created no errors on the 5500 whatsoever. Here's the kicker: When we went back and changed the port speed/duplex to "auto" on the 6500, it negociated the same speed/duplex settings we had forced, but now there were no more errors. (i.e. a server set for 100-Full, that was plugged into a switchport on the 5500 forced to 100-Full was fine, but plugged into a port on the 6500 forced to 100-Full caused errors, and plugged into the exact same 6500 port set for "auto" speed/duplex had no errors.) Any ideas on why letting the switch detect settings caused no errors while forcing it to those same settings causes errors? Thanks, Mike W. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=32853&t=32853 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Errors on Ethernet Ports on 6500?!?!?! [7:32853]
I have been seeing a lot of problems with 3COM NIC's If the switch is forced 100/full and the NIC is auto we get a lot of errors, if NIC is forced 100/Full errors go away. If Switch and 3Com NIC left to auto switch will come up 100/full and NIC 100/half. You have to make sure the NIC is also forced. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Williams Sent: Tuesday, January 22, 2002 1:41 PM To: [EMAIL PROTECTED] Subject: Errors on Ethernet Ports on 6500?!?!?! [7:32853] This is wild stuff, so I thought I'd run it by GroupStudy to see if anyone had seen this before or knew what caused it. We're currently migrating connections from a 5513+RSM to a new 6509+Sup2/MSFC2. There were three ethernet connections, that upon being moved from the 5500 to the 6500, starting showing input errors and CRC errors. When these connections were moved, the port on the 6500 was configured identically to the same port on the 5500 as far as speed, duplex, VLAN assignment, and spanning tree settings. These same devices (same patch cables and all) created no errors on the 5500 whatsoever. Here's the kicker: When we went back and changed the port speed/duplex to "auto" on the 6500, it negociated the same speed/duplex settings we had forced, but now there were no more errors. (i.e. a server set for 100-Full, that was plugged into a switchport on the 5500 forced to 100-Full was fine, but plugged into a port on the 6500 forced to 100-Full caused errors, and plugged into the exact same 6500 port set for "auto" speed/duplex had no errors.) Any ideas on why letting the switch detect settings caused no errors while forcing it to those same settings causes errors? Thanks, Mike W. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33725&t=32853 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Errors on Ethernet Ports on 6500?!?!?! [7:32853]
That is a common problem with 3Com NICs you can try upgrading the dirvers witch sometimes helps but hardsetting speed and duplex to 100/full on both sides is you best bet. ""Bill Carter"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I have been seeing a lot of problems with 3COM NIC's If the switch is > forced 100/full and the NIC is auto we get a lot of errors, if NIC is forced > 100/Full errors go away. If Switch and 3Com NIC left to auto switch will > come up 100/full and NIC 100/half. > > You have to make sure the NIC is also forced. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Michael Williams > Sent: Tuesday, January 22, 2002 1:41 PM > To: [EMAIL PROTECTED] > Subject: Errors on Ethernet Ports on 6500?!?!?! [7:32853] > > > This is wild stuff, so I thought I'd run it by GroupStudy to see if anyone > had seen this before or knew what caused it. > > We're currently migrating connections from a 5513+RSM to a new > 6509+Sup2/MSFC2. There were three ethernet connections, that upon being > moved from the 5500 to the 6500, starting showing input errors and CRC > errors. When these connections were moved, the port on the 6500 was > configured identically to the same port on the 5500 as far as speed, duplex, > VLAN assignment, and spanning tree settings. > > These same devices (same patch cables and all) created no errors on the 5500 > whatsoever. > > Here's the kicker: When we went back and changed the port speed/duplex to > "auto" on the 6500, it negociated the same speed/duplex settings we had > forced, but now there were no more errors. (i.e. a server set for 100-Full, > that was plugged into a switchport on the 5500 forced to 100-Full was fine, > but plugged into a port on the 6500 forced to 100-Full caused errors, and > plugged into the exact same 6500 port set for "auto" speed/duplex had no > errors.) > > Any ideas on why letting the switch detect settings caused no errors while > forcing it to those same settings causes errors? > > Thanks, > Mike W. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33731&t=32853 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
