LocalDirector User Interface

System Requirements

Install the LocalDirector User Interface on a PC with the following minimum system requirements:

• 80486 processor or higher

• RAM

  • Windows NT - 40 MB recommended

  • Windows 95 - 32 MB recommended

• Hard disk space - 2 MB for program files

• Operating system - Windows NT 4.0 or Windows 95 OEM Service Release 2 (OSR2)

---

Note To check the version of Windows 95 on your PC, open a command prompt window (DOS window), then enter the ver command. If the version displayed is 4.00.1111, then the system is running W95 OSR2.

---

Installation and Use

This section describes the following:

• Connecting the LocalDirector Hardware to the PC

• Installing and Starting the LocalDirector User Interface

• Initial Configuration

• Server Farm Configuration

• Configuring Telnet

Connecting the LocalDirector Hardware to the PC

Step 1 Connect the power cord to LocalDirector and plug it in.

Step 2 Connect one end of the null modem serial cable to the LocalDirector DB-9 console port, and connect the other end to an available COM port on your PC.

---

Note Initial configuration must be done through the COM port.

In a failover configuration, do not connect to the standby unit. Always use the LocalDirector User Interface with the active LocalDirector.

---

Step 3 Connect one end of the network cable from the hub or switch containing the physical servers to one of the network interface connections on the back of the LocalDirector, and connect the other end of the cable to the network interface that connects to the outside network.

Step 4 Turn on the LocalDirector power switch.

Installing and Starting the LocalDirector User Interface

The LocalDirector User Interface is shipped on a 3.5" diskette, or it can be downloaded from CCO as a self-extracting file. Install the user interface program as follows:

Installing from the LocalDirector Program Diskette

Step 1 Insert the program diskette into the diskette drive on the PC.

Step 2 Run the lui211.exe program.

Step 3 From the Start menu, click Programs, and then Cisco LocalDirector User Interface. Double-click the LocalDirector User Interface icon, and the main window appears.

Download from CCO

Step 1 Copy the self-extracting executable file onto the hard drive of the PC.

Step 2 Double-click the file to expand the user interface files.

Step 3 Double-click the LocalDirector user interface icon, and the LocalDirector User Interface main window appears.

---

Note The LocalDirector User Interface installer performs an operating system version check in the beginning of setup. The LocalDirector User Interface and LocalDirector software must be at the same version level.

---

The LocalDirector User Interface provides a graphical editor for managing LocalDirector configurations. The main window is divided into three areas as shown in Figure 7-1.

Figure 7-1: LocalDirector User Interface Main Window

• Tree View - used to add, delete, and bind virtual and real servers.

• List View - used to set, copy, and paste properties of virtual and real servers.

• Map View - provides a graphical representation of the real servers bound to a specific virtual server.

Initial Configuration

Step 1 Make sure that you are connected to the LocalDirector via the COM port. See "Connecting the LocalDirector Hardware to the PC."

---

Note Initial configuration must be done through the COM port.

---

Step 2 From the LocalDirector User Interface main menu, select LocalDirector, then Load Primary Configuration. The Select Current LocalDirector screen appears.

Step 3 Click Add to define the connection configuration. A password is not required until you define one using the Passwords tab option (see Figure 7-2). Click OK to define the new connection, and OK again to load the configuration. The Primary Configuration property sheets appear, as shown in Figure 7-2:

Figure 7-2: Primary Configuration Property Sheets

Step 4 Define the LocalDirector IP address and subnet mask. Use the tabs on the Primary Configuration property sheets to configure LocalDirector ARP, Failover, Interfaces, Passwords, Routes, SNMP, SYSLOG, and Telnet settings.

Server Farm Configuration

From the Servers menu, define real and virtual servers and their bind associations. An existing server configuration can be imported by selecting Load Server Farm Configuration from the LocalDirector menu.

Configuring Telnet

In order to configure Telnet access to the LocalDirector, complete the following steps:

Step 1 From the LocalDirector main menu, select LocalDirector and Load Primary Configuration to connect to the LocalDirector via the COM port.

Step 2 From the Primary Configuration property sheets, click the Passwords and Telnet tabs in order to define authorized Telnet hosts and set the Telnet password.

---

Note If you want to access the LocalDirector via a network connection, the IP address of the PC that is running the LocalDirector User Interface program must be added to the list of authorized Telnet hosts.

---

When Telnet access is configured, you can define the current LocalDirector as a network connection, as shown in Figure 7-3.

Figure 7-3: Network Connection Configuration

Supported Commands

The following commands are supported by the LocalDirector User Interface:

• Real server commands

autounfail	name	retry
data	out-of-service	threshold
in-service	real	timeout
maxconns	reassign	weight

• Virtual server commands

assign	in-service	sticky
bind	out-of-service	synguard
delay	predictor	virtual
name	replicate

• System commands

arp	ip address	route
enable password	mtu	secure
failover	password	snmp-server
failover IP address	ping-allow	syslog
interface	rip	telnet

Unsupported Commands

The following commands are not supported by the LocalDirector User Interface:

backup	kill	static
channel	pager	tftp
configure	ping	who
failover active	reload	write
hostname	restart

Troubleshooting Connection Problems

The following information is provided for troubleshooting the LocalDirector User Interface connection:

• If you receive one of the following error messages, "Unable to connect to LocalDirector at <IP>" or "login failed," verify that:

  • You can Telnet to this LocalDirector and can enter into configuration mode from the workstation that you are using.

  • You can ping the LocalDirector IP from the workstation that you are using.

  • There is a LocalDirector configured with the IP address that you are trying to use.

  • There is a Telnet entry for the workstation that you are using in the current LocalDirector's configuration.

  • You have used the valid LocalDirector passwords for Telnet and privileged mode access.

• If you receive one of the following error messages, "Unable to connect to LocalDirector via COM <#>" or "login failed," verify that:

  • This COM port is not being used by another application such as HyperTerminal.

  • You have used the valid LocalDirector password for privileged mode access.

  • You can open a LocalDirector console session (HyperTerminal) from the workstation that you are using on this COM port.

  • Check that the workstation that you are using is physically connected to the LocalDirector via a null modem serial cable.

  • Verify that the COM port is properly set up for 9600 baud rate, no parity, 8 data bits, 1 stop bit, and no flow control as follows:
    
    In the Windows 95 Control Panel, click the System icon and then the Ports (COM & LPT) icon. Expand the tree to view a list of COM ports. Select the port that is connected to the LocalDirector and click the Properties button and then the Port Settings tab.
    
    In the Windows NT Control Panel click the Ports icon to view a list of COM ports that are already set up. Select the one that is connected to the LocalDirector and click the Settings button.

LocalDirector User Interface Online Help

The LocalDirector User Interface includes online help that can be accessed by clicking the Help buttons on the screen. In addition, press the F1 key when a menu item is highlighted to display popup help for that menu item.

Notes

• After setup, the LocalDirector User Interface includes the following files:

File name	Contents
sample.lui	sample server farm configuration file
lui.hlp	help file
lui.cnt	help file
lui.gid	help file
Uninst.isu	file needed for the uninstallation process
readme.rtf	release notes
lui.log	log file
lui_read.txt	log file
lui_writ.txt	log file

• The LocalDirector User Interface generates a file called lui.dat that contains a list of user-defined LocalDirector profiles. This information is needed for initiating connection to a LocalDirector unit. The file is not removed when uninstalling the LocalDirector User Interface; therefore, if the LocalDirector User Interface is upgraded, existing profiles do not have to be re-defined.

• If the LocalDirector User Interface is installed on two PCs, and either PC will be used to connect to the same set of LocalDirector units, LocalDirector profiles can be defined on one PC and then copied to the other PC. First exit the LocalDirector User Interface program, and then copy the lui.dat file from one PC to the other. To connect to a LocalDirector over the network from the other PC, make sure that a Telnet entry is defined for that PC in the LocalDirector configuration.

• The lui.dat file must reside in the same directory as lui.exe.