Topic: SPnet with v4.46d - upgrade feasible at this time?

[Noisycow]

We have several sites, but one in particular that has the MCP (7200) networked on older 4.22/4.30 software and the customer complains about slow dialing, misdialing and such.  The earlier MCP processor is of course a dog.

Can we upgrade site #1 7200 MCP to an MCP 20; the MGI card to an OAS card, the software to 4.46d, add the SPNet licensing.  We were smart enough to get the SPnet licensing back two months ago, but of course it is for the MCP that is there :(.

It is hard to go to a customer and ask them to pay for all of this 1.5 yrs after purchasing a system, when it is being done to fix inherent system problems.  That is a bridge we have to cross since the manufacturer sees no issues with the MCP.

If we take the steps, are we going to fall on our face like we did when we tried to upgrade the MCP 7200 to v4.46d a couple of months ago and the systems would talk because of some IP address bug?

[Noisycow]

It is our opinion that the MCP is fine for a smaller, single-site.   For a larger 7200 with expansion, SPnet, etc, we are upgrading them all to MP20s.   Selling off the MCPs with licensing on Ebay.

Note to self:  The MP20 cards do NOT come with the memory SD card - you must order it separately.

[Noisycow]

Finally - the solution my friends. We went out to the about site we attempted back in June. Upgraded the MCP to an MP20, upgraded the PRI to 4.28, the LCP to 4.18; etc. Then it did it to us again.

Calling the other nodes got 'no user response.'

Tech support had us initialize the system and get up just the basics for a test. Then again, 'no user response.' Port 6100 was responding via telnet on both sides.

Finally my tech and the Samsung tech had a revelation. MMC XXX. Set it to match the private IP range on the other side. For instance, the MP10a on node site 001 was 192.168.1.44. So we entered 192.169.1.255.

Problem solved. Damn.

[Marc Haycook]

I don't know if I would say the problem is solved, but it looks like you got it working. The IP Address 192.169.1.255 is not an actual address - rather it's the broadcast for the 192.169.1.0 network.

I mention this because if Samsung does figure out the problem - your SPNet might stop working again on a future upgrade.

Keep in mind that broadcasts will travel to every single client on a network - at least, until a router is encountered. A router is the only device that can separate a broadcast domain.

[Noisycow]

Samsung tech support specifically had us set it up as a .255 broadcast, not the MP10a address on node 1 (the second node).