draft-ietf-bridge-rstpmib-03.txt   draft-ietf-bridge-rstpmib-04.txt 
Internet Draft V. Ngai Internet Draft V. Ngai
Expires November 2002 Enterasys Networks Expires August 2004 Enterasys Networks
draft-ietf-bridge-rstpmib-03.txt E. Bell draft-ietf-bridge-rstpmib-04.txt E. Bell
3Com Corp. 3Com Corp.
June 2002 March 2004
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
with Rapid Spanning Tree Protocol with Rapid Spanning Tree Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC2026. Internet-Drafts are working documents of of Section 10 of RFC2026. Internet-Drafts are working documents of
the Internet Engineering Task Force (IETF), its areas, and its the Internet Engineering Task Force (IETF), its areas, and its
working groups. Note that other groups may also distribute working working groups. Note that other groups may also distribute working
skipping to change at page 1, line 33 skipping to change at page 1, line 33
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular, it defines a MIB module for managing the Rapid In particular, it defines a MIB module for managing the Rapid
Spanning Tree capability defined by the IEEE P802.1t [802.1t] and Spanning Tree capability defined by the IEEE P802.1t [802.1t] and
P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging
between Local Area Network (LAN) segments. between Local Area Network (LAN) segments.
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3.4.1 Relationship to Original Bridge MIB ...................... 5 3.4.1 Relationship to Original Bridge MIB ...................... 5
3.4.1.1 The dot1dBase Group .................................... 5 3.4.1.1 The dot1dBase Group .................................... 5
3.4.1.2 The dot1dStp Group ..................................... 5 3.4.1.2 The dot1dStp Group ..................................... 5
3.4.1.3 The dot1dTp Group ...................................... 6 3.4.1.3 The dot1dTp Group ...................................... 6
3.4.1.4 The dot1dStatic Group .................................. 6 3.4.1.4 The dot1dStatic Group .................................. 6
4 Definition for RSTP-MIB ...................................... 7 4 Definition for RSTP-MIB ...................................... 7
5 Acknowledgments .............................................. 13 5 Acknowledgments .............................................. 13
6 Security consideration ....................................... 13 6 Security consideration ....................................... 13
7 References ................................................... 14 7 References ................................................... 14
8 Authors' Addresses ........................................... 16 8 Authors' Addresses ........................................... 16
9 Full Copyright ............................................... 17 9 Intellectual Property ........................................ 17
10 Full Copyright .............................................. 18
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 7, line 14 skipping to change at page 7, line 14
4. Definitions for RSTP-MIB 4. Definitions for RSTP-MIB
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 IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dStp, dot1dStpPortEntry dot1dBridge, dot1dStp, dot1dStpPortEntry
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200206170000Z" LAST-UPDATED "200403210000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that support the Rapid Spanning Tree Protocol defined that support the Rapid Spanning Tree Protocol defined
by IEEE 802.1w." by IEEE 802.1w."
REVISION "200206170000Z" REVISION "200403210000Z"
DESCRIPTION DESCRIPTION
"Draft 1" "Draft 4"
::= { dot1dBridge 11 } ::= { dot1dBridge 11 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Addition to the dot1dStp group -- Addition to the dot1dStp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dStpVersion OBJECT-TYPE dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stpCompatible(0), stpCompatible(0),
rstp(2) rstp(2)
skipping to change at page 8, line 13 skipping to change at page 8, line 13
IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning
Tree Protocol specified in IEEE 802.1w. New value may Tree Protocol specified in IEEE 802.1w. New value may
be defined as future versions of the protocol become be defined as future versions of the protocol become
available." available."
REFERENCE REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp } DEFVAL { rstp }
::= { dot1dStp 16 } ::= { dot1dStp 16 }
dot1dStpTxHoldCount OBJECT-TYPE dot1dStpTxHoldCount OBJECT-TYPE
SYNTAX INTEGER (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value used by the Port Transmit state machine to limit "The value used by the Port Transmit state machine to limit
the maximum transmission rate." the maximum transmission rate."
REFERENCE REFERENCE
"IEEE 802.1w clause 17.16.6" "IEEE 802.1w clause 17.16.6"
DEFVAL { 3 } DEFVAL { 3 }
::= { dot1dStp 17 } ::= { dot1dStp 17 }
skipping to change at page 9, line 25 skipping to change at page 9, line 25
TruthValue, TruthValue,
dot1dStpPortAdminEdgePort dot1dStpPortAdminEdgePort
TruthValue, TruthValue,
dot1dStpPortOperEdgePort dot1dStpPortOperEdgePort
TruthValue, TruthValue,
dot1dStpPortAdminPointToPoint dot1dStpPortAdminPointToPoint
INTEGER, INTEGER,
dot1dStpPortOperPointToPoint dot1dStpPortOperPointToPoint
TruthValue, TruthValue,
dot1dStpPortAdminPathCost dot1dStpPortAdminPathCost
INTEGER Integer32
} }
dot1dStpPortProtocolMigration OBJECT-TYPE dot1dStpPortProtocolMigration OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When operating in RSTP (version 2) mode, writing TRUE(1) "When operating in RSTP (version 2) mode, writing TRUE(1)
to this object forces this port to transmit RSTP BPDUs. to this object forces this port to transmit RSTP BPDUs.
Any other operation on this object has no effect and Any other operation on this object has no effect and
skipping to change at page 11, line 9 skipping to change at page 11, line 9
"The operational point-to-point status of the LAN segment "The operational point-to-point status of the LAN segment
attached to this port. It indicates whether a port is attached to this port. It indicates whether a port is
considered to have a point-to-point connection or not. considered to have a point-to-point connection or not.
The value is determined by management or by auto-detection, The value is determined by management or by auto-detection,
as described in the dot1dStpPortAdminPointToPoint object." as described in the dot1dStpPortAdminPointToPoint object."
REFERENCE REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 5 } ::= { dot1dStpExtPortEntry 5 }
dot1dStpPortAdminPathCost OBJECT-TYPE dot1dStpPortAdminPathCost OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX Integer32 (0..200000000)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administratively assigned value for the contribution "The administratively assigned value for the contribution
of this port to the path cost of paths towards the spanning of this port to the path cost of paths towards the spanning
tree root. tree root.
Writing a value of '0' assigns the automatically calculated Writing a value of '0' assigns the automatically calculated
default Path Cost value to the port. If the default Path default Path Cost value to the port. If the default Path
Cost is being used, this object returns '0' when read. Cost is being used, this object returns '0' when read.
This complements the object dot1dStpPortPathCost, which This complements the object dot1dStpPortPathCost or
returns the operational value of the path cost." dot1dStpPortPathCost32, which returns the operational value
of the path cost."
REFERENCE REFERENCE
"IEEE 802.1D-1998: Section 8.5.5.3" "IEEE 802.1D-1998: Section 8.5.5.3"
::= { dot1dStpExtPortEntry 6 } ::= { dot1dStpExtPortEntry 6 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- rstpMIB - Conformance Information -- rstpMIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 } rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 }
skipping to change at page 16, line 23 skipping to change at page 16, line 23
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Vivian Ngai Vivian Ngai
Enterasys Networks Enterasys Networks
2691 South Decker Lake Lane 2691 South Decker Lake Lane
Salt Lake City, UT 84119 Salt Lake City, UT 84119
USA USA
Phone: +1 801-887-9802 Phone: +1 801 556 5652
Fax: +1 801-972-5789 Email: vivian_ngai@acm.org
Email: vngai@enterasys.com
9. Full Copyright 9. Intellectual Property
Copyright (C) The Internet Society (date). All Rights Reserved. The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
10. Full Copyright
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, copied, explain it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed Internet Society or other Internet organizations, except as needed
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/