OID reference

softwareElement-SoftwareElementID

1.3.6.1.4.1.14851.3.1.9.2.1.4

Description

SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.14851.3.1.9.2.1 (softwareElementEntry)
Node code
4
Node name
softwareElement-SoftwareElementID
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.14851.3.1.9.2.1.4
URN notation
urn:oid:1.3.6.1.4.1.14851.3.1.9.2.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 14851 3 1 9 2 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) snia(14851) libraries(3) smlRoot(1) softwareElementGroup(9) softwareElementTable(2) softwareElementEntry(1) softwareElement-SoftwareElementID(4)}
OID-IRI notation
  • /1/3/6/1/4/1/14851/3/1/9/2/1/4
  • /ISO/Identified-Organization/6/1/4/1/14851/3/1/9/2/1/4
  • /ISO/3/6/1/4/1/14851/3/1/9/2/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/enterprise/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/enterprises/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/enterprises/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/vendor-objects/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/identified-organization/dod/internet/private/vendor-objects/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/enterprise/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/enterprise/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/enterprises/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/enterprises/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/ldap-enterprise/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/ldap-enterprise/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/vendor-objects/14851/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • /iso/org/dod/internet/private/vendor-objects/snia/libraries/smlRoot/softwareElementGroup/softwareElementTable/softwareElementEntry/softwareElement-SoftwareElementID
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-only
Status in MIB
mandatory
Allowed size (octets)
0–255

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: softwareElementIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.14851.3.1.9.2.1.4

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.

softwareElement-SoftwareElementID   OBJECT-TYPE 
    SYNTAX          DisplayString  ( SIZE ( 0 .. 255  ) ) 
    MAX-ACCESS      read-only
    STATUS          mandatory
    DESCRIPTION     
        "SoftwareIdentity represents software, viewed as an
        asset and/or individually identifiable entity (similar to 
        Physical Element). It does NOT indicate whether the software
        is installed, executing, etc. (The latter is the role of the
        SoftwareFeature/ SoftwareElement classes and the Application
        Model.) Since software may be acquired, SoftwareIdentity can
        be associated with a Product using the
        ProductSoftwareComponent relationship.
        Note that the Application Model manages the deployment and
        installation of software via the classes, SoftwareFeatures and
        SoftwareElements. The deployment/installation concepts are
        related to the asset/identity one. In fact, a SoftwareIdentity
        may correspond to a Product, or to one or more
        SoftwareFeatures or SoftwareElements - depending on the
        granularity of these classes and the deployment model. The
        correspondence of Software Identity to Product,
        SoftwareFeature or SoftwareElement is indicated using the
        ConcreteIdentity association. Note that there may not be
        sufficient detail or instrumentation to instantiate
        ConcreteIdentity. And, if the association is instantiated,
        some duplication of information may result. For example, the
        Vendor described in the instances of Product and
        SoftwareIdentity MAY be the same. However, this is not
        necessarily true, and it is why vendor and similar information
        are duplicated in this class.
        Note that ConcreteIdentity can also be used to describe the
        relationship of the software to any LogicalFiles that result
        from installing it. As above, there may not be sufficient
        detail or instrumentation to instantiate this association."
    ::=  {  softwareElementEntry  4  }

Meaning

Descriptions

1 unique

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

SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may be acquired, SoftwareIdentity can be associated with a Product using the ProductSoftwareComponent relationship. Note that the Application Model manages the deployment and installation of software via the classes, SoftwareFeatures and SoftwareElements. The deployment/installation concepts are related to the asset/identity one. In fact, a SoftwareIdentity may correspond to a Product, or to one or more SoftwareFeatures or SoftwareElements - depending on the granularity of these classes and the deployment model. The correspondence of Software Identity to Product, SoftwareFeature or SoftwareElement is indicated using the ConcreteIdentity association. Note that there may not be sufficient detail or instrumentation to instantiate ConcreteIdentity. And, if the association is instantiated, some duplication of information may result. For example, the Vendor described in the instances of Product and SoftwareIdentity MAY be the same. However, this is not necessarily true, and it is why vendor and similar information are duplicated in this class. Note that ConcreteIdentity can also be used to describe the relationship of the software to any LogicalFiles that result from installing it. As above, there may not be sufficient detail or instrumentation to instantiate this association.

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)

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 1IBM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

softwareElement-SoftwareElementID · mandatoryIBM MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: softwareElement-SoftwareElementID

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "softwareElement-SoftwareElementID",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may be acquired, SoftwareIdentity can be associated with a Product using the ProductSoftwareComponent relationship. Note that the Application Model manages the deployment and installation of software via the classes, SoftwareFeatures and SoftwareElements. The deployment/installation concepts are related to the asset/identity one. In fact, a SoftwareIdentity may correspond to a Product, or to one or more SoftwareFeatures or SoftwareElements - depending on the granularity of these classes and the deployment model. The correspondence of Software Identity to Product, SoftwareFeature or SoftwareElement is indicated using the ConcreteIdentity association. Note that there may not be sufficient detail or instrumentation to instantiate ConcreteIdentity. And, if the association is instantiated, some duplication of information may result. For example, the Vendor described in the instances of Product and SoftwareIdentity MAY be the same. However, this is not necessarily true, and it is why vendor and similar information are duplicated in this class. Note that ConcreteIdentity can also be used to describe the relationship of the software to any LogicalFiles that result from installing it. As above, there may not be sufficient detail or instrumentation to instantiate this association.\"",
    "::=",
    "{",
    "softwareElementEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "DisplayString",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may be acquired, SoftwareIdentity can be associated with a Product using the ProductSoftwareComponent relationship. Note that the Application Model manages the deployment and installation of software via the classes, SoftwareFeatures and SoftwareElements. The deployment/installation concepts are related to the asset/identity one. In fact, a SoftwareIdentity may correspond to a Product, or to one or more SoftwareFeatures or SoftwareElements - depending on the granularity of these classes and the deployment model. The correspondence of Software Identity to Product, SoftwareFeature or SoftwareElement is indicated using the ConcreteIdentity association. Note that there may not be sufficient detail or instrumentation to instantiate ConcreteIdentity. And, if the association is instantiated, some duplication of information may result. For example, the Vendor described in the instances of Product and SoftwareIdentity MAY be the same. However, this is not necessarily true, and it is why vendor and similar information are duplicated in this class. Note that ConcreteIdentity can also be used to describe the relationship of the software to any LogicalFiles that result from installing it. As above, there may not be sufficient detail or instrumentation to instantiate this association."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.14851)

Jones Arnold

Siblings (10)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.14851.3.1.9.2.1.1 softwareElementIndex00
1.3.6.1.4.1.14851.3.1.9.2.1.2 softwareElement-Name00
1.3.6.1.4.1.14851.3.1.9.2.1.3 softwareElement-Version00
1.3.6.1.4.1.14851.3.1.9.2.1.5 softwareElement-Manufacturer00
1.3.6.1.4.1.14851.3.1.9.2.1.6 softwareElement-BuildNumber00
1.3.6.1.4.1.14851.3.1.9.2.1.7 softwareElement-SerialNumber00
1.3.6.1.4.1.14851.3.1.9.2.1.8 softwareElement-CodeSet00
1.3.6.1.4.1.14851.3.1.9.2.1.9 softwareElement-IdentificationCode00
1.3.6.1.4.1.14851.3.1.9.2.1.10 softwareElement-LanguageEdition00
1.3.6.1.4.1.14851.3.1.9.2.1.11 softwareElement-InstanceID00