idnits 2.17.1 draft-ietf-ipoib-channel-adapter-mib-08.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1034. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 986. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 993. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 999. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** 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: ---------------------------------------------------------------------------- ** Missing revision: the document name given in the document, 'draft-ietf-ipoib-channel-adapter-mib08', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-ipoib-channel-adapter-mib08', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-ietf-ipoib-channel-adapter-mib08', but the file name used is 'draft-ietf-ipoib-channel-adapter-mib-08' == 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. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (October 2006) is 6402 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 (**), 1 flaw (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IP over InfiniBand 2 Internet Draft Hal Rosenstock 3 Document: draft-ietf-ipoib-channel-adapter-mib08.txt HNR Consulting 4 Expires: April 2007 October 2006 6 Definitions of Managed Objects for 7 InfiniBand Channel Adapters (CA) 9 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Abstract 36 InfiniBand Architecture (IBA) specifies a high speed, channel based, 37 switched fabric architecture that delivers scalable performance in 38 data centers. 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it defines objects for managing InfiniBand Channel 43 Adapters (CA). 45 Copyright Notice 47 Copyright (C) The Internet Society (2006). 49 Table of Contents 51 1. Introduction...................................................2 52 2. The Internet-Standard Management Framework.....................3 53 3. Structure of the MIB...........................................3 54 3.1 Overview...................................................3 55 3.2 Discussion of MIB Groups.................................3 56 3.3 The CA MIB Objects.........................................3 57 3.3.1 The General Channel Adapter Info Group...................3 58 3.3.2 The Channel Adapter Attributes Info Group................4 59 3.3.3 The Channel Adapter Port Attributes and Gid Info Group...4 60 3.4 The CA Conformance Group...................................4 61 3.4.1 CA Compliance Groups.....................................4 62 4. IPOIB CA MIB Definitions.......................................4 63 5. Security Considerations.......................................19 64 6. IANA Considerations...........................................19 65 7. Revision History..............................................19 66 7.1 Changes from 19 67 8. References....................................................20 68 8.1 Normative References......................................20 69 8.2 Informative References....................................20 70 9. Acknowledgements..............................................20 71 10. Author's Addresses...........................................20 72 11. Intellectual Property Notice.................................21 73 12. Full Copyright Statement.....................................21 74 Acknowledgment...................................................22 76 1. Introduction 78 This document defines a MIB for InfiniBand Channel Adapters (CA). 80 The InfiniBand Architecture [INFINIV1] (IBA) is defined by the 81 InfiniBand Trade Association. InfiniBand is designed to provide low 82 latency, high bandwidth interconnect in a computing environment. 83 This document will define the objects related to managing a specific 84 class of InfiniBand nodes called Channel Adapters. 86 A Channel Adapter (CA) is the end-point for IBA packets that are sent 87 and received over the IBA switching fabric. There are two types of 88 CAs: Host Channel Adapters (HCA) and Target Channel Adapters (TCA). 89 Typically, HCAs are used by host processors and TCAs are used by I/O 90 adapters to connect to the IBA switch fabric. The HCA supports the 91 IBA Verbs layer as the transport layer interface, while the TCA often 92 uses its own implementation-specific interface to the transport 93 layer. 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 97 this document are to be interpreted as described in 98 RFC 2119 [RFC2119]. 100 2. The Internet-Standard Management Framework 102 For a detailed overview of the documents that describe the current 103 Internet-Standard Management Framework, please refer to section 7 of 104 RFC 3410 [RFC3410]. 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. MIB objects are generally 108 accessed through the Simple Network Management Protocol (SNMP). 109 Objects in the MIB are defined using the mechanisms defined in the 110 Structure of Management Information (SMI). This memo specifies a MIB 111 module that is compliant to the SMIv2, which is described in STD 58, 112 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 113 [RFC2580]. 115 3. Structure of the MIB 117 This section describes the structure of the IPOIB CA MIB. 119 3.1 Overview 121 The SNMP management of the CA involves the monitoring of key channel 122 adapter attributes. 124 3.2 Discussion of MIB Groups 126 The CA MIB is divided into two basic groups: MIB objects and the 127 conformance group. 129 3.3 The CA MIB Objects 131 The CA MIB objects correlate to the set of Channel Adapter 132 attributes. These attributes are organized into three major CA MIB 133 groups. 135 These are: the General Channel Adapter Info Group, the Channel 136 Adapter Attributes Info Group, and the Channel Adapter Port 137 Attributes and Gid Info Group. 139 3.3.1 The General Channel Adapter Info Group 141 This group provides general information common to any InfiniBand 142 network entity that contains CAs. This includes distinguishing 143 between the HCA and the TCA, displaying the node GUIDs, and showing 144 the number of ports on each CA. 146 3.3.2 The Channel Adapter Attributes Info Group 148 This group provides more specific information about the CAs on a 149 network entity. This includes various attribute flags, transport 150 service support, and other CA characteristics. 152 3.3.3 The Channel Adapter Port Attributes and Gid Info Group 154 This group provides information about the CA ports. This includes 155 the type of physical interfaces supported, other port attributes, 156 and a table containing the port GIDs. 158 3.4 The CA Conformance Group 160 The CA Conformance Group lists the possible compliances for various 161 types of InfiniBand nodes that contain channel adapters. Currently, 162 two types of compliance are defined: basic and full. The units of 163 conformance which define the constituent object groups are also 164 listed. 166 3.4.1 CA Compliance Groups 168 The Compliance Groups list acceptable MIB implementation 169 requirements. 171 4. IPOIB CA MIB Definitions 173 IB-CA-MIB DEFINITIONS ::= BEGIN 175 IMPORTS 176 MODULE-IDENTITY, OBJECT-TYPE, 177 Unsigned32 FROM SNMPv2-SMI 178 TruthValue FROM SNMPv2-TC 180 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 181 infinibandMIB, IbPhysPort FROM IB-TC-MIB; 183 ibCaMIB MODULE-IDENTITY 184 LAST-UPDATED "200610101200Z" -- October 10, 2006 12:00:00 GMT 185 ORGANIZATION "IETF IP Over IB (IPOIB) Working Group" 186 CONTACT-INFO 187 "Hal Rosenstock 188 Postal: HNR Consulting 189 200 Old Harvard Road 190 Boxboro MA 01719-1834 191 United States 192 Email: hnrose@earthlink.net 194 Email comments to the IPOIB WG Mailing List at 195 ipoverib@ietf.org." 196 DESCRIPTION 197 "Copyright (C) The Internet Society (2006). The initial 198 version of this MIB module was published in RFC XXXX; for 199 full legal notices see the RFC itself. Supplementary 200 information may be available on 201 http://www.ietf.org/copyrights/ianamib.html. 203 This module contains managed object definitions for 204 the instrumentation for an InfiniBand Channel Adapter (CA)." 205 REVISION 206 "200610101200Z" -- 10 October 2006 12:00:00 GMT 207 DESCRIPTION 208 "Initial version published as part of RFC XXXX." 209 ::= { infinibandMIB 4 } 211 --**************************************************************** 212 -- Object Identifiers for the IPOIB CA MIB 213 --**************************************************************** 215 ibCaObjects OBJECT IDENTIFIER ::= { ibCaMIB 1 } 216 ibCaConformance OBJECT IDENTIFIER ::= { ibCaMIB 2 } 218 --**************************************************************** 219 -- General Channel Adapter Info Group 220 -- 221 -- DESCRIPTION: This group contains a table that describes 222 -- general information about the Channel Adapters present in 223 -- this Managed System Element. 224 --**************************************************************** 226 ibCaGeneralInfo OBJECT IDENTIFIER ::= { ibCaObjects 1 } 228 --**************************************************************** 229 -- Channel Adapters General Information Table 230 --**************************************************************** 232 ibCaGeneralInfoTable OBJECT-TYPE 233 SYNTAX SEQUENCE OF IbCaGeneralInfoEntry 234 MAX-ACCESS not-accessible 235 STATUS current 236 DESCRIPTION 237 "A table containing general information about the Channel 238 Adapters on this network entity." 239 ::= { ibCaGeneralInfo 1 } 241 ibCaGeneralInfoEntry OBJECT-TYPE 242 SYNTAX IbCaGeneralInfoEntry 243 MAX-ACCESS not-accessible 244 STATUS current 245 DESCRIPTION 246 "A conceptual row of the ibCaGeneralInfoTable containing 247 information about the general characteristics of each 248 Channel Adapter on this network entity." 249 INDEX { ibCaIndex } 250 ::= { ibCaGeneralInfoTable 1 } 252 IbCaGeneralInfoEntry ::= SEQUENCE { 253 ibCaIndex Unsigned32, 254 ibCaType INTEGER, 255 ibCaNodeGuid OCTET STRING, 256 ibCaNumPorts Unsigned32 257 } 259 ibCaIndex OBJECT-TYPE 260 SYNTAX Unsigned32(1..254) 261 MAX-ACCESS not-accessible 262 STATUS current 263 DESCRIPTION 264 "Index that identifies the specific CA on this network 265 entity. The index is defined for a range of CAs from 266 1 to N, where N can have a maximum value of 254." 267 ::= { ibCaGeneralInfoEntry 1 } 269 ibCaType OBJECT-TYPE 270 SYNTAX INTEGER { 271 unknown(1), 272 hca(2), -- host CA 273 tca(3) -- target CA 274 } 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "Type of Channel Adapter: either a Host Channel Adapter (HCA), 279 or a Target Channel Adapter (TCA). The key difference between 280 an HCA and a TCA is that the HCA supports the IBA Verbs layer, 281 while the TCA uses an implementation dependent interface to 282 the transport layer. If the type of CA cannot be determined, 283 the unknown(1) value is returned." 284 REFERENCE 285 "InfiniBand Architecture Release 1.2 Vol. 1. Section 17.1." 286 ::= { ibCaGeneralInfoEntry 2 } 288 ibCaNodeGuid OBJECT-TYPE 289 SYNTAX OCTET STRING (SIZE(8)) 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The GUID of this CA. All ports on the same node shall 294 report the same CA node GUID value. This provides a 295 means for uniquely identifying a CA node within a 296 subnet and helps to determine the co-location of 297 the ports." 298 REFERENCE 299 "InfiniBand Architecture Release 1.2 Vol. 1. Section 17.2.5." 300 ::= { ibCaGeneralInfoEntry 3 } 302 ibCaNumPorts OBJECT-TYPE 303 SYNTAX Unsigned32(1..254) 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "Number of physical IB data ports on this Channel Adapter. 308 Ports 309 are numbered starting from 1. If there is more than one port, 310 the ports are numbered sequentially." 311 REFERENCE 312 "InfiniBand Architecture Release 1.2 Vol. 1. 313 Section 17.2.1.3; Table 313 Port Attributes & Functions." 314 ::= { ibCaGeneralInfoEntry 4 } 316 --**************************************************************** 317 -- Channel Adapter Attributes Info Group 318 -- 319 -- DESCRIPTION: This group contains a table that describes more 320 -- specific attributes about each CA on the network entity. 321 --**************************************************************** 323 ibCaAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 2 } 325 --**************************************************************** 326 -- Channel Adapter Attributes Table 327 --**************************************************************** 329 ibCaAttributeTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF IbCaAttributeEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "A table containing information about the Channel Adapter 335 attributes on this network entity." 336 ::= { ibCaAttrInfo 1 } 338 ibCaAttributeEntry OBJECT-TYPE 339 SYNTAX IbCaAttributeEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "A conceptual row of the ibCaAttributeTable containing 344 information about the general characteristics of each 345 Channel Adapter on this network entity." 346 INDEX { ibCaIndex } 347 ::= { ibCaAttributeTable 1 } 349 IbCaAttributeEntry ::= SEQUENCE { 350 ibCaHasReliableConnection TruthValue, 351 ibCaHasUnreliableConnection TruthValue, 352 ibCaHasReliableDatagram TruthValue, 353 ibCaHasUnreliableDatagram TruthValue, 354 ibCaSupportsAtomicOperations TruthValue, 355 ibCaSupportsOtherOperations TruthValue, 356 ibCaSupportsSolicitedEvents TruthValue, 357 ibCaPathMtuSetSupport INTEGER, 358 ibCaGenEndToEndFlowControl TruthValue, 359 ibCaSupportsMulticast TruthValue, 360 ibCaSupportsAutoPathMigration TruthValue, 361 ibCaSupportsMemoryProtection TruthValue, 362 ibCaSupportsLoopback TruthValue, 363 ibCaSupportsSubnetManager TruthValue 364 } 366 ibCaHasReliableConnection OBJECT-TYPE 367 SYNTAX TruthValue 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "Flag that indicates whether this CA supports 372 Reliable Connection (RC) transport service." 373 REFERENCE 374 "InfiniBand Architecture Release 1.2 Vol. 1. 375 Section 17.2.2; Table 314 Channel Adapter Attributes." 376 ::= { ibCaAttributeEntry 1 } 378 ibCaHasUnreliableConnection OBJECT-TYPE 379 SYNTAX TruthValue 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "Flag that indicates whether this CA supports 384 Unreliable Connection (UC) transport service." 385 REFERENCE 386 "InfiniBand Architecture Release 1.2 Vol. 1. 388 Section 17.2.2; Table 314 Channel Adapter Attributes." 389 ::= { ibCaAttributeEntry 2 } 391 ibCaHasReliableDatagram OBJECT-TYPE 392 SYNTAX TruthValue 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "Flag that indicates whether this CA supports 397 Reliable Datagram (RD) transport service." 398 REFERENCE 399 "InfiniBand Architecture Release 1.2 Vol. 1. 400 Section 17.2.2; Table 314 Channel Adapter Attributes." 401 ::= { ibCaAttributeEntry 3 } 403 ibCaHasUnreliableDatagram OBJECT-TYPE 404 SYNTAX TruthValue 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "Flag that indicates whether this CA supports 409 Unreliable Datagram (UD) transport service." 410 REFERENCE 411 "InfiniBand Architecture Release 1.2 Vol. 1. 412 Section 17.2.2; Table 314 Channel Adapter Attributes." 413 ::= { ibCaAttributeEntry 4 } 415 ibCaSupportsAtomicOperations OBJECT-TYPE 416 SYNTAX TruthValue 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "Flag that indicates whether this CA supports 421 atomic operations. An atomic operation is an operation 422 that is guaranteed to finish without having another 423 operation alter the results once the atomic operation 424 has been initiated." 425 REFERENCE 426 "InfiniBand Architecture Release 1.2 Vol. 1. 427 Section 17.2.2; Table 314 Channel Adapter Attributes." 428 ::= { ibCaAttributeEntry 5 } 430 ibCaSupportsOtherOperations OBJECT-TYPE 431 SYNTAX TruthValue 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "Flag that indicates whether this CA supports 436 all of the other operations (excluding atomic operations) 437 defined for a particular supported transport service." 438 REFERENCE 439 "InfiniBand Architecture Release 1.2 Vol. 1. 440 Section 17.2.2; Table 314 Channel Adapter Attributes." 441 ::= { ibCaAttributeEntry 6 } 443 ibCaSupportsSolicitedEvents OBJECT-TYPE 444 SYNTAX TruthValue 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "Flag that indicates whether this CA supports the 449 generation and reception of solicited events. A solicited 450 event is a feature by which a queue pair consumer on a 451 CA can cause an event to be generated at the destination 452 when its message is received." 453 REFERENCE 454 "InfiniBand Architecture Release 1.2 Vol. 1. 455 Section 17.2.2; Table 314 Channel Adapter Attributes. 456 and Section 9.2.3 Solicited Event (SE) - 1 bit." 457 ::= { ibCaAttributeEntry 7 } 459 ibCaPathMtuSetSupport OBJECT-TYPE 460 SYNTAX INTEGER { 461 mtu256(1), 462 mtu256n512(2), 463 mtu256n512n1024(3), 464 mtu256n512n1024n2048(4), 465 mtu256n512n1024n2048n4096(5) 466 } 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "Set of MTU values (in bytes) supported by this CA for all 471 transport service classes. The Maximum Transfer Unit is the 472 largest size allowable for the packet payload." 473 REFERENCE 474 "InfiniBand Architecture Release 1.2 Vol. 1. 475 Section 17.2.2; Table 314 Channel Adapter Attributes." 476 ::= { ibCaAttributeEntry 8 } 478 ibCaGenEndToEndFlowControl OBJECT-TYPE 479 SYNTAX TruthValue 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "Flag that indicates whether this CA supports 484 the generation of end-to-end flow control. End-to-end 485 flow control is a mechanism that prevents sending messages 486 when the destination does not have adequate receive buffers 487 to receive the message." 488 REFERENCE 489 "InfiniBand Architecture Release 1.2 Vol. 1. 490 Section 17.2.2; Table 314 Channel Adapter Attributes." 491 ::= { ibCaAttributeEntry 9 } 493 ibCaSupportsMulticast OBJECT-TYPE 494 SYNTAX TruthValue 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "Flag that indicates whether this CA supports multicast 499 operations. Multicast is the ability to deliver a single 500 packet to multiple ports." 501 REFERENCE 502 "InfiniBand Architecture Release 1.2 Vol. 1. 503 Section 17.2.2; Table 314 Channel Adapter Attributes." 504 ::= { ibCaAttributeEntry 10 } 506 ibCaSupportsAutoPathMigration OBJECT-TYPE 507 SYNTAX TruthValue 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "Flag that indicates whether this CA supports 512 automatic path migration. Automatic path migration 513 is the process by which a CA (on a per QP basis) 514 signals another CA to cause path migration to a 515 preset alternate path." 516 REFERENCE 517 "InfiniBand Architecture Release 1.2 Vol. 1. 518 Section 17.2.2; Table 314 Channel Adapter Attributes." 519 ::= { ibCaAttributeEntry 11 } 521 ibCaSupportsMemoryProtection OBJECT-TYPE 522 SYNTAX TruthValue 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "Flag that indicates whether this CA supports InfiniBand 527 memory management protection mechanisms." 528 REFERENCE 529 "InfiniBand Architecture Release 1.2 Vol. 1. 530 Section 17.2.2; Table 314 Channel Adapter Attributes. 531 and Section 10.6 Memory Management." 532 ::= { ibCaAttributeEntry 12 } 534 ibCaSupportsLoopback OBJECT-TYPE 535 SYNTAX TruthValue 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "Flag that indicates whether this CA supports 540 loopback operations. Loopback support allows for the 541 sending and receiving of self-addressed packets that 542 do not go out on the wire. If this feature is supported, 543 self-addressed packets must work, even if no switch is 544 present." 545 REFERENCE 546 "InfiniBand Architecture Release 1.2 Vol. 1. 547 Section 17.2.2; Table 314 Channel Adapter Attributes." 548 ::= { ibCaAttributeEntry 13 } 550 ibCaSupportsSubnetManager OBJECT-TYPE 551 SYNTAX TruthValue 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "Flag that indicates whether this CA supports 556 a Subnet Manager (SM) instance." 557 REFERENCE 558 "InfiniBand Architecture Release 1.2 Vol. 1. 559 Section 17.2.2; Table 314 Channel Adapter Attributes." 560 ::= { ibCaAttributeEntry 14 } 562 --**************************************************************** 563 -- Channel Adapter Port Attributes and GID Info Group 564 -- 565 -- DESCRIPTION: This group contains information about the CA ports 566 -- on the network entity and the GID table associated with each 567 -- port. 568 --**************************************************************** 570 ibCaPortAttrInfo OBJECT IDENTIFIER ::= { ibCaObjects 3 } 572 --**************************************************************** 573 -- Channel Adapter Port Attribute Table 574 --**************************************************************** 576 ibCaPortAttributeTable OBJECT-TYPE 577 SYNTAX SEQUENCE OF IbCaPortAttributeEntry 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "A table containing information about the Channel Adapter 582 port attributes on this network entity." 583 ::= { ibCaPortAttrInfo 1 } 585 ibCaPortAttributeEntry OBJECT-TYPE 586 SYNTAX IbCaPortAttributeEntry 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION 590 "A conceptual row of the ibCaPortAttributeTable containing 591 information about the general characteristics of each 592 Channel Adapter port on this network entity." 593 INDEX { ibCaIndex, ibCaPortIndex } 594 ::= { ibCaPortAttributeTable 1 } 596 IbCaPortAttributeEntry ::= SEQUENCE { 597 ibCaPortIndex IbPhysPort, 598 ibCaPortGuid OCTET STRING, 599 ibCaPhysicalInterface INTEGER, 600 ibCaSupportsStaticRateControl TruthValue, 601 ibCaInterpacketDelayValue Unsigned32, 602 ibCaSupportsMultipathing TruthValue, 603 ibCaValidatesInPktDlid TruthValue, 604 ibCaMaxGidsPerPort Unsigned32 605 } 607 ibCaPortIndex OBJECT-TYPE 608 SYNTAX IbPhysPort 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "Index that identifies the InfiniBand data port. The IBA 613 defines a range of valid data ports from 1 to N, where 614 N can have a maximum value of 254 for an IBA switch." 615 ::= { ibCaPortAttributeEntry 1 } 617 ibCaPortGuid OBJECT-TYPE 618 SYNTAX OCTET STRING (SIZE(8)) 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The GUID of this CA port. All ports on the same CA shall 623 report a unique ibCaPortGuid value. This provides a means 624 for uniquely identifying a CA port on a node within a subnet 625 and helps to determine the co-location of the ports." 626 REFERENCE 627 "InfiniBand Architecture Release 1.2 Vol. 1. Section 17.2.5." 628 ::= { ibCaPortAttributeEntry 2 } 630 ibCaPhysicalInterface OBJECT-TYPE 631 SYNTAX INTEGER { 632 cable(1), 633 fiber(2), 634 backplane(3) 635 } 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The physical interface for this CA. When the value 640 is cable(1), the CA supports a cable connector physical 641 interface. This physical attach point is defined for use 642 with copper cables. When the value is fiber(2), the CA 643 supports a fiber connector physical interface. This 644 physical attach point is defined for use with optical 645 cables. When the value is backplane(3), the CA supports 646 a backplane connector physical interface. This physical 647 attach point is defined for accepting a specified form 648 factor that houses the channel adapter." 649 REFERENCE 650 "InfiniBand Architecture Release 1.2 Vol. 1. 651 Section 17.2.1.3 Port Attributes and Functions; 652 Vol. 2. 3.1 Introduction (Physical Layer Overview)." 653 ::= { ibCaPortAttributeEntry 3 } 655 ibCaSupportsStaticRateControl OBJECT-TYPE 656 SYNTAX TruthValue 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "Flag that indicates whether this CA supports static 661 rate control. Static rate controls are required for 662 all IB ports that support a data rate over 2.5 Gbps." 663 REFERENCE 664 "InfiniBand Architecture Release 1.2 Vol. 1. 665 Section 17.2.6 Static Rate Control." 666 ::= { ibCaPortAttributeEntry 4 } 668 ibCaInterpacketDelayValue OBJECT-TYPE 669 SYNTAX Unsigned32 (0..255) 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "Interpacket Delay Value (IPD) supported for CAs that have 674 static rate control (i.e., the ibCaSupportsStaticRateControl 675 object must have a value of true(1) for this object to 676 contain a valid value; Otherwise, 0 is returned). 677 The IPD allows for the slowing of the packet rate for all 678 of the standard link rates." 679 REFERENCE 680 "InfiniBand Architecture Release 1.2 Vol. 1. 682 Section 17.2.6 Static Rate Control, and Table 315 683 Static Rate Control IPD Values. 684 Section 9.11.1 Static Rate Control for Heterogeneous Links, 685 and Table 63 Inter Packet Delay" 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.2 Vol. 1. 701 Section 17.2.1.3 and Table 313 Port Attributes & Functions; 702 Also, Section 7.11.1 Multipathing Requirements on End Node." 703 ::= { ibCaPortAttributeEntry 6 } 705 ibCaValidatesInPktDlid OBJECT-TYPE 706 SYNTAX TruthValue 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "Flag that indicates whether this CA supports the validation 711 of incoming packet DLIDs, and if the GRH is present, the 712 DGID." 713 REFERENCE 714 "InfiniBand Architecture Release 1.2 Vol. 1. 715 Section 17.2.1.3. and Table 313 Port Attributes & Functions." 716 ::= { ibCaPortAttributeEntry 7 } 718 ibCaMaxGidsPerPort OBJECT-TYPE 719 SYNTAX Unsigned32(1..65535) 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "Maximum number of GIDs per port. The maximum number of 724 unicast GIDs supported per CA port is implementation specific. 725 Each port will support at least one (1) GID." 726 REFERENCE 727 "InfiniBand Architecture Release 1.2 Vol. 1. 728 Section 17.2.1.3. and Table 313 Port Attributes & Functions." 729 ::= { ibCaPortAttributeEntry 8 } 731 --**************************************************************** 732 -- Channel Adapter Port Global Identifier (GID) Table 733 --**************************************************************** 735 ibCaPortGidTable OBJECT-TYPE 736 SYNTAX SEQUENCE OF IbCaPortGidEntry 737 MAX-ACCESS not-accessible 738 STATUS current 739 DESCRIPTION 740 "A table containing the port GIDs for each CA." 741 ::= { ibCaPortAttrInfo 2 } 743 ibCaPortGidEntry OBJECT-TYPE 744 SYNTAX IbCaPortGidEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "A conceptual row of the ibCaPortGidTable containing 749 information about a particular GID on an IB port 750 for a particular CA." 751 INDEX { ibCaIndex, ibCaPortIndex, ibCaPortGidIndex } 752 ::= { ibCaPortGidTable 1 } 754 IbCaPortGidEntry ::= SEQUENCE { 755 ibCaPortGidIndex Unsigned32, 756 ibCaPortGidValue OCTET STRING 757 } 759 ibCaPortGidIndex OBJECT-TYPE 760 SYNTAX Unsigned32(1..65535) 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "Index that identifies the GID entry for this IB data port. 765 Each port on a CA is assigned at least 1 unicast GID. 766 Note, the value of ibCaPortGidIndex will never be greater 767 than the value of ibCaMaxGidsPerPort that defines the 768 upper value for this index." 769 ::= { ibCaPortGidEntry 1 } 771 ibCaPortGidValue OBJECT-TYPE 772 SYNTAX OCTET STRING (SIZE(16)) 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The Global Identifier (GID) is a 128-bit (16-byte) unicast 777 or multicast identifier used to identify a channel adapter 778 port. A GID is a valid 128-bit IPv6 address (as defined in 779 RFC 2373) with additional IBA modifications that facilitate 780 node discovery, routing, and communications." 781 REFERENCE 782 "InfiniBand Architecture Release 1.2 Vol. 1. 783 Section 4.1.1 GID Usage and Properties." 784 ::= { ibCaPortGidEntry 2 } 786 --**************************************************************** 787 -- Module Conformance Statement 788 -- 789 -- DESCRIPTION: The module conformance statement includes the 790 -- compliance statements and the units of conformance 791 -- section. 792 --**************************************************************** 794 ibCaCompliances OBJECT IDENTIFIER ::= { ibCaConformance 1 } 796 ibCaGroups OBJECT IDENTIFIER ::= { ibCaConformance 2 } 798 --**************************************************************** 799 -- Compliance Statements 800 --**************************************************************** 802 ibCaBasicCompliance MODULE-COMPLIANCE 803 STATUS current 804 DESCRIPTION 805 "The basic CA implementation requirements for agents that 806 support the IPOIB CA MIB." 808 MODULE -- this module 809 MANDATORY-GROUPS { 810 ibCaGeneralGroup 811 } 812 ::= { ibCaCompliances 1 } 814 ibCaFullCompliance MODULE-COMPLIANCE 815 STATUS current 816 DESCRIPTION 817 "The complete node implementation requirements for agents that 818 support the full IPOIB CA MIB." 819 MODULE -- this module 820 MANDATORY-GROUPS { 821 ibCaGeneralGroup, 822 ibCaAttrGroup, 823 ibCaPortAttrGroup, 824 ibCaPortGidGroup 825 } 826 ::= { ibCaCompliances 2 } 828 --**************************************************************** 829 -- Units of Conformance 830 --**************************************************************** 832 ibCaGeneralGroup OBJECT-GROUP 833 OBJECTS { 834 ibCaType, 835 ibCaNodeGuid, 836 ibCaNumPorts 837 } 838 STATUS current 839 DESCRIPTION 840 "The ibCaGeneralGroup defines the MIB objects that describe 841 the general characteristics of this Channel Adapter." 842 ::= { ibCaGroups 1 } 844 ibCaAttrGroup OBJECT-GROUP 845 OBJECTS { 846 ibCaHasReliableConnection, 847 ibCaHasUnreliableConnection, 848 ibCaHasReliableDatagram, 849 ibCaHasUnreliableDatagram, 850 ibCaSupportsAtomicOperations, 851 ibCaSupportsOtherOperations, 852 ibCaSupportsSolicitedEvents, 853 ibCaPathMtuSetSupport, 854 ibCaGenEndToEndFlowControl, 855 ibCaSupportsMulticast, 856 ibCaSupportsAutoPathMigration, 857 ibCaSupportsMemoryProtection, 858 ibCaSupportsLoopback, 859 ibCaSupportsSubnetManager 860 } 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. Revision History 921 This section should be removed when this document is published as an 922 RFC. 924 7.1 Changes from 925 Replaced IbDataPort with IbPhysPort 927 Updated to InfiniBand Architecture Revision 1.2 from 1.1 929 8. References 931 8.1 Normative References 933 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 934 Requirement Levels", BCP 14, RFC 2119, March 1997. 936 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 937 IANA Considerations Section in RFCs", BCP: 26, RFC 2434, 938 October 1998. 940 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 941 Rose, M. and S. Waldbusser, "Structure of Management 942 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 943 1999. 945 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 946 Rose, M. and S. Waldbusser, "Textual Conventions for 947 SMIv2", STD 58, RFC 2579, April 1999. 949 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 950 Rose, M. and S. Waldbusser, "Conformance Statements for 951 SMIv2", STD 58, RFC 2580, April 1999. 953 [INFINIV1] InfiniBand Architecture Specification Volume 1, 954 Release 1.2, October, 2004, Final Release. 956 8.2 Informative References 958 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 959 "Introduction and Applicability Statements for 960 Internet-Standard Management Framework", RFC 3410, 961 December 2002. 963 9. Acknowledgements 965 This MIB module was updated based on the original work done by Sean 966 Harnedy. 968 10. Author's Addresses 970 Hal Rosenstock 971 HNR Consulting 972 200 Old Harvard Road 973 Boxboro, MA 01719-1834 974 USA 975 Email: hnrose@earthlink.net 977 11. Intellectual Property Notice 979 The IETF takes no position regarding the validity or scope of any 980 Intellectual Property Rights or other rights that might be claimed 981 to pertain to the implementation or use of the technology 982 described in this document or the extent to which any license 983 under such rights might or might not be available; nor does it 984 represent that it has made any independent effort to identify any 985 such rights. Information on the procedures with respect to rights 986 in RFC documents can be found in BCP 78 and BCP 79. 988 Copies of IPR disclosures made to the IETF Secretariat and any 989 assurances of licenses to be made available, or the result of an 990 attempt made to obtain a general license or permission for the use 991 of such proprietary rights by implementers or users of this 992 specification can be obtained from the IETF on-line IPR repository 993 at http://www.ietf.org/ipr. 995 The IETF invites any interested party to bring to its attention 996 any copyrights, patents or patent applications, or other 997 proprietary rights that may cover technology that may be required 998 to implement this standard. Please address the information to the 999 IETF at ietf-ipr@ietf.org. 1001 12. Full Copyright Statement 1003 Copyright (C) The Internet Society (2006). This document is 1004 subject to the rights, licenses and restrictions contained in BCP 1005 78, and except as set forth therein, the authors retain all their 1006 rights. 1008 This document and translations of it may be copied and 1009 furnished to others, and derivative works that comment on 1010 or otherwise explain it or assist in its implementation may 1011 be prepared, copied, published and distributed, in whole or 1012 in part, without restriction of any kind, provided that the 1013 above copyright notice and this paragraph are included on 1014 all such copies and derivative works. However, this document 1015 itself may not be modified in any way, such as by removing the 1016 copyright notice or references to the Internet Society or other 1017 Internet organizations, except as needed for the purpose of 1018 developing Internet standards in which case the procedures for 1019 copyrights defined in the Internet Standards process must be 1020 followed, or as required to translate it into languages other 1021 than English. 1023 The limited permissions granted above are perpetual and 1024 will not be revoked by the Internet Society or its 1025 successors or assigns. 1027 This document and the information contained herein are provided 1028 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1029 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 1030 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 1031 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 1032 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1033 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1034 PARTICULAR PURPOSE. 1036 Acknowledgment 1038 Funding for the RFC Editor function is currently provided by the 1039 Internet Society.