21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• interval time<br />

• loss-threshold number<br />

To enable the continuity check protocol, include the continuity-check statement at the<br />

[edit protocols oam ethernet connectivity-fault-management maintenance-domain<br />

domain-name maintenance-association ma-name] hierarchy level.<br />

Configuring the Continuity Check Hold Interval<br />

You can specify the continuity check hold interval. The hold interval is the number of<br />

minutes to wait before flushing the MEP database if no updates occur. The default value<br />

is 10 minutes.<br />

The hold interval logic runs a polling timer per CFM session level (not per remote MEP<br />

level) where the polling timer duration is equal to the configured hold time. When the<br />

polling timer expires, it deletes all the auto discovered remote MEP entries which have<br />

been in the failed state for a time period equal to or greater than the configured hold<br />

time. If the remote MEP completes the hold time duration in the failed state, then flushing<br />

will not occur until the next polling timer expires. Hence remote MEP flushing may not<br />

happen exactly at the configured hold time.<br />

Configuring the Continuity Check Interval<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

To configure the hold interval, include the hold-interval statement at the [edit protocols<br />

oam ethernet connectivity-fault-management maintenance-domain domain-name<br />

maintenance-association ma-name continuity-check] hierarchy level.<br />

NOTE: Hold timer based flushing is applicable only for auto discovered remote<br />

MEPs and not for statically configured remote MEPs.<br />

You can specify the continuity check message (CCM) interval. The interval is the time<br />

between the transmission of CCMs. You can specify 10 minutes (10m), 1 minute (1m),<br />

10 seconds (10s), 1 second (1s), 100 milliseconds (100ms), or 10 milliseconds (10ms).<br />

The default value is 1 minute.<br />

Chapter 13: Configuring IEEE 802.1ag OAM Connectivity-Fault Management<br />

NOTE: For the continuity check message interval to be configured for 10<br />

milliseconds, periodic packet management (PPM) runs on the Routing Engine<br />

and Packet Forwarding Engine (PFE) by default. You can only disable PPM<br />

on the PFE. To disable PPM on the PFE, use the no-delegate-processing<br />

statement at the [edit routing-options ppm] hierarchy level.<br />

Continuity check interval of 10 milliseconds is not supported for CFM sessions<br />

over a Label-Switched interface (LSI).<br />

To configure the interval, include the interval statement at the [edit protocols oam ethernet<br />

connectivity-fault-management maintenance-domain domain-name<br />

maintenance-association ma-name continuity-check] hierarchy level.<br />

189

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!