HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Simpler explanation of tcp keepalive parameter...
Operating System - HP-UX
1834142
Members
2167
Online
110064
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
Go to solution
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
11-03-2000 08:33 AM
11-03-2000 08:33 AM
I read S1100002433B and am confused. Is a simpler explanation possible? I understand tcp_keepalive_interval, but I get lost on the secondary timers. For instance, suppose tcp_keepalive_interval = 15 and tcp_ip_abort_interval = 10. Does that mean a total of 25 minutes must past before a connection is determined invalid and is terminated? TIA
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2000 02:17 PM
11-03-2000 02:17 PM
Solution
If a TCP packet was retransmitted again and again, it first triggers the R1 timer (tcp_ip_notify_interval).
If the retransmission goes on it will reach the R2 timer which will close the whole connection.
This is done due to the fact that a huge amount of retransmissions indicates that the complete connection is not working anymore.
R2 must always be bigger than R1, otherwise we would drop the connection before we could trigger the Dead Gateway Detection.
Berlene
If the retransmission goes on it will reach the R2 timer which will close the whole connection.
This is done due to the fact that a huge amount of retransmissions indicates that the complete connection is not working anymore.
R2 must always be bigger than R1, otherwise we would drop the connection before we could trigger the Dead Gateway Detection.
Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2000 06:15 AM
11-06-2000 06:15 AM
Re: Simpler explanation of tcp keepalive parameters
What parameter sets the interval between the individual retransmissions?
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