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:
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.
Have you rebooted the device after configuring "set chassis network-service enhanced-ip" ?
Because for this configuration to take effect device needs to be rebooted.
If this solves your problem, please mark this post as "Accepted Solution" so we can help others too
Kudos are appreciated too
Apologies, I forgot to mention that, yes, I have rebooted with no difference.
My understanding is that with vMX you need to have a license installed for this, but did not think this was applicable in the eve-ng virtualisation as we are utilising an actual Junos OS.
I will check the eve-ng site and see if there is anything there, but this is a problem otherwise.
You may load a trial licence. Grab the trial license from here
Bingo. Just needed the right license. Awesome. Thanks