atcomsystems.ca/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems 7200 MCP loses comm w/MGI...IP phones fail

This is a little involved, so sorry for in advance for the rambling.

Had a 7200 MCP running 4.14k for over a year with no problems. (6) 5121 phones running remotely via port forwarding in the customers firewall.

Upgraded to 4.42a a few weeks ago. Upgraded the MGI16 to v1.25 and upgraded the svmi20 to 5.3.3.5. All upgrades went smoothly...no problems whatsoever...initially.

About a week after the upgrade, the customer called and said that all their remote IP phones were showing 'connecting'. I tried to authenticate an IP phone from my office, and the same issue.

When I logged into their VPN and tried doing a ping -t to the MCP and the MGI...most pings were good...but would periodically get a no response. Additionally...when I looked at the alarm history log from the 7200 I would see the following:

Entry Number ID Date Time Alarm Name Position
0 MNF30 12/25/2009 20:49:05 SPNet Link Error 01
1 MNF30 12/26/2009 12:05:24 SPNet Link Error 01
2 MNF30 12/26/2009 12:14:34 SPNet Link Error 01
3 MNF30 12/26/2009 12:15:43 SPNet Link Error 01
4 MNF30 12/26/2009 12:16:51 SPNet Link Error 01
5 MNF30 12/26/2009 12:17:59 SPNet Link Error 01
6 MNF30 12/26/2009 12:34:09 SPNet Link Error 01
7 MNF30 12/26/2009 12:36:26 SPNet Link Error 01
8 MNF30 12/26/2009 12:40:00 SPNet Link Error 01
9 MJE05 12/26/2009 12:56:56 MGI NTWK Rec C1-S04
10 MJE04 12/26/2009 12:57:29 MGI NTWK Error C1-S04
11 MJE05 12/26/2009 12:57:57 MGI NTWK Rec C1-S04
12 MJE04 12/26/2009 12:58:42 MGI NTWK Error C1-S04
13 MJE05 12/26/2009 12:59:04 MGI NTWK Rec C1-S04
14 MJE04 12/26/2009 12:59:48 MGI NTWK Error C1-S04
15 MNF30 12/26/2009 13:00:14 SPNet Link Error 01
16 MJE05 12/26/2009 13:00:17 MGI NTWK Rec C1-S04
17 MJE04 12/26/2009 13:01:00 MGI NTWK Error C1-S04
18 MJE05 12/26/2009 13:01:22 MGI NTWK Rec C1-S04
19 MJE04 12/26/2009 13:02:04 MGI NTWK Error C1-S04
20 MJE05 12/26/2009 13:02:38 MGI NTWK Rec C1-S04


If I try to reset the MGI card, it then shows the recovery message (MJE05), but the IP phones still do not recover. The same intermittent ping errors continue. The only way to correct the issue is to reset the entire system. Then the issue resolves. I've had everything work fine for a week, then within a day the issue reappears...then it will go 3 or 4 days without an issue...then it reappears again. FYI, they do have one IP phone in-house on their network...and when the failure occurs, it does affect the in-house IP phone as well.

Samsung says a corrupt database, which it may be. They have suggested defaulting the database and programming from scratch suggesting a problem during the upgrade from 4.14k to 4.42a. I typically don't buy into the 'corrupt database' diagnosis as I've never had one with Samsung, but am wondering myself.

I'm also wondering about some kind of garbage on the customers network causing the communication issue with the MCP / MGI. I've thought about removing the system from the customers network, installing a linksys/netgear firewall off the back of their cable modem and utilizing a different available static public IP address. I was thinking that would be a way to isolate their network.

I'm not inclined to believe it's a hardware failure on the 7200 since it ran fine for over a year. I know their IT guys have been working on their network quite a bit lately though. So...looking for some thoughts from you other experienced Samsung guru's. Is some type of garbage on the customers network a possibility? Is that even worth trying?...or should I just bite the bullet and go for the complete reprogram? Any other thoughts or ideas would be appreciated. FYI...when the IP phones are down...I do have trouble connecting utilizing IT tool. I guess one thing that is making me think network is that there are ping failures to both the MCP and MGI which have separate IP addresses. This has now become one of those issues that I've looked at so long I'm not quite sure which direction to go.

Thanks in advance.

There is an easy way to check for problems with the LAN. Unplug the MCP and MGI cards and try pinging their addresses. If you get a response, you know there is something else on the network with the same IP address.

Also bump the MGI to 1.26 So its the latest release.

Remember that with the 4.42 you have to license the spnet because of some changes made at Samsung (may not be implemented yet). I don't know if that is the cause of the problem currently. But it kinda sticks out in my head.

Thanks for the responses. I didn't mention Mark that I had done that test with the IP addresses.

I didn't notice the 1.26 on the MGI. Good catch! The switch does have an SPNet license.

Thanks again for your help.

I think its going to be a network issue, either that or you have failing LAN ports on the MCP/MGI (though the chances of both failing at the same time are very low)
The fact that you have issues with local IP phones, and IT Tool, and pinging from their firewall suggests a network issue.
As Mark said try unplugging and pinging then.
Also try different switch ports (I have had switches with a couple of faulty ports cause me grief, even had a faulty switch in a stack take down half the network before)

Thought I would update this in case anyone else runs into the same issue. After attempting to roll back to 4.30i, manually reprogramming the entire system, pulling the customers switch off their data network the problem persisted.

Samsung replaced the MCP with an MP20 and the problem disappeared. Seems that there are certain cases where an MCP doesn't like the upgrade to 4.42a. Samsung acknowledged that they have seen it in rare cases.

Great news!

I just upgraded an MCP to v4.42a last night and ran into a bunch of issues with SPNet.

Right,

I ran into the same problem the topicstarter mentioned.

7200 ran fine for almost a year now on 4.30D
expansion cabinet whit LCP
but since a couple of days i do get the same error MGI NTWK REC. then the MGI card does a reset. Strange thing is the i get another error that does a restart and its preformed by the WATCHDOG this seems tho happen when the MGI gives the error.

I talked tho the techguys at samsung the did say that it could be a corrupted database and should default the system and reprogram from scrath.

But after founding this topic it seems that either we bot are having a netwerk issue or that there is something acting up in the new software version's samsung is not aware off.

Greeting Albion from holland

Don’t waste your time I have had a few of these. Upgrade from an MCP to an MP20 and all your problems will go away. I am also guessing that your MCP is using the black SD card? I havent had any troubles with the old smart media versions upgraded to 4.42. Good Luck