icapstatus (GiCAP) fails

[Romalfox]

Team,


I have 2 RX8640, both contain 1 nPar and each nPar contains 2 vPar.
I have one blade running HPUX running GiCAP software.

All systems have been make_sys_prep'd from a common image (but changes are that some things got messed up in the meantime)

Both Vpars in Rx2 work fine, but both Vpars in Rx1 need some help:
*********************************
[r1nracp:root:/]#icapstatus
Software version: B.11.31.08.03
System ID: r1nracp
Serial number: DEH4813FDC
Product number: AB443A
Unique ID: 7c326747-1991-11dd-b379-ecc5cda46f53
System contact e-mail: Not set
From e-mail: Set to the default ('adm')
Asset reporting: off
Temporary capacity warning period: 15 days
Exception status: No exception

ERROR: Unexpected error

ERROR: Unable to execute command:
/opt/wbem/bin/wbemexec -t 600000

GenericSysName [HP Release B.11.31] (see /etc/issue) THIS IS A PRIVATE COMPUTER SYSTEM --- USAGE MAY BE MONITORED AND UNAUTHORIZED ACCESS OR USE MAY RESULT IN CRIMINAL OR CIVIL PROSECUTIONPermission denied (publickey,password,keyboard-interactive).

Local Virtual Partition Status
------------------------------
Total number of assigned cores: 8
Number of active assigned cores: 8
Number of inactive assigned cores: 0
Additional cores that can be assigned with current usage rights: 0
Number of cores that could be assigned with additional usage rights: 0
Number of cores that can be assigned with temporary capacity: 0
Number of cores currently unavailable for assignment: 6

**************************
As you can understand, it's the ERROR part which worries me. (permision denied)
Especially, because it should be a GiCAP system and when I go to the GiCAP manager (b2qgi) and do:
***********************
[b2qgi:root:/tmp]#icapmanage -s
Software version: B.08.03
Serial number: GB8812F3MS
6 GiCAP Sharing Rights: 0 in use, 6 available

Group ID: RX
Group Members:
R2
r2nracp.mle.mycorp.com

and want to add the r1-system
[b2qgi:root:/tmp]#icapmanage -a -m R1:r1nracp.mle.mycorp.com -g RX
icapmanage command failed.
1 is already a member of a group managed by 127.0.0.1

I think both issues are related.

I should admit that this morning I had a working situation, however I decided to clean up my GiCAP groups (deleted everything in the GiCAP manager using the icapmanage commands), and then wanted to recreate my groups similarly, however now I'm stuck ....

Can someone help ?