test

Solaris PC NetLink 1.0 Administration Guide

Tools for Assessing the Status of the Server

The SunLink Server program includes multiple tools that you can use to assess the operational status of the server at any given time. Frequent assessment of server status will improve your ability as a server administrator to notice a problem or trend quickly.

Periodic review of server status will provide a fairly stable basis for understanding how a normal problem-free server appears. Over time, information that deviates from the norm will be an indication that something has changed and warrants your attention.

Tools for assessing the status of the server are discussed in the following sections.

Event Logs

A number of events related to the daily operation of the server can be tracked using the SunLink Server Manager event logs (see Chapter 3, Configuring and Managing SunLink Server Software). These events are maintained in one of three event logs: system, security, and application. Administrators should develop and implement an event logging policy and include a review of event logs as a regular part of troubleshooting activities.

Administrators will find it particularly useful to characterize the typical use of the server by manipulating event log data using a spreadsheet or word processing program. You can use this approach to generate a standard operating profile of the server and to predict trends in server usage.

Note -

You can also view event logs by using the elfread command. For more information, type man elfread at the SunLink Server command prompt.

Server Status

SunLink Server maintains detailed statistics about its current usage as well as cumulative usage over a particular period of time. It is always helpful to review these statistics on a regular basis as well as when a server problem is encountered.

Server Information

To view data about current server use, use the SunLink Server Manager Information view (see "How to View SunLink Server Information"). This provides details about current client-server sessions and the resources being used by those sessions:

Cumulative Statistics

To view cumulative server usage data, you can use the net statistics command at the SunLink Server command prompt. This command provides cumulative totals for a variety of server activities. Administrators who review the server statistics provided by using this command on a regular basis will find it easier to recognize and address changes in server operation.

The following statistics are maintained for the SunLink Server system, and are available by way of the net statistics command:

Table 6-1 Cumulative Statistics Descriptions

Statistic 

Description 

Refreshed at 

Tells when this set of statistics began (either at the last server startup or the last time the statistics were cleared). 

Sessions accepted 

Tells how many times users connected to the server. 

Sessions timed-out 

Tells how many user sessions were closed because of inactivity. 

Sessions errored-out 

Tells how many user sessions ended because of error. 

Kilobytes sent 

Tells how many Kbytes of data the server transmitted. 

Kilobytes received 

Tells how many Kbytes of data the server received. 

Mean response time (msec) 

Tells the average response time for processing remote server requests. This always will be 0 for Solaris system servers. 

System errors 

This does not apply to Solaris system servers. 

Permission violations 

Tells when a user attempts to access resources without the required permissions. 

Password violations 

The number of incorrect passwords that were tried. 

Files accessed  

The number of files that were used. 

Comm devices accessed 

Not supported in the SunLink Server program. 

Print jobs spooled 

The number of print jobs that were spooled to printer queues on the server. 

Times buffers exhausted 

The number of shortages of big and request buffers. Always set to 0 for Solaris system servers. 

How to Display Session Information From a Windows NT Workstation

Administrators can display and control sessions between clients and the server. You can use this information to gauge the workload on a particular server.

To display session information from a Windows NT Workstation computer or a Windows client computer using Server Manager:

  1. Start Server Manager.

  2. Select the SunLink Server system about which you want to view session information.

  3. Click on the USERS button.

You also can display session information using the net session command at the SunLink Server command prompt.

Note -

You may see sessions displayed that do not show user names. The sessions are a result of administrative activity and should not be deleted.

How to Close Sessions From a Microsoft Windows Computer

An administrator can disconnect a user from the server at any time. Closing a user session does not prevent the user from reconnecting.

To disconnect a user session from a Windows NT computer or from a Windows client computer using Server Manager:

  1. Start Server Manager.

  2. Select the SunLink Server system about which you want to view session information.

  3. Click on the USERS button.

  4. Highlight the user and select the Disconnect button.

You also can disconnect a user session by using the net session command at the SunLink Server command prompt.

How to Close Open Resources From a Microsoft Windows Computer

When a user uses a shared file, the file is open. Sometimes a file will be left open, perhaps even with a lock on it, because of an application program error or some other problem. Such files will remain open and unavailable to other users. Administrators can close these files.

To close an open resource from a Windows NT computer or a Windows client computer using Server Manager:

  1. Start Server Manager.

  2. Select the SunLink Server whose data you want to view.

  3. Click on the IN USE button.

  4. Highlight the open resource and select the Close Resource button.

You also can close an open resource by using the net file command at the SunLink Server command prompt.

Print Subsystem Event Logs

SunLink Server maintains a separate print log for each printer share and each Solaris system printer it uses. These log files record any message generated because of a printer fault or print job error.

An administrator should check these log files periodically to determine whether any such errors are occurring. The logs can be accessed from a client computer by linking to the PRINTLOG shared resource.

The logs also can be accessed from the server. They are in the following directory: /opt/lanman/shares/printlog