|
|
Table Of Contents
casa service-manager multicast-ttl
Command Reference
This chapter contains an alphabetical listing of LocalDirector commands. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, and an example of the command output.
Additionally, this chapter contains the following command usage sections:
Command Line Editing
You can use the commands shown in on the command line to edit or display previously entered commands.
Note
These are the only editing commands supported by LocalDirector. Commands such as !! and !9 that were used in previous versions are no longer supported.
The show history command lists the last ten command lines entered.
Command Line Completion
LocalDirector supports command line completion. When you type a part of a command and the Tab key, the command matching that letter combination displays. For example, typing faTab returns the failover command:
localdirector(config)# faTablocaldirector(config)# failoverShould the partial command have more than one completion option, type Tab again to display a list of possible completions (the first Tab issues a beep to alert you more input is needed). For example:
localdirector(config)# sTabTabsecuresnmp-serverstaticstatisticsstickysynsynguardsysloglocaldirector(config)# sIn the following command example, notice you cannot complete more than the command itself; keywords and variables are not completed:
localdirector(config)# faTablocaldirector(config)# failoverlocaldirector(config)# failover ?usage:[no] failover [active]failover ip address <ip_address>failover alias ip address <ip_address> [<netmask>]failover resetlocaldirector(config)# failover iTabusage:[no] failover [active]Wildcard Searches
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 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::tcpAdditionally, some commands for real servers (such as assign, retry, and timeout) allow you to replace the real_id specifier with the virtual server ID so that all real servers that are bound to the virtual server are affected by the command.
Some action commands also allow a real_id or virtual_id specifier to be padded with the keyword all to act on a set of servers that match. If the command (or no form of the command) does not allow the wildcard all, an error message stating the command cannot be used with the all keyword displays.
Abbreviating Commands
You can abbreviate most commands down to the fewest unique characters for a command; for example, you can enter conf t (configuration terminal) to start configuration mode.
Access Modes
•
•
•
•
Follow this procedure to enter configuration mode:
Step 1
•
•
•
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 displays, 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 "Type `?' for a list of commands" message displays for a variety of reasons. This message can be caused by the following:
•
•
•
Commands Listed by Feature
lists configuration commands by LocalDirector features.
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. A maximum of 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 and replication
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
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
failover alias ip address
show alias ip addressarp
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, and replication
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 Version 1.6 and later.
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 arpassign
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 defining a virtual server is 0 and the protocol is TCP.
Command Modes
Configuration and replication
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 the virtual server a client was sent to. If a client fits more than one assignment, LocalDirector selected the first correct virtual server that it looked up. For example, the following example sends clients from the 172.214.67.0 network to virtual server bind-id 1, with the exception of the individual client 172.214.67.146, which is assigned to virtual server bind-id 2:
LocalDirector(config)# assign 192.9.200.1:80:1:tcp 172.214.67.0 255.255.255.0LocalDirector(config)# assign 192.9.200.1:80:2:tcp 172.214.67.146 255.255.255.255Version 3.1 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.9.200.1:0:1:tcp 172.214.67.0 255.255.255.0LocalDirector(config)# assign 192.9.200.1:80:1:tcp 172.214.67.146 255.255.255.255restricts the 172.214.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 get 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.9.200.1:443:1:tcp 172.214.67.146 255.255.255.255Administrators can validate that the assignments they make using the test assign command:
LocalDirector(config)# test assign dest_ip dest_port client_ip [ip_type]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.
See the definition of client-assigned load balancing in Chapter 1, " ," and the example of client-assigned load balancing in Chapter 4, " ," for more information.
Examples
LocalDirector(config)# assign 192.9.200.1:80:1:tcp 172.89.1.0 255.255.255.0LocalDirector(config)# assign 192.9.200.1:80:2:tcp 172.56.6.0 255.255.255.0Related Commands
show assign
autounfail
To put a failed real server into testing mode when it is sending data for existing connections, 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
real_id
Real server IP address or name, port number (if a port-bound server), bind-id, and protocol.
virtual_id
Virtual server IP address or name, port number, bind-id, and protocol.
Defaults
The autounfail command is on by default.
Command Modes
Configuration and replication
Usage Guidelines
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 into testing mode if it answers or sends data on a connection that is already established.
When the virtual_id is specified, all real servers represented by that virtual server are affected by this command.
In testing mode, the real server gets 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 and replication
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).
It is important to note that the backup is treated just like any other real or virtual server by LocalDirector. For example, if the backup is a real server it has the same adjustable parameters (retry, timeout, reassign, and so on) that other real machines have. The predictor 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 v.3.3.3However, if you tried to bind real server 10.5.5.5 to virtual server 10.1.1.1, you will not be allowed because 10.5.5.5 is already serving as a backup for that virtual server.
Also, if server 10.2.2.2 fails and is backed up by 10.4.4.4, it uses that server as long as it is in service; however, if 10.4.4.4 is also failed it does not check the 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 no bind to release an association between a real server and virtual server.
bind virtual_id real_id [real_id...]
no bind virtual_id real_id [real_id...]
Syntax Description
virtual_id
Virtual server IP address or name, port number, bind-id, and protocol.
real_id
The IP address or name, port (if a port-bound server), bind-id, and protocol of a real server.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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.
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.10.10.101:300:0:udp 192.10.10.1:200:0:udpLd(config)#Ld(config)# show bindVirtual Machine(s) Real Machines192.10.10.101:300:0:udp(OOS)192.10.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 file tftp_server_ip [port port]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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 in, each statement is read into the current configuration and evaluated with these rules:
•
•
Related Commands
show boot
boot image
To enable booting from a remote image, use the boot image command.
boot image image_file tftp_server_ip [port port]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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) 8# boot image ld210115.bin 171.69.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) 9#In the following example, LocalDirector is booted from a remote image and reloaded:
localdirector(config) 2# show versionLocalDirector 410 Version 3.0.0.123localdirector(config) 3# boot image ld300123.bin 171.69.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 0>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 and replication
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 = 4Related Commands
clear bridge
show bridgebuddy
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
The 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 and replication
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 (such as the sticky command) that affect one virtual server affect all other virtual servers in the buddy group. 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
The buddy command cannot be used to group a virtual server using the sticky ssl option with a virtual server using the sticky generic option.
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 sticky 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
clear buddy
show buddy
stickycasa service-manager multicast-ttl
To change the multicast time-to-live value for multicast Cisco Applications and Services Architecture (CASA) environment packets, use the casa service-manager multicast-ttl command. Use the no casa service-manager multicast-ttl command to disable the multicast time-to-live value for multicast CASA packets.
casa service-manager multicast-ttl value
no casa service-manager multicast-ttl value
Syntax Description
Defaults
The default time-to-live value is 3 hops.
Command Modes
Configuration and replication
Usage Guidelines
Note
The CASA environment uses LocalDirector as a Service Manager to load balance a set of routers, called Forwarding Agents, providing increased efficiency and scalability. Once the Service Manager determines the Forwarding Agent that will handle the packet stream, all packets belonging to that packet stream are directly routed to the Forwarding Agent.
The Service Manager and Forwarding Agent communicate by sending UDP IP multicast messages. Use the casa service-manager multicast-ttl command to change the time-to-live value (number of hops) for the IP multicast packets that are sent between the CASA components.
Related Commands
casa service-manager port
casa service-manager port
To change the Cisco Applications and Services Architecture (CASA) Service Manager mulitcast port, use the casa service-manager port command. Use the no casa
service-manager port command to reset the CASA Service Manager mulitcast port to the default port number.casa service-manager port port [password password [password_timeout]]
no casa service-manager port port [password password [password_timeout]]
Syntax Description
Defaults
By default, the Service Manager port is 1638.
Command Modes
Configuration and replication
Usage Guidelines
Note
The CASA environment uses LocalDirector as a Service Manager to load balance a set of routers, called Forwarding Agents, providing increased efficiency and scalability. Once the Service Manager determines the Forwarding Agent that will handle the packet stream, all packets belonging to that packet stream are directly routed to the Forwarding Agent.
The Service Manager and Forwarding Agent communicate by sending UDP IP multicast messages. Use the casa service-manager port command to change the UDP port that the Service Manager uses for multicast communication between the CASA components. An optional password and password timeout can be used, which is disabled by default.
The password is the password to be used in MD5 encryption of packets between the Service Manager and Forwarding Agents. A password_timeout value is assigned for two reasons:
•
•
Related Commands
casa service-manager multicast-ttl
channel
To assign two or four ports as Fast EtherChannels, use the channel command. Use the no channel command to remove a port assignment.
channel interface_number two | four
no channel interface_number two | four
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The channel command sets the interface numbers for the Fast EtherChannel configuration. See the section " Fast EtherChannel Configuration" in the chapter "" for a configuration procedure.
Examples
LocalDirector (config#) channel 0 twoLocalDirector (config#) interface ethernet 0 100fullLocalDirector (config#) interface ethernet 1 100fulllocaldirector 2> show channelFast EtherChannel 0-1 is up, line protocol is up udHardware is rns23x0 ethernet, address is 0000.bc11.3e0cMTU 1500 bytes, BW 200000 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 abort98150 packets output, 5891299 bytes, 0 underrunslocaldirector 3> show interfaceethernet 0 is up, line protocol is upHardware is rns23x0 ethernet, address is 0000.bc11.3e0cMTU 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 abort98156 packets output, 5891685 bytes, 0 underrunsethernet 1 is up, line protocol is downHardware is rns23x0 ethernet, address is 0000.bc11.3e0cMTU 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 2 is down, line protocol is upHardware is rns23x0 ethernet, address is 0000.bc11.3e0eMTU 1500 bytes, BW 100000 Kbit full duplex98084 packets input, 5885226 bytes, 0 no bufferReceived 1 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 upHardware is rns23x0 ethernet, address is 0000.bc11.3e0fMTU 1500 bytes, BW 10000 Kbit half duplex337 packets input, 22827 bytes, 0 no bufferReceived 30 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort35212 packets output, 2114369 bytes, 0 underrunslocaldirector 4>Related Commands
show channel
clear
To delete information associated with the other commands, use the clear command.
clear command
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
Use the clear command with arp, bridge, configuration, route, snmp-server, sticky, syslog, and telnet to clear the values associated with those commands.
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:clear configuration
To delete all or part of the LocalDirector configuration, use the clear configuration command.
clear configuration [secondary | primary | all]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
Use the clear configuration command to delete all or part of the LocalDirector configuration. If you enter the clear configuration command without an optional argument, the default is to clear the secondary configuration.
Caution
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 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 and replication
Usage Guidelines
Note
The color command allows a value to be set on a per-virtual server 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 and configuration
Usage Guidelines
Each statement is read into the current configuration and evaluated with these rules:
•
•
Examples
LocalDirector 4# configuration terminalLocalDirector(config) 5# real 192.168.1.1:0LocalDirector(config) 6# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns 192.168.1.1:0:0:tcp 0 OOS 8 0 0 0LocalDirector(config) 7#Related Commands
show configuration
data
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. Use the no data command to return to the connection value to 0.
data {real_id | virtual_id} [connections]
no data {real_id | virtual_id} [connections]
Syntax Description
Defaults
The feature is disabled by default, with an initial value of 0.
Command Modes
Configuration and replication
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.
When the 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 explains the sequence of events that determine whether the server is responding:
1
2
3
4
5
6
Many kernels will 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) 5# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Conns192.168.1.1:0:0:tcp 0 IS 8 0 0 0localdirector(config) 6# show dataReal Machine(s) DataIn192.168.1.1:0:0:tcp 50localdirector(config) 7# data 192.168.1.1:0:0:tcp 30localdirector(config) 8# show dataReal Machine DataIn192.168.1.1:0:0:tcp 30localdirector(config) 9#Related Commands
show data
default
To set new LocalDirector command defaults, use the default command.
default command value
Syntax Description
command
The command for which a new value is being set.
value
The new default value for the command.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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. lists commands that can be changed and their 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 and replication
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 five 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 where HTTP get requests are sent out of order, and this causes LocalDirector to drop the connection even though it has not 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
disable
To exit privileged mode and return to unprivileged mode, use the disable command.
disable
Syntax Description
This command has no arguments or keywords.
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
dynamic-feedback
To configure a real server to return dynamic usage statistics, use the dynamic-feedback command. Use the no dynamic-feedback command to disable the dynamic feedback.
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
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The dynamic-feedback command configures a TCP connection between the LocalDirector and a server running the Dynamic Feedback Agent. The Dynamic Feedback Agent provides statistical information to LocalDirector about the availability of servers in the server farm. LocalDirector maintains the connection to the Dynamic Feedback Agent server, updates its internal status about the availability of servers, and makes load balancing decisions based on the information it receives. Dynamic feedback ensures the most available server can be chosen to provide future connections.
The real server running the Dynamic Feedback Agent must be specified by its IP address and the port over which it sends the feedback information.
The TCP connection allows messages, whose content is specified by the Dynamic Feedback Protocol (DFP), to be sent to the LocalDirector. The connection that is set up with the dynamic-feedback command is not secure. To set up a secure connection, use the dynamic-feedback-pw command.
The keywords attempts and retries specify how to reconnect to the Dynamic Feedback Agent host should the connection time out or become disconnected. If the timeout keyword is used to specify a timeout value, the connection between the LocalDirector and the Dynamic Feedback Agent host is torn down 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 the LocalDirector, over port 8002, will not time out:
localdirector(config) 1# dynamic-feedback 10.10.10.253:8002Related Commands
dynamic-feedback-pw
show dynamic-feedbackdynamic-feedback-pw
To configure a password for the dynamic feedback connection, use the dynamic-feedback-pw command. Use the no dynamic-feedback-pw command to disable the dynamic feedback password.
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
Configuration and replication
Usage Guidelines
The dynamic-feedback-pw command provides an MD5 secure connection between LocalDirector and the Dynamic Feedback Agent host.
Not only does the Dynamic Feedback Protocol allow real servers to provide feedback about their ability to handle more traffic, but it also allows servers to take themselves out of service and put themselves back in service. This ability presents a security risk if the network security is compromised because the servers could be shut down, even though they still can perform.
In the secure environment, messages sent by the Dynamic Feedback Agent host must contain the MD5 code or they are discarded.
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."
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) 1# dynamic-feedback-pw 10.10.10.253:8002 password abcdeflocaldirector(config) 1# show dynamic-feedbackdfp host 10.10.10.253:8002 - not connectedRelated Commands
dynamic-feedback
show dynamic-feedbackenable
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 and 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 passwordenable password
To set the 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
Privileged and unprivileged
Usage Guidelines
The enable password command 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
disable
enablefailover
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 and replication
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to serve 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 switch 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 switch from the standby unit, or the no failover active command from the active unit to initiate a failover switch. You can use this feature to force an active unit offline for maintenance.
Note
Failover works in a switched environment as long as both units are running LocalDirector Version 1.6.3. or later.
Failover only works with the Cisco failover cable. LocalDirector failover does not work with alternate vendor 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 only be entered from the active unit.
If your network configuration uses switches with spanning tree, make sure the MAX time is set to less than 30 seconds. On Cisco switches, use the portfast option on the port connected to LocalDirector.
Related Commands
failover alias ip address
failover ip address
failover reset
replicate
show failover
shutdownfailover alias ip address
To assign a failover alias IP address, use the failover alias ip address command.
failover alias ip address ip_address [netmask]
Syntax Description
ip_address
This IP address is used by the standby unit to communicate with the active unit.
netmask
(Optional) A subnet mask for the aliased IP address.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to serve 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 than 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 are allowed.
Related Commands
failover
failover ip address
failover reset
replicate
show failover
shutdownfailover ip address
To set the failover IP address, use the failover ip address command.
failover ip address ip_address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to serve the same functionality. Use the failover ip address command to set the IP address on the standby unit.
Examples
The following output shows failover 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
shutdownfailover 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 and replication
Usage Guidelines
Failover provides a mechanism for LocalDirector to be redundant by allowing two identical units to serve the same functionality. To take a unit out of the failed state, cycle the power 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
shutdownhelp
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 get 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)# arpRelated 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-commercelab1(config)#in-service
To mark a real or virtual server as being in service (IS), use the in-service or is command.
in-service {virtual virtual_id} | {real real_id} [all]
is {virtual virtual_id} | {real real_id} [all]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The in-service (or is) command indicates that the virtual server or real server is ready to accept connections.
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) 0# 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) 1# is real 192.168.1.1 allLocalDirector(config) 2# is real www.domain.comLocalDirector(config) 3# is real 192.168.1.3:80:tcpLocalDirector(config) 4# 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) 5#interface ethernet
To configure network interfaces, use the interface ethernet command.
interface ethernet interface_number {10baset | 100basetx | 100full | auto}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The interface ethernet command identifies the type of network interface boards, and the speed and duplex settings for Ethernet. 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 4-port adapter cards do not support the auto keyword.) You can force the Ethernet argument to accept full duplex with the 100full keyword if the network accepts full duplex and 100-Mbps Ethernet.
Note
Note
Use the auto keyword for the 4-port Ethernet interfaces on LocalDirector 430.
Examples
localdirector(config) 9# 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) 0# interface ethernet 0 100fulllocaldirector(config) 1# interface ethernet 1 autoWARNING: setting rns23x0 to autosense mode whichis incompatible with autonegotiating deviceslocaldirector(config) 2# 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 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) 3#Related Commands
show interface
shutdownip 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 and replication
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 of 192.168.1.2 indicates that this is the standby unit for failover. If the current IP is the system IP address, the unit is active. If the current IP is the failover IP address, the unit is standby.
Note
Examples
LocalDirector(config) 4# ip address 192.168.1.1 255.255.255.0LocalDirector(config) 4# failover ip address 192.168.1.2LocalDirector(config) 5# show ip addressSystem IP 192.168.1.1, system subnet 255.255.255.0Current IP 192.168.1.2LocalDirector(config) 6#Related Commands
failover
show ip addresskill
To terminate a Telnet session, use the kill command.
kill id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
The kill command terminates a Telnet session. Use who or show who 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
whomaxconns
To set the maximum number of connections that LocalDirector sends to a real server, use the maxconns command. To remove the nondefault 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 and replication
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 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 message "virtual machine ... at capacity" displays, and no 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
interface_number
The interface number.
bytes
The MTU for the interface. Specify a number from 64 to 65535.
Defaults
For Ethernet interfaces, the default MTU should be 1500 bytes in a block; for FDDI, specify 4352 bytes.
Command Modes
Privileged and 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 mtumultiring
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 and replication
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. See the chapter "Configuring Source-Route Bridging" in the document Router Products Configuration and Reference for more information.
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 DEC-NET, 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.
Related 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
ip
The IP address of the virtual server or real server being named. This does not include port numbers associated with port-bound servers.
name
The name assigned to the IP address.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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-ids. 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 to 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" and then it is 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) 8# name 192.168.1.1 v1ld(config) 9# virtual v1Two more virtual servers are created using the same name, and they are bound to port 80 with bind-ids of :1 and :2.
ld(config) 0# virtual v1:80:1ld(config) 1# 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) 2# virtual 192.168.1.2:443:1ld(config) 3# name 192.168.1.2 v2ld(config) 4# 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) 5# is virtual v1 allld(config) 6# 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) 7# virtual v2:80:1ld(config) 8# 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) 9#Related Commands
show name
names
To determine whether IP addresses or server names display 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, and replication
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 mark a virtual server or real server as out of service (OOS), use the out-of-service or oos command.
out-of-service {virtual virtual_id} | {real real_id} [oos | maintenance | sticky | failed] [all]
oos {virtual virtual_id} | {real real_id} [oos | maintenance | sticky | failed] [all]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
When you mark a real server as being out of service, LocalDirector does not assign new connections to it, but lets old connections continue to run until they complete. An out of service real server can still be accessed by clients specifying its actual IP address. 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 server_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) 1# 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) 2# oos real 192.168.1.1 allLocalDirector(config) 3# oos real www.domain.comLocalDirector(config) 4# oos real 192.168.1.3:80LocalDirector(config) 5# 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) 6#Related Commands
in-service (is)
show realpager
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 option is on, by default, one screen of output displays 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 the system prompt.
Use the show pager command to learn 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 pagerpager 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 displays at a time. Use the pager lines command to change the number of lines that display for one 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 pagerpassword
To modify a Telnet login password, use the password command.
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
The default password is cisco.
Command Modes
Configuration and replication
Usage Guidelines
The password command sets a password for Telnet access. It should be changed from the default.
Examples
LocalDirector(config)# password athensge0rg1aLocalDirector(config)#Related Commands
enable password
show passwordping
To send a ping request message, use the ping command.
ping ip_address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
The ping command determines if LocalDirector has connectivity or if a host is available on the network. The command output shows if the response was received; that is, that the host exists on the network. If the host is not responding, ping displays "no response received." Use 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 and replication
Usage Guidelines
By default, virtual addresses cannot be pinged, which helps protect virtual addresses from an 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
The default load balancing mode is leastconns.
Command Modes
Configuration and replication
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.
Least Conns Keyword
The leastconns keyword directs network connections to the server with the least number of open 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 gets bogged down. In sites where there are large differences in the capacity of various servers, the leastconns predictor also is also very effective. In maintaining the same amount of connections to all servers, those servers that are capable of processing (and thus terminating) connections the fastest will get more connections over time. A server deemed to be twice as powerful as another server gets about twice as many connections per second.
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 one.
For example, in a configuration with 5 servers, the percentage of connections is calculated as follows:
weight server1 7
weight server2 8
weight server3 2
weight server4 2
weight server5 5
total weight of all servers = 24This 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 conns, which is 33%
real server 1.1.1.3 gets 2/9 of conns, which is 22%
real server 1.1.1.4 gets 4/9 of conns, which is 44%
The actual percentage of connections to the real servers is as follows:
real server 1.1.1.2 has 20/50 connections, or 40%
real server 1.1.1.3 has 10/50 connections, or 20%
real server 1.1.1.4 has 15/50 connections, or 30%
Thus, real server 1.1.1.4 will receive connections to bring it closer to having 44% of the connections at the time.
Note
Roundrobin Keyword
The roundrobin keyword directs the network connection to the next server, and treats all servers as equals, regardless of 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.
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 to a point, and then at a certain load there is a sharp, dramatic increase in the response time. In these situations, the fastest predictor will tend to overload a particular server before moving on to another.
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 2 connections, then Server 2 will receive 4 connections, and then Server 3 will receive 1 connection, and so on.
Note
Examples
LocalDirector(config) 9# 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) 2#Related Commands
show predictor
show virtual
weight
real
To define a real server, use the real command. Use no real to remove a real server from LocalDirector.
real real_name | real_ip[:[port]:[bind-id]:[protocol]] [service-state]
no real real_name | real_ip[:[port]:[bind-id]:[protocol]] [service-state]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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) 1# real 192.168.1.1ld(config) 2# real 192.168.1.1:80:tcp isld(config) 3# real 192.168.1.1 23ld(config) 4# 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 6-4 show real Field Descriptions
Related Commands
show real
reassign
To set 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 3 retries.
Command Modes
Configuration and replication
Usage Guidelines
If reassign is at the default of 3, then TCP will attempt to connect three times before going to another real server (TCP SYNs are counted). If threshold is set to 8, connections are attempted eight times before the server is marked as failed.
When the 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 | casa] [igmp igmp_address] [port port] [wildcard-ttl seconds] [fixed-ttl seconds]
Syntax Description
Defaults
By default, directed mode with local architecture is used.
Command Modes
Configuration and replication
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 aliased 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
•
Use the casa igmp keyword to set the multicast group address for the CASA components on the LocalDirector. Messages between the Service Manager and Forwarding Agent are sent using multicast to the members of this group. By default, the IGMP group address is 224.0.1.2. Use the no form of this command to remove a component from the group.
•
Use the casa wildcard-ttl keyword to set the time-to-live value for the wildcard-affinity connection objects on the Forwarding Agents. The Service Manager is responsible for ensuring the wildcard-affinities are refreshed before they time out. The default value is
1 minute.•
Use the casa fixed-ttl keyword to set the time-to-live value for the fixed-affinity connection objects. The fixed-affinity connection objects default time-to-live value is
1 minute.Related Commands
show redirection
virtualreload
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.
Note
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 | virtual_id}
no replicate virtual_id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
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 basis, which means you can turn it on for 3270 and leave it off for HTTP. We do not recommend that LocalDirector maintain state for
short-lived connections.
Note
Use the replicate interface command to dedicate an interface to stateful failover.
Examples
LocalDirector(config) 6# replicate 10.10.10.10:0:0:tcpLocalDirector(config) 7# replicate interface 3LocalDirector(config) 8# show replicatereplicate interface 3Machine Replicate10.10.10.10:0:0:tcp onLocalDirector(config) 9#Related Commands
show replicate
restart
To take a server out of service, and then bring it back in service, use the restart command.
restart {real real_id} | {virtual virtual_id}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged, configuration, and replication
Usage Guidelines
The restart command takes a server out of service and puts it back in service with one command.
Caution
Examples
LocalDirector(config)# restart real server1LocalDirector(config)#retry
To specify the number of minutes before a failed server is sent a live connection to check its state, use the retry command.
retry {real_id | virtual_id} val
Syntax Description
Defaults
The default retry interval is one minute.
Command Modes
Configuration and replication
Usage Guidelines
The retry command sets the number of minutes before a failed real server is assigned another connection. If the retry is set to zero, the failed server is not retried until the server is brought back into service with the in-service command.
When the virtual_id is specified, all real servers represented by that virtual server are affected by this command.
Note
Examples
localdirector(config)# show retryReal Machine(s) Retry192.168.1.1:0:0:tcp 1192.168.1.2:0:0:tcp 1localdirector(config)# retry 192.168.1.1 5localdirector(config)# show retryReal Machine(s) Retry192.168.1.1:0:0:tcp 5192.168.1.2:0:0:tcp 1localdirector(config)#Related Commands
show retry
rip passive
To enable IP routing table updates from Routing Information Protocol (RIP) broadcasts that are received, use the rip passive command. To disable routing table updates, use the no rip passive command.
rip passive
no rip passive
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
If you have RIP on your network, enter the rip passive command. If you are not using RIP on your network, you must assign a static route with the route command. LocalDirector does not broadcast RIP, it only listens to RIP.
LocalDirector supports RIP Version 1.
Examples
LocalDirector(config)# show ripno rip passiveLocalDirector(config)# rip passiveLocalDirector(config)# show riprip passiveLocalDirector(config)#Related Commands
show rip
route
To add a static route to the IP routing table, use the route command. Use the no route command to clear the route.
route dest_net net_mask gateway [metric]
no route dest_net net_mask gateway [metric]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
If you want to change an existing route, you must first use the no route command to clear the route, and then specify the new route with the route command. Defining a new IP route with the route command does not overwrite a route that is already established.
Examples
LocalDirector(config)# route 0.0.0.0 0.0.0.0 192.168.1.1 1LocalDirector(config)#Related Commands
clear route
show routesecure
To turn bridging off per interface, use the secure command. Use the no secure command to turn bridging on per interface.
secure interface_number
no secure interface_number
Syntax Description
Defaults
By default, bridging is off.
Command Modes
Configuration and replication
Usage Guidelines
The secure command blocks bridged traffic bound for a specific interface in LocalDirector without affecting traffic that is load-balanced through a virtual server. Only traffic being serviced by a virtual server traverses the interface, and no traffic is bridged to or from the interface.
Note
Examples
LocalDirector(config) 0# secure 0LocalDirector(config) 1# secure 1LocalDirector(config) 2# show securesecure 0secure 1LocalDirector(config) 3# no secure 0LocalDirector(config) 4# show secureno secure 0secure 1LocalDirector(config) 5#Related Commands
show secure
service
To set the type of service enhancements provided by the virtual server, use the service command. Use the no service command to unset the service
service virtual_id ftp-proxy
no service virtual_id ftp-proxy
Syntax Description
virtual_id
Virtual server IP address or name, port number, bind-id, and protocol of the virtual server where connections are replicated.
ftp-proxy
Enables the FTP service.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Note
Current and past releases of LocalDirector supported load-balancing FTP service in a way that worked, but was not fool proof. Because an FTP session consists of a control and a data connection, LocalDirector must monitor the control connection to discover which data connections will be created so it can attach those data connections to the same server handling the control connection. This default support for FTP monitors the control connection on a packet by packet basis, and it does not work if the packets are out of order or if a control command spans packets.
The service virtual_id ftp-proxy command specifies that the virtual_id provides FTP service. LocalDirector monitors the control connection by proxying it, thus this service is about 100 percent foolproof. The trade-off is that each FTP session now consumes more resources in LocalDirector.
Examples
TCP connections going to port 21 of 10.10.10.202 are proxied by LocalDirector and monitored for FTP commands that create data connections:
LocalDirector(config)# service 10.10.10.202 ftp-proxyTCP connections going to port 1066 of 10.10.10.204 are proxied by LocalDirector and monitored for FTP commands that create data connections:
LocalDirector(config)# service 10.10.10.204:1066 ftp-proxyRelated Commands
show service
show
To view LocalDirector information, use the show command.
show command | ?
Syntax Description
Defaults
No default behavior or values.
Command Modes
All
Usage Guidelines
The show command with a LocalDirector command as an argument displays the value assigned by that command. For example, show real displays all of the real servers defined in the configuration.
Any settings left at their default values do not display with the write terminal command. Use the show command and the command associated with the setting to view the default value in the configuration (for example, show retry). The only exception is the show configuration command, which displays the configuration stored in Flash memory, and therefore does not include default values either.
Use the show ? command to view the names of the arguments that can be used with show.
The pager command is used to control the display of show command output.
Examples
localdirector(config)# show realReal Machines:No Answer TCP Reset DataInMachine Connect State Thresh Reassigns Reassigns Connsserver2:0:0:tcp 0 IS 8 0 0 0server1:0:0:tcp 0 IS 8 0 0 0localdirector(config)#Related Commands
show pager lines
show blocks
To show system buffer utilization, use the show blocks command.
show blocks
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
A block (buffer) is the resource used to store packets from the network.
Examples
localdirector(config)# show blocksSIZE MAX LOW CNT4 1024 1024 102480 256 254 254256 128 127 1271550 1280 664 677A description of the show blocks command output is provided in .
Note
shutdown
To disable an interface, use the shutdown command. To enable an interface, use the no shutdown command.
shutdown {ethernet | fddi} interface_number
no shutdown {ethernet | fddi} interface_number
Syntax Description
ethernet
The interface is an Ethernet interface.
fddi
The interface is an FDDI interface.
interface_number
The number of the interface.
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Use the shutdown command to disable access to a network interface. It is important to shutdown an interface if failover is configured, because failover sees the unused interface as failed if it is not turned off.
Examples
To enable an interface and configure its speed, use the following commands:
LocalDirector(config)# no shutdown ethernet 0 LocalDirector(config)# interface ethernet 0 100fullTo disable this same interface, use the following commands:
LocalDirector(config)# shutdown ethernet 0 LocalDirector(config)# interface ethernet 0 100fullUse the write memory command to save configurations to Flash memory.
Related Commands
show shutdown
snmp-server
To configure LocalDirector SNMP agent, use the snmp-server command. Use the no snmp-server command to unconfigure LocalDirector SNMP agent.
snmp-server {contact text | enable traps | host ipaddr | location text}
no snmp-server {contact text | enable traps | host ipaddr | location text}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The snmp-server contact, snmp-server host, and snmp-server location commands configure the SNMP agent on LocalDirector. LocalDirector converts the contact and location information to lowercase.
Note
The snmp-server enable traps command can be used to enable SNMP traps if traps were turned off with the no snmp-server enable traps command. By default, SNMP traps are enabled.
Follow this procedure to configure SNMP:
Step 1
Step 2
Note
The new version of MIBs must be installed for Version 3.1.
MIB Variables
•
•
•
•
LocalDirector supports GetRequests and GetNextRequests on variables in the following groups:
•
•
•
•
LocalDirector supports SetRequests on the following variable:
•
LocalDirector sends traps from the following MIB groups:
•
•
LocalDirector SNMP Private MIB
•
— LocalDirector Object_IDciscoMgmt.*Virtual
•
— VirtualIpAddress— VirtualPort— VirtualBindID— VirtualState— VirtualTotalConnections— VirtualTotalPackets— TotalBytes— VirtualWeightciscoMgmt.*Real
•
— ReallIpAddress— RealPort— RealBindID— RealState— RealTotalConnections— RealTotalPackets— TotalBytes— RealWeight(read/write) - RealWeight can be set using SNMP commands.cisco.failover
— FailoverEnabled— FailoverCableStatus— FailoverUnitType— FailoverUnitStatus— FailoverActiveTimeStampSNMP Traps
— warmStart— linkDown— linkUP— Cisco Syslog Trap— Cisco LocalDirector TrapsMIB-2 Traps
— warmStart— linkDown— linkUPCisco Syslog Traps
•
— OID{1.3.6.1.4.1.9.9.41.2} Generic trap=6, Specific Trap=1cisco.ldtraps
— ciscoLocalDirectorVirtualStateChange (Virtual State Change)— ciscoLocalDirectorRealStateChange (Real State Change)— ciscoLocalDirectorFailoverEnableChange (Failover is turned on/off)— ciscoLocalDirectorFailoverCableChange (Status of failover serial cable)— ciscoLocalDirectorFailoverUnitStatus (The failover activity of the unit: active or standby)Loading MIBs for HP OpenView
All of the HPOV commands are in the /opt/OV/bin directory. When using HPOV, you must use a name for LocalDirector, and the name must be listed in the /etc/hosts file.
The xnmbrowser on the command line is recommended for viewing the MIBs.
•
•
•
•
•
Note
Loading MIB Files in CiscoWorks for Windows (Castle Rock SNMPc)
Follow this procedure to load the MIB files using the CiscoWorks for Windows program (Castle Rock SNMPc):
Step 1
Note
If you do neither, the downloaded files will not display in the "Load MIBs..." dialog box file list. Also, SNMPc only displays the DOS "8.3" format, so you must either recognize the files by their truncated names, or rename the files to your liking using no more than eight characters for the name, and three for the extension.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Examples
LocalDirector(config)# show snmp-serversnmp-server enable trapsno snmp-server contactno snmp-server locationlocaldirector(config)# snmp-server contact System Administratorlocaldirector(config)# snmp-server location Corporate Headquarterslocaldirector(config)# snmp-server host 10.10.10.2localdirector(config)# show snmp-serversnmp-server host 10.10.10.2snmp-server enable trapssnmp-server contact System Administratorsnmp-server location Corporate Headquarterslocaldirector(config)#Related Commands
clear snmp-server
show snmp-serverstatic
To translate a real server IP address to that of a virtual server, use the static command.
static real_id virtual_id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Use the static command to translate a real server address to a virtual server address. This translation allows the real server to make outbound connections, but keeps the IP address hidden outside the LocalDirector network.
For outbound connections that the real server makes (not in response to a user accessing the virtual server), the IP address is translated to the virtual IP address identified by the static command. The outbound connection count is displayed with the show static command.
If the real_id exists as a real server, then the outbound connection is counted toward the number of connections for that real server (that is, it will affect load balancing); otherwise, the connection is only translated and does not affect load balancing.
Examples
localdirector(config) 6# static 10.10.10.220:0 192.168.1.1:0:0localdirector(config) 7# show staticReal Machine Static Machine Connections10.10.10.220:0:0:tcp 192.168.1.1:0:0:tcp 0localdirector(config) 8#Related Commands
show static
sticky
To set the number of inactivity minutes between connections before the client is sent to another server, use the sticky command. To delete sticky associations on the specified virtual server, use the clear sticky command. To disable the sticky feature, use the no sticky command.
sticky virtual_id minutes [generic | ssl]
no sticky virtual_id minutes [generic | ssl]
clear sticky virtual_id minutes
Syntax Description
Defaults
The default sticky interval is 0 minutes (sticky is off).
Command Modes
Configuration and replication
Usage Guidelines
Note
The buddy command cannot be used to group a virtual server using the sticky ssl option with a virtual server using the sticky generic option.
The sticky command ensures that the same client gets the same server for multiple connections. The connection is based on IP address for generic or sticky session ID for ssl. The sticky command is used when applications require a consistent and constant connection to the same server. If you are connecting to a system that keeps state about your connection, sticky allows you to get back to the same real server again and retain the statefulness of the system. For example, if an online form is being completed by a client, the sticky command ensures that multiple connections are sent to the same server to complete the transaction.
The sticky command is not timing how long a client is connected; it is timing periods of inactivity. If sticky is set to five, and the client is active, new requests from the client are not sent to another server via load balancing, even if five minutes have elapsed. However, if five minutes of connection inactivity elapse, the requests from the client could be sent to another real server.
If maxconns will be exceeded by a new connection, a new host is chosen and sticky information is updated to reflect the new host. Then all future connections (within sticky number of minutes) go to a new host.
Use show sticky or show virtual to display the sticky value. Use the no sticky command return to the default value of 0.
Use the clear sticky command to delete sticky associations on the specified virtual server that are minutes old; if the minutes parameter is set to 0, then delete all associations.
The sticky command can also be used in conjunction with the buddy command to sticky two virtual servers together. The buddy command cannot be used to sticky a virtual server running SSL with a generic sticky virtual server.
Note
Examples
In the following example, the virtual command is used to identify 192.168.1.1:443 as a virtual server accepting traffic on port 443 (SSL), and 192.168.1.1:80 as a virtual server accepting HTTP traffic. The sticky command is used to ensure that SSL requests from the same client will be sent to port 443 on real server 192.168.1.1:443 until 10 minutes of inactivity have elapsed:
ld(config) 5# virtual 192.168.1.1:443:0:tcpld(config) 6# virtual 192.168.1.1:80:0:tcpld(config) 7# sticky 192.168.1.1:443:0:tcp 10 sslld(config) 8# show stickyVirtual Machine(s) Sticky192.168.1.1:80:0:tcp 0 generic192.168.1.1:443:0:tcp 10 ssllocaldirector(config)#ld(config) 9#
Note
Related Commands
buddy
clear sticky
show sticky
show virtualsynguard
To activate synguard mode, use the synguard command. To deactivate synguard mode, use the no synguard command.
synguard virtual_id count
no synguard virtual_id count
Syntax Description
virtual_id
Virtual server IP address or name, port number, and bind-id.
count
The number of unanswered SYNs allowed before entering synguard mode. The default is 0.
Defaults
Synguard mode is off.
Command Modes
Configuration and replication
Usage Guidelines
The synguard command provides limited protection against SYN attacks to the virtual IP address. Once the number of unanswered SYNs set with the synguard command is reached, LocalDirector starts to protect the real network and servers from a SYN attack.
A SYSLOG message is sent when LocalDirector enters synguard mode.
Note
To use synguard effectively, monitor the web site to gather statistics about the highest number of SYN counts (using the show syn command). Then, set the synguard level to a percentage (perhaps 10 to 15 percent, or whatever is appropriate for the site) above that number.
The show synguard command displays the number of inbound TCP SYN packets from the client for which the chosen server has not responded with a SYN ACK. Once the server responds, this counter is decremented.
Examples
LocalDirector(config) 1# show synguardVirtual Machine(s) SynGuard Status192.168.1.1:80:0:tcp 0LocalDirector(config) 2# synguard 192.168.1.1:80:0:tcp 400LocalDirector(config) 3# show synguardVirtual Machine(s) SynGuard Status192.168.1.1:80:0:tcp 400LocalDirector(config) 4# show synVirtual Machine(s) Conns Syn Count192.168.1.1:80:0:tcp 722 400LocalDirector(config) 5#Related Commands
show syn
show synguardsyslog
To log messages to SYSLOG server, use the syslog command. Use the no syslog command to stop the messages.
syslog {host ip | console | output facility.level}
no syslog {host ip | console}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
Use the syslog host command to specify the system that is to receive SYLOG messages. Messages are sent to the SYSLOG host over UDP. You can use the show syslog command to view previously sent messages.
The syslog console command is not stored in the LocalDirector configuration and is valid only for the current session. After logging out, the syslog console command is reset to the default because the console for a Telnet user may not be available when LocalDirector is rebooted, thus causing a problem. The syslog console command must be entered each time you want the SYSLOG output to come to your console, whether it is the actual serial line console or a Telnet console.
Logging is enabled by configuring LocalDirector with the IP address of the log host.
Follow this procedure to configure SYSLOG:
Step 1
Step 2
Step 3
Follow this procedure to configure a UNIX system to accept SYSLOG messages:
Step 1
Step 2
# mkdir /var/log/localdirector # touch /var/log/localdirector/nameStep 3
In the syslog.conf file, configure each selector and action pair for the messages you want to receive. For example, if you want to receive messages in a file called localdirector for message priorities 0, 1, 2, and 3, and use the default LOCAL4 facility, the syslog.conf statements would be:
# LocalDirector SYSLOG messages local4.emerg /var/log/localdirector/ld-emerg local4.alert /var/log/localdirector/ld-alert local4.crit /var/log/localdirector/ld-crit local4.error /var/log/localdirector/ld-errorThis configuration directs LocalDirector SYSLOG messages to the specified file. Alternatively, if you want the message sent to the logging host console or sent as an email message to a system administrator, refer to the UNIX syslog.conf(4) manual page.
Entries in /etc/syslog.conf must obey these rules:
•
•
•
Step 4
# cat /etc/syslog.pid 92 # kill -HUP 92The first command generates the SYSLOG process ID (92 in this example). This number may vary by system. The second command sends SYSLOG the HUP signal to restart.
Examples
The following example shows SYSLOG error messages generated by a bridge loop:
LocalDirector(config) 5# show syslogOUTPUT ON (20.3)CONSOLE OFF<162> : Switching to OK.<162> : Switching to OK.<162> Secondary: Switching to ACTIVE.<162> Secondary: Cable not connected my side.<162> Secondary: Switching to OK.<162> Secondary: Switching to OK.<163> Config FAILED: reassign 3<163> Config FAILED: passwd cisco<163> Bridge Loop, 00a0.2409.4f41 on multiple interfaces.<163> Bridge Loop, 00a0.24c0.e863 on multiple interfaces.<163> Bridge Loop, 00a0.c90d.10bd on multiple interfaces.<163> Bridge Loop, 00a0.c933.287b on multiple interfaces.<163> Bridge Loop, 00a0.c90d.10bd on multiple interfaces.LocalDirector(config)6#Related Commands
clear syslog
show syslogtelnet
Use the telnet command to add authorized IP addresses for Telnet access to LocalDirector. Use the no telnet command to remove Telnet access from an IP address.
telnet ip mask
no telnet ip mask
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The telnet command is used to identify who can configure LocalDirector via Telnet. Up to 16 hosts or networks are allowed access to the LocalDirector console, 4 simultaneously. The show telnet command displays the list of IP addresses authorized to access LocalDirector and the clear telnet command removes Telnet access from an IP address. Use the who command to view IP addresses that are accessing LocalDirector.
Use the password command to change the access password for Telnet.
Examples
LocalDirector(config)# telnet 192.168.1.3 255.255.255.255LocalDirector(config)# telnet 192.168.1.4 255.255.255.255LocalDirector(config)# telnet 192.168.2.0 255.255.255.0LocalDirector(config)# show telnet192.168.1.3 255.255.255.255192.168.1.4 255.255.255.255192.168.2.0 255.255.255.0LocalDirector(config)# no telnet 192.168.1.3LocalDirector(config)# show telnet192.168.1.4 255.255.255.255192.168.2.0 255.255.255.255LocalDirector(config)#Related Commands
clear telnet
password
show telnet
whotftp-server
To set the IP address of the TFTP server for storing secondary configuration information and software image files, use the tftp-server command. To remove a TFTP server, use the no tftp-server command.
tftp-server tftp_server_ip [port port] tftp_directory
no tftp-server tftp_server_ip [port port] tftp_directory
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration and replication
Usage Guidelines
The tftp-server command defines the IP address of a TFTP server. Secondary configuration information can be written to, and read from, a TFTP server with the write net and configure net commands. The secondary configuration contains information about virtual and real servers, server bindings, backup servers, and load balancing.
The commands associated with TFTP are as follows:
•
•
•
•
•
Examples
LocalDirector(config)# tftp-server 192.168.10.1LocalDirector(config)#Related Commands
boot config
boot image
configuration net
show tftp-server
write netthreshold
To configure the number of consecutive TCP connection reassignments that a real server can exhibit before LocalDirector marks the real server as failed, use the threshold command.
threshold real_id | virtual_id connect_failures
Syntax Description
Defaults
The default is 8 connection reassignments.
Command Modes
Configuration and replication
Usage Guidelines
Use show real or show threshold to display real server threshold values. When the number of connection reassignments is equal to the threshold value, the server is failed by LocalDirector. Connection reassignments may be due to a TCP RST, or no answer from the real server.
Failed real servers are not used by virtual servers while in the failed state; however, LocalDirector retests each failed server periodically with a single TCP connection attempt to learn if the server has returned to normal behavior. If so, LocalDirector marks the server as in service, which makes it available to process virtual server requests.
When the virtual_id is specified, all real servers represented by that virtual server are affected by this command.
Examples
localdirector(config)# show thresholdReal Machine(s) Threshold192.168.1.1:0:0:tcp 8192.168.1.2:0:0:tcp 8localdirector(config)# threshold 192.168.1.1 10localdirector(config)# show thresholdReal Machine(s) Threshold192.168.1.1:0:0:tcp 10192.168.1.2:0:0:tcp 8localdirector(config)#Related Commands
reassign
retry
show real
show thresholdtimeout
To set the connection timeout for real server, user the timeout command.
timeout real_id | virtual_id idle_minutes
Syntax Description
Defaults
The default connection interval is 120 minutes.
Command Modes
Configuration and replication
Usage Guidelines
Idle connections will be timed out after the number of minutes set with the timeout command for each real server. In addition, every two minutes LocalDirector will remove a connection that has not been fully established (that is, either the client or server did not complete the TCP handshaking sequence to get the connection established).
When the virtual_id is specified, all real servers represented by that virtual server are affected by this command.
Use the timeout command for real servers running the connectionless UDP protocol. Because no mechanism exists within UDP to signal the end of a connection, set the duration of the UDP connection with the timeout idle_minutes setting. UDP connections can successfully use the timeout minimum, which is 5 minutes.
Note
(120 minutes) to a shorter interval, such as 5 minutes.
Examples
localdirector(config)# show timeoutReal Machine(s) Timeout192.168.1.1:0:0:tcp 120192.168.1.2:0:0:tcp 120localdirector(config)# timeout 192.168.1.2 11localdirector(config)# show timeoutReal Machine(s) Timeout192.168.1.1:0:0:tcp 120192.168.1.2:0:0:tcp 11localdirector(config)#Related Commands
show timeout
virtual
To create a virtual server to accept a connection from the network, use the virtual command. Use the no virtual command to remove the virtual server from LocalDirector.
virtual virtual_name | virtual_ip [:[virtual_port]:[bind-id]:[protocol]]
[service-state]no virtual virtual_name | virtual_ip [:[virtual_port]:[bind-id]:[protocol]]
[service-state]Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration
Usage Guidelines
The virtual command creates a virtual server to accept a connection from the network. Virtual servers present a single address for a group of real servers and load-balance service requests between the real servers in a site. The virtual server IP address is published to the user community, but the real IP address can remain unpublished.
If you are using directed mode, and the published or "advertised" addresses are different from internal addresses, the IP address of LocalDirector must be on the network from which you want to access LocalDirector. That is, if your virtual servers are on network 204.31.17.x, and your real servers are on network 192.168.89.x, then the IP address of LocalDirector should be either 204.31.17.x (if accessing LocalDirector from outside) or 192.168.89.x (if accessing LocalDirector from inside). Here "accessing" means using Telnet, SNMP, or SYSLOG to connect to LocalDirector. Virtual server addresses can only be accessed from the client side of LocalDirector.
If you are using dispatched mode, you can create an alias IP address on LocalDirector and keep it in a subnet different from the location of the real servers.
Specify the IP address of LocalDirector with the ip address command before defining virtual servers.
If no real servers are bound to the virtual server, use the no virtual command to remove the virtual server from LocalDirector.
Examples
The port and bind-id are optional when defining virtual servers. Although a space can be used as a delimiter for the port, a colon is preferred and must be used with the bind-id. Note that the port and bind-id are 0 by default.
ld(config) 5# virtual 10.10.10.1:80:tcpld(config) 6# virtual 10.10.10.1:443:1:tcpld(config) 7# virtual 10.10.10.1ld(config) 8# show virtualMachines:Machine Mode State Connect Sticky Predictor Slowstart10.10.10.1:80:0:tcp directed local OOS 0 0 leastconns roundrobin*10.10.10.1:443:1:tcp directed local OOS 0 0 leastconns roundrobin*10.10.10.1:0:0:tcp directed local OOS 0 0 leastconns roundrobin*In the following example, note the use of the name command. The name is used with the port and bind-id to identify the server (virtual_id).
ld(config) 9# name 10.10.10.1 luckyld(config) 0# is virtual lucky:80ld(config) 1# sticky lucky:443:1 10ld(config) 2# show virtualVirtual Machines:Machine Mode State Connect Sticky Predictor Slowstartlucky:80:0:tcp directed local IS 0 0 leastconns roundrobin*lucky:443:1:tcp directed local OOS 0 10 leastconns roundrobin*lucky:0:0:tcp directed local OOS 0 0 leastconns roundrobin*To remove a virtual server, you must first remove any bind association to real servers. For example:
LocalDirector(config) 5# show virtualVirtual Machines:Machine Mode State Connect Sticky Predictor Slowstart192.168.0.98:0:0:tcp directed local OOS 0 0 leastconns roundrobin*192.168.0.99:0:0:tcp directed local IS 0 0 leastconns roundrobin*LocalDirector(config) 6# show bindVirtual Real192.168.0.98:0:0:tcp(OOS)192.168.0.3:0:0:tcp(OOS)192.168.0.99:0:0:tcp(IS)192.168.0.1:0:0:tcp(IS)192.168.0.2:0:0:tcp(IS)LocalDirector(config) 7# no virtual 192.168.0.98:0:0:tcpMust unbind all reals before removing virtual.LocalDirector(config) 8# no bind 192.168.0.98:0:0:tcp 192.168.0.3:0:0:tcpLocalDirector(config) 9# no virtual 192.168.0.98:0:0:tcpLocalDirector(config) 0# show virtualVirtual Machines:Machine Mode State Connect Sticky Predictor Slowstart192.168.0.99:0:0:tcp directed local IS 0 0 leastconns roundrobin*LocalDirector(config) 1#The show virtual command indicates the service state of virtual servers in addition to other information. Descriptions of the show virtual command output are provided in .
Table 6-6 show virtual Field Descriptions
Possible service states are:
•
•
•
•
•
•
•
•
Related Commands
ip address
show virtualweight
To assign a relative value to the distribution of connections for a real server, use the weight command. Use the no weight command to remove a weight value from a real server.
weight real_id number
no weight real_id number
Syntax Description
Defaults
The default number of connections is 1.
Command Modes
Configuration and replication
Usage Guidelines
Servers with higher performance can support a higher number of connections. In the following example, the weights of all of the servers equals eight. Therefore, server 192.168.1.1 would receive 4/8 of the connections, or 50 percent. Server 192.168.1.2 would receive 25 percent of the connections, and servers 192.168.1.3 and 192.168.1.4 would each receive 12.5 percent of the connections. Faster servers receive more connections because they service the connection faster, regardless of the percentage of connections they are assigned at the time.
Note
Examples
localdirector(config)# show weightReal Machine(s) Weight192.168.1.1:0:0:tcp 1192.168.1.2:0:0:tcp 1localdirector(config)# weight 192.168.1.1 4localdirector(config)# show weightReal Machine(s) Weight192.168.1.1:0:0:tcp 4192.168.1.2:0:0:tcp 1localdirector(config)#Related Commands
show weight
who
To show active Telnet administration sessions, use the who command.
who [ip]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Unprivileged, privileged, and configuration
Usage Guidelines
The who command shows the tty_id and IP address of each Telnet client currently logged in to LocalDirector. This command is the same as the show who command.
Examples
LocalDirector# who2: From 192.168.2.21: From 192.168.1.30: On consoleLocalDirector#Related Commands
kill
show who
telnetwildcard
To show wildcards in use, use the show wildcard command.
show wildcard
Defaults
No default behavior or values.
Command Modes
Privileged
Usage Guidelines
Use this command to view the wildcards that are currently being used.
Note
write
To store the current configuration, use the write command.
write {erase | floppy | memory | terminal | standby}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
Use the write floppy command to save the current running configuration to floppy disk, and use the write memory command to save to Flash memory. You can save your configuration on the distribution diskette that shipped with your LocalDirector. Use configure memory or configure floppy to restore the saved configuration.
Any settings left at the default value will not be displayed with the write terminal command. Use the show command and the command associated with the setting to view the default value in the configuration (for example, show retry). The only exception is the show configuration command, which displays the configuration stored in Flash memory, and therefore will not include default values either.
Examples
LocalDirector(config)# write floppyBuilding configuration...[OK]LocalDirector(config)#write net
To store the current configuration to a TFTP server, use the write net command.
write net [[tftp_server_ip] [port port]] [file file]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged and configuration
Usage Guidelines
Use the write net command to save the current running configuration to a TFTP server. Use the configure net command to restore the saved configuration.
Note
Related Commands
configure net
Posted: Wed Nov 10 22:45:02 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
