[c-nsp] link flaps

[Mindaugas Kubilius]

If a mux link down does bring the router interface down as well, you 
could look at IP route dampening on the interface:

dampening ...

Otherwise kind of dynamic routing/BFD/IPSLA methods can be applied. E.g. 
BGP with route dampening. Or tracked static routes with IPSLA object 
tracking..

Regards,
Mindaugas

On 2010.11.27 20:03, jack daniels wrote:
> any comments Dear friends would be most appreciated and very helpfull for me.
>
> On Sat, Nov 27, 2010 at 9:30 AM, jack daniels<jckdaniels12 at gmail.com>  wrote:
>> Hmm... laying intercity cables Technically good ....but not
>> commercialy (which is most important)..  :)
>>
>> On Sat, Nov 27, 2010 at 1:43 AM, Keegan Holley
>> <keegan.holley at sungard.com>  wrote:
>>> You can always get a really long cable so you don't need the MUX's.
>>>
>>>
>>> On Fri, Nov 26, 2010 at 2:49 PM, jack daniels<jckdaniels12 at gmail.com>
>>> wrote:
>>>> Hi guys,
>>>>
>>>> I have a scenario
>>>>
>>>>
>>>> Router R1 --------------Ethernet
>>>> Cable-----MUX----------------MUX-----------Ethernet Cable-------Router
>>>> R2
>>>>
>>>>
>>>> my MUX to MUX link flaps a lot and my traffic impacts ....I have
>>>> backup links also. Can I do something that when link MUX to MUX flaps
>>>> I dont
>>>> use this for some time , till it stablizes.
>>>>
>>>> Regards
>>>> _______________________________________________
>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>
>>>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/