IP: General Tab
| Name | Description |
|---|---|
| Total datagrams received | The total number of input datagrams received from interfaces, including those received in error. |
| Forwarding capability | This indicates whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). Note that for some nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a badValue response if a management station attempts to change this object to an inappropriate value. |
| Default time-to-live | The default value inserted into the Time-To-Live (TTL) field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol. |
| Reassembly timeout(s) | The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity. |
| Reassemblies required | The number of IP fragments received which needed to be reassembled at this entity. |
| Reassembled datagrams | The number of IP datagrams successfully re-assembled. |
| Fragmented datagrams | The number of IP datagrams that have been successfully fragmented at this entity. |
| Fragmentation failures | The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be (for example, because their Don't Fragment flag was set). |
| Created due to fragmentation | The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. |
| Routing discards | The number of routing entries that were discarded although they were valid. A reason for discard could be to free up buffer space for other routing entries. |
Inbound Details
| Name | Description |
|---|---|
| Delivered | The total number of input datagrams successfully delivered to IP user-protocols including Internet Control Message Protocol (ICMP). |
| Header errors | 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, and so on. |
| Address errors | 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. This count includes invalid addresses (for example., 0.0.0.0) and addresses of unsupported Classes (for example., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. |
| Unknown protocols | The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol. |
| Discards | The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (for example, for lack of buffer space).
Note: This counter does not include any datagrams discarded while awaiting re-assembly. |
Outbound Details
| Name | Description |
|---|---|
| Requests | The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission.
Note: This counter does not include any datagrams counted in ipForwDatagrams. |
| Discards | 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: This counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. |
| No routes | Number of IP datagrams discarded because a route could not be found to transmit them to their destination.
Note: This counter includes any packets counted in ipForwDatagrams which meet this no-route criterion. This includes any datagrams which a host cannot route because all of its default gateways are down. |
