The ASM configuration failed. This feature is only active on a clustered system. This feature is controlled by the AsmConfFailure.Enabled, AsmConfFailure.HAAction.Primary, and AsmConfFailure.HAAction.Secondary BIGdb variables.
A specified cluster member has been disabled by a user. This feature is only active on a clustered system. The feature key is the name of the cluster member.
The specified cluster lacks a sufficent number of members marked as “up”. This feature is only active on a clustered system. The feature key is the name of the cluster. The client data is the required number of members marked “up”. This feature is controlled by the set_minimum_up_member_enabled_state and set_minimum_up_member methods in the System/Cluster interface.
The system time is not synchronized across all members of a specified cluster. This feature is only active on a clustered system. The feature key is the name of the cluster.
The specified daemon is not running or has restarted. The system checks liveliness by sending a zero signal and by checking for a change in a daemon’s process identifier. The feature key is the name of the daemon.
The specified daemon is not maintaining its heartbeat. The feature key is the name of the daemon. The client data is the current heartbeat value, which is a simple counter maintained by the specified daemon.
The FIPS hardware has detected certain classes of errors. In order to conform to FIPS requirements, these errors require a device reset. Until that happens, the FIPS hardware returns errors on all cryptographic requests. When the TMM detects these errors, it uses this feature to trigger the action to reset the device.
The system has been forced offline by the user.
The high availability group score on the current system is lower than its peer’s score. The feature key is the name of the high availability group. The client data is the current system’s group score.
State of the hardware (serial cable) failover peer This is purely informational, as it does not trigger an action. The client data indicates whether the peer is active (1) or in standby or down (0).
Either the send or receive paths are failing on an HSB interface. This is only active on an HSB platform, such as 3900, 6900, 8900, etc.
The license is not operational. This is purely informational, as it does not trigger an action. A “yes” in the “action required” field indicates that the license is not valid.
One of the local MPI connections between TMMs has failed. This usually indicates that at least one internal HSB interface has failed.
The MySQL daemon is failing to respond to an active probe. This feature is controlled by the MysqldFailure.Enabled, MysqldFailure.HAAction.Primary, and MysqldFailure.HAAction.Secondary BIGdb variables.
State of the network failover peer This is purely informational, as it does not trigger an action. The client data is the state: 1 - dead or untalkative, 2 - offline, 5 - standby, 6 - non-redundant Active, 7 - Active-standby Active.
Overdog control of the system watchdog This is purely informational, as it does not trigger an action.
The high availabilty group score on the peer system is higher than the current system’s score. This is purely informational, as it does not trigger an action. The feature key is the name of the high availability group. The client data is the group score on the peer system.
The specified pool lacks a sufficent number of members marked as “up”. The feature key is the name of the pool. The client data is the required number of pool members marked “up”. This feature is controlled by the set_minimum_up_member_enabled_state, set_minimum_up_member, and set_minimum_up_member_action methods in the LocalLB/Pool interface.
A user or daemon has requested a reboot.
A secondary SOD is waiting for the primary SOD to become fully active. This feature is only active on a clustered system. No action is reported in the table, but it is always “go offline”.
SOD lacks sufficient configuration information (usually the network failover address information) required for leaving the offline state.
The software process has either finished updating a software volume or changed the active software volume.
LACP has reported that the internal trunking on the switchboard has failed. This feature is controlled by the “failsafe_action” field in the “system” class, accessible through the LTConfig module.
TMM has detected a failure condition. TMM recognizes some failure conditions faster than SOD, such as a blade’s going down. If detected, TMM puts itself in standby, then triggers this feature, so that SOD can more completely handle it.
The primary TMM is ready for action. This is purely informational, as it does not trigger an action. Normally, setting the “action required” field is set to “yes” signals a failure, but here “yes” indicates that the primary TMM is okay, and “no” indicates not.
Unknown, illegal, or unsupported value
The specified VLAN is not passing traffic. The VLAN is monitored for traffic and if idle for a length of time, probing will be done by sending ARP requests through the VLAN. The feature key is the name of the VLAN. This feature is controlled by the create, set_failsafe_state, set_failsafe_action, and set_failsafe_timeout methods in the Networking/VLAN interface.
The hypervisor has gone offline. The system notifies local VCMP guests to go offline when the hypervisor goes offline.
The QuickAssist compression device has failed. The feature key is a unique identifier for the subsystem, and the client data is not used. This feature applies to 4000/4200 and 2000/2200 BIG-IP models. No actions beyond basic logging are currently allowed.
A crypto accelerator has failed. The feature key is the crypto accelerator instance. The client data is not used.
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.