All MIBs › CRI-SERVER-MIB › domainInterruptVector
domainInterruptVector
Module: CRI-SERVER-MIB
OID (symbolic): CRI-SERVER-MIB::domainInterruptVector
OID (numeric): 1.3.6.1.4.1.34.2.1.3.1.8
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Interrupts to the host processor via JTAG requires 2 pieces of information: the UPA ID of the target CPU and the interrupt number assigned to the bootbus interrupt by the host. The target UPA ID identifies the particular bootbus and the proc ID (0 or 1) to be written into the bootbus interrupt register. The interrupt number is the value to be written into word 0 of the mondo vector of the target CPU. This number is computed by the host kernel.
This object is a 13 bit value and is treated as an integer (32 bit) for easy manipulation.
What is domainInterruptVector?
This read-write INTEGER encodes the interrupt information needed to signal the domain's host processor over JTAG, combining the target CPU's UPA ID (identifying its bootbus and processor 0-or-1 position) with an interrupt number computed by the host kernel for the target CPU's mondo vector. An administrator relies on the platform's own kernel and SSP logic to set this correctly during low-level interrupt delivery rather than crafting it by hand. For example, this value changes as the SSP delivers a specific interrupt to a specific bootbus processor identified by its UPA ID.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.34.2.1.3.1.8 snmpwalk -v2c -c public <target> CRI-SERVER-MIB::domainInterruptVector
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.34.2.1.3.1.8.1 snmpget -v2c -c public <target> CRI-SERVER-MIB::domainInterruptVector.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.34.2.1.3.1.8.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::domainInterruptVector 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.3 | domainTable | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.3.1 | domainEntry | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.3.1.8 | domainInterruptVector | CRI-SERVER-MIB |