Jump to content
Welcome to our new Citrix community!

I am getting ipConflict in log but don't know why


Volt Amper

Recommended Posts

Hi, 

Citrix Load balancer is generating every minute  "ipConflict" logs, and I don't know why. Whole system is working as expected, I did some troubleshooting however it is not clear why this log is generated:

 

2019 Nov 07 10:35:44 logserver->10.10.0.10  11/07/2019:10:35:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246540 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:36:44 logserver->10.10.0.10  11/07/2019:10:36:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246541 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:37:44 logserver->10.10.0.10  11/07/2019:10:37:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246542 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:38:44 logserver->10.10.0.10  11/07/2019:10:38:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246543 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:39:44 logserver->10.10.0.10  11/07/2019:10:39:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246544 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:40:44 logserver->10.10.0.10  11/07/2019:10:40:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246545 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)
2019 Nov 07 10:41:44 logserver->10.10.0.10  11/07/2019:10:41:44 GMT LOADBALANCER01 0-PPE-0 : default SNMP TRAP_SENT 2246546 0 :  ipConflict (ipConflictAddr = 10.10.0.10, nsPartitionName = default)

 

I am not sure if this is a sign that something is misconfigured,

 

I will appreciate any help.

 

700grm

 

 

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

Are you in an ha pair where the two devices aren't communicating? So you do have a conflict between two systems trying to be primary at once.

Are any of your VIPs actually in conflict with actual IPs in the environment (nslog can give you the mac addressses)

Did you actually configure any of your server (destination IPS) and lb vservers (or vice versa)?

Are you possibly experiencing any mis configured channel settings so a switch things you have two interfaces plugged in instead of an aggregated channel.

 

Check syslog for HA errors and other errors:

shell

cd /var/log

tail -f ns.log | grep -v CMD_EXECUTED    

# this version excludes audit/navigation events

# Look for ha communication failures or anything that is unexpected

 

Check nslog for events and console messages and indications of network issues such as a switch muting ports

shell

cd /var/nslog

nsconmsg -K newnslog -d event

nsconmsg -K newnslog -d consmsg

 

The odds are that the ipconflict will be here too, but you may see "switch muting ports" or other indicators of an outside issue that might help you figure out the root cause.

 

Link to comment
Share on other sites

  • 2 months later...

Did you do a trace from your switch? This would probably bring some light into this dark night. This issue will for sure lead to packet loss, packets out of sequence and similar problems, so L4 issues. From perspective of the application everything seems to be fine (that's what we have TCP for, isn't it?). From perspective of the network a nightmare. And performance will go up after resolving the issue!

 

I have seen similar problems after cloning VMs (and preserving the MAC addresses).

 

Cheers

Johannes Norz

CCI, CCE-N, CTA

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...