Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

Getting RIP routes over a Non-Working FR PVC

$
0
0

Hello community,

I accidentally misconfigured my frame-relay connection between R6 and BB1

BB1 s1/1---------------- s1/0 R6

54.1.1.254                 54.1.1.6
DLCI 101                    DLCI 111

The thing is, I never realized until I tried to ping some 212.18.x.x/24 networks I was receiving from BB1 and failed. I started my troubleshooting by pinging BB1 at 54.1.1.254 and when it failed I did the following:

R6(config-if)#do debug ip rip
*Jan 22 22:20:00.751: RIP: received v2 update from 54.1.1.254 on Serial1/0
*Jan 22 22:20:00.751:      212.18.0.0/24 via 0.0.0.0 in 1 hops
*Jan 22 22:20:00.751:      212.18.1.0/24 via 0.0.0.0 in 1 hops
*Jan 22 22:20:00.751:      212.18.2.0/24 via 0.0.0.0 in 1 hops
*Jan 22 22:20:00.751:      212.18.3.0/24 via 0.0.0.0 in 1 hops

R6(config-if)#
*Jan 22 22:20:04.766: RIP: sending v2 update to 224.0.0.9 via Loopback0 (150.1.6.6)
*Jan 22 22:20:04.766: RIP: build update entries
*Jan 22 22:20:04.766:   54.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Jan 22 22:20:04.766:   212.18.0.0/24 via 0.0.0.0, metric 2, tag 0
*Jan 22 22:20:04.766:   212.18.1.0/24 via 0.0.0.0, metric 2, tag 0
*Jan 22 22:20:04.766:   212.18.2.0/24 via 0.0.0.0, metric 2, tag 0
*Jan 22 22:20:04.766:   212.18.3.0/24 via 0.0.0.0, metric 2, tag 0
*Jan 22 22:20:04.766: RIP: ignored v2 packet from 150.1.6.6 (sourced from one of our addresses)
R6(config-if)#do u all

As you can see, R6 is receiving the 212.18.x.x/24 networks from 54.1.1.254 so then I questioned myself, how am I getting these RIP updates when I'm not even able to ping 54.1.1.254 so I continued my troubleshooting with the following commands:


R6(config-if)#do sh frame map
Serial1/0 (up): ip 54.1.3.254 dlci 51(0x33,0xC30), dynamic,
              broadcast,
              CISCO, status defined, active
Serial1/0 (up): ip 54.1.2.254 dlci 100(0x64,0x1840), dynamic,
              broadcast,
              CISCO, status defined, active
Serial1/0 (up): ip 54.1.1.254 dlci 111(0x6F,0x18F0), static,
              broadcast,
              CISCO, status deleted

So here I realized I had statically configured a DLCI of 111 on R6 when it should actually be 101 (that's what BB1 is configured as), but then again I am scratching my head wondering how can R6 be possibly getting the RIP updates from 54.1.1.254 when BB1&R6 do not have a working frame-relay PVC. Ping reveals they are unable to communicate:

R6(config-if)#do ping 54.1.1.254
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 54.1.1.254, timeout is 2 seconds:
..
Success rate is 0 percent (0/2)

Yet the 212.18.x.x/24 networks are installed R6's routing table as well as in the rest of the devices R1-R6, SW1-SW4:

R6(config-if)#do sh ip route | i 212.18
R     212.18.0.0/24 [120/1] via 54.1.1.254, 00:00:24, Serial1/0
R     212.18.1.0/24 [120/1] via 54.1.1.254, 00:00:24, Serial1/0
R     212.18.2.0/24 [120/1] via 54.1.1.254, 00:00:24, Serial1/0
R     212.18.3.0/24 [120/1] via 54.1.1.254, 00:00:24, Serial1/0

How can this be happening please?


Viewing all articles
Browse latest Browse all 10744

Trending Articles