If you noticed in the following diagram also, I have added a link between MPLS cloud to Internet to counter this behavior.
You can see the mentioned link in red and I am going to remove it and make it work like it is not necessary.
Before doing this, let's examine the routing tables.
(click on the images to view in full size)
There is a setting called max-control-connection under VPN interface. Default value is 2 and it means 2 controllers can connect to a TLOC. But if we change this value to "0", it will not expect to connect to any controller over that interface and will advertise the TLOC for MPLS to vSmart from other control connections. In the above case, it's Biz-Internet..
Since these WAN egdes are managed by vManage, we need to change the configuration from editing the templates. It is in the Interface Feature template which relates to the MPLS transport interface.
Note that if it is configured on only one router, that router will send its MPLS TLOCs to vSmart and vSmart will send them to other routers but these other routers will make it an invalid route as their MPLS transport is not included in OMP routing. So in order for this to work, it should have done from other routers as well so that Data Plane tunnels will be established.
Only the Control Plane tunnels to controllers will be established from Biz-Internet transport as a single point of failure now anyway.
No comments:
Post a Comment