Next Page

Banyan Server Operations Guide

About This Book

Note: Most of the information in this book is relevant only to native VINES servers. However, Chapter 15 (Managing and Setting Time) contains information relevant to StreetTalk for Windows NT servers.

General Operations

Managing Backups

Restoring and Rebuilding Data




Chapter 1 - Starting Up and Shutting Down the Server

Overview of Rebooting and Shutting Down a Server

Caution: Always shut down services before you power off or reboot the server. An abrupt power off or reboot can result in inconsistent data.

Notifying Users About a Server Shutdown

To Send a Message to Users

Figure 1-1. Operator Menu Screen

1. From the Operator Menu, select Send Messages to Users. The Message Courier screen appears and you are prompted to enter a message destination.

Figure 1-2. Message Courier Screen

2. Indicate who you want to send the message to by entering one of the following:

ALL - Broadcasts a message to all users within one hop. This broadcast does not reach users across a WAN link.

StreetTalk name or nickname of an individual or list - Sends a message to the user or list specified.

StreetTalk wildcard - Sends a message to all users in a group or organization, such as *@Mkt@XYZCorp or *@*@XYZCorp.

Note: When sending a message to a StreetTalk name or wildcard, you may not be able to reach all of the intended users. SEND transmits to a maximum of 400 StreetTalk destinations. If the StreetTalk group or list that you specify includes more than 400 destinations, the message is not sent. No limit exists for the number of destinations reached when a message is sent to ALL. Also, if you send a message to a StreetTalk list and the list includes StreetTalk groups, users belonging to the group do not receive the message.

The StreetTalk name you enter must be in the following format:


You are prompted to enter a message.

3. Enter a message and press ENTER. For example:

Server1 is shutting down at 5PM today.

The message is sent to all specified users, except for those who have disabled incoming messages at their workstations. The message prompt appears again.

4. To send another message, do one of the following:

- To send another message to the same users, repeat step 3.

- To send a message to other users, press ENTER once and repeat step 2.

5. To exit the Message Courier screen, press ENTER two times. The Operator Menu appears.

You are now ready to shut down the server.

To Shut Down and Reboot a Server

1. From the Operator Menu, select Shut Down Server Software.

Figure 1-3. Operator Menu Screen

If the console is locked, you are prompted for the console password. Enter a password and press ENTER.

You are prompted to confirm the shutdown.

2. Enter Y. The Shut Down Menu appears.

Figure 1-4. Shut Down Menu Screen

3. Select one of the following:

- To reboot the server automatically, select Shut down services and do AUTOMATIC REBOOT.

- To reboot the server manually, select Shut down services and await MANUAL POWEROFF/REBOOT.

You are prompted to notify network users of the shutdown.

4. Enter Y to send users three warnings that the server is shutting down.

A message appears, confirming that users are receiving notice of the shutdown. Users receive warning messages every 30 seconds until shutdown. After one minute, a message informs you that the server is shutting down.

5. If you select automatic or manual reboot, one of the following occurs:

- If you are rebooting the server automatically, following shutdown, the initialization screens and then the Service Monitor screen appear.

- If you are rebooting the server manually, when prompted, turn the power switch OFF.

6. When you are ready to reboot the server, turn the power switch ON.

The power-on LED lights up when you start the server. Server initialization messages appear at the console, and the server runs system memory tests and displays information about the disks or devices it locates.

Rebooting From a Workstation

Note: You can reboot the server only from a VINES client workstation.

To Reboot a Server from a Workstation

1. At the DOS or OS/2 command prompt, enter:

REBOOT servername

where servername is the name of the server that you want to reboot.

The Reboot menu appears. The name of the server appears on the top right of the screen.

Figure 1-5. Reboot Menu Screen

2. Select Schedule a reboot. You are prompted to enter a time to reboot the server.

Figure 1-6. Scheduling a Reboot Screen

3. Do one of the following:

- To reboot the server now, press ENTER. You are prompted to press any key to reboot the server.

- To reboot the server at a later time, enter the time in HH:MM format and press ENTER. The time of the scheduled reboot appears at the bottom of the screen. The server reboots approximately one minute after the scheduled time.

Before the server reboots, users receive a series of warnings, indicating that the server is about to reboot.

Canceling a Scheduled Reboot

To Cancel a Scheduled Reboot

1. At the DOS or OS/2 command prompt, enter

REBOOT servername

where servername is the name of the server that you want to reboot.

The Reboot menu appears.

2. Select Abort a Pending Reboot. The screen displays the scheduled time of the reboot and the time at which you cancelled the reboot.

Displaying the Reboot Status Log

To Display the Reboot Status Log

1. At the DOS or OS/2 command prompt, enter:

REBOOT servername

where servername is the name of the server that you want to reboot.

The Reboot menu appears.

2. Select Show the status log.

The reboot log contains the following types of status messages:

- The time of the next scheduled reboot

- The scheduled and actual time of any completed reboot

Note: You can use REBOOT to reboot servers in different time zones. If your DOS workstation is not in the same time zone as the server you want to reboot, be sure to adjust the scheduled time accordingly. For example, to reboot a server in California at midnight (24:00 PDT) from a workstation on the same WAN in New York, add three hours and schedule the reboot for 03:00 EDT.

Avoiding Conflicts Between Reboot and Patch Schedules

Server Initialization

Disk and File System Checks

===== vfsck log =====
vfsck -y
Fri May 24 15:16:40 1996
vfs shut down normally

===== vfsck log =====
vfsck -y
Tue May 28 18:26:10 1996
vfs didn shut down normally - vfsck required
current_fid too low: current_fid = 3393 max fid in fid file = 3410
vfsck finished fixing at Tue May 28 18:42:21 1996

vfsck failed to run!

Consult the Server Operating System log from the SYSTEM MAINTENANCE Menu
after the server is up, to find out why.

You must fix the problem and reboot before continuing to use the server,
otherwise inconsistent file system information may result!

Press <RETURN> to continue booting.

Verifying the File System Type

mount -f S51K /dev/adusr/diskn

To Verify the File System Type

1. Reboot the server.

2. After the server is running, examine the following log:


where servername is the name of the server. Refer to "Generating Server Log Reports from the Console" in Chapter 13 for instructions on how to view the server logs.

For each disk installed, the following line appears:

File Volume Name: diskn Type Sx

where n = the number of the disk and x = the file system type.

The Service Monitor

Service Monitor waiting for system initialization...

Note: Establishing a connection to StreetTalk takes time following any new installation, upgrade, reloading of the system software, or full restoration.



Figure 1-7. Service Monitor Screen

Displaying Service Status

To Display the Status of a Service

The server is not currently in operation.

Table 1-1. Service Status

Displaying Information About a Server's Disks and Printer Ports

To Display Information About Server Resources from a Workstation

From StreetTalk Explorer

1. Click on the server in the left pane.

2. Right-click the server in the right pane and select Properties.

3. Select the Resources tab. See step 2 below for an explanation of the information.

From the DOS Prompt

1. At the DOS prompt, enter:

OPERATE servername

where servername is the name of your server. The Operate A Server menu appears.

Figure 1-8. Operate A Server Menu Screen

2. Select SHOW Server Resources. The Server Resources screen appears and displays the following information:

Figure 1-9. Server Resources Screen

- Number of disks, or file systems, on the server

- Number of 1024-byte blocks available on each disk

- Number of disk blocks in use

- Percentage of total blocks in use

- Number and type of printer ports available on the server

- Status (Used or Unused) of each printer port

Displaying Information About Disk Use from the Server Console

Table 1-2. Statistics on the Server Console Disk Use Screen

To Display Information About Server Disk Usage from the Server Console

Figure 1-10. Operator Menu Screen

1. From the Operator Menu, select Run Network Management. The Available Servers screen appears.

2. Select the name of the server from the list of available servers.

3. Press F10. The Network Summary screen appears.

Figure 1-11. Network Summary Screen

4. Select SHOW disk usage statistics. The cursor moves to the server name in the lower half of the screen.

5. Press ENTER. The Disk Use screen appears. The screen shows a table with each row representing the activity for a single disk volume. The names of the disks are in the left-most column. The item entries are named by headings in the first row.

Figure 1-12. Disk Use Screen

6. Press ESC three times when you are finished viewing the information. The Operator Menu appears.

Reboot Problems

Service Monitor waiting for system initialization...

Initialization problems

To Recover from Initialization Problems

1. Check that the power cord and console cable are connected securely.

2. Check that you followed instructions properly in making any changes to the server.

3. Reboot the server.

4. If the server does not start, refer to the Server Installation Guide for further information, or contact your Banyan service representative for assistance.

Service Monitor Problems

Service Monitor timed out waiting for StreetTalk. Check the StreetTalk and Server Service logs for errors.

Press RETURN to continue.

Unable to make connection with StreetTalk. Check the Server Service and StreetTalk logs for errors.

Press RETURN to continue.

Top Of PageNext Page