Following on from the recent (November 2015) ESXi 6.0 CBT bug, which has now been fixed in the latest released patch ESXi600-201511401-BG, some further information has come to light, provided by Anton Gostev, of Veeam.
You can read the snippet of important information from the Veeam forum post following the issue (Official Veeam KB2075);
All, we have completed the first day of testing in the same exact lab and using the same heavy write I/O test that made the original issue easily reproducible. After a few TB of increments, the above-mention patch appears to fully resolve the original issue when installed on ESX 6.0 Update 1a build 3073146.
However, we found that simply installing the patch is not sufficient, and CBT reset is required for all of your VMs. This is because existing CBT map files may contain issues created earlier due to the original bug, which may result in inconsistent full backups in future. Having CBT reset will also force the following job run use "full scan" incremental pass, thus fixing any existing inconsistencies in backups and replicas, as discussed earlier in this topic.
Provided CBT reset has been performed, Active Full backups is not required.
Performing Active Full backups by itself cannot be considered as a substitute to CBT reset with this particular CBT issue.
You can either follow the CBT Reset instructions from Veeam or look over to Chris Wahl’s latest blog post “Resetting VMware’s Changed Block Tracking (CBT) File with PowerCLI”.
I wrote about the latest CBT issue (November edition) a couple of days ago, and as promised by VMware a patch has been released.
Original issue – KB 2136854
Patch to resolve the issue – ESXi600-201511001 (2137545)
Note: Before applying this patch on HP Proliant Gen 9 servers, see VMware ESXi 6.0 host fails to detect local disk after patching or applying Update 1 on HP Proliant Gen 9 servers (2120539).
Cheers VMware, lets hope this is the last of the CBT issues!!!
Firmware WB.15.18.0007 resolves the issue, see below
A colleague of mine found an issue with the latest HP 2920 switch firmware.
If you create VLANs using the CLI Menu, the switch reboots and the configuration is not saved.
We have reported this to HP, but is currently being treated as a non critical issue as when creating a VLAN via the web interface or native CLI, the issue doesn’t happen.
We have also noticed on this firmware the switch seems to be less responsive. Luckily we had a few units in stock that we could replicate this issue on, and can confirm downgrading to the previous firmware version removes the issue.
A quick cheers to my colleague Marco for finding and researching this issue.
Switch: HP 2920-48G-POE+
Primary Image : 12852982 08/12/15 WB.15.18.0006
Software revision : WB.15.18.0006
- Go to the Main Menu
- Select (2) Switch Configuration…
- Select (8) VLAN Menu…
- Select (3) VLAN Port Assignment
- Select Edit
- Modify the tagging mode for a port
- Select Save
- Switch reboots and doesn’t save configuration
Hopefully HP will release a fix for this firmware soon, as mentioned we have recreated this issue in production and test.
The following information was provided by HP Support. Continue reading HP 2920 Switch – Reboot issue on firmware ver 15.18.0006 #vDM30in30