cancel
Showing results for 
Search instead for 
Did you mean: 

Client Connectivity Issue with new Master.

MABaig
Level 3

Hi,

Got a query on a issue I am facing

I am migrating clients from old master to new master, and there are several connectivity issues I am fcaing with new master like Ping test is failing and BPCD and VNETD services are not responding or not connected, can any one tell me how to trouble shoot these problems.

Thanks,

Abaig. 

1 ACCEPTED SOLUTION

Accepted Solutions

Faysal
Level 3
Partner Accredited

Note the following communication step to find network issue.


1. Verify the master and media server ip address are resolve hostnames.

bpclntcmd -ip master_server_ipaddress
bpclntcmd -ip media_server_ipaddress

2. verify the master amd media server hostnames are resolve address.

bpclntcmd -hn master_server_name
bpclntcmd -hn media_server_name

3. verify what name the master server sees as each machine's peer name.

bpclntcmd -pn

4. Test the bpcd connection between each machine and the master server.

bptestbpcd -host master_server

5. Run the command for connectivity.

bptestbpcd -debug

bptestbpcd -client <MediaServer_name> -debug
bptestbpcd -client <Master_name> -debug -verbose



# netstat -an | grep 13724 ( if you then on the client server run the command)

Then to test the bpcd port locally on the client server from the command prompt, run this telnet test using the loopback interface-

telnet localhost 13782 or

telnet 127.0.0.1 13782

verify these port

bash-3.00# netstat -a | grep 13724
      *.13724              *.*                0      0 49152      0 LISTEN
bash-3.00# netstat -a | grep 13782
      *.13782              *.*                0      0 49152      0 LISTEN

bash-3.00# telnet localhost 1556 (or remote server)
 

and also please check your system firwall

View solution in original post

3 REPLIES 3

Andy_Welburn
Level 6

If 'ping' is actually allowed in your environment (i.e. it 'normally' works) then you're looking at hostname resolution or client connectivity issues - you need to resolve that first before you can get NetBackup to work.

hosts files, DNS entries are a good place to start

revarooo
Level 6
Employee

I fully agree with Andy, forget NetBackup and look at the networking first and ensure it works (that servers/clients can communicate to each other), only when that is working do you then check NetBackup.

Faysal
Level 3
Partner Accredited

Note the following communication step to find network issue.


1. Verify the master and media server ip address are resolve hostnames.

bpclntcmd -ip master_server_ipaddress
bpclntcmd -ip media_server_ipaddress

2. verify the master amd media server hostnames are resolve address.

bpclntcmd -hn master_server_name
bpclntcmd -hn media_server_name

3. verify what name the master server sees as each machine's peer name.

bpclntcmd -pn

4. Test the bpcd connection between each machine and the master server.

bptestbpcd -host master_server

5. Run the command for connectivity.

bptestbpcd -debug

bptestbpcd -client <MediaServer_name> -debug
bptestbpcd -client <Master_name> -debug -verbose



# netstat -an | grep 13724 ( if you then on the client server run the command)

Then to test the bpcd port locally on the client server from the command prompt, run this telnet test using the loopback interface-

telnet localhost 13782 or

telnet 127.0.0.1 13782

verify these port

bash-3.00# netstat -a | grep 13724
      *.13724              *.*                0      0 49152      0 LISTEN
bash-3.00# netstat -a | grep 13782
      *.13782              *.*                0      0 49152      0 LISTEN

bash-3.00# telnet localhost 1556 (or remote server)
 

and also please check your system firwall