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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Identifier MAC address State Interface<br />

200 00:05:85:73:39:4a ok xe-5/0/0.0<br />

Use the interfaces command to display MAC status defects:<br />

user@host> show oam ethernet connectivity-fault-management interfaces detail<br />

Interface name: xe-5/0/0.0, Interface status: Active, Link status: Up<br />

Maintenance domain name: md6, Format: string, Level: 6<br />

Maintenance association name: ma6, Format: string<br />

Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames<br />

Interface status TLV: up, Port status TLV: up<br />

MEP identifier: 500, Direction: down, MAC address: 00:05:85:73:7b:39<br />

MEP status: running<br />

Defects:<br />

Remote MEP not receiving CCM : no<br />

Erroneous CCM received : no<br />

Cross-connect CCM received : no<br />

RDI sent by some MEP : no<br />

Some remote MEP's MAC in error state : yes # MAC Status Defects<br />

yes/no<br />

Statistics:<br />

CCMs sent : 1328<br />

CCMs received out of sequence : 0<br />

LBMs sent : 0<br />

Valid in-order LBRs received : 0<br />

Valid out-of-order LBRs received : 0<br />

LBRs received with corrupted data : 0<br />

LBRs sent : 0<br />

LTMs sent : 0<br />

LTMs received : 0<br />

LTRs sent : 0<br />

LTRs received : 0<br />

Sequence number of next LTM request : 0<br />

1DMs sent : 0<br />

Valid 1DMs received : 0<br />

Invalid 1DMs received : 0<br />

DMMs sent : 0<br />

DMRs sent : 0<br />

Valid DMRs received : 0<br />

Invalid DMRs received : 0<br />

Remote MEP count: 1<br />

Identifier MAC address State Interface<br />

200 00:05:85:73:39:4a ok xe-5/0/0.0<br />

Configuring Remote MEP Action Profile Support<br />

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

Based on values of interface-status-tlv and port-status-tlv in the received CCM packets,<br />

a specific action, such as interface-down, can be taken using the action-profile options.<br />

Multiple action profiles can be configured on the router, but only one action profile can<br />

be assigned to a remote MEP.<br />

The action profile can be configured with at least one event to trigger the action; but the<br />

action will be triggered if any one of these events occurs. It is not necessary for all of the<br />

configured events to occur to trigger action.<br />

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

An action-profile can be applied only at the remote MEP level.<br />

217

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

Saved successfully!

Ooh no, something went wrong!