OID reference

lcssFlowVersion

1.3.6.1.4.1.2356.14.2.20.1

Description

Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version> must be '1.3', the version of this MIB. <Organization> the name of the organization responsible for the agent implementation. <Revi…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2356.14.2.20 (lcssFlow)
Node code
1
Node name
lcssFlowVersion
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2356.14.2.20.1
URN notation
urn:oid:1.3.6.1.4.1.2356.14.2.20.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2356 14 2 20 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcssFlow(20) lcssFlowVersion(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2356/14/2/20/1
  • /ISO/Identified-Organization/6/1/4/1/2356/14/2/20/1
  • /ISO/3/6/1/4/1/2356/14/2/20/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ELSA/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprise/lancom-systems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprise/elsa/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprise/lancomSystems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprises/ELSA/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprises/lancom-systems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprises/elsa/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/enterprises/lancomSystems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ELSA/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancom-systems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/elsa/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancomSystems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/vendor-objects/ELSA/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancom-systems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/vendor-objects/elsa/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancomSystems/lcosSX/lcsConfiguration/lcssFlow/lcssFlowVersion
  • Additional combinations skipped.

SNMP properties

Value type
SnmpAdminString
Maximum access defined by MIB
read-only
Status in MIB
current
Default value
"1.3;;"

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.

lcssFlowVersion OBJECT-TYPE
              SYNTAX      SnmpAdminString
              MAX-ACCESS  read-only
              STATUS      current
              DESCRIPTION "Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version>  must be '1.3', the version of this MIB.
                    <Organization> the name of the organization responsible for the agent implementation. <Revision>     the specific software build of this agent.
                 As an example, the string '1.3;InMon Corp.;2.1.1' indicates that this agent implements version '1.2' of the SFLOW MIB, that
                 it was developed by 'InMon Corp.' and that the software build is '2.1.1'.
                 The MIB Version will change with each revision of the SFLOW MIB.
                 Management entities must check the MIB Version and not attempt to manage agents with MIB Versions greater than that for which
                 they were designed.
                 Note: The sFlow Datagram Format has an independent version number which may change independently from <MIB Version>.
                       <MIB Version> applies to the structure and semantics of the SFLOW MIB only." DEFVAL { "1.3;;" }
              ::= { lcssFlow 1 }

Meaning

Descriptions

1 unique

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

Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version> must be '1.3', the version of this MIB. <Organization> the name of the organization responsible for the agent implementation. <Revision> the specific software build of this agent. As an example, the string '1.3;InMon Corp.;2.1.1' indicates that this agent implements version '1.2' of the SFLOW MIB, that it was developed by 'InMon Corp.' and that the software build is '2.1.1'. The MIB Version will change with each revision of the SFLOW MIB. Management entities must check the MIB Version and not attempt to manage agents with MIB Versions greater than that for which they were designed. Note: The sFlow Datagram Format has an independent version number which may change independently from <MIB Version>. <MIB Version> applies to the structure and semantics of the SFLOW MIB only.

Sources for this description

LANCOM official release MIBsLANCOM 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 1LANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)1 record · 23 sources

Description 1

lcssFlowVersion · currentLANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)23 sources

Status in source: current.

Names: lcssFlowVersion

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lcssFlowVersion",
    "OBJECT-TYPE",
    "SYNTAX",
    "SnmpAdminString",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version> must be '1.3', the version of this MIB. <Organization> the name of the organization responsible for the agent implementation. <Revision> the specific software build of this agent. As an example, the string '1.3;InMon Corp.;2.1.1' indicates that this agent implements version '1.2' of the SFLOW MIB, that it was developed by 'InMon Corp.' and that the software build is '2.1.1'. The MIB Version will change with each revision of the SFLOW MIB. Management entities must check the MIB Version and not attempt to manage agents with MIB Versions greater than that for which they were designed. Note: The sFlow Datagram Format has an independent version number which may change independently from <MIB Version>. <MIB Version> applies to the structure and semantics of the SFLOW MIB only.\"",
    "DEFVAL",
    "{",
    [
      "literal",
      "22312e333b3b22"
    ],
    "}",
    "::=",
    "{",
    "lcssFlow",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "SnmpAdminString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version> must be '1.3', the version of this MIB. <Organization> the name of the organization responsible for the agent implementation. <Revision> the specific software build of this agent. As an example, the string '1.3;InMon Corp.;2.1.1' indicates that this agent implements version '1.2' of the SFLOW MIB, that it was developed by 'InMon Corp.' and that the software build is '2.1.1'. The MIB Version will change with each revision of the SFLOW MIB. Management entities must check the MIB Version and not attempt to manage agents with MIB Versions greater than that for which they were designed. Note: The sFlow Datagram Format has an independent version number which may change independently from <MIB Version>. <MIB Version> applies to the structure and semantics of the SFLOW MIB only."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "\"1.3;;\""
    ]
  ]
}

Browse all 23 supporting sources

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2356)

Udo Brocker

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2356.14.2.20.2 lcssFlowAgentAddressType00
1.3.6.1.4.1.2356.14.2.20.3 lcssFlowAgentAddress00
1.3.6.1.4.1.2356.14.2.20.4 lcssFlowRcvrTable110
1.3.6.1.4.1.2356.14.2.20.5 lcssFlowFsTable17
1.3.6.1.4.1.2356.14.2.20.6 lcssFlowCpTable15