Routing

Dear Juniper,

I am curious about the "next-table" option of "static routing".

The topology is as follows.

First, the below config is committed.
"set routing-options static route 33.33.33.0/24 next-table VRF10.inet.0"

After that, when I commit the below config, an error occurs.
"set routing-instances VRF10 routing-options static route 11.11.11.0/24 next-table inet.0"

[edit]
root@XM1# commit
error: [rib inet.0 routing-options static]
next-table may loop
error: configuration check-out failed"

I searched on the internet and it says it's because of "loop protection".

I'm curious aboutthe conditions under which loop protection occurs (when it occurs).

And is it impossible to communicate between different routing instances with only static routing?

Yes, the config commit checks that you don't have at the same time a static route from the VRFs A to B, and from B to A (whatever the prefixes are, the default instance being like a VRF here):

Commit fails with a "next-table may loop" message

However you can go through a third VRF to circumvent this (stupid/ridiculous/absurd/nonsense) «feature».

------------------------------
Olivier Benghozi
------------------------------