Table Of Contents
Configuring Cisco IOS IP SLAs DNS Operations
Information About IP SLAs DNS Operations
How to Configure IP SLAs DNS Operations
Configuring an IP SLAs DNS Operation on the Source Device
Configuring a Basic DNS Operation on the Source Device
Configuring a DNS Operation with Optional Parameters on the Source Device
Configuration Examples IP SLAs DNS Operations
Example: Configuring a DNS Operation
Feature Information for IP SLAs DNS Operations
Configuring Cisco IOS IP SLAs DNS Operations
First Published: August 14, 2006Last Updated: January 6, 2011
This module describes how to configure the Cisco IOS IP Service Level Agreements (SLAs) Domain Name System (DNS) operation to measure the difference between the time taken to send a DNS request and receive a reply. This module also demonstrates how the results of the DNS operation can be displayed and analyzed to determine the DNS lookup time which is a critical element for determining the performance of a DNS or web server.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for IP SLAs DNS Operations" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About IP SLAs DNS Operations
•
How to Configure IP SLAs DNS Operations
•
Configuration Examples IP SLAs DNS Operations
•
Feature Information for IP SLAs DNS Operations
Information About IP SLAs DNS Operations
DNS Operation
The DNS operation measures the difference between the time taken to send a DNS request and receive a reply. DNS is used in the Internet for translating names of network nodes into addresses. The IP SLAs DNS operation queries for an IP address if you specify a host name, or queries for a host name if you specify an IP address.
In Figure 1 Router B is configured as the source IP SLAs device and a DNS operation is configured with the DNS server as the destination device.
Figure 1 DNS Operation
Connection response time is computed by measuring the difference between the time taken to send a request to the DNS server and the time a reply is received by Router B. The resulting DNS lookup time can help you analyze your DNS performance. Faster DNS lookup times translate to a faster web server access experience.
How to Configure IP SLAs DNS Operations
•
Configuring an IP SLAs DNS Operation on the Source Device (required)
•
Scheduling IP SLAs Operations (required)
Configuring an IP SLAs DNS Operation on the Source Device
Note
There is no need to configure an IP SLAs responder on the destination device.
Perform one of the following tasks:
•
Configuring a Basic DNS Operation on the Source Device
•
Configuring a DNS Operation with Optional Parameters on the Source Device
Configuring a Basic DNS Operation on the Source Device
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip sla operation-number
4.
dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number]
5.
frequency seconds
6.
end
DETAILED STEPS
Configuring a DNS Operation with Optional Parameters on the Source Device
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip sla operation-number
4.
dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number]
5.
history buckets-kept size
6.
history distributions-of-statistics-kept size
7.
history enhanced [interval seconds] [buckets number-of-buckets]
8.
history filter {none | all | overThreshold | failures}
9.
frequency seconds
10.
history hours-of-statistics-kept hours
11.
history lives-kept lives
12.
owner owner-id
13.
history statistics-distribution-interval milliseconds
14.
tag text
15.
threshold milliseconds
16.
timeout milliseconds
17.
end
DETAILED STEPS
Scheduling IP SLAs Operations
Restrictions
•
The frequency of all operations scheduled in a multioperation group must be the same.
•
Operation ID numbers are limited to a maximum of 125 characters. Do not give large integer values as operation ID numbers.
SUMMARY STEPS
1.
enable
2.
configure terminal
For individual IP SLAs operations only:
3.
ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
For multioperation scheduler only:
4.
ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]
5.
exit
6.
show ip sla group schedule
7.
show ip sla configuration
DETAILED STEPS
Examples
The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the DNS operation number 11.
Router# show ip sla configuration 11Complete Configuration Table (includes defaults)Entry number: 11Owner: DNS-TestTag: DNS-TestType of operation to perform: dnsTarget address: www.cisco.comSource address: 0.0.0.0Source port: 0Operation timeout (milliseconds): 9000Operation frequency (seconds): 60Next Scheduled Start Time: Start Time already passedGroup Scheduled: FALSELife (seconds): ForeverEntry Ageout (seconds): neverRecurring (Starting Everyday): FALSEStatus of entry (SNMP RowStatus): ActiveThreshold (milliseconds): 5000Number of statistic hours kept: 2Number of statistic distribution buckets kept: 1Statistic distribution interval (milliseconds): 20Number of history Lives kept: 0Number of history Buckets kept: 15History Filter Type: NoneTroubleshooting Tips
Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see Configuring Proactive Threshold Monitoring.
To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.
Configuration Examples IP SLAs DNS Operations
•
Example: Configuring a DNS Operation
Example: Configuring a DNS Operation
The following example shows how to configure a DNS operation as shown in Figure 1 from Router B to the DNS server (IP address 172.20.2.132). The operation is scheduled to start immediately. In this example, the target address is a hostname and the DNS operation will query the DNS server for the IP address associated with the hostname host1. No configuration is required at the DNS server.
Router B Configuration
ip sla 11dns host1 name-server 172.20.2.132frequency 50timeout 8000tag DNS-Testip sla schedule 11 start-time nowAdditional References
Related Documents
Related Topic Document TitleCisco IOS commands
Cisco IOS IP SLAs commands
Cisco IOS IP SLAs: general information
"Cisco IOS IP SLAs Overview" chapter of the Cisco IP SLAs Configuration Guide.
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
MIBs MIBs LinkCISCO-RTTMON-MIB
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for IP SLAs DNS Operations
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006-2010 Cisco Systems, Inc. All rights reserved.

