1.154 SET

Purpose

Use at the server console to view and configure operating system parameters.

HINT:You can also modify server parameter values from Monitor's Available Options, and then Server Parameters or using the Set Parameter link in Novell Remote Manager.

The default SET parameter values give maximum performance for most systems. Server parameter values should seldom need to be modified.

Syntax


set [parameter]  [value]

Parameter Categories

Using SET

Although most default values of the server parameters don't need to be modified, you might increase the performance of your system by adjusting the values of certain parameters. Suggestions for improving server performance can be found in Optimizing the NetWare Server and Setting Server Parameter Values in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Server parameter settings are persistent in NetWare. If the server goes down, any settings that you have made to tune your server for performance will not be lost.

Displaying and Changing Current Settings

You can also use the Monitor utility to modify server parameter values. See Section 1.94, MONITOR.

Entering Parameters

Parameters That Control the Allocation of Services

Some SET parameters control how the system dynamically allocates services. Three types of parameters interact to control the allocation of a service:

Common File System Parameters

Common File System Parameters contain parameters that apply to both the NSS file system and the NetWare Traditional file system. For a description of file system parameters, see the following table.

Table 1-3 Common File System Parameters

Parameter

Use to

Maximum Transactions number

Specify how many transactions can occur at the same time.

Supported values: 100 to 10000Default: 10000

Owning NLM: filesys.nlm

Maximum Concurrent Directory Cache Writes number

Specify how many write requests from directory cache buffers are put in the elevator before the disk head begins a sweep across the disk.

Supported values: 5 to 500Default: 75

A high number creates more efficient write requests. A low number creates more efficient read requests.

Owning NLM: filesys.nlm

Minimum File Delete Wait Time time

Specify how long a deleted file remains salvageable on the volume.

Supported values: 0 seconds to 7 daysDefault: 1 minute 5.9 seconds

Files deleted for less than this minimum aren't automatically purged even if the volume is full and users can't create new files.

Owning NLM: filesys.nlm

Immediate Purge of Deleted Files value

Supported values: On, OffDefault: Off

If this parameter is set to On, all files are purged immediately when they are deleted.

Owning NLM: filesys.nlm

Compression Daily Check Stop Hour number

Specify the hour when you want the file compressor to stop scanning enabled volumes for files that need to be compressed.

Supported values: 0 to 23Default: 6

Hours are specified by a 24-hour clock: (0 midnight; 23 11 p.m.).

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Compression Daily Check Starting Hour number

Specify the hour when you want the file compressor to start scanning enabled volumes for files that need to be compressed.

Supported values: 0 to 23Default: 0

Hours are specified by a 24-hour clock: (0 midnight; 23 11 p.m.).

Note: If the Compression Daily Check Stop Hour parameter is the same as the Compression Daily Check Starting Hour, then the file compressor starts checking every day at the Compression Daily Starting Hour time and runs as long as necessary to finish all files that meet the compressible criteria.

This parameter can be set in the startup.ncf file.

Minimum Compression Percentage Gain number

Set the minimum percentage a file must compress to remain in a compressed state.

Supported values: 0 to 50Default: 20

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Enable File Compression value

Specify whether file compression is suspended.

Supported values: On, OffDefault: On

On allows file compression on compression-enabled volumes.

Off suspends compression; immediate compress requests are queued until the value is reset to On, when the files meeting criteria are compressed.

This parameter can be set in the startup.ncf.

Owning NLM: filesys.nlm

Maximum Concurrent Compressions number

Specify the maximum concurrent or simultaneous compressions allowed.

Supported values: 1 to 8Default: 2

Concurrent compressions can occur only if there are multiple volumes.

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Convert Compressed to Uncompressed Option value

Specify what the file system does with an decompressed version of a file after the server has decompressed it.

Supported values:

0 Always leave the file compressed 1 Leave the file compressed until second access if it is read only once during the time specified by the Days Untouched Before Compression parameter 2 Always leave the file decompressed

Default: 1

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Decompress Percent Disk Space Free to Allow Commit number

Specify the percentage of free disk space required on a volume for file decompression to permanently change compressed files to decompressed.

Supported values: 0 to 75Default: 10

This parameter prevents newly decompressed files from filling up the volume.

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Decompress Free Space Warning Interval number

Specify the time between alerts when the file system is not changing compressed files to decompressed because of insufficient disk space. Setting the interval to 0 turns off the alert.

Supported values: 0 seconds to 29 days 15 hours 50 minutes 3.8 seconds Default: 31 minutes 18.5 seconds

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Deleted Files Compression Option number

Specify whether and when deleted files are compressed.

Supported values:

0 Don't Compress deleted files 1 Compress deleted files the next day 2 Compress deleted files immediately

Default: 1

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Days Untouched Before Compression number

Specify the number of days the system waits after a file was last accessed before it is compressed.

Supported values: 0 to 100000Default: 14

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Communications Parameters

Communication parameters control settings for communication buffers. Four parameters configure packet receive buffers; four control the watchdog.

For a description of communications parameters, see Table 1-4.

Table 1-4 Communications Parameters

Parameter

Use to

IPX CMD Mode Routing value

Control whether IPX CMD Mode Routing is on or off.

Supported values: On, OffDefault: Off

Owning NLM: ipxspx.nlm

IPMGMT Push Pull Interval number

Change the time (in seconds) between change in the configuration and its effect.

Supported values: 1 to 5Default: 2

Recommended: If you find that your configuration change is reverted to the old one after refresh, increase this time.

Owning NLM: ipmgmt.nlm

IPMGMT Fetch Expiry Time number

Change the expiration time (in seconds) of IPMGMT Fetch operation.

Supported values: 1 to 60Default: 5

Recommended: If a lesser number of applications is shown on the IP Management page than the actual number of applications that are running on the server, increase the time.

Owning NLM: ipmgmt.nlm

Maximum Pending TCP Connection Requests number

Change the maximum number of pending TCP connections.

Supported values: 128 to 4096Default: 128

Owning NLM: bsdsock.nlm

PGM Socket Send Buffer Size number

Set the PGM Socket default send buffer size (in bytes).

Supported values: 102400 to 1073741824Default: 400*1024 bytes

Owning NLM: bsdsock.nlm

BSD Socket default Buffer Size in Bytes number

Set the BSD Socket default send and receive buffer size (in bytes).

Supported values: 4096 to 1073741824Default: 32768 bytes

Owning NLM: bsdsock.nlm

Discard Oversized Ping Packets value

Specify whether or not to discard ping packets larger than the current setting of largest ping packet size.

Supported values: On, OffDefault: On

  • On Discard

  • Off Do not discard

Owning NLM: tcpip.nlm

Largest Ping Packet Size number

Set the largest ping packet size that can be received.

Supported values: 0 to 36992Default: 10240

The upper limit is under assumption that MTU is 1500 (Ethernet).

Owning NLM: tcpip.nlm

TOS for IP packets number

Set TOS in the IP header for all outgoing packets for all interfaces.

Supported values: 0 to 127Default: 0

Owning NLM: tcpip.nlm

Arp entry update time number

Change the update time (in seconds) of Arp Entries.

Supported values: 240 to 14400Default: 300 (5 minutes)

Recomended: The Arp entry update time should be greater than or equal to the Arp entry expiration time.

Owning NLM: tcpip.nlm

Arp entry expiry time number

Change the expiration time (in seconds) of Arp Entries.

Supported values: 240 to 14400Default: 300 (5 minutes)

Recomended: The Arp entry expiration time should be less than or equal to the Arp entry update time.

Owning NLM: tcpip.nlm

ICMP Redirect Timeout number

Set the time period (in minutes) for expiring ICMP redirect learned routes.

Supported values: 0 to 525600 (1 year)Default: 3

A setting of 0 disables route learning from ICMP redirects.

Owning NLM: tcpip.nlm

Largest UDP Packet Size number

Set the largest UDP packet size that can be received.

Supported values: 0 to 36992Default: 16384

The upper limit is under assumption that MTU is 1500 (Ethernet).

Owning NLM: tcpip.nlm

Discard Oversized UDP Packets value

Specify whether to discard UDP packets larger than the current setting of Largest UDP Packet Size.

Supported values: On, OffDefault: On

  • On Discard

  • Off Do not discard

Owning NLM: tcpip.nlm

TCP UDP Diagnostic Services value

Start or stop diagnostic servers over TCP and UDP (Echo/Chargen/Discard).

Supported values: On, OffDefault: Off

Owning NLM: tcpip.nlm

TCP Path MTU Black Hole Detection and Recovery value

Enable or disable Path MTU Black Hole Detection and Recovery feature.

Supported values: On, OffDefault: Off

  • On Enable

  • Off Disable

Owning NLM: tcpip.nlm

TCP Max Port Limit number

Modify the upper limit of TCP ephemeral port range.

Supported values: 4999 to 54999Default: 54999

Owning NLM: tcpip.nlm

TCP Sack Option value

Enable or disable Sack support. This option does not change the behaviour of existing connections.

Supported values: On, OffDefault: On

  • On Enable

  • Off Disable

Owning NLM: tcpip.nlm

TCP Large Window Option value

Enable or disable Large Window support. This option does not change the behaviour of existing connections.

Supported values: On, OffDefault: On

  • On Enable

  • Off Disable

Owning NLM: tcpip.nlm

TCP Defend Land Attacks value

Defend against TCP/UDP Land Attacks.

Supported values: On, OffDefault: On

  • On Defend

  • Off Do not defend

Owning NLM: tcpip.nlm

TCP Secure ISN value

Enable or disable the use of a secure algorithm for generating TCP Initial Sequence Numbers. This option does not change the behaviour of existing connections.

Supported values: On, OffDefault: On

  • On Discard

  • Off Do not discard

Owning NLM: tcpip.nlm

Maximum RIP SAP Events number

Specify the maximum number of RIP/SAP process time events (such as RIP/SAP consumption) allowed before guaranteeing that a thread switch will occur.

Supported values: 1 to 100000Default: 100

Owning NLM: ipxspx.nlm

IPX Router Broadcast Delay number

Specify how long (in ticks) the IPX router should delay between SAP/RIP broadcast packets.

Supported values: 0 to 2Default: 0

  • 0 Adjust delay to size of SAP/RIP tables

  • 1 Delay 1 tick

  • 2 Delay 2 ticks

Owning NLM: ipxspx.nlm

IPX NetBIOS Replication Option number

Control how the IPX router deals with NetBIOS replicated broadcasts.

Supported values: 0 to 3Default: 2

  • 0 Do not replicate NetBIOS replicated broadcasts.

  • 1 Replicate NetBIOS replicated broadcasts using the "old" algorithm (which causes duplicate broadcasts when there are redundant routes).

  • 2 Replicate NetBIOS replicated broadcasts using the "new" algorithm (which squelches duplicate broadcasts but doesn’t go as far).

  • 3 Use the same replication as method 2, but do not replicate NetBIOS replicated broadcasts to WAN links.

Owning NLM: ipxspx.nlm

Use Old Watchdog Packet Type value

Use type 0 instead of type 4 for watchdog packets. Some old router hardware will filter out type 4 IPX packets that can cause a client to lose its connection to the sever when it sits inactive for a few minutes..

Supported values: On, OffDefault: Off

Owning NLM: ipxspx.nlm

Reply to Get Nearest Server value

Specify whether the server responds to GET NEAREST SERVER requests from workstations that are attempting to locate a server.

Supported values: On, OffDefault: On

Owning NLM: ipxspx.nlm

Number of Watchdog Packets number

Specify the number of unanswered watchdog packets that the server sends to a workstation before closing its connection.

Supported values: 5 to 100Default: 10

Owning NLM: connmgr.nlm

Delay Between Watchdog Packets time

Specify the amount of time between watchdog packets.

Supported values: 9.9 seconds to 10 minutes 26.2 seconds Default: 59.3 seconds

After a server sends out the first watchdog packet, it waits the specified time before sending out succeeding packets if it receives no reply.

Owning NLM: connmgr.nlm

Delay Before First Watchdog Packet time

Specify the amount of time the server waits without receiving a request from a workstation before sending out the first watchdog packet to that station.

Supported values: 15.7 seconds to 14 daysDefault: 4 minutes 56.6 seconds

Owning NLM: connmgr.nlm

Console Display Watchdog Logouts value

Specify whether a console message is displayed when a connection is cleared.

Supported values: On, OffDefault: Off

If your network is running smoothly, you don't need to display watchdog logouts.

If your workstations are having connection problems, the watchdog logout messages can help you isolate which stations aren't receiving or sending watchdog packets.

Owning NLM: connmgr.nlm

Maximum Packet Receive Buffers number

Specify the maximum number of packet receive buffers the operating system can allocate.

Supported values: 50 to 3303820Default: 10000

Before increasing this parameter, use MONITOR to view the server's use of packet receive buffers and service processes.

If the number of packet receive buffers is at maximum, increase this parameter in increments of 10 until you have one packet receive buffer per workstation.

If you have EISA or microchannel bus master boards in your server, increase this parameter to provide at least five buffers per board.

If the board is producing No ECB available count errors, provide 10 buffers per board. Use MONITOR (LAN/WAN Drivers) to determine whether the board is producing errors.

If the number of allocated service processes is at maximum, you can increase the Maximum Service Processes parameter to decrease the need for more packet receive buffers.

The value of this parameter should be greater than the value of the Minimum Packet Receive Buffers parameter. If it is less, the system increases the value to match that of the Minimum Packet Receive Buffers parameter.

This parameter can be set in the appropriate startup file.

Owning NLM: lsl.nlm

Minimum Packet Receive Buffers number

Specify the minimum number of packet receive buffers the operating system can allocate. The operating system allocates this number of buffers as soon as the server boots. You must add this command to the startup.ncf file. You cannot change the setting at the console prompt.

Supported values: 10 to 32768Default: 2000

Before increasing this parameter, use Novell Remote Manager or MONITOR to view the server's use of packet receive buffers.

If you have EISA or microchannel bus master boards in your server and are receiving No ECB available count errors (see LAN/WAN Drivers in Section 1.94, MONITOR) right after the server boots, increase this parameter so that each board can have at least five packet receive buffers.

If the allocated number is higher than 10 and the server doesn't respond immediately after booting, increase this parameter.

The value of this parameter must be less than the value of the Maximum Packet Receive Buffers parameter. If it is greater, the system increases the value of the Maximum Packet Receive Buffers parameter to match that of the Minimum Packet Receive Buffers parameter.

Owning NLM: lsl.nlm

Maximum Physical Receive Packet Size number

Specify the maximum size of packets that can be transmitted on the network.

IMPORTANT:You must add this command to the startup.ncf file. You cannot change the setting at the console prompt or by using any other utilties.

Supported values: 618 to 65642Default: 4224

The default allows 2 KB (data with the packet header). If you use token ring or Ethernet boards, the default is acceptable.

If some of your network boards transmit more than 512 bytes of data per packet, set this parameter for the largest packet size.

Owning NLM: lsl.nlm

New Packet Receive Buffer Wait Time time

Specify how long (in seconds) the operating system waits after receiving a request for a packet receive buffer before granting a new buffer.

Supported values: 0 seconds to 20Default: 0

This parameter prevents the system from granting too many buffers during a sudden peak in usage.

If you have an EISA bus master board in your server, don't change this parameter.

Owning NLM: lsl.nlm

Maximum Interrupt Events number

Specify the maximum number of interrupt time events (such as IPX routing) allowed before a thread switch is guaranteed to have occurred.

Supported values: 1 to 1000000Default: 10

Owning NLM: lsl.nlm

Directory Services Parameters

Directory services parameters allow you to do the following:

For descriptions of directory services parameters, see the following table.

Table 1-5 Directory Services Parameters

Parameter

Use to

NDS Trace to Screen value

Enable the DS trace screen; this displays information about eDirectory events on the monitor.

Supported values: On, OffDefault: Off

Owning NLM: ds.nlm

NDS Trace to File value

Send messages about eDirectory events to the eDirectory trace file on volume sys:. The default file is system:\dstrace.dbg.

Supported values: On, OffDefault: Off

The file path and name can be changed with the eDirectory Trace Filename parameter.

The file is circular; it grows to a maximum length of approximately 500 KB and then starts to overwrite itself at the beginning of the file.

If this parameter is set to On, the trace information is also scrolled on the screen.

Owning NLM: ds.nlm

NDS Trace Filename path\name

Specify the path and name of the DS trace file on volume sys:.

Maximum length: 254

Default: system:\dstrace.dbg

Owning NLM: ds.nlm

Bindery Context context;context

Specify one or more containers to be used by eDirectory when it provides bindery services.

Maximum: 2047 characters, 16 contexts

Multiple contexts are separated by semicolons ( ; ). Whatever string it specified is set. To make that string effective for all valid contexts, make sure the container you specify in the context is present on that server.

Example: set bindery context ou=sales_la.ou=sales. o=novell_us;ou=accounting.o=novell

This parameter can be set in the startup.ncf file.

Owning NLM: server.nlm

NDS External Reference Life Span number_in_hours

Specify how long (in hours) unused external references are allowed to exist before being removed.

Supported values: 1 to 384Default: 192

External references are local IDs assigned to users when they access other servers. When users no longer have access, the external references should be removed.

Owning NLM: ds.nlm

NDS Inactivity Synchronization Interval number_in_minutes

Specify the maximum elapsed time (in minutes) between exhaustive synchronization checks. As soon as you change this value, the system executes the synchronization check. Synchronization checks then recur at the specified interval.

Supported values: 2 to 1440Default: 60

If the system has replicas across a WAN link, this value should be set as high as 240 (4 hours) to reduce WAN traffic.

Owning NLM: ds.nlm

NDS Synchronization Restrictions value, version_number_list

Specify which versions of eDirectory the server can synchronize with.

Supported values: Off; On, list of version numbers (Maximum length of version number list: 131 characters)

Default: Off

To determine what version is currently loaded on a server, enter modules at the server prompt. The eDirectory version number is displayed under the heading ds.nlm.

If this parameter is set to Off, the server synchronizes with all versions available.

If this parameter is set to On, the server synchronizes only with those versions specified as parameters to the On value.

Example: On,420,421

Owning NLM: ds.nlm

NDS Servers Status value

Mark the status of all Server objects in the local namebase as up or down.

Supported values: Up, Down

Use this parameter to reset the status of all the servers if the status of one server isn't accurately recognized by the system.

For example, if a server is up but the system recognizes it as down, set this parameter to mark all servers as up.

Subsequently, the system would reassess the status of all servers and change the status to down for those servers that were truly down.

Owning NLM: ds.nlm

NDS Janitor Interval number_in_minutes

Specify the interval (in minutes) at which the janitor process is executed. The janitor process is executed as soon as you change this value and then recurs at the specified interval.

Supported values: 1 to 10080Default: 720

The janitor process cleans up unused records, reclaims disk space, and purges objects flagged for deletion.

Owning NLM: ds.nlm

NDS Distributed Reference Link Interval number_in_minutes

Specify the interval (in minutes) at which distributed reference link consistency checking is performed. Distributed reference link consistency checking is executed as soon as you change this value. It then recurs at the specified interval.

Supported values: 2 to 10080Default: 780

A distributed reference link indicates that an object in a partition has an ID in that partition where the actual object doesn't exist.

This process creates needed distributed reference links and deletes unnecessary ones.

Owning NLM: ds.nlm

NDS Bindery QOS mask number

Select which objects should be subject to bindery QOS delay. This switch should be used with the NDS Bindery QOS delay switch.

Supported values: 0 to 4294967295Default: 8

Owning NLM: ds.nlm

NDS Bindery QOS delay number_in_milliseconds

Set the delay (in milliseconds) after sucessfuly finding bindery objects. This switch should be used with the NDS Bindery QOS mask switch.

Supported values: 0 to 60000Default: 150

Owning NLM: ds.nlm

NDS Backlink Interval number_in_minutes

Specify the interval (in minutes) at which backlink consistency checking is performed. Backlink consistency checking is executed as soon as you change this value. It then recurs at the specified interval.

Supported values: 2 to 10080Default: 780

A backlink indicates that an object in a replica has an ID on a server where the replica doesn't exist.

This process creates needed backlinks and deletes unnecessary ones.

Owning NLM: ds.nlm

NDS Trace File Length to Zero value

Delete the contents of the trace file. This parameter does not delete the file itself. As soon as the file is cleared, the value of the parameter resets to Off.

Supported values: On, OffDefault: Off

To use this parameter, you must also set the eDirectory Trace to File parameter to On, because the trace file must be open for the system to delete its contents.

Owning NLM: ds.nlm

NDS Bootstrap Address address

Allow eDirectory to operate properly in the absence of SLP. When SLP is not available to advertise servers and partitions, the local server uses this value to set the bootstrap address that the server would use to find its tree and authenticate to it.

Format for IP Address: Use the standard IP format of four decimal values delimited by periods.

Example: 123.45.67.89 <:524> or 137.65.62.144 (port number is optional) This number is used for both TCP and UDP connections.

Format for IPX Address: Use the standard IPX format of hexadecimal digits representing Network, Node, and Socket.

Example: 12345678:23456789ABCD:0451 or 01010480:00001B1E983A:0451

Defaults apply to any field not present, where the default is current value.

Owning NLM: ds.nlm

Check Equivalent to Me value

Enforce checking of the Equivalent To Me attribute on eDirectory authentication.

Supported values: On, OffDefault: Off

If this parameter is set to On, DSRepair must be used to synchronize the Equivalence attribute and the Equivalent To Me attribute.

Setting this parameter to On might adversely affect communication performance.

Owning NLM: ds.nlm

Disk Parameters

Disk parameters control aspects of disk reads and writes.

For a description of disk parameters, see the following table.

Table 1-6 Disk Parameters

Parameter

Use to

Auto scan for devices value

Automatically scan for devices when a HAM is loaded. If turned off, operator must issue a Scan for New Devices on the command line before the devices will be seen.

Supported values: On, OffDefault: On

Owning NLM: nwpa.nlm

Auto load of CDM modules value

Automatically scan and load defined generic Custom Device Modules (CDMs). If turned off, the desired CDMs must be loaded manually or added to the startup.ncf file.

Supported values: On, OffDefault: On

Owning NLM: nwpa.nlm

Sequential Elevator Depth number

Set the maximum elevator depth for sequential requests.

Media Manager sends the number of sequential requests up to this value to the same device. When the device contains this number of requests and another device in the mirror group is empty, Media Manager begins sending requests to the idle device.

Supported values: 0 to 4294967295Default: 8

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Enable IO Handicap Attribute value

Enable drivers and applications to inhibit read requests from one or more devices.

Supported values: On, OffDefault: Off.

Setting this parameter to On enables the Inhibit attribute to function. Setting this parameter to Off prevents the attribute from functioning.

Do not set this attribute to On unless instructed to do so by a device manufacturer.

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Mirrored Devices Are Out of Sync Message Frequency time

Set the frequency (in minutes) for checking out-of-sync devices.

Supported values: 5 to 9999Default: 28

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Remirror Block Size number

Set the remirror block size in 4 KB increments. (1=4 KB, 2=8 KB, 8=32 KB, etc.)

Supported values: 1 to 8Default: 1

Owning NLM: mm.nlm

Concurrent Remirror Requests number

Set the number of remirror requests per Mirror object.

Supported values: 2 to 32Default: 32

Owning NLM: mm.nlm

Ignore Partition Ownership value

Specify whether partitions owned by other servers in a cluster can be activated on this server.

Setting this parameter to On allows partitions owned by other servers in the cluster to be activated on this server.

Supported values: On, OffDefault: Off

Owning NLM: mm.nlm

Ignore Disk Geometry value

Create nonstandard and unsupported partitions.

Supported values: On, OffDefault: Off

If you set this parameter to On before modifying or creating a partition, the software ignores disk geometry when creating the partition. This allows you to create nonstandard partitions.

Caution: Setting this parameter to On might harm other file systems contained on the disk.

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Multi-path Support value

Enable or disable support for multipath devices or adapter failover.

Supported values: On, OffDefault: Off

Owning NLM: mm.nlm

Enable Hardware Write Back value

Enable hardware write back, if supported.

Hardware write back means that I/O write requests might be cached at the device and succeeded before data is committed to the media. Hardware write back usually improves write performance.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Enable Disk Read After Write Verify value

Control whether information written to disk is read back and compared with the original data.

Supported values: On, OffDefault: Off

Setting this parameter to On might decrease performance significantly.

To set this value for currently loaded disks, use the Storage Devices option of MONITOR.

You can set this parameter in the startup.ncf file.

Owning NLM: mm.nlm

Auto LFVMount

Control whether any local FAT volumes not recognized by DOS are automatically mounted and assigned a local drive letter when they are detected.

Supported values: On, OffDefault: Off

On automatically mounts and assigns a local drive letter when the drive is detected.

When set to Off, you must use the LFVMOUNT comand to manually mount local FAT volumes.

Owning NLM: fatfs.nlm

Error Handling Parameters

Error handling parameters control the size of error logs and specify what happens when logs exceed the specified size. They also control how the server responds to an abend or to an NLM that does not unload from a protected address space.

For descriptions of error handling parameters, see the following table.

Table 1-7 Error Handling Parameters

Parameter

Use to

Server Log File State number

Control what happens when the sys$log.err file is larger than the size specified by the Server Log File Overflow Size parameter.

Supported values:

0 Leave sys$log.err as is 1 Delete sys$log.err 2 Rename sys$log.err

Default: 1

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Server Log File Overflow Size number

Specify the maximum size of the sys$log.err file before the action specified by the Server Log File State parameter occurs.

Supported values: 65536 to 4294967295Default: 4194304

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Boot Error Log File State number

Control what happens when the boot$log.err file is larger than the size specified by the Boot Error Log Overflow Size parameter.

Supported values:

0 Leave boot$log.err as is 1 Delete boot$log.err 2 Rename boot$log.err 3 Start a new log file whenever the server is restarted

Default: 3

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Boot Error Log File Overflow Size number

Specify the maximum size to which the boot$log.err file can grow before the action specified by the Boot Error Log File State parameter occurs.

Supported values: 65536 to 4294967295Default: 4194304

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Boot Error Log value

Specify which error messages from the console will be saved in the boot$log.err file.

Supported values: On, OffDefault: On

If you set this parameter to On, all error messages displayed on the console will be saved in boot$log.err.

If you set this parameter to Off, only error messages displayed during the boot procedure will be saved in boot$log.err.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Hung Unload Wait Delay number

Specify the amount of time the server waits for an NLM program to be unloaded from a protected address space after the unload address space command is executed. If the NLM is not successfully unloaded within this interval, the server displays a prompt to kill the address space.

Supported values: 0 seconds to 1 minute 58.3 secondsDefault: 30 seconds

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Auto Restart Down Timeout number

When the server tries to go down after an abend, it sets a timeout just in case there is a problem going down. Specify the amount of time (in seconds) that the server waits before automatically restarting.

Supported values: 0 to 600Default: 180

Owning NLM: server.nlm

Auto Restart After Abend Delay Time number

Specify the amount of time (in minutes) before the server is brought down after an abend, if the Auto Restart After Abend parameter is in effect.

Supported values: 2 to 60Default: 2

Regardless of what time is set, the server sends a message every two minutes to warn users that the server will be brought down.

Owning NLM: server.nlm

Auto Restart After Abend value

Specify the system's automatic response to an abend.

Supported values:

  • 0 The system does not respond to the abend.

  • 1 After an abend, the system determines the source of the abend. Based on findings, the system either keeps the computer running or shuts down the computer and attempts to restart it.

  • 2 After an abend, the system attempts to recover from the problem and restart the computer after the time specified by the Auto Restart After Abend Delay Time parameter.

  • 3 After an abend, the system immediately restarts the computer.

Default: 1

For values 1, 2, or 3 to take effect, the Developer Option parameter described in Miscellaneous Parameters must be set to Off.

If the server is to be shut down, the system sends a message every two minutes to warn all connections.

To configure the amount of time the system waits before shutting down the server, use the Auto Restart After Abend Delay Time parameter.

After an abend, the screen displays information about the abend. This information is sent to the abend.log file on the c: drive. After the server is shut down and restarted, the abend.log file is transferred to sys:system.

Important: Because the server can abend and be restarted automatically, you should determine whether any abends have occurred. Periodically check either the abend.log file or the Server Up Time field on MONITOR's General Information screen.

Owning NLM: server.nlm

Licensing Services Parameters

Licensing service parameters control Novell Licensing Service diagnosis features.

For a description of licensing parameters, see Table 1-8.

Table 1-8 Licensing Service Parameters

Parameter

Use to

NLS Search Type

Specify the scope of a license certificate search.

Supported values:

0 Search to the root of the tree

1 Search to the root of the partition

Default: 0

You must set this parameter in either the startup.ncf or autoexec.ncf file for the changes to be persistent.

Owning NLM: nlslsp.nlm

Store NetWare 5 Conn SCL MLA usage in NDS

Supported Values: On, OffDefault: On

Owning NLM: nlslsp.nlm

Memory Parameters

Memory parameters control garbage collection, corruption checking, the amount of memory below 16 MB available to device drivers, and aspects of protected and virtual memory.

For a description of memory parameters, see the following table.

Table 1-9 Memory Parameters

Parameter

Use to

Restart Server on Address Space Cleanup Failure value

Specify which actions to take during a server cleanup.

Supported Values: On, OffDefault: Off

When this parameter is On and the server is unable to completely clean up an address space after a memory protection error, then the server reacts according to the Auto Restart settings. (See the Auto Restart parameters in Error Handling Parameters.)

When this set parameter is Off, address spaces with cleanup failures will be isolated.

Owning NLM: server.nlm

Memory Protection Abend After Restart Count value

This parameter works in conjunction with the Memory Protection No Restart Interval and Memory Protection Restart Count parameters.

Supported Values: On, offDefault: Off

If this parameter is On, then the server abends if an address space has restarted more than the number of times specified in the Memory Protection Restart Count parameter in the time interval specified by the Memory Protection No Restart Interval parameter.

Owning NLM: server.nlm

Memory Protection Restart Count number

Specify the number of restarts allowed during the Memory Protection No Restart Interval.

Supported Values: 0 to 1000Default: 1

This parameter works in conjunction with the Memory Protection No Restart Interval parameter.

The default value is 1, meaning that if more than one protection fault occurs in an address space, then the address space will be restarted only once.

If you want to configure NetWare to allow two restarts during a three-minute period, then you should set the Memory Protection Restart Count to 2 and the Memory Protection No Restart Interval to 3.

Owning NLM: server.nlm

Memory Protection No Restart Interval value

Prevent a server from restarting a protected address space that continues to fault.

Supported Values: 0 to 60 minutesDefault: 1

If the address space faults but has already been restarted within the time period specified by this parameter, the server will not restart the address space. Restart functionality is disabled for the address space.

A restartable address space that continues to fault consumes server resources because the server is forced to continually shut down and restart the space.

Setting the value to 0 disables the parameter so that the address space will always be restarted if it faults.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Memory Protection Fault Cleanup value

Enable the server to clean up a protected address space that has faulted.

Supported Values: On, OffDefault: On

If this parameter is on and a protected address space faults, the server removes the address space and its NLM programs and returns the resources to the system.

If this parameter is off and a protected address space faults, the server does not remove the address space or return resources to the system. The situation is left to the abend recovery mechanism.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Average Page In Alert Threshold value

Specify the point at which the server sends an alert to the console because excessive memory swapping indicates the server might be low on memory.

Supported values: 0 to 4294967295Default: 2000

The value of the parameter is the average number of pages swapped from disk to memory per second, calculated over the last five seconds.

If the average page-in rate is high, it means a large amount of data is being swapped to and from disk, indicating that the server might be running low on memory.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Garbage Collection Interval number

Specify the maximum time between garbage collections.

Supported values: 1 minute to 1 hourDefault: 5 minutes

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Alloc Memory Check Flag value

Specify whether the server will check for corruption in the alloc memory nodes.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Reserved Buffers Below 16 Meg number

Specify the number of file cache buffers reserved for device drivers that can't access memory above 16 MB.

Supported values: 8 to 2000Default: 300

You must set this parameter in the startup.ncf file. You cannot set the value at the command line. Callback may be called at startup time.

Owning NLM: server.nlm

Miscellaneous Parameters

Miscellaneous parameters do not fit aptly or neatly into other categories. The functionality is listed below and described in Table 1-10.

Table 1-10 Miscellaneous Parameters

Parameter

Use to

Display Incomplete IPX Packet Alerts value

Specify whether alert messages are displayed when IPX receives incomplete packets. This parameter can be used as a debugging tool.

Supported values: On, OffDefault: On

You can set this parameter in the startup.ncf file.

Owning NLM: ipxspx.nlm

Enable SECURE.NCF=value

Execute the secure.ncf file at server startup.

Supported values: On, OffDefault: Off

You can set this parameter in the autoexec.ncf or startup.ncf file.

Owning NLM: filesys.nlm

Allow Audit Passwords value

Specify whether passwords can be used to identify auditors.

Supported values: On, OffDefault: Off

Owning NLM: filesys.nlm

Command Line Prompt Default Choice value

Specify a default response to an optional command in an .ncf file.

An optional command in an .ncf file is preceded by a question mark (?). The question mark causes the file to prompt you to execute the command. For information about optional commands in .ncf files, see Using Server Batch Files in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Supported Values: On, OffDefault: On

On means the default response to the command prompt is Y (Yes). If the user does not respond to the prompt within a specified time period, the command is executed by default.

Off means the default response to the command prompt is N (No). If the user does not respond to the prompt within a specified time period, the command is not executed.

To specify the time period before the response is executed, use the Command Line Prompt Timeout parameter.

Owning NLM: server.nlm

Command Line Prompt Time Out time

Specify how long (in seconds) an .ncf file waits before executing the default response to an optional command.

An optional command in an. ncf file is preceded by a question mark (?). The question mark causes the file to prompt you to execute the command. For information about optional commands in .ncf files, see Using Server Batch Files in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Supported Values: 0 to 4294967295Default: 10

Owning NLM: server.nlm

Sound Bell for Alerts value

Control whether a bell sounds when an alert message appears on the console.

Supported values: On, OffDefault: On

Owning NLM: server.nlm

Replace Console Prompt with Server Name value

Control whether the console prompt is replaced with the NetWare server name.

Supported values: On, OffDefault: On

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Alert Message Nodes number

Specify the number of alert message nodes that have been previously allocated.

Supported values: 10 to 256Default: 20

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Classic Work to do Pre-check Flag

When a classic work to do is scheduled, this flag causes the scheduler to verify if the work to do is scheduled. If it's on the scheduled list, the operating system will trap.

Supported values: On, OffDefault: Off

Owning NLM: server.nlm

Worker Thread Execute In a Row Count number

Specify the number of times the scheduler consecutively dispatches new work before allowing other threads to run.

Supported values: 1 to 20Default: 10

Worker threads are created by the kernel to perform work for the kernel itself.

Owning NLM: server.nlm

Halt System on Invalid Parameters value

Specify whether to stop the system when invalid parameters are detected.

Supported values:

On You want the system to stop when an invalid parameter or condition is detected

Off You want the system to display an alert and continue running when an invalid parameter or condition is detected

Default: Off

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display Relinquish Control Alerts value

Control whether messages about processor control are sent to the server console. This parameter can be used as a debugging tool.

Supported values:

On Use if you're writing your own loadable modules Off Use if you're not writing your own loadable modules

Default: Off

If a module uses the processor for more than 0.4 seconds without relinquishing control to other processes, the following types of messages appear:

process_name: Process did not relinquish control frequently Module: module_name Code offset in module: memory_address

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display Old API Names value

Control messages about outdated API functions from earlier versions of NetWare. This parameter can be used as a debugging tool.

Supported values: On, Off

On Use if you write your own modules and you are upgrading your NetWare modules to use newer APIs

Off Use if you aren't upgrading modules

Default: Off

The following types of messages appear when a module is loaded that uses the obsolescent APIs:

Module is using old API: SetInterruptVector Module is using old API: ReturnPermanentMemory Module is using old API: AllocateReturnablePermMemory

If you receive messages such as these, contact the vender of the module.

You can set this parameter in the startup.ncf file.

Note: Outdated API functions are those that have been replaced with newer, more efficient functions. These functions still work—they are not obsolete—but they work more slowly. Outdated API functions are not limited to NetWare 3 versions.

Also, not all older API functions have been replaced—many of them are still in use.

Owning NLM: server.nlm

CPU Hog Timeout Amount number

Specify the amount of time (in seconds) to wait before terminating a thread that has not relinquished control of the processor.

Supported values: 0 to 3600 (1 hour)Default: 60

A value of 0 (zero) disables this option.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Developer Option value

Control whether options associated with a developer environment are enabled.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display EOI Threshold number

Specify the number of spurious interrupts that are allowed to happen before inserting a delay before the End of Interrupt (EOI).

The delay before the EOI is added only if the threshold is reached and the Delay EOI SET parameter value On.

You can set this parameter in the startup.ncf file.

Supported values: 1 to 1000000Default: 200

Owning NLM: server.nlm

Display EOI value

Control whether a delay is inserted before the End of Interrupt (EOI). Specify the number of spurious interrupts that are allowed to happen before inserting a delay before the EOI.

Setting this parameter to On allows a delay to be inserted prior to the EOI. The delay is inserted only if the number of spurious interrupts reaches the value set by the Delay EOI Threshold SET parameter.

You can set this parameter in the startup.ncf file.

Supported values: On, OffDefault: On

Owning NLM: server.nlm

Display Spurious Interrupts Threshold number

Set the minimum number of spurious interrupts per second that must be detected before a spurious interrupt alert message is displayed on the system console.

Supported values: 1 to 1000000Default: 200

NOTE:The Set Display Lost Interrupt Alerts parameter must also be set to On.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display Lost Interrupts Threshold number

Set the minimum number of lost interrupts per second that must be detected before a lost interrupt alert message is displayed on the system console.

Supported values: 1 to 1000000Default: 10

Note: The Set Display Lost Interrupt Alerts must also be set to On.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display Spurious Interrupt Alerts number

Control alert messages displays when a spurious hardware interrupt is detected.

Supported values: On, OffDefault: Off

A spurious interrupt occurs when hardware in the server creates an interrupt that is defined and reserved for another device.

Spurious interrupts generate the following message: Spurious hardware interrupt number detected.

This message indicates a serious error in the hardware.

If your server console displays this message, remove all add-on boards and run SERVER.

If the message doesn't appear, add the boards one at a time to determine which hardware is creating the spurious interrupt. Then contact the vendor.

Set the parameter to Off while you are waiting for a resolution.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Display Lost Interrupt Alerts value

Control alert messages about lost interrupts.

Supported values: On, OffDefault: Off

A lost interrupt occurs when a driver or board requests a service with an interrupt call and then drops the request before the processor can respond.

Lost interrupts generate the following message: Interrupt controller detected a lost hardware interrupt.

This message indicates a hardware or driver problem that could degrade performance.

Unload all drivers and then reload them one at a time to determine which driver has a problem. Then contact the vender of the driver.

Set the parameter to Off while you are waiting for a resolution.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Pseudo Preemption Count number

Specify the number of times threads are allowed to make file read or write system calls before a relinquish is forced.

Supported values: 1 to 4294967295Default: 40

If you increase the value too much, the thread could run for its lifetime.

If you decrease the value too much, every read or write call that normally would not block might, in fact, end up blocking.

Owning NLM: server.nlm

Global Pseudo Preemption value

Specify whether or not all threads on the server that use the Traditional File System will also use pseudo pre-emption.

Supported values: On, OffDefault: On

Set this parameter to On if you rely on pseudo pre-emption to enforce blocking for threads.

Owning NLM: server.nlm

Minimum Service Processes number

Specify the number of service processes that the server will retain as it frees unneeded service processes. Service process are freed after 5 minutes of inactivity.

Supported values: 10 to 3000Default: 300

Owning NLM: server.nlm

Maximum Service Processes number

Specify the maximum number of service processes that the operating system can create.

You can view the number of service processes in Novell Remote Manager or MONITOR.

Supported values: 50 to 5000Default: 750

Decrease this parameter value temporarily if the server is low on memory. If the server is always low on memory, add more RAM for memory.

Increase this parameter value if the number of service processes is at the maximum.

Increasing this number helps only if more than 20 requests are being delayed simultaneously for a disk I/O to be completed.

Owning NLM: server.nlm

Allow Unencrypted Passwords value

Control the use of unencrypted passwords. This parameter provides for backward compatibility with network services that do not support encrypted passwords in the NetWare authentication protocol.

Supported values: On, OffDefault: Off

We strongly recommend that you retain the default Off setting.

NetWare 3.1x and later versions support encrypted passwords. If servers on your network run earlier versions of NetWare, set the value of this parameter to On.

Warning: Because the use of unencrypted (plaintext) passwords represents a significant security risk, you should update your servers, utilities, print servers, and NetWare clients to versions that support encrypted passwords. If you cannot update or upgrade to a newer version and are willing to assume the security risk, use the On setting.

Owning NLM: server.nlm

Multiprocessor Parameters

Multiprocessor parameters allow you to

Multiprocessor parameters are described in the following table.

Table 1-11 Multiprocessor Parameters

Parameter

Use to

System Threshold number

Adjust the load balancing threshold for multiprocessor servers.

This number controls the main value used in calculating thread shedding for load balancing across multiple processors. The optimum value has been preset by Novell.

Supported values: 0 to 102400Default: 1536

Important: The default value is the optimum value. We recommend that you retain it. If after careful consideration you decide to change the setting, experiment only in a nonproduction environment.

You can set this parameter in the startup.ncf file.

Owning NLM: server.nlm

Auto Clear Interrupt Statistics value

Specify whether interrupt statistics are removed from memory at the time a processor is taken offline or an interrupt handler (ISR) is removed.

Supported values: On, OffDefault: On

To retain per-processor interrupt handler statistics for offline processors or to retain the total interrupt contribution from a previously loaded handler (ISR), set the parameter to Off.

This parameter is preferably set in the startup.ncf file.

Owning NLM: server.nlm

Auto Start Processors value

Start secondary processors on startup.

Supported values: On, OffDefault: On

On Secondary processors are automatically started when the Platform Support Module (PSM) is loaded.

Off Secondary processors are not automatically loaded on bootup. When this is the case, the command START PROCESSORS must be used at the console prompt to activate secondary processors.

This parameter is preferably set in the startup.ncf file.

Owning NLM: server.nlm

NCP Parameters

With NetWare Core Protocol™ (NCP™) parameters, you can

For a description of NCP parameters, see the following table.

Table 1-12 NCP Parameters

Parameter

Use to

NCP Exclude IP Addresses values

Specify IP addresses over which NCP is disabled. All other IP addresses on this server will accept NCP traffic.

Supported values: None, AllDefault: None

  • None Indicates that no bound IP addresses on this server will disable NCP

  • All Disables NCP on all bound IP addresses on this server

Addresses listed in this setting have priority over the values set in the "Set NCP Include IP Addresses" command.

You can set this parameter in the startupfile.

Owning NLM: ncpip.nlm

NCP Include IP Addresses values

Specify IP addresses over which NCP is enabled. All other IP addresses on this server will ignore NCP traffic.

Supported values: None, AllDefault: All

  • None Disables NCP on all IP addresses

  • All Enables NCP over all bound IP addresses on this server

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

NCP over UDP values

Enable or disable NCP over UDP.

Supported values: On, OffDefault: On (Enable)

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

NCP TCP keep alive interval number

Set the delay before TCP keep alive closes idle NCP connections.

Supported values: 0 seconds to 15 hours 59 minutes 53.6 secondsDefault: 9 minutes 53.2 seconds

0 Never time out idle connections

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

Minimum NCP TCP receive window to advertise number

Set the minimum receive window to advertise on NCP connections.

Supported values: 256 to 16384Default: 4096

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

NCP TCP receive window number

Set the advertised receive window on NCP connections.

Supported values: 1400 to 65535Default: 23360

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

Enable UDP Checksums on NCP Packets number

Enable checksumming of NCP UDP packets

Supported values: 0, 1, 2Default: 1

0 No checksums 1 Checksum if enabled at client 2 Require checksums

You can set this parameter in the startup.ncf file.

Owning NLM: ncpip.nlm

Enable IPX Checksums number

Enable checksumming of IPX™ packets.

Supported values: Default: 1

0 No checksums 1 Checksum if enabled at the client 2 Require checksums

You can set this parameter in the startup.ncf file.

Owning NLM: ncpipx.nlm

Enable Task Zero Checkings number

Enable zero task checking. Enable packet checking for valid use of task zero.

Supported values: On, OffDefault: Off

Owning NLM: ncpipx.nlm

NCP Packet Signature Option number

Control the NCP packet signature level on the server.

Supported values:

0 Server doesn't sign packets (regardless of the client level)

1 Server signs packets only if the client requests it (client level is 2 or higher)

2 Server signs packets if the client is capable of signing (client level is 1 or higher)

3 Server signs packets and requires all clients to sign packets (or logging in will fail)

Default: 1

NCP Packet Signature prevents packet forgery on servers and clients using NCP by requiring server and client to sign each NCP packet.

Note: Because Packet Signature consumes processor resources and slows performance on both client and server, NCP Packet Signature is optional.

After starting the server, you can only increase the level of packet signature. To decrease the level, you must add the SET command to the startup.ncf file and restart the server.

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Level 2 OpLocks Enabled value

Allow or disallow level 2 (shared) oplocks.

Supported values: On, OffDefault: On (Allow)

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Client File Caching Enabled value

Allow or disallow the client-side caching of opened files.

Supported values: On, OffDefault: On (Allow)

This parameter is also settable in the startup.ncf file.

Owning NLM: ncp.nlm

NCP Protocol Preferences value

When multiple protocols are supported, specify the order in which eDirectory™ selects a protocol to use when communicating with other servers in the replica.

Supported values: IPX, TCP, UDP, noneDefault: None

For example, the following command instructs eDirectory to try TCP first and IPX second when it communicates with another server:

SET NCP PROTOCOL PREFERENCES TCP IPX

If only one protocol is supported, that protocol is used by eDirectory, no matter what values are specified for this parameter.

If multiple protocols are supported but no value is specified for this parameter, eDirectory uses the protocols in the order in which they are loaded.

Owning NLM: ncp.nlm

NCP File Commit value

Control whether applications can flush pending file writes to disk.

Supported values: On, OffDefault: On

If the value is set to On, then when a File Commit NCP is issued, a file is sent from cache to disk immediately instead of waiting for the cache manager to send it to disk later.

Owning NLM: ncp.nlm

Display NCP Bad Component Warnings value

Control whether NCP bad component alert messages are displayed.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Reject NCP Packets with Bad Components value

Specify whether NCP packets that fail component checking are rejected.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Display NCP Bad Length Warnings value

Control whether or not to display NCP bad length alert messages.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Reject NCP Packets with Bad Lengths value

Specify whether to reject NCP packets that fail boundary checking. This parameter can be used as a debugging tool.

Supported values: On, OffDefault: Off

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Maximum Outstanding NCP Searches number

Specify the maximum number of NCP directory searches that can be processed simultaneously.

Supported values: 10 to 1000Default: 51

Normally, only one NCP directory search occurs at a time.

Increase the default only if you use applications that support multiple outstanding directory search operations and you have problems with corrupted or invalid directory information.

Owning NLM: ncp.nlm

Allow Change to Client Rights value

Control whether a job server can assume the rights of a client for NCP packet signatures.

Supported values: On, OffDefault: On

Note: Some job servers and third-party applications can't function without changing to client rights.

Using Off might prevent some job servers from getting access to the files they need, but it prevents the forging of a packet through the job or print server.

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Allow LIP value

Set Large Internet Packet (LIP) support.

Supported values: On, OffDefault: On

You can set this parameter in the startup.ncf file.

Owning NLM: ncp.nlm

Novell Storage Services Parameters

The following are the default settings in NetWare 6.5 for the NSS file system SET parameters.

Common File System SET Parameters for NSS and Traditional File Systems

Default Value

NSS Auto Locks HFS CD-ROM Disc in device

Off

NSS Auto Update CDHFS Volume Objects To NDS

Off

Mount ISO 9660 multi disc set as one CD9660 volume

Off

NSS Auto Locks CD-ROM Disc in device

Off

NSS Auto Update CD9660 Volume Objects To NDS

Off

Emulate Classic NetWare Directory Quotas

Off

NSS Work To Do Count

(This parameter can be set only in the nssstart.cfg file.)

50

NSS Maximum Cache Balance Buffers Per Session

1024

NSS Cache Balance Timer

30

NSS Cache Balance Percent

60

NSS Cache Balance Enable

On

NSS Buffer Flush Timer

1

NSS Minimum OS Cache Buffers

256

NSS Minimum Cache Buffers

256

NSS File Flush Timer

10

NSS Closed File Cache Size

(This parameter can be set only in the nssstart.cfg file.)

50000

NSS Open File Hash Shift

16

NSS Auth Cache Size

(This parameter can be set only in the nssstart.cfg file.)

1024

NSS ASCII Name Cache Enable

(This parameter can be set only in the nssstart.cfg file.)

On

NSS Name Cache Enable

(This parameter can be set only in the nssstart.cfg file.)

On

NSS Name Cache Size

2111

NSS Low Volume Space Alerts

On

NSS Low Volume Space Warning Reset Threshold

15

NSS Low Volume Space Warning Threshold

10

Power Management Parameters

Power Management parameters let you control the behavior of the Power button and the Down and Reset options on a server running the ACPI power management driver.

Table 1-13 Power Management Parameters

Parameter

Use to

Power Button Mode number

Control the behavior of the Power button on a server running the ACPI power management driver.

Supported values: 0, 1Default: 1

  • 0 Disables the Power button

  • 1 Enables the Power button for shutdown

    This setting uses the Power Down Delay setting before shutting down and powering off the server.

You can set this parameter at any time. The changes will be saved (persistent).

You can set this parameter in the startup.ncf file.

WARNING:Without the ACPI power management driver loaded, pressing the Power button immediately removes power from the system.

Pressing and holding the Power button for four seconds removes system power regardless of this setting.

Owning NLM: acpipwr.nlm

Power Down Delay time

Control the fixed delay on a server running the ACPI power management driver before the server begins shutting down in response to pressing the Power button or entering SHUTDOWN at the System Console prompt.

If you need to cancel a pending shutdown, you must enter SHUTDOWN ABORT before the delay time expires.

Supported values: 0 seconds to 10 minutesDefault: 30 seconds

You can set this parameter at any time. The changes will be saved (persistent).

Owning NLM: acpipwr.nlm

Server Power Down Options value

Control the behavior of the DOWN and RESTART SERVER console commands on a server running the ACPI power management driver, .

Supported values: On, OffDefault: On

  • On Executing DOWN shuts down and powers off the server. Executing RESTART SERVER shuts down the server and performs a system reset.

  • Off Executing DOWN shuts down server and leaves the power on. Executing RESTART SERVER shuts down and then restarts the server.

You can set this parameter at any time. The changes will be saved (persistent).

Owning NLM: acpipwr.nlm

Service Location Protocol Parameters

The service location protocol parameters define how SLP locates and distributes information about services that are available on the network.

For descriptions of service location protocol parameters, see the following table.

Table 1-14 Service Location Protocol Parameters

Parameter

Use to

SLP Exclude IP Addresses value

Specify IP addresses over which SLP is disabled. All other IP addresses on this server will accept SLP traffic.

Supported values: None, AllDefault: None

  • None Indicates that no bound IP addresses on the server will disable SLP.

  • All Disables SLP on all bound IP addresses on the server. Addresses listed here have priority over the Set SLP Include IP Addresses command.

This parameter can be set in the startup.ncf file.

Owning NLM: slptcp.nlm

SLP Include IP Addresses value

Specify IP addresses over which SLP is enabled. All other IP addresses on this server will ignore SLP traffic.

Supported values: None, AllDefault: None

  • None Indicates that SLP is disabled on all IP addresses.

  • All Enables SLP over all bound IP addresses on this server.

This parameter can be set in the startup.ncf file.

Owning NLM: slptcp.nlm

SLP Agent IP Address value

Specify the IP address of the SLP SA/DA on the server.

Supported values: First, FollowDefault: First

  • First Use the first bound NON-Excluded IP address.

  • Follow Use the IP address of the received SA/DA service request.

This parameter can be set in the startup.ncf file.

Owning NLM: slptcp.nlm

SLP API Handicap value

Set the maximum number of UA requests before SLP starts slowing them down.

Supported values: 1 to 100000Default: 50

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Maximum Memory Percent number

Set the maximum memory percentage that sends can allocate before rejecting future allocations and purging UA cache.

Supported values: 5 to 70Default: 15

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Cache Timeout number

Specify how long (in seconds) the UA cache will retain information. Zero disables cache.

Supported values: 0 to 4294967295Default: 120

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Enable UA Multicast values

Enable or disable the use of User Agent General Multicast packets. Disabling requires full dependancy on the directory agent.

Supported values: On, OffDefault: On

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Register nwserver values

Enable or disable the nwserver.novell service registration.

Supported values: On, OffDefault: On

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP nwserver NLM names values

Enable or disable the nwserver.novell service to include NLM names as an attribute.

Supported values: On, OffDefault: Off

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Maximum WTD number

Specify the maximum number of controlled work-to-do threads.

Supported Values: 1 to 256Default: 32

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Maximum WTD Queue number

Specify the maximum number of work-to-do threads allowed to be queued before dropping packets.

Supported Values: 0 to 1048575Default: 15000

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Reset values

Force SA to send new service registers. Force DA to send DA Advertise. Flag will be reset to off.

Supported values: On, OffDefault: Off

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Scope List number

Specify scope list using a comma-delimited string.

Max Length: 185Default: ...

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Static Scope List number

Use SLP Scope List as the only source of scopes. The SA/UA will only use scopes listed in the SLP Scope List. Otherwise, the SA will use scopes listed in the SLP scope list and filtered scopes from slp.cfg and the UA will use scopes listed in the SLP scope list, filtered scopes from slp.cfg, and scopes discovered from DAs.

This parameter has no effect when SLP Scope List is not set or is set to the default.

Supported values: On, OffDefault: On

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Close Idle TCP Connections Time value

Specify the amount of time (in seconds) to wait before idle TCP connections should be terminated.

Supported values: 0 to 86400Default: 300

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP DA Heart Beat Time value

Specify the amount of time (in seconds) to wait before sending the next Directory Agent heartbeat packet.

Supported values: 0 to 65535Default: 10800

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP DA Event Timeout number

Specify the amount of time (in seconds) to wait before timing out Directory Agent packet requests.

Supported values: 0 to 128Default: 15

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP MCA Timeout number

Specify the amount of time (in seconds) to wait before timing out multicast packet requests.

Supported values: 0 to 128Default: 16

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP SA Default Lifetime number

Specify the default lifetime (in seconds) on service registers.

Supported values: 129 to 65535Default: 3600

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Retry Count number

Specify the maximum number of retries.

Supported values: 0 to 128Default: 3

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Debug number

Enable SLP debug mode.

  • Bit 0x01 COMM

  • Bit 0x02 TRAN

  • Bit 0x04 API

  • Bit 0x08 SA_DA

  • Bit 0x10 ERR

  • Bit 0x20 SA

  • Bit 0x40 UA_DA

Supported values: 0 to 4294967295Default: 0

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Rediscover Inactive Directory Agents number

Specify the minimum time period (in seconds) that SLP will wait to issue service requests to rediscover inactive Directory Agents.

Supported values: 0 to 86400Default: 60

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Multicast Radius number

Specify the multicast radius. SLP v2 is administratively scoped in accordance with RFC 2365.

Supported values: 0 to 255Default: 255

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP DA Discovery Options number

Use multicast DA advertisements.

  • 1 (0001b) Dynamic discovery via multicast

  • 2 (0010b) Use DHCP discovery

  • 4 (0100b) Use static file sys:etc\\slp.cfg

  • 8 (1000b) Always disable dynamic discovery when DHCP or static file bits are set.

Bits can be added together for multiple values and are specified as decimal numbers.

Example: To enable DHCP discovery and static file discovery, you would add 2 and 4 then specify the decimal value 6 (2 + 4 6).

These bits can be ordered together for multiple values.

Supported values: 0 to 15Default: 15

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP MTU Size value

Specify the maximum transfer unit size.

Supported values: 0 to 24682Default: 1450

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP Broadcast value

Use broadcast packets instead of multicast packets.

Supported values: On, OffDefault: Off

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

SLP TCP value

Use TCP packets instead of UDP packets when possible.

Supported values: On, OffDefault: Off

This parameter can be set in the startup.ncf file.

Owning NLM: slp.nlm

Time Parameters

Time parameters control time synchronization, the timesync.cfg file, and time zone settings to ensure that the time reported by all servers is consistent, or synchronized. For more information, see the NW 6.5 SP8: Network Time Synchronization Administration Guide.

For a description of time parameters, see the following table.

Table 1-15 Time Parameters

Parameter

Use to

start of daylight savings time date_and_time

Specify a local date and time when the switch to daylight savings time should occur. Formats include a simple date and time or rules introduced by a open paren "( ".

For example: April 4 1993 2:0:0 am, (April 4 2:0:0 am), (April Sunday < 1 2:0:0 am), or (April Sunday First 2:0:0 am).

Only rules can reschedule for the next year. You must set both the start and end dates before either will be scheduled.

The settings will not be saved in the NetWare Registry.

Owning NLM: server.nlm

end of daylight savings time date_and_time

Specify a local date and time when the switch off of daylight savings time should occur. Formats include a simple date and time or rules introduced by an open paren "( ".

For example: October 31 1993 2:0:0 am, (October 31 2:0:0 am), (October Sunday < 31 2:0:0 am), or (October Sunday last 2:0:0 am).

Only rules can reschedule for the next year. You must set both the start and end dates before either will be scheduled.

The settings will not be saved in the NetWare Registry.

Owning NLM: server.nlm

daylight savings time offset [+|-] hour:minute:second

Specify the offset applied in time calculations when daylight savings time is in effect.

Issuing this command causes UTC time to be recalculated from local time.

The offset applied in time calculations when daylight savings time is in effect. The default is +1:00:00 (one hour). Issuing this command causes UTC time to be recalculated from local time. +0:00:00 to +0:00:00

Supported values: +0:00:00 to +0:00:00Default: +1:00:00 (one hour)

The settings will not be saved in the NetWare Registry.

Owning NLM: server.nlm

timesync configured sources on|off

Specify whether the server listens to the advertising time sources.

When On, this server does not listen to advertising time sources. Instead, it contacts only sources explicitly configured with the Time Sources parameter.

Supported values: On, OffDefault: Off

Owning NLM: timesync.nlm

timesync debug flag number

Specify whether Timesync opens or logs a debug screen to view or log debug information.

To enable the debug screen and log it to timesync.log (located in sys:\system), use

set timesync debug=15

To enable the debug screen only and disable the log, use

set timesync debug=7

To disable both the debug screen and logging, use

set timesync debug=0

For more information, see Section 1.56, FLAG.

Supported values: 0, 7, 15 Default: 0

Owning NLM: timesync.nlm

timesync polling count number

Specify the number of time packets to exchange while polling with the time provider.

Supported values: 1 to 1000Default: 3

Owning NLM: timesync.nlm

timesync polling interval number

Specifiy the time interval (in seconds) before the next polling begins.

Supported values: 10 to 2678400Default: 600

Owning NLM: timesync.nlm

timesync reset value

Specify whether Timesync resets the previous internal values and reads the new values on the configured server list.

Supported values: On, Off Default: Off

Owning NLM: timesync.nlm

timesync restart flag

Specify whether Timesync restarts.

When set to On, Timesync restarts.

Supported values: On, OffDefault: Off

Owning NLM: timesync.nlm

timesync service advertising on|off

Specify time source advertising.

When On, this time source advertises itself using SAP/SLP. Secondary time servers never advertise.

Supported values: On, OffDefault: Off

Owning NLM: timesync.nlm

timesync synchronization radius value_in_seconds

Specify the maximum tolerance (in seconds).

If the offset is less than this value (in milliseconds), Timesync remains in synchronization.

Supported values: 0 to 2147483647Default: 2000

Owning NLM: timesync.nlm

timesync time adjustment [+|-]hour:minute:second[at month/day/year hour:minute:second [AM or PM]]

Schedule a time adjustment. Can be issued only from a Single, Reference, or Primary type server.

Single and Reference time servers do not accept adjustments from Primary time servers.

Supported values: A date in the format of [+|-]hh:mm:ss [AT [date and time]] or CancelDefault: Six polling intervals or one hour (whichever is longer) from now.

Using the word cancel instead of a date cancels a previously scheduled adjustment.

Owning NLM: timesync.nlm

timesync time source IP_address

Specify that this server contacts the servers in this list as time providers.

Each time server (IP address, DNS name) in this list is separated by a semicolon ( ; ).

For example:

MyServer:123;

where the semicolon ( ; ) clears the MyServer list and specifies that MyServer is the NetWare (NTP) time source.

Supported values: A server list (IP address or DNS name, each separated by a semicolon) or an empty listDefault: Empty list

Owning NLM: timesync.nlm

timesync type value

Specify the Timesync server type.

Supported values: Single, Reference, Primary, SecondaryDefault: Single

Owning NLM: timesync.nlm

standard time offset time zone IST [Time_offset_from_IST]

Offset (in hours) from Universal Time Coordinated (UTC).

The time zone string indicates the abbreviated name of the time zone, the offset from UTC, and the alternate abbreviated time zone name to be used when daylight savings time is in effect.

Issuing this command causes UTC time to be recalculated from local time.

Supported values: On, OffDefault: Off

Owning NLM: timesync.nlm

timesync max log file size number

Specify the largest size (in KB) of the sys:\system\timesync.log file.

Supported values: 500 to 1,073,741,824Default: 1048576

Owning NLM: timesync.nlm

timesync NTP Client port number

Specify the port that the NTP Client uses to make an NTP Time Request.

Supported values: 0 (Dynamic Port) and values greater than 1024 up to 32768Default: 0

Owning NLM: timesync.nlm

Time Zone value

Specify a time zone string that indicates the abbreviated name of the time zone.

Supported values: The offset from Universal Time Coordinated (UTC), and the alternate abbreviated time zone name to be used when daylight savings time is in effect. Default:<>

Issuing this command causes UTC time to be recalculated from local time.

Owning NLM: server.nlm

default time server type primary|single|secondary|reference

Specify the default time synchronization server type.

This parameter can be overridden by separate time synchronization parameters.

Supported values: Secondary, Primary, Reference, Single Can be overridden by separate time synchronization parameters.

Default: Secondary

Owning NLM: server.nlm

Traditional File Parameters

Traditional file parameters now contain parameters that were previously designated as Directory Caching, File Caching, Error Handling, File System, Locks, and Transaction Tracking

File Caching Parameters for the Traditional File System

File caching allows faster access to frequently used files by holding a file (or a portion of it) in disk cache memory. Files being read from or written to are kept in file cache buffers. When the requested data is already in cache, disk reads are unnecessary.

The number of files kept in memory depends on the number of file cache buffers allowed. This is determined by the amount of disk cache memory available and the value of the Minimum File Cache Buffers parameter.

Disk cache memory not only speeds up access to file data, it is also used to cache portions of the eDirectory database. If you want to tune your NetWare server in general, or eDirectory in particular, tune the file caching parameters. The key to optimizing cache utilization is to monitor both Long Term Cache Hits and LRU Sitting Time statistics. Both parameters are found in MONITOR's Available Options > Disk Cache Utilization. (File caching parameters can also be set in MONITOR's Available Options > Server Parameters.)

File caching and directory caching work together, however. In tuning the server, directory caching and file caching need to be balanced for maximum performance. See How Directory Caching and File Caching Work Together.

Remember also that the file and directory caching parameters in SET apply only to NetWare servers using the Traditional File System. In contrast, the NSS file system provides improved resource use, requiring less memory to mount multiple volumes.

For information about NSS directory caching parameters, see Overview of NSS in the NW 6.5 SP8: NSS File System Administration Guide.

For a description of file caching parameters, see the following table.

Table 1-16 File Caching Parameters for the Traditional File System

Parameter

Use to

Read Ahead Enabled value

Specify whether the system conducts background reads to cache in advance of blocks soon to be requested.

Supported values: On, OffDefault: On

Read-aheads can happen only when sequential file accesses are occurring.

Owning NLM: filesys.nlm

Read Ahead LRU Sitting Time Threshold number

Specify the minimum cache LRU (least recently used) sitting time for read-aheads to take place.

Supported values: 0 seconds to 1 hourDefault: 10 seconds

Owning NLM: filesys.nlm

Minimum File Cache Buffers number

Set the minimum number of cache buffers the operating system can allow for file caching.

Supported values: 20 to 2000Default: 20

All memory not allocated for other processes is given to disk cache memory to use for file and directory caching. As memory is requested for other processes, the server gives up cache buffers.

This limit specifies when the server must stop giving file cache buffers to other processes.

If you set the minimum too high, other processes might not be able to allocate necessary memory resources.

For example, a module could fail to load because the server is out of available memory.

Owning NLM: filesys.nlm

Maximum Concurrent Disk Cache Writes number

Specify the number of write requests for changed file data that can be put in the elevator before the disk head begins a sweep across the disk.

Supported values: 10 to 4000Default: 50

A high number creates more efficient write requests. A low number creates more efficient read requests.

Monitor the number of Dirty Cache Buffers displayed on the Cache Utilization Statistics screen in MONITOR or in Novell Remote Manager > View Memory Config > File System Cache.

If this number is above 70 percent of total cache buffers, optimize the write speed by increasing this parameter.

Owning NLM: filesys.nlm

Dirty Disk Cache Delay Time time

Specify how long (in seconds) the system keeps a write request (that does not fill a cache buffer) in memory before writing the request to disk.

Supported values: 0.1 second to 10Default: 3.3

Increasing the time makes disk writing more efficient if your users make many small write requests.

Decreasing the time can reduce performance drastically and reduces the chances of losing data only slightly.

Owning NLM: filesys.nlm

Minimum File Cache Report Threshold number

Specify how few cache buffers can be available before the operating system warns you that the number of buffers is getting low.

Supported values: 0 to 2000Default: 20

For example, if the value of the Minimum File Cache Buffers parameter is set to 20 and this parameter is set to 25, you are warned when all but 45 cache buffers are allocated for other processes.

Regardless of how this parameter value is set, the operating system will issue a warning when it reaches the minimum number of cache buffers. You receive the following message: Cache memory allocator exceeded minimum cache buffer left limit.

Owning NLM: filesys.nlm

Directory Caching Parameters for the Traditional File System

Directory caching allows fast access to frequently used directories. A directory cache buffer is a portion of NetWare server memory (disk cache memory) that holds entries from the directory table.

A directory entry stays in a cache buffer as long as it is accessed frequently (default=33 seconds). The system can overwrite the directory entry if the allocated directory cache buffers are accessed more frequently.

Directory caching and file caching work together, however. In tuning the server, directory caching and file caching need to be balanced for maximum performance.

Remember also that the directory and file caching parameters in SET apply only to NetWare servers using the Traditional File System. In contrast, the NSS file system provides improved resource use, requiring less memory to mount multiple volumes.

For information about NSS caching parameters, see Cache Balancing Commands (NetWare) and Overview of NSS in the NW 6.5 SP8: NSS File System Administration Guide.

For a description of directory caching parameters, see Table 1-17.

Allocation of Directory Cache Buffers

When the server boots, the system allocates a minimum number of directory cache buffers (default=20). It creates these buffers immediately when it receives a request for a new buffer.

The server obtains directory cache buffers by removing a minimal set of file cache buffers from the file cache during server startup. Additional directory cache buffers are obtained from the file cache later on if they are needed.

When the minimum number of buffers is allocated and another is needed, the system must wait a specified amount of time before allocating another buffer.

If necessary, the system allocates buffers until it reaches the maximum. If enough directory cache buffers are allocated and enough memory is available for directory caching, all directory tables can be cached in memory.

How Directory Caching and File Caching Work Together

As directory cache buffers increase, file cache buffers decrease. Thus, a tradeoff exists between directory caching and file caching, and directory caching and file caching must be balanced for maximum performance.

If you adjust the system to use too much memory for directory caching, you can leave too little memory for file caching, and vice versa.

For a description of file caching parameters, see Table 1-16. For a description of directory caching parameters, see the following table.

Table 1-17 Directory Caching Parameters for the Traditional File System

Parameter

Use to

Dirty Directory Cache Delay Time time

Specify how long (in seconds) the system keeps a directory table write request in memory before writing it to disk.

Supported values: 0 to 10Default: 0.5

Increasing the delay time gives slightly quicker performance but increases the probability of the directory tables becoming corrupted.

Decreasing the delay time slightly reduces the chance of directory tables becoming corrupted, but can reduce performance slightly.

A setting of 0 reduces performance dramatically.

Owning NLM: filesys.nlm

Directory Cache Allocation Wait Time number

Specify how long the system must wait after allocating a new directory cache buffer before it can allocate another buffer.

Supported values: 0.1 second to 2 minutesDefault: 2.2 seconds

During this time, all requests for a new directory cache buffer are ignored.

If the wait time is too low, peak usage requests cause more resources than necessary to be allocated to directory caching.

If the wait time is too high, the system is very slow in allocating the directory cache buffers necessary to service the usual number of directory requests.

If directory searches seem slow even after the server has been running for 15 minutes, you should decrease this parameter.

Owning NLM: filesys.nlm

Directory Cache Buffer NonReferenced Delay time

Specify how long a directory entry must be cached before it can be overwritten by another directory entry.

Supported values: 1 second to 1 hourDefault: 5.5 seconds

Increasing this parameter speeds up directory access. The system allocates more directory cache buffers, and a directory is more likely to be cached in memory.

Decreasing this parameter slows directory access but also reduces the need for directory cache buffers.

Owning NLM: filesys.nlm

Maximum Directory Cache Buffers number

Specify the maximum number of cache buffers that the system can allocate for directory caching.

Supported values: 20 to 200000Default: 2000

This parameter keeps the system from allocating too many directory cache buffers so that memory is available for other server processes.

Increase this limit if the server responds slowly to directory searches.

Decrease this limit if too much memory is being allocated for directory caching.

If users are warned that the server is low on memory, this parameter should be one of the first to be reduced. (Reboot the server to return the memory to the cache buffer memory pool.)

When a directory cache buffer is allocated, the allocation is permanent until the server reboots; the buffers don't return to file caching when the need for directory cache buffers decreases.

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Minimum Directory Cache Buffers number

Specify the minimum number of cache buffers that the system can allocate for directory caching.

Supported values: 10 to 100000Default: 500

The number needs to be high enough that directory searches can be done quickly, but no higher than necessary.

If the system doesn't need the minimum number of directory cache buffers, the buffers can't be reallocated to file caching. The unneeded portion remains unused.

If the server responds slowly to directory searches after it is booted, monitor the number of directory cache buffers usually allocated for directory caching.

If the number is significantly higher than this limit, consider increasing the limit to remove the delay time that normally occurs while the server is self-configuring. Use MONITOR to view the current statistics.

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Maximum Number of Internal Directory Handles number

Specify the maximum number of directory handles available for internal NLM programs that use connection 0.

Supported values: 40 to 1000Default: 100

A directory handle is a version of the directory access rights that is held in cache memory. Caching the access rights speeds mapping to the rights.

Connection 0 (zero) is the connection number reserved for use by the server itself and by NLM programs operating within the server.

Each time an NLM using connection 0 accesses a file or directory, a directory handle is allocated (up to the total specified by this parameter). This value represents the total number of handles available to be shared by all NLM programs using connection 0.

Owning NLM: filesys.nlm

Maximum Number of Directory Handles number

Specify the maximum number of directory handles available for each connection.

Supported values: 20 to 1000Default: 20

A directory handle is a version of the directory access rights that is held in cache memory. Caching the access rights speeds mapping to the rights.

Each time a connection accesses a file or directory, a directory handle is allocated (up to the total specified by this parameter).

Owning NLM: filesys.nlm

File Parameters for the Traditional File System

For a description of file system parameters, see the following table.

Table 1-18 File Parameters for the Traditional File System

Parameter

Use to

Automatically Repair Bad Volumes value

Specify whether VREPAIR runs automatically on a volume that fails to mount.

Supported values: On, OffDefault: On

You can set this parameter in the startup.ncf file.

Owning NLM: filesys.nlm

File Delete Wait Time time

Specify when a salvageable file can be purged to create free space on a volume.

Supported values: 0 seconds to 7 daysDefault: 5 minutes 29.6 seconds

Set this parameter as high as is useful for your users, but this parameter doesn't guarantee that a file remains salvageable.

The system tries to keep at least 1/32 of available space on the volume free for new files.

This parameter guarantees only that files aren't purged to maintain this free disk space.

Files that haven't met this time limit are purged if the volume is full and the system needs space for a user to create a new file.

When a deleted file remains on the server longer than the File Delete Wait Time parameter setting, the system marks the file as purgeable.

When the volume is full of purgeable files and needs free space, the oldest purgeable files are purged.

Owning NLM: filesys.nlm

Allow Deletion of Active Directories value

Specify whether a directory can be deleted when another connection has a drive mapped to it.

Supported values: On, OffDefault: On

Owning NLM: filesys.nlm

Maximum Percent of Volume Space Allowed for Extended Attributes percentage

Limit the portion of volume space used for extended attribute storage. The setting takes effect only when the volume is being mounted.

Supported values: 5 to 50Default: 10

Owning NLM: filesys.nlm

Maximum Extended Attributes per File or Path number

Limit the number of extended attributes that can be assigned to a file or path (subdirectory). This limit applies to all volumes on the server.

Supported values: 4 to 512Default: 16

Owning NLM: filesys.nlm

Purge Files On Dismount value

Have the system purge deleted files on a volume when it is dismounted.

Supported values: On, OffDefault: Off

Owning NLM: filesys.nlm

Fast Volume Mounts value

Increase the speed at which volumes are mounted.

Supported values: On, OffDefault: On

The operating system checks only the most important fields during the mounting process. Use this parameter only if volumes were dismounted normally.

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Maximum Percent of Volume Used by Directory percentage

Limit the portion of a volume that can be used as directory space.

Supported values: 5 to 85Default: 13

Owning NLM: filesys.nlm

Maximum Subdirectory Tree Depth number

Specify how many levels of subdirectories the system supports.

Supported values: 10 to 100Default: 25

This parameter can be set in the startup.ncf or in the autoexec.ncf file, or at the server console.

Increase the number if your applications support trees deeper than 25.

Decrease the number if your applications support only shallow tree structures.

(Some DOS applications can't support more than 10 levels if the subdirectories have 11-character names.)

Owning NLM: filesys.nlm

Volume Low Warn All Users value

Have the system notify users when a volume is almost full.

Supported values: On, OffDefault: On

If you choose not to have your server warn users, monitor volume statistics at least daily with MONITOR or Novell Remote Manager > Volumes > Volume Inventory Report.

Owning NLM: filesys.nlm

Volume Low Warning Reset Threshold number

Control how much disk space (in blocks) must be freed up before a second warning is issued that the volume is almost full. (The first warning is controlled by the Volume Low Warn All Users parameter.)

Supported values: 0 to 100000Default: 256

When a volume is almost full, it can hover at its warning threshold as users create and delete files.

This parameter controls the minimum amount of space that must be made available above the threshold before the warning message disappears.

Example: Assume the volume block size is 4 KB, the Volume Low Warning Reset Threshold is set to 256, the Volume Low Warning Threshold is set to 256, and the volume has less than 1 MB of free space.

Given these conditions, the volume must gain at least 1 MB of free space (for a total of 2 MB of free space) and then dip below the 1 MB threshold before the system sends another warning that the volume is almost full.

Owning NLM: filesys.nlm

Volume Low Warning Threshold number

Specify how much free disk space (in blocks) can remain on a volume before the system issues a warning.

Supported values: 0 to 1000000Default: 256

Consider the following: A block is the minimum space allocated to a file; a file can grow only in multiples of the block size.

The block's physical size is determined when the volume is created. A volume can be assigned these block sizes: 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB.

For example, if you specify 256 blocks for this parameter and the volume's block size is 4 KB, the system warns you that the volume is full when about 1 MB of space is left.

If your volumes are assigned different block sizes, each volume has a different amount of free space when the warning is issued.

Owning NLM: filesys.nlm

Turbo FAT Re-Use Wait Time time

Specify how long a turbo FAT buffer remains in memory after an indexed file is closed.

Supported values: 0 to 7 daysDefault: 5 minutes 29.6 seconds

Once the wait-time value has passed, the system can allocate the buffer to another indexed file.

Increase the wait time if

  • You want the turbo FAT index to remain in memory for long periods of time, even when the file is closed.

  • You frequently reopen the same file after a specific delay and know that another file opened during that delay will reuse the index.

Decrease the wait time if you want the memory released immediately to service the next file that needs to be indexed.

When a program randomly accesses a file that contains more than 64 FAT entries, the system builds a turbo FAT index for the file so that information is accessed quickly. (NetWare indexes any randomly accessed file with 64 FAT entries.)

The system doesn't immediately delete the index from its buffer when the file is closed.

Having the turbo FAT index in memory makes reopening the file and accessing information faster.

Owning NLM: filesys.nlm

Allow Unowned Files To Be Extended value

Specify whether files can be modified when the owner has been lost or deleted.

Supported values: On, OffDefault: On

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Auto Mount Mirrored Volume Containing Inactive Device value

Specify whether to automatically mount a volume detected to have a mirrored partition and an inactive device associated with it.

Supported values: On, OffDefault: On

This parameter can be set in the startup.ncf file.

Owning NLM: filesys.nlm

Locks Parameters for the Traditional File System

Locks parameters control

There are three types of locks:

For a description of locks parameters, see the following table.

Table 1-19 Locks Parameters for the Traditional File System

Parameter

Use to

Maximum Record Locks Per Connection number

Control how many record locks a client connection can use at one time. (Use MONITOR to view how many record locks each connection is using.)

Supported values: 10 to 100000Default: 500

Increase the value of this parameter when an application can't lock enough records and fails.

Decrease the value of this parameter if one or more client connections are using an excessive amount of server resources.

Owning NLM: filesys.nlm

Maximum File Locks Per Connection number

Control how many opened and locked files a client connection can use at one time. (Use MONITOR to view how many opened and locked files a connection is using.)

Supported values: 10 to 1000Default: 2500

Increase the value of this parameter when an application can't open enough files and fails.

Decrease the value of this parameter if client connections are using an excessive amount of server resources.

Owning NLM: filesys.nlm

Maximum Record Locks number

Control how many record locks the operating system can handle. (Use MONITOR to view how many record locks each client connection is using on that server.)

Supported values: 100 to 400000Default: 20000

Increase the value of this parameter if users have problems running applications and receive messages indicating that not enough record locks are available.

Decrease the value of this parameter if client connections are using an excessive amount of server resources.

Owning NLM: filesys.nlm

Maximum File Locks number

Control how many opened and locked files the operating system can handle. (Use MONITOR to view the number of files that are open during peak usage.)

Supported values: 100 to 2000000Default: 200000

Increase the value of this parameter if the number of open files is near or equal to the default.

Decrease the value of this parameter to restrict the amount of available server resources.

Owning NLM: filesys.nlm

Error Handling Parameters for the Traditional File System

Error handling parameters control the size of error logs and specify what happens when logs exceed the specified size. They also control how the server responds to an abend or to an NLM that does not unload from a protected address space.

For descriptions of error handling parameters, see the following table.

Table 1-20 Error Handling Parameters for the Traditional File System

Parameter

Use to

Volume Log File State number

Control what happens when the vol$log.err file is larger than the size specified by the Volume Log File Overflow Size parameter.

Supported values:

  • 0 Leave vol$log.err as is
  • 1 Delete vol$log.err
  • 2 Rename vol$log.err

Default: 1

You can set this parameter in the startup.ncf file.

Owning NLM: filesys.nlm

Volume TTS Log File State number

Control what happens when the tts$log.err file is larger than the size specified by the Volume TTS Log File Overflow Size parameter.

Supported values:

  • 0 Leave tts$log.err as is
  • 1 Delete tts$log.err
  • 2 Rename tts$log.err

Default: 1

You can set this parameter in the startup.ncf file.

Owning NLM: filesys.nlm

Volume Log File Overflow Size number

Specify the maximum size of the vol$log.err file before the action specified by the Volume Log File State parameter occurs.

Supported values: 65536 to 4294967295Default: 4194304

You can set this parameter in the startup.ncf file.

Owning NLM: filesys.nlm

Volume TTS Log File Overflow Size number

Specify the maximum size of the tts$log.err file before the action specified by the Volume TTS Log File State parameter occurs.

Supported values: 65536 to 4294967295Default: 4194304

You can set this parameter in the startup.ncf file.

Owning NLM: filesys.nlm

Transaction Tracking Parameters for the Traditional File System

For a description of transaction tracking parameters for the Traditional File System, see the the following table.

Table 1-21 Transaction Tracking Parameters for The Traditional File System

Parameter

Use to

Auto TTS Backout Flag value

Specify whether a server with transactional files will automatically back out of incomplete transactions when the server is restarted.

Supported values:

On The server backs out incomplete transactions when booting Off The server waits for you to answer a prompt before it backs out of transactions

Default: On

You must set this parameter in the startup.ncf file. You cannot set the parameter at the command line.

Owning NLM: filesys.nlm

TTS Abort Dump Flag value

Specify whether a file is created to log transactional backout data.

Supported values:

On The information is saved in tts$log.err Off The information backed out is not saved

Default: Off

If the parameter is set to On, the backed-out information is written to file tts$log.err on volume sys:. You can print the file or view it with a text editor.

Owning NLM: filesys.nlm

TTS UnWritten Cache Wait Time time

Specify how long a block of transactional data can be held in memory.

Supported values: 11 seconds to 10 minutes 59.1 seconds Default: 1 minute 5.9 seconds

Some blocks of transactional data wait for other transactional blocks to be written first.

If one of these blocks reaches its maximum time limit, other write requests are held up and this block is written to disk.

Owning NLM: filesys.nlm

TTS Backout File Truncation Wait Time time

Specify how long allocated blocks remain available for the TTS backout file when these blocks are not in use.

Supported values: 1 minute 5.9 seconds to 1 day 2 hours 21 minutes 51.3 seconds

Default: 59 minutes 19.2 seconds

Owning NLM: filesys.nlm

Additional Information

Topic

See

Using Novell Remote Manager to set server parameters

Server Parameters option in the NW 6.5 SP8: Novell Remote Manager Administration Guide.

Using MONITOR to set server parameters

Server Parameters option in Section 1.94, MONITOR.

Improving server performance

NW 6.5 SP8: Server Operating SystemAdministration GuideOptimizing the NetWare Server in the NW 6.5 SP8: Server Operating SystemAdministration Guide

Editing .ncf files

Using Server Batch Files in the NW 6.5 SP8: Server Operating SystemAdministration Guide

Time synchronization and the timesync.cfg file

NW 6.5 SP8: Network Time Synchronization Administration Guide.