The latest release of VIN 1.2 supports the following ESX(i) builds:
- ESX/ESXi 3.5 (builds 425420, 408533, and 409724)
- ESX/ESXi 4.0 (builds 398348, 403553, and 403554)
- ESX/ESXi 4.1 (builds 433742, 433803, and 433804)
- and all builds of ESXi 5.x.
Disclaimer: ESX(i) hosts with build numbers that are smaller than the ones listed may still be added, but this will most likely not be supported as the list of default build numbers are the minimum requirements. Please thoroughly test this in a lab environment before applying to your production environment.
You will need SSH access to your VIN appliance and before we get started, we will quickly verify the list of supported ESX(i) build versions by querying the VIN database (I was able to find the details in /var/log/vadm/dbconfig.log). Run the following command which will connect to VIN Postgres DB:
psql -h 127.0.0.1 -U vadm -d inceptionThe password for the database is vadm
Next, we will run the following SQL query to display the list of supported ESX(i) build numbers which should match the release notes. Run the following command:
select * from valid_host_build;
To add a non-supported ESXi build number into VIN's DB, we will be using the following script /opt/vadm-engine/set_valid_host_versions.sh which is located in the VIN appliance.
Note: You do not need to stop or restart the VIN service to run the command.
The script accepts a very simple XML file that contains the list of supported ESX(i) build numbers and it is very IMPORTANT to note that this will override the original defaults. This is part of the reason we performed a query to the VIN DB to ensure we have a copy of the original build numbers as a reference.
To add our additional ESXi build number, we will need to construct an XML file containing both the original build numbers as well as our non-supported. In this example, I created a file called myHostVersion.xml (based on the original DB data) which contains following:
Next we will pass in our XML input file to the set_valid_host_versions.sh script. Here is a screenshot of what that looks like after the operation has been successfully completed: