PowerFlex Management Platform - How To Manually Clear Alerts From 4.X PowerFlex Manager UI

Summary: The PowerFlex Manager 4.x UI shows alerts from various sources, whether it be the PowerFlex block cluster (MDM) or Hardware events. Each event can only be cleared by the system/service originally called them. Sometimes that service is no longer running and the alert will not clear. This KB will explain how to clear the stuck alerts. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

Run these commands from one of the PFMP nodes:

Note: "INGRESS_PASSWORD" variable, if your password contains special characters e.g (!#@$%^&)  Put single quotes around the password when configuring the variable.

Ex. 

Password123!!
INGRESS_PASSWORD='Password123!!'
  1. Set these environment variables:

    INGRESS_IP=<IP_ADDRESS or HOSTNAME for PFxM>
    INGRESS_USER=admin
    INGRESS_PASSWORD=<PASSWORD>
    
  2. Run these 2 commands to get the needed authentication tokens:
    TOKEN=$(curl -s -k --location --request POST "https://${INGRESS_IP}/rest/auth/login" --header "Accept: application/json" --header "Content-Type: application/json" --data "{\"username\": \"${INGRESS_USER}\",\"password\": \"${INGRESS_PASSWORD}\"}")
    
    ACCESS_TOKEN=$(echo "${TOKEN}" | jq -r .access_token)
  3. In the PFxM UI, go to Monitoring --> Alerts, then look at the "Alert ID" for the alerts that need to be cleared.
    It should look something like "000000000000002d" (just an example)
  4. Run this final command to clear the alert ID that was just collected:

    curl -i --insecure -X POST "https://${INGRESS_IP}/rest/v1/alerts/000000000000002d/clear" -H "accept: application/json" -H "Authorization: Bearer ${ACCESS_TOKEN}"

    If the command is successful, the following message will show:

    mno21:~ # curl -i --insecure -X POST "https://${INGRESS_IP}/rest/v1/alerts/000000000000002d/clear" -H "accept: application/json" -H "Authorization: Bearer ${ACCESS_TOKEN}"
    HTTP/2 204
    date: Thu, 30 Mar 2023 14:53:21 GMT
    strict-transport-security: max-age=15724800; includeSubDomains
    
  5. Run through steps 3 and 4 as often as needed. The access token is good for 5 minutes. So if the process goes longer than that, just re-run steps 2-4

Affected Products

PowerFlex rack, PowerFlex Appliance, PowerFlex custom node, PowerFlex Software
Article Properties
Article Number: 000220827
Article Type: How To
Last Modified: 18 Dec 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.