Important notes about High Availability login profiles
You can use the High Availability login profile tables in this
section to configure the upper and lower client re-login values for your
subcluster. You configure the upper and lower client login values by selecting
Cisco Unified CM IM and Presence
Administration > System > Service
Parameters, and selecting
Cisco Server Recovery Manager from the
Service menu.
By configuring the upper and lower client re-login limits on your
subcluster based on the tables we provide here, you can avoid performance
issues and high CPU spikes in your deployment.
We provide a High Availability login profile for each
IM and Presence server memory size (2, 4 or 6 GB), and for each High
Availability deployment type, active/active or active/standby.
The High Availability login profile tables are calculated based on
the following inputs:
The
Users Moved Per Iteration service
parameter. This parameter determines the number of users moved per iteration
during a failover or a fallback operation. We provide a recommended value for
the
Users Moved Per Iteration service
parameter for each High Availability login profile table.
The total number of users in the subcluster for Active/Standby
deployments, or the node with highest number of users for Active/Active
deployments.
You must configure the upper and lower client re-login limit
values, and the
Users Moved Per Iteration service parameter
on both nodes in a subcluster. You must manually configure all these values on
both nodes in the subcluster.
The upper and lower client re-login limit values must be the same
on each node in the subcluster.
If you
rebalance your users, you must reconfigure the upper and
lower client re-login limit values based on the High Availability login profile
tables.
Use the High Availability login profile tables to retrieve
the following values:
Client Re-Login Lower
Limit service parameter value
Client Re-Login Upper
Limit
service parameter value.
Users Moved Per
Iteration service parameter value.
Procedure
Step 1
Select a profile table based on your memory size, and your High
Availability deployment type.
Step 2
In the profile table, select the number of users in your
deployment (round up to the nearest value). If you have an active/standby
deployment, use the node with the highest number of users.
Step 3
Based on the Number of Users value for your subcluster, retrieve
the corresponding lower and upper retry limits in the profile table.
Step 4
Configure the lower and upper retry limits on
IM and Presence by selecting
Cisco Unified CM IM and Presence
Administration > System > Service
Parameters, and selecting
Cisco Server Recovery Manager from the Service menu.
Step 5
Retrieve the corresponding
Users Moved Per Iteration service parameter value for your
High Availability login profile table.
Step 6
Configure the
Users Moved Per Iteration value on
IM and Presence by selecting
Cisco Unified CM IM and Presence
Administration > System > Service
Parameters, and selecting
Cisco Server Recovery Manager from the
Service menu.
You have 3000 users in your subcluster, with 2000 users on one node, and 1000 users on the second node. For active/standby deployments, we recommend you use the node with the highest number of users, in this case the node with 2000 users. Using 6 GB active/standby profile, you retrieve these lower and upper retry values:
Number of Users
Lower Retry Limit
Upper Retry Limit
2000
40
107
Note
The upper retry limit is the approximate time (seconds) it takes for all clients to login to their backup node after a failover occurs.
You also configure the corresponding Users Moved per Iteration service parameter value for 6 GB active/standby profile which is 50.
Example 2: 4GB Active/Active IM-Only Deployment
You have 6800 users on the first node in your subcluster in an IM-only deployment. We recommend that you round up to the nearest value, so using 4 GB active/active profile you retrieve the lower and upper retry value based on a number of users value of 7000:
Number of Users
Lower Retry Limit
Upper Retry Limit
7000
280
1447
You also configure the corresponding Users Moved per Iteration service parameter value for 4 GB active/active profile which is 25.
2 GB active/active profile
Corresponding Users Moved per Iteration service parameter value: 6
Table 1 User Login Retry Limits for Standard Deployment (2 GB Active/Active)
Number of Users
Lower Retry Limit
Upper Retry Limit
100
17
83
250 (Default)
42 (Default)
208 (Default)
500
83
417
2 GB active/standby profile
Corresponding Users Moved per Iteration service parameter value: 6
Table 2 User Login Retry Limits for Standard Deployment (2 GB Active/Standby)
Number of Users
Lower Retry Limit
Upper Retry Limit
100
17
57
250
42
142
500
83
283
750
125
425
1000
167
567
4 GB active/active profile
Corresponding Users Moved per Iteration service parameter value: 25
Table 3 User Login Retry Limits for Standard Deployment (4GB Active/Active)
Number of Users
Lower Retry Limit
Upper Retry Limit
100
4
21
500 (Default)
20 (Default)
103 (Default)
1000
40
207
1500
60
310
2000
80
413
2500
100
517
Corresponding Users Moved per Iteration service parameter value: 25
Table 4 User Login Retry Limits for IM-Only Deployment (4GB Active/Active)
Number of Users
Lower Retry Limit
Upper Retry Limit
3000
120
620
3500
140
723
4000
160
827
4500
180
930
5000
200
1033
6000
240
1240
7000
280
1447
7500
300
1550
4 GB active/standby profile
Corresponding Users Moved per Iteration service parameter value: 25
Table 5 User Login Retry Limits for Standard Deployment (4GB Active/Standby)
Number of Users
Lower Retry Limit
Upper Retry Limit
100
4
14
500
20
70
1000
40
140
1500
60
210
2000
80
280
2500
100
350
3000
120
420
3500
140
490
4000
160
560
4500
180
630
5000
200
700
Corresponding Users Moved per Iteration service parameter value: 25
Table 6 User Login Retry Limits for IM-Only Deployment (4GB Active/Standby)
Number of Users
Lower Retry Limit
Upper Retry Limit
6000
240
840
7000
280
980
8000
320
1120
9000
360
1260
10000
400
1400
11000
440
1540
12000
480
1680
13000
520
1820
14000
560
1960
15000
600
2100
6 GB active/active profile
This section includes the upper and lower user login retry limits for both standard and IM-only deployments.
User login retry limits for standard deployments
Corresponding Users Moved per Iteration service parameter value: 50
Table 7 User Login Retry Limits for Standard Deployments (6 GB Active/Active)-IM and Presence Release 9.0(1) and Later
Number of Users
Lower Retry Limit
Upper Retry Limit
100
2
10
500 (Default)
10 (Default)
52 (Default)
1000
20
103
1500
30
155
2000
40
207
2500
50
258
3000
60
310
3500
70
362
4000
80
413
4500
90
465
5000
100
517
6000
120
620
7000
140
723
7500
150
775
User retry limits for IM-only deployments
Corresponding Users Moved per Iteration service parameter value: 50
Table 8 User Login Retry Limits for IM-Only Deployments (6 GB Active/Active)-IM and Presence Release 9.0(1) and Later
Number of Users
Lower Retry Limit
Upper Retry Limit
3000
60
227
3500
70
264
4000
80
302
4500
90
340
5000
100
378
6000
120
453
7000
140
529
7500
150
569
8000
160
827
9000
180
930
10000
200
1033
11000
220
1137
12000
240
1240
12500
250
1292
6 GB active/standby profile
This section includes the upper and lower retry limits for both standard and IM-only deployments.
User login retry limits for standard deployments
Corresponding Users Moved per Iteration service parameter value: 50
Table 9 User Login Retry Limits for Standard Deployments (6 GB Active/Standby)-IM and Presence Release 9.0(1) and Later
Number of Users
Lower Retry Limit
Upper Retry Limit
100
2
7
500 (Default)
10 (Default)
33 (Default)
1000
20
65
1500
30
98
2000
40
131
2500
50
164
3000
60
196
3500
70
229
4000
80
262
4500
90
295
5000
100
327
6000
120
393
7000
140
458
8000
160
524
9000
180
589
10000
200
655
11000
220
720
12000
240
785
13000
260
851
14000
280
916
15000
300
982
User login retry limits for IM-only deployments
Corresponding Users Moved per Iteration service parameter value: 50
Table 10 User Login Retry Limits for IM-Only Deployments (6 GB Active/Standby)-IM and Presence Release 9.0(1) and Later