- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Numerous calls to icmp_error
Operating System - OpenVMS
1752808
Members
6174
Online
108789
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
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
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
02-24-2010 06:22 PM
02-24-2010 06:22 PM
Hi Folks,
I'm seeing a lot of this errors on our nodes and would just like to get some points on how to troubleshoot here:
$ tcpip show prot icmp
icmp:
28116 calls to icmp_error
0 errors not generated because old ip message was too short
0 errors not generated because old message was icmp
Output histogram:
echo reply: 362556
destination unreachable: 28116
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
Input histogram:
echo reply: 887448
destination unreachable: 224
echo: 362556
router solicitation: 3
address mask request: 3
362556 message responses generated
$
1. Is this kind of error specific to a single network card? Because on our nodes, we have 2 network cards and 1 is not used but is still active.
2. I have read somewhere that this might be due to the fact that the router where our node is connected to might be experiencing high utilization. What should I ask our network admin to check first in this case?
3. The item "destination unreachable" seems to equate to the number of calls to icmp_error. How can I see which destination it is trying to reach? Will this be visible on any of our log files? I can't seem to see it on the operator.log yet.
This node is an ES80 on OpenVMS 7.3-2, TCPIP v5.4 ECO7.
Thanks.
I'm seeing a lot of this errors on our nodes and would just like to get some points on how to troubleshoot here:
$ tcpip show prot icmp
icmp:
28116 calls to icmp_error
0 errors not generated because old ip message was too short
0 errors not generated because old message was icmp
Output histogram:
echo reply: 362556
destination unreachable: 28116
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
Input histogram:
echo reply: 887448
destination unreachable: 224
echo: 362556
router solicitation: 3
address mask request: 3
362556 message responses generated
$
1. Is this kind of error specific to a single network card? Because on our nodes, we have 2 network cards and 1 is not used but is still active.
2. I have read somewhere that this might be due to the fact that the router where our node is connected to might be experiencing high utilization. What should I ask our network admin to check first in this case?
3. The item "destination unreachable" seems to equate to the number of calls to icmp_error. How can I see which destination it is trying to reach? Will this be visible on any of our log files? I can't seem to see it on the operator.log yet.
This node is an ES80 on OpenVMS 7.3-2, TCPIP v5.4 ECO7.
Thanks.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2010 05:10 AM
02-25-2010 05:10 AM
Solution
The "destination unreachable" typically indicates that your adjacent router is having a problem forwarding packets from your server onward to their destination. Routers send these messages back to the source when it can not successfully forward a packet. Could be that the destination host is down, a network link on the other side of the router is down, the host that is supposed to recieve the packets is not listening on the target port, or a myriad of other things. You _probably_ need not be concerned with your host. You'll _likely_ want to be looking on the other side of your local routers for the issue (if there still is an issue).
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP