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

Dire que j’ai connu les disquette 5″1/4

]]> http://www.julienmousqueton.fr/2010/12/31/lhistoire-du-stockage-amovible-2/feed/ 1 http://www.julienmousqueton.fr/2010/11/11/alerte-vmware-utilisateurs-ibm/ http://www.julienmousqueton.fr/2010/11/11/alerte-vmware-utilisateurs-ibm/#comments Thu, 11 Nov 2010 20:26:37 +0000 Julien http://www.julienmousqueton.fr/?p=1760

 
An issue that affects users with IBM hardware, running ESX/ESXi 4.1 has prompted us to issue this Support Alert.

When using IBM x3650 M3 or BladeCenter HS22V servers, you may experience these symptoms:

HBAs stop responding
Other PCIs devices may also stop responding
You see an an illegal vector shortly before an HBA stops responding to the driver. For example:
vmkernel: 6:01:34:46.970 cpu0:4120)ALERT: APIC: 1823: APICID 0×00000000 – ESR = 0×40
The HBA stops responding to commands. For example:
vmkernel: 6:01:42:36.189 cpu15:4274)<6>qla2xxx 0000:1a:00.0: qla2x00_abort_isp: **** FAILED ****
vmkernel: 6:01:47:36.383 cpu14:4274)<4>qla2xxx 0000:1a:00.0: Failed mailbox send register test
The HBA card gets marked offline. For example:
vmkernel: 6:01:47:36.383 cpu14:4274)<4>qla2xxx 0000:1a:00.0: ISP error recovery failed – board disabled
We have created Knowledgebase article 1030265 – HBAs and other PCI devices may stop responding in ESX 4.1 when using IBM servers. This KB article may be updated with new information if it becomes available. Bookmark the KB, or subscribe to its rss feed here to receive updates.

• 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

(Please open the article to see the flash file or player.)

Il n’y a plus qu’à espérer que les SLA soient respectées lorsque nous suivrons cette procédure.

VMware annonce enfin officiellement la couleur à travers un email de « fin de disponibilité »

Dear Valued Customer,

The purpose of this letter is to inform you of our vSphere backup product strategy, ongoing enhancements, and end of availability plans for VMware Consolidated Backup.

VMware Backup Product Strategy
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.

Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP). You can find more information about the use of vStorage APIs for Data Protection in our Developer Community. For information on the availability of VADP integrated release of your backup product please contact your backup vendor.

End of Availability
With the release of the next vSphere platform, we will continue to provide the binaries for VCB, but they will not be compatible with the next platform release. We will continue to provide support for VCB on the current vSphere platform per the VMware support policy.

If you need assistance in the migration from VMware Consolidated Backup to the vStorage APIs for Data Protection, please contact your local reseller or storage backup vendor.

Best regards,
VMware Product Management

Les choses ont au moins le mérite d’être claires maintenant …

• Gold devient Basic (12×5)
• Platinium devient  Production (24×7)

Ces changements « marketing » n’impactent ni les tarifs, ni les prestations associées.

Néanmoins VMware va proposer de nouvelles offres de support prochainement.