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