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

Chapter 16 195
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: If the linkname being started is a valid linkname, then there
may be a problem with Link Support Services. Halt the system, take a
system memory dump, then restart the system. If the problem still
occurs, see Appendix A, “Submitting an SR.
MESSAGE: Cannot add to link table.
205 ($CD) CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator successfully started the driver, but
encountered an error trying to add the link to the link table.
ACTION: Possibly too many links are started. If not, try starting a
different link, to see if that works. If not, first try doing a
:LINKCONTROL @ command to see if any LSS errors occur. If they do,
you may need to reinstall MPE software; contact your Hewlett-Packard
Representative for assistance. Otherwise try restarting the system to
see if it corrects the problem or LINKCONTROL errors. If none of these
suggestions helps, see Appendix A, “Submitting an SR.”.
MESSAGE: Cannot delete from link table.
206 ($CE) CAUSE: During the final link-close operation by an upper level
subsystem, the link module deconfigurator attempted to delete the link
from the link table, but encountered an error.
ACTION: The module deconfigurator reported an error, but attempted
to continue with the close. Network management services may have
been shut down. Otherwise, if this happens every time, see Appendix A,
“Submitting an SR.
MESSAGE: Cannot open tracing.
208 ($D0) CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator found that the link was configured to enable
tracing at startup, but encountered an error trying to open the trace
file.
ACTION: Using NMMGR, check if a filename was configured. If so,
verify it is a legal MPE filename. A group and account may need to be
specified. Make sure the user starting the link has the necessary
capabilities to create that file in the group and account specified. Check
whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks. Make sure the
version of the NMCONFIG file matches the rest of the system software,
by running NMMGRVER.PUB.SYS. If none of these suggestions solves the
problem, contact your Hewlett-Packard Representative for assistance
with configuring a 100VG-AnyLAN or 100Base-T link to enable tracing
at startup.