Re: ip mroute considered a static route?

This is good stuff, team, many thanks. I like the input and thoughts on the
resolution.

Is it breaking to NDA rules to discuss how mcast will be checked by
auto-verify? For example, if you get mcast on your lab, I would expect it
to require you to configure a join-group somewhere so that auto-verify can
ping it and perhaps run some show commands to verify the rp mappings.

Is this the answer then? We should verify our configs and setup via ping
and show commands?

The reason I ask is that I can imagine myself, configuring this, and then
moving on to the next task while not noticing that something is broke. If I
do not take the extra steps and verify it, then I might have something
simple out of place and easily loose points.

Make sense?

Andrew Lee Lissitz

On Fri, Sep 4, 2009 at 10:22 AM, Darby Weaver <darby.weaver_at_gmail.com>wrote:

> In looking at this again...
>
> I read "which you could easiest resolve with ip mroute blah"...
>
> And then I'd have to ask myself what are they probably looking for a
> solution within the bounds of reason as defined by the rules on the first
> couple of pages of the lab materials.
>
> And then I'd ask myself:
>
> 1. Can I reach it? Is it in my RT? From which ip and interface.
> 2. What route am I taking to get there?
> 3. What interface am I using?
> 4. Does the reverse path work?
> 5. Did I enable ip multicast on each router as instructed?
> 6. Did I enable ip pim (correct mode) on the appropriate interfaces?
> 7. Verify with a few show commands and ensure everything is as expected.
>
>
>
>
> --
> Darby Weaver
> Network Engineer
>
> 407-802-7394
> darbyweaver_at_yahoo.com
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Andrew Lee Lissitz
all.from.nj_at_gmail.com
Blogs and organic groups at http://www.ccie.net