Reference record for OID 1.3.6.1.4.1.36.2.18.11.1.1.1.13.6.1.2

parent

1.3.6.1.4.1.36.2.18.11.1.1.1.13.6.1 (chasLigoLabelEntry)

node code

2

node name

chasLigoLabelString

dot oid

1.3.6.1.4.1.36.2.18.11.1.1.1.13.6.1.2

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) mib-extensions-1(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) decMIBextension(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

...skipped...

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) mib-extensions-1(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) decMIBextension(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) mib-extensions-1(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) decMIBextension(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

...skipped...

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) mib-extensions-1(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) decMIBextension(18) decHub900(11) mgmtAgent(1) mgmtAgentVersion1(1) chassis(1) chasLigo(13) chasLigoLabelTable(6) chasLigoLabelEntry(1) chasLigoLabelString(2)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/dec/ema/mib-extensions-1/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

/iso/identified-organization/dod/internet/private/enterprise/dec/ema/decMIBextension/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

...skipped...

/iso/org/dod/internet/private/enterprise/dec/ema/mib-extensions-1/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

/iso/org/dod/internet/private/enterprise/dec/ema/decMIBextension/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

/iso/org/dod/internet/private/enterprises/dec/ema/mib-extensions-1/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

/iso/org/dod/internet/private/enterprises/dec/ema/decMIBextension/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

...skipped...

/iso/iso-identified-organization/dod/internet/private/enterprises/dec/ema/mib-extensions-1/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

/iso/iso-identified-organization/dod/internet/private/enterprises/dec/ema/decMIBextension/decHub900/mgmtAgent/mgmtAgentVersion1/chassis/chasLigo/chasLigoLabelTable/chasLigoLabelEntry/chasLigoLabelString

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/36/2/18/11/1/1/1/13/6/1/2

Description by mibdepot

A textual description of the port number associated
with a LIGO. If the device is bridge then bridge port number
should be used for the ethernet and fddi. If the device is a
wire concentrator then concentrator port numbers should be used.

Parsed from file DEChub900-Chassis.mib.txt
Company: None
Module: DECHUB900-CHASSIS-MIB-V3-0

Description by circitor

A textual description of the port number associated
with a LIGO. If the device is bridge then bridge port number
should be used for the ethernet and fddi. If the device is a
wire concentrator then concentrator port numbers should be used.

Parsed from file DECHUB900-CHASSIS-MIB-V3-0.mib
Module: DECHUB900-CHASSIS-MIB-V3-0

Information by oid_info

Vendor: DEC
Module: DECHUB900-CHASSIS-MIB-V3-0

[Automatically extracted from oidview.com]

Information by mibdepot

chasLigoLabelString OBJECT-TYPE
    SYNTAX  DisplayString (SIZE (0..32))
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
        "A textual description of the port number associated
         with a LIGO.  If the device is bridge then bridge port number
         should be used for the ethernet and fddi. If the device is a
         wire concentrator then concentrator port numbers should be used."
    ::= { chasLigoLabelEntry 2 }

Information by circitor

chasLigoLabelString OBJECT-TYPE
    SYNTAX  DisplayString (SIZE (0..32))
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
        "A textual description of the port number associated
         with a LIGO.  If the device is bridge then bridge port number
         should be used for the ethernet and fddi. If the device is a
         wire concentrator then concentrator port numbers should be used."
    ::= { chasLigoLabelEntry 2 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.36)

Ron Bhanukitsiri

Brothers (1)