CRI-SERVER-MIB :: cbeConnected

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCRI-SERVER-MIBcbeConnected

cbeConnected

Module: CRI-SERVER-MIB

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

OID (numeric): 1.3.6.1.4.1.34.0.24

Node type: NOTIFICATION-TYPE

Description: This trap indicates that the control board server (cbs) is connected to the control board executive (cbe) and is ready for control board operation. All variables are mandatory for 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::cbeConnected
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.34.0.24

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]:49380->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (266194660) 30 days, 19:25:46.60
  SNMPv2-MIB::snmpTrapOID.0 = OID: CRI-SERVER-MIB::cbeConnected

SNMPv3 example:

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

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::cbeConnected 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.24cbeConnectedCRI-SERVER-MIB