Improved control for Live Partition Mobility : Choose your destination fibre channel port

I’m working in an virtualized environnement fully based on NPIV. All NPIV lpars can move from one machine to another with Live Partition Mobility. A few months ago I had to move all lpars from one machine to another, and I realized one major drawback of Live Partition Mobility. All Virtual I/O Servers were configured with two or four fibre channel adapters. When a mobility operation is performed the moving lpar is always using the first fibre channel adapter. If you have 60 lpars on a machine it can be a big problem : fibre channel switch port can be saturated. With the new release of PowerVM, you can now choose the destination fibre channel adapter and all lpars can be distributed among all fibre channel adapters.

Prerequisites

Be sure Hardware Management Console and Virtual I/O Server are up to date with the latest version :

  • Hardware Management Console version has to be 7.6.0 :
  • # lshmc -V 
    "version= Version: 7
     Release: 7.6.0
     Service Pack: 1
    HMC Build level 20121109.1
    ","base_version=V7R7.5.0
    "
    
  • Source and destination Virtual I/O Servers have to be 2.2.2.1 :
  • # ioslevel 
    2.2.2.1
    

Mobility

Here is an example : all virtual fibre channel adapters are mapped on the same fibre channel adapter : fcs0 is mapped to seven virtual fibre channel adapters, and fcs1 to none, this is a result of multiple mobility operations :

# lsnports
name             physloc                        fabric tports aports swwpns  awwpns
fcs0             U5803.001.9ZZ03PZ-P1-C2-T1          1     64     57   2048    2021
fcs1             U5803.001.9ZZ03PZ-P1-C2-T2          1     64     64   2048    2048
# lsmap -all -npiv | grep "FC name"
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1
FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P1-C2-T1

Choosing the destination fibre channel adapter can only be done using command line (I hope a dialog box will be available with the next Hardware Management Console release). You have to choose the destination adapter by your own :

  • Before the mobility operation 64 aports are available on fcs5 on this Virtual I/O Server :
  • # lsnports 
    name             physloc                        fabric tports aports swwpns  awwpns
    fcs2             U5803.001.9ZZ03PZ-P2-C2-T1          1     64     64   2048    2048
    fcs3             U5803.001.9ZZ03PZ-P2-C2-T2          1     64     64   2048    2048
    fcs4             U5803.001.9ZZ03PZ-P2-C3-T1          1     64     64   2048    2048
    fcs5             U5803.001.9ZZ03PZ-P2-C3-T2          1     64     64   2048    2048
    
  • The mobility operation is launched by the command line only, as you can see fibre channel adapter fcs5 is used on this mobility operation :
  • # migrlpar -o m -m P795-SRC -t P795-DST -p lpar-test -w 1 -i 'virtual_fc_mappings="10/vios1/15//fcs5,11/vios2/16//fcs5",source_msp_name=vios3,dest_msp_name=vios1,shared_proc_pool_name=shp_test'
    
  • After the mobility operation 63 aports are available on fcs5 on the destination Virtual I/O Server :
  • # lsnports
    name             physloc                        fabric tports aports swwpns  awwpns
    fcs2             U5803.001.9ZZ03PZ-P2-C2-T1          1     64     64   2048    2048
    fcs3             U5803.001.9ZZ03PZ-P2-C2-T2          1     64     64   2048    2048
    fcs4             U5803.001.9ZZ03PZ-P2-C3-T1          1     64     64   2048    2048
    fcs5             U5803.001.9ZZ03PZ-P2-C3-T2          1     64     63   2048    2045
    

Use case

After moving all my lpars from one machine to another here is the result : all lpars fibre channel adapters are distributed among all the real fibre channel adapters.

# lsnports
name             physloc                        fabric tports aports swwpns  awwpns
fcs0             U5803.001.9ZZ03PZ-P2-C6-T1          1     64     43   2048    1967
fcs1             U5803.001.9ZZ03PZ-P2-C6-T2          1     64     58   2048    2030
fcs4             U5803.001.9ZZ03PZ-P2-C8-T1          1     64     55   2048    2017
fcs5             U5803.001.9ZZ03PZ-P2-C8-T2          1     64     59   2048    2033
# /usr/ios/cli/ioscli lsmap -all -npiv | grep "FC name" | sort | uniq -c
  12 FC name:fcs0                    FC loc code:U5803.001.9ZZ03PZ-P2-C6-T1
   8 FC name:fcs1                    FC loc code:U5803.001.9ZZ03PZ-P2-C6-T2
   8 FC name:fcs4                    FC loc code:U5803.001.9ZZ03PZ-P2-C8-T1
   9 FC name:fcs5                    FC loc code:U5803.001.9ZZ03PZ-P2-C8-T2

Hope this can help.

3 thoughts on “Improved control for Live Partition Mobility : Choose your destination fibre channel port

  1. Hi, congratulatiosn for your web site, is amazing and give us a lot of useful tips, i have a question
    the syntax virtual_fc_mappings=”10/vios1/15//fcs5,11/vios2/16//fcs5 means that vfc slot 10 that belongs to vios1 in the destination machine must be mapped to the physical port fcs5 and virtual fc slot 15, the same is for vios 2 and fcs5 in the destination machine?

    thanks for your help, the man is a little bit confused for me

    • Hi Carlos, Thanks for your support :

       virtual_fc_mappings
                         (slot_num/vios_lpar_name/vios_lpar_id[/[vios_slot_num][/
                         [vios_fc_port_name]]]),
      

      In my case :
      10 = First Virtual I/O Client FC adapter slot number.
      vios1 = Destination Virtual I/O Server on which adapter with slot number 10 will be mapped.
      15 = Destination Virtual I/O Server lpar id.
      fcs5 = Destination physical fibre channel adapter on which Virtual I/O Client FC adapter will be mapped.
      11 = Second Virtual I/O Cleint FC adapter slot number.
      vios2 = Destination Virtual I/O Server on which adapter with slot number 11 will be mapped.
      16 = Destination Virtual I/O Server lpar id.
      fcs5 = Destination physical fibre channel adapter on which Virtual I/O Client FC adapter will be mapped.

      Hope it helps.
      Regards,

      BenoƮt.

      • In your example, your destination managed system have 2 VIOS : vios1 and vios2 ? VIOS1 have fcs5 and VIOS2 also have fcs5 . So what phsycal FC port fcs5 on VIOS1 map to, what physical FC port fcs5 on VIOS2 map to ? Two fcs5 can not map to one physical FC port right ?
        You will migrate LPAR lpar-test from P795-SRC to P795-DST and mapping FC to both vios1 and vios 2 for HA. Is this right ?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>