Original Publication Date: 05/22/2012
Updated Date: 11/20/2013
You should consider using this procedure under the following condition:
You must meet the following prerequisites to use this procedure:
Starting in BIG-IP 11.2.0, you can add customized MIB entries to a BIG-IP system to provide visibility to statistics and information that are not available through standard BIG-IP MIBs. These statistics and information can help you make decisions about the system configuration.
Customized MIB entries can be defined in a TCL file named custom_mib.tcl that you create and save on the BIG-IP system in the /config/snmp/ directory. You must register the customized entries and provide callback to the newly registered entries using the register_mib TCL command. To do so, use the following format when you specify the register_mib command in the custom MIB file:
register_mib "<oid>" <callback> <type>
The three arguments for the register_mib command are described in the following table:
||A customized OID with a format of .184.108.40.206 with a limit of four digits. The common root of a customized OID on the BIG-IP system is .220.127.116.11.4.1.3375.2.100.|
||A TCL procedure that is called when the registered OID is browsed. The procedure cannot have any arguments. The return value of the procedure is returned for the registered OID entry.|
||The type of OID entry you are customizing. Four types are supported: INT, STRING, GAUGE, and COUNTER.|
Creating the MIB file and customized MIB entries
To create the MIB file and customized MIB entries on the BIG-IP system, perform the following procedure:
Impact of procedure: None
Using a MIB browser to obtain the values of the newly registered MIB entries
You can use an snmp MIB browser to query the newly-created entries. To use the snmpwalk MIB browser to obtain the values of the newly-registered MIB entries, perform the following procedure:
Impact of procedure: Performing the following procedure should not have a negative impact on your system.
Note: The following links take you to a resource outside of AskF5, and it is possible that the information may be removed without our knowledge.