vtc_routes(1M) — DG/UX R4.11MU05



vtc_routes(1M)                 DG/UX R4.11MU05                vtc_routes(1M)


NAME
       vtcroutes - change a VTC's/PTC's routing information

SYNOPSIS
       vtcroutes [-a] [ -d dir ] [ -f file ] device

   where:
       device    The full device node pathname of a VTC/PTC.

DESCRIPTION
       The vtcroutes command changes the routing information used by the
       specified VMEbus/PCI bus Terminal Controller (VTC/PTC).  The old
       routing information is flushed from the board unless the -a option is
       specified.  The new information for the VTC/PTC board is taken from a
       routing file as specified in /etc/tcload/vtc.addrs unless either the
       -f or the -d option is specified.

       Note that if the specified VTC/PTC is configured for failover, none
       of the modifications made to the primary board's routing information
       using the -f or the -d option will be incorporated into its backup
       board's routing information when failover occurs. Using VTC/PTC's for
       failover requires the Failover package or DG/UX Cluster Software
       product.

   Options
       -a     Add the new routing information to that which is already in
              use by the board.  By default, the board's current routing
              information is flushed before the new routing information is
              communicated to the board.

       -f file
              Read the new routing information from the specified file
              instead of from the one specified in vtc.addrs(4M).  Its
              format should be identical to that of the gateways(4M) file.
              If default is specified for the file name, then the routing
              information currently in use by the host computer will be
              communicated to the board.  This option should be avoided for
              VTCs/PTCs that are part of a failover configuration.

       -d dir Look in the specified alternate directory for the
              vtc.addrs(4M) file.  This option should be avoided for
              VTCs/PTCs that are part of a failover configuration.

EXAMPLES
       vtcroutes -a '/dev/async/ctrl/syac(vme(0),0)'

       This example will read the routing file specified in vtc.addrs(4M)
       and add the routing information found there to the specified VTC.
       The board's current routing information will not be flushed.

       vtcroutes -f default '/dev/async/ctrl/syac(vme(0),0)'

       This example will communicate the routing information in use by the
       host computer to the specified VTC.  The board's current routing
       information will be flushed before the new routing information is
       communicated to the board.

       vtcroutes -f /etc/testfile '/dev/async/ctrl/spac(pci(0),F,0)'

       This example will read the file /etc/testfile and communicate the
       routing information found there to the specified PTC.  The current
       routing information will be flushed before communicating the new
       routing information to the board.

       vtcroutes -d /tmp/test '/dev/async/ctrl/spac(pci(0),F,0)'

       This example will read the routing file specified in
       /tmp/test/vtc.addrs and communicate it to the specified PTC.  The
       board's current routing information will be flushed before the new
       routing information is communicated to the board.

FILES
       /etc/tcload/vtc.addrs  VTC/PTC configuration file

DIAGNOSTICS
       Exit status is 0 for success, nonzero otherwise.

SEE ALSO
       tcload(1M), vtcttyaddrs(1M), gateways(4M), vtc.addrs(4M),
       admfailovervtc(1M), syac(7).


Licensed material--property of copyright holder(s)
Museum

Related Articles
