Internet Draft malhotra-mstpmib-01.txt Sumeshwar Malhotra Bhaskar S Anand Goenka Motorola, Inc Oct 2004 Definitions of Managed Objects for Bridges with Multiple Spanning Tree Protocol Status of this Memo This document is an Internet-Draft and is subject to all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines a MIB module for managing the Multiple Spanning Tree capability defined by the IEEE Std 802.1s amendment to IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) segments. This memo gives a MIB module for managing the MSTP protocol in a manner that is compliant to SMIv2 [RFC2578]. Sumeshwar, et. al. [Page 1] Internet Draft Bridge MIB extensions 2 Oct 2004 Table of Contents 1 The SNMP Management Framework ................................ 3 2 Overview ..................................................... 4 2.1 Scope ...................................................... 4 3 Structure of MSTP-MIB......................................... 4 4 Relation to Original Bridge MIB............................... 5 5 Definition for MSTP-MIB ...................................... 5 6 Acknowledgments .............................................. 20 7 Security consideration ....................................... 21 8 References ................................................... 21 9 Authors' Addresses ........................................... 22 10 Full Copyright .............................................. 22 Sumeshwar, et. al. [Page 2] Internet Draft MSTP MIB Oct 2004 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine Sumeshwar, et. al. [Page 3] Internet Draft MSTP MIB Oct 2004 readable information is not considered to change the semantics of the MIB. 2. Overview A common device present in many networks is the Bridge. This device is used to connect Local Area Network segments below the network layer. These devices are often known as 'layer 2 switches'. There are two major modes defined for this bridging: Source-Route and transparent. Management of Source-Route bridging is not discussed in this document. MSTP is defined by IEEE 802.1s. MST is defined as one or more logical topologies on a common physical interface. Typically one or more VLANs are mapped to a logical topology. 2.1. Scope This MIB includes a comprehensive set of managed objects which attempts to match the set defined in IEEE 802.1s. 3. Structure of MSTP-MIB MSTP-MIB Name IEEE 802.1s Name/Purpose dot1sStp Name MSTP Name Revision MSTP Revision Enable For enabling/disabling MSTP BridgeMaxAge Bridge Max Age BridgeHelloTime Bridge Hello Time BridgeForwardDelay Bridge Forward Delay TxHoldCount Transmit Hold Count ProtocolSpecification Protocol Specification InstTable InstId MSTP Instance Id Priority Bridge Priority InstTimeSinceTopologyChange Time since Topology Change InstTopChanges Number of Topology Changes InstDesignatedRoot Root Bridge InstRootCost Root Path Cost InstRootPort Root Port InstMaxAge Max Age InstHelloTime Hello Time InstForwardDelay Forward Delay InstAdminEnable For administratively enabling/disabling an MST Instance InstOperEnable To know the operational status of MSTI PortTable Port Port Id Sumeshwar, et. al. [Page 4] Internet Draft MSTP MIB Oct 2004 PortAdminEdgePort Admin Edge Port PortAdminPointToPoint Admin Point-To-Point PortOperEdgePort Oper Edge Port PortOperPointToPoint Oper Point-To-Point Version Version InstPortTable InstPortPriority Port Priority InstPortState Port State InstPortPathCost Port Path Cost InstPortDesignatedRoot Root Bridge InstPortDesignatedCost Root Path Cost InstPortDesignatedBridge Designated Bridge InstPortDesignatedPort Designated Port InstPortForwardTransitions Number of forward transitions InstPortRole Port Role VlanTable VlanMstIndex MSTI Index VlanRangeIndex VLAN entry index VlanMin Lower value in the VLAN range VlanMax Higher value in the VLAN range VlanRowStatus Status of this VLAN entry 4. Relation to Original Bridge MIB The interpretation of all the existing groups in the original Bridge MIB [BRIDGEMIB] remains unchanged. In addition to the objects in the original Bridge MIB [BRIDGEMIB], this document adds dot1sStp group with the following OID to manage the Multiple Spanning Tree Protocol: dot1sStp 7 5. Definitions for MSTP-MIB -- ------------------------------------------------------------- -- MIB for IEEE 802.1s Multiple Spanning Tree Protocol -- ------------------------------------------------------------- MSTP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32 FROM SNMPv2-SMI TruthValue, RowStatus, DisplayString FROM SNMPv2-TC TimeTicks FROM RFC1155-SMI BridgeId, Timeout FROM BRIDGE-MIB; Sumeshwar, et. al. [Page 5] Internet Draft MSTP MIB Oct 2004 dot1sStp MODULE-IDENTITY LAST-UPDATED "20041250000Z" 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 Multiple Spanning Tree Protocol defined by IEEE 802.1s." REVISION "20041250000Z " DESCRIPTION "Draft 1" ::= { dot1dBridge 7 } dot1sStpName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The configuration name that identifies the MST region and is used as one of the inputs in the computation of the MST Configuration Identifier. This object does not have any default value." REFERENCE "IEEE 802.1s clause 13.7" ::= { dot1sStp 1 } dot1sStpRevision OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "This object identifies the MST revision that identifies the MST region and is used as one of the inputs in the computation of the MST configuration Identifier. This object does not have any default value." REFERENCE "IEEE 802.1s: Section 13.7" ::= { dot1sStp 2 } dot1sStpEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This parameter is used for enabling or disabling MST globally on all the bridging ports." Sumeshwar, et. al. [Page 6] Internet Draft MSTP MIB Oct 2004 REFERENCE "IEEE 802.1s" DEFVAL { 2 } ::= { dot1sStp 3 } dot1sStpBridgeMaxAge OBJECT-TYPE SYNTAX Timeout (600..4000) MAX-ACCESS read-write STATUS current DESCRIPTION "The value that all bridges use for MaxAge when this bridge is acting as the root. This parameter is applicable for all MST Instances including CIST." REFERENCE "IEEE 802.1s: Section 13.23.4, 13.23.10" DEFVAL { 2000 } ::= { dot1sStp 4 } dot1sStpBridgeHelloTime OBJECT-TYPE SYNTAX Timeout (100..1000) MAX-ACCESS read-write STATUS current DESCRIPTION "The value that all bridges use for HelloTime when this bridge is acting as the root. This parameter is applicable for all MST Instances including CIST." REFERENCE "IEEE 802.1s: Section 13.23.4, 13.23.10" DEFVAL { 200 } ::= { dot1sStp 5 } dot1sStpBridgeForwardDelay OBJECT-TYPE SYNTAX Timeout (4..30) MAX-ACCESS read-write STATUS current DESCRIPTION "The value that all bridges use for ForwardDelay when this bridge is acting as the root. This parameter is applicable for all MST Instances including CIST." REFERENCE "IEEE 802.1s: Section 13.23.4, 13.23.10" DEFVAL { 1500 } ::= { dot1sStp 6 } dot1sStpTxHoldCount OBJECT-TYPE SYNTAX Integer32 (1..15) MAX-ACCESS read-only STATUS current DESCRIPTION "The value used by the Port Transmit state machine to limit the maximum transmission rate of MST BPDUs within the hello interval." Sumeshwar, et. al. [Page 7] Internet Draft MSTP MIB Oct 2004 REFERENCE "IEEE 802.1s: Section 13.22" DEFVAL { 3 } ::= { dot1sStp 7 } dot1sStpProtocolSpecification OBJECT-TYPE SYNTAX INTEGER { unknown(1), decLb100(2), ieee8021d(3), ieee8021w(4), ieee8021s(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of what version of the Spanning Tree Protocol is being run. The value 'decLb100(2)' indicates the DEC LANbridge 100 Spanning Tree protocol. IEEE 802.1w implementations will return 'ieee8021w(4)'. IEEE 802.1s implementations will return 'ieee8021s(5). If future versions of the IEEE Spanning Tree Protocol are released that are incompatible with the current version a new value will be defined." REFERENCE "IEEE 802.1s: Section 13.22" DEFVAL { 5 } ::= { dot1sStp 8 } dot1sStpInstTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1sStpInstEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains MST instance-specific configuration and operational information." ::= { dot1sStp 9 } dot1sStpInstEntry OBJECT-TYPE SYNTAX Dot1sStpInstEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of information maintained by every mst instance about the STP topology for that instance." INDEX { dot1sStpInstId } ::= { dot1sStpInstTable 1 } Sumeshwar, et. al. [Page 8] Internet Draft MSTP MIB Oct 2004 Dot1sStpInstEntry ::= SEQUENCE { dot1sStpInstId Integer32, dot1sStpPriority Integer32, dot1sStpInstTimeSinceTopologyChange TimeTicks, dot1sStpInstTopChanges Counter32, dot1sStpInstDesignatedRoot BridgeId, dot1sStpInstRootCost Integer32, dot1sStpInstRootPort Integer32, dot1sStpInstMaxAge Timeout, dot1sStpInstHelloTime Timeout, dot1sStpInstForwardDelay Timeout, dot1sStpInstAdminEnable TruthValue, dot1sStpInstOperEnable TruthValue } dot1sStpInstId OBJECT-TYPE SYNTAX Integer32 (1..64) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifier of this MST Instance" REFERENCE "IEEE 802.1s" ::= { dot1sStpInstEntry 1 } dot1sStpPriority OBJECT-TYPE SYNTAX Integer32 (0..61440) MAX-ACCESS read-write STATUS current DESCRIPTION "The value of the write-able portion of the Bridge ID, i.e., the first two octets, out of which the priority is the most significant 4 bits of the first octet of the (8 octet long) Bridge ID. The other (last) 6 octets of the Bridge ID are given by the value of dot1dBaseBridgeAddress in the BRIDGE-MIB. The value of this object should always be a multiple of 4096. Sumeshwar, et. al. [Page 9] Internet Draft MSTP MIB Oct 2004 REFERENCE "IEEE 802.1s: Section 13.23.2" DEFVAL { 32768 } ::= { dot1sStpInstEntry 2 } dot1sStpInstTimeSinceTopologyChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity running MSTP." REFERENCE " IEEE 802.1D-1990: Section 6.8.1.1.3" ::= { dot1sStpInstEntry 3 } dot1sStpInstTopChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of topology changes detected by this bridge entity running MST since the management entity was last reset or initialized." REFERENCE " IEEE 802.1D-1990: Section 6.8.1.1.3" ::= { dot1sStpInstEntry 4 } dot1sStpInstDesignatedRoot OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "The bridge identifier of the root of the corresponding spanning tree instance as determined by the Spanning Tree Protocol for that instance. This value is used as the CIST Root Identifier or MSTI regional root identifier parameter in all MST BPDUs originated by this node." REFERENCE "IEEE 802.1s: Section 13.23.6, 13.23.12" ::= { dot1sStpInstEntry 5 } dot1sStpInstRootCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The cost of the path to the root as seen from this bridge for this instance." Sumeshwar, et. al. [Page 10] Internet Draft MSTP MIB Oct 2004 REFERENCE "IEEE 802.1s: Section 13.23.6, 13.23.12" ::= { dot1sStpInstEntry 6 } dot1sStpInstRootPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The port number of the port which offers the lowest cost path from this bridge to the root bridge for this instance." REFERENCE "IEEE 802.1s: Section 13.23.6, 13.23.12" ::= { dot1sStpInstEntry 7 } dot1sStpInstMaxAge OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value, which is advertised by the Root bridge and is currently used for this MST Instance." REFERENCE "IEEE 802.1s: Section 13.23.7, 13.23.13" ::= { dot1sStpInstEntry 8 } dot1sStpInstHelloTime OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current DESCRIPTION "The period of time between the transmission of MST BPDUs by this node on any port when it is the root of the spanning tree or trying to become so, in units of hundredths of a second. This is the actual value, which is advertised by the Root bridge and is currently used for this MST Instance." REFERENCE "IEEE 802.1s: Section 13.23.7, 13.23.13" ::= { dot1sStpInstEntry 9 } dot1sStpInstForwardDelay OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current Sumeshwar, et. al. [Page 11] Internet Draft MSTP MIB Oct 2004 DESCRIPTION "This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Discarding and Learning states, which precede the Forwarding state. This value is also used, when a topology change has been detected and is underway, to age all dynamic entries in the Forwarding Database. [Note that this value is the one that this bridge is currently using, in contrast to dot1sStpBridgeForwardDelay which is the value that this bridge and all others would start using if/when this bridge were to become the root.]" REFERENCE "IEEE 802.1s: Section 13.23.7, 13.23.13" ::= { dot1sStpInstEntry 10 } dot1sStpInstAdminEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative enabled/disabled status of the instance" REFERENCE "IEEE 802.1s" DEFVAL { 2 } ::= { dot1sStpInstEntry 11 } dot1sStpInstOperEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The operational enabled/disabled status of the instance. An MST Instance may be administratively enabled but may not be operationally running, for example, when no VLAN is mapped to that MST Instance." REFERENCE "IEEE 802.1s" DEFVAL { 2 } ::= { dot1sStpInstEntry 12 } Sumeshwar, et. al. [Page 12] Internet Draft MSTP MIB Oct 2004 dot1sStpPortTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1sStpPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains MSTP ports' information." ::= { dot1sStp 9 } dot1sStpPortEntry OBJECT-TYPE SYNTAX Dot1sStpPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of information maintained by every MST port about the Spanning Tree Protocol state for that port." INDEX { dot1sStpPort } ::= { dot1sStpPortTable 1 } Dot1sStpPortEntry ::= SEQUENCE { dot1sStpPort Integer32, dot1sStpPortAdminEdgePort TruthValue, dot1sStpPortAdminPointToPoint INTEGER, dot1sStpPortOperEdgePort TruthValue, dot1sStpPortOperPointToPoint TruthValue, dot1sStpVersion INTEGER } dot1sStpPort OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The port number of the port for which this entry contains Spanning Tree Protocol management information." REFERENCE " IEEE 802.1s: Section 13.24.21" ::= { dot1sStpPortEntry 1 } dot1sStpPortAdminEdgePort OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current Sumeshwar, et. al. [Page 13] Internet Draft MSTP MIB Oct 2004 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." REFERENCE "IEEE 802.1s: Section 12.8.2.1.3" ::= { dot1sStpPortEntry 2 } dot1sStpPortAdminPointToPoint OBJECT-TYPE SYNTAX INTEGER { forceTrue(1), forceFalse(2), auto(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative point-to-point status of the LAN segment attached to this port. A value of forceTrue(1) indicates that this port should always be treated as if it is connected to a point-to-point link. A value of forceFalse(2) indicates that this port should be treated as having a shared media connection. A value of auto(3) 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." REFERENCE "IEEE 802.1s: Section 13.18" ::= { dot1sStpPortEntry 3 } dot1sStpPortOperEdgePort OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The operational 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." REFERENCE "IEEE 802.1s: Section 12.8.2.1.3" ::= { dot1sStpPortEntry 4 } dot1sStpPortOperPointToPoint OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current Sumeshwar, et. al. [Page 14] Internet Draft MSTP MIB Oct 2004 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 or not. The value is determined by management or by auto-detection, as described in the dot1dStpPortAdminPointToPoint object." REFERENCE "IEEE 802.1s: Section 13.18" ::= { dot1sStpPortEntry 5 } dot1sStpVersion OBJECT-TYPE SYNTAX INTEGER { stpCompatible(0), rstp-mstp(2) } MAX-ACCESS read-only 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 and 'rstp/mstp(2)' indicates the Rapid Spanning Tree Protocol specified in IEEE 802.1w and Multiple Spanning Tree Protocol specified in IEEE 802.1s. New value may be defined as future versions of the protocol become available." REFERENCE "IEEE 802.1s: Section 14.2" DEFVAL { rstp-mstp } ::= { dot1sStpPortEntry 6 } dot1sStpInstPortTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1sStpInstPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains MST port and instance information." ::= { dot1sStp 10 } dot1sStpInstPortEntry OBJECT-TYPE SYNTAX Dot1sStpInstPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of information maintained by every MST port for each MST instance it belongs to about the Spanning Tree Protocol state for that port." INDEX { dot1sStpInstId, dot1sStpPort } ::= { dot1sStpInstPortTable 1 } Sumeshwar, et. al. [Page 15] Internet Draft MSTP MIB Oct 2004 Dot1sStpInstPortEntry ::= SEQUENCE { dot1sStpInstPortPriority Integer32, dot1sStpInstPortState INTEGER, dot1sStpInstPortPathCost Integer32, dot1sStpInstPortDesignatedRoot BridgeId, dot1sStpInstPortDesignatedCost Integer32, dot1sStpInstPortDesignatedBridge BridgeId, dot1sStpInstPortDesignatedPort OCTET STRING, dot1sStpInstPortForwardTransitions Counter32, dot1sStpInstPortRole INTEGER } dot1sStpInstPortPriority OBJECT-TYPE SYNTAX Integer32 (0..240) MAX-ACCESS read-write STATUS current DESCRIPTION "The value of the priority field which is contained in the most significant 4 bits of the first (in network byte order) octet of the (2 octet long) Port ID. As it is contained only in 4 bits, the value has to be a multiple of 16. The other octet of the Port ID is given by the value of dot1dStpPort." REFERENCE "IEEE 802.1s: Section 13.24.21" ::= { dot1sStpInstPortEntry 1 } dot1sStpInstPortState OBJECT-TYPE SYNTAX INTEGER { disabled(1), discarding(2), learning(3), forwarding(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The port's current state as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on Sumeshwar, et. al. [Page 16] Internet Draft MSTP MIB Oct 2004 reception of a frame. For ports which are disabled (see dot1dStpPortEnable), this object will have a value of disabled(1)." REFERENCE "IEEE 802.1s: Section 13.16" ::= { dot1sStpInstPortEntry 2 } dot1sStpInstPortPathCost OBJECT-TYPE SYNTAX Integer32 (1..200000000) MAX-ACCESS read-write STATUS current DESCRIPTION "The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1990 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN." REFERENCE "IEEE 802.1s: Section 13.24.8, 13.24.17" ::= { dot1sStpInstPortEntry 3 } dot1sStpInstPortDesignatedRoot OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached." REFERENCE "IEEE 802.1s: Section 13.24.4, 13.24.11" ::= { dot1sStpInstPortEntry 4 } dot1sStpInstPortDesignatedCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs." REFERENCE "IEEE 802.1s: Section 13.24.4, 13.24.11" ::= { dot1sStpInstPortEntry 5 } Sumeshwar, et. al. [Page 17] Internet Draft MSTP MIB Oct 2004 dot1sStpInstPortDesignatedBridge OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "The Bridge Identifier of the bridge which this port considers to be the Designated Bridge for this port's segment." REFERENCE "IEEE 802.1s: Section 13.24.4, 13.24.11" ::= { dot1sStpInstPortEntry 6 } dot1sStpInstPortDesignatedPort OBJECT-TYPE SYNTAX OCTET STRING (SIZE (2)) MAX-ACCESS read-only STATUS current DESCRIPTION "The Port Identifier of the port on the Designated Bridge for this port's segment." REFERENCE "IEEE 802.1s: Section 13.24.4, 13.24.11" ::= { dot1sStpInstPortEntry 7 } dot1sStpInstPortForwardTransitions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times this port has transitioned from the Learning state to the Forwarding state." REFERENCE "IEEE 802.1s" ::= { dot1sStpInstPortEntry 8 } dot1sStpInstPortRole OBJECT-TYPE SYNTAX INTEGER { master(0), alternate-backup(1), root(2), designated(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The role of the port. As per IEEE 802.1s, the port can have any of the following roles: Disabled, Root, Designated, Alternate, Backup, Master" REFERENCE "IEEE 802.1s: Section 13.24.25" ::= { dot1sStpInstPortEntry 9 } Sumeshwar, et. al. [Page 18] Internet Draft MSTP MIB Oct 2004 dot1sStpVlanTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1sStpVlanEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains MSTI-VLAN mapping." ::= { dot1sStp 11 } dot1sStpVlanEntry OBJECT-TYPE SYNTAX Dot1sStpVlanEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of information maintained by every MST instance about the VLANs mapped to that instance." INDEX { dot1sStpVlanMstIndex, dot1sStpVlanRangeIndex } ::= { dot1sStpVlanTable 1 } Dot1sStpVlanEntry ::= SEQUENCE { dot1sStpVlanMstIndex Integer32, dot1sStpVlanRangeIndex Integer32, dot1sStpVlanMin Integer32, dot1sStpVlanMax Integer32, dot1sStpVlanRowStatus RowStatus } dot1sStpVlanMstIndex OBJECT-TYPE SYNTAX Integer32 (2..8) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the primary index to the MST-VLAN table and is derived from the MST Instance id by incrementing by 1." REFERENCE "IEEE 802.1s" ::= { dot1sStpVlanEntry 1 } dot1sStpVlanRangeIndex OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS read-only STATUS current Sumeshwar, et. al. [Page 19] Internet Draft MSTP MIB Oct 2004 DESCRIPTION "This is the secondary index to the MSTI-VLAN Table. It signifies the index to the VLAN range entry in the table." REFERENCE "IEEE 802.1s" ::= { dot1sStpVlanEntry 2 } dot1sStpVlanMin OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS read-write STATUS current DESCRIPTION "The lower value in the VLAN range mapped to the MST Instance." REFERENCE "IEEE 802.1s" ::= { dot1sStpVlanEntry 3 } dot1sStpVlanMax OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS read-write STATUS current DESCRIPTION "The higher value in the VLAN range mapped to the MST Instance." REFERENCE "IEEE 802.1s" ::= { dot1sStpVlanEntry 4 } dot1sStpVlanRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of the row as per SNMP-v2." REFERENCE "IEEE 802.1s" ::= { dot1sStpVlanEntry 5 } END 5. Acknowledgments This document was produced on behalf of the Bridge MIB Working Group in the Operations and Management area of the Internet Engineering Task Force. The authors wish to thank the members of the BSR Project especially Phanibhushan Rao Gandeed, whose valuable suggestions helped to improve the draft. Sumeshwar, et. al. [Page 20] Internet Draft MSTP MIB Oct 2004 The authors also wish to thank the Motorola Broadband Communications Sector, especially Mike Patrick and Will Murwin for their valuable comments and suggestions. 6. Security Considerations Security Issues are not discussed in this memo. 7. References [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for Describing SNMP Management Frameworks, RFC 2571, April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Structure of Management Information Version 2 (SMIv2), STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, STD 58, RFC 2579, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC 1905, January 1996. [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie, "Definitions of Managed Objects for Bridges", RFC 1493, July 1993. [802.1d] IEEE 802.1d-1998, "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". [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.1s] IEEE 802.1s-2002, "(Amendment to IEEE Standard 802.1Q) IEEE Standard for Local and metropolitan area networks-Virtual Bridged Local Area Networks-Amendment 3: Multiple Spanning Trees. Sumeshwar, et. al. [Page 21] Internet Draft MSTP MIB Oct 2004 8. Authors' Addresses Sumeshwar Malhotra Motorola India Electronics Pvt. Ltd. No. 66/1, Plot No 5, Bagmane Techpark C V Raman Nagar Post Bangalore 560 093 India Phone: +91 80 26014098 Email: Sumeshwar.Malhotra@motorola.com Bhaskar S Motorola India Electronics Pvt. Ltd. No. 66/1, Plot No 5, Bagmane Techpark C V Raman Nagar Post Bangalore 560 093 India Phone: +91 80 26014089 Email: bhaskar.s@motorola.com Anand Goenka Motorola India Electronics Pvt. Ltd. No. 66/1, Plot No 5, Bagmane Techpark C V Raman Nagar Post Bangalore 560 093 India Phone: +91 80 26014110 Email: Anand.Kumar.Goenka@motorola.com 9. Full Copyright Copyright (C) The Internet Society (date). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. Sumeshwar, et. al. [Page 22] Internet Draft MSTP MIB Oct 2004 The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. Sumeshwar, et. al. [Page 23]