Powercli Baseline scan Status details

[engineer4kailas]

Is there any way to get the conflict vibs details using powercli .

I already tried

Test-Compliance

Get-Compliance -Baseline

But it gives only compliant status and NO information about conflicting VIBs using powercli

[scott28tt]

Moderator: Thread moved to the PowerCLI area.

[LucD]

Did you already see Re: VUM cmdlets - get name of "conflicting VIBs" on ESXi hosts?

[engineer4kailas]

Yes , i have alrwady seen this thread but this is not what i am looking for .

I am planning to upgarde ~200 Host using VUM (powercli) but when i scanned one of my host with the ref  baseline i got the vib conflict status in complaince check but didnt get any details using powercli.

The upgrade contains the following set of conflicting VIBs:

QLogic_bootbank_scsi-qla4xxx_644.5.34.0-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla4xxx_644.5.34.0-1OEM.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.2.1.0-1OEM.500.0.0.472560

Emulex_bootbank_scsi-lpfc820_10.2.292.0-1OEM.500.0.0.472560

Mellanox_bootbank_net-mst_2.0.0.0-1OEM.500.0.0.472560

QLogic_bootbank_net-nx-nic_5.0.639-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla2xxx_934.5.38.0-1OEM.500.0.0.472560

QLogic_bootbank_net-qlcnic_5.3.191-1OEM.500.0.0.472560

Mellanox_bootbank_net-mst_2.0.0.0-1OEM.500.0.0.472560

QLogic_bootbank_net-qlcnic_5.3.191-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla2xxx_934.5.38.0-1OEM.500.0.0.472560

Emulex_bootbank_scsi-lpfc820_10.2.292.0-1OEM.500.0.0.472560

This list is not same of each host so i wan to write a script to get this details using powercli 

The upgrade contains the following set of conflicting VIBs:

QLogic_bootbank_scsi-qla4xxx_644.5.34.0-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla4xxx_644.5.34.0-1OEM.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.2.1.0-1OEM.500.0.0.472560

Emulex_bootbank_scsi-lpfc820_10.2.292.0-1OEM.500.0.0.472560

Mellanox_bootbank_net-mst_2.0.0.0-1OEM.500.0.0.472560

QLogic_bootbank_net-nx-nic_5.0.639-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla2xxx_934.5.38.0-1OEM.500.0.0.472560

QLogic_bootbank_net-qlcnic_5.3.191-1OEM.500.0.0.472560

Mellanox_bootbank_net-mst_2.0.0.0-1OEM.500.0.0.472560

QLogic_bootbank_net-qlcnic_5.3.191-1OEM.500.0.0.472560

QLogic_bootbank_scsi-qla2xxx_934.5.38.0-1OEM.500.0.0.472560

Emulex_bootbank_scsi-lpfc820_10.2.292.0-1OEM.500.0.0.472560

[Ankushsethi]

scan result I am not aware
but yes you can definitely use the esxcli to get the details for vcenter level how many hosts are having those vibs just change the name in below below

This is for one host

$esxcli=Get-esxcli -vmhost (get-vmhost hostname) -v2

$esxcli.software.vib.list.invoke()|?{$_.name-match "net-mst"}|select vendor,ID,Name

******************************************************************************************************************
for vcenter level

$esxi=get-vmhost

$report=@()

foreach($server in $esxi)

{

$cli=Get-esxcli -vmhost $server -v2

$report+=@($cli.software.vib.list.invoke()|?{$_.name-match "net-mst"}|select Vendor,ID,Name)

}