Help for IP, TCP, UDP and ICMP Data Display
This help page explains the system wide display, the MIB objects which are not interface specific, ICMP MIB objects, TCP and UDP Mib objects, and IP data from RFC1213 for a TCP/IP resource.
ICMP Data for
ICMP data is displayed for the IP address listed. Displays system wide the MIB objects which are not interface specific, ICMP MIB objects from RFC1213 for a TCP/IP resource. This display shows the input and output counters for a series of ICMP MIB objects.
Messages
In | The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors. |
Out | The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors. |
Errors
In | The number of ICMP messages which the entity received but determined as having ICMP-specific errors (for example, bad ICMP checksums, bad length). |
Out | The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to the value of this counter. |
Destination Unreachable
In | The number of ICMP Destination Unreachable messages received. |
Out | The number of ICMP Destination Unreachable messages sent. |
Time Exceeded
In | The number of ICMP Time Exceeded messages received. |
Out | The number of ICMP Time Exceeded messages sent. |
Parameter Problems
In | The number of ICMP Parameter Problem messages received. |
Out | The number of ICMP Parameter Problem messages sent. |
Source Quenches
In | The number of ICMP Source Quench messages received. |
Out | The number of ICMP Source Quench messages sent. |
Redirect
In | The number of ICMP Redirect messages received. |
Out | The number of ICMP Redirect messages sent. For a host, this object will always be zero since hosts do not send redirects. |
Echo Requests
In | The number of ICMP Echo (request) messages received. |
Out | The number of ICMP Echo (request) messages sent. |
Echo Replies
In | The number of ICMP Echo Reply messages received. |
Out | The number of ICMP Echo Reply messages sent. |
Timestamp Requests
In | The number of ICMP Timestamp (request) messages received. |
Out | The number of ICMP Timestamp (request) messages sent. |
Timestamp Replies
In | The number of ICMP Timestamp Reply messages received. |
Out | The number of ICMP Timestamp Reply messages sent. |
Address Mask Requests
In | The number of ICMP Address Mask Request messages received. |
Out | The number of ICMP Address Mask Request messages sent. |
Address Mask Replies
In | The number of ICMP Address Mask Reply messages received. |
Out | The number of ICMP Address Mask Reply messages sent. |
TCP/UDP Data for
TCP/UDP data is displayed for this IP address. The display system wide the MIB objects which are not interface specific, TCP and UDP MIB objects from RFC1213 for a TCP/IP resource.
TCP Data
The TCP data displayed.
Retransmit Algorithm
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. The retransmit algorithm can be on of the following values:
None of the following | |
Constant rto | |
MIL-STD-1778, Appendix B | |
Van Jacobson's algorithm (10) |
Min Retransmit Timeout
The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
Max Retransmit Timeout
The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
Maximum TCP Connections
The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
Active Open Connections
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
Passive Open Connections
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
Failed Connect Attempts
The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
Establish Resets
The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
Current Established Conn
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
Segments Received
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
Segments Sent
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
Retransmitted Segments
The number of TCP segments transmitted is the number of TCP segments transmitted containing one or more previously transmitted octets.
Bad TCP CHKSUMS
The total number of segments received in error (for example, bad TCP checksums).
RST Flagged Segments
The number of TCP segments sent containing the RST flag.
UDP Data
The UDP data displayed.
Datagrams Received
The total number of UDP datagrams delivered to UDP users.
Number Destination Ports
The total number of received UDP datagrams for which there was no application at the destination port.
Error Datagrams Received
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
Datagrams Sent
The total number of UDP datagrams sent from this entity.
IP Data for
The IP data for this IP address is displayed.
Gateway Forwarding
The indication of 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 from the host). The gateway forwarding can be either yes (forwarding), or no (not-forwarding). Click on the drop-down list to change this value.
Default TTL
The default value inserted into the Time-To-Live field of the IP header of datagrams originates at this entity whenever a TTL value is not supplied by the transport layer protocol. Click on the data field to change this value.
Total Datagrams Received
The total number of input datagrams received from interfaces, including those received in error.
IP Header Discards
The number of input datagrams discarded due to errors in their IP headers. This can include bad checksums, version number mismatch, other format errors, time-to-live exceeded, and errors discovered in processing their IP options, etc.
Invalid Address Discards
The number of input datagrams discarded because the IP address in the destination field of the IP header 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.
Forwarded Datagrams
The number of input datagrams for which this entity was not the final IP destination and, as a result, an attempt was made to find a route to forward them to their final destination. In entities which do not act as IP gateways, this counter will include only those packets which were source-routed from this entity, and the Source-Route option processing was successful.
Unknown Protocol Discards
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
All Other 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 that this counter does not include any datagrams discarded while awaiting reassembly.
Delivered Datagrams
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
Output Requests
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.
Reassemble Timeout
The maximum number of seconds in which received fragments are held while they are awaiting reassembly at this entity.
Reassemble Requests
The number of IP fragments received which needed to be reassembled at this entity.
Reassemble Success
The number of IP datagrams successfully reassembled.
Reassemble Failures
The number of failures detected by the IP reassembly algorithm (for example, timed out, errors). 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.
Fragments Success
The number of IP datagrams that have been successfully fragmented at this entity.
Fragments Fail
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.
Fragments Create
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 which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to clear buffer space for other routing entries.
Discard No Route Available
The number of IP datagrams discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. This also includes any datagrams which a host cannot route because all of its default gateways are down.
Output Discards
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (for example, lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
Community Name
The Write Community name allows you to enter a write password for this resource to enable you to set an object using the SNMP Set command.
Update Input Fields
Click on this button to update the changes you made to the data fields.