From: Mihai Petcu (mpetcu2004@yahoo.com)
Date: Sun Mar 06 2005 - 04:41:14 GMT-3
Jongsoo,
Try also using "debug ip rip" command and see
what networks are advertised to the BB router.
This way you can see if the summary address
configured on Ethernet 2 (in your example) is really
advertised to BB.
Also, you can verify if disabling "ip
split-horizon" is necessary or not.
HTH,
Mihai
--- Jongsoo.Kim@Intelsat.com wrote:
> Just replace step 4 and 5 with this new 4)
>
> 4) validate the summarization with " show ip
> protocols" command.
>
> router#show ip protocols
> Routing Protocol is "rip"
> Sending updates every 30 seconds, next due in 8
> seconds
> Invalid after 180 seconds, hold down 180, flushed
> after 240
> Outgoing update filter list for all interfaces is
>
> Incoming update filter list for all interfaces is
>
> Redistributing: rip
> Default version control: send version 2, receive
> version 2
> Interface Send Recv Triggered RIP
> Key-chain
> Ethernet2 2 2
>
> Ethernet3 2 2
>
> Ethernet4 2 2
>
> Ethernet5 2 2
>
> Automatic network summarization is not in effect
> Address Summarization:
> 12.11.0.0/16 for Ethernet2 <=====
>
>
> This is from cisco document.
>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1830/products_feature_guid
> e09186a0080087ad1.html
>
>
> -----Original Message-----
> From: Kim, Jongsoo
> Sent: Saturday, March 05, 2005 9:14 PM
> To: ccielab@groupstudy.com
> Subject: RE: Summary address for rip
>
>
> I like to share this with you folks.
> On lab test, if I were asked to do rip
> summary-address, I will do the
> following.
>
> 1) configure a proper summary command.
> 2) disable ip split-horizon for summary address to
> be advertise.
> 3) configure distribute-list out to manually
> subsitite the role of ip
> split-horizon that was diabled on setp 2.
> 4) in order to validate, turn on "debug ip icmp" and
> extended-ping with some
> vague source address within summary-address.
> 5) I should see proper debug messages of ping
> response from BB router if
> summary address were advertized to BB.
>
> I hope I help someone to save precious 3 points on
> tricky and mighty rip (
> ^^).
>
> Regrads
>
> Jongsoo
>
> -----Original Message-----
> From: Kim, Jongsoo
> Sent: Saturday, March 05, 2005 4:12 PM
> To: bdennis@internetworkexpert.com;
> ccielab@groupstudy.com
> Subject: RE: Summary address for rip
>
>
> Brian
>
>
> Your email influence me with some other thought.
> Maybe, I will ping with some vague source address
> within summary address and
> will do "debug ICMP".
>
>
> Jongsoo
>
> -----Original Message-----
> From: Kim, Jongsoo
> Sent: Saturday, March 05, 2005 4:07 PM
> To: 'Brian Dennis'; ccielab@groupstudy.com
> Subject: RE: Summary address for rip
>
>
> Brian
>
> I think ping may still work even if BB router
> doesn't have summary route
> because otherwise, it will have specific routes.??
>
> Regards
>
> Jongsoo
>
> -----Original Message-----
> From: Brian Dennis
> [mailto:bdennis@internetworkexpert.com]
> Sent: Saturday, March 05, 2005 3:48 PM
> To: Kim, Jongsoo; ccielab@groupstudy.com
> Subject: RE: Summary address for rip
>
>
> <Quote>
> If summary route is announced to BB router, there is
> no way to find if
> it
> work or not.
> </Quote>
>
> It would actually be really easy to test. Just
> create a loopback
> interface (or use an existing interface) that has an
> IP address in part
> of the summarized range and then ping the BB router
> sourcing the ping
> off of the loopback (or existing interface). If you
> get a reply to the
> ping, you will know that the BB is receiving the
> summarized route.
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> bdennis@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Jongsoo.Kim@Intelsat.com
> Sent: Saturday, March 05, 2005 10:49 AM
> To: ccielab@groupstudy.com
> Subject: Summary address for rip
>
> I am sure many of you know about this.
> This is totally news to me. ( I have obvioulsy
> underestimated the
> mighty
> RIP!)
>
> As passive interface behaves differently between Rip
> and EIGRP, so does
> ip
> summary-address.
> For rip, Ip split-horizon has be to diable for
> summary-address to be
> advertise, while EIGRP don't care about it.
> If summary route is announced to BB router, there is
> no way to find if
> it
> work or not.
> For rip, Ip split-horizon has be to diable for
> summary-address to be
> advertise, while EIGRP don't care about it unless
> you out things right!
> This is the very reason I believe Rip is the most
> tricky in IGP!!!
>
> See below I copy from IOS command.
>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_command_
> refe
> rence_chapter09186a008010a39d.html#wp1019063
>
<http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_command
> _ref
> erence_chapter09186a008010a39d.html#wp1019063>
>
> In the following example the major network is
> 10.0.0.0. The summary
> address
> 10.2.0.0 overrides the autosummary address of
> 10.0.0.0, so that 10.2.0.0
> is
> advertised out Ethernet interface 1 and 10.0.0.0 is
> not advertised.
> Note <<...OLE_Obj...>> If split horizon is enabled,
> neither autosummary
> nor
> interface summary addresses (those configured with
> the ip
> summary-address
> rip command) are advertised.
> router rip
> router interface e1
> ip address 10.1.1.1 255.255.255.0
> ip summary-address rip 10.2.0.0 255.255.0.0
> no ip split-horizon
>
=== message truncated ===
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:41 GMT-3