There is not a whole lot of changes for kickstart configurations between ESXi 5.1 and ESXi 5.0, majority of the tips and tricks noted in the ESXi 5.0 kickstart guide are still relevant for ESXi 5.1. Below are a few new tips and tricks (some old) as well as a complete working ESXi 5.1 kickstart example that can be used as a reference.
Disabling IPv6 via Command-Line For ESXi 5.1 (Without Automatic Host Reboot)
IPv6 for the VMkernel interface is now automatically enabled by default for the latest release of ESXi 5.1 and you may have also noticed the additional IP Address in DCUI after the host boots up.
IPv6 support has been around for awhile now and you can enable IPv6 by using the old vSphere C# Client or the new vSphere Web Client. If you enable or disable IPv6, you will need to perform a system reboot for the changes to go into effect. You also have the ability to enable/disable it via the DCUI, which also has been around for awhile as well.
UPDATE: 07/20/15 - For ESXi 6.0, the VMkernel module is name is now tcpip4 instead of tcpip3.
There is one very important thing to note if you do enable/disable IPv6 on the DCUI, after you made your changes and you wish to apply, there is a very important confirmation box that is displayed.
Carefully read the last sentence which is underline in red "In case IPv6 has been enabled or disabled this will restart your host". If you are not careful in reading the confirmation screen, you may hit yes and your host will issue a reboot. If you are going to use the DCUI to enable or disable IPv6, make sure you do not have any running VMs on your host and you should already have your host maintenance mode when making configuration changes to your host.
In addition to the two methods listed above (vSphere Web Client/C# CLient and DCUI) you can easily enable/disable IPv6 using ESXCLI (my preferred method) and restart the ESXi host when you get a chance.
To view whether IPv6 is currently enabled, run the following ESXCLI command (ESXi 5.5 Update 1 the VMkernel module is now called tcpip4):
esxcli system module parameters list -m tcpip3
As you can see from the screenshot above, ipv6 property is set to 1 which means it is enabled.
To disable IPv6, you just need to set the property to 0, run the following ESXCLI command:
esxcli system module parameters set -m tcpip3 -p ipv6=0
We can now reconfirm by re-running our list operation to ensure the changes were made successfully. All that is left is to perform a system reboot, you can either type in "reboot" or use the new ESXCLI 5.1 command:
esxcli system shutdown reboot -d 60 -r "making IPv6 config changes"
Note: You can run the ESXCLI command locally on the ESXi Shell or you can run the same command remotely by specifying additional connection options & proxy through vCenter Server if you wish. Take a look here for additional connection options for ESXCLI.
vCloud Director 5.1 Introduces "Open in vSphere Web Client" & Task Correlation ... Awesomeness!
Have you ever had to troubleshoot something in vCloud Director such as looking into a particular vApp and then realizing you needed to jump over to the vSphere environment to continue troubleshooting? This meant you had to perform a separate login to your vSphere environment and most likely using a different set of credentials and then find the set of Virtual Machines that made up that vCloud Director vApp ... painful and annoying right? Wish you could just right click and jump straight to that vApp construct in vSphere?
Well, now you can with the latest release of vCloud Director 5.1 which introduces a new option called "Open in vSphere Web Client".
In the screenshot above, I have a vCloud Director vApp which contains 3 Virtual Machines and I want to jump straight to that object in the vSphere Web Client. To do so, simply right click on the object and select "Open in vSphere Web Client".
This will open up a new browser to the vSphere Web Client and locate the object in the appropriate vCenter Server and automatically log you in using the new vCenter SSO. Pretty cool huh!? This new option is not just limited to vCloud Director vApps and VMs, but applies to any vSphere object found within vCloud Director.
Note: You will need to be a System Administrator in vCloud Director to perform this operation as you will need access to the vSphere infrastructure.
Another challenge that you might have faced while troubleshooting in vCloud Director is to be able to correlate the tasks generated from vCloud Director and map those back to vSphere tasks in vCenter Server. This is not a trivial thing to do and required you to jump between vCloud Director and vCenter Server manually correlating the tasks. In vCloud Director 5.1, this has been enhanced by providing users with a single view for a given vCloud Director task and all the associated vSphere tasks that were created.
When you open a given vCloud Director task, you will be defaulted to the vCloud Director task details as you would expect. In the same view, there is also a new tab called vSphere Tasks which contains all the vCenter Server tasks generated from that given vCloud Director task.
As you can see from these two enhancements, you will be able to quickly and easily view all tasks that have taken place between vCloud Director and vCenter Server, all from a single location. If you need to drill down further into the vSphere layer, it is simply a right click and you will be taken directly to the vSphere object in the vSphere Web Client without having to provide additional credentials.
- « Previous Page
- 1
- …
- 465
- 466
- 467
- 468
- 469
- …
- 549
- Next Page »