The Remote Annex allows four forms of dedicated ports for use with terminals and modems. To set a dedicated port:
• Set the serial line port parameter mode to telnet, tn3270, rlogin, or connect for ports using the telnet, tn3270, rlogin, or LAT protocols, respectively.
In earlier software releases, setting the mode parameter to dedicated enabled access to a single host. Connection to the host was made using either the rlogin or telnet protocol. Using telnet, you could configure a TCP port to allow the automatic start-up of an application on the host. (Valid TCP port numbers range from 1–65535.) A dedicated port had two mechanisms for originating the connection, depending on the setting of the control_lines parameter. If control_lines was set to modem_control or both, a connection was made automatically when DCD and DSR were asserted. If control_lines was not set to modem_control or both, pressing the Return key initiated the connection.
Ports defined as dedicated do not support either host-based security or local password protection.
For backward compatibility, the Remote Annex continues to support the dedicated option for the mode parameter, but we recommend using the newer options.
• Set the speed, data_bits, stop_bits, and parity parameters to match the terminal or modem used.
• If the dedicated port is connected directly to a terminal, set the type parameter to hardwired. The user is registered with the who database according to the input_is_activity and
output_is_activity parameter settings. If neither parameter is set, any user on this port is invisible to who. If input_is_activity is set, when the user enters data, the line is registered with the who database (generally used for hardwired CLI terminals). If output_is_activity is set, the line is registered when the Remote Annex first sends data (generally used for hardwired printers or other slave devices). This entry is removed on a hang-up or when the slave line is released, regardless of the
input_is_activity and output_is_activity parameter settings. If the connection times out without having received input from the user, the Remote Annex prompts Press return to restart login and then waits for input, or a hang-up, before retrying the connection.
If the dedicated port is connected to a modem, set type to dial_in. The user is registered with the who database as soon as a process (CLI or slave) attaches to the line, regardless of the input_is_activity and output_is_activity parameter settings.
The Remote Annex continuously retries the connection, regardless of errors.
• Set the dedicated_arguments parameter to the target host’s name or IP address. The Remote Annex passes this string to the command given in the mode parameter setting, so any command line arguments, such as the optional telnet port number, are valid here.
Some sample settings for the mode and dedicated_arguments parameters are:
• Creating a dedicated raw TCP connection to port 7001 on another Remote Annex:
port mode telnet
port dedicated_arguments "-st annextwo 7001"
• Using the name-resolution interface (no hardwired IP address is required as it would be with the older dedicated option):
port mode rlogin
port dedicated_arguments "myhost"
To test the dedicated port configuration, enter the port mode and dedicated_arguments settings as a CLI command. Since the
Remote Annex handles the arguments in exactly the same manner, you can easily test variations of the desired arguments until they work correctly.
When configuring a dedicated port, you may also want to set the following parameters:
• Setting the allow_broadcast parameter permits the display of any administrative messages at the terminal connected to the dedicated port.
• Set both the user_name and location parameters; the CLI who command displays these parameters. If the dedicated_port parameter is set to rlogin, the user name is passed with the connection request.
• The term_var parameter is a string that identifies the terminal type. Any value defined for this parameter is passed with both the telnet and rlogin connection requests. If you define a
• If you set the inactivity_timer parameter, also set the
input_is_activity or output_is_activity parameters (or both).
• To use EIA/hardware flow control (RTS/CTS), set the control_lines parameter to flow_control or both, and the input_flow_control and output_flow_control parameters to eia. The Remote Annex asserts RTS when it is ready to receive data, and checks the CTS input before transmitting data.
• To use software flow control (XON/XOFF), set control_lines to none or modem_control, and set both input_flow_control and output_flow_control to start/stop. The Remote Annex sends XOFF when it does not want to receive any more data; it sends XON when it is again ready to receive data. When the
Remote Annex receives XOFF, it stops sending data to the port;
when it receives XON, it resumes sending data to the port.
• The telnet_escape parameter defines the character that returns you to thetelnet:prompt when using the CLI telnet command.
Setting this parameter to U disables the Telnet escape. The default isCTRL-].