298 Chapter 6: Link error messages553-3211-510 Standard 1.0 October 1998Diagnostic tools error messagesThis is a summary of error messages reported when using the followingdiagnostic tools: continuity test, traffic reports, and loopback test.No more input is allowedCertain diagnostic tests are in progress. No other input is allowed untilthe tests are completed. Wait for the “mlusr>” prompt before enteringother commands.File cannot be opened for writingThe traffic report cannot be written to . Use the diskusecommand to check amount of space available or try another name.Message from tsmain: Printer is not connectedThe user directed the traffic report to a printer that is not connected.Check printer connections.Loopback Test Failed: Cannot configure any linkLoopback test cannot configure link 0 or 1. Use the fileverifApplication Module command to check the loopback configurationfiles in directory /usr/mlusr/conf or refer to Error 0909—LinkConfiguration Fail.Loopback Test Failed: Cannot enable any linkLoopback test cannot enable link 0 or 1. Either use the fileverifApplication Module command to check the loopback configurationfiles in directory /usr/mlusr/conf, or refer to Error 090A—Enable linkcommand failed.Loopback Test Failed: Link doesn’t come upLoopback test has tried four DTE and DCE combination tests, and thelink does not come up.1. Ensure that the proper cable is used and that the cable is wiredcorrectly. Try a different cable.2. Run maint> fileverif to ensure that the correct application files arepresent and that they are the proper size.
