What is the use of BPCD port on client?
is it bidirectional?
it's a client deamon, which is always with listening status and used to listen on the requests from Master or Media, lets NBU start some programs.
Before NBU 6.5, server -> client comms was made to bpcd directly. The client then needed to connect back on a range of ports. (512 -1023).
Since 6.0, all comms between server and client are directed via vnetd, needing only vnetd open in both directions. So, media server bpbrm -> client bpcd connection is directed via vnetd. Client then connects back using vnetd port as well.
Since 7.0.1, connection attempts will prefer PBX. Failing that, will fail back to vnetd.
Please see the NBU functional overview in Appendix A of NBU Troubleshooting Guide http://www.symantec.com/docs/DOC3683
as well as NetBackup 6.x and 7.x firewall port requirements http://www.symantec.com/docs/TECH136090
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
so vnetd needs t be pen in both direction?dats it?
So in 7.1,only PBX needs to be open bidirectionally anr rest in unidirectionaly?
For now vnetd will be enough for server/client comms.
Please add PBX (1556) to firewall ports (both directions) as vnetd will eventually be phased out.
Extract from TECH136090:
The vnetd process is still listening on TCP port 13724. But most connections that previously used the vnetd port will now prefer to use the PBX port 1556. ....
Not sure what you mean by 'rest'?
These are the only 2 ports needed for comms in 7.x - both bi-directional:
Server <- vnetd -> Client
As from 7.0.1:
Server <- PBX / vnetd -> Client
Server <- PBX -> Server
What this means?
Rest means other daemons
The arrow means the direction in which the port needs to be open.
So, vnetd need to be open to server and to client (bi-directional).
Same for PBX.
so in short,
PBX AND VNETD needs to be open bidirectionally in 7.x?
AND vnetd bidirectionally in 6.x?
Detailed explanation in TECH136090.