CLARENT-MIB :: dbClerkStarted

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLARENT-MIBdbClerkStarted

dbClerkStarted

Module: CLARENT-MIB

OID (symbolic): CLARENT-MIB::dbClerkStarted

OID (numeric): 1.3.6.1.4.1.2858.4.0.9945

Node type: NOTIFICATION-TYPE

Description: A new database clerk was started. The value of trapNumber represents the total number of clerks running.

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> '' CLARENT-MIB::dbClerkStarted
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2858.4.0.9945

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]:53696->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (27116480) 3 days, 3:19:24.80
  SNMPv2-MIB::snmpTrapOID.0 = OID: CLARENT-MIB::dbClerkStarted

SNMPv3 example:

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

Start monitoring Clarent VoIP gateway (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CLARENT-MIB::dbClerkStarted OID value, configure state conditions and alerts, and monitor any Clarent VoIP gateway (legacy) 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.2858clarentCLARENT-MIB
1.3.6.1.4.1.2858.4clarent_trapsCLARENT-MIB
1.3.6.1.4.1.2858.4.0.9945dbClerkStartedCLARENT-MIB