NetWare Integration Guide
International Technical Support Organization IBM PC Server and Novell NetWare Integration Guide December 1995 SG24-4576-00
IBML International Technical Support Organization IBM PC Server and Novell NetWare Integration Guide December 1995 SG24-4576-00
Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xv. First Edition (December 1995) This edition applies to IBM PC Servers, for use with an OEM operating system. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1.
Abstract This document describes the procedures necessary to successfully implement Novell NetWare on an IBM PC Server platform. It describes the current IBM PC Server line and discusses the technology inside the machines. It outlines step-by-step procedures for installing both NetWare V3.12 and V4.1 using both IBM ServerGuide and the original product media. It has a detailed section on performance tuning.
iv NetWare Integration Guide
Contents Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How This Document is Organized . . . . . . . . . . . . . . . . . . . . . . Related Publications International Technical Support Organization Publications ITSO Redbooks on the World Wide Web (WWW) . . . . . .
1.8.5 Selectable Drive Startup . . . . 1.8.6 Unattended Start Mode . . . . . 1.9 Systems Management . . . . . . . . . . . . . . . . . . . . . . . . 1.9.1 DMI . . . . . . . . . . . . . . . 1.9.2 SNMP . . . . . . . . . . . . . 1.9.3 NetFinity . . . . . . . . . . . 1.9.4 SystemView . . . . . . . . . . . 1.10 Fault Tolerance 1.10.1 NetWare SFT III . . . . . . . . . 1.11 Uninterruptible Power Supply (UPS) 1.11.1 APC PowerChute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2 Software Requirements 4.4.3 Information Requested at Time of Installation 4.4.4 Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.5 Installation Procedure 4.5 Installing NetWare 4.1 with the Original CD-ROM 4.5.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Software Requirements . . . . . . . . . . . . . 4.5.3 Installation Procedure 4.
viii NetWare Integration Guide
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. Copyright IBM Corp. 1995 SMP Shared Secondary Cache . . . . . . . . . . . . . . . . . . . . . . . . SMP with Dedicated Secondary Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-Way Interleaved Memory Banks Dual Path Bus Implementation . . . . . . . . . . . . . . .
52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. 100. 101. 102. 103. 104. 105. x NetWare Integration Guide Advanced Diagnostic Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Selection Menu RAID Configuration Program - Adapter Selection . . . . . . . RAID Configuration Program - Main Menu . . . . . . . . . . . . .
106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 129. 130. 131. 132. 133. 134. 135. 136. 137. 138. 139. 140. 141. 142. 143. 144. 145. NetFinity Network Driver Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetFinity Installation NetFinity Services for NetWare . . . . . . . . . . . . . . . . . . . . . . NetFinity Installation - Copying Files . . . . . . . . . . . . . . . . . . .
xii NetWare Integration Guide
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. Copyright IBM Corp. 1995 ECC Memory Performances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Memory Implementations . . . . . . . . . . . . . . . . . . . . . SCSI Adapters Summary PCI SCSI Adapters Summary . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Disks Performance Characteristics . . . . . . . . . . . . . . . . . . . . . . . .
xiv NetWare Integration Guide
Special Notices This document is intended for IBM customers, dealers, systems engineers and consultants who are implementing Novell NetWare on an IBM PC Server. The information in this publication is not intended as the specification of any programming interfaces that are provided by IBM. References in this publication to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates.
NetView PS/2 Power Series 800 SystemView VM/ESA OS/2 Personal System/2 Presentation Manager Ultimedia The following terms are trademarks of other companies: C-bus is a trademark of Corollary, Inc. PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Windows is a trademark of Microsoft Corporation.
Preface This document describes the procedures necessary to implement Novell NetWare on IBM PC Server platforms. It provides detailed information on installation, configuration, performance tuning, and management of the IBM PC Server in the NetWare environment. It also discusses the features and technologies of the IBM PC Server brand and positions the various models in the brand.
Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this document.
IBM employees may access LIST3820s of redbooks as well. Point your web browser to the IBM Redbooks home page at the following URL: http://w3.itsc.pok.ibm.com/redbooks/redbooks.
xx NetWare Integration Guide
Chapter 1. IBM PC Server Technologies IBM PC Servers use a variety of technologies. This chapter introduces many of these technologies and gives examples of system implementations where they are used. 1.1 Processors The microprocessor is the central processing unit (CPU) of the server. It is the place where most of the control and computing functions occur. All operating system and application program instructions are executed here.
performance. (Please see 1.3, “Memory” on page 3 for a discussion of memory speeds and system performance.) The point is that you cannot compare system performance by simply looking at the speed at which the processor is running. A 90 MHz machine with a set of matched components can out perform a 100 MHz machine which is running with slow memory. IBM PC Servers are always optimized to incorporate these factors and they always deliver a balanced design. 1.1.
1.2 Multiprocessing Multiprocessing uses two or more processors in a system to increase throughput. Multiprocessing yields high performance for CPU intensive applications such as database and client/server applications. There are two types of multiprocessing: • • Asymmetric Multiprocessing Symmetric Multiprocessing Asymmetric Multiprocessing: In asymmetric multiprocessing the program tasks (or threads) are strictly divided by type between processors and each processor has its own memory address space.
The key is to achieve a balanced design where the speed of the processor is matched to that of the external components. IBM engineers achieve a balanced design by using several techniques to reduce the effective access time of main system memory: • Cache • Interleaving • Dual path buses • SynchroStream technology 1.3.1 Caches Research has shown that when a system uses data, it will be likely to use it again.
• Write-Back Cache Write operations are also performed on the cache. Transfer to standard memory is done if: − − Memory is needed in the cache for another operation Modified data in the cache is needed for another application The third level of cache or L3 cache is sometimes referred to as a victim cache. This cache is a highly customized cache used to store recently evicted L2 cache entries. It is a smaller cache usually less than 256 bytes.
Dedicated Cache: This SMP design supports a dedicated L2 cache for each processor. This allows more cache hits than a shared L2 cache. Adding a second processor using a dedicated L2 cache can improve performance as much as 80%. With current technology, adding even more processors can further increase performance in an almost linear fashion up to the point where the addition of more processors does not increase performance and can actually decrease performance due to excessive overhead.
In interleaved systems, memory is currently organized in either two or four banks. Figure 3 on page 7 shows a two-way interleaved memory implementation. Figure 3. Two-Way Interleaved M e m o r y Banks Memory accesses are overlapped so that as the controller is reading/writing from bank 1, the address of the next word is presented to bank 2. This gives bank 2 a head start on the required access time. Similarly, when bank 2 is being read, bank 1 is fetching/storing the next word.
CPU L2 Cache Memory Control. Memory I/0 Control. BUS ISA/EISA/MCA/VL/PCI Slots SCSI VGA Figure 4. Dual Path Bus Implementation Without a dual path bus, there is often contention for system resources such as main memory. When contention between the processor and a bus master occurs, one has to wait for the other to finish its memory cycle before it can proceed.
1.4 Memory Error Detection and Correction IBM PC servers implement four different memory systems: • Standard (parity) memory • Error Correcting Code-Parity • Error Correcting Code (ECC) memory • ECC Memory on SIMMs (EOS) Memory 1.4.1 Standard (Parity) Memory Parity memory is standard IBM memory with 32 bits of data space and 4 bits of parity information (one check bit/byte of data).
Figure 5. ECC M e m o r y Operation As the data is read from memory, the ECC circuit again performs a scan and compares the resulting pattern to the pattern which was stored in the check bits. If a single-bit error has occurred (the most common form of error), the scan will always detect it, automatically correct it and record its occurrence. In this case, system operation will not be affected. The scan will also detect all double-bit errors, though they are much less common.
Figure 6 on page 11 shows the implementation of ECC-P. When ECC-P is enabled via the reference diskette, the controller reads/writes two 32-bit words and 8 bits of check information to standard parity memory. Since 8 check bits are available on a 64-bit word, the system is able to correct single-bit errors and detect double-bit errors just like ECC memory. 32 data 4 parity 32 data 4 parity 64 bits for data 8 bits for ECC Memory Controller Figure 6.
1.4.5 Performance Impact As previously discussed, systems which employ ECC memory have slightly longer memory access times depending on where the checking is done. It should be stressed that this affects only the access time of external system memory, not L1 or L2 caches. Table 1 shows the performance impacts as a percentage of system memory access times of the different ECC memory solutions. Again, these numbers represent only the impact to accessing external memory.
1.5.1 ISA Bus The Industry Standard Architecture (ISA) is not really an architecture at all but a defacto standard based on the original IBM PC/AT bus design. The main characteristics of the ISA bus include a 16-bit data bus and a 24-bit address bus. The bus speed is limited to 8 MHz and it did not allow for DMA and bus masters in its original form. It does not support automatically configuring adapters and resolving resource conflicts among adapters nor does it allow for sharing of interrupts.
Figure 7. Micro Channel - Basic Data Transfer (20 MBps) However, in many cases, blocks transferred to and from memory are stored in sequential addresses, so repeatedly sending the address for each 4 bytes is unnecessary. With data streaming transfers, the initial address is sent, and then the blocks of data are sent; it is then assumed that the data requests are sequential. Figure 8 shows 40 MBps data streaming in operation. Figure 8.
The Micro Channel supports another mode of data streaming whereby the address bus can also be used to transfer data. This is depicted in Figure 9 on page 15. Figure 9. Micro Channel - Data Streaming Transfer (80 MBps) As can be seen from this figure, in this mode, after the initial address is presented during the first bus cycle, the address bus is then multiplexed to carry an additional 32 bits of data. This results in an effective data transfer rate of 80 MBps.
is available with previous bus architectures. In order to optimize performance, the PCI architecture strictly limits the number of loads (hence the number of adapters) on the bus. It therefore needs an I/O expansion bus to handle the more routine I/O devices. The bus has 32 or 64 bits of address and data, is processor independent and is capable of speeds over 50 MHz. 8-bit and 16-bit devices are not supported.
4. Small Computer System Interface (SCSI) - The SCSI interface is a high speed parallel interface that transfers eight bits at a time rather than one bit at a time for the ST506 and ESDI serial interfaces. Thus data transfer rates for SCSI are measured in mega bytes versus mega bits and are considerably faster than those of the serial interfaces. SCSI is also a bus level interface which makes it very flexible.
It defines an 8-bit interface with a data transfer rate of 5 MBps. SCSI-II is the second SCSI standard and is defined in ANSI standard X3T9.2/375R REV10K. It defines extensions to SCSI-I which allow for 16 and 32-bit devices, a 10 MBps transfer rate, and other enhancements discussed below. • Common Command Set The SCSI standard defines a set of commands which must be interpreted by all devices that attach to a SCSI bus. This is called the common command set.
SCSI bus bandwidth. If the controller held onto the bus while waiting for the device to seek, then the other devices would be locked out. This is also sometimes referred to as overlapped operations or multi-threaded I/O on the SCSI bus. This feature is very important in multitasking environments. • Synchronous versus Asynchronous An asynchronous device must acknowledge each byte as it comes from the controller. Synchronous devices may transfer data in bursts and the acknowledgments happen after the fact.
standard 8-bit SCSI devices. Up to seven SCSI physical devices may be attached to this adapter. This adapter has a dedicated 80C186 local processor on board, which allows it to implement advanced features such as TCQ. The dual bus design of the adapter prevents access to internal DASD from the external port. It also allows the maximum cable length to be calculated individually for each bus. This allows for additional capability externally.
In addition to the features supported with the IBM SCSI-2 F/W PCI Adapter, the IBM SCSI-2 F/W RAID adapter provides a RAID controller. Please reference 1.6.5, “RAID Technology” on page 22 for a discussion on RAID. 1.6.3.1 Summary The following tables summarize the features of the IBM SCSI adapters. Table 3.
to the desired cylinder of the disk. The latency is the amount of time it takes for the disk to rotate to the proper sector on that cylinder. It should be noted that two disks of the same physical size, for example 3.5-inch disks, will differ in their access times with the larger capacity disk having a better access time. This is due to the fact that the distance between cylinders is shorter on the larger disk and, therefore, seek time is reduced.
Disks are often among the least reliable components of the computer systems, yet the failure of a disk can result in the unrecoverable loss of vital business data, or at the very least a need to restore from tape with consequent delays. • Cost It is cheaper to provide a given storage capacity and a given performance level with several small disks connected together than with a single disk. There is nothing unusual about connecting several disks to a computer to increase the amount of storage.
1.6.6.1 RAID-0 - Block Interleave Data Striping without Parity Striping of data across multiple disk drives without parity protection is a disk data organization technique sometimes employed to maximize DASD subsystem performance (for example, Novell NetWare′ s data scatter option). An additional benefit of this data organization is drive spanning . With data striped across multiple drives in an array, the logical drive size is the sum of the individual drive capacities.
Disk Controller Disk 1 Disk 2 Figure 12. RAID-1 (Disk Mirroring) Disk mirroring involves duplicating the data from one disk onto a second disk using a single controller. Disk duplexing is the same as mirroring in all respects, except that the disks are attached to separate controllers. The server can now tolerate the loss of one disk controller, as well as or instead of a disk, without loss of the disk subsystem′s availability or the customer′s data.
Disk Controller DATA AAA BBB CCC DATA MIRROR CCC AAA BBB DATA DDD EEE FFF DATA MIRROR FFF DDD EEE Disk 1 Disk 2 Disk 3 Figure 14. RAID-1 Enhanced, Data Strip M i r r o r i n g Some vendors have also implemented another slight variation of RAID-1 and refer to it as RAID-10 since it combines features of RAID-1 and RAID-0. Others refer to this technique as RAID-6, which is the next available RAID level.
1.6.6.4 RAID-2 - Bit Interleave Data Striping with Hamming Code This type of array design is another form of data striping: it spreads the data across the disks one bit or one byte at a time in parallel. This is called bit (or byte) interleaving. Thus, if there were five disks in the array, a sector on the first drive will contain bits 0 and 5, and so on of the data block; the same sector of the second drive will contain bits 1 and 6, and so on as shown in Figure 16.
1.6.6.5 RAID-3 - Bit Interleave Data Striping with Parity Disk The use of additional disks to redundantly encode customer′s data and guard against loss is referred to as check sum, disk parity or error correction code (ECC). The principle is the same as memory parity, where the data is guarded against the loss of a single bit. Figure 17 shows an example of RAID-3.
Disk Controller xxxxx xxxxx xxxxx xxxxx Parity yyyyy yyyyy yyyyy yyyyy Parity Block 0 Block n Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 xxxxx and yyyyy = Blocks belonging to long files Figure 18. RAID-4 (Block Interleave Data Striping with One Parity Disk) 1.6.6.7 RAID-5 - Block Interleave Data Striping with Skewed Parity The RAID-5 design tries to overcome all of these problems.
1.6.6.
1.6.7 Recommendations • Use IDE on smaller systems IDE actually outperforms SCSI on systems where only one or two devices are attached. Several models of the IBM PC Server 300 and 320 lines implement IDE as an integrated controller on the planar board. This is more than adequate if no more than a couple of hard disks will be used.
system memory because they occur across an I/O expansion bus. This means that when shared RAM adapters are involved, the CPU spends a significant amount of time doing the primitive task of moving data from point A to point B. On lightly loaded servers providing traditional productivity applications such as word-processing, spreadsheets, and print sharing, this is not really a problem.
sometimes moves quickly to the CPU when servers are upgraded to incorporate LANStreamer technology. Of course, other components can emerge as the bottleneck as throughput increases. The wire (network bandwidth) itself can become a bottleneck if throughput requirements overwhelm the ability of the network technology being used. For example, if an application requires 3 MBps of throughput, then a token-ring at 16 Mbps will not perform the task. In this case a different network technology must be employed.
• • • Attaching more than four Ethernet 10Base-2 segments to the server Providing switching between 10Base-T and 10Base-2 segments Conserving server slots An add-on to NetFinity provides an advanced Ethernet subsystem management tool. Parameters such as packets/second or total throughput can be monitored for each port, for traffic within an adapter, or for traffic between adapters.
1.8.1 Tamper-Evident Cover Systems equipped with a tamper-evident cover have a key lock for their covers and internal I/O devices. In the locked position, it mechanically prevents the covers from being removed. The key has been changed to a type that can be duplicated only by the manufacturer. If the covers are forced open, an electro-mechanical switch and perimeter sensor detect the intrusion.
there is a power failure; the machine is able to recover with the keyboard lock still in place. 1.8.3.1 Privileged-Access Password Because the power-on and keyboard passwords can be defeated by deactivating the battery inside the system, another level of password protection is provided. This security feature is called the privileged-access password. It provides a much higher level of security.
1.8.5 Selectable Drive Startup Selectable drive startup allows the system owner or administrator to select the IPL source and sequence. This allows the system owner to control the IPL source, but prevents the user from modifying the source and sequence. For example, the diskette drive can be excluded as an IPL source. This feature helps to ensure that the system owner′s specified operating system is loaded.
manage those products. As DMI technology evolves, installation and management in desktops and servers will become easier. It should be noted that the DMI specs say nothing about the transport protocol that is used between the manageable products and the management applications. Both of these elements of a DMI compliant system can be implemented using any native transport protocol available in the system.
The simplest MIF file contains only the component ID group, but MIFs can become as complex as needed for any given product. 1.9.1.3 Management Interface (MI) The management interface (MI) shields managements applications from the different mechanism used to obtain management information for products within a desktop system. The MI allows a management application to query for a list of manageable products, access specific components and get and set individual attributes.
SNMP provides a means of communicating between the network management stations and the agents in the network resources. This information can be status information, counters, identifiers, etc. The SNMP manager continuously polls the agents for error and statistical data. The performance of the network will be dependent upon the setting of the polling interval. 1.9.2.
• • • Agents maintain vital information about their respective devices and networks. This information is stored in a MIB. The SNMP manager polls each agent for MIB information and stores and displays this information at the SNMP manager station. In this manner, the system administrator can manage the entire network from one management station. Agents also have the ability to send unsolicited data to the SNMP manager. This is called a trap. 1.9.
• System Profile Allows the systems administrator to define additional information for each system, such as location • System Monitor Provides system performance monitoring utilities, such as CPU, DASD, and Memory • Critical File Monitor Can generate alerts when critical files are changed or deleted • System Partition Access Allows an administrator to access the system partition on remote PS/2s • Predictive Failure Analysis Monitors PFA-enabled drives for errors • ServerGuard Service Can monitor
It also supports Novell NetWare. This means that there is a version of NetFinity Services which installs as a NetWare NLM on the file server and allows the server to be managed by a NetFinity Manager station. NetFinity Services can also be installed on a Windows NT server and used to manage this platform as well.
• File Transfer Can send/receive files to the remote system. • Remote Session Can open a remote console to the managed device. • Screen View Can take a snapshot of any screen on the remote device. • DMI Browser Enables you to view information about DMI compliant hardware and software. • Process Manager Enables you to start/stop/view processes running on the managed device. • Software Inventory Can scan remote device for installed software using a software dictionary .
Manager services and system module. This feature provide an extensive capability to merge dissimilar LANs into a single view of NetFinity managed assets. 1.9.3.4 DMI Support NetFinity is the first product available to customers that includes DMI support. NetFinity implementation of DMI support provides instrumentation from its System Information Tool to the DMI service layer for both OS/2 and Windows clients.
graphical drag and drop capability of OS/2 or AIX/6000. The primary benefit of the end-use dimension is the end-user productivity. Some examples of products that have implemented SystemView conforming interfaces are: • • • • • • • LAN Network Manager NetView for OS/2 NetView for AIX DataHub Family of Database Management Products NetView Performance Monitor NetView Distribution Manager/2 Service Level Reporter 2.
• • • Open and extendable data model: This specifies the data definitions that represent the information processing data of an enterprise. The SystemView data dimension includes descriptions of the characteristics of resources and the relationships among them. Heterogeneous access: This structure provides for access of systems management data across heterogeneous platforms through the interfaces. Support of existing applications: Existing systems management applications are supported by the structure.
1.10.1 NetWare SFT III NetWare SFT III is a special version of the NetWare 3.x or 4.x NOS which adds a high degree of fault tolerance. It is composed of two servers, a primary and a secondary, which are mirrored together. To clients on the network, only the primary server appears to be active. The secondary server remains in the background; however, it maintains the same essential memory image and the same disk contents as the primary server.
Mirrored Server Link (MSL): The MSL is a bidirectional point-to-point connection that is used by the two servers to synchronize with each other. Information such as client requests and acknowledgments are passed back and forth on the MSL. After a failure has occurred, the MSL is used to synchronize the memory and disk of the failed server. As it is being brought back up, the active server transfers the entire contents of its MS Engine memory image to the formally inactive server.
Consequently, clients only receive reply packets from the primary server′ s IOEngine; this is the same IOEngine to which they sent the original request packet. The clients view the mirrored server as any other NetWare server. Clients send a single request packet and receive a single reply packet from the same address. The duplication of requests to the secondary IOEngine and synchronization of events to both server engines happens transparently to network clients.
The primary server sends the disk changes over the mirrored server link to update the repaired server and to mirror the contents of the disk. Disk mirroring occurs in the background during idle cycles. Scenario 2. Hardware fails in the secondary server: The primary server notifies the system administrator that the secondary server is down and that it is still the primary server. SFT III keeps track of any disk changes following the secondary server′s failure.
1.11 Uninterruptible Power Supply (UPS) Digital computers require a clean source of direct current (DC). It is the computer′s power supply which takes an alternating current (AC) from the input line and transforms it into clean DC voltages. However, problems on the input AC signal can often lead to DC voltages that are less than satisfactory for the digital circuits to operate properly. There are five main types of AC line problems that can cause trouble for a computer system: 1.
The primary service, however, that the UPS provides in the case of AC line problems is extra time. While a UPS can enable the server to continue operating even if there is a power loss, the primary benefit of a UPS is that the server software has time to ensure that all caches are written to disk, and to perform a tidy shutdown of the system. Some UPSs also offer an automated shutdown and reboot facility for network operating systems.
Flex Events is programmable such that when an event occurs, you can configure PowerChute to take certain actions.
Chapter 2. IBM PC Server Family Overview The IBM PC Server family contains three product lines which offer different features and capabilities: • The PC Server 300 series This series is targeted at small enterprises or workgroup LANs. These machines offer leading technology and are very price competitive. They are more limited in terms of upgrade and expansion capabilities than the other two lines in the family.
2.1 IBM PC Server Model Specifications The following tables show the specifications for each model in the current line. They are included for a reference of the standard features of each line. 2.1.1 IBM PC Server 300 Table 8.
2.1.2 IBM PC Server 310 Table 9. IBM PC Servers 310 Models System Model 8639 0XT 8639 MXT Processor Pentium 75 Pentium 75 Bus Architecture PCI/ISA PCI/MCA Disk Controller PCI SCSI-2 Fast PCI SCSI-2 Fast STD Hard File Size 1.08GB 1.08GB Memory Std/Max (MB) 16/192 16/192 L2 Cache (KB) 256 256 Graphics SVGA SVGA Chapter 2.
2.1.3 IBM PC Server 320 EISA Table 10. IBM PC Servers 320 EISA Models System Model 8640 0N0 8640 ONJ 8640 0P0 8640 0PT Processor Pentium 90 Pentium 90 Pentium 90 Pentium 90 SMP 1-2 P90 1-2 P90 1-2 P90 1-2 P90 Bus Architecture PCI/EISA PCI/EISA PCI/EISA PCI/EISA Disk Controller ISA IDE PCI SCSI-2 F/W ISA IDE PCI SCSI-2 F/W ISA IDE PCI SCSI-2 F/W Raid ISA IDE PCI SCSI-2 F/W Raid STD Hard File Size None 1.12GB None 2 * 1.
2.1.4 IBM PC Server 320 MCA Table 11. IBM PC Servers 320 M C A Models System Model 8640 MX0 8640 MXT 8640 MYO 8640 MYT 8640 MYR Processor Pentium 75 Pentium 75 Pentium 90 Pentium 90 Pentium 90 SMP 1-2 P75 1-2 P75 1-2 P75 1-2 P75 1-2 P75 Bus Architecture PCI/MCA PCI/MCA PCI/MCA PCI/MCA PCI/MCA Disk Controller PCI SCSI-2 F/W PCI SCSI-2 F/W PCI SCSI-2 F/W PCI SCSI-2 F/W PCI SCSI-2 F/W RAID STD Hard File Size None 1.08GB None 1.12GB 2 * 1.
2.1.5 IBM PC Server 500 Table 12. IBM PC Server 500 Models System Model 8641 0Y0 8641 1Y0 8641 0YT 8641 0YV 8641 0YR 8641 0YS Processor Pentium 90 Pentium 90 Pentium 90 Pentium 90 Pentium 90 Pentium 90 Bus Architecture MCA MCA MCA MCA MCA MCA Disk Controller SCSI-2 F/W SCSI-2 F/W RAID SCSI-2 F/W SCSI-2 F/W SCSI-2 F/W RAID SCSI-2 F/W RAID Hard File Size None None 1.12GB 2.25GB 1.12GB x 3 2.
2.1.6 IBM PC Server 520 EISA Table 13. IBM PC Servers 520 EISA Models System Model 8641 EZ0 8641 EZV 8641 EZS 8641 EZE Processor Pentium 100 Pentium 100 Pentium 100 Pentium 100 SMP 1-2 P 100 1-2 P 100 1-2 P 100 1-2 P 100 Bus Architecture PCI/EISA PCI/EISA PCI/EISA PCI/EISA Disk Controller PCI SCSI-2 F/W PCI SCSI-2 F/W PCI SCSI-2 F/W RAID PCI SCSI-2 F/W RAID Hard File Size None 2.25GB 2 * 2.25GB 4 * 2.
2.1.7 IBM PC Server 520 MCA Table 14. IBM PC Servers 520 M C A Models System Model 8641 MZ0 8641 MZV 8641 MZS 8641 MZE 8641 MZL Processor Pentium 100 Pentium 100 Pentium 100 Pentium 100 Pentium 100 SMP 1-2 P100 1-2 P100 1-2 P100 1-2 P100 1-2 P100 Bus Architecture PCI/MCA PCI/MCA PCI/MCA PCI/MCA PCI/MCA Disk Controller PCI SCSI-2 F/W PCI SCSI-2 F/W PCI SCSI-2 F/W RAID PCI SCSI-2 F/W RAID PCI SCSI-2 F/W RAID Hard File Size None 2.25GB 2 * 2.25GB 4 * 2.25GB 6 * 2.
2.1.8 IBM PC Server 720 Table 15.
64 NetWare Integration Guide
Chapter 3. Hardware Configuration The different technologies used to implement the PC Server family require different methods for configuration. Unfortunately, there is no one common configuration program which can be run on a machine to completely configure it. In most cases, multiple programs will need to be run in order to complete this process. This chapter gives instructions on using the various configuration programs and when to use each one. There are some model dependencies, however.
What is the Server Architecture? PCI/ISA/EISA (300/310/320/520 PCI/MCA or MCA (500/520/720) - Setup Program Section - EISA Configuration utility Section - SCSI Select Utility Section - System Programs Section - Reference Diskette - Diagnostic Diskette Is the Server a RAID Model? No Yes - Raid Controller Utility Section Figure 22.
3.1 The Setup Program The setup program is used to configure system options on ISA and EISA machines. The system options include such things as diskette and hard disk options, video subsystem, and system memory. These parameters are controlled by system BIOS and, hence, need to be modified before the operating system boots. To access the setup program: 1. Turn on the server and watch the screen. The BIOS level appears. 2. When the message Press to enter SETUP appears, press F2. 3.
The Main panel contains fields which allow the user to: • Modify date and time Configure the diskette drives Configure the IDE disks Configure the video Enable/Disable level 2 system memory cache • • • • Notes: 1. Video BIOS Shadow This option allows the user to shadow the video BIOS into RAM for faster execution. The pre-installed SVGA Adapter supports this feature. 2. IDE Devices If no IDE DASD devices are installed, you must set all the IDE devices to none.
3.1.2.1 Advanced Menu - Boot Options By pressing the Enter key, a screen like that shown in Figure 25 will appear. Phoenix BIOS Setup - Copyright 1985-94 Phoenix Technologies Ltd. Advanced Boot Options Boot Sequence: Swap Floppies: Floppy Check: [A: then C:] [Normal] [Enabled] SETUP prompt: POST errors: [Enabled] [Enabled] Figure 25. PC Server 320 Setup Program - Boot Options M e n u Boot Sequence: Boot sequence allows the user to change the order the system uses to search for a boot device.
If disabled, the system ignores the error and attempts to boot. 3.1.2.2 Advanced Menu - Peripherals To reach this menu: • Press ESC to quit the Boot options. Use the arrows keys to select the integrated peripherals option. Press Enter. • • A screen like the one in Figure 26 will appear: Phoenix BIOS Setup - Copyright 1985-94 Phoenix Technologies Ltd.
Memory Gap: Some ISA network adapters need to be mapped in system memory address space, normally at the upper end. Since the ISA bus is limited to 24-bit addressing (0-16 MB), systems with more than 16MB of memory installed will not accommodate these adapters. When enabled, this selection will remap system memory such that a gap is created between the addresses of 15 and 16MB. This gap is then used to map the I/O space on the adapter into this area. 3.1.
Enter password If you enter the wrong password, the following message appears on the screen, and you are prompted again: Incorrect password After 3 incorrect attempts, the following message appears and you must turn off the server and start again: System disabled Notes: 1. Before you set a supervisor password, you must first set your selectable drive-startup sequence. 2. Only the supervisor can change the supervisor password. 3.
Note BIOS of PCI/EISA servers is located in a Flash ROM on the motherboard. If necessary, it can be updated with a bootable diskette which has the new BIOS (.BIN) file. This file will be named: • • M4PE_Txx.BIN for DX2-66 models M5PE_Txx.BIN for Pentium models Where xx is the BIOS level as it appears when booting. For more information on how to obtain BIOS updates, please reference Appendix B, “Hardware Compatibility, Device Driver, and Software Patch Information” on page 199.
3.2 EISA Configuration Utility This utility is used when you add or remove an ISA or EISA adapter. We will use an example to illustrate the process. In our example we will add an Auto T/R 16/4 ISA adapter in slot 3 of a PC Server 320. The steps to complete the process are: 1. Boot with the EISA configuration utility diskette. 2.
EISA Configuration Utility Help=F1 Listed are the boards and options detected in your computer. . Press INSERT to add the boards or options which could not be detected or which you plan to install . Press DEL to remove the highlighted board from your configuration . Press F7 to move the highlighted board to another slot .
After adding EISA or ISA adapters, you will often need to view and/or edit the settings for the adapter. To view or edit an adapter′s details: a. From the Main menu, select step 3 (View or Edit Details) with the arrow key. b. Press Enter to view configuration details. You will see a screen similar to that shown in Figure 32 Step 3: View or edit details Press Enter to edit the functions of the highlighted item. Press F6 to edit its resources (IRQs, DMAs, I/O ports, or memory).
System - IBM Dual Pentium PCI-EISA System Board Jumper Name: W1 - Level 1 Cache Default factory settings: OFF Change settings to: OFF . . 1 2 Figure 33. EISA Configuration Utility - Step 4 d. Press F7 if you want to print configuration settings.
3.3 SCSI Select Utility Program This utility is used on PCI/EISA models of the IBM PC Server line and allows the user to: • • • View and modify parameters for the SCSI controller View and modify parameters of SCSI devices Perform low-level formatting of attached SCSI hard disks To access the SCSI Select Utility Program: • • Turn on the server and watch the screen When the message Press appears, press Ctrl and A simultaneously. A screen like the one in Figure 34 will appear.
The fields on this panel are described as follows: SCSI Parity Checking: Select this option to enable or disable SCSI Parity checking on the host adapter. If enabled, the host adapter will check parity when reading from the SCSI bus to verify the correct transmission of data from your SCSI devices. SCSI Parity checking should be disabled if any attached SCSI device does not support SCSI parity. Most currently available SCSI devices do support SCSI parity.
SCSI Device Configuration SCSI Device ID #0 #1 #2 #3 #4 #5 #6 Initiate Sync Negotiation Yes Yes Yes Yes Yes Yes Yes Max Sync Transfer Rate 10.0 10.0 10.0 10.0 10.0 10.0 10.0 Enable disconnection Yes Yes Yes Yes Yes Yes Yes Initiate Wide negotiation Yes Yes Yes Yes Yes Yes Yes Options listed below have NO EFFECT if the BIOS is disabled Send start init command No No No No No No No Include in BIOS Scan Yes Yes Yes Yes Yes Yes Yes SCSI Device ID #8 #9 #7 Yes 10.
The SCSI-2 Fast and Wide adapter issues the start unit command to each drive one at a time. The SCSI-2 Fast/Wide Streaming RAID adapter issues the start unit command to two drives at a time. Note In order to take advantage of this option, verify that the auto-start jumpers have been removed on hard drives. Otherwise, the drives will spin up twice: once at Power on Reset (POR) time and again when the adapter sends the start unit command.
• • • Press Enter to edit the parameter. Use the arrow keys to select the new value or press Esc to quit. Press Enter to validate the new value. When finished: • • • • Press Esc to quit the SCSI Advanced Configuration options menu. Press Esc to quit the Configuration menu. Use the arrow keys to select the SCSI Disk utility. Press Enter. A screen like the one in Figure 38 will appear.
These programs are obtainable in several ways: • Shipped with the server on two diskettes called the reference diskette and the diagnostic diskette • Created from images for these diskettes on the ServerGuide CD-ROM shipped with the system. • On the system partition of the machine Non-array systems are shipped with the system programs already installed in a protected area of the hard disk called the system partition.
Main Menu Select one: 1. Start Operating System 2. Backup/Restore system programs 3. Update system programs 4. Set configuration 5. Set Features 6. Copy an option diskette 7. Test the computer 8. More utilities Enter F1=Help F3=Exit Figure 39. System Programs - Main M e n u 3.4.2 Starting From the Reference Diskette To start the system programs from the reference diskette: 1. Turn off the server. 2. Insert the reference diskette into your diskette drive. 3. Turn on the system.
Periodically, updated versions of the reference diskette and diagnostic diskette are made available. This option copies a new version of the system programs to the system partition. This option does not apply to disk-array models. Note This utility will only install system programs that are a later version that the ones already installed on the system partition. 4. Set configuration This option contains programs used to view, change, back up, or restore the configuration information.
3.4.4 Backup/Restore System Programs Menu When you select this option from the Main Menu, a screen like the one in Figure 40 will appear. Backup / Restore System Programs Select One: 1.-Backup the system diskette 2.-Backup the system partition 3.-Restore the system partition Enter F1=Help F3=Exit Figure 40. System Programs - Backup/Restore System Programs M e n u The following options are available: 1. Backup the system diskettes Makes a backup copy of the Reference and Diagnostic diskettes. 2.
Set Configuration Select One: 1.-View configuration 2.-Change configuration 3.-Backup configuration 4.-Restore configuration 5.-Run automatic 6.-Display memory map 7.-Set and view SCSI device configuration Enter F1=Help F3=Exit Figure 41. System Programs - Set Configuration M e n u The following options are available: 1.
View Configuration Total System Memory Installed memory....................................32768KB(32.0MB) Usable Memory.......................................32584KB(31.6MB) Built In Features Installed Memory....................................32768KB(32.0MB) Diskette drive 0 Type...............................2.88MB 3.5† Math Coprocessor....................................Installed Num Lock............................................Off Display F1 prompt...................................
If a setting conflicts with another, an asterisk(*) appears next to the conflicts and the word conflicts appears at the right corner of the windows. You must remove all conflicts before the configuration can be saved. Note Some settings are set by the system and can not be overridden. The user can change only those settings which have not been set by the system. These are the settings enclosed in brackets( [ .. ] ). 3.
Memory Map 0C000H SVGA Adapter Micro Channel slot............................5 Size(in KB)...................................32 0C8000H IBM SCSI-2 Fast/Wide Streaming RAID Adapter Micro Channel Slot............................1 Size(in KB)...................................8 0CA000H Memory not being used Size(in KB)...................................88 F1=Help F3=Exit Figure 43. Set Configuration - M e m o r y Map 7.
Set and View SCSI Device Configuration SCSI Configuration Verification................[Enabled] Slot 1-IBM SCSI-2 Fast/Wide Adapter SCSI Address (ID)...........................7 SCSI Device Device type............................Hard Disk Device Address (ID,LUN)................6,0 Device size ...........................540MB Presence error reporting...............[Enabled] SCSI Device Device Type............................ROM Device Device address (ID,LUN)................3,0 Presence error reporting.......
Set Features Select one: 1.-Set date and time 2.-Set password and unattended start mode 3.-Set keyboard speed 4.-Set console 5.-Set startup sequence 6.-Set fast startup mode 7.-Set power-on features Enter F1=Help F3=Exit Figure 45. Set Features M e n u 1. Set date and time This allows you to set the current date and time. Once set, CMOS RAM keeps the date and time even when the system is powered off. 2.
Set Passwords and Security features Select one: 1.- Set Power-On password 2.- Change Power-On password 3.- Remove Power-On password 4.- Set unattended start mode 5.- Set privileged-access password 6.- Change privileged-access password 7.- Remove privileged-access password 8.- Set unauthorized-access monitor Enter F1=Help F3=Exit Figure 46. Set Passwords and Security Features a. Set power-on password This prevents unauthorized use of the server.
c. Remove power-on password This option shows the instructions for removing the current power-on password which are: 1) Turn off the server and wait a few seconds; then turn it on. 2) When Enter password appears, type the current password followed by a space. 3) Press Enter. Attention! If the unattended start mode is active, you must remove it before you can change or remove the power-on password because the password prompt does not appear when the unattended start mode is set. d.
This option allows you to change the administrator password. You must know the current privileged-access password in order to complete the procedure. g. Remove privileged password This option removes the administrator password. You must know the current privileged-access password in order to complete the procedure. h. Set unauthorized-access monitor If your system is equipped with a tamper-evident cover, you can select this option to enable or disable the unauthorized-access monitor feature.
This option lets you select the sequence of the drives on which the system searches for a valid boot record when you turn it on. The default startup sequence is the first diskette drive followed by the first hard disk. You can alter this sequence with this utility. Figure 47 shows an example of the startup sequence when one hard disk is installed. Set Startup Sequence Startup Number Device 1 . . . . . .[2.88Mb 3.5-inch diskette drive ] 2 . . . . . .[SCSI ROM device slot 1 bus 0 (ID,LUN)..6,0] 3 . . . .
Set Power-On Features Serial-Port Power-On mode..................[Disabled] Real-Time-Clock Power-On mode..............[Enabled] Power-On day of the month.............01 Power-On time.........................12:00 System-error restart.......................[Disabled] F1=Help F3=Exit F9=Toggle Figure 48. Set Power-On Features Screen Serial-Port Power-On Mode: This option allows you to start the server using a modem.
3.4.8 More Utilities Menu When you select this option from the Main Menu, a screen like the one in Figure 49 will appear. More Utilities Select one: 1.- Display revision levels 2.- Display system error log 3.- Stand-alone utility information 4.- Set system identification 5.- Set character font Enter F1=Help F3=Exit Figure 49. More Utilities M e n u This panel has the following options: 1. Display revision levels This displays information that you might need if you required service.
This displays and resets the entries in the error log. As errors occur, they are recorded in this log. Error log information is helpful when service is required. Figure 51 on page 99 is an example of a System Error Log screen.
1. Start the system programs. 2. When the system programs main menu appears, press and hold Ctrl and then press A. A message appears telling you to insert the diagnostic diskette. 3. Insert the diagnostic diskette. After a few seconds, a screen like the one in Figure 52 appears. Advanced Diagnostic Menu Select One: 1.-Run System Checkout 2.-Format the hard disk Enter F1=Help F3=Exit Figure 52.
Select this option to test the devices one time. If you use it, you will be asked to respond to questions about areas of the server hardware. Press and hold Ctrl and then press C to stop the test. 2. Run the test continuously Select this option to continuously test devices. Tests requiring a response are bypassed. Press and hold Ctrl and then press C to stop the test. 3. Log or display the errors Select this option to start an error log, stop a log in process, or display an existing log.
The common configuration tasks that will be described here are as follows: 1. 2. 3. 4. 5. 6. 7. Verify the configuration Low-level format of the disks Defining a hot-spare drive Creating a disk array Defining logical drives Look at the drives information Backup/restore the configuration After booting with the RAID Controller program diskette, if more than one RAID adapter is installed, it will prompt you to select which adapter you want to work with (see Figure 54).
3.5.1 Drive Information During this first step, we will verify that all the installed units are recognized and available for future use. Select Drive Information on the main menu. The following screen appears: IBM RAID Controller Configuration Ver 2.12 Adapter in Slot 1 Drive Information Ch 1 Bay Array Drive ID Drive Capacity Soft Error Hard Error Misc Error IBM DFHSS2W 2150MB 0 0 0 1717 Ch 2 Bay Array 1 1 2 2 3 RDY 3 4 RDY 4 5 RDY 5 6 RDY 6 7 CDR 7 Figure 56.
Note The RAID Utility shows device type and/or status for each device which it recognizes. The devices may take on several states which you may encounter when running the Utility. Here is a list of indicators used along with a description of each: • CDR = A CD-ROM device. DDD = A DASD device which is defunct. FMT = A DASD which is being formatted. HSP = A DASD which has been defined as hot-spare Drive. OFL = A DASD which is being used to rebuild a defunct drive.
4. Press Enter to format the selected drives. Notes All the desired devices may be selected and formatted together to reduce the time necessary for formatting. The operation can be time consuming. It takes approximately 20 minutes to format six 2GB disks attached to the same adapter. IBM RAID Controller Configuration Ver 2.12 Adapter in Slot 1 Advanced Functions 1. 2. 3. 4. 5. 6. 7. Help Backup config. to diskette Restore config.
Stripe Unit size: This parameter should be chosen such that the stripe unit size is close to the size of the system I/O requests. The default is set to 8KB. Note: Once data is stored in the logical drive, the stripe unit cannot be changed without destroying data in the logical drives. Rebuild Priority: This parameter sets the priority of the execution order of the rebuild I/O requests with respect to the system I/O requests. The rebuild priority can be changed without affecting data in the logical drive.
IBM RAID Controller Configuration Ver 2.12 Adapter in Slot 1 Create/Delete Array 1. 2. 3. 4. 5. 6. 7. Help Define Delete Create Define Format Exit hot-spare drive disk array disk array Logical drive drive Ch 1 Bay Array Ch 2 Bay Array 1 1 2 2 3 RDY 3 4 RDY 4 5 RDY 5 6 RDY 6 7 7 Figure 60. RAID Configuration Program - Create/Delete A r r a y M e n u 1. Select Define hot-spare drive. The cursor becomes active in the Bay/Array selection list. 2.
3.5.4 Creating a Disk Array 1. Select Create/Delete Array from the Main Menu. 2. Select Create Disk Array from the Create/Delete Array menu and press Enter. 3. Using the Enter key, select each drive you want included in the array you are now defining. The devices will be highlighted as they are selected and the status changes from RDY to ONL (online). Also the array ID, (A for the first one, then B and so on) appears behind the drives that make up the array. 4. Press Esc to validate.
3.5.5 Defining Logical Drives 1. Select Define logical drive from the Create/Delete Array menu. The following screen appears: IBM RAID Controller Configuration Ver 2.12 Adapter in Slot 1 Create/Delete Array 1. 2. 3. 4. 5. 6. 7.
Notes: a. If only one hard disk has been assigned to the array, RAID level 0 will be automatically assigned and the pop-up menu does not appear. b. If only two hard disks are assigned to the array, RAID-5 is not selectable, since at least three hard disk drives in an array are necessary to assign RAID level 5 to one of the logical drives. c. Define any RAID 5 logical drives first. This is because the first logical drive seen will be the first RAID 5 drive created and will be assigned drive letter c:.
IBM RAID Controller Configuration Ver 2.12 Adapter in Slot 1 Create/Delete Array 1. 2. 3. 4. 5. 6. 7. Help Define Delete Create Define Format Exit hot-spare drive disk array disk array Logical drive drive Array Arrays Log Size RAID Date ID Size (MB) Drv (MB) Level Created A 6450 A0 400 RAID-5 08/24/95 Ch 1 Bay Array Ch 2 Bay Array 1 1 2 2 3 HSP 3 4 ONL A 4 5 ONL A 5 6 ONL A 6 7 7 Figure 66. RAID Configuration Program - Size Definition 7.
3.5.6 Setting the Write Policy Now that the logical drives have been created, you may wish to change the write policy for these drives. If you want to change the write policy: 1. 2. 3. 4. Select Advanced functions from the main menu. Select Change write policy. Use the up and down arrow keys to select the logical drive. Press Enter to toggle the write policy.
2. 3. 4. 5. 6. Select Backup config. to diskette. Press Enter. Enter the filename you want for backup (config is the default). Insert a diskette to hold the backup file. Press Enter. To restore the configuration: 1. 2. 3. 4. 5. 6. Select Advanced functions from the Main Menu. Select Restore config. from diskette. Press Enter. Enter the filename you used for backup. Insert the diskette used for backup. Press Enter. A screen like the one in Figure 68 will appear.
114 NetWare Integration Guide
Chapter 4. Novell NetWare Installation In this chapter, we examine the different steps required to install Novell NetWare. Novell NetWare can be installed in the following three ways: • • • With the ServerGuide CD-ROM With the original product diskettes With the original product CD-ROM We will focus on the ServerGuide process. 4.1 ServerGuide Overview ServerGuide is a CD-ROM library shipped with every IBM PC Server. It contains software products, device drivers, utility programs, and diskette images.
After the POST tests run, ServerGuide boots, and the ServerGuide language selection screen appears (see Figure 69 on page 116). Figure 69. ServerGuide Language Select the language that you want to use during the software installation process. There are three options: • • • Espanol Francais US English For this installation process, we selected US English. The Main Menu appears See Figure 70 on page 117.
Figure 70. ServerGuide Main M e n u This menu contains seven options: Start Here: This option contains information to help you become familiar with ServerGuide features and the contents of the CDs. Software Installation: Select this option to install any of the software programs included with ServerGuide. NetFinity Overview: This allows you to learn more about NetFinity and its capabilities.
The performance tuning programs can tune your server automatically based on this input.
Figure 71. Installing NetWare The installing NetWare screen appears. This screen allows you to select the NetWare version to install. You also can specify whether you want to install NetFinity Services for NetWare on the server. Note For NetWare 4.1, ServerGuide provides the ability for you to transfer your existing license during the software installation process. If you transfer your NetWare license, you do not need to purchase a software activation key. 5. Select Install NetWare 4.1. 6.
Figure 72. Configuring NetWare A screen like the one in Figure 72 will appear. This screen confirms your choice of country and keyboard and asks you to confirm the LAN adapter and Disk Controller that ServerGuide detected in the server. 7. Accept the default or modify the values if you want to use a different configuration. If you selected to install NetFinity Services, the Configuring IBM NetFinity screen appears (see Figure 73 on page 121).
Figure 73. Configuring I B M NetFinity 8. Specify the following information: • • • Network Driver Type (Protocol) System Name System Keywords 9. Select OK. Note You can also use the NF config command from the server console to configure NetFinity after the initial installation. Chapter 4.
Figure 74. Partitioning the Hard Disk A screen like the one in Figure 74 appears. ServerGuide defaults to create the following partitions: • • • DOS Startup Drive NetWare Free Space 10. Select OK if you want to accept the values or change them.
Figure 75. Reviewing Configuration At this point, you will see a screen like the one in Figure 75. You can review or change the selected options you have just entered. 11. Select OK after you have verified any parameters you wish to recheck. At this point, the server is rebooted and the hard disk is partitioned by ServerGuide. Chapter 4.
Figure 76. Unlocking Programs 12. When the server comes back up, you will see a screen like the one in Figure 76. Enter the activation keys for the NetWare version selected as shown in Figure 71 on page 119. 13. Select Unlock. 14. You are prompted to insert the NetWare CD and remove the license diskette. ServerGuide proceeds with the installation. Attention While ServerGuide is installing software, be sure not to touch any keys on the keyboard unless prompted by the install program.
19. Type SERVER from the NWSERVER directory to restart NetWare. 20. Install NetWare Directory Services. a. Type LOAD INSTALL and press Enter to start the installation utility. b. Select Directory Options(Install NetWare Directory Services) from the main menu and press Enter. c. Select Install Directory Services onto this server and then press Enter. A screen like the one in Figure 77 will appear. Figure 77. Installing NetWare Directory Services (NDS) d.
A screen like the one in Figure 79 on page 126 will appear. This is where the context for the server will be defined. Figure 79. Assigning a Context for the Server h. Specify the server context and type an administrator password. i. Retype the administrator password. j. Select Yes when the system asks you to save the directory information. A screen like the one in Figure 80 will appear. All the information that you have previously entered for NetWare Directory Services is shown in this screen.
21. Type DOWN at the colon prompt. 22. Type EXIT at the colon prompt to return to DOS and finish the installation. 23. Reboot the server and verify that the server comes up properly. The installation is complete. You are now ready to log on as the administrator and add users and applications. 4.4 Installing NetWare 3.12 with Diskettes In this section, we detail the procedures necessary to install NetWare V3.12 via the original product diskettes. 4.4.
This is the primary network operating system file that identifies the server as a NetWare 3.12 server. During installation it is copied to a directory on the DOS partition. 3. Disk Drivers These are specialized NLMs (NetWare Loadable Modules) that work with the disk controller and act as the interface to the disk subsystem to provide the server′s disk operating system. Disk drivers are loaded from the directory where NetWare was installed after SERVER.EXE is executed. Disk driver files have a .
Figure 81. NetWare Installation 6. Select Install new NetWare 3.12 and then press Enter. 7. Select Retain Current Disk Partition and then press Enter. 8. Enter a server name and the press Enter. 9. Enter an IPX internal network number or accept the default and then press Enter. Note An IPX internal network number is a number used to identify the server from any other server on the network. The IPX internal network number must be different than the network number used for the LAN adapter card. 10.
When the system asks whether the DOS AUTOEXEC.BAT should load the SERVER.EXE, select Yes and press Enter. At this point, SERVER.EXE is automatically invoked and the system console screen will appear. 18. Load the disk driver. Enter the appropriate disk driver at the colon prompt. For example, for an IBM PC server 320 with a RAID controller, you must use the IBMRAID.DSK driver. Type LOAD C:SERVER.312IBMRAID. 19. Type LOAD INSTALL.NLM and press Enter. You will see a screen like the one in Figure 82.
22. Select Create NetWare Partition and press Enter. You will see a screen like the one in Figure 84 on page 131. 23. Press Esc. This will accept the default values, namely the partition size, which is the remaining free space on the drive. Figure 84. Partition Information 24. Select Yes to create the partition and then press Esc twice to return to the Installation Options menu. 25. Select Volume Options from the Installation Options menu. 26. Press the Insert key to create a volume.
30. Place the cursor on the status field and press Enter. A screen like the one in Figure 86 on page 132 will appear. Figure 86. Volume Status 31. Select Mount Volume and then press Enter. 32. Press Esc to return to the Installation Options menu. 33. Select System Options. 34. Select Copy System and Public Files and press Enter. A screen like the one in Figure 87 will appear. Figure 87. Copy System and Public Files The system will prompt you to insert some diskettes.
For example if you are using an IBM 16/4 ISA Adapter you would type LOAD TOKEN, and then press Enter. 37. Press Enter to accept the default value for the I/O port address, or change the address if your LAN adapter needs a specific value. 38. When the system prompts you for the interrupt setting, press Enter to accept the default value, or change the value to the correct interrupt setting for your LAN adapter. 39. You now must bind the IPX protocol to your LAN adapter.
Figure 89. STARTUP.NCF File 45. Press Esc and select YES to save the STARTUP.NCF file. 46. Press Esc to return to the System Options menu. 47. Select Create AUTOEXEC.NCF File. A screen like the one in Figure 90 will appear. All the console commands you have previously entered have been placed in the AUTOEXEC.NCF file. Figure 90. AUTOEXEC.NCF File 48. Press Esc and select Yes to save the AUTOEXEC.NCF file. 49. Press Esc twice to exit the installation utility. 50. Type DOWN at the colon prompt. 51.
4.5 Installing NetWare 4.1 with the Original CD-ROM In this section, we detail the procedures necessary to install NetWare 4.1 using the original product CD-ROM. 4.5.1 Hardware Requirements The following hardware is required to install NetWare 4.1: • • • • • One file server with an Intel 386 processor or higher A minimum of 8 MB of RAM A minimum of 20 MB in a DOS disk partition At least one network adapter card A CD-ROM drive 4.5.
Figure 91. Installation M e n u 7. Select NetWare Server Installation and press Enter. 8. Select NetWare 4.1 and press Enter. 9. Select the kind of installation that you want perform. There are two options, as follows: • Simple Installation If you select this option, the installation program sets the default values. You must specify only the server name. The installation then proceeds to copy the boot files to the DOS partition.
18. Specify the path where the AUTOEXEC.BAT file is located or press Enter to accept the default. The default is C:AUTOEXEC.BAT. A screen like the one in Figure 92 will appear. Figure 92. Disk Driver Options 19. Select a disk driver. If the driver that you need is not in the list, insert the disk driver diskette appropriate for your adapter and press the Insert key. A screen like the one in Figure 93 will appear. Figure 93. Network Driver Options 20. Select a network driver.
Attention This number must be different from the IPX internal network number. 23. Select Manually when the system asks you to choose the method for setting up the NetWare partition(s). 24. Select Create, delete and modify disk partitions and press Enter. A screen like the one in Figure 94 will appear. Figure 94. Create Partition 25. Select Create NetWare disk partition. A screen like the one in Figure 95 will appear. Figure 95. Disk Partition Information 26.
29. Press Enter to continue when the information for available disk space appears. A screen like the one in Figure 96 will appear. Figure 96. New Volume Information 30. Press F10 to accept the defaults for volume SYS:. 31. Select YES when the system asks whether you want to save the volume changes. 32. The system asks for a license diskette. Insert the license diskette in drive A: and press Enter. A screen like the one in Figure 97 will appear. Figure 97. Optional NetWare Files 33.
Figure 98. Install NetWare Directory Services(NDS) 35. Select Yes, this is the first NetWare 4 server if this is the only NetWare 4.X server on your network. Otherwise, if you have other NetWare 4.X servers, check your network connections to make sure that you can communicate with them over the LAN connection where you are installing this server. Figure 99. Assigning a Name to the Directory Tree 36. Enter a name for this directory tree and press Enter. 37. Select a time zone and press Enter. 38.
Figure 100. Context for the Server 39. Specify the server context and type an administrator password. 40. Retype the administrator password. 41. Select Yes when the system asks whether you want to save the directory information. Figure 101. Server Context Information Attention Be sure to remember this information. You will need the context of the server to log on as well as to perform many administrator and end-user tasks. Please also remember that the context is case-sensitive . 42. Press Enter.
Figure 102. Editing STARTUP.NCF File 43. Press F10 and select Yes to save the STARTUP.NCF file. A screen like the one in Figure 103 will appear. Many of the configuration parameters you have previously entered have been placed in the AUTOEXEC.NCF file for you. Figure 103. Editing AUTOEXEC.NCF File 44. Press F10 and select Yes to save the AUTOEXEC.BAT file. The files are transferred from the CD to hard disk.
Figure 104. File Copy Status 45. When all files have been transferred, a screen like the one in Figure 105 will appear. Figure 105. Other Installation Options 46. Select Continue Installation and press Enter. 47. Press Enter to exit to the system console screen and finish the installation. 48. Type DOWN at the colon prompt. 49. Type EXIT at the colon prompt to return to DOS. 50. Reboot the server and verify that it comes up properly. The installation is complete.
4.6 NetFinity Services for NetWare NetFinity Services for NetWare allows you to monitor and manage NetWare servers remotely. With the NetFinity programs running on the server, the administrator can anticipate and correct many problems before they become serious enough to affect the server. NetFinity Services for NetWare will also enhance other hardware systems management tasks, including hardware inventory and resource allocation.
6. The installation program will prompt you to insert NetFinity Services for NetWare, Diskette #2. 7. Configure the Network Driver. After the program files have been copied onto your NetWare server, the following screen appears. Please note that in this example, the name of the NetWare server is PCSERVER.
11. Set System Keywords. System keywords can help the NetFinity Manager system organize the systems on the network more effectively. Each system can have up to eight keywords. a. Type 4 and then press Enter. A numbered list of keywords and the following message appears: Choose keyword number to edit-> b. Type the number of the system keyword you want to use and press Enter. The following message appears: Type new keyword (1-16 characters) or type DELETE to remove-> c.
The following lines need to be added to AUTOEXEC.NCF: SEARCH ADD SYS:NETFIN\ LOAD NETFBASE If you choose to update AUTOEXEC.NCF, AUTOEXEC.NCF will be backed up to AUTOEXEC.RPS. Otherwise, additions will be saved to the file AUTOEXEC.NEW in the path SYS:NETFIN\. Update AUTOEXEC.NCF(Enter Y or N)? SYS:NETFIN\ is the default target path or the new path you entered during the installation procedure. 17. Type Y if you want NetFinity Services for NetWare to start automatically when the server is started.
5. Enter the source drive and directory name where the NetFinity program files are located or accept A: as the default. 6. Enter the drive and directory name where the NetFinity program files will be copied. The default is C:NETFIN. This should be the drive letter that you mapped to earlier. 7. Select OK. If the path includes a directory that does not exist, the installation program will tell you that this directory will be created. Select OK to continue the installation.
9. Insert NetFinity Services for NetWare Diskette #2 and select OK. After the program files have been copied onto your NetWare server, a window like the one in Figure 110 will appear. Figure 110. Network Driver Configuration 10. Enter a name for the server in the System Name field. This name identifies the server on the network. 11. Select Novell IPX from the Network Drivers field.
NetFinity will generate an alert whenever one of your NetFinity services is started by a remote user that is accessing the server. The alert includes the name of the service that was run and information about the user that started the service. To activate this option: a. Select Options.... b. Select Service Execution Alerts. c. Select OK. 16. Select Save to save the configuration. A screen like the one in Figure 111 will appear. Figure 111. Configuration Update 17.
After you save these changes, the NetFinity base program will start automatically when the server is started. • If you do not want the NetFinity base programs to start automatically, you can start them manually. To start NetFinity manually: 1. Turn on the server. 2. When the command prompt appears type SEARCH ADD SYS:NETFIN\ and then press Enter. 3. Type LOAD NETFBASE, and then press Enter. SYS:NETFIN is the default target path or the path for the program files that you specified during installation. 4.
6. Type LOAD RAIDADM at the NetWare server console prompt and press Enter to start the RAID Administration for NetWare Utility. Note Loading RAIDADM.NLM will automatically load RAIDASPI.NLM. A screen like the one in Figure 113 will appear. Figure 113. Raid Administration for NetWare - Main M e n u 4.7.1.2 Copying NLMs to the NetWare Server To install RAID Administration for NetWare: 1. Turn on the server. 2. Insert the RAID Adapter Options diskette into the diskette drive. 3.
configured. It is also assumed that the RAID administration in the server and the NetFinity Manager in a workstation are running. 4.8.1 Simulating with a Hot Spare Drive 1. Start the RAID Administration for NetWare Utility. A screen like the one in Figure 114 will appear. Figure 114.
Figure 115. Verifying Array Configuration The array configuration can also be verified from a workstation with NetFinity Manager installed using RAID manager (see Figure 116). Figure 116. Using RAID Manager to View Array Configuration The hot spare drive is enclosed in a box. 3. Simulate a disk failure by unplugging it with the machine powered on. In this example, the disk in bay 5 was unplugged.
Figure 117. Detecting the Disk Failure If NetFinity has been configured properly, it will generate an alert. Figure 118 shows the NetFinity Alert Manager Log where such an alert has been generated. Figure 118. Disk Failure - NetFinity Alert In this example, two alerts were received. The first alert refers to the logical drive which was defined using the failed disk. This has been logged as a critical alert. The second alert relates to the physical drive which has failed.
Figure 119. Disk Failure - NetFinity RAID Service 4. Select the View Last Event option from the Administration Options menu. A screen like the one in Figure 120 will appear. Figure 120. View Last Event Message 5. At the end of the rebuild process, the RAID Administration for NetWare Utility sends a message. This message is shown in Figure 121 on page 157.
Figure 121. RAID Administration - Recovery Message NetFinity also sends some alerts. Figure 122 shows the NetFinity Alert Manager Log for these alerts. Figure 122. NetFinity Recovery Alert Again, two alerts are received. The first refers to the logical drive which is now online and the second to the physical disk which is also now online. 6. Select Show Drive Information to review the changes in the array configuration. A screen like the one in Figure 123 on page 158 will appear. Chapter 4.
Figure 123. Changes in Array Configuration The changes in the array are as follows: • • The original hot spare disk in bay 3 changed to status ONL (online). The faulty disk in bay 5 changed to status DDD (defunct). We will now make the simulated failed disk the new hot spare disk. 7. Plug the unplugged disk back in. 8. Select Replace a Defunct Drive from the Administration Options menu. 9. Select DDD and press Enter. A screen like the one in Figure 124 will appear. Figure 124.
Figure 125. RAID Administration - Verifying the Replacement of a Defunct Drive The new array configuration is as follows: • • The disk status in bay 3 remains as ONL. The disk status in bay 5 changed to HSP. 11. NetFinity sends another alert. The NetFinity Alert Manager looks like Figure 126. Figure 126. NetFinity New Hot Spare Drive Alert This alert indicates that a new hot spare drive is available. 12. Verify the process using the NetFinity RAID service.
Figure 127. NetFinity RAID Service - New Hot Spare You can see that a new disk is enclosed in a box. It is the new hot spare drive in the array configuration. This simulation is complete. 4.8.2 Simulating without a Hot Spare Drive To do the same test without a hot spare drive: 1. Start the RAID Administration for NetWare Utility. 2. Select Show Drive Information to review the array configuration. A screen like the one in Figure 128 will appear. Figure 128.
Figure 129. NetFinity RAID Service - Verifying Configuration 3. Simulate a disk failure by unplugging it with the machine powered on. In this example the disk in bay 5 was unplugged. If you do this, you will see an asterisk next to bay 5 and a flashing asterisk in the View Last Event option. This is depicted in Figure 130. Figure 130. Detecting the Disk Failure 4. NetFinity will send an alert. The Alert Manager screen will look like Figure 131 on page 162. Chapter 4.
Figure 131. NetFinity Alert Log In this example, two alerts were received. The first alert refers to the logical drive which was defined using the failed disk. This has been logged as a critical alert. The second alert relates to the physical drive which has failed. It shows up as a dead device on the alert. 5. The failure also can be checked using the NetFinity RAID service (see Figure 132). Figure 132.
6. Select View Last Event from the RAID Administration Utility to see the message. A screen like the one in Figure 133 will appear. Figure 133. Last Event Message Since there is no hot spare drive defined in this example, the disk can not be automatically replaced. 7. Select Show Drive Information to review the disks′ status in the array configuration. A screen like the one in Figure 134 will appear. Figure 134.
Figure 135. RAID Administration - Replace a Defunct Drive After the drive is started, the RAID Administration for NetWare Utility attempts to rebuild the new disk. The progress of the rebuild is shown in Figure 136. Figure 136. RAID Administration - Rebuild Progress When the process is finished, a screen like the one in Figure 137 on page 165 will appear.
Figure 137. RAID Administration - Verifying the Rebuild Status 11. Press any key to complete the process. 12. NetFinity sends two alerts. The NetFinity Manager looks like Figure 138. Figure 138. NetFinity Alert - New Disk Online These alerts indicate that the new disk is online. 13. The simulation is complete. Chapter 4.
166 NetWare Integration Guide
Chapter 5. Performance Tuning To get the optimal performance from your NetWare server, you need to consider the performance of both the hardware and the software. In this chapter, we examine the general performance characteristics of file server hardware. We also discuss several performance monitoring tools. We then discuss the NetWare operating system and its relevant performance parameters. 5.
LAN adapters and fast disk subsystems. In contrast, database servers typically need fast processors (or multiple processors) and fast disk subsystems. Both file and database servers require large amounts of memory for operating system caching. Tuning system performance involves determining where the current bottleneck is and then alleviating this bottleneck.
Systematic measurements of server performance employing adequate resolution typically produce a graph shaped like the one shown in Figure 140 on page 169. The characteristics that shape this graph are important for understanding potential bottlenecks in a file server. Figure 140. File Server Performance - General Characteristics The horizontal axis shows the number of simultaneous active users. The vertical axis indicates server throughput, or number of transactions per second.
which represents the maximum server transactions per second or throughput rate. After the peak throughput is reached, the curve begins to slope downward. As the number of users is increased, the caching engine of the operating system begins to break down. The reduction in the disk cache hit rate is caused by the increasing amount of data that each additional user requests the server to access.
Figure 141. Differences in LAN Adapters Upgrading the disk subsystem will tend to flatten out the top of the curve as it will provide a higher sustainable data transfer rate. In most cases, the disk subsystem becomes the bottleneck when a large number of users becomes active. Since most disk subsystems are significantly slower than a cache-hit operation, the throughput curve begins to decline.
Figure 142. Differences in Disk Subsystems Improving performance of the disk subsystem transactions per second rate shown in Figure be to improve the disk cache hit rate. This is from the cache quicker, so that the amount of new data is increased. will usually prolong the maximum 142. The effect of a faster disk can because write-data can be flushed memory available for caching of 5.2 Performance Analysis Tools Using performance analysis tools is an effective method of understanding server performance.
• • • • • • • • Flexible, user-definable interface Reliable, accurate information Continuous reports of top talkers, ring map (token-ring only), error conditions, statistics, and selected network data Broad data import and export support Extensive protocol decode coverage 10-millisecond time stamp (token-ring) or 32-millisecond time stamp (Ethernet) Optional 840-nanosecond, high-resolution time stamp Fully windowed, graphical, multitasking user interface DatagLANce supports all or portions of the follow
Figure 143. MONITOR Utility The monitor utility allows you to check many important aspects of file server performance. It allows you check resource allocations and utilization of these resources. For example, you can: • List system modules loaded • View memory statistics • View tracked resources • Check status of LAN drivers and statistics • List active connections • Clear a connection • List open files • List record locks 5.2.2.
4. You are the given a choice of parameters to either view or set. In the following sections, we look at many of these parameters and make recommendations for setting them. Note Many of the set parameters can be adjusted from the server console while the server is up and running. However, several parameters must be set in either the AUTOEXEC.NCF or STARTUP.NCF files. The information displayed using the set command will indicate which parameters must be set in this way. 5.2.2.3 SERVMAN.
5.3.1 Disk Subsystem The file server disk subsystem contains the files which are accessed by the LAN workstations. The efficiency at which access is performed is directly related to the file server performance. The following section describes some of the findings of the IBM PC Server performance laboratory on the major factors that affect hard disk subsystem performance. 5.3.1.1 Block Size and Cache Buffer Size (NetWare 3.12) NetWare V3.
5.3.1.2 Block Size (NetWare 4.1) In all versions of NetWare prior to NetWare 3.X, the block allocation unit was fixed at 4KB. In NetWare 3.X, larger allocation units are possible, but they result in a lot of unused disk space at the end of files. For example, if the last part of a file took up 1KB of a 16KB block, the remaining 15KB was wasted. Sub-allocation is implemented in NetWare 4.1 to overcome the problem of wasted disk space due to under-allocated disk blocks.
NetWare 3.12 and 4.1: Default = 5 minutes 29.6 seconds Increasing the Turbo FAT re-use wait time helps ensure that the index structures are not flushed if the file is reused quickly. For example, a large database file might be accessed frequently throughout the day, with many file load and save operations. By increasing this parameter there is an increased likelihood of servicing the file request from a Turbo FAT index, thereby improving performance. 5.3.1.
5.3.1.5 File Caching File caching has the most affect on overall file server performance. Because accessing data from cache is much faster than accessing data from disk, the more data than can be held in cache, the better the server performance. Hence, the number of file cache buffers available can greatly impact server performance.
size is equal to 4096, the amount of memory used in megabytes can be calculated as follows: system memory used = (original cache buffers - total cache buffers) x cache buffer size (3000 - 2500) x 4096= 2,048,000 bytes (2MB) From this calculation, you can determine if the file server requires more memory, particularly when adding NLMs or changing the server configuration with set parameters.
5.3.1.7 Dirty Disk Cache Delay Time The dirty cache delay time controls the time taken to hold the write requests in the cache when the cache is not full. If your system has unused cache memory, and your typical server workload contains a high number of sequential write operations, then you may improve performance by increasing this value. The dirty cache delay time value can be set in the AUTOEXEC.NCF file using the following format: SET DIRTY DISK CACHE DELAY TIME=VALUE NetWare 3.12 and 4.
Attention Set this parameter to ON only if you are absolutely sure your backup strategy enables you to restore a file which has been deleted. 5.3.1.11 Enable Disk Read After Write Verify In NetWare, this read-after-write verify capability complements the hot fix function. This allows the system to prevent any file from being written to a bad disk block by attempting to read the data after it has been written to disk. NetWare′s read-after-write capability and hot fix function are implemented in software.
5.3.2.2 Packet Size Different network topologies will use different packet sizes. For example, a token-ring LAN adapter set to 16 Mbps can use packets of up to 4202 bytes. If the packet size is left at the network default value, which is 1514 bytes, this could unnecessarily slow down the LAN adapter performance. The reason for this is that it takes just as many instructions to process a small frame as it does a larger frame.
monitored using MONITOR.NLM. Use this value rather than the number of defined LAN users. For example: 1. For 40 LAN users with 2 LAN adapters in the file server: 40 (users) + ((10 x 2) LAN adapters) = 60 buffers minimum; set the maximum to 160. 2. For 100 LAN users with 4 LAN adapters in the file server: 100 (users) + ((10 x 4) LAN adapters) = 140 buffers minimum; set the maximum to 240.
Recommendation • • For networks without wide area (WAN) segments, set the maximum packet receive buffers to 300. For networks that use WANs, set the maximum packet receive buffers to 1000. This should be adequate to handle the additional buffering needed for WAN links. 5.3.2.4 New Packet Receive Buffer Wait Time The new packet receive buffer wait time is the wait time taken before spawning a new packet receive buffer. This parameter must be set in the AUTOEXEC.NCF file to change the value.
The size of the cache buffer pool is dynamic and determined by the amount of memory left over after the other pools have been allocated. As more buffers are allocated for NLMs and other system resources, this reduces the size of the cache buffers pool. Both the movable and non-movable pools return memory to the cache buffer pool when it is no longer needed. Checking the Allocation of Memory to Each Memory Pool: You can use the MONITOR.NLM utility to view the allocation of system memory by pool.
5.3.4 Memory Requirements The following sections present some guidelines for calulating total server memory requirements for both the NetWare V3.12 and V4.1 environments. 5.3.4.1 Calculating Server Memory Requirements (V3.12) To calculate the total system memory required, use the following guidelines: 1. Allocate a m i n i m u m of 4MB of RAM for loading the operating system, disk drivers, LAN drivers and the INSTALL.NLM. 2.
processing, this is an indication that the LAN adapter could be a bottleneck in the file server. In this case, the LAN adapter could be upgraded or another one added to balance the LAN load and use the system processor more efficiently. The use of bus mastering LAN adapters and disk controllers also helps to spread the load on the file server more evenly and thereby uses the system processor in a more efficient manner. To use the MONITOR.
Appendix A. EISA Configuration File Board Information IBM Dual Pentium PCI-EISA System Board System Manufacturer ................. Micronics Computers, Inc. ID ........................... MIC0054 Category ..................... SYS Board slot type .............. Embedded Readable ID .................. Yes SYSTEM BOARD MEMORY System Base Memory ........................... 640 KB Base Memory Total System Memory. ......................... 16 MB Total Memory Memory Gap between 15-16Megs. ................
System - IBM Dual Pentium PCI-EISA System Board Jumper Name: W1 - Level 1 Cache. Default factory settings: OFF Change settings to: OFF +-------+ |o o| +-------+ 1 2 This jumper sets the level 1 (CPU¢s internal) cache to write-back or write-through mode. Install a jumper for write-through mode. Do not jumper for write-back mode. Default is the faster write-back mode. ======================================================================= Jumper Name: W5 - Level 2 Cache.
Jumper Name: W10 - Level 2 Cache. Default factory settings: OFF ON Change settings to: OFF ON +-----------+ | o o---o | +-----------+ 1 2 3 This jumper along with W5 selects the level 2 cache size. Jumper pins 1-2 for 256K cache size. Jumper pins 2-3 for 512K cache size. Default is pins 2-3; 512K cache. ======================================================================= Jumper Name: W20 - Monitor Type.
Jumper Name: W28 - PCI IDE IRQ. Default factory settings: ON OFF Change settings to: ON OFF +-----------+ | o---o o | +-----------+ 1 2 3 Jumper the pins to set the PCI IDE controller as the PRIMARY IDE controller at IRQ 14. Remove the jumper to disable the PCI IDE. The PCI IDE can not be set up as a SECONDARY IDE controller.
Board Information IBM Auto 16/4 Token-Ring ISA Adapter Slot 3 Manufacturer ................. PNP ID ........................... IBM0001 Category ..................... OTH Board slot type .............. Other Readable ID .................. No Skirt ........................ No IBM Auto 16/4 Token-Ring ISA Adapter ........... Enabled Appendix A.
Board Information PCI SCSI Controller Embedded Manufacturer ................. PCI ID ........................... 90047178 Category ..................... MSD Board slot type .............. PCI Readable ID .................. No Skirt ........................ No PCI Function 1 .................................
Used Resources Resource Slot IRQ 0.................. System IRQ 1.................. System IRQ 3.................. System IRQ 4.................. System IRQ 6.................. System IRQ 7.................. System IRQ 8.................. System IRQ 2(9)............... Slot 3 IRQ 11.................. Embedded IRQ 12.................. System IRQ 13.................. System IRQ 15.................. System Function Reserved System Resources. Reserved System Resources.
Available Resources IRQs 5 10 14 196 NetWare Integration Guide DMAs 0 1 3 5 6 7 ISA I/O Ports 100h - 2F1h 2F3h - 400h Memory Amount 64K 64K 8K 64K 64K 64K 1M Address 0A0000h 0B0000h 0CE000h 0D0000h 0E0000h 0F0000h 15M
System Specifications Slot Name Slot Slot Slot Slot Slot Slot 1 2 3 4 5 6 Slot Type Board ID Accept Max BusSlot Skirted Length master Tag(s) EISA EISA EISA EISA EISA EISA (Empty) (Empty) IBM0001 (Empty) (Empty) (Empty) Yes Yes Yes Yes Yes Yes 341mm 341mm 341mm 341mm 341mm 341mm Yes Yes Yes Yes Yes Yes Nonvolatile memory ................. 8K Appendix A.
198 NetWare Integration Guide
Appendix B. Hardware Compatibility, Device Driver, and Software Patch Information One of the challenges that LAN administrators face is ensuring that the adapters they want to use are supported and then finding the latest level of device drivers for these adapters. Another problem they face is trying to find information about known software bugs and their corresponding fixes. This appendix is included to help readers solve these problems. B.
Figure 145. Sample Compatibility Report Showing Ethernet LAN Adapters In addition, it contains reports by NOS and by machine and model number which shows the testing done to certify the hardware against the operating system. These reports show detailed information on hardware configurations, adapters, device drivers, and code levels used in the testing. B.
For OEM adapters, many manufactures have web and FTP sites which work very similar to the process outlined above. There is a one very useful web site which maintains an index to many OEM web sites which have device drivers for many popular boards. The site is called the LAN Drivers Page and the URL for this site is: • http://sunsite.unc.edu/ ∼ towfiq/lan-drivers.html B.
202 NetWare Integration Guide
Appendix C. Configuring DOS CD-ROM Support This appendix is included to aid in configuring CD-ROM support in the DOS environment. C.1 Installing CD-ROM Support for PCI Adapters. To install CD-ROM support for an IBM PC Server with a PCI SCSI adapter: 1. Copy the following files from the ServerGuide license diskette to the hard disk (C:SERVER directory): • • • • IBMPRAID.SYS IBMASPI.SYS DAFCDA.SYS MSCDEX.EXE 2. Add the following statements to the CONFIG.SYS file: DEVICE=C:SERVERIBMPRAID.
• MSCDEX.EXE 2. Add the following statements to the CONFIG.SYS file: DEVICE=C:SERVERIBMRAID.SYS DEVICE=C:SERVERRDASPII.SYS DEVICE=C:SERVERIBMCDROM.SYS /Q DEVICE=C:SERVERRDCDROM.SYS DEVICE=C:SERVERRAMDRIVE.SYS 2800 512 128 /E 3. Add the following statement to the AUTOEXEC.
List of Abbreviations ALU Arithmetic-Logic Unit APA all points addressable ASCII American Standard Code for Information Interchange ASPI Advanced SCSI Programming Interface BIOS Basic Input/Output System CI Component Interface (as in Desktop Management Interface) CMIP Common Management Information Protocol CMOS Complementary Metal Oxide Semiconductor CPU Central Processing Unit DASD Direct Access Storage Device DIMM Dual In-Line Memory Module DMA Direct Memory Access DMI Desktop Man
206 NetWare Integration Guide
Index Special Characters C .ADF files 85 .CFG file 75 cable cover 35 cache buffer size 176 cache memory cache hit 4, 171 cache miss 4 coherency of 6 enabling/disabling 68 hit rate 168 L1 cache 4 L2 cache 4 L3 cache 5 lazy-write cache 4 MESI protocol 6 tags 6 write-back cache 4 write-through cache 4 caching, on disk subsystems 22, 179 calculating memory requirements 187 CD-ROM, Installing NetWare 4.
defunct drives 158 design considerations availability 22 cost 23 performance and capacity 22 Desktop Management Interface (DMI) 37 browser in NetFinity 44 communicating service 38 Component Interface (CI) 39 manageable products 38 management applications 38 Management Information Format (MIF) 38 Management Interface (MI) 39 MI commands get 39 list 39 set 39 destination address 172 detecting disk failures 155 diagnostics 97 diagnostics, running 85 Direct Access Storage Device (DASD) 16 average access time 21
high availability 22 hot spare drive 154 HP OpenView, interoperability with NetFinity I IBM LANStreamer MC32 32 IBM Quad PeerMaster Adapter 33 IDE See Integrated Drive Electronics (IDE) immediate file purging 181 Industry Standard Architecture (ISA) 12 INSTALL.BAT file 127 INSTALL.NLM 128 installing NetFinity Services 144 Installing NetWare 4.
P P5 1 P54C 1 packet receive buffers 183 packet size 183 parallel port, configuration of 70 parity 9 parity placement, in RAID arrays 106 passive client, NetFinity 43 password jumper 36 password on boot 72 PCI See Peripheral Component Interconnect (PCI) PeerMaster technology 33 Pentium 2 Peripheral Component Interconnect (PCI) 12, 15 permanent memory 186 Personal System/2 Micro Channel SCSI Adapter 19 Personal System/2 Micro Channel SCSI Adapter with Cache 19 POST error detect, NetFinity 44 POST errors, pro
security (continued) tamper-evident switches 34 unattended start mode 37 unattended start mode, MCA 94 user password, EISA 71 security manager, NetFinity 42 seek time 22 selectable drive startup 37 selecting a time zone 125 serial control service, NetFinity 42 serial port, configuration of 70 serial-port power-on 97 server components 167 SERVER.
T Tagged Command Queuing (TCQ) 18 tamper-evident switches 34 TCP/IP See Transmission Control Protocol/Internet Protocol (TCP/IP) TCQ See Tagged Command Queuing (TCQ) terminator, SCSI bus 79 testing the computer 97 throughput 169 time zone, NetWare 125 TOKEN.
ITSO Technical Bulletin Evaluation RED000 International Technical Support Organization IBM PC Server and Novell NetWare Integration Guide December 1995 Publication No. SG24-4576-00 Your feedback is very important to help us maintain the quality of ITSO Bulletins. Please fill out this questionnaire and return it using one of the following methods: • • • • Mail it to the address on the back (postage paid in U.S.
ITSO Technical Bulletin Evaluation SG24-4576-00 Fold and Tape RED000 Please do not staple IBML Fold and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE IBM International Technical Support Organization Department HZ8, Building 678 P.O.
IBML Printed in U.S.A.
Artwork Definitions id File ITSLOGO 4576SU Page References 1 i Figures id File ASYM CH1A Page References 5 1 5 SYMM CH1A 6 2 6 INTERL CH1A 7 3 7 DUALP CH1A 8 4 7 ECCMEM CH1A 10 5 9 ECCP CH1A 11 6 11 STRM20 CH1A 14 7 13 STRM40 CH1A 14 8 14 STRM80 CH1A 15 9 15 DISK2 CH1B 17 10 17 STRIP4 CH1B MIRROR CH1B DUPLEX CH1B STR1 CH1B RAID6 CH1B 24 11 25 12 25 13 26 14 26 15 26 STRIP1 CH1B 27 16 27, 27 STRIP3 CH1B 28 17 28 STRIP5 CH1B STRIP6 CH1B
71 27 71 CH313 CH3 74 28 74 CH314 CH3 74 29 74 CH315 CH3 75 30 74 CH316 CH3 CH317 CH3 75 31 76 32 76 CH318 CH3 77 33 76 CH308 CH3 78 34 78 CH309 CH3 78 35 78 CH310 CH3 80 36 79 CH311 CH3 81 37 81, 81 CH312 CH3 82 38 82 RDMAIN CH3 84 39 83, 84 BACKUP CH3 86 40 86 SCMENU CH3 87 41 86 VCMENU CH3 88 42 87 MEMAP CH3 90 43 89 VSCSI CH3 91 44 90 SETFEAT CH3 92 45 91 SETPAS CH3 93 46 92 SSSEQ CH3 96 47 96 POFEAT CH3 97 48 96, 97 MUMENU CH3 98 49 9
CH323 CH3 CH324 CH3 104 57 105 58 105 59 105 CH325 CH3 CH326 CH3 107 60 107 61 107 CH327 CH3 CH328 CH3 CH329 CH3 CH330 CH3 CH331 CH3 108 62 109 63 109 64 110 65 111 66 110 CH332 CH3 111 67 111 CH333 CH3 113 68 113 CH401 SGOVER 116 69 116 CH402 SGOVER 117 70 116 SVINET 4576CH4 119 71 124 SGCONF 4576CH4 120 72 120 SGCNETF 4576CH4 121 73 120 SVPARHD 4576CH4 122 74 122 SVREV 4576CH4 123 75 123 SVUNL 4576CH4 124 76 124 SGINST1 4576CH4 125 77 1
133 312STF 4576CH4 134 89 133 312AEX 4576CH4 134 90 134 41NW01 4576CH4 136 91 135 NW41DD 4576CH4 137 92 137 NW41ND 4576CH4 137 93 137 NW41CP1 4576CH4 138 94 138 NW41V 4576CH4 138 95 138 NW41VOL 4576CH4 139 96 139 NW41OF 4576CH4 139 97 139 NW41FS 4576CH4 140 98 139 NW41TN 4576CH4 NW41DN 4576CH4 140 99 141 100 140 NW41SI 4576CH4 NW41ES 4576CH4 141 101 142 102 141 NW41AF 4576CH4 142 103 142 NW41MC 4576CH4 143 104 142 NW41IO 4576CH4 143 105 143 NETFND NETF
155 WRAID07 RAIDADM 156 119 155 WRAID08 RAIDADM 156 120 156 WRAID09 RAIDADM 157 121 156 WRAID10 RAIDADM 157 122 157 WRAID11 RAIDADM 158 123 157 WRAID12 RAIDADM 158 124 158 WRAID13 RAIDADM 159 125 158 WRAID14 RAIDADM 159 126 159 WRAID15 RAIDADM 160 127 159 WRAID16 RAIDADM 160 128 160 WRAID17 RAIDADM 161 129 160 WRAID18 RAIDADM 161 130 161 WRAID19 RAIDADM 162 131 161 WRAID20 RAIDADM 162 132 162 WRAID21 RAIDADM 163 133 163 WRAID22 RAIDADM 163 134 163 WRAID23 RAI
Headings id File NOTICES 4576FM BIBL 4576PREF CH1 CH1A PROCESR CH1A TYPES CH1A MP CH1A ASYMUL CH1A SMP CH1A MEMORY CH1A SMPSH CH1A SMPDED CH1A INTERL CH1A DUAL CH1A ECC CH1A BUS CH1A ISA CH1A EISA CH1A MCA CH1A STREAM CH1A PCI CH1A DISKSS CH1B DISKIF CH1B SCSI CH1B SCSIADA CH1B ADAPSUM CH1B DISKS CH1B RAID CH1B LAN CH1C SECURE CH1D SECIO CH1D MANAGMT CH1E COMSL CH1E MIF CH1E MI CH1E CI CH1E MIB CH1E AGENT CH1E MANAGER CH1E TRAPS
SERVS CH1E MGR CH1E NARCH CH1E DMI CH1E INTEROP CH1E STRUC CH1E PROTOC CH1E PCHUTE CH1F FLEX CH1F CH2 CH2A FAMSPEC CH2A HWCONF CH3 SYSPRO CH3 STPART CH3 REFDISK CH3 MMENU CH3 BRSYS CH3 CONFIG CH3 SFEAT CH3 TEST CH3 MOREUT CH3 ADGPR CH3 DASDDEF CH3 NOSINST SGOVER NETSG STUNING HTUNING EISACFG DDINFO 40 1.9.2.4, Traps 41 1.9.3.1, NetFinity Services 43 1.9.3.2, NetFinity M a n a g e r 44 1.9.3.3, NetFinity Architecture 45 1.9.3.
Index Entries id File CPU CH1A ALU CH1A SMP CH1A DRAM SRAM RAM CACHE SIMM ECC ECCP EOS NVRAM ISA EISA MCA PCI BUSES I004 DASD ESDI IDE SCSI TCQ SCB DISKC RAID SEC Page References 1 (1) central processing unit (CPU) 1 (1) arithmetic logic unit (ALU) 3 (1) symmetric multiprocessing (SMP) 3 3 (1) dynamic random access memory (DRAM) 3 3 (1) static random access memory (SRAM) 3, 3 4 (1) Random Access Memory (RAM) 4, 4, 12 4 (1) cache memory 4, 4, 4, 4, 4, 4, 4, 5, 6
71, 71, 72, 92, 92, 94, 94 DMI CH1E MIF CH1E MI CH1E MIC SNMP TCPIP CH1E CH1E UPS CH1F NDS 39 (1) Desktop Management Interface (DMI) (2) Management Interface (MI) 39 39 (1) Desktop Management Interface (DMI) (2) MI commands 39, 39, 39 39 (1) Simple Network Management Protocol (SNMP) 39, 40, 40, 40, 40, 40 39 (1) Transmission Control Protocol/Internet Protocol (TCP/IP) 39 40 (1) Management Information Base (MIB) 41 (1) NetFinity 41, 41 41 (1) NetFinity (2) M a n a g e r 43 45 (1)
Processing Options Runtime values: Document fileid ........................................................................................... Document type ............................................................................................ Document style ........................................................................................... Profile ........................................................................................................... Service Level ........................
Imbed Trace Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page 0 0 1 i ii xv xv xvi xix xx 16 31 34 37 47 51 54 63 113 113 143 151 165 188 197 201 204 212 212 212 213 213 4576SU 4576VARS 4576FM 4576EDNO 4576ABST 4576SPEC 4576TMKS 4576PREF 4576ACKS CH1A CH1B CH1C CH1D CH1E SFTCH1 CH1F CH2A CH3 4576CH4 SGOVER NETF RAIDADM 4576CH5 AX1 AX3 AXCDSUP 4576ABRV 4576EVAL RCFADDR ITSCADDR FILE RCFADDR ITSCAD
