Chapter 14 VALERR and VALWARN Messages

CAUSE: No data has been entered for the specified path.

ACTION: Check for correct spelling of configuration path; enter data for the path, if necessary.

CAUSE: Name entered in configuration screen is too long.

ACTION: Rename, using no more than the expected number of characters.

CAUSE: Link name specified in link configuration screen (LINK.linkname) differs from name in NETXPORT configuration screen.

ACTION: Make sure that link name specified in link configuration screen (LINK.linkname) is the same as that specified in NETXPORT screen.

CAUSE: Displayed path should contain no data.

ACTION: Contact your Hewlett-Packard representative for assistance.

CAUSE: Home network specified in the Global Transport Configuration screen (path NETXPORT.GLOBAL) is not configured.

ACTION: Check name of IEEE 802.3 network interface as configured in the Network Interface Configuration screen (path NETXPORT.NI). Enter this name as Home Network Name in Global Transport Configuration screen.

CAUSE: Displayed configuration path not found in configuration file.

ACTION: Contact your Hewlett-Packard representative for assistance.

CAUSE: No network interfaces have been configured.

ACTION: Configure the network interface, using the Network Interface Configuration screen (path NETXPORT.NI).

CAUSE: Retransmission interval lower bound is set higher than upper bound in Transmission Control Protocol screen (path NETXPORT.GPROT.TCP).

ACTION: Reconfigure transmission interval bounds so that the lower bound is less than or equal to the upper bound in NETXPORT.GPROT.TCP.

CAUSE: Initial retransmission interval is not in range between lower and upper retransmission interval bounds.

ACTION: Reconfigure initial retransmission interval or interval bounds so that initial interval falls in range, using the Transport Control Protocol (TCP) Configuration screen (path NETXPORT.GPROT.TCP).

CAUSE: Unknown path found in configuration file.

ACTION: Contact your Hewlett-Packard representative.

CAUSE: In the Router Mapping Screen the specified link is a dial type link and local is specified, but a phone number is not configured.

ACTION: Configure the appropriate phone number for the dial link in the Router Mapping Screen (path NETXPORT.NI.NIname.MAPPING.mapentry.)

CAUSE: On the Router Mapping Screen local is specified, dial is enabled for the specified link, and security is set ON in the Dial Protocol Screen, but there is no security string configured for the mapping entry.

ACTION: Either configure the appropriate security string in the Router Mapping Screen or disable security in the Dial Protocol Screen.

CAUSE: The network portion of the gateway IP internet address specified in the Neighbor Gateway screen differs from the network portion of the IP internet address configured in the IP Protocol Screen.

ACTION: Correct one of the two addresses such that their network portions match.

CAUSE: You are configuring a LAP-B network interface link, but the link name specified corresponds to a non-LAP-B link.

ACTION: Reconfigure the link in the Link Selection screen (LINK) as a LAP-B link type.

CAUSE: The Dial Protocol screen is configured with Security On = Y but there are no security strings configured.

ACTION: Either disable security in the Dial Protocol Screen, or configure at least one security string.

CAUSE: The specified home network name in the Global Transport configuration screen corresponds to a configured gatehalf type network interface.

ACTION: Check the names of the network interfaces configured in NETXPORT.NI. Except for loop and gatehalf types, enter one of the configured network interfaces as the home network name on the Global Transport Configuration Screen (NETXPORT.GLOBAL).

CAUSE: The specified home network name in the Global Transport configuration screen corresponds to configured loopback type network interface.

ACTION: Check the NI names configured in NETXPORT.NI. Choose one of the names that does not correspond to a LOOPBACK type.

CAUSE: There are no entries configured on the Router Mapping Screen.

ACTION: Configure mapping entries for the Router NI (NETXPORT.NI.NIname.MAPPING).

CAUSE: A home network is not configured on the Global Transport Screen, but a gatehalf network interface is configured.

ACTION: Check the names of the NI configured. Choose one of the names that does not correspond to a gatehalf type.

CAUSE: The maximum number of internet reachable networks configured for the specified network interface exceeds the maximum number of networks.

ACTION: Use the NMMGR utility to reduce the number of reachable networks in NETXPORT.NI.NIname.INTERNET.gatename to be equal to or less than the maximum value. Validate the configuration again.

CAUSE: The number of gateways configured for the specified NETXPORT.NI.NIname.INTERNET screen is greater than the maximum value permitted.

ACTION: Use the NMMGR utility to reduce the number of gateways in NETXPORT.NI.NIname.INTERNET to be equal to or less than the maximum value. Validate the configuration again.

CAUSE: The number of configured entries on the Router Mapping screen exceeds the maximum number of router table entries.

ACTION: Use the NMMGR utility to reduce the number of mappings in NETXPORT.NI.NIname.MAPPING to be equal to or less than the maximum value. Validate the configuration again.

CAUSE: The link name entered in the Router Mapping Screen differs from any configured in the NI Link Screen.

ACTION: Make sure that the link name specified in the Router Mapping Screen is the same as one of the links configured in the NI Screen (NETXPORT.NI.NIname.LINK).

CAUSE: The network portion of the IP internet address specified in the network interface mapping screen differs from the network portion of the IP internet address configured in the IP Protocol Screen.

ACTION: Make sure that the IP network number in the Mapping Screen (NETXPORT.NI.NIname.MAPPING) is the same as the IP number specified in the IP Protocol Screen (NETXPORT.NI.NIname.PROTOCOL.IP).

CAUSE: The NI type is LAN802.3, but the link configured corresponds to a non-LAN link in Link Configuration.

ACTION: Configure a LAN802.3 type link on the NI Link Screen (NETXPORT.NI.NIname.LINK).

CAUSE: There are two or more Router Mapping Screens with the wild card IP address "@" configured for the same router NI.

ACTION: Consult the discussion on the use of the wild card address on the Router Mapping Screen in the NS 3000/iX NMMGR Screens Reference Manual.

CAUSE: The wild card IP address was used in the specified Router Mapping Screen and a total of 2 router mapping entries are not configured for this router NI.

ACTION: Consult the discussion on the use of the wild card address on the Router Mapping Screen in the NS 3000/iX NMMGR Screens Reference Manual.

CAUSE: A wild card IP address mapping is configured for this router network, but more than one link is configured for this network under the NETXPORT.NI.NIname.LINK screen.

ACTION: Use the NMMGR utility to change the configuration file so that only one link is configured for this screen; or, do not use the wild card for the IP address mapping. Validate the configuration file again.

CAUSE: The LOGGING.SUB0003 record does not exist in the configuration file.

ACTION: Use the NMMGR utility to add the LOGGING.SUB0003 record to the configuration file so that logging for Network Transport will be configured. Be sure to add logging classes 1 through 6 to the LOGGING.SUB0003 level. Validate the Network Transport again.

CAUSE: There are no configuration file records beneath the LOGGING.SUB0003 path in the configuration file.

ACTION: Use the NMMGR utility to add in configuration records CLAS0001 through CLAS0006. Validate the Network Transport again.

CAUSE: Some other configuration record besides CLAS0001 through CLAS0006 exists beneath the LOGGING.SUB0003 record of the configuration file.

ACTION: Use the NMMGR utility to change the configuration file so that the only records beneath the LOGGING.SUB0003 path are CLAS0001 through CLAS0006. Validate the Network Transport again.

CAUSE: The node number portion of an IP internet address in the specified configuration file record is equal to zero.

ACTION: Use the NMMGR utility to change the node number portion of the offending IP internet address to be a non-zero value. Validate the Network Transport again.

CAUSE: The node number portion of the gateway IP internet address in the specified configuration file record is the same as the network's local IP internet address node number.

ACTION: Use the NMMGR utility to change the local node number or gateway number so that they are no longer equal. Validate the Network Transport again.

CAUSE: The LOGGING.SUB0004 record does not exist in the configuration file.

ACTION: Use the NMMGR utility to add the LOGGING.SUB0004 record to the configuration file so that logging for the DC/LDM will be configured. At this time logging class 0 should also be added to the LOGGING.SUB0004 screen. Validate the Network Transport again.

CAUSE: There is no class zero logging configured for the DC/LDM beneath the LOGGING.SUB0004 path in the configuration file.

ACTION: Use the NMMGR utility to add in configuration record CLAS0000 so that all logging is configured for the DC/LDM. Validate the Network Transport again.

CAUSE: The LOGGING.SUB005 record does not exist in the configuration file.

ACTION: Use the NMMGR utility to add the LOGGING.SUB0005 record to the configuration file so that logging for NetIPC will be configured. At this time logging classes 0 through 2 should also be added to the LOGGING.SUB0005 screen. Validate the Network Transport again.

CAUSE: There are not three logging classes configured beneath the LOGGING.SUB0005 path in the configuration file.

ACTION: Use the NMMGR utility to add in configuration records CLAS0000 through CLAS0002 so that all three logging classes are configured for NetIPC. Validate the Network Transport again.

CAUSE: Some other configuration record besides CLAS0000 through CLAS0002 exists beneath the LOGGING.SUB0005 path in the configuration file.

ACTION: Use the NMMGR utility to change the configuration file so that the only records beneath the LOGGING.SUB0005 path in the configuration file are CLAS0000 through CLAS0002. Validate the Network Transport again.

CAUSE: The network number portion of the next hop IP internet address on the specified NETXPORT.NI.NIname.MAPPING screen is not the same as the network's local IP internet address number.

ACTION: Use NMMGR to change the network number of either the next hop IP internet address or the local IP internet address so that they are the same. Validate the Network Transport again.

CAUSE: There is no NETXPORT.NI.NIname.MAPPING record for the specified network which has the same destination IP internet address and linkname as those on the specified non-adjacent mapping screen.

ACTION: Use NMMGR to change the configuration file so that the next hop IP internet address and the linkname on the specified mapping screen match those of an adjacent mapping screen for the same network. Validate the Network Transport again.

CAUSE: There are no NETXPORT.NI.NIname.LINK.linkname records in the configuration file for this non-software loopback network.

ACTION: Use NMMGR to change the configuration file so that at least one NETXPORT.NI.NIname.LINK.linkname record exists for this network. Validate the Network Transport again.

CAUSE: Phone data has been erroneously configured for a direct connect link.

ACTION: Delete the phone data, or correct the link type.

CAUSE: Loopback is the only NI configured.

ACTION: Use NMMGR to add NIs for LAN or router networks and validate the Network Transport again.

CAUSE: The link specified in the NETXPORT.NI.NIname.LINK.linkname is not configured as an X.25 link.

ACTION: Use NMMGR to change the link type in LINK.linkname to an X.25, or create a new link of type X.25 and associate it with this NIname. Validate the network transport configuration again.

CAUSE: There is no node name configured under the NODENAME path.

ACTION: Use NMMGR to configure a local node name under the NODENAME path.

CAUSE: A class other than CLAS0000, CLAS0001, CLAS0002, CLAS0003, CLAS0004, or CLAS0005 has been configured as a logging class for subsystem 40 (remote link manager).

ACTION: Use NMMGR to change the configuration file so that only valid classes are configured. Validate the network transport configuration again.

CAUSE: The LOGGING.SUB0040 record does not exist in the configuration file.

ACTION: Use NMMGR and go to the LOGGING screens to add the LOGGING.SUB0040 record to the configuration. Logging classes 0000 through 0005 should also be added to the configuration so that logging is completely configured for Remote Link Management.

CAUSE: All required logging classes are not configured for subsystem 40. Six logging classes configured: CLAS0000, CLAS0001, CLAS0002, CLAS0003, CLAS0004, CLAS0005.

ACTION: Use NMMGR to configure all classes under the path LOGGING.SUB0040. Validate the network transport configuration again.

CAUSE: A link of type SNA must be used when configuring an NI for NS over SNA.

ACTION: Use NMMGR to configure a link of type SNA. Validate Transport again.

CAUSE: In the SVCPATH configuration an X.25 address key is mapped to an undefined facility set.

ACTION: Modify the X.25 address key so that it is mapped to an existing facility set. Or, create a new facility set with the name to which the X.25 address key is mapped.

CAUSE: At least one X.25 address key must be configured under either the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH or the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path.

ACTION: Use NMMGR to configure an address key under either the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH or the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path.

CAUSE: More than the allowed number of address keys were defined. The maximum number of combined SVC and PVC address keys allowed is 1024.

ACTION: Use NMMGR to delete excess address key paths.

CAUSE: An X.25 address key was defined more than once under either the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH or the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path.

ACTION: Make sure an X.25 address key is configured only once. Delete all but one of any given X.25 address key.

CAUSE: A PVC number is defined more than once under the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path.

ACTION: Make sure all PVC numbers are unique in a given PVC configuration path.

CAUSE: An X.25 address is defined more than once under the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH path.

ACTION: Make sure all X.25 addresses are unique in a given SVC configuration path.

CAUSE: The number of SVC entries under the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH path exceeds the maximum of 1024 allowed.

ACTION: Delete the excess SVC entries.

CAUSE: The number of PVC entries under the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path exceeds the maximum of 128 allowed.

ACTION: Delete the excess PVC entries.

CAUSE: An internal error occurred while building the local node's path report to place in the configuration file.

ACTION: RESTORE a backup copy of NMCONFIG.PUB.SYS from tape and try to validate the Network Transport again. If this fails, the configuration file is corrupt. See Appendix A “Submitting an SR ” of this manual.

CAUSE: An internal error occurred while adding the local node's path report to the configuration file.

ACTION: RESTORE a backup copy of NMCONFIG.PUB.SYS from tape and try to validate the Network Transport again. If this fails, the configuration file is corrupt. See Appendix A “Submitting an SR ” of this manual.

CAUSE:

ACTION:

CAUSE: The T1 timer parameter configured is less than the value recommended in the LAP-B specification for the type of point to point link configured in LINK.linkname.

ACTION: Confirm that the configuration in this LINK.linkname is correct. If any changes are made, validate the Network Transport again.

CAUSE: The network directory is configured as part of the search path in the NETXPORT.GLOBAL screen, but no NSDIR.NET.SYS file exists.

ACTION: Prior to completing the current configuration activity, the network directory NSDIR.NET.SYS should be created, or the search path in the NETXPORT.GLOBAL screen should be modified to not include the network directory.

CAUSE: Another LAP-B link in the configuration file is configured for the same physical path as the specified LAP-B link.

ACTION: This is not a problem if one of the LAP-B links configured for this path is not activated. However, if a LAP-B link is brought up while another such link is active at that physical path, an error will result during link startup.

CAUSE: The X.25 timer is set too low.

ACTION: Hewlett-Packard recommends that the X.25 Inactivity timer be configured with a value greater than that of the TCP Connection Assurance timer to avoid unnecessary closing and opening of the X.25 virtual circuit. For optimum performance, configure the X.25 Inactivity timer (or the TCP Connection Assurance timer) so that the X.25 timer has a greater value than the TCP timer.

CAUSE: At least one SVCPATH entry does not have an X.25 address key configured. This configuration will work only if the link is connected to a DDN.

ACTION: If the link is not connected to a DDN, make sure all SVCPATH entries have an address key configured under the path NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH.