Cisco Unified MeetingPlace, Release 7.0 -- System Capacity Quick Reference Tables

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m
(Capacity: -- edit as Footnote numbering was incorrect..)
 
(22 intermediate revisions not shown)
Line 2: Line 2:
'''Main page:'''  [[Cisco Unified MeetingPlace, Release 7.0]]
'''Main page:'''  [[Cisco Unified MeetingPlace, Release 7.0]]
-
'''Up one level:'''  [[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]]
+
'''Navigation:'''  [[Cisco Unified MeetingPlace, Release 7.0 -- Planning Your Deployment|Planning Your Deployment]] > [[Cisco Unified MeetingPlace, Release 7.0 -- Planning the Capacity of your Cisco Unified MeetingPlace System|Planning the Capacity of your Cisco Unified MeetingPlace System]]
-
This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 7.0 and 8.0.  
+
This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 7.0.  
-
For more detailed information, see the following:
+
For more detailed information, see [[Cisco Unified MeetingPlace, Release 7.0 -- System Capacity#System Capacity|System Capacity]].
-
 
+
-
* Release 7.0: [[Cisco Unified MeetingPlace, Release 7.0 -- System Capacity#System Capacity|System Capacity]]
+
-
 
+
-
* Release 8.0: [[Cisco Unified MeetingPlace Release 8.0 -- Planning the Capacity of your Cisco Unified MeetingPlace System#Planning the Capacity of your Cisco Unified MeetingPlace System|Planning the Capacity of your Cisco Unified MeetingPlace System]]
+
Line 22: Line 18:
This configuration assumes the following:
This configuration assumes the following:
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC1 or equivalent.
+
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
* Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
* Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
* Six Audio blades
* Six Audio blades
Line 29: Line 25:
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
*Does not support Cisco WebEx-scheduled meetings
*Does not support Cisco WebEx-scheduled meetings
-
 
====Capacity ====
====Capacity ====
Line 109: Line 104:
|
|
-
300
+
500
|
|
-
Largest possible audio meeting (or 299 when recorded)<sup>2</sup>
+
Largest possible audio meeting <sup>2</sup>
|-
|-
|
|
-
300
+
500
|
|
Line 126: Line 121:
|
|
-
300
+
500
|
|
Line 134: Line 129:
|
|
-
20
+
5
|
|
Simultaneous Conference Manager sessions  
Simultaneous Conference Manager sessions  
 +
 +
|-
 +
|
 +
 +
200
 +
 +
|
 +
 +
Largest possible number of instances of the recurrence meeting  <sup>2</sup>
 +
 +
|-
 +
|
 +
 +
500
 +
 +
|
 +
 +
Largest possible number of invitees on single meeting <sup>4</sup>
|-
|-
Line 154: Line 167:
'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.
'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.
-
'''Footnote 2:''' We recommend that you schedule larger meetings.
+
'''Footnote 2:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
-
'''Footnote 3:''' The Cisco MCS 7845-I3 Web Server supports a maximum of 600 web ports per server. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 300 ports due to the rate at which a single Audio blade can accept traffic.
+
'''Footnote 3:''' The Cisco MCS 7845-I3 Web Server supports a maximum of 600 web ports per server. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 500 ports due to the rate at which a single Audio blade can accept traffic.
 +
'''Footnote 4:''' Largest possible number of invitees on MPWeb is 450.
Line 225: Line 239:
====Recommended Practices====
====Recommended Practices====
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
* Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
Line 239: Line 253:
This configuration assumes the following:
This configuration assumes the following:
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC1 or equivalent.
+
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
-
* One or two Windows web servers  
+
* Two Windows web servers  
* Six Audio blades
* Six Audio blades
* Six Video blades
* Six Video blades
Line 304: Line 318:
|
|
-
300
+
500
|
|
-
Largest possible audio meeting (or 299 when recorded)<sup>2</sup>
+
Largest possible audio meeting <sup>2</sup>
|-
|-
Line 321: Line 335:
|
|
-
20
+
200
 +
 
 +
|
 +
 
 +
Largest possible number of instances of the recurrence meeting  <sup>2</sup>
 +
 
 +
|-
 +
|
 +
 
 +
500
 +
 
 +
|
 +
 
 +
Largest possible number of invitees on single meeting <sup>4</sup>
 +
 
 +
|-
 +
|
 +
 
 +
5
|
|
Line 331: Line 363:
'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.
'''Footnote 1:''' When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.
-
'''Footnote 2:''' We recommend that you schedule larger meetings.
+
'''Footnote 2:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
 +
'''Footnote 3:''' Largest possible number of invitees on MPWeb is 450.
====Sizes====
====Sizes====
Line 399: Line 432:
====Recommended Practices====
====Recommended Practices====
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
* Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
Line 484: Line 517:
|
|
-
300
+
500
|
|
-
Largest possible audio meeting (or 299 when recorded)<sup>1</sup>
+
Largest possible audio meeting <sup>1</sup>
|-
|-
|
|
-
300
+
500
|
|
-
Largest possible web meeting when not using SSL or recording<sup>2</sup>
+
Largest possible web meeting when not using SSL or recording
|-
|-
|
|
-
300
+
500
|
|
-
Largest possible web meeting when using SSL or recording<sup>2</sup>
+
Largest possible web meeting when using SSL or recording
|-
|-
|
|
-
20
+
5
|
|
Line 526: Line 559:
'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
-
 
-
'''Footnote 2:''' The Cisco MCS-7845-I2 Web Server supports a maximum of 500 web ports per server when there is no SSL/recording and 350 web ports per server when there is recording enabled. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 300 ports due to the rate at which a single Audio blade can accept traffic.
 
Line 673: Line 704:
|
|
-
300
+
500
|
|
-
Largest possible audio meeting (or 299 when recorded)<sup>1</sup>
+
Largest possible audio meeting <sup>1</sup>
|-
|-
Line 691: Line 722:
-
'''Footnote 1:''' We recommend that you schedule larger meetings.
+
'''Footnote 1:''' We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
Line 768: Line 799:
==Release 7.0.2 (MR1) Using RSNA==
==Release 7.0.2 (MR1) Using RSNA==
 +
====Configuration Details====
====Configuration Details====
Line 778: Line 810:
*Two nodes using the Hardware Media Server  
*Two nodes using the Hardware Media Server  
*Supports audio/video-only reservationless meetings
*Supports audio/video-only reservationless meetings
-
*There is no web conferencing and no scheduling interface
+
*Supports Outlook Scheduling interface
 +
*There is no web conferencing with RSNA deployments
Line 820: Line 853:
|
|
-
300
+
500
|
|
Line 898: Line 931:
-
 
+
[[CategoryPlanning Cisco Unified MeetingPlace, Release 7.0]]
-
==Release 8.0 Using an Express Media Server==
+
-
 
+
-
====Configuration Details====
+
-
 
+
-
This configuration assumes the following:
+
-
 
+
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
+
-
* Two Web servers
+
-
* Three Cisco WebEx Node for MCS
+
-
*Single node configuration using the Express Media Server and Cisco WebEx Node for MCS web conferencing
+
-
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
+
-
*Does not support Cisco WebEx-scheduled meetings
+
-
 
+
-
 
+
-
====Capacity ====
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Number
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
1300
+
-
|
+
-
 
+
-
Audio ports using G.711
+
-
|-
+
-
|
+
-
 
+
-
260
+
-
|
+
-
 
+
-
Audio ports using G.729 or G.722
+
-
|-
+
-
|
+
-
650
+
-
|
+
-
 
+
-
Combined audio/video ports using G.711 and 384Kpbs
+
-
|-
+
-
|
+
-
108
+
-
|
+
-
 
+
-
Combined audio/video ports using G.722 and 2Mbps
+
-
|-
+
-
|
+
-
1000
+
-
   
+
-
|
+
-
 
+
-
Web sessions per Application Server
+
-
|-
+
-
|
+
-
 
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Maximum number of concurrent audio and web meetings per Application Server
+
-
|-
+
-
|
+
-
50
+
-
 
+
-
|
+
-
 
+
-
Simultaneous meetings that can be recorded
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
 
+
-
|
+
-
 
+
-
Largest possible audio meeting (or 999 when recorded)<sup>1</sup>
+
-
|-
+
-
|
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Largest possible web meeting using Meeting Center meetings<sup>1</sup>
+
-
|-
+
-
|
+
-
 
+
-
1
+
-
 
+
-
|
+
-
 
+
-
Database replication connection per Windows cluster (internal and external).
+
-
 
+
-
Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.
+
-
|}
+
-
 
+
-
'''Footnote 1:''' For larger meetings, we recommend that you use Event Center.
+
-
 
+
-
 
+
-
====Sizes====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Size
+
-
!Component
+
-
|-
+
-
|
+
-
 
+
-
250,000
+
-
|
+
-
 
+
-
User profiles in the database
+
-
|-
+
-
|
+
-
 
+
-
700,000
+
-
|
+
-
 
+
-
Meetings in the database
+
-
 
+
-
|}
+
-
 
+
-
 
+
-
 
+
-
====Call Rate====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
180 seconds
+
-
|
+
-
 
+
-
Time to get all ports into meetings (includes the time to disconnect from previous meetings)
+
-
|-
+
-
|
+
-
 
+
-
20 seconds
+
-
|
+
-
 
+
-
Time to get the meetings started
+
-
|-
+
-
|
+
-
 
+
-
15 CPS
+
-
+
-
|
+
-
 
+
-
Maximum call rate for inbound calls
+
-
|}
+
-
 
+
-
 
+
-
====Redundancy====
+
-
 
+
-
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.
+
-
 
+
-
 
+
-
====Recommended Practices====
+
-
 
+
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
 
+
-
 
+
-
==Release 8.0 Using a Hardware Media Server==
+
-
 
+
-
====Configuration Details====
+
-
 
+
-
This configuration assumes the following:
+
-
 
+
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
+
-
* Two Web servers
+
-
* Eight Audio blades
+
-
* Eight Video blades
+
-
* Three Cisco WebEx Node for MCS
+
-
*Single node configuration using the Hardware Media Server and Cisco WebEx Node for MCS web conferencing
+
-
*Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
+
-
*Does not support Cisco WebEx-scheduled meetings
+
-
 
+
-
 
+
-
====Capacity ====
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Number
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
2000
+
-
|
+
-
 
+
-
Audio ports using G.711 or G.729 (without LEC)
+
-
|-
+
-
|
+
-
 
+
-
1328
+
-
|
+
-
 
+
-
Audio ports using G.729 (with LEC), G.722, or iLBC
+
-
|-
+
-
|
+
-
 
+
-
300
+
-
|
+
-
 
+
-
Video ports using standard rate video
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
|
+
-
 
+
-
Web sessions per Application Server
+
-
|-
+
-
|
+
-
 
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Number of concurrent audio and web meetings per Application Server
+
-
|-
+
-
|
+
-
50
+
-
 
+
-
|
+
-
 
+
-
Simultaneous meetings that can be recorded
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
 
+
-
|
+
-
 
+
-
Largest possible audio meeting (or 999 when recorded<sup>1</sup>
+
-
|-
+
-
|
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Largest possible web meeting using Meeting Center meetings<sup>1</sup>
+
-
|-
+
-
|
+
-
 
+
-
1
+
-
 
+
-
|
+
-
 
+
-
Database replication connection per Windows cluster (internal and external).
+
-
 
+
-
Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.
+
-
 
+
-
 
+
-
|}
+
-
 
+
-
'''Footnote 1:''' For larger meetings, we recommend that you use Event Center.
+
-
 
+
-
 
+
-
 
+
-
====Sizes====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Size
+
-
!Component
+
-
|-
+
-
|
+
-
 
+
-
250,000
+
-
|
+
-
 
+
-
User profiles in the database
+
-
|-
+
-
|
+
-
 
+
-
700,000
+
-
|
+
-
 
+
-
Meetings in the database
+
-
 
+
-
|}
+
-
 
+
-
 
+
-
 
+
-
====Call Rate====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
180 seconds
+
-
|
+
-
 
+
-
Time to get all ports into meetings (includes the time to disconnect from previous meetings)
+
-
|-
+
-
|
+
-
 
+
-
20 seconds
+
-
|
+
-
 
+
-
Time to get the meetings started
+
-
|-
+
-
|
+
-
 
+
-
20 CPS
+
-
+
-
|
+
-
 
+
-
Maximum call rate for inbound calls
+
-
|}
+
-
 
+
-
 
+
-
====Redundancy====
+
-
 
+
-
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.
+
-
 
+
-
 
+
-
====Recommended Practices====
+
-
 
+
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
 
+
-
 
+
-
==Release 8.0 Using an Express Media Server from Cisco WebEx==
+
-
 
+
-
====Configuration Details====
+
-
 
+
-
This configuration assumes the following:
+
-
 
+
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
+
-
* Three Cisco WebEx Node for MCS
+
-
*Single node configuration using the Express Media Server and Cisco WebEx web conferencing
+
-
*Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
+
-
 
+
-
 
+
-
====Capacity ====
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Number
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
1300
+
-
|
+
-
 
+
-
Audio ports using G.711
+
-
|-
+
-
|
+
-
 
+
-
650
+
-
|
+
-
 
+
-
Combined audio/video ports using G.711 and 384Kpbs
+
-
|-
+
-
|
+
-
 
+
-
108
+
-
|
+
-
 
+
-
Combined audio/video ports using G.722 and 2Mbps
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
|
+
-
 
+
-
Web sessions per Application Server
+
-
|-
+
-
|
+
-
 
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Number of concurrent audio and web meetings per Application Server
+
-
|-
+
-
|
+
-
50
+
-
 
+
-
|
+
-
 
+
-
Simultaneous meetings that can be recorded
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
 
+
-
|
+
-
 
+
-
Largest possible audio meeting (or 999 when recorded)<sup>1</sup>
+
-
|-
+
-
|
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Largest possible web meeting using Meeting Center meetings<sup>1</sup>
+
-
|-
+
-
|
+
-
 
+
-
3500
+
-
 
+
-
|
+
-
 
+
-
Largest possible meeting using Event Center as follows:
+
-
*Up to 500 users with speaking privileges on the Cisco Unified MeetingPlace audio bridge
+
-
*Up to 3000 users with listening-only privileges on the audio broadcast
+
-
 
+
-
|}
+
-
 
+
-
'''Footnote 1:''' For larger meetings, we recommend that you use Event Center.
+
-
 
+
-
 
+
-
 
+
-
====Sizes====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Size
+
-
!Component
+
-
|-
+
-
|
+
-
 
+
-
250,000
+
-
|
+
-
 
+
-
User profiles in the database
+
-
|-
+
-
|
+
-
 
+
-
700,000
+
-
|
+
-
 
+
-
Meetings in the database
+
-
 
+
-
|}
+
-
 
+
-
 
+
-
 
+
-
====Call Rate====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
180 seconds
+
-
|
+
-
 
+
-
Time to get all ports into meetings (includes the time to disconnect from previous meetings)
+
-
|-
+
-
|
+
-
 
+
-
20 seconds
+
-
|
+
-
 
+
-
Time to get the meetings started
+
-
|-
+
-
|
+
-
 
+
-
15 CPS
+
-
+
-
|
+
-
 
+
-
Maximum call rate for inbound calls
+
-
|}
+
-
 
+
-
 
+
-
====Redundancy====
+
-
 
+
-
Warm Standby Application Server is supported. This requires duplicate hardware for the Application Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration.
+
-
 
+
-
 
+
-
====Recommended Practices====
+
-
 
+
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
 
+
-
 
+
-
==Release 8.0 Using a Hardware Media Server from Cisco WebEx==
+
-
 
+
-
 
+
-
====Configuration Details====
+
-
 
+
-
This configuration assumes the following:
+
-
 
+
-
* One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
+
-
* Eight Audio blades
+
-
* Eight Video blades
+
-
* Three Cisco WebEx Node for MCS
+
-
*Single node configuration using the Hardware Media Server and Cisco WebEx Node for MCS web conferencing
+
-
*Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
+
-
 
+
-
 
+
-
====Capacity ====
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Number
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
2000
+
-
|
+
-
 
+
-
Audio ports using G.711 or G.729 (without LEC)
+
-
|-
+
-
|
+
-
 
+
-
1328
+
-
|
+
-
 
+
-
Audio ports using G.729 (with LEC), G.722, or iLBC
+
-
|-
+
-
|
+
-
 
+
-
300
+
-
|
+
-
 
+
-
Video ports using standard rate video
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
|
+
-
 
+
-
Web sessions per Application Server
+
-
|-
+
-
|
+
-
 
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Number of concurrent audio and web meetings per Application Server
+
-
|-
+
-
|
+
-
50
+
-
 
+
-
|
+
-
 
+
-
Simultaneous meetings that can be recorded
+
-
|-
+
-
|
+
-
 
+
-
1000
+
-
 
+
-
|
+
-
 
+
-
Largest possible audio meeting (or 999 when recorded)<sup>1</sup>
+
-
|-
+
-
|
+
-
500
+
-
 
+
-
|
+
-
 
+
-
Largest possible web meeting using Meeting Center meetings<sup>1</sup>
+
-
|-
+
-
|
+
-
 
+
-
3500
+
-
 
+
-
|
+
-
 
+
-
Largest possible meeting using Event Center as follows:
+
-
*Up to 500 users with speaking privileges on the Cisco Unified MeetingPlace audio bridge
+
-
*Up to 3000 users with listening-only privileges on the audio broadcast
+
-
 
+
-
|}
+
-
 
+
-
'''Footnote 1:''' For larger meetings, we recommend that you use Event Center.
+
-
 
+
-
 
+
-
 
+
-
====Sizes====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum Size
+
-
!Component
+
-
|-
+
-
|
+
-
 
+
-
250,000
+
-
|
+
-
 
+
-
User profiles in the database
+
-
|-
+
-
|
+
-
 
+
-
700,000
+
-
|
+
-
 
+
-
Meetings in the database
+
-
 
+
-
|}
+
-
 
+
-
 
+
-
 
+
-
====Call Rate====
+
-
 
+
-
 
+
-
{| border = 1
+
-
|-
+
-
!Maximum
+
-
!Details
+
-
|-
+
-
|
+
-
 
+
-
180 seconds
+
-
|
+
-
 
+
-
Time to get all ports into meetings (includes the time to disconnect from previous meetings)
+
-
|-
+
-
|
+
-
 
+
-
20 seconds
+
-
|
+
-
 
+
-
Time to get the meetings started
+
-
|-
+
-
|
+
-
 
+
-
20 CPS
+
-
+
-
|
+
-
 
+
-
Maximum call rate for inbound calls
+
-
|}
+
-
 
+
-
 
+
-
====Redundancy====
+
-
 
+
-
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration.
+
-
 
+
-
 
+
-
====Recommended Practices====
+
-
 
+
-
* Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
+
-
 
+
-
* Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
+

Latest revision as of 23:16, 24 January 2012

Main page: Cisco Unified MeetingPlace, Release 7.0

Navigation: Planning Your Deployment > Planning the Capacity of your Cisco Unified MeetingPlace System


This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 7.0.

For more detailed information, see System Capacity.


Contents

Release 7.0.3 (MR2) with Cisco Unified MeetingPlace Web Conferencing

Configuration Details

This configuration assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
  • Six Audio blades
  • Six Video blades
  • Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace web conferencing
  • Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
  • Does not support Cisco WebEx-scheduled meetings

Capacity

Maximum Number Details

1500

Audio ports using G.711 or G.729 (without LEC)1

996

Audio ports using G.729 (with LEC), G.722, or iLBC1

240

Video ports using standard rate video

1000

Web sessions per Application Server when not using SSL or recording

1000

Web sessions per Application Server when using SSL or recording

500

Number of concurrent audio and web meetings per Application Server

3000

Total meetings per day

1000

Continuous meetings

50

Simultaneous meetings that can be recorded

500

Largest possible audio meeting 2

500

Largest possible web meeting when not using SSL or recording3

500

Largest possible web meeting when using SSL or recording3

5

Simultaneous Conference Manager sessions

200

Largest possible number of instances of the recurrence meeting 2

500

Largest possible number of invitees on single meeting 4

1

Database replication connection per Windows cluster (internal and external).

Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.

Footnote 1: When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

Footnote 2: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

Footnote 3: The Cisco MCS 7845-I3 Web Server supports a maximum of 600 web ports per server. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 500 ports due to the rate at which a single Audio blade can accept traffic.

Footnote 4: Largest possible number of invitees on MPWeb is 450.


Sizes

Maximum Size Component

250,000

User profiles in the database

400,000

Meetings in the database


Call Rate

Maximum Details

180 seconds

Time to get all ports into meetings (includes the time to disconnect from previous meetings)

20 seconds

Time to get the meetings started

15 CPS

Maximum call rate for inbound calls


Redundancy

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.


Recommended Practices

  • Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.
  • Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.



Release 7.0.3 (MR2) with Cisco WebEx Web Conferencing

Configuration Details

This configuration assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Two Windows web servers
  • Six Audio blades
  • Six Video blades
  • Single node configuration using the Hardware Media Server and Cisco WebEx web conferencing
  • Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
  • Does not support Cisco WebEx-scheduled meetings


Capacity

Maximum Number Details

1500

Audio ports using G.711 or G.729 (without LEC)1

996

Audio ports using G.729 (with LEC), G.722, or iLBC1

240

Video ports using standard rate video

1000

Web sessions per Application Server

500

Number of concurrent audio and web meetings per Application Server

50

Simultaneous meetings that can be recorded

500

Largest possible audio meeting 2

500

Largest possible web meeting using Meeting Center meetings

200

Largest possible number of instances of the recurrence meeting 2

500

Largest possible number of invitees on single meeting 4

5

Simultaneous Conference Manager sessions

Footnote 1: When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

Footnote 2: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.

Footnote 3: Largest possible number of invitees on MPWeb is 450.

Sizes

Maximum Size Component

250,000

User profiles in the database

400,000

Meetings in the database


Call Rate

Maximum Details

180 seconds

Time to get all ports into meetings (includes the time to disconnect from previous meetings)

20 seconds

Time to get the meetings started

15 CPS

Maximum call rate for inbound calls


Redundancy

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.


Recommended Practices

  • Scheduling and rescheduling of recurring meetings with more than 60 instances and 20 invitees should be performed during off-peak times to minimize delays perceived by users joining meetings. 5 Conference Manager limit is including 1 rescheduling session and 4 schedule/monitoring sessions of such meeting chain.
  • Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.



Release 7.0.2 (MR1) with Cisco Unified MeetingPlace Web Conferencing

Configuration Details

This configuration assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
  • Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
  • Six Audio blades
  • Six Video blades
  • Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace web conferencing
  • Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
  • Does not support Cisco WebEx-scheduled meetings


Capacity

Maximum Number Details

1500

Audio ports using G.711 or G.729 (without LEC)

996

Audio ports using G.729 (with LEC), G.722, or iLBC

240

Video ports using standard rate video

1000

Web sessions per Application Server when not using SSL or recording

700

Web sessions per Application Server when using SSL or recording

500

Number of concurrent audio and web meetings per Application Server

50

Simultaneous meetings that can be recorded

500

Largest possible audio meeting 1

500

Largest possible web meeting when not using SSL or recording

500

Largest possible web meeting when using SSL or recording

5

Simultaneous Conference Manager sessions

1

Database replication connection per Windows cluster (internal and external).

Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.

Footnote 1: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.


Sizes

Maximum Size Component

250,000

User profiles in the database

400,000

Meetings in the database


Call Rate

Maximum Details

180 seconds

Time to get all ports into meetings (includes the time to disconnect from previous meetings)

20 seconds

Time to get the meetings started

15 CPS

Maximum call rate for inbound calls


Redundancy

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.


Recommended Practices

  • Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
  • Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.



Release 7.0.2 (MR1) with Cisco WebEx Web Conferencing

Configuration Details

This configuration assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
  • One or two Windows web servers
  • Six Audio blades
  • Six Video blades
  • Single node configuration using the Hardware Media Server and Cisco WebEx web conferencing
  • Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
  • Does not support Cisco WebEx-scheduled meetings


Capacity

Maximum Number Details

1500

Audio ports using G.711 or G.729 (without LEC)

996

Audio ports using G.729 (with LEC), G.722, or iLBC

240

Video ports using standard rate video

1000

Web sessions per Application Server

500

Number of concurrent audio and web meetings per Application Server

50

Simultaneous meetings that can be recorded

500

Largest possible audio meeting 1

500

Largest possible web meeting using Meeting Center meetings1


Footnote 1: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.


Sizes

Maximum Size Component

250,000

User profiles in the database

400,000

Meetings in the database


Call Rate

Maximum Details

180 seconds

Time to get all ports into meetings (includes the time to disconnect from previous meetings)

20 seconds

Time to get the meetings started

15 CPS

Maximum call rate for inbound calls


Redundancy

Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.


Recommended Practices

  • Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
  • Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.



Release 7.0.2 (MR1) Using RSNA

Configuration Details

This configuration assumes the following:

  • Two Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
  • 12 Audio blades
  • 12 Video blades
  • Two nodes using the Hardware Media Server
  • Supports audio/video-only reservationless meetings
  • Supports Outlook Scheduling interface
  • There is no web conferencing with RSNA deployments


Capacity

Maximum Number Details

2x1500

Audio ports using G.711 or G.729 (without LEC)

2x996

Audio ports using G.729 (with LEC), G.722, or iLBC

2x240

Video ports using standard rate video

1000

Simultaneous audio meetings

500

Largest possible audio meeting1

Footnote 1: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.


Sizes

Maximum Size Component

250,000

User profiles in the database

400,000

Meetings in the database


Call Rate

Maximum Details

180 seconds

Time to get all ports into meetings (includes the time to disconnect from previous meetings)

20 seconds

Time to get the meetings started

30 CPS

Maximum call rate for inbound calls


Recommended Practices

  • Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
  • Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.

Rating: 0.0/5 (0 votes cast)

Personal tools