Disable ATS Heartbeat

KB ID 0001529

Problem

After ESX 5.5 Update 2, VMware added ATS Heartbeat.Some vendors, (like HPE SureStore and VSA) recommend that this is disabled. I can’t find any info about whether it’s safe to do this in production, so to be on the safe side I placed the hosts in maintenance mode first.

Enter Maintenance Mode

Use the following command;

[box]

vim-cmd /hostsvc/maintenance_mode_enter

[/box]

Disable ATS Heartbeat

Use the following command to disable;

[box]

esxcli system settings advanced set -i 0 -o /VMFS3/UseATSForHBOnVMFS5

[/box]

Then confirm it worked with following command;

[box]

esxcli system settings advanced list -o /VMFS3/UseATSForHBOnVMFS5

[/box]

Confirm that INT Value is set to 0 (zero).

Exit Maintenance Mode

Use the following command;

[box]

vim-cmd /hostsvc/maintenance_mode_exit

[/box]

 

Related Articles, References, Credits, or External Links

NA

Virtual SAN: Suppress ‘Datastore Usage on Disk’ Alarm

KB ID 0001527

Problem

While deploying a HPE StoreVirtual VSA this week. We noticed all the local Datastore were showing an ‘Alarm’. If you are unfamiliar with Virtual SANs, then you give all the LOCAL Storage to them, which then gets ‘aggregated’ and provided back to the host(s) as fault tolerant clustered storage, like so;

Which is great, but the VMware hosts just see that their LOCAL Datastore(s) are full, and they alarm;

Solution

Whilst in ‘Datastore View’: Create a ‘Local Datastore Folder‘ and add all you local datastore(s) to that, then create a ‘Virtual Datastore Folder’ and add all your virtual/clustered datastore(s) to that. Select the vCenter > Monitor > Issues > Alarm Definitions > Locate the ‘Datastore usage on disk’ alarm and Edit it. 

Untick: Enable this alarm.

You will recreate this alarm again below, so take a note all ALL its settings;

Now select your Virtual Datastore folder > Monitor > Issues > Alarm Definitions > Add > Recreate the alarm again, Note: I’ve called it ‘Virtual-Datastore-Usage-On-Disk‘.

Have a coffee, refresh the page, the alarms should have gone.

Related Articles, References, Credits, or External Links

NA

HPE Synergy ‘Unable to Apply Local Storage Settings’

KB ID 0001497

Problem

While deploying some Blade severs, I was unable to get the ‘Local’ storage on the blades themselves to configure, (when setting up the server profiles). They were throwing this error;

Unable to apply local storage settings on server (Enclosure-name}, bay {number} because HPE OneView cannot communicate with the integrated Smart Array controller : Locked.

Resolution

Ensure that there is an integrated Smart Array controller present in the server. For Dynamic Smart Array Controllers, ensure the server is configured in UEFI boot mode, the  ‘Embedded SATA Configuration’ in the BIOS settings is set to ‘Smart Array SW RAID Support’ and firmware versions of the iLO and ROM are updated to the latest available. If the problem persists, contact your authorised support representative and provide them with a support dump.

Solution

Errm OK? UEFI boot mode will be on by default, unless you’ve manually changed it for some reason. And the Embedded SATA configuration BIOS setting will ONLY BE APPLICABLE if your blade DOES NOT have a RAID (Smart Array) card in it.

After manually trying to set the storage up on the Blade, I worked out what the problem was! 

You would only use the top option if you DIDN’T Have a ‘physical’ Smart Array controller in the blade! Which is what that original error is for, it’s trying to connect to the SOFTWARE RAID configuration which is disabled by default. If you need to use that, then you can either enable it directly on the blade like this;

Or (more sensibly, seeing as we are deploying server profiles,) in the profiles BIOS settings like this;

Related Articles, References, Credits, or External Links

HP BL460c (Gen 10) Blade No RAID?