Highlighted
Absent Member.
Absent Member.
5166 views

Connection to CRS failed.

Jump to solution

Dear all,

I've instaled a new Cell Manager (HP Data Protector v.9.0) in a CentOS machine.

As I know, all seems to be fine:

[root@BCKCENTOS01 lbin]# omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Active  [3592]
    mmd         : Active  [3590]
    kms         : Active  [3591]
    hpdp-idb    : Active  [3560]
    hpdp-idb-cp : Active  [3584]
    hpdp-as     : Active  [3623]
    omnitrig    : Active
    Sending of traps disabled.
===============================
Status: All Data Protector processes/services up and running.

 

Asking about CRS:

[root@BCKCENTOS01 lbin]# crs
**********************  DEFAULT ERROR REPORT  *******************************
[Critical] From: CRS@bckcentos01 ""  Time: 11/29/2016 12:41:07 PM
CRS is already running.
File /var/opt/omni/tmp/CRS.pid contains its process ID.


*****************************************************************************

 

It seems that is running too. So.... I guess that all in working fine in the server.

 

Now I'm trying to install GUI System in my Windows 10 machine.

I've installed Installation Server (for Windows) and GUI.

When I try to connect HP Data Protector Manager (GUI), I receive the following error:

 

Connection to CRS failed.
To start the Data Protector daemons on the Cell Manager host use the command
omnisv -start on the Cell Manager
or check if the communication between the Cell Manager and client is encrypted with the command
omnicc -encryption -status -all on the Cell Manager.

 

As you read before Data Protector Cell is running.

And the answer for: omnicc -encryption -status -all is:

[root@BCKCENTOS01 lbin]# omnicc -encryption -status -all
Client          Enabled         Enabled(CM)
bckcentos01     true            true
[root@BCKCENTOS01 lbin]#

I can reach each machine with ping (server and my computer with GUI).

I guess that GUI download a ssl certificate, but not sure where it is stored. Or how can I find and delete it.

I was searching during last days, but nothing usefull for me.

Could you please help me?

Many thanks in advance,

 

 

 

Tags (3)
0 Likes
1 Solution

Accepted Solutions
Absent Member.
Absent Member.

As it seems, I have a miss speling in de host file in Windows machine.

Now it connects to Data Protector, but it ask for a user and password to connect.

I'm trying with root and it says: Insufficient permissions, access denied.

Do you have nay clue on this?

 

Best regards,

Santiago

View solution in original post

0 Likes
3 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

CRS will be running, the error you get from the GUI is a red herring.

I would check firewalls to make sure you the GUI from windows 10 can connect through to the cell manager.

Yes once you connect a default certificate will be used.

0 Likes
Absent Member.
Absent Member.

As it seems, I have a miss speling in de host file in Windows machine.

Now it connects to Data Protector, but it ask for a user and password to connect.

I'm trying with root and it says: Insufficient permissions, access denied.

Do you have nay clue on this?

 

Best regards,

Santiago

View solution in original post

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

You need to add the windows user who starts the DP GUI to the UserList file on the cell manager (/etc/opt/omni/server/users).

Syntax:
"<DESCRIPTION>" "<USERNAME>" "<AD-DOMAIN_OR_UNIX-GROUP>" <HOSTNAME-OF-GUI-SYSTEM> "<DP-USER-GROUP>"

Syntax example:
"User for GUI access" "ADMINISTRATOR" "PEANUTS" snoopy.eu.hp.net "admin"

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.