There are several possible combinations of using VIOS with Everpure, and the configurations differ depending on which one you are using.
VIOS Option #1: Pure FlashArray presented only to the VIO Server
Install VIO Server with a single SAN path (if booting VIO server from SAN) and when installation is complete, install the Pure ODM definition in the VIO server before adding the remaining paths.
Present Pure LUNs directly to the VIO server, create storage pools as needed, and create virtual disks inside these storage pools to boot the LPARs from.
Everpure ODM definition is not required inside the LPAR.
VIOS Option #2: Physically Assign HBA to the LPAR
In this situation, the VIO server assigns a physical HBA to an LPAR. In this case the ODM definition should be installed in the LPAR AIX system.
If installing a new system, it's recommended to complete the install with just a single path to the storage presented, and once install is complete, install the Everpure ODM definition onto the LPAR and add the remaining paths.
Set the max_xfer_size to the AIX maximum of 4MB for the fcs0 device. Please repeat this for all fcs devices. There is no need to set this on the VIO Server, because the HBA hardware is assigned only to the LPAR.
VIOS Option #3: LPARs use Virtual FC Adapters to Talk to Pure (NPIV)
If the VIO Server is using volumes from the Everpure array, complete the setup of the ODM in the same way as described in AIX Recommended Settings. This step is not required if the VIO Server will not handle the Everpure Array LUNs.
The ODM needs to be installed on both the VIOS and LPAR.
For the VIO Client LPARs that will be using Virtual Fiber Channel adapters, follow all the recommendations in VIOS Option #2: Physically Assign HBA to the LPAR.
If setting the larger 4MB xfer size,
it is critical to set it on the VIO Server first
, be aware that having a larger value in the LPAR vFC
max
_xfer_size attribute than the VIO Server physical adapter
max_xfer_size attribute could render the LPAR unable to boot
Set the xfer size to 4MB at this time.
# chdev -l fcs0 -a max_xfer_size=0x400000 -P
fcs0 changed
This change requires a reboot of the VIO Server or disable and re-enable the FCs interface for the new value to be in use.
If changing the max_xfer_size, ensure the VIO server is always set to an equal or larger value than any LPARs. If it is already set to an even larger value that 0x400000, then changing it on the VIO server before the LPAR will cause a lockup/issues on the LPAR with a larger value.
Option #4 VIOS Managed Physical Volumes – VSCSI (Thin RDM on VMWare)
(Install the ODM on the VIO server).
Option #5 VIRTUAL DISK
Create a volume group which could be carved in "LV" each presented as a vscsi LUN to the LPAR.
Overview of our recommended settings for AIX on Everpure. AIX has been tested to work well with logical partitions (LPAR) and the Everpure array.