vtc.addrs(4M) DG/UX R4.11 vtc.addrs(4M)
NAME
vtc.addrs - VTC/PTC configuration file
SYNOPSIS
/etc/tcload/vtc.addrs
DESCRIPTION
The vtc.addrs file contains network configuration information for
Systech VMEbus/PCI bus Terminal Controller (VTC/PTC) boards. The
information contained in this file is communicated to the board when
tcload(1M) is run or when the controller is reset.
Note that if a controller or tty device entry is added or modified
for a VTC/PTC that is part of a failover configuration involving a
remote host, then the failover databases must be synchronized with
that remote host after modifications are complete (see
admfailovervtc(1M)). To use the remote failover functionality, you
must have either the Failover package or the DG/UX Cluster Software
product installed.
The vtc.addrs file contains entries for controller specific
information and entries for tty specific information. Each tty entry
in this file must be for a tty that is associated with a VTC/PTC, and
tty entries must immediately follow the controller entry with which
the tty is associated. Fields in all entries are whitespace
separated. There must be one controller specific entry for each
configured VTC/PTC. Tty specific entries are optional.
The tty specific entries allow the system administrator to alter the
behavior of ttys associated with a controller. By default, ttys
associated with a VTC/PTC answer telnet connections made to the
default Internet address for that controller. Since the default
telnet port number is 23, the basic behavior of the VTC/PTC is to
only accept telnet connections made to the default Internet address
at port 23. The tty specific entries allow the system administrator
to support multiple rotaries per board by configuring ttys to answer
connections for different Internet addresses or to call out to
different Internet addresses. The system administrator also has
control over which protocol and port is used by the VTC/PTC for each
specified tty. This behavior is useful when it is necessary to
associate a specific terminal entry with a specific device via a
telnet, rlogin, or TCP connection (see vtcttyaddrs(1M)).
Tty specific entries also allow the system administrator to determine
how telnet binary mode affects onboard input processing for telnet
connections (see termio(7)). By default, onboard input processing is
unaffected by the state of telnet binary mode, and can only be
enabled or disabled by changing the line discipline settings (see
termio(7)). Ttys associated with a VTC/PTC can be configured such
that when the telnet connection is in telnet binary mode, onboard
input processing is also disabled. Note, however, that input
processing performed by the host for a tty associated with a VTC/PTC
will always be unaffected by the state of telnet binary mode. Rarely
will an application require that onboard input processing be disabled
when telnet binary mode is in effect, as input processing is normally
controlled exclusively via the line discipline settings.
Controller Specific Entries
The controller specific entries have the following format:
BoardSpec InetAddr BAddr Netmask RouteInfo [NetRej]
The BoardSpec field specifies the full pathname of a controller's
device node (see syac(7)) that must refer to a VTC/PTC device (e.g.,
/dev/async/ctrl/syac(vme(0),0) or /dev/async/ctrl/spac(pci(0),F)).
The InetAddr field specifies the default Internet address that will
be assigned to the controller. The Internet address is specified in
dot format (see inet(3N)). By default, all ttys associated with this
VTC/PTC will respond to telnet connections to this address at port
23. This behavior may be altered via tty specific entries in this
file or by using vtcttyaddrs(1M).
The BAddr field specifies, in dot format (see inet(3N)), the
broadcast address for the network to which the VTC/PTC is attached.
The Netmask field specifies, in dot format (see inet(3N)), the
netmask for the network to which the VTC/PTC is attached.
The RouteInfo field specifies the location of the routing
information that should be communicated to the controller. The value
of this field should be either the keyword default or the full
pathname of a file containing routing information. If the keyword
default is specified, then the routing information read from the host
routing table will be communicated to the VTC/PTC. If a pathname is
specified, then the named file is read and the routing information in
the file is communicated to the VTC/PTC. The format of the file
should be identical to that of the gateways(4M) file.
The NetRej field is an optional field that can have either the
keyword on or the keyword off as its value. If the field is not
present or if the keyword off is specified, then the VTC/PTC will not
send a network rejection message when it rejects a connection. If
the keyword on is specified, then the VTC/PTC will send a network
rejection message when it rejects a connection.
It is an error if a configured VTC/PTC does not have a controller
specific entry in this file or if any of the fields other than
NetRej are missing or blank.
Tty specific Entries
The tty specific entries have the following format:
Ttypath [InetAddr][@Port] [Protocol [Binaryflag [Inputflag]]]
The Ttypath specifies the full pathname of the tty device for the
entry (e.g. /dev/tty34).
For call in ttys, InetAddr specifies the Internet address to which
the tty should respond to network connections. For call out ttys,
InetAddr specifies the Internet address that the tty should attempt
to make a connection when the tty device is opened. The calling
direction of the tty depends on the tty entry's specified Protocol.
The Internet address should be in dot format (see inet(3N)).
For call in ttys, Port specifies the port number to which the tty
should respond to network connections. For call out ttys, Port
specifies the port number on the remote host that the tty should
attempt to make a connection when the tty device is opened. The
calling direction of the tty depends on the tty entry's specified
Protocol. The Port is optional for all Protocols except tcpin and
tcpout, since neither has a default port. If the Port is specified,
there should be no spaces between the InetAddr, @, and the port's
decimal value (e.g. 128.222.3.16@23). If the Port is not specified,
the @ symbol should not be included in the tty specific entry. Note
that port definitions are per controller and a port can only have one
defined input protocol. In other words, do not use the same port
number for multiple tty entries if the entries have different input
protocols. For example, if an entry for tty02 has the port set to
200 and protocol set to telnetin, and the next entry is for tty03
with the port set to 200 and protocol set to rlogin, tty02 will
really end up using a rlogin protocol, since its port's protocol has
been changed by the tty03 entry.
The Protocol field specifies the network protocol and direction of
the specified tty. Below is a list of the allowable Protocol values
along with their default Port values and a brief description of their
meaning.
Protocol Default Port Description
telnetin 23 Uses TELNET protocol
rlogin 513 Uses RLOGIN protocol
tcpin None Uses TCP protocol
telnetout 23 Calls out using TELNET protocol
tcpout None Calls out using TCP protocol
The Binaryflag field is an optional field that can have either the
keyword on or the keyword off as its value. If the field is not
present or if the keyword on is specified, then the controller will
attempt to negotiate telnet binary mode whenever a telnet connection
is accepted for the tty in question. If the keyword off is
specified, then the controller will not attempt to negotiate telnet
binary mode when a connection is accepted for the tty in question.
This flag only pertains to the telnetin protocol.
The Inputflag field is an optional field that can have either the
keyword on or the keyword off as its value. If the field is not
present or if the keyword on is specified, then input processing will
be unaffected by the state of telnet binary mode. If the keyword off
is specified, then onboard input processing will be disabled when
telnet binary mode is in effect on the line. Note that if this field
is specified, then the Binaryflag field must also be specified.
This flag only pertains to the telnetin protocol.
It is not necessary for each tty controlled by a VTC/PTC to have a
tty specific entry in this file. By default, a tty will answer to
telnet connections to the Internet address of the associated
controller, telnet binary mode will be negotiated on when a
connection is established, and input processing will be unaffected by
the state of telnet binary mode. A tty should have an entry in this
file only if this default behavior needs to be changed.
Tty specific entries must be located after the controller specific
entry for their controlling VTC/PTC and before any other controller
specific entries.
EXAMPLES
/dev/async/ctrl/syac(vme(0),0) 128.222.3.112 128.222.3.255 255.255.255.0 default on
/dev/tty34 128.222.3.113
/dev/tty35 128.222.3.113
/dev/tty112 128.222.3.84@800 telnetout
/dev/tty114 @1000 tcpin
In this example, syac(vme(0),0) will have an Internet address of
128.222.3.112, a broadcast address of 128.222.3.255, and a netmask of
255.255.255.0. It will use the same routing information as the host
computer. It will send a network rejection message for all
connections it rejects. It should control /dev/tty34 and /dev/tty35,
which forms one rotary that answers telnet connections to Internet
address 128.222.3.113 at port 23. It should also control
/dev/tty112, which forms its own rotary that calls out to Internet
address 128.222.3.84 at port 800 with a TELNET protocol. Finally it
should control /dev/tty114, which will answer connections to Internet
address 128.222.3.112 (i.e. this VTC's default) at port 1000 with a
TCP protocol. Tty114 and all other tty connections made to the
default internet address form the third rotary. The default behavior
as regards telnet binary mode will apply to /dev/tty34 and all other
ttys controlled by syac(vme(0),0) that do not have tty specific
entries in the vtc.addrs file.
/dev/async/ctrl/spac(pci(0),F,0) 128.222.8.96 128.222.8.255 255.255.255.0 /etc/spac1
/dev/tty260 128.222.8.97 telnetin off on
/dev/tty265 128.222.8.87 rlogin
In this example, spac(pci(0),F,0) will have an Internet address of
128.222.8.96, a broadcast address of 128.222.8.255, and a netmask of
255.255.255.0. The routing information in /etc/spac1 will be
communicated to the board. spac(pci(0),F,0) should control
/dev/tty260, which will respond to telnet connections to Internet
address 128.222.8.97 at port 23. telnet binary mode will not be
negotiated on when a connection is established for /dev/tty260.
However, if the connection is negotiated into telnet binary mode (by
a termserver, for example), on board input processing will be
unaffected (this is the default). spac(pci(0),F,0) should also
control /dev/tty265, which will respond to rlogin connections to
Internet address 128.222.8.87 at port 513.
FILES
/etc/tcload/vtc.addrs VTC/PTC configuration file
SEE ALSO
tcload(1M), vtcroutes(1M), vtcttyaddrs(1M), vtcsnmpfiles(1M),
admfailovervtc(1M), chk.devlink(1M), devlinktab(4M), inet(3N),
gateways(4M), syac(7), termio(7).
NOTE
The chk.devlink command is responsible for creating and maintaining
links to each port device node, with a pathname of the form
/dev/tty[0-9]* (see chk.devlink(1M) and devlinktab(4M)).
Licensed material--property of copyright holder(s)