draft-ietf-bridge-rstpmib-02.txt   draft-ietf-bridge-rstpmib-03.txt 
Internet Draft V. Ngai Internet Draft V. Ngai
Expires August 2002 Enterasys Networks Expires November 2002 Enterasys Networks
draft-ietf-bridge-rstpmib-02.txt E. Bell draft-ietf-bridge-rstpmib-03.txt E. Bell
3Com Corp. 3Com Corp.
March 2002 June 2002
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 5, line 5 skipping to change at page 5, line 5
contains some recommendations regarding usage of objects in the contains some recommendations regarding usage of objects in the
original bridge MIB by devices implementing the enhancements defined original bridge MIB by devices implementing the enhancements defined
here. here.
3.1. Structure of RSTP-MIB 3.1. Structure of RSTP-MIB
Objects in this MIB are defined as an addition to the dot1dStp group Objects in this MIB are defined as an addition to the dot1dStp group
in the original bridge MIB [BRIDGE-MIB]. The overall structure is in the original bridge MIB [BRIDGE-MIB]. The overall structure is
shown below: shown below:
Bridge MIB Name IEEE P802.1t(t) or 802.1w(w) Bridge MIB Name IEEE 802.1 Reference
Reference
dot1dStp dot1dStp
dot1dStpVersion (w) 17.6.1 ForceVersion dot1dStpVersion (w) 17.16.1 ForceVersion
dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount
dot1dStpPathCostDefault dot1dStpPathCostDefault
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration (w) 17.18.10 mcheck dot1dStpPortProtocolMigration (w) 17.18.10 mcheck
dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort
dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort
dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC
dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC
dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost
3.4. Relationship to Other MIBs 3.4. Relationship to Other MIBs
As described above, some IEEE 802.1D management objects have not been As described above, some IEEE 802.1D management objects have not been
included in this MIB because they overlap with objects in other MIBs included in this MIB because they overlap with objects in other MIBs
applicable to a bridge implementing this MIB. In particular, it is applicable to a bridge implementing this MIB. In particular, it is
assumed that a bridge implementing this MIB will implement the assumed that a bridge implementing this MIB will implement the
original bridge MIB [BRIDGEMIB]. original bridge MIB [BRIDGEMIB].
3.4.1. Relation to Original Bridge MIB 3.4.1. Relation to Original Bridge MIB
skipping to change at page 7, line 24 skipping to change at page 7, line 24
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
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 "200111160000Z" LAST-UPDATED "200206170000Z"
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 "200111160000Z" REVISION "200206170000Z"
DESCRIPTION DESCRIPTION
"Draft 1" "Draft 1"
::= { dot1dBridge 11 } ::= { dot1dBridge 11 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Addition to the dot1dStp group -- Addition to the dot1dStp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dStpVersion OBJECT-TYPE dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 9, line 23 skipping to change at page 9, line 23
SEQUENCE { SEQUENCE {
dot1dStpPortProtocolMigration dot1dStpPortProtocolMigration
TruthValue, TruthValue,
dot1dStpPortAdminEdgePort dot1dStpPortAdminEdgePort
TruthValue, TruthValue,
dot1dStpPortOperEdgePort dot1dStpPortOperEdgePort
TruthValue, TruthValue,
dot1dStpPortAdminPointToPoint dot1dStpPortAdminPointToPoint
INTEGER, INTEGER,
dot1dStpPortOperPointToPoint dot1dStpPortOperPointToPoint
TruthValue TruthValue,
dot1dStpPortAdminPathCost
INTEGER
} }
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 6 skipping to change at page 11, line 8
DESCRIPTION DESCRIPTION
"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
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administratively assigned value for the contribution
of this port to the path cost of paths towards the spanning
tree root.
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.
This complements the object dot1dStpPortPathCost, which
returns the operational value of the path cost."
REFERENCE
"IEEE 802.1D-1998: Section 8.5.5.3"
::= { dot1dStpExtPortEntry 6 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- rstpMIB - Conformance Information -- rstpMIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 } rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 }
rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 }
skipping to change at page 11, line 45 skipping to change at page 12, line 18
DESCRIPTION DESCRIPTION
"Default Spanning Tree path cost information." "Default Spanning Tree path cost information."
::= { rstpGroups 2 } ::= { rstpGroups 2 }
rstpPortGroup OBJECT-GROUP rstpPortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpPortProtocolMigration, dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort, dot1dStpPortAdminEdgePort,
dot1dStpPortOperEdgePort, dot1dStpPortOperEdgePort,
dot1dStpPortAdminPointToPoint, dot1dStpPortAdminPointToPoint,
dot1dStpPortOperPointToPoint dot1dStpPortOperPointToPoint,
dot1dStpPortAdminPathCost
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rapid Spanning Tree information for individual ports." "Rapid Spanning Tree information for individual ports."
::= { rstpGroups 3 } ::= { rstpGroups 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Compliance statements -- Compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 13, line 11 skipping to change at page 13, line 11
::= { rstpCompliances 1 } ::= { rstpCompliances 1 }
END END
5. Acknowledgments 5. Acknowledgments
This document was produced on behalf of the Bridge MIB Working Group This document was produced on behalf of the Bridge MIB Working Group
in the Operations and Management area of the Internet Engineering in the Operations and Management area of the Internet Engineering
Task Force. Task Force.
The authors wish to thank the members of the Bridge MIB Working Group The authors wish to thank the members of the Bridge MIB Working
for their comments and suggestions which improved this effort. Group, especially Alex Ruzin, for their comments and suggestions
which improved this effort.
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
 End of changes. 

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