5550 IP console problem locking up

[mrosa@beiinc.com]

We have a site that we upgraded the MCD 3300 to rel 5.  The 5550 IP console has been installed there for 3 years working fine.  The PC for the IP console has 2 NIC cards.  One NIC is on the data vlan subnet and one NIC is on the voice vlan subnet as it has been for 3 years.  The inactivity timer is set to 0 which disables it.  Since the upgrade the console has been  intermittently losing connectivity to the 3300.  You have to either power reset the console or stop and start the console software on the PC.  It can work fine for days or it can work fine for a few hours and some days it locks up every 10 minutes.  Tech support tells me that the PC with 2 NIC's is not supported.  The customer won't accept that as it worked for 3 years that way.  I have attempted packet captures but not been able to capture anything helpful yet.  Any thoughts would be appreciated.

[x-man]

might be worth a check on the option 125 settings as they can do odd  things if not set just right. What did you upgrade from? It could be dhcp lease settings and not getting a lease back properly for instance......

[acejavelin]

x-man might be on the right track here... Make sure all VLAN info is removed from the voice VLAN's DHCP options and I always set the phone VLAN DHCP server to have less than 24 hour lease times, 8 hours seems the most stable. The 5550 IP Console seems to work best with a static DHCP assignment too.

[bobcheese]

what does the maint logs say when this happens? When I have this type of issue I try to narrow it down to one of the devices (as it could be either causing the issue). So one fothe first things I try is; put the keypad on a static reservation, put the PC on a static address (or reservation) then when the issue next occurs, from the controller attempt to ping both addresses. In most cases one of them has dropped off the network so will not respond. From there you can start to dig a little deeper but you know which device has the issue.

[mrosa@beiinc.com]

Thanks for the suggestions.  The logs are full of loss of communication errors from x700 console.  The PC that runs the console has 2 NIC cards.  One is on the voice vlan and one is on the data vlan which was how we originally configured it.  It worked that way for 3 years.  Since the upgrade from rel 4 to rel 5 (11.0.0.102) the console has been acting up. 
1984
  Info
  2012/Dec/26
  17:10:36
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in NIGHT 1 Service.
   Reason: 11  Now Out of Service: Console 700.
 
  1979
  Info
  2012/Dec/26
  13:07:47
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in DAY Service.
   Reason: 1   Dialed by device 700.
 
  1978
  Warning
  2012/Dec/26
  13:07:43
  Call Control - Maintenance
  IP Device  192 (Ext:700)  at location 01 3 02 067 01 
The set has been returned to service.

 
  1977
  Info
  2012/Dec/26
  13:07:43
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in NIGHT 1 Service.
   Reason: 9   Now in service: Console 700.
 
  1976
  Warning
  2012/Dec/26
  13:07:43
  Call Control - Maintenance
  IP Device  192 (Ext:700)  at location 01 3 02 067 01 
The set has been returned to service.

 
  1975
  Warning
  2012/Dec/26
  13:03:19
  Call Control - Maintenance
  IP Device  192 (Ext:700)  at location 01 3 02 067 01 
The set is out of service due to loss of communication.

 
  1974
  Info
  2012/Dec/26
  13:03:19
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in NIGHT 1 Service.
   Reason: 11  Now Out of Service: Console 700.
 
  1973
  Info
  2012/Dec/26
  12:57:15
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in DAY Service.
   Reason: 1   Dialed by device 700.
 
  1972
  Warning
  2012/Dec/26
  12:56:53
  Call Control - Maintenance
  IP Device  192 (Ext:700)  at location 01 3 02 067 01 
The set has been returned to service.

 
  1971
  Info
  2012/Dec/26
  12:56:53
  Call Control - Maintenance
  SYSTEM SERVICE: Dept 0 now in NIGHT 1 Service.
   Reason: 9   Now in service: Console 700.
 

[x-man]

as bobcheese suggests you will have to see what is happening by pinging the network and the 3300 from the PC to see whether its the console or the 3300 that has dissapeared and then you can investigate further, its in all probability a network card and just a coincidence....

[Mattmayn]

I'm pretty sure that the timer you have at 0 should be at 1440 to disable it.

[nwike]

I found your forum post by googling 5550 IP console problems. 

We are currently experiencing the same issue.  Our console has worked fine for over 8 years.  Now it is dropping connection intermittently and won't reconnect until I reboot the power to the console and reopen the Mitel program.   I was wondering if you ever found a solution.  Our tech is stumped as well.

Any assistance would be greatly appreciated.