Reference record for OID 1.3.6.1.4.1.193.72.300.30.1.3.1.64

Parent
1.3.6.1.4.1.193.72.300.30.1.3.1 (pvcEntry)
Node code
64
Node name
l2cpTunneling
Numeric OID
1.3.6.1.4.1.193.72.300.30.1.3.1.64
URN notation
urn:oid:1.3.6.1.4.1.193.72.300.30.1.3.1.64
ASN.1 notation

{1 3 6 1 4 1 193 72 300 30 1 3 1 64}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) pvcTable(3) pvcEntry(1) l2cpTunneling(64)}
OID-IRI notation
  • /1/3/6/1/4/1/193/72/300/30/1/3/1/64
  • /ISO/Identified-Organization/6/1/4/1/193/72/300/30/1/3/1/64
  • /ISO/3/6/1/4/1/193/72/300/30/1/3/1/64
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/org/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/org/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/org/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/org/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling
  • /iso/iso-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/pvcTable/pvcEntry/l2cpTunneling

Descriptions

l2cpTunneling — Ericsson MIB copies (MibBrowser.online)

This parameter is used to enable Layer 2 Protocol Tunneling. The tunneling mechanism is a propritary solution specified by Cisco. The Layer 2 Control Protocol tunneling feature is only available when accessMethod is transparrentLan. Customers at different sites connected across a SP network need to use various Layer 2 protocols to scale their topologies to include all remote sites, as well as the local sites. STP must run properly, and every VLAN should build a proper spanning tree that includes the local site and all remote sites across the SP network. Cisco Discovery Protocol (CDP) must discover neighboring Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP) must provide consistent VLAN configuration throughout all sites in the customer network. When protocol tunneling is enabled, DSLAM on the inbound side of the SP network encapsulate Layer 2 protocol packets with a special MAC address and send them across the SP network. Core switches in the network do not process these packets but forward them as normal packets. Layer 2 protocol data units (PDUs) for CDP, STP, or VTP cross the SP network and are delivered to customer switches on the outbound side of the SP network. Identical packets are received by all customer ports on the same VLANs with these results: Users on each of a customer's sites can properly run STP, and every VLAN can build a correct spanning tree, based on parameters from all sites and not just from the local site. CDP discovers and shows information about the other Cisco devices connected through the SP network. VTP provides consistent VLAN configuration throughout the customer network, propagating to all switches through the SP. When the Layer 2 PDUs that entered the DSLAM on the inbound side, the DSLAM overwrites the customer PDU-destination MAC address with a well-known Cisco proprietary multicast address (01-00-0c-cd-cd-d0). The DSLAM on the outbound side restore the proper Layer 2 protocol and MAC address information and forward the packets to all PVCs in the same VLAN. Therefore, the Layer 2 PDUs remain intact and are delivered across the SP network to the other side of the customer network. Tunneling of Layer 2 control protocols is enabled using this bit-map. The various bit positions are: 0 stp When set Layer 2 Control Protocol tunneling is enabled for Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00) 1 pvstp When set Layer 2 Control Protocol tunneling is enabled for Per VLAN Spanning Tree Protocol, a Cisco specified extension to STP (destination MAC = 01:00:0c:cc:cc:cd). 2 cdp When set Layer 2 Control Protocol tunneling is enabled for Cisco Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc). 3 vtp When set Layer 2 Control Protocol tunneling is enabled for Virtual Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc). Valid from: EDA 2.1 SP2

Source records

l2cpTunneling

Status in source: current.

Names: l2cpTunneling

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "l2cpTunneling",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "stp",
    "(",
    "0",
    ")",
    ",",
    "pvstp",
    "(",
    "1",
    ")",
    ",",
    "cdp",
    "(",
    "2",
    ")",
    ",",
    "vtp",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This parameter is used to enable Layer 2 Protocol Tunneling. The tunneling mechanism is a propritary solution specified by Cisco. The Layer 2 Control Protocol tunneling feature is only available when accessMethod is transparrentLan. Customers at different sites connected across a SP network need to use various Layer 2 protocols to scale their topologies to include all remote sites, as well as the local sites. STP must run properly, and every VLAN should build a proper spanning tree that includes the local site and all remote sites across the SP network. Cisco Discovery Protocol (CDP) must discover neighboring Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP) must provide consistent VLAN configuration throughout all sites in the customer network. When protocol tunneling is enabled, DSLAM on the inbound side of the SP network encapsulate Layer 2 protocol packets with a special MAC address and send them across the SP network. Core switches in the network do not process these packets but forward them as normal packets. Layer 2 protocol data units (PDUs) for CDP, STP, or VTP cross the SP network and are delivered to customer switches on the outbound side of the SP network. Identical packets are received by all customer ports on the same VLANs with these results: Users on each of a customer's sites can properly run STP, and every VLAN can build a correct spanning tree, based on parameters from all sites and not just from the local site. CDP discovers and shows information about the other Cisco devices connected through the SP network. VTP provides consistent VLAN configuration throughout the customer network, propagating to all switches through the SP. When the Layer 2 PDUs that entered the DSLAM on the inbound side, the DSLAM overwrites the customer PDU-destination MAC address with a well-known Cisco proprietary multicast address (01-00-0c-cd-cd-d0). The DSLAM on the outbound side restore the proper Layer 2 protocol and MAC address information and forward the packets to all PVCs in the same VLAN. Therefore, the Layer 2 PDUs remain intact and are delivered across the SP network to the other side of the customer network. Tunneling of Layer 2 control protocols is enabled using this bit-map. The various bit positions are: 0 stp When set Layer 2 Control Protocol tunneling is enabled for Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00) 1 pvstp When set Layer 2 Control Protocol tunneling is enabled for Per VLAN Spanning Tree Protocol, a Cisco specified extension to STP (destination MAC = 01:00:0c:cc:cc:cd). 2 cdp When set Layer 2 Control Protocol tunneling is enabled for Cisco Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc). 3 vtp When set Layer 2 Control Protocol tunneling is enabled for Virtual Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc). Valid from: EDA 2.1 SP2 \"",
    "::=",
    "{",
    "pvcEntry",
    "64",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "stp",
          0
        ],
        [
          "pvstp",
          1
        ],
        [
          "cdp",
          2
        ],
        [
          "vtp",
          3
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This parameter is used to enable Layer 2 Protocol Tunneling. The tunneling mechanism is a propritary solution specified by Cisco. The Layer 2 Control Protocol tunneling feature is only available when accessMethod is transparrentLan. Customers at different sites connected across a SP network need to use various Layer 2 protocols to scale their topologies to include all remote sites, as well as the local sites. STP must run properly, and every VLAN should build a proper spanning tree that includes the local site and all remote sites across the SP network. Cisco Discovery Protocol (CDP) must discover neighboring Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP) must provide consistent VLAN configuration throughout all sites in the customer network. When protocol tunneling is enabled, DSLAM on the inbound side of the SP network encapsulate Layer 2 protocol packets with a special MAC address and send them across the SP network. Core switches in the network do not process these packets but forward them as normal packets. Layer 2 protocol data units (PDUs) for CDP, STP, or VTP cross the SP network and are delivered to customer switches on the outbound side of the SP network. Identical packets are received by all customer ports on the same VLANs with these results: Users on each of a customer's sites can properly run STP, and every VLAN can build a correct spanning tree, based on parameters from all sites and not just from the local site. CDP discovers and shows information about the other Cisco devices connected through the SP network. VTP provides consistent VLAN configuration throughout the customer network, propagating to all switches through the SP. When the Layer 2 PDUs that entered the DSLAM on the inbound side, the DSLAM overwrites the customer PDU-destination MAC address with a well-known Cisco proprietary multicast address (01-00-0c-cd-cd-d0). The DSLAM on the outbound side restore the proper Layer 2 protocol and MAC address information and forward the packets to all PVCs in the same VLAN. Therefore, the Layer 2 PDUs remain intact and are delivered across the SP network to the other side of the customer network. Tunneling of Layer 2 control protocols is enabled using this bit-map. The various bit positions are: 0 stp When set Layer 2 Control Protocol tunneling is enabled for Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00) 1 pvstp When set Layer 2 Control Protocol tunneling is enabled for Per VLAN Spanning Tree Protocol, a Cisco specified extension to STP (destination MAC = 01:00:0c:cc:cc:cd). 2 cdp When set Layer 2 Control Protocol tunneling is enabled for Cisco Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc). 3 vtp When set Layer 2 Control Protocol tunneling is enabled for Virtual Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc). Valid from: EDA 2.1 SP2"
    ],
    null,
    null,
    null,
    null
  ]
}
  • Ericsson MIB copies (MibBrowser.online) · Publisher's source file: PEA-BRIDGE-IPDSLAM — archive MIB indexed for Ericsson

    Vendor MIB copy from the MibBrowser.online archive. Ericsson support.

    Module: PEA-BRIDGE-IPDSLAM

    Published definition
    l2cpTunneling OBJECT-TYPE
        SYNTAX      BITS {
                          stp(0),
                          pvstp(1),
                          cdp(2),
                          vtp(3)
                         }
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
        "This parameter is used to enable Layer 2 Protocol Tunneling. The tunneling
         mechanism is a propritary solution specified by Cisco. The Layer 2 Control
         Protocol tunneling feature is only available when accessMethod is
         transparrentLan.
         
         Customers at different sites connected across a SP network need to use
         various Layer 2 protocols to scale their topologies to include all remote
         sites, as well as the local sites. STP must run properly, and every VLAN
         should build a proper spanning tree that includes the local site and all
         remote sites across the SP network. Cisco Discovery Protocol (CDP) must
         discover neighboring Cisco devices from local and remote sites. VLAN
         Trunking Protocol (VTP) must provide consistent VLAN configuration
         throughout all sites in the customer network.
         
         When protocol tunneling is enabled, DSLAM on the inbound side of the SP
         network encapsulate Layer 2 protocol packets with a special MAC address
         and send them across the SP network. Core switches in the network do not
         process these packets but forward them as normal packets. Layer 2 protocol
         data units (PDUs) for CDP, STP, or VTP cross the SP network and are
         delivered to customer switches on the outbound side of the SP network.
         Identical packets are received by all customer ports on the same VLANs
         with these results:
         Users on each of a customer's sites can properly run STP, and every VLAN
         can build a correct spanning tree, based on parameters from all sites and
         not just from the local site.
         CDP discovers and shows information about the other Cisco devices connected
         through the SP network.
         VTP provides consistent VLAN configuration throughout the customer network,
         propagating to all switches through the SP.
         
         When the Layer 2 PDUs that entered the DSLAM on the inbound side, the DSLAM
         overwrites the customer PDU-destination MAC address with a well-known Cisco
         proprietary multicast address (01-00-0c-cd-cd-d0).
         The DSLAM on the outbound side restore the proper Layer 2 protocol and MAC
         address information and forward the packets to all PVCs in the same VLAN.
         Therefore, the Layer 2 PDUs remain intact and are delivered across the SP
         network to the other side of the customer network.
        
         Tunneling of Layer 2 control protocols is enabled using this bit-map.
    
         The various bit positions are:
         0    stp      When set Layer 2 Control Protocol tunneling is enabled for
                       Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00)
         1    pvstp    When set Layer 2 Control Protocol tunneling is enabled for
                       Per VLAN Spanning Tree Protocol, a Cisco specified extension
                       to STP (destination MAC = 01:00:0c:cc:cc:cd).
         2    cdp      When set Layer 2 Control Protocol tunneling is enabled for
                       Cisco Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc).
         3    vtp      When set Layer 2 Control Protocol tunneling is enabled for
                       Virtual Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc).
    
         Valid from:                EDA 2.1 SP2
         "
        ::= { pvcEntry 64 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'TEXTUAL-CONVENTION', 'MacAddress', 'RowStatus', 'DateAndTime'], 'DIESEL-SMI': ['peaIpDslam'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'Unsigned32', 'IpAddress', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Counter32', 'Counter64', 'TimeTicks'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber']}
    · Download PEA-BRIDGE-IPDSLAM — archive MIB indexed for Ericsson

    Related source files and packages:

    • DIESEL-SMI — archive MIB indexed for EricssonNative third-party archive copy; vendor association comes from the archive catalog and does not establish a current manufacturer release; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:11 GMT; 380 bytes
    • INET-ADDRESS-MIB — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Native LAST-UPDATED: 200502040000Z; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:05 GMT; 17,177 bytes
    • SNMPv2-SMI — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:04 GMT; 10,283 bytes
    Show all 4 related files and packages
    • SNMPv2-TC — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:11 GMT; 38,034 bytes

    Source location: PEA-BRIDGE-IPDSLAM::l2cpTunneling.
    Source version and references

    Published package: Ericsson archived MIB 200604251200Z; file: PEA-BRIDGE-IPDSLAM.mib.

    Native third-party archive copy; vendor association comes from the archive catalog and does not establish a current manufacturer release; Native LAST-UPDATED: 200604251200Z; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:13 GMT; 256,722 bytes

    Downloaded: 2026-10-27T05:19:20.410930+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.193)

David Partain

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.193)

Daniel Farias

Siblings (82)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.193.72.300.30.1.3.1.52 vlanPrioMappingPrio200
1.3.6.1.4.1.193.72.300.30.1.3.1.53 vlanPrioMappingPrio300
1.3.6.1.4.1.193.72.300.30.1.3.1.54 vlanPrioMappingPrio400
1.3.6.1.4.1.193.72.300.30.1.3.1.55 vlanPrioMappingPrio500
1.3.6.1.4.1.193.72.300.30.1.3.1.56 vlanPrioMappingPrio600
1.3.6.1.4.1.193.72.300.30.1.3.1.57 vlanPrioMappingPrio700
1.3.6.1.4.1.193.72.300.30.1.3.1.58 downstreamFlows00
1.3.6.1.4.1.193.72.300.30.1.3.1.59 upstreamFlows00
1.3.6.1.4.1.193.72.300.30.1.3.1.60 flowIdentificationCriterionDownstream00
1.3.6.1.4.1.193.72.300.30.1.3.1.61 flowIdentificationCriterionUpstream00
1.3.6.1.4.1.193.72.300.30.1.3.1.62 schedulingScheme00
1.3.6.1.4.1.193.72.300.30.1.3.1.63 floodDownstreamUnknownDestMac00
1.3.6.1.4.1.193.72.300.30.1.3.1.65 upstreamMcastEnable00
1.3.6.1.4.1.193.72.300.30.1.3.1.66 clearDhcpLeaseTable00
1.3.6.1.4.1.193.72.300.30.1.3.1.67 clearMACHistory00
1.3.6.1.4.1.193.72.300.30.1.3.1.68 gatewayMacfilteringDirection00
1.3.6.1.4.1.193.72.300.30.1.3.1.69 downstreamFramesPerSecond00
1.3.6.1.4.1.193.72.300.30.1.3.1.70 upstreamFramesPerSecond00
1.3.6.1.4.1.193.72.300.30.1.3.1.71 downstreamBitsPerSecond00
1.3.6.1.4.1.193.72.300.30.1.3.1.72 upstreamBitsPerSecond00
1.3.6.1.4.1.193.72.300.30.1.3.1.73 arpProxyConfig00
1.3.6.1.4.1.193.72.300.30.1.3.1.80 endUserVlanOperation00
1.3.6.1.4.1.193.72.300.30.1.3.1.85 vlanIdFilter00
1.3.6.1.4.1.193.72.300.30.1.3.1.90 pvcFilterVersion00
1.3.6.1.4.1.193.72.300.30.1.3.1.93 pvcUpstreamVlanIdAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.94 pvcDownstreamVlanIdAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.95 pvcUpstreamEtherTypeAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.100 pvcDownstreamEtherTypeAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.105 pvcUpstreamIpAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.110 pvcDownstreamIpAclId00
1.3.6.1.4.1.193.72.300.30.1.3.1.115 dhcpServerMacAddress00
1.3.6.1.4.1.193.72.300.30.1.3.1.120 allowAnonymousMulticastSubscriber00