VMware Support Insider: Top 10 Support Insider Articles for October

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware Support Insider: Top 10 Support Insider Articles for October
Okt 312012
 

Happy Hallowe’en, readers! As it’s the last day of the month, I thought I’d look back on my personal Gangnam-style parody what posts were popular in October. Not surprisingly, our number one post revolves around the release of Windows 8. Have a look… See anything you missed?

  1. Installing Windows 8 as a guest operating system in VMware Workstation 9.x
  2. Installing the VMware vSphere 5.1 Web Client
  3. Installing Mac OS X 10.7 (Lion) as a virtual machine in VMware Fusion 4
  4. Configuring and Using WSX in VMware Workstation 9
  5. ALERT: vSphere 5.1 is not compatible with any versions of VMware View
  6. vSphere SSO Resources
  7. Installing VMware vCenter Server 5.1 using the Simple Install method
  8. Getting Started Right with vSphere 5.1
  9. Installing or upgrading to ESXi 5.1 best practices
  10. vSphere Client on Windows 7 now supported

IPK statuses are incorrect in the Activity in Previous Period section of the IPK Statistics – IPK Activity report (20350…

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für IPK statuses are incorrect in the Activity in Previous Period section of the IPK Statistics – IPK Activity report (20350…
Okt 312012
 
In the *Activity in Previous Period* section of the *IPK Statistics - IPK Activity* report: · All IPK statuses are shown as... Published: 10/31/12

-- Delivered by Feed43 service

Duplicate Column Value section in the VMware Service Manager 9.x Integration module (2034099)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Duplicate Column Value section in the VMware Service Manager 9.x Integration module (2034099)
Okt 312012
 
In the Integration module of VMware Service Manager 9.x, the Column Values section in the Source Details screen is duplicating. This issue occurs when... Published: 10/31/12

-- Delivered by Feed43 service

In VMware Service Manager, Feedback Comments pop-up in KB Admin does not close (2034499)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für In VMware Service Manager, Feedback Comments pop-up in KB Admin does not close (2034499)
Okt 312012
 
In VMware Service Manager 9.x, when viewing the comments submitted for a Knowledge Base article, the Feedback Comments pop-up cannot be closed by clicking OK. ... Published: 10/31/12

-- Delivered by Feed43 service

Monitors do not automatically refresh after being placed within a dashboard (2010159)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Monitors do not automatically refresh after being placed within a dashboard (2010159)
Okt 312012
 
· Monitors do not auto refresh in the Dashboard · Auto Refresh with Monitors does not work This issue occurs because of the way controls in VMware Service Manager... Published: 10/31/12

-- Delivered by Feed43 service

Windows 8 / Windows Server 2012 Operating System does not boot or install on ESXi or ESX (2006859)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Windows 8 / Windows Server 2012 Operating System does not boot or install on ESXi or ESX (2006859)
Okt 312012
 
· Windows 8 / Windows Server 2012 fails to boot or install on any version of ESXi or ESX · Windows 8 / Windows Server 2012 is not working · You cannot... Published: 10/31/12

-- Delivered by Feed43 service

View Administrator 5.1 shows security servers’ health status as red, with the message: Server certificate cannot be chec…

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für View Administrator 5.1 shows security servers’ health status as red, with the message: Server certificate cannot be chec…
Okt 312012
 
After you install View security servers and pair them with View Connection Server instances, in the View... Published: 10/31/12

-- Delivered by Feed43 service

vSphere 5.1 Web Client reports this SSL warning after an installation or upgrade: Failed to verify the SSL certificate f…

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für vSphere 5.1 Web Client reports this SSL warning after an installation or upgrade: Failed to verify the SSL certificate f…
Okt 312012
 
After installing or upgrading to the vSphere Web Client 5.1, you experience these... Published: 10/31/12

-- Delivered by Feed43 service

Email alert received for Resource Kind: "CIQAdapter Adapter Instance" which is unable to confirm the details from vSpher…

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Email alert received for Resource Kind: "CIQAdapter Adapter Instance" which is unable to confirm the details from vSpher…
Okt 312012
 
In VMware vCenter Operations Manager 5.0.x Standard, you experience... Published: 10/31/12

-- Delivered by Feed43 service

Deploying a ThinApp package in VMware View fails with the error: HRESULT hr = 0x80070050. The file exists. (1027266)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Deploying a ThinApp package in VMware View fails with the error: HRESULT hr = 0x80070050. The file exists. (1027266)
Okt 312012
 
· Unable to deploy a ThinApp package in VMware View  · Deploying a ThinApp package in VMware View  · You see the error: Failed to... Published: 10/31/12

-- Delivered by Feed43 service

Virtual machine powers off while creating or deleting snapshots with the error: Failed to lock the file (1033571)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Virtual machine powers off while creating or deleting snapshots with the error: Failed to lock the file (1033571)
Okt 312012
 
During a Create or Delete Snapshots operation, the virtual machine is abruptly powered off with these symptoms: · The Create or Delete... Published: 10/31/12

-- Delivered by Feed43 service

Port numbers that must be open for Site Recovery Manager and vCenter Server (1009562)

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Port numbers that must be open for Site Recovery Manager and vCenter Server (1009562)
Okt 312012
 
In a VMware Site Recovery Manager (SRM) deployment, both the Protected and Recovery sites must be able to resolve their partner vCenter Server by name. Their... Published: 10/31/12

-- Delivered by Feed43 service

VMware vSphere Blog: vCenter 5.1.0A Readme

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware vSphere Blog: vCenter 5.1.0A Readme
Okt 312012
 

I was involved with a document for the release of vCenter Server 5.1.0A which when released I could not find. It wasn’t until I raised this internally that I found where the document was actually listed. This document is a readme for the vCenter 5.1.0A release and contains information that will help with vCenter Single Sign-On design and installation. I thought I would share it here as more than likely you missed it as well.

For reference the file is located in the notes section of the vCenter 5.1.0A download page and I have linked it here

vCenter Server 5.1.0a README
VMware vCenter Server 5.1.0a has been released in response to bugs and usability issues encountered by VMware customers. A number of these bugs concern installation and upgrade. This release also addresses several other bugs that did not have any workarounds. The goal of vCenter Server 5.1.0a is to provide you with a smoother upgrade path so that you can take advantage of the new features in vCenter Server 5.1 right away.

Upgrade Paths
vCenter Server 5.1.0a is not a patch release. You can upgrade to this version of vCenter Server from the following previous versions:
• vCenter Server 4.1, 4.1 Ux
• vCenter Server 5.0, 5.0 Ux
• vCenter Server 5.1 GA

vCenter Server 5.1.0a supports the same database and OS configurations as the original release of vCenter Server 5.1.

Architectural Changes
The vCenter Server 5.1 release includes significant architectural changes. You must understand these changes before attempting to freshly install or upgrade to vCenter Server 5.1 from older versions of the product. There are four separate services that constitute the vCenter Server 5.1 platform. These are:
• vCenter Single Sign On (SSO)
• vCenter Inventory Service
• vCenter Server
• vSphere Web Client

Upgrade Prerequisites
Before you upgrade to vCenter Server 5.1 determine whether your environment is right for vCenter Server 5.1 by observing the following prerequisites.

- Check your Active Directory (AD) domain settings
• vCenter SSO uses standard LDAP protocols to interact with AD. The machine where SSO is being deployed must have default read-only LDAP privileges (domain member default).
• Read the following Knowledge Base articles (KBs) for detailed prerequisites related to AD.
Upgrading to vCenter Server 5.1 best practices (KB2021193)
Installing vCenter Server 5.1 best practices (KB2021202)
Required ports for vCenter Server 5.1 (KB2031843)

- Check that vCenter Server and Inventory Service Certificates are valid
• Having expired certificates in your environment is a security risk. vCenter SSO checks for certificate validity. You can find details on how to check for expired certificates and renew them in KB2035413.
• For Microsoft Windows deployments, ensure that your certificates meet minimum certificate key-length requirements. Refer to VMware KB2037082 and Microsoft Security Advisory KB2661254.

- Database Configuration
• Know your database user and password quality policies.
• Ensure that SQL Authentication is set to Mixed Mode.
• TCP/IP must be enabled for MS SQL Server.

- Decide on the choice of Basic, HA, or Multi-site installation for SSO
You can find details that will help you decide which type of installation is applicable for your environment by reading the following:
Installing vCenter Single Sign On in a multisite deployment (KB2034074)
Configuring vCenter Single Sign On for High Availability (KB2033588)
• For the basic SSO installation, see the vSphere Installation and Setup Guide

- Knowledge of where your VC administrators live
• Going forward, SSO will be the single point for all user authentications.
• With vCenter Server no longer managing users it is imperative that you understand the source of your users, especially administrators.
• Depending on how you deploy SSO server (on a different machine from vCenter Server), your local OS users might not be migrated to the new environment. If this occurs, you must create new administrative users, preferably local SSO users. If your administrators are AD users, these users will be migrated to SSO provided SSO can find the AD domains.

You can find additional information in the vSphere Installation and Setup Guide and vSphere Upgrade Guide.

Upgrade Strategy
Use a step-by-step approach to installation or upgrade. This approach ensures a smoother upgrade and the ability to revert to a stable state should any problems arise. VMware offers two modes of installation and upgrade for the vCenter Server platform: simple installation and the custom installation.

1. Back up your vCenter Server Database. If you are running vCenter Server in a virtual machine, take a snapshot of the vCenter Server virtual machine.
2. Use the individual installer for each service wherever possible, as opposed to the simple installer. Install SSO first and then upgrade or install the vSphere Web Client.
3. Log into the vSphere Web Client as the SSO administrator (admin@system-domain, ).
4. Verify that you can see all the AD domains for your administrators. If you cannot see some of the AD domains, use the Configuration tab to add them as described in KB2035934.
5. Assign one of the AD users as an SSO administrator. Log out and log back in using the new SSO administrator user. If you are able to connect successfully, SSO is configured correctly.
6. Upgrade vCenter Server, keeping the following in mind:
• Upgrade the Inventory Service before upgrading vCenter Server.
• As a best practice, avoid using local OS users.
• Your configured AD domains must be reachable during vCenter Server upgrades. Refer to KB2035758 for more information.
7. Handle Administrators as follows during vCenter Server upgrade:
• During vCenter Server upgrade, the installer might notify you that administrator permissions are being deleted for users who the installer could not find. This is expected behavior if local OS users were not migrated during SSO installation.
• In where local OS users were the only administrators, the installer prompts you to provide a user or group to which vCenter Server administrator privileges will be assigned. Provide a valid user or group that vCenter Server can recognize. This will be the only user or group granted administrator permissions on vCenter Server. Connect to vCenter Server using this singleton user or any user from the group. After you log into vCenter Server, you can provide administrator access to other users.
• Do not use an administrator from a child domain during setup.

If you want to use the simple installation method, be aware that users and permissions carry over from your old vCenter Server to vCenter Server 5.1 only if SSO and vCenter Server can find the Local OS Users and AD Domains during the upgrade process. If you perform an in-place upgrade and plan to install vCenter Server with SSO and IS on the same machine your existing Local OS users will persist across upgrades.

Release Notes
Be aware of the following caveats when upgrading to vCenter Server 5.1.0a. These caveats have workarounds that you can apply if you encounter problems.

Dynamic Port support in Microsoft SQL Server
Microsoft SQL Server uses dynamic ports by default. SSO requires a fixed port to connect to SQL Server. Refer to the vSphere Installation and Setup Guide to configure SQL Server with static ports. If your datacenter policy requires dynamic ports, you can specify the port number during initial installation of SSO. If the port number may change after SQL server restarts, read KB2033516 to learn about resetting SSO to use the new port. SSO service dependency on MS SQL
When SSO is installed with local Microsoft SQL Server, the services must start in a specific order. SSO must start after SQL Server starts. If SSO starts before SQL Server starts, restart the SSO server after SQL server starts.

Non-standard UPN
Authentication fails with nonstandard UPN using Windows authentication from the vSphere Web
Client or the vSphere Client. Use the original domain name when connecting to the vCenter
Server platform and authenticate with a valid user name and password. This issue impacts
customers who use smart cards to log into either client and who also use nonstandard UPN.

Short File Names
Ensure that short filenames are enabled on your Windows operating system before creating the
folder where you plan to install SSO. If you do not, SSO installation will fail.

vSphere Web Client might appear inaccessible or plugin modules might not be visible in
the vSphere Web Client

After updating the vCenter Server Appliance to 5.1.0a, the appliance does not prompt for reboot
or automatically reboot. When the vSphere Web Client is later updated with a newer version of a
vCenter Server plug-in module found on vCenter Server, the vSphere Web Client might appear
inaccessible or the new plug-in might not be visible in the vSphere Web Client. After updating the
vCenter Server Appliance or a vSphere Web Client plug-in, reboot the vCenter Server Appliance
to complete the process.

VMware vFabric Blog: Join us at the Cloud Computing Expo in Santa Clara

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware vFabric Blog: Join us at the Cloud Computing Expo in Santa Clara
Okt 312012
 

Join at the upcoming Cloud Expo in Santa Clara, CA on November 5-8.

Recent IDC research shows that worldwide spending on cloud services will grow almost threefold, reaching $44.2 billion by 2013. And a recent Gartner report predicts that the volume of enterprise data overall will increase by a phenomenal 650% over the next five years.

These two enterprise IT trends, Cloud Computing and Big Data, will converge at the 11th Cloud Expo – at the Santa Clara Convention Center. There are 200+ technical sessions covering everything from infrastructure to platforms to applications.

How to find us at the Show

1. Of course, we will have a booth (#209) – come see demonstrations of:

  • Infrastructure – vCloud Director, vCenter Chargeback Manager, vCloud Connect, and the Software Defined Data Center
  • Operations – vCenter Operations, DynamicOps, vShield, and vSphere
  • Cloud Application Platform/PaaS – vFabric, Data Director, Application Director, SQLFire, GemFire, Business Critical Applications Services, and Cetas/Big Data
  • End User Computing – View, Horizon, Socialcast

2. There are two technical sessions we will be presenting:

3. We have a General Session on November 7th from 1:35 – 2:05PM

We look forward to seeing you there!

VMware vCloud Blog: vCloud Director 5.1 VXLAN Configuration

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware vCloud Blog: vCloud Director 5.1 VXLAN Configuration
Okt 312012
 

By: Rawlinson Rivera, Senior Technical Marketing Manager at VMware

This is a repost from Rawlinson’s personal blog, Punching Clouds

The new vCloud Director 5.1 delivers many new features and enhancements, one in particular is the introduction and support of Virtual Extensible LAN (VXLAN). VXLAN is a technology that enables the expansion of isolated vCloud architectures across layer 2 domains beyond the limits imposed by the IEEE 802.1Q standard. By utilizing a new MAC-in-UDP encapsulation technique, a VXLAN ID adds a 24 bit identifier, which allows networks to push beyond the IEEE 802.1Q limit to a possible 16 million logical networks. Figure 1 below illustrates the changes added to the Ethernet frame by VXLAN.

Figure 1: Ethernet Frame with VXLAN Encapsulation

While the conventional IEEE 802.1Q standard works perfectly, when trying to meet greater scalability demands VXLAN surpasses the IEEE 802.1Q limitation by offering scalable capabilities of up to 16 million possible networks. Because of the scalable and flexible capabilities offered by VXLAN, this technology is something to be consider for large scalable Cloud (vCloud) networks. For a quick crash course on VXLAN, take a look at Duncan Epping’s post “Understanding VXLAN and the value prop in just 4 Minutes…”

Configuring VXLAN in vCloud Director 5.1 required some initial steps that are outside of the vCloud Director 5.1 management interface which I want to illustrate here.

First a couple of facts:

A VXLAN network pool is automatically created in vCloud Director 5.1 whenever a Provider vDC is created. If the hosts of any given cluster are not prepared to use VXLAN first, the VXLAN network Pool in vCloud Director will display an error. I would recommend identifying all of the pre-requisites for the use of VXLAN from a network as well as the software dependency perspective before creating new Provider vDC in vCloud Director 5.1.

In order to prepare the resource clusters (hosts) to use VXLAN, log in the vCloud Networking and Security appliance (previously knows as vShield Manager). The preparation of the networks as well as the hosts requires the identification and assignment of the Segment ID Pool and the Multicast addresses. Below are the steps necessary to prepare and configure VXLAN for vCloud Director 5.1.

Step 1: Log into the vCloud Networking and Security appliance. Select the Datacenter. Then, select the Network Virtualization tab on the right side of the screen and click the Preparation hyperlink. This will reveal the Connectivity and Segment ID screen, as illustrated in figure 2.

Figure 2: Network Virtualization Settings

Step 2: Click the Edit button on the right end of the screen, and enter the required Segment ID Pool, and Multicast address that will be used by vCloud Networking and Security appliance. The Segment ID’s cannot be mapped directly to any one Multicast Address, as the possibility of one-to-one mapping doesn’t exist. This Segment ID and Multicast Address configuration is defined in ranges. Figure 3 illustrates the Segment ID and Multicast Address options.

Figure 3: Segment ID Pool and Multicast Address

Step 3: Click on the Connectivity button in the Network Virtualization tab to prepare the resource clusters (hosts) to be part of the VXLAN with vCloud Director. Choose the Distributed switch that is to be associated with the resource cluster, and enter the VLAN ID for the desired network segment that will be used to overlay the VXLAN traffic coming from the Distributed Switches. Figure 4 illustrates the configuration options.

Figure 4: Resource Cluster

Step 4: Specify the NIC teaming policy that applies to the respective Distributed Switch configuration, and the MTU settings. The MTU settings for VXLAN default to 1600 bytes due to the VXLAN ID encapsulation technique which increases the size of the packets. This behavior is similar for the configuration of vCDNI in vCloud Director.  vCDNI required the minimum MTU packet configuration of 1524. Overall, the important thing to understand here is the requirement to use jumbo frames across all network devices. Figure 5 illustrates the NIC teaming policies available as well as the default MTU settings and click Finish.

Figure 5: VXLAN Attributes

After choosing and completing the specification for the Distributed Switches, the VXLAN vmkernel modules are pushed and enabled on to all of the hosts that are part of the selected cluster. New dvPort Groups and vmknic interfaces are added and automatically created on the Distributed Switch associated to the VXLAN. The new dvPort group can be identified by the unique naming convention vxw-vmknicPg-dvs-xx-xx-xx-xx. Figure 6 offers an example of the adapter configuration.

Figure 6: VXLAN VMkernel Interfaces

A troublesome results of the automated network configuration process for the vmknics, is that all interfaces will be automatically assigned an IP address based on DHCP. This behavior can become a configuration management issue; unless there is a DHCP server on that network segment (normally the management network), all of the newly created interfaces will receive an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical link.

This configuration will not work as an IPv4 local addresses are not suitable for communication with devices not directly connected to the same physical or logical link, and are only used where stable, routable addresses are not available. As a result of this configuration the status of the hosts preparation will be displayed as “Not ready” in the vCloud Networking and Security appliance interface. Figure 7 illustrates the issue discussed above.

Figure 7: vmknics IP Address Status

The solution to this issue is simple: update the vmknics interface with automatically assigned IP with valid addresses. This can be achieved in a manual or automated format. Figure 8 illustrate the results of a successful configuration.

Figure 8: VXLAN Successful Preparation Results

Step 5: At this point, all the required network, and hosts preparation for the use of VXLAN with vCloud Director 5.1 have been completed. In order to start using the VXLAN feature in vCloud Director 5.1,  create a Provider vDC.  A VXLAN Pool is automatically created. Figure 9 illustrates the existence of VXLAN capable network pool in the management interface of vCloud Director.

Figure 9: VXLAN Network Pool in vCloud Director 5.1

There you have it, folks. You can now proceed with the creation and configuration of Organization, and vApp networks to harness the scalable features delivered by VXLAN in vCloud Director 5.1 infrastructures.

Enjoy!

Rawlinson is a Senior Technical Marketing Manager in the Cloud Infrastructure Technical Marketing Group at VMware, focused on Storage Virtualization technologies. Previously he was an architect focused on Cloud and vSphere enterprise architectures for VMware fortune 100, 500 customers. Rawlinson is amongst the first VMware Certified Design Experts (VCDX#86), author of multiple books and a retired Professional Skater.