Intel SRCU32 - RAID Controller, Руководство пользователя

Страница: 68 / 182

68 Intel RAID Controller SRCU32 User’s Guide
“Cache Memory Allocator Out of Available Memory” in PCI-ISA
Systems
PCI systems which are not equipped with an EISA Bus behave in the same way as an ISA
mainboard with regard to the available RAM memory. NetWare therefore does not automatically
recognize the available memory above 16 MB. The command
register memory
allows the
registration of memory above 16 MB. Memory shortage can appear while loading several
applications simultaneously on the server, especially where large volumes are concerned. This is
because the register memory command is normally carried out in the “autoexec.ncf” file. This is
usually located in the SYS volume. An “autoexec.ncf” file placed in the DOS partition of the
NetWare Server helps to get around this problem. To carry out this process, the hard driver must be
removed from the “startup.ncf” and inserted into the “autoexec.ncf” in the DOS partition. After
completing this process, the hard driver must be loaded directly after the register memory command
as indicated in the following “autoexec.ncf” file example:
register memory 1000000 1000000
LOAD C:SRCRP312
....
An additional start file can be loaded on the SYS volume for differentiation, for example, with the
name “autonet.ncf.”
Installing NetWare 4.1 - Wrong Drive Name
The following problem often occurs when installing NetWare 4.1 server. While copying the
module “cdrom.nlm,” the system hangs. This problem only occurs when the CD-ROM drive’s
name under MS-DOS is “cdrom.” For example, the config.sys/autoexec.bat contains the
following files:
DEVICE=aspicd.sys /D:cdrom
and
mscdex /D:cdrom
To avoid this problem, change the CD-ROM’s name in DOS to another name. For example, use:
/D:scsicd’ instead of ’/D:cdrom
NetWare-Server Not Stable When Under High Utilization
High server utilization combined with a large number of applications running on the server can lead
to an increase in the number of dirty cache buffers resulting in an unstable server. To avoid this
situation, modify the following parameters.
•
Increase the number of concurrent disk cache writes for the disk subsystem. Set maximum
concurrent disk cache writes. This parameter can be increased up to 500 for high performance
controllers and fast hard drives.
•
Decrease the delayed write standard parameter. Set dirty disk cache delay time. This
parameter sets the time where dirty buffers are written (flushed) from the cache of NetWare to
the hard drive. The minimum value is 0.8 seconds. Care should be taken not to go below
0.8 seconds because this value influences server performance substantially.