PowerVS

Power Virtual Server

Explore the cloud-based infrastructure offering from IBM that enables businesses to run IBM Power workloads in a virtualized environment on IBM Cloud.


#Power
#Power
#IIBManufacturing
#Power
#Power
#AppConnectEnterprise(ACE)
#Cloud
#Cloud
#IBMCloud
 View Only
Back to discussions
Expand all | Collapse all

Allocation of existing storage to LPARs (new or existing)

  • 1.  Allocation of existing storage to LPARs (new or existing)

    Posted Tue June 29, 2021 11:29 PM
    Hi,
    I am not sure if anyone has run into this issue that I ran into last month.  I have a number of LUNs I use for testing and assign to LPARs as I need.  However I found that I was only able to assign some LUNs to some LPARs and not others.

    I now understand that a change has been made to introduce the concept of LUN affinity (related to the back end controller, which matches the storage pool) and at the moment we are unable to allocate storage from another affinity.  Note I am not talking about Storage Tiers, affinity is a subset of the Tier.

    Thus if your rootvg is from one affinity, you will not be able to allocate exiting LUNs from the other affinity.  However when you create new LUNs for an LPAR they will have the same affinity as the rootvg.

    I understand that a change is coming towards the end of this year that will allow you to view the affinity of existing LUNs and to control the affinity of new LUNs.  I also understand that the rules restricting LPARs to using only LUNs from one affinity may be relaxed as well - but be warned, as you will be crossing storage pools, so there will be restrictions on taking snapshots.

    I hope this is useful - will update when I find out more.
    Cheers,



    ------------------------------
    --------------------
    Antony Steel (Red)
    ===============
    ------------------------------


Related Content