| sctpCurrEstab |
.1.3.6.1.2.1.104.1.1.1 |
|
The number of associations for which the current state is
either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.
|
| sctpActiveEstabs |
.1.3.6.1.2.1.104.1.1.2 |
|
The number of times that associations have made a direct
transition to the ESTABLISHED state from the COOKIE-ECHOED
state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated
the association attempt.
|
| sctpPassiveEstabs |
.1.3.6.1.2.1.104.1.1.3 |
|
The number of times that associations have made a direct
transition to the ESTABLISHED state from the CLOSED state:
CLOSED -> ESTABLISHED. The remote endpoint initiated the
association attempt.
|
| sctpAborteds |
.1.3.6.1.2.1.104.1.1.4 |
|
The number of times that associations have made a direct
transition to the CLOSED state from any state using the
primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful
termination of the association.
|
| sctpShutdowns |
.1.3.6.1.2.1.104.1.1.5 |
|
The number of times that associations have made a direct
transition to the CLOSED state from either the SHUTDOWN-SENT
state or the SHUTDOWN-ACK-SENT state. Graceful termination of
the association.
|
| sctpOutOfBlues |
.1.3.6.1.2.1.104.1.1.6 |
|
The number of out of the blue packets received by the host.
An out of the blue packet is an SCTP packet correctly formed,
including the proper checksum, but for which the receiver was
unable to identify an appropriate association.
|
| sctpChecksumErrors |
.1.3.6.1.2.1.104.1.1.7 |
|
The number of SCTP packets received with an invalid
checksum.
|
| sctpOutCtrlChunks |
.1.3.6.1.2.1.104.1.1.8 |
|
The number of SCTP control chunks sent (retransmissions are
not included). Control chunks are those chunks different from
DATA.
|
| sctpOutOrderChunks |
.1.3.6.1.2.1.104.1.1.9 |
|
The number of SCTP ordered data chunks sent (retransmissions
are not included).
|
| sctpOutUnorderChunks |
.1.3.6.1.2.1.104.1.1.10 |
|
The number of SCTP unordered chunks (data chunks in which the
U bit is set to 1) sent (retransmissions are not included).
|
| sctpInCtrlChunks |
.1.3.6.1.2.1.104.1.1.11 |
|
The number of SCTP control chunks received (no duplicate
chunks included).
|
| sctpInOrderChunks |
.1.3.6.1.2.1.104.1.1.12 |
|
The number of SCTP ordered data chunks received (no duplicate
chunks included).
|
| sctpInUnorderChunks |
.1.3.6.1.2.1.104.1.1.13 |
|
The number of SCTP unordered chunks (data chunks in which the
U bit is set to 1) received (no duplicate chunks included).
|
| sctpFragUsrMsgs |
.1.3.6.1.2.1.104.1.1.14 |
|
The number of user messages that have to be fragmented
because of the MTU.
|
| sctpReasmUsrMsgs |
.1.3.6.1.2.1.104.1.1.15 |
|
The number of user messages reassembled, after conversion
into DATA chunks.
|
| sctpOutSCTPPacks |
.1.3.6.1.2.1.104.1.1.16 |
|
The number of SCTP packets sent. Retransmitted DATA chunks
are included.
|
| sctpInSCTPPacks |
.1.3.6.1.2.1.104.1.1.17 |
|
The number of SCTP packets received. Duplicates are
included.
|
| sctpDiscontinuityTime |
.1.3.6.1.2.1.104.1.1.18 |
|
The value of sysUpTime on the most recent occasion at which
any one or more of this general statistics counters suffered a
discontinuity. The relevant counters are the specific
instances associated with this interface of any Counter32 or
Counter64 object contained in the SCTP layer statistics
(defined below sctpStats branch). If no such discontinuities
have occurred since the last re-initialization of the local
management subsystem, then this object contains a zero value.
|
| sctpRtoAlgorithm |
.1.3.6.1.2.1.104.1.2.1 |
|
The algorithm used to determine the timeout value (T3-rtx)
used for re-transmitting unacknowledged chunks.
|
| sctpRtoMin |
.1.3.6.1.2.1.104.1.2.2 |
|
The minimum value permitted by a SCTP implementation for the
retransmission timeout value, measured in milliseconds. More
refined semantics for objects of this type depend upon the
algorithm used to determine the retransmission timeout value.
A retransmission time value of zero means immediate
retransmission.
The value of this object has to be lower than or equal to
stcpRtoMax's value.
|
| sctpRtoMax |
.1.3.6.1.2.1.104.1.2.3 |
|
The maximum value permitted by a SCTP implementation for the
retransmission timeout value, measured in milliseconds. More
refined semantics for objects of this type depend upon the
algorithm used to determine the retransmission timeout value.
A retransmission time value of zero means immediate re-
transmission.
The value of this object has to be greater than or equal to
stcpRtoMin's value.
|
| sctpRtoInitial |
.1.3.6.1.2.1.104.1.2.4 |
|
The initial value for the retransmission timer.
A retransmission time value of zero means immediate re-
transmission.
|
| sctpMaxAssocs |
.1.3.6.1.2.1.104.1.2.5 |
|
The limit on the total number of associations the entity can
support. In entities where the maximum number of associations
is dynamic, this object should contain the value -1.
|
| sctpValCookieLife |
.1.3.6.1.2.1.104.1.2.6 |
|
Valid cookie life in the 4-way start-up handshake procedure.
|
| sctpMaxInitRetr |
.1.3.6.1.2.1.104.1.2.7 |
|
The maximum number of retransmissions at the start-up phase
(INIT and COOKIE ECHO chunks).
|
| sctpAssocEntry |
.1.3.6.1.2.1.104.1.3.1 |
|
General common variables and statistics for the whole
association.
|
| sctpAssocLocalAddrEntry |
.1.3.6.1.2.1.104.1.4.1 |
|
Local information about the available addresses. There will
be an entry for every local IP address defined for this
association.
Implementors need to be aware that if the size of
sctpAssocLocalAddr exceeds 114 octets then OIDs of column
instances in this table will have more than 128 sub-
identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv3.
|
| sctpAssocRemAddrEntry |
.1.3.6.1.2.1.104.1.5.1 |
|
Information about the most important variables for every
remote IP address. There will be an entry for every remote IP
address defined for this association.
Implementors need to be aware that if the size of
sctpAssocRemAddr exceeds 114 octets then OIDs of column
instances in this table will have more than 128 sub-
identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv3.
|
| sctpLookupLocalPortEntry |
.1.3.6.1.2.1.104.1.6.1 |
|
This table is indexed by local port and association ID.
Specifying a local port, we would get a list of the
associations whose local port is the one specified.
|
| sctpLookupRemPortEntry |
.1.3.6.1.2.1.104.1.7.1 |
|
This table is indexed by remote port and association ID.
Specifying a remote port we would get a list of the
associations whose local port is the one specified
|
| sctpLookupRemHostNameEntry |
.1.3.6.1.2.1.104.1.8.1 |
|
This table is indexed by remote host name and association ID.
Specifying a host name we would get a list of the associations
specifying that host name as the remote one.
Implementors need to be aware that if the size of
sctpAssocRemHostName exceeds 115 octets then OIDs of column
instances in this table will have more than 128 sub-
identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv3.
|
| sctpLookupRemPrimIPAddrEntry |
.1.3.6.1.2.1.104.1.9.1 |
|
This table is indexed by primary address and association ID.
Specifying a primary address, we would get a list of the
associations that have the specified remote IP address marked
as primary.
Implementors need to be aware that if the size of
sctpAssocRemPrimAddr exceeds 114 octets then OIDs of column
instances in this table will have more than 128 sub-
identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv3.
|
| sctpLookupRemIPAddrEntry |
.1.3.6.1.2.1.104.1.10.1 |
|
This table is indexed by a remote IP address and association
ID. Specifying an IP address we would get a list of the
associations that have the specified IP address included
within the set of remote IP addresses.
|
| sctpAssocId |
.1.3.6.1.2.1.104.1.3.1.1 |
|
Association Identification. Value identifying the
association.
|
| sctpAssocRemHostName |
.1.3.6.1.2.1.104.1.3.1.2 |
|
The peer's DNS name. This object needs to have the same
format as the encoding in the DNS protocol. This implies that
the domain name can be up to 255 octets long, each octet being
0<=x<=255 as value with US-ASCII A-Z having a case insensitive
matching.
If no DNS domain name was received from the peer at init time
(embedded in the INIT or INIT-ACK chunk), this object is
meaningless. In such cases the object MUST contain a zero-
length string value. Otherwise, it contains the remote host
name received at init time.
|
| sctpAssocLocalPort |
.1.3.6.1.2.1.104.1.3.1.3 |
|
The local SCTP port number used for this association.
|
| sctpAssocRemPort |
.1.3.6.1.2.1.104.1.3.1.4 |
|
The remote SCTP port number used for this association.
|
| sctpAssocRemPrimAddrType |
.1.3.6.1.2.1.104.1.3.1.5 |
|
The internet type of primary remote IP address.
|
| sctpAssocRemPrimAddr |
.1.3.6.1.2.1.104.1.3.1.6 |
|
The primary remote IP address. The type of this address is
determined by the value of sctpAssocRemPrimAddrType.
The client side will know this value after INIT_ACK message
reception, the server side will know this value when sending
INIT_ACK message. However, values will be filled in at
established(4) state.
|
| sctpAssocHeartBeatInterval |
.1.3.6.1.2.1.104.1.3.1.7 |
|
The current heartbeat interval..
Zero value means no HeartBeat, even when the concerned
sctpAssocRemAddrHBFlag object is true.
|
| sctpAssocState |
.1.3.6.1.2.1.104.1.3.1.8 |
|
The state of this SCTP association.
As in TCP, deleteTCB(9) is the only value that may be set by a
management station. If any other value is received, then the
agent must return a wrongValue error.
If a management station sets this object to the value
deleteTCB(9), then this has the effect of deleting the TCB (as
defined in SCTP) of the corresponding association on the
managed node, resulting in immediate termination of the
association.
As an implementation-specific option, an ABORT chunk may be
sent from the managed node to the other SCTP endpoint as a
result of setting the deleteTCB(9) value. The ABORT chunk
implies an ungraceful association shutdown.
|
| sctpAssocInStreams |
.1.3.6.1.2.1.104.1.3.1.9 |
|
Inbound Streams according to the negotiation at association
start up.
|
| sctpAssocOutStreams |
.1.3.6.1.2.1.104.1.3.1.10 |
|
Outbound Streams according to the negotiation at association
start up.
|
| sctpAssocMaxRetr |
.1.3.6.1.2.1.104.1.3.1.11 |
|
The maximum number of data retransmissions in the association
context. This value is specific for each association and the
upper layer can change it by calling the appropriate
primitives. This value has to be smaller than the addition of
all the maximum number for all the paths
(sctpAssocRemAddrMaxPathRtx).
A value of zero value means no retransmissions.
|
| sctpAssocPrimProcess |
.1.3.6.1.2.1.104.1.3.1.12 |
|
This object identifies the system level process which holds
primary responsibility for the SCTP association.
Wherever possible, this should be the system's native unique
identification number. The special value 0 can be used to
indicate that no primary process is known.
Note that the value of this object can be used as a pointer
into the swRunTable of the HOST-RESOURCES-MIB(if the value is
smaller than 2147483647) or into the sysApplElmtRunTable of
the SYSAPPL-MIB.
|
| sctpAssocT1expireds |
.1.3.6.1.2.1.104.1.3.1.13 |
|
The T1 timer determines how long to wait for an
acknowledgement after sending an INIT or COOKIE-ECHO chunk.
This object reflects the number of times the T1 timer expires
without having received the acknowledgement.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times as
indicated by the value of sctpAssocDiscontinuityTime.
|
| sctpAssocT2expireds |
.1.3.6.1.2.1.104.1.3.1.14 |
|
The T2 timer determines how long to wait for an
acknowledgement after sending a SHUTDOWN or SHUTDOWN-ACK
chunk. This object reflects the number of times that T2- timer
expired.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times as
indicated by the value of sctpAssocDiscontinuityTime.
|
| sctpAssocRtxChunks |
.1.3.6.1.2.1.104.1.3.1.15 |
|
When T3-rtx expires, the DATA chunks that triggered the T3
timer will be re-sent according with the retransmissions
rules. Every DATA chunk that was included in the SCTP packet
that triggered the T3-rtx timer must be added to the value of
this counter.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times as
indicated by the value of sctpAssocDiscontinuityTime.
|
| sctpAssocStartTime |
.1.3.6.1.2.1.104.1.3.1.16 |
|
The value of sysUpTime at the time that the association
represented by this row enters the ESTABLISHED state, i.e.,
the sctpAssocState object is set to established(4). The
value of this object will be zero:
- before the association enters the established(4)
state, or
- if the established(4) state was entered prior to
the last re-initialization of the local network management
subsystem.
|
| sctpAssocDiscontinuityTime |
.1.3.6.1.2.1.104.1.3.1.17 |
|
The value of sysUpTime on the most recent occasion at which
any one or more of this SCTP association counters suffered a
discontinuity. The relevant counters are the specific
instances associated with this interface of any Counter32 or
Counter64 object contained in the sctpAssocTable or
sctpLocalAddrTable or sctpRemAddrTable. If no such
discontinuities have occurred since the last re-initialization
of the local management subsystem, then this object contains a
zero value.
|
| sctpAssocLocalAddrType |
.1.3.6.1.2.1.104.1.4.1.1 |
|
Internet type of local IP address used for this association.
|
| sctpAssocLocalAddr |
.1.3.6.1.2.1.104.1.4.1.2 |
|
The value of a local IP address available for this
association. The type of this address is determined by the
value of sctpAssocLocalAddrType.
|
| sctpAssocLocalAddrStartTime |
.1.3.6.1.2.1.104.1.4.1.3 |
|
The value of sysUpTime at the time that this row was
created.
|
| sctpAssocRemAddrType |
.1.3.6.1.2.1.104.1.5.1.1 |
|
Internet type of a remote IP address available for this
association.
|
| sctpAssocRemAddr |
.1.3.6.1.2.1.104.1.5.1.2 |
|
The value of a remote IP address available for this
association. The type of this address is determined by the
value of sctpAssocLocalAddrType.
|
| sctpAssocRemAddrActive |
.1.3.6.1.2.1.104.1.5.1.3 |
|
This object gives information about the reachability of this
specific remote IP address.
When the object is set to 'true' (1), the remote IP address is
understood as Active. Active means that the threshold of no
answers received from this IP address has not been reached.
When the object is set to 'false' (2), the remote IP address
is understood as Inactive. Inactive means that either no
heartbeat or any other message was received from this address,
reaching the threshold defined by the protocol.
|
| sctpAssocRemAddrHBActive |
.1.3.6.1.2.1.104.1.5.1.4 |
|
This object indicates whether the optional Heartbeat check
associated to one destination transport address is activated
or not (value equal to true or false, respectively).
|
| sctpAssocRemAddrRTO |
.1.3.6.1.2.1.104.1.5.1.5 |
|
The current Retransmission Timeout. T3-rtx timer as defined
in the protocol SCTP.
|
| sctpAssocRemAddrMaxPathRtx |
.1.3.6.1.2.1.104.1.5.1.6 |
|
Maximum number of DATA chunks retransmissions allowed to a
remote IP address before it is considered inactive, as defined
in RFC2960.
|
| sctpAssocRemAddrRtx |
.1.3.6.1.2.1.104.1.5.1.7 |
|
Number of DATA chunks retransmissions to this specific IP
address. When T3-rtx expires, the DATA chunk that triggered
the T3 timer will be re-sent according to the retransmissions
rules. Every DATA chunk that is included in a SCTP packet and
was transmitted to this specific IP address before, will be
included in this counter.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times as
indicated by the value of sctpAssocDiscontinuityTime.
|
| sctpAssocRemAddrStartTime |
.1.3.6.1.2.1.104.1.5.1.8 |
|
The value of sysUpTime at the time that this row was
created.
|
| sctpLookupLocalPortStartTime |
.1.3.6.1.2.1.104.1.6.1.1 |
|
The value of sysUpTime at the time that this row was created.
As the table will be created after the sctpAssocTable
creation, this value could be equal to the sctpAssocStartTime
object from the main table.
|
| sctpLookupRemPortStartTime |
.1.3.6.1.2.1.104.1.7.1.1 |
|
The value of sysUpTime at the time that this row was created.
As the table will be created after the sctpAssocTable
creation, this value could be equal to the sctpAssocStartTime
object from the main table.
|
| sctpLookupRemHostNameStartTime |
.1.3.6.1.2.1.104.1.8.1.1 |
|
The value of sysUpTime at the time that this row was created.
As the table will be created after the sctpAssocTable
creation, this value could be equal to the sctpAssocStartTime
object from the main table.
|
| sctpLookupRemPrimIPAddrStartTime |
.1.3.6.1.2.1.104.1.9.1.1 |
|
The value of SysUpTime at the time that this row was created.
As the table will be created after the sctpAssocTable
creation, this value could be equal to the sctpAssocStartTime
object from the main table.
|
| sctpLookupRemIPAddrStartTime |
.1.3.6.1.2.1.104.1.10.1.1 |
|
The value of SysUpTime at the time that this row was created.
As the table will be created after the sctpAssocTable
creation, this value could be equal to the sctpAssocStartTime
object from the main table.
|
