Question:
Why is the command "which dmidecode" reporting as INCOMPLETE?
Answer:
"which: no dmidecode in (/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin)"
Based on the above validation result, this is actually a full command failure, which resulted in an Incomplete Inventory process for this device (meaning although this command failed, it did not stop inventory from being successful on this device).
-The reason this command failed is likely due to DMIDECODE not being installed on this server (we see this semi often). This is evident based on the output of the failure from above.
The DMIdecode pulls the Hardware Vendor, Model and Serial information. This will not inhibit the gathering of CPU, Ram and storage information and should the above mentioned information be desired, DMIDECODE can be installed of the desired servers and those servers can be re-scanned.
