Mitel 3300 MXe excessive network ARPing 1

[mkangiser]

We have a Mitel 3300 MXe with one IP phone on or network and the system will send a network ARP every 1 second looking for address 192.168.1.2 but all our network equipment have an 10.0.1.x address.

The 3300 is at 10.0.1.10 (on switch port 1 of 2) and the IP phone on 10.0.1.150. We are not using the WAN/DMZ port.

I’ve gone thru the GUI interface looking for any reference to the 192.168.1.1 address and the mac address that this IP is at.

The 10.0.1.10 IP is from the mac address 08:00:0f:2d:94:99 and the arping keeps coming from 08:00:0f:33:14:f8, both of which appear on switch port 1. I’ve checked all the DHCP settings and they are all disabled.

Any thoughts on how to disable the 3300 from ARPing? I’ve asked or installers and they supposedly contacted Mitel but they never came back with a solution.

 

[Supernova99]

Have you set the IP address for the L2 port?
Also do you have a E2T card?
The MAC addresses are Mitel so it has to be one of these devices
Check for the L2 in the system IP properties form as the default value is 192.168.1.1
You will also see in here the E2T settings however we need to determine if you have on fitted first
go to Hardware Compute Cards form and see if there are 2 entries if there is only 1 then you only have an RTC
If there are 2 entries I suspect that the E2T has not been configured correctly by default it is set up as DHCP to get an IP address from 192.168.1.2

If it is there respond to this post and I will provide details of how to change it.

Share what you know - Learn what you don't

 

[mkangiser]

Hi Supernova99,
It looks like the Layer 2 switch IP is not set and I don't appear to have an E2T card. What should I put as an IP?

Here is the System IP Configuration:

System IP Address: 10.0.1.10
Subnet Mask: 255.255.255.0
Gateway IP Address: 10.0.1.4
Layer 2 (L2) Switch IP Address: 0.0.0.0
E2T Card IP Address: Not Installed

Thanks,
Marty

 

[mkangiser]

I assumed you can just use an unused IP on my 10.0.1.x network but I got a message saying the system would need to be rebooted and I wasn't positive if it would do it if I clicked OK, so I cancelled out of changing it. Bosses don’t like their phones going down in the middle of the day. I will wait to here back from you.
Marty

 

[Supernova99]

Unfortunately it will require a reboot to do this
However it will not reboot when you change it
I would scedule a reboot for tonight that way there will be no downtime

So change the L2 IP address click OK to the warning
go to the maintainance commands and turn on programmed schedule reboot (default will be tonight at 02:15)

You are correct just use an unused address

Share what you know - Learn what you don't

 

[mkangiser]

Thanks Supernova, we will see what happens tonight.

Marty

 

[mkangiser]

I’m not sure if it was related but after the reboot we lost all phone service. After rebooting the system several times I got the service back and the ARP went away. I guess the problem is solved until we need to reboot the system again.
Marty

 

[Supernova99]

Are you saying this morning that you did not have any phone service or you never had phone service during reboot?

The system will take around 20 mins to reboot and during this time you will not have any phone service.


Share what you know - Learn what you don't

 

[mkangiser]

It took 16 minutes to reboot and about 4 hours later (6:15am) I tried calling into the office from home and got a fast busy.

I checked with our phone company and they showed no issues so I came in early and was able to log into the admin gui and my settings (L2 IP) had taken. I decided to undo my changes, reboot the system and the IP was still there so I deleted the IP and rebooted again and the changes took (no IP) but still no dialing into or out of the office. I rebooted one more time and it started working. I believe the alarm said no trunk lines available. The good part was the system was working 15 minutes before work started.

I really don’t think it had anything to do with the IP address, I think it was related to the reboot(s).

I’m not too worried the system works pretty well but I might send a note to our Mitel tech in case they want to view the logs.

Thanks for your help!
Marty

 

[Supernova99]

I have seen this before when after a reboot where the ISDN trunks do not come back in service and another reboot is required.

Glad you got it sorted in time for the start of the day.

Share what you know - Learn what you don't