idnits 2.17.1 draft-ietf-ipoib-channel-adapter-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 8 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 293 has weird spacing: '... of CAs from...' == Line 735 has weird spacing: '... before compa...' == Line 978 has weird spacing: '... rights migh...' == Line 979 has weird spacing: '...that it has ...' == Line 981 has weird spacing: '...ack and stan...' == (1 more instance...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2002) is 7864 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) == Unused Reference: 'IBTC' is defined on line 1064, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. 'IBTAArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'IBTC' Summary: 15 errors (**), 0 flaws (~~), 10 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Sean Harnedy 2 InfiniSwitch Corp. 3 Expiration Date: April 2003 October 2002 5 Definitions of Managed Objects for 6 Infiniband Channel Adapters (CA) 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other documents 22 at any time. It is inappropriate to use Internet-Drafts as 23 reference material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Copyright Notice 32 Copyright (C) The Internet Society (2001). All Rights Reserved. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) 37 for use with network management protocols in the Internet community. 38 In particular, it defines objects for managing InfiniBand Channel 39 Adapters (CA). 41 Table of Contents 43 1. Introduction ................................................ 2 44 2. The SNMP Management Framework ............................... 2 45 3. Conventions used in this document ........................... 3 46 4. Structure of the MIB ........................................ 3 47 4.1. Overview .................................................. 3 48 4.2. Discussion of MIB Groups .................................. 3 49 4.3. The CA MIB Objects ........................................ 3 50 4.3.1. The General Channel Adapter Info Group .................. 4 51 4.3.2. The Channel Adapter Attributes Info Group ............... 4 52 4.3.3. The Channel Adapter Port Attributes and Gid Info Group .. 4 53 4.4. The CA Notifications Group ................................ 4 54 4.5. The CA Conformance Group .................................. 4 55 4.5.1. CA Compliance Groups .................................... 4 56 5. IPOIB CA MIB Definitions .................................... 4 57 6. Revision History ............................................ 19 58 6.1 Changes from . 19 59 6.2 Changes from . 19 60 6.3 Changes from . 19 61 7. Security Considerations ..................................... 20 62 8. Intellectual Property ....................................... 20 63 9. References .................................................. 20 64 10. Author's Address ........................................... 22 66 1. Introduction 68 This document defines a MIB for InfiniBand Channel Adpaters (CA). 70 The Infiniband Architecture[IBTAArch] (IBA) is defined by the 71 Infiniband Trade Association. Infiniband is designed to provide low 72 latency, high bandwidth interconnect in a computing environment. This 73 document will define the objects related to managing a specific class 74 of InfiniBand nodes called Channel Adapters. 76 A Channel Adapter (CA) is the end-point for IBA packets that are sent 77 and received over the IBA switching fabric. There are two types of 78 CAs: Host Channel Adapters (HCA) and Target Channel Adapters (TCA). 79 Typically, HCAs are used by host processors and TCAs are used by I/O 80 adapters to connect to the IBA switch fabric. The HCA supports the 81 IBA Verbs layer as the transport layer interface, while the TCA often 82 uses its own implementation-specific interface to the transport layer. 84 2. The SNMP Management Framework 86 The SNMP Management Framework presently consists of five major 87 components: 89 o An overall architecture, described in RFC 2571[RFC2571]. 91 o Mechanisms for describing and naming objects and events for 92 the purpose of management. The first version of this 93 Structure of Management Information (SMI) is called SMIv1 94 and described in STD 16, RFC 1155[RFC1155], STD 16, RFC 1212 95 [RFC1212] and RFC 1215 [RFC1215]. The second version, 96 called SMIv2, is described in STD 58, RFC 2578[RFC2578], STD 97 58, RFC 2579[RFC2579], and STD 58, RFC 2580[RFC2580]. 99 o Message protocols for transferring management information. 100 The first version of the SNMP message protocol is called 101 SNMPv1 and described in STD 15, RFC 1157[RFC1157]. A second 102 version of the SNMP message protocol, which is not an 103 Internet standards track protocol, is called SNMPv2c and 104 described in RFC 1901[RFC1901] and RFC 1906[RFC1906]. The 105 third version of the message protocol is called SNMPv3 and 106 described in RFC 1906[RFC1906], RFC 2572[RFC2572] and RFC 107 2574[RFC2574]. 109 o Protocol operations for accessing management information. 110 The first set of protocol operations and associated PDU 111 formats is described in STD 15, RFC 1157[RFC1157]. A second 112 set of protocol operations and associated PDU formats is 113 described in RFC 1905[RFC1905]. 115 o A set of fundamental applications described in RFC 116 2573[RFC2573] and the view-based access control mechanism 117 described in RFC 2575[RFC2575]. 119 A more detailed introduction to the current SNMP Management 120 Framework can be found in RFC 2570[RFC2570]. 122 Managed objects are accessed via a virtual information store, 123 termed the Management Information Base or MIB. Objects in the MIB 124 are defined using the mechanisms defined in the SMI. 126 This memo specifies a MIB module that is compliant to the SMIv2. 127 A MIB conforming to the SMIv1 can be produced through the 128 appropriate translations. The resulting translated MIB must be 129 semantically equivalent, except where objects or events are 130 omitted because no translation is possible (use of Counter64). 131 Some machine readable information in SMIv2 will be converted into 132 textual descriptions in SMIv1 during the translation process. 133 However, this loss of machine readable information is not 134 considered to change the semantics of the MIB. 136 3. Conventions used in this document 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [RFC2119]. 142 4. Structure of the MIB 144 This section describes the structure of the IPOIB CA MIB. 146 4.1. Overview 148 The SNMP management of the CA involves the monitoring of key channel 149 adapter attributes. 151 4.2. Discussion of MIB Groups 153 The CA MIB is divided into two basic groups: MIB objects and the 154 conformance section. 156 4.3. The CA MIB Objects 158 The CA MIB objects correlate to the set of Channel Adapter attributes. 159 These attributes are organized into three major CA MIB groups. 160 These are: The General Channel Adpater Info Group, The Channel Adapter 161 Attributes Info Group, and the Channel Adpater Port Attributes and 162 Gid Info Group. 164 4.3.1. The General Channel Adapter Info Group 166 This group provides general information common to any InfiniBand 167 network etnity that contains CAs. This includes distinguishing 168 between the HCA and the TCA, displaying the node GUIDs, and showing 169 the number of ports on each CA. 171 4.3.2. The Channel Adapter Attributes Info Group 173 This group provides more specific information about the CAs on a 174 network entity. This includes various attribute flags, transport 175 service support, and other CA characteristics. 177 4.3.3. The Channel Adapter Port Attributes and Gid Info Group 179 This group provides information about the CA ports. This includes 180 the type of physical interfaces supported, other port attributes, 181 and a table containing the port GIDs. 183 4.4. The CA Notifications Group 185 The CA MIB currently does not define a Notifications Group. 187 4.5. The CA Conformance Group 189 The CA Conformance Group lists the possible compliances for various 190 types of InfiniBand nodes that contain channel adapters. Currently, 191 two types of compliance are defined: basic and full. The units of 192 conformance which define the constituent object groups are also 193 listed. 195 4.5.1. CA Compliance Groups 197 The Compliance Groups list acceptable MIB implementation requirements. 199 5. IPOIB CA MIB Definitions 201 IB-CA-MIB DEFINITIONS ::= BEGIN 203 IMPORTS 204 MODULE-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI 205 TruthValue FROM SNMPv2-TC 206 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 207 infinibandMIB, IbDataPort FROM IB-TC-MIB; 209 ibCaMIB MODULE-IDENTITY 210 LAST-UPDATED "200210261200Z" -- October 26, 2002 211 ORGANIZATION "IETF IP Over IB Working Group 212 Email: ipoib@ietf.org" 213 CONTACT-INFO 214 "Sean Harnedy (sharnedy@infiniswitch.com) 215 InfiniSwitch Corporation" 216 DESCRIPTION 217 "This module contains managed object definitions for 218 the instrumentation for an InfiniBand Channel Adpater (CA)." 219 REVISION 220 "200210261200Z" 221 DESCRIPTION 222 "Made scalar groups into tables to model multiple CAs per 223 Managed System Element (-03)." 224 REVISION 225 "200206231200Z" 226 DESCRIPTION 227 "Removed ibCaSupportsPKeyCheck object; corrected ibCaPortGuid 228 DESCRIPTION (-02)." 229 REVISION 230 "200205101200Z" 231 DESCRIPTION 232 "Updated IMPORTS section (-01)." 233 REVISION 234 "200203291200Z" 235 DESCRIPTION 236 "Initial IETF Draft Revision (-00)." 237 ::= { infinibandMIB 4 } 239 --**************************************************************** 240 -- Object Indentifiers for the IPOIB CA MIB 241 --**************************************************************** 243 ibCaObjects OBJECT IDENTIFIER ::= { ibCaMIB 1 } 244 ibCaConformance OBJECT IDENTIFIER ::= { ibCaMIB 2 } 246 --**************************************************************** 247 -- General Channel Adapter Info Group 248 -- 249 -- DESCRIPTION: This group contains a table that describes 250 -- general information about the Channel Adpaters present in 251 -- this Managed System Element. 252 --**************************************************************** 254 ibCaGeneralInfo OBJECT IDENTIFIER ::= { ibCaObjects 1 } 256 --**************************************************************** 257 -- Channel Adapters General Information Table 258 --**************************************************************** 260 ibCaGeneralInfoTable OBJECT-TYPE 261 SYNTAX SEQUENCE OF IbCaGeneralInfoEntry 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "A table containing general information about the Channel 266 Adapters on this network entity." 267 ::= { ibCaGeneralInfo 1 } 269 ibCaGeneralInfoEntry OBJECT-TYPE 270 SYNTAX IbCaGeneralInfoEntry 271 MAX-ACCESS not-accessible 272 STATUS current 273 DESCRIPTION 274 "A conceptual row of the ibCaGeneralInfoTable containing 275 information about the general characteristics of each 276 Channel Adpater on this network entity." 277 INDEX { ibCaIndex } 278 ::= { ibCaGeneralInfoTable 1 } 280 IbCaGeneralInfoEntry ::= SEQUENCE { 281 ibCaIndex Integer32, 282 ibCaType Integer32, 283 ibCaNodeGuid OCTET STRING, 284 ibCaNumPorts Integer32 285 } 287 ibCaIndex OBJECT-TYPE 288 SYNTAX Integer32(1..254) 289 MAX-ACCESS not-accessible 290 STATUS current 291 DESCRIPTION 292 "Index that identifies the specific CA on this network 293 entity. The index is defined for a range of CAs from 294 1 to N, where N can have a maximum value of 254." 295 ::= { ibCaGeneralInfoEntry 1 } 297 ibCaType OBJECT-TYPE 298 SYNTAX INTEGER { 299 unknown(1), 300 hca(2), -- host CA 301 tca(3) -- terminal CA 302 } 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "Type of Channel Adapter: either a Host Channel Adpater (HCA), 307 or a Target Channel Adapter (TCA). If the type of CA cannot 308 be determined, the unknown(1) value is returned." 309 REFERENCE 310 "InfiniBand Architecture Release 1.0.a. Vol 1. 311 Section 17.1." 312 ::= { ibCaGeneralInfoEntry 2 } 314 ibCaNodeGuid OBJECT-TYPE 315 SYNTAX OCTET STRING (SIZE(8)) 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The GUID of this CA. All ports on the same node shall 320 report the same CA node GUID value. This provides a 321 means for uniquely identifing a CA node within a 322 subnet and helps to determine the co-location of 323 the ports." 324 REFERENCE 325 "InfiniBand Architecture Release 1.0.a. Vol 1. 326 Section 17.2.5." 327 ::= { ibCaGeneralInfoEntry 3 } 329 ibCaNumPorts OBJECT-TYPE 330 SYNTAX Integer32(1..254) 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "Number of physical IB data ports on this Channel Adapter. Ports 335 are numbered starting from 1. If there is more than one port, 336 the ports are numbered sequentially." 337 REFERENCE 338 "InfiniBand Architecture Release 1.0.a. Vol 1. 339 Section 17.2.1.3; Table 254 Port Attributes & Functions." 340 ::= { ibCaGeneralInfoEntry 4 } 342 --**************************************************************** 343 -- Channel Adapter Attributes Info Group 344 -- 345 -- DESCRIPTION: This group contains a table that describes more 346 -- specific attributes about each CA on the network entity. 347 --**************************************************************** 349 ibCaAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 2 } 351 --**************************************************************** 352 -- Channel Adapter Attributes Table 353 --**************************************************************** 355 ibCaAttributeTable OBJECT-TYPE 356 SYNTAX SEQUENCE OF IbCaAttributeEntry 357 MAX-ACCESS not-accessible 358 STATUS current 359 DESCRIPTION 360 "A table containing information about the Channel Adapter 361 attributes on this network entity." 362 ::= { ibCaAttrInfo 1 } 364 ibCaAttributeEntry OBJECT-TYPE 365 SYNTAX IbCaAttributeEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "A conceptual row of the ibCaAttributeTable containing 370 information about the general characteristics of each 371 Channel Adpater on this network entity." 372 INDEX { ibCaIndex } 373 ::= { ibCaAttributeTable 1 } 375 IbCaAttributeEntry ::= SEQUENCE { 376 ibCaHasReliableConnection TruthValue, 377 ibCaHasUnreliableConnection TruthValue, 378 ibCaHasReliableDatagram TruthValue, 379 ibCaHasUnreliableDatagram TruthValue, 380 ibCaSupportsAtomicOperations TruthValue, 381 ibCaSupportsOtherOperations TruthValue, 382 ibCaSupportsSolicitedEvents TruthValue, 383 ibCaPathMtuSetSupport TruthValue, 384 ibCaGenEndToEndFlowControl TruthValue, 385 ibCaSupportsMulticast TruthValue, 386 ibCaSupportsAutoPathMigration TruthValue, 387 ibCaSupportsMemoryProtection TruthValue, 388 ibCaSupportsLoopback TruthValue, 389 ibCaSupportsSubnetManager TruthValue 390 } 392 ibCaHasReliableConnection OBJECT-TYPE 393 SYNTAX TruthValue 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "Flag that indicates whether this CA supports 398 Reliable Connection (RC) transport service." 399 REFERENCE 400 "InfiniBand Architecture Release 1.0.a. Vol 1. 401 Section 17.2.2; Table 255 Channel Adapter Attributes." 402 ::= { ibCaAttributeEntry 1 } 404 ibCaHasUnreliableConnection OBJECT-TYPE 405 SYNTAX TruthValue 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "Flag that indicates whether this CA supports 410 Unreliable Connection (UC) transport service." 411 REFERENCE 412 "InfiniBand Architecture Release 1.0.a. Vol 1. 413 Section 17.2.2; Table 255 Channel Adapter Attributes." 414 ::= { ibCaAttributeEntry 2 } 416 ibCaHasReliableDatagram OBJECT-TYPE 417 SYNTAX TruthValue 418 MAX-ACCESS read-only 419 STATUS current 420 DESCRIPTION 421 "Flag that indicates whether this CA supports 422 Reliable Datagram (RD) transport service." 423 REFERENCE 424 "InfiniBand Architecture Release 1.0.a. Vol 1. 425 Section 17.2.2; Table 255 Channel Adapter Attributes." 426 ::= { ibCaAttributeEntry 3 } 428 ibCaHasUnreliableDatagram OBJECT-TYPE 429 SYNTAX TruthValue 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "Flag that indicates whether this CA supports 434 Unreliable Datagram (UD) transport service." 435 REFERENCE 436 "InfiniBand Architecture Release 1.0.a. Vol 1. 437 Section 17.2.2; Table 255 Channel Adapter Attributes." 438 ::= { ibCaAttributeEntry 4 } 440 ibCaSupportsAtomicOperations OBJECT-TYPE 441 SYNTAX TruthValue 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "Flag that indicates whether this CA supports 446 atomic operations. An atomic operation is an operation 447 that is guaranteed to finish without having another 448 operation alter the results once the atomic operation 449 has been initiated." 450 REFERENCE 451 "InfiniBand Architecture Release 1.0.a. Vol 1. 452 Section 17.2.2; Table 255 Channel Adapter Attributes." 453 ::= { ibCaAttributeEntry 5 } 455 ibCaSupportsOtherOperations OBJECT-TYPE 456 SYNTAX TruthValue 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "Flag that indicates whether this CA supports 461 all of the other operations (excluding atomic operations) 462 defined for a particular supported transport service." 463 REFERENCE 464 "InfiniBand Architecture Release 1.0.a. Vol 1. 465 Section 17.2.2; Table 255 Channel Adapter Attributes." 466 ::= { ibCaAttributeEntry 6 } 468 ibCaSupportsSolicitedEvents OBJECT-TYPE 469 SYNTAX TruthValue 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "Flag that indicates whether this CA supports the 474 generation and reception of solicited events. A solicited 475 event is a feature by which a queue pair consumer on a 476 CA can cause an event to be generated at the destination 477 when its message is received." 478 REFERENCE 479 "InfiniBand Architecture Release 1.0.a. Vol 1. 480 Section 17.2.2; Table 255 Channel Adapter Attributes. 481 and Section 9.2.3 Solicited Event (SE) - 1 bit." 482 ::= { ibCaAttributeEntry 7 } 484 ibCaPathMtuSetSupport OBJECT-TYPE 485 SYNTAX INTEGER { 486 mtu256(1), 487 mtu256n512(2), 488 mtu256n512n1024(3), 489 mtu256n512n1024n2048(4), 490 mtu256n512n1024n2048n4096(5) 491 } 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "Set of MTU values (in bytes) supported by this CA for all 496 transport service classes. The Maximum Transfer Unit is the 497 largest size allowable for the packet payload." 498 REFERENCE 499 "InfiniBand Architecture Release 1.0.a. Vol 1. 500 Section 17.2.2; Table 255 Channel Adapter Attributes." 501 ::= { ibCaAttributeEntry 8 } 503 ibCaGenEndToEndFlowControl OBJECT-TYPE 504 SYNTAX TruthValue 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "Flag that indicates whether this CA supports 509 the generation of end-to-end flow control. End-to-end 510 flow control is a mechanism that prevents sending messages 511 when the destination does not have adequate receive buffers 512 to receive the message." 513 REFERENCE 514 "InfiniBand Architecture Release 1.0.a. Vol 1. 515 Section 17.2.2; Table 255 Channel Adapter Attributes." 516 ::= { ibCaAttributeEntry 9 } 518 ibCaSupportsMulticast OBJECT-TYPE 519 SYNTAX TruthValue 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "Flag that indicates whether this CA supports multicast 524 operations. Multicast is the ability to deliver a single 525 packet to multiple ports." 526 REFERENCE 527 "InfiniBand Architecture Release 1.0.a. Vol 1. 528 Section 17.2.2; Table 255 Channel Adapter Attributes." 529 ::= { ibCaAttributeEntry 10 } 531 ibCaSupportsAutoPathMigration OBJECT-TYPE 532 SYNTAX TruthValue 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "Flag that indicates whether this CA supports 537 automatic path migration. Automatic path migration 538 is the process by which a CA (on a per QP basis) 539 signals another CA to cause path migration to a 540 preset alternate path." 541 REFERENCE 542 "InfiniBand Architecture Release 1.0.a. Vol 1. 543 Section 17.2.2; Table 255 Channel Adapter Attributes." 544 ::= { ibCaAttributeEntry 11 } 546 ibCaSupportsMemoryProtection OBJECT-TYPE 547 SYNTAX TruthValue 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION 551 "Flag that indicates whether this CA supports InfiniBand 552 memory management protection mechanisms." 553 REFERENCE 554 "InfiniBand Architecture Release 1.0.a. Vol 1. 555 Section 17.2.2; Table 255 Channel Adapter Attributes 556 and Section 10.6 Memory Management." 557 ::= { ibCaAttributeEntry 12 } 559 ibCaSupportsLoopback OBJECT-TYPE 560 SYNTAX TruthValue 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "Flag that indicates whether this CA supports 565 loopback operations. Loopback support allows for the 566 sending and receiving of self-addressed packets that 567 do not go out on the wire. If this feature is supported, 568 self-addressed packets must work, even if no switch is 569 present." 571 REFERENCE 572 "InfiniBand Architecture Release 1.0.a. Vol 1. 573 Section 17.2.2; Table 255 Channel Adapter Attributes." 574 ::= { ibCaAttributeEntry 13 } 576 ibCaSupportsSubnetManager OBJECT-TYPE 577 SYNTAX TruthValue 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "Flag that indicates whether this CA supports 582 a Subnet Manager (SM) instance." 583 REFERENCE 584 "InfiniBand Architecture Release 1.0.a. Vol 1. 585 Section 17.2.5." 586 ::= { ibCaAttributeEntry 14 } 588 --**************************************************************** 589 -- Channel Adapter Port Attributes and GID Info Group 590 -- 591 -- DESCRIPTION: This group contains information about the CA ports 592 -- on the network entity and the GID table associated with each 593 -- port. 594 --**************************************************************** 596 ibCaPortAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 3 } 598 --**************************************************************** 599 -- Channel Adapter Port Attribute Table 600 --**************************************************************** 602 ibCaPortAttributeTable OBJECT-TYPE 603 SYNTAX SEQUENCE OF IbCaPortAttributeEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "A table containing information about the Channel Adapter 608 port attributes on this network entity." 609 ::= { ibCaPortAttrInfo 1 } 611 ibCaPortAttributeEntry OBJECT-TYPE 612 SYNTAX IbCaPortAttributeEntry 613 MAX-ACCESS not-accessible 614 STATUS current 615 DESCRIPTION 616 "A conceptual row of the ibCaPortAttributeTable containing 617 information about the general characteristics of each 618 Channel Adpater port on this network entity." 619 INDEX { ibCaIndex, ibCaPortIndex } 620 ::= { ibCaPortAttributeTable 1 } 622 IbCaPortAttributeEntry ::= SEQUENCE { 623 ibCaPortIndex IbDataPort, 624 ibCaPortGuid OCTET STRING, 625 ibCaPhysicalInterface INTEGER, 626 ibCaSupportsStaticRateControl TruthValue, 627 ibCaInterpacketDelayValue INTEGER, 628 ibCaSupportsMultipathing TruthValue, 629 ibCaValidatesInPktDlid TruthValue, 630 ibCaMaxGidsPerPort Integer32 631 } 633 ibCaPortIndex OBJECT-TYPE 634 SYNTAX IbDataPort 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION 638 "Index that identifies the InfiniBand data port. The IBA 639 defines a range of valid data ports from 1 to N, where 640 N can have a maximum value of 254 for an IBA switch." 641 ::= { ibCaPortAttributeEntry 1 } 643 ibCaPortGuid OBJECT-TYPE 644 SYNTAX OCTET STRING (SIZE(8)) 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "The GUID of this CA port. All ports on the same CA shall 649 report a unique ibCaPortGuid value. This provides a means 650 for uniquely identifing a CA on a node within a subnet 651 and helps to determine the co-location of the ports." 652 REFERENCE 653 "InfiniBand Architecture Release 1.0.a. Vol 1. 654 Section 17.2.5." 655 ::= { ibCaPortAttributeEntry 2 } 657 ibCaPhysicalInterface OBJECT-TYPE 658 SYNTAX INTEGER { 659 cable(1), 660 fiber(2), 661 backplane(3) 662 } 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "The physical interface for this CA. When the value 667 is cable(1), the CA supports a cable connector physical 668 interface. This physical attach point is defined for use 669 with copper cables. When the value is fiber(2), the CA 670 supports a fiber connector physical interface. This 671 physical attach point is defined for use with optical 672 cables. When the value is backplane(3), the CA supports 673 a backplane connector physical interface. This physical 674 attach point is defined for accepting a specified form 675 factor that houses the channel adapter." 676 REFERENCE 677 "InfiniBand Architecture Release 1.0.a. Vol 1. 678 Section 17.2.1.3 Port Attributes and Functions; 679 Vol 2. 3.1 Introduction (Physical Layer Overview)." 680 ::= { ibCaPortAttributeEntry 3 } 682 ibCaSupportsStaticRateControl OBJECT-TYPE 683 SYNTAX TruthValue 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "Flag that indicates whether this CA supports static 688 rate control. Static rate controls are required for 689 all IB ports that support a data rate over 2.5 Gbps." 690 REFERENCE 691 "InfiniBand Architecture Release 1.0.a. Vol 1. 692 Section 17.2.6 Static Rate Control." 693 ::= { ibCaPortAttributeEntry 4 } 695 ibCaInterpacketDelayValue OBJECT-TYPE 696 SYNTAX INTEGER { 697 unknown(1), 698 zero(2), -- 100% 699 three(3), -- 25% 700 two(4), -- 33% 701 eleven(5) -- 8% 702 } 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "Interpacket Delay Value (IPD) supported for CAs that have 707 static rate control (i.e., the ibCaSupportsStaticRateControl 708 object must have a value of true(1) for this object to 709 contain a valid value; Otherwise, unknown(1) is returned). 710 The IPD allows for the slowing of the packet rate for all 711 of the standard link rates. 713 An ibCaInterpacketDelayValue of zero(2) is required for all CAs 714 that support static rate control. An ibCaInterpacketDelayValue 715 of three(3) is required by CAs that support 1 GBs or higher 716 link rate. An ibCaInterpacketDelayValue of two(4) is required by 717 CAs that support 3 Gbps or higher link rates and, an 718 ibCaInterpacketDelayValue of eleven(5) is required by CAs that 719 also support 3 Gbps or higher link rates." 720 REFERENCE 721 "InfiniBand Architecture Release 1.0.a. Vol 1. 722 Section 17.2.6 Static Rate Control, and Table 256 723 Static Rate Control IPD Values." 724 ::= { ibCaPortAttributeEntry 5 } 726 ibCaSupportsMultipathing OBJECT-TYPE 727 SYNTAX TruthValue 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "Flag that indicates whether this CA supports multipathing. 732 The CA link layer port checks the unicast DLID in the 733 received packet for validity by masking the number of low 734 order bits indicated by the LID Mask Control field (LMC) 735 before comparing the DLID to its assigned LID if this 736 object is true(1)." 737 REFERENCE 738 "InfiniBand Architecture Release 1.0.a. Vol 1. 739 Section 7.2.1.3. and Table 255; Also, Section 7.11.1 740 Multipathing Requirements on End Node." 741 ::= { ibCaPortAttributeEntry 6 } 743 ibCaValidatesInPktDlid OBJECT-TYPE 744 SYNTAX TruthValue 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "Flag that indicates whether this CA supports the validation 749 of incoming packet DLIDs, and if the GRH is present, the 750 DGID." 751 REFERENCE 752 "InfiniBand Architecture Release 1.0.a. Vol 1. 753 Section 7.2.1.3. and Table 255." 754 ::= { ibCaPortAttributeEntry 7 } 756 ibCaMaxGidsPerPort OBJECT-TYPE 757 SYNTAX Integer32(1..65535) 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "Maximum number of GIDs per port. The maximum number of 762 unicast GIDs supported per CA port is implementation specific. 763 Each port will support at least one (1) GID." 764 REFERENCE 765 "InfiniBand Architecture Release 1.0.a. Vol 1. 766 Section 7.2.1.3. and Table 255." 767 ::= { ibCaPortAttributeEntry 8 } 769 --**************************************************************** 770 -- Channel Adapter Port Global Identifier (GID) Table 771 --**************************************************************** 773 ibCaPortGidTable OBJECT-TYPE 774 SYNTAX SEQUENCE OF IbCaPortGidEntry 775 MAX-ACCESS not-accessible 776 STATUS current 777 DESCRIPTION 778 "A table containing the port GIDs for each CA." 779 ::= { ibCaPortAttrInfo 2 } 781 ibCaPortGidEntry OBJECT-TYPE 782 SYNTAX IbCaPortGidEntry 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "A conceptual row of the ibCaPortGidTable containing 787 information about a particular GID on an IB port 788 for a particular CA." 789 INDEX { ibCaIndex, ibCaPortIndex, ibCaPortGidIndex } 790 ::= { ibCaPortGidTable 1 } 792 IbCaPortGidEntry ::= SEQUENCE { 793 ibCaPortGidIndex Integer32, 794 ibCaPortGidValue OCTET STRING 795 } 797 ibCaPortGidIndex OBJECT-TYPE 798 SYNTAX Integer32(1..65535) 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "Index that identifies the GID entry for this IB data port. 803 Each port on a CA is assigned at least 1 unicast GID. 804 Note, the value of ibCaPortGidIndex will never be greater 805 than the value of ibCaMaxGidsPerPort that defines the 806 upper value for this index." 807 ::= { ibCaPortGidEntry 1 } 809 ibCaPortGidValue OBJECT-TYPE 810 SYNTAX OCTET STRING (SIZE(16)) 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "The Global Identifier (GID) is a 128-bit (16-byte) unicast 815 or multicast identifier used to identify a channel adapter 816 port. A GID is a valid 128-bit IPv6 address (as defined in 817 RFC 2373) with additional IBA modifications that facilitate 818 node discovery, routing, and communications." 819 REFERENCE 820 "InfiniBand Architecture Release 1.0.a. Vol 1. 821 Section 4.1.1 GID Usage and Properties." 822 ::= { ibCaPortGidEntry 2 } 824 --**************************************************************** 825 -- Module Conformance Statement 826 -- 827 -- DESCRIPTION: The module conformance statement includes the 828 -- compliance statements and the units of conformance 829 -- section. 830 --**************************************************************** 832 ibCaCompliances OBJECT IDENTIFIER ::= { ibCaConformance 1 } 834 ibCaGroups OBJECT IDENTIFIER ::= { ibCaConformance 2 } 836 --**************************************************************** 837 -- Compliance Statements 838 --**************************************************************** 840 ibCaBasicCompliance MODULE-COMPLIANCE 841 STATUS current 842 DESCRIPTION 843 "The basic CA implementation requirements for agents that 844 support the IPOIB CA MIB." 845 MODULE -- this module 846 MANDATORY-GROUPS { 847 ibCaGeneralGroup 848 } 849 ::= { ibCaCompliances 1 } 851 ibCaFullCompliance MODULE-COMPLIANCE 852 STATUS current 853 DESCRIPTION 854 "The complete node implementation requirements for agents that 855 support the full IPOIB CA MIB." 856 MODULE -- this module 857 MANDATORY-GROUPS { 858 ibCaGeneralGroup, 859 ibCaAttrGroup, 860 ibCaPortAttrGroup, 861 ibCaPortGidGroup 862 } 863 ::= { ibCaCompliances 2 } 865 --**************************************************************** 866 -- Units Of Conformance 867 --**************************************************************** 869 ibCaGeneralGroup OBJECT-GROUP 870 OBJECTS { 871 ibCaType, 872 ibCaNodeGuid, 873 ibCaNumPorts 874 } 875 STATUS current 876 DESCRIPTION 877 "The ibCaGeneralGroup defines the MIB objects that describe 878 the general characteritics of this Channel Adapter." 879 ::= { ibCaGroups 1 } 881 ibCaAttrGroup OBJECT-GROUP 882 OBJECTS { 883 ibCaHasReliableConnection, 884 ibCaHasUnreliableConnection, 885 ibCaHasReliableDatagram, 886 ibCaHasUnreliableDatagram, 887 ibCaSupportsAtomicOperations, 888 ibCaSupportsOtherOperations, 889 ibCaSupportsSolicitedEvents, 890 ibCaPathMtuSetSupport, 891 ibCaGenEndToEndFlowControl, 892 ibCaSupportsMulticast, 893 ibCaSupportsAutoPathMigration, 894 ibCaSupportsMemoryProtection, 895 ibCaSupportsLoopback, 896 ibCaSupportsSubnetManager 897 } 898 STATUS current 899 DESCRIPTION 900 "The ibCaAttrGroup defines the MIB objects that describe 901 more specific attributes about the Channel Adpater." 902 ::= { ibCaGroups 2 } 904 ibCaPortAttrGroup OBJECT-GROUP 905 OBJECTS { 906 ibCaPortGuid, 907 ibCaPhysicalInterface, 908 ibCaSupportsStaticRateControl, 909 ibCaInterpacketDelayValue, 910 ibCaSupportsMultipathing, 911 ibCaValidatesInPktDlid, 912 ibCaMaxGidsPerPort 913 } 914 STATUS current 915 DESCRIPTION 916 "The ibCaPortAttrGroup defines the MIB objects that describe 917 attributes about the Channel Adpater ports." 918 ::= { ibCaGroups 3 } 920 ibCaPortGidGroup OBJECT-GROUP 921 OBJECTS { 922 ibCaPortGidValue 923 } 924 STATUS current 925 DESCRIPTION 926 "The ibCaPortGidGroup defines the MIB objects that describe 927 attributes about the Channel Adpater port GIDs." 928 ::= { ibCaGroups 4 } 930 END 932 6.0 Revision History 934 This section should be removed when this document is published as an 935 RFC. 937 6.1 Changes from 939 Fixed object definitions as needed. 941 6.2 Changes from 943 Deleted ibCaSupportsPKeyCheck object (CAs are required to enforce P_Key 944 per the InfiniBand spec). Fixed DESCRIPTION of ibCaPortGuid object. 946 6.3 Changes from 948 The MIB now models network entities with one or more CAs. The CA number 949 is now the index into each table. Other minor edits to objects, 950 descriptions, etc. 952 7. Security Considerations 954 SNMPv1 by itself is not a secure environment. Even if the network 955 itself is secure (for example by using IPSec), even then, there is no 956 control as to who on the secure network is allowed to access and 957 GET/SET (read/change/create/delete) the objects in this MIB. 959 It is recommended that the implementers consider the security 960 features as provided by the SNMPv3 framework. Specifically, the use 961 It is recommended that the implementers consider the security 962 features as provided by the SNMPv3 framework. Specifically, the use 963 of the User-based Security Model RFC 2574 [RFC2574] and the View- 964 based Access Control Model RFC 2575 [RFC2575] is recommended. 966 It is then a customer/user responsibility to ensure that the SNMP 967 entity giving access to an instance of this MIB, is properly 968 configured to give access to the objects only to those principals 969 (users) that have legitimate rights to indeed GET or SET 970 (change/create/delete) them. 972 8. Intellectual Property 974 The IETF takes no position regarding the validity or scope of any 975 intellectual property or other rights that might be claimed to 976 pertain to the implementation or use of the technology described 977 in this document or the extent to which any license under such 978 rights might or might not be available; neither does it 979 represent that it has made any effort to identify any such 980 rights. Information on the IETF's procedures with respect to 981 rights in standards-track and standards-related documentation 982 can be found in BCP-11. Copies of claims of rights made 983 available for publication and any assurances of licenses to be 984 made available, or the result of an attempt made to obtain a 985 general license or permission for the use of such proprietary 986 rights by implementors or users of this specification can be 987 obtained from the IETF Secretariat. 989 The IETF invites any interested party to bring to its attention 990 any copyrights, patents or patent applications, or other proprietary 991 rights which may cover technology that may be required to practice this 992 standard. Please address the information to the IETF Executive Director. 994 9. References 996 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 997 Architecture for Describing SNMP Management Frameworks", 998 RFC 2571, April 1999. 1000 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 1001 of Management Information for TCP/IP-based Internets", STD 1002 16, RFC 1155, May 1990. 1004 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 1005 16, RFC 1212, March 1991. 1007 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 1008 the SNMP", RFC 1215, March 1991. 1010 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1011 Rose, M. and S. Waldbusser, "Structure of Management 1012 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1013 1999. 1015 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1016 Rose, M. and S. Waldbusser, "Textual Conventions for 1017 SMIv2", STD 58, RFC 2579, April 1999. 1019 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1020 Rose, M. and S. Waldbusser, "Conformance Statements for 1021 SMIv2", STD 58, RFC 2580, April 1999. 1023 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 1024 Network Management Protocol", STD 15, RFC 1157, May 1990. 1026 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1027 "Introduction to Community-based SNMPv2", RFC 1901, 1028 January 1996. 1030 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1031 "Transport Mappings for Version 2 of the Simple Network 1032 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1034 [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, 1035 "Message Processing and Dispatching for the Simple Network 1036 Management Protocol (SNMP)", RFC 2572, April 1999. 1038 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 1039 (USM) for version 3 of the Simple Network Management 1040 Protocol (SNMPv3)", RFC 2574, April 1999. 1042 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1043 "Protocol Operations for Version 2 of the Simple Network 1044 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1046 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", 1047 RFC 2573, April 1999. 1049 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 1050 Access Control Model (VACM) for the Simple Network 1051 Management Protocol (SNMP)", RFC 2575, April 1999. 1053 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 1054 "Introduction to Version 3 of the Internet-standard 1055 Network Management Framework", RFC 2570, April 1999. 1057 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1058 Requirement Levels", BCP 14, RFC 2119, March 1997. 1060 [IBTAArch] Infiniband Trade Association, Infiniband(TM) 1061 Architecture Specification Vol 1&2 Release 1.0a, 1999, 1062 2000. 1064 [IBTC] Harnedy, S., "Definitions of Textual Conventions and OBJECT- 1065 IDENTITIES for IP Over InfiniBand (IPOVERIB) Management" 1066 . May 2002. 1068 10. Author's Address 1070 Sean Harnedy 1071 InfiniSwitch Corporation 1072 134 Flanders Road Phone: 1-508-599-6388 1073 Westborough, MA 01581 Email: sharnedy@infiniswitch.com 1074 USA