MitaiSrv Log error Mitel MCD 6.0

[august]

Several times a day, I got these logs.  As soon as I got them, I lost contact with many IP Phones.
As someone already see this?


Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.103 (08-00-0F-3B-E9-92)), network driver cluster pool free: 6066 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.63 (08-00-0F-5A-A0-F2)), network driver cluster pool free: 6066 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.160 (08-00-0F-80-12-80)), network driver cluster pool free: 6067 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.154 (08-00-0F-3D-0D-D5)), network driver cluster pool free: 6066 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Error   2017/Jan/30   23:10:24   MitaiSrv   ProcessNewConnection: Could not accept client connections   Main   vxw_msssu.c;308
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 100 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 90 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 80 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.68 (08-00-0F-7D-06-DD)), network driver cluster pool free: 6067 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 70 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:24   Heartbeat Server   ICP has lost contact with (10.10.150.104 (08-00-0F-39-D9-3B)), network driver cluster pool free: 6067 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 60 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:24   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 50 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:23   Heartbeat Server   ICP has lost contact with (10.10.150.167 (08-00-0F-45-20-6D)), network driver cluster pool free: 6067 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:23   Heartbeat Server   ICP has lost contact with (10.10.150.56 (08-00-0F-39-C5-75)), network driver cluster pool free: 6067 and low water mark: 5778   Main   HeartbeatRecvTimeoutHandler.cpp;273
Warning   2017/Jan/30   23:10:23   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 40 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:23   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 30 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:23   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 20 loops   Main   vxw_msssu.c;298
Warning   2017/Jan/30   23:10:23   MitaiSrv   accept() returns EWOULDBLOCK, retrying after 10 loops   Main   vxw_msssu.c;298

[acejavelin]

Do you have any other servers that talk to the Mitel, like UCA/MiCollab Client? MiTai can be phones or other application servers, something is giving it bad info. I would open a low priority ticket online with support unless you can clearly identify a server that is in trouble or maybe hasn't been upgraded to the correct version to talk to the MCD.

[august]

The only other server is prairiefyre....

[mszodiac]

The logs that show the IP addresses 10.10.X.X (08-00-0F..) are the IP phones.  Is there a common point on these phones like a Cisco switch?

You can go through the Device Connectivity form to help you see a common point.  It will be the "Last Known CDP L2 IP Address".

The last time I had those logs, we were able to pinpoint it to a faulty Gigastack module on the Cisco switch.

[august]

I will look at this.

Thanks.