Occasionally it happens that a pair of predefined WWPNs should be used for a virtual FC client adapter. E.g. if, after deleting a virtual FC client adapter, it turns out that it is still needed.

In the last chapter a virtual FC client adapter of the LPAR aix22 was removed. The adapter had the two WWPNs c05076030aba0002 and c05076030aba0003. In the following we show how to recreate the adapter, in case it is needed again, using the original WWPNs; all LUNs should then be accessible again by the adapter.

When creating a virtual FC client adapter, predefined WWPNs can be specified as an additional argument, as shown below:

$ lpar addfc aix22 10 ms03-vio1 5 c05076030aba0002,c05076030aba0003 fcs4
aix22 slot 10 c05076030aba0002,c05076030aba0003 -> ms03-vio1 slot 5 added by DLPAR operation
aix22 slot 10 c05076030aba0002,c05076030aba0003 -> ms03-vio1 slot 5 added to current profile (standard)
ms03-vio1 slot 5 -> aix22 slot 10 added by DLPAR operation
vfchost2 mapped to fcs4
$

The virtual slot number 5 on the virtual I/O server could have been omitted; a free slot number would have been selected automatically (not necessarily 5). The mapping to the physical FC port fcs4 was also specified on the command line.

A look at the virtual slots shows that the virtual FC client adapter with the desired WWPNs was created in slot 10 again:

$ lpar lsvslot aix22
SLOT  REQ  ADAPTER_TYPE   DATA
0     Yes  serial/server  remote: (any)/any connect_status= hmc=1
1     Yes  serial/server  remote: (any)/any connect_status= hmc=1
5     No   eth            PVID=100 VLANS= ETHERNET0 
10    No   fc/client      remote: ms03-vio1(1)/5 c05076030aba0002,c05076030aba0003
20    No   fc/client      remote: ms03-vio2(2)/4 c05076030aba0000,c05076030aba0001
$

The mapping on the virtual I/O server ms03-vio1 has also been set up again:

$ vios lsnpiv ms03-vio1
NAME      SLOT  FC    FCLABEL  CLIENT        CLNTOS  VFCCLIENT  VFCSLOT  STATUS       PORTS
vfchost2  C5    fcs4  Fabric1  aix22(5)      AIX     fcs0       C10      LOGGED_IN      7
vfchost3  C125  fcs0  Fabric1  aixsap01(9)   AIX     fcs0       C10      LOGGED_IN      7
vfchost4  C181  fcs0  Fabric1  aixdbp02(11)  AIX     fcs0       C10      LOGGED_IN      5
vfchost5  C182  fcs0  Fabric1  aixdbi02(13)  AIX     fcs0       C10      LOGGED_IN      5
vfchost6  C38   fcs0  Fabric1  aix22(5)      AIX     fcs2       C11      LOGGED_IN      1
$

Finally, the paths and LUNs on the client LPAR can be reconfigured again with a run of the config manager in the operating system:

aix22 # cfgmgr
aix22 #

All paths and the deleted hdisk2 are available again:

aix22 # lspath
Enabled hdisk0 fscsi0
Enabled hdisk1   fscsi0
Enabled hdisk2   fscsi0
Enabled hdisk3   fscsi0
Enabled hdisk4   fscsi0
Enabled hdisk5   fscsi0
Enabled hdisk0 fscsi0
Enabled hdisk1   fscsi0
Enabled hdisk2   fscsi0
Enabled hdisk3   fscsi0
Enabled hdisk4   fscsi0
Enabled hdisk5   fscsi0
Enabled hdisk0 fscsi1
Enabled hdisk1   fscsi1
Enabled hdisk3   fscsi1
Enabled hdisk4   fscsi1
Enabled hdisk5   fscsi1
Enabled hdisk0 fscsi1
Enabled hdisk1   fscsi1
Enabled hdisk3   fscsi1
Enabled hdisk4   fscsi1
Enabled hdisk5   fscsi1
aix22 #

To configure the virtual FC client adapter in the profile only (using predefined WWPNs), the option “-p“, together with the name of the profile in question, has to be specified.