EDNS/COMMANDS Aegis EDNS/COMMANDS
NAME
edns/commands - Summary of edns Commands.
DESCRIPTION
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.
addr[ep] 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.
del[ete] 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.
delr[ep] 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.
rep[lace] 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.