HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Issue with veritas netbackup connectivity exit cod...
Operating System - HP-UX
1834657
Members
2853
Online
110069
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2006 06:20 AM
12-05-2006 06:20 AM
Issue with veritas netbackup connectivity exit code :54
I have netbackup 5.1 running on HP UX 11i server.
The backup is failing with the exit status 54 which is about the connectivity between master and client.
My question is i have two default gateways configured one for primary lan0 and other for backup lan1, could this be the issue?
bpcd port is listening
#-> netstat -a|grep bpcd
tcp 0 0 *.bpcd *.* LISTEN
#telnet 13782 is failing
KIndly suggest again could two default gateway be the issue.
Please suggest
The backup is failing with the exit status 54 which is about the connectivity between master and client.
My question is i have two default gateways configured one for primary lan0 and other for backup lan1, could this be the issue?
bpcd port is listening
#-> netstat -a|grep bpcd
tcp 0 0 *.bpcd *.* LISTEN
#telnet
KIndly suggest again could two default gateway be the issue.
Please suggest
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2006 06:59 AM
12-05-2006 06:59 AM
Re: Issue with veritas netbackup connectivity exit code :54
Hi,
Having two default gateways could be causing your problem. Study your routing table ('netstat -nr') to determine which interface handles traffic for which destination IP. You may need to add a static route via the 'route' command.
PCS
Having two default gateways could be causing your problem. Study your routing table ('netstat -nr') to determine which interface handles traffic for which destination IP. You may need to add a static route via the 'route' command.
PCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2006 10:29 AM
12-05-2006 10:29 AM
Re: Issue with veritas netbackup connectivity exit code :54
I am looking at exit code 54 (timed out connecting to client).
Veritas relies heavily on good network communication. Make sure that you can resolve short and long names. It would be a good idea to put an entry in the /etc/hosts file on both the client and server if you already haven't done so.
In your /etc/inetd.conf file make sure that you have the following entry;
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
Veritas relies heavily on good network communication. Make sure that you can resolve short and long names. It would be a good idea to put an entry in the /etc/hosts file on both the client and server if you already haven't done so.
In your /etc/inetd.conf file make sure that you have the following entry;
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP