Академический Документы
Профессиональный Документы
Культура Документы
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 1 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Table of Contents
Introduction........................................................................................................................................ 5 1.1 Overview ................................................................................................................................... 5 1.2 BladeCenter Subsystems.......................................................................................................... 6 1.3 Notes ......................................................................................................................................... 6 1.3.1 Contributors....................................................................................................................... 6 Installation and Configuration ....................................................................................................................... 7 2 Preparatory Steps ............................................................................................................................. 7 2.1 Initial Configuration ................................................................................................................... 7 2.2 Network Configuration............................................................................................................... 7 2.3 BladeCenter Management Module ........................................................................................... 8 2.4 User Configuration .................................................................................................................... 8 2.5 BladeCenter Firmware .............................................................................................................. 9 Switch Configuration ................................................................................................................................... 11 3 Embedded Ethernet switches ......................................................................................................... 11 3.1 Configuring the Ethernet switch .............................................................................................. 11 3.1.1 Changing the IP addresses............................................................................................. 11 3.1.2 Enabling the external ports ............................................................................................. 11 3.2 Access and log on to the management module...................................................................... 11 3.2.1 Externally managing the Nortel GbE switch module....................................................... 11 3.2.2 Externally Managing Cisco CIGESM .............................................................................. 12 3.2.3 Testing Procedures Ethernet Connectivity................................................................... 12 3.2.4 Problem Documentation Requirements .......................................................................... 12 3.3 Updating the Firmware on the Nortel GbESM ........................................................................ 13 3.4 Ethernet Port Numbering ........................................................................................................ 15 4 Embedded Fibre Channel Switches................................................................................................ 16 4.1 SAN Configuration .................................................................................................................. 16 4.2 Disabling ports on the QLogic switch ...................................................................................... 16 4.2.1 Using Telnet .................................................................................................................... 16 4.2.2 Using SANSurfer GUI ..................................................................................................... 17 4.3 Updating the Firmware on the QLogic Switch......................................................................... 18 4.3.1 Updating via SANSurfer GUI........................................................................................... 18 4.3.2 Updating via Telnet ......................................................................................................... 19 5 SAN Configuration .......................................................................................................................... 21 5.1 Description .............................................................................................................................. 21 5.2 Firmware Revision Levels ....................................................................................................... 21 5.3 Fabric Domain IDs .................................................................................................................. 21 5.3.1 Determining the Domain ID for McData .......................................................................... 21 5.3.2 Determining the Domain ID for Qlogic ............................................................................ 22 5.4 Principle Switch ....................................................................................................................... 23 1
Appendix A.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 3 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Table of Tables
Table 1 Recommended settings for the QLogic QLA23xx adapter card for Windows 2000 or 2003 ......... 20 Table 2 Management Module BIOS Information......................................................................................... 26 Table 3 Nortel Networks Layer 2/3 GbE Switch Module............................................................................. 26 Table 4 Nortel Switch Firmware Information............................................................................................... 26 Table 5 Cisco GbESM Firmware Information ............................................................................................. 26 Table 6 QLogic 2pt Fibre Channel Switch BIOS Information...................................................................... 27 Table 7 QLogic 6pt Fibre Channel Switch BIOS Information...................................................................... 27 Table 8 Brocade SAN Switch Module Firmware Information...................................................................... 27 Table 9 QLogic Firmware Information......................................................................................................... 27
Table of Figures
Figure 1 BladeCenter Chassis Rear View ................................................................................................. 6 Figure 2 BladeCenter internal network ......................................................................................................... 8 Figure 3 Firmware Levels from Management Module ................................................................................ 10 Figure 4 Updating the firmware on the Nortel switch.................................................................................. 14 Figure 5 Storage Connection Diagram ....................................................................................................... 16 Figure 6 Port Status Online......................................................................................................................... 17 Figure 7 Port Status Offline......................................................................................................................... 17 Figure 8 SANSurfer Switch Faceplate ........................................................................................................ 18 Figure 9 Port Properties .............................................................................................................................. 18 Figure 10 Firmware Update via Telnet........................................................................................................ 20 Figure 11 Switch Parameters (McData)...................................................................................................... 22 Figure 12 Change domain ID (McData) ...................................................................................................... 22 Figure 13 Launch SANbox Manager........................................................................................................... 23 Figure 14 Determine Qlogic domain ID....................................................................................................... 23 Figure 15 Setting Switch Priority................................................................................................................. 24 Figure 16 Setting Switch to Principle .......................................................................................................... 24
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Cisco Systems Intelligent Gigabit Ethernet Switch Module for IBM BladeCenter. This Redpaper helps plan for, install, and configure the Cisco CIGESM in several network topologies. The topology examples are provided in this Redpaper for the purpose of demonstrating a number of ways to perform the integration of the switch module into different networks. (REDP3869)
1.3 Notes
This is currently a living document and will continue to grow as we have more experience with IBM Blades in the boot-to-SAN environment. This document is intended as a personal productivity tool. It is not intended to be comprehensive, and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
1.3.1 Contributors
We would like to acknowledge the contributions of the following people: 1. Richard Gebhardt, IBM Lab Services Appendix E Error! Reference source not found., portions of Section Error! Reference source not found. Error! Reference source not found.. 2. Fred Rabert, Nortel Networks Assistance with Section 3 Embedded Ethernet switches plus BroadCom Driver installation instructions.
6 2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 7 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Figure 2 BladeCenter internal network Note: For switch communication through the management module external Ethernet port, the switch module internal network interface and the management module internal and external interfaces must be on the same subnet.
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Custom: User may or may not have any restrictions, depending on which custom authority level is assigned to the user.
If you select the Custom option, you must select one or more of the following custom authority levels: Chassis Operator User may browse status and properties of chassis components (MM, blowers, midplane, power modules, media tray). Ability to backup MM configuration. Chassis User Account Management User may add, modify, and delete MM login profiles. Chassis Log Administration User may clear the MM event log and change log policy settings. Chassis Configuration User may modify and save any chassis configuration parameter (except user profiles and event log settings). For example, general MM settings, MM port assignments, MM network interfaces, MM network protocols, MM security. Ability to restore MM configuration. Ability to restore MM factory defaults if the user also has Chassis Administration permissions. Chassis Administration User may do MM firmware updates, restore MM factory defaults if the user also has Chassis Configuration permissions, or restart the MM. Blade Operator User may browse status and properties of blades. Blade Remote Presence User may access the Remote Control web panel and the functions provides on the panel: remote console (KVM) and remote disk. The CLI "console" command to start an SOL session to a blade will also require this authority. Blade Configuration User may modify and save and blade configuration parameters. For example, parameters in the Blade Configuration web panel, and blade SOL parameters on the Serial Over LAN web panel. Blade Administration User may power on/off and restart blades, activate standby blade servers, do firmware updates. Switch Operator User may browse status and properties of I/O modules, and may ping the I/O modules. Switch Configuration User may modify the switch module IP address, configure switch Advanced Management parameters, and restore factory defaults. Switch Administration User may power on/off and restart switch modules, update switch module firmware, and enable/disable the Fast POST and External Ports of a switch. Note: in order to be able to launch the switch module telnet or web UI, supervisor access is required for that switch module. This means that both Switch Configuration and Administration roles must be assigned. Note: In order to prevent a situation where none of the users have read/write access, login profile #1 must be set with at least the ability to modify the login profiles. This means that this user must be given either Supervisor access, or User Account Management access. This guarantees that at least one user can perform actions or make configuration changes, or at the very least, add users to the login profiles who can.
There is also a URL for registering for proactive emails regarding firmware updates.
https://www-1.ibm.com/support/mysupport/us/en/
If first time select register. After you have logged into the site, select edit profile and add the servers that you would like receive notification on. The tables in that appendix will also help translate between build ids and release versions. You can see the current firmware levels from the management module, shown in Figure 3 Firmware Levels from Management Module.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 9 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
10
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Switch Configuration
3 Embedded Ethernet switches 3.1 Configuring the Ethernet switch
3.1.1 Changing the IP addresses
Establish a TCP/IP session for the GbE switch through the management module by completing the following steps: 1. Access and log on to the management module. For more information, see Section 2.1 2. Select Management on the I/O Module Tasks menu on the left side of the BladeCenter Management Module window. 3. From the I/O Module Management portion of the window, click the bay number that corresponds to the location of the GbE switch module that you installed. The applicable bay number (Note: Bay 1 is the designated primary Ethernet switch, Bay 2 is designated as the standby Ethernet) appears in the bottom portion of the window, followed by other related switch-module information, including the IP address. The switch-module information is divided under two headings: Current IP Configuration and New Static IP Configuration. 4. To change the IP address of the GbE switch module, use the Tab key to reach the IP address data field under the New Static IP Configuration heading; then, type the new IP address and click Save. Click Advanced Management under the applicable bay information (in this example, bay 1) in the Management Module window. You can now start a browser-based interface session, a Telnet session, or a Secure Shell (SSH) session.
Start a Telnet session with the GbE switch module from your laptop connected directly to any of the IBM Nortel switch external ports. USERID: admin Passwd: admin The following example shows how to create this configuration using the CLI: /cfg/13/if 1/mask 255.255.255.0 /cfg/13/if 1/addr 10.10.1.1 /cfg/13/if 1/vlan 1 /cfg/13/if 1/ena ena apply save yes Critical Note: Please remember the following acronym: (EASY) E= Enable A= Apply S= Save Y= Yes after making your CLI changes to avoid losing your changes.
12
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
e-Gatherer The process to gather the server's information begins by downloading a copy of e-gatherer. 1. Download a copy of e-Gatherer from the following link for Windows or Linux and then follow the instructions below. http://www-1.ibm.com/support/docview.wss?rs=113&context=HW180&q1=egatherer&uid=psg1MIGR-4R5VKC&loc=en_US&cs=utf-8&lang=en 2. Double-click on the file to run the e-Gatherer program. At the DOS window type Y to accept the terms and conditions of the disclaimer. 3. When the progress bar indicates that the e-Gatherer program has completed its information gathering operation, close the DOS window. For Linux, use the following commands: 1. Log in as root 2. Download or copy egather2-2.09.linux to a directory of your choice, for example /tmp 3. Enter the command: chmod u+x egatherer2-2.09.linux 4. Enter the command: ./egatherer2-2.09.linux to run eGatherer. When e-Gatherer has successfully executed, an output file is generated. This file resides in the same directory as your e-Gatherer program file. The name of this output file takes has the format IBM-xxxxxxxABCDEFG.eg2 where: "xxxxxxx" denotes a seven digit machine type number and "ABCDEFG" denotes the serial number of your system. This output file contains all of your system's configuration information. Attach this output file (IBMxxxxxxx-ABCDEFG.eg2) to an e-mail and send this e-mail back to IBM's support center.
6.
7. 8.
b. Type /boot/gtimg imageX TFTPAddr GbESM-AOS-<ver>-os.img at the telnet prompt and press enter where imageX is the name of the OS image (image1 or image2) that was determined in previous step. TFTPAddr is the IP address of the TFTP server on your production network where the image files reside. See Figure 4 for an example. The image file name must match file downloaded in Steps 1 through 3 above. c. Type y and press enter when prompted to Confirm download operation d. Wait for the flashing operation to complete. Note: Type y and press enter to boot from the new image if you were forced to update image2 because it was previously empty. e. Type exit and press enter to terminate the telnet interface. f. Close the window in which the telnet session was running. Restart the Nortel GbESM a. From the Management Module Web Interface, click on the Power/Restart link under the I/O Module Tasks section. b. Check the box next to the Nortel GbESM and click on the Power Off Module(s) link. c. Click the OK button on the confirmation screen. d. Check the box next to the Nortel GbESM and click on the Power On Module(s) link e. Click the OK button on the confirmation screen. You must wait approximately 60 seconds for the swtitch to fully restart before continuing. Reconnect to the Nortel GbESM telnet interface by repeating Step 4. Update the Nortel GbESM boot image Type /boot/gtimg boot TFTPAddr GbESM-AOS-<ver>-boot.img at the telnet prompt and press enter where TFTPAddr is the IP address of the TFTP server on your production network where the image files reside. The image file name must match file downloaded in Steps 1 through 3 above. Type y and press enter when prompted to Confirm download operation Wait for the flashing operation to complete. Type exit and press enter to close the telnet interface, close the window in which the telnet session was running. Restart the Nortel GbESM by repeating Step 6 above.
Browse MAC Address Table Top Switch VID MAC Address 9 00-11-25-4a-00-4c
eth1
Port Bay 13
Learned Dynamic
Link encap:Ethernet HWaddr 00:11:25:4A:00:4D inet addr:10.0.200.32 Bcast:10.0.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
Browse MAC Address Table Bottom Switch VID MAC Address 100 00-11-25-4a-00-4d
Port Bay 13
Learned Dynamic
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 15 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
4.2
Here are the steps necessary to disable ports on the QLogic switch. This can be done either via a telnet session or a browser session.
16
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Operational State ----------Online Offline Online Offline Offline Online Offline Offline Offline Offline Offline Offline Offline Offline Offline Offline
Config Running Type GL Type F Unknown F Unknown Unknown F Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown ------ -------
Ext2:15 Online Bay1 Bay2 Bay3 Bay4 Bay5 Bay6 Bay7 Bay8 Bay9 Bay10 Bay11 Bay12 Bay13 Bay14 Online Online Online Online Online Online Online Online Online Online Online Online Online Online
NotLoggedIn GL LoggedIn F
NotLoggedIn F NotLoggedIn F LoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F NotLoggedIn F
Inactive 2Gb/s Inactive 2Gb/s Active 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s
Figure 6 Port Status Online 3. Enter admin mode by entering admin start 4. Disable the target port by entering the command set port x state offline where x is the number of the port. For this example, we used 4 5. Confirm the status by entering show portagain.
QLogic: USERID> admin start QLogic (admin): USERID> set port 4 state offline QLogic (admin): USERID> show port Admin Port ---Ext1:0 State ----Online Operational State ----------Online Offline Online Offline Offline Offline Offline Offline Login Status -----LoggedIn Config Running Type GL Type F Unknown F Unknown Unknown Unknown Unknown Unknown ------ ------Link State ----Active Link Speed ----1Gb/s
Ext2:15 Online Bay1 Bay2 Bay3 Bay4 Bay5 Bay6 Online Online Online Offline Online Online
NotLoggedIn GL LoggedIn F
Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s Inactive 2Gb/s
Figure 8 SANSurfer Switch Faceplate 3. Right click on the desired port and choose "port properties" from the menu. 4. At the top of port properties put a bullet next to "offline" or "down". 5. Repeat steps 1-4 and reverse step 5 to online the port.
4.3
1. In the faceplate display, open the Switch menu and select Load Firmware. 2. In the Firmware Upload dialog, click the Select button to browse and select the firmware file to be uploaded. 3. Click the Start button to begin the firmware load process. 4. The application prompts you to activate the new firmware, non-disruptively, if possible. Click the OK button to reset the switch and activate the new firmware. Note: For firmware versions that follow the initial release of version 2.0, you have the ability to install and activate new firmware without resetting the switch, and therefore, without disrupting traffic. The application will attempt a nondisruptive firmware installation and activation whenever possible. Important: During a hotreset operation, fabric services will be unavailable for a short period (30-75 seconds depending on switch model). To ensure that a Non-Disruptive Code Load and Activation (NDCLA) operation is successful, verify that all administrative changes to the fabric (if any) are complete. Changes to the fabric may disrupt the NDCLA process. Common administrative operations that change the fabric include: 1. Zoning modifications 2. Adding, moving or removing devices attached to the switch fabric. This includes powering up or powering down attached devices. 3. Adding, moving or removing ISLs or other connections. After an NDCLA operation is complete, management connections must be re-initiated. Sessions will reconnect automatically Telnet sessions must be restarted manually. Applicable Code Versions NDCLA capability is available starting with version 2.0 of the switch code. (N/A for 20-Port 10-Gbps switches) Upgrading to version 2.0 from previous releases will be disruptive. (N/A for 20-Port 10-Gbps switches) An NDCLA operation to previous switch code release is not supported.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 19 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
QLogic (admin): USERID> image unpack firmware_2.0.0.22 Processing the command ... A notification with the command result will appear on the screen when the command has completed. QLogic (admin): USERID> image unpack command result: Passed. The firmware will become active and the SWImageVersion information will be updated after the next switch reset. QLogic (admin): USERID> hotreset
Figure 10 Firmware Update via Telnet http://knowledge.storage.ibm.com/servers/storage/support/hbasearch/interop/hbaSearch.do Parameters BIOS Frame size Loop reset delay Adapter hard loop ID Hard loop ID Execution throttle Fast command posting >4 GB addressing LUNs per target Enable LIP reset Enable LIP full login Enable target reset Recommended settings Disabled 2048 5 (minimum) Disabled 0 100 Enabled Disabled (for 32-bit systems) 0 No Yes Yes Note: Enable LIP reset, Enable LIP full login, and Enable target reset parameters control the behavior of the adapter when Windows tries to do a SCSI bus reset. You must perform a target reset to make cluster failovers work. Use the SCSI bus device reset option to clear SCSI reservations. 20 (minimum) 20 (minimum) Enabled No No 256 Disabled
Login retry count Port down retry count Driver load RISC code Enable database updates Disable database load IOCB allocation Extended error logging
Table 1 Recommended settings for the QLogic QLA23xx adapter card for Windows 2000 or 2003
20
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
To merge the QLogic and McData switches. The McData switch will handle the zoning, while the QLogic switch will operate in a passive mode. Since there are two separate fabrics, the following rules apply to each fabric: Firmware Revision Levels Verify the correct version of firmware is installed on the McData and Qlogic products and also the correct versions of SANavigator, EFCM, and SANbox Manager are installed. Fabric Domain IDs Ensure there are no duplicate domain IDs in each fabric. Principle Switch Select a McData Director as the Principle Switch. Zone Names Ensure there are no duplicate zone/zone set names. Soft Zoning Ensure the McData switch has fabric zoning configured with WWN. Zone Naming Conventions Ensure McData and QLogic switches comply with proper zone naming. Operating Mode Ensure the fabrics are in the proper operating mode. Rerouting Delay Ensure rerouting delay is disabled on McData. Auto Save Ensure the QLogic Auto Save is disabled. Qlogic Zoning Ensure default zoning is disabled on QLogic. Merge Fabrics Add the switches to the fabric one at a time. Complete Zoning Use SANavigator for Zoning Activities. Save Zone Set After fabrics are merged, save your current active zone set.
5.2
The correct versions of firmware and the correct versions of SANavigator, EFCM, and SANbox Manager must be installed before attempting to merge the fabrics. Since updates are frequent, contact your local McDATA or QLogic customer service representative to determine what versions are needed and if necessary, obtain the latest versions of applications and firmware.
5.3
Each switch in a fabric has a domain ID. These domain IDs are assignable and must be unique to each switch. QLogic offsets domain IDs by a factor of 96; in other words a domain ID of 1 on a McData switch will be the same as domain ID 97 on a QLogic switch. Before attempting to merge the fabrics, domain IDs must be changed to ensure unique addresses.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 21 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Figure 11 Switch Parameters (McData) 3. From the Configure Switch Parameters dialog box, change the number in Domain ID Preferred box to the appropriate domain ID.
22
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Figure 13 Launch SANbox Manager 2. Once SANbox Manager is launched, you can change the domain number in the Domain ID box from the Switch Properties SANbox Manager dialog.
5.4
Principle Switch
Setting McData as the principle switch
To select McData as the Principle Switch, perform these steps,
Since the Qlogic switches are in passive mode, the McData switches are used as the principle switch. This reduces build fabric traffic and hops, and ensures that Fabric Address Zoning is not used.
Note: This is an offline operation, which requires a switch outage. Traffic may be moved to the alternate SAN if available. Please plan accordingly.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 23 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
1. Use SANavigator to launch EFCM. Select Configure Operating Parameters, Fabric Parameters.
Figure 15 Setting Switch Priority 2. On the Configure Fabric Parameters dialog box, change Switch Priority to Principal.
AdminState (1=Online, 2=Offline, 3=Diagnostics) [Online] BroadcastEnabled (True / False) [True] InbandEnabled (True / False) [True] DefaultDomainID (decimal value, 1-239) [111] DomainIDLock (True / False) [True] SymbolicName (string, max=32 chars) [Switch-2] R_T_TOV (decimal value, 1-1000 msec) [100] R_A_TOV (decimal value, 100-100000 msec) [10000] E_D_TOV (decimal value, 10-20000 msec) [2000] FS_TOV (decimal value, 100-100000 msec) [5000] DS_TOV (decimal value, 100-100000 msec) [5000] PrincipalPriority (decimal value, 1-255) [254] 253 ConfigDescription (string, max=64 chars) [QLogic SANbox2 FC Switch] Finished configuring attributes. This configuration must be saved with the config save command and activated with the config activate command before the configuration can take effect. To discard this configuration use the config cancel command. Switch-2 (admin-config) #> config save Switch-2 (admin) #> config act The configuration will be activated. Please confirm (y/n): [n] y
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 25 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Table 2 Management Module BIOS Information A minimum of BRET82A is highly recommended since it contains several important fixes: 1) Repeating keystrokes fix 2) Gratuitous arp fix 3) Improved failover and firmware transfer handling Ethernet switches Nortel Networks Layer 2/3 GbE Switch Module
Minimum Req Version Release Date Build Id 1.1.1.1 2005/10/12 1.1.1.1 Most Current 1.1.1.1 2005/10/12 1.1.1.1
Table 3 Nortel Networks Layer 2/3 GbE Switch Module Nortel Networks Layer 2-7 GbE Switch Module (GbESM) Firmware
Minimum Req Version Release Date Build Id Build Date Revision 20.1.2.2 2004/07/23 WM01000 2004/03/09 2001 Most Current 20.2.2.7 2005/11/05 WM01001 10/15/2004 2002
Table 4 Nortel Switch Firmware Information Cisco Systems Intelligent Gigabit Ethernet Switch Module firmware
Minimum Req Version Release Date Build Id Build Date Revision 12.1(22)AY1 2005/03/25 BRCSMI12.1 tbd 22AY Most Current 12.1(22)EA6a 2005/01/03 BRCSMI12.1 TBD EA6
26
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Table 6 QLogic 2pt Fibre Channel Switch BIOS Information QLogic 6pt Fibre Channel Switch Module Firmware
Minimum Req Version Release Date Build Id Revision 4.1.0.22 2004/08/06 4122 tbd Most Current 5.2.0.26 2005/08/03 5226 tbd
Table 7 QLogic 6pt Fibre Channel Switch BIOS Information Notes regarding the QLogic 2pt and 6pt switches 1. Obtain this firmware from the QLogic website: http://www.qlogic.com/support/oem_detail_all.asp?oemid=324 2. Firmware versions that follow the initial release of version 2.0 support the ability to install and activate new firmware without resetting the switch, and therefore, without disrupting traffic. The application will attempt a non-disruptive firmware installation and activation whenever possible. Important: During a hotreset operation, fabric services will be unavailable for a short period. To ensure that a Non-Disruptive Code Load and Activation (NDCLA) operation is successful, verify that all administrative changes to the fabric (if any) are complete. Changes to the fabric may disrupt the NDCLA process. See 4.3 for more information on this process. Brocade Entry/Enterprise SAN Switch Module Firmware
Minimum Req Version Release Date Build Id Revision 4.2.1 2004/04/08 BREFSM 421 Most Current 4.4.1a 2005/02/15 BREFSM 441a
Table 8 Brocade SAN Switch Module Firmware Information QLogic HBA Firmware
Minimum Req Version Most Current
1.43
Note: we are now recommending v1.43 for the QLogic BIOS. Old minimum was v1.38.
Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 27 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
Index
Brocade SAN Switch Firmware level ..............................................27 Cisco Ethernet Switch Module Firmware Levels...........................................26 Management ................................................12 Firmware Levels Brocade SAN Switch Module .......................27 Cisco Ethernet Switch Module .....................26 Download page ..............................................9 Management Module ...................................26 Nortel Networks Switches Layer 2/3 GbE Switch Module..................26 Layer 2-7 GbE Switch Module .................26 QLogic Fibre Channel Switch Module..........27 QLogic HBA..................................................27 Management Module Connecting To ............................................7, 8 View firmware levels ......................................9 Management Module Failover .........................26 Nortel Networks Switches Configuration................................................ 11 Firmware Update ......................................... 13 Layer 2/3 Switch Firmware Levels....................................... 26 Layer 2-7 Switch Firmware Levels....................................... 26 Management ................................................ 11 QLogic HBA Firmware levels............................................ 27 QLogic Switch Disabling ports ............................................. 16 Firmware level.............................................. 27 Firmware update .................................... 18, 27 SANSurfer.............................................. 17, 18 Related Documents ........................................... 5 Repeating keystrokes ...................................... 26 SAN Configuration ........................................... 21
28
2006 IBM Version 3.0, 3/10/2006 http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.