Network Working Group J. Pastor
Request for Comments: 3873 M. Belinchon
Category: Standards Track Ericsson
September 2004
Network Working Group J. Pastor
Request for Comments: 3873 M. Belinchon
Category: Standards Track Ericsson
September 2004
Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)
流控制传输协议（SCTP）管理信息库（MIB）
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
The Stream Control Transmission Protocol (SCTP) is a reliable transport protocol operating on top of a connectionless packet network such as IP. It is designed to transport public switched telephone network (PSTN) signaling messages over the connectionless packet network, but is capable of broader applications.
流控制传输协议（SCTP）是一种在IP等无连接分组网络上运行的可靠传输协议。它设计用于通过无连接分组网络传输公共交换电话网（PSTN）信令消息，但具有更广泛的应用能力。
This memo defines the Management Information Base (MIB) module which describes the minimum set of objects needed to manage the implementation of the SCTP.
本备忘录定义了管理信息库（MIB）模块，该模块描述了管理SCTP实施所需的最小对象集。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Abbreviations. . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. MIB Structure. . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. SCTP Objects . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. SCTP Statistics. . . . . . . . . . . . . . . . . 4
3.1.2. SCTP Parameters. . . . . . . . . . . . . . . . . 5
3.1.3. MIB Tables . . . . . . . . . . . . . . . . . . . 5
3.1.3.1. Association Table. . . . . . . . . . . 5
3.1.3.2. Reverse Lookup Table . . . . . . . . . 8
3.2. Conformance. . . . . . . . . . . . . . . . . . . . . . . 9
4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Abbreviations. . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. MIB Structure. . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. SCTP Objects . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. SCTP Statistics. . . . . . . . . . . . . . . . . 4
3.1.2. SCTP Parameters. . . . . . . . . . . . . . . . . 5
3.1.3. MIB Tables . . . . . . . . . . . . . . . . . . . 5
3.1.3.1. Association Table. . . . . . . . . . . 5
3.1.3.2. Reverse Lookup Table . . . . . . . . . 8
3.2. Conformance. . . . . . . . . . . . . . . . . . . . . . . 9
4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Compiling Notes. . . . . . . . . . . . . . . . . . . . . . . . 42
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1. Normative References . . . . . . . . . . . . . . . . . . 42
6.2. Informative References . . . . . . . . . . . . . . . . . 43
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 44
8. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 45
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 45
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 46
5. Compiling Notes. . . . . . . . . . . . . . . . . . . . . . . . 42
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1. Normative References . . . . . . . . . . . . . . . . . . 42
6.2. Informative References . . . . . . . . . . . . . . . . . 43
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 44
8. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 45
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 45
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 46
This memo defines the Management Information Base (MIB) module which describes managed objects for implementations of the SCTP.
本备忘录定义了管理信息库（MIB）模块，该模块描述了SCTP实现的托管对象。
The document starts with a brief description of the SNMP framework and continues with the MIB explanation and security consideration sections among others.
本文档首先简要介绍SNMP框架，然后是MIB说明和安全注意事项部分。
The managed objects in this MIB module are based on [RFC2012] update: "Management Information Base for the Transmission Control Protocol (TCP)" referred as [TCPMIB] (work in progress), and RFC 3291 "Textual Conventions for Internet Network Addresses" [RFC3291].
此MIB模块中的受管对象基于[RFC2012]更新：“传输控制协议（TCP）的管理信息库”，称为[TCPMIB]（进行中的工作），以及RFC 3291“Internet网络地址的文本约定”[RFC3291]。
Terms related to the SCTP architecture are explained in [RFC2960]. Other specific abbreviations are listed below.
[RFC2960]中解释了与SCTP体系结构相关的术语。下面列出了其他特定缩写。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
DNS - Domain Name System IANA - Internet Assigned Numbers Authority IETF - Internet Engineering Task Force IP - Internet Protocol MIB - Management Information Base RFC - Request For Comments RTO - Retransmission Time Out SCTP - Stream Control Transmission Protocol SMI - Structure of Management Information SNMP - Simple Network Management Protocol TCB - Transmission Control Block TCP - Transmission Control Protocol
DNS-域名系统IANA-互联网分配号码管理局IETF-互联网工程任务组IP-互联网协议MIB-管理信息库RFC-征求意见RTO-重传超时SCTP-流控制传输协议SMI-管理信息结构SNMP-简单网络管理协议TCB-传输控制块TCP-传输控制协议
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This chapter explains the main objects this MIB defines. A detailed view of the MIB structure with the OID values is below.
本章介绍MIB定义的主要对象。下面是具有OID值的MIB结构的详细视图。
MIB-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
| +--(1) sctpStats
| | |
| | +-- <scalars>
| |
| +--(2)sctpParameters
| | |
| | +-- <scalars>
| |
| +--(3) sctpAssocTable
| |
| +--(4) sctpAssocLocalAddrTable
| |
| +--(5) sctpAssocRemAddrTable
| |
| +--(6) sctpLookupLocalPortTable
| |
| +--(7) sctpLookupRemPortTable
| |
| +--(8) sctpLookupRemHostNameTable
| |
| +--(9) sctpLookupRemPrimIPAddrTable
| |
| +--(10) sctpLookupRemIPAddrTable
MIB-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
| +--(1) sctpStats
| | |
| | +-- <scalars>
| |
| +--(2)sctpParameters
| | |
| | +-- <scalars>
| |
| +--(3) sctpAssocTable
| |
| +--(4) sctpAssocLocalAddrTable
| |
| +--(5) sctpAssocRemAddrTable
| |
| +--(6) sctpLookupLocalPortTable
| |
| +--(7) sctpLookupRemPortTable
| |
| +--(8) sctpLookupRemHostNameTable
| |
| +--(9) sctpLookupRemPrimIPAddrTable
| |
| +--(10) sctpLookupRemIPAddrTable
|
|
+--(2)sctpMibConformance
|
+--(1) sctpMibCompliances
| |
| +--(1) sctpMibCompliance
|
+--(2) sctpMibGroups
|
+--(1) sctpLayerParamsGroup
|
+--(2) sctpStatsGroup
|
+--(3) sctpPerAssocParamsGroup
|
+--(4) sctpInverseGroup
|
|
+--(2)sctpMibConformance
|
+--(1) sctpMibCompliances
| |
| +--(1) sctpMibCompliance
|
+--(2) sctpMibGroups
|
+--(1) sctpLayerParamsGroup
|
+--(2) sctpStatsGroup
|
+--(3) sctpPerAssocParamsGroup
|
+--(4) sctpInverseGroup
The main groups are explained further in the MIB definition.
MIB定义中进一步解释了主要组。
This branch contains the SCTP statistics and general parameters (both of them scalars) and the SCTP MIB tables.
该分支包含SCTP统计信息和常规参数（两者都是标量）以及SCTP MIB表。
The SCTP MIB includes both Counter32s and Counter64s to deal with statistics. Counter64s are used for those counters, which are likely to wrap around in less than one hour, according to [RFC2863].
SCTP MIB包括计数器32和计数器64，用于处理统计数据。根据[RFC2863]的说法，计数器64用于那些可能在不到一个小时内完成的计数器。
In addition Gauge32 is also used.
此外，还使用了量规32。
These statistics are based on the TCP model, but adapted to the SCTP states. They store the number of successful association attempts, how many associations have been initiated by the local or the remote SCTP layer, and the number of associations terminated in a graceful (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE procedure).
这些统计数据基于TCP模型，但适用于SCTP状态。它们存储成功关联尝试的次数、本地或远程SCTP层已启动的关联数以及以正常方式（通过关闭过程）或不正常方式（通过关闭过程）终止的关联数。
This set of objects specifies statistics related to the whole SCTP layer. There are, e.g., statistics related to both SCTP packets and SCTP chunks.
这组对象指定与整个SCTP层相关的统计信息。例如，存在与SCTP数据包和SCTP数据块相关的统计信息。
Statistics related to a specific association, or local/remote IP addresses are defined inside their associated table.
与特定关联或本地/远程IP地址相关的统计信息在其关联表中定义。
This section of the MIB contains the general variables for the SCTP protocol. Maximum, minimum, initial and default values are listed here.
MIB的这一部分包含SCTP协议的常规变量。此处列出了最大值、最小值、初始值和默认值。
SCTP RTO mechanism definition is based on the TCP MIB [TCPMIB]. In SCTP, only options 'other' and 'vanj' are valid since SCTP defines Van Jacobson's algorithm (vanj) as the one to be used to calculate RTO. 'Other' is left for future use.
SCTP RTO机制定义基于TCP MIB[TCPMIB]。在SCTP中，只有选项“其他”和“vanj”有效，因为SCTP将Van Jacobson算法（vanj）定义为用于计算RTO的算法“其他”留作将来使用。
There are several tables included in the SCTP MIB. The first group deals with the SCTP association variables and is composed of a main and two extended tables. The second group is a bunch of tables used to perform reverse lookups.
SCTP MIB中包含多个表。第一组处理SCTP关联变量，由一个主表和两个扩展表组成。第二组是一组用于执行反向查找的表。
It is NOT possible to create rows in any table (sctpAssocTable, sctpAssocLocalAddrTable, sctpRemAddrTable and Reverse Lookup tables) using SNMP.
无法使用SNMP在任何表（sctpAssocTable、SCTPASSOCLOCALADDRABLE、SCTPREMADDRABLE和反向查找表）中创建行。
It is NOT possible to delete rows in any table using SNMP except in sctpAssocTable under the particular conditions explained below.
在下面解释的特定条件下，使用SNMP无法删除任何表中的行，sctpAssocTable除外。
The sctpAssocTable is the main MIB table, where all the association related information is stored on a per association basis. It is structured according to expanded tables. The main table is called sctpAssocTable and is indexed by sctpAssocId (the association identification). This is a value that uniquely identifies an association. The MIB does not restrict what value must be written here, however it must be unique within the table.
sctpAssocTable是主MIB表，其中所有关联相关信息都以每个关联为基础存储。它是根据扩展的表来构造的。主表称为sctpAssocTable，并由sctpAssocId（关联标识）索引。这是唯一标识关联的值。MIB不限制此处必须写入的值，但它在表中必须是唯一的。
The sctpAssoc index is also shared by two more tables: - sctpAssocLocalAddrTable: to store the local IP address(es). - sctpAssocRemAddrTable: to store the remote addresses and the per-remote-address related information.
sctpAssoc索引还由另外两个表共享：-SCTPASSOCLOCALADDRABLE:用于存储本地IP地址sctpAssocRemAddrTable：存储远程地址和每个远程地址的相关信息。
Entries in the sctpAssocTable are created when trying to establish the association, i.e., when sending the COOKIE-ECHO message (originating side) or the COOKIE-ACK message (server side). At this point, i.e., at established state, all entry fields are filled in with valid values.
sctpAssocTable中的条目是在尝试建立关联时创建的，即在发送COOKIE-ECHO消息（发起端）或COOKIE-ACK消息（服务器端）时创建的。此时，即在已建立状态下，所有输入字段都用有效值填充。
Note: The following representation is a conceptual mode of describing the relationship between the tables in this MIB. Note that the real relationship of the tables is by sharing an index, so tables are not truly within tables. Every entry is explained when defining the corresponding objects in the MIB.
注意：以下表示是描述此MIB中表之间关系的概念模式。请注意，表的真正关系是通过共享索引实现的，因此表并不真正在表中。在MIB中定义相应的对象时，将解释每个条目。
mib-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
. .
. .
|
+--(3) sctpAssocTable
| |
| +--(1) sctpAssocId (index)
| |
| +--(2) sctpAssocRemHostName
| |
| +--(3) sctpAssocLocalPort
| |
| +--(4) sctpAssocRemPort
| |
| +--(5) sctpAssocRemPrimAddrType
| |
| +--(6) sctpAssocRemPrimAddr
| |
| +--(7) sctpAssocHeartBeatInterval
| |
| +--(8) sctpAssocState
| |
| +--(9) sctpAssocInStreams
| |
| +--(10) sctpAssocOutStreams
| |
| +--(11) sctpAssocMaxRetr
| |
| +--(12) sctpAssocPrimProcess
| |
| +--(13) sctpAssocT1expireds
| |
| +--(14) sctpAssocT2expireds
| |
| +--(15) sctpAssocRtxChunks
| |
| +--(16) sctpAssocStartTime
| |
mib-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
. .
. .
|
+--(3) sctpAssocTable
| |
| +--(1) sctpAssocId (index)
| |
| +--(2) sctpAssocRemHostName
| |
| +--(3) sctpAssocLocalPort
| |
| +--(4) sctpAssocRemPort
| |
| +--(5) sctpAssocRemPrimAddrType
| |
| +--(6) sctpAssocRemPrimAddr
| |
| +--(7) sctpAssocHeartBeatInterval
| |
| +--(8) sctpAssocState
| |
| +--(9) sctpAssocInStreams
| |
| +--(10) sctpAssocOutStreams
| |
| +--(11) sctpAssocMaxRetr
| |
| +--(12) sctpAssocPrimProcess
| |
| +--(13) sctpAssocT1expireds
| |
| +--(14) sctpAssocT2expireds
| |
| +--(15) sctpAssocRtxChunks
| |
| +--(16) sctpAssocStartTime
| |
| +--(17) sctpAssocDiscontinuityTime
|
|
+--(4) sctpAssocLocalAddrTable
| |
| |--(-) sctpAssocId (shared index)
| |
| +--(1) sctpAssocLocalAddrType(index)
| |
| +--(2) sctpAssocLocalAddr (index)
| |
| +--(3) sctpAssocLocalAddrStartTime
|
|
+--(5) sctpAssocRemAddrTable
| |
| |--(-) sctpAssocId (shared index)
| |
| +--(1) sctpAssocRemAddrType (index)
. |
. +--(2) sctpAssocRemAddr (index)
. |
+--(3) sctpAssocRemAddrActive
|
+--(4) sctpAssocRemAddrHBActive
|
+--(5) sctpAssocRemAddrRTO
|
+--(6) sctpAssocRemAddrMaxPathRtx
|
+--(7) sctpAssocRemAddrRtx
|
+--(8) sctpAssocRemAddrStartTime
| +--(17) sctpAssocDiscontinuityTime
|
|
+--(4) sctpAssocLocalAddrTable
| |
| |--(-) sctpAssocId (shared index)
| |
| +--(1) sctpAssocLocalAddrType(index)
| |
| +--(2) sctpAssocLocalAddr (index)
| |
| +--(3) sctpAssocLocalAddrStartTime
|
|
+--(5) sctpAssocRemAddrTable
| |
| |--(-) sctpAssocId (shared index)
| |
| +--(1) sctpAssocRemAddrType (index)
. |
. +--(2) sctpAssocRemAddr (index)
. |
+--(3) sctpAssocRemAddrActive
|
+--(4) sctpAssocRemAddrHBActive
|
+--(5) sctpAssocRemAddrRTO
|
+--(6) sctpAssocRemAddrMaxPathRtx
|
+--(7) sctpAssocRemAddrRtx
|
+--(8) sctpAssocRemAddrStartTime
Both sctpAssocLocalAddrTable and sctpAssocRemAddrTable are indexed by addresses. 'Addr' and 'AddrType' use the syntax InetAddress and InetAddressType defined in the Textual Conventions for Internet Network Address (RFC3291). The InetAddressType TC has codepoints for unknown, IPv4, IPv6, non-global IPv4, non-global IPv6, and DNS addresses, but only the IPv4 and IPv6 address types are required to be supported by implementations of this MIB module. Implementations that connect multiple zones are expected to support the non-global IPv4 and non-global IPv6 address types as well.
SCTPASSOCLOCALADDRABLE和SCTPASSOCREMADDRABLE都是按地址索引的。”Addr'和'AddrType'使用在Internet网络地址（RFC3291）的文本约定中定义的语法InetAddress和InetAddressType。InetAddressType TC具有未知、IPv4、IPv6、非全局IPv4、非全局IPv6和DNS地址的代码点，但此MIB模块的实现只需要支持IPv4和IPv6地址类型。连接多个区域的实现预计也支持非全局IPv4和非全局IPv6地址类型。
Note that DNS addresses are not used in this MIB module. They are always resolved to the on-the-wire form prior to connection setup, and the on-the-wire form is what appears in the MIB objects.
请注意，此MIB模块中不使用DNS地址。在连接设置之前，它们始终解析为在线表单，在线表单是MIB对象中显示的内容。
The sctpAssocLocalAddrTable table will have as many entries as local IP addresses have been defined for the association. The sctpAssocRemAddrTable table will contain as many entries as remote IP addresses are known to reach the peer. For the multihoming concept see reference RFC2960.
SCTPASSOCLOCALADDRABLE表的条目数与为关联定义的本地IP地址数相同。sctpAssocRemAddrTable表将包含已知到达对等方的远程IP地址的尽可能多的条目。有关多址概念，请参阅参考RFC2960。
To keep the name of the remote peer (when provided by the peer at initialization time), an entry has been created in the sctpAssocTable called sctpAssocRemHostName. When no DNS name is provided by the remote endpoint, this value will be NULL (zero-length string). Otherwise, the received DNS name will be stored here.
为了保留远程对等方的名称（当对等方在初始化时提供该名称时），已在名为sctpAssocRemHostName的sctpAssocTable中创建了一个条目。当远程端点未提供DNS名称时，此值将为NULL（零长度字符串）。否则，接收到的DNS名称将存储在此处。
If it is necessary to abort an existing association, the value deleteTCB(9) must be written in the variable sctpAssocState. That is the only way to delete rows in any of the mentioned tables.
如果需要中止现有关联，则必须在变量sctpAssocState中写入值deleteTCB（9）。这是删除上述任何表中的行的唯一方法。
There are five reverse lookup tables to help management applications efficiently access conceptual rows in other tables. These tables allow management applications to avoid expensive tree walks through large numbers of associations.
有五个反向查找表可帮助管理应用程序有效地访问其他表中的概念行。这些表允许管理应用程序避免通过大量关联进行昂贵的树遍历。
All of these tables are optional. If these tables are implemented, an entry in them must be created after the entry in the main table (sctpAssocTable) associated with it has been created. This ensures that the field indexing the lookup table exists.
所有这些表都是可选的。如果实现了这些表，则必须在创建与之关联的主表（sctpAssocTable）中的条目后创建其中的条目。这样可以确保索引查找表的字段存在。
The defined reverse lookup tables allow for performing a lookup using the following variables:
定义的反向查找表允许使用以下变量执行查找：
- Local Port: It allows a management application to find all the associations that use a specific local port - Remote Port: It allows a management application to find all the associations that use a specific remote port - Remote Host Name: It allows a management application to find all the associations with a specific host name. - Remote Primary IP Address: It allows a management application to find all the associations that use a specific remote IP address as primary. - Remote IP address: a management application to find all the associations that use a specific remote IP address.
- 本地端口：允许管理应用程序查找使用特定本地端口的所有关联-远程端口：允许管理应用程序查找使用特定远程端口的所有关联-远程主机名：允许管理应用程序查找使用特定主机名的所有关联。-远程主IP地址：它允许管理应用程序查找将特定远程IP地址用作主IP地址的所有关联。-远程IP地址：用于查找使用特定远程IP地址的所有关联的管理应用程序。
As an example the picture below shows the table to look up by local port.
作为示例，下图显示了要按本地端口查找的表。
MIB-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
. .
. .
| |
| +--(6) sctpLookupLocalPortTable
| | |
. . +--(-) sctpAssocLocalPort (shared index)
. . |
+--(-) sctpAssocId (shared index)
|
+--(1) sctpLookupLocalPortStartTime
MIB-2 {1 3 6 1 2 1}
+--(104)sctpMIB
|
+--(1) sctpObjects
| |
. .
. .
| |
| +--(6) sctpLookupLocalPortTable
| | |
. . +--(-) sctpAssocLocalPort (shared index)
. . |
+--(-) sctpAssocId (shared index)
|
+--(1) sctpLookupLocalPortStartTime
It is not possible for the operator to either create or delete rows in these tables. The rows in this table will dynamically appear and be removed as the corresponding entries in sctpAssocTable are.
操作员无法在这些表中创建或删除行。此表中的行将动态显示并删除，因为sctpAssocTable中的相应条目是可用的。
The conformance section recommends all the inverse lookup tables in this MIB as optional. General layer and per association parameters and statistics are considered mandatory.
一致性部分建议将此MIB中的所有反向查找表作为可选表。一般图层和每个关联参数和统计信息被认为是强制性的。
IP addresses use the global IPv4 and global IPv6 address formats. Unknown value and DNS name formats are not used. Names, if present, are stored in the sctpRemoteHostName variable.
IP地址使用全局IPv4和全局IPv6地址格式。未使用未知值和DNS名称格式。名称（如果存在）存储在sctpRemoteHostName变量中。
SCTP-MIB DEFINITIONS ::= BEGIN
SCTP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32,
Counter32, Counter64, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TimeStamp, TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB; -- [RFC3291]
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32,
Counter32, Counter64, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TimeStamp, TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB; -- [RFC3291]
sctpMIB MODULE-IDENTITY LAST-UPDATED "200409020000Z" -- 2nd September 2004 ORGANIZATION "IETF SIGTRAN Working Group" CONTACT-INFO " WG EMail: sigtran@ietf.org
sctpMIB模块标识最后更新的“200409020000Z”--2004年9月2日组织“IETF SIGTRAN工作组”联系方式工作组电子邮件：sigtran@ietf.org
Web Page:
http://www.ietf.org/html.charters/sigtran-charter.html
Web Page:
http://www.ietf.org/html.charters/sigtran-charter.html
Chair: Lyndon Ong Ciena Corporation 0480 Ridgeview Drive Cupertino, CA 95014 USA Tel: Email: lyong@ciena.com
主席：Lyndon Ong Ciena Corporation 0480 Ridgeview Drive Cupertino，CA 95014美国电话：电子邮件：lyong@ciena.com
Editors: Maria-Carmen Belinchon R&D Department Ericsson Espana S. A. Via de los Poblados, 13 28033 Madrid Spain Tel: +34 91 339 3535 Email: Maria.C.Belinchon@ericsson.com
编辑：Maria Carmen Belinchon研发部爱立信Espana S.A.Via de los Poblados，13 28033西班牙马德里电话：+34 91 339 3535电子邮件：Maria.C。Belinchon@ericsson.com
Jose-Javier Pastor-Balbas R&D Department Ericsson Espana S. A. Via de los Poblados, 13 28033 Madrid Spain Tel: +34 91 339 1397 Email: J.Javier.Pastor@ericsson.com " DESCRIPTION "The MIB module for managing SCTP implementations.
Jose Javier Pastor Balbas研发部爱立信Espana S.A.Via de los Poblados，13 28033西班牙马德里电话：+34 91 339 1397电子邮件：J.Javier。Pastor@ericsson.com“描述”用于管理SCTP实现的MIB模块。
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. "
版权所有（C）互联网协会（2004年）。此版本的MIB模块是RFC 3873的一部分；有关完整的法律通知，请参见RFC本身。"
REVISION "200409020000Z" -- 2nd September 2004
修订版“200409020000Z”-2004年9月2日
DESCRIPTION " Initial version, published as RFC 3873"
说明“初始版本，发布为RFC 3873”
::= { mib-2 104 }
::= { mib-2 104 }
-- the SCTP base variables group
--SCTP基本变量组
sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 }
sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 }
sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 }
sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 }
sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 }
sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 }
-- STATISTICS
-- **********
-- STATISTICS
-- **********
-- STATE-RELATED STATISTICS
--与国家有关的统计
sctpCurrEstab OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of associations for which the current state is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." REFERENCE "Section 4 in RFC2960 covers the SCTP Association state diagram."
sctpCurrEstab对象类型语法量表32 MAX-ACCESS只读状态当前描述“当前状态为已建立、关机接收或关机挂起的关联数”。参考“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpStats 1 }
::= { sctpStats 1 }
sctpActiveEstabs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "Section 4 in RFC2960 covers the SCTP Association state diagram."
SCTPActivieStabs对象类型语法计数器32 MAX-ACCESS只读状态当前描述“关联从COOKIE-Echored状态直接转换到已建立状态的次数：COOKIE-Echored->已建立。上层启动了关联尝试。”参考“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpStats 2 }
::= { sctpStats 2 }
sctpPassiveEstabs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "Section 4 in RFC2960 covers the SCTP Association state diagram."
sctpPassiveEstabs对象类型语法计数器32 MAX-ACCESS只读状态当前描述“关联从关闭状态直接转换到已建立状态的次数：关闭->已建立。远程终结点已启动关联尝试。”参考“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpStats 3 }
::= { sctpStats 3 }
sctpAborteds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "Section 4 in RFC2960 covers the SCTP Association state diagram."
sctpAborteds对象类型语法计数器32 MAX-ACCESS只读状态当前描述“关联使用原语'ABORT'从任何状态直接转换到关闭状态的次数：AnyState--ABORT-->关闭。关联的非正常终止。”参考“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpStats 4 }
::= { sctpStats 4 }
sctpShutdowns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "Section 4 in RFC2960 covers the SCTP Association state diagram."
sctpShutdowns对象类型语法计数器32 MAX-ACCESS只读状态当前描述“关联从SHUTDOWN-SENT状态或SHUTDOWN-ACK-SENT状态直接转换到关闭状态的次数。关联的正常终止。”参考“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpStats 5 }
::= { sctpStats 5 }
-- OTHER LAYER STATISTICS
--其他层统计信息
sctpOutOfBlues OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "Section 8.4 in RFC2960 deals with the Out-Of-The-Blue (OOTB) packet definition and procedures."
sctpOutOfBlues对象类型语法计数器32 MAX-ACCESS只读状态当前描述“主机接收到的蓝包数。蓝包是一个格式正确的SCTP包，包括正确的校验和，但接收方无法识别相应的关联。”参考“RFC2960中的第8.4节涉及突发事件（OOTB）数据包定义和过程。”
::= { sctpStats 6 }
::= { sctpStats 6 }
sctpChecksumErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP packets received with an invalid checksum." REFERENCE "The checksum is located at the end of the SCTP packet as per Section 3.1 in RFC2960. RFC3309 updates SCTP to use a 32 bit CRC checksum."
sctpChecksumErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“使用无效校验和接收的SCTP数据包的数量。”参考“根据RFC2960中的第3.1节，校验和位于SCTP数据包的末尾。RFC3309更新SCTP以使用32位CRC校验和。”
::= { sctpStats 7 }
::= { sctpStats 7 }
sctpOutCtrlChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP control chunks sent (retransmissions are not included). Control chunks are those chunks different from DATA." REFERENCE "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as those chunks different from those that contain user information, i.e., DATA chunks."
sctpOutCtrlChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“发送的SCTP控制块的数量（不包括重传）。控制块是与数据不同的块。”参考RFC2960中的1.3.5和1.4节将控制块称为与包含用户信息的块不同的块，即数据块
::= { sctpStats 8 }
::= { sctpStats 8 }
sctpOutOrderChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP ordered data chunks sent (retransmissions are not included)." REFERENCE "Section 3.3.1 in RFC2960 defines the ordered data chunk."
sctpOutOrderChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“发送的SCTP有序数据块的数量（不包括重传）。“参考”RFC2960中的第3.3.1节定义了有序数据块
::= { sctpStats 9 }
::= { sctpStats 9 }
sctpOutUnorderChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included)." REFERENCE "Section 3.3.1 in RFC2960 defines the unordered data chunk."
sctpOutUnorderChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“发送的SCTP无序块（U位设置为1的数据块）的数量（不包括重传）。“参考”RFC2960中的第3.3.1节定义了无序数据块。”
::= { sctpStats 10 }
::= { sctpStats 10 }
sctpInCtrlChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP control chunks received (no duplicate chunks included)." REFERENCE "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as those chunks different from those that contain user information, i.e., DATA chunks."
sctpInCtrlChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收的SCTP控制块的数量（不包括重复块）。“参考”RFC2960中的第1.3.5和1.4节将控制块称为与包含用户信息的块不同的块，即数据块
::= { sctpStats 11 }
::= { sctpStats 11 }
sctpInOrderChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP ordered data chunks received (no duplicate chunks included)."
sctpInOrderChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的SCTP有序数据块的数量（不包括重复块）。”
REFERENCE "Section 3.3.1 in RFC2960 defines the ordered data chunk."
参考“RFC2960中的第3.3.1节定义了有序数据块。”
::= { sctpStats 12 }
::= { sctpStats 12 }
sctpInUnorderChunks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included)." REFERENCE "Section 3.3.1 in RFC2960 defines the unordered data chunk."
SCTPinUnderChunks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的SCTP无序块（U位设置为1的数据块）的数量（不包括重复块）。“参考”RFC2960中的第3.3.1节定义了无序数据块。”
::= { sctpStats 13 }
::= { sctpStats 13 }
sctpFragUsrMsgs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION
sctpFragUsrMsgs对象类型语法计数器64 MAX-ACCESS只读状态当前说明
"The number of user messages that have to be fragmented because of the MTU."
“由于MTU而必须分段的用户邮件数。”
::= { sctpStats 14 }
::= { sctpStats 14 }
sctpReasmUsrMsgs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of user messages reassembled, after conversion into DATA chunks." REFERENCE "Section 6.9 in RFC2960 includes a description of the reassembly process."
sctpReasmUsrMsgs对象类型语法计数器64 MAX-ACCESS只读状态当前说明“转换为数据块后重新组装的用户消息数。”RFC2960中的“参考”第6.9节包括重新组装过程的说明
::= { sctpStats 15 }
::= { sctpStats 15 }
sctpOutSCTPPacks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP packets sent. Retransmitted DATA chunks are included."
SCTPOUTPCTPPACKS对象类型语法计数器64 MAX-ACCESS只读状态当前描述“发送的SCTP数据包数。包括重新传输的数据块。”
::= { sctpStats 16 }
::= { sctpStats 16 }
sctpInSCTPPacks OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SCTP packets received. Duplicates are included."
sctpInSCTPPacks对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的SCTP数据包的数量。包括重复数据包。”
::= { sctpStats 17 }
::= { sctpStats 17 }
sctpDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "The inclusion of this object is recommended by RFC2578."
SCTPYTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“最近一次任何一个或多个此常规统计计数器出现中断时的系统正常运行时间值。相关计数器是与SCTP层统计信息（定义见sctpStats分支）中包含的任何Counter32或Counter64对象的此接口相关联的特定实例。如果自上次重新初始化本地管理子系统以来未发生此类中断，则此对象包含零值。“参考”RFC2578建议包含此对象
::= { sctpStats 18 }
::= { sctpStats 18 }
-- PROTOCOL GENERAL VARIABLES
-- **************************
-- PROTOCOL GENERAL VARIABLES
-- **************************
sctpRtoAlgorithm OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- Other new one. Future use
vanj(2) -- Van Jacobson's algorithm
}
sctpRtoAlgorithm OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- Other new one. Future use
vanj(2) -- Van Jacobson's algorithm
}
MAX-ACCESS read-only STATUS current DESCRIPTION "The algorithm used to determine the timeout value (T3-rtx) used for re-transmitting unacknowledged chunks." REFERENCE "Section 6.3.1 and 6.3.2 in RFC2960 cover the RTO calculation and retransmission timer rules." DEFVAL {vanj} -- vanj(2)
MAX-ACCESS只读状态当前描述“用于确定用于重新传输未确认数据块的超时值（T3 rtx）的算法。”RFC2960中的“参考”第6.3.1节和第6.3.2节介绍RTO计算和重传计时器规则。“DEFVAL{vanj}--vanj（2）
::= { sctpParams 1 }
::= { sctpParams 1 }
sctpRtoMin OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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.
SCTPTOMIN对象类型语法无符号32单位“毫秒”最大访问只读状态当前说明SCTP实现允许的重传超时值的最小值，以毫秒为单位。此类型对象的更精确语义取决于用于确定重传超时值的算法。
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." DEFVAL {1000} -- milliseconds
此对象的值必须小于或等于stcpRtoMax的值。“deffal{1000}--毫秒
::= { sctpParams 2 }
::= { sctpParams 2 }
sctpRtoMax OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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.
sctpRtoMax对象类型语法无符号32单位“毫秒”最大访问只读状态当前说明SCTP实现允许的重传超时值的最大值，以毫秒为单位。此类型对象的更精确语义取决于用于确定重传超时值的算法。
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." DEFVAL {60000} -- milliseconds
此对象的值必须大于或等于stcpRtoMin的值。“deffal{60000}--毫秒
::= { sctpParams 3 }
::= { sctpParams 3 }
sctpRtoInitial OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The initial value for the retransmission timer.
SCTProInitial对象类型语法Unsigned32单位“毫秒”最大访问只读状态当前描述“重传计时器的初始值”。
A retransmission time value of zero means immediate re-transmission." DEFVAL {3000} -- milliseconds
重传时间值为零表示立即重传。“DEFVAL{3000}--毫秒
::= { sctpParams 4 }
::= { sctpParams 4 }
sctpMaxAssocs OBJECT-TYPE SYNTAX Integer32 (-1 | 0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "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."
sctpMaxAssocs对象类型语法整数32（-1 | 0..2147483647）MAX-ACCESS只读状态当前描述“实体可支持的关联总数限制。在最大关联数为动态的实体中，此对象应包含值-1。”
::= { sctpParams 5 }
::= { sctpParams 5 }
sctpValCookieLife OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds"
sctpValCookieLife对象类型语法无符号32单位“毫秒”
MAX-ACCESS read-only STATUS current DESCRIPTION "Valid cookie life in the 4-way start-up handshake procedure." REFERENCE "Section 5.1.3 in RFC2960 explains the cookie generation process. Recommended value is per section 14 in RFC2960." DEFVAL {60000} -- milliseconds
MAX-ACCESS只读状态当前描述“4路启动握手过程中的有效cookie寿命”。RFC2960中的“参考”第5.1.3节解释了cookie生成过程。建议的值为RFC2960中的第14节。“DEFVAL{60000}--毫秒
::= { sctpParams 6 }
::= { sctpParams 6 }
sctpMaxInitRetr OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of retransmissions at the start-up phase (INIT and COOKIE ECHO chunks). " REFERENCE "Section 5.1.4, 5.1.6 in RFC2960 refers to Max.Init.Retransmit parameter. Recommended value is per section 14 in RFC2960." DEFVAL {8} -- number of attempts
sctpMaxInitRetr对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“启动阶段（初始化和COOKIE回显块）的最大重新传输次数”。“参考”RFC2960中的第5.1.4节、第5.1.6节指的是MAX.INIT.Retransmit参数。建议的值根据RFC2960中的第14节。“定义{8}”--尝试次数
::= { sctpParams 7 }
::= { sctpParams 7 }
-- TABLES
-- ******
-- TABLES
-- ******
-- the SCTP Association TABLE
--SCTP关联表
-- The SCTP association table contains information about each
-- association in which the local endpoint is involved.
-- The SCTP association table contains information about each
-- association in which the local endpoint is involved.
sctpAssocTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpAssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SCTP association-specific information."
SCTPASSONCENTRY MAX-ACCESS的sctpAssocTable对象类型语法序列不可访问状态当前描述“包含SCTP关联特定信息的表”
::= { sctpObjects 3 }
::= { sctpObjects 3 }
sctpAssocEntry OBJECT-TYPE SYNTAX SctpAssocEntry MAX-ACCESS not-accessible
SCTPASSONTERY对象类型语法SCTPASSONTERY MAX-ACCESS不可访问
STATUS current DESCRIPTION "General common variables and statistics for the whole association." INDEX { sctpAssocId }
状态当前描述“整个关联的通用变量和统计数据”。索引{sctpAssocId}
::= { sctpAssocTable 1 }
::= { sctpAssocTable 1 }
SctpAssocEntry ::= SEQUENCE {
sctpAssocId Unsigned32,
sctpAssocRemHostName OCTET STRING,
sctpAssocLocalPort InetPortNumber,
sctpAssocRemPort InetPortNumber,
sctpAssocRemPrimAddrType InetAddressType,
sctpAssocRemPrimAddr InetAddress,
sctpAssocHeartBeatInterval Unsigned32,
sctpAssocState INTEGER,
sctpAssocInStreams Unsigned32,
sctpAssocOutStreams Unsigned32,
sctpAssocMaxRetr Unsigned32,
sctpAssocPrimProcess Unsigned32,
sctpAssocT1expireds Counter32, -- Statistic
sctpAssocT2expireds Counter32, -- Statistic
sctpAssocRtxChunks Counter32, -- Statistic
sctpAssocStartTime TimeStamp,
sctpAssocDiscontinuityTime TimeStamp
}
SctpAssocEntry ::= SEQUENCE {
sctpAssocId Unsigned32,
sctpAssocRemHostName OCTET STRING,
sctpAssocLocalPort InetPortNumber,
sctpAssocRemPort InetPortNumber,
sctpAssocRemPrimAddrType InetAddressType,
sctpAssocRemPrimAddr InetAddress,
sctpAssocHeartBeatInterval Unsigned32,
sctpAssocState INTEGER,
sctpAssocInStreams Unsigned32,
sctpAssocOutStreams Unsigned32,
sctpAssocMaxRetr Unsigned32,
sctpAssocPrimProcess Unsigned32,
sctpAssocT1expireds Counter32, -- Statistic
sctpAssocT2expireds Counter32, -- Statistic
sctpAssocRtxChunks Counter32, -- Statistic
sctpAssocStartTime TimeStamp,
sctpAssocDiscontinuityTime TimeStamp
}
sctpAssocId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Association Identification. Value identifying the association. "
sctpAssocId对象类型语法Unsigned32（1..4294967295）MAX-ACCESS不可访问状态当前描述“关联标识。标识关联的值。”
::= { sctpAssocEntry 1 }
::= { sctpAssocEntry 1 }
sctpAssocRemHostName OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "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.
sctpAssocRemHostName对象类型语法八位字符串（大小（0..255））最大访问只读状态当前说明“对等方的DNS名称。此对象需要与DNS协议中的编码具有相同的格式。这意味着域名最多可以有255个八位字节，每个八位字节的值为0<=x<=255，US-ASCII A-Z具有不区分大小写的匹配。
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."
如果在初始化时（嵌入在init或init-ACK块中）没有从对等方接收到DNS域名，则此对象没有意义。在这种情况下，对象必须包含长度为零的字符串值。否则，它将包含在初始化时收到的远程主机名。“
::= { sctpAssocEntry 2 }
::= { sctpAssocEntry 2 }
sctpAssocLocalPort OBJECT-TYPE SYNTAX InetPortNumber (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The local SCTP port number used for this association."
sctpAssocLocalPort对象类型语法InetPortNumber（1..65535）MAX-ACCESS只读状态当前描述“用于此关联的本地SCTP端口号。”
::= { sctpAssocEntry 3 }
::= { sctpAssocEntry 3 }
sctpAssocRemPort OBJECT-TYPE SYNTAX InetPortNumber (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The remote SCTP port number used for this association."
sctpAssocRemPort对象类型语法InetPortNumber（1..65535）MAX-ACCESS只读状态当前描述“用于此关联的远程SCTP端口号。”
::= { sctpAssocEntry 4 }
::= { sctpAssocEntry 4 }
sctpAssocRemPrimAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The internet type of primary remote IP address. "
sctpAssocRemPrimAddrType对象类型语法InetAddressType MAX-ACCESS只读状态当前描述“主远程IP地址的internet类型”
::= { sctpAssocEntry 5 }
::= { sctpAssocEntry 5 }
sctpAssocRemPrimAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The primary remote IP address. The type of this address is determined by the value of sctpAssocRemPrimAddrType.
sctpAssocRemPrimAddr对象类型语法InetAddress MAX-ACCESS只读状态当前描述“主远程IP地址。此地址的类型由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."
客户端在接收到INIT_ACK消息后会知道这个值，服务器端在发送INIT_ACK消息时会知道这个值。但是，值将在已建立（4）状态下填写。”
::= { sctpAssocEntry 6 }
::= { sctpAssocEntry 6 }
sctpAssocHeartBeatInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The current heartbeat interval..
SCTPASSOCHEARTBEATTERVAL对象类型语法Unsigned32单位“毫秒”最大访问只读状态当前描述“当前心跳间隔..”。。
Zero value means no HeartBeat, even when the concerned sctpAssocRemAddrHBFlag object is true." DEFVAL {30000} -- milliseconds
零值表示没有心跳，即使相关的sctpAssocRemAddrHBFlag对象为true。“deffal{30000}--毫秒
::= { sctpAssocEntry 7 }
::= { sctpAssocEntry 7 }
sctpAssocState OBJECT-TYPE
SYNTAX INTEGER {
closed(1),
cookieWait(2),
cookieEchoed(3),
established(4),
shutdownPending(5),
shutdownSent(6),
shutdownReceived(7),
shutdownAckSent(8),
deleteTCB(9)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of this SCTP association.
sctpAssocState OBJECT-TYPE
SYNTAX INTEGER {
closed(1),
cookieWait(2),
cookieEchoed(3),
established(4),
shutdownPending(5),
shutdownSent(6),
shutdownReceived(7),
shutdownAckSent(8),
deleteTCB(9)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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.
与TCP中一样，deleteTCB（9）是管理站可以设置的唯一值。如果收到任何其他值，则代理必须返回错误值错误。
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.
如果管理站将此对象设置为值deleteTCB（9），则这将导致删除受管节点上相应关联的TCB（如SCTP中定义的），从而立即终止关联。
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."
作为特定于实现的选项，由于设置了deleteTCB（9）值，可以将中止块从受管节点发送到另一个SCTP端点。中止区块意味着不正常的关联关闭。“
REFERENCE
参考
"Section 4 in RFC2960 covers the SCTP Association state diagram."
“RFC2960中的第4节介绍了SCTP关联状态图。”
::= { sctpAssocEntry 8 }
::= { sctpAssocEntry 8 }
sctpAssocInStreams OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Inbound Streams according to the negotiation at association start up." REFERENCE "Section 1.3 in RFC2960 includes a definition of stream. Section 5.1.1 in RFC2960 covers the streams negotiation process."
sctpAssocInStreams对象类型语法Unsigned32（1..65535）MAX-ACCESS只读状态当前描述“根据关联启动时的协商的入站流”。参考“RFC2960中的第1.3节包括流的定义。RFC2960中的第5.1.1节介绍了流协商过程。”
::= { sctpAssocEntry 9 }
::= { sctpAssocEntry 9 }
sctpAssocOutStreams OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Outbound Streams according to the negotiation at association start up. " REFERENCE "Section 1.3 in RFC2960 includes a definition of stream. Section 5.1.1 in RFC2960 covers the streams negotiation process."
sctpAssocOutStreams对象类型语法Unsigned32（1..65535）MAX-ACCESS只读状态当前描述“根据关联启动时的协商出站流”。参考“RFC2960中的第1.3节包括流的定义。RFC2960中的第5.1.1节介绍了流协商过程。”
::= { sctpAssocEntry 10 }
::= { sctpAssocEntry 10 }
sctpAssocMaxRetr OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "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).
sctpAssocMaxRetr对象类型语法Unsigned32 MAX-ACCESS只读状态当前说明“关联上下文中的最大数据重传次数。该值对于每个关联都是特定的，上层可以通过调用适当的原语来更改它。此值必须小于所有路径（sctpAssocRemAddrMaxPathRtx）的所有最大数之和。
A value of zero value means no retransmissions." DEFVAL {10} -- number of attempts
零值表示没有重新传输。“deffal{10}——尝试次数
::= { sctpAssocEntry 11 }
::= { sctpAssocEntry 11 }
sctpAssocPrimProcess OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
sctpAssocPrimProcess对象类型语法未签名32 MAX-ACCESS只读状态当前说明“此对象标识对SCTP关联负有主要责任的系统级进程。在可能的情况下，这应该是系统的本机唯一标识号。特殊值0可用于指示主进程未知。
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."
请注意，此对象的值可以用作指向HOST-RESOURCES-MIB的swRunTable（如果该值小于2147483647）或sysappll-MIB的sysApplElmtRunTable的指针。”
::= { sctpAssocEntry 12 }
::= { sctpAssocEntry 12 }
-- Association Statistics
--关联统计
sctpAssocT1expireds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
SCTPASSOCT1EEXPIREDS对象类型语法计数器32 MAX-ACCESS只读状态当前描述“T1计时器确定发送初始化或COOKIE-ECHO块后等待确认的时间。此对象反映T1计时器在未收到确认的情况下过期的次数。
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." REFERENCE "Section 5 in RFC2960."
管理系统重新初始化时，以及sctpAssocDiscontinuityTime值指示的其他时间，该计数器的值可能出现不连续。“参考”RFC2960中的第5节
::= { sctpAssocEntry 13 }
::= { sctpAssocEntry 13 }
sctpAssocT2expireds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only
sctpAssocT2expireds对象类型语法计数器32 MAX-ACCESS只读
STATUS current DESCRIPTION "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.
STATUS current DESCRIPTION“T2计时器确定发送关机或关机确认区块后等待确认的时间。此对象反映T2计时器过期的次数。
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."
REFERENCE
"Section 9.2 in RFC2960."
::= { sctpAssocEntry 14 }
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."
REFERENCE
"Section 9.2 in RFC2960."
::= { sctpAssocEntry 14 }
sctpAssocRtxChunks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
sctpAssocRtxChunks对象类型语法计数器32 MAX-ACCESS只读状态当前描述“当T3 rtx过期时，触发T3计时器的数据块将根据重传规则重新发送。触发T3 rtx计时器的SCTP数据包中包含的每个数据块必须添加到此计数器的值。
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." REFERENCE "Section 6 in RFC2960 covers the retransmission process and rules."
管理系统重新初始化时，以及SCTPASSOCDDISCONTINUITYTIME值指示的其他时间，可能会出现此计数器值的不连续性。RFC2960中的“参考”第6节介绍了重传过程和规则
::= { sctpAssocEntry 15 }
::= { sctpAssocEntry 15 }
sctpAssocStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "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
sctpAssocStartTime对象类型语法TimeStamp MAX-ACCESS只读状态当前描述“此行表示的关联进入已建立状态时的sysUpTime值，即sctpAssocState对象设置为已建立（4）。此对象的值将为零：-在关联进入已建立（4）状态之前，或
- if the established(4) state was entered prior to the last re-initialization of the local network management subsystem."
- 如果在本地网络管理子系统最后一次重新初始化之前进入已建立（4）状态。”
::= { sctpAssocEntry 16 }
::= { sctpAssocEntry 16 }
sctpAssocDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "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. " REFERENCE "The inclusion of this object is recommended by RFC2578."
sctpAssocDiscontinuityTime对象类型语法时间戳MAX-ACCESS只读状态当前说明“最近一次任何一个或多个SCTP关联计数器出现中断时的sysUpTime值。相关计数器是与sctpAssocTable或sctpLocalAddrTable或SCTPremAddressTable中包含的任何Counter32或Counter64对象的此接口相关联的特定实例。如果自上次重新初始化本地管理子系统以来未发生此类中断，则此对象包含零值。“参考”RFC2578建议包含此对象
::= { sctpAssocEntry 17 }
::= { sctpAssocEntry 17 }
-- Expanded tables: Including Multi-home feature
--扩展表：包括多主功能
-- Local Address TABLE
-- *******************
-- Local Address TABLE
-- *******************
sctpAssocLocalAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpAssocLocalAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
SCTPASSOCLOCALADDRABLE对象类型SCTPASSOCLOCALADDRABLE的语法序列MAX-ACCESS不可访问状态当前描述“基于AssocId索引的sctpAssocTable扩展表。此表显示与此关联使用的每个本地IP地址相关的数据。”
::= { sctpObjects 4 }
::= { sctpObjects 4 }
sctpAssocLocalAddrEntry OBJECT-TYPE SYNTAX SctpAssocLocalAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Local information about the available addresses. There will be an entry for every local IP address defined for this
sctpAssocLocalAddrEntry对象类型语法sctpAssocLocalAddrEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“有关可用地址的本地信息。为此定义的每个本地IP地址都有一个条目
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." INDEX { sctpAssocId, -- shared index sctpAssocLocalAddrType, sctpAssocLocalAddr }
协会实施者需要知道，如果sctpAssocLocalAddr的大小超过114个八位字节，那么此表中列实例的OID将具有128个以上的子标识符，并且不能使用SNMPv1、SNMPv2c或SNMPv3进行访问。“索引{SCTPASSOID，--共享索引SCTPASSOCLOCALADDRYPE、sctpAssocLocalAddr}”
::= { sctpAssocLocalAddrTable 1 }
::= { sctpAssocLocalAddrTable 1 }
SctpAssocLocalAddrEntry ::= SEQUENCE {
sctpAssocLocalAddrType InetAddressType,
sctpAssocLocalAddr InetAddress,
sctpAssocLocalAddrStartTime TimeStamp
}
SctpAssocLocalAddrEntry ::= SEQUENCE {
sctpAssocLocalAddrType InetAddressType,
sctpAssocLocalAddr InetAddress,
sctpAssocLocalAddrStartTime TimeStamp
}
sctpAssocLocalAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "Internet type of local IP address used for this association."
SCTPASSOCLOCALADDRYPE对象类型语法InetAddressType MAX-ACCESS不可访问状态当前描述“用于此关联的本地IP地址的Internet类型。”
::= { sctpAssocLocalAddrEntry 1 }
::= { sctpAssocLocalAddrEntry 1 }
sctpAssocLocalAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of a local IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType."
sctpAssocLocalAddr对象类型语法InetAddress MAX-ACCESS不可访问状态当前描述“可用于此关联的本地IP地址的值。此地址的类型由sctpAssocLocalAddrType的值确定。”
::= { sctpAssocLocalAddrEntry 2 }
::= { sctpAssocLocalAddrEntry 2 }
sctpAssocLocalAddrStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time that this row was created."
sctpAssocLocalAddrStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时sysUpTime的值。”
::= { sctpAssocLocalAddrEntry 3 }
::= { sctpAssocLocalAddrEntry 3 }
-- Remote Addresses TABLE
-- **********************
-- Remote Addresses TABLE
-- **********************
sctpAssocRemAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpAssocRemAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
sctpAssocRemAddrTable SCTPASSOCREMADRENTRY MAX-ACCESS的对象类型语法序列不可访问状态当前描述“基于AssocId索引的sctpAssocTable扩展表。此表显示与此关联使用的每个远程对等IP地址相关的数据。”
::= { sctpObjects 5 }
::= { sctpObjects 5 }
sctpAssocRemAddrEntry OBJECT-TYPE SYNTAX SctpAssocRemAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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.
SCTPASSOCREMADRENTRY对象类型语法SCTPASSOCREMADRENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“有关每个远程IP地址的最重要变量的信息。为此关联定义的每个远程IP地址都有一个条目。
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." INDEX { sctpAssocId, -- shared index sctpAssocRemAddrType, sctpAssocRemAddr }
实施者需要注意，如果SCTPASSOCREMADR的大小超过114个八位字节，则此表中列实例的OID将具有128个以上的子标识符，并且无法使用SNMPv1、SNMPv2c或SNMPv3进行访问。“索引{SCTPASSOID，--共享索引sctpAssocRemAddrType，SCTPASSOCREMADR}”
::= { sctpAssocRemAddrTable 1 }
::= { sctpAssocRemAddrTable 1 }
SctpAssocRemAddrEntry ::= SEQUENCE {
sctpAssocRemAddrType InetAddressType,
sctpAssocRemAddr InetAddress,
sctpAssocRemAddrActive TruthValue,
sctpAssocRemAddrHBActive TruthValue,
sctpAssocRemAddrRTO Unsigned32,
sctpAssocRemAddrMaxPathRtx Unsigned32,
sctpAssocRemAddrRtx Counter32, -- Statistic
sctpAssocRemAddrStartTime TimeStamp
}
SctpAssocRemAddrEntry ::= SEQUENCE {
sctpAssocRemAddrType InetAddressType,
sctpAssocRemAddr InetAddress,
sctpAssocRemAddrActive TruthValue,
sctpAssocRemAddrHBActive TruthValue,
sctpAssocRemAddrRTO Unsigned32,
sctpAssocRemAddrMaxPathRtx Unsigned32,
sctpAssocRemAddrRtx Counter32, -- Statistic
sctpAssocRemAddrStartTime TimeStamp
}
sctpAssocRemAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Internet type of a remote IP address available for this
association."
::= { sctpAssocRemAddrEntry 1 }
sctpAssocRemAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Internet type of a remote IP address available for this
association."
::= { sctpAssocRemAddrEntry 1 }
sctpAssocRemAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of a remote IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType."
SCTPASSOCREMADR对象类型语法InetAddress MAX-ACCESS不可访问状态当前描述“可用于此关联的远程IP地址的值。此地址的类型由sctpAssocLocalAddrType的值确定。”
::= { sctpAssocRemAddrEntry 2 }
::= { sctpAssocRemAddrEntry 2 }
sctpAssocRemAddrActive OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object gives information about the reachability of this specific remote IP address.
sctpAssocRemAddrActive对象类型语法TruthValue MAX-ACCESS只读状态当前描述“此对象提供有关此特定远程IP地址可访问性的信息。
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.
当对象设置为“true”（1）时，远程IP地址被理解为活动的。Active表示未达到从该IP地址接收到的无应答阈值。
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."
当对象设置为“false”（2）时，远程IP地址被理解为非活动。Inactive表示没有从该地址接收到心跳信号或任何其他消息，达到协议定义的阈值。”
REFERENCE "The remote transport states are defined as Active and Inactive in the SCTP, RFC2960."
参考“远程传输状态在SCTP RFC2960中定义为活动和非活动。”
::= { sctpAssocRemAddrEntry 3 }
::= { sctpAssocRemAddrEntry 3 }
sctpAssocRemAddrHBActive OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "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). "
SCTPASSOCREMADRDHBACTIVE对象类型语法TruthValue MAX-ACCESS只读状态当前描述“此对象指示是否激活与一个目标传输地址关联的可选心跳检查（值分别等于true或false）。”
::= { sctpAssocRemAddrEntry 4 }
::= { sctpAssocRemAddrEntry 4 }
sctpAssocRemAddrRTO OBJECT-TYPE -- T3-rtx- Timer SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The current Retransmission Timeout. T3-rtx timer as defined in the protocol SCTP." REFERENCE "Section 6.3 in RFC2960 deals with the Retransmission Timer Management."
sctpAssocRemAddrRTO对象类型--T3 rtx-计时器语法无符号32单位“毫秒”最大访问只读状态当前描述“当前重传超时。协议SCTP中定义的T3 rtx计时器。RFC2960中的“参考”第6.3节处理重传计时器管理。”
::= { sctpAssocRemAddrEntry 5 }
::= { sctpAssocRemAddrEntry 5 }
sctpAssocRemAddrMaxPathRtx OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum number of DATA chunks retransmissions allowed to a remote IP address before it is considered inactive, as defined in RFC2960."
SCTPASSOCREMADRDRMAXPATHRTX对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“在远程IP地址被视为非活动之前，允许向其重新传输的最大数据块数，如RFC2960中定义的。”
REFERENCE "Section 8.2, 8.3 and 14 in RFC2960." DEFVAL {5} -- number of attempts
参考“RFC2960中的第8.2、8.3和14节。”定义{5}——尝试次数
::= { sctpAssocRemAddrEntry 6 }
::= { sctpAssocRemAddrEntry 6 }
-- Remote Address Statistic
--远程地址统计
sctpAssocRemAddrRtx OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
sctpAssocRemAddrRtx对象类型语法计数器32 MAX-ACCESS只读状态当前说明“重新传输到此特定IP地址的数据块数。当T3 rtx过期时，触发T3计时器的数据块将根据重传规则重新发送。SCTP数据包中包含的每个数据块，以及之前传输到此特定IP地址的数据块，都将包含在此计数器中。
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."
管理系统重新初始化时，以及sctpAssocDiscontinuityTime值指示的其他时间，可能会出现此计数器值的不连续性。”
::= { sctpAssocRemAddrEntry 7 }
::= { sctpAssocRemAddrEntry 7 }
sctpAssocRemAddrStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time that this row was created."
sctpAssocRemAddrStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时sysUpTime的值。”
::= { sctpAssocRemAddrEntry 8 }
::= { sctpAssocRemAddrEntry 8 }
-- ASSOCIATION INVERSE TABLE
-- *************************
-- ASSOCIATION INVERSE TABLE
-- *************************
-- BY LOCAL PORT
--按本地港口
sctpLookupLocalPortTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpLookupLocalPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "With the use of this table, a list of associations which are
sctpLookupLocalPortTable对象类型语法SctpLookupLocalPortEntry MAX-ACCESS的序列不可访问状态当前描述“使用此表时，关联列表如下所示：
using the specified local port can be retrieved."
可以检索使用指定的本地端口。“
::= { sctpObjects 6 }
::= { sctpObjects 6 }
sctpLookupLocalPortEntry OBJECT-TYPE SYNTAX SctpLookupLocalPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
sctpLookupLocalPortEntry对象类型语法sctpLookupLocalPortEntry MAX-ACCESS不可访问状态当前描述“此表由本地端口和关联ID索引。指定本地端口，我们将获得其本地端口为指定端口的关联列表。”
INDEX { sctpAssocLocalPort, sctpAssocId }
索引{sctpAssocLocalPort，sctpAssocId}
::= { sctpLookupLocalPortTable 1 }
::= { sctpLookupLocalPortTable 1 }
SctpLookupLocalPortEntry::= SEQUENCE {
sctpLookupLocalPortStartTime TimeStamp
}
SctpLookupLocalPortEntry::= SEQUENCE {
sctpLookupLocalPortStartTime TimeStamp
}
sctpLookupLocalPortStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time that this row was created.
sctpLookupLocalPortStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时的sysUpTime值。
As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table."
由于该表将在sctpAssocTable创建之后创建，因此该值可能等于主表中的sctpAssocStartTime对象。”
::= { sctpLookupLocalPortEntry 1 }
::= { sctpLookupLocalPortEntry 1 }
-- BY REMOTE PORT
--通过远程端口
sctpLookupRemPortTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpLookupRemPortEntry MAX-ACCESS not-accessible STATUS current
SCTPLookupTemportTable对象类型语法序列SCTPLookupTemportEntry MAX-ACCESS不可访问状态当前
DESCRIPTION "With the use of this table, a list of associations which are using the specified remote port can be got"
DESCRIPTION“使用此表，可以获得使用指定远程端口的关联列表”
::= { sctpObjects 7 }
::= { sctpObjects 7 }
sctpLookupRemPortEntry OBJECT-TYPE SYNTAX SctpLookupRemPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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 "
SCTPLookupTemportEntry对象类型语法SCTPLookupTemportEntry MAX-ACCESS不可访问状态当前描述“此表由远程端口和关联ID索引。指定远程端口，我们将获得其本地端口为指定端口的关联列表”
INDEX { sctpAssocRemPort, sctpAssocId }
索引{sctpAssocRemPort，sctpAssocId}
::= { sctpLookupRemPortTable 1 }
::= { sctpLookupRemPortTable 1 }
SctpLookupRemPortEntry::= SEQUENCE {
sctpLookupRemPortStartTime TimeStamp
}
SctpLookupRemPortEntry::= SEQUENCE {
sctpLookupRemPortStartTime TimeStamp
}
sctpLookupRemPortStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time that this row was created.
SCTPLookupReportStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时sysUpTime的值。
As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table."
由于该表将在sctpAssocTable创建之后创建，因此该值可能等于主表中的sctpAssocStartTime对象。”
::= { sctpLookupRemPortEntry 1 }
::= { sctpLookupRemPortEntry 1 }
-- BY REMOTE HOST NAME
--按远程主机名
sctpLookupRemHostNameTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "With the use of this table, a list of associations with that particular host can be retrieved."
sctpLookupRemHostNameTable SctpLookupRemHostNameEntry的对象类型语法序列MAX-ACCESS不可访问状态当前描述“使用此表，可以检索与该特定主机的关联列表。”
::= { sctpObjects 8 }
::= { sctpObjects 8 }
sctpLookupRemHostNameEntry OBJECT-TYPE SYNTAX SctpLookupRemHostNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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.
sctpLookupRemHostNameEntry对象类型语法sctpLookupRemHostNameEntry MAX-ACCESS不可访问状态当前描述“此表由远程主机名和关联ID索引。指定主机名我们将获得一个关联列表，指定该主机名为远程主机名。
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."
实施者需要注意，如果sctpAssocRemHostName的大小超过115个八位字节，则此表中列实例的OID将具有128个以上的子标识符，并且无法使用SNMPv1、SNMPv2c或SNMPv3进行访问。”
INDEX { sctpAssocRemHostName, sctpAssocId }
索引{sctpAssocRemHostName，sctpAssocId}
::= { sctpLookupRemHostNameTable 1 }
::= { sctpLookupRemHostNameTable 1 }
SctpLookupRemHostNameEntry::= SEQUENCE {
sctpLookupRemHostNameStartTime TimeStamp
}
SctpLookupRemHostNameEntry::= SEQUENCE {
sctpLookupRemHostNameStartTime TimeStamp
}
sctpLookupRemHostNameStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time that this row was created.
sctpLookupRemHostNameStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时sysUpTime的值。
As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table."
由于该表将在sctpAssocTable创建之后创建，因此该值可能等于主表中的sctpAssocStartTime对象。”
::= { sctpLookupRemHostNameEntry 1 }
::= { sctpLookupRemHostNameEntry 1 }
-- BY REMOTE PRIMARY IP ADDRESS
--按远程主IP地址
sctpLookupRemPrimIPAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
SCTPLookupEmprimiPaddrTable对象类型语法SCTPLookupEmprimiPaddrEntry MAX-ACCESS不可访问状态当前描述“使用此表，可以检索远程活动地址集中指定IP地址为主的关联列表。”
::= { sctpObjects 9 }
::= { sctpObjects 9 }
sctpLookupRemPrimIPAddrEntry OBJECT-TYPE SYNTAX SctpLookupRemPrimIPAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
SCTPLookupEmprimipAddressEntry对象类型语法SCTPLookupEmprimipAddressEntry MAX-ACCESS不可访问状态当前说明“此表按主地址和关联ID编制索引。指定主地址，我们将获得指定远程IP地址标记为主的关联列表。实施者需要注意，如果sctpAssocRemPrimAddr的大小超过114个八位字节，则此表中列实例的OID将具有128个以上的子标识符，并且无法使用SNMPv1、SNMPv2c或SNMPv3进行访问。”
INDEX { sctpAssocRemPrimAddrType, sctpAssocRemPrimAddr, sctpAssocId }
索引{sctpAssocRemPrimAddrType，sctpAssocRemPrimAddr，SCTPASSOID}
::= { sctpLookupRemPrimIPAddrTable 1 }
::= { sctpLookupRemPrimIPAddrTable 1 }
SctpLookupRemPrimIPAddrEntry::= SEQUENCE {
sctpLookupRemPrimIPAddrStartTime TimeStamp
}
SctpLookupRemPrimIPAddrEntry::= SEQUENCE {
sctpLookupRemPrimIPAddrStartTime TimeStamp
}
sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current
SCTPlookupEmprimiPaddrStartTime对象类型语法时间戳MAX-ACCESS只读状态当前
DESCRIPTION "The value of SysUpTime at the time that this row was created.
DESCRIPTION“创建此行时的SysUpTime值。
As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table."
由于该表将在sctpAssocTable创建之后创建，因此该值可能等于主表中的sctpAssocStartTime对象。”
::= { sctpLookupRemPrimIPAddrEntry 1 }
::= { sctpLookupRemPrimIPAddrEntry 1 }
-- BY REMOTE IP ADDRESS
--按远程IP地址
sctpLookupRemIPAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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. "
SCTPLookupRemipaddertable对象类型语法SctpLookupRemIPAddrEntry MAX-ACCESS不可访问状态当前描述“使用此表，可以检索具有指定IP地址作为远程地址之一的关联列表。”
::= { sctpObjects 10 }
::= { sctpObjects 10 }
sctpLookupRemIPAddrEntry OBJECT-TYPE SYNTAX SctpLookupRemIPAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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."
SCTPLookupRemiPadRentry对象类型语法SCTPLookupRemiPadRentry MAX-ACCESS不可访问状态当前描述“此表由远程IP地址和关联ID索引。指定IP地址，我们将获得包含在远程IP地址集中的指定IP地址的关联列表。”
INDEX { sctpAssocRemAddrType, sctpAssocRemAddr, sctpAssocId }
索引{sctpAssocRemAddrType，sctpAssocRemAddr，sctpAssocId}
::= { sctpLookupRemIPAddrTable 1 }
::= { sctpLookupRemIPAddrTable 1 }
SctpLookupRemIPAddrEntry::= SEQUENCE {
SctpLookupRemIPAddrEntry::= SEQUENCE {
sctpLookupRemIPAddrStartTime TimeStamp }
SCTPLookupEmipardsStartTime时间戳}
sctpLookupRemIPAddrStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of SysUpTime at the time that this row was created.
sctpLookupRemIPAddrStartTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“创建此行时SysUpTime的值。
As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table."
由于该表将在sctpAssocTable创建之后创建，因此该值可能等于主表中的sctpAssocStartTime对象。”
::= { sctpLookupRemIPAddrEntry 1 }
::= { sctpLookupRemIPAddrEntry 1 }
-- 4.1 Conformance Information
--4.1一致性信息
sctpMibConformance OBJECT IDENTIFIER ::= { sctpMIB 2 }
sctpMibCompliances OBJECT IDENTIFIER ::= { sctpMibConformance 1 }
sctpMibGroups OBJECT IDENTIFIER ::= { sctpMibConformance 2 }
sctpMibConformance OBJECT IDENTIFIER ::= { sctpMIB 2 }
sctpMibCompliances OBJECT IDENTIFIER ::= { sctpMibConformance 1 }
sctpMibGroups OBJECT IDENTIFIER ::= { sctpMibConformance 2 }
-- 4.1.1 Units of conformance
--4.1.1一致性单位
-- -- MODULE GROUPS --
----模块组--
sctpLayerParamsGroup OBJECT-GROUP OBJECTS { sctpRtoAlgorithm, sctpRtoMin, sctpRtoMax, sctpRtoInitial, sctpMaxAssocs, sctpValCookieLife, sctpMaxInitRetr }
sctpLayerParamsGroup对象组对象{SCTPToAlgorithm、SCTPToMin、SCTPToMax、SCTPToInitial、sctpMaxAssocs、sctpValCookieLife、SCTPMaxiMonitor}
STATUS current DESCRIPTION "Common parameters for the SCTP layer, i.e., for all the associations. They can usually be referred to as configuration parameters."
STATUS current DESCRIPTION“SCTP层的通用参数，即所有关联。它们通常可以称为配置参数。”
::= { sctpMibGroups 1 }
::= { sctpMibGroups 1 }
sctpStatsGroup OBJECT-GROUP OBJECTS { sctpCurrEstab, sctpActiveEstabs, sctpPassiveEstabs, sctpAborteds, sctpShutdowns, sctpOutOfBlues, sctpChecksumErrors, sctpOutCtrlChunks, sctpOutOrderChunks, sctpOutUnorderChunks, sctpInCtrlChunks, sctpInOrderChunks, sctpInUnorderChunks, sctpFragUsrMsgs, sctpReasmUsrMsgs, sctpOutSCTPPacks, sctpInSCTPPacks, sctpDiscontinuityTime, sctpAssocT1expireds, sctpAssocT2expireds, sctpAssocRtxChunks, sctpAssocRemAddrRtx }
sctpStatsGroup对象组对象{sctpCurrEstab、sctpActiveEstabs、sctpPassiveEstabs、SCTPborteds、sctpShutdowns、sctpOutOfBlues、sctpChecksumErrors、SCTPoutCtrChunks、sctpOutOrderChunks、sctpOutUnorderChunks、sctpInCtrlChunks、sctpInOrderChunks、SCTPFragusrMsg、SCTPoutCtPpPacks、SCTPInsCtPpPacks、SCTPInsctTime、SCTPAscoct1Expireds、 SCTPASSOCT2expired、sctpAssocRtxChunks、sctpAssocRemAddrRtx}
STATUS current DESCRIPTION "Statistics group. It includes the objects to collect state changes in the SCTP protocol local layer and flow control statistics."
STATUS current DESCRIPTION“统计组。它包括用于收集SCTP协议本地层中状态更改和流控制统计信息的对象
::= { sctpMibGroups 2 }
::= { sctpMibGroups 2 }
sctpPerAssocParamsGroup OBJECT-GROUP OBJECTS { sctpAssocRemHostName, sctpAssocLocalPort, sctpAssocRemPort, sctpAssocRemPrimAddrType, sctpAssocRemPrimAddr, sctpAssocHeartBeatInterval, sctpAssocState, sctpAssocInStreams, sctpAssocOutStreams, sctpAssocMaxRetr, sctpAssocPrimProcess, sctpAssocStartTime, sctpAssocDiscontinuityTime,
SCTPassocParamsGroup对象组对象{SCTPassocCremHostName、sctpAssocLocalPort、SCTPassocCremprImport、SCTPassocCremprAddrType、SCTPassocCremprAddr、SCTPassocChartBeatInterval、sctpAssocState、SCTPassoconStreams、sctpAssocOutStreams、sctpAssocMaxRetr、SCTPassocPrimprProcess、sctpAssocStartTime、SCTPassocDiscontinuTime、，
sctpAssocLocalAddrStartTime, sctpAssocRemAddrActive, sctpAssocRemAddrHBActive, sctpAssocRemAddrRTO, sctpAssocRemAddrMaxPathRtx, sctpAssocRemAddrStartTime }
SCTPASSOCLOCALADDRSTARTIME，sctpAssocRemAddrHBActive，sctpAssocRemAddrRTO，SCTPASSOCREMADDRMAXPATHRX，SCTPASSOCREMADDRSTARTIME}
STATUS current DESCRIPTION "The SCTP group of objects to manage per-association parameters. These variables include all the SCTP basic features."
STATUS current DESCRIPTION“根据关联参数管理的SCTP对象组。这些变量包括所有SCTP基本功能。”
::= { sctpMibGroups 3 }
::= { sctpMibGroups 3 }
sctpPerAssocStatsGroup OBJECT-GROUP OBJECTS { sctpAssocT1expireds, sctpAssocT2expireds, sctpAssocRtxChunks, sctpAssocRemAddrRtx }
SCTPASSOCSTATSGROUP对象组对象{SCTPASSOCT1EEXPIREDS，sctpAssocT2expireds，sctpAssocRtxChunks，sctpAssocRemAddrRtx}
STATUS current DESCRIPTION "Per Association Statistics group. It includes the objects to collect flow control statistics per association."
每个关联统计信息组的“状态当前描述”。它包括每个关联收集流控制统计信息的对象
::= { sctpMibGroups 4 }
::= { sctpMibGroups 4 }
sctpInverseGroup OBJECT-GROUP OBJECTS { sctpLookupLocalPortStartTime, sctpLookupRemPortStartTime, sctpLookupRemHostNameStartTime, sctpLookupRemPrimIPAddrStartTime, sctpLookupRemIPAddrStartTime }
sctpInverseGroup对象组对象{sctpLookupLocalPortStartTime，SCTPlookupTemportStartTime，SCTPlookupEmHostNameStartTime，SCTPlookupEmprimipAddressStartTime，SCTPlookupEmipardStartTime}
STATUS current DESCRIPTION "Objects used in the inverse lookup tables."
状态当前描述“反向查找表中使用的对象”
::= { sctpMibGroups 5 }
::= { sctpMibGroups 5 }
-- 4.1.2 Compliance Statements
--4.1.2合规性声明
-- -- MODULE COMPLIANCES --
----模块符合性--
sctpMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which implement this SCTP MIB Module.
SCTPMIB COMPLIANCE MODULE-COMPLIANCE STATUS current DESCRIPTION“实现此SCTP MIB模块的SNMP实体的符合性声明。
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:
有许多索引对象无法在SMIv2中以对象条款的形式表示，但我们对其有以下符合性要求，在本说明条款中以对象条款的形式表示：
-- 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.
--
" -- closes DESCRIPTION clause of MODULE-COMPLIANCE
-- 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.
--
" -- closes DESCRIPTION clause of MODULE-COMPLIANCE
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS { sctpLayerParamsGroup, sctpPerAssocParamsGroup, sctpStatsGroup, sctpPerAssocStatsGroup }
必填组{sctpLayerParamsGroup，sctpPerAssocParamsGroup，sctpStatsGroup，SCTPperassoctatsGroup}
OBJECT sctpAssocRemPrimAddrType SYNTAX InetAddressType { ipv4(1), ipv6(2) } DESCRIPTION "It is only required to have IPv4 and IPv6 addresses without zone indices.
对象sctpAssocRemPrimAddrType语法InetAddressType{ipv4（1），ipv6（2）}说明“只需要具有不带区域索引的ipv4和ipv6地址。
The address with zone indices is required if an implementation can connect multiple zones."
如果实现可以连接多个区域，则需要具有区域索引的地址。”
OBJECT sctpAssocRemPrimAddr SYNTAX InetAddress (SIZE(4|16)) DESCRIPTION "An implementation is only required to support globally unique IPv4 and globally unique IPv6 addresses."
对象sctpAssocRemPrimAddr语法InetAddress（大小（4 | 16））说明“一个实现只需要支持全局唯一的IPv4和全局唯一的IPv6地址。”
OBJECT sctpAssocState WRITE-SYNTAX INTEGER { deleteTCB(9) } MIN-ACCESS read-only DESCRIPTION "Only the deleteTCB(9) value MAY be set by a management station at most. A read-only option is also considered to be compliant with this MIB module description."
对象sctpAssocState WRITE-SYNTAX INTEGER{deleteTCB（9）}MIN-ACCESS只读说明“管理站最多只能设置deleteTCB（9）值。只读选项也被认为符合此MIB模块说明。”
GROUP sctpInverseGroup DESCRIPTION "Objects used in inverse lookup tables. This should be implemented, at the discretion of the implementers, for easier lookups in the association tables"
GROUP sctpInverseGroup DESCRIPTION“反向查找表中使用的对象。这应由实现者自行决定实现，以便于在关联表中查找”
::= { sctpMibCompliances 1 }
::= { sctpMibCompliances 1 }
END
终止
When compiling the MIB module warnings similar to the following may occur:
编译MIB模块时，可能会出现与以下类似的警告：
- warning: index of row `sctpAssocLocalAddrEntry' can exceed OID size limit by 141 subidentifier(s) - warning: index of row `sctpAssocRemAddrEntry' can exceed OID size limit by 141 subidentifier(s) - warning: index of row `sctpLookupRemHostNameEntry' can exceed OID size limit by 140 subidentifier(s) - warning: index of row `sctpLookupRemPrimIPAddrEntry' can exceed OID size limit by 141 subidentifier(s) - warning: index of row `sctpLookupRemIPAddrEntry' can exceed OID size limit by 141 subidentifier(s)
- 警告：“sctpAssocLocalAddrEntry”行的索引可以超过OID大小限制141个子标识符-警告：“SCTPASSOCREDRENTRY”行的索引可以超过OID大小限制141个子标识符-警告：“sctpLookupRemHostNameEntry”行的索引可以超过OID大小限制140个子标识符-警告：“SCTPLookupEmprimiPaddrEntry”行的索引可以超过OID大小限制141个子标识符-警告：“SCTPLookupEmpiPaddrEntry”行的索引可以超过OID大小限制141个子标识符
These warnings are due to the fact that the row objects have index objects of type InetAddress or OCTET STRING whose size limit is 255 octets, and if that size limit were reached the names of column instances in those rows would exceed the 128 sub-identifier limit imposed by current versions of the SNMP. Actual limitations for the index object sizes are noted in the conceptual row DESCRIPTION clauses. For the InetAddress index objects these size limits will not be reached with any of the address types in current use.
这些警告是由于行对象具有InetAddress或八进制字符串类型的索引对象，其大小限制为255个八进制，如果达到该大小限制，则这些行中的列实例名称将超过当前版本的SNMP施加的128个子标识符限制。索引对象大小的实际限制在概念行描述子句中有所说明。对于InetAddress索引对象，当前使用的任何地址类型都不会达到这些大小限制。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson, "Stream Control Transmission Protocol", RFC 2960, October 2000.
[RFC2960]Stewart，R.，Xie，Q.，Morneault，K.，Sharp，C.，Schwarzbauer，H.，Taylor，T.，Rytina，I.，Kalla，M.，Zhang，L.，和V.Paxson，“流控制传输协议”，RFC 29602000年10月。
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 3291, May 2002.
[RFC3291]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 3291，2002年5月。
[RFC3309] Stone, J., Stewart, R., and D. Otis, "Stream Control Transmission Protocol (SCTP) Checksum Change", RFC 3309, September 2002.
[RFC3309]Stone，J.，Stewart，R.，和D.Otis，“流控制传输协议（SCTP）校验和更改”，RFC 33092002年9月。
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets:MIB-II", STD 17, RFC 1213, March 1991.
[RFC1213]McCloghrie，K.和M.Rose，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[RFC2012] McCloghrie, K., "SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2", RFC 2012, November 1996.
[RFC2012]McCloghrie，K.，“使用SMIv2的传输控制协议的SNMPv2管理信息库”，RFC 2012，1996年11月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[VANJ] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988, Stanford, California.
[VANJ]Jacobson，V.，“拥塞避免和控制”，SIGCOMM 1988，加利福尼亚州斯坦福。
[IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, A., and B. Zill, "IPv6 Scoped Address Architecture", Work in Progress, December 2002.
[IPv6ARCH]Deering，S.，Haberman，B.，Jinmei，T.，Nordmark，E.，Onoe，A.，和B.Zill，“IPv6作用域地址体系结构”，正在进行的工作，2002年12月。
[sctpImplem] Stewart, R., Ong, L., Arias-Rodriguez, I., Caro, A., and M. Tuexen, "Stream Control Transmission Protocol (SCTP) Implementers Guide", Work in Progress, January 2002.
[sctpImplem]Stewart，R.，Ong，L.，Arias Rodriguez，I.，Caro，A.，和M.Tuexen，“流控制传输协议（SCTP）实施者指南”，正在进行的工作，2002年1月。
[TCPMIB] Fenner, B., McCloghrie, K., Raghunarayan, R., and J. Schoenwalder, "Management Information Base for the Transmission Control Protocol (TCP)", Work in Progress, November 2002.
[TCPMIB]Fenner，B.，McCloghrie，K.，Raghunarayan，R.，和J.Schoenwalder，“传输控制协议（TCP）的管理信息库”，正在进行的工作，2002年11月。
[UDPMIB] Fenner, B., "Management Information Base for User Datagram Protocol (UDP)", Work in Progress, June 2002.
[UDPMIB]Fenner，B.，“用户数据报协议（UDP）的管理信息库”，正在进行的工作，2002年6月。
[MIBGUIDE] Heard, C.M., "Guidelines for MIB Authors and Reviewers", Work in Progress, February 2003.
[MIBGUIDE]Heard，C.M.，“MIB作者和评审员指南”，正在进行的工作，2003年2月。
There are management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
此MIB中定义的管理对象具有读写和/或读创建的MAX-ACCESS子句。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o The sctpAssocState object has a MAX-ACCESS clause of read-write, which allows termination of an arbitrary connection. Unauthorized access could cause a denial of service.
o sctpAssocState对象有一个读写MAX-ACCESS子句，它允许终止任意连接。未经授权的访问可能导致拒绝服务。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. Thus, it is important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点很重要。以下是表和对象及其敏感度/漏洞：
o The sctpAssocTable, sctpAssocLocalAddressTable, sctpAssocRemAddressTable and the lookup tables contain objects providing information on the active associations on the device, local and peer's IP addresses, the status of these associations and the associated processes. This information may be used by an attacker to launch attacks against known/unknown weakness in certain protocols/applications.
o sctpAssocTable、SCTPASSOCLOCALADDRESTABLE、SCTPASSOCREMADESTABLE和查找表包含提供有关设备上活动关联、本地和对等IP地址、这些关联的状态和关联进程的信息的对象。攻击者可利用此信息对某些协议/应用程序中的已知/未知弱点发起攻击。
o The sctpAssocTable contains objects providing information on local and remote ports objects, that can be used to identify what ports are open on the machine and can thus suggest what attacks are likely to succeed, without the attacker having to run a port scanner.
o SCTPassectable包含提供有关本地和远程端口对象信息的对象，这些对象可用于识别计算机上打开的端口，从而建议可能成功的攻击，而攻击者无需运行端口扫描程序。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The above objects also have privacy implications, i.e., they disclose who is connecting to what hosts. These are sensitive from a perspective of preventing traffic analysis, and also to protect individual privacy.
上述对象还具有隐私含义，即它们公开了谁正在连接到什么主机。从防止流量分析和保护个人隐私的角度来看，这些都是敏感的。
The authors wish to thank Juergen Schoenwaelder, David Partain, Shawn A. Routhier, Ed Yarwood, John Linton, Shyamal Prasad, Juan-Francisco Martin, Dave Thaler, and Bert Wijnen for their invaluable comments.
作者希望感谢Juergen Schoenwaeld、David Partain、Shawn A.Routhier、Ed Yarwood、John Linton、Shymal Prasad、Juan Francisco Martin、Dave Thaler和Bert Wijnen的宝贵评论。
Javier Pastor-Balbas Ericsson Espana S.A. Network Signaling System Management Via de los Poblados 13 Madrid, 28033 Spain
Javier Pastor Balbas Ericsson Espana S.A.网络信号系统管理途经西班牙马德里13号，邮编28033
Phone: +34-91-339-1397
EMail: J.Javier.Pastor@ericsson.com
Phone: +34-91-339-1397
EMail: J.Javier.Pastor@ericsson.com
Maria-Carmen Belinchon Ericsson Espana S.A. Network Signaling System Management Via de los Poblados 13 Madrid, 28033 Spain
Maria Carmen Belinchon Ericsson Espana S.A.网络信号系统管理途经西班牙马德里13号，邮编28033
Phone: +34-91-339-3535
EMail: maria.carmen.belinchon@ericsson.com
Phone: +34-91-339-3535
EMail: maria.carmen.belinchon@ericsson.com
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、其代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。