NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 14 141
VALERR and VALWARN Messages
2. If this condition is not desired, use the NMMGR utility to configure
store andforward buffersinthe NETXPORT.NI.NIname.PROTOCOL.IP
screen, and validate the Network Transport again.
ACTION:
1. More than one non-loopback network is configured, but no store and
forward buffers have been configured in the
NETXPORT.NI.NIname.PROTOCOL.IP screen. It will not be possible to
send inbound packets from another network out on a link on this
network without any store and forward buffers.
2. If this condition is not desired, use the NMMGR utility to configure
store andforward buffersinthe NETXPORT.NI.NIname.PROTOCOL.IP
screen, and validate the Network Transport again.
1007 MESSAGE: CONFIGURED T1 PARAMETER (!) IS THE
RECOMMENDED FORMULA VALUE (!).
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.
1100 MESSAGE: NETWORK DIRECTORY CONFIGURED BUT NOT FOUND.
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.
1101 MESSAGE: ANOTHER LAP-B LINK HAS THIS SAME PHYSICAL PATH.
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.
1102 MESSAGE: X.25 INACTIVITY TIMER IS LESS THAN OR EQUAL TO
TCP CONNECTION ASSURANCE TIMER.
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