Reference record for OID 1.3.6.1.2.1.47.1.2.1.1.4



parent
1.3.6.1.2.1.47.1.2.1.1 (entLogicalEntry)
node code
4
node name
entLogicalCommunity
dot oid
1.3.6.1.2.1.47.1.2.1.1.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
    • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/identified-organization/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
    • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/47/1/2/1/1/4

    Description by circitor

    An SNMPv1 or SNMPv2C community-string, which can be used to
    access detailed management information for this logical
    entity. The agent should allow read access with this
    community string (to an appropriate subset of all managed
    objects) and may also return a community string based on the
    privileges of the request used to read this object. Note
    that an agent may return a community string with read-only
    privileges, even if this object is accessed with a
    read-write community string. However, the agent must take



    care not to return a community string that allows more
    privileges than the community string used to access this
    object.

    A compliant SNMP agent may wish to conserve naming scopes by
    representing multiple logical entities in a single 'default'
    naming scope. This is possible when the logical entities,
    represented by the same value of entLogicalCommunity, have
    no object instances in common. For example, 'bridge1' and
    'repeater1' may be part of the main naming scope, but at
    least one additional community string is needed to represent
    'bridge2' and 'repeater2'.

    Logical entities 'bridge1' and 'repeater1' would be
    represented by sysOREntries associated with the 'default'
    naming scope.

    For agents not accessible via SNMPv1 or SNMPv2C, the value
    of this object is the empty string. This object may also
    contain an empty string if a community string has not yet
    been assigned by the agent, or if no community string with
    suitable access rights can be returned for a particular SNMP
    request.

    Note that this object is deprecated. Agents which implement
    SNMPv3 access should use the entLogicalContextEngineID and
    entLogicalContextName objects to identify the context
    associated with each logical entity. SNMPv3 agents may
    return a zero-length string for this object, or may continue
    to return a community string (e.g., tri-lingual agent
    support).

    Parsed from file ENTITY-MIB.mib
    Module: ENTITY-MIB

    Description by cisco_v1

    An SNMPv1 or SNMPv2C community-string, which can be used to
    access detailed management information for this logical
    entity. The agent should allow read access with this
    community string (to an appropriate subset of all managed
    objects) and may also return a community string based on the
    privileges of the request used to read this object. Note
    that an agent may return a community string with read-only
    privileges, even if this object is accessed with a
    read-write community string. However, the agent must take


    care not to return a community string that allows more
    privileges than the community string used to access this
    object.

    A compliant SNMP agent may wish to conserve naming scopes by
    representing multiple logical entities in a single 'default'
    naming scope. This is possible when the logical entities,
    represented by the same value of entLogicalCommunity, have
    no object instances in common. For example, 'bridge1' and
    'repeater1' may be part of the main naming scope, but at
    least one additional community string is needed to represent
    'bridge2' and 'repeater2'.

    Logical entities 'bridge1' and 'repeater1' would be
    represented by sysOREntries associated with the 'default'
    naming scope.

    For agents not accessible via SNMPv1 or SNMPv2C, the value
    of this object is the empty string. This object may also
    contain an empty string if a community string has not yet
    been assigned by the agent, or if no community string with
    suitable access rights can be returned for a particular SNMP
    request.

    Note that this object is deprecated. Agents which implement
    SNMPv3 access should use the entLogicalContextEngineID and
    entLogicalContextName objects to identify the context
    associated with each logical entity. SNMPv3 agents may
    return a zero-length string for this object, or may continue
    to return a community string (e.g., tri-lingual agent
    support).

    Description by oid_info

    entLogicalCommunity OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE (0..255))
    MAX-ACCESS read-only
    STATUS deprecated
    DESCRIPTION
    "An SNMPv1 or SNMPv2C community-string which can be used to
    access detailed management information for this logical
    entity. The agent should allow read access with this
    community string (to an appropriate subset of all managed
    objects) and may also return a community string based on the
    privileges of the request used to read this object. Note
    that an agent may return a community string with read-only
    privileges, even if this object is accessed with a read-
    write community string. However, the agent must take care
    not to return a community string which allows more
    privileges than the community string used to access this
    object.
    A compliant SNMP agent may wish to conserve naming scopes by
    representing multiple logical entities in a single default
    naming scope. This is possible when the logical entities
    represented by the same value of entLogicalCommunity have no
    object instances in common. For example, ridge1 and

    epeater1 may be part of the main naming scope, but at
    least one additional community string is needed to represent
    ridge2 and
    epeater2.
    Logical entities ridge1 and
    epeater1 would be
    represented by sysOREntries associated with the default
    naming scope.
    For agents not accessible via SNMPv1 or SNMPv2C, the value
    of this object is the empty string. This object may also
    contain an empty string if a community string has not yet
    been assigned by the agent, or no community string with
    suitable access rights can be returned for a particular SNMP
    request.
    Note that this object is deprecated. Agents which implement
    SNMPv3 access should use the entLogicalContextEngineID and
    entLogicalContextName objects to identify the context
    associated with each logical entity. SNMPv3 agents may
    return a zero-length string for this object, or may continue
    to return a community string (e.g., tri-lingual agent
    support)."
    View at oid-info.com

    Description by mibdepot

    An SNMPv1 or SNMPv2C community-string, which can be used to
    access detailed management information for this logical
    entity. The agent should allow read access with this
    community string (to an appropriate subset of all managed
    objects) and may also return a community string based on the
    privileges of the request used to read this object. Note
    that an agent may return a community string with read-only
    privileges, even if this object is accessed with a
    read-write community string. However, the agent must take



    care not to return a community string that allows more
    privileges than the community string used to access this
    object.

    A compliant SNMP agent may wish to conserve naming scopes by
    representing multiple logical entities in a single 'default'
    naming scope. This is possible when the logical entities,
    represented by the same value of entLogicalCommunity, have
    no object instances in common. For example, 'bridge1' and
    'repeater1' may be part of the main naming scope, but at
    least one additional community string is needed to represent
    'bridge2' and 'repeater2'.

    Logical entities 'bridge1' and 'repeater1' would be
    represented by sysOREntries associated with the 'default'
    naming scope.

    For agents not accessible via SNMPv1 or SNMPv2C, the value
    of this object is the empty string. This object may also
    contain an empty string if a community string has not yet
    been assigned by the agent, or if no community string with
    suitable access rights can be returned for a particular SNMP
    request.

    Note that this object is deprecated. Agents which implement
    SNMPv3 access should use the entLogicalContextEngineID and
    entLogicalContextName objects to identify the context
    associated with each logical entity. SNMPv3 agents may
    return a zero-length string for this object, or may continue
    to return a community string (e.g., tri-lingual agent
    support).

    Parsed from file ENTITY-MIB.mib.txt
    Company: None
    Module: ENTITY-MIB

    Description by cisco

    An SNMPv1 or SNMPv2C community-string, which can be used to
    access detailed management information for this logical
    entity. The agent should allow read access with this
    community string (to an appropriate subset of all managed
    objects) and may also return a community string based on the
    privileges of the request used to read this object. Note
    that an agent may return a community string with read-only
    privileges, even if this object is accessed with a
    read-write community string. However, the agent must take


    care not to return a community string that allows more
    privileges than the community string used to access this
    object.

    A compliant SNMP agent may wish to conserve naming scopes by
    representing multiple logical entities in a single 'default'
    naming scope. This is possible when the logical entities,
    represented by the same value of entLogicalCommunity, have
    no object instances in common. For example, 'bridge1' and
    'repeater1' may be part of the main naming scope, but at
    least one additional community string is needed to represent
    'bridge2' and 'repeater2'.

    Logical entities 'bridge1' and 'repeater1' would be
    represented by sysOREntries associated with the 'default'
    naming scope.

    For agents not accessible via SNMPv1 or SNMPv2C, the value
    of this object is the empty string. This object may also
    contain an empty string if a community string has not yet
    been assigned by the agent, or if no community string with
    suitable access rights can be returned for a particular SNMP
    request.

    Note that this object is deprecated. Agents which implement
    SNMPv3 access should use the entLogicalContextEngineID and
    entLogicalContextName objects to identify the context
    associated with each logical entity. SNMPv3 agents may
    return a zero-length string for this object, or may continue
    to return a community string (e.g., tri-lingual agent
    support).

    Information by circitor

    entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take



            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

    Information by cisco_v1

    entLogicalCommunity OBJECT-TYPE
    SYNTAX OCTET STRING(SIZE(0..255))
    ACCESS read-only
    STATUS deprecated
    DESCRIPTION
        "An SNMPv1 or SNMPv2C community-string, which can be used to
        access detailed management information for this logical
        entity.  The agent should allow read access with this
        community string (to an appropriate subset of all managed
        objects) and may also return a community string based on the
        privileges of the request used to read this object.  Note
        that an agent may return a community string with read-only
        privileges, even if this object is accessed with a
        read-write community string.  However, the agent must take
        
        
        care not to return a community string that allows more
        privileges than the community string used to access this
        object.
        
        A compliant SNMP agent may wish to conserve naming scopes by
        representing multiple logical entities in a single 'default'
        naming scope.  This is possible when the logical entities,
        represented by the same value of entLogicalCommunity, have
        no object instances in common.  For example, 'bridge1' and
        'repeater1' may be part of the main naming scope, but at
        least one additional community string is needed to represent
        'bridge2' and 'repeater2'.
        
        Logical entities 'bridge1' and 'repeater1' would be
        represented by sysOREntries associated with the 'default'
        naming scope.
        
        For agents not accessible via SNMPv1 or SNMPv2C, the value
        of this object is the empty string.  This object may also
        contain an empty string if a community string has not yet
        been assigned by the agent, or if no community string with
        suitable access rights can be returned for a particular SNMP
        request.
        
        Note that this object is deprecated.  Agents which implement
        SNMPv3 access should use the entLogicalContextEngineID and
        entLogicalContextName objects to identify the context
        associated with each logical entity.  SNMPv3 agents may
        return a zero-length string for this object, or may continue
        to return a community string (e.g., tri-lingual agent
        support)."
    ::= { entLogicalEntry 4 }

    Information by oid_info

    Automatically extracted from RFC2737

    Information by mibdepot

    entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take



            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

    Information by cisco

    entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take


            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (7)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.47.1.2.1.1.1 entLogicalIndex 0 0 The value of this object uniquely identifies the logical
    entity. The value should be a small positive integer; index
    values for …
    1.3.6.1.2.1.47.1.2.1.1.2 entLogicalDescr 0 0 A textual description of the logical entity. This object
    should contain a string that identifies the manufacturer's
    name for the…
    1.3.6.1.2.1.47.1.2.1.1.3 entLogicalType 0 0 An indication of the type of logical entity. This will
    typically be the OBJECT IDENTIFIER name of the node in the
    SMI's naming h…
    1.3.6.1.2.1.47.1.2.1.1.5 entLogicalTAddress 0 0 The transport service address by which the logical entity
    receives network management traffic, formatted according to
    the corresp…
    1.3.6.1.2.1.47.1.2.1.1.6 entLogicalTDomain 0 0 Indicates the kind of transport service by which the
    logical entity receives network management traffic.
    Possible values for this…
    1.3.6.1.2.1.47.1.2.1.1.7 entLogicalContextEngineID 0 0 The authoritative contextEngineID that can be used to send
    an SNMP message concerning information held by this logical
    entity, to…
    1.3.6.1.2.1.47.1.2.1.1.8 entLogicalContextName 0 0 The contextName that can be used to send an SNMP message
    concerning information held by this logical entity, to the
    address speci…