Le Blog de Julien Mousqueton » mise à jour

Plus d’évolution de VMware Lab Manager

Julien — Tue, 15 Feb 2011 13:21:22 +0000

VMware l’a annoncé le 14 février, il n’y aura plus de mise à jour majeure de VMware Lab Manager.

Le support sera assuré jusqu’au 1er mai 2013

We want to provide you with an important update about the vCenter Lab Manager product. As customers continue to expand the use of virtualization both inside the datacenter and outside the firewall, we are focusing on delivering infrastructure solutions that can support these expanded scalability and security requirements. As a result of this focus, we have decided to discontinue additional major releases of vCenter Lab Manager. Lab Manager 4 will continue to be supported in line with our General Support Policy through May 1^st, 2013.

As VMware continues to invest in our customers’ journey to cloud computing, we are focusing on delivering secure multi-tenant enterprise hybrid clouds with VMware vCloud Director. vCloud Director is a new software solution that provides the scalability and security necessary to deliver catalog-based self-service provisioning across different workload types, across multiple enterprise tenants, and across both private and public deployment models.

As a customer of Lab Manager, we would like to offer you a special opportunity to leverage the scale and security of vCloud Director. Customers who are active on SnS may exchange their existing licenses of Lab Manager to licenses of vCloud Director at no additional cost. This exchange program is entirely optional and may be exercised anytime during Lab Manager’s General Support period. This provides you the freedom and flexibility to decide whether and when to implement a secure enterprise hybrid cloud.

For more information about this product update, visit http://www.vmware.com/go/labmanager-update

A lire avant de migrer vers vSphere 4.1

Julien — Fri, 16 Jul 2010 13:02:47 +0000

A peine quelques jours après la sortie de vSphere 4.1, un certain nombre de KB sont déjà disponibles, voici une liste non exhaustive, à étudier avant de migrer :

http://kb.vmware.com/kb/1023163 Installing a VMware Service Manager license
http://kb.vmware.com/kb/1017910 Using Tech Support Mode in ESXi 4.1
http://kb.vmware.com/kb/1017928 Downloading the license file fails
http://kb.vmware.com/kb/1018178 ESX virtual machine monitor encounters a critical error and shuts down

http://kb.vmware.com/kb/1018180 Cannot power on a virtual machine and you receive an Admission Check Failed error
http://kb.vmware.com/kb/1018181 Attempting to remove a host from the inventory when it is connected to vDS generates an error
http://kb.vmware.com/kb/1018183 vSphere 4 license expires and you cannot register your product
http://kb.vmware.com/kb/1019144 vCenter Server 4.1 fails to install or upgrade with the error: This installation package is not supported by this processor type
http://kb.vmware.com/kb/1019738 Upgrading to Site Recovery Manager 4.0 Update 1 fails with the error: can’t open perl script « e:\program »: no such file or directory
http://kb.vmware.com/kb/1019890 Virtual machines fail to start with a timeout error when performing a test failover
http://kb.vmware.com/kb/1020121 Powering on virtual machines fails with the error: MAX VCPUs limit is reached
http://kb.vmware.com/kb/1021491 Network configuration of a recovered virtual machine during Site Recovery Manager failover fails with the log error: Network Device Not Found
http://kb.vmware.com/kb/1021635 Migrating to the vCenter Server 4.1 database
http://kb.vmware.com/kb/1021695 Update Manager 4.1 patch repository features
http://kb.vmware.com/kb/1021769 Configuring IPv6 with ESX and ESXi 4.1
http://kb.vmware.com/kb/1021779 Working with firewall rules in ESX 4.x
http://kb.vmware.com/kb/1021801 Location of ESXi log files
http://kb.vmware.com/kb/1021806 Location of log files for VMware products
http://kb.vmware.com/kb/1021827 A recovery or test recovery plan fails with virtual machines that have a pre-boot message
http://kb.vmware.com/kb/1021829 Deleted networks continue to appears in the Site Recovery Manager Configure Test Network dialog
http://kb.vmware.com/kb/1021919 Site Recovery Manager shadow virtual machines on the recovery site lose their vDS settings after a test failover
http://kb.vmware.com/kb/1021953 I/O Statistics in vSphere 4.1
http://kb.vmware.com/kb/1021970 Overview of Active Directory integration in ESX 4.1 and ESXi 4.1
http://kb.vmware.com/kb/1021976 vStorage APIs for Array Integration FAQ
http://kb.vmware.com/kb/1022030 ALUA parameters in the output of ESX/ESXi 4.1 commands
http://kb.vmware.com/kb/1022077 Support for the scsi_device_reprobe() API in VMKLinux in ESX 4.0 and 4.1
http://kb.vmware.com/kb/1022101 Installing ESX 4.1 and vCenter Server 4.1 best practices
http://kb.vmware.com/kb/1022104 Upgrading to ESX 4.1 and vCenter Server 4.1 best practices
http://kb.vmware.com/kb/1022137 vSphere 4.1 upgrade pre-installation requirements and considerations
http://kb.vmware.com/kb/1022140 Upgrading ESX 4.0 to ESX 4.1
http://kb.vmware.com/kb/1022178 Solution Licensing
http://kb.vmware.com/kb/1022256 vCenter Server 4.1 network port requirements
http://kb.vmware.com/kb/1022263 Deploying ESXi 4.1 using the Scripted Install feature
http://kb.vmware.com/kb/1022289 Changing the number of virtual CPUs per virtual socket in ESX/ESXi 4.1
http://kb.vmware.com/kb/1022290 USB support for ESX/ESXi 4.1
http://kb.vmware.com/kb/1022303 Avocent ACS6000 Virtual Serial Port Concentrator
http://kb.vmware.com/kb/1022308 Troubleshooting ESXi 4.1 Scripted Install errors
http://kb.vmware.com/kb/1022536 Using vShieldZones 1.0 with ESX 4.1
http://kb.vmware.com/kb/1022585 Network I/O Resource Management in vSphere 4.1 with vDS
http://kb.vmware.com/kb/1022587 Excluding a physical NIC from network resource management
http://kb.vmware.com/kb/1022590 Load Based Teaming in vSphere 4.1
http://kb.vmware.com/kb/1022842 Changes to DRS in vSphere 4.1
http://kb.vmware.com/kb/1022843 Changes to VMware High Availability in vSphere 4.1
http://kb.vmware.com/kb/1022844 Changes to Fault Tolerance in vSphere 4.1
http://kb.vmware.com/kb/1022851 Changes to vMotion in vSphere 4.1
http://kb.vmware.com/kb/1022867 Performing local administration of vCenter Server Heartbeart from an account that did not perform the installation
http://kb.vmware.com/kb/1022869 Joining a vCenter Server Heartbeat instance to a Linked Mode Group and Isolating a vCenter Server Instance from a Linked Mode Group when protected by vCenter Server Heartbeat
http://kb.vmware.com/kb/1022874 Downgrading vCenter Server Heartbeat to a previous version
http://kb.vmware.com/kb/1022877 Uninstalling VMware vCenter Server Heartbeat
http://kb.vmware.com/kb/1023026 Creating a static route for the VMware Channel
http://kb.vmware.com/kb/1023118 Changes to VMware Support Options in vSphere 4.1
http://kb.vmware.com/kb/1024066 TCP Offload features on all NICs must be disabled before installing vCenter Server Heartbeat
http://kb.vmware.com/kb/1021920 Site Recovery Manager registering virtual machine task fails during failover with the error: Creating VM timeout
http://kb.vmware.com/kb/1022091 Troubleshooting Storage I/O Control
http://kb.vmware.com/kb/1023990 VMware ESX and ESXi 4.1 Comparison

VMware vSphere 4.0 Update 2 et le Cisco Nexus 1000v

Julien — Sat, 19 Jun 2010 10:00:33 +0000

Si vous utilisez le switch virtuel de chez Cisco pour vSphere et que vous souhaitez mettre à jour votre infrastructure virtuelle avec l’update 2, n’oublie pas la gestion des compatibilités entre le Nexus 1000v et vSphere.

En effet ESX 4.0 U2 n’est pas compatible avec le Nexus 1000V release 4.0(4)SV1(1). Il est impératif de mettre à jour le Nexus 1000v avec la release 4.0(4)SV1(2) ou mieux la release 4.0(4)SV1(3) du module VEM.

VMware vSphere 4 Update 1 avec le Cisco Nexus 1000v

Julien — Sat, 21 Nov 2009 14:22:10 +0000

Attention si votre infrastructure comporte des Cisco Nexus 1000v, lors de l’upgrade de vSphere 4 vers vSphere 4 Update 1.

Il est impératif de mettre à jour les VEM (Virtual Ethernet Module) du Cisco Nexus 1000v juste après l’upgrade.

vSphere 4 Update 1

Julien — Fri, 20 Nov 2009 06:29:55 +0000

Une grande partie de la suite vSphere vient d’être mise à jour :

ESX 4 Update 1
ESXi 4 Update 1
vCenter 4 Update 1
DataRecovery 1.1

La suite sur Forum-VMware …