AskF5 _ Manual Chapter_ SNMP
June 21, 2016 | Author: Beatriz Roman | Category: N/A
Short Description
f5...
Description
06/11/13
AskF5 | Manual Chapter: SNMP Support
Global Sites
How to Buy
Login HOME
ABOUT F5
SOLUTIONS
PRODUCTS
SERVICES
PARTNERS
Careers
Contact
Search www.F5.com Search NEWS
RESOURCES
COMMUNITY
AskF5 Knowledge Base Home > Supported Products > BIGIP LTM > BIGIP TMOS: Concepts > SNMP Search AskF5 Supported Products BIGIP LTM BIGIP AAM
Manual Chapter: SNMP
Applies To:
Show Versions
BIGIP AFM BIGIP Analytics BIGIP APM
Table of Contents |
BIGIP ASM BIGIP Edge Gateway
BIGIP Link Controller
11
BIGIP PEM
BIGIP GTM
BIGIP PSM BIGIP WebAccelerator BIGIP WOM ARX ARX Cloud Extender Data Manager Enterprise Manager F5 Monitoring Pack FirePass BIGIQ Cloud BIGIQ Security Traffix SDC EndofLife Products Recent Additions
SNMP Introduction to SNMP administration SNMP agent configuration Working with SNMP MIB files Overview of F5 enterprise MIB files Overview of the RMON MIB file Collecting performance data
BIGIP Edge Apps About AskF5
Introduction to SNMP administration Downloads BIGIP iHealth WebSupport Licensing
Simple Network Management Protocol (SNMP) is an industrystandard protocol that gives a standard SNMP management system the ability to remotely manage a device on the network. One of the devices that an SNMP management system can manage is a BIGIP® system. The SNMP versions that the BIGIP system supports are: SNMP v1, SNMP v2c, and SNMP v3. The BIGIP system implementation of SNMP is based on a wellknown SNMP package, NetSNMP, which was formerly known as UCDSNMP. To configure and manage SNMP, log in to the BIGIP Configuration utility, and on the Main tab, expand Network, and click SNMP.
Feedback Mailing lists
Reviewing an industrystandard SNMP implementation A standard SNMP implementation consists of an SNMP manager, which runs on a management system and makes requests to a device, and an SNMP agent, which runs on the managed device and fulfills those requests. SNMP device management is based on the standard management information base (MIB) known as MIBII, as well as object IDs and MIB files. The MIB defines the standard objects that you can manage for a device, presenting those objects in a hierarchical, tree structure. Each object defined in the MIB has a unique object ID (OID), written as a series of integers. An OID indicates the location of the object within the MIB tree. A set of MIB files resides on both the SNMP manager system and the managed device. MIB files specify values for the data objects defined in the MIB. This set of MIB files consists of standard SNMP MIB files and enterprise MIB files. Enterprise MIB files are those MIB files that pertain to a particular company, such as F5 Networks®, Inc. Typical SNMP tasks that an SNMP manager performs include polling for data about a device, receiving notifications from a device about specific events, and modifying writable object data.
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
1/13
06/11/13
AskF5 | Manual Chapter: SNMP
Reviewing the BIGIP system SNMP implementation To comply with the standard SNMP implementation, the BIGIP system includes both an SNMP agent, a set of standard SNMP MIB files, and a set of enterprise MIB files (those that are specific to the BIGIP system). The enterprise MIB files typically reside on both the BIGIP system and system running the SNMP manager. Fortunately, you can use the browserbased Configuration utility to download the enterprise MIB files to your SNMP manager. Using the BIGIP system implementation of SNMP, the SNMP manager can perform these distinct functions: Poll for information (such as performance metrics) Receive notification of specific events that occur on the BIGIP system Set data for SNMP objects that have a read/write access type
Summarizing SNMP configuration on the BIGIP system Before you can use an SNMP manager system to manage a BIGIP system remotely, you must perform the following procedures on the BIGIP system, using the BIGIP® Configuration utility. Configuring the SNMP agent There are a number of ways to configure the SNMP agent on the BIGIP system. For example, you can allow client access to information that the SNMP agent collects, and you can configure the way that the SNMP agent handles SNMP traps. (Traps are definitions of unsolicited notification messages that the BIGIP alert system and the SNMP agent send to the SNMP manager when certain events occur.) Downloading MIB files You can download two sets of MIB files to your remote manager system: the standard SNMP MIB files and the enterprise MIB files. Note: An alternate way to configure SNMP is to use tmsh. For more information, see the Traffic Management Shell (tmsh) Reference Guide.
SNMP agent configuration You configure the SNMP agent by performing the following tasks: Configuring BIGIP system information Specify a system contact name and the location of the BIGIP system. Configuring client access to the SNMP agent Configure the BIGIP system to allow access to the SNMP agent from an SNMP manager system. Controlling access to SNMP data Assign access levels to SNMP communities or users, to control access to SNMP data. Configuring traps Enable or disable traps and specify the destination SNMP manager system for SNMP traps. Note: Only users with either the Administrator or Resource Administrator user role can configure SNMP on the BIGIP system.
Controlling access to SNMP data To better control access to SNMP data, you can assign an access level to an SNMP v1 or v2c community, or to an SNMP v3 user. There is a default access level for communities, and this access level is readonly. This means that you cannot write to an individual data object that has a read/write access type until you change the default readonly access level of the community or user. When you set the access level of a community or user to read/write, and an individual data object has a readonly access type, access to the object remains readonly. In short, the access level or type that is the most secure takes precedence when there is a conflict. Table 11.1 illustrates this point. Table 11.1 Access control for SNMP data And you set the access level of a community or user to...
Then access to the object is...
Readonly
Readonly
Readonly
Read/write
Readonly
Read/write
Readonly
Readonly
Read/write
Read/write
If the access type of an object is...
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
2/13
06/11/13
AskF5 | Manual Chapter: SNMP
Working with SNMP MIB files There are two sets of MIB files that typically reside on the BIGIP system and the SNMP manager system: enterprise MIB files (that is, F5®specific MIB files) and standard SNMP MIB files. Both sets of MIB files are present on the BIGIP system, in the directory /usr/share/snmp/mibs. However, you still need to download them to your SNMP manager system. You can download these MIB files from the Welcome screen of the browserbased Configuration utility.
The implementation of the Packet Velocity® ASIC (PVA) feature affects the ability for users to use MIBII to gather certain kinds of data. For example, with a PVA system, you can use MIBII to collect statistics on physical system interfaces, but not on logical interfaces (that is, VLANs). The BIGIP system uses MIBII for gathering standard Linux data only. You cannot use MIBII to gather data that is specific to the BIGIP system and instead must use the F5 enterprise MIB files. All OIDS for BIGIP system data are contained in the F5 enterprise MIB files, including all interface statistics (1.3.6.1.4.1.3375.2.1.2.4 (sysNetwork.sysInterfaces)). If you want to use SNMP to monitor a specific process on the BIGIP system, you can use the HOSTRESOURCES MIB and then write a script to monitor that process. Then, for example, to determine the number of TMM processes currently running on the system, you can use a command such as the following: snmpwalk -v2c -c public localhost hrSWRunName | egrep "\"tmm(.[0-9]+)?\"" | wc -l Note: All BIGIP system statistics are defined by 64bit counters. Thus, because only SNMP v2c supports 64bit counters, your management system needs to use SNMP v2c to query BIGIP system statistics data.
Overview of F5 enterprise MIB files The F5 enterprise MIB files contain information that you can use for your remote management station to: poll the SNMP agent for BIGIP systemspecific information, receive BIGIP systemspecific notifications, or set BIGIP system data. To perform remote management, download the following F5 enterprise MIB files to the SNMP manager system: F5BIGIPCOMMONMIB.txt F5BIGIPLOCALMIB.txt F5BIGIPSYSTEMMIB.txt F5BIGIPGLOBALMIB.txt Once you have downloaded all of the necessary MIB files, you should familiarize yourself with the contents of the enterprise MIBs, for purposes of managing the BIGIP system and troubleshooting BIGIP system events. Note: To manage a BIGIP system with SNMP, you need to use the standard set of SNMP commands. For information about SNMP commands, consult your favorite thirdparty SNMP documentation, or visit the web site http://netsnmp.sourceforge.net.
Using the F5BIGIPCOMMONMIB.txt file The F5BIGIPCOMMONMIB.txt file contains objects pertaining to any common information, as well as all F5specific notifications (SNMP traps). This MIB file specifies and defines objects for which all other BIGIP MIB files reference. You can identify the traps within this MIB file by viewing the file and finding object names that show the designation NOTIFICATIONTYPE. When an F5specific trap sends a notification to the SNMP manager system, the SNMP manager system receives a text message describing the event or problem that has occurred. For troubleshooting assistance regarding F5specific traps, see Appendix A, Troubleshooting SNMP Traps.
Using the F5BIGIPLOCALMIB.txt file The F5BIGIPLOCALMIB.txt file contains information about the properties associated with any local traffic management object (virtual servers, pools, nodes, profiles, SNATs, health monitors, and iRules®). An SNMP manager system can access and use this information to help you manage local application traffic. For example, you can: View the maximum number of entries that a node can have open at any given time. Get a pool name. View the current active members for a load balancing pool. Reset pool statistics Get profile information such as the total number of concurrent authentication sessions. You can also reset statistics for any of these objects.
Using the F5BIGIPSYSTEMMIB.txt file The F5BIGIPSYSTEMMIB.txt file describes objects representing common BIGIP system information. Examples of
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
3/13
06/11/13
AskF5 | Manual Chapter: SNMP information in this MIB file are global statistic data, network information, and platform information. Some of the data in this MIB file is similar to that defined in MIBII, but is not exactly the same.
Using the F5BIGIPGLOBALMIB.txt The F5BIGIPGLOBALMIB.txt file contains information that an SNMP manager system can use to help manage global application traffic objects, such as wide IPs, virtual servers, pools, links, servers, and data centers. You can reset statistics for any of these objects.
Overview of the RMON MIB file In addition to the F5 enterprise MIB files, the BIGIP system also provides the remote network monitoring (RMON) MIB file, RMONMIB.txt.
Using the RMONMIB.txt file The implementation of RMON on the BIGIP system differs slightly from the standard RMON implementation, in the following ways: The BIGIP system implementation of RMON supports four of the nine RMON groups. The four supported RMON groups are: statistics, history, alarms, and events. The RMONMIB.txt file monitors the BIGIP system interfaces (that is, sysIfIndex), and not the standard Linux interfaces. For hardware reasons, the packetlengthspecific statistics in the RMON statistics group offer combined transmission and receiving statistics only. This behavior differs from the behavior described in the definitions of the corresponding object IDs.
Collecting performance data The Configuration utility on the BIGIP system displays graphs showing performance metrics for the system. However, you can also use SNMP to collect the same information. The types of performance metrics that you can gather using SNMP are: Memory use Number of active connections Number of new connections Throughput in bits per second Number of HTTP requests RAM Cache use CPU use Number of SSL transactions Each type of metric has one or more SNMP object IDs (OIDs) associated with it. To gather performance data, you specify these OIDs with the appropriate SNMP command. For example, the following SNMP command collects data on current memory use, where public is the community name and bigip is the host name of the BIGIP system: snmpget -c public bigip sysGlobalStat.sysStatMemoryUsed.0 For some types of metrics, such as memory use, simply issuing an SNMP command with an OID gives you the information you need. For other types of metrics, the data that you collect with SNMP is not useful until you perform a calculation on it to interpret the data. For example, to determine the throughput rate of client bits coming into the BIGIP system, you must you must use the relevant OID (sysStatClientBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.3)) to take two polls at a certain interval (such as ten seconds), calculate the delta of the two polls, and then perform the following calculation on that delta value: ( *8 ) / Important: For calculations that include a polling interval, the interval can be any amount of time that you choose, as long as you use that same number as the value for in your calculations. Note that the performance graphs that the Configuration utility displays are based on a polling interval of ten seconds. The following sections contain tables that list: The OIDs that you can use to collect the performance data The calculations that you must perform to interpret the performance data that you collect (not required for interpreting data on memory use and active connections).
Collecting data on memory use You can use an SNMP command with OIDs to gather data on the number of bytes of memory currently being used on
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
4/13
06/11/13
AskF5 | Manual Chapter: SNMP the BIGIP system. Table 11.2 shows the OIDs that you need to specify to gather data on current memory use. To interpret data on memory use, you do not need to perform a calculation on the collected data. Table 11.2 Required OIDs for collecting metrics on memory use Performance Graph (Configuration utility) Memory Used
Graph Metric
Required SNMP OIDs
TMM Mem Usage
sysStatMemoryUsed (.1.3.6.1.4.1.3375.2.1.1.2.1.45)
Host Mem Usage
sysHostMemoryUsed (.1.3.6.1.4.1.3375.2.1.7.1.2)
Collecting data on active connections You can use SNMP commands with various OIDs to gather data on the number of active connections on the BIGIP system. Table 11.3 shows the OIDs that you need to specify to gather data on active connections. To interpret data on active connections, you do not need to perform any calculations on the collected data. Table 11.3 Required OIDs for collecting metrics on active connections Performance Graph (Configuration utility)
Graph Metrics
Required SNMP OIDs
Active Connections (summary graph)
Connections
sysStatClientCurConns (.1.3.6.1.4.1.3375.2.1.1.2.1.8)
Active Connections (detailed graph)
client
sysStatClientCurConns (.1.3.6.1.4.1.3375.2.1.1.2.1.8)
server
sysStatServerCurConns (.1.3.6.1.4.1.3375.2.1.1.2.1.15)
pva client
sysStatPvaClientCurConns (.1.3.6.1.4.1.3375.2.1.1.2.1.22)
pva server
sysStatPvaServerCurConns (.1.3.6.1.4.1.3375.2.1.1.2.1.29)
ssl client
sysClientsslStatCurConns (.1.3.6.1.4.1.3375.2.1.1.2.9.2)
ssl server
sysServersslStatCurConns (.1.3.6.1.4.1.3375.2.1.1.2.10.2)
Collecting data on new connections You can use SNMP commands with various OIDs to gather and interpret data on the number of new connections on the BIGIP system. To gather and interpret the data for each of these metrics, you must perform some polling and calculations: First, for each OID, you must perform two separate polls, at a time interval of your choice. Next, you calculate the delta of the two poll values. Finally, for each graph metric, you perform a calculation on those OID deltas. Table 11.4 shows the individual OIDS that you must poll to retrieve two separate poll values for each OID. Table 11.4 Required OIDs for polling for data on new connections Performance Graph (Configuration utility)
Graph Metrics
Required SNMP OIDs
New Connections (summary graph)
Client Accepts
sysTcpStatAccepts (.1.3.6.1.4.1.3375.2.1.1.2.12.6)
Server Connects
sysStatServerTotConns (.1.3.6.1.4.1.3375.2.1.1.2.1.14)
Client Connects
sysStatClientTotConns (.1.3.6.1.4.1.3375.2.1.1.2.1.7)
Server
sysStatServerTotConns
Total New Connections (detailed graph)
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
5/13
06/11/13
AskF5 | Manual Chapter: SNMP Connects
(.1.3.6.1.4.1.3375.2.1.1.2.1.14)
pva client
sysStatPvaClientTotConns (.1.3.6.1.4.1.3375.2.1.1.2.1.21)
pva server
sysStatPvaServerTotConns (.1.3.6.1.4.1.3375.2.1.1.2.1.28)
New Client SSL Profile Connections (detailed graph)
SSL Client
sysClientsslStatTotNativeConns (.1.3.6.1.4.1.3375.2.1.1.2.9.6) sysClientsslStatTotCompatConns (.1.3.6.1.4.1.3375.2.1.1.2.9.9)
SSL Server
sysServersslStatTotNativeConns (.1.3.6.1.4.1.3375.2.1.1.2.10.6) sysServersslStatTotCompatConns (.1.3.6.1.4.1.3375.2.1.1.2.10.9)
New Accepts/Connects (detailed graph)
Client Accepts
sysTcpStatAccepts (.1.3.6.1.4.1.3375.2.1.1.2.12.6)
Server Connects
sysTcpStatConnects (.1.3.6.1.4.1.3375.2.1.1.2.12.8)
New PVA Connections (detailed graph)
For example, the following steps show how to collect data for the Client Accepts graph metric: 1.
Poll OID sysTcpStatAccepts (.1.3.6.1.4.1.3375.2.1.1.2.12.6) twice, at a 10second interval. This results in two values, and . Note: Although this example uses an interval of ten seconds, the interval can actually be any duration that you choose. 2.
Calculate the delta of the two poll values: = -
3.
Calculate the value of the Client Accepts graph metric using the calculation shown in Table 11.5 ( / ), where the value of is 10.
Table 11.5 Required calculations for interpreting metrics on new connections Performance Graph (Configuration utility)
Graph Metrics
Required calculations for new connection metrics
Client Accepts
/
Server Connects
/
Total New Connections (detailed graph)
Client Connects
/
Server Connects
/
New PVA Connections (detailed graph)
pva client
/
pva server
/
New SSL Connections (detailed graph)
SSL Client
( + ) /
SSL Server
( + ) /
New Accepts/Connects (detailed graph)
Client Accepts
/
Server Connects
/
New Connections (summary graph)
Collecting data on throughput rates You can use SNMP commands with various OIDs to gather and interpret data on the throughput rate on the BIGIP system, in terms of bits per second. To gather and interpret the data for each of these metrics, you must perform some polling and calculations: First, for each OID, you must perform two separate polls, at an interval of your choice. Next, you calculate the delta of the two poll values. Finally, for each graph metric, you perform a calculation on those OID deltas.
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
6/13
06/11/13
AskF5 | Manual Chapter: SNMP Table 11.6 shows the individual OIDS that you must poll, retrieving two separate poll values for each OID. Table 11.6 Required OIDs for polling for data on throughput rates Performance Graph (Configuration utility)
Graph Metrics
Required SNMP OIDs
Client Bits
sysStatClientBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.3) sysStatClientBytesOut (.1.3.6.1.4.1.3375.2.1.1.2.1.5)
Server Bits
sysStatServerBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.10) sysStatServerBytesOut (.1.3.6.1.4.1.3375.2.1.1.2.1.12)
Clientside Throughput (detailed graph)
Client Bits In
sysStatClientBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.3)
Client Bits Out
sysStatClientBytesOut (.1.3.6.1.4.1.3375.2.1.1.2.1.5)
Serverside Throughput (detailed graph)
Server Bits In
sysStatServerBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.10)
Server Bits Out
sysStatServerBytesOut (.1.3.6.1.4.1.3375.2.1.1.2.1.12)
Compression
sysHttpStatPrecompresssBytes (.3375.2.1.1.2.4.21)
Throughput (summary graph)
HTTP Compression Rate (detailed graph)
For example, the following steps show how to collect data on throughput rates for the Server Bits In graph metric: 1.
Poll OID sysStatServerBytesIn (.1.3.6.1.4.1.3375.2.1.1.2.1.10) twice, at a 10second interval. This results in two values, and . Note: Although this example uses an interval of ten seconds, the interval can actually be any duration that you choose. 2.
Calculate the delta of the two poll values: = -
3.
Calculate the value of the Server Bits In graph metric using the calculation shown in Table 11.7 ( / ), where the value of is 10.
. Table 11.7 Required calculations for interpreting metrics on throughput rates Performance Graph (Configuration utility) Throughput (summary graph)
Throughput (detailed graph)
Graph Metrics
Required calculations for throughput rates
Client Bits
( ( + )*8 ) /
Server Bits
( ( + )*8 ) /
Compression
( *8 ) /
Client Bits In
( *8 ) /
Client Bits Out
( *8 ) /
Server Bits In
( *8 ) /
Server Bits Out
( *8 ) /
Compression
( *8 ) /
Collecting data on HTTP requests You can use SNMP commands with an OID to gather and interpret data on the number of current HTTP requests on the BIGIP system, in terms of requests per second.
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
7/13
06/11/13
AskF5 | Manual Chapter: SNMP To gather and interpret the data for this metric, you must perform some polling and calculations: First, you must use the OID to perform two separate polls, at an interval of your choice. Next, you calculate the delta of the two poll values. Finally, you perform a calculation on the OID delta. Table 11.8 shows the OID that you must poll, retrieving two separate poll values for this OID. Table 11.8 Required OIDs for polling for data on HTTP requests Performance Graph (Configuration utility)
Graph Metric
Required SNMP OIDs
HTTP Requests
HTTP Requests
sysStatHttpRequests (.1.3.6.1.4.1.3375.2.1.1.2.1.56)
For example, to collect data on HTTP requests for the HTTP Requests graph metric, follow these steps. 1.
Poll OID sysStatHttpRequests (.1.3.6.1.4.1.3375.2.1.1.2.1.56) twice, at a 10second interval. This results in two values, and . Note: Although this example uses an interval of ten seconds, the interval can actually be any duration that you choose. 2.
Calculate the delta of the two poll values: = -
3.
Calculate the value of the HTTP Requests graph metric using the calculation shown in Table 11.9, where the value of is 10.
Table 11.9 Required calculations for interpreting metrics on HTTP requests Performance Graph (Configuration utility)
Graph Metric
Required calculations for HTTP requests
HTTP Requests
HTTP Requests
/
Collecting data on RAM Cache use You can use an SNMP command with various OIDs to gather and interpret data on RAM cache use. To gather and interpret the data for each of these metrics, you must perform some polling and calculations: First, for each OID, you must poll for data. Then, for each graph metric, you perform a calculation using the OID data. Table 11.10 shows the individual OIDS that you must use to poll for RAM Cache data. Table 11.10 Required OIDs for polling for data on RAM Cache use Performance Graph (Configuration utility) RAM Cache Utilization
Graph Metric
Required SNMP OID
Hit Rate
sysHttpStatRamcacheHits (.1.3.6.1.4.1.3375.2.1.1.2.4.46) sysHttpStatRamcacheMisses (.1.3.6.1.4.1.3375.2.1.1.2.4.47)
Byte Rate
sysHttpStatRamcacheHitBytes (.1.3.6.1.4.1.3375.2.1.1.2.4.49) sysHttpStatRamcacheMissBytes (.1.3.6.1.4.1.3375.2.1.1.2.4.50)
Eviction Rate
sysHttpStatRamcacheEvictions (.1.3.6.1.4.1.3375.2.1.1.2.4.54) sysHttpStatRamcacheHits (.1.3.6.1.4.1.3375.2.1.1.2.4.46) sysHttpStatRamcacheMisses (.1.3.6.1.4.1.3375.2.1.1.2.4.47)
For example, the following steps show how to collect data on RAM Cache use for the Hit Rate graph metric: 1.
Poll the OID sysHttpStatRamcacheHits (.1.3.6.1.4.1.3375.2.1.1.2.4.46). This results in a value of .
2.
Poll the OID sysHttpStatRamcacheMisses (.1.3.6.1.4.1.3375.2.1.1.2.4.47). This results in a value of .
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
8/13
06/11/13
AskF5 | Manual Chapter: SNMP 3.
Calculate the value of the Hit Rate graph metric using the calculation shown in Table 11.11 ( / ( + ) *100).
Table 11.11 Required calculations for interpreting metrics on RAM Cache use Performance Graph (Configuration utility) RAM Cache Utilization
Graph Metric
Required SNMP OID
Hit Rate
/ ( + ) *100
Byte Rate
/ ( + ) *100
Eviction Rate
/ ( + ) *100
Collecting data on CPU use You can use SNMP commands to gather and interpret data on CPU use on the BIGIP system. Specifically, you can gather and interpret data for these types of graph metrics: CPU[0n] and Global Host CPU Usage For these graph metrics, you can either instruct the BIGIP system to collect the data automatically, based on a predefined polling interval, or you can use a polling interval of your choice. In either case, you use the MIBs named sysMultiHostCpu and sysGlobalHostCpu, respectively. Collecting data based on a predefined polling interval is the recommended way to collect CPU[0n] and Global Host CPU Usage graph metrics. However, you can also perform the calculation manually, if you want to use a polling interval other than 5 seconds, one minute, or five minutes. For the procedure on collecting CPU[0n] and Global Host CPU Usage graph metrics based on a predefined polling interval, see Using a predefined polling interval, on this page. For the procedure on collecting this performance data manually, see Using a custom polling interval. TMM CPU Usage For these graph metrics, there is no predefined polling interval for this MIB; therefore, you must choose a polling interval and perform the calculations manually. To perform the calculations, you use the MIB sysStatTm. For more information, see Using a custom polling interval.
Using a predefined polling interval The sysMultiHostCpu and sysGlobalHostCpu MIBs include some special CPU usage ratio OIDs that cause the BIGIP system to automatically calculate graph metrics for you. The particular CPU usage ratio OID that you use is based on a predefined polling interval that you want the BIGIP system to use when performing the calculation: five seconds, one minute, or five minutes. Specifically, a CPU usage ratio OID: Polls each individual CPU OID twice Calculates the delta of the two polls Performs a calculation using all delta values (that is, delta values from all OIDs polled) The sysMultiHostCpu usage ratio OIDs available for you to use are: sysMultiHostCpuUsageRatio (uses a 5second polling interval) sysMultiHostCpuUsageRatio5s (also uses a 5second polling interval) sysMultiHostCpuUsageRatio1m (uses a 1minute polling interval) sysMultiHostCpuUsageRatio5m (uses a 5minute polling interval) The sysGlobalHostCpu usage ratio OIDs available for you to use are: sysGlobalHostCpuUsageRatio (uses a 5second polling interval) sysGlobalHostCpuUsageRatio5s (also uses a 5second polling interval) sysGlobalHostCpuUsageRatio1m (uses a 1minute polling interval) sysGlobalHostCpuUsageRatio5m (uses a 5minute polling interval) Table 11.12 shows the individual OIDS that the BIGIP system polls for CPU[0n] graph metrics, based on 5second, 1minute, or 5minute intervals. Note that for each polling interval, the MIB also includes the pertinent CPU usage ratio OID or OIDs that you use to initiate the automatic polling and resulting delta calculations. Table 11.12 Required OIDs for automatic collection of CPU[0n] graph metrics Performance Graph (Configuration
Graph
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
9/13
06/11/13
AskF5 | Manual Chapter: SNMP utility)
Metric
Required SNMP OIDs
CPU Usage
CPU[0n]
5second Polling Interval sysMultiHostCpuUser5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.12) sysMultiHostCpuNice5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.13) sysMultiHostCpuSystem5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.14) sysMultiHostCpuIdle5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.15) sysMultiHostCpuIrq5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.16) sysMultiHostCpuSoftirq5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.17) sysMultiHostCpuIowait5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.18) sysMultiHostCpuUsageRatio5s (.1.3.6.1.4.1.3375.2.1.7.5.2.1.19) sysMultiHostCpuUsageRatio (.1.3.6.1.4.1.3375.2.1.7.5.2.1.11) 1minute Polling Interval
sysMultiHostCpuUser1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.20) sysMultiHostCpuNice1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.21) sysMultiHostCpuSystem1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.22) sysMultiHostCpuIdle1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.23) sysMultiHostCpuIrq 1m(.1.3.6.1.4.1.3375.2.1.7.5.2.1.24) sysMultiHostCpuSoftirq1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.25 sysMultiHostCpuIowait1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.26) sysMultiHostCpuUsageRatio1m (.1.3.6.1.4.1.3375.2.1.7.5.2.1..26) 5minute Polling Interval
sysMultiHostCpuUse5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.28) sysMultiHostCpuNice5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.29) sysMultiHostCpuSystem5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.30) sysMultiHostCpuIdle5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.31) sysMultiHostCpuIrq5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.32 sysMultiHostCpuSoftirq5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.33) sysMultiHostCpuIowait5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.34) sysMultiHostCpuUsageRatio5m (.1.3.6.1.4.1.3375.2.1.7.5.2.1.35) Table 11.13 shows the individual OIDS that the BIGIP system polls for Global Host CPU Usage graph metrics, based on fivesecond, 1minute, or 5minute intervals. Note that for each polling interval, the MIB also includes the pertinent CPU usage ratio OID or OIDs that you use to initiate the automatic polling and resulting delta calculations. Table 11.13 Required OIDs for automatic collection of Global Host CPU Usage graph metrics Performance Graph (Configuration utility)
Graph Metric
Required SNMP OIDs 5second Polling Interval sysGlobalHostCpuUser5s (.1.3.6.1.4.1.3375.2.1.1.2.20.14) sysGlobalHostCpuNice5s (.1.3.6.1.4.1.3375.2.1.1.2.20.15) sysGlobalHostCpuSystem5s (.1.3.6.1.4.1.3375.2.1.1.2.20.16) sysGlobalHostCpuIdle5s (.1.3.6.1.4.1.3375.2.1.1.2.20.17) sysGlobalHostCpuIrq5s (.1.3.6.1.4.1.3375.2.1.1.2.20.18)
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
10/13
06/11/13
AskF5 | Manual Chapter: SNMP CPU Usage
Gobal Host CPU Usage
sysGlobalHostCpuSoftirq5s (.1.3.6.1.4.1.3375.2.1.1.2.20.19) sysGlobalHostCpuIowait5s (.1.3.6.1.4.1.3375.2.1.1.2.20.20) sysGlobalHostCpuUsageRatio5s (.1.3.6.1.4.1.3375.2.1.1.2.20.21) sysGlobalHostCpuUsageRatio (.1.3.6.1.4.1.3375.2.1.1.2.20.13) 1minute Polling Interval
sysGlobalHostCpuUser1m (.1.3.6.1.4.1.3375.2.1.1.2.20.22) sysGlobalHostCpuNice1m (.1.3.6.1.4.1.3375.2.1.1.2.20.23) sysGlobalHostCpuSystem1m (.1.3.6.1.4.1.3375.2.1.1.2.20.24) sysGlobalHostCpuIdle1m (.1.3.6.1.4.1.3375.2.1.1.2.20.25) sysGlobalHostCpuIrq1m (.1.3.6.1.4.1.3375.2.1.1.2.20.26) sysGlobalHostCpuSoftirq1m (.1.3.6.1.4.1.3375.2.1.1.2.20.27) sysGlobalHostCpuIowait1m (.1.3.6.1.4.1.3375.2.1.1.2.20.28) sysGlobalHostCpuUsageRatio1m (.1.3.6.1.4.1.3375.2.1.1.2.20.29) 5minute Polling Interval
sysGlobalHostCpuUser5m (.1.3.6.1.4.1.3375.2.1.1.2.20.30) sysGlobalHostCpuNice5m (.1.3.6.1.4.1.3375.2.1.1.2.20.31) sysGlobalHostCpuSystem5m (.1.3.6.1.4.1.3375.2.1.1.2.20.32) sysGlobalHostCpuIdle5m (.1.3.6.1.4.1.3375.2.1.1.2.20.33) sysGlobalHostCpuIrq5m (.1.3.6.1.4.1.3375.2.1.1.2.20.34) sysGlobalHostCpuSoftirq5m (.1.3.6.1.4.1.3375.2.1.1.2.20.35) sysGlobalHostCpuIowait5m (.1.3.6.1.4.1.3375.2.1.1.2.20.36) sysGlobalHostCpuUsageRatio5m (.1.3.6.1.4.1.3375.2.1.1.2.20.37)
Using a custom polling interval The sysMultiHostCpu and sysGlobalHostCpu MIBs include additional OIDs that you can use to calculate CPU performance data based on a custom polling interval, that is, a polling interval that you choose. Using a custom polling interval requires you to poll each individual OID twice at an interval of your choice, calculate the delta of the two polls, and then perform a calculation according to a predefined formula. Table 11.14 includes a list of OIDs to use when collecting CPU performance data with a custom polling interval. Note that in this case, you do not use a CPU usage ratio OID. Following the table is the procedure for collecting the data. Table 11.14 Required SNMP OIDs for collecting CPU data manually Performance Graph (Configuration utility) CPU Usage
Graph Metric
Required SNMP OIDs
CPU[0n]
sysMultiHostCpuUser (.1.3.6.1.4.1.3375.2.1.7.5.2.1.4) sysMultiHostCpuNice (.1.3.6.1.4.1.3375.2.1.7.5.2.1.5) sysMultiHostCpuSystem (.1.3.6.1.4.1.3375.2.1.7.5.2.1.6) sysMultiHostCpuIdle (.1.3.6.1.4.1.3375.2.1.7.5.2.1.7) sysMultiHostCpuIrq (.1.3.6.1.4.1.3375.2.1.7.5.2.1.8) sysMultiHostCpuSoftirq (.1.3.6.1.4.1.3375.2.1.7.5.2.1.9) sysMultiHostCpuIowait (.1.3.6.1.4.1.3375.2.1.7.5.2.1.10)
Global Host CPU Usage
sysGlobalHostCpuCount (.1.3.6.1.4.1.3375.2.1.1.2.20.4) sysGlobalHostActiveCpu (.1.3.6.1.4.1.3375.2.1.1.2.20.5)
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
11/13
06/11/13
AskF5 | Manual Chapter: SNMP sysGlobalHostCpuUser (.1.3.6.1.4.1.3375.2.1.1.2.20.6) sysGlobalHostCpuNice (.1.3.6.1.4.1.3375.2.1.1.2.20.7) sysGlobalHostCpuSystem (.1.3.6.1.4.1.3375.2.1.1.2.20.8) sysGlobalHostCpuIdle (.1.3.6.1.4.1.3375.2.1.1.2.20.9) sysGlobalHostCpuIrq (.1.3.6.1.4.1.3375.2.1.1.2.20.10) sysGlobalHostCpuSoftirq (.1.3.6.1.4.1.3375.2.1.1.2.20.11) sysGlobalHostCpuIowait (.1.3.6.1.4.1.3375.2.1.1.2.20.12) TMM CPU Usage
sysStatTmTotalCycles (.1.3.6.1.4.1.3375.2.1.1.2.1.41) sysStatTmIdleCycles (.1.3.6.1.4.1.3375.2.1.1.2.1.42) sysStatTmSleepCycles (.1.3.6.1.4.1.3375.2.1.1.2.1.43)
To calculate CPU usage data manually 1.
Poll the OID sysMultiHostCpuUser (.1.3.6.1.4.1.3375.2.1.7.5.2.1.4) twice, at a 10second interval. This results in two values, and . Note: Although this example uses an interval of ten seconds, the interval can actually be any duration that you choose. 2.
Calculate the delta of the two poll values: = -
3.
Repeat steps one and two for each OID pertaining to the CPU[0n] graph metric.
4.
Repeat steps 1 and 2 again, using the OIDs from the MIBs sysStatTm and sysGlobalHostCpu.
5.
Calculate the values of the graph metrics, using the formulas shown in Table 11.15.
Table 11.15 Formulas for calculating metrics on CPU use Performance Graph (Configuration utility) CPU Usage
Graph Metric
Required calculations for CPU use
CPU[0n]
( + + ) / ( + + + + + + ) *100
Global Host CPU Usage
( + + ) / ( + + + + + + ) *100
TMM CPU Usage
(( ( + )) / ) *100
Collecting data on SSL transactions per second You can use SNMP commands with an OID to gather and interpret data on SSL performance, in terms of transactions per second. To gather and interpret the data for this metric, you must perform some polling and calculations: First, you must poll two OIDs separately and then add the two poll values together. Next, you must repeat the first two steps at some time interval (such as ten seconds) from the first two polls. Again, you add the two poll values together. Next, you calculate the delta of the two sums. Finally, you perform a calculation on the OID delta. Table 11.16 shows the OID that you must poll, retrieving two separate poll values for this OID. Table 11.16 Required OIDs for polling for data on SSL TPS Performance Graph (Configuration utility)
Graph Metrics
Required SNMP OIDs
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
12/13
06/11/13
AskF5 | Manual Chapter: SNMP SSL TPS
SSL TPS
sysClientsslStatTotNativeConns (.1.3.6.1.4.1.3375.2.1.1.2.9.6)
SSL TPS
SSL TPS
sysClientsslStatTotCompatConns (.1.3.6.1.4.1.3375.2.1.1.2.9.9)
SSL TPS
SSL TPS
sysServersslStatTotNativeConns (.1.3.6.1.4.1.3375.2.1.1.2.10.6)
SSL TPS
SSL TPS
sysServersslStatTotCompatConns (.1.3.6.1.4.1.3375.2.1.1.2.10.9)
For example, the following steps show how to collect data on SSL transactions for the SSL TPS graph metric: 1.
Poll the OID sysClientsslStatTotNativeConns (.1.3.6.1.4.1.3375.2.1.1.2.9.6).
2.
Poll the OID sysClientsslStatTotCompatConns (.1.3.6.1.4.1.3375.2.1.1.2.9.9).
3.
Add the two values together. This results in the value sysClientsslStatTotConns1.
4.
Poll the two OIDs again, within ten seconds of the previous polls (shown in steps 1 and 2). Note: Although this example uses an interval of ten seconds, the interval can actually be any duration that you choose. 5. 6.
Again, add the two values together. This results in the value sysClientsslStatTotConns2. Calculate the delta of the two sums: =
7.
Calculate the actual value of the SSL TPS graph metric using the calculation shown in Table 11.17. An example of the value is 10.
Table 11.17 Required calculations for interpreting metrics on SSL TPS Performance Graph (Configuration utility)
Graph Metric
Required calculations for SSL TPS
SSL TPS
SSL TPS
/
Table of Contents | Was this resource helpful in solving your issue? Yes this resource was helpful No this resource was not helpful I don‘t know yet
Additional Comments (optional) Type your comment here (1000 character limit)...
NOTE: Please do not provide personal information.
Please enter the words to the right:
Reload
Audio Help Submit
Home | Site Map | Contact F5 | Glossary | Policies | Trademarks © 1998–2013 F5 Networks, Inc. All rights reserved.
support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_tmos_concepts_11_0_0/tmos_snmp.html#1054044
13/13
View more...
Comments
