IBM TotalStorage 201, TotalStorage 226 User Reference Manual

Download

IBM TotalStorage®Network Attached Storage 200 Models 20 1 and 226

User’s Reference

Release 2



GA27-4263-01

Note

Before using this information and the product it supports, be sure to read the general information in “Appendix A. Notices” on page 81.

First Edition (November 2001)

This edition applies to Release 2 of the IBM 5194 TotalStorage Network Attached Storage 200 (Models 201 and 226) (product numbers 5194–201 and 5194–226) and to all subsequent releases and modifications until otherwise indicated in new editions.

Order publications through your IBM representative or the IBM branch office servicing your locality. Publications are not stocked at the address below.

IBM welcomes your comments. A form for reader’s comments is provided at the back of this publication. If the form has been removed, you may address your comments to:

International Business Machines Corporation Design & Information Development Department CGF PO Box 12195 Research Triangle Park, NC 27709–9990 U.S.A.

You can also submit comments on the Web at http://www.ibm.com/networking/support/feedback.nsf/docsoverall. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any

way it believes appropriate without incurring any obligation to you.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corp.

Contents

Figures ...........................vii

Tables ............................ix

About this book ........................xi

Who should read this book.....................xi

Frequently used terms ......................xi

Publications ..........................xi

NAS 200 product library.....................xi

Hardcopy publications shipped with the NAS 200 ...........xii

Related publications ......................xii

Web sites ...........................xii

Chapter 1. Introduction......................1

Roadmap for setting up and configuring the NAS 200 ...........2

Chapter 2. Configuration and administration tools ...........5

Using a keyboard, monitor, and mouse for setup and configuration ......5

Terminal Services and the IBM NAS Administration Console.........8

Connecting to the desktop through Terminal Services ..........8

IBM NAS Administration console ..................9

Determining who is using the network-attached storage .........9

IBM Advanced Appliance Configuration Utility ..............9

IAACU Agent ........................10

IAACU Console........................10

Universal Manageability Services ..................15

System requirements .....................15

Starting UM Services .....................16

Windows 2000 for Network Attached Storage..............17

Telnet Server support ......................18

SNMP support .........................18

Chapter 3. Getting started ....................19

Methods for setting up your NAS 200 ................19

Installing the IBM Advanced Appliance Configuration Utility........19

Accessing Universal Management Services .............20

Initial setup and configuration ...................20

Maintenance (Date and Time) ..................21

Network Setup ........................21

Enabling National Language Support (NLS) .............21

Chapter 4. Storage configuration .................23

ServeRAID configuration .....................23

RAID technology .......................23

Updating the ServeRAID BIOS, firmware, and device drivers .......23

Functionality not needed and not supported in the NAS 200 .......23

Solving ServeRAID problems...................24

Initial storage configuration of the NAS 200 ..............24

Creating arrays and logical drives ..................24

Format the logical drives ....................25

Chapter 5. Completing setup ...................27

Defining Windows users and groups .................27

Defining local Windows users and groups ..............27

Giving storage access to Windows domain users and groups.......28

Defining UNIX users and groups ..................28

Using a local UNIX name space .................29

Using the UNIX name space on an NIS domain............31

Creating shares ........................32

Chapter 6. Additional administrative functions ............35

NAS Backup Assistant ......................35

Restoring using the NT Backup panel ...............35

Persistent Images ........................36

Global Settings ........................37

Volume Settings .......................37

Persistent Images .......................38

Schedules .........................39

Restore Persistent Images ...................39

Disaster Recovery.......................39

Granting user access to persistent image files ............42

PSM notes .........................43

Ethernet adapter teaming .....................44

Intel Ethernet adapter teaming ..................44

Alacritech Ethernet adapter teaming ................45

Chapter 7. Troubleshooting....................47

Engine troubleshooting and diagnostics................47

Engine diagnostic tools overview .................47

Identifying problems using LEDs .................48

Engine troubleshooting charts..................52

Power problems .......................57

Recovering BIOS .......................58

Replacing the battery .....................59

Adapter troubleshooting and diagnostics ...............62

Integrated Ethernet adapter ...................62

Gigabit Ethernet SX adapter ...................66

Troubleshooting the Intel PRO 1000 XT Server adapter .........67

Troubleshooting the Alacritech Quad-Port 10/100 Ethernet adapter .....69

Troubleshooting the ServeRAID-4Lx and 4H .............70

Troubleshooting the Integrated System Management Processor ......74

Troubleshooting the Remote Supervisor Adapter ...........75

Testing SCSI Adapters .....................76

Chapter 8. Using the Recovery and Supplementary CDs ........77

Using the Recovery Enablement Diskette and Recovery CD Set.......77

Using the Supplementary CD ...................79

Appendix A. Notices ......................81

Trademarks ..........................82

Appendix B. Getting help, service, and information ..........83

Service support.........................83

Before you call for service.....................84

Getting customer support and service ................84

Getting help online: www.ibm.com/storage/support/nas .........84

Getting help by telephone ....................85

Appendix C. Engine POST messages................87

iv NAS 200 User’s Reference

Power-on self-test (POST).....................87

POST beep code descriptions ..................87

POST beep codes ......................89

POST error messages .....................92

Event/error logs .......................97

POST diagnostic programs ....................97

Text messages ........................98

Starting the diagnostic programs .................98

Viewing the test log......................100

Diagnostic error message tables .................100

IBM Glossary of Storage Networking Terms.............107

Index ............................125

Contents v

vi NAS 200 User’s Reference

Figures

1. Diagnostics panel LEDs ............................50

2. Boot block jumper location ...........................59

3. Battery removal ...............................60

4. Battery replacement..............................61

viii NAS 200 User’s Reference

Tables

1. Summary of configuration and administration tools for the NAS 200 ............6

2. Standard features of ServeRAID-4Lx and ServeRAID-4H ................23

3. Power-supply LEDS..............................49

4. Descriptions of light-path diagnostics LEDs .....................51

5. Engine troubleshooting symptoms and suggested actions ................52

6. Power error messages.............................57

7. Integrated Ethernet adapter troubleshooting chart ...................63

8. 10/100 PCI Ethernet adapter troubleshooting chart ..................64

9. Gigabit Ethernet SX adapter troubleshooting chart ..................66

10. Intel PRO 1000 XT Server adapter troubleshooting chart ................67

11. Alacritech Quad-Port 10/100 Ethernet adapter LED definitions ..............69

12. ServeRAID-4x problems and actions .......................73

13. Supplementary CD directories ..........................79

14. IBM Web sites for help, services, and information...................83

15. POST beep codes ..............................89

16. POST no-beep codes .............................91

17. POST error messages .............................92

18. Diagnostic error messages...........................100

x NAS 200 User’s Reference

About this book

This book provides information necessary to configure and administer the software for the IBM 5194 TotalStorage Network Attached Storage 200 (Models 201 and

226). Hereafter, this product is referred to as the NAS 200, unless otherwise noted.

Who should read this book

This book is for administrators of the NAS 200. Note that although this product is relatively easy to install, configure, and

administer, the NAS 200 administrator should have experience in at least the following skills, or have access to personnel with experience in the skills:

v Microsoft v Networking and network management v Disk management v General technologies of the product (such as storage, RAID, and so on) v Critical business issues (such as backup, disaster recovery, security)

Frequently used terms

The following terms, used within this document or within the Safety Information, have these specific meanings:

Windows

Term Definition in this document Attention These notices indicate possible damage to programs, devices, or

Caution These notices indicate situations that can be potentially hazardous

Danger These notices indicate situations that can be potentially lethal or

Notes These notices provide important tips, guidance, or advice.

Publications

The latest versions of the following product publications are available in softcopy at:

www.ibm.com/storage/support/nas

NAS 200 product library

The NAS 200 library consists of the following publications: v Hardware Installation Guide GA27-4262

This book describes hardware physical specifications, electrical specifications,

cabling, environmental specifications, and networking specifications for installing

the NAS 200. v User’s Reference GA27-4263

data. An attention notice is placed just before the instruction or situation in which damage could occur.

to you. A caution notice is placed just before descriptions of potentially hazardous procedure steps or situations.

extremely hazardous to you. A danger notice is placed just before descriptions of potentially lethal or extremely hazardous procedure steps or situations.

This book describes such operational and administrative activities as:

– Using the configuration utilities – Administering the NAS 200 – Troubleshooting – Using the Recovery and Supplementary CDs

v Storage Unit Installation and User’s Guide GA27-4259

This book provides instructions for installing and replacing components in your IBM 5194 TotalStorage Network Attached Storage Storage Unit. It also provides information on troubleshooting the unit.

Hardcopy publications shipped with the NAS 200

The following publications are shipped in hardcopy and are also provided in softcopy form at www.ibm.com/storage/support/nas/techdocs:

v Hardware Installation Guide, GA27-4262 v Release Notes

This document provides any changes that were not available at the time this book was produced.

Related publications

The following publications contain additional information about the NAS 200: v IBM 5194 TotalStorage Network Attached Storage 200 (Models 201 and 226)

Hardware Installation Guide GA27–4262

v IBM 5194 TotalStorage Network Attached Storage 200 (Models 201 and 226)

Service Guide GA27–0400

v IBM 5194 TotalStorage Network Attached Storage 200 (Models 201 and 226)

Storage Unit Installation and User’s Guide GA27–4259

v The following information is provided on the Documentation CD that came with

the appliance:

– ServeRAID Adapter Installation and User’s Guide – UM Services User’s Guide

Web sites

The following Web site has additional and up-to-date information about the NAS 200:

v http://www.ibm.com/storage/nas v http://www.ibm.com/storage/support/nas

xii NAS 200 User’s Reference

Chapter 1. Introduction

With the IBM TotalStorage Network Attached Storage (NAS) 200 (5194 Models 201, 226, and EXP), your enterprise will gain scalable, network-attached storage devices that deliver excellent value, state-of-the-art systems management capabilities, and task-optimized operating system technology. These NAS devices provide you with increased performance, storage capacity, and functionality.

These models have been developed for workgroup or department environments with file-serving requirements across Windows and NFS clients, e-business, and small applications. In addition, these devices support Ethernet LAN environments with large or shared end-user workspace storage, remote running of executables, remote user data access, and personal data migration.

These new machines replace the IBM 5194 Models 200, 225, and EXU. Enhancements provided by the new models include:

v Greater granularity in configuring storage size v Double the maximum storage size v More options in configuring Ethernet connections v More options for tape backup

To help provide quick and easy installation, both NAS models have preloaded, preconfigured, pretuned, and pretested operating systems, supporting system management, and RAID management software. You can order the models as a workgroup or department appliance depending on the specific use.

The Workgroup Model (Model 201) features:

v Compact tower configuration v One 1.133 GHz processor; second (dual) processor optional v 512 MB of ECC 133 MHz memory standard v ServeRAID-4Lx, an economical, single-channel RAID controller v One integrated 10/100 Ethernet connection v A dual-channel, 160 MB/s Ultra 160 SCSI controller v Three to six 36.4 GB HDD or 72.8 GB HDD (109.2 GB up to 436.8 GB)

The Departmental Model (Model 226) features:

v Rack-optimized configuration v Two 1.133 GHz processors v 1 GB of ECC 133 MHz memory standard v ServeRAID-4H, a high function, four-channel RAID controller v One integrated 10/100 Ethernet connection v A dual-channel, 160 MB/s Ultra160 SCSI controller v Configurable with three to six 36.4 HDD or three to six 72.8 GB HDD (218.4 GB

up to 436.8 GB) v Expandable up to 3.49 TB using up to three IBM 5194 NAS Storage Unit Model

EXP The preloaded software is based on the Windows Powered OS operating system,

which is very similar to Microsoft software includes:

Windows®2000 Advanced Server. Preloaded

Microsoft Windows 2000 for Network Attached Storage

Enables remote administration of the appliance using a web-based graphical user interface (GUI)

Microsoft Windows Terminal Services

Enables remote administration of the appliance using its Windows desktop

Microsoft Services for UNIX

Provides file access to UNIX and UNIX-based clients and servers via Network File System (NFS) protocol

IBM Director Agent and Universal Manageability Server Extensions

Provides system management support based on industry standards (in conjunction with the IBM Director console application as well as other management software)

IBM Advanced Appliance Configuration Utility agent

Supports management via the IBM Advanced Appliance Configuration Utility console application (supports aggregate web-based management of all of your IBM appliances)

ServeRAID Manager RAID Configuration and Monitoring

Provides configuration tools and RAID management of the ServeRAID-4x adapter

Intel PROSet II

Provides diagnostics for the Intel Ethernet adapters

Alacritech SLICuser

Provides diagnostics for the Alacritech Quad-port Ethernet adapter

Columbia Data Products

Persistent Storage Manager (PSM)

Provides 250 persistent images of customer data and enables full online backup of system with Microsoft’s backup applications

Tivoli

Storage Manager Client

Provides data backup/archive support (in conjunction with Tivoli Storage Manager Server)

Note: Note that both models are generically referred to as NAS 200 in the rest of

this document.

Roadmap for setting up and configuring the NAS 200

The following roadmap presents the requirements and instructions required to set up and configure the NAS 200. Following these directions and referring to the appropriate sections of this book will help you in this task.

Configuration and administration tools (“Chapter 2. Configuration and administration tools” on page 5)

The NAS 200 has several different methods of configuration depending on your environment.

Determine how you will manage the device. You can manage the NAS 200 in “headless” mode or with a keyboard, display, and mouse directly attached to each node. For “headless” management of the NAS 200, you can use one of the following tools: v Terminal Services, for remote configuration and management from

another device on the network

v Universal Manageability Services (UMS) for management through a web

browser

2 NAS 200 User’s Reference

v Windows 2000 for NAS, a Web-based GUI for those not familiar with the

Windows desktop

v IBM Advanced Appliance Configuration Utility (IAACU) for setup and

configuring multiple devices or other appliances on a single network

Having determined how you will manage the NAS 200, you can begin setup and configuration of the device.

Step 1 - Initial network setup (“Chapter 3. Getting started” on page 19)

Configure the NAS 200 to enable access over the network. First, use DHCP or static addressing to set up one network connection. If

you are running with a keyboard, display, and mouse, set up a network connection to access the device. If you are running in a headless environment, you can use one of the following methods: v If DHCP is installed and the IP address requested can be determined,

you can use this method for initial setup, but you should change this address to static later in the configuration.

v If you have multiple appliances or cannot determine the DHCP address,

you can install the IAACU utility to identify appliances and define IP addresses. The tool will also allow you to set static addresses.

Next, complete the steps in “Initial setup and configuration” on page 20.

Step 2 - Define storage (“Chapter 4. Storage configuration” on page 23)

The NAS 200 comes with preconfigured storage spanning the internal hard disk drives:

v A RAID-level 1E array, for the System partition (drive letter will be C:) v A RAID-level 1E array, for the Maintenance partition (drive letter will be

D:)

v A RAID-level 5 array, comprised of the remaining storage. This array

consists of a single logical unit number (LUN), for the Data drive (drive letter will be E). The size of this (LUN) depends on the number and size of hard disk drives that came with your NAS 200.

You can use the preconfigured Data drive, or delete it and configure new storage.

Step 3 - Completing setup (“Chapter 5. Completing setup” on page 27)

Step 4 - Additional functions (“Chapter 6. Additional administrative functions”

on page 35)

At this point you can define users and file shares to the NAS 200, to allow the storage to be accessed by clients and servers on the network.

Additional functions are available for such tasks as backup and creating persistent images. It is recommended that once you complete the setup and configuration procedures, you use the Persistent Storage Manager Disaster Recovery option (“Disaster Recovery” on page 39) or other method to back up the system configuration in the event of a failure.

Chapter 1. Introduction 3

4 NAS 200 User’s Reference

Chapter 2. Configuration and administration tools

Attention

Changing the preloaded software configuration of this product, including

applying or installing unauthorized service packs or updates to preinstalled

software, or installing additional software products that are not included in

either the preloaded image or on the Supplementary CD, may not be

supported and could cause unpredictable results. For updated compatibility

information, please see

http://www.ibm.com/storage/nas

To correct problems with a preloaded software component, back up your user

and system data. Then use the Recovery CD to restore the preloaded

software image.

The NAS 200 appliance comes with the following configuration programs that you can use to configure and administer the appliance:

v Terminal Services Client (page 6 and page 8) v IBM Advanced Appliance Configuration Utility (IAACU, page 7 and page 9) v Universal Manageability Services (page 7 and page 15) v Windows 2000 for Network Attached Storage (page 7 and page 17)

This chapter describes these tools in general and then in detail. In addition to these primary tools, the NAS 200 offers several secondary

administrative tools:

v Telnet Server support (page 18) v Simple Network Management Protocol (SNMP) support (page 18)

There are several ways to setup and administer the NAS 200. Table 1 on page 6 suggests which tool you can use for specific functions, but does not list all options or combinations. The administrator training-level or administrator preferences may determine an alternate approach from that suggested in the table.

Using a keyboard, monitor, and mouse for setup and configuration

It is highly recommended that you directly attach a keyboard, monitor, and mouse to the NAS 200 when:

v Initially setting up and configuring the device v Changing or adding to RAID arrays (for example, adding a new array with

ServeRAID Manager, adding a new RAID controller, or adding a storage

expansion unit) v Troubleshooting the device

Table 1. Summary of configuration and administration tools for the NAS 200

Administration Tool Main functions

Windows Domain Controller (not NAS appliance)

IBM Advanced Appliance Configuration Utility

Users and user groups may be defined and authenticated by a Windows Domain Controller, although this is not required.

Access a headless NAS 200, particularly for the initial setup of the network connectivity. (Alternatively, you can attach a keyboard, mouse, and display to the NAS 200.)

v Set time and date v Configure initial network connectivity parameters v Access to Windows 2000 for NAS GUI, Terminal Services (NAS Desktop),

and Universal Manageability Services

Windows 2000 for NAS GUI Provides ease-of-use administration, but not all the capability of Terminal

Services and IBM NAS Administration

v Configure networking connectivity v Create and format logical drives v Join domains v Setup access permissions and disk quotas for CIFS, NFS, HTTP, FTP,

Novell

NetWare®, and Apple Macintosh shares

v Use Persistent Storage Manager

IBM NAS desktop and IBM NAS Admin program, via a Terminal Services session or a directly connected keyboard and display

Provides in-depth administration of all aspects of NAS 200. Provides all of the Windows 2000 for NAS GUI functions above, plus:

v Use NAS Backup Assistant, or NTBackup and Restore wizard v Learn detailed inventory information about hardware, OS, and so on, using

Universal Manageability Services.

v RAID configuration via ServeRAID Manager

– Create RAID arrays and logical unit numbers (LUNs) – Add additional RAID or storage enclosure after initial purchase

v Diagnose system problems

– Check 10/100 or Gb Ethernet using PROSet II – Check RAID subsystem using ServeRAID Manager – Check Alacritech

Quad-Port Ethernet Adapter using SLICuser

Disaster Recovery Restores a previously saved PSM image of the system partition to a failed

machine. This will restore all configuration information on the machine. You create the recovery boot diskette from the PSM tools in the Windows 2000 for NAS GUI.

Recovery CD Set Reinstalls the software to the original state as shipped on the machine;

however, does not restore configuration information (so configuration changes you applied to the original shipped configuration are lost). You must first boot with the Recovery Enablement Diskette, and then reboot with the Recovery CD. To create the Recovery Enablement Diskette, run \DiskImages\Recovdsk.bat on the Supplementary CD.

IBM NAS AutoRaid Diskette Resets the RAID configuration to its original configuration, or to the

departmental configuration when you change from a workgroup (tower) configuration to a departmental (rack) configuration.

Integrated System Management Processor (ISMP) configuration program

Remote Supervisor Adapter (RSA) configuration program

Configures the ISMP that is integrated on the planar. To create this diskette, run C:\IBM\ASMP\UPDATES\32P0303.EXE on the NAS 200 operating system volume.

Configures the optional RSA. To create this diskette, run C:\IBM\ASMP\UPDATES\33P2474.EXE on the NAS 200 operating system volume.

Terminal Services Client

The Terminal Services Client, when installed on a workstation that is attached to the same network as the NAS 200, enables you to remotely

6 NAS 200 User’s Reference

administer the appliance using the NAS 200 desktop. If you are familiar with administrative tasks using a Windows desktop, you can use Terminal Services.

See “Terminal Services and the IBM NAS Administration Console” on page 8 for more information.

IBM Advanced Appliance Configuration Utility (IAACU)

The IBM Advanced Appliance Configuration Utility (IAACU) aids in setting up and reconfiguring the network configuration on your appliances. The IAACU agent works with the IAACU Console to automatically detect the presence of appliances on the network.

Once the appliance is detected by the IAACU Console, you can use the IAACU to:

v Set up and manage the appliance’s network configuration, including

assigning the IP address, default gateway, network mask, and DNS server to be used by the appliance.

v Start Universal Manageability Services on the appliance, enabling you to

do more advanced systems-management tasks

See “IBM Advanced Appliance Configuration Utility” on page 9 for more information.

Universal Manageability Services

Universal Manageability Services (UM Services) provides point-to-point remote management of client systems through a Web browser window. You can use UM Services to:

v Learn detailed inventory information about your computers, including

operating system, memory, network cards and hardware

v Track your computers with features such as power management, event

log, and system monitor capabilities

v Upwardly integrate with Tivoli Enterprise, Tivoli NetView

Associates Unicenter, Microsoft SMS, and Intel Suite

In addition, you can link to Windows 2000 for Network Attached Storage and Terminal Services from UM Services.

See “Universal Manageability Services” on page 15 for more information.

Windows 2000 for Network Attached Storage

For administrators who are not familiar with the Windows operating systems, the NAS 200 provides a Web-based GUI, Microsoft Windows 2000 for Network Attached Storage (Windows 2000 for NAS). Using Windows 2000 for NAS, you navigate through various administrative task categories by clicking on the appropriate links or buttons, and then selecting a task from that category.

LANDesk Management

, Computer

Detailed information about each of these configuration programs follows.

See “Windows 2000 for Network Attached Storage” on page 17 for more information.

Chapter 2. Configuration and administration tools 7

Terminal Services and the IBM NAS Administration Console

If you are familiar with Windows operating systems, you can use Terminal Services. In some cases, you must use Terminal Services to complete administrative tasks.

You can access Terminal Services in two ways:

1. Through the UM Services browser, as described in step 3 on page 16.

2. By using the Terminal Services Client software. To use Terminal Services Client, complete the following steps to install it on the

remote workstation and connect to your NAS 200 appliance:

1. Insert the Supplementary CD into the workstation CD-ROM drive.

2. Click Start → Run.

3. In the Open field, type (with quotes)

"x:\Terminal Services Client\Disk 1\setup.exe"

where x is the drive letter assigned to the CD-ROM drive. Then click OK to begin the Terminal Services Client Setup program.

4. Accept the defaults in each window that opens or refer to the Microsoft Windows documentation for more instructions. When the Terminal Services Client Setup program is completed, proceed to the next step.

5. Check the workstation network TCP/IP protocol configuration settings.

Connecting to the desktop through Terminal Services

To connect to Terminal Services from your workstation, do the following:

1. Click Start → Programs → Terminal Services → Terminal Services Client.

2. In the Server field, select the computer name of the desired NAS 200 . If the desired NAS 200 is not listed, enter the IP address or the computer name of the NAS 200. The computer name is predefined as IBM5194-xxxxxxx, where xxxxxxx is the serial number located in the lower right corner of the bezel on the front of the appliance. If you have changed the computer name from the predefined value, use that name instead.

For Size, select a size other than full screen in which the NAS 200 desktop will appear, then click Connect to start the Terminal Services Client session. A user log in window displays.

Log in. Type Administrator in the Username field, type password in the password field, and then click OK to log in. Once you have logged in, you can begin using Terminal Services Client to configure and manage your NAS 200.

Once you have logged into Terminal Services, you can perform administrative tasks on the NAS 200, as if your keyboard, mouse, and monitor were directly attached to it. The NAS 200 desktop contains a shortcut, titled IBM NAS Admin, to a special console, the IBM NAS Administration console.

8 NAS 200 User’s Reference

IBM NAS Administration console

The IBM NAS Administration console contains all of the standard functions that are contained in the standard Computer Management console available on any Windows 2000 desktop, plus the following functions specific to the NAS 200, as described in “Chapter 6. Additional administrative functions” on page 35:

v NAS Backup Assistant v Persistent Storage Manager v ServeRAID Configuration

Determining who is using the network-attached storage

Occasionally, the administrator may want to know who is using the network-attached storage. The administrator can determine this information as follows:

1. Start a Windows Terminal Services session from the administrator’s console to the NAS 200.

2. Click on the IBM NAS Admin icon on the desktop.

3. In the left plane, click on File Systems, then Shared Folders, then Sessions.

4. The users currently using the storage are displayed. If necessary, you can close those sessions with a right-click. Before you close a session, you can notify the user that you are going to close the session by clicking on Start, Programs,

Accessories, Command Prompt, and then issuing the net send hostname messagetext command.

IBM Advanced Appliance Configuration Utility

The IBM Advanced Appliance Configuration Utility (IAACU) helps you to set up and reconfigure the network configuration on your NAS 200, as well as other IBM appliances.

The IAACU agent, preinstalled on your NAS 200, works with the IAACU Console, a

™

-based application that is installed on a remote workstation. You can use the

Java agent and console as a systems-management device to automatically detect the presence of NAS 200 appliances on the network. Once the NAS 200 appliance is detected by the IAACU Console, use the IAACU to set up and manage the appliance’s network configuration, including assigning the IP address, default gateway, network mask, and DNS server to be used by the appliance. You can also use the IAACU to start Universal Manageability Services (UM Services) on the appliance, enabling you to perform more advanced systems-management tasks.

For networks that are not currently running DHCP servers, the IAACU is useful for automatically configuring network settings for newly added appliances, such as the NAS 200.

However, networks with DHCP servers will also benefit from using the IAACU because it enables you to reserve and assign the appliance IP address in an orderly, automated fashion. Even when you use DHCP and do not reserve an IP address for the appliance, you can still use the IAACU to discover appliances and to start UM Services Web-based systems-management.

Notes:

1. The Advanced Appliance Configuration configures and reports the TCP/IP settings of the first adapter on each appliance only. The first adapter is typically

Chapter 2. Configuration and administration tools 9

IAACU Agent

the built-in Ethernet controller. Be sure to connect the built-in Ethernet connector to the same physical network as your systems management console.

2. The Advanced Appliance Configuration Utility must be running to configure newly installed appliances automatically.

3. The system running the Advanced Appliance Configuration Utility console automatically maintains a copy of its database (ServerConfiguration.dat) in the Advanced Appliance Configuration Station installation directory. To remove previous configuration data, close the Advanced Appliance Configuration Utility, delete this file, and then restart the utility. This deletes all previously configured Families. However, the Advanced Appliance Configuration Utility will automatically discover connected appliances and their network settings.

Once you connect the NAS 200 to your network, the IAACU agent automatically reports the appliance’s serial number and type, the MAC address of its onboard Ethernet controller, and whether DHCP is in use by the appliance. Furthermore, it will report the hostname, primary IP address, subnet mask, primary DNS server address, and primary gateway address if these are configured on the system.

The IAACU agent is preinstalled on your NAS 200 appliance. Note: The IAACU agent periodically broadcasts the appliance IP settings. To

prevent the service from broadcasting this data periodically, stop the iaaconfig service.

IAACU Console

The IAACU Console is a Java application that you install on one remote workstation in your network for use as a systems-management console. For information on how to install the IAACU Console, see Table 13 on page 79.

Note: The IAACU creates a private database that is specific to the IP subnetwork

to which it is attached. Therefore, do not install it on more than one systems-management console residing on the same IP subnetwork.

The IAACU Console enables you to: v Automatically discover NAS 200 appliances, as well as other IBM appliances,

that run the IAACU agent and are attached to the same physical subnet as the IAACU Console.

When you start the IAACU Console, it automatically detects all appliances on your physical subnet that are running the IAACU agent.

v Use a GUI-based application to configure the appliance network settings.

Use the IAACU to assign network parameters such as IP addresses, DNS and gateway server addresses, subnet masks, and hostnames.

v Group discovered appliances into function-specific Families. Appliances are

added to a Family based on the appliance type. Appliances that perform the same function appear in the same Family. (Note that all NAS 200 appliances are in the same family.)

v Start UM Services Web-based systems-management console.

Launch UM Services on your appliances and perform advanced systems-management tasks on a selected appliance with a single mouse click.

The IAACU Console is divided into two panes:

10 NAS 200 User’s Reference

v The Tree View Pane

The Tree View Pane, located on the left side of the IAACU Console window, presents a list of all discovered NAS 200 appliances and includes any Families you have previously defined. The Tree View Pane also includes groups for appliances that do not fit any of the defined Families, that were not configured using the IAACU, or that have IP addresses that conflict with other devices on your network. When you click on any item in the Tree View, information about that item (and any items that are nested below that item in the tree view) displays in the Information Pane.

v The Information Pane

The Information Pane, located at the right side of the IAACU Console, displays information about the item that is currently selected in the Tree View Pane. The information that displays in the Information Pane varies depending on the item that is selected. For example, if you select the All Appliances item from the Tree View Pane, the Information Pane displays configuration information (IP settings, hostname, serial number, and so on) about each of the NAS 200 appliances that have been discovered by the IAACU Console. However, if you select a Family, the Information Pane displays information about the Family settings for the selected Family.

The IAACU Console also features the following menus: v File: Use the File menu to import or export the IAACU Console configuration

data, to scan the network, or to exit the program.

v Family: Use the Family menu to add or delete Families, or to move Families up

or down in the tree view.

v Appliance: Use the Appliance menu to remove a previously discovered

appliance from a Family or group, and to add an appliance to the first matching Family in the tree view.

v Help: Use the Help menu to display product information.

Discovering NAS 200 Appliances

Any NAS 200 appliance, or other IBM appliance, that is running and is connected to the same subnet as the system running the IAACU Console is automatically discovered when you start the IAACU Console. Discovered appliances appear in the IAACU Console tree view (in the left pane of the IAACU Console window). Each appliance will appear in two locations in the tree view:

1. Every discovered appliance is listed in the tree view under All Appliances.

2. Each discovered appliance will also appear in one of the following portions of the tree view:

v In a Family

If the discovered appliance fits the requirements of a Family, it will automatically appear as part of a Family.

Note: If a discovered appliance fits the requirements of more than one

Family, it is automatically added to the first appropriate Family that is listed in the tree view, starting from the top of the tree. For information on how to move appliances between families, see “Using Families and Groups in the Tree View” on page 12.

v In the Orphaned Appliances group

If the discovered appliance does not fit a previously configured Family, it is placed in the Orphaned Appliances group.

v In the Orphaned Externally Configured Appliances group

Chapter 2. Configuration and administration tools 11

Appliances that are running the IAACU agent, but that have a network configuration that was not set by the IAACU agent or console, will appear in the Orphaned Externally Configured Appliances group. If an appliance is contained in the Orphaned Externally Configured Appliances group, you can use the Adopt By First Matching Family function to add it to a previously defined Family. For more information, see “Using the Adopt by First Matching Family Function” on page 14.

Using Families and Groups in the Tree View

Families are important elements of the IAACU. They specify the parameters that the IAACU uses to automatically categorize discovered appliances and to configure them with the appropriate network settings. Family rules are defined solely by appliance type or purpose. Each Family can contain only one type of appliance. The only way to automatically apply predetermined network settings to newly installed and discovered appliances is to create and use Families.

Appliances that match the rules criteria for a Family group can be automatically configured to use predefined network settings. A Family can be configured to allow appliances to use DHCP to configure their IP settings, or can be defined to automatically assign IP settings (such as primary gateway and DNS server addresses, assigning an IP address from a specified IP address range, and specifying a subnet mask). Host names for discovered appliances can also be defined so that they are allocated using either a prefix or appliance serial number.

The IAACU is not the only way to configure network settings. For example, network settings can be configured using Terminal Services for Windows or by attaching a keyboard and mouse to the appliance and using Windows Control Panel. If the appliance network settings have been configured by a method other than using the IAACU, the appliance will be discovered by the IAACU and it will be added to an appropriate Family, if one exists. Appliances that have been configured using a method other than the IAACU for which no appropriate family exists will appear in the Orphaned Externally Configured Appliances group.

The Tree View Pane contains the following items:

v All Appliances

Every discovered appliance is listed in the tree view under All Appliances.

v Families

The Families group in the Tree View Pane shows all Families that have been defined, with appliances that have already been assigned to each Family nested beneath the Family name in the tree view. Families are defined by appliance purpose, so all appliances that appear in a given family are of the same type. If you select a Family from the Tree View Pane, a description of the Family and the rules that are used to define the selected Family display in the Information Pane. If you select an appliance from a Family in the Tree View Pane, the selected appliance network settings display in the Information Pane.

If you are not using DHCP, the IAACU automatically assigns one IP address per appliance, using available addresses within the range defined in the Family rules. When a Family’s IP address range has been exhausted, the IAACU automatically searches for other Families that have rules matching the appliance being configured. If a matching Family with an available address is found, the appliance will automatically be assigned to the Family that has available IP addresses. This enables you to define multiple Families, each of which uses a set of non-contiguous IP address ranges.

When an appliance is discovered on the network, the IAACU automatically searches all previously defined Families, starting with the first Family listed in the

12 NAS 200 User’s Reference

Families tree view and moving downward. Appliances are automatically added to the first defined Family that matches the appliance purpose. Therefore, the order in which Families appear is important. To adjust this search order, right-click on a Family and then select Move Up or Move Down to adjust its position within the Families list.

v Orphaned Appliances

Any discovered appliances that have been configured using the IAACU but that do not meet the rules for any existing Family are automatically added to the Orphaned Appliances group.

v Orphaned Externally Configured Appliances

Any discovered appliance that has been configured without using the IAACU tool and that does not meet the rules for any existing Family is automatically added to the Orphaned Externally Configured Appliances group. Appliances configured without the IAACU that meet the rules for any existing Family are automatically added to the matching Family. To add an Orphaned Externally configured Appliance to an appropriate Family that was created after the orphaned appliance was discovered, right-click on the orphaned appliance and select Adopt by First Matching Family. For more information, see “Using the Adopt by First Matching Family Function” on page 14.

Note: The IAACU will not change manually configured network settings of

discovered appliances. If the manually configured IP and Subnet addresses fit an existing Family, the IAACU will place that appliance into that Family, but will not change any other settings (such as Host Name, DNS, or gateway addresses).

v Conflicting Network Addresses

Any discovered appliance that has the same IP address as a previously discovered appliance will be listed in the Conflicting Network Addresses group.

Creating a Family: To create a Family:

1. Select Create Family from the Family menu. The IAACU Family Setup window displays.

2. Select the Appliance Family Rules. The Appliance Family Rules determine what purpose an appliance must serve

to be included in the Family. You can select one of the following values:

v IBM TotalStorage NAS Appliances v IBM xSeries 130 and 135

You should select IBM TotalStorage NAS Appliances for a family that is to include your NAS 200.

3. Specify a Family name. In the Family Name field type the name that will be used for this Family.

4. Specify network resources to be used by members of the Family. You can use the IAACU to assign network resources for members of this

Family, or you can use a DHCP server to assign network resources. v To use the IAACU to assign network resources, uncheck the Use DHCP

checkbox and fill in the following fields:

Min IP Address

The lowest IP address in a range of IP addresses that can be assigned to an appliance that is a member of this Family

Chapter 2. Configuration and administration tools 13

Max IP Address

The highest IP address in a range of IP addresses that can be assigned to an appliance that is a member of this Family

Subnet Mask

The subnet mask value that will be used by appliances that are members of this Family

Default Gateway

The IP address of the default gateway that will be used by appliances that are members of this Family (optional)

DNS The IP address of the DNS server that will be used by appliances

that are members of this Family (optional)

v To use a DHCP server to assign network resources, check the Use DHCP

checkbox. This will allow a DHCP server on your network to assign an IP address and subnet mask and to specify the default gateway address and address of the DNS server that will be used by appliances that are members of this Family.

5. Select a Host Name Allocation Type. The Host Name Allocation Type enables you to automatically specify a Host

Name that members of this Family will use. You can select one of the following Host Name Allocation Types:

No Allocation

No preconfigured host name format will be assigned to appliances that are members of this family.

Use Serial Number

The Serial Number of the discovered appliance will be used as a host name for the appliance.

Use Prefix Name

A user-specified prefix, along with an incremental number for each appliance, will be used for the host name of each appliance that is a member of this Family. Type the desired prefix in the Host Name Prefix field.

6. Click OK to save this Family.

Removing Appliances from Families: Use the Remove Appliance function to delete an appliance from the IAACU Console database and view pane. Removing an appliance that is no longer in use allows the IP address that was assigned to the appliance to be allocated to another appliance. You can also remove an appliance from a family and then rescan the network to add it to an appropriate Family that appears higher in the Tree View pane.

To remove an appliance, right-click on the appliance, and then select Remove Appliance from the pop-up menu.

v If the IAACU is unable to communicate with the selected appliance (because, for

example, it has been removed from the network or has failed), the appliance is removed immediately.

v If the IAACU is able to communicate with the selected appliance, you will be

asked to confirm removal of the appliance before the appliance removal task is completed. This helps prevent accidental removal of an active and functional appliance.

Using the Adopt by First Matching Family Function: Use this function to:

14 NAS 200 User’s Reference

v Add an Orphaned Externally Configured Appliance to an appropriate Family.

Appliances that have been configured without using the IAACU tool and that do not meet the rules for any existing Family are automatically added to the Orphaned Externally Configured Appliances group. If, after the orphaned appliance is discovered, you create a Family that is appropriate for the orphaned appliance, right-click on the orphaned appliance and select Adopt by First Matching Family to move the appliance from the Orphaned Externally Configured Appliances group to the newly created Family.

v Move an appliance from one Family to another appropriate Family that occurs

higher in the list of previously defined Families. If there is more than one appropriate Family for a newly discovered appliance, it automatically appears in the first appropriate Family in the list of Families. If you want to move a discovered appliance from one appropriate Family to another appropriate Family:

1. Right-click on the Family that you want the appliance moved to.

2. Select Move Up in List to move the selected Family up in the list of families. Repeat steps 1 and 2 until the Family that you want to add the appliance to displays above the Family that currently contains the appliance.

3. Right-click on the appliance that you want to move to another Family and then select Adopt by First Matching Family.

Universal Manageability Services

The Universal Manageability Services (UM Services) GUI enhances the local or remote administration, monitoring, and maintenance of IBM systems. UM Services is a lightweight client that resides on each managed computer system. With UM Services, you can use a Web browser and UM Services Web console support to inventory, monitor, and troubleshoot IBM systems on which UM Services is installed.

This “point-to-point” systems-management approach, in which you use a Web browser to connect directly to a remote client system, enhances support and enables you to effectively maintain IBM systems without requiring the installation of additional systems-management software on your administrator console.

In addition to point-to-point systems-management support, UM Services also includes support for UM Services Upward Integration Modules. These modules enable systems-management professionals who use any supported systems-management platform (including Tivoli Enterprise, CA Unicenter TNG Framework, and Microsoft Systems Management Server [SMS]) to integrate portions of UM Services into their systems-management console. Because it was designed to use industry-standard information-gathering technologies and messaging protocols, including Common Information Model (CIM), Desktop Management Interface (DMI), and Simple Network Management Protocol (SNMP), UM Services adds value to any of these supported workgroup or enterprise systems-management platforms.

Complete documentation on how to use UM Services is included on the Documentation CD that came with the appliance.

System requirements

The UM Services client is preinstalled on the NAS 200 appliance. However, you must have a Web browser installed on your systems-management console. It is recommended that you set Microsoft Internet Explorer 5.x (or later) as the default browser.

Chapter 2. Configuration and administration tools 15

Notes:

1. You must install the optional Java Virtual Machine (VM) support to access a client system running UM Services.

2. If you reinstall Internet Explorer after installing UM Services, you must reapply the Microsoft VM update. The UM Services client requires Microsoft VM Build 3165 or later. Download the latest Microsoft VM from:

http://www.microsoft.com/java

3. If you install UM Services before you install Microsoft Management Console (MMC) 1.1 (or a later version), you will not have an icon for Microsoft Management Console in the IBM Universal Manageability Services section of your Start menu.

Starting UM Services

You can use IAACU or Terminal Services Client to configure the network setting remotely, or you can attach a keyboard and mouse to your appliance and configure the Network settings using the Windows Control Panel. Once you have configured the network settings for your appliance, you are ready to use UM Services.

To start UM Services:

1. Start your Web browser and then, in the Address or Location field of the browser, enter:

http://ip_address:1411

where ip_address is the IP address of the NAS 200 and then press Enter. Or, type:

http://computer_name:1411

where computer_name is the computer name of the NAS 200. The computer name is predefined as: IBM5194-xxxxxxx, where xxxxxxx is the serial number located in the lower right corner of the bezel on the front of the appliance.

If you have changed the computer name from the predefined value, use that name instead. After you have entered the computer name, press Enter.

2. A user log in window displays. Type Administrator in the Username field, and type password in the Password field. You can leave the Domain field blank. Make sure the “Save this password in your password list ” checkbox is not checked, and then click OK.

Note: To ensure system security, change the Administrator password from

“password” to something else. Once you do, or if you create another user in the Administrator group in the future, use your new username/password combination instead of the default username/password combination.

The first time you connect you may be prompted to install XML and Swing components. Follow the on-screen instructions to install these components and then close and restart Internet Explorer before you proceed.

3. You are now connected to the NAS 200 through UM Services. In addition to the standard UM Services functionality, your appliance includes functionality for administering the appliance, available from the Appliances tab in the left pane of the UM Services browser. The default view (in the right pane of the UM Services browser) when you connect to your appliance is Windows 2000 for

16 NAS 200 User’s Reference

NAS. The other selectable view in the Appliances tab is Windows 2000 Terminal Services, which displays a Terminal Services Web Connection page.

To start Windows 2000 for NAS, click Administer this server appliance in the right pane of the UM Services browser. To connect to the NAS 200 and manage it as though you were running Terminal Services Client from your desktop, select Terminal Services in the Appliances tab of the UM Services browser, and then follow the instructions for connecting to the NAS 200 using Terminal Services described in “Terminal Services and the IBM NAS Administration Console” on page 8.

Launching UM Services from the configuration utility

You can use the IAACU to launch UM Services on your NAS 200 appliance. Note: The selected appliance must be running Universal Manageability (UM)

Services as a UM Services client. Also, the systems-management console (the system that is running the IAACU Console) must use a Web browser that is supported for use with UM Services. If you have not used UM Services from this system, you will need to install several plug-ins before proceeding. If you are using an unsupported browser, or if your browser does not have the necessary plug-ins, you will be notified when you attempt to launch UM Services on the appliance. For more information on UM Services, go to:

http://www.ibm.com/pc/ww/software/applications/ums/library.html

To use the IAACU Console to start UM Services on an appliance:

1. Click on the appliance in the IAACU Console Tree View Pane. When you select the appliance from the tree view, information about the

selected appliance displays in the Information Pane. A Start Web-Based Management button displays as well.

2. Click Start Web-Based Management. Your default Web browser starts, loading the UM Services browser

automatically.

3. Log in to the UM Services browser. Refer to step 2 on page 16 for log in instructions.

For more information on using UM Services to manage your appliances, see the Universal Manageability Services User’s Guide, included on the Documentation CD that came with the appliance.

Windows 2000 for Network Attached Storage

You can perform the appliance administration tasks with the Windows 2000 for Network Attached Storage GUI. You navigate through various administrative task categories by clicking on the appropriate links on pages or buttons at the top of the page, and then selecting the task from that category.

Online help is available for Windows 2000 for NAS. This online help can be accessed in two ways:

1. By clicking the Help button at the top of any Web page. This will display a table of contents which you can navigate to find help for any Windows 2000 for NAS task.

2. By clicking the question mark (?) button at the top of any Web page. This will display context-sensitive help for the task you are currently performing.

Chapter 2. Configuration and administration tools 17

While you can perform most administrative tasks using Windows 2000 for NAS, there are some advanced tasks for which you must use Terminal Services Client. See “Terminal Services and the IBM NAS Administration Console” on page 8 for more information.

You can start Windows 2000 for NAS in one of three ways:

1. Through UM Services, as described in step 3 on page 16.

2. From a Web browser, by entering http://ip_address:8099 or http://computer_name:8099 and then logging on to the NAS 200.

3. From the NAS 200 desktop while using Terminal Services Client and starting a browser.

Telnet Server support

CAUTION: When you Telnet to another machine, your user name and password are sent over the network in plain, unencrypted, text.

The NAS 200 includes Telnet server capability. The Telnet server provides limited administrative capability for the NAS 200. This may be useful in cases where you need to remotely administer the NAS 200, but do not have access to a Windows-based workstation (from which you could remotely administer the appliance via a supported Web browser or Terminal Services Client).

SNMP support

You can access the NAS 200 from any Telnet client by specifying the IP address or hostname of the NAS 200, then logging in using an ID and password (defined on the NAS 200) with administrative authority. Once you have logged in, you will be presented with a command-line interface similar to that of a DOS command prompt in Windows (in fact, it will start at the C:\ prompt). From this interface, you can issue DOS-like commands (such as dir and cd), and some UNIX-like commands (such as grep and vi). You can launch some applications, but only character-mode applications are supported.

By default, the Telnet server is disabled. To enable the Telnet server, from the Windows 2000 for NAS user interface, go to the Network task group, then select Telnet. On the Telnet Administration Configuration page that appears, put a check in the Enable Telnet access to this appliance check box. Later, if you wish to disable Telnet access, you can uncheck Enable Telnet access to this appliance.If you do not require Telnet access to the NAS 200, then it is recommended that you leave the Telnet server disabled.

Support for the Simple Network Management Protocol (SNMP) is enabled. In order to manage the NAS 200 from your SNMP-capable management application, you will need to install the Management Information Base (MIB) files for various components of the NAS 200 on the management application workstation, so that the application can recognize those SNMP elements (values, alerts, etc.) supported by the components. Go to www.storage.ibm.com/nas for information on MIB files that are supported by the NAS 200.

18 NAS 200 User’s Reference

Chapter 3. Getting started

This chapter presents a recommended minimal procedure to quickly set up, configure, and administer your appliance. These instructions refer specifically to a base configuration as shipped and do not cover the setup of additional storage units, which are purchased separately.

Methods for setting up your NAS 200

The following sections detail how to set up your NAS 200. You first need to ensure that the network recognizes the new appliance. The appropriateness of the method you use to do this depends on several conditions:

v If you are operating in “headless” mode (that is, without a keyboard, monitor, and

mouse directly attached to the unit), you can use one of the following methods: – Windows Terminal Services

If DHCP is installed and the IP address requested can be determined, you can use this method for initial setup, but you should change the address to static later in the configuration. This condition is most appropriate for use of Windows Terminal Services for operation of the NAS 200.

If you are using this method, proceed with “Initial setup and configuration” on page 20.

– IBM Advanced Appliance Configuration Utility

If you have multiple appliances or cannot determine the DHCP address, you can install the IAACU to identify appliances and define IP addresses. The tool will also allow you to set static addresses.

If you are using this method, proceed with “Installing the IBM Advanced Appliance Configuration Utility”.

v Using a keyboard, display, and mouse is most appropriate when there is a single

or few appliances in the network and you use static setup and definition. If you are operating in this mode, proceed with “Initial setup and configuration” on

page 20.

Installing the IBM Advanced Appliance Configuration Utility

These instructions assume that you have installed and powered on the appliance according to the installation guide procedures. You are now ready to install the IBM Advanced Appliance Configuration Console application from the Supplementary CD.

Note: The Advanced Appliance Configuration Utility creates a private database that

is specific to the IP subnetwork to which it is attached. Therefore, do not install it on more than one systems management console residing on the same IP subnetwork.

Install the Advanced Appliance Configuration console application from the Supplementary CD onto a Windows NT 4.0 (or more recent version) or Windows 2000 workstation that is attached to the same IP subnetwork to which the appliance is attached. The Advanced Appliance Configuration icon will be placed on the workstation desktop.

For information on how to install the Advanced Appliance Configuration Utility Console, see Table 13 on page 79.

After you have installed the Advanced Appliance Configuration console application, the following steps will take you to the point where you can administer the appliance.

1. Start the Advanced Appliance Configuration console application by clicking its icon.

2. On the left pane of the Advanced Appliance Configuration console, select the appliance you want to administer. Initially, the appliance will be named IBM5194-serial number, which is located in the lower right corner of the bezel on the front of the appliance.

3. Click the Start Web Management button at the bottom of the right pane of the Advanced Appliance Configuration console to start the Universal Manageability (UM) Services browser. This will open a separate Web browser.

To read more information on the Advanced Appliance Configuration Utility, see “IAACU Console” on page 10.

Accessing Universal Management Services

1. You will be prompted to authenticate with administrative user name (“Administrator”) and password (initially “password”, but you will need to change this later).

If this is the first time you have accessed the UM Services browser (on any appliance) from this workstation, you will also be prompted to install the Swing and XML Java libraries in your Web browser.

2. The UM Services browser will start. In the left pane, Microsoft Windows 2000 for Network Attached Storage will be automatically selected, on the Appliance tab. In the right pane, Windows 2000 for Network Attached Storage will start.

3. Again, you will be prompted to authenticate with administrative user name (“Administrator”) and password (initially “password”, but you will need to change this later).

4. Click Administer this server appliance to bring up the Microsoft Windows 2000 for Network Attached Storage GUI.

You are now ready to begin administering the appliance. Details for this task are described in “Initial setup and configuration”.

Initial setup and configuration

This section provides details on the initial setup and configuration of the NAS 200. Note that if you are administering the NAS 200 without a keyboard, monitor, and

mouse (“headless” mode), there are one of two methods that you can use: v Terminal Services, which provides full administrative function. (See “Terminal

Services and the IBM NAS Administration Console” on page 8.)

v Windows 2000 for Network Attached Storage, which provides a subset of the full

administrative function in Terminal Services. (See “Windows 2000 for Network Attached Storage” on page 17.)

In general, you administer the appliance by adjusting information contained in the following task groups:

Note: In this example, you access the task groups through the Windows 2000 for

Network Attached Storage Web-based GUI.

v “Maintenance (Date and Time)” on page 21

20 NAS 200 User’s Reference

v “Network Setup” Although you can modify multiple appliance and network attributes in each task

group, the information given here is the minimum you need to know to administer the appliance and network.

You can find more information on administration elsewhere in this book and in the online help.

Note that the icons for the task groups on the administration home page are not in the same order as presented here.

You can access these task groups in one of three ways:

1. Click the Home tab and then select the task group link.

2. Click the top tab associated with that task group.

3. Click the Back button on your browser until you arrive Home and then select the task group link.

Maintenance (Date and Time)

In the Maintenance task group, you will need to change the date and time. To do so, click on Date and Time or the green arrow. (Remember that you can also access all of these task groups by clicking on the titled tabs at the top of the page.) The Set Date and Time page appears to allow you adjust information as necessary.

Network Setup

Note: All appliances have an initial default User Name of “administrator” and

Password of “password”.

In the Network Setup task group, you are required to change the administrator password. Optionally, you can configure the properties of each network interface that resides on the appliance.

To change the administrator password, click on Change Administrator Password or the green arrow. The Change Administrator Password page appears to allow you to change the password. Note the warning on the page that any information you enter can be viewed by others on the network. To prevent others from seeing your information, set up a secure administration Web site as described in the online help.

To optionally change interface properties such as IP addresses, click on Interfaces or the green arrow. The Network Adapters on Server Appliance page appears. You would use this page primarily to change IP addresses from dynamic (DHCP, which is the system default) to static.

You can then select the network adapter you want to modify, and then choose one of the following tasks related to that adapter:

v IP, to modify IP configurations v DNS, to modify DNS configurations v WINS, to modify WINS configurations

Enabling National Language Support (NLS)

Through the Windows 2000 for NAS GUI or the Windows desktop, you can set up the NAS 200 interface to display in any of the following languages:

Chapter 3. Getting started 21

v French v German v Japanese v Spanish

Using Windows 2000 for NAS, open the Maintenance task group, select Language, pick one of the four languages noted above, and then restart the machine.

Using the desktop, select: Start → Settings → Control Panel → Regional Settings.

22 NAS 200 User’s Reference

Chapter 4. Storage configuration

This chapter gives the details for setting up and configuring the NAS 200 storage.

ServeRAID configuration

This section gives details on configuring the ServeRAID adapter.

RAID technology

RAID technology allows you to group several physical drives into an array that you can define as one or more logical drives. Each logical drive appears to the operating system as a single drive. This grouping technique greatly enhances logical-drive capacity and performance beyond the physical limitations of a single physical drive.

For an overview of RAID technology, see Chapter 3 ″Understanding RAID technology″ in the ServeRAID-4x Ultra160 SCSI Controller publication, which is included on the Documentation CD that came with your appliance.

Table 2 shows the standard features of the ServeRAID-4Lx and ServeRAID-4H.

Table 2. Standard features of ServeRAID-4Lx and ServeRAID-4H

Feature ServeRAID-4Lx (Model 201) ServeRAID-4H (Model 226)

Arrays (maximum) 8 8 Battery-backup cache No Yes Cache memory 16 MB 128 MB Logical drives (maximum) 8 8 SCSI channels 1 4 SCSI transfer speed

(maximum) Supported RAID levels 0, 1, 5, Enhanced-1 (1E),

System PCI data bus 64–bit at 33 MHz 64–bit at 33 MHz

160 MB/sec 160 MB/sec

and Enhanced-5 (E5), 00, 10, 1E0, 50

0, 1, 5, Enhanced-1 (1E) and Enhanced-5 (E5), 00, 10, 1E0, 50

Updating the ServeRAID BIOS, firmware, and device drivers

The NAS 200 preloaded software ships with the required BIOS, firmware and device drivers. You do not need to load or update any of these items. Should replacement software be required, it will be available online as described in the Storage Unit Installation and User’s Guide GA27-4259.

Attention: Because the NAS 200 hardware and software is preconfigured as a high-performance network-attached storage appliance, you should not update the BIOS, firmware, or device drivers using the procedures described in the ServeRAID-4x Ultra160 SCSI Controller publication.

Functionality not needed and not supported in the NAS 200

Because the ServeRAID hardware and software is used in several IBM products, note that the ServeRAID-4x Ultra160 SCSI Controller publication refers to the following items that are not applicable and not supported on the NAS 200:

v Failover v Clustering v Other operating systems

Solving ServeRAID problems

For a complete description of how to diagnose ServeRAID problems see Chapter 18, “Solving ServeRAID problems” in the ServeRAID-4x Ultra160 SCSI Controller publication.

If you need help on your NAS 200, you should follow the support instructions as described in the Storage Unit Installation and User’s Guide GA27-4259 appendix. Because the NAS 200 is a preconfigured system, do not use the information described in Chapter 19 of the ServeRAID-4x Ultra160 SCSI Controller publication.

Initial storage configuration of the NAS 200

The NAS 200 comes with preconfigured storage, formatted as follows:

v A RAID-level 1E array, for the System partition (drive letter will be C:) v A RAID-level 1E array, for the Maintenance partition (drive letter will be D:) v A RAID-level 5 array, comprised of the remaining storage. This array consists of

a single LUN, for the Data drive (drive letter will be E). The size of this LUN depends on the number and size of hard disk drives that came with your NAS

200.

Attention: Note that although you will be using files in the System and Maintenance drives, it is strongly recommended that you do not repartition them. Doing so could wipe out important data and seriously impair the functioning of your system. Repartitioning is advised ONLY for the Data drive.

You can use the preconfigured Data drive, or delete it and configure new storage. If the preconfigured storage is agreeable with your requirements, you can proceed with “Chapter 5. Completing setup” on page 27. If you delete the Data drive, you will need to complete the steps in this chapter.

Creating arrays and logical drives

You configure RAID disk arrays and logical drives on your NAS 200 using the ServeRAID Manager. With ServeRAID Manager, you can configure and manage the storage mounted in the NAS 200 itself (the internal hard disk drives), in addition to the storage mounted in any IBM 5194 TotalStorage NAS 200 Storage Unit enclosures.

To start ServeRAID Manager, click the IBM NAS Admin icon, and then open the Storage folder and double-click ServeRAID Manager.

For details on how to use the ServeRAID Manager, see the following sections in Chapter 4, “Understanding RAID technology” in the ServeRAID-4x Ultra160 SCSI Controller publication:

v Configuring the ServeRAID controller v Using the ServeRAID manager program

Considerations for configuring the arrays and logical drives for the NAS 200:

24 NAS 200 User’s Reference

1. It is recommended that all arrays used for data drives are RAID-5, though other RAID levels are supported.

2. All disk drives in a single array must be of the same size (36.4 GB and 72.8 GB disk drives are supported by the NAS 200, but the two sizes cannot be mixed in a single array).

3. The preconfigured arrays for the System (C:) and Maintenance (D:) drives (both RAID-1E) must not be deleted.

Continue with “Format the logical drives”.

Format the logical drives

Attention: Disk 0 and Disk 1 that appear in the Disk Management application

described in the following procedure represent the System and Maintenance partitions described earlier in this chapter. As a further reminder, do not delete or reformat these partitions.

Follow this procedure to format logical drives:

1. Open IBM NAS Admin and select Disk Management (Local), in the Storage folder.

2. You will see a Write Signature and Upgrade Disk Wizard pop up on the screen. Click Cancel.

3. Right-click on the area in the bottom of the right pane, where it says Disk 2, and select Write Signature.

4. Repeat the previous step for all other data disks (Disk 3, Disk 4, and so on).

5. On each data disk: a. Right-click and select Create Partition and click Next. b. Select Primary Partition and click Next. c. Select the entire disk size and click Next. d. Specify NTFS as the file system, and specify whatever name you want to

assign to the partition.

e. Click Finish. Do not enable disk compression, and select Finish.

6. Assign a drive letter of E for the first drive, G for the second drive, H for the third drive, and so on. Drive letter F will remain assigned to the CD-ROM drive.

At this point, you have set up storage. You can now continue with “Chapter 5. Completing setup” on page 27.

Chapter 4. Storage configuration 25

26 NAS 200 User’s Reference

Chapter 5. Completing setup

This chapter gives the details for setting up the NAS 200 so clients and servers on your network can access the storage.

v If Windows clients and servers will access your storage, follow the steps in

“Defining Windows users and groups”.

v If UNIX and UNIX-based clients and servers will access your storage, follow the

steps in “Defining UNIX users and groups” on page 28.

v If both Windows and UNIX clients and servers will access your storage, you will

need to follow the steps in “Defining Windows users and groups” and then follow the steps in “Defining UNIX users and groups” on page 28.

Defining Windows users and groups

This section describes how to set up Windows users and groups who will access the NAS 200 storage.

You may define Windows users and groups locally on the NAS 200. Alternatively, you can add the NAS 200 to an existing Windows domain that is controlled by a Primary Domain Controller (PDC), and define new users and groups on the PDC who can access the NAS 200 storage and/or allow existing users and groups to access the NAS 200 storage.

If you are defining local Windows users and groups, follow the steps in “Defining local Windows users and groups”. If you are giving access to the NAS 200 storage to users and groups in an existing Windows domain, follow the steps in “Giving storage access to Windows domain users and groups” on page 28.

Defining local Windows users and groups

If you are defining local Windows users and groups, you may use the Windows 2000 for Network Attached Storage user interface. In the Users task group, you create and manage local users and groups on the NAS 200. Clicking on Users takes you to the Users page. From this page you can create, edit, and delete local users and groups on the NAS 200 by clicking either Local Users or Local Groups.

To create new local users, do the following:

1. Click Local Users.

2. Click New...

3. Fill in user name, password, and description (optional).

4. Click OK. The new user name should appear in the list of user names.

5. Repeat Steps 1 through 4 for each new local user you wish to add.

6. When you are finished adding new users, click Back to return to the Users and Groups page.

To create new local groups, do the following:

1. Click Local Groups.

2. Click New....

3. Fill in group name and description (optional).

4. Click Members.

5. For each user you wish to add to the group, select the user name from the list of users, and then click Add.

6. Click OK. The new group name should appear in the list of group names.

7. Repeat Steps 1 on page 27 through 6 for each new local group you wish to add. If your storage is also going to be accessed by UNIX or UNIX-based clients and servers, continue with “Defining UNIX users and groups”. Otherwise, continue with “Creating shares” on page 32.

Giving storage access to Windows domain users and groups

You must first join the NAS 200 to the Windows domain. You may use the Windows 2000 for Network Attached Storage user interface to do this. Start the Windows 2000 for Network Attached Storage user interface, then do the following:

v Click Network. v Click Identification. v Select the radio button labeled Domain, and specify the name of the domain

being joined.

v Specify a user name and password that can be used to log on to the domain. v Click OK. v Shut down and restart the NAS 200.

Users and groups already defined in the domain can now be given access to any file shares that you create on the NAS 200. If you need to add new users and groups to the domain, consult the online documentation on the PDC for information on performing this procedure, or if you are not the administrator of the domain (PDC), contact the domain administrator to have the users and groups defined.

If your storage is also going to be accessed by UNIX or UNIX-based clients and servers, continue with “Defining UNIX users and groups”. Otherwise, continue with “Creating shares” on page 32.

Defining UNIX users and groups

This section describes how to set up UNIX users and groups who will access the NAS 200 storage via the Network File System (NFS) protocol.

Support for NFS is provided in the NAS 200 by a preloaded and preconfigured software component, Microsoft Services for UNIX. The levels of NFS supported by Services for UNIX, and in turn the NAS 200, are NFS Versions 2 and 3. Any client or server that is using an NFS software stack supporting NFS Version 2 or NFS Version 3, regardless of the operating system, should be able to connect to the NAS 200 and access its storage via NFS.

You administer NFS file shares and other attributes with standard Windows administration tools, including those provided as part of the IBM NAS desktop, and the Microsoft Windows 2000 for NAS user interface. Additional configuration of the User Name Mapping component of Services for UNIX, which maps the UNIX user name space to the Windows user name space, is required to support NFS security.

You can define a local UNIX name space on the NAS 200 by configuring the Server for PCNFS component of Services for UNIX. Alternately, you can point Services for UNIX to an existing Network Information Service (NIS) domain which defines the UNIX name space. In both cases, you will need to configure the User Name Mapping component to map the UNIX name space you select to the Windows name space, since file shares and individual file/directory permissions on the NAS 200 are defined in the context of the Windows name space.

28 NAS 200 User’s Reference

If you are going to define a local UNIX name space, continue with “Using a local UNIX name space”. If you are going to use a UNIX name space defined on a NIS domain, continue with “Using the UNIX name space on an NIS domain” on page 31.

Using a local UNIX name space

This procedure should only have to be performed once. You may have to add more groups and users in the Server for PCNFS page if you add more users and groups to your UNIX environment and NAS 200 or Windows domain at a later time.

1. Open the IBM NAS Administration console by double-clicking the IBM NAS Admin icon on the NAS desktop.

2. In the left pane, click the plus sign (+) next to File Systems, then click the plus sign next to Services for UNIX.

3. In the left pane, click Server for NFS.

4. In the right pane, in the Computer name: field, enter localhost.

5. In the left pane, click Server for PCNFS.

6. In the right pane, click Groups.

7. On the Groups page, you will need to add the groups from your UNIX host to which all of your UNIX users belong. You will need to know both the group name and the group ID (GID) number. This information can be found in the /etc/group file on most UNIX systems.

As an example, on an AIX system, in the following line from an /etc/group file, the fields are separated by a colon (:). The first field (″staff″) is the group name; the third column (″1″) is the GID:

staff:!:1:pemodem,ipsec,netinst,protcs

You add a group by entering the group name and GID number in the Group name and Group number (GID) fields, respectively, and then clicking New.

8. When you have finished adding groups, click Apply.

9. Click Users.

10. On the Users page, you will need to add all of the UNIX users who will be accessing and storing files on the NAS 200 through an NFS share. For each user you will need to know the Windows user name, the UNIX user name, the primary group, and the user ID (UID) number. This information can be found in the /etc/passwd and /etc/group files on most UNIX systems.

As an example, on an AIX system, in the following line from an /etc/passwd file, the fields are separated by a colon (:). The first field (″user1″) is the user name; the third field (″3135″) is the UID, and the fourth field (″1″) is the GID of the user’s primary group. This will correspond to a line in the /etc/group file, where you can find the primary group name corresponding to the GID.

user1:!:3135:1:User 1:/home/user1:/bin/ksh

You add a user by clicking New, entering the required information, and then clicking OK.

11. When you have finished adding users, click Apply.

12. In the left pane, click User Name Mapping.

13. In the right pane, click the radio button next to Personal Computer Network File System (PCNFS).

14. In the Password file path and name field, enter c:\winnt\system32\drivers\etc\passwd.

Chapter 5. Completing setup 29

15. In the Group file path and name field, enter c:\winnt\system32\drivers\etc\group, then click Apply.

16. Click Maps.

17. On the Maps page, you can configure simple maps or advanced maps. Configure simple maps if the Windows user name and UNIX user name is the same for each UNIX user to be mapped, and the Windows group name and UNIX group name is the same for each UNIX group to be mapped. Otherwise, you should configure advanced maps.

To configure simple maps, check the Simple maps checkbox and continue with Step 18. To configure advanced maps, uncheck the Simple maps checkbox and continue with Step 19.

18. Under the Simple maps checkbox, select the Windows domain name from the drop-down list, then continue with Step 20 on page 31. (If your Windows users are defined locally on the NAS 200, select the entry containing the computer name of the NAS 200, preceded by two backslash characters (“\\”). Otherwise, select the name of the Windows domain where the users are defined from the list.)

19. Under Advanced maps, do the following: a. Define user mappings as follows:

1) Click Show user maps.

2) Select the Windows domain name from the drop-down list. (If your Windows users are defined locally on the NAS 200, select the entry containing the computer name of the NAS 200, preceded by two backslash characters (“\\”). Otherwise, select the name of the Windows domain where the users are defined from the list.)

3) Click Show Windows Users to display all of the Windows user names in the Windows domain you selected.

4) Click Show UNIX Users to display all of the UNIX user names in the NIS domain you selected.

5) Enter a Windows user name, or select one from the list of Windows user names.

6) Enter a UNIX user name to be mapped to the Windows user name you specified, or select one from the list of UNIX user names.

7) Click Add to add the mapping between the UNIX user name and Windows user name to the list of maps.

8) If multiple Windows user names are mapped to one UNIX user name, you must select one Windows user name to be the primary user name. Select the mapping corresponding to the primary user name from the list of maps, and then click Set Primary.

b. Define group mappings as follows:

1) Click Show group maps.

3) Click Show Windows Groups to display all of the Windows group names in the Windows domain you selected.

4) Click Show UNIX Groups to display all of the UNIX group names in the NIS domain you selected.

5) Enter a Windows group name, or select one from the list of Windows group names.

6) Enter a UNIX group name to be mapped to the Windows group name you specified, or select one from the list of UNIX group names.

30 NAS 200 User’s Reference

7) Click Add to add the mapping between the UNIX group name and Windows group name to the list of maps.

8) If multiple Windows group names are mapped to one UNIX group name, you must select one Windows group name to be the primary group name. Select the mapping corresponding to the primary group name from the list of maps, and then click Set Primary.

20. Click Apply. You may now continue with “Creating shares” on page 32.

Using the UNIX name space on an NIS domain

The following procedure applies whether your NIS server is UNIX-based or Windows-based (implemented as a Windows domain controller running Microsoft’s Server for NIS).

1. Open the IBM NAS Administration console by double-clicking the IBM NAS Admin icon on the NAS desktop.

2. In the left pane, click the plus sign (+) next to File Systems, then click the plus sign next to Services for UNIX.

3. In the left pane, click Server for NFS.

4. In the right pane, in the Computer name: field, enter localhost.

5. In the left pane, click User Name Mapping.

6. In the right pane, click the radio button next to Network Information Services (NIS), then click Maps.

7. On the Maps page, you can configure simple maps or advanced maps. Configure simple maps if the Windows user name and UNIX user name is the same for each UNIX user to be mapped, and the Windows group name and UNIX group name is the same for each UNIX group to be mapped. Otherwise, you should configure advanced maps. To configure simple maps, check the Simple maps checkbox and continue with Step 8. To configure advanced maps, uncheck the Simple maps checkbox and continue with Step 9.

8. Under the Simple maps checkbox, do the following: a. Select the Windows domain name from the drop-down list. (If your

Windows users are defined locally on the NAS 200, select the entry containing the computer name of the NAS 200, preceded by two backslash characters (“\\”). Otherwise, select the name of the Windows domain where the users are defined from the list.)

b. In the NIS domain box, enter the NIS domain name. You may also enter

the name of a specific NIS server in the NIS server box.

c. Continue with Step 10 on page 32.

9. Under Advanced maps, do the following: a. Define user mappings as follows:

1) Click Show user maps.

3) In the NIS domain field, enter the NIS domain name. You may also enter the name of a specific NIS server in the NIS server field.

4) Click Show Windows Users to display all of the Windows user names in the Windows domain you selected.

5) Click Show UNIX Users to display all of the UNIX user names in the NIS domain you selected.

Chapter 5. Completing setup 31

6) Enter a Windows user name, or select one from the list of Windows user names.

7) Enter a UNIX user name to be mapped to the Windows user name you specified, or select one from the list of UNIX user names.

8) Click Add to add the mapping between the UNIX user name and Windows user name to the list of maps.

9) If multiple Windows user names are mapped to one UNIX user name, you must select one Windows user name to be the primary user name. Select the mapping corresponding to the primary user name from the list of maps, and then click Set Primary.

b. Define group mappings as follows:

1) Click Show group maps.

3) In the NIS domain field, enter the NIS domain name. You may also enter the name of a specific NIS server in the NIS server field.

4) Click Show Windows Groups to display all of the Windows group names in the Windows domain you selected.

5) Click Show UNIX Groups to display all of the UNIX group names in the NIS domain you selected.

6) Enter a Windows group name, or select one from the list of Windows group names.

7) Enter a UNIX group name to be mapped to the Windows group name you specified, or select one from the list of UNIX group names.

8) Click Add to add the mapping between the UNIX group name and Windows group name to the list of maps.

9) If multiple Windows group names are mapped to one UNIX group name, you must select one Windows group name to be the primary group name. Select the mapping corresponding to the primary group name from the list of maps, and then click Set Primary.

10. Click Apply. You may now continue with “Creating shares”.

Creating shares

To create new file shares on the NAS 200, do the following:

1. Start the Windows 2000 for Network Attached Storage user interface.

2. Click the Shares tab.

3. Click the Shares task.

4. Click New....

5. Specify the share name (the name which clients and servers will use to access

6. Specify the share path, and check the Create folder if it does not already exist

7. By default, the Microsoft Windows (CIFS) and UNIX (NFS) checkboxes are

8. If this share is to be accessed by

32 NAS 200 User’s Reference

the share).

checkbox.

checked (enabled). If this share is not to be accessed by Windows clients and servers, uncheck (disable) the Microsoft Windows (CIFS) checkbox. If this share is not to be accessed by UNIX clients and servers, uncheck the UNIX (NFS) checkbox.

v Windows clients and servers, then click CIFS Sharing and specify access

permissions as desired. (Note that by default, every user has full access to all files and directories under the shared folder.)

v UNIX clients and servers, then click NFS Sharing and specify access

permissions as desired. (Note that by default, every user has full access to all files and directories under the shared folder.)

9. Click OK. The new share should appear in the list of shares.

10. Repeat Steps 4 on page 32 through 9 for each additional share you wish to create.

You may now continue with “Chapter 6. Additional administrative functions” on page 35.

Chapter 5. Completing setup 33

34 NAS 200 User’s Reference

Chapter 6. Additional administrative functions

This chapter describes the additional administrative functions that you can do on the NAS 200.

The following functions are available:

v “NAS Backup Assistant”, accessed through IBM NAS Admin icon

v “Persistent Images” on page 36, accessed through the Windows 2000 for

Network Attached Storage user interface

v “Ethernet adapter teaming” on page 44, accessed through Intel PROSet II or

Alacritech SLICuser

NAS Backup Assistant

The NAS Backup Assistant is a preloaded utility that helps you create and schedule backup batch files, and maintain log files. It can be used for backing up either the NAS 200 operating system or user data.

You invoke the NAS Backup Assistant by clicking on the IBM NAS Admin desktop

icon to open the IBM NAS Administration console. Select Backup and Restore to expand that tree, then select IBM NAS Backup Assistant. Once you have selected this option, a logon prompt appears. You will need to log on as a user who has backup operator privilege (that is, as an administrator or backup administrator).

Because NAS Backup Assistant only creates and launches scripts, and is not a comprehensive backup application, it does not support interactive error messages. To check status of jobs, you must either view the Backup Logs or view the Windows Event Viewer. If a logon prompt does not appear, right-click on the IBM NAS Backup Assistant link, and select refresh. Once you log on, the main panel appears.

There are four tabs on the main panel:

Backup Operations

The main window where you create and schedule backup batch jobs.

Scheduled Jobs

Displays a list of backup batch jobs that you scheduled.

Backup Logs

Displays a list of log files for each backup that has run.

Displayed Logs

Displays the text contained in the log files that you can select from the Backup Logs tab.

All of the options on each tab are described in detail in the online help. To access the online help, click on the IBM NAS Admin icon, then expand the Backup and Restore directory, then select IBM NAS Backup Assistant Help and log in.

Restoring using the NT Backup panel

To restore backups, use the following procedure:

1. Note these two conditions: v If you are restoring a backup that you created using the standard backup

method, go to step 2 on page 36.

v If you are restoring a backup that you created using Persistent Images in

the NAS Backup Assistant, the NT Backup file (*.BKF) was created for the persistent image virtual drive letter instead of the original drive letter. For example, if you selected drive C for backup, a persistent image was created on the next available drive letter in the system, and that drive was backed up instead of drive C. If you do not remember the original drive letter, you can view the backup log files in NAS Backup Assistant. The top section of the log file gives you the original drive letter, and the bottom section gives you the persistent image drive letter. Now that you have the original drive letter, go to step 2.

2. Click on the Restore using NT Backup link in the Backup and Restore section of the IBM NAS Admin console to open the backup GUI.

3. Click Restore Wizard, then click Next.

4. You are asked what you want to restore. Select the appropriate media that you are restoring from.

5. If you are restoring from tape, expand the backup media pool name, and then double-click on the media (this will normally be named media created on {date

- time}). This action will read the set list from the tape. If you are restoring from file, click the Import File... button, then click Browse

and find the .BKF file created for this backup. If you do not know the .BKF file name, refer to the backup log in NAS Backup Assistant. Click OK. You will now have a Media created on {date - time} listed under file. Click on the plus sign (+) to the left of this media to see the set list. You may be prompted to enter the path to the file you want to catalog; if so, select the same file that you just imported. This will build a set list.

6. Select the files and directories you want to restore by placing a check in the corresponding check box.

7. In the bottom left corner of the window, there is an option called Restore files to:. Using the pull-down, select Alternate Location. In the alternate location window, select the root directory of the original backup drive letter you determined in step on page 35.

8. If desired, select Tools from the menu bar at the top of the window, then select Options to change restore options. Refer to NTBackup online help (see Restore files from a file or a tape) for use of these options.

9. Once you have selected the files or directories for restore, the alternate location, and options, click the Start Restore button in the lower right corner.

10. You will now be prompted to confirm that you want to begin the restore. You can click the Advanced button to select advanced options (see the NTBackup online help for details), then click OK to begin the restore.

Persistent Images

A persistent image is a copy you make of one or more file system volumes at a specific time. The Persistent Images function allows the recovery of a file or volume to the state it was in at the time you created the persistent image. Persistent images are maintained in a way that minimizes the storage required to keep a second (or third or fourth, and so on) copy of the volume. This is done by using a copy-on-write technique that uses, for each volume, an area of pre-allocated storage (the PSM cache file) that keeps only those data blocks which have been written since the time you made a persistent image of the volume.

Persistent Storage Manager (PSM) allows you to create and preserve images of the NAS 200 drives. You can take a persistent image immediately or schedule

36 NAS 200 User’s Reference

persistent images as one-time events or regularly repeated events. You can access the PSM tasks in the Disks/Persistent Storage Manager task group within the Windows 2000 for Network Attached Storage user interface, in one of two ways:

v By going to the IBM NAS Admin console on the appliance desktop (via Terminal

Services or directly-attached keyboard, monitor, and mouse) and selecting Persistent Storage Manager (this automatically launches the Windows 2000 for Network Attached Storage user interface and brings up the Disks/Persistent Storage Manager page containing the PSM tasks).

v By starting the Windows 2000 for Network Attached Storage user interface

directly

Once you create a persistent image, it appears as a directory on the original drive. Access rights and permissions from the original drive are inherited by the persistent image. Persistent images are used in the same way as conventional drives. However, unlike conventional drives, persistent images are records of the content of the original drive at the time you created the persistent image. Persistent images are retained following shutdown and reboot.

There are six PSM tasks in the Disks/Persistent Storage Manager group:

v Global Settings v Volume Settings v Persistent Images v Schedules v Restore Persistent Images v Disaster Recovery

Each of these tasks are described in the following sections. More detailed descriptions and instructions for each of the control panels and topics are contained in the online help.

Global Settings

On this panel you can configure the following attributes of the persistent image function:

Volume Settings

This panel displays statistics for each volume, such as total volume capacity, free space, and cache file size and usage. You can also select any volume and configure volume-specific PSM attributes for that volume, such as:

Attribute: Default value:

Maximum number of persistent images 250 Inactive period 5 seconds Inactive period wait timeout 15 minutes

Attribute: Default value:

Cache-full warning threshold 80 percent full Cache-full persistent image deletion threshold 90 percent full Cache size 15 percent (of the total volume

capacity)

Chapter 6. Additional administrative functions 37

Persistent Images

This panel lists all of the persistent images that exist on all volumes. On this panel you can:

v Create a new persistent image immediately (without scheduling it via the

v Delete an existing persistent image. v Modify properties of an existing persistent image, including read-only or

When you create the persistent image, you can specify properties for the persistent image, including:

Volume(s) The persistent image can contain a single volume

Name You can name the persistent image. This will be the

Schedules panel).

read-write, and retention value.

or multiple volumes. To select multiple volumes, hold down the Ctrl key while clicking on the volumes you wish to select. For multi-volume persistent images, a virtual directory containing data for a volume will appear under the persistent image directory in the top level of each volume in the persistent image (the name of the persistent image directory is configured in the Global Settings panel).

name of the virtual directory containing the persistent image, underneath the persistent image directory in the top level of the volume (the name of the persistent image directory is configured in the Global Settings panel).

Read-only or read-write A persistent image is read-only by default, so no

modifications can be made to it. However, you can set the persistent image to read-write, which permits you to modify it. When a persistent image is written, the modifications made are also persistent (they survive a reboot of the system). Changing a persistent image from read-write to read-only resets the persistent image to its state at the time you took the persistent image, as does selecting Undo Writes for a read-write persistent image from the Persistent Images panel.

Retention value A persistent image can be given a relative retention

value or weight. This is important when PSM needs to delete some persistent images for a volume because the cache file for the volume for which the persistent image was taken capacity has reached a certain threshold, as described later in this section. If the volume cache file completely fills, then all persistent images for that volume are deleted regardless of the retention values. By default, a new persistent image is assigned a “Normal” retention value (there are other higher and lower values which can be selected).

38 NAS 200 User’s Reference

Schedules

Use this panel to schedule persistent images to be taken at specific times (this is independent of the scheduled backup function via NAS Backup Assistant described earlier). Each PSM schedule entry defines a set of persistent images to be taken starting at a specified time and at a specified interval, with each image having the set of properties defined in the entry. This allows you to customize scheduled persistent images on a per-volume basis.

For instance, you could set a persistent image for one volume to occur every hour, and for another volume to occur only once a day. The set of properties you can define are the same properties described in the Persistent Images panel description above; when you define these properties, all persistent images created according to this schedule entry will be given those properties. Once a scheduled persistent image is created, certain properties of that persistent image can be modified via the Persistent Images panel, independently of other persistent images created according to the schedule.

Once a schedule entry is created, it appears in the list of scheduled persistent images. Subsequently you can modify the properties of an existing entry, such as start time, repetition rate, the volume(s), and so on. For a schedule you can name the persistent images based on a pattern you configure; format specifiers (defined on the New Persistent Image Schedule panel under the Persistent image name(s) entry field) allow you to customize variable portions of the name.

Restore Persistent Images

On this panel, you can select an existing persistent image and quickly restore the volume contained in the image back to the state it was in at the time the selected persistent image was taken. This is useful if you need to recover an entire volume, as opposed to just a few files. This volume restore function is available for the data volumes, but not the system volume.

Disaster Recovery

PSM provides a disaster recovery solution for the system drive. This extends the volume restore function of PSM to provide disaster recovery in the event that the system drive is corrupted to the point where the file system is corrupt, or the operating system is unbootable. Note that while disaster recovery is also supported via the Recovery CD-ROM and backup and restore capability, that is a two-step process. In contrast, the method supported by PSM allows you to restore the system drive from a single image, without having to go through the entire recovery procedure and then additionally having to restore a system drive backup.

Use the Disaster Recovery panel to schedule and create backup images of the system drive, and to create a bootable diskette which will allow you to restore the system drive from a backup image (located on the maintenance partition, or network drive). The remainder of this section provides additional information on how to perform backup and recovery operations for the NAS 200.

Note: Restoration of a PSM backup image over the network is not supported for

the Gigabit Ethernet Adapter. If you have only Gigabit Ethernet adapters installed, it is recommended that you perform PSM backup of each NAS 200 to its maintenance partition (D: drive), which would allow you to recover if the system volume is corrupt and/or unbootable. Should the hard disk drive fail completely, you would need to use the Recovery CD as described in “Using

Chapter 6. Additional administrative functions 39

the Recovery Enablement Diskette and Recovery CD Set” on page 77 to restore the NAS 200 to its original (factory) configuration.

Backing up the system drive

On the Disaster Recovery panel you will find status information for backup operations, both scheduled and immediate, as well as buttons for starting and stopping a backup operation, for configuring backup, and for creating a recovery diskette.

Click the Modify Settings button to open the Disaster Recovery Settings page. Modify the settings for backup as you desire. Note that you must not include spaces in the Backup name field. When you have modified the settings, click the OK button to save the changes.

On the Disaster Recovery page, click the Start Backup button to begin the backup. The backup process will first create a persistent image of the system drive (C:), named System Backup. Then it will create the backup images from that persistent image, and then delete that persistent image once the backup operation is complete.

Creating a recovery disk

You will now create a bootable recovery diskette which, when used to boot up the NAS 200, will use the backup location settings you configured on the Disaster Recovery Settings page to locate the backup image and restore it to the system drive of the NAS 200.

1. Insert a blank, formatted diskette in the diskette drive of the NAS 200.

2. On the Disaster Recovery page, click Create Disk.

3. Click OK on the Create Recovery Disk page to create the diskette. The diskette

drive LED will turn off when the creation is complete. The diskette creation should take no more than two minutes.

4. One of the files that is copied onto the diskette is a utility to make it DOS

bootable, called fixboot.exe. From a command prompt, either via the desktop of the NAS 200 itself (with the diskette still in the diskette drive of the NAS 200), or on another system with the diskette in its diskette drive, type a:\fixboot.exe and answer the prompts.

Note: Once you have run fixboot.exe for the diskette, the diskette remains

5. Remove the diskette from the diskette drive (of the NAS 200 itself, or other

system if you used that system to run the fixboot utility). You should label the diskette appropriately and keep it in a safe place.

You may create additional copies of the diskette using the above procedure for each new copy. Note that if you change the backup location or logon settings using the Disaster Recovery Settings page, you will need to rebuild the recovery diskette(s) for that NAS 200 to reflect the new backup location and/or logon settings for that NAS 200.

Static IP addressing

If you do not have a DHCP server on your network, and you must access a backup image that is only accessible via the network (for example, no backup image is located on the maintenance partition [D: drive] of the NAS 200 to be recovered),

40 NAS 200 User’s Reference

bootable unless you format it again (without specifying an option to make it bootable), so if you later erase files on the diskette you do not need to run fixboot.exe again.

then you must configure the recovery diskette so that it will use a static IP address and subnet mask when accessing the network.

On the recovery diskette, edit the file a:\net_sets.bat. Near the top of this file are two lines that begin with rem (comment lines) that, when you uncomment them, set

the IPAddress and SubnetMask environment variables. Change these lines as follows:

1. Uncomment both lines by removing rem from the beginning of both lines.

2. For each line, what follows the equals sign (=) is an IP address expressed as a set of four space-separated numbers (an IP address without the dots [.]). Change the SubnetMask value to match the subnet mask your network uses. Change the IPAddress value to match the IP address you want to assign to the NAS 200, during the recovery operation. Do not insert dots between the numbers (octets) in either value.

As an example, here is how the lines would look for a NAS 200 using IP address

192.168.1.200, and subnet mask 255.255.255.0:

set SubnetMask=255 255 255 0 set IPAddress=192 168 1 200

If you later want to reconfigure the recovery diskette to use DHCP to obtain an IP address instead of static IP addressing, you must reinsert rem in front of the

SubnetMask and IPAddress lines to disable static IP addressing, as follows (based on the previous example):

REM set SubnetMask=255 255 255 0 REM set IPAddress=192 168 1 200

If you have multiple 10/100 Ethernet adapters

If your NAS 200 has more than one 10/100 Ethernet adapter, then you must configure the recovery diskette to select the 10/100 Ethernet adapter to be used for disaster recovery over the network (the network over which the network drive(s) containing backup image(s) can be accessed). On the recovery diskette, edit the file a:\net_sets.bat, and add the following line:

set SLOT=slotvalue where slotvalue is one of the following, depending on the PCI slot (on the rear of

the NAS 200) in which the desired 10/100 Ethernet adapter is installed:

v 0x0009 for PCI slot 1 v 0x000a for PCI slot 2 v 0x0026 for PCI slot 4 v 0x0027 for PCI slot 5

Restoring the system drive

If you need to restore the system drive from a backup image created via the PSM Disaster Recovery panel as described above, you must use a recovery diskette created via the Disaster Recovery panel. If you did not create a recovery diskette then you must use the Recovery CD as described in “Using the Recovery Enablement Diskette and Recovery CD Set” on page 77 to restore the system drive to its original (factory) configuration.

To restore the system drive:

1. Set the write-protect tab of the recovery diskette to the write-protect position. (This is a protection feature to prevent accidental initiation of the recovery process (by booting the NAS 200 with the recovery diskette in the diskette drive).

Chapter 6. Additional administrative functions 41

2. Insert the recovery diskette in the diskette drive of the NAS 200, and restart the NAS 200.

3. The recovery process begins. The recovery diskette software will locate the first backup image it can find, based on the backup locations specified on the Disaster Recovery Settings panel in Microsoft Windows 2000 for NAS when the diskette was created. Once it has located a backup image it will begin restoring the system drive from the image. During the restore operation the hard disk drive LEDs (on the front right of each hard disk drive) will flash green or stay nearly solid green; this indicates write activity to the system volume.

Note: If the hard disk drive LEDs stay off for at least 10 minutes since you

restarted the NAS 200, then there is a problem with the recovery procedure and it will not be able to restore the system volume from a backup image. Should this occur, you will need to use the Recovery CD as described in “Using the Recovery Enablement Diskette and Recovery CD Set” on page 77.

4. When the restore operation completes, the hard disk drive LEDs will turn off, and a short song will play periodically (every 15 seconds). Remove the diskette, set the write-enable tab back to the write-enabled position, and reinsert the diskette. The log file results.htm will be written to the diskette; this log file can be viewed with any Web browser to examine the results of the restore operation.

5. Once the log file is written, another song will play (continuously). Remove the diskette and restart the NAS 200. If the restore was successful, the NAS 200 will come back up in the state it was in at the time you created the backup image used for the recovery operation.

Note: The persistent image that was created on the system drive (named System

Backup) by the backup process is restored by the restore process as it is preserved in the backup image. It is recommended that you now delete that persistent image as it is no longer needed. On the Persistent Images panel, select the persistent image named System Backup on drive C: from the list of persistent images, then click Delete, then click OK on the Delete Persistent Image panel that appears.

If the restore was unsuccessful, then you must use the Recovery CD as described in “Using the Recovery Enablement Diskette and Recovery CD Set” on page 77.

Granting user access to persistent image files

You can give end-users access to files in the persistent images. For example, this would be helpful to a user who has accidentally corrupted a file and needs to get an uncorrupted copy of that file.

To enable end-user access to persistent image files, go into Terminal Services. Once you are in Terminal Services, click the My Computer icon. Next, click the volume on which you want to enable persistent image access. Then, go into the persistent images directory and right-click the mouse on your desired persistent image mount point, select Sharing, then specify sharing as desired. If you want to enable the same access to all persistent images on the volume, you can right-click on the persistent images directory (from the top level of the volume), select

Sharing, and then specify sharing as desired.

42 NAS 200 User’s Reference

PSM notes

Note: The share settings are maintained in a persistent image. Therefore, granting

access to all end-users only permits those users to access files and directories within the persistent image that they would have been able to access originally on the actual drive.

1. As mentioned, you can take and keep a maximum of 250 persistent images. These can be taken on local drives, or drives on the external storage that are logically local.

Note that on various panels, such as the New Persistent Image Schedule panel, you will see a field, Keep the last: (number of persistent images). The total number of persistent images that you enter in these fields will not override the maximum number of persistent images that you set in the Global Settings panel. For example, if your maximum number of persistent images is 10, and you enter in numbers in other fields that add up to greater than 10, only 10 persistent images will be taken.

2. You cannot take a persistent image of the maintenance drive (D:). Hence, you will not see it as a choice in either the New Persistent Image Schedule panel or the Create Persistent Image panel.

3. PSM stores the cache file for each drive on the drive itself. The first persistent image created on a particular drive will take a significant amount of time because the PSM cache file must be created (pre-allocated) for that drive.

The time required for creation depends on the configured size of the cache file (15 percent of the total drive size by default). Creation takes roughly three to four minutes per gigabyte. For example, a 10 GB cache file would take 30 to 40 minutes to create. You should create a persistent image for a drive before scheduling any persistent images for that drive, to build the cache file. You may then delete the persistent image that you just created if you do not need to keep it.

After the creation of the first persistent image on a volume, future persistent images on that volume will complete faster.

4. As mentioned, the default size of the cache file per drive is 15 percent of the total drive capacity. In most cases, that should be sufficient.

However, it is possible that it will not be enough to maintain the number of persistent images you wish to keep concurrently on the drive, given the amount of file-write activity to the drive. PSM will automatically take action to prevent the cache file from overflowing, because if that occurred, PSM would be forced to automatically delete all persistent images on the drive (once it cannot keep track of changes made to the drive, it cannot maintain a valid persistent image).

PSM takes the following actions as the cache file usage approaches a full condition:

v Once the cache file usage exceeds the warning threshold (configured in the

PSM Volumes panel for the drive; the default value is 80 percent), PSM generates a warning message to the system event log (viewable via the Windows 2000 Event Viewer in the IBM NAS Admin console), and to the alert log in the Microsoft Windows 2000 for Network Attached Storage user interface. The name of the source for the message will be psman5. Additionally, while the cache file usage is above the warning threshold, PSM prohibits any attempt to create a new persistent image, and logs an error message (to the system log and alert log). The text of the error message that is logged in the system event log (from psman5)is“A persistent image could not be created due to error 0xe000102b”.

Chapter 6. Additional administrative functions 43

v Once the cache file usage exceeds the automatic deletion threshold (also

configured in the PSM Volumes panel for the drive; the default value is 90 percent), PSM automatically selects a persistent image on the volume and deletes it to reduce the cache file usage. It selects the persistent image with the lowest retention value (as described above in the Persistent Images panel section). If more than one persistent image has the same (lowest) retention value, then the oldest image will be selected for deletion. If this deletion does not reduce the cache file usage below the automatic deletion threshold, then it will continue to select and delete persistent images until the cache file usage is reduced below the automatic deletion threshold. For each deletion, PSM generates an error message to the system event log and to the Windows 2000 for Network Attached Storage alert log indicating that a persistent image was deleted.

You should periodically check the system event log or Windows 2000 for Network Attached Storage alert log to ensure that the cache file usage is not consistently high, forcing existing persistent images to be deleted and preventing new persistent images from being created. If you find that this is the case, you can increase the size of the cache file using the PSM Volumes page, but you will need to delete all persistent images currently on that volume as dynamic cache file resizing is not supported in this release.

5. Volume restore of the system volume (C: drive) is not supported. If you attempt to restore a persistent image containing the system volume, the restore operation will not take place.

6. Volume restore of a data volume may require a reboot of the node. You will be notified by the Restore Persistent Images panel whether a reboot is required after a restore operation is initiated.

Attention: The recovery process invalidates persistent images and leaves them in an inconsistent state. So, if you plan to use the Recovery CD, it is recommended that you first delete all persistent images to ensure a clean reload of the system software. For more information on using the Recovery CD, see “Using the Recovery Enablement Diskette and Recovery CD Set” on page 77.

Ethernet adapter teaming

This section describes how to enable adapter teaming on the Intel and Alacritech Ethernet adapters.

Intel Ethernet adapter teaming

The Ethernet adapters (Gb Ethernet SX and 10/100 Ethernet) that you install in the PCI slots of the NAS 200 support adapter teaming. With adapter teaming, two or more PCI Ethernet adapters can be physically connected to the same IP subnetwork and then logically combined into an adapter team. Such a team can support one of the following functional modes:

Fault tolerance

In fault tolerance mode, only one adapter in the team is fully active on the Ethernet network (for example, sending and receiving data) at any point in time, while the other adapters are in standby mode (receiving data only). If that adapter detects a link failure or fails completely, another adapter in the team automatically and rapidly takes over as the active adapter, and all Ethernet traffic being handled by the failing adapter is seamlessly switched to the new active adapter, with no interruption to network sessions (for example, file transfers) in progress at the time of the failover.

44 NAS 200 User’s Reference

Load balancing

In load balancing mode, all adapters in the team are active, increasing the total transmission throughput over the common IP subnetwork. If any adapter in the team fails (link failure or complete failure), the other adapters in the team continue to share the network transmission load, although total throughput is decreased. Load balancing is only supported for adapter teams consisting of only one type of adapter; different types of adapters cannot be combined in a load balancing team.

You configure adapter teaming with Intel PROSet II, which is preloaded on the NAS 200, as follows:

1. On the NAS 200, physically connect the adapters that you wish to team to the same IP subnetwork.

2. Access the NAS 200 desktop by directly attaching a keyboard, mouse, and monitor, or over the network by starting Terminal Services on another workstation. (For instructions on how to invoke Terminal Services, see “Terminal Services and the IBM NAS Administration Console” in Chapter 3 of the User’s Reference.

3. From the NAS 200 desktop, go to the Start menu, then select Settings, then select Control Panel.

4. Double-click the Intel PROSet II icon in the Control Panel to start Intel PROSet II.

5. You will see a list of all adapters for each slot and type supported under Network Components.

6. Under Network Components, you will see a list of resident and non-resident adapters for each slot and type supported under Network Components. Drivers are preset for all supported adapter configurations, but will be loaded only for resident adapters.

7. Identify which adapters you are going to team. You do this by left-clicking the adapter under Network Components, and selecting one of the adapters that will be part of the teaming.

8. Right click the adapter, then select Add to Team, then select Create New

Team....

9. Select the type of team you wish to create.

10. Select the adapters for the team you are creating by selecting the check box for the appropriate adapters in the list, and then select Next.

11. Verify that these settings are correct, and then select Finish.

The procedure creates a device named Intel Advanced Network Services Virtual Adapter. It also binds all network protocols that were bound to the physical adapters that were added to the team to this virtual adapter, and unbinds those protocols from the physical adapters. If you delete the team, the settings will return to the state prior to creating the team.

For complete help on adapter teaming, from Intel PROSet II click Network

Components, and then select Help from the Help menu.

Alacritech Ethernet adapter teaming

The Quad-port 10/100 Ethernet Adapter supports the Cisco Fast EtherChannel (FEC) technology across the four ports on the adapter. You can configure it by clicking successively on Control Panel→Network→Adapter→Properties→Teaming in

the Windows interface.

Chapter 6. Additional administrative functions 45

Fast Etherchannel (FEC) is a proprietary technology developed by Cisco. With FEC, you can create a team of two to four ports on the Quad-port 10/100 Ethernet PCI Adapter in to increase transmission and reception throughput. This feature may also be referred to as load balancing, port aggregation, or trunking. When you configure this feature, the adapter ports comprising the FEC team or group create a single high-speed, fault-tolerant link between the engine and the Ethernet switch sharing one IP address. With FEC, fault tolerance and load balancing is provided for both outbound and inbound traffic, unlike other load balancing schemes that only balance outbound traffic.

FEC requires an Ethernet switch with FEC capability. The FEC implementation on the Quad-port 10/100 Ethernet Adapter does not support the optional Port Aggregation Protocol (PAgP) feature of FEC-capable Ethernet switches.

46 NAS 200 User’s Reference

Chapter 7. Troubleshooting

This chapter provides basic troubleshooting information to help you resolve some common problems that might occur with your NAS 200. The chapter is divided into:

v “Engine troubleshooting and diagnostics” v “Adapter troubleshooting and diagnostics” on page 62

If you cannot locate and correct the problem using the information in this section, refer to “Appendix B. Getting help, service, and information” on page 83 for more information.

Engine troubleshooting and diagnostics

This section gives troubleshooting information for the IBM 5187 Network Attached Storage Model 6RZ (engine).

Engine diagnostic tools overview

The following tools are available to help you identify and resolve hardware-related problems:

v POST beep codes, error messages, and error logs

The power-on self-test (POST) generates beep codes and messages to indicate successful test completion or the detection of a problem. See “Power-on self-test (POST)” on page 87 for more information.

POST error messages and descriptions are given in “Appendix C. Engine POST messages” on page 87.

v Diagnostic programs and error messages

The diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of your appliance. See “POST diagnostic programs” on page 97 for more information.

v Light-path diagnostics

Your appliance has light-emitting diodes (LEDs) to help you identify problems with appliance components. These LEDs are part of the light-path diagnostics that are built into your appliance. By following the path of lights, you can quickly identify the type of system error that occurred. See “Light-path diagnostics” on page 50 for more information.

v Intel

v Troubleshooting charts

v Support

PROSet II

See “Testing the Ethernet adapters with Intel PROSet II” on page 65.

These charts list problem symptoms, along with suggested steps to correct the problems. See “Engine troubleshooting charts” on page 52 for more information.

You can register with the following support site to subscribe to e-mail notification of new technical tips and frequently asked questions, obtain downloads, and join forum discussions:

http://www.ibm.com/storage/support/nas

Identifying problems using LEDs

The LEDs are part of the light-path diagnostics built into the NAS 200 engine. The LEDs help you identify the type of system error that occurred. See the following sections for more information.

Power-supply LEDs

The AC and DC power LEDs on the power supply provide status information about the power supply.

Table 3 on page 49 describes the AC and DC power LEDs. Note: The minimum configuration required for the DC good light to come on is:

v Power supply v Power backplane v System board (with pins 2 and 3 on J23 extension cable connected

together to bypass the power switch.

48 NAS 200 User’s Reference

Table 3. Power-supply LEDS

AC Good LED

Off Off No power to system

On Off Standby mode or DC

DC Good LED

Description FRU/action

or AC problem.

problem.

1. Check AC power to system.

2. Power supply

1. Check system board cable

2. Remove the adapters and

3. Power supply

4. Power backplane

5. System board

On On Power is OK. N/A

connectors J32, J33, and J35.

Move jumper on J32’s extension cable to pins 2-3 to bypass power control. If the DC Good LED comes on, press Ctrl+Alt+Delete. Watch the screen for any POST errors. Check the System Event/Error Log for any listed problems. If the system powers up with no errors: a. Power switch assembly b. System board

disconnect the cables and power connectors to all internal and external devices. Power-on the system. If the DC Good LED comes on, replace the adapters and devices one at a time until you isolate the problem.

Chapter 7. Troubleshooting 49

Light-path diagnostics

You can use the light-path diagnostics built into the NAS 200 engine to identify the type of system error that occurred. Any LEDs that are illuminated remain illuminated during a shutdown as long as the AC power source is good and the power supplies can supply +5V DC current to the NAS 200 engine. This feature helps you isolate the problem, if an error causes the NAS 200 to shut down. See “Light-path diagnostics”.

Diagnostics panel

You can use the light path diagnostics to quickly identify the type of system error that occurred. The diagnostics panel is under the “wind tunnel”. Any LEDs that are On, remain On when the NAS 200 shuts down as long as the AC power source is stable and the power supplies can provide +5V DC current. This feature helps isolate the problem if an error causes the NAS 200 to shut down.

Figure 1 shows the LEDs on the diagnostics panel on the system board. You need to remove the top cover to view the LEDs.

See “Light-path diagnostics” for information on identifying problems using these LEDs.

MEM

PS1

CPU

PS2

PCI A

PS3

PCI B

NON

PCI C

OVER

VRM

NMI

DASD

TEMP

FAN

REMIND

Figure 1. Diagnostics panel LEDs

Light-path diagnostics

Table 4 on page 51 describes the light-path diagnostics LEDs. The system error LED is turned on when an error is detected. If the system error LED (an amber “!” on the lower right corner) is on, remove the cover and check the diagnostic panel LEDs. Table 4 on page 51 is valid only when the system error LED is on.

Notes:

1. If a diagnostic panel LED is on and the information LED panel system error LED is off, there is probably an LED problem. Run LED diagnostics.

2. Check the System Error Log for additional information before replacing a FRU.

3. The DIMM error LEDs, processor error LEDs, and VRM error LEDs turn off when the system is powered off.

50 NAS 200 User’s Reference

Table 4. Descriptions of light-path diagnostics LEDs

LED Meaning

PS1 Power supply 1 failure PS2 Power supply 2 failure PS3 Power supply 3 failure NON Non-redundant power OVER The system has exceeded the power capabilities of the installed power supplies NMI Non-maskable-interrupt occurred TEMP System temperature exceeded maximum rating FAN A fan failed or is operating slowly MEM Memory failure. One or more memory DIMMs have failed CPU Microprocessor failure. One or both microprocessors have failed PCI A Error on PCI channel A or system board. Note: PCI bus A is often referred to as PCI bus 0 PCI B Error on PCI channel B or system board. Note: PCI bus B is often referred to as PCI bus 1 PCI C Error on PCI channel C or system board. Note: PCI bus C is often referred to as PCI bus 2 VRM VRM Error on voltage regulator module or on integrated voltage regulator DASD A hot-swap disk drive, backplane, or other part of SCSI channel A has failed SP Integrated System Management Processor detected an error

Remind button: You can use the remind button to place the front panel system-error light into a remind mode. By pressing the button, you acknowledge the failure but indicate that you will not take immediate action. If a new error occurs, the LED will be on again.

In the remind mode, the system-error LED flashes every 2 seconds. The system-error LED remains in remind mode until one of the following situations occurs:

1. All known problems are resolved

2. The system is restarted

3. A new problem occurs You can use the remind button to delay maintenance. Also, resetting the

system-error LED enables the LED to react to another error. If the LED is still blinking from the first error, it will mask additional errors.

Chapter 7. Troubleshooting 51

Engine troubleshooting charts

You can use Table 5 to find solutions to problems that have the described symptoms.

If you cannot find the problem in the table, go to “Starting the diagnostic programs”

on page 98 to test the appliance. If you have run the diagnostic test programs or if

running the tests does not reveal the problem, call for service. The symptom appears in the left column of the table. Instructions and probable

solutions to the problem are in the right column. If you have just added new software or a new option and your appliance is not working, do the following before using the troubleshooting charts:

v Remove the software or device that you just added. v Run the diagnostic tests to determine if your appliance is running correctly. v Reinstall the new software or new device.

Table 5. Engine troubleshooting symptoms and suggested actions

Device/Problem Symptom Suggested action CD-ROM drive CD-ROM drive is not

recognized.

Verify that:

1. The primary IDE channel is enabled in the Configuration/Setup Utility program.

2. All cables and jumpers are installed correctly.

3. The correct device driver is installed for the CD-ROM drive.

Diskette drive Diskette drive in-use

light stays on, or the system bypasses the diskette drive.

Expansion enclosure problems

General problems Problems such as

SCSI expansion enclosure used to work, but does not work now.

broken cover locks or indicator lights not working.

If the problem remains, call for service. If there is a diskette in the drive, verify that:

1. The diskette drive is enabled in the Configuration/Setup Utility program.

2. The diskette is good and not damaged. (Try another diskette if you have one.)

3. The diskette contains the necessary files to start the appliance.

4. Your software program is OK.

If the diskette drive in-use light stays on, or the system continues to bypass the diskette drive, call for service.

Verify that:

1. The cables for all external SCSI options are connected correctly.

2. The last option in each SCSI chain, or the end of the SCSI cable, is terminated correctly.

3. Any external SCSI option is turned on. You must turn on an external SCSI option before turning on the appliance.

For more information, see your SCSI and expansion enclosure documentation.

Call for service.

52 NAS 200 User’s Reference

Table 5. Engine troubleshooting symptoms and suggested actions (continued)

Device/Problem Symptom Suggested action Intermittent problems A problem occurs only

occasionally and is difficult to detect.

Verify that:

1. All cables and cords are connected securely to the rear of the appliance and attached options.

2. When the appliance is turned on, air is flowing from the rear of the appliance at the fan grill. If there is no air flow, the fan is not working. This causes the appliance to overheat and shut down.

3. Ensure that the SCSI bus and devices are configured correctly and that the last external device in each SCSI chain is terminated correctly.

If the items above are correct, call for service.

Keyboard, mouse, or pointing-device problems (if attached).

All or some keys on the keyboard do not work.

1. Make sure that the keyboard cable is properly connected to the appliance.

2. Make sure that the appliance and the monitor are turned on.

3. Try using another keyboard.

If the items above are correct, call for service.

The mouse or pointing device does not work.

1. Verify that the mouse or pointing-device cable is securely connected and the device drivers are installed correctly.

2. Try using another mouse or pointing device.

If the problem remains, call for service.

Memory problems The amount of memory

displayed is less than the amount of memory installed.

Verify that:

1. The memory modules are seated properly.

2. You have installed the correct type of memory.

3. If you changed the memory, you updated the memory configuration with the Configuration/Setup Utility program.

4. All banks of memory on the DIMMs are enabled. The appliance might have automatically disabled a DIMM bank when it detected a problem or a DIMM bank could have been manually disabled.

Microprocessor problems

The appliance emits a continuous tone during POST.

If the above items are correct, run the memory diagnostic program. The system might have detected a bad memory module and automatically reallocated memory to enable you to continue to operate. If the memory tests fail, call for service or replace the failing DIMM.

The startup (boot) microprocessor is not working properly. Verify that the startup microprocessor is seated properly. If it is,

replace the startup microprocessor. If the problem remains, call for service.

Chapter 7. Troubleshooting 53

Table 5. Engine troubleshooting symptoms and suggested actions (continued)

Device/Problem Symptom Suggested action Monitor Testing the monitor. Some IBM monitors have their own self-tests. If you suspect a

problem with your monitor, refer to the information that comes with the monitor for adjusting and testing instructions.

If you still cannot find the problem, call for service.

The screen is blank. Verify that:

1. The appliance power cord is plugged into the appliance and a working electrical outlet.

2. The monitor cables are connected properly.

3. The monitor is turned on and the Brightness and Contrast controls are adjusted correctly.

If the items above are correct and the screen remains blank, call for service.

Only the cursor appears.

The monitor works when you turn on the appliance, but goes blank when you start some application programs.

Wavy, unreadable, rolling, distorted screen, or screen jitter.

Call for service.

Verify that:

1. The primary monitor cable is connected to the video port.

2. You installed the necessary device drivers for the applications.

If the items above are correct and the screen remains blank, call for service.

If the monitor self-tests show the monitor is OK, consider the location of the monitor. Magnetic fields around other devices (such as transformers, appliances, fluorescent lights, and other monitors) can cause screen jitter or wavy, unreadable, rolling, or distorted screen images. If this happens, turn off the monitor. (Moving a color monitor while it is turned on might cause screen discoloration.) Then move the device and the monitor at least 305 mm (12 in.) apart. Turn on the monitor.

Notes:

1. To prevent diskette drive read/write errors, be sure the distance between monitors and diskette drives is at least 76 mm (3 in.).

2. Non-IBM monitor cables might cause unpredictable problems.

3. An enhanced monitor cable with additional shielding is available for the 9521 and 9527 monitors. For information about the enhanced monitor cable, see your IBM reseller or IBM marketing representative.

Wrong characters appear on the screen.

54 NAS 200 User’s Reference

If the problem remains, call for service. If the wrong language is displayed, update the BIOS with the

correct language. If the problem remains, call for service.

Table 5. Engine troubleshooting symptoms and suggested actions (continued)

Device/Problem Symptom Suggested action Option problems An IBM option that was

just installed does not work.

Verify that:

1. The option is designed for the appliance. Refer to the hardware installation guide that came with this appliance for a list of supported options.

2. You followed the installation instructions that came with the option.

3. The option is installed correctly.

4. You have not loosened any other installed options or cables.

5. You updated the configuration information in the Configuration/Setup Utility program. Whenever memory or an option is changed, you must update the configuration.

If the problem remains, call for service.

An IBM option that used to work does not

Verify that all of the option hardware and cable connections are secure.

work now.

If the option comes with its own test instructions, use those instructions to test the option.

If the failing option is a SCSI option, verify that:

1. The cables for all external SCSI options are connected correctly.

2. The last option in each SCSI chain, or the end of the SCSI cable, is terminated correctly.

3. Any external SCSI option is turned on. You must turn on an external SCSI option before turning on the appliance.

Power problems The appliance does not

power on.

Serial port problems The number of serial

ports identified by the operating system is less than the number of serial ports installed.

If the problem remains, call for service. Verify that:

1. The power cables are properly connected to the appliance.

2. The electrical outlet functions properly.

3. The type of memory installed is correct.

4. If you just installed an option, remove it, and restart the appliance. If the appliance now powers on, you might have installed more options than the power supply supports.

5. The LEDs on the power supply are on.

If the problem remains, call for service. Verify that:

1. Each port is assigned a unique address by the Configuration/Setup Utility program and none of the serial ports are disabled. Note: The management C connector is the same as a serial port connector, but it is used only by the ISMP, and is not available for use by the operating system. This port does not appear in the Configuration/Setup Utility program menus; it can be configured using Netfinity Manager.

2. The serial-port adapter, if you installed one, is seated properly.

If the problem still exists, call for service.

Chapter 7. Troubleshooting 55

Table 5. Engine troubleshooting symptoms and suggested actions (continued)

Device/Problem Symptom Suggested action

A serial device does not work.

Service processor problems

Software problem Suspected software

Netfinity Service Processor Manager reports a general monitor failure

problem.

Verify that:

1. The device is compatible with the appliance.

2. The serial port is enabled and is assigned a unique address.

3. Make sure that the device is not connected to the management port C. Note: The management C connector is the same as a serial port connector, but it is used only by the ISMP, and is not available for use by the operating system. This port does not appear in the Configuration/Setup Utility program menus; it can be configured using Netfinity Manager.

If the problem still exists, call for service. Disconnect the appliance from all electrical sources, wait for 30

seconds, reconnect the appliance to the electrical sources, and restart the appliance.

If a problem remains, call for service. To determine if problems are caused by the software, verify that:

1. Four appliance has the minimum memory requirements needed to use the software. For memory requirements, refer to the information that comes with the software. Note: If you have just installed an adapter or memory, you might have a memory address conflict.

2. The software is designed to operate on your appliance.

3. Other software works on your appliance.

4. The software that you are using works on another system.

Universal Serial Bus (USB) port problems

A USB device does not work.

If you received any error messages when using the software program, refer to the information that comes with the software for a description of the messages and solutions to the problem.

If the items above are correct and the problem remains, contact your place of purchase.

Verify that:

1. You are not trying to use a USB device during POST if you have a standard (non-USB) keyboard attached to the keyboard port. Note: If a standard (non-USB) keyboard is attached to the keyboard port, then the USB is disabled and no USB device will work during POST.

2. The correct USB device driver is installed.

3. Your operating system supports USB devices.

If the problem still exists, call for service.

56 NAS 200 User’s Reference

Power problems

Power problems can be difficult to troubleshoot. For example, a short circuit can exist anywhere on any of the power distribution busses. Usually a short circuit causes the power subsystem to shut down because of an overcurrent condition.

Table 6 lists the power error messages that you might encounter. A general procedure for troubleshooting power problems is as follows:

1. Power off the system and disconnect the AC cord(s).

2. Check for loose cables in the power subsystem. Also check for short circuits, for example, if there is a loose screw causing a short circuit on a circuit board.

3. Remove adapters and disconnect the cables and power connectors to all internal and external devices until the NAS 200 engine is at minimum configuration required for power on.

4. Reconnect the AC cord and power on the NAS 200 engine. If the engine powers up successfully, replace adapters and devices one at a time until the problem is isolated. If the engine does not power up from minimal configuration, replace FRUs of minimal configuration one at a time until the problem is isolated.

Table 6. Power error messages

Message Action Power supply ″X″ current share fault

(level-critical; excessive current demand on power supply ″X″)

Power supply ″X″ DC good fault

(level-critical; power good signal not detected for power supply ″X″)

Power supply ″X″ temperature fault Power supply ″X″ removed Power supply ″X″ fan fault (level-critical;

fan fault in power supply ″X″) Power supply ″X″ 12V fault (level-critical;

overcurrent condition detected) Power supply ″X″ 3.3V fault (level-critical;

3.3V power supply ″X″ had an error) Power supply ″X″ 5V fault (level-critical; 5V

power supply ″X″ had an error)

System over recommended ″X″ current

(level-non-critical; system running too much current on that voltage)

System running non-redundant power

(level-non-critical; system does not have redundant power)

System under recommended voltage for

″X″ v (level-warning; indicated voltage supply under nominal value; value for ″X″ can be +12, -12, or +5)

1. See “Power problems”

1. Replace power supply ″X″

1. Replace fan ″X″

1. No action required - information only

1. Replace power supply ″X″

1. See “Power problems”

1. Add another power supply

2. Remove options from system

3. System can continue to operate without redundancy protection if 1

1. Check connections to power subsystem

2. Replace power supply

3. Replace power backplane

and 2 above are not followed.

Chapter 7. Troubleshooting 57

Table 6. Power error messages (continued)

Message Action System under recommended voltage on

3.3 v (level-warning; 3.3 volt supply under

nominal value)

System under recommended X current

(level-non-critical; system drawing less current than recommended on voltage ″X″)

″X″ V bus fault (level-critical; overcurrent condition on ″X″ voltage bus)

12V ″X″ bus fault (level-critical; overcurrent condition on 12 volt ″X″ voltage bus)

5V fault (level-critical; overcurrent condition on 5 V subsystem)

240 VA fault (level-critical; overcurrent or overvoltage condition in power subsystem)

1. Check connections to power subsystem

2. Replace power supply

3. Replace power backplane

1. See “Power problems” on page 57

1. Check for short circuit on ″X″ voltage bus

2. See “Power problems” on page 57

1. Check for short circuit on 12 volt ″X″ voltage bus

2. See “Power problems” on page 57

1. Check for short circuit on5vbus

2. See “Power problems” on page 57

1. See “Power problems” on page 57

Recovering BIOS

If your BIOS has become corrupted, such as from a power failure during a flash update, you can recover your BIOS using the recovery boot block and a BIOS flash diskette.

Note: Note: You can obtain a BIOS flash diskette from one of the following

sources: v Download a BIOS flash diskette from the Web site at

http://www.ibm.com/storage/support/nas

v Contact your IBM service representative.

The flash memory contains a protected area that cannot be overwritten. The recovery boot block is a section of code in this protected area that enables the NAS 200 to start up and to read a flash diskette. The flash utility recovers the system BIOS from the BIOS recovery files on the diskette.

To recover the BIOS:

1. Power off the NAS 200 and peripheral devices. Disconnect all external cables and power cords. Remove the cover.

2. Locate the boot-block jumper block (J16) on the system board. See Figure 2

on page 59.

3. Place a jumper on pins 2 and 3 to enable the BIOS backup page.

4. Insert the BIOS flash diskette into the diskette drive.

5. Restart the NAS 200.

6. When the NAS 200 completes POST, select 1 -- Update POST/BIOS from the menu that contains various flash (update) options.

7. When you are asked if you would like to move the current POST/BIOS image to the backup ROM location, type N. Attention: Typing Y will copy the corrupted BIOS into the secondary page.

8. When you are asked if you would like to save the current code on a diskette, select N.

58 NAS 200 User’s Reference

9. You will be asked to choose the language you wish to use. Select your language (0-7) and press Enter to accept your choice. You will be prompted to remove the diskette and press Enter to restart the system. Remove the flash diskette from the diskette drive.

10. Power off the NAS 200.

11. Remove the jumper on the boot-block jumper block, or move it to pins 1 and 2 to return to normal startup mode.

12. Restart the NAS 200. It should start up normally.

Figure 2 shows the location of the boot block jumper on the system board.

System board Switch block (SW1)

SW1

1 2 3 4 5 6 7 8

Figure 2. Boot block jumper location

Replacing the battery

IBM has designed this product with your safety in mind. The lithium battery must be handled correctly to avoid possible danger. If you replace the battery, you must adhere to the following instructions.

Note: In the U.S., call 1-800-IBM-4333 for information about battery disposal. If you replace the original lithium battery with a heavy-metal battery or a battery with

heavy-metal components, be aware of the following environmental consideration. Batteries and accumulators that contain heavy metals must not be disposed of with normal domestic waste. They will be taken back free of charge by the manufacturer, distributor, or representative, to be recycled or disposed of in a proper manner.

To order replacement batteries, call 1-800-772-2227 within the United States, and 1-800-465-7999 or 1-800-465-6666 within Canada. Outside the U.S. and Canada, call your IBM reseller or IBM marketing representative.

Flash boot block recovery jumper (J16)

Note: After you replace the battery, you must reconfigure your appliance and reset

the system date and time.

Chapter 7. Troubleshooting 59

CAUTION:

When replacing the lithium battery, use only IBM Part Number 10L6432 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.

Do not:

v Throw or immerse into water. v Heat to more than 100 C (212 F) v Repair or disassemble

Dispose of the battery as required by local ordinances or regulations. Note: For translations of the safety notice, refer to the multilingual Safety Information on the

Documentation CD that came with the appliance.

To replace the battery:

1. Review the information in the section “Before you begin” in the hardware installation guide that came with this appliance, and any special handling and installation instructions supplied with the replacement battery.

2. Turn off the appliance and peripheral devices and disconnect all external cables and power cords; then, remove the appliance cover.

3. Remove the battery: a. Use one finger to lift the battery clip over the battery. b. Use one finger to slightly slide the battery from its socket. The spring

mechanism behind the battery will push the battery out toward you as you slide it from the socket.

c. Use your thumb and index finger to pull the battery from under the battery

clip.

d. Ensure that the battery clip is touching the base of the battery socket by

pressing gently on the clip.

Figure 3. Battery removal

4. Insert the new battery: a. Tilt the battery so that you can insert it into the socket, under the battery

clip.

b. As you slide it under the battery clip, press the battery down into the socket.

60 NAS 200 User’s Reference

Figure 4. Battery replacement

5. Reinstall the appliance cover and connect the cables. Note: Wait approximately 20 seconds after you plug the power cord of your

appliance into an electrical outlet for the Power Control button to become active.

6. Turn the appliance on.

7. Start the Configuration/Setup Utility program and set configuration parameters.

v Set the system date and time. v Set the power-on password. v Reconfigure your appliance.

Chapter 7. Troubleshooting 61

Adapter troubleshooting and diagnostics

This section presents information on troubleshooting and diagnosing the following engine adapters:

v 10/100 integrated Ethernet adapter v IBM 10/100 PCI Ethernet adapter v IBM Gigabit Ethernet SX adapter v Intel PRO 1000 XT Server Adapter v Alacritech Quad-Port Ethernet Adapter v IBM ServeRAID-4Lx and 4H SCSI Controller v Integrated System Management Processor (ISMP) v Remote Supervisor Adapter (RSA) v IBM Fast/Wide Ultra SCSI Adapter v IBM PCI Ultra 160 SCSI Adapter

Integrated Ethernet adapter

This section provides troubleshooting information for problems that might occur with the 10/100 Mbps integrated Ethernet adapter.

Network connection problems

If the Ethernet adapter cannot connect to the network, check the following: v Make sure that the cable is installed correctly.

The network cable must be securely attached at all connections. If the cable is attached but the problem persists, try a different cable.

If you set the Ethernet adapter to operate at 100 Mbps, you must use Category 5 cabling.

If you directly connect two workstations (without a hub), or if you are not using a hub with X ports, use a crossover cable.

Note: To determine whether a hub has an X port, check the port label. If the

label contains an X, the hub has an X port.

v Determine if the hub supports auto-negotiation. If not, try configuring the

integrated Ethernet adapter manually to match the speed and duplex mode of the hub.

v Check the Ethernet adapter lights on the operator information panel.

These lights indicate whether a problem exists with the connector, cable, or hub. – The Ethernet Link Status light is On when the Ethernet adapter receives a

LINK pulse from the hub. If the light is Off, there might be a bad connector or cable, or a problem with the hub.

– The Ethernet Transmit/Receive Activity light is On when the Ethernet adapter

sends or receives data over the Ethernet Network. If the Ethernet Transmit/Receive Activity light is Off, make sure that the hub and network are operating and that the correct device drivers are loaded.

v Make sure that you are using the correct device drivers, supplied with the NAS

200 engine.

v Check for operating system-specific causes for the problem. v Make sure that the device drivers on the client and the NAS 200 engine are

using the same protocol.

v Test the Ethernet adapter by running the diagnostic program.

62 NAS 200 User’s Reference

Integrated Ethernet adapter troubleshooting chart

Use Table 7 to find solutions to 10/100 Mbps integrated Ethernet adapter problems that have definite symptoms.

Table 7. Integrated Ethernet adapter troubleshooting chart

Ethernet adapter problem Suggested Action

Ethernet Link Status light is not On.

The Ethernet Transmit/Receive Activity light is not On.

Data errors Check the following:

The Ethernet adapter stopped working when another adapter was added to the NAS 200 engine.

Check the following:

v Ensure that the hub is powered on. v Check all connections at the Ethernet adapter and the hub. v Check the cable. A crossover cable is required unless the hub has an X

designation.

v Use another port on the hub. v If the hub does not support auto-negotiation, manually configure the Ethernet

adapter to match the hub.

v If you manually configured the duplex mode, ensure that you also manually

configure the speed.

v Run diagnostics on the LEDs. If the problem remains, go to “Starting the diagnostic programs” on page 98 to run

the diagnostic programs. Check the following:

Note: The Ethernet Transmit/Receive Activity LED is On only when data is sent to or by this Ethernet adapter.

v Ensure that you have loaded the network device drivers. v The network might be idle. Try sending data from this workstation. v Run diagnostics on the LEDs. v The function of this LED can be changed by device driver load parameters. If

necessary, remove any LED parameter settings when you load the device drivers.

v Ensure that you are using Category 5 cabling when operating the NAS 200 engine

at 100 Mbps.

v Make sure that the cables do not run close to noise-inducing sources like

fluorescent lights.

Check the following:

v Ensure that the cable is connected to the Ethernet adapter. v Ensure that the PCI system BIOS is current. v Reseat the adapter. v Ensure that the adapter you are testing is supported by the NAS 200 engine.

Go to “Starting the diagnostic programs” on page 98 to run the diagnostic programs.

The Ethernet adapter stopped working without apparent cause.

Check the following:

v Run diagnostics for the Ethernet adapter. v Try a different connector on the hub. v Reinstall the device drivers. Refer to your operating-system documentation and to

If the problem remains, go to “Starting the diagnostic programs” on page 98 to run the diagnostic programs.

the User’s Reference information.

Chapter 7. Troubleshooting 63

Troubleshooting the 10/100 PCI Ethernet adapter

You can use Table 8 to find solutions to 10/100 Mbps Ethernet adapter problems that have definite symptoms.

See “Testing the Ethernet adapters with Intel PROSet II” on page 65 for information on testing the adapter.

Table 8. 10/100 PCI Ethernet adapter troubleshooting chart

Ethernet adapter problem Suggested Action

The adapter cannot connect to the network.

Diagnostics pass, but the connection fails or errors occur.

Check the following:

1. Ensure that the network cable is installed correctly. The cable must be securely

attached at both RJ-45 connections (adapter and hub). The maximum allowable distance from adapter to the hub is 100 m (328 ft.). If the cable is attached and the distance is within acceptable limits but the problem persists, try a different cable. If you are directly connecting two computers without a hub or switch, make sure you are using a crossover cable.

2. Check the LED lights on the adapter. The adapter has two diagnostic LEDs, one

on each side of the cable connector. These lights help you to determine whether there is a problem with the connector, cable, switch, or hub.

ACT/LNK — On

v Adapter and switch is receiving power and cable connection between

them is good

ACT/LNK — Off

Check the following:

v Adapter not sending or receiving data v Adapter or switch not receiving power v Cable connection between adapter and switch is faulty v Drivers not configured properly

ACT/LNK — Flashing

Normal operation. LED flashes when the adapter sends or receives data. The frequency of the flashes varies with the amount of network traffic

100 — On

Adapter is operating at 100 Mbps

100 — Off

Adapter is operating at 10 Mbps

3. Ensure that you are using the correct drivers. Ensure that you are using the

drivers that come with this adapter. Drivers that support previous versions of this adapter do not support this version of the adapter.

4. Ensure that the switch port and the adapter have the same duplex setting. If you

configured the adapter for full-duplex, ensure that the switch port is also configured for full-duplex. Setting the wrong duplex mode can degrade performance, cause data loss, or result in lost connections.

Check the following:

1. For 100 Mbps:

v Use Category 5 cabling and ensure that the network cable is securely

attached.

v Verify the adapter is seated firmly in the slot and connected to a 100BASE-TX

hub/switch (not 100BASE-T4).

2. Ensure the duplex mode setting on the adapter matches the setting on the switch

64 NAS 200 User’s Reference

Table 8. 10/100 PCI Ethernet adapter troubleshooting chart (continued)

Ethernet adapter problem Suggested Action

The LNK LED is not On. Check the following:

1. Ensure that you loaded the correct network drivers.

2. Check all connections at the adapter and the switch.

3. Try another port on the switch.

4. Ensure that the duplex mode setting on the adapter matches the setting on the switch.

5. Ensure that you have the correct type of cable between the adapter and the hub. 100BASE-TX requires two pairs. Some hubs require a crossover cable while others require a straight-through cable.

The ACT LED is not On. Check the following:

1. Ensure that you loaded the correct network drivers.

2. The network might be idle. Try accessing a server.

3. The adapter is not transmitting or receiving data. Try another adapter.

4. Ensure that you are using two-pair cable for TX wiring.

Adapter stops working without apparent cause.

The LNK LED is not On when you connect the power.

Check the following:

1. Run the diagnostics.

2. Try reseating the adapter in its slot, or try a different slot if necessary.

3. The network driver files might be corrupt or missing. Remove and then reinstall the drivers.

Check the following: Ensure that the network cable is securely attached at both ends.

Testing the Ethernet adapters with Intel PROSet II

Each NAS 200 engine comes with Intel PROSet II. You can use PROSet to view the following:

v Adapter parameters such as MAC and IP addresses v Network link status such as speed, duplex mode, and activity v Device-driver level used for the adapter

You can also use PROSet II to test the 10/100 Ethernet and Gigabit Ethernet PCI adapters for any problems with the adapter hardware, cabling, or network connections. PROSet performs a loopback test on the 10/100 Ethernet and Gigabit Ethernet PCI cards.

To access the PROSet II utility, go into Terminal Services. For instructions on how to invoke Terminal Services, see “Terminal Services and the IBM NAS

Administration Console” on page 8. Within Terminal Services do the following steps:

1. Go to the Start menu, select Settings, then Control Panel.

2. Double-click the INTEL PROSet II icon in the Control Panel to start the INTEL PROSet II utility.

3. In the INTEL PROSet II utility, select the Ethernet adapter you want to test (Gigabit Ethernet PCI adapter or 10/100 Ethernet Adapter).

4. Select the Diagnostics tab. A list of available tests is displayed.

5. Select Run Tests. You can also select or deselect individual tests with the check boxes. If an error is detected, information about the error is displayed.

6. Repeat Steps 3 through 5 for each Ethernet adapter installed.

Chapter 7. Troubleshooting 65

For additional information about Intel PROSet, please refer to the online help that accompanies the utility.

Gigabit Ethernet SX adapter

Use Table 9 to find solutions to Gigabit Ethernet adapter problems that have definite symptoms.

See “Testing the Ethernet adapters with Intel PROSet II” on page 65 for information on testing the adapter.

Table 9. Gigabit Ethernet SX adapter troubleshooting chart

Gigabit adapter problem Suggested Action

No Link or TX/RX Activity If you cannot link to your switch, check the following:

1. Check the following LED lights on the adapter:

TX — On

The adapter is sending data

RX — On

The adapter is receiving data.

Link — On

The adapter is connected to a valid link partner and is receiving link pulses.

Link — Off

Link is inoperative.

v Check all connections at the adapter and link partner v Make sure the link partner is set to 1000 Mbps and full-duplex v Ensure the required drivers are loaded

PRO — Programmable LED

Identifies the adapter by blinking. Use the Identify Adapter push-button in INTEL PROSet II to control blinking.

2. Ensure that the cable is installed correctly. The network cable must be securely attached at all connections. If the cable is attached but the problem persists, try a different cable.

Your computer cannot find the Gigabit Ethernet SX adapter

Diagnostics pass but the connection fails

Another adapter stopped working after you installed the Gigabit Ethernet SX Adapter

The adapter stopped working without apparent cause

Check the following:

1. Verify that the adapter is seated firmly in the slot

2. Try a different Gigabit Ethernet SX adapter

Check the following: Ensure the network cable is securely attached

Check the following:

1. Verify that the cable is connected to the Gigabit Ethernet SX Adapter and not to another adapter.

2. Check for a resource conflict

3. Ensure both adapters are seated firmly in the slot

4. Check all cables

Check the following:

1. Try reseating the adapter

2. The network driver files might be damaged or deleted. Reinstall the drivers

3. Try a different Gigabit Ethernet SX Adapter

66 NAS 200 User’s Reference

Table 9. Gigabit Ethernet SX adapter troubleshooting chart (continued)

Gigabit adapter problem Suggested Action

LINK LED is not On Check the following:

1. Ensure that you have loaded the adapter driver

2. Check all connections at the adapter and the buffered repeater or switch

3. Try another port on the buffered repeater or switch

4. Ensure that the buffered repeater or switch port is configured for 1000 Mbps and full-duplex.

5. Try changing the auto-negotiation setting on the link partner, if possible

RX or TX LED is no On Check the following:

1. Ensure that you have loaded the adapter driver

2. Network might be idle; try logging in from a workstation

3. The adapter is not transmitting or receiving data; try another adapter

Troubleshooting the Intel PRO 1000 XT Server adapter

Use Table 10 to find solutions to the Intel PRO 1000 XT Server adapter problems that have definite symptoms.

See “Testing the Ethernet adapters with Intel PROSet II” on page 65 for information on testing the adapter.

Table 10. Intel PRO 1000 XT Server adapter troubleshooting chart

Adapter problem Suggested Action

The NAS 200 cannot find the adapter

Diagnostics pass but the connection fails

Another adapter stopped working after you installed the adapter

v Make sure the adapter is seated firmly in the slot. v Download the latest drivers from the Intel support web site:

http://www.intel.com/network

v Try a different PCI busmaster slot. See your server’s documentation to identify

busmaster slots.

v Check to see if your motherboard has the latest BIOS. v Make sure your PCI slots are v2.2 compatible. v Try rebooting the computer. v Try a different Intel adapter.

v Check the responding link partner. v Make sure the cable is securely attached, is the proper type and does not exceed

the recommended lengths.

v Try another cable. v Try running the Sender-Responder diagnostic Test. v Make sure the duplex mode and speed setting on the adapter matches the

setting on the switch.

v For NetWare, make sure you specify the correct frame type in the

AUTOEXEC.NCF file.

v Make sure the cable is connections are correct. Make sure your PCI BIOS is

current.

v Check for interrupt conflicts and sharing problems. Make sure the other adapter

supports shared interrupts. Also, make sure your operating system supports shared interrupts.

v Unload all PCI device drivers, then reload all drivers. v Try reseating the most recently installed adapter.

Chapter 7. Troubleshooting 67

Table 10. Intel PRO 1000 XT Server adapter troubleshooting chart (continued)

Adapter problem Suggested Action

Adapter unable to connect to switch at 1000 Mbps, instead connects at 100 Mbps

The adapter stopped working without apparent cause

The Link indicator light is off v Run the adapter and network tests.

The link light is on, but communications are not properly established

Note: This is applicable only to copper-based connections.

v Check the cable type. v Try another cable. v Make sure the link partner is set to Auto-negotiate or manually set to 1000 Full

Duplex.

v Verify that the switch is IEEE 802.3ab-compliant and the latest IOS is installed. v The network driver files may be damaged or deleted. Reinstall the drivers.

v Try reseating the adapter in its slot or different slot, if necessary. v Try rebooting the computer. v Try another cable. v Try a different adapter. v Run diagnostics.

v Make sure you have loaded the adapter driver. v Check all connections at the adapter and the switch. v Try another port on the switch. v Try another cable. v Make sure that the link partner is configured to auto-negotiate (or forced to match

adapter). Verify that the switch is SX-mode fiber or IEEE 802.3ab-compliant.

v Make sure the proper (and latest) driver is loaded. v Both the adapter and its link partner must be set to either auto-negotiate or

manually set to the same speed and duplex settings.

RX or TX light is off (Gigabit only)

The diagnostic utility reports the adapter is “Not enabled by BIOS.”

The computer hangs when the drivers are loaded.

The ACT light is off (non-Gigabit adapters)

Event viewer message: A device attached to the system is not functioning.

The adapter link indicator light may be on even if communications between the adapter and its link partner have not been properly established. Technically, the link indicator light represents the presence of a carrier signal but not necessarily the ability to properly communicate with a link partner. This is expected behavior and is consistent with the IEEE specification for physical layer operation.

v Make sure you’ve loaded the network drivers. v Network may be idle; try creating traffic while monitoring the lights. v Try another adapter.

The PCI BIOS isn’t configuring the adapter correctly.

Try changing the PCI BIOS interrupt settings.

v Make sure you’ve loaded the correct network drivers. v The network may be idle. Try accessing a server. v Try another adapter. v Make sure you’re using two-pair cable for TX wiring.

In Windows NT and NetWare, if there is a BIOS setting for “Plug and Play OS,” make sure it is set to NO. For Windows 2000 and later, this should be set to YES.

68 NAS 200 User’s Reference

Table 10. Intel PRO 1000 XT Server adapter troubleshooting chart (continued)

Adapter problem Suggested Action

For Windows 2000 or XP: Unable to remove PROSet in SAFE mode

If the computer hangs (blue screen) after configuring network adapters with PROSet, try the following:

v Start Windows in Safe mode v Go to the Device Manger, and disable the network adapters and teams. v Restart the computer. v Windows should be operating normally if the problem was caused by the disabled

adapters.

To uninstall PROSet, perform the following steps:

v Start Windows in Safe mode. v Use the Device Manager to disable all teaming instances. v Restart the computer in Normal mode. v Using PROSet, remove all teams and VLANs shown. v Go to the Control Panel, select Add/Remove Programs. v Uninstall PROSet.

Indicator lights

The adapter has the following indicator lights:

Label Indication Meaning

ACT/LNK Green on The adapter is connected to a valid link partner.

Green flashing Data activity Off No link.

v If the LINK light is not on, check all

connections at the adapter and link partner. Make sure the link partner matches the link partner or is set to auto-negotiate, and the driver is loaded. (The link indicator will not be active until the driver is loaded.)

v Make sure the cable is installed properly. The

network cable must be securely attached at all connections. If the cable is attached but the problem persists, try a different cable. – For copper connections, make sure the

cable is a 4-pair Category-5 or better.

– For fiber connections, make sure the cable

is SX mode. Check to see if the Rx and Tx port connectors have been reversed.

Yellow flashing Identity. Use the Identify Adapter button in

PROSet II to control blinking. See PROSet II

Help for more information. 10 = OFF Off 10 MBPS 100 = GRN Green 100 MBPS 1000 = YLW Yellow 1000 MBPS

Troubleshooting the Alacritech Quad-Port 10/100 Ethernet adapter

Table 11 on page 70 displays the LED definitions for the Alacritech Quad-Port 10/100 Ethernet adapter LED definitions

Chapter 7. Troubleshooting 69

Table 11. Alacritech Quad-Port 10/100 Ethernet adapter LED definitions

LED Indication Meaning

LNK Off Either the adapter or the switch (or both)

are not receiving power, or the cable connection between them is faulty.

Green The adapter and switch are receiving

power. The cable connection between them is good. A 100 Mbps link has been established.

Amber The adapter and switch are receiving

power. The cable connection between them is good. A 10 Mbps link has been established.

ACT Off The adapter is not sending or receiving

network data.

Flashing amber The adapter is sending or receiving

network data.

Testing the Quad-Port 10/100 Ethernet adapter

The event log tells you when you should run diagnostics. You can view the event log from the Event Viewer located in the Administrative Tools folder on the Start Menu, located under Programs. When the event log reports that “SLICx has determined that the adapter is not functioning properly,” you can run diagnostics on the Quad-Port 10/100 Ethernet adapter using the following procedure:

1. Run the SLICuser application from the Start Menu, located under the Program Files folder in the Alacritech Folder.

2. Select the Diagnostics tab. Note: Running diagnostics disrupts all ports of the adapter.

3. Click Run. The adapter will then run through a self-test of the IPP and the selected port of the adapter. A properly functioning board will display a window in which all of its tests have Passed.

4. Close the SLICuser utility by clicking OK.

Troubleshooting the ServeRAID-4Lx and 4H

Error codes and messages display on the screen in a line of text immediately after the adapter BIOS version.

If POST detects changes in the controller configuration or detects a controller hardware problem, messages appear on the screen. Refer to “POST (ISPR) error procedures” on page 71 and correct the problem.

If there is no POST Error or Configuration Error message, the BIOS screen messages resemble the sample shown below. Note that your version may be different from the one shown.

70 NAS 200 User’s Reference

__________________________________ IBM ServeRAID BIOS Copyright IBM Corp. 1994, 2001. All rights reserved. BIOS Ver: 4.70.17 __________________________________ Controller 1 Slot 3, Logical drive=3, Other=0, Firmware=4.70.17, Status=OK

<< Press Ctrl+I to access the Mini-Configuration Program >>

Initializing ServeRAID Controller 1 in Slot 1. Power-on self-test can take up to 59 Second(s) -- test Passed. Drive configuration can take up to 6 Minute(s) 0 Second(s) -- test Passed.

If there is a POST Error message, the BIOS screen resembles the sample shown below. Refer to “POST (ISPR) error procedures” and correct the problem. Note that your version may be different from the one shown. The characters XXXX indicate the POST (ISPR) error.

<< Press Ctrl+I to access the Mini-Configuration Program >>

Initializing ServeRAID Controller 1 in Slot 1. Power-on self-test can take up to 59 Second(s) -- test Failed. Controller is not responding properly - Run Diagnostics. Error Code: XXXX-YY

The sample BIOS screen below shows configuration status and error information.

<< Press Ctrl+I to access the Mini-Configuration Program >>

__________________________________ Initializing ServeRAID Controller 1 in Slot 1. Power-on self-test can take up to 59 Second(s) -- test Passed. Drive configuration-can take up to 6 Minute(s) 0 Second(s) -- test Failed. Controller POST and Config Error Codes: ISPR = EF10 BCS = 09 ECS = 20. Following drives not responding (old state: new state: ch SID)

(RDY:EMP: 2:0)

The system has a configuration error due to above condition(s). Press: F4 - Retry the command F5 - Update Controller configuration to exclude NON-RESPONDING drives Warning: NON-RESPONDING drives will be set to DDD, DHS, or EMP state F10 - Exit without change

Note: Do not replace a ServeRAID-4 controller or a system board containing an

imbedded ServeRAID-4 controller for ServeRAID problems unless replacing the controller is listed in Table 12 on page 73.

POST (ISPR) error procedures

The Interrupt Status Port Register (ISPR) Error Procedures list errors, symptoms, and the possible causes. The most probable cause is listed first. Use these

Chapter 7. Troubleshooting 71

procedures to help you solve ServeRAID problems when servicing the computer. A complete list of error codes is in Table 12 on page 73.

EF 10 Default ISPR. No ISPR error present. 9ZXX thru BZXX

SCSI bus error caused either by cables, termination, defective drives, and so on.

1. Isolate the error between SCSI subsystem and controller by disconnecting all SCSI cables from suspect card, and reboot.

CAUTION: Do not press F5. Doing so changes the configuration.

If an ISPR error is still present, take the following actions until the error is no longer present: a. Reseat the controller b. Replace the controller

Note: If the controller detects a configuration change, do not choose

Save Changes. Instead, press F10 to bypass any options to this

effect.

2. If the ISPR error is EF10 after disconnecting cables: a. Confirm that the identified channel(s) is the cause of the error by

verifying that the error presents itself only when the offending

channel is reconnected. b. Check termination of identified channel. c. Check for proper backplane jumper configuration. d. Check for proper cabling configuration in systems that use DASD

status cables. Reconnect all cables that you disconnected at the

beginning of this procedure. e. Replace SCSI cable. f. Replace SCSI backplane.

FFFF (or other code not listed)

1. Isolate between SCSI Subsystem and controller by disconnecting all SCSI cables attached to the suspect card, and reboot.

CAUTION: CAUTION: Do not press F5. Doing so changes the configuration.

If ISPR code is EF10 after disconnecting cables, follow the steps below until the error is eliminated: a. Identify which channel is causing the error by reconnecting cables

one at a time and rebooting until the error returns.

b. Disconnect one drive at a time attached to identified channel and

reboot each time to determine which drive is causing the problem. c. Replace SCSI cable attached to the identified channel. d. Replace backplane attached to the identified channel

2. If the original ISPR code is still present after disconnecting all SCSI cables and rebooting, take the following actions until the error is no longer present: a. Reseat the controller b. Replace the controller

ServeRAID-4x problems and actions

Table 12 on page 73 lists problems and corrective actions associated with the adapter. The table helps you determine which adapters may need to be replaced at the conclusion of troubleshooting procedures.

72 NAS 200 User’s Reference

Note: Do not replace any controllers until you have followed the POST (ISPR) error

procedures (see “POST (ISPR) error procedures” on page 71).). Replace a ServeRAID controller only when indicated to do so in the POST (ISPR) error procedures.

XXX in Table 12 is used as a placeholder and may be any letter or number in an actual error message.

Table 12. ServeRAID-4x problems and actions

Problem Action

1XXX (Microcode Checksum Error) ServeRAID-4 controller 2XXX thru 5XXX (Code DRAM Error) 1. Install download jumpers, flash latest

level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID-4 controller

6XXX (Cache DRAM Error) (ServeRAID-4H only)

7XXX thru 8XXX (Host/Local PCI Bus Interface Error)

9ZXX thru BZXX SCSI Bus error caused by cables, termination, defective drives, and so on). The Z refers to the specific channel or channels that cause the error.

EFFE (Firmware code corrupt or download jumpers are in place)

FFFF or other code not listed 1. Follow indications in the POST (ISPR)

1. Reseat Daughter card

2. Install download jumpers, flash latest level BIOS and firmware for controller. Remove jumpers.

3. ServeRAID-4 controller

1. Install download jumpers, flash latest level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID-4 controller

1. Follow indications in the POST error procedures (see “POST (ISPR) error procedures” on page 71). Follow those instructions before continuing with the next steps listed in this table.

2. SCSI cable

3. SCSI backplane

4. Hard drive

5. ServeRAID-4 controller

1. Flash latest level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID-4 controller

error procedures (“POST (ISPR) error procedures” on page 71).

2. SCSI cable

3. SCSI backplane

4. Hard drive

5. ServeRAID-4 controller

Testing the ServeRAID 4x adapter

You can run all diagnostic operations for the ServeRAID adapters through the IBM ServeRAID Configuration software in the Advanced Functions option. You can run subsystem diagnostics through the system diagnostics.

Note: Before running any test, back up the current disk array configuration using

the ServeRAID diagnostics test program. Always keep a current backup of the ServeRAID configuration information. Dynamic changes may occur in the configuration due to hot-spare replacement.

Chapter 7. Troubleshooting 73

The IBM PC ServeRAID Adapter diagnostics test program runs independently of the operating system and is run from diskette. You can obtain a copy from the ServerGuide Diskette Factory or download it from IBM’s web site.

To back up the ServeRAID configuration:

1. From the Main Menu, select Advanced Functions

2. Select Backup IPS ServeRaid Config You can use the ServeRAID Subsystem Diagnostic program to test the PC

ServeRAID Adapter and the devices connected to it. To test the ServeRAID subsystem:

1. Start the ServeRAID Configuration Utility program

2. Select Advanced Functions from the Main Menu and press Enter

3. Select IBM ServeRAID Subsystem Diagnostic from the next menu and press

Enter

4. Select the diagnostic test that you want to run and press Enter . Descriptions of the diagnostic tests available include:

Run Adapter Self-tests

Tests the PC ServeRAID Adapter. Restart the server after the self-test completes.

SCSI Device Self-test

Runs diagnostic tests on the SCSI devices attached to the PC ServeRAID Adapter.

Troubleshooting the Integrated System Management Processor

1. Insert the ISMP Utility CD-ROM into the CD-ROM drive and restart the NAS 200 engine. If the engine does not boot from the CD-ROM, use POST/BIOS setup to configure the CD-ROM drive as a boot device.

2. After the engine boots, the main option menu appears. The main menu contains the following selections:

v Hardware Status and Information v Configuration Settings v Update System Management firmware

3. Use the up and down arrow keys to select Hardware Status and Information and press Enter. The Hardware Status and Information menu contains the list of ISMP devices with the following diagnostic test results:

Processor Communication : Passed

-> Built in Self Test Status ...... : Passed

Boot Sector Code Revision ... :6, Build ID: RIET62A Main Application Code Revision :4, Build ID: ILET15A

Processor Communication : Passed

-> Built in Self Test Status ...... : Passed

Boot Sector Code Revision ... :6, Build ID: WMICT60A Main Application Code Revision :4, Build ID: WMXT57A

4. Use the up and down arrow keys to select the device you want to look at in more detail. Press Enter. You will see a list of tests and results on the device:

Current System Management Processor Status

74 NAS 200 User’s Reference

Current BIST Results:

SRAM Memory Test: Passed Serial Port 1 Test : Passed Serial Port 2 Test: Passed NVRAM Memory Test Passed Realtime Clock Test Passed Programmable Gate Array Test: Passed

I2C Interface Test: Passed Main Application Checksum: Passed Boot Sector Checksum: Passed

Current System Management Adapter Status

Current BIST Results:

SRAM Memory Test: Passed Serial Port 1 Test : Passed Serial Port 2 Test: Passed NVRAM Memory Test Passed Realtime Clock Test Passed Programmable Gate Array Test: Passed I2C Interface Test: Passed Main Application Checksum: Passed Boot Sector Checksum: Passed Onboard Ethernet Hardware Test: Passed PCI EEPROM Initialization Test: Passed

5. When you are finished viewing this information, press Esc to return to the main option menu. Remove the CD then restart the NAS 200 engine.

Troubleshooting the Remote Supervisor Adapter

1. Insert the Remote Supervisor Adapter Support CD into the CD-ROM drive and restart the engine. If the engine does not boot from the CD-ROM, use POST/BIOS setup to configure the CD-ROM drive as a boot device.

2. After the engine boots, the main option menu appears. The main menu contains the following selections:

v Hardware Status and Information v Configuration Settings v Update System Management firmware

3. Use the up and down arrow keys to select Hardware Status and Information and press Enter. The Hardware Status and Information menu contains the list of devices with the following diagnostic test results:

System Management Processor Communication : Passed

-> Built in Self Test Status ...... : Passed

Boot Sector Code Revision ... :16, Build ID: CNET15A Main Application Code Revision :16, Build ID: TUET15A

4. Use the up and down arrow keys to select the device you want to look at in more detail. Press Enter. You will see a list of tests and results on the device:

Current System Management Processor Status

Current BIST Results:

Current System Management Adapter Status

Current BIST Results:

SRAM Memory Test: Passed Serial Port 1 Test : Passed Serial Port 2 Test: Passed NVRAM Memory Test Passed Realtime Clock Test Passed

Chapter 7. Troubleshooting 75

5. When you are finished viewing this information, press Esc to return to the main option menu. Remove the CD then restart the engine.

Testing SCSI Adapters

The SCSI adapters are used for tape backup operations. They may be configured during engine boot time by entering Ctrl-A when prompted. This invokes the BIOS SCSI Select utility. Follow the on-screen directions when this utility appears. The adapters are tested during the boot process.

Programmable Gate Array Test: Passed I2C Interface Test: Passed Main Application Checksum: Passed Boot Sector Checksum: Passed Onboard Ethernet Hardware Test: Passed PCI EEPROM Initialization Test: Passed

76 NAS 200 User’s Reference

Chapter 8. Using the Recovery and Supplementary CDs

This chapter describes the applications included on the Supplementary and Recovery CDs, and how and when you should use them.

Attention: Changing the preloaded software configuration of this product, including applying or installing unauthorized service packs or updates to preinstalled software, or installing additional software products that are not included in the preloaded image, on the Supplementary CD, or on the IBM website, may not be supported and could cause unpredictable results. For updated compatibility information, please see

http://www.ibm.com/storage/support/nas

To correct problems with a preloaded software component, back up your user and system data. Then use the Recovery CD Set to restore the preloaded software image.

As an alternative to using the Recovery CD Set, you can use the restore portion of the disaster recovery solution provided by Persistent Storage Manager (PSM) to recover the appliance, if you have met the requirements (including creating a PSM backup image and PSM recovery diskette). The restore function allows you to restore the appliance to the state it was in at the time of the PSM backup, in one step, without having to revert back to the original (factory) configuration which would require you to subsequently reconfigure networking and other components. See “Restoring the system drive” on page 41 to determine whether you have met the requirements. If so, you can use the PSM recovery method. If you have not met the requirements for using the PSM recovery method, or if the PSM recovery fails, then you must use the Recovery CD Set as described in this chapter.

Using the Recovery Enablement Diskette and Recovery CD Set

The Recovery CD Set (three CDs, labeled as Recovery CD 1, Recovery CD 2, and Recovery CD 3) contains the preload image for your NAS 200 and is used to recover the preloaded image on your appliance. You must start the appliance using the Recovery Enablement Diskette before you can boot Recovery CD 1.

Attention: The NAS 200 does not have a monitor, keyboard, or mouse attached to it under normal operating conditions. Because of this, you cannot interact with the preload-image restore process using a monitor. Starting Recovery CD 1 will, without visually prompting the user, automatically destroy all data on the system drive. Use the Recovery Enablement Diskette and Recovery CD Set only when it is absolutely necessary to restore the preloaded system image.

To recover the preloaded image on an appliance, do the following steps. Note that the recovery process invalidates persistent images and leaves them in a state that is inconsistent with their pre-recovery state. So, if you plan to use the Recovery CD Set, it is recommended that you first delete all persistent images to ensure a clean reload of the system software.

1. Attach a keyboard and display to the appliance.

2. Insert the Recovery Enablement Diskette into the diskette drive of the appliance and restart the appliance. When the Recovery Enablement Diskette has completed loading and modifying your node startup sequence, the node will begin a continuous beep. Do not continue with this procedure until the node begins the beep.

Important

The Recovery Enablement Diskette enables the NAS 200 to start from the CD-ROM drive. You will not be able to restore the preload image from the Recovery CD Set without first restarting the appliance using the Recovery Enablement Diskette.

3. Remove the Recovery Enablement Diskette from the diskette drive of the appliance.

4. Place Recovery CD 1 in the CD-ROM drive of the appliance and restart the appliance.

5. If you have installed more processor memory on the failed node, the BIOS configuration program will now appear. Click Continue on the first screen, then click Continue again, then click Exit Setup, and finally, click Yes, save and exit Setup.

6. The recovery process will begin automatically. Follow the instructions provided by the image restoration software, and the original manufacturing preload will be restored. During the restoration of the preload, you will be prompted to insert the other recovery CDs into the CD-ROM drive. Once the preload image is restored, the node restarts automatically.

7. If you have installed more processor memory, the BIOS configuration program will now appear a second time. Click Continue on the first screen, then click Continue again, then click Exit Setup, and finally, click Yes, save and exit Setup. You may now detach the keyboard and display from the appliance and allow the recovery process to complete automatically.

Important

v After the appliance restarts, a series of configuration and system

preparation programs that finish configuring the appliance run automatically. These programs must finish running before you use any included applications (such as the IBM Advanced Appliance Configuration Utility or the Terminal Services Client) to connect to or configure your NAS 200. Do not connect to or configure the appliance for at least 15 minutes after system restart. This notice applies only to the first time the NAS 200 is started after using the Recovery CD Set.

v Logical Disk 0 will be configured to have a 6-GB NTFS boot partition.

Any other previously configured logical disk drives, as well as the remainder of Logical Disk 0 (which, on the original hard disk drive of the appliance, contains the Maintenance partition, but for a replacement hard disk drive would not contain any other partitions), will be left unchanged.

8. Reinstall all software updates you had installed on the appliance since you installed the NAS 200 out of the box. Or, if the Recovery CD Set you used in this procedure is a newer version than the one you received with the NAS 200, reinstall only those software updates that are newer than those on the Recovery CD Set.

78 NAS 200 User’s Reference

Using the Supplementary CD

The Supplementary CD contains documentation and copies of key software applications that are preinstalled on your NAS 200. Table 13 includes the names of the directories found on the Supplementary CD and a description of the contents of the directory.

Table 13. Supplementary CD directories

Directory Name Contents

IBM Advanced Appliance Configuration

DiskImages Diskette images for the Recovery Enablement Diskette and the IBM NAS AutoRAID

IBM Advanced Appliance Configuration console and agent installation files. The IBM Advanced Appliance Configuration agent is preinstalled as a Windows Powered service on the NAS 200. To install the Advanced Appliance Configuration console (on another network-attached workstation running Windows 98, Windows NT, or Windows 2000), run lpv2setup.exe from the x:\IBM Advanced Appliance Configuration directory, where x is the drive letter assigned to your workstation’s CD-ROM drive. Note: When the installation completes, it will leave behind a temporary directory named iaacu on the workstation, under the directory specified by the TEMP environment variable (usually c:\temp; you can determine the value of the TEMP variable by typing set temp from a DOS command prompt). You should remove this directory (using Windows Explorer) after the installation has completed.

diskette. To create the Recovery Enablement Diskette, run RecovDsk.bat and insert an HD 1.44

floppy diskette into drive A: when prompted. To create the IBM NAS AutoRAID diskette, run IBM_NAS_AutoRAID.exe and insert an

HD 1.44 floppy diskette into drive A: when prompted. Note that the NAS 200 supports three, four, five, or six internal hard disk drives. Please

read the file readme.txt in the root directory and readme.txt in this directory for more information about the diskette images and how to create diskettes from the images.

Attention: Starting the NAS 200 with the IBM NAS AutoRAID diskette will remove all RAID configuration changes from your ServeRAID adapter, including any changes you applied to the configuration for any additional storage (internal hard disk drives and/or external storage units) you added to the NAS 200 since you received it, and restore the RAID configuration to its factory default configuration.All data stored in your ServeRAID arrays will be lost. Use this diskette only if you want to reset the NAS 200 to factory default settings. After using the diskette, you must use the Recovery CD (described earlier in this chapter) to restore the preloaded software image on the system drive.

I386 Windows Powered installation files. If you add device drivers, OS features, and so on,

you may be prompted to insert your Windows Powered CD-ROM. If so, insert the Supplementary CD, and specify path x:\i386, where x is the drive letter assigned to your CD-ROM drive.

W2KSP2 Windows Powered Service Pack 2, which is preloaded on your NAS 200. If you add

any device drivers, OS features, and so on, you should reapply Service Pack 2. Run the executable w2ksp2.exe, and follow the instructions provided.

Chapter 8. Using the Recovery and Supplementary CDs 79

Table 13. Supplementary CD directories (continued)

Directory Name Contents

Services for UNIX SFU 2.2 installation files, zipped into a self-extracting executable, sfu22.exe. If you add

features that are not preloaded, you will be prompted for these installation files. You will need to extract the installation files onto the hard disk drive of your NAS 200. It is recommended that you use the maintenance drive (D: drive) as the destination, but you can use the system drive (C: drive). On whatever drive you choose, make sure that you have at least 250 MB of free space available, create a temporary directory on the drive, and then issue the following command from the Services for UNIX directory on the Supplementary CD: sfu22 path, where path is the drive letter and path of the temporary directory you created. Then when you are prompted by the Services for UNIX installation to provide the path of the installation files, specify the same path you specified in extracting the files from the CD.

Terminal Services Client The standalone Win32 Terminal Services Client application. The NAS 200 appliance

supports Web-based terminal services, so this is an optional installation. To install the Terminal Services Client, run setup.exe from the Disk1 subdirectory.

readme.txt This is a text file that describes the contents of the Supplementary CD.

80 NAS 200 User’s Reference

Appendix A. Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering the subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or program(s) described in this publication at any time without notice.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Trademarks

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

The following terms are trademarks of International Business Machines Corporation in the United States or other countries or both:

IBM Netfinity Netfinity Advanced System Management Netfinity Manager ServeRAID ServerGuide TotalStorage

Lotus and Domino are trademarks of Lotus Development Corporation in the United States, other countries, or both.

Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United States, other countries, or both.

Intel, MMX, LANDesk, Pentium, Pentium II Xeon, and Pentium III Xeon are trademarks or registered trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries and is licensed exclusively through The Open Group.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

82 NAS 200 User’s Reference

Appendix B. Getting help, service, and information

If you need help, service, technical assistance, or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you.

IBM maintains pages on the World Wide Web where you can get information about IBM products and services and find the latest technical information.

Table 14 lists some of these pages.

Table 14. IBM Web sites for help, services, and information

www.ibm.com Main IBM home page www.ibm.com/storage IBM Storage home page www.ibm.com/storage/support/nas IBM NAS Support home page

You might also want to visit the Web pages of other companies for information about other operating systems, software, and accessories. The following are some other Web sites you might find helpful:

www.tivoli.com www.cdpi.com

Service support

Services available and telephone numbers listed are subject to change without notice.

With the original purchase of an IBM hardware product, you have access to extensive support coverage. During the IBM hardware product warranty period, you may call the IBM Support Center (1-800-426-7378 in the U.S.) for hardware product assistance covered under the terms of the IBM hardware warranty. See “Getting help by telephone” on page 85 for Support Center telephone numbers in other countries.

The following services are available during the warranty period: v Problem determination - Trained personnel are available to assist you with

determining if you have a hardware problem and deciding what action is necessary to fix the problem.

v IBM hardware repair - If the problem is determined to be caused by IBM

hardware under warranty, trained service personnel are available to provide the applicable level of service.

v Engineering change management - Occasionally, there might be changes that

are required after a product has been sold. IBM or your reseller, if authorized by IBM, will make Engineering Changes (ECs) available that apply to your

hardware. Be sure to retain your proof of purchase to obtain warranty service. Please have the following information ready when you call:

v Machine Type and Model v Serial numbers of your IBM hardware products

v Description of the problem v Exact wording of any error messages v Hardware and software configuration information

If possible, be at your computer when you call. A compatible monitor, keyboard, and mouse may be required for some service

activities. The following items are not covered:

v Replacement or use of non-IBM parts or nonwarranted IBM parts

Note: All warranted parts contain a 7-character identification in the format IBM

FRU XXXXXXX.

v Identification of software problem sources v Configuration of BIOS as part of an installation or upgrade v Changes, modifications, or upgrades to device drivers v Installation and maintenance of network operating systems (NOS) v Installation and maintenance of application programs

Refer to your IBM hardware warranty for a full explanation of IBM’s warranty terms.

Before you call for service

Many computer problems can be solved without outside assistance, by using the online help or by looking in the online or printed documentation that comes with your Model 200. Also, be sure to read the information in any README files that come with your software.

Your Model 200 comes with documentation that contains troubleshooting procedures and explanations of error messages. The documentation that comes with your appliance also contains information about the diagnostic tests you can perform.

If you receive a POST error code or beep code when you turn on your Network Attached Server appliance, refer to the POST error-message charts in your hardware documentation. If you do not receive a POST error code or beep code, but suspect a hardware problem, refer to the troubleshooting information in your hardware documentation or run the diagnostic tests.

If you suspect a software problem, consult the documentation (including any README files) for the operating system or application program.

Getting customer support and service

Purchasing an IBM Network Attached Storage appliance entitles you to standard help and support during the warranty period. If you need additional support and services, a wide variety of extended services are available for purchase that address almost any need.

Getting help online: www.ibm.com/storage/support/nas

Here you can visit a support page that is specific to your hardware, complete with FAQs, parts information, technical hints and tips, technical publications, and downloadable files, if applicable.

84 NAS 200 User’s Reference

Getting help by telephone

During the warranty period, you can get help and information by telephone through the IBM Support Center. Expert technical-support representatives are available to assist you with questions you might have on the following:

v Setting up your Network Attached Storage appliance v Arranging for service v Arranging for overnight shipment of customer-replaceable parts

In addition, if you purchased a Network Attached Storage appliance, you are eligible for IBM up-and-running support for 90 days after installation. This service provides assistance for:

v Setting up your appliance v Limited configuration assistance

Please have the following information ready when you call:

v Machine Type and Model v Serial numbers of your appliance and other components, or your proof of

purchase

v Description of the problem v Exact wording of any error messages v Hardware and software configuration information for your system

If possible, be at your computer when you call. In the U.S. and Canada, these services are available 24 hours a day, 7 days a

week. In the U.K., these services are available Monday through Friday, from 9:00 a.m. to 6:00 p.m.

1. Response time will vary depending on the number and complexity of incoming calls.

Appendix B. Getting help, service, and information

86 NAS 200 User’s Reference

Appendix C. Engine POST messages

This appendix identifies and describes POST messages that you might encounter, and gives corrective actions where applicable.

Note: The information in this appendix applies to each engine in the appliance. For

example, when the text reads, “When a monitor and keyboard is attached to the appliance,” that means that a monitor and keyboard has been attached to either of the two engines.

Power-on self-test (POST)

When you turn on your NAS 200, its engine performs a power-on self-test (POST) to check the operation of appliance components and some of the options installed in the appliance.

If POST finishes without detecting any problems when a monitor and keyboard are not attached to the appliance, you will hear one long and three short beeps. When a monitor and keyboard are attached, you will hear one short beep. Any other series of beeps indicates a problem, and an error message appears on your screen. See “POST beep code descriptions” for more information.

Notes:

1. If you have a power-on password or administrator password set, you must type

the password and press Enter, when prompted, before POST will continue.

2. A single problem might cause several error messages. When this occurs, work

to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time you run the test.

POST beep code descriptions

Beep codes are sounded in a series of beeps. For example, a 1-2-4 beep code sounds like one beep, a pause, two consecutive beeps, another pause, and four more consecutive beeps.

The possible types of beep codes that your appliance might emit include the following:

No beeps

If no beep occurs after your appliance completes POST (that is, after the system POST complete (OK) light on the operator information panel is illuminated), call for service.

Continuous beep

The recovery enablement disk has booted, your startup (boot) microprocessor has failed, or your system board or speaker subsystem might contain a failing component. If the system continues through POST with no errors, call for service. If no video appears, the startup processor has failed; replace the startup processor.

One short beep

When a monitor and keyboard is attached to the appliance, one beep indicates that your appliance successfully completed POST. POST detected no configuration or functional errors. One beep also occurs after your appliance completes POST if you enter an incorrect power-on password.

Two short beeps

POST encountered an error. The Configuration/Setup Utility program will display additional information; follow the instructions that appear on the screen. See “POST error messages” on page 92 for descriptions of the text messages that might appear.

Three short beeps

A system memory error has occurred. This combination occurs only if the video Basic Input/Output System (BIOS) cannot display the error message. Replace the failing memory module.

Repeating short beeps

The system board might contain a failing component, your keyboard might be defective, or a key on the keyboard might be stuck. Ensure that:

1. Nothing is resting on the keyboard and pressing a key.

2. No key is stuck.

3. The keyboard cable is connected correctly to the keyboard and to the correct connector on the appliance.

Running the diagnostic tests can isolate the appliance component that failed, but you must have your system serviced. If the error message remains, call for service.

Note: If you just connected a new mouse or other pointing device, turn off

the appliance and disconnect that device. Wait at least 5 seconds; then, turn on the appliance. If the error message goes away, replace the device.

One long and one short beep

POST encountered an error on a video adapter. If you are using the integrated video controller, call for service. If you are using an optional video adapter, replace the failing video adapter.

One long and two short beeps

A video I/O adapter ROM is not readable, or the video subsystem is defective. If you hear this beep combination twice, both the system board and an optional video adapter have failed the test. This beep combination might also indicate that the system board contains a failing component.

One long and three short beeps

This series of beeps has two meanings. The first means that the POST has completed without detecting errors, when a monitor and keyboard is not attached. However, when a monitor is attached, and you hear this series, it means the system-board video subsystem has not detected a monitor connection to the appliance. Ensure that the monitor is connected properly to the appliance. If the problem persists, replace the monitor.

Two long and two short beeps

POST does not support the optional video adapter. This beep combination occurs when you install a video adapter that is incompatible with your appliance. Replace the optional video adapter with one that the appliance supports or use the integrated video controller.

Table 15 on page 89 describes the codes and specifies the action to take.

88 NAS 200 User’s Reference

IBM TotalStorage 201, TotalStorage 226 User Reference Manual

Specifications and Main Features

Frequently Asked Questions

User Manual