R - MR-1CN-VPLEXOPMGT - 02 Management Interfaces PDF

This module focuses on the two methods of managing a VPLEX - CLI and GUI.
The module
covers the CLI tree, how to use wildcards and how to navigate within the different contexts.
The GUI covers how to perform the same operations from a graphical interface.
Copyright © 2012 EMC Corporation. All rights reserved. Module 2: VPLEX Management Interfaces 1
VPLEX provides two ways of management through the VPLEX Management Console. The
Management Console can be accessed through a command line interface (CLI) as well as a
graphical user interface (GUI). The CLI is accessed by connecting with SSH to the
Management Server and then entering the command vplexcli. This command causes the
CLI to telnet to port 49500.
The GUI is accessed by pointing a browser at the Management Server IP using the https
protocol. The GUI is based on Flash and requires the client to have Adobe Flash installed.
Every time the Management Console is launched, it creates a session log in the
/var/log/VPlex/cli/ directory. The log is created when launching the CLI as well as
the GUI. This can be helpful in determining which commands were run while a user was
using VPLEX.
This lesson covers how to access the VPLEX CLI and familiarize yourself with its tree
structure. Wild cards and how to use them are also covered, together with different context-
sensitive commands. The lesson covers how to access help from different locations in the
CLI.
EMC VPLEX software architecture is object-oriented, with various types of objects defined
with specific attributes for each. The fundamental philosophy of the management
infrastructure is based on the idea of viewing, and potentially modifying, attributes of an
object.
The VPLEX CLI is based on a tree structure similar to the structure of a Linux file system.
Fundamental to the VPLEX CLI is the notion of “object context”, which is determined by the
current location or pwd within the directory tree of managed objects.
Many VPLEX CLI operations can be performed from the current context. However, some
commands may require the user to cd to a different directory before running the command.
VPLEX CLI supports both standard UNIX styles of options.
Both -<letter> and --<word> are supported.
Some commands can be executed anywhere in the tree and other commands must be
executed in specific directories. Within any context typing the tab key provides the
complete list of valid commands within the current context. This is a useful mechanism to
“discover” the set of valid operations on each type of EMC VPLEX managed object.
The VPLEX CLI includes detailed online help for every command. Users can find help on any
VPLEX CLI command by entering –h directly after the command. VPLEX CLI also supports
Linux tab completion for commands. If part of a command has been entered, the user can
press the tab key to have the system discover the commands that match the letters
entered. If more than one command matches the letters entered, multiple commands are
returned as output.
Wild card symbols aid in command completion. They help in the creation of shorter and
easier to run commands. The ** wildcard is the most helpful wildcard as it allows the system
to match the next characters specified in the string recursively. Wildcard can be useful to
save time when entering commands. The wildcard symbols and there meanings are listed.
Please take a moment to read them.
The command context must map to an available context in the VPLEX directory structure.
Each component has a location or name associated with it.
More information can be displayed about an VPLEX object by entering llwithin the object’s
context. The ll command is an alias to ls –la.
If the meaning of attributed is unknown to the user, the describe command can be issued
to provide a description of all attributes of an object. Entering the describe command
here describes the attributes of a front-end port named A0-FC00.
This table lists several useful summary and status commands. Some of these are
particularly useful during troubleshooting.
Standard UNIX-style navigation is supported for traversing the directory tree within a VPLEX
CLI session. Note that pushd and popd are supported as well, as in some UNIX shells. The
tree command can be used to view a map of the entire object tree starting from the
current context as the root of the tree.
Users can create, list, and delete aliases for their favorite and frequently-run commands, as
in any standard Unix shell.
As with any Unix shell, convenient mechanisms exist to display history and recall previously-
executed commands. The up arrow allows the user to recall previously used commands.
The history command displays the current history in the session. And the Ctrl+R
command allows the user to search and execute previously used commands.
The ! and !! key sequences are similar to that of the bash shell. The !<String>
sequence executes the last command that matches the string of characters. The !!
Command executes the last command run.
The capture command is a simple mechanism to capture and replay frequently-run
sequences of commands. The capture session will save all the stdin, stdout,
stderr and session to the capture directory. The capture session will contain I/O from
all the streams.
• capture begin <session name>
 Opens a new capture session
 Records commands entered
• capture end <session name>
 Ends the capture session
• capture pause / capture resume
 Pauses and resumes the capture
 While paused commands will not be recorded until a resume
• capture replay <capture_Session>
 Replays a capture session
The schedule command can be used to run commands at an arbitrary time, or periodically
on a schedule. This can be particularly useful to offload certain types of activity. For example,
mobility jobs can be scheduled to run during off-production hours. The example shown will
run the tree command every night at 1:00 am.
schedule add <minute> <hour> <dayOfMonth> <month> <dayOfWeek>
-c <command>
• <minute> = 0-59
• <hour> = 0-23
• <dayOfMonth> = 1-31
• <month> = 1-12
• <dayOfWeek> = 0-6 (0 is Sunday)
This lesson covered how to access the VPLEX CLI and familiarize yourself with it’s tree
structure. Wild cards and how to use them were also covered, together with different
context-sensitive commands. The lesson covered how to access help from different locations
in the CLI.
This lesson covers how to use the GUI to access your VPLEX environment. The main sections
of the GUI are described and different ways of accessing help are also covered.
The VPLEX GUI provides many of the features that the VPLEX CLI provides. The GUI is very
easy to navigate and requires no knowledge of VPLEX CLI commands. Operations are
accomplished by clicking on VPLEX icons and selecting desired values.
System Status on the navigation bar shows a graphical representation of your system. It
allows you to quickly view the status of your system and some of its major components such
as directors, storage arrays, and storage views. The cluster display also shows the size of the
cluster configuration (single-engine, dual-engine, or quad-engine). Blue lights on the cluster
display represent the number of engines in the cluster. For example, a quad-engine
configuration display shows four blue lights, a dual-engine display shows two blue lights, and
so forth. System Status is the default screen when you log in to the GUI.
Notice we have a VPLEX Metro configuration with a VPLEX witness in place.
Provisioning Overview on the navigation bar shows a graphical overview of provisioning, and
provides steps to begin using the two methods of provisioning storage.
• EZ Provisioning - EZ provisioning allows you to create virtual volumes directly from
selected storage volumes. The Create Virtual Volumes wizard eliminates the individual
steps required to claim storage, create extents, devices, and then virtual volumes on
those devices. EZ provisioning uses the entire capacity of the selected storage volume to
create a device, and then creates a virtual volume on top of the device for you. Use this
method to quickly create a virtual volume that uses the entire capacity of a storage
volume. Creating a virtual volume provides more information.
• Advanced Provisioning - Advanced provisioning allows you to slice (use less than the
entire capacity) storage volumes into extents. You can then use one or more of these
extents to create devices, and then virtual volumes on these devices. This method
requires you to perform each of these steps individually, in the order listed in the Step-
by-Step instructions. Use this method when you want to slice storage volumes and
perform other advanced provisioning tasks such as creating complex devices.
VPLEX automatically discovers storage arrays that are connected to the back-end ports. All
arrays connected to each director in the cluster are listed in the Storage Arrays screen. Note
that in some cases you may need to rediscover the storage array, if for example:
• The array was not discovered correctly (you do not see the expected number of
logical units on the array when you show logical units for the array).
• You have made changes to the storage exported in a previously discovered array.
By default, arrays are sorted by name, in ascending alphabetical order. To change the order of
the default sort, click in the column header. The arrow in the default sort column indicates
the direction of the sort.
This screen also shows the following information about storage arrays. To see additional
storage array properties, click the array name (when properties links are shown) to open the
Properties dialog box.
• Name — The name of the discovered storage array.
• Logical Unit Count — The number of LUNs exported from the array.
• Auto Failover — Indicates whether VPLEX will trespass the LUNs after a controller
failure. This attribute is reported from the array, and displays only for active/passive
arrays.
• Connectivity Status — Indicates if the directors have at least one path to both of the
array’s controllers.
The Storage Volumes screen lists all storage volumes in a cluster. Use this screen to quickly
see the status of a storage volume, find a specific storage volume, or view the ITLs for a
storage volume. By default, storage volumes are sorted by use in ascending alphabetical
order, then by name. To change the order of the default sort, click the column header. The
arrow in the default sort column indicates the direction of the sort.
This screen also shows the following information about storage volumes. To see additional
storage volume properties, click the storage volume name (when properties links are shown)
to open the Properties dialog box.
• Name - The name of the storage volume. You can change this name in the properties
dialog box.
• Capacity - The size of the storage volume.
• Use - Indicates whether the storage volume is Unclaimed, Claimed, Used, Unusable,
or contains metadata (used as a meta-volume).
• Vendor - The name of the supporting array's manufacturer.
• Status - Indicates how the storage volume is functioning in the cluster.
• Largest Free Chunk - The total number of bytes in the largest range of blocks
available on the storage volume.
• Health - The overall health of the storage volume.
The Extents screen shows all extents in a cluster. Use this view to quickly view the status of
an extent, or find a specific extent. By default, extents are sorted by Use, showing all claimed
extents first. The arrow in the default sort column indicates the direction of the sort. To
change the direction of the default sort, click in the column header.
This screen also shows the following information about extents. To see additional extent
properties, click the extent name (when properties links are shown) to open the Properties
dialog box.
• Name - The name of the extent. By default, the name includes the underlying storage
volume name.
• Capacity - The size of the extent.
• Use - Indicates whether the extent is currently in use. Possible values: Claimed or
Used.
• Health - The overall health of the extent.
• Status - Indicates how the extent is functioning in the cluster.
• Storage Volume - The name of the underlying storage volume.
The Devices screen shows all local devices in a cluster. Use this view to quickly view the
status of a device, view the components of a device, or find a specific device. By default,
devices are sorted by name in ascending alphabetical order. The arrow in the default sort
column indicates the direction of the sort. To change the direction of the default sort, click in
the column header.
This screen also shows the following information about devices. To see additional device
properties, click the device name (when properties links are shown) to open the Properties
dialog box.
• Name - The name of the top-level device.
• Geometry - The underlying RAID structure of the device.
• Capacity - The size of the device.
• Virtual Volume - The name of the virtual volume built on the device.
• Health - The overall health of the device.
• Status - Indicates how the device is functioning in the cluster.
• Components of Selected Device - Shows the underlying devices and extents.
The Virtual Volumes screen shows all the virtual volumes in a cluster. Use this screen to
quickly view the status of a virtual volume, or view the supporting device for a virtual
volume. By default, virtual volumes are sorted by name in ascending alphabetical order. The
arrow in the default sort column indicates the direction of the sort. To change the direction
of the default sort, click the column header.
This screen also shows the following information about virtual volumes. To see additional
virtual volume properties, click the volume name (when properties links are shown) to open
the Properties dialog box.
• Name - The name of the virtual volume.
• Capacity - The size of the virtual volume.
• Locality - The location of the supporting device: Local, Remote, or Distributed.
• Visibility - Indicates where a virtual volume is visible: Global (both clusters) or Local
(only at this cluster).
• Health - The overall health of the virtual volume.
• Operational Status - Indicates how the virtual volume is functioning in the cluster.
• Service Status - Indicates the status of I/O to the virtual volume.
• Expandable - Indicates whether or not you can expand the selected virtual volume.
You cannot expand a virtual volume if it is built on a distributed device.
• Supporting Device - Shows the volume's supporting device.
Consistency groups group multiple virtual volumes and apply the same properties to all
virtual volumes within the group. This includes cache-mode, I/O access behaviors and I/O
behaviors in the event of a link outage/restore.
The Ports screen lists all VPLEX front-end ports used in a cluster. Use this screen to view
information about a port. By default, ports are sorted by name, in ascending order. The
arrow in the default sort column indicates the direction of the sort. To change the direction
of the default sort, click the column header.
This screen also shows the following information about ports. To see additional port
properties, click the port name (when properties links are shown) to open the properties
dialog box.
• Name - The name of the VPLEX port.
• Enabled - Indicates whether or not the port is enabled.
• Export Status - Indicates how the port is functioning.
• Port WWN - A unique network identifier for the port.
• Discovered Initiators of a Selected Port - Shows the discovered initiators for the
selected port.
The Initiators screen lists all initiators (discovered and registered) in a cluster. Use this screen
to see discovered initiators, register an initiator, or view the target ports for an initiator. By
default, initiators are sorted by name, in ascending alphabetical order. The arrow in the
default sort column indicates the direction of the sort. To change the direction of the default
sort, click the column header.
This screen also shows the following information about initiators:
• Name - The name given to a registered initiator, or the default name discovered by
VPLEX. All unregistered initiator names are prefixed with "UNREGISTERED-". You can
rename the initiator during the registration process.
• Host Type - The type of host associated with the initiator.
• Node WWN - A unique network identifier for the HBA's interface card. All ports on
the card share this node World Wide Name (WWN).
• Port WWN - A unique network identifier for the port.
• Target Ports of Selected Initiator - The VPLEX ports visible to the selected initiator.
The Storage Views screen lists all storage views in a cluster. Use this screen to find a specific
storage view, assess the health of a storage view, or show associated initiators, ports and
virtual volumes. By default, storage views are sorted by name, in ascending alphabetical
order. The arrow in the default sort column indicates the direction of the sort. To change the
direction of the default sort, click the column header.
This screen shows the following information about storage views. You can also view these
properties by clicking a storage view name (when properties links are shown) to open the
Properties dialog box.
• Name - The name of the storage view.
• Operational Status - Indicates how the storage view is functioning in the cluster.
• Active - Indicates the status of the storage view: Active or Inactive.
• Components of Selected Storage View - Shows the status and properties of initiators,
VPLEX ports, and virtual volumes in the selected storage view.
The Distributed Devices screen shows all distributed devices in the system. Use this screen to
quickly view the status of a distributed device, view the components of a distributed device,
or find a Distributed device. By default, distributed devices are sorted by name in ascending
alphabetical order. The arrow in the default sort column indicates the direction of the sort.
To change the direction of the default sort, click the column header.
This screen also shows the following information about distributed devices. To see additional
distributed device properties, click the device name (when properties links are shown) to
open the Properties dialog box.
• Name - The name of the Distributed device. You can change the name in the
properties dialog box.
• Geometry - Indicates the underlying RAID structure of the Distributed device.
• Capacity - The size of the Distributed device.
• Virtual Volume - The name of the virtual volume created on the Distributed device.
• Rule Set - The name of the Rule Set applied to the Distributed device. You can change
the Rule Set in the Distributed device Properties dialog box.
• Health - The overall health of the distributed device.
• Status - Indicates how the distributed device is functioning.
• Components of Selected Device - Shows the components of the selected device.
The data mobility feature allows you to non-disruptively move data on an extent or device to
another extent or device in the same cluster. The procedure for moving extents and devices
is the same—use either devices or extents as the source or target.
The GUI supports moving data from extents and devices to other extents and devices only
within the same cluster. To move data between extents or devices in different clusters in a
Metro-Plex, use the CLI.
You can run up to a total of 25 extent and device migrations concurrently. The system
allocates resources and queues any remaining mobility jobs as necessary. View the status
and progress of a mobility job in Mobility Central.
Mobility Central provides a central location to create, view, and manage all extent and device
mobility jobs. Use this screen to:
• Filter the jobs to view by cluster and job type (extent mobility jobs, device mobility
jobs, or all jobs)
• Launch the appropriate wizards to create extent and device mobility jobs
• View the progress and status of mobility jobs
• Manage mobility jobs (pause, resume, cancel, commit, and so forth)
• View the properties of a mobility job
• Sort jobs
The VPLEX Management Console GUI also provides online help under the Support tab. The
online support page provides online help details on the VPLEX GUI, VPLEX System Status tab,
Provisioning Storage tab, Exporting Storage, and Mobility.
The VPLEX online GUI help also links to the VPLEX product documentation, VPLEX Procedure
Generator, and Knowledgebase. It can be conveniently referenced anytime help is required.
This lesson covered how to use the GUI to access your VPLEX environment. The main
sections of the GUI were described and different ways of accessing help were also covered.
This module covered the two methods of managing a VPLEX; CLI and GUI. The module
covered the CLI tree, how to use wildcards and how to navigate within the different contexts.
The GUI covered how to perform the same operations from a graphical interface.

R - MR-1CN-VPLEXOPMGT - 02 Management Interfaces PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

R - MR-1CN-VPLEXOPMGT - 02 Management Interfaces PDF

Загружено:

Авторское право:

Доступные форматы

This module focuses on the two methods of managing a VPLEX - CLI and GUI.

Вам также может понравиться