trigger(8) [ultrix man page]

trigger(8)						      System Manager's Manual							trigger(8)

Name
       trigger - trigger a target node to request a down-line load

Syntax
       /etc/trigger node [ options ]

Description
       The command triggers the bootstrap mechanism of a target node, causing the target to request a down-line load.  Once a target node is trig-
       gered, it loads itself in whatever manner its primary loader is programmed to operate.  The target node could request a down-line load from
       the host that just triggered it or from another adjacent node, or the target node could load itself from its own mass storage device.

       The  node argument is the name or address of the target node.  A node name consists of from one to six alphanumeric characters.	For single
       networks, a node address consists of a decimal integer (1-1023).  For multiple networks, a node address consist	of  two  decimal  integers
       (n.n), where the first indicates the network number (1-63), and the second indicates the node address (1-1023).

       The  command requires the identification of the service circuit over which the load is performed, the Ethernet hardware address of the tar-
       get node, and the service password needed to gain access to the target.	This information is included in the nodes database entry  for  the
       target node.  A node entry is defined with the command.	For further information, see Alternatively, you can choose not to include a target
       node's service password in the nodes database for security reasons.  You must therefore specify this value in the command line by using the
       -p option.

Options
       -p     Uses the specified service and password (next arguments) in accessing the target node.

Examples
       This command triggers node Bangor to issue a down-line load request:
       # /etc/trigger bangor <RET>

See Also
       mop_mom(8), addnode(8), load(8), remnode(8), getnode(8), ccr(8)
       Guide to Local Area Transport Servers

																	trigger(8)

ccr(8)							      System Manager's Manual							    ccr(8)

Name
       ccr - remote console carrier requester

Syntax
       ccr [ options ] node

Description
       The  command  establishes  a logical connection between your ULTRIX system and the console carrier server on a remote system.  enables your
       terminal to act as the console for a remote unattended system.  For example, your terminal can act as the console for  a  Digital  Ethernet
       Communications Server (DECSA) and its resident software.  The node is the name or address of the target node.  A node name consists of from
       one to six alphanumeric characters.  A node address consist of two decimal integers (n.n), where the first  indicates  the  network  number
       (1-63), and the second indicates the node address (1-1023).

       You  can  use  to  force  a  crash if a server node becomes unresponsive.  To determine how to force a crash, see the documentation for the
       respective server product.

       The requirements for using are as follows:

       o   The host node (that is, your local ULTRIX node) and the remote node must be on the same Ethernet.

       o   If your server product is a DECSA, the console carrier server image (plutocc.sys) and its loader file (plutowl.sys) must be located	in
	   on  your  ULTRIX node. The pluocc.sys and plutowl.sys files are not need, nor is any loading done for other servers.  For more details,
	   see the installation guide for the particular server product.

       <CTRL/D> exits from console carrier mode and terminates

Options
       -c   Uses the specified circuit to connect to the target node.

       -h   Uses the specified address (next argument) as the Ethernet address of the target node.

       -n   Uses the next argument as the target node ID.

       -p   Uses the specified service password (next arguments) in accessing the target node.

Examples
       # /etc/ccr -c qna-0 -n dallas <RET>
       ccr: Remote console reserved
	    .
	    .
	    .
       <CTRL/D>
       ccr: Remote console released
       #

Restrictions
       You must have superuser privileges to run

Diagnostics
       The command can return the following diagnostic messages:

       ccr: Remote console reserved
       The command has successfully connected to the remote console server and your terminal is now capable of acting as a console for the  remote
       node.

       ccr: Remote console released
       Your connection with the remote console server has been terminated and you are no longer in console carrier mode.

       ccr: Remote console already in use
       The remote console server that you are attempting to connect to is already reserved by another user.

       ccr: Permission denied
       You do not have the necessary privileges to run (You must be a superuser.)

       ccr: Hardware address required
       The  command  is unable to locate the hardware address of the remote node to which you are attempting to connect.  A remote node's hardware
       address must be defined either in the command line, or in its nodes database entry.  (Nodes database entries are defined with the command.)

       ccr: No node entry in database
       The command does not recognize the remote node to which you are attempting to connect, since the node-id that you specified is not  defined
       in the nodes database.  (Nodes database entries are defined with the command.)

Files
       Console carrier server image

       Console carrier server loader

See Also
       addnode(8), getnode(8), load(8), remnode(8), trigger(8)
       Guide to Local Transport Servers

																	    ccr(8)