Status in source: current.
Names: rlPolicyFlowClassificationOffsetsTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlPolicyFlowClassificationOffsetsTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"RlPolicyFlowClassificationOffsetsGroupEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Specifies the byte offsets that the platform can use for policy decisions. This table is used for platforms which impose limitations on choosing the OMPCs for classification. If the platform does not impose any limitations, the value of rlPolicyFlowClassificationOffsetsGroupScheme is allOffsetsPermitted. Each entry in the table specifies a combination of byte offsets which can be used to specify flow classification. A rule may use a subset of the bytes of its Offset Group. The maximum value for each offset is given by rlPolicyFlowClassificationOffsetGroupMaximumOffset. The maximum number of offsets per Offset Group is given by rlPolicyNumberOfOffsetsPerFlowClassificationOffsetGroup.\"",
"::=",
"{",
"rlPolicyClassifier",
"2",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"RlPolicyFlowClassificationOffsetsGroupEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Specifies the byte offsets that the platform can use for policy decisions. This table is used for platforms which impose limitations on choosing the OMPCs for classification. If the platform does not impose any limitations, the value of rlPolicyFlowClassificationOffsetsGroupScheme is allOffsetsPermitted. Each entry in the table specifies a combination of byte offsets which can be used to specify flow classification. A rule may use a subset of the bytes of its Offset Group. The maximum value for each offset is given by rlPolicyFlowClassificationOffsetGroupMaximumOffset. The maximum number of offsets per Offset Group is given by rlPolicyNumberOfOffsetsPerFlowClassificationOffsetGroup."
],
null,
null,
null,
null
]
}
- HPE Instant On official MIBs
· Publisher's source file: hpe-policy.mib
Module: HPE-POLICY-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndexOrZero', 'InterfaceIndex'], 'HPE-MIB': ['Percents', 'VlanPriority', 'nm'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'RowPointer', 'DisplayString'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Counter32', 'zeroDotZero', 'MODULE-IDENTITY', 'Counter64'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DIFF-SERV-MIB': ['diffServClassifierEntry'], 'HPE-BRIDGEMIBOBJECTS-MIB': ['VlanList1', 'VlanList2', 'VlanList3', 'VlanList4']}Same file in HPE Instant On 1960 2.6.0.73.
Same file in HPE Instant On 1960 2.7.0.103.
Same file in HPE Instant On 1930 2.6.0.73.
Same file in HPE Instant On 1960 2.8.1.35.
- HPE networking MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
HPE networking support.
Module: HPE-POLICY-MIB
Same published definition
Module imports
{'IF-MIB': ['InterfaceIndexOrZero', 'InterfaceIndex'], 'HPE-MIB': ['Percents', 'VlanPriority', 'nm'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'RowPointer', 'DisplayString'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Counter32', 'zeroDotZero', 'MODULE-IDENTITY', 'Counter64'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DIFF-SERV-MIB': ['diffServClassifierEntry'], 'HPE-BRIDGEMIBOBJECTS-MIB': ['VlanList1', 'VlanList2', 'VlanList3', 'VlanList4']}
Related source files and packages: