|
|
This chapter contains an alphabetical listing of the LocalDirector commands. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, and an example of the command output.
You can use the following commands to edit or view previously entered commands:
If you are using a VT100-compatible terminal, such as HyperTerminal with Windows 95 or Windows NT, the up and down arrow keys have the same effect as ^p and ^n. In addition, the left arrow key works as a backspace.
The command interpreter provides a command set that emulates Cisco IOS technologies. this command set provides three administrator access modes:
At startup, the console is in unprivileged mode. You can access privileged mode by entering the enable command. LocalDirector then prompts you for a password. When you first configure LocalDirector, a password is not required. Press the Enter key at the prompt. Assign a password to privileged mode with the enable password command. Exit privileged mode by entering the disable command.
Access configuration mode by entering the configure terminal command while in privileged mode. You can then write your settings to Flash memory, diskette, or to the console.
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.0
The syntax of the command is displayed, and the prompt returns with the previous entry on the command line. Use the pager command to control display output.
For a listing of all commands available for the current mode, enter a question mark by itself.
If you enter a command that the LocalDirector does not recognize, the "Type `?' for a list of commands" message is displayed for a variety of reasons. This could be caused by the following:
1 Incorrect access mode-Ensure you are in configuration mode before entering configuration mode commands. From unprivileged mode, enter the enable command to start privileged mode. From privileged mode, enter config terminal to start configuration mode.
2 Incorrect number of parameters-Enter the help command to check the syntax of the command that you are entering.
3 Incorrect abbreviations-Try the command again with more characters or the full command name.
Table 6-1 lists configuration commands by LocalDirector features:
| Item | Command |
|---|---|
Access modes
|
enable configure terminal disable |
ARP cache
|
arp no arp |
Configuration management
|
configure clear configuration reload write tftp-server boot |
Display output
|
show pager show history |
Connections
|
timeout synguard data show conn show stats |
Failover
|
failover replicate failover active failover reset failover ip address show failover |
Flash memory access
|
write erase show configuration reload write memory |
Floppy disk access
|
configure floppy write floppy |
Help | help, ? |
Hot-standby servers | backup |
Interface:
|
interface ethernet interface fddi mtu channel |
IP address
| failover ip address |
Load balancing
|
predictor virtual real bind show bind show conn sticky timeout weight |
MAC addresses
|
show bridge clear bridge |
Names
|
name names |
Passwords
|
enable password |
Ping
|
ping ping-allow |
Processes, show thread information | show processes |
Prompt host name, change | hostname |
Real server adjustments
|
reassign retry threshold data timeout static |
RIP listening, enable or disable | rip passive |
Routing table
|
route show route |
Security
|
secure assign ping-allow synguard |
Service state
|
in-service out-of-service autounfail restart retry |
SNMP
|
snmp-server contact snmp-server location snmp-server host |
SYSLOG
|
syslog console show syslog syslog output syslog host |
Telnet
|
telnet kill who password |
Virtual server adjustments
|
name predictor sticky |
Add an entry to the LocalDirector ARP table. (Privileged mode.)
[no] arp ip en interface number [alias]ip | IP address for the ARP table entry. |
en | Hardware MAC address for the ARP table entry. |
interface number | The interface number. |
Alias entries do not time out and are stored in the configuration with the write command. Alias entries stay in the ARP table after the LocalDirector reboots. |
The arp command adds an entry to the LocalDirector ARP table. ARP is a low-level TCP/IP protocol that resolves a node's physical address from its IP address.
Gratuitous ARPs are supported in LocalDirector version 1.6 and later.
Use no arp to delete alias ARP entries, and clear arp to remove other ARP entries.
LocalDirector(config)# arp 192.168.1.42 0000.0101.0202 0
LocalDirector(config)# arp 192.168.1.43 0000.0101.0203 1 alias
LocalDirector(config)# show arp
Interface 0:
192.168.1.42 (0000.0101.0202)
Interface 1:
192.168.1.43 (0000.0101.0203) alias
LocalDirector(config)# clear arp
LocalDirector(config)# show arp
Interface 0:
Interface 1:
192.168.1.43 (0000.0101.0203) alias
LocalDirector(config)# no arp 192.168.1.43 000.0101.0203 1
LocalDirector(config)# show arp
Interface 0: Interface 1: LocalDirector(config)#
Directs connection requests to a specific instance of a virtual server. (Configuration mode.)
[no] assign virtual_id client_ip [netmask]virtual_id | Virtual server IP address or name, port number, and bind-id. |
client_ip | The IP address of the client requesting a connection. |
netmask | The subnet mask used with the client IP address. |
Use the assign command to associate client IP addresses with specific virtual servers. If you do not specify a bind-id when defining a virtual server, the default bind-id is 0. Any client IP address not identified by an assign command statement will be 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 the bind-id of 0 is reserved for default traffic.
See the definition of Client-Assigned Load Balancing (Traffic Shaping) in Chapter 1, "Introduction" and the example of Client-Assigned Load Balancing (Traffic Shaping) in Chapter 4, "Installing and Configuring LocalDirector" for more information.
LocalDirector(config)# assign 192.9.200.1:80:1 197.89.1.0 255.255.255.0
LocalDirector(config)# assign 192.9.200.1:80:2 167.56.6.0 255.255.255.0
LocalDirector(config)#
Automatically bring a failed real server back into service. (Configuration mode.)
[no] autounfail real_idreal_id | Real server IP address or name, and port (if a port-bound server). |
A 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 will bring a failed server into testing mode if it answers or sends data on a connection that is already established. The autounfail command is on by default.
In testing mode, the real server will get one real incoming connection. If it answers that connection, it will be put in service. If it does not answer that connection, it will be failed again.
LocalDirector(config)# autounfail 192.168.1.2
LocalDirector(config)#
Assign a backup server for real and virtual servers. (Configuration mode.)
[no] backup real_id|virtual_id backup_id
real_id | The IP address or name, and port (if a port-bound server) of the real server to be backed up. |
virtual_id | Virtual server IP address or name, port number, and bind-id of the virtual server to be backed up. |
backup_id | The IP address or name, and port (if a port-bound server) of the real or virtual server that will serve as a backup. |
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 the LocalDirector. For example, if the backup is a real server it will have the same adjustable parameters (retry, timeout, reassign, etc.) that other real machines have. The predictor for the backup virtual server will be 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. This means that the following configuration:
virtual 1.1.1.1 real 2.2.2.2 real 3.3.3.3 real 4.4.4.4 real 5.5.5.5 backup 2.2.2.2 4.4.4.4 backup 3.3.3.3 5.5.5.5 bind 1.1.1.1 2.2.2.2 bind 1.1.1.1 3.3.3.3
will work; however, if you tried to bind real machine 5.5.5.5 to virtual 1.1.1.1, it will not let you since 5.5.5.5 is already serving as a backup for that virtual.
Also, if server 2.2.2.2 fails and it is backed up by 4.4.4.4, it will use that server as long as it is in service; however, if 4.4.4.4 is also failed it will not check the backup for 4.4.4.4.
LocalDirector(config)# backup server1 remote1
LocalDirector(config)# backup server2 remote1
LocalDirector(config)# backup server3 remote1
LocalDirector(config)# show backup
Machine Port Backup Port
server1 default remote1 default
server3 default remote1 default
server2 default remote1 default
LocalDirector(config)#
Associate a virtual server with one or more real servers. (Configuration mode.)
[no] bind virtual_id real_id [real_id...]
virtual_id | Virtual server IP address or name, port number, and bind-id. |
real_id | The IP address or name, and port (if a port-bound server) of a real server. A port number can also be specified. |
Use virtual or real to define the virtual and real server addresses before using bind. Use the bind command to direct network traffic from a virtual server to a real server. Use no bind to release an association between a real and virtual server.
LocalDirector(config)# bind 204.31.17.1 80 192.168.1.1 192.168.1.2
LocalDirector(config)# bind 204.31.17.1 192.168.1.3 192.168.1.4
LocalDirector(config)# show bind
Virtual Real
204.31.17.1 80 (IS)
192.168.1.2 (IS)
192.168.1.1 (IS)
204.31.17.1 default (IS)
192.168.1.4 (IS)
192.168.1.3 (IS)
LocalDirector(config)# no bind 204.31.17.1 192.168.1.3
LocalDirector(config)# show bind
Virtual Real
204.31.17.1 80 (IS)
192.168.1.2 (IS)
192.168.1.1 (IS)
204.31.17.1 default (IS)
192.168.1.4 (IS)
LocalDirector(config)#
The boot command enables booting from a remote image.
[no] boot config filename tftp_server_ipconfig | Boot a LocalDirector configuration file. |
image | Boot a LocalDirector software file. |
filename | The name of the configuration file stored on the TFTP server. |
image_filename | The name of the LocalDirector software file stored on the TFTP server. |
tftp_server_ip | The IP address of the TFTP server. |
LocalDirector configuration files and software can be stored on a TFTP server.
In the following example, the LocalDirector is booted from a remote image, but not reloaded.
localdirector(config) 8# boot image ld210115.bin 171.69.183.249
boot image /usr/users/admin/ldimage 192.168.89.9 confirm boot [N]: y
saving image from flash
copying 274944 bytes
saving config from flash
[no] boot config <filename> <tftp server ip>
boot image <image filename> <tftp server ip>erasing flash
writing image to flash
wrote 274944 bytes e.size=274944
writing the config to flash
confirm reboot on new image [N]: n
localdirector(config) 9#
In the following example, the LocalDirector is booted from a remote image and reloaded.
localdirector(config) 2# show version
LocalDirector 420 Version 0.116 localdirector(config) 3# boot image ld210115.bin 171.69.183.249
confirm boot [N]:
saving image from flash
copying 279040 bytes
saving config from flash
erasing flash
atmel_erase(): Unsupported!
writing image to flash
wrote 279040 bytes e.size=279040
writing the config to flash
confirm reboot on new image [N]:
remove floppy from drive and hit any key
Rebooting....
Finesse Bios V3.3
Booting Floppy
Loading from Flash
128MB RAM
rns23x0 Ethernet @ irq 11 dev 4 index 3 MAC: 0000.bc11.4c6b
rns23x0 Ethernet @ irq 10 dev 5 index 2 MAC: 0000.bc11.4c6a
rns23x0 Ethernet @ irq 15 dev 6 index 1 MAC: 0000.bc11.4c69
rns23x0 Ethernet @ irq 9 dev 7 index 0 MAC: 0000.bc11.4c68
Flash=AT29C040A @ 0x300
LocalDirector 420 Version 2.1.0.115
........................................
Copyright (c) 1998 by Cisco Systems, Inc.
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
localdirector 0>
The channel command is used to assign 2 or 4 ports as Fast EtherChannels.
[no] channel port two|fourport | The first interface included in the Fast EtherChannel. Two segment channels are 0, 2, 4, etc., and four segment channels are 0, 4, 8, etc. |
two|four | The number of interfaces that comprise the channel. |
The show channel starting interface command displays the aggregate numbers for the channel, that is, the sum of the numbers from the individual interfaces that comprise the channel.
localdirector 2> show channel
Fast EtherChannel 0-1 is up, line protocol is up ud Hardware is rns23x0 ethernet, address is 0000.bc11.3e0c MTU 1500 bytes, BW 200000 Kbit full duplex 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 98150 packets output, 5891299 bytes, 0 underruns localdirector 3> show interface
ethernet 0 is up, line protocol is up Hardware is rns23x0 ethernet, address is 0000.bc11.3e0c MTU 1500 bytes, BW 100000 Kbit full duplex 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 98156 packets output, 5891685 bytes, 0 underruns ethernet 1 is up, line protocol is down Hardware is rns23x0 ethernet, address is 0000.bc11.3e0c MTU 1500 bytes, BW 100000 Kbit full duplex 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns ethernet 2 is down, line protocol is up Hardware is rns23x0 ethernet, address is 0000.bc11.3e0e MTU 1500 bytes, BW 100000 Kbit full duplex 98084 packets input, 5885226 bytes, 0 no buffer Received 1 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns ethernet 3 is up, line protocol is up Hardware is rns23x0 ethernet, address is 0000.bc11.3e0f MTU 1500 bytes, BW 10000 Kbit half duplex 337 packets input, 22827 bytes, 0 no buffer Received 30 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 35212 packets output, 2114369 bytes, 0 underruns localdirector 4>
Combine with other commands to delete information associated with the other commands. (Privileged and Configuration mode.)
clear (variable command)secondary | Clears information about virtual and real servers, server bindings, backup servers, and load balancing. |
primary | Clears settings for routing, failover, network interfaces, passwords, error logging, and networking. |
all | Clears all configuration information. |
Use the clear command with arp, bridge, configuration, route, snmp-server, syslog, and telnet to clear the values associated with those commands.
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.
LocalDirector(config)# show arp
Interface 0:
192.168.1.42 (0000.0101.0202)
Interface 1:
LocalDirector(config)# clear arp
LocalDirector(config)# show arp
Interface 0: Interface 1:
Define the current configuration. (Privileged mode.)
configure {floppy|memory|terminal|net}
floppy | Merge the current running configuration with the configuration stored on diskette with the write floppy command. |
memory | Merge the configuration in Flash memory with the current configuration in RAM. |
terminal | |
net | Configure from a remote TFTP server. To use this option, issue the tftp-server command first, or include the full path name of the file and the IP address of the TFTP server. |
Each statement is read into the current configuration and evaluated with these rules:
LocalDirector 4# configure terminal
LocalDirector(config) 5# real 192.168.1.1:0
LocalDirector(config) 6# show real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.1:0 0 OOS 8 0 0 0
LocalDirector(config) 7#
Limit number of connections to a server that has an open connection to a client but is not sending data in response to a request. (Configuration mode.)
[no] data real_id [number of connections]
real_id | The IP address or name, and port (if a port-bound server) of a real server. |
number of connections | The number of connections to allow to a real server where data has been requested, but no data has been sent by server. The feature is disabled by default with an initial value of 0. To calculate this value, examine the data count during busy periods, and double it. |
Some web servers (especially those running Microsoft Windows NT 4.0) will 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 sent to a server that is not sending data.
There is no time interval associated with the data command, and the following explains the sequence of events that determine whether or not the server is responding:
1 Client sends SYN.
2 Server kernel responds with SYN/ACK.
3 Client sends HTTP GET request (LocalDirector counts this as one data request).
4 If the Server responds, the LocalDirector subtracts 1 from the count.
5 If the count reaches a preset threshold, the LocalDirector fails the server.
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), the LocalDirector does not recognize this as a real machine 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 machine reaches this number, the LocalDirector will check to see if other machines bound to the virtual server are also at 80 percent of their threshold capacity (based on DataIn value). If the other machines are close to reaching this value, then the LocalDirector assumes the site is busy and does not fail the machine.
If the other machines are not at this capacity, then the LocalDirector fails the real machine and sends the following SYSLOG/SNMP message:
Real machine 'x' Failed Application
The 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. Use the no data command to return to the default value of 0.
localdirector(config) 5# show real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.1:0 0 IS 8 0 0 0
localdirector(config) 6# show data
Machine DataIn
192.168.1.1:0 50
localdirector(config) 7# data 192.168.1.1:0 30
localdirector(config) 8# show data
Machine DataIn
192.168.1.1:0 30
localdirector(config) 9#
Keep connections in LocalDirector memory for five minutes after TCP ending sequence. (Configuration mode.)
[no] delay virtual_id
virtual_id | Virtual server IP address or name, port number, and bind-id. |
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 will remain in memory for approximately five minutes.
If any data arrives for the connection, it will be put back in an "active" state. If any other packet comes across for the connection, the packet will pass through the virtual server, but the connection will not be 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 the LocalDirector to drop the connection even though it has not completed.
localdirector(config) 1# virtual 10.10.10.1
localdirector(config) 2# delay 10.10.10.1
localdirector(config) 3# show delay
Machine Deletion
10.10.10.1:0:0 normal
localdirector(config) 4#
Exit privileged mode and return to unprivileged mode. (Privileged mode.)
disableThe disable command exits privileged mode and returns you to unprivileged mode. Use the enable command to return to privileged mode.
LocalDirector# disable
LocalDirector>
Start privileged mode. (Unprivileged mode.)
enableThe 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 disable to exit privileged mode. Use enable password to change the privileged mode password.
In the example below, note that the prompt changes from ">" to "#" when you enter privileged mode.
LocalDirector> enable
Password: ####### LocalDirector# disable
LocalDirector>
Set the privileged mode password. (Privileged mode and Configuration mode.)
enable password password
password | A password of up to 16 alphanumeric characters, which is not case sensitive. LocalDirector converts the password to all lowercase. |
The enable password command changes the privileged mode password, for which you are prompted after you enter the enable command. When you first configure LocalDirector, a password is not required and you can press the Enter key at the prompt. Assign a password to privileged mode with the enable password command.
LocalDirector(config)# enable password fnord42
LocalDirector(config)#
Enable access to the optional failover feature. (Configuration mode.)
[no] failover [active]
[active] | Make a LocalDirector the active unit. Use this command to make a standby unit active. Either enter no failover active on the active unit to switch service back to the standby unit, or enter failover active on the standby unit. |
ip address | This IP address will be used by the standby unit to communicate with the active unit. Use this IP address with the ping command to check the status of the standby unit. This address must be on the same network as the system IP address. For example, if the system IP address is 192.168.1.1, set the failover IP address to 192.168.1.2. |
reset | Forces both units back to an unfailed state. Use this command instead of rebooting the LocalDirector. This will not cause a switch to occur, and if the LocalDirector still has problems, it will be failed again. The failover reset command can be entered from either unit, but it is best to always enter commands at the active unit. Entering the failover reset command at the active unit will "unfail" the standby unit and clear the "Active time" counter displayed in the show failover command output. |
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. The default configuration includes the no failover command; however if the failover cable is present at boot-up, it will be detected automatically and failover will be enabled. 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 basis.
Failover works by passing control to the secondary unit should the primary 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.
The following output shows failover on, and the primary unit state is active:
ld-prim(config)# failover ip address 192.168.89.2
ld-prim(config)# show failover
Failover On Cable status: Normal This host: Primary - Active Active time: 6885 (sec) Interface 0 (192.168.89.1): Normal Interface 1 (192.168.89.1): Normal Other host: Secondary - Standby Active time: 0 (sec) Interface 0 (192.168.89.2): Normal Interface 1 (192.168.89.2): Normal
The following example shows the show failover output if failover has not started monitoring the network interfaces:
ld-prim(config)# show failover
Failover On Cable status: Normal This host: Primary - Active Active time: 6930 (sec) Interface 0 (192.168.89.1): Normal (Waiting) Interface 1 (192.168.89.1): Normal (Waiting) Other host: Secondary - Standby Active time: 15 (sec) Interface 0 (192.168.89.2): Normal (Waiting) Interface 1 (192.168.89.2): Normal (Waiting)
Display help information. (All modes.)
helpThe 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.
LocalDirector(config)# arp ?
usage: [no] arp <ip> <en> [alias] LocalDirector(config)# arp
Change the host name in the LocalDirector command line prompt. (Configuration mode.)
hostname newname
newname | New host name for the LocalDirector prompt. This name can be up to |
The hostname command changes the host name label on prompts.
LocalDirector(config)# hostname lab1
lab1(config)#
Configure network interfaces. (Configuration mode.)
[no] interface ethernet|fddi interface number
interface number | The interface number. |
10baseT | Sets 10 Mbit Ethernet and half duplex communications. |
100baseTX | Sets 100 Mbit Ethernet and half duplex communications. |
100full | Sets 100 Mbit Ethernet and full duplex communications. |
auto | Automatically determines networking speed and sets full duplex communications, if available. This is the recommended full duplex Ethernet option, but the network interface must support auto-detection. |
fddi | Identifies the interface as FDDI. |
The interface command identifies the type of network interface boards, and the speed and duplex settings for Ethernet. Use show interface to view information about the interface.
Use the no interface command to disable access to the network interface. This is important if failover is configured, because failover will see the unused interfaces as failed if they are not turned off.
To configure full duplex Ethernet, the auto option is recommended, but your network interface has to support auto-detection. You can force the Ethernet argument to accept full duplex with the 100full option if the network accepts full duplex and 100 megabit Ethernet.
localdirector(config) 9# show interface
ethernet 0 is down, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c68
MTU 1500 bytes, BW 10000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 1 is down, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c69
MTU 1500 bytes, BW 10000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 2 is up, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c6a
MTU 1500 bytes, BW 100000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 3 is up, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c6b
MTU 1500 bytes, BW 100000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
localdirector(config) 0# interface ethernet 0 100full
localdirector(config) 1# interface ethernet 1 auto
WARNING: setting rns23x0 to autosense mode which
is incompatible with autonegotiating devices
localdirector(config) 2# show interface
ethernet 0 is down, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c68
MTU 1500 bytes, BW 100000 Kbit full duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 1 is down, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c69
MTU 1500 bytes, BW 10000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 2 is up, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c6a
MTU 1500 bytes, BW 100000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
ethernet 3 is up, line protocol is down
Hardware is rns23x0 ethernet, address is 0000.bc11.4c6b
MTU 1500 bytes, BW 100000 Kbit half duplex
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
localdirector(config) 3#
Mark a real or virtual server as being in service (IS). (Configuration mode.)
in-service {virtual|real} virtual_id|real_id [all]
virtual | Mark a virtual server as in service. |
real | Mark a real server as in service. |
virtual_id | Virtual server IP address or name, port number, and bind-id of the virtual server that will be put in service. |
real_id | The IP address or name, and port (if a port-bound server) of the real server that will be put in service. |
[all] | Mark all virtual servers or all real servers with the same IP address as in service. Port numbers and bind-ids do not have to be specified. |
The in-service command indicates that the virtual server or real server is ready to accept connections.
In following example, the in-service (is) command is used with the all option 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 real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.3:0 0 OOS 8 0 0 0
192.168.1.3:21 0 OOS 8 0 0 0
192.168.1.3:80 0 OOS 8 0 0 0
www.domain.com:0 0 OOS 8 0 0 0
www.domain.com:21 0 OOS 8 0 0 0
www.domain.com:80 0 OOS 8 0 0 0
192.168.1.1:0 0 OOS 8 0 0 0
192.168.1.1:21 0 OOS 8 0 0 0
192.168.1.1:80 0 OOS 8 0 0 0
LocalDirector(config) 1# is real 192.168.1.1 all
LocalDirector(config) 2# is real www.domain.com
LocalDirector(config) 3# is real 192.168.1.3:80
LocalDirector(config) 4# show real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.3:0 0 OOS 8 0 0 0
192.168.1.3:21 0 OOS 8 0 0 0
192.168.1.3:80 0 IS 8 0 0 0
www.domain.com:0 0 IS 8 0 0 0
www.domain.com:21 0 OOS 8 0 0 0
www.domain.com:80 0 OOS 8 0 0 0
192.168.1.1:0 0 IS 8 0 0 0
192.168.1.1:21 0 IS 8 0 0 0
192.168.1.1:80 0 IS 8 0 0 0
LocalDirector(config) 5#
Assign the system IP address for the LocalDirector. (Configuration mode.)
ip address ip [subnet_mask]
ip | System IP address of the LocalDirector. |
[subnet_mask] | Subnet mask of LocalDirector network. |
The ip address command assigns an IP address to the 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.
See also: failover
LocalDirector(config) 4# ip address 192.168.89.1 255.255.255.0
LocalDirector(config) 4# failover ip address 192.168.89.2
LocalDirector(config) 5# show ip address
System IP 192.168.89.1, system subnet 255.255.255.0 Current IP 192.168.89.2 LocalDirector(config) 6#
Terminate a Telnet session. (Privileged mode.)
kill id
id | Telnet session ID. |
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.
LocalDirector(config)# show who
2: From 192.168.2.2 1: From 192.168.1.3 0: On console LocalDirector(config)# kill 2
LocalDirector(config)# who
1: From 192.168.1.3 0: On console
Set the maximum number of connections that LocalDirector will send to a real server. (Configuration mode.)
[no] maxconns real_id number
real_id | The IP address or name, and port (if a port-bound server) of the real server. |
number | The maximum number of connections allowed for the server, or "unlimited" if there is no limit. |
You can set the maximum number of connections that a real server accepts to avoid overloading the server. There is no default setting for maxconns, and the value is "unlimited" when viewed with the show maxconns command.
LocalDirector(config)# show maxconns
Machine Port Limit
192.168.1.1 default unlimited
192.168.1.2 default unlimited
LocalDirector(config)# maxconns 192.168.1.1 500
LocalDirector(config)# show maxconns
Machine Port Limit
192.168.1.1 default 500
192.168.1.2 default unlimited
LocalDirector(config)#
Specify the maximum transmission unit (MTU) value for the specified network interface. (Configuration and Privileged modes.)
mtu interface number bytes
interface number | The interface number. |
bytes | The MTU for the interface. Specify a number between 64 and 65,535. |
For Ethernet interfaces, the default MTU should be 1,500 bytes in a block; for FDDI, specify 4,096 bytes.
The value for the mtu command depends on the type of network interface specified in the interface command. The minimum value for val is 64 and the maximum is 65,535 bytes.
LocalDirector(config)# show mtu
mtu 0 1500 mtu 1 1500 LocalDirector(config)# mtu 0 4096
LocalDirector(config)# show mtu
mtu 0 4096 mtu 1 1500
Associate a name with an IP address. (Configuration mode.)
[no] name ip name
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. |
Use the name command to identify a virtual or real server by a text name. This 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 when identifying 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 do not have to be synchronized with DNS.
In the example that follows, the name command is used to identify IP address 192.168.1.1 as "v1" and then it is defined as a virtual server with the virtual command. This creates a virtual server with a default port of 0 and a bind-id of 0.
ld(config) 8# name 192.168.1.1 v1
ld(config) 9# virtual v1
Two more virtual servers 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:1
ld(config) 1# virtual v1:80:2
A 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:1
ld(config) 3# name 192.168.1.2 v2
ld(config) 4# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
v1:80:2 OOS 0 0 leastconns roundrobin*
v1:80:1 OOS 0 0 leastconns roundrobin*
v1:0:0 OOS 0 0 leastconns roundrobin*
v2:443:1 OOS 0 0 leastconns roundrobin*
The name "v1" is used as the virtual_id with the in-service command and the all option to put all virtual servers with IP address 192.168.1.1 in service.
ld(config) 5# is virtual v1 all
ld(config) 6# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
v1:80:2 IS 0 0 leastconns roundrobin*
v1:80:1 IS 0 0 leastconns roundrobin*
v1:0:0 IS 0 0 leastconns roundrobin*
v2:443:1 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:1
ld(config) 8# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
v1:80:2 IS 0 0 leastconns roundrobin*
v1:80:1 IS 0 0 leastconns roundrobin*
v1:0:0 IS 0 0 leastconns roundrobin*
v2:443:1 OOS 0 0 leastconns roundrobin*
v2:80:1 OOS 0 0 leastconns roundrobin*
ld(config) 9#
Determine whether IP addresses or server names display in screen output. (Configuration mode.)
[no] namesYou 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.
LocalDirector(config)# show names
names are on LocalDirector(config)# show real
Real Machines: No Answer TCP Reset DataIn Machine Port Connect State Thresh Reassigns Reassigns Conns server1 default 0 IS 8 0 0 0 server2 default 0 IS 8 0 0 0 LocalDirector(config)# no names
LocalDirector(config)# show real
Real Machines: No Answer TCP Reset DataIn Machine Port Connect State Thresh Reassigns Reassigns Conns 192.168.0.1 default 0 IS 8 0 0 0 192.168.0.2 default 0 IS 8 0 0 0 LocalDirector(config)# show names
names are off LocalDirector(config)#
Mark a virtual or real server as being out of service (OOS). (Configuration mode.)
out-of-service {virtual|real} real_id|virtual_id [all]
virtual | Mark a virtual server as out of service. |
real | Mark a real server as out of service. |
real_id | The IP address or name, and port (if a port-bound server) of a real server. |
virtual_id | Virtual server IP address or name, port number, and bind-id. |
[all] | Mark all virtual servers or all real servers with the same IP address as out of service. Port numbers and bind-ids do not have to be specified. |
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 show real to watch the status of open connections; when all connections appear as OOS, you can power-off the server or reconfigure it as required.
In following example, the out-of-service (oos) command is used with the all option to take all ports of real server 192.168.1.1 out-of-service. This takes all ports of the real server (both default and port-bound) 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 real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.3:0 0 IS 8 0 0 0
192.168.1.3:21 0 IS 8 0 0 0
192.168.1.3:80 0 IS 8 0 0 0
www.domain.com:0 0 IS 8 0 0 0
www.domain.com:21 0 IS 8 0 0 0
www.domain.com:80 0 IS 8 0 0 0
192.168.1.1:0 0 IS 8 0 0 0
192.168.1.1:21 0 IS 8 0 0 0
192.168.1.1:80 0 IS 8 0 0 0
LocalDirector(config) 2# oos real 192.168.1.1 all
LocalDirector(config) 3# oos real www.domain.com
LocalDirector(config) 4# oos real 192.168.1.3:80
LocalDirector(config) 5# show real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.3:0 0 IS 8 0 0 0
192.168.1.3:21 0 IS 8 0 0 0
192.168.1.3:80 0 OOS 8 0 0 0
www.domain.com:0 0 OOS 8 0 0 0
www.domain.com:21 0 IS 8 0 0 0
www.domain.com:80 0 IS 8 0 0 0
192.168.1.1:0 0 OOS 8 0 0 0
192.168.1.1:21 0 OOS 8 0 0 0
192.168.1.1:80 0 OOS 8 0 0 0
LocalDirector(config) 6#
Control display output. The pager command is on by default. (Configuration and Privileged modes.)
[no] pagerlines | Indicates that you are defining the number of lines that will be displayed. In order to use this option, pager must be turned on first (see example). |
number | The number of lines displayed. |
If the pager option is on, only one screen of output appears at a time. Pressing the spacebar displays the next page of information, and pressing Enter displays the next line. Pressing the "q" key stops the output and returns to the system prompt.
If the no pager command is used, screen output scrolls until the end without stopping.
Use the show pager command to see if the pager option is on or off.
LocalDirector(config)# show pager
pager is off LocalDirector(config)# pager lines 20
turn pager on first LocalDirector(config)# pager
LocalDirector(config)# pager lines 20
LocalDirector(config)# show pager
pager is on LocalDirector(config)#
Modify Telnet login password. (Configuration mode.)
password password
password | A password of up to 16 alphanumeric characters, which is not case sensitive. LocalDirector converts the password to all lowercase. |
The password command sets a password for Telnet access. The default password is cisco, and it should be changed from the default.
See also: enable password
LocalDirector(config)# password athensge0rg1a
LocalDirector(config)#
Send a ping request message. (Configuration mode.)
ping ip
ip | The IP address of a host on the network. |
The ping command determines if the 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 show interface to ensure that the LocalDirector is connected to the network and has connectivity.
The command displays three attempts to reach the specified address:
LocalDirector(config)# ping 192.168.42.54
192.168.42.54 response received - 10Ms 192.168.42.54 response received - 10Ms 192.168.42.54 response received - 10Ms LocalDirector(config)#
Turn on or off the ability to ping a virtual address. The default is to not allow a virtual address to be pinged. (Configuration mode.)
[no] ping-allow interface numberinterface number | The interface number. |
By default, virtual addresses cannot be pinged. This 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.
The following example allows a virtual address to be pinged from interface 0:
LocalDirector(config)# ping-allow 0
LocalDirector(config)#
Choose the type of load balancing for each virtual server. (Configuration mode.)
predictor virtual_id {fastest|roundrobin|leastconns|weighted|loaded} [none]
virtual_id | Virtual server IP address or name, port number, and bind-id. |
fastest | Assigns new connections to the physical server with the fastest predicted response time. |
roundrobin | Rotates through the list of physical servers bound to virtual, assigning connections to the next server. |
leastconns | Assigns new connections to the physical server that has the least number of current connections. This is the default. |
weighted | Assigns new connections based on values set with the weight command. The default weight for each server is one. |
loaded | Assigns a weighted portion of connections to a server before moving to the next. |
none | Disables slowstart for the virtual server. |
Each virtual server can have a different predictor option. The show virtual command shows an asterisk (*) next to the active predictor. This indicates 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. The LocalDirector will rotate through the servers until the number of connections reaches a pre-determined level when slowstart is enabled. This avoids overloading a server with too many requests when it is brought in-service. The slowstart option is enabled by default.
The leastconns predictor option 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 does quite well. At web sites where there is a collection of servers with similar performance, the leastconns option is effective in smoothing distribution in situations where a server gets bogged down for one reason or another. In sites where there are large differences in the capacity of various servers, the leastconns option also performs very well. In maintaining the same amount of connections to all servers, those 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 does, in fact, get about twice as many connections per second.
The weighted predictor option allows you to assign a performance weight to each server. Weighted load balancing is similar to leastconns, but servers with a higher weight value will receive a larger percentage of connections at any one time. LocalDirector administrators can assign a weight to each real server, and the LocalDirector will use 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:
This will result in server1 getting 7/24 of the current number of connections, server2 getting 8/24, server3 getting 2/24, etc. If a new server, server6, is added with a weight of 10, it will get 10/34, and so on.
The weighted predictor will give new connections to the real machine that is in most need of a connection based on how many connections the virtual machine 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.
Based on weights, the load should be distributed as follows:
The actual percentage of connections to the real servers is as follows:
Thus, real server 1.1.1.4 will receive connections to bring it closer to having 44% of the connections at the time.
The roundrobin predictor option 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 roundrobin predictor appears similar to DNS round robin, it is superior because there is no propagation delay or caching that will hinder the algorithm. Also, the LocalDirector can determine when a server is not responding, and avoid sending connections to that server.
The fastest predictor option 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.
Use the loaded predictor to give each server a weighted number of connections in a row (roundrobin 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, etc.
LocalDirector(config) 9# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
www.domain.com:0:0 OOS 0 0 leastconns roundrobin*
LocalDirector(config) 0# predictor www.domain.com weighted none
LocalDirector(config) 1# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
www.domain.com:0:0 OOS 0 0 weighted* none
LocalDirector(config) 2#
Define a real server. (Configuration mode.)
[no] real real_ip|real_name [:real_port] [service-state]
real_ip | The IP address of a real server. |
real_name | The name of a real server. |
real_port | The port traffic that will run on the server. Use a colon as a delimiter between the IP address and port number. If you do not identify a specific port, all traffic will be allowed to the server and the port will be labeled "default." Zero is the same as default. Servers with a port specified are referred to as "port-bound" servers. |
service-state | In service (is) or out of service (oos). The default is oos. |
Real servers are actual host machines with unique IP addresses that provide TCP/IP services to the network. Use no real to remove a real server from LocalDirector. 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:
The show real command provides the following information:
| Column heading | Description |
|---|---|
Machine | IP address and port (if a port-bound server) or name of the server. |
Connect | the current number of connections to the server. This does not include direct connections to the server that are bridged by the LocalDirector. |
State | IS (in-service), OOS (out-of-service), failed, or testing. |
Thresh | threshold value for reassignments before server is marked as failed. |
No Answer Reassigns | number of connections that are not answered by a real server. |
TCP Reset Reassigns | number of connections that are reassigned because a real server responded with a RST on a new connection. |
DataIn Conns | number of clients requesting but not receiving data. |
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.1
ld(config) 2# real 192.168.1.1 80 is
ld(config) 3# real 192.168.1.1:23
ld(config) 4# show real
Real Machines:
No Answer TCP Reset DataIn
Machine Connect State Thresh Reassigns Reassigns Conns
192.168.1.1:23 0 OOS 8 0 0 0
192.168.1.1:80 0 IS 8 0 0 0
192.168.1.1:0 0 OOS 8 0 0 0
Set number of retries to a real server before the connection is reassigned to another server. (Configuration mode.)
reassign real_id val
real_id | The IP address or name, and port (if a port-bound server) of a real server. |
val | The number of retries allowed. This value can be a number between |
If reassign is at the default of 3, then TCP will attempt to connect three times before going to another server (TCP SYNs are counted). If threshold is set to 8, this can happen eight times before the server is marked as failed.
LocalDirector(config)# show reassign
Machine Port Reassign 192.168.89.252 default 3 192.168.89.251 default 3 LocalDirector(config)# reassign 192.168.89.252 4
LocalDirector(config)# show reassign
Machine Port Reassign 192.168.89.252 default 4 192.168.89.251 default 3 LocalDirector(config)#
Reboot and reload the configuration. (Configuration and Privileged modes.)
reloadThe reload command reboots the LocalDirector and reloads the configuration from Flash memory.
LocalDirector# reload
Proceed with reload?[confirm] Rebooting...
The replicate command enables stateful failover. (Configuration mode.)
[no] replicate virtual_id
interface number | The interface through which the active LocalDirector unit sends connection replication data to the standby unit. The default is interface 0. |
virtual_id | Virtual server IP address or name, port number, and bind-id of the virtual server for which connections will be replicated. |
Connection replication is a property of the virtual server, and it is set and cleared with the replicate command. This will replicate all established connections to standby unit. In the event of a LocalDirector failure (with failover configured), the standby unit will have information for current connections, and will keep connections to the virtual server alive.
This is settable on a per-virtual basis, which means you can turn it on for 3270 and leave it off for HTTP. Because HTTP connections are short-lived, it is not recommended that the LocalDirector maintain state for these connections.
Use the replicate interface command to dedicate an interface to stateful failover.
LocalDirector(config) 6# replicate 10.10.10.10
LocalDirector(config) 7# replicate interface 3
LocalDirector(config) 8# show replicate
replicate interface 3
Machine Replicate
10.10.10.10:0:0 on
LocalDirector(config) 9#
Take a server out of service, and then bring it back in service. (Privileged and Configuration modes.)
restart real|virtual [real_id|virtual_id]real_id | The IP address or name, and port (if a port-bound server) of the real server that will be restarted. |
virtual_id | Virtual server IP address or name, port number, and bind-id of the virtual server that will be restarted. |
The restart command takes a server out-of-service and puts it back in-service with one command.
LocalDirector(config)# restart real server1
LocalDirector(config)#
Specify the number of minutes before a failed machine will be sent a live connection to check its state. (Configuration mode.)
retry real_id val
real_id | Real server IP address or name and port (if a port-bound server). |
val | The number of minutes before a failed server is retried. The default is one minute. |
The retry command sets the number of minutes before a failed real machine is assigned another connection. If the retry is set to zero, the failed server will not be retried until the server is brought back into service with the in-service command.
LocalDirector(config)# show retry
Machine Port Retry
server1 default 1
server2 default 1
LocalDirector(config)# retry server1 5
LocalDirector(config)# show retry
Machine Port Retry
server1 default 5
server2 default 1
LocalDirector(config)#
Enable IP routing table updates from received RIP broadcasts. (Configuration mode.)
[no] rip passiveIf 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. The LocalDirector does not broadcast RIP, it only listens to RIP.
LocalDirector(config)# show rip
no rip passive LocalDirector(config)# rip passive
LocalDirector(config)# show rip
rip passive LocalDirector(config)#
Add a static route to the IP routing table. (Configuration mode.)
[no] route dest_net net_mask gateway [metric]
dest_net | Destination IP network address; if default route, specify as all zeros (0.0.0.0). |
net_mask | Subnet mask for the network; if default route, specify as all zeros (0.0.0.0). |
gateway | The adjacent gateway to reach network. |
[metric] | Optional distance metric (defaults to one). |
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 will not overwrite a route that is already established.
LocalDirector(config)# route 0.0.0.0 0.0.0.0 192.168.1.1 1
LocalDirector(config)#
The secure command turns bridging on or off per interface. (Configuration mode.)
[no] secure interface number
interface number | The interface that is secured against bridged traffic. By default, bridging is off. |
The secure command blocks bridged traffic bound for a specific interface in the LocalDirector without affecting traffic that is load-balanced through a virtual server. Only traffic being serviced by a virtual server will traverse the inteface, and there will be no bridged traffic to or from the interface.
LocalDirector(config) 0# secure 0
LocalDirector(config) 1# secure 1
LocalDirector(config) 2# show secure
secure 0 secure 1 LocalDirector(config) 3# no secure 0
LocalDirector(config) 4# show secure
no secure 0 secure 1 LocalDirector(config) 5#
View LocalDirector information. (All modes.)
show (variable command)Any settings left at their default values 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 to this is the show configuration command which displays the configuration stored in Flash memory, and therefore will 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.
See also: pager
LocalDirector(config)# show real
Real Machines: No Answer TCP Reset DataIn Machine Port Connect State Thresh Reassigns Reassigns Conns 192.168.1.1 80 0 IS 8 0 0 0 192.168.1.1 21 0 IS 8 0 0 0 192.168.1.1 default 0 IS 8 0 0 0 www.domain.com 80 0 OOS 8 0 0 0
Configure the LocalDirector SNMP agent. (Configuration mode.)
[no] snmp-server contact text
contact | Your name or that of the LocalDirector system administrator. |
host | The IP address of a host to which SNMP traps should be sent. You can specify a maximum of 64 host IP addresses, one per command. |
location | The LocalDirector location. |
text | When used with contact, specify your name or that of the LocalDirector system administrator. When used with location, specify your LocalDirector location. |
ipaddr | When used with host, the IP address of a host to which SNMP traps should be sent. You can specify a maximum of 64 host IP addresses. |
This command configures the SNMP agent on the LocalDirector. LocalDirector converts the contact and location information to lowercase.
To configure SNMP, use the following commands:
cisco.ciscoMgmt.ciscoLocalDirectorMIB.ciscoLocalDirectorMIBObjects
ciscoMgmt.*.cldVirtualMachine.cldVirtualTable.cldVirtualTableEntry
ciscoMgmt.*.cldReallMachine.cldRealTable.cldRealTableEntry
All syslog messages are sent as an enterprise(cisco) trap.
OID{1.3.6.1.4.1.9.9.41.2} Generic trap=6, Specific Trap=1
All of the HPOV commands are in the /opt/OV/bin directory. When using HPOV, you must use a name for the LocalDirector, and the name must be listed in the /etc/hosts file.
The xnmbrowser on the command line is recommended for viewing the mibs.
LocalDirector(config)# show snmp-server
no snmp-server contact no snmp-server location LocalDirector(config)# snmp-server contact System Administrator
LocalDirector(config)# snmp-server location Corporate Headquarters
LocalDirector(config)# snmp-server host 10.10.10.2
LocalDirector(config)# show snmp-server
snmp-server host 10.10.10.2 snmp-server contact system administrator snmp-server location corporate headquarters LocalDirector(config)#
The static command translates a real server IP address to that of a virtual server. (Configuration mode.)
static real_id [real_port] virtual_id
real_id | The IP address of the real server that will be translated. |
real_port | The port associated with the real server. |
virtual_id | The virtual address that the real server will be translated to. The virtual server must exist on the LocalDirector, but it does not have to have real servers bound to it. |
Use the static command to translate a real server address to a virtual server address. This 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 will be 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_port exists as a port-bound server, then the outbound connection will be counted towards the number of connections for that real server (that is, it will affect load balacing); otherwise, the connection is only translated and does not affect load balancing.
localdirector(config) 6# static 10.10.10.220:0 192.168.1.1:0:0
localdirector(config) 7# show static
Real Machine Static Machine Connect
10.10.10.220:0 192.168.1.1:0:0 0
localdirector(config) 8#
Set the number of minutes defining the period of inactivity between connections before the client is sent to another server. (Configuration mode.)
[no] sticky virtual_id minutes
virtual_id | Virtual server IP address or name, port number, and bind-id. |
minutes | The elapsed time of connection inactivity, after which a connection from the same client can be reassigned to a different real server. The default is 0 minutes, and the maximum value is 65535 (45.5 days). |
The sticky command ensures that the same client (based on IP address) gets the same server for multiple connections. This 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 will ensure that multiple connections are sent to the same server in order to complete the transaction.
The sticky command is not timing how long a client will be 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 after five minutes. However, if five minutes of connection inactivity elapse, the requests from the client could be sent to another real server.
Use show sticky or show virtual to display the sticky value. Use the no sticky command to turn sticky off and return to the default value of 0.
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
ld(config) 6# virtual 192.168.1.1:80:0
ld(config) 7# sticky 192.168.1.1:443:0 10
ld(config) 8# show sticky
Machine Sticky
192.168.1.1:443:0 10
192.168.1.1:80:0 0
ld(config) 9#
Set the number of unanswered SYNs to a virtual server before entering synguard mode. (Configuration mode.)
A SYSLOG message is sent when the LocalDirector enters synguard mode.
[no] synguard virtual_id countvirtual_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. |
The synguard command provides limited protection against SYN attacks to the virtual IP address. Once the number of unanswered SYNs set with synguard command is reached, the LocalDirector starts to protect the real network and servers from a SYN attack.
Use the no synguard command to return to the default value of 0. The show synguard command displays synguard settings and whether or not synguard is active, and the show syn command displays the number of connections and SYN count for the virtual server.
LocalDirector(config) 1# show synguard
Machine SynGuard Status
www.domain.com:0:0 0
LocalDirector(config) 2# synguard www.domain.com 400
LocalDirector(config) 3# show synguard
Machine SynGuard Status
www.domain.com:0:0 400
LocalDirector(config) 4# show syn
Machine Conns Syn Count www.domain.com:0:0 722 400 LocalDirector(config) 5#
Log messages to SYSLOG server. (Configuration mode.)
[no] syslog {host|console} ip
host | Define which hosts are sent SYSLOG messages. |
console | Displays SYSLOG messages on the console port. Use no syslog console to stop the display. SYSLOG messages to the console will appear as they are logged, and may appear in the middle of other screen information. SYSLOG messages scroll on the screen without pausing. This command is not stored in the configuration. |
output | Set the facility number and error level for messages sent to SYSLOG, hosts, and to the console. |
ip | The IP address of the log host. |
facility | Eight facilities LOCAL0(16) through LOCAL7(23); the default is LOCAL4(20). Hosts file the messages based on the facility number in the message. The facility number is a unique device number that identifies logging information and is saved in a log file shared by a number of devices. |
level | Message type; sets the level above which LocalDirector suppresses messages to the SYSLOG hosts. Setting the level to 3, for example, allows messages with levels 0, 1, 2, and 3 to display. The default is 3. The levels are: · 0 - System unusable · 1 - Take immediate action · 2 - Critical condition · 3 - Error message · 4 - Warning message · 5 - Normal but significant condition · 6 - Informational · 7 - Debug message |
Messages are sent to the SYSLOG host over UDP. Use the syslog host command to specify which systems receive the messages. You can use show syslog to view previously sent messages.
The syslog console command is not stored in the LocalDirector configuration. This is because the console for a Telnet user may not be available when the box 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 the LocalDirector with the IP address of the log host.
To configure SYSLOG, use the following commands:
To configure a UNIX system to accept SYSLOG messages, take the following steps:
Step 1 Use the LocalDirector syslog host command to configure the LocalDirector to send SYSLOG messages to the UNIX host's IP address.
Step 2 Log into the UNIX system as root (superuser) and execute the following commands; change name to the log file in which you want SYSLOG messages to appear:
Step 3 While still logged in as root, edit the /etc/syslog.conf file with a UNIX editor and add the following selector and action pairs for each message type you want to capture:
| Message Priority | UNIX syslog.conf File Keyword |
|---|---|
0 - Emergency | local n.emerg |
1 - Immediate action | local n.alert |
2 - Critical condition | local n.crit |
3 - Error | local n.err |
4 - Warning | local n.warning |
5 - Notice | local n.notice |
6 - Information | local n.info |
7 - Debug | local n.debug |
In the syslog.conf file, code 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 you use the default LOCAL4 facility, the syslog.conf statements would be:
This configuration directs LocalDirector SYSLOG messages to the specified file. Alternatively, if you want the message sent to the logging host console or emailed to a system administrator, refer to the UNIX syslog.conf(4) manual page.
Entries in /etc/syslog.conf must obey these rules:
Step 4 Inform the SYSLOG server program on the UNIX system to reread the syslog.conf file by sending it a HUP (hang up) signal with the following commands:
The first command lists the SYSLOG process ID. This number may vary by system. The second command sends SYSLOG the HUP signal to restart.
The following example shows SYSLOG error messages generated by a bridge loop:
LocalDirector(config) 5# show syslog
OUTPUT 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#
Add authorized IP addresses for Telnet access to LocalDirector. (Configuration mode.)
[no] telnet ip mask
ip | The IP address or network of a host that is authorized to access the LocalDirector Telnet management interface. |
mask | The subnet mask for the network specified in this command. Use any valid mask, or a network IP address to enable access to all in the subnet; for example if you set mask to 255.255.255.0, all systems in the subnet can access the LocalDirector over Telnet. If you set mask to 255.255.255.255, only the IP address you specify can access the LocalDirector. |
The telnet command is used to identify who can configure the LocalDirector via Telnet. Up to 16 hosts or networks are allowed access to the LocalDirector console, four simultaneously. The show telnet command displays the list of IP addresses authorized to access the LocalDirector. Use no telnet or clear telnet to remove Telnet access from an IP address. Use the who command to view IP addresses that are accessing the LocalDirector.
Use the password command to change the access password for Telnet.
LocalDirector(config)# telnet 192.168.1.3 255.255.255.255 LocalDirector(config)# telnet 192.168.1.4 255.255.255.255
LocalDirector(config)# telnet 192.168.2.0 255.255.255.0
LocalDirector(config)# show telnet
192.168.1.3 255.255.255.255
192.168.1.4 255.255.255.255
192.168.2.0 255.255.255.0
LocalDirector(config)# no telnet 192.168.1.3
LocalDirector(config)# show telnet
192.168.1.4 255.255.255.255
192.168.2.0 255.255.255.255
LocalDirector(config)#
Set the IP address of the TFTP server for storing secondary configuration information and software image files. (Configuration mode.)
[no] tftp-server tftp_server_ip tftp_directory
tftp_server_ip | IP address of the TFTP server. |
tftp_directory | The directory in which the secondary configuration and software image files are stored. The default directory is /tftp/boot. |
The tftp-server command defines the IP address of a TFTP server. When a TFTP server is defined, 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:
LocalDirector(config)# tftp-server 192.168.10.1
LocalDirector(config)#
Configure the number of consecutive TCP connection reassignments that a real server can exhibit before LocalDirector marks the real server as failed. (Configuration mode.)
threshold real_id connect_failures
real_id | Real server IP address or name and port (if a port-bound server). |
connect_failures | The number of consecutive connection reassignments to tolerate; the default is 8. Zero is the same as one and the maximum number of reassigns is limited to 256. |
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 the LocalDirector. Connection reassignments may be due to a TCP RST, or no answer from the real server.
Failed real servers are not utilized by virtual servers while in the failed state; however, LocalDirector retests each failed server periodically with a single TCP connection attempt to see if the server has returned to normal behavior. If so, LocalDirector marks the server as in service which makes it available to handle virtual server requests.
LocalDirector(config)# show threshold
Machine Port Threshold
192.168.1.1 default 8
192.168.1.1 80 8
192.168.1.2 default 8
LocalDirector(config)# threshold 192.168.1.1 80 10
LocalDirector(config)# threshold 192.168.1.2 5
LocalDirector(config)# show threshold
Machine Port Threshold
192.168.1.1 default 8
192.168.1.1 80 10
192.168.1.2 default 5
LocalDirector(config)#
Set connection timeout for real machine. (Configuration mode.)
timeout real_id idle_minutes
real_id | Real server IP address or name and port (if a port-bound server). |
idle_minutes | The number of minutes the server maintains a connection before dropping it. The default is 120 minutes, and the minimum is |
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 the 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).
LocalDirector(config)# show timeout
Machine Port Timeout
192.168.1.1 80 120
192.168.1.1 default 120
192.168.1.2 default 120
LocalDirector(config)# timeout 192.168.1.1 80 360
LocalDirector(config)# timeout 192.168.1.2 200
LocalDirector(config)# show timeout
Machine Port Timeout
192.168.1.1 80 360
192.168.1.1 default 120
192.168.1.2 default 200
LocalDirector(config)#
Create a virtual server to accept a connection from the network. (Configuration mode.)
[no] virtual virtual_ip|virtual_name [:[virtual_port]:[bind-id]] [service-state]
virtual_ip | The IP address of the virtual server being defined. |
virtual_name | The name of the virtual server being defined. |
virtual_port | The port traffic that runs on the server. Use a colon as a delimiter between the IP address and port number. If you do not identify a specific port, all traffic will be allowed to the server and the port will be labeled 0. Servers with a port specified are referred to as "port-bound" servers. |
bind-id | Used with the assign command to direct traffic to to a specific location. Use a colon as a delimiter between the bind-id and port number. If you do not specify a bind-id when defining a virtual server, the default is :0. Any client IP address not identified by an assign command statement will be directed to the default bind-id of 0. |
service-state | In service (is) or out of service (oos). The default is oos. |
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.
In cases where the published or "advertised" addresses are different from internal addresses, the IP address of the LocalDirector must be on the network from which you want to access the 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 the LocalDirector should be either 204.31.17.x (if accessing the LocalDirector from outside) or 192.168.89.x (if accessing the LocalDirector from inside). Here "accessing" means using Telnet, SNMP, or SYSLOG to connect to the LocalDirector. Virtual server addresses can only be accessed from the client side of LocalDirector.
Specify the IP address of the LocalDirector with the ip address command before defining virtual servers. If no real servers are bound to the virtual server, the no virtual command can be used to remove the virtual server from LocalDirector.
The show virtual command indicates the service state of virtual servers. Possible service states are:
The show virtual command provides the following information:
| Column heading | Description |
|---|---|
Machine | IP address and port (if a port-bound server) or name of the server. |
State | IS (in-service), OOS (out-of-service), or Max. Max means the server has reached maximum connetions set with the maxconns command. |
Connect | number of connections to the server. |
Sticky | elapsed time of inactivity before connection is sent to another server. |
Predictor | type of load balancing. An asterisk (*) indicates that this predictor is active. |
Slowstart | slowstart option set with predictor command (roundrobin or none). An asterisk (*) indicates that this predictor is active. |
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
ld(config) 6# virtual 10.10.10.1:443:1
ld(config) 7# virtual 10.10.10.1
ld(config) 8# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
10.10.10.1:80:0 OOS 0 0 leastconns roundrobin*
10.10.10.1:443:1 OOS 0 0 leastconns roundrobin*
10.10.10.1:0:0 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 lucky
ld(config) 0# is virtual lucky:80
ld(config) 1# sticky lucky:443:1 10
ld(config) 2# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
lucky:80:0 IS 0 0 leastconns roundrobin*
lucky:443:1 OOS 0 10 leastconns roundrobin*
lucky:0:0 OOS 0 0 leastconns roundrobin*
In order to remove a virtual server you have to first remove any bind association to real servers. For example:
LocalDirector(config) 5# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
192.168.0.98:0:0 OOS 0 0 leastconns roundrobin*
192.168.0.99:0:0 IS 0 0 leastconns roundrobin*
LocalDirector(config) 6# show bind
Virtual Real
192.168.0.98:0:0(OOS)
192.168.0.3:0(OOS)
192.168.0.99:0:0(IS)
192.168.0.1:0(IS)
192.168.0.2:0(IS)
LocalDirector(config) 7# no virtual 192.168.0.98:0:0
Must unbind all reals before removing virtual. LocalDirector(config) 8# no bind 192.168.0.98:0:0 192.168.0.3:0
LocalDirector(config) 9# no virtual 192.168.0.98:0:0
LocalDirector(config) 0# show virtual
Virtual Machines:
Machine State Connect Sticky Predictor Slowstart
192.168.0.99:0:0 IS 0 0 leastconns roundrobin*
LocalDirector(config) 1#
Assign a relative value to the distribution of connections for real servers. (Configuration mode.)
[no] weight real_id number
real_id | The IP address or name, and port (if a port-bound server) of a real server. |
number | The number that will be averaged to determine the distribution of current connections among real servers. The default is one, and the value can be a whole number from 0 to 65535. A value of 0 is equivalent to placing the server out of service. |
Assign a larger number to servers with higher performance. In the example below, the weights of all of the servers equals eight. Therefore, server 192.168.1.1 would receive 4/8 of the connections, or 50%. Server 192.168.1.2 would receive 25% of the connections, and servers 192.168.1.3 and 192.168.1.4 would each receive 12.5% of the connections. Faster servers will still receive more connections because they will service the connection faster, regardless of the percentage of connections that they are assigned at the time.
LocalDirector(config)# show weight
Machine Port Weight
192.168.1.1 default 1
192.168.1.2 default 1
192.168.1.3 default 1
192.168.1.4 default 1
LocalDirector(config)# weight 192.168.1.1 4
LocalDirector(config)# weight 192.168.1.2 2
LocalDirector(config)# show weight
Machine Port Weight
192.168.1.1 default 4
192.168.1.2 default 2
192.168.1.3 default 1
192.168.1.4 default 1
LocalDirector(config)#
Show active Telnet administration sessions. (Unprivileged mode.)
who [ip]
[ip] | An optional IP address to limit the listing to one IP address or to a network IP address. |
The who command shows the tty_id and IP address of each Telnet client currently logged in to the LocalDirector. This command is the same as the show who command.
LocalDirector# who
2: From 192.168.2.2 1: From 192.168.1.3 0: On console LocalDirector#
Store the current configuration. (Privileged and Configuration modes.)
write erase|floppy|memory|terminal|standby
erase | The write erase command clears the Flash memory configuration. |
floppy | The write floppy command stores the current running configuration on floppy disk. |
memory | The write memory command saves the current running configuration to Flash memory. When using failover, this will force the configuration to be written to Flash memory on the standby unit also. |
standby | This will copy the active configuration to the standby unit. |
terminal | The write terminal command displays the current running configuration on the console computer. Before using this command, you can set your terminal communications program to store the screen display in a log file. |
net | Save configuration to a remote TFTP server. To use this option, issue the tftp-server command first, or identify the name of the file and the IP address of the TFTP server. The file must be created on the TFTP server before it can be saved to the TFTP server. |
file | The name of the file on the TFTP server. |
tftp server ip | The IP address of the TFTP server.
|
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 to this is the show configuration command which displays the configuration stored in Flash memory, and therefore will not include default values either.
LocalDirector(config)# write floppy
Building configuration... [OK]
LocalDirector(config)#
|
|