6 |
Table 6-10. Exception Log Event Codes - Continued
Log Event |
|
Code | Possible Cause and Resolution |
Eventª18º | Entry 3 of any Internet Control Message Protocol (ICMP) exception is a code |
ICMP events | uniquely identifying the software component of ICMP which reported the excep- |
| tion. |
| Entry 2 (hexadecimal) codes are as follows: |
| 2 ªCan't locate remote node; discarded requestº |
| A remote IP entity returned a ªDestination Unreachable ICMP message.º It |
| was unable to route the message to the destination. Entry 4 indicates the |
| ICMP message code field value present in the message. (See an ICMP |
| reference document for a description of field code values.) Entries 5 & 6 |
| contain the IP address bytes of the unreachable destination displayed as two |
| hexadecimal words. For example, 3.0.0.1 would be shown as 0300H 0001H. |
| Verify that the local and remote nodes are both connected and that both |
| applicationsarespecifyingproperIPaddresses. |
| 6 ªLocal request to send was rejected; discarded requestº |
| A call to icmp_out failed. PossibleEthernet cable problems. Check that the |
| LAN LED is ON or Blinking. Entry 4 contains a message type code for Echo |
| Response (0). Entries 5 & 6 contain the IP address bytes of the node to which |
| we are responding displayed as two hexadecimal words. For example,3.0.0.1 |
| would be shown as 0300H 0001H. |
| 8 ªLANdatamemory |
| A call to BuffAlloc failed. |
| 9 ªLocal request to send was rejected; discarded requestº |
| Internal error: An attempt to send an IP datagram with ipsend failed. Possible |
| Ethernet cable problems. Check that the LAN LED is ON or Blinking. Entry |
| 4 contains the length of the datagram. Entries 5 & 6 contain the IP address |
| bytes of the destination IP address of the datagram displayed as two |
| hexadecimal words. For example, 3.0.0.1 would be shown as 0300H 0001H. |
TCP/IP Ethernet Communications User's Manual ± January 1996 |
|
