CISCO-IETF-SCTP-MIB: View SNMP OID List / Download MIB

The MIB module for managing SCTP protocol (RFC 2960).

The algorithm used to determine the timeout value (T3-rtx) used for re-transmitting unacknowledged chunks. Enumeration: 'vanj': 2, 'other': 1.

The minimum value permitted by a SCTP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. Minimum recommended value is 1000 milliseconds. Some telephony applications could require less than 1 second, see [SIGAS] for further information.

The maximum value permitted by a SCTP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. Recommended value is 60000 milliseconds.

Initial value for the Retransmission timer. Recommended value is 3000 milliseconds.

The limit on the total number of SCTP associations the entitycan support. In entities where the maximum number of associations is dynamic, this object should contain the value -1.

Valid cookie life in the 4-way start-up handshake procedure. Recommended value: 60000 milliseconds.

The maximum number of retransmissions at the start-up phase (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts.

The number of SCTP associations for which the current state is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.

The number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has initiated the association attempt.

The number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state: CLOSED -> ESTABLISHED. The remote endpoint has initiated the association attempt.

The number of times that SCTP 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.

The number of times that SCTP 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.

Number of out of the blue packets (SCTP packet correctly formed -right checksum- but the receiver is not able to identify the association to which this packet belongs) received by the host.

Number of SCTP packets received from the peers with an invalid checksum.

Number of SCTP control chunks sent to the peers (no retransmissions included).

Number of SCTP ordered data chunks sent to the peers (no retransmissions included).

Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent to the peers (no retransmissions included).

Number of SCTP control chunks received from the peers (no duplicated included).

Number of SCTP ordered data chunks received from the peers (no duplicated included).

Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received from the peers (no duplicated included).

Number of user messages that have to be fragmented because of the MTU.

Number of user messages reassembled.

Number of SCTP packets received from the peers.

Number of SCTP packets received from the peers.

A table containing SCTP association-specific information.

General common variables and statistics for the whole association.

Association Identification. Value identifying the association (typically the Initiate Verification Tag). If the selected AssocID is the Initiate Verification Tag, this value must not be zero.

Peer's DNS name. If no DNS domain name was received at init time (embedded in the INIT or INIT-ACK chunk) from the peer, this entry will be meaningless, therefore it will contain a NULL value. Otherwise, the remote host name received at init time will be stored.

Local SCTP port number used for this association.

Remote SCTP port number used for this association.

Internet type of primary destination IP address. - unknown (0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address different from IPv4 or IPv6. This value is used in this MIB for error conditions. - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 textual convention [RFC2851]. - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 textual convention [RFC2851] This value will be filled in after INIT or INIT ACK messages have been received (when the primary path is selected by SCTP).

Primary destination IP address. An InetAddress value is always interpreted within the context of an InetAddressType value. This value will be filled in after INIT or INIT ACK messages have been received (when the primary path is selected by SCTP).

The current heartbeat time-out. The recommended default value is 30000 milliseconds.

The state of this SCTP association. As in TCP, the only value which may be set by a management station is deleteTCB. Accordingly, it is appropriate for an agent to return a 'badValue' response if a management station attempts to set this object to any other value. 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. Enumeration: 'established': 4, 'shutdownSent': 6, 'shutdownReceived': 7, 'shutdownPending': 5, 'deleteTCB': 9, 'cookieWait': 2, 'closed': 1, 'shutdownAckSent': 8, 'cookieEchoed': 3.

Inbound Streams according to the negotiation at association start up. This parameter has to be read-only by the manager.

Outbound Streams according to the negotiation at association start up. This parameter has to be read-only by the manager.

The maximum number of data retransmissions in the association context. This value is specific for each association and the upper layer can change it calling the appropriate primitives. This value has to be smaller than the addition of all the maximum number for all the paths (cSctpAssocRemAddressMaxPathRetrans). Recommended value: 10 attempts.

Number of times that T1 timer expired (timer for sending either INIT or COOKIE-ECHO chunks and receiving an acknowledgment).

Number of times that T2-shutdown timer expired (shutdown timer).

Number of data chunks retransmitted to the peer in the current association.

The value of SysUpTime at the time that this row was created.

Expanded table of cSctpAssocTable based on the AssocId index. It shows several interesting data for each local address which takes part in this association.

Local information about the available addresses.

Internet type of local IP address used for this association. - unknown (0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address different from IPv4 or IPv6. This value is used in this MIB for error conditions. - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 textual convention [RFC2851]. - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 textual convention [RFC2851].

The value of a local IP address available for this association. An InetAddress value is always interpreted within the context of an InetAddressType value. If SCTP are using DNS names, the mapping to IP address-es will be done at reception of INIT or INIT_ACK messages.

The value of SysUpTime at the time that this row was created.

Expanded table of cSctpAssocTable based on the AssocId index. It shows several interesting data for each remote peer IP address which is used in this association.

Information about THE most important variables for every remote IP address

Internet type of a remote IP address available for this association. - unknown (0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address different from IPv4 or IPv6. This value is used in this MIB for error conditions. - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 textual convention [RFC2851]. - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 textual convention [RFC2851].

The value of a remote IP address available for this association. An InetAddress value is always interpreted within the context of an InetAddressType value.

The current status of the remote transport address, according to [SCTP]. Active means that the threshold of no answer received from this IP address has not been reached. Inactive means that either no heartbeat was received from this address, or any other message, reaching the threshold defined by the protocol. Enumeration: 'active': 0, 'inactive': 1.

The optional Heartbeat associated to one destination transport address could be active or not (value equal to 0 or 1, respectively). An active destination transport address is the one considered available by a peer endpoint for receiving SCTP packets, as it is described in [cSctp]. Enumeration: 'active': 0, 'inactive': 1.

The current Retransmission Timeout. T3-rtx timer as defined in the protocol SCTP.

Maximum number of DATA retransmissions allowed to a remote IP address before it is considered inactive, as defined in [cSctp]. Recommended value 5 attempts.

Number of DATA retransmissions as defined in [cSctp].

The value of SysUpTime at the time that this row was created.

With the use of this table, a list of associations which use that local port can be got

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

The value of SysUpTime at the time that this row was created.

With the use of this table, a list of associations which use that remote port can be got

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

The value of SysUpTime at the time that this row was created.

With the use of this table, a list of associations with that particular host can be got

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

The value of SysUpTime at the time that this row was created.

With the use of this table, it can be got a list of associations that have that the specified IP address as primary within the remote set of active addresses

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.

The value of SysUpTime at the time that this row was created.

With the use of this table, a list of associations that have the specified IP address as one of the remote ones can be got.

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

The value of SysUpTime at the time that this row was created.

Common parameters for all the associations. They can usually be referred as configuration parameters

The cSctp group of objects to control state changes in the SCTP protocol local layer. They include the data for all the associations.

The cSctp group of objects providing for management of SCTP most common statistics for the local SCTP layer.

The sctp group of objects to manage specific local and remote SCTP variables (local and remote tables). These variables include all the SCTP basic features.

The cSctp group of objects to manage SCTP statistics related to the remote endpoint.

Objects used in the inverse lookup table.

The compliance statement for SNMPv3 entities which implement SCTP. As a remark, the not-accessible objects: cSctpAssocLocalAddressIPType and cSctpAssocRemAddressIPType do not support the dns(4)type since the use of the host names is limited to first stage, when the association is being established. cSctpAssocLocalAddressIP and cSctpAssocRemAddressIP will only accept the size of 4 or 16 because it is only required to support IPv4 and unique IPv6 addresses.