IGRP into RIP distribution leads to Inaccessible routes

Simple setup with big problems and i cant pinpoint it. Pleasy help me out with this one guys.

L1-L3 Topology:

2 routers called Router6 and Router8 Router6 ser1 is wired to Router8 ser1 using network Router6 eth0 has network Router8 tokenRing0 has network

Routing Topology: Router6 has RIPv2 Router8 runs RIPv2 on its ser1 only and runs IGRP on tokenring. Router8 redistributes RIP into IGRP and reverse.

Problem: Router6 does all perfect with RIP Router8 receives RIP well and redistributes it into IGRP on the other interfaces BUT it markes those routes learned from RIP as "Inaccessible"

see debugoutput on Router8: Router8#debug ip rip Router8#debug ip igrp transactions

00:33:53: RIP: sending v2 update to via Serial1 ( 00:33:53: RIP: build update entries 00:33:53: via, metric 1, tag 0 00:34:00: RIP: received v2 update from on Serial1 00:34:00: via in 1 hops 00:34:00: via in 1 hops 00:34:21: RIP: sending v2 update to via Serial1 ( 00:34:21: RIP: build update entries 00:34:21: via, metric 1, tag 0 00:34:22: IGRP: sending update to via TokenRing0 ( 00:34:22: subnet, metric=8476 00:34:22: network, metric=Inaccessible 00:34:22: network, metric=Inaccessible


Dont tell me to use other routing protocols please, i want to understand the inner workings of IGRP for my certification.

Configs are:

Router6: ip subnet-zero ! interface Loopback1 ip address ! interface Ethernet0 ip address no ip route-cache ! interface Serial1 ip address no ip route-cache ! router rip version 2 passive-interface Ethernet0 passive-interface Loopback1 network network network no auto-summary ! ip classless

Router8: ip subnet-zero ! interface Serial1 ip address no ip route-cache no ip mroute-cache clockrate 2000000 ! interface TokenRing0 ip address no ip route-cache no ip mroute-cache ring-speed 16 ! router rip version 2 redistribute igrp 666 passive-interface TokenRing0 network no auto-summary ! router igrp 666 redistribute rip passive-interface Serial1 network ! ip classless

Reply to
Loading thread data ...

The metric in IGRP and RIP are totally different so you have to supply metric to routes when redistributing like this:

redistribute igrp 666 metric 1

redistribute rip metric 10000 1000 255 1 1500

or supply default metric in routing protocol using 'default-metric' command.

Reply to
Ivan Ostres


I am helping/trying to set up a connection between a FR T1 and ATM OC3.

We have them talking, but can't ping a computer sitting on the fastethernet port. It can telnet in, and ping the interfaces on the local computer but from a telenet session within the local router we can't ping back to the router. (*.254)

We are new to this have have been looking at all the reference material we can find but are missing what we are sure is an obvious thing.

If someone could point us inthe right direction we would greatly appreciate it. - -Kathy

This is the config.

2620t#show run Building configuration...

Current configuration : 993 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime service password-encryption ! hostname 2620 ! enable password ! ip subnet-zero ! ! no ip domain-lookup ip name-server ip name-server ! ! ! ! interface FastEthernet0/0 description connected to Internet ip address no ip redirects no ip unreachables no ip proxy-arp no ip mroute-cache speed auto half-duplex no cdp enable ! interface Serial0/0 description Connection 7206 ds3 atm ip address encapsulation frame-relay IETF frame-relay interface-dlci 16 ! ip classless ip route ip http server ip pim bidir-enable ! no cdp run snmp-server community public RO snmp-server location ! line con 0 exec-timeout 0 0 password login line aux 0 line vty 0 4 password login ! no scheduler allocate end

Reply to
Kathy White

Put in a default metric:

router rip redistribute blahblahblah default-metric 1

Reply to
John Agosta

thanks a lot Ivan and John the metric is indeed overcalculated (delay 16777215 as default) without the default-metric or redistribute ..... metrics, and thus marked as inaccessible thanks for helping me out with this one, i owe you guys a beer ;-)

Reply to

Hello Kathy,

when you say that you cannot ping back to the router with IP address

*.254 I assume that means:

You have a TELNET session to the router of which you have posted the configuration. From there, you are trying to ping a device that is connected to the FastEthernet port of that router, and that device has IP address ? Is the line protocol on your FastEthernet interface up ? Can you check if the subnet mask on the device with IP address is correct ( ?



Reply to

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.