idnits 2.17.1 draft-ietf-ipoib-channel-adapter-mib-05.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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 59 lines 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 RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet has text resembling 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 2004) is 7376 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) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) -- Possible downref: Non-RFC (?) normative reference: ref. 'INFINIV1' Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Sean Harnedy 3 Mangrove Systems, Inc. 4 Expires: August 2004 February 2004 6 Definitions of Managed Objects for 7 InfiniBand Channel Adapters (CA) 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Copyright Notice 33 Copyright (C) The Internet Society (2004). All Rights Reserved. 35 Abstract 37 InfiniBand Architecture (IBA) specifies a high speed, channel based, 38 switched fabric architecture that delivers scalable performance in 39 data centers. 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it defines objects for managing InfiniBand Channel 44 Adapters (CA). 46 Table of Contents 48 1. Introduction ................................................ 3 49 2. The Internet-Standard Management Framework .................. 3 50 3. Structure of the MIB ........................................ 3 51 3.1. Overview .................................................. 3 52 3.2. Discussion of MIB Groups .................................. 3 53 3.3. The CA MIB Objects ........................................ 4 54 3.3.1. The General Channel Adapter Info Group .................. 4 55 3.3.2. The Channel Adapter Attributes Info Group ............... 4 56 3.3.3. The Channel Adapter Port Attributes and Gid Info Group .. 4 57 3.4. The CA Conformance Group .................................. 4 58 3.4.1. CA Compliance Groups .................................... 4 59 4. IPOIB CA MIB Definitions .................................... 4 60 5. Security Considerations ..................................... 18 61 6. IANA Considerations ......................................... 18 62 7. References .................................................. 19 63 7.1. Normative References ...................................... 19 64 7.2. Informative References .................................... 19 65 8. Authors' Addresses .......................................... 19 66 9. Intellectual Property Notice ................................ 19 67 10. Full Copyright Statement ................................... 20 69 1. Introduction 71 This document defines a MIB for InfiniBand Channel Adapters (CA). 73 The InfiniBand Architecture [INFINIV1] (IBA) is defined by the 74 InfiniBand Trade Association. InfiniBand is designed to provide low 75 latency, high bandwidth interconnect in a computing environment. 76 This document will define the objects related to managing a specific 77 class of InfiniBand nodes called Channel Adapters. 79 A Channel Adapter (CA) is the end-point for IBA packets that are sent 80 and received over the IBA switching fabric. There are two types of 81 CAs: Host Channel Adapters (HCA) and Target Channel Adapters (TCA). 82 Typically, HCAs are used by host processors and TCAs are used by I/O 83 adapters to connect to the IBA switch fabric. The HCA supports the 84 IBA Verbs layer as the transport layer interface, while the TCA often 85 uses its own implementation-specific interface to the transport layer. 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 89 this document are to be interpreted as described in 90 RFC 2119 [RFC2119]. 92 2. The Internet-Standard Management Framework 94 For a detailed overview of the documents that describe the current 95 Internet-Standard Management Framework, please refer to section 7 of 96 RFC 3410 [RFC3410]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. MIB objects are generally 100 accessed through the Simple Network Management Protocol (SNMP). 101 Objects in the MIB are defined using the mechanisms defined in the 102 Structure of Management Information (SMI). This memo specifies a MIB 103 module that is compliant to the SMIv2, which is described in STD 58, 104 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 105 [RFC2580]. 107 3. Structure of the MIB 109 This section describes the structure of the IPOIB CA MIB. 111 3.1. Overview 113 The SNMP management of the CA involves the monitoring of key channel 114 adapter attributes. 116 3.2. Discussion of MIB Groups 118 The CA MIB is divided into two basic groups: MIB objects and the 119 conformance group. 121 3.3. The CA MIB Objects 123 The CA MIB objects correlate to the set of Channel Adapter 124 attributes. These attributes are organized into three major CA MIB 125 groups. 127 These are: the General Channel Adapter Info Group, the Channel 128 Adapter Attributes Info Group, and the Channel Adapter Port 129 Attributes and Gid Info Group. 131 3.3.1. The General Channel Adapter Info Group 133 This group provides general information common to any InfiniBand 134 network entity that contains CAs. This includes distinguishing 135 between the HCA and the TCA, displaying the node GUIDs, and showing 136 the number of ports on each CA. 138 3.3.2. The Channel Adapter Attributes Info Group 140 This group provides more specific information about the CAs on a 141 network entity. This includes various attribute flags, transport 142 service support, and other CA characteristics. 144 3.3.3. The Channel Adapter Port Attributes and Gid Info Group 146 This group provides information about the CA ports. This includes 147 the type of physical interfaces supported, other port attributes, 148 and a table containing the port GIDs. 150 3.4. The CA Conformance Group 152 The CA Conformance Group lists the possible compliances for various 153 types of InfiniBand nodes that contain channel adapters. Currently, 154 two types of compliance are defined: basic and full. The units of 155 conformance which define the constituent object groups are also 156 listed. 158 3.4.1. CA Compliance Groups 160 The Compliance Groups list acceptable MIB implementation 161 requirements. 163 4. IPOIB CA MIB Definitions 165 IB-CA-MIB DEFINITIONS ::= BEGIN 167 IMPORTS 168 MODULE-IDENTITY, OBJECT-TYPE, 169 Unsigned32 FROM SNMPv2-SMI 170 TruthValue FROM SNMPv2-TC 171 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 172 infinibandMIB, IbDataPort FROM IB-TC-MIB; 174 ibCaMIB MODULE-IDENTITY 175 LAST-UPDATED "200402011200Z" -- February 1, 2004 12:00:00 GMT 176 ORGANIZATION "IETF IP Over IB (IPOIB) Working Group" 177 CONTACT-INFO 178 "Sean Harnedy (sharnedy@mangrovesystems.com) 179 Mangrove Systems, Inc. 181 Email comments to the IPOIB WG Mailing List at 182 ipoverib@ietf.org." 183 DESCRIPTION 184 "Copyright (C) The Internet Society (2004). The initial 185 version of this MIB module was published in RFC XXXX; for 186 full legal notices see the RFC itself. Supplementary 187 information may be available on 188 http://www.ietf.org/copyrights/ianamib.html. 190 This module contains managed object definitions for 191 the instrumentation for an InfiniBand Channel Adapter (CA)." 192 REVISION 193 "200402011200Z" -- 2 February 2004 12:00:00 GMT 194 DESCRIPTION 195 "Initial version published as part of RFC XXXX." 196 ::= { infinibandMIB 4 } 198 --**************************************************************** 199 -- Object Identifiers for the IPOIB CA MIB 200 --**************************************************************** 202 ibCaObjects OBJECT IDENTIFIER ::= { ibCaMIB 1 } 203 ibCaConformance OBJECT IDENTIFIER ::= { ibCaMIB 2 } 205 --**************************************************************** 206 -- General Channel Adapter Info Group 207 -- 208 -- DESCRIPTION: This group contains a table that describes 209 -- general information about the Channel Adapters present in 210 -- this Managed System Element. 211 --**************************************************************** 213 ibCaGeneralInfo OBJECT IDENTIFIER ::= { ibCaObjects 1 } 215 --**************************************************************** 216 -- Channel Adapters General Information Table 217 --**************************************************************** 219 ibCaGeneralInfoTable OBJECT-TYPE 220 SYNTAX SEQUENCE OF IbCaGeneralInfoEntry 221 MAX-ACCESS not-accessible 222 STATUS current 223 DESCRIPTION 224 "A table containing general information about the Channel 225 Adapters on this network entity." 226 ::= { ibCaGeneralInfo 1 } 228 ibCaGeneralInfoEntry OBJECT-TYPE 229 SYNTAX IbCaGeneralInfoEntry 230 MAX-ACCESS not-accessible 231 STATUS current 232 DESCRIPTION 233 "A conceptual row of the ibCaGeneralInfoTable containing 234 information about the general characteristics of each 235 Channel Adapter on this network entity." 236 INDEX { ibCaIndex } 237 ::= { ibCaGeneralInfoTable 1 } 239 IbCaGeneralInfoEntry ::= SEQUENCE { 240 ibCaIndex Unsigned32, 241 ibCaType INTEGER, 242 ibCaNodeGuid OCTET STRING, 243 ibCaNumPorts Unsigned32 244 } 246 ibCaIndex OBJECT-TYPE 247 SYNTAX Unsigned32(1..254) 248 MAX-ACCESS not-accessible 249 STATUS current 250 DESCRIPTION 251 "Index that identifies the specific CA on this network 252 entity. The index is defined for a range of CAs from 253 1 to N, where N can have a maximum value of 254." 254 ::= { ibCaGeneralInfoEntry 1 } 256 ibCaType OBJECT-TYPE 257 SYNTAX INTEGER { 258 unknown(1), 259 hca(2), -- host CA 260 tca(3) -- terminal CA 261 } 262 MAX-ACCESS read-only 263 STATUS current 264 DESCRIPTION 265 "Type of Channel Adapter: either a Host Channel Adapter (HCA), 266 or a Target Channel Adapter (TCA). The key difference between 267 an HCA and a TCA is that the HCA supports the IBA Verbs layer, 268 while the TCA uses an implementation dependent interface to 269 the transport layer. If the type of CA cannot be determined, 270 the unknown(1) value is returned." 271 REFERENCE 272 "InfiniBand Architecture Release 1.1 Vol. 1. Section 17.1." 273 ::= { ibCaGeneralInfoEntry 2 } 275 ibCaNodeGuid OBJECT-TYPE 276 SYNTAX OCTET STRING (SIZE(8)) 277 MAX-ACCESS read-only 278 STATUS current 279 DESCRIPTION 280 "The GUID of this CA. All ports on the same node shall 281 report the same CA node GUID value. This provides a 282 means for uniquely identifying a CA node within a 283 subnet and helps to determine the co-location of 284 the ports." 285 REFERENCE 286 "InfiniBand Architecture Release 1.1. Vol. 1. Section 17.2.5." 287 ::= { ibCaGeneralInfoEntry 3 } 289 ibCaNumPorts OBJECT-TYPE 290 SYNTAX Unsigned32(1..254) 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "Number of physical IB data ports on this Channel Adapter. Ports 295 are numbered starting from 1. If there is more than one port, 296 the ports are numbered sequentially." 297 REFERENCE 298 "InfiniBand Architecture Release 1.1. Vol. 1. 299 Section 17.2.1.3; Table 259 Port Attributes & Functions." 300 ::= { ibCaGeneralInfoEntry 4 } 302 --**************************************************************** 303 -- Channel Adapter Attributes Info Group 304 -- 305 -- DESCRIPTION: This group contains a table that describes more 306 -- specific attributes about each CA on the network entity. 307 --**************************************************************** 309 ibCaAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 2 } 311 --**************************************************************** 312 -- Channel Adapter Attributes Table 313 --**************************************************************** 315 ibCaAttributeTable OBJECT-TYPE 316 SYNTAX SEQUENCE OF IbCaAttributeEntry 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "A table containing information about the Channel Adapter 321 attributes on this network entity." 322 ::= { ibCaAttrInfo 1 } 324 ibCaAttributeEntry OBJECT-TYPE 325 SYNTAX IbCaAttributeEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "A conceptual row of the ibCaAttributeTable containing 330 information about the general characteristics of each 331 Channel Adapter on this network entity." 332 INDEX { ibCaIndex } 333 ::= { ibCaAttributeTable 1 } 335 IbCaAttributeEntry ::= SEQUENCE { 336 ibCaHasReliableConnection TruthValue, 337 ibCaHasUnreliableConnection TruthValue, 338 ibCaHasReliableDatagram TruthValue, 339 ibCaHasUnreliableDatagram TruthValue, 340 ibCaSupportsAtomicOperations TruthValue, 341 ibCaSupportsOtherOperations TruthValue, 342 ibCaSupportsSolicitedEvents TruthValue, 343 ibCaPathMtuSetSupport INTEGER, 344 ibCaGenEndToEndFlowControl TruthValue, 345 ibCaSupportsMulticast TruthValue, 346 ibCaSupportsAutoPathMigration TruthValue, 347 ibCaSupportsMemoryProtection TruthValue, 348 ibCaSupportsLoopback TruthValue, 349 ibCaSupportsSubnetManager TruthValue 350 } 352 ibCaHasReliableConnection OBJECT-TYPE 353 SYNTAX TruthValue 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "Flag that indicates whether this CA supports 358 Reliable Connection (RC) transport service." 359 REFERENCE 360 "InfiniBand Architecture Release 1.1. Vol. 1. 361 Section 17.2.2; Table 260 Channel Adapter Attributes." 362 ::= { ibCaAttributeEntry 1 } 364 ibCaHasUnreliableConnection OBJECT-TYPE 365 SYNTAX TruthValue 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "Flag that indicates whether this CA supports 370 Unreliable Connection (UC) transport service." 371 REFERENCE 372 "InfiniBand Architecture Release 1.1. Vol. 1. 373 Section 17.2.2; Table 260 Channel Adapter Attributes." 374 ::= { ibCaAttributeEntry 2 } 376 ibCaHasReliableDatagram OBJECT-TYPE 377 SYNTAX TruthValue 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "Flag that indicates whether this CA supports 382 Reliable Datagram (RD) transport service." 383 REFERENCE 384 "InfiniBand Architecture Release 1.1. Vol. 1. 385 Section 17.2.2; Table 260 Channel Adapter Attributes." 386 ::= { ibCaAttributeEntry 3 } 388 ibCaHasUnreliableDatagram OBJECT-TYPE 389 SYNTAX TruthValue 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "Flag that indicates whether this CA supports 394 Unreliable Datagram (UD) transport service." 395 REFERENCE 396 "InfiniBand Architecture Release 1.1. Vol. 1. 397 Section 17.2.2; Table 260 Channel Adapter Attributes." 398 ::= { ibCaAttributeEntry 4 } 400 ibCaSupportsAtomicOperations OBJECT-TYPE 401 SYNTAX TruthValue 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "Flag that indicates whether this CA supports 406 atomic operations. An atomic operation is an operation 407 that is guaranteed to finish without having another 408 operation alter the results once the atomic operation 409 has been initiated." 410 REFERENCE 411 "InfiniBand Architecture Release 1.1. Vol. 1. 412 Section 17.2.2; Table 260 Channel Adapter Attributes." 413 ::= { ibCaAttributeEntry 5 } 415 ibCaSupportsOtherOperations OBJECT-TYPE 416 SYNTAX TruthValue 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "Flag that indicates whether this CA supports 421 all of the other operations (excluding atomic operations) 422 defined for a particular supported transport service." 423 REFERENCE 424 "InfiniBand Architecture Release 1.1. Vol. 1. 425 Section 17.2.2; Table 260 Channel Adapter Attributes." 426 ::= { ibCaAttributeEntry 6 } 428 ibCaSupportsSolicitedEvents OBJECT-TYPE 429 SYNTAX TruthValue 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "Flag that indicates whether this CA supports the 434 generation and reception of solicited events. A solicited 435 event is a feature by which a queue pair consumer on a 436 CA can cause an event to be generated at the destination 437 when its message is received." 438 REFERENCE 439 "InfiniBand Architecture Release 1.1. Vol. 1. 440 Section 17.2.2; Table 260 Channel Adapter Attributes. 442 and Section 9.2.3 Solicited Event (SE) - 1 bit." 443 ::= { ibCaAttributeEntry 7 } 445 ibCaPathMtuSetSupport OBJECT-TYPE 446 SYNTAX INTEGER { 447 mtu256(1), 448 mtu256n512(2), 449 mtu256n512n1024(3), 450 mtu256n512n1024n2048(4), 451 mtu256n512n1024n2048n4096(5) 452 } 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "Set of MTU values (in bytes) supported by this CA for all 457 transport service classes. The Maximum Transfer Unit is the 458 largest size allowable for the packet payload." 459 REFERENCE 460 "InfiniBand Architecture Release 1.1. Vol. 1. 461 Section 17.2.2; Table 260 Channel Adapter Attributes." 462 ::= { ibCaAttributeEntry 8 } 464 ibCaGenEndToEndFlowControl OBJECT-TYPE 465 SYNTAX TruthValue 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "Flag that indicates whether this CA supports 470 the generation of end-to-end flow control. End-to-end 471 flow control is a mechanism that prevents sending messages 472 when the destination does not have adequate receive buffers 473 to receive the message." 474 REFERENCE 475 "InfiniBand Architecture Release 1.1. Vol. 1. 476 Section 17.2.2; Table 260 Channel Adapter Attributes." 477 ::= { ibCaAttributeEntry 9 } 479 ibCaSupportsMulticast OBJECT-TYPE 480 SYNTAX TruthValue 481 MAX-ACCESS read-only 482 STATUS current 483 DESCRIPTION 484 "Flag that indicates whether this CA supports multicast 485 operations. Multicast is the ability to deliver a single 486 packet to multiple ports." 487 REFERENCE 488 "InfiniBand Architecture Release 1.1. Vol. 1. 489 Section 17.2.2; Table 260 Channel Adapter Attributes." 490 ::= { ibCaAttributeEntry 10 } 492 ibCaSupportsAutoPathMigration OBJECT-TYPE 493 SYNTAX TruthValue 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "Flag that indicates whether this CA supports 498 automatic path migration. Automatic path migration 499 is the process by which a CA (on a per QP basis) 500 signals another CA to cause path migration to a 501 preset alternate path." 502 REFERENCE 503 "InfiniBand Architecture Release 1.1. Vol. 1. 504 Section 17.2.2; Table 260 Channel Adapter Attributes." 505 ::= { ibCaAttributeEntry 11 } 507 ibCaSupportsMemoryProtection OBJECT-TYPE 508 SYNTAX TruthValue 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "Flag that indicates whether this CA supports InfiniBand 513 memory management protection mechanisms." 514 REFERENCE 515 "InfiniBand Architecture Release 1.1. Vol. 1. 516 Section 17.2.2; Table 260 Channel Adapter Attributes. 517 and Section 10.6 Memory Management." 518 ::= { ibCaAttributeEntry 12 } 520 ibCaSupportsLoopback OBJECT-TYPE 521 SYNTAX TruthValue 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "Flag that indicates whether this CA supports 526 loopback operations. Loopback support allows for the 527 sending and receiving of self-addressed packets that 528 do not go out on the wire. If this feature is supported, 529 self-addressed packets must work, even if no switch is 530 present." 531 REFERENCE 532 "InfiniBand Architecture Release 1.1. Vol. 1. 533 Section 17.2.2; Table 260 Channel Adapter Attributes." 534 ::= { ibCaAttributeEntry 13 } 536 ibCaSupportsSubnetManager OBJECT-TYPE 537 SYNTAX TruthValue 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "Flag that indicates whether this CA supports 542 a Subnet Manager (SM) instance." 543 REFERENCE 544 "InfiniBand Architecture Release 1.1. Vol. 1. 545 Section 17.2.2; Table 260 Channel Adapter Attributes." 546 ::= { ibCaAttributeEntry 14 } 548 --**************************************************************** 549 -- Channel Adapter Port Attributes and GID Info Group 550 -- 551 -- DESCRIPTION: This group contains information about the CA ports 552 -- on the network entity and the GID table associated with each 553 -- port. 554 --**************************************************************** 556 ibCaPortAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 3 } 558 --**************************************************************** 559 -- Channel Adapter Port Attribute Table 560 --**************************************************************** 562 ibCaPortAttributeTable OBJECT-TYPE 563 SYNTAX SEQUENCE OF IbCaPortAttributeEntry 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "A table containing information about the Channel Adapter 568 port attributes on this network entity." 569 ::= { ibCaPortAttrInfo 1 } 571 ibCaPortAttributeEntry OBJECT-TYPE 572 SYNTAX IbCaPortAttributeEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "A conceptual row of the ibCaPortAttributeTable containing 577 information about the general characteristics of each 578 Channel Adapter port on this network entity." 579 INDEX { ibCaIndex, ibCaPortIndex } 580 ::= { ibCaPortAttributeTable 1 } 582 IbCaPortAttributeEntry ::= SEQUENCE { 583 ibCaPortIndex IbDataPort, 584 ibCaPortGuid OCTET STRING, 585 ibCaPhysicalInterface INTEGER, 586 ibCaSupportsStaticRateControl TruthValue, 587 ibCaInterpacketDelayValue INTEGER, 588 ibCaSupportsMultipathing TruthValue, 589 ibCaValidatesInPktDlid TruthValue, 590 ibCaMaxGidsPerPort Unsigned32 591 } 593 ibCaPortIndex OBJECT-TYPE 594 SYNTAX IbDataPort 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "Index that identifies the InfiniBand data port. The IBA 599 defines a range of valid data ports from 1 to N, where 600 N can have a maximum value of 254 for an IBA switch." 602 ::= { ibCaPortAttributeEntry 1 } 604 ibCaPortGuid OBJECT-TYPE 605 SYNTAX OCTET STRING (SIZE(8)) 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "The GUID of this CA port. All ports on the same CA shall 610 report a unique ibCaPortGuid value. This provides a means 611 for uniquely identifying a CA port on a node within a subnet 612 and helps to determine the co-location of the ports." 613 REFERENCE 614 "InfiniBand Architecture Release 1.1. Vol. 1. Section 17.2.5." 615 ::= { ibCaPortAttributeEntry 2 } 617 ibCaPhysicalInterface OBJECT-TYPE 618 SYNTAX INTEGER { 619 cable(1), 620 fiber(2), 621 backplane(3) 622 } 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The physical interface for this CA. When the value 627 is cable(1), the CA supports a cable connector physical 628 interface. This physical attach point is defined for use 629 with copper cables. When the value is fiber(2), the CA 630 supports a fiber connector physical interface. This 631 physical attach point is defined for use with optical 632 cables. When the value is backplane(3), the CA supports 633 a backplane connector physical interface. This physical 634 attach point is defined for accepting a specified form 635 factor that houses the channel adapter." 636 REFERENCE 637 "InfiniBand Architecture Release 1.1. Vol. 1. 638 Section 17.2.1.3 Port Attributes and Functions; 639 Vol. 2. 3.1 Introduction (Physical Layer Overview)." 640 ::= { ibCaPortAttributeEntry 3 } 642 ibCaSupportsStaticRateControl OBJECT-TYPE 643 SYNTAX TruthValue 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "Flag that indicates whether this CA supports static 648 rate control. Static rate controls are required for 649 all IB ports that support a data rate over 2.5 Gbps." 650 REFERENCE 651 "InfiniBand Architecture Release 1.1. Vol. 1. 652 Section 17.2.6 Static Rate Control." 653 ::= { ibCaPortAttributeEntry 4 } 655 ibCaInterpacketDelayValue OBJECT-TYPE 656 SYNTAX INTEGER { 657 unknown(1), 658 zero(2), -- 100% 659 three(3), -- 25% 660 two(4), -- 33% 661 eleven(5) -- 8% 662 } 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "Interpacket Delay Value (IPD) supported for CAs that have 667 static rate control (i.e., the ibCaSupportsStaticRateControl 668 object must have a value of true(1) for this object to 669 contain a valid value; Otherwise, unknown(1) is returned). 670 The IPD allows for the slowing of the packet rate for all 671 of the standard link rates. 673 An ibCaInterpacketDelayValue of zero(2) is required for all CAs 674 that support static rate control. An ibCaInterpacketDelayValue 675 of three(3) is required by CAs that support 1 GBs or higher 676 link rate. An ibCaInterpacketDelayValue of two(4) is required by 677 CAs that support 3 Gbps or higher link rates and, an 678 ibCaInterpacketDelayValue of eleven(5) is required by CAs that 679 also support 3 Gbps or higher link rates." 680 REFERENCE 681 "InfiniBand Architecture Release 1.1. Vol. 1. 682 Section 17.2.6 Static Rate Control, and Table 261 683 Static Rate Control IPD Values." 684 ::= { ibCaPortAttributeEntry 5 } 686 ibCaSupportsMultipathing OBJECT-TYPE 687 SYNTAX TruthValue 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "Flag that indicates whether this CA supports multipathing. 692 The CA link layer port checks the unicast DLID in the 693 received packet for validity by masking the number of low 694 order bits indicated by the LID Mask Control field (LMC) 695 before comparing the DLID to its assigned LID if this 696 object is true(1)." 697 REFERENCE 698 "InfiniBand Architecture Release 1.1. Vol. 1. 699 Section 7.2.1.3. and Table 259 Port Attributes & Functions; 700 Also, Section 7.11.1 Multipathing Requirements on End Node." 701 ::= { ibCaPortAttributeEntry 6 } 703 ibCaValidatesInPktDlid OBJECT-TYPE 704 SYNTAX TruthValue 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "Flag that indicates whether this CA supports the validation 709 of incoming packet DLIDs, and if the GRH is present, the 710 DGID." 711 REFERENCE 712 "InfiniBand Architecture Release 1.1. Vol. 1. 713 Section 7.2.1.3. and Table 259 Port Attributes & Functions." 714 ::= { ibCaPortAttributeEntry 7 } 716 ibCaMaxGidsPerPort OBJECT-TYPE 717 SYNTAX Unsigned32(1..65535) 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "Maximum number of GIDs per port. The maximum number of 722 unicast GIDs supported per CA port is implementation specific. 723 Each port will support at least one (1) GID." 724 REFERENCE 725 "InfiniBand Architecture Release 1.1. Vol. 1. 726 Section 7.2.1.3. and Table 259 Port Attributes & Functions." 727 ::= { ibCaPortAttributeEntry 8 } 729 --**************************************************************** 730 -- Channel Adapter Port Global Identifier (GID) Table 731 --**************************************************************** 733 ibCaPortGidTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF IbCaPortGidEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "A table containing the port GIDs for each CA." 739 ::= { ibCaPortAttrInfo 2 } 741 ibCaPortGidEntry OBJECT-TYPE 742 SYNTAX IbCaPortGidEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "A conceptual row of the ibCaPortGidTable containing 747 information about a particular GID on an IB port 748 for a particular CA." 749 INDEX { ibCaIndex, ibCaPortIndex, ibCaPortGidIndex } 750 ::= { ibCaPortGidTable 1 } 752 IbCaPortGidEntry ::= SEQUENCE { 753 ibCaPortGidIndex Unsigned32, 754 ibCaPortGidValue OCTET STRING 755 } 757 ibCaPortGidIndex OBJECT-TYPE 758 SYNTAX Unsigned32(1..65535) 759 MAX-ACCESS not-accessible 760 STATUS current 761 DESCRIPTION 762 "Index that identifies the GID entry for this IB data port. 763 Each port on a CA is assigned at least 1 unicast GID. 764 Note, the value of ibCaPortGidIndex will never be greater 765 than the value of ibCaMaxGidsPerPort that defines the 766 upper value for this index." 767 ::= { ibCaPortGidEntry 1 } 769 ibCaPortGidValue OBJECT-TYPE 770 SYNTAX OCTET STRING (SIZE(16)) 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The Global Identifier (GID) is a 128-bit (16-byte) unicast 775 or multicast identifier used to identify a channel adapter 776 port. A GID is a valid 128-bit IPv6 address (as defined in 777 RFC 2373) with additional IBA modifications that facilitate 778 node discovery, routing, and communications." 779 REFERENCE 780 "InfiniBand Architecture Release 1.1. Vol. 1. 781 Section 4.1.1 GID Usage and Properties." 782 ::= { ibCaPortGidEntry 2 } 784 --**************************************************************** 785 -- Module Conformance Statement 786 -- 787 -- DESCRIPTION: The module conformance statement includes the 788 -- compliance statements and the units of conformance 789 -- section. 790 --**************************************************************** 792 ibCaCompliances OBJECT IDENTIFIER ::= { ibCaConformance 1 } 794 ibCaGroups OBJECT IDENTIFIER ::= { ibCaConformance 2 } 796 --**************************************************************** 797 -- Compliance Statements 798 --**************************************************************** 800 ibCaBasicCompliance MODULE-COMPLIANCE 801 STATUS current 802 DESCRIPTION 803 "The basic CA implementation requirements for agents that 804 support the IPOIB CA MIB." 805 MODULE -- this module 806 MANDATORY-GROUPS { 807 ibCaGeneralGroup 808 } 809 ::= { ibCaCompliances 1 } 811 ibCaFullCompliance MODULE-COMPLIANCE 812 STATUS current 813 DESCRIPTION 814 "The complete node implementation requirements for agents that 815 support the full IPOIB CA MIB." 816 MODULE -- this module 817 MANDATORY-GROUPS { 818 ibCaGeneralGroup, 819 ibCaAttrGroup, 820 ibCaPortAttrGroup, 821 ibCaPortGidGroup 822 } 823 ::= { ibCaCompliances 2 } 825 --**************************************************************** 826 -- Units of Conformance 827 --**************************************************************** 829 ibCaGeneralGroup OBJECT-GROUP 830 OBJECTS { 831 ibCaType, 832 ibCaNodeGuid, 833 ibCaNumPorts 834 } 835 STATUS current 836 DESCRIPTION 837 "The ibCaGeneralGroup defines the MIB objects that describe 838 the general characteristics of this Channel Adapter." 839 ::= { ibCaGroups 1 } 841 ibCaAttrGroup OBJECT-GROUP 842 OBJECTS { 843 ibCaHasReliableConnection, 844 ibCaHasUnreliableConnection, 845 ibCaHasReliableDatagram, 846 ibCaHasUnreliableDatagram, 847 ibCaSupportsAtomicOperations, 848 ibCaSupportsOtherOperations, 849 ibCaSupportsSolicitedEvents, 850 ibCaPathMtuSetSupport, 851 ibCaGenEndToEndFlowControl, 852 ibCaSupportsMulticast, 853 ibCaSupportsAutoPathMigration, 854 ibCaSupportsMemoryProtection, 855 ibCaSupportsLoopback, 856 ibCaSupportsSubnetManager 857 } 858 STATUS current 859 DESCRIPTION 860 "The ibCaAttrGroup defines the MIB objects that describe 861 more specific attributes about the Channel Adapter." 862 ::= { ibCaGroups 2 } 864 ibCaPortAttrGroup OBJECT-GROUP 865 OBJECTS { 866 ibCaPortGuid, 867 ibCaPhysicalInterface, 868 ibCaSupportsStaticRateControl, 869 ibCaInterpacketDelayValue, 870 ibCaSupportsMultipathing, 871 ibCaValidatesInPktDlid, 872 ibCaMaxGidsPerPort 873 } 874 STATUS current 875 DESCRIPTION 876 "The ibCaPortAttrGroup defines the MIB objects that describe 877 attributes about the Channel Adapter ports." 878 ::= { ibCaGroups 3 } 880 ibCaPortGidGroup OBJECT-GROUP 881 OBJECTS { 882 ibCaPortGidValue 883 } 884 STATUS current 885 DESCRIPTION 886 "The ibCaPortGidGroup defines the MIB objects that describe 887 attributes about the Channel Adapter port GIDs." 888 ::= { ibCaGroups 4 } 890 END 892 5. Security Considerations 894 This memo defines textual conventions and object identities for use 895 in IPOVERIB MIB modules. Security issues for these MIB modules are 896 addressed in the memos defining those modules. Because this memo 897 does not define management objects, the memo has no impact on the 898 security of the Internet. 900 6. IANA Considerations 902 IANA is requested to make a MIB OID assignment under the transmission 903 branch, that is, assign the infinibandMIB under { transmission 199 }. 904 This sub-id is requested because 199 is the ifType for 905 infiniband(199) and is available under transmission. 907 In the future, IPOIB related standards track MIB modules should be 908 rooted under the infinibandMIB subtree. The IANA is requested to 909 manage that namespace. New assignments can only be made via a 910 Standards Action as specified in [RFC2434]. 912 This document also requests IANA to assign { infinibandMIB 4 } to the 913 IB-CA-MIB specified in this document. 915 7. References 917 7.1. Normative References 919 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 920 Requirement Levels", BCP 14, RFC 2119, March 1997. 922 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 923 IANA Considerations Section in RFCs", BCP: 26, RFC 2434, 924 October 1998. 926 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 927 Rose, M. and S. Waldbusser, "Structure of Management 928 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 929 1999. 931 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 932 Rose, M. and S. Waldbusser, "Textual Conventions for 933 SMIv2", STD 58, RFC 2579, April 1999. 935 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 936 Rose, M. and S. Waldbusser, "Conformance Statements for 937 SMIv2", STD 58, RFC 2580, April 1999. 939 [INFINIV1] InfiniBand Architecture Specification Volume 1, 940 Release 1.1, November 6, 2002. 942 7.2. Informative References 944 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 945 "Introduction and Applicability Statements for Internet- 946 Standard Management Framework", RFC 3410, December 2002. 948 8. Author's Address 950 Sean Harnedy 951 Mangrove Systems, Inc. 952 10 Fairfield Boulevard 953 Wallingford, CT 06492 954 USA 955 Phone: +1-203-679-7539 956 Email: sharnedy@mangrovesystems.com 958 9. Intellectual Property Notice 960 The IETF takes no position regarding the validity or scope of any 961 intellectual property or other rights that might be claimed to 962 pertain to the implementation or use of the technology described in 963 this document or the extent to which any license under such rights 964 might or might not be available; neither does it represent that it 965 has made any effort to identify any such rights. Information on the 966 IETF's procedures with respect to rights in standards-track and 967 standards-related documentation can be found in BCP-11. Copies of 968 claims of rights made available for publication and any assurances of 969 licenses to be made available, or the result of an attempt made to 970 obtain a general license or permission for the use of such 971 proprietary rights by implementers or users of this specification can 972 be obtained from the IETF Secretariat. 974 The IETF invites any interested party to bring to its attention any 975 copyrights, patents or patent applications, or other proprietary 976 rights which may cover technology that may be required to practice 977 this standard. Please address the information to the IETF Executive 978 Director. 980 10. Full Copyright Statement 982 Copyright (C) The Internet Society (2004). All Rights Reserved. 984 This document and translations of it may be copied and 985 furnished to others, and derivative works that comment on 986 or otherwise explain it or assist in its implementation may 987 be prepared, copied, published and distributed, in whole or 988 in part, without restriction of any kind, provided that the 989 above copyright notice and this paragraph are included on 990 all such copies and derivative works. However, this document 991 itself may not be modified in any way, such as by removing the 992 copyright notice or references to the Internet Society or other 993 Internet organizations, except as needed for the purpose of 994 developing Internet standards in which case the procedures for 995 copyrights defined in the Internet Standards process must be 996 followed, or as required to translate it into languages other 997 than English. 999 The limited permissions granted above are perpetual and 1000 will not be revoked by the Internet Society or its 1001 successors or assigns. 1003 This document and the information contained herein is provided on an 1004 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1005 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1006 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1007 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1008 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.