Installation guide

Chapter 3. Requirements
3.1. Required States and Modes
Once booted, a Freeway is always in only one state: ready. All references to any Freeway operation in this document
refer to a Freeway in the ready state.
3.2. Freeway Capability Requirements
This section describes the requirements which are specific to the primary mission of most Freeways, which is to
enable WAN access via an IP network.
3.2.1. DLI/TSI Server Requirement
The Freeway software must provide a complete DLI/TSI server interface, as described in the two manuals Freeway
Data Link Interface Reference Guide (DC-900-1385) and Freeway Transport Subsystem Interface Reference Guide
(DC-900-1386).
3.2.2. ICP Hosting Requirement
The Freeway software must provide complete support for one or more ICP boards. This support must include not
only driver-level support and protocol-downloading support, but also inter-communication between DLI/TSI clients
and the ICP board serial data ports.
3.2.3. User Interface Requirements
The Freeway software must provide a user interface to allow one or more users to login and control the operation of
the Freeway . Users may login via either an Ethernet interface, or directly through a serial console cable. The user
interface must offer the ability for logged-in users to perform all actions which may be necessary to get information
about or control the Freeway.
3.3. Freeway External Interface Requirements
The external interfaces of the Freeway software are to one or more DLI/TSI clients (generally across the Ethernet, but
may also be via the "localhost" network address from within the Freeway), to one or more data-communications ports
(on the ICP boards), and to one or more logged-in users (which may be via a serial console connection, or via an
Ethernet connection). The requirements which must be met for each of these interfaces are specified in
Section 3.2.
12