Forum Discussion
3 Replies
- David_LarsenEmployee
This guide on ask.f5.com would be a good start: TMOS Operations Guide.
As for SolarWinds it looks like it may be using the wrong OID values. The F5 tends to take all resources into ready to use state so that most SNMP monitors tend to look like what you are seeing. I believe there are other OID to use that would give you what TMOS is actually using of the resources it has reserved.
David
- David_Larsen_23Historic F5 Account
Unfortunately I do not know Solarwinds so I can't speak to the way it is using the SNMP OID values. This article on ask.f5.com shows what the OID values should be. https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_nsm_guide_943/nsm_snmp.html1042852 If you know where to find the SNMP OID's in Solarwinds then you should be good to go.
If not hopefully someone on DC will know how to point you in the correct direction.
as David says and you probably have seen yourself on the BIG-IP GUI, the BIG-IP reports on different sections (for lack of a better word) of memory. some of these are at 100% or just below. that isn't an issue or a bad thing. but if your reporting tool doesn't understand that it might look odd.
you could just ignore this in your tool.