10-27-2018 04:40 AM - last edited on 10-29-2018 02:29 AM by Marianne
After running this command (bpcoverage -c bactest), I am getting 58 status code.
Here can able to telnet from master to client (13782 and 13724) but not able to telnet from client to master.
Are we need open the ports manually on client side ?
***************************
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpcoverage -c bactest
CLIENT: backrest
Exit status 58: can't connect to client
CLIENT: bactest
Exit status 58: can't connect to client
********************
Solved! Go to Solution.
10-29-2018 01:57 AM
Hello,
The application registers the port on OS for communication. Open port it mean you have to change the OS firewall or Network firewall rule to send and receive the request on those ports.
If you are using Network firewall then ask respected person or team to open the port in the firewall.
Regards,
10-29-2018 03:15 AM - edited 10-29-2018 03:17 AM
Port 1556 neeed to be open in both directions, meaning both side need to be able to initiate sessions.
Port 13782 & 13724 will still work, but are not the default port any more, unless you are using a very old version of Netbackup.
bptestbpcd is a good utility for testing connectivity from master and media servers
How to test client connections using the bptestbpcd command:
https://www.veritas.com/support/en_US/article.100017088.html
10-30-2018 08:18 AM
PLEASE add 1556 as well.
Actually, you can drop the other two and only use 1556.
As per @Nicolai's post -
Port 13782 & 13724 will still work, but are not the default ports any more.
As from 7.0.1, the default is 1556.
When that fails, 13742 will be tried.
When that fails, 13782 will be tried.
10-29-2018 01:57 AM
Hello,
The application registers the port on OS for communication. Open port it mean you have to change the OS firewall or Network firewall rule to send and receive the request on those ports.
If you are using Network firewall then ask respected person or team to open the port in the firewall.
Regards,
10-29-2018 03:15 AM - edited 10-29-2018 03:17 AM
Port 1556 neeed to be open in both directions, meaning both side need to be able to initiate sessions.
Port 13782 & 13724 will still work, but are not the default port any more, unless you are using a very old version of Netbackup.
bptestbpcd is a good utility for testing connectivity from master and media servers
How to test client connections using the bptestbpcd command:
https://www.veritas.com/support/en_US/article.100017088.html
10-30-2018 07:13 AM
while the failure occured :
+++++++++++++++++++
[root@bactest bin]# telnet <Master server> 13782
Trying xxxx...
Connected to <Master server>.
[root@bactest bin]# telnet <Master server> 13724
Trying xxxx...
Connected to <Master server>.
C:\Program Files\Veritas\NetBackup\bin\admincmd>telnet bactest 13782
Connecting To bactest...Could not open connection to the host, on port 13782:
Connect failed
C:\Program Files\Veritas\NetBackup\bin\admincmd>telnet bactest 13724
Connecting To bactest...Could not open connection to the host, on port 13724:
Connect failed
[root@bactest bin]# ./bpps -x
NB Processes
------------
root 6642 1 0 Oct26 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -standalone
root 6647 1 0 Oct26 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
++++++++++++++
Requested the Unix platform team to open the telnetport 13782 and 13724 on the client.
After opened the port, the issue is fixed.
I can telnet from master to client and vise versa.
10-30-2018 08:18 AM
PLEASE add 1556 as well.
Actually, you can drop the other two and only use 1556.
As per @Nicolai's post -
Port 13782 & 13724 will still work, but are not the default ports any more.
As from 7.0.1, the default is 1556.
When that fails, 13742 will be tried.
When that fails, 13782 will be tried.
10-31-2018 11:11 PM