- Notes, cautions, and warnings
- Introduction
- Revision history
- Initial configuration and setup
- Performing common tasks
- Expanding PowerFlex storage
- Displaying system information at a glance
- Managing block storage after PowerFlex deployment
- Protection domains
- Fault sets
- Storage data servers
- Storage pools
- Acceleration pools
- Devices
- Volumes
- NVMe targets
- Hosts
- Managing file storage
- High availability
- Multitenancy
- Overview of configuring NAS servers
- About file system storage
- File protection
- Create a protection policy
- Create snapshot rules
- Create a snapshot
- Modify a snapshot
- Delete a snapshot
- Assign a protection policy to a file system
- Unassign a protection policy
- Modify a protection policy
- Delete a protection policy
- Modify a snapshot rule
- Delete a snapshot rule
- Refresh a file system using snapshot
- Restore a file system from a snapshot
- Clone NAS server and file system
- Clone the file system
- Create a thin clone using a snapshot
- Protecting a block storage environment
- Snapshots
- Create snapshots
- Overwrite volume content from a snapshot
- Set bandwidth and IOPS limits for snapshots
- Lock and unlock snapshots
- Delete snapshots
- Map snapshots
- Unmap snapshots
- Increase the size of a snapshot
- Migrate a snapshot vTree
- Pause snapshot vTree migration
- Roll back snapshot vTree migration
- Set snapshot vTree migration priority
- Snapshot policies
- Remote protection
- Extract and upload certificates
- Journal capacity
- Add a peer system
- Restart the replication cluster
- SDRs
- Replication consistency group
- Replication direction and mapping
- Create a replication consistency group
- Map RCG target volumes to hosts
- Unmap a host from RCG target volumes
- Set the target to inconsistent mode
- Set the target to consistent mode
- Modify the recovery point objective
- Add a replication pair to an RCG
- Pause replication for an RCG
- Resume replication for an RCG
- Create a snapshot of an RCG volume
- Add an RCG snapshot policy
- Perform a failover
- Reverse replication
- Restore replication
- Test Failover
- Stop a failover test
- Freeze an RCG
- Unfreeze an RCG
- Activate an RCG
- Terminate replication in an RCG
- Delete an RCG
- Pause creation of an initial copy
- Resume creation of initial copy
- Set copying priority
- Unpair from RCG
- Snapshots
- Performing lifecycle operations for a resource group
- Deploying a resource configuration in a resource group
- Basic tasks
- Deploying a resource group
- Adding an existing resource group
- Updating a resource group with new firmware and software
- Viewing a compliance report
- Entering and exiting service mode
- Replacing a drive
- Replacing NVDIMM node or battery
- Reconfiguring MDM roles
- Migrating vCLS VMs to shared storage
- Adding components to a resource group
- Resize a volume
- Removing resources from a resource group
- Adding NVMe/TCP storage access
- Replacing the operating system for a node
- Additional resource group management tasks
- Basic tasks
- Preparing a template for a resource group deployment
- Basic tasks
- Additional template management tasks
- Deploying a resource configuration in a resource group
- Managing resources
- Basic tasks
- Discover a resource
- Viewing resource details
- Update resource inventory
- Viewing a compliance report for a resource
- Updating firmware and software
- Removing resources
- Additional resource management tasks
- Basic tasks
- Monitoring events and alerts
- Configuring system settings
- User management
- Repositories
- Getting started
- Networking
- Events and alerts
- License management
- Security
- Serviceability
- Software upgrade
- PowerFlex Manager user interface reference
- Maintenance for a PowerFlex controller node
- Retrieving logs for the PowerFlex nodes
- Retrieving logs for PowerFlex components
- Retrieving additional PowerFlex logs
- Enabling audit logging
- Managing storage devices using CloudLink
- Understanding NVMe over TCP load balancing
- Managing NAS server configuration
- Migrating to NVMe over TCP on VMware ESXi
Dell PowerFlex 4.6.x Administration Guide
Alerts
An alert is a state in the system which is usually on or off. Alerts monitor serious events that require user attention or action.
When an alert is no longer relevant or is resolved, the system automatically clears the alerts with no user intervention. This action ensures that cleared alerts are hidden from the default view so that only relevant issues are displayed to administrators. Cleared alerts can be optionally displayed through table filtering options. Alerts can also be acknowledged which removes the alert from default view. Acknowledging an alert does not indicate that the issue is resolved. You can view acknowledged alerts through the table-filtering options.
Alert severity level
The severity levels are as follows:
| Severity level | Explanation | Example |
|---|---|---|
| Information | An information level informs you of things that happen in the system that do not require action. | NDU |
| Minor | A minor level informs you that action is required but is not urgent. | This Storage Pool contains devices that are not being accelerated. |
| Major | A major level informs you that action is required soon. | The MDM certificate is about to expire. |
| Critical | A critical level informs you that the system requires immediate attention. | The MDM certificate has expired. |
Alert default and advanced fields
The default and advanced fields are as follows:
| Field | Description | Example |
|---|---|---|
| Description | A message that describes the alert. | The MDM cluster is degraded, and data is not protected. |
| System impact | A free text, description of the system impact of the alert. | Risk of cluster unavailability |
| Repair Flow | Free text, actions that you can take in order to repair the issue. | Check that all MDM cluster nodes are functioning correctly, and fix and replace faulty nodes, if necessary, to return to full protection |
| Alert Details | Any extra details that are relevant to the object and or incident involved. | Percentage of SP capacity usage |
| Associated Events | A list of events that modified the life cycle of the alert. | [object Object] |
| Resource ID | The ID of the resource that is associated with the alert. | 86fb0000000000 |
| Resource Name | The name of the resource that is associated with the alert. This is usually the resource that is involved with raising the event. | sds212 |
| Resource Type | The type of resource that is associated with the alert. this is usually the resource that is involved with raising the event. | sdses |
| Last Updated | The UTC date and time that the alert was last updated. | 2022-04-28T07:58:46.16Z |
| Timestamp | The UTC date and time that the alert was initially raised. | 2022-04-28T07:58:46.16Z |
| Acknowledged status | The acknowledged status indicates whether the alert is acknowledged or unacknowledged. | Y |
The total number of alerts that can be sent to Secure Remote Services gateway from the PowerFlex Manager dispatcher service is restricted to 200 per day. The threshold for the number of alerts for a particular event is set to three per hour. After the first three alerts are sent, if fourth alert is generated for the same event, it is not sent to the Secure Remote Services. However, if the alerts are sent from two different systems running iDRAC, the alerts are sent to the Secure Remote Services gateway.
A new threshold alert is triggered from PowerFlex Manager when the threshold of 200 alerts per 24 hrs is crossed per day and is automatically sent to Secure Remote Services gateway. Similarly, a new alert is triggered from PowerFlex Manager and sent to Secure Remote Services gateway when threshold of three alerts per hour for same alert type, symptom code, or resource is reached.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\