Power

 View Only
  • 1.  VIOS consolidation

    Posted Mon April 03, 2023 10:08 AM

    Hi, our customer is in the process of reducing their AIX footprint, and they have requested us to reduce/consolidate the number of VIOS virtualizing the connection of the LPARs in the physical frames. I have only done this via a hardware refresh/LPAR migration to a different physical frame.
    I was wondering if somebody has experience moving LPARs from one vios pair to another one in the same physical frame.

    The main roadblock I'm facing right now is the heterogenous environment: AIX and IBM i LPARs coexist in the same frame, although depending on different pairs of VIOS. Our customer would like to have just one pair of VIOS per frame, and decommision the rest.

    Anyway, if anybody has some actual experience, or some pointers on where to look for information, I'd be more than thankful.



    ------------------------------
    Luis Hernan Otegui
    ------------------------------


  • 2.  RE: VIOS consolidation

    Posted Mon April 03, 2023 10:43 AM
    IMHO, VIO Servers are not to be treated as “AIX” servers…
    Treat them as black-box infrastructure. Yes, they happen to be running AIX, but that’s not the customers concern.. They’re not paying more for having 4 of them than just 2 (that I’m aware of anyway)..
    They need to look at the full functionality-picture, and make a technical decision to consolidate, if it still makes sense.

    If ultimately you have to do it.. then for the most part it can be done dynamically. Network may be the biggest headache.
    Do you have the capacity to do an LPM off the box, then back to it again?
    when you specify the target of an LPM operation you can specify the target VIOs to use (as long as they’re defined as Mover Service Partitions)

    For storage, if using external san storage, build new paths through the new VIOs, so the client just sees additional paths show up. Then remove the old path structure from the old VIOs.
    If you’ve allocated internal storage (or LVs off of san storage on the VIO), then allocate similarly sized storage off the new VIOs, and migrate the storage on the client, (as you would with a SAN refresh).

    For network..This may cause/require an outage.. (I’m not as savvy with networking, so hopefully someone can clarify these steps)
    The more I think about this, there’s a lot that depends on how you have it configured.. Do the New/Old VIOs share VLANs, etc..
    Are you using access ports?
    Are you using ether-channel/LACP/802.3ad ??
    Does the client see multiple VLANs? Does the client have multiple IP addresses across multiple subnets?
    Is there any chance you’re using a virtual IP address (VIP)?

    As I type, I realize I’m in over my head with networking (I don’t know what I don’t know, so can’t even ask all the right questions).… so I’m going to stop here…

    Other than storage and networkging, the only other thing I can think of…
    Do you use Shared memory? (where there are paging devices defined through the VIOs)..

    IN short, you’ve just got to make sure the new VIOS have all the resources allocated.. either “migrate” to them (as with disk storage). or fail-over to them.

    Tom




  • 3.  RE: VIOS consolidation

    Posted Mon April 03, 2023 09:53 PM
    Edited by Satid Singkorapoom Tue April 04, 2023 04:33 AM

    Dear Luis

    >>>> The main roadblock I'm facing right now is the heterogenous environment: AIX and IBM i LPARs coexist in the same frame,  <<<<

    I never had this kind of experience before but I see that this fact should not be a roadblock for you at all.  I see you should aim to move all IBM i LPARs to use the additional resources you will create in the pair of VIOS that currently serves AIX LPARs. This is because I figure IBM i provides convenient capability to do so.   And then you move HW resource from the decommissioned pair of VIOS to the remaining pair.

    Of more concern as a roadblock is whether you use vSCSI virtual disk from VIOS for the client LPARs or not?  If you do, you need to add more disk units (more investment?) to the pair of VIOS that currently serves AIX LPARs and create new vSCSI disks for IBM i LPARs and use IBM i load source mirroring and STRASPBAL command to move to the new set of vSCSI disk and remove the old virtual disk.  (Use the method I described here: https://community.ibm.com/community/user/power/discussion/is-flashsystems-migration-function-available-when-only-storage-is-being-migrated#bm4ebc040a-8a7f-40f9-b98e-e22ba1f690cd )   It may be more difficult for AIX to do this and so is a good reason you should leave all AIX LPARs remain where they are.

    But if you use NPIV for all, LPARs, then it would be more convenient to move IBM i LPARs to the other pair of VIOS. After the new NPIV paths are added to IBM i LPARs, you remove the old paths from the to-be-decommissioned VIOS and run  IBM i Multipath Resetter described by Mr. Greene in the same URL I provide above ( https://www.ibm.com/support/pages/reducing-or-removing-paths-multipath-lun ). 

    As for virtual LAN, you just create more vNIC in the pair of VIOS that serves AIX LPARs and assign them to IBM i LPARs.  

    https://community.ibm.com/community/user/power/blogs/charles-graham1/2020/06/19/vnic-failover-in-powervm-225
    https://www.ibm.com/support/pages/vnic-functionality-guide

    Hope you have a successful attempt. 



    ------------------------------
    Education is not the learning of facts but the training of the mind to think. -- Albert Einstein.
    ------------------------------
    Satid S.
    ------------------------------



  • 4.  RE: VIOS consolidation

    Posted Tue April 04, 2023 06:04 AM

    I think Tom's point is important.

    If you stand back from the problem, what does a VIOS do:

    1) a device driver for physical networks
    2) a device driver for virtual networks
    3) a device driver for physical storage
    4) a device driver for virtual storage

    And not much else.

    Having this workload split between one pair of VIOS or two pairs of VIOS does not change the total number of CPU cycles to run the device drivers.

    If you monitor the VIOS they are probably not going to be using many resources, so where are the consolidation savings? 

    The CPU use will be additive, you might save a little memory (fewer copies of AIX running but the I/O buffering memory will be additive too). 

    Perhaps, there will be less effort up upgrade each VIOS once a year! 
    Is that worth the planning and hands-on effort of consolidation and the risk of mistakes=outages?

    I hope this helps, N



    ------------------------------
    Nigel Griffiths
    ------------------------------



  • 5.  RE: VIOS consolidation

    Posted Wed April 05, 2023 09:34 AM

    if VIOS has no tuning done then may be tcp_sendspace and tcp_recvspace will be 64K and if this value is increase it could improve things. There will be no outage or no need for consolidation.



    ------------------------------
    minesh patel
    ------------------------------