xw5033 3.50 part 4 troubleshooting
DESCRIPTION
ibm training troubleshootingTRANSCRIPT
BladeCenter ®Education
BladeCenter Fundamentals
Part 4 – Troubleshooting and Support References
BladeCenter Fundamentals
BladeCenter Fundamentals
BladeCenter Fundamentals
Module 8 – Solving Problems
BladeCenter FundamentalsObjectives
•By the end of this module, you will be able to:-Describe how to troubleshoot the BladeCenter and blade servers
-Identify Troubleshooting Tools-Identify Troubleshooting Procedures
BladeCenter FundamentalsSolving Problems Means Good Information Gathering and Processing
•Gather the facts (two sources if possible)-From the client
•Symptom description, event logs and status lights-From the IBM case history if there is one
•Analyze the facts-Use information resources at your disposal
•ServerProven, HMM, support Web site•Establish the cause
-Apply your knowledge and skill•Fix the problem
-Make the client happy again•If you can’t fix the problem, seek help, don’t guess!
BladeCenter FundamentalsKnow the Product
•Get to know the product you are supporting-Be familiar with:
•The ‘look and feel’ of the system-Physical dimensions of the system-How heavy is it?-How deep is it?-How does it fit into the rack (slider rails or fixed sled rails?)-Power requirements
•Proper installation procedures•Software considerations
-How do I back up my configuration?-Which software version is recommended (SP’s etc)?
•Physical access limitations
BladeCenter FundamentalsIBM BladeCenter – Management Module –The Key to Information Gathering in BladeCenter
•The management module (MM) stores all event and error information for the BladeCenter-The MM is:
•The first ‘door’ for BladeCenter component enablement•The starting point for all configuration steps for non-blade server functions
•The starting point for all problem handling and repair•The repository for the BladeCenter system event log (SEL)
BladeCenter FundamentalsIBM BladeCenter – Six System States
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) Light Path
System event log
3 There is AC and DC power but the system fails to complete post
Checkpoint codesF1 and F2 Beep codesAdapter BIOS messages
PDSGRetain tipsIBM Support Web site
4There is AC and DC power, the system completes POST but the NOS fails to start loading
F2 diagnostics PDSGRetain tips
5There 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
DSANOS event logs DSA
ACAC/DC
POSTNOS
StartComplete
Stop
BladeCenter FundamentalsIBM BladeCenter – 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
BladeCenter FundamentalsIBM BladeCenter – 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
BladeCenter FundamentalsIBM BladeCenter – 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- Not very common- 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
BladeCenter FundamentalsIBM BladeCenter – 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
BladeCenter FundamentalsIBM BladeCenter – 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
BladeCenter FundamentalsIBM BladeCenter – Maintaining Firmware Updates
The following BladeCenter S system components have firmware that can be updated:• Advanced management module • Blade servers • I/O modules, including the SAS connectivity module • Storage module
Blade-serverSAS Connectivity
Module Storage ModuleAdvanced Management
Module
BladeCenter FundamentalsIBM BladeCenter – Firmware Updates –Storage Configuration Manager
BladeCenter FundamentalsIBM BladeCenter – SCM – Device Log
Device Log record events:• Firmware updates• Connectivity status changes• Errors• SAS module power state changes• Port issues.
Error Counters:• View or clear error on a specific device• Indicates failing devices
.
BladeCenter FundamentalsIBM BladeCenter – SCM Collect Support Data
To gather this data:1. Select the correct SAS module from the Current Device pull-down list box 2. Click Collect Support Data. It will take a short time for the data to be gathered.3. After the data has been collected, click the Click here link to save the data to your local computer.4. Click Save if using Internet Explorer and select a location for the data to be saved. Click Save again
to complete the process.
BladeCenter FundamentalsIBM BladeCenter – BC-S Disk Storage Module (DSM) Fault Isolation
• The AMM provides System Status for:
- DSM Fault- Drive Presence- Drive Fault
• Things to look for:- DSM not powering
on automatically - DSM Fault LED on- DSM FW at x.14- DSM FW at 0.40- DSM FW Update Failing
Power-on Policy
•If the BC-S configuration consists of only two power supplies, then only one DSM is allowed in the chassis
•If a second DSM is installed, then it will not power on•Four power supplies are needed for a two DSM configuration
BladeCenter FundamentalsIBM BladeCenter – DSM Not Powering On Automatically
- This can be done through the AMM’s Debugger page:• http://192.168.70.125/private/debug.ssi• Issue “i2c132 1 10 3f 40 f0 01 81” to power on DSM1• Issue “i2c132 1 18 3f 40 f0 01 81” to power on DSM2• The command may need to be issued a couple of times before
“Write Successful” is displayed
BladeCenter FundamentalsIBM BladeCenter – SAS Fault Isolation
• Issues can be caused by any portion of the fabric- Expansion Card- SAS Module- BCS Storage Modules
• Use of the Module’s “sasport status all” command will quickly show all connected ports
- Blades or storage that do not appear in this list can be quickly identified for further review
- It will also show if any port faults have been encountered.• A link reset or re-seating of the SAS cable can be attempted to
eliminate a port fault- SCM can also be used to obtain port status‘
• If connection is present, another tool would be the Expansion Card “Topology” View in CTRL-C, or LSI’s MegaRAID Storage Manager.
- This will give the user a view through the Module, and whether any attached disks can be seen.
SAS Connectivity Module
BladeCenter FundamentalsIBM BladeCenter – 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
http://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-BLADE&brandind=5000008
BladeCenter FundamentalsIBM BladeCenter – Gather Information from the Management Module
• Gather information from the following screens:- Save file as ‘Web archive – single file (*.MHT)’
• System status• Event log• Hardware VPD• Software VPD
BladeCenter FundamentalsIBM BladeCenter – Gather Information from the 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
HS Series Linux Dynamic System Analysis
LS Series Windows Dynamic System Analysis
LS Series Linux Dynamic System Analyses
JS Series Linux SNAP
JS Series AIX SNAP
SNAP is built into AIX and SNAP for Linux on Power can be found at: http://techsupport.services.ibm.com/server/lopdiags.
BladeCenter FundamentalsIBM BladeCenter – Gather Information from the ESM
• Use the Web interface- Logon to the MM and start a management session via the ‘Switch Tasks’ menu
• Save the log to a file
BladeCenter FundamentalsIBM BladeCenter – Gather Information from Other Switches
• Logs from a Brocade, Cisco, Nortel 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
Type of switch: Command:
Brocade showSupport
Cisco show tech-support
Nortel maint/tsdmp
Qlogic support show
BladeCenter FundamentalsIBM BladeCenter – MM - Recovering From a Forgotten TCP/IP address
MM configuration data is stored in the midplane and on the MM itself-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 192.168.70.125/255.255.255.0-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
BladeCenter FundamentalsIBM BladeCenter – Know your Support Resources – 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, etc.) and initial
customer setup
BladeCenter FundamentalsIBM BladeCenter – Know Your Support Resources – Blade Server References
• IBM BladeCenter Products and Technologyhttp://www.redbooks.ibm.com/redpapers/pdfs/redp4264.pdf
• IBM ServerProven – Compatibility for BladeCenter Products
- http://www-03.ibm.com/servers/eserver/serverproven/compat/us/
• System x Reference (xREF)- http://www.redbooks.ibm.com/xref/usxref.pdf
• Intel Products - http://www.intel.com/products/server/processors/index.htm
• AMD Products- http://www.amd.com/us-
en/Processors/ProductInformation/0,,30_118_8825,00.html
BladeCenter FundamentalsIBM BladeCenter – Know Your Support Resources – Cisco Links
• Cisco Systems Intelligent Gigabit Ethernet Switch Module for theIBM eServer BladeCenter - http://www.redbooks.ibm.com/abstracts/redp3869.html
• Troubleshooting Cisco Systems IGESM issues - http://www-
304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-59637&brandind=5000008
• Link to VLAN best practices- http://www.cisco.com/en/US/products/hw/switches/ps708/products_white_pap
er09186a008013159f.shtml• IBM Serial Over LAN Guide
- http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-54666
BladeCenter FundamentalsIBM BladeCenter – MM - 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 192.168.70.125/255.255.255.0-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 BEFORE REPLACING THE MM
BladeCenter FundamentalsIBM BladeCenter – AMM - Recovering From a Forgotten TCP/IP address or Forgotten Password
AMM configuration data is stored on the MM itself-To reset a TCP/IP address only:
•Remove the cable from the MM ethernet port•Press and hold the IP reset button for +5 seconds
-TCP/IP address will reset to 192.168.70.125 255.255.255.0-AMM configuration will be lost
-Ensure that the AMM configuration has been stored to either external media or midplane•User invention requires AMM configuration to be stored to eithermidplane or external media
-PERFORM RESET STEPS BEFORE REPLACING THE AMM
BladeCenter FundamentalsIBM BladeCenter – Accessing the Management Module
•Default values are known quantities•External TCP/IP address is: 192.168.70.125•Default user ID is: USERID•Default password is: PASSW0RD
192.168.70.125
USERID
BladeCenter FundamentalsIBM BladeCenter – Web Interface to the Management Module
NB: Use IE 4.0 (SP1) or Netscape 4.72 (not 6) and above + Java + JavaScript 1.2
BladeCenter FundamentalsIBM BladeCenter – System Status Screen
•A successful logon will show this screen:
Main information window
Navigation menu
BladeCenter FundamentalsIBM BladeCenter – System Event Log (SEL) Screen
•This screen shows event history of the BladeCenter
BladeCenter FundamentalsIBM BladeCenter – Hardware Vital Product Data (VPD)
•This screen shows information relating to the hardware in the BladeCenter
BladeCenter FundamentalsIBM BladeCenter – Firmware Vital Product Data (VPD)
•This screen shows information relating to the firmware levels of the devices in the BladeCenter
BladeCenter FundamentalsIBM BladeCenter – System Status Menu –Close Up
Tasks
Monitored Components
BladeCenter FundamentalsIBM BladeCenter – Blade Tasks – Close Up
BladeCenter FundamentalsIBM BladeCenter – Management Module Tasks – Close Up
BladeCenter FundamentalsIBM BladeCenter – Management Module Tasks – Configuration Management
BladeCenter FundamentalsIBM BladeCenter – Rules for I/O Module Management
•In-band management-Use the MM 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, MM path to I/O module is unavailable
BladeCenter FundamentalsIBM BladeCenter – I/O Module Tasks –Close Up
BladeCenter FundamentalsIBM BladeCenter – I/O Module Tasks –Advanced Switch Management
BladeCenter FundamentalsIBM BladeCenter – ESM Web Interface
1
2
BladeCenter FundamentalsIBM BladeCenter – CIGESM Web Interface
BladeCenter FundamentalsIBM BladeCenter – Nortel ESM Web Interface
BladeCenter FundamentalsIBM BladeCenter – Fibre Channel Switch Module Web Interface
•SAN Utility (QLogic)- Full Function GUI
•SAN Browser (Qlogic)- Limited functionality
•Switch Explorer (Brocade)- Limited functionality
BladeCenter FundamentalsIBM BladeCenter – UpdateXpress CD-ROM Package
•UpdateXpress CD #1-Bootable CD-ROM (requires local blade server access)
-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
•UpdateXpress CD #2-Bootable CD-ROM for JS20 blade server (requires local blade server to have access to the CD-ROM AND SoL for console view)
-Updates firmware on JS20 blade server-For more information, see http://www-307.ibm.com/pc/support/site.wss/MIGR-53046.html
BladeCenter FundamentalsIBM BladeCenter – 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 http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57201
BladeCenter FundamentalsIBM BladeCenter – 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 http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55021
BladeCenter FundamentalsIBM BladeCenter – 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, seehttps://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-BLADE&brandind=5000020
•For general BladeCenter questions and answers refer to the BladeCenter forum at:
http://www-128.ibm.com/developerworks/forums/forum.jspa?forumID=819
BladeCenter FundamentalsIBM BladeCenter – Gathering Information from the Management Module
•Gather information from the following screens:-Save file as ‘Web archive – single file (*.MHT)’
•System status•Event log•Hardware VPD•Software VPD
BladeCenter FundamentalsIBM BladeCenter – Gathering Information from the Advanced Management Module
•Use the “Service Tools”, “Service Data” to capture from the advanced management module
BladeCenter FundamentalsIBM BladeCenter – 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
HS Series Linux Dynamic System Analysis
LS Series Windows Dynamic System Analysis
LS Series Linux Dynamic System Analyses
JS Series Linux SNAPJS Series AIX SNAP
SNAP is built into AIX and SNAP for Linux on Power can be found at: http://techsupport.services.ibm.com/server/lopdiags.
BladeCenter FundamentalsIBM BladeCenter – Gathering Information from the ESM
•Use the Web interface-Logon to the MM and start a management session via the ‘Switch Tasks’ menu•Save the log to a file
BladeCenter FundamentalsIBM BladeCenter – Gathering Information from Other Switches
•Logs from a Brocade, Cisco, Nortel 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-For more information, seehttp://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=SERV-BLADE
Type of switch: Command:Brocade showSupportCisco show tech-supportNortel maint/tsdmpQlogic support show
BladeCenter FundamentalsIBM BladeCenter – MM Debug Screen
•Useful when debugging MM•http://ip-address/private/debug.ssi
BladeCenter FundamentalsIBM BladeCenter – Serial Over LAN Firmware Debug Tips
•Verify that minimum firmware requirements are met for SoL to function-Components to verify include
•Firmware for MM and ESM, ethernet and SP firmware and drivers onthe blade server
-See the compatibility pages for supported combinations for SoL
BladeCenter FundamentalsIBM BladeCenter – SoL Function Debug Tips
•Ensure SoL is enabled-Ensure that SoL has been enabled for the MM AND the blade server itself•After making changes, save and restart the MM
•Ensure Telnet to MM is functional-If Telnet fails, logon to the MM Web interface and reapply SoL settings (and reboot the MM)
•Start a SoL session to an enabled blade server-If SoL works to one blade server and not another, the SoL function is correctly configured for the BladeCenter•Check the local settings for the malfunctioning blade server
BladeCenter FundamentalsIBM BladeCenter – SoL Debug Tips for JS20 Blade Servers
•If SOL will not come Ready-Restart the MM after making SOL changes-Ensure that the ESM sees ports to JS20 as connected
•On CIGESM, run the command <show int status>•Older AIX drivers will fail to bring up links after a switch restart-The new version of AIX driver resolves this issue
•If SOL intermittently toggles between “Ready” and “Not Ready”-Check the JS20 Broadcom firmware (2.30 or higher)-Verify the firmware in AIX: <lscfg –vpl ent0>
•ROM Level should be no lower than 03210230
BladeCenter FundamentalsIBM BladeCenter – SoL Debug Tips for HSxx Blade Servers
•If SOL will not come Ready-Verify that the MM VLAN is set and that blade servers are enabled for SoL
-Restart the MM after SoL configuration changes-Ensure the ESM sees ports to blade servers as connected
•If ports to blade servers show not connected, reboot blade servers that are showing not connected
-Verify switch configuration•Is SoL VLAN created and matches the VLAN set on MM?
-<show vlan> (e.g. using Cisco Telnet interface)•Is SoL VLAN being carried on blade server ports?
-<show run int g0/X> (X = 1 through 14, slot to be checked)•Is SoL VLAN being carried on port to MM?
-<show run int g0/15>
BladeCenter FundamentalsIBM BladeCenter – ESM Debug Tips
•Through the MM, verify the following:-Switch TCP/IP address-External ports are enabled-Management over external ports is enabled (if direct connect management is to be deployed
BladeCenter FundamentalsIBM BladeCenter – FC HBA Debug Tips for HSxx Blade Servers
•Access Fast!UTIL using Ctrl+Q at boot-Scan Fibre Devices
•Verifies controllers can be seen by showing loop IDs•Verify BIOS and WWN
BladeCenter Fundamentals
Module 9 – Support References
BladeCenter FundamentalsObjectives
•By the end of this module, you will be able to:-Identify documentation resources available to support the servers discussed in this class
-Identify the support web sites for the units and what they offer
BladeCenter FundamentalsIBM Support Web Site
• New central Web site for all server products:- http://www-304.ibm.com/systems/support/
BladeCenter FundamentalsServerProven Web Site
•Navigate to:-http://www-03.ibm.com/servers/eserver/serverproven/compat/us/
BladeCenter FundamentalsBladeCenter Documentation
• Hardware Maintenance Manual- Available electronically (Adobe Acrobat .PDF format) from the
IBM support Web site or on the service update CD-ROM- Primary support document for diagnostics and troubleshooting
• BladeCenter data collection guide:- http://www-
307.ibm.com/pc/support/site.wss/document.do?lndocid=SERV-BLADE
• System documentation (User’s Guide, Installation Guide, etc.)- Useful for confirming shipping group contents (missing parts, etc.)
and initial customer setup
BladeCenter FundamentalsCISCO Links
•Useful Cisco information•IBM/Cisco Design Guide for the CIGESM
-http://www-1.ibm.com/services/alliances/cisco/files/cisco-igesm-design-guide.pdf
•IBM CIGESM Deployment Redpaper-http://www.redbooks.ibm.com/abstracts/redp3869.html
•IBM Serial Over LAN Guide-http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-54666
•CIGESM Software Configuration Guide-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55261
•Link to VLAN best practices-http://www.cisco.com/en/US/products/hw/switches/ps708/products_white_paper09186a008013159f.shtml
BladeCenter FundamentalsCisco File Downloads
•Useful Cisco download locations•CIGESM IOS Code Download (AY4)
-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58132
-MIBS can also be found at the link for AY4 code•CiscoView Package Download
-Support provided at FCS-http://www.cisco.com/cgi-bin/tablebuild.pl/cview50-Download cv50.v1-0.readme and cigesm.cv50.v1-0.zip
•CiscoWorks IDU's to support the CIGESM -Version 10 and above IDU’s support CIGESM-Minimum code on CIGESM to support CiscoWorks is 12.1(14)AY1-http://www.cisco.com/kobayashi/sw-center/cw2000/lan-planner.shtml-Under "Application-Level Updates" for each module
BladeCenter FundamentalsNortel – ‘Must Have’ Documents
•Useful Nortel switch information•GbESM Application Guide
- Overview and detailed step by step guide to configuration•GbESM Command Reference
- Detailed description of every command and it’s parameters•Alteon OS xx Release Notes
- Newest features, upgrade instructions and known issues as of the release date
•Browser Based Interface Quick Guide- Explains how to use the browser based interface to configure the switch
•GbESM Switch Module Installation Guide- Supported networking standards, install instructions for the switch, initial configuration of the switch, software update instructions, LED and POS error descriptions
BladeCenter FundamentalsNortel – ‘Must Have’ Documents (Continued)
•More useful Nortel switch information •GbESM Pre-Sales Guide -
-A primer on the capabilities of the GbESM switch. Gives a comprehensive overview of the GbESM switch and its features and real world deployment scenarios
•IBM Red Book BladeCenter Layer 2-7 Network Switching –-A step by step deployment guide in multi-vendor environments. Most commonly used upstream devices and different connectivity scenarios are covered in a comprehensive manner, that includes illustrations and CLI commands for most common Cisco and Nortel devices
•Refer to the following URL for documentation•http://www.pc.ibm.com/us/eserver/bladecenter/literature.html
BladeCenter FundamentalsBC Fibre - Reference Materials
•Useful FC links and documents•IBM BladeCenter SAN Interoperabilty Guide
-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46241•IBM BladeCenter SAN Solutions Guide
-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-54854•IBM BladeCenter Remote Boot Document (HS20/HS40)
-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57563•IBM BladeCenter Remote Boot Document (JS20)
-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57235•Brocade SAN Switch Modules for IBM BladeCenter Solution Brief
-ftp://ftp.software.ibm.com/common/ssi/rep_sp/n/XSD00107USEN/XSD00107USEN.PDF
•Brocade Design Deployment and Management Guide (DDM)-http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55327