mib Provider

{anchor:top}
h1. {anchor:CHP-MIB} {{mib}} Provider
The {{mib}} provider makes available probes that correspond to counters in the 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 [{{kstat}}(1M)|http://docs.sun.com/doc/819-2240/kstat-1m?a=view] and [{{netstat}}(1M)|http://docs.sun.com/doc/819-2240/netstat-1m?a=view] commands. The {{mib}} provider facilitates quick exploration of aberrant networking behavior that is observed using either remote or local networking monitors.

|ICMP|RFC 1213|{{icmp}}|[Table 28–2|#TBL-MIB-ICMP]|
|IP|RFC 1213|{{ip}}|[Table 28–3|#TBL-MIB-IP]|
|IPsec|—|{{ip}}|[Table 28–4|#TBL-MIB-IPSEC]|
|IPv6|RFC 2465|—|[Table 28–5|#TBL-MIB-IPV6]|
|SCTP|“SCTP MIB” (Internet draft)|{{sctp}}|[Table 28–7|#TBL-MIB-SCTP]|
|TCP|RFC 1213|{{tcp}}|[Table 28–8|#TBL-MIB-TCP]|
|UDP|RFC 1213|{{udp}}|[Table 28–9|#TBL-MIB-UDP]|
h6. {anchor:TBL-MIB-ICMP} ICMP {{mib}} Probes
|{{icmpInAddrMaskReps}}|Probe that fires whenever an ICMP Address Mask Reply message is received.|
|{{icmpInAddrMasks}}|Probe that fires whenever an ICMP Address Mask Request message is received.|
|{{icmpInBadRedirects}}|Probe that 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}}|Probe that fires whenever an ICMP message with a bad checksum is received.|
|{{icmpInDestUnreachs}}|Probe that fires whenever an ICMP Destination Unreachable message is received.|
|{{icmpInEchoReps}}|Probe that fires whenever an ICMP Echo Reply message is received.|
|{{icmpInEchos}}|Probe that fires whenever an ICMP Echo request message is received.|
|{{icmpInErrors}}|Probe that fires whenever an ICMP message is received that is determined to have an ICMP-specific error (bad ICMP checksum, bad length, etc.).|
|{{icmpInFragNeeded}}|Probe that 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 Don't Fragment flag was set.|
|{{icmpInMsgs}}|Probe that 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}}|Probe that fires whenever an ICMP message is received, but the message is subsequently dropped due to lack of buffer space.|
|{{icmpInParmProbs}}|Probe that fires whenever an ICMP Parameter Problem message is received.|
|{{icmpInRedirects}}|Probe that fires whenever an ICMP Redirect message is received.|
|{{icmpInSrcQuenchs}}|Probe that fires whenever an ICMP Source Quench message is received.|
|{{icmpInTimeExcds}}|Probe that fires whenever an ICMP Time Exceeded message is received.|
|{{icmpInTimestampReps}}|Probe that fires whenever an ICMP Timestamp Reply message is received.|
|{{icmpInTimestamps}}|Probe that fires whenever an ICMP Timestamp request message is received.|
|{{icmpInUnknowns}}|Probe that fires whenever an ICMP message of unknown type is received.|
|{{icmpOutAddrMaskReps}}|Probe that fires whenever an ICMP Address Mask Reply message is sent.|
|{{icmpOutDestUnreachs}}|Probe that fires whenever an ICMP Destination Unreachable message is sent.|
|{{icmpOutDrops}}|Probe that 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}}|Probe that fires whenever an ICMP Echo Reply message is sent.|
|{{icmpOutErrors}}|Probe that 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}}|Probe that fires whenever an ICMP Destination Unreachable (Fragmentation Needed) message is sent.|
|{{icmpOutMsgs}}|Probe that 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}}|Probe that fires whenever an ICMP Parameter Problem message is sent.|
|{{icmpOutRedirects}}|Probe that fires whenever an ICMP Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects.|
|{{icmpOutTimeExcds}}|Probe that fires whenever an ICMP Time Exceeded message is sent.|
|{{icmpOutTimestampReps}}|Probe that fires whenever an ICMP Timestamp Reply message is sent.|
h6. {anchor:TBL-MIB-IP} IP {{mib}} Probes
|{{ipForwDatagrams}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an IP datagram fragment is generated as a result of fragmentation.|
|{{ipFragFails}}|Probe that fires whenever an IP datagram is discarded because it could not be fragmented, for example, because fragmentation was required and the Don't Fragment flag was set.|
|{{ipFragOKs}}|Probe that fires whenever an IP datagram has been successfully fragmented.|
|{{ipInCksumErrs}}|Probe that fires whenever an input datagram is discarded due to a bad IP header checksum.|
|{{ipInDelivers}}|Probe that fires whenever an input datagram is successfully delivered to IP user protocols, including ICMP.|
|{{ipInDiscards}}|Probe that fires whenever an input IP 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.|
|{{ipInHdrErrors}}|Probe that 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}}|Probe that fires whenever an IPv6 packet erroneously arrives on an IPv4 queue.|
|{{ipInReceives}}|Probe that fires whenever a datagram is received from an interface, even if that datagram is received in error.|
|{{ipInUnknownProtos}}|Probe that fires whenever a locally addressed datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol.|
|{{ipOutDiscards}}|Probe that 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}}|Probe that fires whenever an IPv6 packet is sent over an IPv4 connection.|
|{{ipOutNoRoutes}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever a connection changes from using IPv4 to using IPv6 as its IP protocol.|
|{{ipReasmDuplicates}}|Probe that fires whenever the IP reassembly algorithm determines that an IP fragment contains _only_ previously received data.|
|{{ipReasmFails}}|Probe that 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}}|Probe that fires whenever an IP datagram is successfully reassembled.|
|{{ipReasmPartDups}}|Probe that fires whenever the IP reassembly algorithm determines that an IP fragment contains both some previously received data and some new data.|
|{{ipReasmReqds}}|Probe that fires whenever an IP fragment is received that needs to be reassembled.|
h6. {anchor:TBL-MIB-IPSEC} IPsec {{mib}} Probes
|{{ipsecInFailed}}|Probe that fires whenever a received packet is dropped because it fails to match the specified IPsec policy.|
|{{ipsecInSucceeded}}|Probe that fires whenever a received packet matches the specified IPsec policy and processing is allowed to continue.|
h6. {anchor:TBL-MIB-IPV6} IPv6 {{mib}} Probes
|{{ipv6ForwProhibits}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is received.|
|{{ipv6IfIcmpInBadNeighborAdvertisements}}|Probe that fires whenever an ICMPv6 Neighbor Advertisement message is received that is malformed in some way.|
|{{ipv6IfIcmpInBadNeighborSolicitations}}|Probe that fires whenever an ICMPv6 Neighbor Solicit message is received that is malformed in some way.|
|{{ipv6IfIcmpInBadRedirects}}|Probe that fires whenever an ICMPv6 Redirect message is received that is malformed in some way.|
|{{ipv6IfIcmpInDestUnreachs}}|Probe that fires whenever an ICMPv6 Destination Unreachable message is received.|
|{{ipv6IfIcmpInEchoReplies}}|Probe that fires whenever an ICMPv6 Echo Reply message is received.|
|{{ipv6IfIcmpInEchos}}|Probe that fires whenever an ICMPv6 Echo request message is received.|
|{{ipv6IfIcmpInErrors}}|Probe that 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}}|Probe that fires whenever an ICMPv6 Group Membership Query message is received that is malformed in some way.|
|{{ipv6IfIcmpInGroupMembBadReports}}|Probe that fires whenever an ICMPv6 Group Membership Report message is received that is malformed in some way.|
|{{ipv6IfIcmpInGroupMembOurReports}}|Probe that fires whenever an ICMPv6 Group Membership Report message is received.|
|{{ipv6IfIcmpInGroupMembQueries}}|Probe that fires whenever an ICMPv6 Group Membership Query message is received.|
|{{ipv6IfIcmpInGroupMembReductions}}|Probe that fires whenever an ICMPv6 Group Membership Reduction message is received.|
|{{ipv6IfIcmpInGroupMembResponses}}|Probe that fires whenever an ICMPv6 Group Membership Response message is received.|
|{{ipv6IfIcmpInGroupMembTotal}}|Probe that fires whenever an ICMPv6 multicast listener discovery message is received.|
|{{ipv6IfIcmpInMsgs}}|Probe that 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}}|Probe that fires whenever an ICMPv6 Neighbor Advertisement message is received.|
|{{ipv6IfIcmpInNeighborSolicits}}|Probe that fires whenever an ICMPv6 Neighbor Solicit message is received.|
|{{ipv6IfIcmpInOverflows}}|Probe that fires whenever an ICMPv6 message is received, but that message is subsequently dropped due to lack of buffer space.|
|{{ipv6IfIcmpInParmProblems}}|Probe that fires whenever an ICMPv6 Parameter Problem message is received.|
|{{ipv6IfIcmpInRedirects}}|Probe that fires whenever an ICMPv6 Redirect message is received.|
|{{ipv6IfIcmpInRouterAdvertisements}}|Probe that fires whenever an ICMPv6 Router Advertisement message is received.|
|{{ipv6IfIcmpInRouterSolicits}}|Probe that fires whenever an ICMPv6 Router Solicit message is received.|
|{{ipv6IfIcmpInTimeExcds}}|Probe that fires whenever an ICMPv6 Time Exceeded message is received.|
|{{ipv6IfIcmpOutAdminProhibs}}|Probe that fires whenever an ICMPv6 Destination Unreachable (Communication Administratively Prohibited) message is sent.|
|{{ipv6IfIcmpOutDestUnreachs}}|Probe that fires whenever an ICMPv6 Destination Unreachable message is sent.|
|{{ipv6IfIcmpOutEchoReplies}}|Probe that fires whenever an ICMPv6 Echo Reply message is sent.|
|{{ipv6IfIcmpOutEchos}}|Probe that fires whenever an ICMPv6 Echo message is sent.|
|{{ipv6IfIcmpOutErrors}}|Probe that 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}}|Probe that fires whenever an ICMPv6 Group Membership Query message is sent.|
|{{ipv6IfIcmpOutGroupMembReductions}}|Probe that fires whenever an ICMPv6 Group Membership Reduction message is sent.|
|{{ipv6IfIcmpOutGroupMembResponses}}|Probe that fires whenever an ICMPv6 Group Membership Response message is sent.|
|{{ipv6IfIcmpOutMsgs}}|Probe that 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}}|Probe that fires whenever an ICMPv6 Neighbor Advertisement message is sent.|
|{{ipv6IfIcmpOutNeighborSolicits}}|Probe that fires whenever an ICMPv6 Neighbor Solicitation message is sent.|
|{{ipv6IfIcmpOutParmProblems}}|Probe that fires whenever an ICMPv6 Parameter Problem message is sent.|
|{{ipv6IfIcmpOutPktTooBigs}}|Probe that fires whenever an ICMPv6 Packet Too Big message is sent.|
|{{ipv6IfIcmpOutRedirects}}|Probe that fires whenever an ICMPv6 Redirect message is sent. For a host, this probe will never fire, because hosts do not send redirects.|
|{{ipv6IfIcmpOutRouterAdvertisements}}|Probe that fires whenever an ICMPv6 Router Advertisement message is sent.|
|{{ipv6IfIcmpOutRouterSolicits}}|Probe that fires whenever an ICMPv6 Router Solicit message is sent.|
|{{ipv6IfIcmpOutTimeExcds}}|Probe that fires whenever an ICMPv6 Time Exceeded message is sent.|
|{{ipv6InAddrErrors}}|Probe that 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}}|Probe that fires whenever an input datagram is successfully delivered to IPv6 user-protocols (including ICMPv6).|
|{{ipv6InDiscards}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an IPv4 packet erroneously arrives on an IPv6 queue.|
|{{ipv6InMcastPkts}}|Probe that fires whenever a multicast IPv6 packet is received.|
|{{ipv6InNoRoutes}}|Probe that 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}}|Probe that fires whenever an IPv6 datagram is received from an interface, even if that datagram is received in error.|
|{{ipv6InTooBigErrors}}|Probe that fires whenever a fragment is received that is larger than the maximum fragment size.|
|{{ipv6InTruncatedPkts}}|Probe that fires whenever an input datagram is discarded because the datagram frame didn't carry enough data.|
|{{ipv6InUnknownProtos}}|Probe that fires whenever a locally-addressed IPv6 datagram is received successfully but subsequently discarded because of an unknown or unsupported protocol.|
|{{ipv6OutDiscards}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an IPv6 datagram fragment is generated as a result of fragmentation.|
|{{ipv6OutFragFails}}|Probe that fires whenever an IPv6 datagram is discarded because it could not be fragmented, for example, because its Don't Fragment flag was set.|
|{{ipv6OutFragOKs}}|Probe that fires whenever an IPv6 datagrams has been successfully fragmented.|
|{{ipv6OutIPv4}}|Probe that fires whenever an IPv6 packet is sent over an IPv4 connection.|
|{{ipv6OutMcastPkts}}|Probe that fires whenever a multicast packet is sent.|
|{{ipv6OutNoRoutes}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever a connection changes from using IPv6 to using IPv4 as its IP protocol.|
|{{ipv6ReasmDuplicates}}|Probe that fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains _only_ previously received data.|
|{{ipv6ReasmFails}}|Probe that 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}}|Probe that fires whenever an IPv6 datagram is successfully reassembled.|
|{{ipv6ReasmPartDups}}|Probe that fires whenever the IPv6 reassembly algorithm determines that an IPv6 fragment contains both some previously received data and some new data.|
|{{ipv6ReasmReqds}}|Probe that fires whenever an IPv6 fragment is received that needs to be reassembled.|
h6. {anchor:TBL-MIB-RAWIP} Raw IP {{mib}} Probes
|{{rawipInCksumErrs}}|Probe that fires whenever a raw IP packet is received that has a bad IP checksum.|
|{{rawipInDatagrams}}|Probe that fires whenever a raw IP packet is received.|
|{{rawipInErrors}}|Probe that fires whenever a raw IP packet is received that is malformed in some way.|
|{{rawipInOverflows}}|Probe that fires whenever a raw IP packet is received, but that packet is subsequently dropped due to lack of buffer space.|
|{{rawipOutDatagrams}}|Probe that fires whenever a raw IP packet is sent.|
|{{rawipOutErrors}}|Probe that 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.|
h6. {anchor:TBL-MIB-SCTP} SCTP {{mib}} Probes
|{{sctpAborted}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an SCTP packet is received from peers with an invalid checksum.|
|{{sctpCurrEstab}}|Probe that 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}}|Probe that fires whenever a user message has to be fragmented because of the MTU.|
|{{sctpInClosed}}|Probe that fires whenever data is received on a closed SCTP association.|
|{{sctpInCtrlChunks}}|Probe that 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}}|Probe that fires whenever a duplicate ACK is received.|
|{{sctpInInvalidCookie}}|Probe that fires whenever an invalid cookie is received.|
|{{sctpInOrderChunks}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an incoming connection is dropped for any reason.|
|{{sctpOutAck}}|Probe that fires whenever a selective acknowledgement is sent.|
|{{sctpOutAckDelayed}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever a window probe is sent.|
|{{sctpOutWinUpdate}}|Probe that fires whenever a window update is sent.|
|{{sctpPassiveEstab}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever an SCTP association is aborted due to failure to receive a heartbeat acknowledgement.|
|{{sctpTimHeartBeatProbe}}|Probe that fires whenever an SCTP heartbeat is sent.|
|{{sctpTimRetrans}}|Probe that fires whenever timer-based retransmit processing is performed on an association.|
|{{sctpTimRetransDrop}}|Probe that fires whenever prolonged failure to perform timer-based retransmission results in the association being aborted.|
h6. {anchor:TBL-MIB-TCP} TCP {{mib}} Probes
|{{tcpActiveOpens}}|Probe that fires whenever a TCP connection makes a direct transition from the CLOSED state to the SYN_SENT state.|
|{{tcpAttemptFails}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever a TCP connection makes the direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE_WAIT state.|
|{{tcpHalfOpenDrop}}|Probe that fires whenever a connection is dropped due to a full queue of connections in the SYN_RCVD state.|
|{{tcpInAckBytes}}|Probe that fires whenever an ACK is received for previously sent data. The number of bytes acknowledged is passed in {{args\[0\]}}.|
|{{tcpInAckSegs}}|Probe that fires whenever an ACK is received for a previously sent segment.|
|{{tcpInAckUnsent}}|Probe that fires whenever an ACK is received for an unsent segment.|
|{{tcpInClosed}}|Probe that fires whenever data was received for a connection in a closing state.|
|{{tcpInDataDupBytes}}|Probe that 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}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever a segment is received such that _all_ data prior to the new segment's sequence number has been previously received.|
|{{tcpInDataPartDupBytes}}|Probe that 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}}|Probe that 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}}|Probe that fires whenever data is received that lies past the current receive window. The number of bytes is in {{args\[0\]}}.|
|{{tcpInDataPastWinSegs}}|Probe that fires whenever a segment is received that lies past the current receive window.|
|{{tcpInDataUnorderBytes}}|Probe that 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}}|Probe that fires whenever a segment is received such that some data prior to the new data's sequence number is missing.|
|{{tcpInDupAck}}|Probe that fires whenever a duplicate ACK is received.|
|{{tcpInErrs}}|Probe that fires whenever a TCP error (for example, a bad TCP checksum) is found on a received segment.|
|{{tcpInSegs}}|Probe that fires whenever a segment is received, even if that segment is later found to have an error that prevents further processing.|
|{{tcpInWinProbe}}|Probe that fires whenever a window probe is received.|
|{{tcpInWinUpdate}}|Probe that fires whenever a window update is received.|
|{{tcpListenDrop}}|Probe that fires whenever an incoming connection is dropped due to a full listen queue.|
|{{tcpListenDropQ0}}|Probe that fires whenever a connection is dropped due to a full queue of connections in the SYN_RCVD state.|
|{{tcpOutAck}}|Probe that fires whenever an ACK is sent.|
|{{tcpOutAckDelayed}}|Probe that fires whenever an ACK is sent after having been initially delayed.|
|{{tcpOutControl}}|Probe that fires whenever a SYN, FIN, or RST is sent.|
|{{tcpOutDataBytes}}|Probe that fires whenever data is sent. The number of bytes sent is in {{args\[0\]}}.|
|{{tcpOutDataSegs}}|Probe that fires whenever a segment is sent.|
|{{tcpOutFastRetrans}}|Probes that fires whenever a segment is retransmitted as part of the fast retransmit algorithm.|
|{{tcpOutRsts}}|Probe that fires whenever a segment is sent with the RST flag set.|
|{{tcpOutSackRetransSegs}}|Probe that fires whenever a segment is retransmitted on a connection that has selective acknowledgement enabled.|
|{{tcpOutSegs}}|Probe that fires whenever a segment is sent that contains at least one non-retransmitted byte.|
|{{tcpOutUrg}}|Probe that fires whenever a segment is sent with the URG flag set, and with a valid urgent pointer.|
|{{tcpOutWinProbe}}|Probe that fires whenever a window probe is sent.|
|{{tcpOutWinUpdate}}|Probe that fires whenever a window update is sent.|
|{{tcpPassiveOpens}}|Probe that fires whenever a TCP connections have made a direct transition to the SYN_RCVD state from the LISTEN state.|
|{{tcpRetransBytes}}|Probe that fires whenever data is retransmitted. The number of bytes retransmitted is in {{args\[0\]}}.|
|{{tcpRetransSegs}}|Probe that fires whenever a segment is sent that contains one or more retransmitted bytes.|
|{{tcpRttNoUpdate}}|Probe that fires whenever data was received, but there was no timestamp information available with which to update the RTT.|
|{{tcpRttUpdate}}|Probe that fires whenever data was received containing the timestamp information necessary to update the RTT.|
|{{tcpTimKeepalive}}|Probe that fires whenever timer-based keep-alive processing is performed on a connection.|
|{{tcpTimKeepaliveDrop}}|Probe that fires whenever keep-alive processing results in termination of a connection.|
|{{tcpTimKeepaliveProbe}}|Probe that fires whenever a keep-alive probe is sent out as a part of keep-alive processing.|
|{{tcpTimRetrans}}|Probe that fires whenever timer-based retransmit processing is performed on a connection.|
|{{tcpTimRetransDrop}}|Probe that fires whenever prolonged failure to perform timer-based retransmission results in termination of the connection.|
h6. {anchor:TBL-MIB-UDP} UDP {{mib}} Probes
|{{udpInCksumErrs}}|Probe that fires whenever a datagram is discarded due to a bad UDP checksum.|
|{{udpInDatagrams}}|Probe that fires whenever a UDP datagram is received.|
|{{udpInErrors}}|Probe that 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}}|Probe that fires whenever a UDP datagram is received, but subsequently dropped due to lack of buffer space.|
|{{udpNoPorts}}|Probe that fires whenever a UDP datagram is received on a port to which no socket is bound.|
|{{udpOutDatagrams}}|Probe that fires whenever a UDP datagram is sent.|
|{{udpOutErrors}}|Probe that fires whenever a UDP datagram is not sent due to some error condition, typically because the datagram was malformed in some way.|

[Top|#top]
h2. {anchor:CHP-MIB-1} 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.

[Top|#top]
h2. {anchor:CHP-MIB-STABILITY} Stability
The {{mib}} provider uses DTrace's stability mechanism to describe its stabilities, as shown in the following table. For more information about the stability mechanism, see [Chapter 39, Stability|Stability].
||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|
{excerpt:hidden=true}Converted by tech dogg's sgml2wiki on Tue 20 Nov 2007 at 9:25:03 PM{excerpt}