Guru's,
Very frustrating. More frustrating that the tools are limited to
diagnoses. The below logs excerpts were sent back from NB support
indicating where the failure is occurring, during
et_type_of_client_port: db_getCLIENT().
I agree with the diagnosis, however, nslookup, blclntcmd, host file
entries all check out. Any suggestions would be appreciated
Master/Media Server: W2/SP2
Client: Target NW
>From BPBRD
(The request dameon sets up a connection from host,
xxx.xxx.xxx.xxx, on reserved port 698.)
15:45:49 [2744.1888] <4> bprd: Looking for request-timeout file
D:\VERITAS\NetBackup\BPRD_REQUEST_TIMEOUT
15:45:49 [2744.1888] <4> bprd: File
D:\VERITAS\NetBackup\BPRD_REQUEST_TIMEOUT not found, using the default
request-timeout value of 300 seconds
15:45:49 [2744.1888] <4> connected_peer: Connection from
host, xxx.xxx.xxx.xxx, on reserved port 698
(NetBackup does a security check to see if the host is a valid server
and fails completely.)
15:45:49 [2744.1888] <2> nb_is_valid_server: checking if
netback.ctp.com is
a valid server
15:45:49 [2744.1888] <4> get_type_of_client_port: db_getCLIENT()
failed: no
entity was found (227)
15:45:49 [2744.1888] <4> hosts_equal: gethostbyname failed for NONE: No
such
host is known.
15:45:49 [2744.1888] <2> getsockconnected: host=netback service=bpdbm
address=149.44.15.53 protocol=tcp non-reserved port=13721
15:45:49 [2744.1888] <2> db_getCLIENT_by_hostname: db_CLIENTreceive:
no
entity was found 227
Thanks,
Scott J.
|