Duplicate IP issue

[Ceaserx]

i have a duplicate IP issue on a client's ICP3300 MXE running version 9ur3.

Duplicate IP Address Detector
Description: Possibly 2 computers with the same IP address (10.45.37.7). One of those computers has MAC address 08:00:0f:2b:7d:43. If this IP is used by the Mitel RTC card, E2T card, a phone or router, there may be disruption in telephone service.

This is the IP of the Layer 2 Switch. There is definitely not another device on the network with the same IP. I have even changed this IP last night from .37.8 to the current .37.7 address. Almost directly after the reboot apllied the change i got another duplicate error in the logs.


Currently the E2T card's IP is: .37.6

Should this be the same as the Layer 2 switch IP?

How can i correct this issue

 

[Waldosworld]

The RTC, E2T and L2 should all have there own static IP address.

 

[bribob]

If you ping 10.45.37.7 (or .8) from a host on the 10.45.37.0 network, and then check your ARP cache (arp -a), do you see the same MAC address (08:00:0f:2b:7d:43)?

Assuming that 7d:43 is a set, have a look at your DHCP leases (either on the 3300 or external server) and see what IP address has been handed out.

Can you verify that the E2T cards MAC is not 08:00:0f:2b:7d:43?

-b

 

[LoopyLou]

If the 3300 is handing out IP addresses for the phones on the voice VLAN, set the 3300 to service only phones. There is a knowledge base article on how to do this and its quite easy. As long as the reported address is not part of the DHCP scope, this issue should be solved.

 

[kwbMitel]

Loopylou, the 3300 will not hand out addresses that conflict even if it is part of the range and available.

The key here is to discover what device has the MAC address above. On that Note, Ceaserx, what is the mac of the other conflicting device, the system would have told you both and it might be important.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Ceaserx]

The Mitel is not the DHCP server. Thanks for the advice, will get all the info and post again tomorrow or the day after.

 

[Jakt99]

Also and probably stating the obvious...

When chasing mac addresses on devices a good tip to ID the device is review the 1st three byte of the address, which indicates the vendor manaufacture of the NIC. For example in the case of mitel devices, in general they begin with:

08 00 0f xx yy zz

cheers