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. The node 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 ccr is the console carrier requester, which sets up a logical connection between your ULTRIX node and the console carrier server on a remote node. The 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.

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.

When you are attempting to use ccr, the remote console carrier server can be in one of the following states:

Loaded and unreserved

Loaded and reserved by another user

Not loaded

If the console carrier  server  is  loaded  and  unreserved, ccr reserves it, and the following message is displayed at your terminal:

ccr: Remote console reserved

If the console carrier server is loaded and  reserved by another user, the following diagnostic message is displayed at your terminal:

ccr: Remote console already in use

If the console carrier server is not loaded, ccr loads the  server.  In order to load the server, your ULTRIX node must have the console carrier server image file, plutocc.sys, and its loader file, plutowl.sys, present in the directory, /usr/lib/dnet. Once the server is loaded, ccr attempts to reserve the console and to proceed as previously described.

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. 

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 following special characters are used by ccr:

<CTRL/B> Operates as a break command to get the attention of the console on-line debugging tool (odt). 

<CTRL/D> Exits from console carrier mode and terminates ccr.

OPTIONS

−c Uses the specified service and device number (UBA-n or QNA-n) as the circuit 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 and password (next arguments) in accessing the target node. 

EXAMPLE

In the following sample session, you invoke ccr to use the on-line debugging tool, odt to examine locations in memory of node Dallas.  After invoking ccr, You type <CTRL/B> to invoke odt.  The system then displays the current program counter and the at sign prompt, (@).  At this point, you can enter commands as if you were physically located at the console of node Dallas.  ccr commands are transmitted by the requester to the server, and the appropriate responses are transmitted by the server to the requester and displayed on your terminal.

To examine a register, enter the dollar sign ($) followed by the register number and a slash (/).  To examine a location, enter the address of the location  and a slash.  The system then displays the contents on the same line. Enter <LF> to view the next register or location, or enter <RET> to return to the @ prompt. When you want to exit odt, enter p (proceed). You must then issue a <CTRL/D> to return to the ULTRIX system prompt. 

# /etc/ccr dallas <RET>
ccr: Remote console reserved
<CTRL/B>
002160
@$0/000000 <LF>
R1/005621 <LF>
R2/112000 <LF>
R3/000000 <LF>
R4/000001 <LF>
R5/000000 <RET>
@100/016122 <LF>
000102/000340 <LF>
000104/001614 <LF>
000106/000341 <RET>
@p <RET>
<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

ccr 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

ccr 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