What to Do Before Calling Technical Support for OS Issues
Articles and Tips: tip
01 Aug 2003
NetWare is very reliable, but there are times when problems can arise. When trouble comes to your NetWare server, it is sometimes helpful to have a list of steps that help you identify the root cause of the problem.
TID #10016899 is such a document, from which this Tip and Trick has been adapted. The TID has five simple steps that help you determine what the problem might be. If you can't find the solution, these steps also prepare you for contacting technical support at Novell. So let's go down through these steps.
Step 1: What version of NetWare do you have?
You can probably answer this without even looking. If not, you will need to download the file CONFIG.NLM and find out. (The current version is available at http://download.novell.com/.)
What about other Novell software that's running on the server? What about third-party software? All of these pieces may be playing a part in your server problem. Get versions on all of the software that you're using.
Step 2: What patches have been applied to the server?
Is your server current? If not, go to http://support.novell.com/produpdate/patchlist.html and find out. If the server is out of date, get it current. What about patches for other Novell software and third-party applications? If they're not current, update them also. And don't forget your drivers--make sure they are up to date as well.
If there are still problems, then it's time to identify the symptoms your server is having.
Is there anything in the error logs?
Are there any error messages?
Does the problem occur only under certain conditions?
Can you duplicate the problem? (If so, list the steps.)
Could the problem be with hardware?
If you unload certain applications or NLMs, does the problem go away?
When was the last time you scanned for viruses? Are the virus definitions up to date?
When did the problem first appear?
What has recently changed in the system?
At this point, it is time to use a few utilities to see if the problem can be isolated. Support recommends the following:
Use CONFIG.NLM and config reader to check software versions. In some cases, the output of this NLM will be requested by technical support.
Run VREPAIR.NLM if you are having volume problems.
Run DRVSPEC.EXE to verify compatibility of ODI modules and LAN drivers. The current version is at http://download.novell.com/Download?buildid=VI0kzmTwlQU~.
If you've gone through the previous steps without a resolution, it is now time to review some documents that cover diagnosing and solving problems.
TABNDx.EXE is the Abend Troubleshooting Guide. The current version is available at http://download.novell.com/Download?buildid=LG4r1fbxXEY~. The Abend Trouble-shooting Guide contains diagnostic programs and utilities as well as documentation.
Search for your specific problem in the TID (Technical Information Database) Knowledgebase at http://support.novell.com/search/kb_index.jsp.
Check AppNotes for solutions. The AppNotes Search page is at http://developer.novell.com/research/search.htm. This full-text search only searches the AppNotes archives.
If you want to search all of Novell, use the search dialog at the top of any Novell web page. There is a drop down window that allows you to refine your search to specific sub-sites, such as http://developer.novell.com or http://support.novell.com.
Try the support forums. This service is free and has some of the most knowledgeable sysops around. Begin your search at http://support.novell.com/forums/.
Check your manuals, online documentation, and so forth. Novell's online documentation is at http://www.novell.com/documentation/. Also, don't forget those readme files on your product CDs. They sometimes contain late-breaking information that never made it into the product documentation.
TID #10012765 ( http://support.novell.com/cgi-bin/search/searchtid.cgi?/10012765.htm) covers Performance, Tuning, and Optimization. While this isn't exactly troubleshooting, many of the tips found in this TID can fix related server problems.
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.