Name

ccr − Remote console carrier requester

Syntax

ccr [ options ] node

Description

The ccr command establishes a logical connection between your Digital UNIX 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 network server and its resident software. The node is the name or address of the target system. 

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 Digital UNIX node) and the remote node must be on the same Ethernet. 

•The console requestor has to be enabled on the circuit over which ccr is performed.  Issue ncl> show mop circuit circuit_name func to verify that the function is enabled. 

<CTRL/B> sends a break condition to the server

<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. 

−v Verbose mode.  Prints informational messages during the connection establishment process. 

−e Uses Ethernet format packets only.  The default is to try 802.3 packets first, and if that fails, to try Ethernet format packets. 

−8 Uses 802.3 format packets only.  The default is to try 802.3 packets first, and if that fails, to try Ethernet format packets. 

Restrictions

You must have superuser privileges to run
ccr. When using NCL to specify the circuit name, use the DECnet name (for example, circuit-1).  When specifying the circuit on the command line with -c, use the hardware device name (for example, xna-0).

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: Superuser privileges required
You do not have the necessary privileges to run ccr. (You must be a superuser.)

ccr: No valid address available
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 address must be defined either in the ccr command line, or in its mop database entry.  (The mop database entries are defined with the addnode command.)

ccr: No entry for node found in database
The ccr 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 mop database.  (mop database entries are defined with the addnode command.)

ccr: No response from target
The ccr command was unable to establish any communication with the target system.

ccr: No valid device available
The ccr command was unable to locate an appropriate device over which a connection would be attempted.  The circuit must be specified on the command line or in the mop database entry of the target, and the mop database entry must have the ccr function enabled.

Example

# /etc/ccr −c ln0 −n dallas <RET>
ccr: Remote console reserved
.
.
.
<CTRL/D>
ccr: Remote console released
#

Files

/var/dna/mop_ccrcircuit_db

See Also

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