cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
404
Views
4
Helpful
3
Replies

Add Subsequent Node and BusinessHours

Gentlemen,

Are there any arguments against adding subsequent node to CM 6.x cluster during Business Hours ?

I've been looking through Admin Guide, Installing Guide.

Nowhere exists any warning about recommendation to move such an operation to non-business time interval.

Thank you.

1 Accepted Solution

Accepted Solutions

I think it's not hours for the whole process but it needs much system ressources like processor.

With RTMT you can watch your DB replication Status under "performance-> "yourfirstserver" -> Number of Replicates Created and State of Replication->Replicate_State"

This displays the state of replication: Thus 0 = Initializing (Will be 0 if server is not defined OR if server is defined but realize template is not done); 1 = Replicates created but their count isn't right; 2 = Replication is good; 3 = Replication is bad in the cluster; 4 = Replication Setup didn't succeed

After adding a node, your count should say "2" on every server.

HTH

Chris

View solution in original post

3 Replies 3

Jaime Valencia
Cisco Employee
Cisco Employee

it's not recommended because at that time a copy of almost all the DB tables needs to be pushed to the server, SDL links need to be created, RIS info, etc

depending on the size of the DB it can take quite some time to push all the info and that causes some high CPU

also it's best practice to restart the cluster after the addition of a new server to sync the SDL layer, so afterhours is always the best choice

HTH

java

if this helps, please rate

HTH

java

if this helps, please rate

Jaime,

Can you please approx. estimate total time (in hours) of the whole process of adding subsequent node to PUB with ~500 phones.

Please, explain what do you mean in saying "restart the cluster" ?

What actions and where should perform to complete this ?

Thank you.

I think it's not hours for the whole process but it needs much system ressources like processor.

With RTMT you can watch your DB replication Status under "performance-> "yourfirstserver" -> Number of Replicates Created and State of Replication->Replicate_State"

This displays the state of replication: Thus 0 = Initializing (Will be 0 if server is not defined OR if server is defined but realize template is not done); 1 = Replicates created but their count isn't right; 2 = Replication is good; 3 = Replication is bad in the cluster; 4 = Replication Setup didn't succeed

After adding a node, your count should say "2" on every server.

HTH

Chris