Skip Navigation Links
Exit Print View
| SPARC T4-1 Server HTML Document Collection

Search Scope:

- This Document
- Entire Library

##### DIMM Configuration Errors—System Console

When the server boots, system firmware checks the memory configuration against the rules described in DIMM Population Rules. If a memory configuration error is detected, a general error message is displayed:

    Please refer to the service documentation for supported memory configurations.

In some cases, the server boots in a degraded state, and a message such as the following is displayed:

    NOTICE:  /SYS/MB/CMP0/CORE0/P0 is degraded

In other cases, the configuration error is fatal, and a message such as the following is displayed:

    Fatal configuration error - forcing power-down

In addition, one or more rule-specific messages is displayed, indicating the type of configuration error detected.

The following table identifies and explains the various DIMM configuration error messages.

Note - The messages described in this table apply to SPARC T4-1 servers. The DIMM configuration requirements for other servers in the SPARC T4 series are different in some details, so some of their configuration error messages will also be different.

DIMM Configuration Error Messages | Notes
--- | ---
`Fatal configuration error - forcing power-down.` | Ensure that DIMMs are installed in a supported configuration. See DIMM Population Rules. Ensure that DIMMs are identical (identical capacity, identical DIMM classification). See DIMM Rank Classification Labels See Increase System Memory With Additional DIMMs.
`Not all MCUs enabled.` `Unsupported Config.` | Ensure that DIMMs are installed in a supported configuration. See DIMM Population Rules. See DIMM Rank Classification Labels.
`Invalid DIMM population.` `No DIMM is present in MCU` n`/BOB` n | Install a DIMM with the appropriate characteristics in the slot specified in the message.
`Not all DIMMs have the same SDRAM capacity.` | All DIMM components must have the same storage capacity—all 4 GByte, all 8 GByte, all 16 GByte, or all 32 GByte. Replace any DIMMs that do not match the intended capacity. For more information, see DIMM Rank Classification Labels.
`Not all DIMMs have the same device width.` | All DIMM components must have the same device width. Replace any DIMMs that do not match the desired width. See DIMM Rank Classification Labels
`Not all DIMMs have the same number of ranks.` | All DIMM components must have the same number of ranks. The supported rank arrangements are: 2 ranks—4 GByte, 8 GByte, 16 GByte DIMMs 4 ranks—16 GByte, 32 GByte DIMMs Replace any DIMMs that do not match the intended rank number. For more information, see DIMM Rank Classification Labels.
`Invalid DIMM population. DIMMs in the same position must be all present or absent.` | Memory configurations must be populated in sets of 4, 8, or 16 DIMM components as as described in DIMM Population Rules. Either add DIMM components to fill a partially populated set, or remove DIMM components to empty a partial set. Note - The DIMM slots labeled set 1 in the figure must always be fully populated.
`Invalid DIMM population. T4-1 only supports 1/4, 1/2 or full memory configs.` | Add or remove DIMM components to achieve one of the supported memory configurations. See DIMM Population Rules.
`DIMM population across nodes is different.` | This message does not apply to SPARC T4-1 servers.
`DRAM capacity of DIMMs is different across nodes.` | This message does not apply to SPARC T4-1 servers.
`Device width of DIMM is different across nodes.` | This message does not apply to SPARC T4-1 servers.
`Number of ranks of DIMM is different across nodes.` | This message does not apply to SPARC T4-1 servers.

##### Related Information

- Memory Fault Handling Overview

- DIMM Population Rules

- Locate a Faulty DIMM (DIMM Fault Remind Button)

- Locate a Faulty DIMM (`show faulty` Command)

- DIMM Rank Classification Labels

- DIMM Configuration Errors—`show faulty` Command Output

- DIMM Configuration Errors—`fmadm` `faulty` Output

Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |