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.
Parsed from file e10k_mib.txt
Company: None
Module: CRI-SERVER-MIB
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.
Parsed from file CRI-SERVER-MIB.mib
Module: CRI-SERVER-MIB
Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.
confMemAddrMap OBJECT-TYPE SYNTAX OCTET STRING(SIZE(16)) ACCESS read-write STATUS mandatory 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. " ::= { conf 25 }
confMemAddrMap OBJECT-TYPE SYNTAX OCTET STRING(SIZE(16)) ACCESS read-write STATUS mandatory 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. " ::= { conf 25 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.34.2.1.2.25.0 | confMemAddrMap | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.34.2.1.2.1 | confNumDomain | 1 | 1 | The number of domain in the platform. Domains are created with command, domain_create. Domains are removed with command, domain_re… |
| 1.3.6.1.4.1.34.2.1.2.2 | confNumSysBrd | 1 | 1 | The number of system board in the platform. The max # system board in a Starfire system is 16. |
| 1.3.6.1.4.1.34.2.1.2.3 | confNumProc | 1 | 1 | The number of processor in a system board. The max # processors in a Starfire system is 64. |
| 1.3.6.1.4.1.34.2.1.2.4 | confNumConBrd | 1 | 1 | The number of control board in the system. The max # control board in a Starfire system is 2. |
| 1.3.6.1.4.1.34.2.1.2.5 | confNumCenterplane | 1 | 1 | The number of centerplane in the system. The max # centerplane half board in a Starfire system is 2. |
| 1.3.6.1.4.1.34.2.1.2.6 | confNumSuppBrd | 1 | 1 | The number of centerplane support board in the system. The max # of centerplane support board in a Starfire system is 2. |
| 1.3.6.1.4.1.34.2.1.2.7 | confNumIoCab | 1 | 1 | The number of IO cabinet connected to the system. The max # of IO cabinets that can be connected to a Starfire system is 3. |
| 1.3.6.1.4.1.34.2.1.2.8 | confNumFanTray | 1 | 1 | The number of fan tray in the system. The max # of fan trays that can be installed in a Starfire system is 16. |
| 1.3.6.1.4.1.34.2.1.2.9 | confNumBulkPower | 1 | 1 | The number of bulk power supply in the system. The max # of bulk power supply in a Starfire system is 8. |
| 1.3.6.1.4.1.34.2.1.2.10 | confNumSysBrdPower | 1 | 1 | The number of system board power supply in the system. The max # of system board power supply for a Starfire system is 16. In Star… |
| 1.3.6.1.4.1.34.2.1.2.11 | confSysBrdList | 1 | 1 | A string identifying the system boards that are present in the system. The format of the string is: xx-xx-.. where xx is the syste… |
| 1.3.6.1.4.1.34.2.1.2.12 | confProcList | 1 | 1 | A string identifying the processors that are present in the system. The format of the string is: bb.pp-bb.pp-... where bb is the s… |
| 1.3.6.1.4.1.34.2.1.2.13 | confConBrdList | 1 | 1 | A string identifying the control boards that are present in the system. The format of the string is: xx-xx-.. where xx is the cont… |
| 1.3.6.1.4.1.34.2.1.2.14 | confCenterplaneList | 1 | 1 | A string identifying the centerplanes that are present in the system. The format of the string is: xx-xx-.. where xx is the center… |
| 1.3.6.1.4.1.34.2.1.2.15 | confSuppBrdList | 1 | 1 | A string identifying the centerplane support boards that are present in the system. The format of the string is: xx-xx-... where … |
| 1.3.6.1.4.1.34.2.1.2.16 | confIoCabList | 1 | 1 | A string identifying the IO cabinets that are connected to the system. The format of the string is: xx-xx-... where xx is the I/O… |
| 1.3.6.1.4.1.34.2.1.2.17 | confFanTrayList | 1 | 1 | A string identifying the fan trays that are present in the system. the format of the string is: xx-xx-... where xx is the fan tray… |
| 1.3.6.1.4.1.34.2.1.2.18 | confBulkPowerList | 1 | 1 | A string identifying the bulk power supplies that are present in the system. The format of the string is: x-x where x is the bulk … |
| 1.3.6.1.4.1.34.2.1.2.19 | confSysBrdPowerList | 1 | 1 | A string identifying the system board power supplies that are present in the system. The format of the string: xx-xx-... where xx … |
| 1.3.6.1.4.1.34.2.1.2.20 | confMaxProcPerSysBrd | 1 | 1 | The maximum number of processor in a system board. There is a max of 4 processors in a Starfire system board. |
| 1.3.6.1.4.1.34.2.1.2.21 | confMaxFanPerTray | 1 | 1 | The maximum number of fan in a fan tray. There is a max of 2 fan in a Starfire fan tray. |
| 1.3.6.1.4.1.34.2.1.2.22 | confMaxLEDPerFanTray | 1 | 1 | The maximum number of LED in a fan tray. There is a max of 2 LEDs in a Starfire fan tray. |
| 1.3.6.1.4.1.34.2.1.2.23 | confMaxLEDPerBulkPower | 1 | 1 | The maximum number of LED in a bulk power supply. There is a max of 2 LEDs in a Starfire bulk power supply. |
| 1.3.6.1.4.1.34.2.1.2.24 | confMaxLEDPerSysBrd | 1 | 1 | The maximum number of LED in a system board. |