NetWare server Optimization, (the basics)

things to look at first, especially if the server seams to be running slow.

Things to Check; LRU sitting time, Cache Buffers, LAN Traffic Jams, TIDs

Also make sure there aren't any RConsole sessions left open in the background on any systems as that can really slow down systems

LRU Sitting Time (for servers with Traditional Volumes, NSS is a whole other thing that still need to document)
in the Console Monitor
'Available Options'
'Disk cache utilization'
look at the entry (5th down) of 'LRU sitting time:'
that time should generally be several hours
if you see it below 30 minutes on any kind of frequency during the day then you'd benefit from more RAM in the server.

notes about 'LRU Sitting time'

it will always be less than the server up time so don't bother with it right after a reboot

large data flows like the backup or a large restore will tend to flush the cache resulting in a low time, normally this is not a problem and is just the reasoning why you try not to do those things during the business day

also check that the server is actually seeing all the RAM. At the server prompt, type in 'Memory'. If it is radically different than what it should be check the following things:

make sure that no memory managers or drivers are being loaded in DOS. Ex. himem.sys, emm386.exe, CD-ROM drivers, etc.
run the hardware configuration and a simply run of hardware diags. The memory may not have been recognized properly.
Check the c:\nwserver\startup.ncf, any Autoexec.ncf on C:, and sys:\system\autoexec.ncf for any 'register memory' lines and REMark then all out

Cache Buffers
in the Console Monitor
if the screen is evenly split in half horizontally, press TAB
make note of how many 'Packet receive buffers:' and 'Directory cache buffers:' are in use
press TAB, and scroll down to 'LAN/WAN information'
check each NIC for 'No ECB available count:' (is slightly different for NW5) and make sure it is Zero, otherwise you need to make changes below. Back out to the main Monitor menu
scroll down to the bottom for 'Server parameters'
select, Communications,
part way down, you'll see 'Maximum Packet Receive Buffers' & 'Minimum Packet Receive Buffers'
make sure that the min is near the number you recorded and that the max is more than twice that
Esc. once and then select 'Directory caching'
part way down, you'll see 'Maximum Directory Cache Buffers' & 'Minimum Directory Cache Buffers'
make sure that the min is near the number you recorded and that the max is more than twice that

LAN Traffic Jams

Under Monitor, check the LAN/WAN information/Drivers to make sure that there aren't any errors. There should be no collisions on a full Duplex Switched environment, otherwise there will certainly be a good number for the typical EtherNet LAN.

If you are still running IPX on the server(s) and have any MS Windows in the environment, then there is a setting that can significantly affect Broadcast storms. For all NetWare servers running IPX that are not operating as a router, IPX NetBIOS Replication Option should be set to 0(zero). If you are not using the NetWare servers to route Microsoft NetWrecking packets, then it can set that to 0 on all the NetWare servers. Otherwise should be set to 3. If in doubt just set to 0 after hours and see if anything breaks. This can also be configured in INETCFG, Protocols, IPX, Expert Configuration Options:, Advanced Packet Type 20 Flooding:
IPX NetBIOS Replication Option (Advanced Packet Type 20 Flooding) Explained TID 10027840

Make sure eDirectory is healthy

Novell's TID 3564075 (Formerly TID 10060600) says it all.
Note that eDirectory was previously known as NDS (Novell/NetWare Directory Service) but it has grown well beyond those beginings now running on various Linux distros and Windows.

Make sure the config.sys has good settings

There should be no memory management in the DOS bootup, and generally there shouldn't be any drivers loading from the config.sys or autoexec.bat. What should be in the Config.sys are 'Files=X' and 'Buffers=Y' where those numbers should always be over 50, and I'm finding that having them both to 100 works very well. Until the later patches of NetWare 5.1 we didn't need to worry too much about those two settings, but the increase reliance on Java does push those needs for some odd reason.
Check the version of DOS used, if Windows 9x (aka DOS 7), you'd best replace it as in my NetWare best practices

Novell TIDs and other documents of relevance

NetWare Performance Troubleshooting and Tuning Guide TID10018661 (says for TCPIP but is really good for all tuning)

NetWare Performance, Tuning and Optimization TID10012765

Increasing Performance of Backups TID 10023910. While focused on ARCserve, it has much usefulness for all backup/restore issues.

Before calling support for OS Issues 2938836

Before calling support for DS Issues 2938838

Before calling support on Client Issues 2939526

If you are still having problems and are using ARCserve use the great document about ARCserve issues from CA
otherwise for click here for more advanced NetWare optimization or get one of our senior techs involved.