AWAN 3883/4/5 Access Server Configuration and Management Manual

Command Line Interface (CLI) Commands
AWAN 3883/4/5 Access Server Configuration and Management Manual—424242-001
C-6
User Validation
Term Type 6530, Current Loop, Autoconnect Enabled
For current loop ports with Port Autoconnect Enabled (RMT Port Properties Adv. Line
Autoconnect checkbox), the single character login feature is not allowed. For these
ports, login is accomplished by three consecutive Enter (hex 0d) keys, or by a terminal
hard Reset/Power ON (hex 05 0d). If any other input, including Break, is received,
AWAN displays the following:
To login, press Enter or Return 3 times, or use Hard Reset
Term Type 6530, Not a Modem Port
Any single character indicates a terminal session. When a 6530 terminal is powered on,
a two-character sequence (ENQ CR, or hex 05 0d) is sent by the terminal to the AWAN
access server, which begins the session. The same ENQ CR is sent on a hard reset
function, which is initiated by key combinations that vary by terminal or emulator. The
following greeting is displayed:
Connected to AWAN access server name Port Port_num
Term Type 6530, Modem Port
Some special considerations apply to modem ports. These considerations are designed to
enable the same port to support dial-in from both 6530 terminals and remote access
clients and include the following:
•
When the AWAN access server detects a new call, a four-second timer is started.
This interval enables remote access clients (such as the Windows 95 RAS dialer) to
automatically begin their unique identification sequence. If a proper sequence is
received, normal remote access login proceeds.
•
The Enter-Enter-Enter sequence may be keyed in at any time before the four-second
interval expires to indicate a terminal session. If no response is received after four
seconds, a terminal session is assumed just as if the Enter-Enter-Enter sequence was
typed. This feature allows automated terminal session initiation. If this automatic
sequence interferes with login from remote access clients, you should change the
Term Type to ANSI and use the standard protocol detection described in Term Type
Not 6530 on page C-5.
User Validation
After the protocol is detected as a terminal or as a particular type of remote access
session, user validation begins. User validation varies according to Term Type that is
configured and the type of session. (Term Type may be configured on the Adv. Line tab
dialog box in the RAS Management Tool or by using the Change Port Type command.)
Each Term Type configuration and session combination is described in the following
subsections.