HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Error adding client to network IUX server
Operating System - HP-UX
1836889
Members
2360
Online
110111
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
03-26-2006 03:38 PM
03-26-2006 03:38 PM
I am trying to add a system running HP-UX 11.11 (patched to Dec 2004 patch level) to network Ignite-UX server running B5725AA version B.6.1.44. Using add_new_client command on the IUX-client system, I am getting an error message:
/opt/ignite/bin/add_new_client -f -s tnt2uds1
ERROR: Client could not ping Ignite-UX Server: "tnt2uds1 "
Debugging the add_new_client script I found the error message is coming from the command:
ping_out=$(ping "$1" 1024 2 2> /dev/null)
It seems that pinging from client to IUX server with 1024 packet size is failing.
I tried to ping with different packet sizes from client to IUX server with the following result:
Packet Size Ping Result
64 Ok
512 Ok
1024 failed
2048 Ok
Questions:
1. Why pinging with packet size of 1024 fails, where as all other packet are successful.
2. Even after changing the add_new_client to use different packet size, the make_net_recovery command fails with the same message. Does the packet 1024 is used for NFS optimisation.
Has any one seen or heard this error with pinging with different packet sizes.
Navin
/opt/ignite/bin/add_new_client -f -s tnt2uds1
ERROR: Client could not ping Ignite-UX Server: "tnt2uds1 "
Debugging the add_new_client script I found the error message is coming from the command:
ping_out=$(ping "$1" 1024 2 2> /dev/null)
It seems that pinging from client to IUX server with 1024 packet size is failing.
I tried to ping with different packet sizes from client to IUX server with the following result:
Packet Size Ping Result
64 Ok
512 Ok
1024 failed
2048 Ok
Questions:
1. Why pinging with packet size of 1024 fails, where as all other packet are successful.
2. Even after changing the add_new_client to use different packet size, the make_net_recovery command fails with the same message. Does the packet 1024 is used for NFS optimisation.
Has any one seen or heard this error with pinging with different packet sizes.
Navin
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2006 04:18 PM
03-26-2006 04:18 PM
Solution
Hi Navin,
I believe the ping failure with 1024 packet is a network issue. You might want to check with network admin. It might be a case in the network, 1024 bytes packets are being dropped. Incorrect configuration maybe at firewall?
However if you change the packet size in the script , you should be able to add the client.
I don't think there is any relation of packet size 1024 bytes with NFS optimization.
I believe the ping failure with 1024 packet is a network issue. You might want to check with network admin. It might be a case in the network, 1024 bytes packets are being dropped. Incorrect configuration maybe at firewall?
However if you change the packet size in the script , you should be able to add the client.
I don't think there is any relation of packet size 1024 bytes with NFS optimization.
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