You can specify these alerts to help you manage BIG-IP devices from F5 BIG-IQ Centralized Management.
|Alert||Enable if you want to know when||Action (if applicable)|
|Certificate expiration||A certificate for a BIG-IP device is within a specific number of days of expiring.|
|Certificate expired||A certificate for a BIG-IP device has expired.||Update the certificate so the BIG-IP device can continue to manage traffic.
|DNS Sync failed||A synchronization failed for the DNS synchronization group.||Investigate and resolve the issue, then synchronize the group.
Some potential reasons for this error might be: A network error, a BIG-IP device in the DNS sync group is unavailable (down), and so forth.
|Data Collection Device snapshot failed||A snapshot for a Data Collection Device failed.||Investigate and resolve the issue, then rerun the failed snapshot.|
|Device CPU above threshold||The CPU usage for a BIG-IP device is over a specified threshold.||Rebalance resources as needed.|
|Device backup failed||A backup failed for a BIG-IP device.||Investigate and resolve the issue, then rerun the failed backup.
Some potential reasons for this error might be: A network failure, not enough space for the backup, the device is unavailable (down), another BIG-IQ has discovered this device and is managing it, and so forth.
|Device could not be assigned to a Data Collection device||The maximum number of devices (200) has been assigned to a single Data Collection Device.||If you want to assign more BIG-IP devices, you must add another Data Collection
|Device is low on memory||The BIG-IP device is low on memory.||Investigate and resolve the issue.|
|Device software version update is required||A managed BIG-IP device is running a software version that is not compatible with the BIG-IQ software version.||This could happen after you upgrade BIG-IQ. To manage this BIG-IP device from BIG-IQ, you must upgrade it to a compatible software version. For more information about that process, refer to the F5 BIG-IQ Centralized Management : Device Management guide.|
|Framework update required||The framework for a BIG-IP device is not compatible with BIG-IQ.||This could happen after you upgrade BIG-IQ or update a BIG-IP device to version
11.x. To manage the BIG-IP device from BIG-IQ, you must update its framework.
|HA error||There is an issue with communication between the peer BIG-IQ systems in an high availability configuration.||Investigate and resolve the issue.
Some potential reasons for this error might be: A network failure, the peer is unavailable (down), and so forth.
|License expired||The license for a BIG-IP device has expired.||For a BIG-IP device managed from BIG-IQ, reactivate and reinstall its
Note: BIG-IQ does not send alerts for unmanaged BIG-IP devices. If you have licensed a BIG-IP device you are not managing from BIG-IQ, you'll have to monitor the expiration dates directly on the BIG-IP device itself.
|Managed Device Available||BIG-IQ successfully contacted a BIG-IP device.|
|Managed Device Unavailable||BIG-IQ cannot reach a BIG-IP device.||Check the health and status of the BIG-IP device, and resolve the issue.
Some potential reasons for this error might be: A network error, a BIG-IP device is offline for maintenance, another BIG-IQ has discovered this device and is managing it, and so forth.
|Statistics Collection Agent update required||A BIG-IP device has an older version of the stats agent installed.||Update the stats agent for the BIG-IP device.
|Statics Collection did not happened when expected||BIG-IQ has exceeded the time configured for the frequency of statistics collection for a device. The default is 60 seconds||This could be caused by an expired license, communication issues, and so forth.
To troubleshoot, take a look at the device.
|Used disk space is above threshold for a DCD||The disk space on a DCD is running out.||Take a look at your resources and adjust as needed.|
|Used disk space is above threshold for a device||The disk space for a device is over a specified threshold.||Check the BIG-IP device for non-critical files, such as old tcpdump, qkview, or core files. If you are uncertain about files to remove, contact F5 Technical Support for assistance.|
Simple Network Management Protocol (SNMP) is an Internet-standard protocol for collecting and organizing information about managed devices on IP networks. You can set up BIG-IQ® to work with SNMP so you can receive alerts when certain things happen on a managed device.
Gather the following information before you start your SNMP configuration.
|CONFIGURATION COMPONENT||CONSIDERATIONS||FOR MY CONFIGURATION|
|SNMP administrator contact information||Find out or decide who is responsible for SNMP administration. The contact information is a MIB-II simple string variable.|
|Machine location||Find out the location of the BIG-IQ system. The location is a MIB-II simple string variable.|
|BIG-IQ client allow list||Gather the IP or network addresses (with netmasks) of the SNMP managers from which the SNMP agent will accept requests.|
|Access||Find the OID for the top-most node of the SNMP tree to provide access to.|
|Community||Get the v1 and v2c communities and the IP addresses of the SNMP managers you want to grant access to.|
|Users||Get the v3 users you want to grant access to SNMP data, along with the privacy protocols and passwords, Community, Destination, and Port.|
This screen displays specified user addresses allowed to access your 3rd-party SNMP Manager BIG-IQ through the SNMP Agent. An agent can communicate with multiple managers, so you can configure BIG-IQ to support communications with one management station using the SNMP version1 protocol, one using the SNMP version 2C protocol, and another using SMNP version 3.
When you manage BIG-IP® devices that load balance SSL traffic, you must monitor their SSL traffic.
BIG-IQ® imports the certificates for every managed BIG-IP device you discover. This makes it easy to monitor the expiration dates all of your devices' SSL certificates from one location.
You can also: