NSX Local Manager latest backup status not available with error "LM not available"
search cancel

NSX Local Manager latest backup status not available with error "LM not available"

book

Article ID: 431580

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Global Manager (GM) is unable to retrieve the backup status of the Local Manager (LM).
  • The NSX UI displays the Latest Backup status as "Not available" with "Error: LM is unreachable(Error code: 29270)".

  • gmanager.log shows connection timeout error to local manager.

not able to get data from remote site <REMOTE_SITE_ID_MASKED>. Error org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://<REMOTE_IP_MASKED>/policy/api/v1/ui-clusters-rtep-status": Connect to <REMOTE_IP_MASKED>:443 [/<REMOTE_IP_MASKED>] failed: Connect timed out; nested exception is org.apache.http.conn.ConnectTimeoutException: Connect to <REMOTE_IP_MASKED>:443 [/<REMOTE_IP_MASKED>] failed

Environment

VMware NSX

Cause

Connection timeout from Global Manager to Local Manager causing GM unable to retrieve real time status from LM.

Resolution

To resolve this issue, verify the network connectivity between the NSX Global Manager (GM) and Local Manager (LM). Follow these steps:

  • Inspect Intermediate Network Devices: Ensure that all physical/virtual switches, routers, and firewalls between the GM and LM are functioning correctly and not dropping packets.

  • Firewall Rules: Confirm that the required ports for GM-LM communication (e.g., TCP/443, TCP/1236) are allowed on all firewalls.

  • Base Network Configuration: Validate the underlying network settings on both the GM and LM appliances, specifically:

    • IP Addresses: Ensure correct CIDR formatting.

    • Default Gateways: Verify that the gateways are reachable and correctly configured.

    • MTU Settings: Ensure consistent MTU sizes across the path to avoid fragmentation issues.