Have you checked for name resolution, connectivity issues?

e.g. from master (can also be carried out from client to master)

bpclntcmd -pn

bpclntcmd -ip client_ip_add

bpclntcmd -hn client_hostname

nslookup client_ip    (do this twice - should give same result)

nslookup client_hostname (do this twice - should give same result)

Hi Sherin

Apart from running bpclntcmc command  also run bpclient -client <client_name> -L(in master server) and see if ip that is changed is reflecting in current ip address

Hi Sherin,

As you mentioned that on changing the IP the backups are failing with error 54, I wouldn't suspect that something is wrong with the process or ports rightaway

1. Can you tell me what OS is your master server running?

2. Can you do a ping <aix client name> and tell me if the hostname is trying to ping the new IP address or old Ip address?

Once we confirm it is trying to ping the new IP address.

1. can you check if the process bpcd is listening on the client --> netstat -a | grep bpcd

2. can you try and telnet on port bpcd from the master ---> to the aix client --> telnet <aix client> bpcd

Let me know the output of the above tests, we'll take it from there.

Hi Manoj !

Thnx for your kind attention...

My master server is running on AIX 5.3 and Client is also running on the same.

 Yes, I’m able to ping from master to client and wise versa. But cant make a telnet connection in between them.

 Our master server is running on Class C and affected clients are running on Class D. But client IP’s are routed through a firewall…

While running  netstat –a|grep bpcd  from client the following out put occurs

Tcp4                0                      0          *.bpcd             *.*                   LISTEN

I tried to run  telnet <aix client> bpcd with both client name and IP

While trying with hostname I’m getting the following error

Bpcd: bad port

I’m unable to telnet with host IP. 

Hi Amit !

i tried this command in master server

bpclient -client <client name> -L

but it didnt deliver any result....

============================================

[veritas:root] / # bpclient -client app -L
ksh: bpclient:  not found.

============================================

Hi Andy !

 

I tried all the steps you have described here

 

these are the outputs. Still now I couldn't make a conclusion...



=====================================================

[veritas:root] / # bpclntcmd -pn
expecting response from server veritas
veritas veritas 192.168.20.211 47380

=====================================================

[veritas:root] / # bpclntcmd -hn app
host app: app at 202.154.175.27 (0xca9aaf1b)
checkhname: aliases:

=====================================================

[veritas:root] / # nslookup 202.154.175.27
Server:

***  can't find 202.154.175.27:No response from server

=====================================================

[veritas:root] / # nslookup app
Server:

***  can't find app:No response from server
[veritas:root] / #

=====================================================

[veritas:root] / # bpclient -client app -L
ksh: bpclient:  not found.

=====================================================

please give me a suggestion...

 

 

Regards

Shirin R

Sherin

The bpclntcmd commands were just to check the connectivity & resolution between  the master & client.

Output from it should just confirm that you have the correct IP addresses & hostnames in your NetBackup environment. (You missed one tho' bpclntcmd -ip <ip address> !!)

Don't worry too much about the nslookup - no DNS entries?

I'd be more concerned about the telnet <CLIENT> bpcd result. You should get something along the lines of:

telnet <CLINET> bpcd

Trying <CLIENT IP ADD>...
Connected to <CLIENT>.
Escape character is '^]'.

Connection to <CLIENT> closed by foreign host.

Unfortunately 'I know nothing' about AIX to help you there.

Sherin wrote:

I tried to run  telnet <aix client> bpcd with both client name and IP

While trying with hostname I’m getting the following error

Bpcd: bad port

 

I’m unable to telnet with host IP. 

I would imagine that there is some name/IP mis-match somewhere - surely you should get the same response when you use either the client name or the IP address?

Hi Sherin,

You need to issue blclient command from the path

/usr/openv/netbackup/bin/admincmd/bpclient

If it is saying bpcd bad port, check in /etc/services file if bpcd is set to listen from 13782 port

bpcd    13782/tcp       bpcd

also check following command from master server

/usr/openv/netbackup/bin/admincmd/bpcoverage -c <client name>

Hi Sherin,

Couldn't reply any earlier than this.

Seems to me that /etc/services isn't having bpcd settings in there.

Can you try this?

telnet <aix client> 13782

and

telnet <aix client> 13724

Paste me the exact outputs please

Dear Manoj !

I run the command  telnet app 13782  and got the following output (forget to mention, my client name is app)

[veritas:root] / # telnet app 13782
Trying...
telnet: connect: A remote host did not respond within the timeout period.
[veritas:root] / # pwd
/
[veritas:root] / #

and the out put of telnet app 13724  is

[veritas:root] / # telnet app 13724
Trying...
telnet: connect: A remote host did not respond within the timeout period.
[veritas:root] / #

Regards

Shirin R