Brocade SAN Switch Modules for IBM BladeCenter. Firmware Update 5.0.5a 5.0.5a_readme.txt Version 1.00 Sept 15 2006 ________ CONTENTS ________ 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Known Issues 6.0 Unattended Mode 7.0 Web Sites and Support Phone Number 8.0 Trademarks and Notices 9.0 Disclaimer _______________ 1.0 Overview: _______________ This README describes the current firmware version for the Brocade SAN Switch Modules for IBM BladeCenter and procedure for updating firmware on the switch. Products supported Brocade Entry SAN Switch Module for IBM BladeCenter (IBM Option P/N 26K5601) Brocade Enterprise SAN Switch Module for IBM BladeCenter (IBM Option P/N 90P1065) Brocade 4Gb 10 Port SAN Switch Module for IBM BladeCenter (IBM Option P/N 32R1813) Brocade 4Gb 20 Port SAN Switch Module for IBM BladeCenter (IBM Option P/N 32R1812) ____________________ 2.0 Change History ____________________ See change history file _________________________________________ 3.0 Installation and Setup Instructions _________________________________________ 1.) Untar or unzip code package to an FTP Server 2.) Log into the Brocade SAN Switch Module as USERID and PASSW0RD (zero not a O) 3.) Once at a prompt run the command "firmwaredownload" 4.) You will be asked if you want to continue -- press "y" 5.) Enter the IP Address of the FTP Server 6.) Enter the account name for the FTP Server 7.) Enter the path and filename "{PATH}/release.plist" where {PATH} is the path to the top level directory structure for the new firmware. 8.) Enter the password for the FTP Server account 9.) The switch will download and install the code. A reboot will occur automatically when the code is finished installing. Additional detailed instructions for firmware installation of the Brocade Enterprise & Entry SAN Switch Module for IBM eServer BladeCenter can be found in Chapter 4 of the Fabric OS Procedures Guide version 5.0.1 or higher on the BladeCenter Documentation CD provided with each switch module. See section 4.0 Configuration Information for configuring the new Dynamic Port-on-Demand capability for the Brocade 4Gb 10 Port SAN Switch Module for IBM eServer BladeCenter (IBM Option P/N 32R1813) _______________________________ 4.0 Configuration Information _______________________________ Detailed information on configuring the Brocade 4Gb SAN Switch Module for IBM eServer BladeCenter can be found in the Brocade documentations on the BladeCenter Documentation CD provided with each switch module. Additional information is available in the Brocade 5.0.5a Firmware Release Notes. - When using a 4Gb Brocade switch module with a Blade Host in the BladeCenter T Chassis and a Qlogic 4Gb expansion card, the expansion card must be configured to have the Connection Options NVRAM setting set to Point-to-Point. For HS and LS blades, you can use the CTRL-Q option to configure the adapter, and on JS20 blades the SANsurfer Management Application can be used to configure this parameter. - When using a 4Gb Brocade switch module with a Blade Host and a Qlogic 4Gb expansion card in a remote boot environment, the expansion card must be configured to have the Connection Options NVRAM setting set to Point-to-Point. For HS and LS blades, you can use the CTRL-Q option to configure the adapter, and on JS20 blades the SANsurfer Management Application can be used to configure this parameter. - When using a 4Gb expansion card in the HS40 blade, the card must be installed in the slot next to the processors. - Dynamic Ports on Demand (DPOD): The dynamic ports-on-demand (DPOD) feature may be configured on the Brocade 10-port 4Gb SAN switch module (model 32R1813) to “dynamically” select the 10 ports that may be licensed (i.e. which ports to be used). Note that Brocade Web Tools can not enable dynamic POD mode but can be used to release and reserve port licenses. First select the “Admin” button in Web Tools, log into switch and then go to the “Port” tab. - A possible method for implementing DPOD. Please note that enabling DPOD on an existing switch requires a firmware download and then a switch module reboot. The reboot will be disruptive to any IO traffic through the switch module so plan accordingly. Caution: Moving from Static to Dynamic mode requires a reboot of switch module and will clear all port license assignments. This action will result in port license assignments on a first-come-first-server basis which may be different than the static assignments. It is recommended before changing static POD mode to dynamic POD modes do the following: 1) Ensure that only the external devices already attached and logged into to switch module are connected to ports 0, 15, 16. If devices are attached to ports 17, 18, 19 they may acquire port licenses and starve other devices. Before changing POD mode, disconnect any devices connected to ports 17-19. 2) Ensure that server blades with FC daughter cards are installed in slots 1-7. Sever Blades with no FC cards may be installed in slots 8-14. If server blades with FC daughter cards are installed in slots 8-14 then they may acquire a port license and starve other devices 3) Once you have changed to Dynamic method, then you can move POD licenses to unlicensed ports by using Web Tools or the “licensePort –release/reserve” commands. Once the above preliminary steps are followed, perform the following steps to enable dynamic ports-on-demand 1. Install FOS v5.0.5a onto one Brocade 10port 4Gb switch module. 2. Telnet into the switch module. 3. Place switch module in dynamic port licensing mode using the command: a. licensePort –method dynamic 4. Reboot the switch module using the fastboot command or through the BladeCenter Management Module screen. Allow the switch to fully boot. You can verify that server blades and external devices successfully re-connect to the switch module by using the switchShow command. . 5. Issue the licensePort –show command to verify that dynamic mode is enabled and to determine which ports are licensed. 6. To free up (“release”) port licenses from ports that have a license then follow these steps: a. If that port has a device attached and logged into switch then shutdown the device and disable the switch port using portdisable b. licensePort –release 7. To apply (or ‘reserve’) licenses to ports that do not have licenses then use the command: a. licensePort –reserve 8. Issue the licensePort –show command to verify the correct ports are licensed. 9. Once the first SAN Switch module has been configured, then repeat for the 2nd path. _____________________ 5.0 Known Issues _____________________ - When using the command "interopmode 1" ensure that you immediately reboot the switch after changing the interoperability mode. Failure to do so will allow a Domain ID outside of the permitted 97-127 range for interoperability. A domain ID higher then 127 in interoperability mode will prevent the switch from completing POST. If this occurs, use the reset to config defaults option in the BladeCenter Management Module to recover the switch. _____________________ 6.0 Unattended Mode _____________________ 6.1 This update package does not support Unattended Mode ________________________________________ 7.0 WEB Sites and Support Phone Number ________________________________________ 7.1 IBM Support Web Site: http://www.ibm.com/pc/support 7.2 IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity 7.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: 1-800-772-2227 http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. ____________________________ 8.0 Trademarks and Notices ____________________________ 8.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM BladeCenter eServer Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds. Intel trademarks or registered trademarks are trademarks of Intel Corporation. Other company, product, and service names may be trademarks or service marks of others. ________________ 9.0 Disclaimer ________________ 9.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 9.2 Note to Government Users Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. .