Description
background:
every vSAN administrator needs to validate that installed firmware versions and vendor driver map in order to accomplish a certified system according the broadcom hcl :
https://compatibilityguide.broadcom.com/search?program=io&persona=live&column=brandName&order=asc
vSphere systems are simple to manage because you can use the newest versions. vSAN systems need longer time for the certification and you cannot simply use the newest firmware or drivers. You have to search the hcl and check the compliance manually. In order to identify the io devices correctly the most reliable method is the usage of DID, VID, SVID and Max SSID.
Until now i used vDocumentation/powershell/vDocumentation/Public/Get-ESXIODevice.ps1 of vDocumentation . It seems that Ariel did not continue the project and that the API for this information has been changed.
It would be great if you could manage to add this id's in a table of the report.
Additional Context
No response
Before submitting
Description
background:
every vSAN administrator needs to validate that installed firmware versions and vendor driver map in order to accomplish a certified system according the broadcom hcl :
https://compatibilityguide.broadcom.com/search?program=io&persona=live&column=brandName&order=asc
vSphere systems are simple to manage because you can use the newest versions. vSAN systems need longer time for the certification and you cannot simply use the newest firmware or drivers. You have to search the hcl and check the compliance manually. In order to identify the io devices correctly the most reliable method is the usage of DID, VID, SVID and Max SSID.
Until now i used vDocumentation/powershell/vDocumentation/Public/Get-ESXIODevice.ps1 of vDocumentation . It seems that Ariel did not continue the project and that the API for this information has been changed.
It would be great if you could manage to add this id's in a table of the report.
Additional Context
No response
Before submitting