> # Statistics IP

> Field | Description
> --- | ---
> InHdrErrors | The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
> InAddrErrors | The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. For entities which are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
> InUnknownProtos | The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
> InDiscards | The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
> OutDiscards | The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such frames met this (discretionary) discard criterion.
> OutNoRoutes | The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any frames counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagrams which a host cannot route because all of its default routers are down.
> FragFails | The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
> ReasmFails | The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
> InReceives | The total number of input datagrams received from interfaces, including those received in error.
> InDelivers | The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
> OutRequests | The total number of IP datagrams which local IP user- protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
> ForwDatagrams | The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP routers, this counter will include only those frames which were Source-Routed via this entity, and the Source-Route option processing was successful.
> FragOKs | The number of IP datagrams that have been successfully fragmented at this entity.
> FragCreates | The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
> ReasmReqds | The number of IP fragments received which needed to be reassembled at this entity.
> ReasmOKs | The number of IP datagrams successfully re-assembled.

> Copyright 2010-2015, Cisco Systems, Inc. All rights reserved.