Applies To:

Show Versions Show Versions

Manual Chapter: BIG-IP 9.x Network and System Management Guide: Troubleshooting SNMP Traps
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>


A

Troubleshooting SNMP Traps


Understanding F5-specific traps

The alert system and the SNMP agent on the BIG-IP system can send a number of notifications about the current operation of the BIG-IP system. The definitions of these notifications are known as traps, and are contained in the MIB file F5-BIGIP-COMMON-MIB.txt.

The types of notifications that the BIG-IP system can send to an SNMP manager are:

  • General traps
  • Hardware-related traps
  • License-related traps
  • Traffic management operating system (TMOS)-related traps
  • Authentication-related traps
  • Denial of Service (DoS)-related traps
  • Network-related traps
  • Logging-related traps

The remainder of this appendix contains tables that list the trap names contained in the MIB file F5-BIGIP-COMMON-MIB.txt, their descriptions, and the recommended action to take if you receive one of these notifications on your SNMP manager system.

General traps

The general notifications that you might receive on an SNMP manager system are listed and described in Table A.1.

Table A.1 General traps and recommended actions
Trap Name
Description
Recommended Action
bigipAgentStart
The SNMP agent on the BIG-IP system has been started.
For your information only. No action required.
bigipAgentShutdown
The SNMP agent on the BIG-IP system has been shut down.
bigipAgent Restart
The SNMP agent on the BIG-IP system has been restarted.
bigipConfigLoaded
The BIG-IP system configuration data was loaded.
bigipDiskPartitionWarn
Free space on the disk partition is limited.
Increase the available disk space.
bigipDiskPartitionGrowth
The disk partition use exceeds the growth limit.

 

Hardware-related traps

The hardware-related notifications that you might receive on an SNMP manager system are listed and described in Table A.2.

Table A.2 Hardware-related traps and recommended actions
Trap Name
Description
Recommended Action
bigipCpuTempHigh
The CPU temperature is too high.
Contact F5 Networks technical support.
bigipCpuFanSpeedLow
The CPU fan speed is too low.
bigipCpuFanSpeedBad
The CPU fan is not receiving a signal.
bigipChassisTempHigh
The temperature of the chassis is too high.
bigipChassisFanBad
The chassis fan is not operating properly.
bigipChassisPowerSupplyBad
The chassis power supply is not functioning properly.

 

License-related traps

The notifications related to licensing that you might receive on an SNMP manager system are listed and described in Table A.3

Table A.3 License traps and recommended actions
Trap Name
Description
Recommended Action
bigipLicenseFailed
Validation of a BIG-IP system license has failed, or the dossier has errors. Occurs only when first licensing the system or adding a module key (such as HTTP compression) to an existing system.
If using automatic licensing, verify connectivity to the outside world, fix the dossier if needed, and try again.
bigipLicenseExpired
The BIG-IP license has expired.
Call F5 Networks technical support.

 

TMOS-related traps

The TMOS-related notifications that you might receive on an SNMP manager system are listed and described in Table A.4.

Table A.4 TMOS-related traps and recommended actions
Trap Name
Description
Recommended Action
bigipServiceDown
A BIG-IP system health monitor has detected a service on a node to be stopped and has therefore marked the node as down.
Restart the service on the node.
bigipServiceUp
A BIG-IP system health monitor has detected a service on a node to be running and has therefore marked the node as up.
For your information only. No action required/
bigipNodeDown
A BIG-IP system health monitor has marked a node as down.
Check the node and the cable connection.
bigipNodeUp
A BIG-IP system health monitor has marked a node as up.
For your information only. No action required.
bigipStandby
The BIG-IP system has switched to standby mode.
Review the log files in the /var/log directory and then search for core files in the /var/core directory. If you find a core file, or find text similar to fault at location xxxx stack trace:, contact F5 Networks technical support.
bigipActive
The BIG-IP system has switched to active mode.
For your information only. No action required.
bigipActiveActive
The BIG-IP system is in active-active mode.
bigipFeatureFailed
A high-availability feature has failed.
View high-availability processes and their current status using the BIG-IP system command bigpipe ha table.
bigipFeatureOnline
A high-availability feature is responding.
For your information only. No action required.
bigipPacketRejected
The BIG-IP system has rejected some packets.
Check the detailed message within this trap and act accordingly.

 

Authentication-related traps

The notifications related to authentication that you might receive on an SNMP manager system are listed and described in Table A.5.

Table A.5 Authentication traps and recommended actions
Trap Name
Description
Recommended Action
bigipTamdAlert
More than 60 authentication attempts have failed within one second, for a given virtual server.
Investigate for a possible intruder.
bigipAuthFailed
A login attempt failed.
Check the user name and password.

 

DoS-related traps

The notifications related to denial of service that you might receive on an SNMP manager system are listed and described in Table A.6.

Table A.6 Denial of Service traps and recommended actions
Trap Name
Description
Recommended Action
bigipAggrReaperStateChange
The state of the aggressive reaper has changed, indicating that the BIG-IP system is moving to a distress mode.
We recommend that you use our default Denial of Service settings. However, you can add rate filters to survive the attack.

 

Network-related traps

The network-related notifications that you might receive on an SNMP manager system are listed and described in Table A.7.

Table A.7 Network traps and recommended actions
Trap Name
Description
Recommended Action
bigipARPConflict
The BIG-IP system has detected an ARP advertisement for any of its own ARP-enabled addresses. This can occur for a virtual server address or a self IP address.
Check IP addresses and routes.
bigipNetLinkDown
An interface link is down.
Check the cable connection.

 

Logging-related traps

The notifications related to logging that you might receive on an SNMP manager system are listed and described in Table A.8.

Table A.8 Logging-related traps and recommended actions
Trap Name
Description
Recommended Action
bigipLogEmerg
The BIG-IP system is unusable. This notification occurs when the system logs a message with the log level LOG_EMERG.
Check the detailed message within this trap and within the /var/log files to determine which process has the emergency. Then act accordingly.
bigipLogAlert
You must take action immediately for the BIG-IP system to function properly. This notification occurs when the system logs a message with the log level LOG_ALERT.
Check the detailed message within this trap and within the /var/log files to determine which process has the alert situation. Then act accordingly.
bigipLogCrit
The BIG-IP system is in a critical condition. This notification occurs when the system logs a message with the log level LOG_CRIT.
Check the detailed message within this trap and within the /var/log files to determine which process has the critical situation. Then act accordingly.
bigipLogErr
The BIG-IP system has some error conditions. This notification occurs when the system logs a message with the log level LOG_ERR.
Check the detailed message within this trap and within the /var/log files to determine which processes have the error conditions. Then act accordingly.
bigipLogWarning
The BIG-IP system is experiencing some warning conditions. This notification occurs when the system logs a message with the log level LOG_WARNING.
Check the detailed message within this trap and within the /var/log files to determine which processes have the warning conditions. Then act accordingly.

 

Note

You can also view logging information using the Logs screen of the Configuration utility.



Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)