PowerStore Basic Troubleshooting - Participant Guide
PowerStore Basic Troubleshooting - Participant Guide
TROUBLESHOOTING
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerStore Basic Troubleshooting
Serviceability ............................................................................................................ 51
IPMI Overview ................................................................................................................... 52
After the Connection is Established ................................................................................... 55
IPMItool example ............................................................................................................... 56
SSH and PowerStore Management Access over the Service LAN Ports ........................... 57
Serviceability Key Points .................................................................................................... 61
Service Container..................................................................................................... 62
Appendix ................................................................................................. 93
Glossary .................................................................................................. 95
PowerStore
The PowerStore Platform Engineer exam is intended for partners and internal
employees who are responsible for the installation and maintenance of PowerStore
arrays.
A. PowerStore Concepts and Features (ODC) A. PowerStore Concepts and Features (ODC)
B. PowerStore Installation Cabling (ODC) B. PowerStore Implementation (ODC)
C. PowerStore Implementation (ODC) C. PowerStore Installation (ODC)
D. PowerStore Administration (ODC) D. PowerStore Installation:Cabling (ODC)
E. PowerStore Basic Troubleshooting (ODC)
OR
F. PowerStore Maintenance (ODC)
A. PowerStore Implementation and Administration G. PowerStore Upgrades (ODC)
(C)
B. PowerStore Migration: Import External Storage
(C)
(C) - Classroom
Midrange Storage
The Midrange Technology Architect exam is intended for partners and internal
employees who are responsible for positioning or designing a solution using Dell
EMC midrange storage systems. This includes the following products: PowerStore,
Unity XT, and SC Series.
(C) - Classroom
Hardware Troubleshooting
There are LEDs on the front of the base enclosure. The drives are in 2.5-inch
carriers and are hot-swappable. You can enable drive identification from the CLI or
GUI interface to locate a specific drive.
As a quick way to identify a particular appliance in the rack, select BLINK LED from
Hardware > Appliance > Hardware > Disks in PowerStore Manager. Once
activated, the button is relabeled to STOP BLINK LED.
Solid: Fault. Blinking: Drive identification Solid: Power up. Blinking: Drive activity
Power
Ethernet Link
Ethernet Activity
SAS Activity
Port link
Port link
Node Fault
Node fault
Node Power
Node power
Unsafe to Remove
Unsafe to remove
When adding new I/O modules, always install I/O modules in pairs: One module in
node A, and one module in node B. Both nodes must have the same type of I/O
modules in the same slots.
The port link LEDs are below the FC ports. The power fault LED is on the right,
below the ejector handle.
1 2
The image below shows the Power Supplies from the back.
The enclosure power and fault LEDs on expansion enclosures are slightly different
from the LED on the main unit. But the drives are still in 2.5-inch carriers and are
hot-swappable.
1 4
2 3
Amber: Fault
Blue: No fault
2: Drive status/activity
3: Drive fault
Amber: Fault
Off: No fault
The Dell Service Tag (DST) is a serialized label that allow Dell EMC support to
track hardware in the field.
The DST is a black pull-out tag between the drives in slots 16 and 17.
The left side of the tag contains the system serial number and the Express
Service Code information. The QRL code is on the right:
PowerStore Alerts
Major: May have an impact on the system and should be remedied as soon
as possible. For example, the last synchronization time for a resource does
not match the time that its protection policy indicates.
Minor: 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 is not optimum.
Info: An event that does not impact system functions. No action is required.
For example, new software is available for download.
Alerts about the cluster overall are visible on the Dashboard Overview tab or
under Monitoring > Alerts. Click alert headings to show just that type of alert, as
shown here:
Alert Details
On the Dashboard Overview tab, click an alert title to quickly see its details and
the actions that you can take. Focus on critical alerts first, then major alerts. Minor
and Info alerts do not necessarily require any action. On the alert details slide-out
panel, find information about the alert. From this panel, you can acknowledge that
the issue which triggered the alert has been addressed.
You can copy and paste the error code into the monitoring / events / filters to find
all timestamps where this event has occurred for further troubleshooting—for
example, 0x00a00301 here.
Important: Acknowledging an alert does not make the problem go away, it just
makes the alert go away. Since some alerts do not require action, those alerts may
be automatically cleared by the system.
Alert Information
Related Events
Suggested Remedies
Acknowledge
When the alert has been remedied, click the ACKNOWLEDGE button to drop it off
of the list.
Monitoring
All alerts are listed on the Monitoring page. There are two ways to get to this
screen. Select Monitoring from the menu bar. Or, from the Dashboard Overview,
click VIEW ALL ALERTS.
Click any heading on this page to sort by it. Click again to reverse the sort
order. Sort by severity, code, description, resource type or name, updated
date, or timestamp.
In this example, the list has been sorted by severity to show the critical
alerts at the top.
Click the Filter icon to add filters to the columns. Filtering limits the list of
Alerts to show only those that match the filters.
In this example, Last Updated has been filtered to show alerts that were
updated more recently than 01 February 2020.
Acknowledged alerts are no longer displayed on the list. To show
acknowledged alerts, filter the Acknowledged column.
Component-Specific Alerts
The Dashboard Overview shows alerts for the entire cluster. Alerts can also be
found when they are specific to compute, storage, protection, and hardware. If
these objects have generated alerts, see the severity icon in the Alerts column.
From the Compute menu, see alerts related to Hosts & Host Groups
or Virtual Machines.
From the Storage menu, see alerts related to Volumes, Volume Groups, Storage
Containers, File Systems, and NAS Servers.
From the Hardware menu, see alerts related to Appliances and Ports. Port alerts are
shown at an individual port level.
PowerStore Alerts:
May or may not indicate a problem requiring user intervention. Focus on Critical
and Major alerts.
Can be sorted and filtered.
Includes details helpful in solving the problem:
Refer to this guide for more information: PowerStore CLI User Guide.
PowerStore CLI
PSTCLI Overview
The PowerStore Manager CLI enables you to run commands on a system through
a prompt from a Microsoft Windows or UNIX/Linux host. PSTCLI is intended for
users who want to manage a PowerStore system, or to use commands in scripts
for automating routine tasks.
On Windows, double-click the installer and follow the prompts. The default
installation location is:
– 64-bit systems: C:\Program Files\Dell EMC\PowerStore CLI
Command Syntax
You can run PSTCLI against the PowerStore primary node—the node running the
management stack. If you connect to a nonprimary node, it displays an error
message: The system was unable establish a secure connection
to the storage server. If the connection fails on all nodes, the management
stack may be down or unresponsive. Contact your support provider for assistance.
If you have adjusted your PATH variable as described on the previous page, you
can invoke PSTCLI from Windows Command Prompt or UNIX/Linux shell with the
pstcli command. If you have not adjusted the PATH variable, you must include
the path in the command.
The PSTCLI client contacts the server that issued the certificate—the trusted
certificate authority (CA)—and confirms the validity of the certificate before
proceeding. When the certificate is verified, PowerStore CLI and its backend server
establish the connection and begin to exchange data.
Syntax options:
-u username
The username on the PowerStore system, such as admin.
-d hostname or ipaddress
Name or address of the primary node.
[-p password]
Optional: password for the specified account. If you omit this parameter, the
system prompts for it, as shown in the examples which follow.
[-session]
Optional: Opens a persistent session with the cli> prompt. Or you can specify
a command to run and return context back to your workstation.
[-ssl value] Optional. Where value is one of the following:
Command Examples
For example:
Basic Help
Get help on any topic using the help command. Commands are divided into
categories. Get a list of the commands in a category, or a list of all the commands
with the help all command. Under Monitoring, there is a command that is
named alert.
Command Help
The command help alert shows that there is an alert show command, with
an option of -id . Get more information by using help alert show. Note the
syntax shown for the highlighted show subcommand. If you use specify the -id
option, it goes before show. All other options follow show.
Note the highlighted -limit option. The default limit is 100 records. Showing
alerts is described in the Troubleshooting with CLI topic.
PowerStore CLI:
Uses a restricted version of the Linux BASH shell.
Is downloaded from the documentation web site.
Can be used to perform many functions similar to those in the PowerStore
Manager GUI.
Alert Help
The command help alert shows that there is an alert show command, with
an option of -id <value>. You get more information by using help alert
show. Note the syntax show for the highlighted show subcommand. If you use
specify the -id option, it goes before show. All other options follow show.
To show all alerts on the system, use the alert show command with no options.
For example, you may have noticed that Windows clients are having problems
authenticating. An alert mentions a problem with the NAS server NAS_WIN10. To
show the details about this specific alert, use your mouse to select and copy the id
field from the display and use ti in the command that is shown on the next tab.
Using your mouse to select and copy the id from the previous display, show the
full text of the alert. Note that the show subcommand is after the -id option. From
this output, you can determine that the NAS server cannot reach a domain
controller. Under events, there is a suggestion of how to correct the problem.
The default format for show commands is table. The width of the columns is limited
due to the width of your window. Note the minus sign (-) on -sort severity-.
The default sort order is ascending. The minus sign changes it to sort by severity
in descending order.
NVP Format
The default output format is table, as shown on the previous tab. You can also
show events or alerts in name-value pair (NVP), comma-separated values
(CSV), or JavaScript Object Notation (JSON). NVP format shows the full value
of each field name and its value, since it uses one field per line. To display
specific fields and types of events, use some of the options listed on the first
tab. You can use most of these options for events as well as alerts.
Here are four events showing specific fields in NVP format, sorted by severity in
descending order:
CSV Format
You can output the same data to CSV format for use with a spreadsheet, such as
Microsoft Excel. PSTCLI does not allow redirection of output the way Windows
command prompt and UNIX or Linux shells do. To output to a CSV file on your
client system:
1. Exit from session mode back to the command prompt or UNIX/Linux shell.
2. Run PSTCLI from the prompt, providing destination, username, password, and
selection fields. Omit the -session option. Redirect the output to a file. Note: If
you do not specify a password, the system waits for you to enter it, but the
prompt is hidden.
Events are similar to alerts. An alert is a summation of one or more events that
need or needed attention. Many events do not generate an alert, so there are more
events than alerts. In the example of showing alerts, all the alerts fit one screen.
The same system could have 100,000 events, so scrolling through them may be
impractical.
Use the help event show command to list the syntax of the command. It uses
most of the same options as the alert show command. The highlighted options,
-sort, and -select, can be used with the fields listed—and -limit.
By default, event show displays the first 100 events in a table. You have most of
the same options as with alerts.
NVP Format
To display specific fields and types of events, use some of the options listed on
the first tab.
Here are the first four events, showing the most important fields in NVP format
sorted by severity:
Hardware Help
To display the list of available hardware command options, use the help
hardware command. As with other commands, you can select which fields to
display and sort by most fields. Here is a partial list of the help for that command:
If you suspect a problem with the network, you can get a listing of the network
status. As with other commands, there are many options available to display what
you want. Use the help network command to see the list of options.
Network Help
You can change network settings as well as show them. Note the multiple options
for ip_pool_addresses highlighted below. See the next tab for an example.
Show Command
If you have SMB or NFS volumes set up on a PowerStore T system, you can view
their status using the commands that are shown here.
If there are NAS servers running on the PowerStore T system, you can list them
with the following command:
By the names in the example above, you can see that one server is intended for
NFS while the other is intended for SMB. Each server uses its own IP address.
Note that the names the administrator chose for the NAS servers do not define
their purpose.
The smb_server show command displays any SMB servers and their
corresponding domain or workgroup and NAS servers.
The smb_share show command displays SMB shares. In this example, only one
share exists on the system. Add -help to either command for a complete list of
options.
To list all the file systems, use the file_system show command:
To see what other fields are available to select with this command, type
file_system show -help.
You can connect to the PowerStore CLI (PSTCLI) using a downloaded program on
a workstation or from a Service Container session on the maintenance node. The
commands are intended to be the same on both versions. However, the version of
PSTCLI installed on the maintenance node may be different from the version that is
installed on a workstation. Commands may vary between versions.
Connect to PSTCLI
PowerStore CLI:
Can show alerts and events
Can show hardware, network, and NAS properties
Refer to this guide for more information: PowerStore CLI User Guide.
Serviceability
IPMI Overview
The IPMI connection allows you to login to the system as service user, as you
would normally do. The Service docker runs on both nodes, and is the docker
from which all system service scripts and pstcli commands are conducted. SSH
sessions and IPMItool sessions using Serial over LAN, and the Serial Console all
gain access to the Service docker.
It also allows you to monitor the boot process (Serial Over LAN), or interrupt the
boot sequence if needed.
Service Laptop
The laptop can be physically connected to the PowerStore T on either Service LAN
port, or both if a hub or switch is available.
Multiple appliances should never be connected to the same hub or switch as the
nodes use the same internal IP(s).
Never connect multiple appliances to the same hub/switch for Service LAN Port
access. DO NOT use the ToRs.
DO NOT remove the customer management cables as this will make the system
inaccessible to the customer over the network (affects mgmt only)
IP: 128.221.1.249
Netmask: 255.255.255.0
Gateway: none
Node IP addresses
Once the physical connection is established, and the service laptop is configured
with the relevant IP(s), you can verify the connectivity to the PowerStore T using
the ping command. These IP(s) are internal to the node, and not configurable.
Node A: 128.221.1.252
Node B: 128.221.1.253
If you cannot ping to each node, check your service laptop settings and physical
connections. IPMI will not work if a ping command fails. The example shows a
successful ping to Node A
Establish a Connection
Once you are all setup and confirmed that you can ping the IP(s) you can use IPMI
to establish the connection. The most common reason for connection failures is
using the incorrect password in the command line. The password should be the
Dell EMC Service Tag in all Caps.
Important: If the previous session was not cleaned up, you can get
an error with this command. To clean up the previous session,
deactivate it first:
ipmitool.exe -I lanplus -C 3 -U console -P 1234XYZ
-H 128.221.1.252 sol deactivate
PowerStore T:
IPMItool example
The example shows the entry into the service container after a successful login
using IPMItool. From the service shell, you can run a number of svc commands to
get a status of various components. Note the shell is restricted and you must inject
root access to perform some operations.
PowerStore allows customers, tech support, and field to login to the system over
ssh or PowerStore Manager using the Service LAN Ports.
The example shows the IP address needed for an ssh or PowerStore Manager
connection.
Service Laptop
The laptop can be physically connected to the PowerStore T on either Service LAN
port, or both if a hub or switch is available.
Multiple appliances should never be connected to the same hub or switch as the
nodes use the same internal IP(s).
Never connect multiple appliances to the same hub/switch for Service LAN Port
access. DO NOT use the ToRs.
DO NOT remove the customer management cables as this will make the system
inaccessible to the customer over the network (affects mgmt only)
IP: 128.221.1.249
Netmask: 255.255.255.0
Gateway: none
Node IP addresses
Once the physical connection is established, and the service laptop is configured
with the relevant IP(s), you can verify the connectivity to the PowerStore T using
the ping command. These IP(s) are internal to the node, and not configurable.
Node A: 128.221.1.250
Node B: 128.221.1.251
If you cannot ping to each node, check your service laptop settings and physical
connections. IPMI will not work if a ping command fails. The example shows a
successful ping to Node A.
Open a PuTTY session and use the IP address for the Service Port. The example
shows a session for Node A using the Service Port IP of 128.221.1.250. Note the
Port is set at 22 for the connection. Once connected, log into the PowerStore using
the service credentials. Issue the svc_help command to view the options.
Once you have established a successful ssh session to a node, you can log into
the peer node using ssh from the local node. You are still restricted from using
some Bash shell commands.
Place the node service port IP address into your browser to access the PowerStore
Manager interface. The example a shows a PowerStore session to Node A using
the IP address of Node A's service port.
Serviceability:
Use ssh connection to connect to the PowerStore T nodes when the system is
in a unknown or bad state to troubleshoot issues.
Troubleshoot PowerStore by connecting to the system over ssh or PowerStore
Manager over the Service LAN Ports.
Service Container
There are two CLI programs available for managing PowerStore systems.
Service Container
PSTCLI
To access the Service Container use a terminal emulator to connect to one of the
management addresses or hostname using SSH on port 22. This example uses
PuTTY:
1. Open PuTTY.
2. Connect to one of the management addresses or hostname using SSH on port
22:
svc_diag Command
PowerStore Container commands run scripts of the same name. The svc_diag
command (script) displays many different pieces of system information, depending
on which subcommands and options you use. The syntax for this command is
shown in the first tab:
Command Syntax
Add an action subcommand, such as list, from basic help to get more specific help:
To get the Node ID, Appliance Name, Service Tag, Model, IP address, and other
information, use the following command: svc_diag list --info. This
command only displays information about the current node.
1234XYZ
To list fault status for various hardware components, use the following command:
svc_diag list --hardware --sub_options fault_status
svc_journalctl Command
The svc_journalctl command (or script) enables you to view log messages
from the system journal in a consistent format. It also enables you to specify
additional arguments and filter or display additional information. Use this command
as a triage tool to troubleshoot issues.
For a complete list of fields, see the Dell EMC PowerStore Service Scripts Guide.
The -S (or --since) and -U (or --until) options specify a range of time in
the format: YYYY-MM-DD hh:mm:ss
By default, the search uses the timezone on the system. With the --utc
option, it uses Coordinated Universal Time (UTC).
The -g (or --grep) option searches for specified regular expression in the file.
You can also pipe the command to the egrep command for a more complex
search.
In this example, the command looks for messages with a priority of 3 (ERROR),
contain the string "controlpath" and occurred within 4:00 and 6:00 on 12-March-
2020. After you locate the error which identifies the problem, specify a smaller time
range with no other options to see what other events occurred near the error.
Certain commands are restricted from the service account. Accessing the root
account. This process is referred to as inject root. Use the following procedure:
If the PowerStore system is running, but the GUI interface is inaccessible, here are
some troubleshooting tips.
Service commands are available using SSH and logging in with the service
credentials.
This status shows that the Control Path is running, but it may be unresponsive
or in an error state. Go to the next step to dig deeper.
2. Check the journal logs with the svc_journalctl command with the -f (or -
-follow) option, which keeps the command active so that new log entries are
displayed as they occur. Use the -g (or --grep) option to filter the command to
see only st_io_monitor status:
Use the commands shown here to collect PowerStore log files. You can also
generate logs specific to one type of service. For example, to check the status of
PowerStore T NAS service, use the commands that are shown here.
To generate a specific log file, use the svc_dc run -p profile command,
where profile is one of the following:
All normal and detailed bundles include the NAS logs. If you only need the NAS
logs, you can use the NAS profile:
Important: Since the job may take a long time to run, add an
ampersand (&) to the end of the command to run the job in the
background. This action allows you to run other commands while
the job runs. The system notifies you when the job completes, or
you can use the jobs command to check the status.
2. Since the svc_dc run command specified a profile of nas, look for a bundle
with that profile. To list and find your bundle, use the svc_dc list command:
3. Use the ls -l command to list out the files in your directory in a long format,
and look for a file with a pointer to 191cc8a6-baf7-4ac0-861d-
fe408ddc1642:
The l in the first column of each row means that the file is a symbolic link, or
pointer, to a file in the /cyc_var/cyc_service/data_collection folder,
indicated by the ->
Note that each line wraps to the line below, so the id spans two lines.
Use an application, such as Winscp, to download the file to a system where you
can examine the contents. The the application does not accept symbolic links,
copy the oringal file from the subfolder of
/cyc_var/cyc_service/data_collection to your home directory, giving
the new file a different name.
The data collections are critical to Dell EMC, as they provide the ability to diagnose
and repair issues on PowerStore systems.
Data collections can be run manually using PowerStore Manager or the svc_dc
commands.
Listed are the goals and capabilities for data collection on a PowerStore system:
High Availability
Reduced collection size
Customer convenience
Full cluster collection or single appliance collection
Download from the array, upload to support
GUI and service script support
TIP: You can request the collection of support materials for one or
more appliances.
When you request a support materials collection, data is always
collected at the appliance level. For example, if you request a
collection for a volume, the system collects support materials for the
appliance that contains the volume. If you request a collection for
multiple volumes, the system collects support materials for all
appliances that contain the volumes.
By default, data collections are collected daily (24 hrs) by the system from all
appliances. You can manually initiate a data collection at any time.
Data Collections are managed and collected at the appliance level. Data
Collections can run on both appliances or a single appliance depending on the type
of collection. For example, if a data collection is started on a single appliance or
volume on a single appliance, only that appliance stores the files. The files are not
stored on other appliances. In the example, Data Collection 2 and Data
Collection 4 were run on a single appliance.
Cluster
Appliance 1 Appliance 2
Node A Node A
Node B Node B
Support materials are collected using the PowerStore Manager or the svc_dc
commands from the service shell.
The example shows a successful data collection that is initiated from the Settings
> Support Materials window. Both appliances were selected. The data collection
file Initial Configuration and Data Collection 3 were created on both appliance
with the same name and identifier.
Data is always collected at the appliance level. You may include additional
information in the data collection by selecting the Advanced support materials
collection option. The Advanced option collects additional system information and
requires additional space on the Node. Advanced collections can take longer than
the default data collection. The system runs one collection job at a time.
Movie:
The web version of this content contains a movie.
Procedure:
Select the Settings icon, and then select Support Materials in the Support
section.
Click START COLLECTION.
Select the type of support data that are needed and the appliances for which
to collect support information.
Optionally, write a description of the collection. This description is displayed in
the list of support materials on the Support Materials page and can help you
recognize the collection.
Select Send to Support if you want the system to automatically send the
collection to Dell EMC Support when the job completes. This option is only
enabled when remote support through Secure Remote Services is enabled on
the system. You can also send the collection to Dell EMC Support later.
Select Recent Jobs to monitor the support collection job. When the collection
job completes, the system posts the job information, including its status, on the
Support Materials page.
Movie:
The web version of this content contains a movie.
Procedures:
Select the storage object type from the Dashboard > Storage tab.
Open the More Options tab > Gather Support Materials.
From the Collect Support Materials page, type a description.
Select the Send materials to Support when finished box. Note this is
available only if SupportAssist is enabled.
Optionally, open the Advanced Support Materials text and select the box to
include additional information. Do this only when directed by support personnel,
as the collection process takes a considerably longer.
Alerts - Remediation
Movie:
The web version of this content contains a movie.
Procedures:
In addition to the Settings > Support Materials page, you can execute Gather
Support Materials from the Hardware page. The example shows a data collection
being done on TwoApplianceCluster appliance-2.
Movie:
The web version of this content contains a movie.
Procedure:
From the Hardware page, select The appliance for the data collection
From the More Actions drop-down, select Gather Support Materials
From the Gather Support Materials page, provide a Description
Select the icon to expand Advanced support materials collection options, if
needed
Check the box to Include additional information
Select the START button
Once data collection completes, you can DOWNLOAD the file to a host, SEND TO
SUPPORT or DELETE it.
Select the checkbox for the data collection files you want to act on, then select the
option you want. The SEND TO SUPPORT option is only available if the
SupportAssist page is configured.
Movie:
The example shows the download process. The Initial Configuration data
collection includes files from both appliances. Once the files are selected, it is
downloaded to the Downloads directory on the localhost. The output is a .tgz file.
Optionally, the file can be exported in either a .csv or .xlsm file to the same
Downloads directory.
1. Select the file.
2. Click the DOWNLOAD.
3. Select the file to download if both service and dump files are available. There
could be dump file or regular system collect files.
The svc_dc (data collect) command set is used to manage data collections on the
PowerStore. All commands can be found in the PowerStore Service Scripts
Guide. Service commands are available from the Service shell using SSH, Port
22, and logging in with the service credentials. The service shell is restricted and
limits your ability to run certain commands.
svc_dc run
The svc_dc run command generates a new data collection on the local
appliance using the default profile. Each appliance in a cluster generates its own
data collection archive and stores it locally on that appliance. The example
generates a new data collection on appliances FNM00191700631 and
FNM00191500463 using the Essential and Detailed profiles. Use the svc_dc
run -h option for additional details.
svc_dc list
The svc_dc list command lists all data collections, or details for one collection.
Each data collection is identified by an ID. Use the ID in the command to get details
of the collection. For example svc_dc list 949af06e-7896-4b36-9f29-
d3871a13ad6.
svc_dc download
The svc_dc download command allows you to download a data collection file to
a Linux host. The commands requires an IP address, path, username, and
password of the remote Linux host on which the collection is placed. If the
PowerStore contains data collection several files, you can select the file you want
by entering the Index number of the file.
The file transfer uses the SCP protocol on TCP port 22. When the file transfer is
underway, there is no indication of progress, which could take several minutes to
an hour to complete.
In the example, The file indicated by Index 1 is downloaded to the Linux host into
/opt directory.
svc_dc delete
Since data collects require space, it may be advantageous to delete files that are
no longer needed. The svc_dc delete command displays a list of files on the
PowerStore and allow you to delete any or all of them.
The example shows the file with Index 1 will be deleted from the PowerStore
database.
Blink LED
regular expression
Used in UNIX or Linux utilities such as grep--A string that can be used to describe a
sequence of characters, including their position on a line. For example, with the
grep command, "^Mar" searches for a line that begins with "Mar". The regular
expression "arch$" searches for a line that ends with "arch".