Supervising the Network

7-14
Maintaining the NetWare Server
About NetWare Networking Protocols
As a message service, SPXII provides enhanced throughput. This protocol
reduces the amount of traffic on the wire by negotiating for large packets and
reducing the number of acknowledgements.
Applications using SPXII do not need to determine packet size. The SPXII
driver handles packet size for the application.
When setting up NetWare, you may want to turn on SPXII and enter other
information such as the maximum number of SPXII connections and sockets
for your network. See “Managing NetWare Protocols” later in this chapter.
NetWare Virtual Terminal Service (NVT2) The NVT2 service establishes
terminal connections between DOS workstations and UNIX systems over
SPXII.
NVT2 servers advertise remote login service and listen for SPX connection
requests on the advertised socket. The NVT client then sends connection
requests to the advertised socket.
Since NVT2 uses SPXII and each NVT2 connection requires a server SPXII
connection, the maximum allowed SPXII connections which you specify in
the “SAM” window should be at least 100.
With HP-UX, the NVT2 server uses the Service Access Facility (SAF-
configured) listener to handle connect requests and the SAP daemon to
handle advertising. When NVT2 is turned on in the “SAM” window, a script
registers the SAF listener process on the NVT2 socket and NetWare
Protocol Stack Daemon (NPSD) informs the SAP daemon to advertise
NVT2. See “Managing NetWare Protocols” later in this chapter or the nwcm
utility in the Command Reference for more information on NVT2.
If SPXII should go down normally, NVT2 will go down and come back up
when SPXII comes back up.
If SPXII goes down abnormally (such as a crash), NVT2 will go down and
come back up, but the service will remain registered with SAF and will be
invalid. In this case, the protocol stacks must be brought back up manually.