1 – clerk
show [node node-id] dns clerk attribute [,attribute...]
all
all characteristics
all counters
all status
You can also enter this command using the dns$control utility.
You must have the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Examples:
show dns clerk all
show dns clerk default namespace
1.1 – characteristics
o clerk timeout
Default: 60 seconds
Specifies the default timeout of client interface calls. If no
response is received in the specified time, an error message will
be generated.
o default namespace
Contains the name of the clerk's default namespace.
o solicit holddown
Default: 15 seconds
Specifies the time (in seconds) to wait after initialization before
soliciting advertisements from servers.
o UID
Uniquely identifies the entity.
o version
Specifies the version of the DECdns architecture implemented by
this clerk.
1.2 – counters
o athentication failures
Specifies the number of times a requesting principal failed
authentication procedures.
o cache bypasses
Specifies the number of requests to read attributes for which the
clerk was specifically directed by the requesting application to
bypass its own cache. Instead, a server is contacted to get the
requested information. This counter does not account for requests
that the clerk is unable to satisfy from the cache or for requests
to look up names or enumerate the contents of directories.
o cache hits
Specifies the total number of read requests directed to this clerk
that were satisfied entirely by the information contained in its
own cache. This figure accounts only for requests to read attribute
values and does not include requests to look up names or enumerate
the contents of directories.
o creation time
Specifies the time at which this entity was created.
o incompatible protocol errors
Specifies the number of times this clerk received a response to
one of its own requests from a server running a protocol version of
DECdns software that was incompatible with the protocol version of
DECdns software the clerk was running. Clerk requests directed to
servers running incompatible protocol versions do not complete.
o miscellaneous operations
Specifies the number of operations other than read and write
(that is, skulks, enumerating contents of directories, and so on)
performed by this clerk.
o read operations
Specifies the number of lookup operations performed by this clerk.
This counter accounts only for requests to read attributes and does
not include name lookups or enumerations of multiple names.
o write operations
Specifies how many requests to modify data were processed by this
clerk.
1.3 – status
o state
Specifies the state of the DECdns clerk.
Broken The DECdns clerk has a fatal error condition.
Initial The DECdns clerk is in the process of initializing.
Off The DECdns clerk is not available.
On The DECdns clerk is running and available.
Shut The DECdns clerk is in the process of an orderly
shutdown.
1.4 – known_namespace
show [node node-id] dns clerk -
known namespace namespace-ident attribute [,attribute...]
all
all characteristics
all counters
all identifiers
all status
You can use either the name or nscts in this command to
specify the namespace-ident:
name The name of the namespace. The name argument may
be different from the nickname if the nickname is
ambiguous. The name can contain wildcard character
"*".
nscts The value of the namespace creation timestamp
(NSCTS) assigned to the specified namespace when
it was created. The format is 14 pairs of hex
digits (xx-xx).
You can also enter this command using the dns$control utility.
You must have the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Examples:
show dns clerk known namespace * ! Displays the identifiers
! (both name and NSCTS) of
! all known namespace
! subentities of the local
! dns clerk.
show node true dns clerk - ! Displays all the known
known namespace * all ! namespace information for
! the dns clerk on node true.
show dns clerk known namespace *, - ! Displays the names of all
with ambiguous=true ! namespaces known to the
! local dns clerk which
! share the same nickname.
1.4.1 – characteristics
o UID
Unique identifier for the entity.
1.4.2 – counters
o creation time
Specifies the time at which the clerk added this known namespace to
its cache.
1.4.3 – identifiers
o name
Specifies an external, human-readable name by which the namespace
can be identified. If the namespace nickname is unique, the Name
is the same as the Nickname. Otherwise, the Name is generated by
appending _n to the nickname for some value of n that makes it
unique. The Ambiguous attribute is then set true for the known
namespace.
o NSCTS
Specifies the creation timestamp of the namespace.
1.4.4 – status
o ambiguous
Indicates whether the nickname for this namespace is ambiguous;
that is, more than one namespace known to this clerk has the same
nickname. If true, the namespace nickname is ambiguous. If false,
the namespace nickname is unique.
o explicit creation
Specifies whether the namespace was created by a create command.
If false, the namespace was created by the clerk itself.
o nickname
The name given to the namespace when it was created.
1.5 – manual_nameserver
show [node node-id] dns clerk -
manual nameserver name attribute [,attribute...]
all
all characteristics
all counters
all identifiers
all status
Displays the knowledge in the clerk's cache about a server that
exists across a wide area network (WAN).
You can also enter this command using the dns$control utility.
You must have the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Examples:
show dns clerk manual nameserver * all
show dns clerk manual nameserver DEC towers
1.5.1 – characteristics
o towers
Specifes the address(s) of the server that this entity represents.
o UID
Unique identifier for the entity.
1.5.2 – counters
o creation time
Specifies the time at which the clerk created knowledge of this
server in its cache.
o successful solicits
The number of times the clerk made a successful solicit connection
to the server and received clearinghouse advertisement data back.
o failed solicits
The number of times solicitation of clearinghouse advertisement
data from the nameserver failed.
1.5.3 – identifier
o name
Specifies an external, human-readable name by which the
nameserver can be identified.
1.5.4 – status
o last solicit
Indicates the time at which the clerk last tried to solicit this
nameserver.
1.6 – remote_clearinghouse
show [node node-id] dns clerk -
remote clearinghouse clearinghouse-name attribute [,attribute...]
all
all characteristics
all counters
all identifiers
all status
Displays current information about the specified remote
clearinghouse. The clearinghouse-name can be a specific
clearinghouse name or a complete directory specification followed
by a wildcard template for matching simple names of clearinghouses.
You can also enter this command using the dns$control utility.
You must have the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Example:
show dns clerk remote clearinghouse .paris2_ch all
1.6.1 – characteristics
o UID
Identifies the remote clearinghouse entity.
1.6.2 – counters
o creation time
Specifies the time at which this entity was created.
o miscellaneous operations
Specifies the number of operations other than read and write
(that is, skulks, new epochs, and so on) performed by this clerk
on the remote clearinghouse.
o read operations
Specifies the number of lookup operations of any sort performed
by the clerk on the remote clearinghouse.
o write operations
Specifies the number of write operations performed by this clerk
on the remote clearinghouse.
1.6.3 – identifiers
o CTS
Indicates the creation timestamp (CTS) of this entity.
o name
Specifies the full name of the clearinghouse.
1.6.4 – status
o explicit creation
Specifies whether the namespace was created by a create
command.
o towers
Specifes the address(s) of the clearinghouse that this
entity represents.
2 – server
show [node node-id] dns server attribute [,attribute...]
all [characteristics]
all characteristics
all counters
all status
You can also enter this command using the dns$control utility.
You must have the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Examples:
show dns server all
2.1 – characteristics
o future skew
Specifies the maximum amount of time that a timestamp can vary from
local system time at the server node. This characteristic ensures
data consistency.
o maximum protocol version
Specifies the maximum version of the DECdns clerk/server protocol
that this particular DECdns server supports.
o minimum protocol version
Specifies the minimum version of the DECdns clerk/server protocol
that this particular DECdns server supports.
o UID
Uniquely identifies the entity.
o version
Specifies the version of the architecture implemented by this
server.
2.2 – counters
o authentication failures
Specifies the number of times a requesting principal failed
authentication procedures.
o child pointer update failures
Specifies the number of times the server background process was
unable to contact all the clearinghouses where a replica of a
particular child directory's parent directory is stored, and was
therefore unable to apply the child updates that have occurred
since the last skulk. This counter increases by one at each
occurrence of the Cannot Update Child Pointer event.
o creation time
Specifies the time when the DECdns server entity was created.
o crucial replica removals backed out
Specifies the number of times a user attempted (from this server)
to remove a replica that is crucial to the connectivity of a
directory hierarchy. The server background process prevents users
from accidentally disconnecting lower-level directories from
higher-level directories. When it detects an attempt to remove a
crucial replica, it will not execute the command to do so. This
counter increases by one at each occurrence of the Crucial
Replica event.
o incompatible protocol errors
Accounts for the total number of requests received by this server
from a clerk running an incompatible protocol version. A server can
communicate with any clerk running the same protocol version, or
the version previous to the one it is running. This counter increases
by one at each occurrence of the Incompatible Request event.
o possible cycles
Specifies the number of times this server followed a chain and
encountered an entry already in the chain. For example, a soft link
is created that points to a series of links that eventually point
back to the first link, or a group which is a member of itself.
This counter increases by one at occurrence of the Possible Cycles
event.
o read accesses
Specifies the number of read operations directed to this DECdns
server.
o security failures
Specifies the number of times the Security Failures event was
generated. This counter is increased whenever a DECdns server has
insufficient access rights to a directory or object to perform
either a client-requested action or a background operation.
o skulks completed
Specifies the number of skulks that were successfully completed by
this DECdns server.
o Skulks Initiated
Specifies the number of skulks that were initiated by this DECdns
server.
o times loopup paths broken
Specifies the number of broken connections between clearinghouses
on this server and clearinghouses closer to the root. Incoming
requests to this server that require a downward lookup in the
directory hierarchy may still succeed, but requests requiring
lookup in directories closer to the root will fail. This counter
increases by one at each occurrence of the Broken Lookup Paths event.
o write accesses
Specifies the number of write operations to this DECdns server.
2.3 – status
o state
Specifies the state of the DECdns server.
Broken The server has a fatal error condition.
Initial The server is initializing.
Off The server is not available.
On The server is running and available.
Shut The server is undergoing an orderly shutdown.
2.4 – clearinghouse
show [node node-id] dns server -
clearinghouse clearinghouse-name attribute [,attribute...]
all
all characteristics
all counters
all identifiers
all status
Displays current information about the specified clearinghouse.
The clearinghouse-name can be a specific clearinghouse name or
a complete directory specification followed by a wildcard
template for matching simple names of clearinghouses.
You can also enter this command using the dns$control utility.
You need read access to the clearinghouse to display a list of
known attributes or the value of an attribute. You must have
the NET$EXAMINE rights identifier on a OpenVMS system.
No special privileges are required on a Tru64 Unix system.
Examples:
show dns server clearinghouse .paris2_ch all
show dns server clearinghouse *
2.4.1 – characteristic
o CTS
Indicates the creation timestamp (CTS) of this clearinghouse.
o UID
Uniquely identifies this entity.
2.4.2 – counters
o creation time
Specifies the time when the clearinghouse entity was created.
o data corruptions
Specifies the number of times that the Data Corruption event was
generated.
o disable counts
Specifies the number of times that the clearinghouse was disabled
since it was last started.
o enable counts
Specifies the number of times that the clearinghouse was enabled
since it was last started.
o read accesses
Specifies the number of read operations directed to this
clearinghouse.
o references returned
Specifies the number of requests directed to this clearinghouse
that resulted in the return of a partial answer instead of
satisfying the client's request.
o skulk failures
Specifies the number of times that a skulk of a directory,
initiated from this clearinghouse, failed to complete --
usually because one of the replicas in the replica set was
unreachable.
o times clearinhouse entry missing
Specifies the number of times the Clearinghouse Entry Missing
event was generated.
o times root not reachable
Specifies the number of times the Root Lost event was generated.
o upgrades not possible
Specifies the number of times that the clearinghouse tried to
upgrade a directory and failed.
o write accesses
Specifies the number of write operations directed to this
clearinghouse.
2.4.3 – identifiers
o name
Specifies the full name of the clearinghouse.
2.4.4 – status
o state
Specifies the state of the clearinghouse.
Broken The clearinghouse has a fatal error condition.
Initial The clearinghouse is in the process of initializing.
Off The clearinghouse is not available.
On The clearinghouse is running and available.
Shut The clearinghouse is in the process of an orderly
shutdown.