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.
set [parameter] [value]
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.
If you type SET without a parameter, a list of numbered categories appears. When you select a category, the current settings for the server parameters in that category appear along with a brief description of each parameter, the range of valid values, and the default value.
If you type SET with a parameter but no value, the current setting, range of valid values, and a brief description of the parameter are displayed.
If you type SET with a parameter and a value, the operating system is reconfigured according to the specified value.
You can also use the Monitor utility to modify server parameter values. See Section 1.94, MONITOR.
You can modify the values of most SET parameters at the console prompt. The system is immediately configured to that setting. Any setting in the autoexec.ncf file is overridden.
You can enter SET commands that you execute at the console prompt in the autoexec.ncf file. When a parameter value is set in this file, the server configures itself to that setting each time the server is booted—unless the value is modified.
Some commands can be also saved in the startup.ncf file. Use NWCONFIG to edit both the autoexec.ncf and the startup.ncf file.
Some SET parameters control how the system dynamically allocates services. Three types of parameters interact to control the allocation of a service:
Maximum limits control the amount of server resources the operating system can allocate for a particular service.
Minimum limits allow the operating system to allocate a minimum amount of resources as soon as a request is received.
Low minimum limits slow the growth of a particular service. High minimum limits allow rapid growth.
For example, if the minimum number of directory cache buffers is set to 20, the system allocates another buffer resource as soon as a request is made—until 20 cache buffers have been allocated.
When 20 directory cache buffers are allocated, the system waits 2.2 seconds (default) when a request comes in, and then allocates another buffer if the request is still active.
However, if the minimum number of directory cache buffers is set to 40, the system allocates 40 directory cache buffers before it starts slowing the growth by waiting 2.2 seconds after each request.
Wait time limits control how rapidly the operating system can allocate a new resource.
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
Communication parameters control settings for communication buffers. Four parameters configure packet receive buffers; four control the watchdog.
Packet Receive Buffers are areas in the server's memory that are set aside to hold data packets. The packets remain in the buffers while the server processes them.
You can monitor the current number of allocated packet receive buffers on Monitor's General Information screen.
Watchdog Packets are used to make sure stations are connected. If the server doesn't receive a packet from a station within a set time (delay before first watchdog packet), a watchdog packet is sent to the station.
If the station doesn't respond within a configurable amount of time (delay between watchdog packets), another packet is sent.
If the station doesn't respond to a set number of packets, the server assumes that the station is no longer connected and clears the station's connection.
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
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
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
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
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
Owning NLM: tcpip.nlm |
TCP Defend Land Attacks value |
Defend against TCP/UDP Land Attacks. Supported values: On, OffDefault: On
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
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
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
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 allow you to do the following:
Control the Novell eDirectory™ trace file.
Set time intervals for maintenance processes that reclaim disk space, remove external references, and check the consistency of backlinks.
Set eDirectory synchronization intervals and restrictions.
Specify the number of NCP™ retries before timeout.
Mark the status of other servers in the namebase as UP or DOWN.
Specify bindery services contexts.
Handle security issues.
For descriptions of directory services parameters, see the following table.
Table 1-5 Directory Services 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 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:
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 service parameters control Novell Licensing Service diagnosis features.
For a description of licensing parameters, see Table 1-8.
Table 1-8 Licensing Service 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 do not fit aptly or neatly into other categories. The functionality is listed below and described in Table 1-10.
Default response to optional commands
Adding the server's name to the console prompt
Configuring alerts
Controlling alerts for lost or spurious interrupts
Specifying response when invalid parameters are detected
Enabling developer options
Controlling allocation of service processes
Password security
Enabling execution of secure.ncf at startup
Controlling aspects of the kernel, scheduler, and threads
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 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 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 allow you to
Set the threshold for load balancing across multiple processors.
Start secondary processors automatically on startup.
Control whether interrupt statistics are removed from memory when a processor is taken offline or an interrupt handler is removed.
Multiprocessor parameters are described in the following table.
Table 1-11 Multiprocessor Parameters
With NetWare Core Protocol™ (NCP™) parameters, you can
Control NCP packets
Control boundary checking
Assign the NCP Server Packet Signature levels
For a description of NCP parameters, see the following table.
Table 1-12 NCP Parameters
The following are the default settings in NetWare 6.5 for the NSS file system SET 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
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
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 now contain parameters that were previously designated as Directory Caching, File Caching, Error Handling, File System, Locks, and Transaction Tracking
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
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.
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.
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
Three parameters control warnings about volumes that are almost full.
Three parameters control file purging. File-purging parameters influence other parameters which, in turn, control warnings about almost-full volumes.
All deleted files remain on the disk for a specified minimum amount of time. The system calculates a volume's remaining space by subtracting the following from the total space:
Actual files
Salvageable files that can't be purged because their Minimum File Delete Wait Times have not expired
One parameter controls the reuse of turbo FATs.
Ten parameters control file compression.
For a description of file system parameters, see the following table.
Table 1-18 File Parameters for the Traditional File System
Locks parameters control
How many open files each workstation can have
How many open files the system can handle
How many record locks each connection can have
How many record locks the system can handle
There are three types of locks:
File locks secure the file and prevent other stations from accessing it.
Physical record locks control data access by multiple users. They prevent other users from accessing or changing a range of bytes (a record) in a file. They are sometimes referred to as byte-range locks.
Physical record locks are enforced by the system. If a user tries to access a range of bytes that is physically locked, the user receives an Access Denied error message.
Logical record locks also control data access by multiple users. The application assigns a name to each section of data that needs to be locked. The application then locks this name whenever it accesses the data.
Logical locks are enforced only to the extent that the application checks the name each time it needs access to data.
For a description of locks parameters, see the following table.
Table 1-19 Locks 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
A transaction is a set of write operations that must be completed together to maintain file and database integrity.
Write operations consist not only of data and data records, but also of changes to the index and the key structures that are important to an application's continual operation.
Transaction Tracking System™ (TTS™) software guarantees that a transaction is written to disk in its complete form or is backed out if incomplete. This ensures database integrity in case a failure occurs before a transaction is completed.
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
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 Guide |
Editing .ncf files |
|
Time synchronization and the timesync.cfg file |
NW 6.5 SP8: Network Time Synchronization Administration Guide. |