Reference record for OID 1.3.6.1.2.1.17.7.1.4.6


parent
1.3.6.1.2.1.17.7.1.4 (dot1qVlan)
node code
6
node name
dot1qPortVlanStatisticsTable
dot oid
1.3.6.1.2.1.17.7.1.4.6
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) bridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dot1dBridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) dot1dBridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) bridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) dot1dBridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) bridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dot1dBridge(17) qBridgeMIB(7) qBridgeMIBObjects(1) dot1qVlan(4) dot1qPortVlanStatisticsTable(6)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/bridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dot1dBridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • ...skipped...
  • /iso/org/dod/internet/mgmt/mib-2/bridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • /iso/org/dod/internet/mgmt/mib-2/dot1dBridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • /iso/org/dod/internet/mgmt/mib/bridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • /iso/org/dod/internet/mgmt/mib/dot1dBridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/bridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/dot1dBridge/qBridgeMIB/qBridgeMIBObjects/dot1qVlan/dot1qPortVlanStatisticsTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/17/7/1/4/6

    Description by circitor

    A table containing per-port, per-VLAN statistics for
    traffic received. Separate objects are provided for both the
    most-significant and least-significant bits of statistics
    counters for ports that are associated with this transparent
    bridge. The most-significant bit objects are only required on
    high-capacity interfaces, as defined in the conformance clauses
    for these objects. This mechanism is provided as a way to read
    64-bit counters for agents that support only SNMPv1.

    Note that the reporting of most-significant and least-
    significant counter bits separately runs the risk of missing
    an overflow of the lower bits in the interval between sampling.
    The manager must be aware of this possibility, even within the
    same varbindlist, when interpreting the results of a request or



    asynchronous notification.

    Parsed from file Q-BRIDGE-MIB.mib
    Module: Q-BRIDGE-MIB

    Description by cisco_v1

    A table containing per-port, per-VLAN statistics for
    traffic received. Separate objects are provided for both the
    most-significant and least-significant bits of statistics
    counters for ports that are associated with this transparent
    bridge. The most-significant bit objects are only required on
    high capacity interfaces, as defined in the conformance clauses
    for these objects. This mechanism is provided as a way to read
    64-bit counters for agents which support only SNMPv1.

    Note that the reporting of most-significant and least-
    significant counter bits separately runs the risk of missing
    an overflow of the lower bits in the interval between sampling.
    The manager must be aware of this possibility, even within the
    same varbindlist, when interpreting the results of a request or
    asynchronous notification.

    Description by oid_info

    dot1qPortVlanStatisticsTable OBJECT-TYPE
    SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "A table containing per-port, per-VLAN statistics for
    traffic received. Separate objects are provided for both the
    most-significant and least-significant bits of statistics
    counters for ports that are associated with this transparent
    bridge. The most-significant bit objects are only required on
    high capacity interfaces, as defined in the conformance clauses
    for these objects. This mechanism is provided as a way to read
    64-bit counters for agents which support only SNMPv1.
    Note that the reporting of most-significant and least-
    significant counter bits separately runs the risk of missing
    an overflow of the lower bits in the interval between sampling.
    The manager must be aware of this possibility, even within the
    same varbindlist, when interpreting the results of a request or
    asynchronous notification."

    View at oid-info.com

    Description by mibdepot

    A table containing per-port, per-VLAN statistics for
    traffic received. Separate objects are provided for both the
    most-significant and least-significant bits of statistics
    counters for ports that are associated with this transparent
    bridge. The most-significant bit objects are only required on
    high-capacity interfaces, as defined in the conformance clauses
    for these objects. This mechanism is provided as a way to read
    64-bit counters for agents that support only SNMPv1.

    Note that the reporting of most-significant and least-
    significant counter bits separately runs the risk of missing
    an overflow of the lower bits in the interval between sampling.
    The manager must be aware of this possibility, even within the
    same varbindlist, when interpreting the results of a request or



    asynchronous notification.

    Parsed from file Q-BRIDGE-MIB.mib.txt
    Company: None
    Module: Q-BRIDGE-MIB

    Description by cisco

    A table containing per-port, per-VLAN statistics for
    traffic received. Separate objects are provided for both the
    most-significant and least-significant bits of statistics
    counters for ports that are associated with this transparent
    bridge. The most-significant bit objects are only required on
    high capacity interfaces, as defined in the conformance clauses
    for these objects. This mechanism is provided as a way to read
    64-bit counters for agents which support only SNMPv1.

    Note that the reporting of most-significant and least-
    significant counter bits separately runs the risk of missing
    an overflow of the lower bits in the interval between sampling.
    The manager must be aware of this possibility, even within the
    same varbindlist, when interpreting the results of a request or
    asynchronous notification.

    Information by circitor

    dot1qPortVlanStatisticsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high-capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification." ::= { dot1qVlan 6 }

    Information by cisco_v1

    dot1qPortVlanStatisticsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification." ::= { dot1qVlan 6 }

    Information by oid_info

    Automatically extracted from RFC2674

    Information by mibdepot

    dot1qPortVlanStatisticsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high-capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification." ::= { dot1qVlan 6 }

    Information by cisco

    dot1qPortVlanStatisticsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification." ::= { dot1qVlan 6 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.17.7.1.4.6.1 dot1qPortVlanStatisticsEntry 6 6 Traffic statistics for a VLAN on an interface.

    Brothers (10)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.17.7.1.4.1 dot1qVlanNumDeletes 1 1 The number of times a VLAN entry has been deleted from
    the dot1qVlanCurrentTable (for any reason). If an entry
    is deleted, then …
    1.3.6.1.2.1.17.7.1.4.2 dot1qVlanCurrentTable 1 8 A table containing current configuration information
    for each VLAN currently configured into the device by
    (local or network) man…
    1.3.6.1.2.1.17.7.1.4.3 dot1qVlanStaticTable 1 6 A table containing static configuration information for
    each VLAN configured into the device by (local or
    network) management. A…
    1.3.6.1.2.1.17.7.1.4.4 dot1qNextFreeLocalVlanIndex, dot1qPortVlanTable 2 7 A table containing per port control and status
    information for VLAN configuration in the device.
    1.3.6.1.2.1.17.7.1.4.5 dot1qPortVlanTable 1 8 A table containing per-port control and status
    information for VLAN configuration in the device.
    1.3.6.1.2.1.17.7.1.4.7 dot1qPortVlanHCStatisticsTable 1 4 A table containing per-port, per-VLAN statistics for
    traffic on high-capacity interfaces.
    1.3.6.1.2.1.17.7.1.4.8 dot1qLearningConstraintsTable 1 5 A table containing learning constraints for sets of
    Shared and Independent VLANs.
    1.3.6.1.2.1.17.7.1.4.9 dot1qConstraintSetDefault 1 1 The identity of the constraint set to which a VLAN
    belongs, if there is not an explicit entry for that VLAN
    in dot1qLearningConst…
    1.3.6.1.2.1.17.7.1.4.10 dot1qConstraintTypeDefault 1 1 The type of constraint set to which a VLAN belongs, if
    there is not an explicit entry for that VLAN in
    dot1qLearningConstraintsTa…
    1.3.6.1.2.1.17.7.1.4.11 dot1qExtPortVlanTable 1 2 A table containing per port Restricted VLAN Registration
    control information.