HP StorageWorks 8000 - NAS Installation guide

HP Surestore NAS 8000 SAN High Availability Solution Integration Manual (SIM) 1
HP Surestore NAS 8000 SAN
High Availability Solution
Integration Manual (SIM)
Read Me First
This binder includes the details of the integration tasks that Hewlett-Packard or an authorized
reseller has performed. The first section, Solution Integration and Product Configuration
Overview, is intended to give you a detailed picture of the solution you ordered from Hewlett
Packard.
The remaining sections of this binder will be used by your installation specialist, who will work
with you to plan and install your HP Network Attached Storage (NAS) 8000 SAN High
Availability (HA) system according to your specific requirements.
Before installing the HP NAS 8000 SAN HA solution, you must first complete the items in the
“Network and Storage Planning” section of this binder. If your installation specialist has not
done so already, he or she will contact you to schedule a joint planning session.
After the planning is complete, your installation specialist will perform tasks included in this
binder’s “Installation Guide” section.
We sincerely hope that you will be delighted with our integration services and we are looking
forward to hearing from you.
Format Conventions
WARNING Identifies a hazard that can cause personal injury
Caution Identifies a hazard that can cause hardware or software damage
Note Identifies significant concepts or operating instructions
1

2 HP Surestore NAS 8000 SAN High Availability Solution Integration Manual (SIM)
Binder Contents
This binder contains the following sections:
Notice
© Hewlett-Packard Company, 2002. All rights reserved.
Hewlett-Packard Company makes no warranty of any kind with regard to this material,
including, but not limited to, the implied warranties of merchantability and fitness for a
particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing, performance, or use of
this material.
This document contains proprietary information, which is protected by copyright. No part of
this document may be photocopied, reproduced, or translated into another language without
the prior written consent of Hewlett-Packard. The information contained in this document is
subject to change without notice.
Trademark Information
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems,
Inc. in the U.S. and other countries.
Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft
Corporation.
UNIX is a registered trademark of The Open Group.
Section Audience Purpose
1. Read Me First Customer IT administrator Introduction
2. Solution Integration and
Product Configuration
Overview
Customer IT administrator Product information
3. Network and Storage
Planning
Installation specialist and
customer IT administrator
Pre-installation planning
session
4. Installation Guide Installation specialist Hardware installation and
software configuration
5. Safety Installation specialist and
customer IT administrator
Warnings and regulatory
information
6. Warranty and Support Customer IT administrator Warranty and technical
support contracts

Solution Integration and Product Configuration Overview 3
Solution Integration and
Product Configuration Overview
This section contains the following documents, which were customized and inserted by the
Integration Center:
■Deployment information
■Rack, server and component configurations
■Parts list
■Network, cabling, and power connection diagrams
2

4 Solution Integration and Product Configuration Overview

Network and Storage Planning 5
Network and Storage Planning
This section contains pre-planning materials that the installation specialist can review with the
customer before the NAS 8000 system arrives onsite. It includes:
■System Overview: a conceptual overview of the storage system of the HP NAS 8000 SAN
HA solution, including:
—Storage Overview and Terminology
—HA Storage Configuration
—Determining Available Disk Space
■Planning Worksheets to record network and storage settings. The information in the
planning worksheets is required to install and configure the system.
—Storage Planning
—High Availability Planning
—Network Planning
You need to construct an overall storage architecture by:
1. Determining the amount of total storage available
2. Deciding how to allocate it to different groups or functions
Storage space is spread across volume groups. In these volume groups, you must create file
volumes to divide your disk space. It is important that you plan storage space prior to creating
file volumes. Although the HP NAS 8000 lets you expand your volume groups later, you may
want to reserve extra space during setup to allow for the use of snapshots.
3

6 Network and Storage Planning
Storage Overview and Terminology
The HP NAS 8000 SAN HA is an easy-to-manage storage solution for heterogeneous
environments including Windows, UNIX, and Linux.
The storage space on the HP NAS 8000 SAN HA is made up of physical and logical storage:
■Physical storage refers to the hardware you use for data storage.
■Logical storage is created by software that organizes your physical storage into file
volumes and directories that are made accessible to users.
In addition, the HA configurations include high-availability features such as redundant
hardware and failover packages.
Physical Storage
The HP NAS 8000 SAN configurations can manage storage on a variety of devices within a
SAN including the HP Virtual Array 7100, HP Virtual Array 7400 series, and HP XP series disk
arrays using SecureManager VA or SecureManager XP.
Logical Storage
SAN
A SAN, or Storage Area Network, is a high-speed special-purpose network (or subnetwork)
that connects different kinds of storage devices with associated data servers on behalf of a
larger network of users. Typically, a SAN is part of the overall network of computing resources
in a company. SAN devices are usually close to other computing resources, but may also
extend to remote locations for backup and archival storage. HP NAS 8000 SAN solutions can
access storage on supported devices within the SAN.
Logical Unit Number
A logical unit number (LUN) is a logical aggregation of space on physical drives. LUNs are
unique identifiers that enable the controller to differentiate between separate devices (each of
which is a logical unit). Each LUN is a unique number that identifies a specific unit of storage.
The HP NAS 8000 SAN HA supports up to 127 LUNs.
Volume Groups
A volume group is the aggregation of one or more LUNs. Volume groups combine the space
from LUNs and make the space accessible to the file system for creating file volumes and
directories, which can then be made accessible to users.
File Volumes
A volume group is divided into one or more file volumes. File volumes are the basic unit of
logical storage for a file system on the HP NAS 8000 SAN HA. File volumes can be further
subdivided into individual directories.

Network and Storage Planning 7
Directories
Directories let you organize information. Directories contain files or other persistent data
structures in a file system that contains information about other files. Directories are usually
organized hierarchically and may contain both files and other directories, and are used to
organize collections of files for applications or convenience.
Snapshots
Snapshots are an important part of data-protection plans. A good data-protection plan should
include a backup strategy, storage redundancy provided by RAID levels, and snapshots.
Snapshots provide nearly instantaneous access to previous versions of a file stored on the HP
NAS 8000 HA solution.
A snapshot is a read-only picture of a file volume at a specific point in time. When you create
a snapshot of a file volume, the snapshot initially consumes zero physical space. However, as
users modify the file volume, the snapshot tracks changes between the original file volume and
the modified file volume. If an error occurs and a user needs to revert to the previous version,
the snapshot version of the file can be restored.
Snapshots consume storage space. When planning storage, consider how dynamic your data
will be. With file volumes in which data changes rapidly, snapshots will consume a larger
amount of space. At the extreme limit, a file volume can change so much from the original
information that the snapshot consumes the same amount of space as the original data.
Typically, data does not change so rapidly, and the usage and growth of snapshot space is
relatively slow.
Snapshots are optional and may be created at any time after the basic storage configuration is
complete. Users can add or resize a snapshot at a later time if there is enough free space
available in the volume group.

8 Network and Storage Planning
High Availability
The HP NAS 8000 high availability solution includes a cluster , or group, of two NAS servers
that function as a unified system. The cluster is managed by a Quorum server.
The main purpose of high-availability clusters is to provide a higher degree of storage
availability to client systems than is possible with a single server. This is accomplished by
eliminating single points of failure and providing functional redundancy. Uninterrupted service
is provided by failing over file serving capabilities (see “Failover Packages” on page 8) to a
secondary server in the event of a failure in the primary server in the cluster.
■The NAS servers provide failover services for each other.
■The Quorum server manages the NAS servers, or
cluster nodes , and provides cluster
arbitration services that prevent data corruption.
Clusters
HA Clusters provide a higher degree of storage availability than is possible with a single
server. This is provided by:
■Hardware component redundancy designed to eliminate single points of failure. Each
cluster consists of two or more NAS servers (nodes) plus one Quorum server.
■Software failover capabilities. All storage is controlled by packages which are the smallest
units of failover in the cluster.
Failover Packages
When a package failure is detected, the package is halted and will fail over to another node,
provided that an eligible adoptive node is present. Each package and its associated resources
are monitored independently. This allows failures that are limited to a single package to be
handled without affecting the state of other packages.
The NAS solution supports two failover models:
■Active/Active (or “Dual Active”) means that all cluster nodes can be serving data
simultaneously. The nodes will provide failover services for each other, but can be fully
utilized at all times. This mode is achieved by configuring failover packages to run on both
cluster nodes – effectively dividing the storage between the nodes.
■Active/Passive (or “Single Active”) means that one server is actively serving data while the
other node is in full-time stand-by mode, becoming active only when the other node fails.
This mode can be realized by configuring all of the failover packages and storage to run on
only one node. Without any packages to run, the other node will wait and monitor the other
node for failure.

Network and Storage Planning 9
HA Storage Configuration
This section provides suggestions for organizing your storage for optimizing HA features.
On a direct-attach NAS system without HA features, the simplest way to configure the storage
is to create a single LUN for the entire array and create one volume group with multiple file
volumes beneath it. However, in an HA cluster with two NAS servers, each volume group can
be active on only one NAS server, or
node , at a time. Therefore, if you are using active/active
failover packages (see “Failover Packages” on page 8), you must create at least two volume
groups so each node can access some of your storage.
In addition, with SAN configurations storage generally resides on several different storage
devices within the SAN. LUNs are created on each array using the SAN management
software. To ensure that a volume group does not become unavailable due to hardware
problems on a specific storage device, the safest configuration is to create a separate volume
group for each LUN.
Note When a volume group includes LUNs from multiple arrays, if any one array has
a hardware failure, the entire volume group will be unavailable. By creating a
separate volume group for each LUN, you are ensuring that only that portion of
the storage residing on the failed array will be unavailable until the array is
restored. All other storage will remain unaffected.
When determining how many LUNs and volume groups to create, consider the following:
■A volume group can be active on only one node at a time.
■A volume group can be assigned to only one failover package.
■File volumes can’t be split between packages or nodes.
■Multiple volume groups can be assigned to the same package.
■A package can only run on one node at a time.
■The HA cluster is limited to 30 packages total (both nodes combined).
■A package is the smallest unit of failover.
■A volume group is the smallest unit of storage that can be failed over.
■If a package contains multiple volume groups and a single volume group, file volume or
even share fails, the entire package will be failed over.
■More packages means a higher degree of granularity to balance the packages between the
nodes and detect failures.
■More packages also results in higher complexity in the cluster configuration and requires
more virtual IP addresses to keep track of.
■The packages should be divided between the cluster nodes such that the storage access
load (from client systems) will be balanced. This may or may not correspond to balanced
storage capacity between the nodes.
The illustrations on the following pages depict three common storage configurations:
■One LUN and one volume group (for active/passive failover).
■Multiple LUNs, volume groups and packages (most common for SAN configurations).

10 Network and Storage Planning
Figure 1 One LUN and One Volume Group for Active/Passive Failover
Figure 2 Multiple LUNs, Volume Groups and Packages

Network and Storage Planning 11
Planning Worksheets
The following topics should be reviewed in a planning session with the customer prior to
installation:
■Available disk space
■LUN, volume group and file volume requirements
■High availability settings
■Network settings
The planning worksheets in this section provide space to collect the information needed to
install the system. The blank worksheets are also included on the
HP NAS 8000 Documentation
CD.
Available Disk Space
Before you begin the storage planning process with the customer, you must know the amount of
available disk space on their system.
In NAS 8000 SAN configurations, storage may reside on several different devices within the
SAN. LUNs are created using the SAN management software. Ask the customer IT manager
how much space and how many LUNs will be allocated to the NAS 8000 SAN HA system.

12 Network and Storage Planning
Storage Planning Worksheet
Note All space is in Gigabytes (GB).
1. Record total available storage space Instructions
Total available storage Ask the IT manager how much raw space will be
allocated to the NAS 8000.
2. Calculate space for creating LUNs Instructions
Space for LUNs LUN Name Size Ask the IT manager for the number and size of
LUNs allocated to the NAS 8000.
Maximum: 127 LUNs
LUN1:
LUN2:
LUN3:
3. Verify space for creating Volume Groups (VGs) Instructions
Space for VGs VG Name Size See “HA Storage Configuration” on page 9 for tips
on planning Volume Groups and Failover
Packages.
VG1:
VG2:
VG3:
4. Plan space to reserve for Snapshots
Snapshots are associated with a specific file volume and must be created in the same volume group as that file
volume. Therefore you must allocate enough space in each volume group to include all file volumes and snapshots.
Snapshots are optional. You can add or resize a snapshot at a later time if there is enough free space available in
the volume group. Record your reserved space in the table below. See “Snapshots” on page 7.
5. Calculate space and record share settings Instructions
Number of
File Volumes (FVs)
in Volume Group ___
File Space Snapshot Win Share/
Unix Export
Name
Make a copy of this section for each Volume
Group.
Using the numbers from step 3, allocate the
space to as many files volumes as you need.
Maximum: 64 in each volume group
File Volume 1:
File Volume 2:
File Volume 3:
File Volume 4:
File Volume 5:

Network and Storage Planning 13
6. Verify total space for Snapshots and FVs Instructions
Total Used Space in
Volume Group ____
Total the lines in section 5. This number should be
equal to or less than line 1.
7. Remaining Unallocated Space Instructions
Total Remaining Space in
Volume Group ___
Subtract used space (line 6) from total available
space (line 1).

14 Network and Storage Planning
HA Planning Worksheet
Cluster Planning
Node 1 Name
Node 2 Name
Cluster Name
Quorum Server Name or IP Address
Quorum Server Polling Interval
Quorum Server Time-out
Primary Heartbeat NIC
Recommendation: Use the on-board network ports (eht0) used as
direct-connect dedicated heartbeat NICs. See instructions in
“Connect the Network Ports” on page 36 for instructions on
connecting primary heartbeat NICs.
This cannot
cannotcannot
cannot be the same port designated as the system
management port (below).
Node 1:
Node 2:
Secondary (or backup) Heartbeat NICs
Recommendation: Use at least one additional NIC in each NAS
server as a secondary heartbeat NIC.
Secondary heartbeat NICs are not direct-connections. See
instructions on “Connect the Network Ports” on page 36 for
instructions on connecting additional NICs.
Node 1:
Node 2:
System Management Port
The system management port is the port designated to access the
Command View NAS web interface.
This cannot
cannotcannot
cannot be the same port designated as the primary direct-
connect heartbeat (above).
Node 1:
Node 2:
Heartbeat Time-out
Network Polling Interval
Auto Start Time-out

Network and Storage Planning 15
Package Planning
Make a copy of this table for each Package.
Package Name
Fail Back Policy (manual or automatic)
Fail Over Policy (manual or automatic)
Auto Start (yes or no)
Reboot Node on Failure (yes or no)
Primary Node
Volume Groups 1.
2.
3.
4.
5.
6.
….
30.
Virtual IP Addresses &
Subnet Masks
IP Address Subnet Mask

16 Network and Storage Planning
Network Planning Worksheet Node 1
HP NAS 8000 SAN HA system information
System Name
Administrator Password
Contact Information
Contact Name
Contact Phone Number
Contact Pager Number
Contact E-mail
Physical Location
Rack ID
Rack Position
Asset Number
SNMP Settings
SNMP Community Password
SNMP Trap Destination(s)
SMTP Settings
SMTP Server
E-mail Recipients
Remote Event Logging
Remote Log Server Address
Windows Settings
WINS Server IP Address
Network Neighborhood Description
Workgroup Name (Shared Level Security)
Domain Name (User Level Security)
UNIX Settings
NIS Domain Name
NIS Boot Server
Trusted Host(s)

Network and Storage Planning 17
TCP/IP Settings NIC1 (on-board network port eth0)
Note Only one NIC per subnet can be configured. This limitation is required to prevent confusion as to which
NIC to bind a virtual IP address to when a package is started on a node or fails over. It is highly
recommended that one of the NICs (internal 10/100 is recommended) be configured as a dedicated
heartbeat. Having a heartbeat on a dedicated network port makes the heartbeat immune to heartbeat
starvation due to high network traffic. To avoid subnet conflicts, use a private subnet and IP address (e.g.
10.0.0.1) for the dedicated heartbeat, and direct connect the Ethernet CAT5 cross-over cable to the
other node to eliminate the need for an Ethernet hub/switch that could fail. (See “Connect the Network
Ports” on page 36.)
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers
TCP/IP Settings NIC2
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers
TCP/IP Settings NIC3
NIC3
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers

18 Network and Storage Planning
TCP/IP Settings NIC4
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers
TCP/IP Settings NIC5
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers

Network and Storage Planning 19
Network Planning Worksheet Node 2
HP NAS 8000 SAN HA system information
System Name
Administrator Password
Contact Information
Contact Name
Contact Phone Number
Contact Pager Number
Contact E-mail
Physical Location
Rack ID
Rack Position
Asset Number
SNMP Settings
SNMP Community Password
SNMP Trap Destination(s)
SMTP Settings
SMTP Server
E-mail Recipients
Remote Event Logging
Remote Log Server Address
Windows Settings
WINS Server IP Address
Network Neighborhood Description
Workgroup Name (Shared Level Security)
Domain Name (User Level Security)
UNIX Settings
NIS Domain Name
NIS Boot Server
Trusted Host(s)

20 Network and Storage Planning
TCP/IP Settings NIC1(on-board network port eth0)
Note Only one NIC per subnet can be configured. This limitation is required to prevent confusion as to which
NIC to bind a virtual IP address to when a package is started on a node or fails over. It is highly
recommended that one of the NICs (internal 10/100 is recommended) be configured as a dedicated
heartbeat. Having a heartbeat on a dedicated network port makes the heartbeat immune to heartbeat
starvation due to high network traffic. To avoid subnet conflicts, use a private subnet and IP address (e.g.
10.0.0.1) for the dedicated heartbeat, and direct connect the Ethernet CAT5 cross-over cable to the
other node to eliminate the need for an Ethernet hub/switch that could fail. (See “Connect the Network
Ports” on page 36.)
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers
TCP/IP Settings NIC2
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers
TCP/IP Settings NIC3
NIC3
IP Address
Gateway Address
Subnet Mask
Broadcast Address
DNS Domain Name
Primary DNS Server Address
Secondary DNS Servers