Video Screencast Help

client failing with status code 58 using 1of4 media servers

Created: 20 May 2013 • Updated: 01 Aug 2013 | 5 comments
This issue has been solved. See solution.

Hi all,

 

We have a master server (bk100) and four media servers (bk110-113) all are Windows 2008 and have NetBackup 7.1.0.3. One client only fails on bk111 and resulting to status code 58. 

I can successfully run bptestbpcd on the master server and on the media servers except on bk111 which outputs:

 

PS D:\Program Files\Veritas\NetBackup\bin\admincmd>  .\bptestbpcd.exe -client mhprpsawb801.domain.com
<16>bptestbpcd main: Function ConnectToBPCD(mhprpsawb801.domain.com) failed: 25
cannot connect on socket
 
bpclntcmd on bk111: 
 
PS D:\Program Files\Veritas\NetBackup\bin> .\bpclntcmd.exe -hn mhprpsawb801
host mhprpsawb801: mhprpsawb801.domain.com at 10.226.18.135
aliases:     mhprpsawb801.domain.com     mhprpsawb801     10.226.18.135

client and master/media servers sits on the same LAN (10.226.18.0). client is a SunOS 5.8 box with NBU 6.0

Operating Systems:

Comments 5 CommentsJump to latest comment

Marianne's picture

Please create bpcd log folder on the client in /usr/openv/netbackup/logs.

Run bptestbpcd again and check bpcd log on the client.
bpcd log will show us the incoming IP address from media server and how client is attempting to resolve IP to hostname.
No record of incoming IP address means possible firewall.

Status 58 is normally caused by one of the following:

Firewall between media server and client - vnetd (port 13724) needs to be open in both directions between server and client.

Failed reverse lookup on the client - check /etc/hosts on client for missing or incorrect entry for this media server.  Verify that resolved hostname has matching SERVER entry in client's bp.conf.
Use 'bpclntcmd -ip <media-server-ip>' on the client to verify reverse lookup.

Hope this helps.

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

SOLUTION
Dyneshia's picture

In addtion to 13724, you alos need 13782 (bpcd)

 

From master/media to clients

13724 tcp/udp
13782 tcp/udp

From clients to master/media
13724 tcp/udp
13720 tcp/udp
13721 tcp/udp

FYI
13724 = vnetd
13782 = bpcd
13720 = bprd
13721 = bpdbm

Marianne's picture

NBU 6.x use vnetd (13724) for server -> client connection.

See 

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

huanglao2002's picture

you can check  /etc/hosts or DNS on the media server and client side.

LucSkywalker1957's picture

Check your C:|Windows\System32\drivers\etc\hosts and make sure you can connect on both the forward name and reverse IP.