HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- what is "IDLE" for TCP commections
Operating System - HP-UX
1833748
Members
2774
Online
110063
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
04-15-2002 08:31 AM
04-15-2002 08:31 AM
what is "IDLE" for TCP commections
Regarding my previous question
what is difference between "IDLE" and "ESTABLISHED" for TCP connections (not UDP) ?
Does it mean that no traffic posted yet since three-way handshaking ? There also opinion that it could mean not bounded yet socket.
Thank you.
what is difference between "IDLE" and "ESTABLISHED" for TCP connections (not UDP) ?
Does it mean that no traffic posted yet since three-way handshaking ? There also opinion that it could mean not bounded yet socket.
Thank you.
Vytautas Vysniauskas
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2002 02:27 AM
04-16-2002 02:27 AM
Re: what is "IDLE" for TCP commections
Hello
I have no notion of a socket state for TCP called IDLE in HP-UX , normally the states are LISTEN or ESTABLISHED , IDLE is a state for UDP as far as I know , usually meaning the socket is in a LISTENING state , the source code of LSOF might just use IDLE as indication for ESTABLISHED , 'LSOF' is not a standard supported tool by HP ( altough HP advised the use of it if needed) so it might not adhere to the common naming in HP_UX socket states , I don't have the code so I'm not sure about that
I have no notion of a socket state for TCP called IDLE in HP-UX , normally the states are LISTEN or ESTABLISHED , IDLE is a state for UDP as far as I know , usually meaning the socket is in a LISTENING state , the source code of LSOF might just use IDLE as indication for ESTABLISHED , 'LSOF' is not a standard supported tool by HP ( altough HP advised the use of it if needed) so it might not adhere to the common naming in HP_UX socket states , I don't have the code so I'm not sure about that
...knowing one ignores a greath many things is the first step to wisdom...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2002 02:51 AM
04-16-2002 02:51 AM
Re: what is "IDLE" for TCP commections
About idle tcp:
TCP congestion avoidance mechanisms are based on adjustments to the congestion-window size, triggered by the ACK clock. These mechanisms are not well matched to large but intermittent bursts of traffic, such as responses from a HTTP/1.1-based web server. Idle periods between bursts (web page replies) stop the ACK clock and hence disrupt even data flow.
The above tells that IDLE is used on TCP (not only UDP) as well.
See also: http://www.isi.edu/~johnh/PAPERS/Visweswaraiah97b.html
Regards,
Ceesjan
TCP congestion avoidance mechanisms are based on adjustments to the congestion-window size, triggered by the ACK clock. These mechanisms are not well matched to large but intermittent bursts of traffic, such as responses from a HTTP/1.1-based web server. Idle periods between bursts (web page replies) stop the ACK clock and hence disrupt even data flow.
The above tells that IDLE is used on TCP (not only UDP) as well.
See also: http://www.isi.edu/~johnh/PAPERS/Visweswaraiah97b.html
Regards,
Ceesjan
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