53-10000610-02 12 Mar 2008 Fabric Manager Administrator’s Guide Supporting Fabric Manager 5.5.0 Supporting Fabric OS 6.1.
Copyright © 2008 Brocade Communications Systems, Inc. All Rights Reserved. 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. and other countries.
Title Publication number Summary of changes Date Fabric Manager User’s Guide 53-0000823-07 Editorial & structural changes, included new feature support since Fabric Manager 4.1.1, updated graphics, updated troubleshooting information. May 2004 Fabric Manager User’s Guide 53-0000823-08 Editorial & structural changes, device node and device port name support, and minor adjustment for database change.
iv Fabric Manager Administrator’s Guide 53-10000610-02
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xxi What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fabric Manager server uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Uninstalling the Fabric Manager server from Windows. . . . . . . 31 Uninstalling the Fabric Manager server from Solaris . . . . . . . . 32 Uninstalling the Fabric Manager server from Linux. . . . . . . . . . 32 Chapter 3 Fabric Manager Client In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Fabric Manager Startup . . . . . . . . . . . . . . . . . . . . . . . .
Fabric component renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fabric event monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Fabric event viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Fabric event filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Viewing event details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Notification parameter configuration. . . . . . . . . . . . . . . . . . . . . . . .106 Configuring notification parameters . . . . . . . . . . .
Snapshots and change reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Displaying a change report . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Creating snapshots on demand . . . . . . . . . . . . . . . . . . . . . . . .139 Comparing snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Exporting snapshot and change reports . . . . . . . . . . . . . . . . .140 Displaying change reports in external applications. . . . . . . . .
Work with the configuration repository . . . . . . . . . . . . . . . . . . . . . .168 Viewing a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 Deleting a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 Exporting a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 Importing a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Restoring a configuration . . . . . . . . . . . . . . . . . . . . . . . . .
Access Control List management. . . . . . . . . . . . . . . . . . . . . . . . . . .188 Managing ACL policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 Propagation of RADIUS configuration across switches . . . . . . . . .189 Replicating RADIUS configuration. . . . . . . . . . . . . . . . . . . . . . .190 Chapter 14 Manage the iSCSI Target Gateway In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 About the iSCSI Target Gateway . .
Chapter 16 Zone Management In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 Introduction to zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 Offline zone management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222 Use cases for offline zoning . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Requirements for offline zoning . . . . . . . . . . . . . . . . . . . . . . . .223 Offline zone editing .
Identification of switches with FMS mode enabled . . . . . . . . . . . .262 Identifying switches with FMS mode enabled . . . . . . . . . . . . .262 Current port connectivity configuration . . . . . . . . . . . . . . . . . . . . . .262 Editing the current port connectivity configuration . . . . . . . . .263 Stored port connectivity configuration . . . . . . . . . . . . . . . . . . . . . .265 Editing a stored port connectivity configuration . . . . . . . . . . .265 Port zone conflicts. . . . . . . . . . . . .
Work with FCIP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 Viewing all FCIP Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290 FCIP tunnel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Configuring an FCIP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 FCIP tunnel management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298 Viewing FCIP tunnel Information. . . . . . . . . . . . . . .
Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323 Performing backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323 Chapter 26 Server Management Console In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325 Introduction to the Server Management Console. . . . . . . . . . . . . .325 Launching the SMC on Windows . . . . . . . . . . . . . . . . . . . . . . .
Fabric Manager support information . . . . . . . . . . . . . . . . . . . . . . . .347 Capturing Fabric Manager support information . . . . . . . . . . .348 Client issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349 Checking for authentication issues (unable to log in) . . . . . . .349 Client access to switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 Client CPU usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional problem areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357 Fabric Manager license key and serial number. . . . . . . . . . . .358 Switches and hosts do not recognize HBA after firmware download to HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358 503 Service Unavailable/Overloaded error . . . . . . . . . . . . . . .358 Installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LGPL License 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380 LGPL License 2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 MIT License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393 ONC RPC License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393 Open SSL License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii • Additional information . . . . . . . . . . . . .
• Chapter 9, “Change Management” describes how the Change Management feature works and can be set up to create reports and alerts based on defined changes. • Chapter 10, “Call Home Support” provides information on how to enable, configure, and disable the Fabric Manager Call Home feature. • Chapter 11, “Switch Configuration and Management” provides information saving baselines and comparing switches against them. It also includes information on creating custom templates.
• Appendix C, “Licenses for Third-Party Products” lists the licenses for the third-party products that are included as part of Fabric Manager. Supported hardware and software Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for the Brocade Fabric Manager 5.5.
What’s new in this document The following information was added since this document was last released: • Support for new switches • Support for user-configurable IOD Delay For further information about new features and documentation updates for this release, refer to the release notes. Document conventions This section describes text formatting conventions and important notice formats used in this document.
CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations. Key terms For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary.
For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site: http://www.fibrechannel.
• Brocade 7600—On the bottom of the chassis • Brocade 12000, Brocade 24000, and 48000—Inside the chassis next to the power supply bays • Brocade DCX—On the bottom right on the port side of the chassis 3. World Wide Name (WWN) Use the wwn command to display the switch WWN. If you cannot use the wwn command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX.
xxvi Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 1 Fabric Manager Introduction In this chapter This chapter describes the system requirements and supported operating systems, and includes the following sections: • Overview of Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Browser and platform requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Browser and platform requirements FIGURE 1 Fabric Manager client Browser and platform requirements Fabric Manager requires any browser that conforms to HTML version 4.0, JavaScript version 1.0, and Java Plug-in 1.6.0 or later. Brocade has certified and tested Fabric Manager on the platforms shown in Table 1. TABLE 1 Certified and tested platforms Operating system Browser Java plug-in (minimum) Solaris 10 (Sparc only) Firefox 2.0. 1.6.0 Linux Red Hat AS 4.0 Firefox 2.0 1.6.
Browser and platform requirements 1 FM is supported under Windows & RedHat Linux operating systems that run on top of VMWare ESX 3.0. Other virtualization software is not supported. NOTE Fabric Manager is tested and supported on English, Japanese, and German operating systems. Text entered into the application should be done using the English keyboard layout. Most of the displayed text is in English, although message strings and dates may display in the local language.
1 System requirements System requirements The system requirements for the Fabric Manager client and server software depend on the size of the fabric and whether you are using one or more machines for the client and server software. NOTE Best practices recommend that you have a dedicated system for the Fabric Manager server. For a large SAN with 1281 to 2560 ports or 51 to 80 switches, you should run the Fabric Manager client and server software on separate machines.
Fabric and switch access TABLE 2 1 System requirements for client and server machines (Continued) Operating system Installation type Solaris Requirements Small SAN 1-512 ports (1-20 switches) Medium SAN 513-1280 ports (21-50 switches) Large SAN 1281-2560 ports (51-80 switches) Client Sun Ultra 25 or equivalent UltraSPARC CPU 1 @ 750 MHz 512 MB RAM 1 GB of virtual memory Sun Ultra 25 or equivalent UltraSPARC CPU 1 @ 750 MHz 1 GB RAM 1 GB of virtual memory Sun Ultra 45 or equivalent UltraSPARC CP
1 Fabric and switch access Administrative Domains An Administrative Domain (Admin Domain) is a logical grouping of fabric elements that defines what switches, ports, and devices you can view and modify. An Admin Domain is a filtered administrative view of the fabric. The logical view presented within an Admin Domain does not hide fabrics, chassis, switches, and slots; however, the attributes of switch ports and end devices are filtered based on Admin Domain membership.
Fabric and switch access 1 • For fabrics with a Large polling definition, the Admin Domain data is gathered every 60 minutes. All switches in the fabric are expected to have the same Admin Domain membership configuration, although Fabric Manager does not validate this. Fabric Manager displays an unfiltered view in the Fabric Manager client window. All legacy (pre-5.2.
1 Fabric and switch access All fabric-level actions are limited to actions allowed by the user role that you provide for the seed switch.
Chapter 2 Installation In this chapter This chapter describes the installation process, and includes the following sections: • Planning for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Fabric Manager Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 • Fabric Manager server installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 • How to copy an installation from server to server . . .
2 Planning for the installation • RADIUS server authentication: For each RADIUS server, you need to know the IP or DNS name, authentication port and type (PAP or CHAP), and shared secret. • Switch-based authentication: You need to know the switch IP addresses. • Solaris and Linux only: NIS authentication. You need to know the host name or IP address of your NIS server and NIS domain name.
Planning for the installation 2 Installation Wizard If the installation wizard does not appear during the installation, run the DOS command dxdiag and ensure that the graphics tests run without error. If any Microsoft DirectX files are missing or any diagnostics fail, go to the Microsoft Web site and upgrade to the latest version of DirectX. Web Tools Java plug-in and Web browser Fabric Manager launches Web Tools to process some requests. Web Tools requires a Java Plug-in and a compatible Web browser.
2 Planning for the installation TABLE 3 Ports required to be opened for proper communication when using a firewall (Continued) Port Number TCP, UDP or Both Description • • 20 21 TCP Passive FTP data transfer. This range needs to be defined by the user in the ftpd.conf file.
Planning for the installation TABLE 3 2 Ports required to be opened for proper communication when using a firewall (Continued) Port Number TCP, UDP or Both Description • • • 22 TCP SSH 23 TCP Telnet/SecTelnet HTTP and HTTPS port numbers (by default, these are ports 80 and 443, respectively) TCP This is the default setting but can be changed either during installation or after using SMC. If a non-default port is used then open that port instead.
2 Planning for the installation SAN Size polling rates TABLE 4 Polling rates per SAN size Total ports managed Polling rates Performance Monitoring Fabric Manager updates Small SAN (up to 512 ports, 1-20 domains) 5 minutes 1 minute Medium SAN (513-1280 ports, 21-50 domains) 5 minutes 5 minutes1 Large SAN (1281-2560 ports, 51-80 domains) 5 minutes 30 minutes1 1. Medium SANs can take between 5 and 10 minutes to update for some actions.
Fabric Manager Upgrade 2 If you launch the Fabric Manager installation wizard on a Windows XP or 2003 machine and an After the Installation dialog box displays, click Cancel to exit. The After Installation dialog box provides access to a Windows program that exists only on a few Windows XP or 2003 machines (depending on your Windows image). If you do not cancel this program, your Fabric Manager shortcut is moved to the All Users folder after the installation is complete.
2 Fabric Manager server installation • • • • Unlimited Upgrade (10 domain to unlimited) Unlimited Upgrade (Fabric Manager 4.x unlimited to Fabric Manager 5.x unlimited) 10 Domain Limit Upgrade Version (4 to 10 domain) 4 Domain Limit Upgrade (Fabric Manager 4.x with 4 domains to Fabric Manager 5.x with 4 domains) • 10 Domain Limit Upgrade (Fabric Manager 4.x with 10 domains to Fabric Manager 5.x with 10 domains) NOTE Licensing for Fabric Manager is per-server, not one copy per site.
Fabric Manager server installation 2 The Fabric Manager installation wizard launches and asks whether you want to install the full version or the evaluation version of Fabric manager as shown in Figure 3. A valid serial number and license key are required to install the full version of Fabric Manager. FIGURE 3 Fabric Manager installation wizard 3. Select the version you want to install (Full or Evaluation), then click Next. 4.
2 Fabric Manager server installation NOTE This document uses to indicate the folder into which Fabric Manager is installed. 8. Click Next. The Select FTP Server dialog box displays. FIGURE 4 Select FTP server 9. Select whether to use the built-in FTP server or your own external FTP server. The built-in FTP server is always installed, regardless of which option you select. If you select the external FTP server, the built-in FTP server is disabled.
Fabric Manager server installation FIGURE 5 2 Specify port number 11. Enter the Web server port number. The default is 80. If you type a new Web server port number, make note of it; you must use the same port number when you launch the Fabric Manager client. Do not use port 2638; it is used internally by the Fabric Manager server. 12. Enter the starting port number. The default is 24600. If the default starting port number is not a free port number, the server cannot start up correctly.
2 Fabric Manager server installation FIGURE 6 Select authentication method 15. Select your authentication method and click Next. This is the method that will be used to authenticate users when they try to log in to the Fabric Manager server. Depending on your choice of authentication method, a new dialog box displays. 16. Provide additional information depending on the type of authentication method selected.
Fabric Manager server installation 2 NOTE If your machine is running Windows XP and it belongs to a local workgroup, but you want to authenticate the users locally (instead of using a Windows domain controller), you must perform the following Windows XP registry configuration: 1. Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest to 0. 2. Disable the guest account. 3. Create a local user and use it to log in within Fabric Manager.
2 Fabric Manager server installation For switch-based authentication: Enter the IP addresses of the switches, separating each IP address with a semicolon. When using switch-based authentication, you should enter multiple switch IP addresses. If you enter only a single switch IP address, you cannot access Fabric Manager if that switch is down. 17. Click Next. The Please select the size of the SAN dialog box displays. The selected SAN size setting can affect Fabric Manager performance.
Fabric Manager server installation FIGURE 10 2 Installation complete 21. Optional: Click the View ReadMe checkbox to open the ReadMe file after exiting the installation wizard. 22. Click Done to exit the installation wizard. The Fabric Manager server starts. If you selected to use the built-in FTP server, and if no other FTP server is installed on the Fabric Manager server, then the built-in FTP server starts.
2 Fabric Manager server installation The installation wizard provides you the choice of migrating your existing database automatically, or removing it. d. Click Yes if you want to update to the new database and automatically save your existing data, or click No to remove your current data and create the new database. e. Click Next. 4. Select the version you want to install (Full or Evaluation); then click Next. 5.
Fabric Manager server installation 2 If the default starting port number is not a free port number, the server cannot start up correctly. If you enter a new port number, you must ensure that it and the next nine port numbers represent free ports. NOTE If you are upgrading or migrating from a previous version of Fabric Manager, you might receive a message indicating that the ports are unavailable. This can occur when the ports have yet to be released by the previous uninstall.
2 Fabric Manager server installation b. Click Add. c. Optional: You can add multiple RADIUS servers by entering their configuration information and clicking Add. To edit the information you have already entered, select it from the list, make your changes, and then click Update. For password file authentication: No additional information is required. 17. Click Next. The Please select the size of the SAN dialog box displays. 18.
Fabric Manager server installation 2 4. Select the version you want to install (Full or Evaluation); then click Next. 5. Enter a serial number and license key, or accept the license agreement, depending on whether the full or evaluation version is selected. • Full version only: Type a valid serial number and license key. The serial number and license key are verified at this time. If the serial number or license key is invalid, an error message displays and you must re-enter them.
2 Fabric Manager server installation 14. Click Next. The Please select the authentication method dialog box displays. 15. Select your authentication method and click Next. This is the method that is used to authenticate users when they try to log in to the Fabric Manager server. 16. Provide additional information depending on the type of authentication method selected. For NIS authentication: Enter your NIS host name or IP address and NIS domain name.
How to copy an installation from server to server 2 18. Select the size of the SAN that Fabric Manager will be managing (Table 4 on page 14 lists the polling rates for each SAN size). 19. Click Next. When the Fabric Manager installation finishes, the Install Complete dialog box displays. 20. Click Done to exit the installation wizard.
2 How to copy an installation from server to server You can stop the services using the Server Management Console, as described in “Fabric Manager services” on page 326. 5. Delete the fmserver folder on Host2. The default from the Fabric Manager server installation on Host2 is: \server\server\fmserver 6. Delete the databases folder on Host2. The default from the Fabric Manager server installation on Host2 is: \server\db\SYBSsa9\databases 7.
Fabric Manager server uninstall 2 Fabric Manager server uninstall This section describes how to uninstall Fabric Manager from either a Windows, Solaris, or Linux platform. When you uninstall the Fabric Manager server, the FTP service is uninstalled, and the FTP root directory is deleted. Save any firmware files stored in the FTP root directory to another location before uninstalling the server. You must stop the Fabric Manager server, if it is running, before you uninstall it.
2 Fabric Manager server uninstall If you select No, be sure to restart your system before performing any other operations. 5. Click Done. User-specific information, such as login name and server port number, is stored in a separate file and is not removed when you uninstall Fabric Manager. You must manually delete this file. For more information, see “Uninstalling or upgrading Fabric Manager” on page 10. Uninstalling the Fabric Manager server from Solaris 1.
Chapter 3 Fabric Manager Client In this chapter • Fabric Manager Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Manager client uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Manager layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Manager Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Event Options. . . . . . . . . . . .
3 Fabric Manager Startup http://FMserverhost1.companyname.com:8080/ http://192.168.10.11:8080/ The Fabric Manager introduction window displays, as shown in Figure 12 on page 34. FIGURE 12 Fabric Manager introductory window 2. Click the Launch Fabric Manager link. If the browser is not configured with the correct JRE version (JRE version 1.6), then Fabric Manager redirects you to a window from which you can download the correct version.
Fabric Manager Startup FIGURE 13 3 Customizing shortcut creation 4. Type your user name and password in the login dialog, shown in Figure 14. This is the user name and password that you use to log in to the server, and not the ones used to log in to the switches. FIGURE 14 Fabric Manager login NOTE Fabric Manager stores your user name and populates the User name field automatically whenever you subsequently launch the software. The login banner displays, if one is configured.
3 Fabric Manager Startup Figure 15 shows the Fabric Manager window the first time you launch it. Note that it does not show any fabrics. You must discover fabrics before you can manage them with Fabric Manager. See “Fabric Discovery” on page 59 for information about adding devices from a SAN for Fabric Manager to begin monitoring. NOTE The screenshots in the remainder of this chapter show Fabric Manager windows in which fabrics are already discovered.
Fabric Manager client uninstall 3 Any subsequent operation that requires switch authentication will fail until you re-log in and enable the feature. For example, the following operations would not succeed: • • • • Fabric asset collection, such as GigE port info Physical Inventory collection FDMI collection Switch password changes Fabric Manager client uninstall To remove the installed Fabric Manager client, you must clear the Java Control Panel cache, as described in the following procedure.
3 Fabric Manager layout 3. Click View in the Temporary Internet Files section. 4. Select Applications from the selection menu. FIGURE 17 Java application cache viewer 5. Select Fabric Manager and click Remove Selected Application. 6. Click OK to close the Java windows.
3 Fabric Manager layout Menu bar Scope Panel View Panel Task Panel Information Panel FIGURE 18 Fabric Manager client window Scope panel The Scope panel is where you select the information to be displayed in the other panels of the Fabric Manager client. The selections you make in the Scope panel affect what is displayed in the other panels.
3 Fabric Manager layout If you select MetaSAN View, backbone fabrics, edge fabrics, and FCR switches are displayed. When you select a backbone fabric, the LSANs for the fabric are displayed. When you select an LSAN, the associated devices are shown. In Figure 20, the Fabric View is selected in the Scope panel, and the View panel displays the switches that are in the selected fabric. The view that is selected in the Scope panel determines the topology that is displayed in the View panel.
Fabric Manager layout 3 In Figure 20, the Host-Storage View is selected in the Scope panel, and the View panel displays the monitored fabrics and attached devices. See Figure 18 and Figure 19 for examples of the View panel when the SAN View and the Fabric View are selected. The View panel displays the topology for the view that is selected in the Scope panel, in this case, the Host-Storage View.
3 Fabric Manager layout FIGURE 21 Context menu for the fabric element The section directly above the View panel has the following additional components, as shown in Figure 19: • Server date and time The date and time (including the time zone) of the Fabric Manager server. • Alert count Summary of unacknowledged and unresolved alerts. Each alert type is a clickable link; if you click a link, the View panel displays the SAN view and the Information panel displays the Alerts tab for the SAN.
Fabric Manager layout 3 Server date and time Alert count Application toolbar View toolbar FIGURE 22 View panel components TABLE 5 Application toolbar buttons Icon Name Description Help Opens the online help. Print View Prints the contents of the View panel. Refresh View Refreshes the displayed information. Go Back Navigation icon: Returns to the previous view in the navigation history (if applicable).
3 Fabric Manager layout To select a task from the Task panel, click on one of the task groups, and then select the task you want from the pop-up menu that displays, as shown in Figure 23. FIGURE 23 Selecting a task from the Task panel Information panel The Information panel displays detailed information about the elements in the View panel. The Information panel consists of a series of tabs, each containing a table of information (as shown in Figure 24).
Fabric Manager layout FIGURE 25 3 Set the page size • Click Export to save the contents of the table to a tab-delimited file. The entire table contents will be exported to the file. • Click Copy to copy the contents of the table in tab-delimited text format to a file. Only the tables current contents (rows in the current view) will be copied to the file. • Click Search to search for a specific text string in the table.
3 Fabric Manager layout FIGURE 27 Customize the information visible • Click Refresh to refresh the current view. The contents in the Information panel changes depending on the element that is selected in the View panel. For example, the Information panel shown in Figure 18 (SAN View) shows a different set of tabs than the Information panel shown in Figure 19 (Fabric View).
Fabric Manager layout 3 Status indicators The colors that appear as background headers provide a quick, visual status. These colors correspond to the Status Legend available from the Help menu (Help > Status Legend). FIGURE 29 Status legend For example, Figure 30 shows the status of various switches, indicated by colored backgrounds in the View panel, the Scope panel, and the Information panel. In the Information panel, the Status column also indicates the status.
3 Fabric Manager layout Segmented switches appear with a red - (minus sign) overlaid over the topology node in the View panel. A red - (minus sign) is overlaid on the segmented switch both in the Scope and View panel of fabric view. When a new switch joins the fabric, an amber + (plus sign) is overlaid on the new switch both in the Scope and View panel of fabric view. Changing the default color of persistently disabled ports 1. Click Edit > Preferences in the Menu bar.
Fabric Manager layout Select Refresh from the Discovery menu 3 Right-click a fabric or switch and select Refresh Status Information from the context menu. Click Refresh in the View panel The header in the Information panel displays the time of the last refresh. FIGURE 31 Click Refresh in the Information panel to refresh the visible table.
3 Fabric Manager Customization Fabric Manager provides several methods for you to access modules and execute tasks: • From the menu bar • From the Task panel • From the right-click context menu When describing how you can access a module or task, this document describes one way you can do it; however, note that there might be other ways to access the same module or task. Fabric Manager Customization This section describes several ways to change the look and feel of Fabric Manager.
Fabric Manager Customization 3 2. You can use the Search button to find a column name that does not appear in the initial display. 3. Check or uncheck a column name in the dialog to display or hide it in the table. 4. To change the order in which the columns appear in the table, highlight the column and use the up and down arrows to move it. FIGURE 33 Hiding/showing table columns 5. Click OK to complete the change. Setting the number of lines on a page 1.
3 Fabric Manager Customization Sorting the information displayed within a column (ascending or descending) 1. Click the header of the column you want to reorder. Each time you click the column heading, the order toggles between ascending and descending. An up or down arrow to the right of the column name indicates the column that is sorted and whether it is in ascending (up arrow) or descending (down arrow) order.
Fabric Manager Customization FIGURE 35 3 General preferences 3. Select the table font from the Font Name menu. The default font is “Courier New.” 4. Select the font size from the Font Size menu. The default size is 11. 5. Click OK. The table font changes accordingly. This setting is persisted in the Fabric Manager database.
3 Fabric Manager Customization For example, if you name all of the switches for your Accounting team “acctx”, where x is a number, you can view only the accounting switches by typing acct in the Name text field, and clicking Filter. Only the switches that have acct in their name are then displayed in the table. Filtering elements in a table 1. In the filter text fields, type text (letters, numbers, or symbols such as a period) that are included in the elements that you want to view.
Fabric Manager Customization 3 Click the arrows in the panel headers to hide or show the panel. FIGURE 37 Hiding the View panel Default values Many options, such as Alerts history and Log parameters, can be reset to the default value by clicking Restore Defaults. SSH configuration For added security, you can use an SSH client instead of the system’s Telnet or secTelnet client. To use SSH, you must install the SSH client on the Fabric manager client host.
3 Event Options FIGURE 38 Configuring an SSH client 3. Type the full path to the SSH client. This is the client that is installed on the Fabric Manager client host. 4. Enter any parameters required for logging in to the SSH client. 5. Click OK. Event Options Configure the number of events saved in the Fabric Manager database. If you prefer, you can also choose to delete events based on their age.
Event Options FIGURE 39 3 Configuring event options 3. Type the number of events that you want to keep in the history log into the Maximum historical events in the FM DB field. 4. Select the number of days events should be kept. Choose from 1 to 30 days. 5. Click OK to save your configuration.
3 58 Event Options Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 4 Discovering and Customizing Fabrics In this chapter This chapter provides information about discovering fabrics with Fabric Manager (including running subnet scans), renaming and deleting fabrics, customizing and using the information provided in the Fabric Manager views, and synchronizing the data and time across an entire fabric. See the following topics for the steps required to accomplish the specific Fabric Management tasks: • Fabric Discovery. . . . . . . . . . . . . . . . . . . . . . .
4 Fabric Discovery During fabric discovery, if you have defined IPv6 IP addresses for the switch, Fabric Manager remembers the IP address only. If the switch has a DNS name that you have defined, Fabric Manager can remember the DNS name and use that. NOTE To discover an Admin Domain-aware fabric, you must have the role of admin with access to the physical fabric and all possible admin domains on the fabric.
Fabric Discovery 4 To discover a fabric using a DNS name, you must have an entry in the hosts.txt file in C:\WINDOWS\system2\driver\etc or in /etc on Unix-based machines. The entry should be on a new line with the format switchIP switchName. For example 10.144.8.42 mySwitch. The switch is discovered in Fabric Manager using the DNS name switchName as specified in the hosts.txt file (mySwitch in the above example). You do not need to include http:// before the IP address to discover a fabric. 3.
4 Fabric Discovery FIGURE 41 Subnet scan (above) subnet scan results (below) 2. Type the first three sets of digits of an IP address in the first three sections of the IP Address Range field. 3. Type a wildcard in the last section of the IP Address Range field to represent the range of the scan. For example: • 192.168.168.* Discovers any fabric in the address range of 192.168.168.0 through 192.168.168.255. • 192.168.168.1** Discovers any fabric in the address range of 192.168.168.100 through 192.168.
Simultaneous login to multiple switches 4 You are prompted to log in to the seed switch of each fabric you discover. 7. Click Close to close the Subnet scan dialog box. Simultaneous login to multiple switches You can use Fabric Manager to log in to multiple switches at the same time. With multiple logins, you do not need to log in to each switch individually to administer your fabric.
4 Simultaneous login to multiple switches FIGURE 42 Switch login 2. Select the switches or fabrics you want from the SAN Elements tab and click the right arrow to move them to the Selected Switches panel. You can also drag fabric or switch names from the SAN Elements tab directly into the Selected Switches panel. 3. Type your user name in the User ID field. 4. Type your password in the Password field. 5.
Fabric monitoring 4 • The switch is unreachable in Fabric Manager. When you add this unreachable switch to the Selected Switches list, the Status column text changes to Unreachable. NOTE If you did not log in to all of the switches successfully, remove the successful switches from the Selected Switches panel and retry with a new user ID and password. A key icon displays next to each switch and fabric that completes a successful login.
4 Seed switch FIGURE 44 Monitor fabrics dialog box 2. Select the fabrics you want to monitor from the left side of the window and click the right arrow to move them to the right side. 3. Click Start Monitoring. For each selected fabric, you are prompted to provide the user name and password for logging in to the seed switch (see Figure 40). 4. Type the user name and password used to log in to the switch. 5. Click OK.
Seed switch 4 ATTENTION If a seed switch is segmented or merged, historical data such as offline zone DB, Change Management profile and reports, and Firmware Download Profile can be lost. Segmentation of a seed switch does not result in formation of a new fabric. If a merge occurs, the historical data is lost only from the second fabric. You can change the seed switch as long as the following conditions are met: • • • • The new seed switch is HTTP-reachable from Fabric Manager.
4 Fabric removal from Fabric Manager FIGURE 45 Change Seed Switch dialog box 2. Select a switch to be the new seed switch from the Change Seed Switch dialog box. You can select only one switch. Only switches that are running the latest Fabric OS version in the fabric are displayed. The current seed switch is not displayed in this list. 3. Click Ok. If you are not already logged in to the seed switch, the Fabric Login dialog box displays (as shown in Figure 40).
Fabric component renaming 4 Fabric component renaming You can rename the following SAN elements in Fabric Manager: • • • • • • • “Fabric” “Switch” “Port” Switch Group - “Editing a switch group” on page 78 Port Group - see “Editing a port group” on page 80 “Device” “Device name import” In most cases, you can right-click on the element and select Rename from the pop-up menu to rename it. Fabric During the discovery process, you must enter a name for the fabric in the Fabric Discovery Login dialog box.
4 Fabric component renaming Renaming a switch 1. Right-click the switch you want to rename and select Rename from the context menu. You must be logged in to the switch to rename it. If you are not logged in to the switch, Fabric Manager prompts you to log in before proceeding. 2. Type a new name for the switch and press Enter. Port If you rename a port on a switch that runs Fabric OS versions 3.1.0 (and later) or 4.1.
Fabric component renaming FIGURE 46 4 Renaming a device port Device name import The Device Name Import wizard allows you to easily change device names by importing them. You can rename devices by: • Zone aliases • Names from a .csv file • FDMI host names Importing device names 1. Select Tasks > Device Management and Troubleshooting > Import Device Node/Port Names from the menu bar, or right-click the device in the Information panel. The Device Name Import wizard displays (see Figure 47 on page 72). 2.
4 Fabric component renaming FIGURE 47 Device Name Import wizard Zone aliases You can name devices using zone aliases by placing a WWN in a zone alias and then defining the name as you want. Subsequently, the device is identified using the name of the alias in which it was placed, using the zone alias as the name of the device.
Work with switch groups and port groups 4 The format for the .csv file is: WWN, name, comment For example: 10:00:00:00:00:00:00:00, test_node, device node for testing purposes only The parser ignores anything after the second comma to the end of the line. FDMI host names You can import FDMI host names as device port names. All FDMI host names and their WWNs that are currently in the device port database table for the selected fabric are imported.
4 Work with switch groups and port groups • • • • “Editing a switch group” on page 78 “Port group creation” on page 78 “Editing a port group” on page 80 “Deleting a switch or port group” on page 80 The groups view The right panel displays details about the selected element in the left panel. The information is displayed in an At-A-Glance. Figure 48 shows two group At-A-Glance views in the right panel of the Groups View.
Work with switch groups and port groups 4 • Information - At the bottom left of each At-A-Glance view are icons that display the types of switches and ports included in that view. You can point to these icons to get a brief summary of the switch or port type. The At-A-Glance Views contain clickable icons that perform specific tasks, ranging from changing views to opening a Telnet session. Table 7 shows the complete list of icons. Not all icons are available for all elements.
4 Work with switch groups and port groups Click this icon to create switch groups FIGURE 49 Click this icon to create port groups Switch and Port Groups view Switch group creation and population A switch can be in multiple switch groups at the same time. If a switch is removed from a fabric and it was a member of a group, it is also automatically removed from the group. Creating a switch group 1. Select Tasks > Groups > Manage Switch/Port Groups. The Groups View displays (Figure 49). 2.
Work with switch groups and port groups FIGURE 50 4 Edit Switch Groups window 4. Select the SwitchGroups icon in the right panel of the Edit Switch Groups window. The group that you create will be nested within the item that you click in this step. If you click an existing group instead of the SwitchGroups icon, your new group appears as a subgroup of that group.
4 Work with switch groups and port groups Editing a switch group 1. Select Tasks > Groups > Manage Switch/Port Groups. The Groups View displays (Figure 49). 2. Right-click SwitchGroups in the SAN Elements tab on the right side of the window, and select Edit Switch Groups from the context menu. Alternatively, you can click the switch group creation icon in the SwitchGroups panel. The Edit Switch Groups window appears, as shown in Figure 50. 3.
Work with switch groups and port groups FIGURE 51 4 Edit Port Groups window 4. Select the PortGroups icon in the right panel of the Edit Port Groups window. The group that you create will be nested within the item that you click in this step. If you click an existing group instead of the PortGroups icon, your new group appears as a subgroup of that group.
4 Work with switch groups and port groups Editing a port group 1. Select Tasks > Groups > Manage Switch/Port Groups. The Groups View displays (Figure 49). 2. Right-click PortGroups in the SAN Elements tab on the right side of the window, and select Edit Port Groups from the context menu. Alternatively, you can click the port group creation icon in the PortGroups panel. The Edit Port Groups window appears, as shown in Figure 51. 3.
Chapter 5 Fabric Topologies In this chapter This chapter provides information about the View panel within Fabric Manager. The View panel provides a graphical representation of the elements that Fabric Manager monitors and all of their connections. This includes logical SANs (LSANs) and any virtual switches and links associated with them. See the following topics for information about the using View panel: • The View panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 The View panel NOTE When you have more than 50 devices in a fabric, not all of them can be displayed in the Fabric View without affecting performance. In this case, you should select the individual devices from the Device tab to display detailed information for that device in the Fabric View. View panel toolbar items The View panel includes application toolbar buttons (see Table 5 on page 43) as well as its own set of toolbar buttons, described in Table 8.
The View panel FIGURE 53 5 Fabric Legend, three tabs Tool tips In the View panel, tool tips display when you move the mouse over an element or a link. The tool tip provides additional information about that element or link. Figure 54 shows the tool tip for a switch. When a switch is segmented from the fabric, the tool tip of the segmented switch indicates the date and time that the switch left the fabric. If the switch has joined a different fabric, the tool tip displays the name of the other fabric.
5 The View panel You can use Shift-Click to select multiple items in the View panel. If you select multiple items, the Information panel displays data only for the first item selected. You can also click and drag the select tool to select a group of items. You cannot select links using the click-and-drag method. Layout changes Click the Overview icon in the View toolbar if it is difficult to view an entire fabric in the View panel.
Topology views 5 Topology views Fabric Manager displays the following four types of topography views: SAN View Fabric View Host-Storage View MetaSAN View Displays all of the monitored fabrics in the database. Displays the topology of a single fabric; its focus is on the switches and their interconnectivity. Displays all of the monitored fabrics and their attached devices; its focus is on end-to-end connectivity. Displays backbone and edge fabrics, as well as LSAN information.
5 Topology views FIGURE 57 Displaying the backbone and edge fabrics In the MetaSAN View, you can: • View detailed information about the backbone fabric, edge fabric, IFL, and device nodes. • Perform FCR-related tasks. • Configure domain IDs on phantom switches. Displaying switch interconnectivity In the Scope panel, click Fabric View from the View menu. The View panel displays how the switches in a fabric are interconnected, as shown in Figure 58.
Topology views 5 Select the fabric you want to display, along with the Admin Domain context. Select which elements you want to display or hide. FIGURE 58 Displaying switch interconnectivity in the Fabric View In the Scope panel, you can select which fabric to display from the Fabric menu. For each fabric, you can select the Admin Domain context from the Admin Domain menu. Only the Admin Domains to which you have access are shown.
5 Topology views Select the fabrics you want to display or hide, along with the Admin Domain context. Select which elements you want to display or hide. FIGURE 59 Displaying attached devices in the Host-Storage View In the Scope panel, the Fabric Scope section enables you to select which fabrics and Admin Domain contexts to display. The Fabric Scope section lists all monitored fabrics in the SAN. Check the fabrics you want to display in the View panel, and uncheck the fabrics you want to hide.
Link information 5 In the tabbed section of the Scope panel, the Zone tab is selected. Within the Zone tab, the zone database and zone configuration are selected. The selected zone database is from the offline zone database repository, so you can see what the effects of implementing this zone database would be before you actually save it to the fabric. (See “Offline zone management” on page 222 for information about editing zones offline.
5 Link information FIGURE 61 90 Information about ISLs Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Name Server Information 6 Introduction Fabric Manager launches Web Tools to display Name Server entries listed in the Simple Name Server database (see Figure 62). This includes all Name Server entries for the fabric, not only those related to the local domain. Each row in the table represents a different device. For detailed instructions on using the Web Tools Name Server module, see the Web Tools Administrator’s Guide. FIGURE 62 Name Server view Displaying Name Server entries 1.
6 92 Introduction Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Alert and Event Monitoring 7 In this chapter This chapter provides information about the alerts and events generated in Fabric Manager. The Alerts tab within Fabric Manager provides a unified list of all of the alerts for any element you are monitoring. The Events tab provides a list of events for the selected element. Fabric events are displayed at the fabric, switch, and switch group levels. See the following topics for information about working with alerts and events: • Alert monitoring . . .
7 Alert monitoring Viewing alerts for switch groups 1. Click Tasks > Groups > Manage Switch/Port Groups. The Groups view displays (see Figure 48 on page 74). 2. Select one of the following from the tree on the left side of the window, depending on the alerts you want to display: • To view all alerts for all switch groups, select the SwitchGroups node. • To view all alerts for a specific switch group, expand the SwitchGroups node and select the user-created switch group.
Alert monitoring 7 Alert count FIGURE 64 Identifying alerts Table 9 lists the types of alerts in Fabric Manager.
7 Alert monitoring TABLE 9 96 Alert types Type of alert Description Switch Status Change Generated whenever a switch changes from Healthy to Marginal or from Healthy to Down. Note the following characteristics: • If the reason a switch is Marginal or Down changes, but the Marginal or Down status remains unchanged, a new alert is not generated. The original alert remains in the Alerts view but the reason for the Marginal or Down status is updated in the Description column.
Alert monitoring TABLE 9 7 Alert types (Continued) Type of alert Description Change Management Generated only if you have elected to receive alerts through the Change Management feature in Fabric Manager. Any alerts generated on switches or fabrics as defined in your Change Management profile are also displayed in the Alerts tab.
7 Alert monitoring TABLE 9 Alert types (Continued) Type of alert Description User authentication fails Generated when a change to the user role prevents the user from being authenticated on the switch. The last occurrence time of the alert is updated every time the condition is detected, such as when the user logs in to the switch or manually refreshes the status information, or when Fabric Manager automatically polls the switch.
Alert monitoring 7 3. Select the filters at the top of the table to narrow down the information that displays in the Alerts tab. • • • • Severity Select Severity level to display only alerts of that severity. Acked Select Yes or No to display only alerts that are acknowledged or not. Resolved Select Yes or No to display only alerts that are resolved or not. Source ID Type the IP address of a switch to display alerts only for that switch. You can use an asterisk (*) as a wildcard character.
7 Alert monitoring The Acked column value changes from No to Yes, the Acked By column value displays your user name, and the Acked Time column value displays the time that you acknowledged the alert. Alert resolution The Resolved column in the Alerts tab indicates whether an alert is resolved. You cannot manually resolve Fabric Manager alerts.
Alert monitoring 7 4. Select the time period after which resolved alerts are to be deleted. Clicking Restore to Defaults sets the alert history period to the default value (90 days). 5. Click OK. Resolved alerts are deleted after the alert history period is exceeded. Disabling automatic deletion of resolved alerts 1. Select Edit > Preferences. The Options dialog box displays. 2. Expand Server specific and click Alerts History. The Alerts History pane displays (see Figure 66). 3.
7 Fabric event monitoring 2. Expand Server specific and click Alert Display Options. The Alert Display Options pane displays (see Figure 71). 3. Select which type of alert is to be displayed in bold text in the table. 4. Click OK. FIGURE 67 Alert display options Fabric event monitoring Fabric events are events generated by the Fabric OS. Fabric Manager displays these events in the Information panel. These events are stored in the Fabric Manager database.
Fabric event monitoring 7 Viewing events for a specific fabric 1. Select the fabric in the View panel. 2. Click the Events tab in the Information panel. Viewing events for a specific switch 1. Select the switch in the View panel (Fabric View only). 2. Click the Events tab in the Information panel. Viewing events for switch groups 1. Select Tasks > Groups > Manage Switch/Port Groups. The Groups view displays (see Figure 48 on page 74). 2.
7 Fabric event monitoring FIGURE 69 Viewing all events 2. Perform one of the following actions to show only those events you are interested in, based on the column. You can also filter events that occurred within a specific time period: To filter events by Column in the All Events window a. Use the menu to limit the number of events displayed. b. Select the filter from the Filter on Column, and type the filter level in the text area to the right of it.
Fabric event monitoring 7 • Select Between and use the windows to select the time frame window for the events you want to see. b. Click Filter to filter the events as specified. Fabric event filtering You can filter the fabric events that are displayed in the Events tab according to the number of events you want to view, the severity level of the events, and the time frame. Filtering fabric events for switches and fabrics 1.
7 Notification parameter configuration FIGURE 70 Viewing event details 3. Click Close to close the window. Notification parameter configuration You can configure notification parameters for Change Management and Call Home e-mail notifications on a global basis because each user on a server shares the same configuration values. The configuration information is stored in the Fabric Manager database and persists across client and server reboots.
Notification parameter configuration 7 5. Optional: If you use an SMTP mail server that requires authentication, check the Server requires authentication check box in the SMTP area and type the username and password to be used for authentication in the Username and Password fields respectively. 6. Optional: To send a test e-mail, type an e-mail address in the Send Test E-mail To field and click Test. The Test button is unavailable until you type a valid e-mail address. 7. Click OK.
7 108 Notification parameter configuration Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 8 Performance Monitoring In this chapter • Overview of performance monitoring in Fabric Manager . . . . . . . . . . . . . . • Performance monitoring components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port data collection and alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • End-to-end monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Custom reports and graphs . . . . . . . . . . . . . . . . . . . . . .
8 Performance monitoring components Performance monitoring components Before you start using performance monitoring on your fabric, you need to be familiar with the following components: • • • • • • “Port statistics” on page 110 “End-to-end monitoring” on page 110 “Granularity” on page 111 “Reports” on page 112 “Graphs” on page 112 “Templates” on page 113 Port statistics The port statistics component within the performance monitoring feature in Fabric Manager allows you to see how much traffic a partic
Performance monitoring components 8 Fabric Manager sets monitors in the fabric only if the total monitor count is 4000 or less. If the number of monitors is greater than 4000, monitors are not set on any ports. Granularity Granularity is the timeframe for the sample values that are used to generate a report. Since Fabric Manager stores a limited number of samples for each granularity, every level of granularity is not available for all possible time ranges.
8 Performance monitoring components Reports Fabric Manager allows you to present information in two forms: reports and graphs. In Fabric Manager, you can create customized reports or you can create reports from templates. You can also save, print, and export reports created in Fabric Manager.
8 Port data collection and alerts FIGURE 73 Example real time graph with performance and port data Templates To generate an ongoing report without a specified time interval, you can create a Performance Monitor report from a template. Fabric Manager templates are described in Table 11.
8 Port data collection and alerts Port statistic data collection is not supported on switches running Fabric OS 2.x and earlier.
End-to-end monitoring 8 4. Click Update, then click OK. FIGURE 74 Configuring port data collection End-to-end monitoring Using the end-to-end monitoring feature, you can collect information about the traffic generated between devices (end-to-end), the receive/transmit traffic between devices, or both. The end-to-end monitor data is not stored on the Fabric Manager database during periods when the feature is not enabled. NOTE End-to-end Monitor is designed to be enabled at all times.
8 End-to-end monitoring NOTE The retrieval of port statistics and end-to-end monitoring of data can take longer than expected if you issue any CPU-intensive commands (such as the portTest diagnostic command) while performance monitoring is enabled. Enabling end-to-end performance monitoring 1. Log in to the seed switch of the fabric you want to monitor. 2. Select Tasks > Performance Monitoring > Configure End-to-End Monitoring. The Performance Monitoring Configuration dialog box displays. 3. Select On.
End-to-end monitoring 8 Disabling performance monitoring 1. Log in to the seed switch of the fabric you want to monitor. 2. Select the fabric in the View panel and select Tasks > Performance Monitoring > Configure End-to-End Monitoring. The Performance Monitoring Configuration dialog box displays, shown in Figure 76. FIGURE 76 Enabling/disabling end-to-end monitoring 3. Select Off and then click Save to stop the collection of end-to-end statistics.
8 Custom reports and graphs Custom reports and graphs You can use performance monitoring to create a custom one-time user report or a report for a specific timeframe. You can generate the custom Performance Monitor report in two formats: report or graph.
Custom reports and graphs 8 3.
8 Custom reports and graphs If you choose to report on generating (Tx), receiving (Rx) or aggregate (Tx/Rx), the port rate is expressed in MBytes/sec. NOTE If the port type of a switch in a fabric changes, and performance monitoring is enabled, multiple port WWNs with different port types are displayed in the Performance Monitor table and graph reports. FIGURE 79 Selecting ports for a custom report 10. Select the ports from the Available Switches list that you want to include in the report.
Custom reports and graphs FIGURE 80 8 Example tabular report 12. Optional: • Print the report. See “Printing Performance Monitor reports” on page 126. • Save the report. See “Saving Performance Monitor reports” on page 126. • Export the report. See “Exporting Performance Monitor reports” on page 126. Creating a real time Performance Monitor graph 1. Select the fabric in the View panel and select Tasks > Performance Monitoring > Generate Real Time Graph.
8 Custom reports and graphs FIGURE 81 Performance Monitor real time graph (one port visible) 3. Click Stop to stop the real time generation of the graph. Real time graphs display errors in the status bar of the report. If an error occurs, the error appears as a link, showing details about the last error that occurred. To see all errors during the reported session, click this link. Report templates You can use Performance Monitor to create report templates for customized reports or graphs.
Custom reports and graphs FIGURE 82 8 Create or generate report from a template 2. Click Create New Template. The Generate Template dialog box displays (see Figure 83). FIGURE 83 Creating a report or graph template 3. Click End-to-End Monitoring or Ports Monitoring. This defines the theme of the report that will be generated. 4.
8 Custom reports and graphs • “Top N” Conversations by Generating (Tx) traffic over time T • “Top N” Conversations by Receiving (Rx) traffic over time T • “Top N” Conversations by Aggregate (Tx/Rx) traffic over time T For port statistics reports: • • • • “Top N” of ports Generating (Tx) traffic over time T “Top N” of ports Receiving (Rx) traffic over time T “Top N” of ports Aggregate (Tx/Rx) traffic over time T Customized report 5. Type the number of results you want for the report in the Top N field.
Custom reports and graphs FIGURE 84 8 Save template 13. Type a name for the report or graph template; then click OK. Generating reports and graphs from templates 1. Select the fabric in the View panel and select Tasks > Performance Monitoring > Generate Historical reports from Template. The Generate from Template dialog box displays (see Figure 82 on page 123). 2. Select the template you want from the list; then click Generate Report.
8 Custom reports and graphs • Export (XML) - Saves the report as an XML file. The XML format is useful if you want to export the data to another application. • Export (HTML) - Saves the report as an HTML file. 4. Type a name for the report or graph. 5. Click OK. Saving Performance Monitor reports 1. Create a custom report or graph, generate a report or graph from a template, or edit an existing graph as described in the following sections: The report is displayed. 2.
Custom reports and graphs 8 3. Provide a filename for the report; then click OK. Display of saved reports and graphs You can display saved graphs and reports. Note that any graphical reports that were saved to the database using a version of Fabric Manager earlier than v5.3.0 cannot be viewed in v5.3.0 and later. Displaying a saved Performance Monitor report or graph 1. Select the fabric in the View panel and select Tasks > Performance Monitoring > Saved Reports.
8 Custom reports and graphs 3. Click Delete. The report or graph is deleted. End-to-End Monitoring graph changes Existing End-to-End Monitoring graphs can be edited as follows: • Change the graph to a linear or logarithmic format. • Select different values for the y-axis: MB/sec or MB/granularity. • Filter ports. Changing the graph format 1. Create an End-to-End Monitoring graph. See “Creating a real time Performance Monitor graph” on page 121. 2. Display the graph. 3.
Custom reports and graphs 8 NOTE You do not have to use an xslt file, but the translated information is not very useful without the style sheet. Opening a Performance Monitor report (saved as an XML file) in Excel 1. Launch Excel 2003/XP (or later). 2. Click File > Open. The Open dialog box displays. 3. Navigate to the XML file and click Open. The Import XML dialog box displays and asks if you want to open a stylesheet. 4.
8 130 Custom reports and graphs Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Change Management 9 In this chapter • Overview of change management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 • Change management profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 • Snapshots and change reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Change management profiles Change management profiles You create a change management profile so you can monitor changes to fabric elements and provide e-mail notification or alerts automatically when change occurs. Table 13 on page 133 lists the fabric elements you can monitor, and Table 14 on page 134 describes known limitations working with the change management feature.
Change management profiles FIGURE 87 9 Change Management dialog box, Manage Profiles tab Note that the Change Management dialog box does not display all change management profiles, but only those profiles of the monitored fabrics. If a displayed profile contains inaccessible fabrics, then those fabrics are not displayed in the Fabrics column.
9 Change management profiles TABLE 13 Change management profile monitored elements (Continued) Monitored element Description Port Status • • • • • • • • • • • • Security1 Switches ACL iSCSI Configured/Disabled Online/Offline Note: Down status is not reported.
Change management profiles 9 Creating a change management profile 1. Select Tasks > Change Management > Manage CM profiles. The Change Management dialog box displays with the Manage Profile tab selected (see Figure 87). Any existing profiles are displayed in the dialog box. 2. Click New Profile. The Change Management Wizard displays, as shown in Figure 88. 3. Follow the instructions in the wizard to set up the profile.
9 Snapshots and change reports The Change Management Wizard displays with existing values filled in. 3. Follow the wizard instructions as in creating a profile, making any changes to the existing values. Fabric Manager saves the cloned change management profile information to the database. NOTE Figure 87 displays a change management profile and its clone (“Zoning Profile”).
Snapshots and change reports 9 If the snapshot contains any switch configuration information, you can extract this information and export it to a file. When comparing two snapshots they both must be from the same change management profile. You can also export snapshots and change management reports as XML files. When you export change management change reports in XML format (see “Exporting snapshot and change reports” on page 140), an xslt file (style sheet) is also saved with the XML file.
9 Snapshots and change reports FIGURE 89 Change management, View Change Reports and Snapshots tab 2. Select the fabric containing the change reports you want. The Reports section displays a list of profiles and associated snapshots for that fabric. 3. Select a snapshot report (other than the baseline), then click View (in the Change Reports section) to access its change report. The Change Report is displayed as shown in Figure 90.
Snapshots and change reports FIGURE 90 9 Change report You can export the report as an XML file or as an HTML file, or print it using the buttons at the bottom of the report window. NOTE Change reports created with Fabric Manager versions earlier than v5.1.0 display only the Difference Summary; they do not display the Profile information in the header of the report. Creating snapshots on demand 1. Select Tasks > Change Management > View CM reports.
9 Snapshots and change reports Comparing snapshots 1. Select Tasks > Change Management > View CM reports. The Change Management dialog box displays with the View Change Reports and Snapshots tab selected (see Figure 89 on page 138). 2. Select the fabric containing the snapshots you want. The Reports section for that switch shows a list of profiles and associated snapshots for the fabric. 3.
Snapshots and change reports 9 Exporting switch configuration information 1. Select Tasks > Change Management > View CM reports. The Change Management dialog box displays with the View Change Reports and Snapshots tab selected (see Figure 89 on page 138). 2. Select the fabric containing the snapshots you want. The Reports section for that switch displays a list of profiles and associated snapshots for that fabric. 3. Select a snapshot in the Reports section. 4.
9 Snapshots and change reports A confirmation message displays indicating that all previous change reports (compared to the previous baseline) will be deleted. 5. Click Yes in the confirmation window to proceed. A dialog box displays asking if you want to regenerate all change reports based on the new baseline. 6. Select one of the following: • Yes to generate new change reports, then click OK. • No if you do not want to generate new change reports, then click OK.
Chapter Call Home Support 10 In this chapter • About call home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 • Call home configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 • Call home monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 About call home The supportShow and supportSave commands run in the background. When the operation completes, another e-mail message is sent with the zipped supportShow or supportSave output and XML file attachments. When the call home e-mail is configured with supportSave, this is the only e-mail received. For switches using the IPv6 address format, only supportSave information can be captured.
Call home configuration 10 NOTE There might be additional script requirements, depending on your needs. Call home modem support You can also configure call home to receive the details about the events using a modem. This can be done instead of or in addition to the e-mail or external script.
10 Call home configuration Setting up a call home configuration 1. Click Tasks > Call Home > Create or Edit configuration. The Call Home dialog box displays, as shown in Figure 91. FIGURE 91 Call Home dialog box 2. Click Add. The Call Home Configuration wizard is launched (see Figure 92 on page 147).
Call home configuration FIGURE 92 10 Call home configuration overview 3. Follow the instructions in the wizard to set up the call home configuration. Figure 93 shows you the information needed to configure the Call Home feature.
10 Call home configuration FIGURE 93 Configuring Call Home If the call home configuration is successful, you will receive a confirmation e-mail. One important thing to note during configuration is that the call home feature cannot launch an external script if the script is stored in a folder with a name containing more than one space between two words.
Call home configuration FIGURE 94 10 Confirmation of a call home configuration Editing an existing call home configuration 1. Select Tasks > Call Home > Create or Edit configuration. The Call Home dialog box displays (see Figure 91 on page 146). 2. Select a configuration from the list. 3. Click Edit to change the configuration settings. The Call Home Configuration wizard launches. Use the wizard to make changes to the configuration. 4.
10 Call home monitoring FIGURE 95 Adding switches to a call home configuration Enabling or disabling call home globally 1. Select Tasks > Call Home > Create or edit new configuration. The Call Home dialog box displays (see Figure 91 on page 146). 2. Click Enable or Disable. 3. Click OK to commit the change and close the Call Home dialog box. Call home monitoring You can view the call home alerts using the Call Home Monitoring tool.
Call home monitoring 10 Monitoring call home 1. Select Tasks > Call Home > Call Home Alert History to open the window shown in Figure 96. FIGURE 96 Call Home Monitoring window 2. (Optional) Delete an alert by selecting it in the table and clicking Delete. Use Ctrl-click to select multiple alerts.
10 152 Call home monitoring Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 11 Switch Configuration and Management In this chapter • View switch information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • View port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Synchronize date and time across a fabric . . . . . . . . . . . . . . . . . . . . . . . . . • Open a Telnet session for a nonsecure switch . . . . . . . . . . . . . . . . . . . . . . • Enable and disable switches and ports . . . .
11 View switch information FIGURE 97 Displaying switch information The Switches tab in the Information panel displays detailed information about the switches in the fabric. You can scroll across the columns in the table or you can mouse over an entry in the table to display all of the information for the switch in a single pop-up box. Tool tips must be configured in Edit > Preferences for the pop-up box to display the data you want to see.
View port information TABLE 16 11 Switch models and corresponding switch type description (Continued) Switch model Fabric Manager description Brocade 3850 2 Gbit 16-port switch with switch limit Brocade 3900 2 Gbit 32-port switch Brocade 4012 4 Gbit 12-port embedded fabric switch Brocade 4020 4 Gbit 20-port embedded fabric switch Brocade 4100 4 Gbit 32-port switch Brocade 4900 4 Gbit 64-port switch Brocade 5000 4Gbit 32-port switch Brocade 5100 8 Gbit 40-port FC switch Brocade 5300 8
11 View port information FIGURE 98 Displaying detailed port information To see the most detailed port information, launch the FC Port Connectivity View (Figure 99). The FC Port Connectivity View displays information about the FC ports on a selected switch. Launching the FC Port Connectivity View 1. Select a switch. 2. Select Tasks > Switch Management > Show FC Port Connectivity View. The FC Port Connectivity View displays.
Synchronize date and time across a fabric FIGURE 99 11 FC Port Connectivity View Synchronize date and time across a fabric You can synchronize date and time across an entire fabric. Because the firmware timestamps entries in the port log dump, you can more easily correlate events when you synchronize your fabric. You must be logged in to switches within a fabric when attempting to set the time on that fabric. The fabric configuration determines which switches you must be logged in to.
11 Open a Telnet session for a nonsecure switch Open a Telnet session for a nonsecure switch The following procedure describes how to open a Telnet session for a nonsecure switch, that is, a switch without secure mode enabled. See “Telnet on a secure fabric” on page 260 for instructions on opening a Telnet session for a secure fabric. If you prefer to use an external SSH client, see “Configuring SSH” on page 55. Opening a Telnet session for a nonsecure switch 1.
SNMP configuration 11 Configuring SNMP settings 1. Select Tasks > Configure SNMP settings. The SNMP Settings dialog box displays the default settings, as shown in Figure 101. FIGURE 101 Configuring SNMP settings 2. To change any of these settings, type the new value into the appropriate field and click Modify. • The default community string is 'public'. • The default re-try count (number of times an operation is attempted on failure) is 1. • The default operation timeout is 3 seconds.
11 Port configuration 5. Click OK to save your settings. Port configuration NOTE Port configuration is not supported for ICL port types in Fabric Manager or Web Tools. You use the Web Tools Port Management module (Figure 102) to perform the basic port configuration procedures.
Port configuration 11 Port swapping If a port malfunctions, or if you want to connect to different devices without having to re-wire your infrastructure, you can move traffic from one port to another port (swap ports) without changing the I/O Configuration Data Set (IOCDS) on the mainframe computer. Fabric Manager launches the Web Tools Port Management module to swap the ports. Web Tools automatically disables the ports prior to the swap and then re-enables them afterwards.
11 Administer ISL trunking Administer ISL trunking Interswitch link (ISL) trunking optimizes network performance by forming trunking groups that can distribute traffic across shared bandwidth. You use the Trunking tab of the Web Tools Switch Admin module (Figure 104) to view and manage trunks.
Administer license keys 11 A Web Tools license must be installed on a switch before Fabric Manager can recognize the switch. All other licenses can be installed using Fabric Manager. License key export You can export the license keys of multiple switches to a single file. You can even export keys from different switches in different fabrics to one file. The file matches the license keys to the WWN of the appropriate switch so you can quickly and easily import the keys at any time.
11 Administer license keys FIGURE 106 License Administration window 4. Click Export to File. The Save dialog box displays, as shown in Figure 107. FIGURE 107 Save dialog box 5. Optional: Check the WWN, Switch Name, and IP Address check boxes to save these switch properties to the license file. These properties are informational only and have no effect on the file. 6. Select a directory, type a name for the file, and click Export. CAUTION Do not open or manually edit this file.
Administer license keys 11 Import and restore license keys If you need to restore license keys to a switch, import them from the file where they were saved. See “License key export” on page 163 for additional information. Importing license keys from a file 1. Select Tasks > Switch Management > Import from File. The Import License -- Select license file window displays (see Figure 108). FIGURE 108 Importing a license 2.
11 Configuration management The License Administration window displays with the Switch tab selected. NOTE You can print license information about switches from the License Administration window by clicking Print. 4. Select the licenses that you want to remove and click Remove from Switch.
Switch configuration backup and restore 11 Scheduling a backup 1. Select Tasks > Switch Configuration Management > Schedule Periodic Backup. NOTE To modify an existing backup, from the menu select Edit > Preferences, expand the server specific list, and click Update Switch Configuration Backup. Make your changes in the Preferences dialog box. 2. Set the Turn On/Off Periodic Backup option to On. 3. Set the frequency and the start and end dates in the fields provided.
11 Work with the configuration repository Work with the configuration repository You can view and edit all of the saved and backed up configurations for schedules that have been created in Fabric Manager or imported using the Import feature. For each configuration, you can see the fabric name, switch name, switch IP address, switch WWN and backed up time. Marking a backup configuration as a golden copy lets you bypass the configured aging limits for that copy. Viewing a configuration 1.
Replicating configurations 11 Importing a configuration 1. On the configuration browser, click Import. 2. Select the configuration file to import from the file chooser that displays. The imported configuration will be stored in the repository and available for use. 3. Optionally, download the configuration to a switch through Tasks > Replicate Configuration. Imported configurations are not associated to any specific switch.
11 Replicating configurations Replicating a switch SNMP configuration 1. Select the switch. 2. Select Tasks > Switch Configuration Management > Replicate Configuration. 3. Choose to SNMP Configuration to launch the Replicate SNMP Configuration wizard, as shown in Figure 110. Click Next to continue. FIGURE 110 Replicating the SNMP configuration 4. Choose the source that you want to replicate. You can use a file, another switch, or the Fabric Manager Repository. Click Next to continue. 5.
Replicating configurations 11 FIGURE 111 Replicating the Fabric Watch configuration 4. Choose the source that you want to replicate. You can use a file, another switch, or the Fabric Manager Repository. Click Next to continue. 5. Depending on the source type you chose, enter (or select) the information and click Next. 6. Select the destination switch. This is the switch you want to replicate to. Click Next. 7. Click Replicate to begin the process. Replicating an entire switch configuration 1.
11 Switch configuration files backup FIGURE 112 Replicating a switch configuration 4. Choose the source that you want to replicate. You can use a file, another switch, or the Fabric Manager Repository. Click Next to continue. 5. Depending on the source type you chose, enter (or select) the information and click Next. 6. Select the destination switch. This is the switch you want to replicate to. Click Next. 7. Click Replicate to begin the process.
Physical health of a switch 11 FIGURE 113 Selecting the switches 2. Select the switches from which you want to save configuration files on the SAN Elements tab. Click the right arrow. Click Login if you need to log in to the switches. 3. Click OK. Configuration files from the selected switches are saved to the repository. Physical health of a switch The background color of the switch in the View panel and Scope panel indicates the real-time status of the switch.
11 Switch replacement in the fabric FIGURE 114 Checking the physical health of a switch To display a detailed, customizable switch status report, see “Switch health report” on page 317. Switch replacement in the fabric Use the following procedures if you want to replace a switch in the fabric. The procedure for replacing the seed switch differs from that for replacing a non-seed switch.
Asset polling configuration 11 2. Select the switch on the View panel, then right-click and select Resolve fabric membership to remove the switch from the fabric. 3. Physically connect the new switch to the fabric and power it on. Wait until Fabric Manager discovers the switch. (This might take a few minutes.) A plus symbol on the switch in the Scope panel displays. In the View panel, select the fabric and right-click.
11 Domain ID configuration on a phantom switch TABLE 17 Asset collection triggers (Continued) • Switch status change • Port disabled • Changed related to Default Zone Access mode • Zone DB manipulations • Effective Zone Cfg changed / disabled Configuring asset polling 1. Select the amount of time between polling that Fabric Manager should wait to check for state changes within the fabric. 2.
Domain ID configuration on a phantom switch 11 FIGURE 116 Select Configure Domain ID 3. Move the switch into the selected column by selecting it and clicking the right arrow. 4. Select the desired domain ID from the list, as shown in Figure 117. FIGURE 117 Choose from open Domain IDs 5. Click Apply to apply the settings, or Close to apply the settings and close the dialog box.
11 178 Domain ID configuration on a phantom switch Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 12 Manage Access Gateway-moded Switches In this chapter • Introduction to Access Gateway Management . . . . . . . . . . . . . . . . . . . . . . 179 • Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 • Access Gateway-moded switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 Access Gateway-moded switches Access Gateway-moded switches After discovery, you can view information about Access Gateway-moded switches. Discovering an Access Gateway switch Discover an Enterprise fabric by providing the IP address of the seed switch running Fabric OS v5.3.0 or later. Fabric Manager automatically discovers all these switches through the fabric. It can then communicate with the Access Gateway-moded switch directly.
Access Gateway-moded switches 12 FIGURE 119 Using the right-click menu All Access Gateway-moded switches are displayed in the information view. Backing up Access Gateway-moded switches You can choose to back up Access Gateway-moded switches in scheduled backups. For instructions, refer to “Switch configuration backup and restore” on page 166. Performing a firmware download 1. Select View > Fabric View. 2. Select the fabric containing the Access Gateway-moded switches in which you are interested. 3.
12 Access Gateway-moded switches 5. Follow the methods described in Chapter 15 “Firmware Management” to download the firmware.
Chapter 13 Configure Standard Security Features In this chapter • Password management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Secure communication over HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Truststore management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Administrative Domain management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Access Control List management . . . . . . . . .
13 Password management Passwords must adhere to the following conditions: • They must be between 8 and 40 characters long. • The password is entered exactly as you want it. • Only printable ASCII characters are included, with the following exceptions: slash (“/”), backslash (“\”), less than (“<”), greater than (“>”), ampersand (“&”), quotation mark, and apostrophe. You cannot use a backspace as part of a password within Fabric Manager.
Password management 13 2. Select the switches or fabrics for which you want to change the admin password on the SAN Elements tab, then click the right arrow to move them to the Selected Switches panel. You can also drag fabrics or switches from the SAN Elements tab directly into the Selected Switches panel. 3. Type the new admin password in the New Password field. 4. Retype the new password in the Confirm Password field. 5. Click Apply.
13 Secure communication over HTTPS Secure communication over HTTPS By default, Fabric Manager connects to all switches using HTTP. You can change the security configuration to enable switch connection using HTTP over SSL (HTTPS). The connection setting applies to the entire Fabric Manager server and not to selected switches. When setting HTTPS communication for the Fabric Manager client, all switches must support HTTPS. You change the security configuration using the Server Management Console.
Administrative Domain management 13 Administrative Domain management Using Administrative Domains (Admin Domains), you can partition the fabric into logical groups and allocate administration of these groups to different user accounts so that these accounts manage only the Admin Domains assigned to them and do not make changes to the rest of the fabric. You can create domains that are grouped together based on the type of members in the domain.
13 Access Control List management FIGURE 121 Web Tools Admin Domain module Access Control List management For switches running Fabric OS v5.2.x and later, you can create and activate Switch Connection Control (SCC) and Device Connection Control (DCC) policies in the base Fabric OS that are functionally equivalent to the SCC and DCC policies supported in Secure Fabric OS. In Secure Fabric OS, these polices are fabric-wide. In the base Fabric OS (for Fabric OS v5.2.
Propagation of RADIUS configuration across switches 13 Managing ACL policies 1. Right-click a switch and select ACL Management from the context menu. Alternatively, you can select a switch and then select Tasks > Switch Management > ACL Management. The Switch Admin module of Web Tools launches, with the ACL tab selected, as shown in Figure 122. See the Web Tools Administrator’s Guide for instructions on using this interface.
13 Propagation of RADIUS configuration across switches Replicating RADIUS configuration 1. Select Tasks > Fabric Management > Replicate AAA Configuration. The Replicate AAA Configuration wizard opens with an Overview that describes the steps you will be performing. 2. Follow the instructions in the wizard to replicate the RADIUS configuration. For additional help, click Help on the left side of the window.
Chapter Manage the iSCSI Target Gateway 14 In this chapter • About the iSCSI Target Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 • Work with iSCSI information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 • Set up iSCSI Target Gateway services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 Work with iSCSI information iSCSI Host iSCSI Host IP Network Brocade 48000 with FC4-16IP Blade FC SAN Fibre Channel Target Fibre Channel Target FIGURE 123 iSCSI Target Gateway connecting iSCSI servers to FC storage Work with iSCSI information The iSCSI tab in the Information panel displays detailed iSCSI information (see Figure 124). The iSCSI tab is available in the SAN, fabric, or switch context.
Work with iSCSI information 14 iSCSI summary The iSCSI Summary tab, shown in Figure 124, displays a summary of iSCSI-specific parameters as well as a table of information about iSCSI-capable switches. The information shown is in the context of user selection. If you made no selection, the information is SAN-wide; if you selected a fabric, the information is fabric-wide, and if you selected a switch, the information is specific to that switch.
14 Work with iSCSI information Modifying an existing port configuration Right-click a port in the table and click Configure iSCSI Ports in the context menu. The iSCSI Target Gateway Admin module displays, from which you can view and configure iSCSI ports (see “Set up iSCSI Target Gateway services” on page 197 for more information on configuring iSCSI ports). Viewing details about an existing iSCSI port configuration Right-click a port in the table and click iSCSI Port Detail View in the context menu.
Work with iSCSI information 14 FIGURE 127 iSCSI tab, iSCSI Initiators view iSCSI targets The iSCSI Targets tab, shown in Figure 128, lists all iSCSI targets (virtual targets) in the SAN, fabric, or switch. You can filter the list based on iSCSI target name (IQN) and FC target name. This tab is disabled in the switch context because virtual targets are fabric-wide entities.
14 Work with iSCSI information The Web Tools iSCSI Target Gateway Admin module displays, from which you can view and configure iSCSI targets (see “Set up iSCSI Target Gateway services” on page 197). Virtual initiators The Virtual Initiators tab, shown in Figure 129, lists the virtual initiators available in the SAN, fabric, or switch. You can filter the list based on virtual initiator name and switch name.
Set up iSCSI Target Gateway services 14 FIGURE 130 iSCSI tab, iSCSI FC Targets view iSCSI sessions The iSCSI Sessions tab, shown in Figure 131, lists all active iSCSI sessions in the SAN, fabric, or switch. You can filter the list based on initiator name and iSCSI target name. FIGURE 131 iSCSI tab, iSCSI Sessions view Set up iSCSI Target Gateway services To set up the iSCSI Target Gateway service, you use the iSCSI Target Gateway Admin module.
14 Set up iSCSI Target Gateway services • Configure iSCSI ports. • Manage iSCSI sessions and iSCSI authentications. • Edit Discovery Domain Sets that enforce iSCSI device access control. To launch the Web Tools iSCSI Target Gateway Admin module, your user account must have either the Admin or FabricAdmin role. Configuring the iSCSI Target Gateway 1. Select the SAN or an iSCSI-capable switch or fabric. 2. Select the iSCSI > iSCSI Summary in the Information panel. 3.
Chapter 15 Firmware Management In this chapter • Determine the availability of firmware-specific features . . . . . . . . . . . . . . • Built-in FTP server and firmware repository. . . . . . . . . . . . . . . . . . . . . . . . . • File transfer options configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download for multiple switches . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download to HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 Determine the availability of firmware-specific features TABLE 19 Firmware-specific features (Continued) Feature Fabric OS XPath OS 6.1.0 6.0.0 5.3.x 5.2.x 5.1.x 5.0.x 4.4.x 4.2.
Built-in FTP server and firmware repository 15 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.
15 Built-in FTP server and firmware repository Click View to read the firmware release notes. Firmware versions in your repository are displayed here. Click to import a new firmware version into your repository. Switches supported by the selected firmware version are displayed here. FIGURE 133 Firmware repository management Viewing the firmware repository 1. Select a firmware version in the Repository pane to display its information. 2.
Built-in FTP server and firmware repository 15 Importing firmware into the repository 1. Select Tasks > Firmware Management > Firmware Repository Management. The Firmware Repository Management window appears. (See Figure 133 on page 202.) 2. Click Import from File. The Import Firmware dialog box appears. FIGURE 134 Importing from a file 3. Type the path to the firmware directory or file, or click Browse to locate the firmware file and release notes on your local system.
15 Built-in FTP server and firmware repository This table displays the switches, the firmware version to be downloaded, and their current firmware version. Select a fabric to view only the switches associated with that fabric. Click to define your switch firmware policy. FIGURE 135 Fabric Profile Management window Creating a fabric profile for downloading firmware 1. Select Tasks > Firmware Management > Manage Fabric Profile. The Fabric Profile Management window appears, as shown in Figure 135. 2.
Built-in FTP server and firmware repository 15 FIGURE 136 Edit Fabric Profile window 5. For each switch, select the firmware version you want downloaded in the Desired Firmware column. Click Set All To Latest to set all switches to the latest firmware version in the repository. 6. Click OK. 7. Click Close to exit the Fabric Profile Management window. SAN firmware versions Use the SAN Firmware Information window to view firmware versions in switches across your SAN environment.
15 File transfer options configuration FIGURE 137 Viewing switch firmware information in your SAN Viewing SAN firmware information 1. Choose Tasks > Firmware Management > SAN Firmware Information View. The SAN Firmware Information window appears, as shown in Figure 137. 2. From the fabric tree, select the element whose switch information you want to view. 3. Optional: Click Print to print the firmware information.
File transfer options configuration 15 The File Transfer dialog box displays, as shown in Figure 138. FIGURE 138 Options (file transfer) 3. Configure your FTP server using one of the following procedures: If you are using the FTP server built-in with Fabric Manager: a. Click Use built-in FTP Server. b. If you do not want to use the default user name and password, click Use my user name and password. i. Type your user name in the User Name field. ii.
15 Firmware download for multiple switches 4. Click Test to ensure that you can access the FTP server specified. Fabric Manager reports success or failure. The test must be successful for certain features to work (for example, firmware download, configuration download, fabric merge check, and so on). In addition to validating connectivity to the FTP server, clicking Test writes a temporary file to the specified FTP directory.
Firmware download for multiple switches 15 The steps you perform to download firmware vary depending on where your FTP server is located: • If you are using the FTP server built in with Fabric Manager, see “Firmware download with firmware repository support” on page 209. • If your external FTP server resides on the same system as the Fabric Manager server, see “Firmware download with firmware repository support” on page 209.
15 Firmware download for multiple switches Downloading firmware to multiple switches concurrently 1. Select Tasks > Firmware Management > Firmware Download to switches. The Firmware Download to Switches dialog box opens. 2. Select the switches that you want to upgrade from the SAN Elements tab and either drag the switches to the Selected Switches panel or click the right arrow. Use Shift-click and Ctrl-click to select multiple switches. 3.
Firmware download for multiple switches 15 Downloading firmware using an external FTP server 1. Copy the .zip file containing the firmware to the local host on which the Fabric Manager client is running. 2. Unzip the file and extract its contents to the FTP home directory. You need to know where the FTP home directory is located prior to unzipping the file. 3. Select Tasks > Firmware Management > Firmware Download to switches. The Firmware Download to Switches dialog box opens, as shown in Figure 140.
15 Firmware download to HBAs You need to modify this field as follows: a. Delete the extra directory information (C:\Inetpub\ftproot) in the Firmware File field. b. If the path contains backslashes (\), convert these to forward slashes (/). c. For Fabric OS v4.x and v5.x switches only, add /release.plist to the end of the path. For example, the Firmware File field should now contain only one of the following, depending on the firmware version: 2.6.x/v2.6.2 3.x/v3.2.0_rc1 4.4.x/v4.4.0_rc1/release.
Firmware download to HBAs 15 • StorPort Miniport Driver 5-1.2A0-1h (Windows 2003 Server), Firmware 3.93A0 • FCport Driver 5-2.41a3 (Windows 2003 Server), Firmware 1.91A5, 2.70A5 • Solaris driver for Sparc systems version 6.01f and 6.11c, Firmware 3.92A2 and 3.93A0 lpfc.conf must have fdmi-on option set to 1 to turn on FDMI for the Solaris driver. FDMI-capable HBAs must be connected to an FDMI-capable switch to get FDMI functionality. FDMI is disabled by default on the Emulex HBA.
15 Firmware download to HBAs FIGURE 141 Firmware download to HBAs 8. Select the HBAs that you want to upgrade on the SAN Elements tab, and either drag them to the Selected HBAs panel or click the right arrow. Use Shift-click and Ctrl-click to select multiple HBAs. You can also drag a fabric name from the SAN Elements tab into the Selected HBAs panel to add all of the HBAs from that fabric.
Prepare for firmware download to XPath OS switches 15 Prepare for firmware download to XPath OS switches Fabric Manager does not support firmware repository management or firmware download for switches running XPath OS. For these switches, you can extract the firmware files (.zip, .tar, .gz) manually into Fabric Manager’s built-in FTP server or external FTP server, and use the FTP server configuration to perform firmware download through Web Tools—AP Edition or the command line interface.
15 FDMI device information collection FDMI device information collection FDMI device information is updated once a day as a server-side service, with a few exceptions: • Downloading firmware to HBAs starts FDMI data collection so that the data matches the download. • FDMI data for a new fabric is collected when it is discovered. Because the devices and ports must be in the database prior to storing FDMI data, data collection does not start until the device discovery is complete.
Switch reboot 15 Creating a reboot group with multiple switches 1. Select Tasks > Reboot > Create Reboot Sequence. The Create or Change Reboot Groups and Sequence dialog box displays (see Figure 142). FIGURE 142 Create or change reboot groups and sequence 2. Select a fabric from the Select Fabric list. 3. Click Create. The Create Reboot Group dialog box opens, as shown in Figure 143. FIGURE 143 Create reboot group 4. Type a name for the reboot group in the Name of the Reboot Group field. 5.
15 Switch reboot • Continue: Continues the reboot sequence when a timeout occurs. • Abort: Terminates the reboot sequence when a timeout occurs. The default selection is Prompt. 7. Type the amount of time that must elapse before the next reboot in the sequence begins in the Delay After Fabric Stabilization field. Fabric Manager considers a fabric stable when all WWNs appear in the fabricShow command output. 8. Click OK. Your reboot group is displayed automatically in the Reboot Groups tree.
Switch reboot 15 5. Optional: Type a prefix for the reboot group name in the Reboot Group Name field. If you do not enter a prefix for the reboot group, a default name of “Reboot SwitchName”, where SwitchName is the name of the switch. You must provide a prefix for each single-switch reboot group you create. 6. In the Fabric Stabilization Timeout field, specify the amount of time allowed for the fabric to stabilize before a timeout occurs. 7.
15 Switch reboot Performing a sequenced reboot 1. Log in to the switches that you want to reboot. See “Simultaneous login to multiple switches” on page 63 for additional information. 2. Select Tasks > Reboot > Sequence Reboot. The Sequence Reboot dialog box displays, as shown in Figure 145. FIGURE 145 Sequenced reboot 3. Select a fabric from the Select Fabric list. 4.
Chapter Zone Management 16 In this chapter • Introduction to zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 • Offline zone management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 • Zone management with Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Introduction to zoning Zoning enables you to partition your storage area network (SAN) into logical groups of devices that can access each other.
16 Offline zone management Offline zone management Every monitored fabric has a zone database associated with it. For fabrics with Admin Domains, every Admin Domain has a zone database associated with it. This zone database contains zone aliases, zones, and zone configurations. If no zone aliases, zones, or zone configurations are defined, the zone database is empty. A fabric or Admin Domain can have only one active zone database associated with it.
Offline zone management 16 Note that the Zone Administration module does not automatically refresh. To view updated information, you must close and relaunch the module. The Zone Administration module displays the location of each zone database: either fabric (for the active zone database) or offline repository.
16 Offline zone management Access control For live zone databases, you can update the zone databases with the following roles only: • Admin • Zone Admin • Fabric Admin If you do not have one of these roles, you can launch the Zone Editor only in read-only mode. You can update an offline zone database with any role. Admin Domain considerations If an Admin Domain is removed from the fabric, Fabric Manager deletes all of the zone databases associated with that Admin Domain.
Offline zone management 16 • For example, if you are restructuring your SAN and want to merge Fabric A with Fabric B, Fabric A loses all of the zone databases associated with it. Prior to the merge, export the offline zone databases associated with Fabric A so that you can later import them into the merged fabric. • If you downgrade the seed switch, you should first export all of the offline zone databases associated with the fabric so that you do not lose the zone databases.
16 Offline zone management Database deletion You cannot delete the zone database that is on the fabric. Every fabric has a zone database associated with it, even if the zone database is empty. Database checkout When you edit a zone database, either through the Zone Editor Tool or the Compare/Merge Zone Database module, you are implicitly checking out the zone database.
Offline zone management 16 The Zone Editor Tool has similar functionality as the Web Tools Zone Admin module. See the Web Tools Administrator’s Guide for instructions on how to create, modify, and delete zones, zone aliases, and zone configurations. FIGURE 147 Zone Editor Tool 4. To save the zone database to the fabric without changing the effective zone configuration, select File > Save Zone Database > To the fabric without enabling and then click OK in the confirmation window.
16 Offline zone management FIGURE 148 Save zone database to offline repository 6. Fill out this dialog box as follows: • To modify the current zone database, click OK. You can modify only offline (named) zone databases. You cannot replace the zone database that is on the fabric. If you have been editing a copy of the active zone database, then the name in the dialog box displays as Name of Zone DB, as shown in Figure 148.
Offline zone management c. 16 Click OK. If the name you provide does not exist in the fabric and Admin Domain, then a new zone database is created. If the name does exist, then a warning is displayed stating that a zone database with that name already exists and you must provide a different name. Comparing two zone databases 1. Select Tasks > Zone Management > Compare/Merge. Alternatively, if you are in the Zone Editor Tool, you can select Zoning Actions > Compare/Merge Zone Database.
16 Offline zone management 6. Click 3. Compare. The Reference zone database and Editable zone database sections are populated with the two zone databases you selected. Blue triangles in the tree structure indicate nodes that are different between the two zone databases. Expand the nodes to see their contents and the differences. In the Comparison Options section, you can customize the display as follows: • You can click buttons to display the entire zone databases or only the differences between the two.
Offline zone management 16 FIGURE 150 Host-to-Storage Connectivity view Figure 151 shows an example of the Storage-to-Host Connectivity view. As shown in the figure, in BrownZoneDB on the right, two of the devices lose access to the host (Intraserver, shown in red). In this example, Show Only Changes is selected so that only the differences between the two databases are shown.
16 Offline zone management FIGURE 151 Storage-to-Host Connectivity view 7. Optional: If you are in the Traditional comparison view to modify the editable zone database. Add or remove zones, aliases, and configurations from the editable zone database using Add, Merge, and Remove. You cannot modify the zone database from the Host-to-Storage or Storage-to-Host Connectivity views. Elements can appear in more than one place in the zone database.
Offline zone management 16 FIGURE 152 Compare/merge tool tips 8. Click Save to Offline to save the editable zone database in the offline repository. To save the editable zone database under a different name or different fabric and Admin Domain, click the arrow next to Save to Offline and then click Save as. Populate the fields in the dialog box (shown in Figure 148) and click OK. Merging two zone databases 1. Select Tasks > Zone Management > Compare/Merge.
16 Offline zone management FIGURE 153 Merging zones and zone configurations 7. To merge zone configurations, select one or more zone configuration nodes on the left side, select one zone configuration node on the right side, and click Merge in the Zone Config section. To merge zones or aliases, select one or more zone nodes or alias on the left side, select one zone node or alias on the right side, and click Merge in the Zone/Alias section.
Offline zone management 16 3. Right-click the zone database and select Export Zone DB from the context menu to export the contents of the zone database to local storage. The Export Zone Database dialog box (similar to a Save As dialog box) displays. 4. Type the name of the file and browse to the location where you want to save it. 5. Click Export. The zone database contents are saved as a .zip file in the location specified. Importing a zone database 1.
16 Zone management with Web Tools Undoing the automatic checkout of a zone database To undo the checkout of a zone database 1. Select Tasks > Zone Management > Zone Administration. The Zone Administration module launches, as shown in Figure 146. 2. Select a zone database that you have checked out (your user name is in the Who has taken a copy? column). 3. Right-click the zone database and select Undo Zone DB Checkout from the context menu. 4. Click Yes in the confirmation window.
Zone management with Web Tools 16 FIGURE 154 Zone Admin module 3. (Optional) Right-click the name of a device in the Member Selection list to launch the Device Detail view for that element. 4. (Optional) Click the enabled configuration button (located in the top right corner of the Zone Administration module) to view the effective zoning configuration (a separate window opens).
16 238 Zone management with Web Tools Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 17 Fabric Watch In this chapter • Work with Fabric Watch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 • Launching Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 • Fabric Watch activities in Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 Work with Fabric Watch Fabric Watch activities in Web Tools Fabric Watch navigation tree, lists the available classes for the switch Summary of actions The last time the Fabric Watch module was updated FIGURE 155 Fabric Watch module (with Alarm Notification tab displayed) You can administer Fabric Watch operations through the Fabric Watch module in Web Tools (see Figure 155). The Fabric Watch navigation tree, on the left side of the module, displays the available classes.
Chapter 18 Secure Fabric Management In this chapter This chapter provides information on enabling secure mode for a fabric, adding a switch to a secure fabric, and checking secure fabrics prior to merging them. It also includes information about using the policy editor to configure security policies, and provides instructions on how to configure no node WWN zoning, how to change admin security passwords (for FCS or non-FCS switches/directors), and how to use telnet on a secure fabric.
18 Create a secure fabric • You cannot enable secure mode for an edge fabric that is configured for Fibre Channel routing. See “FC-FC routing and secure fabrics” on page 285 for additional limitations when using the FC-FC Routing Service and secure fabrics. • You cannot enable secure mode on Admin Domain-aware fabrics. • You cannot enable secure mode if a fabric-wide consistency policy is configured on the switch. Brocade 3016 and Brocade 4020: The default administrative account is called “USERID”.
Security policy settings 18 FIGURE 157 Select security policy settings (optional) Security policy settings The Policy Editor allows you to view and configure your security policy settings.
18 Security policy settings FIGURE 158 Policy Editor (Summary tab) Using the Policy Editor 1. Select the Policy Editor (shown in Figure 158 on page 244). The Summary tab displays by default. The Summary tab displays the defined and active security policies in two panels. • The Defined Policy Set panel lists the currently defined policies (active and inactive) in the selected fabric. You can define a policy and then save it with or without activating it.
Security policy settings 18 ATTENTION The FCS list can display Access Gateway-moded switches in the list of selections while enabling security, and in the Security Policy Editor. Do not define an Access Gateway-moded switch as the primary FCS switch or in a security policy. FCS policy options configuration Fabric Configuration Server (FCS) policy configuration in Fabric OS is performed on a switch-local basis and may be performed on any switch in the fabric running Fabric OS 5.3.0 or later.
18 Security policy settings FIGURE 159 Configuring the FCS policy 3. Select a switch from the Available Switch List and complete the appropriate following action for the task you want to complete: • To add the switch to the FCS Switch List, click Add FCS. • To add all of the switches in the current fabric simultaneously, click Add All. • To add a switch that is not listed in the Available Switch List, click Add Others, type the WWN of the switch you want to add, and click Add.
Security policy settings 18 • Copy to File (to copy the Security Policy to a file) SCC policy options configuration The SCC policy defines all switches in the secure fabric (FCS and non-FCS). You cannot add a new switch to a secure fabric without adding the switch to the SCC policy. SCC policies are created automatically in Fabric Manager when you enable secure mode on a fabric. Configuring or edit the SCC policy 1.
18 Security policy settings • To remove a switch from the SCC policy, select the switch from the Fabric Switches list, then click Remove Switch. To remove a switch from an SCC policy, remove the switch from the FCS policy first. • To delete the policy, click Delete Policy. 4. Select the Summary tab. 5. Click Save to save your changes but not apply them, or click Activate to save and apply your changes. The Security Policy Review dialog box displays. 6.
Security policy settings 18 FIGURE 161 Configuring the Telnet policy 3. Click Create Policy. You have now created an empty policy, which denies the policy type (Telnet, RSNMP, WSNMP, HTTP, or API) access from all hosts to all switches in the fabric. ATTENTION If you create policies without Fabric Manager client/server IP addresses, or... If you create empty Serial, Telnet, HTTP, and API policies simultaneously, then... You will not be able to manage security and the secure fabric.
18 Security policy settings 6. Complete the following appropriate action for the task you want to perform: • To add a switch to the policy, click Add IP. The IP address is placed in the Permitted Access Points list. • To remove a switch from the policy, select the IP address from the Permitted Access Points list, then click Remove IP. • To delete the policy, click Delete Policy. 7. Select the Summary tab. 8.
Security policy settings 18 FIGURE 162 Configuring the DCC policy 3. Click Create Policy. The Enter DCC Policy dialog box displays. 4. Type a name for the new policy in the Enter Policy Name field and click Create in the Enter DCC Policy dialog box. The new name is displayed in the Policy list on the DCC tab. 5. (Optional) Click Name, IP, or WWN to change how the switches and devices are displayed in the Available Switches and Devices list. 6.
18 Security policy settings • Copy to File (to copy the Security Policy to a file) Making changes to existing DCC policies 1. In the Information panel, right-click the secure fabric for which you want to set policies and choose Security > Security Policy Editor from the context menu. The Policy Editor appears (see Figure 158 on page 244). 2. Click the DCC tab (see Figure 162 on page 251). 3.
Security policy settings 18 2. Click the tab that corresponds to the policy you want (SES or MS). The selected policy appears (see Figure 163). The SES policy is used in this example; the MS policy is similar. FIGURE 163 Configuring the SES policy 3. Click Create Policy. The WWN of a device that connects to the fabric displays in the Available Access Points list. 4. Select a device from the Available Access Points list. 5. Click Add Device. 6. Click the Summary tab. 7.
18 Security policy settings The selected policy appears (see Figure 163). 3. Perform the appropriate following action based on the action you want to perform: • To add a device to the policy, select the device in the Available Access Points list, then click Add Device. • To remove a device from the policy, select the device in the Permitted Access Points list, then click Remove Device. 4. Click the Summary tab. 5.
Security policy settings 18 FIGURE 164 Configuring the Serial policy 3. Click Create Policy. You have now created an empty policy, which denies Serial and Front Panel access from all hosts to all switches in the fabric. ATTENTION If you create policies without Fabric Manager client/server IP addresses, or... If you create empty Serial, Telnet, HTTP, and API policies simultaneously, then... You cannot manage security in the switch or on the secure fabric. 4.
18 Security policy settings • Copy to File (to copy the Security Policy to a file) Making changes to the Serial or Front Panel policy 1. In the Information panel, right-click the secure fabric for which you want to set policies and choose Security > Security Policy Editor from the context menu. The Policy Editor appears (see Figure 158 on page 244). 2. Click the tab that corresponds to the policy you want (Serial or Front Panel). The selected policy appears (see Figure 164 on page 255).
Security policy settings 18 FIGURE 165 Configuring the FCS or non-FCS admin security password 3. Type the current password in the FCS Administrator Password field. 4. Type the new password in the New Password field. 5. Type the new password again in the Verify field. 6. Perform the appropriate following action based on the task you want to perform: • To change the admin password for secure FCS switches only, click FCS Switches.
18 Add a switch to a secure fabric No-Node WWN Zoning Configuration Fabric Manager allows you to enable or disable No-Node WWN Zoning. When you enable this feature, security becomes port-oriented. Devices have port and node WWNs. When you disable node zoning, you ensure that devices with multiple ports cannot access secure fabrics with node WWNs. You must add individual port WWNs to your policies for devices to access your secure fabric. Configuring No-Node WWN Zoning 1.
Secure fabric merge 18 Secure fabric merge Fabric Manager provides a wizard to help you merge secure fabrics that are not physically connected. This wizard performs a compatibility check that identifies non-compatible parameters and enables you to create security policies for the merged fabric. Before launching the wizard, you first select the secondary fabric that you want to merge into a primary fabric. You select the primary fabric within the wizard.
18 Telnet on a secure fabric 3. Follow the instructions in the wizard to merge the secondary fabric with another (primary) secure fabric. Before performing the merge, the wizard performs a compatibility check for the two fabrics. If this check fails, you must exit the Merge Secure Fabrics wizard and fix the incompatibility using the CLI. After fixing the incompatibility, run the Merge Secure Fabrics wizard again. See the Fabric OS Command Reference for additional information about CLI commands.
Chapter 19 FICON and CUP In this chapter • Introduction to FICON and CUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Identification of switches with FMS mode enabled . . . . . . . . . . . . . . . . . . • Current port connectivity configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Stored port connectivity configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port zone conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19 Identification of switches with FMS mode enabled To configure FICON emulation features, you must have the following on all switches at either end of the tunnel: • Fabric OS v6.0 or later • FICON XRC license (for FICON XRC Emulation feature) • FICON tape license (for FICON Tape Read and FICON Tape Write Emulation features) For instructions on configuring the FICON Emulation features, refer to “Configuring an FCIP tunnel” on page 291.
Current port connectivity configuration 19 • Modify port names Other activities include: • • • • Analyze zone conflicts Activate the current configuration Refresh current information Save the current configuration for later use If you save the configuration for future use, see “Stored port connectivity configuration” on page 265 for the activation procedure. NOTE You can activate the current port connectivity configuration only for FMS-enabled switches running Fabric OS v4.4.0 or later.
19 Current port connectivity configuration FIGURE 167 Editing the port connectivity configuration 2. Complete the appropriate following action based on the type of edit you wish to make. • To block a port, click the check box in the Block column corresponding to that port. • To block all ports, click the Block All check box. • To prohibit all ports from communicating with one another, click the Prohibit All check box.
Stored port connectivity configuration 19 Resolve any conflicts identified by the Analyze Zone Conflicts tool and repeat this step until no further conflicts are identified. 4. Click Refresh to receive up-to-date information 5. Choose one of the following options. • Click Activate to activate the configuration that is currently displayed. A confirmation dialog box displays. a.
19 Port zone conflicts FIGURE 168 Activating a stored port connectivity configuration 2. Select a configuration from the CUP Port Connectivity Configurations dialog box and perform any of the following actions: • Click Activate to activate the stored configuration. • Click New to create a new configuration. This launches the Edit FICON CUP Port Connectivity Configurations dialog box (see Figure 167 on page 264). • Click Edit to edit the selected configuration.
Insistent Domain ID mode 19 Identifying port zone conflicts 1. Display the Edit FICON CUP Port Connectivity Configuration dialog box for the active configuration, as described in “Editing the current port connectivity configuration” on page 263, or for a stored configuration, as described in “Editing a stored port connectivity configuration” on page 265. 2. Optional: Click the check boxes for a combination of ports that you want to block. You can block as many ports as you want. 3.
19 Ports that completed the RNID exchange 2. Click Yes in the confirmation dialog box. The switch is disabled, and Web Tools launches and displays the Configure tab of the Switch Admin module (see Figure 170 on page 268). See the Web Tools Administrator’s Guide for instructions on using Web Tools to set the IDID mode. Afterwards, you must manually enable the switch using either Web Tools or Fabric Manager.
Link incidents 19 The Capability column identifies ports that have completed the RNID exchange with a value of FICON. Link incidents Problems that occur on links between a host and the switch, or between the storage CUP and the switch are known as link incidents. Any FRU failures are referred to as implicit link incidents. Table 20 describes the types of link and implicit link incidents.
19 Cascaded FICON setup • • • • • Turns on the insistent domain ID flag (IDID) on all switches. Enables port-based routing on 4 Gbps platform switches. Disables Dynamic Load Sharing (DLS) on all switches. Enables In-Order Delivery (IOD) on all switches. Sets High Integrity Fabric Configuration (HIFC) on the seed switch. • Fabric-wide consistency policy is configured to include SCC in strict mode. • SCC policy is created or modified to limit connectivity to only the switches in the selected fabric.
Cascaded FICON setup 19 FIGURE 171 Configure a fabric for cascaded FICON 2. Select a fabric to configure for cascaded FICON. 3. (Optional) Check the Turn ON FMS Mode check box if you want FMS mode to be set on all of the switches in the selected fabric. 4. (Optional) Click Configure IOD Delay Time to change the IOD delay by domain ID. The IOD Delay Time dialog box displays.
19 Cascaded FICON setup a. Choose the fabric from the Fabric list. This list is available only if the dialog box is launched from the Main menu. If launched from the Configure Cascaded FICON Fabric dialog box, the fabric is already selected. b. Choose a switch from the From switch list. c. Choose a switch from one of the To switch lists. You can choose a switch by either Name/IP Address or by Domain ID depending on which button is clicked. The default list is Name/IP Address.
Cascaded FICON setup 19 • Checks the fabrics for any merge issues. • Turns on the insistent domain ID (IDID) flag on all of the switches in both fabrics. • Clears Admin Domain, Access Control Lists (ACLs), and zone databases, if they exist, from one of the fabrics (you select which fabric from within the wizard). NOTE Clearing the ACL database in a large fabric might take a long time; for example, in a 50-switch fabric, this operation might take from 30 minutes to 1 hour.
19 Cascaded FICON setup FIGURE 173 Merge two fabrics for cascaded FICON 2. Follow the instructions in the wizard to merge two fabrics for cascaded FICON. If DCC policies are defined on the seed switch, they are activated when Security policies are activated on the seed switch. A message displays, notifying you that the DCC policies will be activated. If you do not want the DCC policies to be activated, click Cancel to exit the wizard. The wizard displays a summary screen upon successful fabric merge. 3.
Chapter 20 FC-FC Routing Service Management In this chapter The FC-FC Routing Service provides Fibre Channel routing between two or more fabrics without merging those fabrics. • Requirements for Fibre Channel routing . . . . . . . . . . . . . . . . . . . . . . . . . . . • About Fibre Channel routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Connect edge fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20 About Fibre Channel routing About Fibre Channel routing Fibre Channel routing provides connectivity to devices in different fabrics without merging the fabrics. For example, using Fibre Channel routing you can share tape drives across multiple fabrics without the administrative problems, such as change management, network management, scalability, reliability, availability, and serviceability, that might result from merging the fabrics.
About Fibre Channel routing 20 VE_Port Edge Fabric 2 IP Cloud Edge Fabric 1 Edge Fabric 3 E_Port E_Port IFL IFL IFL VEX_Port SilkWorm 7500 EX_Port (2) = LSAN Backbone Fabric FIGURE 174 A metaSAN with edge-to-edge and backbone fabrics For additional information about FC-FC routing, see the Fabric OS Administrator’s Guide. Setting Up FC-FC routing 1. Ensure that the backbone fabric ID of the FC Router is the same as that of other FC Routers in the backbone fabric. 2.
20 Connect edge fabrics Connect edge fabrics Fabric Manager allows you to connect edge fabrics without merging them using an FC Router. Using the following procedure, you select a fabric to be the edge fabric, then launch the FC Router Configuration wizard to configure an FC Router to which the edge fabric will be connected. The wizard prompts you to select an FC Router to connect to the edge fabric, set the fabric ID, and then select which ports on the FC Router are to be configured as EX_Ports.
Fabric device sharing diagnosis 20 Fabric device sharing diagnosis Before you set up device sharing, you can verify whether two fabrics are configured to share devices. Using the Diagnose Fabric Device Sharing wizard, you select two or more fabrics and generate a report on whether device sharing is possible for each pair of selected fabrics.
20 Device sharing between fabrics FIGURE 177 Summary screen 3. Optional: Click Print to print the summary. 4. Click Finish to exit the wizard. Device sharing between fabrics You can share devices between fabrics without merging them using an FC Router (see Figure 174 on page 277). Fabric Manager allows you to set up the shared devices with the Share Devices wizard. Using the Share Devices wizard, you must first select the devices you want to share, then the wizard creates a logical SAN (LSAN).
Device sharing between fabrics 20 FIGURE 178 Share Devices wizard 2. Read the overview information, then click Next. The Select Devices to Share screen displays (see Figure 179). Note that the wizard does not display AD-enabled fabrics or iSCSI devices (Virtual Initiators and Virtual Targets). FIGURE 179 Selecting devices to share 3. Type a name for the logical SAN (LSAN). The name is automatically prefixed with LSAN_.
20 Logical SANs and imported/exported devices 4. Select the devices you want to share using any of the following methods. You must select at least one device from the Available Devices list, and at least one device using any of the following methods: • Click the name of a device you want to share in the Available Devices list, and click the right arrow to move the device to the Selected Devices list. • Type the full path name of a valid .
FC Router information 20 FIGURE 180 Expanded LSAN Zone Information 3. Optional: Select an LSAN and click Modify LSAN. This launches the Share Devices wizard, which allows you to add or remove devices from the LSAN. 4. Optional: Select an LSAN and click Delete LSAN to delete the LSAN from the selected fabric. NOTE The Modify and Delete buttons are enabled only for users with the Admin, Fabric Admin, or Zone Admin roles. Displaying virtual devices Select Show virtual device nodes in the Scope panel.
20 FC Router information Hos t 1 P roxy Hos t 1 P roxy T arget 2 T arget 2 E dge F abric 1 E dge F abric 2 E E EX E FC Router 1 B ac kbone F abric E EX FC Router 2 FIGURE 181 Backbone fabric with multiple FC Routers NOTE In the Information Panel of a single FC Router, the information displayed in the Physical and Virtual Devices tabs varies from what is displayed in the CLI commands.
Translate domains and virtual device status 20 FIGURE 182 FCR route information Translate domains and virtual device status When you select a device in the View panel, the Information panel displays detailed information about that device. In the Overview tab, the Status field displays the status. For virtual devices created by FC-FC Routing, the Information panel might show the status as Partially Offline.
20 FC-FC routing and AD-enabled fabrics • Security operations are not supported for fabrics containing an FC Router. • Fabric Manager does not support enabling security for edge fabrics that are configured for Fibre Channel routing. FC-FC routing and AD-enabled fabrics The following limitations apply to FC-FC routing and AD-enabled fabrics: • Fabric Manager does not support FC Router configuration for AD-enabled edge fabrics.
Chapter 21 FCIP Tunneling Service In this chapter • About FCIP Tunneling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Work with FCIP information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP tunnel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP tunnel management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21 About FCIP Tunneling This means that a switch with two GigE ports can have up to 16 virtual Fibre Channel ports. A properly configured FCIP tunnel between two virtual Fibre Channel ports is an FCIP interswitch link (FCIP ISL). For a properly configured tunnel, the source or destination’s virtual Fibre Channel port must be configured as a virtual E_Port (VE_Port), and the other end configured as a virtual EX_Port (VEX_Port).
21 Work with FCIP information Figure 184 illustrates the same Fibre Channel network using FCIP but in a way that does not merge the fabrics. The FCIP interfabric link (VE_Ports connected through the IP network to VEX_Ports) allows the two SANs (Data Center FC and Office FC) to access portions of each other, but they remain separate fabrics. The path from the host (Initiator) in one SAN to the target in the other SAN is shown with a dotted line.
21 Work with FCIP information Viewing all FCIP Tunnels 1. Click the FCIP tunnels tab in the Detail Information panel to locate a specific FCIP link or ensure that all links are configured and working correctly, as shown in Figure 185. FIGURE 185 View all FCIP tunnels 2. Alternatively, click the FCIP tunnel link tab to see only active tunnels (ISLs) in the SAN or fabric, as shown in Figure 186. FIGURE 186 View active tunnel links 3.
FCIP tunnel configuration 21 FCIP tunnel configuration To configure an FCIP tunnel, you must configure the local switch, and you can configure the remote switch. If you do not configure both ends of the tunnel at this point, the administrator doing so will need to know all of the information about the local end of the tunnel and some information about the remote end of the tunnel: the IP address, subnet mask, and gateway to get to the remote end of the tunnel.
21 FCIP tunnel configuration FIGURE 189 Configuring a new FCIP tunnel After you have selected your local switch, click Next. 5. Optionally, select the remote switch. In most cases, the remote switch will be in a different fabric than the local switch, unless you are creating a redundant tunnel. 6. Click Next to continue. Selected switches are shown in the appropriate area of the window. 7.
FCIP tunnel configuration 21 • If you enter an IP address in IPv4 format, you must also enter the subnet mask ID, and it must be in IPv4 format. • If you enter an IP address in IPv6 format, do not enter a subnet mask value. The IPv6 address should be in the IPv6 address/IPv6 prefix format. FIGURE 190 Configuring the IP interface 8. Verify the connectivity of the configuration. Click Verify IP Connectivity. The IP connectivity of the connection is tested with the ping utility.
21 FCIP tunnel configuration FIGURE 192 Configuring the tunnel Enter the settings for the following fields: Tunnel ID - Each end of the tunnel has a tunnel ID, which is associated with the GigE port. Bandwidth - You can choose uncommitted, which allows the use of available uncommited bandwidth, or committed, which assigns a specific bandwidth.
FCIP tunnel configuration 21 FIGURE 193 Advanced configuration settings Because FCIP links are long distance links, speed, performance, and security are critical. These are controlled with the advanced options settings. Make your selections and click OK. Consider the following when making advanced configuration settings: • Tape Pipelining is disabled unless Fast Write is selected. Fast Write is used to improve throughput by acknowledging data locally while attempting to send it to the remote switch.
21 FCIP tunnel configuration FIGURE 194 IKE Policies These policies are used to make the connection more secure through authentication and encryption. If the IPSec policy is selected, you must specify the preshared key. The Preshared Key is the key to be used during IKE/IPSec authentication. It must be between 12 and 32 alphanumeric characters. It must also be an exact match on both switches. • FICON Emulation features are available only when all of the switches on both ends are running Fabric OS v6.0.
FCIP tunnel configuration 21 FIGURE 195 Confirming FCIP tunnel configuration The tunnel configuration begins. You can see a progress bar and the configuration results in the wizard Report panel, shown in Figure 196. FIGURE 196 Configuration in progress 13. Click Finish to close the FCIP Tunnel Configuration wizard.
21 FCIP tunnel management How MTU Suggest works When you click Suggest, Fabric Manager performs an IPPerf test on both ends of the tunnel. This utility determines the maximum transmission unit (MTU) that can be sent and received. NOTE When you use the shortcut option to launch the IP Perf or Verify IP Connectivity dialog box from the GigE Port tab, all monitored fabrics care displayed. Expand the fabric tree node to display FCIP-capable switches only.
FCIP tunnel management 21 FIGURE 197 FCIP tunnel details 2. Click Close to close the dialog box. Modifying FCIP tunnels NOTE You cannot modify an active tunnel; disable the tunnel before making changes. 1. On the FCIP Tunnel tab, right-click the tunnel to be modified and select Modify FCIP tunnel. You are prompted for confirmation, as shown. 2. Read the information on the dialog and click Modify FCIP Tunnel. You cannot select switches or fabrics at this point. 3. The Modify FCIP Tunnel wizard displays.
21 FCIP tunnel management Disabling FCIP tunnels 1. In the SAN or Fabric view, select the FCIP Tunnel or FCIP Tunnel Link tab. 2. Select the FCIP tunnel to be disabled. To select multiple tunnels, hold the CTRL key while selecting. 3. Right-click and select Disable FCIP Tunnel, as shown in Figure 198. FIGURE 198 Enabling and disabling FCIP tunnels 4. Click OK to disable the tunnel or tunnels. Re-enabling disabled FCIP tunnels 1. In the SAN or Fabric view, select the FCIP Tunnel or FCIP Tunnel Link tab.
FCIP tunnel management 21 FIGURE 199 Deleting FCIP tunnels 4. Click OK to delete the tunnel or tunnels.
21 302 FCIP tunnel management Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 22 SYSLOG Fault Management Configuration In this chapter • About Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SYSLOG destination registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SYSLOG registration policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Viewing the SYSLOG status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 SYSLOG registration policy Setting the SYSLOG server destination manually 1. Select Tasks > SYSLOG Configuration to launch the SYSLOG Server Destination Registration/Deregistration dialog box, as shown in Figure 200. FIGURE 200 Registering a SYSLOG server to a fabric 2. From the Fabric list, select the fabric to which you want to add the destination. All switches in the fabric will be added. 3. If the SYSLOG server IP address is not already defined, type the IP address in the text field. 4.
Viewing the SYSLOG status 22 Removing the autoselect SYSLOG registration policy 1. Select Tasks > SYSLOG Configuration. 2. Choose Configure SYSLOG Destination Registration Policy. 3. Clear the check mark to the left of the Auto register SYSLOG destination on the managed switches text. 4. Click OK. Viewing the SYSLOG status 1. Select Tasks > SYSLOG Configuration. 2. Select SYSLOG status from the menu to see the Syslog Status Dialog window, shown in Figure 201. FIGURE 201 Viewing the syslog status 3.
22 306 Viewing the SYSLOG status Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Third-Party and Foreign Device Management 23 In this chapter • Third-party management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 • Foreign fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Third-party management applications You can add up to three management applications to a fabric or switch. They can be either .exe Files located on the Fabric Manager client system, or URLs to the application.
23 Third-party management applications FIGURE 202 Accessing third-party applications Adding applications 1. In the View panel, right-click the fabric or switch to which you want the application associated and choose Management Application > Configure from the context menu. The Configure Application dialog box appears. FIGURE 203 Configure Application dialog box 2. Click Add. The Add application dialog box appears.
Third-party management applications 23 FIGURE 204 Add application dialog box 3. Type a name for the application. The name is what appears in the Launch submenu and does not have to be the same as the application name. 4. If you are adding a program located on your local hard disk, do the following: a. Click Executable. b. Click Browse to locate the application and click Open. Executable programs must reside on the Fabric Manager client system. c.
23 Third-party management applications Adding an application to multiple fabrics or nodes 1. In the View panel, select the fabrics or switches with which you want the application associated. 2. Right-click and choose Management Applications > Configure from the context menu that appears. 3. Follow the steps in “Adding applications” on page 308 to add the application and its arguments. 4. Click Apply to All Fabrics (or Apply to All Switches).
Third-party management applications 23 The gping program requires an IP address as an argument. This example uses the IP address of the principal switch. 6. Click Edit, select %PRINC_SWITCH_IP%, and click OK. Your Add application dialog box should look similar to Figure 206. FIGURE 206 Configure gping 7. Click OK. 8. In the Configure Applications for Switch dialog box, click Apply. 9. In the View panel, right-click the switch you just configured and choose Management Application > Launch > gping.
23 Third-party management applications 4. Click URL. 5. In the URL edit box, type http://%IP% 6. Click OK. Switch Explorer requires the IP address of the switch to display. Your dialog box should look similar to Figure 208. FIGURE 208 Configuring Switch Explorer 7. Click Apply. 8. In the View panel, right-click the switch you just configured and choose Management Application > Launch > WebTools SwitchExplorer.
Foreign fabrics 23 Foreign fabrics This section describes how you can share devices between foreign fabrics and a fabric managed by Fabric Manager. Foreign fabric definitions stored in a .csv file can be imported into Fabric Manager through the Share Devices wizard. The Share Devices wizard creates the logical SAN (LSAN) in the Brocade fabrics that are being managed from Fabric Manager.
23 Foreign fabrics FIGURE 210 Share Devices wizard, step 2 6. Click Select Device Ports. A list of the devices defined in the .csv file displays, as shown in Figure 211. FIGURE 211 Select device ports 7. Select the devices to import and click Add Selected Device Ports. The devices appear in the Selected Devices list in the wizard. 8. Click Close to close the Foreign Device Port(s) dialog box. 9. Click Next in the wizard. 10. Read the summary.
Foreign fabrics 23 If something is incorrect, click Previous and then correct it. If everything is correct, click Finish. 11. Create an LSAN in the foreign fabric, as directed by the summary step in the wizard, and ensure that the LSAN is part of the effective zone configuration.
23 316 Foreign fabrics Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Fabric Manager Reports 24 In this chapter • Switch health report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 • Fabric summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 • Physical inventory report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Switch health report Fabric Manager creates a switch health report that is Web-based.
24 Switch health report FIGURE 212 Switch Health report 2. Optional: Click the underlined links in the left panel to display detailed information about ports and Switch Availability Monitoring (SAM). 3.
Fabric summary report 24 Fabric summary report Fabric Manager creates a summary report containing information about the fabric. The report displays fabric details, switch details, health status, Admin Domain information, device port information, ISL trunking summary information and a license summary. The fabric summary report is available only for switches running the following firmware versions: • • • • Fabric OS v2.6.2 or later Fabric OS v3.2.x or later Fabric OS v4.4.x or later Fabric OS v5.0.
24 Physical inventory report FIGURE 215 Page two of the report, and the Export to option 4. Click Close to close the report. Physical inventory report For switches running Fabric OS v5.1.0 and later, the physical inventory report lets you see information about the chassis, blades, power supplies, fans and WWN cards of each switch in the physical fabric. • Switches with earlier Fabric OS versions will only show minimal information in the report, and switches running the XPath OS are not supported.
Physical inventory report 24 FIGURE 216 Physical inventory report 2. Use the arrow buttons to move to the next page of the report. From this page, you can choose to save or print the report, using the appropriate buttons. 3. To close the report, click Close.
24 322 Physical inventory report Fabric Manager Administrator’s Guide 53-10000610-02
Chapter Data Storage and Backup 25 In this chapter • Data persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 • Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Data persistence Fabric Manager stores user settings when you exit, not while you run the software. When the client attempts to log in to the server, the server authenticates the client login.
25 Backups where: • is the destination directory for the backup files. • -y is an option that causes the dbbackup utility to overwrite files without any prompt. ATTENTION Be careful with the -y option if you are always backing up the same directory. The fabman.db database file is overwritten without a prompt by this option. • -r is an option that renames and restarts the transaction log file after backing it up. You can use this option to reduce the transaction log file size.
Chapter 26 Server Management Console In this chapter • Introduction to the Server Management Console . . . . . . . . . . . . . . . . . . . . • Fabric Manager services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Authentication information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Database backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Technical support information . . . . . . . . . . . . .
26 Fabric Manager services FIGURE 217 Server Management Console, Services tab Launching the SMC on Windows • On the Fabric Manager server, select Start > Programs > FabricManager > Server Management Console Launching the SMC on Linux and Solaris 1. On the Fabric Manager server, go to the following directory: /server/util/smc/bin 2. Type the following at the command line: ./smc.
Authentication information 26 Monitoring and managing Fabric Manager services 1. Click the Services tab. The pane displays information about all of the Fabric Manager services, as shown in Figure 217. 2. Click Stop Services to stop all of the services. Click Restart Services to stop and then restart the services. Click Start Services to start the services. This button is activated only if the FM Services are already stopped.
26 Authentication information Click Authentication Audit Trail to display the log file messages from the current month and the previous month. Changing authentication information 1. Click the Authentication tab. 2. Click Edit. The Edit Authentication Information wizard appears, as shown in Figure 219. The wizard fields are populated with the existing authentication configuration. 3. Follow the instructions in the wizard to select an authentication method and configure the appropriate parameters.
Database backup and restore 26 Database backup and restore The Database tab of the Server Management Console allows you to back up and restore the Fabric Manager database (fabmandb). The Database Server must be running when you back up the database, and it must be stopped when you restore the database. NOTE You should periodically back up the database for disaster recovery and so that the database transaction log does not get too large.
26 Technical support information Restoring the database 1. Click the Database tab. 2. Click Restore Database. The Database Restore window displays. 3. Click Browse to select the path to the database. 4. Click Restore. Upon completion, a window displays the status of the restore operation. 5. Click OK to close the window. Technical support information The SupportShow tab of the Server Management Console allows you to capture technical support information.
Login banner 26 3. Click Capture Technical Support Information. The Server Management Console displays the following confirmation message when the capture is complete:. Login banner You can configure a login banner that displays after you successfully log in to Fabric Manager (see Figure 222). By default, no banner is set up. If you configure a login banner, then after a user successfully logs in to Fabric Manager, the Fabric Manager client displays the login banner dialog with two buttons.
26 Secure communication settings (HTTP or HTTPS) FIGURE 223 Server Management Console, BannerMessage tab Creating or editing the login banner 1. Click the BannerMessage tab. 2. Type a new banner message or edit the existing message. To disable the banner message, delete the existing message (set the message to a zero-length string). 3. Click Submit.
Secure communication settings (HTTP or HTTPS) 26 • Fabric Manager client machine is capable of supporting HTTPS. • All switches have a valid SSL certificate. If a fabric contains some switches running Fabric OS versions that do not support HTTPS, then southbound operations to those switches will fail. NOTE If HTTP is turned off, all client-initiated HTTP operations stop working.
26 Web Server port numbers 3. Replace the port number in the Port field if you need to use a different port number than the default. 4. Optional: If you selected Connect using HTTPS (HTTP over SSL) only, check or uncheck the following options. By default, both options are enabled. • Enable hostname verification If enabled, hostname verification fails if the name on the security certificate on the switch is invalid or does not match the name or IP address of the switch.
SYSLOG listening port 26 Changing the Web Server port number 1. Click the Settings tab. 2. Type a new port number in the Web Server port field. Do not use port 2638, and do not use the ten consecutive port numbers that were reserved for Fabric Manager during server installation. These ports are reserved for Fabric Manager to use internally. 3. Click Apply to save the changes. You must restart the server for the change to take effect.
26 336 SYSLOG listening port Fabric Manager Administrator’s Guide 53-10000610-02
Chapter 27 Fabric Troubleshooting Tools In this chapter • General device diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric merge check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Merge failure resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Event message severity level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Trace route . . . . . . . .
27 Fabric merge check 2. Follow the instructions in the wizard to set up the profile. FIGURE 226 Device Connectivity Troubleshooting wizard Fabric merge check This section describes how to perform a fabric merge check. The purpose of the fabric merge check is to show inconsistencies between the two fabrics that might cause the new fabric to segment after it has been physically connected. The fabric merge check also provides an option to resolve any zone merge issues between the selected fabrics.
Fabric merge check TABLE 22 Fabric Merge Check Component Tests All fabrics Secure fabrics only Non-secure fabric only • • • • • • • • • • • • • • • • • • • • • 1.
27 Fabric merge check NOTE If you run a fabric merge check between a secure fabric and a nonsecure fabric, the results of the Security, FCS policies, version stamp, and Management Server platform tests display the message, “Not applicable to subject fabrics.” FIGURE 228 Merge check results If the two zone databases on the fabrics will prevent the fabrics from merging, you are queried about launching the Zone Merge Manager tool. 5. Optional: Launch the Zone Merge Manager tool.
Merge failure resolution 27 Merge failure resolution If the results of a fabric merge check show failures, you can often correct the issue that is causing the failure. Most likely, changing a configuration value so that the two fabrics do not have conflicting parameters corrects the conflict; you can then merge the fabrics successfully. Run the fabric merge check again (as described in “Fabric merge check” on page 338) to verify that the issue has been corrected.
27 Merge failure resolution TABLE 23 Fabric merge check between two non-secure fabrics (Continued) Test Details/Example Corrective action LongDistanceTest LongDistance mode incompatible: fabric fabric_1 LongDistance mode: 1 fabric fabric_2 LongDistance mode: 0 Change the long distance mode value on one fabric or the other so that the values match1 InteropMode Test interop Mode incompatible: fabric fabric_1 interopMode: 0 fabric fabric_2 interopMode: 1 Change the interop mode value on one fabric
Event message severity level 27 Event message severity level Fabric Manager writes event messages to a log file, which can then be used to capture diagnostic information. You can set the log parameters to capture diagnostic information only at the severity level you want. Configuring the severity level determines which messages you want Fabric Manager to save to the log file. Any changes you make to the log level are immediate (they do not require an application restart).
27 Trace route Trace route displays detailed routing information from a source port or area on the local switch to a destination port or area on another switch. This routing information describes the exact path that a user data stream takes to go from the source port to the destination port, including all intermediate switches. NOTE Fabric Manager cannot capture the routing information if any of the switches in the path are running Fabric OS v2.x or XPath OS.
Trace route 27 2. Select two devices from the Available Devices panel and move them to the Selected devices to collect trace route panel using the arrow buttons. Alternatively, you can search for devices either by device port WWN or device port name using the Search and Add panel. The following rules apply to selecting devices: • • • • Two and only two devices must be selected. Devices must be online. Devices must not be iSCSI virtual devices. iSCSI virtual devices are filtered out.
27 Trace route 5. Click Close to exit the Trace Route Summary window. 6. Click Close to exit the Trace Route dialog box.
Appendix A Troubleshooting In this appendix • Fabric Manager support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Client issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Client/server interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Server issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric discovery problems . .
A Fabric Manager support information Fabric Manager Server data captured successfully to /test/fm4.4/FabricManager/support/2006-06-23-09-28-12/server fmgr007006:/test/fm5.2/FabricManager/bin# Capturing Fabric Manager support information 1. Perform one of the following actions, depending on your operating system to capture server-side information: • Windows: Select Start > Programs > Fabric Manager > Utilities > Capture FM Support Information to generate fmsupportshow output.
Client issues A FIGURE 232 Capture Fabric Manager support information Client issues If you suspect the problem is related to the Fabric Manager client, check the following areas: • “Checking for authentication issues (unable to log in)” on page 349 • “Client access to switches” on page 351 • “Client CPU usage” on page 351 If the problem persists or cannot be resolved, see “Capturing/reporting client issues” on page 351. Checking for authentication issues (unable to log in) 1.
A Client issues • Fabric Manager server running under Solaris or Linux when using local password authentication: File • Fabric Manager server running under Windows, Solaris, or Linux when using RADIUS authentication: RADIUS yourRADIUSserver RADIUSportnumbers CHAP;PAP;
Client/server interaction A To fix a changed authentication method problem Perform one of the following actions to restart the Fabric Manager services: Select Start > Settings > Control Panel > Administrative Tools > Services. Right-click Fabric Manager. Select Restart. or Start the Server Management Console and follow the directions outlined in “Monitoring and managing Fabric Manager services” on page 327.
A Server issues If the client has an incompatible version, a warning is issued. Checking for no client/server interaction 1. Ensure that the server name is correct. 2. Ensure that the port number is correct. 3. Ensure there is IP connectivity (for example, using ping or trace route). 4. Check for the presence of firewalls. 5. Ensure that the proper ports are opened if a firewall is present. See “Blocked port numbers” on page 11 for a complete list of ports and firewall requirements.
Server issues A If the problem persists or cannot be resolved, see “Capturing/reporting server-side issues” on page 353. Checking switch access If the server cannot access any switches, follow these steps: 1. Ensure that there is IP connectivity to the switches. 2. If you are running secure Fabric OS, check http_policy. 3.
A Fabric discovery problems #wrapper.java.additional.19=-Dserver.network.interface.sb= for example, wrapper.java.additional.19=-Dserver.network.interface.sb=192.168.22.131 3. Open /server/conf ftpservice.conf. 4. Uncomment the following entry and provide a reachable IP interface of the server: #wrapper.java.additional.5=-Dserver.network.interface.sb= for example, wrapper.java.additional.5=-Dserver.network.interface.sb=192.168.22.131 5. Save the files. 6.
supportShow and supportSave output A • Fabric Manager Client displays data that is not synchronized, it could be due to some stale cached data on the Client or Server failing to fetch the latest information from the SAN. • If the Table view is not updating: In some instances, even though the Fabric Manager Server updates the data, the Fabric Manager Client may not. So before trying the following steps wait about six minutes after the change has occurred on the fabric.
A Topology For additional information about the supportSave and supportShow commands, see the Fabric OS Command Reference. NOTE You can also generate fmSupportShow (in Windows) by clicking Start Menu > Programs > Fabric Manager > Utilities > Capture FM Support Information. Capturing the supportShow and supportSave command output 1. Click Tasks > Technical Support Information > Capture SupportSave/SupportShow. The Capture Technical Support Information wizard launches, as shown in Figure 233. 2.
Additional problem areas • • • • A “Nodes swapped with another switch node” “Lettering in legend unreadable when printed” “Links do not reconfigure after disruptive failover” “Nodes Overlap” Nodes swapped with another switch node Nodes are repositioned after expanding or collapsing link bundles in any of the topology layouts. Sometimes the nodes are not only repositioned but also swapped with another switch node.
A Additional problem areas • • • • • “Stopping Fabric Manager server on Solaris and Linux” on page 361 “Changing printers in Fabric Manager” on page 362 “Changing the time in Fabric Manager” on page 362 “ODBC driver installer error” on page 362 “fmsupportshow output file is empty” on page 362 Fabric Manager license key and serial number Fabric Manager v5.2.0 and later stores the serial number and license key in a file each time a user successfully registers Fabric Manager. The file name is fmlicense.
Additional problem areas A Installation wizard locks up Press the Ctrl key until a DOS Java console displays. The console captures a log of the entire installation process. Services not starting after upgrade After upgrading Fabric Manager, if the services do not start after the host is restarted it could be a problem with the installation program, Install Anywhere. During the upgrade process, Install Anywhere marks some files for deletion.
A Additional problem areas 3. Click Custom Level. 4. Under the Scripting category, enable the following: • Active scripting • Allow paste options through script • Scripting of Java applets 5. Click OK to close the Security Settings window. 6. In the Internet Options window, select Trusted sites and then click Sites. 7. Type the URL of the server that hosts the Fabric Manager server. 8. Uncheck the Require server verification check box. 9. Click Add. 10. Click OK to close the Internet Options window.
Additional problem areas A Relaunch the FC Router Configuration wizard by right-clicking on the edge fabric and selecting FC Router Configuration; relaunch the Device Connectivity Troubleshooting wizard by clicking Tasks>Device Management and Troubleshooting>Device Connectivity Troubleshooting (GDD). Performance monitoring The following problems might happen if you are using performance monitoring. Incorrect performance monitoring port statistics If you are running a 4.
A Additional problem areas Changing printers in Fabric Manager If you have multiple printers configured, selecting a non-default printer on the page setup dialog in Fabric Manager might crash the Fabric Manager client when you click OK. This occurs rarely on some Windows hosts. To prevent the Fabric Manager client from crashing, do not change the printer from the page setup dialog.
Additional problem areas A Fabric Manager server restarts when IP interface is changed When an IP interface is changed or an IPv4 host is transitioned to an IPv6 host by adding IPv6 interfaces, the Fabric Manager server will restart if it is already running on that host. It is recommended that you do not update IP interfaces of the host while the Fabric Manager server is running.
A 364 Additional problem areas Fabric Manager Administrator’s Guide 53-10000610-02
Appendix B CIM Representations of Fabric Elements In this appendix • About CIM and the CIM tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B SAN SAN A SAN is represented in CIM by AdminDomain. Fabrics in a SAN are represented in CIM by the ContainedDomain relationship and are not modeled in Fabric Manager. Fabric Manager has only one SAN and all fabrics are added to that SAN. Fabric A fabric is represented in CIM by AdminDomain. Use the CIM_AdminDomain view to access the fabric table.
B Device TABLE 26 CIM_ComputerSystem view (Continued) Column Type Qualifier Description Database equivalent Example OtherIdentifyingInfo String 10 String value of domain_id. This is a string[ ] in MOF. Switches.domain_id 20 IdentifyDescriptions String 8 Fixed value of “DomainID”. This is a string[ ] in CIM. None. Fixed value of 'DomainID 'DomainID ElementName String Name of switch. Switches.name Meteor1 OperationalStatus Int Switch status. Maps Switch_detail.
B Switch port Switch port CIM uses an FCPort class and a ProtocolEndPoint class for switch ports. Fabric Manager provides a CIM_FCPort view for the FCPort class. This view also contains rows for device ports. The CIM_FCPort view does not filter out virtual ports created for phantom switches. Virtual ports do not automatically show up in the switch_port table; they are created when a device node is imported from the phantom switches. Fabric Manager does not have a view for the ProtocolEndPoint class.
Switch port TABLE 29 B CIM_FCPort view (Continued) Column Type Qualifier Description Database equivalent Example Speed Double Long Bits per second. For switch_port: switch_port.port_speed For device_port: switch_port.port_speed where device_port.switch_port_wwn = switch_port.port_wwn If the join fails, it is set to 0. 2125000000 (for 2 Gbps) PortNumber Int Short PortNumber. For switch_port: switch_port.port_number. For device_port: switch_port. port_number where device_port.
B Device port TABLE 30 Port status mapping (Continued) API port status WT port status (switch_port. port_status) Operational status (CIM) Unused 1 Warning 4 Faulty No_Sync, 6 Disabled Disabled, Disabled (FMS mode) null Device port CIM uses an FCPort class and a ProtocolEndPoint class for device ports. Fabric Manager provides a CIM_FCPort view for the FCPort class. This view also contains rows for switch ports. See “Switch port” on page 368 for information on the CIM_FCPort view.
B Zone membership TABLE 32 CIM_Zone Column Type Qualifier Description Database equivalent Example Dbid Int Key Database key, used for joins to replace traversal of associations. Zone_config.dbid 1 Fabric_id Int Key of fabric. Zone_config.fabric_id 2 ElementName String Name of zone. Zone_config.name where config_type=2 LSAN_zone1 Active Int Small Boolean, 1 for zones in enabled config. If zone appears in Zone_config, members of some zone_config whose Zone_confg.
B Zone alias TABLE 34 372 CIM_NamedAddressCollection Column Type Qualifier Description Database equivalent Example Dbid Int Key Unique key. None 100 Fabric_id Int Key of fabric. Zone_config.fabric_id 2 Zone_id Int Key of zone. Zone_config.dbid 4 ElementName String 64 Name of the alias. Connectivity MemberType Int Small 2–device_port 4–domain:port 5–device Go through each member in Zone_config.members.
Appendix C Licenses for Third-Party Products In this appendix • Third-party products included in Fabric Manager . . . . . . . . . . . . . . . . . . . . • ABA License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Apache License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • AXL License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C ABA License • • • • • • • • • • • • • • • • Java Web Services 1.1 (Sun Java License) Javatar 2.5 (Public Domain) Javax.comm 3.0 (Sun Binary Code License) JBOSS 4.0.5 Application Server (LGPL License 2.1) JBOSS Rules 3.0.4 (Apache License) JDOM 1.0 (Jason Hunter & Brett McLaughlin License) JfreeChart 1.0.2 (LGPL License 2.1) Log4J package 1.2.8 (Apache License) ONC/RPC C Based RPC Library 4.0 (ONC RPC License) Open JCE v1.1 (ABA License) OpenSSL Encryption Library - v0.9.
ABA License C c) Modified files must contain a prominent notice stating the date, purpose, location and author of each change. d) All modifications must be promptly emailed to sec@aba.net.au. e) A copy of the Software must be supplied to recipient of a work, product or service which uses the Software. This condition will be considered fulfilled if the recipient is notified in writing of the Australian Business Access web site address "www.aba.net.au".
C Apache License Apache License Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
Apache License C 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License.
C AXL License 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty.
Jason Hunter & Brett McLaughlin License C AXL Radius Client License AXL Software, hereinafter referred to as AXL, grants you a worldwide non- exclusive, transferable limited license to use the Software Components comprising the Radius Client class package. You may not redistribute any of the Software Components except as follows: 1.
C LGPL License 2.0 Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2.
LGPL License 2.0 C Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it.
C LGPL License 2.0 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
LGPL License 2.0 C c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it.
C LGPL License 2.0 It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices.
LGPL License 2.1 C If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
C LGPL License 2.1 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it.
LGPL License 2.1 C We call this license the “Lesser” General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.
C LGPL License 2.1 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.
LGPL License 2.1 C This option is useful when you wish to copy part of the code of the Library into a program that is not a library. 4.
C LGPL License 2.1 b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.
LGPL License 2.1 C 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.
C LGPL License 2.1 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16.
MIT License C Technical questions about the website go to Steve M.: webmaster at opensource.org / Policy questions about open source go to the Board of Directors. The contents of this website are licensed under the Open Software License version 1.1. MIT License Copyright (c) 1999, 2003 TanukiSoftware.
C Open SSL License * SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE * INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC * OR ANY PART THEREOF. * * In no event will Sun Microsystems, Inc. be liable for any lost revenue * or profits or other special, indirect and consequential damages, even if * Sun has been advised of the possibility of such damages. * * Sun Microsystems, Inc.
Open SSL License * the documentation and/or other materials provided with the * distribution. C * * 3. All advertising materials mentioning features or use of this * software must display the following acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4.
C Open SSL License * * This product includes cryptographic software written by Eric Young * (eay@cryptsoft.com). This product includes software written by Tim * Hudson (tjh@cryptsoft.com). * */ Original SSLeay License ----------------------/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) * All rights reserved. * * This package is an SSL implementation written * by Eric Young (eay@cryptsoft.com). * The implementation was written so as to conform with Netscapes SSL.
Open Symphony License C * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * "This product includes cryptographic software written by * Eric Young (eay@cryptsoft.
C Public Domain * Copyright 2004-2005 OpenSymphony * * Licensed under the Apache License, Version 2.0 (the “License”); you may not * use this file except in compliance with the License. You may obtain a copy * of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an “AS IS” BASIS, WITHOUT * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
Reusable Objects/NetComponents License C This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
C Sun Java License To clarify, you may use the Licensed Software only to build new software you develop, and you may only distribute the Licensed Software as part of this new software. You may not include the Licensed Software in a software development kit or other library or development tool that exposes the API's of the Licensed Software without first negotiating a specific license for that purpose with ORO, Inc.
Sun Java License C THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE. 1. DEFINITIONS.
C Sun Java License 7. TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right.
Sun Binary Code License C B. License to Distribute Software.
C Sun Binary Code License 1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively “Software”), by the number of users and the class of computer hardware for which the corresponding fee has been paid. 2. RESTRICTIONS. Software is confidential and copyrighted.
Sun Binary Code License C 10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate. 11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter.
C Wolf Paulus License 4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations (“Sun Marks”), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit. 5.
Wolf Paulus License C GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
C Wolf Paulus License (9) This Application/Agreement shall be governed by California law and controlling U.S. federal law. This Application/Agreement is the parties' entire agreement relating to its subject matter, and it may not be modified unless in writing signed by an authorized representative of each party.
Index Symbols .csv file, 72 Numerics Alerts view configuring display options, 101 API policy, configuring, 248 authentication domain, 15 authentication issues, 349 authentication options, changing, 327 authentication password, 159 503 Service Unavailable/Overloaded error, 358 A AAA configuration, 189 access control. See RBAC. Access Gateway, 180 account lockout, 350 acknowledging alerts, 99 activating current port connectivity configuration, 262 stored port connectivity configuration, 265 AD.
change management configuring notification parameters, 106 limitations, 134 managing profiles, 132 snapshots and change reports, 136 taking snapshots, 139 change reports displaying, 137 displaying in Excel, 140 exporting, 140 printing, 141 changing admin password, 184 admin security password, 256 baseline snapshots, 141 default color, 48 printers, 362 Topology view layout, 84 checking physical health of a switch, 173 CIM model device, 367 device port, 370 fabric, 366 SAN, 366 switch, 366 switch port, 368 zo
customizing Fabric Manager, 50 tables, 50 D database backups full, 323, 329 database views, 365 date and time, synchronizing, 157 dbbackup utility, 323 DCC policy, configuring, 250 default color, changing, 48 deleting alerts, 100 change management profiles, 136 fabrics, 68 LSANs, 282 performance monitoring reports and graphs, 127 switch and port groups, 80 DES, 159 device diagnostic wizard, troubleshooting, 360 device diagnostics, 337 device management, diagnosing, 279 device names, 70 device port, CIM mod
exporting license keys, 163 performance monitoring reports, 126 snapshot and change reports, 140 switch configuration information, 141 external executable for call home, 144 F Fabric Configuration Server, see FCS fabric events filtering, 105 viewing, 102 Fabric Manager customizing, 50 installing, 16 installing on Linux, 26 installing on Solaris, 23 installing server, 23, 26 launching, 33 licensing, 15 registering, 16 uninstalling, 31 upgrading, 15 Fabric Manager license key and serial number, 358 Fabric Ma
FTP server (built-in) as firmware repository, 201 creating user account in, 215 full database backup, 323 G GbE ports, 288 generating reports, 317 generating reports and graphs from performance monitoring templates, 125 gping application, launching, 310 granularity levels in performance monitoring, 111 graphs, performance monitoring about, 112 creating, 121 deleting, 127 displaying, 127 editing, 128 saving, 126 groups about, 73 creating, 76, 78 deleting, 80 editing, 78, 80 H hard disk space requirements,
links customizing in Topology view, 82 viewing, 89 log level, setting, 343 logging in credentials, 36 logging in to switches and fabrics, 63 logical SANs. See LSANs.
polling rates, 14, 48 port connectivity activating current configuration, 262 activating stored configuration, 265 identifying port zone conflicts, 266 port groups about, 73 creating, 78 deleting, 80 editing, 80 port names, 70 port statistics, 110 port zone conflicts, identifying, 266 ports configuring, 160 enabling and disabling, 158 renaming, 70 primary FCS, 59 printers, changing, 362 printing performance monitoring reports, 126 snapshot and change reports, 141 privacy password, 159 profiles cloning, 135
saving performance monitoring reports and graphs, 126 supportShow and supportSave output, 355 switch configuration files, 172 SCC policy, configuring, 247 sectelnet, launching, 260 secure communication settings, changing, 332 secure fabrics adding switches to, 258 limitations with FC Routing, 285 merging, 259 using telnet, 260 secure mode enabling, 241 policy editor, 243 requirements, 241 security password, changing, 256 security policies, configuring, 245, 247, 248, 250, 252, 254 security, no-node WWN zoni
synchronizing date and time fabric-wide, 157 SYSLOG registration policy, 304 system requirements, 4 T table items, sorting, 52 tables customizing, 50 telnet, 158 Telnet policy, configuring, 248 telnet session, opening for nonsecure switch, 158 templates for performance monitoring reports, 113, 122 generating reports and graphs from, 125 third-party management applications adding, 308 editing, 310 launching, 310 time and date, synchronizing, 157 tool tips enabling and disabling, 54 Topology view, 83 topolog
418 Fabric Manager Administrator’s Guide 53-10000610-02
