The vCenter Server in the management workload domain is inaccessible from a Windows or Linux jump VM after upgrading an unmanaged host.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• The vCenter Server in the management workload domain is inaccessible from a Windows or Linux jump VM after upgrading an unmanaged host.
• You see a second default route on the network interface attached to the 192.168.100.x network on the vCenter Server appliance.
• Attempts to deploy vRealize Operations Manager via the SDDC Manager UI will fail.

Environment

VMware Cloud Foundation 2.3.x

Resolution

This is a known issue affecting VMware Cloud Foundation 2.3.1. There is currently no resolution.

Workaround:
To workaround this issue, use the following steps to delete the second default route on the vCenter Server in the management workload domain.

1. Log in to the SDDC Manager Controller virtual machine as the root user. Issue the /home/vrack/bin/lookup-passwords command to obtain the root password for the vCenter Server Appliance.

Note: You will see output similar to the following:
 

       vCenter
       identifiers: 10.0.0.26,vcenter-1.vrack.vsphere.local
       workload: MGMT
       VM: vcenter-1
           username: root
           password: q5^L3T!V^-2Fw2D5+U
               type: SSH

Note: In a multi-workload domain environment, you will see multiple vCenter entries. Make a note of the one where the workload value is MGMT.

2. Log in to the vCenter Server Appliance for the management workload domain, either at the console or via SSH, as the root user. Use the password obtained in Step 1.
3. Verify that there are two default routes by issuing the ip route | grep default command.

Note:  You will see output similar to the following:

       default via 192.168.103.254 dev eth1 proto static
       default via 10.115.0.1 dev eth0 proto static

Note: If only one route is present, do not proceed to the next step.

4. Delete the second route on the 192.168.100.x network by issuing commands similar to the following:

route delete default gw 192.168.103.254 eth1
sed -i '/^Gateway=/ d' /etc/systemd/network/10-eth1.network
 

Note: Replace 192.168.103.254 with the IP address returned in Step 3 and replace eth1 with the NIC name returned in Step 3. Do not delete the route using the eth0 interface.

The vCenter Server in the management workload domain should be accessible again.

Note: These steps should be followed after each unmanaged host upgrade.

Additional Information

To be alerted when this article is updated, click the Subscribe to Document link in the Actions box.