Del Mar College
CIS 306 - Managing NOVELL® Networks
Instructor: Michael P. HarrisIntranetWare 4.11
![]()
![]()
IntranetWare Administration Guide
5. Managing the Network and Servers
Introduction
Managing the network includes using NetWareŽ maintenance tools to monitor server activity, customize the network, and maintain servers and volumes.
NOTE: Managing and maintaining the IntranetWareTM for Small Business network requires some knowledge of NetWare. You may also have to use NetWare Administrator and the server console utilities (some of which are listed and described in this chapter).
This section provides basic information about and commands for managing a network server. If your environment requires a customized solution, however, refer to "Maintaining the NetWare Server" in Supervising the Network, "SERVER" in Utilities Reference , or "Server" in Concepts (NetWare 4.11 online documentation).
Accessing the Server
The server can be accessed two ways:
- From the server console. Servers are controlled and managed at the server console using server commands. Once the server is installed, these commands assist the network administrator in performing various tasks required to manage the network. See Table 5-1 for a list of the most common tasks and commands that can be used at the server console to manage the server.
- At a workstation. If it is more convenient for you to manage the server from your workstation rather than the server console, you can use RCONSOLE for most management tasks.
During a remote console session, you can load and unload modules, execute console commands, and copy files to network directories. However for security reasons, you cannot transfer files from the server.
To access a particular server, type
RCONSOLE servername
where servername specifies the name of the server or Internetwork Packet ExchangeTM (IPXTM ) address you want to reach through a direct connection. See "Using Remote Console to Manage a Server" in Supervising the Network (NetWare 4.11 online documentation).NOTE: RCONSOLE will not allow remote access to a server if the network supervisor has not enabled remote connections using the REMOTE command. See "REMOTE" in Utilities Reference (NetWare 4.11 online documentation).
Using Help
If you are at the server console prompt and are unsure how to use a command, type the command name and add the /? option to access help. For example, for help with the SET command, type SET /? .
Server Utilities
Many Small Business utilities can be used at the server console or by using RCONSOLE to configure your server. The utilities most often used by network administrators are these:
- INSTALL - Maintenance Mode. This utility is best used to install and upgrade, modify your server configuration, or perform some maintenance operations.
- MONITOR. This utility is best used to view server activity, lock the console, access server RAM and CPU utilization, and set server parameters. Figure 5-1 shows the main screen.
Figure 5-1. MONITOR Main Screen
![]()
- SERVMAN. This utility is best used to view and configure system parameters; change parameter values in AUTOEXEC.NCF, STARTUP.NCF, and TIMESYNC.CFG files; and view volume, network, device, and disk partition information. Figure 5-2 shows the SERVMAN main screen.
Figure 5-2. SERVMAN Main Screen
![]()
- SET. This utility is best used to view and configure operating system parameters.
See "INSTALL," "MONITOR," "SET," or "SERVMAN" in Utilities Reference (NetWare 4.11 online documentation) for more information on these utilities.
Common Server Utilities
Table 5-1 briefly lists commands that are often used to manage the network. See Utilities Reference (NetWare 4.11 online documentation) for complete information on these and other NetWare utilities.
See "Utilities" in Utilities Reference (NetWare 4.11 online documentation) for complete information on these and other NetWare utilities
Advanced Server Utilities
Table 5-2 briefly lists some of the available advanced commands used to maintain and repair NovellŽ Directory ServicesTM (NDSTM ) and the network.
See "Utilities" in Utilities Reference (NetWare 4.11 online documentation) for complete information on these and other advanced NetWare commands.
Selected Server Tasks
The following sections explain frequently used server tasks you may need to perform. Several of the tasks list cross references to procedures in the NetWare 4.11 online documentation (included on the Small Business CD-ROM).
Common Server Tasks
Table 5-3 lists tasks often used by network administrators to maintain and repair the server and network and the commands used to perform these tasks.
Bind/Unbind a Network Board
Binding is the process of assigning a communications protocol to network boards and local area network (LAN) drivers.
When you add a network board to the server, you must bind the driver of the network board to a communications protocol; otherwise, the network board cannot process information on the network. Initially, INSTALL binds the board to the appropriate protocol and adds the BIND command to the AUTOEXEC.NCF file so that binding is in effect any time the server is booted. However, you may need to bind and unbind at the command line during maintenance procedures.
For more information on binding and unbinding network boards, see "Loading and Binding LAN Drivers" in Supervising the Network (NetWare 4.11 online documentation).
Install NetWare Loadable Modules
A NetWare Loadable Module (NLM) is a program you can load and unload from the server's memory while the server is running (some NLM programs are loaded automatically because other NLM programs cannot run without them). An example of an NLM program is MONITOR.NLM, which allows you to view activities taking place on all the servers in the NDS tree.
When loaded, an NLM program is dynamically linked to the operating system, and the server allocates a portion of memory to it. The amount of memory an NLM program uses depends on the task it performs.
The NLM uses the memory to perform a task, and then returns control of the memory to the operating system when the NLM is unloaded.
You load and unload NLM programs at the console prompt.
- To load an NLM, type the following command:
LOAD NLM name <Enter >
where NLM name is the name of the NLM. For example, if you want to load MONITOR.NLM, type the following:
LOAD MONITOR <Enter >- To unload an NLM, type the following command:
UNLOAD NLM name <Enter >
where NLM name is the name of the NLM. For example, if you want to unload MONITOR.NLM, type the following:
UNLOAD MONITOR <Enter >For more information on loading and unloading NLMs, see "LOAD" and "UNLOAD" in Utilities Reference (NetWare 4.11 online documentation).
Edit Server Boot Files
The server contains two server boot files that you can edit to customize your system. The two files are
- AUTOEXEC.NCF
- STARTUP.NCF
AUTOEXEC.NCF loads NLMs and configures the NetWare operating system. STARTUP.NCF loads drivers for the server's hardware devices and some SET parameters (which are used to enhance the network's performance).
To edit AUTOEXEC.NCF or STARTUP.NCF do the following.
Procedure
At the console prompt type
LOAD INSTALL <Enter >
From the Installation Options menu, choose NCF Files Options.
From the NCF Files Options menu, choose Edit AUTOEXEC.NCF File or Edit STARTUP.NCF File.
Make the desired changes.
To exit and save the file, press < F10 > , choose Yes, then press < Alt > < F10 > .
Type the following at the console prompt:
DOWN <Enter >
EXIT <Enter >
Activate the changes you have made to the files by restarting the server (turn the computer off, then back on; or press < Ctrl > < Alt > < Delete > at the same time).
Bring Down and Restart a Server
Occasionally, you may need to bring down a server to perform maintenance work or to upgrade hardware. When you bring down a server, you remove the server from the network, thus preventing users from accessing the server and any data or resources assigned to it.
To bring down a server, do the following.
Procedure
At the console prompt, send a message to all users informing them they should close all files and log out of the server.
For example, at the console prompt type
SEND "Please close files and log out from server server name." <Enter >
SEND "Going down in 5 minutes." <Enter >
where server name is the name of the server you are going to bring down.
To bring the server down, type
DOWN <Enter>
If any files are open, the console displays a list of the files, the users who have the files open, and the workstation connection numbers.
You may need to go to the workstations that have open files and close the files for the users if the workstations are unattended.
Type
EXIT <Enter>
To bring up the server, type the following at the DOS prompt:
CD\NWSERVER <Enter >
SERVER <Enter >
When you bring up a server, the server and its data and resources are once again available to users.
View the Server Configuration
You can view the hardware and software configuration of a server using the CONFIG command. At the console prompt, type CONFIG , then press <Enter >.
The console displays information concerning how the server (both hardware and software) is set up.
List Servers on the Network
You can view a list of servers on the network using the DISPLAY SERVERS command. At the console prompt, type DISPLAY SERVERS , then press <Enter >.
Use SET Commands
SET commands allow you to enhance the performance of the network by setting operating system parameters. For example, the File Delete Wait Time SET command allows you to define the amount of time that will pass between the time when a user chooses to delete a file and when the file is actually deleted from the system. This could be a useful parameter if you have users who consistently delete files by mistake.
For more information on using SET commands, see "SET" in Utilities Reference (NetWare 4.11 online documentation).
To set a system parameter using the SET command, do the following.
Procedure
At the console prompt, type
SET <Enter>
A list of categories displays.
Type the number for the desired category, then press < Enter > .
Type the name of the desired parameter, then press <Enter > .
If prompted, type necessary information, then press <Enter> .
Monitor and Resolve Communications Problems
Problems that occur with networking can originate in a myriad of places: corrupted hardware or software, bad links, not enough memory, and so on.
This section briefly explains ways to optimize or make communication work among all of your network resources.
Maintain Network Hardware
A common cause of network problems is faulty hardware. The following topics address some of these potential problems.
Check Available Disk Space
To find out how much disk space you have, do the following.
Procedure
At the workstation, type
NDIR volume: /VOL <Enter>
Statistics for the volume you selected appear on the screen.
Write down the percentage shown for Space remaining on volume.
Repeat this procedure weekly for each volume.
Tracking this percentage over time helps you predict when a volume may run out of space. See " NDIR" inUtilities Reference (NetWare 4.11 online documentation) for more information.
Add Hard Disks
This procedure tells you how to add a new IDE hard disk only. See "Adding a Hard Disk to the NetWare Server ," Replacing a Hard Disk" in Supervising the Network (NetWare 4.11 online documentation) for more information.
Prerequisites
- All users logged out of the server
- Access to the hard disk manufacturer's documentation
- Access to the computer manufacturer's documentation
Procedure
Bring the server down by typing
DOWN <Enter >
EXIT <Enter>
Turn off the power to the server.
Install and cable the hard disk.
Make sure the jumpers are configured so that one disk is the master and one the slave.
Configure the computer to recognize the new disk.
Reboot the server.
At the server console prompt, type
LOAD INSTALL <Enter >
Use INSTALL to create a new NetWare disk partition.
If you need help, see "Creating NetWare Disk Partitions" in Supervising the Network (NetWare 4.11 online documentation) for more information.
Create a new volume or designate the disk partition as a new segment of an existing volume.
If you need help, see "Create a Volume" or "Adding a Segment to an Existing Volume " in Supervising the Network (NetWare 4.11 online documentation).
Check for Hard Disk Errors
Check for disk errors regularly. Tracking new errors can help you predict and prevent problems that would otherwise result in a failed file system and loss of data. You can then replace the disk before it causes data loss.
Procedure
At the server console prompt, type
LOAD MONITOR <Enter >
From the Available Options menu, choose Disk Information.
From the System Disk Drives menu, choose the disk drive you want to check.
Write down the number of redirected blocks and the number of redirection blocks shown in the upper window of the screen.
When the system cannot reliably write a block of data to the disk, it marks the disk block as bad and writes the data to the Hot Fix Redirection Area.
The Redirected Blocks count shown in MONITOR is the number of blocks redirected since the server was installed.
The Redirection Blocks count is the number of blocks assigned as the Hot Fix Redirection Area.
Evaluate the statistics and proceed according to the following steps.
Compare the current number of redirected blocks to the number you recorded the last time you checked this number.
If the number is the same as the previously noted number, you do not need to take any corrective action.
If the number has increased significantly, or if the number is over half the number of redirection blocks, continue to Step 5b.
If the number has slightly increased over the previous number, monitor the server closely.
Send a message to all users to close files and log out.
Back up the server data and bring down the server.
Troubleshoot the disk drive, controller, and host bus adapter using the hardware documentation.
View the Server Error Log
The server error log is a text file called SYS$LOG.ERR in the server's SYS_servername:SYSTEM directory. All system messages and alerts that appear on the server console are recorded in the SYS$LOG.ERR file.
You can view or clear the server error log file using NETADMIN or FILER. See "Viewing the Server Error Log " in Supervising the Network of the NetWare 4.11 online documentation.
Monitor and Maintain Network Data
On all NDS servers, volume SYS: contains the Novell Directory Services database for that server. The database files are stored in a hidden directory.
If volume SYS: runs out of space, some software may shut down.
See Chapter 4, " Maintaining NetWare 4 Networks" in Supervising the Network (NetWare 4.11 online documentation) for information on how to prevent this from occurring.
Monitor Novell Directory Services
This section discusses how to repair, remove, and re-install NDS.
Repair Novell Directory Services
The DSREPAIR utility is used to repair problems with NDS. You must run DSREPAIR on each server that contains the corrupted NDS database.
Before you start this procedure, read "Repairing the NetWare Directory Database" in Supervising the Network (NetWare 4.11 online documentation) for complete information.
This procedure runs an automatic unattended full repair of the Directory database.
Prerequisites
- Have access to the server console or establish an RCONSOLE session with the server.
- Make sure all servers in the tree use the same time source. See "Check Time Synchronization."
- Log in as ADMIN.
Procedure
At the server console, type
LOAD DSREPAIR < Enter>If you have placed DSREPAIR in a directory other than SYS: SYSTEM, you must enter the full path to the utility.
Choose Full Unattended Repair.
A window displays the repairs in process. A message window appears at the end of the process that informs you of the repair status, the total number of errors corrected, and the amount of time used to complete the repair operation.
Press <Enter> to display the error log file.
The error log contains a full text editor. You can modify the error log if preferred.
Check Time Synchronization
Use this procedure on the server before or after performing a repair. It allows you to contact all servers within this server's local database to request information about Novell Directory Services and time synchronization.
All servers in the Directory tree are contacted.
IMPORTANT: Time synchronization is very important to Novell Directory Services. All servers in a tree must be synchronized to the same time source. If they are not, data collision will occur when some objects are synchronized.
Prerequisites
- Access to the server console or an established RCONSOLE session with the server
- All servers in the tree use the same time source
Procedure
At the server console prompt, load the module by typing
LOAD DSREPAIR <Enter>If you have placed DSREPAIR in a directory other than SYS: SYSTEM, you must enter the full path to the utility.
The utility locks the database.
Choose Time Synchronization.
The "Collecting Time Synchronization and Server Status" screen appears. A window is available to observe the operations in process.
Following the operation, the DSREPAIR log is displayed within a full text editor. You can annotate or modify the DSREPAIR log as needed.
The DSREPAIR log contains the following:
Field Indicates Server Name All of the server names known to the local Directory database. If this server contains a replica of the root partition, then this list contains all the servers in the tree.
Version The version of DS.NLM running on the server. Replica Depth The replica depth field reports "-1" if no replicas are stored on the server or "0" if the server contains a replica of the root partition. A positive integer indicates how many objects deep from the root the first replica is on that server.
Time Source The time server type. This information helps you determine if time synchronization for all the trees in the server is configured properly.
All servers in a tree must be using the same time source.
For example, if there are two Single time servers then you know that all servers in the tree cannot be polling the same time source and there is a configuration problem.Time in Sync The local time synchronization status on each server. The status should be Yes. If the status is No, then the server is not able to contact its time source. Time +/-- The difference in time between the local server and the selected server in the list. All servers should be within one second of each other; if they are not, they have not been configured properly.
This field reports up to 999 minutes and 59 seconds (which is approximately 16 hours and 30 minutes) in the form minutes:seconds. If the time difference is greater than 16 hours and 30 minutes, then the maximum value is displayed as --999: 59.
If the difference in time is more than a few minutes, it might indicate that the servers are using different time source servers.
Remove Novell Directory Services
If you experience problems (such as the network users cannot log in, you cannot map a drive, or the Directory tree is behaving erratically), you may be having NDS problems.
Before you decide to remove NDS, check all of your hardware components and LAN drivers to see if they could be causing the problem. You can also use the DSTRACE utility which prints NDS error messages to the screen. Remove NDS only as a last resort. See Removing NetWare Directory Services from a Server" in Supervising the Network (NetWare 4.11 online documentation) for more information.
Prerequisites
- Access to the server console.
- The Supervisor object right to the NetWare Server object and its associated Volume objects.
- Make sure all of the server's volumes are mounted. Volume objects will not be removed from the Directory database if the volume is not mounted.
Procedure
At the server console, type
LOAD INSTALL < Enter>
From the Installation Options menu, select Directory Options (Install NetWare Directory Services) and press < Enter> .
From the Directory Services Options menu, select Remove Directory Services from this Server and press <Enter> .
At the confirmation prompt, choose Yes.
The "Directory Services Login/Authentication" screen appears.
Type the password for User ADMIN in the Password field and press <Enter> .
After you enter the password, the server's mounted volumes are downgraded and a message displays the number of volumes affected. Then the system checks for Directory connections to other servers.
(Conditional) If this server contains a master replica, you must designate another server to hold it. Choose one of the following and press <Enter> :
- Do it automatically.
INSTALL finds the first server with a replica of this partition and changes its type to "master."- Designate the server yourself.
Highlight the server where you want the master replica located.
Press <F10> to save and continue.A message notifies you that the master replica has been moved.
To continue, press <Enter> .
INSTALL removes NDS and deletes the NetWare Server object and Volume objects associated with it from the Directory database.
NOTE: If a Directory link is down (such as another server containing objects from this server), you must use NDS Manager to delete the Server and Volume objects from the Directory database. See "NDS Manager " in Utilities Reference or " Managing the NetWare Directory Tree" in Supervising the Network (NetWare 4.11 online documentation) for more information on NDS Manager.
To exit INSTALL, press <Esc> .
Re-install Novell Directory Services
This procedure re-installs Novell Directory Services on a server. It doesn't preserve the trustee assignments from the first time NDS was installed on the server; you must make those assignments again. Use either the Novell Easy Administration Tool (NEAT) or NetWare Administrator to create new assignments.
Prerequisites
- Access to the server console
- The Supervisor object right to the container you want to install the server in
Procedure
At the server console, type
LOAD INSTALL < Enter>
From the Installation Options menu, select Directory Options (Install NetWare Directory Services) and press < Enter> .
From the Directory Services Options menu, select Install Directory Services onto this Server and press <Enter > .
Install Novell Directory Services on the server.
To exit INSTALL, press <Esc> .
Back Up and Restore NDS to New Hardware
To understand how backup and restore is used with Small Business, see "Backing Up and Restoring Data" in "Check Time Synchronization."Supervising the Network (NetWare 4.11 online documentation) for information.
Manage Volumes
This section explains how to create, delete, rename, and mount volumes.
Create a Volume
You can create a new volume if you add a new hard disk to your server or you need a volume with more space. If you add a hard disk, you must first create a NetWare partition using INSTALL, then create the volume and mount it so it is recognized to the network. See "Maintaining Volumes" in Supervising the Network (NetWare 4.11 online documentation) for more information.
You can create a new volume on any hard disk that has a NetWare partition and an existing SYS: volume.
To create a new volume, do the following.
Procedure
At the server console, type
LOAD INSTALL <Enter >
From the Installation Options menu, choose Volume Options.
Press < Insert > .
Select any existing free space and press < Enter > .
By default, the new volume takes up all remaining free space in the partition. If no free space is available, you must add a new hard disk.
Type a new volume name in the box provided and press < Enter > .
The newly created volume appears in the Volume Disk Segment List.
If you want the new volume to use all the free disk space, skip to Step 7. If not, continue with Step 6.
If you don't want the new volume to use all the free space, do the following:
Select the volume you just created and press < Enter > .
Enter a new volume size and press < Enter > .
Press < Esc > and save the settings.
To assign the free space you just created to another volume, repeat Step 4 and Step 5.
Skip to Step 9.
If you want the new volume to use all the free disk space, either press < Esc > to continue with other volume tasks or press < F10 > to save volume information to disk.
From the menu, choose Mount/Dismount an Existing Volume .
Choose Mount.
Mount and Dismount Volumes
Mount a volume to make information available to network users. You can mount or dismount volumes when the server is running. Rarely used volumes should be dismounted because they use memory.
Use INSTALL to mount or dismount a volume.
Procedure
At the server console, type
LOAD INSTALL <Enter >
Select the volume you want to mount or dismount and press < Enter >.
Press < Insert > .
Highlight the Status field using the arrow keys.
The volume status is displayed.
If the status is New, now mounted, press < Esc > and < F10 > to save the volume changes to disk before the volume can be mounted.
Press < Enter > to display a menu of available actions.
Depending on your preference, select either Mount or Dismount and press <Enter> .
Mount a CD-ROM as a Volume
Mounting a CD-ROM as a volume allows you to read the contents from the CD-ROM; for example, you can access the online documentation from CD-ROM by mounting a volume to that CD-ROM.
To mount a CD-ROM as a volume, do the following.
Procedure
Insert the CD-ROM into the CD-ROM drive.
At the server console, type
LOAD CDROM <Enter >
Type
CD MOUNT volume name
For example, to mount the documentation CD-ROM, type
CD MOUNT IWSB_DOC
where IWSB_DOC is the name of the volume on the CD-ROM.
If you don't know the volume name, type
CD DEVICE LIST
A list appears with numbers associated with all the devices on your network. Determine which number is the volume number and enter it in the volume name command above.
At the server console, type
LOAD INSTALL <Enter >
From the Installation Options menu, choose Product Options.
Choose View/Configure/Remove Installed Products.
Choose Install to install a new product.
Supply a path to the installation software.
Delete a Volume
You can delete a volume if users are no longer using that volume and it is taking up valuable disk space, or if you want to replace it with a larger volume. When you delete the volume, all data is destroyed.
To delete a full volume, do the following.
Prerequisites
- Back up the data stored on the volume you want to delete
- Dismount the volume you want to delete
Procedure
At the server console, type
LOAD INSTALL <Enter >
From the Installation Options menu, choose Volume Options.
From the list of existing volumes, select the volume you want to delete and press < Delete > .
Press < Enter > to continue.
When the Delete existing volume? prompt appears, select Yes and press < Enter > .
This procedure does not delete Volume objects. Use NetWare Administrator to delete objects.
Rename a Volume
Procedure
Dismount the volume you want to rename.
At the server console, type
LOAD INSTALL <Enter >
From the Installation Options menu, choose Volume Options and press < Enter > .
Select the volume whose name you want to change and press < Insert > .
Highlight the Name field using the arrow keys and press < Enter > .
Backspace to erase the old name; then type in the new name and press < Enter > .
Do not change the name of the SYS: volume. This volume name is mandatory for your network to function properly.
Press < Esc > twice; then press < F10 > to save the volume information.
When prompted, answer Yes to mount the volume with the new name.
To set the Volume object name and context in NDS, you are prompted to log in to the Directory tree.
After you log in, verify that the displayed context and Volume object name are correct.
NOTE: Renaming a volume with INSTALL creates a Volume object with the new name. It does not delete the Volume object with the old name. Use NetWare Administrator to remove the old object.
Manage Memory
One of the most common causes of a slow network is insufficient Random Access Memory (RAM) in the server. The following topics address this problem.
View Server RAM
To determine if your server has enough RAM, do the following.
Procedure
At the server console prompt, type
LOAD MONITOR <Enter >
From the Available Options menu, choose Cache Utilization.
Write down the percentage of Long Term Cache Hits shown in the lower window of the screen.
Tracking cache hits helps you predict when you need more RAM so that you can anticipate serious performance loss.
If the percentage of Long Term Cache Hits consistently falls below 90 percent, add more RAM to the server.
(Optional) To temporarily free up RAM, unload any NLM programs that are not critical.
To exit MONITOR, press < Esc > , or to toggle to the console prompt without exiting MONITOR, press < Alt > < Esc > .
Control Memory Allocation
To limit the amount of memory available for file and directory caching and make more memory available for NLM programs and server processes, do the following.
Procedure
At the server console prompt, load either SERVMAN or MONITOR by typing
LOAD SERVMAN|MONITOR <Enter >
From the Available Options menu, choose Server Parameters.
From the Categories menu, choose File Caching .
Choose Minimum Cache Buffers.
This parameter specifies the minimum amount of memory the system will keep for file caching. Memory above this minimum amount is available for other processes.
Reduce the value of this parameter.
Press < Esc > twice to reach the Categories menu.
From the Categories menu, choose Directory Caching.
Choose Maximum Directory Cache Buffers.
Reduce the value of the Maximum Directory Cache Buffers parameter.
Press < Esc > twice to reach the Update Options menu.
From the Update Options menu, choose Update AUTOEXEC.NCF and STARTUP.NCF Now.
Press < Enter > to update the file.
Reboot the server to free the memory.
Prior Main Index Next This page is maintained by: Michael P. Harris
viking.delmar.edu
Last Updated: Sep 20mpharris@surf.delmar.edu
Copyright © 1998