OID reference

fsVlanTunnelStpAddress

1.3.6.1.4.1.2076.137.2.2

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.2076.137.2 (fsVlanTunnelObjects)
Node code: 2
Node name: fsVlanTunnelStpAddress
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.2076.137.2.2
URN notation: urn:oid:1.3.6.1.4.1.2076.137.2.2

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 2076 137 2 2}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanExtMIB(137) fsVlanTunnelObjects(2) fsVlanTunnelStpAddress(2)}

OID-IRI notation

/1/3/6/1/4/1/2076/137/2/2
/ISO/Identified-Organization/6/1/4/1/2076/137/2/2
/ISO/3/6/1/4/1/2076/137/2/2

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/identified-organization/dod/internet/private/enterprises/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/identified-organization/dod/internet/private/ldap-enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/identified-organization/dod/internet/private/vendor-objects/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/org/dod/internet/private/enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/org/dod/internet/private/enterprises/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/org/dod/internet/private/ldap-enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/org/dod/internet/private/vendor-objects/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-identified-organization/dod/internet/private/enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-identified-organization/dod/internet/private/enterprises/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-organization/dod/internet/private/enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-organization/dod/internet/private/enterprises/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-organization/dod/internet/private/ldap-enterprise/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress
/iso/iso-organization/dod/internet/private/vendor-objects/2076/futureVlanExtMIB/fsVlanTunnelObjects/fsVlanTunnelStpAddress

SNMP properties

Value type: MacAddress
Maximum access defined by MIB: read-write
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.

Published definitions

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

Show 2 published definitions

fsVlanTunnelStpAddress · current

fsVlanTunnelStpAddress OBJECT-TYPE
    SYNTAX      MacAddress
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        " The MAC address to be used for Customer STP BPDUs tunneling.

        When STP tunneling is enabled on a port, this MAC address will be
        used as the the destination MAC address of the customer BPDUs received.
        This is the default behaviour in Provider (Q-in-Q) Bridges and customer
        bridges. In case of 802.1ad bridges, this will be done only when the
        outgoing port type is proprietary PNP.
        
        Inside a given Network, BPDUs received with this MAC address will be 
        treated as data packets and not processed. This is the default
        behavior in case of Provider (Q-in-Q) Bridges and customer bridges. 
        In case of 802.1ad Bridges, when the outgoing port type is not 
        proprietary PNP, the destination address will be replaced with the 
        reserved address defined for customer STP BPDU.Otherwise, they will
        be treated as data packets.
        
        When the BPDU is sent out of the given Network, this MAC address
        will be replaced with the reserved address defined for Customer STP
        BPDU. This is done only when STP protocol tunnel status is set to 
        Tunnel on the outgoing port, dropped otherwise."
        
    ::= { fsVlanTunnelObjects 2 }

fsVlanTunnelStpAddress · current

fsVlanTunnelStpAddress OBJECT-TYPE
    SYNTAX      MacAddress
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        " The MAC address to be used for Customer STP BPDUs tunneling.

        When STP tunneling is enabled on a port, this MAC address will be
        used as the the destination MAC address of the customer BPDUs received.
        This is the default behaviour in Provider (Q-in-Q) Bridges and customer
        bridges. In case of 802.1ad bridges, this will be done only when the
        outgoing port type is proprietary PNP.
        
        Inside a given Network,BPDUs received with this MAC address will be 
        treated as data packets and not processed. This is the default
        behaviour in case of Provider (Q-in-Q) Bridges and customer bridges. 
        In case of 802.1ad Bridges, when the outgoing port type is not 
        proprietary PNP, the destination address will be replaced with the 
        reserved address defined for customer STP BPDU.Otherwise, they will
        be treated as data packets.
        
        When the BPDU is sent out of the given Network, this MAC address
        will be replaced with the reserved address defined for Customer STP
        BPDU. This is done only when when STP protocol tunnel status is set to 
        Tunnel on the outgoing port.Dropped otherwise."
        
    ::= { fsVlanTunnelObjects 2 }

Meaning

Descriptions

2 unique

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

Description 1

The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network, BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behavior in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when STP protocol tunnel status is set to Tunnel on the outgoing port, dropped otherwise.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network,BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behaviour in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when when STP protocol tunnel status is set to Tunnel on the outgoing port.Dropped otherwise.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

2 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 · 1 source

Description 1

fsVlanTunnelStpAddress · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: fsVlanTunnelStpAddress

Technical details

{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsVlanTunnelStpAddress",
"OBJECT-TYPE",
"SYNTAX",
"MacAddress",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\" The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network, BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behavior in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when STP protocol tunnel status is set to Tunnel on the outgoing port, dropped otherwise.\"",
"::=",
"{",
"fsVlanTunnelObjects",
"2",
"}"
],
"syntax_tree": [
[
"row",
"MacAddress"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network, BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behavior in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when STP protocol tunnel status is set to Tunnel on the outgoing port, dropped otherwise."
],
null,
null,
null,
null
]
}

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.

Module: ARICENT-VLAN-EXT-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'MacAddress'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'Integer32', 'enterprises', 'Counter32'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'AricentMIVlan-MIB': ['VlanId']}
```
· Download ARICENT-VLAN-EXT-MIB
Related source files and packages:
- Observium Community original distribution archive

Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

fsVlanTunnelStpAddress · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsVlanTunnelStpAddress

Technical details

{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsVlanTunnelStpAddress",
"OBJECT-TYPE",
"SYNTAX",
"MacAddress",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\" The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network,BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behaviour in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when when STP protocol tunnel status is set to Tunnel on the outgoing port.Dropped otherwise.\"",
"::=",
"{",
"fsVlanTunnelObjects",
"2",
"}"
],
"syntax_tree": [
[
"row",
"MacAddress"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The MAC address to be used for Customer STP BPDUs tunneling. When STP tunneling is enabled on a port, this MAC address will be used as the the destination MAC address of the customer BPDUs received. This is the default behaviour in Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad bridges, this will be done only when the outgoing port type is proprietary PNP. Inside a given Network,BPDUs received with this MAC address will be treated as data packets and not processed. This is the default behaviour in case of Provider (Q-in-Q) Bridges and customer bridges. In case of 802.1ad Bridges, when the outgoing port type is not proprietary PNP, the destination address will be replaced with the reserved address defined for customer STP BPDU.Otherwise, they will be treated as data packets. When the BPDU is sent out of the given Network, this MAC address will be replaced with the reserved address defined for Customer STP BPDU. This is done only when when STP protocol tunnel status is set to Tunnel on the outgoing port.Dropped otherwise."
],
null,
null,
null,
null
]
}

Belden, GarrettCom and Hirschmann IT official standalone MIBs · Publisher's source file: fsvlnext.mib
Module: ARICENT-VLAN-EXT-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'MacAddress'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'Integer32', 'enterprises', 'Counter32'], 'P-BRIDGE-MIB': ['EnabledStatus']}
```
· Download fsvlnext.mib
Related source files and packages:
- Firmware > Magnum 5RX_10RX > 5RX_10RX MIB — 10RX_mibs.zip

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (16)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.2076.137.2.1	fsVlanTunnelBpduPri	0	0
1.3.6.1.4.1.2076.137.2.3	fsVlanTunnelLacpAddress	0	0
1.3.6.1.4.1.2076.137.2.4	fsVlanTunnelDot1xAddress	0	0
1.3.6.1.4.1.2076.137.2.5	fsVlanTunnelGvrpAddress	0	0
1.3.6.1.4.1.2076.137.2.6	fsVlanTunnelGmrpAddress	0	0
1.3.6.1.4.1.2076.137.2.7	fsVlanTunnelTable	1	3
1.3.6.1.4.1.2076.137.2.8	fsVlanTunnelProtocolTable	1	14
1.3.6.1.4.1.2076.137.2.9	fsVlanTunnelProtocolStatsTable	1	25
1.3.6.1.4.1.2076.137.2.10	fsVlanTunnelMvrpAddress	0	0
1.3.6.1.4.1.2076.137.2.11	fsVlanTunnelMmrpAddress	0	0
1.3.6.1.4.1.2076.137.2.12	fsVlanTunnelElmiAddress	0	0
1.3.6.1.4.1.2076.137.2.13	fsVlanTunnelLldpAddress	0	0
1.3.6.1.4.1.2076.137.2.14	fsVlanTunnelEcfmAddress	0	0
1.3.6.1.4.1.2076.137.2.15	fsServiceVlanTunnelProtocolTable	1	10
1.3.6.1.4.1.2076.137.2.16	fsVlanTunnelEoamAddress	0	0
1.3.6.1.4.1.2076.137.2.17	fsVlanTunnelIgmpAddress	0	0