Last Modified - Mar 22, 2012

Added config.log file - June 01, 2010
Added details on switch logs - Aug 02, 2010
Added details on CLI debug command - Aug 24, 2010
Added details  to check active status for migration - June 29, 2011
Added migrlpar debug options


Purpose:

After complete data is collected and further data is needed where 
it's not clear what the problem is due to no time stamp in the
logs etc, below will clear up all the logs and hence the
re-create will only have the "minimum" needed afer commad
is run ....


=========  CUT =============

1. Make sure following is "active" for all lpars used:
   Run below only on the IVM to test status for all
   lpars.

   $ lssyscfg -r lpar -F rmc_state --filter lpar_ids=1
 
     lpar_ids=1 here is for IVM lpar. for client lpars modify this number.

   results should return:
   active


2. If above does not return active, try to fix RSCT:

    -----------------------------------------
    Fixing RSCT on VIOs lpars & Client LPARS:
    -----------------------------------------
    $oem_setup_env
    # lssrc -a | grep rsct
    #/usr/sbin/rsct/install/bin/recfgct
    #/usr/sbin/rsct/bin/rmcctrl -z
    #/usr/sbin/rsct/bin/rmcctrl -A
    #/usr/sbin/rsct/bin/rmcctrl -p

    Check for below:

    # lssrc -a | grep rsct
    Are IBM.HostRM and IBM.DRM and ctcas active / inoperative  now? 
    If so, there is a pretty good chance the problem is resolved.

    Below shows listing for => VIO 2.2.0.12-FP-24 SP-02

    ctrmc            rsct             5374136      active
    IBM.DMSRM        rsct_rm          9109536      active
    IBM.ServiceRM    rsct_rm          1769568      active
    IBM.DRM          rsct_rm          8847378      active
    IBM.AuditRM      rsct_rm          7864432      active
    IBM.HostRM       rsct_rm          6357090      active
    ctcas            rsct                          inoperative
    IBM.ERRM         rsct_rm                       inoperative
    IBM.CSMAgentRM   rsct_rm                       inoperative
    IBM.LPRM         rsct_rm                       inoperative

2. Clear up all error logs on all IVMs and Client lpars.
    -  errclear 0

3. Clear up cfglog for all IVMs and Client lpars
    - rm /var/adm/ras/cfglog
    - echo "log cleared" | alog -t cfg
    - echo "Create cfg log1" | alog -t cfg 
    - create file /etc/drlog.cmd containing below line:
      CFGLOG=timestamp,detail,verbosity:9 

4. sync up all times on all IVMs and Clients 

5. Provide, exact time command run
      
6  *** re-run test using CLI using "-d 5" debug flags from IVM***
   Use help command to find options.
   
   Example:
   $ migrlpar -o m -m  -t  -p  -d 5 -v

   //////////////////////
   More debugging options    
   //////////////////////
   migrlpar -o m -m managed system -t managed system -p partition name
   -i "source_msp_id=,source_msp_ipaddr=,dest_msp_id=,dest_msp_ipaddr="
   -d 5 -v 

7. Provide names and partiton ID of:
   - client LPAR
   - IVMs Source LPARS
   - IVMS Destination LPARS.

8. Provide IVMS snaps
    - snaps from IVMs ( padmin shell ) - no flags
    - This will create =>  /home/padmin/snap.pax.Z

9. Provide IVMS  ctsnaps
    - $ oem_setup_env
    - # ctsnap -x runrpttr
    - This will create =>  /tmp/ctsupt/ctsnap*.tar.gz

10. Provide Client snap and cfglog.
    - # snap -r
    - # snap -ac
    - # "alog -t cfg -o > /tmp/client.cfglog_out" ( from client )

11. From IVM: scsi info:

    FOR ALL MANAGED SYSTEMS:

     - login to IVM SERVER 
     - $ oem_setup_env 
     - # script pmr_scsi_eth.out 
     - $ su - padmin
       $ lssyscfg -r sys -F name ( to get  )
       $ lshwres -r virtualio --rsubtype scsi -m [managed_system_name] --level lpar
       $ lshwres -r virtualio --rsubtype eth -m  [managed_system_name] --level lpar 
       NOTE: add below 2 commands here, if using NPIV
     - $ exit 
     - # exit 
     -  the output of the command is placed in the pmr_scsi_eth.out file on IVMserver 

    Additional 2 commands if using NPIV;

     - lshwres -r virtualio -m  --rsubtype fc --level sys
     - lshwres -r virtualio -m  --rsubtype fc --level lpar

12. From storage switches 
    **************************************************************
    *** IF ITS 3RD PARTY STORAGE OR SWITCH CONTACT YOUR VENDOR ***
    *** FOR DATA REVIEW AND REQUIREMENTS - BELOW ARE SOME TIPS ***
    **************************************************************

      *** ZONING MULTIPLE FABRIC ***
          For Partition mobility, when using multiple fabric swiches,
          DO NOT USE port-level zoning BUT MUST use WWN Level zoning.
      *** ZONING MULTIPLE FABRIC ***


      Switch Logs for Cisco & Brocade:

      - Switch logs ("show tech-support details" for Cisco)
      - 'show tech detail' if more then 1 switch.
      - 'supportshow' collected via CLI using either
         HyperTerm or Putty to collect the output for Brocade.
      - 'supportsave'  as that has additional debug information.
      - How the RSCN ( Registered State Change Notification )
        events are sent when a zoning change is done on the switch?


    Switch Logs for McData:

      - "data collection" from the switch management console, EFCM.
      - any other related to ones described above under Cisco / Brocade.


    Switch Logs using iSCSI TOE:

      - igroup show
      - lun show -m

13)  FTP the file to ibm:
      ftp  testcase.software.ibm.com,
      login:   anonymous,
      passwd:  your email address,
      ftp>  cd /toibm/aix
      ftp>  bin
      ftp>  put  pmr#.date.pax.gz
      ftp>  quit


=============  CUT  ===============