07-09-2003 05:47 AM - edited 03-02-2019 08:43 AM
I have this alert : %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down.
It's comming at different time and not regularly. I have test it with a 2620 and 2620XM. It's the same problem. We have test it with 2 version 12.2(17a) on 2620XM and 12.2(3b) see below
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.2(3b), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Thu 25-Oct-01 22:38 by pwade
Image text-base: 0x80008088, data-base: 0x8097C0FC
ROM: System Bootstrap, Version 12.2(6r), RELEASE SOFTWARE (fc1)
Gaci2620 uptime is 5 hours, 11 minutes
System returned to ROM by power-on
System restarted at 10:33:02 France Wed Jul 9 2003
System image file is "flash:c2600-i-mz.122-3b.bin"
cisco 2620 (MPC860) processor (revision 0x00) with 26624K/6144K bytes of memory.
Processor board ID JAD06210LTZ (1527763399)
M860 processor: part number 0, mask 49
Channelized E1, Version 1.0.
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
31 Serial network interface(s)
1 Channelized E1/PRI port(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
Configuration register is 0x0 (will be 0x2102 at next reload)
Do you think it's a problem on HSRP ?
Configuration below
interface FastEthernet0/0
ip address X.X.X.X 255.255.0.0
speed 100
full-duplex
no cdp enable
standby ip 10.1.1.1
standby priority 200
standby preempt
bridge-group 6
07-09-2003 05:51 AM
More than likely you have an issue with hardware , can you paste in a sh int f0/0 from the router and a sh port or sh interface & sh ver from the switch it is connected to
07-09-2003 06:13 AM
Counters Table of the Switch(not cisco)
Drop Events 0
Collisions 1
Broadcasts 570433516
Multicasts 162657941
CRC/Alignment Errors 2
Undersize Packets 0
Oversize Packets 0
Fragments 52769
Jabbers 0
Total Packets 1268268752
Total Octets 2288901892
64 Octets 625565685
65-127 299739035
128-255 235663343
256-511 50669245
512-1023 16118860
1024-1518 40459815
Gaci2620#sh int f 0/0
FastEthernet0/0 is up, line protocol is up
Hardware is AmdFE, address is 0009.b7f4.9a00 (bia 0009.b7f4.9a00)
Internet address is X.X.X.X/16
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/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 never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 31 drops
5 minute input rate 19000 bits/sec, 28 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
573534 packets input, 47068603 bytes
Received 517133 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
63198 packets output, 8779459 bytes, 0 underruns(0/0/0)
0 output errors, 0 collisions, 6 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Gaci2620#
I have the same architecture with router 3640 and I use straight cable, but for 2620 or 2620XM it's neccessary to use Cross cable. Strange No ?
07-09-2003 06:17 AM
Is there any way to verify if the directly connected switch is losing power ? This would cause the FE interface to bounce .
07-09-2003 06:39 AM
Name 6H303-48
Status
Slot No. 6
Serial No. 01470002050F
Firmware Rev 05.02.03
BOOT Rev 03.03.01
Operation Mode 802.1Q Switching
System Descr Enterasys Networks 6H303-48 Rev 05.02.03 01/11/02--13:37 ofc
System Uptime 248 days, 13:13:56
The port was previously use by router 7507 for more 5fyears and there no problem on it.
What do you think about HSRP disturb ?
07-09-2003 06:44 AM
I do not think it is a problem with HSRP , htis would not cause protocol to bounce , is there any logs on the directly connected switch , Can you see if the port on that switch is losing carrier ? Another possiblility is the FE is getting hammered with traffic and this is causing the protocole to drop, you could be having a spanning tree loop or a broadcast storm that is causing the protocol to drop
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: