Yes. You are right. This is a problem specific to BDR taking over the role of DR. The problem you describe has been around for a while and I have seen people using decent workarounds without requiring protocol changes to solve this problem.
Rgds Shraddha From: Alexander Okonnikov [mailto:[email protected]] Sent: Monday, April 24, 2017 3:33 PM To: Shraddha Hegde <[email protected]>; [email protected]; [email protected] Subject: Re: draft-ietf-ospf-link-overload-06 - DR migration Hi Shraddha, For planned link maintenance there still could be traffic disruption. Even if router with overloaded link is detached from broadcast link, the latter still could be used by other routers on this one. If router with overloaded link was DR, traffic between other routers on broadcast link could be disrupted. Am I correct? 24.04.2017 12:55, Shraddha Hegde пишет: Hi Alexander, The objective of this draft is to re-route the traffic from the link that is expected to undergo maintenance And the case of broadcast links is explained in sec 5.2 which achieves the objective. The case you described may be relevant for unplanned link-down events which is outside the scope of this draft. Thanks Shraddha From: Alexander Okonnikov [mailto:[email protected]] Sent: Thursday, April 20, 2017 6:50 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: draft-ietf-ospf-link-overload-06 - DR migration Hi authors, In case when the node that has the link to be overloaded is DR (for broadcast/NBMA link case), taking this link out of service could be disruptive. What if to modify procedure in such manner that when BDR receives Link-Overload-sub-TLV from DR, it generates Network LSA in advance, before taking DR role. The node with overloading link then waits some time (for example, 3 secs) and changes its interface priority to 0. Thank you.
_______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
