Re: ip mroute considered a static route?

From: CCIE League <ccieleague_at_ymail.com>
Date: Fri, 4 Sep 2009 14:02:19 +0000 (GMT)

sorry missed the MBONE via DVMRP part :)

---------------------------------------------------------------
Connect to MBONE via DVMRP tunnel:

interface tunnel 0
 ip unnumbered f0/0
 tunnel souce ....
 tunnel destination ...
 tunnel mode dvmrp

all routers that need DVMRP to derive information for RPF check:

interface [any multicast interface that might received DVMRP]
 ip dvmrp unicast-routing

to advertise networks that will deliver multicast feeds to hosts on MBONE via DVMRP:

interface tunnel 0
 ip dvmrp metric 1 list TEMP
 ip dvmrp summary-address .... (optional, if want to summarize networks specified in TEMP)
 
ip access-list standard XXX
permit y.y.y.y
permit x.x.x.x (all the networks that will provide multicast feeds)

--------------------------------------------------------------

----- Original Message ----
From: CCIE League <ccieleague_at_ymail.com>
To: Danshtr <danshtr_at_gmail.com>; Martin Hogan <martin.john.hogan_at_gmail.com>
Cc: Cisco certification <ccielab_at_groupstudy.com>
Sent: Friday, 4 September, 2009 14:56:33
Subject: Re: ip mroute considered a static route?

ip mroute is NOT static route... ?
 
"ip mroute" is exact opposite of "ip route". ip route specifies where the packet should go next. ip mroute specifies when the packet should be coming from.
when the multicast paths (linked by various interface that has "ip pim sparse-dense") does not map to unicast routing paths:
 
ip mroute [RP address] 255.255.255.255 [which upstream router this should be coming from]
ip mroute [RP mapping agent address] 255.255.255.255 [which upstream router this should be coming from]
ip mroute [multicast sources] 255.255.x.x [which upstream router this should be coming from]
 
 
What could be the alternate way?
 
 
 
 
Connect to MBONE via DVMRP tunnel:

interface tunnel 0
ip unnumbered f0/0
tunnel souce ....
tunnel destination ...
tunnel mode dvmrp
all routers that need DVMRP to derive information for RPF check:
interface [any multicast interface that might received DVMRP]
ip dvmrp unicast-routing
2. to advertise networks that will deliver multicast feeds to hosts on MBONE via DVMRP:
interface tunnel 0
ip dvmrp metric 1 list TEMP
ip dvmrp summary-address .... (optional, if want to summarize networks specified in TEMP)
 ip access-list standard XXX
permit y.y.y.y permit x.x.x.x (all the networks that will provide multicast feeds)
 
 
 
 
 

----- Original Message ----
From: Danshtr <danshtr_at_gmail.com>
To: Martin Hogan <martin.john.hogan_at_gmail.com>
Cc: Cisco certification <ccielab_at_groupstudy.com>
Sent: Friday, 4 September, 2009 6:52:52
Subject: Re: ip mroute considered a static route?

I asked the proctor. He told me they are not allowed. He might be wrong. At
the end I have found another solution.

Best regards,
Dan

On Fri, Sep 4, 2009 at 7:15 AM, Martin Hogan <martin.john.hogan_at_gmail.com>wrote:

> Hi all,
>
> If you were in a lab situation and were given the rule that you aren't
> allowed to use static routes, yet you had an RPF issue which you could
> easiest resolve with ip mroute blah, would you consider that breaching the
> rule? Why? Why not?
>
> This is prompted by me doing IGP manipulation in order to resolve, where-as
> the solution guide just did the ip mroute.
>
> Apologies if this has been covered extensively in the past and im rehashing
> it however I was unable to find it in the archive. Hopefully im better at
> browsing the Cisco docs :)
>
> Cheers for the thoughts.
>
> Martin
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri Sep 04 2009 - 14:02:19 ART

This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:02 ART