Bug ID 652799: When BIG-IP is used on an appliance with over 24 CPU cores (or VE on a HW platform with over 24 CPU cores) some processes may be constantly restarting until disabled.

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Mar 22, 2017

Severity: 2-Critical

Related Article: K29141414


ping_access_agent may be constantly restarting on BIG-IP appliance that has over 24 CPU cores.


PingAccess integration functionality will not be accessible to the users.


-- BIG-IP appliance has over 24 CPU cores or VE platform has over 24 CPU cores. -- APM is provisioned.


If PingAccess functionality is not required - disable process by running 'bigstart stop ping_access_agent'. If PingAccess functionality is needed: 1. Stop ping_access_agent by running "bigstart stop ping_access_agent'. 2. Modify file '/etc/bigstart/scripts/ping_access_agent' as follows: a) Replace line: cpu_count=$(get_number_cpu) with line: tmm_count=$(get_tmm_count) b) Replace line: exec /usr/sbin/${service} -n ${cpu_count} with line: exec /usr/sbin/${service} -n ${tmm_count} 3. Save the file, and restart the process by running 'bigstart start ping_access_agent'.

Fix Information

ping_access_agent no longer restarts when used on a platform with over 24 CPU cores and under 64 CPU cores.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips