SCTP-MIB

All MIBs › SCTP-MIB

Organization: IETF SIGTRAN Working Group

Last Updated: 2004-09-02

Category: IP and Core Protocols

Description: Manages Stream Control Transmission Protocol (SCTP) implementations, providing association state, parameter configuration, and transport statistics.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring SCTP-MIB with a free 30-day trial of IPNetwork Monitor.

What Is SCTP-MIB?

SCTP-MIB is a vendor-neutral IETF standards MIB (RFC 3873) for managing implementations of the Stream Control Transmission Protocol, a transport-layer protocol used in telecom signaling (e.g., SIGTRAN) and multi-homed reliable messaging. It exposes association-level state, configured parameters, and detailed transport statistics including established/aborted/shutdown association counts and chunk-level traffic counters. Its monitoring value is squarely on software/protocol health: tracking active vs. passive association establishment rates, checksum errors, and out-of-the-blue packets that reveal misconfigured peers, network corruption, or attack traffic. It is a self-contained transport-layer MIB with no dependency on other MIBs beyond the standard SNMPv2 SMI. It is typically deployed on SCTP-capable routers, telecom signaling gateways, and servers running SIGTRAN or multi-homed SCTP applications. Engineers researching sctp cisco reference this IETF MIB, the standard module vendors implement to expose SCTP association and endpoint statistics via SNMP.

IPNetwork Monitor allows you to monitor SNMP objects defined in SCTP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
SCTP-capable routers and signaling gateways

Monitoring Examples

An operator would poll sctpCurrEstab to see the number of live SCTP associations, alongside sctpActiveEstabs and sctpPassiveEstabs to distinguish locally versus remotely initiated connections. A spike in sctpAborteds, sctpChecksumErrors, or sctpOutOfBlues alongside a drop in sctpCurrEstab would indicate transport-level instability, packet corruption, or a misbehaving peer. Chunk counters like sctpOutCtrlChunks, sctpInOrderChunks, and sctpInUnorderChunks help characterize the traffic mix on the SCTP stack.

What Can Be Monitored

current established associations
active vs passive association counts
aborted/shutdown associations
checksum errors
out-of-the-blue packets
control vs data chunk traffic

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType
InetPortNumber

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using sctpActiveEstabs OID:

Select a device implementing SCTP-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type sctpActiveEstabs into the Find box to locate it in the OID tree, then select it and click OK. The number of times that associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state: COOKIE-ECHOED -> ESTABLISHED. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
sctpMIB	1.3.6.1.2.1.104			The MIB module for managing SCTP implementations. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3873; see the RFC itself for full legal notices.
sctpObjects	1.3.6.1.2.1.104.1
sctpStats	1.3.6.1.2.1.104.1.1
G32 sctpCurrEstab	1.3.6.1.2.1.104.1.1.1	Gauge32	read-only	The number of associations for which the current state is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.
C32 sctpActiveEstabsEx	1.3.6.1.2.1.104.1.1.2	Counter32	read-only	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.
C32 sctpPassiveEstabs	1.3.6.1.2.1.104.1.1.3	Counter32	read-only	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.
C32 sctpAborteds	1.3.6.1.2.1.104.1.1.4	Counter32	read-only	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.
C32 sctpShutdowns	1.3.6.1.2.1.104.1.1.5	Counter32	read-only	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.
C32 sctpOutOfBlues	1.3.6.1.2.1.104.1.1.6	Counter32	read-only	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.
C32 sctpChecksumErrors	1.3.6.1.2.1.104.1.1.7	Counter32	read-only	The number of SCTP packets received with an invalid checksum.
C64 sctpOutCtrlChunks	1.3.6.1.2.1.104.1.1.8	Counter64	read-only	The number of SCTP control chunks sent (retransmissions are not included). Control chunks are those chunks different from DATA.
C64 sctpOutOrderChunks	1.3.6.1.2.1.104.1.1.9	Counter64	read-only	The number of SCTP ordered data chunks sent (retransmissions are not included).
C64 sctpOutUnorderChunks	1.3.6.1.2.1.104.1.1.10	Counter64	read-only	The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included).
C64 sctpInCtrlChunks	1.3.6.1.2.1.104.1.1.11	Counter64	read-only	The number of SCTP control chunks received (no duplicate chunks included).
C64 sctpInOrderChunks	1.3.6.1.2.1.104.1.1.12	Counter64	read-only	The number of SCTP ordered data chunks received (no duplicate chunks included).
C64 sctpInUnorderChunks	1.3.6.1.2.1.104.1.1.13	Counter64	read-only	The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included).
C64 sctpFragUsrMsgs	1.3.6.1.2.1.104.1.1.14	Counter64	read-only	The number of user messages that have to be fragmented because of the MTU.
C64 sctpReasmUsrMsgs	1.3.6.1.2.1.104.1.1.15	Counter64	read-only	The number of user messages reassembled, after conversion into DATA chunks.
C64 sctpOutSCTPPacks	1.3.6.1.2.1.104.1.1.16	Counter64	read-only	The number of SCTP packets sent. Retransmitted DATA chunks are included.
C64 sctpInSCTPPacks	1.3.6.1.2.1.104.1.1.17	Counter64	read-only	The number of SCTP packets received. Duplicates are included.
TIM sctpDiscontinuityTime	1.3.6.1.2.1.104.1.1.18	TimeStamp	read-only	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.
sctpParams	1.3.6.1.2.1.104.1.2
INT sctpRtoAlgorithm	1.3.6.1.2.1.104.1.2.1	INTEGER	read-only	The algorithm used to determine the timeout value (T3-rtx) used for re-transmitting unacknowledged chunks.
U32 sctpRtoMin	1.3.6.1.2.1.104.1.2.2	Unsigned32	read-only	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.
U32 sctpRtoMax	1.3.6.1.2.1.104.1.2.3	Unsigned32	read-only	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.
U32 sctpRtoInitial	1.3.6.1.2.1.104.1.2.4	Unsigned32	read-only	The initial value for the retransmission timer. A retransmission time value of zero means immediate re- transmission.
I32 sctpMaxAssocs	1.3.6.1.2.1.104.1.2.5	Integer32	read-only	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.
U32 sctpValCookieLife	1.3.6.1.2.1.104.1.2.6	Unsigned32	read-only	Valid cookie life in the 4-way start-up handshake procedure.
U32 sctpMaxInitRetr	1.3.6.1.2.1.104.1.2.7	Unsigned32	read-only	The maximum number of retransmissions at the start-up phase (INIT and COOKIE ECHO chunks).
sctpAssocTable	1.3.6.1.2.1.104.1.3		not-accessible	A table containing SCTP association-specific information.
sctpAssocEntry	1.3.6.1.2.1.104.1.3.1		not-accessible	General common variables and statistics for the whole association.
U32 sctpAssocId	1.3.6.1.2.1.104.1.3.1.1	Unsigned32	not-accessible	Association Identification. Value identifying the association.
OCT sctpAssocRemHostName	1.3.6.1.2.1.104.1.3.1.2	OCTET STRING	read-only	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.
INE sctpAssocLocalPort	1.3.6.1.2.1.104.1.3.1.3	InetPortNumber	read-only	The local SCTP port number used for this association.
INE sctpAssocRemPort	1.3.6.1.2.1.104.1.3.1.4	InetPortNumber	read-only	The remote SCTP port number used for this association.
IPt sctpAssocRemPrimAddrType	1.3.6.1.2.1.104.1.3.1.5	InetAddressType	read-only	The internet type of primary remote IP address.
IP sctpAssocRemPrimAddr	1.3.6.1.2.1.104.1.3.1.6	InetAddress	read-only	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.
U32 sctpAssocHeartBeatInterval	1.3.6.1.2.1.104.1.3.1.7	Unsigned32	read-only	The current heartbeat interval.. Zero value means no HeartBeat, even when the concerned sctpAssocRemAddrHBFlag object is true.
INT sctpAssocState	1.3.6.1.2.1.104.1.3.1.8	INTEGER	read-write	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.
U32 sctpAssocInStreams	1.3.6.1.2.1.104.1.3.1.9	Unsigned32	read-only	Inbound Streams according to the negotiation at association start up.
U32 sctpAssocOutStreams	1.3.6.1.2.1.104.1.3.1.10	Unsigned32	read-only	Outbound Streams according to the negotiation at association start up.
U32 sctpAssocMaxRetr	1.3.6.1.2.1.104.1.3.1.11	Unsigned32	read-only	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.
U32 sctpAssocPrimProcess	1.3.6.1.2.1.104.1.3.1.12	Unsigned32	read-only	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.
C32 sctpAssocT1expireds	1.3.6.1.2.1.104.1.3.1.13	Counter32	read-only	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.
C32 sctpAssocT2expireds	1.3.6.1.2.1.104.1.3.1.14	Counter32	read-only	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.
C32 sctpAssocRtxChunks	1.3.6.1.2.1.104.1.3.1.15	Counter32	read-only	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.
TIM sctpAssocStartTime	1.3.6.1.2.1.104.1.3.1.16	TimeStamp	read-only	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.
TIM sctpAssocDiscontinuityTime	1.3.6.1.2.1.104.1.3.1.17	TimeStamp	read-only	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.
sctpAssocLocalAddrTable	1.3.6.1.2.1.104.1.4		not-accessible	Expanded table of sctpAssocTable based on the AssocId index. This table shows data related to each local IP address which is used by this association.
sctpAssocLocalAddrEntry	1.3.6.1.2.1.104.1.4.1		not-accessible	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.
IPt sctpAssocLocalAddrType	1.3.6.1.2.1.104.1.4.1.1	InetAddressType	not-accessible	Internet type of local IP address used for this association.
IP sctpAssocLocalAddr	1.3.6.1.2.1.104.1.4.1.2	InetAddress	not-accessible	The value of a local IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType.
TIM sctpAssocLocalAddrStartTime	1.3.6.1.2.1.104.1.4.1.3	TimeStamp	read-only	The value of sysUpTime at the time that this row was created.
sctpAssocRemAddrTable	1.3.6.1.2.1.104.1.5		not-accessible	Expanded table of sctpAssocTable based on the AssocId index. This table shows data related to each remote peer IP address which is used by this association.
sctpAssocRemAddrEntry	1.3.6.1.2.1.104.1.5.1		not-accessible	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.
IPt sctpAssocRemAddrType	1.3.6.1.2.1.104.1.5.1.1	InetAddressType	not-accessible	Internet type of a remote IP address available for this association.
IP sctpAssocRemAddr	1.3.6.1.2.1.104.1.5.1.2	InetAddress	not-accessible	The value of a remote IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType.
T/F sctpAssocRemAddrActive	1.3.6.1.2.1.104.1.5.1.3	TruthValue	read-only	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.
T/F sctpAssocRemAddrHBActive	1.3.6.1.2.1.104.1.5.1.4	TruthValue	read-only	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).
U32 sctpAssocRemAddrRTO	1.3.6.1.2.1.104.1.5.1.5	Unsigned32	read-only	The current Retransmission Timeout. T3-rtx timer as defined in the protocol SCTP.
U32 sctpAssocRemAddrMaxPathRtx	1.3.6.1.2.1.104.1.5.1.6	Unsigned32	read-only	Maximum number of DATA chunks retransmissions allowed to a remote IP address before it is considered inactive, as defined in RFC2960.
C32 sctpAssocRemAddrRtx	1.3.6.1.2.1.104.1.5.1.7	Counter32	read-only	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.
TIM sctpAssocRemAddrStartTime	1.3.6.1.2.1.104.1.5.1.8	TimeStamp	read-only	The value of sysUpTime at the time that this row was created.
sctpLookupLocalPortTable	1.3.6.1.2.1.104.1.6		not-accessible	With the use of this table, a list of associations which are using the specified local port can be retrieved.
sctpLookupLocalPortEntry	1.3.6.1.2.1.104.1.6.1		not-accessible	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.
TIM sctpLookupLocalPortStartTime	1.3.6.1.2.1.104.1.6.1.1	TimeStamp	read-only	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.
sctpLookupRemPortTable	1.3.6.1.2.1.104.1.7		not-accessible	With the use of this table, a list of associations which are using the specified remote port can be got
sctpLookupRemPortEntry	1.3.6.1.2.1.104.1.7.1		not-accessible	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
TIM sctpLookupRemPortStartTime	1.3.6.1.2.1.104.1.7.1.1	TimeStamp	read-only	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.
sctpLookupRemHostNameTable	1.3.6.1.2.1.104.1.8		not-accessible	With the use of this table, a list of associations with that particular host can be retrieved.
sctpLookupRemHostNameEntry	1.3.6.1.2.1.104.1.8.1		not-accessible	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.
TIM sctpLookupRemHostNameStartTime	1.3.6.1.2.1.104.1.8.1.1	TimeStamp	read-only	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.
sctpLookupRemPrimIPAddrTable	1.3.6.1.2.1.104.1.9		not-accessible	With the use of this table, a list of associations that have the specified IP address as primary within the remote set of active addresses can be retrieved.
sctpLookupRemPrimIPAddrEntry	1.3.6.1.2.1.104.1.9.1		not-accessible	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.
TIM sctpLookupRemPrimIPAddrStartTime	1.3.6.1.2.1.104.1.9.1.1	TimeStamp	read-only	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.
sctpLookupRemIPAddrTable	1.3.6.1.2.1.104.1.10		not-accessible	With the use of this table, a list of associations that have the specified IP address as one of the remote ones can be retrieved.
sctpLookupRemIPAddrEntry	1.3.6.1.2.1.104.1.10.1		not-accessible	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.
TIM sctpLookupRemIPAddrStartTime	1.3.6.1.2.1.104.1.10.1.1	TimeStamp	read-only	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.
sctpMibConformance	1.3.6.1.2.1.104.2
sctpMibCompliances	1.3.6.1.2.1.104.2.1
sctpMibCompliance	1.3.6.1.2.1.104.2.1.1			The compliance statement for SNMP entities which implement this SCTP MIB Module. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT sctpAssocLocalAddrType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRIPTION -- It is only required to have IPv4 and IPv6 addresses without -- zone indices. -- The address with zone indices is required if an -- implementation can connect multiple zones. -- -- OBJECT sctpAssocLocalAddr -- SYNTAX InetAddress (SIZE(4\|16)) -- DESCRIPTION -- An implementation is only required to support globally -- unique IPv4 and IPv6 addresses. -- -- OBJECT sctpAssocRemAddrType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRIPTION -- It is only required to have IPv4 and IPv6 addresses without -- zone indices. -- The address with zone indices is required if an -- implementation can connect multiple zones. -- -- OBJECT sctpAssocRemAddr -- SYNTAX InetAddress (SIZE(4\|16)) -- DESCRIPTION -- An implementation is only required to support globally -- unique IPv4 and IPv6 addresses. --
sctpMibGroups	1.3.6.1.2.1.104.2.2
sctpLayerParamsGroup	1.3.6.1.2.1.104.2.2.1			Common parameters for the SCTP layer, i.e., for all the associations. They can usually be referred to as configuration parameters.
sctpStatsGroup	1.3.6.1.2.1.104.2.2.2			Statistics group. It includes the objects to collect state changes in the SCTP protocol local layer and flow control statistics.
sctpPerAssocParamsGroup	1.3.6.1.2.1.104.2.2.3			The SCTP group of objects to manage per-association parameters. These variables include all the SCTP basic features.
sctpPerAssocStatsGroup	1.3.6.1.2.1.104.2.2.4			Per Association Statistics group. It includes the objects to collect flow control statistics per association.
sctpInverseGroup	1.3.6.1.2.1.104.2.2.5			Objects used in the inverse lookup tables.

RFC description

SCTP (Stream Control Transmission Protocol) implementation management with association, connection, and statistics objects.

Start monitoring vendor-neutral, standards-based MIB, SCTP-capable routers and signaling gateways (association/transport statistics) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SCTP-MIB