PowerVM

Expand all | Collapse all

Simplified Remote Restart - LPAR Configuration Data

  • 1.  Simplified Remote Restart - LPAR Configuration Data

    Posted Thu June 25, 2020 02:26 PM
    Hello, 

    About the synchronization of lpar configuration data in HMC and the possibles states (https://www.ibm.com/support/knowledgecenter/TI0002C/p8hat/p8hat_remresovw.htm

    1.- What (can) cause that this data isn't in REMOTE RESTARTABLE always?
    2.- Where I can find the "recommendations", if possible, to work safety with Server, HMC and LPAR  and be sure that we make all in the right way?

    Thanks ...

    Fernando

    ------------------------------
    Fernando Plaza Vidaurre
    IBM i System Admin
    ------------------------------


  • 2.  RE: Simplified Remote Restart - LPAR Configuration Data

    Posted Fri June 26, 2020 02:41 AM
    Hi Fernando,

      Remote Restart state documented at https://www.ibm.com/support/knowledgecenter/TI0002C/p8hat/p8hat_remresovw.htm represent 2 aspects . One is the actual remote restart operation status when a partition is getting remote restarted, other one is the status of configuration data collected & stored in the HMC for performing remote restart. Remote Restartable is a valid state where configuration data has been collected successfully and in case of a system crash or failure, remote restart can be initiated for the partition. 

    In a normal case, if all configuration is setup properly, data collection should be successful and status should be remote restartable., but Remote Restart status can move out of "Remote Restartable" for reasons like configuration data was never collected successfully even once (invalid), configuration data collection failure (local storage update update), not enough space to store data in the HMC (out of space) , data has been collected partially(for example, a system was connected to the hmc , but RMC connection to VIOS hosting adapters of partitions is not yet active and hence HMC is able to collect only the configuration information from hypervisor, but the virtual storage/network info from vios) , collected data has become stale (i.e., HMC has collected data earlier, but some state transition or event happened such that the data might or might not be stale) etc. Its important to check the remote restart status to make sure its at remote restartable, so that at the time of a unfortunate system failure, remote restart can be triggered to move the partition to another system and reduce downtime.

    Hope this helps. Let us know if you need more info. 

    Thanks.

    ------------------------------
    Hariganesh Muralidharan
    Cognitive Systems Management Architecture
    IBM
    ------------------------------



  • 3.  RE: Simplified Remote Restart - LPAR Configuration Data

    Posted Fri June 26, 2020 03:48 AM
    Hi Hariganesh, 

    Thank for your time ... is enough  ...

    To find information I must read all hmc readme.txt ... to find "best practices" ...

    https://delivery04.dhe.ibm.com/sar/CMA/HMA/06887/7/MH01616.readme.html

    Best Practices
    • For partitions enabled with Remote Restart or Simplified Remote Restart, if storage/network changes are made using VIOS CLI, without going through the HMC,  the user should run the HMC refdev command to refresh the partition configuration data stored for remote restart. For more information on Simplified Restart go to DeveloperWorks.
      Enhancements and New Functions


    One more, this white paper "Simplified Remote Restart" Document Author : Hari G M - Copyright IBM Corporation 2016." I have one copy but is possible to have one updated version??

    Thanks again Hariganesh ...




    ------------------------------
    Fernando Plaza Vidaurre
    ------------------------------