Inter-Datacenter Networks

Inter-Datacenter Networks extend a logical Layer-2 segment beyond one Mission Planner datacenter. There is no parent datacenter, no A-to-B pairing, and no two-site limit. Within the same tenant, every configured Inter-Datacenter Network that uses the same nonzero ID joins the same logical network.

Boston, Denver, Tokyo, an edge lab, and cloud-hosted STRATUM workers can all participate in ID 42. STRATUM resolves that shared tenant + Inter-Datacenter ID into a common network identity and carries it across the Continuum using the distributed overlay.

Cross-worker Inter-Datacenter networking requires the STRATUM Continuum distributed overlay. STRATUM creates the host-side bridge/VXLAN attachment needed on participating workers and uses the Fabric peer set to carry the segment across hosts.

LAN-only mode does not provide cross-worker VXLAN transport. Use Continuum when an Inter-Datacenter Network must span physical workers, remote sites, or platforms.

Inter-Datacenter ID 0 means NOT CONNECTED. An unbound network must fail closed rather than silently joining a shared segment.

The capability is disabled by default. In Network Fabric administration, enable Inter-Datacenter Networks beneath the Continuum controls. This is a provisioning policy, not a kill switch.

Enabling or disabling the provisioning capability is immediate and does not require a STRATUM restart, worker restart, or VM restart. When disabled, STRATUM blocks creation/configuration of new Inter-Datacenter networks. Existing configured networks continue operating so an administrative checkbox cannot unexpectedly disconnect running datacenters.

1. Confirm STRATUM Continuum is enabled and the Inter-Datacenter Networks administrative capability is enabled.
2. In the first datacenter, add an Inter-Datacenter Network object from System Arsenal.
3. Set a nonzero Inter-Datacenter ID, for example 42.
4. Wire the required VMs and switches to that network object. A single network object can accept many attachments; do not create duplicate ID-42 bubbles in the same datacenter.
5. Open the second datacenter, add another Inter-Datacenter Network, and set the same ID 42.
6. Repeat for any additional datacenters that should share the Layer-2 segment.
7. Start/reconcile the attached workloads and verify Layer-2 connectivity across the participating datacenters.

The shared identity is tenant-scoped: Tenant A / ID 42 is not Tenant B / ID 42. Matching IDs are authoritative only inside the same tenant.

Datacenter export/import deliberately deactivates the shared binding by resetting the Inter-Datacenter ID to 0 in the exported/imported copy. This prevents a copied datacenter from unexpectedly reconnecting to a production broadcast domain simply because its source used ID 42.

Because this is a real shared Layer-2 segment, normal Layer-2 responsibilities still apply. Avoid redundant loops through other links, and do not place competing DHCP/gateway services on the same segment unless that is intentional.

STRATUM already treats execution, storage and networking as software-defined resources. Inter-Datacenter Networks extend that operating model across datacenter canvases: workloads can remain organized as separate datacenters while selected Layer-2 segments become shared Continuum resources.

That means a logical application network can span multiple physical workers, multiple datacenters, edge sites and remote platforms without turning the UI into a collection of point-to-point tunnels. The operator names the shared identity once—with the Inter-Datacenter ID—and STRATUM owns the distributed network implementation underneath it.

Every datacenter in the same tenant that uses the same nonzero Inter-Datacenter ID participates in the same logical Layer-2 network across the Continuum, while unconfigured ID 0 networks remain disconnected and exported/imported copies remain safely unbound.