OS/2 Shareware BBS: 8 Other/08-Other.zip/plusdemo.zip/WITPLANL.INF

OS/2 Help File | 1996-03-05 | 14KB | 414 lines

ΓòÉΓòÉΓòÉ 1. Mean Response ΓòÉΓòÉΓòÉ

Mean Response indicates how long each request takes to service. It doesn't
necessary indicate processor overload but the inability of the server to
respond. It does not take into account whether a request was complex or
trivial.

It doesn't necessarily indicate processor overload but the inability of the
server to respond. Some reasons for this are:

   1. Lack of processor power.

   2. Excessive utilization of disk storage.

   3. Lack of resources such as connections, shares, buffers or commands.

   4. System errors.

 Don't jump to conclusions. Usually items 2 and 3 are where the action is.
 Dumping faster and faster hardware on the problem may give minor relief but
 the problem will still persist.


ΓòÉΓòÉΓòÉ 2. Sessions ΓòÉΓòÉΓòÉ

Sessions are the number of active sessions that the server has outstanding.
Usually you have "extra" capacity but as users are added it is easy to overlook
giving away more then you have.

The number of sessions a server can handle is controlled in multiple places. In
the IBMLAN.INI file the NETx and MAXUSERS entries control the number of
sessions the server can accept.

You must make sure that the NETBIOS session entry in the PROTOCL.INI file is
larger then the NETx definition. Update this entry using LAPS and edit the
NETBIOS definition.

The NETx entry sets the number of NETBIOS sessions , NETBIOS Commands and
NETBIOS Names for the system. You should have about twice as many NETBIOS
commands as sessions.

NETx = netbeui$,0,LM10,# SESSIONS,# COMMANDS,# NAMES

MAXUSERS sets the maximum number of users who can use the server. This value is
the number of NETBIOS sessions on the server. The maxusers parameter value
cannot exceed the maxconnections parameter value.

MAXUSERS has a maximum is 250 per adapter. Set the value for the number who
will be logged on not the number of defined IDs.

       maxusers = (number of requesters) + (number of additional servers)

       Default value:  45

       Minimum value:  1

       Maximum value:  1000  (250 maximum for each adapter

                   netx specified in the IBMLAN.INI file)

      A suggested calculation is:

      MAXUSERS =  a + b + c + d

       a   Domain controller 1 per additional server (if  any)

       b   Remote IPL server  1 for each remote IPL requester to be IPLed
      simultaneously

       c   Server  1 if the DLRinst service is  running; 0 otherwise

       d   Server  1 for each OS/2  and  DOS LAN  Requester

 If you still need more sessions than can be defined consider AUTODISCONNECT
 and CLEANUP in the IBMLAN.INI file.

 AUTODISCONNECT sets the time, in minutes, the server waits before
 disconnecting inactive sessions. With a  value  of -1, the server does not
 disconnect inactive sessions.

       Default value:  120

       Minimum value:  -1

       Maximum value:  65535

 CLEANUP specifies whether  to clean up (disconnect) shares for dynamic
 aliases.  A dynamic alias  is shared with the as required by user. If the
 autodisconnect parameter value is set to -1, the cleanup parameter should be
 set  to Y to make it active.  Making the cleanup parameter active disconnects
 shares for dynamic aliases that no longer have users.  When autodisconnect is
 set  to -1, idle sessions are never ended by the server. If  the cleanup
 parameter is set to  N, the number of dynamic shares  may  require  maxshares
 to be increased. If  the autodisconnect  parameter  is not set to -1, set  the
 cleanup parameter to suit your requirements.  If autodisconnect is not -1 and
 cleanup =  Y, cleanup of a dynamic alias share will occur when there are no
 users using the alias.  Idle sessions will end and the dynamic aliases shared
 will be released when the autodisconnect time-out t occurs.


ΓòÉΓòÉΓòÉ 3. Session opens ΓòÉΓòÉΓòÉ

The number of new sessions created during this sample period. See Sessions


ΓòÉΓòÉΓòÉ 4. Pass Word Errors ΓòÉΓòÉΓòÉ

Password errors - Failed logons due to Password errors

Access to resources is governed in two ways.  User Profile Management (UPM)
provides validation for a user ID and password at logon. The  LAN Server
provides access control with a set of permissions that allow the  network
administrator to grant users various levels of access to shared resources.


ΓòÉΓòÉΓòÉ 5. Session errors ΓòÉΓòÉΓòÉ

The number of session errors for the sample.


ΓòÉΓòÉΓòÉ 6. Shares ΓòÉΓòÉΓòÉ

Shares indicate the number of outstanding shares the server has. Expect this
number to fluctuate only when resources are shared "as required". When analyzed
along with sessions and file accesses it may be used to better understand the
need for "connections".

There are two entries in the IBMLAN.INI file that have an effect on shared
resources.

MAXSHARES is the maximum number of resources the server can share. If one user
is using five resources on the server, the value of this parameter must be at
least 5; but if five users are using the same server resource, the value of
this parameter need only be set to 1.  The following equation can be used to
calculate a value for the maxshares parameter.

       maxshares=

           (3*(number of applications))+

           (number of home directories)+

           (number of file and printer aliases)

       Default value:  16

       Minimum value:  2

       Maximum value:  500

 Note:  The number of shared resources displayed by the NET CONFIG SRV command
 will be different from the number specified with the maxshares parameter.
 Resources displayed by the NET CONFIG SRV command  include  system shares
 (ibmlan$, admin$, and so on), and one  for each partition on the server (a$,
 b$, and etc). consider:

      All active application ALIASs

      All active home directories

      All Print ALIASs

      Some reasonable number of extras

 The MAXCONNECTIONS parameter of the IBMLAN.INI represents the maximum number
 of NET USE commands that requesters can issue to the server. As a capacity
 parameter it may limit access to server resources. The limit is 2000. Consider
 a setting of:

       All active application SHARES * the number of users +

       All active home directories +

       All Print ALIAS * the number of users +

       4 * OS/2 users +

       3 * Windows users +

       Some reasonable number of extras

 Two other IBMLAN.INI parameters provide for the conservation of this resource.
 AUTODISCONNECT sets the time in minutes for the server to wait to disconnect
 inactive session.  The default is -1 which requests the server to make no
 attempt at reclaiming unused sessions. CLEANUP specifies if dynamic shares
 will be disconnected. See the TUNE LAN SERVER section of this manual for a
 more in-depth discussion.

 MAXCONNECTIONS is the maximum number of connections that requesters can have
 to the server.  This is the number of NET USE commands the server can handle.
 Maxconnections  must be greater than or equal to the maxusers parameter value.

       maxconnections =

           (maxusers * 6) +

           (3 * (number of DLR Windows** requesters))+

           (4 * (number of OS/2 requesters)

       Default value:  128

       Minimum value:  1

       Maximum value:  2000


ΓòÉΓòÉΓòÉ 7. File Opens ΓòÉΓòÉΓòÉ

The number of file opens during the sample.

The number of files that may be opened is controlled by two entries in the
IBMLAN.INI file.

MAXOPENS is the maximum number of files, pipes, and devices the server will
allow to be  open at one time. Each DOS remote IPL workstation requires 3 open
files at the remote IPL server workstation. A suggested value might be:

       maxopens=

        (10*(number of DLRs))+

        (55*(number of OS/2 requesters))+

        (45 * (number of DLR Windows requesters))+

        a resonable number of extras

 Note:  The maximum number of open files is 8000.  However, the maximum number
 of unique open files is 1279. The first opening of a file counts against the
 maximum of 1279. Additional opening of the same file count against the maximum
 of 8000.

       Default value:  250

       Minimum value:  1

       Maximum value:  8000


 MAXSESSOPENS specifies the maximum number of files, pipes, and devices one
 requester can have open on the server.  Increase the value of this parameter
 if many of the server resources are used simultaneously.

 Note:  The server uses some of the value specified with the maxsessopens
 parameter for internal processing, so the entire value specified with this
 parameter is not available to the user.

       Default value:  80

       Minimum value:  1

       Maximum value: 8000 (must be less than maxopens)


ΓòÉΓòÉΓòÉ 8. Traffic ΓòÉΓòÉΓòÉ

Byte traffic is the total bytes transferred during the sample. The chart
provides you with the traffic on a per minute basis. If bytes transferred, mean
time and file accesses rise and fall together you may be having excessive disk
activity that should be reduced.

SRVANNDELTA varies the time in milliseconds used by the server to announce
itself. Increase  the number ( max 65535 ) to reduce network traffic.

       Default value:  3000

       Minimum value:  0

       Maximum value:  65535


ΓòÉΓòÉΓòÉ 9. Inbound Traffic ΓòÉΓòÉΓòÉ

The number of bytes received by the server across the network.

See Traffic


ΓòÉΓòÉΓòÉ 10. Outbound Traffic ΓòÉΓòÉΓòÉ

The number of bytes sent by the server across the network.

See Traffic


ΓòÉΓòÉΓòÉ 11. Request Buffers ΓòÉΓòÉΓòÉ

The number of times the server required a Request Buffer but failed to allocate
one. When the system runs short of these buffers it will break up a BIG buffer
to alleviate the short fall. The BIG buffer is never returned to its former use
when the shortage is over.

Request buffer exhausted indicates the system has run out of REQ BUFFERS. If it
never happens the memory allocated may be used for other purposes such as a
disk cache. They default to 4096 bytes with the IBMLAN.INI entry of SIZREQBUF.
The default number of NUMREQBUF is 36 for a total of 146,456 bytes. Usually you
need to increase the number of buffers as you increase users. Each active
requester should have 2 request buffers. If they become exhausted the system
will break up a BIG BUFFER to add to the pool.

Request buffers are managed by two enries in the IBMLAN.INI file.

 NUMREQBUF size determined by sizreqbuf  they are used by the server to take
requests. It should be one of the first parameters checked if there is a
performance problem. There should be enough request buffers available to handle
peak requester workload.

  (sizreqbuf + 260) * numreqbuf < 5MB

Setting the numreqbuf value too high may cause excessive swapping  since
request buffers are locked in physical memory and cannot be swapped..

       Default value:  36

       Minimum value:  5

       Recommended maximum value: 300

 The server should have enough to handle the peak period of requester activity.
 You should allocate at least 2 per requester and an additional 2 per named
 pipe in use.

 SIZEREQBUF sets the size, in bytes of request buffers.  This parameter should
 be the same for every server on the network as well as  the sizworkbuf  on
 each requester.

   (sizreqbuf + 260) x numreqbuf < 5MB

       Default:  4096

       Minimum value:  1024

       Maximum value:  32768


ΓòÉΓòÉΓòÉ 12. Big Buffers ΓòÉΓòÉΓòÉ

Big buffer allocations are the number of times the system has run out of BIG
BUFFERS. If it never happens the memory allocated may be used for other
purposes such as a disk cache. These buffers are used for large file sequential
access. If your users do short random reads to the server ( DATA BASE ) you may
have too many. Remember that each buffer is 64k and the system default is to
have 12. Unless you changed the default about 768k is allocated. The IBMLAN.INI
entry is NUMBIGBUF.

Notification that a Big Buffer failed to allocate. These buffers are used while
loading programs and copying files. A shortage of these buffers will cause the
server to move large files slowly to the requesters. These buffers are used for
large file seque ntial access. If your users do short random reads to the
server ( DATA BASE ) you may have too many. Since each big buffer takes up
64KB, do not allocate more big buffers than the server memory can support.

If you never exhaust Big Buffers it may indicate that the memory allocated
might be used for other purposes such as a larger disk cache.  Remember that
each buffer is 64k and the system default is to have 12. Unless you changed the
default, 768k is alloca ted.

The IBMLAN.INI entry is NUMBIGBUF.

NUMBIGBUF are used by the system for large sequential file accesses when the
system switches to RAW BLOCK PROTOCOL. If you exhaust them increase the number
to get these requests serviced faster. On the other hand if they never exhaust
you may be using memory for them needlessly.

For LAN Server-Entry, the size of a big buffer is fixed at 64KB.  If  the big
buffers resource is never exhausted, reduce the numbigbuf parameter value.
Repeat this process until the server occasionally uses all the big buffer
resource during peak workload times.

In LAN Server-Advanced, 64KB buffers (up to 16) are allocated as needed.
Numbigbuf  should be set to 0 if  the server only accesses 386 HPFS files and
does no printing. If you want the system to balance this number dynamically
consider changing the Server Heuristics parms.

       Default value:  12

       Minimum value:  0

       Maximum value:  80


ΓòÉΓòÉΓòÉ 13. Print Jobs ΓòÉΓòÉΓòÉ

Print jobs is a count of print data being spooled to the server. You may not
have much control of the volume but should recognize as print activity
increases  bytes being received, and disk activity will also. If the spool is
on the same drive as the data,  increased activity can cause a bottleneck and
increase mean response time.

The IBMLAN.INI entry to increase the number of threads to handle printing is
the number of file tasks.

NUMFILETASKS is the number of concurrent processes to handle file and print
requests. There are 48 threads per task. Only increase this number when you get
an error in the log indicating the server exhausted its threads.

       Default value:  1

       Minimum value:  1

       Maximum value:  8


ΓòÉΓòÉΓòÉ 14. System Errors ΓòÉΓòÉΓòÉ

Notification on LAN Server reported system errors.

LAN Server maintains an error log. The log maintains a record of problems that
occur during operation.

The error count presented here were provided by the LAN SERVER API and may not
correlate directly to the error log.