0% found this document useful (0 votes)

128 views92 pages

Enclosures and Expansion Units: Power Systems

This edition applies to IBM Power Systems servers that contain the POWER7 processor. Identifying and configuring I / O expansion units..

Uploaded by

johnwooder

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

128 views92 pages

Enclosures and Expansion Units: Power Systems

This edition applies to IBM Power Systems servers that contain the POWER7 processor. Identifying and configuring I / O expansion units..

Uploaded by

johnwooder

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 92

Power Systems

Enclosures and expansion units

Power Systems

Enclosures and expansion units

Note Before using this information and the product it supports, read the information in Notices on page 69, Safety notices on page v, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z1255823.

This edition applies to IBM Power Systems servers that contain the POWER7 processor and to all associated models. Copyright IBM Corporation 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Connecting and configuring I/O expansion units . . . . . . . . . . . . . . . . . . 1
Overview for I/O expansion units . . . . . . . . . . . . . . . . . . . Preparing to connect your expansion units . . . . . . . . . . . . . . . . Where to install a new expansion unit . . . . . . . . . . . . . . . . . Identifying 12X and SPCN cables . . . . . . . . . . . . . . . . . . Cable options . . . . . . . . . . . . . . . . . . . . . . . . . System unit 12X cable options . . . . . . . . . . . . . . . . . . Expansion unit 12X cable options . . . . . . . . . . . . . . . . . Expansion unit configuration rules . . . . . . . . . . . . . . . . . Connecting your expansion units . . . . . . . . . . . . . . . . . . . Connecting expansion units with 12X cables . . . . . . . . . . . . . . . Adding expansion units to a new 12X loop . . . . . . . . . . . . . . Adding expansion units to an existing 12X loop . . . . . . . . . . . . Examples: 12X connections . . . . . . . . . . . . . . . . . . . Connecting expansion units with SPCN cables. . . . . . . . . . . . . . Examples: SPCN connections . . . . . . . . . . . . . . . . . . Connector locations. . . . . . . . . . . . . . . . . . . . . . . Model 8202-E4B connector locations . . . . . . . . . . . . . . . . Model 8205-E6B connector locations . . . . . . . . . . . . . . . . Model 8231-E2B connector locations . . . . . . . . . . . . . . . . Model 8233-E8B connector locations . . . . . . . . . . . . . . . . Model 9117-MMB or 9179-MHB connector locations . . . . . . . . . . . Model 5796 or 7314-G30 connector locations . . . . . . . . . . . . . Model 5802 and 5877 connector locations . . . . . . . . . . . . . . Verifying that the new configuration is functioning . . . . . . . . . . . . Verifying the 12X loops with an HMC . . . . . . . . . . . . . . . Verifying the 12X loops without an HMC . . . . . . . . . . . . . . Verifying the system power control network (SPCN). . . . . . . . . . . . Setting I/O enclosure configuration ID and MTMS value . . . . . . . . . Using the ASMI to verify and set the configuration ID and MTMS value . . . Updating the SPCN firmware . . . . . . . . . . . . . . . . . . . Removing an expansion unit . . . . . . . . . . . . . . . . . . . . Removing an expansion unit concurrently . . . . . . . . . . . . . . . Removing an expansion unit nonconcurrently . . . . . . . . . . . . . . Common procedures for expansion units . . . . . . . . . . . . . . . . Verifying that the new configuration is functioning . . . . . . . . . . . . Starting the system or logical partition . . . . . . . . . . . . . . . . Starting a system that is not managed by a Hardware Management Console . . Starting a system or logical partition by using the Hardware Management Console Stopping a system or logical partition . . . . . . . . . . . . . . . . Stopping a system that is not managed by a Hardware Management Console . . Stopping a system by using the Hardware Management Console . . . . . . Identifying a failing part . . . . . . . . . . . . . . . . . . . . . Identifying a failing part in an AIX system or logical partition . . . . . . . Locating a failing part in an AIX system or logical partition . . . . . . . Activating the indicator light for the failing part . . . . . . . . . . . Identifying a failing part in an IBM i system or logical partition . . . . . . . Activating the failing-part indicator light . . . . . . . . . . . . . Deactivating the failing-part indicator light . . . . . . . . . . . . . Identifying a failing part in a Linux system or logical partition . . . . . . . Locating a failing part in a Linux system or logical partition . . . . . . . Finding the location code of a failing part in a Linux system or logical partition Activating the indicator light for the failing part . . . . . . . . . . .
Copyright IBM Corp. 2010

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . .

. 1 . 2 . 2 . 2 . 3 . 3 . 4 . 4 . 5 . 8 . 9 . 9 . 10 . 11 . 13 . 13 . 14 . 14 . 15 . 16 . 17 . 17 . 18 . 18 . 19 . 20 . 21 . 22 . 23 . 25 . 25 . 26 . 29 . 31 . 31 . 31 . 31 . 33 . 33 . 33 . 35 . 35 . 35 . 35 . 36 . 36 . 36 . 37 . 37 . 37 . 38 . 38

iii

Deactivating the failing-part indicator light . . . . . . . . . . Locating a failing part in a Virtual I/O Server system or logical partition. Identifying a part by using the Virtual I/O Server . . . . . . .

. . .

. 38 . 39 . 39

Connecting and configuring disk drive enclosures . . . . . . . . . . . . . . . . . 41

Overview for disk drive enclosures . . . . . . . . . . . . . . . . . . . . . . . . . 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure . . . . . . . . . . . . . . . . . Connecting the 5786, 5787, 7031-D24, or 7031-T24 to a system that has an AIX operating system . . . . Connecting and configuring the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure in an AIX clustered environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting and configuring the disk drive enclosure in a system that has a Linux operating system . . Connecting and configuring the enclosure in a system with the IBM i operating system . . . . . . . SCSI repeater card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing and replacing a SCSI repeater card . . . . . . . . . . . . . . . . . . . . . Configuring the disk drive subsystem on the 5802 expansion unit . . . . . . . . . . . . . . . Cabling the 5802 disk subsystem . . . . . . . . . . . . . . . . . . . . . . . . . Cabling the 5802 and 5877 to the server . . . . . . . . . . . . . . . . . . . . . . . 5886 SAS disk drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting the SAS adapter to the 5886 disk drive enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 . 41 . 41 . . . . . . . . . . 45 47 51 54 57 58 60 64 64 64

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Trademarks . . . . . Electronic emission notices Class A Notices . . . Class B Notices . . . Terms and conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 70 70 74 77

Power Systems: Enclosures and expansion units

Safety notices
Safety notices may be printed throughout this guide: v DANGER notices call attention to a situation that is potentially lethal or extremely hazardous to people. v CAUTION notices call attention to a situation that is potentially hazardous to people because of some existing condition. v Attention notices call attention to the possibility of damage to a program, device, system, or data.

World Trade safety information

Several countries require the safety information contained in product publications to be presented in their national languages. If this requirement applies to your country, a safety information booklet is included in the publications package shipped with the product. The booklet contains the safety information in your national language with references to the U.S. English source. Before using a U.S. English publication to install, operate, or service this product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the U.S. English publications.

German safety information

Das Produkt ist nicht fr den Einsatz an Bildschirmarbeitspltzen im Sinne 2 der Bildschirmarbeitsverordnung geeignet.

Laser safety information

IBM servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs. Laser compliance IBM servers may be installed inside or outside of an IT equipment rack.

Copyright IBM Corp. 2010

DANGER When working on or around the system, observe the following precautions: Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product. v Do not open or service any power supply assembly. v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords. v Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet supplies proper voltage and phase rotation according to the system rating plate. v Connect any equipment that will be attached to this product to properly wired outlets. v When possible, use one hand only to connect or disconnect signal cables. v Never turn on any equipment when there is evidence of fire, water, or structural damage. v Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. v Connect and disconnect cables as described in the following procedures when installing, moving, or opening covers on this product or attached devices. To Disconnect: 1. Turn off everything (unless instructed otherwise). 2. Remove the power cords from the outlets. 3. Remove the signal cables from the connectors. 4. Remove all cables from the devices To Connect: 1. Turn off everything (unless instructed otherwise). 2. Attach all cables to the devices. 3. Attach the signal cables to the connectors. 4. Attach the power cords to the outlets. 5. Turn on the devices. (D005)

DANGER

Power Systems: Enclosures and expansion units

Observe the following precautions when working on or around your IT rack system: v Heavy equipmentpersonal injury or equipment damage might result if mishandled. v Always lower the leveling pads on the rack cabinet. v Always install stabilizer brackets on the rack cabinet. v To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest devices in the bottom of the rack cabinet. Always install servers and optional devices starting from the bottom of the rack cabinet. v Rack-mounted devices are not to be used as shelves or work spaces. Do not place objects on top of rack-mounted devices.

v Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords in the rack cabinet when directed to disconnect power during servicing. v Connect all devices installed in a rack cabinet to power devices installed in the same rack cabinet. Do not plug a power cord from a device installed in one rack cabinet into a power device installed in a different rack cabinet. v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock. CAUTION v Do not install a unit in a rack where the internal rack ambient temperatures will exceed the manufacturer's recommended ambient temperature for all your rack-mounted devices. v Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is not blocked or reduced on any side, front, or back of a unit used for air flow through the unit. v Consideration should be given to the connection of the equipment to the supply circuit so that overloading of the circuits does not compromise the supply wiring or overcurrent protection. To provide the correct power connection to a rack, refer to the rating labels located on the equipment in the rack to determine the total power requirement of the supply circuit. v (For sliding drawers.) Do not pull out or install any drawer or feature if the rack stabilizer brackets are not attached to the rack. Do not pull out more than one drawer at a time. The rack might become unstable if you pull out more than one drawer at a time. v (For fixed drawers.) This drawer is a fixed drawer and must not be moved for servicing unless specified by the manufacturer. Attempting to move the drawer partially or completely out of the rack might cause the rack to become unstable or cause the drawer to fall out of the rack. (R001)

Safety notices

vii

CAUTION: Removing components from the upper positions in the rack cabinet improves rack stability during relocation. Follow these general guidelines whenever you relocate a populated rack cabinet within a room or building: v Reduce the weight of the rack cabinet by removing equipment starting at the top of the rack cabinet. When possible, restore the rack cabinet to the configuration of the rack cabinet as you received it. If this configuration is not known, you must observe the following precautions: Remove all devices in the 32U position and above. Ensure that the heaviest devices are installed in the bottom of the rack cabinet. Ensure that there are no empty U-levels between devices installed in the rack cabinet below the 32U level. v If the rack cabinet you are relocating is part of a suite of rack cabinets, detach the rack cabinet from the suite. v Inspect the route that you plan to take to eliminate potential hazards. v Verify that the route that you choose can support the weight of the loaded rack cabinet. Refer to the documentation that comes with your rack cabinet for the weight of a loaded rack cabinet. v Verify that all door openings are at least 760 x 230 mm (30 x 80 in.). v v v v v Ensure that all devices, shelves, drawers, doors, and cables are secure. Ensure that the four leveling pads are raised to their highest position. Ensure that there is no stabilizer bracket installed on the rack cabinet during movement. Do not use a ramp inclined at more than 10 degrees. When the rack cabinet is in the new location, complete the following steps: Lower the four leveling pads. Install stabilizer brackets on the rack cabinet. If you removed any devices from the rack cabinet, repopulate the rack cabinet from the lowest position to the highest position. v If a long-distance relocation is required, restore the rack cabinet to the configuration of the rack cabinet as you received it. Pack the rack cabinet in the original packaging material, or equivalent. Also lower the leveling pads to raise the casters off of the pallet and bolt the rack cabinet to the pallet. (R002) (L001)

(L002)

viii

Power Systems: Enclosures and expansion units

(L003)

All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information. CAUTION: This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive, DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information: v Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device. v Use of the controls or adjustments or performance of procedures other than those specified herein might result in hazardous radiation exposure. (C026)

Safety notices

CAUTION: Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. (C027) CAUTION: This product contains a Class 1M laser. Do not view directly with optical instruments. (C028) CAUTION: Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following information: laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. (C030)

Power and cabling information for NEBS (Network Equipment-Building System) GR-1089-CORE
The following comments apply to the IBM servers that have been designated as conforming to NEBS (Network Equipment-Building System) GR-1089-CORE: The equipment is suitable for installation in the following: v Network telecommunications facilities v Locations where the NEC (National Electrical Code) applies The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposed wiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to the interfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connect these interfaces metallically to OSP wiring. Note: All Ethernet cables must be shielded and grounded at both ends. The ac-powered system does not require the use of an external surge protection device (SPD). The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminal shall not be connected to the chassis or frame ground.

Power Systems: Enclosures and expansion units

Connecting and configuring I/O expansion units

Use this information to learn about connecting and configuring Input/Output (I/O) expansion units to system units.

Overview for I/O expansion units

Input/Output expansion units provide additional I/O slots. Some I/O expansion units also provide additional disk and removable media slots. Input/Output (I/O) expansion units are connected to system units with 12X cables and system power control network (SPCN) cables. The 12X cables can transport data and control information. The SPCN cables can only transport control information. The 12X cables from an I/O-expansion unit connect to a12X cable port pair (also called a connector pair) at the system unit. The 12X port pair is either on a pluggable card installed in the system unit, or mounted directly on the system unit chassis. In either case, the connectors are wired to an I/O hub chip that drives the 12X protocol. The pluggable cards are referred to as GX adapters or GX cards. The 12X interconnect between I/O expansion units and system units can be single data rate (SDR) or double data rate (DDR). Some I/O expansion units are capable of SDR only. Others are capable of both SDR and DDR. Similarly some I/O hub chips and 12X cables are capable of SDR only while others are capable of both SDR and DDR. In order for a 12X interconnect between a system unit and I/O expansion unit to run at DDR, the I/O hub chip, 12X cable, and expansion unit must all be DDR capable. While components that are strictly SDR capable cannot run at DDR, components that are DDR capable can be configured by the system firmware to run at SDR if one or more of the other components in the interconnect are strictly SDR capable. For example, a DDR capable I/O expansion unit that is connected to a GX adapter that has a strictly SDR capable I/O hub chip will be configured to run at SDR. Similarly, a DDR capable GX adapter that is connected to a strictly SDR capable I/O expansion unit will be configured to run at SDR. Notes: v Except where the distinction is important, '12X cable' may be used to refer to either a 12X SDR cable or a 12X DDR cable. v Except where the distinction is important, GX adapter or GX card may be used to refer to either an SDR or a DDR version. v The terms I/O expansion unit and expansion unit may be used interchangeably. Important: v Depending on your configuration, you might be able to add your expansion units concurrently. This means you can add or install the expansion units with the server powered on and the firmware in standby or running state. Active partitions do not have to be shut down. Only if the expansion units are being added to an IBM Power Systems server that is not managed by a Hardware Management Console (HMC) and is running the AIX or Linux operating system must the server be shut down (powered off) to add expansion units. v If additional GX adapters are needed to accommodate the new I/O expansion units, refer to the instructions that came with the GX adapters for information on how to install them. Installing GX adapters must be done separately from installing expansion units. Depending on your configuration, it may be necessary to power off the system to install the GX adapters.

Copyright IBM Corp. 2010

v Expansion units cannot be moved or relocated concurrently. If existing expansion units must be relocated in the configuration in order to add the new expansion units, complete the following tasks: 1. Power off the system. 2. Physically relocate the expansion units. 3. Power on the system to firmware standby or firmware running state. The relocation of the existing expansion units is complete. 4. Follow the instructions in this procedure to add the new expansion units.

Preparing to connect your expansion units

Use this information to plan the installation and configuration of your expansion units. This topic collection provides information about connecting your expansion units with 12X and system power control network (SPCN) cables. This is a customer task. You can perform this task yourself or contact a service provider for this service. To prepare to connect the expansion units, complete the following tasks: 1. Decide where you want to install the new expansion units. For details, see Where to install a new expansion unit. 2. Unpack the expansion units by using the unpacking instructions. 3. Identify the cables. For details, see Identifying 12X and SPCN cables. 4. Plan for cable layout. For details, see Cable options on page 3. 5. Continue with Connecting your expansion units on page 5.

Where to install a new expansion unit

Before you begin the installation process, plan where you will install the new expansion units. When deciding where to install a new expansion unit, consider several elements that include size, security, and environmental factors. For more information, see Site preparation and physical planning. If you plan to install your expansion unit in a rack, refer to Racks, rack features, and installing systems or expansion units into a rack. Note: Two expansion units, the 5796 and 7314-G30, can be ordered with a 12X adapter that has a repeater to support longer 12X cable lengths, or a 12X card without a repeater that does not support longer cable lengths. If you are installing a 5796 or 7314-G30 expansion unit with a Short Run Dual-Port Channel Attach 12X adapter (FC 6446), the expansion unit must be placed in the same rack as the system unit. If you are installing a 5796 or 7314-G30 expansion unit with a Long Run Dual-Port Channel Attach 12X adapter (FC 6457), the expansion unit can be placed in the same rack as the system unit, or a different rack.

Identifying 12X and SPCN cables

Use this information to help identify the 12X cables and system power control network (SPCN) cables for the expansion unit. The system uses 12X SDR or 12X DDR cables to send and receive customer data and auxiliary control information to and from the expansion unit, and to download expansion unit firmware. The SPCN network is used to control power to the expansion units and as a backup to the 12X cables for auxiliary control and firmware control.

Power Systems: Enclosures and expansion units

Table 1. 12X cables Cable feature 1828 (copper) 1841 1842 1861 1862 1863 1864 1865 Table 2. SPCN cables Cable feature 6001 6006 6007 6008 6029 CCIN 6001 6006 6007 6008 6029 Length 2 meters 3 meters 15 meters 6 meters 30 meters Part number 22R5217 22R5239 22R5221 22R5219 22R5222 Cable type 12X to 4X channel conversion adapter 12X to 4X channel conversion cable 12X to 4X channel conversion cable DDR 12X DDR 12X DDR 12X DDR 12X DDR 12X Length 1.5 meters 3.0 meters 10 meters 0.6 meters 1.5 meters 2.5 meters 8.0 meters 3.0 meters Part number 45D2235 45D2236 45D2237 45D4785 45D4786 45D4787 45D4788 45D5271

Cable options
Learn about cable topologies, options, and configuration requirements. When you decide where to place the cables, follow your site plan and keep the following items in mind: v Avoid creating a safety hazard. v Avoid damaging the cables. v Avoid placing cables parallel to high-voltage lines.

System unit 12X cable options

Learn which 12X cables are supported on which system units. Use the following table to identify the 12X cables for the machine types and model numbers identified.
Table 3. 12X cable options for system units Cable feature 1828 (copper) 1829 1830 1834 1840 (12X adapter) 1841 1842 1861 (DDR 12X adapter) 8233-E8B Used for clustering only To attach the 5796 or 7314-G30 expansion units To attach the 5796 or 7314-G30 expansion units To attach the 5796 or 7314-G30 expansion units To attach the 5796 or 7314-G30 expansion units Used for clustering only Used for clustering only X

Connecting and configuring I/O expansion units

Table 3. 12X cable options for system units (continued) Cable feature 1862 (DDR 12X adapter) 1864 (DDR 12X adapter) 1865 (DDR 12X adapter) 8233-E8B X X X

Expansion unit 12X cable options

Learn which 12X cables are available for which expansion units. Use the following table to identify the 12X cables for the expansion units identified.
Table 4. Expansion unit 12X cable options Cable feature 1861 0.6M DDR 12X adapter 1862 1.5M DDR 12X adapter 1863 2.5M DDR 12X adapter 1864 8.0M DDR 12X adapter 1865 3.0M DDR 12X adapter 7314-G30, 5796, or 5802 and 5877 X X X X X

Expansion unit configuration rules

Learn about important configuration rules that must be followed when connecting expansion units to system units. When you set up an expansion unit, observe the configuration rules in the following list: v Expansion units must be connected to system units with 12X cables in a loop topology. Doing so produces redundancy in the 12X connections so a single cable failure does not result in loss of communication between the system unit and one or more expansion units. v Expansion units must be connected to system units with SPCN cables in a loop topology. Doing so produces redundancy in the SPCN connections so a single cable failure does not result in loss of communication between the system unit and one or more expansion units. v Expansion units with 12X SDR capability cannot be in the same 12X loop as expansion units with 12X DDR capability. Expansion units with 12X SDR capability include the 5796 and 7314-G30. Expansion units with 12X DDR capability include the 5802 and 5877. The following table specifies limits related to 12X loops.
Table 5. 12X loop limits Machine type and model Supported expansion units Maximum number of loops Maximum number of expansion units per loop 7314-G30 and 5796 = 4 5802 = 2 5877 = 2 Maximum number of supported expansion units 7314-G30 and 5796 = 8 5802 = 4 5877 = 4

8233-E8B

7314-G30 5796 5802 5877

The maximum number of loops varies with the number of processor cards: 1 card = 1 loop 2-4 cards = 2 loops

Power Systems: Enclosures and expansion units

Connecting your expansion units

Learn important information about connecting your expansion units. Important: If you have not reviewed the information in Overview for I/O expansion units on page 1 and Preparing to connect your expansion units on page 2, do so now. Note: Steps in this section require you to have connector information for the hardware in your configuration. For details on expansion unit or system connector locations, see Connector locations (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/connectorlocations.htm). To add expansion units, follow these steps: 1. You can install the expansion units with the system powered on or off. For more information about when system unit power must be off before installation, see Overview for I/O expansion units (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/p7hamconcepts.htm). a. If you are installing a new system unit and expansion units, refer to step 5 on page 6. b. If you are adding expansion units to an existing system and will be doing so with the system powered off, remove power from the system now. For details, see Stopping a system or logical partition (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7haj/ crustopsys.htm). After you have powered off your system unit, continue with step 5 on page 6 to complete this procedure. c. If you are adding expansion units to an existing system and can leave the power on, continue with step 2. 2. Verify the existing 12X configuration. If problems with the 12X loops are discovered in this step, they must be corrected before continuing with this procedure. Follow the appropriate step to determine if there are problems with the 12X configuration. v If your system is not managed by an HMC and you are running the IBM i operating system, see Verifying the 12X loops without an HMC (http://publib.boulder.ibm.com/infocenter/systems/ scope/hw/topic/p7ham/ipham_verifyriohslloopwohmc.htm). v If your system is managed by an HMC, see Verifying the 12X loops with an HMC (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ ipham_verifyriohslloopwhmc.htm). When instructed in that section to use the View Hardware Topology task on the HMC, you can use the Save button to save the current hardware topology. This action allows you to compare the topology that was created by adding the expansion units to the topology that existed before the expansion units were added. 3. Verify the existing system power control network (SPCN). For details, see Verifying the system power control network (SPCN) (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/ topic/p7ham/verifyspcn.htm). If you discover a problem with the SPCN, you must correct the problem before continuing. 4. Set the SPCN Firmware Update Policy to prevent firmware updates over the serial SPCN interface. The SPCN Firmware Update Policy controls when and how SPCN firmware on expansion units is updated. The default setting shipped with your system 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. a. Access the ASMI using an authority level of Administrator or Authorized service provider. For details on using the ASMI, see Managing the Advanced System Management Interface (ASMI) (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hby/asmi.htm). b. In the ASMI navigation area, expand System Configuration and select Configure I/O Enclosures. v If the SPCN Firmware Update Policy is Expanded, record the current setting so you can restore it later. Then change the setting to Enabled.

Connecting and configuring I/O expansion units

v If the SPCN Firmware Update Policy is Enabled or Disabled, continue without changing the setting. c. Verify there are no SPCN firmware updates in progress by checking the Power Control Network Firmware Update Status column. This column shows the words In Progress and a percent complete if an SPCN firmware update is in progress. If there is an SPCN firmware update in progress, determine if the update is a Serial or HSL update by checking the Power Control Network Firmware Update Status column for one of these words indicating the type of update. If the SPCN firmware update is an HSL update, wait for the update to complete before continuing. An HSL update of the SPCN firmware completes quickly. If the SPCN firmware update is a Serial update, either wait for the update to complete or stop the update. A Serial update of the SPCN firmware can take 20 minutes or more depending on how many expansion units are in the configuration. To determine when the update is complete, select Configure I/O Enclosures every 15 seconds to 30 seconds until the words Not Required are displayed in the Power Control Network Firmware Update Status column. Do not use the Back or Refresh buttons on the browser to monitor the status. If you choose to stop the update, the update will be restarted from the beginning after you have completed the procedure. To stop the update, perform the following steps: 1) Press the Stop SPCN Firmware Update button on the Configure I/O Enclosures panel. 2) Select Configure I/O Enclosures every 15 - 30 seconds until the word Pending is displayed in the Power Control Network Firmware Update Status column. Do not use the Back or Refresh buttons on the browser to monitor the status. 5. Remove or open the back of the system unit. 6. To connect the expansion units with 12X cables, see Connecting expansion units with 12X cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/direct.htm). Note: If you are installing expansion units in an existing 12X loop with the system powered on and firmware at standby or running state, serviceable events and informational logs might be generated when you disconnect and reconnect cables. This is normal and will be addressed later in the procedure. 7. To connect the expansion units with SPCN cables, see Verifying the system power control network (SPCN) (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ spcndirect.htm). Note: If you are installing expansion units in an existing SPCN loop with the system powered on and firmware at standby or running state, serviceable events and informational logs might be generated when you disconnect and reconnect cables. This is normal and will be addressed later in the procedure. 8. Connect the power cables for the expansion units that you are installing to the power source. Then connect them to the power supplies on the expansion units. If you installed the expansion units with the system's power off, continue with step 10 on page 7. If not, continue with the next step. Note: Plug the power cable into the power source before connecting it into the power supply of the expansion unit. 9. The expansion units will power on automatically. After the expansion units that you have installed are powered on and you have waited 10 minutes for the hardware initialization to complete, continue with step 11 on page 7. Tip: For each expansion unit, wait for the green power indicator to light solid on the control panel of the expansion unit that just powered on. This action might take between one and 10 minutes. During this time, a yellow attention indicator might be lit on the control panel of the expansion unit

Power Systems: Enclosures and expansion units

that just powered on. After the green power indicators are lit on the control panels of all the expansion units that were just powered on, wait 10 additional minutes for hardware initialization to complete before proceeding to step 11. 10. To start the system or logical partition, see Starting the system or logical partition (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7haj/crustartsys.htm). 11. Verify the SPCN configuration. After reading the note below, see Verifying the system power control network (SPCN) (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ spcndirect.htm). Note: While concurrently adding an expansion unit, 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. The logs can be ignored during this verification step if their timestamps indicate that they occurred during the add procedure and if the resources that they refer to were involved in the procedure. v 10009135: This reference code indicates that the SPCN loop was opened, and might appear in a serviceable event or an informational log. v 10009136: This reference code indicates that an SPCN firmware update was stopped, and appears in an informational log. v 10009137: This reference code indicates disruption of the 12X loop, and appears in a serviceable event. v 10009139: This reference code indicates that the SPCN loop was closed, and appears in an informational log. v 1000910A: This reference code indicates that an SPCN firmware update was initiated, and appears in an informational log. v 100091DE: This reference code indicates that an SPCN firmware update completed, and appears in an informational log. v 1000913B: This reference code indicates that an SPCN firmware update was required, but not automatically started, and appears in a serviceable event. This condition is corrected in step 15 on page 8. 12. Verify that the Power Control Network Identifier value is set correctly for the expansion units you are adding by completing the tasks in Setting I/O enclosure configuration ID and MTMS value (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ ipham_setconfigid.htm) for each one. Note: Because you checked for temporary type, model, and serial number values in the previous step, the tasks that refer to setting the type, model, and serial number values can be ignored. 13. Verify the 12X configuration. After reading the note below, perform one of the following steps. v If your system is not managed by an HMC and you are running the IBM i operating system, see Verifying the 12X loops without an HMC (http://publib.boulder.ibm.com/infocenter/systems/ scope/hw/topic/p7ham/ipham_verifyriohslloopwohmc.htm). v If your system is managed by an HMC, see Verifying the 12X loops with an HMC (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ ipham_verifyriohslloopwhmc.htm). If you performed a save of the original hardware topology before adding expansion units in step 2 on page 5, the save now appears in Last Valid Hardware Topology section of the View Hardware Topology output. This save allows you to compare the topology that was created by adding the expansion units to the topology that existed before the expansion units were added. Note: While concurrently adding an expansion unit 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. The logs can be ignored during this verification step if their timestamps indicate that they occurred during the add procedure and if the resources that they refer to were involved in the procedure.
Connecting and configuring I/O expansion units

v B7006907: This reference code indicates that an expansion unit was added that was previously configured on a different system, and appears in an informational log. v B7006984: This reference code indicates that a 12X loop was opened, and appears in an informational log. v B7006985: This reference code indicates that a 12X loop was closed, and appears in an informational log. v B70069E6: This reference code indicates that a 12X link was lost, and appears in an informational log. v B70069E7: This reference code indicates that a 12X link was restored, and appears in an informational log. 14. Check for and handle new serviceable events that were generated during the procedure by performing the following steps: a. Select from the following options: v If your system is managed by an HMC, select Serviceability Manage Serviceable Events. v If your system is not managed by an HMC, from an IBM i session select Work with service action log from Hardware Service Manager in System Service Tools. b. Specify event criteria that will include any events that were generated during the procedure. c. Serviceable events generated during the procedure that include one of the reference codes listed in step 11 on page 7 or step 13 on page 7 and call out resources involved in the procedure should be closed. d. Perform problem analysis on any remaining open serviceable events. 15. Start necessary SPCN firmware updates. If reference code 1000913B was found in step 11 on page 7, an SPCN firmware update is needed. However, due to the current SPCN Firmware Update Policy, the update could not be initiated automatically. Therefore, the SPCN firmware update must be initiated manually. To complete this task, see Updating the SPCN firmware (http://publib.boulder.ibm.com/infocenter/systems/scope/ hw/topic/p7ham/ipham_updatespcn.htm). Wait for the SPCN firmware updates to complete before continuing to the next step. This update could take from 20 minutes to several hours depending on the number of expansion units on the SPCN loop and the current level of the SPCN firmware in the expansion units that were added. 16. If you changed the SPCN Firmware Update Policy in step 4 on page 5, the policy can be changed back to the original setting now. a. Access the ASMI using an authority level of Administrator or Authorized service provider. For details, see Managing the Advanced System Management Interface (http:// publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hby/asmi.htm). b. In the ASMI navigation area, expand System Configuration and select Configure I/O Enclosures. c. Change the SPCN Firmware Update Policy setting to the setting recorded in step 4 on page 5. The default and recommended setting is Enabled. 17. Verify the new configuration. For details, see Verifying that the new configuration is functioning (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/verify.htm). 18. If the system is logically partitioned, you can now assign I/O slots in the expansion units that were added to logical partitions.

Connecting expansion units with 12X cables

These instructions explain how to connect expansion units to a system unit with 12X cables in either a new or existing loop. Tip: If multiple expansion units are to be added with the system power on, work with one 12X loop at a time. For example, if the plan is to add three expansion units to loop X and two to loop Y, follow the

Power Systems: Enclosures and expansion units

complete procedure to simultaneously add the three units to loop X. When the first procedure has been completed, then follow the procedure to simultaneously add the two units to loop Y. It is not necessary to complete the procedure for each expansion unit separately. After reviewing Examples: 12X connections on page 10, select one of the following options: v If you are creating a new 12X loop with the expansion units you are adding, see Adding expansion units to a new 12X loop. v If you are adding expansion units to an existing 12X loop, see Adding expansion units to an existing 12X loop.

Adding expansion units to a new 12X loop

Use this procedure when the expansion units will create a new 12X loop as opposed to being added to an existing 12X loop. Unused 12X connectors might be covered with metal clips. Remove the clips before you install the 12X cables. Complete the following steps to add the expansion units to the 12X configuration: 1. On the system unit to which you are going to connect the new expansion units, identify connectors 0 and 1 of the 12X connector pair that you are going to use. 2. Find the 12X cables that were included with the expansion units. 3. Connect a 12X cable to connector 0 on one of the expansion units to be added. 4. Connect another 12X cable to connector 1 on the expansion unit added in step 3. 5. If there is another expansion unit to add, do the following: a. Connect the other end of the cable from connector 1 on the expansion unit just added to connector 0 on the next expansion unit to be added. b. Connect another cable to connector 1 on the expansion unit added in step 5a. c. Repeat step 5 for each additional expansion unit. 6. Connect the other end of the cable from connector 0 on the first expansion unit added to connector 0 on your system unit. 7. Connect the other end of the cable from connector 1 on the last expansion unit added to connector 1 on your system unit. 8. Return to the procedure that sent you here.

Adding expansion units to an existing 12X loop

Use this procedure to add expansion units to an existing 12X loop. Unused 12X connectors might be covered with metal clips. Remove the clips before you install the 12X cables. Complete the following steps to add the expansion units to the 12X configuration: 1. Identify the 12X loop to which you want to add the expansion units. 2. Identify connectors 0 and 1 of the 12X connector pair on the system unit that are associated with the loop identified in step 1. 3. Find the 12X cables that were included with the expansion units. 4. Choose from the following options: v To add the expansion units to the beginning of the loop, go to step 5. v To add the expansion units to the middle of the loop, go to step 6 on page 10. v To add the expansion units to the end of the loop, go to step 7 on page 10. 5. To add the expansion units to the beginning of the loop, complete the following steps:

Connecting and configuring I/O expansion units

a. Move the 12X cable from connector 0 on the first expansion unit on the loop (the one connected to connector 0 on the system unit) to connector 0 on one of the expansion units to be added. b. Connect another 12X cable to connector 1 on the expansion unit added in step 5a. c. If you are adding another expansion unit, do the following: 1) Connect the other end of the cable from connector 1 on the expansion unit just added to connector 0 on the next expansion unit to be added. 2) Connect another cable to connector 1 on the expansion unit added in step 5c1. 3) Repeat step 5c for each additional expansion unit. d. Connect the other end of the cable from connector 1 on the last expansion unit added to connector 0 on the expansion unit that was disconnected in step 5a. 6. To add the expansion units to the middle of the loop, complete the following steps: a. Move the 12X cable from connector 0 on the expansion unit that will follow the expansion units that are being added to connector 0 on one of the expansion units to be added. b. Connect another 12X cable to connector 1 on the expansion unit added in step 6a. c. If you are adding another expansion unit, do the following: 1) Connect the other end of the cable from connector 1 on the expansion unit just added to connector 0 on the next expansion unit to be added. 2) Connect another cable to connector 1 on the expansion unit added in step 6c1. 3) Repeat step 6c for each additional expansion unit. d. Connect the other end of the cable from connector 1 on the last expansion unit added to connector 0 on the expansion unit that was disconnected in step 6a. 7. To add the expansion units to the end of the loop, complete the following steps: a. Move the 12X cable from connector 1 on the system unit to connector 0 on one of the expansion units to be added. b. Connect another 12X cable to connector 1 on the expansion unit added in step 7a. c. If you are adding another expansion unit, do the following: 1) Connect the other end of the cable from connector 1 on the expansion unit just added to connector 0 on the next expansion unit to be added. 2) Connect another cable to connector 1 on the expansion unit added in step 7a. 3) Repeat step 7c for each additional expansion unit. d. Connect the other end of the cable from connector 1 on the last expansion unit added to connector 1 on the system unit. 8. Return to the procedure that sent you here.

Examples: 12X connections

See how 12X cables are connected to expansion units and system units to form 12X loops. Note: The physical connectors on the system units and expansion units might not have labels, or might have labels that are different from what is shown in the examples. In all cases, the top or left 12X connector corresponds to connector 0 in the examples, and the bottom or right 12X connector corresponds to connector 1 in the examples.

Power Systems: Enclosures and expansion units

Figure 1. Example of 12X and 12X DDR connections

Figure 2. Example of 12X and 12X DDR connections

Connecting expansion units with SPCN cables

Use these instructions to learn how to connect expansion units into the system power control network (SPCN). Review Examples: SPCN connections on page 13 and then return here and continue with the instructions. Important: As noted in Overview for I/O expansion units on page 1, there is only one SPCN loop per system to which all expansion units are connected. 1. Choose from the following options: v To add expansion units when there is not already an SPCN loop, go to step 2. v To add expansion units to the beginning of an existing SPCN loop, go to step 3 on page 12. v To add expansion units to the middle of an existing SPCN loop, go to step 4 on page 12. v To add expansion units to the end of an existing SPCN loop, go to step 5 on page 12. 2. To add expansion units when there is not already an SPCN loop, do the following: a. Find the SPCN cables that were included with your expansion units. b. Connect an SPCN cable to connector SPCN0 on your system unit.

Connecting and configuring I/O expansion units

c. Connect the other end of the SPCN cable to connector SPCN 0 on one of the expansion units to be added. d. Connect another cable to connector SPCN 1 on the expansion unit added in step 2c. e. If there is another expansion unit to add, do the following: 1) Connect the other end of the cable from connector SPCN 1 on the expansion unit just added to connector SPCN 0 on the next expansion unit. 2) Connect another cable to connector SPCN 1 on the expansion unit added in step 2e1. 3) Repeat step 2e for each additional expansion unit to be added. f. Connect the other end of the cable from connector SPCN 1 on the last expansion unit added to connector SPCN1 on your system unit. g. Return to the procedure that sent you here. 3. To add expansion units to the beginning of an existing SPCN loop, do the following: a. Find the SPCN cables that were included with your expansion units. b. Move the SPCN cable from connector SPCN 0 on the first expansion unit (the one connected to connector SPCN0 on the system unit) to connector SPCN 0 on one of the expansion units to be added. c. Connect another SPCN cable to connector SPCN 1 on the expansion unit added in step 3b. d. If there is another expansion unit to add, do the following: 1) Connect the other end of the cable from connector SPCN 1 on the expansion unit just added to connector SPCN 0 on the next expansion unit to be added. 2) Connect another cable to connector SPCN 1 on the expansion unit added in step 3d1. 3) Repeat step 3d for each additional expansion unit. e. Connect the other end of the cable from connector SPCN 1 on the last expansion unit added to connector SPCN 0 on the expansion unit that was disconnected in step 3b. f. Return to the procedure that sent you here. 4. To add expansion units to the middle of an existing SPCN loop, do the following: a. Find the SPCN cables that were included with your expansion units. b. Move the SPCN cable from connector SPCN 0 on the expansion unit that will follow the expansion units that are being added to connector SPCN 0 on one of the expansion units to be added. c. Connect another SPCN cable to connector SPCN 1 on the expansion unit added in step 4b. d. If there is another expansion unit to add, do the following: 1) Connect the other end of the cable from connector SPCN 1 on the expansion unit just added to connector SPCN 0 on the next expansion unit to be added. 2) Connect another cable to connector SPCN 1 on the expansion unit added in step 4d1. 3) Repeat step 4d for each additional expansion unit. e. Connect the other end of the cable from connector SPCN 1 on the last expansion unit added to connector SPCN 0 on the expansion unit that was disconnected in step 4b. f. Return to the procedure that sent you here. 5. To add expansion units to the end of an existing SPCN loop, do the following: a. Find the SPCN cables that were included with your expansion units. b. Move the SPCN cable from connector SPCN 1 on the last expansion unit (the one connected to connector SPCN1 on the system unit) to connector SPCN 1 on one of the expansion units to be added. c. Connect another SPCN cable to connector SPCN 0 on the expansion unit added in step 5b. d. If there is another expansion unit to add, do the following: 1) Connect the other end of the cable from connector SPCN 0 on the expansion unit just added to connector SPCN 1 on the next expansion unit to be added.

Power Systems: Enclosures and expansion units

2) Connect another cable to connector SPCN 0 on the expansion unit added in step 5d1 on page 12. 3) Repeat step 5d on page 12 for each additional expansion unit. e. Connect the other end of the cable from connector SPCN 0 on the last expansion unit added to connector SPCN 1 on the expansion unit that was disconnected in step 5d on page 12. f. Return to the procedure that sent you here.

Examples: SPCN connections

Review examples that show how SPCN cables are connected to expansion units and system units for form SPCN loops. Note: The physical connectors on the system units and expansion units might not have labels, or might have labels that are different from what is shown in the examples. In all cases, the top or left SPCN connector corresponds to SPCN 0 in the examples, and the bottom or right SPCN connector corresponds to SPCN 1 in the examples.

Figure 3. Example of SPCN connections

Figure 4. Example of SPCN connections

Connector locations
Learn about 12X and system power control network (SPCN) connector locations.

Connecting and configuring I/O expansion units

Model 8202-E4B connector locations

Learn about connector locations on rack-mounted and stand-alone models.

Figure 5. Model 8202-E4B connector locations on rack-mounted model

Figure 6. Model 8202-E4B connector locations on stand-alone model

Model 8205-E6B connector locations

Learn about connector locations on rack-mounted and stand-alone models.

Power Systems: Enclosures and expansion units

Figure 7. Model 8205-E6B connector locations on rack-mounted model

Figure 8. Model 8205-E6B connector locations on stand-alone model

Model 8231-E2B connector locations

Learn about connector locations on rack-mounted models.

Connecting and configuring I/O expansion units

Figure 9. Model 8231-E2B connector locations on rack-mounted model

Model 8233-E8B connector locations

Learn about connector locations on the 8233-E8B rack-mounted model.

Figure 10. Model 8233-E8B connector locations

Power Systems: Enclosures and expansion units

Model 9117-MMB or 9179-MHB connector locations

Learn about connector locations.

Figure 11. Model 9117-MMB or 9179-MHB connector locations

Model 5796 or 7314-G30 connector locations

Learn about connector locations.

Figure 12. Model 5796 or 7314-G30 connector locations

Connecting and configuring I/O expansion units

Model 5802 and 5877 connector locations

Learn about connector locations.

Figure 13. Model 5802 and 5877 connector locations

Verifying that the new configuration is functioning

Power Systems: Enclosures and expansion units

1) Make sure that the expansion units are powered on and the power cables are connected to the power source and the expansion units. 2) Make sure that the 12X cables are connected correctly. For details, see Connecting expansion units with 12X cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ p7ham/direct.htm). 3) Make sure that the SPCN cables are connected correctly. For details, see Connecting expansion units with SPCN cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ p7ham/spcndirect.htm). 4) Make sure you verified the MTMS and Configuration ID of the new expansion units. For details, see Setting I/O enclosure configuration ID and MTMS value (http:// publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ipham_setconfigid.htm). 5) If the expansion units still are not displayed, contact your next level of support for assistance. 4. Return to the procedure that sent you here.

Verifying the 12X loops with an HMC

Learn how to verify that there are no failed links in the 12X loops when the system is managed by a Hardware Management Console (HMC). To verify that the 12X loops do not have failed links, complete the following steps with an HMC and with the system powered on: 1. Use the HMC to verify that there are no serviceable events with B70069xx reference codes by completing the following steps. Note: A B70069xx reference code is any reference code that begins with the characters B70069 and ends with any two characters each in 0-9, A-F. a. In the Navigation area, select Service Management. b. Select Manage Serviceable Events. c. In the Manage Serviceable Events window, perform the following steps: 1) Select Open for the Serviceable event status field. 2) Select the machine type, model, and serial numbers (MTMS) of the server you are working with for the Reporting MTMS field. 3) Select ALL for all other fields. d. Click OK. e. Scan for serviceable events with B70069xx reference codes. v If there are no serviceable events with B70069xx reference codes, click Cancel to exit and continue with step 2 v If there are serviceable events with B70069xx reference codes, there might be problems with the 12X loops. Perform problem analysis on the serviceable events to correct the problems before continuing. If you need assistance, contact your next level of support. 2. To verify the status of the links in the 12X loops, perform the following steps from the HMC: a. From the navigation bar, expand Systems Management. b. Select Servers. c. Select the server you are working with. d. From the Tasks area, do the following: 1) Expand Hardware Information. 2) Select View Hardware Topology. e. Find the Current Hardware Topology section of the Hardware Topology data. Look for rows that have something other than Operational in the Leading Port Status or Trailing Port Status column. Then choose from the following options: v If no rows were found with port statuses other than operational, continue to the next step.
Connecting and configuring I/O expansion units

v If rows were found with port statuses other than operational, there are failed or degraded links in the 12X configuration. The links must be repaired before you continue. To repair the links, repeat step 1 on page 19. If you need assistance, contact your next level of support. 3. Return to the procedure that sent you here.

Verifying the 12X loops without an HMC

If your system is not managed by an HMC and is running the IBM i operating system, you can use IBM i to verify that there are no failed links in the 12X loops. Complete the following steps to verify the 12X loops do not have failed links on a system that is not managed by an HMC with the system powered on: 1. Use the service action log to verify that there are no serviceable events with B70069xx reference codes by completing the following steps. Note: A B70069xx reference code is any reference code that begins with the characters B70069 and ends with 2 characters, each in 0 - 9 or A - F. a. Sign on to IBM i with at least service level authority. b. On the command line of the IBM i session, type strsst and press Enter. Note: If you cannot access the System Service Tools display, use function 21 from the control panel. 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. Select Start a service tool from the System Service Tools (SST) display. Press Enter. Select Hardware service manager from the Start a Service Tool display. Press Enter. Select Work with service action log from the Hardware Service Manager display. Press Enter.

c. d. e. f.

g. On the Select Timeframe display, change the From: Date and Time to the appropriate date and time range. The suggested range is 30 days. h. Search for serviceable events with B70069xx reference codes, and select from the following options: v If there are no serviceable events with B70069xx reference codes, press F3 to exit and return to the Hardware Service Manager display. Continue with step 2. v If there are serviceable events with B70069xx reference codes, there might be problems with the 12X loops. Perform problem analysis on the serviceable events to correct the problems before continuing. If you need assistance, contact your next level of support. 2. Use the Hardware Service Manager to verify the statuses of the links in the 12X loops by completing the following steps: a. 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. b. Select Logical hardware resources from the Hardware Service Manager display. Press Enter. c. Select High-speed link resources from the Logical Hardware Resources display. Press Enter. d. Select Display port information for the first 12X loop. Press Enter. e. For each row, verify that the connection status is Operational. If the connection status in each row is operational, press F12 to cancel, and select Display port information for the next 12X loop. v If all of the external 12X connections are operational, press F3 to exit, and continue to the next step. v If the status is not operational for any one of the 12X connections, there are failed or degraded links in the 12X configuration that must be repaired before continuing. To repair the links, repeat step 1. If you need assistance, contact your next level of support.

Power Systems: Enclosures and expansion units

Verifying the system power control network (SPCN)

Check for system power control network (SPCN) errors and inactive enclosures, and fix machine type, model, and serial number (MTMS) problems. 1. Choose from the following options: v If your system is managed by an HMC, continue with step 2. v If your system is not managed by an HMC, continue with step 3. 2. Use the HMC to verify that there are no serviceable events that include 10009xxx reference codes by completing the following steps. Note: A 10009xxx reference code is any reference code that begins with the characters 10009 and ends with 3 characters, each in 0 - 9 or A - F. a. In the navigation area of the HMC, select Service Management. b. In the contents area, select Manage Serviceable Events. c. In the Manage Serviceable Events window, perform the following steps: 1) Select 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) Select ALL for all other fields and click OK. d. Scan for any serviceable events that include 10009xxx reference codes, and perform one of the following actions: v If there are no serviceable events that include 10009xxx reference codes, click Cancel twice to exit Manage Serviceable Events. v If there are serviceable events that include 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. e. Go to step 5 on page 22. 3. If your system is not managed by an HMC, choose from the following options: v If your system is running the IBM i operating system, continue with step 4. v If your system is running the AIX or Linux operating system, continue with step 5 on page 22. 4. Use the service action event log to verify that there are no 10009xxx errors by completing the following steps. Note: A 10009xxx reference code is any reference code that begins with the characters 10009 and ends with 3 characters, each in 0 - 9 or A - F. a. Sign on with at least service level authority. b. On the command line of the IBM i session, type strsst and press Enter. Tip: If you cannot get to the System Service Tools display, use function 21 from the control panel. c. Type your service tools user ID and service tools password on the System Service Tools (SST) Sign On display. Press Enter. Tip: The service tools password is case-sensitive. d. Select Start a Service Tool from the System Service Tools (SST) display. Press Enter. e. Select Hardware Service Manager from the Start a Service Tool display. Press Enter. f. Select Work with Service Action Event Log from the Hardware Service Manager display. Press Enter. g. On the Select Timeframe display, change the From: Date and Time to the desired date and time range. The suggested range is 30 days.

Connecting and configuring I/O expansion units

h. Search for serviceable events with 10009xxx reference codes, and perform one of the following actions: v If there are no serviceable events with 10009xxx reference codes, press F3 (Exit) to return to the Hardware Service Manager display. v 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. i. Go to step 5. 5. Verify that none of the existing expansion units report problems communicating with the system. (Expansion units with a control panel that has a display area report a C62E code when encountering a communication problem with the system.) Correct any reported problems before continuing by performing one of the following options: v If you did not use previous steps in this procedure to check for serviceable events that include 10009xxx reference codes, return to step 1 on page 21 to do so now and perform problem analysis on any you find. If you do not find any problems, or need assistance, contact your next level of support. v If you did use previous steps in this procedure to check for serviceable events that include 10009xxx reference codes and did not find any, contact your next level of support for assistance. 6. To verify that there are no inactive expansion units in the SPCN, perform the following steps: a. Access the ASMI using an authority level of administrator or authorized service provider. For details on using the ASMI, see Managing the Advanced System Management Interface (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hby/asmi.htm). b. In the ASMI navigation area, expand System Configuration and select Configure I/O Enclosures. c. Scan for inactive expansion units by looking for rows that have the word Inactive in the Status column. If inactive expansion units exist, choose from the following options: v If you were sent here from the procedure to concurrently add expansion units and you have already added the expansion units, do not continue. Contact your service provider for assistance. v If the previous item about disconnecting the ac power cables does not apply to you, click the Clear inactive enclosures button on this panel. Wait for the completion indication, and repeat steps 6b and 6c. If inactive expansion units remain, do not continue. Contact your next level of support for assistance. 7. Correct any temporary machine type, model, and serial number (MTMS) values assigned to the expansion units connected to the system by completing the following steps: a. Access the ASMI using an authority level of administrator or authorized service provider. For details on using the ASMI, see Managing the Advanced System Management Interface (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hby/asmi.htm). b. In the ASMI navigation area, expand System Configuration and select Configure I/O Enclosures. c. Look for expansion units that have a location code of the form UTMPx.xxx.xxxxxxx, where x is any number 0 - 9 or character A - Z. For each row has that value in the Location code column, the associated expansion unit has temporary type, model, and serial number values that must be corrected. Correct these values by performing Setting I/O enclosure configuration ID and MTMS value (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ ipham_setconfigid.htm) starting at step 8 on page 24. 8. Return to the procedure that sent you here.

Setting I/O enclosure configuration ID and MTMS value

The configuration ID and the machine type, model, and serial number (MTMS) values are used by the system to identify and determine certain characteristics of an expansion unit. If these values are not set correctly, the system might not manage the expansion unit properly.

Power Systems: Enclosures and expansion units

To set the configuration ID, use the Advanced System Management Interface (ASMI). However if the ASMI is not available you can use the physical control panel to set the configuration ID. To set the MTMS value you must use the ASMI, not the control panel. However, if you do not have access to the ASMI, the system will still operate without updating this information. The MTMS value should match the original value of the enclosure, which can be found on a label affixed to the enclosure. Using the ASMI to verify and set the configuration ID and MTMS value: You can use the Advanced System Management Interface to verify and set the configuration ID and machine type, model, and serial number (MTMS) values for an expansion unit. To perform this operation, verify that the following prerequisites have been met: v The system must be powered on to firmware standby or firmware running state. v The expansion unit must have power and be correctly installed in the system power control network. v Your authority level must be one of the following: Administrator Authorized service provider 1. Login in to ASMI. 2. Expand System Configuration. 3. Click Configure I/O Enclosures Clear Inactive Enclosures. 4. If you were directed here from a part replacement procedure, the part that was replaced contained the nonvolatile storage where the expansion unit machine type, model, and serial number (MTMS) is stored. It is necessary to restore the expansion unit MTMS now. It might also be necessary to set or change the expansion unit configuration ID (power control network identifier). The nonvolatile storage where the expansion unit MTMS value is stored in a new replacement part is uninitialized. The system will detect the uninitialized value and assign an obvious, unique value of the form TMPx.xxx.xxxxxxx, where x can be any character in 0 - 9 or A - Z. As a result, the expansion unit location code will change to UTMPx.xxx.xxxxxxx. You must use the new UTMPx.xxx.xxxxxxx location code in the following instructions when you select the expansion unit to power off and select the expansion unit for settings changes. 5. From the ASMI utility, expand System Configuration. 6. Select Configure I/O Enclosures. 7. Verify the configuration ID and MTMS data by completing the following steps: a. Compare the power control network identifier value shown for the expansion unit you are working with to the power control network identifier (configuration ID) values in the following list: v 0x84 for 5096 and 5296 expansion units v 0x88 for 7311-D11 and 5790 expansion units v 0x89 for 5088 and 0588 expansion units v 0x8A for 5094, 5294, 5096, and 5296 expansion units v 0x8B for 5095 and 0595 expansion units v 0x8C for 7311-D20 expansion units v 0x8D for 7314-G30 and 5796 expansion units v 0x8E for 5802 and 5877 expansion units b. Compare the values shown on the Type-Model and Serial number columns for the expansion unit you are working with to the type, model, and serial values on the label located on the expansion unit. The expansion unit location code displayed in the Location code column will be either UTMPx.xxx.xxxxxxx, where x is any character in 0 - 9 or A - Z, or UTTTT.MMM.SSSSSSS, where TTTT, MMM, and SSSSSSS are the enclosure type (TTTT), model (MMM), and serial number (SSSSSSS).
Connecting and configuring I/O expansion units

Notes: v A 10009132 informational log is produced during an initial program load (IPL), or when an expansion unit is added concurrently if a temporary MTMS was assigned to an expansion unit. The temporary MTMS will cause the expansion unit to have a location code of UTMPx.xxx.xxxxxxx, where x is any character in 0 - 9 or A - Z. c. If any changes must be made, go to step 8. Otherwise, go to step 18 on page 25. 8. If the system is powered on to the firmware running state, go to step 9. If the system is powered on to the firmware standby state, go to step 10. 9. Choose from the following options: v If the configuration ID must be changed, perform the following steps: a. Read the following notes. b. Power off the I/O expansion unit. c. Go to step 10. v If the MTMS data must be changed and any of expansion unit resources are owned by active system partitions that are running the AIX or Linux operating system, perform the following steps: a. Read the following notes. b. Power off the I/O enclosure. c. Go to step 10. v If neither of the above statements apply, go to step 10. Notes: v Do not disconnect the power cables after powering off the expansion unit. v If the expansion unit is not immediately displayed on the service utility that is used to power off the expansion unit, refresh the utility periodically for up to 10 minutes until it does. If it still is not displayed, go to step 1 on page 23 and repeat this procedure. v If you were directed here from a part replacement procedure, remember to use the new UTMPx.xxx.xxxxxxx location code when you select the expansion unit to power off. v If the procedure that directed you here involved powering off the expansion unit and while powering off the expansion unit you were instructed to use panel function 69 to power on the expansion unit, perform panel function 69 now (with the control panel set to manual mode) from the control panel of the logical partition where you were instructed to use panel function 69. Do this even though the expansion unit is already on. 10. From the ASMI utility, expand System Configuration. 11. Click Configure I/O Enclosure the expansion you are working with Change settings. 12. If in step 7 on page 23 you determined that the power control network identifier (configuration ID) value was not correct, enter the correct value now. 13. If in step 7 on page 23 you determined that the Type-Model and Serial number values were not correct, enter the correct values now. Note: Serial numbers are case-sensitive. All alphabetic characters contained in the serial number must be entered as a capital letter. 14. Click Save settings to complete the operation. 15. Verify that the values you just entered are reflected in the Power Control Network Identifier, Type-Model, Serial number, and Location code columns for the expansion unit you are working with by expanding System Configuration Configure I/O Enclosures. Do not use the Back button to do this. 16. If the system is powered on to firmware standby state and you entered a new power control network identifier (Configuration ID) in step 12, the expansion unit will power off and back on automatically. If this is the case, go to step 18 on page 25. Otherwise, go to step 17 on page 25.

Power Systems: Enclosures and expansion units

17. If you powered off the expansion unit in step 9 on page 24, read the following notes to power on the expansion unit. Notes: v If the system is not managed by an HMC, disconnect all power to the expansion unit by disconnecting the cables from the power supplies on the expansion unit. Wait for the power indicator light on the expansion unit control panel to go off, wait an additional 30 seconds, and then reconnect the power cables. The expansion unit will power on automatically. v If the system is managed by an HMC, power on the expansion unit by using the Serviceability Hardware Power On/Off Unit task on the HMC. If the values you just entered are not immediately reflected in the location code of the expansion unit in the Power On/Off Unit task, restart the task periodically for up to 10 minutes until the values you entered are reflected. 18. Log off and close the ASMI. 19. Return to the procedure that sent you here.

Updating the SPCN firmware

The system power control network (SPCN) firmware update is required but is not started automatically due to the current SPCN firmware update policy. Therefore, the SPCN firmware update must be started manually. Notes: v Do not perform maintenance on an expansion unit or change the SPCN network while the SPCN firmware update is being performed. v If you power off the system while performing firmware updates, the SPCN firmware update is interrupted and must be restarted. v This procedure can take several hours depending on the number of expansion units on the SPCN loop and the current level of the SPCN firmware on the expansion units that will be updated. To change the SPCN firmware update policy to expanded and start an SPCN firmware update, perform the following steps: 1. Access the Advanced System Management Interface (ASMI). 2. Click System Configuration Configure I/O Enclosures. 3. Record the current SPCN Firmware Update Policy setting so that it can be restored later. 4. Change the SPCN Firmware Update Policy setting to Expanded, and click Save Policy Setting to allow SPCN firmware updates to be performed over the serial SPCN interfaces. 5. Click Start SPCN Firmware Update. The SPCN firmware is then downloaded to the expansion units that require an update. 6. Change the SPCN Firmware Update Policy setting back to the setting that was recorded in step 3, and click Save Policy Setting. Notes: v To monitor the progress of the SPCN firmware update, click Configure I/O Enclosures. The window is refreshed. Do not use the browser Back or Refresh button to monitor the update progress. The Power Control Network Firmware Update Status column shows the percentage completed, and In Progress is displayed while the download operation is in progress. Not Required is displayed when the download process is completed. v To stop the SPCN firmware update (not recommended), click Stop SPCN Firmware Update.

Removing an expansion unit

Learn about removing an expansion unit from a system unit concurrently or nonconcurrently.
Connecting and configuring I/O expansion units

You can remove expansion units from a system with the system powered on and running (concurrently), or with the system powered off (nonconcurrently), depending on your situation.

Removing an expansion unit concurrently

Learn about removing an I/O expansion unit from a system unit concurrently. Perform the following tasks before beginning this procedure: v Record the time that you start the procedure. You need to reference this time later during error log analysis. v If you are planning to print this topic to perform the procedure, also print the SPCN and 12X diagrams. For details, see Examples: 12X and 12X DDR SPCN connections and Examples: 12X and 12X DDR expansion unit connections. v Before performing any procedure that involves changes to the 12X cabling or configuration for a system that is managed by an HMC, obtain a record that identifies for each expansion unit which I/O buses exist in that expansion unit. To acquire this information, use one of the following methods: From an HMC, select the managed system and then select the Properties task. From the HMC command line, enter the command lshwres r io rsubtype bus m <managed system>. Important: Be aware of the following items when you are removing an expansion unit: v Concurrent I/O expansion unit removal is supported only on Power 570 systems running firmware level EM350 and Power 595 systems running firmware level EH350. v Concurrent I/O expansion unit removal is supported only for 12X-attached I/O expansion units. v Concurrent I/O expansion unit removal is supported only on systems that are managed by a Hardware Management Console (HMC). v An I/O expansion unit that is concurrently removed from a system by using these procedures and then later added back to the system configuration either concurrently or nonconcurrently is assigned new bus numbers when it is added back to the configuration. v Concurrent removal of I/O expansion units must be done one expansion unit at a time. If multiple expansion units are to be removed concurrently, the procedure must be done separately for each one. Use the following steps to remove an I/O expansion unit from the system configuration. 1. Verify the existing 12X configuration. For details, see Verifying the 12X loops with an HMC on page 19. If problems occur with the 12X configuration, they must be corrected before continuing with the expansion unit removal procedure. 2. Verify the existing system power control network (SPCN) configuration using the Advanced System Management Interface (ASMI). For details, see Verifying the system power control network (SPCN) on page 21. If problems with the SPCN configuration occur, they must be corrected before continuing with the expansion unit removal procedure. 3. Optional: Identify the expansion unit that you want to remove. Select the Operations LED Status Identify LED task for the managed system from which the expansion unit is being removed to activate and deactivate identify indicators. Note: The identify indicators (LEDs) can help you verify the physical enclosure. 4. Select from the following options: v If the system is not in manufacturing default configuration (MDC), continue with step 5 v If the system is in manufacturing default configuration (MDC), continue with step 7 on page 27. 5. Ensure that none of the I/O resources in the expansion unit that is to be removed are owned by active logical partitions by doing one of the following actions: v Use dynamic logical partitioning (DLPAR) to dynamically remove I/O resources in the expansion unit from active partitions, if necessary.

Power Systems: Enclosures and expansion units

v Power off logical partitions that own I/O resources in the expansion unit. 6. Remove all I/O resources in the expansion unit that is to be removed from logical partition profiles. Note: Failure to complete this step can produce messages when a profile that includes resources in an expansion unit that was removed is activated or edited. When such a profile is activated or edited, the HMC presents a message about missing resources. At that time the option to have the HMC automatically remove the missing resources from the profile is shown. 7. Power off the expansion unit that is to be removed by performing the following steps: a. Select the managed system, Serviceability Hardware Power On/Off Unit. b. In the Power On/Off Unit window, expand the managed system and select the expansion unit that is to be removed. c. Click the Power Off button and follow the instructions on the HMC until the expansion unit is powered off. 8. Remove ac power from the expansion unit that is to be removed by disconnecting the ac cables from the power supplies on the expansion unit. 9. Familiarize yourself with the SPCN cabling rules. For SPCN cabling examples, see Examples: 12X and 12X DDR SPCN connections. 10. Perform the following steps: a. Remove the SPCN cable between the T1 connector on the expansion unit that is to be removed and the corresponding connector on the preceding unit on the SPCN loop. Note: The preceding unit on the SPCN loop could be another expansion unit or a system unit. b. Disconnect the SPCN cable from the T2 connector on the expansion unit that is to be removed and attach it to the connector on the preceding unit on the SPCN loop that was opened in the previous step. 11. Familiarize yourself with the 12X cabling rules. For 12X cabling examples, see Examples: 12X connections on page 10. 12. Choose from the following options. To remove an expansion unit from a 12X loop that has only one expansion unit, continue with step 13. v To remove an expansion unit from the beginning of a 12X loop, continue with step 14. v To remove an expansion unit from the middle of a 12X loop, continue with step 15 on page 28. v To remove an expansion unit from the end of a 12X loop, continue with step 16 on page 28. 13. To remove an expansion unit from a 12X loop with only one expansion unit, complete the following steps. a. Remove the 12X cable between connector T1 on the system unit and connector T1 on the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T2 on the expansion unit that is to be removed and attach it to connector T1 on the system unit. v Important: This step creates a 12X loop with no expansion units on it. The 12X cable runs between connectors T1 and T2 on the system unit. Do not skip this step. It is necessary to allow system firmware to complete the removal process. c. Wait 2 minutes. d. Remove the 12X cable between connectors T1 and T2 on the system unit. e. Continue with step 17 on page 28. 14. To remove an expansion unit from the beginning of a 12X loop, complete the following steps. a. Remove the 12X cable between connector T1 on the system unit and connector T1 on the expansion unit that is to be removed.

Connecting and configuring I/O expansion units

b. Disconnect the 12X cable from connector T2 on the expansion unit that is to be removed and attach it to connector T1 on the system unit. c. Continue with step 17. 15. To remove an expansion unit from the middle of a 12X loop, complete the following steps. a. Remove the 12X cable between connector T1 on the expansion unit that is to be removed and connector T2 on the expansion unit that precedes the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T2 on the expansion unit that is to be removed and attach it to connector T2 on the expansion unit that precedes the expansion unit that is to be removed. c. Continue with step 17. 16. To remove an expansion unit from the end of a 12X loop, complete the following steps. a. Remove the 12X cable between connector T2 on the system unit and connector T2 on the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T1 on the expansion unit that is to be removed and attach it to connector T2 on the system unit. c. Continue with step 17. 17. Clear the inactive enclosure record for the expansion unit that was removed. a. Access the ASMI from the HMC: Select Operations Launch Advanced System Management (ASM) task for the managed system from which the expansion unit is being removed. 1) In the navigation pane, select System Management Servers. 2) In the contents pane, select the system that has the expansion unit you want to remove. 3) Select Tasks Launch Advanced Systems Management (ASM). b. Log in to ASMI with administrator or authorizes service provider authority. c. Expand System Configuration. d. Click Configure I/O Enclosures Clear inactive enclosures. 18. Repeat step 1 on page 26 to verify the 12X configuration. Note: While concurrently removing an expansion unit, it is normal for error logs and event logs to be created with the following reference codes. The number and combination of these logs is dependent on the configuration. The logs can be ignored during this verification step if their timestamps indicate that they occurred during the removal procedure and if the resources that they refer to were involved in the procedure. v B7006981 permanent reference code indicates a 12X adapter failure v v B7006982 permanent reference code indicates 12X link failure B7006984 informational reference code indicates an open 12X loop

v B7006985 informational reference code indicates the 12X loop was closed v B70069E6 informational reference code indicates a 12X link stopped v B70069E7 informational reference code indicates a 12X link started 19. Repeat step 2 on page 26 to verify the SPCN configuration. Note: While concurrently removing an expansion unit, it is normal for error logs and event logs to be created with the following reference codes. The number and combination of these logs is dependent on the configuration. The logs can be ignored during this verification step if their timestamps indicate that they occurred during the removal procedure and if the resources that they refer to were involved in the procedure. v 100090F0 permanent reference code indicates an expansion unit was dropped from the power control network v v 10009135 informational or permanent reference code indicates an open SPCN loop 10009137 permanent reference code indicates disruption of the 12X loop

Power Systems: Enclosures and expansion units

v 10009139 informational reference code indicates the SPCN loop was closed 20. Check for new serviceable events that were generated during the removal procedure by performing the following steps: a. Select the managed system, then select Serviceability Manage Serviceable Events. b. In the Manage Serviceable Events window, specify event criteria that will include any events that were generated during the procedure. Using the default criteria will work as well. c. Click OK when you have specified the criteria you want for the serviceable events you want to view. A table appears with the serviceable events that match your criteria. d. You can close any serviceable events generated during the procedure that include one of the reference codes identified in step 18 on page 28 or 19 on page 28 and call out resources involved in the procedure, such as the expansion unit that was removed, should be closed. e. Perform standard problem analysis on any remaining open serviceable events generated during the procedure. The expansion unit is now removed from the system configuration. 21. Physically remove the expansion unit from the rack.

Removing an expansion unit nonconcurrently

Learn about removing an I/O expansion unit from a system unit nonconcurrently with the system powered off. Be aware of the following items when you are removing an expansion unit: v If you are planning to print this topic to perform the procedure, also print the SPCN and 12X diagrams. For details, see Examples: 12X and 12X DDR SPCN connections and Examples: 12X and 12X DDR expansion unit connections. v Before performing any procedure that involves changes to the 12X cabling or configuration for a system that is managed by an HMC, obtain a record that identifies for each expansion unit which I/O buses exist in that expansion unit. To acquire this information, use one of the following methods: From an HMC, select the managed system and then select the Properties task. From the HMC command line, enter the command lshwres r io rsubtype bus m <managed system>. Use the following steps to remove an I/O expansion unit from the system configuration that has the system powered off. 1. If the system is powered on, power it off. 2. Remove ac power from the expansion unit that is to be removed by disconnecting the ac cables from the power supplies on the expansion unit. 3. Familiarize yourself with the SPCN cabling rules. For SPCN cabling examples, see Examples: 12X and 12X DDR SPCN connections. 4. Perform the following steps: a. Remove the SPCN cable between the T1 connector on the expansion unit that is to be removed and the corresponding connector on the preceding unit on the SPCN loop. Note: The preceding unit on the SPCN loop could be another expansion unit or a system unit. b. Disconnect the SPCN cable from the T2 connector on the expansion unit that is to be removed and attach it to the connector on the preceding unit on the SPCN loop that was opened in the previous step. 5. Familiarize yourself with the 12X cabling rules. For 12X examples, see Examples: 12X connections on page 10.

Connecting and configuring I/O expansion units

Note: Some hardware might not have labels for the 12X connectors, or it might have labels other than T1/T2, such as 0/1 or 1/2. In those cases, the top connector corresponds to T1 and the bottom connector corresponds to T2. 6. Choose from the following options. v To remove an expansion unit from a 12X loop that has only one expansion unit, continue with step 7. v To remove an expansion unit from the beginning of a 12X loop, continue with step 8. v To remove an expansion unit from the middle of a 12X loop, continue with step 9. v To remove an expansion unit from the end of a 12X loop, continue with step 10. 7. To remove an expansion unit from a 12X loop with only one expansion unit, complete the following steps. a. Remove the 12X cable between connector T1 on the system unit and connector T1 on the expansion unit that is to be removed. b. Remove the 12X cable between connector T2 on the system unit and connector T2 on the expansion unit that is to be removed. c. Continue with step 11. 8. To remove an expansion unit from the beginning of 12X loop, complete the following steps. a. Remove the 12X cable between connector T1 on the system unit and connector T1 on the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T2 on the expansion unit that is to be removed and attach it to connector T1 on the system unit. c. Continue with step 11. 9. To remove an expansion unit from the middle of a 12X loop, complete the following steps. a. Remove the 12X cable between connector T1 on the expansion unit that is to be removed and connector T2 on the expansion unit that precedes the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T2 on the expansion unit that is to be removed and attach it to connector T2 on the expansion unit that precedes the expansion unit that is to be removed. c. Continue with step 11. 10. To remove an expansion unit from the end of a 12X loop, complete the following steps. a. Remove the 12X cable between connector T2 on the system unit and connector T2 on the expansion unit that is to be removed. b. Disconnect the 12X cable from connector T1 on the expansion unit that is to be removed and attach it to connector T2 on the system unit. c. Continue with step 11. 11. Physically remove the expansion unit from the rack. 12. Power on the system but do not start partitions. 13. Check for new serviceable events that were created since starting the system: v If the system is managed by an HMC, complete the following steps to check for new serviceable events. a. Select the managed system Serviceability Manage Serviceable Events. b. In the Manage Serviceable Events window, click OK to accept the default criteria. A table appears with the serviceable events that match the criteria. Continue with step 14. v If the system is not managed by an HMC, use the serviceable event log tool in the operating system to check for new serviceable events. Continue with step 14. 14. Perform standard problem analysis on any open serviceable events that were created since starting the system. 15. Start the logical partitions.

Power Systems: Enclosures and expansion units

Common procedures for expansion units

These procedures are used throughout the expansion unit topic.

Verifying that the new configuration is functioning

Use the procedures in this section to verify that the new configuration is correctly functioning. 1. Choose from the following options: v If your system is not managed by an HMC, see http://publib.boulder.ibm.com/infocenter/ systems/scope/hw/topic/p7haj/p7hajhsmverify.htm (http://publib.boulder.ibm.com/infocenter/ systems/scope/hw/topic/p7haj/p7hajhsmverify.htm). When you are finished, return to the procedure that sent you here. v If your system is managed by an HMC, continue with step 2 on page 18. 2. To view more information about the managed system, complete the following steps: a. From the navigation area of the HMC, expand Systems Management. b. Click Servers. c. Select the system with which you want to work. Information about the system is shown under the Tasks section in the contents area. 3. View the properties of the managed system and verify the new expansion units by doing the following: a. b. c. d. Select the server for which you want to verify the configuration. Click Tasks Properties. Select the I/O tab. Verify that the new expansion units are displayed in the list. It might take several minutes for the new expansion units to be displayed in the list. Tip: To refresh the list of expansion units, you must repeat step 3b on page 18 and step 3c on page 18. It is not necessary to exit the Properties task before launching again, but doing so reduces the number of active HMC tasks. If the I/O Properties panel does not display the new expansion units after 10 minutes, verify the installation by performing the following steps: 1) Make sure that the expansion units are powered on and the power cables are connected to the power source and the expansion units. 2) Make sure that the 12X cables are connected correctly. For details, see Connecting expansion units with 12X cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ p7ham/direct.htm). 3) Make sure that the SPCN cables are connected correctly. For details, see Connecting expansion units with SPCN cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ p7ham/spcndirect.htm). 4) Make sure you verified the MTMS and Configuration ID of the new expansion units. For details, see Setting I/O enclosure configuration ID and MTMS value (http:// publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/ipham_setconfigid.htm). 5) If the expansion units still are not displayed, contact your next level of support for assistance. 4. Return to the procedure that sent you here.

Starting the system or logical partition

Learn how to start a system or logical partition after performing a service action or system upgrade.

Starting a system that is not managed by a Hardware Management Console

You can use the power button or the Advanced System Management Interface to start a system that is not managed by a Hardware Management Console.
Connecting and configuring I/O expansion units

To start a system that is not managed by a Hardware Management Console (HMC), follow these steps: 1. Open the front rack door, if necessary. 2. Before you press the power button on the control panel, ensure that power is connected to the system unit as follows: v All system power cables are connected to a power source. v The power-on light, as shown in the following figure, is slowly blinking. v The top of the display, as shown in the following figure, shows 01 V=F. 3. Press the power button (A), as shown in the following figure, on the control panel.

Figure 14. Control panel

v A: Power-on button v B: Power LED A constant light indicates full system power to the unit. A blinking light indicates standby power to the unit. Note: There is approximately a 30-second transition period from the time the power-on button is pressed to when the power LED goes from blinking to solid. During the transition period, the LED might blink faster. v C: Enclosure identify light A constant light indicates the identify state, which is used to identify a part. No light indicates that the system is operating normally. v D: Attention light No light indicates that the system is operating normally. A blinking light indicates that the system requires attention. v E: USB port v F: Enclosure fault roll-up light A constant light indicates a fault in the system. No light indicates that the system is operating normally.

Power Systems: Enclosures and expansion units

v v v v v

G: Function/Data display H: Decrement button I: Enter button J: Increment button K: Pinhole reset button

4. Observe the following after pressing the power button: v The power-on light begins to blink faster. v The system cooling fans are activated after approximately 30 seconds and begin to accelerate to operating speed. v Progress indicators, also referred to as checkpoints, appear on the control panel display while the system is being started. The power-on light on the control panel stops blinking and remains on, indicating that system power is on. Tip: If pressing the power button does not start the system, do the following steps to start the system using the Advanced System Management Interface (ASMI): 1. Access the ASMI. For instructions, see Accessing the ASMI. 2. Start the system using the ASMI. For instructions, see Powering the system on and off.

Starting a system or logical partition by using the Hardware Management Console

You can use the Hardware Management Console (HMC) user interface to start the system or logical partition after the required cables are installed and the power cables are connected to a power source. For instructions on working with the HMC, see Managing the Hardware Management Console. For instructions on starting a logical partition, see Logical partitioning. For instructions on starting the system, see Powering on the managed system. Progress indicators, also referred to as checkpoints, appear on the control panel display while the system is being started. When the power-on light on the control panel stops blinking and remains on, the system power is on.

Stopping a system or logical partition

Learn how to stop a system or logical partition as a part of a system upgrade or service action. Attention: Using either the power-on button on the control panel or entering commands at the Hardware Management Console (HMC) to stop the system can cause unpredictable results in the data files. Also, the next time you start the system, it might take longer if all applications are not ended before stopping the system. To stop the system or logical partition, select the appropriate procedure. Related tasks Shutting down logical partitions using the Integrated Virtualization Manager Use this procedure to shut down a logical partition or the entire managed system that is managed using the Integrated Virtualization Manager.

Stopping a system that is not managed by a Hardware Management Console

You might need to stop the system to perform another task. Use these instructions to stop the system using the power button or Advanced System Management Interface. Before you stop the system, follow these steps: 1. If an Integrated xSeries Adapter (IXA) is present on the system, shut it down using IBM i options. 2. Ensure that all jobs are completed and end all applications. 3. Ensure that the operating system is stopped.
Connecting and configuring I/O expansion units

Attention: Failure to do so can result in the loss of data. 4. If a Virtual I/O Server (VIOS) logical partition is running, ensure that all clients are shut down or that the clients have access to their devices using an alternate method. The following procedure describes how to stop a system that is not managed by a Hardware Management Console (HMC). 1. Log in to the system as a user with the authority to run the shutdown or pwrdwnsys (Power Down System) command. 2. At the command line, enter one of the following commands: v If your system is running the AIX operating system, type shutdown. v If your system is running the Linux operating system, type shutdown -h now. v If your system is running the IBM i operating system, type PWRDWNSYS. If your system is partitioned, use the PWRDWNSYS command to power down each of the secondary partitions. Then, use the PWRDWNSYS command to power down the primary partition. The command stops the operating system. The system power turns off, the power-on light begins to slowly flash, and the system goes into a standby state. 3. Record the IPL type and the IPL mode from the control panel display to help you return the system to this state when the installation or replacement procedure is completed. 4. Set the power switches of any devices connected to the system to off. 5. Unplug any power cables that are attached to the unit from electrical outlets. Ensure that you unplug power cables from peripheral devices, such as printers and expansion units. Important: The system is equipped with a second power supply. Before continuing with this procedure, ensure that all power sources to the system have been disconnected. (L003)

Power Systems: Enclosures and expansion units

Stopping a system by using the Hardware Management Console

You can use the Hardware Management Console (HMC) user interface to stop the system or a logical partition. Use the following steps to accomplish this task. By default, the managed system is set to power off automatically when you shut down the last running logical partition on the managed system. If you set the managed system properties on the HMC so that the managed system does not power off automatically, you must use this procedure to power off your managed system. Attention: If possible, shut down the running logical partitions on the managed system before powering off the managed system. Powering off the managed system without shutting down the logical partitions first causes the logical partitions to shut down abnormally and can cause data loss. If you use a Virtual I/O Server (VIOS) logical partition, ensure that all clients are shut down or that the clients have access to their devices using an alternate method. To power off a managed system, you must be a member of one of the following roles: v Super administrator v Service representative v Operator v Product engineer 1. In the Navigation area, expand the Systems Management folder. 2. Click the Servers icon. 3. In the Contents area, select the managed system. 4. Select Tasks, then Operations, and then Power Off 5. Select the appropriate power-off mode and click OK. Related information Shutting down and restarting logical partitions

Identifying a failing part

Use these instructions to learn how to locate and identify a failing part on your system or expansion unit using the appropriate method for your system. For IBM Power Systems servers that contain the POWER7 processor, the light-emitting diodes (LEDs) can be used to identify or verify a part that you are servicing. The fault (amber) LED indicates an error and corresponds to the location code in the system reference code (SRC). The LED is activated and deactivated automatically. If you need to use the identify function, use the following procedures.

Identifying a failing part in an AIX system or logical partition

Use these instructions to learn how to locate a failing part, and then activate the indicator light for that part on a system or logical partition running the AIX operating system. Locating a failing part in an AIX system or logical partition: You might need to use AIX tools, before activating the indicator light, to locate a part that is failing. 1. Log in as root user or celogin-. 2. At the command line, type diag and press Enter. 3. From the Function Selection menu, select Task Selection and press Enter. 4. Select Display Previous Diagnostic Results and press Enter.
Connecting and configuring I/O expansion units

5. From the Display Previous Diagnostic Results display, select Display Diagnostic Log Summary. The Display Diagnostic Log display shows a chronological list of events. 6. Look in the T column for the most recent S entry. Select this row in the table and press Enter. 7. Select Commit. The details of this log entry are shown. 8. Record the location information and the SRN value shown near the end of the entry. 9. Exit to the command line. Use the location information for the failing part to activate the indicator light that identifies the failing part. Activating the indicator light for the failing part. Activating the indicator light for the failing part: Use these instructions to help physically identify the location of a part you are servicing. 1. Log in as root user. 2. At the command line, type diag and press Enter. 3. From the Function Selection menu, select Task Selection and press Enter. 4. From the Task Selection menu, select Identify and Attention Indicators and press Enter. 5. From the list of lights, select the location code for the failing part and press Enter. 6. Select Commit. This turns on the system attention and indicator light for the failing part. 7. Exit to the command line.

Identifying a failing part in an IBM i system or logical partition

You can activate or deactivate the indicator light by using IBM i to assist in locating a failing part. Activating the failing-part indicator light: You can search the service action log for an entry that matches the time, reference code, or resource of a problem, and then activate the indicator light for a failing part. 1. Sign on to an IBM i session, with at least service level authority. 2. On the command line of the session, type strsst and press Enter. Note: If you cannot get to the System Service Tools display, use function 21 from the control panel. Alternatively, if the system is managed by a Hardware Management Console (HMC), use the Service Focal Point utilities to get to the Dedicated Service Tools (DST) display. 3. Type your service tools user ID and service tools password on the System Service Tools (SST) Sign On display. Press Enter. Remember: The service tools password is case-sensitive. Select Start a service tool from the System Service Tools (SST) display and press Enter. Select Hardware service manager from the Start a Service Tool display and press Enter. Select Work with service action log from the Hardware Service Manager display and press Enter. On the Select Timeframe display, change the From: Date and Time field to a date and time prior to when the problem occurred. Search for an entry that matches one or more conditions of the problem: v System Reference code v Resource v Date and time v Failing item list

4. 5. 6. 7. 8.

9. Select option 2 (Display failing item information) to display the service action log entry.

Power Systems: Enclosures and expansion units

10. Select option 2 (Display details) to display location information for the failing part to be replaced. The information displayed in the date and time fields is the date and time for the first occurrence of the specific System reference code for the resource displayed during the time range selected. 11. If location information is available, select option 6 (Indicator on) to turn on the failing part's indicator light. Tip: If the failing part does not contain a physical indicator light, a higher-level indicator light is activated. For example, the indicator light for the backplane or unit that contains the failing part might be lit. In this case, use the location information to locate the actual failing part. 12. Look for the enclosure indicator light to locate the enclosure that contains the failing part. Deactivating the failing-part indicator light: Use this procedure to turn off any indicator light that you turned on as a part of a service action. To deactivate the indicator light, follow these steps: 1. Sign on to an IBM i session, with at least service level authority. 2. On the command line of the session, type strsst and press Enter. Note: If you cannot get to the System Service Tools display, use function 21 from the control panel. Alternatively, if the system is managed by a Hardware Management Console (HMC), use the Service Focal Point utilities to get to the Dedicated Service Tools (DST) display. 3. Type your service tools user ID and service tools password on the System Service Tools (SST) Sign On display. Press Enter. Remember: The service tools password is case-sensitive. 4. Select Start a service tool from the System Service Tools (SST) display and press Enter. 5. Select Hardware service manager from the Start a Service Tool display and press Enter. 6. Select Work with service action log from the Hardware Service Manager display and press Enter. 7. On the Select Timeframe display, change the From: Date and Time field to a date and time prior to when the problem occurred. 8. Search for an entry that matches one or more conditions of the problem: v System Reference code v Resource v Date and time v Failing item list Select option 2 (Display failing item information) to display the service action log entry. Select option 2 (Display details) to display location information for the failing part to be replaced. The information displayed in the date and time fields is the date and time for the first occurrence of the specific System reference code for the resource displayed during the time range selected. Select option 7 (Indicator off) to turn off the indicator light. Select the Acknowledge all errors function at the bottom of the Service Action Log display, if all problems have been resolved.

9. 10.

11. 12.

13. Close the log entry by selecting option 8 (Close new entry) on the Service Action Log Report display.

Identifying a failing part in a Linux system or logical partition

If the service aids have been installed on a system or logical partition, you can activate or deactivate the indicator lights to locate a part or compete a service action. Locating a failing part in a Linux system or logical partition:

Connecting and configuring I/O expansion units

If the service aids have been installed on a system or logical partition, you need to activate the indicator lights to locate a part. To 1. 2. 3. activate the indicator light, follow these steps: Log in as root user. At the command line, type /usr/sbin/usysident -s identify -l<location code> and press Enter. Look for the system attention light to identify the enclosure that contains the failing part.

Related information Service and productivity tools for Linux on POWER systems IBM provides hardware diagnostic aids and productivity tools, as well as installation aids for Linux operating systems on IBM Power systems. Finding the location code of a failing part in a Linux system or logical partition: To retrieve the location code of the failing part, if you do not know the location code, use the procedure in this topic. To locate the failing part in a system or logical partition follow these steps: 1. Log in as root user. 2. At the command line, type grep diagela /var/log/platform and press Enter. 3. Look for the most recent entry that contains a system reference code (SRC). 4. Record the location information. Note: IBM provides hardware diagnostic aids and productivity tools, as well as installation aids for Linux operating systems on IBM Power systems. See Service and productivity tools for Linux on POWER systems Activating the indicator light for the failing part: If you know the location code of the failing part, activate the indicator light to help you locate which part to replace. To activate the indicator light, follow these steps: 1. Log in as root user. 2. At the command line, type /usr/sbin/usysident -s identify -l<location code> and press Enter. 3. Look for the system attention light to identify the enclosure that contains the failing part. Note: IBM provides hardware diagnostic aids and productivity tools, as well as installation aids for Linux operating systems on IBM Power systems. See Service and productivity tools for Linux on POWER systems Deactivating the failing-part indicator light: After you complete a removal and replacement procedure, you must deactivate the failing-part indicator light. To deactivate the indicator light, follow these steps: 1. Log in as root user. 2. At the command line, type /usr/sbin/usysident -s normal -l<location code> and press Enter.

Power Systems: Enclosures and expansion units

Note: IBM provides hardware diagnostic aids and productivity tools, as well as installation aids for Linux operating systems on IBM Power systems. See Service and productivity tools for Linux on POWER systems

Locating a failing part in a Virtual I/O Server system or logical partition

You can use Virtual I/O Server (VIOS) tools, before activating the indicator light, to locate a part that is failing. 1. Log in as root user or celogin-. 2. At the command line, type diagmenu and press Enter. 3. From the Function Selection menu, select Task Selection and press Enter. 4. Select Display Previous Diagnostic Results and press Enter. 5. From the Display Previous Diagnostic Results display, select Display Diagnostic Log Summary. A Display Diagnostic Log display appears. This display contains a chronological list of events. 6. Look in the T column for the most recent S entry. Select this row in the table and press Enter. 7. Choose Commit. The details of this log entry are shown. 8. Record the location information and the SRN value shown near the end of the entry. 9. Exit to the command line. Use the location information for the failing part to activate the indicator light that identifies the failing part. For instructions, see Identifying a part by using the Virtual I/O Server. Identifying a part by using the Virtual I/O Server: Use these instructions to turn on the indicator light to help you physically locate a part by using the Virtual I/O Server (VIOS). 1. Log in as root user. 2. At the command line, type diagmenu and press Enter. 3. From the Function Selection menu, select Task Selection. Press Enter. 4. From the Task Selection menu, select Identify and Attention Indicators. Press Enter. 5. From the list of lights, select the location code for the failing part and press Enter. 6. Select Commit. This turns on the system attention and indicator light for the failing part. 7. Exit to the command line.

Connecting and configuring I/O expansion units

Power Systems: Enclosures and expansion units

Connecting and configuring disk drive enclosures

Use this information to learn about the cabling, SCSI addressing, and postconnection requirements for the disk drive enclosure.

Overview for disk drive enclosures

The disk drive subsystem is the portion of the expansion unit that houses and controls the disk drives.

5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure

Learn about the SCSI disk drive enclosure and how to assemble it. This SCSI disk drive enclosure can hold up 24 disk drives. The enclosure is organized into four groups, with each group containing six disk drive slots. The enclosure can be used as a stand-alone enclosure or a rack-mounted drawer. When connecting with your server, you can connect your SCSI cables to either a single-initiator repeater card or to a dual-initiator repeater card on your SCSI disk drive enclosure. The dual-initiator repeater card allows for high availability and combining groups of disk drive slots. To determine the level of software you need to support the SCSI disk drive enclosure, seeIBM Prerequisite. Notes: Before you connect the enclosure, read the following information. v You need to install the SCSI adapter that is used to connect the enclosure to your system. To view the PDF file of PCI adapters, approximately 40 MB in size, see . http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hak/p7hak.pdf v For systems or partitions with an AIX or Linux operating system, you need to have the SCSI adapter information for your operating system. This will be critical information for configuring the disks after you have attached the enclosure. You need to print the information before you begin the procedure. This information is available from the SCSI PCI Adapters (http://publib.boulder.ibm.com/infocenter/ pseries/v5r3/index.jsp?topic=/com.ibm.pseries.doc/hardware_docs/scsipciadapters.htm) Web site. v If you are going to configure RAID arrays, ensure that you have the following number of available disks for each RAID level: RAID 0 or 1 Two drives per array RAID 5 At least three drives per array RAID 6 At least four drives per array

Connecting the 5786, 5787, 7031-D24, or 7031-T24 to a system that has an AIX operating system
Use the information in this section to perform the cabling, SCSI addressing, and postconnection requirements for the disk drive enclosure. To connect the 5786, 5787, 7031-D24, or 7031-T24 to a system that has an AIX operating system, perform the following steps:
Copyright IBM Corp. 2010

1. Install the initiator repeater cards into the disk drive enclosure. For instructions, see SCSI repeater card on page 54. 2. Connect the SCSI cable to your repeater card. Choose one of the following methods based on your situation: v Single repeater cards or dual repeater cards: If you are using only single repeater cards or only dual repeater cards, install your SCSI cable (A) to the initiator repeater card (B) as shown in the following figure. v Single SCSI adapter connected to single repeater card: If, in this case, you are not sharing resources (disk drives), simply attach each SCSI cable to each repeater card.

Figure 15. SCSI cable to single repeater card

v Two SCSI adapters connected to dual repeater cards: If, in this case, you are sharing resources (disk drives) between systems or logical partitions, ensure that you understand the SCSI addressing and cabling order. For more information, see Connecting and configuring the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure in an AIX clustered environment on page 45.

Power Systems: Enclosures and expansion units

Figure 16. SCSI cable to a dual repeater card that is connected with two SCSI cards

v Four SCSI adapters connected to dual repeater cards: If, in this case, you are sharing resources (disk drives) between systems or logical partitions, ensure that you understand the SCSI addressing and cabling order. For more information, see Connecting and configuring the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure in an AIX clustered environment on page 45.

Figure 17. SCSI cable to a dual repeater card that is connected with four SCSI cards

v Single SCSI adapter connected to a combination of single and dual repeater cards: If, in this case, you are sharing resources (disk drives) between systems or logical partitions, ensure that you
Connecting and configuring disk drive enclosures

understand the SCSI addressing and cabling order. For more information, see Connecting and configuring the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure in an AIX clustered environment on page 45.

Figure 18. SCSI cable to a dual repeater card that is connected to a single repeater card

3. Use the information that you printed for the SCSI adapter to complete the configuration of your disk drives. For more information, see the SCSI PCI Adapters (http://publib.boulder.ibm.com/infocenter/ pseries/v5r3/index.jsp?topic=/com.ibm.pseries.doc/hardware_docs/scsipciadapters.htm) Web page and locate the file for the adapter that you are using to attach the enclosure to your system. Important: If you plan on using the disk enclosure in an AIX environment, it is critical that you set up an AIX CRON job so that if errors occur, they are reported to the attached system. The AIX CRON job needs to be set up during the initial installation. Note: Errors on disks in the enclosure are found without this CRON job (script) through normal automatic error log analysis; however, other errors such as fan and power supply problems in the enclosure can only be found when you run diagnostics manually, which is accomplished by using the following scripts. To collect enclosure errors, add the run_ses_healthcheck job to the system CRON table. Edit the system CRON by using the crontab -e command. At the bottom of that file, enter:
* 3 * * * /usr/lpp/diagnostics/bin/run_ses_healthcheck 1>/dev/null 2>/dev/null

This CRON runs the script run_ses_healthcheck daily at 3 a.m. The contents of the script depend on the configuration of the system to which the enclosure is attached. Example 1

Power Systems: Enclosures and expansion units

If the system to which the enclosure is attached either has a Hardware Management Console (HMC) or is running the Electronic Service Agent application, create a file named run_ses_healthcheck in the /usr/lpp/diagnostics/bin directory, with the following contents:
-----------------------------------------------------------------#!/bin/ksh #Name:run_ses_healthcheck #Location:/usr/lpp/diagnostics/bin #Function: SCSI SES hourly heathcheck for i in lsdev -Cc container -t ses -s scsi -F name -S available do diag -cd $i > /dev/null done #any registered "external notification" will be notified of errors #(such as HMC or Electronic Service Agent) ------------------------------------------------------------------

Note: On a logically partitioned system, it is only necessary to have the CRON job and script running on one partition that is associated with the enclosure, although it is acceptable to have the same CRON job and scripts on any partition that is associated with the enclosure. Example 2 If the system to which the enclosure is attached has no HMC and is not running the Electronic Service Agent application, create a file named run_ses_healthcheck in the /usr/lpp/diagnostics/bin directory, with the following contents:
-----------------------------------------------------------------------#!/bin/ksh #Name:run_ses_healthcheck #Location:/usr/lpp/diagnostics/bin #Function: SCSI SES hourly heathcheck for i in lsdev -Cc container -t ses -s scsi -F name -S available do diag -cd $i > /dev/null if [$? -ne 0] then /usr/lpp/diagnostics/bin/diagrpt -o >/tmp/ses.health.output #you might want to process the output prior to placing it in #a file #somhow notify the user of the error. A sample is shown #below. mail -s "7031 Health Check" root</tmp/ses.health.output rm /tmp/ses.health.output fi done ------------------------------------------------------------------------

Note: You can customize the actual notification in the script based on your preferences. These scripts send mail to the root user if errors need attention. You can modify the script if needed to inform certain users about the errors. In both examples, you have created the run_ses_healthcheck file. To make this command executable, type the following command at the AIX command prompt: chmod 544 /usr/lpp/diagnostics/bin/run_ses_healthcheck

Connecting and configuring the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure in an AIX clustered environment
Special considerations exist for connecting the disk drive enclosure in a clustered environment. The information in this section can help you meet these considerations. Gather and have available any planning and cabling documentation that you have for the system to which you are connecting in a clustered environment so that you can refer to it during this procedure.

Connecting and configuring disk drive enclosures

To assure that the SCSI disk drive enclosure is ready to be connected to the cluster, complete the following steps: 1. Ensure that each SCSI device that is connected to the shared SCSI bus has a unique ID. A common configuration is to set the SCSI ID of the adapters on the nodes to be higher than the SCSI IDs of the shared devices. (Devices with higher IDs take precedence in a SCSI bus contention.) v Use the command lscfg | grep scsi to determine and record the logical name of each adapter. In the command output, the first column lists the logical name of the SCSI adapter, such as + SCSI0. v Use the lscfg -vpl command and logical name of the adapter to record the I/O slot (physical slot) that each SCSI adapter uses, for example, lscfg -vpl scsi0, where scsi0is the logical name of the adapter. v Use the lsattr command, as in the following example, to find the ID of the adapter scsi0: lsattr -E -l scsi0 | grep id Note: Do not use wildcard characters or full path names on the command line for the device name designation. In the resulting output, the first column lists the attribute names. The integer to the right of the ID attribute is the adapter SCSI ID. 2. If a SCSI adapter address conflict exists, go to the next step. If no conflict exists, return to the SCSI connection method overview that referred you to this procedure. 3. Examine the cabling to see if the correct ports on the system are connected to the correct ports on the repeater cards on the disk drive enclosure. For example, if you are connecting the system using two host adapter cards and a dual repeater card as shown in the following figure, connect the systems as in the instructions that follow.

Figure 19. SCSI cable to a dual repeater card that is connected with two SCSI cards

4. Cable the first SCSI bus or set of shared disks by performing the following steps: a. Connect the bottom port of the adapter on Host A (SCSI address 7) to the exterior port on the repeater card in slot C2 on the enclosure. b. Connect the top port of the adapter on Host B (SCSI address 6) to the exterior port on the repeater card in slot C3 on the enclosure.

Power Systems: Enclosures and expansion units

This connection creates a set of shared disks and a shared SCSI bus (such as scsi0) between Host A and Host B. The important thing to consider at this point is that you connect the cables in descending order of the SCSI address on the host adapter. Connecting the cables in descending order of the host SCSI address reduces the potential for conflicting addresses. 5. Cable the second SCSI bus or set of shared disks by performing the following steps: a. Connect the bottom port of the adapter on Host B (SCSI address 7) to the interior port on the repeater card in slot C5 on the enclosure. b. Connect the top port of the adapter on Host A (SCSI address 6) to the interior port on the repeater card in slot C4 on the enclosure. This connection creates a set of shared disks and a shared SCSI bus (such as scsi1) between Host A and Host B. The important thing to consider at this point is that this is an independent SCSI bus or set of shared disks from the first set. Ensuring that you do not mistakenly connect one of the cables from either SCSI bus to another SCSI bus reduces the potential for conflicting SCSI addresses. Important: When adding, removing, or replacing SCSI adapters in host systems, you might want to disconnect the cabling at the enclosure first and reconnect the cabling to the enclosure last. This is because the new adapter SCSI ID default might be 7. You should ensure that the correct SCSI ID is set for the port you are cabling.

Connecting and configuring the disk drive enclosure in a system that has a Linux operating system
Use the information in this section to perform the cabling, SCSI addressing, and postconnection requirements for the disk drive enclosure. To connect and configure the disk drive enclosure in a system that has a Linux operating system, perform the following steps: 1. Install the initiator repeater cards into the disk drive enclosure. For instructions, see SAS RAID controller for AIX (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7hal/ scsirepeatcard.htm). 2. Connect the SCSI cable to your repeater card. Choose one of the following options based on your situation: v If you are using only single repeater cards or only dual repeater cards, connect your SCSI cable (A) to the initiator repeater card (B). For more details, see Figure 20 on page 48, Figure 21 on page 48, or Figure 22 on page 49, depending on your situation.

Connecting and configuring disk drive enclosures

Figure 20. SCSI cable to a single repeater card

Figure 21. SCSI cable to a dual repeater card that is connected with two SCSI cards

Power Systems: Enclosures and expansion units

Figure 22. SCSI cable to a dual repeater card that is connected with four SCSI cards

v If you are using a combination of single and dual repeater cards, connect a SCSI cable to the dual-initiator repeater card (A). Then, connect the dual repeater card (A) to the single repeater card (B) by using a different SCSI cable. For more information, see Figure 23 on page 50.

Connecting and configuring disk drive enclosures

Figure 23. SCSI cable to a dual repeater card that is connected to a single repeater card

3. Complete the SCSI cable connection process in this step. Important: The SCSI adapter or the system or partition must be powered off before making the connection in this step. Connect the other end of the SCSI cable (C) to the SCSI adapter (D) on the server. For more details, see Figure 24.

Figure 24. SCSI cable to a SCSI interface card

4. Add the disk drives to the operating system that you are using. See Installing PCI adapters.

Power Systems: Enclosures and expansion units

Important: If you plan on using the disk enclosure in a Linux environment, it is critical that you set up a Linux CRON job so that if errors exist, they are reported to the attached system. The Linux CRON job needs to be set up during the initial installation. 5. Set up the Linux CRON job during the initial installation of your SCSI disk drive enclosure. Perform the following tasks to ensure that your Linux CRON job is set up: a. Install the following RPMs from Service and productivity tools (http://www14.software.ibm.com/ webapp/set2/sas/f/lopdiags/home.html): v librtas v lsvpd v ppc64-utils v diagela b. If your logical partitions are managed by a Hardware Management Console (HMC), install the src, rsct.core.utils, rsct.core, csm.core, csm.client, and devices.chrp.base.ServiceRM packages in order to report errors to the HMC. Instructions for installing the packages are located at Service and productivity tools (http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html). Note: Errors on hard disks within the enclosure are not found using this CRON job. This diagnostic test is limited to reporting errors with the fans, power supplies, Vital Product Data (VPD) card, and repeater in the enclosure. c. To run enclosure diagnostics, add the diag_encl job to the system CRON table. As root user, edit the system CRON by using the crontab -e command. At the bottom of that file, enter:
* 3 * * * /usr/sbin/diag_encl -s 1>/dev/null 2>&1

The contents of the script depend on the configuration of the system to which the enclosure is attached. This CRON runs the diagnostic application diag_encl daily at 3 a.m. The application reads the contents of the /etc/diagela/diagela.config file to determine which applications have been registered to be notified of errors. To add additional notification methods or for more information, see that file. By default, the following notifications occur: v If the system is managed by an HMC, notifications are shown in the Manage Serviceable Events task on the HMC. If the system is not managed by an HMC, the root group is notified. v If the system has the Electronic Service Agent application installed, it is notified. v The error details are printed to the console, to the end of the /var/log/platform log file, and to the syslog file in /var/log/messages. Notes: 1) On a logically partitioned system, it is only necessary to have the CRON job on one partition that is associated with the enclosure. However, it is acceptable to have the same CRON job on all partitions. 2) The diag_encl application might run at any time to diagnose enclosures that are attached to the system.

Connecting and configuring the enclosure in a system with the IBM i operating system
If you are running the IBM i operating system, use this information to perform the cabling, SCSI addressing, and postconnection requirements for the disk drive enclosure. To connect and configure the disk drive enclosure in a system that has an IBM i operating system, perform the following steps: 1. Install the initiator repeater cards into the disk drive enclosure. For instructions, see SCSI repeater card on page 54.

Connecting and configuring disk drive enclosures

2. Connect the SCSI cable to your repeater card. Choose one of the following options based on your situation: Tip: Ensure that the cable length for connections across the enclosure are long enough to allow concurrent maintenance of disk drives. v If you are using only single repeater cards or only dual repeater cards, connect your SCSI cable (A) to the initiator repeater card (B).

Figure 25. SCSI cable to a single repeater card

Power Systems: Enclosures and expansion units

Figure 26. SCSI cable to a dual repeater card that is connected to a single repeater card

Figure 27. SCSI cable to a SCSI interface card

4. Add the disk drives to the operating system.

Connecting and configuring disk drive enclosures

SCSI repeater card

Learn about where to place and how to install the SCSI repeater card. Use the following figures and instructions to place your repeater cards.

Figure 28. Repeater card location of the 5786 and 7031-D24 SCSI disk drive enclosure (drawer models)

Power Systems: Enclosures and expansion units

Figure 29. Repeater card location of the 5787 and 7031-T24 SCSI disk drive enclosure (deskside models)

If you only have dual repeater cards, place them as follows: Important: On deskside models, the locations C3 and C5 are located on top, and C2 and C4 are located on the bottom. Follow the location codes when placing repeater cards.
Table 6. Repeater card placement for single and dual style repeater cards Type and number of repeater cards 1 single repeater card and 0 dual repeater cards 2 single repeater cards and 0 dual repeater cards 3 single repeater cards and 0 dual repeater cards 4 single repeater cards and 0 dual repeater cards 1 single repeater card and 1 dual repeater card 1 single repeater card and 2 dual repeater cards Single repeater card placement C5 Place in order C5 and C2 Place in order C5, C2, and C4 Place in order C5, C2, C4, and C3 Place in C5 first, and then place dual repeater card Place in C5 first, and then place dual repeater card C4 Place in order C4 and C3 Dual repeater card placement

Connecting and configuring disk drive enclosures

Table 6. Repeater card placement for single and dual style repeater cards (continued) Type and number of repeater cards 2 single repeater cards and 1 dual repeater cards 2 single repeater cards and 2 dual repeater cards 0 single repeater cards and 1 dual repeater card 0 single repeater cards and 2 dual repeater cards 0 single repeater cards and 3 dual repeater cards 0 single repeater cards and 4 dual repeater cards Restriction: This configuration is for System p models only. Single repeater card placement Place in C5, C2, and then place dual repeater card Place in C5, C2, and then place dual repeater card Dual repeater card placement C4 Place in order C4 and C3 C4 Place in order C4 and C5 Place in order C4, C5, and C3 Place in order C4, C5, C3, and C2

The following figures show the locations of the disk drives for the front and back of the 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure.

Figure 30. Front view of 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure

Power Systems: Enclosures and expansion units

Figure 31. Back view of 5786, 5787, 7031-D24, or 7031-T24 SCSI disk drive enclosure

The following list describes how the repeater card locations affect the disk drive slots. v The top-left repeater card (C2) drives the front right six slots (D07 to D12). See Figure 30 on page 56. v The top-right repeater card (C3) drives the front left six slots (D01 to D06). See Figure 30 on page 56. v The bottom-left repeater card (C4) drives the back left six slots (D13 to D18). See Figure 31. v The bottom-right repeater card (C5) drives the back right six slots (D19 to D24). See Figure 31. To install your repeater card, complete the following steps: 1. Remove the filler from the repeater card slot. 2. Install your new repeater card.

Removing and replacing a SCSI repeater card

You might need to remove and replace one of the Small Computer System Interface (SCSI) repeater cards to repair a failing device or as a part of another service action. Before you remove and replace a SCSI repeater card, follow the instructions for your operating system to save any jobs. For IBM i, power off the partition to save any jobs. Important: The I/O adapter (IOA) needs to be powered off before disconnecting or reconnecting cables or before removing or replacing the repeater card. The IOA can be powered off by powering off the IOA slot or the logical partition. Depending on the disk protection level, the system or logical partition might be affected during the service procedure. For additional information, see Installing PCI adapters. Restriction: You must replace the repeater card with the same type of card to continue. If you are changing card configurations from single repeater cards to dual repeater cards, stop here and follow the instructions in Connecting the 5786, 5787, 7031-D24, or 7031-T24 to a system that has an AIX operating system on page 41 or Connecting and configuring the disk drive enclosure in a system that has a Linux operating system on page 47. The disk drive enclosure SCSI repeater card can be removed and replaced with the system and enclosure power on. To avoid errors, you must power off the adapter that connects the disk drive enclosure to your system. To remove and replace a SCSI repeat card, complete the following steps.

Connecting and configuring disk drive enclosures

1. Locate the repeater card that you are replacing. For instructions see Identifying a failing part on page 35. 2. Remove the cable (A) from the repeater card (B).

Figure 32. Removing SCSI cable from the repeater card

3. Lift the handle (C) to unseat the repeater card from the enclosure. 4. Pull the repeater card out of the enclosure. 5. Align the replacement repeater card with the empty slot on the enclosure, and insert the card until it is firmly seated. 6. Lower the handle to secure the repeater card into place. 7. Reattach the cable to the repeater card. 8. Restart the adapter. See Installing PCI adapters.

Configuring the disk drive subsystem on the 5802 expansion unit

Learn how to configure the disk drive subsystem on the 5802 expansion unit. Note: For 5802 SAS disk drive enclosure connector locations referred to in this procedure, see http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/connector5802.htm (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ham/connector5802.htm). 1. The 5802 SAS disk drive enclosure can hold up to 18 disk drives. The disks in this enclosure can be organized in several different configurations depending on the operating system used, the type of SAS adapter, and the position of the hard-disk-drive partitions switch. Notes: v The hard-disk-drive partitions switch is located at the rear of the 5802 SAS disk drive enclosure. The hard-disk-drive partitions switch is located just below the SAS connectors. v If the hard-disk-drive partitions switch position is changed, you must power cycle the 5802 SAS disk drive enclosure in order for the 5802 to sense the new position of the hard-disk-drive partitions switch. The 5802 SAS disk drive enclosure supports the following operating systems:

Power Systems: Enclosures and expansion units

v AIX v IBM i v Linux To determine the level of software you need to support the 5802 SAS disk drive enclosure, see IBM Prerequisite (http://www-912.ibm.com/e_dir/eServerPrereq.nsf).
Table 7. Positions of the hard-disk-drive toggle switch Operating system AIX Position 1 Either a (FC 5901) PCIe Dual - x4 SAS Adapter or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters IBM i Not supported Position 2 Either two (FC 5901) PCIe Dual - x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Either two (FC 5901) PCIe Dual - x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Linux Either a (FC 5901) PCIe Dual - x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Note: FC means feature code. Either two (FC 5901) PCIe Dual - x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Four (FC 5901) - PCIe Dual - x4 SAS Adapters Not supported Position 4 Four (FC 5901) - PCIe Dual - x4 SAS Adapters

Tip: If you are planning to configure RAID arrays, ensure that you have the following minimum number of available disks for each RAID level: RAID 0 1 drive minimum per array RAID 5 3 drives minimum per array RAID 6 4 drives minimum per array RAID 10 2 drives minimum per array For additional SAS RAID controller information for the AIX operating system, see SAS RAID controller for AIX (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ebj/ sascontroller_kickoff_aix.htm). For additional SAS RAID controller information for the Linux operating system, see SAS RAID controller for Linux (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7ebk/ sascontroller_kickoff.htm). For information related to device parity protection, see Device parity protection (http:// publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/rzaly/rzalydpy.htm).

Connecting and configuring disk drive enclosures

Cabling the 5802 disk subsystem

Learn about how to connect the 5802 disk subsystem. Use this procedure to cable the 5802 disk subsystem: 1. To select a cabling configuration that suits your requirements, see the table in this section. 2. Cable the 5802 disk subsystem. Note: For SAS cable information, see Serial-attached SCSI cable planning (http:// publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7had/p7hadsascabling.htm).
Table 8. Configuration requirements of the 5802 disk subsystem Configuration features Two hard-disk-drive partitions with nine disks per hard disk drive partition This is a multi-initiator high-availability configuration. Dual Serial-attached SCSI (SAS) connectivity to all drives. Configuration requirements To see the physical cabling, see Figure 33 on page 61. Operating system: AIX, IBM i, or Linux SAS adapter card: Either two (FC 5901) - PCIe Dual x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Hard-disk-drive partitions switch: position 2 Cables: Four (FC 3688) - SAS cables (AT) 0.6 Meter. Note: v For AIX and Linux operating systems, this must be a RAID configuration. v You must have a minimum of one disk drive per hard-disk-drive partition. One hard-disk-drive partition with 18 disks and a single SAS adapter. For related physical cabling, see Figure 34 on page 62. Operating system: AIX or Linux SAS adapter: One (FC 5901) - PCIe Dual - x4 SAS Adapter Hard-disk-drive partitions switch: position 1 Cables: One (FC 3688) - SAS Cable (AT) 0.6 Meter. Two hard-disk-drive partitions with nine disks per hard-disk-drive partition and a single SAS adapter. To see the physical cabling, see Figure 35 on page 62. Operating system: AIX, IBM i, or Linux SAS adapter: One (FC 5901) - PCIe Dual - x4 SAS Adapter Hard-disk-drive partitions switch: position 2 Cables: Two (FC 3688) - SAS Cables (AT) 0.6 Meter. Note: A minimum of one disk drive per hard-disk-drive partition is required. Two hard-disk-drive partitions with nine disks per hard-disk-drive partition and two SAS adapters. To see the physical cabling, see Figure 36 on page 62. Operating system: AIX, IBM i, or Linux SAS adapter: Two (FC 5901) - PCIe Dual - x4 SAS Adapters Hard-disk-drive partitions switch: position 2 Cables: Two (FC 3688) - SAS Cables (AT) 0.6 Meter. Note: A minimum of one disk drive per hard-disk-drive partition is required.

Power Systems: Enclosures and expansion units

Table 8. Configuration requirements of the 5802 disk subsystem (continued) Configuration features Configuration requirements

To see physical cabling, see Figure 37 on page 63. Two hard-disk-drive partitions with nine disks per Operating system: AIX, IBM i, Linux hard-disk-drive partition and four SAS adapters (two pairs of SAS adapters, each running a set of nine disk SAS adapter: Either four (FC 5901) - PCIe Dual - x4 drives). SAS Adapters or four (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters This is a multi-initiator high-availability configuration. Hard-disk-drive partitions switch: position 2 Dual SAS connectivity to all drives. Cables: Four (FC 3688) - SAS Cables (AT) 0.6 Meter. Notes: v For AIX and Linux operating systems, this must be a RAID configuration. v A minimum of one disk drive per hard-disk-drive partition is required. One hard-disk-drive partition with 18 disks and dual SAS adapters. This is a multi-initiator high-availability configuration. Dual SAS connectivity to all drives. For related physical cabling, see Figure 38 on page 63. Operating system: AIX or Linux SAS adapter: Either two (FC 5901) - PCIe Dual - x4 SAS Adapters or two (FC 5903) - PCIe Dual - x4 3Gb SAS RAID Adapters Hard-disk-drive partitions switch: position 1 Cables: Two (FC 3688) - SAS Cables (AT) 0.6 Meter. Note: Fore AIX and Linux operating systems, this must be a RAID configuration. Four hard-disk-drive partitions: v Partition 1: Drives 01-05 v Partition 2: Drives 06-09 v Partition 3: Drives 10-14 v Partition 4: Drives 15-18 This configuration is optimized for boot partitions. To see the physical cabling, see Figure 39 on page 63. Operating system: AIX or Linux SAS adapter: Four (FC 5901) - PCIe Dual - x4 SAS Adapters Hard-disk-drive partitions switch: position 4 Cables: Four (FC 3688) - SAS Cables (AT) 0.6 Meter. Note: A minimum of one disk drive per hard-disk-drive partition is required.

Figure 33. Physical cabling example: Two hard-disk-drive partitions with nine disks per hard-disk-drive partition, dual SAS adapters, and hard-disk-drive partitions switch position 2

Connecting and configuring disk drive enclosures

Figure 34. Physical cabling example: One hard-disk-drive partition with 18 disks, a single SAS adapter, and hard-disk-drive partitions switch position 1

Figure 35. Physical cabling example: Two hard-disk-drive partitions with nine disks per hard-disk-drive partition, a single SAS adapter, and hard-disk-drive partitions switch position 2

Figure 36. Physical cabling example: Two hard-disk-drive partitions with nine disks per hard-disk-drive partition, two SAS adapters, and hard-disk-drive partitions switch position 2

Power Systems: Enclosures and expansion units

Figure 37. Physical cabling example: Two hard-disk-drive partitions with nine disks per hard-disk-drive partition, four SAS adapters, and hard-disk-drive partitions switch position 2

Figure 38. Physical cabling example: One hard-disk-drive partition with 18 disks, dual SAS adapters, and hard-disk-drive partitions switch position 1

Figure 39. Physical cabling example: Four hard-disk-drive partitions with four or five disks per hard-disk-drive partition and hard-disk-drive partitions switch position 4

Connecting and configuring disk drive enclosures

3. Set the hard-disk-drive partitions switch to the correct position for your cabling configuration by using the table in this section. 4. Cable the 5802 disk subsystem to your server. For details, see Cabling the 5802 and 5877 to the server.

Cabling the 5802 and 5877 to the server

Learn how to cable the 5802 and 5877 to the server. Use this procedure to connect the 5802 and 5877 to the server: 1. Install the 12X adapter into your server. 2. Connect the 12X DDR cable to your 5802 or 5877 expansion unit. For information on 12X DDR cables, see Identifying 12X and SPCN cables (http://publib.boulder.ibm.com/infocenter/systems/scope/hw/ topic/p7ham/identifycables.htm). Note: Two modes are available for connecting the 12X interface: v Double-barrel mode: Using two 12X DDR cables, connect port 0 of the 5802 or 5877 expansion unit to port 0 of the 12X interface on the server, and connect port 1 of the 5802 or 5877 expansion unit to port 1 of the 12X interface on the server. v Loop mode. 3. Install the other end of the 12X DDR cable to the 12X adapter on the server. 4. Add the disk drives to the operating system you are using.

5886 SAS disk drive enclosure

Learn about the SAS disk drive enclosure and how to assemble it. 1. Review the following information. The SAS disk drive enclosure can hold up to 12 disk drives. The enclosure cannot be split into two independent groups. The SAS disk drive enclosure supports the following operating systems: v AIX v IBM i v Linux To determine the level of software that you need to support the SAS disk drive enclosure, see IBM Prerequisite (http://www-912.ibm.com/e_dir/eServerPrereq.nsf). Tip: If you are planning to configure RAID arrays, ensure that you have the following number of available disks for each RAID level: RAID 0 or 1 Two drives per array RAID 5 At least 3 drives per array RAID 6 At least 4 drives per array

Connecting the SAS adapter to the 5886 disk drive enclosure

Learn about how to connect the 5886 disk drive enclosure Use this procedure to connect the 5886 disk drive enclosure:

Power Systems: Enclosures and expansion units

For additional information related to Serial-attached SCSI (SAS) cabling and cabling configurations, see Serial attached SCSI cable planning. Note: You need to power off the server before connecting the cables. 1. Install the SAS adapter into your server. 2. Connect the SAS cable to your disk drive. Choose one of the following methods based on your situation: v Figure 40 v Figure 41 on page 66 v Figure 42 on page 66

Figure 40. SAS YO cable to single enclosure with EE cables adding an additional enclosure or two YO connected enclosures each with an additional enclosure attached

Connecting and configuring disk drive enclosures

Figure 41. Single enclosure attached with YI cable to external SAS port

Figure 42. SAS YO cable to single enclosure card

3. Install the other end of the SAS cable to the SAS adapter or to the external SAS port on the server. 4. Add the disk drives to the operating system you are using.

Power Systems: Enclosures and expansion units

5. For steps to verify the new configuration, see Verifying the installed part (http:// publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7haj/p7hajhsmverify.htm).

Connecting and configuring disk drive enclosures

Power Systems: Enclosures and expansion units

Notices
This information was developed for products and services offered in the U.S.A. The manufacturer may not offer the products, services, or features discussed in this document in other countries. Consult the manufacturer's representative for information on the products and services currently available in your area. Any reference to the manufacturer's product, program, or service is not intended to state or imply that only that product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any intellectual property right of the manufacturer may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any product, program, or service. The manufacturer may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to the manufacturer. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The manufacturer may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to Web sites not owned by the manufacturer are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this product and use of those Web sites is at your own risk. The manufacturer may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning products not produced by this manufacturer was obtained from the suppliers of those products, their published announcements or other publicly available sources. This manufacturer has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to products not produced by this manufacturer. Questions on the capabilities of products not produced by this manufacturer should be addressed to the suppliers of those products. All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information in softcopy, the photographs and color illustrations may not appear. The drawings and specifications contained herein shall not be reproduced in whole or in part without the written permission of the manufacturer. The manufacturer has prepared this information for use with the specific machines indicated. The manufacturer makes no representations that it is suitable for any other purpose. The manufacturer's computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure. In addition, users must establish procedures to ensure that there is independent data verification before relying on such data in sensitive or critical operations. Users should periodically check the manufacturer's support websites for updated information and fixes applicable to the system and related software.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

Electronic emission notices Class A Notices

The following Class A statements apply to the IBM servers that contain the POWER7 processor and its features unless designated as electromagnetic compatibility (EMC) Class B in the feature information.

Federal Communications Commission (FCC) statement

Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.

Power Systems: Enclosures and expansion units

Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate the equipment. This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Industry Canada Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformit la rglementation d'Industrie Canada

Cet appareil numrique de la classe A est conforme la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards. This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment. European Community contact: IBM Deutschland GmbH Technical Regulations, Department M456 IBM-Allee 1, 71139 Ehningen, Germany Tele: +49 7032 15-2937 e-mail: tjahn@de.ibm.com Warning: This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures.

VCCI Statement - Japan

The following is a summary of the VCCI Japanese statement in the box above: This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio interference may occur, in which case, the user may be required to take corrective actions.

Notices

Japanese Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guideline (products less than or equal to 20 A per phase)

Japanese Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guideline with Modifications (products greater than 20 A per phase)

Electromagnetic Interference (EMI) Statement - People's Republic of China

Declaration: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may need to perform practical action.

Electromagnetic Interference (EMI) Statement - Taiwan

The following is a summary of the EMI Taiwan statement above. Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user will be required to take adequate measures. IBM Taiwan Contact Information:

Power Systems: Enclosures and expansion units

Electromagnetic Interference (EMI) Statement - Korea

Please note that this equipment has obtained EMC registration for commercial use. In the event that it has been mistakenly sold or purchased, please exchange it for equipment certified for home use.

Germany Compliance Statement

Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse A EU-Richtlinie zur Elektromagnetischen Vertrglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften ber die elektromagnetische Vertrglichkeit in den EU-Mitgliedsstaaten und hlt die Grenzwerte der EN 55022 Klasse A ein. Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren und zu betreiben. Des Weiteren drfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung von IBM gesteckt/eingebaut werden. EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden: "Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Strungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Manahmen zu ergreifen und dafr aufzukommen." Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse A Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Einhaltung der EMV Vorschriften ist der Hersteller: International Business Machines Corp.
Notices

New Orchard Road Armonk, New York 10504 Tel: 914-499-1900 Der verantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland GmbH Technical Regulations, Abteilung M456 IBM-Allee 1, 71139 Ehningen, Germany Tel: +49 7032 15-2937 e-mail: tjahn@de.ibm.com Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.

Electromagnetic Interference (EMI) Statement - Russia

Class B Notices
The following Class B statements apply to features designated as electromagnetic compatibility (EMC) Class B in the feature installation information.

Federal Communications Commission (FCC) statement

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: v Reorient or relocate the receiving antenna. v Increase the separation between the equipment and receiver. v Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. v Consult an IBM-authorized dealer or service representative for help. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. Proper cables and connectors are available from IBM-authorized dealers. IBM is not responsible for any radio or television interference caused by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate this equipment.

Power Systems: Enclosures and expansion units

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Industry Canada Compliance Statement

This Class B digital apparatus complies with Canadian ICES-003.

Avis de conformit la rglementation d'Industrie Canada

Cet appareil numrique de la classe B est conforme la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards. This product has been tested and found to comply with the limits for Class B Information Technology Equipment according to European Standard EN 55022. The limits for Class B equipment were derived for typical residential environments to provide reasonable protection against interference with licensed communication equipment. European Community contact: IBM Deutschland GmbH Technical Regulations, Department M456 IBM-Allee 1, 71139 Ehningen, Germany Tele: +49 7032 15-2937 e-mail: tjahn@de.ibm.com

VCCI Statement - Japan

Japanese Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guideline (products less than or equal to 20 A per phase)

Japanese Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guideline with Modifications (products greater than 20 A per phase)

Notices

IBM Taiwan Contact Information

Electromagnetic Interference (EMI) Statement - Korea

Germany Compliance Statement

Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse B EU-Richtlinie zur Elektromagnetischen Vertrglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften ber die elektromagnetische Vertrglichkeit in den EU-Mitgliedsstaaten und hlt die Grenzwerte der EN 55022 Klasse B ein. Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren und zu betreiben. Des Weiteren drfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung von IBM gesteckt/eingebaut werden. Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse B Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Einhaltung der EMV Vorschriften ist der Hersteller: International Business Machines Corp. New Orchard Road Armonk, New York 10504 Tel: 914-499-1900 Der verantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland GmbH Technical Regulations, Abteilung M456

Power Systems: Enclosures and expansion units

IBM-Allee 1, 71139 Ehningen, Germany Tel: +49 7032 15-2937 e-mail: tjahn@de.ibm.com Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse B.

Terms and conditions

Permissions for the use of these publications is granted subject to the following terms and conditions. Personal Use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative works of these publications, or any portion thereof, without the express consent of the manufacturer. Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of the manufacturer. Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. The manufacturer reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by the manufacturer, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. THE MANUFACTURER MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THESE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices

Power Systems: Enclosures and expansion units

Printed in USA

Server 3850x6
No ratings yet
Server 3850x6
2,018 pages
ps701 PDSG PDF
No ratings yet
ps701 PDSG PDF
310 pages
P 8 Eal
No ratings yet
P 8 Eal
160 pages
Flex System x440 Compute Node 7917, 7167, 2590 and 2584 Installation and Service Guide
No ratings yet
Flex System x440 Compute Node 7917, 7167, 2590 and 2584 Installation and Service Guide
760 pages
7145 PDSG PDF
No ratings yet
7145 PDSG PDF
1,064 pages
PDF 3850x6 Isg PDF
No ratings yet
PDF 3850x6 Isg PDF
1,990 pages
Expansion Unit
No ratings yet
Expansion Unit
104 pages
System x3650 M3 7945
No ratings yet
System x3650 M3 7945
210 pages
IBM Flex System X220
No ratings yet
IBM Flex System X220
370 pages
ps700 Iug PDF
No ratings yet
ps700 Iug PDF
74 pages
PDF 2583 Isg
No ratings yet
PDF 2583 Isg
566 pages
Lenovo Storage d1212 d1224 d3284 Hardware Installation and Maintenance Guide
No ratings yet
Lenovo Storage d1212 d1224 d3284 Hardware Installation and Maintenance Guide
146 pages
Installation and User's Guide - IBM System x3250 M3
No ratings yet
Installation and User's Guide - IBM System x3250 M3
106 pages
Manual de Servicio IBM x3650 M4
No ratings yet
Manual de Servicio IBM x3650 M4
480 pages
dw1hn Iug
No ratings yet
dw1hn Iug
86 pages
Hardware Maintenance Manual and Troubleshooting Guide: Ibm Xseries 225 Types 8649
No ratings yet
Hardware Maintenance Manual and Troubleshooting Guide: Ibm Xseries 225 Types 8649
194 pages
IBM x240 Installation Guide
No ratings yet
IBM x240 Installation Guide
666 pages
Manual Lewmar V700
No ratings yet
Manual Lewmar V700
20 pages
Eserver 330 Xseries
No ratings yet
Eserver 330 Xseries
72 pages
P9hak 914 924
No ratings yet
P9hak 914 924
130 pages
User's Guide: IBM System x3850 M2 and System x3950 M2 Types 7141 and 7233
No ratings yet
User's Guide: IBM System x3850 M2 and System x3950 M2 Types 7141 and 7233
102 pages
X 3530 M 4 Ibm
No ratings yet
X 3530 M 4 Ibm
708 pages
Hardware Installation Maintenance Guide Lenovo Storage d1212 d1224 d3284
No ratings yet
Hardware Installation Maintenance Guide Lenovo Storage d1212 d1224 d3284
152 pages
Enclosures and Expansion Units
No ratings yet
Enclosures and Expansion Units
168 pages
x3530 m4 Installation PDF
No ratings yet
x3530 m4 Installation PDF
402 pages
2107 Install Guide v5
No ratings yet
2107 Install Guide v5
114 pages
P8eg5 85x
No ratings yet
P8eg5 85x
120 pages
IBM x3250 m4 Server
No ratings yet
IBM x3250 m4 Server
558 pages
170 250 6xx 7xx SXX System Installation and Upgrade - Y4459505 PDF
No ratings yet
170 250 6xx 7xx SXX System Installation and Upgrade - Y4459505 PDF
387 pages
IBM System x3850 X5 and x3950 X5 Installation and User's Guide
No ratings yet
IBM System x3850 X5 and x3950 X5 Installation and User's Guide
164 pages
Installation Guide - IBM System x3850 M2 and x3950 M2 (7141, 7233, 7234)
No ratings yet
Installation Guide - IBM System x3850 M2 and x3950 M2 (7141, 7233, 7234)
100 pages
Catálogo Johnson Controls
100% (1)
Catálogo Johnson Controls
145 pages
Manual Do Sensor de Incendio - Globalfire - AD - Series - Manual
No ratings yet
Manual Do Sensor de Incendio - Globalfire - AD - Series - Manual
2 pages
P 8 Egt
No ratings yet
P 8 Egt
90 pages
Power Supplies For The Emx0 Pcie Gen3 I/O Expansion Drawer
No ratings yet
Power Supplies For The Emx0 Pcie Gen3 I/O Expansion Drawer
96 pages
Installing The Model 024, ESLL, or ESLS Storage Enclosure: Power Systems
No ratings yet
Installing The Model 024, ESLL, or ESLS Storage Enclosure: Power Systems
64 pages
System x3650 m3
No ratings yet
System x3650 m3
194 pages
IBM FlashSystem™ 710 User's Guide
No ratings yet
IBM FlashSystem™ 710 User's Guide
46 pages
DS 80 Manual PDF
100% (1)
DS 80 Manual PDF
82 pages
Lenovo SR530 Maintenance - Manual
No ratings yet
Lenovo SR530 Maintenance - Manual
184 pages
Qcs 2010 Part 28.02 Irrigation System Specifications
100% (1)
Qcs 2010 Part 28.02 Irrigation System Specifications
38 pages
User's Guide: System x3650 Type 7979
No ratings yet
User's Guide: System x3650 Type 7979
144 pages
Ibm X3850 8864
No ratings yet
Ibm X3850 8864
202 pages
Voltage Regulator Modules For The Emx0 Pcie Gen3 I/O Expansion Drawer
No ratings yet
Voltage Regulator Modules For The Emx0 Pcie Gen3 I/O Expansion Drawer
52 pages
Flashsystem Bkmap Install
No ratings yet
Flashsystem Bkmap Install
82 pages
IBM 3500 M2 User's Guide
No ratings yet
IBM 3500 M2 User's Guide
126 pages
GX Adapters
No ratings yet
GX Adapters
92 pages
x3100 m5 Type 5457
No ratings yet
x3100 m5 Type 5457
688 pages
0595 Service Manual
No ratings yet
0595 Service Manual
68 pages
Installation and User's Guide: IBM System x3250 M4 Type 2583
No ratings yet
Installation and User's Guide: IBM System x3250 M4 Type 2583
108 pages
4007-9810 Network Interface PDF
No ratings yet
4007-9810 Network Interface PDF
32 pages
(Cd光碟 - 操作手冊) Motoman-mh180 Instructions
No ratings yet
(Cd光碟 - 操作手冊) Motoman-mh180 Instructions
97 pages
Trio 50.0 - 60.0 TL Outd Product Manual en Reva (M000035ag)
No ratings yet
Trio 50.0 - 60.0 TL Outd Product Manual en Reva (M000035ag)
138 pages
Xseries 346 Types 8840 and 1880 Maintenance Manual
No ratings yet
Xseries 346 Types 8840 and 1880 Maintenance Manual
176 pages
IBM System x445 Type 8870 Hardware Maintenance Manual
No ratings yet
IBM System x445 Type 8870 Hardware Maintenance Manual
324 pages
LSI RAID 1060E Installation and Users Guide
No ratings yet
LSI RAID 1060E Installation and Users Guide
68 pages
Xseries 226 Type 8488 & 8648 - Hardware Maintenance
No ratings yet
Xseries 226 Type 8488 & 8648 - Hardware Maintenance
198 pages
Conlog PDF
67% (12)
Conlog PDF
73 pages
Electrical Wiring Design1 - BTech
No ratings yet
Electrical Wiring Design1 - BTech
33 pages
Installation Manual & Technical Information Automatic Laser Control Control Box Model CB26 Model CB24+
100% (1)
Installation Manual & Technical Information Automatic Laser Control Control Box Model CB26 Model CB24+
33 pages
25 K 8114
No ratings yet
25 K 8114
210 pages
Detection and Control Components: FCM-1 Control Module (IQ-318/IQ-636X-2)
No ratings yet
Detection and Control Components: FCM-1 Control Module (IQ-318/IQ-636X-2)
98 pages
PS 503K Draings
No ratings yet
PS 503K Draings
12 pages
Xseries 235 Type 8671 - Hardware Maintenance Manual
No ratings yet
Xseries 235 Type 8671 - Hardware Maintenance Manual
222 pages
Installation and User's Guide: System x3100 M4 Type 2582
No ratings yet
Installation and User's Guide: System x3100 M4 Type 2582
108 pages
69NT40 551 500 To 599: Container Refrigeration
No ratings yet
69NT40 551 500 To 599: Container Refrigeration
132 pages
ABL SwitchingDevices Web 2016
No ratings yet
ABL SwitchingDevices Web 2016
116 pages
IBM System x3550M2 Type 7946 Installation & User Guide
No ratings yet
IBM System x3550M2 Type 7946 Installation & User Guide
138 pages
7976 IBM System X 3400 PDF
No ratings yet
7976 IBM System X 3400 PDF
124 pages
System x3650 Type 7979 - Installation Guide
No ratings yet
System x3650 Type 7979 - Installation Guide
108 pages
p640 Installation Guide
No ratings yet
p640 Installation Guide
104 pages
x3250 m1 Guide
No ratings yet
x3250 m1 Guide
74 pages
EM100 User Manual EN V108 Draft 20151119
No ratings yet
EM100 User Manual EN V108 Draft 20151119
123 pages
English - EnerSolis User's Msnual192321462003003
No ratings yet
English - EnerSolis User's Msnual192321462003003
19 pages
DSE72xx DSE73xx Operators Manual PDF
No ratings yet
DSE72xx DSE73xx Operators Manual PDF
19 pages
Deliverables
No ratings yet
Deliverables
13 pages
Baron 58P - Chapter 25 01062020R00
No ratings yet
Baron 58P - Chapter 25 01062020R00
19 pages
D H Reasi 8 Bedded
No ratings yet
D H Reasi 8 Bedded
30 pages
NBCC
No ratings yet
NBCC
16 pages
Kidde Spec ADS Fluoro-K 2023
No ratings yet
Kidde Spec ADS Fluoro-K 2023
5 pages
HG MCCB
No ratings yet
HG MCCB
12 pages
RainBird Model ESP-Me Advanced User Manual
No ratings yet
RainBird Model ESP-Me Advanced User Manual
36 pages
Wiring Installation According To IE Rules Emw Jlcaph
No ratings yet
Wiring Installation According To IE Rules Emw Jlcaph
23 pages
ABS Rules For Integrated Power Systems (IPS)
No ratings yet
ABS Rules For Integrated Power Systems (IPS)
17 pages
PF Shelter Wiring TPJ Division
No ratings yet
PF Shelter Wiring TPJ Division
7 pages
Installation Manual Air Pure For Ducted Type M00503Q 202004 V00
No ratings yet
Installation Manual Air Pure For Ducted Type M00503Q 202004 V00
8 pages
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
From Everand
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
Vladimir Kiselev
No ratings yet
Firelite BG12LSP
No ratings yet
Firelite BG12LSP
2 pages
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.