CRI-SERVER-MIB :: signatureBlockChange

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCRI-SERVER-MIBsignatureBlockChange

signatureBlockChange

Module: CRI-SERVER-MIB

OID (symbolic): CRI-SERVER-MIB::signatureBlockChange

OID (numeric): 1.3.6.1.4.1.34.0.65

Node type: NOTIFICATION-TYPE

Description: This trap indicates that the signature block has changed. All variables will be provided with this trap.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' CRI-SERVER-MIB::signatureBlockChange
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.34.0.65

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:62838->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (69267830) 8 days, 0:24:38.30
  SNMPv2-MIB::snmpTrapOID.0 = OID: CRI-SERVER-MIB::signatureBlockChange

SNMPv3 example:

snmptrap -v3 -l authPriv -u snmpv3user -a SHA -A "AuthPass1" -x AES -X "PrivPass1" <manager> '' CRI-SERVER-MIB::signatureBlockChange

Start monitoring CRI server platform (vendor unclear) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CRI-SERVER-MIB::signatureBlockChange OID value, configure state conditions and alerts, and monitor any CRI server platform (vendor unclear) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.34sunCRI-SERVER-MIB
1.3.6.1.4.1.34.0.65signatureBlockChangeCRI-SERVER-MIB