Skip to main content

VMware Configurations Maximum Tool URL

VMware has created a nice friendly URL - to help you quickly look at the configuration maximums across a few of their product ; NSX Data Center for vSphere, vSphere, VMware NSX-T, vRealize Operations Manager and VMware Site Recovery Manager. I assume VMware will add more as time goes by.

As you can see from the screenshot I have selected vSphere as the product and the version is 6.7. Under All Maximum you can select which maximums you want to view. From my screenshot I have selected Virtual Machine Maximums and to the right of the screen you can see all the maximum related to virtual machines. You can select to display other maximums as well and click View Limits to have the data updated, use the collapse all button to help collapse all the section of  your selected configuration maximums . There is a button to export all maximums to pdf  which exports all the maximums and not just what you have filtered down for display on the screen. It would be good if that function was to export what you had currently displayed on screen.

Another great feature of this site is that you can compare limits of different versions of the product which you can access by selecting Compare Limits button at the top of the page. So for example I have again select vSphere as the product and the base version I wanted to compare is 6.0. On the right hand side of the screen I have selected to compare with vSphere 6.5 and 6.7. You can add as many version as you want that can be compared and hit the Compare button. 

A new screen is displayed with the details of the version of vSphere we selected to compare. Again there is a button to export this information to csv file.

As you can see this site can be useful for when you are designing or upgrading a new environment so that you know what the new maximums are. It is also useful when you are taking your VCP exam too.


Post a comment

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://,udp:// 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net