1 SCTP-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32,
5 Counter32, Counter64, mib-2
6 FROM SNMPv2-SMI -- [RFC2578]
8 FROM SNMPv2-TC -- [RFC2579]
9 MODULE-COMPLIANCE, OBJECT-GROUP
10 FROM SNMPv2-CONF -- [RFC2580]
11 InetAddressType, InetAddress, InetPortNumber
12 FROM INET-ADDRESS-MIB; -- [RFC3291]
20 sctpMIB MODULE-IDENTITY
21 LAST-UPDATED "200409020000Z" -- 2nd September 2004
22 ORGANIZATION "IETF SIGTRAN Working Group"
25 WG EMail: sigtran@ietf.org
28 http://www.ietf.org/html.charters/sigtran-charter.html
36 Email: lyong@ciena.com
38 Editors: Maria-Carmen Belinchon
41 Via de los Poblados, 13
45 Email: Maria.C.Belinchon@ericsson.com
47 Jose-Javier Pastor-Balbas
50 Via de los Poblados, 13
54 Email: J.Javier.Pastor@ericsson.com
57 "The MIB module for managing SCTP implementations.
59 Copyright (C) The Internet Society (2004). This version of
60 this MIB module is part of RFC 3873; see the RFC itself for
63 REVISION "200409020000Z" -- 2nd September 2004
65 DESCRIPTION " Initial version, published as RFC 3873"
71 -- the SCTP base variables group
73 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 }
75 sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 }
76 sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 }
81 -- STATE-RELATED STATISTICS
83 sctpCurrEstab OBJECT-TYPE
88 "The number of associations for which the current state is
89 either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING."
91 "Section 4 in RFC2960 covers the SCTP Association state
97 sctpActiveEstabs OBJECT-TYPE
102 "The number of times that associations have made a direct
103 transition to the ESTABLISHED state from the COOKIE-ECHOED
104 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated
105 the association attempt."
107 "Section 4 in RFC2960 covers the SCTP Association state
122 sctpPassiveEstabs OBJECT-TYPE
127 "The number of times that associations have made a direct
128 transition to the ESTABLISHED state from the CLOSED state:
129 CLOSED -> ESTABLISHED. The remote endpoint initiated the
130 association attempt."
132 "Section 4 in RFC2960 covers the SCTP Association state
138 sctpAborteds OBJECT-TYPE
143 "The number of times that associations have made a direct
144 transition to the CLOSED state from any state using the
145 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful
146 termination of the association."
148 "Section 4 in RFC2960 covers the SCTP Association state
154 sctpShutdowns OBJECT-TYPE
159 "The number of times that associations have made a direct
160 transition to the CLOSED state from either the SHUTDOWN-SENT
161 state or the SHUTDOWN-ACK-SENT state. Graceful termination of
164 "Section 4 in RFC2960 covers the SCTP Association state
173 -- OTHER LAYER STATISTICS
175 sctpOutOfBlues OBJECT-TYPE
180 "The number of out of the blue packets received by the host.
181 An out of the blue packet is an SCTP packet correctly formed,
182 including the proper checksum, but for which the receiver was
183 unable to identify an appropriate association."
185 "Section 8.4 in RFC2960 deals with the Out-Of-The-Blue
186 (OOTB) packet definition and procedures."
190 sctpChecksumErrors OBJECT-TYPE
195 "The number of SCTP packets received with an invalid
198 "The checksum is located at the end of the SCTP packet as per
199 Section 3.1 in RFC2960. RFC3309 updates SCTP to use a 32 bit
204 sctpOutCtrlChunks OBJECT-TYPE
209 "The number of SCTP control chunks sent (retransmissions are
210 not included). Control chunks are those chunks different from
213 "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as
214 those chunks different from those that contain user
215 information, i.e., DATA chunks."
224 sctpOutOrderChunks OBJECT-TYPE
229 "The number of SCTP ordered data chunks sent (retransmissions
232 "Section 3.3.1 in RFC2960 defines the ordered data chunk."
236 sctpOutUnorderChunks OBJECT-TYPE
241 "The number of SCTP unordered chunks (data chunks in which the
242 U bit is set to 1) sent (retransmissions are not included)."
244 "Section 3.3.1 in RFC2960 defines the unordered data chunk."
248 sctpInCtrlChunks OBJECT-TYPE
253 "The number of SCTP control chunks received (no duplicate
256 "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as
257 those chunks different from those that contain user
258 information, i.e., DATA chunks."
263 sctpInOrderChunks OBJECT-TYPE
268 "The number of SCTP ordered data chunks received (no duplicate
276 "Section 3.3.1 in RFC2960 defines the ordered data chunk."
281 sctpInUnorderChunks OBJECT-TYPE
286 "The number of SCTP unordered chunks (data chunks in which the
287 U bit is set to 1) received (no duplicate chunks included)."
289 "Section 3.3.1 in RFC2960 defines the unordered data chunk."
295 sctpFragUsrMsgs OBJECT-TYPE
301 "The number of user messages that have to be fragmented
307 sctpReasmUsrMsgs OBJECT-TYPE
312 "The number of user messages reassembled, after conversion
315 "Section 6.9 in RFC2960 includes a description of the
326 sctpOutSCTPPacks OBJECT-TYPE
331 "The number of SCTP packets sent. Retransmitted DATA chunks
337 sctpInSCTPPacks OBJECT-TYPE
342 "The number of SCTP packets received. Duplicates are
347 sctpDiscontinuityTime OBJECT-TYPE
352 "The value of sysUpTime on the most recent occasion at which
353 any one or more of this general statistics counters suffered a
354 discontinuity. The relevant counters are the specific
355 instances associated with this interface of any Counter32 or
356 Counter64 object contained in the SCTP layer statistics
357 (defined below sctpStats branch). If no such discontinuities
358 have occurred since the last re-initialization of the local
359 management subsystem, then this object contains a zero value."
361 "The inclusion of this object is recommended by RFC2578."
366 -- PROTOCOL GENERAL VARIABLES
367 -- **************************
369 sctpRtoAlgorithm OBJECT-TYPE
371 other(1), -- Other new one. Future use
372 vanj(2) -- Van Jacobson's algorithm
380 "The algorithm used to determine the timeout value (T3-rtx)
381 used for re-transmitting unacknowledged chunks."
383 "Section 6.3.1 and 6.3.2 in RFC2960 cover the RTO calculation
384 and retransmission timer rules."
385 DEFVAL {vanj} -- vanj(2)
390 sctpRtoMin OBJECT-TYPE
396 "The minimum value permitted by a SCTP implementation for the
397 retransmission timeout value, measured in milliseconds. More
398 refined semantics for objects of this type depend upon the
399 algorithm used to determine the retransmission timeout value.
401 A retransmission time value of zero means immediate
404 The value of this object has to be lower than or equal to
406 DEFVAL {1000} -- milliseconds
410 sctpRtoMax OBJECT-TYPE
416 "The maximum value permitted by a SCTP implementation for the
417 retransmission timeout value, measured in milliseconds. More
418 refined semantics for objects of this type depend upon the
419 algorithm used to determine the retransmission timeout value.
421 A retransmission time value of zero means immediate re-
428 The value of this object has to be greater than or equal to
430 DEFVAL {60000} -- milliseconds
435 sctpRtoInitial OBJECT-TYPE
441 "The initial value for the retransmission timer.
443 A retransmission time value of zero means immediate re-
445 DEFVAL {3000} -- milliseconds
450 sctpMaxAssocs OBJECT-TYPE
451 SYNTAX Integer32 (-1 | 0..2147483647)
455 "The limit on the total number of associations the entity can
456 support. In entities where the maximum number of associations
457 is dynamic, this object should contain the value -1."
462 sctpValCookieLife OBJECT-TYPE
469 "Valid cookie life in the 4-way start-up handshake procedure."
471 "Section 5.1.3 in RFC2960 explains the cookie generation
472 process. Recommended value is per section 14 in RFC2960."
473 DEFVAL {60000} -- milliseconds
479 sctpMaxInitRetr OBJECT-TYPE
484 "The maximum number of retransmissions at the start-up phase
485 (INIT and COOKIE ECHO chunks). "
487 "Section 5.1.4, 5.1.6 in RFC2960 refers to Max.Init.Retransmit
488 parameter. Recommended value is per section 14 in RFC2960."
489 DEFVAL {8} -- number of attempts
497 -- the SCTP Association TABLE
499 -- The SCTP association table contains information about each
500 -- association in which the local endpoint is involved.
503 sctpAssocTable OBJECT-TYPE
504 SYNTAX SEQUENCE OF SctpAssocEntry
505 MAX-ACCESS not-accessible
508 "A table containing SCTP association-specific information."
510 ::= { sctpObjects 3 }
513 sctpAssocEntry OBJECT-TYPE
514 SYNTAX SctpAssocEntry
515 MAX-ACCESS not-accessible
519 "General common variables and statistics for the whole
521 INDEX { sctpAssocId }
523 ::= { sctpAssocTable 1 }
530 SctpAssocEntry ::= SEQUENCE {
531 sctpAssocId Unsigned32,
532 sctpAssocRemHostName OCTET STRING,
533 sctpAssocLocalPort InetPortNumber,
534 sctpAssocRemPort InetPortNumber,
535 sctpAssocRemPrimAddrType InetAddressType,
536 sctpAssocRemPrimAddr InetAddress,
537 sctpAssocHeartBeatInterval Unsigned32,
538 sctpAssocState INTEGER,
539 sctpAssocInStreams Unsigned32,
540 sctpAssocOutStreams Unsigned32,
541 sctpAssocMaxRetr Unsigned32,
542 sctpAssocPrimProcess Unsigned32,
543 sctpAssocT1expireds Counter32, -- Statistic
544 sctpAssocT2expireds Counter32, -- Statistic
545 sctpAssocRtxChunks Counter32, -- Statistic
546 sctpAssocStartTime TimeStamp,
547 sctpAssocDiscontinuityTime TimeStamp
551 sctpAssocId OBJECT-TYPE
552 SYNTAX Unsigned32 (1..4294967295)
553 MAX-ACCESS not-accessible
556 "Association Identification. Value identifying the
559 ::= { sctpAssocEntry 1 }
562 sctpAssocRemHostName OBJECT-TYPE
563 SYNTAX OCTET STRING (SIZE(0..255))
567 "The peer's DNS name. This object needs to have the same
568 format as the encoding in the DNS protocol. This implies that
569 the domain name can be up to 255 octets long, each octet being
570 0<=x<=255 as value with US-ASCII A-Z having a case insensitive
573 If no DNS domain name was received from the peer at init time
574 (embedded in the INIT or INIT-ACK chunk), this object is
575 meaningless. In such cases the object MUST contain a zero-
576 length string value. Otherwise, it contains the remote host
577 name received at init time."
581 ::= { sctpAssocEntry 2 }
584 sctpAssocLocalPort OBJECT-TYPE
585 SYNTAX InetPortNumber (1..65535)
589 "The local SCTP port number used for this association."
591 ::= { sctpAssocEntry 3 }
594 sctpAssocRemPort OBJECT-TYPE
595 SYNTAX InetPortNumber (1..65535)
599 "The remote SCTP port number used for this association."
601 ::= { sctpAssocEntry 4 }
604 sctpAssocRemPrimAddrType OBJECT-TYPE
605 SYNTAX InetAddressType
609 "The internet type of primary remote IP address. "
611 ::= { sctpAssocEntry 5 }
613 sctpAssocRemPrimAddr OBJECT-TYPE
618 "The primary remote IP address. The type of this address is
619 determined by the value of sctpAssocRemPrimAddrType.
621 The client side will know this value after INIT_ACK message
622 reception, the server side will know this value when sending
623 INIT_ACK message. However, values will be filled in at
624 established(4) state."
626 ::= { sctpAssocEntry 6 }
632 sctpAssocHeartBeatInterval OBJECT-TYPE
638 "The current heartbeat interval..
640 Zero value means no HeartBeat, even when the concerned
641 sctpAssocRemAddrHBFlag object is true."
642 DEFVAL {30000} -- milliseconds
644 ::= { sctpAssocEntry 7 }
647 sctpAssocState OBJECT-TYPE
659 MAX-ACCESS read-write
662 "The state of this SCTP association.
664 As in TCP, deleteTCB(9) is the only value that may be set by a
665 management station. If any other value is received, then the
666 agent must return a wrongValue error.
668 If a management station sets this object to the value
669 deleteTCB(9), then this has the effect of deleting the TCB (as
670 defined in SCTP) of the corresponding association on the
671 managed node, resulting in immediate termination of the
674 As an implementation-specific option, an ABORT chunk may be
675 sent from the managed node to the other SCTP endpoint as a
676 result of setting the deleteTCB(9) value. The ABORT chunk
677 implies an ungraceful association shutdown."
685 "Section 4 in RFC2960 covers the SCTP Association state
688 ::= { sctpAssocEntry 8 }
691 sctpAssocInStreams OBJECT-TYPE
692 SYNTAX Unsigned32 (1..65535)
696 "Inbound Streams according to the negotiation at association
699 "Section 1.3 in RFC2960 includes a definition of stream.
700 Section 5.1.1 in RFC2960 covers the streams negotiation
703 ::= { sctpAssocEntry 9 }
705 sctpAssocOutStreams OBJECT-TYPE
706 SYNTAX Unsigned32 (1..65535)
710 "Outbound Streams according to the negotiation at association
713 "Section 1.3 in RFC2960 includes a definition of stream.
714 Section 5.1.1 in RFC2960 covers the streams negotiation
717 ::= { sctpAssocEntry 10 }
720 sctpAssocMaxRetr OBJECT-TYPE
725 "The maximum number of data retransmissions in the association
726 context. This value is specific for each association and the
727 upper layer can change it by calling the appropriate
728 primitives. This value has to be smaller than the addition of
729 all the maximum number for all the paths
730 (sctpAssocRemAddrMaxPathRtx).
734 A value of zero value means no retransmissions."
735 DEFVAL {10} -- number of attempts
737 ::= { sctpAssocEntry 11 }
739 sctpAssocPrimProcess OBJECT-TYPE
744 "This object identifies the system level process which holds
745 primary responsibility for the SCTP association.
746 Wherever possible, this should be the system's native unique
747 identification number. The special value 0 can be used to
748 indicate that no primary process is known.
750 Note that the value of this object can be used as a pointer
751 into the swRunTable of the HOST-RESOURCES-MIB(if the value is
752 smaller than 2147483647) or into the sysApplElmtRunTable of
755 ::= { sctpAssocEntry 12 }
758 -- Association Statistics
760 sctpAssocT1expireds OBJECT-TYPE
765 "The T1 timer determines how long to wait for an
766 acknowledgement after sending an INIT or COOKIE-ECHO chunk.
767 This object reflects the number of times the T1 timer expires
768 without having received the acknowledgement.
770 Discontinuities in the value of this counter can occur at re-
771 initialization of the management system, and at other times as
772 indicated by the value of sctpAssocDiscontinuityTime."
774 "Section 5 in RFC2960."
777 ::= { sctpAssocEntry 13 }
779 sctpAssocT2expireds OBJECT-TYPE
787 "The T2 timer determines how long to wait for an
788 acknowledgement after sending a SHUTDOWN or SHUTDOWN-ACK
789 chunk. This object reflects the number of times that T2- timer
792 Discontinuities in the value of this counter can occur at re-
793 initialization of the management system, and at other times as
794 indicated by the value of sctpAssocDiscontinuityTime."
796 "Section 9.2 in RFC2960."
797 ::= { sctpAssocEntry 14 }
800 sctpAssocRtxChunks OBJECT-TYPE
805 "When T3-rtx expires, the DATA chunks that triggered the T3
806 timer will be re-sent according with the retransmissions
807 rules. Every DATA chunk that was included in the SCTP packet
808 that triggered the T3-rtx timer must be added to the value of
811 Discontinuities in the value of this counter can occur at re-
812 initialization of the management system, and at other times as
813 indicated by the value of sctpAssocDiscontinuityTime."
815 "Section 6 in RFC2960 covers the retransmission process and
818 ::= { sctpAssocEntry 15 }
821 sctpAssocStartTime OBJECT-TYPE
826 "The value of sysUpTime at the time that the association
827 represented by this row enters the ESTABLISHED state, i.e.,
828 the sctpAssocState object is set to established(4). The
829 value of this object will be zero:
830 - before the association enters the established(4)
836 - if the established(4) state was entered prior to
837 the last re-initialization of the local network management
840 ::= { sctpAssocEntry 16 }
842 sctpAssocDiscontinuityTime OBJECT-TYPE
847 "The value of sysUpTime on the most recent occasion at which
848 any one or more of this SCTP association counters suffered a
849 discontinuity. The relevant counters are the specific
850 instances associated with this interface of any Counter32 or
851 Counter64 object contained in the sctpAssocTable or
852 sctpLocalAddrTable or sctpRemAddrTable. If no such
853 discontinuities have occurred since the last re-initialization
854 of the local management subsystem, then this object contains a
857 "The inclusion of this object is recommended by RFC2578."
859 ::= { sctpAssocEntry 17 }
861 -- Expanded tables: Including Multi-home feature
863 -- Local Address TABLE
864 -- *******************
866 sctpAssocLocalAddrTable OBJECT-TYPE
867 SYNTAX SEQUENCE OF SctpAssocLocalAddrEntry
868 MAX-ACCESS not-accessible
871 "Expanded table of sctpAssocTable based on the AssocId index.
872 This table shows data related to each local IP address which
873 is used by this association."
875 ::= { sctpObjects 4 }
877 sctpAssocLocalAddrEntry OBJECT-TYPE
878 SYNTAX SctpAssocLocalAddrEntry
879 MAX-ACCESS not-accessible
882 "Local information about the available addresses. There will
883 be an entry for every local IP address defined for this
888 Implementors need to be aware that if the size of
889 sctpAssocLocalAddr exceeds 114 octets then OIDs of column
890 instances in this table will have more than 128 sub-
891 identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
893 INDEX { sctpAssocId, -- shared index
894 sctpAssocLocalAddrType,
897 ::= { sctpAssocLocalAddrTable 1 }
900 SctpAssocLocalAddrEntry ::= SEQUENCE {
901 sctpAssocLocalAddrType InetAddressType,
902 sctpAssocLocalAddr InetAddress,
903 sctpAssocLocalAddrStartTime TimeStamp
907 sctpAssocLocalAddrType OBJECT-TYPE
908 SYNTAX InetAddressType
909 MAX-ACCESS not-accessible
912 "Internet type of local IP address used for this association."
915 ::= { sctpAssocLocalAddrEntry 1 }
917 sctpAssocLocalAddr OBJECT-TYPE
919 MAX-ACCESS not-accessible
922 "The value of a local IP address available for this
923 association. The type of this address is determined by the
924 value of sctpAssocLocalAddrType."
926 ::= { sctpAssocLocalAddrEntry 2 }
938 sctpAssocLocalAddrStartTime OBJECT-TYPE
943 "The value of sysUpTime at the time that this row was
946 ::= { sctpAssocLocalAddrEntry 3 }
948 -- Remote Addresses TABLE
949 -- **********************
951 sctpAssocRemAddrTable OBJECT-TYPE
952 SYNTAX SEQUENCE OF SctpAssocRemAddrEntry
953 MAX-ACCESS not-accessible
956 "Expanded table of sctpAssocTable based on the AssocId index.
957 This table shows data related to each remote peer IP address
958 which is used by this association."
960 ::= { sctpObjects 5 }
963 sctpAssocRemAddrEntry OBJECT-TYPE
964 SYNTAX SctpAssocRemAddrEntry
965 MAX-ACCESS not-accessible
968 "Information about the most important variables for every
969 remote IP address. There will be an entry for every remote IP
970 address defined for this association.
972 Implementors need to be aware that if the size of
973 sctpAssocRemAddr exceeds 114 octets then OIDs of column
974 instances in this table will have more than 128 sub-
975 identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
977 INDEX { sctpAssocId, -- shared index
978 sctpAssocRemAddrType,
981 ::= { sctpAssocRemAddrTable 1 }
989 SctpAssocRemAddrEntry ::= SEQUENCE {
990 sctpAssocRemAddrType InetAddressType,
991 sctpAssocRemAddr InetAddress,
992 sctpAssocRemAddrActive TruthValue,
993 sctpAssocRemAddrHBActive TruthValue,
994 sctpAssocRemAddrRTO Unsigned32,
995 sctpAssocRemAddrMaxPathRtx Unsigned32,
996 sctpAssocRemAddrRtx Counter32, -- Statistic
997 sctpAssocRemAddrStartTime TimeStamp
1001 sctpAssocRemAddrType OBJECT-TYPE
1002 SYNTAX InetAddressType
1003 MAX-ACCESS not-accessible
1006 "Internet type of a remote IP address available for this
1008 ::= { sctpAssocRemAddrEntry 1 }
1011 sctpAssocRemAddr OBJECT-TYPE
1013 MAX-ACCESS not-accessible
1016 "The value of a remote IP address available for this
1017 association. The type of this address is determined by the
1018 value of sctpAssocLocalAddrType."
1020 ::= { sctpAssocRemAddrEntry 2 }
1023 sctpAssocRemAddrActive OBJECT-TYPE
1025 MAX-ACCESS read-only
1028 "This object gives information about the reachability of this
1029 specific remote IP address.
1031 When the object is set to 'true' (1), the remote IP address is
1032 understood as Active. Active means that the threshold of no
1033 answers received from this IP address has not been reached.
1040 When the object is set to 'false' (2), the remote IP address
1041 is understood as Inactive. Inactive means that either no
1042 heartbeat or any other message was received from this address,
1043 reaching the threshold defined by the protocol."
1046 "The remote transport states are defined as Active and
1047 Inactive in the SCTP, RFC2960."
1049 ::= { sctpAssocRemAddrEntry 3 }
1052 sctpAssocRemAddrHBActive OBJECT-TYPE
1054 MAX-ACCESS read-only
1057 "This object indicates whether the optional Heartbeat check
1058 associated to one destination transport address is activated
1059 or not (value equal to true or false, respectively). "
1061 ::= { sctpAssocRemAddrEntry 4 }
1064 sctpAssocRemAddrRTO OBJECT-TYPE -- T3-rtx- Timer
1066 UNITS "milliseconds"
1067 MAX-ACCESS read-only
1070 "The current Retransmission Timeout. T3-rtx timer as defined
1071 in the protocol SCTP."
1073 "Section 6.3 in RFC2960 deals with the Retransmission Timer
1076 ::= { sctpAssocRemAddrEntry 5 }
1079 sctpAssocRemAddrMaxPathRtx OBJECT-TYPE
1081 MAX-ACCESS read-only
1084 "Maximum number of DATA chunks retransmissions allowed to a
1085 remote IP address before it is considered inactive, as defined
1092 "Section 8.2, 8.3 and 14 in RFC2960."
1093 DEFVAL {5} -- number of attempts
1095 ::= { sctpAssocRemAddrEntry 6 }
1098 -- Remote Address Statistic
1100 sctpAssocRemAddrRtx OBJECT-TYPE
1102 MAX-ACCESS read-only
1105 "Number of DATA chunks retransmissions to this specific IP
1106 address. When T3-rtx expires, the DATA chunk that triggered
1107 the T3 timer will be re-sent according to the retransmissions
1108 rules. Every DATA chunk that is included in a SCTP packet and
1109 was transmitted to this specific IP address before, will be
1110 included in this counter.
1112 Discontinuities in the value of this counter can occur at re-
1113 initialization of the management system, and at other times as
1114 indicated by the value of sctpAssocDiscontinuityTime."
1116 ::= { sctpAssocRemAddrEntry 7 }
1118 sctpAssocRemAddrStartTime OBJECT-TYPE
1120 MAX-ACCESS read-only
1123 "The value of sysUpTime at the time that this row was
1126 ::= { sctpAssocRemAddrEntry 8 }
1128 -- ASSOCIATION INVERSE TABLE
1129 -- *************************
1133 sctpLookupLocalPortTable OBJECT-TYPE
1134 SYNTAX SEQUENCE OF SctpLookupLocalPortEntry
1135 MAX-ACCESS not-accessible
1138 "With the use of this table, a list of associations which are
1142 using the specified local port can be retrieved."
1144 ::= { sctpObjects 6 }
1147 sctpLookupLocalPortEntry OBJECT-TYPE
1148 SYNTAX SctpLookupLocalPortEntry
1149 MAX-ACCESS not-accessible
1152 "This table is indexed by local port and association ID.
1153 Specifying a local port, we would get a list of the
1154 associations whose local port is the one specified."
1156 INDEX { sctpAssocLocalPort,
1159 ::= { sctpLookupLocalPortTable 1 }
1162 SctpLookupLocalPortEntry::= SEQUENCE {
1163 sctpLookupLocalPortStartTime TimeStamp
1167 sctpLookupLocalPortStartTime OBJECT-TYPE
1169 MAX-ACCESS read-only
1172 "The value of sysUpTime at the time that this row was created.
1174 As the table will be created after the sctpAssocTable
1175 creation, this value could be equal to the sctpAssocStartTime
1176 object from the main table."
1178 ::= { sctpLookupLocalPortEntry 1 }
1182 sctpLookupRemPortTable OBJECT-TYPE
1183 SYNTAX SEQUENCE OF SctpLookupRemPortEntry
1184 MAX-ACCESS not-accessible
1194 "With the use of this table, a list of associations which are
1195 using the specified remote port can be got"
1197 ::= { sctpObjects 7 }
1199 sctpLookupRemPortEntry OBJECT-TYPE
1200 SYNTAX SctpLookupRemPortEntry
1201 MAX-ACCESS not-accessible
1204 "This table is indexed by remote port and association ID.
1205 Specifying a remote port we would get a list of the
1206 associations whose local port is the one specified "
1208 INDEX { sctpAssocRemPort,
1211 ::= { sctpLookupRemPortTable 1 }
1213 SctpLookupRemPortEntry::= SEQUENCE {
1214 sctpLookupRemPortStartTime TimeStamp
1218 sctpLookupRemPortStartTime OBJECT-TYPE
1220 MAX-ACCESS read-only
1223 "The value of sysUpTime at the time that this row was created.
1225 As the table will be created after the sctpAssocTable
1226 creation, this value could be equal to the sctpAssocStartTime
1227 object from the main table."
1229 ::= { sctpLookupRemPortEntry 1 }
1231 -- BY REMOTE HOST NAME
1233 sctpLookupRemHostNameTable OBJECT-TYPE
1234 SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry
1235 MAX-ACCESS not-accessible
1238 "With the use of this table, a list of associations with that
1239 particular host can be retrieved."
1244 ::= { sctpObjects 8 }
1247 sctpLookupRemHostNameEntry OBJECT-TYPE
1248 SYNTAX SctpLookupRemHostNameEntry
1249 MAX-ACCESS not-accessible
1252 "This table is indexed by remote host name and association ID.
1253 Specifying a host name we would get a list of the associations
1254 specifying that host name as the remote one.
1256 Implementors need to be aware that if the size of
1257 sctpAssocRemHostName exceeds 115 octets then OIDs of column
1258 instances in this table will have more than 128 sub-
1259 identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
1262 INDEX { sctpAssocRemHostName,
1265 ::= { sctpLookupRemHostNameTable 1 }
1268 SctpLookupRemHostNameEntry::= SEQUENCE {
1269 sctpLookupRemHostNameStartTime TimeStamp
1272 sctpLookupRemHostNameStartTime OBJECT-TYPE
1274 MAX-ACCESS read-only
1277 "The value of sysUpTime at the time that this row was created.
1279 As the table will be created after the sctpAssocTable
1280 creation, this value could be equal to the sctpAssocStartTime
1281 object from the main table."
1283 ::= { sctpLookupRemHostNameEntry 1 }
1295 -- BY REMOTE PRIMARY IP ADDRESS
1297 sctpLookupRemPrimIPAddrTable OBJECT-TYPE
1298 SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry
1299 MAX-ACCESS not-accessible
1302 "With the use of this table, a list of associations that have
1303 the specified IP address as primary within the remote set of
1304 active addresses can be retrieved."
1306 ::= { sctpObjects 9 }
1309 sctpLookupRemPrimIPAddrEntry OBJECT-TYPE
1310 SYNTAX SctpLookupRemPrimIPAddrEntry
1311 MAX-ACCESS not-accessible
1314 "This table is indexed by primary address and association ID.
1315 Specifying a primary address, we would get a list of the
1316 associations that have the specified remote IP address marked
1318 Implementors need to be aware that if the size of
1319 sctpAssocRemPrimAddr exceeds 114 octets then OIDs of column
1320 instances in this table will have more than 128 sub-
1321 identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
1324 INDEX { sctpAssocRemPrimAddrType,
1325 sctpAssocRemPrimAddr,
1328 ::= { sctpLookupRemPrimIPAddrTable 1 }
1330 SctpLookupRemPrimIPAddrEntry::= SEQUENCE {
1331 sctpLookupRemPrimIPAddrStartTime TimeStamp
1335 sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE
1337 MAX-ACCESS read-only
1347 "The value of SysUpTime at the time that this row was created.
1349 As the table will be created after the sctpAssocTable
1350 creation, this value could be equal to the sctpAssocStartTime
1351 object from the main table."
1353 ::= { sctpLookupRemPrimIPAddrEntry 1 }
1356 -- BY REMOTE IP ADDRESS
1358 sctpLookupRemIPAddrTable OBJECT-TYPE
1359 SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry
1360 MAX-ACCESS not-accessible
1363 "With the use of this table, a list of associations that have
1364 the specified IP address as one of the remote ones can be
1367 ::= { sctpObjects 10 }
1370 sctpLookupRemIPAddrEntry OBJECT-TYPE
1371 SYNTAX SctpLookupRemIPAddrEntry
1372 MAX-ACCESS not-accessible
1375 "This table is indexed by a remote IP address and association
1376 ID. Specifying an IP address we would get a list of the
1377 associations that have the specified IP address included
1378 within the set of remote IP addresses."
1380 INDEX { sctpAssocRemAddrType,
1384 ::= { sctpLookupRemIPAddrTable 1 }
1387 SctpLookupRemIPAddrEntry::= SEQUENCE {
1389 sctpLookupRemIPAddrStartTime TimeStamp
1397 sctpLookupRemIPAddrStartTime OBJECT-TYPE
1399 MAX-ACCESS read-only
1402 "The value of SysUpTime at the time that this row was created.
1404 As the table will be created after the sctpAssocTable
1405 creation, this value could be equal to the sctpAssocStartTime
1406 object from the main table."
1408 ::= { sctpLookupRemIPAddrEntry 1 }
1411 -- 4.1 Conformance Information
1413 sctpMibConformance OBJECT IDENTIFIER ::= { sctpMIB 2 }
1414 sctpMibCompliances OBJECT IDENTIFIER ::= { sctpMibConformance 1 }
1415 sctpMibGroups OBJECT IDENTIFIER ::= { sctpMibConformance 2 }
1418 -- 4.1.1 Units of conformance
1424 sctpLayerParamsGroup OBJECT-GROUP
1425 OBJECTS { sctpRtoAlgorithm,
1436 "Common parameters for the SCTP layer, i.e., for all the
1437 associations. They can usually be referred to as configuration
1440 ::= { sctpMibGroups 1 }
1448 sctpStatsGroup OBJECT-GROUP
1449 OBJECTS { sctpCurrEstab,
1458 sctpOutUnorderChunks,
1461 sctpInUnorderChunks,
1466 sctpDiscontinuityTime,
1467 sctpAssocT1expireds,
1468 sctpAssocT2expireds,
1475 "Statistics group. It includes the objects to collect state
1476 changes in the SCTP protocol local layer and flow control
1479 ::= { sctpMibGroups 2 }
1482 sctpPerAssocParamsGroup OBJECT-GROUP
1483 OBJECTS { sctpAssocRemHostName,
1486 sctpAssocRemPrimAddrType,
1487 sctpAssocRemPrimAddr,
1488 sctpAssocHeartBeatInterval,
1491 sctpAssocOutStreams,
1493 sctpAssocPrimProcess,
1495 sctpAssocDiscontinuityTime,
1499 sctpAssocLocalAddrStartTime,
1500 sctpAssocRemAddrActive,
1501 sctpAssocRemAddrHBActive,
1502 sctpAssocRemAddrRTO,
1503 sctpAssocRemAddrMaxPathRtx,
1504 sctpAssocRemAddrStartTime
1509 "The SCTP group of objects to manage per-association
1510 parameters. These variables include all the SCTP basic
1513 ::= { sctpMibGroups 3 }
1515 sctpPerAssocStatsGroup OBJECT-GROUP
1517 { sctpAssocT1expireds,
1518 sctpAssocT2expireds,
1525 "Per Association Statistics group. It includes the objects to
1526 collect flow control statistics per association."
1528 ::= { sctpMibGroups 4 }
1530 sctpInverseGroup OBJECT-GROUP
1531 OBJECTS { sctpLookupLocalPortStartTime,
1532 sctpLookupRemPortStartTime,
1533 sctpLookupRemHostNameStartTime,
1534 sctpLookupRemPrimIPAddrStartTime,
1535 sctpLookupRemIPAddrStartTime
1540 "Objects used in the inverse lookup tables."
1542 ::= { sctpMibGroups 5 }
1550 -- 4.1.2 Compliance Statements
1553 -- MODULE COMPLIANCES
1556 sctpMibCompliance MODULE-COMPLIANCE
1559 "The compliance statement for SNMP entities which implement
1560 this SCTP MIB Module.
1562 There are a number of INDEX objects that cannot be represented
1563 in the form of OBJECT clauses in SMIv2, but for which we have
1564 the following compliance requirements, expressed in OBJECT
1565 clause form in this description clause:
1567 -- OBJECT sctpAssocLocalAddrType
1568 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)}
1570 -- It is only required to have IPv4 and IPv6 addresses without
1572 -- The address with zone indices is required if an
1573 -- implementation can connect multiple zones.
1575 -- OBJECT sctpAssocLocalAddr
1576 -- SYNTAX InetAddress (SIZE(4|16))
1578 -- An implementation is only required to support globally
1579 -- unique IPv4 and IPv6 addresses.
1581 -- OBJECT sctpAssocRemAddrType
1582 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)}
1584 -- It is only required to have IPv4 and IPv6 addresses without
1586 -- The address with zone indices is required if an
1587 -- implementation can connect multiple zones.
1589 -- OBJECT sctpAssocRemAddr
1590 -- SYNTAX InetAddress (SIZE(4|16))
1592 -- An implementation is only required to support globally
1593 -- unique IPv4 and IPv6 addresses.
1595 " -- closes DESCRIPTION clause of MODULE-COMPLIANCE
1597 MODULE -- this module
1601 MANDATORY-GROUPS { sctpLayerParamsGroup,
1602 sctpPerAssocParamsGroup,
1604 sctpPerAssocStatsGroup
1607 OBJECT sctpAssocRemPrimAddrType
1608 SYNTAX InetAddressType { ipv4(1),
1612 "It is only required to have IPv4 and IPv6 addresses
1613 without zone indices.
1615 The address with zone indices is required if an
1616 implementation can connect multiple zones."
1618 OBJECT sctpAssocRemPrimAddr
1619 SYNTAX InetAddress (SIZE(4|16))
1621 "An implementation is only required to support globally
1622 unique IPv4 and globally unique IPv6 addresses."
1625 OBJECT sctpAssocState
1626 WRITE-SYNTAX INTEGER { deleteTCB(9) }
1627 MIN-ACCESS read-only
1629 "Only the deleteTCB(9) value MAY be set by a management
1630 station at most. A read-only option is also considered to
1631 be compliant with this MIB module description."
1633 GROUP sctpInverseGroup
1635 "Objects used in inverse lookup tables. This should be
1636 implemented, at the discretion of the implementers, for
1637 easier lookups in the association tables"
1639 ::= { sctpMibCompliances 1 }