Fabric OS Administrator’s Guide Supporting Fabric OS v5.0.
Copyright © 2005, Brocade Communications Systems, Incorporated. ALL RIGHTS RESERVED. Publication Number: 53-0000518-09 Brocade, the Brocade B weave logo, Secure Fabric OS, and SilkWorm are registered trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON, IBM BladeCenter are registered trademarks of IBM Corporation in the U.S. and other countries.
Document History The following table lists all versions of the Fabric OS Administrator’s Guide. Document Title Publication Number Summary of Changes Publication Date Fabric OS Procedures Guide 53-0000518-02 First released edition. April 2003 Fabric OS Procedures Guide 53-0000518-03 Revised for Fabric OS v4.2.0. December 2003 Fabric OS Procedures Guide 53-0000518-04 Revised to include switchspecific information. March 2004 Fabric OS Procedures Guide 53-0000518-05 Revised for Fabric OS v4.
Contents About This Document How This Document Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Supported Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi What’s New in This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Additional Information . . . . . . . . . . . . . . . . . .
Disabling and Enabling a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Disabling and Enabling a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Activating Ports on Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Making Basic Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Connecting to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring for the SSL Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Browser and Java Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Summary of SSL Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Choosing a Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 Generating a Public/Private Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Obtaining and Unzipping Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Checking Connected Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 About the Download Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Upgrading SilkWorm Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7 Using Dynamic Load Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Viewing Routing Path Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Viewing Routing Information Along a Path . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Administering FICON Fabrics FICON Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Configuring Switches . . . . . . . . . . . . . . .
Recording Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Chapter 8 Chapter 9 Configuring the Distributed Management Server Enabling and Disabling the Platform Services . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Controlling Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Configuring the Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Correcting Link Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19 Correcting Marginal Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22 Inaccurate Information in the System Message Log . . . . . . . . . . . . . . . . . . . 10-23 Recognizing the Port Initialization and FCP Auto Discovery Process. . . . . . 10-24 Section II Chapter 11 Licensed Features Administering Extended Fabrics About Extended Link Buffer Allocation.
Chapter 13 Administering Advanced Zoning Zoning Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 Zoning Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Zone Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Zone Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5 Zone Aliases . . .
Monitoring ISL Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10 Monitoring Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10 Displaying Monitor Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11 Clearing Monitor Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14 Saving and Restoring Monitor Configurations . . . . . . . . . . . . . . .
Supported Brocade Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Unsupported Brocade Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Configuration Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Configuration Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Zoning Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document This document is a procedural guide to help SAN administrators configure and manage a storage area network (SAN) using the Brocade Fabric OS Command Line Interface (CLI).
• Chapter 13, “Administering Advanced Zoning” provides procedures for use of the Brocade Advanced Zoning licensed feature. • Chapter 14, “Administering Advanced Performance Monitoring” provides procedures for use of the Brocade Advanced Performance Monitoring licensed feature. • Appendix A, “Configuring the PID Format” provides information about the various switch PID formats available and procedures for setting the PID format.
What’s New in This Document The following changes were made in the 53-0000518-07 edition of this document: • The book has been reorganized; Section I contains standard Fabric OS features, and Section II contains licensed Fabric OS features. • • • • The RADIUS configuration procedures were revised. New features and procedures related to the SilkWorm 48000 switch have been added New features and procedures related to the SilkWorm 200E switch have been added.
Notes, Cautions, and Warnings The following notices appear in this document. Note A note provides a tip, emphasizes important information, or provides a reference to related information. Caution A caution alerts you to potential damage to hardware, firmware, software, or data. Warning A warning alerts you to potential danger to personnel. Additional Information This section lists additional Brocade and industry-specific documentation that you might find helpful.
• SilkWorm 24000 QuickStart Guide SilkWorm 12000 • • SilkWorm 12000 Hardware Reference Manual SilkWorm 12000 QuickStart Guide SilkWorm 4100 • • SilkWorm 4100 Hardware Reference Manual (for v4.4.x and later software) SilkWorm 4100 QuickStart Guide (for v4.4.x and later software) SilkWorm 3900 • • SilkWorm 3900 Hardware Reference Manual (for v4.x software) SilkWorm 3900 QuickStart Guide (for v4.x software) SilkWorm 3250/3850 • • SilkWorm 3250/3850 Hardware Reference Manual (for v4.
Release notes are available on the Brocade Connect Web site and are also bundled with the Fabric OS firmware. Other Industry Resources For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, as well as other applications: http://www.t11.
The serial number label is located as follows: 3.
xxii Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Section Standard Features This section describes standard Brocade Fabric OS features, and includes the following chapters: • • • • • • • • • • Chapter 1, Introducing Fabric OS CLI Procedures Chapter 2, Performing Basic Configuration Tasks Chapter 3, Configuring Standard Security Features Chapter 4, Maintaining Configurations and Firmware Chapter 5, Configuring SilkWorm 12000, 24000, and 48000 Directors Chapter 6, Routing Traffic Chapter 7, Administering FICON Fabrics Chapter 8, Configuring the Distribut
Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Introducing Fabric OS CLI Procedures 1 This guide contains procedures for configuring and managing a Brocade® SilkWorm® Storage Area Network (SAN) using the Fabric OS Command Line Interface (CLI). The guide applies to the following Brocade product models: • SilkWorm switches: 200E, 3016, 3250, 3850, 3900, 4012, and 4100 These SilkWorm models contain a fixed number of ports (they are fixed-port switches).
1 Scope and References Scope and References Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc., documenting all possible configurations and scenarios is beyond the scope of this document. In some cases, earlier releases are highlighted to present considerations for interoperating with them. The hardware reference manuals for SilkWorm products describe how to power up devices and set their IP addresses.
Help Information 1 You can access switches from different connections, such as Web Tools, CLI, and API. When these connections are simultaneous, changes from one connection might not be updated to the other, and some modifications might be lost. When simultaneous connections are used, make sure that you do not overwrite the work of another connection.
1 Help Information Example switch:admin> help configure Administrative Commands configure(1m) NAME configure - change system configuration settings SYNOPSIS configure AVAILABILITY admin DESCRIPTION This command changes some system configuration settings, including: o Arbitrated loop settings o Switch fabric settings o System services settings o Virtual channel settings (output truncated) Displaying Additional Help Topics The following commands provide help files for specific topics: 1-4 diagHelp Diagn
Chapter Performing Basic Configuration Tasks 2 This chapter contains procedures for performing basic switch configuration tasks using the Fabric OS command line interface (CLI). Connecting to the Command Line Interface You can connect to the command line interface (CLI) either through a telnet connection or through the serial port. To connect with telnet 1. Verify that the switch is connected to the IP network through the RJ-45 Ethernet port.
2 Connecting to the Command Line Interface Observe these considerations for telnet connections: • • Never change the IP address of the switch while two telnet sessions are active; if you do, your next attempt to log in fails. To recover, gain access to the switch by one of these methods: - You can use Web Tools and perform a fast boot. When the switch comes up, the telnet quota is cleared. (For instructions on performing a fast boot with Web Tools, refer to the Web Tools Administrator’s Guide.
Setting the IP Address 2 Setting the IP Address You must connect through the serial port to set the IP address (refer to “To connect through the serial port” on page 2-2). After connecting, use the ipAddrSet command to set the IP address. To set the IP address on the SilkWorm 3016 The SilkWorm 3016 does not have an Ethernet port or an external serial port. You must configure the IP address for this model through the IBM eServer BladeCenter management module.
2 Setting the Default Account Passwords You can also create up to 15 additional accounts per logical switch and designate their roles as either admin, switchAdmin, or user. Refer to the procedures for doing so in “Creating and Maintaining UserDefined Accounts” on page 3-6. For large enterprises, Fabric OS supports RADIUS services, as described in “Setting Up RADIUS AAA Service” on page 3-9. In addition to the account access passwords, each switch can set a boot PROM password.
Setting the Date and Time 2 login: admin Password: Please change your passwords now. Use Control-C to exit or press 'Enter' key to proceed. for user - root Changing password for root Enter new password: ***** Password changed. Saving password to stable storage. Password saved to stable storage successfully. Please change your passwords now. for user - factory Changing password for factory Enter new password: ***** Password changed. Saving password to stable storage.
2 Setting the Date and Time Note If secure mode is not enabled, a change in date or time to one switch is forwarded to the principal switch and distributed to the fabric. If secure mode is enabled, date or time changes can be made only on the primary FCS switch and distributed to the fabric. To set the date and time 1. Connect to the switch and log in as admin. 2.
Setting the Date and Time 2 Example switch:admin> tsclockserver LOCL switch:admin> tsclockserver “132.163.135.131” switch:admin> tsclockserver 132.163.135.131 switch:admin> It is suggested that you synchronize time with an external NTP server, as described on page 2-6. If you cannot do so, use the next procedure. To set the time zone 1. Connect to the switch and log in as admin. 2.
2 Maintaining Licensed Features Table 2-2 Conversion from UTC to Local Time (Continued) Local Time tstimezone Parameter (Difference From Universal Time Conversion) Pacific Daylight -7,0 Alaskan Standard -9,0 Alaskan Daylight -8,0 Hawaiian Standard -10,0 Maintaining Licensed Features Feature licenses might be part the licensed Paper Pack supplied with switch software, or you can purchase licenses separately from your switch vendor, who will provide you with keys to unlock the features.
Maintaining Licensed Features 7. 2 Click Next. A verification screen appears. 8. Verify that the information appears correctly. Click Submit if the information displayed is correct. If the information is incorrect, Click Previous and change the information. 9. After the information is corrected, click Submit. An information screen displays the license keys. You also receive an e-mail from Brocade with the keys and installation instructions. 10. Activate and verify the license as follows: a.
2 Customizing the Switch Name To remove a licensed feature 1. Connect to the switch and log in as admin. 2. Enter the licenseShow command to display the active licenses. 3. Remove the license key using the licenseRemove command. switch:admin> licenseremove “key” The license key is case sensitive and must be entered exactly as given. The quotation marks are optional.
Customizing the Switch Name • 2 SilkWorm 24000 and 48000: swd77 Note Changing the switch name causes a domain address format RSCN to be issued. To customize the switch name 1. SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 switches: Proceed to the next step. SilkWorm 12000, 24000, and 48000 directors: Open a telnet window for each logical switch and enter the switchName command. 2. Connect to the switch and log in as admin. 3.
2 Customizing the Chassis Name Customizing the Chassis Name Beginning with Fabric OS v4.4.0, it is recommended that you customize the chassis name for each switch. Some system logs identify switches by chassis names, so if you assign meaningful chassis names in addition to meaningful switch names, logs will be more useful. To change the chassis name 1. Connect to the switch and log in as admin. 2.
Activating Ports on Demand 2 To disable a port 1. Connect to the switch and log in as admin. 2. SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 switches: Enter the following command: portdisable portnumber where portnumber is the port number of the port you want to disable. SilkWorm 12000, 24000, and 48000 directors: Enter the following command: portdisable slotnumber/portnumber where slotnumber and portnumber are the slot and port numbers of the port you want to disable.
2 Making Basic Connections Ports on Demand is ready to be unlocked in the switch firmware. Its license key might be part of the licensed Paper Pack supplied with switch software, or you can purchase the license key separately from your switch vendor. You might need to generate a license key from a transaction key supplied with your purchase. If so, launch an Internet browser and go to the Brocade Web site at http://www.brocade.com.
Working With Domain IDs 2 Connecting to Devices To minimize port logins, power off all devices before connecting them to the switch. For devices that cannot be powered off, first use the portDisable command to disable the port on the switch, and then connect the device. When powering the devices back on, wait for each device to complete the fabric login before powering on the next one.
2 Working With Domain IDs To display domain IDs 1. Connect to a switch and log in as admin. 2. Enter the fabricShow command. Fabric information is displayed, including the domain ID (D_ID): ras045:admin> fabricshow Switch ID Worldwide Name Enet IP Addr FC IP Addr Name ------------------------------------------------------------------------1: fffc01 10:00:00:60:69:e4:00:3c 10.32.220.80 0.0.0.0 "ras080" 2: fffc02 10:00:00:60:69:e0:01:46 10.32.220.1 0.0.0.0 "ras001" 3: fffc03 10:00:00:60:69:e0:01:47 10.
Linking Through a Gateway 5. 2 Enter a unique domain ID at the Domain prompt. Use a domain ID value from 1 through 239 for normal operating mode (FCSW compatible): Domain: (1..239) [1] 3 6. Respond to the remaining prompts (or press Ctrl-d to accept the other settings and exit). 7. Enter the switchEnable command to reenable the switch.
2 Checking Status To configure a link through a gateway 1. If you are not sure that the PID format is consistent across the entire fabric, enter the configShow command on all switches to check the PID setting. If necessary, change the PID format on any nonconforming switches, as described in “Configuring the PID Format” on page A-1. 2. Connect to the switch on one end of the gateway and log in as admin. 3.
Checking Status 2 To verify high-availability features High-Availability (HA) features provide maximum reliability and nondisruptive replacement of key hardware and software modules. To verify these features, connect to the switch as admin and use any of the following commands: • • chassisshow verifies the field replaceable units (FRUs).
2 Tracking and Controlling Switch Changes Example switch:admin> nsallshow { 010e00 012fe8 012fef 030500 030b1e 030b1f 040000 050000 050def 051700 061c00 071a00 0a07cb 0a07cc 0a07cd 0a07ce 0a07d5 0a07d6 0a07d9 0a07da 0a0f02 0a0f0f 0a0f10 0a0f1b 0b2fef 0f0000 0f0226 0f0233 211700 211fe8 211fef 2c0000 611600 620800 621026 621036 621500 621700 621a00 75 Nx_Ports in the Fabric } switch:admin> 030b04 050200 073c00 0a07d1 0a07dc 0a0f1d 0f02e4 2c0300 6210e4 030b08 050700 090d00 0a07d2 0a07e0 0b2700 0f02e8 61100
Tracking and Controlling Switch Changes 2 The output from the track changes feature is dumped to the system message log for the switch. Use the errDump or errShow command to view the log. Items in the system message log created from the track changes feature are labeled TRCK: 2004/08/24-08:45:43, [TRCK-1001], 212,, INFO, ras007, Successful login by user admin. To display the status of the track changes feature 1. Connect to the switch and log in as admin. 2. Enter the trackChangesShow command.
2 Tracking and Controlling Switch Changes SilkWorm 12000, 24000 and 48000: The output is similar to the following: switch:admin> switchstatuspolicyshow The current overall switch status policy parameters: Down Marginal ---------------------------------PowerSupplies 3 0 Temperatures 2 1 Fans 2 1 WWN 0 1 CP 0 1 Blade 0 1 Flash 0 1 MarginalPorts 2 1 FaultyPorts 2 1 MissingSFPs 0 0 switch:admin> The policy parameter determines the number of failed or inoperable units for each contributor that will trigger a
Tracking and Controlling Switch Changes 2 SilkWorm 3016, 3250, 3850, 3900, 4012, and 4100 switches: The following example shows the command as executed on a SilkWorm 3900 switch.
2 2-24 Tracking and Controlling Switch Changes Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Configuring Standard Security Features 3 This chapter provides information and procedures for configuring standard Fabric OS security features such as account and password management. Additional security features are available when secure mode is enabled. For information about licensed security features available in Secure Fabric OS, refer to the Secure Fabric OS Administrator’s Guide. Secure Protocols Fabric OS supports the secure protocols shown in Table 3-1.
3 Secure Protocols Table 3-2 describes additional software or certificates that you must obtain to deploy secure protocols.
Ensuring Network Security 3 Ensuring Network Security To ensure security, Fabric OS supports secure shell (SSH) encrypted sessions. SSH encrypts all messages, including the client’s transmission of password during login. The SSH package contains a daemon (sshd), which runs on the switch. The daemon supports a wide variety of encryption algorithms, such as Blowfish-CBC and AES.
3 Configuring the Telnet Interface 3. In response to the System Services prompt, enter y. 4. In response to the telnetd prompt, enter off. The telnet interface is disabled. If you entered the command during a standard telnet session, the session terminates. Example switch:admin> configure telnetd Not all options will be available on an enabled switch. To disable the switch, use the “switchDisable” command. Configure...
Blocking Listeners 3 Blocking Listeners SilkWorm switches block Linux subsystem listener applications that are not used to implement supported features and capabilities. Table 3-4 lists the listener applications that SilkWorm switches either block or do not start.
3 Creating and Maintaining User-Defined Accounts Creating and Maintaining User-Defined Accounts In addition to the default administrative and user accounts, Fabric OS supports up to 15 user-defined accounts in each logical switch (domain). These accounts expand your ability to track account access and audit administrative activities. User-defined accounts can be assigned either admin, switchAdmin, or user level roles. Admin-level accounts allow up to two simultaneous login sessions.
Creating and Maintaining User-Defined Accounts 3 To create a user-defined account 1. Connect to the switch and log in as admin. 2. Enter the following command: userConfig --add username -r rolename [-d description] 3. username Specifies the account name, which must begin with an alphabetic character. The name can be from 8 to 40 characters long. It is case-sensitive and can contain alphabetic and numeric characters, the dot (.) and the underscore ( _ ).
3 Changing an Account Password To change account parameters 1. Connect to the switch and log in as admin. 2. Enter the following command: userconfig --change username [-r rolename] [-d description] [-e yes | no] username Changes the account attribute for username. The account must already exist. -r rolename Optionally, changes the role: either admin, switchAdmin, or user in nonsecure mode; admin, user, or nonfcsadmin in secure mode. An account cannot change its own role.
Setting Up RADIUS AAA Service 3 If you log in to an admin account, you can change admin and user passwords. You must provide the old password when the account being changed has the same or higher privileges than the current login account. For example, when logged in as admin, you need admin passwords to change passwords for admin accounts (except when you change the default user account password at login), but you do not need user passwords to change passwords for user accounts.
3 Setting Up RADIUS AAA Service To enable RADIUS service, it is strongly recommended that you access the CLI through an SSH connection so that the shared secret is protected. Multiple login sessions can configure simultaneously, and the last session to apply a change leaves its configuration in effect. After a configuration is applied, it persists after a reboot or an HA failover.
Setting Up RADIUS AAA Service 3 User accounts should be set up by their true network-wide identity, rather than by the account names created on a Fabric OS switch. Along with each account name, the administrator should assign appropriate switch access roles. To manage a nonsecure fabric, these roles can be user or admin. To manage a secure fabric, these roles can be user, admin, or nonfcsadmin.
3 Setting Up RADIUS AAA Service To create the user Open the $PREFIX/etc/raddb/user file in a text editor and add user names and roles for users who will be accessing the switch and authenticating RADIUS. The user will log in using the role specified with Brocade-Auth-Role. The valid roles include root, factory, admin, switchAdmin, and user. You must use quotation marks around “password” and “role”.
Setting Up RADIUS AAA Service • 3 Enabling the Challenge Handshake Authentication Protocol (CHAP) If CHAP authentication is required, then Windows must be configured to store passwords with reversible encryption. Reverse password encryption is not the default behavior; it must be enabled. Note If a user is configured prior to enabling reverse password encryption, then the user’s password is stored and cannot utilize CHAP. To use CHAP, the password must be reentered after encryption is enabled.
3 Setting Up RADIUS AAA Service To configure the RADIUS server 1. From the Windows Start menu, select Programs> Administrative Tools>Internet Authentication Service to open the Internet Authentication Service window. 2. In the Internet Authentication Service window, right-click the Clients folder and select New Client from the pop-up menu. Note A client is the device that uses the RADIUS server; in this case, it is the switch. 3. 4.
Setting Up RADIUS AAA Service 3 12. In the Edit Dial-in Profile window, click the Authentication tab and check only the Encrypted Authentication (CHAP) and Unencrypted Authentication (PAP, SPAP) checkboxes; then click the Advanced tab and click Add. 13. In the Add Attributes window, select Vendor-Specific and click Add. 14. In the Multivalued Attribute Information window, click Add. 15. In the Vendor-Specific Attribute Information window, click the Enter Vendor Code radio button and enter the value 1588.
3 Setting Up RADIUS AAA Service To display the current RADIUS configuration 1. Connect to the switch and log in as admin. 2. Enter this command: switch:admin> aaaConfig --show If a configuration exists, its parameters are displayed. If RADIUS service is not configured, only the parameter heading line is displayed.
Setting Up RADIUS AAA Service 3 At least one RADIUS server must be configured before you can enable RADIUS service. If no RADIUS configuration exists, turning it on triggers an error message. When the command succeeds, the event log indicates that the configuration is enabled or disabled. To delete a RADIUS server from the configuration 1. Connect to the switch and log in as admin. 2. Enter this command: switch:admin> aaaConfig --remove server | all server 3.
3 Configuring for the SSL Protocol Enabling and Disabling Local Authentication It is useful to enable local authentication so that the switch can take over authentication locally if the RADIUS servers fail to respond because of power outage or network problems. To enable or disable local authentication, enter the following command: switch:admin> aaaConfig --switchdb on | off Specifying on enables local authentication; specifying off disables it.
Configuring for the SSL Protocol 3 In countries that allow the use of 128-bit encryption, you should use the latest version of your browser. For example, Internet Explorer 6.0 and later supports 128-bit encryption by default. You can display the encryption support (called “cipher strength”) using the Internet Explorer Help:About menu option. If you are running an earlier version of Internet Explorer, you might be able to download an encryption patch from the Microsoft Web site at http://www.microsoft.com.
3 Configuring for the SSL Protocol Choosing a Certificate Authority To ease maintenance and allow secure out-of-band communication between switches, consider using one certificate authority (CA) to sign all management certificates for a fabric. If you use different CAs, management services operate correctly, but the Web Tools Fabric Events button is unable to retrieve events for the entire fabric.
Configuring for the SSL Protocol 3. 3 Enter the requested information: Country Name (2 letter code, eg, US):US State or Province Name (full name, eg, California):California Locality Name (eg, city name):San Jose Organization Name (eg, company name):Brocade Organizational Unit Name (eg, department name):Eng Common Name (Fully qualified Domain Name, or IP address): 192.1.2.3 Generating CSR, file name is: 192.1.2.3.csr Done.
3 Configuring for the SSL Protocol 6. Copy and paste this section (including the BEGIN and END lines) into the area provided in the request form; then, follow the instructions to complete and send the request. It might take several days to receive the certificates. If the certificates arrive by email, save them to an FTP server. If the CA provides access to the certificates on an FTP server, make note of the path name and make sure you have a login name and password on the server.
Configuring for the SSL Protocol 3 Example Configure... System services (yes, y, no, n): [no] ssl attributes (yes, y, no, n): [no] yes Certificate File. (filename or none): [10.33.13.182.crt] 192.1.2.3.crt CA Certificate File. (filename or none): [none] Select length of crypto key. (Valid values are 40, 56, and 128.): (40..
3 Configuring for the SSL Protocol Installing a Root Certificate to the Java Plug-in For information on Java requirements, refer to “Browser and Java Support” on page 3-18. This procedure is a guide for installing a root certificate to the Java Plug-in on the management workstation. If the root certificate is not already installed to the plug-in, you should install it. For more detailed instructions, refer to the documentation that came with the certificate and to the Sun Microsystems Web site (www.sun.
Configuring for SNMP 3 Troubleshooting Certificates If you receive messages in the browser or in a pop-up window when logging in to the target switch using HTTPS, refer to Table 3-8. Table 3-8 SSL Messages and Actions Message Action The page cannot be displayed The SSL certificate is not installed correctly or HTTPS is not enabled correctly. Make sure that the certificate has not expired, that HTTPS is enabled, and that certificate file names are configured correctly.
3 Configuring for SNMP The SNMP trap configuration specifies the MIB trap elements to be used to send information to the SNMP management station. There are two main MIB trap choices: • Brocade-specific MIB trap Associated with the Brocade-specific SilkWorm MIB (SW-MIB), this MIB monitors SilkWorm switches specifically. • FibreAlliance MIB trap Associated with the FibreAlliance MIB (FA-MIB), this MIB manages SAN switches and devices from any company that complies with FibreAlliance specifications.
Configuring for SNMP 3 Using the snmpConfig Command Use the snmpConfig --set command to change either the SNMPv3 or SNMPv1 configuration. You can also change access control, MIB capability, and system group. Sample SNMPv3 configuration switch:admin> snmpconfig --set snmpv3 SNMPv3 user configuration: User (rw): [snmpadmin1] adminuser Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: New Auth Passwd: Verify Auth Passwd: Priv Protocol [DES(1)/noPriv[2]): (1..
3 Configuring for SNMP Sample SNMPv1 configuration switch:admin> snmpconfig --set snmpv1 SNMP community and trap recipient configuration: Community (rw): [Secret C0de] admin Trap Recipient's IP address in dot notation: [0.0.0.0] 10.32.225.1 Trap recipient Severity level : (0..5) [0] 1 Community (rw): [OrigEquipMfr] Trap Recipient's IP address in dot notation: [10.32.225.2] Trap recipient Severity level : (0..5) [1] Community (rw): [private] Trap Recipient's IP address in dot notation: [10.32.225.
Configuring for SNMP 3 Sample mibCapability configuration switch:admin> snmpconfig --show mibCapability FA-MIB: YES FICON-MIB: YES HA-MIB: YES SW-TRAP: YES swFCPortScn: YES swEventTrap: YES swFabricWatchTrap: YES swTrackChangesTrap: NO FA-TRAP: YES connUnitStatusChange: YES connUnitEventTrap: NO connUnitSensorStatusChange: YES connUnitPortStatusChange: YES SW-EXTTRAP: NO FICON-TRAP: NO HA-TRAP: YES fruStatusChanged: YES cpStatusChanged: YES fruHistoryTrap: NO Sample systemGroup configuration (default) sw
3 Configuring for SNMP Using Legacy Commands for SNMPv1 You should use the snmpConfig command to configure the SNMPv1 agent and traps (refer to “Using the snmpConfig Command” on page 3-27). However, if necessary for backward compatibility, you can choose to use legacy commands. Sample SNMP agent configuration information switch:admin> agtcfgshow Current SNMP Agent Configuration Customizable MIB-II system variables: sysDescr = FC Switch sysLocation = End User Premise sysContact = Field Support.
Configuring for SNMP 3 Sample modification of the SNMP configuration values switch:admin> agtcfgset Customizing MIB-II system variables ... At each prompt, do one of the followings: o to accept current value, o enter the appropriate new value, o to skip the rest of configuration, or o to cancel any change.
3 Configuring for SNMP Sample reset of the SNMP agent configuration to default values switch:admin> agtcfgdefault ***** This command will reset the agent's configuration back to factory default ***** Current SNMP Agent Configuration Customizable MIB-II system variables: sysDescr = Fibre Channel Switch. sysLocation = End User Premise sysContact = sweng authTraps = 0 (OFF) SNMPv1 community and trap recipient configuration: Community 1: Secret C0de (rw) Trap recipient: 192.168.15.
Configuring for SNMP 3 Sample modification of the options for configuring SNMP MIB traps switch:admin> snmpmibcapset The SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB FA-TRAP FA-MIB (yes, y, no, n): [yes] FICON-MIB (yes, y, no, n): [no] y HA-MIB (yes, y, no, n): [no] y SW-TRAP (yes, y, no, n): [no] y swFCPortScn (yes, y, no, n): [no] swEventTrap (yes, y, no, n): [no] swFabricWatchTrap (yes, y, no, n): [no] swTrackChangesTrap (yes, y, no, n): [no] FA-TRAP (yes, y, no, n): [yes] conn
3 Configuring Secure File Copy Sample view of the SNMP MIB trap setup switch:admin> snmpmibcapshow FA-MIB: YES FICON-MIB: YES HA-MIB: YES SW-TRAP: YES swFCPortScn: YES swEventTrap: YES swFabricWatchTrap: YES swTrackChangesTrap: YES FA-TRAP: YES SW-EXTTRAP: YES HA-TRAP: YES fruStatusChanged: YES cpStatusChanged: YES fruHistoryTrap: YES Configuring Secure File Copy You can use the configure command to specify that secure file copy (scp) be used for configuration uploads and downloads.
Setting the Boot PROM Password 3 You should set the boot PROM password and the recovery string on all switches, as described in “With a Recovery String” on page 3-35. If your site procedures dictate that you set the boot PROM password without the recovery string, refer to “Without a Recovery String” on page 3-37. Note SilkWorm 3016: This model does not have a serial port; therefore, boot PROM procedures do not apply.
3 Setting the Boot PROM Password The recovery string must be between 8 and 40 alphanumeric characters. A random string that is 15 characters or longer is recommended for higher security. The firmware prompts for this password only once. It is not necessary to remember the recovery string because it is displayed the next time you enter the command shell. The following prompt displays: New password: 6. Enter the boot PROM password; then reenter it when prompted.
Setting the Boot PROM Password 3 If a password was previously set, the following messages display: Send the following string to Customer Support for password recovery: afHTpyLsDo1Pz0Pk5GzhIw== Enter the supplied recovery password. Recovery Password: 6. Enter the recovery password (string). The recovery string must be between 8 and 40 alphanumeric characters. A random string that is 15 characters or longer is recommended for higher security. The firmware only prompts for this password once.
3 Setting the Boot PROM Password 1. Create a serial connection to the switch as described in “To connect through the serial port” on page 2-2. 2. Reboot the switch by entering the reboot command. 3. Press ESC within four seconds after the message “Press escape within 4 seconds...” displays. The following options are available: Option Description 1 Start system. Continues the system boot process. 2 Recovery password. Lets you set the recovery string and the boot PROM password.
Recovering Forgotten Passwords 3 The following options are available: Option Description 1 Start system. Continues the system boot process. 2 Recovery password. Lets you set the recovery string and the boot PROM password. 3 Enter command shell. Provides access to boot parameters. 6. Enter 3. 7. Enter the passwd command at the shell prompt. Note The passwd command applies only to the boot PROM password when it is entered from the boot interface. 8.
3 Recovering Forgotten Passwords • • 3-40 To recover a lost root password, contact your switch service provider. To recover a lost boot PROM password, contact your switch service provider. You must have previously set a recovery string to recover the boot PROM password.
Chapter Maintaining Configurations and Firmware 4 This chapter contains procedures for maintaining switch configurations and for installing firmware. Maintaining Configurations It is important to maintain consistent configuration settings on all switches in the same fabric, because inconsistent parameters (such as inconsistent PID formats) can cause fabric segmentation.
4 Maintaining Configurations You must have a valid account on the FTP server where the backup file is to be stored. You can specify the use of secure file copy (scp) during the procedure. For instructions on configuring the use of scp by default, refer to “Configuring Secure File Copy” on page 3-34. Before beginning, verify that you can reach the FTP server from the switch. Using a telnet connection, save a backup copy of the configuration file from a logical switch to a host computer as follows: 1.
Maintaining Configurations 4 1. Verify that the FTP service is running on the server where the backup configuration file is located. 2. Connect to the switch and log in as admin. 3. Disable the switch by entering the switchDisable command. 4. Enter the configDownload command. The command becomes interactive and you are prompted for the required information. 5. Respond to the prompts as follows: Protocol (scp or ftp) If your site requires the use of Secure Copy, specify scp.
4 Maintaining Configurations Restoring Configurations in a FICON Environment If the switch is operating in a FICON CUP environment, and the ASM (active=saved) bit is set on, then the switch ignores the IPL file downloaded when you restore a configuration. Table 4-1 describes this behavior in more detail. Table 4-1 Backup and Restore in a FICON CUP Environment ASM bit Command Description on or off configupload All the files saved in file access facility are uploaded to the management workstation.
Maintaining Firmware 4 Downloading Configurations Across a Fabric To save time when configuring fabric parameters and software features, you can save a configuration file from one switch and download it to other switches of the same model type, as shown in the following procedure. Avoid downloading configuration files to different model switches, because that can cause the switches to fail. 1. Configure one switch first. 2. Use the configUpload command to save the configuration information.
4 Maintaining Firmware Obtaining and Unzipping Firmware Firmware upgrades are available for customers with support service contracts and partners on the Brocade Web site at http://www.brocade.com. At the Brocade Web site, click Brocade Connect and follow the instructions to register and download firmware. Partners with authorized accounts can use the Brocade Partner Network.
Maintaining Firmware 4 a. During code activation on SilkWorm 3016, 3250, 3850, or 3900 running Fabric OS v4.1.0 or later, data continues to flow between hosts and storage devices; however, fabric services are unavailable for a period of approximately 5055 seconds. Possible disruption of the fabric can be minimized by ensuring that switches logically adjacent to these models (directly connected via an ISL) are running at the minimum Fabric OS v2.6.1 or later, v3.1.0 or later, or v4.1.0 or later.
4 Maintaining Firmware Table 4-3 Change Effects of Firmware Changes on Accounts and Passwords First Time Subsequent Times (After upgrade, then downgrade, then upgrade) Upgrading Default accounts and their passwords are preserved. User-defined and default accounts and their passwords are preserved. Downgrading User-defined accounts are no longer valid. Default accounts and their passwords are preserved. If a default account was disabled, it is reenabled after the downgrade.
Maintaining Firmware 4 Optionally, before starting a firmware download, you can connect the switch with a serial console cable to a computer that is running a session capture. The information collected might be useful for troubleshooting. Summary of the Upgrade Process The following summary describes the default behavior of the firmwareDownload command (without options) on SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 models: 1. You enter the firmwareDownload command. 2.
4 Maintaining Firmware 5. Use the firmwareShow command to check the current firmware version of the switch to verify compatibility with the version of firmware you are going to download. Note SilkWorm 3016: If you are running Fabric OS v4.2.1 firmware, you cannot downgrade to earlier versions. SilkWorm 3250 and 3850: If you are running Fabric OS v4.2.0 firmware, you cannot downgrade to earlier versions. SilkWorm 3900: If you are running Fabric OS v4.0.2 firmware, you cannot downgrade to earlier versions.
Maintaining Firmware 4 Example switch:admin> firmwaredownload You can run firmwareDownloadStatus to get the status of this command. This command will cause the switch to reset and will require that existing telnet, secure telnet or SSH sessions be restarted. Do you want to continue [Y]: y Server Name or IP Address: 192.1.2.3 User Name: JohnDoe File Name: /pub/v5.0.1/release.plist Password: xxxxx Firmwaredownload has started.
4 Maintaining Firmware During the upgrade process, the director fails over to its standby CP blade and the IP addresses for the two logical switches move to that CP blade's Ethernet port. This might cause informational ARP address reassignment messages to appear on other switches in the fabric. This is normal behavior, because the association between the IP addresses and MAC addresses has changed.
Maintaining Firmware 4 Follow this procedure to upgrade the firmware on SilkWorm 12000, 24000, and 48000 directors: 1. Verify that the FTP service is running on the host server and that you have a user ID on that server. 2. Obtain the firmware file from the Brocade Web site at http://www.brocade.com and store the file on the FTP server. Verify that the FTP service is running and unpack the compressed files preserving directory structures. 3.
4 Maintaining Firmware Example switch:admin> firmwaredownload This command will upgrade both CPs in the switch. If you what to upgrade a single CP only, please use -s option. You can run firmwareDownloadStatus to get the status of this command. This command will cause the active CP to reset and will require that existing telnet, secure telnet, or SSH sessions be restarted. Do you want to continue [Y]: y Server Name or IP Address: 192.1.2.3 User Name: JohnDoe File Name: /pub/v5.0.1/release.
Troubleshooting Firmware Downloads 4 Troubleshooting Firmware Downloads A firmware download can fail for many reasons, such as a power failure, a failed network connection, a failed FTP server, or an incorrect path to unpacked firmware files. In most cases, the firmware will not be affected. You can make necessary corrections (for example, check the Ethernet cables and check the file path names) and then run the firmwareDownload command again. Note Under firmware versions earlier than v4.1.
4 4-16 Troubleshooting Firmware Downloads Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Configuring SilkWorm 12000, 24000, and 48000 Directors 5 This chapter contains procedures that are specific to SilkWorm 12000, 24000, and 48000 Directors. Because directors contain interchangeable 16-port blades (32-port blades in the SilkWorm 48000), their procedures differ from those for SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 fixed-port switches. For example, fixed-port models identify ports by domain, port number, while director models identify ports by slot/port number.
5 Identifying Ports In the SilkWorm 24000 and 48000 default configuration, all the ports are part of a single logical switch. With Fabric OS v4.4.0 and later, you can configure the SilkWorm 24000 as two logical switches (domains). The following sections tell how to identify ports on SilkWorm 12000, 24000, and 48000 models, and how to identify ports for zoning commands. By Slot and Port Number The port number is a number assigned to an external port to give it a unique identifier in a switch.
Basic Blade Management 5 Basic Blade Management The following sections provide procedures for powering a port blade off and on and for disabling and enabling a port blade. Powering Port Blades Off and On Port blades are powered on by default. To power off a port blade 1. Connect to the switch and log in as admin. 2. Enter the slotPowerOff command with the slot number of the port blade you want to power off. The slot must exist in the logical switch where you are logged in.
5 Basic Blade Management To disable a port blade 1. Connect to the switch and log in as admin. 2. Enter the slotOff command with the slot number of the port blade you want to disable: switch:admin> slotoff 3 Slot 3 is being disabled switch:admin> To enable a port blade 1. Connect to the switch and log in as admin. 2.
Basic Blade Management Table 5-1 5 SilkWorm Director Terminology and Abbreviations Term Abbreviation Blade ID Definition SilkWorm 12000 control processor blade CP1 1 The first generation CP blade provided with the SilkWorm 12000. This CP supports 1 and 2 Gbit/sec port speeds. It only supports the dual domain configuration within the chassis. SilkWorm 24000 control processor blade CP2 5 The second generation CP blade provided with the SilkWorm 24000.
5 Setting Chassis Configurations CP Blades CP blades determine the director type: • • • If CP1 blades are installed, the director is a SilkWorm 12000. If CP2 blades are installed, the director is a SilkWorm 24000. If CP4 blades are installed, the director is a SilkWorm 48000. Mixed CP blades are not supported on a single chassis, except during specific upgrade procedures detailed in SilkWorm Director Migration Guide.
Setting Chassis Configurations 5 Table 5-3 lists the supported configurations options for Fabric OS v5.0.1. Table 5-3 Supported Configuration Options Option Number of Domains Maximum Number of Ports Per Switch Supported Port Blades Supported CP Blades Notes 1 1 128 FC2-16, FC4-16 CP2 or CP4 CP4 fits all chassis except the D2 chassis. Option 1 is the default configuration for SilkWorm 24000.
5 Setting Chassis Configurations Obtaining Slot Information For a SilkWorm 12000 or 24000 configured as two logical switches, the chassis-wide commands display or control both logical switches. In the default configuration, SilkWorm 24000 and 48000 directors are configured as one logical switch, so the chassis-wide commands display and control the single logical switch. To display the status of all slots in the chassis 1. Connect to the switch and log in as user or admin. 2.
Setting Chassis Configurations 5 Configuring a New SilkWorm 24000 with Two Domains By factory default, the SilkWorm 24000 director is configured as one 128-port switch (one domain). The procedure assumes that the new director: • • Has been installed and connected to power, but is not yet attached to the fabric. Has been given an IP address, but is otherwise running factory defaults. If this is not the case, back up the current configuration before starting, so that you can restore it later if necessary.
5 Setting Chassis Configurations 9. c. On sw0, enable security mode and use the secModeEnable command to create an FCS list that matches your overall fabric’s FCS policy. d. Reset the version stamp on sw0. e. If you connected sw0 and sw1 in step a and you do not want them connected, disconnect the ISL link between them. If you did not connect them, repeat step b through step d on sw1. Optionally, connect the new two-domain SilkWorm 24000 director to the fabric. 10.
Setting Chassis Configurations 5 5. After the system reboots, log in again as admin to each logical switch and enter the switchName command to assign a name to the new switch. 6. Using the configuration file saved in step 3 as a guide, manually reconfigure sw0 and sw1. Do not configure zoning parameters; these are propagated automatically when you merge the director into the fabric. 7. 8. If the fabric is in secure mode, perform the following steps; otherwise, proceed to step 8. a.
5 Setting the Blade Beacon Mode Setting the Blade Beacon Mode When beaconing mode is enabled, the port LEDs will flash amber in a running pattern from port 0 through port 15 and back again. The pattern continues until the user turns it off. This can be used to locate a particular blade. To set the blade beacon mode on: 1. Connect to the switch and log in as admin. 2.
Chapter Routing Traffic 6 This chapter describes SilkWorm switch routing features and procedures. About Data Routing and Routing Policies Data moves through a fabric from switch to switch and storage to server along one or more paths that make up a route. Routing policies determine the correct path for each frame of data. Caution For most configurations, the default routing policy is optimal, and provides the best performance.
6 Specifying the Routing Policy Specifying the Routing Policy The following routing policies are supported: • Port-based path selection Default on SilkWorm 3016, 3250, 3850, 3900, 12000, 24000, 48000 (using configuration options 1 through 4). These switches support the port-based policy only; you cannot change the routing policy for these switches. SilkWorm 200E, 4012, and 4100 switches can also use port-based routing.
Assigning a Static Route 6 Assigning a Static Route A static route can be assigned only when the active routing policy is port-based. When device-based or exchange-based routing is active, you cannot assign static routes. Thus, the SilkWorm 48000 using configuration option 5 does not support static routing. To assign a static route, use the uRouteConfig command.
6 Using Dynamic Load Sharing To force in-order frame delivery across topology changes 1. Connect to the switch and log in as admin. 2. At the command line, enter the iodSet command. Note This command can cause a delay in the establishment of a new path when a topology change occurs; use it with care. To restore out-of-order frame delivery across topology changes 1. Connect to the switch and log in as admin. 2. Enter the iodReset command at the command line.
Viewing Routing Path Information 6 Viewing Routing Path Information The topologyShow and uRouteShow commands provide information about the routing path. 1. Connect to the switch and log in as admin. 2. Enter the topologyShow command to display the fabric topology, as it appears to the local switch. The following entries appear: Local Domain ID Domain number of the local switch. Domain Domain number of the destination switch. Metric Cost of reaching the destination domain.
6 Viewing Routing Path Information Example switch:admin> topologyshow 2 domains in the fabric; Local Domain ID: 1 Domain: 6 Metric: 500 Name: switch Path Count: 4 Hops: 1 Out Port: 60 In Ports: None Total Bandwidth: 2 Gbps Bandwidth Demand: 0% Flags: D Hops: 1 Out Port: 61 In Ports: None Total Bandwidth: 2 Gbps Bandwidth Demand: 0% Flags: D Hops: 1 Out Port: 62 In Ports: None Total Bandwidth: 2 Gbps Bandwidth Demand: 0% Flags: D Hops: 1 Out Port: 58 In Ports: None Total Bandwidth: 2 Gbps Bandwidth Demand:
Viewing Routing Information Along a Path 6 This example displays the routing information of all the active ports: : switch:admin> urouteshow Local Domain ID: 3 In PortDomain Out Port Metric Hops Flags Next (Dom, Port) --------------------------------------------------------------------------0 1 11 1000 1 D 1,0 11 2 0 1500 2 D 4,0 4 16 500 1 D 4,0 16 1 27 1000 1 D 1,1 27 2 16 1500 2 D 4,16 4 0 29 500 1 D 4,0 This example displays the routing information for port 11 on slot 1: switch:admin> urouteshow 1/1
6 Viewing Routing Information Along a Path Extended stats Detailed statistics on every link. Trace reverse path Traverses from the destination switch back to the source switches. Source route Forces the frame to follow a specified path to reach the destination. Timeout The maximum time to wait for a response from pathInfo, in seconds. Paths always originate on the local switch. The path destination can be specified by domain or port.
Chapter Administering FICON Fabrics 7 FICON Overview IBM Fibre Connections (FICON®) is an industry-standard, high-speed input/output (I/O) interface for mainframe connections to storage devices. Fabric OS supports intermix mode operations, in which FICON and Fibre Channel technology work together. For specific information about intermix mode and other aspects of FICON, refer to the IBM Redbook, FICON® Native Implementation and Reference Guide.
7 FICON Overview To incorporate and manage FICON on a switch or fabric, your system must have Fabric OS v4.1.2 or later installed. If you are implementing FICON in a single-switch noncascaded environment, there are no additional software requirements. The Secure Fabric OS and Advanced Zoning optional Brocade licensed features are required on all switches participating in a FICON multiple-switch cascaded environment. Note Some licenses are installed and activated on the switch at the factory.
FICON Overview 7 Table 7-1 summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics. For detailed information on these commands, refer to the Fabric OS Command Reference Manual. Table 7-1 Fabric OS Commands Related to FICON and FICON CUP Command Description Standard Fabric OS commands: configure Sets the domain ID and the insistent domain ID mode. portSwap Swaps ports. portSwapDisable Disables the portSwap command. portSwapEnable Enables the portSwap command.
7 Configuring Switches Configuring Switches This section describes how to configure a switch in a FICON environment. Use the worksheet on page 7-18 to record your configuration information. The following are recommended FICON environment configuration settings: • Disable dynamic load sharing (dlsReset command). If DLS is enabled, traffic on existing ISL ports might be affected when one or more new ISLs is added between the same two switches.
Preparing a Switch 7 Configuring a Single Switch Single-switch configuration does not require IDID or fabric binding, provided that connected channels are configured for single-byte addressing. However, you should configure IDID to ensure that domain IDs are maintained. Configuring a High-Integrity Fabric To configure a high-integrity fabric (cascaded configuration): 1. Disable each switch in the fabric. 2. For each switch: a. Enable the IDID flag. b. Set the domain ID. c.
7 Setting a Unique Domain ID Setting a Unique Domain ID In a cascaded configuration, each switch must have a unique domain ID, and insistent domain ID (IDID) mode must be enabled. To set a unique domain ID and enable IDID mode, follow these steps: 1. Connect to the switch and log in as admin. 2. Verify that the switch has a unique domain ID. If it does not, set a unique domain ID. For instructions on displaying and changing the domain ID, refer to “Working With Domain IDs” on page 2-15. 3.
Displaying Information 7 Displaying Information You can display link incidents, registered listeners, node identification data, and FRU failures, as described in the following procedures. Link Incidents The registered link incident record (RLIR) ELS contains the link incident information sent to a listener N_Port.
7 Swapping Ports 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 a port’s traffic to another port (swap ports) without changing the I/O Configuration Data Set (IOCDS) on the mainframe computer. To swap ports, perform the following steps (refer to the example that follows): 1. Connect to the switch and log in as admin. 2. Enter the portSwapEnable command (to enable the command for port swapping). 3.
Using FICON CUP 7 Using FICON CUP Host-based management programs manage switches using CUP protocol by sending commands to an emulated control device in Fabric OS. A Brocade switch that supports CUP can be controlled by one or more host-based management programs, as well as by Brocade tools. A mode register controls the behavior of the switch with respect to CUP itself, and with respect to the behavior of other management interfaces.
7 Using FICON CUP The fmsmode setting can be changed whether the switch is offline or online. If fmsmode is changed while the switch is online, a device reset is performed for the control device and an RSCN is generated with PID 0xDDFE00 (where 0xDD is the domain ID of the switch). When FICON Management Server mode is on, the Fabric OS CLI commands listed here return a “switch busy” response if they are issued when the host-based management tool is performing a write operation.
Using FICON CUP 7 Setting Up CUP When FICON Management Server Mode Is Enabled Fmsmode may be enabled and in use on a switch without a CUP License. The transition from fmsmode disabled to fmsmode enabled with the CUP license installed triggers the notification to the host systems that the CUP feature is available. Without this notification the host systems will never know the CUP feature is available, and consequently will never try to communicate with it.
7 Using FICON CUP Displaying Mode Register Bit Settings The mode register bits are described in Table 7-2. Table 7-2 FICON CUP Mode Register Bits POSC Programmed offline state control. When this bit is set on, the host is prevented from taking the switch offline. The default setting is 1 (on). UAM User alert mode. When this bit is set on, a warning is issued when an action is attempted that will write CUP parameters on the switch. The default setting is 0 (off). ASM Active=saved mode.
Using FICON CUP 7 Setting Mode Register Bits The ficoncupset modereg command is used to set the FICON CUP mode register bits for the local switch. Consider the following when changing mode register bits: • • As required by the CUP protocol, the UAM bit cannot be changed using this command. • Mode register bits can be changed when the switch is offline or online.
7 Using FICON CUP In this example, the ASM bit is set to on; then, the port at slot 1, port 1 is enabled persistently: switch:admin> ficoncupshow modereg POSC UAM ASM DCAM ACP HCP -----------------------------1 0 0 0 1 1 switch:admin> ficoncupset modereg ASM 1 Mode register bit ASM has been set to 1.
Troubleshooting 7 Zoning and PDCM Considerations The FICON Prohibit Dynamic Connectivity Mask (PDCM) controls whether or not communication between a pair of ports in the switch is prohibited or allowed. If there are any differences in restrictions set up with Brocade Advanced Zoning and PDCM, the most restrictive rules are automatically applied. All FICON devices should be configured in a single zone using the “Domain, Area” notation.
7 Backing Up FICON Files Identifying Ports The ficonshow rlir command displays, among other information, a tag field for the switch port. You can use this tag to identify the port on which a FICON link incident occurred. The tag field is a concatenation of the switch domain ID and port number, in hexadecimal format.
Recording Configuration Information 7 To download configuration files with Active=Saved mode enabled Enter the configDownload command. The contents of existing files saved on the switch, which are also present in the “FICON_CUP” section, are overwritten. The files in the “FICON” section of the configuration file, which are not currently on the switch, are saved on the switch. The IPL will not be replaced because Active=Saved mode is enabled.
7 Recording Configuration Information FICON® Switch Configuration Worksheet FICON® Switch Manufacturer:___________________Type: _________ Model: ______ S/N: ________ HCD Defined Switch ID_________(Switch ID) FICON® Switch Domain ID_________(Switch @) Cascaded Directors No _____Yes _____ Corresponding Cascaded Switch Domain ID _____ Fabric Name ________________________________ FICON® Switch F_Ports Attached N_Ports / E_Ports (CU, CPC, or ISL) Slot Port Number Number 7-18 Port Address Laser Type:
Recording Configuration Information 7 Sample IOCP Configuration File for SilkWorm 3900, 12000, and 24000 Switches The channel subsystem controls communication between a configured channel, the control unit, and the device. The I/O Configuration Dataset (IOCDS) defines the channels, control units, and devices to the designated logical partitions (LPARs) within the server; this is defined using the Input/Output Configuration Program (IOCP).
7 Recording Configuration Information In the following sample IOCP configuration file, the UNIT value for FICON CUP definitions is 2032 for any FICON director regardless of vendor or platform. So all SilkWorm 3900, SilkWorm 12000, or SilkWorm 24000 switches require UNIT=2032 for the CUP definition. All Domain IDs are specified in hex values in the IOCP (and not in decimal values); the Domain IDs in the example are for demonstration purposes only.
Recording Configuration Information 7 /*********************************************************************/ /* MONITOR I OPTIONS */ /* */ /* X A O N L Y */ /* */ /*********************************************************************/ FCD /* FICON Director */ CHAN /* COLLECT CHANNEL STATISTICS */ CPU /* COLLECT CPU STATISTICS */ CYCLE(1000) /* SAMPLE ONCE EVERY SECOND */ DEVICE(NOSG) /* PREVENT SORT OF STORAGE GROUPS*/ DEVICE(NOCHRDR) /* CHARACTER READER STATISTICS WILL NOT BE COLLECTED */ DEVICE(COMM) /
7 7-22 Recording Configuration Information Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Configuring the Distributed Management Server 8 The Brocade Fabric OS Distributed Management Server allows a SAN management application to retrieve information and administer interconnected switches, servers, and storage devices. The management server assists in the autodiscovery of switch-based fabrics and their associated topologies. A client of the management server can find basic information about the switches in the fabric and use this information to construct topology relationships.
8 Controlling Access To disable platform services 1. Connect to the switch and log in as admin. 2. Enter the msplMgmtActivate command. 3. Enter y to confirm the deactivation. switch:admin> msplmgmtdeactivate MS Platform Service is currently enabled. This will erase MS Platform Service configuration information as well as database in the entire fabric. Would you like to continue this operation? (yes, y, no, n): [no] y Request to deactivate MS Platform Service in progress......
Controlling Access 8 In the following example, the list is empty: switch:admin> msconfigure 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN select : (0..3) [1] 1 MS Access list is empty. 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN done ... switch:admin> To add a member to the ACL 1. Connect to the switch and log in as admin. 2. Enter the msConfigure command.
8 Controlling Access Example switch:admin> msconfigure 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN select : (0..3) [1] 2 Port/Node WWN (in hex): [00:00:00:00:00:00:00:00] 20:00:00:20:37:65:ce:aa *WWN is successfully added to the MS ACL. 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN select : (0..
Configuring the Server Database 8 Example switch:admin> msconfigure 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN select : (0..3) [1] 3 Port/Node WWN (in hex): [00:00:00:00:00:00:00:00] 20:00:00:20:37:65:ce:aa *WWN is successfully deleted from the MS ACL. 0 Done 1 Display the access list 2 Add member based on its Port/Node WWN 3 Delete member based on its Port/Node WWN select : (0..
8 Controlling Topology Discovery The contents of the management server platform database are displayed. switch:admin> msplatshow ----------------------------------------------------------Platform Name: [9] "first obj" Platform Type: 5 : GATEWAY Number of Associated M.A.: 1 [35] "http://java.sun.
Controlling Topology Discovery 3. 8 Enter the mstdEnable all command to enable the discovery feature on the entire fabric. switch:admin> mstdenable Request to enable MS Topology Discovery Service in progress.... *MS Topology Discovery enabled locally. switch:admin> mstdenable ALL Request to enable MS Topology Discovery Service in progress.... *MS Topology Discovery enabled locally. *MS Topology Discovery Enable Operation Complete!! To disable topology discovery 1.
8 8-8 Controlling Topology Discovery Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Working With Diagnostic Features 9 This chapter provides information on diagnostics and how to display system, port, and specific hardware information. It also describes how to set up system logging mapping (syslogd) and how to set up the offloading of error messages (supportSave). The purpose of the diagnostic subsystem is to evaluate the integrity of the system hardware.
9 Viewing Power-On Self Test The following example shows a typical boot sequence, including POST messages: The system is coming up, please wait... Read board ID of 0x80 from addr 0x23 Read extended model ID of 0x16 from addr 0x22 Matched board/model ID to platform index 4 PCI Bus scan at bus 0 : : : : : : Checking system RAM - press any key to stop test Checking memory address: 00100000 System RAM test using Default POST RAM Test succeeded. Press escape within 4 seconds to enter boot interface.
Viewing Switch Status 9 Viewing Switch Status Use the switchStatusShow command to display the overall status of the switch, including its power supplies, fans, and temperature. If the status of any one of these components is either marginal or down, the overall status of the switch is also displayed as marginal or down. If all components have a healthy status, the switch displays a healthy status. To modify the rules used to classify the health of each component use the switchStatusPolicySet command.
9 Viewing Port Information The switchShow command also displays the following information for ports on the specified switch: • • Module type - The SFP type if a SFP is present. • • Port state - The port status. Port speed - The speed of the Port (1G, 2G, 4G, N1, N2, N4, or AN). The speed can be fixed, negotiated, or auto negotiated. Comment - Displays information about the port. This section might be blank or display WWN for F_Port or E_Port, Trunking state, upstream or downstream status.
Viewing Port Information 9 To view the status of a port 1. Connect to the switch and log in as admin. 2. Enter the portShow command, specifying the number that corresponds to the port you are troubleshooting. In this example, the status of port two is shown: switch:admin> portshow 2 portName: portHealth: HEALTHY Authentication: None portDisableReason: None portCFlags: 0x1 portFlags: 0x4903 PRESENT ACTIVE E_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN LED portType: 10.
9 Viewing Port Information Example: portStatsShow command output switch:admin> portstatsshow 3/7 stat_wtx 0 stat_wrx 0 stat_ftx 0 stat_frx 0 stat_c2_frx 0 stat_c3_frx 0 stat_lc_rx 0 stat_mc_rx 0 stat_mc_to 0 stat_mc_tx 0 tim_rdy_pri 0 tim_txcrd_z 0 er_enc_in 0 er_crc 0 er_trunc 0 er_toolong 0 er_bad_eof 0 er_enc_out 0 er_bad_os 0 er_c3_timeout 0 er_c3_dest_unreach 0 er_other_discard 0 er_crc_good_eof 0 er_inv_arb 0 open 0 transfer 0 opened 0 starve_stop 0 fl_tenancy 0 nl_tenancy 0 zero_tenancy 0 4-byte w
Viewing Port Information 9 Example: portErrShow command output switch:admin> porterrshow frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig sig===================================================================== 0: 22 24 0 0 0 0 0 1.5m 0 7 3 0 0 0 1: 22 24 0 0 0 0 0 1.
9 Viewing Equipment Status Table 9-1 Error Summary Description (Continued) Error Type Description link fail Link failures (LF1 or LF2 states) loss sync Loss of synchronization loss sig Loss of signal frjt Frames rejected with F_RJT fbsy Frames busied with F_BSY Viewing Equipment Status You can display status for fans, power supply, and temperature. Note The number of fans, power supply units, and temperature sensors depends on the switch type.
Viewing Equipment Status 9 To display the status of a power supply 1. Connect to the switch and log in as admin. 2. Enter the psShow command: switch:admin> psshow Power Supply #1 is OK 0335,FF2Z0007161,60-0000739-02, B,,DCJ3002-01P, B,FF2Z0007161 Power Supply #2 is faulty 0335,FF2Z0007176,60-0000739-02, B,,DCJ3002-01P, B,FF2Z0007176 switch:admin> The possible status values are: OK Power supply functioning correctly. Absent Power supply not present. Unknown Unknown power supply unit installed.
9 Viewing the System Message Log Viewing the System Message Log The system message log feature enables messages to be saved across power cycles and reboots. SilkWorm 12000, 24000, and 48000 director models maintain an independent system message log for each of the two CP blades. For these models, you should configure syslogd to support chronological system message logs. For details, see “Configuring for syslogd” on page 9-12.
Viewing the Port Log 9 To view the port log 1. Connect to the switch and log in as admin. 2. Enter the portLogShow command: switch:admin> portlogshow 12 time task event port cmd args ------------------------------------------------Thu Apr 14 12:07:09 2005 12:07:09.350 PORT Rx 0 40 02fffffd,00fffffd,0608ffff,14000000 12:07:09.350 PORT Tx 0 0 c0fffffd,00fffffd,060807fc 12:07:10.812 PORT Tx 0 40 02fffffd,00fffffd,07feffff,14000000 12:07:10.813 PORT Rx 0 0 c0fffffd,00fffffd,07fe0627 12:07:19.
9 Configuring for syslogd Because a portLogDump output is long, a truncated example is presented: switch:admin> portlogdump task event port cmd args ------------------------------------------------16:30:41.780 PORT Rx 9 40 02fffffd,00fffffd,0061ffff,14000000 16:30:41.780 PORT Tx 9 0 c0fffffd,00fffffd,0061030f 16:30:42.503 PORT Tx 9 40 02fffffd,00fffffd,0310ffff,14000000 16:30:42.505 PORT Rx 9 0 c0fffffd,00fffffd,03100062 16:31:00.464 PORT Rx 9 20 02fffc01,00fffca0,0063ffff,01000000 16:31:00.
Configuring for syslogd 9 Configuring the Host Fabric OS supports a subset of UNIX-style message severities that default to the UNIX local7 facility. To configure the host, edit the /etc/syslog.conf file to map Fabric OS message severities to UNIX severities, as shown in Table 9-3.
9 Viewing and Saving Diagnostic Information You can specify up to six host IP addresses for storing syslog messages, as shown in this example: switch:admin> syslogdipadd 10.1.2.1 switch:admin> syslogdipadd 10.1.2.2 switch:admin> syslogdipadd 10.1.2.3 switch:admin> syslogdipadd 10.1.2.4 switch:admin> syslogdipadd 10.1.2.5 switch:admin> syslogdipadd 10.1.2.6 switch:admin> syslogdipshow syslog.IP.address.1 10.1.2.1 syslog.IP.address.2 10.1.2.2 syslog.IP.address.3 10.1.2.3 syslog.IP.address.4 10.1.2.4 syslog.
Setting Up Automatic Trace Dump Transfers 9 Setting Up Automatic Trace Dump Transfers You can set up a switch so that diagnostic information is transferred automatically to a remote server. Then, if a problem occurs you can provide your customer support representative with the most detailed information possible. To ensure the best service, you should set up for automatic transfer as part of standard switch configuration, before a problem occurs.
9 Setting Up Automatic Trace Dump Transfers To set up periodic checking of the remote server 1. Connect to the switch and log in as admin. 2. Enter the following command: supportftp -t interval The interval is in hours. The minimum interval is 1 hour. Specify 0 hours to disable the checking feature. To save a comprehensive set of diagnostic files to the server 1. Connect to the switch and log in as admin. 2.
Chapter Troubleshooting 10 Troubleshooting should begin at the center of the SAN — the fabric. Because switches are located between the hosts and storage devices and have visibility into both sides of the storage network, starting with them can help narrow the search path. After eliminating the possibility of a fault within the fabric, see if the problem is on the storage side or the host side, and continue a more detailed diagnosis from there.
10 Gathering Information for Technical Support Table 10-1 Common Troubleshooting Problems and Tools (Continued) Problem Area Investigate Tools Hosts • Incorrect host bus adapter installation • • Host adaptor LEDs • • Incorrect device driver installation • • Device driver diagnostic tools Storage Management Applications Incorrect device driver configuration Incorrect installation and configuration of the storage devices that the software references.
Gathering Information for Technical Support 4. 10 Impact assessment and urgency: • • • • Is the switch down? Is it a standalone switch? How large is the fabric? Is the fabric redundant? 5. Run the supportSave command. (Refer to “Viewing and Saving Diagnostic Information” on page 9-14 and “Setting Up Automatic Trace Dump Transfers” on page 9-15). 6.
10 Analyzing Connection Problems 3. Storage information: • • • • • • Disk/tape type Disk/tape firmware level Controller type Controller firmware level Configuration settings Storage software (such as EMC Control Center, Veritas SPC, etc.) Analyzing Connection Problems If a host is unable to detect its target (for example, a storage or tape device), you should begin troubleshooting the problem in the middle of the data path.
Analyzing Connection Problems 2. 10 Regardless of the device’s zoning, the fcPing command sends the ELS frame to the destination port. A device can take any one of the following actions: • • • Send an ELS Accept to the ELS request. Send an ELS Reject to the ELS request. Ignore the ELS request. There are some devices that do not support the ELS ECHO request. In these cases, the device will either not respond to the request or send an ELS reject.
10 Analyzing Connection Problems Following is sample output from the fcPing command in which one device accepts the request and another device does not respond to the request: switch:admin> fcping 0x020800 22:00:00:04:cf:75:63:85 Source: 0x20800 Destination: 22:00:00:04:cf:75:63:85 Zone Check: Zoned Pinging 0x020800 with 12 bytes of data: received reply from 0x020800: 12 bytes time:1159 usec received reply from 0x020800: 12 bytes time:1006 usec received reply from 0x020800: 12 bytes time:1008 usec receive
Analyzing Connection Problems 10 To check the Simple Name Server (SNS) 1.
10 Restoring a Segmented Fabric 4. Enter the fcpProbeShow command to display the FCP probing information for the devices attached to the specified F_Port or FL_Port. This information includes the number of successful logins and SCSI INQUIRY commands sent over this port and a list of the attached devices. 5. Check the port log to determine whether or not the device sent the FLOGI frame to the switch, and the switch probed the device. To check for zoning problems 1.
Restoring a Segmented Fabric • • • • • • 10 Disable device probing Suppress class F traffic Per-frame route priority Long distance fabric (not necessary on Bloom-based fabrics) BB credit PID format To reconcile fabric parameters individually 1. Log in to one of the segmented switches as admin (switch A). 2. Enter the configShow command. 3. Log in to another switch (switch B) in the same fabric as admin. 4. Enter the configShow command. 5.
10 Correcting Zoning Setup Issues 3. Compare the fabricShow output from the two fabrics. Note the number of domain ID conflicts; there might be several duplicate domain IDs that will need to be changed. Determine which switches have domain overlap and change the domain IDs for each of those switches. 4. Chose the fabric on which to change the duplicate domain ID; connect to the conflicting switch in that fabric. 5. Enter the switchDisable command. 6. Enter the switchEnable command.
Correcting Zoning Setup Issues Table 10-3 10 Commands for Debugging Zoning (Continued) Command Function zoneAdd Use to add a member to an existing zone. zoneCreate Use to create a zone. Before a zone becomes active, the cfgSave and cfgEnable commands must be used. zoneHelp Displays help information for zone commands. zoneShow Displays zone information. Refer to “Administering Advanced Zoning” on page 13-1 for additional information about setting up zoning properly.
10 Recognizing MQ-WRITE Errors 6. Print the output from the cfgShow command. 7. Compare the two fabric zone configurations line by line and look for an incompatible configuration. 8. Connect to one of the fabrics. 9. Run zone configure edit commands to edit the fabric zone configuration for the segmented switch (refer to Table 10-3 on page 10-10 for specific commands.
Correcting I2C Bus Errors 10 To check fan components 1. Log in to the switch as user. 2. Enter the fanShow command. 3. Check the fan status and speed output. If any of the fan speeds display abnormal RPMs, replace the fan FRU. To check the switch temperature 1. Log in to the switch as user. 2. Enter the tempShow command. 3. Check the temperature output. Look for indications of high or low temperatures. To check the power supply 1. Log in to the switch as user. 2. Enter the psShow command.
10 Correcting Device Login Issues Correcting Device Login Issues To try to pinpoint problems with device logins, use this procedure: 1. Log in to the switch as admin. 2. Enter the switchShow command; then, check for correct logins: switch:admin> switchshow switchName: sw094135 switchType: 26.
Correcting Device Login Issues 4.
10 Identifying Media-Related Issues 6. Enter the portLogDumpPort portid command where the port ID is the port number; then, view the device to switch communication. sw094135:admin> portlogdumpport 10 time task event port cmd args ------------------------------------------------12:38:21.590 SPEE sn 10 WS 00000000,00000000,00000000 12:38:21.591 SPEE sn 10 WS 000000ee,00000000,00000000 12:38:21.611 SPEE sn 10 WS 00000001,00000000,00000000 12:38:21.871 SPEE sn 10 NC 00000002,00000000,00000001 12:38:21.
Identifying Media-Related Issues • 10 Functional tests verify the intended operational behavior of the switch by virtue of running frames through ports or bypass circuitry. Table 10-4 Component Test Descriptions Test Name Operands Checks crossporttest [-nframes count] [-lb_mode mode][-spd_mode mode] [-gbic_mode mode] [-norestore mode] [-ports itemlist] Functional test of port external transmit and receive path.
10 Identifying Media-Related Issues 3. Enter the crossporttest -lb_mode 5 command where 5 is the operand that causes the test to be run on the internal switch components (this is a partial list—refer to the Fabric OS Command Reference Manual for additional command information): [-nframes count] Specify the number of frames to send. [-lb_mode mode] Select the loopback point for the test. [-spd_mode mode Select the speed mode for the test. [-ports itemlist] Specify a list of user ports to test.
Correcting Link Failures Table 10-5 10 Switch Component Tests (Continued) Test Function turboramtest Verifies that the on chip SRAM located in the 2 Gbit/sec ASIC is using the Turbo-Ram BIST circuitry. These same SRAMs are tested by portregtest and sramretentiontest using PCI operations, but for this test the BIST controller is able to perform the SRAM write and read operations at a much faster rate. statstest Verifies that the ASIC statistics counter logic.
10 Correcting Link Failures If these fields do not appear, proceed to the step 6. 6. Correct the negotiation by entering the portCfgSpeed [slotnumber/]portnumber, speed_level command if the fields in step 5 do not appear. To check for a loop initialization failure 1. 2. Verify the port is an L_Port. a. Enter the switchShow command. b. Check the comment field of the output to verify that the switch port indicates an L_Port.
Correcting Link Failures 10 Some fabric devices have problems with loop initialization. If this is evident, enter the portCfgPort port #, 1 command. To correct a port that has come up in the wrong mode 1. Enter the switchShow command. 2. Refer to the comment fields (refer to Table 10-6) and follow the suggested actions.
10 Correcting Marginal Links Correcting Marginal Links A marginal link involves the connection between the switch and the edge device. Isolating the exact cause of a marginal link involves analyzing and testing many of the components that make up the link (including the switch port, switch SFP, cable, the edge device, and the edge device SFP). To troubleshoot a marginal link: 1. Enter the portErrShow command.
Inaccurate Information in the System Message Log 5. You will need an adapter to run the loopback test for the SFP. Otherwise, run the portLoopBack test on the marginal port using the loopback mode lb=5. Refer to the Fabric OS Command Reference Manual for additional information. Table 10-7 6.
10 Recognizing the Port Initialization and FCP Auto Discovery Process Recognizing the Port Initialization and FCP Auto Discovery Process The steps in the port initialization process represent a protocol used to discover the type of connected device and establish the port type. The possible port types are as follows: U_Port Universal FC port. This port type is the base Fibre Channel port type and all unidentified, or uninitiated ports are listed as U_Ports. FL_Port Fabric Loop port.
Section Licensed Features This section describes licensed Brocade Fabric OS features and includes the following chapters: • • • • Chapter 11, Administering Extended Fabrics Chapter 12, Administering ISL Trunking Chapter 13, Administering Advanced Zoning Chapter 14, Administering Advanced Performance Monitoring Additional Brocade licensed features are documented in the following books: • • • • Web Tools Administrator’s Guide Fabric Manager Administrator’s Guide Fabric Watch Administrator’s Guide Secur
Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Administering Extended Fabrics 11 This chapter contains procedures for using the Brocade Extended Fabrics licensed feature, which extends the distance that interswitch links (ISLs) can reach. To use extended ISL modes, you must first install the Extended Fabrics license. For details on obtaining and installing licensed features, refer to “Maintaining Licensed Features” on page 2-8.
11 Fabric Considerations A buffer-limited port can come online with fewer buffer credits allocated than its configuration specifies, allowing it to operate at a reduced bandwidth instead of being disabled for lack of buffers. Buffer-limited operation is supported for the L0 and LD extended ISL modes only, and is persistent across reboots, switch disabling and enabling, and port disabling and enabling.
Choosing an Extended ISL Mode 11 Choosing an Extended ISL Mode Table 11-1 lists the extended ISL modes for switches that have a Bloom ASIC. You can configure extended ISL modes with the portCfgLongDistance command when the Extended Fabrics license is activated.
11 Choosing an Extended ISL Mode Table 11-3 lists the extended ISL modes for switches that have a Condor ASIC. Table 11-3 Extended ISL Modes: Switches with Condor ASIC Mode Buffer Allocation Distance @ 1 Gbit/ sec Distance @ 2 Gbit/ sec Distance @ 4 Gbit/ sec Earliest Fabric OS Release Extended Fabrics License Required? 1 Gbit/ sec 2 Gbit/ sec 4 Gbit/ sec L0 5 (26)a 5 (26) 2.5 km 10 km 5 km 2 km All No LE 11 16 10 km n/a 5 km 5 km v3.x, v4.x No L0.
Choosing an Extended ISL Mode 11 • If you set one external port to L2 (60 km) and the other external port is an E_Port, then one internal port is disabled. • • Setting both external ports to L1 (50 km) disables two internal ports. • If you set one external port to L1 (50 km) and the other external port is an E_Port, then one internal port is disabled. • Setting both external ports to L0.5 (25 km) disables one internal port. Setting one external port to L1 (50 km) and the other external port to L0.
11 Choosing an Extended ISL Mode SilkWorm 4012 The number of ports that can be configured at various distances is summarized in Table 11-6. Note that for the SilkWorm 4012, exact distances (rather than set, incremental distances) are used. Table 11-6 SilkWorm 4012 Speed (Gbit/sec) Number of Ports Allowed at Distance (km) 1 Port Up to 2 Ports Up to 3 Ports Up to 4 ports 1 318 km 170 km 120.6 km 96 km 2 159 km 85 km 60.3 km 48 km 4 79.5 km 42.5 km 30.
Configuring an Extended ISL 11 Configuring an Extended ISL Before configuring the ISL, ensure that the following conditions are met: • Extended ISL support for SilkWorm 2000-series switches is limited as follows: - Extended ISLs are not supported between SilkWorm 2000-series switches and other SilkWorm models. - To support extended ISLs between Silkworm 2000-series switches, the fabric.ops.mode.longDistance parameter must be set to 1 on all switches in the fabric.
11 Trunking Over Distance vc_translation_link_init This extended link initialization sequence, which is an enhanced link reset protocol, avoids excessive resetting of ports. By default this option is set to 1 (enabled). To prevent fabric segmentation, this option must be set to 0 (disabled) when connecting to switches running Fabric OS versions earlier than v3.0.2c or v4.0.2. It must be set to 1 (enabled) when configuring a trunk over extended fabrics.
Chapter Administering ISL Trunking 12 This chapter contains procedures for using the Brocade ISL Trunking licensed feature, which optimizes the use of bandwidth by allowing a group of interswitch links to merge into a single logical link. Overview Brocade ISL Trunking reduces or eliminates situations that require static traffic routes and individual ISL management to achieve optimal performance.
12 Standard Trunking Criteria Figure 12-1 Distribution of Traffic over ISL Trunking Groups Trunks operate best when the cable length of each trunked link is roughly equal to the others in the trunk. Cable lengths for participating links should differ by no more than 550 meters. For optimal performance, no more than 30 meters difference is recommended.
Fabric Considerations • 12 SilkWorm 3016: Trunks are supported on the two external ports (0 and 15). Fabric Considerations The ISL Trunking feature is provided with the Fabric OS and can be activated by entering a license key, available from the switch supplier. When the ISL Trunking license is activated (after you have entered the switchDisable and switchEnable commands), trunking is automatically implemented for any eligible ISLs.
12 Initializing Trunking on Ports For trunking groups over which traffic is likely to increase as business requirements grow, consider leaving one or two ports in the group available for future nondisruptive addition of bandwidth. • Consider creating redundant trunking groups where additional ports are available or paths are particularly critical. This helps to protect against oversubscription of trunking groups, multiple ISL failures in the same group, and the rare occurrence of an ASIC failure.
Monitoring Traffic 12 • Brocade Advanced Performance Monitoring monitors traffic flow and allows you to view the impact of different fabric configurations on performance. Refer to “Administering Advanced Performance Monitoring” on page 14-1 for additional information. • Brocade Fabric Watch allows you to monitor traffic flow through specified ports on the switch and send alerts when the traffic exceeds or drops below configurable thresholds.
12 Enabling and Disabling ISL Trunking Enabling and Disabling ISL Trunking You can enable or disable Brocade ISL Trunking for a single port or for an entire switch.When you execute the commands portCfgTrunkPort or switchCfgTrunk to update the trunking configuration, the ports for which the configuration applies are disabled and reenabled with the new trunk configuration. As a result, traffic through those ports could be disrupted. To enable or disable ISL Trunking on one port 1.
Setting Port Speeds 12 Setting Port Speeds For long-distance ports, if a port is set to autonegotiate port speed, the maximum speed (which is 4 Gbit/ sec) is assumed for reserving buffers for the port–this wastes buffers if the port is actually running at 2 Gbit/sec. For long-distance ports, it is best to set the port speed (this applies to SilkWorm 4100 and SilkWorm 48000 only). You can set the port speed for one port or for an entire switch. Trunked ports must be set to the same speed.
12 Displaying Trunking Information To set the speed for all of the ports on the switch 1. Connect to the switch and log in as admin. 2. Enter the switchCfgSpeed command. The format is: switchcfgspeed speedlevel speedlevel Specifies the speed of the link: • 0—Auto-negotiating mode. The port automatically configures for the highest speed. • 1—one Gbit/sec mode. Fixes the port at a speed of one Gbit/sec. Changing the speed to one Gbit/sec causes the port to be excluded from the trunk group.
Trunking Over Extended Fabrics 12 This example shows three trunking groups (1, 2, and 3); ports 1, 4, and 14 are masters: switch:admin> trunkshow 1: 1 -> 1 10:00:00:60:69:04:10:83 0 -> 0 10:00:00:60:69:04:10:83 2: 4 -> 4 10:00:00:60:69:04:01:94 5 -> 5 10:00:00:60:69:04:01:94 7 -> 7 10:00:00:60:69:04:01:94 6 -> 6 10:00:00:60:69:04:01:94 3:14 -> 14 10:00:00:60:69:04:10:83 15 -> 15 10:00:00:60:69:04:10:83 switch:admin> deskew deskew deskew deskew deskew deskew deskew deskew 16 Master 15 16 Master 15 17 16
12 Troubleshooting Trunking Problems • • • • • • • • • Trunking is not supported in switch interoperability mode. Port trunking is disabled. The port is not an E_Port. The port is not 2 Gbit/sec or 4 Gbit/sec. The port connects to different switches. The ports are not same speed, or they are not set to a valid speed. The ports are not set to the same long distance mode. Local or remote ports are not in same port group.
Troubleshooting Trunking Problems • 12 In Fabric OS v4.4.0 and later, specify a slightly shorter distance for the desired_distance parameter in the portCfgLongDistance command.
12 12-12 Troubleshooting Trunking Problems Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Administering Advanced Zoning 13 This chapter provides procedures for using the Brocade Advanced Zoning feature. Zoning Terminology The following terms are used in the Advanced Zoning procedures: • zone A zone is a region within the fabric where a specified group of fabric-connected devices (called zone members) have access to one another. When zoning is enabled, objects not explicitly defined in a zone are isolated, and members in the zoned fabric do not have access to them.
13 Zoning Concepts Any zone object connected to the fabric can be included in one or more zones. Zone objects can communicate only with other objects in the same zone. For example, consider Figure 13-1, which shows: • • • • • Three zones are configured, named Red, Green, and Blue. Server 1 can communicate only with the Loop 1 devices. Server 2 can communicate only with the RAID and Blue zone devices. Server 3 can communicate with the RAID device and the Loop1 device.
Zoning Concepts Table 13-1 13 Types of Zoning Zone Type Description Storage-based Storage units typically implement LUN-based zoning, also called LUN masking. LUN-based zoning limits access to the LUNs on the storage port to the specific WWN of the server HBA. It is needed in most SANs. It functions during the probe portion of the SCSI initialization. The server probes the storage port for a list of available LUNs and their properties.
13 Zoning Concepts Table 13-2 Approaches to Fabric-Based Zoning Zoning by: Single HBA Zoning by single HBA most closely re-creates the original SCSI bus. Each zone created has only one HBA (initiator) in the zone; each of the target devices is added to the zone. Typically, a zone is created for the HBA and the disk storage ports are added. If the HBA also accesses tape devices, a second zone is created with the HBA and associated tape devices in it.
Zoning Concepts 13 Zone Objects A zone object is any device in a zone, such as the: • • • Physical port number or area ID on the switch Node World Wide Name (N-WWN) Port World Wide Name (P-WWN) Zone objects identified by port number or area number are specified as a pair of decimal numbers in the form d, area (d is the domain ID of the switch and area is the area number on that switch). For example, on SilkWorm 12000 or 24000 models, “4, 46” specifies port 14 in slot number 3 (domain ID 4, area 46).
13 Zoning Concepts The different types of zone configurations are: • • Defined Configuration. The complete set of all zone objects defined in the fabric. • Saved Configuration. A copy of the defined configuration plus the name of the effective configuration, which is saved in flash memory by the cfgSave command. (You can also use the configUpload command to provide a backup of the zoning configuration and the configDownload command to restore the zoning configuration.
Zoning Concepts • 13 Is exclusively enforced through selective information presented to end nodes through the fabric Simple Name Server (SNS). When an initiator queries the name server for accessible devices in the fabric, the name server returns only those devices that are in the same zone as the initiator. Devices that are not part of the zone are not returned as accessible devices.
13 Zoning Concepts Table 13-3 shows the various Brocade switch models, the hardware zoning methodology for each, and tips for best usage. Table 13-3 Enforcing Hardware Zoning Fabric Type Methodology Best Practice SilkWorm 2000series Enables hardware-enforced zoning only on domain, port zones; WWN or mixed zones are not hardware-enforced. Any domain, port zone that overlaps a mixed or WWN zone is not hardware-enforced. Use domain, port identifiers. Do not identify a zone member by its WWN.
Zoning Concepts 13 Figure 13-2 shows a fabric with four nonoverlapping hardware-enforced zones. Figure 13-2 Hardware-Enforced Nonoverlapping Zones WWN_Zone1 Port_Zone1 Port_Zone2 Core Switch WWN_Zone2 Zone Boundaries 22.2b(13.2) Figure 13-3 shows the same fabric components zoned in an overlapping fashion. Figure 13-3 Hardware-Enforced Overlapping Zones WWN_Zone1 Port_Zone1 Port_Zone2 Core Switch Zone Boundaries WWN_Zone2 22.3b(13.
13 Zoning Concepts Figure 13-4 Zoning with Hardware Assist (Mixed-Port and WWN Zones) Port_WWN Zone3 Port_WWN Zone1 Port_WWN Zone2 Core Switch Zone Boundaries Port_WWN Zone4 22.4b(13.4) Figure 13-5 Session-Based Hard Zoning Port_Zone2 Port_Zone1 WWN_Zone1 Core Switch Zone Boundaries WWN_Zone2 22.5b(13.5) In Figure 13-5, only the ports that are overlapped are software-enforced with hardware assist. Rules for Configuring Zones Observe the following rules when configuring zones.
Creating and Managing Zone Aliases 13 Evaluate whether the fabric will also use QuickLoop Fabric Assist (QLFA) or QuickLoop (QL). If you are running Brocade Fabric OS v4.x, consider the following before creating and setting up QLFA zones: • - QuickLoop Zoning. QuickLoop/QuickLoop zones cannot run on switches running Brocade Fabric OS v4.x. However, Brocade Fabric OS v4.x can still manage (create, remove, update) QuickLoop zones on any non-v4.x switch. - QuickLoop Fabric Assist. Brocade Fabric OS v4.
13 Creating and Managing Zone Aliases To create an alias 1. Connect to the switch and log in as admin. 2. Enter the aliCreate command. 3. Enter the cfgSave command to save the change to the defined configuration. Example switch:admin> alicreate “array1”, “2,32; 2,33; 2,34; 4,4” switch:admin> alicreate “array2”, “21:00:00:20:37:0c:66:23; 4,3” switch:admin> alicreate “loop1”, “4,6” switch:admin> cfgsave You are about to save the Defined zoning configuration.
Creating and Managing Zone Aliases 13 Example switch:admin> aliremove “array1”, “1,2” switch:admin> aliremove “array2”, “21:00:00:20:37:0c:72:51” switch:admin> aliremove “loop1”, “4,6” switch:admin> cfgsave You are about to save the Defined zoning configuration. This action will only save the changes on the Defined configuration. Any changes made on the Effective configuration will not take effect until it is re-enabled.
13 Creating and Maintaining Zones Creating and Maintaining Zones Before executing cfgDisable, cfgEnable, or cfgSave, execute the rcsDisabled command to check whether or not your fabric has Reliable Commit Service (RCS) enabled (rcsDisabled=0). If RCS is disabled (rcsDisabled=1), check for older switches in the fabric. After the older switches are upgraded, RCS is enabled by default. RCS is available on all switch versions 4.1 and later.
Creating and Maintaining Zones 13 To remove devices (members) from a zone 1. Connect to the switch and log in as admin. 2. Enter the zoneRemove command. 3. Enter the cfgSave command to save the change to the defined configuration. Example switch:admin> zoneremove “greenzone”, “1,2” switch:admin> zoneremove “redzone”, “21:00:00:20:37:0c:72:51” switch:admin> zoneremove “bluezone”, “4,6; 21:00:00:20:37:0c:66:23 switch:admin> cfgsave You are about to save the Defined zoning configuration.
13 Creating and Maintaining Zones Merging Zones Before linking two switches together, it is important that you know the zone database limit of adjacent switches. For example, when switches running FOS v3.2, v4.4.0, or v5.x discover that the zone merge database is larger than its pre-determined zone database size limit, they issue a reject notification before symmetrically segmenting their own ends of the ISL, thereby preventing the new switch from joining the fabric.
Creating and Maintaining Zones Table 13-5 13 Resulting Database Size: 96K to 128K Receiver FOS v2.6 FOS v3.1 FOS v3.2 FOS v4.0/ v4.1/v4.2 FOS v4.3/ FOS v4.4.0 v5.0.0/ v5.0.1 Fibre Channel Router XPath v7.3 Initiator FOS v2.6/v3.1 Segment Segment Segment Segment Segment Segment Join Segment FOS v3.2 Segment Segment Join Join Join Join Join Join FOS v4.0/v4.1/ Segment v4.2 Segment Segment Join Join Join Join Join FOS v4.3/ v4.4.
13 Creating and Modifying Zoning Configurations Table 13-7 Resulting Database Size: 256K to 1M Receiver FOS v2.6 FOS v3.1 FOS v3.2 FOS v4.0/ v4.1/v4.2 FOS v4.3/ FOS v4.4.0 v5.0.0/ v5.0.1 Fibre Channel Router XPath v7.3 Initiator FOS v2.6/v3.1 Segment Segment Segment Segment Segment Segment Segment Segment FOS v3.2 Segment Segment Segment Segment Segment Segment Segment Segment FOS v4.0/v4.1/ Segment v4.2 Segment Segment Segment Segment Segment Segment Segment FOS v4.3/ v4.
Creating and Modifying Zoning Configurations 13 Example switch:admin> cfgcreate “NEW_cfg”, “redzone; bluezone; greenzone” switch:admin> cfgsave You are about to save the Defined zoning configuration. This action will only save the changes on the Defined configuration. Any changes made on the Effective configuration will not take effect until it is re-enabled. Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] y To add zones (members) to a zoning configuration 1.
13 Creating and Modifying Zoning Configurations To delete a zone configuration 1. Connect to the switch and log in as admin. 2. Enter the cfgDelete command: 3. Enter the cfgSave command to save the change to the defined configuration. Example switch:admin> cfgdelete “testcfg” switch:admin> cfgsave You are about to save the Defined zoning configuration. This action will only save the changes on the Defined configuration.
Creating and Modifying Zoning Configurations 1. Connect to the switch and log in as admin. 2. Enter the cfgShow command with no operands.
13 Creating and Modifying Zoning Configurations To view a configuration in the effective zone database 1. Connect to the switch and log in as admin. 2. Enter the cfgActvShow command.
Creating and Modifying Zoning Configurations 13 5. If you want the change preserved when the switch reboots, save it to nonvolatile (also known as “flash”) memory by entering the cfgSave command. 6. For the change to become effective, enable the appropriate zone configuration using the cfgEnable command. To delete a zone object 1. Connect to the switch and log in as admin. 2. Enter the cfgShow command to view the zone configuration objects you want to delete.
13 Managing Zoning Configurations in a Fabric 3. Enter the zoneObjectRename command to rename zone configuration objects. Note that zone configuration names are case sensitive; blank spaces are ignored switch:admin> zoneObjectRename "White_zone", “Red_zone” 4. Enter the cfgShow command to verify the renamed zone object is present. 5. If you want the change preserved when the switch reboots, save it to nonvolatile (also known as “flash”) memory by entering the cfgSave command. 6.
Managing Zoning Configurations in a Fabric 13 Adding a New Switch or Fabric When a new switch is added to the fabric, it automatically takes on the zone configuration information from the fabric.
13 Managing Zoning Configurations in a Fabric • Objects in adjacent configurations If a zoning object appears in an adjacent defined configuration, but not in the local defined configuration, the zoning object is added to the local defined configuration. The modified zone database must fit in the nonvolatile memory area allotted for the zone database.
Using Zoning to Administer Security 13 Splitting a Fabric If the connections between two fabrics are no longer available, the fabric will segment into two separate fabrics. Each new fabric will retain the same zone configuration. If the connections between two fabrics are replaced and no changes have been made to the zone configuration in either of the two fabrics, then the two fabrics will merge back into one single fabric.
13 Resolving Zone Conflicts After examining the configuration file, you can choose to resolve zone conflicts by using the cfgClear command followed by the cfgDisable command on the incorrectly configured segmented fabric, followed by a portDisable/portEnable command on one of the ISL ports that connects the fabrics. This will cause a merge, making the fabric consistent with the correct configuration. Caution Be careful using the cfgClear command, because it deletes the defined configuration.
Resolving Zone Conflicts Table 13-9 13 Considerations for Zoning Architecture (Continued) Item Description Effect of changes in a production fabric Zone changes in a production fabric can result in a disruption of I/O under conditions where an RSCN is issued as a result of a zone change and the HBA is unable to process the RSCN fast enough. Though RSCNs are a normal part of a functioning SAN, the pause in I/O might not be acceptable.
13 13-30 Resolving Zone Conflicts Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Chapter Administering Advanced Performance Monitoring 14 This topic contains procedures for the Brocade Advanced Performance Monitoring licensed feature: Based on Brocade Frame Filtering technology and a unique performance counter engine, Advanced Performance Monitoring is a comprehensive tool for monitoring the performance of networked storage resources.
14 Administering Advanced Performance Monitoring Table 14-1 lists commands associated with Advanced Performance Monitoring. For detailed information on these commands, refer to the Fabric OS Command Reference Manual. Table 14-1 Advanced Performance Monitoring Commands Command Description perfAddEEMonitor Add an end-to-end monitor to a port. perfAddIPMonitor Add an IP monitor to a port. perfAddReadMonitor Add a SCSI Read monitor to a port.
Displaying and Clearing the CRC Error Count 14 Displaying and Clearing the CRC Error Count You can use the perfShowAlpaCrc command to display the CRC error count for all AL_PA devices or for a single AL_PA on a specific active L_Port.
14 Monitoring End-to-End Performance You can monitor end-to-end performance using the perfMonitorShow command, as described in “Displaying Monitor Counters” on page 14-11. You can clear end-to-end counters using the perfMonitorClear command, as described in “Clearing Monitor Counters” on page 14-14. Note For end-to-end monitors, CRC counters are not displayed on the SilkWorm 200E, 4012, 4100, and SilkWorm 48000 switches.
Monitoring End-to-End Performance 14 Figure 14-1 Setting End-to-End Monitors on a Port SID 0x051200 Switch x Host A Switch y ... Monitor 0 domain 0x05, switch area ID 0x12 AL_PA 0x00 DID 0x111eef ... Dev B Monitor 1 domain 0x11, switch area ID 0x1e AL_PA 0xef Note End-to-end performance monitoring looks at traffic on the receiving port respective to the SID only.
14 Monitoring End-to-End Performance Setting a Mask for End-to-End Monitors End-to-end monitors count the number of words in Fibre Channel frames that match a specific SID/DID pair. If you want to match only part of the SID or DID, you can set a mask on the port to compare only certain parts of the SID or DID. By default, the frame must match the entire SID and DID to trigger the monitor.
Monitoring Filter-Based Performance 14 Example: Setting and displaying an end-to-end mask switch:admin> perfsetporteemask 1/11, “00:00:ff” “00:00:ff” “00:00:ff” “00:00:ff” The EE mask on port 11 is set and EE counters are reset.
14 Monitoring Filter-Based Performance You can monitor filter-based performance using the perfMonitorShow command, as described in “Displaying Monitor Counters” on page 14-11. You can clear filter-based counters using the perfMonitorClear command, as described in “Clearing Monitor Counters” on page 14-14. Adding Standard Filter-based Monitors Table 14-2 lists the commands for adding standard filter-based monitors to a port.
Monitoring Filter-Based Performance • • • 14 Applies the mask to the byte found in the frame. Compares the value with the given values in the perfAddUserMonitor command. Increments the filter counter if a match is found. The following number of offsets can be specified: • SilkWorm 3016, 3250, 3850, 3900, 12000, and 24000 models (Fabric OS v4.0.0 or later) Up to two different offsets per port (one offset when FICON management server mode (FMS) is enabled). • SilkWorm 48000 model (Fabric OS v5.0.
14 Monitoring ISL Performance Two filter-based monitors are added. The first monitor (#5) counts all FCP and IP frames transmitted from domain 0x02 for slot 4, port 2. The FCP and IP protocols are selected by monitoring offset 12, mask 0xff and matching values of 0x05 or 0x08. Domain 2 is selected by monitoring offset 9, mask 0xff, and matching a value of 0x02. The monitor counter is incremented for all outgoing frames from port 2 where byte 9 is 0x02 and byte 12 is 0x05 or 0x08.
Displaying Monitor Counters 14 End-to-end monitors are not supported for ISLs. SilkWorm 3016, 3250, 3850, 3900, 12000, 24000, and 48000 models support eight filter-based monitors for trunks. The SilkWorm 200E, 4012, and 4100 switches support 12 filter-based monitors for trunks. Displaying Monitor Counters Use the perfMonitorShow command to display the monitors on a specified port.
14 Displaying Monitor Counters Example: Displaying end-to-end monitor on a port at an interval of every 6 seconds switch:admin> perfMonitorShow --class EE 4/5 6 perfmonitorshow 53, 6: Tx/Rx are # of bytes and crc is 0 1 2 3 ------------- ------------- ------------- ------------crc Tx Rx crc Tx Rx crc Tx Rx crc Tx Rx ============= ============= ============= ============= 0 0 0 0 0 0 0 0 0 0 0 0 0 53m 4.9m 0 53m 4.9m 0 53m 4.9m 0 53m 4.9m 0 53m 4.4m 0 53m 4.4m 0 53m 4.4m 0 53m 4.4m 0 53m 4.8m 0 53m 4.
Displaying Monitor Counters 14 To display filter-based monitor on a port at an interval of every 6 seconds switch:admin> perfMonitorShow --class FLT 2/5 6 perfmonitorshow 21, 6 0 1 2 3 4 5 6 #Frames #Frames #Frames #Frames #Frames #Frames #Frames --------------------------------------------------------------0 0 0 0 0 0 0 26k 187 681 682 682 494 187 26k 177 711 710 710 534 176 26k 184 734 734 734 550 184 26k 182 649 649 649 467 182 26k 188 754 755 755 567 184 26k 183 716 716 717 534 183 26k 167 657 656 655
14 Clearing Monitor Counters Clearing Monitor Counters Before you clear statistics counters, verify the valid monitor numbers on a specific port using the perfMonitorShow command, to make sure the correct monitor counters are cleared. To clear statistics counters for all or a specified monitor, use the perfMonitorClear command. After the command has been executed, the telnet shell confirms that the counters on the monitor have been cleared.
Saving and Restoring Monitor Configurations 14 To clear statistics counters for an ISL monitor switch:admin> perfMonitorClear --class ISL 1 This will clear ISL monitor on port 1, continue? (yes, y, no, n): [no] y Saving and Restoring Monitor Configurations To save the current end-to-end and filter monitor configuration settings into nonvolatile memory, use the perfCfgSave command: switch:admin> perfcfgsave This will overwrite previously saved Performance Monitoring settings in FLASH ROM.
14 14-16 Collecting Performance Data Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Appendix Configuring the PID Format A Port identifiers (called PIDs) are used by the routing and zoning services in Fibre Channel fabrics to identify ports in the network. All devices in a fabric must use the same PID format, so when you add new equipment to your SAN, you might need to change the PID format on legacy equipment.
A Impact of Changing the Fabric PID Format • core The default for SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 switches and SilkWorm 12000, 24000, and 48000 directors, this is the recommended format for Brocade switches and fabrics. It uses the entire 8-bit address space and directly uses the port number as the area_ID. It supports up to 256 ports per switch.
Impact of Changing the Fabric PID Format A With the introduction of the SilkWorm 200E, 3016, 3250, 3850, 3900, 4012, and 4100 switches and the SilkWorm 12000, 24000, and 48000 directors, the Native PID format used in earlier switches was supplemented with the Core PID format, which is capable of addressing higher port counts. Changing from Native PID format to Core PID format changes the PID, which requires hosts that use port binding to be rebooted.
A Selecting a PID format Table A-1 Effects of PID Format Changes on Configurations (Continued) PID Format Before Change PID Format After Change Configuration Effect? Native Core You must: Core Native • Extended Edge Core Reenable zoning, if there is an active zone set and it uses port zones.
Evaluating the Fabric A eliminate host reboots, and second to minimize the need for a host reboot in the future. Table A-2 PID Format Recommendations For Adding New Switches Existing Fabric OS Versions; PID Format Switch to be Recommendations (in Order of Preference) Added v2.6.2 and later/v3.1.2 and later; Native PID v2.6.2 and later/v3.1.2 and later 1. Use Native PID format for new switch Host reboot is not required. 2.
A Evaluating the Fabric • Determine how any multipathing software will respond to a fabric service interruption If current details about the SAN are already available, it might be possible to skip the Data Collection step. If not, it is necessary to collect information about each device in the SAN. Any type of device might be able to bind by PID; each device should be evaluated before attempting an online update.
Planning the Update Procedure A It is also important to understand how multipathing software reacts when one of the two fabrics is taken offline. If the time-outs are set correctly, the failover between fabrics should be transparent to the users. You should use the multipathing software to manually fail a path before starting maintenance on that fabric. 4. Perform empirical testing. Empirical testing might be required for some devices, to determine whether they bind by PID.
A Planning the Update Procedure Online Update The following steps are intended to provide SAN administrators a starting point for creating sitespecific procedures. 1. Back up all data and verify backups. 2. Verify that the multipathing software can automatically switchover between fabrics seamlessly. If there is doubt, use the software’s administrative tools to manually disassociate or mark offline all storage devices on the first fabric to be updated. 3.
Changing to Core PID Format A 8. Bring the devices online in the order appropriate to the SAN. This usually involves starting up the storage arrays first, and the hosts last. 9. For any devices manually bound by PID, bring the device back online, but do not start applications. Update their bindings and reboot again if necessary. This might involve changing them to the new PIDs, or might (preferably) involve changing to WWN binding. 10.
A Changing to Extended Edge PID Format Example switch:admin> switchdisable switch:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [1] BB credit: (1..27) [16] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (1000..120000) [0] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] SYNC IO mode: (0..1) [0] Switch PID Address Mode: (0..
Changing to Extended Edge PID Format d. Verify that the switches form a single fabric and that all domain IDs do not change after forming the fabric. e. Verify that the number of switches is the same. 3. Disable the switch by entering the switchDisable command. 4. Change the switch configuration in the fabric to Extended Edge PID format. A a. Configure Extended Edge PID (Format 2) on each switch. (See Figure A-1 for a sample configure command on a SilkWorm switch running Fabric OS v3.1.
A Converting Port Number to Area ID Example: Configure Command on a Switch Running Fabric OS 5.0.1 configure Configure... Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [11] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (0..30000) [0] MAX_HOPS: (7..19) [7] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] Switch PID Format: (1..2) [1] 2 Per-frame Route Priority: (0..
Converting Port Number to Area ID A 0 ≤ p < 128 When the port number is greater than or equal to 128, the area ID and port number are the same. Figure A-1 shows a SilkWorm 48000 with Extended Edge PID.
A Converting Port Number to Area ID Table A-4 SilkWorm 48000 With Extended Edge PID ! 31 143 47 159 63 175 79 191 30 142 46 158 62 174 78 190 29 141 45 157 61 173 77 28 140 44 156 60 172 27 139 43 155 59 26 138 42 154 25 137 41 24 136 40 111 223 127 239 15 255 94 206 110 222 126 238 14 254 189 93 205 109 221 125 237 13 253 76 188 92 204 108 220 124 236 12 252 171 75 187 91 203 107 219 123 235 11 251 58 170 74 186
Performing PID Format Changes A Performing PID Format Changes There are several routine maintenance procedures which might result in a device receiving a new PID.
A Performing PID Format Changes Example switch:admin> switchdisable switch:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] yes Domain: (1..239) [1] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] SYNC IO mode: (0..1) [0] Core Switch PID Format: (0..2) [0] 1 Per-frame Route Priority: (0..1) [0] Long Distance Fabric: (0..
Performing PID Format Changes 7. A Export the volume group using vgexport. The proper usage would be vgexport –m . For example: vgexport –m /tmp/jbod_map /dev/jbod 8. Connect to each switch in the fabric 9. Issue the switchDisable command. 10. Issue the configure command and change the Core Switch PID Format to 1. 11. Issue the command cfgEnable [effective_zone_configuration]. For example: cfgEnable my_zones 12. Issue the switchEnable command.
A Performing PID Format Changes 20. Validate that the entry has been removed by using the command ioscan –funC disk. In this example, the NO_HW entry is no longer listed: het46 (HP-50001)> ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ------------------------------------------------------------------------------------disk 0 0/0/1/1.2.0 adisk CLAIMED DEVICE SEAGATE ST39204LC /dev/dsk/clt2d0 /dev/rdsk/c1t2d0 disk 1 0/0/2/1.2.
Swapping Port Area IDs A This command might take several minutes to complete. 13. If you are not using multipathing software, vary on the disk volume groups. The proper usage would be varyonvg . For example: varyonvg datavg 14. If you are not using multipathing software, mount all devices again and restart I/O. For example: mount /mnt/jbod 15. If you are using multipathing software, reenable the affected path. 16. Repeat for all fabrics.
A A-20 Swapping Port Area IDs Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Appendix Configuring Interoperability Mode B This topic provides information on setting up a heterogeneous fabric that includes Brocade switches and switches from other manufacturers. The interoperability mode enables Brocade switches and others to exchange interoperability parameters, allowing their fabrics to merge into one fabric with one principal switch and unique domain IDs. The interopMode command must be executed on all Brocade switches in the fabric.
B Brocade Switch Requirements Brocade Switch Requirements Following are the SilkWorm software requirements: • • • • • • • • 2000-series models must be running Fabric OS v2.6.0 or later. 3000-series models must be running Fabric OS v3.1.0 or later. 3016, 3250, 3850, 3900, 12000, and 24000 models must be running 4.2.0 or later. 4100 model must be running Fabric OS v4.4.0 or later. 4012 model must be running Fabric OS v5.0.0 or later. 200E model running Fabric OS v5.0.1 or later.
Configuration Recommendations • • • • • • • • B QuickLoop Fabric Assist Remote Switch Extended Fabrics Trunking Alias Server Platform Service Virtual Channels FC-IP Configuration Recommendations The following is recommended when configuring an interoperable fabric: • Avoid domain ID conflicts before fabric reconfiguration. Every switch in the fabric must have a unique domain ID.
B Configuration Restrictions • Between Brocade switches, you can connect more than one ISL when in interoperability mode. Zoning Restrictions The following restrictions apply to zoning in interoperable fabrics: • When interoperability mode is in effect, the space available for the zoning database is about half the usual size. The maximum zoning database size in interoperability mode is 1:1.
Enabling and Disabling Interoperability Mode • • • • B Length must be between 1 and 64 characters. All characters must be 7-bit ASCII. The first character must be a letter, which can be either upper case (A-Z) or lower case (a-z). Any character other than the first character must be lower case (a-z), upper case (A-Z), a singledigit number (0-9), dash (-), or underscore (_).
B Enabling and Disabling Interoperability Mode 9. After enabling interoperability mode on all switches, physically connect the non-Brocade switches into the Brocade fabric, one at a time. To disable interoperability mode 1. Connect to the switch and log in as admin. 2. Enter the switchDisable command to disable the switch. 3. Enter the interopmode 0 command to disable interoperability. This command resets a number of parameters and disables interactive mode. 4.
Appendix Using Remote Switch C The Brocade Remote Switch feature, which aids in ensuring gateway compatibility, was formerly a licensed feature. Its functionality is now available as part of the Fabric OS standard feature set through the use of the portCfgIslMode command, which is described in “Linking Through a Gateway” on page 2-17. For those who use Remote Switch as part of their legacy set of tools, this appendix contains a description and procedure for the feature.
C Using Remote Switch Remote Switch can be used for these types of gateway devices: • • • • Fibre Channel over ATM Fibre Channel over IP Fibre Channel over SONET Fibre Channel over DWDM Most of these gateway devices have enough buffers to cover data transfer over a wide area network (WAN). The SilkWorm switches on each side of the gateway must have identical configurations. Only qualified SFPs should be used.
Using Remote Switch C Example This example shows how to modify the data field size and suppress class F traffic on a switch: switch:admin> switchdisable switch:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] yes Domain: (1..239) [3] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] Data field size: (256..2112) [2112] 1000 Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] 1 VC Encoded Address Mode: (0..
C C-4 Using Remote Switch Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Appendix Understanding Legacy Password Behavior D The following sections provide password information for early versions of Fabric OS firmware. Password Management Information The following table describes the password standards and behaviors between various versions of firmware. Table D-1 Account/Password Characteristics Matrix Topic v4.0.0 Number of default 4, chassis based accounts on the switch v4.1.0 to v4.2.0 v4.4.0 to 5.0.
D Password Management Information Table D-1 D-2 Account/Password Characteristics Matrix (Continued) Topic v4.0.0 v4.1.0 to v4.2.0 v4.4.0 to 5.0.1 When connecting to a factory installed switch, do you use the default passwords? Yes Yes Yes Does a user need to know the old passwords when changing passwords using the passwd command? Yes, except when the root user changes another user’s password. This is standard UNIX behavior; Fabric OS does not enforce any additional security.
Password Prompting Behaviors D Password Prompting Behaviors The following table describes the expected password prompting behaviors of various Fabric OS versions. Table D-2 Password Prompting Matrix Topic v4.0.0 v4.1.0 and later Must all password prompts be completed for any change to take effect? No. Partial changes of all four passwords are allowed. No. Partial changes of all four passwords are allowed.
D Password Migration During Firmware Changes Password Migration During Firmware Changes Table D-3 describes the expected outcome of password settings when upgrading or downgrading firmware for various Fabric OS versions. Table D-3 D-4 Password Migration Behavior During Firmware Upgrade/Downgrade Topic v4.2.0 to 5.0.1 v4.4.0 to v5.0.1 Passwords used when upgrading to a newer firmware release for the first time. Default accounts and passwords are preserved.
Password Recovery Options D Password Recovery Options The following table describes the options available when one or more types of passwords are lost. Table D-4 Password Recovery Options Topic v4.0.0 v4.1.0 and later If all the passwords are forgotten, what is the password recovery mechanism? Are these procedures non-disruptive recovery procedures? Contact your switch service provider. A non-disruptive procedure is available. Contact your switch service provider.
D D-6 Password Recovery Options Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Appendix Zone Merging Scenarios E Table E-1 provides information on merging zones and the expected results. Table E-1 Zone Merging Scenarios Description Switch A Switch B Expected Results Switch A with a defined configuration defined: cfg1: zone1: ali1; ali2 effective: none defined: none effective: none Configuration from Switch A to propagate throughout the fabric in an inactive state, because the configuration is not enabled.
E Zone Merging Scenarios Table E-1 Zone Merging Scenarios (Continued) Description Switch A Switch B Expected Results Switch A and Switch B have different defined configurations. Neither have an enabled zone configuration.
Appendix Upgrading Firmware in Single CP Mode F For all SilkWorm switches and directors, the firmwareDownload command, by default, performs a full installation, automatic reboot (autoreboot), and automatic firmware commit (autocommit). Automatic reboot and automatic commit modes are not selectable by default; however, they become selectable when single CP mode is enabled by entering the -s option on the command line.
F Upgrading Firmware in Single CP Mode 4. Enter your user name for the server. 5. Enter the full path to the firmware file on the server; for example: /pub/v5.0.1/release.plist 6. Enter your password. 7. Answer the next prompts as indicated here: Do Auto Commit after reboot [Y]: y If you specify no, you must manually enter the firmwareCommit command. Reboot system after download [N]: y The default is no.
Upgrading Firmware in Single CP Mode F 1. Connect to the switch and log in as admin. 2. Enter the haShow command to determine which CP blade is the active and which one is the standby. In the following example, the active CP blade is CP0, and the standby CP blade is CP1: switch:admin> hashow Local CP (Slot 5, CP0): Active Remote CP (Slot 6, CP1): Standby, Healthy HA enabled, Heartbeat Up, HA State in sync 3. Log in to the standby CP blade as admin. 4.
F Upgrading Firmware in Single CP Mode 12. Reboot the standby CP blade (if you set the option to reboot automatically to no in step 9). 13. Log in to the same CP blade and enter the firmwareDownloadStatus command to verify firmware has downloaded successfully and has either committed or is in the process of doing so. (If you set the option to do auto commit after reboot to no in step 9, you must enter the firmwareCommit command manually.) 14.
Glossary # 8b/10b encoding An encoding scheme that converts each 8-bit byte into 10 bits. Used to balance 1s and 0s in high-speed transports. A ABTS ACC address identifier AL_PA Abort Basic Link Service. Also referred to as “Abort Sequence.” Accept link service reply. The normal reply to an Extended Link Service request (such as FLOGI), indicating that the request has been completed. A 24-bit or 8-bit value used to identify the source or destination of a frame. Refer to S_ID and DID.
area number In Brocade Fabric OS v4.0.0 and above, ports on a switch are assigned a logical area number. Port area numbers can be viewed by entering the switchshow command. They are used to define the operative port for many Fabric OS commands: for example, area numbers can be used to define the ports within an alias or zone. ARR Asynchronous response router. Refers to Management Server GS_Subtype Code E4, which appears in portlogdump command output. ASD Alias server daemon.
broadcast The transmission of data from a single source to all devices in the fabric, regardless of zoning. See also “multicast”, “unicast”. buffer-tobuffer flow control Management of the frame transmission rate in either a point-to-point topology or in an arbitrated loop. See also “BB_Credit”. bypass circuitry Circuits that automatically remove a device from the data path when valid signals are dropped. C CA CAM Certificate authority. A trusted organization that issues digital certificates.
CP Control processor. credit As it applies to Fibre Channel technology, the number of receive buffers available to transmit frames between ports. See also “BB_Credit”. D_ID Destination identifier. A 3-byte field in the frame header, used to indicate the address identifier of the N_Port to which the frame is headed. D defined zone configuration digital certificate disparity DLS The set of all zone objects defined in the fabric. Can include multiple zone configurations.
entry fabric The basic Brocade software license that allows one E_Port per switch. EOF End of frame. A group of ordered sets used to mark the end of a frame. error As it applies to the Fibre Channel industry, a missing or corrupted frame, timeout, loss of synchronization, or loss of signal (link errors). exchange The highest-level Fibre Channel mechanism used for communication between N_Ports. Composed of one or more related sequences, it can work in either one or both directions.
FC-3 Layer of Fibre Channel transport that contains common services used by multiple N_Ports in a node. FC-4 Layer of Fibre Channel transport that handles standards and profiles for mapping upper-level protocols such as SCSI and IP onto the Fibre Channel Protocol. FC-CT Fibre Channel common transport. FC-FG Fibre Channel generic requirements. FC-GS Fibre Channel generic services. FC-GS-2 Fibre Channel generic services, second generation. FC-GS-3 Fibre Channel Generic Services, third generation.
FFFFFD Well-known Fibre Channel address for a fabric controller. FFFFFE Well-known Fibre Channel address for a fabric F_Port. FFFFFF Well-known Fibre Channel address for a broadcast alias ID. Fibre Channel Fibre Channel is a protocol used to transmit data between servers, switches, and storage devices. It is a high-speed, serial, bidirectional, topology-independent, multiprotocol, and highly scalable interconnection between computers, peripherals, and networks.
G G_Port gateway GBIC Gbit/sec Gbyte/sec Generic port. A port that can operate as either an E_Port or an F_Port. A port is defined as a G_Port when it is not yet connected or has not yet assumed a specific function in the fabric. Hardware that connects incompatible networks by providing translation for both hardware and software. For example, an ATM gateway can be used to connect a Fibre Channel link to an ATM connection. Gigabit interface converter.
I I2C Related to internal circuitry on motherboard. [Is this useful?] idle Continuous transmission of an ordered set over a Fibre Channel link when no data is being transmitted, to keep the link active and maintain bit, byte, and word synchronization. in-band Transmission of management protocol over the Fibre Channel. initiator A server or workstation on a Fibre Channel network that initiates communications with storage devices. See also “target”.
L L_Port Loop port. A node port (NL_Port) or fabric port (FL_Port) that has arbitrated loop capabilities. An L_Port can be in either Fabric Mode or Loop Mode. LAN Local area network. A network in which transmissions typically take place over fewer than 5 kilometers (3.4 miles). latency The time required to transmit a frame. Together, latency and bandwidth define the speed and capacity of a link or system. LED Light-emitting diode. Used to indicate the status of elements on a switch.
LR LRR Link reset. A primitive sequence used during link initialization between two N_Ports in point-to-point topology or an N_Port and an F_Port in fabric topology. The expected response is an LRR. Link reset response. A primitive sequence during link initialization between two N_Ports in point-topoint topology or an N_Port and an F_Port in fabric topology. It is sent in response to an LR and expects a response of Idle. M MALLOC Memory allocation. Usually relates to buffer credits.
NOS Not operational. The NOS primitive sequence is transmitted to indicate that the FC_Port transmitting the NOS has detected a link failure or is offline, waiting for the offline sequence (OLS) to be received. NS Name Server. The service provided by a fabric switch that stores names, addresses, and attributes related to Fibre Channel objects. Can cache information for up to 15 minutes. Also known as “Simple Name Server” or as a “directory service.” See also “SNS”.
phantom device A device that is not physically in an arbitrated loop but is logically included through the use of a phantom address. PID Port identifier. PKI Public key infrastructure. An infrastructure that is based on public key cryptography and CA (certificate authority) and that uses digital certificates. See also “CA”, “digital certificate”, “public key cryptography”. PKI certification utility PLOGI point-to-point Public key infrastructure certification utility.
principal switch private key The first switch to boot up in a fabric. Ensures unique domain IDs among roles. The secret half of a key pair. See also “key”, “key pair”. private loop An arbitrated loop that does not include a participating FL_Port. private loop device A device that supports a loop and can understand 8-bit addresses but does not log in to the fabric. private NL_Port An NL_Port that communicates only with other private NL_Ports in the same loop and does not log in to the fabric.
R_RDY R_T_TOV RAID RCS remote switch responder RLS route routing Receiver ready. A primitive signal indicating that the port is ready to receive a frame. Receiver transmitter timeout value, used by receiver logic to detect loss of synchronization between transmitters and receivers. Redundant array of independent disks. A collection of disk drives that appear as a single volume to the server and are fault tolerant through mirroring or parity checking. See also “JBOD”. Reliable Commit Service.
SAN architecture SAN port count The overall design of a storage network solution, which includes one or more related fabrics, each of which has a topology. The number of ports available for connection by nodes in the entire SAN. SCN State change notification. Used for internal state change notifications, not external changes. This is the switch logging that the port is online or is an Fx_port, not what is sent from the switch to the Nx_ports. SCR State change registration.
SNMP Simple Network Management Protocol. An Internet management protocol that uses either IP for network-level functions and UDP for transport-level functions, or TCP/IP for both. Can be made available over other protocols, such as UDP/IP, because it does not rely on the underlying communication protocols. SNS Simple Name Server. SOF Start of frame. A group of ordered sets that marks the beginning of a frame and indicates the class of service the frame will use.
Switched fabric. Multiple N_Ports linked to a switch by F_Ports. Arbitrated loop. Multiple NL_Ports connected in a loop. track changes A Brocade Fabric OS feature that can be enabled to report specific activities (for example, logins, logouts, and configuration task changes). The output from the track-changes feature is dumped to the system message log for the switch.
W WAN watchdog well-known address Wide area network. A software daemon that monitors Fabric OS modules on the kernel. As it pertains to Fibre Channel technology, a logical address defined by Fibre Channel standards as assigned to a specific function and stored on the switch. WWN World Wide Name. An identifier that is unique worldwide. Each entity in a fabric has a separate WWN. zone A set of devices and hosts attached to the same fabric and configured as being in the same zone.
Glossary-20 Fabric OS Administrator’s Guide Publication Number: 53-0000518-09
Index A boot PROMpassword Brocade switch requirements for interoperability Web site 2-8 browser and Java support 3-18 accessing switches and fabrics 3-5 account ID 2-1 account privilege levels 2-3 activating a switch certificate 3-22 ports on demand 2-13 adding a new switch or fabric 13-25 alias members 13-12 and removing FICON CUP licenses 7-14 custom filter-based monitors 14-8 end-to-end monitors 14-4 filter-based monitors 14-8 members to a zone configuration 13-19 standard filter-based monitors 1
command advanced performance monitoring 14-2 chassisshow 2-19 configupload 4-5 fabricshow 2-19 hashow 2-19 licenseadd 2-9 licenseremove 2-10 licenseshow 2-10 nsallshow 2-19 nsshow 2-19 slotshow 2-19 switchshow 2-18 configuration FICON environment switched point-to-point 7-2 FICON environment, cascaded 7-2 high-integrity fabric 7-5 new SilkWorm 24000 with two domains 5-9 recommendations for interoperability B-3 restrictions for interoperability B-3 save to a host 4-1 settings, FICON environment 7-4 configur
13-6 disabling and enabling a port 2-12 disabling and enabling a switch 2-12 disabling and enabling cards 5-3 disabling interoperability mode B-6 disabled zone configuration displaying CRC error count 14-3 end-to-end mask 14-6 node identification data, FICON environments 7-7 registered listeners for link incidents, FICON environment 7-7 displaying additional help topics 1-4 displaying and clearing the CRC error count 14-3 displaying and deleting certificates displaying command help 7-12 fabric high integ
filter-based monitors 14-7 adding 14-8 deleting 14-10 restoring configuration 14-15 saving configuration 14-15 firmware download 4-7 frame transfer with brocade remote switch fru failures identifying ports 5-1 by port area ID 5-2 IDID 7-1 C-1 7-7 IDID mode enabling and disabling in a FICON environment 7-6 impact of changing the fabric PID format A-2 inaccurate information in the system message log fru failures, monitoring in FICON environments 7-3, 7-7 10-23 initializing trunking on ports insistent
linking through a gateway 2-17 listing link characteristics 12-9 offline update A-8 online update A-8 login switch 2-1 long distance ISLs optimizing resources through zoning LUN masking P 11-2 13-3 LWL ISL Trunking support for password 2-1 boot prom 3-34 default 2-4 password management information 12-1 M 13-1 D-1 password migration during firmware changes maintaining configurations maintaining firmware 4-1 password prompting behaviors D-3 4-5 D-5 maintaining licensed features 2-8 passw
ports identifying by port area ID 5-2 identifying by slot and port number status of 9-5 ports, swapping 7-8 routing policies rules for configuring zones preparing a switch S 5-3 saved zone configuration 13-6 7-4 saving and restoring monitor configurations 14- printing hard copies of switch information 4-5 15 privileges in accounts 2-3 saving monitor configuration procedural differences between fixed-port and variable-port switches 1-1 scope and references public key infrastructure encryption
12-2 static PID mapping errors A-3 static route 6-3 storage-based zoning 13-3 summary of PID formats A-1 summary of SSL procedures 3-19 supported brocade features B-2 supportsave command 9-14 swapping port area IDs A-19 swapping ports 7-8 standard trunking criteria upgrading SilkWorm 3016, 3250, 3850, 3900, and 4100 switches 4-8 user-defined filter-based monitors 14-8 using dynamic load sharing 6-4 using FICON CUP using legacy commands for SNMPv1 3-30 using the snmpconfig command V 7-4 switch names 2-10
Z zone adding members 13-14 adding switches 13-25 creating 13-14 creating a configuration 13-18 deleting 13-15 deleting a configuration 13-20 removing members 13-15 viewing 13-15 viewing configurations 13-22 zone aliases 13-5 zone configuration adding members 13-19 removing members 13-19 zone configurations 13-5 zone name restrictions B-4 13-5 zone types 13-2 zone objects zoning administering security 13-27 zoning and PDCM considerations 7-15 13-2 zoning enforcement 13-6 zoning restrictions B-4 zoning sc
