All MIBs › CRI-SERVER-MIB › procCommGenObpMboxCmd
procCommGenObpMboxCmd
Module: CRI-SERVER-MIB
OID (symbolic): CRI-SERVER-MIB::procCommGenObpMboxCmd
OID (numeric): 1.3.6.1.4.1.34.2.1.6.1.13
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The command of Obp-to-SSP mailbox.
#define SSPC_MULTIPROC 0x0b0b0001 /* Request to release slave CPUs */ #define SSPC_GETTOD 0x0b0b0002 /* Get Unix time of day from SSP */ #define SSPC_GETEEPROM 0x0b0b0003 /* Get EEPROM image from SSP */ #define SSPC_PUTEEPROM 0x0b0b0004 /* Put EEPROM image to SSP */ #define SSPC_UPDREBOOT 0x0b0b0005 /* Invalidate Reboot-info in eeprom */ #define SSPC_MOVECPU0 0x0b0b0006 /* Move Cpu0 Command */ #define SSPC_GETAPDATABASELOC 0x0b0b0007 /* Get AP database location */ #define SSPC_SAVEBOOTPATH 0x0b0b0008 /* Store boot path info */
What is procCommGenObpMboxCmd?
This read-write INTEGER holds the command posted in the Obp-to-SSP mailbox, drawn from a defined set including release-slave-cpu, time-of-day, get-eeprom-image, put-eeprom-image, invalidate-reboot-info, and move-cpu0, among others truncated from the source. An administrator relies on OBP firmware to post these commands as it coordinates low-level boot and configuration actions with the SSP. For example, a get-eeprom-image command posted here would be OBP requesting the SSP retrieve the EEPROM image data for that processor.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.34.2.1.6.1.13 snmpwalk -v2c -c public <target> CRI-SERVER-MIB::procCommGenObpMboxCmd
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.34.2.1.6.1.13.1 snmpget -v2c -c public <target> CRI-SERVER-MIB::procCommGenObpMboxCmd.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.34.2.1.6.1.13.1 i <value>
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::procCommGenObpMboxCmd 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.34 | sun | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2 | products | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1 | general | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.6 | procCommGenTable | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.6.1 | procCommGenEntry | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.6.1.13 | procCommGenObpMboxCmd | CRI-SERVER-MIB |