INTERNET-DRAFT Sean Harnedy
Mangrove Systems, Inc.
Expiration Date: November 2003 May 2003
Definitions of Textual Conventions
and OBJECT-IDENTITIES for
IP Over InfiniBand (IPOVERIB) Management
<draft-ietf-ipoib-ibmib-tc-mib-03.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to
the IP Over IB (ipoib) Working Group, ipoverib@ietf.org.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This memo describes Textual Conventions and OBJECT-IDENTITIES
for use in definitions of management information for IP Over
InfiniBand (IPOVERIB) networks. The intent is that these TEXTUAL
CONVENTIONs (TCs) will be imported and used in IPOVERIB related
MIB modules.
Harnedy Expires November 2003 [Page 1]
Internet-Draft IPOVERIB TC MIB May 2003
Table of Contents
1. Introduction ............................................... 2
2. Terminology ................................................ 2
3. The Internet-Standard Management Framework ................. 2
4. IPOVERIB Textual Conventions MIB Definitions ............... 3
5. Intellectual Property Notice ............................... 0
6. Normative References ....................................... 9
7. Informative References ..................................... 9
8. Security Considerations .................................... 8
9. Acknowledgments ............................................ 8
10. Author's Address .......................................... 9
11. Full Copyright Statement .................................. 1
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines Textual Conventions used in IETF IPOVERIB
and IPOVERIB-related MIBs.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
For an introduction to the concepts of InfiniBand, see [INFINIV1].
3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
Harnedy Expires November 2003 [Page 2]
Internet-Draft IPOVERIB TC MIB May 2003
4. IPOVERIB Textual Conventions MIB Definitions
IB-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental, MODULE-IDENTITY, Integer32
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
ibTcMIB MODULE-IDENTITY
LAST-UPDATED "200305271200Z" -- 27 May 2003 12:00:00 GMT
ORGANIZATION
"IETF IP over IB Working Group
Email: ipoverib@ietf.org"
CONTACT-INFO
"Sean Harnedy
Postal: Mangrove Systems, Inc.
10 Fairfield Boulevard
Wallingford, CT 06492
United States
Tel: 203 679 7539
Email: sharnedy@mangrovesystems.com
"
DESCRIPTION
"Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFCXXXX; see the RFC itself
for full legal notices.
This MIB contains managed object definitions and textual
conventions for managing InfiniBand devices that support
the IP Over InfiniBand (IPOIB) protocols and procedures."
-- Revision history.
REVISION
"200305271200Z" -- 27 May 2003 12:00:00 GMT
DESCRIPTION
"Updated Author information. Updated MIB boilerplate
section, general format adjustment to adhere to
guidelines for Internet Draft writers and MIB authors."
REVISION
"200301011200Z" -- 1 January 2003 12:00:00 GMT
DESCRIPTION
"Updated for IBTA Specification Version 1.1."
REVISION
"200205101200Z" -- 10 May 2002 12:00:00 GMT
DESCRIPTION
"Deleted ibPortTC. Changed ibPhysicalPort to IbDataPort
and changed range to (1..254) to match IB port numbering.
Changed IbValidPhysicalPort to IbDataPortAndInvalid and
changed range to (1..255). Corrected definition of
IbMulticastLid to end at 65536. Added
Harnedy Expires November 2003 [Page 3]
Internet-Draft IPOVERIB TC MIB May 2003
IbIpoibClientIdentifier TC."
REVISION
"200111131200Z" -- 13 November 2001 12:00:00 GMT
DESCRIPTION
"Separated TCs from InfiniBand Interface MIB. Added IANA
experimental number for MIB. Made TC names more consistent.
Added Intellectual Property and Acknowledgment sections."
REVISION
"200110031200Z" -- 3 October 2001 12:00:00 GMT
DESCRIPTION
"Initial version of this MIB."
::= { infinibandMIB 1 }
-- The IANA has defined the InfiniBand MIB on the experimental branch.
infinibandMIB OBJECT IDENTIFIER ::= { experimental 117 }
-- Textual Conventions.
IbDataPort ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies a physical IB Port. The IBA defines a maximum of 254
physical ports numbered Port 1 to Port 254. A port is the
location on a Channel Adapter, IB Router, or IB Switch to which
a link is connected. If a device has N ports, the ports are
always numbered from 1 to N. Note: this definition does NOT
include logical Port 0 that is reserved for IB management
packets."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 18.2.4.1 (C18-10.a1) for switches, Section 17.2.1.3
(C17-7.a1) for Channel Adapters, and Section 19.2.4.2 for
routers."
SYNTAX Integer32 (1..254)
IbDataPortAndInvalid ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies a physical IB port plus an invalid port number.
Note: this definition does NOT include logical Port 0
that is reserved for IB management packets."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 18.2.4.1 (C18-10.a1) for switches, Section 17.2.1.3
(C17-7.a1) for Channel Adapters, and Section 19.2.4.2 for
routers."
SYNTAX Integer32 (1..255)
Harnedy Expires November 2003 [Page 4]
Internet-Draft IPOVERIB TC MIB May 2003
IbVirtualLane ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies a Virtual Lane (VL) instance on a given interface
(i.e., IB port). VLs provide a mechanism for creating multiple
virtual links within a physical link. IBA defines VL 0 through
VL 14 for data and VL 15 exclusively for Subnet Management.
The actual data VLs that a port uses are configured by the
Subnet Manager. The default data VL is always VL 0. Note: this
definition is +1-based."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 3.5.7."
SYNTAX Integer32 (1..16)
IbDataVirtualLane ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies a Data Virtual Lane instance on a given interface
(i.e., IB port). This TC definition excludes the management
Virtual Lane (VL 15). The actual data VLs that a port uses
are configured by the Subnet Manager. The default data VL is
always the first VL (VL 0). Note: this definition is +1-based."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 3.5.7."
SYNTAX Integer32 (1..15)
IbDlid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies the Destination Local Identifier (DLID). The IBA
defines LID 0 as reserved and valid LID values from 1 to 65535.
LID 65535 is defined as a permissive DLID.
This value is stored in IBA defined bit order, that is, the
high-order bit of the Local Identifier byte 0 is positioned as
the high-order bit of the first byte of the integer
representation.
Note: this definition is +1-based."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 4.1.3."
SYNTAX Integer32 (1..65536)
Harnedy Expires November 2003 [Page 5]
Internet-Draft IPOVERIB TC MIB May 2003
IbUnicastLid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies a Unicast LID. Value is stored in IBA defined bit
order, that is, the high-order bit of the Local Identifier
byte 0 is positioned as the high-order bit of the first byte
of the integer representation.
Note: this definition is +1-based."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 4.1.3."
SYNTAX Integer32 (1..49152)
IbMulticastLid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Identifies a Multicast LID. Value is stored in IBA defined
bit order, that is, the high-order bit of the Local
Identifier byte 0 is positioned as the high-order bit of the
first byte of the integer representation.
Note: this definition is +1-based."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1].
Section 4.1.3."
SYNTAX Integer32 (49153..65536)
IbGuid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"Globally Unique Identifier (GUID) is a number that uniquely
identifies a IB device or component. It is a compliant EUI-64
identifier for channel adapters, routers, and switches.
This 64-bit value is created by concatenating a 24-bit
company ID value and a 40-bit extension. The IEEE Registration
Authority assigns the company ID. The extension ID is assigned
by the particular company. Therefore, each HCA, TCA, switch, and
router shall be assigned an EUI-64 GUID by the manufacturer."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 4.1."
SYNTAX OCTET STRING (SIZE(8))
Harnedy Expires November 2003 [Page 6]
Internet-Draft IPOVERIB TC MIB May 2003
IbSmPortList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Each bit mapping within this value specifies a port presence
within the managed IB device. This definition includes bit0
as IB Port 0, the logical port used exclusively for management
packets. Valid data port mappings are from bit1 to bit254.
Bit255 is invalid."
REFERENCE
"InfiniBand Architecture Release 1.1 Vol 1. [INFINIV1]
Section 18.2.4.1 (C18-10.a1) for switches, Section 17.2.1.3
(C17-7.a1) for Channel Adapters, and Section 19.2.4.2 for
routers."
SYNTAX OCTET STRING (SIZE(32))
IbIpoibClientIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The IPOIB Client Identifier uniquely identifies an IPOIB link
layer address associated with the InfiniBand port. It comprises
three fields.
1. reserved
2. Queue Pair Number field (QPN)
3. Global Identifier (GID)
+................+................+................+...............+
|20: (reserved) |19: QPN[23-16] |18: QPN[15-8] |17: QPN[7-0] |
+................+................+................+...............+
|16: GID[127-120]|15: GID[119-112]|14: GID[111-104]|13: GID[103-96]|
+................+................+................+...............+
|12: GID[95-88] |11: GID[87-80] |10: GID[79-72] |9 GID[71-64] |
+................+................+................+...............+
|8: GID[63-56] |7: GID[55-48] |6: GID[47-40] |5: GID[39-32] |
+................+................+................+...............+
|4: GID[31-24] |3: GID[23-16] |2: GID[15-8] |1: GID[7-0] |
+................+................+................+...............+
The reserved field is octet 20. It is reserved for future use.
These bits MUST be set to zero.
The Queue Pair Number field is a 3 octet field (octets 17, 18, &
19) that identifies the destination queue pair. Note: The
reserved field and the QPN field are collectively referred to as
the interface-id. If an IPOIB interface has only 1 GID
associated with it, the interface-id MAY contain all zeroes.
The Global Identifier field is a 16 octet field (octets 1
through 16) that is formed by the combination of the IB subnet
prefix and the port's GUID. It is unique in the InfiniBand
fabric. NOTE: An IPOIB interface may have more than 1 GID
associated with it."
SYNTAX OCTET STRING (SIZE(20))
Harnedy Expires November 2003 [Page 7]
Internet-Draft IPOVERIB TC MIB May 2003
END
5. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
6. Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[INFINIV1] InfiniBand Architecture Specification Volume 1,
Release 1.1, November 6, 2002.
7. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Harnedy Expires November 2003 [Page 8]
Internet-Draft IPOVERIB TC MIB May 2003
8. Security Considerations
This memo defines textual conventions and object identities for use
in IPOVERIB MIB modules. Security issues for these MIB modules are
addressed in the memos defining those modules. Because this memo
does not define management objects, the memo has no impact on the
security of the Internet.
9. Acknowledgments
This MIB module was updated based on the original work done by Bill
Anderson and Bill Strahm.
10. Author's Address
Sean Harnedy
Mangrove Systems, Inc.
10 Fairfield Boulevard
Wallingford, CT 06492
Phone: +1-203-679-7539
Email: sharnedy@mangrovesystems.com
11. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and
furnished to others, and derivative works that comment on
or otherwise explain it or assist in its implementation may
be prepared, copied, published and distributed, in whole or
in part, without restriction of any kind, provided that the
above copyright notice and this paragraph are included on
all such copies and derivative works. However, this document
itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other
than English.
The limited permissions granted above are perpetual and
will not be revoked by the Internet Society or its
successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Harnedy Expires November 2003 [Page 9]
