High Availability troubleshooting: Virtual IP not working

High Availability troubleshooting: Virtual IP not working

Issue description  

The virtual IP does not function properly in the High Availability (HA) setup. This impacts EventLog Analyzer access and syslog log collection.

Possible causes  

  • Wrong interface name in StartHA.vbs or StopHA.vbs
  • Virtual IP isn’t in the same network range or subnet
  • Syslog devices are not set to use the virtual IP
  • Missing license files on the secondary server
  • Elasticsearch is not configured for HA
What to check first  
  • Is the interface name correct in StartHA.vbs and StopHA.vbs?
 
  • Is the virtual IP in the same subnet?
  • Were license files copied from primary to secondary?

Resolution steps

Step 1: Confirm the interface name in the scripts is correct.
Step 2: Make sure the virtual IP is in the same subnet.
Step 3: Verify syslog devices are sending logs to the virtual IP.
Step 4: Copy these files from primary to secondary:
    • <EventLog Analyzer Home>\lib\petinfo.dat
    • <EventLog Analyzer Home>\lib\AdventNetLicense.xml
Step 5: Check Elasticsearch is configured for HA.

Validation and testing

  • Ping the virtual IP
  • Open EventLog Analyzer using the virtual IP
  • Check if syslog logs are received

Tips  

  • Make sure settings match on both servers


      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • Troubleshooting: Disk space issues in EventLog Analyzer

                      Issue description EventLog Analyzer server might run out of storage due to misconfiguration and other known factors. This article offers troubleshooting steps to resolve when your disk or drive where the application is installed is full and help you ...

                    • Troubleshooting guide: EventLog Analyzer UI is unresponsive

                      Overview This document outlines the common causes and recommended steps to resolve the issue when the EventLog Analyzer UI becomes unresponsive. Possible causes Insufficient system resources High CPU or memory usage on the server. Low disk space in ...

                    • Troubleshooting: Some events are not available in the Search tab | EventLog Analyzer

                      Issue description The user might not be able to see some events that happened natively within the EventLog Analyzer Search tab. This article offers steps to review and resolve this issue. Possible causes The event was not recorded natively due to ...

                    • IIS Issue Troubleshooting [INTERNAL]

                      Issue 1 : Site "Failed" status Scan the IIS Server in which the site status is Failed in IIS Server pages. You can get the IIS Log Folder name from Log Directory. eg : W3SVC4 Search in ELA serverout for that Log folder trace followed by "File does ...

                    • Troubleshooting guide: No data available in a Compliance Report

                      Overview This document provides a technical explanation and resolution guide when there is no data being displayed under compliance reports in ManageEngine EventLog Analyzer. Compliance reports include regulatory standards such as PCI-DSS, HIPAA, ISO ...

                      Related Products