Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Collision issue with NEC SL2100

Status
Not open for further replies.

wally1214

Technical User
Apr 27, 2020
3
PH
Hi Guys,

Good day.

I have assigned a static IP address of 10.1.1.230 to our NEC phone system.
Default gateway address is set to 10.1.1.1 and DHCP pool range between 10.1.1.100 to 10.1.1.190.

I'm not sure why IP collision error is being detected on system alarm.

MIN 0057 WAR 27/04/20 19:02 IP Collision -none- 00 00 1
MIN 0057 WAR 27/04/20 19:07 IP Collision -none- 00 00 1
MIN 0057 WAR 27/04/20 19:12 IP Collision -none- 00 00 1

Any help would be appreciated.
Thank you.

Kind regards,
Wally
 
Start a WIN continuous ping, then unplug the system from the network. Does the ping continue or stop?
 
@belevedere
Thanks for your input. I will try your recommendation tomorrow morning.

Tried to changed NEC pbx address to 10.1.1.10 and rebooted pbx to apply the changes, got the same IP collision issue.

I'm sure that static IP is out from the DHCP pool and yet still getting this problem.
 
The ping idea is good except that I have encountered places where Windows blocks ping replies by default so it is not as reliable a test as it once was.

Could the collision be a CDMA collision vs. an IP address conflict? Perhaps there is trouble on the switch port, the PBX Ethernet port, or the patch cable?
 
Try downloading one of those IP scanner programs. Run it on the network.
 
Hi Guys,

G'day.

Did a continuous ping on 10.1.1.230 and got a reply.
Then unplugged NEC pabx and got a time out which is normal.

ping_gdm5q1.png


Ran IP scanner program and found no conflicting IP address whether NEC pabx is connected or not.

NEC pabx disconnected
without_cokkvy.png


NEC pabx connected
with_ogunte.png


Sad to say, I'm still seeing IP collision alarm.
systemalarm_ufucj1.png


With the above steps done, what would be our next course of action?

Thanks for your assistance in advance.

Regards,
Wally
 
Check the programs that have addresses in them. Usually if you try to program in a duplicate the system yells at you.
10-12
84-26
10-23 - SIP trunks
10-28
10-29
10-14
Even though you are getting this alarm, is the system affected in any way?
And, make sure you have the latest software level loaded.
After that, call NEC NTAC. They may be able to look at DIM files and traces.
 
Hey Wally.

We see this quite often when customer is using Cisco switches.

I believe it’s caused by ARP probing.
Can either disable this on the switches, or turn the alarm off in the PBX.
Just be very sure there isn’t a duplicate IP, as once the alarm is off, you won’t get told it there is an actual conflict.

Bit of background info:
 
Good afternoon

My is Ambao and I need help on Network how to link to pbx NEC 2100 and SV9100

 
ambao, you should start another thread for this. But, frankly speaking lose the 2100, get another 9100. Networking is one the big reasons why we have a SV9100. Then you can choose CCIS or Netlink depending on what you want to do.
 
Good morning did you ever find a resolution to your IP Collision issue? Having the same issue on a SV9100.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top