OID reference

h3cAcfpServerCurContextType

1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.4

Description

In some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. h3cAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.74.1.1.1 (h3cAcfpServer)
Node code
4
Node name
h3cAcfpServerCurContextType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {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) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {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) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {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) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {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) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cAcfp(74) h3cAcfpObjects(1) h3cAcfpOAP(1) h3cAcfpServer(1) h3cAcfpServerCurContextType(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/74/1/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/74/1/1/1/4
  • /ISO/3/6/1/4/1/43/45/1/10/2/74/1/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cAcfp/h3cAcfpObjects/h3cAcfpOAP/h3cAcfpServer/h3cAcfpServerCurContextType
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current

Enumerated values

ValueName
1no-context
2context-VLANID
3context-HG
4context-FlowID
5context-HGPlus

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.4.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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

h3cAcfpServerCurContextType · current

h3cAcfpServerCurContextType 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.  h3cAcfpServerCurContextType is
        used to distinguish this difference, ACFP client may
        process distinctively."
    ::= { h3cAcfpServer 4 }

h3cAcfpServerCurContextType · current

h3cAcfpServerCurContextType 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.  h3cAcfpServerCurContextType is
        used to distinguish this difference, ACFP client may
        process distinctively."
    ::= { h3cAcfpServer 4 }

Meaning

Descriptions

1 unique

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

In some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. h3cAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.

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

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

Status in source: current.

Names: h3cAcfpServerCurContextType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cAcfpServerCurContextType",
    "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. h3cAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.\"",
    "::=",
    "{",
    "h3cAcfpServer",
    "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. h3cAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.1 h3cAcfpServerInfo00
1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.2 h3cAcfpServerMaxLifetime00
1.3.6.1.4.1.43.45.1.10.2.74.1.1.1.3 h3cAcfpServerPersistentRules00