[j-nsp] Prefer RIP Neighbor
Shane Ronan
sronan at fattoc.com
Thu Mar 11 23:50:47 EST 2010
config snippet, show rip neighbors and rip routes are below.
As you can see in the routes, despite the higher metric on
ge-0/1/2.10, some routes are preferred via ge-0/1/0.10
Thoughts?
Thanks for your help!
---------------------------------------------------------------
set protocols rip send multicast
set protocols rip receive version-2
set protocols rip holddown 75
set protocols rip update-interval 30
set protocols rip group SFTI export advertise-rip-route
set protocols rip group SFTI neighbor ge-0/0/3.0
set protocols rip group SFTI neighbor ge-0/1/1.10
set protocols rip group SFTI neighbor ge-0/1/0.0
set protocols rip group SFTI neighbor ge-0/1/2.10 metric-in 5
Source Destination Send
Receive In
Neighbor State Address Address Mode
Mode Met
-------- ----- ------- ----------- ----
------- ---
ge-0/0/3.0 Up 10.0.1.44 224.0.0.9 mcast v2
only 1
ge-0/1/0.0 Up 10.4.1.65 224.0.0.9 mcast v2
only 1
ge-0/1/1.10 Up 10.152.1.173 224.0.0.9 mcast v2
only 1
ge-0/1/2.10 Up 10.170.3.177 224.0.0.9 mcast v2
only 5
sronan at pe02.ny2.fat> show route receive-protocol rip 10.170.3.178
inet.0: 319246 destinations, 638064 routes (319245 active, 0 holddown,
27 hidden)
+ = Active Route, - = Last Active, * = Both
8.9.19.128/25 *[RIP/100] 04:47:01, metric 6, tag 1025
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
8.9.33.128/25 *[RIP/100] 04:47:01, metric 6, tag 1025
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
63.211.72.128/25 *[RIP/100] 04:47:01, metric 6, tag 1025
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
156.48.100.192/28 *[RIP/100] 04:47:01, metric 6, tag 1035
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
156.48.100.208/28 *[RIP/100] 04:47:01, metric 6, tag 1035
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
156.48.101.192/28 *[RIP/100] 04:47:01, metric 6, tag 1035
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.33.5/32 *[RIP/100] 04:47:01, metric 6, tag 15
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.41.72/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.41.80/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.41.88/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.41.120/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.41.168/29 *[RIP/100] 04:47:01, metric 6, tag 1015
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.42.72/29 *[RIP/100] 04:47:01, metric 6, tag 1005
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.42.80/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.42.88/29 *[RIP/100] 04:47:01, metric 6, tag 1005
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.42.120/29 *[RIP/100] 04:47:01, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.42.168/29 *[RIP/100] 04:47:00, metric 6, tag 1015
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.53.128/26 *[RIP/100] 04:47:00, metric 6, tag 1025
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.54.128/26 *[RIP/100] 04:47:00, metric 6, tag 1025
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.58.104/29 *[RIP/100] 04:47:00, metric 6, tag 1025
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.61.72/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.61.80/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.61.88/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.61.120/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.61.168/29 *[RIP/100] 04:47:00, metric 6, tag 1015
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.62.72/29 *[RIP/100] 04:47:00, metric 6, tag 1005
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.62.80/29 *[RIP/100] 04:47:00, metric 6, tag 1005
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
198.140.62.88/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.62.120/29 *[RIP/100] 04:47:00, metric 6, tag 1005
> to 10.152.1.174 via ge-0/1/1.10
to 10.170.3.178 via ge-0/1/2.10
198.140.62.168/29 *[RIP/100] 04:47:00, metric 6, tag 1015
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
208.92.194.128/25 *[RIP/100] 04:47:01, metric 6, tag 1025
to 10.152.1.174 via ge-0/1/1.10
> to 10.170.3.178 via ge-0/1/2.10
On Mar 11, 2010, at 10:42 PM, Hoogen wrote:
> Config with a small snapshot of the routing table would be nice..
>
> -Hoogen
>
> On Thu, Mar 11, 2010 at 6:58 PM, Stefan Fouant <sfouant at shortestpathfirst.net
> > wrote:
> Show us your config for 'protocols rip'.
>
> Stefan Fouant
> ------Original Message------
> From: Shane Ronan
> To: sfouant at shortestpathfirst.net
> Cc: 'Juniper Puck'
> Subject: Re: [j-nsp] Prefer RIP Neighbor
> Sent: Mar 11, 2010 7:53 PM
>
> Neighbor level, this is not at all how I expected it to behave.
>
> On Mar 11, 2010, at 9:45 PM, Stefan Fouant wrote:
>
> > Are you setting the metric-in statement at the global level or the
> > neighbor level?
> >
> > Stefan Fouant
> > ------Original Message------
> > From: Shane Ronan
> > To: Stefan Fouant
> > Cc: 'Juniper Puck'
> > Subject: Re: [j-nsp] Prefer RIP Neighbor
> > Sent: Mar 11, 2010 7:32 PM
> >
> > I did, and it seems to set the metric on the route, regardless of
> > interface.
> >
> > On Mar 11, 2010, at 9:28 PM, Stefan Fouant wrote:
> >
> >>> -----Original Message-----
> >>> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> >>> bounces at puck.nether.net] On Behalf Of Shane Ronan
> >>> Sent: Thursday, March 11, 2010 4:53 PM
> >>> To: Juniper Puck
> >>> Subject: [j-nsp] Prefer RIP Neighbor
> >>>
> >>> Hello list,
> >>>
> >>> I have exhausted all of my capabilities to figure out the answer
> to
> >>> this question, so I am hoping you can help.
> >>>
> >>> I have two connections to the same network, which both provide me
> >>> routes via RIP for Multicast sources.
> >>>
> >>> Is there a way for me to prefer the routes I receive via one of
> the
> >>> connections over there other?
> >>
> >> Real stupid question, but did you try the metric-in statement to
> >> adjust the
> >> metric for the route from one of the neighbors, assuming both
> >> neighbors are
> >> not on the same interface...
> >>
> >> Stefan Fouant, CISSP, JNCIE-M/T
> >> www.shortestpathfirst.net
> >> GPG Key ID: 0xB5E3803D
> >>
> >
> >
> >
> > Sent from my Verizon Wireless BlackBerry
>
>
>
> Sent from my Verizon Wireless BlackBerry
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list