VCP/VCDX


VCP5: Recertify before March 10, 2015

On October 1st, VMware released a new delta exam to qualify recertification candidates for the VCP5-DCV Certification. The exam is offered to current VCP-DCVs who need to renew their VCP5-DCV credential. The exam will be available through March 10, 2015 (extended!) and offers some key advantages :

  • Based on new material between the vSphere 5.0/5.1 and vSphere 5.5 examens, (you save hours of prep time)
  • Avaiable online (you can take it from any location and don’t have to travel to an exam center)
  • Far less expensive (you save money, the costs are $120)

If you hold a VCP5-DCV certification, this is the quickest route to recertification.

Download the Exam Blueprint

Take advantage of the FREE 1-hr online course VMware vSphere: What’s New Fundamentals of V5.5 to help you prepare for the exam.

If you don’t recertify for VCP5 you have to wait to VCP6-DCV becomes available. You likely need to attend a 5-day course as well before being able to register for the exam.

The exam has 65 questions and you have 75 minutes for the exam. No retake limit other than a 7-day waiting period. Content is vSphere 5.5 specific content. Expect vSan questions. Study, book and do the exam within 48 hours after booking.


Disable ESXi SSH warnings

Today a customer wanted SSH by default on for specific reasons and didn’t like the yellow warning on their ESXi servers. This is how you disable this :

First enable SSH :

ssh001

Go to Security Profile –> SSH –> options and enable it.

Notice that now you have a yellow warning neir your hosts :

ssh002

 

Now this is how you can disable the warning :

ssh003

Go through Advanced Settings –> UsersVars –> SuppressShellWarning and change the value from 0 to 1

Notice the warning sign is gone :

ssh004

You can also use the CLI :

esxcli system settings advanced set -o /UserVars /SuppressShellWarning -i 1

Upgrade Veeam Backup & Replication 5 to 6

 

I’ve been working some time with Veeam Backup & Replication and I’m very pleased about it.
At last I found some time to upgrade my V5 to V6… it took about 2 minutes Smile Hereby the steps for the upgrade :

upgrade001upgrade002

Notice that Veeam already sees the previous installation. Hit Yes to upgrade.

upgrade003upgrade004

It’s very straightforward. Smile

upgrade005upgrade006

Check that the correct paths are displayed.

upgrade007upgrade008

Check the database and the service account. (How long ago did youo change that password? Smile)

upgrade009upgrade010

This settings should be fine if you’ve done a default installation. I did.

upgrade011

Et voila! No more excuses for failed back-up’s! Smile

Update : for more information visit http://www.veeam.com/vmware-esx-backup.html (English) of http://www.veeam.com/nl/vmware-esx-backup.html  (Dutch)


Unable to update to ESXi 4.1 using VC Client Update Manager – “Failed to read the upgrade package metadata.xml”

I ran into some problems usingthe VC Client Update Manager. After checking the .ZIP update file it came with an error.

The solution, download the .ZIP upgrade file, extract it and copy it to your ESXi server using winscp or VC storage browse

Go to the directory where you placed the files and do the manual upgrade to ESXi 4.1 as follows :

Place your ESXi server into maintenance mode;

esxupdate update -m metadata.zip (after that restart your server and check the build level)

You’re al done!


How to enable SSH on ESXi

I install my ESXi servers with a pre-compiled version with ESXi with SSH access already enabled. But for the people who don’t, this is how you enable (unsupported!) SSH access to ESXi.

Logon to the console (you don’t have SSH access, so this is the only option)

Press ALT-F1 and type unsupported (you don’t see what you type) and hit enter.

You will be asked for the root password. Now you can edit using VI (no, nano isn’t there!) the /etc/inetd.conf

Search for #ssh (2 lines) and remove the #. Save the file using :wq and restart the server.

You are al done!


Changing the VLAN ID of a ESX Service Console from the Command Line

This is just a quick note to describe how you can easily change the vlan ID of the service console in ESX.

To remove the vlan id completely, just set it to 0 (in case you have set it by accident on an access port)

esxcfg-vswitch vSwitch0 -v 0 -p “Service Console”

To set a vlan id on the service console (in case you forgot to define this during the installation)

esxcfg-vswitch vSwitch0 -v X -p “Service Console” (enter the vlan number where X is)

Of course make sure to check which vSwitch the Service Console is on (and the name of the Service Console) with esxcfg-vswitch -l


Difference between WWNN and WWPN

I’ve got this question several times from customers, friends, co-workers etc. Suppose now it’s time to make a small blogpost of it. (Also handy for VCP/VCDX exams)

A WWPN (World Wide Port Name) is physically assigned to a part in a Fibre Channel device, such as a FC HBA or SAN. It is the equivalent of the MAC address in the Ethernet protocol as it is supposed to be a unique identifier in the netwok.
The WWN’s are administred by the IEEE like the MAC Address is. The first few octets are assigned to a manafacturer, the rest is arbitrary.

The WWNN (World Wide Node Name) is a World Wide Name assigned to a node in a Fibre Channel fabric. It is valid for the same WWNN to be seen on many different ports on the netwerk.

The WWNN can be regenerated, the WWPN not :

(Screendump of VM properties below)

More info in this (usefull) document : Brocade_NPIV_ESX3.5_WP


VMFS access is slow (unload VMFS-2 & NFS drivers)

When using several VMFS 3 datastores, there is no need to use the VMFS 2 driver. You can unload the driver with the following command :

vmkload_mod -u vmfs2

Also, if you are not using (or planning to use) NFS datastores, you can also unload the NFS driver with the following command :

vmkload_mod -u nfsclient

In my (growing) lab environment the performance improvement was considerably.