I had the above situation on 2 of the 3 vCenter Appliances in the lab. All 3 are running the latest 5.5 Updates. I found a useful article here, which then link to this great article.
As you can see below, the Coredumps is full. It shows 100%.
To empty it, simply login to the appliance via SSH. I use Bitvise, a great utility, in the example below.
From there, just browse to the directory where we need to delete the files. As shown below, I have a lot of files that I no longer require.
It’s a matter of deleting them. The result is a clean directory 🙂
And the core dump now shows a healthy usage.
Speaking of vCenter, I’d recommend you deploy the vCenter Support Assistant. You should also upgrade your vCenter independently of your ESXi. I have provided some articles on vSphere 6.0, which I hope you find useful:
- How to redirect the vSphere 6.0 Platform Services Controller log
- vSphere 6 Update 1 appliance installation error.
- vSphere 6 enhancements. A tour of the web client.
- Features that are now global (cross vCenter Servers) in vSphere 6
There are a lot of blogs that covers the major, headlines new features. In this blog, I’d focus on the little things that I spotted as I tour the UI.
Check the screen below. Notice the APD and PDL information is now visible in the UI.
Do you use a lot of vESXi, also called nested ESXi? In 5.5, when you create a new VM, you do not see ESXi as an option. You normally choose Other (64 bit) as the Guest OS.
With 6.0, you will see it as an option. It is still not supported as there are many technical considerations that make support difficult. But in most cases, it is good enough as it just works!
Certificate is an areas that is complex. So it’s good to see the information on the ESXi Host. Together with the certificate management feature, this is a welcome improvement.
Smart Card integration makes its way. You find it under the Authentication Services, as shown below.
As a comparison, this is what it looks like in 5.5:
Search gets a little upgrade too. The Cluster option has more choices now in 6.0.
Compare the above with 5.5, which only lets you specify the cluster name. From what I’ve checked, other property remains the same.
Most of us have multiple vCenter Servers. As described in my book, there are reasons why you want to have a separate vCenter. It is common for me to see customers with 4 as the minimum numbers. I have 2 customers with >64 vCenter Servers (they are consolidating).
In vSphere 6, certain features are now global. You can apply at the “global” level. The first one is license. Check out the screenshot below! The tabs have also been streamlined. It’s cleaner now.
To refresh, here is how it looks like in 5.5. Notice you have to select a vCenter.
You may wonder what happens to the tabs in 5.5. For example, what happens to vCenter Server, Hosts, Clusters, Solutions. They are now parked under Assets as shown below.
Another feature going global is Tag! Cool, as you certainly want a consistent tagging across your SDDC. This is what it looks like in 5.5. Notice you have to select a vCenter.
And here is how it looks like in 6.0.
What about Permission? Yup, it’s going global too. The following screenshot shows that. Notice that under Access Control in the side bar, there is Global Permission in addition to Roles.
Below is the 5.5. equivalent. There is only Roles under Access Control.
The roles in 6.0 is also global. The screenshot below allows you to specify “All vCenter 6.0” from the drop down. There are also new roles. Can you notice them? Yup, Tagging Admin and Content Library Administrator.