---
oid: "1.3.6.1.4.1.11.2.14.11.1.4.10.1.1.1"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 11 nm(2) icf(14) hpicfObjects(11) hpicfCommon(1) hpicfBasic(4) hpicfBasicTraps(10) hpicfFixedTrapTable(1) hpicfFixedTrapEntry(1) hpicfFixedTrapID(1)}"
description: "hpicfFixedTrapID OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2022-10-03"
---

## OID : `1.3.6.1.4.1.11.2.14.11.1.4.10.1.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 11 nm(2) icf(14) hpicfObjects(11) hpicfCommon(1) hpicfBasic(4) hpicfBasicTraps(10) hpicfFixedTrapTable(1) hpicfFixedTrapEntry(1) hpicfFixedTrapID(1)}
```

### Description

```asn1
hpicfFixedTrapID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The object identifier of the notification this entry
provides mapping information for.
For notifications that are defined using the SNMPv2
NOTIFICATION-TYPE macro, the OID value assigned by
the macro is used directly as the hpicfFixedTrapID.
For traps defined using the SNMpv1 TRAP-TYPE macro,
the value of hpicfFixedTrapID is formed by adding
two sub IDs to the trap enterprise. The first added
sub ID is 0, and the second is the specific trap
value assigned by the macro to the trap. Note: this
is the method specified in RFC 1908, 'Coexistence
between Version 1 and Version 2 of the
Internet-standard Network Management Framework' for
converting the enterprise and specific-trap fields
of a received Trap-PDU into a value of snmpTrapOID
for use in building an SNMPv2-Trap-PDU in a proxy
agent."
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
