Re: OSPF Demand Circuit

From: Georg Pauwen (pauwen@hotmail.com)
Date: Fri Jul 04 2003 - 08:08:59 GMT-3


Hello,

AFAIK, the broadcast statement in the dialer map causes broadcasts to bring
up the link, hence you need an access list denying OSPF packets in the
dialer-list. Without the broadcast statement in the dialer map, you don4t
need the access list.

Regards,

Georg

>From: "ccie2be" <ccie2be@nyc.rr.com>
>Reply-To: "ccie2be" <ccie2be@nyc.rr.com>
>To: "Group Study" <ccielab@groupstudy.com>
>Subject: OSPF Demand Circuit
>Date: Fri, 4 Jul 2003 06:22:15 -0400
>
>Hi,
>
>After checking the archieves, I didn't find anything that specifically
>addressed this question, so here goes.
>
>I thought that when a BRI interface is configured as an ip ospf
>demand-circuit, it will automatically suppress ospf hello's as long as the
>interface is configured as a p2p or p2m ospf network type.
>
>However, in the example at
>http://www.cisco.com/warp/public/129/config-bri-map.html , it shows an
>access
>list being used to prevent ospf hello's in addition to the ip ospf
>demand-circuit command being configured.
>
>Is it really necessary (or just sometimes necessary) to use an access list
>to
>deny ospf hello's (packets addressed to 224.0.0.5) when one side of the
>isdn
>circuit is configured as an ip ospf demand circuit? If so, why is that?
>Also, if the access-list in addtion to the ip ospf demand circuit is only
>needed in certain situations, what are those situations?
>
>Thanks, Jim
>
>
>_______________________________________________________________________
>You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:23 GMT-3