E-mail alert, Port fencing and port decommissioning – Brocade Monitoring and Alerting Policy Suite Administrators Guide (Supporting Fabric OS v7.3.0) User Manual
Page 53
SNMP MIB support
MAPS requires SNMP management information base (MIB) support on the device for management
information collection. For additional information on SNMP MIB support, refer to the Fabric OS
Administrator's Guide.
E-mail alert
An “e-mail alert” action sends information about the event to one or more specified e-mail addresses.
The e-mail alert specifies the threshold and describes the event, much like an error message.
You configure the e-mail recipients using the mapsConfig --emailcfg command. You must separate
multiple e-mail addresses with a comma and include the complete e-mail address. For example,
[email protected] is a valid e-mail address; abc@12 is not. Refer to
on page
61 for more information.
Port fencing and port decommissioning
MAPS supports port fencing and port decommissioning for E_Ports and F_Ports. These actions
automatically take ports offline when configured thresholds in a given rule are exceeded. Port fencing
immediately takes ports offline, which may cause loss of traffic. Port decommissioning takes a port
offline more slowly, but without loss of traffic. Both are disabled by default. Port decommissioning and
port fencing can only be configured for the port health monitoring system rules, the monitoring systems
for which decommissioning is supported.
Port decommissioning cannot be configured by itself in a MAPS rule or action, as it requires port fencing
to be enabled in the same rule. If you attempt to create a MAPS rule or action that has port
decommissioning without port fencing, the rule or action will be rejected. MAPS can be configured to
have only port fencing enabled in a rule; if this is the case, MAPS behaves the same as it did in Fabric
OS 7.2.x.
Port fencing and port decommissioning actions in MAPS are valid only for conditions evaluated on
physical ports, E_Ports, F_Ports, and VE_Ports, and can only be configured using the Port Health
monitoring rules. Refer to the
Port Health monitoring thresholds
on page 100 tables for these rules.
Be aware that if port fencing and port decommissioning are both configured for multiple similar rules,
both actions must be configured for the rule with the highest threshold monitored. For example, if you
configure one rule with a CRC threshold value “greater than 10 per minute” and you configure a second
rule with a CRC threshold value “greater than 20 per minute”, you should configure port fencing and
port decommissioning as the action for the rule with the 20 per minute threshold, as configuring it for the
10 per minute rule will block the other rule from being triggered.
Port decommissioning for E_Ports and F_Ports
For E_Ports, if port decommissioning fails, MAPS will fence the port. Switches themselves can
decommission E_Ports through MAPS. In this case, when port decommissioning is triggered on an
E_Port, the neighboring switches will perform a handshake so that traffic is re-routed before the port is
disabled. Be aware that there are multiple reasons that the port-decommissioning operation between
two E_Ports could fail; for example, if the link that fails is the last link between the two switches. To see
which parameters can trigger port fencing and port decommissioning, refer to
on page 100.
For F_Ports, port decommissioning will only work if BNA has been configured to perform the port
decommissioning and port fencing actions, and the switch running MAPS has SNMP traps enabled.
1
Port fencing is supported on VE_Ports in Brocade FR4-18i blades installed in Brocade 7500 switches. It is not supported
on VE_Ports in FX8-24 blades or on Brocade 7800 switches.
E-mail alert
Monitoring and Alerting Policy Suite Administrator's Guide
53
53-1003147-01