The CISCO-RTTMON-MIB, whose name still contains the initial feature-naming convention RTT, lets you configure most of the operations described in this chapter. Furthermore, the CISCO-RTTMON-MIB lets you monitor the operation results. The only exceptions, for both configuration and monitoring, are the Frame Relay and ATM operations.
The CISCO-RTTMON-MIB defines managed objects that enable a network administrator to do the following:
Query the supported operation types on the agent (similar to the output of the show ip sla application command), along with some administrative information such as the low-memory watermark and the estimated number of configurable operations.
Configure an operation along with all its parameters (type, frequency, interval, number of packets, packet size, tag, owner, timeout, target IP address, type of service, VRF, precision). The configuration of operation-specific details is also possible: the URL and HTTP version for the HTTP operation, the codec type for the VoIP operation, and so on.
Configure the operation scheduling, including the Recurring Function, Multiple Operation Scheduling, and Random Scheduling.
Configure the notification/trigger generation (see the "Thresholds and Notifications" section). Previous versions of the MIB specified four different notifications; these are now deprecated: rttMonConnectionChangeNotification, rttMonTimeoutNotification, rttMonThresholdNotification, and rttMonVerifyErrorNotification. The new MIB version specifies the generic notification rttMonNotification, which is used for any violation on any metric of interest.
Monitor the operational state of all operations, and collect the results. Two extra tables, specific to the HTTP and jitter operations, contain the detailed results of the last operation.
Configure the history and collect its results. The MIB limits the hours-of-statistics kept for the UDP Jitter operation to 2 hours. Configuring a larger value using the hours-of-statistics hours global configuration change does not increase the value beyond 2 hours. However, the Data Collection MIB can be used to collect historical data for the operation. The enhanced history feature is currently supported only with the CLI. SNMP support will be added later.
Configure and monitor the MD5 Authentication for Control Protocol.
Note that, when the rttMonCtrlAdminNvgen MIB variable is set to true, its associated operation is shown in the output of the show running command and therefore can be saved in nonvolatile memory (NVRAM). The default rttMonCtrlAdminNvgen value is false.