Learn about adding an input/output (I/O) expansion unit
to the system with the system powered on.
Important: To use the following procedure to add
I/O expansion units to the system, your configuration must meet one
of the following requirements:
- Your system is managed by an IBM® Hardware Management Console (HMC).
- Your system is not managed by an HMC, but has only one partition,
and that partition is running the IBM i operating system.
If your configuration does not meet any of these
requirements, you must add your I/O expansion unit by completing the
procedure at
Adding an I/O expansion unit with the system powered off.
Note: Steps in this topic require
you to have connector information for the hardware in your configuration.
For details about expansion unit or system connector locations, see
Connector
locations.
To add an I/O expansion unit to the system with the system
powered on, complete the following steps:
- Verify the existing 12X configuration
by choosing one of the following options.
Important: Any
problems that you discover with the 12X loops in this step must be
corrected before you continue with the procedure.
- If your system is managed by an HMC, see Verifying the 12X loops with an HMC
Tip: This task includes a step to verify the status of the links
in the 12X loops. When you are instructed to use the View
Hardware Topology task, you can click Save to
save the current hardware topology. Use this action to compare the
topology that existed before the expansion unit was added with the
topology that was created by adding the expansion unit.
- If your system is not managed by an HMC, see Verifying the 12X loops without an HMC.
- Verify the system power control network
(SPCN). For instructions, see Verifying the system power control network.
Important: Any problems that you discover with the SPCN in this
step must be corrected before you continue with the procedure.
- Set the SPCN Firmware Update Policy to
prevent firmware updates over the serial SPCN interface by completing
the following steps.
Note: The SPCN Firmware Update Policy controls
when and how SPCN firmware on expansion units is updated. The default
setting for the SPCN Firmware Update Policy is Enabled. This setting
allows for firmware updates to be completed over the 12X interface
whenever an update is required and does not allow updates over the
slower serial SPCN interface.
- Access the Advanced System Management Interface (ASMI) by using
an authority level of administrator or authorized service provider.
For instructions, see Managing the Advanced System
Management Interface.
- In the ASMI navigation area, expand System Configuration and
select Configure I/O Enclosures.
- If the SPCN Firmware Update Policy shows Expanded,
record the current setting so that you can restore it later, and then,
change the setting to Enabled.
- If the SPCN Firmware Update Policy shows Enabled or Disabled,
continue without changing the setting.
- Check to see whether an SPCN firmware update is in progress and
choose one of the following options.
Note: An SPCN firmware update
is in progress if the Power Control
Network Firmware Update Status column shows In Progress and
displays the percentage that is completed.
- If an SPCN firmware update is in progress, continue with step 4.
- If an SPCN firmware update is not in progress, continue with step 5.
- Check the Power Control Network Firmware Update Status
column to determine the type of update that is in progress, and then,
choose one of the following options:
- If the SPCN firmware update is a High Speed Link (HSL) update,
wait for the update to complete before you continue. An HSL update
completes quickly. To determine when the update is complete, select Configure
I/O Enclosures every 15 – 30 seconds until Not
Required is displayed in the Power Control Network Firmware Update Status
column. Do not click Back or Refresh on
the browser to monitor the status.
- If the SPCN firmware update is a serial update, choose one of
the following options:
- If the system has a rear cover, remove
or open it.
- Record the current date and time for use later
in the procedure when you check for serviceable events.
- Connect the expansion unit with 12X cables.
For instructions, see Connecting expansion units with 12X cables.
Note: When
you connect an expansion unit in an existing 12X loop with the system
powered on, serviceable events and informational logs might be generated
when you disconnect and reconnect cables. This behavior is normal
and is covered later in the procedure.
- Connect the expansion unit with SPCN
cables. For instructions, see Connecting expansion units with SPCN cables.
Note: When
you connect an expansion unit in an existing SPCN loop with the system
powered on, serviceable events and informational logs might be generated
when you disconnect and reconnect cables. This behavior is normal
and is covered later in the procedure.
- Connect the power cables for the expansion
unit that you are installing. The expansion unit powers on automatically
when the power cables are connected.
Important: Ensure
that you plug the power cable into the power source before you connect
it into the power supply of the expansion unit.
- Wait for the green power indicator
on the control panel of the expansion unit to light solid. This action
might take 1 - 10 minutes. During this time, a yellow attention indicator
might be lit on the control panel of the expansion unit. After the
green power indicator is lit on the control panel, wait 10 extra minutes
for hardware initialization to complete before you proceed with the
installation.
- Verify the SPCN configuration by completing
the following steps.
- Read and understand the following information
about reference codes that might be generated when an expansion unit
is added while the system is powered on to firmware standby state.
Note: When
an expansion unit is added while the system is powered on, it is normal
for error logs and event logs to be created with the following SPCN-related
reference codes. The number and combination of these logs is dependent
on the configuration.
Logs with the following reference codes
can be ignored during this verification step if their time stamps
indicate that they occurred during the add procedure and the resources
that they refer to were involved in the procedure.
- 10009133: The 12X loop was disrupted. This reference code appears
in an informational log.
- 10009135: The SPCN loop was opened. This reference code might
appear in a serviceable event or an informational log.
- 10009136: An SPCN firmware update was stopped. This reference
code appears in an informational log.
- 10009137: The 12X loop was disrupted. This reference code appears
in an informational log.
- 10009139: The SPCN loop was closed. This reference code appears
in an informational log.
- 1000913B: An SPCN firmware update was required, but not automatically
started. This reference code appears in a serviceable event.
- 1000910A: An SPCN firmware update was initiated. This reference
code appears in an informational log.
- 100091DE: An SPCN firmware update has completed. This reference
code appears in an informational log.
- Complete the verification task that is specified in Verifying the system power control network.
- Verify that the Power Control Network Identifier
value is set correctly for the expansion unit that you are adding
by completing the following steps:
- Access the ASMI by using an authority level of administrator or
authorized service provider. For instructions, see Managing the Advanced System
Management Interface.
- In the ASMI navigation area, expand System Configuration and
select Configure I/O Enclosures.
- Review the Enclosure Configuration table to locate the expansion
unit that you added.
- Use the following information to verify that the expansion unit
that you added has the correct Power Control Network Identifier:
- Identifier 0x8D is for 5796 and 7314-G30 expansion units.
- Identifier 0x8E is for 5802 and 5877 expansion units.
- If an incorrect Power Control
Network Identifier is specified for the expansion unit that you added,
contact your service provider for assistance before you continue with
this procedure.
- Verify the 12X configuration by completing
the following steps:
- Read and understand the following information about reference
codes that might be generated when an expansion unit is added while
the system is powered on.
Note: When an expansion unit is added while
the system is powered on, it is normal for error logs and event logs
to be created with the following 12X-related reference codes. The
number and combination of these logs is dependent on the configuration.
Logs
with the following reference codes can be ignored during this verification
step if their time stamps indicate that they occurred during the add
procedure and the resources that they refer to were involved in the
procedure.
- B7006907: An expansion unit was added that was previously configured
on a different system. This reference code appears in an informational
log.
- B7006982: A 12X connection failure was experienced. This reference
code appears in an informational log.
- B7006984: A 12X loop was opened. This reference code appears in
an informational log.
- B7006985: A 12X loop was closed. This reference code appears in
an informational log.
- B70069E6: A 12X link was lost. This reference code appears in
an informational log.
- B70069E7: A 12X link was restored. This reference code appears
in an informational log.
- Choose one of the following options.
- If your system is managed by an HMC, see Verifying the 12X loops with an HMC.
Tip: If you saved the original hardware topology in step
1 before you
added the expansion unit, the saved topology now appears in the last
Valid Hardware Topology section of the
View Hardware Topology output.
Use this operation to compare the topology that was created by adding
the expansion unit to the topology that existed before the expansion
unit was added.
- If your system is not managed by an HMC, see Verifying the 12X loops without an HMC.
- Check for new serviceable events
that were generated during the procedure by choosing one of the following
options:
Important: Multiple options might apply to your
configuration. Choose only the first option that applies.
- If your system is managed by an HMC, complete the following
steps:
- In the navigation area, select .
- Specify event criteria that includes events that were generated
during the procedure. In particular, specify the managed system that
the expansion unit was added to, and specify a date and time range
that includes the data and time that were recorded in step 6.
- Continue with step 15.
- If your system is not managed by an HMC and has a partition
that is running the Virtual I/O Server (VIOS) operating system,
complete the following steps:
- Log in as the padmin user. If you need
assistance, contact the system administrator.
- Type diagmenu -d sysplanar0 -E xx and press
Enter, where xx specifies the number of days
in the range 1 - 60. This command returns results for the most recent
number of days specified. Specify a range that includes the date and
time that was recorded in step 6.
- On the DIAGNOSTIC MODE SELECTION display, highlight the Problem
Determination option, and press Enter.
- Continue with step 15.
- If your system is not managed by an HMC and has a partition
that is running the AIX operating
system, complete the following steps:
- Log in as the root user, or use the CE login. If you need assistance,
contact the system administrator.
- Type diag -d sysplanar0 -E xx and press
Enter, where xx specifies the number of days
in the range 1 - 60. This command returns results for the most recent
number of days specified. Specify a range that includes the date and
time that was recorded in step 6.
- On the DIAGNOSTIC MODE SELECTION display, highlight the Problem
Determination option, and press Enter.
- Continue with step 15.
- If your system is not managed by an HMC and has a partition
that is running the IBM i operating
system, complete the following steps:
- Sign on with at least service level authority.
- At the command line of the IBM i session, type strsst and
press Enter.
- Type your service tools user ID and service tools password on
the System Service Tools (SST) Sign On display, and press Enter. The
service tools password is case-sensitive.
- Click .
- On the Select Timeframe display, change
the From Date and Time field to the wanted
date and time range. Specify a range that includes the date and time
that was recorded in step 6.
- Continue with step 15.
- If your system is not managed by an HMC and has a partition
that is running the Linux operating
system, complete the following steps:
- Log in as the root user. If you need assistance, contact the system
administrator.
- Type servicelog –query='serviceable=1 AND closed=0
AND time_event>="yyyy-mm-dd"' and press Enter, where yyyy-mm-dd is
the day on which the procedure occurred.
- Continue with step 15.
- Handle serviceable events that were generated
during the procedure by completing the following steps:
- Close any serviceable events that were generated during the procedure
that includes one of the reference codes that are listed in step 11 or step 13.
- Perform problem analysis on any remaining open serviceable events.
- Start necessary SPCN firmware updates.
If
you found the reference code 1000913B in step
11.a, an SPCN firmware
update is needed. However, because of the current SPCN Firmware Update
Policy, the update could not be initiated automatically. To initiate
the SPCN firmware update manually, complete the following steps:
- To initiate the SPCN firmware updates, see Updating the SPCN firmware.
- Wait for the SPCN firmware updates to complete before you continue
to the next step. This update can take 20 minutes to several hours,
depending on the number of expansion units on the SPCN loop. The amount
of time can also be influenced by the current level of the SPCN firmware
in the expansion units that were added.
- If you changed the SPCN Firmware Update Policy in step 3.b.i, change the
policy back to the original setting now by completing the following
steps:
- Access the ASMI by using an authority level of administrator or
authorized service provider. For instructions, see Managing the Advanced System
Management Interface.
- In the ASMI navigation area, expand System Configuration and
select Configure I/O Enclosures.
- Change the SPCN Firmware Update Policy setting
to the setting recorded in step 3.b.i.
Note: The
default setting of Enabled is recommended.
- Verify the new configuration. For
instructions, see Verifying that the new configuration is functioning.
- If the system has logical partitions, you
can now assign I/O slots in the expansion units that were added to
logical partitions.
You have completed the addition of your expansion
unit.
Subscribe to this information