VMware HCX

 View Only
  • 1.  unable to protect VM via HCX DR functionality

    Posted Aug 15, 2023 02:39 PM

    Hi All,

     

    I am trying to protect a VM via HCX DR and it returning below error

    I verified from OnPrem vCenter is able to reach Cloud vCenter over 443

    I verified from OnPrem HCX Connector is able to reach Cloud vCenter over 443

     

    any suggestion here .. thanks

    lvaibhavt_0-1692110290506.png

    java.lang.RuntimeException: Operation Prepare Target failed. Reason : Error communicating to VC endpoin nsx-vc-01.home.local:443. Reason: SocketTimeoutException
    2023-08-15 14:19:48.562 UTC [VsphereReplicationService_SvcThread-4985, T:'protect', R:protect-a74bc530-76d8-41f9-873b-4125e5ff5537, J:29b865a1-1a2c-4a1d-a9bb-da2927f725cd, S:FETCH_CGW_IDS, , TxId: 58b453d2-7344-4d59-8ef8-7aa47eefe35f] INFO DR.OP- Noticed failure for sub-operation [PREPARE_DESTINATION/Prepare Target] with result as {"isDone":true,"reason":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","taskSpec":{"name":"Prepare Replication Destination","reason":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","status":"error","taskId":"4ee3b70f-746e-456e-87d3-e0f9c89c0aa9","endTime":1692109185187,"message":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","progress":100,"extraInfo":{},"requestId":"Prepare Replication Destination-1692109123654","startTime":1692109123238,"messageIndex":4},"isSuccess":false,"errorMessage":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException"}
    2023-08-15 14:20:03.648 UTC [VsphereReplicationService_SvcThread-4972, T:'protect', R:protect-a74bc530-76d8-41f9-873b-4125e5ff5537, J:29b865a1-1a2c-4a1d-a9bb-da2927f725cd, S:FETCH_CGW_IDS, , TxId: 58b453d2-7344-4d59-8ef8-7aa47eefe35f] INFO DR.OP- Noticed failure for sub-operation [PREPARE_DESTINATION/Prepare Target] with result as {"isDone":true,"reason":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","taskSpec":{"name":"Prepare Replication Destination","reason":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","status":"error","taskId":"4ee3b70f-746e-456e-87d3-e0f9c89c0aa9","endTime":1692109185187,"message":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException","progress":100,"extraInfo":{},"requestId":"Prepare Replication Destination-1692109123654","startTime":1692109123238,"messageIndex":4},"isSuccess":false,"errorMessage":"Error communicating to VC endpoint nsx-vc-01.home.local:443. Reason: SocketTimeoutException"}



  • 2.  RE: unable to protect VM via HCX DR functionality

    Posted Aug 16, 2023 03:11 PM

    I'm experiencing a similar issue in my environment...



  • 3.  RE: unable to protect VM via HCX DR functionality

    Posted Aug 21, 2023 07:44 PM

    Do you have "vSphere Replication" enabled on the VMkernel Adapter? I'm not sure if vSphere Replication NFC" is required for Disaster Recovery, I just know it's required for Cold Migration and it might be used for the DR feature in HCX.



  • 4.  RE: unable to protect VM via HCX DR functionality

    Broadcom Employee
    Posted Aug 29, 2023 08:13 AM

    Does HCX have a proxy configured?



  • 5.  RE: unable to protect VM via HCX DR functionality

    Posted Aug 29, 2023 12:46 PM

    nope



  • 6.  RE: unable to protect VM via HCX DR functionality

    Broadcom Employee
    Posted Aug 29, 2023 02:00 PM

    Have all required connectivity between the various appliances as per https://ports.esp.vmware.com/home/VMware-HCX ?

    And is vSphere Replication tagged on a vmk interface (as asked above)?



  • 7.  RE: unable to protect VM via HCX DR functionality

    Posted Sep 27, 2023 11:56 AM

    Use the following link to double-check if all the required ports are opened.
    https://ports.esp.vmware.com/home/VMware-HCX

    Did you configured a separate network profile for the replication service? or you are using the management profile for both management and replication?