Category Archives: VMware - Page 2

Being a vExpert is a great motivation booster!

Returning from a month long Euro Trip a few weeks back I had been struggling to get back into work mode. So it was a huge motivation boost to receive an email earlier this week welcoming me to the VMware vExpert Program as a 2015 vExpert. I’m thrilled to have been recognised along with a lot of other amazing people.

My history with VMware products goes back to the Virtual Infrastructure and ESX Server 3 days. I still remember my scepticism when my manager said we’re going to migrate to this virtualisation stuff. Over the last few years VMware and Virtualisation have become a crucial part of my role in the Cloud & Managed Services department of Optus Business in Australia.

I’m really looking forward to engaging ever more with the virtualisation community throughout the remainder of the year and into next.

The 2015 second half intake of vExperts can be found here.

and the full list here.

Enable SSH on vCenter Server Appliance 6 (VCSA)

Posted by Mark Ukotic on June 14, 2015 2 comments

If you’re running the Appliance version of vCenter 6 at some stage you may want console access via SSH. When you install VCSA 6 for the first time you have the option during installation to enable SSH. Depending on your security stance you may have left SSH off and now you want it on.

There are a few different methods for enabling SSH on VCSA. The below two methods both use the web client.

Method 1.
Directly enabling SSH in the Web Client.

This method is probably the easiest and quickest way. The settings just happen to be in a non-intuitive location.

On the Home screen of the Web Client select Administration -> System Configuration

Select Nodes and right click on your vCenter server.

Select Edit Settings

Select the Checkbox Enable SSH login

Click OK.

You should now be able to SSH to the vCenter name or IP.

Method 2.
Enabling SSH via the Remote Console.

Navigate to your vCenter Appliance VM. Click on Launch Remote Console.

Press ALT + F1 to get a login TTY session and login as root

Run the below commands to enable SSH. ssh.get shows the current status. ssh.set allows you to change the state of SSH. Use ‘false’ instead of true to disable SSH.

Command> ssh.get
Enabled: False
Command> ssh.set --enabled true
Command> ssh.get
Enabled: True
Command>

The above methods takes effect immediately, no need to reboot. When disabling SSH, current sessions stay active and don’t end. So if someone has an open SSH session they won’t be kicked out until they logoff or their session times out.

References

VMware vCenter 6 Documentation
Edit Access Settings to the vCenter Server Appliance

No vmkcore disk partition is available

Posted by Mark Ukotic on May 31, 2015 5 comments

Sometimes I really do feel the computer gremlins are out to get me. As long as I can remember I’ve had a flawlessly running Test Lab at work. The day of my scheduled ESXi host upgrades I come across numerous hosts with the below error.

No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.

I tried to ignore the error but VMware Update Manager would have no bar of it and prevented me from performing an ESXi version upgrade.

The error is referring to the location ESXi will dump its core during a Purple Screen of Death (PSOD). Usually you’ll see this warning with a statless configured ESXi host. In this situation a host will be running in memory with no disk. You will usually configure the vSphere Network Dump Collector service. This wasn’t the case in my situation.

Logging into the Shell I ran the follow

~ # esxcli system coredump partition list

no configured dump partition found; skipping

Next I attempted to set the coredump

~ # esxcli system coredump partition set --enable true --smart

Unable to smart activate a dump partition. Error was: Not a known device: naa.6000097000024659483748380304235.

Not really sure what was going on here. I just hope no one was messing with LUN mappings.

So next I use the set -u to unconfigure any current core dump follow by set --enable true --smart which allows ESXi to automatically determine the best location to set.

~ # esxcli system coredump partition set -u

~ # esxcli system coredump partition set --enable true --smart

~ # esxcli system coredump partition get

Active: naa.600601600fc04857394578c4d945e311:7

Configured: naa.600601600fc04857394578c4d945e311:7

This resolved the error immediately without any reboots and allowed me to continue with ESXi host upgrades.

I don’t know the root cause to this issue but as I’m upgrading ESXi versions I think it’s okay to sometimes let things go.

Note; --enable true --smart contains double dashes.

Modifying vCenter Server Appliance 6 (VCSA) NTP settings

Posted by Mark Ukotic on March 23, 2015 8 comments

For some unknown reason that I’m yet to learn. The VAMI in vCenter Server Appliance 6 has been removed. VAMI is the management interface that you usually connect to on port 5480 for most VMware appliances. Prior to vCenter 6 you could connect to your VCSA appliance on port 5480. In the VAMI you could check that status of the appliance services, change its network settings, perform updates, and change NTP settings.

It’s this last setting that quickly alerted me to this change shortly after deploying my first VCSA 6. During the initial deployment of my vCenter Appliance I would specify my NTP servers when prompted. During my first two attempts the deployment would error out and fail because my NTP time sources specified were timing out. So on the third attempt I decided to skip the NTP servers and configure them post install.

Here in lies the new way of modifying NTP settings on a vCenter 6 Appliance.

Firstly we need to log into the appliance via SSH or via the console using the root account.

We will be presented with a VMware shell with instructions on how to enable BASH. For this task and many other vCenter tasks the current shell is good enough. From here we can run our NTP commands. If we type ntp followed by the ‘TAB’ key we get a list of ntp commands we can run.

Typing ntp.get lists the current status of NTP and what NTP servers are configured. In this case the status is Down and no servers have been configured.

Command> ntp.get
Config:
Status: Down
Servers:
Command>

As we have no NTP servers listed we can use the ntp.server.set command. This will override any current servers that may also be listed.

Command> ntp.server.set --servers 0.au.pool.ntp.org
Command> ntp.get
Config:
Status: Down
Servers: 0.au.pool.ntp.org
Command>

We now have one NTP time source set. If we wish to make modifications to the list of servers without overriding them we can use the ntp.server.add command.

Command> ntp.server.add --servers 1.au.pool.ntp.org
Command> ntp.get
Config:
Status: Down
Servers: 0.au.pool.ntp.org 1.au.pool.ntp.org
Command>

With our NTP time sources set we now enable and start NTP using the command timesync

Command> timesync.set --mode NTP
Command> timesync.get
Config:
Mode: NTP

Command> ntp.get
Config:
Status: Up
Servers: 0.au.pool.ntp.org 1.au.pool.ntp.org

And that’s really all that is required. Relatively straight forward to perform. From my point of view it’s certainly not as convenient as using the VAMI web portal from previous versions. As mentioned above. I don’t know why it was removed. Perhaps time constraints meant that it will be introduced in a future update. Or perhaps it’s just hidden on a different port I’m not aware of. In any case it would be nice to officially know.

Note; ‘--servers’ above is a double dash.

References

Add or Replace NTP Servers in the vCenter Server Appliance Configuration

VCP5-DCV Delta done and dusted

Posted by Mark Ukotic on October 21, 2014 No comments

Over the weekend logic and common sense failed me and I decided to sit my VCP5-DCV Delta Exam. Since VMware introduced a recertification policy back in March 2014 I’ve been buying my time to renew. My deadline was approaching and with the limited time offer to sit a Delta exam recertification I jumped on it.

To date I’ve seen nothing out there on user experiences taking the Delta exam, though, it’s only been three weeks since the VCP5-DCV Delta exam has been available. So unfortunately taking this exam would be unchartered waters. I’ve been psyching myself up all week so that wasn’t going to phase me 🙂

I had my plan ready for first thing Saturday morning. I would fire up the vSphere environment on my new NUC test lab. Download all the PDFs in the VCP5-DCV Delta Blueprint. Then cram like I’ve never crammed before over 48 hours and take the exam Sunday night.

Step 1 was Requesting Authorization on the VMware MyLearn site. I had already performed this earlier on in the week and was authorized the same day, my authorization was valid for 10 years, I guess just in case I became a little busy. Step 2 was booking for the VCP550D exam on the Pearsons website first thing Saturday morning. There’s nothing like preparing for an exam than knowing you’ve already paid to take it. The exam cost was $130 AUD ($120 USD).

Next I downloaded and studied the Blueprint. 65 questions over 75 minutes, that’s 1 minute 15 seconds per a question. Vmware are notorious for pushing time limits in exams 🙁 The MyLearn site states that only new material between vSphere 5.0/5.1 and vSphere 5.5 would be on the exam yet the blueprint contained everything that would be in a full VCP exam. This made study a little difficult. I wasn’t going to study everything obviously. So I took advantage of the FREE 1-hr online course -VMware vSphere: What’s New Fundamentals of V5.5 to help prepare for the exam. I used that has the basis of what I needed to study. The online course was a good starting point of where to start the deep dives into the PDFs. What I found was absent in the video, but clearly mentioned on the blueprint, was vCOPs and vSAN. Something to keep in mind.

Next came the mind numbingly hard part of reading the PDFs. I focused heavily on some of the new guides, In particular, the Replication guide, Data Protection, and Storage. By Sunday afternoon (after a day and half of reading) I had covered most of the material in the PDFs. The only exception being the three vCOPS PDFs totalling 400 pages which I refused to read!

Next came taking a few practice exams off the VMware MyLearn site. I knew the questions would be broader than the Delta exam so I just focused on the new 5.5 material.

As the end of Sunday approached it was time to take the exam. Now If it’s not clear by this point, this is an online exam. For the people that don’t know what that means. It is an open book exam! Now I don’t want hate messages. It’s an open book exam!

So this is where my three monitors got put to good use. Monitor 1, the exam window. Monitor 2, Google. Monitor 3, the Advanced Search function of Adobe Reader set to search all PDFs in the Blueprint folder.

Now if you’ve read this far, plain and simply, I’m not going to give you the answers. I feel, though, based on my experience I can comfortably recommend what you need to be studying. So know your vSAN, know your vFlash, know your VDP, and know Replication. It felt like the lower end of 50% -- 75% was this new material and the rest was standard VCP knowledge material that we should all know. Looking at the exam at a high level it’s set in the format of a traditional VCP exam. So if you can remember back to your last one expect the same types of questions worded the same way.

Where I felt I was weak on and would also recommend. Know your vSphere Editions and high level vCOPs 😉 If you’ve done your VCA-DCV certification you’ll been fine with that knowledge for vCOPs. Just focus on your knowledge of what Badges are and what they are comprised of.

So now long story short I am recertified for another 728 days.

As an open disclaimer I’ve been using vSphere 5.5 since day one of release. I’ve been closely following all the new technologies that have been accompanying vSphere 5.5. Keep that in mind before you say this was a paper certification.

References

Recertification Policy

VCP5-DCV Delta recertification exam

Pearsons VMware exam registration site

Configuring and Testing NTP on ESXi

Posted by Mark Ukotic on September 11, 2014 1 comment

I hate NTP. I hate time sync issues. I hate time skew issues on ESXi.

So now that I’ve got that out I feel a whole lot better. I can now talk about how to configure and importantly validate your NTP settings on an ESXi host.

Setting and syncing time on an ESXi host is done within Time Configuration on the Settings tab of an ESXi host.

The time can either be set manually or it can be set via NTP. Setting the time manually is self explanatory. Basically change your time and click OK. It’s not something I’m going to go into any further. Ideally, though, you want to be setting your time with NTP. Using NTP is relatively easy too, the hardest part will be making sure you have the correct ports open on all parts of the network. NTP generally uses UDP port 123 btw.

timesync03

So firstly you want to select Use Network Time Protocol. You next want to head over to http://www.pool.ntp.org and find your closest NTP time sources. Understanding how the underlying technology of how NTP works is actually quite interesting but beyond what this post is about. Wikipedia is a good start on NTP. Each region around the world has a number of NTP pools and within those regions many countries have pools of their own. For me my closest pool is Australia within the Oceania region. Australia has 4 pools. Within these pools are actually a number of servers. I can use one of these pools or I can use them all. I’ll be using them all for redundancy. Once I enter these pool addresses and separate them with commas I click the Start button and click OK.

timesync04

The Time Configuration should now look something similar to below. The time change in not instant and can take… well… time.

timesync05

But how do you test that these settings are correct, considering that the time sync process is not instant. Further more, NTP uses UDP port 123 which is connectionless. Well, we can query the output our NTP sources gives us, which can be done from the CLI of the ESXi host.

Log into the console of the ESXi host using whatever method you prefer. The simplest is usually just starting and connecting to SSH.

We use the NTPQ command and type the following.

ntpq -p localhost

The output should be sometime similar to below. VMware have a good KB article which explains what it all means if your really want to know.

timesync06

If we see something similar we know we’re good and the time should start to change shortly. If we get all zeros we probably have network and DNS working but NTP is block at the firewall somewhere.

My VCA experience

Posted by Mark Ukotic on December 7, 2013 No comments

When a friend sent me a link to the offical VMware Certified Associate (VCA) site shortly after release I have to admit I wasn’t too impressed. I think my official response back to him was ‘meh’. You had this exam track that you could take online, at home. What challenge is that?!? It looked like a cert targeted at the virtualization sales consultant. But then came October and I strangely changed my opinion. VMware had a few offers on table, when combined, allowed you to sit the exam for free. How could you refuse!

I heard about the offers mid October and was already in the middle of unrelated study with some tight deadlines. Never the less on the following quiet Friday after work I sat down and read through the blueprint of the VCA -- Data Center Virtualization exam. It all looked very straight-forward. Watch a 2.5 hour training course and a handful of short PDF {marketing} documents. I think I got about 20 minutes into the fundamentals training video and skipped to the end. The plan prior was to study and take the exam on Sunday. Being free, though, I thought what the hell and just sat the exam right there and then. 75 minutes and 50 questions to answer. It took me 35-40 minutes to complete the exam. I scored somewhere around 430. There was some satisfaction but I was really searching for it. The questions held no real technical depth. It was really more around knowing the concepts and basic vSphere terminology.

So confident I was, a few days later (Sunday), I sat the VCA Cloud exam. Out of the three Certification tracks VMware have, Cloud is no doubt my weakest one. Never the less I applied my same logic from the VCA-DCV --It’s a free exam and I can always take it again. A few questions into the exam and I new I was in trouble. Against better judgement I opened up a browser window and started searching for answers. Great, I was starting to find the answers now. But time was against me. I couldn’t find the answers fast enough. I finished the exam with 5 minutes left and wasn’t feeling confident. I failed with a 298. What are the odds that I failed by 2 points. Pretty good if you search the net. People always fail by 1, 2, or 3 points.

Feeling embarrassed I went to bed to rethink my VCA-Cloud tactics. The following Friday night I pulled up the Cloud blueprint. Took the 3 hour course video and read through the PDF documents referenced in the blueprint. Saturday morning, I woke up, opened up a browser full of tabs on VMware Cloud material and sat the exam. This time the answers came much easier to me. With no need to reference any online material, bar one question, I completed the exam in 40 minutes with a score of 485. With a little more satisfaction and much needed vindication I tried to find some pride in the score. Not bad for one nights study. Though we’ll ignore the fact that more than half the questions were the same as my first attempt.

Time was against me in the month of October and I wasn’t able to sit the third VCA-WM end user (Desktop) exam. The multiple discount codes to sit the VCA exams for free have now ended. One VMware offer still exists till the end of the year to sit the exams for half price. Normally $120 US you can sit it for $60. I have to admit my interest to pay (only) $60 to sit a VCA isn’t really there. My only motivation is really to just get that Hat-Trick.

In a recent VMware Communities Roundtable podcast with John Arrasjid (@vcdx001), they spoke about the VCA track. It was an interesting podcast that helped answer a lot of questions I had around the VCA track. They spoke about the objective of the VCA track. Its intended target audience. Why it was chosen to be an ‘Open Book’ exam. Oddly it didn’t even occur to me that it was expect you would search for the answers online during the exam.

While my criticism of the VCA track has somewhat diminished I still have my doubts on it’s validity in the community. I was a little worried about being so negative in the post. But the truth is these are just my opinions and I just needed to get it out there.

Installing NetApp NFS Plug-in for VMware VAAI

Posted by Mark Ukotic on December 1, 2013 No comments

For some time now NetApp have supported VAAI for NFS on vSphere. If you’re using NFS on your NetApp with vSphere you might want to investigate installing the NFS Plug-in for VMware VAAI.

The plug-in helps vSphere communicate with NetApp basically allowing it to offload certain tasks from vSphere to NetApp. By passing certain tasks off to the NetApp, tasks can be processed faster and communicated back to vSphere when complete. An example is provisioning a VMDK file or performing a vMotion task. Rather than vSphere attempting to perform these tasks over the wire they can be performed directly on the NetApp by the array itself.

There are three different ways to get the NFS Plug-in installed onto an ESXi host. I’ve detailed the three different options below. Before you start you’ll obviously need the NFS Plug-in which can be downloaded from the NetApp support site. You’ll need a login ID and a valid support contract to do this.

Option 1. ESXCLI

This is my preferred option when only needed for a few hosts. It can be done on the actual ESXi host (e.g. ssh) or via the vMA.

Step 1. Copy the NFS plug-in zip file to a location that the ESXi host has access to. Below I copied the file to a folder called ‘vib’ on a test datastore.

Step 2. On the ESXCLI run the following command.

esxcli --server HOST_IP_ADDRESS software vib install -d /PATH_TO_VIB/vib_filename_.zip

Step 3. Reboot the host

Step 4. Check that the NFS plugin was installed with the following command. Scroll till you find NetAppNasPlugin under Name.

Option 2. VMware Update Manager

Step 1. Install the Plug-in into the Patch Repository. Click Import Patches and Browse to the location of the Plug-in zip file.

Click Next and ignore any certificate warning you may get to Import the patch.

Click Finish to finish the Import.

You should now see the NetAppNasPlugin in the Patch Repository list.

Step 2. Create a new baseline for the NFS Plug-in.

Click on Baseline and Groups. Right click to create a New Baseline. Fill in the Name and Description and select Host Patch.

Click next and select Fixed.

Scroll through the list of patches and locate the NetAppNassPlugin. Add the patch using the down arrow and click next.

Click Finish to install the patch.

Step 3. Attach the newly created Baseline to your hosts. Where you choose to do this is up to you. I choose to do it at the Cluster level.

Step 4. Once attached Scan and Remediate your host.

Option 3. NetApp Virtual Storage Console

This option is obviously dependant on you having already installed the Virtual Storage Console on a server and having the vSphere Plugin enabled.

If correctly installed the NetApp VSC can be found under Solutions and Applications called NetApp.

Navigate to Monitoring and Host Configuration and click on Tools. Under NFS plug-in for VMware VAAI it will say Unable to location plug-in.

Step 1. Extract the NFS zip file and locate the vib inside it. The vib will be denoted with a version number at the end. Make a copy of the file and call it NetAppNasPlugin.vib

This specific filename is required for the VSC to detect the vib correctly.

Step 2.

On the server where the Virtual Storage Console was installed. Copy the renamed file to C:Program FilesNetAppVirtual Storage Consoleetcvscweb

Step 3. Exit vCenter and log back in. Open the VSC back up. If the vib was renamed correctly and copied to the correct location. The VIB should now be detected under Tools of Monitoring and Host Configuration.

Step 4. Click on Install on Host to install the VIB plug-in. Any incompatible hosts will show up greyed out with a null besides there name.

In the below screenshot I have three incompatible hosts.

So there you have it. Three different ways to install the NetApp NFS Plug-in onto an ESXi host and three different pain in the ass ways.

Good Luck.

vSphere Update Manager 5.x to 5.5 Upgrade

Posted by Mark Ukotic on October 3, 2013 No comments

A few days back I upgrade a vCenter Server Appliance from 5.0 to 5.5. With that prerequisite out the way I can now upgrade vSphere Update Manager (VUM) from 5.0 to 5.5. This will bring me one step closer to being able to use VUM to upgrade my ESXi hosts to 5.5.

The process is very simple and just a matter of a few clicks. VUM still requires that it runs on a Windows Server, VMware having yet provided an appliance alternative --yet. So you will have to download the entire vSphere vCenter 5.5 Windows installation from VMware.

The process for a fresh install of VUM is similar to an upgrade. As I’m upgrading I’ll be running through the process I used. The first step is executing the installer.

Select vSphere Update Manager and Click Install

Click OK

If you have a previous version of VUM installed you will be prompted to upgrade.

Click Next to start to installation wizard.

Accept the license agreement.

A few things have changed in the latest version of VUM. Take note of what will be removed. Make sure the checkbox to download updates after installation is selected.

Enter in your vCenter details. Port 80 is the default unless you have changed this during vCenter installation. Enter in a user account and password that has admin rights into vCenter. If you’re running a vCenter Server Appliance like me you can use the root account.

If you haven’t already upgraded your vCenter to 5.5 you will receive the following warning and will need to upgrade vCenter before you can continue any further.

If you’re upgrading you won’t be able to change any database DSN or driver details. Click Next.

Select ‘Yes, I want to upgrade my Update Manager Database’. Select the checkbox ‘I have taken a backup of the existing Update Manager database’.

If your windows server’s IP address is resolvable its name will be listed in the drop down list. Select the server and leave the default ports unless you wish to change them. If you need to go through a proxy to access the internet select the checkbox below else click Next

Click Install to start the installation.

Update manager will need to be shutdown to upgrade it. Select ‘Automatically close and attempt to restart applications’.

Once the installation is complete open up the vCenter 5.5 C# client. Select plugins on the menu bar. Scroll down to Available Plug-ins and click Download and Install on VMware vSphere Update Manager.

So that’s it. Maybe a little more than a few click though 😉

You can now access Update Manager as you normally would in the vCenter Client.

vCenter Server Appliance 5.0 to 5.5 upgrade

Posted by Mark Ukotic on September 28, 2013 2 comments

VMware has recently released their latest version of vSphere 5.5. This includes a new version of the vCenter Server Appliance. If you’re still running vCenter Appliance 5.0 now is a great time to upgrade to the recently released VSA 5.5. With a switch from the embedded IBM DB2 to PostgresSQL the vCenter Server Appliance 5.5 now scales out far greater than before.

Earlier on in the year I wrote up a post on Why I don’t virtualize vCenter. I still like my physical vCenter. Slowly VMware are knocking down those barriers. With the latest version of VSA 5.5 they’ve removed the scalability issue for all but the largest deployments. Things like Update Manage and SRM are the few remaining obstacles to a VSA only environment.

Upgrading your VSA from a previous version is a simple and quick process. There are only a couple things that you really need to take into account before starting the process. Make sure you take a snapshot of your current VSA 5.x and a backup of any external DB you may be using. Don’t attempt to change the hostname of the VSA during the installation. Finally, and really less of a concern, if using custom SSL certificates make sure you met VSA requirements for signed certs.

Download the latest vCenter Service Appliance 5.5 OVF file from VMware. In vCenter import the OVF into your datacenter and Power On the VM.

Using a web browser connect to the Admin Management Portal of both Appliances on Port 5480 in two separate windows. e.g. https://vCenter_ip_address:5480

When you browse to the admin management portal on the new 5.5 appliance for the first you will be presented with a Setup wizard. Accepted the end user license agreement and click Next.

Select the second option, ‘Upgrade from previous version‘, and click Next.

The Setup wizard will skip a bunch of steps and present you with a key. Click click on it and select copy.

Now change browser tabs and navigate to the original 5.0 appliance. Click the Appliance Upgrade tab.

Select Source as the appliance role and click Set Role. You should receive the message, ‘Operation was successful’.

Click on Establish Trust and in the Remote appliance key field paste in the key you copied from the New (Remote) appliance and click Import remote key.

vc5_5_upgrade_07

Copy the key from the old 5.0 appliance (Source).

Navigate back to the new (remote) application and paste in the key you just copied and click Next.

If you attempted to set or change the hostname of the new 5.5 appliance you will receive a warning prompt. To save you a world of pain after the install it’s honestly best to cancel at this point and not set a hostname during the OVF import process. Trust me!

If you are using self-signed certificated you will most likely receive a prompt with certificate issues. Click Replace the SSL certificate and click Next.

The Setup wizard will now jump back up a few steps. Set an SSO password for [email protected] and click Next.

Confirm and select your hosts.

The Pre-Upgrade Checker now runs, hopefully with no errors and you can click Next.

vc5_5_upgrade_12

As a final precaution before the upgrade you are required to confirm that you have made a backup/snapshot of the source 5.5 vCenter Server Appliance --which of course you have and so you click Next.

vc5_5_upgrade_13

The Upgrade process now begins.

The new 5.5 VSA will now reboot.

If you were running vCenter Appliance 5.0 you would have no doubt still been working with the C# client. That’s still available and will need to be upgraded. You will be prompted to perform this action if you connect with an old client. After you upgrade and run the client a message states that all new features are only available via the vSphere Web Client.

You can access the new vSphere Web Client with a browser on port 9443. e.g. https://vCenter_ip_address:9443

Reference

Upgrading vCenter Server Appliance 5.0.x/5.1 to 5.5 (2058441)

« Previous page | Next page »

blog.ukotic.net

Too many problems, not enough time.

Category Archives: VMware - Page 2

Being a vExpert is a great motivation booster!

Enable SSH on vCenter Server Appliance 6 (VCSA)

No vmkcore disk partition is available

Modifying vCenter Server Appliance 6 (VCSA) NTP settings

VCP5-DCV Delta done and dusted

Configuring and Testing NTP on ESXi

My VCA experience

Installing NetApp NFS Plug-in for VMware VAAI

vSphere Update Manager 5.x to 5.5 Upgrade

vCenter Server Appliance 5.0 to 5.5 upgrade

Pages

Categories

Archives

Supporters