{1 3 6 1 4 1 11 2 14 11 15 2 74 1 1 1 4}
In some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. hpnicfAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.
Status in source: current.
Names: hpnicfAcfpServerCurContextType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpnicfAcfpServerCurContextType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"no-context",
"(",
"1",
")",
",",
"context-VLANID",
"(",
"2",
")",
",",
"context-HG",
"(",
"3",
")",
",",
"context-FlowID",
"(",
"4",
")",
",",
"context-HGPlus",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"In some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. hpnicfAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.\"",
"::=",
"{",
"hpnicfAcfpServer",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"no-context",
1
],
[
"context-VLANID",
2
],
[
"context-HG",
3
],
[
"context-FlowID",
4
],
[
"context-HGPlus",
5
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"In some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. hpnicfAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPN-ICF-ACFP-MIB
hpnicfAcfpServerCurContextType OBJECT-TYPE
SYNTAX INTEGER
{
no-context(1),
context-VLANID(2),
context-HG(3),
context-FlowID(4),
context-HGPlus(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In some circumstances, it's necessary that packets go to
ACFP client with context from ACFP server. However, the context
perhaps is different. hpnicfAcfpServerCurContextType is
used to distinguish this difference, ACFP client may
process distinctively."
::= { hpnicfAcfpServer 4 }{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'MacAddress', 'DisplayString'], 'SNMPv2-SMI': ['IpAddress', 'Integer32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfCommon'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength']}Related source files and packages:
Downloaded: 2026-10-23T19:25:40.636293+00:00.
Vendor MIB copy from the Netdisco archive.
Module: HPN-ICF-ACFP-MIB
hpnicfAcfpServerCurContextType OBJECT-TYPE
SYNTAX INTEGER
{
no-context(1),
context-VLANID(2),
context-HG(3),
context-FlowID(4),
context-HGPlus(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In some circumstances, it's necessary that packets go to
ACFP client with context from ACFP server. However, the context
perhaps is different. hpnicfAcfpServerCurContextType is
used to distinguish this difference, ACFP client may
process distinctively."
::= { hpnicfAcfpServer 4 }{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'MacAddress', 'DisplayString'], 'SNMPv2-SMI': ['IpAddress', 'Integer32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfCommon'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength']}Related source files and packages:
Downloaded: 2026-10-24T15:28:10.476994+00:00.
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.14.11.15.2.74.1.1.1.1 | hpnicfAcfpServerInfo | 0 | 0 | |
| 1.3.6.1.4.1.11.2.14.11.15.2.74.1.1.1.2 | hpnicfAcfpServerMaxLifetime | 0 | 0 | |
| 1.3.6.1.4.1.11.2.14.11.15.2.74.1.1.1.3 | hpnicfAcfpServerPersistentRules | 0 | 0 |