home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
nfssft.exe
/
NFSSFT.TXT
Wrap
Text File
|
1995-11-02
|
22KB
|
536 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: NFSSFT; SFT III for NFS Service 2.1-NW 4 Ed
README FOR: NFSSFT.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare NFS Services - NetWare 4 Edition 2.1
ABSTRACT:
The SFT III Update for NetWare NFS Services 2.1 is a software
update to the NetWare NFS Services 2.1 product that enables the
NFS Services 2.1 software to run on NetWare SFT III 4.10.
-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY
THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT
OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------
SYMPTOM:
NetWare NFS Services 2.1, NetWare 4 Edition requires this update
in order to support NetWare 4.10 SFT III system software.
SOLUTION:
Install NFSSFT.EXE file as described below in Installation.
Self-Extracting File Name: NFSSFT.EXE
This SOLUTION contains the following sections:
General Information
Additional Release Notes
TCP/IP Configuration
===============
General Information
===============
NFSSFT replaces some but not all of the NFS Services 2.1 files.
It cannot run on its own, and cannot be used to upgrade from
NetWare NFS 1.x or NFS Gateway 1.x to NetWare NFS Services 2.1
NetWare 4 Edition.
NFSSFT is not intended for use with native 4.10. The SFT III
upgrade to NetWare 4.10 operating system is required.
If you remove this SFT III update from an NetWare SFT III
server, make sure that you also remove the NetWare NFS Services
2.1 product. NetWare NFS Services cannot function properly by
itself and would be unstable on SFT III.
NFSSFT patch can be installed before or after the NFS Services
product itself.
===================
Additional Release Notes:
===================
* If NetWare NFS file system is mounted using the "soft"
option, then I/O errors on the NFS client may be seen if the
primary server fails, since it takes time for the secondary
server to take over. If you wish to prevent this possibility,
use the hard mount option or increase the timeout parameter
associated with the soft mount.
* The RARP Server is not supported on NetWare SFT III. The
RARP NLM will exit when loaded on SFT III.
* The remote access services are available only through
UNICON. Do not enable remote access (FTP and XCONSOLE) by using
INETCFG utility. Instead, use UNICON to do the same thing.
* XCONSOLE does not use the fault-tolerant features of SFT
III, since the NLMs related to XCONSOLE service load in the I/O
Engine. Therefore, in the event of the SFT III Primary Server
failure, the XCONSOLE service stops and any XCONSOLE sessions are
terminated. However, the service can be restarted through UNICON
and new XCONSOLE sessions can be created by attaching to the IO
Engine of the new Primary Server.
For example, consider an SFT III system having the following IP
addresses for its IO Engines:
IO Engine 1: IP addr=154.88.219.48
IO Engine 2: IP addr=154.88.219.49
REMOTE.NLM and RSPX.NLM are loaded in both the IO Engines.
Let us assume that IO Engine 1 is initially the Primary Server.
To start an XCONSOLE session, the following steps are carried
out:
1. Start the XCONSOLE service through UNICON.
2. Open an XCONSOLE session from an XServer by connecting to
the Primary Server IOEngine, e.g. telnet to IOEngine1 (IP
addr=154.88.219.48)
Subsequently, the Primary Server fails and IOEngine2 takes over
as the new Primary Server. The XCONSOLE service stops.
To restart the XCONSOLE session, follow these steps:
1. Start the XCONSOLE service through UNICON.
2. Open an XCONSOLE session from an XServer by connecting to
the Primary Server current IOEngine, e.g. telnet to IOEngine2 (IP
addr=154.88.219.49).
You cannot start XCONSOLE on both IO1 and IO2 concurrently,
because they share the same
MS Engine.
XCONSOLE clients (X servers) can attach to the IP address of the
primary I/O engine. Attempts to access the MS engine will fail.
* TIME Synchronization is important. NFS Services will not
function properly if the time is not synchronized to the network.
To ensure that the NFS Services are loaded only after time is
synchronized, this update modifies MSAUTO.NCF so that it loads a
TIMCHK.NLM instead of executing UNISTART.NCF. The TIMCHK.NLM in
turn executes UNISTART.NCF, but only after the time is
synchronized. Do not manually start the NFS Services or use
UNISTART until time synchronization is complete (the console
command TIME reports that "Time is synchronized to the network").
===============================
TCP/IP Configuration on NetWare SFT III
===============================
The SFT III system from an TCP/IP network perspective consists
of the following:
1. The two IO Engines - IO1 and IO2 connected to the physical
network, each having a unique IP address and using the same
Subnet Mask as used by other Nodes on the Subnet.
2. The MS Engine resides on a Virtual LAN and is not directly
connected to the physical or the real network. The MS Engine
interfaces to the real network through the IO Engine. The two IO
Engines (can be visualized to) have a common IO Engine interface
which resides on the Virtual LAN along with the MS Engine. Let
us call this common interface as the IO Engine-MS Engine Internal
Interface.
The Virtual LAN in effect is a stub-subnet with the IO Engines
acting as routers between the real network and the Virtual LAN
(the IO Engine on the Primary Server routes IP packets between
the MS Engine and the real/physical network).
The two nodes on the Virtual LAN, the MS Engine and the IO
Engine-MS Engine Internal Interface, have a common stub-subnet
Mask and each has a unique IP address.
From the above description, it is clear that an SFT III system
requires four IP addresses: one for IO Engine 1, one for IO
Engine 2, one for the MS Engine and one for the IO Engine-MS
Engine Internal Interface.
However, it is important to note that addresses in the
stub-subnet mask address range cannot be allocated to any other
node on the real/physical network. Therefore, the actual range
of IP addresses to be allocated or reserved for the SFT III
system extends beyond four addresses.
Figure 1. TCP/IP Configuration Example
+-------------------------------+
| Mirrored Server - MS Engine |
| 154.88.219.33 |
+-------------------------------+
|
|
| Virtual LAN
----------------------------------------------
|
|
(IO Engine-MS Engine | Internal Interface)
|------------54.88.219.34-----------|
+-----------------+ +-----------------+
| IO Engine 1 | | IO Engine 2 |
| 154.88.219.48 | | 154.88.219.49 |
+-----------------+ +-----------------+
| |
| Real Network 154.88.219.0 |
--------------------------------------------------------------
Let us assume some example addresses. An SFT III system is to
be setup on a class B subnetwork; the Subnet IP address is
154.88.219.0. The Subnet Mask used by the IO Engines will be
255.255.255.0 (FF.FF.FF.00) - the same as for any node on a Class
B Subnet.
Let us assume that the range of IP addresses from 154.88.219.32
to 154.88.219.63 is available.
The stub-subnet mask can be configured to one of the following:
Stub-Subnet Mask Number of IP addresses to be
set aside
exclusively for the
Stub-Subnet
1. 255.255.255.248 (FF.FF.FF.F8) 8
2. 255.255.255.240 (FF.FF.FF.F0) 16
3. 255.255.255.224 (FF.FF.FF.E0) 32
Let us assume that we select the Stub-Subnet Mask as
255.255.255.240 and that we choose to allocate the following IP
addresses for the Nodes on the Virtual LAN or the Stub-Subnet:
Node IP Address Stub-subnet
Mask
MS Engine 154.88.219.33
255.255.255.240
IOEngine-MSEngine Internal Interface 154.88.219.34
255.255.255.240
Stub-Subnet Mask = 255.255.255.240:
240 = 1111 0000
33 = 0010 0001 (MS Engine)
34 = 0010 0010 (IO-MS internal interface)
Stub-Subnet Address = 154.88.219.32:
Node ID for MS Engine = 1
Node ID for IO-MS internal interface=2
Now the range of IP addresses from 154.88.219.32 to
154.88.219.47 has to set aside or reserved exclusively for the
SFT-III system and cannot be used by any other node on the Class
B subnet. So, we allocate the IP addresses for the two IO
Engines as follows:
Node IP Address Subnet Mask
IO Engine 1 154.88.219.48 255.255.255.0
IO Engine 2 154.88.219.49 255.255.255.0
To setup TCP/IP configuration on SFT III system, the following
steps are to be carried out:
1. Load INETCFG in IO Engine1 - select Bindings Option,
add/select TCP/IP protocol and configure the IP address and the
Subnet Mask for IO Engine1.
Then select the Protocols Option, select TCP/IP protocol and
configure the following:
"IP address for the SFT III Network" (i.e. IP address for the
IO-MS Internal Interface) and the "Subnet Mask of SFT III
Network" (i.e. the Stub-subnet Mask)
2. Load INETCFG in IO Engine2 and repeat the same steps as was
done on IO Engine1.
3. Load INETCFG in the MS Engine - select Protocols Option,
select TCP/IP protocol and configure the following:
"IP address for the SFT III Network" (i.e. IP address for the MS
Engine) and the "Subnet Mask of SFT III Network" (i.e. the
Stub-subnet Mask).
Once the TCP/IP configuration for the SFT III system is complete
(and TCP/IP has been loaded in both the IO Engines and the MS
Engine), you can verify the same by doing a PING operation to the
MS Engine IP address from another node (say, a Unix host) on the
network.
Note that the IO Engine - MS Engine Internal Interface address
must exist on the same network as the IP address bound to the I/O
engines, as seen below in MSAUTO.NCF.
Note also that the RIP = YES parameter is required for proper
function, to allow RIP broadcasts to go to the network.
Do not modify these files with any text editor, use INETCFG
only.
After successful configuration, the .NCF script files used by
NetWare SFT III during bootup will contain the network
configuration. Using the same example, the script files would
contain:
I/O Engine 1 SYS:ETC/IO1/NETINFO.CFG (IO engine 1) contains:
LOAD TCPIP RIP=YES FORWARD=YES
BIND IP NE2000 ADDR=154.88.219.48 MASK=255.255.255.0
BIND IP MSENGINE ADDR=154.88.219.33 MASK=255.255.255.240
I/O Engine 2 SYS:ETC/IO1/NETINFO.CFG (IO engine 2) contains:
LOAD TCPIP RIP=YES FORWARD=YES
BIND IP NE2000 ADDR=154.88.219.49 MASK=255.255.255.0
BIND IP MSENGINE ADDR=154.88.219.33 MASK=255.255.255.252
SYS:ETC/NETINFO.CFG (the MS engine) contains:
LOAD TCPIP RIP=YES FORWARD=NO
BIND IP MSENGINE ADDR=154.88.219.34
Self-Extracting File Name: nfssft.exe
Files Included Size Date Time
..\
NFSSFT.TXT (This file)
NFSSFT.TXT 22196 11-2-95 5:36:14 pm
..\DISK1\
PINSTALL.NLM 166639 10-7-95 10:17:36 am
README.TXT 15668 11-2-95 5:09:32 pm
SPACE.DAT 13 10-10-95 1:28:48 pm
..\DISK1\SYSTEM\
CONFADDR.NLM 27582 6-28-95 5:39:06 pm
DISPATCH.NLM 17781 9-28-95 7:22:18 pm
DNSADMIN.NLM 43527 6-28-95 11:48:46 am
DNSAGENT.NLM 32606 10-6-95 4:26:28 pm
DNSDBGEN.NLM 12992 6-28-95 11:51:42 am
NAMED.NLM 33893 9-28-95 7:24:42 pm
NFS_41X.NAM 14930 6-12-95 4:24:42 pm
NISADMM.NLM 19763 6-12-95 11:25:24 am
NISDMAG.NLM 32917 6-12-95 10:57:40 am
NISSERV.NLM 23871 6-12-95 11:06:30 am
PCONFIG.NLM 21587 10-7-95 10:17:14 am
SRVAGT.NLM 24861 6-12-95 10:51:12 am
UNICON.NLM 92205 6-28-95 5:28:02 pm
UNINSTAL.NLM 94256 10-7-95 10:18:34 am
USRAGT.NLM 15695 9-28-95 7:21:00 pm
..\DISK1\SYSTEM\NLS\
..\DISK1\SYSTEM\NLS\4\
CONFADDR.MSG 2201 6-28-95 5:39:00 pm
DISPATCH.MSG 1691 9-28-95 7:22:16 pm
DNSADMIN.HLP 6167 5-31-95 4:25:56 pm
DNSADMIN.MSG 5193 6-28-95 11:48:38 am
DNSAGENT.MSG 2016 10-6-95 4:26:26 pm
NAMED.MSG 4699 9-28-95 7:24:38 pm
NFS_41X.MSG 2169 6-12-95 4:24:38 pm
NIS.MSG 7886 10-4-95 2:04:14 pm
NISADMM.HLP 3250 10-20-94 1:17:20 pm
NISADMM.MSG 2980 6-12-95 11:25:16 am
PCONFIG.DAT 550 10-6-95 4:24:34 pm
PCONFIG.HLP 2183 7-29-92 1:27:20 pm
PCONFIG.MSG 1142 10-7-95 10:17:12 am
PFILES.DAT 6705 10-10-95 1:28:48 pm
PINSTALL.HLP 7839 6-20-95 9:20:58 am
PINSTALL.MSG 11860 10-7-95 10:17:30 am
SRVAGT.MSG 1361 6-12-95 10:51:06 am
UNICON.HLP 15185 5-31-95 8:12:20 am
UNICON.MSG 10301 6-28-95 5:27:46 pm
UNINSTAL.HLP 898 3-3-95 1:01:18 pm
UNINSTAL.MSG 11860 10-7-95 10:18:30 am
USRAGT.MSG 705 9-28-95 7:20:56 pm
..\DISK2\
..\DISK2\SYSTEM\
FTPSERV.NLM 47875 10-7-95 4:39:12 pm
IOTADJST.NLM 4294 9-11-95 12:02:42 pm
IOXCSTUB.NLM 4685 9-11-95 11:53:46 am
LPR_GWY.NLM 14043 10-10-95 1:25:24 pm
MSSHIM.NLM 1149 3-28-95 9:35:08 am
MSTADJST.NLM 3507 9-11-95 12:02:04 pm
MSXCSTUB.NLM 3495 9-11-95 11:54:26 am
NFSCA.NLM 31728 6-28-95 12:08:12 pm
NFSGWVS.NLM 225079 10-4-95 3:23:04 pm
NFSSERV.NLM 39901 10-7-95 6:17:04 pm
NWPCNFSD.NLM 24294 10-10-95 12:14:42 pm
PKPATCH.NLM 2266 8-7-95 6:28:30 pm
PLPD.NLM 34854 10-7-95 3:57:30 pm
PM410.NLM 9484 3-21-95 11:25:16 am
PRADM.NLM 36487 10-7-95 3:56:06 pm
PRADM_SA.NLM 8275 10-6-95 4:38:46 pm
PRLIB.NLM 21948 10-7-95 3:58:32 pm
RARPSERV.NLM 8175 10-7-95 4:24:22 pm
TADJST.NLM 2299 9-11-95 12:00:48 pm
TCPIP.NLM 163028 5-8-95 11:52:22 am
TELNETD.NLM 10802 9-29-95 1:02:44 pm
TIMCHK.NLM 2243 8-16-95 2:32:04 pm
UNIXLIB.NLM 32589 6-28-95 12:41:22 pm
XCONSOLE.NLM 4039 9-11-95 11:52:44 am
XCONSSRV.NLM 67252 10-7-95 4:08:42 pm
XCSTUB.NLM 2249 8-8-95 3:08:54 pm
..\DISK2\SYSTEM\NLS\
..\DISK2\SYSTEM\NLS\4\
FTPSERV.MSG 5286 10-7-95 4:38:56 pm
IOTADJST.MSG 655 9-11-95 12:02:40 pm
IOXCSTUB.MSG 722 9-11-95 11:53:44 am
LPR_GWY.MSG 2431 10-10-95 1:25:20 pm
MSTADJST.MSG 533 9-11-95 12:02:00 pm
MSXCSTUB.MSG 504 9-11-95 11:54:24 am
NFSCA.MSG 5007 6-28-95 12:08:08 pm
NFSCAHLP.HLP 13190 1-20-95 10:27:20 am
NFSGWVS.MSG 26699 10-4-95 3:22:28 pm
NFSSERV.MSG 4574 10-7-95 6:16:56 pm
NWPCNFSD.MSG 3848 10-10-95 12:14:40 pm
PKPATCH.MSG 236 8-7-95 6:28:28 pm
PLPD.MSG 6859 10-7-95 3:57:26 pm
PRADM.MSG 3676 10-7-95 3:56:00 pm
PRADM_SA.MSG 211 10-6-95 4:38:42 pm
PRLIB.MSG 1596 10-7-95 3:58:28 pm
TADJST.MSG 197 9-11-95 12:00:46 pm
TELNETD.MSG 1832 9-29-95 1:02:42 pm
TIMCHK.MSG 318 8-16-95 2:32:02 pm
UNIXLIB.MSG 2253 6-28-95 12:41:12 pm
XCONSOLE.MSG 799 9-11-95 11:52:42 am
XCONSSRV.MSG 4358 10-7-95 4:08:36 pm
XCSTUB.MSG 265 8-8-95 3:08:52 pm
Installation Instructions:
1. (Optional step) After the base SFT III system is installed,
make complete backup of SYS:SYSTEM and any critical data
directories.
2. Apply all the latest NetWare SFT III Operating System
patches to the base SFT III system. Also, apply the latest
version of DS.NLM.
You can get these either from NetWire or from the Web site at
http://www.novell.com.
3. Configure TCP/IP on the SFT III server. Detailed
instructions are at the end of this document.
4. (Optional step) Make a backup of TCPIP.NLM. The
installation process automatically upgrades TCPIP.NLM if the
installation program (INSTALL.NLM) detects an older version.
5. From a workstation attached to the NetWare SFT III 4.10
server, create a directory named NFSSFT on any NetWare volume on
the Primary MS Engine.
MD NFSSFT
6. Copy NFSSFT.EXE into the new directory.
NCOPY NFSSFT.EXE SYS:NFSSFT
7. Type NFSSFT <enter> to extract the files.
CD NFSSFT
NFSSFT
8. From the console of the MS engine, check the mirror status
to ensure both partitions are synchronized.
MIRROR STATUS
9. From the server console, run UNISTOP.NCF as a general
precaution.
UNISTOP
10. If NFS Services 2.1 is already installed on this machine,
make sure that you are at the console of the same machine now.
This software update and NFS Services 2.1 both should be
installed on the same physical machine. When both partitions
activates, this will be the primary server.
11. Load the installation program.
LOAD INSTALL
12. Select PRODUCT OPTIONS.
The Currently Installed Products list appears.
13. Press <Insert> to install a new product.
14. Press <F3> to specify the location of the NFSSFT directory.
The "SPECIFY DIRECTORY PATH" dialogue box will appear.
15. Enter the path to the directory where the NFSSFT files were
previously extracted, in the DISK1 subdirectory.
SYS:/NFSSFT/DISK1
After the installation program installs the files, the
"Currently Installed Products" list will contain a new entry:
NFSSFT NetWare NFS Services 2.1, SFT III Update
16. Exit the Installation program or press <ALT-ESC> to return
to the system console prompt. The installation of the update
software is now almost complete.
17. Copy the file NFS.NAM manually from the Netware boot
directory on the server where this update was installed to the
boot directory of the other server in the SFT III pair. This is
necessary because the NFS.NAM is loaded from the DOS partition,
usually the C: drive, which is not mirrored. All console
commands which access files in the DOS partition go to the DOS
partition on the Primary MS Engine.
18. If NFS Services 2.1 is not already installed on this
machine, install it now according to its packaged instructions.
19. Installation is now complete, NFS Services is running, and
the startup files have been modified for NFS Services to autoload
the next time SFT III boots. If it is ever necessary to manually
start the Services from the server console, load the TIMECHK.NLM.
Although UNISTART.NCF is still present, as with pre-upgrade NFS
Services, it is better to use TIMECHK instead. See notes below
on Time Synchronization for more information.
20. Additional steps are needed to allow replication of the NIS
database with other NIS servers because NIS broadcasts cannot
propagate across the internal IP router of SFT III. Similarly,
the NIS server on SFT III will never recieve the "ypbind
-broadcast" from any other UNIX NIS client.
To enable replication and proper operation of NIS:
20a. If NetWare is an NIS slave server, explicitly enter the IP
address of the NIS master server. From UNICON, go to Manage
Replica Databases and try to create a replica domain, and enter
the domain name. When the broadcast fails, enter the IP address
of the NIS master for the domain.
20b. If NetWare is an NIS master, NIS clients have to be
explicitly bound to the IP address for the MS engine.
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their respective owners. Consult your product manuals for
complete trademark information.
-----------------------------------------------------------------