Virtual Private LAN Services
7750 SR OS Services Guide Page 461
If MC-EP de-registers with BFD using the “no bfd-enable” command, the following processing
steps occur:
• Local peer indicates to the MC-EP peer the fact that local BFD is being disabled using
MC-EP peer-config-TLV fields ([BFD local : BFD remote]). This is done to avoid wrong
interpretation of BFD session loss.
• Remote peer acknowledges reception indicating through the same peer-config-TLV fields
that it is de-registering with the BFD session.
• Both MC-EP peers de-register and are going to use only keep-alives for failure detection
• There should be no pseudowire status change during this process.
Traps are sent when the status of the monitoring of the MC-EP session through BFD changes in
the following instances:
• When red/mc/peer is no shutdown and BFD is not enabled, send a notification indicating
BFD is not monitoring MC-EP peering session
• When BFD changes to open, send a notification indicating BFD is monitoring MC-EP
peering session
• When BFD changes to down/close, send a notification indicating BFD is not monitoring
MC-EP peering session.
MC-EP Passive Mode
The MC-EP mechanisms are built to minimize the possibility of loops. It is possible that human
error could create loops through the VPLS service. One way to prevent loops is to enable the
MAC move feature in the gateway PEs (PE3, PE3', PE1 and PE2).
An MC-EP passive mode can also be used on the second PE pair, PE1 and PE2, as a second layer
of protection to prevent any loops from occuring if the operator introduces operational errors on
the MC-EP PE3, PE3 pair.
To Next Page
Loading...
