NAME

ccr − remote console carrier requester

SYNTAX

ccr [ options ] node

DESCRIPTION

The ccr command establishes a logical connection between your ULTRIX system and the console carrier server on a remote system. ccr 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 ccr 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 ccr are as follows:

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

If your server product is a Digital Ethernet Communiscations Server (DECSA), the console carrier server image (plutocc.sys) and its loader file (plutowl.sys) must be located in /usr/lib/dnet 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 ccr.

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. 

EXAMPLE

# /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 ccr.

DIAGNOSTICS

The ccr command can return the following diagnostic messages:

ccr: Remote console reserved

The ccr 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 ccr. (You must be a superuser.)

ccr: Hardware address required

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

ccr: No node entry in database

ccr 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 addnode command.)

FILES

/usr/lib/dnet/plutocc.sys (console carrier server image)
/usr/lib/dnet/plutowl.sys (console carrier server loader)

SEE ALSO

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

Maintenance