Diagnostics
B-2
Troubleshooting
User Troubleshooting Procedure
•
Verify that the SMB is plugged in securely.
•
Via in-band or out-of-band connection, query the SMB Event Log to determine the cause of
the failure based on the most recent event code. (Refer to Appendix A for a listing of event
codes.)
Services Troubleshooting Procedure
•
Same as above
Server Modem Does Not Answer
Possible Causes
•
Cables not connected or bad
•
Modem “dead”
•
Modem power out
•
SMB modem initialization string incorrect
User Troubleshooting Procedure
•
Verify that the modem is powered on
For an internal modem, unplug the SMB and verify that the modem power cord is connected
between the modem and the power connecter on the SMB.
•
Verify the phone lines
•
Verify that the modem initialization string contains valid modem commands
•
Verify the modem initialization string includes the auto answer capability (usually S0=1),
ignore DTR function (usually &D0), and standard Carrier Detect Control (usually &C1)
•
Use a regular phone line to dial the SMB and listen for the modem tones
Services Troubleshooting Procedure
•
Same as above
•
Enable console logging as described in the section titled “SMB Modem Transport Logging”
Modem Connects - No Password Prompt
Possible Causes
•
SMB not in Server Management mode
•
Incorrect flow control set on modem(s)
•
SMB or console modem set to ignore or translate BREAKs to NULLs
Summary of Contents for WorldMark 4300
Page 1: ...BD20 1398 B000 12 97 WorldMark 4300 Server Management Product Manual Release 2 0...
Page 6: ...Contents iv Table of Contents...
Page 10: ...Preface viii Preface...
Page 14: ...Monitored Controlled Attributes 1 4 Overview...
Page 50: ...Working With Event Actions 2 36 User Interface...
Page 66: ...Chassis Events A 10 SMB Event Code Tables...
Page 96: ...LANDesk UNIX Server Troubleshooting B 30 Troubleshooting...
Page 100: ...Index Index 4 WorldMark 4300 Server Management Product Manual...