Search the VMware Knowledge Base (KB)
View by Article ID

Plugin status for vSphere Replication 6.5 reports unknown (2151155)

  • 0 Ratings

Symptoms

  • Logging in to Web Client, the VR plugin reports unknown.
  • In the Virgo logs, you see entries similar to:

    data-service-pool-1611 70001083 100106 200074 com.vmware.vr.provider.appliance.AppliancePropertyResolver getApplian
    ceStatus Returning UNKNOWN, failed to retrieve status. com.vmware.vr.client.topology.VcNotAccessibleException: vCenter Server is not available.
    at com.vmware.vr.client.topology.TopologyHelper.getVcService(TopologyHelper.java:126)
    at com.vmware.vr.provider.appliance.AppliancePropertyResolver.getExtension(AppliancePropertyResolver.java:217)
    at com.vmware.vr.provider.appliance.AppliancePropertyResolver.getApplianceStatus(AppliancePropertyResolver.java:163)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    vr-topology-main-thread-12 70000587 100009 200005 com.vmware.vr.client.topology.impl.schedule.TaskProviderImpl Entity op failed with : com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 403

Cause

This issue might occur when web filter blocks port 80 for further communication.This communication is basically for the vCenter traffic.

Resolution

To resolve this issue:
 
  1. Run this command in production VC and VR:

    curl -v -p -x http://FQDN_Target Site:80 sdkTunnel:8089

    If you see this output, it indicates communication is blocked:

    < HTTP/1.1 403 Forbidden
    < Server: http_scan_byf/3.3.1
    < Mime-Version: 1.0
    < Date: Wed, 02 Aug 2017 17:43:44 GMT
    < Content-Type: text/html
    < Content-Length: 8639
    < X-Squid-Error: ERR_ACCESS_DENIED 0
    < Vary: Accept-Language
    < Content-Language: en
    < X-Cache: MISS from x.x.x.x
    < Via: 1.1 x.x.x (http_scan_byf/3.3.1)
    < Connection: keep-alive


    Where x.x.x is the FQDN of the web filter which was blocking the communication.
  2. After you specify a rule to allow the traffic for port 80 under web filter, run the same command in step 1.

    You should see output similar to:

    * Connected to vCenter_FQDN (x.x.x.x) port 80 (#0)
    * Establish HTTP proxy tunnel to sdkTunnel:8089
    > CONNECT sdkTunnel:8089 HTTP/1.1
    > Host: sdkTunnel:8089
    > User-Agent: curl/7.47.1
    >
    < HTTP/1.1 200 OK
    < Date: 
    < Content-Type: text/html
    < Content-Length: 0
    <*
    Proxy replied OK to CONNECT request
    > GET / HTTP/1.1
    > Host: sdkTunnel:8089
    > User-Agent: curl/7.47.1
    > Accept: */*


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: