- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Networking issue
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
Forums
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
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
08-16-2006 10:09 PM
08-16-2006 10:09 PM
Networking issue
we have HP UX 11 and we are facing a problem with networking causing applications failure.
the problem is that HP UX cannot detect if another computer inside its SUBNET is turned off or not, if we tried to ping that computer while its off it doesnt reply AT ALL and it doesnt return "not reachable" or "time out" in the contrary it stays waiting while it PINGS that computer when its turned on.
are there any time-out parameters in HP ux for TCP communications. or should we do any other action?
your quick response is appreciated.
thank you,
Jamal Hammadi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2006 10:17 PM
08-16-2006 10:17 PM
Re: Networking issue
ping your_remote_host -n 3 ; echo $?
Base on return code, you can do what you want to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2006 10:19 PM
08-16-2006 10:19 PM
Re: Networking issue
man ping shows:
-n count The number of packets ping will transmit before
terminating. The -n is not needed if also specifying
packet-size. Range: zero to 2147483647. The default
is zero, in which case ping sends packets until
interrupted.
-m timeout Override the default timeout value (10 seconds) which
ping uses to timeout (in seconds) when a host or
network is unreachable. This option is valid only
with the -n option or when count is specified. The
-m option should not be used with count equal to 0.
The -m option is not effective for reachable hosts or
networks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2006 12:54 PM
08-17-2006 12:54 PM
Re: Networking issue
On linux one cannot rely on the ARP timeout bit anyway for remote destinations.
And if there is something doing proxy-ARP, or if someone has hard-coded an ARP setting, the ARP timeouts won't happen for a powered-down local subnet system either, so even on Linux one should probably be using request limits.
Strictly speaking, ping is not TCP communications. ping is ICMP, which is below TCP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2006 01:23 PM
08-17-2006 01:23 PM
Re: Networking issue
This is the way things are with ping on many flavors of Unix/Linux.
On certain ISP based servers, an alias was created that made ping form the commands recommended above. This was done to prevent inexerienced users from clogging systems and support with questions.
As with many things, its left for the administrator to decide what the best practice is for their system.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com