Error: VSP runtime status unknown and VMSP adapter NoRouteToHostException
search cancel

Error: VSP runtime status unknown and VMSP adapter NoRouteToHostException

book

Article ID: 443190

calendar_today

Updated On:

Products

VCF Operations VMware Cloud Foundation

Issue/Introduction

  • In VMware Cloud Foundation 9.1, the VSP runtime status shows as "unknown" and the VMSP adapter fails to collect resources, reporting a "No route to host" exception.
  • VSP runtime status is unknown.
  • Resource collection for the VMSP adapter fails.
  • VMSP nodes are reachable via ping from VCF Operations collector nodes, but the REST API connection fails.
  • VMSP nodes are reachable via ping from the VCF Operations collector nodes.

    Following error seen in the - /usr/lib/vmware-vcops/user/log/adapters/VmspAdapter/VmspAdapter_#####.log

    ERROR VmspAdapter ###### [ops@#### threadId="###" threadName="Collector worker thread 10" instanceId="#####"] [(#####) com.broadcom.adapter3.vmsp.collector.ResourceCollector.collectVMSPResources] - Error occurred while collecting resources from VMSP :
    com.broadcom.adapter3.vmsp.client.exception.NetworkException: Failed to connect REST Endpoint : NoRouteToHostException - No route to host

  • Validate VMSP cluster health state with - 
    • ssh control-pane-ipaddress@vmware-system-user
    • curl -sk 'https://<control-pane-ipaddress>:30006/status' | jq



Environment

VCF 9.1

Cause

This issue occurs due to a DNS record conflict where the VSP cluster gateway IP address overlaps with a production reserved IP address. This overlap prevents the REST API calls from being correctly routed to the VSP cluster components.

Resolution

  1. Verify the DNS records for the VSP cluster gateway.
  2. Ensure the VSP cluster gateway IP address is unique and does not overlap with any reserved production IP addresses.
  3. Ensure the DNS record resolves correctly to the designated POC CIDR.
  4. Execute a cleanup of the VSP components if connectivity is not restored after the DNS correction.
  5. In the VCF Operations UI, navigate to Administration > Integrations, select the VMSP adapter, and click Validate Connection.
  6. Confirm the VSP runtime status updates to healthy.

Additional Information