Problem Summary:
The Druva Phoenix Hyper-V File Level Restore (FLR) proxy VM fails to obtain an IP address via DHCP during deployment. As a result, the FLR proxy remains non-functional for file-level restores. The FLR VM console might show no IP or report network connectivity failures.
Cause:
The issue is commonly caused by incorrect VLAN configuration on the FLR proxy’s virtual NIC. If the VM is assigned to a VLAN or virtual switch that:
Lacks DHCP access,
Uses incorrect VLAN tagging, or
Is misaligned with the physical switch configuration,
Then the FLR proxy cannot reach the DHCP server to get an IP.
Resolution:
1. Access the FLR Proxy Console
In Hyper-V Manager, open the console of the FLR proxy VM.
Check for network configuration status (e.g., via ip a or ifconfig if Linux-based).
Look for absence of an IP address or DHCP errors.
2. Verify Virtual Switch and VLAN Settings
In Hyper-V Manager, go to Virtual Switch Manager.
Identify the switch used by the FLR proxy’s network adapter.
If VLAN tagging is used:
Check that the VLAN ID assigned to the VM NIC matches the VLAN where the DHCP server is reachable.
For trunk ports (multiple VLANs), ensure the VM's VLAN ID is allowed (tagged) on that trunk.
For access ports (single VLAN), the VM NIC should not use VLAN tagging, or the VLAN tag should match the access port configuration.
3. Check the Physical Network & DHCP Scope
Ensure the DHCP server for the assigned VLAN is active and has available IPs.
Confirm that the physical switch port (to which the Hyper-V host is connected) is correctly configured for VLAN access or trunking.
4. Update VM Network Adapter Settings
In the FLR Proxy VM > Settings > Network Adapter:
Ensure the adapter is connected to the correct virtual switch.
Set or correct the VLAN ID, if applicable.
Apply and save the changes.
5. Restart Network Setup
Reboot the FLR proxy VM or restart the DHCP client.
Monitor the console to see if it now obtains an IP address successfully.
6. Static IP Configuration (Alternative Option)
If DHCP still fails, configure a static IP via the FLR proxy console.
Use valid:
IP address,
Subnet mask,
Default gateway,
DNS servers for the intended VLAN.
Static IP setup is supported and may be ideal for environments with complex VLAN/firewall rules.
Key Takeaway:
For the Hyper-V FLR proxy to work correctly, ensure the virtual and physical network configurations are aligned, particularly VLAN IDs and DHCP availability. A mismatch can silently block network connectivity, causing proxy activation failures.