![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Arguments:
| dump destination | Destination that the dump operation used. | |
| dump reason | Reason for the dump failure. | |
| directive | In response to a dump command. | |
| failure | In response to a device failure while in the running state. | |
| failure reason | Reason why the dump failed. The values of this argument are device specific. | |
Arguments:
| failure reason | Reason for the load failure. The values of this argument are device dependent. | |
| load reason | Reason for the load operation. | |
| directive | In response to a load command. | |
| dump | After completion of a dump operation. | |
| failure | After a device failure. | |
| initial | Initial loading of the device at device unit enable when auto load is true. | |
| load source | Source used to retrieve the microcode during the load operation. | |
Arguments:
| firmware identifier | Firmware identifier of the loaded microcode. | |
| load reason | Reason for the load operation. | |
| directive | In response to a load command. | |
| dump | After completion of a dump operation. | |
| failure | After a device failure. | |
| initial | Initial loading of the device at device unit enable when auto load is true. | |
| load source | Source used to retrieve the microcode during the load operation. | |
dump failure
The dump operation failed.illegal dump destination
The value of the dump destination characteristic is not a valid file specification. Check the value of the character, correct as necessary, and reissue the dump command.For load:
illegal load source
The value of the load source characteristic is not a valid file specification. Check the value of the characteristic, correct as necessary, and reissue the load command.load failure
The load operation failed.
The Digital Distributed Name Service (DECdns) is a networkwide service that makes it possible to use network resources without having to know their physical location. DECdns has two NCL modules: DNS Server and DNS Clerk.
The DNS Server module maintains a distributed database for use by the client modules on other nodes of the network. The responsibilities of this entity include responding to lookup requests, managing the namespace, and updating object entries.
Figure 7-1 shows the hierarchical relationship of entities that constitute the DNS Server module.
Figure 7-1 Hierarchy of DNS Server Module Entities
Note
You can manage the DECdns entities from either NCL or the DECdns Control Program (DNSCP). The commands are the same for both interfaces and are documented in the DECnet-Plus DECdns Management guide. Online help for DECdns is available from DNSCP only.
Figure 7-2 shows the hierarchical relationship of entities that constitute the DNS Clerk module.
Figure 7-2 Hierarchy of DNS Clerk Module Entities
Note
You can manage the DECdns entities from either NCL or the DECdns Control Program (DNSCP). The commands are the same for both interfaces and are documented in the DECnet-Plus DECdns Management guide. Online help for DECdns is available from DNSCP only.
This section alphabetically lists and describes all events for the dns entity.
DECdns uses the DECnet event logger to record significant events for DECdns clerks, servers, and clearinghouses. By default, all DECdns events are turned on by the DECnet configuration program.
clerk event
The clerk received a response from a server running an incompatible or unsupported version (major version number) of the DECdns clerk/server protocol. A clerk can only communicate with other clerks or servers that are running the same version as (or one version earlier than) the protocol version that the clerk itself is running. This event increments the Incompatible Protocol Errors clerk counter.
incompatible protocol errorArgument:
version received Specifies the protocol version running on the responding entity. broken lookup paths
The clearinghouse on this server has become disconnected from clearinghouses that contain replicas closer to the root. Incoming requests that require the server to look downward in the hierarchy may still succeed, but requests requiring lookups in directories that exist closer to the root will fail because the parent of the directory does not seem to exist. Without a parent, the directory is cut off from upper levels of the hierarchy. This problem can be caused by either of the following conditions:
- During a directory lookup operation, the account (principal) under which the server is running (nodename.dns$server) was found to have insufficient access to the child pointer of the target directory. (A directory's child pointer exists in its parent directory.) Access to a directory's child pointer is inherited from the access assigned to the directory's parent directory. To correct the problem, make sure the nodename.dns$server principal has write access to the parent directory.
- The child pointer to the disconnected directory was accidentally deleted from its parent directory. See the problem-solving appendix in the DECnet-Plus DECdns Management guide for complete information on how to restore a lost child pointer.
This event increments the Times Lookup Paths Broken server counter.
Argument:
orphan Specifies the full name of the directory being accessed by the server at the time the disconnection was detected. cannot update child pointer
The server was unable to update a parent directory's Child Pointer attribute (with update information stored in the child directory's Parent Pointer attribute). This happens when the server is unable to contact all the clearinghouses that store a replica of the directory's parent directory and, therefore, zex cannot apply updates that occurred since the last skulk. One or more replicas of the parent directory may be unreachable temporarily. This event increments the Child Pointer Update Failures server counter.This event may also be generated if the server was found to have insufficient access to perform the update. In this case, the Security Failure server event is also logged.
Arguments:
directory Specifies the full name of the directory for which the server's parent pointer tracking failed. reason Specifies the reason for the update failure. Reasons are expressed as DECdns or operating system error messages. If the Security Failure or Broken Lookup Paths events are also logged, take action on those events first. If DECdns only logs the Cannot Update Child Pointer event, then one or more of the clearinghouses that stores a replica of the directory being updated could not be contacted. This condition will be corrected when the server's ability to communicate with the clearinghouses is restored.
crucial replica
An attempt was made, from this server, to delete a replica that is crucial to the preservation of the clearinghouse rules. The clearinghouse rules require every directory to store at least one of its replicas in a clearinghouse that is named closer to the root than is the directory itself. (See the appendix describing clearinghouse rules in the DECnet-Plus DECdns Management guide for complete information on the clearinghouse rules.) When the background process on the server detects that a crucial replica was deleted, it reverses the delete replica operation and returns the replica to the on state.This event is raised as a result of two separate delete replica operations. Although each operation may be valid, the combination of the two operations is not. The server background process examines the combined deletions and reverses the deletion of the replica that will preserve the clearinghouse rules and restore the server's ability to communicate with the root directory. This event increments the Crucial Replica Removals Backed Out server counter.
Arguments:
directory Specifies the full name of the directory whose replica was being deleted when the server background process detected the failure. clearinghouse Specifies the full name of the clearinghouse that stores the crucial replica whose removal caused the failure. If you must remove a crucial replica from a clearinghouse, first create another replica of the directory in some other clearinghouse whose name is closer to the root directory than is the directory itself.
incompatible protocol error
The server received a request from a clerk running an incompatible or unsupported version (major version number) of the DECdns clerk/server protocol. A server can only communicate with clerks that are running the same version (or one version previous to) the protocol version that the server itself is running. This event increments the Incompatible Protocol Errors server counter.Arguments:
version received Specifies the protocol version running on the requesting entity. source Specifies the full name of the node entity containing the clerk that generated the incompatible request. possible cycle
The server detected a possible soft link loop or group loop while trying to resolve a name or group. This event increments the Possible Cycles server counter.Argument:
name Specifies the full name being resolved when the loop was detected. See the problem-solving appendix in the DECnet-Plus DECdns Management guide for information on how to break a soft link loop or group loop.
security failure
The server encountered an unexpected security failure while trying to perform an operation on behalf of a user or application, or while trying to perform an internal background operation. For example, the server, on behalf of a requesting application, was unable to create an object entry in a directory because the account under which the application was running (principal) did not have write access to the directory. This event increments the Security Failures server counter.Arguments:
accessing Specifies the full name being accessed when the security failure was detected. source Specifies the full name of the accessing principal. time went backward
The time on this server system appears to have gone backward.Argument:
time Specifies the time after which you must reset the system clock to correct the problem. This problem can occur when a user mistakenly sets the system time ahead to adjust for normal clock drift or for daylight savings time; then, after realizing an error was made, the user sets the system clock back again. All DECdns transactions that occur while a server's system clock is set ahead appear, to DECdns, to have occurred in the future. DECdns is unable carry out updates and other background operations on names that bear timestamps specifying future times.
If the future timestamps are only a few minutes or hours in the future, you can simply wait until the date and time expressed in the timestamps has passed. At that time, DECdns will continue to synchronize update information in the normal manner.
If the timestamps are so far in the future that you would need to wait for days or weeks before resuming normal operations, you must repair the damage manually.
clearinghouse created
The clearinghouse was created by use of the create dns server clearinghouse command.clearinghouse deleted
The clearinghouse was deleted by use of the delete dns server clearinghouse command.clearinghouse disabled
The clearinghouse was disabled by use of the disable dns server clearinghouse command. This event increments the Disable Counts clearinghouse counter.Argument:
how Specifies how the clearinghouse was disabled: graceful or abort. clearinghouse enabled
The clearinghouse was enabled by use of the enable clearinghouse command. This event increments the Enable Counts clearinghouse counter.clearinghouse entry missing
The clearinghouse object entry that represents this clearinghouse in the name-space has disappeared, possibly because of accidental deletion. This event increments the Times Clearinghouse Entry Missing clearinghouse counter.See the problem-solving appendix in the DECnet-Plus DECdns Management guide for instructions on how to restore a deleted clearinghouse object entry.
data corruption
The clearinghouse data files may have become corrupted. This event increments the Data Corruptions clearinghouse counter.Argument:
reason Specifies why the integrity of the clearinghouse data is suspect. Reasons are expressed as DECdns or operating system error messages. Check the appropriate DECdns error messages in the DECnet-Plus DECdns Management error messages appendix and take the indicated user actions. See the problem-solving appendix in the DECnet-Plus DECdns Management guide for instructions on how to recover a corrupted clearinghouse.
root lost
The namespace tree has become disconnected; the root directory cannot be found starting from this clearinghouse. This condition can occur when the clearinghouse does not store at least one directory with both of the following properties:
- The directory's name must be closer to the root (contain fewer simple names) than the name of the clearinghouse itself.
- The directory must have its DNS$InCHName attribute set to true.
This event increments the Times Root Not Reachable clearinghouse counter.
To recover from this problem, use the create replica command to create (in this clearinghouse) a replica of some directory that satisfies the preceding requirements. The root directory is guaranteed to satisfy these requirements.
skulk failed
A skulk (initiated by this server) of some directory that stores a replica on this clearinghouse has failed. This event increments the Skulk Failures clearinghouse counter.Arguments:
directory Specifies the full name of the directory being skulked. reason Specifies why the skulk failed. Reasons are expressed as DECdns or operating system error messages. Check the appropriate DECdns error messages in the DECnet-Plus DECdns Management error messages appendix and take the indicated user actions.
upgrade not possible
The server where this clearinghouse resides was unable to upgrade a directory during a skulk of that directory. This event increments the Upgrades Not Possible clearinghouse counter.Arguments:
directory Specifies the full name of the directory that could not be upgraded. why Specifies why the attempted upgrade failed. Reasons are expressed as DECdns or operating system error messages. Check the appropriate DECdns error messages in the DECnet-Plus DECdns Management error messages appendix and take the indicated user actions.
The Digital Distributed Time Service (DECdts) is a networkwide time service that enables you to synchronize and manage the system clocks in a distributed network.
Figure 8-1 shows the hierarchical relationship of the entities that constitute the DECdts module.
Figure 8-1 Hierarchy of DECdts Module Entities
This section alphabetically lists and describes all events for the dtss entity.
clock set
This event is generated each time a DECdts process sets its local clock.
Arguments:
| new time | Specifies the corrected clock setting. | |
| old time | Specifies the faulty time before the clock was set. | |
different epoch detected
This event is generated each time the local node receives a time value that has an epoch number different from its own. This event normally occurs after a node's epoch has been changed.
Arguments:
|
local epoch
number |
Specifies the local node's epoch number. | |
| server [id] | Specifies the known servers and their epoch numbers. | |
disable completed
This event is generated each time a disable command is executed to stop DECdts.
enable completed
This event is generated each time an enable command is executed to start DECdts.
epoch change completed
This event is generated each time the epoch is set for the local node.
Arguments:
| new epoch | Specifies the epoch number after the epoch was declared. | |
| old epoch | Specifies the epoch number before the epoch was declared. | |
insufficient resources detected
This event is generated each time the node's virtual memory is full. The event is displayed on all nodes and is usually followed by a system abort.
invalid message detected
This event is generated each time the local node receives a corrupted or incorrect message. Invalid messages are normally retransmitted, but the hexadecimal contents of the invalid message are supplied for troubleshooting.
Arguments:
| message | Specifies the hexadecimal contents of the invalid message. | |
| node [id] | Specifies the full name of the node that generated the invalid message. | |
local time does not intersect
This event is generated each time the time interval of the local node does not intersect with the values received from other servers. If this event is generated frequently, you can decrease the setting for the characteristic synchronization hold down or increase the settings for the characteristics error tolerance or maximum inaccuracy.
Arguments:
| clock set | Specifies whether or not the clock was automatically set to correct the time on the local system. If false, the clock was not set to correct the time on the local system. | |
| computed time | Specifies the intersection of the majority of server times. | |
| local time | Specifies the local time interval that does not intersect with the computed time. | |
no global server
This event is generated at a courier server when it cannot locate a global server.
protocol version mismatch detected
This event is generated each time the DECdts protocol version of a received message does not match the protocol in force at the local node.
Argument:
| node [id] | Specifies the full name of the node that generated the message with the incompatible protocol version. | |
server not responding
This event is generated at a courier server when it attempts to synchronize with the listed global server, but the server does not respond. The event may be caused by a low characteristic setting for wan timeout.
Argument:
| node [id] | Specifies the node name of the server not responding. | |
server time does not intersect
This event is generated each time the local node receives a faulty time value from a server. If continuing faulty servers detected events are generated for the same node, examine the node's settings for these characteristics: error tolerance, synchronization hold down, and maximum inaccuracy.
Argument:
| server [id] | Specifies the list of servers used in the synchronization. | |
synchronization completed
This event is generated each time a synchronization is completed for the local node.
Arguments:
| clock adjustment | Specifies the relative time that the local clock needs to be adjusted to match the computed time. | |
| computed time | Specifies the time computed from the intersection of all server time intervals. | |
system error detected
This event is generated each time the operating system has a system error relevant to DECdts operation. See the system documentation for an explanation of the report text.
Argument:
| error text | Specifies the system error report. | |
time provider failure detected
This event is generated each time an external time-provider returns an invalid time or does not respond.
time representation version mismatch detected
This event is generated each time the local node receives a response indicating that it is using an invalid time representation version.
Argument:
| node [id] | Specifies the name of the node that is running the incompatible time representation version. | |
too few servers detected
This event is generated each time the number of servers specified by the servers required characteristic are not available for synchronization with the local node.
Arguments:
| number detected | Specifies the number of servers that responded to the synchronization request. | |
| number required | Specifies the number of servers required for synchronization. | |
too many servers detected
This event is generated each time the server responses overflow the synchronization list buffer of the local node. The difference between the maximum delivered and number accepted arguments is the number of responses that overflowed the buffer.
Arguments:
| number accepted | Specifies the number of server responses that were accepted by the node. | |
| number detected | Specifies the number of servers responding to a solicitation. | |
update initiated
This event confirms an attempt to change the system time resulting from the update command.
NCL_PROFILE_006.HTML OSSG Documentation 2-DEC-1996 12:47:47.10
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.