CHAPTER 7: TERMINAL SERVER APPLICATION NOTES
TERMINAL SERVER APPLICATION NOTES
MULTINET4 MULTI-PORT SERIAL SERVER & MANAGED SWITCH – INSTRUCTION MANUAL
7–5
The following configuration parameters also effect the operation of the port in active
mode:
•
Local IP
– the IP address to which the channel binds before making an outgoing
connection. This is the address used in a transmitted packet's source address IP
header field.
•
Local TCP
– the TCP port to which the channel binds before making an outgoing
connection. The TCP port may be in the range 1000 to 65535. This is the port
number used in a transmitted packet's source port TCP header field. It is invalid to
assign the same TCP port to multiple terminal server channels. When a channel is
configured in active mode, it is also valid to assign a value of '0' for the Local TCP
port. This tells the system that it can select any unused port number as the local
TCP port for this connection.
•
Remote IP
– the IP address to which the terminal server attempts to connect
•
Remote TCP
– the TCP port to which the terminal server attempts to connect
•
Retry Time
– when a connection attempt fails (for any reason), this is the minimum
amount of time the terminal server will wait before re-trying the attempt.
7.3.3
Mixed Mode
You can configure a terminal server port to operate in a mixed mode in which it
simultaneously acts as both a passive server and an active client. This is accomplished by
adding an "
IN
" channel as well as at least one "
OUT
" channel that uses the port. In general,
this mode should be used with care. If you configure both sides of a connection with a
mixed mode you can produce redundant TCP connections.
7.3.4
Session Type
Each terminal server port can be configured as a raw TCP connection or as a Telnet
connection. Generally, the session type should be specified as raw (the default) unless you
plan on connecting to the port using a telnet application. This may be appropriate in
certain cases where you are accessing a device console port using the terminal server.
Such a case is illustrated in
section 7.3.4: Session Type
.