Supported Platforms
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- protocol-down
- ACX, EX, M, MX, T Series
- IEEE 802.3ah OAM Link-Fault Management Overview
- Configuring IEEE 802.3ah OAM Link-Fault Management
- Enabling IEEE 802.3ah OAM Support
- Configuring Link Discovery
- Configuring the OAM PDU Interval
- Configuring the OAM PDU Threshold
- Configuring Threshold Values for Local Fault Events on an Interface
- Disabling the Sending of Link Event TLVs
- Detecting Remote Faults
- Configuring an OAM Action Profile
- Specifying the Actions to Be Taken for Link-Fault Management Events
- Monitoring the Loss of Link Adjacency
- Configuring Threshold Values for Fault Events in an Action Profile
- Applying an Action Profile
- Setting a Remote Interface into Loopback Mode
- Example: Configuring IEEE 802.3ah OAM Support on an Interface
- ACX, EX, MX, T Series
- Enabling Remote Loopback Support on the Local Interface
- Additional Information
- Junos® OS Ethernet Interfaces
Monitoring Protocol Status
The CCC-DOWN flag is associated with a circuit cross-connect (CCC) connection, Layer 2 circuit, and Layer 2 VPN, which send the CCC-DOWN status to the kernel. The CCC-DOWN flag indicates that the CCC is down. The CCC-DOWN status is sent to the kernel when the CCC connection, Layer 2 circuit, or Layer 2 VPN is down. This in turn, brings down the CE-facing PE interface associated with the CCC connection, Layer 2 circuit, or Layer 2 VPN.
When the CCC-DOWN flag is signaled to the IEEE 802.3ah protocol, the system takes the action defined in the action statement of the action profile. For additional information about Layer 2 circuits, see the Junos OS Layer 2 Circuits Feature Guide, Junos OS VPNs Configuration Guide.
To monitor the IEEE 802.3ah protocol, on the CE-facing PE interface, include the protocol-down statement at the [edit protocols oam ethernet link-fault-management action-profile profile-name event] hierarchy level:
 | Note: If multiple events are specified in the action profile, all the events must occur before the specified action is taken. |
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- protocol-down
- ACX, EX, M, MX, T Series
- IEEE 802.3ah OAM Link-Fault Management Overview
- Configuring IEEE 802.3ah OAM Link-Fault Management
- Enabling IEEE 802.3ah OAM Support
- Configuring Link Discovery
- Configuring the OAM PDU Interval
- Configuring the OAM PDU Threshold
- Configuring Threshold Values for Local Fault Events on an Interface
- Disabling the Sending of Link Event TLVs
- Detecting Remote Faults
- Configuring an OAM Action Profile
- Specifying the Actions to Be Taken for Link-Fault Management Events
- Monitoring the Loss of Link Adjacency
- Configuring Threshold Values for Fault Events in an Action Profile
- Applying an Action Profile
- Setting a Remote Interface into Loopback Mode
- Example: Configuring IEEE 802.3ah OAM Support on an Interface
- ACX, EX, MX, T Series
- Enabling Remote Loopback Support on the Local Interface
- Additional Information
- Junos® OS Ethernet Interfaces
Published: 2013-04-03
Supported Platforms
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- protocol-down
- ACX, EX, M, MX, T Series
- IEEE 802.3ah OAM Link-Fault Management Overview
- Configuring IEEE 802.3ah OAM Link-Fault Management
- Enabling IEEE 802.3ah OAM Support
- Configuring Link Discovery
- Configuring the OAM PDU Interval
- Configuring the OAM PDU Threshold
- Configuring Threshold Values for Local Fault Events on an Interface
- Disabling the Sending of Link Event TLVs
- Detecting Remote Faults
- Configuring an OAM Action Profile
- Specifying the Actions to Be Taken for Link-Fault Management Events
- Monitoring the Loss of Link Adjacency
- Configuring Threshold Values for Fault Events in an Action Profile
- Applying an Action Profile
- Setting a Remote Interface into Loopback Mode
- Example: Configuring IEEE 802.3ah OAM Support on an Interface
- ACX, EX, MX, T Series
- Enabling Remote Loopback Support on the Local Interface
- Additional Information
- Junos® OS Ethernet Interfaces
