What is the goal or outcome the customer wants? As the OP said, HA. HA solutions don't have *any* SPOFs.
You've added the risk of complexity and potentially unexpected feature interactions that may negate the benefits your solution provides. (Have you tested what you proposed through all the failure modes? Will you test it before deploying a firmware upgrade, because Juniper may not realise anybody us using VRRP/BGP in this manner, and therefore won't test that combination before they do their firmware releases?) As a general rule, I think a good upgrade cycle to aim for is one upgrade every 6 to 12 months. If the customer can't tolerate a e.g., 10 minute service outage once every 6 months for a device upgrade, then they need two of everything i.e., no SPOFs, or they need to lower their service availability expectations. On 29 May 2017 at 10:58, Chris Kawchuk <juniperd...@gmail.com> wrote: > Yep, but rule out the PE or CE device as a SPOF. Lets you make code upgrades > on the network devices without knocking out the link. > > If the link goes down, you're in the same boat; no worse off. > > - CK. > > On 29 May 2017, at 10:56 am, Mark Smith <markzzzsm...@gmail.com> wrote: > >> And the service is still a SPOF. >> >> Just get two services/links, and use plain vanilla BGP. > _______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net http://lists.ausnog.net/mailman/listinfo/ausnog
