User manual HP STORAGEWORKS 20 SCALEABLE FILE SHARE STORAGEWORKS SCALABLE FILE SHARE RELEASE NOTES - VERSION 2.3

[. . . ] HP StorageWorks Scalable File Share Release Notes Version 2. 3 Product Version: HP StorageWorks Scalable File Share Version 2. 3 Published: April 2008 © Copyright 2005, 2008 Hewlett-Packard Development Company, L. P. Myrinet® and Myricom® are registered trademarks of Myricom, Inc. InfiniBand® is a registered trademark and service mark of the InfiniBand Trade Association. Voltaire, ISR 9024, Voltaire HCA 400, and VoltaireVision are all registered trademarks of Voltaire, Inc. [. . . ] (7682) Client panic in replay_lock_interpret; don't resend lock cancels and only resend if no reconnect on ETIMEDOUT case. (7677) lfs quota block count statistics do not reflect real block usage /removing files did not always reduce quota block count. (7664) Was logging /var/evlog. local on mds/admin when admin service was not running there. (7635) Repeated "disk has been inserted" events were logged after a disk has been inserted. (7610) Collectl when enabled, could fill up /var with /var/log/collectl/system log files. (7608) start syslogd on OSS nodes, thereby stopping minilogd which should not have been running on OSS nodes and slowly leaked user memory. (7492) sfsconfig: on failure to find common tcp subnet with server, find routed tcp network instead. (7359) import reference counting in a log_commit thread was incorrect, leaving a window open for the import to disappear while the thread was still using it, leading to a NULL pointer dereference in ptlrpc_prep_req (ll_log_comt thread) and crashing an OSS node. (5988) configure server failed with error can't wait for variable "Done": would wait forever. · · · · · · · · · · · · · · · Problems fixed in HP SFS Version 2. 3 1­15 1. 8 Documentation updates and corrections This section provides updates for new features and corrections for errors in the HP SFS Version 2. 3 documentation. 1. 8. 1 HP StorageWorks Scalable File Share System Installation and Upgrade Guide This section contains the following affected sections: · · · · · · · · · Section 2. 4. 3. 1a Configuring multiple InfiniBand interfaces with OFED (Section 1. 8. 1. 1) Section 2. 4. 3. 1b Configuring multiple o2ib LNETs per IB interface with OFED (Section 1. 8. 1. 2) Section 2. 4. 3. 2 Determining the OFED InfiniBand interconnect information (Section 1. 8. 1. 3) Section 5. 2. 4 Configuring the EVA software using the SSSU utility (Section 1. 8. 1. 4) Section 6. 4. 3 iLO settings -- iLO browser tasks (Section 1. 8. 1. 5) Section 6. 13 Step 13: Scanning MAC addresses (Section 1. 8. 1. 6) Section 7. 2. 3 iLO settings -- iLO browser tasks (Section 1. 8. 1. 7) Section 7. 10 Step 10: Scanning MAC addresses (Section 1. 8. 1. 8) Appendix F SSSU script examples (Section 1. 8. 1. 9) 1. 8. 1. 1 Section 2. 4. 3. 1a Configuring multiple InfiniBand interfaces with OFED Insert the following section between 2. 4. 3. 1 and 2. 4. 3. 2: SFS V2. 3 allows you to configure two or more IB interfaces on the SFS server nodes. This can be done if the HCA board has 2 InfiniBand ports, or if the servers are configured with multiple InfiniBand HCAs. Configuring multiple IB interfaces on the servers allows you to connect the SFS system to multiple IB fabrics. For instance, two computer clusters that do not share the same IB fabric can be connected to the same SFS system. The purpose of using multiple interfaces on the servers is not to increase the per server IO bandwidth, since the storage is the limiting factor. Configuring additional IB interfaces requires a unique range of IPoIB addresses for each interface. At interconnect configuration time, the sfsmgr cli will detect all IB ports connected to an IB fabric. For each corresponding IPoIB interface it will perform the following tasks: · · Prompt for the required IPoIB address information. Automatically create one LNET (o2ib0, o2ib1, . . . ) 1. 8. 1. 2 Section 2. 4. 3. 1b Configuring multiple o2ib LNETs per IB interface with OFED Insert the following section between 2. 4. 3. 1 and 2. 4. 3. 2, after 2. 4. 3. 1a above: The purpose of configuring multiple o2ib LNETs per server IB interface is to allow SFS client nodes that are configured with multiple IB interfaces to distribute the Lustre traffic across multiple LNETs to multiple server nodes. This is a method of increasing the per client node aggregate bandwidth. At the SFS server side, this requires adding multiple IB interface aliases on the same physical IB interface. There is no requirement for extra physical IB interfaces on the SFS servers side. But if there are multiple IB interfaces, each of them can have multiple aliases if desired. Configuring additional IB interface aliases requires a new unique range of IPoIB addresses for each alias. 1­16 New and changed features in HP SFS Version 2. 3 At interconnect configuration time, the sfsmgr cli will detect all IPoIB interfaces corresponding to a connected port (see the previous section). [. . . ] Using a Linux 2. 6. x kernel on the NFS server is not supported in this release. If the NFS server is configured to access the Lustre file system via an InfiniBand?Version 3. 4. 5 interconnect driver must be used, because it is compatible with Linux 2. 4. x kernels. 1. 8. 3. 16 Section 5. 1. 3 Configuration factors for multiple NFS servers Third and fourth bullets: 1­40 New and changed features in HP SFS Version 2. 3 · · If using the fsid capability in an NFS export entry, this fsid must be the same across all of the NFS servers that are exporting the same file system. Using more than four servers is not supported at this time. are replaced with the following: · It is mandatory to specify the fsid parameter in the /etc/exports file. [. . . ]