Eric Sloof - NTPRO.NL

NFS is a great storage solution within a VMware vSphere environment but when the connection to the NFS server is lost, you’re in big trouble. In most circumstances some virtual machines are still connected to the NFS Datastore and since it’s in use, you cannot delete and recreate it. I’ve tried this by using the vSphere Client and trough the command line but didn’t succeed. In the end there’s no other alternative than rebooting the ESX host, or is there… If you want to find out how to remount an NFS Datastore you better watch this online training.

http://www.screencast.com/users/esloof/folders/Online-Training

You also have the ability to embed or link to it at Vimeo.

It's really a rough unprepared video but in the end you'll get the picture

This morning I had a nice email discussion with a fellow VCI who has attended my online VLAN training. His question had to do with the VLAN IDs that need to be configured at the physical Cisco switch. Do you only  need to configure the primary or do you also need to configure the secondary and isolated VLAN IDs?

Hi Eric, when you configure PVLAN, the Switch itself should configured with ONLY the PRIMARY VLAN not the whole range of Primary / secondary… doing so could be a security issue… Could you check at your  side that using 23-23 instead of 23-26 at timecode 31:07 in your movie, don't change the behaviour or the communications between VMs?

After applying 23-23 of both port 2 and 3 at the Cisco switch, virtual machines within both the communities cannot connect to the router and to each other. After  putting in 23-25, the virtual machines in community 2 (26) could not ping each other and in community 1 (25) can.

I knew I’ve seen it somewhere -> Community and Isolated PVLANs traffic travels tagged as the associated Secondary PVLAN. At the bottom of this KB article.

•Promiscuous PVLANs have the same VLAN ID both for Primary and Secondary VLAN.
•Community and Isolated PVLANs traffic travels tagged as the associated Secondary PVLAN.
•Traffic inside PVLANs is not encapsulated (no Secondary PVLAN encapsulated inside a Primary PVLAN Packet).
•Traffic between virtual machines on the same PVLAN but on different ESX hosts go through the Physical Switch. Therefore, the Physical Switch must be PVLAN aware and configured appropriately, to allow the secondary PVLANs to reach destination.
•Switches discover MAC addresses per VLAN. This can be a problem for PVLANs because each virtual machine appears to the physical switch to be in more than one VLAN, or at least, it appears that there is no reply to the request, because the reply travels back in a different VLAN. For this reason, it is a requirement that each physical switch, where ESX with PVLANs are connected, must be PVLAN aware.

During the delivery of VMware Training Courses, I’ve noticed students who are really  interested in how to configure the Cisco Switch in order to use  Private VLAN IDs. This session will show you how to configure dvPortGroup Settings and Private VLANs on a Distributed Virtual Switch and on a Physical Cisco Switch.

• This presentation will lead you trough configuring VLAN IDs at both the vSphere environment and on the physical Cisco switch.

• You’ll get a good understanding of trunking on a Cisco switch and dvPortGroup Settings.

• At the end you’re able to configure a Cisco switch using Cisco’s Network Assistant and understand the different dvPortGroup Settings.

The online training will take around 40 minutes, you can view it here: http://itunes.apple.com/nl/podcast/online-vmware-training/id415180540

You also have the ability to download the complete “Configure VMware vSphere Private VLANS” training, or embed and link to it on Vimeo.

Some of the feedback I’ve received after the initial launch of the vmClient 4.0 a few weeks ago had to do with creating a list of frequently used virtual machines. A lot of people are using the vmClient as a helpdesk app and don’t want to give out the full blown viClient for accessing the virtual machine desktop by their helpdesk staff. The new favourites menu item enables you to create a list with virtual machines. After creating a list through the registry or by adding and removing virtual machines from within the vmClient it’s possible to customize the user interface and hide the obsolete menus. I recorded a demo session with my newly bought Camtasia software.

Here’s the download link for vmClient 4.1 Beta: http://vmClient.nl

Here’s the online demo: http://www.screencast.com/users/esloof/folders/Online-Training

I've stumbled upon a great presentation created by Nicholas Travers who works as a VMware Technology Consultant at EMC.  The presentation is called "Storage Protocol Choices & Storage Best Practices for VMware ESX" and deals with storage considerations like:

• How many VMs per LUN?
• Standard LUN Size?
• NFS, RDM or VMFS?
• iSCSI, or FC?
• How do I scale iSCSI and NFS?
• Queue Depths?
• I need a 3TB LUN... How?
• Why do I need multi-pathing?
• I need SRM support... How?

The presentation can be downloaded from: Storage Protocol Choices & Storage Best Practices for VMware ESX

Mike Laverick has released his newest book “Administering VMware Site Recovery Manager 4.0” and you don’t have to pay for it, well it would be a great if you donate at least 10$ to Unisef.

This book will teach you how to install and configure VMware’s Site Recovery Manager product. It also covers in detail the failover and failback processes and Mike will guide you step-by-step through the setup of the product. This book in not filled with project management padding that typifies a lot of IT books. It’s practical and technical, and assumes you are already pretty familiar with VMware vSphere4. In This book you will learn the strengths and weaknesses of Site recovery Manager, and Mike will show you the common pitfalls and errors that can happen, and also more importantly why they happen, and how to fix them.

There are a lot of automation tools available which are able to deploy and configure an ESX host but if you want to use PowerCLI for the finishing configuration part there was always a manual step involved. I’ve found a way to start a PowerShell script from the service console trough SSH. The only thing you have to do is install WinSSHD on one of your Windows servers, just execute the distributable that you downloaded from the Bitvise website and follow the process. As soon as the installer completes, you will have a working WinSSHD installation on your machine. No changes to the default configuration are necessary; you only need to start it. However, you might want restrict your users' access to those features that they actually need, which will improve security. If you are new to WinSSHD, it’s highly recommended that you first make sure that you can establish a working SSH connection before you change any settings on the server. If you cannot connect to WinSSHD using its default configuration, this is most likely due to a network or firewall problem that you will need to resolve before you are able to connect. In its default configuration, WinSSHD accepts connections on the well-known port number for SSH servers, 22.

I’ve recorded a Jing video (with audio) which demos the CPU-Ready PowerCLI script running on my vCenter server launched from one of my ESX host’s service console.

Several months ago one of my students (Jan-Peter Klijn) showed me a real nifty application called QlikView, it’s a program that makes it possible to retrieve and assimilate data from different sources. Once loaded into the program, the data is presented in a way that is easy to understand and work with. To make selections in QlikView, you don’t need any previous knowledge of databases or search routines: you simply click on the item of which you want to know more. The clicked item turns green, and the program immediately presents all the items associated with the selected one. Graphics and tables can be created to get an even better overview of data. Any graphic or table can be printed or exported to other programs.

I’ve managed to connect QlikView with the vCenter database and within minutes, I was able to create some great “Real Time” reports. I’ve created a Jing movie which demos the configuration and report creation. QlikView is free for personal use, you can get it here.

Continue reading "Data Mining the vCenter Database with QlikView" »

It’s possible to configure the ESX host's virtual switches so the Cisco Discovery Protocol on a standard or distributed switch is issuing broadcasts containing some of your ESX host's information. After enabling the CDP on your ESX server, the Cisco administrator is able to listen for information broadcasted by your ESX host but what can he actually see? To find out I’ve installed the Tallsoft’s Cisco CDP Monitor on my vCenter server.

With Cisco CDP Monitor, you can display the information of the connecting Cisco devices, such as device names, device models, connecting port , administrative ip address, IOS version, VTP Domain Name, and so on. With this information, one could easily learn the total topology of the complete network and do troubleshooting. Once the Cisco Discovery Protocol information changes (such as the link or device failed, or the setup of Cisco device changed), Cisco CDP Monitor will detect it and will display the related info. It also shows information broadcasted by you ESX servers.

Virtual switches can be configured for four different CDP modes of operation:

Down – CDP information is neither sent nor received
Listen – CDP information is received from the physical switches
Advertise – CDP information is sent to the physical switches
Both – CDP information is sent to and received from the physical switches

For enabling CDP on standard switches you have to use command-line interface. CDP can be enabled on distributed switches using the vSphere Client. Here’s the info I was able to retrieve from an ESX host after running  “esxcfg-vswitch -B both vSwitch0” in the service console.

Neigbour1:
device id: esx4-l.ntpro.local
ipaddress: 0.0.0.0
port: vmnic0
capabilities: Switch  
ios_version: Releasebuild-208167
platform: VMware ESX
prefix: 
vtp_domain: 
native_vlan: 
duplex: full

This is a song by Varrowinc told in first person from the perspective of a physical server that has been virtualized by vSphere. This was done on an iPhone with I am T-pain App.

VMware ThinApp delivers the following new capabilities:

Windows 7 support – This expanded platform support allows for applications of older Windows OS’s to be packaged and deployed on Windows 7 allowing for greater compatibility support of legacy applications.

Relink – Applications packaged using previous versions of ThinApp can be updated to the new ThinApp 4.5 format without the need of associated project files for application. This command line utility helps to speed upgrade process of existing ThinApp packages.

Performance Accelerator – Reduced page file usage for virtual applications and increased memory sharing between multiple instances of applications allows for quicker application invocation and improved application delivery to end users. This helps to improve user experience, at the same time reduces network bandwidth consumption.

Registry Transaction Protection - Ensure registry file integrity and eliminate potential data corruption due to crash or system failure.

ThinApp SDK - Published APIs to allow for integration of ThinApp with third party software.

ThinApp Community Portal - Users can upload application instructions and share with the community.

Enhanced Supportability - Customers have option to share packaging results with VMware for better support…

http://www.vmware.com/products/thinapp/

VMware will also offer a one day ThinApp  training course in the near future, this course will equip applications-oriented administrators with the knowledge and skills to virtualize Windows applications with VMware ThinApp, modify the package.ini parameters to handle special circumstances, and choose the best deployment and updating processes for their environment.

Application Virtualization with VMware ThinApp - Beta

VMware will shortly announce advanced Certification to follow on from VCP. There will be new Enterprise and Design level Certifications.  I cannot disclose the names of the new Certification tracks but look out for external, communication from VMware this month.  I can tell you I would be very proud to hold one of these titles.

Arne Fokkema over at ict-freak.nl just tweeted about the availability of Workstation 7.1 beta. You can get your copy here: http://communities.vmware.com/community/beta/ws?view=overview

The VMware Workstation 7.1 Beta includes several new features and hundreds of minor improvements. Some release highlights include:

•OpenGL 2.1 support for Windows 7 and Vista guests: The addition of hardware accelerated OpenGL 2.1 support to the WDDM driver enables many more graphics applications to run inside of your virtual machines.
•Improved graphics performance: Significant enhancements have been made to the VMware WDDM driver that have produced benchmark results that are up to 80% faster. The updated driver also produces smoother video playback and addresses many reported rendering issues. Of course games run better as well!
•8-way SMP support plus virtual disks up to 2TB in size: The virtual hardware continues to become more powerful to meet the needs of Workstation customers who are running server class applications.
•OVF 1.0 support: Including the OVF Tool with this release enables users to easily import or export virtual machines and vApps and move them to vSphere or up into the cloud.•Direct Launch: Blur the distinction between running native and virtual applications by launching an application installed in a virtual machine directly from the start menu or taskbar of the host system.
•Automatic software updates: These VMware applications can now detect when a new version is released and are able to update at the click of a button.
•Fedora 12 virtual machines: We are excited about finally offering support for running one of the most popular Linux distributions on the planet!