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