- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Keeping an idle tcp connection up for more than 2 ...
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
Keeping an idle tcp connection up for more than 2 hours
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2010 01:28 PM
04-07-2010 01:28 PM
Keeping an idle tcp connection up for more than 2 hours
Keeping an idle tcp connection up for more than 2 hours
It has been suggested that I can maintain this connection by adjusting a parameter in tcpip services that would exersize the connection periodically, like less than two hours. I've browsed the help and manual in tcpip services and googled it but I haven't found the correct setting I looking for. Can anybody help me here?
thanks
Clark Powell
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2010 02:00 PM
04-07-2010 02:00 PM
Re: Keeping an idle tcp connection up for more than 2 hours
Re: Keeping an idle tcp connection up for more than 2 hours
Details of the connection would lend themselves to determining which particular keepalive is appropriate. Or whether there's a brute-force solution for the protocol.
I'd be looking most carefully at the interface engine, and at the network itself.
Details on the connection and the network and the identity of the interface engine involved here might help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2010 10:09 PM
04-07-2010 10:09 PM
Re: Keeping an idle tcp connection up for more than 2 hours
Re: Keeping an idle tcp connection up for more than 2 hours
look at the 'tcpip_keepidle' mechanism.
Is a firewall involved here between those systems ? I've seen a case, where a firewall dropped an IDLE connection after 60 minutes when the OpenVMS (default) tcpip_keepidle was 14400 (i.e. 120 minutes). Lowering the value to 55 minutes on OpenVMS solved that problem.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2010 10:15 PM
04-07-2010 10:15 PM
Re: Keeping an idle tcp connection up for more than 2 hours
Re: Keeping an idle tcp connection up for more than 2 hours
as I assume this is a reproducable problem, consider to start a TCPDUMP trace on the OpenVMS system to capture all packets to/from the 'interface engine'.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2010 11:32 PM
04-07-2010 11:32 PM
Re: Keeping an idle tcp connection up for more than 2 hours
Re: Keeping an idle tcp connection up for more than 2 hours
TCPIP> sysconfig -q inet
...
tcp_keepalive_default = 0
...
TCPIP> sysconfig -r inet tcp_keepalive_default=1
The last command needs to be done after TCPIP is (re)started.
Oswald
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP