EDNS/COMMANDS -- Summary of EDNS Commands. 86/07/10 Some EDNS commands use node specifications and internet addresses as arguments. If a command accepts a node specification, the syntax line uses the term node_spec. If a command accepts an internet address, the syntax line uses the term [net.]node_id. When a command accepts a node specification, you can provide a node name (if the name is cataloged in the default NS_HELPER database) or you can provide an internet address. When a command accepts an internet address, you must specify a node ID, and in some cases, a network number. Note that the rules for specifying internet addresses with EDNS commands differ slightly from the rules for specifying internet addresses with Shell commands. If the node is on the local ring, the network number is optional. If the node is on a remote ring, the network number is required. When you specify an internet address with an EDNS command, the internet address must begin with an integer. If the address begins with a letter, precede the address with a 0 (e.g. 0D34.1E05). When you issue EDNS commands from a node in a non-zero network, you cannot specify the number 0 to indicate the local ring. For complete information on EDNS command usage, see Administering Your DOMAIN System and Managing DOMAIN Internets. __________________________________________________________________________ SYNTAX FUNCTION (abbreviation shown in uppercase) __________________________________________________________________________ Default options are indicated by "(D)". ADD name [net.]node_id Adds a new node name, and the associated node information, to the default NS_HELPER's copy of the master root directory. After accepting a name, the NS_HELPER propagates the new information to all NS_HELPERs in its replica list. The NS_HELPER accepts a new name only if it does not already exist in the master root directory. If a name already exists, then the NS_HELPER does not accept the entry and EDNS displays an error message. The node you are adding must be connected to the network in order for EDNS to obtain information needed for the database. For a disked node, EDNS obtains the UID for the node entry directory. For a diskless node, EDNS verifies the diskless status and creates a canned UID. ADDRep node_spec Adds a replica to the default NS_HELPER's replica list. The NS_HELPER propagates the new replica's identity to all NS_HELPERs in its replica list. The NS_HELPER accepts a new replica only if the entry does not already exist in the replica list. If an entry already exists, then the NS_HELPER does not accept the entry and EDNS displays an error message. CMP [node_specA] node_specB Compares two NS_HELPER databases and lists names, network numbers, and UIDs that appear in both copies of the master root directory. CMP also lists replicas that appear in both replica lists. If you do not provide a value for node_specA, then EDNS uses the default NS_HELPER database. DELete name Deletes a node name from the default NS_HELPER's copy of the master root directory. The NS_HELPER propagates the delete request to all NS_HELPERs in its replica list. If the name you specify does not exist, EDNS returns an error message and does not accept or propagate the DELETE request. DELRep node_spec Deletes an NS_HELPER from the default NS_HELPER's replica list. The NS_HELPER propagates the delete request to all NS_HELPERs in its replica list, thereby removing the replica from all other replica lists. In addition, DELRep causes the deleted replica to delete its database. The deleted replica stops running after its propagation list has been emptied. If the replica you specify with the DELRep command does not exist in the NS_HELPER's replica list, EDNS returns an error and does not accept or propagate the DELRep request. It is best to wait at least fifteen minutes before restarting a deleted replica. DIFF [node_specA] node_specB Lists the differences between two NS_HELPER databases. The DIFF command shows differences between both copies of the master root directory, and between both replica lists. If you do not provide a value for node_specA, then EDNS uses the default NS_HELPER database. INFO Displays the internet address and status information for the default NS_HELPER. INIT [node_specA] [-FROM node_specB] Initializes an NS_HELPER database. If you do not specify a value for node_specA, then EDNS initializes the default NS_HELPER database. After you initialize an NS_HELPER, it becomes active. That is, the NS_HELPER can communicate with other NS_HELPERs and can respond to naming requests from other nodes. (Before an NS_HELPER is initialized, it will respond only to the INFO, INIT, MERGE_ALL and SHUT commands.) To use the INIT command without the -FROM option, you must use EDNS from a node on the same ring as the NS_HELPER you are initializing. In such a case, EDNS gets a list of all nodes on the local ring, and adds these nodes to the NS_HELPER database that you are initializing. The NS_HELPER propagates the new information to all replicas in its replica list. If you initialize an NS_HELPER that has previously been initialized, the INIT command adds any new node names to the existing database and propagates these names to the NS_HELPERs on its replica list. -FROM node_specB If you specify the -FROM option, EDNS performs a different type of initialization. First, EDNS adds the NS_HELPER on node A (or the default node) to node B's replica list. Then node B propagates the new replica information to all the replicas in its (node B's) replica list. Thus, the other NS_HELPERs will now have node A (or the default NS_HELPER) on their replica lists. Next, EDNS merges all entries from node B's NS_HELPER database into node A's (or the default) database. This merge includes the entries in node B's copy of the master root directory and in node B's replica list. Finally, if node A (or the default node) and node B are on different rings, EDNS also gets a list of all nodes on node A's network and adds these nodes to node A's copy of the master root directory. Then node A's NS_HELPER propagates these names to all the NS_HELPERs on its replica list. When node A and node B are on different rings, you must use EDNS from a node on the same ring as node A. LD [names] [-NODE node_id] Lists root directory entries by name; if [-NET net] names are specified, only those names [-SN|-NSN] are listed. [-T] [-U] [-N] [-IA] [-DTE] -NET net Lists root directory entries with the specified network number; if names are specified, LD lists entries with the specified names, and also lists entries with the specified network number. -NODE node_id Lists entries with specified node ID; if names are also specified, LD lists entries with the specified names and also lists entries with the specified node ID. -SN (D) Lists entries sorted by name. -NSN Suppresses name sorting. The following options specify the special information to be displayed with each entry that is listed: -T Displays entry type. -U Displays uid. -N Displays node_id. -IA Displays internet address. -DTE Displays date/time this entry was made to the directory and the node_id of the replica where this entry was made. LR [-CLOCKS] Displays list of replicas in the network. -CLOCKS Displays each replica's current clock date/time and checks for any replicas whose clocks are skewed. MERGE [node_specA] -FROM node_specB Merges all entries in the NS_HELPER database on node B into the NS_HELPER database on node A; node B's database remains unchanged. If you do not specify a value for node A, then EDNS merges node B's database into the default NS_HELPER database. If node A's database contains an entry with the same name as an entry being merged from node B, then the entry with the latest time-stamp is saved in node A's database. (A timestamp is the time an entry receives when it is first added to an NS_HELPER database. An entry keeps its original timestamp when it is propagated to other NS_HELPERs.) The MERGE command affects only the database on node A; node A does not propagate any entries it obtains from the merge. MERGE_ALL [node_spec] Performs a global merge using the NS_HELPER at the node you specify as the base for the merge. If you omit the node_spec, EDNS uses the default NS_HELPER. To do a global merge, EDNS merges each NS_HELPER database (in the specified NS_HELPER's replica list) into the specified NS_HELPER's database. Then, EDNS merges the updated database back out to each replica. Note that EDNS merges both the replica lists and the copies of the master root directory. If a database contains an entry with the same name as an entry being merged, then the entry with the latest timestamp is saved. (A timestamp is the time an entry receives when it is first added to an NS_HELPER database. An entry keeps its original timestamp when it is propagated to other NS_HELPERs.) An NS_HELPER must be listed in the base NS_HELPER's replica list to be included in a global merge. The NS_HELPERs in the replica list may be uninitialized. If an NS_HELPER is not already initialized, the MERGE_ALL command will initialize its database and allow the NS_HELPER to be active. QUIT Terminates the current EDNS session. REPlace name [net.]node_id Changes the internet address and UID associated with a name in the default NS_HELPER's copy of the master root directory. The NS_HELPER propagates the new information to all NS_HELPERs in its replica list. Use this command after running the utilities CHUVOL, or INVOL, or replacing a disk. The node you are replacing must be connected to the network in order for the NS_HELPER to obtain information needed for the database. For a disked node, EDNS obtains the UID for the node entry directory. For a diskless node, EDNS verifies the diskless status and creates a canned UID. SET [node_spec] Sets the default to the NS_HELPER running on the node you specify. Subsequent EDNS commands will be directed to this NS_HELPER, unless you specify a different NS_HELPER in the command. If you use the SET command and omit a node specification, EDNS will select an active NS_HELPER (with an initialized database) to be the default. SHUT node_spec Shuts down the NS_HELPER replica on the node you specify. This command causes the specified replica to delete its database and stop running immediately. The shutdown replica is not removed from any replica lists. UPDATE [node_spec] Updates the NS_HELPER database on the node specified. If you do not specify a node, then EDNS updates the default NS_HELPER database. An NS_HELPER must be initialized before it can be updated. EDNS gets a list of all nodes on the EDNS node's local ring. It adds nodes which are not already in the NS_HELPER database and replaces node information (such as internet address and entry directory UID) which has changed. NS_HELPER propagates new information to all replicas in its replica list.