I don't want to convert a regular port into a routing-instance, I want to put fxp0 / em0 into a routing-instance or logical router. I don't want to pollute the main inet.0 routing table with mgmt routes. There are various workarounds, but some features (inline jflow) that only work properly via the main inet.0 routing table.
On Fri, Jul 8, 2016, at 05:03 AM, Paul S. wrote: > Likewise, it really doesn't make much sense to me. > > Having to retrofit a normal port to act as management in its own vrf is > stupid (and not even always possible). _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp