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
Absent Member.. dheeru_shetty Absent Member..
Absent Member..
1781 views

Facing problem while importing Linux IS to windows CM

Jump to solution
Facing problem while importing Linux IS to windows CM.
 

 

Hi all...

I have installed the HP DP 9.04 locally on a linux client (Centos 6.5).
Installation has completed successfully but was unable to import the client to CM.
Client is reachable from Cell Manager but telnet doesn't work on the port 5555.
From Client end, I am able to telnet the Cell manager on port 5555.

There is no firewall setup on the machine and both server are in the same subnet.

Work around done till now:-

1. I have added the host entries in Cell Manager and Linux Machine(Path : /etc/hosts).
2. Restarted xinetd daemon and checked.
3. Added a file cell_server with Cell Manager Name in it inside the directory /etc/opt/omni/client & /etc/opt/omni/IS.
4. Activated the omnirc parameters “OB2PORTRANGE=62000-63000 OB2INETTIMEOUT=10” to keep the connection active.

 

Telnet Result from Linux Client to Cell Manager :-

[root@ client]# telnet uscarbku**.***.***. 5555
Trying 10.3.10.41...
Connected to uscarbku**.***.***.
Escape character is '^]'.
HP Data Protector A.09.00: INET, internal build 104, built on Thursday, July 30, 2015, 2:28 PM
Connection closed by foreign host.


Port 5555 is listening to the port from Linux Installation Server :-

[root@client ~]# netstat -an |grep 5555
tcp 0 0 :::5555 :::* LISTEN

[root@client etc]# cat services | grep -i 5555
omni 5555/tcp # DATA-PROTECTOR
#omni 5555/udp # DATA-PROTECTOR

 

Telnet & Import Host Results from the Cell Manager :-
C:\Windows\system32>telnet 10.3.10.** 5555
Connecting To 10.3.10.**...Could not open connection to the host, on port 5555:
Connect failed

Importing the host manually is failing :-

[12:1625] Import host failed.
System error: [10060] Connection timed out

 

please suggest some inputs.

 

Thanks.

Dheeraj Shetty

0 Likes
1 Solution

Accepted Solutions
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

The firewall is up and running. Try iptables -F and service iptables stop. chkconfig iptables off will make it permanent.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
10 Replies
Eblyn Solis Acclaimed Contributor.
Acclaimed Contributor.

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi,

If you do not have firewall, why do you use the OB2PORTRANGE=62000-63000 OB2INETTIMEOUT=10 ? Take it off and try again.

Regards.

 

 

Please assign a kudo to this post, if you find it useful.
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Please share iptables -L, chkconfig --list | grep omni and service xinetd status from the CentOS box.

Regards,
Sebastian Koehler

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

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi Eblyn Solis ,

The ports were opened initially as a wor around.

Anyways the import of client gave me the same error even after removing the parameters.

I really dont know where the miss is, have update the host entries, added the cell manager info manually in cell_server file.

Error while importing from GUI :-

[12:1625] Import host failed.

C:\Windows\system32>omnicc -import_is uscaradgw01
[12:1660] Import Installation Server failed.
System error: [10060] Connection timed out

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

OB2PORTRANGE is not used for client imports. You need to reach port 5555 (default Data Protector INET port) on the Installation Server from Cell Manager to be successful.

Regards,
Sebastian Koehler

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

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi Sebastian,

Below are the outputs from the Centos Machine.

[root@USCARADGW01 ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s sh
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:h ttps
REJECT all -- anywhere anywhere reject-with icmp-ho st-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,EST ABLISHED
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with icmp-ho st-prohibited
ACCEPT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain DOCKER (1 references)
target prot opt source destination
[root@USCARADGW01 ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source destination
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
ACCEPT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain DOCKER (1 references)
target prot opt source destination
[root@USCARADGW01 ~]# chkconfig --list | grep omni
omni: on
[root@USCARADGW01 ~]# service xinetd status
xinetd (pid 2400) is running...
[root@USCARADGW01 ~]#

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

The firewall is up and running. Try iptables -F and service iptables stop. chkconfig iptables off will make it permanent.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Eblyn Solis Acclaimed Contributor.
Acclaimed Contributor.

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

hi,

just to be sure check this, and post.

 

from Linux

 

ping <CM_longname>

ping <CM_shortname>

nslookup <CM_longname>

nslookup <CM_shortname>

nslookup <CM_ip>

telnet <CM > 5555

 

Cell Manager Windows

 

 

ping <client_longname>

ping <client_shortname>

ping -a<client_ip>

nslookup <client_longname>

nslookup <client_shortname>

nslookup <client_ip>

telnet <client_name> 5555

 

Note: allow_hosts or deny_hosts files in linux should be empty, also cell_server.

/etc/opt/omni/client.

Regards.

 

 

 

 

Please assign a kudo to this post, if you find it useful.
0 Likes
Absent Member.. dheeru_shetty Absent Member..
Absent Member..

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi Sebastian,

Thanks a lot. That actually did work for me. :)
I just took a backup of the firewall config and stopped the iptable services. Was afraid if flushing would delete the existing settings.

Was able to telnet the Client from the Cell Manager without any fuss and also imported the client and took a test backup successfully.

The moment i started the service. Backup failed with the below error. So there was a firewall blocking the connection.

 

[Critical] From: BSM@uscarbku01.us.oup.com "TEST_VM_LINUX" Time: 7/14/2016 9:24:10 AM
IPC Cannot Connect
System error: [10060] Connection timed out

[Major] From: BSM@uscarbku01.us.oup.com "TEST_VM_LINUX" Time: 7/14/2016 9:25:17 AM
[61:4006] Could not connect to inet in order to start VBDA@uscaradgw01 "/ /".

[Warning] From: BSM@uscarbku01.us.oup.com "TEST_VM_LINUX" Time: 7/14/2016 9:25:17 AM
The backup of this object will be retried at end of session.

[Critical] From: BSM@uscarbku01.us.oup.com "TEST_VM_LINUX" Time: 7/14/2016 9:25:39 AM
IPC Cannot Connect
System error: [10060] Connection timed out

[Major] From: BSM@uscarbku01.us.oup.com "TEST_VM_LINUX" Time: 7/14/2016 9:26:08 AM
[61:4006] Could not connect to inet in order to start VBDA@uscaradgw01 "/ /".

 

Regards,

Dheeraj

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi Dheeraj,

if you need the firewall you must add the required rules for INET and the values used in OB2PORTRANGE. OB2PORTRANGE must be specified on omnirc on Cell Manager and client system. 1000 ports are way enough even for large environments.

If this works, please mark this topic as resolved and don't forget the kudos. :)

Regards,
Sebastian Koehler

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

Re: Facing problem while importing Linux IS to windows CM

Jump to solution

Hi Sebastian/Eblyn,

Kudos to you guys. Thanks for your kind responce. The issue is resolved now.

I was able to telnet the localhost on 5555 so i suspected there is something blocking at the client firewall. Upon checking the firewall settings, i discovered there was a misconfiguration in the local machine firewall rule which had to be modified.

There was rule that was blocking all the incoming connection and not letting any server to communicate with the client.

I had to remove the rule which was REJECTING ALL THE INCOMING CONNECTION, and add a new rule to specifically allow (ACCEPT) packets from the backup server which eventually made the telnet to work from cell manager to client.

Was able to successfully import the centos machine in client list and installation server list.

Even backups are running smoothly. :)

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.