Re: frame-relay map ipv6 broadcast

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
Blogs and organic groups at http://www.ccie.net