- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Any way to avoid a "TCP RST"?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
05-02-2012 01:07 PM
05-02-2012 01:07 PM
I have both an Alpha and a VAX cluster with monitoring software that pulls performance data from various Alpha and VAX servers every morning. The servers are running OpenVMS 6.2 or 7.1 with UCX 4.2 - ECO 5. Most of the servers I am pulling the data from are behind firewalls so I use RCP to pull the files. The monitoring servers successfully pull the data from all but TWO of the Alpha and VAX servers. When trying to pull data from these two servers I get the message
"%RCP-E-INVRESP, invalid response from remote system".
I can successully send a file from the monitoring clusters to ALL servers using RCP and if I sign onto either of the two Alpha or VAX servers that I have the problem I can successfully send and pull files to the monitoring clusters. So it's only when I'm signed onto one of the monitoring cluster nodes and try to pull a file from these two servers that I have have this issue. According to the customer's vault and network support team they are seeing "TCP RST" messages in their log files for the servers I have the trouble with, the others have "TCP FIN".
Any idea how to determine what is causing the "TCP RST" and how to fix or avoid it?
Solved! Go to Solution.
- Tags:
- rcp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2012 01:45 PM
05-02-2012 01:45 PM
Re: Any way to avoid a "TCP RST"?
Options, well, other than upgrading from fossil-grade fifteen-year-old -- and clearly somewhat buggy -- software, I presume.
OpenVMS V6.2 and later offer the DCL command COPY /FTP, which means you have an easy way to embed this stuff in a command procedure, and a potential alternative to RCP. But then the COPY /FTP stuff could be a little wonky that far back, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2012 02:17 PM
05-02-2012 02:17 PM
Re: Any way to avoid a "TCP RST"?
Russ,
Could this be an issue with the firewall? Any logs to see what happens to the request?
Have you tried COPY/FTP/PASSIVE?
If that fails, do RSH commands work? That way you could trigger the copy from the monitoring servers, but initiate the copy from the monitored server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2012 06:57 AM
05-03-2012 06:57 AM
SolutionThanks for the replies. The server creating the performance data is in their vault, i.e. behind their firewall, now and FTP is blocked. I can RSH to it so I'm creating a command that I can send via RSH to have that server RCP the data back to me as a work around. Network support hasn't seen anything in their logs tp explain why there is this one way issue.