[sbutton]

Hi,

I've added some Virtual SCSI devices to my VIO server and matching devices on my LPAR, but when I run cfgdev nothing appears.

I've also added them dynamically to the active profile but they do not show up. ioslevel shows 1.3.0.0 and the virtual adapters appear to be configured correctly (as confirmed by my colleagues). Of course we could be missing something. They are all marked as "required".

One thing I have noticed is the adapters are marked as "Inactive" in the Client adapter properties. I get to this by right clicking on the LPAR Profile properties, selecting Virtual I/O Adapters tab, then clicking "Create client adapter..."

I do get a warning about "No RMC Connection" when trying to make the Dynamic changes, but I don't see why this should be. I suspect this might have something to do with the problem but I can't see how to get past this.

Any ideas?

Steve

[jprabaker]

No RMC connection is your problem, your HMC can't talk to the client over the network.

To re-initial RMC daemons run the following on the VIO server (in oem_setup_env):

/usr/sbin/rsct/install/bin/recfgct
/usr/sbin/rsct/bin/rmcctrl –z
/usr/sbin/rsct/bin/rmcctrl -A

Wait a couple of mins & verify dlpar is enabled by running lspartition -dlpar on the hmc You should see "OS:<AIX, 5.3>, DCaps:<0x3f>" on the entry for the VIO server partition. If DCaps=<0x0> then dlpar doesn't work.

However, I believe that if you get dlpar working you'll still have to shutdown & reactivate the partition to pick up the vscsi devices added by dlpar when it was broke. I had a similar problem adding virtual processesors & either a reboot or shutdown had to be done.

[sbutton]

Hi,

I've tried the above and re-started the LPARs but it doesn't seem to help. I can't run the lspartition -dlpar as these partiotions have not yet been installed with AIX, they just sit at the SMS menus for the time being. I forgot to mention that in the original post. We're still waiting for SAN disk, so we can build them.

I guess rebooting the VIO servers might help, but I'd like to avoid this as I'm going to have to kick off the other two LPARs which are being build at the moment and more importantly this is going to become more impractical as we move out of build and into live.

Steve

[jprabaker]

You run lspartition from your hmc. ssh to your hmc, login as hscroot & then run lspartition -dlpar. This will tell you if dlpar is working for each partition defined. Once you've confirmed its working I'm pretty sure you'll need to take down the VIO server to pick up vscsi devices, not sure if a reboot is required or an actual shutdown... but try a cfgdev first.

HTH

John

[jprabaker]

Tried to post a URL link but it won't let me :-(. Have you gone through the dlpar checklist? If not, google search "dlpar checklist" & the first link takes you to the checklist.

[ScriptDaddy]

You can DLPAR in VSCSI devices, however, if you did it when receiving a RMC no connection, then the DLPAR did not complete correctly.

What has happened is that the HMC know's it has DLPAR'd in the VSCSI devices, but the LPAR has no idea this has happened, since the RMC connection did not work.

You can try rebooting the HMC, see if it will reconnect to the LPAR, then try restarting RSCT (via oem_setup_env on the VIO Server). If not, then you will have to shutdown the LPAR and re-activate it to pick up the changes, if you just reboot, it will not read the partition profile. Which reminds me, make sure you added those devices to the VIO Server partition profile, other wise it will not know about the VSCSI devices you attempted to DLPAR in.

Ben