Comentarios (7)

1 JH3D_Aarne_Ojanperä ha hecho un comentario el Enlace permanente

worked with a bunch of 7.1 SP04 that had installed from a single mksysb. thanks a lot for this

2 meyawi ha hecho un comentario el Enlace permanente

I'm glad I could help.

3 grahd ha hecho un comentario el Enlace permanente

I follow the logic with this, I have 2 LPAR's that are reporting back 'Unknown' for AIX version. and in attempting to DLpar something, I get the dreaded RMC connection is not available. But your logic and examples are geared to AIX 7.x :) I am dealing with AIX 5.3 TL12

 
What commands would I have to follow for that version of AIX?
 
V/r
 
Dave

4 meyawi ha hecho un comentario el Enlace permanente

You could read Chris Gibson's posts on this topic :

 
- https://www.ibm.com/developerworks/mydeveloperworks/blogs/cgaix/entry/february_24_2011_6_51_pm79?lang=en
- https://www.ibm.com/developerworks/mydeveloperworks/blogs/cgaix/entry/dlpar_and_aix_5_32?lang=en

5 SEYY_Babu_Chunduri ha hecho un comentario el Enlace permanente

Hi All, I have a similar issue working with LPAR on PS701 blades. We have a setup with network configured on switch port. And later we planned to move it to trunk port to enhance the networking capabilities. Once this is changed, the LPAR lost connection with the VIOS (we are using IVM) on the management network. The service network using HEA is all in good shape after VLAN tagging. It is only the problem with other PCI-X adapters trying to use them for management network.

 
I tried all above steps, but to no avail. The rmc state still show inactive for the lpar. Can some brilliant minds throw some smart ideas to fix this.
 
$ lssyscfg -r lpar -F name,rmc_state
06-2222B,active
srvtagivacb02,inactive

6 POWERHAguy ha hecho un comentario el Enlace permanente

I just encountered a similar problem for cloning a primary node in PowerHA and making it a standby node. Though the environment as far as PowerHA was concerned worked, but errpt every 60 seconds was recording the errors I listed below. I went through the procedures above, though I stopped PowerHA on the standby node before starting. After performing the steps I got cthags was no longer found. I rebooted and all worked but I wasn't real happy with that.

 
So I recreated my environment again. The only step difference this time was when stopping PowerHA on the stby node I also stopped CAA services,
went through steps, then restarted and told it to start CAA services again. Now this exact clmgr syntax only works with PowerHA 7.1.3 SP1 or above. Earlier versions of CAA/HA have different options/commands to stop/start CAA individually. This seems to have worked for me, hopefully it works for others.
 
clmgr stop node dtcu0_stby WHEN=now MANAGE=offline STOP_CAA=yes
 
stopsrc -g rsct_rm; stopsrc -g rsct
/usr/bin/odmdelete -o CuAt -q 'attribute=node_uuid'
/usr/sbin/rsct/bin/mknodeid -f (when I ran this step I go no output, I think it just pulls in the existing one from repos disk for node but not sure)
lsattr -El cluster0
/usr/sbin/rsct/bin/lsnodeid
/usr/sbin/rsct/install/bin/recfgct
 
clmgr start node web WHEN=now MANAGE=auto START_CAA=yes
 
________________________________________________________________________________________-
LABEL: CONFIGRM_ONLINEFAIL
IDENTIFIER: E509DBCA
 
LABEL: CONFIGRM_STARTED_ST
IDENTIFIER: DE84C4DB
 
LABEL: SRC_RSTRT
IDENTIFIER: CB4A951F
 
LABEL: CONFIGRM_EXIT_ONLIN
IDENTIFIER: 68FD23E8

7 BMangesh ha hecho un comentario el Enlace permanente

I use a AIX 7.1 MKSYSB to restore 2 Lpar, on one lpar i am able to perform DLPAR Operation, but other lpar is not running.
Also i get below on one Lpar which is facing issue with the Dlpar operation, not sure what can be the issue( Tried the rsct reset on LPAR )
lsrsrc "IBM.MCP"
Resource Persistent Attributes for IBM.MCP