Cisco Unified MeetingPlace, Release 7.0 -- Network Requirements - Revision history

Annekim: 1 revision

2010-08-17T15:28:28Z

1 revision

← Older revision		Revision as of 15:28, 17 August 2010
Line 764:		Line 764:
	* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.		* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.

-	* Replication happens ~~asynchronousously~~ for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.	+	* Replication happens asynchronously for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.

	* Data for user profiles; groups; and past, present, and future meetings is replicated.		* Data for user profiles; groups; and past, present, and future meetings is replicated.

Annekim: /* Failover Requirements */

2010-08-03T22:15:35Z

Failover Requirements

← Older revision		Revision as of 22:15, 3 August 2010
Line 764:		Line 764:
	* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.		* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.

-	* Replication happens ~~asynchronousously~~ for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.	+	* Replication happens asynchronously for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.

	* Data for user profiles; groups; and past, present, and future meetings is replicated.		* Data for user profiles; groups; and past, present, and future meetings is replicated.

Annekim: 1 revision

2010-07-14T12:54:39Z

1 revision

← Older revision		Revision as of 12:54, 14 July 2010
Line 764:		Line 764:
	* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.		* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.

-	* Replication happens ~~asynchronously~~ for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.	+	* Replication happens asynchronousously for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.

	* Data for user profiles; groups; and past, present, and future meetings is replicated.		* Data for user profiles; groups; and past, present, and future meetings is replicated.

Annekim at 21:23, 14 May 2010

2010-05-14T21:23:23Z

← Older revision		Revision as of 21:23, 14 May 2010
Line 729:		Line 729:
	Cisco WebEx		Cisco WebEx
	\|}		\|}
		+
		+
		+	'''Note:''' The SOCKS configuration is an optional configuration and is not used unless you specifically configure it. The standard SOCKS port is 1080 but you can configure a different port. Other types of proxies (such as HTTP) are not supported by Cisco Unified MeetingPlace for Cisco WebEx connectivity.
		+
		+

	== Application Server to Media Server Connectivity ==		== Application Server to Media Server Connectivity ==

Annekim: /* Table: Outgoing Ports Used by Cisco Unified MeetingPlace */

2010-05-14T21:01:04Z

Table: Outgoing Ports Used by Cisco Unified MeetingPlace

← Older revision		Revision as of 21:01, 14 May 2010
Line 709:		Line 709:

	SMTP server or Microsoft Exchange server		SMTP server or Microsoft Exchange server
-	\|}	+	\|-
		+	\|

		+	SOCKS
		+	\|

		+	TCP
		+	\|

		+	1080
		+	\|

		+	Optional configuration for connecting to Cisco WebEx via a proxy configuration
		+
		+	\|
		+	Application Server
		+	\|
		+
		+	Cisco WebEx
		+	\|}

	== Application Server to Media Server Connectivity ==		== Application Server to Media Server Connectivity ==

Docwikibot: Bot: Adding {{Template:Required Metadata}}

2009-12-18T01:37:58Z

Bot: Adding {{Template:Required Metadata}}

← Older revision		Revision as of 01:37, 18 December 2009
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
	'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]		'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

Jmcmulle at 19:48, 4 June 2009

2009-06-04T19:48:47Z

← Older revision		Revision as of 19:48, 4 June 2009
Line 721:		Line 721:
	* If Primary and Failover Application Servers are deployed in different locations, then Media Server hardware must be duplicated at the second site and is only utilized when that "Failover" Application Server is made "Active".		* If Primary and Failover Application Servers are deployed in different locations, then Media Server hardware must be duplicated at the second site and is only utilized when that "Failover" Application Server is made "Active".

-
-
-	~~== Application Server Redundancy and Failover==~~
-	* Both Primary and Failover Application Servers must be licensed exactly the same. Each Application Server license key is applied separately based on MAC address of the MCS server where the software is installed.
-	*If Primary and Failover Application Server are deployed in different locations, then the same VLAN configuration must be spanned between data centers to accomodate the shared IP address and hostname on both Application Servers.
-	* Informix Database replication is buffered via the LAN/WAN and the heartbeat is done every 60 sec. If there is no response, it does a ping. For latency, there is no minimum requirement. Network Bandwidth: 128kbps minimum between Application Servers.
-	* Replication strategy: Replication happens asynchronousously for each configuration change related to users/groups/conferences. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the config changes are queued up on the source server and is synced with the target server when the connection is re-established.
-	* What is replicated: Data relevant to user profiles, groups and past, present and future meetings.

	== Application Server to Web Server Connectivity ==		== Application Server to Web Server Connectivity ==
Line 743:		Line 735:
	== Failover Requirements ==		== Failover Requirements ==

		+	* To configure failover, you need two Application Servers with a high-speed network connection (preferably 100Mpbs or better) between them.
		+
		+	* Both the active and the standby Application Servers must be licensed exactly the same. Each Application Server license key is applied separately based on the MAC address of the Cisco MCS where the software is installed.
		+
		+	*If the active and standby Application Server are deployed in different locations, then the same VLAN configuration must be spanned between data centers to accomodate the shared IP address and hostname on both Application Servers.
		+
		+	* Informix database replication is buffered via the LAN/WAN and the heartbeat is done every 60 seconds. If there is no response, it does a ping. For latency, there is no minimum requirement. Network bandwidth is 128kbps minimum between Application Servers.
		+
		+	* Replication happens asynchronousously for each configuration change related to users, groups, or meetings. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the configuration changes are queued up on the source server and are synced with the target server when the connection is re-established.

-	~~To configure failover~~, ~~you need two Application Servers with a high-speed network connection (preferably 100Mpbs or better) between them~~.	+	* Data for user profiles; groups; and past, present, and future meetings is replicated.



	[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]		[[Category:Requirements for Cisco Unified MeetingPlace, Release 7.0]]

Jmcmulle: for 5003 and 61004 changed "expose to web server" to "expose to ALL web serverS"

2009-04-16T18:14:18Z

for 5003 and 61004 changed "expose to web server" to "expose to ALL web serverS"

← Older revision		Revision as of 18:14, 16 April 2009
Line 121:		Line 121:
	\|		\|

-	Expose to Web ~~Server~~ in the DMZ.	+	Expose to all Web Servers in the DMZ.


Line 223:		Line 223:
	\|		\|

-	Expose to Web ~~Server~~ in the DMZ.	+	Expose to all Web Servers in the DMZ.
	\|-		\|-
	\|		\|

Bobbmart: /* Application Server to Media Server Connectivity */

2009-04-14T17:46:32Z

Application Server to Media Server Connectivity

← Older revision		Revision as of 17:46, 14 April 2009
Line 717:		Line 717:


-	The Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Media Server blades that are remotely located.	+	* The Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Media Server blades that are remotely located.
		+	* If Primary and Failover Application Servers are deployed, all Media Server hardware can be shared if deployed in a single datacenter.
		+	* If Primary and Failover Application Servers are deployed in different locations, then Media Server hardware must be duplicated at the second site and is only utilized when that "Failover" Application Server is made "Active".


		+
		+	== Application Server Redundancy and Failover==
		+	* Both Primary and Failover Application Servers must be licensed exactly the same. Each Application Server license key is applied separately based on MAC address of the MCS server where the software is installed.
		+	*If Primary and Failover Application Server are deployed in different locations, then the same VLAN configuration must be spanned between data centers to accomodate the shared IP address and hostname on both Application Servers.
		+	* Informix Database replication is buffered via the LAN/WAN and the heartbeat is done every 60 sec. If there is no response, it does a ping. For latency, there is no minimum requirement. Network Bandwidth: 128kbps minimum between Application Servers.
		+	* Replication strategy: Replication happens asynchronousously for each configuration change related to users/groups/conferences. The source server captures the configuration changes and reliably transmits each transaction to the other server. In case the target server or the link between them is down, the config changes are queued up on the source server and is synced with the target server when the connection is re-established.
		+	* What is replicated: Data relevant to user profiles, groups and past, present and future meetings.

	== Application Server to Web Server Connectivity ==		== Application Server to Web Server Connectivity ==

MeetingPlace Express Moderator at 16:35, 6 April 2009

2009-04-06T16:35:25Z

← Older revision		Revision as of 16:35, 6 April 2009
Line 126:		Line 126:
	You can set up port 5003 to traverse the firewall either inbound or outbound.		You can set up port 5003 to traverse the firewall either inbound or outbound.

-	'''NOTE:''' Port 5003 must be closed inbound (that is, communication from the DMZ Web Server to the Application Server must be closed) to allow the Application Server to do a reverse connection.	+	'''NOTE:''' Port 5003 must be closed inbound (that is, communication from the DMZ Web Server to the Application Server must be closed) to allow the Application Server to consistently use a reverse connection successfully.

	\|-		\|-