VLCR Direct Connect Configuration Persistence Failure

Products

• VMware Live Recovery

Issue/Introduction

• Connector appliances deployed prior to version v27m6 switch from private Direct Connect IPs to public SCFS IPs after a VM reboot.
• Traffic destined for the Cloud File System (SCFS) is forced to traverse the  internal core network instead of the Direct Connect path.
• drc show config may still reflect Direct Connect settings, but drc network test confirms the public IP is being used.

Environment

VMware Live Cyber Recovery 7.26.0.0

Cause

• A configuration retention bug at the Photon OS level fails to preserve Direct Connect routing settings across reboots.
• Older connector versions utilize an upgrade path that only updates the container layer, leaving the underlying OS-level bug unpatched.

Resolution

The affected appliances must be redeployed using the latest .ova image. This provides an updated architecture that supports both OS and container-level upgrades. 

Note: Do not attempt to run drc setup on an existing connector already carrying Direct Connect configuration; redeployment is the only supported method to resolve the OS-level drift.