VCH Admin Status Reference

The Web-based administration portal for virtual container hosts (VCHs), VCH Admin, presents status information about a VCH.

If the vSphere environment in which you are deploying a VCH does not meet the requirements, the deployment does not succeed. However, a successfully deployed VCH can stop functioning if the vSphere environment changes after the deployment. If environment changes adversely affect the VCH, the status of the affected component changes from green to yellow.

Virtual Container Host (VCH)

VCH Admin checks the status of the processes that the VCH runs:

  • The port layer server, that presents an API of low-level container primitive operations, and implements those container operations via the vSphere APIs.
  • VCH Admin server, that runs the VCH Admin portal.
  • The vSphere Integrated Containers Engine initialization service and watchdog service for the other components.
  • The Docker Engine server, that exposes the Docker API and semantics, translating those composite operations into port layer primitives.

Error

  • The VCH status is yellow.
  • The VCH status is yellow and an error message informs you that the VCH cannot connect to vSphere.

Cause

  • One or more of the VCH processes is not running correctly, or the VCH is unable to connect to vSphere.
  • The management network connection is down and the VCH endpoint VM cannot connect to vSphere.

Solution

  1. (Optional) If you see the error that the VCH is unable to connect to vSphere, check the VCH management network.
  2. In the VCH Admin portal for the VCH, click the link for the VCH Admin Server log.

  3. Search the log for references to the different VCH processes.

    The different processes are identified in the log by the following names:

    • port-layer-server
    • vicadmin
    • vic-init
    • docker-engine-server

  4. Identify the process or processes that are not running correctly and attempt to remediate the issues as required.

Registry and Internet Connectivity

VCH Admin checks connectivity on the public network by attempting to connect from the VCH to docker.io and google.com. VCH Admin only checks the public network connection. It does not check other networks, for example the bridge, management, client, or container networks.

Error

The Registry and Internet Connectivity status is yellow.

Cause

The public network connection is down.

Solution

Check the VCH Admin Server log for references to network issues. Use the vSphere Web Client to remediate the management network issues as required.

Firewall

VCH Admin checks that the firewall is correctly configured on an ESXi host on which the VCH is running. If the VCH is running in a cluster, VCH Admin checks the firewall configuration on all of the hosts in the cluster.

Error

  • The Firewall status is unavailable.
  • The Firewall status is yellow and shows the error Firewall must permit 2377/tcp outbound to use VIC.

Cause

  • The management network connection is down and the VCH endpoint VM cannot connect to vSphere.

  • The firewall on the ESXi host on which the VCH is running no longer allows outbound connections on port 2377.

    • The firewall was switched off when the VCH was deployed. The firewall has been switched on since the deployment of the VCH.
    • A firewall ruleset was applied manually to the ESXi host to allow outbound connections on port 2377. The ESXi host has been rebooted since the deployment of the VCH. Firewall rulesets are not retained when an ESXi host reboots.

Solution

  • If the Firewall status is unavailable:

    • Check the VCH Admin Server log for references to network issues.
    • Use the vSphere Web Client to remediate the management network issues as required.

  • If you see the error about port 2377, run the vic-machine update firewall command on the ESXi host or hosts to allow outbound connections on port 2377. For information about how to run vic-machine update firewall, see Open the Required Ports on ESXi Hosts.

License

VCH Admin checks that the ESXi hosts on which you deploy VCHs have the appropriate licenses.

Error

  • The License status is yellow and shows the error License does not meet minimum requirements to use VIC.
  • The License status is unavailable.

Cause

  • The license for the ESXi host or for one or more of the hosts in a vCenter Server cluster on which the VCH is deployed has been removed, downgraded, or has expired since the deployment of the VCH.
  • The management network is down, or the VCH endpoint VM is unable to connect to vSphere.

Solution

  • If the license does not meet the requirements:

    • If the VCH is running on an ESXi host that is not managed by vCenter Server, replace the ESXi host license with a valid vSphere Enterprise license.
    • If the VCH is running on a standalone ESXi host in vCenter Server, replace the ESXi host license with a valid vSphere Enterprise Plus or vSphere Remote Office Branch Office (ROBO) Advanced license.
    • If the VCH is running in a vCenter Server cluster, check that all of the hosts in the cluster have a valid vSphere Enterprise Plus or vSphere ROBO Advanced license, and replace any licenses that have been removed, downgraded, or have expired.

  • If the License status is unavailable:

    • Check the VCH Admin Server log for references to network issues.
    • Use the vSphere Web Client to remediate the management network issues as required.

results matching ""

    No results matching ""