All MIBs › CRI-SERVER-MIB › confMemAddrMap
confMemAddrMap
Module: CRI-SERVER-MIB
OID (symbolic): CRI-SERVER-MIB::confMemAddrMap
OID (numeric): 1.3.6.1.4.1.34.2.1.2.25
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: Starfire supports Shared Memory Domains. This requires the memory boards in the machine to have unique address. Because of this global requirement, Starfire hpost assigns the memory addresses, as well as for attaching boards. DR detach operation also assigns memory addresses. The method used to ensure unique addresses is to assign addresses based on slot number. To allow for 2 way inter-board interleaving, these addresses are slot number*8G.
The map is a 16-byte array representing the 16 slots. The lower 7 bits of each byte represents the unique address assign to that slot. The high bit is significant on a write-operation only, when set the corresponding slot of the map will be changed with the address represented by the lower 7 bits. On a read operation the returning data represents the current memory map and the high bit of each byte is always 0. On a write operation the byte with the high bit set will be modified.
The SNMP agent will perform a consistency check before committing a write operation. Consistency check simply makes sure no two slots will contain the same address if the write is performed. If consistency check fails, the write operation will return an error.
What is confMemAddrMap?
This read-write OCTET STRING of 16 bytes holds the memory address map for the platform's Shared Memory Domains feature, under which Starfire's host POST process assigns each memory board a unique address based on its slot number multiplied by 8G to support two-way inter-board interleaving, with DR detach operations also updating these assignments. An administrator relies on the platform's own POST and DR logic to maintain this map correctly rather than editing it directly, but can read it to understand current memory address assignments. For example, after a dynamic reconfiguration detach operation removes a board, this map reflects the address space being reassigned as a result.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.34.2.1.2.25 snmpwalk -v2c -c public <target> CRI-SERVER-MIB::confMemAddrMap
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.34.2.1.2.25.1 snmpget -v2c -c public <target> CRI-SERVER-MIB::confMemAddrMap.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.34.2.1.2.25.1 s <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::confMemAddrMap 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.2 | conf | CRI-SERVER-MIB |
| 1.3.6.1.4.1.34.2.1.2.25 | confMemAddrMap | CRI-SERVER-MIB |