mib
Probes
The mib
provider makes available probes for counters from several MIBs. The protocols that export MIBs instrumented by the mib
provider are listed in Table 11-11. The table includes a reference to documentation that specifies some or all of the MIB, the name of the kernel statistic that may be used to access the running counts using the kstat2 -g uri
and a reference to the table that has a complete definition of the probes. All MIB counters are also available using the -s
option to netstat
.
Table 11-11 Descriptions With Links to Specific mib
Probes
Protocol | MIB Description | kstat2 URIs | MIB Probes Table |
---|---|---|---|
ICMP |
|
||
IP |
|
||
IPsec |
- |
|
|
IPv6 |
- |
||
SCTP |
SCTP MIB (Internet draft) |
|
|
TCP |
|
||
UDP |
|
Table 11-12 ICMP mib
Probes
Probe | Description |
---|---|
|
Fires whenever an ICMP Address Mask Reply message is received. |
|
Fires whenever an ICMP Address Mask Request message is received. |
|
Fires whenever an ICMP Redirect message is received that is determined to be malformed in some way (unknown ICMP code, sender or target off-link, and the like). |
|
Fires whenever an ICMP message with a bad checksum is received. |
|
Fires whenever an ICMP Destination Unreachable message is received. |
|
Fires whenever an ICMP Echo Reply message is received. |
|
Fires whenever an ICMP Echo request message is received. |
|
Fires whenever an ICMP message is received that is determined to have an ICMP-specific error, such as bad ICMP checksum and bad length. |
|
Fires whenever an ICMP Destination
Unreachable (Fragmentation Needed) message is
received, indicating that a sent packet was lost
because it was larger than some MTU and the
|
|
Fires whenever an ICMP message is received.
Whenever this probe fires, the
|
|
Fires whenever an ICMP message is received, but the message is subsequently dropped due to lack of buffer space. |
|
Fires whenever an ICMP Parameter Problem message is received. |
|
Fires whenever an ICMP Redirect message is received. |
|
Fires whenever an ICMP Source Quench message is received. |
|
Fires whenever an ICMP Time Exceeded message is received. |
|
Fires whenever an ICMP Timestamp Reply message is received. |
|
Fires whenever an ICMP Timestamp request message is received. |
|
Fires whenever an ICMP message of unknown type is received. |
|
Fires whenever an ICMP Address Mask Reply message is sent. |
|
Fires whenever an ICMP Destination Unreachable message is sent. |
|
Fires whenever an outbound ICMP message is dropped for some reason (such as memory allocation failure, broadcast/multicast source or destination, and the like). |
|
Fires whenever an ICMP Echo Reply message is sent. |
|
Fires whenever an ICMP message is not sent due to problems discovered within ICMP, such as a lack of buffers. This probe will not fire if errors are discovered outside the ICMP layer, such as the inability of IP to route the resulting datagram. |
|
Fires whenever an ICMP Destination Unreachable (Fragmentation Needed) message is sent. |
|
Fires whenever an ICMP message is sent.
Whenever this probe fires, the
|
|
Fires whenever an ICMP Parameter Problem message is sent. |
|
Fires whenever an ICMP Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects. |
|
Fires whenever an ICMP Time Exceeded message is sent. |
|
Fires whenever an ICMP Timestamp Reply message is sent. |
Table 11-13 IP mib
Probes
Probe | Description |
---|---|
|
Fires whenever a datagram is received that does not have this machine as its final IP destination, and an attempt is made to find a route to forward the datagram to that final destination. On machines that do not act as IP gateways, this probe will only fire for those packets that are source-routed through this machine, and for which the source-route option processing was successful. |
|
Fires whenever a datagram is received that does not have this machine as its final IP destination, but because the machine is not permitted to act as a router, no attempt is made to find a route to forward the datagram to that final destination. |
|
Fires whenever an IP datagram fragment is generated as a result of fragmentation. |
|
Fires whenever an IP datagram is discarded
because it could not be fragmented, for example,
because fragmentation was required and the
|
|
Fires whenever an IP datagram has been successfully fragmented. |
|
Fires whenever an input datagram is discarded due to a bad IP header checksum. |
|
Fires whenever an input datagram is successfully delivered to IP user protocols, including ICMP. |
|
Fires whenever an input IP datagram is discarded for reasons unrelated to the packet, such as for lack of buffer space. This probe does not fire for any datagram discarded while awaiting reassembly. |
|
Fires whenever an input datagram is discarded due to an error in its IP header, including a version number mismatch, a format error, an exceeded time-to-live, an error discovered in processing IP options, and the like. |
|
Fires whenever an IPv6 packet erroneously arrives on an IPv4 queue. |
|
Fires whenever a datagram is received from an interface, even if that datagram is received in error. |
|
Fires whenever a locally addressed datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol. |
|
Fires whenever an output IP datagram is
discarded for reasons unrelated to the packet (for
example, for lack of buffer space). This probe
will fire for a packet counted in the
|
|
Fires whenever an IPv6 packet is sent over an IPv4 connection. |
|
Fires whenever an IP datagram is discarded
because no route could be found to transmit it to
its destination. This probe will fire for a packet
counted in the |
|
Fires whenever an IP datagram is supplied to
IP for transmission from local IP user protocols
(include ICMP). Note that this probe will not fire
for any packet counted in the
|
|
Fires whenever a connection changes from using IPv4 to using IPv6 as its IP protocol. |
|
Fires whenever the IP reassembly algorithm determines that an IP fragment contains only previously received data. |
|
Fires whenever any failure is detected by the IP reassembly algorithm. This probe does not necessarily fire for every discarded IP fragment because some algorithms, notably the algorithm in RFC 815, can lose track of fragments by combining them as they are received. |
|
Fires whenever an IP datagram is successfully reassembled. |
|
Fires whenever the IP reassembly algorithm determines that an IP fragment contains both some previously received data and some new data. |
|
Fires whenever an IP fragment is received that needs to be reassembled. |
Table 11-14 IPsec mib
Probes
Probe | Description |
---|---|
|
Fires whenever a received packet is dropped because it fails to match the specified IPsec policy. |
|
Fires whenever a received packet matches the specified IPsec policy and processing is allowed to continue. |
Table 11-15 IPv6 mib
Probes
Probe | Description |
---|---|
|
Fires whenever an IPv6 datagram is received that does not have this machine as its final IPv6 destination, but because the machine is not permitted to act as a router, no attempt is made to find a route to forward the datagram to that final destination. |
|
Fires whenever an ICMPv6 neighbor discovery protocol message is received that is found to have a Hop Limit less than the defined maximum. Such messages might not have originated from a neighbor, and are therefore discarded. |
|
Fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is received. |
|
Fires whenever an ICMPv6 Neighbor Advertisement message is received that is malformed in some way. |
|
Fires whenever an ICMPv6 Neighbor Solicit message is received that is malformed in some way. |
|
Fires whenever an ICMPv6 Redirect message is received that is malformed in some way. |
|
Fires whenever an ICMPv6 Destination Unreachable message is received. |
|
Fires whenever an ICMPv6 Echo Reply message is received. |
|
Fires whenever an ICMPv6 Echo request message is received. |
|
Fires whenever an ICMPv6 message is received that is determined to have an ICMPv6-specific error (such as bad ICMPv6 checksum, bad length, and the like). |
|
Fires whenever an ICMPv6 Group Membership Query message is received that is malformed in some way. |
|
Fires whenever an ICMPv6 Group Membership Report message is received that is malformed in some way. |
|
Fires whenever an ICMPv6 Group Membership Report message is received. |
|
Fires whenever an ICMPv6 Group Membership Query message is received. |
|
Fires whenever an ICMPv6 Group Membership Reduction message is received. |
|
Fires whenever an ICMPv6 Group Membership Response message is received. |
|
Fires whenever an ICMPv6 multicast listener discovery message is received. |
|
Fires whenever an ICMPv6 message is
received. When this probe fires, the
|
|
Fires whenever an ICMPv6 Neighbor Advertisement message is received. |
|
Fires whenever an ICMPv6 Neighbor Solicit message is received. |
|
Fires whenever an ICMPv6 message is received, but that message is subsequently dropped due to lack of buffer space. |
|
Fires whenever an ICMPv6 Parameter Problem message is received. |
|
Fires whenever an ICMPv6 Redirect message is received. |
|
Fires whenever an ICMPv6 Router Advertisement message is received. |
|
Fires whenever an ICMPv6 Router Solicit message is received. |
|
Fires whenever an ICMPv6 Time Exceeded message is received. |
|
Fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is sent. |
|
Fires whenever an ICMPv6 Destination Unreachable message is sent. |
|
Fires whenever an ICMPv6 Echo Reply message is sent. |
|
Fires whenever an ICMPv6 Echo message is sent. |
|
Fires whenever an ICMPv6 message is not sent due to problems discovered within ICMPv6, such as a lack of buffers. This probe will not fire if errors are discovered outside the ICMPv6 layer, such as the inability of IPv6 to route the resulting datagram. |
|
Fires whenever an ICMPv6 Group Membership Query message is sent. |
|
Fires whenever an ICMPv6 Group Membership Reduction message is sent. |
|
Fires whenever an ICMPv6 Group Membership Response message is sent. |
|
Fires whenever an ICMPv6 message is sent.
When this probe fires, the
|
|
Fires whenever an ICMPv6 Neighbor Advertisement message is sent. |
|
Fires whenever an ICMPv6 Neighbor Solicitation message is sent. |
|
Fires whenever an ICMPv6 Parameter Problem message is sent. |
|
Fires whenever an ICMPv6 Packet Too Big message is sent. |
|
Fires whenever an ICMPv6 Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects. |
|
Fires whenever an ICMPv6 Router Advertisement message is sent. |
|
Fires whenever an ICMPv6 Router Solicit message is sent. |
|
Fires whenever an ICMPv6 Time Exceeded message is sent. |
|
Fires whenever an input datagram is discarded because the IPv6 address in their IPv6 header's destination field is not a valid address to be received by this entity. This probe will fire for invalid addresses (for example, ::0) and for unsupported addresses (for example, addresses with unallocated prefixes). For machines that are not configured to act as IPv6 routers and therefore do not forward datagrams, this probe will fire for datagrams discarded because the destination address was not a local address. |
|
Fires whenever an input datagram is successfully delivered to IPv6 user-protocols (including ICMPv6). |
|
Fires whenever an input IPv6 datagram is discarded for reasons unrelated to the packet (for example, for lack of buffer space). This probe does not fire for any datagram discarded while awaiting reassembly. |
|
Fires whenever an input datagram is discarded due to an error in its IPv6 header, including a version number mismatch, a format error, an exceeded hop count, an error discovered in processing IPv6 options, and the like. |
|
Fires whenever an IPv4 packet erroneously arrives on an IPv6 queue. |
|
Fires whenever a multicast IPv6 packet is received. |
|
Fires whenever a routed IPv6 datagram is discarded because no route could be found to transmit it to its destination. This probe will only fire for packets that have originated externally. |
|
Fires whenever an IPv6 datagram is received from an interface, even if that datagram is received in error. |
|
Fires whenever a fragment is received that is larger than the maximum fragment size. |
|
Fires whenever an input datagram is discarded because the datagram frame did not carry enough data. |
|
Fires whenever a locally-addressed IPv6 datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol. |
|
Fires whenever an output IPv6 datagram is
discarded for reasons unrelated to the packet (for
example, for lack of buffer space). This probe
will fire for a packet counted in the
|
|
Fires whenever a datagram is received that does not have this machine as its final IPv6 destination, and an attempt is made to find a route to forward the datagram to that final destination. On a machine that does not act as an IPv6 router, this probe will only fire for those packets that are source-routed through the machine, and for which the source-route option processing was successful. |
|
Fires whenever an IPv6 datagram fragment is generated as a result of fragmentation. |
|
Fires whenever an IPv6 datagram is discarded
because it could not be fragmented, for example,
because its |
|
Fires whenever an IPv6 datagrams has been successfully fragmented. |
|
Fires whenever an IPv6 packet is sent over an IPv4 connection. |
|
Fires whenever a multicast packet is sent. |
|
Fires whenever an IPv6 datagram is discarded because no route could be found to transmit it to its destination. This probe will not fire for packets that have originated externally. |
|
Fires whenever an IPv6 datagram is supplied
to IPv6 for transmission from local IPv6 user
protocols (including ICMPv6). This probe will not
fire for any packet counted in the
|
|
Fires whenever a connection changes from using IPv6 to using IPv4 as its IP protocol. |
|
Fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains only previously received data. |
|
Fires whenever a failure is detected by the IPv6 reassembly algorithm. This probe does not necessarily fire for every discarded IPv6 fragment since some algorithms can lose track of fragments by combining them as they are received. |
|
Fires whenever an IPv6 datagram is successfully reassembled. |
|
Fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains both some previously received data and some new data. |
|
Fires whenever an IPv6 fragment is received that needs to be reassembled. |
Table 11-16 Raw IP mib
Probes
Probe | Description |
---|---|
|
Fires whenever a raw IP packet is received that has a bad IP checksum. |
|
Fires whenever a raw IP packet is received. |
|
Fires whenever a raw IP packet is received that is malformed in some way. |
|
Fires whenever a raw IP packet is received, but that packet is subsequently dropped due to lack of buffer space. |
|
Fires whenever a raw IP packet is sent. |
|
Fires whenever a raw IP packet is not sent due to some error condition, typically because the raw IP packet was malformed in some way. |
Table 11-17 SCTP mib
Probes
Probe | Description |
---|---|
|
Fires whenever an SCTP association has made a direct transition to the CLOSED state from any state using the ABORT primitive, denoting ungraceful termination of the association. |
|
Fires whenever an SCTP association has made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state, denoting that the upper layer has initiated the association attempt. |
|
Fires whenever an SCTP packet is received from peers with an invalid checksum. |
|
Fires whenever an SCTP association is
tallied as a part of reading the
|
|
Fires whenever a user message has to be fragmented because of the MTU. |
|
Fires whenever data is received on a closed SCTP association. |
|
Fires whenever the
|
|
Fires whenever a duplicate ACK is received. |
|
Fires whenever an invalid cookie is received. |
|
Fires whenever the
|
|
Fires whenever the
|
|
Fires whenever the
|
|
Fires whenever an incoming connection is dropped for any reason. |
|
Fires whenever a selective acknowledgement is sent. |
|
Fires whenever delayed acknowledgement
processing is performed for an SCTP association.
Any acknowledgements sent as a part of delayed
acknowledgement processing will cause the
|
|
Fires whenever the
|
|
Fires whenever an otherwise correct SCTP packet is received for which the receiver is not able to identify the association to which the packet belongs. |
|
Fires whenever the
|
|
Fires whenever the
|
|
Fires whenever the
|
|
Fires whenever a window probe is sent. |
|
Fires whenever a window update is sent. |
|
Fires whenever SCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state. The remote endpoint has initiated the association attempt. |
|
Fires whenever the
|
|
Fires whenever the
|
|
Fires whenever an SCTP association makes the direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state, denoting graceful termination of the association. |
|
Fires whenever an SCTP association is aborted due to failure to receive a heartbeat acknowledgement. |
|
Fires whenever an SCTP heartbeat is sent. |
|
Fires whenever timer-based retransmit processing is performed on an association. |
|
Fires whenever prolonged failure to perform timer-based retransmission results in the association being aborted. |
Table 11-18 TCP mib
Probes
Probe | Description |
---|---|
|
Fires whenever a TCP connection makes a
direct transition from the
|
|
Fires whenever a TCP connection makes a
direct transition to the |
|
Fires whenever a TCP connection is tallied
as a part of reading the
|
|
Fires whenever a TCP connection makes the
direct transition to the |
|
Fires whenever a connection is dropped due
to a full queue of connections in the
|
|
Fires whenever an |
|
Fires whenever an |
|
Fires whenever an |
|
Fires whenever data was received for a connection in a closing state. |
|
Fires whenever a segment is received such
that all data in the segment has been previously
received. The number of bytes in the duplicated
segment is passed in
|
|
Fires whenever a segment is received such
that all data in the segment has been previously
received. The number of bytes in the duplicated
segment is passed in
|
|
Fires whenever data is received such that
all data prior to the new
data's sequence number has been previously
received. The number of bytes received in-order is
passed in |
|
Fires whenever a segment is received such that all data prior to the new segment's sequence number has been previously received. |
|
Fires whenever a segment is received such
that some of the data in the segment has been
previously received, but some of the data in the
segment is new. The number of duplicate bytes is
passed in |
|
Fires whenever a segment is received such
that some of the data in the segment has been
previously received, but some of the data in the
segment is new. The number of duplicate bytes is
passed in |
|
Fires whenever data is received that lies
past the current receive window. The number of
bytes is in |
|
Fires whenever a segment is received that lies past the current receive window. |
|
Fires whenever data is received such that
some data prior to the new data's sequence number
is missing. The number of bytes received unordered
is passed in |
|
Fires whenever a segment is received such that some data prior to the new data's sequence number is missing. |
|
Fires whenever a duplicate ACK is received. |
|
Fires whenever a TCP error (for example, a bad TCP checksum) is found on a received segment. |
|
Fires whenever a segment is received, even if that segment is later found to have an error that prevents further processing. |
|
Fires whenever a window probe is received. |
|
Fires whenever a window update is received. |
|
Fires whenever an incoming connection is dropped due to a full listen queue. |
|
Fires whenever a connection is dropped due
to a full queue of connections in the
|
|
Fires whenever an |
|
Fires whenever an |
|
Fires whenever a |
|
Fires whenever data is sent. The number of
bytes sent is in
|
|
Fires whenever a segment is sent. |
|
Fires whenever a segment is retransmitted as part of the fast retransmit algorithm. |
|
Fires whenever a segment is sent with the RST flag set. |
|
Fires whenever a segment is retransmitted on a connection that has selective acknowledgement enabled. |
|
Fires whenever a segment is sent that contains at least one non-retransmitted byte. |
|
Fires whenever a segment is sent with the URG flag set, and with a valid urgent pointer. |
|
Fires whenever a window probe is sent. |
|
Fires whenever a window update is sent. |
|
Fires whenever a TCP connections have made a
direct transition to the
|
|
Fires whenever data is retransmitted. The
number of bytes retransmitted is in
|
|
Fires whenever a segment is sent that contains one or more retransmitted bytes. |
|
Fires whenever data was received, but there was no timestamp information available with which to update the RTT. |
|
Fires whenever data was received containing the timestamp information necessary to update the RTT. |
|
Fires whenever timer-based keep-alive processing is performed on a connection. |
|
Fires whenever keep-alive processing results in termination of a connection. |
|
Fires whenever a keep-alive probe is sent out as a part of keep-alive processing. |
|
Fires whenever timer-based retransmit processing is performed on a connection. |
|
Fires whenever prolonged failure to perform timer-based retransmission results in termination of the connection. |
Table 11-19 UDP mib
Probes
Probe | Description |
---|---|
|
Fires whenever a datagram is discarded due to a bad UDP checksum. |
|
Fires whenever a UDP datagram is received. |
|
Fires whenever a UDP datagram is received, but is discarded due to either a malformed packet header or the failure to allocate an internal buffer. |
|
Fires whenever a UDP datagram is received, but subsequently dropped due to lack of buffer space. |
|
Fires whenever a UDP datagram is received on a port to which no socket is bound. |
|
Fires whenever a UDP datagram is sent. |
|
Fires whenever a UDP datagram is not sent due to some error condition, typically because the datagram was malformed in some way. |