manualshive.com logo in svg

IBM PS700, Problem Determination And Service Manual

The IBM PS700 Installation and User Manual is a comprehensive guide that enables users to effortlessly set up and navigate through the features of this advanced product. Download this manual for free from manualshive.com to unlock the device's full potential and ensure a seamless user experience.

Share
Download
background image

3.

If the AIX operating system records a service request number (SRN), see “Service request
numbers (SRNs)” on page 129.

4.

Check the BladeCenter management-module event log. If an error was recorded by the
system, see “POST progress codes (checkpoints)” on page 84 or “System reference codes
(SRCs)” on page 16.

5.

If no error was recorded, or if the login prompt appears and you still suspect a problem,
continue to Step

003

.

Step

003

Is the operating system AIX?

Yes

Record any information or messages that may be in the management module event log;
then go to Step

005

.

No

Go to Step

004

.

Step

004

Is the operating system Linux?

Yes

Record any information or messages that may be in the management module event log;
then go to Step

007

. If you cannot load the stand-alone

Diagnostics

CD, answer this

question

No

.

No

Go to “Solving undetermined problems” on page 227.

Step

005

Perform the following steps:

Note:

When possible, run AIX online diagnostics in concurrent mode. AIX online diagnostics

perform more functions than the stand-alone Diagnostics.

1.

Perform the AIX online diagnostics, see “Starting AIX concurrent diagnostics” on page 186.
Record any diagnostic results and see the “Service request numbers (SRNs)” on page 129 to
identify the failing component.

Note:

When replacing a component, perform system verification for the component. See

“Using the diagnostics program” on page 189.

2.

If you cannot perform AIX concurrent online diagnostics, continue to Step

006

.

Step

006

Perform the following steps:

1.

Use the management-module Web interface to make sure that the device from which you load
the stand-alone diagnostics is set as the first device in the blade server boot sequence.

2.

Turn off the system unit power and wait 45 seconds before proceeding.

3.

Turn on the blade server and establish an SOL session.

4.

Check for the following responses:

a.

Progress codes are recorded in the management-module event log.

b.

Record any messages or diagnostic information that might be in the log.

5.

Load the stand-alone diagnostics. Go to “Starting stand-alone diagnostics from a CD” on page
187 or “Starting stand-alone diagnostics from a NIM server” on page 188.

6.

If you have replaced the failing component, perform system verification for the component.
See “Using the diagnostics program” on page 189

This ends the AIX procedure.

Step

007

Perform the following steps:

1.

Use the management-module Web interface to make sure that the device from which you load
the stand-alone diagnostics is set as the first device in the blade server boot sequence.

Chapter 2. Diagnostics

185

Summary of Contents for PS700

Page 1: ...Power Systems Problem Determination and Service Guide for the IBM Power PS700 8406 70Y GI11 9831 00 ...

Page 2: ......

Page 3: ...Power Systems Problem Determination and Service Guide for the IBM Power PS700 8406 70Y GI11 9831 00 ...

Page 4: ... Notices manual G229 9054 and the IBM Environmental Notices and User Guide Z125 5823 This edition applies to IBM Power Systems servers that contain the POWER7 processor and to all associated models Copyright IBM Corporation 2010 2011 US Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp ...

Page 5: ...dure 184 Performing the checkout procedure 184 Verifying the partition configuration 186 Running the diagnostics program 186 Starting AIX concurrent diagnostics 186 Starting stand alone diagnostics from a CD 187 Starting stand alone diagnostics from a NIM server 188 Using the diagnostics program 189 Boot problem resolution 190 Troubleshooting tables 191 General problems 191 Drive problems 192 Inte...

Page 6: ...talling the battery 251 Removing the disk drive tray 252 Installing the disk drive tray 253 Removing the tier 2 management card 255 Installing the tier 2 management card 256 Obtaining a PowerVM Virtualization Engine system technologies activation code 257 Replacing the FRU system board and chassis assembly 260 Chapter 5 Configuring 263 Updating the firmware 263 Configuring the blade server 264 Usi...

Page 7: ...he 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...

Page 8: ...tached 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 proce...

Page 9: ...he 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 ...

Page 10: ...ight 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 2030 mm 30 x 80 in v Ensure that all devices shelves drawers doors and cables are secure v Ensure that the four leveling pads are raised to their highest position v Ensure that there is no stabilizer bracket installe...

Page 11: ... 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 per...

Page 12: ...n 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 interface...

Page 13: ...ssistance see the information center or the Warranty and Support Information document on the IBM BladeCenter Documentation CD Related documentation Documentation for the PS700 blade server includes documents in Portable Document Format PDF on the IBM BladeCenter Documentation CD and the online information center The most recent version of all BladeCenter documentation is in the BladeCenter informa...

Page 14: ...or problem situations v Attention These notices indicate potential damage to programs devices or data An attention notice is placed just before the instruction or situation in which damage might occur v Caution These statements indicate situations that can be potentially hazardous to you A caution statement is placed just before the description of a potentially hazardous procedure step or situatio...

Page 15: ...n 10 to 35 C 50 to 95 F Altitude 0 to 914 m 3000 ft Blade server on 10 to 32 C 50 to 90 F Altitude 914 m to 2133 m 3000 ft to 7000 ft Blade server off 40 to 60 C 40 to 140 F v Humidity Blade server on 8 to 80 Blade server off 8 to 80 PS700 Size v Height 24 5 cm 9 7 inches v Depth 44 6 cm 17 6 inches v Width 30 mm 1 14 inches Systems management v Supported by BladeCenter chassis management module v...

Page 16: ...nufacturers v Each DIMM within a processor support group 1 4 and 5 8 must be the same size and speed v Install only supported DIMMs as described on the ServerProven Web site See http www ibm com servers eserver serverproven compat us v Installing or removing DIMMs changes the configuration of the blade server After you install or remove a DIMM the blade server is automatically re configured and th...

Page 17: ...D on the button flashes while the request is being processed then is lit when the ownership of the media tray has been transferred to the blade server It can take approximately 20 seconds for the operating system in the blade server to recognize the media tray If there is no response when you press the media tray select button use the management module to determine whether local control has been d...

Page 18: ... the partition Use this recessed button only as directed by IBM Support 6 Power on LED This green LED indicates the power status of the blade server in the following manner v Flashing rapidly The service processor is initializing the blade server v Flashing slowly The blade server has completed initialization and is waiting for a power on command v Lit continuously The blade server has power and i...

Page 19: ...Center unit The blade server can respond to requests from the service processor such as a remote request to turn on the blade server To remove all power from the blade server you must remove it from the BladeCenter unit Shut down the operating system before you turn off the blade server See the operating system documentation for information about shutting down the operating system You can turn off...

Page 20: ...or panel connector 2 DIMM 1 4 connectors See Figure 4 on page 9 for individual connectors Expansion unit SMP connector 3 Management card connector P1 C9 4 SAS hard disk drive connector P1 D2 5 Light Path Blue Button 6 SAS hard disk drive P1 C10 7 CIOv 1Xe expansion card connector P1 C11 8 High Speed CFFh expansion card connector P1 C12 9 DIMM 5 8 connectors See Figure 4 on page 9 for individual co...

Page 21: ...ssing and use Figure 5 to identify the failing component Figure 5 shows the locations of LEDs on the system board Table 3 shows LED descriptions Table 3 PS700 LEDs Callout Base unit LEDs 1 3V lithium battery LED 2 DIMM 1 4 LEDs 3 Management card LED 4 Light path power LED 5 System board LED 6 HDD1 LED 7 Interposer LED Figure 4 DIMM connectors Base unit connectors Figure 5 LED locations on the syst...

Page 22: ... Callout Base unit LEDs 8 CIOv 1Xe expansion card connector LED 9 High Speed CFFh expansion card connector LED 10 HDD2 LED 11 DIMM 5 8 LEDs 10 Power Systems Problem Determination and Service Guide for the IBM Power PS700 8406 70Y ...

Page 23: ...nd system buses IBM hardware error checkers have these distinct attributes v Continuous monitoring of system operations to detect potential calculation errors v Attempted isolation of physical faults based on runtime detection of each unique failure v Initiation of a wide variety of recovery mechanisms designed to correct a problem POWER7 processor based systems include extensive hardware and firm...

Page 24: ...e troubleshooting tables to find solutions to problems that have identifiable symptoms See Troubleshooting tables on page 191 v Dump data collection In some circumstances an error might require a dump to show more data The Integrated Virtualization Manager IVM or Hardware Management Console HMC sets up a dump area Specific IVM or HMC information is included as part of the information that can opti...

Page 25: ...al information that is useful in problem determination All hardware state information is part of the dump if a hardware checkstop occurs When a checkstop occurs the service processor attempts to dump data that is necessary to analyze the error from appropriate parts of the system Note If you power off the blade through the management module while the service processor is performing a dump platform...

Page 26: ...rocedure on page 184 Table 4 Location codes Components Physical Location Code CRU LED Un location codes are for enclosure and VPD locations Un Utttt mmm sssssss tttt system machine type mmm system model number sssssss system serial number DIMM 1 Un P1 C1 Yes DIMM 2 Un P1 C2 Yes DIMM 3 Un P1 C3 Yes DIMM 4 Un P1 C4 Yes DIMM 5 Un P1 C5 Yes DIMM 6 Un P1 C6 Yes DIMM 7 Un P1 C7 Yes DIMM 8 Un P1 C8 Yes 2...

Page 27: ...o analyze the error log the system reference code SRC and turn on the system attention LED The service processor logs the nine word eight digit per word error code in the BladeCenter management module event log Error codes are either system reference codes SRCs or service request numbers SRNs A location code might also be included Isolation procedures If the fault analysis does not determine a def...

Page 28: ... 1 E Blade_05 01 21 2008 17 15 14 PS700 BC1BLD5E SYS F W Error Replace UNKNOWN 5008FECF B7001111 22222222 33333333 44444444 55555555 66666666 77777777 88888888 99999999 Depending on your operating system and the utilities you have installed error messages might also be stored in an operating system log See the documentation that comes with the operating system for more information The management m...

Page 29: ... server documentation refer to the POWER7 Reference Code Lookup page at http publib boulder ibm com infocenter powersys v3r1m5 index jsp topic ipha8 codefinder htm 1xxxyyyy SRCs The 1xxxyyyy system reference codes are system power control network SPCN reference codes Look for the rightmost 4 characters yyyy in 1xxxyyyy in the error code this is the reference code Find the reference code in Table 7...

Page 30: ... described in Replacing the FRU system board and chassis assembly on page 260 262C 5V reg_pgood fault 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 262D 3 3V reg_pgood fault 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis a...

Page 31: ...ltage alert Perform the DTRCARD symbolic CRU isolation procedure by completing the following steps 1 Reseat the PCIe expansion card 2 If the problem persists replace the expansion card 3 If the problem persists go to the Checkout procedure on page 184 4 If the problem persists replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page ...

Page 32: ...g steps 1 Reseat the PCIe expansion card 2 If the problem persists replace the expansion card 3 If the problem persists go to the Checkout procedure on page 184 4 If the problem persists replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 The DTRCARD symbolic CRU isolation procedure is in Service processor problems on page 2...

Page 33: ...e the system board as described in Replacing the FRU system board and chassis assembly on page 260 8402 Unable to get VPD from the concentrator 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 8413 Invalid processor 1 VPD 1 Go to Checkout procedure on page 184 2 Replace the system board as described in...

Page 34: ...hat the proper file is specified in the list of volumes and that the proper authority is granted 632BCFC5 A non recoverable error was detected while reading a virtual optical volume Resolve any errors on the Network File System server 632BCFC6 The file specified does not contain data that can be processed as a virtual optical volume On the Network File System server verify that all the files speci...

Page 35: ...as a supported format 2 If the format is supported clean the disk and attempt the failing operation again 3 If the operation fails again with the same system reference code ask your media source for a replacement disk 632CC400 Physical link error detected by device Refer to the hosting partition for problem analysis 632CC402 An internal program error occurred Install any available operating system...

Page 36: ...action is required A2D03002 User initiated RSCDUMP of IBM i partition s SLIC bootloader and PFW content No corrective action is required A700yyyy Licensed internal code SRCs An A700xxxx system reference code SRC is an error event code that is related to licensed internal code Table 11 A700yyyy Licensed internal code SRCs Reference Code Description Action A700173C Informational system log entry onl...

Page 37: ...des a suggested action to correct the problem Table 12 AA00E1A8 to AA260005 Partition firmware attention codes v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved If an action solves the problem then you can stop performing the remaining actions v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CR...

Page 38: ...he blade server 2 If the problem remains go to Boot problem resolution on page 190 AA06000C The media in a device in the boot list was not bootable 1 Replace the media in the device with known good media or modify the boot list to boot from another bootable device 2 If the problem remains go to Boot problem resolution on page 190 AA06000D The media in the device in the bootlist was not found under...

Page 39: ...tes then install the updates if available and retry the operation AA170210 Setenv setenv parameter error the name contains a null character 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 AA170211 Setenv setenv parameter error the value contains a null character 1 Go to Checkout procedure on page 184 ...

Page 40: ... see Solving undetermined problems on page 227 Table 13 B181xxxx Service processor early termination SRCs B181 xxxx Error Code Description Action 7200 Invalid boot request Go to Checkout procedure on page 184 7201 Service processor failure 7202 The permanent and temporary firmware sides are both marked invalid 7203 Error setting boot parameters 7204 Error reading boot parameters 7205 Boot code err...

Page 41: ...ix power or thermal problems and then retry the migration B2001131 A problem occurred during the migration of a partition The migration of a partition did not complete Check for server firmware updates then install the updates if available B2001132 A problem occurred during the startup of a partition A platform firmware error occurred while it was trying to allocate memory The startup will not con...

Page 42: ...server firmware updates then install the updates if available B2001150 During the startup of a partition a partitioning configuration problem occurred Go to Verifying the partition configuration on page 186 B2001151 A problem occurred during the migration of a partition The migration of a partition did not complete Check for server firmware updates then install the updates if available B2001170 Du...

Page 43: ...ation mismatch Go to Isolating firmware problems on page 218 B2001281 A partition memory error occurred The failed memory will no longer be used Restart the partition B2001282 A problem occurred during the startup of a partition Go to Isolating firmware problems on page 218 B2001320 A problem occurred during the startup of a partition No default load source was selected The startup will attempt to...

Page 44: ...f a partition the partition firmware attempted an operation that failed Go to Isolating firmware problems on page 218 B2002320 During the startup of a partition the partition firmware attempted an operation that failed Go to Isolating firmware problems on page 218 B2002425 During the startup of a partition the partition firmware attempted an operation that failed Go to Isolating firmware problems ...

Page 45: ...rver to use for managing the creation of a partition Check for server firmware updates then install the updates if available B2003128 A problem occurred during the startup of a partition A return code for an unexpected failure was returned when attempting to query the load source path Look for and resolve B700 69xx errors B2003130 A problem occurred during the startup of a partition Check for serv...

Page 46: ...urce into main storage The startup will attempt to continue If the startup does not continue look for and resolve other errors B2005117 A problem occurred during the startup of a partition A partition main storage dump has occurred but cannot be written to the load source device because a valid dump already exists Use the Main Storage Dump Manager to rename or copy the current main storage dump B2...

Page 47: ... server firmware updates then install the updates if available B200542A A Firmware Assisted Dump did not complete due to a read error Check for server firmware updates then install the updates if available B200542B A Firmware Assisted Dump did not complete due to a copy error Check for server firmware updates then install the updates if available B200543A A Firmware Assisted Dump did not complete ...

Page 48: ...to Isolating firmware problems on page 218 B2007200 Informational system log entry only No corrective action is required B2008080 Informational system log entry only No corrective action is required B2008081 During the startup of a partition an internal firmware time out occurred the partition might continue to start up but it can experience problems while running Check for server firmware updates...

Page 49: ...the updates if available B2008121 During the startup of a partition the partition did not start up due to a system firmware error Go to Isolating firmware problems on page 218 B2008123 During the startup of a partition the partition did not start up due to a system firmware error Go to Isolating firmware problems on page 218 B2008125 During the startup of a partition the partition did not start up...

Page 50: ...nd 2 Go to Isolating firmware problems on page 218 B200A140 A lower priority partition lost a usable processor to supply it to a higher priority partition with a bad processor Evaluate the entire LPAR configuration Adjust partition profiles with the new number of processors available in the system B200B07B Informational system log entry only No corrective action is required B200B215 A problem occu...

Page 51: ...008 Informational system log entry only No corrective action is required B200F009 Informational system log entry only No corrective action is required B200F00A Informational system log entry only No corrective action is required B200F00B Informational system log entry only No corrective action is required B200F00C Informational system log entry only No corrective action is required B200F00D Inform...

Page 52: ...ct the platform dump information 3 Go to Isolating firmware problems on page 218 0200 System firmware has experienced a low storage condition No immediate action is necessary Continue running the system normally At the earliest convenient time or service window work with IBM Support to collect a platform dump and restart the system then go to Isolating firmware problems on page 218 0201 System fir...

Page 53: ...og 2 Collect the platform dump data 3 Collect the partition configuration information 4 Go to Isolating firmware problems on page 218 0651 The system detected an error in the system clock hardware Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 0803 Informational system log entry only No corrective action is required 080...

Page 54: ...ttings results in the loss of all of the partition data that is stored on the service processor Before continuing with this operation manually record all settings that you intend to preserve The service processor reboots after IBM Support resets the server firmware settings If the problem persists Replace the system board as described in Replacing the FRU system board and chassis assembly on page ...

Page 55: ...m firmware detected a programming problem for which a platform dump may have been initiated 1 Collect the event log information 2 Collect the platform dump information 3 Go to Isolating firmware problems on page 218 5122 An error occurred during a search for the load source If the partition fails to startup go to Isolating firmware problems on page 218 Otherwise no corrective action is required 51...

Page 56: ...em with a processor Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 5442 System firmware detected an error Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 54DD Informational system log entry only No corrective action is required 5600 Informatio...

Page 57: ... to find or retrieve VPD LID file Check for server firmware updates then install the updates if available 6944 Informational system log entry only No corrective action is required 6950 A platform dump has occurred 1 Collect the platform dump information 2 Go to Isolating firmware problems on page 218 6951 An error occurred because a partition needed more NVRAM than was available Use the Integrated...

Page 58: ...nd chassis assembly on page 260 6974 Informational system log entry only No corrective action is required 6978 Informational system log entry only No corrective action is required 6979 Informational system log entry only No corrective action is required 697C Connection from service processor to system processor failed Replace the system board and chassis assembly as described in Replacing the FRU ...

Page 59: ...formational system log entry only No corrective action is required 69C3 Informational system log entry only No corrective action is required 69D9 Host Ethernet Adapter HEA failure Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 69DA Informational system log entry only No corrective action is required 69DB System firmware...

Page 60: ...e event log information 2 Go to Isolating firmware problems on page 218 F120 Informational system log entry only No corrective action is required F130 Thermal Power Management Device firmware error was detected Check for server firmware updates then install the updates if available BA000010 to BA400002 Partition firmware SRCs The power on self test POST might display an error code that the partiti...

Page 61: ...board as described in Replacing the FRU system board and chassis assembly on page 260 BA000032 The firmware failed to register the lpevent queues 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA000034 The firmware failed to exchange capacity and al...

Page 62: ...ge 260 BA000070 The firmware was unable to load the open firmware code lid 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA000080 The user did not accept the license agreement Accept the license agreement and restart the blade server If the problem...

Page 63: ... and chassis assembly on page 260 BA00E840 Failure when initializing PCI hot plug 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA00E843 Failure when initializing the interface to AIX or Linux 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system ...

Page 64: ...acing the FRU system board and chassis assembly on page 260 BA010003 Cannot get server hardware address Perform the following actions that checkpoint CA00E174 describes 1 Verify that v The bootp server is correctly configured then retry the operation v The network connections are correct then retry the operation 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system ...

Page 65: ...ists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA010008 The device_type property for this device is not supported by the iSCSI initiator configuration specification 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described ...

Page 66: ... of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter HBA which is the iSCSI initiator BA01000E The LUN specified is not valid The embedded host Ethernet adapters HEAs help provide iSCSI which is supported by iSCSI software device drivers on either AIX or Linux Verify that all of the iSCSI configuration arguments on the operating...

Page 67: ... persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA012010 Opening the TCP node failed 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA012011 ...

Page 68: ...the following actions that checkpoint CA00E174 describes 1 Verify that v The bootp server is correctly configured then retry the operation v The network connections are correct then retry the operation 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA01B012 BOOTP failed to w...

Page 69: ...ections are correct then retry the operation 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA01D001 Opening the DHCP node failed 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing t...

Page 70: ...ard as described in Replacing the FRU system board and chassis assembly on page 260 BA01D050 DHCP discover no good offer DHCP discovery did not receive any DHCP offers from the servers that meet the client requirements Verify that the DHCP server configuration file is not overly constrained An over constrained file might prevent a server from meeting the configuration requested by the client BA01D...

Page 71: ...nfiguration file to authoritative Verify that the DHCP server is functioning properly BA01D055 DHCP discover DHCP decline DHCP discovery did receive a DHCP offer from one or more servers that meet the client requirements However the client performed an ARP test on the address and found that another client was using the address The client sent a DHCP decline to the server but the client did not rec...

Page 72: ...the blade server firmware 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA040030 The firmware was not able to build the UID properly for this system As a result problems may occur with the licensing of the AIX operating system 1 Go to Checkout proc...

Page 73: ...led message 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA060008 No configurable adapters found by the Remote IPL menu in the SMS utilities This error occurs when the firmware cannot locate any LAN adapters that are supported by the remote IPL function Verify that the devices in the remote IPL dev...

Page 74: ...ed processors 2 Disable logical partitioning with shared processors in the operating system 3 If the problem remains a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA060060 The operating system expects an IOSP partition but it failed to make the transition to alpha mode 1 Verify that v The alpha mode...

Page 75: ...agement module boot list 1 Using the SMS menus set the boot list to the default boot list 2 Shut down then start up the blade server 3 Use SMS menus to customize the boot list as required 4 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA060201 Failed to read the VPD boot pat...

Page 76: ...sembly on page 260 BA090004 SCSD DASD send diagnostic failed devofl cmd 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA09000A There was a vendor specification error 1 Check the vendor specification for additional information 2 If the problem persists a Go to Checkout procedure on page 184 b Replace...

Page 77: ...acing the FRU system board and chassis assembly on page 260 BA09000F Media is not present 1 Insert new media with the correct format 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA090010 The request sense command failed 1 Troubleshoot the SCSD devices 2 Verify that the SCS...

Page 78: ...em board as described in Replacing the FRU system board and chassis assembly on page 260 BA120001 On an undetermined SCSD device test unit ready failed hardware error 1 Troubleshoot the SCSD devices 2 Verify that the SCSD cables and devices are properly plugged Correct any problems that are found 3 Replace the SCSD cables and devices 4 If the problem persists a Go to Checkout procedure on page 184...

Page 79: ...iagnostic failed devofl command 1 Troubleshoot the SCSD devices 2 Verify that the SCSD cables and devices are properly plugged Correct any problems that are found 3 Replace the SCSD cables and devices 4 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA120010 Failed to generate...

Page 80: ...U system board and chassis assembly on page 260 BA130012 USB CD ROM in the media tray execution of ATA ATAPI command failed 1 Retry the operation 2 Reboot the blade server 3 Troubleshoot the media tray and CD ROM drive 4 Replace the USB CD or DVD drive 5 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chas...

Page 81: ...I packet command execution failed 1 Remove the CD or DVD in the drive and replace it with a known good disk 2 If the problem persists a Retry the operation b Reboot the blade server c Troubleshoot the media tray and CD ROM drive d Replace the USB CD or DVD drive e If the problem persists 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system boar...

Page 82: ...SCSD cables and devices 4 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA140004 The SCSD read write optical send diagnostic failed devofl command 1 Troubleshoot the SCSD devices 2 Verify that the SCSD cables and devices are properly plugged Correct any problems that are foun...

Page 83: ...the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA154030 Invalid parameters were passed to the HEA device driver 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA154040 The TFTP package open failed 1 ...

Page 84: ...ard as described in Replacing the FRU system board and chassis assembly on page 260 BA170201 The firmware was unable to expand target partition saving configuration variable 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA170202 The firmware was un...

Page 85: ...s again for the network boot or network installation BA170998 NVRAMRC script evaluation error command line execution error 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA180008 PCI device Fcode evaluation error 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replac...

Page 86: ...Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA180099 PCI probe error bridge in freeze state slot in reset state 1 Reseat the PCI adapter card 2 Check for adapter firmware updates then install the updates if available 3 Check for server firmware updates then install the updates if available 4 Replace the PCI adapter card 5 If the problem ...

Page 87: ...ndshake properly with the serial interface 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA210000 Partition firmware reports a default catch 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the sy...

Page 88: ...described in Replacing the FRU system board and chassis assembly on page 260 BA210010 The transfer of control to the SLIC loader failed 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA210011 The transfer of control to the IO Reporter failed 1 Go to Checkout procedure on page 184 2 Replace the system...

Page 89: ...dule event log 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA210101 The partition firmware event log queue is full 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described ...

Page 90: ...nt log 2 Resolve any EEH event log entries that are found 3 Correct any errors that are found and reboot the blade server 4 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA220020 CRQ registration error partner vslot may not be valid Verify that this client virtual slot device...

Page 91: ...ed in Replacing the FRU system board and chassis assembly on page 260 BA280000 RTAS discovered an invalid operation that may cause a hardware error 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA290000 RTAS discovered an internal stack overflow 1 Go to Checkout procedure on page 184 2 Replace the s...

Page 92: ...U system board and chassis assembly on page 260 BA330000 Memory allocation error 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA330001 Memory allocation error 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 1...

Page 93: ...t communication failure reading the BladeCenter open fabric manager location code mapping data from the service processor 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA340003 An internal firmware error occurred unable to allocate memory for the o...

Page 94: ... firmware error occurred the open fabric manager system initiator capability data version was not correct 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 BA340009 An internal firmware error occurred the open fabric manager system initiator capability...

Page 95: ... and chassis assembly on page 260 BA340021 A logical partition event communication failure occurred when writing the BladeCenter open fabric manager system initiator capabilities data to the service processor 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on pa...

Page 96: ...ition Notes 1 For checkpoints with no associated location code see Light path diagnostics on page 214 to identify the failing component when there is a hang condition 2 For checkpoints with location codes see Location codes on page 14 to identify the failing component when there is a hang condition 3 For eight digit codes not listed here see Checkout procedure on page 184 for information The manag...

Page 97: ...tion file 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1001F0D Pre standby discovery completed in initial transition file While the blade server displays this checkpoint the service processor reads the system vital product data VPD The service processor must complete reading the system VPD before ...

Page 98: ... page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x10 Hardware object manager HOM initialize HOM 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x14 Hardware object manager HOM validate HOM 1 Go to Checkout procedure on page ...

Page 99: ...ure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x38 Processor check ring IPL step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x39 Processor L2 line delete in progress 1 Go to Checkout procedure on page...

Page 100: ...d in Replacing the FRU system board and chassis assembly on page 260 C1009x54 Start processor clocks IPL step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x58 Processor SCOM initialization step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as describ...

Page 101: ... step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x74 ASIC mask attentions being set up 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x78 ASIC check rings being set up 1 Go to ...

Page 102: ...scribed in Replacing the FRU system board and chassis assembly on page 260 C1009x94 ASIC transmit receive initialization step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009x98 ASIC wrap test in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described i...

Page 103: ... on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009xB8 ASIC memory diagnostic step in progress 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C1009xB9 PSI diagnostic step in progress 1 Go to Checkout procedure on page 184 2 Rep...

Page 104: ...ransferred to system storage 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C103A2xx Hypervisor data areas are being built in system storage 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C103A3xx Hyper...

Page 105: ... and the specific operating system code continues the IPL The virtual service processor can start a variety of operating systems Some codes are specific to an operating system and therefore do not apply to all operating systems Table 19 lists the progress codes that might be displayed during the power on self test POST along with suggested actions to take if the system hangs on the progress code O...

Page 106: ...m board as described in Replacing the FRU system board and chassis assembly on page 260 C20012FF Partition startup is allowed to proceed 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2001300 Initializing ISL roadmap 1 Go to Recovering the system firmware on page 220 2 Replace the system...

Page 107: ...n page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C200211F Power on command successful 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C20021FF Power on phase complete 1 Go to Recovering the system firmware on page 220 2 R...

Page 108: ... as described in Replacing the FRU system board and chassis assembly on page 260 C20024FF End powering on slots 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2002500 Begin power on VIO slots 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Re...

Page 109: ...Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C20031FF Waiting for ISL command completion 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C20032FF ISL command complete successfully 1 Go to Recovering the system firmware on page 220...

Page 110: ...ibed in Replacing the FRU system board and chassis assembly on page 260 C20043FF Load source device is connected 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2006000 Locating first LID information on the load source 1 Go to Recovering the system firmware on page 220 2 Replace the syste...

Page 111: ... Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2006060 Waiting for LID load to complete 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2006100 LID load completed successfully 1 Go to Recovering the system firmware on page 220 2 ...

Page 112: ...cribed in Replacing the FRU system board and chassis assembly on page 260 C20080FF Hypervisor low level session manager object is ready 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C2008100 Initializing service processor communication area 2 1 Go to Recovering the system firmware on pag...

Page 113: ...in Replacing the FRU system board and chassis assembly on page 260 C200813F End associate of system ports 1 Go to Recovering the system firmware on page 220 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 C20081FF Processors started successfully now waiting to receive the continue acknowledgement from system firmware 1 Go to Recovering the...

Page 114: ...d in the Action column until the problem is solved If an action solves the problem you can stop performing the remaining actions v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CRUs and which components are FRUs Table 20 C700xxxx Server firmware IPL status checkpoints Progress code Description Action C700xxxx A problem has occurred with the system firmware dur...

Page 115: ...communication link by using lpevents 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA000032 Attempting to register lpevent queues 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA000034 Attempting to e...

Page 116: ...g to load the second pass of C code 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA0000A0 Open firmware package corrupted phase 2 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00D001 PCI probe proc...

Page 117: ...FRU system board and chassis assembly on page 260 CA00D011 First pass open firmware initialization complete control returned to initialization firmware 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00D012 Second pass open firmware initialization complete control returned to initialization firmware...

Page 118: ... Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E110 Create KDUMP properties 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E130 Build device tree 1 Go to Checkout procedure on page 1...

Page 119: ... Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E139 Create aliases node and system aliases 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E13A Create packages node 1 Go to Checkout procedure on p...

Page 120: ...odule bootlist 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E149 Create boot manager node 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E14...

Page 121: ...156 Create plug in PCI bridge node 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E15B Transfer control to operating system service mode boot Go to Boot problem resolution on page 190 CA00E15F Adapter VPD evaluation 1 Go to Checkout procedure on page 184 2 Replace the system board as described in...

Page 122: ...retry the operation v The network connections are correct then retry the operation 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E177 Transfer failure due to TFTP error condition 1 Verify that v The bootp server is correctly configured then retry the operation v The net...

Page 123: ...ge 260 CA00E198 The system is rebooting to enact changes that were specified in ibm client architecture support Go to Boot problem resolution on page 190 CA00E199 The system is rebooting to enact changes that were specified in the boot image ELF header 1 Verify that v The bootp server is correctly configured then retry the operation v The network connections are correct then retry the operation 2 ...

Page 124: ...on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E1A4 User requested boot to SMS menus 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E1A5 User requested boot to open firmware prompt 1 Go to Checkout procedure on page 184 2...

Page 125: ...o Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E1B1 System booting system directed boot device repair 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E1B2 XOFF received waiting for XON 1 Go to Checkout...

Page 126: ...s described in Replacing the FRU system board and chassis assembly on page 260 CA00E1DD A graphics adapter has been selected as the firmware console but the USB keyboard is not attached 1 Verify that there is a USB keyboard attached to a USB port that is assigned to the partition 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing t...

Page 127: ...bly on page 260 CA00E1F9 Build boot device list for fibre channel adapters The location code of the SAN adapter being scanned is also displayed 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E1FA Building device list for SCSD adapters The device ID and device LUN of the device being scanned is al...

Page 128: ...00E443 Generate NVRAM configuration variable dictionary words 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E444 The NVRAM size is less than 8K bytes 1 Reboot the blade server 2 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing th...

Page 129: ...out procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E860 Initializing sensors 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E865 Initializing VPD 1 Go to Checkout procedure on page 184 2 Replace the system board...

Page 130: ...irmware 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E890 Starting to initialize open firmware 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA00E891 Finished initializing open firmware 1 Go to C...

Page 131: ...mware installation error did occur resolve the problem 3 Retry the firmware update 4 If the problem persists a Go to Checkout procedure on page 184 b Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 CA2799FD A firmware update module is being read This checkpoint alternates in the control panel with CA2799FF This pair of checkpoints might stay...

Page 132: ...he permanent boot image as described in Starting the PERM image on page 220 3 Use the Update and Manage System Flash menu to reject the temporary image D1001xxx to D1xx3FFF Service processor dump codes D1xx service processor dump status codes indicate the cage or node ID that the dump component is processing the node from which the hardware data is collected and a counter that increments each time...

Page 133: ...84 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1031xxx Dump dump header fips header 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1041xxx Dump dump header entry header 1 Go to Checkout procedure on page 184 2 Replace the system board a...

Page 134: ...cing the FRU system board and chassis assembly on page 260 D1141xxx Dump code version 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1151xxx Dump all opt p3 except rtbl 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assemb...

Page 135: ...rocedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1231xxx Dump update dump headers 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1241xxx Dump CRC1 calculation off 1 Go to Checkout procedure on page 184 2 Replace the syst...

Page 136: ...age 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D12D1xxx Rmove core core app time pid 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D12E1xxx Remove core core 1 Go to Checkout procedure on page 184 2 Replace the system board as descri...

Page 137: ...y on page 260 D13A1xxx Get dump identity sequence 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D13B1xxx Get dump length sequence 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1FF1xxx Dump complete 1...

Page 138: ...3y03 Get array values 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1xx3y04 Stop the clocks 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1xx3y05 Flush the cache 1 Go to Checkout procedure on page 1...

Page 139: ... FRU system board and chassis assembly on page 260 D1xx3y0C Get JTAG register 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1xx3y0D Stop clocks without quiescing 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on ...

Page 140: ...stem board as described in Replacing the FRU system board and chassis assembly on page 260 D1xxB0FF Request to initiate power off program has been sent 1 Go to Checkout procedure on page 184 2 Replace the system board as described in Replacing the FRU system board and chassis assembly on page 260 D1xxC000 Indicates a message is ready to send to the hypervisor to power off 1 Go to Checkout procedur...

Page 141: ...n the table see Solving undetermined problems on page 227 4 After replacing a component verify the replacement part and perform a log repair action using the AIX diagnostics 101 711 through FFC 725 SRNs AIX might generate service request numbers SRNs from 101 711 to FFC 725 Replace any parts in the order that the codes are listed in Table 25 Note An x in the following SRNs represents a digit or ch...

Page 142: ... to Failing function codes 151 through 2E33 on page 181 to identify the failing feature 2 Run stand alone diagnostics and the problem determination procedure for your operating system 111 107 A machine check occurred Go to Performing the checkout procedure on page 184 111 108 An encoded SRN was displayed Go to Performing the checkout procedure on page 184 111 121 There is a display problem Go to P...

Page 143: ...FRU has failed Go to Performing the checkout procedure on page 184 651 170 Sensor status not available Go to Performing the checkout procedure on page 184 651 171 Sensor status not available Go to Performing the checkout procedure on page 184 651 600 Uncorrectable memory or unsupported memory 1 Examine the memory modules and determine if they are supported types 2 If the modules are supported then...

Page 144: ...re on page 184 651 632 308 Internal device error Go to Performing the checkout procedure on page 184 651 639 210 Error log analysis indicates an error detected by the I O Using the problem determination procedure failing function codes and the physical location codes from the diagnostic problem report to determine the FRUs 651 640 2D5 I O general bus error Go to Performing the checkout procedure o...

Page 145: ...kout procedure on page 184 651 712 214 System bus parity error Go to Performing the checkout procedure on page 184 651 713 214 System bus protocol transfer error Go to Performing the checkout procedure on page 184 651 714 2C4 System bus protocol transfer error Go to Performing the checkout procedure on page 184 651 715 2C4 System bus protocol transfer error Go to Performing the checkout procedure ...

Page 146: ...voltage sensor Go to Performing the checkout procedure on page 184 651 750 2D4 Service processor detected NVRAM error Go to Performing the checkout procedure on page 184 651 751 2D4 Service processor error accessing real time clock time of day clock Go to Performing the checkout procedure on page 184 651 752 2D4 Service processor error accessing JTAG COP controller hardware Go to Performing the ch...

Page 147: ...displays select sysplanar0 651 813 System shutdown due to loss of ac power to the site System resumed normal operation no action required 651 818 Power fault due to manual activation of power off request Resume normal operation 651 820 2E1 An over temperature condition was detected 1 Make sure that v The room ambient temperature is within the system operating environment v There is unrestricted ai...

Page 148: ...expansion bus parity error Schedule deferred maintenance Go to Performing the checkout procedure on page 184 652 631 307 A non critical error has been detected I O expansion bus time out error Schedule deferred maintenance Go to Performing the checkout procedure on page 184 652 632 307 A non critical error has been detected I O expansion bus connection failure Schedule deferred maintenance Go to P...

Page 149: ...tected intermediate or system bus data parity error Schedule deferred maintenance Go to Performing the checkout procedure on page 184 652 772 2D2 292 A non critical error has been detected intermediate or system bus time out error Schedule deferred maintenance Go to Performing the checkout procedure on page 184 652 773 227 A non critical error has been detected intermediate or system bus data pari...

Page 150: ...84 817 215 817 Time of day clock not running test failed Go to Performing the checkout procedure on page 184 817 217 817 Time of day clock not running Go to Performing the checkout procedure on page 184 887 101 887 POS register test failed Go to Performing the checkout procedure on page 184 887 102 887I O register test failed Go to Performing the checkout procedure on page 184 887 103 887 Local RA...

Page 151: ...n page 184 887 125 887 Fuse test failed Go to Performing the checkout procedure on page 184 887 202 887 Vital Product Data test failed Go to Performing the checkout procedure on page 184 887 203 887 Vital Product Data test failed Go to Performing the checkout procedure on page 184 887 209 887 RJ 45 converter test failed Go to Performing the checkout procedure on page 184 887 304 887 Coprocessor in...

Page 152: ...ween cascaded enclosures Go to Performing the checkout procedure on page 184 2506 4020 Configuration error connections exceed IOA design limits Go to Performing the checkout procedure on page 184 2506 4030 Configuration error incorrect multipath connection Go to Performing the checkout procedure on page 184 2506 4040 Configuration error incomplete multipath connection between controller and enclos...

Page 153: ...6 Disk Array Go to Performing the checkout procedure on page 184 2506 9022 Two or more disks are missing from a RAID 5 or RAID 6 Disk Array Go to Performing the checkout procedure on page 184 2506 9023 One or more Disk Array members are not at required physical locations Go to Performing the checkout procedure on page 184 2506 9024 Physical location of Disk Array members conflict with another Disk...

Page 154: ...ces Go to Performing the checkout procedure on page 184 2506 9075 Incomplete multipath connection between controller and remote controller Go to Performing the checkout procedure on page 184 2506 9076 Missing remote controller Go to Performing the checkout procedure on page 184 2506 9081 Controller detected device error during internal media recovery Go to Performing the checkout procedure on page...

Page 155: ...e 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 252B 715 252B Temporary adapter failure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 ...

Page 156: ...m see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 254E 201 254E 221 Adapter configuration error Go to Performing the checkout procedure on page 184 254E 601 254 Error log analysis indicates adapter failure Go to Performing the checkout procedure on page 184 254E 602 254 Error log analysis indicates an error attention ...

Page 157: ...lure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 256D 605 256D Error Log Analysis indicates permanent adapter failure is reported on the other port of this adapter 1 Check the BladeCenter management module event log If an er...

Page 158: ...el adapter card Go to Performing the checkout procedure on page 184 2604 110 2604 Enhanced Error Handling Failure on the Fibre Channel adapter card Replace the 4Gb Fibre Channel Adapter card 2604 201 2604 221 Configuration Register Test Failure for the Fibre Channel adapter card Go to Performing the checkout procedure on page 184 2604 203 2604 PCI Wrap Test Failure for the Fibre Channel adapter ca...

Page 159: ... Expansion Card 2607 201 2607 221 Configuration Register Test Failure for the Fibre Channel adapter card Go to Performing the checkout procedure on page 184 2607 203 2607 PCI Wrap Test Failure for the Fibre Channel adapter card Replace the 8Gb PCIe Fibre Channel Expansion Card 2607 204 2607 221 DMA Test Failure for the Fibre Channel adapter card Go to Performing the checkout procedure on page 184 ...

Page 160: ...ming the checkout procedure on page 184 2624 702 2624 Error Log Analysis indicates that this adapter has failed due to a failure with the uplink interface used to connect this device to the host processor system board and chassis assembly Go to Performing the checkout procedure on page 184 2624 703 2624 Error Log Analysis indicates that this adapter has failed due to a memory error system board an...

Page 161: ...pter configuration error 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E10 601 2E10 Error Log Analysis indicates adapter failure 1 Check the BladeCenter management module event log If an error was recorded by the system see P...

Page 162: ...onfiguration error 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E13 601 2E13 Error Log Analysis indicates adapter failure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST pr...

Page 163: ...stem board 2E14 201 2E14 221 Adapter configuration error 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E14 601 2E14 Error Log Analysis indicates adapter failure 1 Check the BladeCenter management module event log If an error ...

Page 164: ...pter configuration error 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E15 601 2E15 Error Log Analysis indicates adapter failure 1 Check the BladeCenter management module event log If an error was recorded by the system see P...

Page 165: ...stem board 2E21 201 2E21 221 Adapter configuration error 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E21 601 2E21 Error Log Analysis indicates adapter failure 1 Check the BladeCenter management module event log If an error ...

Page 166: ... any parts reported by the diagnostic program 3 Replace the system board 2E23 101 2E23 Register Test Failure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E23 102 2E23 VPD Checksum Test Failure 1 Check the BladeCenter managem...

Page 167: ...2E23 221 Enhanced Error Handling Failure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E23 202 241 2E23 Network link test failure 1 Check the BladeCenter management module event log If an error was recorded by the system see ...

Page 168: ...anagement module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board 2E33 701 2E33 221 Permanent adapter failure 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts rep...

Page 169: ... If no entry is found Replace the system board A01 00x Error log analysis indicates an error detected by the microprocessor but the failure could not be isolated 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A01 01x GCPU internal error 1 Check the BladeCenter ...

Page 170: ...rded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A02 01x Uncorrectable Memory Error 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A02 03x Correctable error threshold exceeded 1 Check the BladeCen...

Page 171: ... progress codes checkpoints on page 84 2 If no entry is found Replace the system board A02 12x I O Host Bridge time out error 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A02 13x I O Host Bridge address data parity error 1 Check the BladeCenter management mod...

Page 172: ...ST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A03 12x Error on System bus 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A03 13x I O Expansion bus parity error 1 Check the BladeCenter management module event log if an ...

Page 173: ...t module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A05 03x Sensor indicates a voltage outside normal range 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A05 0...

Page 174: ...ply failure 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A05 10x System shutdown due to FRU that has failed 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry...

Page 175: ...s checkpoints on page 84 2 If no entry is found Replace the system board A0D 00x Error log analysis indicates an error detected by the Service Processor but the failure could not be isolated 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A0D 06x Service Process...

Page 176: ...the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A0D 23x Loss of heart beat from Service Processor 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A0D 24x Service Processor detected a surveillance time out...

Page 177: ...he resource is unavailable due to an error System is operating in degraded mode 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A10 200 The resource was marked failed by the platform The system is operating in degraded mode 1 Check the BladeCenter management mod...

Page 178: ... for an entry around this time If no entry is found replace the system board and chassis assembly A11 50x Recoverable errors on resource indicate a trend toward an unrecoverable error However the resource could not be deconfigured and is still in use The system is operating with the potential for an unrecoverable error 1 If repair is not immediately available reboot and the resource will be deconf...

Page 179: ... A non critical error has been detected an ECC correctable error 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A12 03x A non critical error has been detected a correctable error threshold exceeded 1 Check the BladeCenter management module event log if an error...

Page 180: ...odes checkpoints on page 84 2 If no entry is found Replace the system board A12 11x A non critical error has been detected a system bus protocol transfer error 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A12 12x A non critical error has been detected an I O ...

Page 181: ... the system board A13 01x A non critical error has been detected an I O bus address parity error 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A13 02x A non critical error has been detected an I O bus data parity error 1 Check the BladeCenter management module...

Page 182: ... POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A13 12x A non critical error has been detected an error on system bus 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A13 13x A non critical error has been detected an I ...

Page 183: ...ge 84 2 If no entry is found Replace the system board A15 03x Sensor indicates a voltage outside normal range 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A15 05x Sensor indicates an abnormally high internal temperature 1 Make sure that a The room ambient tem...

Page 184: ...an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A15 19x Fan failure 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A15 20x Non critical cooling problem loss of redundant fan 1 Ch...

Page 185: ...le error 1 If repair is not immediately available reboot and the resource will be deconfigured operations can continue in a degraded mode 2 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 3 If no entry is found Replace the system board A1D 00x A non critical error has been detected Error log analysis indicates ...

Page 186: ... system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A1D 09x A non critical error has been detected a service processor error accessing vital product data EEPROM 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A1...

Page 187: ...vent log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A1D 24x A non critical error has been detected a service processor detected a surveillance time out 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is fo...

Page 188: ... 84 2 If no entry is found Replace the system board A1D 40x A non critical error has been detected Presence Detect Error Mis Plugged 1 Check the BladeCenter management module event log if an error was recorded by the system see POST progress codes checkpoints on page 84 2 If no entry is found Replace the system board A1D 50x Recoverable errors on resource indicate a trend toward an unrecoverable e...

Page 189: ...eported by the diagnostic program 3 Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 ssss 104 ssss The motor failed to restart 1 Check the BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 R...

Page 190: ...eported by the diagnostic program 3 Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 ssss 116 ssss A protocol error 1 Make sure that the device adapter and diagnostic firmware and the application software levels are compatible 2 If you do not find a problem call your operating system support person ssss 117 ssss A write p...

Page 191: ...management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 ssss 129 252B ssss software Error log analysis indicates a SCSD bus problem 1 Check the BladeCenter man...

Page 192: ...he BladeCenter management module event log If an error was recorded by the system see POST progress codes checkpoints on page 84 2 Replace any parts reported by the diagnostic program 3 Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 ssss 138 ssss Error log analysis indicates that the disk drive is operating at a higher ...

Page 193: ... Note If more than one pair of memory DIMMs are reported missing 1 Replace the memory DIMM at the physical location code that is reported 2 Replace the system board 221 System board and chassis assembly 226 System board and chassis assembly 227 System board and chassis assembly 241 Ethernet network problem 282 System board and chassis assembly 292 System board and chassis assembly Host PCI bridge ...

Page 194: ...day logic 820 System board and chassis assembly interprocessor related testing problem 887 System board and chassis assembly integrated Ethernet adapter 893 LAN adapter D01 System board and chassis assembly cache problem E19 System board and chassis assembly power supply sensor failed 2506 3Gb SAS Passthrough Expansion Card 2506 101 Adapter configuration error indicated by test failures Reconfigur...

Page 195: ...ntries that are currently stored in the management module event log This log includes entries for events that are detected by the blade servers The log displays the most recent entries first The following table shows the syntax of a nine word B700xxxx SRC as it might be displayed in the event log of the management module The first word of the SRC in this example is the message identifier B7001111 ...

Page 196: ...n a POST checkpoint see POST progress codes checkpoints on page 84 If the blade server is halted and no error message is displayed see Troubleshooting tables on page 191 and Solving undetermined problems on page 227 v For intermittent problems check the management module event log and POST progress codes checkpoints on page 84 v If the blade server front panel shows no LEDs verify the blade server...

Page 197: ...equest numbers SRNs on page 129 to identify the failing component Note When replacing a component perform system verification for the component See Using the diagnostics program on page 189 2 If you cannot perform AIX concurrent online diagnostics continue to Step 006 Step 006 Perform the following steps 1 Use the management module Web interface to make sure that the device from which you load the...

Page 198: ...sources that fail during system startup could cause the startup problem in the partition Make sure that there are enough functioning processor and memory resources in the system for all the partitions 2 Check the bus and virtual adapter allocations for the partition Make sure that the partition has load source and console I O resources 3 Make sure that the Boot Mode partition properties are set to...

Page 199: ...lade server firmware is at the latest version v SOL is enabled for the blade server v The CD or DVD drive is selected as the first boot device for the blade server 4 Insert the stand alone diagnostics CD into the CD or DVD drive 5 Turn on the blade server and establish an SOL session Note It can take from 3 to 5 minute to load the stand alone diagnostics from the CD Please be patient The screen wi...

Page 200: ...pplicable and enter the subnet mask If there is no gateway between the NIM server and the client set the gateway address to 0 0 0 0 See your network administrator to determine if there is a gateway f If the NIM server is set up to allow pinging the client system use the Ping Test option on the Network Parameters menu to verify that the client system can ping the NIM server Note If the ping fails s...

Page 201: ... you want to run another test press F3 again to return to the Function Selection menu v System Verification a From the Function Selection menu select Diagnostic Routines and press Enter b From the Diagnostic Mode Selection menu select System Verification c Select the resource to be tested and press F7 Commit d Record any results provided and go to Service request numbers SRNs on page 129 to identi...

Page 202: ...ry the boot Note If Network is selected the blade server will try to boot from both Ethernet ports on the system board c If this boot attempt fails do the following 1 If you are attempting to boot from the network go to Step 002 2 If you are attempting to boot from the CD or DVD drive go to Step 003 3 If you are attempting to boot from a hard disk drive go to Step 004 2 If you are attempting to bo...

Page 203: ...bout testing the blade server If you have just added new software or a new optional device and the blade server is not working complete the following steps before using the troubleshooting tables 1 Remove the software or device that you just added 2 Run the diagnostic tests to determine whether the blade server is running correctly 3 Reinstall the new software or new device General problems Identi...

Page 204: ...e diagnostic test runs successfully replace the drive you removed with a new one Intermittent problems Identify intermittent problem symptoms and corrective actions v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CRUs and which components are F...

Page 205: ...the suggested actions in the order in which they are listed in the Action column until the problem is solved v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CRUs and which components are FRUs v If an action step is preceded by Trained service technician only that step must be performed only by a trained service technician Symptom Action The amount of system me...

Page 206: ...oms and what corrective actions to take v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CRUs and which components are FRUs v If an action step is preceded by Trained service technician only that step must be performed only by a trained service ...

Page 207: ...ng system for more information Table 32 shows the procedure for isolating which PCI expansion card is failing Table 32 PCI expansion card problem isolation procedure v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved v See Chapter 3 Parts listing Type 8406 on page 229 to determine which components are CRUs and which components are ...

Page 208: ...loosened any other installed devices or cables 2 If the option comes with its own test instructions use those instructions to test the option 3 Reseat the device that you just installed 4 Replace the device that you just installed Power problems Identify power problem symptoms and what corrective actions to take v Follow the suggested actions in the order in which they are listed in the Action col...

Page 209: ...b interface to erify or the blade server was instructed through the management module Web interface to start 2 If you just installed a device in the blade server remove it and restart the blade server If the blade server now starts you might have installed more devices than the power to that blade bay supports 3 Try another blade server in the blade bay if it works replace the faulty blade server ...

Page 210: ...n action step is preceded by Trained service technician only that step must be performed only by a trained service technician Isolation Procedure Code Symptom Action LPARCFG Symbolic CRU There is a configuration problem with the system or a logical partition 1 Perform the procedure associated with the SRC code that is called out after the LPARCFG call 2 Check processor and memory allocations of th...

Page 211: ...odule 6 14 DIMM 7 Px C7 Memory module 7 15 DIMM 8 Px C8 Memory module 8 16 2 See Removing a memory module on page 244 for location information and the removal procedure 3 Install new memory DIMMs as described in Installing a memory module on page 245 See Supported DIMMs on page 4 for more information NEXTLVL Symbolic CRU Contact IBM Support PIOCARD Symbolic CRU The hardware that controls PCI adapt...

Page 212: ...management module event log A message with three procedures might be similar to the following example except that the entry would be on one line in the event log SN YL31W7120029 SYS F W CEC Hardware VPD See procedure FSPSP07 FSPSP28 then FSP0200 5000004C B15A3303 22222222 33333333 44444444 55555555 66666666 77777777 88888888 99999999 B15A3303 is the identifier word of the associated SRC The rest o...

Page 213: ...lly but the 1xxx2670 problem persists replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 CAPACTY Symbolic CRU The failing component is the management card 1 Replace the management card as described in Removing the tier 2 management card on page 255 and Installing the tier 2 management card on page 256 2 After replacing the ...

Page 214: ... correctly v Yes Go to step 3 v No Correct the memory plugging problem and continue with the next step 2 Install the blade server into the BladeCenter unit and restart the blade to verify whether the problem is solved Does the problem persist v Yes Continue with the next step v No This ends the procedure 3 Perform the following steps a Reseat all of the memory DIMMs but do not replace any memory D...

Page 215: ...d as described in Removing the tier 2 management card on page 255 and Installing the tier 2 management card on page 256 2 After replacing the card and installing the blade server in the chassis unit and before rebooting the blade server or performing other operations ensure that the initialization of the management card VPD occurs by waiting for the management module to discover the blade server O...

Page 216: ...51 FSPSP09 A problem has been detected with a memory DIMM but it cannot be isolated to a specific memory DIMM Replace the CRU called out after this FSPSP call If the CRU that is called out is a DIMM CRU perform the following procedure 1 Replace both memory DIMMs of the pair on the microprocessor that contains the failing CRU DIMM 1 Px C1 For P1 C1 replace DIMMs 1 and 3 for P2 C1 replace DIMMs 9 an...

Page 217: ...n Replacing the FRU system board and chassis assembly on page 260 FSPSP14 The service processor cannot establish communication with the server firmware The server firmware will continue to run the system and partitions while it attempts to recover the communications Server firmware recovery actions will continue for approximately 30 to 40 minutes 1 View the event log in the management module to lo...

Page 218: ...cing the FRU system board and chassis assembly on page 260 FSPSP23 The system needs to perform a service processor dump 1 Save the service processor dump to storage by using the partition dump pin control on the control panel 2 Once the dump is complete attempt to re IPL the system 3 Call IBM Support FSPSP24 The system is running in a degraded mode Array bit steering might be able to correct this ...

Page 219: ...replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 FSPSP31 The service processor has detected that one or more of the required fields in the system VPD has not initialized 1 When the system reaches the SMS set the system VPD values that are required which automatically resets the service processor 2 Power on the blade serve...

Page 220: ...exchange the memory cards of the incorrect type with those of the correct type SRC B1xx C02B A group of memory cards are missing and are required so that other memory cards on the board can be configured The additional parts in the CRU callout list include all the missing memory cards in the group To correct the error add or move the memory cards to the correct locations SRC B1xx C036 A memory car...

Page 221: ...vice Processor Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 FSPSP47 The system has detected an error within the PSI link Replace the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 FSPSP48 A diagnostics function detects an external processor interface p...

Page 222: ...that contains the failing CRU DIMM 1 Px C1 For P1 C1 replace DIMMs 1 and 3 for P2 C1 replace DIMMs 9 and 11 DIMM 2 Px C2 Replace DIMMs 2 and 4 or DIMMs 10 and 12 DIMM 3 Px C3 Replace DIMMs 1 and 3 or DIMMs 9 and 11 DIMM 4 Px C4 Replace DIMMs 2 and 4 or DIMMs 10 and 12 DIMM 5 Px C5 Replace DIMMs 5 and 7 or DIMMs 13 and 15 DIMM 6 Px C6 Replace DIMMs 6 and 8 or DIMMs 14 and 16 DIMM 7 Px C7 Replace DI...

Page 223: ...exits in the BladeCenter unit drawer as required If you cleared obstructions retry the operation 3 Verify that the fans in the BladeCenter unit are working correctly If not replace fans that are not turning or that are turning slowly If you replace fans wait for the unit to cool and retry the operation 4 If the cooling components are functioning correctly replace the system board and chassis assem...

Page 224: ...upported DIMMs on page 4 for more information NO12VDC Symbolic CRU Error code 1xxx2647 indicates that the blade server is reporting that 12V dc is not present on the BladeCenter midplane 1 Check the management module event log for entries that indicate a power problem with the BladeCenter unit 2 Resolve any problems 3 Remove the blade from the BladeCenter unit and then reinsert the blade server 4 ...

Page 225: ...ddress conflict v The software is designed to operate on the blade server v Other software works on the blade server v The software works on another server 2 If you received any error messages when using the software see the information that comes with the software for a description of the messages and suggested solutions to the problem 3 Contact your place of purchase of the software Universal Se...

Page 226: ...nd activate the light path indications Before working inside the blade server to view light path diagnostic LEDs see the Safety topic and the Handling static sensitive devices on page 234 guidelines If an error occurs view the light path diagnostic LEDs in the following order 1 Look at the control panel on the front of the blade server See Blade server control panel buttons and LEDs on page 5 v If...

Page 227: ...ansion card connector LED 10 HDD2 LED 11 DIMM 5 8 LEDs Light path diagnostics LEDs Light path diagnostics is a system of LEDs on the control panel and on the system board of the blade server When an error occurs LEDs are lit throughout the blade server If the control panel indicates an error use the descriptions of the LEDs to diagnose the problem and take corrective action Figure 6 LED locations ...

Page 228: ...t the DIMM indicated by the lit LED is a supported memory module as described on the ServerProven Web site 2 Reseat the DIMM indicated by the lit LED as described in Installing a memory module on page 245 3 Replace the DIMM indicated by the lit LED as described in Removing a memory module on page 244 and Installing a memory module on page 245 Note Multiple DIMM LEDs do not necessarily indicate mul...

Page 229: ...ce the system board and chassis assembly as described in Replacing the FRU system board and chassis assembly on page 260 CIOv expansion card error P1 C12 1Xe An I O expansion card option error occurred 1 Make sure that the I O expansion option is supported as described on the ServerProven Web site See http www ibm com servers eserver serverproven compat us 2 Reseat the I O expansion option as desc...

Page 230: ...st save the original virtual Fibre Channel vfchost data of your blade server To save the original vfchost data and the original physical Fibre Channel adapter port fcs location codes complete the following steps by using the padmin user account 1 To save the original vfchost data use the lsmap command as follows Enter the command from the command line interface on the source Virtual I O Server VIO...

Page 231: ...e appropriate vfchost To restore the vfchost mapping data complete the following steps by using the padmin user account 1 To save the new Fibre Channel adapter fcs location codes use the lsdev vpd command as follows Enter the command from the command line interface on the source Virtual I O Server VIOS lsdev vpd grep fcs tee LSDEV_OUTPUT_after1 The output might look like the following example fcs0...

Page 232: ... a power failure during a firmware update you can recover the TEMP image from the PERM image If your system hangs access the management module and select Blade Tasks Configuration Boot Mode to show the PS700 blade server in the list of blade servers in the BladeCenter unit Click the appropriate blade server and select Permanent to force the system to start from the PERM image See the documentation...

Page 233: ...te the following procedure 1 If you have not started the system from the PERM image do so now See Starting the PERM image on page 220 2 Issue the appropriate command for your operating system to reject the TEMP image v If you are using the Red Hat Linux or SUSE Linux operating system type the following command update_flash r v If you are using the AIX operating system type the following command us...

Page 234: ...am on page 186 2 From the Function Selection menu select Task Selection and press Enter 3 From the Tasks Selection List menu select Update and Manage System Flash and press Enter 4 From the Update and Manage System Flash menu select Commit the Temporary Image and press Enter 5 When the commit function is complete press F3 until the Diagnostic Operating Instructions screen is displayed then press F...

Page 235: ...er but might actually be a problem in a BladeCenter unit media tray component To check the general function of shared BladeCenter media tray resources perform the following procedure 1 Verify that the media tray select button LED on the front of the blade server is lit A lit media tray select button LED shows that the blade server is connected to the shared media tray 2 Verify that the media tray ...

Page 236: ... Troubleshoot one or more of the removable media drives if they are the only failing components a Reseat the following components v Removable media drive cable if applicable v Removable media drive v Media tray cable if applicable v Media tray 8 Replace the following components one at a time in the order shown restarting the blade server each time a Removable media drive cable if applicable b Medi...

Page 237: ...odule are correct for the blade server Some settings in the I O module are specifically for each blade server 8 Verify that the I O modules for the network interface are operating correctly Troubleshoot and replace the I O module as indicated in the documentation for the I O module 9 Verify that the management module is operating correctly See the online information center or the Problem Determina...

Page 238: ...Some IBM monitors have their own self tests If you suspect a problem with the monitor see the information that comes with the monitor for instructions for adjusting and testing the monitor To check for video problems perform the following procedure 1 Verify that the monitor brightness and contrast controls are correctly adjusted 2 Verify that the keyboard video select button LED on the front of th...

Page 239: ...ing correctly and reseating the blade server does not correct the problem complete the following steps 1 Make sure that the control panel connector is correctly seated on the system board See System board connectors on page 8 for the location of the connector 2 If no LEDs on the control panel are working replace the bezel assembly then try to power on the blade server from the BladeCenter Web inte...

Page 240: ...server configuration ever worked What changes if any were made before it failed Is this the original reported failure or has this failure been reported before v Diagnostic program type and version level v Hardware configuration print screen of the system summary v Firmware level v Operating system type and version level v Advanced Management Module service data See Advanced Management Module Messa...

Page 241: ...s listing identifies each replaceable part and its part number Figure 7 shows replaceable components that are available for the PS700 blade server Figure 7 Parts illustration Type 8406 PS700 base unit with cover Copyright IBM Corp 2010 2011 229 ...

Page 242: ... through 2E33 on page 181 1 Cover 46C7341 2 4x InfiniBand DDR Expansion Card CFFh for BladeCenter option 49Y9976 2 Combo 4Gb Fibre Channel Expansion Card 1 GB Ethernet Card CFFh PCIe option 39Y9304 2 QLogic 8 Gb Fibre Channel and 1 Gb Ethernet expansion card CFFh PCIe option 44X1943 2E12 2 QLogic 2 port 10 GB Ethernet FCoE Expansion Card CFFh PCIe option 42C1832 3 3Gb SAS Passthrough Expansion Car...

Page 243: ...rd drive filler 40K5928 Service Label 46K5891 IBM FRU CRU Label 46K5893 OEM IBM FRU CRU Label 46K5894 Cover warning label 90P4799 Miscellaneous parts kit 32R2451 3 0V Battery 33F8354 RFID Tag for North America Latin America Asia Pacific 46K5362 RFID Tag for Europe 46K5363 RFID Tag for Japan 46K5364 Chapter 3 Parts listing Type 8406 231 ...

Page 244: ...232 Power Systems Problem Determination and Service Guide for the IBM Power PS700 8406 70Y ...

Page 245: ...d operating system and then click Go Click the Download tab if necessary for device driver and firmware updates Note Changes are made periodically to the IBM Web site Procedures for locating firmware and documentation might vary slightly from what is described in this documentation v Observe good housekeeping in the area where you are working Place removed covers and other parts in a safe place v ...

Page 246: ...nt Movement can cause static electricity to build up around you v Handle the device carefully holding it by its edges or its frame v Do not touch solder joints pins or exposed circuitry v Do not leave the device where others can handle and damage it v While the device is still in its static protective package touch it to an unpainted metal part of the BladeCenter unit or any unpainted metal surfac...

Page 247: ...opic and the Installation guidelines on page 233 2 If the blade server is operating shut down the operating system 3 Press the power control button behind the control panel door to turn off the blade server See Turning off the blade server on page 7 4 Wait at least 30 seconds for the hard disk drive to stop spinning 5 Open the two release handles as shown by 1 in Figure 8 The blade server moves ou...

Page 248: ...u have not done so already install any optional devices that you want such as a SAS drive or memory modules 4 Select the bay for the blade server v See the online information or the Installation and User s Guide that comes with your BladeCenter unit to verify that the bay you choose is powered v Ensure proper cooling performance and system reliability by installing a blade server expansion unit or...

Page 249: ...he BladeCenter unit bezel Important Do not place the label on the blade server or in any way block the ventilation holes on the blade server See the online information or the documentation that comes with your BladeCenter unit for information about label placement 12 Use the SMS Utility program to configure the blade server See Using the SMS utility on page 265 13 Also use the management module to...

Page 250: ...h the cover side up 4 Press the blade cover release as shown by 1 for the base unit in Figure 10 on each side of the blade server rotate the cover on the cover pins 2 and lift the cover open 5 Lay the cover flat or lift it from the cover pins on the blade server and store the cover for future use Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power sourc...

Page 251: ...before installing the blade server Perform the following procedure to replace and close the blade server cover 1 Read the Safety topic and the Installation guidelines on page 233 2 Lower the cover so that the slots at the rear slide down onto the pins 1 in Figure 11 at the rear of the blade server Before you close the cover verify that all components are installed and seated correctly and that you...

Page 252: ...protective surface with the cover side up 4 Open and remove the blade server cover See Removing the blade server cover on page 237 5 Press the cover assembly release as shown by 3 in Figure 12 on each side of the blade server and pull the bezel assembly 4 away from the blade server approximately 1 2 cm 0 5 inch 6 Disconnect the control panel 1 from the control panel connector 2 7 Pull the bezel as...

Page 253: ... and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before installing the blade server 4 Install the blade server into the BladeCenter unit See Installing the blade server in a BladeCenter unit on page 236 Removing a drive You can remove the SAS hard disk drive ...

Page 254: ... server on a flat static protective surface with the cover side up 5 Open and remove the blade server cover See Removing the blade server cover on page 237 6 Remove the drive a Pull and hold the blue release lever 1 at the front of the drive tray b Slide the drive forward 2 to disengage the connector c Lift the drive 3 out of the drive tray Installing a drive You can install a hard disk drive in d...

Page 255: ...a flat static protective surface with the cover side up 4 Open and remove the blade server cover See Removing the blade server cover on page 237 5 Locate the connector for the drive 6 Place the drive 1 into the drive tray and push it toward the rear of the blade into the connector until the drive moves past the lever at the front of the tray Attention Do not press on the top of the drive Pressing ...

Page 256: ...rver cover See Removing the blade server cover on page 237 5 Remove the bezel See Removing the bezel assembly on page 240 6 Locate the DIMM connector that contains the DIMM that is to be replaced Attention To avoid breaking the DIMM retaining clips or damaging the DIMM connectors open and close the clips gently 7 Carefully open the retaining clips on each end of the DIMM connector and remove the D...

Page 257: ... a DIMM complete the following steps 1 Read the Safety topic and the Installation guidelines on page 233 2 Read the documentation that comes with the DIMMs 3 Shut down the operating system turn off the blade server and remove the blade server from the BladeCenter unit See Removing the blade server from a BladeCenter unit on page 235 4 Carefully lay the blade server on a flat static protective surf...

Page 258: ...Install and close the blade server cover See Installing and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before installing the blade server 14 Install the blade server into the BladeCenter unit See Installing the blade server in a BladeCenter unit on page 236 ...

Page 259: ...side up 4 Open and remove the blade server cover See Removing the blade server cover on page 237 5 Lift the expansion card 1 up and away from the 1Xe connector and out of the blade server 6 If you are instructed to return the expansion card follow all packaging instructions and use any packaging materials for shipping that are supplied to you Installing a CIOv form factor expansion card You can in...

Page 260: ...d 1 over the system board 6 Lower the card to the system board aligning the connectors on the card with the 1Xe connector on the system board 7 Install and close the blade server cover See Installing and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before inst...

Page 261: ...connector b Gently pivot the card up and out of the expansion card standoff 3 on the system board c Lift the card out of the blade server d Optional Reattach the plastic cover 1 for the PCI Express connector if it is available 5 If you are instructed to return the expansion card follow all packaging instructions and use any packaging materials for shipping that are supplied to you Installing a com...

Page 262: ...d close the blade server cover See Installing and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before installing the blade server 8 Install the blade server into the BladeCenter unit See Installing the blade server in a BladeCenter unit on page 236 9 Use the d...

Page 263: ...s gently on the clip to make sure that the battery clip is touching the base of the battery socket Installing the battery You can install the battery The following notes describe information that you must consider when replacing the battery in the blade server v When replacing the battery you must replace it with a lithium battery of the same type from the same manufacturer v To order replacement ...

Page 264: ...e it under the battery clip press the battery down into the socket 4 Install and close the blade server cover See Installing and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before installing the blade server 5 Install the blade server into the BladeCenter uni...

Page 265: ...ay the blade server on a flat static protective surface with the cover side up 4 Open and remove the blade server cover See Removing the blade server cover on page 237 5 Remove the disk drive if one is installed See Removing a drive on page 241 6 Remove the four screws that secure the drive tray 1 in Figure 24 to the system board and remove the drive tray Installing the disk drive tray You can ins...

Page 266: ...e blade server cover See Installing and closing the blade server cover on page 239 Statement 21 CAUTION Hazardous energy is present when the blade server is connected to the power source Always replace the blade server cover before installing the blade server 4 Install the blade server into the BladeCenter unit See Installing the blade server in a BladeCenter unit on page 236 Figure 25 Installing ...

Page 267: ...teps Note See 3 in System board connectors on page 8 for the location of the management card on the system board 1 Read the Safety topic and the Installation guidelines on page 233 2 Turn off the blade server and remove the blade server from the BladeCenter unit See Removing the blade server from a BladeCenter unit on page 235 3 Carefully lay the blade server on a flat static protective surface wi...

Page 268: ...te the connector on the currently installed system board into which the management card will be installed See System board connectors on page 8 for the location 3 Touch the static protective package that contains the management card to any unpainted metal surface on the BladeCenter unit or any unpainted metal surface on any other grounded rack component then remove the management card from its pac...

Page 269: ...the management card was not properly installed the power on LED blinks rapidly and a communication error is reported to the management module If this occurs remove the blade server from the BladeCenter as described in Removing the tier 2 management card on page 255 Reseat the management card then reinstall the blade server in the BladeCenter 10 A new Virtualization Engine technologies VET code mus...

Page 270: ...ng example CoD VET Information System type 7895 System serial number 12 34567 Anchor card CCIN 52EF Anchor card serial number 01 231S000 Anchor card unique identifier 30250812077C3228 Resource ID CA1F Activated Resources 0000 Sequence number 0040 Entry check EC Go to step 3 v By using Integrated Virtualization Manager IVM a Start the IVM if it is not running already b In an IVM session enter the l...

Page 271: ...on code for the new management card anchor card in my blade server The System p Capacity on Demand site then generates the code and posts the VET activation code on the website 4 Go to the Capacity on Demand Activation code web page to retrieve your code a Enter the system type which is the value of the sys_type field from the IVM or the System type field from the HMC or SDMC b Enter the serial nu...

Page 272: ...er replacement you must either update the system with the latest firmware or restore the pre existing firmware that the customer provides on a diskette or CD image Note See System board layouts on page 8 for more information on the locations of the connectors and LEDs on the system board Perform the following procedure to replace the system board and chassis assembly 1 Read the Safety topic and th...

Page 273: ...attery on page 250 10 Touch the static protective package that contains the system board and chassis assembly to any unpainted metal surface on the BladeCenter unit or any unpainted metal surface on any other grounded rack component then remove the assembly from its package 11 Install any of the components listed below that were removed from the old system board and chassis assembly v I O expansio...

Page 274: ...ethods v If this system is managed by an HMC recover the partition profile data because the blade server is in Recovery state For instructions see Correcting a Recovery state for a managed system http pic dhe ibm com infocenter powersys v3r1m5 topic p7eav aremanagedsystemstate_recovery htm Note The blade server is turned on as part of the recovery process v If this system is managed by an IVM turn...

Page 275: ... capabilities such as the update_flash command for Linux and AIX or the ldfware command for Virtual I O Server v The firmware update function of AIX diagnostics v The firmware update function of the stand alone diagnostics CD Attention Before the installation of the new firmware to the temporary side begins the contents of the temporary side are copied into the permanent side After the firmware in...

Page 276: ...r While the firmware is running POST and before the operating system starts a POST menu with POST indicators is displayed The POST indicators are the words Memory Keyboard Network SCSI and Speaker that are displayed as each component is tested You can then select configuration utilities from the POST menu v System management services SMS Use the system management services SMS utility to view infor...

Page 277: ...ect this choice to change the language that is used to display the SMS menus v Setup Remote IPL Initial Program Load Select this choice to enable and set up the remote startup capability of the blade server or partition v Change SCSD Settings Select this choice to view and change the addresses of the self configuring SCSI device SCSD controllers that are attached to the blade server v Select Conso...

Page 278: ... Other types of blade servers such as the BladeCenter HS20 Type 8678 blade server in the same BladeCenter unit as the PS700 blade server might have different Ethernet controller routing See the documentation for a blade server for information You must install a device driver for the blade server operating system to address the Ethernet controllers For device drivers and information about configuri...

Page 279: ...d a compatible switch module or pass thru module in I O module bay 3 or 4 MAC addresses for host Ethernet adapters Two integrated Ethernet controllers in the PS700 blade server provide a Host Ethernet Adapter HEA that in turn provides virtual logical host Ethernet adapters LHEAs to client logical partitions LPARs The Virtual I O Server software uses LHEAs as if they were real physical adapters The...

Page 280: ... the operating system in the blade server Before you can create a RAID array you must reformat the drives so that the sector size of the drives changes from 512 bytes to 528 bytes If you later decide to remove the drives delete the RAID array before you remove the drives If you decide to delete the RAID array and reuse the drives you must reformat the drives so that the sector size of the drives c...

Page 281: ...d Click BladeCenter PS700 to display the list of downloadable files for the blade server Chapter 5 Configuring 269 ...

Page 282: ...270 Power Systems Problem Determination and Service Guide for the IBM Power PS700 8406 70Y ...

Page 283: ...ted 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...

Page 284: ...stablish 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 Ethernet connection usage restriction This product is not intended to be connected directly or indirectly by any m...

Page 285: ...ions 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...

Page 286: ...corrective actions 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 C...

Page 287: ...aiwan 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 Electromagnetic Interference EMI Statement Korea Appendix Notices 275 ...

Page 288: ...nn vom Betreiber verlangt werden angemessene Maßnahmen zu ergreifen und dafür aufzukommen Deutschland Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten Dieses Produkt entspricht dem Gesetz über die elektromagnetische Verträglichkeit von Geräten EMVG Dies ist die Umsetzung der EU Richtlinie 2004 108 EG in der Bundesrepublik Deutschland Zulassungsbescheinigung laut dem ...

Page 289: ...y 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 represe...

Page 290: ...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 Communit...

Page 291: ...die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen wenn das Produkt ohne Zustimmung von IBM verändert bzw wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung von IBM gesteckt eingebaut werden Deutschlan...

Page 292: ...ded 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 ...

Page 293: ......

Page 294: ... Printed in USA GI11 9831 00 ...

Reviews:

No comments

Related manuals for PS700

Wacker Neuson BS 50 Repair Manual preview
BS 50
Brand: Wacker Neuson Pages: 156
Icom PS-300 Instructions preview
PS-300
Brand: Icom Pages: 2
Parkside 352083 2007 Original Instructions Manual preview
352083 2007
Brand: Parkside Pages: 78
FASTER TOOLS FSG-100 Instruction Manual preview
FSG-100
Brand: FASTER TOOLS Pages: 19
CMT ORANGE TOOLS CMT300 Instruction Manual preview
CMT300
Brand: CMT ORANGE TOOLS Pages: 116
Northern 999320 Owner'S Manual preview
999320
Brand: Northern Pages: 11
LANCMAN VS-A Series Instructions For Safe Use preview
VS-A Series
Brand: LANCMAN Pages: 32
Xantrex 42V 10A Operating Manual preview
42V 10A
Brand: Xantrex Pages: 30
YATO YT-82806 Manual preview
YT-82806
Brand: YATO Pages: 88
Parkside PARKSIDE PPHSS 715 Operation And Safety Notes preview
PARKSIDE PPHSS 715
Brand: Parkside Pages: 10
OfiTE 170-00-4S Instruction Manual preview
170-00-4S
Brand: OfiTE Pages: 20
Fein AFSC18Q Instruction Manual preview
AFSC18Q
Brand: Fein Pages: 59
Pattfield Ergo Tools E-AS 10,8 V Li Operating Instructions Manual preview
E-AS 10,8 V Li
Brand: Pattfield Ergo Tools Pages: 56
KRAUSMANN U78012-00 Operation Manual preview
U78012-00
Brand: KRAUSMANN Pages: 20
Deprag 347-218-31 Operating Instruction Booklet preview
347-218-31
Brand: Deprag Pages: 40
Eaton Vickers VT16 Overhaul Manual preview
Vickers VT16
Brand: Eaton Pages: 11
NEBO PAL+ 6715 User Manual preview
PAL+ 6715
Brand: NEBO Pages: 2
Parkside 353304 2007 Original Instructions Manual preview
353304 2007
Brand: Parkside Pages: 46

Brands by name

Popular brands

Load more brands