ULTRIX Remote Console

Remote Console Capabilities

The console carrier requester command, ccr, sets up a logical connection between your ULTRIX node and the console carrier server on a remote node. The ccr command enables a terminal to act as the console for a remote unattended node. For example, your terminal can act as the console for the DECserver 100 terminal server and its resident software. You can use the ccr command 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 ccr Command

When you use the ccr command, the remote console carrier server is in one of these states:

• Loaded and unreserved
• Loaded and reserved
• Not loaded

If the console carrier server is loaded and unreserved, issuing the ccr command reserves it, and this message appears on your terminal:

ccr: Remote console reserved

If the console carrier server is loaded and reserved by another user, the following message appears on your terminal:

ccr: Remote console already in use

If the console carrier server is not loaded, the ccr command loads the server. To load a server, an ULTRIX node must have the console carrier server image file and its loader file present in the directory /usr/lib/dnet. When the server is loaded, the ccr command attempts to reserve the console and to proceed as previously described.

Requirements of the ccr Command

To use the ccr command, these requirements must be met:

• The host node (your ULTRIX node) and the remote node must be on the same Ethernet.
• The console carrier server image must be located in /usr/lib/dnet on the ULTRIX node.
• The node data base must contain these definitions, or they must be specified in the ccr command line:
  • The service circuit to the target node
  • The Ethernet hardware address of the target node
  • The service password needed to gain access to the target node

You can define an entry in the node data base with the addnode command.