Hi all,
I have already found the solution for this issue but it is not working for me. So, I am configuring up some VRFs that require a physical interface interaction rather than the loopback and stumled on this issue when trying to commit:
RT Instance: Only loopback interface is supported under vrf routing instances in triton mode.
The resolution on these boards is at this location:
https://forums.juniper.net/t5/Routing/Commit-fails-when-creating-VRF-on-MX-Only-loopback-interface-is/td-p/33207
When running the command "show chassis network-services" I do get the following results:
Network Services Mode: Enhanced-Ethernet
So, I enter the command "set chassis network-service enhanced-ip", so, this should allow the ge interface to be utilised in the vrf, but I am still getting the same error and that is because the chassis thinks it is still in "enhanced-ethernet" mode.
So, given that I have completed what was recommended before, anyone got any ideas or at least how I can remove the "enhanced-ethernet" from the Network Services Mode so that it is enhanced-ip instead?
I am running version: 18.2R1.9 on the eve-ng virtualisation and it is an MX.
Thanks