Cisco Cisco ASA 5510 Adaptive Security Appliance Leaflet

Cisco ASA Series 명령 참조, S 명령      

3장      show as-path-access-list through show auto-update 명령

Syslogs:

    None.

----------------------------------------------------------------

Name: invalid-ip-header

Invalid IP header:

    This counter is incremented and the packet is dropped when the appliance receives an 

IP packet whose computed checksum of the IP header does not match the recorded checksum in 

the header.

Recommendation:

    The packet corruption may be caused by a bad cable or noise on the line. It may also 

be that a peer is sending corrupted packets and an attack is in progress. Please use the 

packet capture feature to learn more about the origin of the packet.

Syslogs:

    None

----------------------------------------------------------------

Name: unsupported-ip-version

Unsupported IP version:

    This counter is incremented when the security appliance receives an IP packet that has 

an unsupported version in version field of IP header. Specifically, if the packet does not 

belong to version 4 or version 6. The packet is dropped.

Recommendation:

    Verify that other devices on connected network are configured to send IP packets 

belonging to versions 4 or 6 only.

Syslogs:

    None.

----------------------------------------------------------------

Name: invalid-ip-length

Invalid IP Length:

    This counter is incremented when the security appliance receives an IPv4 or IPv6 

packet in which the header length or total length fields in IP header are not valid or do 

not conform to the received packet length.

Recommendation:

    None.

Syslogs:

    None.

----------------------------------------------------------------

Name: invalid-ethertype

Invalid Ethertype:

    This counter is incremented when the fragmentation module on the security appliance 

receives or tries to send a fragmented packet that does not belong IP version 4 or version 

6. The packet is dropped.

Recommendation:

    Verify mtu of device and other devices on connected network to determine why the 

device is processing such fragments.

Syslogs:

    None.