-
Cisco IOS Configuration Fundamentals Command Reference, Release 12.2T
-
About the Cisco IOS Release 12.2 T Documentation Set
-
Basic Command-Line Interface Commands
-
The Setup Command
-
Terminal Operating Characteristics Commands
-
Connection, Menu, and System Banner Commands
-
Cisco IOS Web Browser User Interface Commands
-
Cisco IOS File System Commands
-
Configuration File Management Commands
-
System Image and Microcode Commands
-
Router Memory Commands
-
Booting Commands
-
Basic File Transfer Services Commands
-
Basic System Management Commands
-
Troubleshooting and Fault Management Commands
-
SNMP Commands
-
CDP Commands
-
RMON Commands
-
Cisco Service Assurance Agent Commands
-
WCCP Commands
-
CNS Commands
-
Distributed Director Commands
-
XSM Commands for VPN Device Manager (VDM)
-
Appendix: ASCII Character Set and Hex Values
-
Index: Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 T
-
Table Of Contents
ip director default priorities
ip director server availability
ip director server port availability
snmp-server enable traps director
DistributedDirector Commands
This chapter describes the commands used to configure the Cisco DistributedDirector.
alias (boomerang)
To configure an alias name for a specified domain, use the alias command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
alias alias-name
no alias alias-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The alias command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
Use the alias command to specify one or more alias names for an existing domain. Because the boomerang client maintains separate counters for requests received for each domain name (alias or otherwise), use the show ip drp boomerang command to view these counters for a specified domain name and each of its aliases.
Examples
In the following example, the domain name alias is configured for www.boom1.com. The new alias for www.boom1.com is www.boom2.com:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# alias www.boom2.comRouter# show running-config...ip drp domain www.boom1.comalias www.boom2.comRelated Commands
Related Commands
ip director cache size
To configure the variable size of the DistributedDirector cache, use the ip director cache size command in global configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ip director cache size entries
no ip director cache size entries
Syntax Description
Defaults
Maximum number of cache entries: 2000
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip director cache size command to configure the maximum number of cache entries that the DistributedDirector system will retain in its cache. This cache size is the maximum number of cache entries that are displayed when the user enters the show ip director cache command.
Examples
The following example configures the maximum number of cache entries:
Router(config)# ip director cache size 1500Cache size shrinked to 1500Router# show ip director cacheDirector cache is onCache current size = 0 maximum size = 1500Cache time for sort cache entries: 60 secsDirector sort cache hits = 0Related Commands
ip director cache refresh
To enable the DistributedDirector Cache Auto Refresh feature, use the ip director cache refresh command in global configuration mode. To disable automatic background refresh, use the no form of this command.
ip director cache refresh
no ip director cache refresh
Syntax Description
This command has no keywords or arguments.
Defaults
Automatic background refresh is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The sorting cache on DistributedDirector must be enabled before you can use the ip director cache refresh command. To enable the sorting cache, use the ip director cache command.
Once automatic background refresh for the DistributedDirector cache is enabled, the cache will actively and continuously update every expired entry by processing a fake Domain Name System (DNS) request. The cache accumulates and updates answers to all past DNS queries received since cache auto refresh was initiated. Any repeat DNS request is always serviced directly from the cache.
Examples
The following example enables automatic background refresh for the DistributedDirector cache:
Router(config)# ip director cacheRouter(config)# ip director cache refreshRouter# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...ip director cache refreship director cache time
To configure how long the DistributedDirector system will retain per-client sorting information, use the ip director cache time command in global configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ip director cache time seconds
no ip director cache time seconds
Syntax Description
seconds
How long the per-client sorting information is retained, in number of seconds. Range is from 1 to 2147483.
Defaults
60 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip director cache time command to specify how long the DistributedDirector system will retain per-client sorting in its cache. This cache time is the maximum amount of cache time displayed when the user enters the show ip director cache command.
Examples
The following example configures how long the DistributedDirector system will retain per-client sorting information:
Router(config)# ip director cache time 100Router# show ip director cacheDirector cache is onCache current size = 0 maximum size = 2000Cache time for sort cache entries: 100 secsDirector sort cache hits = 0Related Commands
ip director cache
Enables the sorting cache on DistributedDirector.
ip director cache size
Configures the variable size of the DistributedDirector cache.
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 num] [drp-ext num] [drp-ser num] [random num] [admin num] [drp-rtt num] [portion num] [availability num] [route-map num] [boomerang num]
no ip director default priorities [drp-int num] [drp-ext num] [drp-ser num] [random num] [admin num] [drp-rtt num] [portion num] [availability num] [route-map num] [boomerang num]
Syntax Description
Defaults
No default priorities are specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Not all of the metrics need to be specified, but at least one must be specified. If the boomerang metric is specified for a given host name, then all metrics of lower priority (that is, having a higher priority number) than boomerang are always ignored.
The default priorities specified will take effect if no priorities are specified in the ip director host priority command or in the corresponding Domain Name System (DNS) text record for the host.
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
In the following example, the boomerang metric is selected as the default priority:
Router(config)# ip director default priorities boomerang 1Router# show running-configip host boom1 172.2.2.10 172.2.2.20 172.2.2.30ip director server 172.2.2.20 drp-association 172.4.4.2ip director server 172.2.2.30 drp-association 172.4.4.3ip director server 172.2.2.10 drp-association 172.4.4.1ip director host boom1no ip director cacheip dns primary boom1 soa boom1 boom1@comip director host boom1 priority boomerang 1no ip director drp synchronizedRelated 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.
The availability default value is 65,535.
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 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 weight 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 command in global configuration mode. 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 command in global configuration mode. 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 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 director drp synchronized
To activate clock synchronization between DistributedDirector and Director Response Protocol (DRP), use the ip director drp synchronized command in global configuration mode. To deactivate synchronization between the clocks in DistributedDirector and the DRPs, use the no form of this command.
ip director drp synchronized
no ip director drp synchronized
Syntax Description
This command has no arguments or keywords.
Defaults
Clock synchronization is deactivated.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used in conjunction with boomerang racing.
When the ip dir drp synchronized command is configured, DistributedDirector specifies an absolute time at which the DRP agent should respond to the DNS client.
When no ip director drp synchronized is configured (which is the default), DistributedDirector specifies a relative time (based on the delay measured between DistributedDirector and the DRP agent) at which the DRP agent should respond to the DNS client.
Examples
In the following example, DistributedDirector and DRP clock synchronization are activated:
Router# ip director drp synchronizedRouter# show running-configip host boom1 172.2.2.10 172.2.2.20 172.2.2.30ip director server 172.2.2.20 drp-association 172.4.4.2ip director server 172.2.2.30 drp-association 172.4.4.3ip director server 172.2.2.10 drp-association 172.4.4.1ip director host boom1...ip director drp synchronizedip director host priority
To configure the order in which the DistributedDirector considers metrics when picking a server, use the ip director host priority command in global configuration mode. 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
Usage Guidelines
Not all of the metrics need to be specified, but at least one must be specified. If the boomerang metric is specified at a given priority level, then all other metrics of lower priority (that is, having a higher priority number) for that host name are ignored. If the boomerang metric is being considered, then it is the final step in determining the best server.
The availability keyword 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:
Router(config)# ip director host www.xyz.com priority drp-ext 1 admin 2
The following example specifies the per-host priority of the metric, with a host named boom1, where the DRP internal metric is specified with a priority number of 1 and boomerang is specified with a priority number of 2:
Router(config)# ip director host BOOM1 priority drp-int 1 boomerang 2Router(config)# do show running-configip host BOOM1 172.2.2.10 172.2.2.20 172.2.2.30...ip director host BOOM1no ip director cacheip dns primary boom1 soa boom1 boom1@comip director host boom1 priority drp-int 1 boomerang 2Related Commands
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 command in global configuration mode. 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
No host weights are set. If the ip director default-weights command is configured, the configured weights are the default.
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 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 server availability
To configure a default availability value for all ports on a server, use the ip director server availability command in global configuration mode. 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
To configure a default availability value for a specific port on a server, use the ip director server port availability command in global configuration mode. 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 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 serverip drp domain
To add a new domain to the DistributedDirector client or to configure an existing domain, use the ip drp domain command in global configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ip drp domain domain-name
no ip drp domain domain-name
Syntax Description
Defaults
No default domain is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
The ip drp domain command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
Enabling this command puts the client in boomerang configuration mode.
Use the ip drp domain command to enter a new or existing domain name. Entering a new domain name creates a new domain, and entering an existing domain name allows the user to configure the specified domain. When a domain name is configured on the boomerang client, the user can configure specific parameters, such as server address, aliases, and time to live (TTL) values, for that domain.
When a Director Response Protocol (DRP) agent receives a Domain Name System (DNS) racing message from boomerang servers such as DistributedDirector, the DRP agent extracts the specified domain name (for example, www.cisco.com) in the DNS message.
Examples
In the following example, a domain named "www.boom1.com" is added on the boomerang client:
Router(config)# ip drp domain www.boom1.comRouter# show running-config...ip drp domain www.boom1.comRelated Commands
server (boomerang)
To configure the server address for a specified boomerang domain, use the server command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
server server-ip-address
no server server-ip-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The server command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
Use the server command to specify a server address that is to be associated with a given domain name. This configuration overrides the server-to-DRP agent association that is configured on DistributedDirector.
Examples
The following example configures the server for a domain named "www.boom1.com". The server address for www.boom1.com is 172.16.101.101:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# server 172.16.101.101Router# show running-config...ip drp domain www.boom1.comcontent-server 172.16.101.101Related Commands
show 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
ip director default priorities
Sets default priorities for DistributedDirector metrics.
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 command in EXEC mode.
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.0show ip drp boomerang
To display the status of various boomerang domains, use the show ip drp boomerang command in privileged EXEC mode.
show ip drp boomerang [domain-name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show ip drp boomerang command can be used on the boomerang client to display the status of the various boomerang domains. The following information can be shown for each domain:
•
•
–
–
–
–
Examples
The following is sample output from the show ip drp boomerang command:
Router# show ip drp boomerang www.boom1.comDNS packets with unknown domain 0Domain www.boom1.comContent server 172.16.101.101 upOrigin server 0.0.0.0DNS A record requests 0Dropped (server down) 0Dropped (no origen server) 0Security failures 0Alias www.boom2.comDNS A record requests 0Related Commands
snmp-server enable traps director
To enable DistributedDirector SNMP notifications, use the snmp-server enable traps director command in global configuration mode. To disable DistributedDirector SNMP notifications, use the no form of this command.
snmp-server enable traps director [server-up | server-down]
no snmp-server enable traps director [server-up | server-down]
Syntax Description
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) DistributedDirector status notifications for systems. If none of the optional keywords is specified, all available environmental notifications are enabled.
Examples
In the following example, both ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are enabled:
Router(config)# snmp-server enable traps directorRouter# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...ip director host myhostip dns primary myhost soa myhost myhost@comip director host myhost priority boomerang 1no ip director drp synchronizedsnmp-server enable traps director server-up server-downRelated Commands
ttl dns
To configure the number of seconds for which an answer received from the boomerang client will be cached by the Domain Name System (DNS) client, use the ttl dns command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ttl dns seconds
no ttl dns seconds
Syntax Description
seconds
Number of seconds for which an answer received from the boomerang client will be cached by the DNS client. Range is from 10 to 2147483647.
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The ttl dns command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
The ttl dns command configures the number of seconds for which the DNS client can cache a boomerang reply from a boomerang client.
Examples
In the following example, the number of seconds for which the DNS client can cache a boomerang reply from a boomerang client is configured as 10:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# ttl dns 10Router# show running-config...ip drp domain www.boom1.comdns-ttl 10Related Commands
ttl ip
To configure the IP time to live (TTL) value for the boomerang response packets sent from the boomerang client to the DNS client, use the ttl ip command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ttl ip hops
no ttl ip hops
Syntax Description
hops
Number of hops that occur between the boomerang client and the DNS client before the boomerang response packet fails. Range is from 1 to 255.
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The ttl ip command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
The ttl ip command configures the maximum number of hops allowed between the boomerang client and the DNS client, after which the boomerang response packet fails. If the user wants to restrict the contending proxies only to nearby ones, the value of the ttl ip command can be set to a specific number within the allowed range. Any proxy outside of this range will be automatically disqualified in the boomerang race because its replies will never reach the DNS client. Because the ttl ip command specifies the number of hops for which a response from a client will live, it allows faraway proxies to avoid wasting bandwidth.
Examples
In the following example, the number of hops that occur between the boomerang client and the DNS client before the boomerang response packet fails is configured as 2:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# ttl ip 2Router# show running-config...ip drp domain www.boom1.comip-ttl 2Related Commands
