ospfv3 suppress-flapping peer hold-max-cost disable

Usage Scenario

Flapping suppression works in either Hold-down or Hold-max-cost mode.

• Hold-down mode: In the case of frequent flooding and topology changes during neighbor relationship establishment, interfaces prevent neighbor relationship reestablishment during Hold-down suppression, which minimizes LSDB synchronization attempts and packet exchanges.
• Hold-max-cost mode: If the traffic forwarding path changes frequently, interfaces use 65535 as the cost of the flapping link during Hold-max-cost suppression, which prevents traffic from passing through the flapping link.

Flapping suppression can also work first in Hold-down mode and then in Hold-max-cost mode.

By default, the Hold-max-cost mode takes effect. To configure the Hold-down mode and set duration for this mode, run the ospfv3 suppress-flapping peer hold-down interval command.

The Hold-max-cost mode can prevent a device from being isolated from the network. If a device on a key path is isolated from the network due to OSPFv3 neighbor relationship flapping, the network is separated into two isolated parts. To prevent this problem, use the Hold-max-cost mode on the key path.

Prerequisites

OSPFv3 neighbor relationship flapping suppression must have been enabled globally before you configure duration for the Hold-max-cost mode. By default, the function is enabled. If it is disabled, run the undo suppress-flapping peer disable command to enable it before you configure duration for the Hold-max-cost mode.

Precautions

The Hold-max-cost mode takes effect only unidirectionally. If a remote device does not support OSPFv3 neighbor relationship flapping suppression, bidirectional traffic between the local and remote devices may travel along different paths.