\n
...
up.time
...
...
up.time captures the following Novell NRM system (version 6.5) statistics:
...
- \n
- Work To Do Response Time \n
- Allocated Service Processes \n
- Available Server Processes \n
- Abended Thread Count \n
- CPU Utilization \n
- Connection Usage \n
- Available Memory \n
- DS Thread Usage \n
- Packet Receive Buffers \n
- Available Event Control Blocks (ECBs) \n
- LAN Traffic \n
- Available Disk Space \n
- Disk Throughput \n
...
| Table of Contents |
|---|
Each statistic returns one of the following status options:
...
- Good \n
- Good \n
The statistic is well within the threshold suspect value.
\n \n - Suspect \n
The statistic is between the threshold good and critical values.
\n \n - Bad \n
The statistic is greater than the threshold critical value.
\n \n
...
Work To Do Response Time
...
This statistic enables you to view how processes share the CPU. The \nresponse response time is the amount of time that a Work To Do process requires \nto to run.
...
If this statistic returns a value of Suspect, you can check the \nrunning running threads to determine why there is a delay in the Work To Do \nthreadsthreads. If the value is Bad, thread is probably running more than it \nshould should or it is hung. You should identify the parent NetWare Loadable \nModule Module and then unload and reload it if possible.
...
Allocated Service Processes
...
This statistic enables you to view, as a graph, how the service processes are allocated on your server.
...
If the service processes are approaching the maximum, increase the \nvalue value of the Maximum Server Processes Set parameter. If you have only a \nfew few available server processes, increase the Minimum Server Processes \nSet Set parameter.
...
If the status is Bad, examine your server by doing the following:
...
- In Novell NRM, click Profiling / Debugging. \n
- Check the information for server process functions. \n
- Change the Maximum Server Processes and the Minimum Server Process Set parameters. \n
...
Available Server Processes
...
This statistic enables you to view the number of available processes \non on your server as a graph. The graph charts the processes that are \navailable available every five seconds over a 50 second period.
...
If the status is Suspect or Bad, increase the Set \nparameters parameters for Maximum Server Processes and the Minimum Server \nProcesses Processes settings. If the number of available server processes has not \nreached reached the maximum and is not increasing, add memory to \nyour your server.
...
Abended Thread Count
...
This statistic enables you to view the threads that have ended abnormally (abended) and are suspended.
...
If the status is Suspect or a Bad, your server has abended and has \nrecovered recovered automatically by suspending the offending thread while \nleaving leaving the rest of the server processes running. As a result, some of \nthe the server's functions were compromised. You must determine which \nmodulemodule, driver, or hardware the abended threads belong to, and then \ntake take the appropriate action.
...
CPU Utilization
...
This statistic enables you view, as a graph, how busy any given CPU \nisis. up.time tracks usage on a per CPU basis, collecting data every 30 \nsecondsseconds. The graph displays a 10 second history.
...
If the status is Suspect or Bad, determine which thread or module is \ncausing causing the most CPU cycles and take appropriate action, including:
...
- \n
- Unloading and reloading the module. \n
- Reporting problems to the vendor of the module. \n
- Loading an updated module. \n
...
To determine which thread or module is using the most CPU cycles:
...
- In Novell NRM, click Profile / Debug. \n
- Do one of the following: \n
- \n
- View the Execution Profile Data by Thread data. \n
- Click Profile CPU Execution by NLM. \n
\n
...
Connection Usage
...
up.time monitors connections on a per-server basis. NRM displays only the following metrics:
...
- \n
- The number of connections that are being used. \n
- The peak number of connections used on this server. \n
...
Available Memory
...
This statistic enables you to view the amount of memory that is not \nallocated allocated to any service. Most, if not all, of this memory is used by \nthe the file system cache. When available memory gets too low, modules \nmight might not be able to load or file system access might become sluggish.
...
DS Thread Usage
...
This statistic enables you view the number of server threads that \nNovell Novell eDirectory uses. The server thread limit ensures that threads \nare are available for other functions as needed – for example, when large \nnumber number of users log in at the same time.
...
eDirectory uses multiple server threads. However, its thread \nrequirements requirements should not cause poor performance because eDirectory \ncannot cannot use more than its allocated maximum number of threads.
...
If this statistic returns a Good status, eDirectory is using less \nthan than 25% of the available server threads. If it returns a Suspect \nstatusstatus, eDirectory is using between 25% and 50% of the available server \nthreadsthreads. If the status is Bad, eDirectory is using more than 50% of the \navailable available server threads.
...
Packet Receive Buffers
...
This statistic enables you to view the status of Packet Receive \nBuffers Buffers for the server. Packet Receive Buffers transmit and receive \npacketspackets. You can set the maximum or minimum number of buffers to \nallocate allocate using the Maximum Packet Receive Buffers or Minimum Packet \nReceive Receive Buffers SET parameters. The minimum number of buffers is the \nnumber number of packets that are allocated at when the system is initialized.
...
If the number of Packet Receive Buffers is increasing, the system \nwill will be sluggish. If the number of Packet Receive Buffers reaches the \nmaximummaximum, and no Event Control Blocks (ECBs) are available, the server \nwill will become very sluggish and will not recover.
...
Available Event Control Blocks (ECBs)
...
This statistic enables you to view the status of available Event \nControl Control Blocks (ECBs). Available ECBs are Packet Receive Buffers that \nhave have been created but which are not currently being used.
...
If the available ECB count is zero, the server will become sluggish \nuntil until enough ECBs are created to fill the demand. The server will \nrecover recover as long as the number of Packet Receive Buffers does not \nincrease increase to the maximum that can be allocated.
...
LAN Traffic
...
This statistic shows whether or not your server can transmit and \nreceive receive packets. If this statistic returns a Good status, the server is \nable able to accept or transmit packets through the network board. If the \nstatus status is Bad, the network board is not transmitting or receiving \npacketspackets.
...
All servers should be able to transmit or receive packets. If your \nserver server is not transmitting, your LAN is not functioning properly. Check \nthe the drivers and protocol bindings for the network board on the server. \nIf If the drivers and protocol bindings are functioning properly, then the \nnetwork network board is probably faulty. If the network board is functioning, \nyou you should perform a diagnostic on your LAN.
...
Available Disk Space
...
This statistic enables you to view the status of the available disk \nspace space on all mounted volumes on a server. This statistic returns the \nfollowing following statuses:
...
Disk Throughput
...
This statistic enables you to view the status of amount of the data \nthat that is being read from and written to the storage media on this server.
...
If this statistic returns a Good status, then the storage system is \nexperiencing experiencing reads or writes, and there are no pending disk I/Os. If \nthe the status is Suspect, the storage system has disk I/Os pending, no \nreads reads or writes have occurred, and less than four samples have been \ntakentaken. If the status is Bad, the storage system has disk I/Os pending, \nno no reads or writes have occurred, and four or more samples have been \ntakentaken.