Network Working Group D. Levi
Request for Comments: 4318 Nortel Networks
Category: Standards Track D. Harrington
Effective Software
December 2005
Network Working Group D. Levi
Request for Comments: 4318 Nortel Networks
Category: Standards Track D. Harrington
Effective Software
December 2005
Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol
基于快速生成树协议的网桥托管对象定义
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 (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This memo defines an SMIv2 MIB module for managing the Rapid Spanning Tree capability defined by the IEEE P802.1t and P802.1w amendments to IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) segments. The objects in this MIB are defined to apply both to transparent bridging and to bridges connected by subnetworks other than LAN segments.
本备忘录定义了一个SMIv2 MIB模块，用于管理IEEE标准802.1D-1998的IEEE P802.1t和P802.1w修正案中定义的用于局域网（LAN）网段之间桥接的快速生成树功能。此MIB中的对象定义为既适用于透明桥接，也适用于由除LAN段以外的子网连接的桥接。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
3. Relationship to IEEE 802.1t and 802.1w Amendments ...............2
4. Relation to the BRIDGE-MIB ......................................3
5. Definitions for RSTP-MIB ........................................3
6. Acknowledgements ...............................................10
7. IANA Considerations ............................................10
8. Security Considerations ........................................10
9. Normative References ...........................................11
10. Informative References ........................................12
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
3. Relationship to IEEE 802.1t and 802.1w Amendments ...............2
4. Relation to the BRIDGE-MIB ......................................3
5. Definitions for RSTP-MIB ........................................3
6. Acknowledgements ...............................................10
7. IANA Considerations ............................................10
8. Security Considerations ........................................10
9. Normative References ...........................................11
10. Informative References ........................................12
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 memo defines an SMIv2 MIB module for managing the Rapid Spanning Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] for bridging between Local Area Network (LAN) segments. The objects in this MIB are defined to apply both to transparent bridging and to bridges connected by subnetworks other than LAN segments.
本备忘录定义了一个SMIv2 MIB模块，用于管理由IEEE标准802.1D-1998[802.1D-1998]的IEEE P802.1t[802.1t]和P802.1w[802.1w]修正案定义的快速生成树（RSTP）能力，用于局域网（LAN）网段之间的桥接。此MIB中的对象定义为既适用于透明桥接，也适用于由除LAN段以外的子网连接的桥接。
This document defines managed objects for the Rapid Spanning Tree Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to 802.1D-1998.
本文档为IEEE P802.1t和IEEE P802.1w对802.1D-1998的修订定义的快速生成树协议定义了托管对象。
RSTP-MIB Name IEEE 802.1 Reference
RSTP-MIB名称IEEE 802.1参考
dot1dStp dot1dStpVersion (w) 17.16.1 ForceVersion dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount dot1dStpExtPortTable dot1dStpPortProtocolMigration (w) 17.18.10 mcheck dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost
dot1dStp dot1dStpVersion（w）17.16.1强制版本dot1dStpTxHoldCount（w）17.16.6 TxHoldCount dot1dstpextportable dot1dstportprotocolmigration（w）17.18.10 mcheck dot1dstportadminigeport（t）18.3.3管理报告dot1dstportoperatedeport（t）18.3.4操作报告dot1dstportadminimportadminingpointpoint（w）6.4.3 adminPointToPointMAC DOT1DSTPortOpperPointTopoint（w）6.4.3 OpperPointTopointMac DOT1DSTPortAdminPathCost（D）8.5.5.3路径成本
There are concerns that there may be changes made in the 802.1D-2004 edition that would lead to non-backward-compatible SMI changes for 802.1t and 802.1w managed objects in the MIB modules. The Bridge MIB working group decided to 'freeze' the technical content of the MIB modules at a level that is compatible with the 802.1t and 802.1w
有人担心，802.1D-2004版中的更改可能会导致MIB模块中802.1t和802.1w受管对象的SMI更改不向后兼容。桥接MIB工作组决定“冻结”MIB模块的技术内容，使其与802.1t和802.1w兼容
versions, and leave to the IEEE 802.1 working group any updates beyond this.
版本，并将超出此范围的任何更新留给IEEE 802.1工作组。
For informational purposes only, these are the references for the above objects in 802.1D-2004 [802.1D-2004].
仅供参考，这些是802.1D-2004[802.1D-2004]中上述对象的参考。
RSTP-MIB Name IEEE 802.1D-2004 Reference
RSTP-MIB名称IEEE 802.1D-2004参考
dot1dStp dot1dStpVersion 17.13.4 ForceVersion dot1dStpTxHoldCount 17.13.12 TxHoldCount dot1dStpExtPortTable dot1dStpPortProtocolMigration 17.19.13 mcheck dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort dot1dStpPortOperEdgePort 17.19.17 operEdgePort dot1dStpPortAdminPointToPoint 6.4.3 adminPointToPointMAC dot1dStpPortOperPointToPoint 6.4.3 operPointToPointMAC dot1dStpPortAdminPathCost 17.13.11 Path Cost
dot1dStp dot1dStpVersion 17.13.4强制版本dot1dStpTxHoldCount 17.13.12 TxHoldCount dot1dStpExtPortTable dot1dstportprotocol迁移17.19.13 mcheck dot1dstportadminigeport 17.13.1管理端口dot1dstportoperatedport 17.19.17操作端口dot1dstportadminintopointmac dot1dportoperateportpointtopoint 6.4.3OpperPointTopointMac Dot1DSTPortAdminPathCost 17.13.11路径成本
The objects in the RSTP-MIB supplement those defined in the Bridge MIB [RFC4188].
RSTP-MIB中的对象补充了桥接MIB[RFC4188]中定义的对象。
The Original BRIDGE-MIB [RFC1493] has been updated in an SMIv2- compliant version [RFC4188]. Conformance statements have been added and some description and reference clauses have been updated. The interpretations of some objects were changed to accommodate IEEE 802.1t and 802.1w amendments.
原来的BRIDGE-MIB[RFC1493]已更新为符合SMIv2的版本[RFC4188]。添加了一致性声明，并更新了一些说明和参考条款。对某些对象的解释进行了更改，以适应IEEE 802.1t和802.1w修正案。
The object dot1dStpPortPathCost32 was added to support IEEE 802.1t, and the permissible values of dot1dStpPriority and dot1dStpPortPriority have been clarified for bridges supporting IEEE 802.1t or IEEE 802.1w. The interpretation of dot1dStpTimeSinceTopologyChange has been clarified for bridges supporting the RSTP.
添加了对象Dot1DSTPortPathCost32以支持IEEE 802.1t，并澄清了支持IEEE 802.1t或IEEE 802.1w的网桥的Dot1DSTPortPriority和Dot1DSTPortPriority的允许值。对于支持RSTP的桥梁，dot1dStpTimeSinceTopologyChange的解释已得到澄清。
See the updated BRIDGE-MIB [RFC4188] for details.
有关详细信息，请参阅更新的BRIDGE-MIB[RFC4188]。
RSTP-MIB DEFINITIONS ::= BEGIN
RSTP-MIB DEFINITIONS ::= BEGIN
-- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- -------------------------------------------------------------
IMPORTS
进口
MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 FROM SNMPv2-SMI TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF dot1dStp, dot1dStpPortEntry FROM BRIDGE-MIB;
SNMPv2中的模块标识、对象类型、整数32、mib-2、SNMPv2中的SMI TruthValue、SNMPv2中的TC模块符合性、SNMPv2 CONF dot1dStp中的对象组、BRIDGE-mib中的dot1dstportentry；
rstpMIB MODULE-IDENTITY LAST-UPDATED "200512070000Z" ORGANIZATION "IETF Bridge MIB Working Group" CONTACT-INFO "Email: Bridge-mib@ietf.org" DESCRIPTION "The Bridge MIB Extension module for managing devices that support the Rapid Spanning Tree Protocol defined by IEEE 802.1w.
rstpMIB模块标识最后更新的“2005120700NZ”组织“IETF桥接MIB工作组”联系人信息电子邮件：Bridge-mib@ietf.org“描述”桥接MIB扩展模块，用于管理支持IEEE 802.1w定义的快速生成树协议的设备。
Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4318; See the RFC itself for full legal notices."
版权所有（C）互联网协会（2005年）。此版本的MIB模块是RFC 4318的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200512070000Z"
DESCRIPTION
"The initial version of this MIB module as published in
RFC 4318."
::= { mib-2 134 }
REVISION "200512070000Z"
DESCRIPTION
"The initial version of this MIB module as published in
RFC 4318."
::= { mib-2 134 }
-- ---------------------------------------------------------- --
-- subtrees in the RSTP-MIB
-- ---------------------------------------------------------- --
-- ---------------------------------------------------------- --
-- subtrees in the RSTP-MIB
-- ---------------------------------------------------------- --
rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 }
rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 }
rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 }
rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 }
-- -------------------------------------------------------------
-- Addition to the dot1dStp group
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- Addition to the dot1dStp group
-- -------------------------------------------------------------
dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER {
stpCompatible(0),
rstp(2)
}
MAX-ACCESS read-write
STATUS current
dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER {
stpCompatible(0),
rstp(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The version of Spanning Tree Protocol the bridge is currently running. The value 'stpCompatible(0)' indicates the Spanning Tree Protocol specified in IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid Spanning Tree Protocol specified in IEEE 802.1w and clause 17 of 802.1D-2004. The values are directly from the IEEE standard. New values may be defined as future versions of the protocol become available.
描述“网桥当前运行的生成树协议版本。值'STPComatible（0）'表示IEEE 802.1D-1998和'rstp（2）中指定的生成树协议'表示IEEE 802.1w和802.1D-2004第17条中规定的快速生成树协议。这些值直接来自IEEE标准。新值可在协议的未来版本可用时定义。
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp }
::= { dot1dStp 16 }
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp }
::= { dot1dStp 16 }
dot1dStpTxHoldCount OBJECT-TYPE SYNTAX Integer32 (1..10) MAX-ACCESS read-write STATUS current DESCRIPTION "The value used by the Port Transmit state machine to limit the maximum transmission rate.
dot1dStpTxHoldCount对象类型语法整数32（1..10）MAX-ACCESS读写状态当前描述“端口传输状态机用于限制最大传输速率的值。
The value of this object MUST be retained across reinitializations of the management system."
此对象的值必须在管理系统的重新初始化过程中保留。”
REFERENCE
"IEEE 802.1w clause 17.16.6"
DEFVAL { 3 }
::= { dot1dStp 17 }
REFERENCE
"IEEE 802.1w clause 17.16.6"
DEFVAL { 3 }
::= { dot1dStp 17 }
--
-- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault
-- in an earlier version of this MIB. It has since been
-- obsoleted, and should not be used.
--
--
-- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault
-- in an earlier version of this MIB. It has since been
-- obsoleted, and should not be used.
--
dot1dStpExtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dStpExtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains port-specific Rapid Spanning Tree
information."
::= { dot1dStp 19 }
dot1dStpExtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dStpExtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains port-specific Rapid Spanning Tree
information."
::= { dot1dStp 19 }
dot1dStpExtPortEntry OBJECT-TYPE
SYNTAX Dot1dStpExtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Rapid Spanning Tree information maintained by
each port."
AUGMENTS { dot1dStpPortEntry }
::= { dot1dStpExtPortTable 1 }
dot1dStpExtPortEntry OBJECT-TYPE
SYNTAX Dot1dStpExtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Rapid Spanning Tree information maintained by
each port."
AUGMENTS { dot1dStpPortEntry }
::= { dot1dStpExtPortTable 1 }
Dot1dStpExtPortEntry ::=
SEQUENCE {
dot1dStpPortProtocolMigration
TruthValue,
dot1dStpPortAdminEdgePort
TruthValue,
dot1dStpPortOperEdgePort
TruthValue,
dot1dStpPortAdminPointToPoint
INTEGER,
dot1dStpPortOperPointToPoint
TruthValue,
dot1dStpPortAdminPathCost
Integer32
}
Dot1dStpExtPortEntry ::=
SEQUENCE {
dot1dStpPortProtocolMigration
TruthValue,
dot1dStpPortAdminEdgePort
TruthValue,
dot1dStpPortOperEdgePort
TruthValue,
dot1dStpPortAdminPointToPoint
INTEGER,
dot1dStpPortOperPointToPoint
TruthValue,
dot1dStpPortAdminPathCost
Integer32
}
dot1dStpPortProtocolMigration OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When operating in RSTP (version 2) mode, writing true(1)
to this object forces this port to transmit RSTP BPDUs.
Any other operation on this object has no effect and
it always returns false(2) when read."
REFERENCE
"IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
::= { dot1dStpExtPortEntry 1 }
dot1dStpPortProtocolMigration OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When operating in RSTP (version 2) mode, writing true(1)
to this object forces this port to transmit RSTP BPDUs.
Any other operation on this object has no effect and
it always returns false(2) when read."
REFERENCE
"IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
::= { dot1dStpExtPortEntry 1 }
dot1dStpPortAdminEdgePort OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative value of the Edge Port parameter. A value of true(1) indicates that this port should be assumed as an edge-port, and a value of false(2) indicates that this port should be assumed as a non-edge-port.
Dot1DSTPortAdminedgePort对象类型语法TruthValue MAX-ACCESS读写状态当前描述“边缘端口参数的管理值。true值（1）表示应将此端口假定为边缘端口，false值（2）表示应将此端口假定为非边缘端口。
Setting this object will also cause the corresponding instance of dot1dStpPortOperEdgePort to change to the same value. Note that even when this object's value is true, the value of the corresponding instance of dot1dStpPortOperEdgePort can be false if a BPDU has been received.
设置此对象还将导致dot1dstportoperedeport的相应实例更改为相同的值。请注意，即使此对象的值为true，如果已接收到BPDU，则DOT1DSTPortoperedReport的对应实例的值也可能为false。
The value of this object MUST be retained across reinitializations of the management system."
此对象的值必须在管理系统的重新初始化过程中保留。”
REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.3"
::= { dot1dStpExtPortEntry 2 }
REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.3"
::= { dot1dStpExtPortEntry 2 }
dot1dStpPortOperEdgePort OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The operational value of the Edge Port parameter. The object is initialized to the value of the corresponding instance of dot1dStpPortAdminEdgePort. When the corresponding instance of dot1dStpPortAdminEdgePort is set, this object will be changed as well. This object will also be changed to false on reception of a BPDU."
DOT1DSTPortoperedReport对象类型语法TruthValue MAX-ACCESS只读状态当前说明“边缘端口参数的操作值。该对象初始化为Dot1DSTPortAdminedgePort的相应实例的值。当设置Dot1DSTPortAdminedgePort的相应实例时，此对象也将更改。接收到BPDU时，此对象也将更改为false。”
REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.4"
::= { dot1dStpExtPortEntry 3 }
REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.4"
::= { dot1dStpExtPortEntry 3 }
dot1dStpPortAdminPointToPoint OBJECT-TYPE
SYNTAX INTEGER {
forceTrue(0),
forceFalse(1),
auto(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative point-to-point status of the LAN segment
attached to this port, using the enumeration values of the
IEEE 802.1w clause. A value of forceTrue(0) indicates
that this port should always be treated as if it is
connected to a point-to-point link. A value of
forceFalse(1) indicates that this port should be treated as
having a shared media connection. A value of auto(2)
indicates that this port is considered to have a
point-to-point link if it is an Aggregator and all of its
dot1dStpPortAdminPointToPoint OBJECT-TYPE
SYNTAX INTEGER {
forceTrue(0),
forceFalse(1),
auto(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative point-to-point status of the LAN segment
attached to this port, using the enumeration values of the
IEEE 802.1w clause. A value of forceTrue(0) indicates
that this port should always be treated as if it is
connected to a point-to-point link. A value of
forceFalse(1) indicates that this port should be treated as
having a shared media connection. A value of auto(2)
indicates that this port is considered to have a
point-to-point link if it is an Aggregator and all of its
members are aggregatable, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by management means. Manipulating this object changes the underlying adminPortToPortMAC.
成员是可聚合的，或者如果MAC实体配置为全双工操作，则可以通过自动协商或通过管理手段。操作此对象会更改基础adminPortToPortMAC。
The value of this object MUST be retained across reinitializations of the management system."
此对象的值必须在管理系统的重新初始化过程中保留。”
REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 4 }
REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 4 }
dot1dStpPortOperPointToPoint OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational point-to-point status of the LAN segment
attached to this port. It indicates whether a port is
considered to have a point-to-point connection.
If adminPointToPointMAC is set to auto(2), then the value
of operPointToPointMAC is determined in accordance with the
specific procedures defined for the MAC entity concerned,
as defined in IEEE 802.1w, clause 6.5. The value is
determined dynamically; that is, it is re-evaluated whenever
the value of adminPointToPointMAC changes, and whenever
the specific procedures defined for the MAC entity evaluate
a change in its point-to-point status."
REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 5 }
dot1dStpPortOperPointToPoint OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational point-to-point status of the LAN segment
attached to this port. It indicates whether a port is
considered to have a point-to-point connection.
If adminPointToPointMAC is set to auto(2), then the value
of operPointToPointMAC is determined in accordance with the
specific procedures defined for the MAC entity concerned,
as defined in IEEE 802.1w, clause 6.5. The value is
determined dynamically; that is, it is re-evaluated whenever
the value of adminPointToPointMAC changes, and whenever
the specific procedures defined for the MAC entity evaluate
a change in its point-to-point status."
REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 5 }
dot1dStpPortAdminPathCost OBJECT-TYPE SYNTAX Integer32 (0..200000000) MAX-ACCESS read-write STATUS current DESCRIPTION "The administratively assigned value for the contribution of this port to the path cost of paths toward the spanning tree root.
DOT1DSPTPORTADMINPATHCOST对象类型语法整数32（0..20000000）MAX-ACCESS读写状态当前描述“此端口对指向生成树根的路径的路径成本的贡献的管理分配值。
Writing a value of '0' assigns the automatically calculated default Path Cost value to the port. If the default Path Cost is being used, this object returns '0' when read.
写入值“0”会将自动计算的默认路径成本值分配给端口。如果正在使用默认路径成本，则此对象在读取时返回“0”。
This complements the object dot1dStpPortPathCost or dot1dStpPortPathCost32, which returns the operational value of the path cost.
这是对对象Dot1DSTPortPathCost或Dot1DSTPortPathCost32的补充，后者返回路径成本的操作值。
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE
"IEEE 802.1D-1998: Section 8.5.5.3"
::= { dot1dStpExtPortEntry 6 }
The value of this object MUST be retained across
reinitializations of the management system."
REFERENCE
"IEEE 802.1D-1998: Section 8.5.5.3"
::= { dot1dStpExtPortEntry 6 }
-- -------------------------------------------------------------
-- rstpMIB - Conformance Information
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- rstpMIB - Conformance Information
-- -------------------------------------------------------------
rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 }
rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 }
rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 }
rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 }
-- -------------------------------------------------------------
-- Units of conformance
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- Units of conformance
-- -------------------------------------------------------------
rstpBridgeGroup OBJECT-GROUP
OBJECTS {
dot1dStpVersion,
dot1dStpTxHoldCount
}
STATUS current
DESCRIPTION
"Rapid Spanning Tree information for the bridge."
::= { rstpGroups 1 }
rstpBridgeGroup OBJECT-GROUP
OBJECTS {
dot1dStpVersion,
dot1dStpTxHoldCount
}
STATUS current
DESCRIPTION
"Rapid Spanning Tree information for the bridge."
::= { rstpGroups 1 }
rstpPortGroup OBJECT-GROUP
OBJECTS {
dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort,
dot1dStpPortOperEdgePort,
dot1dStpPortAdminPointToPoint,
dot1dStpPortOperPointToPoint,
dot1dStpPortAdminPathCost
}
STATUS current
DESCRIPTION
"Rapid Spanning Tree information for individual ports."
::= { rstpGroups 2 }
rstpPortGroup OBJECT-GROUP
OBJECTS {
dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort,
dot1dStpPortOperEdgePort,
dot1dStpPortAdminPointToPoint,
dot1dStpPortOperPointToPoint,
dot1dStpPortAdminPathCost
}
STATUS current
DESCRIPTION
"Rapid Spanning Tree information for individual ports."
::= { rstpGroups 2 }
-- -------------------------------------------------------------
-- Compliance statements
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- Compliance statements
-- -------------------------------------------------------------
rstpCompliance MODULE-COMPLIANCE STATUS current
rstpCompliance模块-合规状态当前
DESCRIPTION
"The compliance statement for device support of Rapid
Spanning Tree Protocol (RSTP) bridging services."
MODULE
MANDATORY-GROUPS {
rstpBridgeGroup,
rstpPortGroup
}
::= { rstpCompliances 1 }
DESCRIPTION
"The compliance statement for device support of Rapid
Spanning Tree Protocol (RSTP) bridging services."
MODULE
MANDATORY-GROUPS {
rstpBridgeGroup,
rstpPortGroup
}
::= { rstpCompliances 1 }
END
终止
This document was produced on behalf of the Bridge MIB Working Group in the Operations and Management area of the Internet Engineering Task Force.
本文件代表互联网工程任务组运营和管理领域的桥梁MIB工作组编制。
The authors wish to thank the members of the Bridge MIB Working Group, especially Alex Ruzin, for their comments and suggestions that improved this effort.
作者希望感谢Bridge MIB工作组的成员，特别是Alex Ruzin，感谢他们的意见和建议改进了这项工作。
Vivian Ngai and Les Bell were the initial authors of this document, and did the bulk of the development work for this document.
Vivian Ngai和Les Bell是本文件的最初作者，并为本文件进行了大部分开发工作。
The IANA has assigned the following OID:
IANA已分配以下OID：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
rstpMIB { mib-2 134 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
rstpMIB { mib-2 134 }
There are a number of management objects defined in this MIB module with 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子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
Writable objects that could be misused to cause network delays and spanning tree instabilities include dot1dStpVersion, dot1dStpTxHoldCount, dot1dStpPortProtocolMigration, dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.
可能被误用以导致网络延迟和生成树不稳定的可写对象包括dot1dStpVersion、dot1dStpTxHoldCount、dot1dstportprotocolmigration、dot1dstportadminedgeport和dot1dstportadminpathcost。
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. It is thus 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通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
dot1dStpVersion could be read by an attacker to identify environments containing applications or protocols that are potentially sensitive to RSTP mode.
攻击者可以读取dot1dStpVersion以识别包含对RSTP模式可能敏感的应用程序或协议的环境。
dot1dStpPortAdminPointToPoint could be used to mislead an access control protocol, such as 802.1x, to believe that only one other system is attached to a LAN segment and to enable network access based on that assumption. This situation could permit potential man-in-the-middle attacks.
Dot1DSTPortAdminPointPointPointPoint可用于误导访问控制协议（如802.1x），以为只有一个其他系统连接到LAN网段，并基于该假设启用网络访问。这种情况可能允许潜在的中间人攻击。
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实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
[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月。
[802.1D-1998] "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Media Access Control (MAC) Bridges: Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e." ISO/IEC 15802-3: 1998.
[802.1D-1998]“信息技术-系统间电信和信息交换-局域网和城域网-通用规范-第3部分：媒体访问控制（MAC）网桥：修订版。这是ISO/IEC 10038:1993、802.1j-1992和802.6k-1992的修订版。它包含了P802.11c、P802.1p和P802.12e。”ISO/IEC 15802-3:1998。
[RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects for Bridges", RFC 4188, September 2005.
[RFC4188]Norseth，K.和E.Bell，“网桥托管对象的定义”，RFC 4188，2005年9月。
[802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Media Access Control (MAC) Bridges: Technical and Editorial Corrections".
[802.1t]IEEE 802.1t-2001，“（对IEEE标准802.1D的修订）IEEE信息技术标准-系统间电信和信息交换-局域网和城域网-通用规范-第3部分：媒体访问控制（MAC）网桥：技术和编辑更正”。
[802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE Standard for Information technology-- Telecommunications and information exchange between systems--Local and metropolitan area networks--Common Specifications--Part 3: Media Access Control (MAC) Bridges: Rapid Reconfiguation".
[802.1w]IEEE 802.1w-2001，“（对IEEE标准802.1D的修订）IEEE信息技术标准——系统间电信和信息交换——局域网和城域网——通用规范——第3部分：媒体访问控制（MAC）网桥：快速识别”。
[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月。
[802.1D-2004] IEEE Project 802 Local and Metropolitan Area Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004.
[802.1D-2004]IEEE项目802局域网和城域网，“IEEE标准802.1D-2004 MAC网桥”，2004年。
[RFC1493] Decker, E., Langille, P., Rijsinghani, A., and K. McCloghrie, "Definitions of Managed Objects for Bridges", RFC 1493, July 1993.
[RFC1493]Decker，E.，Langille，P.，Rijsinghani，A.，和K.McCloghrie，“桥梁管理对象的定义”，RFC 1493，1993年7月。
Authors' Addresses
作者地址
David Levi Nortel Networks 4655 Great America Parkway Santa Clara, CA 95054 USA
David Levi Nortel Networks 4655美国加利福尼亚州圣克拉拉大美洲大道95054
Phone: +1 408 495 5138
EMail: dlevi@nortel.com
Phone: +1 408 495 5138
EMail: dlevi@nortel.com
David Harrington Effective Software 50 Harding Rd. Portsmouth, NH 03801 USA
美国新罕布什尔州朴茨茅斯哈丁路50号大卫哈林顿有效软件公司03801
Phone: +1 603 436 8634
EMail: ietfdbh@comcast.net
Phone: +1 603 436 8634
EMail: ietfdbh@comcast.net
Les Bell Hemel Hempstead Herts. HP2 7YU UK
贝尔·赫梅尔·亨普斯特德·赫茨。HP2 7YU英国
EMail: elbell@ntlworld.com
EMail: elbell@ntlworld.com
Vivian Ngai Salt lake City, UT USA
美国犹他州盐湖城Vivian Ngai
EMail: vivian_ngai@acm.org
EMail: vivian_ngai@acm.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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/SHE 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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见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编辑功能的资金目前由互联网协会提供。