IP collision detection

Last Updated: Aug 06, 2018 07:17AM PDT

IP collision is caused by several servers in the network which has the same IP. 

If you got the following message on your NooBaa console:
IP conflict
it means that NooBaa has detected an IP collision of its own IP with another device in the network.

This article would help you to solve this issue. There are two main courses.

Changing NooBaa core IP

Before you perform this step, please make sure you configured DNS name for NooBaa core. Setting DNS name will make sure that the storage node can connect to NooBaa core regardless of its IP. 

Read more about DNS settings here

Static IP - In case NooBaa core is using a static IP, the easiest solution is to change this IP to another IP.  
DHCP - In case NooBaa core is configured with DHCP, you can go the first install wizard and re-apply the DHCP settings. if the problem persists you will need to find the second device which holds this IP.

Finding the second device 

If using static or if re-applying DHCP didn't help. You can try to find the second server by one of the following:
  1. In order to get all the MAC addresses which are connected to this IP, you can run arp -a  command from a LINUX machine.
  2. You can try to get information about the second server by running the command nbtstat -a <IP> from a WINDOWS machine.
  3. If the IP is associated to a DNS name, you can use the nslookup command from a LINUX server.
  4. You can try to find the hostname associated to this IP by running the host command from a Linux server. 
  5. You can install the nbtscan package on a Linux server and run it.
Did you find this article helpful?
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found