OID reference

oslam8gPortDoubleTag

1.3.6.1.4.1.11606.4.2.2.10

Description

OSLAM-8G Port Double Tag ======================== Ingress Double Tag 2 - The ingressing frames are examined to see if they contain 802.3ac tag with the IEEE standard EtherType of 0x8100 or if they contain a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag will be used if this port's oslam8gPortUseCo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.11606.4.2.2 (oslam8g-portCtrl)
Node code
10
Node name
oslam8gPortDoubleTag
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.11606.4.2.2.10
URN notation
urn:oid:1.3.6.1.4.1.11606.4.2.2.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 11606 4 2 2 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) pbn(11606) oslam8g(4) oslam8g-Port(2) oslam8g-portCtrl(2) oslam8gPortDoubleTag(10)}
OID-IRI notation
  • /1/3/6/1/4/1/11606/4/2/2/10
  • /ISO/Identified-Organization/6/1/4/1/11606/4/2/2/10
  • /ISO/3/6/1/4/1/11606/4/2/2/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/enterprise/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/enterprises/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/enterprises/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/vendor-objects/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/identified-organization/dod/internet/private/vendor-objects/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/enterprise/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/enterprise/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/enterprises/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/enterprises/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/ldap-enterprise/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/ldap-enterprise/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/vendor-objects/11606/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • /iso/org/dod/internet/private/vendor-objects/pbn/oslam8g/oslam8g-Port/oslam8g-portCtrl/oslam8gPortDoubleTag
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
1normal
2useDoubleCoreTag

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.11606.4.2.2.10.0

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

oslam8gPortDoubleTag · mandatory

oslam8gPortDoubleTag OBJECT-TYPE
			SYNTAX INTEGER
				{
				normal(1),
				useDoubleCoreTag(2)
				}
			ACCESS read-write
			STATUS mandatory
			DESCRIPTION
				"OSLAM-8G Port Double Tag
				========================
				Ingress Double Tag
				
				2 - The ingressing frames are examined to see if they contain 802.3ac 
				    tag with the IEEE standard EtherType of 0x8100 or if they contain
				    a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag
				    will be used if this port's oslam8gPortUseCoreTag is used. If the 
				    frames do contain the expected tag, the tag is removed (and the 
				    CRC is recomputed).
				
				    Essentially, untagged frames remain untagged, single tagged frames
				    become untagged and double tagged frames become single tagged. 
				    These now single tagged frames will be considered tagged only if 
				    its EtherType value is 0x8100 no matter what the EtherType value 
				    was found on the removed tag. No padding is performed so a tagged
				    frame must be at least 68bytes in size or it will be discarded.
				
				1 - Tagged frames are not modified when received.
				
				    The Tag data that is removed from the frame can be ignored 
				    (i.e., the frame is treated as if the removed tag never existed)
				    or the removed Tag data can be used for switching and priority
				    decisions (i.e., the removed Tag's VID and PRI bits are internally 
				    assigned to the frame). The action that is taken is controlled by
				    the oslam8gUseDoubleTagData"
			::= { oslam8g-portCtrl 10 }

oslam8gPortDoubleTag · mandatory

oslam8gPortDoubleTag OBJECT-TYPE
			SYNTAX INTEGER
				{
				normal(1),
				useDoubleCoreTag(2)
				}
			ACCESS read-write
			STATUS mandatory
			DESCRIPTION
				"OSLAM-8G Port Double Tag
				========================
				Ingress Double Tag
				
				2 - The ingressing frames are examined to see if they contain 802.3ac 
				    tag with the IEEE standard EtherType of 0x8100 or if they contain
				    a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag
				    will be used if this port's oslam8gPortUseCoreTag is used. If the 
				    frames do contain the expected tag, the tag is removed (and the 
				    CRC is recomputed).
				
				    Essentially, untagged frames remain untagged, single tagged frames
				    become untagged and double tagged frames become single tagged. 
				    These now single tagged frames will be considered tagged only if 
				    its EtherType value is 0x8100 no matter what the EtherType value 
				    was found on the removed tag. No padding is performed so a tagged
				    frame must be at least 68bytes in size or it will be discarded.
				
				1 - Tagged frames are not modified when received.
				
				    The Tag data that is removed from the frame can be ignored 
				    (i.e., the frame is treated as if the removed tag never existed)
				    or the removed Tag data can be used for switching and priority
				    decisions (i.e., the removed Tag's VID and PRI bits are internally 
				    assigned to the frame). The action that is taken is controlled by
				    the oslam8gUseDoubleTagData"
			::= { oslam8g-portCtrl 10 }

Meaning

Descriptions

1 unique

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

OSLAM-8G Port Double Tag ======================== Ingress Double Tag 2 - The ingressing frames are examined to see if they contain 802.3ac tag with the IEEE standard EtherType of 0x8100 or if they contain a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag will be used if this port's oslam8gPortUseCoreTag is used. If the frames do contain the expected tag, the tag is removed (and the CRC is recomputed). Essentially, untagged frames remain untagged, single tagged frames become untagged and double tagged frames become single tagged. These now single tagged frames will be considered tagged only if its EtherType value is 0x8100 no matter what the EtherType value was found on the removed tag. No padding is performed so a tagged frame must be at least 68bytes in size or it will be discarded. 1 - Tagged frames are not modified when received. The Tag data that is removed from the frame can be ignored (i.e., the frame is treated as if the removed tag never existed) or the removed Tag data can be used for switching and priority decisions (i.e., the removed Tag's VID and PRI bits are internally assigned to the frame). The action that is taken is controlled by the oslam8gUseDoubleTagData

Sources for this description

Multiple manufacturers; see the original MIB 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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

oslam8gPortDoubleTag · mandatoryMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)2 sources

Status in source: mandatory.

Names: oslam8gPortDoubleTag

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "oslam8gPortDoubleTag",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "normal",
    "(",
    "1",
    ")",
    ",",
    "useDoubleCoreTag",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"OSLAM-8G Port Double Tag ======================== Ingress Double Tag 2 - The ingressing frames are examined to see if they contain 802.3ac tag with the IEEE standard EtherType of 0x8100 or if they contain a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag will be used if this port's oslam8gPortUseCoreTag is used. If the frames do contain the expected tag, the tag is removed (and the CRC is recomputed). Essentially, untagged frames remain untagged, single tagged frames become untagged and double tagged frames become single tagged. These now single tagged frames will be considered tagged only if its EtherType value is 0x8100 no matter what the EtherType value was found on the removed tag. No padding is performed so a tagged frame must be at least 68bytes in size or it will be discarded. 1 - Tagged frames are not modified when received. The Tag data that is removed from the frame can be ignored (i.e., the frame is treated as if the removed tag never existed) or the removed Tag data can be used for switching and priority decisions (i.e., the removed Tag's VID and PRI bits are internally assigned to the frame). The action that is taken is controlled by the oslam8gUseDoubleTagData\"",
    "::=",
    "{",
    "oslam8g-portCtrl",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "normal",
            1
          ],
          [
            "useDoubleCoreTag",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "OSLAM-8G Port Double Tag ======================== Ingress Double Tag 2 - The ingressing frames are examined to see if they contain 802.3ac tag with the IEEE standard EtherType of 0x8100 or if they contain a tag with an EtherType defined in oslam8gCoreTag. The oslam8gCoreTag will be used if this port's oslam8gPortUseCoreTag is used. If the frames do contain the expected tag, the tag is removed (and the CRC is recomputed). Essentially, untagged frames remain untagged, single tagged frames become untagged and double tagged frames become single tagged. These now single tagged frames will be considered tagged only if its EtherType value is 0x8100 no matter what the EtherType value was found on the removed tag. No padding is performed so a tagged frame must be at least 68bytes in size or it will be discarded. 1 - Tagged frames are not modified when received. The Tag data that is removed from the frame can be ignored (i.e., the frame is treated as if the removed tag never existed) or the removed Tag data can be used for switching and priority decisions (i.e., the removed Tag's VID and PRI bits are internally assigned to the frame). The action that is taken is controlled by the oslam8gUseDoubleTagData"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.11606)

Vloothuis Ger

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.11606.4.2.2.1 oslam8gPortForceFlowCtrl00
1.3.6.1.4.1.11606.4.2.2.2 oslam8gPortForceLink00
1.3.6.1.4.1.11606.4.2.2.3 oslam8gPortForceDuplex00
1.3.6.1.4.1.11606.4.2.2.4 oslam8gPortForceSpeed00
1.3.6.1.4.1.11606.4.2.2.5 oslam8gPortPortState00
1.3.6.1.4.1.11606.4.2.2.6 oslam8gPortFwdUnknown00
1.3.6.1.4.1.11606.4.2.2.7 oslam8gPortDefFwd00
1.3.6.1.4.1.11606.4.2.2.8 oslam8gPortUseIPForPriority00
1.3.6.1.4.1.11606.4.2.2.9 oslam8gPortUseCoreTag00