You can change the static routes for the eth0 and eth1 network interfaces after the initial vCloud Director deployment.

Procedure

  1. If you want to change the static route value temporarily, for example, for testing purposes, edit the static routes in vCloud Director.
    1. Log in directly or by using an SSH client to the vCloud Director appliance console as root.
    2. (Optional) Verify the current static route configuration.
      • For eth0, run the following command.
        ovfenv --key vcloudnet.routes0.VMware_vCloud_Director 
      • For eth1, run the following command.
        ovfenv --key vcloudnet.routes1.VMware_vCloud_Director
    3. Change the static route value.
      The static routes must be in a comma-separated list of route specifications. For example, for eth0 you must run:
      ovfenv --key vcloudnet.routes0.VMware_vCloud_Director  --value "172.16.100.253 172.16.96.0/19, 172.16.100.253 192.168.100.0/24"
      • For eth0, run the following command.
        ovfenv --key vcloudnet.routes0.VMware_vCloud_Director  --value "new_static_routes0"
      • For eth1, run the following command.
        ovfenv --key vcloudnet.routes1.VMware_vCloud_Director  --value "new_static_routes1"
    4. Restart the network service on the vCloud Director appliance.
      systemctl restart vcd-ova-netconfig.service
  2. If you want to change the static route value permanently, change the OVF property by using the vSphere UI.
    The static routes must be in a comma-separated list of route specifications.
    Note: You must power off the VM to change the value of the property in vSphere.
    • Use the vSphere user interface to set the value of the vcloudnet.routes0.VMware_vCloud_Director property to the new route specification string.
    • Use the vSphere user interface to set the value of the vcloudnet.routes1.VMware_vCloud_Director property to the new route specification string.