Forum Discussion

bharatchoudhary's avatar
9 years ago

bptestbpcd cmd Connectivity from mediaserver to client Failed

Hi,

I am working on windows environemt (master, meida and client)

I am getting connectivity error for bptest cmd from mediaserver to cleint and the same bptest runs fine from another media server.

Host enteries all are fine.windows firewall is also disabled.

Mater ,media server and client is on same version : 7.6.1.2 

 

Kindly assist me how to further check this issue.

 

 

  • You are pinging xyz.m.com which is different from the client you run the bptestbpcd for (that is xyz).

     

    Ping to xyz.m.com resolves to 10.11.1.214 and bptestbpcd to xyz resolves to 192.168.225.22

     

            status: FAILED, (42) CONNECT_REFUSED; system: (10061) No connection coul
    d be made because the target machine actively refused it. ; FROM 0.0.0.0 TO xyz
    192.168.225.22 bpcd VIA pbx

     

    How about double or triple checking hostname resolution from both sides?

     

  • What did you see when you do bptestbpcd from the mediaserver to client?

    Please paste the output here, the error code may be helpful

    Using "-verbose" can give us more info as well, e.g. 

    bptestbpcd -client <hostname> -debug -verbose

     

  • Did you confirm that Server name was added on this client for this media server? Please confirm forward and reverse name lookup between media server and client using bpclntcmd command with -hn and -ip options. Test from server and client. Create bpcd log folder on the client and then run bptestbpcd command again with -debug -verbose. Please post output of all commands as well as client's bpcd log.
  • Hi, 

    I have attached the output of cmd bptestbpcd -client <hostname> -debug -verbose.

    master server,media server names were added to client host.

    nslokup is also working fine from media server 

    C:\Program Files\Veritas\NetBackup\bin\admincmd>ping -a xyz.m.com

    Pinging xyz.m.com [10.11.1.214] with 32 bytes of data:
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127

    Ping statistics for 10.11.1.214:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Program Files\Veritas\NetBackup\bin\admincmd>ping -a 10.11.1.214

    Pinging xyz.m.com [10.11.1.214] with 32 bytes of data:
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127
    Reply from 10.11.1.214: bytes=32 time<1ms TTL=127

    Ping statistics for 10.11.1.214:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

     

  • In your client, can you make sure this media server is added in the SERVER entry?  You can check this from the client host properties, restart Netbackup services on the client once you add it and try again.

  • You are pinging xyz.m.com which is different from the client you run the bptestbpcd for (that is xyz).

     

    Ping to xyz.m.com resolves to 10.11.1.214 and bptestbpcd to xyz resolves to 192.168.225.22

     

            status: FAILED, (42) CONNECT_REFUSED; system: (10061) No connection coul
    d be made because the target machine actively refused it. ; FROM 0.0.0.0 TO xyz
    192.168.225.22 bpcd VIA pbx

     

    How about double or triple checking hostname resolution from both sides?

     

  • Few things to check

    Is Telnet on port 1556 , 13782 working ?

    Is NBAC enabled on this media server ? Check USE_VxSS setting ..