Hi Jorge, Section 2.1.1. Current DF election procedure and AC failures
If AC2 is accidentally shutdown or even not configured, CE12 traffic will be impacted. In case of all-active multi-homing, only the BUM traffic to CE12 will be impacted, whereas for single-active multi-homing all the traffic to/from CE12 will be discarded. This is due to the fact that a logical failure in PE-2 AC2 will not trigger an ES route withdrawn for ESI12 (since there are still other ACs active on ESI12) and therefore PE-1 will not re-run the DF election procedures. In Single Active a sub interface goes down, it will send a type 4 withdrawal and other PE will become DF based. This is taken care in SA but AA it makes sense. How about the 3 second timer, there will be a loop if there is transition of PE's moving to DF to NON DF when a new PE as added or a link failure. During this time, may I know how the traffic is handled because RFC is not clear about that period. How you are going to tackle that issue.During this transition period if both PE starts forwarding the traffic there will be a loop, how to address that. If you are using AC per Vlan but customers require vlan bundle, some times local switching how to handle those situations. Kindly clarify. Correct me if I am wrong. Regards, Sudhin On Mon, 30 Nov 2015 11:50:09 +0530 "Rabadan, Jorge (Jorge)" wrote > Hi Sudhin, Please see in-line. Thanks. Jorge From: BESS on behalf of sudeep g ggg Date: Wednesday, November 25, 2015 at 2:58 PM To: "[email protected]" Subject: [bess] REG: draft-rabadan-bess-evpn-ac-df-02 Respected Authors, I had gone through the draft at high level,I am happy to see a real provider provisioning issues addressed in your draft. Much appreciated. Some key highlights in your draft. 1. No changes. 2. Using existing features to address a problem. 3. Addresses provisioning issues. [JORGE] not only provisioning issues but also ‘logical’ failures like an "Attachment Circuit” going oper-down due to OAM or admin shutdown. How ever I have following queries. May I know how to deal with vlan provisioning issues like one PE will have vlan 2,3,4 and other PE will have 3,4 this will end up in both PE's as DF correct me if I am wrong, you use type 1 Ad per ES and EVI for DF election, how about vlan issues. [JORGE] the draft talks about how to influence the DF election based on the status of an “Attachment Circuit (AC)”. For VLAN-based services, a customer VID equals an AC (and there is a single VLAN per EVI per ES), hence in this case you can actually catch VLAN provisioning mistakes, i.e. if you don’t provision VLAN 2 in PE1, PE1 won’t ever send the AD per EVI route for that VLAN, hence PE1 won’t be elected the DF within the ES in any PE using the AD per-EVI route in the DF election. May I know how to handle transient loop during 3 seconds period during DF election.May I know the state of PE during the DF election, clarity required[humble opinion]. [JORGE] the draft is not changing the DF election itself (where, by the way, there is no transient loops). It is only removing PEs from the candidate DF list for a given EVI based on the presence of the AD per-EVI route. All the rest of the RFC7432 procedures are kept intact. This seems to be a good customer focused solution. I appreciate it.[please note: this is my humble opinion as an individual not representing any one] Regards, Sudhin Jacob Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More > _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
