Applies To:

Show Versions Show Versions

Supplemental Document: BIG-IP Health Model for F5 Monitoring Pack

Original Publication Date: 08/30/2013

When the F5 Networks Monitoring Pack is used to discover a BIG-IP network, many objects contained within the BIG-IP network will also be discovered. These objects are displayed in the Diagram View within Operations Manager, and the Health Explorer may be used to investigate various health properties for each type of object.

The health explorer above depicts the health model of a Node. Every object's health model consists of monitors grouped into four categories (Availability, Configuration, Performance, and Security). The monitors will display in one of the following states:

  • Green: Up and Available
  • Yellow: No monitor associated with the object / unknown (object would be blue or yellow in BIG-IP config utility)
  • Red: Object is disabled or marked down by a monitor (object would appear black or red in BIG-IP config utility)
  • Empty green circle: Monitor is not in use and does not affect the state of the object. Most performance monitors are by default not in use but can be enabled using overrides.

As you can see from the health explorer diagram, monitor states roll up to determine the overall health of the object. The worst state of any monitor ultimately determines the state of the object.

The following is a list of all discoverable BIG-IP objects and a description of which monitors make up each object's health model:

Note: The only performance monitors listed below that are enabled by default are Global Memory Used (BIG-IP), Total Blocks (Partitions), and Free Blocks (Partitions)

Note: This documentation was adapted from the F5 Management Pack Wiki hosted on DevCentral (http://devcentral.f5.com/wiki/MgmtPack.HomePage.ashx). Certain links or context described in this document may refer to content originally created on the Wiki.


BIG-IP Device

  • Availability
    • Control Device Connection: Indicates whether the F5 Monitoring Pack service has a connection to the BIG-IP device.
    • Failover State: This monitor will be green if the device is in Active mode
  • Performance
    • Global Client Bytes In (avg/sec)
    • Global Client Bytes Out (avg/sec)
    • Global Client Packets In (avg/sec)
    • Global Client Packets Out (avg/sec)
    • Global Client Maximum Connections (avg/sec)
    • Global Client Total Connections (avg/sec)
    • Global Client Current Connections
    • Global Server Bytes In (avg/sec)
    • Global Server Bytes Out (avg/sec)
    • Global Server Packets In (avg/sec)
    • Global Server Packets Out (avg/sec)
    • Global Server Maximum Connections (avg/sec)
    • Global Server Total Connections (avg/sec)
    • Global Server Current Connections
    • Global Memory
    • Global Memory Used
    • Global Dropped (avg/sec)
    • Global Errors In (avg/sec)
    • Global Errors Out (avg/sec)
    • Udp Opens (avg/sec)
    • Udp Accepts (avg/sec)
    • Udp Accept Fails (avg/sec)
    • Udp Connects (avg/sec)
    • Udp Connect Fails (avg/sec)
    • Udp Expires (avg/sec)
    • Udp Received Datagrams (avg/sec)
    • Udp Bad Receive Datagrams (avg/sec)
    • Udp Receive Unreachables (avg/sec)
    • Udp Bad Receive Checksums (avg/sec)
    • Udp Receive No Checksums (avg/sec)
    • Udp Transmited Datagrams (avg/sec)
    • Tcp Opens
    • Tcp Close Waits
    • Tcp FIN Waits
    • Tcp Time Waits
    • Tcp Accepts (avg/sec)
    • Tcp Accept Fails (avg/sec)
    • Tcp Connects (avg/sec)
    • Tcp Connect Fails (avg/sec)
    • Tcp Expires (avg/sec)
    • Tcp Abandons (avg/sec)
    • Tcp Receive Resets (avg/sec)
    • Tcp Bad Receive Checksums (avg/sec)
    • Tcp Bad Receive Seg (avg/sec)
    • Tcp OO Seg (avg/sec)
    • Tcp Received Cookies (avg/sec)
    • Tcp Bad Cookies Received (avg/sec)
    • Tcp SYN Cache Overrun (avg/sec)
    • Tcp Retransmits (avg/sec)
    • Http Set-Cookie header insertions (avg/sec)
    • Http Successful Responses (avg/sec)
    • Http Redirection Responses (avg/sec)
    • Http Client Error Responses (avg/sec)
    • Http Server Error Responses (avg/sec)
    • Http HTTP Requests (avg/sec)
    • Http Get Requests (avg/sec)
    • Http Post Requests (avg/sec)
    • Http Version 0.9 Requests (avg/sec)
    • Http Version 1.0 Requests (avg/sec)
    • Http Version 1.1 Requests (avg/sec)
    • Http Version 0.9 Responses (avg/sec)
    • Http Version 1.0 Responses (avg/sec)
    • Http Version 1.1 Responses (avg/sec)
    • Http Max Requests
    • Http Responses (00-01 Kilobytes) (avg/sec)
    • Http Responses (01-04 Kilobytes) (avg/sec)
    • Http Responses (04-16 Kilobytes) (avg/sec)
    • Http Responses (16-32 Kilobytes) (avg/sec)
    • Http Responses (32-64 Kilobytes) (avg/sec)
    • Http Responses (64-128 Kilobytes) (avg/sec)
    • Http Responses (128-512 Kilobytes) (avg/sec)
    • Http Responses (512K-2 Megabytes) (avg/sec)
    • Http Responses (Over 2 Megabytes) (avg/sec)
    • Http Idle Connection Splices (avg/sec)
    • Http Idle Connections (avg/sec)
    • Http Pre-compression Bytes (avg/sec)
    • Http Post-compression Bytes (avg/sec)
    • Http NULL-compression Bytes (avg/sec)
    • Http HTML Pre-compression Bytes (avg/sec)
    • Http HTML Post-compression Bytes (avg/sec)
    • Http CSS Pre-compression Bytes (avg/sec)
    • Http CSS Post-compression Bytes (avg/sec)
    • Http JS Pre-compression Bytes (avg/sec)
    • Http JS Post-compression Bytes (avg/sec)
    • Http XML Pre-compression Bytes (avg/sec)
    • Http XML Post-compression Bytes (avg/sec)
    • Http SGML Pre-compression Bytes (avg/sec)
    • Http SGML Post-compression Bytes (avg/sec)
    • Http Plain Pre-compression Bytes (avg/sec)
    • Http Plain Post-compression Bytes (avg/sec)
    • Http Octet Pre-compression Bytes (avg/sec)
    • Http Octet Post-compression Bytes (avg/sec)
    • Http Image Pre-compression Bytes (avg/sec)
    • Http Image Post-compression Bytes (avg/sec)
    • Http Video Pre-compression Bytes (avg/sec)
    • Http Video Post-compression Bytes (avg/sec)
    • Http Audio Pre-compression Bytes (avg/sec)
    • Http Audio Post-compression Bytes (avg/sec)
    • Http Other Pre-compression Bytes (avg/sec)
    • Http Other Post-compression Bytes (avg/sec)
    • Http RAM Cache Hits (avg/sec)
    • Http RAM Cache Misses (Cacheable) (avg/sec)
    • Http RAM Cache Misses (Uncacheable) (avg/sec)
    • Http RAM Cache Hits (Bytes) (avg/sec)
    • Http RAM Cache Misses (Bytes) (Cacheable) (avg/sec)
    • Http RAM Cache Misses (Bytes) (Uncacheable) (avg/sec)
    • Http RAM Cache Size
    • Http RAM Cache Count (avg/sec)
    • Http RAM Cache Evictions (avg/sec)
    • Http RAM Cache Inter-Stripe Hit Count (avg/sec)
    • Http RAM Cache Inter-Stripe Miss Count (avg/sec)
    • Http RAM Cache Inter-Stripe Hit Byte Count (avg/sec)
    • Http RAM Cache Inter-Stripe Cache Size (Bytes)
    • Http RAM Cache Inter-Stripe Cache Entity Count
    • Http RAM Cache Inter-Stripe Cache Evictions (avg/sec)
    • Http RAM Cache Remote Hit Count (avg/sec)
    • Http RAM Cache Remote Miss Count (avg/sec)
    • Http RAM Cache remote Hit Byte Count (avg/sec)
    • ClientSSL Bad Records (avg/sec)
    • ClientSSL Current Compat-mode Connections
    • ClientSSL Current Connections
    • ClientSSL Current Native Connections
    • ClientSSL Decrypted Bytes In (avg/sec)
    • ClientSSL Decrypted Bytes Out (avg/sec)
    • ClientSSL Encrypted Bytes In (avg/sec)
    • ClientSSL Encrypted Bytes Out (avg/sec)
    • ClientSSL Fatal Alerts (avg/sec)
    • ClientSSL Offloaded Connections (avg/sec)
    • ClientSSL Non-SSL Greeting Failures (avg/sec)
    • ClientSSL Handshake Failures (avg/sec)
    • ClientSSL Max Compat-mode Connections
    • ClientSSL Max Connections
    • ClientSSL Max Native Connections
    • ClientSSL Mid-connection Handshakes (avg/sec)
    • ClientSSL Software Connections (avg/sec)
    • ClientSSL Assisted Connections (avg/sec)
    • ClientSSL Invalid Certificates (avg/sec)
    • ClientSSL Connections Without Certificates (avg/sec)
    • ClientSSL Valid Certificates (avg/sec)
    • ClientSSL Unclean Shutdowns (avg/sec)
    • ClientSSL Records Received (avg/sec)
    • ClientSSL Records Transmitted (avg/sec)
    • ClientSSL Session Cache Entries (avg/sec)
    • ClientSSL Session Cache Hits (avg/sec)
    • ClientSSL Session Cache Invalidations (avg/sec)
    • ClientSSL Session Cache Lookups (avg/sec)
    • ClientSSL Session Cache Overflows (avg/sec)
    • ClientSSL Compat-mode Connections (avg/sec)
    • ClientSSL Native Connections (avg/sec)
[ Top ]

Global BIG-IP Objects

Interface

  • Availability
    • Interface State: green if the I/O channel is available
  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Errors In (avg/sec)
    • Errors Out (avg/sec)
    • Drops In (avg/sec)
    • Drops Out (avg/sec)
    • Collisions (avg/sec)

 

Trunk

  • Availability
    • Trunk State: green if the I/O channel is available
  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Errors In (avg/sec)
    • Errors Out (avg/sec)
    • Drops In (avg/sec)
    • Drops Out (avg/sec)
    • Collisions (avg/sec)

 

CPU

  • Availability
    • CPU State: always green in this version
  • Performance
    • Temperature
    • Fan Speed
    • Processor Utilization

 

Partition

  • Availability
    • Partition State: always green in this version
  • Performance
    • Block Size
    • Total Blocks
    • Free Blocks
    • Total Nodes
    • Free Nodes

 

Chassis

  • Availability
    • Chassis State: always green in this version
  • Performance
    • Temperature
[ Top ]

BIG-IP Local Traffic Manager (LTM) Objects

There are two monitors that every LTM and GTM object have in common:

  • Availability
    • Availability Monitor: Indicates whether a monitor on the BIG-IP network has marked the object up, down, or checking.
  • Configuration
    • Enabled State Monitor: Indicates whether the object is enabled or disabled.
      In addition to the monitors that every object have in common, many objects have additional monitors that help determine state. The following list shows all supported GTM and LTM BIG-IP objects and their additional monitors.

 

LTM Node

A node is the IP address associated with a device on the network. This IP address can be the real IP address of a network server, or it can be an alias IP address on a network server.

Additional Monitors

  • Availability
    • Monitor State
    • Session State
  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Maximum Connections (avg/sec)
    • Total Connections (avg/sec)
    • Current Connections

 

LTM Virtual Address

A virtual address and virtual port make up a virtual server.

LTM Virtual Server

Virtual servers are a specific combination of virtual address and virtual port, associated with a content site that is managed by a BIG-IP system or other type of host server.

Additional Monitors

  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Maximum Connections (avg/sec)
    • Total Connections (avg/sec)
    • Current Connections

 

LTM iRule

An iRule is a user-written script that controls the behavior of a connection passing through the BIG-IP system. iRules are an F5 Networks feature and are frequently used to direct certain connections to a non-default load balancing pool. However, iRules can perform other tasks, such as implementing secure network address translation and enabling session persistence.

LTM Pool

A pool is a logical group of pool members. The BIG-IP system load balances requests to the pool members within a pool, based on the load balancing method and persistence method you choose when you configure the pool.

Additional Monitors

  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Maximum Connections (avg/sec)
    • Total Connections (avg/sec)
    • Current Connections

 

LTM Pool Member

A pool member is one of the members of a load balancing pool. A pool member name indicates a node IP address and a service number.

Additional Monitors

  • Availability
    • Monitor State
    • Session State
  • Performance
    • Bytes In (avg/sec)
    • Bytes Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Maximum Connections (avg/sec)
    • Total Connections (avg/sec)
    • Current Connections
[ Top ]

BIG-IP Global Traffic Manager (GTM) Objects

BIG-IP Global Traffic Manager (GTM) Objects

GTM Data Center

A data center defines the group of Global Traffic Managers, Local Traffic Managers, and host systems that reside in a single physical location. Within the Global Traffic Manager, a data center contains at least one server and one link. Every resource, whether physical or logical, is associated in some way with a data center. The statistics for data centers revolve around the amount of traffic flowing to and from each data center.

Additional Monitors

  • Performance
    • CPU (avg/sec)
    • Memory (avg/sec)
    • Bits In (avg/sec)
    • Bits Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Connections (avg/sec)

 

GTM Server

A server, in the context of the Global Traffic Manager, defines a specific system on the network. A system can be a single Global Traffic Manager, Local Traffic Manager, or host system. Within the Global Traffic Manager, a server, with the exception of Global Traffic Managers and Link Controllers, must also contain at least one virtual server.

Additional Monitors

  • Performance
    • CPU (avg/sec)
    • Memory (avg/sec)
    • Bits In (avg/sec)
    • Bits Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Connections (avg/sec)

 

GTM Virtual Server

A virtual server, in the context of the Global Traffic Manager, is a combination of IP address and port number that points to a specific resource on the network.

Additional Monitors

  • Performance
    • CPU (avg/sec)
    • Memory (avg/sec)
    • Bits In (avg/sec)
    • Bits Out (avg/sec)
    • Packets In (avg/sec)
    • Packets Out (avg/sec)
    • Connections (avg/sec)

 

GTM Link

A link, in the context of the Global Traffic Manager, defines a physical connection to the Internet. Links are associated with one or more routers on the network. The Global Traffic Manager tracks the performance of links, which in turn can dictate the overall availability of a given pool, data center, wide IP, or distributed application.

GTM Distributed Application

The broadest collection of logical network components is distributed applications. A distributed application is a group of wide IPs that serves as a single application to a site visitor. The Global Traffic Manager does not load balance on wide IPs in a distributed application; however, using distributed applications within the Global Traffic Manager provides better visibility into the applications users access.

GTM Wide IP

A wide IP is a collection of one or more domain names that maps to one or more groups of virtual servers managed either by BIG-IP systems, or by host servers. The Global Traffic Manager load balances name resolution requests across the virtual servers that are defined in the wide IP that is associated with the requested domain name.

Additional Monitors

  • Performance
    • Atls (avg/sec)
    • Fallbacks (avg/sec)
    • Preferred (avg/sec)
    • Dropped (avg/sec)

 

GTM Pool

A pool is a group of virtual servers managed by a BIG-IP system, or a host. The Global Traffic Manager load balances among pools (using the Pool LB Mode), as well as among individual virtual servers.

Additional Monitors

  • Performance
    • Fallbacks (avg/sec)
    • Preferred (avg/sec)
    • Dropped (avg/sec)

 

GTM Pool Virtual Server

Just as a virtual server is a collection of IP addresses and port numbers, a pool is a collection of virtual servers. Pools represent virtual servers that share a common role on the network. A virtual server, in the context of the Global Traffic Manager, is a combination of IP address and port number that points to a specific resource on the network.

Additional Monitors

  • Performance
    • Fallbacks (avg/sec)
    • Preferred (avg/sec)
    • Dropped (avg/sec)
[ Top ]

Contacting F5 Networks

  Phone: (206) 272-6888
Fax: (206) 272-6802
Web: http://support.f5.com
Email: support@f5.com

For additional information, please visit http://www.f5.com.


Legal notices

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)