Upon verifying that a hardware upgrade is successfully completed and the system is stable, the command to remove the maintenance suppression is purealert untag --maintenance .

During upgrade activities, engineers often apply a "maintenance" tag or flag to the alert system to prevent the generation of "noise" (false positive alerts) that would otherwise be triggered by expected events like controller failovers, link downs, or path fluctuations. This suppression ensures that the customer and Pure Support are not flooded with critical tickets for planned work.

Once the work is done, it is critical to remove this suppression so the array resumes normal monitoring. The purealert command with the untag verb and the specific --maintenance flag is the correct syntax to clear this state. Options A and C use invalid syntax (--cancel or --unset) that is not recognized by the Purity CLI for this specific alert management function. Failing to run this command leaves the array in a state where genuine failures might be masked, violating the "Always-On" monitoring standard.