53-1001188-01 November 24, 2008 Fabric Watch Administrator’s Guide Supporting Fabric OS v6.2.
Copyright © 2008 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the Brocade B weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm, and StorageX are registered trademarks and the Brocade B wing logo and Tapestry are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U.S. and other countries.
Document History Title Publication Number Summary of Changes Date Fabric Watch User’s Guide 53-0001559-02 New document May 2000 Fabric Watch User’s Guide 53-0000198-02 n/a January 2002 Fabric Watch User’s Guide 53-0000186-02 n/a March 2002 Fabric Watch User’s Guide 53-0000504-02 n/a April 2003 Fabric Watch User’s Guide 53-0000524-02 n/a April 2003 Fabric Watch User’s Guide 53-0000524-03 Updated default values and restructured the document.
Title Publication Number Summary of Changes Date Fabric Watch Administrator’s Guide 53-1000438-01 Updates to support Fabric OS v5.3.0, implementation of IPV6. June 2007 Fabric Watch Administrator’s Guide 53-1000601-01 Updates to support Fabric OS v6.0.0 September 2007 Fabric Watch Administrator’s Guide 53-1000601-02 Updates to support Fabric OS v6.1.0 March 2008 Fabric Watch Administrator’s Guide 53-1000601-03 Updates to support Fabric OS v6.2.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xvi What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 Notification methods In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Fabric Watch notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Event configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Event behavior types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Threshold configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Selecting the class and area. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring thresholds for classes and areas . . . . . . . . . . . . . . 59 Configuring port fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Advanced configuration options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Changing the threshold boundary level . . . . . . . . . . . . . . . . .
Appendix B Port fencing types Index Fabric Watch Administrator’s Guide 53-1001188-01 ix
x Fabric Watch Administrator’s Guide 53-1001188-01
Figures Figure 1 Threshold monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 2 A buffered data region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 3 Time base set to none . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Figure 4 Event trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii Fabric Watch Administrator’s Guide 53-1001188-01
Tables Table 1 Product Name classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Table 2 Environment class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 3 Fabric class areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 4 FRU class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv Fabric Watch Administrator’s Guide 53-1001188-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii • Additional information . . . . . . . . . . . . .
• Appendix B, “Port fencing types,” lists the set of port fencing types that are available with Brocade Fabric OS version 6.2. • The index points you to the exact pages on which specific information is located. Supported hardware and software This document is specific to Brocade Fabric OS version 6.2.0 and all switches running Fabric OS version 6.2.
What’s new in this document The following Information was added: • Virtual Fabric Support • Ability to monitor switch health on 8 logical switches. • Ability to configure thresholds and alarm matrix for ports belonging to a particular logical switch. • Port Movement Support • Ability to monitor a port moving from one logical switch to another. • Link Reset Monitoring • New Link Reset area added to Port, E_Port, and F/FL class. • Ability to monitor the number of link resets happening on a link.
Document conventions This section describes text formatting conventions and important notices formats.
Key terms For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at http://www.snia.org/education/dictionary. Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources To get up-to-the-minute information, join Brocade Connect. It’s free! Go to http://www.brocade.
Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1.
Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.com Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xxii Fabric Watch Administrator’s Guide 53-1001188-01
Chapter 1 About Fabric Watch In this chapter • Fabric health concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Watch overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Watch alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Watch event notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Watch audit messages. .
1 Fabric Watch overview Fabric Watch overview Fabric Watch is an optional storage area network (SAN) health monitor that allows you to enable each switch to constantly monitor its SAN fabric for potential faults and automatically alerts you to problems long before they become costly failures. Fabric Watch tracks a variety of SAN fabric elements, events, and counters.
Fabric Watch alarm notifications 1 Fabric Watch alarm notifications Fabric Watch provides the following types of automatic notifications: • A continuous alarm provides a warning message whenever a threshold is breached; it continues to send alerts until the condition is corrected. For example, if a switch exceeds its temperature threshold, Fabric Watch activates an alarm at every measurement interval until the temperature returns to an acceptable level.
1 Fabric Watch audit messages Fabric Watch audit messages Fabric Watch events caused by configuration value changes are tagged as Audit messages. NOTE Audit messages are generated for port fencing configuration changes, whether port fencing is enabled or disabled. You can set up an external host to receive Audit messages so you can easily monitor unexpected changes. For information on error messages generated by Fabric Watch, see the Fabric OS Message Reference.
Switch policies 1 Switch policies Switch policies are a series of rules that define specific health states for the overall switch. Fabric OS interacts with Fabric Watch using these policies. Each rule defines the number of types of errors that transitions the overall switch state into a state that is not healthy. For example, you can specify a switch policy so that if a switch has two port failures, it is considered to be in a marginal state; if it has four failures, it is in a down state.
1 Port fencing Port fencing A port that is consistently unstable can harm the responsiveness and stability of the entire fabric and diminish the ability of the management platform to control and monitor the switches within the fabric. Port Fencing is a Fabric Watch enhancement that takes the Port class, E_Port class, F/FL_Port class, and Link Reset ports offline if the user-defined thresholds are exceeded. NOTE Port Fencing is not enabled by default. You must manually enable Port Fencing.
Chapter Fabric Watch Best Practices 2 In this chapter • Fabric Watch default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 • Reasons to customize Fabric Watch settings . . . . . . . . . . . . . . . . . . . . . . . . . 7 • Configuration decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Fabric Watch default settings A default Fabric Watch configuration is available for the purpose of saving setup time.
Configuration decisions Configuration decisions Before you begin an implementation, make some decisions surrounding the following major configuration tasks. Monitoring Do you want to monitor all class areas, or implement the monitoring in incremental stages? Refer to Chapter 3, “Fabric Watch components,” for a description of all configurable Fabric Watch classes and areas.
Configuration decisions Thresholds Before you begin to configure thresholds, decide if you want to have different levels of alerts for E_ports and F/FL_Ports and configure the ports individually. Always set up thresholds one fabric at a time and test the configuration before you apply the threshold configuration to more switches or fabrics.
Configuration decisions Notification methods Fabric Watch alerts can be sent using one of the following notification methods, which are described in detail in “Fabric Watch event notifications” on page 3. We recommend using either SNMP trap alerting to your system management console or event log entry in conjunction with Syslog forwarding configured on your switches.
Chapter 3 Fabric Watch components In this chapter • Fabric Watch classes, areas, and elements . . . . . . . . . . . . . . . . . . . . . . . . . • Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Classes Table 1 describes the classes into which Fabric Watch groups all switch and fabric elements. TABLE 1 12 Product Name classes Class Description Environment Includes information about the physical environment in which the switch resides and the internal environment of the switch. For example, an Environment-class alarm alerts you to problems or potential problems with temperature and power.
Areas 3 Areas While classes represent large groupings of information, areas represent the information that Product Name monitors. For example, switch temperature, one of the values tracked by Fabric Watch, is an area within the class Environment. The tables in this section describe all of the areas monitored by Fabric Watch, organized by their associated classes. Environment class areas Table 2 lists and describes the Product Name areas in the Environment class.
3 Areas TABLE 3 Fabric class areas (Continued) Area Description Segmentation Changes Tracks the cumulative number of segmentation changes. Segmentation changes occur because of one of the following: • Zone conflicts. • Incompatible link parameters. During E_Port and VE_Port initialization, ports exchange link parameters, and incompatible parameters result in segmentation. This is a rare event. • Domain conflicts. • Segmentation of the principal link between two switches.
Areas 3 Performance Monitor class areas Table 5 lists Product Name areas in the Performance Monitor class and describes each area. TABLE 5 Performance Monitor class areas Area Indicates Customer Define Values for customer-defined performance areas. For more information on this area, see the Fabric OS Command Reference. Invalid Cyclic Redundancy Checks (CRC) Errors have been detected in the Fibre Channel frame.
3 Areas TABLE 6 Port class areas (Continued) Area Indicates State Changes The state of the port has changed for one of the following reasons: The port has gone offline. The port has come online. The port is testing. The port is faulty. The port has become an E_Port, EX_Port, VE_Port, or VEX_Port. The port has become an F/FL_Port. The port has segmented. The port has become a trunk port. • • • • • • • • Transmit (TX) Performance The percentage of maximum bandwidth consumed in packet transmissions.
Areas TABLE 8 3 Security class areas (Continued) Area Indicates Invalid Timestamps Invalid timestamps which occur if a time interval becomes too great from the time a packet is sent to the time it is received, and the switch rejects it. Login Violation Login violations which occur when a secure fabric detects a login failure. MS Violation MS (Management Server) violations which occur when an access request reaches a secure switch from an unauthorized WWN (World Wide Name).
3 Elements SFP class areas Table 9 lists Product Name areas in the SFP class and describes each area. NOTE SFPs connected to GbE ports are not monitored. TABLE 9 SFP class areas Area Description Temperature Measures the physical temperature of the SFP, in degrees Celsius. A high temperature indicates that the SFP might be in danger of damage. Receive Power Measures the amount of incoming laser, in µwatts, to help determine if the SFP is in good working condition.
Chapter Fabric Watch thresholds 4 In this chapter • Threshold values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 • Time bases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 • Threshold event settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Threshold values FIGURE 1 Threshold monitoring Figure 2 shows how to limit the number of event notifications using a buffer. When you specify a buffer, events cannot occur below the high threshold and above the low threshold. Event notification occurs only where the arrows indicate. The event criteria are continued to be met until the data sensed falls below the low threshold value or above the high threshold value.
Time bases 4 Time bases Time bases are time periods within Fabric Watch. This configurable field impacts the comparison of sensor-based data with user-defined threshold values. Time base set to none If you set a time base to none, Fabric Watch compares a data value against a threshold boundary level. When the absolute value of the measuring counter exceeds the threshold boundary, an event is triggered. Figure 3 shows a high limit of 65 degrees Celsius placed on a counter measuring temperature.
4 Time bases Example1: Triggering an event Figure 4 shows a sample graph of data obtained by Fabric Watch (the type of data is irrelevant to the example). A high threshold of 2 is specified to trigger an event. A time base of minute is defined. An event occurs only if the rate of change in the specific interval (one minute in this example) is across the threshold boundary. It should be either higher than the high threshold limit or lower than the low threshold limit.
Threshold event settings FIGURE 5 4 Example without an event Threshold event settings This section describes how Fabric Watch compares a fabric element’s data value against a threshold value to determine whether or not to trigger an event. It describes how a specified buffer zone affects event triggering. For Fabric Watch to monitor data values for one of the following conditions, the alarm setting must be set to a nonzero value.
4 Threshold event settings FIGURE 6 Above event trigger with buffer zone Below event trigger The Below event trigger generates an event when a data value becomes less than the low threshold boundary. When a buffer is defined, the event will be triggered only when the value goes below the lower threshold. A second event will not be generated until the value crosses the buffer region set above the lower threshold.
Threshold event settings 4 In-between event triggers Fabric Watch event triggers are usually set to notify the user of a warning or failure condition, but there is an exception. You can define the In-Between event trigger to receive a notification of fault recovery. For example, when measuring port performance, crossing the high threshold triggers an Above threshold event, which displays a warning message. The threshold might be crossed for a period so brief that is not a true cause for an alarm.
4 26 Threshold event settings Fabric Watch Administrator’s Guide 53-1001188-01
Chapter Notification methods 5 In this chapter • Fabric Watch notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 • Event configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Fabric Watch notification Fabric Watch provides the following notification methods, but not all notification methods can be applied to all of the classes.
5 Fabric Watch notification An SNMP trap forwards the following information to an SNMP management station: • • • • • • Name of the element whose counter registered an event Class, area, and index number of the threshold that the counter crossed Event type Value of the counter that exceeded the threshold State of the element that triggered the alarm Source of the trap The trap stores event information but does not actively send alerts. Port changes do not generate SNMP traps.
Event configuration 5 NOTE To send e-mail alerts, the switch must be connected to a DNS server. Use the dnsConfig command to configure DNS settings. In case a DNS server is not available, e-mails can be forwarded through a relay host. The relay host IP can be configured using the fwMailCfg command. Enabling e-mail alerts for the Changed threshold state in several areas can quickly result in a significant amount of e-mail.
5 30 Event configuration Fabric Watch Administrator’s Guide 53-1001188-01
Chapter Activating Fabric Watch 6 In this chapter • Interfaces for activating Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Interfaces for activating Fabric Watch This section provides a brief overview of the available user interfaces for activating Fabric Watch. Further details about Fabric Watch operations for each interface are provided later in this guide.
6 Interfaces for activating Fabric Watch If the Fabric Watch license is not listed, continue to step 4; otherwise, you are ready to use Fabric Watch. 4. Enter the license key with the licenseAdd key command, where key is the Fabric Watch license key. License keys are case-sensitive, so type the license key exactly as it appears. switch:admin> licenseadd "R9cQ9RcbddUAdRAX" 5. Enter the licenseShow command to verify successful activation.
Interfaces for activating Fabric Watch 6 Fabric Watch and SNMP You can integrate Fabric Watch with existing enterprise systems management tools, such as SNMP. The Fabric Watch Management Information Base (MIB) lets system administrators configure fabric elements, receive SNMP traps generated by fabric events, and obtain the status of fabric elements through SNMP-based enterprise managers. NOTE The following instructions apply to the AdvantNet MIB browser.
6 Interfaces for activating Fabric Watch 6. Start a Telnet session, and enter the snmpConfig -set mibcapability command at the prompt to set the SNMP MIB capability. NOTE Currently, setting the SNMP MIB capability can only be done from the CLI.
Interfaces for activating Fabric Watch 6 Trap Recipient's IP address in dot notation: [0.0.0.0] Community (ro): [FibreChannel] Trap Recipient's IP address in dot notation: [0.0.0.
6 Interfaces for activating Fabric Watch FIGURE 10 Example OID tree 11. Obtain the specific identifier for the element that will be modified. To get the identifier, click the swFwThresholdTable and swFwThresholdEntry directory, and run a get operation on swFwName. A list of elements appears in which each element is preceded by an identifier. Remember the numeric portion of the identifier, which appears before the “==>” symbol.
Interfaces for activating Fabric Watch FIGURE 11 6 Example swFwName screen In this example, 83.1 is the numeric identifier for the element referenced as resFlash000. Traverse the fields beneath swFwClassAreaTable and swFwThresholdTable, appending the numeric identifier from the previous step to each field before performing a get or write operation. For example, to get and modify information specific to the resFlash000 element, select one of the fields and append “83.
6 38 Interfaces for activating Fabric Watch Fabric Watch Administrator’s Guide 53-1001188-01
Chapter 7 Fabric Watch default settings In this chapter • Fabric Watch default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Environment class default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric class default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Performance Monitor class default settings . . . . . . . . . . . . . . . . . . . . . . . . . • Port class default settings . . . . . . .
7 Class default settings Environment class default settings Table 10 provides default Environment class settings for all switches. Check the appropriate hardware reference manual for differences in actual environmental requirements. NOTE Fabric Watch no longer supports fan monitoring. Event Manager (EM) now manages fan monitoring and the switch status is calculated based on the fan status reported by EM.
Class default settings TABLE 10 Area 7 Environment class default settings (Continued) Description Default threshold settings Default alarm settings Threshold state Brocade 48000 Low: 0 High: 60 Buffer: 10 Brocade DCX Low: 0 High: 70 Buffer: 10 Brocade DCX-4S Low: 0 High: 70 Buffer: 10 Power Supply Fabric Watch Administrator’s Guide 53-1001188-01 Monitors power supply condition Time Base: None Low: 1 High: 0 Buffer: 0 Informative Out-of-range In-range Informative Changed: 0 Below: 3 Above: 3 In-Be
7 Class default settings TABLE 10 Environment class default settings (Continued) Area Description Default threshold settings Default alarm settings Threshold state Fan Monitors switch fan speed in RPMs Unit: RPM Time Base: none Changed: 0 Above: 3 Below: 3 In-Between: 1 Informative Out_of_range Out_of_range In-range Brocade 300 Low: 2500 High: 13000 Buffer: 3 Brocade 4100 Low:3000 High: 12000 Buffer: 3 Brocade 4900 Low: 4100 High: 8500 Buffer: 3 Brocade 5000 Low:3000 High: 12000 Buffer: 3 Broc
Class default settings 7 Fabric class default settings Table 11 provides default settings for areas in the Fabric class.
7 Class default settings Performance Monitor class default settings Table 12 provides default settings for areas in the AL_PA Performance Monitor class.
Class default settings 7 Port class default settings Table 15 provides default settings (per minute) for areas in the Port class.
7 Class default settings TABLE 15 Area 46 Port class default settings (Continued) Description Default threshold settings Default alarm settings Threshold state Receive Performance Monitors receive rate, Unit: Percentage (%) by percentage Time Base: minute Low: 0 High: 100 Buffer: 0 Changed: 0 Below: 0 Above: 0 In-Between: 0 Informative Informative Informative Informative State Changes Monitors state changes Changed: 0 Below: 0 Above: 0 In-Between: 0 Informative Informative Out_of_range In_rang
Class default settings 7 E_Port class default settings Table 16 provides default settings for areas in the E_Port class.
7 Class default settings TABLE 16 E_Port class default settings (Continued) Area 48 Description Default threshold settings Default alarm settings Threshold state Receive Performance Monitors the receive rate, by percentage Unit: Percentage (%) Time Base: minute Low: 0 High: 100 Buffer: 0 Changed: 0 Below: 0 Above: 0 In-Between: 0 Informative Informative Informative Informative State Changes Monitors state changes Unit: Changes Time Base: minute Low: 0 High: 5 Buffer: 0 Changed: 0 Below: 0 A
Class default settings 7 F/FL_Port class default settings Table 17 provides default settings for areas in the F/FL_Port class.
7 Class default settings TABLE 17 F/FL_Port class default settings (Continued) Area Description Loss of Signal Count Link Reset Monitors the number of link resets sent by a given port (LR-Out) and received on a given port (LR-In).
Class default settings 7 Security class default settings Table 19 provides default settings for areas in the Security class.
7 Class default settings TABLE 19 52 Security class default settings (Continued) Area Description Default threshold settings Default alarm settings Threshold state Login Violations Monitors login violations Unit: Violations Time Base: minute Low: 1 High: 2 Buffer: 0 Changed: 0 Below: 0 Above: 3 In-Between: 0 Informative Informative Out_of_range In_range MS Violations Monitors MS violations Unit: Violations Time Base: minute Low: 1 High: 2 Buffer: 0 Changed: 0 Below: 0 Above: 3 In-Between: 0
Class default settings TABLE 19 Security class default settings (Continued) Area Description Default threshold settings Default alarm settings Telnet Violations Monitors Telnet violations Unit: Violations Time Base: minute Low: 1 High: 2 Buffer: 0 Changed: 0 Below: 0 Above: 3 In-Between: 0 Informative Informative Out_of_range In_range TS Out of Sync Monitors instances in Unit: Violations which the timestamp is Time Base: minute Low: 1 out of sync High: 2 Buffer: 0 Changed: 0 Below: 0 Above: 3 I
7 Class default settings SFP class default settings Table 20 provides default settings for areas in the SFP class. NOTE SFPs connected to GbE ports are not monitored.
Chapter 8 Fabric Watch Configurations In this chapter • Fabric Watch configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Threshold configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Advanced configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Notification configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 Fabric Watch configuration Configuration files When you activate Fabric Watch, it uses the default settings described in “Fabric Watch Best Practices” on page 7. You cannot alter these default settings; if the default values do not suit your specific needs, configure Fabric Watch to use more appropriate settings. When you configure the new settings for Fabric Watch, your switch stores the settings in the configuration file.
Threshold configuration 8 Threshold configuration Before you configure thresholds, you must first identify and select the appropriate class and areas, If you want a basic configuration, accept the default configuration settings. Selecting the class and area During your planning activities, you should determine exactly which elements or monitors you want to configure, and in which class they reside. After you have made this decision, you need to identify the classes. 1.
8 Threshold configuration 3. Type the number from the list that corresponds to the class that you want to configure. For example, if you type 5, the menu corresponding to the E_Port class displays. 1 : Link loss 2 : Sync loss 3 : Signal loss 4 : Protocol error 5 : Invalid words 6 : Invalid CRCS 7 : RXPerformance 8 : TXPerformance 9 : State Changes 10 : return to previous page Select an area => : (1..
Threshold configuration 8 where: Index A numeric identifier assigned to the element ThresholdName A string identifier assigned to the element Port The user port number CurVal The current data value contained by the element Status Monitoring status, either enabled or disabled LastEvent The last event setting that triggered an event.
8 Threshold configuration Disabling a threshold configuration To stop monitoring a selected option, use the disable a threshold option, as follows: 1. Type 2 at the Select choice => prompt. The system generates output, which varies based on the class and area you selected. 2. Type the index number of the element for which Fabric Watch should disable monitoring. Fabric Watch redraws the element table with the selected element disabled.
Threshold configuration 8 Select threshold index => : (216..
8 Threshold configuration 3. Type the number from the list that corresponds to the class that you want to configure. Select 3 for Port class, 5 for E_Port class, or 6 for F/FL Port (Optical) class. For each class that you select, Fabric Watch provides a list of the areas of the class available for configuration. 4. Select an area (areas 1 - 2 and 4 - 6 are available for Port Fencing).
Threshold configuration 8 8. Verify that the alarm matrix displays the Above Custom as 32, and then change the Threshold alarm level to custom by typing 11. 1 : change behavior type 11 2 : change behavior interval 12 3 : change threshold boundary level 13 4 : change custom unit 14 5 : change custom time base 15 6 : change custom low 16 7 : change custom high 17 8 : change custom buffer 18 9 : apply threshold boundary changes 10 : cancel threshold boundary changes Select choice => : (1..
8 Threshold configuration 12. Change the Threshold boundary level to custom by typing 3, and then select custom by typing 2 at the Enter boundary level type.
Advanced configuration options 8 Advanced configuration options To customize Fabric Watch monitoring to suit your environment, use the advanced configuration options, which are listed in Table 21. Table 21 describes the customization options displayed at the end of the Advanced Configuration menu. With the exception of the last option, which exits advanced configuration mode, each option has similar behavior.
8 Advanced configuration options TABLE 21 Advanced configuration options Option Effect Input information change above alarm Changes the notification method for above event occurrences for this method, but only affects the custom column. The required notification methods change below alarm Changes the notification method for below event occurrences for this method, but only affects the custom column.
Advanced configuration options 8 Changing the threshold boundary level NOTE The allowed advanced settings are displayed on a per-class basis. Although Port Fencing is displayed for other areas, such as RX Performance, for which Port Fencing is not supported, you will not be able to set or apply the changes on such areas. 1. Type 4 at the Select choice => prompt. The system generates output, which varies based on the class and area you select.
8 Advanced configuration options where: Index A numeric identifier assigned to the element ThresholdName A string identifier assigned to the element BehaviorType Frequency of alarm notifications BehaviorInt The element behavior interval, in seconds 2. Refer to the following system output to customize high threshold boundary for RXPerformance. The threshold boundary section of the Advanced Configuration menu includes the threshold information for the selected area.
Advanced configuration options 8 3. Type 3 at the Select choice => prompt to change the threshold boundary level, and then type 2 at the Enter boundary level type = > prompt to specify that this is a custom value, as shown in the following system output.
8 Advanced configuration options Changing the behavior type There are two behavior types: • Triggered A triggered behavior type signals you once after a threshold has been crossed. Triggered is the default behavior type signal for all class areas. • Continuous A continuous behavior type signals you continuously after a threshold has been crossed.
Notification configuration 8 Notification configuration You can be notified of an alarm condition through a notification. There are a number of methods through which you can be notified and they are discussed in this section. Alarm notification configuration Alarms act as a signal or alert that notifies you when a threshold has been crossed. NOTE The allowed alarm types are displayed on a per-class basis.
8 Notification configuration Notification value configuration You can specify a particular notification method that you want Fabric Watch to use by assigning it a value. The value is the sum of the alarm matrix values; for example, PortFencing-32, SnmpTrap-2, and Errlog-1 (32+2+1=35). Table 22 shows the numerical values for each notification method.
Notification configuration 8 Errlog-1, SnmpTrap-2, PortLogLock-4 RapiTrap-8, EmailAlert-16 PortFencing - 32 Valid alarm matrix is 63 Enter above alarm matrix => : (0..
8 Notification configuration 220 221 222 223 eportRXPerf220 eportRXPerf221 eportRXPerf222 eportRXPerf223 Triggered Triggered Triggered Triggered 1 1 1 1 Threshold boundary level is setat : Custom DefaultCustom Unit Percentage(%) Time base minuteminute Low 0 0 High 100 80 BufSize 0 0 Percentage(%) Threshold alarmlevel is set at: Custom . . . 4. Type 16 at the Select choice => prompt to apply the threshold alarm level changes. Unless you apply the value, it does not take effect.
Notification configuration 8 API notification configuration In the Brocade Fabric OS API, notifications are triggered programatically. The Brocade Fabric OS API is an application programming interface (API) that provides the method for any application to access critical information about a Brocade SAN. Using Fabric OS API, an application can query or control individual switches or the entire fabric. You can also configure API notifications using the Brocade Fabric OS API.
8 Notification configuration Showing mail configuration information 1. Type 1 in the fwMailCfg menu to view the current e-mail configuration classes. The Config Show menu displays.
Notification configuration 8 Enabling an e-mail alert 1. Type 3 in the fwMailCfg menu to enable e-mail alert for a specific class. The Config Show menu displays. 2. Select a class for which Fabric Watch should enable e-mail alerts. The following confirmation message displays: Email Alert is enabled! If the class does not have an e-mail configuration (there is no e-mail address assigned to the class), the following error message displays: Mail configuration for class Environment is not done.
8 Notification configuration Setting recipient mail address for e-mail alert 1. Type 5 in the fwMailCfg menu to specify the recipient to whom Fabric Watch should send the e-mail alert for a class. The configShow menu displays. 2. Select a class. The following prompt displays: Mail To: [NONE] Enter the e-mail address of the person responsible for the specific class of alerts. Fabric Watch uses the default value, located between the brackets in the prompt, as the current e-mail address for the class.
Switch status policy configuration 8 Removing the relay host configuration 1. Type 6 in the fwMailCfg menu to display the relay host configuration menu. 1 2 3 4 Display Relay Host configuration Set Relay Host IP Remove Relay Host configuration Quit 2. Type 3 to remove the configuration. Switch status policy configuration The switch status policy monitors the overall status of a switch based on several contributing parameters.
8 Switch status policy configuration Switch status policy planning Before entering the switchStatusPolicySet command, plan your switch status policy. Determine your system requirements and the factors that affect its monitors. Table 23 lists the monitors in a switch and identifies the factors that affect their health. Note that not all switches use the listed monitors.
Switch status policy configuration 8 Implementing your switch status policy After you planned and defined your switch status policy, implement it using the following procedure. 1. Enter the switchStatusPolicySet command to configure each policy. Each policy has two parameters that can be configured: Marginal and Down. 2. Set the number of units Marginal or Down based on your system requirements for each policy or parameter.
8 FRU configuration FRU configuration The configuration of FRUs is an exception to the procedures described thus far in this chapter. FRUs are monitored using state values, as opposed to the quantitative values used to monitor the rest of the fabric. As a result of the qualitative nature of this monitoring, the concept of thresholds does not apply. 1. Establish a Telnet connection with a switch. 2. Log in using administrative privileges. 3. Enter the fwFruCfg command at the command prompt.
FRU configuration 8 Specifying triggers for alarms You can specify triggers for any number of alarm states or alarm actions. The first prompt enables you to select which FRU states trigger events. 1. Add the numbers beside each state (for the states you want to include). 2. Enter the total at the prompt. For example, to trigger events using the Absent, Off, and Faulty states, add the assigned values and enter that value at the prompt.
8 84 FRU configuration Fabric Watch Administrator’s Guide 53-1001188-01
Chapter 9 Fabric Watch Reports In this chapter • Fabric Watch reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Fabric Watch reports You can run reporting commands in Fabric Watch to get instant access to switch information. Although the switchShow command provides basic switch information, the Fabric Watch reports provide detailed information, which enables you to track marginal or faulty ports that can affect throughput or switch performance.
9 Switch Availability Monitor (SAM) report Switch Availability Monitor (SAM) report The switch availability monitor (SAM) report lets you see the uptime and downtime for each port. It also enables you to check if a particular port is failing more often than the others. NOTE SAM report details do not display the health status of GbE ports. Fabric Watch only monitors and reports the status for physical and virtual FC ports.
Switch Health report 2/11 2/12 2/13 2/14 2/15 3/0 3/1 3/2 3/3 3/4 3/5 3/6 3/7 3/8 3/9 3/10 . . . T LB LB U LB T U U U U U U U U U VE 100 100 100 0 100 100 0 0 0 0 0 0 0 0 0 100 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 0 0 0 100 0 0 100 100 100 100 100 100 100 100 100 0 Switch Health report The Switch Health report lists the following information: • Current health of each port, based on the currently-configured policy settings.
9 Switch Status Policy report WWN servers monitor Standby CP monitor Standby CP monitor Core blade monitor Blades monitor Flash monitor Marginal ports monitor Faulty ports monitor Missing SFPs monitor HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY All ports are healthy The final portion of the report, detailing port health, is not available without a Fabric Watch license. Switch Status Policy report The Switch Status Policy report displays the current policy parameter.
Port Detail report 9 Port Detail report If the Switch Health report shows marginal throughput or decreased performance, use the Port Detail report to see statistics on each port. The Port Detail report is a Fabric Watch licensed product. You can also see port details by health. For example, you can see only healthy ports, only marginal ports, only faulty ports, or only offline ports. The following is an example of a Port Detail report.
9 Port Detail report 216 217 218 219 220 221 222 223 VE VE VE VE VE VE VE VE HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY HEALTHY 061:19 061:19 061:19 003:37 002:48 061:19 061:19 061:19 - - - - - - - - - - - - - NOTE Output of the Port Detail Report depends on the ports that belong to the current Admin Domain context. If a port does not belong to the current Admin Domain, nothing other than port number is displayed for that port.
Appendix A Fabric Watch Commands In this appendix The following table displays the Fabric Watch commands. Many of these commands are used in advanced configuration. For more information about how to use these commands, refer to Chapter 8, “Fabric Watch Configurations”.
A 92 In this appendix Fabric Watch Administrator’s Guide 53-1001188-01
Appendix B Port fencing types The following table lists and describes the set of port fencing types that are available in M-EOS and Fabric OS v6.2.0. Fencing Type Violation Subtype Description Firmware Class / Area FOS Support Security Port Binding The login server detects a Port Binding violation when an attached device attempts to FLOGI with a port name WWN that does not match the WWN in the Port Binding configuration for that F_Port.
Port fencing types Fencing Type Violation Subtype Description Protocol ISL Segmentation An E_Port has segmented, exceeding the threshold limit. Security ISL Security Error The attached switch previously placed in the Invalid Attachment state has persisted in consuming switch resources and has violated the threshold limit of ISL Security Errors. This is similar to Authentication subtype.
Index A above event triggers, 23 activating Fabric Watch, 31 alarms continuous, 3, 29, 70 triggered, 3, 29, 70 API notification method, 75 area environment class, 13 fabric class, 13 FRU class, 14 performance monitor class, 15 port class, 15 resource class, 16 security class, 16 SFP class, 18 areas, 13 B behavior types continuous, 70 triggered, 70 below event trigger, 24 buffer values, 19 C changed event trigger, 24 class environment, 12 fabric, 12 FRU, 12 Performace Monitor, 12 port, 12 resource, 12 sec
Fabric Watch activation, 31 components, 1, 11 description of, 1 interface types, 31 notification methods, 27 thresholds, 19 fencing, port types, 93 FRU class areas, 14 I in-between triggers, 25 interface types, 31 N notification methods, 2, 27 API, 75 e-mail, 75 e-mail alert, 28 event log entry, 3 port log lock, 28 port log lock action, 75 RAPI trap, 28 SNMP, 3, 74 SNMP trap, 27 P performance monitor class areas, 15 port class areas, 15 port fencing types, 93 port log lock, 28, 75 port persistence, 5 se
