All MIBs › CRI-SERVER-MIB › domainProcConfig
domainProcConfig
Module: CRI-SERVER-MIB
OID (symbolic): CRI-SERVER-MIB::domainProcConfig
OID (numeric): 1.3.6.1.4.1.34.2.1.3.1.10
Node type: OBJECT-TYPE
Type: DisplayString
Access: read-only
Description: POST scans both blacklist and redlist files to determine which components should not be used to configure a domain. The content of the blacklist and redlist files along with the final result of a POST run is kept in a data structure, P2OBP, in the boot processor's BBSRAM. The SNMP agent is responsible to retrieve the data structure and extracts the necessary information to produce the result.
domainProcConfig describes the processors configuration. Its format is a DisplayString (character string) in the format of xx.yyS-xx.yyS-... where xx is a system board number [0..15], yy is a processor number within a system board [0..3], S is a single character status code, and (dash) '-' is for delimiting multiple components. Valid status code include: F - Tested and Failed M - Missing R - Redlisted B - Blacklisted c - Crunched U - Good but not configured G - Good A - Architecturally missing
What is domainProcConfig?
This read-only DisplayString describes the configuration status of processors in this domain, drawing on POST's blacklist and redlist scans of which components should be excluded, with results stored in the P2OBP data structure in the boot processor's BBSRAM and retrieved by the SNMP agent. An administrator reads this to see which processors POST decided to configure into or exclude from the domain and why. For example, a processor missing from this configured list that POST's blacklist flagged would explain why that CPU is not participating in the domain despite being physically present.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.34.2.1.3.1.10 snmpwalk -v2c -c public <target> CRI-SERVER-MIB::domainProcConfig
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.34.2.1.3.1.10.1 snmpget -v2c -c public <target> CRI-SERVER-MIB::domainProcConfig.1
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::domainProcConfig 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.10 | domainProcConfig | CRI-SERVER-MIB |