Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out) and we are drowning. I use VSCSI on on POWER6 system so I know the general idea but this appears to be a bit different. We looked at other profiles and set up things that look right as for the virtual FC adapter in the VIO Server profile. We gave the adapter id 64 and we assigned an LPAR to it SAPTEST(5). Then modified the AIX LPAR profile to include a new FC Adapter and pointed it at the VIOS id side of 64. I think we gave the client side id 5. The LPAR id is 5 as well as the port id. We need to do this on both VIO Servers I know but just working with one right now.
However the output from the lsmap command does not show all the info I see on the other vfchosts already defined. The VFC client name, VFC client DRC, and ClntName slots are empty. From other articles I have read this will only populate after the client LPAR is up and has the proper multipathing software installed on it. Then the client and VIOS will sync up. That doesn't work for me when to get the client LPAR up I am depending on a SAN disk to install the O/S on.
What am I missing? I have run the vfcmap command to assign the vadapter to the VIO servers physical adapter.
I have provided the output from the lsmap output below.
Thank you for your time.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out) and we are drowning. I use VSCSI on on POWER6 system so I know the general idea but this appears to be a bit different. We looked at other profiles and set up things that look right as for the virtual FC adapter in the VIO Server profile. We gave the adapter id 64 and we assigned an LPAR to it SAPTEST(5). Then modified the AIX LPAR profile to include a new FC Adapter and pointed it at the VIOS id side of 64. I think we gave the client side id 5. The LPAR id is 5 as well as the port id. We need to do this on both VIO Servers I know but just working with one right now.
However the output from the lsmap command does not show all the info I see on the other vfchosts already defined. The VFC client name, VFC client DRC, and ClntName slots are empty. From other articles I have read this will only populate after the client LPAR is up and has the proper multipathing software installed on it. Then the client and VIOS will sync up. That doesn't work for me when to get the client LPAR up I am depending on a SAN disk to install the O/S on.
What am I missing? I have run the vfcmap command to assign the vadapter to the VIO servers physical adapter.
Code:
vfcmap -vadapter vfchost15 -fcp fcs1Code:
$ lsmap -vadapter vfchost15 -npiv
Name Physloc ClntID ClntName ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost15 U8233.E8B.101A99P-V2-C64 5
Status:NOT_LOGGED_IN
FC name:fcs1 FC loc code:U78A0.001.DNWHN7Y-P1-C1-T2
Ports logged in:0
Flags:4<NOT_LOGGED>
VFC client name: VFC client DRC:Thank you for your time.