OID reference

serviceId

1.3.6.1.4.1.43.10.14.3.1.1.1

Description

This is a number representing the service in the rack. This id can be used to reference the service elsewhere in the MIB. There are several conventions used to allocate a service Id. Firstly if a card forms a service by itself, for example a bridge card, which uses none of the backplane 802.3 or token ring lines, then…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.10.14.3.1.1 (serviceEntry)
Node code
1
Node name
serviceId
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.10.14.3.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.43.10.14.3.1.1.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

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 serviceId is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.43.10.14.3.1.1.1.<serviceId>. Use an index value actually 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.1.1.1

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.

serviceId OBJECT-TYPE
	SYNTAX	INTEGER 
	ACCESS	read-only
	STATUS	mandatory
	DESCRIPTION	"This is a number representing the 
	service in the rack/stack. This id can be used to reference
	the service elsewhere in the MIB.

	There are several conventions used to allocate a service Id.
	Firstly if a card (or unit) forms a service by itself, for
	example a bridge card, which uses none of the backplane 802.3
	or token ring lines, then the service id is the same as the
	slot position of that card within the rack.
	
	If a service is constructed using one of the backplane 802.3 
	facilities then the service id is 101, 102 or 103 for the 
	three backplane 802.3 paths.
	
	If a service is a token ring fragment then the service id 
	for that service is 200 plus the ring fragment id. For 
	example if Ring Builder builder builds a ring from MAU cards 
	with ring fragment id 7, the corresponding service will be 207.
	
	If a service corresponds to a workgroup, then the service id
	is the same as the workgroup id."
	::= {serviceEntry 1}

Meaning

Descriptions

2 unique

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

Description 1

This is a number representing the service in the rack. This id can be
used to reference the service elsewhere in the MIB. There are several
conventions used to allocate a service Id. Firstly if a card forms a
service by itself, for example a bridge card, which uses none of the
backplane 802.3 or token ring lines, then the service id is the same as
the slot position of that card within the rack.

If a service is constructed using one of the backplane 802.3
facilities then the service id is 101, 102 or 103 for the three
backplane 802.3 paths.

If a service is a token ring fragment then the service id for that
service is 200 plus the ring fragment id. For example if Ring Builder
builder builds a ring from MAU cards with ring fragment id 7, the
corresponding service will be 207.
Sources for this description

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

Related source files and packages:

Show more related files and packages

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

Description 2

This is a number representing the service in the rack/stack. This id can be used to reference the service elsewhere in the MIB. There are several conventions used to allocate a service Id. Firstly if a card (or unit) forms a service by itself, for example a bridge card, which uses none of the backplane 802.3 or token ring lines, then the service id is the same as the slot position of that card within the rack. If a service is constructed using one of the backplane 802.3 facilities then the service id is 101, 102 or 103 for the three backplane 802.3 paths. If a service is a token ring fragment then the service id for that service is 200 plus the ring fragment id. For example if Ring Builder builder builds a ring from MAU cards with ring fragment id 7, the corresponding service will be 207. If a service corresponds to a workgroup, then the service id is the same as the workgroup id.

Sources for this description

MIBdepot

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 2MIBdepot1 record · 1 source

Description 2

serviceId · mandatoryMIBdepot1 source

Status in source: mandatory.

Names: serviceId

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "serviceId",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This is a number representing the service in the rack/stack. This id can be used to reference the service elsewhere in the MIB. There are several conventions used to allocate a service Id. Firstly if a card (or unit) forms a service by itself, for example a bridge card, which uses none of the backplane 802.3 or token ring lines, then the service id is the same as the slot position of that card within the rack. If a service is constructed using one of the backplane 802.3 facilities then the service id is 101, 102 or 103 for the three backplane 802.3 paths. If a service is a token ring fragment then the service id for that service is 200 plus the ring fragment id. For example if Ring Builder builder builds a ring from MAU cards with ring fragment id 7, the corresponding service will be 207. If a service corresponds to a workgroup, then the service id is the same as the workgroup id.\"",
    "::=",
    "{",
    "serviceEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This is a number representing the service in the rack/stack. This id can be used to reference the service elsewhere in the MIB. There are several conventions used to allocate a service Id. Firstly if a card (or unit) forms a service by itself, for example a bridge card, which uses none of the backplane 802.3 or token ring lines, then the service id is the same as the slot position of that card within the rack. If a service is constructed using one of the backplane 802.3 facilities then the service id is 101, 102 or 103 for the three backplane 802.3 paths. If a service is a token ring fragment then the service id for that service is 200 plus the ring fragment id. For example if Ring Builder builder builds a ring from MAU cards with ring fragment id 7, the corresponding service will be 207. If a service corresponds to a workgroup, then the service id is the same as the workgroup id."
    ],
    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 
serviceId OBJECT-TYPE
	SYNTAX		INTEGER
	ACCESS		read-only
	STATUS		mandatory
	DESCRIPTION	"
This is a number representing the service in the rack. This id can be
used to reference the service elsewhere in the MIB. There are several
conventions used to allocate a service Id. Firstly if a card forms a
service by itself, for example a bridge card, which uses none of the
backplane 802.3 or token ring lines, then the service id is the same as
the slot position of that card within the rack.

If a service is constructed using one of the backplane 802.3
facilities then the service id is 101, 102 or 103 for the three
backplane 802.3 paths.

If a service is a token ring fragment then the service id for that
service is 200 plus the ring fragment id. For example if Ring Builder
builder builds a ring from MAU cards with ring fragment id 7, the
corresponding service will be 207."
	::= { serviceEntry 1 }
Information from Circitor 
serviceId OBJECT-TYPE
	SYNTAX		INTEGER
	ACCESS		read-only
	STATUS		mandatory
	DESCRIPTION	"
This is a number representing the service in the rack. This id can be
used to reference the service elsewhere in the MIB. There are several
conventions used to allocate a service Id. Firstly if a card forms a
service by itself, for example a bridge card, which uses none of the
backplane 802.3 or token ring lines, then the service id is the same as
the slot position of that card within the rack.

If a service is constructed using one of the backplane 802.3
facilities then the service id is 101, 102 or 103 for the three
backplane 802.3 paths.

If a service is a token ring fragment then the service id for that
service is 200 plus the ring fragment id. For example if Ring Builder
builder builds a ring from MAU cards with ring fragment id 7, the
corresponding service will be 207."
	::= { serviceEntry 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.10.14.3.1.1.2 serviceName00 This is a text string describing the service at a particular Service Index.
1.3.6.1.4.1.43.10.14.3.1.1.3 serviceReset00 This action will reset all the cards that belong to this service.