SCN migration to Server Edition

[George FA]

I have a customer with nine distributed IP500v2, all linked together with a variety SCN links. Customer wants to migrate to Server Edition solution, as it shown at the attached picture, and has already invested to the required licenses
After parsing this forum and related documentation, I still have two important questions:

1) What to do with existing SCN lines after migtation? Can I keep them as they are (it works!) or I need to replace them with SE-based channels and manualy re-program all?

2) What is, if any, offiucial post migration activities? I never manage to find the detaled dtsciption of that transition (SCN to Server Edition), so I would like to unredstand what actions is expected after I coonverted all IP500v2 to Expansion Server?

 

[derfloh]

If you have Server Edition Select, you can keep the intersite SCN connections. If Server Edition (non Select) only connections to primary and secondary server are supported. Officially…

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[George FA]

Thank you for the answer, derfloh!

But, if, let's say, I manage to convince my Sales Rep to sale Select licences, what should I do with already exisitng SCN mess? There a hell a lot of strange SCN connections bettween IP500v2, not sure even used, but it works somehow and I would't like to touch it. Can I keep them untouch or should I delete them all?

 

[KottV]

Does this scheme makes a sense ever? I think that only one SCN plan can exist.

PS It could be a MESH just for a case if one of V500 goes offline then other units can exchange with each other.
I've read that with non-Select SE you have to have Primary (and Secondary if exist) to be online for having interconnect - a star topology.
With Select - it should work like MESH topology, ie if two of V500 both loses connect to main or primary but see each other, then they can route calls to each other.

 

[George FA]

thank you so much for your willingness to help, but here is the question I can not find an answer to: what to do with the existing SCN channels? Delete? Reprogram?

The fact is that I don’t even want to touch them, here’s an example of how it looks like at a customer’s site...

 

[snowman50]

I haven’t done any converting to server from existing SCN.

But doesn’t the server Automatically create the SCN lines between all units
Eg 99001,99002,99003 etc so as they talk to each other Via the primary server
These would be the lines you use.

I think the other lines would be not used after the units have been converted to expansion units as you have to default them and erase the config.
But go with derfloh more experienced suggestion

 

[TouchToneTommy]

I would make sure that you have your network configured such that you can see each IP 500 and the Server Edition Primary from one management computer. Make sure the SE can ping each IPO, and each IPO can ping the SE.

On migration day, log into each IPO, and delete the SCN lines. Now they become stand alone systems. Then go into the SE and add each IPO to the SE as an expansion control unit, retaining settings.

Prior to this, make sure that all line group numbers on all control units are unique, and copy/paste the 50 ARS table, as adding to the solution usually automatically modifies that table.

 

[George FA]

OK, seems we finaly coming to the mutual argeenet that in SE envirometn there should not be SCN lines there... all network nodes sould be linked by a new aoutomatically created SE lines.

Also, very important note from derfloh, to have intersite IP500v2 - IP500v2 connection I would need a Select licenses.

I am going to follow Tommy's advice to zero all SCN before migration... though I am scared to do it on customer's site, but I fortunately have some lab to test.

But here I see another trouble to overcome - I can't convers all nodes in to SE in one jump. I need to do it site by site. As I convert one node to SE I would stll have eight nodes in SCN. And before I converted them all, I need to provide coimmuniocations between the node in SCN and the node in SE enviromet... If I delet a SCN channels at one of the sites, how will that site communicate to other SCN sites?