02-22-2011 09:57 PM - edited 03-06-2019 03:42 PM
Hi all,
I faced the problem that my cisco 881 routers has configure already and line is up between ISP , and also can use internet from internal users.
But when i checked on the router, every 10 secs i found that error messages.
Feb 23 05:43:28.047: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Lat
Feb 23 05:43:29.679: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:43:29.723: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:43:29.727: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:44:25.419: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:44:33.563: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:44:34.015: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:44:46.727: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Sometime network is down and cannot bring up to network connection.
this is my IOS version.
Cisco IOS Software, C880 Software (C880DATA-UNIVERSALK9-M), Version 15.0(1)M4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 29-Oct-10 00:02 by prod_rel_team
ROM: System Bootstrap, Version 12.4(22r)YB5, RELEASE SOFTWARE (fc1)
TGSrouter uptime is 59 minutes
System returned to ROM by power-on
System restarted at 12:52:07 utc Wed Feb 23 2011
System image file is "flash:c880data-universalk9-mz.150-1.M4.bin"
Last reload type: Normal Reload
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and
Feb 23 05:51:09.295: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision
Feb 23 05:51:10.071: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(4), Late collision regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html you require further assistance please contact us by sending email to
export@cisco.com. 881 (MPC8300) processor (revision 1.0) with 236544K/25600K bytes of memory.
Processor board ID FHK150273SN
If
Cisco
5 FastEthernet interfaces
1 Virtual Private Network (VPN) Module
256K bytes of non-volatile configuration memory.
125440K bytes of ATA CompactFlash (Read/Write)
License Info:
License UDI:
-------------------------------------------------
Device# PID SN
-------------------------------------------------
*0 CISCO881-K9 FHK150273SN
License Information for 'c880-data'
License Level: advsecurity Type: Permanent
Next reboot license Level: advsecurity
Configuration register is 0x2102
-#- --length-- -----date/time------ path
1 28461436 Mar 01 1984 00:01:00 c880data-universalk9-mz.150-1.M4.bin
2 3331 Jan 05 2011 12:27:48 cpconfig-8xx.cfg
3 2941440 Jan 05 2011 12:28:04 cpexpress.tar
4 1038 Jan 05 2011 12:28:14 home.shtml
5 115712 Jan 05 2011 12:28:40 home.tar
6 1697952 Jan 05 2011 12:28:56 securedesktop-ios-3.1.1.45-k9.pkg
7 415956 Jan 05 2011 12:29:08 sslclient-win-1.1.4.176.pkg
94633984 bytes available (33652736 bytes used)
I used IP address for WAN port fe4 and for internal, use vlan 1 with public ip range.
Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up up
FastEthernet1 unassigned YES unset down down
FastEthernet2 unassigned YES unset up up
FastEthernet3 unassigned YES unset down down
FastEthernet4 123.123.123.123 YES NVRAM up up
Vlan1 210.210.210.210 YES NVRAM up up
router#sh int f4
FastEthernet4 is up, line protocol is up
Hardware is PQII_PRO_UEC, address is e05f.b9b9.4a88 (bia e05f.b9b9.4a88)
Description: WAN link to Singtel
Internet address is 123.123.123.123 /30
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 249/255, txload 1/255, rxload 4/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:05, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1644000 bits/sec, 150 packets/sec
5 minute output rate 131000 bits/sec, 132 packets/sec
398671 packets input, 488595441 bytes
Received 4 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
325927 packets output, 43881552 bytes, 0 underruns
21202 output errors, 14801 collisions, 3 interface resets
0 unknown protocol drops
0 babbles, 261 late collision, 20983 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
There has so many output errors , and I configure very simple and just use default route.
Please suggest me what should I do to solve this problem .
Thanks a lot
02-22-2011 10:02 PM
if I had a penny for each time I see this issue, I'd be rich
your port is auto negotiated to Half duplex. This happens when one side is set to auto duplex and the other side is set to manual half or full duplex. This also happens if your port is connected to a hub. Try setting your interface to "duplex full" and "speed 100", the collisions should go away. The interface will bounce when you do this.
06-25-2022 11:53 PM
It works. Thanks to Cisco Community.
06-26-2022 06:36 AM
I'll add one minor point of clarification. This would NOT have been a big issue if the other side is manually set to half duplex. Then both sides would work correctly (albeit a little slower) in half duplex mode. It is a HUGE problem when one side is forced to full duplex and the other side is auto. Forcing a device to full means that device does not respond to duplex negotiation requests, which means the other side has to assume half duplex if it is set to auto. Really short version is "late collisions are always bad"!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide