Release Notes: SCO OpenServer ESP Driver
Release notes for version 3.14 of the ESP software for SCO OpenServer.
Supported OpenServer Releases
The ESP driver and associated software is only supported on SCO OpenServer releases 5.04 and up. This package may not be used on OpenServer 6 systems.
Installation
The driver package can be installed using the standard procedure for installing OpenServer packages:
Please refer to the SCO man page or documentation if you are unfamiliar with the procedures for using custom.
Components
The following are provided on the installation diskette:
- version 3.14 of the eqnesp device driver
- versions 3.14 of the diagnostic utilities (esp, espcfg, espdiag and esptty)
- system man pages.
Installation From Equinox FTP Site
The following steps should be followed to update and configure the ESP driver on the OpenServer system.
1. Transfer the driver image to the OpenServer system.
This step is required only if you downloaded the file to a DOS system. You may skip this step if you downloaded directly to the OpenServer system.
a. Copy the archive file onto a high density DOS diskette.
"copy esp_openserver_314.Z a:"
b. Remove the DOS diskette and insert into the OpenServer system.
c. Copy the file into the /tmp directory:
"doscp a:esp_openserver_314.Z /tmp/esp_openserver_314.Z"
2. Uncompress the driver file from the download file .
a. Change directory to /tmp:
b. Uncompress the driver file in the /tmp directory:
"uncompress esp_openserver_314.Z"
This will create a file with the same name as the download file without the extension .Z, i.e. “ esp_openserver_314"
This file is a media image of an installable floppy.
3. Build installation media .
There are two installation options: install directly from file or install from floppy.
a. Installation from Media Image
"mv esp_openserver_314 VOL.000.000" –or-
"cp esp_openserver_314 VOL.000.000"
NOTE: the 000 in the above file name are Zeroes, not the letter O.
You will need to remember where the media image file exists (e.g., /tmp). Proceed to step 4.
b. Installation from Floppy
b1. Insert a blank UNIX formatted 3.5" HIGH DENSITY diskette into the first drive on your OpenServer system.
b2. Copy the uncompressed file from the /tmp directory to the floppy using "dd" " dd if=/tmp/esp_openserver_314 of=/dev/fd0 bs=1024 "
NOTE: Check your operating system documentation for the correct syntax to use for your floppy drives.
4. Install the Driver
a. Install the driver
Install the driver using the “custom” utility. Installation will be either from media image or floppy. Note that if an existing driver is installed, it must first be removed. Refer to the operating system documentation for more information on custom.
b. Customize
You will need the following information for the driver configuration:
a. The maximum number of ESPs you would like to configure the driver to support. If you need to increase the maximum number of ESPs at a later date, you will need to remove the driver and reinstall
b. You may also need to know the MAC address of the ESPs to differentiate between multiple units (if you are installing multiple units) and what IP address you wish to assign to the ESPs. This information may be required during the "espcfg" portion of the install process.
5. Configure the ESPs
Configure and enable the ESPs using the "espcfg" program. A man page is provided with the installation. You can check the status of the ESPs after they are configured using either the "esptty" utility or the "espdiag" utility. Man pages are provided for these utilities as well. There is also an overview man page named "esp".
The "espcfg" program will be invoked automatically during the installation of the package. If this is an upgrade and there is an existing configuration file (/etc/eqnx/esp.conf) you will be asked if you want topreserve the existing configuration.
Please refer to the SCO OpenServer documentation for information on how to configure ports for login, printing, and other serial capabilities (i.e., cu).
The device names in the file system space follow OpenServer conventions.
For example, ESP 1 will have names like /dev/tty01e0 (the direct connect or lower case device) or /dev/tty01E0 (modem or upper case device).
The "01" in the name reflects the ESP number assigned by espcfg and the ports range from 0 (zero) to f (Hexadecimal for 15). On ESPs with less than 16 ports the range of port numbers will match that of the ESP (e.g., 0 to 8 on an 8 port ESP, 0 to 1 on a 2 port ESP).
Differences between release 3.13 and 3.14:
- Added support for ESP-8 MI and ESP-16 MI models.
- Changes to support "Avocent" branding.
- Fix to espcfg to eliminate problem with clearing ARP cache after removing an ESP.
Differences between release 3.12 and 3.13:
- Added support for ESP-4 MI models.
Differences between release 3.10 and 3.12:
- Added support for ESP-4 Mc models.
- Fix for espcfg with ESP-8 MI models. The esp_port.conf file would be
built incorrectly. This would affect the replace function for an
ESP-8 MI.
- Added remote datascope capability to espdiag. This allows datascope
to be run to monitor serial traffic on an ESP even if the data is not
being sent to/from the local system.
- Added the -m option to espdiag. When invoked with this option, menu
items that specify an ESP port will present two fields for an ESP number
(01-64) and ESP port number (1-16). Without this option (the default),
these menu items will expect a device name (such as /dev/ttyQ01e0).
- Modifications to esp process, primarily for handling the case when
ESP connectivity is lost.
Differences between release 3.08 and 3.10:
- This release incorporates support for the ESP-2 OPTO product.
- There are a number of fixes associated with interactions between the modem (upper case) device and the direct connect (lower case) device. Concurrent opens of both devices could result in hung ports or in one case a locked up system.
- A fix related to the draining of ouput and ioctls was added. This problem was actually found on the SST OpenServer driver but it seemed a good idea to add a similar fix to the ESP driver.
Differences in release 3.08:
- Modified the esp utility so that it closes all files inherited from its parent process.
- Added the ability to configure the UDP timeout value using the espcfg utility. A timeout occurs if the amount of time since a UDP “heartbeat” message has been received exceeds the timeout value. When the timeout occurs, the connection between server and ESP is severed. By default, the timeout value is 60 seconds. On some WANs, it may be desirable to change this value (typically increasing it).
- Fix to the espcfg utility so that the “one-port option” is provided when manually adding an ESP-2 MI that was not discovered on the network.
- Fix to the espcfg utility so that the “one-port option” is preserved when replacing an ESP-2 MI.
- Fix to the espdiag utility so that the display updates correctly when running loopback at very low baud rates.
|
