home *** CD-ROM | disk | FTP | other *** search
- NetWare 3.12 Readme
-
- ==================================================================
-
- This NetWare 3.12 package includes three optionally installable
- products: NetWare for Macintosh (5 User), BasicMHS, NETVIEW.
-
- In addition, the electronic documentation is included on the CDROM.
- It is available on diskettes from fulfilment houses.
-
- To install any of these products, LOAD INSTALL and select from
- the menu "Product Options". Press <INS> to bring up a window
- prompting you to
-
- "Enter drive and/or path to new product source media"
-
- This is the path where INSTALL.NLM expects to find the appropriate
- PINSTALL files. The default is set to A:
-
- If you are installing from the NetWare 3.12 CDROM, you must change
- this path to one of the following: (assuming your cdrom is drive D)
-
- D:\NETWARE.312\ENGLISH\NW_MAC or
-
- D:\NETWARE.312\ENGLISH\BASICMHS or
-
- D:\NETWARE.312\ENGLISH\NETVIEW or
-
- D:\NETWARE.312\ENGLISH\DOC
-
- If you are installing from the diskette set, place the first
- appropriate Product diskette into drive A: . The names of the
- first diskettes for each product are as follows:
-
- NW_MAC
-
- BASICMHS_1
-
- NETVIEW_1
-
- DOC_01 (available upon request from fulfilment houses.)
-
- ==================================================================
- Space considerations
-
- For ease of customer installation, all disk drivers are
- copied to the startup directory (i.e. C:\SERVER.312).
- This includes all Novell and third party drivers.
-
- Also, all Novell and third party LAN drivers are
- copied to SYS:SYSTEM during the installation process.
-
- NOTE: You may remove any of these drivers that your system
- does not use without causing any detrimental effect.
- You can list all the disk drivers by looking for *.DSK
- and you can list all LAN drivers by looking for *.LAN
- in the appropriate directories.
-
- ==================================================================
- NetWare 3.12 Installation and Upgrade Errata
-
- On page 20 of "Installation and Upgrade", replace step 5
- with the following:
-
- 5. Change to the drive letter corresponding to the CD-ROM.
-
- 5a. Change to the NETWARE.312/ENGLISH directory and type
-
- INSTALL <enter>
-
-
- ==================================================================
-
- SMS Supported Storage Devices
-
- NetWare 3.12 supports tape drive technologies including 1/4 inch,
- 4mm, and 8mm storage devices. While most tape drives will work
- with the device drivers and the SBACKUP backup/restore utility
- provided in NetWare 3.12, Novell does not precertify any tape
- drives for use with NetWare.
-
- Novell's internal system qualification and testing exercise tape
- storage devices to a reasonable extent. However, Novell
- encourages all users to contact Novell Labs for a list of tape
- drives that have been certified as tested and approved with
- NetWare 3.12 to ensure reliable operation.
-
- A backup system is only as good as its ability to restore
- information consistently and reliably.
-
- Novell strongly recommends that users thoroughly pretest
- non-Novell-certified tape storage devices with the appropriate
- NetWare device driver and SBACKUP backup/restore utility prior
- to using the backup system to ensure that your network data is
- secure.
-
- In-Place Upgrade NLM
-
- Enhancements to v1.10
-
- The following enhancements have been added to the In-Place
- Upgrade NLM v1.10.
-
- - All problems listed in the version 1.00 README file have been
- fixed.
-
- - Color has been added.
-
- - The NLM has been enabled to quickly estimate the memory
- needed to upgrade during system analysis.
-
- - The NLM has been enabled to detect if the MAC.NAM module
- needs loading during system analysis.
-
- - The NLM has been enabled to make more efficient use of
- memory, shrinking the size of the NLM.
-
- - The /BATCH2 option (which allows the NLM to not pause on
- non-critical errors) has been added.
-
- - The NLM now renames the server object in the bindery if the
- server is renamed.
-
- - The /BINDERY option has been added to upgrade the 2.1x
- bindery only.
-
- - The NLM no longer upgrades dynamic bindery objects (such as
- advertising servers).
-
- - Seven new error messages (104, 114, 123, 135, 214, 248, 249)
- have been added.
-
- - Users can now easily exit the upgrade whenever the screen
- pauses.
-
- - Text changes have been made on the screens.
-
- - The NLM has been enhanced to work with the NetWare 3.12
- operating system.
-
- Problems with 2XUPGRDE.NLM
-
- Known problems in 2XUPGRDE.NLM v1.10 include the following:
-
- - 2XUPGRDE.NLM will not upgrade disks on IBM PS/2 models 56
- and 95. (Models 57 and 90 have not been tested but are similar
- to models 56 and 95). These models contain a hidden disk
- partition which stores the Micro Channel reference disk
- information. The In-Place Upgrade fails at the beginning of the
- disk modification phase and does not harm the file system.
-
- - To make the 3.1x Read Only attribute functionally equivalent
- to the 2.1x Read Only attribute, you must also set the Delete
- Inhibit and Rename Inhibit attributes. Unlike 3.1x, the v2.1x
- Read Only attribute does not allow a file to be deleted.
-
- - If you use the /BINDERY option, trustee assignments for all
- users except SUPERVISOR and GUEST are lost. Use the GRANT
- utility to reassign trustee rights.
-
- - Under rare circumstances the In-Place upgrade will run out of
- memory after upgrading the file system and bindery, but before
- updating trustee assignments. If this happens, use the GRANT
- utility to reassign trustee rights.
-
- Read README.UPG, which contains detailed information about
- the In-Place Upgrade Utility. To view this and other README
- files, run the INSTALL.BAT utility and select the
- "Select A README to view" option.
-
- Operating System
-
- - In NetWare 3.11, database applications occasionally returned
- errors that the disk was full. These errors generally occurred
- when a file's owner field was marked N/A. The OS would not
- allocate another disk block for the file when the file was
- written to. This situation generally occurred when the owner
- of the file was deleted from the bindery. This potential
- problem has been fixed. When the owner of the file is deleted
- the file ownership is given to SUPERVISOR instead of being set
- to N/A.
-
- - Support has been added to the console command processor for
- the PAUSE command in the .NCF files. You can also pass an
- argument to pause, and it will be printed before the user is
- prompted for a key to continue.
-
- - The RIP and SAP handling code has been made more efficient.
-
- - Because of changes in how NetWare 3.12 uses memory, the
- "Maximum Alloc Short Term Memory" has been changed so
- that the default minimum value is 8 MB and the maximum
- value is 32 MB. (The previous values were 2 MB and 16 MB.)
-
- Server Performance and Optimization
-
- If you are benchmarking NetWare 3.12 and performance
- optimization is an issue, please refer to Appendix A,
- "Optimizing Network Performance," in Installation and Upgrade.
-
- Ethernet 802.2/802.3 Frame Types
-
- In NetWare 3.12, Ethernet LAN drivers load with a default frame
- type of ETHERNET_802.2. If a client's ODI LAN driver is set to
- the ETHERNET_802.3 frame type, that client will not see a
- server that is using the ETHERNET_802.2 frame type.
-
- Client
-
- The NetWare shell will be left in NetWare 3.12. The shell files
- (NETX, EMSNETX, XMSNETX) will be copied to the SYS:LOGIN
- directory at installation time.
-
- Editing the INSTALL.CFG File for DOS and MS Windows Client
- Installation Software on Multiple NetWare Environments
-
- You can set up the installation program software for DOS and
- MS Windows to suit your particular networking environment. You
- should edit the [NETCFG] section of the INSTALL.CFG file before
- installing the workstation software on multiple workstations with
- similar NET.CFG files.
-
- NET.CFG is a configuration file that contains section headings
- and options that deviate from the established defaults of the
- workstation software. Use entries in the NET.CFG file to
- change the workstation's network environment or configuration.
- For more details on how to edit or create a NET.CFG file, see
- "Configuring Your Workstation" in Workstation for DOS and
- MS Windows.
-
- Configuring the [NETCFG] section in INSTALL.CFG to Load
- NetWare 4.xx Support
-
- The INSTALL.CFG file is copied on the WSDOS_1 diskette. The
- default configuration for the [NETCFG] section adds a line for
- the first network drive option only. You will need to edit the
- INSTALL.CFG file to add lines for other settings under the
- NetWare DOS Requester line option. A sample of the [NETCFG]
- section in the INSTALL.CFG file is as follows:
-
- [NETCFG]
- FIRST NETWORK DRIVE = F
-
- USE DEFAULTS = OFF
-
- VLM = CONN.VLM
-
- VLM = IPXNCP.VLM
-
- VLM = TRAN.VLM
-
- VLM = SECURITY.VLM
-
- ; VLM = NDS.VLM
-
- VLM = BIND.VLM
-
- VLM = NWP.VLM
-
- VLM = FIO.VLM
-
- VLM = GENERAL.VLM
-
- VLM = REDIR.VLM
-
- VLM = PRINT.VLM
-
- VLM = NETX.VLM
-
- Delete the semicolon (;) in front of the NDS.VLM to load the VLM
- for NetWare Directory Services.
-
- Editing Your NETCFG File to Load NetWare 4.xx Support
-
- The NET.CFG file is located in your workstation directory
- (default C:\NWCLIENT).
-
- You will need to edit the "USE DEFAULTS = OFF" section under the
- NetWare DOS Requester heading. Delete the semicolon (;) in front
- of the NDS.VLM to load the VLM for NetWare Directory Services.
-
- A sample of the default "USE DEFAULTS = OFF" section under the
- NetWare DOS Requester heading is as follows:
-
- NetWare DOS Requester
-
- USE DEFAULTS = OFF
-
- VLM = CONN.VLM
-
- VLM = IPXNCP.VLM
-
- VLM = TRAN.VLM
-
- VLM = SECURITY.VLM
-
- ; VLM = NDS.VLM
-
- VLM = BIND.VLM
-
- VLM = NWP.VLM
-
- VLM = FIO.VLM
-
- VLM = GENERAL.VLM
-
- VLM = REDIR.VLM
-
- VLM = PRINT.VLM
-
- VLM = NETX.VLM
-
- NOTE: Your initial login to a NetWare 3.12 server is slowed if
- the NDS.VLM is loading. The NDS.VLM is a default VLM and will
- load if not renamed or commented out.
-
- NetWare SQL v3.0
-
- Although most NetWare SQL v3.0 programs run successfully with
- NetWare v3.12, the following programs do not currently work
- properly with NetWare 3.12:
-
- - NetWare SQL Backup Support program (TSA-NWS.NLM)
-
- - NetWare SQL DAL Server (DALSVR.NLM)
-
- New versions of these two programs will be uploaded to NetWire
- as soon as they are available. Call 1-800-NetWare
- (1-800-638-9273) for information on the programs' availability
- and for technical support.
-
- TCP/IP
-
- - Chapter 2 of the TCP/IP Transport Supervisor's Guide includes
- information on configuring TCP/IP with INETCFG. INETCFG is
- available with add-on products such as the NetWare
- MultiProtocol Router. INETCFG is not included with NetWare
- 3.12. If you do not have INETCFG, refer to Appendix C,
- "Manually Configuring and Loading TCP/IP" of the TCP/IP
- Transport Supervisor's Guide for information on the use of
- manual LOAD and BIND commands for TCP/IP.
-
- - Name files in the /ETC. directory, such as HOSTS, NETWORKS,
- SERVICES, and PROTOCOLS are now cached into memory for
- fast lookup. As such, TCP/IP uses more memory than before. If
- this is not desirable, reduce the size of (or delete) those
- database files.
-
- - The system will fail if the TCPIP.NLM is unloaded while any
- application is actively using the AT&T Streams interface for
- TCP, UDP, or IP communications. If any such application is
- present, TCP/IP issues the following warning:
-
- Warning: Some utilities have streams open to
- the TCP/IP protocols. TCP/IP service to
- those utilities will be terminated, and
- SYSTEM INTEGRITY MAY BE COMPROMISED
-
- Unload module anyway? N
-
- You should not unload TCP/IP until you have found the utilities
- using the Streams interface and have unloaded them.
-
- MultiProtocol Router
-
- If you plan to use the NetWare MultiProtocol Router with NetWare
- 3.12 you must use NetWare MultiProtocol Router v2.1 or later;
- NetWare MultiProtocol Router versions v2.0 or earlier are not
- compatible with NetWare 3.12.
-
- NetWare Management Agent
-
- If you encounter problems with NetWare Management Agent v1.0
- running on a NetWare 3.12 server, you may need to upgrade to
- NetWare Management Agent v1.5. You can access this upgrade on
- NetWire NOVLIB LIB8.
-
- Two network servers that appear in Figure 1-2 and Figure 1-3 of
- the "NetWare Management Agent for NetView Administration Guide"
- are mislabeled.
-
- In Figure 1-2, the server labeled "NetWare for SAA server . . ."
- should be labeled "NMA for NetView server. . ."
-
- In Figure 1-3, the server labeled "NMA for NetView server
- configured as a collection point server" should be labeled
- "NetWare for SAA server configured as a collection point server."
-
- Unmirroring/Remirroring Scenarios
-
- This section describes three possible scenarios which can be
- confusing when unmirroring and remirroring NetWare devices. All
- three scenarios stem from the same situation.
-
- Suppose you have two duplexed devices, and you need to manually
- remove one of those devices from the mirrored pair. This is
- necessary before upgrading disks, adding disks, or replacing
- failed components.
-
- Assume you have only two disk drivers loaded: ISADISK and DCB,
- in that order. The corresponding controllers have only one disk
- attached. Each disk contains a NetWare partition, and volume SYS:
- is the only volume defined on the system. The data on volume SYS:
- is duplicated on each disk.
-
- Although this example deals with volume SYS: , the discussion
- also applies to any other volumes that might be mirrored.
-
- You decide to replace the ISADISK drive. First, you need to
- unmirror the drives. You go into INSTALL, select
- "Disk Options" from the "Installation Options" menu, and then
- select "Mirroring" from the "Available Disk Options" menu.
-
- From the "Partition Mirroring Status" window, you press <Enter>
- to go into the "Mirrored NetWare Partitions" window so you can
- see the individual physical devices. You highlight the second
- physical device and press <Delete>. The device entry is then
- removed from that particular window, while the other device is
- still displayed as being "In Sync."
-
- When you come back out to the "Partition Mirroring Status"
- window, it now lists the in-sync device as being a "Not Mirrored"
- logical partition. The device you deleted is listed as an
- "Out Of Sync" partition.
-
- The reason the device you deleted is considered out of sync is
- because it was once a member of a mirrored pair, and it still
- contains system fault tolerance information. As a precautionary
- feature, NetWare does not delete the drive's data when you remove
- it from the mirrored pair. You have to manually tell the OS to
- remove the SFT data if you don't want to keep the disk.
-
- It is at this point when you have an "Out Of Sync" device present
- in the system that you must be careful how you proceed,
- especially if you try to remount the volume.
-
- Scenario 1: Single Device Out of Sync
-
- For this scenario, assume that INSTALL is showing the first
- device (ISADISK) as "Not Mirrored" and the second device (DCB)
- as "Out Of Sync." You bring down the server, turn it off, and
- remove the ISADISK drive and controller. So that users can
- continue working while you get the replacement drive, you
- bring the server back up and load only the DCB driver. What
- was once the second device is now the only device in the system.
-
- The problem is that this device is still "Out Of Sync" because
- you haven't modified it to indicate that it's now the only
- device. Without realizing this, you type the MOUNT SYS command
- at the console. Immediately, the console displays the
- following message:
-
- :mount sys
-
- There are no accessible disk drives with
- NetWare partitions
-
- Check to see that the needed disk drivers
- have been loaded and that
- your disk drives are properly connected and
- powered on.
- :
-
- For most people, the first reaction to this message is to
- think, "Wait a minute. All I did was unmirror the devices.
- There is still one good disk in there with a NetWare partition
- on it." The next impulse might be to go into INSTALL and check
- under "Volume Options" to see if volume SYS is still there.
-
- When you press <Enter>, you see the "Volumes" window but no
- volumes are listed.
-
- Go back to INSTALL's "Mirroring" option, which is under "Disk
- OPtions" in the "Installation Options" menu. Check for a device
- listed as "Out Of Sync" in the "Partition Mirroring Status"
- window.
-
- Highlight a partition and press <Enter> to view / modify the
- associated mirror set. Press <F3> to restore an "Out Of Sync"
- partition. Press <Escape> to return to previous menu.
-
- The message about there being no accessible disk drives is only a
- warning message but, unfortunately, it doesn't indicate what's
- really happening. Remember that when a drive's status is "Out Of
- Sync," the OS can no longer recognize volume information on that
- disk. What the OS is trying to say is that it checked for a
- device that might have a copy of volume SYS: on it to mount,
- but couldn't find one.
-
- The help text at the bottom of the INSTALL screen says to press
- <F3> to restore an "Out Of Sync" partition. With the "Out Of
- Sync" device highlighted, press <F3>. Again, you'll see the
- message saying that "There are no accessible disk drives with
- NetWare partitions." As indicated in the message, press <Esc>
- to continue.
-
- You see a message similar to the following:
-
- Salvage Volume SYS Segment 0?
-
- No
-
- Yes
-
- If you want the device to remain volume SYS: and retain its data,
- answer "Yes" to this prompt.
-
- The OS will then modify the drive's tables to indicate that
- this is a standalone drive, it is no longer part of a mirrored
- pair, and it contains volume SYS: data. The device will then
- be listed in the "Partition Mirroring Status" window as a
- "Not Mirrored" device.
-
- If you answer "No" to this prompt, you are in essence saying,
- "No, I don't want this drive to be a member of a mirrored
- pair, I don't care about the volume, and I don't want to
- salvage its data." The OS will then proceed to delete the
- entire volume definition table, and you'll be left with a
- "raw" NetWare partition containing no volume and no data.
-
- Scenario 2: Two In Sync Devices with Same Volume Name
-
- The second scenario continues on from where Scenario 1 leaves
- off. With the ISADISK drive still gone, you've brought the
- other device back into sync with itself. It is now a
- standalone drive containing volume SYS: . In the meantime, you
- discover that there was really nothing wrong with the first
- drive after all it was a cable problem. So you bring the
- server down again, turn it off, replace the cable, reinstall
- the ISADISK controller and drive, and power up the server,
- loading both ISADISK and DCB drivers.
-
- Now, without realizing it, you've introduced two separate devices
- that both have the same volume name but have different table
- information.
-
- If you go into INSTALL and select "Mirroring," you'll see two
- "Not Mirrored" devices. Everything seems fine there, so you go
- to the system console, and type the MOUNT SYS command to get the
- server back up in a hurry. The console now displays a series of
- warning messages:
-
- :mount sys
-
- WARNING: Volume SYS has multiple definitions for segment0
-
- WARNING: Volume SYS segment 0 ends at block 6247
- and segment 0 starts at block 0
-
- WARNING: Definition for sync 0 of volume SYS removed
-
- WARNING: Definition for volume SYS is invalid
- Volume SYS could NOT be mounted
- some or all volume segments can not be
- located
-
- :
-
- The numbers in the second message could be different depending
- on the size of your volume. The third message is a warning
- message; even though it says the definition has been removed,
- it hasn't yet.
-
- All these messages are saying is that there are two devices
- that have the same volume name, and the OS can't determine
- which one contains the valid volume segment.
-
- Again, the first impulse for most people is to go back into
- INSTALL and check the volume options, because SYS was there
- before you downed the server a few minutes ago. At that point,
- these same messages will start displaying one by one in the
- middle of the screen. This time, you have to press <Esc> after
- each one.
-
- Volume SYS has multiple definitions for segment 0.
-
- <Press ESCAPE To Continue>
-
- Volume SYS segment 0 ends at block 6247, and
- segment 0 starts at block 0.
-
- <Press ESCAPE To Continue>
-
- Definition for sync 0 of volume SYS removed.
-
- <Press ESCAPE To Continue>
-
- Definition for volume SYS is invalid.
-
- <Press ESCAPE To Continue>
-
- After you've gone through this string of error messages, a box
- will appear that says:
-
- WARNING: There are currently some invalid
- volume segment entries in the volume
- definition tables. Any new updates made to
- the volume definition tables will cause
- these invalid volume segments to be
- deleted.
-
- <Press ESCAPE To Continue>
-
- When you press <Esc>, the following prompt appears:
-
- Delete The Invalid Volume Segments?
-
- No
-
- Yes
-
- Answer "No" to this prompt.
-
- Everything up to this point is nothing more than a series of
- warning messages. When you answer "No," nothing is deleted.
- You can then determine which device has the most current data
- on it. If necessary, switch to the colon prompt, unload both
- disk drivers, and load them one at a time to try to decipher
- which of the devices contains the most recent volume SYS data.
- Then unload the driver for the device that you know is more
- current, load the other driver, delete the volume, and reload
- the driver. You can then start the remirror process as
- described above.
-
- If you answer "Yes," the OS deletes the invalid volume segments.
- But since it can't determine which of the devices had the
- correct (valid) volume segment, it deletes all of the volume
- definition tables on every device associated with the error.
- You'll then have to start all over from scratch and redo the
- volume the way you thought it should have been.
-
- Scenario 3: One Device In Sync and One Out of Sync
-
- For the third scenario, return to the original unmirroring
- situation. You have two devices, one listed as "Not Mirrored"
- and the other listed as "Out Of Sync." At this point, you have
- not unloaded any device drivers both ISADISK and DCB drivers
- and associated hardware are present.
-
- Suppose you are familiar with the fact that to get an out of
- sync device back in sync with itself, you can highlight it in
- the "Partition Mirroring Status" window and press <F3> (as
- explained in Scenario 1). When there are multiple devices and
- you indicate that you want to modify the tables, NetWare does
- not allow you to modify the tables on devices that contain the
- same volume. So when you press <F3> on the out of sync device,
- a message similar to the following is displayed:
-
- Warning!! The selected partition contains "volume
- SYS segment 0" and that volume is already defined.
-
- <Press ESCAPE To Continue>
-
- When you press <Esc>, a prompt appears that says:
-
- Rename The Volume Segment?
-
- No
-
- Yes
-
- To keep the volume's data intact, answer "Yes" and rename the
- volume segment. If you answer "No," you will end up with two
- volume segments with the same name, but different device
- information. The only way to recover from this problem is to
- restore volume SYS: from a backup. After you rename the volume
- segment, another prompt will appear:
-
- Salvage Volume SYS Segment 0?
-
- No
-
- Yes
-
- At this point, answer "Yes" because you do want to salvage the
- volume.
-
- After you answer "Yes," you will have two separate devices
- with the same data, but with different volume names. You can
- then determine which volume is the most current, delete the
- other volume, and remirror the devices.
-
- Alternatively, you can answer "No" to both prompts. Before doing
- so, however, make sure that one of the devices is still in sync
- and contains the data you want.
-
- When you answer "No" to the prompt about renaming the volume,
- and also answer "No" to the prompt about salvaging volume SYS
- segment 0, INSTALL will update the "Partition Mirroring Status"
- window so that the device is displayed as "Not Mirrored." The OS
- has deleted the volume definition table because you said, in
- essence, that you don't want to rename the volume and you don't
- want to keep the data. So it simply makes this another available
- partition with no volume and no data. You can then remirror the
- partitions.
-