Finisar Surveyor - Manual (Page 267)

10-63
Expert Features
Network Layer
10
ICMP Bad IP Header
Counter
ICMP Bad IP Header events are counted in the ICMP All Errors counter. A count of
all ICMP errors displays in the
Overview counters of Expert View. A threshold can
be set in Expert Alarms for all ICMP errors.
Expert Symptom
ICMP Bad IP Header events are automatically logged as expert symptoms. The
Symptom Summary field provides information about the IP addresses involved.
Examples are:
Sent by Destination Host [206.250.228.69] to
[206.250.228.11]. Bad Octet at 14. SA=[206.250.228.11]
DA=[206.250.228.69]
Sent by Gateway [206.250.228.61] to [206.250.228.11] when
forwarding to Destination [206.250.228.69]. Bad Octet at
14. SA=[206.250.228.11] DA=[206.250.228.69]
Diagnostic Details
__________________________________________________________________
Problem Description:
An ICMP Parameter Problem (IP header is bad) message has been sent.
__________________________________________________________________
Probable Cause(s):
1. A host/router may send this message if the IP header parameters have
problems that prevent it from processing the packet.
2. A host/router may have a bad network stack or a bad interface card.
3. There may be incorrect arguments in IP options.
__________________________________________________________________
Recommended Action(s):
1. Check the ICMP Pointer field to see the octet in the IP header where the error
was detected.
2. Verify that the source that sent this IP header has a good network interface
card.
3. Verify that the network stack on the source that sent the bad IP header
parameters is working properly.