Static routes added to /etc/systemd/network/10-eth0.network do not persist after reboot in VMware Aria Operations 8.18.x

Products

• VCF Operations
• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

• Manual edits made to the /etc/systemd/network/10-eth0.network configuration file to add [Route] sections are lost after a system reboot.
• The network configuration file reverts to its default state, containing only the IP address and Gateway defined in the vApp properties.
• A backup file (e.g., 10-eth0.network.bak or similar) containing the previous manual configuration may be generated in the same directory.
• Commands such as "ip route show" confirm that the custom static routes are not loaded into the kernel table post-reboot.

Environment

VMware Aria Operations 8.18.x

Cause

This behavior is by design in VMware Aria Operations 8.18.x running on Photon OS 5. The appliance utilizes a "Desired State" network configuration model where the vApp Properties (OVF Environment) defined in vCenter Server act as the single source of truth for network settings.

Resolution

While VMware Aria Operations does not natively preserve manual routing changes by default, Photon OS 5 supports systemd drop-in files. This mechanism allows you to define custom routes that persist through system reboots. Perform the steps below to achieve the same : 

1. Create and edit the custom configuration file: Run the following command to open the editor: vi /etc/systemd/network/10-eth0.network.d/custom.conf


2. Define your routes: Press I to enter Insert mode and add your route details in the following format:
   
   [Route]
Destination=##.##.##.##/##
Gateway=##.##.##.##
GatewayOnLink=true
   
   
3. Save and Exit: Press Esc, then type :wq! and press Enter.
   
   
4. Set correct file permissions: Assign standard read permissions to ensure the system can access the file: chmod 644 /etc/systemd/network/10-eth0.network.d/custom.conf


5. Apply the changes: Restart the network service to load the new routes: systemctl restart systemd-networkd


6. Verify the configuration: Confirm the routes are active by running: route -n or ip route

Important Considerations:

While drop-in files are a supported extension method, they may not be retained during major OS upgrades or if vApp properties are modified. Always keep a record of custom routing configurations to re-apply them if the configuration is wiped during such change.

Additional Information

VMware Aria Operations 8.18.x において /etc/systemd/network/10-eth0.network に追加された静的ルートが再起動後に保持されない