Issues with FastEthernet port on the 2621 : RESOLVED

Kalabin

Well, I have been beating my head over this and can't figure it out. What im trying to do is just connect my 2621 to my 3500XL switch. However this is proving to be a royal pain. The issue im running into is the following.

Issue: When connected from FA0/1 on the 2621 to FA0/1 on the 3500 the port goes link up / down constantly, however if I plug the same port from the 2621 and plug it into a cheap Linksys router it connect's right up link stay's up data passes through fine. Port is administrativly up, protocol down.

-- Steps Taken --

- erased running config, vlan.dat on switch
- erased running config on router
- forced 100Mbps / Full duplex on both router and switch.
- forced 10Mbps / Full duplex on both router and switch.
- forced 100Mbps / Half duplex
- Forced 10Mbps / half duplex
- replaced straight-through cable's 5 different times.
- put STP to Fastport
- verified FA0/1 on switch is in Management VLAN.
- tried putting fa0/1 in switchport trunk, dot1q encap

So far im at a loss. The 2501 connect's fine to the 3500. The 2621 does not want to.

gojericho0

What IOS are you using on the 2621 and the 3500? There may be a possible bug

Could you copy and paste a sh int on the interfaces both ints when connecting the 2621 router and switch interface as well as a debug output on the interface? Before you do this run clear counters to reset the interface statistics. (Trying to make sure the keepalives are the same as well if anything else jumps out)

Kalabin

Yeah I can do that when I get home tonight, however I did try with no keepalive to see if that was the issue. When I did a debug all, the only thing it would state for the fa0/1 int was possible issue with the cable / module. But then at the same time if I disconnect from the 3500 and plug into the linksys router it would instantly go up and up and recieve an IP via DHCP from the cheap linksys.

gojericho0

Have you tried forcing it up with no keepalive?

Kalabin

Yeah, I did the no shutdown, with forced keepalive, along with STP fastport etc. I implimented each of the troubleshooting step's one at a time and copied the running config, then reloaded it.

So, when I get home tonight im going to take your advice and take a look at the IOS of the 2621 and the 3500. It still just doesnt make sense as to why they wont talk to one another, but all other devices work fine. Only an issue with the two of them.

I need to figure this out tonight so I can study up for my case study due wed... good times.

Kalabin

Version info from the 2621

---

Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IS-M), Version 12.3(1a), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Fri 06-Jun-03 22:09 by dchih
Image text-base: 0x80008098, data-base: 0x819D9744

ROM: System Bootstrap, Version 12.2(7r) [cmong 7r], RELEASE SOFTWARE (fc1)

Router uptime is 22 hours, 25 minutes
System returned to ROM by reload
System image file is "flash:c2600-is-mz.123-1a.bin"

cisco 2621XM (MPC860P) processor (revision 0x100) with 93184K/5120K bytes of mem
ory.
Processor board ID JAE07420DZK (3519801902)
M860 processor: part number 5, mask 2
Bridging software.
X.25 software, Version 3.0.0.
2 FastEthernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
32K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)


Version info from Cisco 3500XL

---

Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5)WC11, RELEASE SOFTWA
RE (fc1)
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 11-Jan-05 10:23 by antonino
Image text-base: 0x00003000, data-base: 0x00351B48

ROM: Bootstrap program is C3500XL boot loader

Switch uptime is 2 minutes
System returned to ROM by power-on
System image file is "flash:c3500xl-c3h2s-mz.120-5.WC11.bin"


cisco WS-C3524-XL (PowerPC403) processor (revision 0x01) with 8192K/1024K bytes
of memory.
Processor board ID FAB0601P37J, with hardware revision 0x00
Last reset from power-on

Processor is running Enterprise Edition Software
Cluster command switch capable
Cluster member switch capable
24 FastEthernet/IEEE 802.3 interface(s)

Kalabin

And to add to it. While debugging the interface on both the router and switch, the only thing that show's up is the following. Which show's up without debugging.

00:08:18: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 15 times per min
00:08:18: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:19: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:20: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:21: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:23: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 15 times per min
00:08:23: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:23: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:25: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:25: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:27: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:28: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 16 times per min
00:08:28: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:29: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:30: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:08:31: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:08:32: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down

Kalabin

Welp, finally broke down after trying everything I could with the IOS and deleted everything on the flash. I had to be very sneaky and get a known good IOS from a certaint campus which will remain unknown. However, with the clean flash, and IOS V12.2(23) it's working like a champ.

Bah, wish I would have had a crossover cable sooner. Broke down and grabbed my old man's cable testers along with some cat5 and started making some spare cable's for the future.

Thanks for the hint at the IOS earlier, that was going to be my last resort. Could have swore it was some stupid setting I was over looking, seeing as how it would talk to every other device besides the 3500.