LM to LM synchronization warning Alarm
search cancel

LM to LM synchronization warning Alarm

book

Article ID: 345814

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Title: LM to LM synchronization warning
Event ID:
lm_to_lm_synchronization_warning
Alarm Description

  • Purpose: Synchronization between remote locations failed for more than 3 minutes.
  • Impact: In this scenario, no stretched configuration data will be transferred between remote locations.



Environment

VMware NSX-T Data Center

Resolution

Steps to Resolve
For 3.0.1 and higher

Recommended Action:

Resolve the connection problem between the sites.

Steps to resolve the issue:

  1. Invoke the NSX CLI command get site-replicator remote-sites to get connection state between the remote locations. If a remote location is connected but not synchronized, it is possible that the location is still in the process of leader resolution. In this case, wait for around 10 seconds and try invoking the CLI again to check for the state of the remote location. If a location is disconnected, try the next step.
     
  2. Check the connectivity from Local Manager (LM) in the current location to the LMs in remote location via ping. If they are not pingable, check for flakiness in WAN connectivity. If there are no physical network connectivity issues, try the next step.
     
  3. Invoke the NSX CLI command set debug to enable debug mode.
    Invoke the NSX CLI command get site-replicator remote-sites debug. Record the master controller UUID for the remote site from the results.
    Invoke the NSX CLI command get cluster status. In the result, locate the Group Type labelled as 'CONTROLLER' and correlate the controller UUID from the previous command's output to determine the IP of the master controller for the remote site.
    Log onto the appliance using the identified IP address and restart CCP service using the following command.
    service nsx-ccp restart
    If issue persists after the restart, proceed to next step.
     
  4. Repeat the above step on the remote site.

Maintenance window required for remediation? No

Additional Information