1. Installation and troubleshooting overview
Welcome to the topic - BladeCenter Installation and Troubleshooting Overview.
© Copyright IBM Corporation 2009

2. Unit objectives After completing this unit, you should be able to:
Identify the BladeCenter components used to provide PD information
List the planning elements required for the BladeCenter management network
Select the functions available to modify firmware settings
List the blade server indicators and Light Path Components
Select the steps appropriate in diagnosing blade server hardware failures
Identify the utility to use in displaying BladeCenter component health
Upon completion of this unit, you should be able to accomplish the following objectives:
Identify the BladeCenter components used in providing PD information
List the planning elements required for the BladeCenter management network
Select the functions available to modify firmware settings
List the Blade Server indicators and Light Path Components
Select the steps appropriate in diagnosing Blade Server hardware failures
Identify the utility to use in displaying BladeCenter component health
© Copyright IBM Corporation 2009

3. Best practices Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
Our next section identifies components and offers features to help troubleshoot issues that can occur on the blade server.
© Copyright IBM Corporation 2009

4. BladeCenter chassis questions: Requirements
Given your specific needs, what is the best BladeCenter solution (in terms of components) necessary to meet your requirements?
Define the networking and SAN requirements for your BladeCenter environment based on your existing infrastructure, including fault tolerance, throughput and interoperability.
Do you plan on having a separate Management LAN and production LAN? What is the advantage/disadvantage of this environment?
Are all of the components being installed in the BladeCenter chassis on the ServerProven list?
Is this BladeCenter chassis to be deployed locally or in a remote location?
The BladeCenter chassis serves as the foundation for a flexible combination of blade servers, network capabilities and storage options. Research and early verification of the solution will help guide in the selection for proper chassis configuration, network, power and cooling requirements.
The network environment surrounding the BladeCenter is influenced by many factors, and the selection of the proper I/O modules will be required. Similarly, the requirements for attachment to external storage will guide in the selection of storage I/O module implementation, and connection to a new or existing storage switch fabric.
Management in the BladeCenter environment centers on the Advanced Management Module, including the LAN connectivity specific to this function. Separating LAN communication between the management LAN and production in-band data LAN is a consideration that should be taken into account in the network design supporting a BladeCenter. Two important aspects to be considered are security of the management components, and access to the critical control functions required to maintain the BladeCenter environment. Providing access to the management functions of the BladeCenter on a production data network increases the risk of unauthorized access. Separation of critical control traffic in the topology of the network is also important in designing redundancy and the physical paths selected for the management network.
The IBM ServerProven list provides an initial verification of components planned for installation on an IBM server.
The BladeCenter is designed for management in both the local and remote environments. Planning for remote deployment should include an analysis of the network and operational elements necessary to manage a significant remote resource. These elements include, among others, network, security and operational procedures.
These basic questions are a starting point to illustrate the process for planning the BladeCenter installation.
© Copyright IBM Corporation 2009

5. Blade server considerations: Questions
Is the blade server at the latest firmware level? If not, what method of applying the latest firmware updates are you going to implement?
Besides the BIOS, what other firmware updates are needed for the blade server?
What operating system are you going to put on the blade server. How do I find out if this OS is supported on the blade server?
What are the different deployment methods for operating system installations, and which method makes the most sense in my environment?
What performance requirements are needed out of my blade server? Based upon these requirements, which model best fits my business needs?
Blade servers, in conjunction with the BladeCenter chassis, are designed for scalability. Adding a new server typically involves installing a new blade into an open bay in a BladeCenter chassis. The questions on this slide apply to the selection of a Blade server, and more broadly, to the considerations that apply to the BladeCenter environment and the requirements address by the Blade server.
© Copyright IBM Corporation 2009

6. BladeCenter chassis questions: Power
Do you understand the necessary power requirements for a given BladeCenter solution?
Will your BladeCenter chassis be connected to either a front-end or high-density front-end rack PDU?
How many blade servers are in the chassis and will that impact oversubscription of the power domains?
Do you have the correct electrical connectors to power your new BladeCenters and their PDUs?
When planning the power for your BladeCenter requires knowledge of your system's power requirements, the power requirements of compatible hardware, and the uninterruptible power supply needs for your BladeCenter. Therefore, there are common questions (as listed) that will need to be addressed in order to implement and distribute power for your chassis. Each BladeCenter supports a minimum of 2 or a maximum of 4 power modules that are powered using a PDU (power distribution unit). Each PDU supports the connection of 2 BladeCenter E AC power cords. Each PDU supports the connection of 3 BladeCenter H AC power cords.
When planning for AC rack power distribution, be sure to plan for enough individual power feeds and PDUs to take advantage of the redundant BladeCenter E and H power supplies.
© Copyright IBM Corporation 2009

7. Cooling questions Are the systems on a raised floor?
How many BTUs am I generating when my installation is complete?
What are the power requirements for the new systems?
Are there plans to grow in the future?
In the datacenter the basic rule is that POWER IN = HEAT OUT. If computers require more power to operate, they will also require more cooling. Therefore, we have to account for any efficiency in the power and cooling systems themselves.
BTU (British Thermal Unit) is used to give an estimate of the power of heating and cooling systems needs of a room. The BTU is a measurement of heat output from a device. The AC wattage x 3.41 = BTU where 3.41 is a constant value. Based on the heat output, or BTUs of a server, it is possible to calculate the tonnage of AC needed. The BTU divided by = AC tons to cool. BTU calculators are available on the internet.
© Copyright IBM Corporation 2009

8. Troubleshooting and problem determination
Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
This section covers Troubleshooting considerations and problem determination for the IBM BladeCenter.
© Copyright IBM Corporation 2009

9. Problem determination: Information gathering
Due to the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions.
Machine type and model
Microprocessor or hard disk upgrades
Failure symptom
Do diagnostics fail?
What, when, where, single, or multiple systems?
Is the failure repeatable?
Has this configuration ever worked?
If it has been working, what changes were made prior to it failing?
Is this the original reported failure?
Diagnostics version — type and version level
Hardware configuration
Print (print screen) configuration currently in use
BIOS level
Operating system software — type and version level
These steps are recommended in a general approach for problem diagnosis.
© Copyright IBM Corporation 2009

10. Blade servers: Diagnostics tools
Light Path Diagnostics
Standalone diagnostics
Diagnostics by PC Doctor
Test results are stored in a test log
Management Module event logs contain system status messages from the blade server service processor and can be:
Viewed
Saved to diskette
Printed
Attached to alerts
Standard log is a summary of tests
Press <Tab> while viewing the test log
Power On Self Test (POST) beep codes
Unified Extensible Firmware Interface (UEFI)
Elimination of Beep Codes
Advanced logging and firmware control
Command-line interface (CLI)
There are several means to determine whether a problem is associated with a blade server. Diagnostic tools provide helpful information such as troubleshooting a single problem that might cause several error messages. When this occurs, work to correct the cause of the first error message. Use the problem isolation tables to find solutions to problems with definite symptoms. These tables are in the Problem Determination and Service Guide for your blade server.
© Copyright IBM Corporation 2009

11. IBM Blade Server: Front panel LEDs HS22 example
Each blade server contains a front panel LEDs that helps determine if the server is operating properly as well as indicate any errors that occur:
Blade-error or Fault LED: This LED is also known as the blade system-error LED. When this amber LED is lit, it indicates that a system error has occurred in the blade server. The blade error LED will turn off only after the error is corrected.
Information LED: When this amber LED is lit, it indicates that information about a system error for the blade server has been placed in the management module event log.
Location LED: When this blue LED is on, it has been turned on in response to a programmed condition, or remotely by the system administrator, to aid in blade identification for maintenance. The location LED on the BladeCenter chassis will be illuminated as well. Turn off the location LED after maintenance is complete.
Blade-activity LED: When this green LED is lit, it indicates that there is activity on the hard disk drive or network.
Power-on LED: While the BladeCenter chassis has AC power, this green LED turns on in blinking mode and stays on when you power on your blade server. When the blade is first inserted, the LED will blink at a high frequency because the blade is being “discovered” by the Management Module (MM) at this time. As soon as the MM has logged the blade’s presence, it will decrease the frequency of the blinking, allowing for the power switch to function.
This slide illustrates the front panel components and locations for the IBM HS22 Blade Server.
IBM HS22 Blade Server Front Panel indicators and controls
HS22 Blade Server Front Panel
© Copyright IBM Corporation 2009

12. IBM Blade Server: System board diagnostic indicators HS22 example
IBM HS22 Blade server system board example
Memory, processor, and disk Indicators
Light Path Panel
The IBM blade server contains a Light Path diagnostic panel that will help you to troubleshoot system-board component problems. The service processor will control the front panel LEDs and is mounted on the blade server system board. The LEDs mounted directly on the system board that are controlled by the service processor have a back-up capacitor driven power system. This allows the LEDs to be lit through the use of a push switch (SW1 or SW4 depending on the type of blade) after the blade has been removed from the BladeCenter chassis.
In order to observe the status of the LEDs, the blade server must be removed from the chassis. Next, open the cover, and press and hold the light path diagnostics switch to help troubleshoot system-board component problems, by lighting any error LEDs that were turned on during processing. Power is available to relight the light path diagnostics LEDs for a maximum of 25 seconds after the blade-server is removed from the BladeCenter chassis. Use the information gathered and the Hardware Maintenance Manual to troubleshoot the error.
This slide illustrates the Light Path indicators and component positions for the IBM HS22 Blade Server.
In addition to the Light Path diagnostic indicators, the HS22 supports the new UEFI firmware standards for diagnostics.
As in earlier Blade Server models, a capacitive storage capability allows the indicators to be viewed when the Blade is removed from the BladeCenter chassis.
IBM Blade Server HS22 System Board Indicators
HS22 System Board Light Path Panel
© Copyright IBM Corporation 2009

13. IBM Blade Server: Front panel LEDs LS22 example
This slide illustrates the placement of front panel indicators for another current Blade Server model, the LS22.
In this configuration, the indicators and controls are located under a fold-down cover at the top of the Blade.
LS22 Blade Server Front Panel Controls and Indicators
IBM LS22 Blade Server Front Panel
© Copyright IBM Corporation 2009

14. IBM Blade Server: System board diagnostic indicators LS22 example
This example shows the LS22 system board, with the error and status indicators positioned near the components to be monitored. The Light Path panel is located towards the rear of the board.
LS22 Blade Server System Board Light Path Panel
IBM LS22 Blade Server System Board
© Copyright IBM Corporation 2009

15. IBM Blade Server: Diagnostics tools
Light Path Diagnostics
Press F2 at POST to invoke standalone diagnostics
Diagnostics by PC Doctor
Test results are stored in a test log
Management Module event logs contain system status messages from the blade server service processor and can be:
Viewed
Saved to diskette
Printed
Attached to alerts
Standard log is a summary of tests
Press <Tab> while viewing the test log
Power On Self Test (POST) beep codes
Real time diagnostics
Command-line interface (CLI)
The diagnostic tools provide helpful information such as troubleshooting a single problem that might cause several error messages. When this occurs, work to correct the cause of the first error message. Use the problem isolation tables to find solutions to problems with definite symptoms. These tables are in the Problem Determination and Service Guide for your blade server. The event log is limited in size. When the log is full, new entries will not overwrite existing entries; therefore, you must periodically clear the BMC log using the Configuration/Setup Utility program located by selecting Advanced Settings, Baseboard Management Controller (BMC) settings, and then BMC System Event Log.
© Copyright IBM Corporation 2009

16. Blade server: Basic input/output system (BIOS)
Blade server BIOS
Menu-driven setup
Settings for configuration and performance
Set, change, delete (IRQ, date and time, and Passwords)
Advanced settings for specific needs (for example, memory, CPU, PCI bus and BMC)
BIOS defaults
Flash diskette
BIOS updates for host and devices CD-ROM BIOS/firmware updates and configuration for host and devices
BIOS system board jumpers or switches
BIOS boot selection
Password override
Wake on LAN enablement
Each blade server has a BIOS. When troubleshooting, ensure that the blade server is operating on the latest released BIOS code updates. Use the BIOS program to change system settings, such as interrupt requests (IRQ), date and time and passwords.
System board switches/jumpers commonly control functions including primary/backup BIOS selection, password override allowing for reset and Wake on LAN selection.
© Copyright IBM Corporation 2009

17. UEFI: Unified Extensible Firmware Interface (1 of 3)
The next generation of BIOS
Allows OSs to take full advantage of the hardware
Architecture independent
Modular
64-bit code architecture
16 TB of memory can be addressed
More functionality
Adapter vendors can add more features in their options (for example, IPv6)
Design allows faster updates as new features are introduced
More adaptors can be installed and used simultaneously
Fully backwards compatible with legacy BIOS
Better user interface
Replaces ctrl key sequences with a more intuitive human interface
Moves adaptor and iSCSI configuration into F1 setup
Creates human readable event logs
Easier management
Eliminates “beep” codes; all errors can now be covered by Light Path
Reduces the number of error messages and eliminates out-dated errors
Can be managed both in-band and out of band
The IBM HS22 Blade Server incorporates the new Unified Extensible Firmware Interface (UEFI).
The Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an operating system and platform firmware. UEFI is intended as a significantly improved replacement of the old legacy BIOS firmware interface historically used by PC compatible personal computers. UEFI allows operating systems to take full advantage of the hardware by being architecture independent and module in design allowing 64 bit code architecture and 16 TB of memory to be addressed. Adapter vendors can add more features in their options such as IPv6 and the design allows faster updates as new features are introduced. More adaptors can be installed and used simultaneously and it is fully backwards compatible with legacy BIOS. UEFI provides a better user interface by replacing control key sequences with a more intuitive human interface and moving adaptor and iSCSI configuration into F1 setup. Creation of human readable event logs is also a feature. Easier management is also enabled. UEFI eliminates “beep” codes and all errors can now be covered by Light Path. It reduces the number of error messages and eliminates out-dated errors and can be managed both in-band and out of band 17
© Copyright IBM Corporation 2009

18. UEFI: Unified Extensible Firmware Interface (2 of 3)
Today’s update and configuration on systems
Tomorrow’s update and configuration on systems
BMC
RSAII
Diags
BIOS
xFlash
ASU
Configuration
Update
&
IMM
Pb DSA
UEFI
Configuration
Update
&
xFlash
ASU
Currently, the legacy BIOS updates and configuration changes (ASU) are only available form the OS. With UEFI, the updates and configuration changes will be available from the OS as well as remotely via the IMM, providing improved access, content availability, coverage and consolidation of information. 18
© Copyright IBM Corporation 2009

19. UEFI: Unified Extensible Firmware Interface (3 of 3)
UEFI versus BIOS
UEFI
BIOS
64 bit code architecture: 16 TB of memory can be addressed
16 bit code architecture: Only 1MB of memory can be addressed.
Eliminates Code Space Constraints. Adapter Option ROMs can be loaded anywhere in memory with no size restrictions.
Adapter Vendors must fit all option code into a shared 128K. Limits the number of adapters that can be effectively installed.
Adapter vendors are free to add function. i.e. IPV6
Vendors are limited in the function they can provide in the option ROM.
UEFI defines a Human Interface that is being extended to Adapter Vendors.
Cryptic Ctrl Key sequences required for configuring Adapters.
iSCSI Configuration is in F1 Setup and consolidated in to ASU.
iSCSI Configuration requires separate tool.
Elimination of Beep Codes – All Errors covered by Light Path. Reduction in Number of Error Messages.
Multiple Beep Codes for fundamental failures.
Adapter Configuration can move into F1 Setup. Eliminates Ctrl Key sequences for configuring Adapters.
Advanced Settings Utility (ASU) has partial coverage of F1 Settings
In & Out of Band UEFI Updates. Settings accessed Out of Band via ASU and the IMM.
In-Band only updates via DOS, wFlash, or lFlash.
UEFI Event codes available out of band. Human readable Event logs in F1 Setup
Numerous Legacy POST Errors.
This table presents a comparison between the new UEFI and legacy BIOS. 19
© Copyright IBM Corporation 2009

20. Blade server: Integrated Management Module (IMM)
Replacement for BMC
LAN over USB
OS drivers included in Windows and Linux
The Unified Extensible Firmware Interface (UEFI) replaces legacy BIOS in System x and Blade Servers (currently the HS22), and is the new interface between operating systems and platform firmware. UEFI provides a modern, well defined environment for booting an operating system and running pre-boot applications.
Unified Extensible Firmware Interface improvements over legacy BIOS:
Advanced Settings Utility (ASU) will now have more complete coverage of system settings.
On rack mount servers, UEFI Settings can be accessed Out of Band via ASU and the Integrated Management Module (available on the HS22 Blade).
Adapter configuration can move into F1 Setup, for example iSCSI Configuration is now in F1 Setup and consolidated in to ASU
Elimination of Beep Codes – All Errors covered by Lightpath
DOS tools are no longer required or officially supported
The Integrated Management Module (IMM) service processor provides competitive, standards based systems management enabling upward integration into wide variety of enterprise management environments "out of the box".
Integrated Management Module provides RSA II functionality and Remote Presence in addition to the following new functions:
Standard CIM and WS-Man interfaces
OS drivers included in Windows and Linux, no additional device drivers needed
Single firmware image for IMM across the product set
Choice of dedicated or shared Ethernet connections
LAN over USB
Unlike the BMC and RSA-II, the IMM does not require IPMI device drivers or USB daemons for in-band IMM communication. Instead, a LAN over USB interface
enables in-band communications to the IMM; the IMM hardware on the system board presents an internal Ethernet NIC from the IMM to the operating system.
LAN over USB is also called the ″USB in-band interface″ in the IMM Web interface.
© Copyright IBM Corporation 2009

21. Blade server six system statesAC
AC/DC
POST
NOS
Start
Complete
Stop
System State
Data Gathering
Data Analysis 1
There is no AC
Visual
PDSG 2
There is AC power but no DC
Advanced Management Module (AMM) & (IMM)
Light Path
System event log 3
There is AC and DC power but the system fails to complete post
Checkpoint codes
F1 and F2
Beep codes (prior to UEFI)
Adapter BIOS messages
Retain tips
IBM Support Web site 4
There is AC and DC power, the system completes POST but the NOS fails to start loading
F2 diagnostics 5
There is AC and DC power, the system completes POST but the NOS fails to complete loading
NOS boot messages
'Blue Screen'
'Safe' mode
NOS Vendor messages 6
There is AC and DC power, the system completes POST and the NOS completes loading but stops during operation
DSA
NOS event logs
A server will be in one of six system states when you are called to provide service. The system states are based around what happened when the system was last started. Each system state has tools available to diagnose problems. These diagnostic tools are carried forward from the previous state to the next state. So that the diagnostic tools in system state one are available in system states two, three, four, five and six. System state two has additional tools that are available in system states three, four, five and six.
© Copyright IBM Corporation 2009

22. Advanced Management Modules (AMM): Overview
The Management Module stores all event and error information for the BladeCenter
The Management Module configuration data is stored both in itself and on the midplane
To reset the IP address back to the default settings, press and hold the IP reset button for 3 seconds or less
Power-on LEDS
Activity LEDS
Error LEDS
Serial Console Connector RJ45
Release handle
Whether you are configuring a new BladeCenter, modifying the settings of an existing BladeCenter, or trying to find out what is causing a problem in a BladeCenter, the Advanced Management Module, also referred to as the management module is always the starting point. In a new chassis, the management module is the only accessible module in the chassis. It’s IP address is a known commodity and it can be accessed by a Web browser.
In order for a BladeCenter to be able to recover from a management module failure, the configuration settings must be stored in more than one location. All the configuration settings for the management module are copied to non-volatile memory (NVRAM) on the BladeCenter midplane. By doing this, when a genuine hardware failure occurs in the management module, a new one can be swapped in and it will automatically adopt the chassis settings without the need to manually apply setting changes. However, because of this design, a problem can arise if a login information or IP address information has been forgotten.
Video Connector
10/100 Ethernet Connector RJ45
Port Link LED
Port Activity LED
Advanced Management Module LEDS
USB Dual Stack
Pin-hole Reset
MAC Address
© Copyright IBM Corporation 2009

23. Recovering Management Module TCP/IP address
MM configuration data is stored in the midplane
To reset a TCP/IP address only:
Remove the cable from the MM Ethernet port
Press and hold the IP reset button for 3 seconds or less
TCP/IP address will reset to /
Simply replacing the MM will cause the replacement MM to adopt the same values as the original MM
PERFORM ALL RESET STEPS BEFORE REPLACING THE MM
In order for a BladeCenter to be able to recover from a MM failure, the configuration settings must be stored in more than one location. All the configuration settings for the MM are copied to non-volatile memory (NVRAM) on the BladeCenter midplane. By doing this, when a genuine hardware failure occurs in the MM, a new MM can be swapped in and it will automatically adopt the BladeCenter settings without the need to manually apply setting changes.
This is by design. However, this behavior can cause a problem where a client has forgotten either the user ID/password combination or the TCP/IP address or both and calls for assistance.
By pressing the IP reset button on the MM with a small probe, it is possible to reset the MM to the default TCP/IP address. The client will be able to logon to the MM, make any changes (e.g. set a new static TCP/IP address) and save the changes. Saving the changes will also update the midplane data to match. It will be a good practice at this time for the client to scan the SEL for errors to assist in the PD process before moving on.
© Copyright IBM Corporation 2009

24. Management Module full reset: Factory defaults
MM configuration data is stored in the midplane
To force a complete MM reset (including password):
Remove the cable from the MM ethernet port
Press and hold the IP reset button for 5 seconds
Release the IP reset button for 5 seconds
Press and hold the IP reset button for 10 seconds
TCP/IP address will be reset to /
All IDs and passwords will be deleted (except USERID/PASSW0RD)
Simply replacing the MM will cause the replacement MM to adopt the same values as the original MM
PERFORM ALL RESET STEPS BEFOIRE REPLACING THE MM
Using the 5-in, 5-out, 10-in method will completely reset the MM and the Midplane NVRAM, losing all client changes.
It is not acceptable to replace a MM because a client is unable to logon. MM failures are not common. Before dispatching a new MM, Ask the client to perform a full reset then attempt a logon using all factory default settings. If it is still not possible to logon after a full factory reset, there may be a genuine hardware problem with the MM.
© Copyright IBM Corporation 2009

25. Advanced management event log
The Advanced Management Module event log contains messages that are generated while the advanced management module is monitoring the BladeCenter S system or during the built-in self test (BIST) process that runs when a BladeCenter S system device powers on.
Messages in the event log have the following format:
Severity error level. The severity level can be Information (I), Warning (W), or Error (E).
Source. The source device that generated the message, such as SERVPROC for the advanced management module or BLADE_xx for blade servers, where xx is the blade server number.
Timestamp. Date and time that the message was generated.
Text description. Text describing the message.
© Copyright IBM Corporation 2009

26. Problem determination: Blade server example
Example of a memory DIMM problem
Display of BladeCenter Front Panel LEDs
This diagram illustrates a problem encountered when a memory DIMM was installed in the wrong DIMM slot. The initial indication included an amber light on both the BladeCenter chassis, and on the operator panel of the HS21. To diagnose the problem, the BladeCenter Management module remote web interface was used.
Management Module web interface indicating error LEDs
© Copyright IBM Corporation 2009

27. Problem determination: Blade server example
Example of a memory DIMM problem
Display of the Blade server front panel LEDs
In this diagram the Blade server Front Panel LEDs as indicated by the Advanced Management Module, further identifying which Blade server contains the error.
Advanced Management Module Blade server LEDs
© Copyright IBM Corporation 2009

28. Problem determination: Blade server example
Example of a memory DIMM problem
Display of the BladeCenter Event Log
Here we have an Event Log error message expanding details of a memory error detected.
Using the error code from the BladeCenter Error Log, the error code reported can be matched to table supplied in the Problem Determination Guide, found on the IBM Internet web site. For some messages, the event log will display a message beginning with the word “Recovery” and followed by the same text as the original message when a problem has been resolved.
By default, entries are sorted by timestamp, which the most recent entries listed first. You can sort the entries by severity, source, or timestamp by clicking on the appropriate column heading. In addition, you can filter entries based on severity, source, or date. Note: When attempting to resolve problems using the messages in the event log, review messages with earlier timestamps before taking action on more recent messages. You should always refer to the IBM BladeCenter Type 8886 Problem Determination and Service Guide (PDSG) for information on working with the event logs.
Advanced Management Module Event Log
© Copyright IBM Corporation 2009

29. Problem determination: Blade server example
Using the IBM Problem Determination guide - IBM BladeCenter HS21
Locate the error symptom code in the log (in this example: 289)
Match the table entry to the code
Check POST error log for error message 289:
After diagnosing the DIMM problem, use the error code from the BladeCenter Error log, the error code reported can be matched to table supplied in the IBM BladeCenter HS21 Problem Determination guide, found on the IBM Internet web site.
© Copyright IBM Corporation 2009

30. Problem determination: Blade server example
Consult the IBM Installation Guide for the HS21
Proper DIMM installation procedure
The problem determines that the second DIMM was placed in connector 2, J142 and should have been in connector 3, J143.
HS21 DIMM Installation slot and order
© Copyright IBM Corporation 2009

31. Problem determination: Blade server example
Verifying fix and proper operation
Following the corrective action taken after consulting the HS21 Users Guide, the Advanced Management Module (AMM) displays of the overall Blade server status and Event Log indicate that the Blade server is now functioning normally.
AMM Status Display and Event Log
© Copyright IBM Corporation 2009

32. Problem determination: Blade servers
What do you do if:
Blade server powered down for no apparent reason
Blade server does not power on, the system-error LED on the BladeCenter system-LED panel is lit, the blade error LED on the blade server LED panel is lit, and the system-error log contains the following message: ″CPUs Mismatched″
Some components do not report environmental status (temperature, voltage)
Switching KVM control between blade servers gives USB device error
The actions in problem determination are dependent upon the symptoms of the problem. Here are some examples of problems that could occur and what you could do to solve the problem Please note that this is not a complete list of possible problems, and the solutions come from the “Hardware Maintenance Manual and Troubleshooting Guide”.
Blade servers power down for no apparent reason.
All blade bays must have a blade server, expansion unit, or filler blade in them. Blade bays that do not have these items installed or have them installed improperly disturb airflow in the BladeCenter unit with an adverse effect on BladeCenter unit cooling. If the BladeCenter unit begins to overheat, blade server processors will begin to slow down and will eventually power down the system.
Blade server does not turn on, the amber system-error LED on the BladeCenter system-LED panel is lit, the amber blade error LED on the blade server LED panel is lit, and the system-error log contains the following message: ″CRUs Mismatched″.
The problem occurs after installing the second microprocessor option or after replacing a failed microprocessor in a two-way Blade server. The processor with the lowest feature set and stepping level must be used as the Bootstrap Processor (BSP). This is Microprocessor 1 in location U66. Move the microprocessor in location U66 to location U70, and move the microprocessor in location U70 to location U66.
Some components do not report environmental status (temperature, voltage).
The green status dot for a component is not automatically a link to environmental information (temperature and voltage) for the component. Only the management module and blade servers have environmental information, and only the green dot for those components contains a link to environmental information.
Switching KVM control between blade servers gives USB device error.
If a blade server is under heavy load, it can take several minutes before it enumerates the USB devices connected to it. If control of the KVM and media tray is switched away from the blade server before this enumeration is complete, a USB device installation error might be displayed. Do not switch KVM control between blade servers until the mouse and keyboard are both working on the blade server that has control of the KVM and media tray.
© Copyright IBM Corporation 2009

33. Ethernet switch modules: Addressing issues
What do you do if:
You have duplicate IP address reported on the ESM
You have duplicate IP address reported on the blade server
You have a native VLAN mismatch reported on the ESM
There are connection problems to the blade servers
The DHCP server uses up all IP addresses and the blade server still cannot get an address
Before going into detail about troubleshooting, it is important to first discuss certain common rules and symptoms for this environment. Certain interactions within the BladeCenter between the ESM and the Management Module require that certain important rules be followed. Failure to follow these rules can produce unexpected results when deploying the BladeCenter containing an ESM. Above are some common issues with the Ethernet switch modules.
Duplicate IP address reported on the ESM
Cause: IP address changed directly on the ESM rather than via Management Module.
Solution: Change IP address to desired setting for the ESM on Management Module and click Save.
Duplicate IP address reported on the blade server
Cause: Server using same VLAN as the ESM management VLAN; Management Module proxying for all addresses on that VLAN and confusing server.
Solution: Separate VLANs, use a different VLAN for the ESM than for any of the data VLANs going to the servers.
Native VLAN mismatch reported on the ESM
Cause: 1) Multiple ESMs in a BladeCenter, and at least one of the ESMs is on a different management VLAN than other ESMs in the same BladeCenter. 2) Upstream trunked and upstream switch using different native VLAN than the ESM.
Solution: 1) Place all ESMs in a BladeCenter into the same management VLAN
2) Be sure that both sides of the external connection agree on a common native VLAN.
Connection problems to the blade servers
Cause: One cause might be that the VLANs not configured to be carried from servers to other devices.
Solution: Make sure desired VLAN is being carried from the blade server to destination.
DHCP server uses up all IP addresses and blade server still cannot get an address
Cause: Servers using same VLAN as the ESM management VLAN, Management Module proxying for all addresses on that VLAN and confusing DHCP server.
Solution: Separate VLANs; do not use any of the data VLANs going to the servers for the ESM VLAN
© Copyright IBM Corporation 2009

34. Problem determination: Ethernet switch I/O modules
Hardware failures
Not very common
On MM, look under I/O Module Tasks -> Power/Restart to see diagnostic code after reboot. Also look at fault LED on the Ethernet Switch Module
Software Failures
As with all products, software bugs do exist
Reference the latest code readme file for a list of resolved bugs with each release of code
Misconfiguration of Ethernet Switch Module or other component
This is the most common issue encountered
Often requires close cooperation between different administrative groups to resolve
Because of the highly integrated nature of the Ethernet Switch Modules (ESM) within the BladeCenter, it is usually necessary to engage several teams for anything beyond basic hardware troubleshooting. There are three types of failures that can occur on an ESM: hardware failures, software failures and mis-configuration. When verifying the hardware, it is important that you verify the LEDs. While the switch is executing POST, both OK and Fault LEDs will be lit. When the Power-On Self-Test (POST) completes successfully the Fault LED will turn off.
© Copyright IBM Corporation 2009

35. Ethernet switch modules: Configuration issues
Most common issue encountered
May be with the Ethernet Switch Module, a device upstream or the server within the BladeCenter
May also be misconfiguration on the Management Module
Same tools used to troubleshoot configuration issues can also be used to help isolate broken hardware and software bugs
Usually requires close cooperation between network administrators and server administrators
Often helps to have special tools (for example, network sniffer) to understand and resolve problem
The most common support issue is miss-configuration. This is often very time consuming to fix and often requires close operation between different vendors.
© Copyright IBM Corporation 2009

36. Ethernet switch modules: Basic rules
Do not attach cables to the ESM until both sides of the connection are configured
Do not put the blade servers on the VLAN that the ESM uses for its management VLAN interface
Make sure the ESM firmware (IOS) code is upgraded
Decide the ESM management path (via Management Module or ESM uplinks) and configure for it
Do not attach cables to the ESM until both sides of the connection are configured.
Symptoms: No upstream connectivity, upstream network failure from spanning tree loop.
Solution: Keep cables disconnected or ports shut down until properly configured on both sides of the connection. This is an important best practice for any switch-to-switch connections in a production network, not just between the ESM and its upstream connections.
Do not put blade servers on the VLAN that the ESM uses for its management VLAN interface.
Symptoms: Duplicate IP addresses reported on blade servers, unstable connectivity to blade servers, blade servers unable to obtain a DHCP address, DHCP server unexpectedly using up all of its IP addresses. Various unexpected connectivity issues to blade servers.
Solution: Use separate VLANs for data and management.
Make sure the ESM firmware Input/Output Supervisor (IOS) code is upgraded.
Symptoms: Any unexpected issue or missing features (Trunk Failover, load balancing, etc).
Solution: Review firmware readme file for latest version of code. Upgrade to latest release of IOS.
Decide the ESM management path (via Management Module or the ESM uplinks) and configure for it.
Symptoms: Intermittent or no connectivity to the ESM IP address.
Solution: Review management path solutions and decide which one best fits your environment.
© Copyright IBM Corporation 2009

37. BladeCenter management interfaces
Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
Our next section identifies components and offers features to help troubleshoot issues that can occur on the blade server.
© Copyright IBM Corporation 2009

38. BladeCenter AMM: System status screen
Navigation menu
Main information window
Assuming the client or Service Support Representative (SSR) is able to logon to the AMM, the System Status screen will appear by default. From here, a ‘snapshot’ of the BladeCenter is presented. Other screens will display detailed information about the health of the BladeCenter and its components. Not that, in the above example, a. green circle indicates that all components are nominal. A cross in a red box would indicate a failure condition and a yellow triangle indicates a non-critical problem. This plus the three other ‘status’ screens hold a wealth of information that will help to isolate the cause of problems on BladeCenter.
© Copyright IBM Corporation 2009

39. System Event Log (SEL) screen
This screen shows event history of the BladeCenter
The system event log (SEL) is a critical part of problem handling. The SEL captures events from a number of sources.
Each blade server has a local service processor that monitors and controls functions relevant to the local host (the blade server itself). If the local SP needs to report a fault, the fault information is passed through the midplane to the AMM and stored centrally.
Similarly, the switch modules in the BladeCenter can report status and fault information to the AMM. When working with the SEL, it is possible to ‘filter’ the log file to concentrate on just one blade server or one switch or to filter only critical errors. In this way, you can use the SEL to focus in on a potential source for the problem at hand.
© Copyright IBM Corporation 2009

40. Hardware Vital Product Data (VPD)
This screen shows information relating to the hardware in the BladeCenter
The hardware VPD shows what the AMM has recognized as being installed in the BladeCenter. If a device is inserted into the BladeCenter and is not recognized by the AMM, it cannot be used. This list acts as an inventory of what is physically present in the chassis. Discrepancies between this inventory and what is physically present may point to faulty hardware or a bad insertion of the device.
© Copyright IBM Corporation 2009

41. Rules for I/O module management
In-band management
Use the AMM path to an I/O module
Provides centralized management of all I/O modules
All activities and reporting is through a single Ethernet port
Makes LAN configuration easier
Requires MM and all I/O modules to be on the same IP subnet
Out-of-band management
Requires enablement of external management over all ports
May require management VLAN configuration
Access will involve many Ethernet ports
I/O module need not be on the same IP subnet as the MM
If subnets are different, AMM path to I/O module is unavailable
In-band management
The IBM BladeCenter I/O Modules can be managed In-band or Out-band. To manage the IBM BladeCenter I/O Modules In-band the AMM and all I/O modules are required to be on the same IP subnet. Use the Advanced Management Module path to mange all I/O modules, this provides a centralized management of all I/O modules and make:
All activities and reporting is through a single Ethernet port
Makes LAN configuration easier
Out-of-band management for the I/O Modules requires enablement of external management over all ports and may require management VLAN configuration. This makes access involves many Ethernet ports. Unlike in-band management the I/O module need not be on the same IP subnet as the AMM, If subnets are different, AMM path to I/O module is unavailable.
© Copyright IBM Corporation 2009

42. I/O module tasks: Close up
On the left of this picture are the configuration options that are given for customising the operations of each switch.
Admin/Power/Restart: From this submenu, users can apply power to or remove power from a switch.
Configuration: A basic interface allows the user to check and change the IP address of each module. Notice in the red circle the default settings for a module plugged into switch bay #1. The default IP address changes according to the bay where the module is inserted.
Firmware Update: Use this panel to update firmware components on a specific I/O module. You first need to download the latest firmware files from the IBM support web site. Then select a target module using the Target pulldown and complete the following steps. Note that only I/O modules that support flashing over the AMM web GUI are listed in the Target pulldown.
The firmware can be updated using a local or a remote file.
By selecting the Advanced Switch Management link, more options are given.
© Copyright IBM Corporation 2009

43. I/O module tasks: Advanced switch management
This screen shows the submenu of the advanced management for an ethernet switch module. From here, the results of the POST test for the device can be seen. To verify the communication path between the switch and management module, a ping test is also available.
© Copyright IBM Corporation 2009

44. Ethernet switch I/O module Web interface
The Web interface to configure the Ethernet switch modules (ESM) can be accessed either through the AMM Web configuration tool (as in this picture) or by pointing a browser directly to the IP address of the ESM itself. The default IP address of the module will change according to the location of the ESM in the chassis. For bay one, the default IP address is
The same requirements of the browser for the MM Web configuration tool apply to this module with a stringent requirement on the Java plug-in that is required to be at 1.4 level or higher.
When connecting to the module, the user will be asked to login and the combination of userid and password (the userid and password defaults vary by manufacturer. For Cisco, it is USERID AND PASSW0RD all in capital letters and with a zero instead of an “0”, for BNT, it is admin, admin).
Both the documentation coming with the switch and the on-screen Help (available by clicking on the blue circle with the question mark inside) have a comprehensive explanation of each of the tasks.
© Copyright IBM Corporation 2009

45. CIGESM Web interface
The Cisco Intelligent Gigabit Ethernet Switch Module (CIGESM) uses a Cisco-provided Web interface for graphical management of the switch.
Initial setup is performed via the MM interface:
Configure IP address
Enable external ports (disabled by default)
Management is performed using http or telnet directly to the switch
Configure the switch
Gather the switch log
Upgrade switch firmware (Trivial File Transfer Protocol (TFTP) only)
Download and upload switch configuration (backup)
© Copyright IBM Corporation 2009

46. Nortel ESM Web interface
Nortel switches use the Blade Network Technologies (BNT) Web Graphical User Interface (GUI) for management.
Initial setup is performed via AMM interface:
Configure IP address
Enable external ports (disabled by default)
Management is performed using telnet or http directly to the switch
Configure the switch
Gather the switch log
Upgrade switch firmware (TFTP, FTP or HTTP client)
Download and upload switch configuration (TFTP or browser)
© Copyright IBM Corporation 2009

47. Fibre Channel switch module Web interface
SAN Utility (QLogic)
Full Function GUI
SAN Browser (Qlogic)
Limited functionality
Switch Explorer (Brocade)
There are three Fibre Channel Switch Module (FSCM) GUI tools. Note: Default userid and password is USERID/PASSW0RD for all three interfaces.
Storage Area Network (SAN) Utility
SAN Utility is a graphical (Java) application that can be installed on many operating system to allow for an intuitive monitoring and control of SAN fabric environments. By using this tool, customers can control the settings for:
Ports which shows port state, speed, modes (F, FL, TL, G or GL) and buffer-to-buffer credits.
Zoning. A zone is a set of ports or devices grouped together to control the exchange of information. A set of zones grouped together creates a zone set. The active zone set defines the zoning for a fabric.
Network which includes the IP address, subnet mask, gateway address, boot method and SNMP configuration of the Fibre Channel Switch Module.
Additionally, diagnostic functionalities have been embedded into the product to allow for easier troubleshooting.
SAN Browser and Switch Explorer
SAN Browser offers the same capabilities as SAN Utility except:
No wizards
Single fabric connection (includes all switches in the same fabric)
No Performance Viewer Access
No view file saving or loading
© Copyright IBM Corporation 2009

48. Firmware updates and settings
Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
There will be occasions when a client needs to update firmware on some BladeCenter components. It is possible to update blade server firmware manually, using bootable diskettes. However, this is very time consuming and not practical in a large BladeCenter environment.
Given the complex nature of the BladeCenter, IBM has developed a number of tools to achieve this task with a minimum of effort on the client’s part. This section describes the options available for flashing and managing firmware in the BladeCenter environment.
© Copyright IBM Corporation 2009

49. UpdateXpress CD-ROM package
Bootable CD-ROM
Supports maintenance of system firmware and Windows device drivers
Automatically detects current device-driver and firmware levels
Gives the option of selecting specific upgrades or allowing UpdateXpress to update all of the system levels it detected as needing upgrades
Can be installed using local DVD or over network using the AMM
IBM UpdateXpress System Packs facilitate the download and install of all drivers and firmware for a given system and ensure that you are working with a complete set of updates which have been tested together by IBM. They allow you to apply co-requisite and dependent code components together and provide a convenient methodology for you to ensure that your entire system is up to date.
© Copyright IBM Corporation 2009

50. UpdateXpress firmware update scripts
UpdateXpress Firmware Update Scripts for BladeCenter (UXBC)
Process that enables firmware updates to be run in a remote, unattended fashion
Requires a management station and supporting software
Windows or Linux OS
FTP and TFTP servers somewhere on the management LAN
UXBC discovery and deployment components
For more information, see
UXBC is a tool that can automatically push firmware updates to management modules and switch modules in the BladeCenter chassis. The solution consists of a top level script (ChassisUpdate.py) written in the Python scripting language, which drives other subscripts to run and push the updates to the components. It requires a management station and some supporting software and the firmware update packages as well as the discovery and deployment components of UXBC.
© Copyright IBM Corporation 2009

51. IBM preboot dynamic system analysis
Provides problem isolation, configuration analysis, error log collection
Collects information about:
System configuration
Network interfaces and settings
Installed hardware
Light path diagnostics status
Service processor status and configuration
Vital product data, firmware, and UEFI configuration
Hard disk drive health
The PreBoot Dynamic System Analysis is a non-volatile random access memory version of the of the Dynamic System Analysis tool, stored on the integrated USB memory and used by the Technical Support teams to collect system and component level information. PreBoot DSA collects information that can be viewed locally or uploaded to an IBM internal FTP server for the Technical Support teams to examine. This is the primary method of testing the major components of the server. The diagnostic programs collect the following information about the server:
System configuration
Network interfaces and settings
Installed hardware
Light path diagnostics status
Service processor status and configuration
Vital product data, firmware, and UEFI (formerly BIOS) configuration
Hard disk drive health
RAID controller configuration
Event logs for ServeRAID controllers and service processors
This image shows the options available from the main PreBoot DSA interface. For additional information about DSA PreBoot diagnostics, see the Problem Determination and Service Guide on the IBM System x Documentation CD
Note: In the IBM HS22 Blade Server, the PreBoot DSA component is implemented within the Blade firmware.
© Copyright IBM Corporation 2009

52. Advanced settings utility
Enables the user to modify firmware settings from the command line
Supported on multiple operating system platforms
Enables remote changes to POST and BIOS settings
Does not require F1 access to a console session
Supports scripting through a batch processing mode
Does not update any of the firmware code
For more information, see
The ASU enables a user to modify firmware settings from the command line on multiple operating system platforms.
Using the utility, the user can modify user preferences and configuration parameters in the power-on self-test (POST) and basic input/output system (BIOS) code, and service processor firmware without the need to restart the server to access F1 settings.
In addition, the ASU supports scripting environments through its batch processing mode.
The Advanced Settings Utility supports the following firmware types;
BIOS code (useful for blade servers)
Remote Supervisor Adapter firmware
Remote Supervisor Adapter II firmware
IMM
© Copyright IBM Corporation 2009

53. Information gathering
Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
The next section identifies components and offers features to help troubleshoot issues that can occur on the blade server.
© Copyright IBM Corporation 2009

54. Data gathering Read the BladeCenter data collection guide
Contains details of what logs and information are needed for escalations
Contains a step-by-step guide on how the logs are collected
For more information, see
The BladeCenter data collection guide is a white paper available externally that will tell you what information is needed for BladeCenter escalations and how-to gather this information.
© Copyright IBM Corporation 2009

55. Gathering information from blade servers
Blade server logs can be gathered within the operating system
Use the following table to determine what utility to use
Type of blade server
Operating system
Type of gathering utility:
HS Series
Windows
Dynamic System Analysis
Linux
LS Series
Dynamic System Analyses
JS Series
SNAP
AIX
The Dynamic System Analysis (DSA) can be downloaded from the IBM support site. SNAP is built into AIX and SNAP for Linux on Power can be found at:
SNAP is built into AIX and SNAP for Linux on Power can be found at:
© Copyright IBM Corporation 2009

56. Gathering information from I/O switch modules
Logs from a Brocade, Cisco, BNT or QLogic switch module can be captured within the switch interface
Enable capture text/console logging within the telnet application
Login to the switch using telnet
Issue the command from the table below
To capture logs from a Brocade, Cisco, BNT or QLogic switch module, ensure that capture text or console logging has been enabled for your Telnet application. Login to the switch using Telnet. Find the command to run from the table and run it within the Telnet session.
The ‘captured’ output on your PC will contain the switch log entries.
Type of switch:
Command:
Brocade
showSupport
Cisco
show tech-support
Nortel
maint/tsdmp
Qlogic
support show
© Copyright IBM Corporation 2009

57. IBM BladeCenter support resources
Best practices
Troubleshooting and problem determination
BladeCenter management interfaces
Firmware updates and settings
Information gathering
IBM BladeCenter support resources
Our next section identifies components and offers features to help troubleshoot issues that can occur on the blade server.
© Copyright IBM Corporation 2009

58. IBM support Web site New central Web site for all server products:
Select BladeCenter from the drop-down menu
The IBM support Web site is an external site that can be accessed by our customers. It contains support information about all server platforms.
© Copyright IBM Corporation 2009

59. Documentation Hardware Maintenance Manual
Available electronically (Adobe Acrobat .PDF format) from the IBM support Web site
Primary support document for diagnostics and troubleshooting
User’s Guide, Installation Guide
System documentation that ships with the BladeCenter and with options such as blade servers and switch modules
Useful for confirming shipping group contents (missing parts, and so on) and initial customer setup
The Problem Determination and Service Guide contains information regarding hardware installation and removal, diagnostics and troubleshooting, hardware interfaces, and replacement (FRU/CRU) part numbers for the IBM BladeCenter chassis and blade servers.
Become familiar with these materials before attempting to troubleshoot a BladeCenter problem. The HMM is the definitive guide for problem isolation and repair actions.
© Copyright IBM Corporation 2009

60. IBM Blade Server references
IBM BladeCenter Products and Technology
IBM ServerProven – Compatibility for BladeCenter Products
System x Reference (xREF)
Intel Products
AMD Products
This slide provides Web sites with helpful information to support the IBM blade servers:
The IBM ServerProven® program validates selected products for compatibility with IBM System x™, BladeCenter® and xSeries® servers. Through the ServerProven Program, IBM works with industry leaders to test their equipment with ours.
System x Reference provides a detailed overview on each of the IBM System x and BladeCenter product specifications.
Intel Products link provides product information on the Intel single, dual and quad-core processors.
AMD Products link provides product information on the AMD Opteron single and dual and quad-core processors.
© Copyright IBM Corporation 2009

61. Key words Review Key Words Advanced Management Module (AMM)
Alternating Current (AC)
Basic Input/Output System (BIOS)
British thermal unit (BTU)
Central Processing Unit (CPU)
Cisco Intelligent Gigabit Ethernet Switch Module (CIGESM)
Command-line interface (CLI)
Compact Disc Read-Only Memory (CD-ROM)
Dynamic Host Configuration Protocol (DHCP)
Ethernet switch modules (ESM)
Fibre Channel Switch Module (FSCM)
File Transfer Protocol (FTP)
Graphical User Interface (GUI)
IBM BladeCenter E (Enterprise)
IBM BladeCenter H (High Performance)
IBM BladeCenter HT (High Performance Telco)
IBM BladeCenter S (Simplification)
IBM BladeCenter T (Telco)
Integrated Management Module (IMM)
Input-output (I/O)
Internet Protocol (IP)
Interrupt Request (IRQ)
Jumper (J)
Keyboard, Video, and Mouse (KVM)
Local-Area Network (LAN)
Management Module (MM)
Non-Maskable Interrupt (NMI)
Operating System (OS)
Peripheral Component Interconnect (PCI)
Power Distribution Unit (PDU)
Power On Self Test (POST)
Remote Supervisor Adapter II (RSA II)
Secure Sockets Layer (SSL)
Serial over LAN (SoL)
Servcie Pack (SP)
Service Support Representative ( SSR )
Simple Mail Transfer Protocol (SMTP)
Simple Network Management Protocol (SNMP)
Storage Area Network (SAN)
System Event Log (SEL)
Transmission Control Protocol (TCP)
Trivial File Transfer Protocol (TFTP)
Unified Extensible Firmware Interface (UEFI)
UpdateXpress Firmware Update Scripts for BladeCenter (UXBC)
Virtual Local Area Network (VLAN)
Vital Product Data (VPD)
Volt (V)
Watt (W)
Review Key Words
© Copyright IBM Corporation 2009

62. Checkpoint (1 of 2)
The _______________________ stores all major event and error information for the BladeCenter and is the starting point for PD.
Ethernet Switch Module (ESM)
AMM
BIOS
Blade Server operating system log
True/False: In planning the BladeCenter management network, bandwidth is the primary consideration.
The __________ enables the user to modify firmware settings from the command line.
True/False: While AMM management can be done through a Web interface, all switch modules must be configured using command line.
Write down your answers here: 3. 4.
© Copyright IBM Corporation 2009

63. Checkpoint solutions (1 of 2)
The _______________________ stores all major event and error information for the BladeCenter and is the starting point for PD.
Ethernet Switch Module (ESM)
AMM
BIOS
Blade Server operating system log
Answer: b
True/False: In planning the BladeCenter management network, bandwidth is the primary consideration.
Answer: False
The __________ enables the user to modify firmware settings from the command line.
Answer: Advanced Settings Utility (ASU)
True/False: While AMM management can be done through a Web interface, all switch modules must be configured using command line.
© Copyright IBM Corporation 2009

64. Checkpoint (2 of 2)
Select the correct statement regarding Blade Server status indicators.
Memory and processor LEDs are on the Blade Server front panel
All Blade Server status LEDs are on the Light Path diagnostics panel
Blade Server status and error LEDs are on the Front Panel, Control Panel and adjacent to components on the system board
Light Path status and error indicators require the Blade to be powered on
True/False: The UEFI is a functional replacement for legacy BIOS
True/False: To diagnose a Blade Server hardware problem, the first step to take would be to remove the Blade from the chassis and check the system board LEDs.
True/False: As a rule, power consumption is directly related to resultant heat output.
Which function should be used to view Service Processor configuration and hard disk drive health?
AMM Event Log
PreBoot DSA
AMM Monitor status page
Write down your answers here: 5. 6. 7. 8. 9.
© Copyright IBM Corporation 2009

65. Checkpoint solutions (2 of 2)
Select the correct statement regarding Blade Server status indicators.
Memory and processor LEDs are on the Blade Server front panel
All Blade Server status LEDs are on the Light Path diagnostics panel
Blade Server status and error LEDs are on the Front Panel, Control Panel and adjacent to components on the system board
Light Path status and error indicators require the Blade to be powered on
Answer: c
True/False: The UEFI is a functional replacement for legacy BIOS
Answer: True
True/False: To diagnose a Blade Server hardware problem, the first step to take would be to remove the Blade from the chassis and check the system board LEDs.
Answer: False
True/False: As a rule, power consumption is directly related to resultant heat output.
Which function should be used to view Service Processor configuration and hard disk drive health?
AMM Event Log
PreBoot DSA
AMM Monitor status page
Answer: b
© Copyright IBM Corporation 2009

66. Unit summary Having completed this unit, you should be able to:
Identify the BladeCenter components used to provide PD information
List the planning elements required for the BladeCenter management network
Select the functions available to modify firmware settings
List the blade server indicators and Light Path Components
Select the steps appropriate in diagnosing blade server hardware failures
Identify the utility to use in displaying BladeCenter component health
This unit provided information on planning and problem determination in the BladeCenter environment.
Having completed this unit, you should be able to accomplish the following objectives:
Identify the BladeCenter components used in providing PD information
List the planning elements required for the BladeCenter management network
Select the functions available to modify firmware settings
List the Blade Server indicators and Light Path Components
Select the steps appropriate in diagnosing Blade Server hardware failures
Identify the utility to use in displaying BladeCenter component health
© Copyright IBM Corporation 2009