[Melih]

Hi pseries Friends,

i have a ugly problem,

i have a p52a which is managed by a hmc.

After installing a vio server in my p52a, i want to a add a new lpar.

But in the section where i can or want to add virtual adapter for my new Lpar i get a error-message like ..:

because my hmc is in german i try to translate this error-message:

While getting the VIO Serverinformations, following errors ...:
Partition ID 2 , which is my VIO Server, --

the E/A Servercommand failed, because the Partition ..../RMC/LparCmdRM
is not known...

this could happen, if the Partition is not reachable, or there is a firewall or the network configuration is not well-done. Because of these the RMC does not know the Partition. Check the network configuration.

....

can anyone help me please...

[cdelgadop]

Hi

Please be sure there's connectivity between the HMC and the VIOS by running ping on both ends. Confirm correct name resolution. In the VIOS you can get into a root userid shell by running the following command:

oem_setup_env

from the padmin shell. Then you can use the following command:

lssrc -a | grep rsct

to check something similar to:

lssrc -a | grep rsct
ctrmc rsct 225430 active
IBM.CSMAgentRM rsct_rm 196792 active
IBM.AuditRM rsct_rm 262358 active
IBM.ServiceRM rsct_rm 163954 active
IBM.HostRM rsct_rm 86076 active
IBM.ERRM rsct_rm 192734 active
IBM.DRM rsct_rm 213152 active
IBM.LPRM rsct_rm 258262 active
ctcas rsct 131244 active


The daemon in charge of DLPAR operations is IBM.DRM , if not installed then you need to install from AIX install CDs. If installed but not activated, then you need to activate.

Open an HMC terminal session either by ssh or as an RSH terminal in the console. Then try the following command:

lspartition -dlpar

All LPARs running these daemons below and communicating correcly with the HMC should appear.

Please take a read of the following document:

Dynamic LPAR tips and checklists for RMC authentication and authorization

Hope this helps

[Melih]

thank u very much for you help..

should i use the internal ip address of hmc to test the network or should i use the real ip adressesss? because i dont configure the network settings of my vio server yet...

regards,

melih

[ross.mather]

Thats the problem right there, you need to configure the network on the VIO to allow for the partition communication.

Because the VIO is running the HMC wants to verify the state of affairs on the VIO rather than blindly trusting the HMC data. The other way to avoid the message is to shutdown the VIO first. Of course you can only do this if you don't have any LPARS using it.

As a brief aside the LPAR cannot address the Service Processor (which is attached to the HMC via the private network), so this communication is directly to the LPAR over the public network.

[Melih]

if i use in my vio the command

lssrc -a | grep rsct

i get

ctrmc rsct 245882 active
IBM:ERRM rsct 155882 active
.....
...
ctcas rsct inoperative
IBM.LPRM rsct_rm inoperative
IBM.HostRM rsct_rm inoperative
IBM.DRM rsct_rm inoperative



i try to start the service

startsrc -s IBM.DRM

and get following msg:

The IBM.DRM Subsystem has been started.

but nevertheless a lssrc -a show me an inoperative status of the service IBM.DRM

now my question:

what is the real problem, the not configured network settings or the inactive daemons?

regards...

[cdelgadop]

Hi

Your HMC has two ip address: one internal that connects every pSeries p5 server to the HMC using the HMC1/HMC2 Ethernet ports in the back of your server. This is a private network you can configure with Dinamic ip address or fixed ones and should have the Partition Communication checkmark enabled, as Ross already said. The second ip address is one on your organization network that connects the HMC daemons with the corresponding ones on each server or LPAR running AIX/Linux instances configured with RSCT subsystem.

Once you have these two networks configured your RSCT daemons should start working and allows you to make Dinamic LPAR operations on either physical and virtual devices.

Hope this helps

[ross.mather]

Regarding the ibm.DRM being inoperative, from the excellent link from cdelgaop:

IBM.DRM and IBM.HostRM are "lazy started" resource managers; they're only started when they get used. If IBM.DRM and IBM.HostRM are inoperative, there's a good chance you're having network/hostname setup problem between HMC and the LPAR. To correct this, see Table 3. Verify Your RMC/DLPAR setup, below.