Once a LAN driver has been loaded with the proper frame type, then you can configure and start the TCP/IP protocol. Loading the TCP/IP protocol does not bind TCP/IP to the LAN driver; it simply loads the necessary modules required by the TCP/IP protocol.
The options for loading the TCP/IP protocol are as follows:
:LOAD TCPIP RIP=(YES/NO) <Enter>
Refer to the configuration worksheet to determine if your LAN will be using the RIP routing protocol. If so, then you will need to specify "RIP=YES" during the load command. If not, then you will need to specify "RIP=NO" during the load command.
An example command that uses information from the sample worksheet would appear as:
:LOAD TCPIP RIP=NO <Enter>
This command would load TCP/IP without support for RIP. Since the system in the sample worksheet uses static routing, it does not require the RIP routing protocol.
NOTE: OSPF routing is not a supported routing protocol unless you are using INETCFG. If you require OSPF, then you must upgrade your NetWare server to 4.11 or IntranetWare, or purchase Novell’s Multi-Protocol Router product. If you do not wish to do this, then you must use a routing service other than OSPF. You can probably use static routing on the server, and simply point a default route to the nearest OSPF router. That router should be able to accept packets from the local LAN and deliver them using OSPF, regardless of whether or not your server is running the OSPF routing protocols.
STEP: To continue to the next step in the configuration process, go to section 2.3.2.3 Bind the TCP/IP Protocol to the LAN Driver.
Copyright 1997 Unoverica Corporation, All Rights Reserved page
Send comments to docs@unoverica.com