GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- port is seen established while the network is down
Operating System - HP-UX
1855860
Members
1806
Online
104107
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
back
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
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
09-03-2010 05:38 AM
09-03-2010 05:38 AM
port is seen established while the network is down
I have a system running on hp-ux 11.23 that controls ATM. each ATM is assigned its own port number that the host listens to. when there is network problems, ATM goes in offline mode but in the host it shows that the port is still established.
unless we are told that the ATM is offline in order for us to kill the port manually for it to re-establish the connection, the ATM can remain in offline mode forever since the port is still established.
Is there a way of constantly checking the ports if indeed are able to reach the remote ATM and then resetting the ports?
unless we are told that the ATM is offline in order for us to kill the port manually for it to re-establish the connection, the ATM can remain in offline mode forever since the port is still established.
Is there a way of constantly checking the ports if indeed are able to reach the remote ATM and then resetting the ports?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2010 01:47 PM
09-03-2010 01:47 PM
Re: port is seen established while the network is down
Hi,
with tcp, the only way to detect that peer is not reachable is to send message which don't get acked.
For this there is a the keepalive (man setsockopt)
by default the keepalive is 2h, but you may for your need lower it to some smaller values.
- for instance 2 min-
then every 2 min a packet will be send to check that the tcp connection is still ok,
If the peer is back online, but it tcp connection was closed while the nework was down, then it will probably reset the connection. if peer doesn't answer , the keepalive packet will be send again for tcp_ip_abort_interval (default 10min)
The keepalive could also be managed at application layer, sending a "keepalive" message which need to be acked before some timeout, else the connection is abortively closed with so_linger (l_onoff=1,l_linger=0)
with tcp, the only way to detect that peer is not reachable is to send message which don't get acked.
For this there is a the keepalive (man setsockopt)
by default the keepalive is 2h, but you may for your need lower it to some smaller values.
- for instance 2 min-
then every 2 min a packet will be send to check that the tcp connection is still ok,
If the peer is back online, but it tcp connection was closed while the nework was down, then it will probably reset the connection. if peer doesn't answer , the keepalive packet will be send again for tcp_ip_abort_interval (default 10min)
The keepalive could also be managed at application layer, sending a "keepalive" message which need to be acked before some timeout, else the connection is abortively closed with so_linger (l_onoff=1,l_linger=0)
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 2026 Hewlett Packard Enterprise Development LP