Go to main content

Oracle® Solaris 11.4 DTrace (Dynamic Tracing) Guide

Exit Print View

Updated: September 2020
 
 

mib Provider

The mib provider makes available probes that correspond to counters in the Oracle Solaris management information bases (MIBs). MIB counters are used by the simple network management protocol (SNMP) that allow remote monitoring of heterogeneous networking entities. You can also view the counters with the kstat2 and netstat commands. For more information, see the kstat2(8) and netstat(8) man pages. The mib provider facilitates quick exploration of aberrant networking behavior that is observed using either remote or local networking monitors.

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 Figure 31, Table 31, Descriptions With Links to Specific mib Probes. 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 31  Descriptions With Links to Specific mib Probes
Protocol
MIB Description
kstat2 URIs
MIB Probes Table
ICMP
/mib2/ip/icmp/*
IP
/mib2/ip/ip/*
IPsec
-
/mib2/ip/ip/*
IPv6
-
SCTP
SCTP MIB (Internet draft)
/mib2/sctp/sctp/*
TCP
/mib2/tcp/tcp/*
UDP
/mib2/udp/udp/*
Table 32  ICMP mib Probes
Probe
Description
icmpInAddrMaskReps
Fires whenever an ICMP Address Mask Reply message is received.
icmpInAddrMasks
Fires whenever an ICMP Address Mask Request message is received.
icmpInBadRedirects
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).
icmpInCksumErrs
Fires whenever an ICMP message with a bad checksum is received.
icmpInDestUnreachs
Fires whenever an ICMP Destination Unreachable message is received.
icmpInEchoReps
Fires whenever an ICMP Echo Reply message is received.
icmpInEchos
Fires whenever an ICMP Echo request message is received.
icmpInErrors
Fires whenever an ICMP message is received that is determined to have an ICMP-specific error, such as bad ICMP checksum and bad length.
icmpInFragNeeded
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 Do not Fragment flag was set.
icmpInMsgs
Fires whenever an ICMP message is received. Whenever this probe fires, the icmpInErrors probe may also fire if the message is determined to have an ICMP-specific error.
icmpInOverflows
Fires whenever an ICMP message is received, but the message is subsequently dropped due to lack of buffer space.
icmpInParmProbs
Fires whenever an ICMP Parameter Problem message is received.
icmpInRedirects
Fires whenever an ICMP Redirect message is received.
icmpInSrcQuenchs
Fires whenever an ICMP Source Quench message is received.
icmpInTimeExcds
Fires whenever an ICMP Time Exceeded message is received.
icmpInTimestampReps
Fires whenever an ICMP Timestamp Reply message is received.
icmpInTimestamps
Fires whenever an ICMP Timestamp request message is received.
icmpInUnknowns
Fires whenever an ICMP message of unknown type is received.
icmpOutAddrMaskReps
Fires whenever an ICMP Address Mask Reply message is sent.
icmpOutDestUnreachs
Fires whenever an ICMP Destination Unreachable message is sent.
icmpOutDrops
Fires whenever an outbound ICMP message is dropped for some reason (such as memory allocation failure, broadcast/multicast source or destination, and the like).
icmpOutEchoReps
Fires whenever an ICMP Echo Reply message is sent.
icmpOutErrors
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.
icmpOutFragNeeded
Fires whenever an ICMP Destination Unreachable (Fragmentation Needed) message is sent.
icmpOutMsgs
Fires whenever an ICMP message is sent. Whenever this probe fires, the icmpOutErrors probe might also fire if the message is determined to have ICMP-specific errors.
icmpOutParmProbs
Fires whenever an ICMP Parameter Problem message is sent.
icmpOutRedirects
Fires whenever an ICMP Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects.
icmpOutTimeExcds
Fires whenever an ICMP Time Exceeded message is sent.
icmpOutTimestampReps
Fires whenever an ICMP Timestamp Reply message is sent.
Table 33  IP mib Probes
Probe
Description
ipForwDatagrams
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.
ipForwProhibits
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.
ipFragCreates
Fires whenever an IP datagram fragment is generated as a result of fragmentation.
ipFragFails
Fires whenever an IP datagram is discarded because it could not be fragmented, for example, because fragmentation was required and the Do not Fragment flag was set.
ipFragOKs
Fires whenever an IP datagram has been successfully fragmented.
ipInCksumErrs
Fires whenever an input datagram is discarded due to a bad IP header checksum.
ipInDelivers
Fires whenever an input datagram is successfully delivered to IP user protocols, including ICMP.
ipInDiscards
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.
ipInHdrErrors
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.
ipInIPv6
Fires whenever an IPv6 packet erroneously arrives on an IPv4 queue.
ipInReceives
Fires whenever a datagram is received from an interface, even if that datagram is received in error.
ipInUnknownProtos
Fires whenever a locally addressed datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol.
ipOutDiscards
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 ipForwDatagrams MIB counter if the packet meets such a (discretionary) discard criterion.
ipOutIPv6
Fires whenever an IPv6 packet is sent over an IPv4 connection.
ipOutNoRoutes
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 ipForwDatagrams MIB counter if the packet meets this "no-route" criterion. This probe will also fire for any datagrams which cannot be routed because all default gateways are down.
ipOutRequests
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 ipForwDatagrams MIB counter.
ipOutSwitchIPv6
Fires whenever a connection changes from using IPv4 to using IPv6 as its IP protocol.
ipReasmDuplicates
Fires whenever the IP reassembly algorithm determines that an IP fragment contains only previously received data.
ipReasmFails
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.
ipReasmOKs
Fires whenever an IP datagram is successfully reassembled.
ipReasmPartDups
Fires whenever the IP reassembly algorithm determines that an IP fragment contains both some previously received data and some new data.
ipReasmReqds
Fires whenever an IP fragment is received that needs to be reassembled.
Table 34  IPsec mib Probes
Probe
Description
ipsecInFailed
Fires whenever a received packet is dropped because it fails to match the specified IPsec policy.
ipsecInSucceeded
Fires whenever a received packet matches the specified IPsec policy and processing is allowed to continue.
Table 35  IPv6 mib Probes
Probe
Description
ipv6ForwProhibits
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.
ipv6IfIcmpBadHoplimit
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.
ipv6IfIcmpInAdminProhibs
Fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is received.
ipv6IfIcmpInBadNeighborAdvertisements
Fires whenever an ICMPv6 Neighbor Advertisement message is received that is malformed in some way.
ipv6IfIcmpInBadNeighborSolicitations
Fires whenever an ICMPv6 Neighbor Solicit message is received that is malformed in some way.
ipv6IfIcmpInBadRedirects
Fires whenever an ICMPv6 Redirect message is received that is malformed in some way.
ipv6IfIcmpInDestUnreachs
Fires whenever an ICMPv6 Destination Unreachable message is received.
ipv6IfIcmpInEchoReplies
Fires whenever an ICMPv6 Echo Reply message is received.
ipv6IfIcmpInEchos
Fires whenever an ICMPv6 Echo request message is received.
ipv6IfIcmpInErrors
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).
ipv6IfIcmpInGroupMembBadQueries
Fires whenever an ICMPv6 Group Membership Query message is received that is malformed in some way.
ipv6IfIcmpInGroupMembBadReports
Fires whenever an ICMPv6 Group Membership Report message is received that is malformed in some way.
ipv6IfIcmpInGroupMembOurReports
Fires whenever an ICMPv6 Group Membership Report message is received.
ipv6IfIcmpInGroupMembQueries
Fires whenever an ICMPv6 Group Membership Query message is received.
ipv6IfIcmpInGroupMembReductions
Fires whenever an ICMPv6 Group Membership Reduction message is received.
ipv6IfIcmpInGroupMembResponses
Fires whenever an ICMPv6 Group Membership Response message is received.
ipv6IfIcmpInGroupMembTotal
Fires whenever an ICMPv6 multicast listener discovery message is received.
ipv6IfIcmpInMsgs
Fires whenever an ICMPv6 message is received. When this probe fires, the ipv6IfIcmpInErrors probe might also fire if the message has an ICMPv6-specific error.
ipv6IfIcmpInNeighborAdvertisements
Fires whenever an ICMPv6 Neighbor Advertisement message is received.
ipv6IfIcmpInNeighborSolicits
Fires whenever an ICMPv6 Neighbor Solicit message is received.
ipv6IfIcmpInOverflows
Fires whenever an ICMPv6 message is received, but that message is subsequently dropped due to lack of buffer space.
ipv6IfIcmpInParmProblems
Fires whenever an ICMPv6 Parameter Problem message is received.
ipv6IfIcmpInRedirects
Fires whenever an ICMPv6 Redirect message is received.
ipv6IfIcmpInRouterAdvertisements
Fires whenever an ICMPv6 Router Advertisement message is received.
ipv6IfIcmpInRouterSolicits
Fires whenever an ICMPv6 Router Solicit message is received.
ipv6IfIcmpInTimeExcds
Fires whenever an ICMPv6 Time Exceeded message is received.
ipv6IfIcmpOutAdminProhibs
Fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is sent.
ipv6IfIcmpOutDestUnreachs
Fires whenever an ICMPv6 Destination Unreachable message is sent.
ipv6IfIcmpOutEchoReplies
Fires whenever an ICMPv6 Echo Reply message is sent.
ipv6IfIcmpOutEchos
Fires whenever an ICMPv6 Echo message is sent.
ipv6IfIcmpOutErrors
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.
ipv6IfIcmpOutGroupMembQueries
Fires whenever an ICMPv6 Group Membership Query message is sent.
ipv6IfIcmpOutGroupMembReductions
Fires whenever an ICMPv6 Group Membership Reduction message is sent.
ipv6IfIcmpOutGroupMembResponses
Fires whenever an ICMPv6 Group Membership Response message is sent.
ipv6IfIcmpOutMsgs
Fires whenever an ICMPv6 message is sent. When this probe fires, the ipv6IfIcmpOutErrors probe might also fire if the message has ICMPv6-specific errors.
ipv6IfIcmpOutNeighborAdvertisements
Fires whenever an ICMPv6 Neighbor Advertisement message is sent.
ipv6IfIcmpOutNeighborSolicits
Fires whenever an ICMPv6 Neighbor Solicitation message is sent.
ipv6IfIcmpOutParmProblems
Fires whenever an ICMPv6 Parameter Problem message is sent.
ipv6IfIcmpOutPktTooBigs
Fires whenever an ICMPv6 Packet Too Big message is sent.
ipv6IfIcmpOutRedirects
Fires whenever an ICMPv6 Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects.
ipv6IfIcmpOutRouterAdvertisements
Fires whenever an ICMPv6 Router Advertisement message is sent.
ipv6IfIcmpOutRouterSolicits
Fires whenever an ICMPv6 Router Solicit message is sent.
ipv6IfIcmpOutTimeExcds
Fires whenever an ICMPv6 Time Exceeded message is sent.
ipv6InAddrErrors
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.
ipv6InDelivers
Fires whenever an input datagram is successfully delivered to IPv6 user-protocols (including ICMPv6).
ipv6InDiscards
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.
ipv6InHdrErrors
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.
ipv6InIPv4
Fires whenever an IPv4 packet erroneously arrives on an IPv6 queue.
ipv6InMcastPkts
Fires whenever a multicast IPv6 packet is received.
ipv6InNoRoutes
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.
ipv6InReceives
Fires whenever an IPv6 datagram is received from an interface, even if that datagram is received in error.
ipv6InTooBigErrors
Fires whenever a fragment is received that is larger than the maximum fragment size.
ipv6InTruncatedPkts
Fires whenever an input datagram is discarded because the datagram frame did not carry enough data.
ipv6InUnknownProtos
Fires whenever a locally-addressed IPv6 datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol.
ipv6OutDiscards
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 ipv6OutForwDatagrams MIB counter if the packet meets such a (discretionary) discard criterion.
ipv6OutForwDatagrams
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.
ipv6OutFragCreates
Fires whenever an IPv6 datagram fragment is generated as a result of fragmentation.
ipv6OutFragFails
Fires whenever an IPv6 datagram is discarded because it could not be fragmented, for example, because its Do not Fragment flag was set.
ipv6OutFragOKs
Fires whenever an IPv6 datagrams has been successfully fragmented.
ipv6OutIPv4
Fires whenever an IPv6 packet is sent over an IPv4 connection.
ipv6OutMcastPkts
Fires whenever a multicast packet is sent.
ipv6OutNoRoutes
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.
ipv6OutRequests
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 ipv6ForwDatagrams MIB counter.
ipv6OutSwitchIPv4
Fires whenever a connection changes from using IPv6 to using IPv4 as its IP protocol.
ipv6ReasmDuplicates
Fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains only previously received data.
ipv6ReasmFails
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.
ipv6ReasmOKs
Fires whenever an IPv6 datagram is successfully reassembled.
ipv6ReasmPartDups
Fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains both some previously received data and some new data.
ipv6ReasmReqds
Fires whenever an IPv6 fragment is received that needs to be reassembled.
Table 36  Raw IP mib Probes
Probe
Description
rawipInCksumErrs
Fires whenever a raw IP packet is received that has a bad IP checksum.
rawipInDatagrams
Fires whenever a raw IP packet is received.
rawipInErrors
Fires whenever a raw IP packet is received that is malformed in some way.
rawipInOverflows
Fires whenever a raw IP packet is received, but that packet is subsequently dropped due to lack of buffer space.
rawipOutDatagrams
Fires whenever a raw IP packet is sent.
rawipOutErrors
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 37  SCTP mib Probes
Probe
Description
sctpAborted
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.
sctpActiveEstab
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.
sctpChecksumError
Fires whenever an SCTP packet is received from peers with an invalid checksum.
sctpCurrEstab
Fires whenever an SCTP association is tallied as a part of reading the sctpCurrEstab MIB counter. An SCTP association is tallied if its current state is ESTABLISHED, SHUTDOWN-RECEIVED, or SHUTDOWN-PENDING.
sctpFragUsrMsgs
Fires whenever a user message has to be fragmented because of the MTU.
sctpInClosed
Fires whenever data is received on a closed SCTP association.
sctpInCtrlChunks
Fires whenever the sctpInCtrlChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpInDupAck
Fires whenever a duplicate ACK is received.
sctpInInvalidCookie
Fires whenever an invalid cookie is received.
sctpInOrderChunks
Fires whenever the sctpInOrderChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpInSCTPPkts
Fires whenever the sctpInSCTPPkts MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpInUnorderChunks
Fires whenever the sctpInUnorderChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpListenDrop
Fires whenever an incoming connection is dropped for any reason.
sctpOutAck
Fires whenever a selective acknowledgement is sent.
sctpOutAckDelayed
Fires whenever delayed acknowledgement processing is performed for an SCTP association. Any acknowledgements sent as a part of delayed acknowledgement processing will cause the sctpOutAck probe to fire.
sctpOutCtrlChunks
Fires whenever the sctpOutCtrlChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpOutOfBlue
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.
sctpOutOrderChunks
Fires whenever the sctpOutOrderChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in aRgs[0].
sctpOutSCTPPkts
Fires whenever the sctpOutSCTPPkts MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpOutUnorderChunks
Fires whenever the sctpOutUnorderChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpOutWinProbe
Fires whenever a window probe is sent.
sctpOutWinUpdate
Fires whenever a window update is sent.
sctpPassiveEstab
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.
sctpReasmUsrMsgs
Fires whenever the sctpReasmUsrMsgs MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpRetransChunks
Fires whenever the sctpRetransChunks MIB counter is updated, either because the MIB counter is explicitly queried or because an SCTP connection is closed. The value by which the MIB counter is to be increased is in args[0].
sctpShutdowns
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.
sctpTimHeartBeatDrop
Fires whenever an SCTP association is aborted due to failure to receive a heartbeat acknowledgement.
sctpTimHeartBeatProbe
Fires whenever an SCTP heartbeat is sent.
sctpTimRetrans
Fires whenever timer-based retransmit processing is performed on an association.
sctpTimRetransDrop
Fires whenever prolonged failure to perform timer-based retransmission results in the association being aborted.
Table 38  TCP mib Probes
Probe
Description
tcpActiveOpens
Fires whenever a TCP connection makes a direct transition from the CLOSED state to the SYN_SENT state.
tcpAttemptFails
Fires whenever a TCP connection makes a direct transition to the CLOSED state from either the SYN_SENT state or the SYN_RCVD state and whenever a TCP connection makes a direct transition to the LISTEN state from the SYN_RCVD state.
tcpCurrEstab
Fires whenever a TCP connection is tallied as a part of reading the tcpCurrEstab MIB counter. A TCP connection is tallied if its current state is either ESTABLISHED or CLOSE_WAIT.
tcpEstabResets
Fires whenever a TCP connection makes the direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE_WAIT state.
tcpHalfOpenDrop
Fires whenever a connection is dropped due to a full queue of connections in the SYN_RCVD state.
tcpInAckBytes
Fires whenever an ACK is received for previously sent data. The number of bytes acknowledged is passed in args[0].
tcpInAckSegs
Fires whenever an ACK is received for a previously sent segment.
tcpInAckUnsent
Fires whenever an ACK is received for an unsent segment.
tcpInClosed
Fires whenever data was received for a connection in a closing state.
tcpInDataDupBytes
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 args[0].
tcpInDataDupSegs
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 args[0].
tcpInDataInorderBytes
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 args[0].
tcpInDataInorderSegs
Fires whenever a segment is received such that all data prior to the new segment's sequence number has been previously received.
tcpInDataPartDupBytes
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 args[0].
tcpInDataPartDupSegs
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 args[0].
tcpInDataPastWinBytes
Fires whenever data is received that lies past the current receive window. The number of bytes is in args[0].
tcpInDataPastWinSegs
Fires whenever a segment is received that lies past the current receive window.
tcpInDataUnorderBytes
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 args[0].
tcpInDataUnorderSegs
Fires whenever a segment is received such that some data prior to the new data's sequence number is missing.
tcpInDupAck
Fires whenever a duplicate ACK is received.
tcpInErrs
Fires whenever a TCP error (for example, a bad TCP checksum) is found on a received segment.
tcpInSegs
Fires whenever a segment is received, even if that segment is later found to have an error that prevents further processing.
tcpInWinProbe
Fires whenever a window probe is received.
tcpInWinUpdate
Fires whenever a window update is received.
tcpListenDrop
Fires whenever an incoming connection is dropped due to a full listen queue.
tcpListenDropQ0
Fires whenever a connection is dropped due to a full queue of connections in the SYN_RCVD state.
tcpOutAck
Fires whenever an ACK is sent.
tcpOutAckDelayed
Fires whenever an ACK is sent after having been initially delayed.
tcpOutControl
Fires whenever a SYN, FIN, or RST is sent.
tcpOutDataBytes
Fires whenever data is sent. The number of bytes sent is in args[0].
tcpOutDataSegs
Fires whenever a segment is sent.
tcpOutFastRetrans
Fires whenever a segment is retransmitted as part of the fast retransmit algorithm.
tcpOutRsts
Fires whenever a segment is sent with the RST flag set.
tcpOutSackRetransSegs
Fires whenever a segment is retransmitted on a connection that has selective acknowledgement enabled.
tcpOutSegs
Fires whenever a segment is sent that contains at least one non-retransmitted byte.
tcpOutUrg
Fires whenever a segment is sent with the URG flag set, and with a valid urgent pointer.
tcpOutWinProbe
Fires whenever a window probe is sent.
tcpOutWinUpdate
Fires whenever a window update is sent.
tcpPassiveOpens
Fires whenever a TCP connections have made a direct transition to the SYN_RCVD state from the LISTEN state.
tcpRetransBytes
Fires whenever data is retransmitted. The number of bytes retransmitted is in args[0].
tcpRetransSegs
Fires whenever a segment is sent that contains one or more retransmitted bytes.
tcpRttNoUpdate
Fires whenever data was received, but there was no timestamp information available with which to update the RTT.
tcpRttUpdate
Fires whenever data was received containing the timestamp information necessary to update the RTT.
tcpTimKeepalive
Fires whenever timer-based keep-alive processing is performed on a connection.
tcpTimKeepaliveDrop
Fires whenever keep-alive processing results in termination of a connection.
tcpTimKeepaliveProbe
Fires whenever a keep-alive probe is sent out as a part of keep-alive processing.
tcpTimRetrans
Fires whenever timer-based retransmit processing is performed on a connection.
tcpTimRetransDrop
Fires whenever prolonged failure to perform timer-based retransmission results in termination of the connection.
Table 39  UDP mib Probes
Probe
Description
udpInCksumErrs
Fires whenever a datagram is discarded due to a bad UDP checksum.
udpInDatagrams
Fires whenever a UDP datagram is received.
udpInErrors
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.
udpInOverflows
Fires whenever a UDP datagram is received, but subsequently dropped due to lack of buffer space.
udpNoPorts
Fires whenever a UDP datagram is received on a port to which no socket is bound.
udpOutDatagrams
Fires whenever a UDP datagram is sent.
udpOutErrors
Fires whenever a UDP datagram is not sent due to some error condition, typically because the datagram was malformed in some way.

mib Probe Arguments

The sole argument for each mib probe has the same semantics: args[0] contains the value with which the counter is to be incremented. For most mib probes, args[0] always contains the value 1, but for some probes args[0] may take arbitrary positive values. For these probes, the meaning of args[0] is noted in the probe description.

mib Stability

The mib provider uses stability mechanism of DTrace to describe its stabilities, as shown in the following table. For more information about the stability mechanism, see DTrace Stability Mechanisms.

Table 40  Stability Mechanism for the mib Provider
Element
Name Stability
Data Stability
Dependency Class
Provider
Evolving
Evolving
ISA
Module
Private
Private
Unknown
Function
Private
Private
Unknown
Name
Evolving
Evolving
ISA
Arguments
Evolving
Evolving
ISA