Forum Discussion

Joseph_Lindsly's avatar
Aug 23, 2018

Adding additional OID to LTM for Solarwinds monitoring

I am currently using Solarwinds to monitor the F5 LTMs.

Whenever I go to add the suggested OID's to poll for disk failures, I get the below message:
"Unable to poll this OID on the test node. Try using a different OID or a different test node."

Here is an example of what i am trying to monitor:

1.3.6.1.4.1.3375.2.4.0.96

When i run the snmptranslate command on the LTM, I get the following message:

F5-BIGIP-COMMON-MIB::bigipRaidDiskFailure

When I run snmpwalk to the LTM for anything that starts with 1.3.6.1.4.1.3375.2.4, the text file is empty. Any help would be appreciated.

Thanks

3 Replies

  • Check F5-BIGIP-SYSTEM-MIB rather than F5-BIGIP-COMMON-MIB. For example sysPhysicalDiskEntry gives some details about physical disk.

     snmptranslate -m +F5-BIGIP-SYSTEM-MIB -IR -On sysPhysicalDiskEntry
    .1.3.6.1.4.1.3375.2.1.7.7.2.1
    
    • Joseph_Lindsly's avatar
      Joseph_Lindsly

      Thanks for the update. We recently had an outage due to Disk Failure and our management wants to monitor for that specifically. I contacted F5 support and they suggested 1.3.6.1.4.1.3375.2.4.0.96, but i can't get it to work.

       

    • Martin_Šebek_58's avatar
      Martin_Šebek_58
      Icon for Nimbostratus rankNimbostratus

      Unfortunately none of my systems has disks in raid so I see disk array status as undefined.

       snmpwalk -m +F5-BIGIP-SYSTEM-MIB -v2c -c public localhost .1.3.6.1.4.1.3375.2.1.7.7.2
      F5-BIGIP-SYSTEM-MIB::sysPhysicalDiskSerialNumber."WD-WMAYP0F5A3W5" = STRING: WDWMAYP0F5A3W5
      F5-BIGIP-SYSTEM-MIB::sysPhysicalDiskSlotId."WD-WMAYP0F5A3W5" = INTEGER: 0
      F5-BIGIP-SYSTEM-MIB::sysPhysicalDiskName."WD-WMAYP0F5A3W5" = STRING: HD1
      F5-BIGIP-SYSTEM-MIB::sysPhysicalDiskIsArrayMember."WD-WMAYP0F5A3W5" = INTEGER: false(0)
      F5-BIGIP-SYSTEM-MIB::sysPhysicalDiskArrayStatus."WD-WMAYP0F5A3W5" = INTEGER: undefined(0)