subscribe iconSubscribe to this information
POWER7 information

Verifying the system power control network

Check for system power control network (SPCN) errors and inactive enclosures, and fix machine type, model, and serial number (MTMS) problems.

  1. Choose one the following options to verify the SPCN:
    • If your system is not managed by a Hardware Management Console (HMC), continue with step 2.
    • If your system is managed by an HMC, continue with step 3.
  2. Choose one the following options:
    Important: Multiple options might apply to your configuration. Choose only the first option that applies.
    • If your system is running the Virtual I/O Server (VIOS) operating system, continue with step 4.
    • If your system is running the AIX® operating system, continue with step 5.
    • If your system is running the IBM® i operating system, continue with step 6.
    • If your system is running the Linux operating system, continue with step 7.
  3. Use the HMC to verify that no serviceable events include 10009xxx reference codes (where x is any character 0 - 9 or A - F) by completing the following steps:
    1. In the navigation area, select Service Management.
    2. In the content area, select Manage Serviceable Events.
    3. In the Manage Serviceable Events window, perform the following steps:
      1. Click Open for the Serviceable Event Status field.
      2. Select the machine type, model, and serial number (MTMS) of the server you are working with for the Reporting MTMS field.
      3. Click ALL for all other fields and click OK.
    4. Scan for any serviceable events that include 10009xxx reference codes, and perform one of the following actions:
      • If there are no serviceable events with 10009xxx reference codes, click Cancel twice to exit Manage Serviceable Events.
      • If there are serviceable events with 10009xxx reference codes, there might be problems with the SPCN loop. Perform problem analysis on the serviceable events to correct the problems before continuing. If you need assistance, contact your service provider.
    5. Go to step 8.
  4. Use the VIOS error log to verify that there are no 10009xxx errors (where x is any character 0 - 9 or A - F) by completing the following steps.
    1. Log in as the padmin user. If you need assistance, contact the system administrator.
    2. Type diagmenu -d sysplanar0 -E xx and press Enter, where xx is any number 1 - 60 that specifies a number of days. This command returns all 10009xxx error log entries for the most recent number of days specified. The suggested range is 30 days.
    3. Highlight the Problem Determination option in the DIAGNOSTIC MODE SELECTION display. Press Enter.
    4. Search the results that are displayed to identify problems with 10009xxx reference codes. You might need to scroll down in the display to see all of the results.
      Note: If the Problem Determination results contain serviceable events that have already been reported, the PREVIOUS DIAGNOSTICS RESULTS display is shown. Respond to the Do you want to review these previously reported errors? prompt by highlighting the YES response, and then press Enter.
    5. Based on the results of your search, perform one of the following options:
      • If there are no problems with 10009xxx reference codes, press Enter to return to the command line.
      • If there are problems with 10009xxx reference codes, there might be problems with the SPCN loop. Perform problem analysis on the problems to correct them before continuing. If you need assistance, contact your service provider.
    6. Go to step 8.
  5. Use the AIX error log to verify that there are no 10009xxx errors (where x is any character 0 - 9 or A - F) by completing the following steps.
    1. Log in as the root user, or use the CE login. If you need assistance, contact the system administrator.
    2. Type diag -d sysplanar0 -E xx and press Enter, where xx is any number 1 - 60 that specifies a number of days. This command returns all 10009xxx error log entries for the most recent number of days specified. The suggested range is 30 days.
    3. Highlight the Problem Determination option in the DIAGNOSTIC MODE SELECTION display. Press Enter.
    4. Search the results that are displayed to identify problems with 10009xxx reference codes. You might need to scroll down in the display to see all of the results.
      Note: If the Problem Determination results contain serviceable events that have already been reported, the PREVIOUS DIAGNOSTICS RESULTS display is shown. Respond to the Do you want to review these previously reported errors? prompt by highlighting the YES response, and then press Enter.
    5. Based on the results of your search, perform one of the following options:
      • If there are no problems with 10009xxx reference codes, press Enter to return to the command line.
      • If there are problems with 10009xxx reference codes, there might be problems with the SPCN loop. Perform problem analysis on the problems to correct them before continuing. If you need assistance, contact your service provider.
    6. Go to step 8.
  6. Use the IBM i service action event log to verify that there are no 10009xxx errors (where x is any character 0 - 9 or A - F) by completing the following steps.
    1. Sign on with at least service level authority.
    2. At the command line of the IBM i session, type strsst and press Enter.
    3. Type your service tools user ID and service tools password on the System Service Tools (SST) Sign On display. Press Enter. The service tools password is case-sensitive.
    4. Select Start a Service Tool > Hardware Service Manager > Work with Service Action Event Log.
    5. On the Select Timeframe display, change the From: Date and Time to the desired date and time range. The suggested range is 30 days.
    6. Search for serviceable events with 10009xxx reference codes, and perform one of the following actions:
      • If there are no serviceable events with 10009xxx reference codes, press F3 (Exit) to return to the Hardware Service Manager display.
      • If there are serviceable events with 10009xxx reference codes, there might be problems with the SPCN loop. Perform problem analysis on the serviceable events to correct the problems before continuing. If you need assistance, contact your service provider.
    7. Go to step 8.
  7. Use the Linux error log to verify that there are no 10009xxx errors (where x is any character 0 - 9 or A - F) by completing the following steps.
    1. Log in as the root user. If you need assistance, contact the system administrator.
    2. Type servicelog --query='refcode like "10009%" AND serviceable=1 AND closed=0' and press Enter
    3. Search the results that are displayed for problems with 10009xxx reference codes and statuses that are open. If there are problems with 10009xxx reference codes, there might be problems with the SPCN loop. Perform problem analysis on the problems to correct them before continuing. If you need assistance, contact your service provider.
      Note: You might need to scroll down in the display to see all of the results.
    4. Go to step 8.
  8. Verify that no inactive expansion units are in the SPCN by performing the following steps:
    1. Access the ASMI by using an authority level of administrator or authorized service provider. For details about using the ASMI, see Managing the Advanced System Management Interface.
    2. In the ASMI navigation area, expand System Configuration and click Configure I/O Enclosures.
    3. Scan for inactive expansion units by looking for rows that show Inactive in the Status column. If inactive expansion units exist, perform the following steps:
      Important: If you are here because the procedure to concurrently add expansion units instructed you to perform this task following steps to connect the power cables and power on the expansion units, do not perform the following steps to clear the inactive enclosures. Contact your service provider for assistance.
      1. Click Clear inactive enclosures.
      2. Wait for the completion indication, and repeat steps 8.b and 8.c. If inactive expansion units remain, do not continue. Contact your service provider for assistance.
  9. Check for temporary machine type, model, and serial number (MTMS) values assigned to the expansion units connected to the system by completing the following steps:
    1. Access the ASMI by using an authority level of administrator or authorized service provider. For details about using the ASMI, see Managing the Advanced System Management Interface.
    2. In the ASMI navigation area, expand System Configuration and click Configure I/O Enclosures.
    3. Review the display to determine if there are any expansion units that require correction. If you find one or more rows that contain a Location code value of UTMPx.xxx.xxxxxxx, where x is any character 0 - 9 or A - Z, continue to step 10 to provide the necessary corrections. If there are no rows with Location codes that require correction, continue to step 11.
  10. For each expansion unit found in your review, complete the following steps to correct the machine type, model, and serial number (MTMS) values. After you have completed the corrections required for all expansion units identified in your review, continue to step 11.
    Important: If your expansion unit contains one or more I/O slots that are owned by active partitions running the VIOS, AIX, or Linux operating system, these partitions will not automatically recognize the MTMS value corrections that you are about to make. For these partitions to recognize the new values, you will be required to take additional action that is potentially disruptive. Before proceeding with this step, review step 10.e to determine whether it is possible to take the required actions at this time. If it is not, continue to step 11 without performing this step.
    1. Access the ASMI by using an authority level of administrator or authorized service provider. For details about using the ASMI, see Managing the Advanced System Management Interface.
    2. In the ASMI navigation area, expand System Configuration and click Configure I/O Enclosures.
    3. Select the row associated with the expansion unit to be corrected and click Change settings. Follow these steps to update the information:
      1. Enter the correct type and model in the Type-Model field.
      2. Enter the correct serial number in the Serial number field.
      3. Do not update the Power Control Network Identifier field.
      4. Click Save settings.
    4. In the ASMI navigation area, expand System Configuration and click Configure I/O Enclosures again. Verify that the values you entered are displayed in the information for the expansion unit that you selected in step 10.c. If the values that you entered are not displayed, wait for a few minutes and repeat this step. If the problem persists, contact your service provider for assistance.
      Important: Do not click Back for the purpose of verifying your values.
    5. If the expansion unit that you corrected contains one or more I/O slots that are owned by active partitions running the AIX, VIOS, or Linux operating system, the corrections will not be recognized by those partitions until you take one of the following actions:
      • Power off and power on the expansion unit. To perform this task, select one of the following options:
        • If the system is managed by an HMC, click Serviceability > Hardware > Power On/Off Unit to perform this task.
        • If the system is not managed by an HMC, you must choose one of the other options in this list.
      • Power off and power on active partitions that own I/O slots in the expansion unit that you corrected and that are running the AIX, VIOS, or Linux operating system.
      • Dynamically remove I/O slots in the expansion unit that you corrected from active partitions that are running the AIX, VIOS, or Linux operating system, and then dynamically add the slots back to those partitions. To perform this task, select one of the following options:
        • If the system is managed by an HMC, click Dynamic Logical Partitioning > Physical Adapters to perform this task.
        • If the system is not managed by an HMC, you must choose one of the other options in this list.
      • Power off and power on the server.
  11. Return to the procedure that sent you here.
Parent topic: Adding I/O expansion units

Send feedback Rate this page

Last updated: Tue, September 30, 2014