Table Of Contents
Dynamic Feedback Protocol Support in DistributedDirector
Supported Standards, MIBs, and RFCs
Configuring DFP Support in DistributedDirector
Verifying DFP Support in DistributedDirector
DFP Support in DistributedDirector Example
ip director server availability
ip director server port availability
Dynamic Feedback Protocol Support in DistributedDirector
This feature module describes the Dynamic Feedback Protocol (DFP) Support in DistributedDirector feature and includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
DistributedDirector can obtain load information from Cisco LocalDirector, Catalyst 4840g, and other clients using Dynamic Feedback Protocol (DFP). This protocol allows the user to configure the DistributedDirector to communicate with various DFP agents. The DistributedDirector tells the DFP agents how often they should report load information; then the DFP agent can tell the DistributedDirector which LocalDirector cluster to remove from providing service.
Benefits
DFP support enables DistributedDirector to make server and site selection on the basis of server load, in addition to other DistributedDirector metrics.
Related Documents
For more information on the Cisco DistributedDirector, see the following documents, which are located on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml:
•
•
•
•
•
•
Supported Platforms
•
•
•
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
None
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Configuration Tasks
See the following sections for the configuration tasks for this feature. This task is optional.
•
•
Configuring DFP Support in DistributedDirector
To configure DFP support in DistributedDirector, use the following command in global configuration mode:
Verifying DFP Support in DistributedDirector
To verify that the DistributedDirector is configured with DFP support for all specified IP addresses, use the show ip director dfp command. To verify that the DistributedDirector is configured with DFP support for a single IP address, use the show ip director dfp command.
Configuration Examples
This section provides the following configuration example DFP Support in DistributedDirector Example.
DFP Support in DistributedDirector Example
In the following example, the DistributedDirector is configured to communicate with a specified DFP agent:
ip director dfp 10.0.0.1 retry 3 attempts 60 timeout 6000Command Reference
This section documents new and modified commands. All other commands used with the DistributedDirector are documented in the "Command Summary" and "Reference" sections of the Cisco DistributedDirector installation and configuration guides.
•
•
ip director default-weights
To configure default weight metrics for the DistributedDirector, use the ip director default-weights global configuration command. To restore the default, 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
The availability default value is 65,535.
Command Modes
Global configuration
Command History
11.1(18)IA
This command was introduced.
12.1(5)T
The availability and route-map metrics were added.
Usage Guidelines
Not all of 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 the DistributedDirector. To override default weights for a certain host, specify host-specific weights in the private DNS server configuration.
When the associated metric is referenced in the sorting decision, it will always be multiplied by the appropriate metric weight. In this way, you can specify that some metrics be weighted more than others. You may determine the weights that you want to use through experimentation. The weights given do not need to add up to 100.
The new availability metric allows the DistributedDirector to attempt to create a TCP connection to each distributed server on a configured port over a configurable time interval.
Examples
The following command configures default weights for the internal and external metrics:
ip director default-weights drp-int 10 drp-ext 90Related Commands
ip director dfp
To configure the DistributedDirector Dynamic Feedback Protocol (DFP) agent with which the DistributedDirector should communicate, use the ip director dfp global configuration command. To turn off the DFP agent, use the no form of this command.
ip director dfp ip-address [port] [retry n] [attempts n] [timeout n]
no ip director dfp ip-address [port] [retry n] [attempts n] [timeout n]
Syntax Description
Syntax Description
The port default value is 8080.
The retry default value is 5 attempts.
The attempts default value is 10,000 seconds.
The timeout default value is 10,000 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
A connection is attempted a specified number of times with a delay of a specified number of seconds between each attempt. Once a connection is established, the DFP protocol will run. If a time interval update has not occurred for this DFP session, the connection breaks and is reestablished as described above.
Examples
The following example configures the DistributedDirector to communicate with a specified DFP agent:
ip director dfp 10.0.0.1 retry 3 attempts 60 timeout 6000
ip director dfp security
To configure a security key for use when connecting to the Dynamic Feedback Protocol (DFP) client named, use the ip director dfp security global configuration command. To turn off the security key, use the no form of this command.
ip director dfp security ip-address md5 string [timeout]
no ip director dfp security ip-address md5 string [timeout]
Syntax Description
Defaults
The timeout default value is 0 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
The ip director dfp security command should be entered before configuring the ip director dfp command, resulting in a connection being made, but it can be entered independently of making a connection.
DFP allows servers to take themselves Out-of-Service and place themselves back In-Service. This function could result in a security risk because a network that is hacked could be shut down even though all the servers are still performing. An optional security vector is included in DFP to allow each message to be verified. The security vector is used to describe the security algorithm being used and to provide the data for that algorithm. The security vector itself is also extensible in that it specifies which security algorithm is being used. This specification allows different levels of security from MD5 to Data Encryption Standard (DES) to be used without overhauling the protocol and disrupting any installed base of equipment. If a receiving unit is configured for the specified security type, all DFP packets must contain that security vector or they are ignored. If a receiving unit is not configured for any security type, the security vector does not have to be present, and if it is present, it is ignored while the rest of the message is processed normally.
Examples
The following example configures the security key hello:
ip director dfp security 10.0.0.1 md5 hello 60Related Commands
ip director dfp
Configures the DistributedDirector DFP agent with which the DistributedDirector should communicate.
ip director host priority
To configure the order in which the DistributedDirector considers metrics when picking a server, use the ip director host priority global configuration command. To turn off metric priorities, use the no form of this command.
ip director host host-name priority {[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 host host-name priority {[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
The availability default value is 65,535.
Command Modes
Global configuration
Command History
11.1(18)IA
This command was introduced.
12.1(5)T
The availability and route-map metrics were added.
Usage Guidelines
Not all of the metrics need to be specified, but at least one must be specified.
The new availability metric allows the DistributedDirector to attempt to create a TCP connection to each distributed server on a configured port over a configurable time interval.
If multiple servers end up with the same metric value, the next metric is considered to determine the "best" server. If multiple metrics have the same priority value, the metrics are added to obtain a composite metric. For example, if two metrics have the same priority value, they are first multiplied by their weight values (if specified) and then added together to form the composite metric.
If you do not specify weights for a group of distributed servers, there are no default weights for the Director, and if you have specified priority values, the weight values are set to 1.
Any metrics that have a nonzero weight and that are assigned no priority value are set to a priority value of 101. They are considered after all other metrics that have priority values. As a result, if no priority values are specified for any metric, metrics are treated additively to form one composite metric.
If you do not use priority and multiple servers have the same metric value, the server whose last IP address was looked at will be returned as the "best" server. If you want to return a random IP address in the case of a tie, use metric priority with the random metric as the last criterion.
To turn off all priorities on all metrics associated with the defined host name, use the no ip director host priority command. You can turn off the priority for a specific metric or metrics using the no ip director host host-name priority [drp-int n] [drp-ext n] [drp-ser n] [drp-rtt n] [random n] [admin n] [portion n] [availability n] [route-map n] command.
Examples
The following example sets the external metric as the first priority and the administrative metric as the second priority:
ip director host www.xyz.com priority drp-ext 1 admin 2Related Commands
ip director host connect
Enables the DistributedDirector to verify that a server is available.
show ip director hosts
Displays the DistributedDirector host information.
ip director host weights
To set host-specific weights for the metrics that the DistributedDirector uses to determine the best server within a specific host name, use the ip director host weights global configuration command. To turn off weights for a host, use the no form of this command.
ip director host host-name 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 host host-name 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
Note
Defaults
The availability default value is 65,535.
Command Modes
Global configuration
Command History
11.1(25)IA
This command was introduced.
12.0(3)T
This command was integrated into the Cisco IOS Release 12.0(3)T.
12.1(5)T
The availability and route-map metrics were added.
Usage Guidelines
Use host-specific weights when you want to use different metric weights for different virtual host names (for example, www.xyz.com and ftp.xyz.com).
The new availability metric allows the DistributedDirector to attempt to create a TCP connection to each distributed server on a configured port over a configurable time interval.
If desired, host-specific weights can instead be configured on the DistributedDirector default DNS server.
For example, you could configure host-specific weights with the following DNS TXT record:
hostname in txt "ciscoDD: weights {[drp-int n] [drp-ext n] [drp-ser n] [random n] [admin n]}"To use the default weights for all metrics associated with this host name, use the no ip director host weights command. To use the default weights for a specific metric or metrics, use the no ip director host host-name weights [drp-int n] [drp-ext n] [drp-ser n] [drp-rtt n] [random n] [admin n] [portion n] [availability n] [route-map n] command.
Examples
The following example sets the DRP internal metric to 4:
ip director host www.xyz.com weights drp-int 4Related Commands
ip director default-weights
Configures default weight metrics for the DistributedDirector.
show ip director hosts
Displays the DistributedDirector host information.
ip director server availability
To configure a default availability value for all ports on a server, use the ip director server availability global configuration command. To restore the default, use the no form of this command.
ip director server ip-address availability {availability-value | dfp [availability-value]}
no ip director server ip-address availability {availability-value | dfp [availability-value]}
Syntax Description
Defaults
The availability default value is 65,535.
Command Modes
Global configuration
Command History
Usage Guidelines
There are two methods for specifying a default availability value. These two methods exist because the LocalDirector and the DistributedDirector deal with values in two different ways. All metrics for the DistributedDirector are arranged such that lower is better; however the LocalDirector load information is calculated such that higher is better. Thus, the DistributedDirector translates the metric value upon receipt from the LocalDirector by subtracting the availability from the maximum possible value of 65,535.
Examples
To configure a default availability to be used if there is no other valid availability information, the following configuration would suffice. The following example shows how to specify the LocalDirector load and DistributedDirector availability, respectively:
ip director server 10.0.0.1 availability dfp 1ip director server 10.0.0.1 availability 65534To make the availability clear and to allow for specifying numbers in both schemes easily, there are two methods of specifying availability information. If the servers are running multiple serves, it may be necessary to configure the default availability value on a per-port basis by using the ip director server port availability command.
ip director server 10.0.0.1 port availability dfp 65535ip director server 10.0.0.20 port availability dfp 65535Related Commands
ip director server port availability
Configures a default availability value for a specific port on a server.
ip director server port availability
To configure a default availability value for a specific port on a server, use the ip director server port availability global configuration command. To restore the default, use the no form of this command.
ip director server ip-address port availability {availability-value | dfp [availability-value]}
no ip director server ip-address port availability {availability-value | dfp [availability-value]}
Syntax Description
Defaults
The availability default value is 65,535.
Command Modes
Global configuration
Command History
Usage Guidelines
There are two methods for specifying a default availability value. These two methods exist because the LocalDirector and the DistributedDirector deal with values in two different ways. All metrics for the DistributedDirector are arranged such that lower is better; however the LocalDirector load information is calculated such that higher is better. Thus, the DistributedDirector translates the metric value upon receipt from the LocalDirector by subtracting the availability from the maximum possible value of 65,535.
Examples
To make the availability clear and to allow for specifying numbers in both schemes easily, there are two methods of specifying availability information. If the servers are running multiple serves, it may be necessary to configure the default availability value on a per-port basis by using the ip director server port availability command.
ip director server 10.0.0.1 port availability dfp 65535ip director server 10.0.0.20 port availability dfp 65535To configure a default availability to be used if there is no other valid availability information, the following configuration would suffice. The following example shows how to specify the LocalDirector load and DistributedDirector availability, respectively:
ip director server 10.0.0.1 availability dfp 1ip director server 10.0.0.1 availability 65534Related Commands
ip director server availability
Configures a default availability value for all ports on a server.
show ip director dfp
To display information about the current status of the DistributedDirector connections with a particular Dynamic Feedback Protocol (DFP) agent, use the show ip director dfp EXEC command.
show ip director dfp [host-name | ip-address]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip director dfp command:
Router# show ip director dfp172.24.9.9:Max retries: 5Timeout between connect attempts: 60Timeout between updates: 90Last update received: 00:00:12 agoServer Port BindID Address Mask172.28.9.9 80 0 0.0.0.0 0.0.0.0192.168.25.25Max retries: 5Timeout between connect attempts: 60Timeout between updates: 90Last update received: 00:00:44 agoServer Port BindID Address Mask192.168.30.30 80 0 0.0.0.0 0.0.0.0
Guest
