For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Rubensk_246355's avatar
Rubensk_246355
Icon for Nimbostratus rankNimbostratus
Dec 21, 2016

Get critical services state via SNMP / REST

Hi,

 

I'd like to monitor some critical Big-IP services via SNMP. - As far I understand those are shown here:

 

 

The only OID I found was .1.3.6.1.2.1.25.4.2 - It shows running deamons:

 

 

I asked our security guy for stopping a services so that I can verify the result via SNMP. The result was that I could not find the entry any longer via SNMP - it came visible again after starting it.

 

Is there any other OID available?

 

If not, I could also accept to get this information via REST. - But here the same I could not locate a proper function in the REST-API.

 

Thanks in advance

 

Rubensk

 

BIG-IP
devops

2 Replies

  • Patrik_Jonsson's avatar
    Patrik_Jonsson
    Icon for MVP rankMVP
    Dec 21, 2016

    Sure thing, fire away all the questions you have. 🙂

    First when the SNMPD is running:

    [patrik@PatrikLab:Active:Changes Pending] log  curl -sku admin:password https://localhost/mgmt/tm/sys/ha-status?options=all-properties  | json-format
...
Loads of data
...
    "https://localhost/mgmt/tm/sys/ha-status/:daemon-heartbeat:snmpd": {
      "nestedStats": {
        "entries": {
          "action": {
            "description": "restart"
          },
          "clientData": {
            "value": 2395725
          },
          "enabled": {
            "description": "yes"
          },
          "failure": {
            "description": "no"
          },
          "haFeature": {
            "description": "daemon-heartbeat"
          },
          "key": {
            "description": "snmpd"
          },
          "respProcess": {
            "description": "snmpd"
          },
          "takeAction": {
            "description": "no"
          },
          "timeout": {
            "value": 300
          }
        }
      }
    },

    Then let's kill it:

    [patrik@PatrikLab:Active:Changes Pending] log  bigstart stop snmpd

    And run the query again:

    [patrik@PatrikLab:Active:Changes Pending] log  curl -sku admin:password https://localhost/mgmt/tm/sys/ha-status?options=all-properties  | json-format | grep -a10 "snmpd"
...
Loads of data
...
    "https://localhost/mgmt/tm/sys/ha-status/:daemon-heartbeat:snmpd": {
      "nestedStats": {
        "entries": {
          "action": {
            "description": "restart"
          },
          "clientData": {
            "value": 2395745
          },
          "enabled": {
            "description": "no"
          },
          "failure": {
            "description": "no"
          },
          "haFeature": {
            "description": "daemon-heartbeat"
          },
          "key": {
            "description": "snmpd"
          },
          "respProcess": {
            "description": "snmpd"
          },
          "takeAction": {
            "description": "no"
          },
          "timeout": {
            "value": 300
          }
        }
      }
    },

    Your network admin might kill me for saying this, but unless you're going through a proxy chances are you already have write access. 🙂 Go and create some mysterious nodes with funny names and what happens. 😄

    Hope that answers your question?

    /Patrik