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.

Junos ®<br />

<strong>OS</strong> 12.3 <strong>Ethernet</strong> <strong>Interfaces</strong> <strong>Configuration</strong> Guide<br />

Configuring MAC Flush Message Processing in CET Mode<br />

220<br />

In carrier <strong>Ethernet</strong> transport (CET) mode, MX Series routers are used as provider edge<br />

(PE) routers, and Nokia Siemens <strong>Networks</strong> A2200 Carrier <strong>Ethernet</strong> Switches (referred<br />

to as E-domain devices) that run standard-based protocols are used in the access side.<br />

On the MX Series routers, VPLS pseudowires are configured dynamically through label<br />

distribution protocol (LDP). On the E-domain devices, topology changes are detected<br />

through connectivity fault management (CFM) sessions running between the E-domain<br />

devices and the MX Series PE routers. The MX Series PE routers can bring the carrier<br />

<strong>Ethernet</strong> interface down if there is CFM connectivity loss. This triggers a local MAC flush<br />

as well as a targeted label distribution protocol (T-LDP) MAC flush notification that gets<br />

sent towards the remote MX Series PEs to trigger MAC flush on them.<br />

In CET inter-op mode, MX Series routers need to interoperate with the Nokia Siemens<br />

<strong>Networks</strong> Ax100 Carrier <strong>Ethernet</strong> access devices (referred to as A-domain devices) that<br />

run legacy protocols. Nokia Siemens <strong>Networks</strong> A4100 and A8100 devices act as an<br />

intermediate between the MX Series PE routers and A-domain devices. These intermediate<br />

devices perform interworking function (IWF) procedures so that operations administration<br />

management (OAM) sessions can be run between MX Series routers and A-domain<br />

devices. There are no VPLS pseudowires between the MX Series PE routers and the Nokia<br />

Siemens <strong>Networks</strong> A4100 and A8100 intermediate devices, so there is no LDP protocol<br />

running between the PE routers to send topology change notifications. In order to<br />

communicate topology changes, MX Series routers can trigger a MAC flush and propagate<br />

it in the core. MX Series routers can use action profiles based upon the connection<br />

protection type length value (TLV) event. The action profile brings down the carrier edge<br />

logical interface in MX Series PE routers, which will trigger a local MAC flush and also<br />

propagate the topology change to the core using LDP notification.<br />

For VPLS there is no end-to-end connectivity monitored. The access rings are<br />

independently monitored by running CFM down multiple end points (MEPs) on the<br />

working and protection paths for each of the services between the E-domain devices<br />

and the MX Series PE routers, and between the A-domain devices and the MX Series PE<br />

routers the IWF hosted by the Nokia Siemens <strong>Networks</strong> A-4100 devices. When there is<br />

a connectivity failure on the working path, the Nokia Siemens <strong>Networks</strong> Ax200 devices<br />

perform a switchover to the protection path, triggering a topology change notification<br />

(in the form of TLVs carried in CCM) to be sent on the active path.<br />

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

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

Saved successfully!

Ooh no, something went wrong!