NOKIA-COMMON-ALARM-REPORTING-MIB :: alResendTrapId

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NOKIA-COMMON-ALARM-REPORTING-MIB › alResendTrapId

alResendTrapId

Module: NOKIA-COMMON-ALARM-REPORTING-MIB

OID (symbolic): NOKIA-COMMON-ALARM-REPORTING-MIB::alResendTrapId

OID (numeric): 1.3.6.1.4.1.94.1.16.1.3.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This variable contains value of the caTrapId of the last successfully resent alarm trap. Initially this variable has value 0. When NMS sets this variable, the NE shall resend the alarm trap whose caTrapId equals to the value provided by NMS, if the corresponding alarm trap is still available in the internal alarm log in NE (e.g. the corresponding log entry has not yet been lost in the alarm log because of wrapping). If this operation fails, the value of this variable is not changed to the value provided by NMS. Note that in addition to this variable, NMS has to set the values of alResendTrapDestinationAddr and alResendTrapDestinationPort to the correct value so that the traps shall be sent to the correct destination. It is preferred that the NMS sets these three variables in the single SNMP SET message in order this operation to be atomic. In these cases the NE must guarantee that the alResendTrapDestinationAddr and alResendTrapDestinationPort are logically set to given values before the value of alResendTrapId is set (This is because at the moment of setting the value of alResendTrapId to the value given by NMS the trap shall be issued to the destination address/port found in variables alResendTrapDestinationAddr and alResendTrapDestinationPort). The value of community string shall be known by NE based on the contents of trap destination MIB.

What is alResendTrapId?

Setting this to a caTrapId value tells the NE to resend that specific historical alarm trap to the address and port configured in alResendTrapDestinationAddr/Port, provided the entry hasn't already been wrapped out of the log; on success this variable then reflects the last successfully resent trap ID. An admin uses this to recover an alarm notification an NMS missed, ideally setting all three resend variables in a single SNMP SET for atomicity.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.94.1.16.1.3.1.6
snmpwalk -v2c -c public <target> NOKIA-COMMON-ALARM-REPORTING-MIB::alResendTrapId

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.94.1.16.1.3.1.6.1
snmpget -v2c -c public <target> NOKIA-COMMON-ALARM-REPORTING-MIB::alResendTrapId.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.94.1.16.1.3.1.6.1 i <value>

Start monitoring Nokia network element (router/transport/access platform, common alarm reporting) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NOKIA-COMMON-ALARM-REPORTING-MIB::alResendTrapId OID value, configure state conditions and alerts, and monitor any Nokia network element (router/transport/access platform, common alarm reporting) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.94nokiaNOKIA-AZC-REGISTRATION-MIB
1.3.6.1.4.1.94.1nokiaProductsNOKIA-AZC-REGISTRATION-MIB
Numeric OIDNameModule
1.3.6.1.4.1.94.1.16ntcCommonNOKIA-COMMON-ALARM-REPORTING-MIB
1.3.6.1.4.1.94.1.16.1ntcCommonAlarmNOKIA-COMMON-ALARM-REPORTING-MIB
1.3.6.1.4.1.94.1.16.1.3alNOKIA-COMMON-ALARM-REPORTING-MIB
1.3.6.1.4.1.94.1.16.1.3.1alVarsNOKIA-COMMON-ALARM-REPORTING-MIB
1.3.6.1.4.1.94.1.16.1.3.1.6alResendTrapIdNOKIA-COMMON-ALARM-REPORTING-MIB