IB-TC-MIB
File:
IB-TC-MIB.mib (19402 bytes)
Imported modules
Imported symbols
Defined Types
| IbPort |
|
| Identifies an InfiniBand (IB) Port. The InfiniBand
Architecture (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 physical ports are
always numbered from 1 to N. The relationship between an
InfiniBand port and an ifIndex is one-to-one. As such, the
value of an ifIndex object instance can be directly used to
identify corresponding instances of the objects defined
herein as IB ports. Note: this definition does include
enhanced switch port 0 but not base switch port 0. In the
case of a switch with enhanced switch port 0, the ifIndex is
offset by 1 from the ibPort. In all other cases, the ifIndex
is identical to the ibPort. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..254 |
|
| IbPhysPort |
|
| Identifies a physical InfiniBand (IB) Port. The InfiniBand
Architecture (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
switch Port 0, which is not a physical port. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..254 |
|
| IbPhysPortAndInvalid |
|
| Identifies a physical IB port plus an invalid port number.
The invalid port number has a value of 255. Note: this
definition does NOT include switch logical Port 0, which is
not a physical port. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..255 |
|
| IbDataPort |
|
| Identifies a physical InfiniBand (IB) Port. The InfiniBand
Architecture (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. The relationship between an InfiniBand
port and an ifIndex is one-to-one. As such, the value of an
ifIndex object instance can be directly used to identify
corresponding instances of the objects defined herein as IB
data ports. Note: this definition does NOT include logical
Port 0, which is reserved for IB management packets. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..254 |
|
| IbDataPortAndInvalid |
|
| Identifies a physical IB port plus an invalid port number.
The invalid port number has a value of 255. Note: this
definition does NOT include logical Port 0, which is reserved
for IB management packets. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..255 |
|
| IbVirtualLane |
|
| 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..15 |
|
| IbDataVirtualLane |
|
| 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). |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..14 |
|
| IbDlid |
|
| Identifies the Destination Local Identifier (DLID). The IBA
defines LID 0 as reserved and valid Local Identifier (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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..65535 |
|
| IbUnicastLid |
|
| 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..49151 |
|
| IbMulticastLid |
|
| 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
49152..65535 |
|
| IbGuid |
|
| Globally Unique Identifier (GUID) is a number that uniquely
identifies an IB device or component. It is a compliant
IEEE-defined 64-bit extended unique identifier (EUI-64)
for Host Channel Adapters (HCA), Terminal Channel Adpaters
(TCA), 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. Each HCA, TCA, switch, and router as well as each
endport shall be assigned an EUI-64 GUID by the
manufacturer. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(8) |
|
| IbSmaPortList |
|
| Each bit mapping within this value specifies a port presence
within the managed IB device. This definition includes bit0
as IB Port 0, the switch management port. Valid physical
port mappings are from bit1 to bit254. Bit255 is invalid
and MUST always be zero. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(32) |
|
| IbSmPortList |
|
| 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 and MUST always be zero. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(32) |
|
| IbIpoibClientIdentifier |
|
| The IPOIB Client Identifier uniquely identifies an IPOIB link
layer address associated with the InfiniBand port. It
comprises three fields.
1. Global Identifier (GID)
2. Queue Pair Number field (QPN)
3. reserved
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1:GID(0-7) |2:GID(8-15) |3:GID(16-23) |4:GID(24-31) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|5:GID(32-39) |6:GID(40-47) |7:GID(48-55) |8:GID(56-63) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|9:GID(64-71) |10:GID(72-79) |11:GID(80-87) |12:GID(88-95) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|13:GID(96-103) |14:GID(104-111)|15:GID(112-119)|16:GID(120-127)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|17:QPN(0-7) |18:QPN(8-15) |19:QPN(16-23) |20:(reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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.
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 reserved field is octet 20. It is reserved for future
use. These bits SHOULD be set to zero. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(20) |
|
| IbSmSubnetPrefix |
|
| The 64-bit value used to identify an InfiniBand subnet. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(8) |
|
| IbSmState |
|
| Subnet Manager's state:
notActive(0) SM is not active
discovering(1) SM is discovering subnet
standby(2) SM is in standby role
master(3) SM is in master role. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
notActive(0), discovering(1), standby(2), master(3) |
|
| IbNodeType |
|
| Type of InfiniBand node. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
unknown(0), channelAdapter(1), switch(2), router(3) |
|
| IbMtu |
|
| The MTU size of this InfiniBand link. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
mtu256(1), mtu512(2), mtu1024(3), mtu2048(4), mtu4096(5) |
|
| IbPartition |
|
| The 15-bit Partition Key Base (without the membership bit). |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..32767 |
|
| IbTransportTime |
|
| The time value used to calculate the InfiniBand network
delay or response. The duration of time is calculated
by the following formula:
delay/response = (4.096 microseconds * 2 ^ IbTransportTime). |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
0..31 |
|
Defined Values
| ibTcMIB |
1.3.6.1.3.117.1 |
| Copyright (C) The Internet Society (2006). The initial
version of this MIB module was published in RFC XXXX; for
full legal notices see the RFC itself. Supplementary
information may be available on
http://www.ietf.org/copyrights/ianamib.html.
This MIB contains managed object definitions and textual
conventions for managing InfiniBand devices that support
the IP Over InfiniBand (IPOIB) protocols and procedures. |
| MODULE-IDENTITY |
|
|
|