subscribe iconSubscribe to this information
POWER6 information

Checking system configuration with Linux

You can check your system configuration with the Linux® operating system.

Verifying the availability of processor resources

To verify the availability of processor resources, perform the following steps:

  1. Run the following command:
    dsh -av "grep processor /proc/cpuinfo" | wc –l

    The total number of processors available in the cluster is shown.

  2. If the total number of processors available in the cluster is not shown, perform the following steps:
    1. Verify that all servers are powered on
    2. Fix any problems with the dsh command not being able to reach all logical partitions
    3. Determine which processors are having problems by running the following command:
      dsh -av "lsdev -C | grep proc | grep -v AVAILABLE"
    4. After you have identified the processors that are having problems, check the HMC controlling the server and complete any required service actions. If no serviceable events are found, try any isolation procedures for unconfigured processors that are found in the Start of service call.
    5. When all processors are available, continue with the procedure to verify memory.
  3. If processor de-configuration persists, contact your next level of hardware support.
  4. Verify processors are running at expected frequencies by using the following command:
    dsh –av “egrep ‘processor|clock' /proc/cpuinfo”

Verifying the availability of memory resources

To verify the availability of memory resources, perform the following steps:
  1. Run the following command:
    dsh –av “grep MemTotal /proc/meminfo”
  2. Select from the following options:
    • If the operating system has access to all memory resources, a command prompt is shown without any data. You can now exit this procedure.
    • If memory requires configuration, check the HMC controlling the server logical partition and perform any service actions as instructed
    Note: Before you perform a memory service action, make certain that the memory was not unconfigured for a specific reason.
  3. If no problems are found in the HMC, refer to the Start of service call and follow the instructions for diagnosing unconfigured memory.
  4. If the memory de-configuration persists, contact your next level of support.

Send feedback | Rate this page

Last updated: Tue, February 08, 2011