03-08-2019 06:54 AM
Hi,
I have Cisco ISR 890 series (System image file is "c800-universalk9-mz.SPA.154-3.M9.bin".).
I noticed recently that it started to "down" the interface GE8. GE8 is the WAN port and using DHCP.
I have checked the interface for the Admin Shutdown (did again no shut), changed cable etc, but same results. When I use this Ge8 cable to some other ports, I can see that interface get link (this means cable is not damaged). Any thoughts ...? Below is the output of the Sh Interface GE8:
///////////////////////////////////////////////////////////////////////////////////////////////////////
GigabitEthernet8 is down, line protocol is down
Hardware is PQ3_TSEC, address is ???.69e6 (bia ????.????.69e6)
Internet address will be negotiated using DHCP
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, Auto Speed, media type is unknown media type
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:02:25, 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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
1 packets output, 60 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
///////////////////////////////////////////////////////////////////////////////////////////////////////
Solved! Go to Solution.
03-11-2019 08:21 AM
03-08-2019 07:00 AM
amh4y0001,
Can you please show the configuration of the port 8 and also tell us what it connects to.
03-08-2019 07:00 AM
03-08-2019 08:06 AM
Hi,
I have connected a PC to that cable (instead of the GE8) and amazingly I can get valid IP address and link was up as normal.
Strange thing is that when I tried with a different box (same model, ISR 890) but GE8 was remain down.
Any thoughts ?
03-08-2019 08:13 AM
03-08-2019 07:01 AM
03-08-2019 08:24 AM
Hi,
Both sides worked well when connected with a PC.
Duplex was set to full, however, I have not checked it with auto or 1000, will check and update here (on Monday).
Thanks and have a nice weekend.
03-08-2019 02:31 PM
Hello,
on a side note, as far as I recall, GigabitEthernet8 is a combo port, so you have to configure the media type under the interface to
select whether you want to use the RJ-45 copper Ethernet port or the SFP port.
interface GigabitEthernet8
media-type ?
03-11-2019 04:56 AM
Hi again,
When I change the duplex of Ge8 to "auto" from "full", the interface was up.
As soon as I change the duplex to full, the interface went down immediately.
While in "Auto" mode, duplex mismatch error messages are visible:
%CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet8 (not full duplex), with Some_OtherDevice_OnNetwork.
%PQ3_TSEC-5-LATECOLL: Gi8, Late collision
What may be the possible cause of this behavior?
03-11-2019 05:07 AM - edited 03-11-2019 05:10 AM
Hello,
"When I change the duplex of Ge8 to "auto" from "full", the interface was up.
As soon as I change the duplex to full, the interface went down immediately.
While in "Auto" mode, duplex mismatch error messages are visible:
%CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet8 (not full duplex), with Some_OtherDevice_OnNetwork.
%PQ3_TSEC-5-LATECOLL: Gi8, Late collision"
What may be the possible cause of this behavior?
"Late collisions, on the other hand, are not normal and are usually the result of out of spec. cabling or a malfunctioning adapter. A late collision is defined as any collision that occurs after 512 bits of the frame have been transmitted. ... A minute amount of time later, a collision occurs."
I think that you have three possible problems.
1. The other side (your isp), has a manually configuration on their router.
2. You have a cable problem.
3. Your router has a problem in his port.
I suggest you in this case, contact your ISP first, after it, if their cant help you, contact the CISCO TAC for RMA process.
Regards,
03-11-2019 05:58 AM
03-11-2019 04:57 AM
Media Type is correct: Rj45
03-11-2019 08:01 AM
I have done the following so far:
1. Changed the physical box (but same model, Cisco ISR 890 series).
2. Updated the IOS to c800-universalk9-mz.SPA.154-3.M9.bin.
3. Changed the Ethernet cable.
All three modifications results the same.
ISP: I have another location where the same ISP /line is being used, which is working fine. Actually, this issue occurs now, before it was working well as well.
Further thoughts ...?
03-11-2019 08:21 AM
03-11-2019 08:45 AM
Hello,
I have connected a PC to that cable (instead of the GE8) and amazingly I can get valid IP address and link was up as normal.
When you was try it, the cable used here, it is directly attached from your pc to ISP device or it pass through a patchpanel?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: