OID reference

lcsVLANPortStatusConflicts

1.3.6.1.4.1.2356.14.1.10.2.6.2.1.8

Description

Two users may have conflicting requirements to a port's configuration. For instance, one user may require all frames to be tagged on egress while another requires all frames to be untagged on egress.Since both users cannot win, this gives rise to a conflict, which is solved in a prioritized way. The Administrator has …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2356.14.1.10.2.6.2.1 (lcsVLANPortStatusEntry)
Node code
8
Node name
lcsVLANPortStatusConflicts
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.8
URN notation
urn:oid:1.3.6.1.4.1.2356.14.1.10.2.6.2.1.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2356 14 1 10 2 6 2 1 8}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsVLANConf(10) lcsVLAN(2) lcsVlanStatus(6) lcsVLANPortStatusTable(2) lcsVLANPortStatusEntry(1) lcsVLANPortStatusConflicts(8)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2356/14/1/10/2/6/2/1/8
  • /ISO/Identified-Organization/6/1/4/1/2356/14/1/10/2/6/2/1/8
  • /ISO/3/6/1/4/1/2356/14/1/10/2/6/2/1/8
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ELSA/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprise/lancom-systems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprise/elsa/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprise/lancomSystems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprises/ELSA/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprises/lancom-systems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprises/elsa/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/enterprises/lancomSystems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ELSA/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancom-systems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/elsa/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancomSystems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/vendor-objects/ELSA/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancom-systems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/vendor-objects/elsa/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancomSystems/lcosSX/lcsSystem/lcsVLANConf/lcsVLAN/lcsVlanStatus/lcsVLANPortStatusTable/lcsVLANPortStatusEntry/lcsVLANPortStatusConflicts
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-only
Status in MIB
current

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.

lcsVLANPortStatusConflicts OBJECT-TYPE
               SYNTAX      DisplayString
               MAX-ACCESS  read-only
               STATUS      current
               DESCRIPTION
                   "Two users may have conflicting requirements to a port's
                    configuration. For instance, one user may require
                    all frames to be tagged on egress while another requires
                    all frames to be untagged on egress.Since both
                    users cannot win, this gives rise to a conflict,
                    which is solved in a prioritized way. The Administrator
                    has the least priority. Other software modules are
                    prioritized according to their position in the drop-down
                    list: The higher in the list, the higher priority.
                    If conflicts exist, it will be displayed as 'Yes'."
               ::= {     lcsVLANPortStatusEntry 8 }

Meaning

Descriptions

1 unique

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

Two users may have conflicting requirements to a port's configuration. For instance, one user may require all frames to be tagged on egress while another requires all frames to be untagged on egress.Since both users cannot win, this gives rise to a conflict, which is solved in a prioritized way. The Administrator has the least priority. Other software modules are prioritized according to their position in the drop-down list: The higher in the list, the higher priority. If conflicts exist, it will be displayed as 'Yes'.

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

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

Status in source: current.

Names: lcsVLANPortStatusConflicts

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lcsVLANPortStatusConflicts",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Two users may have conflicting requirements to a port's configuration. For instance, one user may require all frames to be tagged on egress while another requires all frames to be untagged on egress.Since both users cannot win, this gives rise to a conflict, which is solved in a prioritized way. The Administrator has the least priority. Other software modules are prioritized according to their position in the drop-down list: The higher in the list, the higher priority. If conflicts exist, it will be displayed as 'Yes'.\"",
    "::=",
    "{",
    "lcsVLANPortStatusEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Two users may have conflicting requirements to a port's configuration. For instance, one user may require all frames to be tagged on egress while another requires all frames to be untagged on egress.Since both users cannot win, this gives rise to a conflict, which is solved in a prioritized way. The Administrator has the least priority. Other software modules are prioritized according to their position in the drop-down list: The higher in the list, the higher priority. If conflicts exist, it will be displayed as 'Yes'."
    ],
    null,
    null,
    null,
    null
  ]
}

Browse all 23 supporting sources

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2356)

Udo Brocker

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.2 lcsVLANPortStatusPortType00
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.3 lcsVLANPortStatusIngressFiltering00
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.4 lcsVLANPortStatusFrameType00
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.5 lcsVLANPortStatusPortVLANID00
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.6 lcsVLANPortStatusTxTag00
1.3.6.1.4.1.2356.14.1.10.2.6.2.1.7 lcsVLANPortStatusUntaggedVLANID00