addnode(8) — Maintenance
Name
addnode − add or change an entry in the MOP client database
Syntax
/usr/sbin/addnode node [ options ]
Description
The addnode command adds a new entry to the MOP client database (/var/dna/mop_client_db) or modifies an existing entry. The addnode command defines the information that is necessary for your Digital UNIX node to be capable of down-line loading and up-line dumping a particular target node. The node address is the Phase IV address of the target node. If the target node is a Phase IV DECnet node, then the node address is mandatory and the node name is optional. However, if the target node is a non-DECnet node, for example, a terminal server, you should specify only the node name and omit the node address.
If you do not specify an absolute pathname for secondary load, tertiary load, system load, diagnostic load, or dump file, the default paths /usr/lib/mop and /usr/lib/dnet, are used during the load or dump process.
A Phase IV node address has the format a.n for multiarea networks, where a is the network area number (a decimal integer in the range of 1 to 63) and n is the node number (a decimal integer in the range of 1 to 1023).
The node name is the node name of the target node.
If the target node is a DECnet node, the node name is optional. However, if the target node is a non-DECnet node, for example, a terminal server, the node name is mandatory (and the node address should be ignored).
A node name can be from 1 to 6 alphanumeric characters, including at least 1 alphabetic character.
Options
−A Uses the specified host address (next argument) as that of the target node.
−D Creates an up-line memory dump of the target node in the specified file (next argument).
−N Uses the specified name (next argument) as that of the target node.
−c Uses the specified service and device number (UBA-n or QNA-n) as the circuit to the target node.
−d Sends the specified diagnostic load image (next argument) to the target node.
−h Uses the specified address (next argument) as the Ethernet address of the target node.
−l Sends the specified system load image (next argument) to the target node.
−p Uses the specified service and password (next arguments) in accessing the target node.
−s Sends the specified secondary load file (next argument) to the target node.
−t Sends the specified tertiary load file (next argument) to the target node.
Examples
% /usr/sbin/addnode mynode −h aa−00−03−00−01−19 \ <RET>
-s /usr/download/secondary \ <RET>
-t /usr/download/tertiary \ <RET>
-l system <RET>
This command adds the non-DECnet, node mynode, to the MOP client database, which has the Ethernet physical address aa-00-03-00-01-19. This command also specifies the file names for the secondary loader, the tertiary loader, and the system loader. Note that a path name is not specified for the system loader; consequently, the loader uses the default path /usr/lib/mop when searching for that file.
# /usr/sbin/addnode 44.71 −h aa−00−03−00−01−20 <RET>
This command adds the DECnet node 44.71 to the MOP client database, which has the Ethernet physical address aa-00-03-00-01-20.
Files
/var/dna/mop_client_db (MOP client database)
/var/dna/mop_circuit_db (MOP circuit database)
/var/dna/mop_ccrcircuit_db (MOP circuit / System device mapping database)
/usr/lib/mop (Primary default pathname)
/usr/lib/dnet (Secondary default pathname)
See Also
ccr(8), getnode(8), load(8), mop_mom(8), remnode(8), trigger(8)