Hp StorageWorks Scalable File Share User Manual Page 48
- Page / 84
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
as needed on the file system server nodes. The lustre_config command can take hours
to complete depending on the size of the disks.
2. Start the file system manually and test for proper operation before configuring Heartbeat
to start the file system. Mount the file system components on the servers:
# lustre_start -v -a ./testfs.csv
3. Mount the file system on a client node according to the instructions in Chapter 4 (page 41).
# mount /testfs
4. Verify proper file system behavior as described in “Testing Your Configuration” (page 55).
5. After the behavior is verified, unmount the file system on the client:
# umount /testfs
6. Unmount the file system components from on the servers:
# lustre_start -v -k -a ./testfs.csv
5.2 Configuring Heartbeat
HP SFS G3.2-0 uses Heartbeat V2.1.3 for failover. Heartbeat is open source software. Heartbeat
RPMs are included in the HP SFS G3.2-0 kit. More information and documentation is available
at:
http://www.linux-ha.org/Heartbeat.
IMPORTANT: This section assumes you are familiar with the concepts in the Failover chapter
of the Lustre 1.8 Operations Manual.
HP SFS G3.2-0 uses Heartbeat to place pairs of nodes in failover pairs, or clusters. A Heartbeat
failover pair is responsible for a set of resources. Heartbeat resources are Lustre servers: the MDS,
the MGS, and the OSTs. Lustre servers are implemented as locally mounted file systems, for
example, /mnt/ost13. Mounting the file system starts the Lustre server. Each node in a failover
pair is responsible for half the servers and the corresponding mount-points. If one node fails,
the other node in the failover pair mounts the file systems that belong to the failed node causing
the corresponding Lustre servers to run on that node. When a failed node returns, the
mount-points can be transferred to that node either automatically or manually, depending on
how Heartbeat is configured. Manual fail back can prevent system oscillation if, for example, a
bad node reboots continuously.
Heartbeat nodes send messages over the network interfaces to exchange status information and
determine whether the other member of the failover pair is alive. The HP SFS G3.2-0
implementation sends these messages using IP multicast. Each failover pair uses a different IP
multicast group.
When a node determines that its partner has failed, it must ensure that the other node in the pair
cannot access the shared disk before it takes over. Heartbeat can usually determine whether the
other node in a pair has been shut down or powered off. When the status is uncertain, you might
need to power cycle a partner node to ensure it cannot access the shared disk. This is referred to
as STONITH. HP SFS G3.2-0 uses iLO, rather than remote power controllers, for STONITH.
5.2.1 Preparing Heartbeat
1. Verify that the Heartbeat RPMs are installed:
libnet-1.1.2.1-2.2.el5.rf
pils-2.1.3-1.01hp
stonith-2.1.3-1.01hp
48 Using HP SFS Software
- HP Part Number: SFSUGG32-E 1
- Published: May 2010 1
- Edition: 5 1
- Table of Contents 3
- 4 Table of Contents 4
- Table of Contents 5 5
- List of Figures 7
- List of Tables 9
- About This Document 11
- Related Information 12
- Structure of This Document 13
- Documentation Updates 13
- HP Encourages Your Comments 13
- 1 What's In This Version 15
- 1.3.1 Hardware Configuration 16
- Figure 1-1 Platform Overview 17
- 1.4 Server Security Policy 19
- 1.5 Release Notes 20
- 2.1 Installation 21
- 2.2 Accessing the MSA CLI 21
- 2.3.2 Creating New Volumes 22
- 2.4 MSA2000 Monitoring 24
- 2.4.1 email Notifications 25
- 2.4.2 SNMP Monitoring 26
- 3.1 Supported Firmware 28
- 3.2 Installation Requirements 29
- 3.3 Installation Phase 1 30
- 3.3 Installation Phase 1 31 31
- 3.4 Installation Phase 2 33
- 3.5.3 Configuring pdsh 35
- 3.5.4 Configuring ntp 35
- 3.6 Upgrade Installation 37
- # start lustre config 38
- # end lustre config 38
- 3.6.2 Client Upgrades 39
- 4.1 Installation Requirements 41
- 4.2 Installation Instructions 42
- 5 Using HP SFS Software 45
- 46 Using HP SFS Software 46
- 5.1.1.1 Multiple File Systems 47
- 5.2 Configuring Heartbeat 48
- 5.2.3 Configuration Files 49
- 50 Using HP SFS Software 50
- 5.2.4 Copying Files 51
- 5.2.5 Things to Double-Check 52
- 5.2.6 Things to Note 52
- 5.3 Starting the File System 53
- 5.4 Stopping the File System 53
- 5.5 Monitoring Failover Pairs 54
- 5.7.1.1 On the Server 55
- 56 Using HP SFS Software 56
- 5.7.1.3 On the Client 58
- 6 Licensing 61
- 62 Licensing 62
- 7.1 Server Reboot 63
- 7.2 Errors from install2 63
- 7.3 Application File Locking 63
- 7.4 MDS Is Unresponsive 63
- 7.8 SELinux Support 64
- Correct configuration output 65
- A HP SFS G3 Performance 67
- A.2 Single Client Performance 68
- A.3 Throughput Scaling 70
- A.3 Throughput Scaling 71 71
- A.4 One Shared File 72
- A.6 Random Reads 73
- A.7.1 Benchmark Platform 74
- A.8 10 GigE Performance 76
- A.8.1 Benchmark Platform 77
- 78 HP SFS G3 Performance 78
- A.8.3 Throughput Scaling 79
- 82 Index 82
Related products and manuals for Storage Hp StorageWorks Scalable File Share
Storage Hp Command View EVA Software User Manual
(113 pages)
(113 pages)
Storage Hp XP7 Storage User Manual
(250 pages)
(250 pages)
(58 pages)
(60 pages)© 2020, manymanuals.com. All rights reserved. | 0.688 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals