Video Screencast Help

Bptestbpcd failed for a client using F5 load balancer

Created: 02 Oct 2013 | 5 comments

Hi All,

I am currently having connection challenges after installing a netbackup client that uses a F5 loadbalancer

Master Server runs Solaris 10, netbackup 7.5.0.6, updated the /etc/hosts with IP and hostname of client.

Client runs solaris 10, netbackup 7.5, updated /etc/hosts with IP and hostname of master server, uses F5 load balancer

 

In testing for connectivity,

from client  - ./bpclntcmd -pn returns the IP of the F5 load balancer instead of its hostname and IP address

from Master server  -  ./bpclntcmd -hn clientname returns the correct hostname and IP address of client

                                ./bptestbpcd -client clientname failes with error 46

All netbackup ports for communication 13724, 13786, 1556 opened for vnetd, bpcd and pbx.

 

Kindly assist as only this 2 clients are having isuues out of over 600 clients

 

Thanks.

Operating Systems:

Comments 5 CommentsJump to latest comment

Marianne's picture

Create bpcd log folder on the client, then run bptestbpcd again.

Check bpcd log to see which IP address the connection request is coming from and how the client is resolving this IP address to a hostname which is then compared with client's SERVER list.

NBU has no control over name resolution and must be resolved at OS level.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Peteror's picture

Thanks Marianne,

I created the bpcd and vnetd logs eailier with 777 permission and root ownership. Anytime i run the bptestbpcd from master server, no log is created. I only find this logs below created each day on the client.

root@client # cat log.100113
00:00:03.621 [13799] <2> setup_debug_log: switched debug log file for bpcd
00:00:03.631 [9345] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
00:00:03.633 [9346] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
00:16:03.811 [19762] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
00:32:03.996 [29889] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
00:47:04.174 [9882] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
01:03:04.368 [20197] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
01:19:04.558 [484] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
01:35:04.746 [11151] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
01:51:04.931 [21552] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
02:06:05.107 [1218] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
02:22:05.294 [11774] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
02:38:05.480 [22067] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
02:54:05.667 [2392] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
03:10:05.856 [13006] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
03:25:06.032 [22695] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
03:41:06.220 [3053] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
03:57:06.407 [13589] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
04:13:06.621 [23894] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
04:29:06.805 [4283] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
04:45:06.995 [14823] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
05:00:07.160 [24539] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
05:16:07.355 [5060] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
05:32:07.541 [15575] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
05:48:07.736 [25815] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
06:04:07.911 [6234] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
06:19:08.089 [16153] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
06:35:08.282 [26501] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
06:51:08.473 [6883] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
06:52:08.491 [13799] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=/usr/openv/var/host_cache/0bc/112aeabc+0,1,50,0,2,0+10.199.7.40.txt
07:07:08.664 [17483] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
07:23:08.854 [27751] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
07:38:09.035 [7547] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
07:54:09.228 [17963] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
08:10:09.424 [28262] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
08:26:09.614 [8864] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
08:42:09.807 [19205] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
08:58:09.996 [29398] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
09:13:10.176 [9362] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
09:29:10.354 [19735] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
09:45:10.535 [29866] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
10:01:10.725 [10520] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
10:17:10.919 [20845] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
10:32:11.088 [536] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
10:48:11.277 [11045] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
11:04:11.468 [21372] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
11:20:11.661 [1778] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
11:36:11.853 [12234] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
11:51:12.029 [21927] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
12:07:12.224 [2287] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
12:23:12.417 [12811] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
12:39:12.608 [23045] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
12:55:12.798 [3537] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
13:11:12.986 [14064] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
13:26:13.166 [23737] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
13:42:13.359 [4102] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
13:58:13.548 [14564] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
14:14:13.744 [24906] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
14:30:13.922 [5348] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
14:45:14.100 [15176] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
15:01:14.287 [25498] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
15:17:14.465 [5961] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
15:33:14.651 [16350] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
15:49:14.831 [26664] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
16:05:15.008 [7175] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
16:20:15.174 [17139] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
16:36:15.354 [27345] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
16:52:15.542 [7771] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
17:08:15.730 [18331] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
17:24:15.921 [28537] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
17:39:16.089 [8451] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
17:55:16.277 [18939] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
18:11:16.466 [29190] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
18:27:16.657 [9856] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
18:43:16.845 [20126] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
18:58:17.022 [29747] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
19:14:17.216 [10373] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
19:30:17.406 [20682] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
19:46:17.594 [925] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
20:02:17.781 [11532] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
20:18:17.970 [21793] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
20:33:18.150 [1426] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
20:49:18.340 [12003] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
21:05:18.529 [22263] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
21:21:18.728 [2622] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
21:37:18.918 [13126] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
21:52:19.096 [22720] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
22:08:19.288 [3161] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
22:24:19.488 [13662] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
22:40:19.670 [23997] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
22:56:19.858 [4397] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
23:11:20.037 [14316] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
23:27:20.227 [24671] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
23:43:20.404 [5180] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
23:59:20.580 [15687] <2> unix_daemonize: No close(3) for DOOR file mode 0x0000d124
00:00:20.603 [13799] <2> setup_debug_log: switching debug log file for bpcd
 

Giri_S's picture

U said every thing about hosts file...

what about bp.conf file ? can u ensure Master server name as 1st entry follwed by media servers there ?

Netbackup Admin (Unix)

Peteror's picture

In installing a client, the master server name specified is always listed as the first entry in bp.conf. I have also updated the bp.conf with the media servers.

In troubleshooting, i also specified REQUIRED_INTERFACE to use the client IP address

I worried because ./bpclntcmd -pn from client returns IP address of the F5

Marianne's picture

 ./bptestbpcd -client clientname failes with error 46 

Above error indicates that a connection is made, but that server permission is denied.

Anytime i run the bptestbpcd from master server, no log is created.

This contradicts the status 46 error as no logging means that no connection is made.

There may be a routing issue, meaning that the connection attempt is going 'somewhere else' and not to the intended client. 

Run bpbtestbpcd with -verbose -debug and monitor the network while connection is attempted.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links