Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cluster Existing Systems

Status
Not open for further replies.

12345kevin

Vendor
Feb 15, 2006
125
GB
We currently have 2 3300 enterprise systems which stand alone and are completely seperate. The next phase of the project is to cluster the 2 systems with IP networking etc. Things like Class Of Service are currently being brought into line. However what is the best way of going forward and what will happen with telephone directories etc. As far as I can remember one system is likely to be completely overwritten.

Is there a procedure for doing this or should we export all forms and import when complete ?
 
After you have built your cluster in the 3300s and set your CIEDs in ARS you will need to tell the system/s what forms you want to share under SDS.

To start SDS on an existing cluster or to add a new 3300 to a synchronized cluster:

1-adjust date and time
2-prepare the ARS for the CEID digits
3-SDS-Start Sharing
4-Name the Network Elements
5-Start sharing again (at the cluster level)
6-Sync user and sevice hosting (at this point just sync with data migration not anything else might work)
7-Sync Telephone Directory (if you had previous Telephone directory assignment)


Technology is going to kill us all!
 
Were the systems designed with clustering in mind? No duplicate extensions? (especially VM Ports?)

Also, don't get confused between clustering and Sharing. They are completely separate and for the most part, independant.

You haven't mentioned SW levels, you need to do so.

Your one concern with respect to sharing and things being overwritten can be ignored. The systems can be merged without data loss.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Thanks for the replies.

The software will be latest release prior to the "clustering". The 2 systems were installed completely independently of each other, hence we are aligning as many forms as possible before starting. Extensions numbers are fortunately all different.

We've done plenty of new installs as clusters and adding new systems to clusters, so no problem with that etc, just a few concerns over "merging" which from the above comments should be straightforward
 
As long as there are no DN conflicts, you can create a cluster.
SDS can be actually used for remote directory only. This is the critical part for an intra-cluser routing.

I was adding and removing systems from a cluster without any impact to other members of the cluster.
 
Get you IP trunks working first. Then I think MOL has a guide to setting up SDS that you should review.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top