Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment - Revision history

Sutibbet: Removed the statement, "300 ms RTT maximum if above three minutes is acceptable for Primary Meeting Director to Secondary Meeting Director failover."

2013-01-25T16:04:23Z

Removed the statement, "300 ms RTT maximum if above three minutes is acceptable for Primary Meeting Director to Secondary Meeting Director failover."

← Older revision		Revision as of 16:04, 25 January 2013
Line 59:		Line 59:
	Combined nodes provide Meeting Director services in deployments with four or fewer nodes. Combined nodes also provide conferencing functionality that is described in the following section.		Combined nodes provide Meeting Director services in deployments with four or fewer nodes. Combined nodes also provide conferencing functionality that is described in the following section.

-	Cisco recommends that all nodes in a site should be either all configured as ~~Electronic~~ Media Server (EMS) or all Hardware Media Server (HMS). By using only one type of media server, you ensure a more consistent video quality regardless of which node a conference is hosted on. If a site contains a combination of EMS and HMS servers, the video quality will be based on the node that hosts the meeting.	+	Cisco recommends that all nodes in a site should be either all configured as Express Media Server (EMS) or all Hardware Media Server (HMS). By using only one type of media server, you ensure a more consistent video quality regardless of which node a conference is hosted on. If a site contains a combination of EMS and HMS servers, the video quality will be based on the node that hosts the meeting.

	== About Conferencing Nodes ==		== About Conferencing Nodes ==
Line 90:		Line 90:
	== About Capacity ==		== About Capacity ==

-	Your hardware platform determines the total capacity for your system. For example, two UCS B series blades can accommodate 1,200 G.711 ports (with G.729 less capacity). Licensing is based on the number of users (hosts) and not on the number of ports as it was in previous releases. If you install two UCS blades, you have the capacity for 2,400 non-redundant ports or 1,200 redundant ports.	+	Your hardware platform determines the total capacity for your system. For example, two UCS B series blades can accommodate 1,200 G.711 ports (with G.729 less capacity). Licensing is based on the number of users (hosts) and not on the number of ports as it was in previous releases. If you install two UCS B series blades, you have the capacity for 2,400 non-redundant ports or 1,200 redundant ports.


Line 111:		Line 111:
	RTT latency requirements:		RTT latency requirements:
	* 200 ms or less RTT maximum if you expect approximately one minute for Primary Meeting Director to Secondary Meeting Director failover to occur.		* 200 ms or less RTT maximum if you expect approximately one minute for Primary Meeting Director to Secondary Meeting Director failover to occur.
-	** 300 ms RTT maximum if above three minutes is acceptable for Primary Meeting Director to Secondary Meeting Director failover.
	* Adding new nodes requires maximum latency of 200 ms RTT or less (there is a timeout after 30 minutes).		* Adding new nodes requires maximum latency of 200 ms RTT or less (there is a timeout after 30 minutes).

Sutibbet at 19:37, 17 January 2013

2013-01-17T19:37:56Z

← Older revision		Revision as of 19:37, 17 January 2013
Line 17:		Line 17:


-	*[[Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment#About Meeting Director Nodes\|About Meeting Director Nodes]]	+
-	*[[Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment#About Conferencing Nodes\|About Conferencing Nodes]]	+
-	*[[Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment#About Capacity\|About Capacity]]	+
-	*[[Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment#Planning Your Call Manager Configuration\|Planning Your Call Manager Configuration]]	+
-	*[[Cisco Unified MeetingPlace Release 8.5 -- Planning a Multinode Deployment#Determining Your Multinode Topology\|Determining Your Multinode Topology]]	+

	== About Meeting Director Nodes ==		== About Meeting Director Nodes ==
Line 32:		Line 28:
	* iTSP Server		* iTSP Server
	* UserSync		* UserSync
		+

	Your multinode system must have two Meeting Director nodes. The Primary Meeting Director node is the only active Meeting Director unless a failover condition occurs. If a failure occurs, the Secondary Meeting Director, located on a separate node, assumes all Meeting Director tasks. The Primary Meeting Director node resumes performing all Meeting Director tasks when it comes back online. No user action is required.		Your multinode system must have two Meeting Director nodes. The Primary Meeting Director node is the only active Meeting Director unless a failover condition occurs. If a failure occurs, the Secondary Meeting Director, located on a separate node, assumes all Meeting Director tasks. The Primary Meeting Director node resumes performing all Meeting Director tasks when it comes back online. No user action is required.
Line 108:		Line 105:
	* Video RTP normal video bandwidth sizing is applicable.		* Video RTP normal video bandwidth sizing is applicable.

-	WAN bandwidth ~~recommendations~~:	+	WAN bandwidth requirements:
	* 4 Mbps minimum bandwidth for the WAN link between any two nodes. Nodes can be standalone Meeting Directors, root nodes, or leaf nodes.		* 4 Mbps minimum bandwidth for the WAN link between any two nodes. Nodes can be standalone Meeting Directors, root nodes, or leaf nodes.
	Two data centers with WAN and two servers in each DC requires 4 Mbps.		Two data centers with WAN and two servers in each DC requires 4 Mbps.

-	RTT latency ~~recommendations~~:	+	RTT latency requirements:
	* 200 ms or less RTT maximum if you expect approximately one minute for Primary Meeting Director to Secondary Meeting Director failover to occur.		* 200 ms or less RTT maximum if you expect approximately one minute for Primary Meeting Director to Secondary Meeting Director failover to occur.
	** 300 ms RTT maximum if above three minutes is acceptable for Primary Meeting Director to Secondary Meeting Director failover.		** 300 ms RTT maximum if above three minutes is acceptable for Primary Meeting Director to Secondary Meeting Director failover.
-	* Adding new nodes requires maximum latency of 200 ms RTT (there is a timeout after 30 minutes).	+	* Adding new nodes requires maximum latency of 200 ms RTT or less (there is a timeout after 30 minutes).

-	DNS ~~recommendations~~:	+	DNS requirements:
	* All Meeting Director nodes, conferencing nodes, and Cisco WebEx node FQDNs are required for DNS resolution between all servers.		* All Meeting Director nodes, conferencing nodes, and Cisco WebEx node FQDNs are required for DNS resolution between all servers.
	* Make sure you do not have multiple names to IP addresses.		* Make sure you do not have multiple names to IP addresses.

MeetingPlace Moderator at 18:38, 2 November 2012

2012-11-02T18:38:41Z

← Older revision		Revision as of 18:38, 2 November 2012
Line 14:		Line 14:
	Multinode deployments feature the Cisco WebEx user interface with Cisco Unified MeetingPlace audio and video conferencing.		Multinode deployments feature the Cisco WebEx user interface with Cisco Unified MeetingPlace audio and video conferencing.
	* Using Cisco WebEx Node in a WebEx-scheduling deployment has certain limitations and is therefore not recommended. For a list of limitations, see the "Limitations and Restrictions" section of the Release Notes for Cisco Unified MeetingPlace Release 8.5 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.		* Using Cisco WebEx Node in a WebEx-scheduling deployment has certain limitations and is therefore not recommended. For a list of limitations, see the "Limitations and Restrictions" section of the Release Notes for Cisco Unified MeetingPlace Release 8.5 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.
-	* If you include Cisco WebEx Node as part of your deployment, you must have at least two nodes built (one as the primary and one as the secondary ~~MBD~~) before installing your first Cisco WebEx Node.	+	* If you include Cisco WebEx Node as part of your deployment, you must have at least two nodes built (one as the primary and one as the secondary Meeting Director) before installing your first Cisco WebEx Node.

MeetingPlace Moderator: /* Figure 6: Large-Scale System with Multiple Regions */

2012-01-13T23:33:45Z

Figure 6: Large-Scale System with Multiple Regions

← Older revision		Revision as of 23:33, 13 January 2012
Line 273:		Line 273:
	===== Figure 6: Large-Scale System with Multiple Regions=====		===== Figure 6: Large-Scale System with Multiple Regions=====

-	[[Image:~~281807~~.jpg]]	+	[[Image:284606.jpg]]

	[[Category: Planning for Cisco Unified MeetingPlace Release 8.5]]		[[Category: Planning for Cisco Unified MeetingPlace Release 8.5]]

MeetingPlace Moderator: 1 revision

2011-08-01T18:31:11Z

1 revision

← Older revision

Revision as of 18:31, 1 August 2011

MeetingPlace Moderator: /* One Region with Two Nodes with WebEx Node for ASR */

2011-07-28T03:34:24Z

One Region with Two Nodes with WebEx Node for ASR

← Older revision		Revision as of 03:34, 28 July 2011
Line 79:		Line 79:
	* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)		* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)
	* Maximum of four regions		* Maximum of four regions
-	* Up to 30 Dial-in numbers are supported configured in Cisco Unified MeetingPlace that are sent to Cisco WebEx for email notifications and in session "Info" tab dial-in information. The Email template may be customized to add additional global numbers with a web link or ~~document~~ linked.	+	* Up to 30 Dial-in numbers are supported, configured in Cisco Unified MeetingPlace that are sent to Cisco WebEx for email notifications and in session "Info" tab dial-in information. The Email template may be customized to add additional global numbers with a web link or linked document.

	'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.		'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.
Line 99:		Line 99:

	Configuring Cisco Unified Communications Manager for a multinode topology is a multi-task procedure. You must configure Cisco Unified Call Manager clusters for each region in your multinode deployment. For more information, refer to the "How to Configure Call Control on WebEx-Scheduled Deployments" section of the "Configuring Call Control" module in the Compiled Administration Documentation for Cisco Unified MeetingPlace Release 8.5.		Configuring Cisco Unified Communications Manager for a multinode topology is a multi-task procedure. You must configure Cisco Unified Call Manager clusters for each region in your multinode deployment. For more information, refer to the "How to Configure Call Control on WebEx-Scheduled Deployments" section of the "Configuring Call Control" module in the Compiled Administration Documentation for Cisco Unified MeetingPlace Release 8.5.
-

	== Network Requirements ==		== Network Requirements ==
Line 199:		Line 198:
	Multinode configurations with Webex Node for ASR provide bandwidth aggregation for two media types: WebEx meetings and high-quality video.		Multinode configurations with Webex Node for ASR provide bandwidth aggregation for two media types: WebEx meetings and high-quality video.

-	Configure ASR nodes with Cisco WebEx node software in your network close to your conferencing nodes. This provides bandwidth aggregation for both web conferencing and ~~videoconferencing~~. The example shown in this section is a two-node system but you can configure WebEx node for ASR on larger deployments as well. Cisco WebEx Node is deployed as a shared port adapter for the Cisco ASR 1000 series router.	+	Configure ASR nodes with Cisco WebEx node software in your network close to your conferencing nodes. This provides bandwidth aggregation for both web conferencing and video conferencing. The example shown in this section is a two-node system but you can configure WebEx node for ASR on larger deployments as well. Cisco WebEx Node is deployed as a shared port adapter for the Cisco ASR 1000 series router.

	Cisco WebEx node for ASR supports the following:		Cisco WebEx node for ASR supports the following:
Line 214:		Line 213:

	[[Image:246705.jpg]]		[[Image:246705.jpg]]
-

	== One Region with Three Nodes ==		== One Region with Three Nodes ==

MeetingPlace Moderator at 00:11, 23 July 2011

2011-07-23T00:11:02Z

← Older revision		Revision as of 00:11, 23 July 2011
Line 79:		Line 79:
	* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)		* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)
	* Maximum of four regions		* Maximum of four regions
-	* Up to 30 Dial-in numbers are supported ~~oonfigured~~ in MeetingPlace that are sent to ~~Webex~~ for email notifications and in session "Info" tab dial-in information. The Email template may be customized to add additional global numbers with a web link or document linked.	+	* Up to 30 Dial-in numbers are supported configured in Cisco Unified MeetingPlace that are sent to Cisco WebEx for email notifications and in session "Info" tab dial-in information. The Email template may be customized to add additional global numbers with a web link or document linked.

	'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.		'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.

MeetingPlace Moderator at 00:08, 23 July 2011

2011-07-23T00:08:26Z

← Older revision		Revision as of 00:08, 23 July 2011
Line 79:		Line 79:
	* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)		* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)
	* Maximum of four regions		* Maximum of four regions
-	* Up to 30 ~~Dialin~~ numbers are supported oonfigured in MeetingPlace that are sent to Webex for email notifications and in session "Info" tab ~~dialin~~ information. The Email template may be customized to add additional global numbers with a web link or document linked.	+	* Up to 30 Dial-in numbers are supported oonfigured in MeetingPlace that are sent to Webex for email notifications and in session "Info" tab dial-in information. The Email template may be customized to add additional global numbers with a web link or document linked.

	'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.		'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.

Bobbmart: /* About Conferencing Nodes */

2011-07-22T15:43:40Z

About Conferencing Nodes

← Older revision		Revision as of 15:43, 22 July 2011
Line 79:		Line 79:
	* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)		* Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)
	* Maximum of four regions		* Maximum of four regions
		+	* Up to 30 Dialin numbers are supported oonfigured in MeetingPlace that are sent to Webex for email notifications and in session "Info" tab dialin information. The Email template may be customized to add additional global numbers with a web link or document linked.

	'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.		'''Note: ''' Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.
Line 89:		Line 90:
	** Web conferencing per SPA (500 sessions each)		** Web conferencing per SPA (500 sessions each)
	** HQ Video/VoIP per SPA (capacity based on usage)		** HQ Video/VoIP per SPA (capacity based on usage)
-

	== About Capacity ==		== About Capacity ==

Cgriffen at 19:12, 15 June 2011

2011-06-15T19:12:55Z

← Older revision		Revision as of 19:12, 15 June 2011
Line 98:		Line 98:
	== Planning Your Call Manager Configuration ==		== Planning Your Call Manager Configuration ==

-	Configuring Cisco Unified Communications Manager for a multinode topology is a multi-task procedure. You must configure Cisco Unified Call Manager clusters for each region in your multinode deployment. For more information, refer to the "How to Configure Call Control on WebEx-Scheduled Deployments" section ~~at http://preview~~.~~cisco.com/en/US/docs/voice_ip_comm/meetingplace/8_5/english/administration/route_sip_external_docbase_0900e4b18178c751_4container_external_docbase_0900e4b181f6bf39.html#wp1259172~~.	+	Configuring Cisco Unified Communications Manager for a multinode topology is a multi-task procedure. You must configure Cisco Unified Call Manager clusters for each region in your multinode deployment. For more information, refer to the "How to Configure Call Control on WebEx-Scheduled Deployments" section of the "Configuring Call Control" module in the Compiled Administration Documentation for Cisco Unified MeetingPlace Release 8.5.