Skip to main content

Drift Detection and Repair

euroNAS SDN continuously compares the intended network configuration with the active runtime state. When these differ, the condition is identified as drift.

What drift means

Drift occurs when the current SDN state no longer matches the expected configuration. This can affect switch availability, uplink connectivity, or VM interface policy.

Typical drift conditions

  • Missing switch
  • Missing uplink assignment
  • Missing intended uplink
  • No uplink
  • No connected uplink
  • Degraded uplink
  • Disconnected port
  • Loose uplinks
  • VM profile drift

Why drift matters

Drift can affect connectivity, migration readiness, and failover behaviour. Early detection allows corrective action to be taken before service impact occurs.

Repair and reconciliation

Reconciliation restores the active SDN state to the intended configuration. This provides a structured way to repair network inconsistencies within the cluster.

Typical repair actions

  • Recreate a missing switch
  • Restore intended uplinks
  • Re-enable loop protection
  • Convert loose uplinks into a bonded connection
  • Reapply VM network profile settings

Repair approach

Repairs are applied in a controlled and predictable manner so that network state can be restored safely while maintaining service stability.

Virtual Network Health and repair actions

Open Virtual Network Health from the Virtual Switches area. The page reports both switch drift and VM-profile drift.

Depending on the finding, eEVOS can offer Create Missing Switch On Target, Enable RSTP, Restore Intended Uplinks, Normalize Bond On Target, or Assign Missing Uplinks. Migration target cards can also provide Repair All On Target Node for deterministic repairs.

Automatic repair never invents an unknown physical uplink assignment. Select the uplink manually when the intended state and physical topology do not provide a safe answer, then run the health check again.

Back to top