If it is already clear which physical FC port should be used on the virtual I/O server, when adding a virtual FC client adapter, then the mapping can be carried out immediately after the virtual adapter is created. The “lpar addfc” command offers the option of specifying the physical FC port as an additional argument when creating it:

$ lpar addfc aix22 11 ms03-vio1 fcs0
aix22 slot 11 c050760b72b00012,c050760b72b00013 -> ms03-vio1 slot 38 added by DLPAR operation
aix22 slot 11 c050760b72b00012,c050760b72b00013 -> ms03-vio1 slot 38 added to current profile (standard)
ms03-vio1 slot 38 -> aix22 slot 11 added by DLPAR operation
vfchost6 mapped to fcs0
$

Of course, just like with “vios vfcmap“, the label or a unique suffix of the physical location code can be specified instead of the physical FC port:

$ lpar addfc aix22 11 ms03-vio1 Fabric1
aix22 slot 11 c050760b72b00012,c050760b72b00013 -> ms03-vio1 slot 38 added by DLPAR operation
aix22 slot 11 c050760b72b00012,c050760b72b00013 -> ms03-vio1 slot 38 added to current profile (standard)
ms03-vio1 slot 38 -> aix22 slot 11 added by DLPAR operation
vfchost6 mapped to fcs0
$