Adding AVS NSXT Manager as a datasource in Aria operations for Networks shows an error message, NSX Manager Hostname/IP is unreachable on GUI
search cancel

Adding AVS NSXT Manager as a datasource in Aria operations for Networks shows an error message, NSX Manager Hostname/IP is unreachable on GUI

book

Article ID: 381632

calendar_today

Updated On:

Products

VMware Aria Operations for Networks

Issue/Introduction

  1. GUI error message seen is as below:

    NSX Manager Hostname/IP is unreachable.
  2. GUI Screenshot exhibiting the issue is as below:



  3. In SaaS service logs on the appliance we see that datasource add operations fails with below error entries:

    /var/log/arkin/saasservice/saasservice.STDOUT-2024-11-04-17.14.46.log.error:2024-11-05T19:17:32.433Z INFO vnera.SaasListener.ServiceThriftListener_ServiceImpl dw-265660 - POST /resttosaasservlet sendMessageToCollector:6199 wait over for collector msgType UPDATE_DATA_PROVIDER_CONFIGURATION requestId 7ae9f7c4-###-4aa7-####-f900###6c72a for collector 18895:IDGS5V##########1SIKMPZTIC:saastocollectorservlet
    /var/log/arkin/saasservice/saasservice.STDOUT-2024-11-04-17.14.46.log.error:2024-11-05T19:17:32.434Z ERROR vnera.SaasListener.ServiceThriftListener_ServiceImpl dw-265660 - POST /resttosaasservlet sendMessageToCollector:6220 Request timed out and no response received in timeout (40 Sec) window. Host could be unreachable or request is taking too long. customerId 18895 collectorId IDGS5V##########1SIKMPZTIC msgType UPDATE_DATA_PROVIDER_CONFIGURATION requestId 7ae9f7c4-###-4aa7-####-f900###6c72a
    /var/log/arkin/saasservice/saasservice.STDOUT-2024-11-04-17.14.46.log.error:2024-11-05T19:17:32.434Z INFO vnera.SaasListener.ServiceThriftListener_ServiceImpl dw-265660 - POST /resttosaasservlet removeFromIssuedRequest:5770 removing request 7ae9f7c4-###-4aa7-####-f900###6c72a

    As seen in about output the request timeout happens and takes more than 40 seconds which is quite high.

Environment

VMware vRealize Network Insight 6.8
VMware vRealize Network Insight 6.9
Aria Operations for Networks 6.10.0
Aria Operations for Networks 6.11.0
Aria Operations for Networks 6.12.0
Aria Operations for Networks 6.12.1
Aria Operations for Networks 6.13.0
Aria Operations for Networks 6.14.0

Cause

This issue is seen due of latency between collector and datasource and/ or between collector and platform appliances.

The recommended network latency between platform and collector VMs for optimal performance is up to 150ms. The system performance might degrade beyond this limit.




Resolution

To workaround this default timeout window for SaaS service can be re-configured  to see if this helps for completion of add data sources and for the next steps if this workaround doe snot helps.

Please open a support case with Broadcom Support and refer to this KB article. For more information, see Creating and managing Broadcom support cases.