vtc_ttyaddrs(1M) DG/UX R4.11 vtc_ttyaddrs(1M)
NAME
vtc_ttyaddrs - set a VTC's/PTC's tty specific parameters
SYNOPSIS
vtc_ttyaddrs [ -b on|off ] [ -p on|off ] device ttyname ...
inet_addr port protocol
where:
device The full device node pathname of the VTC/PTC that owns the
specified tty(s).
ttyname The full device node pathname(s) of the tty(s) that should
respond to the specified internet address.
inet_addr The internet address for the specified tty(s), expressed in
dot notation (see inet(3N)).
port The port number for the specified tty(s).
protocol The protocol and direction for the specified tty(s).
DESCRIPTION
The vtc_ttyaddrs command operates on tty(s) controlled by a
VMEbus/PCI bus Terminal Controller (VTC/PTC). Normally, all ttys
associated with a VTC/PTC respond to telnet connections to the
board's default internet address as specified in vtc.addrs(4M). The
vtc_ttyaddrs command directs the named tty(s) to respond to network
connections or call out using the internet address, port, and
protocol specified on the command line. The behavior of the other
ttys that are controlled by the VTC/PTC is unaffected.
Note that if the specified VTC/PTC is configured for failover, none
of the modifications made to the primary board's tty specific
information using this command will be incorporated into its backup
board's tty specific information when failover occurs. Using
VTC/PTC's for failover requires the Failover package or DG/UX Cluster
Software product.
Port numbers are per VTC/PTC and can only have one defined input
protocol. In other words, a port cannot be associated with two
different ttys if the ttys have different input protocols.
The protocol specifies the protocol and direction of the specified
tty. Below is a list of allowable protocol values along with a brief
description of each type.
Protocol Description
telnetin Uses TELNET protocol
rlogin Uses RLOGIN protocol
tcpin Uses TCP protocol
telnetout Calls out using TELNET protocol
tcpout Calls out using TCP protocol
The ability to associate specific internet addresses with specific
ttys is useful when using passive devices, such as printers, with the
VTC/PTC. In order to access a device, a program must know its full
device node pathname. For the case of a device using a permanent
telnet connection to a VTC/PTC (as via a termserver), it would need
to know the device node of a tty, such as /dev/tty56. The system
must ensure that the telnet connection for such a device is always
associated with a specific tty that is controlled by the VTC/PTC.
The only way to associate a device with the proper tty is to assign
an internet address to that specific tty and have the device connect
to the assigned internet address via the telnet protocol.
Tty specific internet addresses can be assigned at any time with the
vtc_ttyaddrs command and are active until the system is rebooted or
the VTC/PTC is reset. The system will also assign tty specific
internet addresses during system boot based on the contents of the
vtc.addrs(4M) file.
The VTC/PTC board performs some aspects of input processing for the
host computer. By default, the input processing performed by the
board (and the input processing performed by the host) is not
affected by the state of telnet binary mode, and can only be enabled
and disabled by changing the current line discipline settings (see
termio(7)). Specific tty lines can be configured so that when the
telnet connection is negotiated into telnet binary mode, the input
processing performed by the board is disabled. Input processing
performed by the host is unaffected. The vast majority of
applications will not require this behavior. However, an option is
supported for applications that may require it. These options only
pertain to the TELNET protocol.
Options
-b on|off
If on, the VTC/PTC will attempt to negotiate telnet binary
mode when a connection is established for any of the tty lines
specified on the command line. If off, the VTC/PTC will not
attempt to negotiate telnet binary mode. By default, the
board will attempt to negotiate telnet binary mode for all
lines when a connection is established.
-p on|off
If on, onboard input processing will not be affected by the
state of telnet binary mode. If off, onboard input processing
will be disabled whenever telnet binary mode is negotiated on.
By default, onboard input processing is not affected by the
state of telnet binary mode.
EXAMPLES
vtc_ttyaddrs '/dev/async/ctrl/syac(vme(0),0)' /dev/tty34 128.222.3.113 23 telnetin
This example configures /dev/tty34 to accept connections from
128.222.3.113 at port 23 using a telnet protocol. An error is
generated if the specified device does not refer to a VTC or if the
specified tty(s) are not controlled by the specified VTC.
vtc_ttyaddrs '/dev/async/ctrl/spac(pci(0),F,0)' /dev/tty265 128.222.8.87 513 rlogin
This example configures /dev/tty265 to accept connections from
128.222.8.87 at port 513 using an rlogin protocol. An error is
generated if the specified device does not refer to a PTC or if the
specified tty(s) are not controlled by the specified PTC.
FILES
/etc/tcload/vtc.addrs VTC/PTC configuration file
DIAGNOSTICS
Exit status is 0 for success, non-zero otherwise.
SEE ALSO
tcload(1M), vtc_routes(1M), inet(3N), vtc.addrs(4M),
admfailovervtc(1M), syac(7), chk.devlink(1M), devlinktab(4M),
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)