!---split horizon is enabled by default,therefor I am not going to write this command:"ip split-horizon"
The definition of the split horizon is :
(Split Horizon blocks routing update to be sent to over the same interface that the route was learned from).
To apply this definition to the scenario above, R1 should receive updates from another router, then split horizon will not let R1 to advertise updates from the same interface where it received them.--> that means split horizon should not affect routes generated by R1 itself, it only should affect routes received from another router.
But my confusion how can we satisfy the note below (quote from the link above)!!!!! :
"If split horizon is enabled, neither an autosummary address nor the interface summary-address is advertised".
My understanding of split horizon is: "it prevents the router from advertising routes out any interface from which the route was learnt". In your case split horizon would affect routes originated from R1 as well.
If you are testing this is in a lab setup then you could configure an interface summary address, enable 'debug ip rip' and look at the rip updates and you would see the summary address getting suppressed by R1. Unfortunately, I don't have access to my lab at this time to post the output.
Basically split horizon affects how received routes are being advertised, not the routes generated locally. So in your case, 10.2.0.0 255.255.0.0 will be the route advertised out of the interface.
The Cisco literature is a little bit confusing. I think it is meant to say the same as "everything received will not be advertised out of the same interface". Becasue RIP by default does classful auto-summary, so the "everything" here can only be anto-summarized route or the "ip summary-address" route configured on the neighboring RIP router.
You can verify it in lab using another router as R2 and configure several /24 networks on it and do a "ip summary-address". You should see 10.2.0.0 255.255.0.0 on R2 as received from R1 but not advertied from R2 to R1 again.
No. 10.2.0.0 255.255.0.0 is locally generated summary route, advertised out by R1. You should see the route on a neighboring RIP router as received from R1. With split horizon, the neighboring router will not advertise the route out of the same interface back to R1.
((No. 10.2.0.0 255.255.0.0 is locally generated summary route, advertised out by R1. You should see the route on a neighboring RIP router as received from R1. With split horizon, the neighboring router will not advertise the route out of the same interface back to R1)).
This is exactly how I understood split Horizon (your explaination is what I understood from the definition of split horizon).
Now my confusion as i have mentioned in my early post can we satisfy the note below :
((((("If split horizon is enabled, neither an autosummary address nor the interface summary-address is advertised".))))),,,,
In our scenario (example) autosummary and summary address (10.2.0.0 255.255.0.0 locally generated route) has been advertised by R1 to neighbor/s!!!!!!now the neighor/s (This is not my concern at this stage, my concern is R1) should not advertise the route back to R1 from the same interface it received.
Now according to the note, R1 should not have advertise 10.2.0.0
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...