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

The MIB module for managing SCTP implementation.

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

The maximum number of associations that can be supported by this implementation. set to zero to indicate unlimited.

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 ESTABLISH 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 CLOSE state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state. Graceful termination of the association.

Number of bytes received(does not include retransmissions).

Number of bytes sent(does not include retransmissions).

Number of chunks that were discarded.

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

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

Number of SCTP data chunks sent that required order to be maintained. (no retransmissions included).

Number of SCTP data chunks sent that do not required order to be maintained. (no retransmissions included).

Number of SCTP control and data chunks, received from the peers (no retransmissions included).

Number of SCTP control chucks received from peers (no retransmissions included).

Number of SCTP data chunks received that required order to be maintained. (no retransmissions included).

Number of SCTP data chunks received that do not required order to be maintained. (no retransmissions included).

Number datagrams sent(does not include retransmissions).

Number datagrams sent(does not include retransmissions).

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

Number of user messages reassembled.

Number of chunks that were re-transmitted.

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 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).

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).

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, 'retrieval': 10, 'cookieEchoed': 3.

Time association has been in established state.

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 telephone applications could require less than 1 second.

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.

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.

Initial value for the Start-up T1 timer.

Initial value for the Shutdown T2-shutdown timer.

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].

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).

Number of supported congestion Levels.

Current congestion level.

Threshold used to abate congestion level 1.

Threshold used to abate congestion level 2.

Threshold used to abate congestion level 3.

Threshold used to mark onset of congestion level 1.

Threshold used to mark onset of congestion level 2.

Threshold used to mark onset of congestion level 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. This value is specific for each association and the upper layer can be able to change it calling the appropriate primitives. This value has to be smaller than the addition of all the maximum number for all the paths (sctpAssocRemAddressMaxPathRetran). Recommended value: 10 attempts.

The Maximum Transmission Size to be used by this association. The size will the smallest MTU size supported by any of the IP Addresses used by the association.

The current local receive window size for this association.

Low water mark for Local Receive Window Size.

Number of times the Local Receive window reached zero bytes.

The Remote Receive Window Size for this association.

Low water mark for Remote Receive Window Size.

Number of times the Remote Receive window reached zero bytes.

Number of data grams waiting to be sent.

High water mark for data grams waiting to be sent.

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

Number of bytes sent by this association.

Number of bytes received by this association.

Total number of Chucks discarded by this association.

Total number of Chucks received by this association.

Number of control Chucks received by this association.

Number of Chucks received by this association where order is required.

Number of Chucks received by this association where order is not required.

Number of Chucks received out of order by this association.

Total number of Chucks retransmitted by this association.

Total number of Chucks sent by this association.

Number of control Chucks sent by this association.

Number of Chucks sent by this association where order is required.

Number of Chucks sent by this association where order is not required.

Number of packets received by this association.

Number of packets sent by this association.

An object that allows entries in this table to be created and deleted using the RowStatus convention. A row in this table will be created after creating the TCB in both sides of the association. The creation of this row implies the creation of at least another row (depending on the number of local and remote addresses) in the tables sctpAssocLocalAddressTable and sctpAssocRemAddressTable. A row is deleted in sctpAssocTable when an association turns down (i.e., when the TCB is deleted according to [sctp] in both sides of the association). The deletion of a row in sctpAssocTable implies the deletion of the tables related to this association (sctpAssocLocalAddressTable and sctpAssocRemAddressTable). Also, a row is deleted in sctpAssocTable when a set operation is received from the manager with destroy option.

Expanded table of ceSctpAssocTable 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.

An object that allows entries in this table to be created and deleted using the RowStatus convention. A row in this table will be created per local IP address defined for this association. The creation takes part when a new row in the sctpAssocTable is created or when a new IP address is added in the local interface (if this function is enabled by the SCTP layer). A row in this table will be deleted per local IP address reserved for the association when the corresponding row in sctpAssocTable is deleted or when an IP address is removed from the local interface (if this function is enabled by the SCTP layer).

Expanded table of ceSctpAssocTable 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 - Destination is alive and active inActive - Destination used as source address only failed - Destination has failed Enumeration: 'active': 0, 'failed': 2, 'inactive': 1.

The current Retransmision Time-Out. T3-rtx timer as defined in the protocol SCTP.

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

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

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

Number of DATA retransmissions as defined in [sctp].

Smoothed Round Trip Time in milliseconds.

An object that allows entries in this table to be created and deleted using the RowStatus convention. A row in this table will be created per remote IP address defined for this association. The creation takes part when a new row in the sctpAssocTable is created or when a new IP address is added in the remote interface (if this function is enabled by the SCTP layer). A row in this table will be deleted per remote IP address reserved for the association when the corresponding row in sctpAssocTable is deleted or when an IP address is removed from the local interface (if this function is enabled by the SCTP layer).

The sctp group of objects providing for management of SCTP entities. Common parameters for the protocol.

The sctp group of objects to control state changes in the SCTP protocol.

The sctp group of objects providing for management of SCTP general statistics.

The sctp group of objects to manage specific local and remote SCTP variables (local and remote tables).

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

The compliance statement for SNMPv3 entities which implement SCTP.