#1
31st May 2016, 08:14 AM
| |||
| |||
Bpclntcmd Pn Null
Hi I am interested in having the solution for the explanation of bpclntcmd options and recommended troubleshooting when the commands return errors?
|
Similar Threads | ||||
Thread | ||||
Bank of India Null Bazar Branch IFSC Code | ||||
Pacific Academy of Higher Education & Research (PAHER) Null |
#2
31st May 2016, 08:14 AM
| |||
| |||
Re: Bpclntcmd Pn Null
The bpclntcmd order performs name determination utilizing the same working framework APIs as the NetBackup programming. The - pn, - self, - hn, and - ip choices are valuable in investigating system network issues connected with name determination. Beginning with NetBackup 7.0, the OS gethostbyname and gethostbyaddr API calls are no more utilized for forward and turn around determination, separately. Rather getaddrinfo is utilized in light of the fact that it is IPv4 and IPv6 agreeable. Likewise take note of that, beginning with NetBackup 7.0.1, a host store is utilized which will hold the getaddrinfo return data for 60 minutes. On the off chance that rolling out improvements to DNS or other name determination administrations, make certain the reasonable the host store to dispose of the stale data. Tenacious NetBackup 7.1 procedures will distinguish the host store reset and pickup the progressions inside 10 seconds. These are some suggested investigating steps when mistakes are returned by the charge. UNIX/Linux:/usr/openv/netbackup/container/bpclntcmd Windows: <install>\Veritas\NetBackup\bin\bpclntcmd bpclntcmd - pn At the point when the - pn choice is keep running on a NetBackup host, it starts a request to the NetBackup expert server, and the expert server returns data about the asking for customer to the asking for host. The data returned is, in actuality, how the expert server "recognizes" the asking for host. The customer contacts the main server recorded in its servers list, found in the bp.conf document on UNIX/Linux customers (the SERVER= lines) and in the Backup, Archive, and Restore GUI, under File - Specify NetBackup Machines and Policy Type on a Windows customer. Bpclntcmd recognizes the server answering to the solicitation (the "expecting reaction from" line), and afterward it shows the data came back from that server. The accompanying is a case of the yield of the bpclntcmd - pn charge: > bpclntcmd - pn expecting reaction from server master_server_01 client_01.domain.com client_01 192.168.0.30 3815 In the above illustration: - The expert server is "master_server_01" - The association name (peername) is "client_01.domain.com" - The designed customer name is "client_01" - The source IP from which the association began is 192.168.0.30 - The source port used to associate is 3815. The expert server determined 192.168.0.30 to "client_01.domain.com". The FQDN was not designed as a customer in any strategy, but rather the shortname "client_01" was available. On the off chance that the yield indicated *NULL* for the designed customer name (as demonstrated as follows), the customer is not arranged in an approach and does not appear in the picture database. > bpclntcmd - pn expecting reaction from server master_server_01 client_01.domain.com *NULL* 192.168.0.30 3815 Audit the arrangement design on the expert server, and check whether the peername is recorded effectively in a strategy. |