Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

There is no UNIX Installation Server available in this cell, only linux servers are configured with the data protector.

hp_dataprotector_1.JPG

and i cannot able to check the below commands in MIPRD server.

omnicheck -patches
omnisv -version

 

regards

Narendran

 

0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

hp_dataprotector_2.JPG

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

A Linux installation server is also a valid UNIX installation server. This means bidevqly should be enough for what I want to do. Good news.

Have you tried to upgrade the client miprd from GUI using Clients => Right click on miprd => Upgrade? What is the result?

If this fails, right click on the client and select Remove and also remove software if prompted. Then perform a push installation to miprd agian using Clients => Add Clients => Select the UNIX Installation server. 

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

tried to upgrade the client miprd from GUI using Clients => Right click on miprd => Upgrade and it has upgraded successfully.hp_dataprotector_upgrade.JPG

0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

i got one warninghp_dataprotector_error.JPG

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

This was more or less expected, try to uninstall the client and install the components again remotely.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

remotely means the same as upgrade..?

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

@Sebastian.Koehler wrote:

If this fails, right click on the client and select Remove and also remove software if prompted. Then perform a push installation to miprd agian using Clients => Add Clients => Select the UNIX Installation server. 


If remote uninstallation fails (see above), we need to uninstall all components using rpm command on the Linux server. After that the agent should be completely uninstalled and can be installed again.

rpm -qa OB2*
rpm -e OB2-DB2-A-06.11-1 rpm -e OB2-INTEG-A-06.11-1 rpm -e OB2-MA-A.06.11-1 rpm -e OB2-DA-A.06.11-1 rpm -e OB2-CC-A-06.11-1 rpm -e OB2-CORE-A.06.20-1
rpm -qa OB2*

Regards,
Sebastian Koehler

 

---
Please use the Like button below, if you find this post useful.
0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

while installing , will it ask for any license details.?

regards

Narendran

 

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

No, this is just an agent while licensing only happens on the Cell Manager.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

i tried adding the client but its promting for a username and password of the client system,

but i gave the username and password but it is prompting that the username and pasword is incorrect.

regards

Narendran

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

SSH key-based authentication is not configured correctly. Here is what you need to do.

  1. On bidevqly create or edit /opt/omni/.omnirc and make sure it contains OB2_SSH_ENABLED=1
  2. On bidevqly check as root the content of /root/.ssh folder for any id_dsa.pub or id_rsa.pub file; if the file does not exist run ssh-keygen -t rsa -b 2048 and save it without any passphrase
  3. On bidevqly run ssh-copy-id -i /root/.ssh/id_rsa.pub root@miprd and enter the password, then login using ssh root@miprd that should work without any prompts
  4. Return to Data Protector GUI and try the push installation again

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

no files found in the name of /opt/omni/.omnirc in the miprd server .

which server you mean as bidevqly ?

regards

Narendran

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

bidevqly should be your Linux installation server according to the screenshots.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Narenicf
New Member.

Re: [Critical] None of the Disk Agents completed successfully. Session has failed.

Jump to solution

i did the steps which you have suggested but still getting the same issue.

Now in doing this client installation in our quality server because of our testing purpose.

[root@ECCQLY ~]# ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
e7:d3:e0:fb:88:78:fc:f3:33:fc:a9:99:25:8d:5a:70 root@ECCQLY
[root@ECCQLY ~]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@ECCQLY
21
The authenticity of host 'eccqly (10.53.1.3)' can't be established.
RSA key fingerprint is ba:01:d9:e8:61:b0:3e:84:a6:7d:da:e0:8c:ee:53:e9.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'eccqly,10.53.1.3' (RSA) to the list of known hosts.
root@eccqly's password:
Now try logging into the machine, with "ssh 'root@ECCQLY'", and check in:

.ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

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.