Brocade Fabric Manager Administrator's Guide (53-10000196-01-HP, November 2006)

ManualsBrandsHP ManualsStorageHP StorageWorks SAN Switch 2/16V

Publication Number: 53-1000196-01-HP

Publication Date: 10/31/06

Fabric Manager

Administrator’s Guide

Supporting Fabric Manager 5.2.0

Supporting Fabric OS v5.2.0

Summary of content (406 pages)

PAGE 1
Fabric Manager Administrator’s Guide Supporting Fabric Manager 5.2.0 Supporting Fabric OS v5.2.
PAGE 2
Copyright © 2006 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the Brocade B weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm, and StorageX are registered trademarks and Tapestry is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered trademarks of IBM Corporation in the U.S. and other countries.
PAGE 3
Document History The following table lists all versions of the Fabric Manager Administrator’s Guide. Title Publication Number Summary of Changes Date Brocade Fabric Manager User’s Guide, v3.0 53-0000204-01 N/A October 2001 Brocade Fabric Manager User’s Guide, v4.0 53-0000823-02 N/A April 2003 Brocade Fabric Manager User’s Guide, v4.1.0 53-0000823-04 N/A September 2003 Brocade Fabric Manager User’s Guide, v4.1.
PAGE 4
PAGE 5
Contents About This Document How This Document Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Supported Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi What’s New in This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Additional Information . . . . . . . . . . . . . . . . . .
PAGE 6
Copying an Installation from Server to Server . . . . . . . . . . . . . . . . . . . . . . . . 2-20 Uninstalling the Fabric Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Chapter 3 Fabric Manager Client Launching Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Uninstalling the Fabric Manager Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Understanding the Fabric Manager Layout . . . . . . . . . . . . .
PAGE 7
Renaming Fabric Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Renaming a Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Renaming a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Renaming a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Renaming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
Chapter 7 Monitoring Alerts and Events Monitoring Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Viewing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Identifying Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Filtering Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Chapter 9 Change Management Using Change Management Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Cloning a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Editing a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Deleting a Profile . . . . . . . . . . . . . .
PAGE 10
Configuring Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7 Swapping Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Administering ISL Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9 Administering License Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10 Exporting License Keys . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Viewing iSCSI Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 iSCSI Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 iSCSI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 iSCSI Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 iSCSI Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Chapter 15 Managing Zones Introduction to Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 Managing Zoning Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 Use Cases for Offline Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 Requirements for Offline Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 Offline Zone Editing . . . . . . . . . . . . . . . . . . . . .
PAGE 13
Configuring Insistent Domain ID Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6 Identifying Ports That Completed the RNID Exchange . . . . . . . . . . . . . . . . . 18-8 Monitoring Link Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9 Cascaded FICON Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9 Configure a Fabric for Cascaded FICON . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
Chapter 22 Creating Reports Displaying the Switch Health Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1 Chapter 23 Storing Data and Performing Backups Data Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1 Performing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1 Full Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
Checking the Client Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3 Authentication Issues (Unable to Login) . . . . . . . . . . . . . . . . . . . . . . . . . 26-3 Client Access to Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5 Client-Side CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-5 Capturing/Reporting Client-Side Issues . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 16
Pinpointing Additional Problem Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-11 Locating Fabric Manager License Key and Serial Number . . . . . . . . . . . 26-11 Switches and Hosts Do Not Recognize HBA After Firmware Download to HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-12 503 Service Unavailable/Overloaded Error . . . . . . . . . . . . . . . . . . . . . . . 26-12 Installation Wizard . . . . . . . . . . . . . . . .
PAGE 17
Apache License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 AXL License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6 Jason Hunter & Brett McLaughlin License . . . . . . . . . . . . . . . . . . . . . . . . . . B-7 LGPL License 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8 LGPL License 2.1 . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 18
xviii Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 19
About This Document The Fabric Manager Administrator’s Guide is written to help you, the storage area network (SAN) administrator, to monitor, configure, and manage your SAN. This document is specific to Fabric Manager version 5.2.0 and all switches running Brocade Fabric OS version 5.2.0 and XPath version 7.1.2c or later. For a detailed list of the firmware and hardware versions that are supported with specific versions of Fabric Manager, refer to the Fabric Manager release notes.
PAGE 20
xx • Chapter 8, “Using Performance Monitoring,” provides information about the Performance Monitoring feature of Fabric Manager. • 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.
PAGE 21
Supported Hardware and Software This document supports the following platforms: • • • • • • • • • • Brocade SilkWorm 200E switch Brocade SilkWorm 3250 switch Brocade SilkWorm 3850 switch Brocade SilkWorm 3900 switch Brocade SilkWorm 4100 switch Brocade SilkWorm 4900 switch Brocade SilkWorm 7500 switch Brocade SilkWorm 24000 director Brocade SilkWorm 48000 director Brocade SilkWorm Multiprotocol Router Model AP7420 Although many different software and hardware configurations are tested and supported by Br
PAGE 22
• Information that was changed: - Fabric Manager client interface Installation instructions Server Management Console For further information, refer to the Fabric Manager release notes. Document Conventions This section describes text formatting conventions, important notices formats, and special term use.
PAGE 23
Key Terms For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at http://www.snia.org/education/dictionary. Additional Information This section lists additional Brocade and industry-specific documentation that you might find helpful.
PAGE 24
• • • SilkWorm 48000 QuickStart Guide FR4-18i Hardware Reference Manual FR4-16IP Hardware Reference Manual SilkWorm 24000 • • SilkWorm 24000 Hardware Reference Manual SilkWorm 24000 QuickStart Guide SilkWorm 24000/48000 • • • • • • • • • Port Blade and Filler Panel Replacement Procedure Control Processor Blade Replacement Procedure Blower Assembly Replacement Procedure Cable Management Tray and Guide Replacement Procedure Chassis Door Replacement Procedure WWN Bezel and Card Replacement Procedure Pow
PAGE 25
SilkWorm 3250/3850 • • SilkWorm 3250/3850 Hardware Reference Manual (for v4.x software) SilkWorm 3250/3850 QuickStart Guide (for v4.x software) SilkWorm 200E • SilkWorm 200E Hardware Reference Manual (for v5.
PAGE 26
Getting Technical Help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1. General Information • • • • • • • • • 2.
PAGE 27
Document Feedback Because quality is our first concern at Brocade, we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.com Provide the title and version number and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
PAGE 28
xxviii Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 29
Chapter Introducing Fabric Manager 1 This chapter describes the system requirements and supported operating systems, and includes the following sections: • • • • “Overview of Fabric Manager” on page 1-1 “Browser and Platform Requirements” on page 1-2 “System Requirements” on page 1-4 “Fabric and Switch Access” on page 1-5 Overview of Fabric Manager Fabric Manager is a fabric monitor and management application that provides a central point of control for multiple switches and fabrics.
PAGE 30
1 Browser and Platform Requirements Figure 1-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.5.0_06 or higher. Brocade has certified and tested Fabric Manager on the platforms shown in Table 1-1. Table 1-1 Certified and Tested Platforms Operating System Browser Java Plug-In Solaris 10 (Sparc only) Firefox 1.5. 1.5.0_06 Linux Red Hat AS 4.0 Firefox 1.5 1.5.
PAGE 31
Browser and Platform Requirements • • 1 Linux Red Hat AS 3.0 Windows 2000 Server SP4 Operating systems that are running on top of any virtualization software (such as VMWare or Microsoft Virtual Server) are not supported. Note Some browsers must be configured to work with Fabric Manager. For information about how to do this, see “Configuring Internet Explorer,” next.
PAGE 32
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 It is recommended 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.
PAGE 33
Fabric and Switch Access Table 1-2 System Requirements for Client and Server Machines (Continued) Operating Machine System Type Solaris 1 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 CPU 1
PAGE 34
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.
PAGE 35
Fabric and Switch Access 1 Role-Based Access Control Role-Based Access Control (RBAC) defines the capabilities that a user account has based on the role the account has been assigned. For each role, there is a set of pre-defined permissions on the jobs and tasks that can be performed on a fabric and its associated fabric elements. When you log in to a switch, your user account is associated with a pre-defined role.
PAGE 36
1 1-8 Fabric and Switch Access Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 37
Chapter Installation 2 This chapter describes how to install, upgrade, or uninstall the Fabric Manager server software. You do not need to explicitly install the Fabric Manager client at this time; the Fabric Manager client automatically installs the first time you launch it.
PAGE 38
2 Planning for the Installation Uninstalling or Upgrading Fabric Manager Fabric Manager stores user-specific information, such as username and server port number, for each user in a FabricManager.Properties file. This file is not removed when you uninstall Fabric Manager. You must manually delete it. FabricManager.Properties is located in your home directory on the file system. For example: C:\Documents and Settings\userA\Fabric Manager\\client\FabricManager.
PAGE 39
Planning for the Installation 2 IP Connection to Switches The Fabric Manager client and server software poll different fabric information directly, necessitating access to each switch via an IP connection. Ensure that the network environment does not have a proxy server or firewall between the switches and the server and clients. If a proxy server or firewall exists, ensure that proper rules are set up to allow access.
PAGE 40
2 Upgrading Fabric Manager Ensure that the recommended J2SE patches for Solaris Java applications are installed. Use the appropriate patch for your version of Solaris. These patches can be found at: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access Note You might encounter issues when using XWindows emulators from Windows to access the SUN host.
PAGE 41
Upgrading Fabric Manager 2 Licence Keys If you are upgrading to Fabric Manager 5.2.0 from a version earlier than 5.0.0, you need a new license key. License keys for versions prior to 5.0.0 can no longer be used. Upgrading from Fabric Manager 5.0.0 or 5.1.0 does not require a new Fabric Manager license. Fabric Manager has the following license types: • • • • • • • 4 Domain Limit • 10 Domain Limit Upgrade (Fabric Manager 4.x with 10 domains to Fabric Manager 5.
PAGE 42
2 Installing the Fabric Manager Server Installing the Fabric Manager Server This section describes how to install the Fabric Manager server using the installation wizard. • • • “Installing Fabric Manager Server on Windows” on page 2-6 “Installing Fabric Manager Server on Solaris” on page 2-14 “Installing Fabric Manager Server on Linux” on page 2-17 Installing Fabric Manager Server on Windows Use the following procedure to install the Fabric Manager server on a Windows platform.
PAGE 43
Installing the Fabric Manager Server • 2 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. You cannot continue installing the full version without a valid serial number and license key. • 5. Evaluation version only: Accept the license agreement. Click Next. If you already have Fabric Manager 4.
PAGE 44
2 Installing the Fabric Manager Server Figure 2-3 9. Select FTP Server Select whether to use the built-in FTP server or your own external FTP server. The FTP server is used primarily for firmware download. To use the Fabric Manager firmware repository, you must either select the built-in FTP server or, if you select the external FTP server, ensure that your FTP server resides on the same system as the Fabric Manager server.
PAGE 45
Installing the Fabric Manager Server Figure 2-4 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, as 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.
PAGE 46
2 Installing the Fabric Manager Server Figure 2-5 Select Authentication Method 14. Select your authentication method and click Next. This is the method that will be used to authenticate users when users try to log in to the Fabric Manager server. 15. Provide additional information depending on the type of authentication method selected. Figure 2-6 Windows Domain or Workgroup Authentication For Windows domain or work group authentication: Type the Windows Domain or Workgroup name.
PAGE 47
Installing the Fabric Manager Server 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.
PAGE 48
2 Installing the Fabric Manager Server c. Figure 2-8 Optional: You can add multiple RADIUS servers by entering their configuration information and clicking Add. To edit information you have already entered, select a server from the table at the bottom of the window, make your changes, and click Update. Switch-Based Authentication For switch-based authentication: Enter the IP addresses of the switches, separating each IP address with a semicolon.
PAGE 49
Installing the Fabric Manager Server Figure 2-9 2 Select SAN Size 17. Select the size of the SAN that Fabric Manager will be managing (Table 2-1 lists the polling rates for each SAN size).
PAGE 50
2 Installing the Fabric Manager Server Figure 2-10 Installation Complete 20. Optional: Click the View ReadMe checkbox to open the ReadMe file after exiting the installation wizard. 21. Click Done to exit the install 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.
PAGE 51
Installing the Fabric Manager Server 2 If you selected Yes: a. Select whether you have client, server, or both installed and click Next. b. Identify the location where the previous Fabric Manager client is installed and click Next. c. Identify the location where the previous Fabric Manager server is installed and click Next. The install wizard provides you the choice of migrating your existing database automatically, or removing it. d.
PAGE 52
2 Installing the Fabric Manager Server The Specify Port Number window appears. 12. 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, as it is used internally by the Fabric Manager server. 13. 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.
PAGE 53
Installing the Fabric Manager Server a. 2 Enter values for the following: - RADIUS server IP address or DNS name. - Shared secret and confirm shared secret. The shared secret is a password for the RADIUS client and server. It is used in an encryption process to obscure details in RADIUS messages like user passwords. - It is recommended that the shared secret should be at least 22 characters containing mixed case letters with numeric and symbol or punctuation characters. - Timeout.
PAGE 54
2 Installing the Fabric Manager Server The Get User Input window displays. 3. Click Yes if you have a previous version of Fabric Manager installed; otherwise, click No and then click Next. If you selected Yes: a. Select whether you have client, server, or both installed and click Next. b. Identify the location where the previous Fabric Manager client is installed and click Next. c. Identify the location where the previous Fabric Manager server is installed and click Next.
PAGE 55
Installing the Fabric Manager Server 2 11. Click Install. Fabric Manager is installed on your machine. The Specify Port Number window appears. 12. 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, as it is used internally by the Fabric Manager server. 13. Enter the starting port number. The default is 24600.
PAGE 56
2 Copying an Installation from Server to Server a. Enter values for the following: - RADIUS server IP address or DNS name. - Shared secret and confirm shared secret. The shared secret is a password for the RADIUS client and server. It is used in an encryption process to obscure details in RADIUS messages like user passwords. - It is recommended that the shared secret should be at least 22 characters containing mixed case letters with numeric and symbol or punctuation characters. - Timeout.
PAGE 57
Copying an Installation from Server to Server • 2 Fabric Manager server will use the same ports on Host2 that are used on Host1. If the Web server port number on Host1 is already in use on Host2, use the Server Management Console on Host2 to change the Web Server port number after installation, as described in “Changing the Web Server Port Number” on page 24-10. • The user will enter the Host2 name/IP address when connecting from the Fabric Manager client.
PAGE 58
2 Uninstalling the Fabric Manager Server Note After copying the Fabric Manager server installation from Host1 to Host2 and confirming that it is working as expected on Host2, you might want to uninstall the Fabric Manager server installation from Host1 so that your switches are polled by only one Fabric Manager server. To upgrade the Fabric Manager server installation on Host2 1.
PAGE 59
Uninstalling the Fabric Manager Server 2 Figure 2-11 Fabric Manager Uninstall Wizard 3. Click Next. You must restart your system when uninstallation is complete. You are prompted whether you want the wizard to restart your system immediately, or whether you want to restart your system yourself. 4. Select Yes to automatically restart your system immediately, or No to restart your system yourself. If you select No, be sure to restart your system before performing any other operations. 5. Click Done.
PAGE 60
2 Uninstalling the Fabric Manager Server To uninstall the Fabric Manager server from Linux 1. Stop the Fabric Manager server, if it is running. See “Managing Fabric Manager Services” on page 24-2 for instructions. 2. Navigate to the location where you installed Fabric Manager. 3. From the Fabric Manager/ UninstallerData directory, run Uninstall_FabricManager. 4. Click Next. You must restart your system when uninstallation is complete.
PAGE 61
Chapter Fabric Manager Client 3 This chapter includes the following topics: • • • • “Launching Fabric Manager” on page 3-1 “Uninstalling the Fabric Manager Client” on page 3-4 “Understanding the Fabric Manager Layout” on page 3-6 “Customizing Fabric Manager” on page 3-18 Launching Fabric Manager This section describes how to launch the Fabric Manager client. Before launching the client, you must have already installed the Fabric Manager server, as described in Chapter 2, “Installation”.
PAGE 62
3 Launching Fabric Manager The Fabric Manager introduction window displays, as shown in Figure 3-1 on page 3-2. Figure 3-1 2. Fabric Manager Introductory Window Click the Launch Fabric Manager link. If the browser is not configured with the correct JRE version (JRE version 1.5), then Fabric Manager redirects you to a window from which you can download the correct version.
PAGE 63
Launching Fabric Manager Figure 3-2 4. 3 Customizing Shortcut Creation Type your user name and password in the login dialog, shown in Figure 3-3. 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 3-3 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.
PAGE 64
3 Uninstalling the Fabric Manager Client Figure 3-4 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 “Discovering a Fabric” on page 4-1 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.
PAGE 65
Uninstalling the Fabric Manager Client 3 To uninstall the Fabric Manager client 1. Launch the Java Control Panel. Windows: From the Start menu, click Settings > Control Panel > Java. Solaris and Linux: Launch the ControlPanel executable file.
PAGE 66
3 Understanding the Fabric Manager Layout Figure 3-6 Java Application Cache Viewer 5. Select Fabric Manager and click Remove Selected Application. 6. Click OK to close the Java windows.
PAGE 67
3 Understanding the Fabric Manager Layout Menu bar Scope Panel View Panel Task Panel Information Panel Figure 3-7 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.
PAGE 68
3 Understanding the Fabric Manager Layout In Figure 3-9, 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. Figure 3-8 View Panel, Fabric Selection The Display By drop-down menu provides four different identifiers you can use to view SAN elements (name, IP address, domain ID, or WWN).
PAGE 69
Understanding the Fabric Manager Layout 3 View Panel The View panel displays the topology of the selection in the Scope panel. In Figure 3-9, the Host-Storage View is selected in the Scope panel, and the View panel displays the monitored fabrics and attached devices. See Figure 3-7 and Figure 3-8 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.
PAGE 70
3 Understanding the Fabric Manager Layout Figure 3-10 Context Menu for the Fabric Element The View Panel has the following additional components, as shown in Figure 3-11: • View bread crumbs The navigation path that resulted in the currently displayed view. Each step in the path is a clickable link; you can click a link to quickly navigate to a previous view. • Server date and time The date and time (including the time zone) of the Fabric Manager server.
PAGE 71
Understanding the Fabric Manager Layout • 3 View toolbar Buttons that allow you to perform operations on the topology displayed in the View panel. These buttons are described in detail in Chapter 5, “Viewing Fabric Topologies”. You can also hover the mouse over any of the buttons to get a short description.
PAGE 72
3 Understanding the Fabric Manager Layout Task Panel The Task panel provides quick access to commonly performed tasks for the selected SAN element in the View panel. This is not a comprehensive list of tasks, but just the tasks that are used most often on the type of selected element. The task list changes depending on the type of element that is selected. For example, Figure 3-7 shows the Task panel when the entire SAN is selected (by clicking on the background of the View panel).
PAGE 73
Understanding the Fabric Manager Layout 3 The Information panel has Export, Copy, and Search options at the top of the tables. These options are not available if the table does not have any content. • • • Click Export to save the contents of the table to a tab-delimited file. Click Copy to copy the contents of the table in tab-delimited text format to a file. Click Search to search for a specific text string in the table.
PAGE 74
3 Understanding the Fabric Manager Layout Menu Bar The menu bar contains drop-down menus with commands for executing specific Fabric Manager tasks. Commands are dependent upon the element selected within the View panel. Not all commands apply to all elements. Unavailable commands appear grayed out in the menu bar. 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).
PAGE 75
Understanding the Fabric Manager Layout 3 Figure 3-17 Background Colors Indicating Status By default, persistently disabled ports are no color (transparent). For switches running Fabric OS v5.0.x or later, you can change this color using the following procedure. To change the default color of persistently disabled ports 1. Click Edit > Preferences in the Menu bar. The Preferences dialog box displays. 2. Expand User Specific and select General (see Figure 3-22 on page 3-20). 3.
PAGE 76
3 Understanding the Fabric Manager Layout Refreshing the Window Fabric Manager views are updated periodically, depending on your SAN size, as shown in Table 3-2. Table 3-2 Polling Rates per SAN Size Total Ports Managed Polling Rates PM and APM 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.
PAGE 77
Understanding the 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 button in the View panel The header in the Information panel displays the time of the last refresh. Click Refresh in the Information panel to refresh the visible table.
PAGE 78
3 Customizing Fabric Manager 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. Customizing Fabric Manager This section describes several ways to change the look and feel of Fabric Manager.
PAGE 79
Customizing Fabric Manager 3 To customize the contents displayed in a table 1. Right-click anywhere in the table header in the Information panel. A pop-up menu displays the available columns for the table, as shown in Figure 3-20. A check next to a column name indicates that the column is displayed in the table. 2. Check or uncheck a column name in the pop-up menu to display or hide it in the table. Figure 3-20 Hiding/Showing Table Columns To reorder the columns in a table 1.
PAGE 80
3 Customizing Fabric Manager Figure 3-21 Editing the Sort Order for Multiple Columns To customize the table font setting 1. Click Edit > Preferences in the Menu bar. The Preferences dialog displays. 2. Expand User Specific and click General (see Figure 3-22). Figure 3-22 General Preferences 3. Select the table font from the Font Name drop-down menu. The default font is “Courier New.” 4. Select the font size from the Font Size drop-down menu. The default size is 11. 5. Click OK.
PAGE 81
Customizing Fabric Manager 3 The filters can consist text fields and drop-down menus. In Figure 3-23, the Name is a text field, and the Type, State, and Status are drop-down menus. Figure 3-23 Filtering Elements in a Table 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.
PAGE 82
3 Customizing Fabric Manager 3. Check the Show “Detailed” table tooltips checkbox to display tool tips for the entire row in a table. Uncheck this box to display tool tips for only a single cell in the table. 4. Click OK. Resizing Panels You can adjust the size of the Fabric Manager panels (Scope panel, View panel, Tasks panel, and Information panel) by dragging the borders between the panels. You can hide or show panels by clicking the arrow in the panel header.
PAGE 83
Chapter Discovering and Customizing Fabrics 4 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.
PAGE 84
4 Discovering a Fabric Discovering a Single Fabric Use the following procedure to discover a single fabric. You need to provide the IP address of the seed switch for the fabric. If you do not know the exact IP address, see “Discovering Multiple Fabrics (Subnet Scan)” on page 4-3. To discover a fabric 1. Click Discovery > Discover Fabric in the Menu bar. The Fabric Discovery Login dialog box appears, as shown in Figure 4-1. Figure 4-1 2.
PAGE 85
Discovering a Fabric 4 Discovering Multiple Fabrics (Subnet Scan) You can use Fabric Manager to scan a subnet and discover fabrics. A subnet scan eliminates the need to know the exact address of a switch to discover a fabric. Fabric Manager lists the switches and fabrics that it finds during the subnet scan. You can then select which fabrics to discover. Note Switches might appear in your subnet scan even after you unplug the Ethernet cables of those switches. To run a subnet scan 1.
PAGE 86
4 Logging In to Multiple Switches Simultaneously 5. Click the checkboxes next to the fabrics you want to discover. Click Select All to select all of the fabrics in the list. 6. Click Discover Selected Fabrics. You are prompted to log in to the seed switch of each fabric you discover. 7. Click Close to close the Subnet Scan dialog. Figure 4-3 Subnet Scan Results Logging In to Multiple Switches Simultaneously You can use Fabric Manager to log in to multiple switches at the same time.
PAGE 87
Logging In to Multiple Switches Simultaneously 4 Note You cannot log in to Fabric OS v4.0 through v4.2 switches with the factory user account in Fabric Manager (although you can from the CLI or Web Tools). You must use an account with administrative privileges (such as admin) to gain access. To log in to multiple switches 1. Click Discovery > Switch Login from the Menu bar. The Switch Login window displays (see Figure 4-4). Figure 4-4 2.
PAGE 88
4 Monitoring Fabrics The success or failure of the login displays in the Status column of the Selected Switches table. The Messages column provides additional information if the login fails. The background of the status field changes colors to display its status: • Green indicates a successful login. The user ID and password are saved for performing administrative operations until the session is terminated.
PAGE 89
Changing the Seed Switch 4 To monitor already discovered fabrics 1. Click Discovery > Monitor Fabrics from the Menu bar. The Monitor Fabrics dialog appears, as shown in Figure 4-6. Figure 4-6 Monitor Fabrics Dialog 2. Select the fabrics you want to monitor from the left-hand side of the window and click the right arrow to move them to the right-hand side. 3. Click Start Monitoring.
PAGE 90
4 Changing the Seed Switch Note that if a fabric of switches running only Fabric OS v2.x or older is created due to segmentation, Fabric Manager continues to monitor that fabric, but if any switch with a higher Fabric OS version joins the fabric, you do not receive any prompts to change the seed switch. You can change the seed switch as long as the following conditions are met: • • • The new seed switch is HTTP-reachable from Fabric Manager.
PAGE 91
Deleting a Fabric from Fabric Manager Figure 4-7 2. 4 Change Seed Switch Dialog Select a switch to be the new seed switch from the Change Seed Switch dialog. 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 displays (as shown in Figure 4-1).
PAGE 92
4 Renaming Fabric Components Renaming Fabric Components You can rename the following SAN elements in Fabric Manager: • • • • • • Fabric Switch Port Switch Group Port Group Device Renaming a Fabric When you discover a fabric, Fabric Manager assigns a name to that fabric that matches the name of the switch that you used to discover the fabric. For example, to monitor a fabric that includes Switch_01, enter the IP address of Switch_01 in the Fabric Discovery Login dialog box to discover the fabric.
PAGE 93
Renaming Fabric Components 4 Switch names can be a maximum of 15 characters long. They must begin with an alpha character, but otherwise can consist of any combination of alphanumeric and underscore characters. To rename 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.
PAGE 94
4 Renaming Fabric Components Figure 4-8 Renaming a Device Port Importing Device Names The Device Name Import wizard allows you to easily rename device names by importing them. You can rename devices by: • • • Using Zone Aliases Importing Names from a .csv File Importing FDMI Host Names To import device names 1. Select Tasks > Device Sharing and Troubleshooting > Import Device Node/Port Names from the Menu bar. The Device Name Import wizard displays (see Figure 4-9 on page 4-13). 2.
PAGE 95
Renaming Fabric Components Figure 4-9 4 Device Name Import Wizard Using 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.
PAGE 96
4 Working With Switch and Port Groups 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. Importing 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.
PAGE 97
Working With Switch and Port Groups • • • • 4 “Editing a Switch Group” on page 4-18 “Creating Port Groups” on page 4-19 “Editing a Port Group” on page 4-20 “Deleting a Switch or Port Group” on page 4-20 Understanding the Groups View The right-hand panel displays details about the selected element in the left-hand panel. The information is displayed in an At-A-Glance view. Figure 4-10 shows two group At-A-Glance views in the right-hand panel of the Groups View.
PAGE 98
4 Working With Switch and Port Groups 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 mouse-over 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 4-1 shows the complete list of icons. Not all icons are available for all elements.
PAGE 99
Working With Switch and Port Groups Click this icon to create switch groups 4 Click this icon to create port groups Figure 4-11 Switch and Port Groups View 2. Select My SAN from the tree in the left-hand side of the window. 3. Click the switch group creation icon in the SwitchGroups panel to create switch groups. The Edit Switch Groups window appears, as shown in Figure 4-12. Figure 4-12 Edit Switch Groups Window 4.
PAGE 100
4 Working With Switch and Port Groups After you create a group, you can drag it to a new location in the hierarchy. 5. Click Create. The Create Group dialog box displays. 6. Type a name for your group in the Name field and click OK. The new switch group appears in the right-hand side of the Edit Switch Groups window. 7. Select the switch group that you created in the right-hand side of the Edit Switch Groups window. 8.
PAGE 101
Working With Switch and Port Groups 4 Creating Port Groups When you create port groups, it is better to create more port groups with fewer ports in each group than to create fewer port groups with a lot of ports in each group. The Fabric Manager client memory usage increases with the number of ports you have in a port group when you view that port group. To create a group of ports 1. Click Tasks > Groups > Manage Switch/Port Groups from the Menu bar. The Groups View displays (see Figure 4-11). 2.
PAGE 102
4 Working With Switch and Port Groups To add multiple ports at once, you can either press and hold the Ctrl key as you click additional ports or drag any node in the tree from the SAN Elements tab to the port group to populate the group quickly. To delete ports from the group, select the ports in the right-hand side of the window and click Delete. To rename the group, select the group and click Edit. 9. Click OK in the Edit Port Groups window when you are finished adding ports to your group.
PAGE 103
Chapter Viewing Fabric Topologies 5 The 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.
PAGE 104
5 Understanding the View Panel You can choose to identify the switches by name, IP address, WWN, or domain ID (see “Scope Panel” on page 3-7). In Figure 5-1 the switches are identified by IP address. The colors that appear as background headers provide a quick, visual status. See “Status Indicators” on page 3-14 for information. View Panel Toolbar Items The View panel includes application toolbar buttons (see Table 3-1 on page 3-11) as well as its own set of toolbar buttons, described in Table 5-1.
PAGE 105
Understanding the View Panel Figure 5-2 5 Fabric Legend, Three Tabs Viewing 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 5-3 shows the tool tip for a switch.
PAGE 106
5 Understanding the View Panel Selecting Items in the Topology You can use the select tool to click an item in the View panel. When you select an item, the item becomes highlighted and the Information panel displays detailed information about the item. For example, in Figure 5-1 switch 10.32.151.161 is selected. 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.
PAGE 107
Topology Views 5 Topology Views Fabric Manager displays three types of topography views: SAN View Displays all of the monitored fabrics in the database. Fabric View Displays the topology of a single fabric; its focus is on the switches and their interconnectivity. Host-Storage View Displays all of the monitored fabrics and their attached devices; its focus is on end-to-end connectivity. The Fabric View and Host-Storage View also allow you to display zone configurations.
PAGE 108
5 Topology Views Displaying Switch Interconnectivity In the Scope panel, click Fabric View from the View drop-down menu. The View panel displays how the switches in a fabric are interconnected, as shown in Figure 5-6. Select the fabric you want to display, along with the Admin Domain context. Select which elements you want to display or hide. Figure 5-6 Displaying Switch Interconnectivity in the Fabric View In the Scope panel, you can select which fabric to display from the Fabric drop-down menu.
PAGE 109
Topology Views 5 Displaying Attached Devices In the Scope panel, click Host-Storage View from the View drop-down menu. The View panel displays the fabrics and their connected devices, as shown in Figure 5-7. Using the Host-Storage View you can: • • • Visualize which storage devices are accessible by a particular host. Visualize which hosts are possible initiators to a particular storage device. See whether devices are routed to multiple fabrics (so you can check for redundancy).
PAGE 110
5 Topology Views Displaying Zone Configurations In the Fabric View and the Host-Storage View, you can select the Zone tab in the Scope panel to display a graphical representation of a selected zone. Figure 5-8 shows how you can visualize zones in the Host-Storage View. In the Scope panel, a single fabric is selected in the Fabric Scope section. The fabric is Admin Domain-aware, and AD0 is selected. In the tabbed section of the Scope panel, the Zone tab is selected.
PAGE 111
Viewing Link Information 5 Viewing Link Information The Fabric View displays interswitch links (ISLs) between switches and the Host-Storage View displays links from switches to devices. You can mouse over a link to display a summary tool-tip. You can also click a link to highlight it and display detailed information about that link in the Information panel. Figure 5-9 shows information about the ISL between two switches. In the View panel, the switches at either end of the link are circled.
PAGE 112
5 5-10 Viewing Link Information Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 113
Chapter Displaying Name Server Information 6 Fabric Manager launches Web Tools to display Name Server entries listed in the Simple Name Server database (see Figure 6-1). 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 6-1 Name Server View To display Name Server entries 1.
PAGE 114
6 6-2 Displaying Name Server Information Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 115
Chapter Monitoring Alerts and Events 7 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.
PAGE 116
7 Monitoring Alerts To view alerts for switch groups 1. Click Tasks > Groups > Manage Switch/Port Groups. The Groups view displays (see Figure 4-10 on page 4-15). 2. 3. 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.
PAGE 117
Monitoring Alerts 7 You can right-click any of the alerts in the Alerts tab and then click Show on Topology to display and highlight the item in the View Panel to which the alert applies (see Figure 7-2). Alert count Figure 7-2 Identifying Alerts Table 7-1 lists the types of alerts in Fabric Manager.
PAGE 118
7 Monitoring Alerts Table 7-1 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.
PAGE 119
Monitoring Alerts Table 7-1 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.
PAGE 120
7 Monitoring Alerts Table 7-1 Alert Types (Continued) Type of Alert Description Password expiration or Generated when a password expires or is about to expire, or when a user lockout account is locked out due to too many unsuccessful login attempts. Note the following characteristics: User authentication fails • If the password expiry warning period is reached, a switch-level warning alert is displayed.
PAGE 121
Monitoring Alerts 7 Filtering Alerts You can filter the alerts that are displayed in the Alerts tab according to the severity of the alert, whether the alert was acknowledged or resolved, and the source ID of the alert. To filter alerts 1. Select a fabric, switch, or the entire SAN in the View Panel, as described in “Monitoring Alerts” on page 7-1. You cannot filter the switch group alerts. 2. Click the Alerts tab in the Information Panel. 3.
PAGE 122
7 Monitoring Alerts Acknowledging Alerts The Acked column in the Alerts tab indicates whether an alert is acknowledged. When you acknowledge an alert, your user name is displayed in the Acked By column of the Alerts tab. This lets other Fabric Manager users on the same server know that you have already acknowledged the alert and are aware of the issue. Once an alert is acknowledged, it cannot be unacknowledged. You can acknowledge alerts regardless of switch role. To acknowledge alerts 1.
PAGE 123
Monitoring Alerts 7 Deleting Alerts Automatically You can configure Fabric Manager to automatically delete resolved alerts after a period of time. When you enable automatic alert deletion, you specify the time period after which resolved alerts are deleted. The options are 60, 90, or 120 days; the default is 90 days. For example, if you set the alert history period to 60 days, a resolved alert is deleted 60 days after the date on which it was resolved.
PAGE 124
7 Monitoring Alerts Figure 7-4 Alerts History Configuring Alert Display Options By default, unacknowledged and unresolved alert information is displayed in bold type in the Alerts tab, and all other alerts are displayed in normal type. Using the following procedure, you can change which type of alert information is displayed in bold type. To configure alert display options 1. Click Edit > Preferences. The Options dialog displays. 2. Expand Server specific and click Alert Display Options.
PAGE 125
Monitoring Fabric Events Figure 7-5 7 Alert Display Options Monitoring Fabric Events Fabric events are events generated by the Fabric OS. Fabric Manager displays these events in the Information panel. These events are not stored in the Fabric Manager database. Viewing Fabric Events You can monitor fabric and switch events from the Events tab in the Information panel. The Events tab allows you to filter events to include only the information you want, and export, copy, and print the table.
PAGE 126
7 Monitoring Fabric Events To view all 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. To view events for switch groups 1. Click Tasks > Groups > Manage Switch/Port Groups. The Groups view displays (see Figure 4-10 on page 4-15). 2. 3.
PAGE 127
Configuring Notification Parameters 7 To filter fabric events for switches and fabrics 1. Select a fabric, switch, or the entire SAN in the View Panel, as described in “Monitoring Fabric Events” on page 7-11. 2. Click the Events tab in the Information panel. 3. Select the filter options. You might need to resize the panel to display all of the filter options and buttons. 4. a. Select the number of events to display from the Number of events drop-down list. b.
PAGE 128
7 Configuring Notification Parameters • Mail Server Address The IP address or DNS name of the mail server • Change Management From-Address The email address that will appear in the email as the From: address • Call Home From-Address The email address that will appear in the email as the From: address 4. Select the format of the XML file for Call Home by clicking either the Format 1 (default) or Format 2 radio button. Fabric Manager provides two formats for the XML file.
PAGE 129
Chapter Using Performance Monitoring 8 The performance monitoring feature in Fabric Manager provides insight into how much traffic a particular port or device is generating on the fabric over a specific timeframe. It is also used to indicate the devices that are creating the most traffic and to identify the ports that are the most congested. Performance monitoring is enabled or disabled on an entire fabric, not on a switch or port basis.
PAGE 130
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 8-2 “End-to-End Monitoring” on page 8-2 “Granularity” on page 8-3 “Reports” on page 8-3 “Graphs” on page 8-4 “Templates” on page 8-4 Port Statistics The port statistics component within the performance monitoring feature in Fabric Manager allows you to see how much traffic a partic
PAGE 131
Performance Monitoring Components 8 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. For example, if you select a timeframe to be the past three days, the five-minute granularity level is not available. The options for granularity (for both Port Statistics and End-to-End Monitoring) are listed in Table 8-1.
PAGE 132
8 Performance Monitoring Components Graphs Fabric Manager allows you to create graphs of performance data (see Figure 8-1). There are no templates for Performance Monitor graphs; however, you can create custom graphs or edit existing for graphs. See the following sections for additional information: • • “Creating Custom Graphs” on page 8-11 “Editing Performance Monitor Graphs” on page 8-19 Each node represents a granularity data point. The intervals are based on the granularity level you selected.
PAGE 133
8 Enabling Performance Monitoring Table 8-2 Default Performance Monitoring Report Templates for Port Statistics Report Name Format Time Granularity Filter “Top N” of Ports (Aggregate Tx/Rx Traffic) over time T Display (HTML) Last 1 hour 5 minutes None “Top N” of Ports (Aggregate Tx/Rx Traffic) over time T Display (HTML) Last 30 minutes 5 minutes None “Top N” of Ports Receiving (Rx) traffic over time T Display (HTML) Last 1 hour 5 minutes None “Top N” of Ports Receiving (Rx) traffic ove
PAGE 134
8 Enabling Performance Monitoring To enable performance monitoring 1. Select the fabric in the View Panel and select Tasks > Performance Monitoring > Configuration from the Menu Bar. The Performance Monitoring Configuration dialog displays, as shown in Figure 8-2. Figure 8-2 Configuring Performance Monitoring 2. To collect end-to-end statistics, click On in the End-to-End Monitors section. To collect switch port transmit and receive data, click On in the Port Rx/Tx History section. 3. Click Save.
PAGE 135
Disabling Performance Monitoring 5. Click Close to return to the Performance Monitoring Configuration dialog (see Figure 8-2). 6. Optional: Select Refresh Monitors to reestablish the End-to-End monitor set at any time. 8 This option is useful when you do not want to wait for the monitor set to be updated (for example, after zoning changes have been made).
PAGE 136
8 Generating Custom Reports and Graphs Creating Custom Reports To generate custom performance monitor reports 1. Select the fabric in the View Panel and select Tasks > Performance Monitoring > Generate Custom Reports from the Menu Bar. The Generate Report dialog displays (see Figure 8-4). Figure 8-4 Generate Custom Report/Graph 2. Click Report. 3. Select one of the following report types from the Report Type drop-down list: For End-to-End monitoring reports...
PAGE 137
Generating Custom Reports and Graphs 4. 8 Select one of the following formats for the report from the Format Type drop-down list: • Display (HTML) Displays the report in HTML format. • 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. 5. Type the number (1 through 100) of results you want for the report in the Top N field. 6.
PAGE 138
8 Generating Custom Reports and Graphs Figure 8-5 9. Selecting Ports for a Custom Report Select the ports from the Available Switches list that you want to include in the report. Use the right-arrow to move them over; then click OK. The Generate Report dialog displays again (see Figure 8-4 on page 8-8). 10. Click Generate Report. If you selected Display HTML as the format type for your report (in step 4), the report is displayed (see Figure 8-6 on page 8-11).
PAGE 139
Generating Custom Reports and Graphs Figure 8-6 8 Custom Report in HTML Format If there is no information matching the report criteria you selected, a message displays “No Performance statistics records were found matching the specified search criteria.” Click OK in the information message to close it. If you selected an export option (see step 4), a Save File dialog displays. Navigate to the location you want to save the file to and click Save. 11. Optional: • • • Print the report.
PAGE 140
8 Generating Custom Reports and Graphs 3. Select one of the following report types from the Report Type drop-down list: For end-to-end monitoring reports... • • • “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...
PAGE 141
Creating and Using Report Templates 8 If there is no information matching the report criteria you selected, an information message is displayed stating “No Performance statistics records were found matching the specified search criteria.” Click OK in the information message to close it. Figure 8-7 9. Custom Performance Monitor Graph Optional: • • Save the graph. See “Saving Performance Monitor Reports or Graphs” on page 8-17. Edit the graph. See “Editing Performance Monitor Graphs” on page 8-19.
PAGE 142
8 Creating and Using Report Templates Creating Templates for Reports and Graphs To create a Performance Monitor report template 1. Select the fabric in the View Panel and select Tasks > Performance Monitoring > Generate from Template from the Menu Bar. The Generate From Template dialog displays (see Figure 8-8). Figure 8-8 2. Create or Generate Report from a Template Click Create New Template. The Generate Template dialog displays (see Figure 8-9).
PAGE 143
Creating and Using Report Templates Figure 8-9 8 Creating a Report or Graph Template 3. Click Report or Graph. 4. Select one of the following report or graph types from the Report Type drop-down list: For end-to-end monitoring reports... • • • “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... • • • 5.
PAGE 144
8 Creating and Using Report Templates 7. Click Last, type a number, and then select the time increment (Minutes, Hours, or Days). 8. Select the granularity (the time interval between samples) from the Granularity drop-down list. The available options are 5 minutes, 30 minutes, 2 hours, and 1 day. See “Granularity” on page 8-3 for information on how granularity is calculated. 9. For Port Statistics reports only (skip to step 10 for End-to-End monitoring reports).
PAGE 145
Saving Performance Monitor Reports or Graphs 8 To generate a report or graph from a Performance Monitor template 1. Select the fabric in the View Panel and select Tasks > Performance Monitoring > Generate reports from Template from the Menu Bar. The Generate from Template dialog displays (see Figure 8-8 on page 8-14). 2. Select the template you want from the list; then click OK. The report or graph is generated and displayed. 3. Click Save in Database to save the report or graph.
PAGE 146
8 Exporting Reports Exporting Reports You can export Performance Monitor reports (not graphs) as HTML or XML files and open them in external applications. To export Performance Monitor reports 1. Create a custom report or generate a report from a template as described in the following sections: • • “Creating Custom Reports” on page 8-8 “Generating Reports and Graphs from Templates” on page 8-16 The report is displayed. 2. Click Export as XML or Export as HTML to export the report.
PAGE 147
Deleting Reports and Graphs 2. Select the report or graph that you want to display or do one of the following: • • • 3. 8 Click All to display all saved end-to-end and port statistics reports. Click Ports to display all saved port statistics reports. Click E-E (End-to-End) to display all saved end-to-end reports. Click View. The report or graph is displayed. Deleting Reports and Graphs To delete a performance monitor report or graph 1.
PAGE 148
8 Displaying Performance Monitor Reports in External Applications To display information about selected ports only 1. Create a performance monitor graph. See “Creating Custom Graphs” on page 8-11. 2. Display the graph (see Figure 8-7 on page 8-13). A list of the ports that correspond to the graph are listed in the graph report. To display only a subset of the ports in the graph, you can filter them out. 3. A selected checkbox indicates information from that port is displayed in the graph.
PAGE 149
Chapter Change Management 9 The change management feature allows you to monitor changes in a fabric and generate Extensible Markup Language (XML) reports listing the changes. The change management feature is available to users with physical fabric access. To use the change management feature, you must set up profiles defining which elements to monitor, when to monitor them, and what to do when changes occur to those elements.
PAGE 150
9 Using Change Management Profiles You view and manage profiles using the Change Management dialog, shown in Figure 9-1. Figure 9-1 Change Management, Manage Profiles Tab Note that the Change Management dialog 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.
PAGE 151
Using Change Management Profiles Table 9-1 9 Change Management Profile Monitored Elements (Continued) Monitored Element Description Port Status • • • • • • • • Configured/Disabled • SCC and DCC policies added/removed/changed (in SFWC mode only) • • • CHAP user ID added/removed Security1 Switches ACL iSCSI Online/Offline Note: Down status is not reported.
PAGE 152
9 Using Change Management Profiles Creating a Profile You can create change management profiles after you have configured the notification parameters (see “Configuring Notification Parameters” on page 7-13). To create a change management profile 1. Click Tasks > Change Management > Manage CM profiles. The Change Management dialog displays with the Manage Profile tab selected (see Figure 9-1). Any existing profiles are displayed in the dialog. 2. Click New Profile.
PAGE 153
Using Change Management Profiles 9 Cloning a Profile You can clone (duplicate) an existing change management profile if you need another similar profile and do not want to repeat all of the steps required to create a new one. For example, if you have another fabric that you want to run the same (or similar) checks on, you can clone an existing profile and make minor adjustments as needed. To clone a change management profile 1. Click Tasks > Change Management > Manage CM profiles.
PAGE 154
9 Using Snapshots and Change Reports Deleting a Profile When you delete a change management profile, all associated snapshots and change reports are also deleted from the database. To delete change management profiles 1. Click Tasks > Change Management > Manage CM profiles. The Change Management dialog displays with the Manage Profile tab selected (see Figure 9-1 on page 9-2). Any existing profiles are displayed in the dialog. 2.
PAGE 155
Using Snapshots and Change Reports 9 To compare a snapshot to the baseline configuration 1. Click Tasks > Change Management > View CM reports. The Change Management dialog displays with the View Change Reports and Snapshots tab selected (see Figure 9-3). Figure 9-3 2. Change Management, View Change Reports and Snapshots Tab Select the fabric containing the change reports you want. The Reports section displays a list of profiles and associated snapshots for that fabric. 3.
PAGE 156
9 Using Snapshots and Change Reports Figure 9-4 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 Use the following procedure to take a snapshot immediately. To create a snapshot on demand 1.
PAGE 157
Using Snapshots and Change Reports 2. 9 Select the fabric containing the change reports you want. The Reports section for that switch displays a list of profiles and associated snapshots for that fabric. 3. Select a snapshot report; then click Take Now (under the Snapshots area) to take a snapshot and display its change report. The Change Report is displayed as shown in Figure 9-4. Comparing Snapshots Use the following procedure to compare two snapshots.
PAGE 158
9 Using Snapshots and Change Reports Exporting Switch Configuration Information If the snapshot contains any switch configuration information, you can extract this information and export it to a file using the Export Switch Config button in the View Change Reports and Snapshots tab. To export switch configuration information 1. Click Tasks > Change Management > View CM reports. The Change Management dialog displays with the View Change Reports and Snapshots tab selected (see Figure 9-3 on page 9-7). 2.
PAGE 159
Using Snapshots and Change Reports 4. 9 Open the file using one of these methods: • Click Open the file with the following stylesheet applied The xslt file created by Fabric Manager is the default selected file. You can either use that file, or navigate to another style sheet of your own. Click OK to display the information in an Excel spreadsheet. • Click Open the file without applying a stylesheet (not recommended) The information is displayed in an Excel spreadsheet without any formatting.
PAGE 160
9 Using Snapshots and Change Reports 5. Click Yes in the confirmation window to proceed. A dialog 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, the click OK. No if you do not want to generate new change reports, the click OK. If you selected Yes or No, a confirmation displays indicating that the baseline has been change successfully.
PAGE 161
Chapter Call Home Support 10 This chapter describes the call home feature of Fabric Manager and contains the following information: • • • • • “About Call Home” on page 10-1 “Configuring Call Home” on page 10-3 “Editing Configurations” on page 10-4 “Enabling or Disabling Call Home Globally” on page 10-5 “Monitoring Call Home” on page 10-6 About Call Home When you enable the call home feature, Fabric Manager monitors the status of switches continuously and generates call home alerts whenever a call home
PAGE 162
10 About Call Home Call Home Email Messages You can configure call home to send an email message to a user-defined email address whenever a call home event is triggered for an unhealthy switch. The email message contains the details of the FTP server location where the supportShow or supportSave information is captured. The supportShow and supportSave commands run in the background.
PAGE 163
Configuring Call Home 10 Configuring Call Home Each call home configuration you create acts independently without impacting any other configuration. If you set up a call home configuration to send an email message, you need to also set up the notification parameters. See “Configuring Notification Parameters” on page 7-13 for instructions on setting the notification parameters for call home and change management.
PAGE 164
10 Editing Configurations Figure 10-2 Call Home Configuration Overview 3. Follow the instructions in the wizard to set up the call home configuration. The wizard is self-explanatory, so the individual steps are not described in this document. If the call home configuration is successful, you get a confirmation email. Editing Configurations You can edit a call home configuration at any time. Any change that you make applies immediately when you commit the change.
PAGE 165
Enabling or Disabling Call Home Globally 10 To add switches to an existing call home configuration 1. In the View panel, select the switches you want to add to a call home configuration. 2. Click Tasks > Call Home > Add switches to existing configuration. The Call Home dialog box displays, as shown in Figure 10-3. 3. Select the call home configuration to which you want to add the selected switches. 4. Click Add Switches.
PAGE 166
10 Monitoring Call Home Monitoring Call Home You can view the call home alerts using the Call Home Monitoring tool. To access this tool, select Tasks > Call Home > Call Home Alert History to open the window shown in Figure 10-4. Figure 10-4 Call Home Monitoring Window The Call Home Monitoring window displays details of the call home alerts triggered by Fabric Manager and also displays the status of call home email messages. The alerts are initially sorted by date, in descending order.
PAGE 167
Chapter Switch Configuration and Management 11 This chapter contains the following sections: • • • • • • • • • • • • • “Viewing Switch Information” on page 11-1 “Viewing Port Information” on page 11-4 “Synchronizing Date and Time Across a Fabric” on page 11-5 “Opening a Telnet Session for a Nonsecure Switch” on page 11-6 “Enabling/Disabling Switches and Ports” on page 11-6 “Configuring Ports” on page 11-7 “Swapping Ports” on page 11-8 “Administering ISL Trunking” on page 11-9 “Administering License Key
PAGE 168
11 Viewing Switch Information Figure 11-1 Displaying Switch Information The Switches tab in the Information panel displays detailed information about the switches.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 (see Figure 11-2). Note The Switches tab in the Information panel displays information about all of the switches in a fabric, even if you uncheck those switches in the Scope panel.
PAGE 169
Viewing Switch Information 11 To see the most detailed information about a switch, select a switch in the View panel and then refer to the various tabs in the Information panel. Note The Overview tab in the Information panel for a switch displays values for port-based routing, dynamic load sharing, and in order delivery. These values are displayed as “N/A” for XPath OS switches and for switches running Fabric OS versions earlier than v5.2.0.
PAGE 170
11 Viewing Port Information Viewing Port Information The Fabric Manager client provides several ways for you to view information about ports. The FC Ports and GigE Ports tabs in the Information panel display detailed information about the ports. 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 port in a single pop-up box (see Figure 11-3). The GigE Ports tab displays GigE ports only on Fabric OS switches.
PAGE 171
Synchronizing Date and Time Across a Fabric 11 To launch the FC Port Connectivity View 1. Select a switch. 2. Click Tasks > Switch Management > Show FC Port Connectivity View from the Menu bar. The FC Port Connectivity View displays.
PAGE 172
11 Opening a Telnet Session for a Nonsecure Switch The Time dialog displays (see Figure 11-5). Figure 11-5 Time Dialog 3. To adjust the time or date, click the applicable areas in the Time dialog (day-of-week, month, day, year, hour, minute, second, AM or PM) and use the up and down arrows to change the values; then click OK.
PAGE 173
Configuring Ports 11 To enable or disable elements 1. Log in to the switches necessary to disable or enable the elements. You cannot enable or disable a port or switch until you log in to that switch. If you are not logged in to the appropriate switches, Fabric Manager prompts you to do so before you can continue. 2. Right-click the switch, port, or switch/port group that you want to enable or disable and select Disable/Enable > Disable or Disable/Enable > Enable from the context menu.
PAGE 174
11 Swapping Ports Figure 11-6 Web Tools Port Management Module Swapping Ports 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.
PAGE 175
Administering ISL Trunking 11 To swap ports 1. Right-click a port to be swapped in the Information panel FC Ports tab and click Port Swap from the context menu. Web Tools launches and displays the Port Swap dialog in the Port Management module, as shown in Figure 11-7. See the Web Tools Administrator’s Guide for additional instructions.
PAGE 176
11 Administering License Keys For more information on the Trunking tab and performing these tasks, see the Web Tools Administrator’s Guide. To view and manage trunks, right-click a switch and choose Trunking Details from the context menu. Figure 11-8 Web Tools Trunking Tab Administering License Keys This section describes how to use Fabric Manager to administer the license keys that are required to use different Fabric OS features.
PAGE 177
Administering License Keys 11 To export license keys to a file 1. Click Tasks > Switch Management > Load from Switch. The License Admin -- Switch Selection window displays (see Figure 11-9). Figure 11-9 License Administration (Switch Selection) 2. Select the switches and fabrics from the SAN Elements tab that have license keys that you want to export to a file. 3. Click the right-arrow to move the selected elements to the right panel, then click OK.
PAGE 178
11 Administering License Keys Figure 11-11 Save Dialog 5. Optional: Check the WWN, Switch Name, and IP Address checkboxes 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. Importing and Restoring License Keys If you need to restore license keys to a switch, import them from the file where they were saved.
PAGE 179
Using Baseline Configurations for Configuration Management 2. 11 Navigate to your license key file (not displayed in Figure 11-12), select it, and click Open. The License Administration window displays with the File tab selected. Note You can print license information about switches from the License Administration window by clicking Print. 3. Select the licenses that you want to download and click Download to Switch. Fabric Manager loads the licenses to the selected switches.
PAGE 180
11 Using Baseline Configurations for Configuration Management Table 11-2 Baseline Sources Source Description Switch Compare multiple switches to one switch that you identify as a baseline. File • • • Save the configuration file of a switch as a file on an FTP server. Compare switches to the baseline configuration file. Propagate the baseline configuration file to switches. See Chapter 9, “Change Management” for information about automatic configuration file backups.
PAGE 181
Using Baseline Configurations for Configuration Management 11 To save a baseline configuration to a file 1. Ensure that file transfer properties between the switches and your host are configured. See “Configuring File Transfer Options” on page 14-9 for additional information. 2. Log in to the switch that has the configuration that you want to save as your baseline. See “Logging In to Multiple Switches Simultaneously” on page 4-4 for additional information. 3.
PAGE 182
11 Using Baseline Configurations for Configuration Management Figure 11-15 Save Baseline (Parameter Selection) 7. Click the checkboxes for each setting or group of settings of the configuration file that you want to save to the baseline. Expand and collapse the navigation tree to access your options. Note The Solaris environment does not display checkboxes clearly. If the checkbox displays full, the value is selected. If the checkbox displays shallow, it is not selected. 8. Click Save.
PAGE 183
Using Baseline Configurations for Configuration Management 11 Figure 11-16 Compare/Download from File 2. Navigate to the baseline file and click Open. The Compare/Download from File -- Target Switch Selection window opens. Note In a Solaris environment, ensure that you select a directory and not the actual file to compare the configuration against. 3.
PAGE 184
11 Using Baseline Configurations for Configuration Management Comparing Switches to a Baseline Switch This section provides information about comparing the configuration data of switches to a switch that you select to be the baseline switch. When you compare the configuration of a switch to a baseline switch, Fabric Manager identifies and lists each parameter that does not match.
PAGE 185
Using Baseline Configurations for Configuration Management 11 Downloading a Configuration You can download a configuration to a switch from a baseline file or from another switch. During the download process, you can choose the settings that you want to download and the settings that you want to omit. See “Saving a Baseline Configuration to a File” on page 11-14 for instructions on saving a baseline configuration file.
PAGE 186
11 Using Baseline Configurations for Configuration Management Figure 11-19 Apply Baseline Dialog The root navigation tree divides the switches into the following two groups: • Non-Reboot Configuration Group Any switches that do not need to reboot if the configuration file is downloaded. • Reboot Configuration Group Any switches that need to reboot if the configuration file is downloaded. Note The delay timer at the bottom of the Apply Baseline dialog cannot be configured from here.
PAGE 187
Using Baseline Configurations for Configuration Management 4. 11 From the SAN Elements tab, select the switches that you want to compare to the baseline file and click the right-arrow or drag the switches to move them to the right-hand window. You can use Ctrl-click or Shift-click to select multiple switches. 5. Click OK. 6. The Compare/Download from Switch -- Switch Configuration comparison and Download window displays and compares the configurations of the switches to the baseline.
PAGE 188
11 Using Baseline Configurations for Configuration Management To create a custom template, you must create an XML file and save it in the following directory on your Fabric Manager client: /Fabric Manager/
PAGE 189
Saving Switch Configuration Files 4. 11 Add or remove prefix tags to section tags to include or remove parameters from the Save Baseline - Parameter Selection dialog box. In each section, only include prefixes that appear in the analogous section in the configuration file. The prefix tag adds parameters to the template. Every parameter in the configuration file includes a prefix before the first dot (.).
PAGE 190
11 Saving Switch Configuration Files To save the switch configuration files 1. Select Tasks > Configuration Management > Save Config files from Switches. The Select a Folder window appears, as shown in Figure 11-22. Figure 11-22 Selecting a Folder to Save Your Switch Configuration Files 2. Browse to the folder where you want to save your switch configuration files and click OK. The Switch Selection window appears, as shown in Figure 11-23. Figure 11-23 Selecting the Switches 3.
PAGE 191
Checking the Physical Health of a Switch 11 Checking the 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. For the meaning of the colors, see the Status Legend available from the Help menu (Help > Status Legend). For example, in Figure 11-24, the View panel shows two switches with a yellow background, indicating Marginal status. The table in the Scope panel also shows a yellow background for those switches.
PAGE 192
11 Replacing a Switch in the Fabric Replacing a Switch 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. Caution If you replace the seed switch, all historical data in the database for the fabric containing the seed switch is lost. To replace a switch in the fabric (non-seed switch) 1. Physically remove the existing switch from the fabric.
PAGE 193
Chapter Configuring Standard Security Features 12 The chapter provides information about standard security features in Fabric Manager and contains the following sections: • • • • • • “Managing Passwords” on page 12-1 “Enabling Secure Communication Over HTTPS” on page 12-3 “Managing the Truststore” on page 12-3 “Managing Administrative Domains” on page 12-4 “Managing Access Control Lists” on page 12-6 “Propagating RADIUS Configuration Across Switches” on page 12-7 Managing Passwords This section descri
PAGE 194
12 Managing Passwords 3. Enable switch passwords to be saved to the server by checking the Persist switch passwords checkbox. Disable switch passwords from being saved to the server by unchecking the box. 4. Click OK. Changing Admin Password on Multiple Switches This section describes how you can set the password for accounts with the role of admin, which includes the default admin account as well as non-default user accounts that have the admin role.
PAGE 195
Enabling Secure Communication Over HTTPS 12 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. In addition, passwords must adhere to any additional conditions that you set up through Web Tools or the CLI. 4.
PAGE 196
12 Managing Administrative Domains The default truststore password is “password”. Fabric Manager provides a set of command line utilities to manage the truststore. You can use these utilities to import, export, delete, and print trusted certificates. You can also change the default trusted password. importcert Imports a certificate from a file and add it to the list of trusted certificates (truststore). exportcert Exports a certificate from the truststore to another file.
PAGE 197
Managing Administrative Domains 12 A fabric running Fabric OS 5.2.0 or higher with a valid zoning license is called an Admin Domaincapable fabric. To manage Admin Domains, you must be a physical fabric administrator. A physical fabric administrator is a user with the Admin role and access to all Admin Domains (AD0 through AD255). Launching the Admin Domain Module You can manage Admin Domains using the Admin Domain module of the Web Tools interface.
PAGE 198
12 Managing Access Control Lists Managing Access Control Lists For switches running Fabric OS v5.2.x and higher, 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.
PAGE 199
Propagating RADIUS Configuration Across Switches 12 Figure 12-2 Web Tools Switch Admin Module, ACL Management Tab Propagating RADIUS Configuration Across Switches Fabric OS supports RADIUS authentication, authorization, and accounting service (AAA). When configured for RADIUS, the switch becomes a Network Access Server (NAS) that acts as a RADIUS client. In this configuration, authentication records are stored in the RADIUS host server database.
PAGE 200
12 Propagating RADIUS Configuration Across Switches 2. Follow the instructions in the wizard to set up the call home configuration. The wizard is self-explanatory, so the individual steps are not described in this document. For additional help, click Help on the left-hand side of the window.
PAGE 201
Chapter Managing the iSCSI Target Gateway 13 The chapter provides information about iSCSI management in Fabric Manager and contains the following sections: • • • “About the iSCSI Target Gateway” on page 13-1 “Viewing iSCSI Information” on page 13-2 “Setting Up iSCSI Target Gateway Services” on page 13-7 About the iSCSI Target Gateway The Brocade iSCSI Target Gateway service provides the ability to leverage your shared Fibre Channel SAN resources with IP-based servers by using iSCSI links between your
PAGE 202
13 Viewing iSCSI Information iSCSI Host iSCSI Host IP Network SilkWorm 48000 with FC4-16IP Blade FC SAN Fibre Channel Target Fibre Channel Target Figure 13-1 iSCSI Target Gateway Connecting iSCSI Servers to FC Storage Viewing iSCSI Information The iSCSI tab in the Information panel displays detailed iSCSI information (see Figure 13-2). The iSCSI tab is available in the SAN, fabric, or switch context.
PAGE 203
Viewing iSCSI Information 13 iSCSI Summary The iSCSI Summary tab, shown in Figure 13-2, 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.
PAGE 204
13 Viewing iSCSI Information Figure 13-4 iSCSI Port Detail View iSCSI Initiators The iSCSI Initiators tab, shown in Figure 13-5, lists all iSCSI initiators in the SAN, fabric, or switch. You can filter the list based on initiator name (IQN) and initiator IP address. To view additional details about an initiator, right-click the initiator in the table and click View iSCSI Initiator Details in the context menu.
PAGE 205
Viewing iSCSI Information 13 iSCSI Targets The iSCSI Targets tab, shown in Figure 13-6, 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.
PAGE 206
13 Viewing iSCSI Information Figure 13-7 iSCSI Tab, Virtual Initiators View Exported FC Targets The Exported FC Targets tab, shown in Figure 13-8, lists details of FC targets that are exported as virtual targets. This tab is disabled when accessed in the switch context.
PAGE 207
Setting Up iSCSI Target Gateway Services 13 iSCSI Sessions The iSCSI Sessions tab, shown in Figure 13-9, 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 13-9 iSCSI Tab, iSCSI Sessions View Setting Up iSCSI Target Gateway Services To set up the iSCSI Target Gateway service, you use the Web Tools iSCSI Target Gateway Admin module.
PAGE 208
13 Setting Up iSCSI Target Gateway Services Figure 13-10 iSCSI Configuration Using Web Tools 13-8 Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 209
Chapter Firmware Management 14 This chapter provides information about using Fabric Manager to download firmware to multiple switches and host bus adapters (HBAs).
PAGE 210
14 Determining Availability of Firmware-Specific Features Table 14-1 Firmware-Specific Features (Continued) Feature Fabric OS XPath OS 5.2.x 5.1.x 5.0.x 4.4.x 4.2.x 4.1.x 4.0.x 3.1.x 3.0.x 2.6.x 7.3.x 7.1.
PAGE 211
Using Built-in FTP Server and Firmware Repository 14 7. If a fabric has a switch running firmware versions 2.6.x or earlier, 3.0 or earlier, or XPath OS v7.1.0, Change Management switch configuration checking is not supported. Fabric Manager uses one switch in the fabric to collect security policy information through the API. Fabric Manager cannot collect security policy information for a fabric if the switch it selects is running firmware versions 2.6.x or earlier, 3.0 or earlier, or XPath OS v7.1.
PAGE 212
14 Using 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 14-1 Firmware Repository Management Select a firmware version in the Repository pane to display its information. Click View to read the release notes associated with that particular firmware version.
PAGE 213
Using Built-in FTP Server and Firmware Repository 14 To import firmware into the repository 1. Select Tasks > Firmware Management > Firmware Repository Management. The Firmware Repository Management window appears. (See Figure 14-1 on page 14-4.) 2. To import firmware from a URL location, click Import from URL. To import from a folder on your local system, click Import from File. The Import Firmware dialog box appears. Figure 14-2 Importing From a URL or From a File 3.
PAGE 214
14 Using Built-in FTP Server and Firmware Repository Figure 14-3 Selecting Firmware Versions From a URL Location a. Select the firmware versions you want to import and click Import. b. Depending on where you are importing your firmware versions, you might be asked to enter your company information and to accept the license agreement. When the firmware has been successfully imported, it appears in the Firmware Versions tree in the Repository pane.
PAGE 215
Using Built-in FTP Server and Firmware Repository 14 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 14-4 Fabric Profile Management Window To create a fabric profile for downloading firmware 1. Select Tasks > Firmware Management > Manage Fabric Profile.
PAGE 216
14 Using Built-in FTP Server and Firmware Repository Figure 14-5 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. Viewing SAN Firmware Versions Use the SAN Firmware Information window to view firmware versions in switches across your SAN environment.
PAGE 217
Configuring File Transfer Options 14 Figure 14-6 Viewing Switch Firmware Information in Your SAN To view SAN firmware information 1. Choose Tasks > Firmware Management > SAN Firmware Information View. The SAN Firmware Information window appears, as shown in Figure 14-4 on page 14-7. 2. From the fabric tree, select the element whose switch information you want to view. 3. Optional: Click Print to print the firmware information.
PAGE 218
14 Configuring File Transfer Options Figure 14-7 Options (File Transfer) 3. Configure your FTP server. If you are using the FTP server built-in with Fabric Manager: a. Click the Use built-in FTP Server radio button. b. If you do not want to use the default user name and password, click the Use my user name and password radio button. i. Type your user name in the User Name field. ii. Type your password in the Password field and confirm it in the Confirm Password field.
PAGE 219
Downloading Firmware to Multiple Switches 4. 14 Click Test to ensure that you can access the FTP server specified. Fabric Manager reports success or failure. The test must be successful in order 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 the Test button writes a temporary file to the specified FTP directory. In order for the test to complete successfully: • • 5.
PAGE 220
14 Downloading Firmware to Multiple Switches • If your external FTP server resides on the same system as the Fabric Manager server, see “Downloading Firmware with Firmware Repository Support” on page 14-12. • If your external FTP server resides on the same system as the Fabric Manager server but the external FTP server user does not have root access, see “Downloading Firmware Using an External FTP Server” on page 14-13.
PAGE 221
Downloading Firmware to Multiple Switches 14 You can select the firmware version to download for each switch. The fabric profile determines the default setting in the drop-down menu. If you did not set up a fabric profile, the default setting is the most recent firmware version. A warning message appears if you try to download firmware that does not match a switch. To download firmware to multiple switches concurrently 1. Choose Tasks > Firmware Management > Firmware Download to switches.
PAGE 222
14 Downloading Firmware to Multiple Switches The Firmware Download to Switches window opens, as shown in Figure 14-9. Note that this window is different from the window that appears when you are downloading firmware with firmware repository support. Figure 14-9 Firmware Download Using External FTP Server 4. In the Host IP Address field, type the local host IP address of the firmware file. Note The file transfer options are not committed until you click Download (in step 9).
PAGE 223
Controlling Firmware Download Reboots 14 2.6.x/v2.6.2 3.x/v3.2.0_rc1 4.4.x/v4.4.0_rc1/release.plist 5.x/v5.2.x_rc1/release.plist 7. Select FTP from the Select Protocol drop-down menu. 8. From the SAN Elements tab, select the switches that you want to upgrade 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.
PAGE 224
14 Downloading Firmware to HBAs • • • Fabric OS v3.1.1 or later Fabric OS v4.1.0 or later Fabric OS v5.0.0 or later Fabric Manager supports only the Emulex HBA with the following drivers for the FDMI-based firmware downloads: • • • • Miniport Driver 5.20a8c-2g (Windows 2003 Server), Firmware 3.93A0 Miniport Driver 5-1.11A0 (Windows 2003 Server), Firmware 3.93A0 FCport Driver 5-2.40a2 (Windows 2003 Server), Firmware 1.91A1 Solaris driver for Sparc systems version 6.00g, Firmware 3.92A2 Note lpfc.
PAGE 225
Downloading Firmware to HBAs 14 Clicking Browse overrides the current settings for host IP address, user name, and password. The information defaults to the current host system from which the Fabric Manager application is executed. 6. In the Password field, type your password. Figure 14-10 Firmware Download to HBAs 7. From the SAN Elements tab, select the HBAs that you want to upgrade and either drag them to the Selected HBAs panel or click the right arrow.
PAGE 226
14 Downloading Firmware to XPath OS Switches 9. Click OK to proceed or Cancel to abort. Fabric Manager provides a report of successful and unsuccessful downloads. Downloading Firmware 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, .
PAGE 227
Collecting FDMI Device Information 14 Collecting FDMI Device Information 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.
PAGE 228
14 Rebooting Switches Creating a Reboot Group with Multiple Switches Create a reboot group containing more than one switch if you want the switches to reboot simultaneously. To create a reboot group 1. Click Tasks > Reboot > Create Reboot Sequence. The “Create or Change Reboot Groups and Sequence” window displays (see Figure 14-11). Figure 14-11 Create or Change Reboot Groups and Sequence 2. Select a fabric from the Select Fabric drop-down list. 3. Click Create.
PAGE 229
Rebooting Switches 6. 14 Optional: In the “What to do if timeout occurs?” field, click one of the following buttons: • • • Prompt: Provides a prompt whenever a timeout occurs that asks if you want to continue. Continue: Continues the reboot sequence when a timeout occurs. Abort: Terminates the reboot sequence when a timeout occurs. The default selection is Prompt. 7. In the Delay After Fabric Stabilization field, type the amount of time that must elapse before the next reboot in the sequence begins.
PAGE 230
14 Rebooting Switches Figure 14-13 Create Single Switch Reboot Groups 5. Optional: In the Reboot Group Name field, type a prefix for the reboot group name. 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.
PAGE 231
Rebooting Switches 14 To assign switches to an existing reboot group 1. Click Tasks > Reboot > Create Reboot Sequence. The Create or Change Reboot Groups and Sequence window displays (see Figure 14-11 on page 14-20). 2. Select a fabric from the Select Fabric drop-down list. The switches in that fabric display in the Unassigned Switches list. 3. Select the reboot group that you want to populate. 4. Select a switch that you want to add to the reboot group and click the left arrow.
PAGE 232
14 Rebooting Switches 3. Select a fabric from the Select Fabric drop-down list. 4. From within the Reboot Groups tab, click the reboot group that you want to reboot first; then click the right arrow to add it to the Selected Switches list. 5. Repeat step 4 to add additional groups in the sequence that you want to reboot. 6. Optional: To rearrange the order of the reboot sequence, click Create/Change Sequence.
PAGE 233
Chapter Managing Zones 15 Fabric Manager allows you to manage the zone database of a fabric directly or by using an offline copy of the live zone database. You can also use Web Tools to manage the live zone database but not the offline zone database. Note If you plan to add a switch to a fabric that uses zoning, first discover that switch with Fabric Manager and run a merge check between that switch and the fabric to which you plan to add it.
PAGE 234
15 Managing Zoning Offline Managing Zoning Offline 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.
PAGE 235
Managing Zoning Offline 15 The Zone Administration module displays the location of each zone database: either fabric (for the active zone database) or offline repository.
PAGE 236
15 Managing Zoning Offline • • Zone Admin Fabric Admin If you do not have one of these roles, you can launch the Zone Editor only in read-only mode. 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 databases are associated with an Admin Domain number and not an Admin Domain name in the Fabric Manager zone database repository.
PAGE 237
Managing Zoning Offline 15 Editing a Zone Database Offline This section describes how you can edit a zone database offline and either save the changes to an offline zone database or replace the zone database on the fabric. To edit a zone database offline 1. Click Tasks > Zone Management > Zone Administration from the menu bar. The Zone Administration module launches, as shown in Figure 15-1. 2. Select the zone database you want to edit from the table.
PAGE 238
15 Managing Zoning Offline 4. To save the zone database to the fabric without changing the effective zone configuration, click File > Save Zone Database > To the fabric without enabling and then click OK in the confirmation window. To save the zone database to the fabric and replace the effective zone configuration, click File > Save Zone Database > To the fabric with enabling and then click OK in the confirmation window. To save the zone database offline, continue with step 5. 5.
PAGE 239
Managing Zoning Offline 15 Copying a Zone Database from One Fabric to Another This section describes how you can copy a zone database from one fabric to another fabric or to a different Admin Domain in the same fabric. To copy a zone database 1. Click Tasks > Zone Management > Zone Administration from the menu bar. The Zone Administration module launches, as shown in Figure 15-1. 2. Select the zone database you want to copy. 3. Click View/Edit Zone DB.
PAGE 240
15 Managing Zoning Offline Figure 15-4 Compare/Merge Zone Database Module 2. Click 1. Choose Reference Zone Database. The Zone Administration dialog box opens. 3. Select the zone database to use as the reference zone database and click OK. You cannot update this zone database during the comparison. 4. Click 2. Choose Editable Zone Database. The Zone Administration dialog box opens. 5. Select the zone database that you want to compare to the reference zone database and click OK.
PAGE 241
Managing Zoning Offline 15 In the Comparison Options section, you can customize the display as follows: • You can click radio buttons to display the entire zone databases or only the differences between the two. • From the Tree Level drop-down menu, you can fully expand the trees by selecting All Levels, or expand the trees to the zone configuration or zone level by selecting Zone Configs or Zones, respectively.
PAGE 242
15 Managing Zoning Offline Figure 15-6 Storage-to-Host Connectivity View 7. Optional: Add or remove zones, aliases, and configurations from the editable zone database using the Add, Merge, and Remove buttons. You must be in the Traditional comparison view to modify the editable zone database. You cannot modify the zone database from the Host-to-Storage or Storage-to-Host Connectivity views.
PAGE 243
Managing Zoning Offline 15 Figure 15-7 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 the Save to Offline button and then click Save as. Populate the fields in the dialog box (shown in Figure 15-3) and click OK. Merging Two Zone Databases This section describes how you can merge two zone databases.
PAGE 244
15 Managing Zoning Offline 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. Figure 15-8 Merging Zones and Zone Configurations 7.
PAGE 245
Managing Zoning Offline 15 Exporting and Importing a Zone Database This section contains procedures for exporting the contents of a zone database from the Fabric Manager repository to local storage and for importing the zone database from local storage to the Fabric Manager repository. Exporting the zone database saves a copy of that zone database for backup purposes.
PAGE 246
15 Managing Zoning Offline Rolling Back Changes to the Zone Database on the Fabric If you have made modifications to the zone database that is on the fabric, saved those changes to an offline zone database, and then saved those changes to the fabric, you can later revert back to the version of the zone database that was on the fabric before you applied the changes.
PAGE 247
Managing Zoning Offline 15 Deleting a Zone Database from the Local Repository The following procedures describes how to delete a zone database from the local repository. 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. To delete a zone database from the local repository 1. Click Tasks > Zone Management > Zone Administration from the menu bar.
PAGE 248
15 Managing Zoning with Web Tools Managing Zoning with Web Tools You can monitor and manage zoning for a single fabric through the Web Tools Zone Admin module (see Figure 15-9). The information in the Zone Admin module is collected from the selected switch. A zoning license and administrative privileges are required to access the Zone Admin module within Web Tools. When you use the Web Tools Zone Admin module to update the zone database, any changes you make update the active zone database on the fabric.
PAGE 249
Managing Zoning with Web Tools 15 In the Zone Admin module, you can right-click the name of a device in the Member Selection list to launch the Device Detail view for that element. You can click the enabled configuration button (located in the top right corner of the Zone Admin module) to view the effective zoning configuration (a separate window opens). A live snapshot is taken of all the zoning configurations at the time you launch the Zone Admin module.
PAGE 250
15 15-18 Managing Zoning with Web Tools Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 251
Chapter Fabric Watch 16 Fabric Watch is an optional, licensed feature that monitors the performance and status of switches and can automatically alert you when problems arise. Fabric Watch tracks a variety of SAN fabric elements, events, and counters. For example, Fabric Watch monitors: • • Fabric resources, including fabric reconfigurations, zoning changes, and new logins. Switch environmental functions such as temperature, power supply, and fan status, along with security violations.
PAGE 252
16 Using Fabric Watch with Web Tools Using Fabric Watch with 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 16-1 Fabric Watch Module (with Alarm Notification Tab Displayed) You can administer Fabric Watch operations through the Fabric Watch module in Web Tools (see Figure 16-1). The Fabric Watch navigation tree, on the left side of the module, displays the available classes.
PAGE 253
Chapter Managing Secure Fabrics 17 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.
PAGE 254
17 Enabling Secure Mode To launch the Secure Fabric wizard to create a secure fabric 1. In the Information Panel, right-click the fabric for which you want to enable security and choose Security > Enable Secure Mode from the context menu. The Enable Secure Mode for Fabric wizard is launched (see Figure 17-1). Figure 17-1 Enable Secure Mode for Fabric Wizard 2. Follow the instructions in the wizard to enable secure mode for the fabric.
PAGE 255
Using the Policy Editor 17 Figure 17-2 Select Security Policy Settings (Optional) Using the Policy Editor The Policy Editor allows you to view and configure your security policy settings. When you launch the Policy Editor (shown in Figure 17-3 on page 17-4), 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.
PAGE 256
17 Using the Policy Editor Figure 17-3 Policy Editor (Summary Tab) Configuring FCS Policy Options Switches in your Fabric Configuration Server (FCS) policy serve as trusted switches. Use the following procedure to display these switches and to add, remove, or reorder switches in the policy. To configure/edit the FCS 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.
PAGE 257
Using the Policy Editor 17 Figure 17-4 Configuring the FCS Policy 3. Select a switch from the Available Switch List and click Add FCS to add the switch to the FCS Switch List, or click Add All to add all of the switches in the current fabric simultaneously. To add a switch that is not listed in the Available Switch List, click Add Others, and type the WWN of the switch you want to add. To remove a switch from the FCS policy, select the switch from the FCS Switch List, then click Remove FCS.
PAGE 258
17 Using the Policy Editor Configuring SCC Policy Options 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. To configure/edit the SCC policy 1.
PAGE 259
Using the Policy Editor 17 4. Click 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 displays. 6.
PAGE 260
17 Using the Policy Editor Figure 17-6 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. Caution 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 suddenly be unable to manage security and the switch.
PAGE 261
Using the Policy Editor 17 5. (Optional) Click Add FM Server IP to add the Fabric Manager server IP address, or click Add this FM Client IP to add the Fabric Manager client IP address. 6. 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. Click the Summary tab. 8.
PAGE 262
17 Using the Policy Editor Figure 17-7 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. The new name is displayed in the Policy menu within 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.
PAGE 263
Using the Policy Editor 17 To make 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 17-3 on page 17-4). 2. Click the DCC tab (see Figure 17-7 on page 17-10). 3. Perform any of the following actions for each DCC policy: • To remove a DCC policy, click Policy > Policy Name You want to delete and click Delete Policy.
PAGE 264
17 Using the Policy Editor The selected policy appears (see Figure 17-8). The SES policy is used in this example; the MS policy is similar. Figure 17-8 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.
PAGE 265
Using the Policy Editor 3. 17 Perform any of the following: • To add a device to the policy, select the device in the Available Access Points field, then click Add Device. • To remove a device from the policy, select the device in the Permitted Access Points field, then click Remove Device. 4. Click 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 displays. 6.
PAGE 266
17 Using the Policy Editor Figure 17-9 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. Caution 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 suddenly be unable to manage security and the switch. 4.
PAGE 267
Using the Policy Editor 17 To make 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 17-3 on page 17-4). 2. Click the tab that corresponds to the policy you want (Serial or Front Panel). The selected policy appears (see Figure 17-9 on page 17-14).
PAGE 268
17 Using the Policy Editor Figure 17-10 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. Passwords must be from 8 through 40 characters long and must differ from the old password by at least one character. In addition, passwords must adhere to any additional conditions that you set up through Web Tools or the command line interface. 5.
PAGE 269
Adding a Switch to a Secure Fabric 17 Configuring No-Node WWN Zoning 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. To configure No-Node WWN Zoning 1.
PAGE 270
17 Merging Secure Fabrics Merging Secure Fabrics Fabric Manager provides a wizard to help you merge secure fabrics that are not physically connected. This wizard performs a compatibility check that identifies noncompatible 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.
PAGE 271
Using Telnet on a Secure Fabric 3. 17 Follow the instructions in the wizard to merge the secondary fabric with another (primary) secure fabric. The wizard is self-explanatory, so the individual steps are not described in this document. 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 via the CLI.
PAGE 272
17 17-20 Using Telnet on a Secure Fabric Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 273
Chapter FICON and CUP 18 FICON is a protocol used between IBM (and compatible) mainframes and storage. FICON is supported on switches running Fabric OS v4.1.2 and later. FICON Control Unit Port (CUP) is a protocol for managing FICON directors. CUP is used by IBM mainframe management applications to provide in-band management for ESCON and FICON. CUP is an optional, license-based feature and is supported on switches running Fabric OS v4.4.0 or later.
PAGE 274
18 Editing the Current Port Connectivity Configuration The following procedure describes how to identify which switches have FMS mode enabled. To identify switches with FMS mode enabled 1. Select a switch from the View panel. 2. Click the Overview tab in the Information panel. 3. Scroll or use the Search function to locate “FMS Mode” in the Property column.
PAGE 275
Editing the Current Port Connectivity Configuration 18 Some cells for the SilkWorm 24000 and 48000 switches are disabled. • For SilkWorm 24000 switches, disabled cells are those with 7E in the Area ID column or 10/14 in the Port column. • For SilkWorm 48000 switches, disabled cells are those with FE or FF in the Area ID column or 10/30 in the Port column. Figure 18-1 Editing the Port Connectivity Configuration 2.
PAGE 276
18 Editing a Stored Port Connectivity Configuration • Modify port names • To add or change the port name, click the Port Name field and type the name. To clear all of the port names, click the Clear All Port Names checkbox. Analyze zone conflicts Click Analyze Zone Conflicts to see if there are any problems between the PDCM and the currently enabled zone configuration. Any port connections that cannot communicate with each other due to a zone conflict are displayed with a red background.
PAGE 277
Editing a Stored Port Connectivity Configuration 18 Note You can activate a stored port connectivity configuration only for FMS-enabled switches running Fabric OS v4.4.0 or later. Users with roles of user or basicswitchadmin can only view the port connectivity configuration. Users with the role of zoneadmin cannot access the port connectivity configuration. All other user roles can view and modify the port connectivity configuration. To view and edit a stored port connectivity configuration 1.
PAGE 278
18 Identifying Port Zone Conflicts Identifying Port Zone Conflicts Fabric Manager identifies ports that cannot communicate with each other due to zone conflicts. Zone conflicts are identified as: • Port zone configurations: If two ports are not defined in the same zone, they cannot communicate with each other. Fabric Manager can analyze port communication conflicts based on only on zones defined by port name (not WWN).
PAGE 279
Configuring Insistent Domain ID Mode 18 Figure 18-3 Information Panel Showing IDID Mode To configure IDID mode on a switch 1. Right-click a switch and select Insistent Domain ID(IDID) from the context menu. Note that this menu item is available only for switches running Fabric OS 5.0.x or higher. A confirmation dialog warns you that the switch will be disabled and asks if you want to continue. 2. Click Yes in the confirmation dialog.
PAGE 280
18 Identifying Ports That Completed the RNID Exchange Figure 18-4 Web Tools Switch Admin Module, Configure Tab Identifying Ports That Completed the RNID Exchange The following procedure describes how to identify ports that have completed the request node identification (RNID) exchange. To identify ports that have completed the RNID exchange 1. Launch the FC Port Connectivity View, as described in “Viewing Port Information” on page 11-4, or access the FC Devices tab in the Information panel. 2.
PAGE 281
Monitoring Link Incidents 18 Monitoring 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 18-1 describes the types of link and implicit link incidents.
PAGE 282
18 Cascaded FICON Setup • • 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. (Optional) Turns on FICON Management Server (FMS) mode on all switches. If some switches already have FMS mode enabled, it is reenabled.
PAGE 283
Cascaded FICON Setup 18 3. (Optional) Check the Turn ON FMS Mode checkbox if you want FMS mode to be set on all of the switches in the selected fabric. 4. Click OK. Fabric Manager starts configuring the fabric for cascaded FICON. If Fabric Manager cannot add the SCC policy to the fabric-wide consistency policy (because the accept distribution parameter for the SCC policy is set to No), a message displays, informing you that HIFC cannot be set on the switches.
PAGE 284
18 Cascaded FICON Setup Note It is recommended that you do a configuration backup on all switches before performing the fabric merge. This helps you to revert back the switch configurations later. To merge two fabrics for cascaded FICON 1. Click Tasks > Cascaded FICON Setup > Merge two fabrics for cascaded FICON setup. The Merge wizard shown in Figure 18-6 on page 18-12 displays. At least two of the discovered fabrics must meet the requirement that all switches must be running Fabric OS v5.2.
PAGE 285
Chapter Managing the FC-FC Routing Service 19 The FC-FC Routing Service provides Fibre Channel routing between two or more fabrics without merging those fabrics.
PAGE 286
19 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.
PAGE 287
Setting Up FC-FC Routing 19 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 19-1 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 The following procedure provides the basic steps for setting up FC-FC Routing using a Fibre Channel router (FC Router). 1.
PAGE 288
19 Connecting Edge Fabrics Connecting 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.
PAGE 289
Diagnosing Fabric Device Sharing 19 Diagnosing Fabric Device Sharing 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.
PAGE 290
19 Sharing Devices Between Fabrics Figure 19-4 Summary Screen 3. Optional: Click Print to print the summary. 4. Click Finish to exit the wizard. Sharing Devices Between Fabrics You can share devices between fabrics without merging them using an FC Router (see Figure 19-1 on page 19-3). Fabric Manager allows you to set up the shared devices easily with the Share Devices wizard.
PAGE 291
Sharing Devices Between Fabrics 19 Figure 19-5 Share Devices Wizard 2. Read the overview information, then click Next. The Select Devices to Share screen displays (see Figure 19-6). Note that the wizard does not display AD-enabled fabrics or iSCSI devices (Virtual Initiators and Virtual Targets). Figure 19-6 Selecting Devices to Share 3. Type a name for the logical SAN (LSAN). The name is automatically prefixed with LSAN_.
PAGE 292
19 Displaying Logical SANs 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 .
PAGE 293
Displaying FC Router Information 19 Figure 19-7 LSAN View Displaying FC Router Information The FCR Info View (see Figure 19-8) displays information about FC Routers. This view is available only for backbone fabrics containing FC Routers. This view is not available for AD-enabled fabrics.
PAGE 294
19 Displaying FC Router Information • Physical Devices This tab displays all the devices shared from the edge fabrics connected to the selected FC Router through EX_Ports. The devices displayed here are only those devices that are physical to the edge fabrics connected to the FC Router. Using Figure 19-9 on page 19-10 as an example, the Physical Devices tab would show Host 1 on Edge Fabric 1 for FC Router 1, and would show Target 2 on Edge Fabric 2 for FC Router 2.
PAGE 295
Translate Domains and Virtual Device Status 19 Note When you access the FCR Info View for a single FC Router, the information displayed in the Physical and Virtual Devices tabs varies from what is displayed in the CLI commands. For example, the fcrproxydevshow command provides information on the devices that are proxy to the edge fabrics connected to the FC Router.
PAGE 296
19 FC-FC Routing and Secure Fabrics FC-FC Routing and Secure Fabrics The following limitations apply to FC-FC routing and secure fabrics: • • Fabric Manager does not support FC Router configuration for secure edge fabrics. • The Share Devices wizard and the Diagnose Fabric Device Sharing wizard do not list secure fabrics. • • • The FCR Info View is not supported for secure backbone fabrics.
PAGE 297
Chapter Using the FCIP Tunneling Service 20 This chapter describes the Fibre Channel over IP (FCIP) Tunneling Service. It contains the following topics: • • • “About FCIP Tunneling” on page 20-1 “Viewing FCIP Information” on page 20-2 “Configuring an FCIP Tunnel” on page 20-3 About FCIP Tunneling The optional FCIP Tunneling Service enables you to use “tunnels” to connect Fibre Channel SANs over IP-based networks.
PAGE 298
20 Viewing FCIP Information Fibre Channel initiator Fibre Channel initiator Office FC SAN Data Center FC SAN IP WAN Network VE_Port VE_Port SilkWorm 7500 SilkWorm 7500 VE_Port SilkWorm 48000 with FR4-18i Blade VE_Port Office FC SAN Office FC SAN Fibre Channel Target SilkWorm 48000 with FR4-18i Blade Fibre Channel Target 31.
PAGE 299
Configuring an FCIP Tunnel 20 Figure 20-2 Information Panel for Physical Gbe Ports The FC Ports tab in the Information panel displays information about all of the ports, including the logical ports for the GbE ports (see Figure 20-3). Logical ports for GbE ports are designated here. Figure 20-3 Information Panel for Logical GbE Ports Configuring an FCIP Tunnel To enable an FCIP interswitch link (ISL), you must configure both the local and remote switches using the Web Tools Port Management module.
PAGE 300
20 Configuring an FCIP Tunnel See the Web Tools Administrator’s Guide for additional information about managing the FCIP Tunneling Service. To configure an FCIP tunnel 1. Right-click a logical port on the local switch in the Information panel and select Port Configuration from the context menu. Logical ports are numbered from 16 through 31 on the SilkWorm 7500 and on the FR4-18i blade of the SilkWorm 48000. The Web Tools Port Management module launches. 20-4 2.
PAGE 301
Chapter Third-Party and Foreign Device Management 21 The chapter provides information about managing third-party application and importing foreign devices in Fabric Manager and contains the following sections: • • “Accessing Third-Party Management Applications” on page 21-1 “Importing Device WWNs” on page 21-7 Accessing Third-Party Management Applications Right-clicking a fabric or switch displays a Management Application option that lets you launch or configure third-party management applications.
PAGE 302
21 Accessing Third-Party Management Applications Adding 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. To add third-party applications to the list 1. In the Information Panel, right-click the fabric or switch to which you want the application associated and choose Management Application > Configure from the context menu.
PAGE 303
Accessing Third-Party Management Applications c. 21 Optional: Type the arguments to the application, separating each argument with a space, or click Edit to select the arguments. Figure 21-4 Selecting Application Arguments Arguments vary, depending on whether you select a fabric or switch. 5. If your application is located on the Internet, select the URL checkbox and then type the URL to the application. 6. Click OK. 7. Click Apply to close the Configure Application window.
PAGE 304
21 Accessing Third-Party Management Applications Editing Third-Party Management Applications After a third-party management application has been added, you can later edit it: for example, to change its arguments, name, or location.
PAGE 305
Accessing Third-Party Management Applications 3. In the Application Name edit box, type gping. 4. Click the Executable radio button. 5. Click Browse to locate the gping executable and click Open. 21 gping requires an IP address as an argument. This example uses the IP address of the switch. 6. Click Edit, select %IP%, and click OK. Your Add Application window should look similar to Figure 21-5. Figure 21-5 Configure gping 7. Click OK. 8.
PAGE 306
21 Accessing Third-Party Management Applications To launch Web Tools Switch Explorer 1. In the Information Panel, right-click the switch from which you want to run Switch Explorer and choose Management Application > Configure. The Configure Applications for Switch window appears (Figure 21-2 on page 21-2). 2. Click Add. The Add Application window appears (Figure 21-3 on page 21-2). 3. In the Application Name edit box, type WebTools SwitchExplorer. 4. Click the URL radio button. 5.
PAGE 307
Importing Device WWNs 21 Figure 21-8 Web Tools Switch Explorer Importing Device WWNs 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 LSAN in the Brocade fabrics that are being managed from Fabric Manager.
PAGE 308
21 Importing Device WWNs When an LSAN is removed from Fabric Manager, the output is similar to: "Delete LSAN_Test1 from the active configuration." To import foreign fabrics 1. Create the .csv file containing the foreign fabric information. Use the following example as the .csv format: Type,Port Id,Port Name,Node Name,COS,FC4 Types, FL,610FEF,21:00:00:20:37:C3:2C:76,20:00:00:20:37:C3:2C:76,3,2, 2. Choose Tasks > Device Sharing and Troubleshooting > Share Devices. 3.
PAGE 309
Importing Device WWNs 21 Figure 21-10 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) window. 9. Click Next in the wizard. 10. Read the summary. The summary displays which devices are being shared in the new LSAN. The summary also displays the LSAN you must create in the foreign fabric and the WWNs of the members that belong to that LSAN.
PAGE 310
21 21-10 Importing Device WWNs Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 311
Chapter Creating Reports 22 Displaying the Switch Health Report Fabric Manager creates a switch health report that is Web-based. The report displays the switch state contributors, the status, and the IP address of the switch. Note that this is a static report and not a dynamic view of the switch. See the Web Tools Administrator’s Guide for additional information. The switch health report is available only for switches running the following firmware versions: • • • Fabric OS v3.2.
PAGE 312
22 Displaying the Switch Health Report Figure 22-1 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.
PAGE 313
Displaying the Switch Health Report 22 Figure 22-2 Switch Report Action Menu Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP 22-3
PAGE 314
22 22-4 Displaying the Switch Health Report Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 315
Chapter Storing Data and Performing Backups 23 This chapter contains the following sections: • • “Data Persistence” on page 23-1 “Performing Backups” on page 23-1 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. After the server authenticates the client, Fabric Manager launches and polls switches.
PAGE 316
23 Performing Backups Full Backup To perform a full backup, enter the following command in the CLI (the entire command is on a single line): dbbackup -c "uid=dba;pwd=sql;eng=fabman;CommLinks=tcpip{DOBROADCAST=DIRECT;HOST=localh ost;ServerPort=2638}" -y -r -n where: • is the destination directory for the backup files. • -y is an option that causes the dbbackup utility to overwrite files without any prompt.
PAGE 317
Performing Backups 23 Incremental Backup To perform an incremental backup, enter the following command in the CLI (the entire command is on a single line): dbbackup -c "uid=dba;pwd=sql;eng=fabman;CommLinks=tcpip{DOBROADCAST=DIRECT;HOST=localh ost;ServerPort=2638}" -y -r -n -t where: • is the destination directory for the backup files. • -y is an option that causes the dbbackup utility to overwrite files without any prompt.
PAGE 318
23 23-4 Performing Backups Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 319
Chapter Server Management Console 24 This chapter contains the following topics: • • • • • • • • • “Introduction to Server Management Console” on page 24-1 “Launching the Server Management Console” on page 24-2 “Managing Fabric Manager Services” on page 24-2 “Changing Authentication Information” on page 24-3 “Backing Up and Restoring the Database” on page 24-5 “Capturing Technical Support Information” on page 24-6 “Creating a Login Banner” on page 24-7 “Changing Secure Communication Settings (HTTP or H
PAGE 320
24 Launching the Server Management Console Figure 24-1 Server Management Console, Services Tab Launching the Server Management Console The Server Management Console is available only to users who have root access on UNIX systems and users who have write privilege to the Fabric Manager installation directory on Windows systems. It is available only on hosts where the Fabric Manager Server is installed.
PAGE 321
Changing Authentication Information 24 Stopping and restarting the Fabric Manager services causes clients connected to the server to lose connection, and they must re-log in to the server. The screen does not automatically refresh; you must click Refresh Status every time you want to refresh the screen. To monitor and manage Fabric Manager Services 1. Launch the Server Management Console. 2. Click the Services tab.
PAGE 322
24 Changing Authentication Information All responses by the Fabric Manager server for authentication requests coming from Fabric Manager clients are logged to an audit trail log file. This file is automatically backed up on the first day of every month. Click Authentication Audit Trail to display the log file messages from the current month and the previous month. To change authentication information 1. Launch the Server Management Console. 2. Click the Authentication tab. 3. Click Edit.
PAGE 323
Backing Up and Restoring the Database 24 Backing Up and Restoring the Database The Database tab of the Server Management Console allows you to backup and restore the Fabric Manager database (fabmandb). The Database Server must be running when you backup 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.
PAGE 324
24 Capturing Technical Support Information To restore the database 1. Launch the Server Management Console. 2. Click the Database tab. 3. Click Restore Database. The Database Restore window displays. 4. Click Browse to select the path to the database. 5. Click Restore. Upon completion, a window displays the status of the restore operation. 6. Click OK to close the window.
PAGE 325
Creating a Login Banner 24 To capture supportShow information 1. Launch the Server Management Console. 2. Click the SupportShow tab. 3. Click Browse to select the path where the supportShow data will be saved. 4. Click Capture Technical Support Information. The Server Management Console displays the following confirmation message when the capture is complete: Creating a Login Banner You can configure a login banner that displays after you successfully log in to Fabric Manager (see Figure 24-6).
PAGE 326
24 Changing Secure Communication Settings (HTTP or HTTPS) Figure 24-7 Server Management Console, BannerMessage Tab To create or edit the login banner 1. Launch the Server Management Console. 2. Click the BannerMessage tab. 3. 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). 4. Click Submit.
PAGE 327
Changing Secure Communication Settings (HTTP or HTTPS) 24 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. These operations include FICON/CUP features (including PDCM matrix) and switch and port control operations (such as enable, disable, and reboot).
PAGE 328
24 Changing the Web Server Port Number 5. Optional: If you selected Connect using HTTPS, check or uncheck the following options. By default, both options are checked. • 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.
PAGE 329
Changing the Web Server Port Number 3. 24 Type a new port number in the Web Server port field. Do not use port 2638, and do not use the nine consecutive port numbers that were reserved for Fabric Manager during server installation. These ports are reserved for Fabric Manager to use internally. 4. Click Apply to save the changes. You must restart the server for the change to take effect.
PAGE 330
24 24-12 Changing the Web Server Port Number Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 331
Chapter Fabric Troubleshooting Tools 25 This chapter describes the following troubleshooting tools that are provided with Fabric Manager: • • • • “General Device Diagnostics” on page 25-1 “Fabric Merge Check” on page 25-2 “Event Message Severity Level” on page 25-4 “Trace Route” on page 25-5 General Device Diagnostics A device diagnostic wizard is available to check communication problems that might arise between devices in the same fabric, or devices shared through FC Routers.
PAGE 332
25 Fabric Merge Check To use the device diagnostic wizard 1. Select Tasks > Device Sharing and Troubleshooting > Device Connectivity Troubleshooting (GDD). The Device Connectivity Troubleshooting wizard appears, as shown in Figure 25-1. 2. Follow the instructions in the wizard to set up the profile. The wizard is self-explanatory, so the individual steps are not described in this document.
PAGE 333
Fabric Merge Check 25 Note If a test is not applicable to the fabric, the test is not executed and Fabric Manager displays the message, “Test not applicable to subject fabrics.” For example, if one or more fabrics are secure, the management server platform test and the zoning test are not executed and the message is displayed. Table 25-1 Fabric Merge Check Tests Component Tests All Fabrics • • • • • • • Domain IDs • ACL 1.
PAGE 334
25 Event Message Severity Level 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 25-3 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.
PAGE 335
Trace Route 25 The Log Parameters dialog displays (see Figure 25-4). Figure 25-4 Setting the Log Parameters 3. Select one of the following severity levels from the Log Level drop-down list. The hierarchy, from most severe to least is: Fatal, Error, Warning, Info, and Debug. Fabric Manager logs all events of the selected severity level and lower. Selecting Off disables the logger. 4. Click OK.
PAGE 336
25 Trace Route To capture the trace route information 1. Select Tasks > Technical Support Information > Trace Route. The Trace Route dialog displays, as shown in Figure 25-5. Figure 25-5 Trace Route Dialog 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.
PAGE 337
Trace Route 3. 25 Click Trace Route. The trace route information displays in a summary window, shown in Figure 25-6. Click the tabs to display the forward route, reverse route, and fcping information. 4. Optional: Click Copy to clipboard to copy the information to the clipboard from which you can then paste it into another application. The information from all three tabs is copied. 5. Click Close to exit the summary window. 6. Click Close to exit the Trace Route dialog.
PAGE 338
25 25-8 Trace Route Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 339
Chapter Troubleshooting 26 This chapter describes problem scenarios that can occur while using Fabric Manager and provides troubleshooting tips to help you resolve these problems.
PAGE 340
26 Capturing Fabric Manager Support Information Windows: \Fabric Manager\\client\fmclientsupportshow.bat For example: C:\Documents and Settings\Admin\Fabric Manager\127.0.0.1\client\fmclientsupportshow.bat Solaris and Linux: /Fabric Manager//client/fmclientsupportshow.sh For example: /user/admin/Fabric Manager/127.0.0.1/client/fmclientsupportshow.sh See page 26-3 for an example of the fmsupportshow output for Solaris. 3.
PAGE 341
Checking the Client Side 26 Client-related information is copied to the client directory, and server-related information is copied to the server directory. For example, in Figure 26-1, the files are located at: • • C:\FabricManager\support\Wed-10-11-2006-15-39-18\client C:\FabricManager\support\Wed-10-11-2006-15-39-18\server\db Solaris and Linux: Following is an example for fmSupportShow output in Solaris. The output for Linux is similar. Example fmgr007006:/test/fm5.2/FabricManager/bin# .
PAGE 342
26 Checking the Client Side • Fabric Manager server running under Solaris or Linux when using NIS authentication: NIS yourdomain.
PAGE 343
Checking Client/Server Interaction 26 This happens only on Windows installations, when the Windows domain authentication method is the authentication method when the server starts up. If the RADIUS, NIS, local password, switch-based, or any other authentication method is in effect when the server starts up, there is no restriction on switching the authentication type.
PAGE 344
26 Checking Client/Server Interaction No Client/Server Interaction If the client cannot talk to the server, follow these steps: 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. If a firewall is present, ensure that the proper ports are opened.
PAGE 345
Checking the Server Side 26 Checking the Server Side If you suspect the problem is related to the server, check the following areas: • • • “Server Cannot Access Switches” on page 26-7 “Server-Side CPU Usage” on page 26-7 “Statistics Not Collected” on page 26-7 If the problem persists or cannot be resolved, see “Capturing/Reporting Server-Side Issues” on page 26-7. Server Cannot Access Switches If the server cannot access any switches, follow these steps: 1.
PAGE 346
26 Checking Fabric Discovery Problems Checking Fabric Discovery Problems If you are having fabric discovery problems, identify the problem (see below) and try the recommended solution: • Switch does not exist or there is no Ethernet path to the switch. Attempt to ping the switch from both the client and the server. • IP address is not properly formed. Fix the IP address and/or URL of the switch. • Seed switch name is unknown to the DNS. Check the DNS configuration.
PAGE 347
Capturing supportShow and supportSave Output 26 The output files are saved on the FTP server. The wizard displays the name and location of the file. If you are using the built-in FTP server, the output files are saved in the following directory: \server\server\fmserver\ftproot\technicalsupport The FTP server must be configured before you can capture the supportShow and supportSave information. If the FTP server is not configured, the wizard prompts you to configure it.
PAGE 348
26 Topology Figure 26-2 Capture Technical Support Information Wizard Topology This section describes a few problem scenarios related to topology. • • • • “Nodes Swapped With Another Switch Node” on page 26-10 “Lettering in Legend Unreadable When Printed” on page 26-10 “Links Do Not Reconfigure After Disruptive Failover” on page 26-11 “Nodes Overlap” on page 26-11 Nodes Swapped With Another Switch Node Nodes are repositioned after expanding/collapsing link bundles in any of the topology layouts.
PAGE 349
Pinpointing Additional Problem Areas 26 Links Do Not Reconfigure After Disruptive Failover Links sometimes do not reconfigure correctly in the core-edge topology mode after a disruptive HA failover, causing them to be out of proportion. Whenever the ISL links that connect to the nodes end up out of proportion, select any of the ISL link styles and the topology layout issue is then corrected. Nodes Overlap If you move nodes then redo the view in the tree layout, the nodes can sometimes overlap.
PAGE 350
26 Pinpointing Additional Problem Areas You can also click Help > Register to view the license key and serial number. If you still cannot find your license key and serial number, contact Technical Support.
PAGE 351
Pinpointing Additional Problem Areas 26 Welcome Page Does Not Launch If the Internet Explorer security settings are configured such that no Active X components or Java Script can be executed, then the Fabric Manager welcome page does not launch. Use the following procedure to configure the Internet Explorer security parameters to allow the Welcome page to launch. To configure the Internet Explorer security parameters 1. In the Internet Explorer, click Tools > Internet Options. 2.
PAGE 352
26 Pinpointing Additional Problem Areas You must have access to at least AD0 and the physical fabric on an Admin Domain-aware switch to monitor and manage that switch. Wizard Hangs Occasionally the FC Router Configuration wizard and the Device Connectivity Troubleshooting wizard (device diagnostic wizard) hang due to rendering issues with Java Swing. If this happens, close the wizard by clicking the X button in the upper right-hand corner of the window, and then relaunch the wizard.
PAGE 353
Pinpointing Additional Problem Areas 26 You can use the uptime command to verify how long the switch has been running. Refer to the Fabric OS Command Reference for information. Stopping Fabric Manager Server on Solaris and Linux Included in the Fabric Manager installation are scripts for starting and stopping the Fabric Manager server. Normally you do not need to use these scripts, because the server starts automatically. However, for troubleshooting you might need to stop and restart the server.
PAGE 354
26 Pinpointing Additional Problem Areas fmsupportshow Output File is Empty On Windows, if the FM_HOME environment variable becomes corrupted, then when you run fmsupportshow, an output file with the proper name and timestamp is created in the wrong directory and is empty. To fix this problem, edit the FM_HOME environment variable to have the correct path.
PAGE 355
Appendix Repository A The Common Information Model (CIM) is an industry standard developed by the Distributed Management Task Force (DMTF). CIM describes application data so that administrators can view data from different platforms and vendors in the same way. CIM is not a database.
PAGE 356
A 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. Table A-1 CIM_AdminDomain View Column Type Qualifier Description Dbid Int Key fabric.
PAGE 357
A Device Table A-2 CIM_ComputerSystem View (Continued) Column Type Qualifier Description Database Equivalent Example Fabric_id Int Foreign Key Database key for fabric, used for joins to go from fabric to switches. Fabric.dbid 1 Name String 16 WWN of switch. Switches.wwn 10000060 691078F2 Dedicated Int Fixed value of 5, indicating a switch. None. Fixed value of 5. 5 OtherIdentifyingInfo String 10 String value of domain_id. This is a string[ ] in MOF. Switches.
PAGE 358
A Switch Port Table A-4 CIM_LogicalPortGroup View Column Type Qualifier Description Database Equivalent Example Dbid Int Key Database key used for joins to replace traversal of associations. device.dbid 1 Name String 16 WWN of node. Device.wwn 20000000c922aec0 NameFormat String 3 Format. It is always “WWN”. None. Fixed string 'WWN 'WWN User defined name. Device.inqname [34] “Emulex LP850 FV3.20X4 DV5-5.
PAGE 359
Switch Port Table A-5 A CIM_FCPort View (Continued) Column Type Qualifier Description Database Equivalent SystemName String 16 Switch or device WWN. Example 10000060695 For switch port: 0056e switches.wwn where switches.dbid=switch_port. switch_id. For device_port: device.wwn where device.dbid=device_port.de vice_id. ElementName String Port symbolic name, if available. Switch ports use port name. OperationalStatus Int Small Operational status of device or switch port.
PAGE 360
A Switch Port Table A-5 CIM_FCPort View (Continued) Column Type Qualifier Description Database Equivalent Example PortNumber Int Short 20 PortNumber. For switch_port: switch_port.port_number. For device_port: switch_port. port_number where device_port.switch_ port_wwn = switch_port.port_wwn. If it fails to join, it is set to -1 PortType Int Short FC Type. For switch_port: switch_port.port_type suitably mapped. For device_port, device_port.port_type suitably mapped.
PAGE 361
Device Port A Table A-6 shows how switch_port. port_status is mapped to API status and CIM operational status. This mapping is not in sync with CIM values because CIM uses API status and Fabric Manager uses the Web Tools Backend port status. These statuses have different values and logic. Table A-6 Port Status Mapping API port status WT port status (switch_port.
PAGE 362
A Zone Table A-7 Column CIM_ZoneSet View (Continued) Type Qualifier Description ElementName String Active Int Small Database Equivalent Example Name of zone config. Zone_config.name where config_type=1 LSAN_cfg Boolean, 1 for enabled config. Zone_confg.config_ state==1 1 Zone A zone is represented in CIM by Zone. Fabric Manager contains a CIM_Zone view in its database and is defined by the following table.
PAGE 363
Zone Alias Table A-9 A CIM_ZoneMembershipSettingData view (Continued) Column Type Qualifier Description Database Equivalent Example Zone_id Int Key of zone. Zone_config.dbid 4 Connectivity MemberType Int 2–device_port 4–domain:port 5–device 4 or 2 Go through each member in Zone_config.members Connectivity MemberID String 16 Connectivity MemberID is Domain:port if Connectivity MemberType is 4 (domain:port) and WWN if Connectivity MemberType is 2 (device port) or 5 (device).
PAGE 364
A Zone Alias Table A-10 A-10 CIM_NamedAddressCollection (Continued) Column Type Qualifier Description Database Equivalent Example Connectivity MemberID String 16 Go through each member in Zone_config.members 1:4 or 21000000870 427BD Connectivity MemberID is Domain:port if Connectivity MemberType is 4 (domain:port) and WWN if Connectivity MemberType is 2 (device port) or 5 (device).
PAGE 365
Appendix Licenses for Third-Party Products B The following third-party products are included as part of Fabric Manager: • • • • • • • • • • • • • • • • • • • • • Apache Xerces XML Parser - v1.7.0 (Apache License) AXL RADIUS Client API 3.29 (AXL License) FTP Client (Reusable Objects/NetComponents License) FTP server by Rana Bhattacharyya (Apache License) FTP tools, edtftpj-1.4.5.jar, (LGPL License 2.1) HTTP Client 0.3-3 (LGPL License 2.1) Java On line help 1.1.
PAGE 366
B ABA Licence 1. For the purposes of this Licence, the term "Software" refers to all files containing a copyright notice referring to "The ABA Public Licence", and all derivative works. If this Licence is applied to a source file, then it applies equally to all compiled, encoded, executable or encrypted formats. Likewise if this Licence is applied to a file it applies to all subsequent modifications to the file. 2.
PAGE 367
Apache License B 10. The Software is provided with NO WARRANTY explicit or implied. Australian Business Access does not claim or represent any suitability of purpose or guarantee of correct operation. This is free software. If it breaks you get to keep both pieces. 11. The Software is put to its Permitted Uses solely at the discretion and risk of the Licensee.
PAGE 368
B Apache License "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
PAGE 369
Apache License B normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
PAGE 370
B AXL License 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.
PAGE 371
Jason Hunter & Brett McLaughlin License B SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. THE SOFTWARE IS NOT DESIGNED FOR USE IN HIGH RISK ACTIVITIES REQUIRING FAIL-SAFE PERFORMANCE. AXL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES. Restricted Rights Legend This software and documentation is a "commercial item," as defined in 48 C.F.R. 2.
PAGE 372
B LGPL License 2.0 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. This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter and Brett McLaughlin .
PAGE 373
LGPL License 2.0 B Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.
PAGE 374
B LGPL License 2.0 Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3.
PAGE 375
LGPL License 2.0 B 7. 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.
PAGE 376
B LGPL License 2.0 12.
PAGE 377
LGPL License 2.1 B Ty Coon, President of Vice LGPL License 2.1 Licensing agreement for JBOSS (http://www.opensource.org/licenses/lgpl-license.php) Licensing agreement for JfreeChart from Object Refinery (http://www.object-refinery.com/lgpl.html) Licensing agreement for HTTP Client package (Ronald Tschalär package) GNU Lesser General Public License Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
PAGE 378
B LGPL License 2.1 Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.
PAGE 379
LGPL License 2.1 B "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
PAGE 380
B LGPL License 2.1 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.
PAGE 381
LGPL License 2.1 B a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library.
PAGE 382
B LGPL License 2.1 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11.
PAGE 383
LGPL License 2.1 B 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.
PAGE 384
B MIT License 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.
PAGE 385
Open SSL License B * * 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.
PAGE 386
B Open SSL License * 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 acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4.
PAGE 387
Open SSL License B * OF THE POSSIBILITY OF SUCH DAMAGE. * ==================================================================== * * 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.
PAGE 388
B Open SSL License * 1. Redistributions of source code must retain the copyright * notice, this list of conditions and the following disclaimer. * 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.
PAGE 389
Public Domain B Public Domain This work was autored by Timothy Gerard Endres, time@gjt.org. This work has been placed into the public domain. You are free to use this work in any way you wish. DISCLAIMER THIS SOFTWARE IS PROVIDED AS-IS, WITH ABSOLUTELY NO WARRANTY. YOU ASSUME ALL RESPONSIBILITY FOR ANY AND ALL CONSEQUENCES THAT MAY RESULT FROM THE USE OF THIS SOFTWARE! Reusable Objects/NetComponents License Original Reusable Objects, Inc. Copyright © 1996-1998 Original Reusable Objects, Inc.
PAGE 390
B Sun Java License ORO MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY OF THE LICENSED SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. ORO SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE LICENSED SOFTWARE OR ITS DERIVATIVES.
PAGE 391
Sun Java License B 2. LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a nonexclusive, non-transferable, limited license without license fees to reproduce and use internally Software complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms. 3. RESTRICTIONS.
PAGE 392
B Sun Java License 9. 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. 10. U.S.
PAGE 393
Wolf Paulus License B C. Java Technology Restrictions. You may not create, modify, or change the behavior of, or authorize your licensees to create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention designation. D. Source Code.
PAGE 394
B Wolf Paulus License INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE 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.
PAGE 395
Wolf Paulus License B (8) CALSBAD CUBES DISCLAIMS ANY WARRANTIES THAT MAY BE EXPRESS OR IMPLIED BY LAW REGARDING THE LOGO, INCLUDING WARRANTIES AGAINST INFRINGEMENT OF THIRD PARTY RIGHTS AND ANY OTHER WARRANTIES THAT MAY BE IMPLIED BY APPLICABLE LAW. CARLSBAD CUBES DOES NOT GRANT ANY INDEMNITY AGAINST INFRINGEMENT OR OTHER CLAIMS ARISING FROM YOUR USE OF THE LOGO. YOUR USE OF THE LOGO IS AT YOUR OWN RISK.
PAGE 396
B B-32 Wolf Paulus License Fabric Manager Administrator’s Guide Publication Number: 53-1000196-01-HP
PAGE 397
Index Symbols .csv file Alerts view configuring display options API policy, configuring 17-7 4-13 7-10 2-4 26-3 authentication domain authentication issues Numerics authentication options, changing 24-3 503 Service Unavailable/Overloaded error 26-12 B A backbone fabric AAA configuration 12-7 26-4 7-8 acknowledging alerts activating current port connectivity configuration 18-2 stored port connectivity configuration 18-4 AD. See Admin Domains.
PAGE 398
C call home configuring 10-3 configuring notification parameters 7-13 editing configurations 10-4 enabling and disabling 10-5 external executable 10-2 monitoring alerts 10-6 triggers 10-1 capturing supportShow and supportSave output change management configuring notification parameters 7-13 limitations 9-3 managing profiles 9-1 snapshots and change reports 9-6 taking snapshots 9-8 change reports displaying 9-6 displaying in Excel 9-10 exporting 9-9 printing 9-11 changing admin password 12-2 admin security p
PAGE 399
creating change management profiles 9-4 custom performance monitoring graphs 8-11 custom performance monitoring reports 8-8 firmware policy 14-6 login banner 24-7 LSANs 19-6 performance monitor report templates 8-14 port groups 4-19 reboot groups (multiple switches) 14-20 reboot groups (single switch) 14-21 reports 22-1 secure fabrics 17-1 snapshots 9-8 switch groups 4-16 user account in FTP server 14-18 CUP 18-1 customizing baseline configurations Fabric Manager 3-18 tables 3-18 11-21 D database backups
PAGE 400
email notification parameters, configuring 7-13 Fabric Watch about 16-1 administering 16-2 Fabric Watch module, launching enabling call home 10-5 no-node WWN zoning 17-17 performance monitoring 8-5 ports 11-6 secure mode 17-1 switch passwords 12-1 switches 11-6 tool tips 3-21 end-to-end monitoring 8-2 fabric, CIM model A-2 FabricManager.
PAGE 401
14-8 14-1 HTTP requirement 2-3 firmware versions, viewing firmware-specific features FMS-enabled switches activating port connectivity configuration 18-2 activating stored port connectivity configuration identifying 18-1 foreign fabrics, importing 21-7 Front Panel policy, configuring I 18-4 17-13 FTP built-in server 2-1 FTP server configuring 14-9 moving firmware to 14-18 FTP server (built-in) as firmware repository 14-3 creating user account in 14-18 full database backup 23-2 icons Topology view 5-2
PAGE 402
19-2 L metaSAN launching Fabric Manager 3-1 Fabric Watch module 16-1 gping application 21-4 policy editor 17-3 Server Management Console 24-2 third-party management applications Web Tools Switch Explorer 21-5 license keys administering 11-10 exporting 11-10 for Fabric Manager 26-11 importing and restoring 11-12 removing 11-13 license types 2-4 monitoring call home alerts 10-6 link incidents 18-9 performance 8-1 MS policy, configuring 17-11 modifying change management profiles link incidents, monitorin
PAGE 403
performance monitoring about 8-1 creating custom graphs 8-11 creating custom reports 8-8 creating report templates 8-14 deleting reports and graphs 8-19 disabling 8-7 displaying reports and graphs 8-18 editing graphs 8-19 enabling 8-5 exporting reports 8-18 generating reports from templates 8-16 graphs 8-4 opening reports in Excel 8-20 printing reports 8-17 report templates 8-4 reports 8-3 saving reports and graphs 8-17 troubleshooting 26-14 physical fabric administrator 1-6 physical health of switches, che
PAGE 404
11, 17-13 reports, performance monitoring deleting 8-19 displaying 8-18 exporting 8-18 opening in Excel 8-20 printing 8-17 saving 8-17 request node identification 18-8 security, no-node WWN zoning 17-17 sequenced reboot sequenced reboot, troubleshooting server installation 2-6, 2-14, 2-17 18-8 Role-Based Access Control.
PAGE 405
supportShow capturing output 26-8 supportshow information capturing 24-6, 26-1 printing 26-9 switch colors 5-2 third-party management applications adding 21-2 editing 21-4 examples 21-4 launching 21-4 time and date, synchronizing 11-5 9-10 Switch Explorer, launching 21-5 tool tips enabling and disabling Topology view 5-3 topologies, viewing 5-1 switch configuration, exporting switch groups about 4-14 creating 4-16 deleting 4-20 editing 4-18 switch health report 22-1 switch models supported 11-3 switch
PAGE 406
version mismatch 26-6 VEX_Ports about 19-2, 20-3 video drivers 2-2 View panel example 5-1 viewing fabric events 7-11 fabric topologies 5-1 firmware repository 14-3 links 5-9 SAN firmware versions 14-8 virtual memory requirements 1-4 W Web Server port number, changing Web Tools, launching 24-10 21-5 2-4 WSNMP policy, configuring 17-7 Windows authentication domain Z zone alias, CIM model A-9 zone configuration, CIM model A-7 zone conflicts, identifying 18-6 zone membership, CIM model A-8 zone, CIM mo