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. |
![]() | Configuring the SNMP agent There are a number of things you can do to configure the SNMP agent on the Access Policy Manager 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 Access Policy Manager 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. From the navigation pane, expand Overview, and click Welcome. From the Welcome screen, scroll down to Downloads. |
Configuring Access Policy Manager system information Specify a system contact name and the location of the Access Policy Manager system. |
Configuring client access to the SNMP agent Configure the Access Policy Manager 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. |
Contact Information The contact information is a MIB-II simple string variable defined by almost all SNMP boxes. The contact name usually contains a user name, as well as an email address. |
Machine Location The machine location is a MIB-II variable that almost all machines support. It is a simple string that defines the location of the machine. |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. The SNMP Agent Configuration screen opens. |
2. | In the Global Setup area, fill in the boxes. For more information, see the online help. |
3. | Click Update. |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. The SNMP Agent Configuration screen opens. |
2. | For the Client Allow List setting, select Host or Network, depending on whether the IP address you specify is a host system or a subnet. |
In the Address box, type an IP address or network address from which the SNMP agent can accept requests. |
4. | Click the Add button to add the host or network address to the list of allowed clients. |
5. | Click Update. |
If the access type of an object is... | And you set the access level of a community or user to... | Then access to the object is... |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. The SNMP Agent Configuration screen opens. |
2. | From Agent menu, choose Access (v1, v2c). The SNMP Access screen opens. |
3. |
5. | In the Community box, type the name of the SNMP community for which you are assigning an access level (in step 8). |
6. | In the Source box, type the source IP address. |
7. | In the OID box, type the OID for the top-most node of the SNMP tree to which the access applies. |
8. | For the Access setting, select an access level, either Read Only or Read/Write. (This access level applies to the community name you specified in step 6.) |
9. | Click Finished. |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. The SNMP Agent Configuration screen opens. |
2. | From Agent menu, choose Access (v3). The SNMP Access screen opens. |
3. |
4. | In the User Name box, type a user name for which you are assigning an access level (in step 8). |
5. | For the Authentication setting, select a type of authentication to use, and then type and confirm the users password. |
6. |
Check the Use Authentication Password box. |
7. | In the OID box, type the object identifier (OID) for the top-most node of the SNMP tree to which the access applies. |
8. | For the Access setting, select an access level, either Read Only or Read/Write. (This access level applies to the user name that you specified in step 5). |
9. | Click Finished. |
/etc/alertd/alert.conf Contains default SNMP traps. |
/config/user_alert.conf Contains user-defined SNMP traps. |
The SNMP agent on the Access Policy Manager system stops or starts. By default, this trap is enabled. |
The Access Policy Manager system receives an authentication warning, generated when a client system attempts to access the SNMP agent. By default, this trap is disabled. |
The Access Policy Manager system receives any type of warning. By default, this trap is enabled. |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. This opens the SNMP Agent Configuration screen. |
2. | From the Traps menu, choose Configuration. This displays the SNMP Trap Configuration screen. |
3. | To send traps when someone starts or stops the SNMP agent, verify that the Agent Start/Stop box is checked. |
4. | To send notifications when authentication warnings occur, check the Agent Authentication box. |
5. | To send notifications when certain warnings occur, verify that the Device box is checked. |
6. | Click Update. |
1. | On the Main tab of the navigation pane, expand System, and click SNMP. The SNMP Agent Configuration screen opens. |
2. | From the Traps menu, choose Destination. The SNMP Destination screen opens. |
3. |
4. | For the Version setting, select an SNMP version number. |
5. | In the Community box, type the community name for the SNMP agent running on the Access Policy Manager system. |
6. | In the Destination box, type the IP address of the SNMP management system. |
7. | In the Port box, type the SNMP management system port number that is to receive the traps. |
8. | Click Finished. |
F5-BIGIP-COMMON-MIB.txt This MIB file contains common information and all notifications (traps). |
F5-BIGIP-LOCAL-MIB.txt This is an enterprise MIB file that contains specific information for properties associated with specific Access Policy Manager system features related to local traffic manager (such as virtual servers, pools, and SNATs). |
F5-BIGIP-SYSTEM-MIB.txt. The F5-BIGIP-SYSTEM-MIB.txt MIB file includes global information on system-specific objects. |
F5-BIGIP-APM-MIB.txt. This MIB file contains specific information for properties associated with viewing and accessing access profile and secure connectivity statistics. |
1. | On the navigation pane, select the About tab. |
2. | Scroll to the Downloads section, and locate the SNMP MIBs section. |
Get profile information such as the total number of concurrent authentication sessions. |
The Access Policy Manager system implementation of RMON supports four of the nine RMON groups. The four supported RMON groups are: statistics, history, alarms, and events. |
The RMON-MIB.txt file monitors the Access Policy Manager system interfaces (that is, sysIfIndex), and not the standard Linux interfaces. |
For hardware reasons, the packet-length-specific 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. |
Performance Graph (Configuration utility) | ||
Performance Graph (Configuration utility) | ||
Active Connections (summary graph | ||
Active Connections (detailed graph) | ||
Performance Graph (Configuration utility) | ||
New Connections (summary graph) | ||
Total New Connections (detailed graph) | ||
New PVA Connections (detailed graph) | ||
New SSL Connections (detailed graph) | ( 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) ) / time | |
( 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) ) / time | ||
New Accepts/Connects (detailed graph) | ||
Performance Graph (Configuration utility) | ||
Throughput (summary graph) | ( (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) )*8 ) / time | |
( (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) )*8 /) time | ||
Throughput (detailed graph) | ||
Performance Graph (Configuration utility) | ||
Performance Graph (Configuration utility) | ||
sysHttpStatRamcacheHits (.1.3.6.1.4.1.3375.2.1.1.2.4.46) / (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) ) *100 | ||
sysHttpStatRamcacheHitBytes (.1.3.6.1.4.1.3375.2.1.1.2.4.49) / (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) ) *100 | ||
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)) *100 |
Performance Graph (Configuration utility) | ||
(DeltaCpuUser + DeltaCpuNice + DeltaCpuSystem) / (DeltaCpuUser + DeltaCpuNice + Delta CpuIdle + DeltaCpuSystem + DeltaCpuIrq + DeltaCpuSoftirq + DeltaCpuIowait) | ||
(DeltaTmTotalCycles - (DeltaTmIdleCycles + DeltaTmSleepCycles) / DeltaTmTotalCycles) *100 |
2. | For each OID, calculate the delta of the values from the two polls, as shown in the following formulas. Note that in the formulas shown, values such as sysHostCpuUser2 and sysHostCpuUser1 represent the values that result from the two polls you performed in step 1 for that OID. |
3. | Using the resulting delta values (for example, DeltaCpuUser), calculate the CPU[0-n] metric, according to the formula shown in table 14.9. |
2. | For each OID, calculate the delta of the values from the two polls, as shown in the following example. Note that in the formula shown, values such as sysStatTmTotalCycles2 and sysStatTmTotalCycles1 represent the values that result from the two polls you performed in step 1 for each OID. |
3. | Using the resulting delta values (for example, DeltaTmTotalCycles), calculate the TMM CPU Usage metric, according to the formula shown in table 14.9. |
Performance Graph (Configuration utility) | ||
apmAccessStatCurrentActiveSessions (.1.3.6.1.4.1.3375.2.6.1.4.3) |
Performance Graph (Configuration utility) | ||