![]() Verify the script execution date is relative to the problem time frame to make sure we aren’t looking at obsolete information.We want the best diagnostic information possible. Download and use the latest supportconfig.The goal for reviewing this file is to confirm the server is patched, major packages installed and if there may be any firewall concerns. Look at the basic-environment.txt file first. The CPU utilization, memory usage and disk space are within normal limits, and the kernel and running services are healthy. A basic server health check in it’s simplest form confirms that the server is patched and up-to-date. Yellow Flags are issues that probably should be addressed or at least monitored, but are not directly related to the problem. Red flags are not necessarily bad, but just need to be explained. They are issues that directly relate to the reported problem or may affect the overall server performance. Red Flags are problems that must be explained before moving forward. The goal in checking the health of the server is to note red and yellow flags. ![]() Make sure you submit both tar balls to Novell Technical Services if you need to open a service request.Įvery time I get a supportconfig, I always check the basics for obvious problems. Compare the supportconfig tar ball taken when the problem occured with the saved good copy for that server. Copy the tar ball off the server for comparison when and if the server experiences a problem that needs troubleshooting. How can you cut the learning curve if you don’t have 100 supportconfigs or the time to look at them? After each of your systems is running smoothly and tuned to your needs, get a supportconfig. After you look at 100 supportconfig tar balls, you will learn what is normal. To get good at reading a supportconfig, you need experience. You can also quickly repeat any piece of information you want because the exact command with it’s path and options were recorded in the text file. This way if the supportconfig ever “hangs,” you know what command it hung on. As far as a teaching tool, all commands used to gather information are first logged to the appropriate log file, and then the output is recorded. All files end with a ‘.txt’ extension so they are easily recognized and opened with default editors across platforms. The lvm.txt file is one location to review much of the LVM information. However, the current state for services specific to Logical Volume Management (LVM) are also recorded in the lvm.txt file. For example, all services and their current run level states are recorded in the chkconfig.txt file. As a result of this objective, several pieces of information are replicated to create a kind of one-stop-shop environment. Once the information is gathered, it should be organized in such a manner that problems can be solved quickly and efficiently. If there’s a problem, the basic supportconfig philosophy is, gather as much information as possible, so we only have to ask for it once. Of course information is critical to any problem solving scenario. Supportconfig has three primary purposes, 1) gather important system information, 2) reduce problem resolution time, and 3) teach useful system commands. Checking the basics begins with the basic-environment.txt and basic-health-check.txt files. Once you have created a supportconfig tar ball, you should perform a server health check. A test case of a server with high CPU utilization will illustrate the process. ![]() The goal of this article is to show the administrator how to use supportconfig to check the basic health of the server. Is the monitor plugged in? Is the install media in the DVD drive? Was the service started? Supportconfig is a tool designed to gather system information in a way that promotes resolving problems as quickly as possible. When problems arise with a server, the simple is often overlooked.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |