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