(Trying yet again, this time from the web interface):

I think my posts are being eaten (usually they show up right away), and
perhaps Paul has a filter on the word "Test" (but I doubt it as there seems
to be a number of those posts).

Anyway, I was setting the 2610 back to half-duplex, then got distracted
before I could set the Catalyst back (it was still on full-duplex) and
received this error on the 2610 when I returned:
May 28 20:18:46.243 PDT: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error

Drawing from this, I'm guessing somehow the 2610 e0/0 was really running
full-duplex before.


Here's the original post (which doesn't look like it ever made it):
Odd situation that I'm dinking around with in my lab (actually stalling from
getting on with the real IDS lab I should be working on).  2610 router with
a 10mbit ethernet port connected to a Catalyst 3524 10/100mbit port.  I've
configured both sides for 10mbit and full-duplex and brought them out of no
shut mode at the same time, cleared counters, and then started up a 100K
packets, 1450 bit size, 0 second timeout from another 10mbit router (1605R)
also connected to the Catalyst (only running 10/half, though).  With that
ping session going, here are some of the results:

Cat3524b_jroysdon#
Cat3524b_jroysdon#sh int f0/22
FastEthernet0/22 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0004.27dc.6196 (bia 0004.27dc.6196)
  Description: 2610 e0/0
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 66/255, rxload 66/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 10Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:08, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:04:32
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  30 second input rate 2622000 bits/sec, 225 packets/sec
  30 second output rate 2623000 bits/sec, 226 packets/sec
     29741 packets input, 43430219 bytes
     Received 93 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 93 multicast
     0 input packets with dribble condition detected
     29771 packets output, 43454247 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
Cat3524b_jroysdon#sh cdp neigh det
-------------------------
Device ID: c2610_jroysdon.internal.artoo.net
Entry address(es):
  IP address: 192.168.45.252
Platform: cisco 2610,  Capabilities: Router
Interface: FastEthernet0/22,  Port ID (outgoing port): Ethernet0/0
Holdtime : 161 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(1), RELEASE SOFTWARE
(fc2)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Fri 27-Apr-01 16:36 by cmong

advertisement version: 2
Duplex: half

Cat3524b_jroysdon#
*Mar  3 00:24:20.250 PST: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered
on FastEthern
et0/22 (not half duplex), with c2610_jroysdon.internal.artoo.net Ethernet0/0
(half duplex)

/////////////////////////////////////////////////////////////////////

c2610_jroysdon#sh int e0/0
Ethernet0/0 is up, line protocol is up
  Hardware is AmdP2, address is 0003.e39b.5cc0 (bia 0003.e39b.5cc0)
  Internet address is 192.168.45.252/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 24/255, rxload 24/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:04:30
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 14/75, 0 drops
  5 minute input rate 968000 bits/sec, 100 packets/sec
  5 minute output rate 967000 bits/sec, 100 packets/sec
     30061 packets input, 43689271 bytes, 0 no buffer
     Received 147 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     29959 packets output, 43659032 bytes, 0 underruns(0/0/0)
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
c2610_jroysdon# sh cdp neigh det
-------------------------
Device ID: Cat3524b_jroysdon.internal.artoo.net
Entry address(es):
  IP address: 192.168.43.2
Platform: cisco WS-C3524-PWR-XL,  Capabilities: Trans-Bridge Switch
Interface: Ethernet0/0,  Port ID (outgoing port): FastEthernet0/22
Holdtime : 143 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5.2)XU,
MAINTENANCE INTERIM SOFT
WARE
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 17-Jul-00 18:29 by ayounes

advertisement version: 2
Protocol Hello:  OUI=0x00000C, Protocol ID=0x0112; payload len=27,
value=00000000FFFFFFFF0
10121FF000000000000000427DC6180FF0002
VTP Management Domain: 'artoo'
Duplex: full

-------------------------
Device ID: c1605r_unused.internal.artoo.net

c2610_jroysdon#
May 28 19:32:07.602 PDT: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered
on Ethernet0/0
 (not full duplex), with Cat3524b_jroysdon.internal.artoo.net
FastEthernet0/22 (full duple
x).
c2610_jroysdon#

///////////////////////////////////

Later with a 100K, 1450 bits, 0 second timeout packet ping session coming
from the 2610 to the same target router, at the same time the 1605R is still
pinging the 2610:

c2610_jroysdon#sh int e0/0
Ethernet0/0 is up, line protocol is up
  Hardware is AmdP2, address is 0003.e39b.5cc0 (bia 0003.e39b.5cc0)
  Internet address is 192.168.45.252/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 90/255, rxload 68/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:10:19
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 43/75, 0 drops
  5 minute input rate 2701000 bits/sec, 265 packets/sec
  5 minute output rate 3562000 bits/sec, 346 packets/sec
     126350 packets input, 184235072 bytes, 2 no buffer
     Received 328 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     155690 packets output, 227384676 bytes, 0 underruns(0/0/0)
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Cat3524b_jroysdon#sh int f0/22
FastEthernet0/22 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0004.27dc.6196 (bia 0004.27dc.6196)
  Description: 2610 e0/0
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 97/255, rxload 138/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 10Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:10:23
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  30 second input rate 5444000 bits/sec, 465 packets/sec
  30 second output rate 3842000 bits/sec, 329 packets/sec
     156097 packets input, 228570188 bytes
     Received 200 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 198 multicast
     0 input packets with dribble condition detected
     126858 packets output, 185267594 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

///////////////////////////////////

The 1605R was getting a ton of collisions (which would be expected if the
2610 was really running 10/full, as it could send and receive at the same
time, whereas the 1605R has to share the media with the Catalyst):
.May 28 19:37:49.616 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded....
..........!..............!....................................!.......
..!............
.May 28 19:37:53.703 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded
.May 28 19:37:54.072 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded
.May 28 19:37:54.576 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded!...........!................................!.........
....................!
.May 28 19:37:54.973 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded
.May 28 19:37:55.429 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded
.May 28 19:37:55.691 PDT: %QUICC_ETHER-5-COLL: Unit 1, excessive collisions.
Retry limit 1
5 exceeded.!...................................!...........

///////////////////////////////////

So I tried testing pinging from the 2610 to a local 100/full workstation
while the 1605-R was pinging the 2610 (this time after a clear counters):

Cat3524b_jroysdon#sh int f0/22
FastEthernet0/22 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0004.27dc.6196 (bia 0004.27dc.6196)
  Description: 2610 e0/0
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 131/255, rxload 134/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 10Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:11, output 00:00:01, output hang never
  Last clearing of "show interface" counters 00:18:35
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  30 second input rate 5293000 bits/sec, 451 packets/sec
  30 second output rate 5167000 bits/sec, 441 packets/sec
     329097 packets input, 482038917 bytes
     Received 346 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 343 multicast
     0 input packets with dribble condition detected
     288210 packets output, 421059923 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

c2610_jroysdon#sh int e0/0
Ethernet0/0 is up, line protocol is up
  Hardware is AmdP2, address is 0003.e39b.5cc0 (bia 0003.e39b.5cc0)
  Internet address is 192.168.45.252/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 114/255, rxload 104/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:05:40
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 18/75, 0 drops
  5 minute input rate 4088000 bits/sec, 375 packets/sec
  5 minute output rate 4479000 bits/sec, 412 packets/sec
     131148 packets input, 191524006 bytes, 0 no buffer
     Received 183 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     137369 packets output, 200751793 bytes, 0 underruns(0/0/0)
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

///////////////////////////////////

Still no errors at all on the Catalyst or 2610.  I added another 100/full
workstation also into the Catalyst pinging the 2610 (I couldn't really have
it ping that fast, DOS limits it to like 1 ping per second, but I could
still generate some "large" traffic at 1450 bits per packet), and the
results didn't change at all.

So, I guess what I'm asking with this long-winded post, is what should
happen with a duplex mismatch?  Collisions and/or errors, correct?  Should
10mbit be able to support full-duplex (something
vendor-specific/proprietary, even)?  Perhaps what was going on the entire
time was that since I had 10mbit configured on the Catalyst (and that's the
only speed supported on e0/0 on the 2610), that it automatically limited to
half-duplex?  Except that the Catalyst CDP was transmitting that it was
running full-duplex (CDP bug?).

--
Jason Roysdon, CCNP+Security/CCDP, MCSE, CNA, Network+, A+
List email: [EMAIL PROTECTED]
Homepage: http://jason.artoo.net/





Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=6176&t=6176
--------------------------------------------------
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