RE: frame-relay map ipv6 broadcast

You guys might wish to run a debug command on the hub and one of the spokes to
see your packets :)

--------------------------
Kambiz Agahian
CCIE (R&S)
CCSI, WAASSE, RSSSE
Technical Instructor
CCBOOTCAMP - Cisco Learning Solutions Partner (CLSP)
Email: kagahian_at_ccbootcamp.com
Toll Free: 877-654-2243
International: +1-702-968-5100
Skype: skype:ccbootcamp?call
FAX: +1-702-446-8012
YES! We take Cisco Learning Credits!
Training And Remote Racks: http://www.ccbootcamp.com
OEQ Voice Waiver: http://www.ccbootcamp.com/noeqvoice.html
OEQ R&S Waiver: http://www.ccbootcamp.com/noeqrs.html
OEQ Commercial: http://www.ccbootcamp.com/noeq.mpg

-----Original Message-----
From: nobody_at_groupstudy.com on behalf of Joe Astorino
Sent: Sun 4/18/2010 10:20 AM
To: Carlos G Mendioroz
Cc: GAURAV MADAN; Tomasz Zajac; Cisco certification
Subject: Re: frame-relay map ipv6 broadcast

The rule still has not changed : ) You can have the broadcast
multiple times if you want to.... you MUST have it once per protocol
per DLCI. So, if you break that rule by not having it at least once
per protocol per dlci you will not broadcast/multicast out that
circuit.

It's definitely important to understand why rules are in place, but
following rules that are there for a reason doesn't mean you don't
know what you are doing. Maybe it just means that you understand the
alternative, understand why the rules are in place, and decide to use
them wisely.

On Sun, Apr 18, 2010 at 11:44 AM, Carlos G Mendioroz <tron_at_huapi.ba.ar>
wrote:
> I'm going to start the anti rule movement. Who's with me ? LOL
>
> Rules help you do things w/o knowing what the heck you are doing.
> If'you are going to take the lab with a bunch of rules in your toolbox,
> good luck. But I'd like to understand what I'm doing. That way, when
> confronted with a really new environment where I don't have a rule set,
> I can actually think what should I do... :)
>
> In any case, the broadcast keyword does enable replication of frames
> on the corresponding circuit when the L3 address calls for multiple
> destinations and your L2 protocol supports circuits, i.e., point to
> point. If you understand this, and your needs, you should be able to
> work out if you do or do not need it.
>
> -Carlos
>
> Joe Astorino @ 18/04/2010 12:34 -0300 dixit:
>> The rule is this -- no matter if you are running IPv6 or IPv4 over
>> frame-relay, you need the broadcast keyword once per protocol per
>> DLCI.
>>
>> Having it defined more than once per protocol per DLCI will not hurt
>> you, it will only make your configuration redundant and your router
>> will end up sending duplicate packets when it needs to send a
>> broadcast/multicast.
>>
>> Not sure why the 360 material has that specifically ... some people
>> prefer to put it everywhere to save in troubleshooting I suppose (safe
>> if you put it everywhere). In actuality like I said, you only need it
>> once per protocol per DLCI
>>
>>
>>
>> On Sun, Apr 18, 2010 at 9:54 AM, Carlos G Mendioroz <tron_at_huapi.ba.ar>
wrote:
>>> Sorry, but what is a spoke -> spoke ?
>>> The minute you have that, it ends being a spoke, or am I missing something
?
>>>
>>> -Carlos
>>>
>>> GAURAV MADAN @ 18/04/2010 10:18 -0300 dixit:
>>>> Generally speaking
>>>>
>>>> 1) For FR networks ; a multicast means a broadcast (pseudo) . Hence is
>>>> something is getting multicasted (hello etc) ; do include the
>>>> Broadcast keyword in mappings
>>>> 2) For NON-Broadcast networks ( ex when u are using neighbor
>>>> statements) ; you will not require broadcast keyword on mappings
>>>>
>>>> You are absolutely correct that Hub-->Spoke will only need the
>>>> Broadcast keywords. Spoke--> Spoke will never require the broadcast
>>>> keywords .
>>>>
>>>>
>>>> Well your config will never go bad if you add broadcast keyword after
>>>> every mapping statement ( unless u r violating some requirements of
>>>> question ).
>>>>
>>>> Gaurav Madan
>>>> CCIE
>>>>
>>>> On Sun, Apr 18, 2010 at 5:45 PM, Tomasz Zajac <tomasz.zajaczek_at_gmail.com>
wrote:
>>>>> Hello Group
>>>>>
>>>>> I have confusion on using broadcast keyword in frame-relay map ipv6
>>>>> statement. In world ipv4 I only use broadcast statement pointing to
>>>>> directly connected routers (hub-spoke). I dont use boadcast between
spoke
>>>>> and spoke.
>>>>>
>>>>> In 360 stuff I find solutlion using broadcast keywords on every place
(spoke
>>>>> - spoke, hub - spoke) also on global and link local adress.
>>>>>
>>>>> I have testing solution using broadcast keyword only for hub - spoke
>>>>> link-local address and for me works great (for ipv6 RIPng and for
OPSFv3).
>>>>>
>>>>> Is any reason for using broadcast everywhere ?
>>>>>
>>>>> Tomasz
>>>>>
>>>>>
>>>>> 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
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>> --
>>> Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina
>

--
Regards,
Joe Astorino - CCIE #24347
Sr. Technical Instructor - IPexpert
Mailto: jastorino_at_ipexpert.com
Telephone: +1.810.326.1444
Live Assistance, Please visit: www.ipexpert.com/chat
eFax: +1.810.454.0130
IPexpert is a premier provider of Self-Study Workbooks, Video on
Demand, Audio Tools, Online Hardware Rental and Classroom Training for
the Cisco CCIE (R&S, Voice, Security & Service Provider)
certification(s) with training locations throughout the United States,
Europe, South Asia and Australia. Be sure to visit our online
communities at www.ipexpert.com/communities and our public website at
www.ipexpert.com
Blogs and organic groups at http://www.ccie.net