SNMP OID List for iLO4

I made a template for Zabbix today to monitor iLO 4 on the HP DL380p G8 server and had to investigate several OIDs.

You can check the OID from Linux with the command:
snmpwalk -c КОМЬЮНИТИ -v 2c OID

Below is a list and description for OID coolers, processors, temperature sensors, logical drives (RAID), hard disks, network controller iLO, RAM.

. (Fan Index)
. (Fan Locale (1=other, 2=unknown, 3=system, 4=systemBoard, 5=ioBoard, 6=cpu, 7=memory, 8=storage, 9=removable media, 10=power supply, 11=ambent, 12=chassis, 13=bridge card, 14=management board, 15=backplane, 16=network slot, 17=blade slot, 18=virtual)
. (Fan Present (1=other, 2=absent, 3=present)
. (Fan Present (1=other, 2=tachOutput, 3=spinDetect)
. (Fan Speed (1=other, 2=normal, 3=high)
. (Fan Condition (1=other, 2=ok, 3=degraded, 4=failed)

. (Temperature Sensor Index)
. (Temperature Sensor Locale (1=other, 2=unknown, 3=system, 4=systemBoard, 5=ioBoard, 6=cpu, 7=memory, 8=storage, 9=removable media, 10=power supply, 11=ambent, 12=chassis, 13=bridge card)
. (Threshold Type (1=other, 5=blowout, 9=caution, 15=critical, 16=noreaction)
. (Temperature Celsius)
. (TemperatureThreshold)
. (TemperatureCondition)

. (CPU Index)
. (CPU Name)
. (CPU Speed in MHz)
. (CPU Step)
. (CPU status (1=unknown, 2=ok, 3=degraded, 4=failed, 5=disabled)
. (Number of enabled CPU cores)
. (Number of available CPU threads)
. (CPU power status (1=unknown, 2=Low Powered, 3=Normal Powered, 4=High Powered)

Logical Drives:
. (Logical Drive Index)
. (Logical Drive Controller)
. (Logical Drive Fault Tolerance (1=other, 2=none, 3=RAID 1/RAID 1+0 (Mirroring), 4=RAID 4 (Data Guard), 5=RAID 5 (Distributed Data Guard), 7=RAID 6 (Advanced Data Guarding), 8=RAID 50, 9=RAID 60, 10=RAID 1 ADM (Advanced Data Mirroring), 11=RAID 10 ADM (Advanced Data Mirroring with Striping))
. (Logical Drive Size in Mb)
. (Logical Drive Status (1=other, 2=ok, 3=Failed, 4=Unconfigured, 5=Recovering, 6=Ready Rebuild, 7=Rebuilding, 8=Wrong Drive, 9=Bad Connect, 10=Overheating, 11=Shutdown, 12=Expanding, 13=Not Available, 14=Queued For Expansion, 15=Multi-path Access Degraded, 16=Erasing, 17=Predictive Spare Rebuild Ready, 18=Rapid Parity Initialization In Progress, 19=Rapid Parity Initialization Pending, 20=No Access – Encrypted with No Controller Key, 21=Unencrypted to Encrypted Transformation in Progress, 22=New Logical Drive Key Rekey in Progress, 23=No Access – Encrypted with Controller Encryption Not Enabled, 24=Unencrypted To Encrypted Transformation Not Started, 25=New Logical Drive Key Rekey Request Received)
. (Logical Drive Condition (1=other, 2=ok, 3=degraded, 4=failed)

. (Drive Index)
. (Drive Bay)
. (Drive Location)
. (Drive Vendor)
. (Drive Serial Number)
. (Drive Size in Mb)
. (Drive Link Rate (1=other, 2=1.5Gbps, 3=3.0Gbps, 4=6.0Gbps, 5=12.0Gbps))
. (Drive Current Temperature)
. (Drive Temperature Threshold)
. (Drive Maximum Temperature)
. (Drive Status (1=Other, 2=Ok, 3=Failed, 4=Predictive Failure, 5=Erasing, 6=Erase Done, 7=Erase Queued, 8=SSD Wear Out, 9=Not Authenticated)
. (Drive Condition (1=other, 2=ok, 3=degraded, 4=failed)
. (Drive Reference Time in hours)

. (iLO location)
. (iLO NIC model)
. (iLO NIC IPv4)
. (iLO NIC speed)
. (Tx bytes)
. (Tx packets)
. (Tx discard packets)
. (Tx error packets)
. (Rx bytes)
. (Rx packets)
. (Rx discard packets)
. (Rx error packets)
. (Rx unknown packets)

. (Memory Index)
. (Location)
. (Manufacturer)
. (Part Number)
. (Size in Kbytes)
. (Memory Technology)
. (Memory Type)
. (Memory status (1=other, 2=notPresent, 3=present, 4=good, 5=add, 6=upgrade, 7=missing, 8=doesNotMatch, 9=notSupported, 10=badConfig, 11=degraded, 12=spare, 13=partial)
. (Memory condition (1=other, 2=ok, 3=degraded, 4=degradedModuleIndexUnknown)

Why Zabbix does not always draw graphics

There are times when some of the information on the graphs in Zabbix is missing, so to say it is displayed partially and with interruptions.

I will describe possible reasons for interruptions and their solution:

1) There may be a bad connection to the network node, you need to check the ping from the Zabbix server to the network node.
For example, the first PING command with large packages from Windows, and the second from Linux:

ping -t -l 1024
ping -i 0.2 -s 1024

2) The device is slow to work and stops responding when there are a large number of requests, in order to solve this problem it is necessary to uncheck “Use mass requests” in the settings of the Zabbix network node.

3) 32-bit counters are used to obtain data from the network node, and when loading device interfaces, for example, above 400 megabits, the data on the graph may not be displayed; in order to solve this problem, in the data elements, they must be replaced with 64-bit ones and the node’s network history is cleared in order there were no leaps.
For example, if traffic is received from the first network interface via the ifInOctets.1 MIB (32-bit), then it must be replaced with ifHCInOctets.1 (64-bit).

Linux snmp OIDs

Example for check:

snmpget -v 1 -c "public" localhost .

System load:
In 1 minute: .
In 5 minutes: .
In 15 minutes: .

percentage of user CPU time: .
raw user cpu time: .
percentages of system CPU time: .
raw system cpu time: .
percentages of idle CPU time: .
raw idle cpu time: .
raw nice cpu time: .

Memory statistics:
Size of the Swap: .
Free Swap Space: .
Total RAM: .
Used RAM: .
Free RAM: .
Total RAM Shared: .
Total RAM Buffered: .
Total Cached Memory: .
Mount point: .
Mount the device for the partition: .
Total disk/partition size in kilobytes: .
Free disk space: .
Used disk space: .
Disk space used as a percentage: .

Uptime system: .
SNMP uptime: .

See also:
SNMP OID and MIB for interfaces