Reference record for OID 1.3.6.1.4.1.193.72.300.30.1.30

Parent
1.3.6.1.4.1.193.72.300.30.1 (bridgeControl)
Node code
30
Node name
downstreamFlowWredConfigTable
Numeric OID
1.3.6.1.4.1.193.72.300.30.1.30
URN notation
urn:oid:1.3.6.1.4.1.193.72.300.30.1.30
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {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) downstreamFlowWredConfigTable(30)}
  • {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) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) downstreamFlowWredConfigTable(30)}
OID-IRI notation
  • /1/3/6/1/4/1/193/72/300/30/1/30
  • /ISO/Identified-Organization/6/1/4/1/193/72/300/30/1/30
  • /ISO/3/6/1/4/1/193/72/300/30/1/30
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/org/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/org/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/org/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/org/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/downstreamFlowWredConfigTable

Descriptions

downstreamFlowWredConfigTable — Ericsson MIB copies (MibBrowser.online)

The IP-DSLAM flow implementation allows multiple VLAN priorities to be mapped to the same downstream flow queue (downstream flows are configured with downstreamFlowConfigTable). Parameters in the downstreamFlowWredConfigTable are used to configure the discard probability of packets with different VLAN priority in the same downstream flow. The mechanisms Weighted Random Early Discard (WRED) is implemented to allow configuration of discard probability of packet with different VLAN priority. The WRED mechanism works as an extention to the other flow mechanisms in the IP-DSLAM. IP DSLAM __________________________________________________________________ | ______ | | ( ) ___ _ _ _ _ | | /--->( WRED )--->___Q3_|_|_|_|-->\ | | / (______) \ | | / ______ \ | | / ( ) ___ _ _ _ _ \ | | ___________/___/--->( WRED )--->___Q2_|_|_|_|-->\___\_______ | Aggregation | ( VLAN priority ) (______) ( ) | Network ---->|->( to flow ) ______ ( Scheduler )->|--> End-user | (____mapping____) ( ) ___ _ _ _ _ (___________) | | \ \--->( WRED )--->___Q1_|_|_|_|-->/ / | | \ (______) / | | \ ______ / | | \ ( ) ___ _ _ _ _ / | | \--->( WRED )--->___Q0_|_|_|_|-->/ | | (______) | | | | WRED = Weighted Random Early Discard | |__________________________________________________________________| The figure above illustrates where in the flow handling process the WRED is performed. Weighted Random Early Discard (WRED) is needed to ensure that high priority packets are favored over low priority packets when the downstream flow queue buffer usage gets close to the maximum buffer limit. Maximum buffer limit is configured with dfcMaxQueueBuffers. A flow has one downstream flow queue associated. All packets for this flow will be stored in the downstream flow queue, disregarding the packets VLAN priority, until they in turn are forwarded to the PVC in the subscriber line. The parameters wredBufferLimit and wredDropProbability are used to configure the WRED mechanism. dfcMaxQueueBuffers | V____________________________________________________________________________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Downstream flow queue | | | | | | | | | | | | |_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|________________________________|_|_|_|_|_|_|_|_|_|_|_| ^ ^ V | | | wredBufferLimit(x) wredBufferLimit(y) dfcMaxQueueBuffers (100%) (70%) in steps of 1 buffer In the figure above is illustrated that packets with VLAN priority X will not be discarded until all buffers in the downstream flow queue are in use while the WRED mechanism will start discarding packets with VLAN priority Y when 70% of the buffers in the downstream flow queue are in use. Valid from: EDA 2.2 R3A

Source records

downstreamFlowWredConfigTable

Status in source: current.

Names: downstreamFlowWredConfigTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "downstreamFlowWredConfigTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DownstreamFlowWredConfigEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The IP-DSLAM flow implementation allows multiple VLAN priorities to be mapped to the same downstream flow queue (downstream flows are configured with downstreamFlowConfigTable). Parameters in the downstreamFlowWredConfigTable are used to configure the discard probability of packets with different VLAN priority in the same downstream flow. The mechanisms Weighted Random Early Discard (WRED) is implemented to allow configuration of discard probability of packet with different VLAN priority. The WRED mechanism works as an extention to the other flow mechanisms in the IP-DSLAM. IP DSLAM __________________________________________________________________ | ______ | | ( ) ___ _ _ _ _ | | /--->( WRED )--->___Q3_|_|_|_|-->\\ | | / (______) \\ | | / ______ \\ | | / ( ) ___ _ _ _ _ \\ | | ___________/___/--->( WRED )--->___Q2_|_|_|_|-->\\___\\_______ | Aggregation | ( VLAN priority ) (______) ( ) | Network ---->|->( to flow ) ______ ( Scheduler )->|--> End-user | (____mapping____) ( ) ___ _ _ _ _ (___________) | | \\ \\--->( WRED )--->___Q1_|_|_|_|-->/ / | | \\ (______) / | | \\ ______ / | | \\ ( ) ___ _ _ _ _ / | | \\--->( WRED )--->___Q0_|_|_|_|-->/ | | (______) | | | | WRED = Weighted Random Early Discard | |__________________________________________________________________| The figure above illustrates where in the flow handling process the WRED is performed. Weighted Random Early Discard (WRED) is needed to ensure that high priority packets are favored over low priority packets when the downstream flow queue buffer usage gets close to the maximum buffer limit. Maximum buffer limit is configured with dfcMaxQueueBuffers. A flow has one downstream flow queue associated. All packets for this flow will be stored in the downstream flow queue, disregarding the packets VLAN priority, until they in turn are forwarded to the PVC in the subscriber line. The parameters wredBufferLimit and wredDropProbability are used to configure the WRED mechanism. dfcMaxQueueBuffers | V____________________________________________________________________________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Downstream flow queue | | | | | | | | | | | | |_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|________________________________|_|_|_|_|_|_|_|_|_|_|_| ^ ^ V | | | wredBufferLimit(x) wredBufferLimit(y) dfcMaxQueueBuffers (100%) (70%) in steps of 1 buffer In the figure above is illustrated that packets with VLAN priority X will not be discarded until all buffers in the downstream flow queue are in use while the WRED mechanism will start discarding packets with VLAN priority Y when 70% of the buffers in the downstream flow queue are in use. Valid from: EDA 2.2 R3A \"",
    "::=",
    "{",
    "bridgeControl",
    "30",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DownstreamFlowWredConfigEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The IP-DSLAM flow implementation allows multiple VLAN priorities to be mapped to the same downstream flow queue (downstream flows are configured with downstreamFlowConfigTable). Parameters in the downstreamFlowWredConfigTable are used to configure the discard probability of packets with different VLAN priority in the same downstream flow. The mechanisms Weighted Random Early Discard (WRED) is implemented to allow configuration of discard probability of packet with different VLAN priority. The WRED mechanism works as an extention to the other flow mechanisms in the IP-DSLAM. IP DSLAM __________________________________________________________________ | ______ | | ( ) ___ _ _ _ _ | | /--->( WRED )--->___Q3_|_|_|_|-->\\ | | / (______) \\ | | / ______ \\ | | / ( ) ___ _ _ _ _ \\ | | ___________/___/--->( WRED )--->___Q2_|_|_|_|-->\\___\\_______ | Aggregation | ( VLAN priority ) (______) ( ) | Network ---->|->( to flow ) ______ ( Scheduler )->|--> End-user | (____mapping____) ( ) ___ _ _ _ _ (___________) | | \\ \\--->( WRED )--->___Q1_|_|_|_|-->/ / | | \\ (______) / | | \\ ______ / | | \\ ( ) ___ _ _ _ _ / | | \\--->( WRED )--->___Q0_|_|_|_|-->/ | | (______) | | | | WRED = Weighted Random Early Discard | |__________________________________________________________________| The figure above illustrates where in the flow handling process the WRED is performed. Weighted Random Early Discard (WRED) is needed to ensure that high priority packets are favored over low priority packets when the downstream flow queue buffer usage gets close to the maximum buffer limit. Maximum buffer limit is configured with dfcMaxQueueBuffers. A flow has one downstream flow queue associated. All packets for this flow will be stored in the downstream flow queue, disregarding the packets VLAN priority, until they in turn are forwarded to the PVC in the subscriber line. The parameters wredBufferLimit and wredDropProbability are used to configure the WRED mechanism. dfcMaxQueueBuffers | V____________________________________________________________________________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Downstream flow queue | | | | | | | | | | | | |_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|________________________________|_|_|_|_|_|_|_|_|_|_|_| ^ ^ V | | | wredBufferLimit(x) wredBufferLimit(y) dfcMaxQueueBuffers (100%) (70%) in steps of 1 buffer In the figure above is illustrated that packets with VLAN priority X will not be discarded until all buffers in the downstream flow queue are in use while the WRED mechanism will start discarding packets with VLAN priority Y when 70% of the buffers in the downstream flow queue are in use. Valid from: EDA 2.2 R3A"
    ],
    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
    downstreamFlowWredConfigTable OBJECT-TYPE
    	  SYNTAX      SEQUENCE OF DownstreamFlowWredConfigEntry
      	MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
        "The IP-DSLAM flow implementation allows multiple VLAN priorities to be mapped to the same
         downstream flow queue (downstream flows are configured with downstreamFlowConfigTable).
         
         Parameters in the downstreamFlowWredConfigTable are used to configure the discard probability
         of packets with different VLAN priority in the same downstream flow. The mechanisms Weighted
         Random Early Discard (WRED) is implemented to allow configuration of discard probability of
         packet with different VLAN priority. The WRED mechanism works as an extention to the other
         flow mechanisms in the IP-DSLAM.
    
                                                        IP DSLAM
                           __________________________________________________________________
                          |                        ______                                    |
                          |                       (      )    ___  _ _ _ _                   |
                          |                  /--->( WRED )--->___Q3_|_|_|_|-->\              |
                          |                 /     (______)                     \             |
                          |                /       ______                       \            |
                          |               /       (      )    ___  _ _ _ _       \           |
                          |   ___________/___/--->( WRED )--->___Q2_|_|_|_|-->\___\_______   |
         Aggregation      |  ( VLAN priority )    (______)                    (           )  |
           Network   ---->|->(    to flow    )     ______                     ( Scheduler )->|--> End-user
                          |  (____mapping____)    (      )    ___  _ _ _ _    (___________)  |
                          |              \   \--->( WRED )--->___Q1_|_|_|_|-->/   /          |
                          |               \       (______)                       /           |
                          |                \       ______                       /            |
                          |                 \     (      )    ___  _ _ _ _     /             |
                          |                  \--->( WRED )--->___Q0_|_|_|_|-->/              |
                          |                       (______)                                   |
                          |                                                                  |
                          | WRED = Weighted Random Early Discard                             |
                          |__________________________________________________________________|
         
         The figure above illustrates where in the flow handling process the WRED is performed.
         
         Weighted Random Early Discard (WRED) is needed to ensure that high priority packets are
         favored over low priority packets when the downstream flow queue buffer usage gets close to
         the maximum buffer limit. Maximum buffer limit is configured with dfcMaxQueueBuffers.
         
         A flow has one downstream flow queue associated. All packets for this flow will be stored in
         the downstream flow queue, disregarding the packets VLAN priority, until they in turn are
         forwarded to the PVC in the subscriber line. The parameters wredBufferLimit and
         wredDropProbability are used to configure the WRED mechanism.
    
         dfcMaxQueueBuffers
                 |
                 V____________________________________________________________________________________
                 | | | | | | | | | | | | | | | |                                | | | | | | | | | | | |
                 | | | | | | | | | | | | | | | |     Downstream flow queue      | | | | | | | | | | | |
                 |_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|________________________________|_|_|_|_|_|_|_|_|_|_|_|
                 ^                       ^                                               V
                 |                       |                                               |
         wredBufferLimit(x)      wredBufferLimit(y)                             dfcMaxQueueBuffers
              (100%)                   (70%)                                    in steps of 1 buffer
         
         In the figure above is illustrated that packets with VLAN priority X will not be discarded
         until all buffers in the downstream flow queue are in use while the WRED mechanism will start
         discarding packets with VLAN priority Y when 70% of the buffers in the downstream flow queue
         are in use.
    
         Valid from:                EDA 2.2 R3A
        "                                               
        ::= { bridgeControl 30 }
    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::downstreamFlowWredConfigTable.
    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

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.193.72.300.30.1.30.5 downstreamFlowWredConfigEntry22

Siblings (27)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.193.72.300.30.1.1 lineIndex00
1.3.6.1.4.1.193.72.300.30.1.2 pvcIndex00
1.3.6.1.4.1.193.72.300.30.1.3 pvcTable184
1.3.6.1.4.1.193.72.300.30.1.4 pvcFiltersTable122
1.3.6.1.4.1.193.72.300.30.1.5 virtualMacAddressDomain00
1.3.6.1.4.1.193.72.300.30.1.6 maximumEthernetFrameSize00
1.3.6.1.4.1.193.72.300.30.1.7 lineTable16
1.3.6.1.4.1.193.72.300.30.1.8 virtualMacAddressNodeId00
1.3.6.1.4.1.193.72.300.30.1.9 vlanTagType00
1.3.6.1.4.1.193.72.300.30.1.10 virtualMacAddressNodeIdEx00
1.3.6.1.4.1.193.72.300.30.1.11 relayAgentEdaIp00
1.3.6.1.4.1.193.72.300.30.1.12 relayAgentEdaNodeId00
1.3.6.1.4.1.193.72.300.30.1.13 flowIndex00
1.3.6.1.4.1.193.72.300.30.1.14 downstreamFlowConfigTable17
1.3.6.1.4.1.193.72.300.30.1.15 downstreamFlowStatsTable16
1.3.6.1.4.1.193.72.300.30.1.16 upstreamFlowConfigTable17
1.3.6.1.4.1.193.72.300.30.1.17 upstreamFlowStatsTable15
1.3.6.1.4.1.193.72.300.30.1.18 mcastFilter211
1.3.6.1.4.1.193.72.300.30.1.19 macHistoryTable14
1.3.6.1.4.1.193.72.300.30.1.20 macFilterAgedTime00
1.3.6.1.4.1.193.72.300.30.1.21 accessControlList651
1.3.6.1.4.1.193.72.300.30.1.22 subsIpFilter29
1.3.6.1.4.1.193.72.300.30.1.24 priorityIndex00
1.3.6.1.4.1.193.72.300.30.1.31 downstreamFlowWredStatisticsTable15
1.3.6.1.4.1.193.72.300.30.1.32 subscriberInfoTable18
1.3.6.1.4.1.193.72.300.30.1.36 mcastGroupInfoTable17
1.3.6.1.4.1.193.72.300.30.1.40 trafficStatistics3122