Includes excerpts from Decnet User Manual

4.3 Common problems
Once you have brought up your system as a network node, you may receive messages related to networking errors. Other problems that can occur at any time during network operation may not result in messages being displayed. This section explains the causes of error messages, suggests troubleshooting techniques, and describes the problems that you might experience in establishing asynchronous connections.

4.3.1 Common error messages and meanings
When using Decnet for Openvms, you may receive network-related messages indicating software or hardware problems, transient conditions, or errors in your input. The following lists some common network-related messages, explains what condition may be causing each message, and suggests actions you can take.

• (all messages displayed on a system, including those generated by Decnet for Openvms, are described in the Openvms system messages documentation.)

• system-f-exquota, exceeded quota
If this message appears when you are attempting to turn on a line, the
Netacp process does not have adequate bytlm to complete the operation.

You can take either of the following courses of action:

• increase the amount of bytlm quota allocated to the netacp process

By defining the netacp$buffer_limit system logical and restarting
Decnet. (reference the Decnet for Openvms Networking Manual for
details on how to estimate the amount of bytlm required by netacp.)

• decrease the amount of bytlm quota in use by lowering the number of
receive buffers associated with one or more lines.

• system-f-ivaddr, invalid media address

This message appears when you are attempting to turn on a line, and a
Duplicate physical address is detected on the lan. Select a unique Decnet address.

• system-f-invlogin, login information invalid at remote node

You receive this message if you attempt to access a remote node using an access control string that contains an invalid user name or password, or if you do not specify any access control information and no default Decnet account or proxy account is available at the remote node.

For example, if you enter this command specifying an invalid user password in the access control string that is part of the file specification, you receive this error message:

$ directory boston"smith ghijkl"::work1:[smith]
%system-f-invlogin, login information invalid at remote node

Retry the file operation with the correct login information.

• ncp-w-invpva, invalid parameter value

This message is displayed if you specify a parameter value in an ncp
Command that is not a valid value for the specified parameter. For example, the following command generates this error message:

Ncp>set line sva-0 protocol ddcmp point
_%ncp-w-invpva, invalid parameter value, protocol

The value for the indicated parameter is invalid because the sva device
uses the ethernet protocol. The name of the parameter for which the
value was invalid is displayed at the end of the error message. Reissue the command with the correct value for the parameter.

If an ethernet or fddi device is already in use by another protocol and
\cannot be reset to use the Decnet address, you receive this message when you enter the following command:

Ncp>set line sva-0 all
_%ncp-w-invpva, invalid parameter value, physical ethernet address
Line = sva-0

To fix this problem, change the system startup procedures to start Decnet before the application using the other protocol.

• system-i-linkexit, network partner exited

This message is displayed if the process on the remote node exited before completing the logical link to your node. The remote process might have exited prematurely, a timeout may have occurred at the remote node, or there may be a problem as indicated in the log file on the remote node. You can retry the operation.

To help diagnose the problem, read the netserver.log file in the directory
Of the account you are attempting to access at the remote node. Decnet for Openvms automatically creates a netserver.log file and places it in the directory for the appropriate account when it receives a connect request.

• system-f-nolinks, maximum network logical links exceeded

This message appears if the maximum number of links that the remote node allows has been exceeded. Wait and try again later.

• system-f-nosuchobj, network object unknown at remote node

You receive this message if you attempt to access a network object at a Remote node and the object is not specified in the remote node database. For example, if you attempt to use the phone utility from a node that supports phone and try to reach a node that does not have an entry for the network object phone in its configuration database, you receive the above message.

• system-f-nosuchnode, remote node is unknown

You receive this message if you attempt to issue a command to access a remote node (for example, the dcl command set host) and the remote node represented by node-id is not identified in the local volatile database. Verify that the node identifier is correct, enter the node name in your node database, and retry the operation.

• system-f-pathlost, path to network partner lost

You receive this message if you logged in to another node over the network (for example, using the dcl command set host) and the path to the remote node is lost. The path may be lost because of too much network activity or communications problems, or because Decnet was turned off at the remote node. Wait, then if the node is still reachable. If so, try again to log in.

• system-f-shut, remote node no longer accepting connects

You receive this message if you attempt to access the remote node using a dcl command (such as the set host command) under either of these conditions:

A. The executor parameter default access on the remote node has been set to none and the node parameter access is not set to allow access to the node. The default access at the remote node must be set to permit incoming and outgoing access before you can connect to the node.

B. The command set executor state shut was executed on the remote system. The network must be restarted on the remote node.

• system-f-unreachable, remote node is not currently reachable

This message is displayed when you attempt to connect to a node that is unreachable. For example, when you address a mail message to a user at remote node purple using the mail utility, if mail cannot create a link to the remote node, you may receive the following message:

%mail-e-loglink, error creating network link to node purple
_system-f-unreachable, remote node is not currently reachable

You can try to access the remote node again at a later time.

The message is also displayed even if the remote node does not exist, as long as you have indicated a node address or a node name that you previously defined in your node database. You also receive notice that the node is unreachable if the value of the executor parameter maximum address in your network database is lower than the address of the remote node you are attempting to access. Increase the value of the ncp executor parameter maximum address in your database to be at least as high as the highest address of any node that you want to contact.
 

> back to questions