We have a small mpls network carrying multiple L3VPN's, 2 of which are used by ourselves. One is corporate, and the other was created to segregate a production voice system - sip carrier terminations, audio infrastructure etc.
Its becoming apparent that splitting these networks up was probably not the wisest choice. There are more and more resources in the production voice VRF that are actually corporate resources etc.
I could explicitly leak routes between the 2 with policy-statements, but the more i think about it the more sense it makes to bring them both together. Could i do this by putting the same vrf-target on both routing-instances? It would save me having to move the interfaces, bgp settings etc from one vrf into another
No comments:
Post a Comment