draft-ietf-bridge-bridgemib-smiv2-00.txt   draft-ietf-bridge-bridgemib-smiv2-01.txt 
Internet Draft Editor of this version: Internet Draft Editor of this version:
Expires December 2001 E. Bell Expires May 2002 K.C. Norseth
draft-ietf-bridge-bridgemib-smiv2-00.txt 3Com Corp. draft-ietf-bridge-bridgemib-smiv2-01.txt Enterasys Networks
Obsoletes: 1493 Authors of previous version: Obsoletes: 1493 Authors of previous version:
E. Bell
3Com Corp.
E. Decker E. Decker
cisco Systems, Inc. Cisco Systems, Inc.
P. Langille P. Langille
Newbridge Networks Newbridge Networks
A. Rijhsinghani A. Rijhsinghani
Enterasys Networks Enterasys Networks
K. McCloghrie K. McCloghrie
cisco Systems, Inc. Cisco Systems, Inc.
June 2001 November 2001
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with This document is an Internet Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet Drafts are working all provisions of Section 10 of RFC2026. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups. Note that other groups may also distribute and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts. working documents as Internet Drafts.
skipping to change at page 9, line 24 skipping to change at page 8, line 7
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Integer32, TimeTicks, mib-2 Counter32, Integer32, TimeTicks, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, MacAddress TEXTUAL-CONVENTION, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
; ;
bridgeMIB MODULE-IDENTITY bridgeMIB MODULE-IDENTITY
LAST-UPDATED "200106260000Z" LAST-UPDATED "200111180000Z"
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 module for managing devices that support "The Bridge MIB module for managing devices that support
IEEE 802.1D." IEEE 802.1D."
REVISION "200111190000Z"
DESCRIPTION
"Draft 1: 01 version of draft."
REVISION "200106260000Z" REVISION "200106260000Z"
DESCRIPTION DESCRIPTION
"Draft 0: initial translation of RFC 1493 to SMIv2." "Draft 1: initial translation of RFC 1493 to SMIv2."
REVISION "199307310000Z" REVISION "199307310000Z"
DESCRIPTION DESCRIPTION
"RFC 1493: SMIv1 version." "RFC 1493: SMIv1 version."
::= { dot1dBridge 8 } ::= { dot1dBridge 8 }
dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Textual Conventions -- Textual Conventions
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- All representations of MAC addresses in this MIB Module use, -- All representations of MAC addresses in this MIB Module use,
-- as a textual convention (i.e. this convention does not affect -- as a textual convention (i.e. this convention does not affect
-- their encoding), the data type MacAddress, defined in -- their encoding), the data type MacAddress, defined in
-- SNMPv2-TC. -- SNMPv2-TC.
-- Similarly, all representations of Bridge-Id in this MIB -- Similarly, all representations of Bridge-Id in this MIB
skipping to change at page 13, line 41 skipping to change at page 12, line 16
dot1dBasePort OBJECT-TYPE dot1dBasePort OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The port number of the port for which this entry "The port number of the port for which this entry
contains bridge management information." contains bridge management information."
::= { dot1dBasePortEntry 1 } ::= { dot1dBasePortEntry 1 }
dot1dBasePortIfIndex OBJECT-TYPE dot1dBasePortIfIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the instance of the ifIndex object, "The value of the instance of the ifIndex object,
defined in MIB-II, for the interface corresponding defined in MIB-II, for the interface corresponding
to this port." to this port."
::= { dot1dBasePortEntry 2 } ::= { dot1dBasePortEntry 2 }
dot1dBasePortCircuit OBJECT-TYPE dot1dBasePortCircuit OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
skipping to change at page 15, line 28 skipping to change at page 13, line 50
::= { dot1dStp 1 } ::= { dot1dStp 1 }
dot1dStpPriority OBJECT-TYPE dot1dStpPriority OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the write-able portion of the Bridge ID, "The value of the write-able portion of the Bridge ID,
i.e., the first two octets of the (8 octet long) Bridge i.e., the first two octets of the (8 octet long) Bridge
ID. The other (last) 6 octets of the Bridge ID are ID. The other (last) 6 octets of the Bridge ID are
given by the value of dot1dBaseBridgeAddress." given by the value of dot1dBaseBridgeAddress.
Permissible values are 0-61440, in steps of 4096."
REFERENCE REFERENCE
"IEEE 802.1D-1990: Section 4.5.3.7" " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3.""
::= { dot1dStp 2 } ::= { dot1dStp 2 }
dot1dStpTimeSinceTopologyChange OBJECT-TYPE dot1dStpTimeSinceTopologyChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in hundredths of a second) since the "The time (in hundredths of a second) since the
last time a topology change was detected by the last time a topology change was detected by the
bridge entity." bridge entity.
For RSTP, this reports the time since the tcWhile timer for
any port on this Bridge was non-zero."
REFERENCE REFERENCE
"IEEE 802.1D-1990: Section 6.8.1.1.3" " IEEE 802.1w clause 14.8.1.1."
::= { dot1dStp 3 } ::= { dot1dStp 3 }
dot1dStpTopChanges OBJECT-TYPE dot1dStpTopChanges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of topology changes detected by "The total number of topology changes detected by
this bridge since the management entity was last this bridge since the management entity was last
reset or initialized." reset or initialized.
For RSTP, this reports the count of times that there have
been at least one non-zero tcWhile timer on this Bridge."
REFERENCE REFERENCE
"IEEE 802.1D-1990: Section 6.8.1.1.3" " IEEE 802.1w clause 14.8.1.1."
::= { dot1dStp 4 } ::= { dot1dStp 4 }
dot1dStpDesignatedRoot OBJECT-TYPE dot1dStpDesignatedRoot OBJECT-TYPE
SYNTAX BridgeId SYNTAX BridgeId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bridge identifier of the root of the spanning "The bridge identifier of the root of the spanning
tree as determined by the Spanning Tree Protocol tree as determined by the Spanning Tree Protocol
as executed by this node. This value is used as as executed by this node. This value is used as
skipping to change at page 20, line 18 skipping to change at page 18, line 26
::= { dot1dStpPortEntry 1 } ::= { dot1dStpPortEntry 1 }
dot1dStpPortPriority OBJECT-TYPE dot1dStpPortPriority OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the priority field which is contained in "The value of the priority field which is contained in
the first (in network byte order) octet of the (2 octet the first (in network byte order) octet of the (2 octet
long) Port ID. The other octet of the Port ID is given long) Port ID. The other octet of the Port ID is given
by the value of dot1dStpPort." by the value of dot1dStpPort.
Permissible values are 0-240, in steps of 16."
REFERENCE REFERENCE
"IEEE 802.1D-1990: Section 4.5.5.1" " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3."
::= { dot1dStpPortEntry 2 } ::= { dot1dStpPortEntry 2 }
dot1dStpPortState OBJECT-TYPE dot1dStpPortState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
blocking(2), blocking(2),
listening(3), listening(3),
learning(4), learning(4),
forwarding(5), forwarding(5),
broken(6) broken(6)
skipping to change at page 21, line 18 skipping to change at page 19, line 23
dot1dStpPortPathCost OBJECT-TYPE dot1dStpPortPathCost OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The contribution of this port to the path cost of "The contribution of this port to the path cost of
paths towards the spanning tree root which include paths towards the spanning tree root which include
this port. 802.1D-1990 recommends that the this port. 802.1D-1990 recommends that the
default value of this parameter be in inverse default value of this parameter be in inverse
proportion to the speed of the attached LAN." proportion to the speed of the attached LAN.
The permissible values must be extended to 1-200,000,000."
REFERENCE REFERENCE
"IEEE 802.1D-1990: Section 4.5.5.3" " IEEE 802.1t clause 8.10.2, Table 8-5."
::= { dot1dStpPortEntry 5 } ::= { dot1dStpPortEntry 5 }
dot1dStpPortDesignatedRoot OBJECT-TYPE dot1dStpPortDesignatedRoot OBJECT-TYPE
SYNTAX BridgeId SYNTAX BridgeId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unique Bridge Identifier of the Bridge "The unique Bridge Identifier of the Bridge
recorded as the Root in the Configuration BPDUs recorded as the Root in the Configuration BPDUs
transmitted by the Designated Bridge for the transmitted by the Designated Bridge for the
skipping to change at page 30, line 4 skipping to change at page 27, line 30
removes the corresponding entry. removes the corresponding entry.
permanent(3) - this entry is currently in use and permanent(3) - this entry is currently in use and
will remain so after the next reset of the will remain so after the next reset of the
bridge. bridge.
deleteOnReset(4) - this entry is currently in use deleteOnReset(4) - this entry is currently in use
and will remain so until the next reset of the and will remain so until the next reset of the
bridge. bridge.
deleteOnTimeout(5) - this entry is currently in use deleteOnTimeout(5) - this entry is currently in use
and will remain so until it is aged out." and will remain so until it is aged out."
::= { dot1dStaticEntry 4 } ::= { dot1dStaticEntry 4 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Traps for use by Bridges -- Notifications for use by Bridges
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Traps for the Spanning Tree Protocol -- Notifications for the Spanning Tree Protocol
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
newRoot NOTIFICATION-TYPE newRoot NOTIFICATION-TYPE
-- OBJECTS { } -- OBJECTS { }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The newRoot trap indicates that the sending agent has "The newRoot trap indicates that the sending agent has
become the new root of the Spanning Tree; the trap is become the new root of the Spanning Tree; the trap is
sent by a bridge soon after its election as the new sent by a bridge soon after its election as the new
root, e.g., upon expiration of the Topology Change Timer root, e.g., upon expiration of the Topology Change Timer
immediately subsequent to its election. Implementation immediately subsequent to its election. Implementation
of this trap is optional." of this trap is optional."
::= { dot1dBridge 0 1 } ::= { dot1dNotification 1 }
topologyChange NOTIFICATION-TYPE topologyChange NOTIFICATION-TYPE
-- OBJECTS { } -- OBJECTS { }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A topologyChange trap is sent by a bridge when any of "A topologyChange trap is sent by a bridge when any of
its configured ports transitions from the Learning state its configured ports transitions from the Learning state
to the Forwarding state, or from the Forwarding state to to the Forwarding state, or from the Forwarding state to
the Blocking state. The trap is not sent if a newRoot the Blocking state. The trap is not sent if a newRoot
trap is sent for the same transition. Implementation of trap is sent for the same transition. Implementation of
this trap is optional." this trap is optional."
::= { dot1dBridge 0 2 } ::= { dot1dNotification 2 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- IEEE 802.1D MIB - Conformance Information -- IEEE 802.1D MIB - Conformance Information
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 }
dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- units of conformance -- units of conformance
skipping to change at page 33, line 21 skipping to change at page 30, line 36
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Static Filtering Database information for each port of "Static Filtering Database information for each port of
the Bridge." the Bridge."
::= { dot1dGroups 8 } ::= { dot1dGroups 8 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- The Trap Notfication Group -- The Trap Notfication Group
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dTrapGroup NOTIFICATION-GROUP dot1dNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
newRoot, newRoot,
topologyChange topologyChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects describing notifications (traps)." "Group of objects describing notifications (traps)."
::= { dot1dGroups 9 } ::= { dot1dGroups 9 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
skipping to change at page 34, line 32 skipping to change at page 31, line 43
DESCRIPTION DESCRIPTION
"Implementation of this group is mandatory for "Implementation of this group is mandatory for
bridges that support the transparent bridging bridges that support the transparent bridging
mode. A transparent or SRT bridge will implement mode. A transparent or SRT bridge will implement
this group." this group."
GROUP dot1dStaticGroup GROUP dot1dStaticGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional." "Implementation of this group is optional."
GROUP dot1dNotificationGroup
DESCRIPTION
"Implementation of this group is optional."
::= { dot1dCompliances 1 } ::= { dot1dCompliances 1 }
END END
4. Security Considerations 4. 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
skipping to change at page 37, line 42 skipping to change at page 34, line 23
The following changes have been made from RFC 1493. The following changes have been made from RFC 1493.
(1) Translated the MIB definition to use SMIv2. (1) Translated the MIB definition to use SMIv2.
(2) Updated the SNMP Framework and references to comply with the (2) Updated the SNMP Framework and references to comply with the
current IETF guidelines. current IETF guidelines.
(3) Updated the Security section to comply with current IETF (3) Updated the Security section to comply with current IETF
guidelines. guidelines.
The following chnages have been made from
draft-ietf-bridge-bridgemib-smiv2-00.txt
(1) Misc. description refernces to IEEE 802.1d documents
(2) dot1dNotificationGroup changed from dot1dTrapGroup
(3) Misc. additions to some descriptions
8. Authors' Addresses 8. Authors' Addresses
Les Bell K.C. Norseth
3Com Europe Limited Enterasys Networks
3Com Centre, Boundary Way 2691 S. Decker Lake Lane
Hemel Hempstead Salt Lake City, Utah 84119
Herts. HP2 7YU Phone: +1 801 887 9823
UK Email: knorseth@enterasys.com
Phone: +44 1442 438025
EMail: Les_Bell@3Com.com
9. Full Copyright 9. Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
skipping to change at page 39, line 7 skipping to change at page 35, line 18
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents Table of Contents
1 The SNMP Management Framework ................................ 3 1 The SNMP Management Framework ................................ 2
2 Overview ..................................................... 4 2 Overview ..................................................... 3
2.1 Structure of MIB ........................................... 4 2.1 Structure of MIB ........................................... 3
2.1.1 The dot1dBase Group ...................................... 6 2.1.1 The dot1dBase Group ...................................... 5
2.1.2 The dot1dStp Group ....................................... 6 2.1.2 The dot1dStp Group ....................................... 5
2.1.3 The dot1dSr Group ........................................ 7 2.1.3 The dot1dSr Group ........................................ 6
2.1.4 The dot1dTp Group ........................................ 7 2.1.4 The dot1dTp Group ........................................ 6
2.1.5 The dot1dStatic Group .................................... 7 2.1.5 The dot1dStatic Group .................................... 6
2.2 Relationship to Other MIBs ................................. 7 2.2 Relationship to Other MIBs ................................. 6
2.2.1 Relationship to the 'system' group ....................... 7 2.2.1 Relationship to the 'system' group ....................... 6
2.2.2 Relationship to the 'interfaces' group ................... 7 2.2.2 Relationship to the 'interfaces' group ................... 6
2.3 Textual Conventions ........................................ 8 2.3 Textual Conventions ........................................ 7
3 Definitions .................................................. 9 3 Definitions .................................................. 7
4 Security Considerations ...................................... 35 4 Security Considerations ...................................... 32
5 Acknowledgments .............................................. 35 5 Acknowledgments .............................................. 32
6 References ................................................... 36 6 References ................................................... 33
7 Changes from RFC 1493 ........................................ 37 7 Changes from RFC 1493 and Previous Drafts .................... 34
8 Authors' Addresses ........................................... 37 8 Authors' Addresses ........................................... 34
9 Full Copyright ............................................... 38 9 Full Copyright ............................................... 34
 End of changes. 

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