HP StorageWorks 2/64, StorageWorks Fabric OS 5.x Fabric Watch Administrator's Manual
HP StorageWorks
Fabric OS 5.x Fabric Watch administrator guide
Part number: AA-RVJ0B-TE
Second edition: September 2005
Legal and notice information
©Copyright 2005 Hewlett-Packard Development Company, L.P.
©Copyright2005BrocadeCommunicationsSystems,Incorporated.
Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential
damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or
translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any
kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Microsoft, Windows, Windows NT, and Windows XP are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Fabric OS 5.x Fabric Watch administrator guide
Contents
About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 An introduction to Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Fabric Watch overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Introduction to fabric health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Fabric Watch concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Fabric watch components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Environment class areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fabric class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
FRU class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Performance monitor class areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Port class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Resource class area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Security class areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SFP class areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Event behavior types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Continuous event behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Triggered event behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Data values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Threshold values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
High and low thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Buffer values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Time bases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Setting time base to none. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Specifying a time base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Event settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Above event triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Below event trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Changed event trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
In-Between triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Port persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Switch event (error) log entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
SNMP trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
RAPITrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Port log lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Email alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Assigning notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Switch policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Interpreting event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fabric OS 5.x Fabric Watch administrator guide 3
3 Activating and accessing Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Activating Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Activating with telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Activating with Advanced Web Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Accessing Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Advanced Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SNMP-Based enterprise managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuration file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 Configuring Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring Fabric Watch thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Step 1: Select the class and area to configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Step 2: Configure thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Step 3: Configure alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
How to calculate values for alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 4: Disable and enable thresholds by port (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring SNMP notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring port log lock actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1: Show Mail configuration information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring switch status policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 1: Plan and define your switch status policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 2: Implement your switch status policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Step 3: View your switch status policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuring Fabric Watch using Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuring Fabric Watch using SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
A Default threshold values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Environment class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Fabric class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Performance monitor class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Port class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Resource class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Security class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
SFP class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B Basic Fabric Watch configuration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
C Using Fabric Watch with configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figures
1 Threshold monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 A buffered data region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3 Time base set to none. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4 Event trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5 Example without an event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6 Above event trigger with buffer zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7 Changed threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8 In-Between trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9 Disabling a threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10 Changing the threshold alarm level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
11 Applying threshold alarm changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
12 fwMailcfg Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13 Config show menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4
14 fwFruCfg configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
15 Configuring Fabric Watch using SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
16 Enabling Fabric Watch Traps in SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
17 Configuring SNMP management host IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
18 Example OID tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
19 Example swFwName screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Tables
1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Fabric Watch classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4 Environment class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5 Fabric class sreas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6 FRU class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Performance monitor class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8 Port class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9 Resource class area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10 Security class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
11 SFP class areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
12 Numerical values of notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
13 Element listing information - RXPerformance area menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14 Element listing information - Advanced Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
15 Element listing information - threshold boundary menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16 Advanced configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
17 Switch status policy monitor health factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18 Environment class threshold defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
19 Fabric Class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
20 AL_PA performance monitor class threshold defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
21 Customer-Defined performance monitor class threshold defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
22 End-to-End performance monitor class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
23 Port Class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
24 E-Port class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
25 F/FL-Port class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
26 Resource class threshold defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
27 Security class threshold defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
28 SFP Class Threshold Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Fabric OS 5.x Fabric Watch administrator guide 5
6
About this guide
This administrator guide provides information about:
• Setting up HP StorageWorks Fabric Watch software
• Managing your SAN via HP StorageWorks Fabric Watch software
Intended audience
This guide is intended for:
• system administrators responsible for setting up HP StorageWorks Fibre Channel Storage Area Network
(SAN) switches
• technicians responsible for maintaining the Fabric Operating System (OS)
Related documentation
Documentation, including white papers and best practices documents, is available on the HP web site:
http://www.hp.com/country/us/eng/prodserv/storage.html
To access current Fabric OS 5.x related documents:
1. Locate the IT storage Products section of the web page.
2. Under Networked storage, click SAN Infrastructure.
3. From the SAN Infrastructure web page, locate the SAN Infrastucture products section.
4. Click Fibre Channel Switches.
5. Locate the B-Series-Fabric-Enterprise Class section.
6. To access Fabric OS 5.x documents (such as this document), click 4/256 SAN Director and 4/256 SAN
Director power pack.
The switch overview page displays.
7. Go to the Product Information section, located on the right side of the web page.
8. Click Technical documents.
9. Follow the onscreen instructions to download the applicable documents.
Fabric OS 5.x Fabric Watch administrator guide 7
Document conventions and symbols
Table 1 Document conventions
Convention Element
Medium blue text: Figure 1 Cross-reference links and e-mail addresses
Medium blue, underlined text
(http://www.hp.com)
Bold font • Key names
Italics font Text emphasis
Monospace font • File and directory names
Monospace, italic font • Code variables
Monospace, bold font Emphasis of file and directory names, system output, code, and text
Web site addresses
• Text typed into a GUI element, such as into a box
• GUI elements that are clicked or selected, such as menu and list
items, buttons, and check boxes
• System output
• Code
• Text typed at the command-line
• Command-line variables
typed at the command line
WARNING! Indicates that failure to follow directions could result in bodily harm or death.
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT: Provides clarifying information or specific instructions.
NOTE: Provides additional information.
TIP: Provides helpful hints and shortcuts.
8
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/
Collect the following information before calling:
• Technical support registration number (if applicable)
• Product serial numbers
• Product model names and numbers
• Applicable error messages
• Operating system type and revision level
• Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
HP strongly recommends that customers sign up online using the Subscriber's choice web site:
http://www.hp.com/go/e-updates
• Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest
versions of drivers, and firmware documentation updates as well as instant access to numerous other
product resources.
• After signing up, you can quickly locate your products by selecting Business support and then Storage
under Product Category.
HP-authorized reseller
.
.
For the name of your nearest HP-authorized reseller:
• In the United States, call 1-800-282-6672.
• Elsewhere, visit the HP web site: http://www.hp.com
telephone numbers.
Helpful web sites
For other product information, see the following HP web sites:
• http://www.hp.com
• http://www.hp.com/go/storage
• http://www.hp.com/support/
• http://www.docs.hp.com
. Then click Contact HP to find locations and
Fabric OS 5.x Fabric Watch administrator guide 9
10
1 An introduction to Fabric Watch
This chapter contains the following information:
• Fabric Watch overview, page 11
• Introduction to fabric health, page 12
Fabric Watch overview
Fabric Watch is an optional Storage Area Network (SAN) monitoring software for B-Series HP
StorageWorks switches running Fabric OS 2.2 or higher. It enables each switch to constantly watch its
SAN fabric for potential faults and to automatically alert you to problems long before they become costly
failures.
Fabric Watch tracks a variety of SAN fabric elements, events, and counters. Monitoring fabric-wide events,
ports, GBICs, and environmental parameters enables early fault detection and isolation as well as
performance measurement. You can select custom fabric elements and alert thresholds or choose from a
selection of preconfigured settings. You can also easily integrate Fabric Watch with enterprise systems
management solutions.
By implementing Fabric Watch, you can rapidly improve SAN availability and performance without
installing new software or system administration tools.
For a growing number of organizations, SAN fabrics are a mission-critical part of their systems
architecture. These fabrics can include hundreds of elements, such as hosts, storage devices, switches, and
inter-switch links (ISLs). An instrumentation solution for SANs delivers optimal value by tracking a wide
spectrum of fabric events. For instance, Fabric Watch monitors:
• Fabric resources, including fabric reconfigurations, zoning changes, and new logins.
• Switch environmental functions such as temperature, power supply, and fan status, along with security
violations.
• Port state transitions, errors, and traffic information for multiple port classes as well as operational
values for supported models of “Smart” GBICs/SFPs.
• Performance information for AL_PA, end-to-end, and SCSI command metrics.
Fabric Watch lets you define notification thresholds. Whenever fabric elements exceed these thresholds,
Fabric Watch automatically provides notification using several methods, including email messages, SNMP
traps, and log entries.
Fabric Watch provides the following two 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.
• A triggered alarm generates the first warning when a threshold condition is reached and a second
alarm when the threshold condition is cleared.
Fabric Watch provides event notifications in several different formats to ensure that event details are
accessible from all platforms and operating systems. In response to an event, Fabric Watch can record
event data as any (or all) of the following:
• Simple Network Management Protocol (SNMP) trap
Following an event, Fabric Watch transmits critical event data as an SNMP trap. Support for SNMP
makes Fabric Watch readily compatible with both network and enterprise management solutions.
• Event log entry
Following an event, Fabric Watch adds an entry to the internal Event Log for an individual switch, which
stores up to 1024 error messages.
• Lock port log
Fabric OS 5.x Fabric Watch administrator guide 11
Following an event, Fabric Watch adds an entry to the internal port log for an individual switch and
freezes the log to ensure that detail-level information is available.
• RapiTrap
Following an event, Fabric Watch forwards event information to a proxy switch, which then forwards
the information to a server to notify you.
• Email notification
Following an event, Fabric Watch creates and sends an Informational email to a designated recipient.
Fabric Watch is designed for rapid deployment. Simply enabling Fabric Watch permits immediate fabric
monitoring. Fabric Watch is also designed for rapid custom configuration. You can easily create and
modify configuration files using a text editor and then distribute configurations to all the switches in the
SAN through the Fabric OS configuration management utility. Fabric Watch also comes with
preconfigured profiles for rapid implementation.
Introduction to fabric health
Fabric health refers to the capability of the fabric to support data to be routed through it. A healthy fabric
enables effective data transmission between networked devices.
Although the concept of fabric health initially seems fairly simple, it can be a deep and complex topic due
to the number of factors that are involved. One of the more obvious criteria for fabric health is the condition
of the network hardware. A switch or port failure could easily prevent data packets from reaching their
destination. Network traffic can also influence fabric health.
If the number of packets routed through a port exceeds the port bandwidth, it causes network delays and
packet losses. Even environmental factors can become issues, as network hardware can fail to function
properly when stored in locations that do not meet the environmental conditions for the device. For
example, switches can fail when stored in rooms that are too hot.
Because of the varied and complex factors in determining fabric health, you need fabric monitoring
software such as Fabric Watch to help you to quickly detect, identify, and resolve fabric health issues by
continuously monitoring possible issues and reporting any potential concerns. Fabric Watch automatically
provides detailed reports on detected issues and helps you correct failures.
Fabric Watch provides customizable monitoring thresholds. You can configure Fabric Watch to provide
notification before problems arise, such as reporting when network traffic through a port is approaching
the bandwidth limit. This information enables you to perform preemptive network maintenance such as
trunking or zoning and avoid potential network failures.
12 An introduction to Fabric Watch
2 Fabric Watch concepts
This chapter contains the following sections:
• Fabric watch components, page 13
• Configuring events, page 19
• Port persistence, page 25
• Notification methods, page 25
• Switch policies, page 27
• Interpreting event messages, page 27
Fabric watch components
Fabric Watch uses a hierarchical organization to track the network device information it monitors. There is
a class, area, and element associated with every monitored behavior. Classes are the highest level in the
system, subdivided into one or more areas. Areas contain one or more elements.
The following sections explain this hierarchy and its application within Fabric Watch.
Classes
Classes are high-level categories of elements. Classes are intentionally wide groupings of similar fabric
devices or fabric data.
Examples of classes include Port (which includes all physical ports on a switch), Security (which includes
information related to unauthorized login attempts), and Environment (which contains information related
to the room temperature, supplied power and fan assemblies).
In some cases, classes are divided into subclasses. This additional level in the hierarchy increases the
flexibility of setting monitoring thresholds. You can use subclasses to add additional event monitoring to
fabric objects that meet the requirements of a subclass.
For example, ports connected to another switch can be monitored using both the Port class and E_Port
subclass. You can configure general port monitoring using the Port class and monitoring specific to a type
of port using the E_Port class. Ports connected to another switch can trigger events based on either of these
configurations. Ports that are not connected to another switch are not affected by the additional monitoring
configured into the E_Port class.
Table 2 describes the classes into which Fabric Watch groups all switch and fabric elements.
Table 2 Fabric Watch 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.
Fabric Groups areas of potential problems arising between devices,
including interswitch link (ISL) details, zoning, and traffic. A
Fabric-class alarm alerts you to problems or potential problems with
interconnectivity.
Field Replaceable Unit
(FRU)
Monitors the status of FRUs and provides an alert when a part
replacement is needed. This class monitors states, not thresholds.
Fabric OS 5.x Fabric Watch administrator guide 13
Table 2 Fabric Watch classes (continued)
Class Description
Performance Monitor Serves as a tuning tool. Performance Monitor classes group areas
that track the source and destination of traffic. Use the Performance
Monitor class thresholds and alarms to determine traffic load and
flow and to reallocate resources appropriately.
The Performance Monitor class is divided into the areas AL_PA
Performance Monitor, EE (end-to-end) Performance Monitor, and
Filter Performance Monitor.
Port Enables you to set additional thresholds, specific to different types of
ports.
The Port class is divided into separate classes:
E_Port class—Represents ports connected to another switch.
F/FL_Port class —Represents fabric or fabric loop ports that are
made of copper or optical fiber.
Resource Monitors flash memory. It calculates the amount of flash space
consumed and compares it to a defined threshold.
Security Monitors all attempts to breach your SAN security, helping you
fine-tune your security measures.
SFP Groups areas that monitor the physical aspects of SFPs. An SFP class
Areas
While classes represent large groupings of information, areas represent the information that Fabric Watch
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 3 lists and describes the Fabric Watch areas in the Environment class.
Table 3 Environment class areas
Area Description
Fan Refers to the speed of the fans inside the switch, in revolutions per
Power Supply Monitors whether power supplies within the switch are on, off,
alarm alerts you to a SFP malfunction fault.
minute. It is important that the fans spin quickly enough to keep the
ambient temperature from rising to levels at which switch damage
might occur.
present, or absent. Fabric Watch monitors power supplies to be
sure that power is always available to a switch.
Temperature Refers to the ambient temperature inside the switch, in degrees
14 Fabric Watch concepts
Celsius. Temperature sensors monitor the switch in case the
temperature rises to levels at which damage to the switch might
occur.
Fabric class areas
Table 4 lists Fabric Watch areas in the Fabric class and describes each area.
Table 4 Fabric class sreas
Area Description
Domain ID Changes Monitors forcible domain ID changes. Forcible domain ID changes
Fabric Logins Occurs when ports and devices initialize with the fabric.
occur when there is a conflict of domain IDs in a single fabric and the
principal switch has to assign another domain ID to a switch.
Fabric
Reconfiguration
Loss of E_Port Tracks the number of times that an E_Port goes down. E_Ports go down
Segmentation
Changes
SFP State Changes Indicates whether the state of the SFP is normal or faulty, on or off. A
Tracks the number of reconfigurations of the fabric. Fabric
reconfiguration occurs when:
• Two fabrics with the same domain ID are connected.
• Two fabrics are joined.
• An E_Port has gone offline.
• A principal link has segmented from the fabric.
each time you remove a cable or an SFP (where there are SFP failures
or transient errors).
Tracks the cumulative number of segmentation changes. Segmentation
changes occur due to:
• Zone conflicts.
• Incompatible link parameters. During E_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.
faulty or off state means that you must reinsert, turn on, or replace the
SFP. Fabric Watch monitors only Digital Diagnostic SFP.
Zoning Changes Tracks the number of zone changes. Because zoning is a security
FRU class areas
Table 5 lists Fabric Watch areas in the FRU class and describes each area. Possible states for all FRU-class
areas are absent, faulty, inserted, on, off, ready, and up.
Table 5 FRU class areas
Area Indicates
Slot State of a slot has changed.
Power Supply State of a power supply has changed.
Fan State of a fan has changed.
WWN State of a WWN card has changed.
Supported FRU areas depend on your particular HP switch model. The Slot and WWN areas are not
supported for the following switches:
provision, frequent zone changes might indicate a security breach or
weakness. Zone change messages occur whenever there is a change
in zone configurations.
Fabric OS 5.x Fabric Watch administrator guide 15
• HP StorageWorks SAN Switch 2/8V, 2/16V and 2/16N
• HP StorageWorks SAN Switch 2/32
• HP StorageWorks SAN Switch 4/32
Performance monitor class areas
Table 6 lists Fabric Watch areas in the Performance Monitor class and describes each area.
Table 6 Performance monitor class areas
Area Indicates
Customer Define Relies on performance monitor telnet commands. For more information
on this area, refer to the
reference guide
Invalid CRC Errors have been detected in the Fibre Channel frame. Invalid CRC
messages occur when the number of CRC errors in Fibre Channel
frames for specific source ID (S_ID) and destination ID (D_ID) pairs
change. These messages can also be caused by dirty or aging
equipment and temperature fluctuations.
Receive Performance The percentage of word frames traveling from the configured S_ID to the
D_ID exceeds the configured thresholds.
Transmit Performance The percentage of word frames traveling from the configured S_ID to the
D_ID; user configuration triggers these messages, so you can use the
Transmit Performance area to tune your network.
HP StorageWorks Fabric OS 5.x command
.
Port class areas
Table 7 lists and describes the Fabric Watch areas in the port class.
Table 7 Port class areas
Area Indicates
Invalid Cyclic
Redundancy Checks
(CRCs)
Invalid Transmission
Word
Link Failure Count A link loses signal. Both physical and hardware problems can
Loss of Signal Count The number of times that a signal loss occurs in a port. Signal loss
Loss of Synchronization
(Sync) Count
A frame is invalid and cannot be transmitted. Invalid CRCs can
represent noise on the network. Such frames are recoverable by
retransmission. Invalid CRCs indicate a potential hardware
problem. These errors occur mostly in aging fabrics.
A word did not transmit successfully. Invalid word messages usually
indicate a hardware problem.
cause link failures. Link failures frequently occur due to a loss of
synchronization. Check for concurrent loss of synchronization errors
and, if applicable, troubleshoot those errors. Link failures also occur
due to hardware failures.
indicates that no data is moving through the port. A loss of signal
usually indicates a hardware problem.
Two devices failed to communicate at the same speed.
Synchronization losses are always accompanied by link failure.
Loss of synchronization errors frequently occur due to a faulty SFP
or cable.
Primitive Sequence
Protocol Error
16 Fabric Watch concepts
A CRC sum disparity. Occasionally, these errors occur due to
software glitches. Persistent errors occur due to hardware problems.
Table 7 Port class areas (continued)
Area Indicates
Receive (RX) Performance The percentage of maximum bandwidth consumed in packet
State Changes The state of the port has changed for one of the following reasons:
Transmit (TX) Performance The percentage of maximum bandwidth consumed in packet
Resource class area
Table 8 describes the Fabric Watch resource class area.
receipts.
• 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.
• The port has become an F/FL_Port.
• The port has segmented.
• The port has become a trunk port.
transmissions.
Table 8 Resource class area
Area Description
Flash Monitor Monitors the compact flash space available by calculating the
Security class areas
Table 9 lists Fabric Watch areas in the security class and describes what each area indicates. For details
on each area, refer to the
Table 9 Security class areas
Area Indicates
API Violation An API access request reaches a secure switch from an unauthorized
DCC Violation An unauthorized device attempts to log in to a secure fabric.
Front Panel Violation A secure switch detects unauthorized front panel access.
HTTP Violation A browser access request reaches a secure switch from an
Illegal Command Commands permitted only to the primary Fibre Channel Switch (FCS)
percentage of flash space consumed and comparing it with the
configured high threshold value.
HP StorageWorks Fabric OS 5.x secure fabric administrator guide
IP address.
unauthorized IP address.
are executed on another switch.
.
Incompatible DB Secure switches with different version stamps have been detected.
Invalid Certificates The primary FCS sends a certificate to all switches in the secure fabric
before it sends configuration data. Receiving switches accept only
packets with the correct certificate; any other certificates are invalid
and represent an attempted security breach.
Fabric OS 5.x Fabric Watch administrator guide 17
Table 9 Security class areas (continued)
Area Indicates
Invalid Signatures If a switch cannot verify the signature of a packet, the switch rejects
the packet and the signature becomes invalid.
Invalid Timestamps If a time interval becomes too great from the time a packet is sent to
the time it is received, the timestamp of the packet becomes invalid
and the switch rejects it.
Login Violation A login violation occurs when a secure fabric detects a login failure.
MS Violation An MS (Management Server) violation occurs when an access request
reaches a secure switch from an unauthorized WWN (World Wide
Name). The WWN appears in the ERRLOG.
No FCS The switch has lost contact with the primary FCS.
RSNMP Violation An RSNMP (remote simple network management protocol) violation
occurs when an SNMP (simple network management protocol) get
operation reaches a secure switch from an unauthorized IP address.
SCC Violation An SCC violation occurs when an unauthorized switch tries to join a
secure fabric. The WWN of the unauthorized switch appears in the
ERRLOG.
Serial Violation A serial violation occurs when a secure switch detects an unauthorized
serial port connection request.
SES Violation An SES violation occurs when an SCSI Enclosed Services (SES) request
SLAP Bad Packets A Switch Link Authentication Protocol (SLAP) bad packets failure
SLAP Failures A SLAP failure occurs when packets try to pass from a nonsecure
Telnet Violation A telnet violation occurs when a telnet connection request reaches a
TS Out of Sync A TS (Time Server) Out of Synchronization error has been detected.
WSNMP Violation A WSNMP violation occurs when an SNMP set operation reaches a
SFP class areas
Table 10 lists Fabric Watch areas in the SFP class and describes each area.
Table 10 SFP class areas
Area Description
Temperature The temperature area measures the physical temperature of the SFP, in
reaches a secure switch from an unauthorized WWN.
occurs when the switch receives a bad SLAP packet. Bad SLAP
packets include unexpected packets and packets with incorrect
transmission IDs.
switch to a secure fabric.
secure switch from an unauthorized IP address.
secure switch from an unauthorized IP address.
degrees Celsius. A high temperature indicates that the SFP might be in
danger of damage.
Receive Power The receive power area measures the amount of incoming laser, in
µwatts, to help determine if the SFP is in good working condition. If the
counter often exceeds the threshold, the SFP is deteriorating.
18 Fabric Watch concepts
Table 10 SFP class areas (continued)
Elements
Area Description
Transmit Power The transmit power area measures the amount of outgoing laser, in
µwatts. Use this to determine the condition of the SFP. If the counter
often exceeds the threshold, the SFP is deteriorating.
Current The current area measures the amount of supplied current to the SFP
transceiver. Current area events indicate hardware failures.
Supply Voltage The supply voltage area measures the amount of voltage supplied to the
SFP. If this value exceeds the threshold, the SFP is deteriorating.
Fabric Watch defines an
each area, there are a number of elements equivalent to the number of components being monitored. For
instance, in the Core Switch 2/64, each area of the Port class will include 64 elements.
Each element contains information pertaining to the description suggested by the area. To continue the
Ports example, each element in the Invalid word area of Ports would contain exactly 64 ports, each of
which would contain the number of times invalid words had been received by the port over the last time
interval. Each of these elements maps to an index number, so that all elements can be identified in terms of
class, area, and index number. As an example, the monitoring of the temperature sensor with an index of
one may be viewed by accessing the first temperature sensor within the temperature area of the
environment class.
Subclasses are a minor exception to the above rule. Subclasses, such as E_Ports, contain areas with
elements equivalent to the number of valid entries. Within the same example used thus far in this section, in
a 64-port switch in which eight ports are connected to another switch, each area within the E_Port class
would contain eight elements.
Each area of a subclass with defined thresholds will act in addition to the settings applied to the element
through the parent class. Assignment of elements to subclasses does not need to be performed by a
network administrator. These assignments are seamlessly made through automated detection algorithms.
Configuring events
The following area attributes are used to define and detect events in Fabric Watch:
• ”Event behavior types” on page 19
• ”Data values” on page 20
• ”Threshold values” on page 20
• ”Time bases” on page 21
• ”Event settings” on page 23
element
as any fabric or switch component that the software monitors. Within
You can customize the information reported by Fabric Watch by configuring event behavior types,
threshold values, time bases, and event settings. You cannot change data values; these represent switch
behavior that is updated by the software.
Event behavior types
Based on the number of notifications delivered for events there are two categories of event behavior types:
• ”Continuous event behavior” on page 19
• ”Triggered event behavior” on page 20
Continuous event behavior
Areas with event behavior types set to
longer meets the criteria defined for the event.
For example, you can configure Fabric Watch to notify you during every sample period that a port is at full
utilization. This information can help you plan network upgrades.
continuous
trigger events in every sample period until the fabric no
Fabric OS 5.x Fabric Watch administrator guide 19
Triggered event behavior
If you do not want notification during each sample period from the port hardware failure to the time of its
repair, you can define the event behavior as
When an event behavior is defined as triggered, Fabric Watch sends only one event notification when the
fabric meets the criteria for the event. It does not send out any more notifications.
For example, when a port fails, Fabric Watch sends you a notification of the failure. After you repair the
port, Fabric Watch detects the repair. At this time, Fabric Watch determines that the fabric no longer meets
the event criteria, and watches for the error again. The next time the port fails, it sends you another
notification.
Data values
A data value represents an aspect of a fabric in three ways: counter value, measured value or state value.
Data values are updated by Fabric Watch approximately every six seconds. You cannot change them.
Counter value is the total number of times that a given event has occurred. For each monitored event
during the time period, the value is incremented.
Measured value is the current, measurable value of a fabric or fabric element, such as environmental
temperature or fan speed.
State value, which is the only qualitative data value, provides information on the overall state of a fabric
component, such as the physical health of a fan. Instead of numerical data, state values contain
information on whether components are faulty, active, or in another state.
Fabric Watch compares counter values and measured values to a set of configurable limits to determine
whether fabric monitoring has occurred and whether to notify you. You must set appropriate threshold
boundaries to trigger an event.
triggered
.
State values are handled differently, as Fabric Watch monitors state values for certain states, which you
can select. When a state value transitions to one of the monitored states, an event is triggered.
Threshold values
Threshold values are of the following types:
• ”High and low thresholds” on page 20
• ”Buffer values” on page 20
High and low thresholds
High and low threshold values are the values at which potential problems might occur. For example, in
configuring a temperature threshold, you can select the temperatures at which a potential problem can
occur due to both overheating and freezing.
You can compare high and low thresholds with a data value. The units of measurement are the same as
that of the associated data.
Buffer values
You can use buffer values to reduce the occurrence of events due to data fluctuation. When you assign a
buffer value, it is used to create a zone in which events cannot occur both above the high threshold and
below the low threshold.
20 Fabric Watch concepts
Figure shows an example in which each time a signal crosses the high limit, an event occurs. The blue
arrows indicate the area where the event criteria is met. In this case, there is a great deal of fluctuation.
Even when the monitor is set to triggered, a number of messages are sent.
Figure 1 Threshold monitoring
Figure shows how to limit the number of event notifications using a buffer. When you specify a buffer,
events cannot occur both above the high threshold and below the low threshold. Event notification occurs
only where the arrow indicates. The event criteria is continued to be met until the data sensed falls below
the high threshold value.
Figure 2 A buffered data region
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.
Setting time base to none
If you set a time base to
When the absolute value of the measuring counter exceeds the threshold boundary, an event is triggered.
Figure shows a high limit of 65 degrees Celsius placed on a counter measuring temperature. During each
sample period, Fabric Watch measures the temperature is measured and compares it against the high
threshold. If the measured temperature exceeds the high threshold, it triggers an event.
none
, Fabric Watch compares a data value against a threshold boundary level.
Figure 3 Time base set to none
Fabric OS 5.x Fabric Watch administrator guide 21
Specifying a time base
If you specify a time base value other than
the current data value. Instead, it calculates the difference between the current data value and the data
value as it existed one time base ago. It compares this difference to the threshold boundary limit.
For example, if you specify the time base
between two samples a minute apart. It then compares the difference (current data value – data value one
minute ago) against the preset threshold boundary.
When you set a time base to a value other than
configuring events:
• Fabric Watch triggers an event only if the difference in the data value exceeds the preset threshold
boundary limit.
• Even if the current data value exceeds the threshold, Fabric Watch does not trigger an event if the
rate of change is below the threshold limit.
The following examples illustrate each point.
Example1: Triggering an Event
Figure 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
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. As
illustrated on the tenth sample, the counter value changes from 0 to 1; hence calculated rate of change is
1 per minute. At the thirteenth sample, the rate of change is 2 per minute. The rate of change must be at
least 3 per minute to exceed the event-triggering requirement of 2, which is met on the eighteenth sample.
none (seconds, minute, hour
minute
, Fabric Watch calculates the counter value difference
none
, there are two main points to remember when
, or
day
), Fabric Watch does not use
minute
is defined. An event
Figure 4 Event trigger
Example 2: Not Triggering an Event
Figure uses the same data to illustrate a case in which a threshold is exceeded without triggering an event.
In this case, the calculated rate of change in the data value is always less than or equal to the high
threshold of 2. At the tenth sample, the rate of change is one per minute. At the fourteenth, twenty-first, and
twenty-fifth sample, the rate of change remains equal to the high threshold of 2. In this case, Fabric Watch
22 Fabric Watch concepts
does not trigger an event even though the absolute value of the counter reaches 4, which is well above the
high threshold.
Figure 5 Example without an event
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 impacts event
triggering.
Fabric Watch monitors data values for one of the following conditions:
• ”Above event triggers” on page 23
• ”Below event trigger” on page 24
• ”Changed event trigger” on page 24
• ”In-Between triggers” on page 24
For Fabric Watch to monitor these conditions, the alarm setting must be set to a non-zero value.
Above event triggers
Use the Above event trigger for an element that requires only high threshold monitoring. In the Above event
trigger, Fabric Watch triggers an event immediately after the data value becomes greater than the high
threshold.
Define a buffer zone within the operational limit of an area to suppress multiple events when the counter
value fluctuates above the high threshold and buffer zone. Figure shows an Above event trigger with a
buffer zone.When a buffer is used, the data value must be greater than the sum of the high threshold and
the buffer value (event 1 in Figure ). When the data value becomes less than the high threshold again,
Fabric Watch triggers a second event (event 2) to indicate that it has returned to normal operation.
Figure 6 Above event trigger with buffer zone
Fabric OS 5.x Fabric Watch administrator guide 23
Loading...