Dell PowerConnect Brocade M6505 Brocade 7.1.0 Fabric Watch Administrator's Gui - Page 39

Fabric Watch Threshold Components, In this Fabric Watch classes, areas, and elements, Classes

Page 39 highlights

Chapter Fabric Watch Threshold Components 3 In this chapter •Fabric Watch classes, areas, and elements 19 Fabric Watch classes, areas, and elements 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 wide groupings of similar fabric devices or fabric data. Table 1 on page 20 describes the classes into which Fabric Watch groups all switch and fabric elements. 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. Class 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. For detailed information about how to configure areas, including recommended threshold and action settings for the classes listed in Table 1, refer to one of the following chapters: • Chapter 6, "Fabric, Security, SFP, and Performance Monitoring" Fabric class, Security class, SFP class, and Performance class areas and actions are configured using the thConfig command. • Chapter 7, "Port Monitoring" The physical port and its subclass areas and actions are configured using the portThConfig command. Fabric Watch Administrator's Guide 19 53-1002752-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126

Fabric Watch Administrator’s Guide
19
53-1002752-01
Chapter
3
Fabric Watch Threshold Components
In this chapter
Fabric Watch classes, areas, and elements . . . . . . . . . . . . . . . . . . . . . . . . .
19
Fabric Watch classes, areas, and elements
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 wide groupings of similar fabric devices or fabric data.
Table 1
on page 20 describes
the classes into which Fabric Watch groups all switch and fabric elements.
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.
Class 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
.
For detailed information about how to configure areas, including recommended threshold and
action settings for the classes listed in
Table 1
, refer to one of the following chapters:
Chapter 6, “Fabric, Security, SFP, and Performance Monitoring”
Fabric class, Security class, SFP class, and Performance class areas and actions are
configured using the
thConfig
command.
Chapter 7, “Port Monitoring”
The physical port and its subclass areas and actions are configured using the
portThConfig
command.