Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bigred1022

Pages: [1]
1
Mitel MiVoice Business/MCD/3300 / Re: Duplicate IP issue
« on: August 17, 2018, 10:28:44 AM »
The IP address on that form is 192.168.1.20 which is the MCD.  192.168.1.19 is the application suite (MiCollab, NuPoint).  Sorry I should have mentioned that originally.

2
Mitel MiVoice Business/MCD/3300 / Duplicate IP issue
« on: August 17, 2018, 10:06:18 AM »
Hey everyone,

So I'm at my wits end with this issue and I'm hoping someone can help me out.  Our phone system is reporting duplicate IP addresses for the phone system itself and another device (our firewall).  This is simply just not true because everything is statically assigned and both MAC addresses have been confirmed many times to be correct.   Here is how it is setup:

Firewall (Sonicwall NSA2600) - LAN Interface is statically set to 192.168.1.18

Mitel 3300 system (VMWare ESXi) - LAN Interface is statically set to 192.168.1.19

Phone system is saying .19 is duplicated and pointing to itself and the Sonicwall.  If I check any ARP table in our network, it shows the proper entries for both units.  Also, no other network monitoring device reports duplicate IP's anywhere in the network.

If I check the phone system ARP table, it shows the following:

192.168.1.18     c0:ea:e4:82:c7:02 0x8405 70     1055       eAtlas0
192.168.1.19     c0:ea:e4:82:c7:02 0x8405 41     520984     eAtlas0

Now this is obviously incorrect and I don't know where it's getting that information from.  That MAC address is correct for .19.  However, .18 should have a different, correct, MAC address.

Any ideas at all on why or how this is happening and how do I get it cleared up.  Thanks in advance-

System info:
MiVoice Business Express 8.0.1.9
 Mitel Standard Linux 10.5.23
 OVA 8.0.1.9

3
Yes we did.  Mitel support has now pretty much given up (which is just fantastic).  They say our firewall isn't forwarding the traffic to .19.  However, I had to send them (for the 3rd time) the logs showing that the traffic is getting passed to it.  Here is part of it:

1   07/08/2015 22:53:13.560   X1*(i)   --   192.168.4.216         192.168.1.19   IP   ICMP   --   CONSUMED   74[74]
2   07/08/2015 22:53:13.560   X1*(hc)   X0   192.168.4.216      192.168.1.19   IP   ICMP   --   FORWARDED   74[74]
3   07/08/2015 22:53:13.560   --           X0*   192.168.4.216      192.168.1.19   IP   ICMP   --   FORWARDED   74[74]
4   07/08/2015 22:53:18.208   X1*(i)   --   192.168.4.216      192.168.1.19   IP   ICMP   --   CONSUMED   74[74]
5   07/08/2015 22:53:18.208   X1*(hc)   X0   192.168.4.216      192.168.1.19   IP   ICMP   --   FORWARDED   74[74]
6   07/08/2015 22:53:18.208   --           X0*   192.168.4.216      192.168.1.19   IP   ICMP   --   FORWARDED   74[74]

4
What I did was putty into .19, did a traceroute to 192.168.4.216 (that's the ip of the offsite computer) and it times out. I should mention that I've been working with Sonicwall support and Mitel support to handle all the network tests.  What is just not making any sense is that .20 responds but .19 doesn't.

5
Traceroutes to .19 timeout (both ways).  However, if I do a traceroute to .20, .19 actually responds as a hop before hitting .20.

The phone system is installed as a virtual machine on an ESXi host if that makes a difference.

6
Looking for any ideas/thoughts on this as I'm completely fried.

We have a 3300 (on-site) with the following IP assignments:
192.168.1.19 (Applications Suite)
192.168.1.20 (MCD)
172.20.0.0 (All of our IP phones)
192.168.4.0 (Offsite network)

We are setting up an offsite office that will be using softphones over a site-to-site VPN tunnel using Sonicwall routers.

The issue we are experiencing is that the tunnel connects, we can ping everything except for the Applications Suite.  We can ping every phone as well.  I've been working with our vendor and Mitel support and they are both 100% stumped.  The MCD responds without issue.  The 192.168.4.0 network is in the list of Local Networks on the server, packet capture from both Sonicwall's show the packets coming in and properly being forwarded to .19.  However, .19 never responds.  We cannot even access via the web, it just times out. 

Has anyone had any experience with this type of issue at all?  Any help would be greatly appreciated.

Pages: [1]