Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > 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
15:07, 24 Aug 2016

Tags

Classifications

Public