Documente Academic
Documente Profesional
Documente Cultură
ii
Table of Contents
Preface ...................................................................................................... xi
Audience ...............................................................................................................xi
Organization .........................................................................................................xi
Conventions .........................................................................................................xii
Overview of Dell EqualLogic Products ...............................................................xii
Technical Support and Customer Service ............................................................xv
iii
CLI Reference
Table of Contents
iv
CLI Reference
Table of Contents
CLI Reference
Table of Contents
vi
CLI Reference
Table of Contents
vii
CLI Reference
Table of Contents
viii
CLI Reference
Table of Contents
ix
CLI Reference
Table of Contents
Preface
The Group Manager command line interface (CLI) lets you manage a PS Series group
an affordable, scalable storage area network (SAN) that is easy to set up and operate. You
can also use CLI commands to manage a specific array for maintenance purposes.
For information about using the Group Manager graphical user interface (GUI) to manage
a group, see the PS Series Group Administration manual.
Audience
The PS Series documentation is designed for administrators responsible for managing a
PS Series group. Administrators are not required to have extensive network or storage
system experience. However, it is helpful to understand:
In addition, administrators may find it useful to understand the basic concepts for:
Network topologies
RAID configurations
Organization
This manual is organized as follows:
xi
CLI Reference
Preface
Chapter 4, Global Commands includes the commands that control CLI behavior.
Appendix A, Third-Party Copyrights, lists the third-party copyrights for software used
in the product.
Conventions
Typographical conventions are shown in the following table.
Convention
Usage
fixed_width_italics
text1 | text2
parameter ...
option[,...]
[parameter]
.
.
.
xii
CLI Reference
Preface
Firmware Installed on each array, PS Series firmware allows you to manage your
storage environment and provides capabilities such as volume snapshots, cloning, and
replication to protect data hosted on the array in the event of an error or disaster.
Group Manager GUI: Provides a graphical user interface for managing a group.
Group Manager CLI: Provides a command line interface for managing a group.
Manual Transfer Utility (MTU) Runs on Windows and Linux systems and enables
you to use physical media to securely transfer large amounts of data to a replication
partner, facilitating replication and preventing network congestion.
Remote Setup Wizard (RSW): Initializes new PS Series arrays, configures host
connections to a group, and configures and manages multipathing.
VSS and VDS Provider Services: Allows backup software vendors to perform offhost backups.
Storage Replication Adapter for Site Recovery Manager (SRM): Allows SRM to
understand and recognize PS Series replication for full SRM integration.
xiii
CLI Reference
Preface
Current Customers: You may not be running the latest versions of the software listed
above. If you are under a valid warranty or support agreement for your PS Series array,
you are entitled to obtain the latest updates and new releases as they become available.
Related Documentation
For detailed information about PS Series arrays, groups, volumes, array software, and host
software, see the documentation shown next.
PS Series Documentation
xiv
CLI Reference
Preface
Contacting Dell
Dell provides several online and telephone-based support and service options. Availability
varies by country and product, and some services may not be available in your area.
For customers in the United States, call 800-945-3355.
If you do not have an Internet connection, you can find contact information on your
purchase invoice, packing slip, bill, or Dell product catalog.
To contact Dell for sales, technical support, or customer service issues:
1. Visit support.dell.com.
2. Verify your country or region in the Choose A Country/Region drop-down menu at
the bottom of the window.
3. Click Contact Us on the left side of the window.
4. Select the appropriate service or support link based on your need.
5. Choose the method of contacting Dell that is convenient for you.
Online Services
You can learn about Dell products and services on the following websites:
www.dell.com/
xv
CLI Reference
support.dell.com
support.dell.com/EqualLogic
xvi
Preface
Use a network connection. From a computer, use telnet or SSH to connect to the
group (or management) IP address orif you are running array management
commands on a specific arrayconnect to an IP address assigned to a network
interface on the array.
Use a serial connection. Set up a serial connection to the array, as appropriate for the
control module model. Make the connection to serial port 0 on the active control
module (the ACT LED will be green). Use the serial cable that shipped with the array.
See the Hardware Maintenance manual shipped with your array for more information.
The serial connection must have the following characteristics:
9600 baud
No parity
8 data bits
1-1
CLI Reference
Once connected to the group (or an array), press the <Enter> key and log in to a group
administration account (for example, grpadmin). You can then enter CLI commands at
the command prompt.
The following example shows how to use telnet to log in to a group. The password is
not shown on the screen.
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
group1>
Command Types
The CLI commands are divided into the following categories:
Group management commands. These commands manage the group, members, and
volumes. They use a tree structure and generally have subcommands, parameters, or
variables.
See Chapter 2, Group Management Commands, for detailed information about
command formats and examples.
Global commands. These commands can be used anywhere in the CLI tree structure.
See Chapter 4, Global Commands, for detailed information about command formats
and examples.
1-2
CLI Reference
1-3
CLI Reference
CLI help messages have two components, as shown in the following example.
> member select ?
<name>
If the component to the left is in angle brackets (<>), it indicates that you must replace the
variable. If the component to the left is not in angle brackets, it indicates that you must
specify the parameter itself (and possibly a variable).
You can also see help on editing the command line itself, with the help edit command:
Available editing keystrokes
Delete current character.....................Ctrl-d
Delete text up to cursor.....................Ctrl-u
Delete from cursor to end of line............Ctrl-k
1-4
CLI Reference
In addition, you can press the <Tab> key to automatically complete a command after
entering a unique portion of the command. This can be useful in completing long
commands or subcommands.
For example, entering grp and then pressing the <Tab> key is the same as entering
grpparams:
> grp<Tab>
> grpparams
1-5
CLI Reference
In some cases, you can use subcommand mode to simplify entering repetitive commands
related to the same component (for example, a volume or member). Subcommand mode is
available with the grpparams command and with commands that use the select
subcommand.
To use subcommand mode with the grpparams command, enter the command without
any parameters and press the <Enter> key. At the resulting grpparams prompt, you can
enter parameters, pressing the <Enter> key after each one. When you are done, enter the
exit command to leave subcommand mode.
With commands that use the select subcommand, select the component and press the
<Enter> key. You can then enter parameters.
For example, the following commands create a volume and then use subcommand mode
to specify a description for the volume and change the permission to read-only:
> volume create dbvol 100
> volume select dbvol
volume dbvol> description Staff Database
volume dbvol> read-only
volume dbvol> exit
Using subcommand mode is optional. The following example uses two complete
command lines to specify a description and read-write permission for a volume.
> volume select mailvol description Staff Mail
> volume select mailvol read-write
There can be multiple levels of subcommand mode when a command uses multiple
select subcommands. Use the exit command to leave one level at a time. Use the exit
all command to leave subcommand mode.
1-6
CLI Reference
Whether to enable or disable the automatic logout of idle CLI sessions after 1 hour of
inactivity.
Screen height
Column width
The stty command also displays the current settings and the type of terminal in use.
See stty on page 4-14.
1-7
Description
account
alerts
chapuser
collection
failback
grpparams
member
mrtg-config
Creates a file for use with the Multi-Router Traffic Grapher (see
mrtg-config on page 2-96).
partner
pool
show
save-config
snapcol
volume
2-1
CLI Reference
account
Manages local administration accounts.
You can create the following types of accounts:
Group administrator Can manage the entire group and all storage pools.
Pool administrator Can manage only the objects (volume and members) that are in
the pool or pools specified by the account. Pool administrators can also optionally
monitor the entire group.
Note: You can also manage administration accounts using external RADIUS servers to
perform the authentication. See grpparams radius-acct-list on page 2-64.
Format
account subcommand
Subcommands
create
delete
Deletes an account.
select
show
account create
Creates an administration account.
Unless you specify pools for the administrator to manage or read-only privilege, the
account will be a group administrator account with the ability to manage the entire group
and all pools.
When you create an account, you must enter the new account password twice. The
password is not shown on the screen. An account password must be between 3 and 16
alphanumeric characters and is case-sensitive. (Only the first 8 characters are validated).
2-2
account
CLI Reference
Format
account create account [parameter ...]
Variable
account
Parameters
description text
permission
group-read-access
enable | disable
contact name
email email_address
phone phone_number
mobile phone_number
pool-admin list
account
2-3
CLI Reference
Examples
The following command creates a pool administration account that can manage the objects
in the default and dbase pools:
> account create userbob pool-admin default,dbase
Enter password:
Retype password:
Account creation succeeded.
The following command creates a pool administration account that can manage the objects
in the pool2 pool, and can see all other objects in the group:
>
Enter password:
Retype password:
Account creation succeeded.
account delete
Deletes an administration account.
Note: You cannot delete the default grpadmin account.
Format
account delete account
Variable
account
2-4
Name of an account.
account
CLI Reference
Example
account select
Shows or modifies an account.
You cannot modify the name of an account. Instead, you must delete the account and then
add it with the new name.
To remove a name, phone or mobile number, e-mail address, or description, enter two
quotation marks ().
Format
account select account parameter ...
Variable
account
Name of an account.
Parameters
contact name
description text
disable
email email_address
enable
group-admin
account
2-5
CLI Reference
group-read-access
enable | disable
mobile phone_number
passwd
permission
pool-admin list
Specifies the pools that the pool administrator can manage. Pool
names must be separated by commas only (no spaces).
show
Examples
The following command modifies the password for the grpadmin account:
> account select grpadmin passwd
Enter New Password:
Retype Password:
2-6
account
CLI Reference
The following command changes the monitor account to be a pool administrator (with
read-write permission by default) for the pools staff and sales:
> account select monitor pool-admin staff,sales
The following command lets the pool3admin account monitor all other objects in the
group (does not change the ability to manage objects in their pools):
> account select pool3admin group-read-access enable
The following command removes the group-read-access permission from the pool
administrator account kristen:
> account select kristen group-read-access disable
The account still has read-write access on all objects in its designated pool or pools, but
can no longer see other objects in the group.
account show
Shows all administration accounts or information about a specific account.
Specify the active parameter to display the accounts currently logged in to the group.
For users logged in through the GUI, the active parameter also shows the remote IP
address of the user and the local IP address (that is, the group or member IP address to
which the user is connected).
Format
account show [account] [active]
account
2-7
CLI Reference
Variable
Name of an account.
account
Examples
Permission
---------read-write
read-only
Privilege
----------group-admin
group-admin
Status LastLogin
-------- -----------------enable 2009-01-02:13:20:17
enable 2009-01-02:12:02:42
The following command shows the accounts currently logged in to the group:
> account show active
Name
-------grpadmin
monitor
Type
-----telnet
gui-ssl
StartTime
--------------------2009-03-22:14:36:05
2009-03-23:17:16:25
Remote IP
Local IP
------------ ---------182.12.22.12 182.1.15.2
2-8
account
CLI Reference
alerts
Sets the event priorities for e-mail and syslog event notification.
When you enable an event notification method, by default, events with fatal, error, or
warning priority result in notification. You can change the notification event priorities.
Table 2-2 shows event priorities in order of decreasing severity.
Table 2-2: Event Priorities
Priority
Description
FATAL
ERROR
WARNING
Potential problems in the group. May become an event with error priority if
administrator intervention does not occur.
INFO
Normal operational and transitional events in the group that are of interest to
administrators but do not require intervention. Setting this priority can result in a
large number of notifications.
To enable e-mail notification, see grpparams email-notify on page 2-52. To enable syslog
notification, see grpparams syslog-notify on page 2-73.
Format
alerts subcommand
Subcommands
select
show
alerts select
Specifies one or more event priorities for the selected type of event notification.
You can also use this command to stop e-mail or syslog notification.
alerts
2-9
CLI Reference
Format
alerts select method priority filter | show
Variable
method
priority filter
Subcommand
show
Examples
The following command configures a remote syslog server to receive only events with
error and fatal priorities:
> alerts select syslog priority error,fatal
The following command shows the event priorities for e-mail notification:
> alerts select email show
Priority is :: warning,error,fatal
alerts show
Shows the event priorities that result in e-mail and syslog notification, if enabled.
Format
alerts show
2-10
alerts
CLI Reference
Example
The following command shows the event priorities for e-mail and syslog notification:
> alerts show
Notification Method
-----------------------------Email
SysLog
alerts
Priority
------------------warning,error,fatal
error,fatal
2-11
CLI Reference
chapuser
Manages local CHAP (Challenge Handshake Authentication Protocol) account names and
passwords that the group uses to authenticate iSCSI initiator access to iSCSI targets
(volumes and snapshots).
Notes: Performance can decrease if you have more than 100 local CHAP users. You can
use an external RADIUS server for initiator authentication if you have a large
number of local CHAP users. See grpparams radius-auth-list on page 2-67.
In addition to iSCSI initiator authentication, you can use target authentication. See
grpparams target-auth-password on page 2-74 and grpparams
target-auth-username on page 2-74.
Format
chapuser subcommand
Subcommands
create
delete
rename
select
show
chapuser create
Creates a local CHAP account for iSCSI initiator authentication.
Requirement: To enable local CHAP authentication of iSCSI initiators, see grpparams
iscsi-local-auth on page 2-56.
Recommendation: To prevent unauthorized hosts from connecting to targets only
protected with CHAP, see grpparams discovery-use-chap on
page 2-50.
After creating a local CHAP account, set up an access control record for the volume and
specify the account name. See volume select access create on page 2-185.
2-12
chapuser
CLI Reference
Format
chapuser create name [enable | disable] [password password]
Variable
name
Parameters
enable | disable
password password
Example
chapuser delete
Deletes a local CHAP account.
Format
chapuser delete name
chapuser
2-13
CLI Reference
Variable
name
Example
chapuser rename
Renames a local CHAP account. CHAP user names are case-sensitive.
Format
chapuser rename old_name new_name
Variables
old_name
new_name
Example
chapuser select
Modifies or shows the selected local CHAP account.
Format
chapuser select name show | parameter
2-14
chapuser
CLI Reference
Variable
Name of a CHAP account. CHAP user names are case-sensitive.
name
Subcommand
Shows details for the selected CHAP account.
show
Parameters
enable | disable
passwd [password]
Example
The following command shows details about the selected CHAP account:
> chapuser select testchap show
_____________________ ChapUser Information ___________________
Name: testchap
Password: ZZJZRXPP2jRhrXZR
Status: enable
chapuser show
Shows all local CHAP accounts or details about a specific account.
Format
chapuser show [name]
Variable
name
Examples
The following command shows the local CHAP accounts in the group:
> chapuser show
chapuser
2-15
CLI Reference
Name
-----------------------------guest
tchen
2-16
Password
------------------0ZBHX0HBXbHPpbxB
8ZP2b8BZRJP2BBBb
Status
---------enable
enable
chapuser
CLI Reference
collection
Manages the volume collections in a group. A volume collection is a set of one or more
volumes (up to eight) grouped together for the purpose of creating simultaneous snapshots
of the volumes in the collection (snapshot collection) or simultaneous replicas of the
volumes in the collection (replica collection).
Note: See snapcol on page 2-170 for information on creating snapshot collections. See
collection select replication on page 2-21 for information on creating replica
collections.
Format
collection subcommand
Subcommands
create
delete
Deletes a volume collection. This will not delete the volumes in the
collection.
rename
select
show
collection create
Creates a volume collection in the group.
Format
collection create collection_name volume[,volume,...] [description text]
Variables
collection_name
collection
2-17
CLI Reference
volume
text
Example
The following command creates a volume collection that includes two volumes:
> collection create dbasecol db1,db2 description Dbase Collection
Volume collection creation succeeded.
collection delete
Deletes a volume collection. The volumes in the collection are not deleted.
Format
collection delete collection_name
Variable
collection_name
Example
collection rename
Renames a volume collection.
2-18
collection
CLI Reference
Format
collection rename old_name new_name
Variables
old_name
new_name
Example
collection select
Selects a volume collection so that you can perform additional operations on it.
See snapcol on page 2-170 for information on creating snapshot collections.
Format
collection select collection_name subcommand | description text
Variable
collection_name
Subcommands
add
delete
description text
replication
schedule
show
collection
2-19
CLI Reference
Example
Variables
collection_name
volume_name
Name of a volume.
Example
Variables
collection
volume_name
Name of a volume.
2-20
collection
CLI Reference
Example
The following command deletes the last volume from a volume collection, and also
deletes the collection:
> collection select coll-2 delete vol-data01
There is only one volume in the volume collection. Deleting this volume
from the collection results in deletion of volume collection. Snapcols
created using this volume collection will continue to exist. Do you really
want to delete the volume from volume collection? (y/n) [n] y
Variable
collection_name
Subcommands
create-repcol
disable
enable
select
collection
2-21
CLI Reference
show
Variables
collection_name
partner
Name of the replication partner that will store the replica collection
(the secondary group).
Subcommand
manual
Examples
The following command creates a replica collection by using manual transfer replication:
> collection select kcoll1 replication create-repcol manual delta
2-22
collection
CLI Reference
Variables
collection_name
partner_name
Example
The following command disables replicating a volume collection to the partner bgroup:
> collection select dbcollection replication disable bgroup
Variables
collection_name
partner_name
collection
2-23
CLI Reference
Example
The following command enables replicating a volume collection to the partner agroup:
> collection select dbcollection replication enable agroup
Variables
collection_name
partner_name
Example
The following command shows information about volume collection replication activity
to a partner:
> collection select dbcollection replication select groupb show
Variables
collection_name
partner_name
2-24
collection
CLI Reference
Example
The following command shows information about the replication partner configured for
the volume collection:
> collection select dbcollection replication show
Variable
collection_name
Subcommands
create
Creates a schedule.
delete
Deletes a schedule.
rename
Renames a schedule.
select
show
collection
2-25
CLI Reference
Schedule name
Schedule type
Optionally, you can specify other parameters, based on the schedule type. To specify more
than one parameter, separate them with commas and no spaces.
Format
collection select collection_name schedule create schedule_name parameters
Variables
collection_name
schedule_name
Parameters
enable | disable
end-date mm/dd/yy
Month, day, and year that the schedule will stop. The default
is no ending date.
frequency nmins |
nhour[s]
max-keep n
partner partner_name
2-26
collection
CLI Reference
read-write | read-only
repeat-interval ndays
start-date mm/dd/yy
Month, day, and year that the schedule will start. The default
is the day that the schedule was created (or the following day,
if the starting time has passed).
type schedule_type
Examples
The following command sets up a schedule that creates a replica collection of a volume
collection every day at 11:30 PM:
> collection select db1col schedule create dailydbsch type daily \
start-time 11:30PM repeat-interval 1days partner psgroup2
Schedule creation succeeded.
The following command sets up a schedule that creates a snapshot collection of a volume
collection every day, every 2 hours, from 7:00AM to 8:00PM:
> collection select mailcol schedule create mailsch type daily \
start-time 07:00AM end-time 20:00 frequency 2hours \ repeat-interval 1days
Schedule creation succeeded.
collection
2-27
CLI Reference
Variables
collection_name
schedule_name
Name of a schedule.
Example
Variables
collection_name
old_name
Name of a schedule.
new_name
Example
2-28
collection
CLI Reference
Note: You cannot modify the partner for a replication collection schedule. Instead, delete
the schedule and then create a new schedule with the correct partner.
Format
collection select collection_name schedule select schedule_name show |
parameter
Variables
collection_name
schedule_name
Name of a schedule.
Parameters
enable | disable
end-date mm/dd/yy
frequency nmins |
nhour[s]
max-keep n
read-write | read-only
repeat-interval ndays
start-date mm/dd/yy
type schedule_type
collection
2-29
CLI Reference
Examples
The following command changes the time that snapshot collections of volume collection
staffcol are created with the schedule backup:
> collection select staffcol schedule select backup start-time 10:15PM
Variables
collection_name
schedule
Name of a schedule.
Example
The following command shows the snapshot and replication collection schedules for the
volume collection dbcol:
> collection select dbcol schedule show
Name
Interval DateRange
------ -------- --------Daily daily
03/28/08-None
2009
2-30
TimeRange
Frequency NextCreate
----------------- ---------12:00AM-12:00AM
Fri Apr 4 00:00:00
collection
CLI Reference
Variable
collection_name
Example
collection show
Shows all the volume collections in the group or detailed information about a specific
collection.
Format
collection show [collection_name]
Variable
collection_name
collection
2-31
CLI Reference
Example
The following command shows all the volume collections in the group:
> collection show
Name
-------------------hrcollection
dbcol
2-32
NoOfVolumes
----------2
3
NoOfSnapcols
------------0
2
collection
CLI Reference
failback
Failback is the third step in recovering replicated data from the secondary group when the
primary group is temporarily unavailable, either because of maintenance or failure:
1. Fail over to the secondary group. This step involves promoting the volumes inbound
replica set to a recovery volume. See partner select inbound-replicaset select promote
on page 2-133.
2. Replicate to the primary group. After the primary group and the original volume
become available, this step involves demoting the original volume to a failback replica
set and replicating the recovery volume to the primary group. See volume select
replicate-to-primary on page 2-193.
3. Fail back to the primary group. When you are ready to fail back, this step performs a
final replication, demotes the recovery volume to the original inbound replica set, and
promotes the failback replica set to the original volume.
All steps are performed on the secondary group in the volume replication configuration.
The replicate-to-primary step and the failback step include multiple tasks that must
complete before you can perform the next step.
You can start or stop failback operations, display in-process and completed operations, or
retry a failback operation if an error occurs. Examine event messages to identify any
problems. If a problem occurs, correct it and retry the operation.
Format
failback subcommand recovery_volume_name
Subcommands
retry recovery_volume_name
show
start [manual-replica]
recovery_volume_name
stop recovery_volume_name
failback
2-33
CLI Reference
Variable
Name of a recovery volume.
recovery_volume_name
failback start
To start a failback operation, you must enter login credentials so the secondary group can
access the primary group. Enter a valid group administrator account name and password
for the primary group, or a pool administrator account and password that has permission to
manage the pool containing the original volume.
You can optionally use manual transfer replication to perform the failback operation. See
the Manual Transfer Utility documentation.
Format
failback start [manual-replica] volume_name
Variable
volume_name
Examples
failback stop
Stops an in-process failback operation and deletes the task.
Format
failback stop volume_name
2-34
failback
CLI Reference
Variable
volume_name
Example
failback show
Displays all failback operations. The output will vary depending on whether operations
are in process or complete.
Format
failback show
Example
recoveryVolumeFinalReplicati 2009-06-17:17:13:14
on
InProgress
StartTime
Error
failback
complete
2009-06-17:17:13:14
2-35
CLI Reference
failback retry
Retries a failback operation that stopped due to an error in one of the tasks. The failback
operation continues from where it stopped.
Format
failback retry volume_name
Variable
volume_name
Example
2-36
failback
CLI Reference
grpparams
Shows or sets group parameters. Changes to group-wide parameters for volumes, such as
thin-provisioning settings and snapshot reserve, apply only to new volumes.
Note: If a parameter accepts multiple values (for example, multiple IP addresses), you
must separate each value with a comma and no space.
Unless otherwise specified, to remove a list, location, or address, enter two quotation
marks ().
Format
grpparams subcommand | parameter
Subcommands
show [list-parameter]
Parameters
cliaccess-ssh enable | disable
cliaccess-telnet enable |
disable
date mm/dd/yy
def-iscsi-alias yes | no
def-language language
grpparams
2-37
CLI Reference
def-mgmt-gateway ipaddress |
none
def-snap-depletion action
snapshots)
snapshots offline)
Applies only to new volumes.
def-snap-reserve n%
def-snap-warn n%
def-thin-growth-max n%
def-thin-growth-warn n%
description text
disallow-downgrades
discovery-use-chap enable |
disable
email-contact email_address
2-38
grpparams
CLI Reference
email-from email_address
email-list email_addresses
group-ipaddress address
group-ipv6address address
iscsi-local-auth enable |
disable
iscsi-radius-auth enable |
disable
isns-server-list ip[:port]
location text
login-radius-acct enable |
disable
login-radius-attr enable |
disable
login-radius-auth enable |
disable
management-network
ipaddress address | ipaddress
none | show
grpparams
2-39
CLI Reference
name group
ntp-server-list ip[:port]
passwd
radius-acct-list ip[:port]
radius-acct-retries n
radius-acct-secrets secrets
radius-acct-timeout n
radius-auth-list ip[:port]
radius-auth-retries n
radius-auth-secrets secrets
radius-auth-timeout n
2-40
grpparams
CLI Reference
show [list-parameter]
isns-server-list
smtp-server-list
email-list
radius-auth-list
syslog-server-list
ntp-server-list
radius-acct-list
smtp-server-list ip[:port]
snmp [subcommand]
syslog-server-list ip[:port]
target-auth-password password
target-auth-username name
time hh:mm:ss
timezone time_zone
vss-vds [subcommand]
webaccess-noencrypt enable |
disable
grpparams cliaccess-ssh
Enables (default) or disables the use of SSH to access the group or a group member, and to
use the CLI.
grpparams
2-41
CLI Reference
Format
grpparams cliaccess-ssh enable | disable
Example
grpparams cliaccess-telnet
Enables (default) or disables the use of telnet to access the group or a group member, and
to use the CLI.
Format
grpparams cliaccess-telnet enable | disable
Example
grpparams conn-balancing
Enables (default) or disables iSCSI connection load balancing across group members.
Format
grpparams conn-balancing enable | disable
Example
2-42
grpparams
CLI Reference
grpparams date
Sets the date for the group members.
Format
grpparams date mm/dd/yy
Variable
mm/dd/yy
Example
The following command sets the date for the group members:
> grpparams date 07/31/08
grpparams def-iscsi-alias
Specifies whether volumes will automatically use the volume name as the iSCSI target
alias (yes, the default).
If this option is disabled, you must manually specify an alias for a volume. Using an alias
is optional. Changing the group-wide setting does not change the settings for current
volumes.
You can override the group-wide setting for a specific volume by using the volume
create command or the volume select command.
Format
grpparams def-iscsi-alias yes | no
Example
The following command specifies that the volume name not be used automatically as the
iSCSI target alias.
> grpparams def-iscsi-alias no
grpparams
2-43
CLI Reference
grpparams def-language
Sets the language for the group.
For the current release, English is the only supported language.
Format
grpparams def-language language
Variable
language
Example
grpparams def-language english
grpparams def-mgmt-gateway
Sets or deletes the default management gateway for the group that uses a dedicated
management network.
The management gateway applies to all the configured management interfaces.
Requirement: You must add a management address to the group. See grpparams
management-network on page 2-60.
Format
grpparams def-mgmt-gateway ipaddress | none
Variable
ipaddress | none
Sets the default gateway for the management network for the group
and the configured management interfaces on all members.
Specify none to delete the default management gateway for the group.
Example
grpparams def-mgmt-gateway 10.119.0.1
2-44
grpparams
CLI Reference
grpparams def-snap-depletion
For new volumes, specifies one of the following group-wide default space recovery
policies when there is no more snapshot reserve:
Changing the group-wide setting does not change the settings for current volumes.
You can override the group-wide setting for a specific volume by using the volume
create command or the volume select command.
Format
grpparams def-snap-depletion delete-oldest | volume-offline
Example
The following command sets the group-wide default to set volumes and their snapshots
offline when the reserved snapshot space has been used:
> grpparams def-snap-depletion volume-offline
grpparams def-snap-reserve
Specifies the group-wide default for new volumes for the amount of space, as a percentage
of the volume reserve, to reserve for volume snapshots.
The default is 100% of the volume reserve.
Changing the group-wide setting does not change the settings for current volumes.
You can override the group-wide setting for an individual volume by using the volume
create command or the volume select command.
Format
grpparams def-snap-reserve n%
grpparams
2-45
CLI Reference
Variable
n
Example
The following command sets the group-wide default for reserved snapshot space to 120%
of the volume reserve. Note that you must specify the percent sign.
> grpparams def-snap-reserve 120%
grpparams def-snap-warn
Specifies the group-wide default threshold at which an alarm occurs when the amount of
free reserved snapshot space is less than this threshold, specified as a percentage of the
total reserved snapshot space. Applies only to new volumes.
The default is 10% of the total reserved snapshot space for a volume.
Changing the group-wide setting does not change the settings for current volumes.
You can override the group-wide setting for an individual volume by using the volume
create command or the volume select command.
Format
grpparams def-snap-warn n%
Variable
n
Percentage of reserved space for the threshold. If free reserved space falls below this
value, a warning occurs.
Example
The following command sets the group-wide default for free snapshot space warning
threshold to 20% of the reserved space:
> grpparams def-snap-warn 20%
2-46
grpparams
CLI Reference
grpparams def-thin-growth-max
Specifies the group-wide default for new thin-provisioned volumes for the maximum
percentage of the reported volume size that can be in use.
The default is 100%.
If the maximum in-use space value is less than 100%, and an initiator write will exceed
this limit, the write will fail, the group will se the volume offline, and the group will
generate event messages.
If the maximum in-use space value is 100%, and an initiator write will exceed this limit,
the volume will not be set offline; However, the write will fail, and the group will generate
event messages.
Changing the group-wide setting does not change the settings for current volumes.
You can override this value on a specific thin-provisioned volume by using the volume
create command or the volume select thin-growth-max command.
Format
grpparams def-thin-growth-max n%
Variable
n
Maximum percentage of the reported volume size that can be in use for a
thin-provisioned volume.
Example
The following command sets the group-wide default to 90% for the maximum percentage
of the volume size that can be in use for a thin-provisioned volume:
grpparams def-thin-growth-max 90%
grpparams
2-47
CLI Reference
grpparams def-thin-growth-warn
Specifies the group-wide default for new thin-provisioned volumes for the in-use space
warning limit. When the in-use space reaches this value, as a percentage of reported
volume size, a warning occurs.
The default is 60%.
Changing the group-wide setting does not change the settings for current volumes.
You can override this value on a specific thin-provisioned volume by using the volume
create command or the volume select thin-growth-warn command.
Format
grpparams def-thin-growth-warn n%
Variable
n
Sets the amount of in-use space, as a percentage of the reported volume size, at
which an event occurs for a thin-provisioned volume.
Example
The following command sets the group-wide default for the in-use space warning limit to
75% of the volume size:
grpparams def-thin-growth-warn 75%
grpparams description
Sets the group description. To remove a group description, enter two quotation marks
().
Format
grpparams description text
2-48
grpparams
CLI Reference
Variable
text
Example
grpparams disallow-downgrades
Prevents group members from reverting to a previous PS Series firmware version.
In some cases, you must run this command to use new features in the installed firmware or
to perform replication.
You can only use this command once on a group. If you later try to use the update
command (see update on page 3-23) to install a previous firmware version on a member,
the operation will fail.
Make sure you are connected to the group IP address (or dedicated management address)
when running this command.
Format
grpparams disallow-downgrades
Example
The following command prevents all the group members from returning to a firmware
version earlier than V3.2.
> grpparams disallow-downgrades
grpparams
2-49
CLI Reference
grpparams discovery-use-chap
To prevent iSCSI initiators from discovering targets for which they are not authorized,
enable the discovery-use-chap parameter (disabled by default). Otherwise, initiators
that support discovery will try to log in to a target, even if they do not have the right access
credentials, resulting in a large number of events logged in the group and an inefficient use
of resources.
Format
grpparams discovery-use-chap enable | disable
Example
The following command prevents unauthorized hosts from discovering volumes that are
only authenticated with CHAP:
> grpparams discovery-use-chap enable
grpparams email-contact
Enables E-Mail Home, which sends notification of firmware updates and hardware
failures to Customer Support and the specified local address.
Requirement: You must specify an SMTP server or e-mail relay for any type of e-mail
notification (see grpparams smtp-server-list on page 2-71). You can also
specify a sender address for the notification messages (see grpparams
email-from on page 2-51).
Format
grpparams email-contact email_address
Variable
email_address
2-50
grpparams
CLI Reference
Example
The following example enables E-Mail Home and configures the specified e-mail address
to receive notification, in addition to EqualLogic Customer Support:
> grpparams email-contact me@myemail.com
grpparams email-from
Specifies the e-mail address to be used as the From address in e-mail notification
messages sent by the group, including E-Mail Home notification, to prevent e-mail
programs from rejecting the notification messages.
Requirement: To configure e-mail notification, see grpparams email-list on page 2-51,
grpparams email-notify on page 2-52, and grpparams smtp-server-list on
page 2-71.
Format
grpparams email-from email_from
Variable
email_from
Example
The following command specifies an e-mail address to be used as the From address in
e-mail event notification messages:
> grpparams email-from admin@cust.com
grpparams email-list
Specifies one to five e-mail addresses to receive e-mail notification of events.
When you enable e-mail notification, by default, events with fatal, error, or warning
priority result in notification, unless you specify different priorities with the alerts
command (see alerts on page 2-9).
grpparams
2-51
CLI Reference
Variable
email_address
Example
The following command specifies two e-mail addresses to receive notification of events:
> grpparams email-list admin8@cust.com,jdt@mymail.com
grpparams email-notify
Enables or disables (default) e-mail notification.
Requirement: To receive e-mail event notification, you must specify one or more e-mail
addresses to receive messages and an SMTP server or e-mail relay. See
grpparams email-list on page 2-51 and grpparams smtp-server-list on
page 2-71. In addition, you can specify a sender address for the
notification messages. See grpparams email-from on page 2-51.
Format
grpparams email-notify enable | disable
2-52
grpparams
CLI Reference
Example
grpparams group-ipaddress
Changes the group IP address, which is used for group administration (unless you
configure a dedicated management network) and iSCSI initiator access to volumes, in
Internet Protocol Version 4 (IPv4) format.
If you modify the group IP address and the group is configured as a replication partner,
make sure the replication partner is notified of the change. In other words, make sure the
IP address stored on the replication partner is changed to match the new group IP address.
Note: Modifying the group IP address will disconnect group management sessions and
iSCSI discovery sessions. If you modify the group IP address and initiators are
configured statically with the group IP address, you may need to update the iSCSI
initiators with the new information. However, if initiators are finding targets
dynamically (for example, through iSNS), they can rediscover the targets.
Format
grpparams group-ipaddress ip_address
Variable
ip_address | none
Example
grpparams
2-53
CLI Reference
grpparams group-ipv6address
Specifies the group IP address, which is used for group administration (unless you
configured a dedicated management network) and iSCSI initiator access to volumes, in
Internet Protocol Version 6 (IPv6) format.
A group can have both an IPv4 address and an IPv6 address.
Understanding IPv6 Addresses
The IPv6 format is the successor to IPv4. IPv6 uses a 128-bit address, written as eight
groups of four hexadecimal digits, with each group separated by a colon. For example, the
following is a valid IPv6 address:
2001:0db8:85a3:08d3:1319:8a2e:0370:7334
If one or more four-digit groups is 0000, you can omit the zeros and replace them with two
colons (::).
For example you can shorten 2001:0db8:0000:0000:0000:0000:1428:57ab to
2001:0db8::1428:57ab.
If an address has only one instance of consecutive groups of 0000, you can replace them
with double colons. Leading zeros in an address group can also be omitted (as in ::1 for
localhost).
All of the following addresses are valid and equivalent:
2001:0db8:0000:0000:0000:0000:1428:57ab
2001:0db8:0000:0000:0000::1428:57ab
2001:0db8:0:0:0:0:1428:57ab
2001:0db8:0:0::1428:57ab
2001:0db8::1428:57ab
2001:db8::1428:57ab
If the group has a replication partner, make sure that the network addressing used will
support replication between the partners. See partner create on page 2-99.
Note: Adding an IPv6 address to a group that also has an IPv4 address has no effect on
current group management sessions. However, if you remove the groups IPv4
address while connections are open, users or initiators that become disconnected
will not be able to reconnect to the original address.
2-54
grpparams
CLI Reference
If initiators are configured statically with the group IP address, you may need to
update the iSCSI initiators with the new information. However, if initiators are
configured to find targets dynamically (for example, through iSNS), they can
rediscover the targets. The computer running the initiator and the group must use a
common Internet Protocol to perform discovery and log in to a target.
Format
grpparams group-ipv6address address
Variable
address | none
Note:
Example
The following command sets an IPv6 address for the group (address shown is an example
only):
> grpparams group-ipv6address fc00:01ab:23cd:45ef:abc1:def2:000e:89ff
grpparams info-messages
Controls whether informational (INFO priority) messages appear the console and in the
GUI.
Messages with INFO priority describe normal operational and transitional events in the
group. Typically, these messages are of interest to administrators but do not require
intervention.
Showing informational messages may result in the logging of a large amount of data to the
console and GUI.
Format
grpparams info-messages enable | disable
grpparams
2-55
CLI Reference
Example
The following command disables showing informational messages on the console and in
the GUI:
> grpparams info-messages disable
grpparams iscsi-local-auth
Enables (the default) or disables using local CHAP accounts to authenticate iSCSI initiator
access to volumes and snapshots (iSCSI targets). If enabled, the local CHAP accounts will
be queried before any external RADIUS authentication servers.
To set up local CHAP accounts in the group, see chapuser on page 2-12.
Note: You can also use RADIUS servers to authenticate iSCSI initiator access to
volumes. See grpparams iscsi-radius-auth on page 2-56.
Format
grpparams iscsi-local-auth enable | disable
Example
grpparams iscsi-radius-auth
Enables or disables (the default) the use of RADIUS authentication servers for
authenticating iSCSI initiator access to volumes or snapshots or Microsoft service access
to the group.
Note: You can set up local CHAP accounts in the group to authenticate iSCSI initiator
access to volumes. See chapuser on page 2-12.
You can set up target authentication in addition to initiator authentication. See
grpparams target-auth-password on page 2-74 and grpparams
target-auth-username on page 2-74.
2-56
grpparams
CLI Reference
Requirement: You must specify external RADIUS servers for authenticating host access
to volumes. See grpparams radius-auth-list on page 2-67.
Format
grpparams iscsi-radius-auth enable | disable
Example
The following command enables the use of RADIUS authentication servers for
authenticating host iSCSI access to volumes:
> grpparams iscsi-radius-auth enable
grpparams isns-server-list
Specifies (or removes) one to three IP addresses (with an optional port number) for iSNS
(Internet Storage Name Service) servers.
An iSNS server can help with the automated discovery, management, and configuration of
iSCSI devices and other devices on a TCP/IP network.
Restriction: By default, iSNS servers cannot discover iSCSI targets (volumes or
snapshots) in a group. You must enable iSNS discovery on each target.
To change a server in the iSNS server list, you must re-enter all the IP addresses (old and
new) on the command line.
To remove all servers from the list, enter two quotation marks ().
Format
grpparams isns-server-list ip_address[:port]
Variable
ip_address[:port]
grpparams
2-57
CLI Reference
Example
grpparams location
Specifies the physical location of the group, up to 63 alphanumeric characters.
The default location is default. To remove a group location, enter two quotation marks
().
Format
grpparams location text
Variable
text
Example
grpparams login-radius-acct
Enables or disables (the default) the use of RADIUS accounting servers for tracking the
activity of group administration accounts that are authenticated using RADIUS
authentication servers.
Requirement: To use RADIUS accounting, you must also enable RADIUS
authentication for accounts. See grpparams login-radius-auth on
page 2-59. For information about specifying RADIUS accounting servers,
see grpparams radius-acct-list on page 2-64.
2-58
grpparams
CLI Reference
Format
grpparams login-radius-acct enable | disable
Example
grpparams login-radius-attr
Enables (the default) or disables requiring a RADIUS authentication server to supply the
EQL-Admin attribute when authenticating group administration accounts.
Requirement: See grpparams login-radius-auth on page 2-59 for information about
enabling RADIUS authentication for group administration accounts.
See the PS Series Group Administration manual for information about additional
RADIUS attributes that you can configure.
Format
grpparams login-radius-attr enable | disable
Example
The following command requires the RADIUS authentication server to supply the
EQL-Admin attribute when authenticating group administration accounts:
> grpparams login-radius-attr enable
grpparams login-radius-auth
Enables or disables (the default) the use of RADIUS authentication servers for
authenticating group administration accounts.
Additionally, you can enable accounting to track accounts authenticated with RADIUS.
See grpparams login-radius-acct on page 2-58.
grpparams
2-59
CLI Reference
Example
The following command enables the use of RADIUS authentication servers for
authenticating group administration accounts:
> grpparams login-radius-auth enable
grpparams management-network
Configures, removes, or displays the management network for a group.
A management network lets you separate iSCSI traffic (volume and snapshot I/O) from
group management traffic. After you configure and enable a management network, you
log in to the management address, instead of the group IP address, to perform any
management operations. Replication and other inter-group communication, in addition to
iSCSI initiators, continue to use the group IP address.
Requirement: To use a dedicated management network, your physical network must be
set up with a separate management router, with unique IP addresses and
subnet masks.
The management network interface addresses and the group
management address must use the IPv4 protocol.
Configuring a Management Network
2-60
grpparams
CLI Reference
Parameter
ipaddress
Variable
mgmt_address
Subcommand
show
Examples
This example assumes you have already correctly configured the network interfaces on all
group members. Adding the management network address is the last step in the process of
configuring and using a management network. To test or use the management network, log
into the group (either through the GUI or CLI) specifying the new management address.
grpparams
2-61
CLI Reference
grpparams name
Modifies the group name, which you use to identify the group for the purposes of adding
new members or setting up replication.
If the group is configured for replication, make sure to update the group name stored on all
replication partners.
Format
grpparams name group_name
Variable
group_name
Example
grpparams ntp-server-list
Specifies from one to three IP addresses (with an optional port number) for Network Time
Protocol (NTP) servers. Using an NTP server sets a consistent time on all group members.
To change a server in the NTP server list, you must enter all the desired IP addresses on
the command line.
2-62
grpparams
CLI Reference
To remove all servers from the list, enter two quotation marks ().
Format
grpparams ntp-server-list ip_address[:port]
Variable
ip_address[:port]
Example
The following command specifies two NTP servers for the group:
> grpparams ntp-server-list 10.25.35.50:250,10.25.40.77
grpparams passwd
Changes the password required to add a member to a group. The original password was set
when the group was created. The password must be between 3 and 16 alphanumeric
characters and is case-sensitive. Do not specify a current user or account password.
Note: Do not specify a password on the command line. After entering the command, you
will be prompted for the new password. Passwords are not shown on the screen.
Format
grpparams passwd
Example
The following command specifies a new password for adding a group member:
> grpparams passwd
Password for adding members:
Retype password:
Password has been changed.
grpparams
2-63
CLI Reference
grpparams perf-balancing
Enables (default) or disables performance load balancing.
When you enable performance load balancing, the group will place volume data on
members that have the optimal RAID level for the volume, based on the volumes
performance metrics and historical I/O pattern.
Performance load balancing occurs only after a period of time during which the group will
monitor the volumes performance and I/O pattern. Over time, volume data may be moved
across members.
Recommendation: Dell recommends that you enable performance load balancing.
Format
grpparams perf-balancing enable | disable
Example
grpparams radius-acct-list
Specifies one to three IP addresses (with optional port number) for external RADIUS
accounting servers that are used to track group administration accounts that are also
authenticated with RADIUS. The servers are contacted in the order specified.
Requirement: To enable RADIUS accounting, see grpparams login-radius-acct on
page 2-58.
Depending on how you configured the RADIUS accounting server, you
may need to specify secrets (passwords). See grpparams
radius-acct-secrets on page 2-66.
Optionally, you can override the default retry and timeout values for contacting RADIUS
accounting servers. See grpparams radius-acct-retries on page 2-65 and grpparams
radius-acct-timeout on page 2-67.
2-64
grpparams
CLI Reference
Format
grpparams radius-acct-list ip_address[:port]
Variable
ip_address[:port]
Example
grpparams radius-acct-retries
Specifies the number of times the group will try to contact a RADIUS accounting servers
after the first try fails. If the group cannot connect within the specified number of retries, it
will try to connect to another accounting server, if one is configured.
For example, when a user logs into a group administration account, the group will try to
contact a RADIUS authentication server. Thenif the account is authenticatedthe
group will try to contact an accounting server. If the group receives no response within the
time limit set by the radius-acct-timeout parameter, the group will keep trying to
contact the server the number of times specified by the radius-acct-retries
parameter.
Requirement: To specify RADIUS accounting servers, see grpparams radius-acct-list
on page 2-64.
Format
grpparams radius-acct-retries n
grpparams
2-65
CLI Reference
Variable
n
Number of times the group will try to contact a RADIUS accounting server after the
initial try fails. The default is 1 retry.
Example
The following command specifies that the group try to contact a RADIUS accounting
server two times after the initial try fails:
> grpparams radius-acct-retries 2
grpparams radius-acct-secrets
Specifies secrets (passwords) for the external RADIUS accounting servers that are used to
track group administration accounts that are authenticated with a RADIUS authentication
server.
Requirement: To specify RADIUS accounting servers, see grpparams radius-acct-list
on page 2-64.
Format
grpparams radius-acct-secrets secrets
Variable
secrets
Example
The following command specifies secrets for two RADIUS accounting servers:
> grpparams radius-acct-secrets gofish2,lin2006
2-66
grpparams
CLI Reference
grpparams radius-acct-timeout
Specifies the number of seconds the group will wait for a RADIUS accounting server to
respond before timing out.
For example, when a user logs into a group administration account, the group will try to
contact a RADIUS authentication server. Thenif the account is authenticatedthe
group will try to contact a RADIUS accounting server. If the server does not respond
within the timeout period, the contact will fail. If the value of the
radius-acct-retries parameter is more than 1, the group will try to contact the server
for the specified number of times.
Requirement: To specify RADIUS accounting servers, see grpparams radius-acct-list
on page 2-64.
Format
grpparams radius-acct-timeout n
Variable
n
Number of seconds to wait for a response from a RADIUS accounting server. The
default is 2 seconds.
Example
The following command specifies that the group wait 3 seconds for a RADIUS accounting
server to respond:
> grpparams radius-acct-timeout 3
grpparams radius-auth-list
Specifies one to three IP addresses (with optional port number) for external RADIUS
authentication servers. These servers can be used to authenticate host (iSCSI initiator)
access to volumes through CHAP, authenticate group administration accounts, or
authenticate Microsoft service access to the group. The servers are contacted in the order
specified.
grpparams
2-67
CLI Reference
Variable
ip_address[:port]
Example
2-68
grpparams
CLI Reference
grpparams radius-auth-retries
Specifies the number of times the group will try to contact a RADIUS authentication
server after the first try fails. If the group cannot connect within the specified number of
retries, it will try to contact another authentication server, if one is configured.
For example, when a host (iSCSI initiator) tries to connect to a volume (or a user logs into
an administration account), the group will try to contact a RADIUS authentication server.
If the group receives no response within the time limit specified by the
radius-auth-timeout parameter, the group will keep trying to contact the server the
number of times specified by the radius-auth-retries parameter.
Requirement: To specify RADIUS authentication servers, see grpparams
radius-auth-list on page 2-67.
Format
grpparams radius-auth-retries n
Variable
n
Number of times the group will try to contact a RADIUS authentication server after
the initial try fails. The default is 1 retry.
Example
> grpparams radius-auth-retries 2
grpparams radius-auth-secrets
Specifies secrets (passwords) for the external RADIUS authentication servers that are
used to authenticate host access to volumes, authenticate group administration accounts,
or authenticate Microsoft service access to the group.
Requirement: To specify RADIUS authentication servers, see grpparams
radius-auth-list on page 2-67.
Format
grpparams radius-auth-secrets secret[,secret,...]
grpparams
2-69
CLI Reference
Variable
secret
Example
> grpparams radius-auth-secrets bigboy1,chen1492
grpparams radius-auth-timeout
Specifies the number of seconds the group will wait for a RADIUS authentication server
to respond before timing out.
For example, when a host tries to connect to a volume (or a user logs into an
administration account), the group will try to contact a RADIUS authentication server. If
the server does not respond within the timeout period, the contact will fail. If the value of
the radius-auth-retries parameter is more than 1, the group will try to contact the
server for the specified number of times.
Requirement: To specify RADIUS authentication servers, see grpparams
radius-auth-list on page 2-67.
Format
grpparams radius-auth-timeout n
Variable
n
Example
> grpparams radius-auth-timeout 3
2-70
grpparams
CLI Reference
grpparams show
Shows the current values of all the group parameters or a specific list parameter.
Format
grpparams show [list-parameter]
Variable
list-parameter
email-list
isns-server-list
ntp-server-list
radius-acct-list
radius-auth-list
smtp-server-list
syslog-server-list
Examples
> grpparams show syslog-server-list
Syslog Server List :: 182.1.12.144
grpparams smtp-server-list
Specifies from one to three IP addresses (with an optional port number) for SMTP (Simple
Mail Transfer Protocol) servers or e-mail relays used for e-mail event notification.
To change any of the servers in the SMTP server list, re-enter all the IP addresses on the
command line.
To remove all servers from the list, enter two quotation marks ().
Requirement: To set up e-mail notification, you must also specify one or more e-mail
addresses to receive the e-mail and enable e-mail event notification. See
grpparams email-list on page 2-51 and grpparams email-notify on
page 2-52. In addition, you can specify a sender address for the
notification messages (see grpparams email-from on page 2-51).
grpparams
2-71
CLI Reference
Format
grpparams smtp-server-list ip_address[:port]
Variable
ip_address[:port]
Example
> grpparams smtp-server-list 12.34.167.25
grpparams snmp
Shows and sets SNMP (Simple Network Management Protocol) configuration parameters,
such as community strings and trap destinations.
To remove a community string, SNMP managers string, or trap community string, specify
two quotation marks ().
Format
grpparams snmp show | parameter
Parameters
read-only-comms string
read-write-comms string
snmp-managers string
trap-community string
Example
> grpparams snmp show
_______________________ Snmp Information _________________________
2-72
grpparams
CLI Reference
read-only-comms:public
trap-community: SNMP-trap
read-write-comms:
snmp-managers: 12.44.140.2
grpparams syslog-notify
Enables or disables (default) event logging to remote syslog servers.
When you enable syslog notification, by default, events with FATAL, ERROR, or
WARNING priority result in notification, unless you specify different priorities with the
alerts command. See alerts on page 2-9.
Requirement: To use syslog notification, you must also specify IP addresses for the
syslog servers. See grpparams syslog-server-list on page 2-73.
Format
grpparams syslog-notify enable | disable
Example
> grpparams syslog-notify enable
grpparams syslog-server-list
Sets one to three IP addresses, separated by commas and no spaces, for remote servers that
will log events to a remote syslog-style log file.
Requirement: The servers must be configured to accept remote log files. The default port
number is 514 (UDP).
To use syslog notification, you must also enable syslog notification. See
grpparams syslog-notify on page 2-73.
To change any of the servers in the syslog server list, re-enter all the IP addresses on the
command line.
To remove all servers from the list, enter two quotation marks ().
Format
grpparams syslog-server-list ip_address
grpparams
2-73
CLI Reference
Variable
ip_address
Example
> grpparams syslog-server-list 12.34.567.89:510
grpparams target-auth-password
Specifies a CHAP password to be used for target authentication, which lets the volume
(iSCSI target) be authenticated by the host (iSCSI initiator).
Requirement: You must also specify the target authentication user name (see grpparams
target-auth-username on page 2-74).
You cannot use target authentication without setting up initiator
authentication. See chapuser on page 2-12 and grpparams cliaccess-ssh
on page 2-41.
Format
grpparams target-auth-password password
Variable
password
Example
> grpparams target-auth-password jjbaset29
grpparams target-auth-username
Specifies a CHAP user name to be used for target authentication, which lets the volume
(iSCSI target) be authenticated by the host (iSCSI initiator).
Requirement: You must also specify the target authentication password (see grpparams
target-auth-password on page 2-74).
2-74
grpparams
CLI Reference
Variable
name
Example
> grpparams target-auth-username joe1492
grpparams time
Sets the time for the group.
Format
grpparams time hh:mm:ss
Variable
hh:mm:ss
Time in 24-hour format: hours (hh), minutes (mm), and seconds (ss).
Example
> grpparams time 13:46:00
grpparams timezone
Sets the time zone for the group, using a country and city designation.
The default is America/New_York.
Format
grpparams timezone zone
grpparams
2-75
CLI Reference
Variable
Time zone. To see a list of supported time zones, use the grpparams
timezone ? command.
zone
Example
> grpparams timezone America/Los_Angeles
grpparams vss-vds
Manages access control records for Microsoft service access to the group, including
Volume Shadow Copy Service (VSS) and Virtual Disk Service (VDS).
When you create an access control record, the group assigns an identification number to
the record. Use this number to manage the record with the CLI.
Note: If you are using CHAP to authenticate Microsoft service access to the group, you
must set up a CHAP account either locally (see chapuser on page 2-12) or on a
RADIUS server (see grpparams radius-auth-list on page 2-67).
The Windows server that is running the Microsoft service must be configured with
a matching CHAP user name and password. You can use the Remote Setup Wizard
to set these credentials. See the Host Integration Tools documentation.
Format
grpparams vss-vds access [subcommand] | show
Subcommands
create [parameter]
delete id
select id [parameter]
show
2-76
grpparams
CLI Reference
Parameters
authmethod chap | none
username chap_name
ipaddress address
initiator name
show
Example
> grpparams vss-vds access create authmethod chap username adm32
grpparams webaccess
Enables (default) or disables the use of standard HTTP Web connections (through port 80)
to the group manager GUI.
To restrict GUI access to Web connections that are secured with SSL, see grpparams
webaccess-noencrypt on page 2-78.
Format
grpparams webaccess enable | disable
grpparams
2-77
CLI Reference
Example
> grpparams webaccess disable
grpparams webaccess-noencrypt
Enables (the default) or disables requiring access to the GUI through a Web connection
that is not encrypted with SSL.
If enabled, SSL encryption is not required. To limit GUI access only to Web connections
that are secured with SSL encryption, disable webaccess no-encrypt and install the
Java plug-in with SSL on the host running the Web browser. Also, you must select the
checkbox next to Encrypt communication in the GUI login dialog box.
Format
grpparams webaccess-noencrypt enable | disable
Example
> grpparams webaccess-noencrypt disable
2-78
grpparams
CLI Reference
member
Manages group members.
Format
member subcommand
Subcommands
delete
rename
Renames a member.
select
show
member delete
Removes a member from its pool and from the group. Resets the array to factory defaults.
Resetting an array removes any group, member, and volume configuration information on
the array.
You cannot remove the only member of a group. You cannot remove the last member in a
pool that contains volumes. You must move the volumes to a different pool before you can
remove the member. You can remove only one member at a time.
All volumes, snapshots, and replica sets stored on the member are moved (vacated) to the
other pool members, with no effect on availability.
If the other pool members do not have enough free space to store the data from the
member being removed, the operation fails. Increase the capacity of the remaining
members and retry the operation.
You can cancel an in-progress member delete operation. To see member status, use the
member show command. While volume data is moving to other members, the member
status is vacating-in-progress. When complete, the member no longer shows in the
member show output.
In rare cases, you may need to remove a member that is offline (for example, if the
member has failed and is no longer operational). When you remove an offline member, an
member
2-79
CLI Reference
error message occurs stating that the vacate has failed; that is, the members data could not
be moved to the remaining pool members. When prompted, agree to remove the member.
Then, the offline member will be removed.
Format
member delete member_name
Variable
member_name
Name of a member.
Example
The following command removes a member from its pool and the group:
> member delete member16
Do you really want to delete the member? (y/n) [n] y
Member deletion succeeded.
member rename
Renames a member.
Format
member rename current_name new_name
Variables
current_name
Name of a member.
new_name
Example
2-80
member
CLI Reference
member select
Shows or modifies the configuration of the selected member, including the network
configuration, RAID policy, and the pool to which the member belongs. You can also
cancel an in-progress member operation, such as a member delete (vacate) operation.
Format
member select member_name subcommand | parameter...
Variable
member_name
Name of a member.
Subcommands
disk select | show
show [component]
Parameters
cancel-operation op_id
controller-safe enable |
disable
def-gateway address |
none
Default gateway for the member. Applies to, and must be set
for, all configured interfaces on the member except the
management network interface. Supports IPv4 protocol only.
Specify none to delete the default gateway for the member.
member
2-81
CLI Reference
delay-data-move enable |
disable
description text
low-battery-safe enable |
disable
pool pool
2-82
member
CLI Reference
raid-policy policy
Sets the RAID policy for the member, either raid5, raid10,
raid50, raid6, raid10-nospares, or
raid50-nospares.
For the highest availability, choose a RAID policy that
includes spare disks, which are used automatically if a disk
fails.
After you set a member RAID policy, you may be able to
convert it to a different RAID policy. However, the group
does not support all RAID policy conversions. When you
convert a RAID policy, the members RAID status is
expanding.
Examples
The following command sets a default gateway for all interfaces on the member (except
the management network interface, if any):
> member select member3 def-gateway 10.127.0.1
member
2-83
CLI Reference
Variables
member_name
Name of a member.
slot_num
Disk slot number. The total number of slots in a member will vary
based on the array model.
Example
> member select memlab2 disk select 0 clear-label
Variables
member_name
Name of a member.
slot_num
Disk slot number. The total number of slots in a member will vary
based on the array model.
Example
> member select memlab2 disk select 0 show
Variable
member_name
2-84
Name of a member.
member
CLI Reference
Examples
A network interface for iSCSI traffic can use either the IPv4 or the IPv6 protocol.
For IPv4, you must specify an IPv4 address and a netmask (subnet mask).
For IPv6, you can specify an IPv6 address, but these are usually configured
automatically when you enable the interface. Subnet masks do not apply to IPv6.
Each interface can have up to eight (8) addresses. One can be a static IPv4 address, and
one can be a static IPv6 address (except for an interface configured for management). The
others are dynamic, and cannot be set, changed or deleted. One of these dynamic
addresses is a link-local address.
Note: If network problems occur, group members may lose the ability to communicate
with each other over the network. In this situation, some management operations
are not allowed. For example, you cannot change the IP address for an isolated
members network interface.
Format
member select member_name eth select port parameter ...
Variables
member_name
member
Name of a member.
2-85
CLI Reference
port
Parameters
description text
mgmt-only
netmask mask_ip
up | down
The following commands configure the eth1 network interface and then enable it:
> member select m5 eth select 1 ipaddress 131.22.3.8 \
netmask 255.255.255.0
> member select m5 eth select 1 up
2-86
member
CLI Reference
In a group using only the IPv6 protocol, you typically do not need to specify an IPv6
address for the network interfaces. The router broadcasts available addresses. When you
enable an interface, it takes one of those addresses.
To enable a network interface in an IPv6 group and allow it to use a dynamic address,
enter:
> member select member1 eth select 0 up
To configure a static IPv6 address for a network interface and enable it, enter the
following commands:
> member select member1 eth select 0 ipv6address fc00::445a:a17:fcf7:686
> member select member1 eth select 0 up
To configure a static IPv6 address for a network interface that is already enabled (up),
enter:
> member select scale16 eth select 2 ipv6address fc00::445a:a17:fcf7:686
Changing the IP address closes all management and iSCSI connections
associated with this IP address. Do you really want to change? (y/n) [n]y
The following command shows the details for the management-only interface:
> member select member1 eth select 2 show
_________________________ Eth Information ________________________
member
2-87
CLI Reference
Name: eth2
Status: up
Changed: Thu Mar 6 16:54:09 2009
Type: ethernet-csmacd
DesiredStatus: up
Mtu: 9000
Speed: 100000000
HardwareAddress:
00:09:8A:01:A7:AE
IPAddress: 10.119.12.12
NetMask: 255.255.0.0
IPv6Address:
Description:
SupportsManagement: yes
ManagementStatus: enabled
__________________________________________________________________
Variables
member_name
Name of a member.
port
Example
> member select member7 eth select 0 show
_________________________ Eth Information ________________________
Name: eth1
Status: down
Changed: Thu May 1 09:07:51 2009
Type: ethernet-csmacd
DesiredStatus: down
Mtu: 1500
Speed: 10000000
HardwareAddress:
00:09:8A:01:B2:15
IPAddress: Not Found
NetMask:
IPv6Address:
Description:
SupportsManagement: no
ManagementStatus: disabled
__________________________________________________________________
2-88
member
CLI Reference
Variable
Name of a member.
member_name
Example
> member select member7 eth show
Name ifType
ifSpeed
---- ------------ -------
Mtu
---
Ipaddress
---------
Status
------
Errors
------
1500
down
1500
down
Variables
member_name
Name of a member.
component
member
channelcards
connections
controllers
disks [n]
enclosure
eths [n]
version
volumes
2-89
CLI Reference
Examples
The following command shows information about the control modules in an array:
> member select member1 show controllers
_____________________ Controller Information _____________________
SlotID: 0
Status: active
Model: 70-0111(TYPE 6)
BatteryStatus: ok
ProcessorTemperature: 65
ChipsetTemperature: 32
LastBootTime: 2009-05-05:10:08:27
SerialNumber: RMS83308A024A51
Manufactured: 3507
ECOLevel: C01
CM Rev.: R07
FW Rev.: V4.0.0
NVRAM Battery: good
BootRomVersion: 6.0.1
BootRomBuilDate: Sat Mar 8 00:59:37
EST 2009
__________________________________________________________________
__________________________________________________________________
2-90
member
CLI Reference
SlotID: 1
Status: secondary
Model: 70-0111(TYPE 6)
BatteryStatus: ok
ProcessorTemperature: 67
ChipsetTemperature: 35
LastBootTime: 2009-05-05:10:08:31
SerialNumber: RMS83308A025BA9
Manufactured: 5207
ECOLevel: C01
CM Rev.: R07
FW Rev.: V4.0.0
NVRAM Battery: good
BootRomVersion: 6.0.1
BootRomBuilDate: Sat Mar 8 00:59:37
EST 2009
__________________________________________________________________
________________________ Cache Information _______________________
CacheMode: write-back
Controller-Safe: disabled
Low-Battery-Safe: enabled
__________________________________________________________________
The following command shows information about the channel cards in an array (applies
only to some PS Series array models):
> member select member1 show channelcards
____________________ Channelcard Information _____________________
SlotID: 0
Status: good
SerialNumber: ICS7139100029EA
FW Rev.: V2.c
Init Rev.: V03.1
__________________________________________________________________
__________________________________________________________________
SlotID: 1
Status: good
SerialNumber: ICS713910002A25
FW Rev.: V2.c
Init Rev.: V03.1
__________________________________________________________________
The following command shows the disks installed in a member (edited for brevity):
> member select mem1 show disks
Slot
---0
1
2
3
4
5
6
.
.
.
Type
------SATA
SATA
SATA
SATA
SATA
SATA
SATA
member
Model
----------------------Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Size
Status
-------- ------465.76GB online
465.76GB online
465.76GB online
465.76GB online
465.76GB online
465.76GB online
465.76GB online
Errors
-----0
0
0
0
0
0
0
2-91
CLI Reference
The following command shows information about the hardware components in the
member enclosure, as applicable to that array model:
> member select mem1 show enclosure
_______________________ Temperature Sensors ______________________
Name
------------------------------Backplane sensor 0
Backplane sensor 1
Control module 0 processor
Control module 0 chipset
Control module 1 processor
Control module 1 chipset
Control module 0 SAS Controller
Control module 0 SAS Expander
Control module 1 SAS Controller
Control module 1 SAS Expander
Value
--------36
36
65
32
67
35
57
60
56
63
Normal Range
--------------2-50
2-50
10-90
10-45
10-90
10-45
10-110
10-110
10-110
10-110
Status
---normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
Speed
--------4650
4680
4620
4710
4650
4710
Normal Range
--------------2100-5200
2100-5200
2100-5200
2100-5200
2100-5200
2100-5200
Status
--------normal
normal
normal
normal
normal
normal
Status
--------on
on
on
FanStatus
--------not-applicable
not-applicable
not-applicable
2-92
member
CLI Reference
ifSpeed
Mtu
Ipaddress
Status Errors
-----up
up
up
-----0
0
0
The following command shows information about the status of Ethernet port 0:
> member select mem1 show eth 0
_________________________ Eth Information ________________________
Name: eth0
Status: up
Changed: Mon May 5 10:31:41 2009 Type: ethernet-csmacd
DesiredStatus: up
Mtu: 9000
Speed: 1000000000
HardwareAddress: 00:09:8A:02:4A:51
IPAddress: 10.127.33.71
NetMask: 255.255.0.0
IPv6Address:
Description:
SupportsManagement: no
ManagementStatus: disabled
__________________________________________________________________
The following command shows the component version information (edited for brevity):
> member select mem1 show version
Component
-------------------Backplane
PCM0
PCM1
PCM2
CM0
CM1
Channel card 0
Channel card 1
EIP Card
Part#
--------62532
64362
64362
64362
70-0111
70-0111
Rev
------NA
NA
NA
NA
R07
R07
V2.c
V2.c
02.9e
SN
-------------------SHU80811000240E
PMA846270004727
PMA846270004726
PMA846270004728
RMS83308A024A51
RMS83308A025BA9
ICS7139100029EA
ICS7139100029EA
Not Available
ECO
-----NA
NA
NA
NA
C01
C01
Type
----SATA
SATA
SATA
SATA
SATA
SATA
member
Model
------------------------Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
Hitachi HUA721050KLA330
2-93
CLI Reference
The following command shows the volumes that have data stored on a member:
> member select mem1 show volumes
Volume Name
--------------vol001
vol002
datavol1
Contribution
-----------1.01GB
100GB
500MB
member show
Shows information about all the group members or a specific member, including any
in-progress operations. Different array models will show slightly different information.
Format
member show [member_name] [-poolinfo]
Variable
member_name
Name of a member.
Examples
Status
------online
online
Version
-------V4.0.0
V4.0.0
Disks
----48
48
Capacity
---------18062.61GB
5301.87GB
FreeSpace
---------17961.53GB
5200.79GB
Connections
--------0
0
Status Version
------ -------online V4.0.0
online V4.0.0
Disks
----48
48
2-94
member
CLI Reference
member
2-95
CLI Reference
mrtg-config
Creates a file containing the information necessary to run Multi-Router Traffic Grapher
(MRTG), a third-party performance monitoring utility, on a system with access to the
PS Series group.
The MRTG utility collects data from the PS Series group about the I/O, latency, and
throughput for the members and volumes in the group. It uses the member and volume
index numbers (stored in the MIB tables) for the group objects.
The mrtg-config command retrieves the index numbers and enters them in a file it
creates, called mrtg.cfg by default. You can optionally specify a different name for the
file. The command also creates an HTML file, called index.html, that you can view in a
browser, to see graphs of the performance data for the members and volumes.
Use ftp or scp to retrieve the configuration and HTML files from the group and copy
them to a system that you will use to view the HTML file. See diag on page 3-5 for
information on retrieving files from an array using the ftp or scp utility.
On the system, you can then run a Perl script that starts MRTG and populates the graph
data.
Format
mrtg-config [-verbose] [-nocr] [file]
Variable
file
Optional name for the configuration file. By default, the file is named mrtg.cfg.
Options
-verbose
-nocr
Use on UNIX systems. Uses the \n newline character when creating the
configuration file instead of the default \r\n character for Windows systems.
Example
The following example creates an MRTG configuration file with the default name:
> mrtg-config
Mrtg configuration saved to mrtg.cfg
2-96
mrtg-config
CLI Reference
The following example creates an MRTG configuration file named for the group
(group1):
> mrtg-config group1_mrtg.cfg
Mrtg configuration saved to group1_mrtg.cfg
Generating html file.
Index file saved to index.html
You can retrieve the files using ftp or scp.
mrtg-config
2-97
CLI Reference
partner
Creates and manages the replication partners for a group.
Replicating volume data from one group to another protects the data from catastrophic
failures. A replica represents the data in the volume at the time replication started. A
replica set is the set of replicas for a volume.
To replicate volume data, you must configure two groups as replication partners. Each
group plays a role in the replication operation:
The group where the original volume is stored is the primary group. The direction of
the replication is outbound from the primary group.
The group where the volume replicas are stored is the secondary group. The direction
of the replication is inbound to the secondary group. If a disaster occurs on the
primary group, you can recover data from the replica set on the secondary group.
2-98
partner
CLI Reference
Format
partner subcommand
Subcommands
create
Creates a partner.
delete
Deletes a partner.
rename
Renames a partner.
select
show
partner create
Sets up a replication partnership between two groups. Before configuring a partner, make
sure that all members of both groups have network connectivity.
Note: The partner create command must be run on both the primary group and the
secondary group.
The following parameters are required:
Partner group name and group IP address, in either IPv4 or IPv6 format, as
appropriate.
Passwords for mutual authentication. Replication between groups cannot occur until
the reciprocal passwords are set on both groups.
The administrator for each group must specify the inbound password (which is the
outbound password from the other group) and the outbound password (which is the
inbound password on the other group).
partner
2-99
CLI Reference
Replication is supported between partners as long as they use a common Internet Protocol,
as follows:
If both partners are using only IPv4 addressing or only IPv6 addressing, replication is
supported. This means that each partner has only one group IP address configured and
their addresses use the same protocol.
If one partner uses only IPv4 or only IPv6 and the other uses a combination of IPv4
and IPv6, replication is supported. This means that one partner has only one IP
address configured, and the other has both an IPv4 address and an IPv6 address. The
partners will replicate using the protocol common to both.
If one partner uses only IPv4 and the other uses only IPv6, replication is not
supported.
The two groups configured as replication partners do not communicate until replication is
enabled on a volume or a replication is tried. Therefore:
You will not know about password or configuration problems until replication is
enabled on a volume. If you receive a login error message, make sure the reciprocal
passwords on the partners agree.
Delegated space will not be shown in the CLI output until a volume replication starts.
If you increase the size of a replicated volume, the secondary group will not update the
information until the next replication starts.
After creating a replication partnership between two groups, you can log in to the group
where the volume is stored (the primary group) and enable replication on the volume. See
volume select replication enable on page 2-198. Then, you can create replicas.
Format
partner create partner_name ipaddress address parameters...
Variable
partner_name
2-100
partner
CLI Reference
Parameters
contact name
description text
email email_address
inbound-password password
ipaddress address
ipv6address address
mobile number
phone number
outbound-password password
pool-delegated pool
space-delegated size[GB]
partner
2-101
CLI Reference
The following commands create a partnership between two groups, AGroup and CGroup.
AGroup (primary group) is replicating volumes to CGroup (secondary group), and both
are using the IPv4 protocol.
In the example output, the passwords are readable to show that the inbound password for
one group is the outbound password on the partner, and vice versa. In reality, passwords
are encrypted for security.
The following command is run on AGroup:
AGroup> partner create CGroup ipaddress 182.1.2.18 inbound-password hello
outbound-password greetings
_______________________ Partner Information ______________________
Name: CGroup
IPAddress: 182.1.2.18
Space-Received: 0MB
Space-Received-Used: 0MB
Outbound-Password: greetings
OutboundDesiredStatus: enabled
Description:
Space-Delegated: 0MB
Space-Delegated-Used: 0MB
Inbound-Password: hello
InboundDesiredStatus: enabled
Contact:
Email:
Phone:
Mobile:
Pool-Delegated: default
__________________________________________________________________
The following commands create a partnership between two groups, called Alpha and Beta.
Both Alpha and Beta will delegate 1TB of space to the other, and both are using the IPv6
protocol.
2-102
partner
CLI Reference
In the example output, the passwords are readable to show that the inbound password for
one group is the outbound password on the partner, and vice versa. In reality, passwords
are encrypted for security.
The following command is run on the group Alpha:
AGroup> partner create Beta ipv6address fc00::10aa:127b:cd25:ef170
space-delegated 1000GB inbound-password helloAlpha999 outbound-password
helloBeta111
Partner creation succeeded.
_______________________ Partner Information ______________________
Name: test
IPv6Address: fc00::10aa:127b:cd25:
ef170
Space-Received: 0MB
Space-Received-Used: 0MB
Outbound-Password: ************ OutboundDesiredStatus: enabled
Description:
Space-Delegated: 1000GB
Space-Delegated-Used: 0MB
Inbound-Password: *************
InboundDesiredStatus: enabled
Contact:
Email:
Phone:
Mobile:
Pool-Delegated: default
FailbackReservedSpace: 0MB
__________________________________________________________________
IPv6Address:fc00::a1a1:b2b2:cc33:
def8
Space-Received: 0MB
Space-Received-Used: 0MB
Outbound-Password: ************* OutboundDesiredStatus: enabled
Description:
Space-Delegated: 1000GB
Space-Delegated-Used: 0MB
Inbound-Password: ************
InboundDesiredStatus: enabled
Contact:
Email:
Phone:
Mobile:
Pool-Delegated: default
FailbackReservedSpace: 0MB
partner
2-103
CLI Reference
partner delete
Breaks the relationship between the group and a replication partner. First, you must pause
inbound replication from the partner to the group. See partner select inbound-pause on
page 2-119.
Note: If the partner you are deleting has recovery volumes, then before you delete the
partner you must either demote the recovery volumes to inbound replica sets
(which will be deleted when you delete the partner) or make the promotion
permanent, which breaks the association between the volume and its group of
origin.
To demote a recovery volume, see volume select replication demote on page 2-197.
To permanently promote a recovery volume, see volume select delete-failback on
page 2-191.
When you delete a replication partner, the partners replicas stored on the group are also
deleted, and the delegated space is released. However, if you delete a replication partner
that is storing replicas from the group, the replicas are not deleted and can be accessed
from the partner.
For example, if you are on GroupB and you delete the partner GroupA, the following
occurs:
If Group-B is storing replicas from GroupA, those replica sets are deleted.
If Group-A is storing replicas from GroupB, those replica sets are not deleted.
Format
partner delete partner_name
Variable
partner_name
Example
2-104
partner
CLI Reference
partner rename
Renames a replication partner.
Rename a replication partner only if the partners group name has changed.
Format
partner rename partner_name new_name
Variables
partner_name
new_name
Example
partner select
Selects a replication partner so that you can perform additional operations on it.
Format
partner select partner_name subcommand | parameter
Variable
partner_name
Subcommands
cancel-operation
partner
2-105
CLI Reference
failback-replicaset
inbound-pause
inbound-repcol
inbound-repcolset
inbound-replicaset
inbound-resume
outbound-pause
outbound-repcol
outbound-repcolset
outbound-replicaset
outbound-resume
show [-poolinfo]
Parameters
contact name
2-106
partner
CLI Reference
description text
email email_address
inbound-password password
ipv6address address
mobile number
characters.
Note:
pool-delegated pool
Moves the delegated space and all the replica sets and
recovery volumes for the partner from the original pool into
the specified pool.
space-delegated size[GB]
partner
2-107
CLI Reference
Example
The following command changes the delegated space pool for a partner:
> partner select group1 pool-delegated staff_pool
Variables
partner_name
Subcommands
select
show
Example
The following command shows the failback replica sets in the group:
> partner select group2 failback-replicaset show
Name
--------------dbvol2
vol5
2-108
ReservedSpace
------------80GB
2.01GB
FreeSpace
------------36.98GB
1.01GB
Replicas
-------21
3
Status
------------ready
ready
partner
CLI Reference
uservol8
clonevol1
40.01GB
16.03GB
20GB
8.01GB
4
0
ready
ready
set_name
Subcommands
access
cancel-operation op_id
delete-failback
pool pool
promote
show
partner
2-109
CLI Reference
Variables
partner_name
set_name
Subcommands
create
delete
select
show
Shows information about the access control records for the failback replica
set.
2-110
partner
CLI Reference
Before you can load transfer files into a volumes failback replica set on the secondary
group, you must configure the system running the Manual Transfer Utility CLI to connect
to the failback replica set, which has an iSCSI target associated with it.
Note: If the replication partners are configured to use only the IPv6 protocol, you must
create an access control record for the failback replica set using either the initiator
name or a CHAP account. Access control records for IPv6 initiator client system
addresses are not currently supported.
Format
partner select partner_name failback-replicaset select set_name access
create subcommand parameter
Variables
partner_name
set_name
Parameters
username chap_name
ipaddress address
initiator name
partner
2-111
CLI Reference
Examples
The following command creates an access control record to grant access to a specific
CHAP user and sets the authentication method to CHAP:
> partner select Group2 failback-replicaset select db2vol access create
username dbuser authmethod chap
Created access entry with ID 2.
The following command creates an access control record for a specific IP address
(supported only for IPv4 addresses):
> partner select Group2 failback-replicaset select db2vol access create
ipaddress 172.17.30.22
Created access entry with ID 3.
The following command creates an access control record for an initiator name:
> partner select Group2 failback-replicaset select db2vol access create
initiator iqn.1991-05.com.microsoft:admin-pc.company.com
Variables
partner_name
set_name
2-112
partner
CLI Reference
access_entry_id
Example
Variables
partner_name
set_name
access_entry_id
Subcommand
show
partner
2-113
CLI Reference
Parameters
authmethod chap | none
initiator name
ipaddress address
username chap_name
Examples
The following commands modify the CHAP user name for an access control record, and
show the detail information for the record before and after the change:
> partner select Group2 failback-replicaset select db2vol access select 2
show
______________________ Access Information ________________________
Initiator:
Ipaddress: *.*.*.*
AuthMethod: chap
UserName: jsmith
Apply-To: both
__________________________________________________________________
2-114
partner
CLI Reference
Variables
partner_name
set_name
access_entry_id
Example
The following command shows detailed information about an access control record for a
failback replica set:
> partner select Group2 failback-replicaset select db2vol access select 1
show
_______________________ Access Information _______________________
Initiator:
AuthMethod: chap-local
Apply-To: both
Ipaddress: *.*.*.*
UserName: secondary
partner
2-115
CLI Reference
Variables
partner_name
set_name
op_id
Example
The following commands show the identification number of a pool move operation in
progress and then cancel the operation:
> partner select group2 failback-replicaset select vol2 show
> partner select group2 failback-replicaset select vol2 cancel-operation 1
Variables
partner_name
set_name
Example
The following example changes a failback replica set to an inbound replica set:
> partner select group2 failback-replicaset select vol3 delete-failback
Failback replica set 'vol3' has been successfully converted to a replica
set with failback deleted.
2-116
partner
CLI Reference
Variables
partner_name
set_name
pool
Example
partner
2-117
CLI Reference
Variables
partner_name
set_name
Example
The following commands pause inbound replication from the partner and promote a
failback replica set to its original volume:
> partner select group2 inbound-pause
> partner select group2 failback-replicaset select vol6 promote
Failback replica set promotion succeeded. In order to establish a failback
baseline, a new replica will be created.
The promoted volume is offline. You must set it online to use it. See volume select on
page 2-179.
To set the new failback baseline, replicate the volume immediately. See volume select
replication create-replica on page 2-196.
Variables
partner_name
set_name
Example
The following command shows detailed information about a failback replica set:
> partner select group-two failback-replicaset select data01 show
_________________ Inbound ReplicaSet Information _________________
2-118
partner
CLI Reference
Name: data01
PrimaryIscsiName:
FailbackSize: 45.03GB
iqn.2001-05.com.equallogic:0-8a0906Pool: default
9427ccb01-d1b000000124820a-data01
Size: 200GB
ReservedSpace: 40.02GB
FreeSpace: 20GB
Replicas: 3
Status: ready
Manual-Xfer: disabled
StartingTime: None
Thin-Provision: enabled
Thin-Min-Reserve: 10%
Thin-Growth-Warn: 60%
Thin-Growth-Max: 100%
Type: failback
__________________________________________________________________
________________________ Inbound-Replicas ________________________
Name
TimeStamp
Size
Status
---------------------------- ----------- ---------- ----------data01-2009-05-07-13:29:01.3 Wed May 7 2009 200GB
ready
13:29:01
2009
data01-2009-05-07-13:34:21.4 Wed May 7 200GB
ready
13:34:21
2009
data01-2009-05-07-13:34:36.5 Wed May 7
13:34:36
2009
200GB
ready
Variable
partner_name
Example
The following command pauses replication data transfer from the partner to the group:
> partner select psgroup2 inbound-pause
partner
2-119
CLI Reference
Variable
partner_name
Subcommands
delete repcol
select repcol
show [custom]
Examples
The following command shows a partners replica collections stored in the group:
> partner select psgroup2 inbound-repcol show
2-120
partner
CLI Reference
Variable
partner_name
Subcommands
delete repcolset
Deletes an inbound replica collection set from the group. This deletes
the replicas in the collection.
select repcolset
show
Examples
The following command shows a partners replica collection sets stored in the group:
> partner select psgroup2 inbound-repcolset show
The following command shows the replica collections in an inbound replica collection set:
> partner select psgroup2 inbound-repcolset select vc1.1 show
partner
2-121
CLI Reference
Variable
partner_name
Subcommands
delete
select
Selects a partners replica set in order to display the replicas in the replica
set, clone a replica, delete a replica, or promote the replica set.
show
Variables
partner_name
set_name
2-122
partner
CLI Reference
Example
Variables
partner_name
set_name
Subcommands
access
clone
Clones a replica.
delete
Deletes a replica.
lost-blocks mark-valid
Sets the replica online and marks the lost cached blocks as
valid. This option may present a security risk, and the blocks
may contain old data.
Lost cached blocks can occur if a power failure lasts longer
than 72 hours.
manual-xfer done
partner
2-123
CLI Reference
promote keep-demote
[retain-iscsi-name]
promote [parameters]
show
Variables
partner_name
set_name
2-124
partner
CLI Reference
Subcommands
create
select
delete
show
Example
The following command shows the access control record for replica placeholder for a
volume configured to use manual transfer replication:
> partner select group1 inbound-replicaset select test1.1 access show
ID Initiator
Ipaddress
AuthMethod UserName
Apply-To
--- -------------- --------------- ---------- ---------- ------1
*.*.*.*
chap-local group1
both
Variables
partner_name
set_name
partner
2-125
CLI Reference
Parameters
username chap_name
ipaddress address
initiator name
Examples
The following command creates an access control record to grant access to a specific
CHAP user and sets the authentication method to CHAP:
> partner select secondary inbound-replicaset select vol-1.1 access
create username dbuser authmethod chap
Created access entry with ID 2.
The following command creates an access control record for a specific IP address
(supported only for IPv4 addresses):
> partner select secondary inbound-replicaset select vol-1.1 access
create ipaddress 172.17.30.22
Created access entry with ID 3.
2-126
partner
CLI Reference
The following command creates an access control record for an initiator name:
> partner select secondary inbound-replicaset
select vol-1.1 access create
initiator iqn.1991-05.com.microsoft:admin-pc.company.com
Variables
partner_name
set_name
access_entry_id
Example
partner
2-127
CLI Reference
Variables
partner_name
set_name
access_entry_id
Subcommand
show
Parameters
authmethod chap | none Specifies whether the record uses CHAP authentication (chap) to
restrict access to the volume. The default is none; CHAP
2-128
partner
CLI Reference
ipaddress address
username chap_name
Examples
The following command shows detailed information about a particular access control
record for an inbound replicaset:
> partner select secondary inbound-replicaset select vol-1.1 access select
1 show
_______________________ Access Information _______________________
Initiator:
Ipaddress: *.*.*.*
AuthMethod: chap-local
UserName: secondary
Apply-To: both
__________________________________________________________________
The following commands modify the CHAP user name for an access control record, and
show the detail information for the record before and after the change:
> partner select secondary inbound-replicaset select vol-1.1 access select
2 show
______________________ Access Information ________________________
Initiator:
Ipaddress: *.*.*.*
AuthMethod: chap
UserName: jsmith
Apply-To: snapshot
_________________________________________________________________
partner
2-129
CLI Reference
Format
partner select partner inbound-replicaset select set_name clone
replica_name new_volume [parameter...]
Variables
partner_name
set_name
replica_name
Name of a replica.
new_volume
2-130
partner
CLI Reference
Parameters
description text
read-write | read-only
offline | online
snap-reserve n%
snap-warn n%
snap-depletion action
iscsi-alias alias
unrestricted
bind member
partner
2-131
CLI Reference
Example
The following command clones an inbound replica and creates a volume named
v1-clone:
> partner select psgroup11 inbound-replicaset select v1.1 clone
v1.1-2009-01-26-11:19:27.15 v1-clone
Note: You cannot delete the most recent replica, or the only replica in a set.
Before deleting an inbound replica, pause inbound replication from the partner to the
group. See partner select inbound-pause on page 2-119.
If possible, manage replicas and replica sets from the primary group (where the original
volume is stored).
Format
partner select partner_name inbound-replicaset select set_name delete
replica_name
Variables
partner_name
set_name
replica_name
Name of a replica.
Example
> partner select psarray11 inbound-replicaset select dbvol.1 delete
dbvol.1-2009-01-24-16:17:32.9
2-132
partner
CLI Reference
Variables
partner_name
set_name
Example
The following example sends a confirmation message for a manual transfer replication for
a volume that originated on group2:
> partner select group2 inbound-replicaset select emailvol manual-xfer
done
partner
2-133
CLI Reference
Permanent promotion to a volume. Replication of the original volume stops and the
replica set is deleted from the group. This promotion is permanent; the volume cannot
later be demoted to the original inbound replica set (although it can be demoted to a
failback replica set).
By default when you promote permanently, the volume will have a new, unique iSCSI
target name, and hosts must access the volume through the IP address of the current
group. Optionally, you can specify that the new volume retain the iSCSI target name
(and SCSI identification number) of the original volume. However, there must be only
one volume associated with a particular target name and SCSI ID.
See the Group Administration manual for detailed information about failback procedures.
Note: Promoting a replica set will fail if replication is in progress for the replica set that
you are trying to promote. You must pause inbound replication before promoting a
replica set, then resume it after the promotion. See partner select inbound-pause on
page 2-119.
Promoting a replica set does not consume additional pool space on the secondary group.
The volume and its snapshot reserve will use exactly the amount of space that was
allocated to the replica set in its storage pool, and the delegated space on the recovery
group will be reduced by that same amount.
Format for Permanent Promotion
partner select partner_name inbound-replicaset select set_name promote
new_volume [parameter...]
2-134
partner
CLI Reference
Variables
partner_name
set_name
new_volume
Parameters
description text
read-write | read-only
offline | online
snap-warn n%
snap-depletion action
iscsi-alias alias
unrestricted
retain-iscsi-name
partner
Sets the new volume target iSCSI name identical to the iSCSI
target name (and SCSI ID) of the original volume.
2-135
CLI Reference
Examples
Variables
partner_name
set_name
Example
2-136
partner
CLI Reference
Format
partner select partner_name inbound-replicaset show
Variable
partner_name
Example
The following command shows the inbound replica sets from partner psgroup2:
> partner select psgroup2 inbound-replicaset show
Name
--------------v1.1
v2.1
ReservedSpace
------------50GB
100.01GB
FreeSpace
------------2.62GB
4.53GB
Replicas
-------5
3
Status
-----online
online
Variable
partner_name
Example
The following command resumes replication from the partner to the group:
> partner select psgroup2 inbound-resume
partner
2-137
CLI Reference
Format
partner select partner_name outbound-pause
Variable
partner_name
Example
The following command pauses all replication from the group to the partner:
> partner select AGroup outbound-pause
Variable
partner_name
Subcommands
delete repcol
select repcol
show [custom]
2-138
partner
CLI Reference
Examples
The following command shows the replica collections stored on the partner:
> partner select psgroupa outbound-repcol show
Variable
partner_name
Subcommands
delete repcolset
select repcolset
show
partner
2-139
CLI Reference
Examples
The following command shows the group replica collection sets stored on the partner:
> partner select psgroupa outbound-repcolset show
Collection
NoOfRepcols
Status
-------------------- --------------------- ---------vc1
2
enabled
The following command shows the replica collections in an outbound replica collection
set:
> partner select psgroupa outbound-repcolset select vc1 show
Variable
partner_name
2-140
partner
CLI Reference
Subcommands
delete
select
Selects a replica set for the purpose of deleting a replica or showing the
replicas in the replica set.
show
Format
partner select partner_name outbound-replicaset delete set_name
Variables
partner_name
set_name
Example
partner
2-141
CLI Reference
Format
partner select partner_name outbound-replicaset select set_name subcommand
Variables
partner_name
set_name
Subcommands
delete
Deletes a replica.
show
Format
partner select partner_name outbound-replicaset select set_name delete
replica
Variables
partner_name
set_name
2-142
partner
CLI Reference
Example
Variables
partner_name
set_name
Example
The following command selects an outbound replica set, and shows details about that
replica set:
> partner select psgroup1 outbound-replicaset select v1 show
__________________ Outbound-Replicaset Information _______________
Name: v1
Remote-Rep-Reserve: 200%
Local-Rep-Reserve: 100%
Borrow-Space: enabled
DesiredStatus: enabled
Status: ready
RemoteISCSIName:
Remaining Data: 0MB
iqn.2001-05.com.equallogic:6-8a0700- Completed Data: 0MB
54f0e0a02-3bdff02a6c641534-v1.1
StartingTime: None
________________________ Outbound-Replicas ______________________
Name
TimeStamp
---------------------------------------------------------v1.1-2006-07-10-11:23:44.1666
Mon Jul 10 11:23:44 2006
v1.1-2006-07-10-12:23:43.1670
Mon Jul 10 12:23:43 2006
v1.1-2006-07-10-13:23:54.1676
Mon Jul 10 13:23:54 2006
partner
2-143
CLI Reference
Variable
partner_name
Example
CurrReplicas
-----------10
6
Status
-----ready
ready
Remaining
--------0MB
0MB
StartingTime
-----------------2009-01-26:14:00:01
2009-01-26:17:12:44
Variable
partner_name
Example
2-144
partner
CLI Reference
Variable
partner_name
Parameters
failback-replicasets
inbound-replicas
inbound-replicasets
outbound-replicas
outbound-replicasets
Example
partner
2-145
CLI Reference
partner show
Shows the following details about the groups replication partners:
RecvUsed Used partner space delegated to the group. (Not shown if you specify the
-poolinfo option.)
Pool Pool containing the delegated space for the partner. (Only shown if you
specify the -poolinfo option.)
Format
partner show [-poolinfo]
Examples
The following command shows details about the groups replication partner:
> partner show
Name Received RecvUsed Delegated DelegUsed OutboundStatus InboundStatus
----- -------- -------- --------- --------- -------------- -------------group1
1069.85GB 4.42GB
951.9GB
148.3GB
enabled
paused
The following command shows details about the pool from which delegated space is
consumed:
> partner show -poolinfo
Name
Received Delegated DelegUsed OutboundStatus InboundStatus Pool
---------- -------- --------- --------- -------------- ------------- -------group1
1069.85GB 951.9GB
148.3GB
enabled
paused
default
2-146
partner
CLI Reference
Description
authfailure
cancelling
completed
disabled
failed
farenddown
inprogress
manual-transfer-in-progress
partner-down
partner-paused-inbound
partner-paused-outbound
paused
pause-max-snaps-reached
partner
2-147
CLI Reference
Description
paused-remote-reserve-low
paused-remote-resize-failed
stopped
waiting
2-148
partner
CLI Reference
pool
Manages pools in the group. The storage in a group can be organized into one to four
pools. A pool contains the storage space on the members that belong to the pool.
A member can belong only to one pool at a time. Unless otherwise specified, a member is
added to the default pool (by default, this pool is named default). If you delete a pool,
the members in the pool are automatically moved to the default pool.
Volumes are created in the default pool, unless you specify otherwise.
You can remove a member or volume from a pool and add it to a different pool. When you
move a member from one pool to another, the remaining pool members must have
sufficient free space to store the volume data from the removed member. When you move
a volume to a different pool, the new pool must have sufficient free space to store the
volume data.
Note: Pool move operations can be slow because the data movement will compete with
user I/O for computational and network bandwidth.
You can also merge one pool into another pool, called the destination pool.
Only one member or volume at a time can be moved into or out of a pool, unless you are
merging one pool into another.
Recommendation: Dell recommends that pool members with the same disk spin rate
have the same RAID level. For example, if a pool contains two
members that have 7200 RPM disks installed, configure both
members with the same RAID level.
Format
pool subcommand
Subcommands
create
Creates a pool.
delete
Deletes a pool.
merge
rename
Renames a pool.
pool
2-149
CLI Reference
select
show
pool create
Creates a pool in the group. Optionally, you can specify a description for a pool.
Format
pool create pool_name [description]
Variables
pool_name
description
Example
pool delete
Deletes a pool from the group. The members in the pool are immediately moved to the
default pool.
Restriction: You cannot delete the default pool.
Format
pool delete pool_name
Variable
pool_name
2-150
pool
CLI Reference
Example
pool merge
Merges one pool into a different pool, called the destination pool.
The group adds the members and volumes from the merged pool to the destination pool
and then deletes the empty pool.
Format
pool merge source_pool destination_pool
Variables
source_pool
destination_pool
Destination pool to which the group adds members and volumes from
the merged pool.
Example
The following command merges the members and volumes from the staff pool into the
default pool:
pool merge staff default
If you merge one pool into another pool, the pool being merged is deleted
after its members are moved to the destination pool. Are you sure you want
to merge the pool? (y/n) [n] y
pool rename
Renames a pool. You can rename the default pool.
pool
2-151
CLI Reference
Format
pool rename pool_name new_name
Variables
pool_name
Pool to rename.
new_name
Example
pool select
Selects a pool so that you can perform additional operations on it.
To remove a pool description, enter two quotation marks ().
Format
pool select pool_name description text
Variable
pool_name
Pool name.
Parameter
description text
Example
2-152
pool
CLI Reference
pool show
Shows information about all the pools in a group.
Format
pool show
pool
2-153
CLI Reference
save-config
Saves the group configuration to a file. You can use the information in this file to restore a
group in the event of a complete group failure.
Note: The save-config command does not save or enable you to restore volume data.
The save-config command creates a restoration file on the array, which contains the
CLI commands needed to recreate the group. For safe-keeping, use ftp or scp to copy the
file from the array (specify the group IP address in the ftp open or scp command) to a
host. For more information on using the ftp or scp commands to copy data off an array,
see diag on page 3-5.
By default, the restoration file is named config.cli, but you can specify a different file
name. For example, you can name the file for the date or group on which it was created.
Also, if you have several PS Series groups, you can give each groups file a unique name
to prevent confusion.
The save-config command can be run in default or group-only mode. Default mode
saves the configuration as a set of commands that you can run to restore the configuration.
Group-only mode saves some of the information as commands and some as commented
text, which you must manually edit.
Whenever any group configuration information changes, run the save-config command
again to create an updated restoration file. For example, run the command again after you:
Storage pools
2-154
save-config
CLI Reference
Member RAID level, pool, and network interface configuration (saved as comments
in -grouponly mode)
Event settings
Account configuration
Format
saveconfig [-verbose] [-grouponly] [file_name]
Parameters
-verbose
Specifies verbose mode; commands saved in the file are also shown
on-screen.
-grouponly
Variable
file_name
Examples
The following command saves the group configuration to a specified file name:
> save-config group23.cli
configuration saved to group23.cli
You can retrieve the file using ftp or scp.
save-config
2-155
CLI Reference
The following command saves the group configuration to the default file name, but
comments out the member and pool configuration:
> save-config -grouponly
configuration saved to config.cli
You can retrieve the file using ftp or scp.
Restoring a Group
If the group does not have the same number of members as it had before the failure, or
if the member names have changed, manually edit the restoration file to reflect the
new group configuration.
If the group members are not running the same firmware version that they were
running when you created the restoration file, the restoration may not succeed.
Before restoring a group, make sure the groups replication partners still have the
group configured as a replication partner. Otherwise, some commands might fail (for
example, enabling replication on a volume).
2-156
save-config
CLI Reference
6. Use telnet or SSH to connect to the group IP address and log in to the group. At the
CLI prompt, use the following format to run the commands in the restoration file:
exec -echo -ignore ../mgtdb/update/file_name
For example:
> exec -echo -ignore ../mgtdb/update/group23rest.cli
save-config
2-157
CLI Reference
show
Shows a summary of the group configuration or detailed information about a specific
group component.
Format
show parameter | -poolinfo
Option
-poolinfo
Parameters
account [active]
alerts
chapuser
collections
grpparams
Shows all the group parameters and their values. The output
is the same as for the grpparams show command.
member member_name |
-poolinfo
partners [-poolinfo]
pool
2-158
show
CLI Reference
recentevents
snapcol
usersessions
volume volume_name |
-poolinfo
show account
Shows all the group administration accounts.
Specify the active parameter to display the accounts currently logged in to the group.
For users logged in through the GUI, the active parameter also shows the remote IP
address of the user and the local IP address (that is, the group or member IP address to
which the user is connected).
Format
show account [active]
show
2-159
CLI Reference
Examples
Privilege
----------pool-admin
pool-admin
Status
-------enable
enable
LastLogin
--------------------2009-08-22:20:46:05
2009-08-17:08:34:25
The following command shows the accounts that are currently logged in to the group:
> show account active
Name
-------grpadmin
monitor
Type
-----telnet
gui-ssl
StartTime
--------------------2009-03-22:14:36:05
2009-03-23:17:16:25
Remote IP
Local IP
------------ ---------182.12.22.12 182.1.15.2
show alerts
Shows the event priorities (info, warning, error, or fatal) for e-mail and syslog
notification, if enabled.
Format
show alerts
Example
The following command shows the priorities for e-mail and syslog notification:
> show alerts
Notification Method
---------------------Email
SysLog
2-160
Priority
--------------------warning,error,fatal
info,warning,error,fatal
show
CLI Reference
show chapuser
Shows the local CHAP accounts configured in the group for iSCSI initiator authentication.
Format
show chapuser
Example
Password
---------------nty57nbe14gmg
jrmainline
testing
Status
------enable
enable
enable
show collections
Shows information about the volume collections in the group.
Format
show collections
Example
NoOfVolumes
----------3
2
NoOfSnapcols
------------2
4
show grpparams
Shows the group parameters and their current values.
show
2-161
CLI Reference
Format
show grpparams
Example
> show grpparams
________________________ Group Information _______________________
Name: kanga
Group-Ipaddress: 10.123.45.255
Def-Snap-Reserve: 100%
Def-Snap-Warn: 10%
Def-Snap-Depletion: delete-oldest Def-Thin-Growth-Warn: 60%
Def-Thin-Growth-Max: 100%
DateAndTime: Wed Apr 30 13:08:12 2009
TimeZone: America/New_York
Description:
Def-Iscsi-Prefix:
Def-Iscsi-Alias: yes
iqn.2001-05.com.equallogic
Info-Messages: enabled
Webaccess: enabled
Webaccess-noencrypt: enabled
Cliaccess-SSH: enabled
Cliaccess-Telnet: enabled
Email-Notify: disabled
Syslog-Notify: disabled
iSNS-Server-List:
Email-List:
NtpServers:
Smtp-Server-List:
Syslog-Server-List:
Target-Auth-UserName:
Target-Auth-Password:
PJJRh8PRZrBBx8pH
BJZpJHHXBzR2PJRH
Email-From:
Location: default
Conn-Balancing: enabled
Discovery-Use-Chap: disabled
Email-Contact:
Perf-balancing: enabled
Disallow-Downgrades: yes
Management-Ipaddress:
Aggressive-Congestion-Avoidance: none
__________________________________________________________________
_______________________ Radius Information _______________________
radius-auth-list:
login-radius-auth: disabled
radius-auth-retries: 1
radius-auth-timeout: 2secs
login-radius-acct: disabled
radius-acct-retries: 1
radius-acct-timeout: 2secs
iscsi-radius-auth: disabled
iscsi-local-auth: enabled
radius-acct-list:
login-radius-attr: enabled
__________________________________________________________________
________________________ Snmp Information ________________________
read-only-comms: public
read-write-comms:
trap-community: SNMP-trap
snmp-managers:
__________________________________________________________________
show member
Shows the members in the group or details about a specific member, including any
in-progress member operation, such as removing a member from a pool.
Format
show member [member_name | -poolinfo]
2-162
show
CLI Reference
Variable
member_name
Name of a member.
Examples
Disks
----48
48
Capacity
---------18062.61GB
5301.87GB
FreeSpace
---------17961.53GB
5200.79GB
Connections
---------0
0
The following command shows a summary of the group members and pool information:
> show member -poolinfo
Name
Status Version
------ ------- -------member1 online V4.0.0
member2 online V4.0.0
Disks
----48
48
show
2-163
CLI Reference
__________________________________________________________________
_____________________ Operations InProgress ______________________
ID StartTime
show partners
Shows the following information about the groups replication partners:
RecvUsed Used partner space delegated to the group. Not shown if you specify the
-poolinfo option.
paused).
paused).
Pool Shows the pool containing the delegated space for the partner. Shown only
with the -poolinfo option.
Format
show partners [-poolinfo]
show pool
Shows information about the pools in the group.
Format
show pool
2-164
show
CLI Reference
show recentevents
Shows event messages in the group, starting with the most recent.
When an event occurs (such as the creation of a volume or the removal of a power supply),
a message is sent. These messages help you monitor normal operations, and identify and
correct problems before they disrupt operations.
The show recentevents command shows one screen of information at a time, unless
paging has been turned off with the cli-settings paging off command. If paging
has been turned off, the command shows all events.
Each event has a priority. Table 2-4 lists event priorities in order from highest (most
severe) to lowest (least severe).
Table 2-4: Event Priorities
Priority
Description
FATAL
ERROR
WARNING
Potential problems in the group. An event with this priority may become an
event with ERROR priority if administrator intervention does not occur.
INFO
Message text
Format
show recentevents
show
2-165
CLI Reference
Example
> show recentevents
170:61:member2:SP:31-Jan-2009
20:08:29.320062:verify.c:338:INFO:14.2.14:0:
Parity verification completed on RAID LUN 0 after 16385 seconds.
.
.
.
312:189:member1:MgmtExec: 1-May-2009
00:00:00.230190:SnapColSchedule.cc:950:WARNING:8.3.11:
Replica collection schedule 'coll1-sched' failed to create a replica
collection.
.
.
.
58:52:member1:SP: 4-Apr-2009
13:32:56.470053:emm.c:1371:WARNING:28.3.51:
Warning health conditions currently exist. Investigate these conditions
before they affect array operation.
Control modules are initializing. Control module failover cannot occur
until the initialization completes.
There are 1 outstanding health conditions. Investigate these conditions
before they affect array operation.
.
.
.
4:2:member2:SP:30-Apr-2009 13:11:09.170003:emm.c:920:ERROR:28.4.50:
Control module in slot 1 is not functioning or not installed.
show snapcol
Shows information about the snapshot collections in the group.
Format
show snapcol
show usersessions
Shows information about the administration accounts that are currently logged in to the
group. For users logged in through the GUI, the following are shown:
2-166
show
CLI Reference
Local IP address. The group or member IP address to which the user is connected).
Format
show usersessions
Example
The following shows the accounts that are currently logged in to the group:
> show usersessions
Name
--------grpadmin
grpadmin
Type
--------telnet
gui-ssl
StartTime
Remote IP
Local IP
-------------------- -------------- ---------2009-06-14:09:36:51
2009-06-14:11:09:29 123.4.56.789
234.56.7.8
show volume
Shows the group volumes or information about a specific volume, including replication
partners (if replication is enabled), access control records, and in-progress operations for
the volume (for example, replication, bind, or pool move operations).
You can also display pool information for all the volumes.
Format
show volume [volume_name | -poolinfo]
Variable
volume_name
Name of a volume.
Examples
The following command shows all the volumes in the group and their status, including
whether the volume has thin provisioning enabled (in the column labeled TP):
> show volume
Name
Size
SnapShots Status
Permission Connections TP
------------- ------ --------- --------- ---------- ----------- -def000
1GB
0
online
read-write 0
N
show
2-167
CLI Reference
def001
def002
def003
def004
def005
1GB
1GB
1GB
1GB
1GB
0
0
0
0
0
online
online
online
online
online
read-write
read-write
read-write
read-write
read-write
0
0
0
0
0
N
N
N
N
N
The following command shows pool information (instead of permissions) for all volumes:
> show volume -poolinfo
Name
---vol01
vol02
vol03
vol04
data01
data02
Size
---10GB
15GB
20GB
50GB
200GB
500GB
SnapShots
--------1
0
0
0
0
1
Status
-----online
online
online
online
online
online
Connections
----------1
1
1
1
1
1
Pool
---default
default
default
default
default
default
TP
-N
N
N
N
Y
Y
Initiator
Ipaddress
AuthMethod UserName
Apply-To
iqn.1991-05.com.microsoft:kab *.*.*.*
bott-pc.equallogic.com
2-168
none
both
show
CLI Reference
show
2-169
CLI Reference
snapcol
Create and manage the snapshot collections in a group.
A snapshot collection contains snapshots of multiple volumes. A snapshot collection is
created each time you create snapshots of the volumes in a volume collection. A custom
snapshot collection is created when you create a snapshot of two or more individual
volumes at the same time.
To restore data, you can restore or clone an individual snapshot in a collection.
Format
snapcol subcommand
Subcommands
create
delete
Deletes a snapshot collection. This will delete the individual snapshots in the
collection.
rename
select
show
snapcol create
Creates a collection of simultaneous snapshots of the volumes in a volume collection, or
volumes you specify individually.
Format
snapcol create {collection_name | volume_name} [snapcol_name] [description
text]
Variables
collection_name
volume_name
2-170
snapcol
CLI Reference
snapcol_name
Parameter
description text
Examples
The actual snapshot collection name will have a timestamp appended; for example:
sc23monday-2009-06-15-13:28:54.49. If the name with the timestamp is longer
than 30 characters, the name will wrap in the output of the snapcol show command.
The timestamp portion of the name is always 23 characters long, and includes the leading
hyphen, year, month, day, and hour (separated by hyphens), then the minute and second
(separated by colons), a period, and an incremental number. This leaves seven (7) more
characters available on the output line for the user-defined part of the name.
The following command creates a snapshot collection from the specified volumes. The
snapshot collection name is created automatically:
> snapcol create vol1,vol2,vol3
Snapshot collection creation succeeded.
For the previous example, the snapshot collection name is snapcol followed by a
hyphen and the timestamp; for example: snapcol-2009-05-01-09:36:42.149.
snapcol delete
Deletes a snapshot collection and all the snapshots in the collection.
snapcol
2-171
CLI Reference
Format
snapcol delete snap_collection
Variable
snap_collection
Example
> snapcol delete scwednesday-2009-06-14-14:27:46.27
Do you really want to delete the snapshot collection? (y/n) [n]y
Snapshot collection deletion succeeded.
snapcol rename
Renames a snapshot collection. The new name is not automatically appended with a
timestamp.
Format
snapcol rename old_name new_name
Variables
old_name
new_name
Names are not case-sensitive. For example, snap-01 and SNAP-01 are
the same.
Example
snapcol select
Selects a snapshot collection so that you can modify the description or display details
about the snapshot collection.
2-172
snapcol
CLI Reference
Format
snapcol select snapcol_name [description text] | show
Variable
snapcol_name
Parameter
description text
Example
> snapcol select staff2-2009-03-09-14:52:16.52 show
snapcol show
Shows all snapshot collections or all custom snapshot collections in the group.
Format
snapcol show [custom]
Examples
The following command shows the custom snapshot collections in the group:
> snapcol show custom
snapcol
2-173
CLI Reference
volume
Manages the volumes in a group.
Format
volume subcommand
Subcommands
create
Creates a volume.
delete
Deletes a volume.
rename
Renames a volume.
select
show
volume create
Creates a volume in the group.
You must specify the volume name and the reported volume size. A volume will be
created in the default pool, unless you specify a different pool.
By default, a volume has read-write permission and is set online. A volume will use the
group-wide snapshot and iSCSI settings unless you override the settings when you create
the volume or modify the volume.
The reported volume size is seen by iSCSI initiators. The volume reserve is the actual
amount of space allocated to the volume. Snapshot reserve is based on a percentage of the
volume reserve.
Note: The actual amount of volume space is rounded up to the nearest multiple of 15MB.
You can enable thin provisioning on a volume. Thin provisioning can provide you with a
more efficient method of allocating storage space to users. However, it should only be
used in environments with administrators who can closely monitor disk space usage.
When you enable thin provisioning on a volume, you can change the default minimum and
maximum volume reserve values, in addition to the in-use space warning threshold.
2-174
volume
CLI Reference
See the Group Administration manual for more information on thin provisioned volumes.
When you create a volume, the group creates an iSCSI target name. This is the name that
iSCSI initiators use to access the volume through TCP/IP port 3260 (the standard iSCSI
port). The iSCSI target name starts with the iSCSI target prefix
(iqn.2001-05.com.equallogic), followed by a string, followed by the volume name.
The following is an example of an iSCSI target name for a volume names dbvol:
iqn.2001-05.com.equallogic:6-4b0200-062460afe-13000011cd5c1-dbvol
Format
volume create volume_name size [parameter]
Variables
volume_name
size[GB]
Parameters
bind member
Binds the new volume to the specified member. Volume data will
be restricted to this member.
Binding a volume to a member will override any RAID preference
and automatically performance load balancing for the volume.
description text
iscsi-alias alias
volume
2-175
CLI Reference
online | offline
pool pool
Pool in which the volume data will reside. The default is the
default pool.
read-write |
read-only
snap-depletion action
snap-reserve n%
snap-warn n%
thin-provision
thin-min-reserve n%
thin-growth-warn n%
2-176
volume
CLI Reference
thin-growth-max n%
unrestricted
Examples
The following command creates a 100 GB volume named dbvol in pool perf1:
> volume create dbvol 100GB pool perf1
Volume creation succeeded.
iSCSI target name is iqn.2001-05.com.equallogic:6-4b0200062460afe-13000011cd5c1-dbvol
The following command tries to create a volume larger than the free space in the default
pool. An error message shows the actual amount of free pool space:
> volume create total 3.05GB snap-reserve 0%
% Error - Available space is less than requested
Available Group space= 3120MB
Requested Volume size= 3123MB Requested Reserved Space= 0MB
The following command tries to create a volume in a pool that has enough space for the
volume, but not enough for the specified snapshot reserve:
> volume create hugevol 1200gb snap-reserve 200%
% Error - Available space is less than requested
Available Group space = 1690785MB
Requested Volume size = 1228800MB Requested Reserved Space = 2457600MB
volume
2-177
CLI Reference
The following command creates a thin-provisioned volume with the specified thresholds:
> volume create vol-thin1 200GB thin-provision thin-min-reserve \ 20%
thin-growth-warn 75% thin-growth-max 85%
Volume creation succeeded.
iSCSI target name is iqn.2001-05.com.equallogic:0-8a0906-5041d1a0261cffd39bde46374-vol-thin1
volume delete
Deletes a volume, which returns free space to the group.
Note: All snapshots associated with the volume are also deleted.
Format
volume delete volume_name
Variable
volume_name
Name of a volume.
Example
volume rename
Renames a volume.
The iSCSI target name does not change if you rename the volume, so no host
modifications are needed. However, if the iSCSI target alias for the volume is set to the
volume name, the alias will change to match the new volume name.
Format
volume rename volume_name new_name
2-178
volume
CLI Reference
Variables
volume_name
Name of a volume.
new_name
Example
volume select
Selects a volume so that you can perform additional operations on it.
Format
volume select volume_name subcommand | parameters
Variable
volume_name
Name of a volume.
Subcommands
access
clone
delete-failback new_volume
replicate-to-primary option
replication
schedule
volume
2-179
CLI Reference
show
shrink [no-snap]
[no-adjust-snap-resv] size[GB]
snapshot
Parameters
bind member
cancel-operation op_id
2-180
volume
CLI Reference
description text
iscsi-alias alias
lost-blocks action
offline | online
pool pool
volume
2-181
CLI Reference
pref-raid-policy policy
read-only | read-write
snap-depletion action
snap-reserve n%
snap-warn n%
2-182
volume
CLI Reference
thin-growth-warn n%
thin-growth-max n%
unbind
volume
2-183
CLI Reference
Examples
The following commands set a volume offline and change its permission to read-only:
> volume select dbvol offline
> volume select dbvol read-only
The following commands identify and then cancel an operation (identification number 1)
to move the volume vol-A to a different pool:
> volume select vol-A show
.
.
.
______________________ Operations InProgress ____________________
ID StartTime
-- ---------------1 2009-07-18:15:42:38
Operation Details
-----------------------------------------Moving from pool default to pool pool2
2-184
volume
CLI Reference
For testing purposes only, you can set up an access control record that gives unrestricted
host access to the volume and snapshots.
Format
volume select volume_name access subcommand
Variable
volume_name
Name of a volume.
Subcommands
create
delete
select
Selects an access control record for the purpose of showing or modifying the
record.
show
CHAP user name. To use CHAP for initiator authentication, you must set up local
CHAP accounts or specify an external RADIUS server. See chapuser on page 2-12
and grpparams cliaccess-ssh on page 2-41. You can allow or prevent (default)
unauthorized hosts from discovering targets that are only authenticated with CHAP.
See grpparams discovery-use-chap on page 2-50.
iSCSI initiator name. Create an access control record for each iSCSI initiator name
presented by an authorized host.
When you create an access control record, the record is automatically given an
identification number. Use this number to manage the record with the CLI.
volume
2-185
CLI Reference
Format
volume select volume_name access create parameter ...
Variable
volume_name
Name of a volume.
Parameters
apply-to type
initiator name
ipaddress address
username chap_name
Example
The following command creates an access control record that restricts volume access to a
host with IP address 123.13.3.44:
> volume select dbvol access create ipaddress 123.13.3.44
Created access entry with ID 2.
2-186
volume
CLI Reference
Variables
volume_name
Name of a volume.
Example
The following command deletes an access control record for volume dbvol:
> volume select dbvol access delete 2
Access entry deletion succeeded.
Variables
volume_name
volume
Name of a volume.
2-187
CLI Reference
Parameters
apply-to type
authmethod chap | none Specifies whether the record uses CHAP authentication (chap) to
ipaddress address
username chap_name
Examples
The following command shows information about an access control record for volume
dbvol:
> volume select dbvol access select 1 show
______________________ Access Information _______________________
Initiator:
Ipaddress: 182.19.1.123
AuthMethod: chap
UserName: tbase
Apply-To: both
2-188
volume
CLI Reference
The following command modifies the access control record in the previous example so
that it includes only IP address 182.20.30.44:
> volume select dbvol access select 1 ipaddress 182.20.30.44
Variable
volume_name
Name of a volume.
Example
The following command shows the two access control records for the volume mailvol:
> volume select mailvol access show
ID Initiator
--- --------1
2
IpAddress
----------182.23.23.23
114.33.23.13
AuthMethod
---------CHAP
none
UserName
Apply-To
---------- -------jchen
volume
both
volume
2-189
CLI Reference
However, a volume clone does not inherit the RAID preference policy of the parent
volume; the RAID policy for the clone is set to none, by default.
The new volume does not inherit the original volumes snapshot reserve settings; the new
volume is created with the group-wide default value for snapshot reserve. The new
volume also does not inherit the original volumes replication space settings or
configuration. To create replicas of the new volume, you must configure replication on the
new volume.
The new volume is available immediately and you can use and modify it as you would any
other volume.
The cloned volume will reside in the same pool as the original volume. To change the
pool, modify the new volume. The original volume is still available after the cloning
operation completes.
Format
volume select volume_name clone new_name parameter ...
Variables
volume_name
Name of a volume.
new_name
Parameters
bind member
description text
iscsi-alias alias
offline | online
read-write | read-only
2-190
volume
CLI Reference
snap-depletion action
snap-reserve n%
snap-warn n%
unrestricted
Example
The following command clones volume dbvol, creating the new volume vol3:
> volume select dbvol clone vol3
Volume creation succeeded.
iSCSI target name is
iqn.2001-05.com.equallogic:6-8b0900-2ae20000-99e00000067405b5-vol3
Cloning is in progress.
volume
2-191
CLI Reference
To replicate the volume, you must configure replication on the volume. The first
replication will require a complete transfer of the volume data.
Format
volume select volume_name delete-failback new_name
Variables
volume_name
new_name
Example
2-192
volume
CLI Reference
You can enable multi-host access to a target if you meet one of the following conditions:
Your cluster environment gives the initiators on each cluster computer a different
IQN, and the environment can manage multiple connections to a target. For example,
the environment uses a Distributed Lock Manager or SCSI reservations.
Your multipathing solution does not use the same IQN on all initiators, and you cannot
modify the names to be the same.
You use an environment, such as a virtual server, that can manage multiple
connections to the same iSCSI target (for example, through SCSI reservations).
In all cases, use access control records as the primary method of protecting targets in a
group.
Format
volume select volume_name multihost-access enable | disable
Variable
volume_name
Name of a volume.
Examples
volume
2-193
CLI Reference
Format
volume select volume_name replicate-to-primary subcommand
Variable
Name of a volume.
volume_name
Subcommands
start [manual-replica]
stop
retry
Examples
The following command starts a replication operation for a recovery volume to the
primary group:
volume select dbase_vol2.1 replicate-to-primary start
The following command starts a manual transfer replication operation for a recovery
volume to the primary group:
volume select vol_04.1 replicate-to-primary start manual-replica
Variable
volume_name
2-194
Name of a volume.
volume
CLI Reference
Subcommands
cancel
create-replica
[manual]
demote
disable
enable
pause
resume
select
show
Variables
volume_name
Name of a volume.
partner_name
Example
volume
2-195
CLI Reference
Variables
volume_name
Name of a volume.
partner_name
Parameter
manual
Specifies that you will use manual transfer replication. See the Manual
Transfer Utility documentation for more information.
Example
The following command creates a replica of a volume, specifying manual replication for
the data transfer:
> volume select vol-thin1 replication create-replica manual group2
2-196
volume
CLI Reference
Variables
volume_name
Name of a volume.
partner_name
Examples
The following commands set the recovery volume vol5.1 offline and demote it to an
inbound replica set:
> volume select vol5.1 offline
> volume select vol5.1 replication demote
1553:125:member1:MgmtExec: 1-May-2009
10:34:10.180126:snapshotRestore.cc:789:INFO:8.2.9:Volume successfully
restored from snapshot 'vol1.1-2009-04-05-09:36:14.13'. A new snapshot
'vol1.1-2009-05-01-10:34:10.109' was created from volume prior to being
restored.
1558:130:member1:MgmtExec: 1-May-2009
10:34:10.410131:volumeSecondaryDemote.cc:1590:INFO:7.2.38:Recovery volume
'vol1.1' has been successfully demoted to a replica set.
The following commands set a volume offline and demote it to a failback replica set:
> volume select data45 offline
> volume select data45 replication demote group2
Demoting a volume to a failback replica set enables you to replicate the
recovery volume to the primary group. Do you want to demote the volume?
(y/n) [n] y
volume
2-197
CLI Reference
Variables
volume_name
Name of a volume.
partner_name
Example
The local replication reserve percentage. This space stores the data that changes while
replication is in progress, and stores the failback snapshot. You can also allow the
2-198
volume
CLI Reference
volume to borrow pool space temporarily if the local replication reserve is not big
enough to store all the changes.
Whether to keep the failback snapshot (most recent complete replica) in the local
replication reserve. If you choose to keep the failback snapshot, you will need more
local replication reserve space than if not. If you have a failback snapshot, you may be
able to synchronize the groups upon failback by replicating only volume changes.
See the Group Administration manual for more information about failback.
Format
volume select volume_name replication enable partner_name [parameter...]
Variables
volume_name
Name of a volume.
partner_name
Parameters
remote-rep-reserve n%
local-rep-reserve n%
volume
2-199
CLI Reference
borrow-space enable |
disable
keep-failback
Examples
The following command enables replication of a to a partner, using the default local
replication reserve and replica reserve values:
>
The following command enables replication of a volume to a partner, and keeping the
failback snapshot:
> volume select vol2 replication enable group2 keep-failback
Variables
volume_name
Name of a volume.
partner_name
Example
2-200
volume
CLI Reference
Variables
volume_name
Name of a volume.
partner_name
Example
volume
2-201
CLI Reference
Format
volume select volume_name replication select partner_name show |
[parameter]
Variables
volume_name
Name of a volume.
partner_name
Parameters
borrow-space enable |
disable
keep-failback enable |
disable
local-rep-reserve n%
remote-rep-reserve n%
2-202
volume
CLI Reference
Examples
The following command shows the replication configuration for volume vo14 on partner
psgroup2:
> volume select vol4 replication select psgroup2 show
Description
disabled
enabled
paused
Variable
volume_name
Name of a volume.
Example
The following command shows the replication partner and status for a volume:
> volume select vol2 replication show
volume
2-203
CLI Reference
Schedules can create snapshots or replicas on an hourly, daily, or weekly basis. For
example, you can set up a schedule that creates a snapshot or replica once a day, once a
week, or every 2 hours during work hours.
Do not configure a replication schedule to start before you have completed the first
transfer, if using manual replication. The scheduled replication will be skipped if the first
transfer is not complete.
Note: Using a schedule can result in the creation of many snapshots or replicas. To
control the number of snapshots or replicas, use the max-keep command
parameter when creating a schedule. In addition, the size of the snapshot reserve
limits the number of snapshots you can create for a volume, and the size of the
replica reserve limits the number of replicas you can create for a volume.
Format
volume select volume_name schedule subcommand
Variable
volume_name
Name of a volume.
Subcommands
create
Creates a schedule.
delete
Deletes a schedule.
rename
Renames a schedule.
select
show
2-204
volume
CLI Reference
Schedule name
Schedule type
Optionally, you can specify other parameters, based on the schedule type.
Format
volume select volume_name schedule create schedule_name parameter ...
Variables
volume_name
Name of a volume.
schedule_name
Parameters
type type
read-write | read-only
max-keep n
frequency nmins |
nhour[s]
volume
2-205
CLI Reference
start-date mm/dd/yy
Month, day, and year that the schedule will start. The default
is the day that the schedule was created (or the following day,
if the starting time has already passed).
end-date mm/dd/yy
Month, day, and year that the schedule will stop. The default
is no ending date.
repeat-interval ndays
partner partner
enable | disable
Examples
The following command creates a replication schedule that creates a replica of volume
db1 on partner psgroup2 every day at 11:30 PM:
> volume select db1 schedule create dailydb type daily start-time 11:30PM
repeat-interval 1days partner psgroup2
Schedule creation succeeded.
The following command creates a snapshot schedule that creates snapshots of volume
mail5 every day, every 2 hours, from 7:00AM to 8:00PM:
> volume select mail5 schedule create msnap type daily start-time 07:00AM
end-time 20:00 frequency 2hours repeat-interval 1days
Variables
volume_name
2-206
Name of a volume.
volume
CLI Reference
schedule_name
Name of a schedule.
Example
Variables
volume_name
Name of a volume.
old_name
new_name
Example
volume
2-207
CLI Reference
Format
volume select volume_name schedule select schedule_name show |
parameter ...
Variables
volume_name
Name of a volume.
schedule_name
Name of a schedule.
Parameters
enable | disable
end-date mm/dd/yy
frequency nmins |
nhour[s]
max-keep n
read-only | read-write
repeat-interval ndays
start-date mm/dd/yy
type type
Examples
The following command changes the time that snapshots of volume staffvol2 are
created with the schedule bckup:
> volume select staffvol2 schedule select bckup start-time 10:15PM
2-208
volume
CLI Reference
The following command shows details about the replication schedule hourly2:
> volume select staff2 schedule select hourly2 show
__________________ Schedule Information ______________________
Name: hourly2
Type: hourly
Start-Date: 05/03/04
End-Date: None
Start-Time: 07:00AM
End-Time: 08:00PM
Frequency: 1hour
Repeat-Interval:
NextCreation: Fri May 5 14:00:00
Partner: psgroup4
2006
Variables
volume_name
Name of a volume.
schedule_name
Name of a schedule.
Example
The following command shows the snapshot and replication schedules for the volume
dbvol:
> volume select dbvol schedule show
Name
Interval DateRange
TimeRange Frequency
------- -------- ------------- ---------- --------hour4
hourly
04/28/04-None 12:00AM
5mins
NextCreate
----------Fri May 5
14:10:00 2006
volume
TimeRange
---------10:00PM
NextCreate Partner
----------- ------Fri May 5
beta1
22:00:00 2006
2-209
CLI Reference
Variable
volume_name
Name of a volume.
Parameters
access
connections
members
replicas
Volume replicas.
replication
schedules
snapshots
Snapshots.
Examples
Current status (Table 2-6), which describes the actual status of the volume.
Requested status (Table 2-7), which is set by the administrator and can be changed
using commands.
2-210
volume
CLI Reference
online
offline
offline-lost-cached-blocks
offline-max-grow-met
offline-member-down
offline-missing-pages
offline-nospace-auto-grow
offline-snap-reserve-met
volume
2-211
CLI Reference
Description
online
offline
online-lost-cached-blocks
The following command shows the access control records for a volume:
> volume select dbvol2 show access
ID
-1
2
Initiator
---------
Ipaddress
--------182.19.1.200
182.19.2.120
AuthMethod UserName
---------- -------none
chap
dos3
Apply-To
-------volume
both
The following command shows volume replicas being stored on partner beta1:
> volume select staff30 show replicas
____________________________ beta1 ______________________________
Name
TimeStamp
---------------------------------------------------------staff30.1-2006-07-10-21:50:30.1763
Mon Jul 10 21:50:30 2006
staff30.1-2006-07-10-22:50:05.1786
Mon Jul 10 22:50:05 2006
staff30.1-2006-07-10-23:49:59.1808
Mon Jul 10 23:49:59 2006
The following command shows information about the active iSCSI connections to a
volume:
> volume select dbvol2 show connections
Initiator
---------182.19.1.200
UpTime
-----------28min 58sec
RxData
TxData
------------- ----------0.00KB
12.00KB
The following command shows the amount of volume data on the members:
> volume select dbvol2 show members
Member Name
2-212
Contribution
volume
CLI Reference
--------------- -----------mem24
95.03GB
mem23
105.00GB
volume
2-213
CLI Reference
Variables
volume_name
Name of a volume.
new_size[GB]
New smaller size for the volume. Size is in megabytes unless you
specify otherwise. You can specify size with any of the following
suffixes: m, mb, MB, g, gb, or GB.
Parameters
no-snap
Does not create a snapshot of the volume before reducing its size.
no-adjust-snap-resv
Example
The following commands set volume bigvol offline and shrink it from 100GB to 50GB,
creating a snapshot:
> volume select bigvol offline
> volume select bigvol shrink 50g
Be sure the file system and/or application using the volume supports
volumes getting smaller. Shrinking a volume could result in losing data.
Using the no-adjust-snap-resv option can result in losing old snapshots.
Do you really want to continue? (y/n) [n]y
Creating snapshot.
2-214
volume
CLI Reference
If you specify a size larger than the amount of available pool space, an error message
shows the actual available space.
Unless you specify the no-snap option, a snapshot will be created for the volume before
the volume size is increased.
Format
volume select volume_name size [no-snap] new_size
Variables
volume_name
Name of a volume.
new_size[GB]
New, larger size for the volume. Size is in megabytes unless you
specify otherwise. You can specify size with any of the following
suffixes: m, mb, MB, g, gb, or GB.
Example
Variable
volume_name
Name of a volume.
Subcommands
create-now
delete
Deletes a snapshot.
rename
Renames a snapshot.
select
volume
2-215
CLI Reference
show
Variable
volume_name
Name of a volume.
Parameters
offline | online
Example
The following command creates a snapshot at the current time with read-only permission:
> volume select dbvol snapshot create-now read-only
Snapshot creation succeeded.
snapshot name is dbvol-2009-01-25-11:28:01.5
2-216
volume
CLI Reference
To display snapshot names, see volume select snapshot show on page 2-225.
Format
volume select volume_name snapshot delete snap_name
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
Example
Variables
volume_name
Name of a volume.
old_name
Name of a snapshot.
new_name
volume
2-217
CLI Reference
Example
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
Subcommands
clone
restore
multihost-access enable |
disable
show [connections]
Parameters
description text
iscsi-alias alias
2-218
volume
CLI Reference
isns-discovery enable |
disable
lost-blocks action
Note that lost cached blocks can occur if a power failure lasts
longer than 72 hours.
offline | online
Snapshot status.
read-only | read-write
Snapshot permission.
Examples
volume
2-219
CLI Reference
By default, the new volume will be set online with read-write permission, and will use the
group-wide snapshot space and iSCSI settings.
Clones are volumes, and are shown in the output of the volume show command. The
clone is in the same pool as the original volume. The snapshot is still available.
Format
volume select volume_name snapshot select snap_name clone new_volume
[parameters]
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
new_volume
Parameters
bind member
description text
iscsi-alias alias
offline | online
read-only | read-write
snap-depletion action
2-220
volume
CLI Reference
snap-reserve n%
snap-warn n%
unrestricted
Example
The following command clones a snapshot and names the new volume stf2:
> volume select stf snapshot select stf-10-2009-01-11-15:44:35.11 clone
stf2
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
volume
2-221
CLI Reference
Example
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
2-222
volume
CLI Reference
Example
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
Example
Table 2-8 lists the possible values for the current status of a snapshot (Status field).
Table 2-8: Current Snapshot Status
Status
online
offline
offline-lost-cached-blocks
volume
2-223
CLI Reference
offline-inconsistent
offline-member-down
offline-nospace-auto-grow
offline-snap-reserve-met
offline-max-grow-met
Table 2-9 lists the possible values for the requested status of a snapshot, which is set by an
administrator (DesiredStatus field).
Table 2-9: Requested Snapshot Status
Status
Description
online
offline
2-224
volume
CLI Reference
Description
online-lost-cached-blocks
Variables
volume_name
Name of a volume.
snap_name
Name of a snapshot.
Example
> volume select dbvol1 snapshot show
volume show
Shows the group volumes or detailed information about a specific volume, including
access control records and in-progress operations (for example, replication, bind, or pool
move operations).
Format
volume show [volume_name]
Variable
volume_name
volume
Name of a volume.
2-225
CLI Reference
Example
> volume show
Name
Size
SnapShots Status
Permission Connections TP
--------------- ---------- --------- -------------- ---------- ----------- Vol22
100GB
0
online
read-write 0
N
2-226
volume
Command name
Brief description
Examples
Description
Clears lost data on an array (see clearlostdata on page 3-3).
Collects diagnostic information from an array (see diag on page 3-5).
Verifies connectivity between an array and other hosts on the network (see
ping on page 3-10).
Resets an array to the factory defaults (original condition) (see reset on
page 3-12).
Shuts down and restarts an array (see restart on page 3-14).
Configures an array and either creates a new group or adds the array to a
group (see setup on page 3-16).
Performs a clean shutdown of an array (see shutdown on page 3-21).
Updates the firmware on an array (see update on page 3-23).
3-1
CLI Reference
9600 baud
No parity
8 data bits
3-2
CLI Reference
clearlostdata
Clears lost data blocks on an array.
Caution:
Use the clearlostdata command when blocks have been lost but the array does not
know which blocks have been lost. In this case, the array will not be able to boot or will no
longer be accessible from the network.
To access the CLI to run the clearlostdata command, see Running Array Management
Commands on page 3-2.
Once connected to the array (either through a serial connection or a network connection to
an IP address for a network interface), press the <Enter> key and log in to a group
administration account that has read-write permission (for example, the grpadmin
account). The console will describe the problem and recommend that you use the
clearlostdata command to try to correct the lost block problem. At the CLI prompt,
enter the clearlostdata command.
The clearlostdata command may or may not be able to correct the entire lost blocks
problem. In some cases, the problem may be corrected enough to boot the array. If
volumes remain offline, you may not be able to recover the data on them. In these cases,
you must delete the volumes, recreate them, and recover the data from a backup or replica.
If the array is a member of a group and the clearlostdata command does not resolve
the problem, the array will not boot and you might have to delete the member from the
group. If you delete the member, the array will be reset and returned to its factory defaults.
Only delete an offline member in extreme circumstances because resetting the array will
remove any data on the array. See member delete on page 2-79.
Format
clearlostdata
clearlostdata
3-3
CLI Reference
Example
The following example shows how to log in to the grpadmin account from a console
terminal and run the clearlostdata command on the array.
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
3-4
clearlostdata
CLI Reference
diag
Collects diagnostic information from an array and sends it in an e-mail message to your
support provider.
Run the diag command only if instructed by your support provider.
The diag output does not contain any data from user volumes in any form.
You can retrieve data collected from the diag command as follows:
E-mail. If e-mail event notification is enabled, and if at least one Ethernet interface on
the array is up and operational, the diag command output is automatically mailed to
the e-mail addresses configured for notification, or to those you specify with the -e
option. The output is sent in one to eight separate e-mail messages, which are encoded
for efficient transmission, and are not human-readable. See grpparams email-notify on
page 2-52 for information about configuring e-mail event notification.
If a problem occurs between the SMTP server and the destination e-mail client, the
messages may not be sent.
FTP or SCP. If e-mail notification is not enabled, or if the messages are not sent, you
can log into the array with FTP or SCP and retrieve the files manually. However, this
method relies on having at least one Ethernet interface up and operational.
Capturing the output using the console interface. This is the method of last resort,
if e-mail and FTP or SCP do not work. To use this method, configure your terminal
emulator, telnet, or ssh client to collect all the text that is sent to the screen, and
answer y to the final prompt.
To access the CLI to run the diag command, see Running Array Management Commands
on page 3-2.
Once connected to the array (either through a serial connection or a network connection to
an IP address for a network interface), press the <Enter> key and log in to a group
administration account that has read-write permission (for example, the grpadmin
account). At the CLI prompt, enter the diag command.
Format
diag [options]
Options
diag
3-5
CLI Reference
Options can be used in any combination, separated by spaces. All options used must be
enclosed in one set of quotes.
-b
-e name@address
-n
Sends no e-mail with the output. You must retrieve the output with FTP
or SCP or use the option to dump output to the console.
-u
Uses current output files. Skips the data-collection step and tries to
resend files from the previous diag command.
Examples
The following example shows how to connect to an IP address for a network interface on
an array and run the diag command. In this example, e-mail notification has already been
configured to send the output to user@email.com.
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001 2009 Dell, Inc.
> diag
The diag command will gather configuration data from this array
for support and troubleshooting purposes. No user information will be
included in this data.
Results will be sent to "user@mail.com" through e-mail.
If this is unsuccessful, other options for retrieving the results
will be presented at the end of the procedure.
Do you wish to proceed (y/n) [y]:y
Starting data collection on Thu Jul 31 15:23:19 EDT 2009.
3-6
diag
CLI Reference
Section 1 of 15: ..
Finished in 1 seconds
Section 2 of 15: .........0.........0...
Finished in 11 seconds
Section 3 of 15: ....
Finished in 8 seconds
Section 4 of 15: .........0......
Finished in 2 seconds
Section 5 of 15: .........0......
Finished in 4 seconds
Section 6 of 15: .........0........
Finished in 3 seconds
Section 7 of 15: .
Finished in 6 seconds
Section 8 of 15: ....
Finished in 1 seconds
Section 9 of 15: .........0.........0.
Finished in 1 seconds
Section 10 of 15: ...
Finished in 0 seconds
Section 11 of 15: .........0.........0........
Finished in 32 seconds
Section 12 of 15: ..
Finished in 0 seconds
Section 13 of 15: .
Finished in 30 seconds
Section 14 of 15:
.........0.........0.........0.........0.........0.........0.........0..
.......0.........0.........0..
.......0.........0.........0.........0.........0.........0.........0...
Finished in 55 seconds
Section 15 of 15: .
Finished in 0 seconds
Sending
Sending
Sending
Sending
Sending
diag
e-mail
e-mail
e-mail
e-mail
e-mail
1
2
3
4
5
of
of
of
of
of
5.
5.
5.
5.
5.
3-7
CLI Reference
You have the option of retrieving the diagnostic data using FTP or SCP.
To use FTP, use the 'mget' command to retrieve all files matching the
specification "Seg_*.dgo". You must use the "grpadmin" account and
password, and connect to one of the IP addresses from the list below.
To use SCP, enter the command: 'scp -r grpadmin@x.x.x.x:. destdir' where
"x.x.x.x" is one of the IP addresses from the list below. Then, in the
destination location, look for files with the name "Seg_*.dgo". You can
delete any other files retrieved by scp.
Here are the IP addresses you can use to retrieve files from this member:
19.127.22.111
19.127.22.110
19.127.22.112
19.119.22.113
19.119.22.110
You also have the option to capture the output by using the "text
capture" feature of your Telnet or terminal emulator program.
Do you wish to do this (y/n) [n]:n
The following example shows how to use the FTP utility to copy the diag output file
from the array to a host. Use FTP on the host and enter the FTP open command,
specifying an IP address for one of the arrays network interfaces.
When prompted, enter the grpadmin account and password. Specify the diag output file
with the mget command.
$ ftp
ftp> open 123.14.1.132
Connected to 123.14.1.132.
220 123.14.1.132 FTP server ready.
User: grpadmin
331 Password required for grpadmin.
Password:
230 User grpadmin logged in.
Using binary mode to transfer files.
ftp> mget Seg_*.dgo
mget Seg_1.dgo? y
227 Entering Passive Mode (123,14,1,132,255,102)
150 Opening BINARY mode data connection for 'Seg_1.dgo' (614247 bytes).
226 Transfer complete.
614247 bytes received in 1.33 secs (4.5e+02 Kbytes/sec)
mget Seg_2.dgo? y
227 Entering Passive Mode (123,14,1,132,255,101)
150 Opening BINARY mode data connection for 'Seg_2.dgo' (880243 bytes).
226 Transfer complete.
3-8
diag
CLI Reference
diag
3-9
CLI Reference
ping
Verifies connectivity from an array to other hosts on the network.
For example, you can use the ping command to test connectivity from an array to the host
bus adapters (HBAs) or NICs on a server. The command is also useful for verifying
connectivity to the groups SMTP server, NTP server, or default gateway.
If multiple network interfaces are configured on an array, you can specify the network
interface from which you want to test connectivity. If you do not specify a network
interface on the array, any configured interface will be used.
To access the CLI to run the ping command, see Running Array Management Commands
on page 3-2.
Once connected to the array (either through a serial connection or a network connection to
an IP address for a network interface), press the <Enter> key and log in to a group
administration account that has read-write permission (for example, the grpadmin
account). At the CLI prompt, enter the ping command.
Use Ctrl/C to stop the ping command.
Format
ping ip-address | "-I array-ip-address ip-address"
Variables
ip-address
array-ip-address
3-10
ping
CLI Reference
Examples
The following ping commands test connectivity from an array to a server and from a
specific network interface on an array to a server:
psg1> ping 182.17.1.110
PING 182.17.1.110 (192.17.1.110): 56 data bytes
64 bytes from 182.17.1.110: icmp_seq=0 ttl=59 time=0.000 ms
64 bytes from 182.17.1.110: icmp_seq=5 ttl=59 time=0.000 ms
^C
----192.17.1.110 PING Statistics---6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms
psg1> ping "-I 182.17.4.88 182.16.20.140"
PING 182.16.20.140 (192.16.20.140): 56 data bytes
64 bytes from 182.16.20.140: icmp_seq=0 ttl=127 time=0.000 ms
64 bytes from 182.16.20.140: icmp_seq=3 ttl=127 time=0.000 ms
^C
----192.16.20.140 PING Statistics---4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms
ping
3-11
CLI Reference
reset
Resets an array to the factory defaults (original condition). The reset command shows a
confirmation message to which you must agree before it starts the operation.
Before resetting an array, call your PS Series support provider.
Caution:
The reset command irretrievably removes all group, member, and volume
configuration information and any volume data on the array. The array will
not be able to connect to a group until you add it to the group.
3-12
reset
CLI Reference
Example
When you run the reset command and agree to the operation, the network connection
closes:
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
psg22> reset
Warning: This command resets an array to the factory
defaults (original condition). The result is the
elimination of all group and volume configuration
information and any volume data residing on the array.
Before resetting an array that is a member of a group,
it is recommended that you delete the member from the
group.
Reset this array to factory defaults? [n/DeleteAllMyDataNow]>
DeleteAllMyDataNow
Connection closed by foreign host.
$
reset
3-13
CLI Reference
restart
Shuts down and restarts an array. Restarting an array has no effect on member, volume, or
group configuration information or volume data. When the restart completes, the member
rejoins the group automatically. Volumes with data located on the member will be
unavailable until the restart completes.
Note: Restart an array only when you are updating the array firmware. Do not repeatedly
restart an array.
To access the CLI to run the restart command, see Running Array Management
Commands on page 3-2.
When you are connected to the array (either through a serial connection or a network
connection to an IP address for a network interface), press the <Enter> key and log in to
a group administration account that has read-write permission (for example, the
grpadmin account). At the CLI prompt, enter the restart command.
When you restart an array, network connections are closed and the array is shut down.
Then, the array automatically restarts.
Note: If you physically connect a serial cable to the secondary control module and run the
restart command, only the secondary control module will be restarted.
To restart both control modules, connect the cable to the active control module
(ACT LED will be green) and run the restart command. Then, connect the cable to
the other control module (now the active control module), and run the restart
command again.
Format
restart
3-14
restart
CLI Reference
Example
When you run the restart command and type yes at the confirmation prompt, the
network connection closes.
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
psg22> restart
Do you really want to restart the system? (yes/no) [no] yes
Connection closed by foreign host.$
restart
3-15
CLI Reference
setup
Interactive utility that configures an array as either:
The first member of a new group that you create while running setup
When creating a new group, you can use the IPv4 or IPv6 protocol, depending on your
network environment.
When adding a member to an existing group, the new member must use the same protocol
as the group. If the member is joining an IPv6 group, specify the ipv6 option with the
command.
After a group is set up, you can later change its protocol with some restrictions. If the
group has a configured replication partner, you must change the partner network address
on both groups.
Both groups must use a common protocol for replication to succeed. For example, if one
group uses only IPv4 and the other group can use either IPv4 or IPv6, replication is
supported. If one group uses only IPv4 and the other uses only IPv6, replication is not
supported.
For more information on the supported protocol configurations on replication partners, see
partner create on page 2-99.
Format
setup [ipv6]
Option
ipv6
3-16
setup
CLI Reference
The following example shows how to set up a new group using the default IPv4 protocol
for the network interface and the group address. This is the only supported protocol for all
versions of PS Series Firmware prior to V4.0.
> setup
Group Manager Setup Utility
The setup utility establishes the initial network and storage
configuration for a storage array and then configures the array
as a member of a new or existing group of arrays.
For help, enter a question mark (?) at a prompt.
Do you want to proceed (yes | no) [no]: yes
Initializing.
Enter the IP address and name of the group that the array will join.
Group name []:v4group
Group IP address []: 10.127.19.150
Searching to see if the group exists.
minutes.
sure you
setup
3-17
CLI Reference
The differences between an IPv4 setup and an IPv6 setup are as follows:
The first time you log in to an uninitialized array (when creating a new group or when
adding a member to a group), the setup utility starts automatically, and by default
uses the IPv4 protocol. Cancel the setup (enter n at the prompt that asks if you want to
set up the array) and enter the command: setup ipv6.
You do not have to enter an IP address for the network interface (eth0). Your router
broadcasts available addresses (shown during the setup) and the network interface
uses one of those addresses.
When creating a new group or specifying the group that a member will join, enter the
group IP address in IPv6 format (for example, fc00::abc1:def2:cba3:fed4),
instead of IPv4 format (for example, 10.234.56.255).
The following example shows how to set up a new group using the IPv6 protocol for the
Ethernet 0 network interface and the group address. Note that you do not have to enter an
3-18
setup
CLI Reference
IP address for the Ethernet 0 interface. Press Enter at the prompt to let the interface use
one of the broadcast addresses.
> setup ipv6
Group Manager Setup Utility
The setup utility establishes the initial network and storage
configuration for a storage array and then configures the array
as a member of a new or existing group of arrays.
For help, enter a question mark (?) at a prompt.
Do you want to proceed (yes | no) [no]: yes
Initializing.
The group does not exist or currently cannot be reached. Make sure you
have entered the correct group IP address and group name.
Do you want to create a new group (yes | no) [yes]: yes
Group Configuration
Group Name:
Group IP address:
v6group
fc00::abc1:def2:cba3:fed4
Do you want to use the group settings shown above (yes | no) [yes]:
Do you want to use the group settings shown above (yes | no) [yes]: yes
Password for managing group membership:**********
Retype password for verification:**********
Password for the default group administration account:**********
Retype password for verification:**********
setup
3-19
CLI Reference
3-20
setup
CLI Reference
shutdown
Cleanly shuts down an array.
Shutting down an array has no effect on member, volume, or group configuration
information or volume data stored on the member. Any volumes with data on the array
will be set offline until the array is completely restarted. Once the array is restarted, it
rejoins the group automatically.
Note: The shutdown command does not power off the array. To power off the array, you
must turn off both power supplies after the array shuts down.
Do not repeatedly shut down and restart an array.
To access the CLI to run the shutdown command, see Running Array Management
Commands on page 3-2.
When you are connected to the array (either through a serial connection to the active
control module or a network connection to an IP address for a network interface), press the
<Enter> key and log in to a group administration account that has read-write permission
(for example, the grpadmin account). At the CLI prompt, enter the shutdown command.
After you agree to shut down the array, network connections are closed, and the array is
shut down.
If you are using a serial connection, the following message is shown on the console when
it is safe to turn off power to both power supplies:
Press any key to reboot.
However, if you are using a network connection to run the shutdown command, the
session will be disconnected before the array is shut down. Therefore, make sure that the
ACT LED on each control module is off (not lit) before turning off power to both power
supplies.
To fully restart the array, turn on power to both power supplies. When the array restart
completes, volumes will be set online.
Note: If you physically connect a serial cable to the secondary control module and run the
shutdown command, only the secondary control module will be shut down. To
shut down both control modules, connect the serial cable to the active control
module (ACT LED will be green) and run the shutdown command.
shutdown
3-21
CLI Reference
If you have a serial connection to an array that is shut down, but still has power,
pressing any key will restart only the active control module. To make sure that
both control modules restart, turn power off and then on to both power supplies on
each array.
Format
shutdown
Example
When you run the shutdown command and agree to the operation, the network
connection closes:
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
psg22> shutdown
Do you really want to shutdown the system? (yes/n) [n] y
Connection closed by foreign host.$
3-22
shutdown
CLI Reference
update
Updates array firmware.A PS Series storage array includes single or dual control modules,
each with a compact flash card running the PS Series firmware. You should always run the
latest storage array firmware to take advantage of new product features, enhancements,
and fixes.
Note: Read the PS Series Release Notes before starting the update.
Format
update
When updating array firmware, keep in mind the following important issues:
Update path. Usually, you can update an array directly to the latest firmware version.
However, in some cases, you may need to update to an interim version before
updating to the latest version. See the PS Series Release Notes for information about
supported firmware update paths.
Mixed firmware in a group. Dell recommends that all PS Series group members run
the same version of the storage array firmware, to make features and bug fixes
common to all versions available. If you are adding a new array to a group, update the
group to the latest firmware before adding the new member.
update
3-23
CLI Reference
completes. When scheduling a firmware update, allow enough time to update and
restart the entire group of arrays.
During an array restart, volumes with data on the array will be momentarily
unavailable until the restart completes. While the volumes are unavailable, some
iSCSI initiators may return errors to the operating system or applications.
The PS Series Release Notes provides examples of operating system and iSCSI
initiator configurations that may be able to tolerate an array restart without disruption.
In some cases, you may need to make modifications to the operating system. You
should also make sure that the applications themselves can tolerate the restart. Other
configurations may be able to tolerate an array restart without disruption. In all cases,
you should first test them in a non-production environment.
If you do not have one of the identified configurations or if you are unsure of your
applications ability to tolerate the restart, plan for downtime when updating firmware.
This can involve shutting down the hosts accessing the group before starting the
update procedure. After the update completes, you can restart the hosts. Planning for
application downtime may be the best way to protect against disruption.
The following steps take you through the PS Series firmware update procedure:
1. Gather network information and locate a host. The update procedure requires the
following items for each array you are updating:
The IP address for a network interface on the array (for example, the IP address
for eth0). Do not use the group IP address.
Host that has the ftp or scp utility available and network access to each array
being updated. You can use the ping command to test network connectivity from
an arrays IP address to a host.
2. Obtain the firmware update kit and documentation. Follow these steps to obtain
the update kit and documentation:
a. On the host that has the FTP or SCP utility available, use a web browser to access
the EqualLogic website (www.equallogic.com). Click Support and log in to a
support account. Create an account if you do not have one.
3-24
update
CLI Reference
b. In the Downloads area, select the archived update kit that is right for your
operating system. The kit is approximately 15 MB in size.
3. Identify host implications. Shut down if necessary. See the PS Series Release Notes
for information about specific configurations that should not be affected by the
momentary disruption in volume availability resulting from an array restart. If your
configuration does not meet the requirements in the Release Notes, you can shut down
the hosts accessing the group volumes. After the update, you can restart the hosts.
4. Cleanly restart the array, if currently running firmware prior to V2.2.3. If the
array is currently running a PS Series firmware version prior to 2.2.3, you must use the
restart command to restart the array before copying the update kit to the array. To
connect to the array, do one of the following:
Use the null modem cable (or cables) shipped with the array to connect Serial Port
0 on the active control module (LED labeled ACT is green) to a console or a
computer running a terminal emulator. See Running Array Management
Commands on page 3-2.
Once connected, press the <Enter> key and log in to an administration account that
has read-write permission (for example, the grpadmin account). At the CLI prompt,
enter the restart command. When the array shuts down, the network connection
closes.
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
> restart
5. Copy the kit to the array. Use FTP or SCP to copy the update kit from the host in
Step 2 to the array being updated. Specify the array IP address obtained in Step 1 as
input to the open command. When prompted for an account and password, specify the
grpadmin account and password. If using ftp, make sure the transfer occurs in
binary mode.
update
3-25
CLI Reference
Note that the update kit name must not be changed at any step in the copy process. If
the name is changed, the update will fail. Because some versions of ftp change the
file names to uppercase, specify the update kit name twice with the put command, as
shown in the example below. Or you can use scp, which does not change file names
and does not require you to log in to the array.
The following example uses ftp to copy a firmware update kit named
kit_12345678.tgz from a host to an array with the IP address 182.168.1.53.
$ ftp
ftp> open 182.168.1.53
Connected to 182.168.1.53.
220 182.168.1.53 FTP server ready.
Name: grpadmin
331 Password required for grpadmin.
Password:
230 User grpadmin logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> binary
200 Type set to I
ftp> put kit_12345678.tgz kit_12345678.tgz
local: kit_1234567.tgz remote: kit_1234567.tgz
229 Entering Extended Passive Mode (|||65534|)
150 Opening BINARY mode data connection for 'kit_12345678.tgz'.
100%|***********************| 13191 KB
81.26 KB/s 00:00 ETA
226 Transfer complete.
13508472 bytes sent in 02:42 (81.06 KB/s)
ftp> close
Data traffic for this session was 13508472 bytes in 1 file.
Total traffic for this session was 13509009 bytes in 1
transfer. 221 Thank you for using the FTP service on
192.168.1.53.
ftp> bye
The following example shows how to use scp to copy a firmware update kit named
kit_12345678.tgz from a host to an array with the IP address 182.168.1.53:
$ scp kit_12345678.tgz grpadmin@182.168.1.53:
grpadmin@182.168.1.53's password:******
kit_12345678.tgz 100%
12MB 198.0KB/s
01:00
6. Update the array firmware. Use a serial connection or use telnet or SSH to connect
to an IP address for a network interface on the array (for example, eth0). Do not
connect to the group IP address.
3-26
update
CLI Reference
Once connected to an array, press the <Enter> key and log in to an administration
account that has read-write permission (for example, the grpadmin account). At the
CLI prompt, enter the update command. On a dual control module array, both
control modules will be updated.
7. Cleanly restart the array. When the update completes, at the CLI prompt, enter the
restart command. Restart the array as soon as possible to apply the new firmware.
8. Verify the firmware. In the GUI, you can view control module information by
expanding the members list in the leftmost panel, selecting a member name, and then
clicking the Controllers tab. You can also use the following CLI command,
specifying the member name:
member select member_name show controllers
On a dual control module array, the firmware on both control modules must be the
same. If not, or if only one control module is shown but two are installed, contact your
support provider.
9. Repeat the procedure on each group member. If you are updating firmware on a
multi-member group, repeat Steps 4 to 8 on the remaining members. Between
updating members, wait for the SAN to stabilize before continuing with the update.
10. Restart hosts. If you chose to shut down the hosts accessing the group volumes, you
can restart them.
update
3-27
CLI Reference
Example
The following example uses a serial connection to an array to which the firmware update
kit has been copied, updates the firmware, and then restarts the array.
PS Series Storage Arrays
Unauthorized Access Prohibited
login: grpadmin
Password:
Welcome to Group Manager
Copyright 2001-2009 Dell, Inc.
> update
This command will update the firmware on the array's flash card memory
using the kit that is already loaded onto the array.
If you choose to proceed, you will be shown the current firmware version
and the version to which you will update. You will then be given the
choice to proceed again.
The firmware update will not take effect until the array is restarted.
Do you want to proceed (y/n) [y]: y
Active and secondary control modules detected.
.
.
.
Update completed successfully.
The update will take effect after the next member restart. If you want to
restart now, invoke the "restart" command.
> restart
3-28
update
4 Global Commands
The global commands control the behavior of the Group Manager command line interface
(CLI). Descriptions of these commands are listed in alphabetical order in Table 4-1.
Each command includes the following information:
Brief description
Command format
Examples
Table 4-1: Global Commands
Command
Description
alias
clear
cli-settings Shows and sets CLI settings. See cli-settings on page 4-4.
exec
exit
When in subcommand mode, moves the user up a level. See exit on page 4-9.
help
history
logout
stty
Shows and sets the terminal settings. See stty on page 4-14.
tree
whoami
Shows the account name of the currently logged-in user. See whoami on
page 4-17.
4-1
CLI Reference
Global Commands
alias
Performs text substitution.
Format
alias alias_name original_text
Variables
alias_name
original_text
Example
4-2
alias
CLI Reference
Global Commands
clear
Clears the screen.
Format
clear
clear
4-3
CLI Reference
Global Commands
cli-settings
Specifies certain CLI settings.
Format
cli-settings show|parameter
Parameters
confirmation on|off
displayinMB on|off
events on|off
formatoutput on|off
idlelogout on|off
paging on|off
4-4
cli-settings
CLI Reference
Global Commands
Examples
The following commands show the effect of turning displayinMB off and on.
> cli-settings displayinMB off
> volume show
Name
----------test-access
dbvol
Connections
----------1
0
Size
SnapShots
------------1024MB
0
10240MB 0
Status
-------online
online
Permission
---------read-write
read-write
Connections
----------1
0
The following commands show the effect of turning formatoutput off and on.
> cli-settings formatoutput off
> grpparams show
________________________ Group Information _______________________
Name: kanga
Group-Ipaddress: 10.127.29.110
Def-Snap-Reserve: 100%
Def-Snap-Warn: 10%
Def-Snap-Depletion: delete-oldest
Def-Thin-Growth-Warn: 60%
Def-Thin-Growth-Max: 100%
DateAndTime: Tue Apr 15 14:32:30 2009
TimeZone: America/New_York
Description:
Def-Iscsi-Prefix: iqn.2001-05.com.equallogic
Def-Iscsi-Alias: yes
Info-Messages: enabled
Webaccess: enabled
Webaccess-noencrypt: enabled
Cliaccess-SSH: enabled
Cliaccess-Telnet: enabled
Email-Notify: disabled
Syslog-Notify: disabled
iSNS-Server-List:
Email-List:
NtpServers:
Smtp-Server-List:
Syslog-Server-List:
Target-Auth-UserName: PJJRh8PRZrBBx8pH
Target-Auth-Password: BJZpJHHXBzR2PJRH
cli-settings
4-5
CLI Reference
Global Commands
Email-From:
Location: default
Conn-Balancing: enabled
Discovery-Use-Chap: disabled
Email-Contact:
Perf-balancing: enabled
Disallow-Downgrades: yes
Management-Ipaddress:
__________________________________________________________________
_______________________ Radius Information _______________________
radius-auth-list:
login-radius-auth: disabled
radius-auth-retries: 1
radius-auth-timeout: 2secs
login-radius-acct: disabled
radius-acct-retries: 1
radius-acct-timeout: 2secs
iscsi-radius-auth: disabled
iscsi-local-auth: enabled
radius-acct-list:
login-radius-attr: enabled
__________________________________________________________________
________________________ Snmp Information ________________________
read-only-comms: public
read-write-comms:
trap-community: SNMP-trap
snmp-managers:
__________________________________________________________________
> cli-settings formatoutput on
> grpparams show
________________________ Group Information _______________________
Name: kanga
Group-Ipaddress: 10.127.29.110
Def-Snap-Reserve: 100%
Def-Snap-Warn: 10%
Def-Snap-Depletion: delete-oldest Def-Thin-Growth-Warn: 60%
Def-Thin-Growth-Max: 100%
DateAndTime: Tue Apr 15 14:34:39 2009
TimeZone: America/New_York
Description:
Def-Iscsi-Prefix:
Def-Iscsi-Alias: yes
iqn.2001-05.com.equallogic
Info-Messages: enabled
Webaccess: enabled
Webaccess-noencrypt: enabled
Cliaccess-SSH: enabled
Cliaccess-Telnet: enabled
Email-Notify: disabled
Syslog-Notify: disabled
iSNS-Server-List:
Email-List:
NtpServers:
Smtp-Server-List:
Syslog-Server-List:
Target-Auth-UserName:
Target-Auth-Password:
PJJRh8PRZrBBx8pH
BJZpJHHXBzR2PJRH
Email-From:
Location: default
Conn-Balancing: enabled
Discovery-Use-Chap: disabled
Email-Contact:
Perf-balancing: enabled
Disallow-Downgrades: yes
Management-Ipaddress:
__________________________________________________________________
________________________ Radius Information ______________________
radius-auth-list:
login-radius-auth: disabled
4-6
cli-settings
CLI Reference
Global Commands
radius-auth-retries: 1
radius-auth-timeout: 2secs
login-radius-acct: disabled
radius-acct-retries: 1
radius-acct-timeout: 2secs
iscsi-radius-auth: disabled
iscsi-local-auth: enabled
radius-acct-list:
login-radius-attr: enabled
__________________________________________________________________
________________________ Snmp Information ________________________
read-only-comms: public
read-write-comms:
trap-community: SNMP-trap
snmp-managers:
__________________________________________________________________
cli-settings
4-7
CLI Reference
Global Commands
exec
Does the commands contained in a CLI script file (file containing other CLI commands).
A script can change terminal settings, perform basic group administration tasks, and
collect system information.
Format
exec parameter filename
Parameter
-echo
-ignore
-history
Variable
filename
4-8
exec
CLI Reference
Global Commands
exit
Moves the user up one or all command levels from subcommand mode.
Format
exit [all]
exit
4-9
CLI Reference
Global Commands
help
Shows information about CLI commands. You can obtain help on any of the group
administration, array management, or global commands. You can also get information
about the available editing keystrokes.
Format
help command [commands|edit]
Variable
Name of command for which to show help.
command
Subcommands
commands
edit
Example
4-10
help
CLI Reference
Global Commands
help
4-11
CLI Reference
Global Commands
history
Shows the CLI command history.
Format
history
4-12
history
CLI Reference
Global Commands
logout
Logs out an administration account user from the group.
Format
logout
logout
4-13
CLI Reference
Global Commands
stty
Shows the terminal settings.
Format
stty parameter ...
Parameters
rows n
Sets the screen height. The n variable indicates the number of rows
and must be an integer from 10 to 254 inclusive.
columns n
Sets the screen width. The n variable indicates the number of columns
and must be an integer from 20 to 255 inclusive.
hardwrap on|off
status
Example
4-14
telnet
80
25
Off
stty
CLI Reference
Global Commands
tree
Shows the CLI command syntax in a tree structure, optionally showing the complete
command syntax.
Format
tree [-syntax] [command]
Variable
command
Examples
The following example shows part of the output from a tree -syntax command:
> tree -syntax
|+---account
|
|
|
+---create [description <String>] [contact <String>]
[email <String>] [phone <String>] [mobile <String>] <name>
[<read-write|read-only>] [<enable|disable>]
|
|
|
+---delete <name>
|
|
|
+---select <name>
|
|
|
|
|
+---contact <contact>
|
|
|
|
|
+---description <description>
.
.
.
The following example shows only the basic syntax of the chapuser command:
> tree chapuser
chapuser
|
+---create
|
+---delete
|
+---rename
|
+---select
|
|
tree
4-15
CLI Reference
Global Commands
|
+---disable
|
|
|
+---enable
|
|
|
+---passwd
|
|
|
+---show
|
+---show
4-16
tree
CLI Reference
Global Commands
whoami
Shows the account name of the logged in user.
Format
whoami
Example
whoami
4-17
A-1
CLI Reference
A-2
CLI Reference
This product includes software developed by the University of California, Berkeley and its
contributors. This product includes software developed by the University of California,
Lawrence Berkeley Laboratory.
Copyright 1985-1995 The Regents of the University of California.
Copyright 1997-2000 Niels Provos.
This code is derived from software contributed to Berkeley by Ralph Campbell.
This code is derived from software contributed to Berkeley by Rick Macklem.
Copyright 1989 Digital Equipment Corporation.
This product includes software developed by Manuel Bouyer.
Copyright 1999 Manuel Bouyer.
This product includes software developed by Adam Glass.
Copyright 1994 Adam Glass.
This code is derived from software contributed to Berkeley by Paul Vixie.
This code is derived from software contributed to Berkeley by Chris Torek.
This code is derived from software contributed to Berkeley by Mike Hibler.
This code is derived from software contributed to Berkeley by Paul Borman at Krystal
Technologies.
This code is derived from software contributed to Berkeley by Peter McIlroy.
This code is derived from software contributed to Berkeley by Peter McIlroy and by Dan
Bernstein at New York University.
This code is derived from software contributed to Berkeley by Stephen Deering of
Stanford University.
This code is derived from software contributed to Berkeley by Jeffrey Mogul.
Copyright 1996 The Board of Trustees of The Leland Stanford Junior University.
A-3
CLI Reference
This product includes software developed by the Computer Systems Laboratory at the
University of Utah. Copyright 1990,1994 The University of Utah and the Computer
Systems Laboratory (CSL). All rights reserved.
This code is derived from software contributed to Berkeley by the Systems Programming
Group of the University of Utah Computer Science Department.
Copyright (c) 2000 Soren S. Jorvang.
Copyright (c) 1993 John Brezak. All rights reserved.
Copyright 1995 - 2000 WIDE Project. All rights reserved.
UNIX System Laboratories, Inc.
All or some portions of this file are derived from material licensed to the University of
California by American Telephone and Telegraph Co. or Unix System Laboratories, Inc.
and are reproduced herein with the permission of UNIX System Laboratories, Inc.
Copyright 1999 Shuichiro URATA.
This product includes software developed by Matthias Pfaller.
Copyright 1996 Matthias Pfaller.
Copyright 1993 Jan-Simon Pendry.
This product includes software developed by Gordon W. Ross.
Copyright 1995 Gordon W. Ross.
This product includes software developed by Philip A. Nelson.
Copyright 1993 Philip A. Nelson.
Copyright 1999 Ross Harvey.
This product includes software developed by Christos Zoulas.
Copyright 1996 Christos Zoulas.
Copyright 1997 Zubin D. Dittia.
A-4
CLI Reference
A-5
CLI Reference
A-6
CLI Reference
A-7
CLI Reference
A-8
Index
A
array
setting up 3-16
accounts
creating 2-2
deleting 2-4
disabling 2-5
displaying 2-7, 2-159
displaying logged in accounts 2-166
enabling 2-5
managing 2-2
modifying 2-5
passwords for 2-6
RADIUS accounting 2-58
RADIUS accounting server retries 2-65
RADIUS accounting servers 2-64
RADIUS authentication 2-59
RADIUS authentication parameter 2-59
authentication
between initiators and targets 2-12, 2-67
between partners 2-99
initiator 2-12
mutual 2-12, 2-99
target 2-74
adding a member
IPv4 group 3-16
IPv6 group 3-16
administration
accounts for 2-2
B
backing up data (replication) 2-98
binding volumes to a member 2-131,
2-175, 2-180
booting arrays 3-22
C
cancelling member operations 2-81
capacity
displaying member status 2-94
using all 2-177
CHAP
Index-1
CLI Reference
Index-2
Index
CLI Reference
Index
delegated space
displaying 2-145
specifying for partner 2-99
diag 3-5
disaster recovery
cloning replicas 2-130
promoting replica sets 2-133
restoring volumes 2-222
disks
clearing foreign labels 2-83
clearing label 2-83
displaying status 2-84, 2-91, 2-92
displaying status
disks 2-84, 2-91, 2-92
enclosure 2-92
Ethernet ports 2-93
volumes 2-94
control modules
updating firmware 3-23
creating a group
with IPv4 3-16
with IPv6 3-16
D
date, setting for group 2-43
default gateway (member) 2-81
default management gateway 2-44
e-mail notification
enabling and disabling 2-52
specifying addresses 2-51
specifying return address 2-51
specifying SMTP servers 2-71
enclosure
displaying status 2-92
Ethernet ports
displaying status 2-93
events
controlling display of 2-165
Index-3
CLI Reference
displaying 2-165
displaying notification priorities 2-10
e-mail notification 2-51, 2-52
modifying notification priorities 2-9
notification methods 2-160
setting notification priorities 2-9
severity levels 2-165
syslog notification 2-73
turning off console messages 4-4
turning off live informational messages
2-55
exec 4-8
executing commands 4-8
exit 4-9
exiting subcommand mode 4-9
F
failback
description 2-33
failback replica sets
cancelling operation 2-115
changing pool 2-117
changing to inbound replica set 2-116
displaying 2-118
managing 2-108
promoting 2-117
selecting 2-109
failback retry 2-36
failback show 2-35
failback start 2-34
failback stop 2-34
failure (catastrophic) member-level 2-79
firmware, preventing downgrade 2-49
Index-4
Index
G
group
access to GUI 2-77
accounts for managing 2-2
CLI access 2-41
CLI management 1-1
collecting diagnostic information 3-5
date 2-43
displaying object information 2-158
displaying parameters for 2-71
IP address, changing 2-53, 2-54
location 2-58
logging out 4-13
management commands 2-1
members 2-162
name, modifying 2-62
parameters 2-37, 2-161
password for adding members 2-63
pools 2-149
replication 2-98
replication partners 2-164
saving configuration 2-154
snapshot collections 2-170
time 2-75
timezone 2-75
volumes 2-174, 2-225
group configuration
displaying 2-158
group IP address
changing 2-53
Group Manager
using the CLI 1-1
group parameters
displaying 2-37, 2-161
CLI Reference
setting 2-37
Index
GUI
secure web access, enabling 2-78
Index-5
CLI Reference
Index
lost blocks
clearing on a member 3-3
handling on a volume 2-181, 2-219
history 4-12
hosts
CHAP authentication 2-56
CHAP authentication through RADIUS
2-56
connections to volumes 2-210
limiting access to snapshots 2-185
limiting access to volumes 2-185
testing connectivity 3-10
using Perl scripts from 1-3
I
identifying problems 3-5
iSCSI target alias
setting for volume 2-175, 2-181
setting group default 2-43
iSNS server discovery
snapshots 2-219
volumes 2-181
M
management network
configuring default gateway 2-44
configuring group management address
2-60
configuring interfaces 2-85
manual replication
confirming completion 2-123
enabling 2-195
member delete 2-79
member rename 2-80
member select 2-81
member select disk select clear-label 2-83
member select disk select show 2-84
member select disk show 2-84
member select eth select 2-85
L
label, clearing on a disk 2-83
language, setting for group 2-44
local reserve
borrowing group space 2-199, 2-202
calculating 2-199, 2-202
Index-6
CLI Reference
Index
2-94
unbinding volumes 2-183
updating firmware 3-23
MRTG (Multi-Router Traffic Grapher)
2-96
mrtg-config 2-96
multi-host access
enabling and disabling 2-192, 2-221
on snapshots 2-221
on volumes 2-192
snapshots 2-218
volumes 2-181
mutual authentication
between replication partners 2-99
N
netmask, specifying for network interface
2-86
network connection load balancing 2-42
network interfaces
configuring 2-85
displaying status 2-88
modifying 2-85
netmask 2-85, 2-86
testing connectivity 3-10
Network Time Protocol (NTP), specifying
servers 2-62
notification
displaying event priorities 2-10
enabling e-mail 2-51
enabling syslog 2-73
setting event priorities 2-9
notifications, customer service 2-50
NTP, specifying servers 2-62
Index-7
CLI Reference
Index
Index-8
CLI Reference
Index
2-133
R
RADIUS
account authentication login parameter
2-59
accounting server list 2-64
accounting server retries 2-65
accounting server secrets 2-66
accounting server timeout 2-67
authentication server list 2-67
authentication server retries 2-69
authentication server secrets 2-69
authentication server timeout 2-70
enabling accounting for RADIUS
authenticated accounts 2-58
enabling authentication for accounts
2-59
using local CHAP accounts before
external 2-56
RADIUS authentication
enabling for host iSCSI access to
volumes 2-56
RAID policy 2-83
recovering data
failback 2-33
promoting to a recovery volume 2-133
replicate to the primary group 2-193
recovery volume 2-134
recovery volumes
creating new volume 2-191
demoting 2-197
replica collections
creating 2-22
schedules 2-25
creating 2-25
Index-9
CLI Reference
deleting 2-27
displaying 2-30
modifying 2-28
renaming 2-28
replica reserve
calculating 2-199, 2-202
calculating delegated space 2-99
replica sets
deleting inbound 2-122
deleting outbound 2-141
displaying inbound 2-136, 2-145
displaying outbound 2-143, 2-144,
2-145
promoting 2-133
replicas
cloning 2-130
creating 2-196
deleting inbound 2-132
deleting outbound 2-142
displaying inbound 2-136, 2-145
displaying outbound 2-143, 2-145
schedules 2-203
creating 2-204
deleting 2-206
displaying 2-209
modifying 2-207
renaming 2-207
status 2-146, 2-203
replication
cancelling 2-195
configuring 2-98
disabling on a volume 2-198
displaying partners for 2-203
enabling on a volume 2-194, 2-196,
2-198
inbound status 2-164
introduction 2-98
Index-10
Index
CLI Reference
Index
reset 3-12
restart 3-14
shutdown 3-21
save-config 2-154
serial connection
setting up 1-1
snapshots
cloning 2-219
cloning volumes from 2-219
creating 2-215, 2-216
current status 2-223
deleting 2-216
displaying 2-223, 2-225
host access to 2-185
Index-11
CLI Reference
Index
T
target names (volumes) 2-175
telnet access, enabling 2-42
terminal settings 4-14
text substitution 4-2
thin 2-38
thin-grow 2-38
time, setting for group 2-75
timezone, setting for group 2-75
trap destinations (SNMP), setting 2-72
tree 4-15
Index-12
U
update 3-23
updating a member 3-23
V
versions
displaying, for components 2-93
volume collections
adding volumes 2-20
creating 2-17
creating a replica collection 2-22
creating snapshot collections 2-170
deleting 2-18
deleting volumes 2-20
CLI Reference
Index
Index-13
CLI Reference
Index-14
Index
CLI Reference
Index
managing 2-215
modifying 2-218
renaming 2-217
status 2-167, 2-225
status of replication 2-203
unbinding from a member 2-183
W
whoami 4-17
wildcard character in access control
records 2-185
Index-15