NetWare 5.1 Advanced Administration

Chapter 2: Using the Server Console to Control and Manage a NetWare Server

 

Objectives:

This chapter discusses managing the server by typing commands and using utilities on the server itself. The objectives important to this chapter are on page 2-1:

  1. Identify NetWare Operating System Components
  2. Execute Commands at the Server Console
  3. Identify How to Load and Unload NLMs
  4. Identify Server Configuration Files
  5. Use Server Script Files to Automate Console Commands
  6. Determine Requirements for Java Application Support on the NetWare Server
  7. Define and Configure the NetWare GUI
  8. Identify Administrative Tasks Performed with ConsoleOne
  9. Identify How to Remotely Manage the Console
  10. Define Methods for Protecting your Server
Concepts:
Introduction

Chapter 2 begins by reviewing a definition of a server: A server must not only have the minimum hardware characteristics from Chapter 1, it must be running the NetWare operating system, or it is not a NetWare server. (Workstations run NetWare client software.)

A server is a computer running the NetWare operating system, which provides services to clients. The key to starting a server, once it is installed, is running the SERVER.EXE program from DOS, which then loads and runs the NetWare operating system. Some functions of a server are reviewed: managing network communications between devices, storing and retrieving data, managing network printing, and providing a network file system.


Identify NetWare Operating System Components

The NetWare operating system is composed of many pieces that fall into three categories:

  • the Kernel - the heart of the operating system that other parts hook into. It is the SERVER.EXE program. Functions of the Kernel include:
    • Multiprocessor support - the operating system will support up to 32 processors in one server
    • Memory protection - programs can run in protected mode, which means that that they run in memory space that is protected from other programs intruding in it
    • Virtual memory - all computers run better with more RAM, so part of the hard drive space can be used as simulated RAM
    • Load balancing - tasks can be shifted from one processor to another to speed up execution
    • Scheduling - events can be set to happen at a later time. A variation on this idea is preemption. Tasks can be set to run preemptively, forcing other tasks to wait until they are done to continue.
  • the Server Console - the command line interface for the server, which allows us to give commands to the operating system, to control processes and manage the network
  • the NetWare Loadable Modules - the NLMs are programs that run in addition to the Kernel; they support it, add to it, hook into it, and perform specific functions. NLMs can be loaded and unloaded to use memory more efficiently.

Be aware that the SERVER.EXE file is a DOS program, and it is stored in the DOS partition. What is a partition? The word has several meanings. In this case, a partition is a logical division of a hard drive. In the example used, we have two logical divisions, one for each operating system we are running on the server (DOS and NetWare). The server boots into DOS (loads and runs it when the server is turned on), then loads NetWare.

Page 2-5 lists four types of NLMs that are important to running the server:

  • Disk drivers - older versions of NetWare used files ending with .DSK; NetWare 5 and 5.1 require two files for each hard drive, ending with .HAM and .CDM The system that requires such files is called NetWare Peripheral Architecture (NPA).
  • LAN drivers - the drivers for your NICs; files typically end with .LAN
  • Name space modules - three name spaces are discussed, each supported by a separate .NAM file:
    • Long name space - supports long file names from Windows 95 (and later), and OS/2. The file is LONG.NAM
    • NetWare File System name space - supports long file names from NetWare itself. The file is NFS.NAM
    • Macintosh name space - supports long file names from Macintosh computers. The file is MAC.NAM (Macintosh files are also stored differently from files on other systems.)
  • NLM utilities - this category covers NLMs that serve any other purpose. A list of common purposes appears on page 2-7. They include running a Java Virtual Machine, supporting printing, and providing file storage.

Execute Commands at the Server Console

Perhaps owing to its DOS heritage, the NetWare server features a command line on which you may enter commands to the system. Some possible commands are listed in your text:

  • DISPLAY NETWORKS. Use to see all IPX networks that are connected to your network.
  • DISPLAY SERVERS. Use to see all IPX servers that are on your network.
  • REINITIALIZE SYSTEM. Use to enable configuration changes made since the last time the commands in NETINFO.CFG were executed.
  • DSTRACE. Use to troubleshoot NDS.

The SET command may be used to change many of the operational settings for the server. The format of the command is:

  set parameter=value

This type of command may be used in the STARTUP.NCF file. (What the hell is that? It's a file that the server reads when it starts. NCF stands for NetWare Configuration File. More in a few pages...) Settings may be changed from the command line for the current work session, or they may be changed and saved in configuration files with the MONITOR and NWCONFIG utilities.

The server runs many processes simultaneously, and it is possible to toggle between screens that provide access to information and management tools for these processes. You should be familiar with the three hot key sequences for moving between screens and commands:

  • CTRL-ESC - pressing the Control and Escape keys will display the Current Screens menu. You can select and move to any listed screen.
  • ALT-ESC - pressing the Alt and Escape keys will toggle you immediately to the next available console screen. Pressing ALT-ESC repeatedly will cycle through the available screens.
  • CTRL-ALT-ESC - this command displays the Hung Console screen, where you may select one of two options: down the server, or cancel a volume mount. This can be handy if you need to shut down the server in a hurry.

In addition, be aware that if the GUI interface stops functioning, you can often use the ALT-ESC command to toggle to the Server Console command line. There, you can enter the command "UNLOAD JAVA", which will unload the GUI interface. You can reload the GUI as described below.

Most commands that can be entered from the Server Console can be explained by the built-in Help system by typing the word "Help", followed by the command you would like help with.


Identify How to Load and Unload NLMs

A command that starts an NLM is said to "load" it into memory. Previous versions of NetWare required the operator to load NLMs using the command "LOAD" like this:

      	LOAD MONITOR
      
However, NetWare 5 removed the need for the keyword "LOAD", so the previous command can be executed simply by entering the name of the NLM:
      	MONITOR
      

To unload an NLM from memory (they are modular, remember?), you enter the command "UNLOAD" followed by the name of the NLM.


Identify Server Configuration Files

The procedure for starting a server is listed below. Most of the steps can, and should, be automated:

  1. The server boots from DOS.
  2. The SERVER.EXE program is run.
  3. The server must be told its name and its IPX Internal number.
  4. The disk driver for NetWare is loaded, giving the server access to the hard drive.
  5. The LAN driver for NetWare is loaded, giving the server access to its NIC and the network.
  6. The process of "binding" IPX and/or IP to the LAN driver teaches the server to use the IPX and/or IP protocol with the network card on the proper net.

Assume you have to start a dozen servers each morning. Do you want to enter all that information on each console? Novell doesn't want you to do that either. Server Configuration files are files used to make the process above more automatic. The text compares the server configuration files to batch files used in DOS: the autoexec.bat file and the config.sys file. Note the server oriented use of each of these:

  1. AUTOEXEC.BAT - a line is put at the end of this file to call (execute) SERVER.EXE. This is really the only purpose of this file on a NetWare server.
  2. SERVER.EXE - this is the core of NetWare. It reads the next two files for more instructions, while it loads the NetWare Operating System.
  3. STARTUP.NCF - basic configuration settings go in this file, like the disk driver. This is similar to the function of config.sys on a DOS machine.
  4. AUTOEXEC.NCF - other configuration settings for the server, like the LAN driver and time zone settings. This is similar to the function of autoexec.bat on a DOS machine.

Server batch files must have .NCF extensions. The ones named above are boot files, because they run on boot. They are configuration files, because they affect how the server runs. They are also text files that can be edited with any ordinary text editor. They can easily be edited with the NetWare utilities NWCONFIG.NLM ( a server configuration utility) and EDIT.NLM. Take care when using NWCONFIG. It is menu based, and offers menu choices for creating or editing .NCF files.  Creating an .NCF file will destroy the existing version of it. This is very counterproductive if all you wanted to do was read the file.

You can start a server without using the usual STARTUP.NCF by entering the command:

	SERVER -S path_to_file\name_of_file

This assumes you are going to supply a path to an alternate STARTUP.NCF file. If you want to start the server without this file at all, the command is:

	SERVER -NS

and you will be prompted for the name of your disk driver file. To start the server without loading the AUTOEXEC.NCF file, the command is similar:

	SERVER -NA

Note the lists of likely contents provided in the text for two NetWare configuration files:
Possible contents of STARTUP.NCF

  • disk drivers
  • name space commands
  • SET commands

Possible contents of AUTOEXEC.NCF

  • time information
  • Bindery context information
  • server name
  • LAN driver
  • commands to bind IPX and/or IP to the LAN driver
  • more SET commands
  • if you are very lucky, comments documenting the settings set by your predecessor

A list of commands from the previous version of this text is useful and worth studying. Each command provides a special function to the server that may be loaded automatically in the AUTOEXEC.NCF file.

  • LOAD REMOTE password - this allows the server to be managed remotely via SPX protocol
  • SEARCH ADD parameter - this adds a path parameter to the the PATH variable, telling the server another place to look for NLM files that you tell it to run
  • SECURE CONSOLE - this also removes DOS from RAM, etc., as well as keeping the server from loading any other NLMs until you say so.
  • LOAD MONITOR - this will load the primary system tool used on the server

Use Server Script Files to Automate Console Commands

Server batch files are like DOS batch files. In essence, the server configuration files discussed above are batch files, except that they are run only when the server starts. Most batch files can be run at will, if they are useful.

If you enter a series of commands on your server frequently, and wish to run them the same way each time they are run, a batch file is a good device. The commands can be saved in an NCF file, which can be called from the console or from another NCF file.


Determine Requirements for Java Application Support on the NetWare Server

The next section of the text discusses Java, which is a programming language. Several of the utilities in NetWare 5 and 5.1 are written in Java.  Normally, you would not care what language a program was written in, but Java is special in that you must have support for it in your operating system, or programs written in it will not run.

Some requirements for a server to support Java programs:

  • at least 64 MB of RAM
  • a PS/2 or Serial mouse (you will REALLY want one)
  • an ISA, EISA or PCI video card, that supports VESA drivers and Super VGA resolutions. Note: Novell recommends a PCI card that supports VESA 1.2 or later. The trick is that you will need to run at 800 by 600 resolution (or greater). If you can't, you will not be able to see portions of some GUI screens. Not fun.

If you should lose control in the GUI interface, toggle to the System Console screen, and enter the command VESA_RSP. This will run an NCF file that will reset mouse and video drivers. This can come in handy if you have to change mice, or if you have chosen a video resolution that is not supported by your card and driver.

Java programs for the server can come in two types:

  • Java classes - these are compiled programs; fully functional applications
  • Java applets - these are smaller programs that must run in a browser. The browser must support Java. Applets are stored in HTML documents.

In addition, both types of programs require that the computer running the application (the server) be running support for the Java language.  The program that supports Java on any computer is its version of the Java Virtual Machine. This will be a different program for each different operating system, because it acts as an interface between the Java program and the actual operating system.

To load the Java Virtual Machine on the NetWare server, enter "JAVA" at the console prompt.

To run a Java class, enter "JAVA class" ("class" would include the path to the actual Java class you want to run).

To run a Java Applet, you should be running the Java Virtual Machine already, which supports the command "APPLET".  The command may be used two ways:

  • APPLET HTTP:// URL
  • APPLET filename_of_HTML_document

NetWare 5.1 includes a Graphic User Interface (GUI) for the server. Support for it must be loaded, and this can be done two ways:

  • type the command "STARTX.NCF" - this will run a server batch file that loads everything needed: drivers, JAVA.NLM, and the GUI. This file is typically called from STARTUP.NCF.
  • load a Java class or applet that needs the GUI - STARTX.NCF will be run automatically

Define and Configure the NetWare GUI

The NetWare GUI is meant to be the future of the server interface. From it, you can presently install more NetWare products, configure screen and keyboard settings, change backgrounds (wallpaper), and add Java programs and applets to the GUI.

An addition to the GUI is the ConsoleOne utility, which can be started two ways:

  • from the GUI, click the Novell button, and select ConsoleOne from the menu that appears
  • from the Server Console, enter the command "C1START.NCF", which will run a batch file that will run ConsoleOne

Identify Administrative Tasks Performed with ConsoleOne

ConsoleOne is a graphic interface that looks like XWindows on a UNIX server. It makes some of the features of NetWare Administrator available to you on the server itself. More features are available in each version.  Presently, you can edit server configuration files, access local and remote server consoles and manage the local server and file system. You can manage NDS for large networks more effectively than with NetWare Administrator. You can create all NDS container types, aliases, and most leaf types.

ConsoleOne has a different look, compared to NetWare Administrator, but the basic idea of browsing on the left screen and selecting objects on the right screen is maintained. Detail screens for objects appear when you right-click an object and select Properties..


Identify How to Remotely Manage the Console

Remote access to the console means accessing it from a workstation. This can be done two ways:

  • RConsoleJ - graphic interface, works with Java and IP; run SYS:PUBLIC\RCONJ.EXE on the workstation and RCONAG6.NLM on the server
  • RCONSOLE.EXE - character interface, runs on the workstation, works with SPX or an asynchronous modem. Requires server to run REMOTE.NLM and either:
    • RSPX.NLM (for an SPX connection) or
    • RS232.NLM and AIO.NLM (for a modem connection)

The following list of key commands is a good reference for the controls available in Remote Console:
View the Available Options menu Alt+F1
Quit the Remote Console Session Alt+F2
Move forward through server console screens Alt+F3
Move backward through server console screens Alt+F4
Display the network and workstation address Alt+F5
Resume the remote session with the server Esc


Define Methods for Protecting your Server

Four suggestions about server security:

  • Lock up the server - If the door to the server room is locked, only people with a key can get at it. Do not put a printer in the server room and give users access to it.
  • SECURE CONSOLE- this is a password protected command which keeps people who do not know the password from changing the server (The password should not be your login password.)
  • SCRSAVER.NLM - this is a password protected screen saver for the server
  • Use a password on remote console - both versions of the remote console program require you to supply a password.