Table Of Contents
Command Reference
This chapter contains an alphabetical listing of LocalDirector commands and command usage sections. Documentation for each command includes a brief description, command syntax, usage guidelines, and command output examples. Topics include:
Command-Line Editing
You can use the commands shown in Table 5-1 on the command line to edit or display previously entered commands.
Note
These are all the editing commands supported by LocalDirector.
The show history command lists the last ten command lines entered.
Command-Line Completion
LocalDirector supports command-line completion. When you enter part of a command and press the Tab key, the command matching that letter combination appears. For example, entering fa and pressing the Tab key returns the failover command:
localdirector(config)# fa[Tab]localdirector(config)# failoverShould the partial command have more than one completion option, press Tab again to display a list of possible completions (the first Tab issues a beep to alert you that more input is needed). For example:
localdirector(config)# s[Tab][Tab]securesnmp-serverstaticstatisticsstickysynsynguardsysloglocaldirector(config)# sIn the following command example, notice you cannot complete more than the command itself; keywords and variables are not completed:
localdirector(config)# fa[Tab]localdirector(config)# failoverlocaldirector(config)# failover ?usage:[no] failover [active]failover ip address <ip_address>failover alias ip address <ip_address> [<netmask>]failover resetlocaldirector(config)# failover i[Tab]usage:[no] failover [active]Wildcard Functions
Wildcards can be used with the show commands and with some action commands that are described in this chapter.
In a show command, any field in a real_id or virtual_id specifier may be left blank or padded with the keyword all to list a set of servers that match.
For example, the following two commands display a list of all TCP virtual servers:
localdirector(config)# show virtual all:all:all:tcplocaldirector(config)# show virtual :::tcpTo display a list of virtual servers configured to use port 443 (trailing colons are unnecessary), use the following command:
localdirector(config)# show virtual all:443To display a list of TCP virtual servers configured to use port 443, use the following minimal command:
localdirector(config)# show virtual :443 tcpWhen using some commands for real servers (such as assign, retry, and timeout), you can replace the real_id specifier with the virtual server ID. This allows all the real servers that are bound to the virtual server to be affected by these commands.
With some action commands, you can pad a real_id or virtual_id specifier with the keyword all to act on a set of servers that match. If the command (or no form of the command) does not accept the wildcard all, an error message appears that states the command cannot be used with the all keyword. With some commands involving real_id or virtual_id you do not need to specify port numbers, bind-id's, or protocols. You can substitute :all:all:all for all port numbers, bind-id's, or protocols.
Abbreviating Commands
You can abbreviate most commands by using only a few unique characters for a command. For example, you can enter conf t (configuration terminal) to start configuration mode.
Access Modes
The command interpreter provides a command set that emulates Cisco IOS technologies. This command set provides three administrator access modes:
•
•
•
Follow this procedure to enter configuration mode:
Step 1
a.
b.
c.
Step 2
Help Information
Information about each command is available when you enter the command name followed by a question mark at the command line prompt, as shown in the following example.
LocalDirector(config)# route 0.0.0.0 0.0.0.0 ? usage: [no] route <dest_net> <net_mask> <gateway> [<metric>]LocalDirector(config)# route 0.0.0.0 0.0.0.0The syntax of the command appears, followed by the prompt with your previous text entry on the command line. If necessary, use the pager command to control display output.
For a listing of all commands available for the current mode, type a question mark.
Unrecognized Commands
If you enter a command that LocalDirector does not recognize, the following message appears:
Type `?' for a list of commandsThis message can be caused by the following:
•
•
•
Commands Listed by Feature
Table 5-2 lists LocalDirector features and the corresponding configuration commands.
alias ip address
To set an alias IP address, use the alias ip address command. Use the no form of this command to remove an alias IP address.
alias ip address ip_address [subnet_mask]
no alias ip address ip_address [subnet_mask]
Syntax Description
ip_address
Alias IP address for LocalDirector. Up to 256 aliases are allowed.
subnet_mask
(Optional) Subnet mask for the aliased IP address. By default, the subnet mask is 255.255.255.0.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The alias ip address command assigns multiple IP addresses to LocalDirector. This allows LocalDirector to be placed on a different IP network than the real servers, without using a router.
Examples
In the following example, an alias IP address of 192.168.34.33 is set. No subnet mask is set, so the default value of 255.255.255.0 is used.
localdirector(config)# alias ip address 192.168.34.33localdirector(config)# show alias ip addressalias ip address 192.168.34.33 255.255.255.0localdirector(config)#Related Commands
show alias
show alias ip
show alias ip address
arp
To add an entry to the LocalDirector Address Resolution Protocol (ARP) table, use the arp command. Use the no arp command to remove an ARP entry.
arp ip mac_address interface_number [alias]
no arp ip mac_address interface_number [alias]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The arp command adds an entry to the LocalDirector ARP table. ARP is a low-level protocol that maps the physical address of a node to its IP address.
Note
Gratuitous ARPs are supported in LocalDirector Versions 1.6 and later. In Versions 3.1 and later, all gratuitous ARPs have the same MAC address regardless of source interface number. A gratuitous ARP is an unsolicited ARP reply. LocalDirector broadcasts its own MAC address to a host on the same wire. This host can be a gateway, router, or switch. These hosts can repopulate the ARP table automatically.
Examples
LocalDirector(config)# arp 192.168.1.42 0000.0101.0202 0LocalDirector(config)# arp 192.168.1.43 0000.0101.0203 1 aliasLocalDirector(config)# show arpInterface 0:192.168.1.42 (0000.0101.0202)Interface 1:192.168.1.43 (0000.0101.0203) aliasInterface 2:LocalDirector(config)# clear arpLocalDirector(config)# show arpInterface 0:Interface 1:192.168.1.43 (0000.0101.0203) aliasInterface 2:LocalDirector(config)# no arp 192.168.1.43 0000.0101.0203 1LocalDirector(config)# show arpInterface 0:Interface 1:Interface 2:LocalDirector(config)#Related Commands
clear arp
show arp
assign
To direct connection requests to a specific instance of a virtual server, use the assign command. Use the no assign command to remove these connection requests.
assign virtual_id client_ip [netmask]
no assign virtual_id client_ip [netmask]
Syntax Description
Defaults
The bind-id when you are defining a virtual server is 0 and the protocol is TCP.
Command Modes
Configuration
Usage Guidelines
Use the assign command to associate client IP addresses with specific virtual servers. Any client IP address not identified by an assign command statement is directed to the default bind-id of 0. A virtual server with a bind-id of 0 cannot be used with the assign command because bind-id 0 is reserved for default traffic.
Prior to Version 3.1, a first-fit algorithm was used to determine which virtual server a client was sent to. If a client fits more than one assignment, LocalDirector selects the first correct virtual server that it looks up. The following example sends clients from the 172.16.67.0 network to virtual server bind-id 1, with the exception of the individual client 172.16.67.146, which is assigned to virtual server bind-id 2:
LocalDirector(config)# assign 192.168.200.1:80:1:tcp 172.16.67.0 255.255.255.0LocalDirector(config)# assign 192.168.200.1:80:2:tcp 172.16.67.146 255.255.255.255Version 3.x uses a best-fit algorithm. The most restrictive subnet mask is judged the best fit, and port assignments are used secondarily. Additionally, to maintain security-related functionality for a particular virtual IP address, if a client IP address fits a subnet mask, then that client is restricted to that subnet mask for all virtual servers with that virtual IP address. As an example:
LocalDirector(config)# assign 192.168.200.1:0:1:tcp 172.16.67.0 255.255.255.0LocalDirector(config)# assign 192.168.200.1:80:1:tcp 172.16.67.146 255.255.255.255restricts the 172.16.67.146 client to port 80. If the client attempts a connection to any other port, even though the IP address fits the subnet mask for the port 0 virtual server, the client is rejected. Once the client is restricted to the 255.255.255.255 subnet mask, any virtual server the client is allowed to access for that IP address must be assigned with an exact subnet mask. If there is no bind-id 0 for that virtual server, and the client is not specifically assigned to another virtual server, the client will be denied access to the virtual server. To allow the client into another port for that IP address, the client must be assigned to that port explicitly (or, of course, with port 0 virtual servers, any port). To allow this client access to port 443, for example:
LocalDirector(config)# assign 192.168.200.1:443:1:tcp 172.16.67.146 255.255.255.255Administrators can validate the assignments they make using the test assign command:
LocalDirector(config)# test assign dest_ip dest_port source_ip [protocol]The command output shows the virtual server the client will be assigned to, or an indication that no virtual server is available for that client.
Examples
LocalDirector(config)# assign 192.168.200.1:80:1:tcp 172.16.1.0 255.255.255.0LocalDirector(config)# assign 192.168.200.1:80:2:tcp 172.16.6.0 255.255.255.0Related Commands
show assign
autounfail
To allow a real server to continue sending data to existing connections after a brief interruption, use the autounfail command. Use the no autounfail command to turn off the autounfail feature.
autounfail real_id | virtual_id
no autounfail real_id | virtual_id
Syntax Description
Defaults
The autounfail command is on by default.
Command Modes
Configuration
Usage Guidelines
An example of a brief interruption would be when a cable is disconnected by mistake, and quickly reconnected. A real server is failed when it does not answer the number of connections set with the threshold command, even though it still might answer one of its existing data connections, or when it responds with TCP RSTs. The autounfail command brings a failed server back in operation if it answers or sends data on a connection that is already established.
When a virtual_id argument is specified, all real servers represented by that virtual server are affected by this command.
In autounfail mode, the real server receives one real incoming connection. If it answers that connection, it is put in service. If it does not answer that connection, it is failed again.
Examples
localdirector(config)# autounfail 192.168.1.2localdirector(config)#Related Commands
show autounfail
backup
To assign a backup server for a real or a virtual server, use the backup command. Use the no backup command to remove a backup server.
backup {real_id | virtual_id} backup_id
no backup {real_id | virtual_id} backup_id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
You can back up real servers with virtual addresses, and you can back up virtual servers with a real server. You can use a backup server when the real or virtual server is not in service (for example, it is failed or out of service).
The url_id is the ID for the Uniform Resource Locator (URL) of a real server as defined by the url command. If you use a url_id as the designated backup server, the url_id can be used to back up a virtual server only.
It is important to note that the backup server is treated just like any other real or virtual server by LocalDirector. For example, if the backup server is a real server, it has the same adjustable parameters (retry, timeout, reassign, and so on) that other real machines have. The predictor command for the backup virtual server is used to load balance the servers being backed up by that virtual server.
A real server bound to a virtual server cannot also be used as a backup for that virtual server, which means that the following configuration works:
virtual 10.1.1.1real 10.2.2.2real 10.3.3.3real 10.4.4.4real 10.5.5.5backup 10.2.2.2 10.4.4.4backup 10.3.3.3 10.5.5.5bind 10.1.1.1 10.2.2.2bind 10.1.1.1 10.3.3.3However, if you tried to bind real server 10.5.5.5 to virtual server 10.1.1.1, you would not be allowed, because that real server is already serving as a backup for that virtual server.
Also, if real server 10.2.2.2 fails and is backed up by real server 10.4.4.4, it uses that real server 10.4.4.4 as long as it is in service. If real server 10.4.4.4 does not stay in service, there is no check for a backup for 10.4.4.4.
Examples
LocalDirector(config)# backup server1 remote1LocalDirector(config)# backup server2 remote1LocalDirector(config)# backup server3 remote1LocalDirector(config)# show backupReal Machine(s) BackupVirtual Machine(s) Backupserver1:0:0:tcp remote1:0:0:tcpserver2:0:0:tcp remote1:0:0:tcpserver3:0:0:tcp remote1:0:0:tcpLocalDirector(config)#Related Commands
show backup
bind
To associate a virtual server with one or more real servers, use the bind command. Use the no bind command to release an association between a real server and virtual server.
bind virtual_id {real_id | url_id} [real_id | url_id...]
no bind virtual_id {real_id | url_id} [real_id | url_id...]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Use the virtual or real command to define the virtual server and real server addresses before using the bind command. Use the bind command to direct network traffic from a virtual server to a real server. If you are binding a real server to more than one virtual server, each real server must use a unique bind-id.
In the following example where the virtual server is defined as 191.191.191.100:0 (a registered Network Information Center address), use the bind command between URLs and a real server as shown:
LocalDirector(config)# virtual 191.191.191.100:0LocalDirector(config)# url w1 http://www1.acme.comLocalDirector(config)# url w2 http://www2.acme.comLocalDirector(config)# bind 191.191.191.100:0 w1LocalDirector(config)# bind 191.191.191.100:0 w2You should create a url_id for each web server at your site. Use the show bind command to confirm binding of URLs to each real server.
Examples
ld(config)# bind 192.168.1.100:80 192.168.1.1:8001ld(config)# bind 192.168.1.100:80 192.168.1.2:8001ld(config)# bind 192.168.1.100:80 192.168.1.3:8001ld(config)# bind 192.168.1.101:80 192.168.1.1:8002ld(config)# bind 192.168.1.101:80 192.168.1.2:8002ld(config)# bind 192.168.1.101:80 192.168.1.3:8002LocalDirector(config)# show bindVirtual Machine(s) Real Machines192.168.1.101:80:0:tcp(IS)192.168.1.3:8002:0:tcp(IS)192.168.1.2:8002:0:tcp(IS)192.168.1.1:8002:0:tcp(IS)192.168.1.100:80:0:tcp(IS)192.168.1.3:8001:0:tcp(IS)192.168.1.2:8001:0:tcp(IS)192.168.1.1:8001:0:tcp(IS)ld(config)#The following is an example of the binding for a UDP virtual and real server:
Ld(config)# bind 192.168.10.101:300:0:udp 192.168.10.1:200:0:udpLd(config)#Ld(config)# show bindVirtual Machine(s) Real Machines192.168.10.101:300:0:udp(OOS)192.168.10.1:200:0:udp(OOS)Related Commands
show bind
boot config
To enable booting from a remote configuration file, use the boot config command. Use the no boot config command to disable booting from a remote configuration file.
boot config filename tftp_server_ip [port port]
no boot config filename tftp_server_ip [port port]
Syntax Description
Defaults
The default port number is 69.
Command Modes
Configuration
Usage Guidelines
LocalDirector configuration files can be stored on a TFTP server. This command accesses the configuration file and boots LocalDirector using the new configuration.
When a configuration file is loaded, each statement is read into the current configuration and evaluated with these rules:
•
•
Examples
localdirector(config)# boot config /tftpboot/ld.conf 10.15.15.253localdirector(config)# write memoryBuilding configuration...[OK]localdirector(config)# reloadProceed with reload? [confirm] [Enter]Rebooting....Finesse Bios V3.3Booting FloppyLoading from Flash384MB RAMi82557 rev 5 Ethernet @ irq15 dev 0 index 0 MAC:00e0.b600.664fi82557 rev 5 Ethernet @ irq 9 dev 1 index 1 MAC:00e0.b600.664ei82557 rev 5 Ethernet @ irq11 dev 2 index 2 MAC:00e0.b600.664di82557 rev 5 Ethernet @ irq 9 dev 3 index 3 MAC:00e0.b600.664cfx1000 rev 3 Ethernet @ irq 9 dev 14 index 4 MAC:0090.27d5.05c4fx1000 rev 3 Ethernet @ irq11 dev 15 index 5 MAC:0090.27d5.05f3Flash=AT29C040A @ 0x300The configuration software is loaded in LocalDirector.
LocalDirector 430 Version 3.3.3 Initialization done.Related Commands
show boot
boot image
To enable booting from a remote image, use the boot image command.
boot image image_filename tftp_server_ip [port port]
Syntax Description
Defaults
The default port number is 69.
Command Modes
Configuration
Usage Guidelines
LocalDirector software (image file) can be stored on a TFTP server. This command accesses that software and boots LocalDirector using the new image. Optionally, you can specify to reload the image.
Examples
In the following example, LocalDirector is booted from a remote image but not reloaded:
localdirector(config)# boot image ld210115.bin 172.18.183.249confirm boot [N]: ysaving image from flashcopying 274944 bytessaving config from flashwriting image to flashwrote 274944 bytes e.size=274944writing the config to flashconfirm reboot on new image [N]: nlocaldirector(config)#In the following example, LocalDirector is booted from a remote image and reloaded:
localdirector(config)# show versionLocalDirector 410 Version 3.3.3localdirector(config) 3# boot image ld333123.bin 172.18.183.249confirm boot [N]:saving image from flashcopying 279040 bytessaving config from flashwriting image to flashwrote 279040 bytes e.size=279040writing the config to flashconfirm reboot on new image [N]:remove floppy from drive and hit any keyRebooting....Finesse Bios V3.3Booting FloppyLoading from Flash32MB RAMFlash=AT29C040A @ 0x300i82557 rev 2 Ethernet @ irq11 dev 13 index 0 MAC: 00a0.c965.576fi82557 rev 2 Ethernet @ irq15 dev 14 index 1 MAC: 00a0.c965.5b33LocalDirector 410 Version 3.x Initialization.....done.Copyright (c) 1998 by Cisco Systems, Inc.Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.Cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706localdirector >bridge
To manipulate bridge table operations, use the bridge command.
show bridge interface_number
clear bridge interface_number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
LocalDirector is a transparent learning bridge. As traffic is received, a bridge table is populated for each interface, showing the MAC addresses that are accessible through that interface. LocalDirector bridges traffic between interfaces only if the source and destination addresses reside on different interfaces. If a server is physically moved from one interface to another, you may need to clear the bridge table to ensure that traffic destined for that server is sent to the correct interface.
Examples
localdirector(config)# show bridgeInterface 0Address Age RX cnt TXcnt0090.f245.3050 1 29934 00050.e2e0.4470 0 16882 25410060.5cc2.0ae5 2 4955 00000.bc11.4b58 12 2003 0Interface 1Address Age RX cnt TXcntInterface 2Address Age RX cnt TXcntInterface 3Address Age RX cnt TXcntCount = 4buddy
To associate virtual servers and create a group, use the buddy command. Use the no buddy command to remove a virtual server from a buddy group, or a buddy group, if all servers have been removed.
buddy buddy_group virtual_id [virtual_id ... ]
no buddy buddy_group virtual_id [virtual_id ... ]
Syntax Description
buddy_group
Name of the group associated with the virtual servers.
virtual_id
(Optional) Virtual server IP address or name, port number, bind-id, and protocol.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Use the buddy command to create a buddy group (named buddy_group) consisting of a list of virtual servers. Certain commands and parameters that affect one virtual server affect all other virtual servers in the buddy group (for example, the buddy relationship shares the generic information from the sticky command). A virtual server can reside in only one buddy group; if it currently exists in a group, it must be removed from that group before it can be added to a new group. An unlimited number of virtual servers can exist within a buddy group.
The show buddy buddy_group command lists the virtual servers in a group, or an error message if the buddy_group does not exist.
Note
Examples
The following example creates the buddy group my_app and adds virtual servers 10.0.0.100 and 10.0.0.200. The contents of the group are displayed with the show buddy command.
localdirector(config)# buddy my-app 10.0.0.100:0:0:tcplocaldirector(config)# buddy my-app 10.0.0.200:0:0:tcplocaldirector(config)# sticky 10.0.0.200 10localdirector(config)# show buddyBuddy Group Virtual Machine(s)my-app10.0.0.100:0:0:tcp10.0.0.200:0:0:tcpWith the sticky feature turned on for virtual server 10.0.0.200, when a client visits the virtual server 10.0.0.100 after visiting 10.0.0.200, the client will be sent to the same real server as on the 10.0.0.100 connection.
Related Commands
show buddy
sticky
channel
To assign two or four interfaces as Fast EtherChannel ports, use the channel command. To restore the primary interface that was channeled, use the no channel command.
channel interface_number two | four
no channel interface_number two | four
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The channel command sets the interface numbers for the Fast EtherChannel configuration. See the "Fast EtherChannel Configuration" section in "Implementing a LocalDirector Network," for a configuration procedure.
The no channel command restores only the primary interface of the channel. The other interfaces are shut down to prevent a bridge loop. For example, the command channel 0 four channels four interfaces to one at interface 0. The command no channel 0 four undoes the channel 0 four command, but only restores interface 0. Interfaces 1, 2, and 3 are shut down to prevent a bridge loop. You must use the no shutdown command to restore interfaces 1, 2, and 3.
Examples
localdirector(config)# show channellocaldirector(config)# show interfaceethernet 0 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex19 packets input, 1020 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort112 packets output, 8720 bytes, 0 underrunsethernet 1 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex3 packets input, 218 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort123 packets output, 9310 bytes, 0 underrunsethernet 2 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex15 packets input, 812 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort120 packets output, 9216 bytes, 0 underrunsethernet 3 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex3 packets input, 218 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort125 packets output, 9494 bytes, 0 underrunsethernet 4 is up, line protocol is upHardware is fx1000 rev 3 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 1000000 Kbit full duplex66 packets input, 7348 bytes, 0 no bufferReceived 44 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 66 frame, 0 overrun, 0 ignored, 0 abort86 packets output, 6946 bytes, 0 underrunsethernet 5 is up, line protocol is upHardware is fx1000 rev 3 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 1000000 Kbit full duplex53 packets input, 4464 bytes, 0 no bufferReceived 3 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort92 packets output, 9298 bytes, 0 underrunslocaldirector(config)# channel 0 twolocaldirector(config)# channel 2 twolocaldirector(config)# show channelFast EtherChannel 0-1 is up, line protocol is up uuHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 200000 Kbit full duplex35 packets input, 2090 bytes, 0 no bufferReceived 4 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort335 packets output, 26910 bytes, 0 underrunsFast EtherChannel 2-3 is up, line protocol is up uuHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 200000 Kbit full duplex32 packets input, 1942 bytes, 0 no bufferReceived 4 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort358 packets output, 29070 bytes, 0 underrunslocaldirector(config)# no channel 0 twolocaldirector(config)# show channelFast EtherChannel 2-3 is up, line protocol is up uuHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 200000 Kbit full duplex121 packets input, 7786 bytes, 0 no bufferReceived 20 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort708 packets output, 50892 bytes, 0 underrunslocaldirector(config)# show interfaceethernet 0 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex106 packets input, 6528 bytes, 0 no bufferReceived 20 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort221 packets output, 16484 bytes, 0 underrunsethernet 1 is administratively down, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810eMTU 1500 bytes, BW 100000 Kbit full duplex19 packets input, 1466 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort473 packets output, 32844 bytes, 0 underrunsethernet 2 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex105 packets input, 6536 bytes, 0 no bufferReceived 20 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort237 packets output, 18238 bytes, 0 underrunsethernet 3 is up, line protocol is upHardware is i82557 rev 5 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 100000 Kbit full duplex21 packets input, 1622 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort483 packets output, 33450 bytes, 0 underrunsethernet 4 is up, line protocol is upHardware is fx1000 rev 3 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 1000000 Kbit full duplex220 packets input, 20060 bytes, 0 no bufferReceived 103 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 339 frame, 0 overrun, 0 ignored, 0 abort473 packets output, 33524 bytes, 0 underrunsethernet 5 is up, line protocol is upHardware is fx1000 rev 3 ethernet, address is 00e0.b600.810fMTU 1500 bytes, BW 1000000 Kbit full duplex364 packets input, 24918 bytes, 0 no bufferReceived 21 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort317 packets output, 27744 bytes, 0 underrunslocaldirector(config)#Related Commands
show channel
show interface
clear
To delete information associated with the other commands, use the clear command.
clear command
Syntax Description
command
arp, bridge, buddy, configuration, counters, route, snmp-server, sticky, syslog, and telnet commands.
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
Use the clear command with arp, bridge, buddy, configuration, counters, route, snmp-server, sticky, syslog, and telnet to clear the values associated with those commands.
Note
Examples
LocalDirector(config)# show arpInterface 0:192.168.1.42 (0000.0101.0202)Interface 1:LocalDirector(config)# clear arpLocalDirector(config)# show arpInterface 0:Interface 1:Related Commands
clear buddy
clear configuration
To delete all or part of the LocalDirector configuration currently operating, use the clear configuration command.
clear configuration [secondary | primary | all]
Syntax Description
Defaults
If you enter the clear configuration command without an optional argument, the default is to clear the secondary configuration.
Command Modes
Privileged, configuration
Usage Guidelines
Use the clear configuration command to delete all or part of the LocalDirector configuration.
Caution
Examples
The following LocalDirector configuration (configured for failover operations with a primary and secondary LocalDirector) exists before you use the clear configuration command. The output appearance has been condensed to conserve space.
LocalDirector4(config)# write terminalBuilding configuration...:Saved:LocalDirector 430 Version 3.3.3syslog output 20.7no syslog consolesyslog host 10.0.0.0enable password 000000000000000000000000000000 encryptedhostname LocalDirector4shutdown ethernet 0no shutdown ethernet 1...no shutdown ethernet 5interface ethernet 0 100full...interface ethernet 4 autointerface ethernet 5 automtu 0 1500mtu 1 1500mtu 2 1500mtu 3 1500mtu 4 1500mtu 5 1500multiring allchannel 0 fourno secure 0no secure 1no secure 2no secure 3no secure 4no secure 5ping-allow 0ping-allow 1ping-allow 2ping-allow 3ping-allow 4no ping-allow 5ip address 10.10.10.1 255.255.255.0route 192.168.0.0 255.0.0.0 10.10.10.10 1...route 10.255.255.255 192.168.0.0 10.0.0.0 1route 15.15.15.0 255.255.255.0 10.10.10.21 1route 0.0.0.0 0.0.0.0 10.10.10.21 1no rip passiverip version 1failover ip address 0.0.0.0no failoverfailover hellotime 30password ciscotelnet 10.10.10.0 255.255.255.0telnet 10.10.10.0 255.255.0.0telnet 10.0.0.0 255.0.0.0snmp-server enable trapssnmp-server community publicno snmp-server contactno snmp-server locationtftp-server 10.0.0.255 port 69 /tftpbootvirtual 10.10.10.163:0:0:tcp isvirtual 10.10.10.164:0:0:tcp is...virtual 10.10.10.161:0:0:tcp isvirtual 10.10.10.162:0:0:tcp isbuddy testgroup 10.10.10.58:0:0:tcpbuddy testgroup 10.10.10.58:80:0:tcp...buddy testgroup 10.10.10.61:80:0:tcpbuddy testgroup 10.10.10.60:0:0:tcppredictor 10.10.10.58:0:0:tcp roundrobinpredictor 10.10.10.58:80:0:tcp roundrobin...predictor 10.10.10.100:80:0:tcp roundrobinpredictor 10.10.10.130:80:0:tcp roundrobinreal 10.10.10.17:0:0:tcp isreal 10.10.10.16:0:0:tcp is...real 10.10.10.7:80:0:tcp isreal 10.10.10.2:80:0:tcp isreplicate interface 4replicate 10.10.10.163:0:0:tcpreplicate 10.10.10.164:0:0:tcp...replicate 10.10.10.161:0:0:tcpreplicate 10.10.10.162:0:0:tcptimeout 10.10.10.17:0:0:tcp 600timeout 10.10.10.16:0:0:tcp 600...timeout 10.10.10.7:80:0:tcp 600timeout 10.10.10.2:80:0:tcp 600name 10.10.10.140 HH_right_bottomname 10.10.10.17 washington8...name 10.10.10.7 lincoln6name 10.10.10.2 lincoln1name 10.10.10.130 HH_right_topname 10.10.10.110 HH_left_topname 10.10.10.120 HH_left_bottomno namesbind 10.10.10.163:0:0:tcp 10.10.10.2:0:0:tcpbind 10.10.10.163:0:0:tcp 10.10.10.3:0:0:tcp...bind 10.10.10.162:0:0:tcp 10.10.10.8:0:0:tcpbind 10.10.10.162:0:0:tcp 10.10.10.9:0:0:tcpsticky 10.10.10.58:0:0:tcp 10 genericsticky 10.10.10.58:80:0:tcp 10 generic...sticky 10.10.10.100:80:0:tcp 5 genericsticky 10.10.10.130:80:0:tcp 10 genericthreshold 10.10.10.17:0:0:tcp 60threshold 10.10.10.16:0:0:tcp 60...threshold 10.10.10.7:80:0:tcp 3threshold 10.10.10.2:80:0:tcp 3:endThe following LocalDirector configuration exists after you use the clear configuration secondary command.
LocalDirector4(config)# clear configuration secondaryLocalDirector4(config)# write terminalBuilding configuration...:Saved:LocalDirector 430 Version 3.3.3syslog output 20.7no syslog consolesyslog host 10.15.15.253enable password 000000000000000000000000000000 encryptedhostname LocalDirector4shutdown ethernet 0no shutdown ethernet 1no shutdown ethernet 2no shutdown ethernet 3no shutdown ethernet 4no shutdown ethernet 5interface ethernet 0 100fullinterface ethernet 1 100fullinterface ethernet 2 100fullinterface ethernet 3 100fullinterface ethernet 4 autointerface ethernet 5 automtu 0 1500mtu 1 1500mtu 2 1500mtu 3 1500mtu 4 1500mtu 5 1500multiring allchannel 0 fourno secure 0no secure 1no secure 2no secure 3no secure 4no secure 5ping-allow 0ping-allow 1ping-allow 2ping-allow 3ping-allow 4no ping-allow 5ip address 10.10.10.1 255.255.255.0route 10.0.0.0 255.0.0.0 10.10.10.10 1route 10.1.0.0 240.0.0.0 10.10.10.11 1...route 192.168.0.0 240.0.0.0 10.10.10.12 1route 192.168.10.0 240.0.0.0 10.10.10.9 1route 10.15.15.0 255.255.255.0 10.10.10.21 1route 0.0.0.0 0.0.0.0 10.10.10.21 1no rip passiverip version 1failover ip address 0.0.0.0no failoverfailover hellotime 30password ciscotelnet 10.10.10.0 255.255.255.0telnet 10.10.10.0 255.255.0.0telnet 10.0.0.0 255.0.0.0telnet 30.0.0.0 255.255.0.0snmp-server enable trapssnmp-server community publicno snmp-server contactno snmp-server locationtftp-server 10.15.15.253 port 69 /tftpbootreplicate interface 4no names:endThe following LocalDirector configuration exists after you use the clear configuration primary command.
LocalDirector4(config)# clear configuration primaryLocalDirector4(config)# write terminalBuilding configuration...:Saved:LocalDirector 430 Version 3.3.3syslog output 20.7no syslog consoleenable password 000000000000000000000000000000 encryptedhostname localdirector4shutdown ethernet 0no shutdown ethernet 1no shutdown ethernet 2no shutdown ethernet 3no shutdown ethernet 4no shutdown ethernet 5interface ethernet 0 100fullinterface ethernet 1 100fullinterface ethernet 2 100fullinterface ethernet 3 100fullinterface ethernet 4 autointerface ethernet 5 automtu 0 1500mtu 1 1500mtu 2 1500mtu 3 1500mtu 4 1500mtu 5 1500multiring allno secure 0no secure 1no secure 2no secure 3no secure 4no secure 5ping-allow 0ping-allow 1ping-allow 2ping-allow 3ping-allow 4no ping-allow 5ip address 10.10.10.1 255.255.255.0no rip passiverip version 1failover ip address 0.0.0.0no failoverfailover hellotime 30password ciscotelnet 10.10.10.0 255.255.255.0telnet 10.10.10.0 255.255.0.0telnet 10.0.0.0 255.0.0.0telnet 10.10.0.0 255.0.0.0snmp-server enable trapssnmp-server community publicno snmp-server contactno snmp-server locationtftp-server 10.15.15.253 port 69 /tftpbootreplicate interface 4no names:endclear counters
To reset the error, interface, or SNMP counters, use the clear counters command.
clear counters [all | error | interface | statistics]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
Use the clear counters command to restart the LocalDirector data counters periodically.
If you enter the clear counters command without an argument, all counters are cleared.
Examples
In the following example, the clear counters command is used to clear all error counters.
LocalDirector# clear counters errorLocalDirector# show error General Indicators: Real machine not available: 0 Connection reassigned: 0 Release Conn extra not handled: 0 Attempt to add conn again: 0 Buddy has no sticky assoc: 0 Invalid TCP checksum in SYN packet: 0 Inbound data packets: 0 Inbound data bytes: 0 Outbound data packets: 0 Outbound data bytes: 0Predictors: `fastest' called: 0 `roundrobin' called: 0 `loaded' called: 0 `leastconns' called: 0 `weighted' called: 0 `slowstart leastconns' called: 0 `slowstarted' called: 0 `sticky buddy' called: 0 Site determined busy: 0Related Commands
show error
show interfaces
show snmp
clear dns-boomerang counters
To clear the counters maintained for each LocalDirector agent domain, use the clear dns-boomerang client command.
clear dns-boomerang counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Configuration
Examples
localdirector (config)# clear dns-boomerang counterslocaldirector (config)Related Commands
dns-boomerang enable
no dns-boomerang enable
show dns-boomerang client
show dns-boomerang counters
show dns-boomerang enable
clock set
To set the date and time for LocalDirector, use the clock set command. You must enter the time based on Coordinated Universal Time (UTC). You cannot disable the clock.
clock set hh:mm:ss month day year
Syntax Description
Defaults
All hour entries are based on Coordinated Universal Time, or UTC.
Command Modes
Privileged, configuration
Usage Guidelines
The clock is used by the sticky command as the timeout reference for the cookie-passive option.
Note
Examples
localdirector(config)# clock set 20:00:00 march 21 2000localdirector(config)# show clock setThurs 12:14:25 Oct 25 2000 GMT localdirector(config)#Related Commands
show clock set
sticky
color
To set an IP precedence value for a virtual server, use the color command. Use the no color command to remove the IP precedence value for a virtual server.
color virtual_id ip_precedence_value
no color virtual_id ip_precedence_value
Syntax Description
Defaults
The IP precedence feature is off by default.
Command Modes
Configuration
Usage Guidelines
The color command allows a value to be set on a per virtual server basis to allow prioritizing of packets for different types of services. Prioritized packets are sent to and from virtual servers. For example, one port may be used for HTTP traffic, using one priority, while another port may handle UDP traffic, with another priority.
Examples
localdirector(config)# color 192.168.1.99 criticallocaldirector(config)# show colorVirtual Machine(s) Coloring192.168.1.99:0:0:tcp criticallocaldirector(config)#Related Commands
show color
configuration
To define the current configuration, use the configuration command.
configuration {floppy | memory | terminal | net}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
Each statement is read into the current configuration and evaluated with these rules:
•
•
Examples
LocalDirector# configuration terminalLocalDirector(config)# real 192.168.1.1:0LocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.1:0:0:tcp 0 OOS 8 0 0 0LocalDirector(config)#Related Commands
show configuration
content-rule
To define the rules to use for content load balancing for a virtual server, use the content-rule command. To remove a content rule, use the no content-rule command. Make sure that no virtual servers are bound when you issue the no content-rule command. Use rule for the abbreviation of the content-rule command.
content-rule rule_name [depth number of bytes] "content_string"
no content rule rule_name [depth number of bytes] "content_string"
Syntax Description
Defaults
The default number of bytes examined in a data packet is 2048.
Command Modes
Privileged, configuration
Usage Guidelines
You can define a maximum number of 512 content rules in each LocalDirector.
LocalDirector does not support the following:
•
•
•
•
Note
Examples
LocalDirector(config)# show ruleRule Name Depth Content to Matchgold001 1024 "/files/customer/gold/?????.lst"spec204 2048 "/public/info/sales/corporate/ filesys/gateway/lev..."images:152 256 "/files/images/*.gif"images:153 256 "/files/images/*.jpgdata
To limit the number of connections to a server that has an open connection to a client, but is not sending data in response to a request, use the data command. To return the connection value to 0, use the no data command.
data {real_id | virtual_id} [number of connections]
no data {real_id | virtual_id} [number of connections]
Syntax Description
Defaults
The feature is disabled by default, with an initial value of 0.
Command Modes
Configuration
Usage Guidelines
Some web servers continue to establish connections to a real server even though the daemon or application running on that port is dead. The data command can be used to limit the number of connections that are sent to a real server that is not sending data.
Note
When a virtual_id is specified, all real servers represented by that virtual server are affected.
No time interval is associated with the data command. The following scenario describes the sequence of events that determines whether the server is responding:
1.
2.
3.
4.
5.
6.
Many kernels do not accept a TCP connection (SYN) if there is no process listening on the port that the client is attempting to connect to. Some kernels, though, mistakenly do accept the connection (SYN/ACK). Because the server is responding (with a SYN/ACK, but not with data), LocalDirector does not recognize this as a real server failure.
The data command determines the number of connections to allow to a real server where data has been not been sent back to the client, regardless of the SYN/ACK response. Once a real server reaches this number, LocalDirector checks whether other machines bound to the virtual server are also at 80 percent of their threshold capacity (based on the DataIn value). If the other machines are close to reaching this value, LocalDirector assumes the site is busy and does not fail the server.
If the other machines are not at this capacity, LocalDirector fails the real server and sends the following syslog/SNMP message:
Real machine 'x' Failed ApplicationThe show real command indicates the number of unanswered connections for each real server, and the show data command indicates the value set with the data command.
Examples
localdirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.1:0:0:tcp 0 OOS 8 0 0 0localdirector(config)# show dataReal Machine(s) DataIn192.168.1.1:0:0:tcp 50localdirector(config)# data 192.168.1.1:0:0:tcp 30localdirector(config)# show dataReal Machine(s) DataIn192.168.1.1:0:0:tcp 30Related Commands
show data
default
To set new LocalDirector command defaults, use the default command.
default command value
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
You can set new default values for some LocalDirector commands. Once a new value is set, it is in effect until set again with the default command. Table 5-3 lists commands that can be changed and the initial default values:
Examples
localdirector(config)# default sticky 10localdirector(config)# virtual 10.10.10.10:80:0:tcplocaldirector(config)# show stickyvirtual sticky10.10.10.10:80:0:tcp 10Related Commands
show default
delay
To keep connections in LocalDirector memory after a TCP ending sequence, use the delay command. Use the no delay command to remove a delay value.
delay virtual_id
no delay virtual_id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The delay command is used to put connections into a "pending deletion" state instead of removing them immediately when a TCP ending sequence is received. If the delay command is set for a virtual server, the connection remains in memory for approximately 5 minutes.
If any data arrives for the connection, it is put back in an "active" state. If any other packet comes across for the connection, the packet passes through the virtual server, but the connection is not considered active.
Use this command only when responses to and from clients are often dropped, especially during the closing of TCP connections. For example, there is a known bug with the Trumpet WinSock stack running on Windows 3.11 in which HTTP GET requests are sent out of order, and this causes LocalDirector to drop the connection even though it has not been completed.
Examples
localdirector(config)# virtual 10.10.10.1localdirector(config)# delay 10.10.10.1localdirector(config)# show delayVirtual Machine(s) Deletion10.10.10.1:0:0:tcp delayed192.168.1.99:0:0:tcp normallocaldirector(config)#Related Commands
show delay
direct-ip
To create a virtual server and a real server with the same IP address, and establish a one-to-one binding between the virtual and the real server in LocalDirector, use the direct_ip command. Use dip for the abbreviation of the direct-ip command.
Use the no direct-ip command to remove the one-to-one binding between the virtual and the real server in LocalDirector.
direct-ip virtual_ip[:[port]:[bind-id]:[protocol]] real-ip[:[port]:[bind-id]:[protocol]] [service-state]
no direct-ip virtual_ip[:[port]:[bind-id]:[protocol]] real-ip[:[port]:[bind-id]:[protocol]] [service-state]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
You cannot bind multiple real servers to direct IP servers (DIPs). Once you create and establish the one-to-one bind between the virtual and the real server using the same IP address with the direct-ip command, the bind condition remains in effect until you use the no direct-ip command. Do not use the no bind command to remove the one-to-one bind established with the direct-ip command. Use the no direct-ip command instead.
Examples
localdirector(config)# direct-ip 1.1.1.10:80:0:tcp islocaldirector(config)disable
To exit privileged mode and return to unprivileged mode, use the disable command.
disable
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged
Usage Guidelines
The disable command exits privileged mode and returns you to unprivileged mode. Use the enable command to return to privileged mode.
Examples
localdirector# disablelocaldirector>Related Commands
enable
dns-boomerang client
To configure the domain you want the LocalDirector agent to support, use the dns-boomerang client command. To remove a domain you no longer want the LocalDirector agent to support, use the
no dns-boomerang client command. Note that the terms "agent" and "client" mean the same thing.dns-boomerang client domain-name ip-addr [key key] [dns-ttl dns-ttl value] [ip-ttl ip-ttl value] [port port value]
no dns-boomerang client domain-name ip-addr [key key] [dns-ttl dns-ttl value] [ip-ttl ip-ttl value] [port port value]
Syntax Description
Defaults
dns-ttl value: 300
ip-ttl value: 255
port value: 0
Command Modes
Configuration
Usage Guidelines
The dns-ttl and ip-ttl values that you set here override the dns-ttl and ip-ttl values that were previously set on the Content Router.
Examples
localdirector(config)# dns-boomerang client www.cisco.com 10.20.30.40 keyencrypt thislocaldirector(config)# dns-boomerang client www.cisco.com 10.20.30.40dns-ttl 200localdirector(config)# dns-boomerang client www.cisco.com 10.20.30.40 ip-ttl7localdirector(config)# dns-boomerang client www.cisco.com 10.20.30.40 port80localdirector(config)#Related Commands
dns-boomerang enable
no dns-boomerang enable
show dns-boomerang enable
show dns-boomerang counters
clear dns-boomerang counters
dns-boomerang enable
To enable the boomerang software on LocalDirector, use the dns-boomerang enable command. To disable boomerang software on LocalDirector, use the no dns-boomerang enable command.
dns-boomerang enable
no dns-boomerang enable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
You can create routing agent domains using the dns-boomerang client command without enabling boomerang on LocalDirector. However, the agent will not respond to incoming boomerang messages from the Content Router until the agent is enabled.
Examples
localdirector (config)# dns-boomerang enablelocaldirector (config)# show dns-boomerang enableBoomerang DNS client is enabled.localdirector (config)Related Commands
clear dns-boomerang counters
no dns-boomerang enable
show dns-boomerang client
show dns-boomerang counters
show dns-boomerang enable
dynamic-feedback
To enable the Dynamic Feedback Protocol (DFP) load manager on LocalDirector to connect to a DFP agent listening for DFP connections on a particular IP address and TCP port combination on a server host, use the dynamic-feedback command. Use the no dynamic-feedback command to disable the connection to a particular IP address and TCP port combination. The command-line abbreviation is dfp.
dynamic-feedback ip_address:port [retry retry] [attempts attempts] [timeout timeout]
no dynamic-feedback ip_address:port [retry retry][attempts attempts] [timeout timeout]
Syntax Description
Defaults
retry: 0 if a value is not specified
attempts: 180 seconds if a value is not specified
timeout: 0 seconds if a value is not specified
Command Modes
Configuration
Usage Guidelines
The dynamic-feedback command opens a TCP connection between the LocalDirector DFP manager and the DFP agent on a server. The connection is specified by the server IP address and the TCP port.
A DFP agent collects load statistics on a server and returns a load metric to the DFP manager. LocalDirector uses the metric to make load-balancing decisions. The message content is specified
by DFP.In the normal configuration, each server in the server farm hosts a DFP agent that collects load information from its host. However, it is also possible for a DFP agent on one server to collect load information from the other servers through local connections. This allows the DFP manager to collect the load metrics for all the servers from a single DFP agent.
The connection that is set up by the dynamic-feedback command is not secure. To set up a secure connection, use the dynamic-feedback-pw command.
The keywords attempts and retry specify how to reconnect to the DFP host if the connection times out or becomes disconnected. If the timeout keyword is used to specify a timeout value, the TCP connection is closed between LocalDirector and the DFP server when the inactivity period on the connection exceeds the timeout value.
Examples
The following command specifies that the connection between the host 10.10.10.253 and LocalDirector, over port 8002, will not time out:
localdirector(config)# dynamic-feedback 10.10.10.253:8002localdirector(config)# show dynamic-feedbackdfp host 10.10.10.253:8002localdirector(config)# no dynamic-feedback 10.10.10.253:8002Related Commands
dynamic-feedback-pw
show dynamic-feedback
dynamic-feedback-agent
To enable listening for connection requests from Dynamic Feedback Protocol (DFP) managers, use the dynamic-feedback-agent command. To disable listening for DFP connection requests from DFP managers, use the no dynamic-feedback-agent command.
dynamic-feedback-agent [port]
no dynamic-feedback-agent [port]
Syntax Description
port
(Optional) Specifies the TCP listening port for DFP manager connections. If no port is specified, port 8080 is used.
Defaults
Port 8080 is used as the TCP listening port if no port is specified.
Command Modes
Privileged, configuration
Usage Guidelines
The dynamic-feedback-agent command activates the DFP agent on LocalDirector, which allows the DFP agent to service DFP manager connection requests on the TCP port specified by the optional port parameter. The DFP agent reports a load metric for each virtual server configured on LocalDirector. The DFP agent also reports on the client network bindings configured on LocalDirector. The DFP manager uses this information to enable quality of service (QoS) controls on connection requests sent to the virtual servers supported on LocalDirector.
DFP managers can reside anywhere on the network that has IP access to LocalDirector. For example, a DFP manager on a Cisco Systems DistributedDirector can use the load metrics from the LocalDirector DFP agent to distribute network traffic to virtual servers based on their availability.
The abbreviation dfp can be substituted for dynamic-feedback at the CLI.
Note
Examples
The following example does not specify the monitoring port, so port 8080 is used by default.
localdirector(config)# dynamic-feedback-agentlocaldirector(config)# show dynamic-feedback-agentdynamic-feedback-agent 8080Related Commands
dynamic-feedback-agent-ip
show dynamic-feedback-agent
dynamic-feedback-agent-ip
To specify Dynamic Feedback Protocol (DFP) manager hosts that can connect to the LocalDirector for DFP communications, use the dynamic-feedback-agent-ip command. To close a host connection to the LocalDirector, use the no dynamic-feedback-agent-ip command.
dynamic-feedback-agent-ip ip_address [password]
no dynamic-feedback-agent-ip ip_address [password]
Syntax Description
ip_address
Identifies the address of the DFP manager host.
password
(Optional) Specifies the password that enables security for the connection.
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The LocalDirector DFP agent uses the host IP address to identify which DFP managers can connect and request server availability information. You can enter up to 256 IP addresses. LocalDirector can support up to 256 connections at one time.
DFP manager hosts ordinarily initiate and terminate connections. However, you can terminate a connection at the LocalDirector by using the no dynamic-feedback-agent-ip command.
A connection is not secure unless the password option is used. The option provides for MD5 encryption in both directions.
DFP managers can reside anywhere on the network that has IP access to LocalDirector. For example, a DFP manager on a Cisco Systems DistributedDirector can use the load metrics from the LocalDirector DFP agent to distribute network traffic to virtual servers based on their availability.
The abbreviation dfp can be substituted for dynamic-feedback at the CLI.
Examples
localdirector(config)# dynamic-feedback-agent-ip 10.10.10.200localdirector(config)# show dynamic-feedback-agent-ipdynamic-feedback-agent-ip 10.10.10.200Related Commands
dynamic-feedback-agent
show dynamic-feedback-agent-ip
dynamic-feedback-pw
To configure a password for TCP connections between a Dynamic Feedback Protocol (DFP) manager on LocalDirector and a DFP agent on a server, use the dynamic-feedback-pw command. Use the no dynamic-feedback-pw command to disable the password (which also closes the connection).
dynamic-feedback-pw ip_address:port [password password]
no dynamic-feedback-pw ip_address:port [password password]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The dynamic-feedback-pw command provides an MD5 secure connection between the DFP manager on LocalDirector and the DFP agent on the server. In this secure environment, DFP messages from the server are discarded unless they contain the MD5 code.
DFP allows servers to provide feedback to LocalDirector about their current loads. DFP also allows servers to take themselves in and out of service. This feature presents a security risk if the network security is compromised, because it allows an invader to take servers out of service. The MD5 code restricts this possibility.
The dynamic-feedback-pw command can be issued before or after the dynamic-feedback command. If it is invoked before, the configuration exists but is considered not connected.
The abbreviation dfp can be substituted for dynamic-feedback at the CLI.
Examples
The following example shows the dynamic-feedback-pw command being invoked before the dynamic-feedback command. The results of the show dynamic-feedback command illustrate that the connection has not been initiated.
localdirector(config)# dynamic-feedback-pw 10.10.10.253:8002 password abcdeflocaldirector(config)# show dynamic-feedbackdfp host 10.10.10.253:8002 - not connectedlocaldirector(config)# no dynamic-feedback-pw 10.10.10.253:8002Related Commands
dynamic-feedback
enable
To enter privileged mode, use the enable command.
enable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Unprivileged, privileged
Usage Guidelines
The enable command starts privileged mode. LocalDirector prompts you for your privileged-mode password. When you first configure LocalDirector, a password is not required and you can press the Enter key at the prompt. Use the disable command to exit privileged mode.
In the following example, note that the prompt changes from ">" to "#" when you enter privileged mode.
Examples
LocalDirector> enablePassword: #######LocalDirector# disableLocalDirector>Related Commands
disable
enable password
enable password
To set or change a privileged mode password, use the enable password command.
enable password password
Syntax Description
password
A password of up to 16 alphanumeric characters, which is not case sensitive. LocalDirector converts the password to all lowercase.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The enable password command sets or changes the privileged mode password, for which you are prompted after you enter the enable command.
Examples
LocalDirector(config)# enable password fnord42LocalDirector(config)#Related Commands
enable
failover
To enable access to the optional failover feature, use the failover command. Use the no failover command to disable the failover feature.
failover [active]
no failover [active]
Syntax Description
Defaults
The default configuration includes the no failover command; however, if the failover cable is present at bootup, it will be detected automatically and failover will be enabled.
Command Modes
Configuration
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to have the same functionality. Both LocalDirector units must run the same version of software, and the failover cable must be used to connect the two units. The failover command without an argument indicates that you have connected the failover cable and intend to use a secondary unit to back up the primary LocalDirector. Use the show failover command to verify the status of the connection and to determine which unit is active. Use the replicate command to maintain connection state on a per virtual server basis.
Note
Failover works by passing control to the standby unit should the active unit fail. The changeover between units occurs within 30 seconds of the failure event. The markings on the failover cable let you choose which unit is primary and which is secondary.
Use the failover active command to initiate a failover changeover from the standby unit, or the no failover active command from the active unit to initiate a failover changeover. You can use this feature to force an active unit offline for maintenance.
Note
or later.Failover only works with the Cisco failover cable. LocalDirector failover does not work with any other vendor's DB-15 to DB-15 cables. Ensure that each end of the LocalDirector cable is connected to a LocalDirector unit.
Because configuration replication is automatic from the active unit to the standby unit, configuration changes should be entered from the active unit only. If your network configuration uses switches with spanning tree, make sure the MAX convergence time is set to less than 30 seconds. On Cisco switches, use the portfast option on the port connected to LocalDirector.
Examples
In this example, the IP address is on the same network as the system IP address, which is 192.168.1.1. The IP address that the secondary LocalDirector uses to communicate with the primary LocalDirector is set to 192.168.1.2.
localdirector(config)# failover ip address 192.168.1.2localdirector(config)#Related Commands
failover alias ip address
failover ip address
failover reset
replicate
show failover
shutdown
failover alias ip address
To assign a failover alias IP address, use the failover alias ip address command.
failover alias ip address ip_address
no failover alias ip address ip_address [netmask]
Syntax Description
ip_address
IP address is used by the standby unit to communicate with the active unit.
netmask
(Optional) Subnet mask for the alias IP address.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to have the same functionality. To take advantage of multiple IP addresses or dispatched mode, or to allow the failover unit to be on a different network from that of the real servers, use the failover alias ip address command to set up an alias on the standby failover unit. A maximum of 256 aliases is allowed.
Examples
In this example, an alias IP address on the secondary LocalDirector is created for the failover environment.
LocalDirector(config)# failover alias ip address 192.168.10.10LocalDirector(config)#Related Commands
failover
failover ip address
failover reset
replicate
show failover
shutdown
failover hellotime
To define how many consecutive seconds can pass without receiving a hello packet before LocalDirector reaches a failover state and initiates a backup routine, use the failover hellotime command. Use the
no failover hellotime command to reset the seconds value to 30 seconds.failover hellotime seconds
no failover hellotime seconds
Syntax Description
seconds
Consecutive seconds that pass without receiving a hello packet before a failover condition initiates a backup routine.
Defaults
The default value is 30 seconds.
Command Modes
Configuration
Usage Guidelines
LocalDirector units in a failover configuration exchange hello packets every 5 seconds across the failover cable and the network interfaces in order to detect communication faults in each other. The failover hellotime command defines how many consecutive seconds can pass without receiving a hello packet before LocalDirector reaches a failover state and initiates a backup routine. The failover state is evaluated in 5-second intervals. For example, if the failover hellotime is 30 seconds, six 5-second intervals must pass without receiving a hello packet before the initiation of a backup routine.
Examples
LocalDirector(config)# failover hellotime 60Related Commands
failover
failover ip address
failover reset
replicate
show failover
shutdown
failover ip address
To set the failover IP address, use the failover ip address command.
failover ip address ip_address [netmask]
no failover ip address ip_address [netmask]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to have the same functionality. Use the failover ip address command to set the IP address on the standby unit.
Examples
The following output shows that failover is on, and the primary unit state is active:
ld-prim(config)# failover ip address 192.168.89.2ld-prim(config)# show failoverFailover OnCable status: NormalThis host: Primary - ActiveActive time: 6885 (sec)Interface 0 (192.168.89.1): NormalInterface 1 (192.168.89.1): NormalOther host: Secondary - StandbyActive time: 0 (sec)Interface 0 (192.168.89.2): NormalInterface 1 (192.168.89.2): NormalThe following example shows the show failover output if failover has not started monitoring the network interfaces:
ld-prim(config)# show failoverFailover OnCable status: NormalThis host: Primary - ActiveActive time: 6930 (sec)Interface 0 (192.168.89.1): Normal (Waiting)Interface 1 (192.168.89.1): Normal (Waiting)Other host: Secondary - StandbyActive time: 15 (sec)Interface 0 (192.168.89.2): Normal (Waiting)Interface 1 (192.168.89.2): Normal (Waiting)
Note
Related Commands
failover
failover alias ip address
failover reset
replicate
show failover
shutdown
failover reset
To take a unit out of the failed state, use the failover reset command.
failover reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to have the same functionality. To take a unit out of the failed state, power cycle the unit or use the failover reset command. The failover reset command also clears failover timers and counters for the LocalDirector unit. When a failed primary unit is fixed and brought back online, it does not automatically resume as the active unit. This action ensures that active control does not resume on a unit that could immediately enter a failed state again. However, if a failure is due to a lost signal on a network interface card, failover autorecovers when the network is available again.
Related Commands
replicate
failover
failover alias ip address
failover ip address
show failover
shutdown
help
To display help information, use the help command.
help
?
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
All
Usage Guidelines
The help or ? command displays help information about all commands. You can view help on an individual command by entering the command name followed by a question mark. The command-line prompt returns with the command syntax, and the command appears on the command line.
Use the pager command to control the display output.
Enter ? at the command prompt to see a list of all of the commands available for the current mode.
Examples
LocalDirector(config)# arp ?usage: [no] arp <ip> <mac_address> <interface_number> [alias]LocalDirector(config)#Related Commands
pager
hostname
To change the host name in the LocalDirector command-line prompt, use the hostname command.
hostname newname
Syntax Description
newname
New host name for the LocalDirector prompt. This name can be up to 16 alphanumeric characters and is not case sensitive. LocalDirector converts the host name to all lowercase.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The hostname command changes the host name label on prompts.
Examples
LocalDirector(config)# hostname e-commercee-commerce(config)#in-service
To set the service state for a real or virtual server or URL to in service (IS), use the in-service command. Use is for the abbreviation of the in-service command.
in-service {virtual virtual_id | real real_id | url url_id | dip dip_id} [all]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The in-service (or is) command indicates that the virtual server, real server, or URL is ready to accept connections.
When you run the is command on multiple port-bound real servers with the same IP address, all servers with the same IP address will have their service state set.
Examples
In the following example, the is command is used with the all keyword to put all ports of real server 192.168.1.1 in service. This puts all ports of the real server (both default and port-bound) in service with just one command.
Server www.domain.com is put in service by using the name of the server for server_id. Because no port is specified, only the default ports are put in service.
When port-bound server 192.168.1.3:80 is put in service, the remaining ports (both default and port-bound) are left out of service.
LocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conn 192.168.1.3:0:0:tcp 0 OOS 8 0 0 0192.168.1.3:21:0:tcp 0 OOS 8 0 0 0192.168.1.3:80:0:tcp 0 OOS 8 0 0 0www.domain.com:0:0:tcp 0 OOS 8 0 0 0www.domain.com:21:0:tcp 0 OOS 8 0 0 0www.domain.com:80:0:tcp 0 OOS 8 0 0 0192.168.1.1:0:0:tcp 0 OOS 8 0 0 0192.168.1.1:21:0:tcp 0 OOS 8 0 0 0192.168.1.1:80:0:tcp 0 OOS 8 0 0 0LocalDirector(config)# is real 192.168.1.1 allLocalDirector(config)# is real www.domain.comLocalDirector(config)# is real 192.168.1.3:80:tcpLocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.3:0:0:tcp 0 OOS 8 0 0 0192.168.1.3:21:0:tcp 0 OOS 8 0 0 0192.168.1.3:80:0:tcp 0 IS 8 0 0 0www.domain.com:0:0:tcp 0 IS 8 0 0 0www.domain.com:21:0:tcp 0 OOS 8 0 0 0www.domain.com:80:0:tcp 0 OOS 8 0 0 0192.168.1.1:0:0:tcp 0 IS 8 0 0 0192.168.1.1:21:0:tcp 0 IS 8 0 0 0192.168.1.1:80:0:tcp 0 IS 8 0 0 0LocalDirector(config)#interface ethernet
To configure network interfaces, use the interface ethernet command. To disable interfaces, use the shutdown ethernet command.
interface ethernet interface_number {10baset | 100basetx | 100full | 1000basesx | 1000full
| auto}Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The interface ethernet command configures the Ethernet interfaces for speed and duplex setting. Use the show interface command to view information about the interface.
To configure full-duplex Ethernet, the auto keyword is recommended, but your network interface must support autodetection. (The RNS four-port adapter cards do not support the auto keyword.) You can set the Ethernet argument to accept full duplex with the 100full keyword if the network accepts full duplex and 100-Mbps Ethernet.
Note
Note
Examples
localdirector(config)# show interfaceethernet 0 is down, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c68MTU 1500 bytes, BW 10000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsethernet 1 is down, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c69MTU 1500 bytes, BW 10000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsethernet 2 is up, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c6aMTU 1500 bytes, BW 100000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsethernet 3 is up, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c6bMTU 1500 bytes, BW 100000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunslocaldirector(config)# interface ethernet 0 100fulllocaldirector(config)# interface ethernet 1 autoWARNING: setting rns23x0 to autosense mode whichis incompatible with autonegotiating deviceslocaldirector(config)# show interfaceethernet 0 is down, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c68MTU 1500 bytes, BW 100000 Kbit full duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsethernet 1 is down, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c69MTU 1500 bytes, BW 10000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsethernet 2 is up, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.4c6aMTU 1500 bytes, BW 100000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunslocaldirector(config)#Related Commands
show interface
shutdown
ip address
To assign the system IP address for LocalDirector, use the ip address command.
ip address ip [subnet_mask]
Syntax Description
ip
System IP address of LocalDirector.
subnet_mask
(Optional) Subnet mask of the LocalDirector network.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The ip address command assigns an IP address to LocalDirector. Use the show ip address command to view the address.
In the following example, the system IP address is 192.168.1.1, and the failover IP address is 192.168.1.2. The current IP address of 192.168.1.2 indicates that this is the standby unit for failover. If the current IP address is the system IP address, the unit is active. If the current IP address is the failover IP address, the unit is standby.
Note
Examples
LocalDirector(config)# ip address 192.168.1.1 255.255.255.0LocalDirector(config)# failover ip address 192.168.1.2LocalDirector(config)# show ip addressSystem IP 192.168.1.1, system subnet 255.255.255.0Current IP 192.168.1.2LocalDirector(config)#Related Commands
failover
show ip address
kill
To terminate a Telnet session, use the kill command.
kill id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The kill command terminates a Telnet session. Use the who command or the show who command to view the Telnet session ID value. When you kill a Telnet session, LocalDirector lets any active commands terminate and then drops the connection without warning to the user.
Examples
LocalDirector(config)# show who2: From 192.168.2.21: From 192.168.1.30: On consoleLocalDirector(config)# kill 2LocalDirector(config)# who1: From 192.168.1.30: On consoleRelated Commands
telnet
show who
who
link
To create an association between a URL and a virtual server, use the link command. To remove an association between a URL and a virtual server, use the no link command.
link url_id {virtual_id | dip_id}
no link url_id {virtual_id | dip_id}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The URL inherits all of the connection counters from the virtual server as a result of the link command. If you have defined leastconns (fewest connections) (with the predictor command) as the load-balancing method, the URL inherits all the connection counters in the virtual server. LocalDirector assigns new connections to the physical server that has the least number of current connections. This feature ensures continued effective load balancing.
Note
Note
Examples
localdirector(config)# link coyote 1.1.1.10:80:0:tcplocaldirector(config)maxconns
To set the maximum number of connections that LocalDirector sends to a real server, use the maxconns command. To remove a maxconns value, use the no maxconns command.
maxconns real_id | virtual_id number
no maxconns real_id | virtual_id number
Syntax Description
Defaults
The default value for the maxconns command is 0, or unlimited connections.
Command Modes
Configuration
Usage Guidelines
You can set the maximum number of connections that a real server accepts to avoid overloading the server. If the server reaches the maximum connection value, or if the virtual server is failed or out of service, LocalDirector responds with a TCP RST packet for all new connections to that server.
When a virtual_id is specified, all real servers represented by that virtual server are affected by this command. When all real servers represented by the virtual ID reach the maximum number of connections, the following message appears:
virtual machine...at capacityNo other connections are sent to this virtual server until the real servers process their connections.
Examples
localdirector(config)# show maxconnsReal Machine(s) Limit192.168.1.1:0:0:tcp unlimited192.168.1.2:0:0:tcp unlimitedlocaldirector(config)# maxconns 192.168.1.1 500localdirector(config)# show maxconnsReal Machine(s) Limit192.168.1.1:0:0:tcp 500192.168.1.2:0:0:tcp unlimitedlocaldirector(config)#Related Commands
show maxconns
mtu
To specify the maximum transmission unit (MTU) value for the specified network interface, use the mtu command.
mtu interface_number bytes
Syntax Description
Defaults
For Ethernet interfaces, the default MTU should be 1500 bytes in a block.
Command Modes
Privileged, configuration
Usage Guidelines
The value for the mtu command depends on the type of network interface specified in the interface command. The minimum value for bytes is 64 and the maximum is 65535 bytes.
Examples
LocalDirector(config)# show mtumtu 0 1500mtu 1 1500LocalDirector(config)# mtu 0 4352LocalDirector(config)# show mtumtu 0 4352mtu 1 1500Related Commands
interface
show mtu
multiring
To enable the Routing Information Field (RIF) for FDDI interfaces, use the multiring command. Use the no multiring command to disable the RIF.
multiring [all]
no multiring [all]
Syntax Description
Defaults
Enabled.
Command Modes
Configuration
Usage Guidelines
The multiring command enables an interface's ability to collect and use source-route information (RIF) for routable protocols. The all keyword enables the multiring for all frames.
In FDDI (and Token Ring), if the upper bit of the source MAC address is set, LocalDirector expects a RIF field to be present in the MAC header. If this field is not present, the packet will be processed incorrectly. Some systems, for example DECnet, set this bit even though no RIF field is present. If source-route bridging is not being used in your network, disable multiring support with the no multiring command on LocalDirector and it will ignore this bit.
Note
Examples
LocalDirector (config) # multiringRelated Commands
show multiring
name
To associate a name with an IP address, use the name command. To remove an assigned name, use the no name command.
name ip name
no name ip name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
Use the name command to identify a virtual or real server by a text name. Using a name makes it easier to change the LocalDirector configuration because you can refer to real and virtual servers by name rather than IP address; however, the port number and bind-id must be included with the name for port-bound servers and virtual servers with bind-id's. The name command can be used before or after a server is defined.
The name command is optional, and it is not related to DNS. It provides a means of making LocalDirector servers easier to configure, and the names associated with the configuration need not be synchronized with DNS.
Examples
In the example that follows, the name command identifies the IP address 192.168.1.1 as "v1." The address is then defined as a virtual server with the virtual command. These commands create a virtual server with a default port of 0 and a bind-id of 0.
ld(config)# name 192.168.1.1 v1ld(config)# virtual v1Two more virtual servers are created using the same name, and they are bound to port 80 with bind-id's of :1 and :2.
ld(config)# virtual v1:80:1ld(config)# virtual v1:80:2A virtual server is created with an IP address of 192.168.1.2 that is bound to port 443 and has a bind-id of :1. The name command is then used to identify IP address 192.168.1.2 as "v2" after the virtual server is defined.
ld(config)# virtual 192.168.1.2:443:1ld(config)# name 192.168.1.2 v2ld(config)# show virtualVirtual Machines:Machine State Connect Sticky Predictor Slowstartv1:80:2:tcp OOS 0 0 leastconns roundrobin*v1:80:1:tc OOS 0 0 leastconns roundrobin*v1:0:0:tcp OOS 0 0 leastconns roundrobin*v2:443:1:tcp OOS 0 0 leastconns roundrobin*The name "v1" is used as the virtual_id with the is command and the all keyword to put all virtual servers with IP address 192.168.1.1 in service.
ld(config)# is virtual v1 allld(config)# show virtualVirtual Machines:Machine State Connect Sticky Predictor Slowstartv1:80:2:tcp IS 0 0 leastconns roundrobin*v1:80:1:tcp IS 0 0 leastconns roundrobin*v1:0:0:tcp IS 0 O leastconns roundrobin*v2:443:1:tcp OOS 0 0 leastconns roundrobin*The name "v2" is used to identify a virtual server bound to port 80 with a bind-id of :1.
ld(config)# virtual v2:80:1ld(config)# show virtualVirtual Machines:Machine State Connect Sticky Predictor Slowstartv1:80:2:tcp IS 0 0 leastconns roundrobin*v1:80:1:tcp IS 0 0 leastconns roundrobin*v1:0:0:tcp IS 0 0 leastconns roundrobin*v2:443:1:tcp OOS 0 0 leastconns roundrobin*v2:80:1:tcp OOS 0 0 leastconns roundrobin*ld(config)#Related Commands
show name
names
To determine whether IP addresses or server names appear in screen output, use the names command. Use the no names command to disable the display of names in screen output.
names
no names
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
You can use either the server name or IP address to configure real and virtual servers regardless of whether the names command is on or off. The status of the names command does not affect the
write terminal and show configuration commands. Use the show names command to check the status of names.Examples
LocalDirector(config)# show namesnames are onLocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Connsserver1:0:0:tcp 0 IS 8 0 0 0server2:0:0:tcp 0 IS 8 0 0 0LocalDirector(config)# no namesLocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.0.1:0:0:tcp 0 IS 8 0 0 0192.168.0.2:0:0:tcp 0 IS 8 0 0 0LocalDirector(config)# show namesnames are offLocalDirector(config)#Related Commands
show names
out-of-service
To set the service state for a virtual server, real server, direct IP server (DIP), or server behind a URL to out of service (oos), use the out-of-service command, which can be abbreviated as oos.
out-of-service {virtual virtual_id} | {real real_id} | {url url_id | dip dip_id}
[oos | maintenance | sticky | failed] [all]Syntax Description
Defaults
The default is 0 for all ports, and the default bind-id is 0.
Command Modes
Configuration
Usage Guidelines
When you set the service state for a real server to out of service, LocalDirector does not assign new connections to it, but lets old connections continue to run until they have been completed. An out-of-service real server can still be accessed by clients specifying its actual IP address.
Note
Use the show real command to watch the status of open connections; when all connections appear as OOS, you can power down the server or reconfigure it as required.
Examples
In the following example, the oos command is used with the all keyword to take all ports of real server 192.168.1.1 out of service with just one command.
Server www.domain.com is placed out of service by using the name of the server for real_id or virtual_id. Because no port is specified, only the default ports are taken out of service.
When port-bound server 192.168.1.3:80 is placed out of service, the remaining ports (both default and port-bound) are left in service.
LocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.3:0:0:tcp 0 IS 8 0 0 0192.168.1.3:21:0:tcp 0 IS 8 0 0 0192.168.1.3:80:0:tcp 0 IS 8 0 0 0www.domain.com:0:0:tcp 0 IS 8 0 0 0www.domain.com:21:0:tcp 0 IS 8 0 0 0www.domain.com:80:0:tcp 0 IS 8 0 0 0192.168.1.1:0:0:tcp 0 IS 8 0 0 0192.168.1.1:21:0:tcp 0 IS 8 0 0 0192.168.1.1:80:0:tcp 0 IS 8 0 0 0LocalDirector(config)# oos real 192.168.1.1 allLocalDirector(config)# oos real www.domain.comLocalDirector(config)# oos real 192.168.1.3:80LocalDirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.3:0:0:tcp 0 IS 8 0 0 0192.168.1.3:21:0:tcp 0 IS 8 0 0 0192.168.1.3:80:0:tcp 0 OOS 8 0 0 0www.domain.com:0:0:tcp 0 OOS 8 0 0 0www.domain.com:21:0:tcp 0 IS 8 0 0 0www.domain.com:80:0:tcp 0 IS 8 0 0 0192.168.1.1:0:0:tcp 0 OOS 8 0 0 0192.168.1.1:21:0:tcp 0 OOS 8 0 0 0192.168.1.1:80:0:tcp 0 OOS 8 0 0 0LocalDirector(config)#Related Commands
in-service (is)
show real
show virtual
pager
To control display output, use the pager command. Use the no pager command to remove paging control.
pager
no pager
Syntax Description
This command has no keywords or arguments.
Defaults
The pager command is on by default.
Command Modes
Unprivileged, privileged, and configuration
Usage Guidelines
If the pager feature is on, by default, one screen of output is displayed at a time. Press the Spacebar to display the next page of information, and press Enter to display the next line. Press the Q key to stop the output and return to the system prompt.
Use the show pager command to see if the pager option is on or off.
Note
Examples
LocalDirector(config)# show pagerpager is offLocalDirector(config)# pagerLocalDirector(config)# show pagerpager is onLocalDirector(config)#Related Commands
pager lines
show pager
pager lines
To set the number of lines in the pager display output, use the pager lines command.
pager lines number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Unprivileged, privileged, and configuration
Usage Guidelines
If the pager option is on, by default, one screen of output is displayed at a time. Use the pager lines command to change the number of lines that appear per screen.
Examples
LocalDirector(config)# show pagerpager is offLocalDirector(config)# pager lines 20turn pager on firstLocalDirector(config)# pagerLocalDirector(config)# pager lines 20LocalDirector(config)# show pagerpager is onRelated Commands
pager
show pager
show pager lines
password
To modify a Telnet login password, use the password command.
password password
Syntax Description
password
Password of up to 16 alphanumeric characters, which is not case sensitive. LocalDirector converts the password to all lowercase and stores it in the configurations as MD5 encrypted text.
Defaults
The default password is cisco.
Command Modes
Configuration
Usage Guidelines
The password command sets a password for Telnet access. It should be changed from the default. The Telnet password is stored in the configuration as MD5 encrypted text for enhanced security.
Examples
LocalDirector(config)# show passwordpassword dfeaf10390e560aea745ccba53e044ed encryptedLocalDirector(config)# password l0cald1rect0rLocalDirector(config)# show passwordpassword 4a1ca4298a78fb276bddfba9fcc7bd81 encryptedLocalDirector(config)# password ciscoLocalDirector(config)# show passwordpassword dfeaf10390e560aea745ccba53e044ed encryptedLocalDirector(config)#Related Commands
show password
ping
To send a ping request message, use the ping command.
ping ip_address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration
Usage Guidelines
The ping command determines whether LocalDirector has connectivity or whether a host is available on the network. The command output shows whether the response was received; that is, that the host exists on the network. If the host is not responding, ping displays this message:
no response receivedUse the show interface command to ensure that LocalDirector is connected to the network and has connectivity.
Examples
In the following example, three attempts reached the specified address:
LocalDirector(config)# ping 192.168.42.54192.168.42.54 response received - 10ms192.168.42.54 response received - 10ms192.168.42.54 response received - 10msLocalDirector(config)#Related Commands
show interface
ping-allow
To turn on the ability to ping a virtual address, use the ping-allow command. Use the no ping-allow command to turn off the ability to ping a virtual address.
ping-allow interface_number
no ping-allow interface_number
Syntax Description
Defaults
The default is to not allow a virtual address to be pinged.
Command Modes
Configuration
Usage Guidelines
By default, virtual addresses cannot be pinged, which helps protect virtual addresses from an Internet Control Message Protocol (ICMP) echo flood.
Use the ping-allow command to enable a LocalDirector virtual address to respond to a ping request.
Examples
The following example allows a virtual address to be pinged from interface 0:
LocalDirector(config)# ping-allow 0LocalDirector(config)#Related Commands
show ping allow
predictor
To choose the type of load balancing for each virtual server, use the predictor command.
predictor virtual_id fastest | roundrobin | leastconns | loaded | weighted [roundrobin | none]
Syntax Description
Defaults
leastconns: default load-balancing mode is round-robin slowstart
weighted: 1
Command Modes
Configuration
Usage Guidelines
Each virtual server can have a different predictor option. The show virtual command places an asterisk (*) next to the active predictor, indicating whether the virtual server is using the selected predictor value, or is in slowstart mode.
The slowstart option is available for the leastconns or weighted arguments. When slowstart is enabled, LocalDirector rotates through the servers until the number of connections reaches a predetermined level, which avoids overloading a server with too many requests when it is brought in service. The slowstart option is enabled by default.
Fastest Keyword
The fastest keyword directs the network connection to the server with the fastest response rate, although it does not perform consistently in varying server configurations. web server performance, in particular, does not follow a linear progression of response time to number of connections. Web servers seem to respond flatly up to a point, and then at a certain load there is a sharp, dramatic increase in the response time. In these situations, the fastest keyword will tend to overload a particular server before moving on to another.
Roundrobin Keyword
The roundrobin keyword directs the network connection to the next server, and treats all servers as equals, regardless of the number of connections or response time. Although the LocalDirector round-robin predictor appears similar to a DNS round-robin, it is superior because no propagation delay or caching hinders the algorithm. Also, LocalDirector can determine when a server is not responding, and avoid sending connections to that server.
LeastConns Keyword
The leastconns keyword directs network connections to the server with the fewest connections. Although it may not be intuitively obvious that the leastconns predictor would provide effective load balancing, in fact it is quite successful. At web sites where there is a collection of servers with similar performance, the leastconns predictor is effective in smoothing distribution when a server becomes bogged down. In sites where there are large differences in the capacity of various servers, the leastconns predictor is also very effective. In maintaining the same number of connections to all servers, those servers that are capable of processing (and thus terminating) connections the fastest will receive more connections over time. A server deemed to be twice as powerful as another server receives about twice as many connections per second.
Loaded Keyword
Use the loaded keyword to give each server a weighted number of connections in a row (round-robin style) before proceeding to the next server on the list. For example:
Server 1 weight 2
Server 2 weight 4
Server 3 weight 1
Server 1 will receive two connections, then Server 2 will receive four connections, and then Server 3 will receive one connection, and so on.
Weighted Keyword
The weighted keyword allows you to assign a performance weight to each server. Weighted load balancing is similar to the function of the leastconns keyword, but servers with a higher weight value receive a larger percentage of connections at any one time. LocalDirector administrators can assign a weight to each real server, and LocalDirector uses this weight to determine the percentage of the current number of connections to give each server. The default weight is 1.
For example, in a configuration with five servers, the percentage of connections is calculated as follows:
Weight of server 1
7
Weight of server 2
8
Weight of server 3
2
Weight of server 4
2
Weight of server 5
5
Total weight of all servers
24
This distribution results in server1 getting 7/24 of the current number of connections, server2 getting 8/24, server3 getting 2/24, and so on. If a new server, server6, is added with a weight of 10, it will get 10/34, and so on.
The weighted predictor gives new connections to the real server that is in most need of a connection, based on how many connections the virtual server and real machines bound to it have at that moment.
For example:
Virtual server 1.1.1.1 has 50 connections and is bound to real servers 1.1.1.2, 1.1.1.3, and 1.1.1.4.
real server 1.1.1.2 has 20 connections with a weight of 3
real server 1.1.1.3 has 10 connections with a weight of 2
real server 1.1.1.4 has 15 connections with a weight of 4
Based on weights, the load should be distributed as follows:
real server 1.1.1.2 gets 3/9 of connections, which is 33 percent
real server 1.1.1.3 gets 2/9 of connections, which is 22 percent
real server 1.1.1.4 gets 4/9 of connections, which is 44 percent
The actual percentage of connections to the real servers is as follows:
real server 1.1.1.2 has 20/50 connections, or 40 percent
real server 1.1.1.3 has 10/50 connections, or 20 percent
real server 1.1.1.4 has 15/50 connections, or 30 percent
Thus, real server 1.1.1.4 will receive connections to bring it closer to having 44 percent of the connections at the time.
Note
Examples
LocalDirector(config)# show virtualMachines:Machine Mode State Connect Sticky Predictor Slowstart10.10.10.1:0:0:tcp directed local OOS 0 least conns roundrobin*192.168.1.99:0:0:tcp directed local OOS 0 least conns roundrobin*LocalDirector(config) 0# predictor www.domain.com weighted noneLocalDirector(config) 1# show virtualVirtual Machines:Machine Mode State Connect Sticky Predictor Slowstartdomain.com:0:0:0:tcp directed local OOS 0 weighted* noneLocalDirector(config)#Related Commands
show predictor
show virtual
weight
probe
To create a probe type (HTTP or DNS) for a real or a virtual machine and set the probing interval, use the probe command. To remove a probe type, use the no probe command.
probe {real | virtual}{real_id | virtual_id} probe_type number_of_intervals
no probe {real | virtual}{real_id | virtual_id} probe_type number_of_intervals
Syntax Description
Defaults
The default for the time interval between probes is 10 seconds.
Command Modes
Configuration
Usage Guidelines
To override a virtual probe on a particular real machine, define a probe for that real machine. To disable probing on a particular real server, define the number_of_intervals as 0 for that real server.
Examples
LocalDirector(config)# probe virtual 10.10.10.1:80:0:tcp http 3LocalDirector(config)# probe real 10.10.10.11:80:0:tcp http 0Related Commands
clear probehttp
probeconfig
probehttp
no probeconfig
show probe
show probeconfig
show probehttp
probeconfig
To enable or begin probing, use the probeconfig command. To disable or stop probing, use the
no probeconfig command.probeconfig probe_type threshold
no probeconfig probe_type
Syntax Description
probe_type
Probe (HTTP or DNS).
threshold
Maximum number of probe failures that can occur before the real machine fails. The threshold can be a minimum of 1 or a maximum of 99.
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
You must use the probe and probehttp commands to configure probes before you can initiate probing using the probeconfig command.
Examples
localdirector(config)# probeconfig http 8localdirector(config)#Related Commands
clear probehttp
probe
probehttp
no probe
show probe
show probeconfig
show probehttp
probedns nodename
To configure the name of the node to be used in DNS query request packets generated by LocalDirector, use the probedns nodename command.
probedns nodename node_name
no probedns nodename node_name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The clear configuration command does not remove any settings configured with the probedns nodename command.
Examples
localdirector(config)# probedns nodename server1.comlocaldirector(config)#probehttp
To set up a customized HTTP probe configuration on a real or virtual machine, use the probehttp command. To clear a customized HTTP probe configuration and reset the default values, use the
clear probehttp command.probehttp {real | virtual} mach_id [file filename_path] [expected return_code]
[request {HEAD | GET}]clear probehttp {real | virtual} mach_id [file filename_path] [expected return_code]
[request {HEAD | GET}]Syntax Description
Defaults
file: /
expected: 200
request: HEAD
Command Modes
Configuration
Usage Guidelines
You must first set up a probe using the probe command before you configure a probe using the probehttp command. Use the probehttp command to set up nondefault configuration values for filename, expected return code, or request type. Use the clear probehttp command to clear customized HTTP probe configuration values and restore the default values.
Note
Examples
localdirector(config)# probehttp virtual 10.10.10.1 file /index.html expected 404 request GETlocaldirector(config)# probehttp virtual 10.10.10.1 file /index.html request GETlocaldirector(config)# probehttp virtual 10.10.10.1 expected 404 request GETlocaldirector(config)# probehttp virtual 10.10.10.1 file /index.htmllocaldirector(config)# probehttp virtual 10.10.10.1 request GETlocaldirector(config)Related Commands
probe
probeconfig
no probe
no probeconfig
show probe
show probeconfig
show probehttp
real
To define a real server, use the real command. Use the no real command to remove a real server from LocalDirector.
real real_ip | real_name[:[port]:[bind-id]:[protocol]] [service-state]
no real real_ip | real_name[:[port]:[bind-id]:[protocol]] [service-state]
Syntax Description
Defaults
:port: 0
:bind-id: 0
:protocol: tcp
service-state: oos (out of service)
Command Modes
Configuration
Usage Guidelines
Real servers are actual host machines with unique IP addresses that provide IP services to the network. Real servers can still be accessed using their actual IP address.
Use the show real command to check the service state of real servers. Possible service states are:
•
•
•
•
Examples
Although a space can be used as a delimiter for port-bound servers, a colon is preferred. Note that the port is 0 by default, and the is (in service) command is used to put the port 80 server in service when it is defined.
ld(config)# real 192.168.1.1ld(config)# real 192.168.1.1:80:tcp isld(config)# real 192.168.1.1 23ld(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.1:23:0:tcp 0 OOS 8 0 0 0192.168.1.1:80:0:tcp 0 IS 8 0 0 0192.168.1.1:0:0:tcp 0 OOS 8 0 0 0The show real command provides the information shown in Table 5-4.
Related Commands
show real
reassign
To set the number of retries to a real server before the connection is reassigned to another server, use the reassign command.
reassign real_id | virtual_id val
Syntax Description
Defaults
The default is three retries.
Command Modes
Configuration
Usage Guidelines
LocalDirector counts the number of TCP SYN packets per connection. When the number of allowable retries is exceeded, LocalDirector reassigns the next TCP SYN packet for the connection to another real server.
Note
When a virtual_id is specified, all real servers represented by that virtual server are affected by
this command.Examples
localdirector(config)# show reassignReal Machine(s) Reassign192.168.1.1:0:0:tcp 3192.168.1.2:0:0:tcp 3localdirector(config)# reassign 192.168.1.1 4localdirector(config)# show reassignReal Machine(s) Reassign192.168.1.1:0:0:tcp 4192.168.1.2:0:0:tcp 3localdirector(config)#Related Commands
show reassign
redirection
To set the type of load-balancing redirection for the virtual server, use the redirection command.
redirection virtual_id {directed | dispatched}[local | assisted]
Syntax Description
Defaults
By default, LocalDirector uses directed mode.
Command Modes
Configuration
Usage Guidelines
The redirection command allows you to change the way packets pass through LocalDirector.
Directed mode uses NAT to translate the IP headers in packets. NAT, supported in LocalDirector since Version 1.0, provides quick setup with no network address changes, reducing system administration time.
Using NAT may not always be the best solution, however. Some protocols embed the IP address within the payload, causing a problem when a packet is encrypted. Additionally, searching though an entire payload for an IP address is processor-intensive and time-consuming. In these cases, performance can be increased using dispatched mode.
Dispatched mode increases traffic throughput, but requires an additional setup of assigning an alias IP address on a real server that matches the virtual IP address on LocalDirector. Dispatched mode should be used for UDP and TCP when the IP address information needs to remain unchanged.
Note
Note
Examples
ld(config)# redirection 192.168.201.55.80 dispatch assistedRelated Commands
show redirection
virtual
reload
To reboot and reload the configuration, use the reload command.
reload
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged
Usage Guidelines
The reload command reboots LocalDirector and reloads the configuration from Flash memory.
Before starting, you are prompted for confirmation with this message:
Proceed with reload?Press y or the Enter key to continue with the reboot.Examples
LocalDirector# reloadProceed with reload? [confirm]Rebooting...replicate
To enable stateful failover, use the replicate command. Use the no replicate command to disable stateful failover on a virtual server.
replicate interface interface_number
no replicate interface interface_number
Syntax Description
Defaults
The default interface number is 0.
Defaults
Configuration
Usage Guidelines
Connection replication is a property of the virtual server, and it is set and cleared with the replicate command. With this command, all established connections are replicated to the standby unit. In the event of a LocalDirector failure (with failover configured), the standby unit has information for current connections, and keeps connections to the virtual server alive.
Replication can be set on a per virtual server basis, which means you can turn it on for 3270 tra
