healthiness of F5 - help with errors

Hi Andy,

I believe I can answer some of your questions.

Q1: The "other memory" is basically just memory being used by Linux processes and other non-TMM related things. It is fairly typical to see it's usage around 70%. So unless you see it steadily increasing, you shouldn't need to worry about it. We also have an article that talks a bit more about memory.

K16419: Overview of BIG-IP memory usage

https://support.f5.com/csp/article/K16419

As far as high CPU usage is concerned, that can depend on how many modules you have provisioned and what kind of traffic is being passed. If you are concerned with it then I would recommend opening a ticket with support just to have someone take a closer look at a qkview from the device to see if the usage appears to be normal or not.

Q2: Is that the full log as it appears in /var/log/ltm? If it isn't then please share the full log. Based on what you included it looks like a configsync of the "device-group-failover-2530624eebc7" occurred but it doesn't seem to say anything more. Are there any other logs around that time related to a sync that took place? Typically we would either see in the logs that the sync failed or that it was successful. It may be worth reviewing the logs of the peer device at that same timestamp as well to see if it logged anything about the sync between the two peers.

Q3: The health monitor will use a small amount of both memory and CPU but I wouldn't expect any noticeable difference in usage from a pool member being unreachable. At any given time the monitor should simply be checking to see if it can reach the pool member and if it can it will send it's health checks at the interval that you have configured within the monitor. That shouldn't cause the CPU or memory to spike up.

-Nathan F