Celerra Basic Administrator Guide

Celerra File ServerVersion 4.1

BASIC ADMINISTRATION GUIDEP/N 300-000-309

REV A02

EMC Corporation171 South StreetHopkinton, MA 01748-9103Corporate Headquarters: (508) 435-1000, (800) 424-EMC2Fax: (508) 435-5374 Service: (800) SVC-4EMC

ii

Copyright © 2002 EMC Corporation. All rights reserved.Printed February, 2002

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

Regulatory Agency Information

Celerra File Server system has been extensively tested and certified to meet UL1950, CSA 22.2 No 950, IEC 60950/EN60950; Safety of Information Technology Equipment including Electrical Business Equipment, FCC Rules Part 15 Subpart B; CISPR22 Class A; European EMC Directive 89/336/EEC on, electromagnetic compatibility.

This class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

Warning! This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

Achtung!Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.

Attention!Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer des interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre les mesures spécifiques appropriées.

This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference.

Celerra File Server Basic Administration Guide

Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.

Any modifications to this device - unless expressly approved by the manufacturer - can void the user’s authority to operate this equipment under part 15 of the FCC rules.

Software CopyrightsThis product incorporates ISE Eiffel 3 Object-Oriented technology from Interactive Software Engineering in Santa Barbara, California.

The EMC® version of Linux®, used as the operating system on the Celerra Control Station, is a derivative of Red Hat® Linux. The operating system is copyrighted and licensed pursuant to the GNU General Public License (GPL), a copy of which can be found in the accompanying documentation. Please read the GPL carefully, because by using the Linux operating system on the EMC Celerra File Server, you agree to the terms and conditions listed therein.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Trademark InformationEMC2, EMC, MOSAIC:2000, Symmetrix, CLARiiON, and Navisphere are registered trademarks and EMC Enterprise Storage, The Enterprise Storage Company, The EMC Effect, Connectrix, EDM, SDMS, SRDF, TimeFinder, PowerPath, InfoMover, FarPoint, EMC Enterprise Storage Network, EMC Enterprise Storage Specialist, EMC Storage Logic, Universal Data Tone, E-Infostructure, and Celerra are trademarks of EMC Corporation.

EMC, ICDA (Integrated Cached Disk Array), EMC2 (the EMC logo), and Symmetrix are registered trademarks, and EMC Enterprise Storage and Celerra are trademarks of EMC Corporation.Adaptec is a trademark of Adaptec, Inc.BT Tymnet is a registered trademark of British Telecommunication plc.BudTool is a registered trademark of Legato CorporationIntel and Pentium are registered trademarks of Intel Corporation.Internet Explorer is a trademark of Microsoft Corporation.This product incorporates ISE Eiffel 3 Object-Oriented technology from Interactive Software Engineering in Santa Barbara, California.Linux is a registered trademark of Linus Torvalds.Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.Netscape is a trademark of Netscape Communications Corporation.Network File System and NFS are trademarks of Sun Microsystems, Inc.Red Hat is a registered trademark of Red Hat Software, Inc.Russellstoll is a registered trademark of Midland-Ross Corporation.3Com is a registered trademark of 3Com Corporation.UNIX is a registered trademark in the United States and other countries and is licensed exclusively through X/Open Company Ltd.VERITAS, VxFS, and NetBackup are registered trademarks of VERITAS Software Corporation.All other trademarks used herein are the property of their respective owners.

Celerra File Server Basic Administration Guide iii

iv

Contents

Preface............................................................................................................................ xv

Chapter 1 Introducing the Celerra File ServerOverview of the Celerra File Server.............................................. 1-2

Advantages................................................................................ 1-2Limitations................................................................................. 1-3

Celerra File Server Features............................................................ 1-4Celerra File Server Cabinet............................................................. 1-8

Single Enclosure........................................................................ 1-8Multi-Cabinet Enclosure........................................................ 1-10Celerra File Server Cabinet Features.................................... 1-10Celerra File Server Functionality.......................................... 1-11

Hardware Components................................................................. 1-13Control Station ........................................................................ 1-13Data Movers ............................................................................ 1-15IP Addresses ............................................................................ 1-17Power Supplies ....................................................................... 1-17CD-ROM Drive ....................................................................... 1-18Modem Connections .............................................................. 1-18Communications (COMM) Board........................................ 1-18Console Multiplexer ............................................................... 1-18

About Celerra Connections .......................................................... 1-19Small Computer Systems Interface ...................................... 1-19Fibre Channel .......................................................................... 1-19

Software Components ................................................................... 1-24Control Station Software........................................................ 1-24Data Mover Software ............................................................. 1-24

Celerra File Server Basic Administration Guide v

Contents

Celerra File Server Environment ................................................. 1-25Network File Sharing Protocols ........................................... 1-25Other Network Protocols ...................................................... 1-26

Celerra Graphical User Interfaces ............................................... 1-27Celerra File Server Manager ................................................. 1-27Celerra Monitor ...................................................................... 1-28

Configuring Celerra ...................................................................... 1-30System Tasks ........................................................................... 1-30Required System Configuration........................................... 1-30Enhanced System Configuration.......................................... 1-33

User Access Configuration Options............................................ 1-34Supported Platforms .............................................................. 1-34

Where to Go From Here................................................................ 1-34

Chapter 2 Planning for a Celerra File ServerInstallation Prerequisites ................................................................ 2-2Determining Storage Needs ........................................................... 2-3

Symmetrix System Options..................................................... 2-3Determining the Number of Data Movers................................... 2-4

Determining Performance Requirements ............................. 2-4Determining Data Availability ............................................... 2-4

Organizing Data and Data Movers ............................................... 2-5Mapping Volumes to File Systems......................................... 2-5Typical Configuration .............................................................. 2-6

Chapter 3 Power SequencesPowering Up the Celerra Cabinet ................................................. 3-2Planned Power Down ..................................................................... 3-4Emergency Shutdown..................................................................... 3-6

Powering Up After an Emergency Shutdown ..................... 3-6The Command Line Interface ........................................................ 3-8

Command-Line Parameters .................................................... 3-8Logging In......................................................................................... 3-9

Chapter 4 Configuring Celerra Network ServicesCreating an IP Interface .................................................................. 4-2

Viewing Network Interfaces ................................................... 4-5Configuring DNS and NIS ............................................................. 4-7Configuring Time Services ............................................................. 4-9Where to Go From Here................................................................ 4-10

Celerra File Server Basic Administration Guidevi

Contents

Chapter 5 Creating Volumes, File Systems, and Mount PointsCreating Volume Configurations .................................................. 5-2

Volume Types ........................................................................... 5-2Configuring a Disk Volume.................................................... 5-2

Slice Volumes ................................................................................... 5-3Configuring a Slice Volume.................................................... 5-3Creating a Slice Volume .......................................................... 5-3

Stripe Volumes................................................................................. 5-5Improving Performance With Stripe Volumes..................... 5-5Configuration Guidelines for Stripe Volumes ..................... 5-6Creating a Stripe Volume ........................................................ 5-7

Meta Volumes .................................................................................. 5-9Configuring a Meta Volume ................................................... 5-9Addressing Within a Meta Volume ..................................... 5-10Expanding Storage Capacity ................................................ 5-11Creating a Meta Volume........................................................ 5-11Verifying Volume Configurations........................................ 5-12

Business Continuance Volumes .................................................. 5-13Creating a File System .................................................................. 5-14

Mandatory File System Requirements................................ 5-14Creating a Mount Point ................................................................ 5-15

Chapter 6 Mounting and Exporting File Systems for the NFS UserUser Types ........................................................................................ 6-2Understanding NFS ........................................................................ 6-3

NFS Environment..................................................................... 6-3NFS User Authentication........................................................ 6-3

Typical NFS Configuration ............................................................ 6-4NFS Configuration Overview ................................................ 6-4Sample NFS User Configuration ........................................... 6-4

Mounting a File System.................................................................. 6-6NFS File Locking ...................................................................... 6-6NFS Mount Options................................................................. 6-6

Exporting a Path.............................................................................. 6-8Export All ................................................................................ 6-10

Providing PC User Access ........................................................... 6-11Authenticating PC Clients for NFS Access ........................ 6-11

Unexporting Paths/Shares .......................................................... 6-14Unexport Limitations ........................................................... 6-14Unexport Advisory................................................................ 6-14

Where to Go From Here ............................................................... 6-15

viiCelerra File Server Basic Administration Guide

Contents

Chapter 7 Configuring StandbysData Mover Availability ................................................................. 7-2Failover Detection............................................................................ 7-4

How Data Mover Failover Works .......................................... 7-4Failover Example ...................................................................... 7-5

Configuring Standby Data Movers ............................................... 7-8When and How to Link ........................................................... 7-8Failover Policies ........................................................................ 7-8Standby Data Mover Rules and Restrictions........................ 7-8Create Standby.......................................................................... 7-9

Activating a Standby..................................................................... 7-10Restoring a Primary Data Mover ......................................... 7-12Verifying Standby Data Movers After an Upgrade........... 7-13CIFS Access After Failover.................................................... 7-14Periodic Tasks.......................................................................... 7-14For More Information ............................................................ 7-14

Control Station Failover................................................................ 7-15Control Station Independence .............................................. 7-15Dual Control Station Configuration .................................... 7-15

Initiating a Control Station Failover ........................................... 7-16Where to Go From Here................................................................ 7-17

Chapter 8 Managing File SystemsCreating an Automount Map......................................................... 8-2Displaying Mounted File Systems ................................................ 8-4Unmounting a File System ............................................................. 8-5

Unmount All ............................................................................. 8-5Checking Capacity........................................................................... 8-6

Checking File System Capacity .............................................. 8-6Checking Data Mover Free Space .......................................... 8-6

Extending a File System.................................................................. 8-7Renaming a File System.................................................................. 8-9Deleting a File System................................................................... 8-10Creating 32-bit GIDs...................................................................... 8-11

Restrictions for the 32-bit GID .............................................. 8-12Setting the 32-bit System Parameter .................................... 8-13

Celerra File Server Basic Administration Guideviii

Contents

Chapter 9 Managing Your SystemManaging Data Movers.................................................................. 9-2

Adding Internal Events........................................................... 9-2Discovering and Saving SCSI Devices .................................. 9-3Rebooting Data Movers .......................................................... 9-4Halting a Data Mover.............................................................. 9-4

Managing Volumes ......................................................................... 9-5Checking Volume Capacity .................................................... 9-5Extending Meta Volumes........................................................ 9-5Renaming Volumes .................................................................. 9-6Cloning Volumes...................................................................... 9-7Deleting Volumes ..................................................................... 9-7

Controlling Access to System Objects .......................................... 9-9Task 1: Create a Linux User .................................................... 9-9Task 2: Creating an Access Control Level Table ................ 9-10Task 3: Establishing Access Control Lists for Objects....... 9-11How ACLs Work.................................................................... 9-13

Managing System Parameters ..................................................... 9-15System Parameters................................................................. 9-15Parameter File Format ........................................................... 9-15Example ................................................................................... 9-18Server Parameters .................................................................. 9-18

Chapter 10 Control Station UtilitiesDatabase Backup ........................................................................... 10-2Enabling Daemons ........................................................................ 10-3

Configuring NTP ................................................................... 10-3Viewing the nas Daemons .................................................... 10-4Viewing the httpd Daemons................................................. 10-4

Rebooting the Control Station(s)................................................. 10-5Locally ..................................................................................... 10-5Remotely.................................................................................. 10-6

Halting the Control Station(s) ..................................................... 10-7Locally ..................................................................................... 10-7Remotely.................................................................................. 10-8

ixCelerra File Server Basic Administration Guide

Contents

Chapter 11 TroubleshootingTroubleshooting ............................................................................. 11-2

Post-Install Error Messages................................................... 11-2Volume Troubleshooting ....................................................... 11-4File System Troubleshooting................................................. 11-5Data Mover Troubleshooting................................................ 11-7

Checking Log Files ...................................................................... 11-11Monitoring System Activity....................................................... 11-12

Appendix A Technical SpecificationsPhysical Data .................................................................................. A-2Environmental Data ...................................................................... A-2Power Requirements ..................................................................... A-3Hardware/Software Specifications ............................................. A-4

Appendix B Customer SupportOverview of Detecting and Resolving Problems ...................... B-2Troubleshooting the Problem ....................................................... B-3Before Calling the Customer Support Center ............................ B-3Documenting the Problem ........................................................... B-4Reporting a New Problem ............................................................ B-4Sending Problem Documentation ............................................... B-5

Appendix C GNU General Public LicenseGNU General Public License ....................................................... C-2

Preamble ................................................................................... C-2Terms and Conditions for Copying, Distribution, andModification ............................................................................. C-3NO WARRANTY .................................................................... C-8

Glossary ........................................................................................................................ g-1

Index................................................................................................................................ i-1

Celerra File Server Basic Administration Guidex

Tables

1-1 Celerra File Server Software Features and Benefits ................................ 1-51-2 Control Station Slots ................................................................................... 1-151-3 Data Mover Slots ........................................................................................ 1-171-4 Fibre Channel Port Types .......................................................................... 1-201-5 Fibre Channel Adapter Specifications ..................................................... 1-201-6 Requirements for Celerra File Server Manager ...................................... 1-281-7 Minimum Configuration for the Celerra Monitor ................................. 1-291-8 Celerra File Server Configuration Process .............................................. 1-312-1 Storage Schemes and Storage Usage ......................................................... 2-34-1 NICs Used in Celerra ................................................................................... 4-24-2 server_sysconfig Sample Breakout ............................................................ 4-34-3 Sample Parameters for an IP Interface ..................................................... 4-45-1 Volume Types ............................................................................................... 5-26-1 NFS Export Options ..................................................................................... 6-87-1 Data Mover Failover .................................................................................... 7-47-2 Failover Standby Policy Types ................................................................... 7-88-1 Parameters for Managing GIDs ................................................................ 8-119-1 Creating ACLs ............................................................................................. 9-119-2 System Parameters ..................................................................................... 9-169-3 Server Parameters ....................................................................................... 9-1911-1 Error Message Troubleshooting ............................................................... 11-311-2 Volume Error Messages ............................................................................. 11-411-3 File System Error Messages ...................................................................... 11-511-4 File System Scenarios ................................................................................. 11-611-5 Data Mover Error Messages ...................................................................... 11-711-6 Data Mover Scenarios ................................................................................ 11-911-7 System Log Error Messages and General Scenarios ............................ 11-1011-8 Log Files ..................................................................................................... 11-1111-9 Monitoring System Performance ........................................................... 11-12

Celerra File Server Basic Administration Guide xi

Tables

Celerra File Server Basic Administration Guidexii

Figures

1-1 Celerra File Server Environment ................................................................ 1-31-2 Single Enclosure Model ............................................................................... 1-91-3 Celerra Multi-Cabinet Enclosure .............................................................. 1-101-4 Hardware Operations ................................................................................ 1-121-5 Typical Front Panel View of a Control Station ....................................... 1-141-6 507 Data Mover Front View ...................................................................... 1-161-7 Fan-Out Topology ...................................................................................... 1-211-8 Fan-In Topology ......................................................................................... 1-221-9 NFS and CIFS Software ............................................................................. 1-261-10 Celerra File Server Configuration Process .............................................. 1-322-1 Data Mover Volumes ................................................................................... 2-52-2 Data Mover Organization ........................................................................... 2-63-1 EPO Power Switch ........................................................................................ 3-23-2 EPO Circuit Breakers ................................................................................... 3-35-1 Slice Volumes ................................................................................................ 5-35-2 Stripe Volumes .............................................................................................. 5-55-3 Addressing a Stripe Volume ....................................................................... 5-65-4 Efficient Stripe Configuration ..................................................................... 5-65-5 Volumes of Unequal Size ............................................................................ 5-75-6 Unevenly Divisible Volumes ...................................................................... 5-75-7 Meta Volume Configuration ....................................................................... 5-95-8 Meta Volume Addressing ......................................................................... 5-105-9 Slice/Stripe Meta Volume ......................................................................... 5-105-10 Addressing a Stripe/Slice Meta Volume ................................................ 5-115-11 Business Continuance Volumes ............................................................... 5-136-1 NFS File System Configuration .................................................................. 6-56-2 PC Client Access ......................................................................................... 6-117-1 Standby Relationship ................................................................................... 7-37-2 Failover Example .......................................................................................... 7-6B-1 Problem Detection and Resolution Process .............................................. B-2

Celerra File Server Basic Administration Guide xiii

Figures

xiv Celerra File Server Basic Administration Guide

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the Celerra File Server product line, EMC from time to time releases new revisions of Celerra hardware and software. Therefore, some functions described in this manual may not be supported by all revisions of Celerra software or hardware presently in use. For the most up-to-date information on product features, see your product release notes.

If your Celerra system does not offer a function described in this guide, please contact your EMC representative for a hardware upgrade or software update.

Audience This guide is part of the Celerra File Server documentation set and is meant for the System Administrator to use during system setup, configuration, and management.

Organization This manual is organized into the following chapters and appendices:

Chapter 1, Introducing the Celerra File Server presents an overview of the Celerra File Server and describes the features, benefits, and setup required when using the command-line interface.

It also provides an overview of the required configuration process with references to step-by-step instructions contained in other parts of this manual.

Chapter 2, Planning for a Celerra File Server, describes how to prepare for Celerra File Server installation.

Chapter 3, Power Sequences, provides essential procedures for powering up and powering down the Celerra cabinet.

Celerra File Server Basic Administration Guide xv

xvi

Preface

Chapter 4, Configuring Celerra Network Services, describes the initial configuration and verification procedures as well as these network services [Domain Name Service (DNS), Network Information Service (NIS), and Network Time Protocol (NTP)].

Chapter 5, Creating Volumes, File Systems, and Mount Points, describes features that help you manage volumes and describes how to create volumes, file systems, and mount points.

Chapter 6, Mounting and Exporting File Systems for the NFS User, describes how to mount and export file systems for NFS environments.

Chapter 7, Configuring Standbys, discusses how to configure standby Data Movers and Control Stations.

Chapter 8, Managing File Systems, provides procedures for managing file systems.

Chapter 9, Managing Your System, provides the procedures for system administration tasks.

Chapter 10, Control Station Utilities, describes how to back up and recover the Control Station database and enable daemons.

Chapter 11, Troubleshooting, provides troubleshooting scenarios and procedures for managing your system.

Appendix A, Technical Specifications, provides the Celerra File Server physical, environmental, hardware, and software specifications.

Appendix B, Customer Support, describes the information you should have before contacting EMC’s Customer Support Center.

Appendix C, GNU General Public License, describes software license information.

The Glossary provides definitions of technical terms.

RelatedDocumentation

Other related EMC publications include:

◆ Celerra File Server Command Reference Manual

◆ Symmetrix Product Manual for your specific Symmetrix model

◆ System documentation for your FC4700-2 storage system

Conventions Used inthis Manual

EMC uses the following conventions for notes, cautions, warnings, and danger notices in its user documentation:


Preface

A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid damage to the system or equipment. The caution may apply to hardware or software.

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning.

DANGER

A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the warning.

EMC uses the following type style conventions in this guide:

Type ConventionsEMC uses the following type style conventions in this guide:

Entries that you type are shown in monospace:

QUERY [CUU=cuu|VOLSER=volser]

The statements presented in this manual follow these conventions:

◆ CAPITALIZATION = must be typed

Boldface Specific filenames or complete paths. Window names and menu items in text. Emphasis in cautions and warnings.

Italic Introduces new terms or unique word usage in text. Command line arguments when used in text.

Fixed space Examples of specific command entries, displayed text, or program listings.

Fixed italic Arguments used in examples of command line syntax.

Celerra File Server Basic Administration Guide xvii

xviii

Preface

◆ [] = optional entry

◆ Italics = parameter

◆ | = alternative parameter value

◆ UNDERSCORED = default

Where to Get Help Obtain technical support by calling your local sales office.

For service, call:

(800) 782-4362 (SVC-4EMC)or(800) 543-4782 (543-4SVC)

and ask for Customer Service.

If you are located outside the USA, call the nearest EMC office for technical assistance. These offices are listed at the back of this manual.

Sales and CustomerService Contacts

For the list of EMC sales locations, please access the EMC home page at:

http://www.emc.com/contact/

For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink Web site at:

http://powerlink.emc.com

Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to [email protected] with your opinions of this guide.


1Invisible Body Tag

This chapter introduces you to the EMC Celerra File Server and it provides an overview of configuring the server for basic operations.

◆ Overview of the Celerra File Server ................................................1-2◆ Celerra File Server Features..............................................................1-4◆ Celerra File Server Cabinet ...............................................................1-8◆ Hardware Components...................................................................1-15◆ About Celerra Connections ............................................................1-21◆ Software Components .....................................................................1-26◆ Celerra File Server Environment ...................................................1-27◆ Celerra Graphical User Interfaces..................................................1-29◆ Configuring Celerra.........................................................................1-32◆ User Access Configuration Options..............................................1-36

Introducing theCelerra File Server

Introducing the Celerra File Server 1-1

1

1-2

Introducing the Celerra File Server

Overview of the Celerra File ServerThe EMC® Celerra™ File Server is a high-end network file server that works in combination with EMC storage system products to provide fast, scalable, high-capacity network storage of centralized data.

The hardware platform consists of the Celerra cabinet (containing a Control Station and multiple Data Movers) and one of the following:

◆ High-performance Symmetrix® Integrated Cached Disk Array (ICDA) storage system

◆ FC4700-2 storage system

These powerful combinations produce sharable, network-accessible storage.

The Celerra File Server supports Network File System (NFS®) and Common Internet File System (CIFS) clients and is easily integrated into existing networks by using standard network interface protocols. The Celerra File Server is easily managed through the command-line interface or a graphical user interface (GUI) known as the Celerra File Server Manager.

Advantages Enterprises that deploy the Celerra File Server can improve performance and maximize efficiency by:

◆ Reducing administrative costs: The Celerra File Server provides a single, centralized hardware and software environment.

◆ Increasing data availability: The Celerra File Server provides redundant components that ensure that access is reliable and data is available.

◆ Improving server performance: The Celerra File Server includes an optimized operating system that increases server performance and data access speed.


1Introducing the Celerra File Server

Figure 1-1 shows the Celerra File Server within a network environment.

Figure 1-1 Celerra File Server Environment

Limitations In this release, the minimum configuration required is the Symmetrix 4 storage system or the FC4700-2 storage system.

A Celerra File Server cannot be attached to:

◆ More than one FC4700-2 storage system

◆ Both a Symmetrix and an FC4700-2 storage system

◆ An FC4700-2 storage system that is also used as a SAN stored array for other servers

Storage System

Celerra

Network

CFS-000196

Overview of the Celerra File Server 1-3

1

1-4


Celerra File Server FeaturesThis section describes the features of the Celerra File Server, including:

◆ Storage capacity

◆ System expansion and scalability

◆ Data access and availability

◆ Server connections to network users

◆ NFS and CIFS compatibility

◆ Time Synchronization

Large StorageCapacity

The Celerra File Server is attached to a storage system. The capacity of the storage system depends on the model and the configuration. Configurations with multiple storage systems provide greater storage capacity.

Large storage capacity storage system configurations are available by requesting a price quotation (RPQ). In addition, EMC storage system development is on-going, and subsequent models may provide capacities greater than the figures cited here. Contact your service representative to learn about the capacities of the most recent storage system models.

System Expansion andScalability

You can increase Celerra File Server performance and capacity by adding:

Table 1-1 Increase Performance and Capacity

Celerra Symmetrix FC4700-2

Data Movers — to increase network connections and throughput

Symmetrix disks — to increase storage capacity

Disk Array Enclosures (DAE) — to increase storage capacity

Memory — to improve Data Mover performance

Symmetrix cache memory and/or directors — to increase I/O and throughput

Disk Array Processor Enclosures (DPE) — to increase I/O and throughput



Data Access andAvailability

The Celerra File Server ensures data availability by providing the software features listed in Table 1-2.

Table 1-2 Celerra File Server Software Features and Benefits

Feature Benefits

Standby Data Movers (optional) This ensures uninterrupted access to data in the unlikely event of a Data Mover failure. Failover support is automatic, quick, and transparent to users accessing the Celerra File Server. Refer to Data Mover Availability on page 7-2 for information about Data Mover failover.

Dual Control Stations (optional) This ensures uninterrupted installation and management of the Celerra File Server.

Independent Data Mover and Control Station Architecture

Except during configuration activity, Data Movers operate independently from the Control Station. Control Station failure affects only the Celerra File Server installation and management features, not user access to data. In dual Control Station environments, the Control Station can failover.

Speedy Reboot and Recovery The Celerra File Server minimizes server reboot recovery time by using a metadata log to record file system changes.

Celerra File Server Features 1-5

1

1-6


Server Connections tothe Network

Celerra File Servers can provide connectivity for the following network types:

◆ Gigabit Ethernet

◆ 10/100Base-T Fast Ethernet

FDDI and ATM are supported in earlier versions of the Celerra File Server. For information about FDDI and ATM, refer to the Celerra File Server Network Guide.

The Celerra File Server can accommodate up to 14 Data Movers, each of which can contain two network interface cards (NICs). Refer to Chapter 4, Configuring Celerra Network Services, for more information about using the Celerra File Server with your network.

Redundant Components The Celerra File Server provides a full set of redundant critical components. Dual components include redundant data paths within the storage system, dual SCSI or Fibre Channel connections between the storage system and the Data Movers, redundant internal Ethernet between each Data Mover and the Control Station, at least two network paths on each Data Mover, n+1 load-sharing power supplies, on-board battery backup, and dual AC power lines. Refer to Hardware Components on page 1-15 for information about Celerra File Server hardware components.Note: The FC4700-2 storage system uses only Fibre Channel connections.

Self-Diagnostic and Self-Reporting Capabilities

The EMC CallHome and Call-In support features automatically alert an EMC support engineer in a support center, providing remote diagnostics and non intrusive repair. Support centers are staffed 7 days a week, 24 hours a day.

Nondisruptive Component Repair Hot-swappable components reduce repair time and increase data availability. Field replaceable components include individual Data Movers, the Control Station, power supplies, battery backup systems, fan subsystems, and all SCSI and Fibre Channel, and power cables.

Table 1-2 Celerra File Server Software Features and Benefits (continued)

Feature Benefits



NFS and CIFSCompatibility

The Celerra File Server supports Network File System (NFS) and Common Internet File System (CIFS) protocols, and provides file system support of both UNIX® and Windows® users. Refer to Chapter 6, Mounting and Exporting File Systems for the NFS User for more information about NFS services available with the Celerra File Server and to the Celerra File Server Windows Environment Configuration Guide for more information about CIFS services.

Time Synchronization Distributed network systems require time synchronization to ensure accurate timestamping and event executions. The Celerra File Server Network Time Protocol (NTP) allows you to synchronize the internal clock in the Data Mover and Control Stations with an external time source.

Celerra File Server Features 1-7

1

1-8


Celerra File Server CabinetThe Celerra File Server cabinet connects to an EMC storage system by Fibre Channel-switched fabric (FC-SW) connections or by Ultra Fast Wide Differential (UFWD) Small Computer Systems Interface (SCSI) connections.

The FC4700-2 storage system connects only to the Celerra File Server with Fibre Channel-switched fabric.

Both the storage system and the Celerra File Server are based on industry-standard hardware architectures. These architectures, which combine modular, industry-standard hardware with optimized software, allow you to integrate advances in hardware and software technology quickly and easily.

EMC has several high-performance storage systems which are designed for on-line data storage. For a complete list of EMC system models and capabilities, refer to the appropriate documentation or contact your EMC representative.

Depending on the model, the Celerra File Server consists of one or two cabinets:

◆ In single enclosure models, the Celerra File Server and the Symmetrix system share the same cabinet enclosures. The FC4700-2 is not available in a single enclosure.

◆ In two-cabinet models, one cabinet contains the Celerra File Server and the other cabinet contains the storage system.

Single Enclosure The single enclosure is designed to provide a single solution (Celerra and Symmetrix) with a smaller footprint. This enclosure contains the following subsystems and is shown in Figure 1-2:

◆ CelerraThe Celerra subsystem is built into the lower half of the cabinet and contains slots for up to two Control Stations and four Data Movers. The system is controlled locally using a keyboard and screen located on the front door.



◆ Internal Dedicated SymmetrixThis is similar to a Symmetrix 33xx or 8xxx ICDA system. It is built into the upper half of the cabinet, and is controlled locally with a Service Processor, mounted inside the rear door.

The two subsystems share the power and backup systems, and are interconnected for data transfer.

Figure 1-2 Single Enclosure Model (Celerra and Symmetrix)

SYMNETWORK

SYMMODEM

CS1

Disk Drives

Data Mover_5

Data Mover_3

Control Station_1(Optional)

SCSI Adapter CardsDisk Adapters

ICDA Comm Board

ICDA Power Supplies

ICDA Modem Connection

Data Mover_4

Data Mover_2

Control Station_0

Power SuppliesComm Board

Control StationsModem Connection(s)

EMUX Board

Main PowerAux Power

Fibre Cards

CFS_000113

DedicatedSymmetrix

ServerSubsystem

Celerra File Server Cabinet 1-9

1

1-10


Multi-Cabinet Enclosure

The Celerra cabinet has up to 16 positions, or slots, numbered 0 through 15. The bottom row of slots contain one Control Station in slot 0 and an optional Control Station in slot 1, and up to 14 servers, or Data Movers, in the upper-seven rows (slot 2 through slot 15). Figure 1-3 shows this cabinet.

Figure 1-3 Celerra Multi-Cabinet Enclosure

Modem Connections

Enhanced MUX (EMUX) Cable

Comm Board

Keyboard

Bottom View of LCD

CS0LED

CS1LED

Control StationToggle Switch

Slot Numbers and DefaultControl Station/Data Mover Names

Power Supplies

PS1

PS3

PS2

PS4

PS5 PS6CFS-000206

Slot #0CS_0

Slot #6Server_6

Slot #4Server_4

Slot #2Server_2

Slot #8Server_8

Slot #10Server_10

Slot #14Server_14

Slot #15Server_15

Slot #12Server_12

Slot #13Server_13

Slot #11Server_11

Slot #9Server_9

Slot #7Server_7

Slot #5Server_5

Slot #3Server_3

Slot #1CS_1



Celerra File Server Cabinet Features

Current Celerra File Server cabinets have the monitor and keyboard inside the front door. Older models have the monitor and keyboard outside the front door. Depending on the model, the keyboard either drops down or pulls out.

Flat Panel Display The flat panel display provides the monitor for interactions with the Celerra File Server local management interface. You use the local management interface to enter Celerra File Server commands.

You can enter commands to the local interface using the keyboard and monitor on the front of the Celerra File Server cabinet. Remote users can access the Celerra over telnet, or by invoking the Celerra File Server Manager from a compatible Web browser.

The flat panel display supports only the Celerra command line interface.

Keyboard andTrackball

You use the keyboard and built-in trackball to enter commands to the local Celerra File Server interface.

Celerra File Server Functionality

The Celerra File Server modular hardware design and autonomous hardware architecture provide maximum data availability.

To ensure high availability, each Data Mover within the Celerra File Server acts as a fully autonomous file server and, except during Data Mover configuration, operates independently from the Control Station. This ensures that Data Mover operations are not interrupted in the unlikely event of a Control Station failure.

Data Movers perform server functions by mounting and exporting file systems and by responding to user requests for data access. Data Movers connect to the external network through Gigabit Ethernet or Fast Ethernet.

FDDI and ATM are supported in earlier versions of the Celerra File Server. For information about FDDI and ATM, refer to the Celerra File Server Network Guide.

The Data Movers and the Control Station connect to the storage system using either Ultra FWD SCSI cards or Fibre Channel adapters (FA). You can only connect to a FC4700-2 storage system using Fibre Channel adapters. When connecting the Data Movers to your storage system, the specific number of connections depends on the attached storage system model.


1

1-12


The Celerra File Server supports the following industry standards:

◆ NFS v2 and v3 over TCP and UDP

◆ CIFS over TCP

◆ FTP over TCP, providing utilities for transferring files among heterogeneous systems

To manage the Celerra File Server, you can use either the command line interface or the Web-based Celerra File Server Manager interface. The Celerra File Server also supports:

◆ Celerra Monitor software for monitoring the performance of a Symmetrix attached to a Celerra File Server and the performance of any Data Movers mounted in the Celerra cabinet

◆ SNMP MIB-II for monitoring server operations and for integration with third-party network management software

◆ Time service, using NTP on individual Data Movers and on the Control Station

Figure 1-4 shows Celerra File Server hardware operations with SCSI connections between the Data Movers and the Symmetrix system and Figure 1-5 shows the Celerra File Server hardware operations with Fibre Channel connections between the Data Movers and the FC4700-2 storage system.



.

Figure 1-4 Hardware Operations (Symmetrix)

Symmetrix Back-end Store

Memory

DiskAdapter

DiskDirector

ChannelDirector

SCSIAdapter

Ultra SCSIConnectors

Control Station

Celerra Cabinet

NFS over TCP/IP, UDP/IPCIFS over TCP/IP

Gigabit Ethernet,Fast Ethernet

Network

Data Mover

Internal EthernetConnection

DiskAdapter

DiskDirector

DiskAdapter

DiskDirector

DiskAdapter

DiskDirector

ChannelDirector

SCSIAdapter

ChannelDirector

SCSIAdapter

ChannelDirector

SCSIAdapter

CFS-000197


1

1-14


Figure 1-5 Hardware Operations (FC4700-2)

Control Station

Celerra Cabinet

NFS over TCP/IP, UDP/IPCIFS over TCP/IP

Gigabit Ethernet,Fast Ethernet

Network

Data Mover

Internal EthernetConnection

CFS-000200

StorageProcessor

A

StorageProcessor

B

Switch

Switch

LinkControlCard

LinkControlCard

LinkControlCard

LinkControlCard

FC4700-2



Hardware ComponentsThe Celerra File Server cabinet contains the major Celerra hardware components. It contains from one to four backplanes, each with four hardware slots. In the lower backplane:

◆ The lower-left slot is reserved for the Control Station.

◆ The lower-right slot is available for a standby Control Station.

Depending on your configuration, the remaining backplane slots contain individual Data Movers, each consisting of:

◆ Pentium® based motherboard

◆ PCI bus

◆ Network cards

◆ Fibre Channel adapters or SSCI cards

The lower section of the cabinet contains redundant power supplies, battery backup, and dual power cables, as well as the CD-ROM drive for loading software, the communications boards, and a multiplexer.

The Celerra File Server contains the following core hardware components:

◆ Primary Control Station and, optionally, a secondary Control Station

◆ 2 to 14 Data Movers

◆ Power supplies

◆ Modem connections

◆ Communications board

◆ Console multiplexer

These components are described in the following sections.

Control Station The Control Station provides the installation, configuration, and management features of the Celerra File Server. Control Station features enable you to install and upgrade software, add hardware components, configure network interfaces, allocate volumes, create and map NFS and CIFS file systems, and manage and monitor individual Data Movers.

Hardware Components 1-15

1

1-16


To provide redundancy in the unlikely event of a Control Station failure, the Celerra File Server can be configured to include a secondary Control Station. The primary Control Station is installed in slot 0 in the Celerra cabinet, and the secondary Control Station is installed in slot 1.

Some older Celerra File Server cabinets do not support a second Control Station. Contact your EMC representative to determine whether you need a hardware upgrade.

Figure 1-6 shows a detailed view of the front panel of a Control Station.

Figure 1-6 Typical Front Panel View of a Control Station

DualSCSI(HBA)

FloppyDrive

External NIC Fast Ethernet(FE)

InternalEthernet

(10 Base2)

Video (SVGA)UnusedMouse / Keyboard

CD-ROM Connection(to MUX Board)

CFS_000124

1 2 3 4 5 6 87



The Control Station provides eight component positions (slots), configured as shown in Table 1-3.

IP Addresses The IP addresses of the Ethernet NICs used for Celerra File Server internal communications are automatically set during installation.

You provide an IP address for the external NIC to the EMC Customer Engineer during the configuration process.

Data Movers Each Data Mover provides the functions of a fully autonomous file server. Data Movers mount and export file systems stored on the storage system and respond to user requests for data access. Data Movers connect to the external network through Fast Ethernet or Gigabit Ethernet.

Earlier models of the Data Mover used FDDI and ATM network protocols.

You manage the Data Movers using the Control Station by entering commands (through the command line interface or through the Celerra File Server Manager) that refer to individual Data Movers by name. User access to data is independent of the Control Station, however, and is not interrupted in the unlikely event of a Control Station failure.

Table 1-3 Control Station Slots

Slot numbers Function

1 Connects the external CD-ROM to the MUX board

2 Connects to the floppy drive; used to install Control Station software

3 Contains the dual-port Ultra FWD SCSI or the Fibre Channel HBA connection to the Symmetrix. Note: For the FC4700-2, use only the Fibre Channel HBA connection.

4 Contains the NIC that connects the Control Station to your network

5 Unused

6 Connects the video board that is used by the monitor on the front of the Celerra File Server cabinet

7, 8 Contain dual, internal Ethernet NICs that connect, through the backplane, to each Data Mover


1

1-18


By default, the name of a Data Mover consists of the prefix server_ added to the number of the slot in which the Data Mover resides. For example, the default name of the server in slot 2 is server_2. You can change the name to whatever you wish and use that name when issuing commands to that Data Mover. Data Movers do not provide remote login capability.

The Celerra File Server supports a minimum of 2 and a maximum of 14 Data Movers. Data Movers are installed in slot 2 through slot 15 in the Celerra File Server cabinet. Refer to Figure 1-3 to see how Data Movers are mounted in the Celerra cabinet.

Figure 1-7 shows a detailed front view of a typical Data Mover configuration. Other Data Movers will have varying external configurations.

Figure 1-7 510 Data Mover Front View

Compared to earlier Data Movers, the internal network connections have moved from the front of the Data Mover to connectors located on the back of the Data Mover.

The VGA interface is now built into the motherboard and is located next to the keyboard/mouse connectors.

RX

RX

TX

TX

RX

TX

RX

TX

CFS-000168Keyboard & Mouse Connectors

VGA Connector

I/O Adapter Slots(Fibre Channel, Fast Ethernet, Gigabit Ethernet)

1 2 3 4 5 6



Each Data Mover provides six component positions, configured as shown in Table 1-4.

IP Addresses The IP addresses of the Ethernet NICs used for Celerra internal communications are set during installation.

You provide an IP address for each NIC in each Data Mover when you configure your external network addresses. For a multiport NIC, you provide individual IP addresses for each port in the NIC.

You can also configure an Ethernet channel, combining several ports into a single trunk with a single IP address. For a description of Ethernet channels, refer to Celerra File Server Network Guide.

Power Supplies The Celerra File Server contains up to six 220 VAC 750 W power supplies in the lower front of the cabinet. These provide N+1 capability to the Celerra File Server.

The Electrical Power Output (EPO) box, visible from the back of the cabinet, contains up to six circuit breakers, one for each power supply. Pressing the red button on the back of the Celerra File Server cabinet automatically trips the circuit breakers.

Main and auxiliary power provide the main and secondary power sources for the system.

If you increase the number of Data Movers to greater than 10 and have only four power supplies, you must add a fifth power supply.

Table 1-4 Data Mover Slots

Slot Numbers Contain

1 Fibre Channel Adapter that connects the Data Mover to the storage system

2 Used for Fibre Channel connections to the storage system or to Tape Library Units

3 Fast Ethernet NIC that connects the Data Mover to the external network

4 Fast Ethernet NIC available for additional configurations

5 and 6 Gigabit Ethernet NICs available for additional configurations


1

1-20


CD-ROM Drive The CD-ROM drive is located above the power supplies. You use the CD-ROM drive to install and upgrade Celerra File Server software.

Modem Connections

Modem connections provide the network access for the CallHome and Call-in utilities. Your customer engineer configures CallHome and Call-in variables during the installation of the Celerra File Server.

CallHome utilities enable the Celerra File Server to automatically notify the EMC Customer Support Center if problems occur on the system. Call-in utilities allow EMC Customer Engineers and technical experts to log in to the Celerra File Server remotely to diagnose and repair problems.

It is sometimes necessary to change site information. For example, you may want to change a telephone number or modify the name of an administrator. To modify CallHome or Call-in variables, contact your EMC service representative.

Communications (COMM) Board

The COMM board monitors environmental conditions and adds messages to the system logs.

Console Multiplexer The Console Multiplexer lets you communicate to the Control Station from the front panel display and keyboard. It also connects the CD-ROM to the Control Station.



About Celerra ConnectionsThe Celerra uses the following connections to storage systems:

◆ Small Computer Systems Interface

◆ Fibre Channel

Small Computer Systems Interface

The Celerra File Server uses Ultra Fast Wide Differential (UFWD) Small Computer Systems Interface (SCSI). Each SCSI interface card has dual ports that are used to connect to the Symmetrix or tape library unit (TLU).

While Fibre Channel is the preferred physical interface between Control Stations, Data Movers, and the storage system, SCSI is used on many Data Movers and Control Stations that do not have Fibre Channel capabilities. When Fibre Channel and SCSI adapters are found on a Data Mover, the SCSI interface is to be used only for the connection to the TLU. Currently, upgrades for both Control Stations and Data Movers are available through EMC Customer Service Representatives.

Only Fibre Channel connectivity is supported for the FC4700-2 storage system.

Fibre Channel Fibre Channel is a serial data transfer interface that operates over optical fiber (or copper wire) at data rates up to 100 MB/s (theoretical limit). Networking and I/O protocols (such as SCSI commands) are encapsulated and transported within Fibre Channel frames, which allows high-speed transfer of multiple protocols over the same physical interface.

The Celerra File Server supports switched fabric topology and supports ANSI Fiber Channel Class 3 service, a connectionless service similar to packet-switched systems, such as Ethernet, in that the path between two devices is not reserved or dedicated.

About Celerra Connections 1-21

1

1-22


Port Types Fibre Channel standards use the term node to describe any device connected to one or more other devices over a Fibre Channel interface. Each node has at least one port that connects to other ports in other nodes. There are seven Fibre Channel port types. A switched fabric without arbitrated loop connections, as supported by the Celerra File Server, uses only the types listed in Table 1-5.

Using Celerra WithFibre Channel

Fibre Channel is supported only on Data Movers and Control Stations with Fibre Channel adapters. Data Movers and Control Stations with Fibre Channel enabled are configured with the following Fibre Channel adapter:

Topologies A Fibre Channel switched environment consists of a physical topology and a logical topology. The physical topology describes the physical connections among devices. The logical topology describes the logical paths established between the Data Mover device names and their associated storage system ports and volumes.

Table 1-5 Fibre Channel Port Types

Port Type Description Use

N_Port A port on a node outside the fabric. Once connected, the port is part of the fabric, but it remains an N_Port.

Fibre Channel-equipped Data Movers connect to the switched fabric using N_Ports.

F_Port A port on a switching device that connects to an N_Port and brings that connection (internally within the switch) to the fabric.

The switches that constitute the switched fabric connect to the Data Movers using F_Ports

E_Port A port on a switching device that connects to another E_Port on the same or a different switching device.

The switches that constitute the switched fabric connect to the each other using E_Ports

G-Port A generic port on the switching device that can operate as an E_Port or an F_Port.

This port, on connection, automatically configures as an F_Port or E_Port.

Table 1-6 Fibre Channel Adapter Specifications

Requirement Data Mover Control Station

Adapter type Emulex LP9002DC/L Qlogic QLA-2212

Ports per adapter Two, full-duplex Two, full-duplex

Cable requirements Multimode cable with SC connectors

Multimode cable with SC connectors



Celerra logical topologies in the switched environment can generally be described in terms of capacity (fan-out) and consolidation (fan-in).

Capacity Topology (Fan-Out)The capacity topology allows a single adapter in a Celerra Data Mover to access multiple storage system devices. A capacity topology, as used in the Celerra File Server, is described by the fan-out rate. In a case with a single Data Mover adapter and three storage systems, the Data Mover N_port connects to the switch F_port. In turn, each storage system Fibre Channel Adapter N_port connects to another switch F_port. Figure 1-8 depicts a simplified fan-out topology.

This Fibre Channel Adapter port is sometimes called the FA port for the Symmetrix and the Storage Processor port for the FC4700-2.

Figure 1-8 Fan-Out Topology

In Figure 1-8, redundancy is implied.

Consolidation Topology (Fan-In)The consolidation topology, as used in the Celerra File Server, is recommended when one or more Data Movers must be connected to

CelerraFibre Channel Switch

Storage System 1

Storage System 2

Storage System 3

DataMover

DataMover

CFS-000212


1

1-24


a high-capacity storage system, expanding the required number of server connections.

A consolidation topology is described by the fan-in ratio. A 32-port switch can be configured with a physical topology of 24 Data Mover links and 4 storage system links, organized into a logical topology of four 6:1 fan-ins. The 6 Data Mover adapter ports that consolidate into each storage system port have shared access to the port.

In the simplified scenario in Figure 1-9, a single Fibre Channel Adapter port is shared by 6 Data Mover connections; a 6:1 logical topology is implied.

Figure 1-9 Fan-In Topology

For most environments, the recommended fan-in ratio is 6:1.

About ZoningYou can configure the switched fabric into zones to limit each Data Mover to a specific set of storage system front-end addresses (for example, when you have a large number of available volumes). Zoning allows you to group devices by such characteristics as function and location. Devices can be assigned to one or more zones. Devices in a zone can see all addresses in the zone, but none in other zones.

DataMover

DataMover

DataMover

DataMover

DataMover

DataMover

Celerra Storage SystemClass 3Fabric

Switch

Switch

CFS-000211

FibreChannel

Adapters



For the Celerra File Server, a zone should encompass both ports on a Data Mover HBA and two Fibre Channel ports in the storage system on different adapters. Note that each FA can be a member of multiple zones, but that only 1 HBA can be in a zone.

Consult your switch vendor’s documentation for details on how to configure zones.

Configuring the Fabric With a Celerra File Server

Using one or more Fibre Channel switches, you can connect the Celerra File Server and storage system across a Class 3 switched fabric. In this configuration, one port on each Data Mover is connected to one switch, while the other port is connected to the other switch. In turn, each port on the Symmetrix FA or each port on a FC4700-2 Storage Processor is also connected to a different switch. These redundant connections provide the following performance advantages:

◆ Under normal conditions, each port automatically performs load-balancing.

◆ The distributed connections to different switches provide both physical redundancy and circuit redundancy by providing alternative connections through the switched fabric in the event of Data Mover port, switch, or Fibre Channel Adapter port failure.

In addition, if the switched fabric is properly configured, each switch can fail over to another in the fabric. In the event of a single switch failure, if the Data Mover and the storage system each have active connections to the fabric, Fibre Channel connectivity between the two devices is maintained.

Supported Switches For the list of Fibre Channel switches that the Celerra File Server supports, please contact your EMC Customer Service representative. Refer to the vendor documentation for particular switches for more information on configuration procedures and capabilities.

For More Information For a comprehensive tutorial on Fibre Channel technology, visit the Fiber Channel Industry Association’s Web site at http://www.fibrechannel.com/technology.


1

1-26


Software ComponentsThe Celerra File Server software components include:

◆ Control Station software, which provides a controlling subsystem and management interface

◆ Data Access in Real Time (DART) software, which provides a server operating system optimized for I/O

The software components are described in the following sections.

Control Station Software

Control Station software provides the controlling subsystem of the Celerra File Server as well as the management interface to all file server components. The Control Station runs an EMC derivative of Red Hat Linux® as the operating system on the Control Station. You use Control Station software to install, manage, and configure the Data Movers, monitor the environmental conditions and performance of all components, and implement the CallHome and dial-in support features.

As part of the installation process, EMC installs Celerra File Server NAS software on the Control Station. NAS software lets you monitor and manage the Data Movers through the Control Station.

A second Control Station can be installed to provide redundancy. Older Celerra cabinets, however, may not support the use of dual Control Stations. Contact your EMC representative to determine whether you need an upgrade to support dual Control Stations.

Data Mover Software

DART software provides a real-time, multi-threaded operating system, optimized for network file access and input/output (I/O) operations. DART software is installed by the Control Station on each Data Mover. Each Data Mover functions as an individual file server and provides user access to the file systems that you create on Data Movers and export for use by clients.



Celerra File Server EnvironmentThe Celerra File Server is a multi-protocol network file server that supports a variety of network connections, protocols, and users.

Network File Sharing Protocols

The Celerra File Server provides support for the following protocols:

◆ Network File Systems (NFS) — provides distributed file services for transparent file sharing in network environments. The NFS protocol is typically used by native UNIX clients, as well as by network clients that include NFS capabilities.

◆ Common Internet File System (CIFS) — extends the Microsoft® SMB file-sharing protocol. It allows users to share file systems over the Internet and Intranet. The CIFS protocol is used by Windows and Windows NT® machines, and is also available on some UNIX and VMSTM systems.

◆ Celerra HighRoad adds a thin, lightweight File Mapping Protocol (FMP) for file layout information and shared conflicts management between the hosts and Celerra. Hosts use the file layout information to read and write file data directly from and to the storage system. One benefit is that data access is at channel speed rather than network speed.

Celerra High Road is supported only on a Celerra File Server attached to a Symmetrix.

Figure 1-10 shows how NFS and CIFS software is organized within a Data Mover. Both CIFS and NFS interfaces to UxFS, a log-based UNIX file system. Data is stored in UxFS format on the disk and can be made available to CIFS and NFS users.

Celerra File Server Environment 1-27

1

1-28


Figure 1-10 NFS and CIFS Software

The File Mapping Protocol (FMP) is supported only on a Celerra File Server attached to a Symmetrix.

Other Network ProtocolsThe Celerra File Server supports the File Transfer Protocol (FTP). FTP is a client/server protocol that operates over TCP/IP and allows file uploading and downloading across heterogeneous systems.

WindowsWorkstation

UNIXWorkstation

FMP

FMP

CIFS(SMB)Traffic

NFSTraffic

Network drivers and protocols

CIFS NFS

Multi-ProtocolSupport Layer

File/System

Storage Layer

Windows Clients UNIX Clients

Data Mover

StorageCFS-000204



Celerra Graphical User InterfacesIn addition to the Linux-like command line interface, the Celerra File Server also offers two graphical user interfaces (GUI) for particular functions:

◆ Celerra File Server Manager

◆ Celerra Monitor

Celerra File Server Manager

The Celerra File Server Manager interface enables you to perform most Celerra File Server operations, including configuring and managing your Celerra File Server. You must have an administrator or operator password to log in to the Celerra File Server Manager.

The Celerra File Server Manager provides a simpler way to enter commands and parameters, especially if you are not familiar with the Linux command style and syntax. The Celerra File Server Manager allows you to select the function you want, and then enters the appropriate Celerra File Server command for you.

Most Celerra File Server commands can be accessed through the Celerra File Server Manager, but some are available only through the command line interface. Refer to Celerra File Server Celerra Monitor and Celerra File Server Manager Technical Note for detailed information about using the Celerra File Server Manager.

To use the Celerra File Server Manager, your system must meet the requirements shown in Table 1-7.

Celerra Graphical User Interfaces 1-29

1

1-30


Table 1-7 Requirements for Celerra File Server Manager

If your system does not meet the minimum resolution requirements, the browser functions at suboptimal capacity. You can increase the area of the browser window available to Celerra File Server Manager by hiding some of the browser toolbars.

The documentation for this interface is contained in and accessible through on-line help.

Celerra Monitor Celerra Monitor is an application that lets you closely monitor specific performance data about the Data Movers in the Celerra cabinet and the attached Symmetrix system that provides the data storage capability of the Celerra File Server. You select the object (Symmetrix system or individual Data Mover) you want to monitor from the top-level window of the Celerra Monitor.

You can use Celerra Monitor to perform the following tasks for the Symmetrix system and the Data Movers:

◆ Receive online alerts of events posted to the system log

◆ View performance

◆ View configuration

◆ View statistics

◆ View logs

◆ View summaries of past configurations

◆ Control access and polling of monitored data

Workstation • UNIX workstation running with minimal options displayed• PC running Windows 95, Windows 98, Windows NT, or

Windows 2000

Monitor • 17-inch or greater is preferred, with support for at least 256 colors• Minimum recommended display resolution is 640 x 480• Preferred resolutions are 1152 x 900 (UNIX) or 1024 x 768 (PC)

Browser One of the following Internet browsers:• Netscape Navigator® 4.5 or higher• Internet Explorer 5.0 or higherIn addition:• JavaScript™ (1.2 or higher) must be enabled (the default)• Cache (disk and memory) must be turned off



Celerra Monitor is a Java™ client/server application that consists of a Java server (poller) that runs on the Control Station and a Java applet (or in the case of Windows, an application) that runs in your browser. Celerra Monitor requires the following minimum configuration:

◆ Direct (rather than proxy) connection to the Internet

◆ Netscape Navigator 4.5 or later or Internet Explorer 5.0 or later

◆ Java Virtual Machine (JVM) 5.0 or later

◆ Symmetrix/4.8 with 5265 microcode or later configuration

Celerra Monitor is only supported on a Celerra File Server attached to a Symmetrix. To monitor the performance of the FC4700-2 storage system, use Navisphere® Manager.

SupportedManagement

Platforms

The workstation on which the Celerra Monitor software is installed must have one of the following minimum configurations.

Table 1-8 Minimum Configuration for the Celerra Monitor

Refer to the Celerra File Server Manager and Celerra Monitor Technical Note for detailed information about installing and using Celerra Monitor.

Operating System Minimum Requirements

Solaris®

(SunOS® 5.5.1)300 MHz processor, 64 MB RAM, 256 MB swap space, 16K color graphics, Netscape Navigator 4.5 or greater

Windows NT 4.0Windows 95Windows 98Windows 2000

200 MHz processor, 64 MB RAM, 128 MB virtual memory, 16K color graphics, 5 MB disk space for Celerra Monitor, 6 MB disk space for JVM 5.0, Netscape Navigator 4.5 or greater, or Internet Explorer 5.0 or greater

Celerra Graphical User Interfaces 1-31

1

1-32


Configuring CelerraOnce EMC’s Customer Service Engineer has completed the initial installation of your Celerra File Server hardware and software, you can begin to customize the Celerra to support the users in your organization.

You must make a number of decisions during the configuration process, especially in the areas of volume configuration, network connectivity, and NFS/CIFS interoperability. These decisions must be based on user expectations and your specific network environment.

System Tasks Using either interface as System Administrator, you perform such tasks as:

◆ System configuration and verification (drives, networks, accounts).

◆ Volume configuration and file system creation.

◆ File system management (creating mount points, mounting/unmounting, extending, deleting, renaming, exporting/unexporting, checking capacity, creating snapshots, archiving).

◆ System monitoring (Data Mover free space, routing table, ARP table, activity logs).

Required System Configuration

Table 1-9 describes the basic steps involved in configuring the Celerra File Server. A brief description of each task, along with specific chapter and page references, is provided.



Also refer to Figure 1-11 for a flow chart of the configuration process.

Table 1-9 Celerra File Server Configuration Process

Task Description ReferenceSee page

1 Set up network interfacesSet up the network interfaces that enable users to connect to the Data Movers and retrieve files.

Creating an IP Interface 4-2

2 Create volumes Create the volume configuration required to support file systems.

Creating Volume Configurations 5-2

3 Create file systemsCreate the file systems that contain user files.

Creating a File System 5-15

4 Create a mount pointCreate a network access point for each Data Mover.

Creating a Mount Point 5-16

5 Mount the file system with optionsMount the file system, specifying the options appropriate for your application.

Mounting a File SystemCelerra File Server Windows Environment Configuration Guide

6-6

6 Export file systemMake the network access point available for NFS and CIFS users.

Exporting a PathCelerra File Server Windows Environment Configuration Guide

6-8

7 Optionally, configure Data Movers to use CIFSConfigure the Data Movers to become members of a Windows domain and establish security policies.

Celerra File Server Windows Environment Configuration Guide

8 Configure network servicesConfigure NIS, DNS, and NTP.

Configuring DNS and NISConfiguring Time Services

4-7 4-9

9 Configure failoverConfigure a Data Mover as a standby for a primary Data Mover.

Configuring Standby Data Movers 7-8

Configuring Celerra 1-33

1

1-34


Figure 1-11 Celerra File Server Configuration Process

Mount withoptions for

NFS

CIFS

NFS

Configureprotocol

Configurenetworkservices

Create filesystems

Createvolumes

Createmount point

Set upnetwork

interfaces

Reviewsystem

configuration

Celerrainstallationcomplete

Mount withoptions for

CIFS

Createshare for

CIFS users

ConfigureData

Movers forCIFS

Y

N

End BasicConfiguration

Usestandby?

Configurestandby

Export forNFS users

CFS-000180



Enhanced System Configuration

Once you have completed the basic Celerra configuration, you can further customize the operation of your system. For example, you can configure the Celerra for disaster recovery.

For a description of additional features, refer to the Celerra File Server User Information CD-ROM, included with this documentation set.

Configuring Celerra 1-35

1

1-36


User Access Configuration OptionsUsing Celerra commands and options, you can configure file systems for access by:

◆ CIFS users◆ NFS users◆ Both CIFS and NFS users

Supported Platforms The Celerra File Server supports users on platforms that have NFS and CIFS capability. For a list of supported platforms, review the Celerra File Server Interoperability matrix:

http://www.emc.com/horizontal/interoperability/matrices/Celerra_Interoperability_Matrix.pdf

Where to Go From HereReferring to Table 1-9 and Figure 1-11, complete the configuration steps appropriate for your network environment.


2Invisible Body Tag

Read this chapter as you plan your Celerra File Server configuration with EMC network and storage specialists. You can also consult this chapter if you need to upgrade your system at a later date.

This chapter describes the Celerra File Server network and storage requirements.

◆ Installation Prerequisites...................................................................2-2◆ Determining Storage Needs .............................................................2-3◆ Determining the Number of Data Movers .....................................2-4◆ Organizing Data and Data Movers .................................................2-5

Planning for a CelerraFile Server

Planning for a Celerra File Server 2-1

2

2-2

Planning for a Celerra File Server

Installation PrerequisitesBefore installing the Celerra File Server, you must determine the following site requirements:

◆ The amount of storage you need today, as well as the amount of additional storage you anticipate needing to expand and meet new business requirements

◆ The number of Data Movers you require

◆ How you will organize volumes and file systems across Data Movers

◆ How your users access data

◆ The topology of your network

◆ The NFS and CIFS environments


2Planning for a Celerra File Server

Determining Storage NeedsWhen calculating storage needs, consider the storage that you need today as well as the space you anticipate needing for future growth. Expanding file system capacity is easier with systems that are well planned and configured with sufficient disk space.

Storage System Options

The amount of storage available depends on the storage system model, the number of disk drives configured, and the protection scheme that you choose. Table 2-1 and Table 2-2 summarizes the ways the available storage protection schemes allocate storage.

Table 2-1 Symmetrix Storage Schemes and Storage Usage

Storage Scheme Storage Usage Supports Drive Size

Mirroring(RAID-1)

• 50% available for storage• 50% used for mirroring

• 9 GB• 18 GB• 36 GB• 73 GB• 181 GB

Parity(RAID-S)Requires a Symmetrix system version later than 4.8

• 75% available for storage• 25% used for backup

• 9 GB• 18 GB• 36 GB

Table 2-2 FC4700-2 Storage Schemes and Storage Usage

Storage Scheme Storage Usage Supports Drive Size

Striping(RAID-5)

• 88% available for storage• 12% used for backup

• 73 GB

Determining Storage Needs 2-3

2

2-4


Determining the Number of Data MoversThe number of Data Movers that you need depends on your:

◆ Data Mover performance requirements

◆ Data availability requirements

◆ Network capacity and topology

Determining Performance Requirements

To help you calculate the number of Data Movers you need, EMC provides on-site specialists who work closely with your technical staff to provide customized solutions based on a thorough understanding of your network and storage requirements.

Determining Data Availability

When determining the number of Data Movers, consider your data availability requirements and include any necessary standby Data Movers in your calculations. A standby Data Mover is a spare Data Mover that is configured to provide failover protection in the unlikely event of a Data Mover failure. Networks that require high data availability usually include one or more standby Data Movers.

You can configure a standby Data Mover to substitute for a single Data Mover or for several Data Movers. Standby Data Movers:

◆ Are not configured to export data until a primary Data Mover fails

◆ Do not count in the number of Data Movers you need to access data

Refer to Data Mover Availability on page 7-2 for information about Data Mover failover.


2Planning for a Celerra File Server

Organizing Data and Data MoversOrganizing data and Data Movers involves deciding:

◆ How to map volumes to file systems. File systems are accessed through specific Data Movers.

◆ The type of data to which each Data Mover provides access.

Mapping Volumes to File Systems

Except for the system volumes, all volumes on the storage system unit are initially available for data storage. The Celerra File Server provides volume management features that help you to divide, combine, and group volumes to meet your configuration needs. Refer to Creating Volume Configurations on page 5-2 for additional information.

During configuration, volumes are sized and file systems are created and assigned to individual Data Movers. Data Movers provide I/O access to the file systems that they control and to data that resides within the files.

Figure 2-1 shows how sized volumes are assigned to Data Movers. In this example, the storage system unit is configured with seven 36 GB disk drives. These are combined into three 72 GB volumes, mapped to file systems, and assigned to Data Mover 2, Data Mover 3, and Data Mover 4. The remaining 36 GB of storage is mapped to a file system and assigned to Data Mover 5.

Figure 2-1 Data Mover Volumes

System Volumes

72 GB 72 GB 72 GB

36 GB 36 GB

36 GB 36 GB 36 GB

36 GB

File System File System File System File System

ControlStation

Data Mover#2

Data Mover#3

Data Mover#4

Data Mover#5

36 GB

CFS-000169

Organizing Data and Data Movers 2-5

2

2-6


Typical Configuration

Figure 2-2 shows how volumes, file systems, and Data Movers can be organized to support users within a business environment. In this illustration:

◆ Data Movers 2 and 3 support the CAD department. This department typically generates and stores large amounts of data.

◆ Data Mover 4 supports the CAE department, where data requirements are comparatively smaller.

◆ Data Mover 5 supports administration. This Data Mover is configured with the least amount of storage space.

Figure 2-2 Data Mover Organization

Data Movers own the file systems and the volumes that you assign to them. You can assign multiple Data Movers to a volume and file system only when the access to the volume and file system is read only.

AdministrationCAD Department CAE Department

Ethernet SwitchEthernet Switch

ControlStation

Data Mover# 2

Data Mover# 3

Data Mover# 4

Data Mover# 5

Celerra

StorageSystem

File SystemFile SystemFile SystemFile System

System Volumes

72 GB

36 GB

36 GB

72 GB

36 GB

36 GB

72 GB

36 GB

36 GB

36 GB

CFS-000199


3Invisible Body Tag

This chapter provides instructions on how to power down the Celerra File Server in a planned format and under emergency conditions. It also explains how to apply power to the Celerra cabinet.

◆ Powering Up the Celerra Cabinet....................................................3-2◆ The Command Line Interface...........................................................3-4◆ Logging In ...........................................................................................3-5◆ Planned Power Down........................................................................3-6◆ Emergency Shutdown .......................................................................3-8

Power Sequences

Power Sequences 3-1

3

3-2

Power Sequences

Powering Up the Celerra CabinetThis chapter describes the procedures to power up the Celerra cabinet after a shutdown of any type.

Refer to the Symmetrix Product Manual for your model for information on applying and removing power to the Symmetrix. Refer to the Rackmount Model Hardware Reference and the Setup Guide for information on applying and removing power to the FC4700-2 storage system.

To apply power to the Celerra cabinet, follow these steps:

Step Action

1. Ensure that the attached storage system is powered up and online before you begin.

2. Make sure that the following switches are set to the OFF (0) position:• EPO (red) switch • Main power (black) switch• Circuit breaker switches • Battery breaker switch

3. Turn on the wall breakers for the main (and auxiliary, if required) AC power source, provided by the customer.

4. At the rear door of the Celerra cabinet, set the red EPO switch to the ON (|) position.

5. Set the black AC In power switch to the ON (|) position. The Power indicator should be green.

EPO AC IN

POWER

I

O

I

O

EPO Switch(Red)

PowerIndicator

Power Switch(Black)

CFS_000131


3Power Sequences

The Control Station boot sequence requires approximately five minutes to complete.

6. Turn on the circuit breakers (CB).

6a. If you have attached storage systems, set all circuit breakers in use to the ON (up) position.

6b. If you have a single enclosure cabinet, turn on circuit breakers 5 and 6. Result: This turns on the power to the Symmetrix. Verify that the Symmetrix is online. Refer to the Symmetrix documentation.Set the rest of the circuit breakers to the ON position. Result: This turns on the power to the Celerra.

The fans in the cooling module at the top of the unit are controlled by the circuit breakers that turn on the power to the Celerra.

7. Set the Battery Breaker switch to ON.

Step Action

CB2 (for PS2)

CB4 (for PS4)

CB1 (for PS1)

CB3 (for PS3)

CB6 (for PS6)CB5 (for PS5)

CFS_000123

Powering Up the Celerra Cabinet 3-3

3

3-4

Power Sequences

The Command Line InterfaceThe Celerra File Server command set allows you full management functionality from the command line interface. The commands are primarily Linux-based while others contain Linux-like syntax for familiarity and usability.

To use the command set through the command line interface, one of the following logins is required:

Local Log in with your owner password.

Remote Telnet into the Control Station (using its IP address), and log in with your owner password. You can also use rlogin if you have an established user account.

RS232 Connect, using the modem or terminal server, to the Control Station’s COM2 port.

The login ID and password for your system are both nasadmin during installation. The password can be changed, but the login ID must remain as nasadmin.

Command-Line Parameters

EMC recommends that you limit the length of volume names, file system names, and so forth, as well as limit the use of multiple commands on the same line.

Details on commands can be found in the Celerra File Server Command Reference Manual.


3Power Sequences

Logging InThis section describes how to access the Celerra File Server from the command line interface.

Local Access For local access to the command line interface:

◆ Log in as nasadmin.

Remote Access For remote access to the command line interface:

1. Enter rlogin or telnet followed by the IP Address of the Control Station.

2. Log in as nasadmin.

RS232 Refer to your modem or terminal server documentation for login instructions.

Logging In 3-5

3

3-6

Power Sequences

Planned Power DownYou must power down the system in an orderly way to ensure that data is protected. Otherwise, the system may be damaged and data corrupted.

CAUTION!Never power down the system using the red EPO switch, unless in an emergency. In addition, you must perform this procedure from the Celerra cabinet keyboard. Do not use a telnet session.

To power down the system:

Halt Data Movers To halt all the Data Movers:

Stage Process

1. If you have a backup Control Station, halt the secondary Control Station. See Halting the Control Station(s) on page 10-7.

2. Halt the Data Movers.

3. Halt the primary Control Station.

4. Turn off the power.

Step Action

1. From the Celerra keyboard logon to the Celerra

2. Enter the following command:/nas/bin/server_cpu ALL -halt now

3. Verify that Data Movers are halted by entering the following command:/nas/sbin/getreason

Returns the following information, where slot_n is the last Data Mover in the Celerra cabinet:10 - slot_0 primary control station 0 - slot_2 powered off 0 - slot_3 powered off 0 - slot_4 powered off 0 - slot_n powered off


3Power Sequences

Halt Primary Control Station

To halt the primary Control Station:

Turn Off Power To turn off the power:

Step Action

1. Log in as root.

2. Turn off the Box Monitor, to prevent a call home event, by typing:/etc/rc.d/rc3.d/S95nas stop

3. Enter the following command:/sbin/init 0

Result: The following displays:The system is halted.Power down.

Step Action

1. Turn the Black A/C power switch at the rear door of the Celerra File cabinet to the Off position.If you have a single enclosure Celerra, take the Symmetrix offline. Refer to the Symmetrix documentation.

2. Turn the EPO (red) switch at the rear door of the Celerra cabinet to the Off position.This automatically turns off the circuit breakers.

3. Turn the Battery switch on the battery box to the Off position

4. Verify that all EPO switches are in the Off position.

Planned Power Down 3-7

3

3-8

Power Sequences

Emergency ShutdownUse the following shutdown procedure only during emergency situations.

WARNING

Unless faced with property damage or personal hazards, never power down a Celerra File Server by using the red EPO switch or black circuit breaker switch on either the Symmetrix or the Celerra cabinet.

To power down the Celerra cabinet in the case of an emergency:

At the rear door of the Celerra cabinet, turn the EPO (red) switch to the OFF position.

This action immediately removes all power from the Data Movers, the Control Station, and the Celerra cabinet. No other action is required in case of emergency.

Powering Up After Emergency Shutdown

To power up the system after an emergency shutdown:

Step Action

1. If needed, re-apply power at the AC wall breakers

2. On the rear door of the Celerra cabinet, set the red EPO switch to the ON position.

3. Set all circuit breakers in use on the EPO Box to the ON (up) position. The system starts to power up.

4. Switch the battery breaker to the ON position.

5. On the rear door of the Celerra cabinet, set the black AC IN breaker to the ON position.

6. Verify that all fans in the cooling module on top of the unit are operating.


4Invisible Body Tag

This chapter describes how to configure an IP network interface and network services on a Celerra File Server. Use the information in this chapter for:

◆ Creating an IP Interface.....................................................................4-2◆ Configuring DNS and NIS................................................................4-7◆ Configuring Time Services ...............................................................4-9

Configuring CelerraNetwork Services

Configuring Celerra Network Services 4-1

4

4-2

Configuring Celerra Network Services

Creating an IP InterfaceThe Celerra File Server acts as a link between users and stored data. To reach the data through a network connection, you must configure the Data Mover IP interfaces.

To create a new Data Mover IP network interface you must configure an IP address, a subnet mask, and a broadcast address for the specified interface and device.

Table 4-1 lists the various network cards used in the Celerra File Server with their respective protocols, types, and mnemonics.

TIP: Configuration for ATM NICs does not follow the same procedure as Ethernet and FDDI. Refer to Creating ATM Interfaces in the Celerra File Server Network Guide.

Initially, the system assigns a default name for each device. This pre-configured device name consists of the interface mnemonic, plus a number that is sequentially appended, starting with 0 (zero). For example, the first Ethernet port is ana0. For a device with four Ethernet ports, the remaining ports would be named ana1, ana2, and ana3 (respectively).

Command To view the device names for all adapters available for a specific Data Mover, type:

$ server_sysconfig movername -pci

Example $ server_sysconfig server_2 -pciSample Output server_2 : PCI DEVICES:

Slot: 1 Emulex LP8000 Fibre Channel Controller 1: fcp-0 IRQ: 14 addr: 10000000c9234f00

0: fcp-1 IRQ: 12 addr: 0000000000000000

Table 4-1 NICs Used in Celerra

Protocol Type Interface mnemonic

Fast Ethernet 4-port 10/100 BaseTa ana

Gigabit Ethernet single port ace

FDDIb single and dual attach fpa

ATMb OC-3 fa2 (OC-3)

a. Single-port Ethernet NICs were supported in earlier versions of the Celerra File Server.

b. FDDI and ATM protocols are supported in earlier versions of the Celerra File Server.


4Configuring Celerra Network Services

Slot: 2 Alteon Tigon-2 Gigabit Ethernet Controller 0: ace0 IRQ: 12 txflowctl=disableSlot: 3 Adaptec AHA-3944AUWD Multiple channel SCSI Controller 0: scsi-0 IRQ: 12 0: scsi-1 IRQ: 9Slot: 4 Adaptec ANA-6944 Multiple Fast Ethernet Controller 3: ana0 IRQ: 9 speed=auto duplex=auto rcvbufs=auto txbufs=auto

2: ana1 IRQ: 9 speed=auto duplex=auto rcvbufs=auto txbufs=auto

1: ana2 IRQ: 9 speed=auto duplex=auto rcvbufs=auto txbufs=auto

0: ana3 IRQ: 9 speed=auto duplex=auto rcvbufs=auto txbufs=autoSlot: 5 Alteon Tigon-2 Gigabit Ethernet Controller 0: ace1 IRQ: 14 txflowctl=disable

Table 4-2 simplifies the output from the previous example.

Table 4-2 server_sysconfig Sample Breakout

PCI Slot Number & Port Board Type Device Name

Slot: 1 Port 1 Fibre Channel Controller fcp-0

Slot: 1 Port 0 Fibre Channel Controller fcp-1

Slot: 2 Port 0 Gigabit Ethernet Card ace0

Slot: 3 Port 0 Multi-Channel SCSI Controller scsi-0

Slot: 3 Port 0 Multi-Channel SCSI Controller scsi-1

Slot: 4 Port 3 Fast Ethernet Controller ana0

Slot: 4 Port 2 Fast Ethernet Controller acna1


4

4-4


The output listing that is returned after issuing the server_sysconfig -pci command contains all PCI–based adapters, including Fiber Channel and SCSI controller cards.

To configure an IP interface for one of the physical ports on a Fast Ethernet card, select the physical port you want to connect to and then use the server_ifconfig command to create the interface.

Table 4-3 consolidates sample information needed to create an IP interface on a Fast Ethernet card shown in Table 4-2.

The following example uses the information in Table 4-3 to configure (create) an IP interface on a Fast Ethernet card using the server_ifconfig command. The sample ethernet card is physically located in the Data Mover named: server_2.

Slot: 4 Port 1 Fast Ethernet Controller ana2

Slot 4 Port 0 Fast Ethernet Controller ana3

Slot: 5 Port 0 Gigabit Ethernet Controller ace1

Table 4-2 server_sysconfig Sample Breakout (continued)

PCI Slot Number & Port Board Type Device Name

Table 4-3 Sample Parameters for an IP Interface

Information Needed Parameter

Data Mover name: server_2

Specific Board Type: Fast Ethernet

Device Name for Slot: 4 Port 0 ana3

Name you wish to give the Interface; Marketing-1

Sample IP: 192.168.42.88

Sample Netmask: 255.255.255.0

Sample Broadcast Address: 192.168.42.255



Command $ server_ifconfig movername -c -D device_name -n if_name -p IP ip_addr ip_mask ipbroadcast

Example $ server_ifconfig server_2 -c -D ana3 -n Marketing-1 -p IP 192.168.42.88 255.255.255.0 192.168.42.255

Output server_2 : done

In the example above, port: 0 of the Fast Ethernet card in slot: 4 of the Data Mover named server_2 (from Table 4-2) is configured for IP. It has a device name of ana3 and an interface name of Marketing-1.

Troubleshooting Tip If the following message appears:

server_2: No such device or address

The addresses you have entered are invalid. Make sure that the broadcast address is in the same subnet as the IP address that you entered.

Viewing Network Interfaces

The device name and interface name of every NIC contained in and recognized by your system is listed by the server_ifconfig -a command. If you have not yet configured an interface, it will not appear in the list of network interfaces.

Command To obtain a list of configured interfaces on a Data Mover, type:

$ server_ifconfig movername -a

Sample Output server_2 :Marketing-1 protocol=IP device=ana3

inet=192.168.42.88 netmask=255.255.255.0 broadcast=192.168.42.255

UP, ethernet, mtu=1500, vlan=0, macaddr=0:0:d1:1e:55:72loop protocol=IP device=loop


UP, loopback, mtu=32704, vlan=0, macaddr=0:0:0:0:0:0 netname=localhostel31 protocol=IP device=el31


UP, ethernet, mtu=1500, vlan=0, macaddr=0:1:2:c0:7e:ef netname=localhostel30 protocol=IP device=el30


4

4-6



UP, ethernet, mtu=1500, vlan=0, macaddr=0:1:2:c0:7e:af netname=localhost

Troubleshooting Tip If you experience problems in network connectivity, your network cables may not have been connected properly. Contact EMC Customer Service.



Configuring DNS and NISUsing server_dns and server_nis, you can create, delete, and view Domain Name Service (DNS) and Network Information Service (NIS) server configurations. You can also query the NIS server. The NIS and DNS servers reside on the network and can be made available to specified Data Movers.

DNS Authentication DNS is a distributed database system that provides authentication services by mapping machine names to the IP address, the protocol and the domain name for client applications. DNS servers maintain databases of hierarchical name structures for various domains in order to use logical names for device identification. To enable the DNS server for a Data Mover, you must know:

◆ The domain

◆ IP address for the host machine

◆ Protocol

Note: See Celerra File Server Windows Environment Configuration Guide for DNS combinations with Windows domains.

NIS Authentication NIS provides authentication for client access to file systems by automatically mapping the IP address and the host name. Once the server is authenticated, access to the file system is permitted. To enable the NIS server for a Data Mover, you must know:

◆ The domain

◆ IP address for the NIS server

Configuring DataMovers as DNS/NIS

Clients

To configure a Data Mover as a DNS or NIS client, you must set the DNS or NIS server configuration for the Data Mover.

You can enter a total of 13 IP addresses; 3 for the DNS and 10 for the NIS server.

Command To create an NIS entry, type:

$ server_nis movername domainname ip_addr

Command To create an DNS entry, type:

$ server_dns movername -p protocol domain_name ip_addr

Configuring DNS and NIS 4-7

4

4-8


Command To delete an NIS entry, type:

$ server_nis movername -delete domainname ip_addr

Command To delete an DNS entry, type:

$ server_dns movername -delete domain_name

Command To display the DNS configuration, type:

$ server_dns movername



Configuring Time Services When a Data Mover reboots and time service activates, the Data Mover polls external time sources and the time on the Data Mover is automatically adjusted. Since this happens at boot, the setting of the clock is not externally visible.

If time synchronization is started after the Data Mover has been running for some time, the server_date -sync_delay option should be used so that the time is gradually adjusted.

After its initial poll, the time synchronization thread polls the time servers (hosts) in order, after each polling interval. After sending the polling message, the Data Mover waits for a reply. When the reply from the first host is received, it is used to correct the time. If no reply is received, then other time source hosts are polled in the order specified. The addresses should be specified in dot decimal form (e.g., 192.1.1.100).

When you start time synchronization, you must indicate a host that acts as the external time source. The host is the address(es) of the host(s) to be used as time synchronization server(s). The hosts (up to four) must be running as NTP, version 2 time servers.

If you are going to synchronize your Data Movers to the Control Station, refer to Configuring NTP on page 10-3 to first configure NTP on the Control Station.

To synchronize a Data Mover to the Control Station, enter the Control Station IP address as the host.

Command To start time synchronization between a Data Mover and an external source, type:

$ server_date movername timesvc start ntp host host host

If you indicate Delay under Clock Set, but do not indicate a time, the delay default is 1 hour or 60 minutes. If you do not indicate a Delay, the default is to execute immediately and again at the polling time indicated.

Sample Output server_3 : done

Configuring Time Services 4-9

4

4-10


Where to Go From HereAfter you configure and test a network interface, you can either continue to configure your network or create volumes and file systems.

To continue configuring your network refer to the Celerra File Server Network Guide to complete the following:

◆ Modify an IP interface after it has been created.

◆ Create multiple interfaces for a device.

◆ Delete an interface after it has been created.

◆ Create Gigabit Ethernet Interfaces.

◆ Create a Fail Safe Network device.

◆ Create Ethernet Channel devices.

To complete the following volume and file system tasks, refer to Chapter 5 and Chapter 6 in this guide and to the Celerra File Server Windows Environment Configuration Guide:

◆ Create volume configurations required to support file systems.

◆ Create the file systems.

◆ Create a network access point (mount point) for each Data Mover.

◆ Mount the file system, specifying the options appropriate for your application (NFS or CIFS).


5

This chapter describes how to create volumes, file systems, and mount points.

◆ Creating Volume Configurations.....................................................5-2◆ Slice Volumes ......................................................................................5-3◆ Stripe Volumes....................................................................................5-5◆ Meta Volumes .....................................................................................5-9◆ Business Continuance Volumes .....................................................5-13◆ Creating a File System .....................................................................5-15◆ Creating a Mount Point...................................................................5-16

Creating Volumes, FileSystems, and Mount

Points

Creating Volumes, File Systems, and Mount Points 5-1

5

5-2

Creating Volumes, File Systems, and Mount Points

Creating Volume ConfigurationsThe Celerra File Server’s volume management feature allows you to choose from a variety of volume configurations that allow you to optimize your system’s storage potential. To create a volume configuration, you must select an unused volume or volumes to create into your new volume. If you do not indicate a name for your new volume configuration, the system will assign a default name which can be changed later.

Volume Types The Celerra File Server supports the volume types listed in Table 5-1.

Important: File systems can only be created and stored on meta volumes.

Before beginning volume management, refer to Chapter 2, Planning for a Celerra File Server, for information about assessing and determining your storage requirements, and which configuration would best accommodate your needs.

Configuring a Disk Volume

Volumes are initially configured as disk volumes. Each usable storage system volume appears as a usable disk volume. After the initial installation, you configure disk volumes only when you add disks to the storage system.

Table 5-1 Volume Types

Volume Type Description For More Information

Disk volume Represents the basic disk configuration on the storage system.

Refer to Configuring a Disk Volume on page 5-2.

Slice volume Typically provides a smaller disk section, similar to a UNIX disk partition.

Refer to Slice Volumes on page 5-3.

Stripe volume Provides an arrangement of volumes, organized into a set of interlaced stripes that improve volume performance.

Refer to Stripe Volumes on page 5-5.

Meta volume Provides a required concatenation of slice, stripe, or disk volumes. Meta volumes are required for dynamic file system storage.

Refer to Meta Volumes on page 5-9.

Business Continuance volume

Enables the use of TimeFinder/FS file system copies. Only supported on a Celerra File Server attached to a Symmetrix.

Refer to Business Continuance Volumes on page 5-13.


5Creating Volumes, File Systems, and Mount Points

Slice VolumesA slice volume is a logical, non-overlapping section cut from another volume component. A slice volume is similar to, but more versatile than, a UNIX disk partition. Unlike UNIX disk partitions, you can create an unlimited number of slice volumes.

Configuring a Slice Volume

Slice volumes are automatically created during Celerra File Server installation and are immediately available for configuration.

Slice volumes can be configured to any size but are typically used to create smaller, more manageable units of storage. The definition of a “more manageable” logical volume size depends on your system configuration and the type of data you are storing.

Figure 5-1 shows a 2 GB volume on which a 0.5 GB slice is defined.

Figure 5-1 Slice Volumes

Although slice volumes define your storage capacity, you cannot use them to store file information. You must configure slice volumes as part of a meta volume in order to store file system data on them. Refer to the section on Meta Volumes on page 5-9 for additional information.

Creating a Slice Volume

Slice volumes are cut out of other volume configurations to make smaller, more manageable volumes.

When you create a slice volume, you can indicate an offset that is the distance (in megabytes) from the end of one slice to the start of the next. Unless a value is specified for the offset (the point on the container volume where the slice volume begins), the system places

2.0 GBBasic Volume

0

0.5 GB

1.0 GB

2.0 GB

0.5 GBSlice Volume

CFS_000023

Slice Volumes 5-3

5

5-4


the slice in the first-fit algorithm (default) that is the next available volume space.

You must first identify the volume from which the slice volume will be created. The root slice volumes created during installation appear when you list your volume configurations; however, you do not have access privileges to them, and therefore, cannot execute any commands against them.

To verify that the volume name selected for the slice volume is not already used, type:

$ nas_slice -list

Command To create a slice, type:

$ nas_slice -name name -create volume_name size

Sample Output id =219name = s11acl = 0in_use = falseslice_of = d58offset (MB) = 0size (MB) = 1230volume_name = s11

Troubleshooting Tip If a volume with sufficient space is not available, an error message appears when you attempt to create the slice volume.

To verify that the volume being selected to slice has adequate unused volume, type:

$ nas_volume -size volume



Stripe VolumesA stripe volume is a logical arrangement of participating disk, slice, or meta volumes that are organized, as equally as possible, into a set of interlaced stripes. Stripe volumes:

◆ Improve system performance by balancing the load across the participating volumes.

◆ Achieve greater performance and higher aggregate throughput because all participating volumes can be active concurrently.

Figure 5-2 shows an example of a stripe volume. The stripe is created across three participating volumes of equal size.

Figure 5-2 Stripe Volumes

Improving Performance With Stripe Volumes

Stripe volumes improve performance because, unlike disk, slice, and meta volumes, addressing within a stripe volume is conducted in an interlaced fashion across volumes, rather than sequentially. Data is interlaced within the stripe volume starting with stripe unit 0 on the first participating volume, continuing to stripe unit 1 on the next participating volume, and so on. As necessary, data wraps back to the first participating volume.

In a stripe volume, a read request is spread across all component volumes concurrently. This scheme optimizes system efficiency, creates less waiting time, and produces higher productivity than disk, slice, or meta volumes that are read sequentially. Figure 5-3 shows addressing within a stripe volume.

10 MB Stripe

10 MB Stripe

10 MB Stripe

30 MB Slice 30 MB Slice 30 MB Slice

CFS_000024

Stripe Volumes 5-5

5

5-6


Figure 5-3 Addressing a Stripe Volume

Configuration Guidelines for Stripe Volumes

Follow these guidelines to configure a stripe volume:

◆ Carefully consider the size of the stripe volume you want. After the stripe volume is created, its size remains fixed. To modify the size of the stripe volume, you must copy the data to another area, remove the existing stripe, and reconfigure the volumes you want.

◆ Configure stripes to use the maximum amount of disk space. Figure 5-4 shows maximum utilization. In this case, the size of the participating volumes within the stripe are uniform and are evenly divisible by the size of the stripe. Each participating volume contains the same number of stripes.

Figure 5-4 Efficient Stripe Configuration

◆ Space is wasted if the volumes are evenly divisible by the stripe size but are unequal in capacity. Figure 5-5 shows this configuration. The extra unit on the larger volume is not included in the configuration and is unavailable for data storage.

Stripe Volume

CFS_000025

10 MB Stripe

10 MB Stripe

10 MB Stripe


CFS_000024



Figure 5-5 Volumes of Unequal Size

◆ Space is also wasted if the size of the volume is not evenly divisible by the stripe size. Figure 5-6 shows an example of a stripe volume with residual storage space.

Figure 5-6 Unevenly Divisible Volumes

Creating a Stripe Volume

Creating a stripe volume allows you to achieve a higher aggregate throughput from a volume set since stripe units contained on volumes in the volume set can be active concurrently.

Special consideration should be paid to the sizes of the volumes and stripes used to create a stripe volume so that unused storage is minimized.

10 MB Stripe

10 MB Stripe

10 MB Stripe


10 MBUnused

CFS_000026

64 Blocks

64 Blocks

64 Blocks

192 Blocks 230 Blocks 192 Blocks

38 (unused blocks)

CFS_000027

Stripe Volumes 5-7

5

5-8


Command To create a stripe volume, type:

$ nas_volume -name name -create -Stripe stripe_size volume_name, volume_name

The recommended stripe size is 32768 bytes; the default size is 32K. Stripe depths must be in multiples of 8192 bytes. If you do not select a name for the stripe volume, a default name is assigned.

Sample Output id = 316name = str1acl = 0in_use = falsetype = slicestripe_size = 32768volume_set = d5,d6,d7disks = d5,d6,d7



Meta VolumesA meta volume is an end-to-end concatenation of one or more disk, slice, stripe, or meta volumes. A meta volume is required to create a file system, because meta volumes provide the expandable storage capacity that may be needed to dynamically expand file systems. A meta volume also provides a way to form a logical volume that is larger than a single disk.

Configuring a Meta Volume

Meta volumes can be created from a disk, stripe, slice, or meta volume. The most common configuration is a meta volume that is created using one or more available stripe volumes. You then create a file system on the meta volume.

You can expand a meta volume by adding additional disk, stripe, slice, or meta volumes to it. Once the new volume is combined with the meta volume, it logically becomes part of the meta volume, takes on the attributes of the meta volume, and is able to host your file system data. Figure 5-7 depicts a meta volume configuration, using three disk volumes.

Figure 5-7 Meta Volume Configuration

DiskVolume

DiskVolume

DiskVolume

Meta Volume

CFS_000028

Meta Volumes 5-9

5

5-10


Addressing Within a Meta Volume

All information stored within a meta volume is arranged in addressable logical blocks and is organized in sequential, end-to-end fashion. Figure 5-8 shows meta volume addressing.

Figure 5-8 Meta Volume Addressing

The meta volume shown in Figure 5-9 is created from a stripe volume and a slice volume.

Figure 5-9 Slice/Stripe Meta Volume

MetaVolume

Information is readinto the Meta Volume in

ascending address order...

Logical BlockAddress 0

Logical BlockAddress N

CFS_000029

Stripe Volume

+ 2 GBSlice Volume

CFS_000030



Addressing within the stripe volume starts at logical block 0 and continues sequentially through logical block 8 in an interlaced fashion across the participating volumes. The slice volume is essentially one 2 GB block addressed sequentially. Figure 5-10 shows the sequential flow of addressing in the resulting meta volume.

Figure 5-10 Addressing a Stripe/Slice Meta Volume

Expanding Storage Capacity

The Celerra File Server provides many ways to expand storage capacity. For example, you can create a stripe volume, convert it to a meta volume, and use it to store file system data. Later, the file system capacity can be expanded by adding additional volumes to the meta volume.

The total capacity of a meta volume equals the sum of all volumes that compose the meta volume.

Creating a Meta Volume

To create and store a file system, you must first create a meta volume. The size of the meta volume must be at least 1 MB to accommodate a file system.

0

3

6

1

4

7

2

5

8

9

Meta Volume

CFS_000031

Meta Volumes 5-11

5

5-12


Command To combine volumes into a meta volume, type:

$ nas_volume -name name -create -Meta volume_name,volume_name

If you do not enter a meta volume name, a default is assigned.

Sample Output id = 312name = meta1acl = 0in_use = falsetype = metavolume_set = d5,d6,d7disks = d5,d6,d7

Verifying Volume Configurations

Your system contains a set of slice volumes that can be arranged into various volume configurations.

Command To obtain a list of all of the current volume configurations within your system, type:

$ nas_volume -listSample Output

id23456

inuseyyyyy

type44444

nameroot_d2d3d4d5d6

cltype00000

clid1,1202,1213,1224,1255,126



Business Continuance VolumesBusiness continuance volumes (BCVs) are dedicated volumes that can be attached to a standard volume upon which a file system resides. Your EMC Customer Engineer creates BCVs on the storage system before the Celerra File Server software is installed. After this process is completed, you create one or more meta volumes on the standard volume(s) and create and mount one or more file systems on the meta volume.

Business Continuance volumes are supported only on a Celerra File Server attached to a Symmetrix.

BCVs must have the capacity to accommodate your largest potential file system. Refer to the appropriate storage system documentation for details on how to create BCVs. Figure 5-11 shows the relationship between standard volumes and BCVs.

Figure 5-11 Business Continuance Volumes

The TimeFinder/FS feature of the Celerra File Server uses BCVs to enable you to create file system copies and dynamically mirror file systems, as follows:

◆ The file system copy function enables you to create an exact copy of a file system that you can use as input to a restore operation, for application development, or for testing.

◆ The mirror function enables you to create a file system copy in which all changes to the original file system are reflected in the mirrored system.

StandardVolume

BusinessContinuance

Volume(BCV)

Size Must Be Equal

18 GB 18 GB

CFS_000032

Business Continuance Volumes 5-13

5

5-14


After a BCV is created, you can use the Celerra File Server Manager or the nas_fs command to create a file system copy.

CAUTION!Do not attempt to use Symmetrix TimeFinder tools and utilities with file system copies created by Celerra TimeFinder/FS.



Creating a File SystemOnce you have created a meta volume, you can create a file system.

Mandatory File System Requirements

When creating a file system:

◆ You can create a file system on only non-root meta volumes that are not in use.

◆ A meta volume must be at least 1 MB to accommodate a file system.

◆ You can specify the meta volume either by name or by size.

For information about verifying the size of a meta volume, refer to Checking Capacity on page 8-6.

To obtain a list of all existing volumes, type:$ nas_volume -list

Command To create a file system, type:

$ nas_fs -name name -create volume_name

The nas_fs man page lists the options available for creating a file system.

Sample Output id = 17name = file1acl = 0in_use = falsetype = uxfsvolume = meta1rw_servers = ro_server =symm_devs = 014,015,016disks = d5,d6,d7,d8

Now that you have created a file system, you must create a mount point before you can mount the file system for server access.

Creating a File System 5-15

5

5-16


Creating a Mount PointA mount point must be created on a Data Mover before you can mount a file system. Each file system can be mounted on only one mount point, and each mount point can provide access to one file system at a time.

The mount point must begin with a “/” followed by alphanumeric characters. For example: /new.

You can mount a file system, rooted on a subdirectory of an already exported file system, as long as the file system has not previously been mounted above or below that mount point.

The maximum number of nested mount points that you can create under a directory is eight; however, you can only mount a file system up to the seventh level.

Command To create a mount point, type:

$ server_mountpoint movername -c pathname

Sample Output server_3: done

Command To verify mount points for a server, type:

$ server_mountpoint movername -list

Sample Output server_3 :/.etc_common/ufs1/ufs1_snap1


6nvisible Body Tag

This chapter describes how to mount and export a file system for NFS users.

◆ User Types...........................................................................................6-2◆ Understanding NFS ...........................................................................6-3◆ Typical NFS Configuration ...............................................................6-4◆ Mounting a File System.....................................................................6-6◆ Exporting a Path.................................................................................6-8◆ Providing PC User Access .............................................................. 6-11◆ Unexporting Paths/Shares .............................................................6-14

Mounting andExporting File Systems

for the NFS User

Mounting and Exporting File Systems for the NFS User 6-1

6

6-2

Mounting and Exporting File Systems for the NFS User

User TypesThe Celerra File Server supports NFS and CIFS users. You must understand which type of user you have so you can configure the file system protocol and access for that user.

The Celerra File Server lets you configure a file system for use by:

◆ NFS users only ◆ CIFS users only ◆ Both CIFS and NFS users

The Celerra File Server also lets you map an NFS and CIFS user to the same username and group ID. This mapping provides the user with seamless access to shared file system data.

For information about configuring the file system protocol for the CIFS environment only or for both an NFS and CIFS environment, refer to the Celerra File Server Windows Environment Configuration Guide.


6Mounting and Exporting File Systems for the NFS User

Understanding NFS The Celerra File Server is a multiprotocol machine that supports the NFS environment. NFS is a client/server, distributed file service that implements file sharing in network environments.

The NFS protocol enables the Celerra File Server to assume the functions of a Network File System Server. NFS environments typically include:

◆ Native UNIX clients◆ Windows systems configured with third-party applications that

provide NFS client services

The Network Information System (NIS) is used on some configurations to manage common files, such as password, group, and host files. The Domain Name Server (DNS) may also be available to resolve hostnames to IP addresses or IP addresses to hostnames for hosts outside the local network.

NFS Environment The NFS protocol provides distributed file services in client/server environments. The NFS protocol is typically configured for environments that include many native UNIX systems. Systems can also include any non-UNIX machines configured to run NFS software.

When you configure a file system for NFS users and associate it with a Data Mover, the Data Mover operates as an NFS server.

In an NFS server environment, the file system is mounted on the Data Mover and exported and mounted on clients. Exported file systems are available across the network and can be mounted by remote users.

NFS User Authentication

Authentication validates NFS user passwords. Authentication is accomplished on the remote client during login, using the local authentication login method. Users who are authenticated are permitted network access to the Data Mover. Access to stored files and directories is determined by the Data Mover, which matches the User and Group ID identification attached to the file or directory with the information supplied by the accessing user.

Understanding NFS 6-3

6

6-4


Typical NFS ConfigurationYou configure a file system for access by NFS users with the Celerra File Server Manager or by typing commands at the command line interface. This section describes how to configure a file system for access by NFS users.

For information about configuring for CIFS users only or for both NFS and CIFS users, refer to Celerra File Server Windows Environment Configuration Guide.

NFS Configuration Overview

Configuring a file system for NFS users involves:

1. Creating a file system

2. Creating a mount point

3. Mounting the file system on a specified Data Mover

4. Exporting the file system to NFS users

5. Mounting the file system on the users’ machines

Tasks 1 and 2 are discussed in Chapter 5, Creating Volumes, File Systems, and Mount Points. Tasks 3-5 are discussed in this chapter.

Sample NFS User Configuration

Figure 6-1 shows a Data Mover configured for NFS users. The Data Mover:

◆ Connects to the network using an IP address

◆ Compares the user request information with the access parameters associated with the file system, directory, or file

◆ Permits or denies file access by the Data Mover, based on the result of the match



Figure 6-1 NFS File System Configuration

FileSystem

Celerra File ServerNativeUNIX Client

Windows ClientRunning NFSClient Software

IP Address

CFS-000181

NetworkData

Mover

Typical NFS Configuration 6-5

6

6-6


Mounting a File System Once you create a mount point, you must mount your file system on the path to provide users access.

If you are mounting a file system for CIFS users, refer to the Celerra File Server Windows Environment Configuration Guide.

NFS File Locking File locking provides a mechanism for ensuring file integrity when more than one user may access the same file. File locks manage attempts to read, write, or lock a file that is held by another user.

In an NFS system, locks can be either:

◆ Read locks

◆ Exclusive (write) locks

NFS locking rules are cooperative, so that a client is allowed to access a file locked by another client if it does not use the lock procedure.

More than one process can hold a read lock on a particular file, but if one process holds an exclusive lock, no other process can hold any lock on the file until the exclusive lock is removed. A read lock can be changed to an exclusive lock, and vice versa.

In NFS, a process can perform advisory locks on a file segment. An advisory lock does not affect read and write access to the file, but it informs other users that the file is already in use.

NFS Mount Options When performing a mount, you can institute the following options to define the mount:

Read-Write When a file system is mounted read-write (default) on a Data Mover, only that Data Mover is allowed access to the file system. No other Data Mover is allowed read or read-write access to that file system.

Read-Only When a file system is mounted read-only on a Data Mover, clients cannot write to the file system regardless of the export permissions. A file system can be mounted read-only on several Data Movers concurrently, as long as no Data Mover has mounted the file system as read-write.



Permanent File systems are mounted permanently by default. The mount is entered into the mount table and the mount and the options defined remain in effect, regardless of a system reboot.

If you perform a temporary unmount, in the case of a system reboot, the mount table is activated, and the file system is automatically mounted again.

When mounting a file system, you must know which Data Mover contains your mount point.

To list available Data Movers, type:

$ nas_server -list

To list mount points for each Data Mover, type:

$ server_mountpoint movername -list

To list existing file systems, type:

$ nas_fs -list

Command To mount a file system, type:

$ server_mount movername -option options fs_name mount_point

This command can take up to a minute or so to complete depending on the size of your file system.


Troubleshooting Tip #1 If the following message appears:

server_x: No such file or directory

The mount point may not exist on the specified Data Mover.


server_x: Device busy

You may have tried to execute the same command more than once. Check your list of mounted file systems to verify that the path has already been successfully mounted.

Mounting a File System 6-7

6

6-8


Exporting a Path After creating a mount point and mounting a file system, you must export the path to allow NFS users to access the system.

Paths are exported from Data Movers using the server_export command. Each time the server_export command is issued, an entry is added to existing entries in an export table. Entries to the table are permanent and are automatically re-exported if the system reboots.

You can overwrite existing options in an export entry by including the -ignore option in the command string. This forces the system to overwrite the options in the export table. Whatever options you include in the command line, overwrite the options in the export table associated with this path.

To display a list of all exports for one or all Data Movers use the -list option.

For more information on the server_export command and supported options, refer to the server_export on-line man page or to the Celerra File Server Command Reference Manual.

NFS Export Options Table 6-1 describes the available NFS options for exporting a path.

Table 6-1 NFS Export Options

Entry Option Result

ro[=client1[:client2][:client3]...] Exports the pathname for NFS clients as read-only. If not specified, the pathname is exported read-write.

rw=client[:client]... Exports the pathname for NFS clients as read-mostly. Read-mostly means exported read-only to most machines, but read-write to those specified. If not specified, the pathname is exported read-write to all. A client may be hostname, an IP address, a subnet, or a netgroup. See the Caution below regarding the use of netgroups.

A subnet is an IP address/netmask. For example, 168.159.50.0/255.255.255.0.



CAUTION!If a host belongs to more than one netgroup, the behavior of the access rights granted for the host is unpredictable, therefore, a host should not belong to multiple netgroups. Netgroups are defined in the system (/.etc/netgroup file or through NIS). There should be no overlap of host(s). See the server_export man page for an example.

anon=uid If a request comes from an unknown user, use the UID as the effective user ID. Root users (uid= 0) are always considered “unknown” by the NFS server, unless they are included in the root option. The default value for this option is the UID of the user “nobody.” If the user “nobody” does not exist, then the value 65534 is used.

root=client[:client]... Provides root access only to the root users from a specified hostname, netgroup, subnet, or IP address. The listing must be typed without spaces, and be colon-separated. The default is for no hosts to be granted root access. See Caution below regarding the use of netgroups.

access=client[:client]... Provides mount access to each client listed. A client may be a hostname, an IP address, a subnet or a netgroup. The listing must be typed without spaces, and be colon-separated. Each client in the list is first checked for in the /.etc/hosts database, then in the /.etc/netgroup database, then finally it checks the NIS or DNS server (if enabled). The default value, no access list, allows any machine to mount the given directory. You create the hosts and netgroup files on the Control Station using your preferred method (with an editor, or by copying from another node, and so on), then copy them to the Data Mover using the server_file command.

A subnet is an IP address/netmask. For example, 168.159.50.0/255.255.255.0.

The Celerra File Server supports netgroups. If the system does not find the client in /.etc/hosts, or in /.etc/netgroup, then it checks the NIS or DNS server (if enabled). If the client name does not exist in either case, then the system displays an error message such as “undefined netgroup.” See the Caution that follows regarding the use of netgroups.

Table 6-1 NFS Export Options (continued)

Entry Option Result

Exporting a Path 6-9

6

6-10


Important: Since the default for root=client[:client] is for no users to be given root access, if you do not enter a value, a root user is unable to create files or directories in this exported file system. To allow a root user write access to the exported file system, export the file system with root privileges to either the Control Station or a trusted host.

Command To export a path, type:

$ server_export movername -option options pathname


Troubleshooting Tip If a system does not find the client in the /.etc/hosts or in /.etc/netgroups directory, the system then checks the NIS server, if it is enabled. If the system cannot find client name, an error message appears.

Export All Every time the system boots, every entry in the export table is re-exported. To re-export every entry within the table while the system is running, type:

$ server_export movername -all

The number of NFS entries in the export table that can be "displayed" is 256. If the entries exceed 256 and you enter server_export -list, an error message is displayed instead of a display of the export table, although all entries are supported.



Providing PC User AccessTo provide PC users NFS access to file systems, you must export the path of the file system for the respective users.

Authenticating PC Clients for NFS Access

To allow PC clients NFS access to the Celerra File Server and its files, a PC client must be successfully authenticated. See Figure 6-2.

Figure 6-2 PC Client Access

Since different user authentication methods exist in PC and UNIX environments, an authentication daemon (typically rpc.pcnfsd or pcnfsd) bridges these differences. The daemon runs on the Data Mover and performs the following services:

1. The daemon receives and validates the user name and password provided by the PC client.

2. The daemon assigns the PC client a user ID and group ID (UID/GID) for each user/password combination.

1

2

NFS Server(Celerra File

Server)

User AuthenticationDaemon

(pcnfsd or rpc.pcnfsd)

SendsUsername

& Password

ReturnsUID/GID

PCRunning PC-NFSClient Software

CFS-000214

Providing PC User Access 6-11

6

6-12


3. PC clients then use the assigned UID/GID to access the Celerra File Server. See Figure 6-2.

Typically, if using NFS from a PC, an authentication daemon is already in use and can be used with the Celerra File Server without change. If your PC is not already using NFS, then you need to purchase a PC client NFS software package, such as Hummingbird® Communications Ltd’s PC-NFS® or NFS-MaestroTM software.

Setting Up PC Client Software

This section describes how to set up a PC client software package for network access to the Celerra File Server. The examples used are PC-NFS and NFS Maestro.

To enable this feature, complete the following steps:

1. Set up a user account. See Task 1: Create a Linux User on page 9-9.

2. Open the /nas/server/server_x/netd file with a text editor, add pcnfs on a separate line, and save the file.

Where x is the number of the Data Mover.

3. Reboot the Data Mover.

4. Export a file system for the user(s) to access. Refer to Exporting a Path on page 6-8.

5. On the PC, launch the PC-NFS or NFS Maestro software

Refer to the vendor’s respective user manual for details on what is required at this point for setup and/or login. For example, PC-NFS is capable of detecting any system running pcnfsd in the subnet, while NFS Maestro has an option where you specify the system's name.

6. Enter the username and password as required by the software package.

The username and password are sent to the Data Mover running pcnfsd, which returns the User ID/Group ID numbers for the PC client.

From this point on, whenever the PC client issues a mount request, the user is authenticated and the rest of the activity is pure NFS traffic typical between a client and server.



Hummingbird PC NFS Client Issues

Interoperability issues have been identified in environments with both CIFS and Hummingbird PC NFS clients accessing Microsoft® Word or Corel® WordPerfect® files.

Range Locking Normally, if a CIFS client opens a Microsoft Word file, and a Hummingbird (or any PC-NFS) client tries to delete the file, the delete request is refused due to the deny delete lock imposed when the CIFS client opened the file.

The file is also range locked, however, with the offset not congruent with the start or end of the file. Thus, if a portion of the file is outside the range specified by range lock, the file can be written to. Write requests that fall within the range lock are denied. Since there is no method to determine which portions of the file are range locked, users may experience unpredictable results.

Share Authentication Hummingbird users have the option of overriding Share authentication for Celerra (or any other) drives when these drives are mounted on the client. In these cases, CIFS and Hummingbird clients will have concurrent access to the file.

Directory Locking If a CIFS client has a directory open in Windows Explorer and a Hummingbird client subsequently opens and attempts to close a WordPerfect file it has opened in the same directory, the Hummingbird client attempts to lock the file. Because the file is opened by Windows Explorer, a lock already exists, and the Hummingbird lock request is denied. The Hummingbird client continuously issues lock requests to the server until the CIFS client closes the directory and releases its lock.

Providing PC User Access 6-13

6

6-14


Unexporting Paths/Shares When performing an unexport of a path or share, you can define the export to be either permanent or temporary. By default, all NFS unexports are temporary, meaning that the next time the system is rebooted, the entry is automatically re-exported. If the unexport is permanent, the entry is deleted from the export table.

By default, all CIFS unexports are permanent.

Command To unexport a path temporarily, type:

$ server_export movername -unexport pathname


Command To unexport a path permanently, type:

$ server_export movername -unexport -perm pathname


Unexport Limitations When you are using NFS, you may unexport a directory or file system only after it is unmounted from a Data Mover. If you export a directory or file system from a Data Mover before it has been unmounted, these error messages appear the next time you try to access the file system:

mount_lookup: No match in the export list

/mnt Stale NFS file handle

Unexport Advisory The server_export option -all -unexport -perm allows you to permanently unexport all file systems in the export table. This option should be used with caution. If you execute this option, you need to subsequently rebuild the export table by re-exporting each path on each Data Mover in order to restore user connectivity to all mounted file systems. server_export -all -unexport unexports every entry within the table, but on a temporary basis.



Where to Go From HereTo complete the basic setup of your Celerra, proceed to Chapter 7, Configuring Standbys, for information about configuring a Data Mover as a standby (backup) for a primary Data Mover.

Where to Go From Here 6-15

6

6-16



7Invisible Body Tag

This chapter discusses the failover process and configuring standby Data Movers.

◆ Data Mover Availability....................................................................7-2◆ Failover Detection ..............................................................................7-4◆ Configuring Standby Data Movers .................................................7-8◆ Activating a Standby .......................................................................7-10◆ Control Station Failover ..................................................................7-15

Configuring Standbys

Configuring Standbys 7-1

7

7-2


Data Mover AvailabilityCreating a standby Data Mover assures continuous availability to file systems. When a primary Data Mover fails over to a standby, the identity and functionality for the failed Data Mover is assumed by the standby.

To act as a standby server, a Data Mover must first be configured as a standby for one or more primary Data Movers. For example, you could have one standby Data Mover acting as a standby for three other Data Movers. A primary Data Mover can be associated with only one standby Data Mover.

If one of the primary Data Movers fails over, the standby Data Mover assumes the IP and MAC address as well as the functions of the failed Data Mover, so the former standby is no longer available in a standby capacity.

The standby Data Mover configuration must have the same type of NIC cards and the same connections as the Data Mover with which it is associated. Any FTP, archive, or NDMP sessions that were active when the failure occurred are automatically disconnected. You must manually restart those sessions.


7Configuring Standbys

Figure 7-1 shows a standby relationship.

Figure 7-1 Standby Relationship

ClientClient Client

FileSystem

FileSystem

Data Mover"Primary"

Data Mover"Standby"

Network

CFS_000045

Data Mover Availability 7-3

7

7-4


Failover DetectionTo detect a Data Mover failover, the Control Station monitors the periodic heartbeat signals that all Data Movers send, using the redundant internal networks that connect the Control Station to each Data Mover. If the Control Station detects a failure, it first attempts to reset and/or cycle power to the Data Mover. If the problem persists, and if CallHome is configured, the Control Station calls EMC with a notification of the event and diagnostic information.

By default, a Data Mover does not call home if it loses connectivity to the network, although it can be configured to do so.

Table 7-1 summarizes the conditions that do and do not trigger Data Mover failover.

Table 7-1 Data Mover Failover

A Data Mover reboots itself when it detects a software problem (that is, a software panic or an exception). Typically, the reboot takes less than 100 seconds, and applications and NFS clients do not see any interruption, except for a possible server not responding message during the reboot.

Failover Condition

Data Mover failover occurs if any of these conditions exists

• Failure (operation below the configured threshold) of both internal Ethernets. This is the same as the lack of a ”heartbeat“ (Data Mover timeout).

• Power failure within the Data Mover.• Software panic.• Exception on the Data Mover.• Data Mover hang.• Memory error on the Data Mover.

Data Mover failover does not occur under these conditions

• Removing a Data Mover from its slot.• Disconnecting SCSI cables from a

Data Mover.• Manually rebooting a Data Mover.



How Data Mover Failover Works

When any of the above conditions occur, you can transfer functionality from the primary Data Mover to the standby Data Mover without disrupting file system availability. The standby Data Mover substitutes for the faulted Data Mover by assuming the faulted Data Mover’s:

◆ Network identity — the IP and MAC addresses of all its NICs

◆ Storage identity — the file systems that the faulted Data Mover controlled

◆ Service identity — the exported file systems that the faulted Data Mover controlled

The standby Data Mover assumes file system services to users within a few seconds of the failure, transparently, and without requiring users to unmount and remount the file system.

Failover Example Figure 7-2 shows how failover works. In this example, server_7 is the Primary and server_2 is the Standby. The sequence is as follows:

1. The faulted Primary is renamed server_7.faulted.server_2.

2. The standby Data Mover acquires the name server_7 from the Primary Data Mover.

3. When the Primary Data Mover is restored, server_7 is renamed, and again represents the Primary Data Mover while server_2 represents the Standby.

Failover Detection 7-5

7

7-6


Figure 7-2 Failover Example

type=nas

state=online,active

name=server_7

standby=server_2,

policy=manual

Primary Data Mover Standby Data Mover

type=standby

state=online,ready

name=server_2

standbyfor=server_7

type=standby

state=online,ready

name=server_2

standbyfor=server_7

type=nas

state=online,active

name=server_7

standby=server_7.faulted.

server_2,policy=manual

type=nas

state=online,active

name=server_7

standby=server_2,

policy=manual

Restore

Failover

Normal

type=standby

state=out_of_service

name=server_7.faulted.

server_2

standbyfor=server_7

Command:server_standby server_7 -create mover=server_2 -policy manual

Command:server_standby server_7 -activate mover

Command:server_standby server_7 -restore mover

<once a failure corrected>

<should a failure occur>

CFS_000046



CAUTION!If a Data Mover fails, Celerra File Server clients retain normal NFS functions, but any ongoing FTP, archive, or NDMP sessions are lost and not restarted. Connections between CIFS clients and the Data Mover are lost, but the redirector on the client will reconnect with the Data Mover after the failover. However, all data cached by the clients prior to failover are lost and data loss can occur. Applications on the client using the shares may not recover.

Failover Detection 7-7

7

7-8


Configuring Standby Data MoversYou should link your primary Data Mover to a standby Data Mover when initially configuring the system.

When and How to Link

You must first identify and designate the standby Data Mover. Once this is done, link the standby with a primary Data Mover and define the policy of the failover.

The failover policy defines the functionality transfer between the primary and the standby. A standby Data Mover can take over functionality automatically or with manual intervention.

Failover Policies A failover policy is a predetermined action that the Control Station invokes when it detects a Data Mover failover condition. The failover policy type you specify determines the action that occurs in the event of a Data Mover failover. The Celerra File Server offers the policies listed in Table 7-2.

Standby Data Mover Rules and Restrictions

To determine whether a Data Mover can be designated as a standby, you must:

◆ Verify that the standby Data Mover is operational.

◆ Ensure that no file systems are mounted by checking the list of mounted file systems.

◆ Have network connectivity of the standby equivalent to that of all the intended primaries.

Table 7-2 Failover Standby Policy Types

Policy Action

Auto The standby Data Mover immediately takes over the function of its primary.

Retry The Celerra File Server first tries to recover the primary Data Mover. If the recovery fails, the Celerra File Server automatically activates the standby.

Manual The Celerra File Server issues a shutdown for the primary Data Mover. The system takes no other action. The standby must be activated manually.



◆ Ensure that the standby contains a superset of the network interface cards installed into each primary Data Mover.

◆ Ensure that the standby has no configured file systems.

Once you ensure that the above criteria are met for your standby, you can link this standby to all of the primary Data Movers in the same cabinet.

It is also possible to have multiple standby Data Movers in a Celerra File Server, with each standby Data Mover acting as a standby for group of primary Data Mover(s).

When you set a Data Mover to standby, it is not configured with an IP address. In the case of a standby activation, the standby assumes the primary’s IP address.

The standby, when activated, functions for only one faulty primary Data Mover at a time.

Restrictions When configuring standby Data Movers, you cannot:

◆ Create a standby Data Mover for a standby.

◆ Have more than one standby Data Mover per primary Data Mover.

Create Standby This section describes how to create a standby Data Mover.

Command To create a standby relationship with policy set to manual, type:

$ server_standby movername -create mover=source_movername -policy manual

If the standby Data Mover is a standby for more than one primary Data Mover, you must repeat this procedure for each primary.

Sample Output server_3 : server_3 is rebooting as type standby

If the policy type is set to Auto or Retry, no further action is required if the primary Data Mover fails. However, if the policy is set to Manual, refer to Activating a Standby on page 7-10 for the necessary procedure.

Configuring Standby Data Movers 7-9

7

7-10


Activating a StandbyYou manually activate a standby Data Mover when the policy type is set to manual. A manual policy type means that the standby does not activate unless you initiate the action.

You must have previously designated a Data Mover that is not being used to be the standby prior to activating the standby Data Mover. Once you have designated a Data Mover as a standby and associated it with one or more functioning Data Movers, you activate the standby to take over for the primary Data Mover, should a failure occur.

Before performing a manual activation, you must thoroughly investigate the problem first by:

◆ Checking error logs

◆ Ruling out other (external) factors such as network, router, client, or storage system problems



Command To activate the standby Data Mover, type:

This process can take from 40 seconds up to 2 minutes to complete. A message appears indicating completion.

Sample Output server_4 : replace in progress ...donecommit in progress (not interruptable)...doneserver_4 : renamed as server_4.faulted.server_5server_5 : renamed as server_4

The standby Data Mover is activated and functions as the primary Data Mover.

When a failover occurs, the primary Data Mover goes into a faulted state and assumes the movername primary.faulted.standby. The standby Data Mover acquires the movername primary from the primary Data Mover.

The Celerra File Server clients retain normal NFS functionality, but any ongoing FTP, archive, or NDMP sessions are lost and are not restarted.


server_x: Error: server_x unable to connect to host

The system waits a period of two minutes after creating your standby. If you try to activate your standby before this waiting period is over, you may be unable to connect to the host.


server_4 : replace in progress ...failedError: replace_net: elv0 : No such device or address

server_standby movername -activate mover

Name of failed primary Data Mover. "mover" is typed in thecommand line exactly as it

appears here.The value was defined when

performing the create command.

CFS-000195

Activating a Standby 7-11

7

7-12


The standby you are activating does not contain the necessary network interface card. The standby Data Mover must contain the same external network interface cards as the primary Data Mover.

Restoring a Primary Data Mover

Type nas_server -info movername to view the status and type of a Data Mover. From the output, you are able to determine whether a Data Mover is of type standby or primary and the policy type. Once the failure has been corrected, restore the primary Data Mover as described below.

The failure of the primary Data Mover is reported to EMC by the CallHome feature of the Control Station. When the problem has been corrected or the Data Mover has been replaced, the Data Mover first must be rebooted before you can restore it to its original state. Use the server_standby command to reboot the faulted Data Mover.

IMPORTANT: Always use the server_standby command to reboot a Data Mover. If you manually reboot the faulted Data Mover, it broadcasts the same MAC address as the standby Data Mover that took over when the failure occurred. This can cause system conflicts and loss of network connections.

When you execute a restore, you still use the original name of the primary Data Mover (from our example, this would be server_7), not the faulted name it is assigned when out of service. The following procedure describes how to restore a primary Data Mover.

Command To restore the primary Data Mover to resume functionality, type:

Sample Output server_4 : server_4.faulted.server_5 : reboot in progress0.0.3replace in progress ...donecommit in progress (not interruptable)...doneserver_5 : renamed as server_5

server_standby movername -restore mover

Name of primary Data Mover.Do not use the faulted name, use the

original name assigned to the primary.

"mover" is typed in thecommand line exactly as it

appears here.The value was defined when

performing the create command.

CFS-000194



server_4.faulted.server_5 : renamed as server_4The primary Data Mover is now restored to a functioning status, the standby is restored to standby status, and the names revert back to their original settings.

Other Options To delete the relationship created between the primary and the standby Data Mover, type:

$ server_standby movername -delete mover

The movername directly following the command is the primary movername.

Changing Data MoverType

To change a Data Mover from standby back to a nas Data Mover, type:

$ server_setup movername -type nas

The movername directly following this command is the standby movername since you are changing the type configuration of the standby back to nas.

When you change a standby back to a regular Data Mover, the original IP address is no longer associated with the Data Mover; therefore you must assign a new IP address.

Verifying Standby Data Movers After an Upgrade

If an EMC Customer Service Engineer upgrades a Data Mover to a new hardware model, or replaces a Data Mover with a unit of the same model, you should verify the standby relationship between the new Data Mover and any standby Data Mover(s) in the Celerra using the following command:

Command $ server_standby movername -verify

This command has two possible usages:

If movername is configured as: The command:

A standby Data Mover Verifies that movername has the appropriate hardware configuration to continue to serve as a standby for those Data Movers.

A regular Data Mover configured with a standby

Verifies that the standby has the appropriate hardware configuration to continue to be a standby for movername.

Activating a Standby 7-13

7

7-14


CIFS Access After Failover

In most cases, during a system reboot, CIFS clients are able to open a new session and re-initialize their contexts. However, since CIFS is not stateless, this can fail to occur in some cases, as with any Windows server. For example, a lock conflict can occur if clients reconnect out of order. Therefore, any application accessing file systems on an activated standby Data Mover may get an error message.

Periodic Tasks Periodically, (about once a month) test standby Data Movers by doing a failover, then failing them back. Standby Data Movers are not tested otherwise.

For More Information

Refer to the server_standby man page or the server_standby entry in the Command Reference Manual.



Control Station FailoverCelerra File Server software provides seamless file access to users even when the Control Station is rebooted, upgraded, or unavailable.

Control Station Independence

The Control Station software, which is used to configure and manage the Celerra File Server, operates independently of the file access operations and services provided by Data Movers. If a Control Station fails:

◆ Individual Data Movers continue to respond to user requests

◆ User access to data is uninterrupted

Control Station failure means only that you are temporarily unable to install new software or to modify your Celerra File Server configuration. You can resume these operations as soon as the Control Station becomes available.

Dual Control Station Configuration

The Celerra File Server supports configurations with dual, redundant Control Stations. This configuration lets you configure or modify your Celerra File Server even in the event of Control Station failure.

CAUTION!Older Celerra cabinets may not support the use of dual Control Stations. If you have an older cabinet, consult your EMC representative to determine whether you need a hardware upgrade.

If the primary Control Station goes off line for any reason:

◆ The secondary Control Station, if properly configured, automatically takes over all Control Station functions.

◆ The secondary Control Station executes any of the Celerra File Server commands that you enter.

◆ The Celerra File Server uses the CallHome utility to notify EMC Customer Service of the event.

Under normal circumstances, after the primary Control Station has failed over, you continue to use the secondary Control Station as the primary. When the Control Stations are next rebooted, either directly or as a result of a power down and restart cycle, the Control Station in slot_0 is restored as the primary.

Control Station Failover 7-15

7

7-16


Initiating a Control Station FailoverThe Control Station can be failed over manually. From the standby Control Station, you can change the state of the standby to that of the primary. From the primary Control Station, you can change the state of the primary to that of standby and activate the standby to takeover the role of primary.

Important: You must log in to nasadmin and su to root in order to execute this functionality. The command for manual failover must be executed from /nas/bin.

Failover from aStandby Control

Station

This activity should be done at the Celerra cabinet console.

To change the state of the standby Control Station to that of the primary, from the /nasmcd/sbin directory type:

Command # cs_standby -takeoverTaking over as Primary Control Stationdone

This command can only be performed on the standby Control Station. If you attempt to use this command from the primary Control Station, you will get an error message.

Failover from aPrimary Control

Station

To change the state of the primary Control Station to the standby Control Station, from the /nasmcd/sbin directory type:

Command # cs_standby -failoverThe system will reboot, do you wish to continue [yes or no]: yFailing over from Primary Control Stationdone



Where to Go From HereYou have now completed the basic setup tasks for your Celerra File Server. The remaining chapters and appendices of this guide provide more information on customizing and managing the operation of your Celerra File Server.

Where to Go From Here 7-17

7

7-18



8

This chapter describes the following tasks:

◆ Creating an Automount Map...........................................................8-2◆ Displaying Mounted File Systems...................................................8-4◆ Unmounting a File System ...............................................................8-5◆ Checking Capacity .............................................................................8-6◆ Extending a File System ....................................................................8-7◆ Renaming a File System ....................................................................8-9◆ Deleting a File System ..................................................................... 8-11◆ Creating 32-bit GIDs ........................................................................8-12

Managing FileSystems

Managing File Systems 8-1

8

8-2

Managing File Systems

Creating an Automount MapYou can create and save an automountmap file that contains every exported path within your system. The automount daemon can reference this file and automatically mount each file system in the automountmap file.

Refer to the Linux automount (8) man page (on the Control Station) for more information about the automount daemon.

After you have created and saved your automountmap file, you must then place it in the appropriate directory for your automount daemon to access the file.

To edit an automountmap file, use a text editor.

Command To create an automountmap file and print it to the screen, type:

$ nas_automountmap -creatempt1 -rw,intr,nosuid 100.192.168.40,193.1.6.10:/mpt1

Creating an automountmap file and printing it to the screen does not save the automountmap file.

Command To save the automountmap file, type:

$ nas_automountmap -create -out outfile

There is no immediate output after executing this command. To view what is in your automount file, type:

$ more outfilebin -rw,intr,nosuid lpce155:/bin

Once you have saved your automount file, use a text editor to make modifications to the file.

Command If you have created and exported additional file systems and would like to create a new automountmap file, type:

$ nas_automountmap -create -out outfile$ more outfile

a 100.1.1.1:/aa_100.1.1.2 100.1.1.2:/a


8Managing File Systems

Command To merge your new automount file with a previous automount file, type:

$ nas_automountmap -create -in infile -out -outfile

If you merge two automount files and the same line appears in both, a conflicting list is generated.

You can view conflicting lists within your automountmap file on the screen or print the file to an output file.

Command To view a conflicting list, type:

$ nas_automountmap -list_conflict infile

Sample Output Conflicting lists:a 100.1.1.1:/aa 100.1.1.2 100.1.2:/a

Command To view a conflicting list and save it to another file, type:

$ nas_automountmap -list_conflict -in infile -out outfile

$ more outfilea 100.1.1.1:/aa_100.1.1.2 100.1.1.2:/a

Creating an Automount Map 8-3

8

8-4


Displaying Mounted File SystemsYou can display mounted file systems to view a listing of the file systems currently mounted and the options assigned to the mount.

Command To display mounted file systems, type:

$ server_mount movername

Sample Output server_3:fs2 on /fs2 uxfs,perm,rwfs1 on /fs1 uxfs,perm,rwroot_fs_3 on / uxfs,perm,rw

server_4:file1 on /mpt1 uxfs,perm,rwroot_fs_4 on / uxfs,perm,rw



Unmounting a File SystemYou can perform either a temporary or permanent unmount of a mount point. When an unmount is temporary, upon a system reboot, the file system or mount point is automatically re-mounted.

A permanent unmount removes the mount entry from the mount table. A file system or mount point must be permanently unmounted (deleted from the mount table) before it can be deleted.

Command To unmount a file system, type:

$ server_umount movername fs_name

Command To unmount a mount point, type:

$ server_umount movername pathname


The default unmount mode is temporary. If you keep this selection, the file system is mounted again when the system reboots. To permanently remove an entry from the mount table, the unmount mode selection must be permanent.

Unmount All To permanently unmount all of the file systems in the mount table, type:

$ server_umount movername -perm -all

The default unmount mode is temporary.

Unmounting a File System 8-5

8

8-6


Checking CapacityTo view file system capacity or Data Mover free space, perform one of the following procedures.

Checking File System Capacity

If file system performance slows, your file system may be reaching capacity. If this is the case, you can extend a file system by performing Displaying Mounted File Systems on page 8-4.

Command Once you have identified a file system, to check capacity, type:

$ nas_fs -size fs_name

Sample Output total = 8654 avail = 8521 used = 133 ( 1% ) (sizes in MB)

Checking Data Mover Free Space

You can view the amount of disk space occupied by all mounted file systems on selected Data Mover(s).

Command To report all free and used inodes, type:

$ server_df movername -inode

Sample Output server_3 : Filesystem inodes used avail capacityMounted onfs2 1070590 2 1070588 0% /fs2fs1 1070590 2 1070588 0% /fs1



Extending a File SystemIf you find that your file system has used up its existing space on a meta volume, you can extend the file system by adding more volume space to the original meta volume. When you extend a file system, the underlying meta volume is also extended, thereby extending the total size of the meta volume.

You can extend a file system with any unused meta, disk, slice, or stripe volume. The volume added does not have to be another meta volume because once the extending volume is added to the existing meta volume, it becomes part of the meta volume. Once you have extended the file system, the volume that the file system now occupies equals the sum of the volumes combined.

To view a list of available volumes, type:

$ nas_volume -list

Preparation Before extending a file system, you must:

◆ Fail over the primary Data Mover to its standby.

◆ Reboot the primary Data Mover.

◆ Fail back to the primary Data Mover and perform the extension.

See Chapter 7, Configuring Standbys for more information about configuring standby Data Movers.

Procedure The procedure below assumes that the primary Data Mover is server_4 and the standby is server_5.

To extend a file system use the following procedure.

1. Verify that server_5 has been designated as a standby Data Mover and check its status.

$ nas_server -i -a$ nas_server -i

2. Failover the primary Data Mover, server_4, to its standby, server_5.

$ server_standby server_4 -a mover

The standby must have the same hardware configuration as the primary file system.

Extending a File System 8-7

8

8-8


3. Verify that the failover occurred successfully.

$ nas_server -l$ /nas/sbin/getreason

4. Once you have verified that the failover was successful, reboot server_4 and verify its status.

$ server_cpu server_4.faulted.server_5 -reboot -m now$ /nas/sbin/getreason

5. Restore server_4 as the primary Data Mover.

$ server_standby server_4 -r mover

6. Verify the size of the file system before extending it. Record this information. You will use it as a comparison figure after extending the file system.

$ nas_fs -size fs_name$ server_df server_4

Note: The result from each of the above commands should be the same value.

7. Extend the file system using the following command:

$ nas_fs -x fs_name volume_name

where fs_name is the name of the file system and volume_name is the volume onto which the file system is being extended.

8. Verify the size of the file system after extending it. Compare this value to the value you recorded in Step 6 above, make sure that the volume amount has increased.

If you delete an extended file system, the extended volume remains in use until the original meta volume is deleted.



Renaming a File SystemFile systems are named when they are created either with the assigned name or a default. You can later go back and change the name of the file system.

Command To rename a file system, type:

$ nas_fs -rename old_name new_name

Sample Output id = 17name = file1acl = 0in_use = truetype = uxfsvolume = meta1rw_servers= server_4ro_servers= symm_devs = 0A4,0A5,0A6,05E,05Ddisks = d74,d75,d76,d4,d3

disk = d74 symm_dev=11-0A4 addr=c0t5l8-06-1 server=server_4disk = d75 symm_dev=11-0A5 addr=c0t5l9-06-1 server=server_4disk = d76 symm_dev=11-0A6 addr=c0t5l10-06-1 server=server_4disk = d4 symm_dev=11-05E addr=c0t1l2-06-1 server=server_4disk = d3 symm_dev=11-05D addr=c0t1l1-06-1 server=server_4

Where: Means:

id The ID of the file system (assigned automatically).

name The name assigned to the file system.

acl The access control value for the file system.

in_use Whether the file system is registered into the mount table of a Data Mover.

type The type of file system.

volume The volume on which the file system resides.

rw_servers The servers with read-write access to the file system.

Renaming a File System 8-9

8

8-10


ro_servers The servers with read-only access to the file system.

symm_devs The storage system devices associated with the file system.

disks The disks on which the meta volume resides.

Where: Means:



Deleting a File SystemBefore you delete a file system, ensure that the file system is not in use or mounted by a Data Mover. If your file system is still mounted on a Data Mover, first perform Unmounting a File System on page 8-5.

Command To delete an unmounted file system, type:

$ nas_fs -delete fs_name

If you are deleting an extended file system, the extended volume remains in use until the original meta volume is deleted.

Sample Output id = 17name = file1acl = 0in_use = truetype = uxfsvolume = meta1rw_servers= server_4ro_servers= symm_devs = 0A4,0A5,0A6,05E,05Ddisks = d74,d75,d76,d4,d3

disk = d74 symm_dev=11-0A4 addr=c0t5l8-06-1 server=server_4disk = d75 symm_dev=11-0A5 addr=c0t5l9-06-1 server=server_4disk = d76 symm_dev=11-0A6 addr=c0t5l10-06-1 server=server_4disk = d4 symm_dev=11-05E addr=c0t1l2-06-1 server=server_4disk = d3 symm_dev=11-05D addr=c0t1l1-06-1 server=server_4

See Renaming a File System on page 8-9, for a description of the command outputs.

Deleting a File System 8-11

8

8-12


Creating 32-bit GIDsThis version of the Celerra File Server software allows 32-bit GID values for NFS file systems only. This feature allows you to create file systems with 32-bit GIDs on a Data Mover.

The 32-bit GID (limited by Celerra to a maximum value of 2 billion) feature is set for file systems by a parameter on the Data Mover(s).

The parameter for managing GIDs is:

param ufs gid32=0 | 1

This parameter is used when a you create a file system.

Celerra allows pre-existing and new file systems with 16-bit GIDs and new NFS file systems with 32-bit GIDs to be mounted on the same Data Mover.

Table 8-1 Parameters for Managing GIDs

Where:

0 Disables the 32-bit GID feature for the Data Mover. Any file system created on the Data Mover with this setting supports only 16-bit GIDs.

1 Enables the 32-bit GID feature for the Data Mover. Any file system created on the Data Mover with this setting supports 32-bit GIDs with a maximum value of 2 billion.



Restrictions for the 32-bit GID

With 32-bit GID support, the following restrictions apply:

◆ Maintains a maximum of 64K GIDs per file system. The 64K GID limit applies to the first 64K and should be considered when planning GID usage for your file system. The value of 32-bit GID is capped at 2 billion for Celerra for future support of CIFS.

The 64K limit is quantity. For any file system, you can have any value between 0 and 2 billion, but you can only have 64K different GIDs per file system.

◆ The 32-bit GID can be used only with NFS file systems.

◆ For CIFS file system, you must set param ufs gid32=0.

◆ Setting this parameter to 0 allows you to create file systems with 16-bit GIDs. It does not, however, disable 32-bit GIDs on those file systems created with the parameter set to 1.

◆ You cannot convert any existing file systems to use a 32-bit GID. The 32-bit GID can be used only with new NFS file systems.

◆ You cannot use the Celerra Linux Control Station as an NFS client if 32-bit GIDs are used. The Linux Control Station supports only 64K GID value. If Linux accesses a file system with GID32=1, the number beyond 64K is truncated.

◆ You must disable quotas on the Data Mover before you create the file system that uses the 32-bit GID.

◆ You cannot set the 32-bit GID with the following server_archive formats:

• emctar up to 31-bit• ustar up to 21-bit• cpio up to 15-bit• bcpio up to 16-bit• sv4cpio up to 21-bit• sv4crc up to 21-bit• tar up to 18-bit

◆ Some backup applications have restrictions. Ensure the application handles 31-bit UID/GID. (For example, Veritas NetBackup NDMP handles 32-bit UID/GID, but Veritas NetBackup network backup via NFS supports only 24-bit UID/GID.)

◆ Sun Solaris supports 2 billion GID as a maximum value.

Creating 32-bit GIDs 8-13

8

8-14


Setting the 32-bit System Parameter

To set the system parameter for 32-bit GID:

1. Log on to the Control Station.

2. Open /nas/server/server_x/param with a text editor.

Where x = the number of the Data Mover where the file system(s) using the 32-bit GID reside.

3. Type or change the parameter to read: param ufs gid32=1.

4. Save the file.

5. Reboot the Data Mover.

Creating a File System with the 32-bit GID Parameter

To ensure that you create a NFS file system that has the 32-bit GID attribute:

1. Log on to the Control Station.

2. Open /nas/server/server_x/param with a text editor.

Where x = the number of the Data Mover that you are about to use to create the file system with the 32-bit attribute set.

3. Ensure that the param file has the following entry:

param ufs gid32=1

4. Use the nas_fs command with the option mover=mover_name option set to the Data Mover (in this case, Data Mover 2) with 32-bit GID enabled to create the file system ufs1. For example, type:

$ nas_fs -name ufs1 -create ufs1 -option mover=server_2

Designating the Data Mover in this way allows you to direct the creation of the file system to a Data Mover with the 32-bit GID attribute enabled.


9

This chapter contains system and network administrative tasks that you may be required to perform, such as:

◆ Managing Data Movers.....................................................................9-2◆ Managing Volumes ............................................................................9-5◆ Controlling Access to System Objects .............................................9-9◆ Managing System Parameters........................................................9-15

Managing Your System

Managing Your System 9-1

9

9-2


Managing Data MoversThis section contains the following management tasks for the Data Movers:

◆ Adding Internal Events◆ Discovering and saving SCSI devices◆ Rebooting Data Movers◆ Halting a Data Mover

Adding Internal Events

An internal event is a change in the operating status of a Data Mover or Control Station. All events are logged in the event log file. The system event log file, nas_eventlog.cfg, is located in the /nas/sys directory.

An internal event contains:

◆ Name of the Celerra facility that issued the event

◆ “High water mark”; that is, the maximum severity of the event (ranging from 1, least severe, to 7, most severe)

◆ Event ID number

◆ Short description of the event that occurred

◆ System-defined action to take when the event occurs

In order to add an internal event you must first create an event configuration file, then load this file to supplement (but not replace) the system events log file, nas_eventlog.cfg.

CAUTION!Do not change nas_eventlog.cfg.

When you create an event configuration file, make sure it does not have the same name as the nas_eventlog.cfg. Also, save the configuration file in the /nas/site directory. This ensures that any site specific additions are maintained when the system is upgraded.

An event configuration file has one line with the keyword facilitypolicy to denote the facility ID and severity level, followed by one or more lines with the keyword disposition denoting the range of event ID’s and the specific action to take when an event is issued with that corresponding event ID range. For example:


9Managing Your System

facilitypolicy facility id, severity id disposition range=(From_eventid-To_eventid), action to take

Procedure To add an internal event:

1. Log onto the Control Station as nasadmin.

2. Create an event configuration file using a standard text editor. Save the file as filename.cfg in the /nas/site directory.

3. From the /nas/bin directory, load the configuration file.

$ nas_event -L /nas/site/filename.cfgEventLog : will load /nas/site/filename.cfg... done

4. From the /nas/site directory, verify that the file has been loaded.

$ more nas_eventlog.cfg/nas/sys/nas_eventlog.cfg/nas/site/filename.cfg

Discovering and Saving SCSI Devices

A listing of all devices is maintained in a database contained within the Control Station. You can periodically probe the storage system to discover all of the present devices and save them back to the device table.

CAUTION!Discovering and/or saving SCSI devices is a time consuming action, and is therefore best performed when the least resources are required. Discovering and Saving SCSI devices may cause a temporary disruption of Celerra File Server service.

The FC4700-2 storage system supports only Fibre Channel connectivity.

Command To discover all devices for the specified Data Mover, type:

$ server_devconfig movername -probe -scsi -all

Sample Outputserver_3 : SCSI devices :chain= 0, scsi-0symm_id= 0 symm_type= 0tid/lun= 0/0 type= disk sz= 2076 val= 1 info=526411005221tid/lun= 1/0 type= disk sz= 8718 val= 2 info=52641105C221tid/lun= 1/1 type= disk sz= 8718 val= 3 info=52641105D221

Managing Data Movers 9-3

9

9-4


tid/lun= 1/2 type= disk sz= 8718 val= 4 info=52641105E221tid/lun= 1/3 type= disk sz= 8718 val= 5 info= 52641105F221tdd/lun= 1/4 type= disk sz= 8718 val= 6 info= 526411060221tid/lun= 1/5 type= disk sz= 8718 val= 7 info= 526411061221 tid/lun= 1/6 type= disk sz= 8718 val= 8 info= 526411062221 tid/lun= 1/7 type= disk sz= 8718 val= 9 info= 526411063221 tid/lun= 1/8 type= disk sz= 8718 val= 10 info= 526411064221 tid/lun= 1/9 type= disk sz= 8718 val= 11 info= 526411065221

Rebooting Data Movers

To immediately reboot and monitor a Data Mover, type:

$ server_cpu movername -r -m now

Sample Output server_4 : reboot in progress ..... 3.4.4.done

You can verify when the system comes back up with the server_uptime command.

Halting a Data Mover

To immediately halt a Data Mover, type:

$ server_cpu movername -h now



Managing VolumesOnce you have configured the volumes and have begun using them to store file systems, you can periodically check their capacity and the remaining amount of unused space and extend them, if needed. You can also rename and delete volumes.

Procedures for managing volumes are:

◆ Checking volume capacity◆ Extending meta volumes◆ Renaming volumes◆ Deleting volumes

Checking Volume Capacity

Once you have configured the volumes and have begun using them to store file systems, you can periodically check their capacity and the remaining amount of unused space.

Command To obtain volume size, type:

$ nas_volume -size volume_name

Sample Output total = 25962 avail = 0 used = 25962 (100%) (sized in MB)

With a meta volume, if the full capacity of the volume is used (100%), you can extend the volume by adding another volume to the configuration.

Extending Meta Volumes

You can increase the total size of a meta volume by adding another volume to the configuration. The volume added to the meta volume can be a stripe volume, a slice volume, a disk volume, or another meta volume as long it is not in use at the time of concatenation.

Once the meta volume has been extended, the new size of the meta volume is equal to the sum of the volumes contained within the new configuration.

Important: You cannot extend a meta volume that is being used by a file system.

Managing Volumes 9-5

9

9-6


Command To extend a meta volume, type:

$ nas_volume -xtend volume_name volume_name

Sample Output id = 312name = meta1acl = 0in_use =falsetype = metavolume_set = d5,d6,d7, d8disks = d5,d6,d7, d8

The meta volume is extended to include the volume or volumes specified. The size of the meta volume increases by the sum of the volume(s) added.


Error: volume : item is currently in used by filesys: file

A file system is mounted on the meta volume you are trying to extend. Since the added volume that is added is now combined into a meta volume configuration, even if you remove the file system that resides on the meta volume, the added volume remains in use until the meta volume is deleted.

If you want to extend a file system while it is in use, you must use the nas_fs -xtend command. For details on this procedure, see Extending a File System on page 8-7.

Renaming Volumes Volumes are given default names when configured unless you specify a name when you created the volume. After volume configuration is complete, you can rename the volumes.

Command To rename a meta volume or stripe volume, type:

$ nas_volume -rename old_name new_name

Command To rename a slice volume, type:

$ nas_slice -rename old_name new_name



Cloning Volumes You can clone a stripe, slice, or meta volume using the nas_volume -Clone command. This enables you to make an exact copy of a volume.

Command To clone a volume, use the following command:

$ nas_volume -Clone volume_name -option disktype svol:dvol

where:

You must be logged in as root to use the -Clone option.

Deleting Volumes Once volumes are no longer used by a file system, you can delete or change your volume configuration. If the status of a volume is In Use, there may still be a file system using the volume.

If a volume was used to extend a meta volume, since the volume that is added is now combined into a meta volume configuration, even if you remove the file system that is residing on the meta volume, the added volume remains in use until the meta volume is deleted.

You must remove the file system before deleting the volume. Volumes must not be In Use when you are deleting them.

Command To delete a meta volume or stripe volume, type:

$ nas_volume -delete volume_name

Parameter Value

volume_name Name of the volume being cloned

disktype Volume type:• BCV for business continuance volume

(TimeFinder/FS operations - not available for FC4700-2)

• STD for standard volume• R1STD and R1BCV are for BCV or STD volumes

that have been mirrored

svol:dvol Source and destination volumes, respectively

Managing Volumes 9-7

9

9-8


Command To delete a slice volume, type:

$ nas_slice -delete slice_name

Sample Output id = 312name = meta1acl = 0in_use =falsetype = metavolume_set = d5,d6,d7, d8disks = d5,d6,d7, d8


Error: volume: item is currently in use by filesys=file

A file system is using the meta volume you are attempting to delete.



Controlling Access to System ObjectsYou can provide access control for certain users to system objects by creating an access control level table, then establishing access control lists (ACLs).

This requires the following tasks:

1. Create a Linux user.

2. Create an Access Control Level table which defines privileges for users.

3. Establish ACL lists for the objects to which you want to control access. These objects are:

• File Systems• Data Movers• Volumes

You must log in as root to perform access control tasks. Each task is described in this section.

Task 1: Create a Linux User

Before you can create an ACL entry for a specific user, you must first create a user profile.

With NIS If NIS (Network Information Service) is available, the Celerra File Server attempts to resolve user names and passwords by searching the NIS database.

Without NIS If you do not have NIS, perform the following steps to assign a user account name and password to one or all Data Movers in the Celerra cabinet:

1. Login to the Celerra File Server Control Station as root and type nasadmin for the password.

2. From nas/sbin, type the following to set up a user account name (John in this example):

Example: # server_user server_2 -add -passwd JohnCreating new user John

This command launches a program script. You must supply information when prompted.

Controlling Access to System Objects 9-9

9

9-10


3. The User ID field is the first prompt and input is mandatory. Enter any integer you wish and press enter. For example:

User ID: 11

4. The next prompt is Group ID. This field is also mandatory and can be any integer. For example:

Group ID: 111

5. Input for the next three prompts is optional. Enter appropriate information or just press enter after each prompt.

Comment: This is John’s account.Home directory:/home/JohnShell:/bash

6. The last two prompts set a password for the new user and are also mandatory. Enter the string you wish the new user to use for access to the Data Mover.

Changing password for user JohnNew passwd:xxxxRetype new passwd:xxxxserver_2 : done

The Celerra File Server accesses a Data Mover by its internal name (server_n), which is server_2 in this example.

7. Repeat steps 1 through 6 for each Data Mover.

To assign the same user account and password to ALL Data Movers in the Celerra cabinet, type:

Command Example: # server_user ALL -add -passed Auser

The user name Auser is an example. Follow steps 3 through 6 after executing this command example.

Task 2: Creating an Access Control Level Table

Using the nas_acl command, you can create an access control level table composed of entries that define the privileges to be allowed for specified users and groups.

Important: The user must have been previously created in Linux, if not, refer to Task 1: Create a Linux User on page 9-9.



Command To create an entry in the access control level table, type:

$ nas_acl -name name -create [ -user | -group ] numerical_id level=acl_level

The name is the name associated to the entry. After specifying either -user or -group, the numerical_id is the applicable UID or GID. The acl_level represents the level assigned to the entry. Numbers 2 through 4 are available ACL level inputs, with 2 being the most privileged, and 4 the least.

Levels 2, 3, and 4, which are established by default are:

2 -- admin - is the most privileged.3 -- operator - includes privileges for the observer level.4 -- observer - includes privileges for levels that may exist up to level 4.

Levels 5 through 9 may be created using nas_acl, then used as input.

Once you have created an ACL table, you can assign ACL lists for file systems, Data Movers and volumes, using the -acl option of the objects’ associated command. Task 3: Establishing Access Control Lists for Objects on page 9-11 contains details on creating ACLs on Data Movers, file systems, or volumes.

Task 3: Establishing Access Control Lists for Objects

By setting an ACL for an object, you define the privileges for each user trying to access the object. When a user or group tries to access a particular object, the access control level table as established by nas_acl is verified against the access control list established by the relevant command for the object.

Commands used to establish ACLs are listed in the following table.

Table 9-1 Creating ACLs

To create ACLs on Use this command Example

File systems nas_fs -acl $ nas_fs -acl 432 fs_1

Data Movers nas_server -acl $ nas_server -acl 432 server_3

Volumes nas_volume -acl $ nas_volume -acl 432 vol65


9

9-12


Access control values 2, 3, and 4 are already established by default and are as follows:

2 -- admin - is the top in hierarchy, and is the most privileged.3 -- operator - includes privileges for the observer level and any other levels that may exist up to level 9.4 -- observer - includes privileges for levels that may exist up to level 9.

Levels 5 through 9 may be created using nas_acl, then used as input.

TheRead-Write-Delete

Columns

When a value is assigned to an object, values are entered into one of four specific positions representing the degrees of operations (owner-read-write-delete). A single digit from the inputted acl_value is applied, starting at the delete column. For example:

◆ The digit in the delete column determines the access level required to issue delete commands to the specified objects.

◆ The digit in the write column determines the access level required to issue write commands to the specified objects.

◆ The digit in the read column determines the access level required to issue read commands to the specified objects.

◆ The number(s) that are left over, if any, are applied to the owner column.

The Owner Column Any number(s) that appears in the owner column relates directly to the index number that appears when an entry is created in the ACL table. The index number is relevant when a number is entered into the owner column indicating that the user created by the entry in the ACL table is the owner of the object. For example:

Rules to Remember The following is a list of rules when setting ACLs.

◆ The root user always has universal access; nasadmin, which is usually indicated as the owner (created by default as index entry 1) is treated like any other user.

◆ With no owner is specified, a "0" in the read-write-delete column indicates universal access.

Owner Read4

Write3

Delete2

Owner2

Read0

Write0

Delete0



◆ If an owner is specified, a "0" in the read-write-delete column indicates no access for anyone but owner.

◆ If an owner is specified, a "1" in the read-write-delete column indicates no access for anyone but owner.

How ACLs Work For the purpose of these examples, assume the following ACL table:

$ nas_acl -list

For ACL value:

• Delete is permitted for the admin only.

• Read-write is permitted for the operator and admin.

• Read is permitted for the observer, operator, and admin.

Note: The owner value is blank. If a 4-digit value is not specified, other types of operations (read-write-delete) are determined for the user.

For ACL value:

• No access is permitted for anyone except the owner.

• Owner privileges are allowed for the nasadmin user. The owner is allowed to read-write-delete.

Alternatively, if no owner had been specified, a "0" in the read-write-delete columns would have indicated universal access.

index123456

typeuseruseruseruseruseruser

leveladminoperatoradminobserveroperatoradmin

num_id101102103104105106

namenasadminxyxzxtyyyz

Owner Read4

Write3

Delete2

Owner1

Read0

Write0

Delete0


9

9-14


For ACL value:

• Read is permitted for users with operator privileges (includes admin).

• The owner of the object (index 3 from ACL table) is allowed to read-write-delete.

For ACL value:

• Delete is permitted for admin.

• Write is permitted for observer (includes operator and admin).

• Read is permitted for the user with ACL level of 6 as defined by nas_acl.

• The owner of the object (index 2) is allowed to read-write-delete.

For ACL value:

• Delete is permitted for admin.

• Write is permitted for admin.

• Read is permitted for operator and admin.

Owner3

Read3

Write0

Delete0

Owner2

Read6

Write4

Delete2

Owner Read3

Write2

Delete2



Managing System ParametersSpecific system attributes are set up by default in the Celerra File Server software. You can override some of these attributes for the entire Celerra File Server by creating an entry in the global parameter file, /nas/site/slot_param, which is the default file that resides on the Control Station. You can also override attributes for a specific Data Mover by creating an entry in a server parameter file, /nas/server server_x/param (the default file), which also resides on the Control Station.

System Parameters The /nas/site/slot_param file contains parameters that pertain to the entire system, including all Data Movers. You may want to change parameter values in order to modify the behavior of the Celerra File Server to make it more compatible with your environment.

Each parameter has a default value. You have to add a parameter entry only if you want to override the default. If you modify slot_param, you must reboot all of the Data Movers to cause the changes to take effect. The /nas/site/slot_param file contains parameters that pertain to the entire system, including all Data Movers. You may want to change parameter values in order to modify the behavior of the Celerra File Server to make it more compatible with your environment.

Each parameter has a default value. You need only to add a parameter entry if you want to override the default. If you modify slot_param, you must reboot all of the Data Movers to cause the changes to take effect.

The parameters are read from the file in sequence. If there is more than one entry for the same parameter, the last entry prevails.

Parameter File Format

/nas/site/slot_param and /nas/server/server_x/param are text files. Modify them using a text editor. Parameters are listed in sequence in the file and have the following format:

$ param module parameter=valueparam

Important: After modifying the /nas/site/slot_param file, you must reboot all of the Data Movers.

Managing System Parameters 9-15

9

9-16


Table 9-2 lists system parameters that are supported:

Table 9-2 System Parameters

Module Parameter Example or Values Comments/Description

ana rxburst 1, 2, 4, 8, 16, 32, 64, 128, 256, 512,1024(256=default)

Sets the maximum number of received packets to be processed and sent to upper streams modules in each invocation of the driver’s real-time routine. If this number is reached and more received packets require processing, the real-time routine schedules another invocation of itself to process the packets and relinquishes the CPU.Setting this value higher increases the number of packets processed per interrupt.Setting this value lower increases the number of interrupts required to process a given number of packets.

cifs useUnixGid 0 (default), 1 Sets the GID mapping for files created on an Windows NT client.0 assigns the GID of the Primary Domain group to which the user belongs.1 assigns the Windows NT user’s GID (as found in the GID field of the.etc/passwd file or NIS database entry).

cifs ntWildcardMode 0, 1 (default) Sets the question mark (?) wildcard matching format for files on the Data Mover.0 sets Windows 95/98 matching (strict matching).1 sets Windows NT matching (loose matching).

cifs simulateNTFS 0, 1 (default) Sets the file system type identifier that is returned to a CIFS client.0 sets the identifier to UxFS (native Celerra File Server file system).1 sets the identifier to NTFS (Windows NT File System).

cifs maxVCThreads # of threads Sets the maximum number of threads for multiple Data Movers; this is used with virus checking.

cifs tcpkeepalive 0xff01030a default Sets the TCP timeout for CIFS.Use this format 0xFFxxyyzz:xx = first timeout in minutesyy = number of probes after the xx minuteszz = time (in seconds) between probes after the xx minutes



file asyncthreshold 1, 32 (default) Sets the maximum number of blocks that are cached by NFSv3 asynchronous writes. The default value for this parameter (32) provides optimal performance for system throughput.Setting the value to 1 improves the accuracy of file system quota enforcement.

ip reflect 0 (default), 1 Enables packet reflect for the system.param ip reflect=0 (disables packet reflect)param ip relfect=1 (default; enables packet reflect)

nfs rstchown 0 or 1 (default) Sets restricted file ownership.When set to 1 (default), only the superuser can change the owner of a file. The current owner can only change the group ID to a group to which the owner belongs. When set to 0, chown and chgrp follow the less restrictive POSIX semantics, enabling the owner of a file to change the file ownership or group ID to any other owner or group.

nfs v3xfersize 8 (default), 16, 32, 64,...kilobytes

Changes the default transfer size for NFSv3 reads and writes.

Table 9-2 System Parameters (continued)



9

9-18


Example Assume you modify the parameter file to establish a maximum UID that is affected by user quotas using the quotamaxuid parameter in the /nas/site/param file, as in the following entry:

param quota maxuid=100000

quota maxuid number indicating the desired maximum UID (0=default)

Sets the maximum user ID to which quotas apply. An entry of 0 indicates no limits.

This prevents problems caused by accidentally imposing quotas on very large UIDs. We recommend that you set this parameter to the highest UID the site expects to support. If you need to go higher than this, the parameter can be changed later to a higher value.

quota policy filesize | blocks(blocks=default)

Specifies the quota checking policy to be used to keep track of disk usage.a

If policy=blocks, quota is based on the number of file system blocks (8K) allocated.If policy=filesize, quota is based on file usage, in 1K increments.

shadow asciifilter 0 (default), 1 To avoid problems on CFS file name storage, if I18N is not turned on, non-ASCII characters must not be used in the file name. If you are using Kerberos authentication by using compname to define the server name on the Data Mover, you must have either this parameter or I18N internationalization enabled.When the parameter is set to on, and at least one compname has been created, it is not possible to reset the parameter to 0 until all the compnames are removed.

This parameter can also be set for each Data Mover.

a. Before you change this parameter, you must turn quotas off. After you change this parameter, you must reboot the Data Mover and turn quotas back on. Refer to, Celerra File Server Techni-cal Note: Using Quotas, for specific procedures.

Table 9-2 System Parameters (continued)




If you then try to enforce a quota using the following command and parameters:

$ nas_quotas -edit -fs fs_1 5000 100000 200000

The quota limit is set for UID 5000 and 100000 but is ignored for UID 200000. In this example, nas_quotas -edit opens the quota editor for uid > maxuid, but displays the limits as ’0’ and ignore the values that are entered. An error message appears in the server_log similar to:

919708458: CFS: 3: invalid uid (200000), greater than maxUid (100000)

Server Parameters These parameters are specific to the Data Mover to which it is set, and they are included in the /nas/server/server_x (where x is the server number)/param file. Server parameters operate like system parameters, except that they affect only the Data Mover with the edited param file.

Important: After you modify /nas/server/server_x/param, you must reboot the Data Mover for which you changed the param file.

Table 9-3 lists server parameters that are supported:

Table 9-3 Server Parameters


cifs maxVCThreads # of threads Sets the maximum number of threads for a single Data Mover; this is used with virus checking.

cifs srvmgr.globalShares 0 (default) or 1 0 = global shares disabled (default). Shares created by Windows clients are specific to the NetBIOS name.

1 = global shares enabled.

NDMP bufsz buffer size in kilobytes bufsz and ntape are used together for setting NDMP backup.

NDMP ntape # _of_tape_drives_attached_to_the_Data Mover (default =0)

bufsz and ntape are used together for setting NDMP backup. For example: param NDMP ntape=2 param NDMP bufsz=128


9

9-20


PAX nbuf #_of_tape_drives_attached_to_the_Data Mover (default =0)

nbuf is added to bufsz and ntape when PAX backup is involved. For example: param NDMP ntape=2 param NDMP bufsz=128

param PAX nbuf=8

shadow asciifilter 0 (default), 1 To avoid problems on CFS file name storage, if I18N is not turned on, non-ASCII characters must not be used in the file name. If you are using Kerberos authentication by using compname to define the server name on the Data Mover, you must have either this parameter or I18N internationalization enabled.When the parameter is set to on, and at least one compname has been created, it is not possible to reset the parameter to 0 until all the compnames are removed.

This parameter can also be set for the entire system.

ufs gid32 0 (default) or 1 0 = disables the 32-bit GID feature for the Data Mover. Any file system created on the Data Mover with this setting supports only 16-bit GIDs. 1 =enables the 32-bit GID feature for the Data Mover. Any file system created on the Data Mover with this setting supports 32-bit GIDs with a maximum value of 2 billion.

Important: Before enabling this parameter, refer to Creating 32-bit GIDs on page 8-12, for its operating restrictions.

Table 9-3 Server Parameters (continued)



10

This chapter describes the backup and restoration procedures necessary to insure a successful recovery of the nas database. It also describes how to enable daemons and reboot or halt the Control Station.

◆ Database Backup ..............................................................................10-2◆ Enabling Daemons...........................................................................10-3◆ Rebooting the Control Station(s)....................................................10-5◆ Halting the Control Station(s) ........................................................10-7

Control Station Utilities

Control Station Utilities 10-1

10

10-2


Database BackupResiding within the Control Station is the nas database that is created during the installation of Celerra File Server.

The nas database stores specific information required for each Data Mover. The Celerra File Server automatically performs a backup of the entire database every hour and saves it to a file named nasdb_backup.1.tar.

This file is located in the /home/nasadmin directory. To back up this file, you can use FTP to copy the file to another destination on your network.

CAUTION!EMC strongly recommends that this database file be regularly copied from the Control Station and saved to a remote location, especially when changes to the configuration have been implemented.

If a restoration from the backup file of the entire database is required, it will be performed by qualified EMC service personnel.


10Control Station Utilities

Enabling DaemonsThere are daemons that must be running on the Control Station at all times. If for some reason they become disabled, this can cause certain facilities to fail. By default, after installation, the daemons should be activated and running; however, should you find that they are not, perform the following procedures.

Configuring NTP Since NTP is not the default timing service for Linux® on the Control Station, you must first create an NTP configuration file and start the NTP daemon before the timing service may operate. You only have to perform this procedure if you want to synchronize your Data Movers to the Control Station. After you complete this procedure, start time synchronization using the server_date command. See Configuring Time Services on page 4-9.

To configure NTP as the time service protocol on the Control Station, follow these steps:

Step Action

1. Change to root and enter the root password.

2. To create the config file using the vi editor, type: $ vi /etc/ntp.conf

3. Enter the following line into the ntp.conf file: $ server IP_address

where:IP_address is the address of the NTP time broadcast server. The customer provides this address.Example: server 168.159.9.10

4. Save the file, then exit.

5. To start the NTP daemon, type: /usr/rc.d/init.d/xntpd start

6. To verify that the daemon is running, type:ps -e|grep in.xntpd

Enabling Daemons 10-3

10

10-4


Troubleshooting If the NTP daemon was not running in Step 6, follow these steps:

Viewing the nas Daemons

To view whether the nas daemons are enabled at the Control Station, type:

ps -e|grep nas

The status of the nas daemons appear on your screen. If the daemons are not running, you must reboot your Control Station.

Viewing the httpd Daemons

For the Celerra File Server Manager to be able to manage your Celerra File Server system, it is essential for the httpd daemons to be running on the Control Station at all times.

To view whether the httpd daemons are enabled at the Control Station, type:

ps -e|grep httpd

The status of the httpd daemons appear on your screen. If the daemons are not running, you must reboot your Control Station.

Refer to Rebooting the Control Station(s) on page 10-5 to perform a reboot of your Control Station.

Step Action

1. To check the local time of the Control Station, type:$ date

2. Compare this value with the time value that is being provided by the NTP server. If they are not relatively close (within several minutes), change the local time on the Control Station so that the two are more closely synchronized. Type:$ date hhmm

3. Return to step 6 in the previous section.



Rebooting the Control Station(s)The Control Station(s) may be rebooted locally or remotely. Follow the steps below to reboot your Control Station(s).

Locally To locally reboot a single Control Station or both Control Stations, perform one of the following procedures:

Rebooting a SingleControl Station

If your system has one Control Station, follow these steps to reboot it:

Rebooting TwoControl Stations

If your system has two Control Stations, follow these steps to reboot:

Step Action


2. Type:reboot

Result: The Control Station reboots.

Step Action

1. To determine which Control Station is functioning as the primary and which as the secondary, type:/nas/sbin/getreason

Result: The primary Control Station returns a reason code of 10; the secondary Control Station returns a reason code of 11.

2. Place the Control Switch (located on the back of the front door) to whichever Control Station is functioning as the primary.


4. Type:reboot

Result: The primary Control Station reboots and fails over to the secondary Control Station.

Rebooting the Control Station(s) 10-5

10

10-6


Remotely From the command-line interface, using Telnet, perform the following steps:

To continue working remotely after the reboot, establish another Telnet connection.

5. Reset the Control Switch to communicate with the new primary Control Station.


7. Type: reboot

Result: The new primary Control Station reboots and fails over back to the original Control Station.

Step Action

Step Action


2. Type: reboot

Result: The Control Station performs an orderly reboot.



Halting the Control Station(s)The Control Station(s) may be halted locally or remotely. Follow the steps below to shut down your Control Station(s).

Locally To halt a single Control Station or both Control Stations, perform one of the following procedures.

Halting a SingleControl Station

If your system has one Control Station, follow these steps to perform a halt:

Halting Two ControlStations

If your system has two Control Stations, follow these steps to perform a halt:

CAUTION!You must halt your secondary Control Station before halting your primary.

Step Action


2. Type:/sbin/init 0

Result: The Control Station performs an orderly shutdown.

Step Action

1. To determine which Control Station is functioning as the primary and which as the secondary, type:/nas/sbin/getreason

Result: The primary Control Station returns a reason code of 10; the secondary Control Station returns a reason code of 11.

2. Place the Control Switch (located on the back of the front door) to whichever Control Station is functioning as the secondary.


4. Type:/sbin/init 0

Result: The secondary Control Station halts and fails over to the primary Control Station.

Halting the Control Station(s) 10-7

10

10-8


Remotely From the command-line interface, using Telnet, perform the following steps:

To reboot the Control Station, you must use the Celerra cabinet console.

5. Reset the Control Switch to communicate with the primary Control Station.


7. Type: /sbin/init 0


Step Action

Step Action


2. Type: /sbin/init 0



11Invisible Body Tag

This chapter contains procedures, information, error messages and tips for troubleshooting your system.

◆ Troubleshooting................................................................................ 11-2◆ Checking Log Files......................................................................... 11-11◆ Monitoring System Activity ......................................................... 11-12

Troubleshooting

Troubleshooting 11-1

11

11-2

Troubleshooting

Troubleshooting While using your system, various messages may appear indicating successful command execution, or in some cases, a failure. Error messages appear when there is a fault in the command syntax or the system, while system messages are routinely reported to the log file.

Both types of messages reflect the performance of your system and can be used to monitor system efficiency and to troubleshoot problems.

In the error message table, the first column contains the error message you may see when you attempt to execute your command. In the second column, the probable cause and the solution are presented.

There are some cases when no message appears relating to a problem. Instead situations present themselves which in turn, may indicate a problem. These occurrences are represented in this chapter by scenario tables.

In the scenario table, the first column contains the symptom you may see when you attempt to execute your command. In the second column, the probable cause, and in the third, the solution.

Post-Install Error Messages

After installation has been completed and you have begun to configure your Celerra File Server, there are a few error messages that may appear indicating a specific condition.

See Table 11-1 for a list of error messages, their probable causes, and solutions.


11Troubleshooting

Table 11-1 Error Message Troubleshooting

Error Message Probable Cause/Solution

A network error occurred: unable to connect to server (TCP Error: Broken Pipe)

The server may be down or unreachable.

Try connecting again later.

When attempting to put the Control Station path into Netscape, one of the following may have occurred:• the path may have been entered incorrectly, or the server

connections may be down• the daemons are not running First, verify that the Control Station is operational, then either enter the proper Control Station IP address or refer to Enabling Daemons on page 10-3.

NAS_DB not defined After installing the software package, you may not have logged out. Before executing any commands, you must first log out and then log back in.

This location (URL) is not recognized...

Check the location and try again.

When attempting to put the Control Station path into Netscape, one of the following may have occurred:• the path may have been entered incorrectly, or the server

connections may be down• the daemons are not running First, verify that the Control Station is operational, then either enter the proper Control Station IP address or refer to Enabling Daemons on page 10-3.


11

11-4

Troubleshooting

Volume Troubleshooting

During volume management, certain error messages may appear indicating an error in your command execution. Table 11-2 contains examples of messages that you may encounter and how to remedy them.

Table 11-2 Volume Error Messages


invalid volumes for extension

You may have attempted to extend a Disk, Stripe, or Slice Volume. Meta Volumes are the only volume type that can be extended. Select a Meta Volume for extension, then retry.

is not a Meta Volume You may be trying to create a file system on a volume other than a Meta Volume. File systems can only be created and stored on Meta Volumes. Create a Meta Volume for the file system, then retry.

item is currently in use by filesys: fsname

You may be trying to extend a Meta Volume that is in use by a file system. Select a Meta Volume that is not in use, then retry.

not extendable volume You may have attempted to extend a Disk, Stripe, or Slice Volume. Meta Volumes are the only volume type that can be extended.

no space left on volume Your volume has run out of space and is unable to accommodate additional files or file systems. You can extend a Meta Volume by adding additional volumes to your base Meta Volume after removing file systems.

requires root command You may be attempting to execute a command against a root file system or volume to which you do not have access. Select a non-root volume or file system.


11Troubleshooting

File System Troubleshooting

This section contains two tables to assist in troubleshooting file system problems. Table 11-3 consists of error messages that may occur while you are performing specific file system functions, while Table 11-4 contains scenarios.

There can be more than one symptom for the same problem, and in some cases more than one probable cause.

Table 11-3 File System Error Messages


filesystem is mounted, can not delete

You may be trying to delete a mounted file system. Verify that this is the correct file system to be deleted, permanently unmount the file system, then retry.

filesystem is not mounted You may be attempting to execute a command to file system that must be mounted. Mount the file system, then retry.

filesystem unavailable for read_write mount

The file system is already mounted by another Data Mover. Verify the list of mounted file systems.

item is currently in use by movername

The file system is still mounted. Unmount the file system, then retry.

Mount Point Name [name] is not valid. Please Re-enter

The mount point wasn’t entered correctly or doesn’t exist. When entering the mount point name, the slash (/) that precedes the mount point name may have been omitted. Type a slash before entering the mount point name, then retry.

If the error message reappears, check your list of mount points.

must unmount from server(s): movername

You may be trying to execute a file system check against a mounted file system. Unmount the file system, then retry.

no such file or directory The value being typed either does not exist or does not exist as typed (typo). Check that you are entering the correct value and insure that the uppercase and lowercase letters match.

Note: All mount points begin with a forward slash “/”


11

11-6

Troubleshooting

File System Behavior When a file system is full, if you try to copy or create a big file, you will receive a message indicating that the file system is full.

If you create a small file, you will not receive an error message; however, the file size is zero and no data is held.

Path busy: filesystem fsname is currently mounted on mountpoint

A file system is already using the mount point you are attempting to mount. Create a new mount point, or unmount the file system, then retry.

requires root command You may be attempting to execute a command against a root file system or volume to which you do not have access. Select a non-root volume or file system, then retry.

undefined netgroup The client you are trying to export for is not recognized. Enter the clients name into the system, then retry.

Table 11-3 File System Error Messages (continued)


Table 11-4 File System Scenarios

Symptom Probable Cause Solution

You are unable to mount a file system.

There are many probable causes for this scenario. Many will provide an error message, though occasionally, there will not be one. In this case, the mount table entry already exists.

Perform a mount all to activate all entries in the mount table. Obtain a list of mounted file systems, then observe the entries. If the file system in question is already mounted (temporary or permanent) perform the necessary steps to unmount it, then retry.

An unmounted file system reappears in the mount table after a system reboot.

The file system may have been temporarily unmounted prior to reboot.

Perform a permanent unmount to remove the entry from the mount table.


11Troubleshooting

Data Mover Troubleshooting

Table 11-5 lists Data Mover error messages, while Table 11-6 describes potential problems that may occur with Data Movers.

Table 11-5 Data Mover Error Messages


hardware components mismatch When creating a Standby Data Mover, the network interface cards between the Standby and the Primary are not identical. Reconfigure and install a network interface configuration to a Data Mover or select another Data Mover.

invalid interface specified The interface name may not have been entered correctly. Check the list of Network Interfaces, then retry.

invalid policy specified The policy type defined when creating the standby relationship is invalid or entered incorrectly. Valid policy types are: auto, manual, retry.

is a faulted standby server You are trying to execute a command to a Data Mover that is in a faulted state, and is, therefore, unavailable. You must first restore the original primary Data Mover before executing a command.

is a standby server You are trying to execute a command to a Data Mover that is of type standby, and is, therefore, unavailable.

is in a faulted state You are trying to execute a command to a Data Mover that is in a faulted state, and is, therefore, unavailable.

is not a standby server You may be trying to activate a Data Mover that is not of type=standby. Create a standby Data Mover, then retry.

non-root filesystems are mounted You may be trying to change a Data Mover with mounted file systems to be type=standby. Select another Data Mover for standby or unmount all file systems.

server not responding A Data Mover is either rebooting in the background or a failure has occurred. First attempt to reboot your Data Mover, then activate your standby Data Mover, then further investigate or call EMC Customer Service.


11

11-8

Troubleshooting

Server_n replace in progress... failed

Error:

replace_net:interface:failed to complete command

You may need to reboot your server. Reboot your Data Mover, then retry.

Slot #, Over temperature warning The internal temperature of the Data Mover has reached 63 degrees C. Insure proper air flow for SNSD and adequate ambient operating temperature, then call EMC Customer Service.

Slot #, Over temperature failure The internal temperature of the Data Mover has reached 71 degrees C, therefore causing it to fail. Call EMC Customer Service.

software license to enable group not installed

You may have attempted to use an unavailable feature.

standby is not configured You may have attempted to activate a Data Mover that is not of type=standby. Set the Data Mover to be of type=standby, then retry.

standby is not available, is active

If you have a standby linked to more than one primary, the standby may have already been activated for the other primary Data Mover. You can designate another standby to take over functionality for your failed primary.

standby is not in faulted state When a failover occurs, the original primary Data Mover becomes the standby for the acting primary (the Data Mover originally set to be type=standby). You may have attempted to perform a restore of a Data Mover that has not undergone a failover.

unable to acquire lock(s), try later

A command is already in progress. Wait until execution is complete, then retry.

unable to connect to host The Data Mover you are trying to reach may have lost connectivity. Verify the state of the Data Mover by checking uptime, then reboot.

Table 11-5 Data Mover Error Messages (continued)



11Troubleshooting

Error messages indicating a problem with a Data Mover may also appear in the system log, therefore, during the process of troubleshooting, you should periodically refer to the log to check for the presence of certain error messages. These error messages appear only in the system log and will not appear on your screen during an active session.

Table 11-6 Data Mover Scenarios

Symptom Probable Cause Solution

Data Mover hangs repeatedly. Data Mover may have lost its connection either physically, or from the network, or may be out of memory or free space.

You can reboot the Data Mover, then check free space and memory. If these appear acceptable, you can verify that the cables are secure, then perform a ping or view system uptime.

When attempting to view SCSI devices, the system hangs.

Storage system is off-line. Verify that the storage system is online, then retry.

When installing a replacement Data Mover into a slot, the movername is not the same as the original movername.

The new movername does not assume the old movername. Instead it takes the next available movername. For example, if you have 5 Data Movers, the next Data Mover name would be server_6.

You can either rename the Data Mover or you can leave the Data Mover with the newly assigned name.


11

11-1

Troubleshooting

See Table 11-7 for a listing of troubleshooting error messages and general scenarios.

Table 11-7 System Log Error Messages and General Scenarios


KERNEL: 3: addrspac: cannot find 1 pages, rechecking, caller:15cf02

The system is hung. Call EMC Customer Service.

UFS: 3: could not allocate cylinder group


LIB: 4: malloc() for 330 bytes failed in more_memory


When attempting to perform a Save As of a log file, Netscape crashes.

You are in “continuous update” instead of “snapshot”. You cannot perform a Save As of a log file while there are continuous updates. Select Snapshot before performing a Save As.

0 Celerra File Server Basic Administration Guide

11Troubleshooting

Checking Log FilesThere are a number of log files available that allow you to monitor system performance. See Table 11-8 for a description of the log files that are available.

Table 11-8 Log Files

Log File Output Command Line Equivalent

Current Displays the current log updates. server_log movername

Complete Displays a complete history of logs for a Data Mover

server_log movername -a

System The System Log displays a cumulative list of system activities and messages from the most recent reboot.

NAS_DB/log/sys_log

Command Displays a log of all commands executed for the Celerra File Server

NAS_DB/log/com_log

Checking Log Files 11-11

11

11-1

Troubleshooting

Monitoring System ActivityVarious statistic outputs that can assist you in performance monitoring and troubleshooting are described in Table 11-9.

Table 11-9 Monitoring System Performance

Type of Display Output Command Line Equivalent

Protocol Packet statistics and connection statuses are displayed.

server_netstat movername -s -p protocol

Routing Table Routing table statistics are displayed. server_netstat movername -r

Interface Statistics regarding specific interfaces are displayed.

server_netstat movername -i

NFS V2 and V3 NFS statistics are displayed. server_nfsstat movername -n

RPC RPC statistics are displayed. server_nfsstat movername -r

Data Mover All Data Mover statistics are displayed. server_nfsstat movername

System Threads information, memory status, and the state of the CPU are displayed.

server_sysstat movername

Active Connections TCP and/or UDP connections appear. server_netstat movername -p protocol

Data Mover Server message block (SMB) statistics are displayed.

server_cifsstat movername

2 Celerra File Server Basic Administration Guide

AInvisible Body Tag

This appendix provides technical specifications for the Celerra File Server and covers the following topics:

◆ Physical Data .....................................................................................A-2◆ Environmental Data..........................................................................A-2◆ Power Requirements ........................................................................A-3◆ Hardware/Software Specifications ................................................A-4

TechnicalSpecifications

Technical Specifications A-1

A

A-2

Technical Specifications

Physical Data

Depth 36.75 in. (93.35 cm)

Width 24 in. (60.96 cm)

Height 73.875 in. (187.64 cm)

Access (Raised) FloorTile Requirements

EMC assumes 24 in. (60.96 cm) floor tiles and requires 11 in. (28 cm) raised floor clearance for cabling.

Weight support for 1175 lb. (533 kg) is required.

Service Area 48 in. (1.22 m) service clearance is required at the front and rear of the Celerra File Server cabinet.

Floor Space forCabinet

7.5 sq. ft. (3.30 sq. m)

These specifications apply to the Celerra File Server cabinet only. Multi-enclosure configurations will vary.

Environmental Data

OperatingTemperature

59--90 degrees F (15--32 degrees C)

Operating Altitude(maximum)

Sea level to 8000 ft. (2,500 m)

Operating Humidity Between 10% and 80%, non condensing


ATechnical Specifications

Power Requirements

For the Celerra FileServer Cabinet

The customer must supply a single (or dual, if required) Russellstoll 3933 VAC connector.

Single (or dual if required) Russellstoll 3750 208 VAC power plug is shipped with the Celerra File Server.

The local site circuit must be rated at 30 Amps.

For the Modem Line The modem line requires:

◆ Analog phone line with RJ11 jack

CAUTION!This phone line must be separate from the storage system phone line.

◆ 110 VAC power receptacle for a modem connection (for configurations in the United States)

Power Requirements A-3

A

A-4

Technical Specifications

Hardware/Software Specifications

Data Movers ◆ FTP◆ NFSv2 and NFSv3 concurrently over TCP/IP and UDP/IP◆ CIFS over TCP/IP◆ Fast Ethernet (10Base-T/100Base-TX), Gigabit Ethernet (FDDI

and ATM-OC3 are supported in earlier versions of the Celerra File Server)

◆ UxFS File System◆ UNIX archive utilities (tar cpio)◆ SNMP MIB II manageability◆ Redundant Ultra Fast Wide Differential SCSI interfaces◆ Autonomous Data Mover architecture◆ Data Mover failover

Control Station ◆ Ethernet (FDDI is supported in earlier versions of the Celerra File Server)

◆ SNMP MIB II manageability◆ Dual Redundant Control Stations (optional second Control

Station)◆ Telnet manageability◆ Remote management with an HTTP server management interface

Celerra Cabinet ◆ Battery backup◆ N+1 load-sharing power supplies◆ Hot-swappable subassemblies◆ Redundant internal Ethernet for environmental status monitoring

and control◆ Auto-Call remote maintenance parameter monitoring

Power and CoolingData

◆ Power Consumption (kVA) 1.34◆ Heat Dissipation (BTU/hr) 4,563

Values represent maximum figures for Celerra File Server Cabinets only. Requirements for multi-enclosure configurations will vary.

Regulatory andAgency Certifications

◆ UL-950◆ IEC 950/EN 60950◆ CISPR 22 Class A/EN 55022◆ CSA C22.2 No. 950◆ FCC Subpart B◆ IEC 801-2/EN 55024-2


Bnvisible Body Tag

This appendix reviews the EMC process for detecting and resolving software problems, and provides essential questions that you should answer before contacting the EMC Customer Support Center.

This appendix covers the following topics:

◆ Overview of Detecting and Resolving Problems ......................... B-2◆ Troubleshooting the Problem .......................................................... B-3◆ Before Calling the Customer Support Center ............................... B-3◆ Documenting the Problem............................................................... B-4◆ Reporting a New Problem ............................................................... B-4◆ Sending Problem Documentation................................................... B-5

Customer Support

Customer Support B-1

B

B-2

Customer Support

Overview of Detecting and Resolving ProblemsEMC software products are supported directly by the EMC Customer Support Center in the United States.EMC uses the following process to resolve customer problems with its software products (Figure B-1).

Figure B-1 Problem Detection and Resolution Process

ProblemDetection

Refer toTroubleshootingin this Manual

Collect ProblemInformation as

Directed

Contact the EMC CustomerSupport Center:

U.S.:Canada:Worldwide:

(800) SVC-4EMC(800) 543-4SVC(508) 497-7901

Confirm that theProblem is Software

Related

Call will be Directedto an EMC SoftwareSupport Engineer

Problem isTracked andManaged toResolution

CFS_000093


BCustomer Support

Troubleshooting the ProblemPlease perform the relevant diagnostic steps before you contact the EMC Customer Support Center:

1. Read the documentation carefully.

2. Reconstruct the events leading up to the problem and describe them in writing.

3. Run some test cases to reproduce the problem.

If you encounter a problem that requires technical programming or analysis, call the nearest EMC office or contact the EMC Customer Support Center at one of the following numbers:

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

Please do not request a specific support representative unless one has already been assigned to your particular system problem.

Before Calling the Customer Support CenterHave the following information available before calling the Customer Support Center or your support representative (if one has been assigned to you):

❑ Your company name

❑ Your name

❑ Your phone number

❑ For an existing problem, the problem tracking system ID, if one was previously assigned to the problem by a support representative

❑ For an MVS problem, the JESLOG, SYSPRINT, all STDOUT DD members of the server job output and similar output for the client, and the relevant portion of the SYSLOG

Troubleshooting the Problem B-3

B

B-4

Customer Support

Documenting the ProblemIf the EMC Customer Support Center requests information regarding the problem, please document it completely, making sure to include the following information:

❑ Your company name and address

❑ Your name

❑ Your telephone number

❑ The importance of the problem, so that it can be assigned a priority level

To expedite the processing of your support request, you can photocopy this list and include it with the package.

Reporting a New ProblemFor a new problem, please provide the following information:

❑ Release level of the software that you are running

❑ Software installation parameters

❑ Host type on which you are running

❑ Operating system you are running and its release number

❑ Functions of the software that you are running

❑ Whether you can reproduce the problem

❑ Previous occurrences of the problem

❑ Whether the software has ever worked correctly

❑ Time period that the software did work properly

❑ Conditions under which the software worked properly

❑ Changes to your system between the time the software worked properly and the problem began

❑ Exact sequence of events that led to the system error

❑ Message numbers and complete text of any messages that the system produced

❑ Log file dated near the time the error occurred


BCustomer Support

❑ Results from tests that you have run

❑ Other related system output

❑ Other information that may help solve the problem

Sending Problem DocumentationUse one of the following methods to send documentation of the problem to the EMC Customer Support Center:

◆ E-mail

◆ FTP

◆ U.S. mail to the following address:

EMC Customer Support Center45 South StreetHopkinton, MA 01748-9103

If the problem was assigned a number or a specific support representative, please include that information in the address as well.

Sending Problem Documentation B-5

B

B-6

Customer Support


CInvisible Body Tag

This section contains the GNU General Public License (GPL). The GPL is the license for the Linux operating system. All EMC software, including the Celerra File Server software, is licensed by the EMC Software License included in the software kit.

◆ GNU General Public License...........................................................C-2◆ Preamble.............................................................................................C-2◆ Terms and Conditions for Copying, Distribution, and

Modification.......................................................................................C-3◆ NO WARRANTY .............................................................................. C-8

GNU General PublicLicense

GNU General Public License C-1

C

C-2

GNU General Public License

GNU General Public LicenseVersion 2, June 1991

Copyright © 1989, 1991 Free Software Foundation, Inc.59 Temple Place, Suite 330Boston MA 02117-1307USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.


CGNU General Public License

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors’ reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

Terms and Conditions for Copying, Distribution, and Modification0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact


C

C-4


all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.



In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.


C

C-6


4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License.However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the



integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.


C

C-8


NO WARRANTY11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS


Glossary

This glossary contains terms related to disk storage subsystems. Many of these terms are used in this manual.

AAccess-control List Contains information about the users and groups that are allowed

access to an object.

Active Indicates the mode (user-defined state) of a physical I/O path. I/O is queued to an active path whenever available.

Adapter Card that provides the physical interface between the Celerra File Server cabinet, the network and disk devices (NIC or SCSI adapter).

Address ResolutionProtocol (ARP)

Allows systems to query the network to identify a machine with a specific internet address.

Aggregation See Ethernet Trunking.

Applications ProgramInterface (API)

Set of calling conventions that define how to invoke a service through a software package.

Arbitrated Loop A Fibre Channel topology structured as a loop and requiring a port to successfully negotiate to establish a circuit between itself and another port on the loop.

Asynchronous TransferMode (ATM)

Known as a fast packet technology. ATM packetizes voice, video, and data, forming 53-byte frames which are put onto a high-speed data channel.

Celerra File Server Basic Administration Guide g-1

g-2

Glossary

ATM Switch ATM switching system for public telecommunications networks. Provides ATM multiplexing, Virtual Path switching, and Virtual Channel switching.

Attribute Describes the condition of a power device, host bus adapter, or device path.

Authentication Process for verifying the identity of a user who is trying to access a file or directory.

Automated LocalBackup and Restore

Procedure in which a remote backup server running an NDMP-compliant backup tool manages the local backup of the Celerra File Server. The network transmits only control information between the remote backup server and the Data Mover. The backup copy is created on a tape library unit locally attached to the Data Mover. Backup data does not travel across the network.

Automated NetworkBackup and Restore

Procedure in which a remote backup server, running an NDMP-compliant backup tool, copies data from a Data Mover over the network to its local tape library as if the files were locally attached to the backup server. Backup data travels across the network. To perform automated network backup, the Data Mover must be NFS-enabled.

Availability The accessibility of a computer system or network resource.

BBackup and Restore Technique that aims to ensure file system integrity and security by

using a procedure that creates a copy (usually on tape) of a file system or incremental changes to a file system, from which that file system can later be restored.

Backup DomainController (BDC)

Domain controller that has the same database as the PDC and may replace the PDC if needed. The BDC provides some fault tolerance and load balancing for the NT domain.

Bandwidth The maximum amount of data that can be transmitted through a data channel per unit of time. Usually expressed in megabytes per second.

BandwidthAggregation

See Ethernet Trunking.

bps Bits per second.


Glossary

BPS Bytes per second (B/S).

Bridge A device that provides a connection between two or more LANs.

Browse Master Provides the service that gathers and organizes the list of computers and domains displayed in Network Neighborhood. The Browse Master maintains an up-to-date list of network resources and provides this information to other computers on the network.

Browser Program, usually graphically based, used to access information over the Internet or an intranet. Celerra File Server Manager uses either Netscape Navigator or Internet Explorer as its browser.

Buffer Storage area used for handling data in transit. Buffers compensate for differences in processing speed between networks.

Bundle See Ethernet Trunking.

BCV (BusinessContinuance

Volumes)

Business Continuance Volumes are copies of active production volumes that can be used to run simultaneous tasks in parallel with one another. This gives customers the ability to do concurrent operations, such as data warehouse loads and refreshes or point-in-time backups, without affecting production systems.

CCache Random access electronic storage used to retain frequently used data

for faster access by the channel.

Cache Slot Unit of cache equivalent to one track.

Celerra File ServerCabinet

Physical component of Celerra File Server which houses the Data Movers and the Control Station. The Celerra File Server cabinet provides an interface between the storage system and the external network.

Celerra File ServerManager

Web-based GUI used to manage and administer the Celerra File Server.

Celerra File ServerMonitor

Java client/server application that lets you observe the performance of a Symmetrix system that is attached to a Celerra File Server and that of any Data Movers mounted in the Celerra File Server cabinet.


g-4

Glossary

Channel Path that allows for the rapid transfer of data between a device and storage.

Channel Director Component in the Symmetrix system that interfaces between the host channels and data storage. It transfers data between the channel and cache.

Client Front-end device that requests services from a server, often across a network.

Common Internet FileSystem (CIFS)

File system that uses the Server Message Block (SMB) protocol to provide secure file access and transfer to a multitude of hosts such as LANs, Intranets, and the Internet. CIFS separates naming conventions tied into SMB and allows use of any chosen standard, (e.g.,Domain Name Service or DNS). CIFS complements existing file access protocols such as HTTP, FTP, and NFS.

Control Station A hardware and software component of the Celerra File Server that provides the controlling subsystem to the Data Movers, as well as the software interface to all server components. The Control Station is used to install, configure, and monitor Celerra File Server components. Resides in slot_0 of the Celerra File Server cabinet.

Connectivity The ability of hardware devices or software to communicate with other hardware or software.

DData Access Real

Time (DART)Operating system software that runs on the Data Mover. It is a real-time, multi-threaded operating system optimized for file access, while providing service for standard protocols.

Data Availability Access to any and all user data by the application.

Data Mover Celerra File Server cabinet component running software that retrieves files from a storage device and exports the file to a network client.

Data EncryptionStandard (DES)

Commonly used algorithm for encrypting and decrypting data.

Device Name given to the physical device of a network adapter.


Glossary

Delayed Fast Write No existence of room in cache for the data presented by the write operation.

Destination Address Hostname or IP address of the machine to which you are routing.

Diagnostics System-level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.

Direct Access StorageDevice (DASD)

Most commonly known as a magnetic disk device.

Director Component in the Symmetrix system that allows it to transfer data between the host channels and disk devices. See also Channel Director and Disk Director.

Disaster Recovery Preventative measures using redundant hardware, software, data centers and other facilities to ensure that a business can continue operations during a natural or man-made disaster and if not, to restore business operations as quickly as possible when the calamity has passed.

Discretionary AccessControl List (DACL)

Allows specific users and groups to perform a specified action.

Disk Array Enclosure(DAE)

A storage device on the FC4700-2 that includes an enclosure, up to 10 disk modules, one or two Fibre Channel Link Control cards (LCC), and one or two power supplies.

Disk Array ProcessorEnclosure (DPE)

A storage device on the FC4700-2 that includes an enclosure, up to 10 disk modules, two Storage Processors (SP), two Fibre Channel Link Control cards (LCC), and two power supplies. A DPE can support up to 11 DAEs (each with up to 10 disk modules) in addition to its own 10 disk modules, for a total of 120 disk modules.

Disk Director Component in the Symmetrix system that interfaces between cache and the disk devices.

Domain Represents a group of machines by a given name that is defined by the internet community.

Domain NameService (DNS)

Option allowing name resolution to be conducted within a system.


g-6

Glossary

Dual-Initiator Symmetrix system feature that automatically creates a backup data path to the disk devices serviced directly by a disk director, if that disk director or the disk management hardware for those devices fails.

Dynamic Sparing Symmetrix system feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non mirrored devices in the Symmetrix subsystem.

EEMCNAS EMC Network Access Storage. Installation package that installs the

Celerra File Server only on the primary Control Station.

EMCNASSBY Installation package that loads various software components on the optional (standby) Control Station. Install this package only after loading emcsys and emcnas.

EMCSYS EMC System. Installation package that loads certain Celerra File Server utilities on both the primary and the optional (standby) Control Station. Install this package before emcnas and nassby.

Enterprise Storage A combination of intelligent storage systems, software and services. Together, these products and services enable an enterprise to store, retrieve, manage, protect and share information from all major computing environments, including UNIX, Windows NT, Windows 2000 and mainframe platforms.

EtherChannel See Ethernet Trunking.

Ethernet LAN technology that transfers packets ranging from 48 to 1500 bytes. Ethernet uses a media access method that listens to the wire before transmitting in order to minimize packet collisions.

Supported cable media and interface connectors include: 10Base-2— thin wire coaxial cable with BNC interface (up to 200 m); 10Base-5—thick wire coaxial cable (up to 500 m); 10Base-T—hub (star) topology with twisted-pair drop cables and RJ45 interface; and 10Base-F—hub topology with optical fiber drop cables.

Ethernet Trunking Data transmission methodology that combines or aggregates up to eight full-duplex, point-to-point communication links into a bundle.


Glossary

Each bundle appears as a single link with only one IP address for the entire bundle.

Extended IndustryStandard Architecture

(EISA)

Bus that is 32 bits wide with a transfer rate of 40 MB/s. It is backward compatible to support ISA devices. Also known as Enhanced Integrated System Architecture.

FFabric A Fibre Channel topology structured with one or more switching

devices that interconnect Fibre Channel N_Ports and route Fibre Channel frames.

Failover Data is immediately and nondisruptively routed to an alternate data path or device in the event of an event of an adapter, cable, channel controller or other device.

Fast Ethernet Can be referred to as 100Base-T. A 100 MB/s version of 10Base-T Ethernet that uses the same media access as Ethernet. Fast Ethernet provides a nondisruptive, smooth evolution from current 10Base-T Ethernet to high-speed 100 MB/s.

Fast Write In the Symmetrix system, a write operation at cache speed that does not require immediate transfer of data to disk. The data is written directly to cache and is available for later destaging.

Fibre Channel (FC) Fibre channel is nominally a one-gigabit-per-second data transfer interface technology, although the specification allows data transfer rates from 133 megabits per second up to 4.25 gigabits per second. Data can be transmitted and received at one-gigabit-per-second simultaneously. Common transport protocols, such as Internet Protocol (IP) and Small Computer System Interface (SCSI), run over Fibre Channel. Consequently, high-speed I/O and networking can stem from a single connectivity technology.

Fibre ChannelArbitrated Loop

(FC-AL)

A standard for a shared access loop, in which a number of Fibre Channel devices are connected (as opposed to point-to-point transmissions). Celerra does not support arbitrated loop.

Fiber Distributed DataInterface (FDDI)

High-speed (100 MB/s) networking standard for LANs or Metropolitan Area Networks (MANs). The underlying medium is fiber optics and the topology is a dual-attached, counter-rotating Token Ring. FDDI connections can be identified by the orange fiber cable.


g-8

Glossary

Field Replaceable Unit(FRU)

Component that is replaced or added by service personnel as a single entity.

File System A file system is composed of the files and directories on each individual disk partition.

File Transfer Protocol(FTP)

High-level protocol for transferring files from one machine to another. Implemented as an application-level program (based on the OSI Model), FTP uses Telnet and TCP protocols.

Full Backup Copies all the scanned client files, independent of the time of their last backup or their location, to the backup server.

GGatekeeper Communication channel between the Celerra File Server and the

storage system disk array.

Gateway Device through which computers may connect.

Gateway Address Host or IP address of the gateway machine through which you are routing.

Gigabit Ethernet Transmission standard that provides a data rate of 1 billion b/s (one gigabit). Gigabit Ethernet is defined in the IEEE 802.3ab standard.

Gigabyte (GB) 109 bytes, defined as 2 to the 30th power (1,073,741,824) bytes. One gigabyte is equal to 1,024 megabytes. Abbreviated as G or GB.

Graphical UserInterface (GUI)

Interface used to administer commands and execute functions.

HHost Addressable end node capable of transmitting and receiving data.

Hub A Fibre Channel device used to connect several devices (such as computer servers and storage systems) into a Fibre Channel-Arbitrated Loop (FC-AL).

IIncremental Backup A backup method that copies only those client files that have

changed since the previous backup of any level.


Glossary

Inode Type of data structure that describes a file system; notably, the maximum number of files that a system can contain.

Integrated CachedDisk Array

Specialized disk subsystem that uses large cache sizes to decrease the amount of time the CPU must wait for an I/O request to be processed.

Internet ControlMessage Protocol

(ICMP)

Communications protocol that reports errors in datagram processing between networked nodes. Part of the Internet (IP) suite of protocols.

Internet Protocol (IP) Suite of network protocols that offer connectionless-mode network service.

I/O Device Addressable input/output unit, such as a disk device.

KKernel Configuration that is read when the computer is powered up. It is

responsible for interacting with the hardware of the computer. The kernel manages memory, controls user access, maintains file systems, handles interrupts and errors, performs input and output services, and allocates the resources of the computer.

Kilobyte (K) 1024 bytes.

LLink A connection between two ports.

Load Balancing Distributes the I/O workload across all paths.

Static load balancing assigns different devices to different physical paths, so that all paths are used for one or more devices.

Dynamic load balancing distributes the workload over all the paths that the devices share, and make all paths equally burdened from moment to moment.

Local Area Network(LAN)

Minimum of two network nodes communicating through a physical medium over a distance of less than 3 kilometers.

Local Backup Celerra File Server backup procedure that creates a backup copy of a file system or incremental changes to a file system on a tape library


g-10

Glossary

unit that is locally attached to a Data Mover. See also Manual Local Backup and Automated Local Backup.

Logical Device One or more physical devices or partitions managed by the storage controller as a single logical entity. Logical devices aggregated and managed at a higher level by a volume manager are referenced as logical volumes rather than logical devices.

Logical Unit Number(LUN)

Last part of a SCSI address. LUNs are numbered 0 through 7.

Logical Volume User-defined storage device.

MManagement

Information Base(MIB)

Database controlled by SNMP. The MIB holds information about all resources managed by a network management system.

Manual Local Backup Non-automated procedure in which an operator enters commands manually or using a script. During the backup operation, single Data Movers or multiple Data Movers in parallel are backed up (fully or incrementally) to one or more locally-attached tape drives. Each Data Mover requires its own tape drive, attached to one of the Data Mover’s SCSI ports. Data goes directly to the Celerra File Server-attached tape drive and does not traverse the network. Also called “simple local backup.”

Media Any of a variety of physical devices, such as the disk surface on which data is stored, the physical cable connecting nodes to form a network, etc. (Medium is the singular form.)

Media Access Control(MAC) Address

The media-specific access control protocol within IEEE802 specifications.

Megabyte (MB) 106 bytes.

Metadata Data containing structural information (such as access methods) about itself.

Meta Drive Group of disk partitions accessed as a single partition. This is made possible by concatenating or striping the physical devices.


Glossary

Meta Volume Concatenation of volumes, which can consist of disk, slice, or stripe volumes.

Metropolitan AreaNetwork (MAN)

Network operating over an area of at least 50 kilometers at approximately 100MB/s.

Mirrored Pair Logical volume with all data recorded twice, once on each of two different physical devices.

Mirroring Method by which the Symmetrix system maintains two identical copies of a designated volume on separate disks. Each volume is automatically updated during a write operation. If one disk device fails, the Symmetrix system automatically uses the other disk device.

Mount In combination with NFS, mount attaches to a subdirectory of a remote system over a dummy directory on the local machine. This protocol allows clients to mount or unmount file systems for access through NFS. Mount is accessible over UDP or TCP.

Mount v2/v3 Protocol that allows clients to mount or unmount file systems for access through NFS. Mount is accessible over UDP or TCP.

NNDMP See Network Data Management Protocol.

NetBIOS Network Basic Input/Output System. A network programming interface and protocol developed for IBM personal computers.

Network Combination of devices, cabling, and software that make up a communication infrastructure.

Network Backup See Remote Backup.

Network DataManagement

Protocol (NDMP)

A network protocol designed for the backup and retrieval of data. It is an open standard protocol for enterprise-wide backup of heterogeneous network-attached storage. Version 1 supports locally-attached tape backup; version 2 supports network-attached tape backup.

Network DataManagement Service

(NDMS)

Network communication service that uses NDMP and contains its own backup and retrieval utilities.


g-12

Glossary

Network File System(NFS)

A distributed file system that provides transparent access to remote disks. NFS allows all systems on the network to share a single copy of the directory (the alternative involves duplicating common directories on every system). Web NFS enables this same functionality to occur over the Internet.

Network InformationService (NIS)

Service whose primary purpose in SNFS is to convert hostnames to IP addresses or IP addresses to hostnames.

Network InterfaceCard (NIC)

Insertable circuit board that provides network communication capabilities to and from a computer system.

Network LockManager (NLM)

Allows file and byte-range locking by clients.

nsap Network source address point.

Network StatusMonitor (NSM)

Protocol that allows clients and servers to monitor each other’s status and be aware of reboots.

PPhysical Volume Addressable disk on the SCSI bus.

Port On a computer, it is a physical connecting point to which a device is attached.

Portmapper v2 Accessible through UDP and TCP. Allows clients access to the services registered on the Data Mover.

Primary DomainController (PDC)

Master domain controller that processes all the users and groups that are connected to a domain.

Promotion Process of moving data from a track on the disk device to cache slot.

Protocol Standard defined between the client and the user that determines how information is transferred and interpreted over a network.

RRAID (Redundant

Array of IndependentDisks)

Data is stored on multiple magnetic or optical disk drives to increase output performance and storage capacities and to provide varying degrees of redundancy and fault tolerance. Instead of storing valuable data on a single hard disk that could fail at any time, RAID


Glossary

makes sure a backup copy of all information always exists by spreading data among multiple hard disks.

Read Hit Data requested by the read operation is in cache.

Read Miss Data requested by the read operation is not in cache.

Redundant Backup arrays, drives, disks or power supplies that duplicate functions performed elsewhere.

Remote Backup Celerra File Server backup procedure that is initiated from a remote workstation. This procedure creates a backup copy of a file system or incremental changes to a file system on a tape library unit that may be attached to a server other than the originating Data Mover. Depending on the type of remote backup, the data may or may not traverse the network. See also, Automated Local Backup and Restore and Automated Network Backup and Restore.

Router Device that transfers information between networks, and determines the most efficient route for it to follow.

Routing InformationProtocol (RIP)

Allows a server to query for the best route to reach an internet address.

SScrubbing Process of reading, checking the error correction bits, and writing

corrected data back to the source.

SCSI Small Computer System Interface. The standard set of protocols for host computers communicating with attached peripherals. SCSI allows connection to as many as six peripherals including printers, scanners, hard drives, zip drives, and CD-ROM drives.

SCSI Adapter Card in the Symmetrix subsystem that provides the physical interface between the disk director and the disk devices.

SCSI bus A parallel bus that carries data and control signals from SCSI devices to an SCSI controller.

Security AccessManager (SAM)

Authenticates users to use resources on the network.


g-14

Glossary

Security Descriptor(SD)

Descriptor, associated with a file that includes the owner and the group SID for the ACL.

Security Identifier (SID) Unique identifier that defines a user or group on Windows NT. Each user or group has its own SID.

Server Back-end device that handles requests made by hosts connected through a network.

Server Message Block(SMB)

Protocol used by CIFS that has been enhanced for use on the Internet to request file, print, and communication services from a Data Mover over the network. CIFS uses SMB to provide secure file access and transfer to many types of hosts such as LANs, Intranets, and the Internet. The SMB protocol is an open, cross-platform protocol for distributed file sharing, and it is supported by Windows 95, Windows 98, and Windows NT.

Short Miss Data requested is not in cache, but is in the process of being fetched.

Simple Local Backup See Manual Local Backup.

Simple NetworkManagement

Protocol (SNMP)

An application protocol developed in the mid 1980s to manage network communications in the Internet Protocol suite. SNMP controls the MIB database. It is most commonly employed using TCP/IP protocols.

Slice Volume Logical piece or specified area of a volume used to create smaller, more manageable units of storage.

Standby User-defined state that indicates the mode of a physical I/O path. A standby path is held in reserve against failure. No I/O is sent over a standby path while the power device can access an available active path.

Storage Device Physical device that can attach to a SCSI device, which in turn connects to the SCSI bus.

Storage Processor (SP) A printed-circuit board with processor memory modules and control logic that manages the FC4700-2 storage system I/O between the server Fibre Channel adapter and the disk modules.

String Series of connected disk devices sharing the same disk director. Also a contiguous series of alphanumeric characters.


Glossary

Stripe Volume Arrangement of volumes that appear as a single volume. Allows for stripe units, which cut across the volume and are addressed in an interlaced manner. Stripe Volumes make load balancing possible.

Switch A network device that selects a path or circuit for sending a data between destinations.

Also, a Fibre Channel device used to connect devices (e.g., computer servers and storage systems) into a Fibre Channel fabric.

TTape Library Unit Physical device that contains and manages multiple magnetic tape

units accessible as a unit.

Target Middle part of a SCSI address. Target numbers are assigned from 0 through 7.

Telnet As the Internet standard protocol for remote terminal connection, Telnet allows a user at one site to interact with a remote device or system that expects terminal-mode traffic.

Terabyte 2 to the 40th power (1,099,511,627,776) bytes, or approximately 1 trillion bytes. Measured as TB.

Thread Sequential flow of control. A thread consists of address space, a stack, local variables, and global variables.

Throughput In computers, it is a measurement of the amount of work that can be processed within a set time period. In networking, it is a measurement of the amount of data that can be successfully transferred with a set time period.

Transmission ControlProtocol (TCP)

Transport protocol that provides connection-oriented transport services in the Internet suite of protocols. TCP/IP is used in network communications routing and data transfer, and it is the accepted standard for UNIX-based operating systems and the Internet.

UUNIX File System (UFS) Standard UNIX File System.


g-16

Glossary

UxFS High-performance, Celerra File Server-default file system, based on traditional Berkeley UFS, enhanced with 64-bit support, metadata logging for high availability and several performance enhancements.

VVolume A virtual disk into which a file system, database management system

or other application places data. A volume can be a single disk partition or multiple partitions on one or more physical drives.

Volume Management Capability of optimizing disk storage with features that provide greatest accessibility, capacity, and reliability for the client.

WWide Area Network

(WAN)Private or public network that covers a wide geographical area.

Window InternetName Service (WINS)

A name resolution system that determines the IP address associated with a particular network computer. WINS provides the mapping between the machine name and the Internet address, allowing Microsoft networking to function over TCP/IP networks.

Windows NT Domain Grouping of computers sharing a common security scheme.

Write Hit Existence of room in cache for the data presented by the write operation.

Write Miss Lack of room in cache for the data presented by the write operation.

ZZones Several devices are grouped by function or by location. All devices

connected to a connectivity product may include configuration of one or more zones. Devices in the same zone can see each other; devices in different zones cannot.


Index

AAccess

control levelcreating accounts 9-10defining privileges 9-10nas_acl 9-10

local 3-5remote 3-5restricting 6-6rights

enabling 6-14Access Control List (ACL) 9-9ACL 9-9

access control values 9-11ACL Table

creating 9-10example 9-13

Adapter, Fibre Channel 1-11, 1-19, 1-22Addressing within a meta volume 5-10Advisory lock 6-6ANSI Fiber Channel Class 3 service 1-21Architecture

hardware 1-8independent Data Mover/Control Station

1-5Assigning an IP address 4-2Authentication

NFS user 6-3PC clients

NFS 6-11using DNS 4-7

Automount mapcreating 8-2

BBenefits, Celerra File Server 1-5Business continuance volumes (BCVs),

configuration 5-13

CCall Home support 1-20CallHome 1-26Call-In support 1-20Capacity

checking file system 8-6Data Mover 8-6volume 9-5

Capacity (fan-out) topology 1-23CD-ROM drive 1-20Celerra cabinet

emergency shutdown 3-8planned power down 3-6powering up 3-2

Celerra File Serverdata availability 1-5display panel 1-11environment 1-27expanding storage capacity 5-11features and benefits 1-5Fibre Channel switches 1-25functionality 1-11hardware 1-15hardware architecture 1-11high availability 1-11managing 1-12network and storage requirements 2-1number of Data Movers 1-6

Celerra File Server Basic Administration Guide i-1

i-2

Index

operations 1-11overview 1-2performance and capacity 1-4protocols 1-28self-diagnostic/self-reporting capability 1-6software components 1-26

Celerra File Server cabinet 1-8internal view 1-15single cabinet model 1-8two-cabinet models 1-8

Celerra File Server interface 1-11Celerra File Server Manager

GUI 1-29requirements 1-30

Celerra Monitor 1-29minimum configuration 1-31software 1-12

CIFS 1-7, 1-27, 1-28compatibility with NFS 1-7configuring clients 1-36, 6-2deleting service 9-2

Class 3, switched fabric 1-25COMM board 1-20Command Line Interface

character parameters 3-4local access 3-4logging in 3-5remote access 3-4

Common Internet File System SeeCompatibility, NFS/CIFS 1-7Component repair, nondisruptive 1-6Configuring

standby Data Movers 7-2time services 4-9

Connectivity, Fibre Channel 1-25Console Multiplexer 1-20Consolidation (fan-in) topology 1-23Control Station

dual 1-5dual configuration 7-15enabling daemons 10-3front view 1-16halting locally 10-7nas database 10-1primary 10-5, 10-7primary and secondary 1-15rebooting locally 10-5

remotelyhalting 10-8rebooting 10-6

secondary 10-5, 10-7slots (component positions) 1-17software 1-26

Creatingautomount map 8-2file system 5-15stripe volume 5-7volume configurations 5-2

Customer support B-3Customer Support Center B-5

DDaemon

Control Station 10-3httpd 10-4nas 10-4ntp 10-3

Data Access in Real Time (DART) software 1-26Data availability 2-4Data Mover

characteristics 1-17checking free space 8-6checking log files 11-11checking system capacity 8-6configuring for standby operations 7-2creating a mount point 5-16current log file 11-11determining the number required 2-4error messages 11-7failover 2-4free space 8-6front view 1-18halting 9-4mapping volumes to 2-5operations 1-11reboot 9-4restoring from standby 7-12slots (component positions) 1-19software 1-26standby 2-4troubleshooting 11-7typical configuration 2-6

Database


Index

Control Station 10-1Deleting

CIFS service 9-2disk volume 9-7file system 8-14meta volume 9-7slice volume 9-7stripe volume 9-7

Dial-in support 1-26Discovering SCSI devices 9-2Disk volume

deleting 9-7renaming 9-6

Displaying mounted file systems 8-4DNS

authentication 4-7server 4-7

Dual Control Station 1-5, 1-26, 7-15

EE_Port, Fibre Channel 1-22Emergency shutdown 3-8Enabling

access rights 6-14EPO Box 1-19, 3-2Error messages

Data Mover 11-7file system 11-5post-install 11-2server_export 6-9volume 11-4

Ethernetfast 1-6gigabit 1-6

Ethernet channel 1-19Export

optionsNFS 6-8

Extendingfile system 8-7meta volume 9-5

FF_Port, Fibre Channel 1-22Failover

example 7-5

policy types (table) 7-8Fan-in topology 1-23Fast Ethernet 1-6, 4-2Features, Celerra File Server 1-5Fibre Channel 1-21

adapter 1-11, 1-15, 1-19, 1-22connectivity 1-25on Celerra File Server 1-22port types 1-22standards 1-22supported switches 1-25switched environment 1-22switched fabric 1-22, 1-24topology 1-22tutorial (url) 1-25zones 1-24

Fibre Channel Director (FA) N_port 1-23File locking

NFS 6-6File system

capacity 2-3checking capacity 8-6creating 5-15deleting 8-14displaying mounted 8-4error messages 11-5extending 8-7inodes 8-6mirroring 5-13mounting 6-6permanent

mount 6-7providing user access rights 6-11read-only option 6-6read-write option 6-6renaming 8-9troubleshooting 11-5unexporting 6-14unmount all 8-5

File Transfer Protocol See FTPFlat panel display 1-11Free space

checking Data Mover 8-6FTP

over TCP 1-12use with Celerra File Server 1-28

i-3Celerra File Server Basic Administration Guide

i-4

Index

GG_Port, Fibre Channel 1-22GIDs 32-bit

creating 8-14overview 8-12restrictions 8-13setting 8-14

Gigabit Ethernet 1-6

HHalting

Control Stationlocally 10-7remotely 10-8

Data Mover 9-4Hardware

architecture 1-8multi-cabinet enclosure 1-10single enclosure 1-8

High availability and Data Movers 1-11httpd daemons 10-4

II/O access through Data Movers 2-5Independent Data Mover/Control Station

architecture 1-5Initially 4-2Inodes 8-6Installation

configuring Data Movers 2-4configuring standby Data Movers 2-4mapping volumes to Data Movers 2-5storage requirements 2-3

IP address, internal Ethernet NIC 1-17, 1-19

LLinux operating system 1-26Local access

Command Line Interface 3-4logging in 3-5

Lockadvisory (NFS) 6-6

locking, file 6-6Logging in 3-5Logical paths 1-22

MManaging

Celerra File Server 1-12system 9-2

Mapping volumes to file systems 2-5Meta volume

configuring 5-9deleting 9-7extending 9-5renaming 9-6

Mirrored file system 5-13Modem connections 1-20Monitoring network statistics 11-12Monitoring server operations

with SNMP MIB-II 1-12Mount point

creating 5-16Mounting a file system path 6-6

NN_Port, Fibre Channel 1-22nas Daemon 10-4nas database

backup 10-1Control Station 10-1

nas_acl 9-10Network

administrationmonitoring statistics 11-12

interfacesassigning an IP address 4-2

Network and storage requirements 2-1Network file sharing protocols 1-27Network File System See NFSNetwork topologies

capacity 2-4NFS 1-7, 1-28

accessfor PC clients 6-11

and CIFS compatibility 1-4, 1-7configuration overview 6-3configuring clients 1-36, 6-2environment 6-3export options 6-8protocol 6-3standards supported 1-12


Index

typical configuration 6-4user authentication 6-3

NICcharacteristics 4-2types 4-2

Nondisruptive component repair, Celerra 1-6NTP

daemon 10-3

PParameters

file format 9-15server 9-19system 9-15

PC clientsproviding NFS access to 6-11

Planned power down 3-6Power supplies 1-19Primary Control Station 1-15, 10-5, 10-7Privileges

access control levels 9-10nas_acl 9-10

ProtocolNFS 6-3

RRAID storage usage 2-3Reason codes

Control Station 10-5, 10-7Reboot/recovery, Celerra File Server 1-5Rebooting

Control Stationlocally 10-5remotely 10-6

Data Movers 9-4Recommended fan-in ratio 1-24Redundant

components 1-6Redundant connections, Fibre Channel 1-25Remote access

Command Line Interface 3-4Renaming

disk volume 9-6file system 8-9meta volume 9-6slice volume 9-6

stripe volume 9-6Restoring

from standby 7-12Rules and restrictions

standby Data Movers 7-2

SSCSI connection to Data Movers 1-11, 1-12Secondary Control Station 1-15, 10-5, 10-7Self-diagnostic/self-reporting capability 1-6Server connections to the network 1-6Server parameters 9-19Single adapter, capacity topology 1-23Slice volume 5-3

deleting 9-7renaming 9-6

SNMP MIB-IImonitoring server operations 1-12

Software components 1-26Standby

restoring 7-12Standby Data Mover 2-4

failover policies 7-8feature 1-5rules and restrictions 7-2

Storage needscalculating 2-3

Storage protectionFC4700-2 2-3Symmetrix 2-3

Stripe volume 5-5creating 5-7deleting 9-7renaming 9-6

Switched fabricconfiguring with Celerra 1-25Fibre Channel 1-22, 1-24

System management 9-2System parameters 9-15

TTechnical support B-3Time services

configuring 4-9Topology

Fibre channel 1-22

i-5Celerra File Server Basic Administration Guide

i-6

Index

physical and logical 1-22Troubleshooting

CIFS 11-4Data Mover 11-7file system 11-5volume 11-4

UUnexport limitations 6-14Unexporting file systems 6-14Unmounting

all file systems 8-5User

access rightsfile system 6-11

UxFS 1-27, 1-28

VVolume

capacity, checking 9-5configurations

creating 5-2error messages 11-4management

creating a stripe volume 5-7troubleshooting 11-4

VolumesBCV configuration 5-13expanding 5-11meta volume addressing 5-10meta volume configuration 5-9slice volume configuration 5-3, 5-6stripe volume performance 5-5types (table) 5-2

ZZones, Fibre Channel 1-24


Documents

Celerra Basic Administrator Guide