LRS Reference Manual
2 - Getting Started
- 2.1 - Introduction
-
- 2.2 - Methods of Configuration
-
- 2.2.1 - EZCon
-
- 2.2.2 - Command Line Interface
-
- 2.2.2.1 - Entering and Editing Commands
-
- 2.2.2.2 - Command Types
-
- 2.2.2.2.1 - Set and Define
-
- 2.2.2.2.2 - Show, Monitor, and List
-
- 2.2.2.2.3 - Clear and Purge
- 2.2.2.3 - Restricted Commands
- 2.2.3 - Front Panel Buttons (LRS2 Only)
- 2.3 - Maintenance Issues
-
- 2.3.1 - Setting the Date and Time
-
- 2.3.1.1 - Setting the Clock
-
- 2.3.1.2 - Setting the Timezone
-
- 2.3.1.3 - Configuring a Timeserver
- 2.3.2 - Rebooting the LRS
-
- 2.3.3 - Restoring Factory Defaults
-
- 2.3.4 - Reloading Operational Software
-
- 2.3.5 - Editing Boot Parameters
-
- 2.3.6 - LRS System Passwords
-
- 2.3.6.1 - Privileged Password
-
- 2.3.6.2 - Login Password
- 2.3.7 - Configuration Files
-
- 2.3.7.1 - Using EZCon
-
- 2.3.7.2 - Without EZCon
-
- 2.3.7.2.1 - Creating the File
-
- 2.3.7.2.2 - Host Configuration
-
- 2.3.7.2.3 - LRS Configuration
- 2.3.7.3 - Download Sequence
-
2.1 Introduction
This chapter covers some background information to get you started using the LRS. Topics include:
- Methods for setting up the LRS
- "Quick start" instructions for basic networking applications; for example, an outgoing LAN to LAN connection
- Ongoing maintenance issues, for example, restoring factory default settings
This chapter assumes the following:
- The LRS is running operational code (in other words, the unit has successfully booted)
- The LRS is connected to an Ethernet
- If IP is being used, the LRS has been assigned an IP address
For details on booting, installation, or assignment of an IP address, refer to your Installation Guide.
2.2 Methods of Configuration
The LRS may be configured using any of the following methods: the EZCon configuration software, commands issued at the command line (Local>) prompt, or the front-panel buttons (LRS2 only).
To configure the LRS when a problem has occurred (for example, the unit doesn't boot successfully and a Boot> prompt appears on the console port), refer to the Troubleshooting appendix of your Installation Guide.
2.2.1 EZCon
The EZCon software is the easiest way to configure the unit. EZCon guides you through configuration using a graphical interface.
UNIX, Macintosh, and Windows versions of EZCon are shipped with the LRS on a CD-ROM. To use the CD-ROM, refer to the instructions on the CD-ROM case. To install EZCon, refer to the appropriate EZCon README file.
All instructions for using EZCon are listed in each README file. For assistance once EZCon is running, refer to the EZCon online help.
2.2.2 Command Line Interface
To configure the LRS without EZCon, configuration commands must be entered at a command line. These commands are entered when a port is in character mode; in this mode, the Local> prompt will be displayed.
There are three ways to display the Local> prompt:
- Connect a terminal to the serial console port and press the Return key until the prompt is displayed.
- Establish a Telnet or Rlogin connection to the LRS from a TCP/IP host.
- In EZCon, click the Terminal icon. The Local> prompt will be displayed in a terminal emulation window.
- Establish a TCP/IP remote console connection. For a complete description, see Chapter 5 - IP.
2.2.2.1 Entering and Editing Commands
In examples throughout the manual, LRS commands and keywords are displayed in upper case for clarity. They may be entered in upper, lower, or mixed case.
The Command Reference (Chapter 12) displays the syntax of each command, including any restrictions, known errors, and references to related commands. Optional parameters are enclosed in brackets [ ]. Required parameters are enclosed in curly braces { }; one and only one of these parameters must be used. User-supplied parameters, such as a particular port number or host name, are shown in italics.
- The privileged and login passwords are case-independent, even when enclosed in quotes.
When entering a string, such as a username or filename, it is important to remember to enclose the string in quotes; this will retain the case entered. If a string is not enclosed in quotes, it will be automatically changed to all upper case characters.
The LRS' command completion feature will complete partially-typed commands for you. This can save time and reduce errors if you're entering a number of commands. To use command completion, type part of a command, then press the space bar; the LRS will automatically "type" the remainder of the command.
Command completion is disabled by default. To enable command completion, refer to Set/Define Port Command Completion.
All keys used for entering and editing commands are listed in Table 2-1.
Table 2-1: Command Line Editing Keys
Key | Purpose |
Return | Executes the current command line |
Delete | Deletes the character before the cursor |
Ctrl-A | Toggles insert mode (insert or overstrike). Overstrike is on by default. |
Ctrl-D | Logs out of the server |
Ctrl-E | Moves the cursor to the end of the line |
Ctrl-H or Backspace | Moves the cursor to the beginning of the line |
Ctrl-R | Redisplays the current command |
Ctrl-U | Deletes the entire current line |
Ctrl-Z | Logs out of the server |
Left Arrow | Moves the cursor left |
Right Arrow | Moves the cursor right |
Up Arrow or Ctrl-P | Recalls the previous command |
Down Arrow or Ctrl-N | Recalls the next command |
!text | Recalls the last command starting with text |
!! | Recalls the last command |
Line editing is disabled on hard copy (printer) ports.
2.2.2.2 Command Types
The following commands appear frequently throughout this manual. There are subtle differences between each group of commands, explained below:
2.2.2.2.1 Set and Define
- Set
- Makes an immediate (but not permanent) change. To make the change permanent, the Save command must be used.
- Define
- Makes a permanent change, but the change doesn't take effect until the LRS is rebooted.
Define Port will take effect as soon as the port is logged out, and Define Site will take effect when a site starts.
2.2.2.2.2 Show, Monitor, and List
- Show
- Displays the current settings. Current settings include those made using the Set command but not saved as permanent changes.
- Monitor
- Displays the current settings; information is updated every three seconds.
- List
- Displays permanent settings.
2.2.2.2.3 Clear and Purge
- Clear
- Removes an item immediately, but does not make a permanent change.
- Purge
- Removes an item permanently, but it doesn't take effect until the unit is rebooted.
Purge Port will take effect as soon as the port is logged out, and Purge Site will take effect when a site starts.
2.2.2.3 Restricted Commands
Some commands require privileged (superuser) status. To obtain privileged status, the privileged password must be entered. See Privileged Password.
2.2.3 Front Panel Buttons (LRS2 Only)
The buttons on the front panel of the LRS2 may be used for limited initial configuration. Items that may be configured include the IP address, subnet mask, and software loadhost.
For complete details on the front panel buttons, refer to the LRS2 Installation Guide.
2.3 Maintenance Issues
The following sections detail configuration that's often required on a sporadic or ongoing basis.
2.3.1 Setting the Date and Time
The LRS can calculate and save the local time, coordinated Universal Time (UTC), also known as Greenwich Mean Time (GMT), standard and Daylight Savings timezones, and the corresponding number of hours difference between UTC and the set timezone.
2.3.1.1 Setting the Clock
Use EZCon's Maintenance feature to set the local date and time, or use the Set/Define Server Clock command at the Local> prompt.
Figure 2-1: Setting the Clock
Local>> SET SERVER CLOCK 14:15:00 12/31/1995 |
2.3.1.2 Setting the Timezone
The LRS is configured to recognize a number of timezones. To display these timezones, use the Show Timezone command at the Local> prompt. Set the timezone by using EZCon's Maintenance feature, or using the Set/Define Server Timezone command at the Local> prompt:
Figure 2-2: Setting the Timezone
Local>> DEFINE SERVER TIMEZONE US/PACIFIC |
If your timezone is not displayed, you will need to set it manually. Use the following information to set the timezone:
- A 3-letter timezone abbreviation; for example, PST
- The number of hours offset from UTC (Greenwich Mean Time); for example, -9:00
- The time, day, and amount of any time changes (for example, daylight savings time information)
Specifying time change information is optional.
To manually set the timezone using EZCon, use the Maintenance option. To set the timezone using commands at the Local> prompt, refer to the following example:
Figure 2-3: Manual Timezone Configuration
Local>> DEFINE SERVER TIMEZONE EST -3:00 EST 1 Mar Sun>=1 3:00 Oct lastSun 2:00 |
In Figure 2-3, the first EST specifies that Eastern Standard Time will be used as the reference point. The second value, -3:00, indicates that this timezone is 3 hours behind of Eastern Standard Time.
The third and fourth values, EST and 1, specify that when a time change occurs the time will move forward one hour. The time change will occur in March, denoted by Mar. The date that the time change will occur will be the Sunday (Sun) greater than or equal to 1 (>=1), in other words, the first Sunday in the month. The 3:00 specifies that the time change will
occur at 3 o'clock.
The final 3 values of the command string represent the day and time when the time will revert to the original time, in other words, when the time change will be reversed. The Oct and lastSun indicate that the time will revert on the last Sunday in October. The time change will occur at 2:00.
2.3.1.3 Configuring a Timeserver
The LRS regularly verifies and updates its time setting with the designated timeserver. A timeserver is a host which provides time of day information for nodes on a network.
To specify a timeserver or backup timeserver, either use the Set/Define IP Timeserver or Set/Define IPX Timeserver command.
Figure 2-4: Set IP Timeserver Command
Local>> DEFINE IP TIMESERVER 193.0.1.50 Local>> DEFINE IP SECONDARY TIMESERVER 193.0.1.51 |
2.3.2 Rebooting the LRS
There are three ways to reboot the LRS:
- At the Local> prompt, use the Initialize Server command.
- Using EZCon, click Reset. You will be prompted with a dialog asking you to confirm the reboot. Click OK. The server will reboot.
- On the LRS2, select the Reboot option from the front-panel menu.
Before rebooting the LRS, any current user sessions should be logged out (if possible). Disconnecting sessions may prevent connection problems after the LRS is rebooted.
- Broadcast messages are not sent to remote networking users.
It is courteous to warn users that the LRS will be "going down"; this can be done using the Broadcast command.
Figure 2-5: Broadcast Command
Local>> BROADCAST ALL "Server shutdown in 5 minutes." |
When the LRS is rebooted, any changes made using Set commands will be lost. To ensure that the changes will be saved, use Define commands, or use the Save command after the Set command is used.
2.3.3 Restoring Factory Defaults
Restoring factory default settings will erase all changes made since the LRS was shipped; the unit will function as if it just came out of the box.
To restore factory defaults, use the Initialize Server Factory command at the Local> prompt. If you're using an LRS2, factory defaults can also be restored using the front panel menus; use the Flush NVR option.
For information on the LRS2 front panel menus, see the LRS2 Installation Guide.
To perform a TFTP boot, the LRS IP and loadhost information will have to be re-entered. (If a BOOTP server will provide this information, this is not required.) Refer to your Installation Guide for instructions.
2.3.4 Reloading Operational Software
The LRS stores its software in Flash ROM. This software controls the initialization process, the operation of the LRS, and the processing of commands. The contents of Flash ROM can be updated by downloading a new version of the operational software.
For instructions on reloading Flash ROM, refer to your Installation Guide.
2.3.5 Editing Boot Parameters
If the information that the LRS uses at boot time changes, you will need to edit the LRS boot parameters. Boot parameters include the following:
- Loadhost (TCP/IP or NetWare)
- The loadhost is the host from which the LRS operational software is downloaded at boot time.
- Backup loadhost (optional)
- Software is downloaded from a backup loadhost when the primary loadhost is unavailable.
- Software filename
- RARP (may be enabled or disabled)
- BOOTP (may be enabled or disabled)
Boot parameters are edited using Set/Define Server commands, for example, Set/Define Server Loadhost.
Figure 2-6: Editing the Loadhost Address
Local>> DEFINE SERVER LOADHOST 192.0.1.8 |
2.3.6 LRS System Passwords
There are two important passwords on the LRS: the privileged password and the login password. Both are discussed in the following sections.
2.3.6.1 Privileged Password
Changing any server, site, or port setting requires being the privileged user. When EZCon is used, you will be prompted for the privileged password when it is needed. If you are not using EZCon, you will need to use the Set Privileged command at the Local> prompt to become the privileged user. The default privileged password on the LRS is system.
Figure 2-7: Set Privileged Command
Local> SET PRIVILEGED Password> system (not echoed) Local>> |
The prompt will change to reflect privileged user status. If another user is currently logged into the LRS as the privileged user, use the Set Privileged Override command to forcibly become the privileged user.
To change the privileged password, the Set/Define Server Privileged Password command is required. Figure 2-8 displays an example of this command.
Figure 2-8: Changing Privileged Password
Local> SET PRIVILEGED Password> system (not echoed) Local>> SET SERVER PRIVILEGED PASSWORD hippo Local>> DEFINE SERVER PRIVILEGED PASSWORD hippo |
2.3.6.2 Login Password
Each port can be configured to require a login password when in character mode. Users will be prompted for this password when attempting to log into the port; the Local> prompt will not be displayed until the correct password is entered.
When a port is in character mode, PPP and SLIP are not running. See Port Modes for a complete description of port modes.
The default login password is access. To change this password, use the Set/Define Server Login Password command:
Figure 2-9: Defining Login Password
Local>> DEFINE SERVER LOGIN PASSWORD badger |
To enable the use of the login password on the appropriate port(s), use the following command:
Figure 2-10: Enabling Login Password
Local>> DEFINE PORT 3 PASSWORD ENABLED |
The LRS uses the login password to log into NetWare file servers. If the login password is changed, NetWare print queue setups must also be changed to reflect the new password.
2.3.7 Configuration Files
A configuration file is a series of LRS commands used to automatically configure the server. A configuration file may be used by the system administrator when necessary or downloaded automatically each time the server boots.
Using a configuration file can reduce the time required to configure the LRS. Options that would need to be manually set using EZCon or using commands at the Local> prompt can be automatically executed.
2.3.7.1 Using EZCon
EZCon will examine the current configuration of your LRS, translate this information into a series of commands, and save the commands in a file. This file may then be downloaded to configure the server. Refer to EZCon's online help for more information.
2.3.7.2 Without EZCon
To create a configuration file without EZCon, each LRS command will need to be manually entered in the file. Complete the instructions in the following sections.
2.3.7.2.1 Creating the File
On your host, enter a series of LRS commands, one command per line. Privileged commands may be included; when the file is downloaded, the commands will be executed as if a privileged user was logged into the LRS.
Capitalization of commands is optional. If a string (such as a password) is entered, it must be enclosed in quotes in order to preserve the case. To include a comment in the file, preface the text with a pound (#) character. These lines will be ignored.
If Define Server commands are included in the file, they will not take effect until the LRS is rebooted. Define Port commands will not take effect until the specified ports are logged out. Define Site commands will take effect when the specified site is started.
Initialization commands (for example, Initialize or Crash) must not be put in the file. The file is read when the LRS boots, if a "reboot" command is in the file, the LRS will perpetually boot; the LRS NVR will have to be flushed in order to correct the error.
Testing the configuration file is strongly recommended. To test the file, use the Source command.
An example of a configuration file is displayed below:
Figure 2-11: Configuration File
DEFINE PORT 2 SPEED 9600 DEFINE PORT 2 PARTIY NONE # this is a comment. The following commands set up the ports: DEFINE PORT 2 ACCESS DYNAMIC |
2.3.7.2.2 Host Configuration
A configuration file can be downloaded from a TCP/IP host (via TFTP) or from a NetWare fileserver.
If you're using a TCP/IP host, ensure that TFTP loading is enabled on your host and place the configuration file in a download directory. If you're using a NetWare host, place the configuration file in the fileserver's login directory.
2.3.7.2.3 LRS Configuration
- If Set Server Startupfile is used (rather than Define), the Save command must be used.
To configure the LRS using the commands in the configuration file, use the Source command.
If the configuration file must be downloaded each time the LRS boots, the filename must be specified using the Set/Define Server Startupfile command. A TCP/IP filename must be specified in host:filename format, where host is an IP address. To download the configuration file from a NetWare fileserver, use the node\sys:\login\filename format.
- If lower-case or non-alphabetical characters are used, the filename must be enclosed in quotes.
For example, to download the file config.sys from TCP/IP host 192.0.1.110, the following command would be used:
Figure 2-12: Downloading From TCP/IP Host
Local>> DEFINE SERVER STARTUP "192.0.1.110:config.sys" |
- To designate a nameserver, see Set/Define Server Nameserver.
If the LRS has a nameserver defined, a text name may be specified as a TCP/IP host name. The LRS will attempt to resolve the name at boot time; if it cannot resolve the name, the download will fail.
Figure 2-13 displays an example of a NetWare download configuration:
Figure 2-13: Downloading From NetWare Fileserver
Local>> DEFINE SERVER STARTUP "TROUT\SYS:\LOGIN\config.sys" |
- The LRS is not usable during download attempts.
During its boot sequence, the LRS will load its operational code first, then attempt to download the configuration file. If the attempt to download the configuration file is unsuccessful, the LRS may re-attempt the download. By default, the LRS will make 6 attempts to download the file (1 initial attempt, and 5 re-attempts). To change this setting, use the Set/Define Server Startupfile Retry command:
Figure 2-14: Setting Number of Download Attempts
Local>> DEFINE SERVER STARTUPFILE "TROUT\SYS:\LOGIN\config.sys" RETRY 10 |
2.3.7.3 Download Sequence
If Retry is set to 0, the LRS will be unusable; it will be endlessly waiting for the configuration file to download.
LRS Reference Manual - 4 MARCH 1996
Generated with Harlequin WebMaker