From: YourPal (dearprudence28@gmail.com)
Date: Fri Jan 04 2008 - 12:58:01 ARST
Hi Ben,
Is the following config functionally the same?
!
interface Serial1/0
encapsulation frame
no fram inv
frame map ip 1.1.1.1 101 <- to the hub
frame map ip 1.1.1.2 101 broadcast <- to the spoke
!
I understand the "broadcast" keyword is per protocol per DLCI. Correct me if
I'm wrong.
Thank you.
BR,
Emil
On 1/4/08, Ben Holko <ben@holnet.net> wrote:
>
> They mean do not map to the spoke with the broadcast keyword, like this
> on the spokes:
>
> !
> interface Serial1/0
> encapsulation frame
> frame map ip 1.1.1.1 101 broadcast <- to the hub
> frame map ip 1.1.1.2 101 <- to the spoke
> !
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Peter
> Sent: Friday, 4 January 2008 11:48 PM
> To: ccielab@groupstudy.com
> Subject: Statically mapping broadcasts
>
> Experts,
>
>
>
> Working in IEWB VOL2,
>
>
>
> Reading in the task:
>
> "Do not send any redundant broadcast traffic from the spokes to the
> hub"?
>
>
>
> I understood not to "statically map" broadcast traffic from spokes to
> the
> hub.
>
> However, when configuring OSPF later, not to use neighbor, requires
>
> broadcast to be correctly mapped for the 224.0.0.5 hellos to flow.
>
>
>
> Any comment what they mean by: "Do not send any redundant broadcast
> traffic
> from the spokes to the hub"?
>
>
>
> Cheers,
>
> Peter
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:37:57 ARST