Brocade Monitoring and Alerting Policy Suite Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 54)

BNA can decommission F_Ports based on CRC, ITW, PE, LR, STATE_CHG, or C3TXTO criteria.
MAPS notifications are integrated with BNA, which in turn must coordinate with the switch and the end
device to orchestrate the port decommissioning. If BNA is not configured on a switch, MAPS will fence
the F_Port.
For more information on port fencing, port decommissioning, and related failure codes, refer to the
Fabric OS Administrator's Guide.
Port decommissioning and firmware downgrades
• If the port decommissioning (decom) configuration is in any of the logical switches, the
firmwareDownload operation from Fabric OS 7.3.0 to a previous version will fail with one of the
following messages:
‐ If the decom action is configured in the MAPS actions, the following error message is
displayed.
Downgrade is not allowed, because port decommmission(decom) actions are
enabled in some logical switches.
Please delete decom action from the FID(S) , …
‐ If any of the MAPS rules have the decom action configured, the following error message is
displayed.
Downgrade is not allowed, because port decommission(decom) actions are
configured in user defined rules in some logical switches.
Please delete decom action from all user defined rules in the FID(S)
, …
• If there are any default policy rules present with port decommissioning configured, the firmware
downgrade is not blocked as in this case, the decommissioning rules are mapped to Fabric OS
7.2.x port fencing rules. That is, a default Fabric OS 7.3.0 MAPS rule with port commissioning
specified will remain mapped to the same rule, but without port decommissioning as an action,
when the switch is downgraded to version Fabric OS 7.2.x.
• Currently the decommission action is present for the port monitoring rules in dflt_aggressive_policy.
When the switch is rebooted using version Fabric OS 7.2.x, the default rules in
dflt_aggressive_policy which had port decommissioning specified will have port fencing specified.
• User-defined rules in the active policy are not checked to see if they have port decommissioning
configured, as user-defined rules in the active policy are present only in memory and are erased as
soon as a different policy is enabled, whether in Fabric OS 7.3.0 or any earlier version.
Configuring port decommissioning
Port decommissioning can be configured in two ways. It can be configured along with port fencing in
the MAPS actions configuration, or it can be configured as an action in a MAPS rule.
To enable port decommissioning, complete the following steps.
1. Connect to the switch and log in using an account with admin permissions.
2. Create a rule or action as follows:
• Enter mapsConfig --actions fence,decom to create an action for the entire switch.
• Use the mapsRule --create new_rule_name -group group_name -monitor monitor_value -
timebase time_unit -op comparison_operator -value comp_op_value -action fence,decom
command to create a rule.
Port decommissioning and firmware downgrades
54 Monitoring and Alerting Policy Suite Administrator's Guide
53-1003147-01