![]() ![]() You might say that is not unexpected, but think about this for a minute and consider the implication. ![]() So I clicked the “Details” tab and obtained some greater details. Well you would expect that the licensing engine would be stable enough to now that your vDS is licensed by your installed VSAN license and to ignore the fact that you are using a software feature that is not authorized in your edition (In my case Enterprise) but rather surprisingly this is what I received when I tried to use our licenses. This is true, if you are using Enterprise Plus Licensing, however what happens if you are not using Enterprise Plus licensing? What? I hear you shout, it is simple open up licensing and just put in your license key and you are away and running. Now I have a completely different view on Licensing the thing. Building and configuring a New VSAN is simple, even if you have to spend most of the morning in 4 machines LSI Bios configuring several single disk RAID0 groups and associated vDisks and then manually marking your SSD as such in ESXCLI. VSAN Makes configuring your ESXi storage so easy, I only wish iSCSI was so simple, (controller issues not withstanding)Īnd I still stand by this remark. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |