298 Chapter 6: Link error messages
Diagnostic tools error messages
553-3211-510 Standard 1.0 October 1998
This is a summary of error messages reported when using the following
diagnostic tools: continuity test, traffic reports, and loopback test.
No more input is allowed
Certain diagnostic tests are in progress. No other input is allowed until
the tests are completed. Wait for the Òmlusr>Ó prompt before entering
other commands.
File <filename> cannot be opened for writing
The traffic report cannot be written to <filename>. Use the diskuse
command to check amount of space available or try another name.
Message from tsmain: Printer is not connected
The user directed the traffic report to a printer that is not connected.
Check printer connections.
Loopback Test Failed: Cannot configure any link
Loopback test cannot configure link 0 or 1. Use the fileverif
Application Module command to check the loopback configuration
files in directory /usr/mlusr/conf or refer to Error 0909ÑLink
Configuration Fail.
Loopback Test Failed: Cannot enable any link
Loopback test cannot enable link 0 or 1. Either use the fileverif
Application Module command to check the loopback configuration
files in directory /usr/mlusr/conf, or refer to Error 090AÑEnable link
command failed.
Loopback Test Failed: Link doesnÕt come up
Loopback test has tried four DTE and DCE combination tests, and the
link does not come up.
1. Ensure that the proper cable is used and that the cable is wired
correctly. Try a different cable.
2. Run maint> fileverif to ensure that the correct application files are
present and that they are the proper size.