celerra for hp-ux, aix, and solaris clients · configuring the clariion using cli commands ......

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® Celerra® MPFS over FCfor HP-UX, AIX, and Solaris Clients

Version 4.0

Product GuideP/N 300-002-870

REV A04

EMC Celerra MPFS over FC for HP-UX, AIX, and Solaris Clients Version 4.0 Product Guide2

Copyright © 2007-2010 EMC Corporation. All rights reserved.

Published January 2010

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.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on the EMC Powerlink website.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Contents

Preface

Chapter 1 Introducing EMC Celerra MPFS over FCOverview of EMC Celerra MPFS over FC..................................... 18EMC Celerra MPFS architectures ................................................... 19

EMC Celerra MPFS over Fibre Channel................................. 19MPFS configuration summary................................................. 21

How EMC Celerra MPFS works..................................................... 22

Chapter 2 MPFS Environment ConfigurationConfiguration roadmap ................................................................... 24Implementation guidelines.............................................................. 26

Celerra with MPFS recommendations.................................... 26Storage configuration recommendations ............................... 28MPFS feature configurations.................................................... 29

MPFS installation and configuration process ............................... 30Configuration planning checklist............................................ 31

Verifying system components ......................................................... 32Required hardware components ............................................. 32Required software components ............................................... 33Verifying configuration............................................................. 33Verifying storage array requirements ..................................... 34Verifying the Fibre Channel switch requirements (FC configuration) ..................................................................... 36Verifying the IP-SAN CLARiiON CX3 or CX4 requirements............................................................................... 37

Setting up the Celerra Network Server ......................................... 38Setting up the file system................................................................. 39

EMC Celerra MPFS over FC for HP-UX, AIX, and Solaris Clients Version 4.0 Product Guide 3

Contents

Before creating a file system .................................................... 39Creating a file system on a Celerra Network Server ............ 40

Enabling MPFS for the Celerra Network Server .......................... 46Configuring the CLARiiON using CLI commands ..................... 47

Best practices .............................................................................. 47Configuring the SAN and storage.................................................. 48

Installing the Fibre Channel switch (FC configuration) ...... 48Zoning the SAN switch (FC configuration)........................... 48Enabling SP A and SP B FC interfaces (FC configuration) .. 49Creating a security file on the Celerra Network Server....... 49Access Logix configuration...................................................... 50Configuring the storage system for PowerPath.................... 52

Installing PowerPath ........................................................................ 56Installing the MPFS software .......................................................... 57

Operating MPFS through a firewall ....................................... 57Configuring and accessing storage ................................................ 58

Installing the Fibre Channel driver (FC configuration) ....... 58Mounting the MPFS file system ..................................................... 61

Chapter 3 Installing PowerPath with MPFSPowerPath overview ........................................................................ 64Before installing ................................................................................ 66Locating PowerPath patches........................................................... 69Installing PowerPath ........................................................................ 70

Related documentation............................................................. 70

Chapter 4 Installing the MPFS Software on an HP-UX ServerBefore installing ................................................................................ 72

MPFS software ........................................................................... 72Storage array .............................................................................. 73

Installing the MPFS software .......................................................... 74Before installing ......................................................................... 74Recognizing storage system devices....................................... 75Mounting the CD....................................................................... 76Installing the MPFS software from a CD ............................... 76Installing the MPFS software from a tar file .......................... 77Post-installation check .............................................................. 79Verifying the installation on an HP-UX server...................... 80Unmounting and removing the CD........................................ 80

Migrating from an earlier release ................................................... 81Uninstalling the MPFS software..................................................... 82


Contents

Chapter 5 Installing the MPFS Software on an AIX ServerBefore installing................................................................................. 86

MPFS software............................................................................ 86Storage array............................................................................... 87

Installing the MPFS software........................................................... 88Before installing.......................................................................... 88Mounting the CD ....................................................................... 88Installing the MPFS software from a CD................................ 89Installing the MPFS software from a tar file .......................... 90

After installing................................................................................... 92Verifying the installation on an AIX server............................ 92Mounting a MPFS file system on an AIX server ................... 93

Migrating from an earlier release.................................................... 94Uninstalling the MPFS software ..................................................... 96

Chapter 6 Installing the MPFS Software on a Solaris ServerBefore installing................................................................................. 98

MPFS software............................................................................ 98Storage system............................................................................ 99Label disks ................................................................................ 100

Installing the MPFS software......................................................... 101Before installing........................................................................ 101Installing the MPFS software from a CD.............................. 102Installing the MPFS software from a tar file ........................ 105

After installing................................................................................. 109Verifying the installation on a Solaris server ....................... 109

Migrating from an earlier release.................................................. 110Uninstalling the MPFS software ................................................... 111

Chapter 7 MPFS Command Line InterfaceOverview of the command line interface .................................... 114Mounting an MPFS file system ..................................................... 115Resuming I/O through MPFS ....................................................... 117Displaying mpfsctl commands ..................................................... 118Setting the number of blocks to prefetch ..................................... 119Resetting the counters .................................................................... 120Enabling read/write interception (Solaris only) ........................ 121Displaying statistics ........................................................................ 122

Understanding the statistics output ...................................... 123Improving client read performance (HP-UX 11.31 only) .......... 124Setting synchronization before using noac (AIX only) .............. 125

5EMC Celerra MPFS over FC for HP-UX, AIX, and Solaris Clients Version 4.0 Product Guide

Contents

Displaying the MPFS version number......................................... 126Displaying the disk quota ............................................................. 127Displaying MPFS devices .............................................................. 128

Appendix A Error Messages and TroubleshootingHP-UX server error messages....................................................... 132Troubleshooting the HP-UX server .............................................. 133

Mounting and unmounting ................................................... 133MPFS software ......................................................................... 136Miscellaneous........................................................................... 137

Troubleshooting the AIX server.................................................... 138Uninstalling .............................................................................. 138Mounting and unmounting ................................................... 140Miscellaneous........................................................................... 144

Troubleshooting the Solaris server............................................... 147Mounting and unmounting ................................................... 147MPFS software ......................................................................... 151Miscellaneous........................................................................... 153

Glossary

Index


Title Page

Figures

1 Celerra unified storage with Fibre Channel ............................................... 202 Celerra gateway with Fibre Channel........................................................... 203 Configuration roadmap................................................................................. 254 Configuring CLARiiON for PowerPath...................................................... 54


Figures


Title Page

Tables

1 MPFS configuration summary ...................................................................... 212 Data Mover capacity guidelines.................................................................... 273 Prefetch and read cache requirements ......................................................... 284 HP-UX, AIX, or Solaris server firewall ports .............................................. 575 Correct arraycommpath and failovermode settings .................................. 586 Summary of PowerPath versions and features........................................... 657 Command Line Interface summary............................................................ 1148 HP-UX server error messages ..................................................................... 132


Tables


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases versions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Important Check the EMC Powerlink website, http://Powerlink.EMC.com, to ensure you have the latest versions of the MPFS software and documentation. For software, open Support > Software Downloads and Licensing > Downloads C > Celerra MPFS Client for UNIX and then select the necessary software for MPFS from the menu.

For documentation, open Support > Technical Documentation and Advisories > Software ~C~ Documentation > Celerra MPFS over Fibre Channel.

Note: You must be a registered EMC Powerlink website user to download the MPFS software.


12

Preface

Audience This document is part of the EMC Celerra MPFS documentation set, and is intended for use by system administrators responsible for installing and maintaining HP-UX, AIX, or Solaris servers.

Readers of this document are expected to be familiar with the following topics:

◆ EMC Symmetrix or CLARiiON storage system

◆ EMC Celerra Network Server

◆ NFS protocol

◆ Operating environments to install the server include HP-UX, AIX, or Solaris

Relateddocumentation

Related documents include:

◆ EMC Celerra MPFS for HP-UX and Solaris Clients Release Notes

◆ EMC Celerra MPFS for AIX Clients Release Notes

◆ EMC Host Connectivity Guide for HP-UX

◆ EMC Host Connectivity Guide for AIX

◆ EMC Host Connectivity Guide for Sun Solaris

◆ EMC documentation for HBAs

PowerPath

◆ PowerPath for UNIX Installation and Administration Guide

◆ PowerPath for HP-UX Release Notes

◆ PowerPath for AIX Release Notes

◆ PowerPath for Solaris Release Notes

CLARiiON storage system

◆ Removing ATF or CDE Software before Installing other Failover Software

◆ EMC Navisphere Manager Administrator’s Guide and online help

Symmetrix storage system

◆ Symmetrix product manual

EMC Celerra MPFS over FC for HP-UX, AIX, and Solaris Clients Version 4.0 Product Guide

Preface

Celerra Network Server

◆ EMC Celerra Network Server Documentation CD

◆ Using MPFS on Celerra

All of these publications can be found on the EMC Powerlink website.

Powerlink The EMC Powerlink website provides the most up-to-date information on documentation, downloads, interoperability, product lifecycle, target revisions, and bug fixes. As a registered EMC Powerlink website user, you can subscribe to receive notifications when updates occur.

E-Lab InteroperabilityNavigator

The EMC E-Lab Interoperability Navigator tool provides access to EMC interoperability support matrices. After logging in to the EMC Powerlink website, go to Support > Interoperability and Product Lifecycle Information > E-Lab Interoperability Navigator.

Conventions used inthis document

EMC uses the following conventions for special notices.

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

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to operation of the 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 message.


14

Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold: Used for:• Specific user input (such as commands)

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to Powerlink and select Support. On the Support page, you can access Support Forms, request a product enhancement, talk directly to an EMC representative, or open a service request. To open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]


http://Powerlink.EMC.com

16

Preface


1

This chapter provides an overview of EMC Celerra MPFS over FC and its architecture. This chapter includes the following topics:

◆ Overview of EMC Celerra MPFS over FC...................................... 18◆ EMC Celerra MPFS architectures .................................................... 19◆ How EMC Celerra MPFS works ...................................................... 22

Introducing EMCCelerra MPFS over FC

Introducing EMC Celerra MPFS over FC 17

18

Introducing EMC Celerra MPFS over FC

Overview of EMC Celerra MPFS over FCEMC® Celerra® Multi-Path File System (MPFS) over Fibre Channel (FC) lets Linux, Windows, UNIX, AIX, or Solaris servers access shared data concurrently over FC connections.

EMC Celerra MPFS uses common IP LAN topology to transport metadata for the EMC Celerra MPFS.

Without the MPFS file system, servers can access shared data using standard Network File System (NFS) or Common Internet File System (CIFS) protocols; the MPFS file system accelerates data access by providing separate transports for file data (file content) and metadata (control data).

For an FC-enabled server, data is transferred directly between the HP-UX, AIX, or Solaris server and storage array over a Fibre Channel SAN.

Metadata passes through the Celerra Network Server (and the IP network), which includes the NAS portion of the configuration.



EMC Celerra MPFS architecturesThe EMC Celerra MPFS over Fibre Channel architecture consists of two configurations:

◆ Celerra unified storage with Fibre Channel (NS20FC, NS-120, NS40FC, NS-480, or NS-960)

◆ Celerra gateway with Fibre Channel (NS40G, NS80G, NS-G2, NS-G8, or NSX) Celerra with EMC CLARiiON® or EMC Symmetrix®

Each is briefly described in this section.

EMC Celerra MPFS over Fibre Channel

The EMC Celerra MPFS over Fibre Channel architecture consists of the following:

◆ Celerra Network Server with MPFS — A network attached storage device that is configured with an EMC Celerra Network Server with MPFS software

◆ Symmetrix or CLARiiON storage array◆ HP-UX, AIX, or Solaris server with MPFS software connected to a

Celerra Network Server through the IP LAN, Symmetrix, or CLARiiON storage arrays using Fibre Channel architecture

The following figures show the common Fibre Channel configurations. Figure 1 on page 20 shows the Celerra unified storage with Fibre Channel configuration where the HP-UX, AIX, or Solaris servers are connected to an NS20FC, NS-120, NS40FC, NS-480, or NS-960 using an IP switch and one or more FC switches. In a smaller configuration of one or two servers, the servers can be connected directly to the NS20FC or NS-120 without the use of Fibre Channel switches.

EMC Celerra MPFS architectures 19

20


Figure 1 Celerra unified storage with Fibre Channel

Figure 2 on page 20 shows the supported Celerra gateway with Fibre Channel configuration. In this diagram, the HP-UX, AIX, or Solaris servers are connected to a CLARiiON or a Symmetrix storage array using an NS40G, NS80G, NS-G2, NS-G8, or NSX and IP switch or optional Fibre Channel switch.

Figure 2 Celerra gateway with Fibre Channel

IP switch

FC switch

FC

NFS/CIFS

NS20FC, NS-120, NS40FC,NS-480, or NS-960

MPFS data

Servers

CNS-001629

MPFS metadata

IP switch

NS40G, NS80G, NS-G2,NS-G8, or NSX

FC switch

FC

FC

NFS/CIFS

CLARiiON or Symmetrix

MPFS data

Servers

CNS-001097

MPFSmetadata



MPFS configuration summary

Table 1 on page 21 compares the MPFS configurations.

Table 1 MPFS configuration summary

Figure Configuration Price/size

Maximum servers supported

Storage system

Max number of arrays

1 Celerra unified storage with Fibre Channel (NS20FC)

Entry-level 60 CLARiiON CX3-10F

1

Celerra unified storage with Fibre Channel (NS-120)

Entry-level 120a CLARiiON CX4-120

Celerra unified storage with Fibre Channel (NS40FC)

Midtier 120 CLARiiON CX3-40F


Midtier 240b CLARiiON CX4-480


High-end 500c CLARiiON CX4-960

2 Celerra gateway with Fibre Channel (NS40G, NS80G, NS-G2, NS-G8, or NSX)

High-end Dependent on CLARiiON and Symmetrix limitsa, b, c

CLARiiON CX300, CX500,CX700, CX3-20F, CX3-40F, CX4-120, CX4-240, CX4-480, CX4-960, Symmetrix DMX™ series, Symmetrix V-Max™ series, or Symmetrix 8000 series

4

a. 240 Linux Servers are supported with EMC FLARE® release 29 or later.

b. 1020 Linux Servers are supported with FLARE release 29 or later.

c. 4080 Linux Servers are supported with FLARE release 29 or later.

EMC Celerra MPFS architectures 21

22


How EMC Celerra MPFS worksAlthough called a file system, the EMC Celerra MPFS is neither a new nor a modified format for storing files. Instead, the MPFS file system interoperates and uses the standard NFS and CIFS protocols to enforce access permissions. The MPFS file system uses a protocol called File Mapping Protocol (FMP) to exchange metadata between the HP-UX, AIX, or Solaris server and the Celerra Network Server.

All requests unrelated to file I/O pass directly to the NFS/CIFS layer. The MPFS layer intercepts only the open, close, read, and write system calls.

When an HP-UX, AIX, or Solaris server intercepts a file-read call, it sends a request to the Celerra Network Server asking for the file's location. The Celerra Network Server responds with a list of file extents, which the HP-UX, AIX, or Solaris server then uses to read the file data directly from the disk.

When an HP-UX, AIX, or Solaris server intercepts a file-write call, it asks the Celerra Network Server to allocate blocks on disk for the file. The Celerra Network Server allocates the space in contiguous extents and sends the extent list to the HP-UX, AIX, or Solaris server. The HP-UX, AIX, or Solaris server then writes data directly to disk, informing the Celerra Network Server when finished, so that the Celerra Network Server can permit other HP-UX, AIX, or Solaris server to access the file.

The remaining chapters describe how to install, manage, and tune HP-UX, AIX, or Solaris servers. The Using MPFS on Celerra technical module, located on the EMC Celerra Network Server Documentation CD and also available on the EMC Powerlink® website at http://Powerlink.EMC.com, provides information on the Celerra Network Server MPFS commands.


2Invisible Body Tag

This chapter presents a high-level overview of configuring and installing EMC Celerra MPFS.

Topics include:

◆ Configuration roadmap .................................................................... 24◆ Implementation guidelines............................................................... 26◆ MPFS installation and configuration process ................................ 30◆ Verifying system components .......................................................... 32◆ Setting up the Celerra Network Server........................................... 38◆ Setting up the file system.................................................................. 39◆ Enabling MPFS for the Celerra Network Server ........................... 46◆ Configuring the CLARiiON using CLI commands ...................... 47◆ Configuring the SAN and storage ................................................... 48◆ Installing PowerPath ......................................................................... 56◆ Installing the MPFS software ........................................................... 57◆ Configuring and accessing storage ................................................. 58◆ Mounting the MPFS file system....................................................... 61

MPFS EnvironmentConfiguration

MPFS Environment Configuration 23

24

MPFS Environment Configuration

Configuration roadmapFigure 3 on page 25 shows the roadmap for configuring and installing the EMC Celerra MPFS FC architecture for FC environments. The roadmap contains the topics representing sequential phases of the configuration and installation process. The descriptions of each phase, which follow, contain an overview of the tasks required to complete the process, and a list of related documents where you can find more information.



Figure 3 Configuration roadmap

!

MPFS installation and configuration process

Verifying system components

Setting up the file system

Implementation guidelines

Enabling MPFS for the Celerra Network Server

Setting up the Celerra Network Server

Installing PowerPath

Configuring the CLARiiON using CLI commands

Configuring the SAN and storage

Configuring and accessing storage

Mounting the MPFS file system

Installing the MPFS software

Configuration roadmap 25

26


Implementation guidelinesThe following MPFS implementation guidelines are valid for all MPFS installations.

Celerra with MPFS recommendations

These recommendations are described in the Celerra Network Server Best Practices for Performance White Paper, which can be found at http://Powerlink.EMC.com:

◆ MPFS is optimized for large I/O transfers and may be useful for workloads with average I/O sizes as small as 16 KB. However, MPFS has been shown conclusively to improve performance for I/O sizes of 128 KB and greater.

◆ For best MPFS performance, in most cases, configure your Celerra volumes using a volume stripe size of 256 KB.

◆ EMC PowerPath® is required for path failover in a CLARiiON environment. Knowledgebase article emc 165953 contains details on using PowerPath and MPFS.

◆ When MPFS is started, 16 threads are run, which is the default number of MPFS threads. The maximum number of threads is 128. If system performance is slow, gradually increase the number of threads allotted for the Data Mover to improve system performance. Add threads conservatively, as the Data Mover allocates 16 KB of memory to accommodate each new thread. The optimal number of threads depends on the network configuration, the number of HP-UX, AIX, or Solaris servers, and the workload.

Using MPFS on Celerra provides the procedures necessary to adjust the thread count and can be found on the EMC Celerra Network Server Documentation CD.



128 TB Data Movercapacity

MPFS supports 128 TB total capacity per Data Mover. This larger Data Mover capacity allows a single 128 TB data access point through the Nested Mount File System (NMFS). Table 2 on page 27 lists the conditions and restrictions of the 128 TB Data Mover capacity.

Additional guidelines are listed below:

◆ EMC Celerra Replicator™ and Celerra SnapSure are not supported with the 128 TB Data Mover capacity. Existing snaps and replication sessions must be deleted when using MPFS with 128 TB Data Mover capacity. If you plan to use Celerra Replicator or Celerra SnapSure, the Data Mover capacity will be the same as the non-MPFS capacity limits.

◆ The 128 TB Data Mover capacity is only supported with MPFS running in an NS-960 or NSX environment.

◆ The Celerra Network Server must be configured for MPFS. However, CIFS, MPFS, and NFS servers can all connect to share file systems.

◆ Single file system size is limited to 16 TB.

◆ Performance is no different during data transfer or Data Mover bootup time when using 128 TB Data Movers from any other Data Mover capacity.

The EMC E-Lab™ Interoperability Navigator contains the latest Data Mover capacity information and MPFS-related restrictions.

Table 2 Data Mover capacity guidelines

MPFS with FC or ATA Conditions and restrictions NS-960 or NSX

Limit per Data Mover/Blade

Minimum NAS version required

5.5.31.x

Data Mover capacity 128 TB

Existing snaps and replication sessions

Must be deleted

New EMC SnapSure™ or replicator sessions

Not supported

Implementation guidelines 27

28


HP-UX, AIX, or Solarisserver configuration

All servers using the MPFS software require:

◆ At least one Fibre Channel connection to a SAN switch, or directly to a CLARiiON or Symmetrix storage array

◆ Network connections to the Data Mover

Storage configuration recommendations

HP-UX, AIX, or Solaris servers read and write directly from a storage system. This has several implications:

◆ FLARE release 26 or later should be used for best performance in new MPFS configurations. The EMC CLARiiON Best Practices for Fibre Channel Storage: FLARE Release 26 Firmware Update provides more details.

◆ All mounted MPFS file systems should be unmounted from the HP-UX, AIX, or Solaris server before changing any storage device or switch configuration.

◆ Table 3 on page 28 lists the prefetch and read cache requirements.

Table 3 Prefetch and read cache requirements

Prefetch requirement Read cache Notes

Modest 50–100 MB 80% of the systems fall under this category.

Heavy 250 MB Requests greater than 64 KB and sequential reads from many LUNs expected over 300 MB/s.

Extremely heavy 1 GB 120 or more drives reading in parallel.



MPFS feature configurations

The following sections describe the configurations for MPFS features.

CHAP authentication The HP-UX, AIX, or Solaris server with MPFS software and the CLARiiON storage array support the Challenge Handshake Authentication Protocol (CHAP) for network security.

CHAP provides a method for the HP-UX, AIX, or Solaris server and CLARiiON storage array to authenticate each other through an exchange of a shared secret (a security key that is similar to a password), which is typically a string of 12 to 16 bytes.

CAUTION!If CHAP security is not configured for the CLARiiON storage array, any computer connected to the same IP network as the CLARiiON storage array ports can read from or write to the CLARiiON storage array.

CHAP has two variants—one-way and reverse CHAP authentication:

◆ In one-way CHAP authentication, CHAP sets up the accounts that the HP-UX, AIX, or Solaris server uses to connect to CLARiiON storage array. The CLARiiON storage array authenticates the HP-UX, AIX, or Solaris server.

◆ In reverse CHAP authentication, the CLARiiON storage array authenticates the HP-UX, AIX, or Solaris server and the HP-UX, AIX, or Solaris server also authenticates the CLARiiON storage array.

Because CHAP secrets are shared between the HP-UX, AIX, or Solaris server and CLARiiON storage array, the CHAP secrets must be configured the same on both the HP-UX, AIX, or Solaris server and CLARiiON storage array.

Implementation guidelines 29

30


MPFS installation and configuration processThe MPFS configuration process involves performing tasks on various system components in a specific order.

Note: This document contains guidelines for installing and configuring MPFS with several options. Disregard steps that do not pertain to your environment.

To manually install and configure MPFS:

1. Collect installation and configuration planning information and complete the checklist:

a. Collect the IP network addresses, Fibre Channel port addresses, and CLARiiON storage array information.

b. Map the Ethernet and TCP/IP network topology.

c. Map the Fibre Channel zoning topology.

d. Map the virtual storage area network (VSAN) topology.

2. Install the MPFS software manually (on a native or hosted HP-UX, AIX, or Solaris operating system):

a. Install the HBA driver (for FC configuration).

b. Install the MPFS software.

c. Check the MPFS software configuration.



Configuration planning checklist

Collect the following information before beginning the MPFS installation and configuration process.

For an FC configuration:

❑ SP A IP address .....................................................................................

❑ SP A login name....................................................................................

❑ SP A password ......................................................................................

❑ SP B IP address......................................................................................

❑ SP B login name ....................................................................................

❑ SP B password .......................................................................................

❑ Zoning for Data Movers ......................................................................

❑ First Data Mover LAN blade IP address or Data Mover IP address....................................................................................................

❑ Second Data Mover LAN blade IP address or Data Mover IP address....................................................................................................

❑ Control Station IP address or CS address .........................................

❑ LAN IP address (same as LAN Data Movers)..................................❑ HP-UX, AIX, or Solaris server IP address on LAN..........................

❑ VSAN name ...........................................................................................

❑ VSAN number (make sure it is not in use) .......................................

❑ SP A FC port assignment or FC ports ................................................

❑ SP B FC port assignment or FC ports.................................................❑ FC switch name.....................................................................................

❑ FC switch password .............................................................................

❑ FC switch port IP address....................................................................❑ Zoning for each FC HBA port.............................................................❑ Zoning for each FC director ................................................................

MPFS installation and configuration process 31

32


Verifying system componentsMPFS environments require standard EMC Celerra hardware and software, with the addition of a few components that are specific to FC configurations. This involves setting up an MPFS environment to verify that each of the previously mentioned components is in place and functioning normally. Each hardware and software component is discussed in the following sections.

Required hardware components

This section lists the MPFS configurations with the required hardware components.

MPFS Celerra unifiedstorage with Fibre

Channel configuration

The hardware components for an MPFS Celerra unified storage with Fibre Channel configuration are:

◆ A Celerra Network Server connected to an FC network and SAN

◆ An IP switch connected to the Celerra Network Server and servers for data and metadata

◆ An FC switch with an HBA for each HP-UX, AIX, or Solaris server

“EMC Celerra MPFS over Fibre Channel” on page 19 contains more information.

MPFS Celerragateway with Fibre

Channel configuration

The hardware components for an MPFS Celerra gateway with Fibre Channel configuration are:

◆ A Celerra Network Server connected to an FC network and SAN◆ A fabric-connected storage system, either CLARiiON or

Symmetrix, with available LUNs◆ An IP switch connected to the Celerra Network Server and the

servers for data and metadata

◆ An FC switch with an HBA for each HP-UX, AIX, or Solaris server

“EMC Celerra MPFS over Fibre Channel” on page 19 contains more information.

An HP-UX, AIX, or Solaris server with MPFS software is required for all types of configurations.



Configuring GigabitEthernet ports

For each HP-UX, AIX, or Solaris server for Fibre Channel, one NIC is required for NFS and FMP traffic. For maximum performance, use one port for the connection between the HP-UX, AIX, or Solaris server and Data Mover for MPFS metadata transfer and NFS traffic.

Configuring and Managing Celerra Networking provides detailed information for setting up network connections and is available on the Powerlink website.

Required software components

The following software components are required for an MPFS configuration:

Note: The EMC Celerra MPFS for HP-UX and Solaris Clients Release Notes and EMC Celerra MPFS for AIX Clients Release Notes provide a complete list of EMC supported operating system versions.

◆ Celerra Network Server NAS software version that supports FC configurations on HP-UX, AIX, or Solaris platforms.

◆ HP-UX, AIX, or Solaris operating system version that supports HBAs.

Note: The EMC E-Lab Interoperability Matrix lists the latest versions of HP-UX, AIX, or Solaris Server operating systems.

◆ MPFS software version 5.0 or later.

Verifying configuration

The next step in setting up MPFS is to verify whether each of the previously mentioned components is in place and functioning normally. If you know each of these components is operational, “MPFS installation and configuration process” on page 30 provides more information.


The following documents, available on the EMC Powerlink website, provide additional information:◆ Configuring and Managing EMC Celerra Networking

◆ Managing Celerra Volumes and File Systems Manually

◆ Configuring Standbys on Celerra

Verifying system components 33

34


Verifying storage array requirements

This section describes storage array requirements for an MPFS environment. The documents listed in “Related documentation” on page 35 detail storage array setup information.

Storage systemsrequirements

All CLARiiON storage arrays used within an MPFS environment must meet these requirements:

◆ Use only CX series storage arrays designed for MPFS file systems. The following models are supported:

• CX300

• CX500

• CX700

• CX3-10F

• CX3-20C/F

• CX3-40C/F

• CX3-80

• CX4-120

• CX4-240

• CX4-480

• CX4-960

◆ Ensure that all MPFS environments have file systems built on disks from only one type of storage system: either all Fibre Channel or all ATA drives.

◆ Ensure that MPFS does not use a file system spanning across two different storage array enclosures.

◆ Build Celerra LUNs using RAID 1, RAID 3, RAID 5, or RAID 6 only.

◆ Build Celerra Management LUNs using 4+1 RAID 5 only.

◆ Enable write cache.

◆ Use EMC Access Logix™.

◆ FLARE release 26 for high performance must be run with NAS 5.5.31.x or later.

Note: As of the FLARE 24 release, the CX series (excluding the CX300i and CX500i) supports jumbo frames.



All Symmetrix storage systems used within an MPFS environment must meet these requirements:

◆ Use only Symmetrix storage arrays designed for MPFS file systems. The following models are supported:

• Symmetrix 8000 series

• Symmetrix DMX series Enterprise Storage Platform (ESP)

• Symmetrix V-Max series

◆ Ensure that the correct version of the microcode is used. Contact your EMC Customer Support Representative or check the EMC E-Lab Interoperability Navigator for microcode release updates.

◆ Ensure that the Fibre Channel port flags are set for the MPFS file system. The Avoid_Reset_Broadcast (ARB) must be set for each port connected to a HP-UX, AIX, or Solaris server.

◆ Ensure that MPFS does not use a file system spanning across two different storage array enclosures.


The following documents, available on the EMC Powerlink website, provide additional information:

◆ Storage system’s rails and enclosures documentation





36


Verifying the Fibre Channel switch requirements (FC configuration)

Ensure the following to set up the Fibre Channel switch:

◆ Install the Fibre Channel switch.

◆ Check that the host bus adapter (HBA) driver is loaded.

◆ Connect cables from each HBA Fibre Channel port to a switch port.

◆ Verify the HBA connection to the switch by checking LEDs for the switch port connected to the HBA port.

◆ Configure zoning for the switch as described in “Zoning the SAN switch (FC configuration)” on page 48.

Note: Configure zoning as single initiator, meaning that each HBA port will have its own zone in which it is the only HBA port.


The documentation that ships with the Fibre Channel switch provides more information about the switch.



Verifying the IP-SAN CLARiiON CX3 or CX4 requirements

The EMC Celerra MPFS over FC environment with CLARiiON CX3 or CX4 series storage array configurations requires the following:

◆ For an unified storage configuration:

• Celerra Network Server NS20FC, NS-120, NS40FC, NS-480, or NS-960.

• CLARiiON CX3 or CX4 storage array.

◆ For a gateway configuration:

• Celerra Network Server NS40G, NS80G, NS-G2, NS-G8, or NSX.

• CLARiiON CX300, CX500, CX700, CX3, CX4, Symmetrix DMX, Symmetrix V-Max, or Symmetrix 8000 series storage array.

• Cabled as any shared storage system.

• Access Logix LUN masking is used to present all Celerra managed LUNs to the HP-UX, AIX, or Solaris server.

◆ HP-UX, AIX, or Solaris servers are load balanced across CLARiiON ports for performance improvement and protection against single-port and Ethernet cable problems.


The following Celerra installation guides provide more information about hardware installation:

◆ EMC Celerra NS20FC System (Single Blade) Installation Guide Addendum for MPFS

◆ EMC Celerra NS20FC System (Dual Blade) Installation Guide Addendum for MPFS

◆ EMC Celerra NS40FC System (Single Blade) Installation Guide Addendum for MPFS

◆ EMC Celerra NS40FC System (Dual Blade) Installation Guide Addendum for MPFS


38


Setting up the Celerra Network ServerThe Celerra Network Server System Software Installation Guide contains information on how to set up the Celerra Network Server, which can be found on the EMC Powerlink website.



Setting up the file systemThis section describes what to do before creating a file system and how to create a file system.

Before creating a file system

This section provides guidelines for storage systems and file system build criteria.

Storage system

CAUTION!Ensure that the file systems used for MPFS do not contain both CLARiiON and Symmetrix LUNs. MPFS does not support a mixed storage environment.

Storage and file system characteristics are very important in high- performance grid computing and virtualization environments.

File system build criteriaA properly built file system must:

◆ Use disk volumes from the same storage system.

Note: Do not use a file system spanning across two storage array enclosures. A file system spanning multiple storage systems is not supported even if the multiple storage systems are of the same type, CLARiiON or Symmetrix.

◆ Use disk volumes from the same disk type, all FC or ATA, not a mixture of FC and ATA.

◆ For best MPFS performance, in most cases, configure your Celerra volumes using a volume stripe size of 256 KB. Be sure to review the Celerra Network Server Best Practices for Performance White Paper for detailed performance related information.

◆ In a Symmetrix environment, ensure that the Symmetrix Fibre Channel port flag settings are properly configured for the MPFS file system; in particular, the ARB flag must be set. The EMC Customer Support Representative configures these settings.

Setting up the file system 39

40


Creating a file system on a Celerra Network Server

This section describes how to configure, create, mount, and export file systems.

Make sure LUNs for the new file system are created optimally for MPFS. All LUNs must:◆ Be of the same RAID type ◆ Have the same number of spindles in each RAID group◆ Contain spindles of the same type and speed

In addition, make sure that all LUNs do not share spindles with: ◆ Other LUNs in the same file system◆ Another file system heavily utilized by high-I/O applications

Before creating the LUNs, ensure that the total usable capacity of all the LUNs within a single file system does not exceed 16 TB. The maximum number of LUNs tested that are supported in MPFS configurations per file system is 256. Ensure that the LUNs are accessible by the Data Movers through LUN masking, switch zoning, and VSAN settings.

Use this procedure to build or mount the MPFS file system on the Celerra Network Server:

1. Log in to the Celerra Network Server Control Station as NAS administrator.

2. Before building the file system, type the nas_disk command to return a list of disks not in use. Use this command syntax:

$ nas_disk -list | grep n | more

For example, type:

$ nas_disk -l



The output is similar to this:

The first stripe alternate SP ownership A,B,A,B,A,B is displayed in bold text and the second stripe alternate SP ownership B,A,B,A,B,A is displayed in a shaded background. The two different stripes (A, B, A) and (B, A, B) are both in RAID group X, Y, and Z.

Note: Use Navicli or EMC Navisphere® Manager to determine which LUNs are on SP A and SP B.

id inuse sizeMB storageID-devID type name servers1 y 11263 APM00065101342-0000 CLSTD root_disk 1,22 y 11263 APM00065101342-0001 CLSTD root_disk 1,23 y 2047 APM00065101342-0002 CLSTD d3 1,24 y 2047 APM00065101342-0003 CLSTD d4 1,25 y 2047 APM00065101342-0004 CLSTD d5 1,26 y 2047 APM00065101342-0005 CLSTD d6 1,27 n 466747 APM00065101342-0010 CLSTD d7 1,28 n 466747 APM00065101342-0011 CLSTD d8 1,29 n 549623 APM00065101342-0012 CLSTD d9 1,210 n 549623 APM00065101342-0014 CLSTD d10 1,211 n 549623 APM00065101342-0016 CLSTD d11 1,212 n 549623 APM00065101342-0018 CLSTD d12 1,213 n 549623 APM00065101342-0013 CLSTD d13 1,214 n 549623 APM00065101342-0015 CLSTD d14 1,215 n 549623 APM00065101342-0017 CLSTD d15 1,216 n 549623 APM00065101342-0019 CLSTD d16 1,217 n 549623 APM00065101342-001A CLSTD d17 1,218 n 549623 APM00065101342-001B CLSTD d18 1,219 n 549623 APM00065101342-001C CLSTD d19 1,220 n 549623 APM00065101342-001E CLSTD d20 1,221 n 549623 APM00065101342-0020 CLSTD d21 1,222 n 549623 APM00065101342-001D CLSTD d22 1,223 n 549623 APM00065101342-001F CLSTD d23 1,224 n 549623 APM00065101342-0021 CLSTD d24 1,225 n 549623 APM00065101342-0022 CLSTD d25 1,226 n 549623 APM00065101342-0024 CLSTD d26 1,227 n 549623 APM00065101342-0026 CLSTD d27 1,228 n 549623 APM00065101342-0023 CLSTD d28 1,229 n 549623 APM00065101342-0025 CLSTD d29 1,230 n 549623 APM00065101342-0027 CLSTD d30 1,2


42


3. Create the first stripe. Use this command syntax:

$ nas_volume -name <name> -create -Stripe <stripe_size> <volume_set>,...

where:<name> = name of the volume<stripe_size> = size of the stripe<volume_set> = set of disks

For example, to create a stripe pair with a depth of 262144 bytes (256 KB), type:

$ nas_volume -name s2_stripe1 -create -Stripe 262144 d9,d14,d11,d16,d17,d22


id = 135name = s2_stripe1acl = 0in_use = Falsetype = stripestripe_size = 262144volume_set = d9,d14,d11,d16,d17,d22disks = d9,d14,d11,d16,d17,d22

Note: For best MPFS performance, in most cases, configure your Celerra volumes using a volume stripe size of 256 KB. Detailed performance-related information is available in the Celerra Network Server Best Practices for Performance White Paper.

4. Create a second stripe. Use this command syntax:

$ nas_volume -name <name> -create -Stripe <stripe_size> <volume_set>,...

where:<name> = name of the volume<stripe_size> = size of the stripe<volume_set> = set of disks

For example, to create a stripe pair with a depth of 262144 bytes (256 KB), type:

$ nas_volume -name s2_stripe2 -create -Stripe 262144 d13,d10,d15,d12,d18,d19




id = 136name = s2_stripe2acl = 0in_use = Falsetype = stripestripe_size = 262144volume_set = d13,d10,d15,d12,d18,d19disks = d13,d10,d15,d12,d18,d19

5. Create the metavolume. Use this command syntax:$ nas_volume -name <name> -create -Meta <volume_name>

where:<name> = assigns this name to a file system<volume_name> = name of the volume

For example, type:

$ nas_volume -name s2_metal -create -Meta s2_stripe1, s2_stripe2


id = 137name = s2_meta1acl = 0in_use = Falsetype = metavolume_set = s2_stripe1, s2_stripe2disks =

d9,d14,d11,d16,d17,d22,d13,d10,d15,d12,d18,d19


44


6. Create the file system. Use this command syntax:$ nas_fs -name <name> -create <volume_name>

where:<name> = assigns this name to a file system<volume_name> = name of the volume

For example, type:$ nas_fs -name s2fs1 -create s2_meta1


id = 33name = s2fs1acl = 0in_use = Falsetype = uxfsworm = complianceworm_clock= Thu Mar 6 16:26:09 EST 2008worm Max Retention Date = Fri Apr 18 12:30:40 EST 2008volume = s2_meta1pool = rw_servers= ro_servers= rw_vdms = ro_vdms = auto_ext = no, virtual_provision=nostor_devs =

APM00065101342-0012,APM00065101342-0015,APM00065101342-0016,APM00065101342-0019,APM00065101342-001A,APM00065101342-001D,APM00065101342-0013,APM00065101342-0014,APM00065101342-0017,APM00065101342-0018,APM00065101342-001B,APM00065101342-001C

disks = d9,d14,d11,d16,d17,d22,d13,d10,d15,d12,d18,d19

7. Create a mount point. Use this command syntax:$ server_mountpoint <movername> -create <pathname>

where:<movername> = name of the Data Mover<pathname> = path of the mount point you create

For example, type:

$ server_mountpoint server_2 -c /s2fs1

Output:server_2 : done



8. Mount the file system. Use this command syntax:$ server_mount <movername> <fs_name> <mount_point>

where:<movername> = name of the Data Mover<fs_name> = name of the file system to mount<mount_point> = name of the mount point

For example, type:$ server_mount server_2 s2fs1 /s2fs1


9. Export the file system. Use this command syntax:$ server_export <mover_name> -Protocol nfs -name

<name> -option <options> <pathname>

where:<mover_name> = name of the Data Mover<name> = assigns an alias for the <pathname><options> = options to include<pathname> = path of the mount point created

For example, type:$ server_export server_2 -P nfs -name ufs1 /ufs1



The following documents contain more information on building the MPFS file system and are available on the EMC Powerlink website:

◆ Celerra Network Server Command Reference Manual

◆ Configuring and Managing Celerra Networking

◆ Managing Celerra Volumes and File Systems Manually

◆ Using MPFS on Celerra


46


Enabling MPFS for the Celerra Network ServerStart MPFS on the Celerra Network Server. Use this command syntax:

$ server_setup <movername> -Protocol mpfs -option <options>

where:<movername> = name of the Data Mover<options> = options to include

Type:$ server_setup server_2 -Protocol mpfs -option start


Note: Start MPFS on the same Data Mover you exported the file system using NFS.



Configuring the CLARiiON using CLI commandsThis section presents an overview of configuring the CLARiiON CX3 or CX4 array ports mounted on the CLARiiON storage array for Celerra gateway configurations. Use your site-specific parameters for these steps.

The configuration of CLARiiON CX3 or CX4 array ports for a Celerra gateway is done using CLI commands.

Best practices To simplify the configuration and management of the HP-UX, AIX, or Solaris server, EMC recommends that the discovery addresses (IP addresses) and enabled targets for each HP-UX, AIX, or Solaris server be configured so that all the target ports on the storage array are equally balanced to achieve maximum performance and availability. Balancing the load across all ports enables speeds up to 4 x 10 Gb/s per storage processor. If one of the target ports fails, the other three will remain operational, so one-fourth of the HP-UX, AIX, or Solaris servers will fail over to the native NFS or CIFS protocol, but three-fourths of the HP-UX, AIX, or Solaris servers will continue operating.

CLARiiON discovery sessions reveal paths to all four ports on each storage processor. The ports are described to the initiators as individual targets. Each of these connections creates another session. The maximum number of initiator sessions or hosts per storage processor is 128 for the CLARiiON CX3, 256 for the CLARiiON CX4-120, 512 for the CLARiiON CX4-240, 1024 for the CLARiiON CX4-480, and 4096 for the CLARiiON CX4-960. Without disabling other targets, a CLARiiON cannot support more than 32 initiators. To increase the number of achievable HP-UX, AIX, or Solaris servers for a Celerra gateway, disable access on each HP-UX, AIX, or Solaris server to as many as three out of four targets per storage processor and ensure that the enabled targets (CLARiiON ports) match the storage group definition.

For Celerra gateway configurations, Access Logix LUN masking is used to present all Celerra managed LUNs to the HP-UX, AIX, or Solaris servers. The non-Celerra LUNs are protected from the initiators. A separate storage group is created for MPFS initiators and all Celerra LUNs that are not Celerra Control LUNs are added to this group. At least one port from each SP should be enabled for each HP-UX, AIX, or Solaris server in this group.

Configuring the CLARiiON using CLI commands 47

48


In a gateway environment, initiator names are used in providing the path in the storage group for the HP-UX, AIX, or Solaris server to access the targets. Unique, known names are required for using Access Logix software.

Configuring the SAN and storageThis section describes how to configure the SAN switch along with specific configuration information for Symmetrix and CLARiiON storage arrays.

Installing the Fibre Channel switch (FC configuration)

To set up the Fibre Channel switch, complete these tasks:

1. Install the Fibre Channel switch (if not already installed).

2. Connect cables from each HBA Fibre Channel port to a switch port.

3. Verify the HBA connection to the switch by checking the LEDs for the switch port connected to the HBA port.

Note: Configure zoning as single initiator, meaning that each HBA port will have its own zone in which it is the only HBA port.

Zoning the SAN switch (FC configuration)

This section presents an overview of configuring and zoning a Fibre Channel switch:

1. Record all attached port WWNs.

2. Create a zone for each Fibre Channel HBA port and its associated Fibre Channel Target.


Review to the documentation that ships with the Fibre Channel switch for information on installing or zoning.

Note: Configure the CLARiiON so that each target is zoned to an SP A and SP B port. Configure the Symmetrix so that it is zoned to a single Fibre Channel Director (FA).



Enabling SP A and SP B FC interfaces (FC configuration)

Enable the Fibre Channel ports for the storage processors. Use the FC interface data collected in “Configuration planning checklist” on page 31. Type:

switch(config)# interface fc4/2switch(config-if)# no shutdownswitch(config-if)# exitswitch(config)# interface fc4/4switch(config-if)# no shutdownswitch(config-if)# exit

Creating a security file on the Celerra Network Server

A storage system will not accept a Secure CLI command unless the user who issues the command has a valid user account on the storage system. You can configure a Navisphere 6.X security file to issue Secure CLI commands on the server. Secure CLI commands require the servers (or the password prompt) in each command line; you do not need to provide these in the command line if you create a security file.

To create a security file:

1. Log in to the Celerra Network Server Control Station as NAS administrator.

2. If you use the same settings for the username and passwords, as done on the switch, type:

$ /nas/sbin/naviseccli -h <hostname:IP address> security -AddUserSecurity -scope 0 -user nasadmin -password nasadmin

Note: Specify the hostname as SP A or SP B.

3. If you are using a new CLARiiON CX3 or CX4 series storage array with NAS v5.5 and content running in non-secure mode, type:

$ /nas/sbin/naviseccli -h <hostname:IP address> security -AddUserSecurity -scope 0 -user emc -password emc

Configuring the SAN and storage 49

50


Access Logix configuration

This section describes how to set up an Access Logix configuration, create storage groups, add LUNs, and set failovermode and the arraycommpath.

Setting failovermodeand the

arraycommpath usingAccess Logix

The naviseccli failovermode command enables or disables the type of trespass needed for the failover software. This method of setting -failovermode works for storage systems with Access Logix only.

To discover the current setting of failovermode, use the port-list-failovermode or port-list-all command:

CAUTION!Changing the failovermode setting may force the storage system to reboot. Changing the failovermode to the wrong value will make the storage group inaccessible to any connected server.

1. To set failovermode to 1 (unified storage only), type:

$ /nas/sbin/naviseccli -h <hostname:IP address> failovermode 1

WARNING: Previous Failovermode setting will be lost!DO YOU WISH TO CONTINUE (y/n)? y

2. To set arraycommpath to 1 (unified storage only), type:

$ /nas/sbin/naviseccli -h <hostname:IP address> arraycommpath 1

WARNING: Previous Arraycommpath setting will be lost!DO YOU WISH TO CONTINUE (y/n)? y

These commands enable failovermode and arraycommpath for the storage system.



Creating storagegroups and adding

LUNs

This section describes how to create storage groups, add LUNs to the storage groups, and configure the storage groups.

The IP addresses of all storage arrays <hostname:IP address> can be found in the /etc/hosts file on the Celerra Control Station. If multiple arrays are used, EMC recommends registering them in the /etc/hosts file:

Note: Specify the hostname as SP A or SP B.

1. Create the storage group:

$ /nas/sbin/navicli -h <hostname:IP address> storagegroup -create -gname MPFS_Clients

2. Add LUNs to the storage group:

$ /nas/sbin/navicli -h <hostname:IP address> storagegroup - addhlu -gname MPFS_Clients -hlu 0 -alu 16

3. Continue for all LUNs:

$ /nas/sbin/navicli -h <hostname:IP address> storagegroup - addhlu -gname MPFS_Clients -hlu 1 -alu 17


52


Configuring the storage system for PowerPath

This section describes how to configure a CLARiiON and Symmetrix storage system for PowerPath on HP-UX and Solaris servers.

Configure CLARiiONproperties for

PowerPath

To use PowerPath with a CLARiiON storage system, use either the CLI or the Navisphere GUI to set the failover mode and array commpath properties to 1. Procedures for both methods follow.

CAUTION!Set the failovermode and arraycommpath properties to 1 for PowerPath only. The Celerra Network Server requires that failovermode and arraycommpath properties be set to the default of 0.

CLI procedure for HP-UX serversOn an HP-UX server, to configure the storage system properties for PowerPath through the Navisphere CLI:

1. Use the following command syntax:

Note: The -type property must be set to 3 for HP-UX servers only.

$ navicli -h <hostname:IP_address> storagegroup -setpath -o gname <storage_group_name> -hbauid <WWN_of_client> -type 3 -failovermode 1 -arraycommpath 1

2. Repeat step 1 for each SP.

CLI procedure for Solaris servers On a Solaris server, configure the storage system properties for PowerPath through the CLI by using the following command syntax:

$ navicli -h <hostname:IP_address> storagegroup -setpath -o gname <storage_group_name> -hbauid <WWN_of_client> -failovermode 1 -arraycommpath 1



GUI procedure for HP-UX and Solaris serversTo configure the array commpath and failover mode settings through the Navisphere GUI:

Note: Before you perform this procedure: -You must have the Navisphere Agent installed on the server where you are configuring the storage system settings.-The RAID groups and storage groups must be set up.

1. Connect to the Navisphere GUI by typing the storage processor’s IP address in an Internet browser’s Address field.

2. Type your username and password when prompted, and then click OK.

3. Right-click the serial number of the storage system to be configured, and select Connectivity Status.

4. In the Connectivity Status window, click Group Edit.

5. In the Group Edit Initiators window:a. Move the PowerPath server WWNs to be configured from the

Available box to the Selected box.

b. Select Enabled from the Array CommPath drop-down menu.

c. For Solaris servers, select CLARiiON Open from the Initiator Type drop-down menu.

d. For HP-UX servers, select HP No Auto Trespass from the Initiator Type drop-down menu.

e. Select 1 from the Failover Mode drop-down menu.

f. Select the appropriate server from the server drop-down menu.

CAUTION!Set the failovermode and arraycommpath properties to 1 for PowerPath only. The Celerra Network Server requires that failovermode and arraycommpath properties be set to the default of 0.


54


Figure 4 on page 54 shows the window to configure these settings.

Figure 4 Configuring CLARiiON for PowerPath

6. Click OK.

PowerPath documentation or the Installation Roadmap for CX-Series and FC-Series Storage Systems provides more information on PowerPath settings in a CLARiiON environment.



Configure Symmetrixproperties for

PowerPath

Use Volume Logix to configure the Symmetrix storage system. In a Symmetrix environment, perform these tasks:

1. Configure the Fibre Channel switch for the specific topology required to support the Data Mover/storage system connections through the switched fabric.

2. Create aliases using WWNs, and use the aliases to create zones.

3. To identify Data Mover port WWNs, use the following command syntax (on the Celerra Network Server):

$ server_sysconfig <movername> -p | grep fcp

where:<movername> = name of the Data Mover

Output:

server_sysconfig test1 -p | grep fcp 1: fcp-0 IRQ: 31 addr: 5006016039a0018b 0: fcp-1 IRQ: 32 addr: 5006016139a0018b 2: fcp-2 IRQ: 33 addr: 5006016239a0018b 1: fcp-3 IRQ: 34 addr: 5006016339a0018b

4. Record all attached port WWNs.

5. Create a zone for each Fibre Channel (HBA) port and its associated Fibre Channel Director (FA).

6. Configure each switch attached to the Data Movers and the Celerra Network Server for failover.

7. Use EMC ControlCenter® or Symmetrix Manager to create and share storage groups with the Celerra Network Server, and supply the interface and share names for the HP-UX, AIX, or Solaris server.


The following documents are available on the EMC Powerlink website:




◆ EMC Navisphere Manager Administrator’s Guide and online help

◆ EMC ControlCenter Administrator/User Guide and online help


56


Installing PowerPathIn a CLARiiON environment, a fully licensed version of PowerPath is required for basic failover functionality. You do not need to install PowerPath in a Symmetrix environment.

In Symmetrix and CLARiiON environments, PowerPath licensed versions provide additional functionality, such as dynamic load balancing and automatic channel failover.

Note: EMC recommends installing PowerPath software before you install the MPFS software.

Before you install the MPFS software:

1. Do one of the following:

• In a CLARiiON environment, install PowerPath on the MPFS system.

• In a Symmetrix environment, optionally, install a licensed PowerPath version. (You need not install PowerPath in a Symmetrix environment.)

2. Proceed with the MPFS Software Installation.

Chapter 3, ”Installing PowerPath with MPFS”, and the PowerPath documentation included in the MPFS distribution package provide more detailed information.


Additional documentation about PowerPath can be found on the EMC Powerlink website.



Installing the MPFS softwareEMC recommends installing PowerPath, where applicable, before installing the MPFS software.

The following chapters within this book detail the MPFS software installation:

◆ Chapter 4, ”Installing the MPFS Software on an HP-UX Server”

◆ Chapter 5, ”Installing the MPFS Software on an AIX Server”

◆ Chapter 6, ”Installing the MPFS Software on a Solaris Server”

Operating MPFS through a firewall

For proper MPFS operation, the HP-UX, AIX, or Solaris server must contact the Celerra Network Server (a Data Mover) on its File Mapping Protocol (FMP) port. The Celerra Network Server must also contact the HP-UX, AIX, or Solaris server on its FMP port.

If a firewall resides between the HP-UX, AIX, or Solaris server and the Celerra Network Server, the firewall must allow access to the ports listed in Table 4 on page 57 for the HP-UX, AIX, or Solaris server.

Table 4 HP-UX, AIX, or Solaris server firewall ports

HP-UX, AIX, or Solaris server HP-UX, AIX, or Solaris server port Celerra Network Server port

HP-UX, AIX, or Solaris O/S 6907 4656, 2079, 1234, 111, 625

Installing the MPFS software 57

58


Configuring and accessing storageThis section describes how to install the Fibre Channel driver, configure the driver, and add initiators to the storage group.

The arraycommpath and failovermode settings are used to see both active and passive paths concurrently. For a LUN failover, LUNs can be presented from active to passive path or passive to active path. Use arraycommpath and failovermode settings as described in Table 5 on page 58.

Any MPFS server that is connected and logged into a storage group should have the arraycommpath and failovermode set to 1. For any Celerra port connected to a storage group, these settings should be 0. These settings are on an individual server/port basis and override the global settings on the storage array default of 0.

When using the CLARiiON CX3 or CX4 series storage array in a gateway configuration, the initiator name, or IQN, is used to define the server, not a WWN.

Installing the Fibre Channel driver (FC configuration)

Install the Fibre Channel driver on the HP-UX, AIX, or Solaris server. The latest driver and qualification information is available on the Fibre Channel manufacturer’s website, the EMC E-Lab Interoperability Navigator, or the documentation provided with the Fibre Channel driver.

Table 5 Correct arraycommpath and failovermode settings

Celerraports

HP-UX, AIX, or Solaris server

Gateway units with Access Logix

arraycommpath 0 1

failovermode 0 1

Unified storage, MPFS capable units

arraycommpath 0 1

failovermode 0 1



Adding Fibre Channelhosts to the storage

group (FCconfiguration)

Use the following steps to view hosts in the storage group and add hosts to the storage group for SP A and SP B:

1. Use the following navicli command to list the hosts in the storage group:

$ /nas/sbin/navicli -h <hostname:IP address> port -list |grep "HBA UID:"


HBA UID: 20:01:00:1B:32:20:D1:3A:21:01:00:1B:32:20:D1:3AHBA UID: 20:00:00:1B:32:00:D1:3A:21:00:00:1B:32:00:D1:3AHBA UID: 20:01:00:1B:32:20:B5:35:21:01:00:1B:32:20:B5:35HBA UID: 20:00:00:1B:32:00:B5:35:21:00:00:1B:32:00:B5:35

2. Use the following navicli command to add hosts to the storage group using this command syntax:

$ /nas/sbin/navicli -h <hostname:IP address> storagegroup -setpath -gname <gname> -hbauid <hbauid> -sp <sp> -spport <spport> -failovermode <failovermode> -arraycommpath <arraycommpath>

where:

For example:

$ /nas/sbin/navicli -h xxx.xxx.xx.x storagegroup -setpath -gname MPFS_Clients -hbauid 20:0a:00:0d:ec:01:53:82:20:09:00:0d:ec:01:53:82 -sp a -spport 0 -failovermode 1 -arraycommpath 1

–gname = storage group name–hbauid = WWN of proxy initiator–sp = storage processor–spport = port on SP–failovermode = enables or disables the type of trespass

needed for failover software (1 = enable, 0 = disable)

–arraycommpath = creates or removes a communication path between the server and the storage system (1 = enable, 0 = disable)

Configuring and accessing storage 59

60


3. Perform this command for each SP.

Note: The IP addresses of all storage arrays <hostname:IP address> can be found in the /etc/hosts file on the Celerra Control Station. If multiple arrays are used, EMC recommends registering them in the /etc/hosts file.


list host wwn

$ /nas/sbin/navicli -h <hostname:IP address> storagegroup -setpath -gname MPFS_Clients -hbauid 20:0a:00:0d:ec:01:53:82:20:09:00:0d:ec:01:53:82 -sp a -spport 0 -failovermode 1 -arraycommpath 1

The recommended configuration is to have all HBAs on one host mapped to the same storage group.

Set Path to storage group MPFS_Clients (y/n)? y WARNING: Changing configuration options may cause the

array to stop functioningcorrectly. Failover-related Initiator settings for a

single host MUST BE CONSISTENTfor all paths from the host to the storage system. Please

verify after reconnect.Do you wish to continue (y/n)? y $ /nas/sbin/navicli -h <hostname:IP address> storagegroup

-setpath -gname MPFS_Clients -hbauid 20:0a:00:0d:ec:01:53:82:20:09:00:0d:ec:01:53:82 -sp a -spport 0 -failovermode 1 -arraycommpath 1

The recommended configuration is to have all HBAs on one

host mapped to the same storage group. Set Path to storage group MPFS_Clients (y/n)? y WARNING: Changing configuration options may cause the

array to stop functioningcorrectly. Failover-related Initiator settings for a

single host MUST BE CONSISTENTfor all paths from the host to the storage system. Please

verify after reconnect.Do you wish to continue (y/n)? y



Mounting the MPFS file systemTo establish an HP-UX, AIX, or Solaris server/Celerra Network Server session, a connection between the servers must be completed. Establish a session by mounting the MPFS file system on the HP-UX, AIX, or Solaris server using the mount command.

Note: MPFS file systems can be added to the /etc/fstab file to mount the file system automatically after the server is rebooted or shut down.

To mount an MPFS file system on an HP-UX or Solaris server, use the mount command with the following syntax:mount -F mpfs -o <MPFS_specific_options>

<movername>:/<FS_export> <mount_point>

To mount an MPFS file system on an AIX server, use the mount command with the following syntax:mount -V mpfs -o <MPFS_specific_options>

<movername>:/<FS_export> <mount_point>

where:

◆ <MPFS_specific_options> = comma-separated list (without spaces) of arguments to the -o option that are supported by the EMC Celerra MPFS. Most arguments to the -o option that are supported by the NFS mount command (as described in the mount_nfs manpage) are also supported by MPFS. MPFS supports the following additional arguments:

• -o mpfs_verbose — Executes the mount command in verbose mode.

• -o mpfs_keep_nfs — If the mount using MPFS fails, the file system is mounted using NFS instead. Warning messages inform the user that the MPFS mount failed.

• -o hvl — Specify the volume management type as hierarchical by default if it is supported by the server (-o hvl=1) or as not hierarchical by default (-o hvl=0). Setting this value overrides the default value specified in /etc/sysconfig/EMCmpfs.

Note: The -o hvl option requires NAS software version 5.6 or later.

◆ <movername> = name or IP address of a Data Mover

◆ <FS_export> = absolute pathname of the directory exported on the Celerra Network Server; FS must be in upper case text

Mounting the MPFS file system 61

62


◆ <mount_point> = absolute pathname of the directory on the HP-UX, AIX, or Solaris server on which to mount the MPFS file system

Note: To view the manpage for the mount command, type man mount_mpfs.

Example The following commands mount an MPFS file system; the mpfs_keep_nfs option causes the file system to mount using NFS if the mount using MPFS fails:

◆ For an HP-UX or Solaris server:

mount -F mpfs -o mpfs_keep_nfs server1:/src /usr/src

◆ For an AIX server:

mount -V mpfs -o mpfs_keep_nfs server1:/src /usr/src

With the mpfs_keep_nfs option, the behavior is to try to mount the file system using MPFS. If all disks are not available, the file system will default to NFS.

The default behavior of mount -F mpfs is to mount the file system. If all disks are not available, the mount will fail with the error below.

For an HP-UX or Solaris server:

$ mount -F mpfs 12.345.6.789:/rcfs /mnt/mpfs


Volume ’APM000643042520000-0008’ not found.Error mounting /mnt/mpfs via MPFS

For an AIX server:

$ mount -V mpfs 12.345.6.789:/rcfs /mnt/mpfs


Disk not found.Error mounting /mnt/mpfs via MPFS


3

This chapter describes PowerPath versions and features, lists prerequisites and relevant documentation, and describes how to locate PowerPath patches.

Note: PowerPath is required in some environments for failover protection, as explained further in this chapter. EMC recommends installing PowerPath before you install MPFS.

This chapter covers the following topics:

◆ PowerPath overview ......................................................................... 64◆ Before installing.................................................................................. 66◆ Locating PowerPath patches ............................................................ 69◆ Installing PowerPath ......................................................................... 70

Installing PowerPathwith MPFS

Installing PowerPath with MPFS 63

64

Installing PowerPath with MPFS

PowerPath overviewPowerPath provides basic failover functionality for CLARiiON storage processors.

Licensed PowerPath provides Fibre Channel load balancing and failover capability for CLARiiON and Symmetrix storage arrays, in addition to providing basic failover functionality for CLARiiON storage processors. Table 6 on page 65 presents a summary of PowerPath versions and functionality with both Symmetrix and CLARiiON storage systems.

In a CLARiiON environment with MPFS, you must install a fully licensed version of PowerPath for basic failover functionality.

In a Symmetrix environment, you can optionally install a licensed version of PowerPath.

Note: EMC Celerra MPFS v 4.0 provides built-in volume protection for CLARiiON storage systems.



Table 6 on page 65 summarizes PowerPath functionality with MPFS in a Symmetrix or CLARiiON environment.

CAUTION!MPFS does not support a file system comprised of both CLARiiON and Symmetrix LUNs.

Table 6 Summary of PowerPath versions and features

Storage systemPowerPath version Supported configurations PowerPath features

CLARiiON with MPFS PowerPath(Required)

One HBA connected to the CLARiiON storage system through a switch fabric with exactly one path from the HBA to SP A and exactly one path from the same HBA to SP B.

Note: Using PowerPath in multipath environments produces non determinate results with respect to path usage. EMC does not support PowerPath in servers with more than one HBA.

Provides basic failover functionality (also called trespassing).

CLARiiON with MPFS Licensed PowerPath(Optional)

• Only two HBAs connected to the CLARiiON storage system with exactly one path from one HBA to SP A and exactly one path from the other HBA to SP B.

• Single or multiple HBAs with multiple paths to the storage processor.

In addition to basic failover capability, provides load balancing and logical volume management.

Symmetrix with MPFS Licensed PowerPath(Optional)

Any Symmetrix configuration. Provides path failover, load balancing, and logical volume management.

PowerPath overview 65

66


Before installingBefore you install PowerPath, ensure you have met the following requirements:

Servers ❑ For servers connected to storage arrays via a Fibre Channel switch (that is, a fabric), configure the HBAs using persistent binding for target IDs.

CAUTION!Failure to use persistent binding could result in loss or corruption of data. The Host Connectivity Guide for Sun Solaris, the HBA driver documentation, and the .conf file for your HBA type are good sources for information about persistent binding.

❑ Ensure that the server is connected to the Fibre Channel ports and can see all its devices.

❑ The Environment and System Requirements section of the EMC PowerPath for UNIX Release Notes describes the operating system versions and patches needed to support PowerPath, and differences between the server-storage system interconnection topologies specified in the EMC NAS Interoperability Matrix and specific PowerPath requirements.

Ensure that there is only one path per logical device. Once PowerPath is installed, more than one path per logical device is permitted. If necessary, disconnect the cable on the server and not on the array.



CLARiiON storagesystem

❑ Before you install PowerPath, you must install the HBA driver, as described in the documentation that shipped with the HBA driver.

❑ In a CLARiiON environment, you cannot run ATF or CDE and PowerPath on the same server. Furthermore, simply removing CDE using the uninstall procedure described in the host utilities administrator’s guide for your operating system may not return the server to its original state, and may result in lost data.Before you transition your server from ATF or CDE to PowerPath, you must:

• Back up your server configurations.

• Back up data on all storage systems connected to the server.

• Remove ATF or CDE, which EMC recommends that EMC Professional Services do, especially if your server configuration is complex. If you want to remove it yourself, you must use the procedures in Removing ATF or CDE Software Before Installing Other Failover Software and EMC Installation Roadmap for CX-Series and FC-Series Storage Systems, which are on the EMC Powerlink website. Simply removing ATF or CDE using the uninstall procedure in the administrator’s guide or the host utilities guide may not return the server to its original state, and may result in lost data.

CAUTION!The procedure for migrating from ATF or CDE to PowerPath is not straightforward and could result in data loss if not performed correctly. We strongly recommend that EMC Professional Services perform the migration. If you nevertheless decide to perform the migration yourself, the manual Removing ATF or CDE Software Before Installing Other Failover Software is available more information. This document is available on the EMC Powerlink website.

❑ Ensure you have configured the appropriate storage system properties. “Storage systems requirements” on page 34 provides more information.

Before installing 67

68


❑ PowerPath installation is an integral part of a CLARiiON setup and configuration procedure. To properly install PowerPath on a server with a CLARiiON storage array, be sure to read the EMC Installation Roadmap for CX-Series and FC-Series Storage Systems. There you will find step-by-step instructions for installing PowerPath and other CLARiiON software. This document may be found on the EMC Powerlink website at http://Powerlink.EMC.com.

❑ If it is running, stop the Navisphere agent before installing either the full release or a patch release of PowerPath.

❑ Ensure that the storage system logical devices are configured for PowerPath support. The EMC Host Connectivity Guides for both Symmetrix and CLARiiON systems provide additional information. Also see the Installation Roadmap for CX-Series and FC-Series Storage Systems for CLARiiON systems.

Symmetrix storagesystem

❑ Install PowerPath after you set up and verify that the Symmetrix is working properly. Additional documentation about installing and configuring PowerPath software is available on the EMC Powerlink website.



Locating PowerPath patchesBefore installing PowerPath, check for required patches and their associated patch ReadMe files at http://Powerlink.EMC.com.

To identify PowerPath patches:

◆ PowerPath releases are identified by a three-digit version number:

<Major>.<Minor>.<Patch>

◆ Full product releases always have a Patch number of zero (0). For example:

4.0.0

◆ Patch files names are formatted as follows:

EMCPower.<Platform>.<M>.<m>.<P>.tar.z

where:

<M> = the major version number<m> = the Minor version number<P> = patch number

For example:

EMCPower.HP.4.2.1.tar.z

The PowerPath patch ReadMe file describes the contents of the patch and provides installation instructions. PowerPath patches are released as required. Typically, different platforms will have different extant patch levels—including no extant patches.

PowerPath patches can be applied only to a full release or an earlier (lower numbered) patch release that has the same major and minor number as the patch that is being applied.

Locating PowerPath patches 69

http://powerlink.emc.com

70


Installing PowerPath

Note: If you are installing PowerPath, you must do so before you install the MPFS software.

CAUTION!In a CLARiiON environment, PowerPath is required for basic failover functionality.

To install PowerPath with the MPFS software:

◆ If the latest version of PowerPath and any required patch is already installed on the server on which you plan to install the MPFS software, ensure any required PowerPath patch is also installed. “Locating PowerPath patches” on page 69 provides additional information.

For an HP-UX Version 11.11 server, install the latest PowerPath patch. “Locating PowerPath patches” on page 69 provides more information.

◆ If PowerPath is not installed on the server, purchase and install PowerPath. Download and install any required patch. This option gives you full PowerPath functionality.

After you install PowerPath, you should run the powermt display command from the command prompt. This allows you to verify the total number of devices that the HP-UX, AIX, or Solaris server can access.

Note: Refer to the EMC E-Lab Interoperability Matrix listing the latest version of PowerPath AIX, HP-UX, or Solaris installation and administration guides.

Related documentation

Additional documentation about PowerPath is available on the EMC Powerlink website.


4

This chapter describes how to install and uninstall MPFS software and how to mount an MPFS file system on a HP-UX server.

If you are migrating from an earlier release of the MPFS software, “Migrating from an earlier release” on page 81 provides more information.


◆ Before installing.................................................................................. 72◆ Installing the MPFS software ........................................................... 74◆ Migrating from an earlier release .................................................... 81◆ Uninstalling the MPFS software ...................................................... 82

Installing the MPFSSoftware on an HP-UX

Server

Installing the MPFS Software on an HP-UX Server 71

72

Installing the MPFS Software on an HP-UX Server

Before installingThis section describes the tasks that must be completed before installing the MPFS software.

Before installing the MPFS software, review the guidelines in this section.

Note: In a CLARiiON environment, a fully licensed version of PowerPath is required for basic failover functionality. EMC recommends that you install PowerPath before you install the MPFS software. “Installing PowerPath” on page 70 provides more information.

MPFS software Verify that the HP-UX server on which you plan to install MPFS:

❑ Meets the hardware, software, and MPFS configuration requirements specified in the Celerra MPFS for HP-UX and Solaris Clients Release Notes.

❑ Has a direct Fibre Channel connection to the storage array, and that the storage array meets the hardware and software requirements specified in the Celerra MPFS for HP-UX and Solaris Clients Release Notes. The EMC Customer Support Representative configures the Symmetrix or CLARiiON storage array and establishes the connection between the HP-UX server and the storage array.

❑ Meets the overall system and other configuration requirements specified in the EMC E-Lab Interoperability Navigator.

❑ Is configured with NFS v3 file system.



Storage array On the storage array, ensure that:

❑ File systems used for MPFS do not contain both CLARiiON and Symmetrix LUNs. MPFS does not support a mixed storage array environment.

❑ The Symmetrix Fibre Channel port flag settings are properly configured for the EMC Celerra MPFS; in particular, that the ARB flag is set. The EMC Customer Support Representative configures these settings.

❑ The HP-UX server has been configured to incorporate the CLARiiON or Symmetrix disk devices into HP-UX and make the devices visible from the HP-UX server. The CLARiiON or Symmetrix devices must be properly configured on the Fibre Channel using Fibre Channel port addresses. The EMC Host Connectivity guides, available on the EMC Powerlink website (http://Powerlink.EMC.com), provide more information.

CAUTION!Incorporating the Symmetrix devices may involve rebooting the HP-UX server. Therefore, make sure that all applications are closed and all users are logged off the HP-UX server before incorporating the Symmetrix devices.

❑ The CLARiiON storage array properties for PowerPath have been properly configured. “Configuring the storage system for PowerPath” on page 52 provides additional information.

❑ For optimal performance with MPFS, the following stripe size depths are required:

• CLARiiON storage array — 256 KB

• Symmetrix storage array — 32 KB



74


Installing the MPFS softwareThe MPFS software can be installed directly from the EMC MPFS for UNIX/HP/Sun Client Software CD by using the Command Line Interface (CLI) or from a compressed tar file on the EMC Powerlink website.

The following sections describe how to:

◆ Meet prerequisites before installing

◆ Recognize the storage system devices

◆ Mount the CD

◆ Install the MPFS software from a CD

◆ Install the MPFS software from the compressed tar file

Before installing Before you install the MPFS software, read the prerequisites for the HP-UX server and storage array, listed in this section:

❑ Verify that the HP-UX server on which you plan to install the MPFS software meets the MPFS configuration requirements specified in the EMC Celerra MPFS for HP-UX and Solaris Clients Release Notes.

❑ Ensure that the system has a network connection to the Data Mover on which the Celerra Network Server with MPFS software resides and that you can contact the Data Mover.

❑ Ensure that the HP-UX server meets the overall system and other configuration requirements specified in the EMC E-Lab Interoperability Navigator.

❑ PA-RISC is supported for HP-UX servers, but not for HP-UX Itanium (ia64) servers.

❑ Install PowerPath before installing the MPFS software. “Installing PowerPath” on page 70 provides more information.

Note: The installation of MPFS on HP-UX 11.31 requires that PowerPath is installed.

❑ In a CLARiiON environment, a fully licensed version of PowerPath is required for basic failover functionality.



Recognizing storage system devices

Use the ioscan command on the HP-UX server to verify that the HP-UX server recognizes the storage system devices.

The command has the following syntax:

ioscan <-C disk>

where:<-C disk> = checks the storage system to recognize the disks.

To verify that the HP-UX server recognizes the storage system devices, type:

ioscan -C disk

Use insf command for the MPFS device files to recognize the storage system devices.


insf <-e>

where:<-e> = insf reinstalls special files for pseudo drivers and existing devices. This is used for restoring special files when one or more have been removed. For MPFS, it is necessary when installing the MPFS software on an Itanium platform running the HP-UX operating system.

For MPFS device files to recognize the storage system devices, type:

insf -e


76


Mounting the CD To mount the EMC Celerra MPFS installation CD:

1. Log in to the HP-UX server as root.

2. Create the directory /cdrom to be the mount point for the CD by typing:

mkdir /cdrom

3. Insert the CD into the CD drive.

4. If you do not know the CD device ID, type:

/usr/sbin/ioscan -funC disk

5. Mount the CD on /cdrom using the following command syntax:

mount -F cdfs -r /dev/dsk/c<x>t<y>d<z> /cdrom

where <x>, <y>, and <z> are values specific to the HP-UX server’s CD drive.

For example:

mount -F cdfs -r /dev/dsk/c0t2d0 /cdrom

Installing the MPFS software from a CD

To install the MPFS software from a CD using the CLI:

1. Mount the CD in the CD drive.

2. Install the software by typing:

swinstall -s /cdrom/hp-ux/EMCmpfs.depot EMCmpfs

The screen displays information about the installation:

======= 08/11/08 15:39:56 EDT BEGIN swinstall SESSION (non-interactive)

* Session started for user "root@hostname".

* Beginning Selection * Target connection succeeded for "<hostname>:/". * Source: /cdrom/hp-ux * Targets: <hostname>:/ * Software selections:

EMCmpfs.MPFS-CORE2-64-11i,r=4.0.23,a=HP-UX_B.11.00_32/64,v=EMC,fr=4.0.23,fa=HP-UX_B.11.11_64

EMCmpfs.MPFS-MAN,r=4.0.23,a=HP-UX_B.11.00_32/64,v=EMC,fr=4.0.23,fa=HP-UX_B.11.00_32/64



* Selection succeeded.

* Beginning Analysis and Execution * Session selections have been saved in the file "/.sw/sessions/swinstall.last". * The analysis phase succeeded for "<hostname>:/". * The execution phase succeeded for "<hostname>:/". * Analysis and Execution succeeded.

NOTE: More information may be found in the agent logfile using the command "swjob -a log <hostname>-0099 @ <hostname>:/".

======= 08/11/08 15:40:17 EDT END swinstall SESSION (non-interactive)

3. Unmount the CD by typing:

umount /cdrom

The MPFS software is now installed on the HP-UX server.

Installing the MPFS software from a tar file

To install the MPFS software from a compressed tar file, download the file from the EMC Powerlink website. Then, uncompress and extract the tar file on the HP-UX server and execute the swinstall command.

Follow these steps to, uncompress, extract, and install the MPFS software from the compressed tar file and installing the EMCmpfs.depot file:

1. Create the directory /tmp/temp_mpfs if it does not already exist.

2. Locate the compressed tar file on the EMC Powerlink website.

Depending on the specific MPFS software release and version, the filename will appear similar to the following:

EMCmpfs.hp-ux.4.0.23.0.tar.Z

3. Download the compressed tar file from the EMC Powerlink website to the directory created in step 1.

Note: For HP-UX Itanium (ia64) Servers only, go to step 9 and continue. Otherwise continue with steps 4 through 8.

4. Change to the /tmp/temp_mpfs directory:

cd /tmp/temp_mpfs


78


5. Uncompress the tar file by using the following command syntax:

uncompress <filename>

where <filename> is the name of the tar file, for example:

uncompress EMCmpfs.hp-ux.4.0.23.0.tar.Z

6. Extract the tar file by using the following command syntax:

tar -xvf <filename>.tar


tar -xvf EMCmpfs.hp-ux.4.0.23.0.tar

7. Install the MPFS software, starting with step 2 in “Installing the MPFS software from a CD” on page 76, changing the source depot path to /tmp/temp_mpfs/hp-ux.

For example, to install the MPFS software, type:

swinstall -s /tmp/temp_mpfs/hp-ux/EMCmpfs.depot EMCmpfs

8. Verify the version of MPFS software installed by typing:

$ mpfsctl version

Note: Steps 9 through 16 are for HP-UX Itanium Servers only.


10. Download the tar file from the EMC Powerlink website to the directory created in step 1. This file must be copied to the directory /tmp/temp_mpfs.

Note: The install will fail if you attempt to install the MPFS software using the EMCmpfs.depot file over the network.


cd /tmp/temp_mpfs




uncompress EMCmpfs.hp-ux.4.0.23.0.tar.Z




tar -xvf <filename>


tar -xvf EMCmpfs.hp-ux.4.0.23.0.tar

14. Issue the insf -e command.

15. Install the MPFS software by typing:

swinstall -x autoreboot=true-s/tmp/temp_mpfs/hp-ux/ EMCmpfs.depot EMCmpfs

16. Verify the version of MPFS software installed by typing:

$ mpfsctl version

Post-installation check

After installing the MPFS software:

1. Verify that the software is installed properly and that both the MPFS daemon mpfsd and the heartbeat daemon hbd have started.

2. Unmount the CD and remove it from the CD drive.

3. Start the software by mounting an MPFS file system.


80


Verifying the installation on an HP-UX server

Use the swlist command to verify that the MPFS software is installed, and use the ps command to verify that the MPFS and heartbeat daemons have started:

1. Use the svlist command to verify the installation by typing:

swlist EMCmpfs

If the MPFS software is installed properly, the command displays output similar to this:

# EMCmpfs 4.0.23 EMC MPFS Filesystem EMCmpfs.MPFS-CORE2-64-11i 4.0.23 EMC MPFS for HP-UX 11.11 64-bit

kernel core fileset EMCmpfs.MPFS-MAN 4.0.23 EMC MPFS man pages

2. Use the ps command to verify that the MPFS daemon has started by typing:

ps -ef | grep mpfsd

The output will look like this if the MPFS daemon has started:

root 10284 13604 2 10:43:16 pts/2 0:00 grep mpfsd root 11744 1 0 Aug 11 - 0:00 /opt/EMCmpfs/bin/mpfsd

3. Use the ps command to verify that the heartbeat daemon has started by typing:

ps -ef | grep hbd

The output will look like this if the heartbeat daemon has started:

root 28473 26698 1 17:26:37 pts/5 0:00 grep hbdroot 28437 1 0 17:23:42 ? 0:00 /opt/EMCmpfs/bin/hbd

Unmounting and removing the CD

Unmount the CD by typing:

umount /cdrom

Then remove the CD from the CD drive.



Migrating from an earlier releaseWhen migrating from an earlier release of the MPFS software, uninstall the earlier release of the MPFS software before installing the new software. “Uninstalling the MPFS software” on page 82 provides details.

Migrating from an earlier release 81

82


Uninstalling the MPFS softwareTo remove the MPFS software using the CLI:

1. Log in to the HP-UX server as root.

2. Make sure that no MPFS mounts are active by unmounting all mounted MPFS file systems by typing:

umountall -F mpfs

3. Comment out, or delete, all MPFS file system entries in the HP-UX server’s /etc/fstab file.

Note: For an HP-UX Itanium Server, go to step 5, otherwise go to step 4 and skip step 5.

4. Remove the MPFS software from an HP-UX server by typing:

swremove EMCmpfs

5. Remove the MPFS software from an HP-UX Itanium Server by typing:

swremove -x autorebpoot=true EMCmpfs



The screen displays information about the removal:

======= 08/11/08 17:11:48 EDT BEGIN swremove SESSION (non-interactive)

* Session started for user "root@<hostname>".

* Beginning Selection * Target connection succeeded for "<hostname>:/". * Software selections:

EMCmpfs.MPFS-CORE2-64-11i,l=/opt/EMCmpfs,r=4.0.22,a=HP-UX_B.11.00_32/64,v=EMC,fr=4.0.22,fa=HP-UX_B.11.11_64

EMCmpfs.MPFS-MAN,l=/opt/EMCmpfs,r=4.0.22,a=HP-UX_B.11.00_32/64,v=EMC,fr=4.0.22,fa=HP-UX_B.11.00_32/64

* Selection succeeded.

* Beginning Analysis * Session selections have been saved in the file "/.sw/sessions/swremove.last". * The analysis phase succeeded for "<hostname>:/". * Analysis succeeded. * Beginning Execution * The execution phase succeeded for "<hostname>:/". * Execution succeeded.

NOTE: More information may be found in the agent logfile using the command "swjob -a log <hostname>-0100 @ <hostname>:/".

======= 08/11/08 17:11:53 EDT END swremove SESSION (non-interactive)

Uninstalling the MPFS software 83

84



5

This chapter describes how to install and uninstall MPFS software and how to mount an MPFS filesystem on an AIX server.

If you are migrating from an earlier release of the MPFS software, “Migrating from an earlier release” on page 94 provides more information.


◆ Before installing.................................................................................. 86◆ Installing the MPFS software ........................................................... 88◆ After installing.................................................................................... 92◆ Migrating from an earlier release .................................................... 94◆ Uninstalling the MPFS software ...................................................... 96

Installing the MPFSSoftware on an AIX

Server

Installing the MPFS Software on an AIX Server 85

86

Installing the MPFS Software on an AIX Server


Before installing the MPFS software, review the guidelines in this section.


MPFS software Verify that the AIX server on which you plan to install the MPFS software:

❑ Meets the hardware, software and MPFS configuration requirements specified in the Celerra MPFS for AIX Clients Release Notes.

❑ Has a direct Fibre Channel connection to the storage array, and that the storage array meets the hardware and software requirements specified in the Celerra MPFS for AIX Clients Release Notes. The EMC Customer Support Representative configures the Symmetrix or CLARiiON storage array and establishes the connection between the AIX server and the storage array.





Storage array On the storage array, ensure that:

❑ File systems used for MPFS do not contain both CLARiiON and Symmetrix LUNs. MPFS does not support a mixed storage array environment.

❑ The Symmetrix Fibre Channel port flag settings are properly configured for the EMC Celerra MPFS; in particular, that the ARB flag is set. The EMC Customer Support Representative configures these settings.

❑ The AIX server has been configured to incorporate the CLARiiON or Symmetrix disk devices into AIX and make the devices visible from the AIX server. Use the Object Data Manager (ODM) definitions supplied by EMC for the Symmetrix. The CLARiiON or Symmetrix devices must be properly configured on the Fibre Channel using Fibre Channel port addresses. The EMC Host Connectivity guides, available on the EMC Powerlink website (http://Powerlink.EMC.com), provide more information.

CAUTION!Incorporating the Symmetrix devices may involve rebooting the AIX server. Therefore, make sure that all applications are closed and all users are logged off the AIX server before incorporating the Symmetrix devices.


❑ For optimal performance with MPFS, the following stripe size depths are required:

• CLARiiON storage array — 256 KB

• Symmetrix storage array — 32 KB



88


Installing the MPFS softwareThe MPFS software can be installed directly from the EMC MPFS for UNIX/HP/Sun Client Software CD by using the CLI or from a compressed tar file on the EMC Powerlink website.



◆ Mount the CD



Before installing Before you install the MPFS software, read the prerequisites for the AIX server and storage array, listed in this section:


❑ PowerPC (32-bit or 64-bit) CPUs use AIX 5.2, 5.3, or 6.1.

❑ AIX 5.2 must be at Maintenance Level 5200-04, AIX 5.3 must be at Maintenance Level 5300-04 or 5300-07, and AIX 6.1 must be at Maintenance Level 6100-00.



Mounting the CD To mount the EMC Celerra MPFS installation CD:

1. Log in to the AIX server as root.

2. Create the directory /cdrom to be the mount point for the CD by typing:

mkdir /cdrom

3. Insert the CD into the CD drive.

4. Mount the CD on /cdrom using the following command:

mount -v cdrfs -p -r /dev/cd0 /cdrom





1. Mount the CD in the CD drive. “Mounting the CD” on page 88 provides more information.

2. Install the software using the following syntax:

installp -ac -gqX -d /cdrom/<directory_name> EMCmpfs

where <directory_name> specifies the version of the operating system running on the AIX server: AIX 5.2, AIX 5.3, or AIX 6.1

If the AIX server is running AIX 5.3, type:

installp -ac -gqX -d /cdrom/aix-53 EMCmpfs

The screen displays information about the installation and concludes with the following screen:

Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------EMCmpfs 4.0.23.0 USR APPLY SUCCESSEMCmpfs 4.0.23.0 ROOT APPLY SUCCESS

3. Unmount the CD by typing:

umount /cdrom

4. Remove the CD from the CD drive.

The MPFS software is now installed on the AIX server. For postinstallation information and instructions, “After installing” on page 92 provides more information.


90



To install the MPFS software from a compressed tar file, download the file from the EMC Powerlink website. Then, uncompress and extract the tar file on the AIX server and execute the installp command.

Use the following steps to install the MPFS software from the compressed tar file:

1. Create the directory /tmp/temp_mpfs if it does not already exist.



EMCmpfs.aix.4.0.23.0.tar.Z



cd /tmp/temp_mpfs




uncompress EMCmpfs.aix.4.0.23.0.tar.Z




tar -xvf EMCmpfs.aix.4.0.23.0.tar



7. Install the MPFS software by using the following syntax:

installp -ac -gqX -d /tmp/temp_mpfs/<directory_name> EMCmpfs

where <directory_name> specifies the version of the operating system running on the AIX server: AIX 5.2, AIX 5.3, or AIX 6.1

If the AIX server is running AIX 5.3, type:

installp -ac -gqX -d /tmp/temp_mpfs/aix-53 EMCmpfs

The screen displays information about the installation, and concludes with the following screen:

Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------EMCmpfs 4.0.23.0 USR APPLY SUCCESSEMCmpfs 4.0.23.0 ROOT APPLY SUCCESS

The MPFS software is now installed on the AIX server. For postinstallation information and instructions, “After installing” on page 92 provides more information.


92


After installingAfter you install the MPFS software, verify that it is installed properly. Then you can start the MPFS software by mounting a MPFS file system. This section describes these procedures.

Verifying the installation on an AIX server

Use the lslpp command to verify that the MPFS software was installed properly by typing:

lslpp -l EMCmpfs

If the MPFS software is installed properly, the command displays output similar to this:

Fileset Level State Description ---------------------------------------------------------------------------- Path: /usr/lib/objrepos EMCmpfs 4.0.23.0 COMMITTED EMC MPFS Filesystem Path: /etc/objrepos EMCmpfs 4.0.23.0 COMMITTED EMC MPFS Filesystem



Mounting a MPFS file system on an AIX server

To start an AIX server, establish a session, that is, a connection between the AIX server and the Celerra Network Server. Establish a session by mounting the MPFS file system on the AIX server using the mount(1) command.

To mount a MPFS file system, use the mount(1) command with the following syntax:

mount -v mpfs -o <MPFS_specific_options> <servername>:/FS_export mount_point

where:

<MPFS_specific_options> is a comma-separated list (without spaces) of arguments to the -o option that are supported by the EMC Celerra MPFS Multiplex File System. All arguments to the -o option that are supported by the NFS mount command are also supported by EMC Celerra MPFS. EMC Celerra MPFS also supports several additional arguments. The man page for mount_mpfs(1) provides a complete list of supported arguments.

<servername> is the name of an EMC Celerra MPFS File Server.FS_export is the absolute pathname of the directory exported on the EMC Celerra MPFS File Server.

mount_point is the absolute pathname of the directory on which to mount the MPFS file system on the AIX server.

For example, the following command mounts an MPFS file system:

mount -v mpfs server1:/src /usr/src

Verifying that thedaemon has started

Once an MPFS file system is mounted, use the ps command to verify the MPFS daemon has started by typing:

ps -ef | grep mpfsd

The output should look like this:

root 10284 13604 2 10:43:16 pts/2 0:00 grep mpfsd root 11744 1 0 Aug 11 - 0:00 /usr/sbin/mpfsd -q

After installing 93

94


Migrating from an earlier releaseThe migration procedure described in this section assumes you are upgrading both the AIX operating system and the MPFS software. If you are not upgrading the AIX operating system, ignore steps 3 through 6 and 12.

Note: If you are not upgrading the AIX operating system, you must reboot the AIX server before installing the new version of the MPFS software.

The procedure also assumes that PowerPath is installed on the AIX server and you wish to upgrade PowerPath. If this is not true, ignore steps 5, 8, 10, and 11.

To migrate from an earlier release of MPFS software, follow this procedure:

1. Ensure that your EMC Customer Service Engineer has upgraded the AIX server to the correct version. Be sure to read the Client-Server Compatibility section in the Celerra MPFS for AIX Clients Release Notes before upgrading the MPFS software.

2. Stop I/O and unmount all MPFS file systems.

3. For MPFS file systems mounted when the AIX server is booted, back up appropriate automounter maps and /etc/filesystems, and change all MPFS mpfs mount-on-boot file system information to mount using NFS.

4. Uninstall the earlier version of the MPFS software “Uninstalling the MPFS software” on page 96 provides detailed information.

5. Uninstall PowerPath. The PowerPath documentation for the version of PowerPath installed on the AIX server provides more detailed information.

6. Install the new version of the AIX operating system. AIX documentation should provide more detailed information for this task.

Note: If you are not installing a new version of the AIX operating system, reboot the AIX server before you install the new version of the MPFS software.



7. Download, uncompress, and install the latest ODM definitions fileset appropriate to the new version of the AIX operating system. “Before installing” on page 86 provides more information.

Note: If you are using EMC Fibre Channel drivers, switch to IBM Fibre Channel drivers.

8. Install the new version of PowerPath. Chapter 3, ”Installing PowerPath with MPFS”, provides more detailed information.

9. Install the new version of the MPFS software. “Installing the MPFS software” on page 88 provides more detailed information.

10. Rediscover the disks by typing:

emc_cfsmgr.sh

11. Configure PowerPath. Documentation about PowerPath is available on the EMC Powerlink website.

12. Restore the automounter maps and /etc/filesystems, or change appropriate NFS-mount-on-boot information to mpfs.

13. Mount the MPFS file systems. “Mounting a MPFS file system on an AIX server” on page 93 provides more detailed information.

14. Resume I/O.

Migrating from an earlier release 95

96



1. Log in to the AIX server as root.

2. Ensure that no MPFS mounts are active by unmounting all mounted MPFS file systems by typing:

umount <local_path>

where <local_path> is the absolute pathname of the directory on which the MPFS file system is mounted.

3. For MPFS file systems mounted when the AIX server is booted, back up appropriate automounter maps and /etc/filesystems, and change all MPFS (mpfs) mount-on-boot file system information to mount using NFS.

4. Remove the MPFS software by typing:

installp -u EMCmpfs

The screen displays information about the removal, and concludes with the following screen:

Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------EMCmpfs 4.0.22.0 ROOT DEINSTALL SUCCESSEMCmpfs 4.0.22.0 USR DEINSTALL SUCCESS

Note: EMC recommends rebooting the AIX server after uninstalling the MPFS software.


6

This chapter describes how to install and uninstall MPFS software on a Solaris server.


◆ Before installing.................................................................................. 98◆ Installing the MPFS software ......................................................... 101◆ After installing.................................................................................. 109◆ Migrating from an earlier release .................................................. 110◆ Uninstalling the MPFS software ..................................................... 111

Installing the MPFSSoftware on a Solaris

Server

Installing the MPFS Software on a Solaris Server 97

98

Installing the MPFS Software on a Solaris Server



MPFS software Verify that the Solaris server on which you plan to install the MPFS software:

❑ Has the required patches, as follows:

• Solaris 5.8—patch level 117350-43 (or later)

• Solaris 5.9—patch level 113278-21 (or later)

• Solaris 5.10 x86—patch level 137138-09 (or later)

• Solaris 5.10 SPARC—patch level 137137-09 (or later)

❑ Meets the hardware, software, and MPFS configuration requirements specified in the Celerra MPFS for HP-UX and Solaris Clients Release Notes.

❑ Has been set to single-user mode before installing MPFS. At a minimum, unmount all NFS shares before beginning the installation.

❑ Has a direct Fibre Channel connection to the storage array, and that the storage array meets the hardware and software requirements specified in the Celerra MPFS for HP-UX and Solaris Clients Release Notes. The EMC Customer Support Representative configures the Symmetrix or CLARiiON storage array and establishes the connection between the Solaris server and the storage array.





Storage system On the storage system, ensure that:

❑ File systems used for MPFS do not contain both CLARiiON and Symmetrix LUNs. MPFS does not support a mixed storage system environment.

❑ In a Symmetrix environment, the Symmetrix Fibre Channel port flag settings are properly configured for the EMC Celerra MPFS; in particular, that the ARB flag is set. Your EMC Customer Support Representative configures these settings.

❑ The Solaris server has been configured to incorporate the Symmetrix or CLARiiON disk devices into Solaris and make the devices visible from the Solaris server. The CLARiiON or Symmetrix devices must be properly configured on the Fibre Channel using Fibre Channel port addresses. The EMC Host Connectivity guides, available on the EMC Powerlink website (http://Powerlink.EMC.com), provide more information.

CAUTION!Incorporating CLARiiON or Symmetrix devices may involve rebooting the server; therefore, make sure that all applications are closed and all users are logged off before you configure the server.




100


Label disks Label any disks to be used with the MPFS file system:

1. Use the format (1M) command to label any unlabeled disks to be used with the MPFS file system.

Note: Perform step 1 before installing the MPFS software.

2. Install the MPFS software as described in “Installing the MPFS software” on page 101.

3. Use the mpfslabel command to relabel all disks to be used with the MPFS file system.

Use the following command syntax:

mpfslabel <disk>

where <disk> is the name of the disk to relabel.

For example:

mpfslabel /dev/rdsk/c1t0d16s2

The mpfslabel command allows Solaris to access the entire raw disk, including the last two cylinders, which are typically reserved as alternate cylinders by the format utility.



Installing the MPFS softwareThe MPFS software can be installed directly from the EMC MPFS for UNIX/HP/Sun Client Software CD by using the CLI or from a compressed tar file on the EMC Powerlink website.





Before installing Before you install the MPFS software, read the prerequisites for the Solaris server and storage array, listed in this section:




CAUTION!Before you install the MPFS software, you must install the Solaris patch on the Solaris server.


102




1. Log in to the Solaris server as root.

2. Insert the CD into the CD drive:

• If the CR-ROM mounts automatically, go to step 4.

• If the CR-ROM does not mount automatically, you must mount it manually. Go to step 3.

3. Mount the CD using the following command syntax:

mount -F hsfs -o ro /dev/dsk/c<x>t<y>d<z>s0 /cdrom

where <x>, <y>, and <z> are values specific to the server’s CD drive.

For example:

mount -F hsfs -o ro /dev/dsk/c0t2d0s0 /cdrom

4. Run the pkgadd utility to install the MPFS software. Use this command syntax:

/usr/sbin/pkgadd -d /cdrom/<directory_name>

where <directory_name> specifies the version of the operating system running on the Solaris server: sunos-sparc-5.8, sunos-sparc-5.9, sunos-sparc-5.10, or sunos-i386-5.10

For example, if the server is running SunOS 5.8, type:

/usr/sbin/pkgadd -d /cdrom/sunos-sparc-5.8 EMCmpfs

You see the following output:

Processing package instance <EMCmpfs> from </cdrom/sunos-sparc-5.8>

EMC MPFS Filesystem(SPARC) 4.0----------------------------------EMC CorporationCopyright 1999, 2000, 2001All rights reserved.----------------------------------## Executing checkinstall script.Using </etc/fs> as the package base directory.## Processing package information.## Processing system information. 27 package pathnames are already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.



## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.

Do you want to continue with the installation of <EMCmpfs> [y,n,?] y

5. Type y and press Return. The installation proceeds displaying the following output:

Installing EMC MPFS Filesystem as <EMCmpfs>

## Executing preinstall script.## Installing part 1 of 1./etc/fs/mpfs/isaexec/etc/fs/mpfs/modify_vfstab.awk/etc/fs/mpfs/restore_vfstab.awk/etc/fs/mpfs/sparcv7/mount/etc/fs/mpfs/sparcv7/mpfsd/etc/fs/mpfs/sparcv7/mpfsperfd/etc/fs/mpfs/sparcv9/mount/etc/fs/mpfs/sparcv9/mpfsd/etc/fs/mpfs/sparcv9/mpfsperfd/etc/init.d/hrdp/etc/init.d/mpfs/kernel/drv/emchrdp/kernel/drv/emchrdp.conf/kernel/drv/mpfs/kernel/drv/mpfs.conf/kernel/drv/sparcv9/emchrdp/kernel/drv/sparcv9/mpfs/usr/bin/mpfsinterp/usr/bin/sparcv7/mpfscollect/usr/bin/sparcv9/mpfscollect/usr/lib/adb/fileextent/usr/lib/adb/fileextentlist/usr/lib/adb/sparcv9/fileextent/usr/lib/adb/sparcv9/fileextentlist/usr/lib/fs/mpfs/sparcv7/mount/usr/lib/fs/mpfs/sparcv9/mount/usr/sbin/mpfslabel/usr/sbin/sparcv7/hrdp/usr/sbin/sparcv7/mpfsctl/usr/sbin/sparcv7/mpfsdiscover/usr/sbin/sparcv7/mpfsinq/usr/sbin/sparcv7/mpfsquota/usr/sbin/sparcv7/mpfsstat/usr/sbin/sparcv9/hrdp/usr/sbin/sparcv9/mpfsctl/usr/sbin/sparcv9/mpfsdiscover/usr/sbin/sparcv9/mpfsinq


104


/usr/sbin/sparcv9/mpfsquota/usr/sbin/sparcv9/mpfsstat/usr/share/man/man1/mount_mpfs.1/usr/share/man/man1/mpfsctl.1/usr/share/man/man1/mpfsd.1/usr/share/man/man1/mpfsdiscover.1/usr/share/man/man1/mpfslabel.1/usr/share/man/man1/mpfsquota.1/usr/share/man/man1/mpfsstat.1/usr/share/man/man7/mpfs.7[ verifying class <none> ]/etc/fs/mpfs/mount <linked pathname>/etc/fs/mpfs/mpfsd <linked pathname>/etc/fs/mpfs/mpfsperfd <linked pathname>/etc/rc0.d/K10hrdp <linked pathname>/etc/rc1.d/S00mpfs <linked pathname>/etc/rc2.d/S00mpfs <linked pathname>/etc/rc2.d/S77mpfs <linked pathname>/etc/rc3.d/S99hrdp <linked pathname>/kernel/fs/mpfs <linked pathname>/kernel/fs/sparcv9/mpfs <linked pathname>/usr/bin/mpfscollect <linked pathname>/usr/lib/fs/mpfs/mount <linked pathname>/usr/sbin/hrdp <linked pathname>/usr/sbin/mpfsctl <linked pathname>/usr/sbin/mpfsdiscover <linked pathname>/usr/sbin/mpfsinq <linked pathname>/usr/sbin/mpfsquota <linked pathname>/usr/sbin/mpfsstat <linked pathname>## Executing postinstall script.** Changed lwp_default_stksize** If you plan to install EMC PowerPath software, please remove the* MPFS package, install PowerPath, and then re-install MPFS* Otherwise, please reboot the system for changes to take effect*Protecting Celerra disks...Running mpfsdiscover...Installation is done. No Reboot is required.

Installation of <EMCmpfs> was successful.

6. Relabel all disks as described in step 3 of “Label disks” on page 100.




To install the MPFS software from a compressed tar file, download the file from the EMC Powerlink website. Then, uncompress and extract the tar file on the Solaris server and use the pkgadd utility.

Use the following steps to install the MPFS software from the compressed tar file:

1. Create the directory /tmp if it does not already exist.



EMCmpfs.sunos.sparc.4.0.23.0.tar.Z


4. Change to the /tmp directory:

cd /tmp




uncompress EMCmpfs.sunos.sparc.4.0.23.0.tar.Z




tar -xvf EMCmpfs.sunos.sparc.4.0.23.0.tar

7. Run the pkgadd utility to install the MPFS software using the following command syntax:

/usr/sbin/pkgadd -d /tmp/<directory_name>

where <directory_name> specifies the version of the operating system running on the Solaris server: sunos-sparc-5.8, sunos-sparc-5.9, sunos-sparc-5.10, or sunos-i386-5.10.


106


For example, if the server is running SunOS 5.8, type:

/usr/sbin/pkgadd -d /tmp/sunos-sparc-5.8 EMCmpfs

You see the following output:

Processing package instance <EMCmpfs> from </tmp/sunos-sparc-5.8>

EMC MPFS Filesystem(SPARC) 4.0----------------------------------EMC CorporationCopyright 1999, 2000, 2001All rights reserved.----------------------------------## Executing checkinstall script.Using </etc/fs> as the package base directory.## Processing package information.## Processing system information. 27 package pathnames are already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.


8. Type y and press Return. The installation proceeds displaying the following output:

Installing EMC MPFS Filesystem as <EMCmpfs>

## Executing preinstall script.## Installing part 1 of 1./etc/fs/mpfs/isaexec/etc/fs/mpfs/modify_vfstab.awk/etc/fs/mpfs/restore_vfstab.awk/etc/fs/mpfs/sparcv7/mount/etc/fs/mpfs/sparcv7/mpfsd/etc/fs/mpfs/sparcv7/mpfsperfd/etc/fs/mpfs/sparcv9/mount/etc/fs/mpfs/sparcv9/mpfsd/etc/fs/mpfs/sparcv9/mpfsperfd/etc/init.d/hrdp/etc/init.d/mpfs/kernel/drv/emchrdp/kernel/drv/emchrdp.conf/kernel/drv/mpfs/kernel/drv/mpfs.conf/kernel/drv/sparcv9/emchrdp



/kernel/drv/sparcv9/mpfs/usr/bin/mpfsinterp/usr/bin/sparcv7/mpfscollect/usr/bin/sparcv9/mpfscollect/usr/lib/adb/fileextent/usr/lib/adb/fileextentlist/usr/lib/adb/sparcv9/fileextent/usr/lib/adb/sparcv9/fileextentlist/usr/lib/fs/mpfs/sparcv7/mount/usr/lib/fs/mpfs/sparcv9/mount/usr/sbin/mpfslabel/usr/sbin/sparcv7/hrdp/usr/sbin/sparcv7/mpfsctl/usr/sbin/sparcv7/mpfsdiscover/usr/sbin/sparcv7/mpfsinq/usr/sbin/sparcv7/mpfsquota/usr/sbin/sparcv7/mpfsstat/usr/sbin/sparcv9/hrdp/usr/sbin/sparcv9/mpfsctl/usr/sbin/sparcv9/mpfsdiscover/usr/sbin/sparcv9/mpfsinq/usr/sbin/sparcv9/mpfsquota/usr/sbin/sparcv9/mpfsstat/usr/share/man/man1/mount_mpfs.1/usr/share/man/man1/mpfsctl.1/usr/share/man/man1/mpfsd.1/usr/share/man/man1/mpfsdiscover.1/usr/share/man/man1/mpfslabel.1/usr/share/man/man1/mpfsquota.1/usr/share/man/man1/mpfsstat.1/usr/share/man/man7/mpfs.7[ verifying class <none> ]/etc/fs/mpfs/mount <linked pathname>/etc/fs/mpfs/mpfsd <linked pathname>/etc/fs/mpfs/mpfsperfd <linked pathname>/etc/rc0.d/K10hrdp <linked pathname>/etc/rc1.d/S00mpfs <linked pathname>/etc/rc2.d/S00mpfs <linked pathname>/etc/rc2.d/S77mpfs <linked pathname>/etc/rc3.d/S99hrdp <linked pathname>/kernel/fs/mpfs <linked pathname>/kernel/fs/sparcv9/mpfs <linked pathname>/usr/bin/mpfscollect <linked pathname>/usr/lib/fs/mpfs/mount <linked pathname>/usr/sbin/hrdp <linked pathname>/usr/sbin/mpfsctl <linked pathname>/usr/sbin/mpfsdiscover <linked pathname>/usr/sbin/mpfsinq <linked pathname>/usr/sbin/mpfsquota <linked pathname>/usr/sbin/mpfsstat <linked pathname>## Executing postinstall script.


108


** Changed lwp_default_stksize** If you plan to install EMC PowerPath software, please remove the* MPFS package, install PowerPath, and then re-install MPFS* Otherwise, please reboot the system for changes to take effect*Protecting Celerra disks...Running mpfsdiscover...Installation is done. No Reboot is required.

Installation of <EMCmpfs> was successful.

9. Relabel all disks as described in step 3 of “Label disks” on page 100.



After installingAfter you install the MPFS software, you should verify that it is installed properly and that the MPFS daemon started. This section describes these procedures.

Verifying the installation on a Solaris server

To verify that the MPFS software was installed and the MPFS daemon was started:

1. Run the pkginfo utility to verify the installation. Type:

pkginfo -l EMCmpfs

If the MPFS software was installed properly, the command displays output similar to this:

PKGINST: EMCmpfsNAME: EMC MPFS FilesystemCATEGORY: systemARCH: SPARCVERSION: 4.0BASEDIR: /etc/fsVENDOR: EMC CorporationPSTAMP: 4.0.23_b0INSTDATE: Sept 14 2009 17:59STATUS: completely installedFILES: 98 installed pathnames

26 shared pathnames18 linked files33 directories35 executables2290 blocks used (approx)

2. Type the ps command to verify that the MPFS daemon has started:

ps -ef | grep mpfsd

The output should look like this:

root 386 1 0 12:03:29 ? 0:00 /etc/fs/mpfs/mpfsdroot 884 867 0 11:13:42 pts/0 0:00 grep mpfsd

“Mounting an MPFS file system” on page 115 provides more information about mounting a file system after verifying that MPFS has been installed and running.

After installing 109

110


Migrating from an earlier releaseWhen migrating from an earlier release of the MPFS software, uninstall the earlier release of the MPFS software before installing the new software. “Uninstalling the MPFS software” provides details.




1. Log in to the Solaris server as root.

2. Make sure that no MPFS mounts are active by unmounting all mounted MPFS file systems. Use the following command syntax:

umount <local_path>

where <local_path> is the absolute pathname of the directory on which the MPFS file system is mounted.

3. Run the pkgrm utility to uninstall the MPFS software by typing:

pkgrm EMCmpfs

The following prompt appears:

The following package is currently installed:EMCmpfs EMC MPFS Fileystem

(SPARC) 4.0

Do you want to remove this package:

4. Type y and press Return.

You see the following prompt:

## Removing installed package instance <EMCmpfs>

This package contains scripts which will be executed with super-userpermission during the process of removing this package.

Do you want to continue with the removal of this package [y,n,?,q]

5. Type y and press Return.

After the MPFS software is removed, the following message appears:

Removal of <EMCmpfs> was successful.

Uninstalling the MPFS software 111

112



7

This chapter describes the mpfsctl utility and mpfs commands, which you can use to manage and tune a HP-UX, AIX, or Solaris server. This chapter covers the following topics:

◆ Overview of the command line interface ..................................... 114◆ Mounting an MPFS file system...................................................... 115◆ Resuming I/O through MPFS........................................................ 117◆ Displaying mpfsctl commands ...................................................... 118◆ Setting the number of blocks to prefetch...................................... 119◆ Resetting the counters ..................................................................... 120◆ Enabling read/write interception (Solaris only) ......................... 121◆ Displaying statistics ......................................................................... 122◆ Improving client read performance (HP-UX 11.31 only) ........... 124◆ Setting synchronization before using noac (AIX only)............... 125◆ Displaying the MPFS version number.......................................... 126◆ Displaying the disk quota............................................................... 127◆ Displaying MPFS devices ............................................................... 128

MPFS Command LineInterface

MPFS Command Line Interface 113

114

MPFS Command Line Interface

Overview of the command line interfaceThe MPFS Control Program, mpfsctl, is a command line utility that can be used by MPFS system administrators to troubleshoot and fine- tune their systems. The mpfsctl utility resides in the following directory:

◆ /usr/sbin — Solaris servers

◆ /usr/sbin — AIX servers

◆ /opt/EMCmpfs/bin — HP-UX server

Table 7 on page 114 lists the mount, mpfsctl, and mpfs commands.

Table 7 Command Line Interface summary

Command Refer to

mount mpfs “Mounting an MPFS file system” on page 115

mpfsctl diskreset “Resuming I/O through MPFS” on page 117

mpfsctl help “Displaying mpfsctl commands” on page 118

mpfsctl prefetch “Setting the number of blocks to prefetch” on page 119

mpfsctl reset “Resetting the counters” on page 120

mpfsctl rwint “Enabling read/write interception (Solaris only)” on page 121

mpfsctl stats “Displaying statistics” on page 122

mpfsctl sync-attr “Improving client read performance (HP-UX 11.31 only)” on page 124

mpfsctl use-sync 1 “Setting synchronization before using noac (AIX only)” on page 125

mpfsctl version “Displaying the MPFS version number” on page 126

mpfsquota “Displaying the disk quota” on page 127

mpfsinq “Displaying MPFS devices” on page 128



Mounting an MPFS file systemTo start an HP-UX, AIX, or Solaris server you must establish a session, that is, a connection between the HP-UX, AIX, or Solaris server and an Celerra Network Server. You establish a session by mounting the MPFS file system on the HP-UX, AIX, or Solaris server using the mount command.

To mount an MPFS file system on a HP-UX or Solaris server, use the mount command with the following syntax:

mount -F mpfs [-o <MPFS_specific_options>] <movername> :/<mount_point> <FS_export> <local_path>

To mount an MPFS file system on an AIX server, use the mount command with the following syntax:

mount -V mpfs [-o <MPFS_specific_options>] <movername> :/<mount_point> <FS_export> <local_path>

where:

◆ <MPFS_specific_options> is a comma-separated list (without spaces) of arguments to the -o option that are supported by the EMC Celerra MPFS. Most arguments to the -o option that are supported by the NFS mount command (see the mount_nfs man page) are also supported by EMC Celerra MPFS. EMC Celerra MPFS also supports the following additional arguments:

• -o mpfs_verbose — Executes the mount command in verbose mode. If the mount succeeds, the list of disk signatures used by the MPFS volume is printed on standard output.

• -o mpfs_keep_nfs — If the mount using MPFS fails, the file system is mounted using NFS instead. Warning messages inform the user that the MPFS mount failed.

• -o mpfs_min_size=<x> — Use NFS for all reads to files that are smaller than x. The default is 32 KB. <x> can be expressed in blocks (b or B), kilobytes (k or K), or megabytes (m or M), for example, 64K (64 kilobytes), 2m (2 megabytes).

Note: For optimal performance, set the rsize and wsize arguments to 32768, as shown in the example that follows.

◆ <movername> = name of an Celerra Network Server, also called the Data Mover.

Mounting an MPFS file system 115

116


◆ <mount_point> = absolute pathname of the directory on which to mount the MPFS file system on the HP-UX, AIX, or Solaris server.

◆ <FS_export> = absolute pathname of the directory that is exported on the Celerra Network Server.

◆ <local_path> = absolute pathname of the directory at which to attach the MPFS file system on the HP-UX, AIX, or Solaris server.

For example, the following command mounts an MPFS file system; the mpfs_keep_nfs option causes the file system to be mounted using NFS if the mount using MPFS fails:

mount -F mpfs -o mpfs_keep_nfs,rsize=32768,wsize=32768 server1:/src /usr/src

Note: You can add MPFS file systems to the /etc/fstab file so that they are mounted automatically after the server is rebooted or shut down.

This command produces no system response.



Resuming I/O through MPFSUse the mpfsctl diskreset command to resume I/O through MPFS after a disk connection is lost.


mpfsctl diskreset

When the Fibre Channel connection between the HP-UX, AIX, or Solaris server and the storage disk device is lost, I/O for an open file falls through to NFS. After you have restored the connection, run mpfsctl diskreset to allow I/O to resume through MPFS for all open files.

This command produces no system response. When the command has finished executing, only the command line prompt is returned.

Resuming I/O through MPFS 117

118


Displaying mpfsctl commandsUse the mpfsctl help command to display a list of mpfsctl commands.


mpfsctl help

The output is:

Usage: mpfsctl op ...Operations supported (arguments in parentheses): help print this list prefetch set number of blocks to prefetch reset reset statistics diskreset resets disk connections srdf add alias for SRDF volume (R2ID, R1ID) stats print statistics version display product compile time stamp rwint enable/disable read/write intercept

Note: EMC SRDF®, which is a Symmetrix feature, is not supported in EMC MPFS Version 4.0.



Setting the number of blocks to prefetchUse the mpfsctl prefetch command to set the number of blocks of metadata to prefetch.


mpfsctl prefetch <blocks>

where:

<blocks> = an integer between 4 and 4096 that specifies the number of blocks to prefetch. The default is 128.

A block contains 8 KB of user data. Thus, you can prefetch 32 KB (4 blocks) of metadata and 32 MB (4096 blocks) of user data.

The default is 128 blocks, or 1 MB of metadata. Performance analysis has proven 128 to be the best number for a variety of work loads. Thus, you are encouraged to leave this value unchanged. Nevertheless, mpfsctl prefetch is available for situations in which it might allow you to tune MPFS for higher performance.

Changing the prefetch value does not affect current MPFS mounts; it affects only subsequent mounts.


Setting the number of blocks to prefetch 119

120


Resetting the countersUse the mpfsctl reset command to reset the counters for the mpfsctl stats command. “Displaying statistics” on page 122 provides more information.

By default, statistics accumulate until you reboot the system. Use mpfsctl reset to reset the counters to 0 before executing mpfsctl stats.


mpfsctl reset

This command produces no system response. When the command has finished executing, only the command line prompt is returned.



Enabling read/write interception (Solaris only)Use the mpfsctl rwint command to enable read/write interception when your application is locking files and experiencing poor performance.


mpfsctl rwint 1 — Enable read/write interception

mpfsctl rwint 0 — Disable read/write interception

Reads and writes on unlocked files are cached inside the kernel and then read or written asynchronously at a convenient time. When files are locked, however, reads and writes are not cached but rather are done directly. In this case, the HP-UX, AIX, or Solaris server waits until the I/O completes before returning control to the application, and performance suffers.

A Solaris performance limitation causes uncached writes to be done in 8 KB chunks. Enabling read/write interception with mpfsctl rwint 1 circumvents this limitation, letting MPFS write data at the size specified in the write system call (up to 64 KB) and thus improving performance somewhat in applications that cannot avoid locking files.


Enabling read/write interception (Solaris only) 121

122


Displaying statisticsUse the mpfsctl stats command to display a set of statistics showing the internal operation of the HP-UX, AIX, or Solaris server. By default, statistics accumulate until you reboot the system. Use mpfsctl reset to reset the counters to 0 before executing mpfsctl stats. “Resetting the counters” on page 120 provides more information.

The output of the mpfsctl stats command can help EMC Customer Support Representatives pinpoint certain performance problems.

To display MPFS statistics, type:

mpfsctl stats

The output is:

=== OS INTERFACE8534 reads totalling 107683852 bytes4974 writes totalling 74902093 bytes25 commits, 14 setattributes, 2 getattribute fixups4 fallthroughs involving 28 bytes

=== EXTENT CACHE8364 read-cache hits (97%)3111 write-cache hits (62%)

=== NETWORK INTERFACE188 open messages, 187 closes178 getmap, 1897 allocspace825 flushes of 1618 extents and 9283 blocks, 43 releases1 notify messages

=== ERRORS0 WRONG_MSG_NUM, 0 QUEUE_FULL 0 INVALIDARG0 client-detected sequence errors0 RPC errors, 0 other errors



Understanding the statistics output

The information contained in the four sections of output is explained as follows:

OS INTERFACE — The first three lines show the number of NFS message types that the EMC Celerra MPFS either handles (reads and writes) or watches and augments (commits, setattributes, and getattributes).

The last line shows the number of fallthroughs, that is, reads and writes attempted over MPFS but accomplished over NFS. The number of fallthroughs should be small. A large number of fallthroughs indicates that you are not using the MPFS file system to full advantage.

EXTENT CACHE — These lines show the cache hit rates. A low percentage (such as the percentage of write-cache hits in this example) indicates heavy network traffic. Contact EMC Customer Support for advice on increasing your cache capacity.

NETWORK INTERFACE — These lines show the number of FMP messages used—in this example, a total of 1244.

Compare this number to the total of 13,549 messages in the OS INTERFACE section—that is the number that NFS would use if the MPFS file system was not installed. The better than 10:1 ratio indicates the MPFS improvement over NFS.

The number of blocks (9283) per flush (825) is also significant: Coalescing multiple blocks into a single flush is a major part of the MPFS strategy for reducing message traffic.

ERRORS — This section shows both serious errors and errors that are completely recoverable. The only serious errors are those described as either RPC or other errors. Contact EMC Customer Support if the number of serious errors is significantly greater than 0.

Displaying statistics 123

124


Improving client read performance (HP-UX 11.31 only)Use the mpfsctl sync-attr command to enable attribute cache to improve client/process read performance.


mpfsctl sync-attr 1 — Enable attribute cache

mpfsctl sync-attr 0 — Disable attribute cache

Read performance is affected by file attributes being cached. File access times can be out of date until the cache gets refreshed. Enabling attribute cache in MPFS retains file attributes on the client. This improves read performance since file attributes are assigned a time to be flushed.




Setting synchronization before using noac (AIX only)Use the mpfsctl use-sync 1 command to set synchronization before using the No Attribute Caching (noac) option to mount the MPFS file system on an AIX server. This allows the MPFS client to skip a query of a cached list of attributes on the NFS client and get them directly from the NFS server.


mpfsctl use-sync 1


Setting synchronization before using noac (AIX only) 125

126


Displaying the MPFS version numberUse the mpfsctl version command to display the version number of the EMC Celerra MPFS kernel driver.


mpfsctl version

The output for the HP-UX server is:

version:EMCmpfs.hp-ux.4.0.23.0 (cal-proj@eng123456), Tue Mar 17, 2009 05:51:55 PM

The output for the AIX server is:

version:EMCmpfs.aix.4.0.23.0 (cal-proj@eng123456), Tue Mar 17 18:45:00 EDT 2009

The output for the Solaris server is:

version:EMCmpfs.sunos.sparc.4.0.23.0 (cal-proj@eng123456), Tue Mar 17 16:25:34 EDT 2009



Displaying the disk quotaUse the mpfsquota command to display a user’s MPFS file system disk quota and usage. You must be superuser to use the optional username argument and view the limits of other users. Without options, mpfsquota displays warnings about mounted file systems where usage is over quota. Remote mounted file systems that do not have quotas turned on are ignored.


mpfsquota [-v] <username>

where:<username> = can be a user’s numeric UID

mpfsquota -v

Displays all MPFS mounted file systems where quotas exist.

Displaying the disk quota 127

128


Displaying MPFS devicesThe mpfsinq command allows you to display MPFS devices. It displays storage devices and device IDs, along with the path where disks are mapped.

Note: The mpfsinq command provides functionality that the mpfsdiscover command provided in previous releases.

PowerPath is required for MPFS systems using CLARiiON storage arrays. Therefore, MPFS only uses PowerPath pseudo devices (/dev/hdiskpower<xx>) and not native devices (/dev/hdisk<xx>).

If you attempt to use a CLARiiON storage array without installing PowerPath, users will not be able to mount disks or use mpfsdiscover or mpfsinq to discover disks. When Symmetrix storage arrays are used, PowerPath is not required and MPFS can use native devices:

◆ On an HP-UX server, to display MPFS device names, type:

/sbin/fs/mpfs/mpfsinq

◆ On a AIX server, to display MPFS devices, type:

/usr/sbin/mpfsinq

◆ On a Solaris server, to display MPFS devices, type:

/usr/sbin/mpfsinq



The output looks similar to this:

/dev/dsk/c6t0d0: Signature 1 = unrecognized/dev/dsk/c6t0d0: Signature 2 = unrecognized

/dev/dsk/c7t0d0: Signature 1 = unrecognized/dev/dsk/c7t0d0: Signature 2 = unrecognized

/dev/dsk/c7t2d0: Signature 1 = 12/dev/dsk/c7t2d0: Signature 2 = APM0003240328900




Note: When the signature is "unrecognized," this indicates that the disk is not configured for MPFS.

Displaying MPFS devices 129

130



AInvisible Body Tag

This appendix describes messages that the HP-UX server writes to the system error log and troubleshooting problems, causes, and solutions for HP-UX, AIX, and Solaris servers. This chapter includes the following topics:

◆ HP-UX server error messages ........................................................ 132◆ Troubleshooting the HP-UX server ............................................... 133◆ Troubleshooting the AIX server ..................................................... 138◆ Troubleshooting the Solaris server ................................................ 147

Error Messages andTroubleshooting

Error Messages and Troubleshooting 131

132

Error Messages and Troubleshooting

HP-UX server error messagesTable 8 on page 132 describes HP-UX server error messages.

Table 8 HP-UX server error messages

Message Explanation

notification error on session create The session was not created. Verify that the mpfsd process is running.

session to server lost The HP-UX, AIX, or Solaris server has lost contact with the Celerra Network Server. This loss of contact is probably due to a network or server problem and not an I/O error.

<server_name> session expired now=<time>, expiration=<time>

reestablished session OK The first message indicates that the HP-UX server has reestablished contact with the Celerra Network Server. The second indicates that some attempt at reestablishing contact has been made but has not succeeded. Neither message indicates an I/O error.

handles may have been lost

could not find the disk signature for <nnnnn>

(<nnnnn> is the five-digit disk signature)The Celerra Network Server specified a storage location, <nnnnn>, that is inaccessible from the HP-UX server.

could not start <xxx> thread (<xxx> is a component of the HP-UX server)

A component of the HP-UX server failed to start.

could not find nfs The HP-UX server could not locate an installed NFS Server. (The HP-UX server cannot function without an installed NFS Server.)

error accessing volume. I/O routed to LAN This message is printed in the log file when the Celerra Network Server receives an error message while communicating with the Symmetrix storage array over Fibre Channel. All subsequent I/O operations for the file are done over NFS until the file is reopened. After the file is reopened, the Fibre Channel SAN path is retried.

could not find disk. Signature 1=<xxx> Signature 2=<xxxxxxx>

This message is printed in the log file when the file system has attempted to be mounted and one or more disks are missing.



Troubleshooting the HP-UX serverThis section describes potential problems with the HP-UX server.

Refer to the Celerra MPFS for HP-UX and Solaris Clients Release Notes for additional information on troubleshooting, known problems and limitations.

Mounting and unmounting

You might encounter the following problems in mounting or unmounting a file system.

Problem The mount command retries indefinitely.

Cause 1The server you specified with the mount command does not exist, cannot be reached, or is down.

If this is the case, you see messages similar to this:

nfs mount: get_fh: <hostname>:: RPC: Unknown hostError mounting nfs partition <hostname>:/<filesystem>

Solution 11. Interrupt the mount command using the interrupt key

combinations (usually Ctrl-C).

2. Try to reach the server using the ping command.

3. If the ping command succeeds, retry the mount.

Cause 2The file system you specified does not exist or is not exported.


No such file or directoryError mounting nfs partition <hostname>:/<filesystem>

Solution 2Use the showmount command to make sure that the file system exists on the server and is exported with the correct access permissions. Type:

showmount -e <hostname>

Troubleshooting the HP-UX server 133

134


Problem The mount command displays messages about unknown file systems.

CauseYou specified an option that is not supported by the mount command.

Solution1. Display the mount_mpfs man page to find supported options;

type:

man mount_mpfs

2. Run the mount command again with the correct options.

Problem The mount command displays this message:

mount: must be root to use mount

CauseYou lack the permissions required to use the mount command.

SolutionLog in as root and try the mount command again.


nfs mount: get_fh: <hostname>:: RPC: Rpcbind failure - RPC: Timed out

CauseThe MPFS or NFS server you specified is down.

SolutionCheck that you specified the correct server name and that the server is up and has an exported file system.

Problem The mount command logs a message similar to the following in the system message log files:

mount command errors with:Physical Volume with serial number '82005' not found.in syslog:Aug 11 13:36:16 <hostname> unix: could not find device for <82005>

CauseThe MPFS mount operation could not find the physical disk associated with the specified file system.



SolutionUse either the mpfsinq command or the mount -o rescan command, to verify that the physical disk device associated with the file system is connected to the server over Fibre Channel and is accessible from the server.

Problem The mount command displays a message similar to this:

mount: /<filesystem>: No such file or directory

CauseNo mount point exists.

SolutionCreate a mount point and try the mount again.

Problem The mount command displays the following message:

mount: mpfs : Invalid argumentusage: mount [-l][-v|-p] mount [-F FStype][-eQ] -a mount [-F FStype][-eQrV][-o specific_options] { special | directory } mount [-F FStype][-eQrV][-o specific_options] special directory

CauseThe HP-UX, AIX, or Solaris server is not installed.

SolutionInstall the HP-UX, AIX, or Solaris server and try the mount again.

Problem You cannot unmount a file system. The umount command displays the following message:

umount: Device busy

CauseExisting processes were using the file system when you attempted to unmount it, or the unmount command was issued from the file system itself.

Solution1. Use the fuser command to identify all processes that are using the

file system.

2. Use the kill -9 command to stop all those processes.

3. Run the umount command again.


136


MPFS software During removal of the MPFS software, the following errors may occur with a HP-UX server:

Problem Removing an MPFS software package that fails.

Cause 1The MPFS software is not installed on the HP-UX server.

Solution 11. Make sure that you spelled the MPFS software name correctly,

with upper- and lowercase letters specified correctly.

2. If the MPFS software name is spelled correctly, verify that the MPFS software is installed on the HP-UX server by typing:

swlist -l product EMCmpfs

If an MPFS file system is installed, the output is similar to this:

EMCmpfs 4.0.22 EMC MPFS Filesystem

If an MPFS file system is not installed, the output is similar to this:

ERROR: Software "EMCmpfs" was not found on host "<hostname>:/".

Cause 2You are trying to remove the MPFS software while one or more MPFS-mounted file systems are active, and I/O is taking place on the active file system(s).

Messages similar to these appear in the /var/adm/sw/swagent.log file:

ERROR: Mounted MPFS filesystems found on the system. Please unmount all MPFS filesystems before removing the product.ERROR: The "checkremove" script for "EMCmpfs.MPFS-CORE" failed (exit code "1").

Solution 21. Stop the I/O.

2. Unmount all active MPFS file systems using the umount command.

3. Restart the removal process.



Miscellaneous The following are miscellaneous problems you might encounter with a HP-UX server.

Problem You cannot write to a mounted file system.

CauseYou lack write permission on the file system, or the file system is mounted as read-only.

Solution1. Check that you have write permission on the file system.

2. Try unmounting the file system and then remounting it in read/write mode.

Problem The HP-UX server hangs if the insf -e command is run after the MPFS software is installed on the HP-UX server. To recover it must use the backup kernel.

CauseThe insf -e command is run after the MPFS software is installed on the HP-UX server.

SolutionIssue the insf -e command on the HP-UX server before installing the MPFS software.


138


Troubleshooting the AIX serverThis section describes potential problems with the AIX server.

Refer to the Celerra MPFS for AIX Release Notes for additional information on troubleshooting, known problems and limitations.

Uninstalling You might encounter the following problems during removal of the MPFS software

Problem Removing the MPFS software using installp fails.

Cause 1The MPFS software is not installed on the AIX server.



2. If the MPFS software name is spelled correctly, verify that the MPFS software is not installed on the AIX server by typing:

lslpp -1 EMCmpfs

If an MPFS file system is installed, the output is similar to this:

Fileset Level State Description -------------------------------------------------------------------------- Path: /usr/lib/objrepos EMCmpfs 4.0.22.3 COMMITTED EMC MPFS Filesystem Path: /etc/objrepos EMCmpfs 4.0.22.3 COMMITTED EMC MPFS Filesystem

If an MPFS file system is not installed, the output is similar to this:

lslpp: 0504-132 Fileset EMCmpfs not installed.

Cause 2You are trying to remove the MPFS software while one or more MPFS-mounted file systems are active, and I/O is taking place on the active file system(s).



If this is the case, you see messages similar to these:

+-----------------------------------------------------------------------------+ Pre-deinstall Verification...+-----------------------------------------------------------------------------+Verifying selections...mpfs volumes still mounted. Cannot unload extension.**** ERROR: MPFS volume are still mounted.**** Unmount mpfs volumes before uninstalling c3s2e0 /c3s2fs0 /mnt/c3s2fs0 mpfs Aug 11 12:57 doneVerifying requisites...doneResults...

FAILURES-------- Filesets listed in this section failed pre-deinstall verification and will not be removed.

Non-Deinstallable Filesets -------------------------- The following filesets were selected for deinstallation. Deinstallability checks indicate that they should not be removed from the system.

EMCmpfs*

<< End of Failure Section >>

FILESET STATISTICS ------------------ 1 Selected to be deinstalled, of which: 1 FAILED pre-deinstall verification ---- 0 Total to be deinstalled

Pre-installation Failure/Warning Summary----------------------------------------Name Level Pre-installation Failure/Warning-------------------------------------------------------------------------------EMCmpfs* Failed pre-deinstallation check

Solution 21. Stop the I/O.

2. Unmount all active MPFS file systems using the unmount command.


Troubleshooting the AIX server 139

140




Problem You cannot mount the MPFS file system. The mount command displays the following message:

Disk not found

Cause

The disks are not available to mount the MPFS file system.

SolutionCheck storage system and run the mpfsdiscover command.

Problem The mount command retries indefinitely.

Cause 1The server you specified with the mount command does not exist, cannot be reached, or is down.


mount: 1831-009 <hostname> not in hosts databasemount: 1831-008 giving up on:<hostname>:/fsnameA route to the remote host is not available.Error mounting nfs partition 20736

Solution 11. Interrupt the mount command using the interrupt key


2. Try to reach the server using the ping command.




Cause 2The file system you specified does not exist or is not exported.


nfsmnthelp: 1831-019 hostname: A file or directory in the path name does not exist.

mount: 1831-008 giving up on: <hostname>:/fsname A file or directory in the path name does not exist.Error mounting nfs partition 512

Solution 2Make sure that the file system exists on the server and is exported with the correct access permissions.

Problem The mount command displays messages about unknown file systems:

CauseYou specified an option that is not supported by the mount command.

Solution1. Display the mount_mpfs(1) man page to find supported options

by typing:

man mount_mpfs



nfsmnthelp: 1831-006 NFS mounts/unmounts are only allowed by superuser and by members of the system group

Cause 1You lack the permissions required to access the file system you specified in the mount command.

Solution 1Ensure that the file system has been exported with the right permissions, or set the right permissions for the file system. The Celerra File Server Command Reference Manual provides more information.

Cause 2You are not the root user on the HP-UX, AIX, or Solaris server.

Solution 2Use the su command to obtain root user authority.


142



mpfsmnthelp: connection refused

CauseThe server you specified in the mount command is not an NFS or Celerra Network Server, or the Celerra Network Server is down.

SolutionCheck that you specified the correct server name and that the server has an exported file system.


mount: 1831-009 c3s2e9 not in hosts databasemount: 1831-008 giving up on:c3s2e9:/c3s2fs0A route to the remote host is not available.Error mounting nfs partition 20736

CauseThere is no entry in the /etc/hosts file or the domain name server database for the server name/IP address specified in the mount command.

Solution1. Make sure that you specified the correct server name in the

mount command.

2. If you did specify the correct name, make sure the host’s /etc/hosts file or the NIS/DNS map contains an entry for the server and that the server name is spelled correctly.

3. Run the ping command, using the server’s name.

If the ping command succeeds, try the mount command again using the server’s name.

If the ping command fails, go to step 4.

4. Try the ping command again, this time using the server’s IP address instead of its name.

5. If ping using the IP address succeeds, try the mount command again, this time using the server’s IP address instead of its name.

6. Make sure the /etc/hosts file or the domain name server database contains the correct entry for future use.




mount: 1831-008 giving up on:<host:/filesystem>vmount: A file or directory in the path name does not

exist.Error mounting nfs partition -256

CauseNo mount point exists.

SolutionCreate a mount point and try the mount again.

Problem The mount command displays the following message:

mount: 0506-318 mpfs is not a known vfs type for object /<filesystem>.

CauseThe HP-UX, AIX, or Solaris server is not installed.

SolutionInstall the HP-UX, AIX, or Solaris server and try the mount again.

Problem The mount command logs a message similar to the following in the system message log files:

mount command errors with:Physical Volume with serial number '82005' not found.in syslog:Aug 11 13:36:16 <hostname> unix: could not find device for <82005>

CauseThe MPFS mount operation could not find one or more physical disks associated with the specified file system.

SolutionUse either the mpfsdiscover command with the -n and -v options or the inq command to verify that the physical CLARiiON or Symmetrix disk device associated with the file system is connected to the HP-UX, AIX, or Solaris server over Fibre Channel and is accessible from the HP-UX, AIX, or Solaris server.

Problem You cannot unmount a file system. The unmount command displays the following message:

uvmount: Device busy


144


CauseExisting processes were using the file system when you attempted to unmount it, or the unmount command was issued from the file system itself.

Solution1. Use the fuser -c command to identify all processes that are using

the file system.

2. Use the kill -9 command to stop all those processes.


Miscellaneous The following are miscellaneous problems you might encounter with a AIX server.

Problem The mpfsdiscover command does not show the disks corresponding to the file systems.

CauseYour disks are of an unknown type.

SolutionCheck your disk types by typing:

lsdev -Ccdisk -fddins |sort -u

powerdiskddscdiskscsidisk

If the output from the lsdev command shows any disk type other than the known disk types—powerdiskdd, scdisk, or scsidisk—report the unknown disk type to the EMC Customer Support Center.

Problem You run the mpfsdiscover command, and some disks are not displayed in the command’s output.

CausePowerPath is installed on the AIX server, providing disk protection. When disk protection is enabled, the mpfsdiscover command does not display disks related to the MPFS file system.

SolutionAs superuser, type the following command:

/etc/powerprotect "mpfsdiscover -n -v"



This command displays all disks. The EMC PowerPath powerprotect man page describes the powerprotect command.

Problem You run the inq command, and some disks are not displayed in the command’s output.

CausePowerPath is installed on the AIX server, providing disk protection. When disk protection is enabled, the inq command does not display disks related to the MPFS file system.

Solution1. Make sure you are running an up-to-date version of inq and an

up-to-date version of PowerPath.

2. As superuser, type the following command:

/etc/powerprotect "inq -celerra"

This command displays all disks and indicates which disks are Celerra and MPFS disks. The EMC PowerPath powerprotect man page describes the powerprotect command.




2. Try unmounting the file system and then remounting it in read-write mode.

Problem The AIX server log contains messages similar to these:

Aug 11 13:19:20 <hostname> unix: biowait returned 5Aug 11 13:19:20 <hostname> unix: read falling through to NFS

CauseThe connection between the AIX server and the physical Symmetrix disk device was lost after the MPFS kernel extension was loaded.

SolutionCheck for Fibre Channel connectivity to the Symmetrix storage array or a bad physical disk device on the Symmetrix storage array.


146


Problem The Celerra Network Server goes down.

CauseThe reserve flag is not set to no in ODM for a disk related to the file system.

Solution1. Set the reserve flag to no.

2. Clear the reserves on the Symmetrix storage array.

3. Rediscover all disks using rmdev and emc_cfgmgr.sh.

4. Reboot the Data Mover.



Troubleshooting the Solaris serverThis section describes potential problems with the Solaris server.

Refer to the Celerra MPFS for HP-UX and Solaris Clients Release Notes for additional information on troubleshooting, known problems and limitations.



Problem The mount command hangs.

CauseThe server you specified with the mount command does not exist, cannot be reached, or is down.

Solution1. Interrupt the mount command using the interrupt key


2. Try to reach the server using the ping (1M) command.



illegal option.

CauseIf you specify an option that is not supported by the mount command, the command displays the following error message and usage information:

mount: illegal option Usage:mount [-v | -p]mount [-F FSType] [-V] [current_options] [-o specific_options] {special | mount_point}mount [-F FSType] [-V] [current_options] [-o specific_options] special mount_pointmount -a [-F FSType] [-V] [current_options][-o specific_options] [mount_point ...]

Troubleshooting the Solaris server 147

148


Solution1. Display the mount_mpfs man page to find supported options by

typing:

$ man mount_mpfs



invalid argument.

CauseAfter you install the Solaris server for the first time, you must reboot the Solaris server before you run the mount command. If you fail to do so, the mount command displays the invalid argument message.

Solution1. Reboot the Solaris server.

2. Run the mount command again.


permission denied.

Cause 1You lack the permissions required to access the file system you specified in the mount command.

Solution 1Ensure that the file system has been exported with the right permissions, or set the right permissions for the file system. The Celerra Network Server Command Reference Manual provides more information.

Cause 2You are not the root user on the server.

Solution 2Use the su command to become root.


RPC program not registered.

CauseThe server you specified in the mount command is not an NFS or Solaris server.



SolutionCheck that you specified the correct server name and that the server has an exported file system.

Problem The mount command logs the following message in the /var/adm/messages file:

Couldn’t find device during mount.

CauseThe MPFS mount operation could not find the physical disk associated with the specified file system.

SolutionUse either the format command or the mpfsinq command to verify that the physical storage system disk device associated with the file system is connected to the Solaris server over either Fibre Channel and is accessible from the Solaris server.


No such file or directory.

CauseThe file system specified in the mount command does not exist on the specified server.

SolutionMake sure that the file system exists on the server and is exported.


RPC: Unknown host.

CauseThe server name specified in the mount command does not exist on the network.


150


Solution1. Make sure that you specified the correct server name in the

mount command.

2. If you did specify the correct name, check whether the host’s /etc/hosts file or the NIS/DNS map contains an entry for the server.

3. If the server does appear in /etc/hosts or the NIS/DNS map, check whether the server responds to the ping (1M) command.

4. If the ping command succeeds, try using the server’s IP address instead of its name in the mount command.


operation not applicable to FSType mpfs.

CauseThe MPFS software has not been installed on the Solaris server.

Solution1. Install the MPFS software on the Solaris server.

2. Run the mount command again.

Problem You cannot unmount a file system.

CauseExisting processes are using the file system, or the umount command was issued from the file system itself.

Solution1. Stop all processes using the file system.




MPFS software During installation, reinstallation, or removal of the MPFS software, the following errors may occur with a Solaris server:

Problem Installing the MPFS software using the pkgadd utility fails.

CauseThe installation procedure could fail if you try to install the MPFS software for the wrong version of the operating system; for example, you try to install the MPFS software for Solaris 5.6 on a Solaris server that is running Solaris 5.7.

If this situation occurs, pkgadd displays the following messages:

## Executing checkinstall script.##### Incorrect version of Solaris.##### This packages requires Solaris 7.0checkinstall script suspends

Installation of <EMCmpfs> was suspended (administration).No changes were made to the system.

Solution1. Determine which version of the Solaris operating system is

running on the Solaris server by typing:

# uname -r

2. Change to the directory corresponding to the operating system version number (Solaris 5.6, 5.7, or 5.8), and start the installation process from that directory.

Problem Reinstalling the MPFS software using the pkgadd (1M) utility fails.

CauseInstallation could fail if you try to reinstall the MPFS software over an existing MPFS software package while one or more MPFS-mounted file systems are active. If this situation occurs, pkgadd displays the following messages:

This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package.

## Executing checkinstall script.Using </etc/fs> as the package base directory.

## Processing package information.## Processing system information.

20 package pathnames are already properly installed.## Verifying disk space requirements.


152


## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user permission during the process of installing this package.


Installing Multiplex File System as <EMCmpfs>

## Executing preinstall script.can't unload the module: Device busy######: Could not unload MPFS kernel module. Are there any MPFS mounts active?pkgadd: ERROR: preinstall script did not complete successfully

Installation of <EMCmpfs> failed.

Solution1. Unmount all active MPFS file systems using the umount

command.

2. Restart the installation process.

Problem Removing the MPFS software using pkgrm (1M) fails.

Cause 1The MPFS software is not installed on the Solaris server.

If this is the case, pkgrm displays the following message:

pkgrm: ERROR: no package associated with <EMCmpfs>



2. If the MPFS software name is spelled correctly, verify that the MPFS software is not installed on the Solaris server by typing:

# pkginfo | grep EMCmpfs



Cause 2You are trying to remove the MPFS software while one or more MPFS-mounted file systems are active.

If this is the case, pkgrm displays the following messages.

## Verifying package dependencies.## Processing package information.## Executing preremove script.can't unload the module: Device busy######: Could not unload MPFS kernel module. Are there any MPFS mounts active?pkgrm: ERROR: preremove script did not complete successfully

Solution 21. Unmount all active MPFS file systems using the umount

command.


Miscellaneous The following are miscellaneous problems you might encounter with a Solaris server.

Problem The Solaris server log contains this message:

Disk not responding to selection.

CauseThe connection between the Solaris server and the physical disk device was lost after the MPFS kernel module was loaded.

SolutionCheck for Fibre Channel connectivity to the storage system or a bad physical disk device on the storage system.

Problem The Solaris server log contains this message:

Disk not labeled/Incorrect label.

CauseThe physical disk associated with the mounted MPFS file system is not labeled, or the label is corrupt.

SolutionUse the format command to relabel the disk.


154





2. Try unmounting the file system and then remounting it in read/write mode.

Problem You see the following message:

NFS server not responding.

CauseThe Celerra Network Server is unavailable due to a network-related problem, a reboot, or a shutdown.

SolutionCheck whether the server responds to the ping (1M) command. Also try unmounting and remounting the file system.


Glossary

This glossary defines terms useful for MPFS administrators.

CCelerra MPFS over

Fibre ChannelMulti-Path File System over Fibre Channel-based clients. MPFS client that works in conjunction with an IP-SAN switch to transfer data between the servers and storage systems over the Fibre Channel SAN. See also Multi-Path File Systems (MPFS).

Celerra NetworkServer

EMC network attached storage (NAS) product line.

Challenge HandshakeAuthentication

Protocol (CHAP)

Access control protocol for secure authentication using shared passwords called secrets.

client Front-end device that requests services from a server, often across a network.

command lineinterface (CLI)

Interface for entering commands through the Control Station to perform tasks that include the management and configuration of the database and Data Movers and the monitoring of statistics for the Celerra cabinet components.

Common Internet FileSystem (CIFS)

File-sharing protocol based on the Microsoft Server Message Block (SMB). It allows users to share file systems over the Internet and intranets.


156

Glossary

Control Station Hardware and software component of the Celerra Network Server that manages the system and provides the user interface to all Celerra components.

Ddaemon UNIX process that runs continuously in the background, but does

nothing until it is activated by another process or triggered by a particular event.

Data Mover In a Celerra Network Server, a cabinet component running its own operating system that retrieves files from a storage device and makes them available to a network client. This is also referred to as a blade. A Data Mover is sometimes internally referred to as DART because DART is the software running on the platform.

disk volume On Celerra systems, a physical storage unit as exported from the storage array. All other volume types are created from disk volumes.

Eextent Set of adjacent physical blocks.

Ffallthrough Fallthrough occurs when MPFS temporarily employs the NFS or CIFS

protocol to provide continuous data availability, reliability, and protection while block I/O path congestion or unavailability is resolved. This fallthrough technology is seamless and transparent to the application being used.

Fast Ethernet Any Ethernet specification with a speed of 100 Mb/s. Based on the IEEE 802.3u specification.

Fibre Channel Nominally 1 Gb/s data transfer interface technology, although the specification allows data transfer rates from 133 Mb/s up to 4.25 Gb/s. Data can be transmitted and received simultaneously. Common transport protocols, such as Internet Protocol (IP) and Small Computer Systems Interface (SCSI), run over Fibre Channel. Consequently, a single connectivity technology can support high-speed I/O and networking.


Glossary

File Mapping Protocol(FMP)

File system protocol used to exchange file layout information between an MPFS client and the Celerra Network Server. See also Multi-Path File Systems (MPFS).

file system Method of cataloging and managing the files and directories on a storage system.

FLARE Embedded operating system in CLARiiON disk arrays.

Ggateway A Celerra Network Server that is capable of connecting to multiple

storage arrays, either directly (direct-connected) or through a Fibre Channel switch (fabric-connected).

Gigabit Ethernet Any Ethernet specification with a speed of 1000 Mb/s. IEEE 802.3z defines Gigabit Ethernet over fiber and cable, which has a physical media standard of 1000Base-X (1000Base-SX short wave, 1000Base-LX long wave) and 1000Base-CX shielded copper cable. IEEE 802.3ab defines Gigabit Ethernet over an unshielded twisted pair (1000Base-T).

Hhost Addressable end node capable of transmitting and receiving data.

IInternet Protocol (IP) Network layer protocol that is part of the Open Systems

Interconnection (OSI) reference model. IP provides logical addressing and service for end-to-end delivery.

Internet Protocoladdress (IP Address)

Address uniquely identifying a device on any TCP/IP network. Each address consists of four octets (32 bits), represented as decimal numbers separated by periods. An address is made up of a network number, an optional subnetwork number, and a host number.

Llogical unit (LU) For FC on a Celerra Network Server, a logical unit is a software

feature that processes commands, such as reading from and writing to storage media. From a host perspective, a logical unit appears as a disk device.


158

Glossary

logical unit number(LUN)

Identifying number of an object that processes commands. The LUN is an ID for the logical unit, but the term is often used to refer to the logical unit itself.

logical volume Logical devices aggregated and managed at a higher level by a volume manager.

Mmetadata Data containing structural information (such as access methods)

about itself.

metavolume On a Celerra system, a concatenation of volumes, which can consist of disk, slice, or stripe volumes. Also called a hyper volume or hyper. Every file system must be created on top of a unique metavolume.

mirrored pair Logical volume with all data recorded twice, once on each of two different physical devices.

mirroring Method by which the storage system maintains two identical copies of a designated volume on separate disks.

mount Process of attaching a subdirectory of a remote file system to a mount point on the local machine.

mount point Local subdirectory to which a mount operation attaches a subdirectory of a remote file system.

MPFS session Connection between an MPFS client and a Celerra MPFS Network Server.

MPFS share Shared resource designated for multiplexed communications using the MPFS file system.

Multi-Path File Systems(MPFS)

Celerra Network Server feature that allows heterogeneous servers with MPFS client software to concurrently access, directly over Fibre Channel, shared data stored on a Symmetrix or CLARiiON array. MPFS adds a lightweight protocol called File Mapping Protocol (FMP) that controls metadata operations.


Glossary

Nnested mount file

system (NMFS)File system that contains the nested mount root file system and component file systems.

nested mount filesystem root

File system on which the component file systems are mounted read-only except for mount points of the component file systems.

network attachedstorage (NAS)

Specialized file server that connects to the network. A NAS device, such as Celerra Network Server, contains a specialized operating system and a file system, and processes only I/O requests by supporting popular file sharing protocols such as NFS and CIFS.

network file system(NFS)

Network file system (NFS) is a network file system protocol allowing a user on a client computer to access files over a network as easily as if the network as easily as if the network devices were attached to its local disks.

PPowerPath EMC host-resident software that integrates multiple path I/O

capabilities, automatic load balancing, and path failover functions into one comprehensive package for use on open server platforms connected to Symmetrix or CLARiiON enterprise storage systems.

RRedundant Array ofIndependent Disks

(RAID)

Method for storing information where the data is stored on multiple disk drives to increase performance and storage capacities and to provide redundancy and fault tolerance.

Sserver Device that handles requests made by clients connected through a

network.

small computersystem interface

(SCSI)

Standard set of protocols for host computers communicating with attached peripherals.

storage area network(SAN)

Network of data storage disks. In large enterprises, a SAN connects multiple servers to a centralized pool of disk storage. See also network attached storage (NAS).


160

Glossary

storage processor (SP) Storage processor on a CLARiiON storage system. On a CLARiiON storage system, a circuit board with memory modules and control logic that manages the storage system I/O between the host’s Fibre Channel adapter and the disk modules.

Storage processor A(SP A)

Generic term for the first storage processor in a CLARiiON storage system.

Storage processor B(SP B)

Generic term for the second storage processor in a CLARiiON storage system.

stripe size Number of blocks in one stripe of a stripe volume.

Symmetrix RemoteData Facility (SRDF)

EMC technology that allows two or more Symmetrix systems to maintain a remote mirror of data in more than one location. The systems can be located within the same facility, in a campus, or hundreds of miles apart using fibre or dedicated high-speed circuits. The SRDF family of replication software offers various levels of high-availability configurations, such as SRDF/Synchronous (SRDF/S) and SRDF/Asynchronous (SRDF/A).

Ttar Backup format in PAX that traverses a file tree in depth-first order.

Transmission ControlProtocol (TCP)

Connection-oriented transport protocol that provides reliable data delivery.

Uunified storage A Celerra Network Server that is connected to a captive storage array

that is not shared with any other Celerra Network Servers and is not capable of connecting to multiple storage arrays.

VVSAN SAN that can be broken up into sections allowing traffic to be isolated

within the section.


Index

AAccess Logix configuration 50accessing storage 58adding Fibre Channel hosts to storage groups 59adding LUNs 51administering a Solaris Server 113administering an AIX Server 113administering an HP-UX Server 113AIX Server

migrating 94mounting an MPFS file system 93session, starting 93troubleshooting 138

architectureCelerra gateway with Fibre Channel 20Celerra unified storage with Fibre Channel

19

CCelerra gateway with Fibre Channel 20Celerra Network Server

configuring 40enabling MPFS 46setup 38

Celerra Network Server configuration 26Celerra unified storage with Fibre Channel 19CHAP 29CLARiiON

based array requirements 37configuring using CLI commands 47

commandsmpfsctl diskreset 117mpfsctl help 118

mpfsctl prefetch 119mpfsctl reset 120mpfsctl rwint 121mpfsctl stats 122mpfsctl sync-attr 124mpfsctl use-sync 1 125mpfsctl version 126

comments 15configuration overview 24configuration planning checklist 31configuring

Celerra Network Server 40storage 58storage access 47zones 47

creatinga file system 40a security file 49storage groups 51

Ddata mover capacity 27devices, displaying 128displaying MPFS devices 128

Eenabling SP interfaces 49Establishing an MPFS session

AIX 93establishing an MPFS session 115


162

Index

FFibre Channel

driver installation 58switch installation 48switch requirements 36

File Mapping Protocol (FMP) 22file system

creation 40mounting 61setup 39

firewall FMP port numbers 57

GGigabit Ethernet port configuration 33

HHP-UX Server

mounting an MPFS file system 115postinstallation instructions 79session, starting 115

HP-UX, AIX, or Solaris Serverconfiguration 28

II/O sizes 26I/O, resuming through MPFS 117inq command, troubleshooting

AIX 145installing MPFS software 81Installing MPFS software, migrating

AIX 94

Llocked files 121

Mmanaging a Solaris Server 113managing an AIX Server 113managing an HP-UX Server 113Migrating

AIX 94migrating

MPFS software 81, 110mounting

troubleshooting, HP-UX 133troubleshooting, Solaris 147

Mounting an MPFS file systemAIX 93

mounting an MPFS file system 61, 115Mounting an MPFS file system, troubleshooting

AIX 140MPFS

devices, displaying 128over Fibre Channel 18server. See HP-UX Server, Solaris Serverthreads 26

MPFS file systemstarting 61

MPFS software 33installing 110migrating 81, 110post installation instructions 109reinstalling 151removing 82, 111, 138uninstalling 82

mpfsctl commandsmpfsctl diskreset 117mpfsctl help 118mpfsctl prefetch 119mpfsctl reset 120mpfsctl rwint 121mpfsctl stats 122mpfsctl sync-attr 124mpfsctl use-synch 1 125mpfsctl version 126

mpfsdiscover command, troubleshootingAIX 144

mpfslabel command 100

Ooverview of configuring MPFS 24

Ppostinstallation instructions

MPFS software 79PowerPath

features summary 65installation prerequisites 70

PowerPath support 26powerprotect command 144, 145


Index

preinstallation instructionsHP-UX 86MPFS software 72, 98

Rread/write interception 121reinstalling MPFS software 151Removing MPFS software

AIX Server 96resetting counters 120resuming I/O through MPFS 117

SSAN switch zoning 48security file creation 49Session, starting

AIX 93session, starting

115setting up a file system 39setting up the Celerra Network Server 38software components

AIX operating system 33Celerra Network Server NAS software 33HP-UX operating system 33MPFS software 33Solaris operating system 33

Solaris Serversession, starting 115

Starting an MPFS sessionAIX 93

starting an MPFS session 115statistics

displaying 122resetting counters 120

storage recommendations 28storage system

requirements 34verification 34

Symmetrix devices, incorporatingHP-UX 73, 87

system component verification 32

TTroubleshooting

AIX Server 138troubleshooting

HP-UX Server 133Solaris Server 147

tuning a Solaris Server 113tuning an AIX Server 113tuning an HP-UX Server 113

UUninstalling MPFS software, troubleshooting

AIX 138Unmounting, troubleshooting

AIX 140, 143unmounting, troubleshooting

HP-UX 135Solaris 150

Upgrading. See Migrating

Vverifying

storage system 34version number, displaying 126volume stripe size 26

163EMC Celerra MPFS over FC for HP-UX, AIX, and Solaris Clients Version 4.0 Product Guide

164

Index


celerra for hp-ux, aix, and solaris clients · configuring the clariion using cli commands ......

Documents