Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > After a failover event Windows detects an IP address conflict

After a failover event Windows detects an IP address conflict

Table of contents

Updated August 1, 2016

Overview

You receive an IP address conflict error immediately after a failover event.

Environment

Any environment with SolarWinds High Availability enabled, such as the following:

  • NPM 12.1
  • SAM 6.4
  • Orion Platform 2016.2

 

Detail

 

When you enable High Availability, you may receive the following error during or immediately after a failover event:

Another computer on this network has the same IP address as this computer. Contact your network administrator for help resolving this issue.

You may also see errors in the Windows Event Log similar to the following:

The system detected an address conflict for IP address 192.168.10.1 with the system.

The failing pool member may take longer than expected to release the virtual IP (VIP) address. This condition should be temporary and resolve itself automatically within a few seconds.

 

 

Last modified

Tags

Classifications

Public