OID reference

h3cQoSTrafficFilterTable

1.3.6.1.4.1.43.45.1.10.2.17.1.2.3

Description

Traffic filter table is used to deny or permit packets. IP and Link ACL rules can be applied simultaneously, IP and User based ACL rules can not be applied simultaneously, Link and User based ACL rules can not be applied simultaneously. Unused ones is represented with default values. To deny or permit packets,the ACL …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.17.1.2 (h3cQoSAction)
Node code
3
Node name
h3cQoSTrafficFilterTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.17.1.2.3
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.17.1.2.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 17 1 2 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cQosProfile(17) h3cQoSProfObjects(1) h3cQoSAction(2) h3cQoSTrafficFilterTable(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/17/1/2/3
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/17/1/2/3
  • /ISO/3/6/1/4/1/43/45/1/10/2/17/1/2/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cQosProfile/h3cQoSProfObjects/h3cQoSAction/h3cQoSTrafficFilterTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF H3cQoSTrafficFilterEntry
Maximum access defined by MIB
not-accessible
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.

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

Show 2 published definitions

h3cQoSTrafficFilterTable · current

h3cQoSTrafficFilterTable OBJECT-TYPE
			SYNTAX SEQUENCE OF H3cQoSTrafficFilterEntry
			MAX-ACCESS not-accessible
			STATUS current
			DESCRIPTION
				"Traffic filter table is used to deny or permit packets.
				IP and Link ACL rules can be applied simultaneously,
				IP and User based ACL rules can not be applied simultaneously,
				Link and User based ACL rules can not be applied simultaneously.
				Unused ones is represented with default values.
				To deny or permit packets,the ACL rules should be defined in h3cAcl table.
				The 'deny' or 'permit' action should be defined with ACL rules.
				In this table,a predefined ACL rules can be referenced in a specified QOS profile group.
				'Direction' means the ACL rules can be applied to the inbound or outbound packets.
				
				"
			::= { h3cQoSAction 3 }

h3cQoSTrafficFilterTable · current

h3cQoSTrafficFilterTable OBJECT-TYPE
			SYNTAX SEQUENCE OF H3cQoSTrafficFilterEntry
			MAX-ACCESS not-accessible
			STATUS current
			DESCRIPTION
				"Traffic filter table is used to deny or permit packets.
				IP and Link ACL rules can be applied simultaneously,
				IP and User based ACL rules can not be applied simultaneously,
				Link and User based ACL rules can not be applied simultaneously.
				Unused ones is represented with default values.
				To deny or permit packets,the ACL rules should be defined in h3cAcl table.
				The 'deny' or 'permit' action should be defined with ACL rules.
				In this table,a predefined ACL rules can be referenced in a specified QOS profile group.
				'Direction' means the ACL rules can be applied to the inbound or outbound packets.
				
				"
			::= { h3cQoSAction 3 }

Meaning

Descriptions

1 unique

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

Traffic filter table is used to deny or permit packets. IP and Link ACL rules can be applied simultaneously, IP and User based ACL rules can not be applied simultaneously, Link and User based ACL rules can not be applied simultaneously. Unused ones is represented with default values. To deny or permit packets,the ACL rules should be defined in h3cAcl table. The 'deny' or 'permit' action should be defined with ACL rules. In this table,a predefined ACL rules can be referenced in a specified QOS profile group. 'Direction' means the ACL rules can be applied to the inbound or outbound packets.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cQoSTrafficFilterTable · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cQoSTrafficFilterTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cQoSTrafficFilterTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cQoSTrafficFilterEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Traffic filter table is used to deny or permit packets. IP and Link ACL rules can be applied simultaneously, IP and User based ACL rules can not be applied simultaneously, Link and User based ACL rules can not be applied simultaneously. Unused ones is represented with default values. To deny or permit packets,the ACL rules should be defined in h3cAcl table. The 'deny' or 'permit' action should be defined with ACL rules. In this table,a predefined ACL rules can be referenced in a specified QOS profile group. 'Direction' means the ACL rules can be applied to the inbound or outbound packets. \"",
    "::=",
    "{",
    "h3cQoSAction",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cQoSTrafficFilterEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Traffic filter table is used to deny or permit packets. IP and Link ACL rules can be applied simultaneously, IP and User based ACL rules can not be applied simultaneously, Link and User based ACL rules can not be applied simultaneously. Unused ones is represented with default values. To deny or permit packets,the ACL rules should be defined in h3cAcl table. The 'deny' or 'permit' action should be defined with ACL rules. In this table,a predefined ACL rules can be referenced in a specified QOS profile group. 'Direction' means the ACL rules can be applied to the inbound or outbound packets."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.17.1.2.3.1 h3cQoSTrafficFilterEntry1010

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.17.1.2.1 h3cQoSTrafficLimitTable125
1.3.6.1.4.1.43.45.1.10.2.17.1.2.2 h3cQoSTrafficPriorityTable123