Re: ip mroute considered a static route?

There is no hard rule don't get me wrong it is just something I always do.

Regards,

Joe Astorino - CCIE #24347 R&S
Technical Instructor - IPexpert, Inc.
Cell: +1.586.212.6107
Fax: +1.810.454.0130
Mailto: jastorino_at_ipexpert.com

-----Original Message-----
From: ALL From_NJ <all.from.nj_at_gmail.com>

Date: Fri, 4 Sep 2009 18:52:24
To: Joe Astorino<jastorino_at_ipexpert.com>
Cc: Darby Weaver<darby.weaver_at_gmail.com>; Martin Hogan<martin.john.hogan_at_gmail.com>; Cisco certification<ccielab_at_groupstudy.com>
Subject: Re: ip mroute considered a static route?

Thanks team.

Joe - I do not normally mtrace, but I always do the first two. Humm ... if
the first two are good, do I need to mtrace? I suppose if the lab required
mcast traffic to go a specific route, then this would be a cool way to
verify.

Because these lab environments are so small, I normally just recheck my
configs end to end. For me in my labs, normally tshooting mcast comes down
to the basics. Something I forgot to do, or configured wrong ...

I will try this command tonight in my lab. Many thanks

Andrew

On Fri, Sep 4, 2009 at 2:26 PM, Joe Astorino <jastorino_at_ipexpert.com> wrote:

> Always ALWAYS verify your configurations in the lab. For mcast I would say
> you need to run at a minimum:
>
> 1) show ip pim rp map -- make sure all your multicast routers have learned
> the RP
> 2) ping -- make sure you are getting responses
> 3) mtrace -- make sure things are going the way you expect
>
>
>
> On Fri, Sep 4, 2009 at 2:19 PM, Darby Weaver <darby.weaver_at_gmail.com>wrote:
>
>> Hmm...
>>
>> There are several show commands that will report the desired output to
>> verify the commands correctly and most any lab usually has some ip igmp
>> join-group x.x.x.x to use and might be used for grading purposes.
>>
>> You can always configure your own to verify that things are working
>> correctly but I think you might be over-doing it.
>>
>> Learn how to answer the question and know how to correct the common issues
>> with Multicast. Start with Unicast.
>>
>>
>>
>>
>> On Fri, Sep 4, 2009 at 1:34 PM, ALL From_NJ <all.from.nj_at_gmail.com>
>> wrote:
>>
>> > 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
>> >
>>
>>
>>
>> --
>> 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
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Regards,
>
> Joe Astorino - CCIE #24347 R&S
> Technical Instructor - IPexpert, Inc.
> Cell: +1.586.212.6107
> Fax: +1.810.454.0130
> Mailto: jastorino_at_ipexpert.com
>

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