One of our own, Michael Roy has just published his first book: Getting Started with VMware Fusion, written to help readers to get started running Windows on their Mac the right way.
Michael talks about how to import your physical PC into the virtual world, and provides practical examples of how to keep your new Virtual Machine secure, backed up, and running smoothly.
Going a bit deeper, he teaches you about snapshots explaining their great uses, and also using Linked Clones in VMware Fusion Professional.
Michael Roy started at VMware working on VMware Fusion version 2 in 2009, where he co-led a world-class global support team, giving customers the help they needed to get the most out of VMware Fusion. He currently specializes in Technical Marketing for Hybrid Cloud Services.
VMware has become aware of an issue that occurs after upgrading to vCloud Networking and Security (vCNS) 5.1.3 in an environment with Cisco Nexus 1000V. The vShield Manager user interface becomes unavailable.
A hot patch fix is available. This does not affect customers with VMware standard or VMware vDS switches.
If you encounter this issue, file a support request with VMware Technical Support and note Knowledge Base article: vShield Manager user interface becomes unavailable after upgrading to 5.1.3 when Cisco Nexus 1000V is present (2073502) in your problem description.
Note: Updates on this issue will be reflected in the aforementioned KB article. To be alerted when this article is updated, click Subscribe to Document in the Actions box on the KB article page.
VMware has become aware of an issue wherein after upgrading to vCloud Connector 2.6, a change to the permissions on the staging directory causes transfers to fail.
A newly installed vCloud Connector node has read/write/execute permissions for user, group, and other on the staging directory (777). When upgrading the node to vCloud Connector 2.6, these permissions are incorrectly set to 755. This removes the write permission for other, which in this instance references the admin user.
For details and updates on this issue refer to KB article: Cannot access the transfer directory after upgrading to vCloud Connector 2.6 (2073208)
Those of you who follow us on Twitter @vmwarecares and @vmwarekb are going to notice a small change. Same goes for our Facebook pages (VMware Knowledge Base and VMware Cares).
In order to better serve our global customer base, we are transitioning the concierge focused vmwarecares responsibilities to our Customer Service team. Some new faces on that team will be responding to your inquires going forward.
The vmwarekb social accounts will still be manned by me, but I will be focusing my efforts on creating more technical content for you IT types and answering your technical questions. In the past I was behind both accounts, and so the lines would sometimes blur between the two.
From now on, if you have a My VMware issue, a problem downloading software, or licensing questions, reach out to @vmwarecares. If you are looking for a KB on <insert topic>, @vmwarekb is your best bet.
See you on the Interwebs!
We got a question this morning on twitter from a customer asking for our best practices for setting up iSCSI storage and vMotion traffic on a VLAN.
The question caused a bit of a discussion here amongst our Tech Support staff and the answer it seems is too long to fit into a Tweet! Instead, here’s what you need to know if you are working on the best design for your VLANS.
iSCSI and vMotion on the same pipe (VLAN) is a big no-no unless you are using multiple teamed 1GbE uplinks or 10GbE uplinks with NIOC to avoid the two stomping on one another.
While vMotion traffic can be turned off/on/reconfigured on the fly, iSCSI traffic does not handle any changes to the underlying network (though great improvements have been made 5.1/5.5) on the fly. You will need to take a maintenance window to reconfigure how you want your VLANs to function – especially for the iSCSI network – and then (more than likely) perform a rolling reboot of all hosts. If iSCSI traffic is already VLAN’d off, you should just leave the iSCSI traffic where it is as to avoid taking down the whole environment and just move the vMotion network to a separate VLAN.
That said, here is our most recent iSCSI Best Practice Setup guide from Cormac Hogan. Also see: vMotion Best Practice Setup guide.
Here are the pertinent pages in our documentation on the subject:
pubs.vmware.com…rking-guide.pdf – Page 187
pubs.vmware.com…orage-guide.pdf – Page 75
Submit support requests and receive troubleshooting alerts with vSphere Web Client
Do you want to shorten the time it takes to submit a support request and upload diagnostic support data to GSS? Do you wish to be notified about latent technical issues in your VMware vSphere environment before they impact your environment so you can spend less time troubleshooting and more time on important business?
If you answered yes to either of these questions, then VMware vCenter Support Assistant 5.5 can help. Support Assistant is a free VMware vCenter Server plug-in available to anyone with VMware support entitlements – regardless of whether that entitlement is via subscription or paid-for incident packs.
This latest release builds on the previous release’s ability to open and manage support requests directly in the vSphere Web Client. vCenter Support Assistant 5.5 introduces new functionality that automates the process of collecting and uploading ESXi and vCenter Server support bundles, and matches this data to a continuously updated list of known customer issues to provide you with proactive alerts and recommended fixes. Furthermore, diagnostic support data is transmitted over either HTTPS or FTP and is sent directly to VMware without going through intermediaries.
To save time and improve your support experience, download vCenter Support Assistant 5.5 for free today!
Download here: http://www.vmware.com/go/download-vcenter-support-assistant
Learn more here: https://www.vmware.com/products/vcenter-support-assistant/overview.html