routers aren't communicating

Hi,
I'm trying to get 2 routers talking to each other.
r1 = 2610 IOS 12.0
e0/1 ip address = 192.168.101.210 255.255.255.0

r2 = 2610xm IOS 12.4
f0/0 ip address = 192.168.101.200 255.255.2550
speed 10
duplex full

r1 doesn't accept speed or duplex commands (old IOS?)
I'm using a crossover cable, I've crimped 2 cables so far.

line status is up, protocol status is down (on both routers). I've had both interfaces works in other configurations (ie connecting each router to a switch).

Any ideas on what might be the problem? I might try a pre-crimped crossover cable tomorrow, but I don't think that's the problem.

thanks

Find more posts tagged with

SAVE $250 on Your CISCO Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View CISCO Boot Camps

Comments

shmish

r2#show running-config
Building configuration...

Current configuration : 777 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname r2
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$ISN8$lcBBzd2KmEX1fmXb8/DQH/
!
no aaa new-model
memory-size iomem 20
no network-clock-participate slot 1
no network-clock-participate wic 0
no ip routing
no ip cef
!
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
interface FastEthernet0/0
 ip address 192.168.101.200 255.255.255.0
 no ip route-cache
 speed 10
 full-duplex
!
ip forward-protocol nd
!
!
ip http server
no ip http secure-server
!
control-plane
!
line con 0
 login
line aux 0
line vty 0 4
 password xxxx
 login
!
!
end

r1#show running-config
Building configuration...

Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r1
!
enable secret 5 $1$wsVP$wrbtRsfr/23G7MOOtq22j1
!
memory-size iomem 10
ip subnet-zero
!
interface Ethernet0/0
 ip address 192.168.100.210 255.255.255.0
 no ip directed-broadcast
!
interface Serial0/0
 no ip address
 no ip directed-broadcast
 shutdown
!
interface Ethernet0/1
 ip address 192.168.101.210 255.255.255.0
 no ip directed-broadcast
!
ip classless
!
!
!
line con 0
 password xxx
 login
 transport input none
line aux 0
line vty 0 4
 password xxx
 login
!
no scheduler allocate
end

mikej412

Do the interface statistics show any errors?

Try 10Mb and HALF Duplex.

It's always a good idea to have a known good working cable to try so that you can rule out a home made cable issue.

shmish

Yes, I've tried half duplex on r2.
I'm not sure I know what you mean by interface statistics, do you mean the results from #show interface f0/0 ? If that is what you mean, then nothing really stuck out at me.

Ya, I do wish I had a known good crossover cable with me.

Netwurk

On the 2500's, the 10Mbps interfaces were half duplex and so you if you were connecting to a fast ethernet (100Mbps) interface, you had to ratchet it down to 10/half. Auto might work in some cases, but why chance it?

Anyhow, I'm assuming it's the same with most non-XM 2600s.

I don't think upgrading your IOS would help, since you'd still be stuck with the hardware limitations of the old interface.

Try this on the 2610XM

conf t
int fa 0/0
speed 10
duplex half

shednik

What are the interface statuses reporting? maybe a sh int on either side??

ilcram19-2

may be this has something to do

no ip routing
no ip cef

go to gobla config mode and type ip routing

CaptainCharisma

As Mike pointed out the duplex mismatch would be an issue. Routing would be an issue once you try to send packets from another network across that link because of the missing routes.

My question after looking at the configs though is that on your 2610 (r1) you have two ethernet interfaces listed in the config, ethernet 0/0 and ethernet 0/1. The non-XM 2610 has 1 built in ethernet interface and that is your ethernet 0/0. Do you have a WIC or Network module plugged into this router that is adding another ethernet interface? If you do have more than one ethernet interface on this router then you may have the cable plugged into the wrong interface because you have to 2 different networks in that config both on different interfaces.

Also (maybe Mike can answer this one) if he has a WIC or NM with additional ethernet interface(s) wouldn't it show up as ethernet 1/0, etc? I ask because in the config he provided for r1 it has 2 ethernet interfaces (but the 2610 only has 1 by default) so wouldn't any added in interfaces increment the number in front of the slash?

rossonieri#1

Also (maybe Mike can answer this one) if he has a WIC or NM with additional ethernet interface(s) wouldn't it show up as ethernet 1/0, etc?

the easy way to review what kind of physical interface, how many of them and to which naming they had, and their configured IPs is #sh ip int brief.

shednik

ilcram19-2 wrote: »

may be this has something to do

no ip routing
no ip cef

go to gobla config mode and type ip routing

I missed that...do that first!!

shmish

I'll check out the ip routing when I'm at home tonight. I did have rip-2 routing enabled but then took it off. I'm just learning this stuff, but it seems to me that ip routing shouldn't be required since it is a direct connection between the interfaces.

The 2610xm only has 1 fast ethernet interface right now. I'm still waiting to get a WIC-1T for it.

Despite crimping 3 xover cables, I think it must be a cable problem. Later last night I tried connecting switch1 to switch 2, with no luck using any of the cables. I've had both sw1 and sw2 connected to both r1 and r2 now so I'm reasonably certain that most/all(?) of my interface settings are okay.

I'm purchasing two new xover cables today and see where I'm at tonight.

BTW, I tried drawing my network topology using Visio and what a pain in the ass! Text and arrows were snapping to each other all over the place and it was difficult to control. If anyone has any tips on how to use Visio efficiently for this, I'd love to hear it. Maybe I'm starting with inappropriate templates/stencils.

thanks

rossonieri#1

@ shednik

its directly connected between 2 interfaces in the same subnet - you dont need ip routing. so forcing those 2 using half duplex, same speed and crossover cable would be the best thing to try.

shmish

Unbelievable. Bad cable(s). I bought two xovers today, and that was the problem. Who knew that I would crimp 4 straight-thru cables ok, whereas all 3 xovers are bad (and I even have the pins correct).

My apologies for causing a fuss over cables, and many thanks to all of the replies.

s