Computing.Net > Forums > Networking > IP confliction logs with own MAC

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

IP confliction logs with own MAC

Reply to Message Icon

Name: jagjit
Date: April 7, 2009 at 11:58:37 Pacific
OS: na
CPU/Ram: na
Subcategory: Routers and Hubs
Comment:

Hi,
Issue: IP confliction error on Sun servers with same MAC address. Six servers facing the problem (192.168.X.X), it comes with this range only. However no other ip range has this problem. These ranges are only dedicated for servers. Static IPs are given.

Issue frequency: very occassionaly (may be after 1 month / week or any day), however it can last for many hour which effects service.

Setup: All Sunserver connected with cisco switch.

Checked/done: No mean any one is using same IP. At network level checked STP for looping. Flushed mac of switch. No logs on switch

Switch port/ports configuration:

switchport mode access
switchport access vlan
switchport host

I want to know if mac- address binding will work. As ips are static, I am wondering if it will work.



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: April 7, 2009 at 13:17:03 Pacific
Reply:

Mac address filtering relates to dhcp. You have static ip.

Have you reviewed you dhcp scope to confirm these addresses are NOT in the dhcp scope?

Next time you have a server ip conflict down the server/disconnect from the network physically and then ping that ip address. If you get a return you know you have a station with that address causing the conflict.


0

Response Number 2
Name: jagjit
Date: April 7, 2009 at 20:40:53 Pacific
Reply:

Thank you for response.

Checked the same. No scope in DHCP. No other ip in network after removal of network cable. No ping response.


This problem is coming on multiple servers having multiple NICs.

This problem arises with particular series 192.186.X.X.

Regards,
Jagjit Brar


0

Response Number 3
Name: wanderer
Date: April 8, 2009 at 06:16:47 Pacific
Reply:

from one server list the ips of all nics.

also post the EXACT error message please

Just to confirm you are getting a ip conflict not a NAME conflict?


0

Response Number 4
Name: jagjit
Date: April 13, 2009 at 05:16:46 Pacific
Reply:

Hi,

Please find the logs.


# cat /var/adm/messages.3 | grep -i hardware
Mar 16 23:39:42 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 01:19:52 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 01:54:51 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 02:39:43 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 03:09:51 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 03:29:50 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 04:14:47 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 05:19:43 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 05:44:44 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 17 06:44:53 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 05:34:53 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 05:59:59 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 06:23:34 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 06:40:00 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 06:54:59 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 07:29:58 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!
Mar 18 07:59:59 delhimail-ph ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:14:4f:41:4b:c3' trying to be our address 192.168.180.010!


Regards,
Jagjit Brar


0

Response Number 5
Name: Curt R
Date: April 13, 2009 at 06:02:55 Pacific
Reply:

All instances show the same MAC address:

00:14:4f:41:4b:c3

I'd start by finding out which machine has that MAC and I'd start looking closely at what that unit is doing.


0

Related Posts

See More



Response Number 6
Name: wanderer
Date: April 13, 2009 at 06:31:41 Pacific
Reply:

Please post a Sun equivalent of ipconfig /all from this machine.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: IP confliction logs with own MAC

ip conflict with another sytem www.computing.net/answers/networking/ip-conflict-with-another-sytem/18484.html

IP conflict www.computing.net/answers/networking/ip-conflict/34916.html

IP Conflict www.computing.net/answers/networking/ip-conflict/15585.html