User manual HP STORAGEWORKS 4/32 SAN SWITCH BROCADE FABRIC MANAGER ADMINISTRATOR'S GUIDE (53-1000610-01, APRIL 2008)

[. . . ] 53-1000610-01 Publication Date: 10/10/07 Fabric Manager Administrator's Guide Supporting Fabric Manager 5. 4. 0 Supporting Fabric OS 6. 0. 0 Copyright © 2006-2007 Brocade Communications Systems, Inc. Brocade, the Brocade B-weave logo, Fabric OS, File Lifecycle Manager, MyView, SilkWorm, and StorageX are registered trademarks and the Brocade B-wing symbol, SAN Health, and Tapestry are trademarks of Brocade Communications Systems, Inc. , in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U. S. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. [. . . ] It is Fabric OS-specific; refer to the appropriate chapters in this document for details about the way Fabric Manager supports these features. TABLE 19 Feature Firmware-specific features Fabric OS 6. 0. 0 5. 3. x X X X X X X X XPath OS 4. 1. x X X X X X X X X2 X2 X 5. 2. x X X X X X X X 5. 1. x X X X X X X X 5. 0. x X X X X X X X 4. 4. x X X X X X X X 4. 2. x X X X X 4. 0. x 3. 1. x/ 3. 2. x X 3. 0. x 2. 6. x 7. 3. x/ 7. 4. x X1 Port name change on a switch Port swapping Topology/ISL monitoring Security administration Enabling secure mode FDMI/HBA firmware download FTP server and firmware repository X X X X X X X X X X X X 3 X X X X FICON FICON-CUP X X X X X X X X X X X X X X Fabric Manager Administrator's Guide 53-1000610-01 205 15 Determining availability of firmware-specific features TABLE 19 Feature Firmware-specific features (Continued) Fabric OS 6. 0. 0 5. 3. x X X X X X X X X X X X X X X X X X X X X X X X X X X X X X XPath OS 4. 1. x 4. 0. x 3. 1. x/ 3. 2. x 3. 0. x 2. 6. x 7. 3. x/ 7. 4. x 5. 2. x X X X 5. 1. x 5. 0. x 4. 4. x 4. 2. x Cascaded FICON4 Performance Monitoring (port statistics) Performance Monitoring (end-to-end)6 QuickLoop7 Fibre Channel Router FCIP Change Management configuration checking8 supportShow information in Fabric Manager supportSave information in Fabric Manager Replicate authentication, authorization, and accounting (AAA) configuration Role-based access control (RBAC) Administrative Domains Offline zone management iSCSI management ACL management Trace Route10 1. 8. 9 X X X X X X X X X X X X X X X X X5 X5 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X XPath OS v7. 1. 2c and higher is required for LSAN view support. Topology/ISL monitoring is supported on Fabric OS v2. 6. 0k or higher and Fabric OS v3. 0. 2k or higher. All switches in the fabric must be running Fabric OS v5. 2. 0 or higher. Performance Monitoring port statistics return incorrect values for Fabric OS v4. x to 4. 2. 0b. Firmware versions v4. 2. 0c or higher work correctly. The seed switch must be running Fabric OS v3. x/4. x or higher for End-to-End Performance Monitoring to be enabled. The QuickLoop feature can be implemented only on switches running Fabric OS v2. x/3. x; however, when using a seed switch running Fabric OS v4. x, you can see the Fabric OS v2. x/3. x switches in QuickLoops. If a fabric has a switch running firmware versions 2. 6. x or earlier, 3. 0 or earlier, or XPath OS v7. 1. 0, Change Management switch configuration checking is not supported. Fabric Manager uses one switch in the fabric to collect security policy information through the API. Fabric Manager cannot collect security policy information for a fabric if the switch it selects is running firmware versions 2. 6. x or earlier, 3. 0 or earlier, or XPath OS v7. 1. 0 because the API does not support those versions of firmware or that switch type. The seed switch must be running Fabric OS v4. 4. 0 or higher or Fabric OS v5. 0. 0 or higher. 9. 10. At least one switch in the trace route must be running Fabric OS v5. 2. 0 or higher. 206 Fabric Manager Administrator's Guide 53-1000610-01 Using built-in FTP server and firmware repository 15 Using built-in FTP server and firmware repository Fabric Manager contains a built-in FTP server that can be used as a firmware repository. The firmware repository has the following advantages: · Displaying firmware based on version. · Providing an interface from which SAN users can retrieve the latest firmware from Brocade or other repositories. · Helping you select the appropriate firmware for switches. · Reporting a SAN-wide inventory of firmware currently installed on fabric switches. These features are also available if you choose to use your own FTP server. Your own FTP server must reside on the same system as the Fabric Manager server and the user name must have root access to the FTP server. You decide whether to use this built-in FTP server or your own FTP server during the installation process. You can change the server you use at any time, as described in "Configuring file transfer options" on page 212. NOTE Fabric Manager does not support firmware repository management or firmware download for switches running XPath OS. See "Downloading firmware to XPath OS switches" on page 221 for information on downloading firmware to these switches. The remainder of this section discusses features available only if you are using the built-in FTP server or if your FTP server resides on the same system as the Fabric Manager server. VIEWING THE FIRMWARE REPOSITORY If you use the built-in FTP server, downloaded firmware versions reside in the Fabric Manager software installation directory under <installdir>/server/server/fmserver/ftproot. A hierarchical structure is created, with each firmware version in its own folder, as in the following example: C:/FabricManager/Server/Server/fmserver/FTPRoot/Switches/4. x/4. 3. x/4. 3 If you use your own external FTP server, downloaded firmware versions reside in your FTP Root directory. [. . . ] (3) You agree to abide by the SWIXML Trademark and Logo Usage Requirements located at http://www. swixml. org/license. txt. You may not alter the logo in any way, including its size, proportions, colors or elements, or otherwise change its appearance. The logo must appear by itself; it may not be combined with any other graphic or textual elements and may not be used as an element of any other logo or mark. (4) Your use of the logo must be truthful and not misleading nor may it imply any relationship with, or endorsement or sponsorship by SWIXML. [. . . ]