OSPF still forming adjacency over VDOM link when one VDOM is disabled?

Hi,

I’m facing a behavior that seems counter‑intuitive regarding OSPF over inter‑VDOM links.

I am in a multi‑VDOM setup:

• OSPF is configured between VDOMs over a VDOM link
• Each VDOM has its own routing instance (OSPF process)

According to documentation:

• Inter‑VDOM routing relies on VDOM link interfaces
• A disabled VDOM does not process traffic (no policy lookup / no forwarding)

I encountered the following situation:

• One of the VDOMs was administratively disabled
• However:
  • OSPF adjacency was still UP
  • Routes were still being exchanged

My understanding was:

• A disabled VDOM should not process traffic
• Therefore:
  • No OSPF Hello packets
  • No adjacency

But this does not match the observed behavior.

Is this behavior expected?

More specifically:

• Does a disabled VDOM still run routing protocols (OSPF control plane)?
• Is it possible that:
  • control plane (OSPF) still runs
  • while dataplane (forwarding) is stopped?

Or:

• Is this a known limitation / bug / specific behavior with VDOM links?

Thanks in advance

BW