SPARC T4-1 – Version All Versions and later
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community.
This document describes one possible reason why CPU’s (cores/threads) and/or Memory, may not be displayed after booting the Solaris Operating System on sun4v platforms.
This document provides steps to recover these CPU’s or Memory, if needed.
The following Solaris commands do not report the actual physical CPU’s (cores/threads) or Memory DIMMs installed within the system:
This gives the impression that the system has less CPU’s or Memory than it should have.
Here are a couple of examples taken from a Sun Fire T2000. As you will see it only shows 4 CPU’s and 1024MB Memory:
However, on the Service Processor (SP) via the Alom account, the following commands will show all the CPU’s and Memory physically installed within the system:
-> show components
A possible common cause for this condition, is the presence of a previously installed LDom (Logical Domain) configuration that has not been cleared/removed completely.
For details on LDoms setup, please refer to the Logical Domains (LDoms) Administration Guides, available at Oracle VM for SPARC Documentation.
For details on the hardware configurations of the relevant sun4v platforms, please refer to the system specific documentation .
Steps to Follow
Steps to Resetting LDoms to factory-default
[1.] Confirm that if there are existing LDoms configurations that are actually in use.
[1-A.] Verify if the LDoms Manager is installed on the system.
Perform the following command to check if the LDoms Manager package SUNWldm is installed on the system.
# pkginfo |grep SUNWldm application SUNWldm Logical Domains Manager
The binaries for the package is located at /opt/SUNWldm if the package is installed.
If the SUNWldm package does not exist on the system, it means that the LDoms Manager is not installed.
If LDoms Manager is not installed, skip Step [1-B.] and proceed to Step [2.]
[1-B.] Verify that there is no other configured or active Guest Domains on the system.
If LDoms Manager does exist, some active Guest Domains are possibly still in-use.
# /opt/SUNWldm/bin/ldm list
Below is an example showing that there are 2 Guest Domains configured, and bound:
# /opt/SUNWldm/bin/ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv SP 4 1G 0.3% 22h 59m ldom2 bound ----- 5000 4 1G ldom3 bound ----- 5001 4 1G
Below is an example showing 2 active Guest Domains, with the Operating System running:
# /opt/SUNWldm/bin/ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv SP 4 1G 3.6% 22h 36m ldom2 active -n--- 5000 4 1G 24% 11s ldom3 active -n--- 5001 4 1G 32% 11s
Below is an example showing if there are no Guest Domains configured, only the Primary Domain entry is shown:
# /opt/SUNWldm/bin/ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv SP 4 1G 0.3% 22h 59m
DO NOT PROCEED FURTHER If you are unsure if the Domains configured are still in use or not.
[2.] Reseting the LDoms configuration back to default.
By now, after carrying out Step [1.] above, we have confirmation that if LDoms configurations on the system are no longer needed, we are ready to reset the system configuration back to factory default settings.
The LDoms configuration for factory default is named as factory-default.
There are 2 possible ways to reset the configurations of the system.
If SUNWldm package is installed and verified, we can reset the system through LDoms Manager using the ldm(1M) command.
However, if the system has been freshly (re)installed with Solaris without LDoms Manager installed, the configurations can be reset from the Service Processor.
[2-A.] Resetting through existing LDoms Manager installed on the system.
List out the current LDom configuration, as well as other available configurations saved on the system.
# /opt/SUNWldm/bin/ldm list-spconfig factory-default prod [current]
To set to factory-default, use the following command:
# /opt/SUNWldm/bin/ldm set-spconfig factory-default
Once set, confirm the next power on configuration used will be factory-default, by running the following command
# /opt/SUNWldm/bin/ldm list-spconfig factory-default [next] prod [current]
NB – MANDATORY STEP:
On booting up, the system would be using the factory-default configuration, and all the hardware components on the system should now be visible.
ldm(1M) will show the current effective configuration as factory-default.
# /opt/SUNWldm/bin/ldm list-spconfig factory-default [current] prod
After the configuration has been reset to factory-default, proceed to remove the other non active LDoms configurations on the system using the remove-spconfig subcommand for ldm(1M).
[2-B.] Reseting through the Service Processor.
The LDoms configuration can be reset through the SP before booting the OS on the system.
For system with the ALOM configured on the Service Processor, use the following syntax:
sc> bootmode config="factory-default" sc> poweroff
Wait for system to power off.
sc> poweron -c OR sc> poweron sc> console -f
For system with ILOM, use the following syntax:
-> set /HOST/bootmode config="factory-default" -> stop /SYS Are you sure you want to stop /SYS (y/n)? y
Wait for machine to power off.
-> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS -> start /SP/console
Once the machine is powered on, it should have all configurations reset to the default with all the hardware components visible.
Please refer to the following documentations for further details on ALOM and ILOM commands:
– Advanced Lights Out Management (ALOM) CMT vX.X Guide
Data Collection for further troubleshooting
If after the above steps of resetting the system back to factory-default, still shows some CPU’s and/or memory not visible, please find out the number of CPU cores the system show be seeing, before contacting Oracle Support with the following information:
– The latest explorer output using the latest version of explorer script.
Please refer to doc 1312847.1 Oracle Explorer Data Collectorfor the latest Explorer Script.