help me in RIP v2

Hello , I am Rohit and preparing for CCIE R&S lab. doing progress with INE 4.2 techno labs and i get stucked.
in RIP v2, there is some complexity between R2 and BB2. both interfaces are pinging, of 192. network but are not able to receive route updates from each other. why?

Comments

  • Hi,

    I believe there is a FR connection between R2 and BB2, can you look on FR mapping, is there broadcast keyword or not? If not put brodcast keyword.

    Another thing, check on BB2 whether RIP authentication is enabled or not?

    can you turn on the RIP debugging and paste output here?

  • Start with troubleshooting the RIP protocol:

    1. Check routing table - there are no RIP routes learnt
      • show ip route rip
    2. Check IP protocols - check RIP configuration
      • show ip protocols
    3. Check RIP database - which routes are in database
      • show ip rip database
    4. Debug RIP updates - see what information is sent/received
      • debug ip rip
    5. Debug IP packets for multicast group 224.0.0.9 - check if RIP updates are sent/received
      • access-list 9 permit 224.0.0.9
      • debug ip packet detailed 9

    You'll find your answers in one of these steps.

     

  • 1. this is frame relay mapping of R2

     

    Rack1R2#sh frame-relay map
    Serial1/0.1 (up): point-to-point dlci, dlci 205(0xCD,0x30D0), broadcast
    status defined, active

    -----------------------------------------------------------------

    2. debugging rip in R2

     


    Rack1R2#
    *Feb 18 17:55:11.179: RIP: sending v2 update to 224.0.0.9 via Serial1/0.1 (155.1.0.2)
    *Feb 18 17:55:11.179: RIP: build update entries
    *Feb 18 17:55:11.179: 150.1.2.0/24 via 0.0.0.0, metric 1, tag 0
    *Feb 18 17:55:11.255: RIP: received v2 update from 155.1.0.5 on Serial1/0.1

    *Feb 18 17:55:11.255: 54.1.1.0/24 via 155.1.0.1 in 3 hops

    *Feb 18 17:55:11.255: 150.1.1.0/24 via 155.1.0.1 in 2 hops

    *Feb 18 17:55:11.255: 150.1.3.0/24 via 155.1.0.3 in 2 hops

    *Feb 18 17:55:11.255: 150.1.4.0/24 via 155.1.0.4 in 2 hops

    *Feb 18 17:55:11.255: 150.1.5.0/24 via 0.0.0.0 in 1 hops


    *Feb 18 17:55:11.255: 150.1.6.0/24 via 155.1.0.1 in 3 hops


    *Feb 18 17:55:11.255: 150.1.7.0/24 via 155.1.0.3 in 3 hops

    ops
    *Feb 18 17:55:11.355: RIP: received v2 update from 155.1.0.5 on Serial1/0.1

    *Feb 18 17:55:11.355: 212.18.0.0/24 via 155.1.0.1 in 4 hops

    Rack1R2#
    *Feb 18 17:55:11.355: 212.18.1.0/24 via 155.1.0.1 in 4 hops

    *Feb 18 17:55:11.355: 212.18.2.0/24 via 155.1.0.1 in 4 hops

    *Feb 18 17:55:11.355: 212.18.3.0/24 via 155.1.0.1 in 4 hops

    Rack1R2#
    *Feb 18 17:55:20.415: RIP: sending v2 update to 224.0.0.9 via Loopback0 (150.1.2.2)

    *Feb 18 17:55:20.415: RIP: build update entries


    *Feb 18 17:55:20.415: 54.1.1.0/24 via 0.0.0.0, metric 4, tag 0


    *Feb 18 17:55:20.415: 150.1.1.0/24 via 0.0.0.0, metric 3, tag 0

    *Feb 18 17:55:20.415: 150.1.3.0/24 via 0.0.0.0, metric 3, tag 0

    *Feb 18 17:55:20.415: 212.18.3.0/24 via 0.0.0.0, metric 5, tag 0

    *Feb 18 17:55:20.415: RIP: ignored v2 packet from 150.1.2.2 (sourced from one of our addresses)

    *Feb 18 17:55:20.415: RIP: ignored v2 packet from 150.1.2.2 (sourced from one of our addresses)



     

    3. i have pasted the rip information from BB2

     

    Routing Protocol is "rip"
    Outgoing update filter list for all interfaces is (prefix-list) LOOPBACKS
    Incoming update filter list for all interfaces is (prefix-list) DENY_DEFAULT
    Sending updates every 30 seconds, next due in 7 seconds
    Invalid after 180 seconds, hold down 180, flushed after 240
    Redistributing: connected, rip
    Default version control: send version 2, receive version 2
    Interface Send Recv Triggered RIP Key-chain
    Ethernet0/0 2 2 RIP
    Automatic network summarization is in effect
    Maximum path: 4
    Routing for Networks:
    192.10.1.0
    Routing Information Sources:
    Gateway Distance Last Update
    Distance: (default is 120)
    ----------------------------------------------------------------------------

  • Hi...

    in between R2 and BB2 its Fastethernet connection.

    Check with RIP v1 /V2 send and receive command configuration on the interfcae connected to BB2.

     

    /Ganpat

  • Another thing, check on BB2 whether RIP authentication is enabled or not?

     

    Turn on authentication or you will not receive any routes.


    key chain RIP

    key 1

    key-string CISCO

    !

    interface FastEthernet0/0

    ip address 192.10.1.2 255.255.255.0

    ip rip authentication mode md5

    ip rip authentication key-chain RIP

  • I agree with Dennis, the connection between R2 and BB2 is setup to use authentication, so you really need that here.

  • Dennis confirmed there is authentication enabled on BB2, configure RIP authentication on R2 with same key-string.

  • Hello , I am Rohit and preparing for CCIE R&S lab. doing progress with INE 4.2 techno labs and i get stucked.
    in RIP v2, there is some complexity between R2 and BB2. both interfaces are pinging, of 192. network but are not able to receive route updates from each other. why?

    If you are doing some vol1 task, its explicitly mentioned in there about authentication between the devices. In some labs if its not mentioned then you probably figure out using debug ip rip command where there is authentication or not. Its quite easy to figure out that but the most difficult part of the puzzle is to determine the password for that we have to do very low level debugging using dump. However this is only true with clear text password but if password is md5 then there is no way to determine that password (except you are trying to bruteforce)

  • thanks to all of you for your valuable guidance

Sign In or Register to comment.