In today’s environment, when people demand access to more and more information, media companies are implementing new solutions for their environments, focusing on performance, availability and cost.
Because GPFS has its historical roots in multimedia, the adoption of this product for digital media environments comes as a natural evolution.
This IBM Technote focuses on (but is not limited to) the newest GPFS functionality and its on demand characteristics for digital media environments:
- Digital media information flow and requirements analyzed and matched with GPFS functionality
- Interoperability of a GPFS cluster and file sharing applications for Windows clients
The IBM Redpaper for this Technote presents a nine-step approach for configuring a GPFS cluster, and also presents various tools and techniques that make a systems administrator's life easier for GPFS implementation and day-to-day management tasks.
Using RDAC/MPP driver on Linux
When the host has more than one HBA and all those HBAs have access to one or more IBM TotalStorage DS4xxx, a multipath driver is required. For the DS4xxx family this is the redundant disk array controller/multipath proxy (RDAC/MPP) driver. On AIX, the base OS already contains the RDAC driver, also known as MPIO. For Linux, you must download and install the RDAC/MPP package manually.
The RDAC multipath driver consists of two modules:
- The mppUpper: module is loaded before any HBA and prevents the HBA to publicize LUNs to the system.
- The mppVhba: module is a virtual HBA that sits on top of the real HBA. The virtual HBA is responsible for bundling the different paths to the same LUN, organizing the traffic from and to the LUN, and presenting it to the OS as single entity.
Note that if RDAC/MPP is used, a non-failover HBA device driver is required, and auto volume transfer (AVT) must be disabled at the DS4xxx level. You achieve this by changing the host type from Linux to LNXCL. Check the latest version of the Readme.txt delivered with the RDAC/MPP driver and follow the instructions.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.