Hello All,

I have a query regarding the behavior of a PE that is a member of an ES and has 
been configured to be in All-Active mode.

According to section 7.5 the multihomed site redundancy mode is set to RED = 
00: A value of 00 means that the multihomed site is operating in All-Active 
redundancy mode.

What defines “operating”?  Is this according to local configuration only?

In section 7.11 the ‘P’ bit of the L2-ATTR Extended Community MUST be set to 1 
for multihoming All-Active scenarios by all active PE(s).
What is an “active PE”? Is this according to local configuration only?


In section 14.1.1 it states that:


For a given ES, if a remote PE has imported the set of Ethernet A-D
   per ES routes from at least one PE, where the "Single-Active" flag in
   the ESI Label extended community is set, then that remote PE MUST
   deduce that the ES is operating in Single-Active redundancy mode.


My understanding is that the meaning of “remote PE” is a PE that is not a 
member of the ES. This statement indicates that the “remote PE” deduces that 
the ES is operating in Single-Active redundancy mode from the set of Ethernet 
A-D per ES routes it has received.

What should be the behavior of the “local PE” that is a member of the ES ? I 
could not find this defined in the document.

Does the “local PE” assume that the configuration of all attached PEs to the ES 
is consistent and therefore it sends RED = 00 and sets the ‘P’ bit in the 
L2-ATTR ? Or does the “local PE” change what it advertises according to what it 
receives from the other “local PEs” attached to the same ES?

Thank you kindly.

Best Regards,

Menachem Dodge​​​​
System Architect
[signature_3596491684]
+972-526175734<tel:+972-526175734>
mdo...@drivenets.com<mailto:mdo...@drivenets.com>
follow us on Linkedin<https://www.linkedin.com/company/drivenets>
www.drivenets.com<http://www.drivenets.com/>
[DriveNets Network Cloud]<https://drivenets.com/products/>

_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to