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

Chapter 17 317
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
NMCONFIG file and is the exact same linkname which is now being
started. Verify the “Data=Y” flag is set at the top of that LINK screen
(meaning that ENTER has been pressed to save the configuration data
there). If the link is being used with NS or DTS, use the VALIDATE
function to validate the network configuration. Correct any
configuration errors and retry the operation.
1440 CLAS0001 MESSAGE: Cannot validate configuration file.
CAUSE: After successfully reading configuration data for a link being
started, the link module configurator checked the data and found it was
not valid (“Cause” is not used here). For NS/3000, probably the link
type and NI type do not match.
ACTION: The module configurator cleaned up and returned an error to
the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the
NMCONFIG file and is either a 100Base-T link type. If the subsystem
being started is NS, verify the link type matches the NI type for the
network being started.
If these are not the problem, an incorrect version of NMMGR may have
been used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=24 to check versions of NMMGR components.
The format of your NMCONFIG file may be incompatible with the link
driver version installed on your system. Run NMMGRVER.PUB.SYS to
update your NMCONFIG file to a newer version, or restore an older
version from a backup tape, whichever is appropriate.
If the problem still occurs, contact your Hewlett-Packard
Representative for assistance in using NMMGR to configure 100Base-T
links.
1580 CLAS0001 MESSAGE: Subsystem is opening link.
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up (“Transport” = name of the
subsystem which is starting the link, or its subsystem number if the
configurator does not know the name).
ACTION: None. This is an informational event only.
A similar event will be logged when the link is closed.
1600 CLAS0001 MESSAGE: Cannot open tracing.
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
(“Cause” = 32-bit status from the call to nmopentrace).