Unified Communications VMware Requirements - Revision history

Davwats2: 1 revision

2013-05-07T14:54:57Z

1 revision

← Older revision

Revision as of 14:54, 7 May 2013

Pacolli2: Add ESXi5.1 support for VCS and Conductor

2013-05-07T13:00:52Z

Add ESXi5.1 support for VCS and Conductor

← Older revision		Revision as of 13:00, 7 May 2013
Line 286:		Line 286:
	! VMware vSphere ESXi 4.1 <br><br>		! VMware vSphere ESXi 4.1 <br><br>
	! VMware vSphere ESXi 5.0 <br><br>		! VMware vSphere ESXi 5.0 <br><br>
		+	! VMware vSphere ESXi 5.1 <br><br>
	\|-		\|-
	\| Cisco TelePresence Manager		\| Cisco TelePresence Manager
Line 291:		Line 292:
	\| 1.8.x, 1.9.0<br>		\| 1.8.x, 1.9.0<br>
	\| 1.8.x, 1.9.0<br>		\| 1.8.x, 1.9.0<br>
		+	\| Not currently supported<br>
	\|-		\|-
	\| Cisco TelePresence Multipoint Switch		\| Cisco TelePresence Multipoint Switch
Line 296:		Line 298:
	\| 1.8.x, 1.9.0<br>		\| 1.8.x, 1.9.0<br>
	\| 1.8.x, 1.9.0<br>		\| 1.8.x, 1.9.0<br>
		+	\| Not currently supported<br>
	\|-		\|-
	\| Cisco TelePresence Video Communication Server<br>		\| Cisco TelePresence Video Communication Server<br>
Line 301:		Line 304:
	\| X7.1 and later<br>		\| X7.1 and later<br>
	\| X7.1 and later with ESXi 5.0 Update 1<br>		\| X7.1 and later with ESXi 5.0 Update 1<br>
		+	\| X7.1 and later<br>
	\|-		\|-
	\| Cisco TelePresence Conductor<br>		\| Cisco TelePresence Conductor<br>
Line 306:		Line 310:
	\| XC1.2 and later<br>		\| XC1.2 and later<br>
	\| XC1.2 and later with ESXi 5.0 Update 1<br>		\| XC1.2 and later with ESXi 5.0 Update 1<br>
		+	\| XC1.2 and later<br>
	\|}		\|}

Dosproul: 1 revision

2013-04-30T16:58:06Z

1 revision

← Older revision

Revision as of 16:58, 30 April 2013

Anilve: Added support for ESXi5.1

2013-04-30T16:31:37Z

Added support for ESXi5.1

← Older revision		Revision as of 16:31, 30 April 2013
Line 172:		Line 172:
	\| 8.0(2)+, 8.5(x), 8.6(x), 9.0(x), 9.1(x)		\| 8.0(2)+, 8.5(x), 8.6(x), 9.0(x), 9.1(x)
	\| 8.0(2)+, 8.5(x), 8.6(x), 9.0(x), 9.1(x)		\| 8.0(2)+, 8.5(x), 8.6(x), 9.0(x), 9.1(x)
-	\| ~~Not supported~~	+	\| 8.0(2)+, 8.5(x), 8.6(x), 9.0(x), 9.1(x)
	\|-		\|-
	\| Cisco Unity		\| Cisco Unity
Line 178:		Line 178:
	\| 7.x and later		\| 7.x and later
	\| 7.x and later		\| 7.x and later
-	\| ~~Not supported~~	+	\| 7.x and later
	\|-		\|-
	\| Cisco Unified Presence		\| Cisco Unified Presence

Karrande: 1 revision

2013-04-18T02:02:45Z

1 revision

← Older revision

Revision as of 02:02, 18 April 2013

Rfarber: /* Multiple Physical NICs and vNICs */

2013-04-17T20:36:36Z

Multiple Physical NICs and vNICs

← Older revision		Revision as of 20:36, 17 April 2013
Line 1,555:		Line 1,555:
	NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client\|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].		NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client\|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

-	Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.	+	Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM and UCCX only support a single vNIC with a single IP address.

	=== VMware High Availability (HA) ===		=== VMware High Availability (HA) ===

Dosproul: 1 revision

2013-04-17T16:27:52Z

1 revision

← Older revision

Revision as of 16:27, 17 April 2013

Jarias: /* 9.1 apps, vSphere 5.1 */

2013-04-17T13:38:04Z

9.1 apps, vSphere 5.1

Show changes

Davwats2: 1 revision

2013-04-08T17:04:10Z

1 revision

← Older revision

Revision as of 17:04, 8 April 2013

Tgerbic at 20:26, 28 March 2013

2013-03-28T20:26:28Z

Show changes