Network Management / (OpenView-NNM) Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

How to list cluster.keystore using keytol

SOLVED
Go to Solution
Regular Advisor

How to list cluster.keystore using keytol

Hello Experts

 

is there any way to list the cluster.keystore using keytool ?

 

I am getting following error, not sure it is due to some syntax error

 

E:\Program Files\HP\HP BTO Software\nonOV\jdk\b\bin>keytool.exe -list -keystore
"F:/Program Data/HP/HP BTO Software/NNMPerformanceSPI/nnmappfailover/keystore/cl
uster.keystore"
keytool error: java.io.IOException: Invalid keystore format

1 ACCEPTED SOLUTION
Honored Contributor

Re: How to list cluster.keystore using keytol

Hi Tanish

 

The cluster.keystore is not a standard keystore you can edit with the java keytool. This store is not customizable and is generated with a random key at installation time. If for some reasons the cluster.keystore is corrupt, then you can copy it from another system if required, just make sure you stop the nnmcluster daemon on the target system before copying the cluster.keystore.

 

The cluster.keystore is used to encrypt all communication between the AF cluster members and therefore, all members must have the same cluster.keystore file. The encryption is based on the standard jgroups protocol encryption.

 

Hope this helps

Dieter

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
1 REPLY
Honored Contributor

Re: How to list cluster.keystore using keytol

Hi Tanish

 

The cluster.keystore is not a standard keystore you can edit with the java keytool. This store is not customizable and is generated with a random key at installation time. If for some reasons the cluster.keystore is corrupt, then you can copy it from another system if required, just make sure you stop the nnmcluster daemon on the target system before copying the cluster.keystore.

 

The cluster.keystore is used to encrypt all communication between the AF cluster members and therefore, all members must have the same cluster.keystore file. The encryption is based on the standard jgroups protocol encryption.

 

Hope this helps

Dieter

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.