Data Channels and Switching Configuration
NetRunner W
AN User’s Manual
5-25
Async Force Connections
In async force connections, the configuration of the port need not exactly
match, however, both ports must be configured as async (and for the same
character set). If a port is force connected, no other port may access it
through switching requests.
The procedure to force connect two async ports was described on page 522,
Force Connections
. Once force connected, the only way to access the
Command Facility is
^X <break> (or
^X ^Y, if enabled). You will not get the
ENTER CLASS
prompt.
Note:
Set the Remote CTS Control (Extended Features menu) for the device attached
to the port(s). If it is not, it may not be possible to connect to the Command
Facility once the force connection is made.
Classes
A class is a name assigned to a group of one or more ports that may be used
for similar purposes by network users (e.g., all ports connected to a specific
application may be contained in a class). Classes may be viewed as hunt
groups, where the user will be connected to any of the available ports in the
group. The maximum number of classes per NetRunner unit is 64. Users
can access port(s) by name, without having to know its physical location in
the network.
Classes provide the following features:
D
Secondary class is used if all ports in the primary class are busy
D
Password protection on destination port access
D
Configurable class messages
D
Disconnection on inactivity timer (no data activity timeout)
D
Port contention handling through firstcome, firstserve queues
(campon queues)
A port may be configured in only one class. A class does not need to be
exclusive to any node - multiple nodes may offer the same class. In fact, this
is desirable if multiple ports on multiple nodes are connected to the same
application.
