OID reference

mgmtAddressType

1.3.6.1.4.1.43.10.14.3.2.1.3

Description

A card in the chassis can have several addresses, either because of multiple stacks and/or for each relevant level in the stack(s). Each relevant address is represented in this table as a display string and a type. Note that ieee8023Address and ieee8025Address types differ from each other in the bit ordering of the ph…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.10.14.3.2.1 (addressTableEntry)
Node code
3
Node name
mgmtAddressType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.10.14.3.2.1.3
URN notation
urn:oid:1.3.6.1.4.1.43.10.14.3.2.1.3
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 10 14 3 2 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) generic(10) chassis(14) logicalConfig(3) addressTable(2) addressTableEntry(1) mgmtAddressType(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/10/14/3/2/1/3
  • /ISO/Identified-Organization/6/1/4/1/43/10/14/3/2/1/3
  • /ISO/3/6/1/4/1/43/10/14/3/2/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/enterprise/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/enterprise/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/enterprises/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/enterprises/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/vendor-objects/a3Com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • /iso/org/dod/internet/private/vendor-objects/a3com/generic/chassis/logicalConfig/addressTable/addressTableEntry/mgmtAddressType
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1ieee8023address
2ieee8025address
3ipaddress
4slipaddress

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.

In LBMSH-MIB, the row index consists of these components in order:

  1. mgmtServiceId (INTEGER): one numeric subidentifier for the non-negative value.
  2. mgmtSubIndex (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.43.10.14.3.2.1.3.<mgmtServiceId>.<mgmtSubIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.43.10.14.3.2.1.3

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.

The displayed source records contain one distinct definition. Compare its source records.

mgmtAddressType OBJECT-TYPE
	SYNTAX	INTEGER  {
		ieee8023address (1),
		ieee8025address (2),
		ipaddress (3),
		slipaddress (4)
	}
	ACCESS	read-only
	STATUS	mandatory
	DESCRIPTION	"A card in the chassis can have several 
	addresses, either because of multiple stacks and/or for each 
	relevant level in the stack(s). Each relevant address is 
	represented in this table as a display string and a type. 
	Note that ieee8023Address and ieee8025Address types differ 
	from each other in the bit ordering of the physical address."
	::= {addressTableEntry 3}

Meaning

Descriptions

1 unique

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

A card in the chassis can have several addresses, either because of
multiple stacks and/or for each relevant level in the stack(s). Each
relevant address is represented in this table as a display string and
a type. Note that ieee8023Address and ieee8025Address types differ from
each other in the bit ordering of the physical address.
Sources for this description

MIBdepot

See 1 matching source record

Circitor

Parsed from LBHUB-MSH-MIB.mib · LBHUB-MSH-MIB

Source file: Download LBHUB-MSH-MIB.mib

Browse all files from Circitor

MIBdepot

Source file: Download lbhub-msh.mib.txt

Source data warning: Publisher uses uppercase SEQUENCE field identifiers. Their exact spelling is preserved without changing value definitions, INDEX references or numeric OID assignments

Source file: Download msh100.mib.txt

Browse all files from MIBdepot

Evidence

Source records

1 records

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

Records for description 1MIBdepot1 record · 1 source

Description 1

mgmtAddressType · mandatoryMIBdepot1 source

Status in source: mandatory.

Names: mgmtAddressType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mgmtAddressType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "ieee8023address",
    "(",
    "1",
    ")",
    ",",
    "ieee8025address",
    "(",
    "2",
    ")",
    ",",
    "ipaddress",
    "(",
    "3",
    ")",
    ",",
    "slipaddress",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"A card in the chassis can have several addresses, either because of multiple stacks and/or for each relevant level in the stack(s). Each relevant address is represented in this table as a display string and a type. Note that ieee8023Address and ieee8025Address types differ from each other in the bit ordering of the physical address.\"",
    "::=",
    "{",
    "addressTableEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "ieee8023address",
            1
          ],
          [
            "ieee8025address",
            2
          ],
          [
            "ipaddress",
            3
          ],
          [
            "slipaddress",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "A card in the chassis can have several addresses, either because of multiple stacks and/or for each relevant level in the stack(s). Each relevant address is represented in this table as a display string and a type. Note that ieee8023Address and ieee8025Address types differ from each other in the bit ordering of the physical address."
    ],
    null,
    null,
    null,
    null
  ]
}

Historical records

Additional source information

Information from OID Repository
Vendor: 3Com
Module: LBHUB-MSH-MIB (lbhub-msh.mib)
Type: TABULAR
Access: read-only
Syntax: INTEGER

Automatically extracted from www.mibdepot.com
Information from MIBdepot
mgmtAddressType OBJECT-TYPE
	SYNTAX		INTEGER {
				ieee8023address		(1),
				ieee8025address	        (2),
				ipaddress		(3),
				slipaddress		(4)
				}
	ACCESS		read-only
	STATUS		mandatory
	DESCRIPTION	"
A card in the chassis can have several addresses, either because of
multiple stacks and/or for each relevant level in the stack(s). Each
relevant address is represented in this table as a display string and
a type. Note that ieee8023Address and ieee8025Address types differ from
each other in the bit ordering of the physical address."
	::= { addressTableEntry 3 }
Information from Circitor
mgmtAddressType OBJECT-TYPE
	SYNTAX		INTEGER {
				ieee8023address		(1),
				ieee8025address	        (2),
				ipaddress		(3),
				slipaddress		(4)
				}
	ACCESS		read-only
	STATUS		mandatory
	DESCRIPTION	"
A card in the chassis can have several addresses, either because of
multiple stacks and/or for each relevant level in the stack(s). Each
relevant address is represented in this table as a display string and
a type. Note that ieee8023Address and ieee8025Address types differ from
each other in the bit ordering of the physical address."
	::= { addressTableEntry 3 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.10.14.3.2.1.1 mgmtServiceId00 Identifies the service for which this row
provides address information.
1.3.6.1.4.1.43.10.14.3.2.1.2 mgmtSubIndex00 Used to distinguish between multiple addresses for a service in the
chassis.
1.3.6.1.4.1.43.10.14.3.2.1.4 mgmtAddress00 The address as block of bytes. An IP address would occupy 4 bytes and
a MAC address 6 bytes.