Thursday, 21 September 2017

some notes about solaris zfs (oracle version)

zfs_vdev_max_queue_wait is a factor used to trigger I/O starvation avoidance behavior. Used in conjunction with zfs_vdev_max_pending to track the earliest I/O that has been issued.
If more than zfs_vdev_max_queue_wait full pending queues have been issued since, this I/O is being starved. Don't accept any more I/Os. This will drain the pending queue until the starved I/O is processed.

spa_mode_global is used to define the mode in which given zpool can be initialized internally by ZFS, typically used as READ/WRITE mode.

zfs_flags are used to control the level of debugging that ZFS can use.


Saturday, 15 July 2017

How to change logical block size for sas disk.

change logical block size:
sg_format --format --size 4096 /dev/rdsk/c0t5000CCA02C4015E4d0


change lba size:
sg_format --resize --count=0x2321 /dev/rdsk/c0t5000CCA02C4015E4d0


refresh drive information (solaris):
update_drv -fv sd

Wednesday, 5 July 2017

netstat -s : Information and notes

RAWIP.
RawipInDatagramsThe total number of RAWIP datagrams sent upstream. (counter)
rawipInCksumErrsThe number of RAWIP packets with bad IPV6_CHECKSUM checksum. (counter)
rawipInErrorsThe number of recv'd datagrams Not deliverable (other). (counter)
RawipOutDatagramsThe total number of datagrams sent. (counter)
rawipOutErrorsThe total number of datagrams Not sent (e.g. no memory). (counter)



UDP.
UdpInDatagramsThe total number of UDP datagrams delivered to UDP users. (counter)
udpInErrorsThe number of received UDP datagrams that could not be delivered for reasons other
than the lack of an application at the destination port. (counter)
UdpOutDatagramsThe total number of UDP datagrams sent from this entity. (counter)
udpOutErrorsThe number of UDP datagrams not sent. (counter)

TCP.
tcpRtoAlgorithmThe algorithm used for retransmit timeout - should display 4 ( Integer )
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.(Integer)
other (1) none of the following,
constant (2) a constant rto ,
rsre (3) MIL-STD-1778, Appendix B ,
vanj (4) Van Jacobson's algorithim **( Solaris)
tcpRtoMinThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. (Integer , default is 400 ms )
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
see: # ndd /dev/tcp tcp_rexmit_interval_min
tcpRtoMaxThe maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. (Integer , default is 60000ms )
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
see: # ndd /dev/tcp tcp_rexmit_interval_max
tcpMaxConnThe 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.(dynamic)
tcpActiveOpensThe number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. The outgoing calls you make are called Active Opens. You decide who to call and why. An outgoing rlogin, or Web browser request causes an active open. (counter)
tcpPassiveOpensThe number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. (counter )
The incoming calls are called Passive Opens as they occur without any activity on your part. In this case, you just have to have a program running that is waiting to pick up the phone. For exampl,e a Web server listens on port 80 for any incoming requests.
tcpAttemptFailsThe number of failed connection attempts. (counter)
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. The tcpAttemptFails increments on outgoing connections when a reset is received and we have sent a syn, or if the connection times out after a syn is sent.
On an incoming connection, it increments if we receive a syn and then send one, but do not get a response, or get a reset.
tcpEstabResetsThe number of connection resets. (client ungracefully shut downs ). (counter)
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.
tcpCurrEstabThe number of connections open, ESTAB or CLOSE_WAIT, (Gauge)
Each connection can last a few milliseconds (for a Web server on a local LAN running a benchmark) or many seconds or minutes (for a large transfer on a slow Internet connection). Each established connection will use up a process or a thread in your system. The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT. see:
ESTABLISHED displayed with # netstat -P tcp
tcpOutSegsThe total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. (counter)
tcpOutDataSegsThe number of TCP segments sent. (counter)
The total number of segments (tcpOutSegs) is mostly made up of tcpOutDataSegs and tcpOutAck, although the numbers don't add up exactly. The outgoing data is divided into segments, where each segment corresponds to an Ethernet packet.
tcpOutDataBytesThe number of data bytes sent. (counter)
tcpRetransSegsThe total number of segments retransmitted is the number of TCP segments transmitted containing one or more previously transmitted octets. If no acknowledgment is received, the segment is retransmitted. (counter)
see Doc 1009001.1 Note: An excessive number of TCP retransmissions indicates that client accessing your server have slow or error-prone connections. Retransmissions consume bandwidth that might otherwise go to serving new connections.
tcpRetransBytesThe number of data bytes retransmitted. (counter)
tcpOutAckThe number of acknowledgement only packets sent. (counter)
tcpOutAckDelayedThe number of delayed acknowledgements sent. (counter)
see: # ndd/dev/tcp tcp_deferred_ack_interval
tcpOutUrgThe number of packets sent with the URGENT flag. (counter)
tcpOutWinUpdateThe number of window update only packets sent. (counter)
tcpOutWinProbeThe number of window probes sent. (counter)
tcpOutControlThe number of control - SYN, FIN, RST packets sent. (counter)
tcpOutRstsThe number of connection resets . client requesting non-listening port. (counter)
The number of TCP segments sent containing the RST flag.
tcpOutFastRetransThe number of TCP segments sent with the URGENT flag only. (counter)
tcpInSegsThe number of segments received on TCP connections. (counter)
The total number of segments received, including those received inerror. This count includes segments received on currently established connections.
tcpInAckSegsThe number of ack only packets recv. (counter)
tcpInAckBytesThe number of bytes ack by received ack packets. (counter)
tcpInDupAckThe number of duplicate ack only packets recv. (counter) Almost every dropped packet will trigger some duplicate acks. and you get them if packets arrive out of order
tcpInAckUnsentThe number of acknowledgements received for unsent data. (counter)
tcpInInorderSegsThe number of packets received in sequence. (counter)
tcpInInorderBytesThe number of bytes received in sequence. (counter)
tcpInUnorderSegsThe number of packets received out of order. (counter)
tcpInUnorderBytesThe number of bytes received, out of order pkts. (counter)
tcpInDupSegsThe number of completely duplicate packets. this is a counter.
tcpInDupBytesThe number of completely duplicate bytes received. (counter)
tcpInPartDupSegsThe number of packets w some duplicate data. (counter)
tcpInPartDupBytesThe number of dup bytes received w some duplicate data. (counter)
tcpInPastWinSegsThe number of segments received after window. (counter)
It is the number of segments received outside of the window -- when the window is non-zero. Note: Segments received when the window is zero are considered probes.
A high number indicates this system has peers that aren't very good at arithmetic.
tcpInPastWinBytesThe number of bytes received after window. (counter)
A large value could actually mean that the peer isn't following the tcp window size of this system. It likely means that your peers don't implement TCP properly.
tcpInWinProbeThe number of window update packets received. (counter) Segments received when the window is zero.
tcpInWinUpdateThe number of window update packets received. (counter)
tcpInClosedThe number of connections closed, including drops. (counter)
tcpRttNoUpdateThe number of times unsuccessful getting RTT. (counter)
tcpRttUpdateThe number of times successful getting round trip time. (counter)
tcpTimRetransThe number of retransmission timeouts. (counter)
tcpTimRetransDropThe number of connections dropped due to retrans timeout. (counter).
The tcpTimRetransDrop parameter shows the number of aborts since boot time due to abort timer expirations. This count includes both SYN requests and established TCP connections.
tcpTimKeepaliveThe number of of keep alive timeouts. (counter)
tcpTimKeepaliveProbeThe number of keep alive probes sent. (counter)
tcpTimKeepaliveDropThe number of connections dropped in keep alive. (counter)
tcpListenDropThe number of connections refused due to backlog full on listen.
the listen queue length is the minimum of tcp_conn_req_max_q and the qlen value passed to listen().
see: # ndd /dev/tcp tcp_conn_req_max_q
tcpListenDropQ0The number of connections refused due to half-open queue (q0) full
see: # ndd /dev/tcp tcp_conn_req_max_q0
tcpHalfOpenDropThe number of connections dropped from a full half-open queue (q0)
see above
tcpOutSackRetransThe number of retransmitted segments by SACK retransmission
if sack enabled
see: # ndd /dev/tcp tcp_sack_permitted

IPv4.
ipForwardingIndication if packet forwarding is enabled. (Integer)
it is the same as ndd /dev/ip ip_forwarding except this variable displays 0 or 1 with ndd,
and 1 or 2 with netstat
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 via the host).
see: # ndd /dev/ip ip_forwarding ( 0=no, 1 =yes )
ipDefaultTTLipDefaultTTL default time-to-live. (variable.)
The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
see: # ndd /dev/ip ip_def_ttl ( defaults to 255)
ipInReceivesThe total number of input datagrams received from interfaces, including those received in error. (counter)
ipInHdrErrorsThe number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. (counter)
ipInAddrErrorsThe number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. (counter) This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., 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.
ipInCksumErrsThe number of IP CheckSum Errors. (counter)
ipForwDatagramsThe number of attempts made to forward. (counter)
The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.
should be Zero unless ip_forwarding is enabled(system is a router)
ipForwProhibitsThe number of packets not forwarded due to adminstrative reasons (counter)
ipInUnknownProtosThe number of datagram discards for unknown protocol. (counter)
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
ipInDiscardsThe number of datagram discards of good datagram's. (counter)
The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. This may indicate a low buffer problem or not enough cpu horsepower to process incoming packets. Incremented when:
We need to forward the packet but the interface we need to forward to is down
We have a broadcast to forward but directed brodcasts is disabled.
ipInDeliversipInDelivers # of datagrams delivered. (counter) The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
ipOutRequestsThe total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. (counter)
Note that this counter does not include any datagrams counted in ipForwDatagrams.
ipOutDiscardsThe number of good outgoing datagrams dicarded. (counter)
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space).
Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
ipOutNoRoutesThe number discarded due to no route to destination (counter)
The number of IP datagrams discarded because no route could be found to transmit them to their destination.
Note1: this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion.
Note2: that this includes any datagrams which a host cannot route because all of its default routers are down.
ipReasmTimeoutThe number of IP reassembly timeout, in secs. (this is a variable.)
The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
ipReasmReqdsThe number of IP fragments needing reassembly received. (counter)
The number of IP fragments received which needed to be reassembled at this entity.
ipReasmOKsThe number of datagrams reassembled. (counter)
The number of IP datagrams successfully re-assembled.
ipReasmFailsThe number of reassembly failures. (counter)
The number of failures detected by the IP re- assembly algorithm (for whatever reason: timed out, errors, etc).
Note: 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.
ipReasmDuplicatesThe number of reassembly with duplcate data. (counter)
( # of complete duplicates in reassembly )
ipReasmPartDupsThe number of reassembly with some duplicate data. (counter)
(# of partial duplicates in reassembly )
ipFragOKsThe number of datagrams fragmented successful. (counter)
The number of IP datagrams that have been successfully fragmented at this entity.
ipFragFailsThe number of datagrams discarded, frag failed. (counter)
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc).
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.
ipFragCreatesThe number of fragments created. (counter)
The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
ipRoutingDiscardsThe number of number received datagrams not delivered. (counter)
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 free-up buffer space for other routing entries.
tcpInErrsThe number of TCP segments discarded format error. (counter)
The total number of segments received in error (e.g., bad TCP checksums).
udpNoPortsThe number of datagrams discarded, no local port -(counter)
Something is sending UDP packets to this machine (or to a multicast or the broadcast) to a port number which this machine does not have anyone listening on.
The udpNoPorts object counter should increase by 1 for each message specifying an unknown UDP port received by the UDP layer.
The total number of received UDP datagrams for which there was no application at the destination port.
This is commonly caused by UDP broadcast pkts to netbios port.
udpInCksumErrsThe number of of UDP packets with bad UDP checksums. (counter)
Incorrect UDP checksums in UDP header.
udpInOverflowsThe number of UDP packets droped due to queue overflow. (counter)
A UDP socket overflow is when a UDP packet arrived for a port and buffer space allocatedfor that port was full. So, the UDP driver had to discard the packet because there was no space.
The size can be set with the SO_RCVBUF setsockopt() option.
It defaults to ` ndd /dev/udp udp_recv_hiwat `.
Basically, udpInOverflows is bumped every time IP cannot pass a message upstream to a client udp stream.on highspeed interfaces, such as HIPPI or gigabit , the buffers can be increased very high
see : # ndd set /dev/udp udp_xmit_hiwat 1045876
# ndd set /dev/udp udp_recv_hiwat 1045876
rawipInOverflowsThe number of RAW IP packets (all IP protocols except UDP, TCP and ICMP) droped due to queue overflow (counter)
Note: udp_max_buf by default is 256k in 2.5.1, use setsockopt() function and set the SO_SNDBUF and SO_RCVBUF (on sender and receiver code) sizes to Max, which is 64K
ipsecInSucceededThe number of incoming packets that succeeded policy checks (counter)
ipsecInFailedThe number of incoming packets that failed policy checks (counter)
ipInIPv6The number of IPv6 packets received by IPv4 and dropped (counter)
ipOutIPv6The number of IPv6 packets transmitted by ip_wput (counter)
ipOutSwitchIPv6The number of times ip_wput has switched to become ip_wput_v6 (counter)

IPv6.
ipv6ForwardingIpv6Forwarding ( Integer)
Forwarding (1), -- acting as a router
notForwarding (2) -- NOT acting as a router
The indication of whether this entity is acting as an IPv6 router in respect to the forwarding of datagrams received by, but not addressed to, this entity. IPv6 routers forward datagrams. Ipv6 hosts do not (except those source-routed via the host).
Note, that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `wrongValue' response if a management station attempts to change this object to an inappropriate value.
see: # ndd /dev/ip ip6_forwarding
ipv6DefaultHopLimitTime to Live field was renamed Hop Limit in Ipv6. ( Integer)
The default value inserted into the Hop Limitfield of the IPv6 header of datagrams originated at this entity, whenever a Hop Limit value is not supplied by the transport layer protocol.
see : # ndd /dev/ip ip6_def_hops ( defaults to 255 )
ipv6InReceivesThe total number of input datagrams received by the interface, including those received in error.(counter)
ipv6InHdrErrorsThe number of input datagrams discarded due to errors in their IPv6 headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IPv6 options, etc. (counter)
ipv6InTooBigErrorsThe number of input datagrams that could not be forwarded because their size exceeded the link MTU of outgoing interface.(counter)
ipv6InNoRoutesThe number of input datagrams discarded because no route could be found to transmit them to their destination.( counter)
ipv6InAddrErrorsThe number of input datagrams discarded because the IPv6 address in their IPv6 header's destination field was not a valid address to be received at this entity. (counter)
This count includes invalid addresses (e.g., ::0) and unsupported addresses (e.g., addresses with unallocated prefixes). For entities which are not IPv6 routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
ipv6InUnknownProtosThe number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.(counter)
This counter is incremented at the interface to which these datagrams were addressed which might not be necessarily the input interface for some of the datagrams.
ipv6InTruncatedPktsThe number of input datagrams discarded because datagram frame didn't carry enough data.(counter)
ipv6InDiscardsThe number of input IPv6 datagrams for which no problems were encountered to prevent their continued processing, but which were discarded e.g., for lack of buffer space). (counter)
Note that this counter does not include any datagrams discarded while awaiting re-assembly.
ipv6InDeliversThe total number of datagrams successfully delivered to IPv6 user-protocols (including ICMP). (counter)
This is incremented at the interface to which these datagrams were addressed which might not be necessarily the input interface for some of the datagrams.
ipv6OutForwDatagramsThe number of output datagrams which this entity received and forwarded to their final destinations.(counter)
In entities which do not act only those packets which were Source-Routed via this entity, and the Source-Route processing was successful.
Note, that for a successfully forwarded datagram the counter of the outgoing interface is incremented.
ipv6OutRequestsThe total number of IPv6 datagrams which local Ipv6 user-protocols (including ICMP) supplied to IPv6 in requests for transmission. (counter)
Note that this counter does not include any datagrams counted in ipv6IfStatsOutForwDatagrams.
ipv6OutDiscardsThe number of output IPv6 datagrams for which no
problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). (counter)
Note that this counter would include datagrams counted in ipv6IfStatsOutForwDatagrams if any such packets met this (discretionary) discard criterion.
ipv6OutNoRoutesThe number of discarded due to no route to destination (counter)
ipv6OutFragOKsThe number of IPv6 datagrams that have been successfully fragmented at this output interface.(counter)
ipv6OutFragFailsThe number of IPv6 datagrams that have been discarded because they needed to be fragmented at this output interface but could not be.(counter)
ipv6OutFragCreatesThe number of output datagram fragments that have been generated as a result of fragmentation at this output interface.(counter)
ipv6ReasmReqdsThe number of IPv6 fragments received which needed to be reassembled at this interface. (counter)
Note, that this counter is incremented at the interface to which these fragments were addressed which might not be the input interface for some of the fragments.
ipv6ReasmOKsThe number of IPv6 datagrams successfully reassembled. (counter)
Note, that this counter is incremented at the interface to which these datagrams were addressed which might not be the input interface for some of the fragments.
ipv6ReasmFailsThe number of failures detected by the IPv6 re- assembly algorithm (for whatever reason: timed out, errors, etc.). (counter)
Note, that this is not necessarily a count of discarded IPv6 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.
This counter is incremented at the interface to which these fragments were addressed. This might not be the input interface for some of the fragments.
ipv6InMcastPktsThe number of ipv6 multicast packets received by the interface (counter)
ipv6OutMcastPktsThe number of ipv6 multicast packets transmitted by the interface (counter)
ipv6ReasmDuplicatesThe number of complete duplicates in reassembly. (counter)
ipv6ReasmPartDupsThe number of partial duplicates in reassembly. (counter)
ipv6ForwProhibitsThe number of packets not forwarded due to adminstrative reasons.(counter)
udpInCksumErrsudpInCksumErrs the number of UDP packets with bad UDP checksums. (counter)
see: ndd /dev/udp upd_do_checksum
udpInOverflowsThe number of RAW IPv6 packets (all IPv6 protocols except UDP, TCP and ICMPv6) dropped due to queue overflow (counter)
rawipInOverflowsThe number of RAW IP packets (all IP protocols except UDP, TCPand ICMP) dropped due to queue overflow. (counter)
This counter is incremented in IP layer, as netstat shows, when IP can not put another packet to send up stream on the Q. (counter)
ipv6InIPv4The number of IPv4 packets received by IPv6 and dropped. (counter)
ipv6OutIPv4The number of IPv4 packets transmitted by ip_wput_wput. (counter)
ipv6OutSwitchIPv4The number of times ip_wput_v6 has switched to become ip_wput. (counter)

ICMPv4 
icmpInMsgsThe total number of ICMP messages which the entity received. (counter)
Note: That this counter includes all those counted by icmpInErrors.
icmpInErrorsThe number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.). (counter)
icmpInCksumErrsThe number of bad packets with checksum errors. (counter)
icmpInUnknownsIcmp Unknown messages
icmpInDestUnreachsThe number of ICMP Destination Unreachable messages received.(counter)
icmpInTimeExcdsThe number of ICMP Time Exceeded messages received. TTL is zero - icmp type 11 code 1: (counter)
icmpInParmProbsThe number of ICMP Parameter Problem messages received. (counter)
icmpInSrcQuenchsThe number of ICMP Source Quench messages received. (counter)
icmpInRedirectsThe number of ICMP redirects received. ``icmp redirect'' messages. (counter)
icmpInBadRedirectsThe number of received ICMP redirect messages that are bad thus ignored.
icmpInEchosThe number of ICMP echo requests received. ``echo request'' messages. (counter)
icmpInEchoRepsThe number of ICMP Echo Reply messages received. (counter)
icmpInTimestampsThe number of ICMP Timestamp requests received. ``time stamp'' messages. (counter)
icmpInTimestampRepsThe number of ICMP Timestamp Reply messages received. (counter)
icmpInAddrMasksThe number of ICMP Address Mask Requests messages received. ``addr mask request'' messages . (counter)
icmpInAddrMaskRepsThe number of ICMP Address Mask Reply messages received. (counter)
icmpInFragNeededThe number of fragments received needing reassembly. (counter)
icmpOutMsgsThe total number of ICMP messages which this entity attempted to send. (counter)
icmpOutDropsThe number of total ICMP messages dropped. (counter)
It is also known as the number of messages not sent since original packet was broadcast/multicast or an ICMP error packet
Normal to get high value on networks using RIP.
icmpOutErrorsThe number of ICMP messages not sent due to errors. (counter)
It is also known as 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 this counter's value.
icmpOutDestUnreachsThe number of ICMP Destination Unreachable messages sent. (counter)
icmpOutTimeExcdsThe number of ICMP Time Exceeded messages sent. TTL is equal to zero = icmp type 11 code 0. (counter)
icmpOutParmProbsThe number of ICMP Parameter Problem messages sent. (counter)
icmpOutSrcQuenchsThe number of ICMP Source Quench messages sent. (counter)
icmpOutRedirectsThe number of ICMP Redirect messages sent. (counter) For a host, this object will always be zero, since hosts do not send redirects.
icmpOutEchosThe number of ICMP Echo (request) messages sent. (counter)
icmpOutEchoRepsThe number of ICMP Echo Reply messages sent. (counter)
icmpOutTimestampsThe number of ICMP Timestamp (request) messages sent. (counter)
icmpOutTimestampRepsThe number of ICMP Timestamp Reply messages sent. (counter)
icmpOutAddrMasksThe number of ICMP Address Mask Request messages sent. (counter)
icmpOutAddrMaskRepsThe number of ICMP Address Mask Reply messages sent. (counter)
icmpOutFragNeededThe number of sent unreachables with fragmentation needed.
icmpInOverflowsThe number of ICMP packets dropped due to queue overflow.



ICMPv6
icmp6InMsgsThe total number of ICMP messages received by the interface which includes all those counted by ipv6IfIcmpInErrors.
Note: This interface is the interface to which the ICMP messages were addressed which may not be necessarily the input interface for the messages.
icmp6InErrorsThe number of ICMP messages which the interface received but determined as having ICMP-specificerrors.
(bad ICMP checksums, bad length, etc.).
icmp6InDestUnreachsThe number of ICMP Destination Unreachable messages received by the interface.
icmp6InAdminProhibsThe number of ICMP destination unreachable/communication administratively prohibited messages received by the interface.
icmp6InTimeExcdsThe number of ICMP Time Exceeded messages received by the interface.
icmp6InParmProblemsThe number of ICMP Parameter Problem messages received by the interface.
icmp6InPktTooBigsThe number of ICMP messages that exceeds outgoing link MTU
icmp6InEchosThe number of ICMP Echo (request) messages received by the interface.
icmp6InEchoRepliesThe number of ICMP Echo Reply messages received by the interface.
icmp6InRouterSolsThe number of ICMP Router Solicit messages received by the interface.
icmp6InRouterAdsThe number of ICMP Router Advertisement messages received by the interface.
icmp6InNeighborSolsThe number of ICMP Neighbor Solicit messages received by the interface.
icmp6InNeighborAdThe number of ICMP Neighbor Advertisement messages received by the interface.
icmp6InRedirectsThe number of Redirect messages received by the interface.
icmp6InBadRedirectsThe Number of incorrect Redirects messages received.
icmp6InGroupQueriesThe number of ICMPv6 Group Membership Query messages received by the interface.
icmp6InGroupRespsThe number of ICMPv6 Group Membership Response messages received by the interface.
icmp6InGroupRedsThe number of ICMPv6 Group Membership Reduction messages received by the interface.
icmp6InOverflowsThe number of ICMP packets droped due to queue overflow.
icmp6OutMsgsThe total number of ICMP messages which this interface attempted to send (includes OutErrors). Note that this counter includes all those counted by icmpOutErrors.
icmp6OutErrorsThe number of ICMP messages which this interface 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 IPv6 to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
icmp6OutDestUnreachsThe number of ICMP Destination Unreachable messages sent by the interface.
icmp6OutAdminProhibsThe number of ICMP dest unreachable/communication administratively prohibited messages sent.
icmp6OutTimeExcdsThe number of ICMP Time Exceeded messages sent by the interface.
icmp6OutParmProblemsThe number of ICMP Parameter Problem messages sent by the interface.
icmp6OutPktTooBigsThe number of ICMP Packet Too Big messages sent by the interface.
icmp6OutEchosThe number of ICMP Echo (request) messages sent by the interface.
icmp6OutEchoRepliesThe number of ICMP Echo Reply messages sent by the interface.
icmp6OutRouterSolsThe number of ICMP Router Solicitation messages sent by the interface.
icmp6OutRouterAdsThe number of ICMP Router Advertisement messages sent by the interface.
icmp6OutNeighborSolsThe number of ICMP Neighbor Solicitation messages sent by the interface.
icmp6OutNeighborAdsThe number of ICMP Neighbor Advertisement messages sent by the interface.
icmp6OutRedirectsThe number of Redirect messages sent.
For a host, this object will always be zero, since hosts do not send redirects.
icmp6OutGroupQueriesThe number of ICMPv6 Group Membership Query messages sent.
icmp6OutGroupRespsThe number of ICMPv6 Group Membership Response messages sent.
icmp6OutGroupRedsThe number of ICMPv6 Group Membership Reduction messages sent.

IGMP
messages receivedTotal number of IGMP messages (counter)
messages received with too few bytesThe number of Multicast packet that was too small (counter)
messages received with bad checksumThe number of IGMP received with bad cksum from IP (counter)
membership queries receivedThe number of group membership queries received (counter)
membership queries received with invalid field(s)The number of invalid IGMP queries (counter)
membership reports receivedThe number of reports received from multicast router (counter)
membership reports received with invalid field(s)The number of invalid reports (counter)
membership reports received for groups to which we belongThe number of group membership report to group address which we are a member of. (counter)
membership reports sentThe Number of group membership reports sent (counter)
SCTP
SCTP
sctpRtoAlgorithmvanj
sctpRtoMax60000 /* Maximum Observed RTO this period */
sctpMaxAssocs-1
sctpMaxInitRetr8
sctpActiveEstabSCTP 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.
sctpAbortedSCTP association has made a direct transition to the CLOSED state from any state using the ABORT primitive, denoting ungraceful termination of the association.
--
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.
sctpOutOfBlueSCTP packet is received for which the receiver is not able to identify the association to which the packet belongs.
sctpOutCtrlChunks/* Control chunks sent - no dups */
either because the MIB counter is explicitly queried or because an SCTP connection is closed.
sctpOutUnorderChunks/* Unordered data chunks sent */
either because the MIB counter is explicitly queried or because an SCTP connection is closed.
sctpOutAckselective acknowledgement is sent.
sctpOutWinUpdatewindow update is sent.
sctpOutWinProbewindow probe is sent.
sctpInOrderChunks/* Control chunks received - no dups */
sctpInAck/* # of received SACK chunks */
sctpInAckUnsent/* # of SACK chunks acking unsent data */
sctpReasmUsrMsgs/* # of Reassembled User Messages { sctpStats 15 } */
sctpInSCTPPkts/* # of Received SCTP Packets { sctpStats 17 } */
sctpTimRetransTimer-based retransmit processing is performed on an association.
sctpTimHearBeatProbeSCTP heartbeat is sent.
sctpListenDropan incoming connection is dropped for any reason.
sctpRtoMin1000
sctpRtoInitial3000
sctpValCookieLife60000
sctpCurrEstabAn SCTP association is tallied if its current state is ESTABLISHED, SHUTDOWN-RECEIVED, or SHUTDOWN-PENDING.
sctpPassiveEstabSCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state. The remote endpoint has initiated the association attempt.
sctpShutdownswhenever 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.
sctpChecksumErrorwhenever an SCTP packet is received from peers with an invalid checksum.
sctpOutOrderChunks
either because the MIB counter is explicitly queried or because an SCTP connection is closed.
sctpRetransChunks/* Retransmitted Chunks */
either because the MIB counter is explicitly queried or because an SCTP connection is closed.
sctpOutAckDelayedAny acknowledgements sent as a part of delayed acknowledgement processing will cause the sctpOutAck probe to fire.
sctpOutFastRetrans/* # of fast retransmits */
sctpInCtrlChunks/* Ordered data chunks received */
sctpInUnorderChunks/* Unordered data chunks received */
sctpInDupAck/* Dups received (ordered+unordered) */
sctpFragUsrMsgswhenever a user message has to be fragmented because of the MTU.
sctpOutSCTPPktseither because the MIB counter is explicitly queried or because an SCTP connection is closed.
sctpInInvalidCookieinvalid cookie is received
sctpTimRetransDropwhenever prolonged failure to perform timer-based retransmission results in the association being aborted.
sctpTimHearBeatDropwhenever an SCTP association is aborted due to failure to receive a heartbeat acknowledgement.
sctpInClosedwhenever data is received on a closed SCTP association.