Highlighted
Contributor.
Contributor.
3055 views

Unable to Add Linux Installation Server to Windows Cell Manager

I recently setup a linux based installation server and i'm having diificulties adding it to the Windows based Cell Manager.

Data Protector version: 10

The error message on the cell manager is

[12:1660] Import Installation Server failed.

Actions:

* Please check that the Data Protector services on the Cell Manager computer are running.
* Also check that Data Protector Inet service on the remote computer is running
(use: telnet <remote computer> 5565 to see if the service responds).
* Install that host as Data Protector Installation Server.

DP services are running.

i can telnet to the remote computer on port 5565

the host was installed as a DP Installation server.

 

I checked the linux installation server log file -> /var/opt/omni/log/debug.log and the error messages are:


2017-10-19 18:11:48.291 INET.10068.0 ["/lib/ipc/ipc.c $Rev: 58918 $ $Date:: 2017-06-14 07:45:17 ":4939] A.10.00 b306
[IpcIPIsLocal] empty_ip

2017-10-19 18:11:50.482 INET.10069.0 ["/lib/ipc/ipc.c $Rev: 58918 $ $Date:: 2017-06-14 07:45:17 ":3345] A.10.00 b306
[IpcGetHostInfoEx] empty_hostname

2017-10-19 18:11:50.482 INET.10069.0 ["/lib/ipc/ipc.c $Rev: 58918 $ $Date:: 2017-06-14 07:45:17 ":4939] A.10.00 b306
[IpcIPIsLocal] empty_ip

2017-10-19 18:11:50.549 INET.10070.0 ["/lib/ipc/ipc.c $Rev: 58918 $ $Date:: 2017-06-14 07:45:17 ":3345] A.10.00 b306
[IpcGetHostInfoEx] empty_hostname

2017-10-19 18:11:50.550 INET.10070.0 ["/lib/ipc/ipc.c $Rev: 58918 $ $Date:: 2017-06-14 07:45:17 ":4939] A.10.00 b306
[IpcIPIsLocal] empty_ip

 

DNS Name resolution is fine on the two servers.

Kindly assist

0 Likes
7 Replies
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Unable to Add Linux Installation Server to Windows Cell Manager

I guess you ran into the same situation like me before .. try the following:

 

There is an official workaround, cause is the "new" encrypted connection:

https://community.saas.hpe.com/t5/Data-Protector-Support-Customer/DP-Support-Tip-12-1603-Connection-to-CRS-failed-DP10-00/td-p/1613187

At GUI (Cell Console) system :
omnicc -secure_comm -configure_peer <hostname of Cell Manager system>

At Cell Manager system :
omnicc -secure_comm -configure_peer <hostname of Cell Console system>

  

BR
Tobias

Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Unable to Add Linux Installation Server to Windows Cell Manager

I'm having this same issue. I want to import a Linux IS (CentOS 7.x) running DP 10.02.

PS X:\> omnicc -import_is is_server.fqdn
- Please use the fingerprint to validate the certificate manually!
Certificate information:
- Hostname:is_server.fqdn
- Valid: from Feb 16 16:12:49 2018 GMT until Feb 14 16:12:49 2028 GMT
- Fingerprint: blahblah
Do you want to continue (y/n)?y
[12:1660] Import Installation Server failed.
[12:1660] Import Installation Server failed.PS X:\>

I added these to /etc/sysconfig/iptables

–A INPUT –p tcp –m state –state NEW –m tcp –dport 5555 –j ACCEPT
–A INPUT –p tcp –m state –state NEW –m tcp –dport 5565 –j ACCEPT

And these to /etc/services

omni 5555/tcp # DATA-PROTECTOR
omni 5565/tcp # DATA-PROTECTOR

Telnet to 5555 from the CM and IS and vise-versa works just fine.
Telnet to 5565 from CM to IS fails

What else needs to be done?

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Unable to Add Linux Installation Server to Windows Cell Manager

I removed

–A INPUT –p tcp –m state –state NEW –m tcp –dport 5555 –j ACCEPT

And then telnet from the CM to IS via 5565 worked (and 5555 fails). However, the import still fails with the same error.

0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Unable to Add Linux Installation Server to Windows Cell Manager

A new installation uses the new port 5565, and an old cell on port 5555 cannot communicate with the new port. So you need to change the port of the new installation in your services, to also use 5555.

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Unable to Add Linux Installation Server to Windows Cell Manager

I must have missed something while I was troubleshooting on my own. This solved it:

IS

  • # vi /etc/services
  • Verify 'omni 5555/tcp # DATA-PROTECTOR' exists. Change from 5565 to 5555, if needed.
  • # service xinetd restart
  • Verify telnet to CM via 5555 works
  • # ./opt/omni/bin/omnicc -secure_comm -configure_peer cell_mgr.fqdn
  • y to accept certificate

CM

  • Verify telnet to IS via 5555 works
  • omnicc -secure_comm -configure_peer is_server..fqdn
  • Import IS via GUI or command line
Highlighted
Frequent Visitor..
Frequent Visitor..

Re: Unable to Add Linux Installation Server to Windows Cell Manager

Hello

I have checked all points but when I wanto to execute

omnicc -secure_comm -configure_peer

This message appear

bash: omnicc: command not found

Can anyone help me?

Thanks in advance

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Unable to Add Linux Installation Server to Windows Cell Manager

Hello @jbasauri

In Linux, you have to go to the path to run the command. 

So, something like this: 

# cd /opt/omni/bin
# ./omnicc ........

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
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.