OID reference

mlxIBCAType

1.3.6.1.4.1.33049.2.5.1.2.1.18

Description

Type of Channel Adapter; either a Host Channel Adapter (HCA), or a Target Channel Adapter (TCA). The key difference between an HCA and a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses an implementation dependent interface to the transport layer. If the type of CA cannot be determined, the unknown(1…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.33049.2.5.1.2.1 (mlxIBCAInfoEntry)
Node code
18
Node name
mlxIBCAType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.33049.2.5.1.2.1.18
URN notation
urn:oid:1.3.6.1.4.1.33049.2.5.1.2.1.18
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 33049 2 5 1 2 1 18}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mellanox(33049) mellanoxMgmt(2) mlxIBObjects(5) mlxIBCAInfoGroup(1) mlxIBCAInfoTable(2) mlxIBCAInfoEntry(1) mlxIBCAType(18)}
OID-IRI notation
  • /1/3/6/1/4/1/33049/2/5/1/2/1/18
  • /ISO/Identified-Organization/6/1/4/1/33049/2/5/1/2/1/18
  • /ISO/3/6/1/4/1/33049/2/5/1/2/1/18
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/enterprise/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/enterprises/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/enterprises/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/vendor-objects/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/identified-organization/dod/internet/private/vendor-objects/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/enterprise/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/enterprise/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/enterprises/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/enterprises/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/ldap-enterprise/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/ldap-enterprise/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/vendor-objects/33049/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • /iso/org/dod/internet/private/vendor-objects/mellanox/mellanoxMgmt/mlxIBObjects/mlxIBCAInfoGroup/mlxIBCAInfoTable/mlxIBCAInfoEntry/mlxIBCAType
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current

Enumerated values

Notes below names come from selected MIB definitions.

ValueName and source notes
1unknown
2hca
host CA
3tca
target CA

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: mlxIBCAIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.33049.2.5.1.2.1.18

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

mlxIBCAType · current

mlxIBCAType  OBJECT-TYPE
	SYNTAX     INTEGER {
		unknown (1),
		hca (2),
		tca (3)
	}
	MAX-ACCESS read-only
	STATUS     current
	DESCRIPTION 
		"Type of Channel Adapter; either a Host Channel Adapter (HCA), or a
		         Target Channel Adapter (TCA). The key difference between an HCA and
		         a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses
		         an implementation dependent interface to the transport layer. If the
		         type of CA cannot be determined, the unknown(1) value is returned."
	REFERENCE 
		"InfiniBand Architecture Release 1.2.1 Vol. 1 Section 17.1"
	::= { mlxIBCAInfoEntry 18 }

mlxIBCAType · current

mlxIBCAType OBJECT-TYPE
    SYNTAX INTEGER {
        unknown(1),
        hca(2), -- host CA
        tca(3)  -- target CA
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Type of Channel Adapter; either a Host Channel Adapter (HCA), or a
         Target Channel Adapter (TCA). The key difference between an HCA and
         a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses
         an implementation dependent interface to the transport layer. If the
         type of CA cannot be determined, the unknown(1) value is returned."
    REFERENCE
         "InfiniBand Architecture Release 1.2.1 Vol. 1 Section 17.1"
    ::= { mlxIBCAInfoEntry 18 }

mlxIBCAType · current

mlxIBCAType OBJECT-TYPE
    SYNTAX INTEGER {
        unknown(1),
        hca(2), -- host CA
        tca(3)  -- target CA
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Type of Channel Adapter; either a Host Channel Adapter (HCA), or a
         Target Channel Adapter (TCA). The key difference between an HCA and
         a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses
         an implementation dependent interface to the transport layer. If the
         type of CA cannot be determined, the unknown(1) value is returned."
    REFERENCE
         "InfiniBand Architecture Release 1.2.1 Vol. 1 Section 17.1"
    ::= { mlxIBCAInfoEntry 18 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Type of Channel Adapter; either a Host Channel Adapter (HCA), or a Target Channel Adapter (TCA). The key difference between an HCA and a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses an implementation dependent interface to the transport layer. If the type of CA cannot be determined, the unknown(1) value is returned.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Reviewed vendor MIB copies in Fujitsu ServerViewNetdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Reviewed vendor MIB copies in Fujitsu ServerView, and others1 record · 7 sources

Description 1

mlxIBCAType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Reviewed vendor MIB copies in Fujitsu ServerView, and others7 sources

Status in source: current.

Names: mlxIBCAType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mlxIBCAType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unknown",
    "(",
    "1",
    ")",
    ",",
    "hca",
    "(",
    "2",
    ")",
    ",",
    "tca",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Type of Channel Adapter; either a Host Channel Adapter (HCA), or a Target Channel Adapter (TCA). The key difference between an HCA and a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses an implementation dependent interface to the transport layer. If the type of CA cannot be determined, the unknown(1) value is returned.\"",
    "REFERENCE",
    "\"InfiniBand Architecture Release 1.2.1 Vol. 1 Section 17.1\"",
    "::=",
    "{",
    "mlxIBCAInfoEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unknown",
            1
          ],
          [
            "hca",
            2
          ],
          [
            "tca",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Type of Channel Adapter; either a Host Channel Adapter (HCA), or a Target Channel Adapter (TCA). The key difference between an HCA and a TCA is that the HCA supports the IBA Verbs layer, while a TCA uses an implementation dependent interface to the transport layer. If the type of CA cannot be determined, the unknown(1) value is returned."
    ],
    [
      "REFERENCE",
      "InfiniBand Architecture Release 1.2.1 Vol. 1 Section 17.1"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.33049)

Sagi Rotem

Siblings (17)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.33049.2.5.1.2.1.1 mlxIBCAIndex00
1.3.6.1.4.1.33049.2.5.1.2.1.2 mlxIBCADeviceName00
1.3.6.1.4.1.33049.2.5.1.2.1.3 mlxIBCAPCIDomain00
1.3.6.1.4.1.33049.2.5.1.2.1.4 mlxIBCAPCIBus00
1.3.6.1.4.1.33049.2.5.1.2.1.5 mlxIBCAPCISlot00
1.3.6.1.4.1.33049.2.5.1.2.1.6 mlxIBCAPCIFunction00
1.3.6.1.4.1.33049.2.5.1.2.1.7 mlxIBCAPCIPhysicalSlot00
1.3.6.1.4.1.33049.2.5.1.2.1.8 mlxIBCAIrq00
1.3.6.1.4.1.33049.2.5.1.2.1.9 mlxIBCAModelString00
1.3.6.1.4.1.33049.2.5.1.2.1.10 mlxIBCASerialNumber00
1.3.6.1.4.1.33049.2.5.1.2.1.11 mlxIBCAPartNumber00
1.3.6.1.4.1.33049.2.5.1.2.1.12 mlxIBCANodeGUID00
1.3.6.1.4.1.33049.2.5.1.2.1.13 mlxIBCASystemImageGUID00
1.3.6.1.4.1.33049.2.5.1.2.1.14 mlxIBCAFirmwareVersion00
1.3.6.1.4.1.33049.2.5.1.2.1.15 mlxIBCAHardwareVersion00
1.3.6.1.4.1.33049.2.5.1.2.1.16 mlxIBCAHealthStatus00
1.3.6.1.4.1.33049.2.5.1.2.1.17 mlxIBCANumPorts00