Fix/ipmi status codes

[AlirieGray]

Closes: #5755

This PR adds support for hex values in IPMI messages. It also adds unit tests for both version 1 & 2 parsing of IPMI messages.

• Has appropriate unit tests.

[glinton]

Also, there's no need to force push on telegraf, we squash and merge so it ends up being one commit in the end.

[danielnelson]

Check length of description first to avoid panic

[danielnelson]

Check error before using descriptionInt

[safadig]

can you please update documentation for where to add hex value? Thanks

[danielnelson]

@safadig This PR should allow hex values to be parsed from the output of ipmitool, but it should be transparent and there is no configuration, values are reported in decimal. Let me know if I am misunderstanding or you can open a new issue.

[safadig]

@safadig This PR should allow hex values to be parsed from the output of ipmitool, but it should be transparent and there is no configuration, values are reported in decimal. Let me know if I am misunderstanding or you can open a new issue.

@danielnelson I am trying to use the ipmi from a Dell iDRAC that has user; password, as well as a hex based encryption key to allow access.
I can get access using ipmitool:
sudo ipmitool -I lanplus -H 192.168.1.1 -U user -P password -y 0000000000000000000000000000000000000000 sdr -v
However, this is how the documentation lists the variables in telegraf.conf. I tried inputing the encrypted hex key before root and other areas but was not successful:
[[inputs.ipmi_sensor]] servers =["root:Password@lan(192.168.1.1)"] interval = "30s" timeout = "20s"

[danielnelson]

Got it. It won't be possible to pass this option right now, but I see your feature request #6858.

[Raynok]

@danielnelson, also need this feature. I believe it can be a set variable that can be commented or uncommented in the config file (similar to the privilege level variable)

encryption Key = "number"