Brocade Network Advisor SAN + IP User Manual v12.1.0 - Manual (Page 1832)

Brocade Network Advisor SAN + IP User Manual 1791
53-1002949-01
MAPS category, object, and measure hierarchy
50
MAPS category, object, and measure hierarchy
Fabric measures and events are organized in a hierarchy by category, object, and measure. There
is a category, object, and measure associated with every monitored behavior. Categories are the
highest level in the system, subdivided into one or more objects. Objects contain one or more
measures.
An example of a very simple category, object, measure hierarchy follows.
Traffic (category)
FC Port (object)
Receive Bandwidth usage % (measure)
Transmit Bandwidth usage % (measure)
Trunk Utilization (measure)
For a list of all categories, objects, and measures, refer to “MAPS categories, measures, and
actions” on page 1792.
MAPS structural elements
MAPS has the following structural elements: categories, groups, rules, and policies. Table 172
provides a brief description of each structural element.
TABLE 172 MAPS structural elements
Element Description
Action What MAPS is to do if a condition defined in a rule evaluates to true. For more information, refer to
“MAPS actions” on page 1803.
Category A grouping of similar elements that can be monitored (for example “Security Violations”.) For more
information, refer to
“MAPS monitoring categories” on page 1794.
Condition A true/false trigger created by the combination of a time base and a threshold value. For more
information, refer to “MAPS conditions” on page 1802.
Measure A value that can be monitored. This includes switch conditions, data traffic levels, error messages, and
many other values. For more information, refer to the specific category in the section
“MAPS
monitoring categories” on page 1794.
Object An object that can be monitored. This includes FC ports, SFP transceivers, local switch, flow and other
values. For more information, refer to
“MAPS categories, measures, and actions” on page 1792.
Group A collection of similar objects that you can monitor as a single entity. For example, you can create a
group of E_ports from different devices to be monitored by the same policies. A Flow can be imported
as a group. For more information, refer to
“MAPS groups” on page 1819.
Rule A rule associates a condition with one or more actions that need to occur when the specified condition
is triggered. For more information, refer to
“MAPS rules” on page 1801.
Policy A set of rules defining thresholds for triggering the actions MAPS takes when that threshold is
triggered. When a policy is enabled, all of the rules in the policy are in effect. For more information,
refer to
“MAPS policies” on page 1800.