IBM i Global

 View Only
Expand all | Collapse all

Removing a storage space from an IBM i host which was used by an AIX guest.

  • 1.  Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Fri August 04, 2023 01:22 PM

    I have a Power 9 with internal disks.  The disks are hosted by an lpar of IBM i to other lpars of IBM i and to an lpar of AIX.

    The AIX guy is done with a lot of space he was using.  His words:

    <snip>

    ok, based on Chad direction I have removed the following filesystems with data from 2016:

     

    /dev/tsmsp1_lv    466.00      3.43  100%       18     1% /tsmsp1

    /dev/tsmsp2_lv    466.00      3.43  100%       18     1% /tsmsp2

    /dev/tsmsp3_lv    440.00      7.43   99%       14     1% /tsmsp3

    /dev/tsmsp4_lv    999.00      1.87  100%       30     1% /tsmsp4

     

     

    I then removed the volume groups which were made up of the following disks. Rob you should be able to reclaim these disks:

    ...

    hdisk63 -->

      hdisk63          U9009.41A.78058E0-V8-C382-T1-L8c00000000000000  Virtual SCSI Solid State Drive

    ...

    </snip>

    I was able to tie back the C382 to a particular WRKNWSD by matching the C382 to the resource tied to that WRKNWSD.

    I cracked the code on L8c00000000000000.  The L8 is known but to God.  The third character is a single character hex digit which ranges from 0-f. 0 = sequence 1 on the entries shown on WRKNWSSTG, f=16 (remember, starts with 0).  You are limited to 16 storages spaces to a single NWSD as documented at https://www.ibm.com/support/pages/create-client-partition-i-aix-or-linux-hosted-ibmi-server-partition-using-enhanced-signon-0

    So this ties back to this entry in WRKNWSSTG

    Name        Server    Seq
    AIXVM04     AIX02      13

    However when I run RMVNWSSTGL NWSSTG(AIXVM04) NWSD(AIX02) I get

    CPD8F59 - Network server storage still linked to network server operating system

    Instead of acting like a gorilla and just varying off all NWSD's associated with this lpar of AIX and trying again I got to thinking that maybe there's something the AIX guy forgot to do to free up the space?  I mean, when you're done with a disk on IBM i you have to do stuff like STRASPBAL, then go into SST and perform some actions.  Maybe there's something else they also need to do?

    Any suggestions?

    See the following cases:

    TS013811380

    TS013802403



    ------------------------------
    Robert Berendt IBMChampion
    ------------------------------


  • 2.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Fri August 04, 2023 10:01 PM

    Dear Rob

    I notice one component was not mentioned in your post and it is Virtual SCSI adapter.   My guess is, perhaps, the vSCSI server-client pair is still active and you may need to do something on them? 

    Since creating and adding vSCSI server and client adapters are need in setting up IBM i vDIsk hosting, so I guess you would need to remove the corresponding vSCSI client adapter from your AIX client LPAR's profile before you can remove the vDisks in the host LPAR?    Or you may ask your AIX colleague if there is a way to deallocate  the client vSCSI adapter from AIX first?



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



  • 3.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Fri August 04, 2023 10:19 PM

    I just found this blog post on Cleanup and Delete old Volume Groups at http://www.capacityreports.net/AIX_Blog/index.php/cleanup-and-delete-old-volume that you may want to use to check with your AIX colleague.   



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



  • 4.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Fri August 04, 2023 10:37 PM

    One last thing that comes to my head.  In the past in IBM i, removal of disk units from an ASP can only be done from DST with an IPL in manual mode.  Later on in IBM i 7.1, an enhancement was delivered that supported removal of disk from ASP on-line from SST.   So, you should ask your AIX colleague if he is certain the removal of AIX VG can be done on-line or not?  If he is not sure, just ask for the client AIX LPAR to be IPLed once and you try RMVNWSSTGL again.



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



  • 5.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 04:14 AM

    Did your AIX gyu also removed the PV ?



    ------------------------------
    Sylvain Manceau
    ------------------------------



  • 6.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 09:35 AM

    >Did your AIX gyu also removed the PV 

    ^--this:  your aix guy will need to remove the disk device from the o/s e.g "rmdev -l hdisk63". 

    I don't expect that a reboot of the aix lpar will be required.

    After removing the NWS on the ibm i, you will probably need to dynamically remove the client/server vscsi configurations from the host IBM i and AIX lpars using the HMC enhanced gui.  Avoid directly changing partition profiles 

    When using VIOS for vscsi, the HMC gui will handle the whole process of configuration cleanup, but I don't think that is true of IBM i hosted disk.



    ------------------------------
    Vincent Greene
    IT Consultant
    Technology Expert labs
    IBM
    Vincent.Greene@ibm.com


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    ------------------------------



  • 7.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 09:47 AM

    With IBM i hosting (for IBM i, AIX or Linux client lpars) dynamic removal of storage is not supported!

    Therefor the AIX lpar must be shutdonw first and the "NWSD" object on the IBM i host for the AIX lpar must the be varied off before the stroage can be removed. (also see my other answer to Roberts question).



    ------------------------------
    Janus Hertz
    Consulting IT Specialist - IBM Power / IBM i - Virtualization, Security, HA/DR.
    IBM Northern Europe
    ------------------------------



  • 8.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 11:44 AM

    I stand corrected, and now have another reason to prefer VIOS over IBM i hosting. 

    Thanks for the clarification Janus.



    ------------------------------
    Vincent Greene
    IT Consultant
    Technology Expert labs
    IBM
    Vincent.Greene@ibm.com


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    ------------------------------



  • 9.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 08:48 AM

    Hi Robert

    You need to shutdown the AIX lpar first, then varyoff the NWSD AIX02, then unlink the AIXVM04 storage. 

    Then vary-on the AIX02 NWSD again and restart the AIX lpar to verify it runs as expected.

    Once that is done you should be able to delete the AIXVM04 storage space.



    ------------------------------
    Janus Hertz
    Consulting IT Specialist - Power Systems / IBM i - Virtualization, Security, HA
    IBM
    ------------------------------



  • 10.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Mon August 07, 2023 10:16 AM
    The disks we want to free up no longer show up in lspv nor lsdev
    # lspv
    hdisk36         00f94403447d35a7                    rootvg          active
    hdisk37         00f9440345bcfe41                    tsmdbvg         active
    hdisk38         00f9440345bcfe6b                    tsmdbvg         active
    hdisk39         00f9440345bcfe96                    tsmdbvg         active
    hdisk40         00f9440345bcfec1                    tsmdbvg         active
    hdisk41         00f9440345bdae96                    tsmlogvg        active
    hdisk42         00f9440345bdaec2                    tsmlogvg        active
    hdisk45         00f9440345bf03be                    tsmdbbkupvg     active
    hdisk71         00f944036936b443                    altinst_rootvg
    hdisk0          00c058e06601ed1a                    tsmdbvg         active
    hdisk1          00c058e06601ed4f                    tsmdbvg         active
    hdisk2          00c058e060693528                    tsmlogvg        active
    hdisk3          00c058e0acdcd79f                    tsmdbvg         active
    hdisk4          00c058e0acf3e7d9                    tsmdbvg         active
    # lsdev -C -c disk
    hdisk0  Available  Virtual SCSI Solid State Drive
    hdisk1  Available  Virtual SCSI Solid State Drive
    hdisk2  Available  Virtual SCSI Solid State Drive
    hdisk3  Available  Virtual SCSI Solid State Drive
    hdisk4  Available  Virtual SCSI Solid State Drive
    hdisk36 Available  Virtual SCSI Solid State Drive
    hdisk37 Available  Virtual SCSI Solid State Drive
    hdisk38 Available  Virtual SCSI Solid State Drive
    hdisk39 Available  Virtual SCSI Solid State Drive
    hdisk40 Available  Virtual SCSI Solid State Drive
    hdisk41 Available  Virtual SCSI Solid State Drive
    hdisk42 Available  Virtual SCSI Solid State Drive
    hdisk45 Available  Virtual SCSI Solid State Drive
    hdisk71 Available  Virtual SCSI Solid State Drive
    #

    These are the disks we removed:

    name --volume group
    hdisk5 - None
    hdisk6 - None
    hdisk7 - None
    hdisk8 - None
    hdisk9 - None
    hdisk10 - None
    hdisk11 - None
    hdisk12 - None
    hdisk13 - None
    hdisk14 - None
    hdisk15 - None
    hdisk16 - None
    hdisk17 - None
    hdisk18 - None
    hdisk19 - None
    hdisk20 - None
    hdisk21 - None
    hdisk22 - None
    hdisk23 - None
    hdisk24 - None
    hdisk25 - None
    hdisk26 - None
    hdisk27 - None
    hdisk28 - None
    hdisk29 - None
    hdisk30 - None
    hdisk31 - None
    hdisk32 - None

    So now I'm guessing we're down to:

    quiescing the IBM Storage Protect app on AIX.

    Shutting down AIX

    WRKCFGSTS CFGTYPE(*NWS) CFGD(AIX*) and vary off all shown

    Then run the appropriate RMVNWSSTGL

    WRKCFGSTS CFGTYPE(*NWS) CFGD(AIX*) and vary on all that still have storage links (2 of the 3 will)

    Start AIX and verify that both AIX and IBM Storage Protect look good.

    Run the appropriate DLTNWSSTG

    True?



    ------------------------------
    Robert Berendt IBMChampion
    ------------------------------



  • 11.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Tue August 08, 2023 05:33 AM

    Yes, sound like a good plan. But just to be safe, remember to note the link sequence numbers for the storage spaces on the IBM i host, before you unlink them with RMVNWSSTGL.



    ------------------------------
    Janus Hertz
    Consulting IT Specialist - IBM Power / IBM i - Virtualization, Security, HA/DR.
    IBM Northern Europe
    ------------------------------



  • 12.  RE: Removing a storage space from an IBM i host which was used by an AIX guest.

    Posted Tue August 08, 2023 02:57 PM

    I want to thank everybody who helped.  It worked perfectly.



    ------------------------------
    Robert Berendt IBMChampion
    ------------------------------