LocalDirector User Interface Basic Configuration

Check the status of the LocalDirector User Interface server service. If the component was configured to start automatically, then information in the Services Control Panel reflects that it is already running.

Step 4 If the server is not running, then as the administrator select the service and click Start. After a moment, the operating system indicates whether the service started successfully.

Once the LocalDirector User Interface server service is started, it waits for connection requests from the LocalDirector User Interface clients.

Note If you start the LocalDirector User Interface server as a system service, it initially starts without a password.

To specify a LocalDirector User Interface server password, select the File menu Server Properties option from the main LocalDirector User Interface window. At the General tab, click the Change Password button. You are prompted to enter the new password and also to confirm that password.

Note To enable the LocalDirector User Interface to be accessed through the localhost interface, stop the LocalDirector User Interface service and start the LocalDirector User Interface server at a command prompt as follows:

gwserver -h localhost

Running the LocalDirector User Interface Server on UNIX Systems

After the LocalDirector User Interface server is installed, it runs as a UNIX process. In UNIX, you start the LocalDirector User Interface server at the command line, although you c an also enter it into a startup file such as /etc/rc.local.

The UNIX LocalDirector User Interface server command line invocation is:

gwserver [-v] [-h host address] [-p port] [-w] [-t tftp_server[:tftp_port]]

The -v flag displays the version number of the LocalDirector User Interface server.
The host address argument is the LocalDirector User Interface server host name or an IP address. The IP address can be the secondary address of an interface in your host; it need not be the primary host IP address. By default, the LocalDirector User Interface server host is the name for the host system.
The port argument is a port number. By default, the LocalDirector User Interface server port is 4800.
The -w flag causes the server to prompt for a password for logging in to the LocalDirector User Interface server. By default, the LocalDirector User Interface server takes no password.
The tftp_server and tftp_port arguments allow you to override the default IP address or port number where the Trivial File Transfer Protocol (TFTP) server for the LocalDirector User Interface server listens. The tftp_server can be a dot-notation IP address or a host name. By default, the LocalDirector User Interface server listens on the default interface for the host on port 69 (the default port for TFTP). (However, the TFTP server does not actually listen on this port unless you enable the TFTP server with the File menu Server Properties option from the main LocalDirector User Interface window.) Because the default is a "low port" (port numbers less than or equal to 1024), the LocalDirector User Interface server needs to run as root on a UNIX system to acquire that port. You can direct the LocalDirector User Interface server to use a "high port" (port numbers greater than 1024).

Caution On UNIX systems, there may already be a TFTP server running on port 69. Use the -t option to change the TFTP server port number to one other than 69.

Starting the LocalDirector User Interface Server on UNIX Systems

On UNIX systems, start the LocalDirector User Interface server at the command line. Enter the following command on the host system of the LocalDirector User Interface server to start the LocalDirector User Interface server:

gwserver

To enable the LocalDirector User Interface to be accessed through the localhost interface, start the LocalDirector User Interface server as follows:

gwserver -h localhost

This command starts a LocalDirector User Interface server process on the local host system. The LocalDirector User Interface server listens for clients at port 4800 and has no password configured. To prompt for a password to be specified, you can enter the following command:

gwserver -w

The LocalDirector User Interface server then prompts you for the login password and confirmation:

Please enter the new server password:
Please confirm the new server password:

The LocalDirector User Interface stores the password on disk. Subsequent invocations of the gwserver command do not require the -w flag.

Note On UNIX systems, if you want to start the LocalDirector User Interface server automatically when the system boots, add the gwserver command to the start up scripts of your system. These scripts are usually found in the /etc directory, in directories or scripts whose names begin with rc. Consult your UNIX system administration documentation for more details.

Accessing the LocalDirector User Interface Server

User interaction with the LocalDirector User Interface server is controlled through the LocalDirector User Interface client. Before you start, you should have available the IP address of the LocalDirector User Interface server host and the port where the LocalDirector User Interface server is listening (by default, 4800).

Follow this procedure to access the LocalDirector User Interface server using a standard browser:

Step 1 On the LocalDirector User Interface client, start the browser and at the URL line, enter the address:

http://host_name_or_IP_address:port/LUI31.html

http://host_name_or_IP_address:port

http://host_name_or_IP_address:port/

or, if you start the LocalDirector User Interface server for localhost access:

http://localhost:port

Alternatively, on the LocalDirector User Interface server, if your server is a Windows server, click the Start button, go to Programs, then go to LocalDirector 3.1, and select LocalDirector User Interface 3.1.

Step 2 At the login window (illustrated in Figure 3-1), enter the password, if any, that you specified when starting the LocalDirector User Interface server.

Figure 3-1: LocalDirector User Interface Login Window

Step 3 Click the Login button. The LocalDirector User Interface server checks whether any LocalDirector configurations exist from a previous version of the LocalDirector User Interface server. If a LocalDirector configuration is detected, the main LocalDirector User Interface window displays (see Figure 3-2).

Note

Using the LocalDirector User Interface to Connect to LocalDirector

Figure 3-2: Main LocalDirector User Interface Window

Now that you have successfully logged in to the LocalDirector User Interface, you can perform one of the following tasks:

Connect to either a new or existing LocalDirector---go to the next section "Using the LocalDirector User Interface to Connect to LocalDirector."
Configure an existing LocalDirector---go to the section "Basic LocalDirector Configuration" later in this chapter.
Start configuring server farms right away---go to the chapter "LocalDirector User Interface Basic Configuration." This step is possible if you are already connected to a LocalDirector or if you press Cancel at the connection dialog.

Using the LocalDirector User Interface to Connect to LocalDirector

You can connect to LocalDirector by using either a serial cable (see "Setting Up a Connection") or with a Telnet connection (see "Using a Telnet Connection to LocalDirector").

Setting Up a Connection

Follow this procedure to establish a connection with a new LocalDirector in your network or to access an existing LocalDirector connection. (Establishing a connection with LocalDirector opens a new configuration for that LocalDirector.) While establishing a serial connection, you can also establish a Telnet connection. Once you establish a Telnet connection to LocalDirector, you can reuse the Telnet configuration to connect to that LocalDirector. See "Using a Telnet Connection to LocalDirector" later in this chapter for more information.

Step 1 If you want to add a new LocalDirector or access an existing LocalDirector not currently known to the LocalDirector User Interface, select Add LocalDirector from the toolbar to bring up the Connection Wizard. The wizard guides you through the steps to establish a connection to a new LocalDirector.

Note If no LocalDirector is associated with the LocalDirector User Interface server, the Connection Wizard starts automatically upon login.

Figure 3-3

Connection Wizard dialog. You can click Cancel to begin configuring server farms right away without connecting to a LocalDirector. Clicking Cancel opens the default configuration so that you can begin configuring server farms. This configuration is not associated with a LocalDirector until you add a LocalDirector and attach it to the configuration.

Figure 3-3: Serial Connection through the Connection Wizard

Step 2 Enter or select the required information in the top two areas (the information requested in the third area changes based on your answers):

(a) Type a name to be associated with the LocalDirector in the Name text field.

Note

(b) Select Serial from the Type drop-down menu to indicate the connection with LocalDirector is through a serial cable.

Select Auto Detect to allow the LocalDirector User Interface to choose a serial port on the LocalDirector User Interface server host for connecting to LocalDirector.
Select Port if you choose to provide a port. Select a port from the list.

Click Next when you have finished.

Note

If the LocalDirector User Interface server detects LocalDirector on the specified port, the following window displays (see Figure 3-4).

Figure 3-4: Specifying the Connection through the Connection Wizard

Step 3 Enter the password and the appropriate connection information in the above window:

(a) Enter the LocalDirector administrator password (or leave it blank if there is no password).

Note You can later change this password at the LocalDirector User Interface main window by right-clicking on the LocalDirector entry and selecting Connection Properties. The resulting popup window allows you to change the LocalDirector administrator password.

(b) Leave checked or uncheck the use Auto Configuration box. Enabling autoconfiguration loads the current LocalDirector configuration into the LocalDirector User Interface and creates a configuration for the LocalDirector with the same name as the LocalDirector. Disabling autoconfiguration requires you to open a configuration later with the File menu Open option.

If you add a LocalDirector that has the same name as an existing configuration, the LocalDirector User Interface automatically appends the string "(1)" to the end of the new LocalDirector configuration name.

Note With Auto Configuration enabled, the LocalDirector User Interface places all servers loaded from LocalDirector into either the Any or Unbound server groups (if the server is specified as unbound in the LocalDirector). If a server needs to be in the Web group, you need to move it manually (see the chapter "

Configuring Server Farms

(c) Click the checkbox to indicate if you would also like to configure a Telnet connection for this LocalDirector system. The bottom of the window changes to provide a Next button so you can continue.

Step 4 If you do not want to set up a Telnet connection, click Finish and return to the main window. The new LocalDirector entry displays in the LocalDirector area. You can now start adding server farms to this LocalDirector entry as described in the chapter "Configuring Server Farms."

If you want to set up a Telnet connection, click Next and the window in Figure 3-5 displays.

Figure 3-5: Setting Up a Telnet Connection

Step 5 Supply the following information in the top area, as requested:

(a) In the Host text field, type the IP address of the LocalDirector.

(b) In the Password text field, enter a new LocalDirector Telnet password.

Note You can later change the LocalDirector administration or Telnet password at the LocalDirector User Interface main window by right-clicking the LocalDirector entry and selecting Connection Properties. The resulting popup window allows you to change and confirm the LocalDirector password (limited to 15 characters). At this window, you can also choose to apply the new password to both the LocalDirector User Interface and LocalDirector, or just to the LocalDirector User Interface (for example, to match the LocalDirector password).

(c) In the Active Connection area, specify whether you would like the default connection to be serial or Telnet. (Note that the default value here is Telnet.)

(d) Click Finish to return to the main LocalDirector User Interface window. The new LocalDirector entry displays in the LocalDirector area. You can now begin adding server farms as described in the chapter "Configuring Server Farms" later in this guide.

Using a Telnet Connection to LocalDirector

Once a Telnet connection has been set up, follow this procedure to connect to LocalDirector using the LocalDirector User Interface:

Step 1 Select Add LocalDirector from the toolbar to bring up the Connection Wizard.

Step 2 Provide the required information in the top two areas (the information requested in the third area changes based on your answers). (See Figure 3-6.)

(a) Type a name to be associated with LocalDirector in the Name field.

(b) Select Telnet from the Type drop-down menu to indicate the connection with LocalDirector is through a Telnet session.

Figure 3-6: Starting a Telnet Connection

Step 3 In the Connection Parameters area, provide the following information:

(a) Enter the IP address of the LocalDirector in the Host text field.

(b) Enter a predefined password, specified when the LocalDirector was first configured for Telnet connections.

Step 4 Enter your LocalDirector administration password, or leave it blank if there is no password (see Figure 3-7).

Note

selecting Connection Properties.

Figure 3-7: Completing the Telnet Connection

Step 5 Leave checked or uncheck the Use Auto Configuration box. Enabling autoconfiguration loads the current LocalDirector configuration into the LocalDirector User Interface and creates a configuration for the LocalDirector with the same name as the LocalDirector. Disabling autoconfiguration requires you to open a configuration later with the File menu Open option.

If you add a LocalDirector that has the same name as an existing configuration, the LocalDirector User Interface automatically appends the string "(1)" to the end of the LocalDirector configuration name.

Note With Auto Configuration enabled, the LocalDirector User Interface places all servers loaded from the LocalDirector into either the Any or Unbound server groups (if the server is specified as unbound in the LocalDirector). If a server needs to be in the Web group, you need to move it manually (see the chapter "

Configuring Server Farms

Caution If you are adding a LocalDirector that is configured for failover standby mode, disable the Auto Configuration option (uncheck the box). Using the Auto Configuration option may corrupt the failover configuration on the standby LocalDirector.

Step 6 Click Finish (see Figure 3-7). An entry for the new LocalDirector configuration displays in the LocalDirector View on the left side of the main LocalDirector User Interface window.

From here, you can configure LocalDirector server farms. See the chapter "Configuring Server Farms." If you want to change the default configuration settings for the LocalDirector User Interface or LocalDirector, continue with the following sections.

Basic LocalDirector Configuration

Using the LocalDirector User Interface, you can set up the basic LocalDirector configuration information. Basic LocalDirector configuration involves defining the parameters required to bring up the LocalDirector and add it to the network. In particular, some of the decisions you might want to make before performing the basic LocalDirector configuration include:

Do you want to configure failover? If so, enable the failover capability, define a backup LocalDirector system, and also set up the Telnet or serial interface for failover. When you configure two LocalDirectors for failover, attach the LocalDirector User Interface to only the active LocalDirector. The standby LocalDirector should not be accessed for modifying secondary configurations.
Do you want to be able to use a Telnet connection to connect to LocalDirector (for example, if you want to be able to access LocalDirector remotely or to enable failover with Telnet access)? If so, set up the Telnet connection to authorize other hosts to configure the LocalDirector.

Note

Do you want to set up a LocalDirector administrator password to connect to the LocalDirector? If so, right-click on the LocalDirector and select Connection Properties. A Connection Properties window displays where you can change the LocalDirector administrator password.

During basic LocalDirector configuration, you will use the tabs in the LocalDirector Properties window (see Figure 3-8) to set up basic properties. These properties are fully described in the Cisco LocalDirector Installation and Configuration Guide.

The tabs in the LocalDirector Properties window are:

ARP
Failover
Interfaces
System
Routes
SNMP
SYSLOG
TFTP
Telnet (This tab limits you to 16 LocalDirector host entries.)
Additional (This tab allows you to enter LocalDirector configuration commands that are not provided in the other tabs. Figure 3-8 shows this tab.)

Note The Additional tab may only contain commands that a LocalDirector configuration file can legally store. Refer to the Cisco LocalDirector Installation and Configuration Guide for these commands.

Figure 3-8: LocalDirector Properties Window Additional Tab

Note You may want to input additional LocalDirector commands at LocalDirector using its command-line interface rather than through the LocalDirector User Interface. The LocalDirector User Interface does not check for syntax errors, but LocalDirector does.

The LocalDirector User Interface does not support the following LocalDirector commands (although you can enter them through the Additional tab of the LocalDirector Properties window):

arp (without the alias keyword)
blocks
boot image
bridge
casa
channel
clear
color
configure net
default
dynamic-feedback
failover (active or reset)
kill
name (the LocalDirector User Interface accepts a name value but does not allow you to modify this value)
pager
ping
reload
static
who

Performing Basic LocalDirector Configuration

Follow this procedure to define the basic configuration of a new LocalDirector:

Step 1 Right-click on the desired LocalDirector entry in the LocalDirector view area.

A drop-down menu displays (see Figure 3-9).

Figure 3-9: LocalDirector Configuration Drop-Down Menu

Step 2 Select Properties to display the basic LocalDirector configurable properties (see Figure 3-10).

Figure 3-10: LocalDirector Properties Window

Step 3 Select the tab representing the configuration property you want to edit.

The window for changing the relevant information displays. The configuration of many of these properties is self-evident, with the exception of the TFTP tab, which is described in the following section, "Accessing and Booting from TFTP Servers."

Step 4 When you are finished editing properties, click OK.

Accessing and Booting from TFTP Servers

Follow this procedure to set up a LocalDirector to communicate with a TFTP server. You need to set up a LocalDirector with TFTP information if you want to boot the LocalDirector from a TFTP server (refer to the Cisco LocalDirector Installation and Configuration Guide).

Step 1 At the LocalDirector Properties window, select the TFTP tab (see Figure 3-11). The TFTP server capability is enabled by default.

Figure 3-11: Selecting the TFTP Tab

Click the LUI is the TFTP Server box to identify the LocalDirector User Interface as the TFTP server. This action grays out the rest of the information in the TFTP Server area and the LocalDirector obtains the relevant TFTP server information from the LocalDirector User Interface.

: To configure a LocalDirector using a configuration from a TFTP server, see the section, "Configuring LocalDirector Using Configuration Files from TFTP Servers" later in this chapter for information.

Step 2 Continue to the Boot Configuration area to configure LocalDirector to boot from a configuration obtained from the TFTP server you have just enabled. If you do not want to configure LocalDirector to boot from the TFTP server configuration, click OK.

Step 3 In the Boot Configuration area, click the Enable Boot from Configuration box. This action allows you to boot from a TFTP server configuration, as illustrated in Figure 3-12.

Figure 3-12: Enabling Boot Configuration

Click the Boot from the attached Configuration box to configure LocalDirector to boot from the LocalDirector User Interface configuration attached to this LocalDirector. This action grays out the rest of the information in the Boot Configuration area.
If you want LocalDirector to boot from a configuration obtained from a TFTP server other than the LocalDirector User Interface, enter the IP address for that server, the port number of the TFTP server, and the name of the configuration file.

Step 4 Click OK.

Configuring LocalDirector Using Configuration Files from TFTP Servers

You can configure a LocalDirector, acting as a TFTP client, using configurations obtained from the LocalDirector User Interface configured as a TFTP server. Use the configure net command in one of the following ways:

configure net /Config/LocalDirector name
configure net /Config/Configuration name

The directions in this section assume that you have enabled the LocalDirector User Interface as a TFTP server and that you have configured LocalDirector to use the LocalDirector User Interface as a TFTP server (refer to the Cisco LocalDirector Installation and Configuration Guide).

Saving Full and Primary Configurations

To access the LocalDirector configuration currently contained in the LocalDirector User Interface via the TFTP server, connect to the LocalDirector and type the following command at the LocalDirector prompt:

configure net /Config/LocalDirector name

If LocalDirector is attached to a configuration, this command generates a full configuration with primary and server farm configurations. If the LocalDirector has no configuration attached to it, entering the configure net command as specified in the previous example causes the LocalDirector User Interface to send only the primary configuration to LocalDirector.

Saving Secondary Configurations

If LocalDirector does not have a configuration attached to it, entering the configure net command with a configuration name:

configure net /Config/Configuration name

saves the LocalDirector User Interface Configuration name to the LocalDirector as a secondary configuration. If the LocalDirector and the configuration have the same name, the result of this command is the same as if you had entered the configure net /Config/LocalDirector name command, described in the section "Saving Full and Primary Configurations" earlier in this chapter.

Caution If LocalDirector is attached to LocalDirector User Interface and you enter the configure net command to load a different configuration, the LocalDirector User Interface may not be aware of this change and assume that the old configuration is still in place. Be careful when entering the configure net command while LocalDirector is attached.

Accessing LocalDirector Configurations through TFTP Servers

To save a LocalDirector configuration to a LocalDirector User Interface configured as a TFTP server, connect to the LocalDirector and enter the following command at the LocalDirector prompt:

write net /configuration name

This command assumes a LocalDirector TFTP directory of "/" (set with the LocalDirector tftp-server command), and writes a copy of the configuration attached to LocalDirector to LocalDirector User Interface base directory/tftpfiles/configuration name for UNIX systems (LocalDirector User Interface base directory\tftpfiles\configuration name for Windows systems).

Alternatively, to save the configuration file attached to LocalDirector to a directory under the LocalDirector User Interface tftpfiles directory, follow this procedure:

Step 1 Create in the LocalDirector User Interface base directory, as necessary, the tftpfiles directory and directory name under it.

Step 2 Connect to the LocalDirector.

Step 3 At the LocalDirector prompt, enter a command like the following:

write net directory name/configuration name

The resulting configuration file appears in directory name (for example, LocalDirector User Interface base directory\tftpfiles\directory name\configuration name).

As a TFTP server, LocalDirector User Interface starts a search for the TFTP configuration information to send to its TFTP client based on the TFTP configuration filename:

If the TFTP configuration file pathname starts with /path/configuration name, where path is not "Config," the LocalDirector User Interface TFTP server looks for the configuration file in LocalDirector User Interface base directory/tftpfiles/path.
If the TFTP configuration file pathname starts with /Config/Configuration name, the LocalDirector User Interface TFTP server looks for Configuration name in LocalDirector User Interface base directory/tftpfiles/Config.

: If the LocalDirector User Interface TFTP server does not find a matching configuration file name, it compares Configuration name with the LocalDirector name. If there is a match, and LocalDirector is attached to a configuration, the LocalDirector User Interface TFTP server sends both the primary and secondary configuration to a TFTP client. If there is a match, but LocalDirector is not attached to a configuration, the LocalDirector User Interface, as the TFTP server, sends only the primary configuration to the TFTP client.
: If the LocalDirector User Interface TFTP server cannot match Configuration name with a LocalDirector, it next looks for the Configuration name in LocalDirector User Interface base directory/Config. If there is a match, the LocalDirector User Interface TFTP server sends the secondary configuration to the TFTP client.

Changing the LocalDirector User Interface Server Properties

You can change any of the LocalDirector User Interface general server properties, such as TFTP server properties and SNMP settings. To set up the LocalDirector User Interface for SNMP communications, refer to the chapter "Working with Messages" later in this guide.

Note To incorporate any changes made to server properties, restart the LocalDirector User Interface server after you make server property changes.

Follow this procedure to change the LocalDirector User Interface general server properties:

Step 1 Select the File menu Server Properties option from the main LocalDirector User Interface window. The Server Properties window displays (see Figure 3-13).

Figure 3-13: LocalDirector User Interface General Server Properties

Step 2 At the General tab, change the default values of following fields, as desired:

Server Host Address---The default value is the address of the host where you installed the LocalDirector User Interface server.
Server Port---The default value is 4800.
Storage Directory---By default, the LocalDirector User Interface server stores data in the root directory where the LocalDirector User Interface server is installed. For Windows systems, you cannot change this value. For UNIX systems, you can change this value with the -s flag of the gwserver command.
Enable TFTP Server---The TFTP server is disabled by default. Select this box to enable the TFTP server.
TFTP Server Address---The default value is the address of the host where you installed the LocalDirector User Interface server.
TFTP Server Port---The default value is 69. Because the default is a "low port," the LocalDirector User Interface server needs to run as root on a UNIX system to use that port. You can change the port number to a "high port" for this reason.

Note

Server Password---Clicking the Change Password button displays the Change Server Password window (see Figure 3-14). Enter the old and new passwords, confirm the new password, and click OK.

Figure 3-14: Changing the LocalDirector User Interface Server Password

Step 3 Click OK on the Server Properties window to save server property changes.

Navigating the Main LocalDirector User Interface Window

The LocalDirector User Interface main window consists of a menu bar, toolbar, and five display areas (see Figure 3-15).

The menu bar contains four menu options: File, Edit, Add, and Help.

Beneath the menu bar is a toolbar with icons that are shortcuts for some of the menu options. Many of these shortcuts, such as Add Probe, Add Virtual Server, Add Real Server, and Add LocalDirector, are available in the Add menu. Others, such as Cut or Copy, are available in the Edit menu.

Note Some commands that are available in the Edit and Add menus are also available for affected objects (such as virtual servers and real servers) if you right-click the selected objected.

Figure 3-15: Main LocalDirector User Interface Window Toolbar

File Menu

From the File menu you can:

Create a new LocalDirector User Interface configuration.
Open a LocalDirector User Interface configuration.
Save a copy of the currently open LocalDirector User Interface configuration to the LocalDirector User Interface server host disk. The LocalDirector continues to be attached to the configuration.
Save a copy of the currently open LocalDirector User Interface to a configuration name for which you are prompted. If that open configuration is attached to a LocalDirector, it continues to be attached to the LocalDirector, but the saved configuration is not attached to a LocalDirector until you explicitly attach it. The saved configuration becomes the currently open LocalDirector User Interface configuration, and subsequent edits you make are to this configuration.
Close the current LocalDirector User Interface configuration.
Delete a LocalDirector User Interface configuration.
Change server properties of the LocalDirector User Interface server.
Log out from the LocalDirector User Interface server.
Exit from the LocalDirector User Interface server completely.

Edit Menu

From the Edit menu you can:

Undo up to the last ten actions
Redo up to the last ten actions
Cut selected objects
Copy selected objects
Paste copied objects to specified locations
Delete selected objects
Manage buddy groups
Edit properties of selected objects
Edit the server state, including:
- In service
- Out of service Normal
- Out of service Failed
- Out of service Sticky
- Out-of-service Maintenance
Enable edits in Online mode
Enable edits in Offline mode

Add Menu

From the Add menu you can add the following objects:

LocalDirector
Virtual server
Real server
Probe

Help Menu

From the Help menu you can access:

The online version of this manual
Information about the LocalDirector User Interface 3.1

Online Edit Option

The Online Edit option allows you to configure LocalDirector in Online or Offline mode. In Online mode, the edits you make at the LocalDirector User Interface client are communicated immediately to the LocalDirector User Interface server and to LocalDirector, if it is connected. In Offline mode, edits are known only to the LocalDirector User Interface client. If you browse from or exit the LocalDirector User Interface while in Offline mode, the LocalDirector User Interface prompts you to save changes you made while in Offline mode.

Note In general, you probably want to work with the LocalDirector User Interface in Online mode. However, you may want to work in Offline mode if you do not want changes to be reflected at the LocalDirector immediately. For example, if you have many virtual server or real server edits, it can be quicker to make the updates in Offline mode. When you are finished, you can switch to Online mode, where you are prompted to save the changes to the LocalDirector User Interface server disk. If there is an attached LocalDirector, all the changes are also sent to the LocalDirector.

Table of Contents

LocalDirector User Interface Basic Configuration