Technical Documentation

Example: Configuring Ethernet LFM for CCC

In this example, LFM is configured between two PEs (PE1 and PE2) connected using CCC. With LFM in place, a link fault will be detected immediately, instead of depending on routing protocols to find the fault on end-to-end CCC connection. This also helps in detecting the exact failed link instead of only finding that the end-to-end CCC connectivity has failed. Also, because LFM runs at the link-layer level, it does not need a IP address to operate and so can be used where bidirectional fault detection (BFD) cannot.

The links running LFM are shown in Figure 1

Figure 1: Ethernet LFM for CCC

Image g016839.gif

To configure Ethernet LFM between two PEs connected using CCC:

  1. Configure LFM on the PE1 router with CCC:

    [edit]
    interfaces ge-1/1/0 {
    encapsulation ethernet-ccc;
    unit 0;
    }
    protocols {
    oam {
    ethernet {
    link-fault-management {
    interface ge-1/1/0 {
    pdu-interval 1000;
    pdu-threshold 5;
    }
    }
    }
    }
    }

  2. Configure LFM on the PE2 router with CCC:

    [edit]
    interfaces ge-1/0/0 {
    encapsulation ethernet-ccc;
    unit 0;
    }
    protocols {
    oam {
    ethernet {
    link-fault-management {
    interface ge-1/0/0 {
    pdu-interval 1000;
    pdu-threshold 5;
    }
    }
    }
    }
    }

Published: 2009-10-11