Forum Discussion
InquisitiveMai
Cirrostratus
CirrostratusSNMP OIDs for Memory, CPU and Disk Usage
I have referred to few KB articles and Devcentral https://support.f5.com/csp/article/K6420. I compared files /var/run/bigip_error_maps.dat /etc/alert/alert.conf for High CPU OID.Looks like the OID...
InquisitiveMaiCirrostratus
CirrostratusThank you for your response. You meant
- To calculate CPU utilization % take two samples, calculate the delta, and calculate: ((<sysStatTmTotalCycles> - (<sysStatTmIdleCycles> + <sysStatTmSleepCycles>)) / <sysStatTmTotalCycles>) * 100
"SNMP not reachable", I was thinking if there is anyway a alert can be generated from F5. Will there be any log or any custom alert? I am thinking with the monitoring tool if F5 is not reachable through SNMP it should be able to trigger a alert.
CeinarF
Employee
EmployeeSorry I pasted a wrong formula.
OID doesn't give you the percentage of CPU utilization, so to calculate CPU utilization percent take two samples, calculate the delta, and calculate: ((<DeltaTmTotalCycles> - (<DeltaTmIdleCycles> + <DeltaTmSleepCycles>)) / <DeltaTmTotalCycles>) * 100
Monitoring tool normally monitors F5 IP, so if the IP is not reachable the F5 become "red". Just like F5 have monitor on Pools/members/nodes used by LTM.
If something is going wrong inside F5, TMOS generates internal alarm/logs, so can F5 can generate SNMP Trap or send "error log" to remote syslog servers or send email using an SMTP server.
So if you're asking "How F5 is able to send alarm if something is going wrong?", you can use one (or more) of the 3 options (SNMP Traps, remote syslog, email using external SMTP server).
BR