How to configure client on partitoning server with same serial and product ID on HP SIM

[Infocamere]

Hello, when try to configure on HP SIM more then one client HP-UX that is a npartition of SD , the first client previously configured
disappear from list.This happen because the HP-SIM detect a client with the same serial and product ID of Superdome.How can solve this configuration problem ?

[Brad Cunningham · Accepted solution]

I'm guessing your problem is related to not being able to talk to the npar namespace. This is what uniquely identifies the partitions in a complex



If you look at the indetification section in SIM the UUID should have a _P# after it is discovered.
Here an example from one of my servers
5C229445-0E9C-11DA-BF76-A05119CE6490_P0
The other partition is listed as
5C229445-0E9C-11DA-BF76-A05119CE6490_P1

Note the same UUID but different partition.

This information is being provided by the npar provider in WBEM


Here's an output of my provider status

root@bmitest1.msr.hp.com:/# cimprovider -ls
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
DNSProviderModule OK
NTPProviderModule OK
NISProviderModule OK
SDProviderModule OK
IOTreeModule OK
SGProvidersModule OK
EMSHAProviderModule OK
HPUXLVMProviderModule OK
HP_NParProviderModule OK
HP_ResParProviderModule OK
HP_iCODProviderModule OK
HP_iCAPProviderModule OK
HP_GiCAPProviderModule OK
HPUX_ProviderModule OK
SFMProviderModule OK
HPUXFCCSProviderModule OK
HPUXFCIndicationProviderModule OK
HPUXFCProviderModule OK
AmgrAgentProviderModule OK
HPUXRAIDSAProviderModule OK
HPUXSASProviderModule OK
HPUXSCSICSProviderModule OK
HPUXSCSIProviderModule OK
HP_VParProviderModule OK
FSProviderModule OK
HPUXIOTreeIndicationProviderModule OK
HP_UtilizationProviderModule OK
HPVMProviderModule OK
HPUXLANProviderModule OK
HPUXLANCSProviderModule OK
HPUXLANIndicationProviderModule OK

Note there is also one for VPars




The namespace for the providers are listed in the /var/opt/wbem/repository directory.

Here's what I have listed for my server


root
root#PG_InterOp
root#PG_Internal
root#cimv2
root#cimv2#hpvm
root#cimv2#hpvm#pending
root#cimv2#npar
root#cimv2#vpar

I'm not sure what your using for WBEM authentication but root will have access to all these namespaces by default. If you are going to use a non privileged user you will need to add these namespaces to the user you have created using the cimauth command.
Here's an outline on how to create a non-priviileged user


1. Create a user or use an existing non-privileged user. The specified username must represent a valid HP-UX user on the local host. In our example we will create a user named wbem , assign the user to the users group, and set a user password:

#useradd â g users wbem
#passwd wbem (When prompted provide the password and confirm the password)

NOTE: This is the user and password you will provide in HP-SIM to subscribe for WBEM indications for this client.

2. Determine the planned CIM configuration:

#cimconfig â l â p
Example Output:
sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=false
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=false
enableHttpsConnection=true
enableHttpConnection=true

3. Based on the previous output, ensure/set the following variables in the CIM planned configuration:

#cimconfig â s enableSubscriptionsForNonprivilegedUsers=true â p
#cimconfig â s enableNamespaceAuthorization=true â p

4. Stop and start the CIM Server to set the configuration changes in the CIM current configuration:

#cimserver â s
#cimserver

5. Verify the settings in the CIM current configuration:

#cimconfig â l -c
Example Output:
sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=true
shutdownTimeout=30
authorizedUserGroups=
enableRemoteprivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthroization=true
enablehttpConnection=false

6. View available namespaces. Each subdirectory under /var/opt/wbem/repository is itâ s own namespace.
Example output:

root@mtlrc137:wbem/repository> ls
root root#cimv2 root#cimv2#npar
root#PG_InterOp root#cimv2#hpvm root#cimv2#vpar
root#PG_Internal root#cimv2#hpvm#pending

7. Add read and write authorizations for the user â wbemâ to each of the namespaces found under /var/opt/wbem/repository. For Example: , root#cimv2, root#PG_InterOp, root#PG_Internal and root#cimv2#vpar, root#cimv2#hpvm:

#cimauth â a â u wbem â n root/cimv2 â R â W
#cimauth â a â u wbem â n root/PG_InterOp â R â W
#cimauth â a â u wbem â n root/PG_Internal â R â W
#cimauth â a â u wbem â n root/cimv2/npar â R â W
#cimauth â a â u wbem â n root/cimv2/vpar â R â W
#cimauth â a â u wbem â n root/cimv2/hpvm â R -W


8. Verify the users authorizations:

#cimauth â l
Example Output:
wbem, root/PG_InterOp, â rwâ
wbem, root/PG_Internal, â rwâ
wbem, root/cimv2, â rwâ



I hope this help you with your problem

brad

[Infocamere]

Thanks Brad for your help.
Comparing your configuration with that on my server I detect the following difference :
- UUID string doesn't list the partition number of client.
- Non privileged user "sim" does not had authorization WR to namenspace npar,vpar, hpvm.
So I have added access to user "sim "has you suggested.Now this is my configuration :

huxdbp02:/> cimauth -l -u sim
sim, root/cimv2, "rw"
sim, root/PG_InterOp, "rw"
sim, root/PG_Internal, "rw"
sim, root/npar, "rw"
sim, root/vpar, "rw"
sim, root/hpvm, "rw"
huxdbp02:/ > ll /var/opt/wbem/repository
total 0
drwx------ 5 cimsrvr cimsrvr 96 Dec 3 2008 root
drwx------ 5 cimsrvr cimsrvr 96 Dec 3 2008 root#PG_InterOp
drwx------ 5 cimsrvr cimsrvr 96 Dec 3 2008 root#PG_Internal
drwx------ 5 cimsrvr cimsrvr 96 Dec 3 2008 root#cimv2
drwxr-xr-x 5 cimsrvr cimsrvr 96 Aug 21 16:07 root#cimv2#hpvm
drwxr-xr-x 5 cimsrvr cimsrvr 96 Aug 21 16:07 root#cimv2#hpvm#pending
drwxr-xr-x 5 cimsrvr cimsrvr 96 Aug 21 16:07 root#cimv2#npar
drwxr-xr-x 5 cimsrvr cimsrvr 96 Aug 21 16:07 root#cimv2#vpar

After do this setting I have tried to discover a client without success.

Than I delete client and run a new discovery with root credentials and this work fine.
Since I can retain the root credentials , i don't know if can I use the nonpriv account ( sim ) for normal activity.
Otherwise I need to understand why the sim credentials doesn't access to namespace npar.

Thanks in advance Maurizio

[Infocamere]

Brad ,problem solved !

I have added an incorect authorization for user "sim" in the namespace npar.
As I wrote in my previous replay , I have digited:
" cimauth -a -u sim -n root/npar -R -W " instead of :
"cimauth -a -u sim -n root/cimv2/npar -R -W " .

Thanks.Maurizio