bptestbpcd successful with name but not ip in NBU 8.1

Hi Everyone,

 Has anything changed from NBU 8.1 with bptestbpcd, Actually it is getting successful with hostname resolving its ip from hostname, However when i try it with ip it fails with an error status 7648

/usr/openv/netbackup/bin/admincmd/bptestbpcd -client tslussdapp1
1 1 1
127.0.0.1:60316 -> 127.0.0.1:37858 PROXY 172.25.193.149:45307 -> 172.25.218.56:1556
127.0.0.1:37303 -> 127.0.0.1:42317 PROXY 172.25.193.149:52006 -> 172.25.218.56:1556
127.0.0.1:42994 -> 127.0.0.1:49971 PROXY 172.25.193.149:47221 -> 172.25.218.56:1556

/usr/openv/netbackup/bin/admincmd/bptestbpcd -client 172.25.218.56
<16>bptestbpcd main: Function ConnectToBPCD(172.25.218.56) failed: 7648
<16>bptestbpcd main: Connection cannot be established because the host validation failed
Connection cannot be established because the host validation failed

Tags (2)
4 Replies

Re: bptestbpcd successful with name but not ip in NBU 8.1

Hello,

The NetBackup use the forward and reverse lookup to handshake.

Kindly share below-mentioned command output for more information.

Master:

nslookup 172.25.218.56

bpclntcmd -ip 172.25.218.56

bptestbpcd -client 172.25.218.56 -verbose -debug

Client:

bpclntcmd -self

nslookup  tslussdapp1

nslookup  172.25.218.56

netstat -an |grep 13782

Regards,

Re: bptestbpcd successful with name but not ip in NBU 8.1

All to do with NBU 8.1 host certificates .... 

If you google the error, you will find a number of forum posts and TNs. 

Highlighted

Re: bptestbpcd successful with name but not ip in NBU 8.1

From the client, what does the following return

nbcertcmd -getCACertificate -server <master>

If that returns a certificate try the following...

nbcertcmd -getCertificate -server <master> -token

It will ask for a token, paste the token you generated from the admin console here

Re: bptestbpcd successful with name but not ip in NBU 8.1

Issue isn't the backup, as backup are getting successful, it's one of script which isn't giving me ip as it relies on bptestbpcd output. Is it possible to push the certificate from master to all servers to resolve this certificate issue?