rip updates ...

what is the reason , some times it says sending v2 flash update

 and some time  sending v2 update . is it code differecnce ? or some any features configured in first case missing in second ???

 

RouterA#debug ip rip
RIP protocol debugging is on00:34:32: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet8/0 (172.16.1.1)
00:34:32: RIP: build flash update entries
00:34:32: 10.10.1.0/24 via 0.0.0.6, metric 1, tag 0


00:34:32: RIP: sending v2 flash update to 224.0.0.9 via Loopback (10.10.1.1)
00:34:32: RIP: build flash update entries


00:34:32: 10.0.0.0/8 via 0.6.0.0, metric 2, tag 0
00:34:32: 172.16.1.0/24 via 0.0.0.0, metric 1, tag 0
00:34:32: RIP: ignored v2 packet from 16.10.1.1 (sourced from one of our addresses)
06:34:33: RIP: received v2 update from 172.16.1.2 on FastEthernet0/6
66:34:33: 16.6.0.0/8 via 6.0.6.6 in 1 hops
66:34:44: RIP: sending v2 update to 224.6.6.9 via FastEthernet0/0 (172.16.1.1)
66:34:44: RIP: build update entries
66:34:44: 10.10.1.0/24 via 0.0.0.0, metric 1, tag 0

 

on another router !!

*Mar  1 04:40:13.614: RIP: sending v2 update to 224.0.0.9 via Loopback2121811 (212.18.1.1)
*Mar  1 04:40:13.618: RIP: build update entries
*Mar  1 04:40:13.618:   30.0.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.622:   30.1.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.626:   30.2.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.626:   30.3.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.630:   31.0.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.634:   31.1.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.634:   31.2.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.634:   31.3.0.0/16 via 0.0.0.0, metric 4, tag 0
*Mar  1 04:40:13.634:   54.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 04:40:13.634:   155.1.0.0/24 via 0.0.0.0, metric 3, tag 0
*Mar  1 04:40:13.634:   155.1.13.0/24 via 0.0.0.0, metric 3, tag 0
*Mar  1 04:40:13.634:   155.1.45.0/24 via 0.0.0.0, metric 3, tag 0
*Mar  1 04:40:13.634:   155.1.67.0/24 via 0.0.0.0, metric 2, tag 0

 

Comments

  • ehtu - This is a triggered update.

    Andrius
  • great ! learned that feature too....

    is my logic correct ...

    configure rip  such that only intended receivers gets the update ..,make sure to send only out of inerface that are required ..

     look at the debug below ...

    BB1#
    *Mar  1 06:45:55.958: RIP: received v2 update from 54.1.1.6 on Serial0/0
    *Mar  1 06:45:55.966: RIP: Update contains 15 routes
    *Mar  1 06:45:56.726: RIP: sending v2 update to 224.0.0.9 via Loopback2121821 (212.18.2.1)
    *Mar  1 06:45:56.734: RIP: Update contains 18 routes
    *Mar  1 06:45:56.738: RIP: Update queued
    *Mar  1 06:45:56.738: RIP: Update sent via Loopback2121821
    *Mar  1 06:45:56.738: RIP: ignored v2 packet from 212.18.2.1 (sourced from one of our addresses)

     

    what does  it mean ?  router sending updates from a logical  inerface where no one else is listening ? or is it saying that it is sourcing the updates from loopback ?

     

    plus notice the last line....it says ...ignoring packets  sources from one of our address..in my topology 212.18.2.1 is the loopback configured on BB1..  


    router rip

    ver 2

    passive interface default

    no passive interface fa0/0

    no passive interface s0/0

     

    will the above config suppresses the advertisments out of loopback ?

     

  •  

     

    configure rip  such that only intended receivers gets the update ..,make sure to send only out of inerface that are required ..

     

     

    ONLY intended receivers get update simply means...send them unicast updates..since a multicast or broadcast update is...well heard by a lot of hosts...

     

    router rip

    neighbor X.X.X.X    <-- the neighbor cmd makes rip send unicast updates to IP described by the command

     

    however this does NOT stop the multicasting/broadcasting of updates so add

    passive-interface default

     

     

     

    ..,make sure to send only out of inerface that are required ..

     

    no passive-interface <interface you want to send updates out of>

     

    HTH

     

     

     

    **<edit...

     

     

     

     

    what does  it mean ?  router sending updates from a logical  inerface where no one else is listening ? or is it saying that it is sourcing the updates from loopback ?

    with RIP you enable the routing protocol for interfaces...however you do that with a network statement with RIPv4

    if a network statement is done for a network and an interface happens to fall in the range of addresses encompassed by that network....then you send updates out of that interface...

    the mistake you are making here is assigning human logic to a stupid protocol...it merely does what its told to do...

     

     

     

  •  1) but does rip send update from loopback ?? a logical interface ?

    or does it imply that it is sourcing from a loopback ?

    2) in case if rip advirtises out of loopback ....how can we suppress the advirtisments ..i want the update to be send only on the interfaces where it is necessary  ?

    3) what does it mean when it says  RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses ?  

     

    is it that rip advirtises out of loopbacks and then drops it because it .....due to sourcing from its own address? ....guys please explain what the error means

    (sourced from one of our addresses )

     

  • ehtu,

    If I remember correctly, unless you configure passive-interface on your loopbacks, RIP will send updates out the loopbacks when the ip address is included in the network statements.

  •  1) but does rip send update from loopback ?? a logical interface ?

    or does it imply that it is sourcing from a loopback ?

    2) in case if rip advirtises out of loopback ....how can we suppress the advirtisments ..i want the update to be send only on the interfaces where it is necessary  ?

    3) what does it mean when it says  RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses ?  

     

    is it that rip advirtises out of loopbacks and then drops it because it .....due to sourcing from its own address? ....guys please explain what the error means

    (sourced from one of our addresses )

     

     

    i'm gonna do my best considering i have a cold...

     

     1) but does rip send update from loopback ?? a logical interface ?

     

    why does it matter to you what sort of interface it is.....<take a second and answer that for yourself>.?   if you wanna be able to ping the loopback..you better let all other routers know what that network exists...of which that loopback is a part of. <would this be a real world example...well ..maybe..maybe not...remember..the CCIE is NOT a reality based test..Morris said so!

     

     

     in case if rip advirtises out of loopback ....how can we suppress the advirtisments ..i want the update to be send only on the interfaces where it is necessary  ?

    seriously??? you are asking this on a CCIE level forum??? i refuse to answer this...go read..as pretty much everyone else on here (rauta excluded) has done so.  you CANNOT ask questions that are CCNA level on a CCIE forum and expect people to answer them.

     

     

     

    3) what does it mean when it says  RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses ?

     

    ditto..above..

     

     

    go read..Routing TCP/IP by Jeff doyle volume 1 and volume 2

    as all the rest of us did...MULTIPLE TIMES

     

     

     

     

  • thanks ! but i guess you dint understood my question ! or could be possible i dint got u !

    any way i got the answer below .

     


    I read two things into that requirement:

     


    "configure rip  such that only intended receivers gets the update"  << Use RIPv2 Neighbors/Unicast

     


    "make sure to send only out of inerface that are required"  << Passive interfaces

     


    In your debug, you see an update is queued and sent on the loopback, and then you see the ignore from the looped update:

     

     

    *Mar  1 06:45:56.738: RIP: Update queued
    *Mar  1 06:45:56.738: RIP: Update sent via Loopback2121821
    *Mar  1 06:45:56.738: RIP: ignored v2 packet from 212.18.2.1 (sourced from
    one of our addresses)

     


    Setting the loopback to passive will still advertise the network into RIP, but will suppress any advertisements out that interface. In RIP, passive interfaces will still receive advertisements, but on a loopback if you aren't sending them you won't receive them.

     


    Since the requirement specifically states that advertisements should ONLY be sent out of required interfaces, I would go with "passive default" and then "no passive-int" as needed, as you did in your RIP configuration.


    I think you got the second part of the requirement, but I'd read "neighbors" out of the first part.

    Best regards,

    Bob

  • Hi ehtu,

       Maybe Toxis is a little hard on you, but short answer is: you fill find people to answer basic, advanced and complex questions. However, this way you will not truly learn technology neither fast or reliable. You need to build some basics on your own, strugle to understand things, and if you need guidance on ceratin areas, of course ask questions. To asnwer your questions:

    1. whenver a routing protocol send an update/packet out of an interface, the source IP address of the packet is the primary IP address of the outgoing interface (BGP can be an exception to this rule, and IS-IS as it is not an IP protocol); so basically in your case, cause you enabled RIP on loopback interface with network command, is send updates out on its loopback and receives it back on its loopback, it also ignores it cause it sees it is sourced by itself, this is why you see those messages
    2. in RIP you can suppress multicast and broadcast updates wih "passive-interface" command
    3. i answered you in the first bullet, it sees an update from itself

    Also, flash update is not really a triggered update (RIP triggered updates can be enabled on point-to-point medias like PPP for example and basically suppresses regular, 30 seconds, updates). Flash update is an update determined by a change in RIP database, by addition or deletion of a prefix.

    Good luck with your studies!

  • Hi ehtu,

     

    Flash Updates sends new update as soon as a route fails. 

    R2(config)#router rip

    R2(config-router)#flash-update-threshold 15

    R2#show ip protocols | in Flash

     Flash update is suppressed when next update due within 15 seconds

    When you execute flash-update-threshold command that flash update will be  suppressed,  if the next regular update is due in either 15  seconds.

    HAPPY STUDY

    [:D]

     

  • Hi nnn,

       Flash updates are not only when a prefix dissapers from RIB/RIP database, but also when a prefix is added to RIP database and gets installed in the RIB.

    Good luck with your studies!

  • You are correct, word should be "changes" instead of disapears on RIP/RIB database:) Fingers were running faster than thinking....

    HAPPY STUDY

    [:D]

     

    Hi nnn,

       Flash updates are not only when a prefix dissapers from RIB/RIP database, but also when a prefix is added to RIP database and gets installed in the RIB.

    Good luck with your studies!

     

  •  

    christian is absolutely right.

     

    i ws a little hard on the guy....i took my annoyance for Rauta and took it out on this guy..

     

    anyhow...

     

    decouple, mentally the networks you advertizing and what interfaces those networks get advertised out of. The two do not have to go together.

    ie>>you do not have to advertise a network out an interface belonging to that network 

     

    REMEMBER >> a passive interface does not send updates...that does not mean another interface that is not passive  does not send updates about interfaces that are passive

     

    as i said before...you are assigning human logic to stupid protocols...

     

     

     

    HTH

     

  • thank you guys  

     

     

  • thank you guys  

     

     

    I Still recommend that you read the jeff doyle books....

     

    i think those books should be a right of passage of sorts...

     

     

Sign In or Register to comment.