DLPAR capable with IVM - checks to do

I cannot find the post with the comment that DLPAR capability was not working with IVM.

The two commands that need to be run are (as root, padmin does not know this command):
VIOS: lsrsrc IBM.MngNode
CLIENTS: lsrsrc IBM.MCP

Examples:

# lsrsrc IBM.MngNode
Resource Persistent Attributes for IBM.MngNode
resource 1:
        Name                   = "192.168.129.102"
        NodeID                 = 14773711625430560719
        KeyToken               = "192.168.129.102"
        Aliases                = {}
        IPAddresses            = {"192.168.129.102"}
        HWType                 = "020123A4B"
        HWModel                = "9110-51A"
        HWSerialNum            = "0123A4B"
        LParID                 = "2"
        StorageFacilityImageID = ""
        ActivePeerDomain       = ""
        NodeNameList           = {"x101"}
resource 2:
        Name                   = "192.168.129.107"
        NodeID                 = 14592256202647740844
        KeyToken               = "192.168.129.107"
        Aliases                = {}
        IPAddresses            = {"192.168.129.107"}
        HWType                 = "020123A4B"
        HWModel                = "9110-51A"
        HWSerialNum            = "0123A4B"
        LParID                 = "7"
        StorageFacilityImageID = ""
        ActivePeerDomain       = ""
        NodeNameList           = {"x101"}
resource 3:
        Name                   = "192.168.129.104"
        NodeID                 = 11534565260322329834
        KeyToken               = "192.168.129.104"
        Aliases                = {}
        IPAddresses            = {"192.168.129.104"}
        HWType                 = "020123A4B"
        HWModel                = "9110-51A"
        HWSerialNum            = "0123A4B"
        LParID                 = "4"
        StorageFacilityImageID = ""
        ActivePeerDomain       = ""
        NodeNameList           = {"x101"}
resource 4:
        Name                   = "192.168.129.103"
        NodeID                 = 7368169307909237225
        KeyToken               = "192.168.129.103"
        Aliases                = {}
        IPAddresses            = {"192.168.129.103"}
        HWType                 = "020123A4B"
        HWModel                = "9110-51A"
        HWSerialNum            = "0123A4B"
        LParID                 = "3"
        StorageFacilityImageID = ""
        ActivePeerDomain       = ""
        NodeNameList           = {"x101"}
resource 5:
        Name                   = "192.168.129.106"
        NodeID                 = 5618725486397751937
        KeyToken               = "192.168.129.106"
        Aliases                = {}
        IPAddresses            = {"192.168.129.106"}
        HWType                 = "020123A4B"
        HWModel                = "9110-51A"
        HWSerialNum            = "0123A4B"
        LParID                 = "6"
        StorageFacilityImageID = ""
        ActivePeerDomain       = ""
        NodeNameList           = {"x101"}
# 
root@x107:[/]lsrsrc IBM.MCP
Resource Persistent Attributes for IBM.MCP
resource 1:
        MNName            = "192.168.129.107"
        NodeID            = 13046875787897679480
        KeyToken          = "x101"
        IPAddresses       = {"192.168.129.101"}
        ConnectivityNames = {"192.168.129.107"}
        HMCName           = "9110-51A*0123A4B"
        HMCIPAddr         = "192.168.129.101"
        HMCAddIPs         = ""
        HMCAddIPv6s       = ""
        ActivePeerDomain  = ""
        NodeNameList      = {"x107"}

If this are being filled, then the RMC communication is working and DLPAR abilities should be working.

1 Like

thanks, here is the output

VIOS SERVER

$ oem_setup_env
# lsrsrc IBM.MngNode
Resource Persistent Attributes for IBM.MngNode
resource 1:
        Name             = "10.1.1.128"
        NodeID           = 15100939804571899700
        KeyToken         = "10.1.1.128"
        Aliases          = {}
        IPAddresses      = {"10.1.1.128"}
        ActivePeerDomain = ""
        NodeNameList     = {"ibmvios"}
resource 2:
        Name             = "10.1.1.110"
        NodeID           = 1439001851767854463
        KeyToken         = "10.1.1.110"
        Aliases          = {}
        IPAddresses      = {"10.1.1.110"}
        ActivePeerDomain = ""
        NodeNameList     = {"ibmvios"}

At the client side

root@test8:/>lsrsrc IBM.MCP
/usr/sbin/rsct/bin/lsrsrc-api: 2612-010 Resource class IBM.MCP is not defined.
root@test8:/>

root@test8:/>oslevel -s
5300-01-00-0000

root@test8:/>lslpp -l | grep -i csm
  csm.client                1.4.0.10  COMMITTED  Cluster Systems Management
  csm.core                  1.4.0.10  COMMITTED  Cluster Systems Management
  csm.diagnostics           1.4.0.10  COMMITTED  Cluster Systems Management
  csm.dsh                   1.4.0.10  COMMITTED  Cluster Systems Management Dsh
  csm.msg.EN_US.core         1.4.0.0  COMMITTED  CSM Core Func Msgs - U.S.
  csm.msg.en_US.core         1.4.0.0  COMMITTED  CSM Core Func Msgs - U.S.
  csm.client                1.4.0.10  COMMITTED  Cluster Systems Management
  csm.core                  1.4.0.10  COMMITTED  Cluster Systems Management
  csm.diagnostics           1.4.0.10  COMMITTED  Cluster Systems Management
  csm.dsh                   1.4.0.10  COMMITTED  Cluster Systems Management Dsh
root@test8:/>

root@test8:/>lsrsrc IBM.ManagementServer
Resource Persistent Attributes for IBM.ManagementServer
resource 1:
        Name             = "10.1.1.110"
        Hostname         = "10.1.1.110"
        ManagerType      = "HMC"
        LocalHostname    = "10.1.1.128"
        ClusterTM        = "9078-160"
        ClusterSNum      = ""
        ActivePeerDomain = ""
        NodeNameList     = {"test8"}

root@test8:/>lssrc -a | grep rsct
 ctrmc            rsct             192636       active
 IBM.ServiceRM    rsct_rm          245888       active
 IBM.ERRM         rsct_rm          237704       active
 IBM.CSMAgentRM   rsct_rm          151708       active
 IBM.AuditRM      rsct_rm          241786       active
 ctcas            rsct                          inoperative
 IBM.HostRM       rsct_rm                       inoperative

root@test8:/>lsrsrc IBM.MCP
/usr/sbin/rsct/bin/lsrsrc-api: 2612-010 Resource class IBM.MCP is not defined.
root@test8:/>

root@test8:/>lparstat -i
Node Name                                  : test8
Partition Name                             : test8
Partition Number                           : 11
Type                                       : Shared-SMT
Mode                                       : Uncapped
Entitled Capacity                          : 0.10
Partition Group-ID                         : 32779
Shared Pool ID                             : 0
Online Virtual CPUs                        : 1
Maximum Virtual CPUs                       : 4
Minimum Virtual CPUs                       : 1
Online Memory                              : 2048 MB
Maximum Memory                             : 2048 MB
Minimum Memory                             : 2048 MB
Variable Capacity Weight                   : 128
Minimum Capacity                           : 0.10
Maximum Capacity                           : 4.00
Capacity Increment                         : 0.01
Maximum Dispatch Latency                   : 17996174
Maximum Physical CPUs in system            : 4
Active Physical CPUs in system             : 4
Active CPUs in Pool                        : 4
Unallocated Capacity                       : 0.00
Physical CPU Percentage                    : 10.00%
Unallocated Weight                         : 0
root@test8:/>



what could be the issue ?

I am guessing that the two versions of VIOS and AIX do not communicate with each other. They changed the names of the lsrsrc components.

I expect if you can get your AIX 5.3 updated to at least TL7 (best guess, there were a lot of changes to bring AIX 5.3 in line with AIX 6) it might work.

command I use to see what is known is:

for i in `lsrsrc | grep IBM`
do
lsrsrc $i
echo
done

One of these should have related information. But basically, my gut says the client does not know how to converse with VIOS.

Not recommended!!! Or - Install a 1.X VIOS. I think it is easier to install/update one partition and see if it works then than go backwards with VIOS.