DLPAR Question 1

[axelsche]

Hi,

I have a p650 and have created 2 Partitions on it.
If I right click the one partition I get the DLPAR Option.
If I right click the other partition I dont't get the DLPAR Option to move
resources in and out the partition. Both Partitons have AIX 5.2 ML1 installed.

Any ideas?
TIA
Axel

 

[ogniemi]

Try logout HMC and login again. I met similiar after LPAR rebooting (before reboot DLPARing was possible after disappeared from menu)

regards,m.

 

[slamcorp]

Have you made required changes to HMC and host to run dlpar? here is a clip;

1.0 Verify the DLPAR Requirements
Please see Appendix session if you need instruction how to access Linux on command line.

Verify > Command -> Result -> Action
1 HMC level Click [Help] and then [About] on the HMC main window.
This should be release 3 version 1.1 or higher
Customers are encouraged to get the latest software which can be obtained at

http://techsupport.services.ibm.com/server/hmc?fetch=corrsrv.html

2 AIX Firmware
> lsmcode
Platform Firmware level is RKA20905
System Firmware level is RG02*_GA3_*
3 AIX filesets required for DLPAR
(on each LPAR/SMP) AIX level should 5.2. These following filesets should be on partitions.
> lslpp -l rsct.core*
> lslpp -l csm.client
The missing fileset can be installed from the AIX installation CD.
1.0 Checklist for DLPAR Setup
1.0.1 Verify If the Required Software is Functional

Verify Result and Action
1 HMC daemons are running > su - root
> lssrc -a
Subsystem Group PID Status
ctrmc rsct 822 active
ctcas rsct 823 active
IBM.DMSRM rsct_rm 906 active
IBM.LparCmdRM rsct_rm 901 active

If these daemons are active go to step 2:
If any of the daemons show as inoperative, start it manually by
> startsrc -s <subsystem name>
Example: startsrc -s ctcas
If a daemon can't be started
Please contact IBM service personnel.
2 AIX daemons are running
(on each LPAR/SMP with AIX 5.20) > su - root
> lssrc -a | grep rsct
Subsystem Group PID Status
ctrmc rsct 21044 active
ctcas rsct 21045 active
IBM.CSMAgentRM rsct_rm 21045 active
IBM.ServiceRM rsct_rm 11836 active
IBM.DRM rsct_rm 20011 active
IBM.HostRM rsct_rm 20012 active

IBM.DRM and IBM.HostRM are ‘lazy started’ resource managers which means they’re only started when they get used. If IBM.DRM and IBM.HostRM are &quot;inoperative,” there is a good chance that you’re having network/hostname setup problem between HMC and the partition; to correct this, please refer to section “Verify Your RMC/DLPAR Setup.”
If any of the daemons show as inoperative
> startsrc -s <subsystem name>
Example: startsrc -s ctcas
If ctcas can’t be started
If ctcas can't be started, please open a PMR before contact your IBM service personnel.

NOTES:
ctrmc: is a RMC subsystem
ctcas: is for security verification
IBM.DMSRM: is for tracking statuses of partitions
IBM.LparCmdRM: is for DLPAR operation on HMC
IBM.CSMAgentRM: is for handshaking between the partition and HMC
IBM.DRM: is for executing the DLPAR command on the partition.
IBM.HostRM: is for obtaining OS information.
1.0.1 Verify Your RMC/DLPAR Network/Hostname Setup
Verify >Result and Actions
1 HMC: List partitions authenticated by RMC
> /opt/csm/bin/lsnodes -a Status
partition01 1
partition02 0
partition03 1
Where “1” means partition is activated and authenticated for DLPAR; “0” means otherwise.
If the partition is activated and still shows Active<0>, you could either have network or hostname setup problem. If you have just rebooted the HMC, wait for a few minutes. If nothing changes after that, check your hostname/network setup as in section Setting up HMC /Partition(s) Hostname and Network.
2 HMC: List partitions recognized by DLPAR > lspartition -dlpar
<#0> Partition:<001, partition01.company.com, 9.3.206.300> Active:<1>, OS:<AIX, 5.2>, DCaps:<0xf>, CmdCaps:<0x1, 0x0>
<#1> Partition:<002, partition02.company.com, 9.3.206.300> Active:<0>, OS:<AIX, 5.2>, DCaps:<0xf>, CmdCaps:<0x1, 0x0>
<#2> Partition:<003, partition03.company.com, 9.3.206.300> Active:<0>, OS:<, 5.1F>, DCaps:<0x0>, CmdCaps:<0x0, 0x0>

If all active AIX 5.2 partitions are listed as Active<1>, ..., DCaps:<0xf> your system has been set up properly for DLPAR, you can skip the checklist now.
(In this example, partition 002 is being shut down, partition 003 is not activated for it is AIX 5.1.)
If you’re missing some active partitions or some partitions are reported as Active<0>, your system probably still has network/hostname set up problem. Refer to section Setting up HMC/Partition(s) Hostname and Network.
(If you partition is Active<1> but the GUI is still not DLPAR capable, do a rebuild to get around this problem. See Appendix session for more information about this problem.)
If you still can’t get partitions recognized by DLPAR after verifying the checklist, contact IBM service personnel.
3 AIX: Ensure /var directory is not 100% full
(on each LPAR/SMP) > df
If /var is 100% full, use smitty to expand it. If there is no more space available, visit subdirectories to remove unnecessary files (e.g. trace.*, core, etc.)
After expanding the /var directory, execute these command to fix possibly corrupted files.
> rmrsrc -s &quot;Hostname!='t' &quot; IBM.ManagementServer
> /usr/sbin/rsct/bin/rmcctrl -z
> rm /var/ct/cfg/ct_has.thl
> rm /var/ct/cfg/ctrmc.acls
> /usr/sbin/rsct/bin/rmcctrl -A
4 AIX: Verify if you have network problem?
(From each LPAR/SMP) > ping <hmc_hostname>
If ping fails, check your hostname/network setup. See section Setting up HMC/Partition(s) Hostname and Network.

5 AIX: Verify partition(s) to HMC authentication
(from each LPAR/SMP) > CT_CONTACT=<HMC name> lsrsrc IBM.ManagedNode
You should get a list of resource classes on HMC.
If there is any error, you probably have network/hostname problem, please refer to section Setting up HMC /Partition(s) Hostname and Network.
6 HMC: Verify network setup by telnet-ing into each partition(s) from the HMC. > telnet <hostname>
> &quot;Ctrl c&quot; or &quot;exit&quot; to end
If you can’t telnet, you have a network problem, refer to section 3.0 Setting up HMC/Partition(s) Hostname and Network.
7 HMC: Verify HMC to partition(s) authentication > CT_CONTACT =<partition_hostname> lsrsrc IBM.ManagementServer
If nothing is displayed or if there are any errors, you probably have a hostname problem, please refer to section Setting up HMC /Partition(s) Hostname and Network.
1.0 Setting up the HMC/Partition(s) Hostname and Network
Most of DLPAR problems we have encounter from the labs during testing have been improper network and hostname(s) setup. This section aims to reduce these network setup/configuration problems.
First, find out the hostname format the HMC and its partition(s) are using; short or long name. Your setup depends largely on the format of the hostname. The hostname format can be determined by typing the command &quot;hostname” on the HMC and AIX system respectively then use “host return_from_hostname” to verify it.
Example:
> hostname
Partition.company.com
> host Partition.company.com
Partitition.company.com has address 9.3.14.199
1.0.1 If DNS is On

1.0.1.1 If the HMC and the Partition(s) both use Long name
Ÿ No hostname entry is needed in /etc/hosts on either AIX or the HMC.
Ÿ If /etc/hosts has the hostname entry, the longname must be before the short name for HMC and all partitions (host names are case sensitive).
Example:
10.10.10.11 mymachine.mycompany.com mymachine
Ÿ After update /etc/host file, refresh RMC by either rebooting or
> /usr/sbin/rsct/bin/rmcctrl -z
> /usr/sbin/rsct/bin/rmcctrl -A
1.0.1.2 Other Hostname Formats
Ÿ If the hostname command returns the short name, put the shortname before the longname in /etc/hosts on both HMC and the partitions; If the hostname command returns the long name, put the longname before the shortname in the /etc/hosts file on HMC and all partitions (names are case sensitive).
Example:
10.10.10.11 mymachine mymachine.mycompany.com
Ÿ Make sure that on the partition(s) (just partition(s)), the file /etc/netsvc.conf exists with one line: hosts=local,bind
Ÿ Refresh RMC by either rebooting or by commands
> /usr/sbin/rsct/bin/rmcctrl -z
> /usr/sbin/rsct/bin/rmcctrl -A
1.0.2 If DNS is Off
Ÿ The HMC and partition(s) /etc/hosts file need to be modified to contain the correct entries for the HMC and all partitions’ hostnames. If the hostname command returns the short name, put the short name before the longname in /etc/hosts for HMC and all partitions (names are case sensitive). If the hostname command returns the long name, put the long name before the short name in /etc/hosts for HMC and all partitions (names are case sensitive)
Ÿ Make sure that on the partition(s) (just partition), file /etc/netsvc.conf exists with one line: hosts=local,bind.
Ÿ Refresh RMC by either rebooting or
> /usr/sbin/rsct/bin/rmcctrl -z
> /usr/sbin/rsct/bin/rmcctrl -A
Customers should add all the LPAR's hostnames to the /etc/hosts file on the HMC. The HMC hostname must be added to each LPAR /etc/hosts file. Because the customer does not have DNS data, we do not have a domain name, only a short hostname, therefore the DNS enabled box will not be enabled.

 

[admincff]

Check the network configuration of your partition, and in your HMC console.

 

[jie]

yes admincff is right put the ip address of the hmc console in the /etc/host of both partition.

 

[trifo]

Hi!

This is just the topic I needed. Thanks slamcorp, I gave a star to you. Now we are on to put your advices in practice.

One more question: can I switch a running LPAR to DLPAR? My guess is "no", but there is a hope.

--Trifo