I absolutely agree here wit Kim.  If you do it in a lab, and run the debugs
as Terry has done, you will see what is really happening : )

On Sun, Sep 13, 2009 at 12:38 PM, Bryan Bartik <[email protected]> wrote:

> Jay,
>
> Why don't you lab it and see the real behavior? Terry did a pretty good job
> of explaining it.
>
> On Sun, Sep 13, 2009 at 10:34 AM, Jay <[email protected]> wrote:
>
>> Hi All,
>>     Just for clarification let me make sure I also understand. Cisco
>> technology handbook states "RIP uses a single routing metric (hop count) to
>> measure the distance between the source and a destination network. Each hop
>> in a path from source to destination is assigned a hop count value, which is
>> typically 1. When a router receives a routing update that contains a new or
>> changed destination network entry, the router adds 1 to the metric value
>> indicated in the update and enters the network in the routing table. The IP
>> address of the sender is used as the next hop. "
>>     From that it seems to me that if RIP sends from R1 with a value of 10
>> , R2 places in RIB with a value of 11, and sends upstream with a value of
>> 11. Does that seem accurate?  I misread the replies initially and it made me
>> want to verify my understanding of the behavior.
>>
>> Thanks,
>> Jay Klus
>>
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>>
>
>
> --
> Bryan Bartik
> CCIE #23707 (R&S), CCNP
> Sr. Support Engineer - IPexpert, Inc.
> URL: http://www.IPexpert.com
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>


-- 
Regards,

Joe Astorino - CCIE #24347 R&S
Technical Instructor - IPexpert, Inc.
Cell: +1.586.212.6107
Fax: +1.810.454.0130
Mailto:  [email protected]
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to