ESS Cluster Separation? 1

[Ronster]

How easy is it to remove an ESS cluster from a s8700 environment and rebuild it as a standalone PBX?

I have a main site with 2 s8720 servers and 5 PN's, a data centre that has 2 ESS 2 PN's and an office with 1 ESS 1 PN.

I want to segregate the main site making it a standalone site. That seems easy enough as it has the main servers and also because all the routing will be trashed and the site will be rebuilt and programmed from the ground up.

What I am not sure of is how easy it will be to maintain services at the remote office/data centre.
Assuming that I get the licencing sorted out, from a technical point of view, can I reprogram the duplex ESS's to be full blown s8720 servers and continue to provide the same local trunks, stations, VDN's etc?



Ronster

Science is the rehab of the masses.

 

[Mitch672]

How easy? Not easy at all. First of all, you need to get a new license from AVAYA, that will cost you a small fortune. 2nd of all, you need to reprogram the new switch from scratch, since it will not have any translations, now that you made it a standalone switch.

Yes, it's possible, however, in reality, the licensing is so expensive, you will probably never do it. When I say expensive, think $200 or more per RTU, if you have say 100 RTU, thats $20,000. Networking (DCS & QSig) RTU is even more, BTW.

Also, you will now only be able to license it as a CM4 or CM5 switch. and, the CM4 option is going away very soon (august)

If you have ProVision, or access to it, you could push out translations fairly quickly, assuming youhave them done in advance, ready to go.

mitch


AVAYA Certified Specialist

 

[Ronster]

Thanks Mitch.

I understand where you are coming from with the licencing costs (you do know AVAYA is an acronym?), but this might not be prohibitive since the main site is being sold (whole kit and kiboodle) to another company.

The current ESS will therefore either have to become standalone or be sold as parts and a new phone system deployed as part of the new parent company for that site.

I am comfortable with the re-programming and can quickly rebuild using exports/imports. There are not too many ports at the ESS site.

As for the removal of the ESS, is it as simple as:
remove survivable-processor 2
remove cabinet 6
done?

Ronster

"Gonny no' dae that?

 

[Mitch672]

not quite Ronster... you have to "X" out all of the stations using anything in that gateway, and remove all members from any trunk groups in that gateway, remove all signalling groups, remove ds1 forms, etc. once everything is removed, you can 'remove cabinet x', after you remove the ipsi's "remove ipsi 02A01" for example.

you can't remove the cabinet until everything in it is unused. You might also have to do a "change sys feat" and disable TTI, so the ports no longer show up as "p"'s, and then do a "change circuit 02" and remove the now freed up TN circuit packs. once you have them all removed, remove the ipsi's, and remove the cabinet. then you can turn TTI back on.

no, its never easy...


mitch


AVAYA Certified Specialist

 

[Tolson]

one other minor issue is that you cannot sell the software for the PBX, only Avaya or it's business partners can do that. The new company woul have to outright purchase new software.

 

[Ronster]

Thanks Guys,

Good tip on the TTI thing, I'll keep that in mind. As for removing all the stations etc. I still think that importing a list and using the remove option will make that fairly straight-forward.

The tricky bit will be re-addressing the IPSIs, CLANs, MEDPROs etc as we will need to give them a new IP's.

What I am aiming at is having a clean (almost pre-install) PBX. The legal guys are talking to Avaya about the licencing.

I don't have to hand over the switch until 1 December. However, it has to be operational in it's current state until 27 October. So just in the planning stage.
November is going to be fun!


Ronster

"Gonny no' dae that?