53-1002933-02 9 September 2013 ® Monitoring and Alerting Policy Suite Administrator’s Guide Supporting Fabric OS v7.2.0a Supporting Fabric OS v7.2.
Copyright © 2010-2013 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Command syntax conventions . . . . . . . . . . . . . . . . . .
MAPS configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Monitoring a new port using existing rules . . . . . . . . . . . . . . . . . . . . 9 Monitoring across different time windows . . . . . . . . . . . . . . . . . . . . . 9 Resetting MAPS configuration upload and download to Brocade defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Chapter 3 MAPS Elements and Categories In this chapter . . . . . . . . .
Chapter 5 MAPS actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling or disabling actions at a global level. . . . . . . . . . . . . . . . . RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-mail alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port fencing . . .
MAPS threshold value tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document In this chapter • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • Getting technical help . . .
- Brocade 6547 embedded switch Brocade 7800 extension switch Brocade VA-40FC Brocade Encryption Switch • Brocade DCX Backbone family: - Brocade DCX - Brocade DCX-4S • Brocade DCX 8510 Backbone family: - Brocade DCX 8510-4 - Brocade DCX 8510-8 Document conventions This section describes text formatting conventions and important notice formats used in this document.
variable Variables are in italics. ... Repeat the previous element, for example “member[;member...]” value Fixed values following arguments are in plain font. For example, --show WWN | Boolean. Elements are exclusive. Example: --show -mode egress | ingress Notes, cautions, and warnings The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards. NOTE A note provides a tip, guidance.
Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations. These references are made for informational purposes only. Corporation Referenced Trademarks and Products Microsoft Corporation Windows, Windows NT, Internet Explorer Mozilla Corporation Mozilla, Firefox Netscape Communications Corporation Netscape Red Hat, Inc.
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.
Chapter 1 Monitoring and Alerting Policy Suite Overview In this chapter • MAPS overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MAPS license requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MAPS interoperability with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MAPS upgrade and downgrade considerations . . . . . . . . . . . . . . . . . . . . . . .
1 MAPS license requirements MAPS license requirements MAPS is an optionally licensed feature of Fabric OS. MAPS requires an active and valid Fabric Vision license. If you already have a license for Fabric Watch plus a license for Advanced Performance Monitoring, you will automatically get MAPS functionality without having to obtain an additional license.
MAPS upgrade and downgrade considerations 1 MAPS upgrade and downgrade considerations When downgrading from Fabric OS 7.2 to any previous version of the OS, the following MAPS-related behaviors should be expected: • When an active CP is running Fabric OS 7.2 with MAPS disabled, and the standby device has an earlier version of the Fabric OS, High Availability will be synchronized, but MAPS will not be allowed to be enabled until the firmware on the standby device is upgraded.
1 Migrating from Fabric Watch to MAPS CAUTION MAPS activation is a non-reversible process. Downgrading to Fabric OS 7.1 will enable Fabric Watch with its last configured settings. When you upgrade back to Fabric OS 7.2, Fabric Watch will continue to be enabled. Differences between Fabric Watch and MAPS configurations The MAPS monitoring and alerting configurations are not as complex as those available in Fabric Watch; consequently MAPS does not have some functionality that was available in Fabric Watch.
MAPS and Flow Vision 1 MAPS and Flow Vision MAPS can work with information generated by the Brocade Flow Vision application. For more information, refer to “Flow Vision integration with the MAPS dashboard” on page 48, and the Fabric OS Flow Vision Administrator’s Guide. MAPS supports only the following statistics generated by Flow Vision flow monitors.
1 6 MAPS and Flow Vision Monitoring and Alerting Policy Suite Administrator’s Guide 53-1002933-02
Chapter Enabling and Configuring MAPS 2 In this chapter • Enabling MAPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 • MAPS configuration quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 • MAPS configuration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Enabling MAPS MAPS is not enabled by default.
2 MAPS configuration tasks 3. Set global actions on the switch to none using use mapsConfig --actions none. Setting the global actions to “none” allows you to test the configured thresholds before enabling the actions. Refer to “MAPS actions” on page 27 for more details. 4. Monitor the switch using mapsDb --show or mapsDb --show all. Refer to “Viewing the MAPS dashboard” on page 41 more details. 5. Fine-tune the rules used by the policy as necessary. Refer to “Modifying a policy” on page 25 more details.
MAPS configuration tasks TABLE 2 2 MAPS configuration tasks (Continued) Configuration task Command Deleting a rule from a policy mapspolicy --delrule Creating a rule mapsrule --create Modifying a rule mapsrule --config Enabling or disabling actions at a global level mapsconfig --actions Sending alerts using e-mail mapsconfig --emailcfg Viewing the MAPS dashboard mapsdb --show Viewing historical data mapsdb --show history Refer to the Fabric OS Command Reference for additional information
2 MAPS configuration tasks Rule Data: ---------RuleName: crc_critical Condition: ALL_PORTS(crc/min>5) Actions: email,snmp Policies Associated: none switch:admin> mapsrule --create crc_persistent -monitor crc -group ALL_PORTS -timebase day -op g -value 20 -action raslog,email switch:admin> mapsrule --show crc_persistent Rule Data: ---------RuleName: crc_persistent Condition: ALL_PORTS(crc/day>20) Actions: raslog,email Policies Associated: none Resetting MAPS configuration upload and download to Brocade de
Chapter MAPS Elements and Categories 3 In this chapter • MAPS structural elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 • MAPS monitoring categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 MAPS structural elements MAPS has the following structural elements: categories, groups, rules, and policies. Table 3 provides a brief description of each structural element.
3 MAPS monitoring categories • • • • • Security Violations Fabric State Changes Switch Resource Traffic Performance FCIP Health The MAPS dashboard also displays the status of these categories. Refer to “MAPS dashboard overview” on page 39 for information on using the MAPS dashboard. Switch Policy Status The Switch Policy Status category enables you monitor the health of the switch by defining the number of types of errors that transitions the overall switch state into a state that is not healthy.
MAPS monitoring categories 3 The Port Health category also monitors the physical aspects of a small form-factor pluggable (SFP) transceiver, such as voltage, current, receive power (RXP), transmit power (TXP), and state changes in physical ports, E_Ports, FOP_Ports, and FCU_Ports. Table 5 lists the monitored parameters in this category and provides a brief description for each one. In the Monitored parameter column, the value in parentheses is the value you can specify for the mapsRule -monitor parameter.
3 MAPS monitoring categories FRU Health The FRU Health category enables you to define rules for field-replaceable units (FRUs), including small form-factor pluggable (SFP) transceivers, power supplies, and flash memory. Table 6 lists the monitored parameters in this category and provides a brief description for each one. Possible states for all FRU measures are faulty, inserted, on, off, ready, and up.
MAPS monitoring categories 3 Fabric State Changes The Fabric State Changes category groups areas of potential problems arising between devices, such as zone changes, fabric segmentation, E_Port down, fabric reconfiguration, domain ID changes, and fabric logins. Table 8 lists the monitored parameters in this category and provides a brief description for each one.
3 MAPS monitoring categories TABLE 9 Switch Resource category parameters Monitored parameter Description Temperature (TEMP) Refers to the ambient temperature inside the switch, in degrees Celsius. Temperature sensors monitor the switch in case the temperature rises to levels at which damage to the switch might occur. Flash (FLASH_USAGE) Monitors the compact flash space available by calculating the percentage of flash space consumed and comparing it with the configured high threshold value.
MAPS monitoring categories 3 FCIP Health The FCIP Health category enables you to define rules for FCIP health, including circuit state changes, circuit state utilization, and packet loss. Table 11 lists the monitored parameters in this category and provides a brief description for each one.
3 18 MAPS monitoring categories Monitoring and Alerting Policy Suite Administrator’s Guide 53-1002933-02
Chapter 4 MAPS Groups, Policies, Rules, and Actions In this chapter • MAPS groups overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MAPS policies overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Working with MAPS policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MAPS rules overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 MAPS groups overview TABLE 12 Predefined MAPS groups (Continued) Predefined group name Object type Description NON_E_F_PORTS FC Port All ports in the logical switch which are neither E_Ports nor F_Ports. ALL_10GSWL_SFP SFP All 10-Gbps SWL SFP transceivers on FC Ports in the logical switch. ALL_10GLWL_SFP SFP All 10-Gbps LWL SFP transceivers on FC Ports in the logical switch. ALL_16GSWL_SFP SFP All 16-Gbps Short Wavelength (SWL) SFP transceivers in the logical switch.
MAPS groups overview 4 Viewing group information MAPS allows you to view the information for all groups or a specific group. To view a summary of all the logical groups on a switch, enter logicalGroup --show. This command returns the group name, and whether the group is predefined. The following example shows the output of logicalGroup --show.
4 MAPS policies overview Monitoring similar ports using the same rules You can create groups of ports that behave in a similar manner and monitor these ports using the same rules and thresholds. Often on a switch there are sets of ports that behave in a similar manner and have a different behavior from other sets of ports. For example, the behavior of ports connected to UNIX hosts and servers is different from the behavior of ports connected to Windows hosts and servers.
MAPS policies overview 4 • dflt_conservative_policy Contains rules with more lenient thresholds that allow a buffer and do not immediately trigger actions. Use this policy in environments where the elements are resilient and can accommodate errors. Although you cannot modify the preconfigured policies, you can create a policy based on these policies. For more information, refer to “Modifying a default policy” on page 25. User-defined policies MAPS allows you to define your own policies.
4 Working with MAPS policies Working with MAPS policies The following sections discuss working with MAPS policies. Viewing policy information MAPS allows you to view all the policies on a switch by using mapsPolicy --show. You can use this command to show all policies, only a particular policy, or a summary.
Working with MAPS policies 4 Modifying a policy In some cases you might need to modify a policy, for example, if elements in the fabric change or if threshold configurations need to be modified to catch certain error conditions. To modify a policy and its associated rules, complete the following steps. 1. Modify the rules in the policy based on your requirements.
4 MAPS rules overview The following example clones the default policy, deletes two rules, and modifies a rule to send an e-mail message in addition to a RASLog entry.
MAPS actions 4 The change in the CRC counter in the last minute is greater than 10. For this condition, the threshold is “greater than 10”. NOTE MAPS conditions are applied on a per-port basis, not switch- or fabric-wide. For example, 20 ports that each get 1 CRC counter would not trigger a “greater than 10” rule. Time base Time bases specify the time interval between two samples to be compared.
4 MAPS actions Enabling or disabling actions at a global level You can define what actions are allowable on the switch, regardless of the actions that are specified in individual rules. Enabling and disabling actions at a global level allows you to configure rules with stricter actions, such as port fencing, but disable the action globally until you can test the configured thresholds. After validating the thresholds, you can enable port fencing globally without having to change all of the rules.
MAPS actions 4 SNMP traps In environments where you have a high number of messages coming from a variety of switches, you may want to receive them in a single location and view them using a graphical user interface (GUI). In this type of scenario, Simple Network Management Protocol (SNMP) notifications may be the most efficient notification method. You can avoid having to log in to each switch individually as you would have to do for error log notifications.
4 Working with MAPS rules and actions If you configure port fencing as an action, make sure that port fencing is configured for the rule with the highest monitored threshold. For example, if you configure a rule for CRC values greater than 10 per minute and you configure a second rule for CRC values greater than 20 per minute, do not configure port fencing as the action for the rule with the threshold value of 10. This action is valid only for conditions evaluated on ports.
Working with MAPS rules and actions 4 mapspolicy --enable policy The following example creates a rule to generate a RASLog message if the CRC counter for a group of critical ports is greater than 10 in an hour. This rule is added to the daily_policy, and the daily_policy is re-enabled for the rule to take effect.
4 Working with MAPS rules and actions switch:admin> mapsrule --show check_crc Rule Data: ---------RuleName: check_crc Condition: critical_ports(crc/hour>15) Actions: raslog Policies Associated: daily_policy switch:admin> mapspolicy --enable daily_policy Cloning a rule You can clone both default and user-defined rules. To clone a rule, complete the following steps. 1. Enter mapsRule --show to display the rule you want to clone. mapsrule --show rule_name 2.
Working with MAPS rules and actions 4 Policies Associated: none The following example shows all rules. Notice that the actions are not abbreviated in the output.
4 Working with MAPS rules and actions Relay Host: Relay Host Domain Name: Paused members : PORT : CIRCUIT : SFP : admin2@mycompany.com, admin3@mycompany.com, Relay Host IP is: 10.168.39.118 brocade.com Configuring e-mail server information Fabric OS 7.2.0 and later allows you to specify the e-mail server used to send e-mail alerts using the relayConfig command. The e-mail configuration is global at the chassis level and is common for all logical switches in the chassis.
Chapter Monitoring flows using MAPS 5 In this chapter • Flows and MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 • Monitoring flows using MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Flows and MAPS MAPS can monitor only static flows created using Flow Vision and generates alert messages based on user-defined rules. To monitor a flow, the flow must first be created in Flow Vision, and then imported into MAPS.
5 Monitoring flows using MAPS Notes on removing flows • Deimporting will succeed only if there are no MAPS rules associated with the flow. Before removing a flow, you must delete all the rules associated with that flow. • You can only remove one flow at a time. • Removing a flow only removes it from MAPS. It does not affect the flow definition in Flow Vision. Monitoring flows using MAPS To monitor the network, you can define flows on a switch with different feature sets.
Monitoring flows using MAPS 5 ATTENTION Small form-factor pluggable (SFP) transceiver monitoring on simulated mode (SIM) ports is not supported for MAPS. Examples of using MAPS to monitor traffic performance The following examples illustrate using MAPS to monitor traffic performance. Monitoring end-to-end performance The following example monitors the percentage of frames exceeding the configured threshold of RX and TX values in a flow between two devices.
5 38 Monitoring flows using MAPS Monitoring and Alerting Policy Suite Administrator’s Guide 53-1002933-02
Chapter MAPS Dashboard 6 In this chapter • MAPS dashboard overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 • Flow Vision integration with the MAPS dashboard . . . . . . . . . . . . . . . . . . . . 48 • Bottleneck detection integration with the MAPS dashboard . . . . . . . . . . . .
6 MAPS dashboard overview • • • • Fabric State Changes: Refer to “Fabric State Changes” on page 15. Switch Resource: Refer to “Switch Resource” on page 15. Traffic Performance: Refer to “Traffic Performance” on page 16. FCIP Health: Refer to “FCIP Health” on page 17. When a category contains an “out-of-range” error, the dashboard displays a table showing the rules triggered in that category since the previous midnight. This allows you to see more precisely where the problem is occurring.
MAPS dashboard overview 6 Notes on dashboard data • The dashboard displays data only for days that have errors. If a day does not have any errors, the dashboard does not include that day in the results. • The “Rule Count” value is the absolute number of different violations in that category since the previous midnight. The “Repeat Count” is the number of times a rule has been violated in the hour, for example between 10:00:00 and 10:59:59.
6 MAPS dashboard overview switch:admin> mapsdb --show DB start time: Tue Jul 9 17:17:33 2013 Active policy: dflt_conservative_policy Fenced Ports : none 1 Switch Health Report: ======================= Current Switch Policy Status: CRITICAL Contributing Factors: --------------------*BAD_PWR (MARGINAL). *BAD_FAN (CRITICAL). 2.
MAPS dashboard overview 6 The following example shows the detailed switch status. The status includes the summary switch status, plus port performance data for the current day (measured since midnight). switch:admin> mapsdb --show all DB start time: Tue Jul 9 17:17:33 2013 Active policy: dflt_conservative_policy Fenced Ports : none 1 Switch Health Report: ======================= Current Switch Policy Status: CRITICAL Contributing Factors: --------------------*BAD_PWR (MARGINAL). *BAD_FAN (CRITICAL). 2.
6 MAPS dashboard overview LF LOSS_SIGNAL(LOS) PE(Errors) STATE_CHG LR C3TXTO(Timeouts) RX(%) TX(%) UTIL(%) BN_SECS(Seconds) - - - - - - - Viewing historical data Entering mapsDb --show history displays a summarized history of the switch status since the previous midnight. This is useful if you want a quick view of what has been happening on the switch in that period. The output of this command differs depending on the platform you run it on.
MAPS dashboard overview ITW(ITWs) LOSS_SYNC(SyncLoss) LF LOSS_SIGNAL(LOS) PE(Errors) STATE_CHG LR C3TXTO(Timeouts) RX(%) TX(%) UTIL(%) BN_SECS(Seconds) - - - - - - 6 - Viewing data for a specific time window Detailed historical data provides the status of the switch for a specific time window. This is useful if, for example, users are reporting problems on a specific day or time. The same port-display patterns apply to viewing detailed historical data as for ordinary historical data.
6 MAPS dashboard overview Switch Resource Traffic Performance FCIP Health |In operating range |In operating range |Not applicable |In operating range |In operating range |Not applicable | | | 2.2 Rules Affecting Health: =========================== Category(Rule Count)|RepeatCount|Rule Name |Execution Time |Object \ -------------------------------------------------------------------------------------------------\ Port Health(2) |1 |defALL_OTHER_F_PORTSCRC_40 |07/09/13 17:18:18|Port 1 \ |1 |defALL_OTHER
Bottleneck detection integration with the MAPS dashboard 6 The following example clears only the dashboard summary data. switch:admin> mapsdb --clear -summary NOTE When the dashboard is cleared, a RASLog message is generated. For more details on RASLog messages in MAPS, refer to the Fabric OS Message Reference. Bottleneck detection integration with the MAPS dashboard The Fabric OS bottleneck daemon is responsible for detecting persistent bottlenecks and providing notifications.
6 Flow Vision integration with the MAPS dashboard Dashboard output for bottleneck data The Summary portion of the MAPS dashboard includes bottleneck (BN) information when available. In the following example, the “Traffic Performance” line is where bottleneck information appears. Notice that the last line indicates a bottleneck caused by a timeout rather than a numeric value. (MAPS Dashboard output trimmed) 2.
Chapter Additional MAPS features 7 In this chapter • Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 • Pausing and resuming MAPS monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 • MAPS Service Availability Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Overview The following sections describe additional features in the Monitoring and Alerting Policy Suite (MAPS).
7 MAPS Service Availability Module Notes on MAPSSAM • The MAPSSAM report does not distinguish why a port is recorded as down, it only reports that how long the port has been down. • The MAPSSAM report does not include the health status of GbE ports. MAPS only monitors and reports the status for physical and virtual FC ports. The following example shows a typical output for mapsSam --show.
Appendix A MAPS Threshold values In this chapter • MAPS threshold value tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch Status Policy thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port Monitoring thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP Monitoring thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric Monitoring thresholds . . . .
A MAPS threshold value tables TABLE 14 Port Monitoring thresholds MAPS Thresholds (RASLOG Threshold/Port Fencing Threshold)1 Monitoring Statistic E_Ports F_Ports (Host) F_Ports (Target) F-Ports (Unknown) NON-E_F_Ports AG MO CO AG MO CO AG MO CO AG MO CO AG C3TX_TO 5 10 20 2/4 3/10 11/20 0/2 3/5 6/10 2/4 3/10 11/20 N/A CRC 0/2 10/20 21/40 Same As E_Ports 0/2 5/10 11/20 Same As E_Ports ITW 15/20 21/40 41/80 5/10 11/20 21/40 Link Reset 2/4 5/10 11/20 0/2
A MAPS threshold value tables TABLE 17 Security Monitoring thresholds MAPS Thresholds (RASLOG Threshold/Port Fencing Threshold)1 Monitoring Statistic AG MO CO DCC Violations 0 2 4 HTTP Violation 0 2 4 Illegal Command 0 2 4 Incompatible security DB 0 2 4 Login Violations 0 2 4 Invalid Certifications 0 2 4 No-FCS 0 2 4 SCC Violations 0 2 4 SLAP failures 0 2 4 Telnet Violations 0 2 4 TS out of sync 1/hr 2/day 2/hr 4/day 4/hr 10/day 1.
A 54 MAPS threshold value tables Monitoring and Alerting Policy Suite Administrator’s Guide 53-1002933-02
Index A actions, 27 e-mail alert, 29 enabling or disabling globally, 28 port fencing, 29 RASLog, 28 SFP marginal, 30 SNMP trap, 29 switch down, 30 switch marginal, 30 Admin Domains considerations, 2 alerts, configuring e-mail address for, 33 B bottleneck detection and MAPS dashboard, 47–48 bottleneck detection data on MAPS dashboard, 48 bottleneckmon command, 47 C categories Fabric State Changes, 15 FCIP Health, 17 FRU Health, 14 monitoring, 11 Port Health, 12 Security Violations, 14 Switch Policy Status
data, deleting, 46 default active policy, 7 default policy, 22 default policy, modifying, 25 deleting stored data from dashboard, 46 detailed switch status, viewing, 42 dflt_agressive_policy policy, 22 dflt_conservative_policy policy, 23 dflt_moderate_policy policy, 22 disabling actions globally, 28 duplicating rules, 32 E element action, 11 category, 11 condition, 11 element, 11 group, 11 policy, 11 rule, 11 e-mail address configuration, 33 sending an alert by, 29 e-mail server configuring, 34 viewing con
M MAPS default policy, 22 elements See: element Fabric Watch configuration differences, 4 flows and, 35–37 importing flows, 35, 36 interoperability with Fabric Watch, 2 license requirement, 2 max number of user-defined groups, 20 overview, 1 predefined policies, listed, 22 resetting configuration download to default, 10 resetting configuration upload to default, 10 structural elements, defined, 11 MAPS and Flow Vision, 36 MAPS dashboard, 39–48 bottleneck detection, 47–48 display options, 41 Flow Vision inte
Q T quick setup, 7–8 thresholds, 26 Fabric Monitoring, 52 FCIP Monitoring, 52 Port Monitoring, 52 Resource Monitoring, 53 Security Monitoring, 53 SFP Monitoring, 53 Switch Status Policy, 51 time base, 27 Traffic Performance category, 16 traffic performance monitoring, 16 R RASLog action, 28 removing flows from MAPS, 35 resetting MAPS configuration download to default, 10 MAPS configuration upload to default, 10 resource monitoring, 15 Resource Monitoring thresholds, 53 resuming MAPS monitoring, 49 rules
