- Notes, cautions, and warnings
- Welcome
- Using the GUI
- Configuring GUI default settings
- Using storage hierarchy maps
- Viewing system status
- Monitoring the system
- The Performance Monitoring dashboard
- Viewing a chart
- Modifying a dashboard layout
- Creating a custom dashboard
- Removing a chart
- Moving a chart
- Back-end Bandwidth Chart
- Back-end Throughput chart
- Back-end Errors chart
- Back-end Latency chart
- CPU utilization chart
- Heap Usage chart
- Front-end Queue Depth chart
- Front-end Bandwidth chart
- Front-end Latency chart
- Front-end Throughput chart
- Front-end Aborts chart
- Write Latency Delta chart
- WAN Port Performance chart
- WAN Latency chart
- Rebuild Status dashboard
- The Virtual Volumes Performance dashboard
- Virtual Volume Throughput chart
- Virtual Volume Latency chart
- Virtual Volume Bandwidth chart
- The Front End Ports dashboard
- System Health
- Provisioning storage
- Guide
- Provisioning from storage volumes
- Provision Job properties
- Distributed storage
- Supported storage arrays
- Using the Storage Arrays view
- Rediscovering a storage array
- Viewing logical units for an array
- Forgetting a storage array
- Storage array connectivity status
- About storage volumes
- The Storage Volumes view
- Claiming storage volumes
- The Claim Storage wizard
- Setting a storage volume rebuild type
- Unclaiming a storage volume
- Viewing ITLs for a storage volume
- Renaming a storage volume
- Storage Volume status
- About devices
- Using the Devices view
- The Create Devices wizard
- The Add Local/Remote Mirror wizards
- Viewing the status of IO to a device
- Creating a device
- Renaming a device
- Deleting a device
- Mirroring a device
- Device status
- Device component properties
- Device properties
- Distributed device properties
- Add capacity to virtual volumes
- Extent properties
- About extents
- Using the Extents view
- The Create Extents wizard
- Creating an extent
- Renaming an extent
- Deleting an extent
- Extent status
- About distributed devices
- The Distributed Devices view
- The Create Distributed Device from Claimed Storage Volumes wizard
- Distributed device rule sets
- Changing the rule set for a distributed device
- Creating a distributed device
- Deleting a distributed device
- Renaming a distributed device
- Distributed Device status
- About virtual volumes
- The Virtual Volumes view
- The Distributed Virtual Volumes view
- Creating a virtual volume
- About virtual volume expansion
- Expanding a virtual volume using storage volumes
- Enabling or disabling remote access for a volume
- Manually assigning LUN numbers to volumes
- Deleting a volume
- Renaming a volume
- Tearing down a volume
- Virtual Volume status
- Pool properties
- Virtual volume properties
- Show ITLs dialog box
- Logical unit properties
- ALUA Support field values
- Visibility field values
- Extent or Device mobility job properties
- Metro node port properties
- Storage array properties
- Storage view properties
- Storage volume properties
- Create Virtual Volumes dialog box
- About consistency groups
- Using the Consistency Groups view
- Distributed Consistency Groups view
- Create Consistency Group wizard
- Types of consistency groups
- Creating a consistency group
- Adding a volume to a consistency group
- Removing a volume from a consistency group
- Deleting a consistency group
- Consistency Group status
- Consistency group properties
- Step 1: Select or create a consistency group for the virtual volume
- Step 1: Create a consistency group
- Step 2: Select volume options
- Step 3: Select a storage pool
- Step 3: Select a pool for each mirror on the second cluster
- Step 3: Select a pool for each mirror in the cluster
- Step3: Create thin virtual volumes
- Select a storage view for the virtual volume(s) (optional)
- Step 5: Review your selections
- Step 6: View results
- Step 2: Select volume options
- Step 2: Select volume options
- Step 3: Select a storage volume to create the virtual volume
- Step 3: Select a source and target storage volume
- Step 3: Create thin volumes
- Step 3: Select a target storage volume on the remote cluster
- Step 3: Select target storage on the remote cluster
- Step 6: View results
- Show Logical Units
- Exporting storage
- About Initiators and metro node ports
- Using the Ports view
- Using the Initiators view
- Enabling or disabling a port
- Registering an initiator
- Rediscovering an initiator
- Manually registering an initiator
- Unregistering an initiator
- Metro node port status
- Initiator properties
- Add capacity to virtual volumes
- About storage views
- Using the Storage Views screen
- The Create Storage View wizard
- Creating a storage view
- Deleting a storage view
- Renaming a storage view
- Adding or removing initiators from a storage view
- Adding virtual volumes to a storage view
- Removing virtual volumes from a storage view
- Adding or removing metro node ports from a storage view
- Storage view status
- Storage group properties
- Director properties
- Cluster properties
- Moving data
- Mobility
- Move Data Within Cluster
- Move Data Across Clusters
- Create Mobility Job wizards
- Mobility job transfer size
- Creating a mobility job
- Viewing job details
- Committing a job
- Canceling a job
- Pausing a job
- Resuming a job
- Removing the record of a job
- Changing a job transfer size
- Searching for a job
- Mobility job status
- Notifications
Dell EMC Metro node 7.0.1 Online Help
Platform view properties
Platform alert tab
- Severity
- Indicates the urgency of alert:
CRITICAL-A condition has occurred that can obstruct the functionality or can lead to failure of the other components.
ERROR-An error has occurred that has a significant impact on the system and must be rectified immediately.
WARNING-An error has occurred that you should be aware of but does not have a significant impact on the system. For example, a component is working, but its performance may not be optimum.
INFO-An event has occurred that does not impact system functions. No action is required.
CLEAR-When a corresponding clear event is generated for the raised alert, and the issue is resolved at the system level.
- State
- Represents the state of the alert-OPEN, CLOSED, or ACK state.
OPEN-The alert is active and no action has been taken on it. The alert generating condition still persists in the system. If the system administrator wants to reopen to pay attention to that event, the alert status can also be changed to open from acknowledge state.
- To reopen an alert: Select the checkbox corresponding to the alert, and then click OPEN.
ACK-After you view an alert and understand its contents, you can acknowledge that you have read through the alert message.- To acknowledge an alert: Select the checkbox corresponding to the alert, and then click ACKNOWLEDGE .
CLOSED-Once the problem condition is resolved, the event state is updated as closed. Once closed the alerts cannot be reopened.- To close an alert: Select the checkbox corresponding to the alert, and then click CLOSE.
- Message
- Indicates the cause of an event for which the alert is generated.
- Category
- Displays the event category.
- Enabled
- Indicates whether the alert is enabled or not.
- Alert ID
- Represents the unique ID assigned to each alert .
- Alert Name
- Represents the name of the alert.
- Description
- Describes the platform alert.
- Corrective Action
- Action to eliminate the cause of event.
- Scope
- Represents whether it is a cluster-level or a director-level alert.
- Condition ID
- Indicates Unique ID of all defined alert definitions.
- Component
- System component that caused the event. Intended for service personnel.
- Event Source
- Represents the context of the event. For example, Virtual Volume.
- Event Source ID
- Unique ID for the source of the event. Helps to narrow down to the final component .
- Resource
- It shows the resource for which the issue has occurred.
- Count
- It represents the number of times the same alert is generated over the selected period. This column is available for historical alerts only.
- Scope Incarnation
- Represents unique ID assigned to each director and cluster.
- Creation Date
- Date and time when the alert is generated.
- Last Updated
- Date and time when the status of the alert is last changed.
- External RCA
- Represents external root cause analysis of the issue.
- Notes
- It shows the notes which are added by user.
- Debug Events
- Associated legacy debug events generated through firmware.
Additional details tab
To view additional information about the alert in name-value pair, click the Additional details tab.
Logs tab
It is for historical alerts only. It provides the list of creation and last updated time for the same alert has occurred.
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: <>()\