Table Of Contents
DistributedDirector Enhancements for Cisco IOS Release 12.2(4)T3
Supported Standards, MIBs, and RFCs
Configuring Default Priorities for Metrics
Setting the Protocol Used for RTT Probing
Verifying Default Priorities for Metrics
Specifying Default Priorities for Metrics Example
Setting the Protocol for RTT Probing Example
Enabling the DNS Server Example
ip director default priorities
DistributedDirector Enhancements for Cisco IOS Release 12.2(4)T3
Feature History
This feature module describes four new commands and one modified command for DistributedDirector in Cisco IOS Release 12.2(4)T3. This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Cisco DistributedDirector can use all of its decision-making metrics to determine the best server for a client request. From the configured metrics, DistributedDirector chooses the best distributed server and returns its IP address to the local Domain Name System (DNS) server for the client.
The new ip director default priorities command specifies the default priorities for each type of metric. The default priorities will take effect if no host-specific priorities are specified in the ip director host priority command or in the corresponding DNS text record. If a metric does not have a priority or a weight specified, the metric is ignored.
The new ip director drp rttprobe command sets the protocol used by Director Response Protocol (DRP) agents for round trip time (RTT) probing. The protocols to be set are the Transmission Control Protocol (TCP) and the Internet Control Message Protocol (ICMP). Both protocols can be activated, in which case DistributedDirector will instruct DRP agents to return the RTT collected from either the TCP or the ICMP, whichever becomes available first. Using the no form of the command causes DistributedDirector to stop using a specified protocol for RTT probing. At any time, one of the protocols must be activated, and both protocols can be activated if desired. The default protocol is TCP.
The new ip dns server command enables the DNS server on the router.
The new show ip director default priority command is used to verify the default priority for any metric.
The ip director default-weights command name has been modified slightly in this release. The command name is now ip director default weights.
Benefits
The ip director default priorities command sets defaults for DistributedDirector metrics.
The ip director drp rttprobe command allows users to select the protocol for RTT probing that works best for your system.
The ip dns server command allows users to activate and use the DNS server on the router.
The show ip director default priority command allows user to verify the default priority for any metric.
Supported Platforms
As of the Cisco IOS 12.2(104)T release, Distributed Director is an integrated IOS feature, based on the Enterprise Plus image bundle, on the 2600, 3600, and 7200 series platforms.
•
Cisco DistributedDirector 2500
•
Cisco DistributedDirector 2600
•
Cisco DistributedDirector 3620
•
Cisco DistributedDirector 3640
•
Cisco DistributedDirector 3660
•
Cisco DistributedDirector 7200
Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.
Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
No new standards are supported by these commands.
MIBs
No new MIBs are supported by these commands.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
No new RFCs are supported by these commands.
Configuration Tasks
See the following sections for configuration tasks for this feature.
•
Configuring Default Priorities for Metrics (optional)
•
Setting the Protocol Used for RTT Probing (optional)
•
Enabling the DNS Server (optional)
Configuring Default Priorities for Metrics
To set a default priority for a metric, use the ip director default priorities command.
To remove a default priority for a metric, use the no ip director default priorities command.
Setting the Protocol Used for RTT Probing
To set the protocol used by DRP agents for RTT probing, use the ip director drp rttprobe command.
To return to the default protocol, use the no ip director drp rttprobe command.
Enabling the DNS Server
To enable the DNS server on a router, use the ip dns server command.
To disable the DNS server on a router and return to the default configuration, use the no ip dns server command.
Verifying Default Priorities for Metrics
To verify a default priority for a metric, enter the show ip director default priority command. The following example shows output from this command.
Router# show ip director default priorityDirector default metric priorities:random priority = 2DRP route lookup external to AS priority = 1administrative preference priority = 0DRP route lookup internal to AS priority = 0DRP distance to associated server priority = 0portion priority = 0Round-trip time from DRP to client priority = 0DFP originated weight priority = 0Route-map evaluation priority = 0Configuration Examples
This section provides the following configuration examples:
•
Specifying Default Priorities for Metrics Example
•
Setting the Protocol for RTT Probing Example
•
Enabling the DNS Server Example
Specifying Default Priorities for Metrics Example
In the following example, a default priority of 1 is configured for the drp-ext metric, and a default priority of 2 is configured for the random metric:
ip director default priorities drp-ext 1 random 2Setting the Protocol for RTT Probing Example
In the following example, the command configures ICMP (in addition to the default of TCP) to be used by DRP agents for RTT probing:
ip director drp rttprobe icmpEnabling the DNS Server Example
In the following example, the DNS server is enabled.
ip dns serverCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New Commands
•
ip director default priorities
Modified Commands
ip director default priorities
To set a default priority for a specific metric on the DistributedDirector, use the ip director default priorities command in global configuration mode. To remove a default priority for a metric, use the no form of this command.
ip director default priorities {[drp-int n] [drp-ext n] [drp-ser n] [random n] [admin n]
[drp-rtt n] [portion n] [availability n] [route-map n]}no ip director default priorities {[drp-int n] [drp-ext n] [drp-ser n] [random n] [admin n] [drp-rtt n] [portion n] [availability n] [route-map n]}
Syntax Description
Defaults
No default priorities are specified.
Command Modes
Global configuration
Command History
Usage Guidelines
The default priorities specified will take effect if no priorities are specified in the ip director host priority command or in the corresponding DNS text record for that host.
The number 1 denotes the highest priority. To set the default priority for several metrics, enter the metric keywords and values to be configured on the same line as the ip director default priorities command.
Examples
The following example shows the default priority for the drp-ext metric configured as 1 (which is the highest priority) and the default priority for the random metric configured as 2:
ip director default priorities drp-ext 1 random 2Related Commands
ip director default weights
To configure default weight metrics for DistributedDirector, use the ip director default weights command in global configuration mode. To set the defaults to zero, use the no form of this command.
ip director default-weights {[drp-int n] [drp-ext n] [drp-ser n] [drp-rtt n] [random n]
[admin n] [portion n] [availability n] [route-map n]}no ip director default-weights {[drp-int n] [drp-ext n] [drp-ser n] [drp-rtt n] [random n] [admin n] [portion n] [availability n] [route-map n]}
Syntax Description
Defaults
No default weights are specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Not all the metrics need to be configured; however, at least one metric must be configured when this command is used.
Default weights are used for all host names sorted by DistributedDirector. To override default weights for a certain host, specify host-specific weights in the private Domain Name System (DNS) server configuration.
When the associated metric is referenced in a sorting decision, it will always be multiplied by the appropriate metric weight. By this means, you can specify that some metrics be weighted more than others. You may use experimentation to determine the weights that you want to use, and the higher the number, the greater the weight. The weights given do not have to add up to 100.
Examples
The following command configures default weights for the internal and external metrics:
ip director default weight drp-int 10 drp-ext 90Related Commands
ip director drp rttprobe
To set the protocol used by Director Response Protocol (DRP) agents for round-trip time (RTT) probing in DistributedDirector, use the ip director drp rttprobe command in global configuration mode. To disable the use of a protocol, use the no form of the command.
ip director drp rttprobe [tcp | icmp]
no ip director drp rttprobe [tcp | icmp]
Syntax Description
Defaults
TCP
Command Modes
Global configuration
Command History
Usage Guidelines
Both protocols can be activated, in which case DistributedDirector will instruct DRP agents to return the RTT collected from either the TCP or Internet Control Message Protocol (ICMP) protocol, whichever becomes available first. At any time, at least one of the protocols must be active.
To use only one protocol, enable the protocol you want to use, and then disable the protocol that was already configured.
Router(config)# ip director drp rttprobe icmpRouter(config)# no ip director drp rttprobe tcpExamples
The following example shows that ICMP is configured for use by DRP agents for RTT probing:
Router(config)# ip director drp rttprobe icmpRelated Commands
ip dns server
To enable the Domain Name System (DNS) server on a router, use the ip dns server command in global configuration mode. To disable the DNS server, use the no form of the command.
ip dns server
no ip dns server
Syntax Description
This command has no arguments or keywords.
Defaults
The DNS server is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the command to enable the DNS server as needed.
Examples
In the following example, the DNS server is enabled:
ip dns servershow ip director default
To verify default metric configuration information for DistributedDirector metrics, use the show ip director default command in privileged EXEC mode.
show ip director default [priority | weight]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to verify default metric configurations.
Examples
The following is sample output from the show ip director default priority command:
Router# show ip director default priorityDirector default metric priorities:random priority = 2DRP route lookup external to AS priority = 1administrative preference priority = 0DRP route lookup internal to AS priority = 0DRP distance to associated server priority = 0portion priority = 0Round-trip time from DRP to client priority = 0DFP originated weight priority = 0Route-map evaluation priority = 0Related Commands
Command Descriptionip director default priorities
Sets default priorities for DistributedDirector metrics.