Netware 6 Installation C4882-4 Ch01.F 2/4/02 9:53 AM Page 4
Total Page:16
File Type:pdf, Size:1020Kb
c4882-4 Ch01.F 2/4/02 9:53 AM Page 3 CHAPTER 1 NetWare 6 Installation c4882-4 Ch01.F 2/4/02 9:53 AM Page 4 Instant Access ● Preparing to install There are four recommended tasks to prepare your network for NetWare 6: ᮣ Back up your data ᮣ Update eDirectory (if necessary) ᮣ Update eDirectory schema (if necessary) ᮣ Update Certificate Authority object in eDirectory Installing ᮣ To install a new server, run INSTALL from the root of the NetWare 6 Operating System CD-ROM. Upgrading ᮣ NetWare 4.x or 5.x — To upgrade to NetWare 6 choose one of these options: • Perform an Accelerated Upgrade by running ACCUPG.exe from the root of the NetWare 6 Operating System CD-ROM. This requires that you first copy the entire NetWare 6 Operating System CD-ROM to a NetWare server that will function as the Staging server. • Perform an In-Place upgrade by running INSTALL from the root of the NetWare 6 Operating System CD-ROM. • Perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NetWare 3 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NT v3.51 or v4 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). • • • 4 c4882-4 Ch01.F 2/4/02 9:53 AM Page 5 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ NETWARE 6 INSTALLATION ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ Getting Ready for NetWare 6 Whether you are building a new network with NetWare 6 or installing it into an existing network, there are certain preparations you should make so the installation goes as smoothly as possible. For those of you creating a new network from the ground up, you have the opportunity to do all the little things that will make that network easier to manage down the road. Carefully consider your choices of cabling, protocols, addressing, naming schemes, and access methods, because these are the net- work building blocks that are very difficult to change once they have been implemented. Factor in issues such as potential company growth, mergers or acquisitions, reorganizations, and all the other business considerations of the twenty-first century. If you don’t, your network may lack the flexibility neces- sary to adapt to changes at the organizational level. All of these factors will then have to be weighed against the realities of your budget. There will be inevitable compromises, but this type of advanced plan- ning will make sure those compromises don’t come back to haunt you once the network is running. As a network administrator, you may already be familiar with the network planning process. However, if you are interested in learning more about good network design techniques, see Appendix B for TIP some additional reference materials. Server Hardware Planning You will need to consider the following as you prepare the server hardware for the NetWare 6 installation: ᮣ Processor speed: The server must have a Pentium II processor or higher. Novell also recommends Pentium III 700 MHz processors for multi- processor servers. ᮣ CD-ROM drive: The server must have a CD-ROM drive that can read ISO9660 CD-ROMs. Novell also recommends using a CD-ROM drive that is compatible with the El Torito specification so that you can boot the server directly from the CD. ᮣ Server memory: A NetWare 6 server should have a minimum of 256MB of system memory (RAM). Novell recommends 512MB memory for best operation. • • • 5 c4882-4 Ch01.F 2/4/02 9:53 AM Page 6 ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● NOVELL’S NETWARE 6 ADMINISTRATOR’S HANDBOOK ᮣ Types of storage adapters and devices: Know the name of the server’s storage controllers (SCSI board, IDE controller, etc.) and the types of devices (hard disks, CD-ROM/DVD drives, tape drive, etc.) attached to those controllers. ᮣ Size of hard disks: There are two considerations when determining the appropriate size of your server hard disk(s): The DOS partition and the NetWare partition. The DOS partition is a portion of the hard disk reserved for DOS system files, server startup files, and any other DOS utilities you want to store on the server. The server should have a DOS partition of at least 200MB, but a good rule of thumb is to start with the minimum and then add 1MB for every MB of server RAM installed. That way you will be able to do a core dump to the DOS partition if necessary. The remainder of the disk is used for NetWare partition(s), which will store network data and applications.You should plan on a minimum of 2GB for your NetWare partition — for the SYS TIP volume. Novell recommends 4GB to give additional room for network data and other applications.Your best bet is to over- estimate wherever possible so you don’t have to worry about adding disk space shortly after installing the server. ᮣ Network adapters: Know the type of network adapters installed in the server and have a copy of the latest LAN drivers available. Also, you should note the adapter’s settings and the frame type(s) associated with each board. The default frame type for TCP/IP is Ethernet II and the default frame type for IPX is Ethernet 802.2. ᮣ Display and input devices: For working on the console, there should be a SVGA or better video adapter and monitor along with a standard keyboard and mouse (USB, PS/2, or Serial). However, for physical security reasons it’s not a bad idea to remove the keyboard and mouse when not in use, thus removing one potential area for mischief. ᮣ Server name: Determine the appropriate name for this server within the conventions of your overall network naming scheme. The server name can be between 2 and 47 characters in length and can incorporate alphanumeric characters, hyphens, and underscores. ᮣ Special hardware configuration: If your server supports any special hardware configurations, such as PCI HotPlug or multiple processors, make sure to note any applicable drivers that will need to be loaded once NetWare 6 has been installed. • • • 6 c4882-4 Ch01.F 2/4/02 9:53 AM Page 7 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ NETWARE 6 INSTALLATION Volume Planning You will need to consider the following as you determine the size and type of volumes to create within your NetWare partition(s): ᮣ Type of volume to create: NetWare 6 now uses NSS volumes as its default volume type. NSS volumes offer a large number of advantages over traditional NetWare volumes, and now support most of the traditional file system features. However, there are still a few features that are not available with NSS volumes, such as block suballocation, auditing, file name locks and data migration. Unless you need one of these features, it will make sense to leverage the many advantages of NSS volumes. For more information on NSS features see Chapter 8. X-REF ᮣ Size of SYS volume: The SYS volume is the storage location for all NetWare system files and products. As such, it is absolutely critical that your SYS volume not run out of space. NetWare 6 requires a minimum of 2GB for its SYS volume. Novell recommends 4GB to leave room for the installation of additional products. ᮣ Size of additional volumes: It is usually a good idea to reserve the SYS volume for NetWare files and create additional volumes for network applications and data. NSS provides disk pools that can span physical drives. Multiple volumes can reside inside each disk pool. Once created, these additional volumes can be used in any way you see fit. You can organize data in volumes based on who needs access, on the type of name space required for the files, or on how you want the data distributed across the network. Remember to keep volume names consistent with your global naming strategy. ᮣ File compression: File compression is now available on both NSS and traditional NetWare volumes. You can choose to implement File Compression at any time, but once installed it cannot be removed without recreating the Volume. ᮣ Block suballocation and block size: These are only applicable to traditional NetWare volumes. A block is a unit of space set aside for file storage. Block size is determined by the overall size of the volume, as shown in the following table. • • • 7 c4882-4 Ch01.F 2/4/02 9:53 AM Page 8 ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● NOVELL’S NETWARE 6 ADMINISTRATOR’S HANDBOOK VOLUME SIZE BLOCK SIZE 0 to 31MB 4KB 32 to 149MB 8KB 150 to 499MB 16KB 500MB to 1999MB 32KB 2000MB and greater 64KB Block suballocation permits you to subdivide a storage block so that multiple small files can share a single block.To conserve disk space on traditional volumes, block suballocation is enabled by NOTE default. However, if your server will store primarily large files, you can disable block suballocation to eliminate the additional management overhead. Protocol Planning Your biggest considerations as you decide which protocols to run on the NetWare 6 server will be: ᮣ What is already out there? ᮣ How will network usage evolve in the future? The world has already decided that its primary network protocol is IP, due to its exclusive use on the Internet.