idnits 2.17.1 draft-ietf-trill-rbridge-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 31, 2012) is 4255 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC4001' is mentioned on line 330, but not defined Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TRILL Working Group A. Rijhsinghani 3 Internet-Draft Hewlett-Packard 4 Intended status: Proposed Standard K. Zebrose 5 Expires: March 4, 2013 H.W. Embedded 6 August 31, 2012 8 Definitions of Managed Objects for RBridges (Routing Bridges) 9 draft-ietf-trill-rbridge-mib-08.txt 11 Status of This Document 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 This document is intended to become a Proposed Standard. Distribution 17 of this document is unlimited. Comments should be sent to the author. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols. In particular it defines 39 objects for managing an RBridge (Routing Bridge), also known as a 40 TRILL Switch, based on the IETF TRILL (Transparent Interconnection of 41 Lots of Links) protocol. 43 Table of Contents 45 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 2. The Internet-Standard Management Framework . . . . . . . . . . . 3 47 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 49 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 4 50 5.1 Textual Conventions . . . . . . . . . . . . . . . . . . . . 4 51 5.2 The rbridgeBase Subtree . . . . . . . . . . . . . . . . . . 4 52 5.3 The rbridgeFdb Subtree . . . . . . . . . . . . . . . . . . . 4 53 5.4 The rbridgeVlan subtree . . . . . . . . . . . . . . . . . . 4 54 5.5 The rbridgeEsadi subtree . . . . . . . . . . . . . . . . . . 5 55 5.6 The rbridgeCounters subtree . . . . . . . . . . . . . . . . 5 56 5.7 The rbridgeSnooping subtree . . . . . . . . . . . . . . . . 5 57 5.8 The rbridgeDtree subtree . . . . . . . . . . . . . . . . . . 5 58 5.9 The rbridgeTrill subtree . . . . . . . . . . . . . . . . . . 5 59 5.10 The Notifications Subtree . . . . . . . . . . . . . . . . . 5 60 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . . 5 61 6.1 Relationship to IF-MIB . . . . . . . . . . . . . . . . . . . 6 62 6.2 Relationship to BRIDGE-MIB . . . . . . . . . . . . . . . . . 6 63 6.3 Relationship to P-BRIDGE-MIB . . . . . . . . . . . . . . . . 6 64 6.4 Relationship to Q-BRIDGE-MIB . . . . . . . . . . . . . . . . 6 65 6.5 Relationship to IEEE8021-BRIDGE-MIB . . . . . . . . . . . . 7 66 6.7 Relationship to ISIS-MIB . . . . . . . . . . . . . . . . . . 7 67 6.8 MIB modules required for IMPORTS . . . . . . . . . . . . . 8 68 7. Definition of the RBridge MIB module . . . . . . . . . . . . . . 8 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 48 70 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 71 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 50 72 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 50 73 11.1 Normative References . . . . . . . . . . . . . . . . . . 50 74 11.2 Informative References . . . . . . . . . . . . . . . . . 51 75 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 51 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 77 Copyright and License Notice . . . . . . . . . . . . . . . . . . 53 79 1. Introduction 81 This document describes a model for managing RBridges (Routing 82 Bridges), also known as TRILL Switches, as defined in [RFC6325]. 83 RBridges provide optimal pair-wise forwarding without configuration 84 using IS-IS routing and encapsulation of traffic. RBridges are 85 compatible with previous IEEE 802.1 customer bridges as well as IPv4 86 and IPv6 routers and end nodes. They are as invisible to current IP 87 routers as bridges are and, like routers, they terminate the bridge 88 spanning tree protocol. In creating an RBridge management model the 89 device is viewed primarily as a customer bridge. For a discussion of 90 the problem addressed by TRILL (Transparent Interconnection of Lots 91 of Links) see [RFC5556]. 93 RBridges support features specified for transparent bridges in IEEE 94 802.1, and the corresponding MIB modules are used to manage those 95 features. For IS-IS purposes, the corresponding MIB module is used to 96 manage the protocol. This MIB module specifies those objects which 97 are TRILL-specific and hence not available in other MIB modules. 99 2. The Internet-Standard Management Framework 101 For a detailed overview of the documents that describe the current 102 Internet-Standard Management Framework, please refer to section 7 of 103 RFC 3410 [RFC3410]. 105 Managed objects are accessed via a virtual information store, termed 106 the Management Information Base or MIB. MIB objects are generally 107 accessed through the Simple Network Management Protocol (SNMP). 108 Objects in the MIB are defined using the mechanisms defined in the 109 Structure of Management Information (SMI). This memo specifies a MIB 110 module that is compliant to the SMIv2, which is described in STD 58, 111 which consists of [RFC2578], [RFC2579] and [RFC2580]. 113 3. Overview 115 The RBridge MIB module is intended as an overall framework for 116 managing RBridges, also known as TRILL Switches. Where possible the 117 MIB references existing MIB definitions in order to maximize reuse. 118 This results in a considerable emphasis on the relationship with 119 other MIB modules. 121 Starting with the physical interfaces, there are requirements for 122 certain elements of the IF-MIB to be implemented. These elements are 123 required in order to connect the per-port parameters to higher level 124 functions of the physical device. 126 Transparent bridging, VLANs, Traffic classes and Multicast Filtering 127 are supported by the TRILL protocol, and the corresponding management 128 is expected to conform to the BRIDGE-MIB [RFC4188], P-BRIDGE-MIB and 129 Q-BRIDGE-MIB [RFC4363] modules. 131 The IS-IS routing protocol is used in order to determine the optimum 132 pair-wise forwarding path. This protocol is managed using the IS-IS 133 MIB module defined in [RFC4444]. Since the TRILL protocol specifies 134 use of a single level and a fixed area address of zero, some IS-IS 135 MIB objects are not applicable. Some IS-IS MIB objects are used in 136 the TRILL protocol. 138 4. Conventions 140 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 141 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 142 "OPTIONAL" in this document are to be interpreted as described in RFC 143 2119 [RFC2119]. 145 5. Structure of the MIB Module 147 Objects in this MIB module are arranged into subtrees. Each subtree 148 is organized as a set of related objects. The various subtrees are 149 shown below. These are supplemented with required elements of the IF- 150 MIB, ISIS-MIB, BRIDGE-MIB, P-BRIDGE-MIB, Q-BRIDGE-MIB and IEEE Bridge 151 MIB modules. 153 5.1 Textual Conventions 155 Textual conventions are defined to represent object types relevant to 156 TRILL. 158 5.2 The rbridgeBase Subtree 160 This subtree contains system and port specific objects applicable to 161 all RBridges. 163 5.3 The rbridgeFdb Subtree 165 This subtree contains objects applicable to the Forwarding database 166 used by the RBridge in making packet forwarding decisions. Because it 167 contains additional information used by the TRILL protocol not 168 applicable to 802.1D/Q bridges, it is a superset of the corresponding 169 subtrees defined in the BRIDGE-MIB and Q-BRIDGE-MIB. 171 5.4 The rbridgeVlan subtree 173 This subtree describes objects applicable to VLANs configured on the 174 RBridge. 176 5.5 The rbridgeEsadi subtree 178 This subtree describes objects relevant to RBridges that support the 179 optional ESADI protocol. 181 5.6 The rbridgeCounters subtree 183 This subtree contains statistics maintained by RBridges that can aid 184 in monitoring and troubleshooting networks connected by them. 186 5.7 The rbridgeSnooping subtree 188 This subtree describes objects applicable to RBridges capable of 189 snooping IPv4 and/or IPv6 Multicast control frames and pruning IP 190 multicast traffic based on detection of IP multicast routers and 191 listeners. 193 5.8 The rbridgeDtree subtree 195 This subtree contains objects relevant to Distribution Trees computed 196 by RBridges for the forwarding of multi-destination frames. 198 5.9 The rbridgeTrill subtree 200 This subtree contains objects applicable to the TRILL IS-IS protocol, 201 beyond what is available in ISIS-MIB. 203 5.10 The Notifications Subtree 205 The defined notifications are focused on the TRILL protocol 206 functionality. Notifications are defined for changes in the 207 Designated RBridge status and the topology. 209 6. Relationship to Other MIB Modules 211 The IF-MIB, BRIDGE-MIB, P-BRIDGE-MIB, Q-BRIDGE-MIB, IEEE8021-BRIDGE- 212 MIB, IEEE8021-Q-BRIDGE-MIB and ISIS-MIB modules all contain objects 213 relevant to the RBridge MIB. Management objects contained in these 214 modules are not duplicated here, to reduce overlap to the extent 215 possible. 217 The Bridge MIB modules were originally written in the IETF, and 218 implemented by many vendors. Per [RFC4663], this has recently been 219 transferred to the IEEE 802.1 group. As vendors may have implemented 220 either the IETF or IEEE Bridge MIB modules, this RBridge MIB module 221 is designed to work with either one. 223 6.1 Relationship to IF-MIB 225 The port identification elements MUST be implemented in order to 226 allow them to be cross referenced. The Interface MIB [RFC2863] 227 requires that any MIB module which is an adjunct of the Interface MIB 228 clarify specific areas within the Interface MIB module. These areas 229 were intentionally left vague in the Interface MIB module to avoid 230 over-constraining the MIB, thereby precluding management of certain 231 media types. Section 4 of [RFC2863] enumerates several areas which a 232 media-specific MIB module must clarify. The implementor is referred 233 to [RFC2863] in order to understand the general intent of these 234 areas. 236 6.2 Relationship to BRIDGE-MIB 238 The following subtrees in the BRIDGE-MIB [RFC4188] contain 239 information relevant to RBridges when the corresponding functionality 240 is implemented. 242 o dot1dBase 243 o dot1dTp 244 o dot1dStatic 246 6.3 Relationship to P-BRIDGE-MIB 248 The following subtrees in the P-BRIDGE-MIB [RFC4363] contain 249 information relevant to RBridges when the corresponding functionality 250 is implemented. 252 o dot1dExtBase 253 o dot1dPriority 254 o dot1dGarp 255 o dot1dGmrp 256 o dot1dTpHCPortTable 257 o dot1dTpPortOverflowTable 259 6.4 Relationship to Q-BRIDGE-MIB 261 The following groups in the Q-BRIDGE-MIB [RFC4363] contain 262 information relevant to RBridges when the corresponding functionality 263 is implemented. This functionality is also contained in IEEE8021-Q- 264 BRIDGE-MIB. 266 o dot1qBase 267 o dot1qTp 268 o dot1qStatic 269 o dot1qVlan 270 o dot1vProtocol 272 6.5 Relationship to IEEE8021-BRIDGE-MIB 274 The following subtrees in the IEEE8021-BRIDGE-MIB contain information 275 relevant to RBridges when the corresponding functionality is 276 implemented. 278 o ieee8021BridgeBase 279 o ieee8021BridgeTp 280 o ieee8021BridgePriority 281 o ieee8021BridgeMrp 282 o ieee8021BridgeMmrp 283 o ieee8021BridgeInternalLan 284 o ieee8021BridgeDot1d 286 6.6 Relationship to IEEE8021-Q-BRIDGE-MIB 288 The following subtrees in the IEEE8021-Q-BRIDGE-MIB contain 289 information relevant to RBridges when the corresponding functionality 290 is implemented. 292 o ieee8021QBridgeBase 293 o ieee8021QBridgeTp 294 o ieee8021QBridgeStatic 295 o ieee8021QBridgeVlan 296 o ieee8021QBridgeProtocol 298 6.7 Relationship to ISIS-MIB 300 The Management Information Base for Intermediate System to 301 Intermediate System (IS-IS)[RFC4444] defines a MIB module for the IS- 302 IS Routing protocol when it is used to construct routing tables for 303 IP networks. While most of these objects are applicable to the TRILL 304 layer 2 implementation, note the IS-IS constraints for the current 305 version of TRILL [RFC6325]: 307 o The TRILL IS-IS instance uses a single Level 1 IS-IS area. 309 o The TRILL Level 1 IS-IS area uses the fixed area address zero. 311 o The TRILL IS-IS instance is not used for IP address advertisement. 313 o The TRILL IS-IS instance is used for only a single protocol: TRILL. 315 Accordingly, tables which report IP address reachability and tables 316 which allow configuration or reporting of multiple IS-IS areas, 317 multiple IS-IS levels or multiple protocols, will be empty in the 318 ISIS-MIB module for the current version of TRILL. 320 Note also that when more than one instance of the IS-IS protocol is 321 running on a device, as in the case of a device performing both 322 RBridge and IS-IS IP router functions, multiple instances of the 323 ISIS-MIB module can be distinguished by the use of SNMPv3 contexts or 324 SNMPv1 communities. 326 6.8 MIB modules required for IMPORTS 328 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 329 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and 330 INET-ADDRESS-MIB[RFC4001]. 332 7. Definition of the RBridge MIB module 334 RBRIDGE-MIB DEFINITIONS ::= BEGIN 336 -- ---------------------------------------------------------- -- 337 -- MIB for RBRIDGE devices, also known as TRILL Switches 338 -- ---------------------------------------------------------- -- 339 IMPORTS 340 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 341 Counter32, Counter64, Unsigned32, mib-2 342 FROM SNMPv2-SMI -- RFC2578 343 TEXTUAL-CONVENTION, TruthValue, MacAddress, RowStatus 344 FROM SNMPv2-TC -- RFC2579 345 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 346 FROM SNMPv2-CONF -- RFC2580 347 VlanId, PortList 348 FROM Q-BRIDGE-MIB -- RFC4363 349 InetAddress, InetAddressType 350 FROM INET-ADDRESS-MIB -- RFC4001 351 BridgeId 352 FROM BRIDGE-MIB -- RFC4188 353 InterfaceIndex 354 FROM IF-MIB -- RFC2863 355 ; 357 rbridgeMIB MODULE-IDENTITY 358 LAST-UPDATED "201201250000Z" 359 ORGANIZATION "IETF TRILL Working Group" 360 CONTACT-INFO 361 "http://www.ietf.org/dyn/wg/charter/trill-charter.html 362 Email: rbridge@postel.org 364 Anil Rijhsinghani 365 Hewlett-Packard 366 Tel: +1 508 323 1251 368 Email: anil@charter.net 370 Kate Zebrose 371 H.W. Embedded 372 Tel: +1 617 840 9673 373 Email: kate.zebrose@alum.mit.edu" 375 DESCRIPTION 376 "The RBridge MIB module for managing switches that support 377 the TRILL protocol." 379 REVISION "201201250000Z" 380 DESCRIPTION 381 "Initial version, published as RFC yyyy" 382 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 384 ::= { mib-2 xxx } 385 -- RFC Ed.: replace xxx with IANA-assigned number & remove this note 387 -- ---------------------------------------------------------- -- 388 -- subtrees in the RBridge MIB 389 -- ---------------------------------------------------------- -- 391 rbridgeNotifications OBJECT IDENTIFIER ::= { rbridgeMIB 0 } 392 rbridgeObjects OBJECT IDENTIFIER ::= { rbridgeMIB 1 } 393 rbridgeConformance OBJECT IDENTIFIER ::= { rbridgeMIB 2 } 395 rbridgeBase OBJECT IDENTIFIER ::= { rbridgeObjects 1 } 396 rbridgeFdb OBJECT IDENTIFIER ::= { rbridgeObjects 2 } 397 rbridgeVlan OBJECT IDENTIFIER ::= { rbridgeObjects 3 } 398 rbridgeEsadi OBJECT IDENTIFIER ::= { rbridgeObjects 4 } 399 rbridgeCounter OBJECT IDENTIFIER ::= { rbridgeObjects 5 } 400 rbridgeSnooping OBJECT IDENTIFIER ::= { rbridgeObjects 6 } 401 rbridgeDtree OBJECT IDENTIFIER ::= { rbridgeObjects 7 } 402 rbridgeTrill OBJECT IDENTIFIER ::= { rbridgeObjects 8 } 404 -- ---------------------------------------------------------- -- 405 -- type definitions 406 -- ---------------------------------------------------------- -- 408 RbridgeAddress ::= TEXTUAL-CONVENTION 409 DISPLAY-HINT "1x:" 410 STATUS current 411 DESCRIPTION 412 "The MAC address used by an RBridge port. This may match the 413 RBridge ISIS SystemID." 414 SYNTAX OCTET STRING (SIZE (6)) 415 RbridgeNickname ::= TEXTUAL-CONVENTION 416 DISPLAY-HINT "d" 417 STATUS current 418 DESCRIPTION 419 "The 16-bit identifier used in TRILL as an 420 abbreviation for the RBridge's 48-bit IS-IS System ID. 421 The value 0 means a nickname is not specified, the values 422 0xffco through 0xfffe are reserved for future allocation, 423 and the value 0xffff is permanently reserved." 424 REFERENCE 425 "RFC 6325 section 3.7" 426 SYNTAX Unsigned32 (0..65471) 428 -- 429 -- the rbridgeBase subtree 430 -- 431 -- Implementation of the rbridgeBase subtree is mandatory for all 432 -- RBridges. 433 -- 435 rbridgeBaseTrillVersion OBJECT-TYPE 436 SYNTAX Unsigned32 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The maximum TRILL version number that this Rbridge 441 supports." 442 REFERENCE 443 "RFC 6325 section 3.2" 444 ::= { rbridgeBase 1 } 446 rbridgeBaseNumPorts OBJECT-TYPE 447 SYNTAX Unsigned32 448 UNITS "ports" 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The number of ports controlled by this RBridge." 453 REFERENCE 454 "RFC 6325 section 2.6.1" 455 ::= { rbridgeBase 2 } 457 rbridgeBaseForwardDelay OBJECT-TYPE 458 SYNTAX Unsigned32 (4..30) 459 UNITS "seconds" 460 MAX-ACCESS read-write 461 STATUS current 462 DESCRIPTION 463 "Modified aging time for address entries after an appointed 464 forwarder change. 466 The value of this object MUST be retained across 467 reinitializations of the management system." 468 REFERENCE 469 "RFC 6325 section 4.8.3" 470 ::= { rbridgeBase 3 } 472 rbridgeBaseUniMultipathEnable OBJECT-TYPE 473 SYNTAX TruthValue 474 MAX-ACCESS read-write 475 STATUS current 476 DESCRIPTION 477 "The enabled status of unicast TRILL multipathing. 478 It is enabled when true. 480 The value of this object MUST be retained across 481 reinitializations of the management system." 482 REFERENCE 483 "RFC 6325 Appendix C" 484 ::= { rbridgeBase 4 } 486 rbridgeBaseMultiMultipathEnable OBJECT-TYPE 487 SYNTAX TruthValue 488 MAX-ACCESS read-write 489 STATUS current 490 DESCRIPTION 491 "The enabled status of multidestination TRILL multipathing. 492 It is enabled when true. 494 The value of this object MUST be retained across 495 reinitializations of the management system." 496 REFERENCE 497 "RFC 6325 Appendix C" 498 ::= { rbridgeBase 5 } 500 rbridgeBaseAcceptEncapNonadj OBJECT-TYPE 501 SYNTAX TruthValue 502 MAX-ACCESS read-write 503 STATUS current 504 DESCRIPTION 505 "Accept TRILL-encapsulated frames from a neighbor with which 506 this RBridge does not have an IS-IS adjacency. 508 The value of this object MUST be retained across 509 reinitializations of the management system." 510 REFERENCE 511 "RFC 6325 section 4.6.2" 512 ::= { rbridgeBase 6 } 514 rbridgeBaseNicknameNumber OBJECT-TYPE 515 SYNTAX Unsigned32 (1..256) 516 MAX-ACCESS read-write 517 STATUS current 518 DESCRIPTION 519 "The number of nicknames this RBridge should acquire. 520 These can be acquired dynamically or configured 521 statically. 523 The value of this object MUST be retained across 524 reinitializations of the management system." 525 REFERENCE 526 "RFC 6325 section 3.7.3" 527 ::= { rbridgeBase 7 } 529 -- ---------------------------------------------------------- -- 530 -- The RBridge Base Nickname Table 531 -- ---------------------------------------------------------- -- 533 rbridgeBaseNicknameTable OBJECT-TYPE 534 SYNTAX SEQUENCE OF RbridgeBaseNicknameEntry 535 MAX-ACCESS not-accessible 536 STATUS current 537 DESCRIPTION 538 "A table that contains information about nicknames 539 associated with this RBridge." 540 REFERENCE 541 "RFC 6325 section 3.7" 542 ::= { rbridgeBase 8 } 544 rbridgeBaseNicknameEntry OBJECT-TYPE 545 SYNTAX RbridgeBaseNicknameEntry 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "A list of information for each nickname of the RBridge." 550 REFERENCE 551 "RFC 6325 section 3.7" 552 INDEX { rbridgeBaseNicknameName } 553 ::= { rbridgeBaseNicknameTable 1 } 555 RbridgeBaseNicknameEntry ::= 556 SEQUENCE { 557 rbridgeBaseNicknameName 558 RbridgeNickname, 560 rbridgeBaseNicknamePriority 561 Unsigned32, 562 rbridgeBaseNicknameDtrPriority 563 Unsigned32, 564 rbridgeBaseNicknameType 565 INTEGER, 566 rbridgeBaseNicknameRowStatus 567 RowStatus 568 } 570 rbridgeBaseNicknameName OBJECT-TYPE 571 SYNTAX RbridgeNickname 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "Nicknames are 16-bit quantities that act as 576 abbreviations for RBridge's 48-bit IS-IS System ID to 577 achieve a more compact encoding." 578 REFERENCE 579 "RFC 6325 section 3.7" 580 ::= { rbridgeBaseNicknameEntry 1 } 582 rbridgeBaseNicknamePriority OBJECT-TYPE 583 SYNTAX Unsigned32 (0..255) 584 MAX-ACCESS read-create 585 STATUS current 586 DESCRIPTION 587 "This RBridge's priority to hold this nickname. When 588 the nickname is configured, the default value of 589 this object is 192. 591 The value of this object MUST be retained across 592 reinitializations of the management system." 593 REFERENCE 594 "RFC 6325 section 3.7" 595 DEFVAL { 192 } 596 ::= { rbridgeBaseNicknameEntry 2 } 598 rbridgeBaseNicknameDtrPriority OBJECT-TYPE 599 SYNTAX Unsigned32 (1..65535) 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "The Distribution tree root priority for this nickname. 604 The default value of this object is 32768. 606 The value of this object MUST be retained across 607 reinitializations of the management system." 609 REFERENCE 610 "RFC 6325 section 4.5" 611 DEFVAL { 32768 } 612 ::= { rbridgeBaseNicknameEntry 3 } 614 rbridgeBaseNicknameType OBJECT-TYPE 615 SYNTAX INTEGER { 616 static(1), 617 dynamic(2) 618 } 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "This object indicates the status of the entry. The 623 default value is static(1). 624 static(1) - this entry has been configured and 625 will remain after the next reset of the RBridge. 626 dynamic(2) - this entry has been acquired by the 627 RBridge nickname acquisition protocol." 628 REFERENCE 629 "RFC 6325 section 3.7" 630 DEFVAL { static } 631 ::= { rbridgeBaseNicknameEntry 4 } 633 rbridgeBaseNicknameRowStatus OBJECT-TYPE 634 SYNTAX RowStatus 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "This object indicates the status of the entry." 639 ::= { rbridgeBaseNicknameEntry 5 } 641 -- ---------------------------------------------------------- -- 642 -- The RBridge Port Table 643 -- ---------------------------------------------------------- -- 645 rbridgeBasePortTable OBJECT-TYPE 646 SYNTAX SEQUENCE OF RbridgeBasePortEntry 647 MAX-ACCESS not-accessible 648 STATUS current 649 DESCRIPTION 650 "A table that contains generic information about every 651 port that is associated with this RBridge." 652 REFERENCE 653 "RFC 6325 section 5.2" 654 ::= { rbridgeBase 9 } 656 rbridgeBasePortEntry OBJECT-TYPE 657 SYNTAX RbridgeBasePortEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "A list of information for each port of the bridge." 662 REFERENCE 663 "RFC 6325 section 5.2" 664 INDEX { rbridgeBasePort } 665 ::= { rbridgeBasePortTable 1 } 667 RbridgeBasePortEntry ::= 668 SEQUENCE { 669 rbridgeBasePort 670 Unsigned32, 671 rbridgeBasePortIfIndex 672 InterfaceIndex, 673 rbridgeBasePortDisable 674 TruthValue, 675 rbridgeBasePortTrunkPort 676 TruthValue, 677 rbridgeBasePortAccessPort 678 TruthValue, 679 rbridgeBasePortP2pHellos 680 TruthValue, 681 rbridgeBasePortState 682 INTEGER, 683 rbridgeBasePortInhibitionTime 684 Unsigned32, 685 rbridgeBasePortDisableLearning 686 TruthValue, 687 rbridgeBasePortDesiredDesigVlan 688 VlanId, 689 rbridgeBasePortDesigVlan 690 VlanId, 691 rbridgeBasePortStpRoot 692 BridgeId, 693 rbridgeBasePortStpRootChanges 694 Counter32, 695 rbridgeBasePortStpWiringCloset 696 BridgeId 697 } 699 rbridgeBasePort OBJECT-TYPE 700 SYNTAX Unsigned32 (1..65535) 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "The port number of the port for which this entry 705 contains RBridge management information." 706 REFERENCE 707 "RFC 6325 section 5.2" 708 ::= { rbridgeBasePortEntry 1 } 710 rbridgeBasePortIfIndex OBJECT-TYPE 711 SYNTAX InterfaceIndex 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The value of the instance of the ifIndex object, 716 defined in IF-MIB, for the interface corresponding 717 to this port." 718 ::= { rbridgeBasePortEntry 2 } 720 rbridgeBasePortDisable OBJECT-TYPE 721 SYNTAX TruthValue 722 MAX-ACCESS read-write 723 STATUS current 724 DESCRIPTION 725 "Disable port bit. When this bit is set (true), all frames 726 received or to be transmitted are discarded, with the 727 possible exception of some layer 2 control frames that may 728 be generated and transmitted or received and processed 729 locally. Default value is false. 731 The value of this object MUST be retained across 732 reinitializations of the management system." 733 REFERENCE 734 "RFC 6325 section 4.9.1" 735 DEFVAL { false } 736 ::= { rbridgeBasePortEntry 3 } 738 rbridgeBasePortTrunkPort OBJECT-TYPE 739 SYNTAX TruthValue 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 "End station service disable (trunk port) bit. When this bit 744 is set (true), all native frames received on the port and all 745 native frames that would have been sent on the port are 746 discarded. Default value is false. 748 The value of this object MUST be retained across 749 reinitializations of the management system." 750 REFERENCE 751 "RFC 6325 4.9.1" 753 DEFVAL { false } 754 ::= { rbridgeBasePortEntry 4 } 756 rbridgeBasePortAccessPort OBJECT-TYPE 757 SYNTAX TruthValue 758 MAX-ACCESS read-write 759 STATUS current 760 DESCRIPTION 761 "TRILL traffic disable (access port) bit. If this bit is set, 762 the goal is to avoid sending any TRILL frames, except 763 TRILL-Hello frames, on the port since it is intended only for 764 native end station traffic. This ensures that the link is 765 not on the shortest path for any destination. Default value 766 is false. 768 The value of this object MUST be retained across 769 reinitializations of the management system." 770 REFERENCE 771 "RFC 6325 4.9.1" 772 DEFVAL { false } 773 ::= { rbridgeBasePortEntry 5 } 775 rbridgeBasePortP2pHellos OBJECT-TYPE 776 SYNTAX TruthValue 777 MAX-ACCESS read-write 778 STATUS current 779 DESCRIPTION 780 "Use P2P Hellos bit. If this bit is set, Hellos sent on this 781 port are IS-IS P2P Hellos, not the default TRILL-Hellos. In 782 addition, the IS-IS P2P three-way handshake is used on P2P 783 RBridge links. Default value is false. 785 The value of this object MUST be retained across 786 reinitializations of the management system." 787 REFERENCE 788 "RFC 6325 4.9.1" 789 DEFVAL { false } 790 ::= { rbridgeBasePortEntry 6 } 792 rbridgeBasePortState OBJECT-TYPE 793 SYNTAX INTEGER { 794 uninhibited(1), 795 portInhibited(2), 796 vlanInhibited(3), 797 disabled(4), 798 broken(5) 799 } 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The port's current state. If the entire port is 804 inhibited, its state is portInhibited(2). If specific VLANs 805 are inhibited, the state is vlanInhibited(3) and 806 rbridgeVlanTable will tell which VLANs are inhibited. 807 For ports that are disabled (see rbridgeBasePortDisable), 808 this object will have a value of disabled(4). If the 809 RBridge has detected a port that is malfunctioning, it will 810 place that port into the broken(5) state." 811 REFERENCE 812 "RFC 6325 section 4.2.4.3" 813 ::= { rbridgeBasePortEntry 7 } 815 rbridgeBasePortInhibitionTime OBJECT-TYPE 816 SYNTAX Unsigned32 817 UNITS "seconds" 818 MAX-ACCESS read-write 819 STATUS current 820 DESCRIPTION 821 "Time in seconds that this RBridge will inhibit forwarding 822 on this port after it observes a spanning tree root bridge 823 change on a link, or receives conflicting VLAN forwarder 824 information. The default value is 30. 826 The value of this object MUST be retained across 827 reinitializations of the management system." 828 REFERENCE 829 "RFC 6325 section 4.2.4.3" 830 DEFVAL { 30 } 831 ::= { rbridgeBasePortEntry 8 } 833 rbridgeBasePortDisableLearning OBJECT-TYPE 834 SYNTAX TruthValue 835 MAX-ACCESS read-write 836 STATUS current 837 DESCRIPTION 838 "Disable learning of MAC addresses seen on this port. 839 To disable learning, the value of this object must be 840 set to 'true'. The default is 'false'. 842 The value of this object MUST be retained across 843 reinitializations of the management system." 844 REFERENCE 845 "RFC 6325 section 4.8" 846 DEFVAL { false } 847 ::= { rbridgeBasePortEntry 9 } 849 rbridgeBasePortDesiredDesigVlan OBJECT-TYPE 850 SYNTAX VlanId 851 MAX-ACCESS read-write 852 STATUS current 853 DESCRIPTION 854 "The VLAN that a DRB will specify in its TRILL-Hellos as the 855 VLAN to be used by all RBridges on the link for TRILL frames. 856 This VLAN must be enabled on this port. 858 The value of this object MUST be retained across 859 reinitializations of the management system." 860 REFERENCE 861 "RFC 6325 section 4.4.3" 862 ::= { rbridgeBasePortEntry 10 } 864 rbridgeBasePortDesigVlan OBJECT-TYPE 865 SYNTAX VlanId 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The VLAN being used on this link for TRILL frames." 870 REFERENCE 871 "RFC 6325 section 4.4.3" 872 ::= { rbridgeBasePortEntry 11 } 874 rbridgeBasePortStpRoot OBJECT-TYPE 875 SYNTAX BridgeId 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The bridge identifier of the root of the spanning 880 tree, as learned from a BPDU received on this port. For 881 MSTP, this is the root bridge of the CIST. If no BPDU has 882 been heard, the value returned is a string of zeros." 883 REFERENCE 884 "RFC 6325 section 4.2.4.3" 885 ::= { rbridgeBasePortEntry 12 } 887 rbridgeBasePortStpRootChanges OBJECT-TYPE 888 SYNTAX Counter32 889 UNITS "changes" 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The number of times a change in the root bridge is seen from 894 spanning tree BPDUs received on this port, indicating a 895 change in bridged LAN topology. Each such change may cause 896 the port to be inhibited for a period of time. 898 Discontinuities in the value of this counter can occur 899 at re-initialization of the management system." 900 REFERENCE 901 "RFC 6325 section 4.9.3.2" 902 ::= { rbridgeBasePortEntry 13 } 904 rbridgeBasePortStpWiringCloset OBJECT-TYPE 905 SYNTAX BridgeId 906 MAX-ACCESS read-write 907 STATUS current 908 DESCRIPTION 909 "The Bridge ID to be used as Spanning Tree root in BPDUs 910 sent for the Wiring Closet topology solution described in 911 [RFC6325]. Note that the same value of this object must be 912 set on all RBridge ports participating in this solution. 913 The default value is all 0s. A non-zero value configured 914 into this object indicates that this solution is in use. 916 The value of this object MUST be retained across 917 reinitializations of the management system." 918 REFERENCE 919 "RFC 6325 section A.3.3" 920 ::= { rbridgeBasePortEntry 14 } 922 -- ------------------------------------------------------------- 923 -- RBridge Forwarding Database 924 -- ------------------------------------------------------------- 926 rbridgeConfidenceNative OBJECT-TYPE 927 SYNTAX Unsigned32 (0..255) 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "The confidence level associated with MAC addresses 932 learned from native frames. The default value is 32. 934 The value of this object MUST be retained across 935 reinitializations of the management system." 936 REFERENCE 937 "RFC 6325 section 4.8.1" 938 ::= { rbridgeFdb 1 } 940 rbridgeConfidenceDecap OBJECT-TYPE 941 SYNTAX Unsigned32 (0..255) 942 MAX-ACCESS read-write 943 STATUS current 944 DESCRIPTION 945 "The confidence level associated with inner MAC addresses 946 learned after decapsulation of a TRILL data frame. 947 The default value is 32. 949 The value of this object MUST be retained across 950 reinitializations of the management system." 951 REFERENCE 952 "RFC 6325 Appendix section 4.8.1" 953 ::= { rbridgeFdb 2 } 955 rbridgeConfidenceStatic OBJECT-TYPE 956 SYNTAX Unsigned32 (0..255) 957 MAX-ACCESS read-write 958 STATUS current 959 DESCRIPTION 960 "The confidence level associated with MAC addresses that 961 are statically configured. The default value is 255. 963 The value of this object MUST be retained across 964 reinitializations of the management system." 965 REFERENCE 966 "RFC 6325 section 4.8.2" 967 DEFVAL { 255 } 968 ::= { rbridgeFdb 3 } 970 -- ------------------------------------------------------------- 971 -- Multiple Forwarding Databases for RBridges 972 -- 973 -- This allows for an instance per FdbId, as defined in the 974 -- Bridge MIB. 975 -- 976 -- Each VLAN may have an independent Fdb, or multiple VLANs may 977 -- share one. 978 -- ------------------------------------------------------------- 980 rbridgeUniFdbTable OBJECT-TYPE 981 SYNTAX SEQUENCE OF RbridgeUniFdbEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "A table that contains information about unicast entries 986 for which the device has forwarding and/or filtering 987 information. This information is used by the 988 transparent bridging function in determining how to 989 propagate a received frame." 990 REFERENCE 991 "RFC 6325 section 4.8" 993 ::= { rbridgeFdb 4 } 995 rbridgeUniFdbEntry OBJECT-TYPE 996 SYNTAX RbridgeUniFdbEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "Information about a specific unicast MAC address for 1001 which the rbridge has some forwarding and/or filtering 1002 information." 1003 INDEX { rbridgeFdbId, rbridgeUniFdbAddr } 1004 ::= { rbridgeUniFdbTable 1 } 1006 RbridgeUniFdbEntry ::= 1007 SEQUENCE { 1008 rbridgeFdbId 1009 Unsigned32, 1010 rbridgeUniFdbAddr 1011 MacAddress, 1012 rbridgeUniFdbPort 1013 Unsigned32, 1014 rbridgeUniFdbNickname 1015 RbridgeNickname, 1016 rbridgeUniFdbConfidence 1017 Unsigned32, 1018 rbridgeUniFdbStatus 1019 INTEGER 1020 } 1022 rbridgeFdbId OBJECT-TYPE 1023 SYNTAX Unsigned32 (0..4294967295) 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "The identity of this Filtering Database." 1028 ::= { rbridgeUniFdbEntry 1 } 1030 rbridgeUniFdbAddr OBJECT-TYPE 1031 SYNTAX MacAddress 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "A unicast MAC address for which the device has 1036 forwarding information." 1037 ::= { rbridgeUniFdbEntry 2 } 1039 rbridgeUniFdbPort OBJECT-TYPE 1040 SYNTAX Unsigned32 (0..65535) 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "Either the value '0', or the Rbridge port number of the 1045 port on which a frame having a source address equal to the 1046 value of the corresponding instance of rbridgeUniFdbAddress 1047 has been seen. A value of '0' indicates that the port 1048 number has not been learned but that the device does have 1049 some information about this MAC address. 1051 Implementors are encouraged to assign the port value to 1052 this object whenever it is available, even for addresses 1053 for which the corresponding value of rbridgeUniFdbStatus is 1054 not learned(3)." 1055 ::= { rbridgeUniFdbEntry 3 } 1057 rbridgeUniFdbNickname OBJECT-TYPE 1058 SYNTAX RbridgeNickname 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The RBridge nickname which is placed in the Egress 1063 Nickname field of a TRILL frame sent to this 1064 rbridgeFdbAddress in this FdbId." 1065 REFERENCE 1066 "RFC 6325 section 4.8.1" 1067 ::= { rbridgeUniFdbEntry 4 } 1069 rbridgeUniFdbConfidence OBJECT-TYPE 1070 SYNTAX Unsigned32 (0..255) 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "The confidence level associated with this entry." 1075 REFERENCE 1076 "RFC 6325 section 4.8.1" 1077 ::= { rbridgeUniFdbEntry 5 } 1079 rbridgeUniFdbStatus OBJECT-TYPE 1080 SYNTAX INTEGER { 1081 other(1), 1082 invalid(2), 1083 learned(3), 1084 self(4), 1085 mgmt(5), 1086 esadi(6) 1087 } 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The status of this entry. The meanings of the values 1092 are: 1093 other(1) - none of the following. 1094 invalid(2) - this entry is no longer valid (e.g., it 1095 was learned but has since aged out), but has not 1096 yet been flushed from the table. 1097 learned(3) - the information in this entry was learned 1098 and is being used. 1099 self(4) - the value of the corresponding instance of 1100 rbridgeFdbAddress represents one of the device's 1101 addresses. The corresponding instance of 1102 rbridgeFdbPort indicates which of the device's 1103 ports has this address. 1104 mgmt(5) - the value of the corresponding instance of 1105 rbridgeFdbAddress was configured by management. 1106 esadi(6) - the value of the corresponding instance of 1107 rbridgeFdbAddress was learned from ESADI." 1108 ::= { rbridgeUniFdbEntry 6 } 1110 -- ------------------------------------------------------------- 1111 -- RBridge FIB 1112 -- ------------------------------------------------------------- 1114 rbridgeUniFibTable OBJECT-TYPE 1115 SYNTAX SEQUENCE OF RbridgeUniFibEntry 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION 1119 "A table that contains information about nicknames 1120 known by the RBridge. If ECMP is implemented, there are 1121 as many entries for a nickname as ECMP paths available for 1122 it." 1123 ::= { rbridgeFdb 5 } 1125 rbridgeUniFibEntry OBJECT-TYPE 1126 SYNTAX RbridgeUniFibEntry 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "A list of information about nicknames known by the RBridge. 1131 If ECMP is implemented, there are as many entries as ECMP 1132 paths available for a given nickname." 1133 INDEX { rbridgeUniFibNickname, rbridgeUniFibPort, 1134 rbridgeUniFibNextHop } 1135 ::= { rbridgeUniFibTable 1 } 1137 RbridgeUniFibEntry ::= 1138 SEQUENCE { 1139 rbridgeUniFibNickname 1140 RbridgeNickname, 1141 rbridgeUniFibPort 1142 Unsigned32, 1143 rbridgeUniFibNextHop 1144 RbridgeNickname, 1145 rbridgeUniFibHopCount 1146 Unsigned32 1147 } 1149 rbridgeUniFibNickname OBJECT-TYPE 1150 SYNTAX RbridgeNickname 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "An RBridge nickname for which this RBridge has 1155 forwarding information." 1156 ::= { rbridgeUniFibEntry 1 } 1158 rbridgeUniFibPort OBJECT-TYPE 1159 SYNTAX Unsigned32 (0..65535) 1160 MAX-ACCESS not-accessible 1161 STATUS current 1162 DESCRIPTION 1163 "The Rbridge port number of the port attached to the 1164 next-hop RBridge for the path towards the RBridge whose 1165 nickname is specified in this entry." 1166 ::= { rbridgeUniFibEntry 2 } 1168 rbridgeUniFibNextHop OBJECT-TYPE 1169 SYNTAX RbridgeNickname 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "The nickname of the next-hop RBridge for the path 1174 towards the RBridge whose nickname is specified in this 1175 entry." 1176 ::= { rbridgeUniFibEntry 3 } 1178 rbridgeUniFibHopCount OBJECT-TYPE 1179 SYNTAX Unsigned32 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "The hop count from this ingress Rbridge to the egress 1184 RBridge whose nickname is specified in 1185 rbridgeUniFibNickname." 1186 ::= { rbridgeUniFibEntry 4 } 1188 rbridgeMultiFibTable OBJECT-TYPE 1189 SYNTAX SEQUENCE OF RbridgeMultiFibEntry 1190 MAX-ACCESS not-accessible 1191 STATUS current 1192 DESCRIPTION 1193 "A table that contains information about egress nicknames 1194 used for multi-destination frame forwarding by this 1195 RBridge." 1196 ::= { rbridgeFdb 6 } 1198 rbridgeMultiFibEntry OBJECT-TYPE 1199 SYNTAX RbridgeMultiFibEntry 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "A list of information about egress nicknames used for 1204 multi-destination frame forwarding by this RBridge." 1205 INDEX { rbridgeMultiFibNickname } 1206 ::= { rbridgeMultiFibTable 1 } 1208 RbridgeMultiFibEntry ::= 1209 SEQUENCE { 1210 rbridgeMultiFibNickname 1211 RbridgeNickname, 1212 rbridgeMultiFibPorts 1213 PortList 1214 } 1216 rbridgeMultiFibNickname OBJECT-TYPE 1217 SYNTAX RbridgeNickname 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "The nickname of the multicast distribution tree." 1222 ::= { rbridgeMultiFibEntry 1 } 1224 rbridgeMultiFibPorts OBJECT-TYPE 1225 SYNTAX PortList 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The list of ports to which a frame destined to this 1230 multicast distribution tree is flooded. This may be pruned 1231 further based on other forwarding information." 1232 ::= { rbridgeMultiFibEntry 2 } 1234 -- ---------------------------------------------------------- -- 1235 -- The RBridge VLAN Table 1236 -- ---------------------------------------------------------- -- 1238 rbridgeVlanTable OBJECT-TYPE 1239 SYNTAX SEQUENCE OF RbridgeVlanEntry 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "A table that contains information about VLANs on the 1244 RBridge." 1245 ::= { rbridgeVlan 1 } 1247 rbridgeVlanEntry OBJECT-TYPE 1248 SYNTAX RbridgeVlanEntry 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "A list of information about VLANs on the RBridge." 1253 INDEX { rbridgeVlanIndex } 1254 ::= { rbridgeVlanTable 1 } 1256 RbridgeVlanEntry ::= 1257 SEQUENCE { 1258 rbridgeVlanIndex 1259 Unsigned32, 1260 rbridgeVlanForwarderLosts 1261 Counter32, 1262 rbridgeVlanDisableLearning 1263 TruthValue, 1264 rbridgeVlanSnooping 1265 INTEGER 1266 } 1268 rbridgeVlanIndex OBJECT-TYPE 1269 SYNTAX Unsigned32 (1..4094|4096..4294967295) 1270 MAX-ACCESS not-accessible 1271 STATUS current 1272 DESCRIPTION 1273 "The VLAN-ID referring to this VLAN." 1274 ::= { rbridgeVlanEntry 1 } 1276 rbridgeVlanForwarderLosts OBJECT-TYPE 1277 SYNTAX Counter32 1278 UNITS "times" 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "The number of times this RBridge has lost appointed 1283 forwarder status for this VLAN on any of its ports. 1285 Discontinuities in the value of this counter can occur 1286 at re-initialization of the management system." 1287 REFERENCE 1288 "RFC 6325 section 4.8.2" 1289 ::= { rbridgeVlanEntry 2 } 1291 rbridgeVlanDisableLearning OBJECT-TYPE 1292 SYNTAX TruthValue 1293 MAX-ACCESS read-write 1294 STATUS current 1295 DESCRIPTION 1296 "Disable learning of MAC addresses seen in this VLAN. 1297 One application of this may be to restrict learning to 1298 ESADI. To disable learning, the value of this object 1299 should be set to true. The default is false. 1301 The value of this object MUST be retained across 1302 reinitializations of the management system." 1303 REFERENCE 1304 "RFC 6325 section 4.8" 1305 DEFVAL { false } 1306 ::= { rbridgeVlanEntry 3 } 1308 rbridgeVlanSnooping OBJECT-TYPE 1309 SYNTAX INTEGER { 1310 notSupported(1), 1311 ipv4(2), 1312 ipv6(3), 1313 ipv4v6(4) 1314 } 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "IP Multicast Snooping on this VLAN. For RBridges 1319 performing both IPv4 and IPv6 IP Multicast Snooping, the 1320 value returned is ipv4v6(3)." 1321 REFERENCE 1322 "RFC 6325 section 4.7" 1323 ::= { rbridgeVlanEntry 4 } 1325 -- ---------------------------------------------------------- -- 1326 -- The RBridge VLAN Port Table 1327 -- ---------------------------------------------------------- -- 1329 rbridgeVlanPortTable OBJECT-TYPE 1330 SYNTAX SEQUENCE OF RbridgeVlanPortEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "A table that contains information about VLANs on an RBridge 1335 port." 1336 ::= { rbridgeVlan 2 } 1338 rbridgeVlanPortEntry OBJECT-TYPE 1339 SYNTAX RbridgeVlanPortEntry 1340 MAX-ACCESS not-accessible 1341 STATUS current 1342 DESCRIPTION 1343 "A list of information about VLANs on the RBridge port." 1344 INDEX { rbridgeBasePort, rbridgeVlanIndex } 1345 ::= { rbridgeVlanPortTable 1 } 1347 RbridgeVlanPortEntry ::= 1348 SEQUENCE { 1349 rbridgeVlanPortInhibited 1350 TruthValue, 1351 rbridgeVlanPortForwarder 1352 TruthValue, 1353 rbridgeVlanPortAnnouncing 1354 TruthValue, 1355 rbridgeVlanPortDetectedVlanMapping 1356 TruthValue 1357 } 1359 rbridgeVlanPortInhibited OBJECT-TYPE 1360 SYNTAX TruthValue 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "This VLAN has been inhibited by the RBridge due to 1365 conflicting Forwarder information received from another 1366 RBridge." 1367 REFERENCE 1368 "RFC 6325 section 4.2.4.3" 1369 ::= { rbridgeVlanPortEntry 1 } 1371 rbridgeVlanPortForwarder OBJECT-TYPE 1372 SYNTAX TruthValue 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "This RBridge is an Appointed Forwarder for this VLAN on 1377 this port." 1379 REFERENCE 1380 "RFC 6325 section 4.2.4.3" 1381 ::= { rbridgeVlanPortEntry 2 } 1383 rbridgeVlanPortAnnouncing OBJECT-TYPE 1384 SYNTAX TruthValue 1385 MAX-ACCESS read-write 1386 STATUS current 1387 DESCRIPTION 1388 "TRILL-Hellos tagged with this VLAN can be sent by this 1389 RBridge on this port. Defaults to true for enabled 1390 VLANs. 1392 The value of this object MUST be retained across 1393 reinitializations of the management system." 1394 REFERENCE 1395 "RFC 6325 section 4.4.3" 1396 DEFVAL { true } 1397 ::= { rbridgeVlanPortEntry 3 } 1399 rbridgeVlanPortDetectedVlanMapping OBJECT-TYPE 1400 SYNTAX TruthValue 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "VLAN mapping has been detected on the link attached 1405 to this port." 1406 REFERENCE 1407 "RFC 6325 section 4.4.5" 1408 ::= { rbridgeVlanPortEntry 4 } 1410 -- ---------------------------------------------------------- -- 1411 -- The RBridge Port Counter Table 1412 -- 1413 -- These counters supplement counters in the Bridge MIB. 1414 -- 1415 -- For example, total frames received by a bridge port and total 1416 -- frames transmitted by a bridge port are reported in the 1417 -- Port In Frames and Ports Out Frames counters of the Bridge MIB. 1418 -- These total bridge frames counters include native as well as 1419 -- encapsulated frames. 1420 -- 1421 -- As another example,frames discarded due to excessive frame 1422 -- size are reported in the port counter MTU Exceeded Discards 1423 -- in the Bridge MIB. 1424 -- ---------------------------------------------------------- -- 1425 rbridgePortCounterTable OBJECT-TYPE 1426 SYNTAX SEQUENCE OF RbridgePortCounterEntry 1427 MAX-ACCESS not-accessible 1428 STATUS current 1429 DESCRIPTION 1430 "A table contains per-port counters for this RBridge." 1431 ::= { rbridgeCounter 1 } 1433 rbridgePortCounterEntry OBJECT-TYPE 1434 SYNTAX RbridgePortCounterEntry 1435 MAX-ACCESS not-accessible 1436 STATUS current 1437 DESCRIPTION 1438 "Counters for a port on this RBridge." 1439 INDEX { rbridgeBasePort } 1440 ::= { rbridgePortCounterTable 1 } 1442 RbridgePortCounterEntry ::= 1443 SEQUENCE { 1444 rbridgePortRpfCheckFails 1445 Counter32, 1446 rbridgePortHopCountExceeds 1447 Counter32, 1448 rbridgePortOptionDrops 1449 Counter32, 1450 rbridgePortTrillInFrames 1451 Counter64, 1452 rbridgePortTrillOutFrames 1453 Counter64 1454 } 1456 rbridgePortRpfCheckFails OBJECT-TYPE 1457 SYNTAX Counter32 1458 UNITS "frames" 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "The number of times a multidestination frame was 1463 dropped on this port because the RPF check failed. 1465 Discontinuities in the value of this counter can occur 1466 at re-initialization of the management system, and at 1467 other times as indicated by the value of 1468 ifCounterDiscontinuityTime object of the associated 1469 interface." 1470 REFERENCE 1471 "RFC 6325 section 4.5.2" 1472 ::= { rbridgePortCounterEntry 1 } 1474 rbridgePortHopCountExceeds OBJECT-TYPE 1475 SYNTAX Counter32 1476 UNITS "frames" 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "The number of times a frame was dropped on this port 1481 because its hop count was zero. 1483 Discontinuities in the value of this counter can occur 1484 at re-initialization of the management system, and at 1485 other times as indicated by the value of 1486 ifCounterDiscontinuityTime object of the associated 1487 interface." 1488 REFERENCE 1489 "RFC 6325 section 3.6" 1490 ::= { rbridgePortCounterEntry 2 } 1492 rbridgePortOptionDrops OBJECT-TYPE 1493 SYNTAX Counter32 1494 UNITS "frames" 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "The number of times a frame was dropped on this port 1499 because it contained unsupported options. 1501 Discontinuities in the value of this counter can occur 1502 at re-initialization of the management system, and at 1503 other times as indicated by the value of 1504 ifCounterDiscontinuityTime object of the associated 1505 interface." 1506 REFERENCE 1507 "RFC 6325 section 3.5" 1508 ::= { rbridgePortCounterEntry 3 } 1510 rbridgePortTrillInFrames OBJECT-TYPE 1511 SYNTAX Counter64 1512 UNITS "frames" 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "The number of TRILL-encapsulated frames that have been 1517 received by this port from its attached link, including 1518 management frames. 1520 Discontinuities in the value of this counter can occur 1521 at re-initialization of the management system, and at 1522 other times as indicated by the value of 1523 ifCounterDiscontinuityTime object of the associated 1524 interface." 1525 REFERENCE 1526 "RFC 6325 section 2.3" 1527 ::= { rbridgePortCounterEntry 4 } 1529 rbridgePortTrillOutFrames OBJECT-TYPE 1530 SYNTAX Counter64 1531 UNITS "frames" 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "The number of TRILL-encapsulated frames that have been 1536 transmitted by this port to its attached link, including 1537 management frames. 1539 Discontinuities in the value of this counter can occur 1540 at re-initialization of the management system, and at 1541 other times as indicated by the value of 1542 ifCounterDiscontinuityTime object of the associated 1543 interface." 1544 REFERENCE 1545 "RFC 6325 section 2.3" 1546 ::= { rbridgePortCounterEntry 5 } 1548 -- ---------------------------------------------------------- -- 1549 -- The RBridge VLAN ESADI Table 1550 -- ---------------------------------------------------------- -- 1552 rbridgeEsadiTable OBJECT-TYPE 1553 SYNTAX SEQUENCE OF RbridgeEsadiEntry 1554 MAX-ACCESS not-accessible 1555 STATUS current 1556 DESCRIPTION 1557 "A table that contains information about ESADI instances on 1558 VLANs, if available." 1559 REFERENCE 1560 "RFC 6325 section 4.2.5" 1561 ::= { rbridgeEsadi 1 } 1563 rbridgeEsadiEntry OBJECT-TYPE 1564 SYNTAX RbridgeEsadiEntry 1565 MAX-ACCESS not-accessible 1566 STATUS current 1567 DESCRIPTION 1568 "Information about an ESADI instance on a VLAN." 1569 INDEX { rbridgeVlanIndex } 1570 ::= { rbridgeEsadiTable 1 } 1572 RbridgeEsadiEntry ::= 1573 SEQUENCE { 1574 rbridgeEsadiEnable 1575 TruthValue, 1576 rbridgeEsadiConfidence 1577 Unsigned32, 1578 rbridgeEsadiDrbPriority 1579 Unsigned32, 1580 rbridgeEsadiDrb 1581 RbridgeAddress, 1582 rbridgeEsadiDrbHoldingTime 1583 Unsigned32, 1584 rbridgeEsadiRowStatus 1585 RowStatus 1586 } 1588 rbridgeEsadiEnable OBJECT-TYPE 1589 SYNTAX TruthValue 1590 MAX-ACCESS read-create 1591 STATUS current 1592 DESCRIPTION 1593 "If the RBridge is participating in an ESADI instance for 1594 this VLAN, the value of this object is 'true'. To disable 1595 participation, set it to 'false'. 1597 The value of this object MUST be retained across 1598 reinitializations of the management system." 1599 REFERENCE 1600 "RFC 6325 section 4.2.5" 1601 DEFVAL { true } 1602 ::= { rbridgeEsadiEntry 1 } 1604 rbridgeEsadiConfidence OBJECT-TYPE 1605 SYNTAX Unsigned32 (0..255) 1606 MAX-ACCESS read-create 1607 STATUS current 1608 DESCRIPTION 1609 "Confidence level of address entries sent by this 1610 ESADI. The default is 16. 1612 The value of this object MUST be retained across 1613 reinitializations of the management system." 1614 REFERENCE 1615 "RFC 6325 section 4.2.5" 1616 DEFVAL { 16 } 1617 ::= { rbridgeEsadiEntry 2 } 1619 rbridgeEsadiDrbPriority OBJECT-TYPE 1620 SYNTAX Unsigned32 (0..127) 1621 MAX-ACCESS read-create 1622 STATUS current 1623 DESCRIPTION 1624 "The priority of this RBridge for being selected as 1625 DRB for this ESADI instance. 1627 The value of this object MUST be retained across 1628 reinitializations of the management system." 1629 REFERENCE 1630 "RFC 6325 section 4.2.5" 1631 ::= { rbridgeEsadiEntry 3 } 1633 rbridgeEsadiDrb OBJECT-TYPE 1634 SYNTAX RbridgeAddress 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "The DRB on this ESADI instance's virtual link." 1639 REFERENCE 1640 "RFC 6325 section 4.2.5" 1641 ::= { rbridgeEsadiEntry 4 } 1643 rbridgeEsadiDrbHoldingTime OBJECT-TYPE 1644 SYNTAX Unsigned32 (0..127) 1645 MAX-ACCESS read-create 1646 STATUS current 1647 DESCRIPTION 1648 "The holding time for this ESADI instance. 1650 The value of this object MUST be retained across 1651 reinitializations of the management system." 1652 REFERENCE 1653 "RFC 6325 section 4.2.5" 1654 ::= { rbridgeEsadiEntry 5 } 1656 rbridgeEsadiRowStatus OBJECT-TYPE 1657 SYNTAX RowStatus 1658 MAX-ACCESS read-create 1659 STATUS current 1660 DESCRIPTION 1661 "This object indicates the status of the entry." 1662 ::= { rbridgeEsadiEntry 6 } 1664 -- ---------------------------------------------------------- -- 1665 -- The RBridge IP Multicast Snooping Port Table 1666 -- ---------------------------------------------------------- -- 1668 rbridgeSnoopingPortTable OBJECT-TYPE 1669 SYNTAX SEQUENCE OF RbridgeSnoopingPortEntry 1670 MAX-ACCESS not-accessible 1671 STATUS current 1672 DESCRIPTION 1673 "For Rbridges implementing IP Multicast Snooping, 1674 information about ports on which the presence of IPv4 1675 or IPv6 Multicast Routers has been detected." 1676 REFERENCE 1677 "RFC 6325 section 4.7" 1678 ::= { rbridgeSnooping 1 } 1680 rbridgeSnoopingPortEntry OBJECT-TYPE 1681 SYNTAX RbridgeSnoopingPortEntry 1682 MAX-ACCESS not-accessible 1683 STATUS current 1684 DESCRIPTION 1685 "Information about ports on which the presence of IPv4 1686 or IPv6 Multicast Routers has been detected." 1687 INDEX { rbridgeBasePort } 1688 ::= { rbridgeSnoopingPortTable 1 } 1690 RbridgeSnoopingPortEntry ::= 1691 SEQUENCE { 1692 rbridgeSnoopingPortAddrType 1693 InetAddressType, 1694 rbridgeSnoopingPortAddr 1695 InetAddress 1696 } 1698 rbridgeSnoopingPortAddrType OBJECT-TYPE 1699 SYNTAX InetAddressType 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "The IP address type of an IP multicast router detected 1704 on this port. This MIB requires support for only 1705 IPv4 and IPv6 address types." 1706 REFERENCE 1707 "RFC 6325 section 4.7" 1708 ::= { rbridgeSnoopingPortEntry 1 } 1710 rbridgeSnoopingPortAddr OBJECT-TYPE 1711 SYNTAX InetAddress 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "The IP address of an IP multicast router detected on 1716 this port, in the context of rbridgeSnoopingPortAddrType. 1717 This MIB requires support for only global IPv4 and IPv6 1718 addresses, so the length of the object can be either 4 1719 or 16 bytes." 1720 REFERENCE 1721 "RFC 6325 section 4.7" 1722 ::= { rbridgeSnoopingPortEntry 2 } 1724 -- ---------------------------------------------------------- -- 1725 -- The RBridge IP Multicast Snooping Address Table 1726 -- ---------------------------------------------------------- -- 1728 rbridgeSnoopingAddrTable OBJECT-TYPE 1729 SYNTAX SEQUENCE OF RbridgeSnoopingAddrEntry 1730 MAX-ACCESS not-accessible 1731 STATUS current 1732 DESCRIPTION 1733 "For Rbridges implementing IP Multicast Snooping, 1734 information about IP Multicast addresses being 1735 snooped." 1736 REFERENCE 1737 "RFC 6325 section 4.8" 1738 ::= { rbridgeSnooping 2 } 1740 rbridgeSnoopingAddrEntry OBJECT-TYPE 1741 SYNTAX RbridgeSnoopingAddrEntry 1742 MAX-ACCESS not-accessible 1743 STATUS current 1744 DESCRIPTION 1745 "Information about IP Multicast addresses being 1746 snooped." 1747 INDEX { rbridgeVlanIndex, rbridgeSnoopingAddrType, 1748 rbridgeSnoopingAddr } 1749 ::= { rbridgeSnoopingAddrTable 1 } 1751 RbridgeSnoopingAddrEntry ::= 1752 SEQUENCE { 1753 rbridgeSnoopingAddrType 1754 InetAddressType, 1755 rbridgeSnoopingAddr 1756 InetAddress, 1757 rbridgeSnoopingAddrPorts 1758 PortList 1759 } 1761 rbridgeSnoopingAddrType OBJECT-TYPE 1762 SYNTAX InetAddressType 1763 MAX-ACCESS not-accessible 1764 STATUS current 1765 DESCRIPTION 1766 "The IP multicast address type for which a listener has been 1767 detected by this RBridge. This MIB requires support for only 1768 IPv4 and IPv6 address types." 1769 REFERENCE 1770 "RFC 6325 section 4.7" 1771 ::= { rbridgeSnoopingAddrEntry 1 } 1773 rbridgeSnoopingAddr OBJECT-TYPE 1774 SYNTAX InetAddress 1775 MAX-ACCESS not-accessible 1776 STATUS current 1777 DESCRIPTION 1778 "The IP multicast address for which a listener has been 1779 detected by this RBridge. The address type of this object 1780 is specified in rbridgeSnoopingAddrType. This MIB requires 1781 support for only global IPv4 and IPv6 addresses, so the 1782 length of the object can be either 4 or 16 bytes." 1783 REFERENCE 1784 "RFC 6325 section 4.7" 1785 ::= { rbridgeSnoopingAddrEntry 2 } 1787 rbridgeSnoopingAddrPorts OBJECT-TYPE 1788 SYNTAX PortList 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "The set of ports on which a listener has been detected 1793 for this IP multicast address." 1794 REFERENCE 1795 "RFC 6325 section 4.7" 1796 ::= { rbridgeSnoopingAddrEntry 3 } 1798 -- ---------------------------------------------------------- -- 1799 -- Distribution Trees 1800 -- ---------------------------------------------------------- -- 1802 rbridgeDtreePriority OBJECT-TYPE 1803 SYNTAX Unsigned32 (1..65535) 1804 MAX-ACCESS read-write 1805 STATUS current 1806 DESCRIPTION 1807 "The Distribution tree root priority for this Rbridge. 1808 The default value of this object is 32768. 1810 The value of this object MUST be retained across 1811 reinitializations of the management system." 1812 REFERENCE 1813 "RFC 6325 section 4.5" 1814 ::= { rbridgeDtree 1 } 1816 rbridgeDtreeActiveTrees OBJECT-TYPE 1817 SYNTAX Unsigned32 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "The total number of trees being computed by all Rbridges 1822 in the campus." 1823 REFERENCE 1824 "RFC 6325 section 4.5" 1825 ::= { rbridgeDtree 2 } 1827 rbridgeDtreeMaxTrees OBJECT-TYPE 1828 SYNTAX Unsigned32 1829 MAX-ACCESS read-only 1830 STATUS current 1831 DESCRIPTION 1832 "The maximum number of trees this Rbridge can compute." 1833 REFERENCE 1834 "RFC 6325 section 4.5" 1835 ::= { rbridgeDtree 3 } 1837 rbridgeDtreeDesiredUseTrees OBJECT-TYPE 1838 SYNTAX Unsigned32 1839 MAX-ACCESS read-only 1840 STATUS current 1841 DESCRIPTION 1842 "The maximum number of trees this Rbridge would like to 1843 use for transmission of ingress multi-destination frames." 1844 REFERENCE 1845 "RFC 6325 section 4.5" 1846 ::= { rbridgeDtree 4 } 1848 rbridgeDtreeTable OBJECT-TYPE 1849 SYNTAX SEQUENCE OF RbridgeDtreeEntry 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "Information about Distribution Trees being computed 1854 by this Rbridge." 1855 REFERENCE 1856 "RFC 6325 section 4.5" 1857 ::= { rbridgeDtree 5 } 1859 rbridgeDtreeEntry OBJECT-TYPE 1860 SYNTAX RbridgeDtreeEntry 1861 MAX-ACCESS not-accessible 1862 STATUS current 1863 DESCRIPTION 1864 "List of information about Distribution Trees being computed 1865 by this Rbridge." 1866 INDEX { rbridgeDtreeNumber } 1867 ::= { rbridgeDtreeTable 1 } 1869 RbridgeDtreeEntry ::= 1870 SEQUENCE { 1871 rbridgeDtreeNumber 1872 Unsigned32, 1873 rbridgeDtreeNickname 1874 RbridgeNickname, 1875 rbridgeDtreeIngress 1876 TruthValue 1877 } 1879 rbridgeDtreeNumber OBJECT-TYPE 1880 SYNTAX Unsigned32 (0..65535) 1881 MAX-ACCESS not-accessible 1882 STATUS current 1883 DESCRIPTION 1884 "The tree number of a distribution tree being computed by 1885 this RBridge." 1886 REFERENCE 1887 "RFC 6325 section 4.5" 1888 ::= { rbridgeDtreeEntry 1 } 1890 rbridgeDtreeNickname OBJECT-TYPE 1891 SYNTAX RbridgeNickname 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "The nickname of the distribution tree." 1896 REFERENCE 1897 "RFC 6325 section 4.5" 1898 ::= { rbridgeDtreeEntry 2 } 1900 rbridgeDtreeIngress OBJECT-TYPE 1901 SYNTAX TruthValue 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "Indicates whether this RBridge might choose this 1906 distribution tree to ingress a multi-destination frame." 1908 REFERENCE 1909 "RFC 6325 section 4.5" 1910 ::= { rbridgeDtreeEntry 3 } 1912 -- ---------------------------------------------------------- -- 1913 -- TRILL neighbor list 1914 -- ---------------------------------------------------------- -- 1916 rbridgeTrillMinMtuDesired OBJECT-TYPE 1917 SYNTAX Unsigned32 1918 MAX-ACCESS read-write 1919 STATUS current 1920 DESCRIPTION 1921 "The desired minimum acceptable inter-RBridge link MTU for 1922 the campus, that is, originatingLSPBufferSize. 1924 The value of this object MUST be retained across 1925 reinitializations of the management system." 1926 REFERENCE 1927 "RFC 6325 section 4.3" 1928 ::= { rbridgeTrill 1 } 1930 rbridgeTrillSz OBJECT-TYPE 1931 SYNTAX Unsigned32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "The minimum acceptable inter-Rbridge link size for the 1936 campus for the proper operation of TRILL IS-IS." 1937 REFERENCE 1938 "RFC 6325 section 4.3" 1939 ::= { rbridgeTrill 2 } 1941 rbridgeTrillMaxMtuProbes OBJECT-TYPE 1942 SYNTAX Unsigned32 (1..255) 1943 MAX-ACCESS read-write 1944 STATUS current 1945 DESCRIPTION 1946 "The number of failed MTU-probes before the RBridge 1947 concludes that a particular MTU is not supported by 1948 a neighbor. 1950 The value of this object MUST be retained across 1951 reinitializations of the management system." 1952 REFERENCE 1953 "RFC 6325 section 4.3" 1954 ::= { rbridgeTrill 3 } 1956 rbridgeTrillNbrTable OBJECT-TYPE 1957 SYNTAX SEQUENCE OF RbridgeTrillNbrEntry 1958 MAX-ACCESS not-accessible 1959 STATUS current 1960 DESCRIPTION 1961 "Information about this Rbridge's TRILL neighbors." 1962 REFERENCE 1963 "RFC 6325 section 4.4.2.1" 1964 ::= { rbridgeTrill 4 } 1966 rbridgeTrillNbrEntry OBJECT-TYPE 1967 SYNTAX RbridgeTrillNbrEntry 1968 MAX-ACCESS not-accessible 1969 STATUS current 1970 DESCRIPTION 1971 "List of information about this Rbridge's TRILL neighbors." 1972 INDEX { rbridgeTrillNbrMacAddr } 1973 ::= { rbridgeTrillNbrTable 1 } 1975 RbridgeTrillNbrEntry ::= 1976 SEQUENCE { 1977 rbridgeTrillNbrMacAddr 1978 MacAddress, 1979 rbridgeTrillNbrMtu 1980 Unsigned32, 1981 rbridgeTrillNbrFailedMtuTest 1982 TruthValue 1983 } 1985 rbridgeTrillNbrMacAddr OBJECT-TYPE 1986 SYNTAX MacAddress 1987 MAX-ACCESS not-accessible 1988 STATUS current 1989 DESCRIPTION 1990 "The MAC address of a neighbor of this RBridge." 1991 REFERENCE 1992 "RFC 6325 section 4.4.2.1" 1993 ::= { rbridgeTrillNbrEntry 1 } 1995 rbridgeTrillNbrMtu OBJECT-TYPE 1996 SYNTAX Unsigned32 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "MTU size for this neighbor for IS-IS communication purposes." 2001 REFERENCE 2002 "RFC 6325 section 4.3.2" 2003 ::= { rbridgeTrillNbrEntry 2 } 2005 rbridgeTrillNbrFailedMtuTest OBJECT-TYPE 2006 SYNTAX TruthValue 2007 MAX-ACCESS read-only 2008 STATUS current 2009 DESCRIPTION 2010 "If true, indicates that the neighbor's tested MTU is less 2011 than the minimum acceptable inter-bridge link MTU for the 2012 campus (1470)." 2013 REFERENCE 2014 "RFC 6325 section 4.3.1" 2015 ::= { rbridgeTrillNbrEntry 3 } 2017 -- ---------------------------------------------------------- -- 2018 -- Notifications for use by RBridges 2019 -- ---------------------------------------------------------- -- 2021 rbridgeBaseNewDrb NOTIFICATION-TYPE 2022 -- OBJECTS { } 2023 STATUS current 2024 DESCRIPTION 2025 "The RBridgeBaseNewDrb notification indicates that the 2026 sending agent has become the new Designated RBridge; the 2027 notification is sent by an RBridge soon after its election 2028 as the new DRB root, e.g., upon expiration of the Topology 2029 Change Timer, immediately subsequent to its election." 2030 ::= { rbridgeNotifications 1 } 2032 rbridgeBaseTopologyChange NOTIFICATION-TYPE 2033 -- OBJECTS { } 2034 STATUS current 2035 DESCRIPTION 2036 "The RBridgeBaseTopologyChange notification is sent by an 2037 RBridge when any of its configured ports transitions to/from 2038 Vlan-x designated forwarder. The notification is not sent 2039 if a newDrb trap is sent for the same transition." 2040 ::= { rbridgeNotifications 2 } 2042 -- Compliance and Group sections 2044 rbridgeGroup OBJECT IDENTIFIER ::= { rbridgeConformance 1 } 2046 rbridgeCompliances OBJECT IDENTIFIER ::= { rbridgeConformance 2 } 2048 -- ---------------------------------------------------------- -- 2049 -- Units of Conformance 2050 -- ---------------------------------------------------------- -- 2051 rbridgeBaseGroup OBJECT-GROUP 2052 OBJECTS { 2053 rbridgeBaseTrillVersion, 2054 rbridgeBaseNumPorts, 2055 rbridgeBaseForwardDelay, 2056 rbridgeBaseUniMultipathEnable, 2057 rbridgeBaseMultiMultipathEnable, 2058 rbridgeBaseAcceptEncapNonadj, 2059 rbridgeBaseNicknameNumber 2060 } 2061 STATUS current 2062 DESCRIPTION 2063 "A collection of objects providing basic control 2064 and status information for the RBridge." 2065 ::= { rbridgeGroup 1 } 2067 rbridgeBaseNicknameGroup OBJECT-GROUP 2068 OBJECTS { 2069 rbridgeBaseNicknamePriority, 2070 rbridgeBaseNicknameDtrPriority, 2071 rbridgeBaseNicknameType, 2072 rbridgeBaseNicknameRowStatus 2073 } 2074 STATUS current 2075 DESCRIPTION 2076 "A collection of objects providing basic control 2077 and status information for RBridge nicknames." 2078 ::= { rbridgeGroup 2 } 2080 rbridgeBasePortGroup OBJECT-GROUP 2081 OBJECTS { 2082 rbridgeBasePortIfIndex, 2083 rbridgeBasePortDisable, 2084 rbridgeBasePortTrunkPort, 2085 rbridgeBasePortAccessPort, 2086 rbridgeBasePortP2pHellos, 2087 rbridgeBasePortState, 2088 rbridgeBasePortDesiredDesigVlan, 2089 rbridgeBasePortDesigVlan, 2090 rbridgeBasePortInhibitionTime, 2091 rbridgeBasePortDisableLearning, 2092 rbridgeBasePortStpRoot, 2093 rbridgeBasePortStpRootChanges, 2094 rbridgeBasePortStpWiringCloset 2095 } 2096 STATUS current 2097 DESCRIPTION 2098 "A collection of objects providing basic control 2099 and status information for RBridge ports." 2100 ::= { rbridgeGroup 3 } 2102 rbridgeFdbGroup OBJECT-GROUP 2103 OBJECTS { 2104 rbridgeConfidenceNative, 2105 rbridgeConfidenceDecap, 2106 rbridgeConfidenceStatic, 2107 rbridgeUniFdbPort, 2108 rbridgeUniFdbNickname, 2109 rbridgeUniFdbConfidence, 2110 rbridgeUniFdbStatus 2111 } 2112 STATUS current 2113 DESCRIPTION 2114 "A collection of objects providing information 2115 about the Unicast Address Database." 2116 ::= { rbridgeGroup 4 } 2118 rbridgeFibGroup OBJECT-GROUP 2119 OBJECTS { 2120 rbridgeUniFibHopCount, 2121 rbridgeMultiFibPorts 2122 } 2123 STATUS current 2124 DESCRIPTION 2125 "A collection of objects providing information 2126 about the Unicast and Multicast FIBs." 2127 ::= { rbridgeGroup 5 } 2129 rbridgeVlanGroup OBJECT-GROUP 2130 OBJECTS { 2131 rbridgeVlanForwarderLosts, 2132 rbridgeVlanDisableLearning, 2133 rbridgeVlanSnooping, 2134 rbridgeVlanPortInhibited, 2135 rbridgeVlanPortForwarder, 2136 rbridgeVlanPortAnnouncing, 2137 rbridgeVlanPortDetectedVlanMapping 2138 } 2139 STATUS current 2140 DESCRIPTION 2141 "A collection of objects providing information 2142 about VLANs on the RBridge." 2143 ::= { rbridgeGroup 6 } 2145 rbridgePortCounterGroup OBJECT-GROUP 2146 OBJECTS { 2147 rbridgePortRpfCheckFails, 2148 rbridgePortHopCountExceeds, 2149 rbridgePortOptionDrops, 2150 rbridgePortTrillInFrames, 2151 rbridgePortTrillOutFrames 2152 } 2153 STATUS current 2154 DESCRIPTION 2155 "A collection of objects providing per-port 2156 counters for the RBridge." 2157 ::= { rbridgeGroup 7 } 2159 rbridgeEsadiGroup OBJECT-GROUP 2160 OBJECTS { 2161 rbridgeEsadiEnable, 2162 rbridgeEsadiConfidence, 2163 rbridgeEsadiDrbPriority, 2164 rbridgeEsadiDrb, 2165 rbridgeEsadiDrbHoldingTime, 2166 rbridgeEsadiRowStatus 2167 } 2168 STATUS current 2169 DESCRIPTION 2170 "A collection of objects providing information 2171 about ESADI instances on the RBridge." 2172 ::= { rbridgeGroup 8 } 2174 rbridgeSnoopingGroup OBJECT-GROUP 2175 OBJECTS { 2176 rbridgeSnoopingPortAddrType, 2177 rbridgeSnoopingPortAddr, 2178 rbridgeSnoopingAddrPorts 2179 } 2180 STATUS current 2181 DESCRIPTION 2182 "A collection of objects providing information 2183 about IP Multicast Snooping. This MIB requires 2184 support for only global IPv4 and IPv6 address 2185 types in rbridgeSnoopingPortAddrType and 2186 rbridgeSnoopingAddrType, so the length of 2187 rbridgeSnoopingPortAddr and rbridgeSnoopingAddr 2188 can be either 4 or 16 bytes." 2189 ::= { rbridgeGroup 9 } 2191 rbridgeDtreeGroup OBJECT-GROUP 2192 OBJECTS { 2193 rbridgeDtreePriority, 2194 rbridgeDtreeActiveTrees, 2195 rbridgeDtreeMaxTrees, 2196 rbridgeDtreeDesiredUseTrees, 2197 rbridgeDtreeNickname, 2198 rbridgeDtreeIngress 2199 } 2200 STATUS current 2201 DESCRIPTION 2202 "A collection of objects providing information 2203 about Distribution Trees." 2204 ::= { rbridgeGroup 10 } 2206 rbridgeTrillGroup OBJECT-GROUP 2207 OBJECTS { 2208 rbridgeTrillMinMtuDesired, 2209 rbridgeTrillSz, 2210 rbridgeTrillMaxMtuProbes, 2211 rbridgeTrillNbrMtu, 2212 rbridgeTrillNbrFailedMtuTest 2213 } 2214 STATUS current 2215 DESCRIPTION 2216 "A collection of objects providing information 2217 about TRILL neighbors." 2218 ::= { rbridgeGroup 11 } 2220 rbridgeNotificationGroup NOTIFICATION-GROUP 2221 NOTIFICATIONS { 2222 rbridgeBaseNewDrb, 2223 rbridgeBaseTopologyChange 2224 } 2225 STATUS current 2226 DESCRIPTION 2227 "A collection of objects describing notifications (traps)." 2228 ::= { rbridgeGroup 12 } 2230 -- ---------------------------------------------------------- -- 2231 -- Compliance Statement 2232 -- ---------------------------------------------------------- -- 2234 rbridgeCompliance MODULE-COMPLIANCE 2235 STATUS current 2236 DESCRIPTION 2237 "The compliance statement for support of RBridge 2238 services." 2240 MODULE 2241 MANDATORY-GROUPS { 2242 rbridgeBaseGroup, 2243 rbridgeBaseNicknameGroup, 2244 rbridgeBasePortGroup, 2245 rbridgeFdbGroup, 2246 rbridgeFibGroup, 2247 rbridgeVlanGroup, 2248 rbridgeDtreeGroup, 2249 rbridgeTrillGroup, 2250 rbridgeNotificationGroup 2251 } 2253 GROUP rbridgePortCounterGroup 2254 DESCRIPTION 2255 "Implementation of this group is optional." 2257 GROUP rbridgeEsadiGroup 2258 DESCRIPTION 2259 "Implementation of this group is optional." 2261 GROUP rbridgeSnoopingGroup 2262 DESCRIPTION 2263 "Implementation of this group is optional." 2265 ::= { rbridgeCompliances 1 } 2267 END 2269 8. Security Considerations 2271 This MIB relates to a system which will provide network connectivity 2272 and packet forwarding services. As such, improper manipulation of the 2273 objects represented by this MIB may result in denial of service to a 2274 large number of end-users. 2276 There are a number of management objects defined in this MIB module 2277 with a MAX-ACCESS clause of read-write and/or read-create. Such 2278 objects may be considered sensitive or vulnerable in some network 2279 environments. The support for SET operations in a non-secure 2280 environment without proper protection can have a negative effect on 2281 network operations. These tables and objects and their 2282 sensitivity/vulnerability are described below. 2284 The following tables and objects in the RBRIDGE-MIB can be 2285 manipulated to interfere with the operation of RBridges: 2287 o rbridgeBaseUniMultipathEnable affects the ability of the RBridge to 2288 multipath unicast traffic, and rbridgeBaseMultiMultipathEnable 2289 affects the ability of the Rbridge to multipath multi-destination 2290 traffic. 2292 o rbridgeBasePortTable contains a number of objects that may affect 2293 network connectivity. Actions that may be triggered by manipulating 2294 objects in this table include disabling of an RBridge port; 2295 discarding of native packets; disabling learning and others. 2297 o rbridgeEsadiTable contains objects that affect the operation of the 2298 ESADI protocol used for learning, and manipulation of the objects 2299 contained therein can be used to confuse the learning ability of 2300 Rbridges. 2302 o rbridgeDtreePriority can affect computation of distribution trees 2303 within an Rbridge campus, thereby affecting forwarding of multi- 2304 destination traffic. 2306 o rbridgeTrillMinMtuDesired can affect the size of packets being used 2307 to exchange information between RBridges. 2309 Some of the readable objects in this MIB module (i.e., objects with a 2310 MAX-ACCESS other than not-accessible) may be considered sensitive or 2311 vulnerable in some network environments. It is thus important to 2312 control even GET and/or NOTIFY access to these objects and possibly 2313 to even encrypt the values of these objects when sending them over 2314 the network via SNMP. For example, access to network topology and 2315 Rbridge attributes can reveal information that should not be 2316 available to all users of the network. 2318 SNMP versions prior to SNMPv3 did not include adequate security. Even 2319 if the network itself is secure (for example by using IPsec), there 2320 is no control as to who on the secure network is allowed to access 2321 and GET/SET (read/change/create/delete) the objects in this MIB 2322 module. 2324 It is RECOMMENDED that implementers consider the security features as 2325 provided by the SNMPv3 framework (see [RFC3410], section 8), 2326 including full support for the SNMPv3 cryptographic mechanisms (for 2327 authentication and privacy). 2329 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2330 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2331 enable cryptographic security. It is then a customer/operator 2332 responsibility to ensure that the SNMP entity giving access to an 2333 instance of this MIB module is properly configured to give access to 2334 the objects only to those principals (users) that have legitimate 2335 rights to indeed GET or SET (change/create/delete) them. 2337 For other RBridge security considerations see [RFC6325]. 2339 9. IANA Considerations 2341 The MIB module in this document uses the following IANA-assigned 2342 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2344 Descriptor OBJECT IDENTIFIER value 2346 ---------- ----------------------- 2348 rbridgeMIB { mib-2 xxx } 2350 Editor's Note (to be removed prior to publication): the IANA is 2351 requested to assign a value for "xxx" under the 'mib-2' subtree and 2352 to record the assignment in the SMI Numbers registry. When the 2353 assignment has been made, the RFC Editor is asked to replace "XXX" 2354 (here and in the MIB module) with the assigned value and to remove 2355 this note. 2357 10. Contributors 2359 The authors would like to acknowledge the contributions of Donald 2360 Eastlake, Radia Perlman, Anoop Ghanwani, Dan Romascanu, Mahesh Akula 2361 and Joan Cucchiara. 2363 11. References 2365 11.1 Normative References 2367 [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. 2368 Ghanwani, "Routing Bridges (RBridges): Base Protocol 2369 Specification", RFC 6325, July 2011. 2371 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2372 Requirement Levels", BCP 14, RFC 2119, March 1997. 2374 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2375 Schoenwaelder, Ed., "Structure of Management 2376 Information Version 2 (SMIv2)", STD 58, RFC 2578, 2377 April 1999. 2379 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2381 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2382 STD 58, RFC 2579, April 1999. 2384 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 2385 Group MIB", RFC 2863, June 2000. 2387 [RFC4188] Norseth, K. and E. Bell, "Definitions of Managed 2388 Objects for Bridges", RFC 4188, September 2005. 2390 [RFC4363] Levi, D. and D. Harrington, "Definitions of Managed 2391 Objects for Bridges with Traffic Classes, Multicast 2392 Filtering, and Virtual LAN Extensions", RFC 4363, 2393 January 2006. 2395 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2396 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2397 April 1999. 2399 [RFC4444] Parker, J., "Management Information Base for 2400 Intermediate System to Intermediate System (IS-IS)", 2401 RFC 4444, April 2006. 2403 [802.1Q-2005] Institute of Electrical and Electronics Engineers, 2404 "Local and Metropolitan Area Networks: Virtual Bridged 2405 Local Area Networks", IEEE 802.1Q, May 2006. 2407 11.2 Informative References 2409 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2410 "Introduction and Applicability Statements for 2411 Internet-Standard Management Framework", RFC 3410, 2412 December 2002. 2414 [RFC5556] Touch, J. and R. Perlman, "Transparent Interconnection 2415 of Lots of Links (TRILL): Problem and Applicability 2416 Statement", RFC 5556, May 2009. 2418 [RFC4663] Harrington, D., "Transferring MIB Work from IETF 2419 Bridge MIB WG to IEEE 802.1 WG", RFC 4663, September 2420 2006. 2422 Appendix A. Change Log 2424 Note to RFC Editor: Please remove this appendix before publication as 2425 an RFC. 2427 Changes from -06 to -07 (incorporating further IETF and IESG 2428 feedback): 2430 1. Changed RBridgeBasePortEntry to RbridgeBasePortEntry 2431 2. rbridgeSnoopingAddrType, rbridgeSnoopingAddr, 2432 rbridgeSnoopingPortAddrType, rbridgeSnoopingPortAddr: Added text in 2433 Description as well as corresponding compliance statement saying that 2434 only IPv4 and IPv6 addresses are supported, thus limiting the length 2435 of the address to 4 or 16. This allows the INDEX of to be of a legal 2436 length. 2437 3. Changed IMPORT from RFC2233 to RFC2863. 2438 4. Moved scalar rbridgeBaseNicknameNumber definition to just above 2439 the rbridgeBaseNicknameTable. Also clarified further the meaning of 2440 rbridgeBaseNicknameNumber. 2441 5. rbridgeVlanDisableLearning: Added text in DESCRIPTION clarifying 2442 what true and false mean. 2443 6. rbridgeEsadiEnable: Added text in DESCRIPTION clarifying what true 2444 and false mean. 2445 7. rbridgeEsadiConfidence: Extended range to 255. 2446 8. Changed some references to IS-IS MIB to ISIS-MIB. 2447 9. Updated all REFERENCE clauses to refer to RFC 6325 instead of 2448 RBridge. 2449 10. rbridgeBaseForwardDelay: Specified range 2450 11. rbridgeUniFdbPort, rbridgeUniFibPort, rbridgeDtreePriority: 2451 Changed SYNTAX to Unsigned32 (from Integer32) 2452 12. rbridgeUniFdbNick: Changed to rbridgeUniFdbNickname 2453 13. rbridgeUniFdbNick: Changed to rbridgeUniFdbNickname 2454 14. rbridgeDtreeNick: Changed to rbridgeDtreeNickname 2455 15. rbridgeUniFdbConfidence: Extended range to 255. 2456 16. Changed any counter name that did not end with "s" to end with 2457 "s" 2458 17. Added text to counter table re-stating that it extends relevant 2459 counters in Bridge MIB 2460 18. rbridgeVlanPortTable: Changed indexing to port, VLAN (instead of 2461 VLAN, port) 2462 19. Removed text in description of notifications saying that their 2463 implementation is optional. 2465 Changes from -07 to -08: 2466 1. Updated section 6.7 to provide guidance on ISIS-MIB implementation 2467 for TRILL switches without the use of MUST language. 2469 Authors' Addresses 2471 Anil Rijhsinghani 2472 Hewlett-Packard Networking 2473 153 Taylor St 2474 Littleton, MA 2475 USA 2477 Phone: +1 508 323 1251 2478 EMail: anil@charter.net 2480 Kate Zebrose 2481 H.W. Embedded 2482 26 Josephine Ave 2483 Somerville, MA 2484 USA 2486 Phone: +1 617 840 9673 2487 EMail: zebrose@alum.mit.edu 2489 Copyright and License Notice 2491 Copyright (c) 2012 IETF Trust and the persons identified as the 2492 document authors. All rights reserved. 2494 This document is subject to BCP 78 and the IETF Trust's Legal 2495 Provisions Relating to IETF Documents 2496 (http://trustee.ietf.org/license-info) in effect on the date of 2497 publication of this document. Please review these documents 2498 carefully, as they describe your rights and restrictions with respect 2499 to this document. Code Components extracted from this document must 2500 include Simplified BSD License text as described in Section 4.e of 2501 the Trust Legal Provisions and are provided without warranty as 2502 described in the Simplified BSD License.