Re: Stop the hello in OSPF

Ok, fair enough... So let's look at it differently.

While it's on ethernet, how many peers are there? If there's only two,
why can't you change to a "ip ospf network point-to-point'???

At that point you can run demand circuit just fine.

Did the original question tell us how many peers? I may have been
sleeping at that point! But you are correct, in a broadcast network
type we aren't allowed to run demand circuit.

*Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,

JNCIE-M #153, JNCIS-ER, CISSP, et al.

JNCI-M, JNCI-ER

evil_at_ine.com

Internetwork Expert, Inc.

http://www.InternetworkExpert.com

Toll Free: 877-224-8987

Outside US: 775-826-4344

Knowledge is power.

Power corrupts.

Study hard and be Eeeeviiiil......

shiran guez wrote:
> Hi Scott
>
> not sure you are correct about this as he is talking about Ethernet a
> broadcast segment unless it is a bug the RFC 1793 strictly indicate
> that hello will not be reduced!
>
> Demand circuits and regular network segments (e.g., leased lines) are
> allowed to be combined in any manner. In other words, there are no
> topological restrictions on the demand circuit support. However,
> while any OSPF network segment can be defined as a demand circuit,
> only point-to-point networks receive the full benefit. When broadcast
> and NBMA networks are declared demand circuits, routing update
> traffic is reduced but the periodic sending of Hellos is not, which
> in effect still requires that the data-link connections remain
> constantly open.
> ...
> ...
> 3.2. Sending and Receiving OSPF Hellos
>
> The following sections describe the required modifications to OSPF
> Hello Packet processing on point-to-point demand circuits.
>
> For OSPF broadcast and NBMA networks that have been configured as
> demand circuits, there is no change to the sending and receiving
> of Hellos, nor are there any changes to the Neighbor State
> Machine. This is because the proper operation of the Designated
> Router election algorithm requires periodic exchange of Hello
> Packets.
>
>
> if you where talking on p2p circuit I would agree with Scott totally.
>
>
>
> On Sun, Jun 28, 2009 at 4:09 PM, Scott Morris<smorris_at_ine.com> wrote:
>
>> Use the demand-circuit.
>>
>> Hellos are suppressed although "show ip ospf neighbor" will still show
>> the neighbor there. We used to use this in dial-on-demand routing
>> where the neighbor would still show up even though the dial circuit had
>> actually gone away.
>>
>> HTH,
>>
>>
>>
>>
>> *Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,
>>
>> JNCIE-M #153, JNCIS-ER, CISSP, et al.
>>
>> JNCI-M, JNCI-ER
>>
>> evil_at_ine.com
>>
>>
>> Internetwork Expert, Inc.
>>
>> http://www.InternetworkExpert.com
>>
>> Toll Free: 877-224-8987
>>
>> Outside US: 775-826-4344
>>
>>
>> Knowledge is power.
>>
>> Power corrupts.
>>
>> Study hard and be Eeeeviiiil......
>>
>>
>>
>>
>> ismail mohamed wrote:
>>
>>> Hi,
>>>
>>> R1--R2 connected with OSPF process.
>>>
>>> Now i want to stop the hellow between this but neighbor should not distrip
>>>
>>> is there any way we can only stop the hello and have a neight between them..
>>>
>>>
>>> I tought using passive inter but neighbr alos deleted.
>>>
>>> Thansk in advance.
>>>
>>>
>>> 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

Blogs and organic groups at http://www.ccie.net
Received on Sun Jun 28 2009 - 14:59:29 ART