Make your own free website on Tripod.com

 Independent Advanced Revelation Support

 Home


NOVELL CONFIGURATION PARAMETERS

 

These are GENERAL guidelines that were developed by system engineers under NetWare 3.11. The guidelines are expected to be helpful with versions 3.12 and 4.1 also.

Command syntax

 
bulletSET (displays all setable parameters)
bulletSET parameter name (displays current setting)
bulletSET parameter name=value (sets parameter to specified value)

NOTE: Adjusting any Cache or Buffer settings may affect available memory for NLM's. Adjusting timings will affect system performance due to the server having to service processes either more often (if increased frequency) or less (if decreased frequency).

 

Minimum Packet Receive Buffers

 
bulletWhere used: STARTUP.NCF only
bulletDefault: 10
bulletLimits: 10 to 1000
bulletDescription: minimum number of packet receive buffers allocated by the server
bulletRecommendation: Adjust upwards if your server is under heavy loads and problems start. Use in conjunction with the Maximum packet Receive Buffers to set the Min and Max for performance.

 

Maximum Packet Receive Buffers

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 100
bulletLimits: 50 to 2000
bulletDescription: maximum number of packet receive buffers that can be allocated by the server.
bulletRecommendation: Adjust upwards if your server is under heavy loads and problems start to show up that indicate lost packets.

 

New Packet Receive Buffer Wait Time

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 0.1 seconds
bulletLimits: 0.1 to 20 seconds
bulletDescription: minimum time to wait before allocating a new packet receive buffer
bulletRecommendation: Insure that it is set low as possible (i.e. the default) to insure quick performance from the system towards packet responses.

 

Cache Buffer Size

 
bulletWhere used: STARTUP.NCF only
bulletDefault: 4096 bytes
bulletLimits: 4096 to 16,384 bytes
bulletDescription: size of the file cache buffers
bulletRecommendation: Adjust upwards if you have specified large frame sizes in your system.

 

Dirty Disk Cache Delay Time (Advanced)

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 3.3 seconds
bulletLimits: 0.1 to 10 seconds
bulletDescription: minimum amount of time the system waits before writing a not completely dirty disk cache buffer
bulletRecommendation: Set to minimum if you are experiencing hanging or truncation problems.

 

Dirty Directory Cache Delay Time (Advanced)

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 0.5 seconds
bulletLimits: 0 to 10 seconds
bulletDescription: minimum time the system waits before writing a dirty directory cache buffer
bulletRecommendation: Set to minimum if problems show up on your system with particular Advanced Revelation volumes.

 

Minimum Directory Cache Buffers

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 20
bulletLimits: 10 to 2000
bulletDescription: minimum number of directory cache buffers to be allocated by the server before delaying
bulletRecommendation: If you have large numbers of Advanced Revelation volumes, you may want to increase this number. This would be in conjunction with Maximum Directory Cache Buffers.

 

Maximum Directory Cache Buffers

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 500
bulletLimits: 20 to 4000
bulletDescription: maximum number of directory cache buffers that can be allocated by the system
bulletRecommendation: If you have large numbers of Advanced Revelation volumes, you may want to increase this number.

 

Volume Low Warn All Users

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: ON
bulletLimits: ON | OFF
bulletDescription: send volume low warning to all users
bulletRecommendation: Set this off if you have a dedicated indexer or batch processor and are getting out-of-disk-space messages from non-AREV data volumes that are not critical. It can effectively hang your system if the indexer gets the message from a volume other than a true data volume (i.e. a users volume).

 

Maximum File Locks

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 10,000
bulletLimits: 100 to 100,000
bulletDescription: system wide maximum number of file locks (including open files)
bulletRecommendation: On systems that use file locking extensively, you will want to set this value higher. This is a server-based setting. (i.e. the total number of file locks the server can offer ALL stations).

 

NOTE: Whereas AREV uses 2 DOS files for each AREV file, we use a special OV lock for accessing overflow files. Do not consider this as 2 * . It should be a 1 AREV file-lock to 1 Maximum File Locks.

Maximum File Locks Per Connection

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 250
bulletLimits: 10 to 1000
bulletDescription: maximum number of file locks per connection (including open files)
bulletRecommendation: Again, if a system uses file locking extensively for large quantities of files, you may need to adjust this parameter.

 

Maximum Record Locks

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 20,000
bulletLimits: 100 to 200,000
bulletDescription: system-wide maximum number of record locks (physical, logical and semaphores)
bulletRecommendation: If you are locking large quantities of records, you may need to adjust this parameter. This is the maximum number of locks that a server can handle at one time.

 

Maximum Record Locks Per Connection

 
bulletWhere used: console and AUTOEXEC.NCF
bulletDefault: 500
bulletLimits: 10 to 10,000
bulletDescription: maximum number of record locks per connection (physical, logical and semaphores)
bulletRecommendation: If your application uses a lot of locks (potentially more than 500 at any time), you may need to increase this parameter.

 

Display Incomplete IPX Packet Alerts

 
bulletWhere used: console, AUTOEXEC.NCF and STARTUP.NCF
bulletDefault: ON
bulletLimits: ON | OFF
bulletDescription: display alert messages when IPX receives incomplete packets
bulletRecommendation: Leave this ON! If your system is receiving bad packets, you can check to see who is having the problem with this log.
 

Revelation , Advanced Revelation , AREV and Open Insight are trademarks of Revelation Technologies, Inc.   All other products mentioned are registered trademarks or trademarks of their respective companies.

Questions or problems regarding this web site should be directed to the WebMaster.
Copyright 2000 TARDIS Systems . All rights reserved..