HP 3PAR SSMC 2.1

© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

HP 3PAR StoreServ Management ConsoleIvan IannacconeHP 3PAR Product Management

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Mastering SSMC

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.3

HP 3PAR StoreServ Management ConsoleDefinitive Advantages.. Customer Reactions• Up to 16 arrays managed from one screen

• Instant display of array(s) status -dashboard

• Compact Screen – same as OneView

• Single Login

• Login Intelligent

• Search

• Mapping

• Capacity Planning

• Reporting

• Easy Menu to understand


Browse 3PAR

• Think about using SSMC as you where browsing the Web

• You have a top Menu when you can change context of the objects your want to display

• Or just SEARCH the object you are looking for.

• The various screens over filter capabilities, on the top of the screen or as a pull out menu on the top left hand side.


Search inside 3PAR

• Search can be in the context of a Menu or Global• Allows users to find objects in seconds • Intelligence search remembers previous queries

User is notified the array is experiencing some delays on a host identified by the name “ATC”

the user has a server attached to the array identified as only “WIN”


Activities on your 3PAR

• All Activities around changes to object or changes to status are recorded as an activity entry

• This is like a real-time blog where all user and system interactions can be tracked

• All objects in SSMC have also their own private Activity - View


Physical map view

Map 3PAR

Virtual map view

Visualize relationships between devices


Storage Systems


Threshold Alerts


Space Allocation


Capacity Efficiency


System Reporter

• Performance Templates• Bird-View with drill-down from daily to hi-res• One-click at-time reports


Looking at Performance data with SSMC


System ReporterData Sampling

Collected data samples are collected and charted asHi-res… data displayed once every 5 minutesHourly... data output once ever hourDaily… data charted once a day

Charted data samples output as a result the delta of countersv = counter collection t = time collectionon-node uses averages for most of the stats, so the hires data is (v2-v1)/(t2-t1)hourly is calculated from point-in-time values (v12-v1)/(t12-t1)daily is calculated from point-in-time values (v288-v1)/(t288-t1)

Samples are cumulative values If for example midnight sample yesterday sampled total IO at 77000 for a host, then midnight sample today sampled total IO at 198000. The daily at-time report will display (198000-77000)/(86400 seconds per day) = 1.4 io/s. This number is accurately capturing all of the IOs that happened during the day, regardless of when there might have been peaks.


General GuidelinesPerformance is a subjective measure. What is good for one application/customer may be bad for another.

It is important to notice change:

Have the IOPs and Bandwidth increased over time?Has the read to write mix changed?Has the response time changed?Has the cache hit ratio changed?

To get an overall view of how the array is processing I/O. I.e. is the workload cache centric, or more backend based, what

performance do volumes see and how busy are the disk drives we want to look at five specific areas:

1. System Balance

2. The volume IOP levels, read to write ratio and service time (Exported Volumes Performance)

3. The cache performance and hit rates (Controller Node Cache)

4. The disk drive IOP levels and service times (Physical Drives Performance)

5. I/O density reports


Real-Time CLI Historical CLI SSMC

Front-End Performance

Host Ports statport -host histport -host srstatport srhistport Host Ports

VLUNs statvlun histvlun srstatvlun srhistvlun Exported Volumes

FCoE Protocol statfcoe NA Host Ports (fcoe)

iSCSI Protocol statiscsi NA Host Ports (iSCSI)

iSCSI Session statiscsisession NA NA

FC RC Links statport -rcfc histport -rcfc srstatrcopy Remote Copy

Controllers Performance

Cache statcmp srstatcmp NA Controller Node Cache

CPUs statcpu srstatcpu NA Controller Node CPU

LDs statld histld srstatld srhistld NA

VVs statvv histvv NA NA

RC Groups statrcopy srstatrcvv Remote Copy

RC VVs statrcvv histrcvv srstatrcvv Remote Copy

Back-End Performance

Disk Ports statport -disk histport -disk srstatport srhistport Enclosure Ports

Physical Disks statpd histpd srstatpd srhistpd Physical Drives


Performance - Templates

Exported Volumes

Host Ports

Enclosure Ports

Controller Node Cache

Controller Node CPU

Physical Drives

Fron

t-En

dBa

ck-E

nd


Balanced System – Host Ports

Before provisioning a new how the System Port view with the right filter can be used to narrow down how many host are alreadyzoned to a give port and the port bandwidth utilization


Balanced System – Capacity

The Drive Enclosure and Physical Drives details under Systems can provide insight around back-end space allocation and performance balance.


Host Port Balance 3PAR is designed to maximize all system resources, so a well balanced system is paramount :

• Host bandwidth balanced between ports and nodes

• Physical drive even space allocation/distribution


Space Allocation Balance


Checking Performance

• The Host Port and Exported Volumes svctimes are the first reports to check when there is a performance incident.

• After confirmed there is indeed a problem all the other reports are need to determine the bottleneck.


Node Cache Performance • The Node Cache information is should

always be the first stop after assessing a spike in svtcime when looking at front-end data.

• Hit Percentage will provide guidance if the was a significant change in I/O pattern

• Delay Ack will confirm if there was any cache page starvation due to back-end resource saturation.


Back-end Resources • Once we know more information around what is happening at the caching layer we can go and check if there is a challenge with back-end resources.

• The Cache report shows delayed ack on the FC tier.


Physical Drives – At-Time

• Once a report against the right tier has been created the user can click where there is a spike in the chart curve and get more information

• In this example we can see that the drives in the FC tier where doing around 400 write IOPS


Who is the culprit?

• The Exporter Volumes chart can be used to check with hosts are driving the majority of the bandwidth as the front-end svctimes increased


Busiest Volumes • At-Time Reports of daily data can be

useful to keep an eye on how much bandwith different hosts are consuming

• You can filter the rule by Vvset/Host/Port


Looking at I/O Density• Even if AO is not used Density Reports can be used to understand the

I/O access and behavior to given volumes

• SSMC provides an ability to have a read/write breakdown of I/O density information on a per VV basis


Using histogram dataAn histogram is a graphical representation of the distribution of numerical data. 3PAR records IO time and IO size of every single IO processed for this very reason histogram data can be very powerful to show your customer how well a system is behaving

or what hosts/volumes have poor service times. The best way of reading the data is looking at percentages.

Number of I/Os

Freq

uenc

y

The graph show the amount of I/O request of a given page size that the

array has served


Histogram data for Port Balance

• This will provide the average over a 24h period with a breakdown of the percentage of read/write requests between 0.125ms and 16ms.

• Request lower than 0.125 are counted in the 0.125 values, request higher than 16ms are counted against the 16ms values


Histogram data for Port Svctime Balance


Exported Volumes Histogram for Flash POC

• This report is a good day to show how low latency is on a 3PAR array.

• It will split all the access of reads and writes over time of svctimes between 0.062 milliseconds and 0.500 milliseconds.


Exported Volumes histogram

• A click in any given point in time will show the overall latency experienced by the various applications/hosts.

Performance Isolation Examples

Exported Volumes Host Ports Physical Drives Action

Service Times Low Low Low None required

Service Times High Low Low Verify host system resources and host hba settings

Service Times High Low High Verify Controller Cache stats

Service Times High High LowVerify connectivity between host and array (possible

port switch problem /ISL congestion)


Capacity Management with SSMC


Chunklets/LDs/VVs/Virtual Size

Understanding Storage Allocation

Chunklet LD VV VLUN

• Allocated• Reserved

(System Usable) • Used

• Virtual Size(Host Usable)

Virtual Size: this is the virtual size of the VV (i.e. the size that the host would see), we also call this host usable.It does not necessarily have anything to do with the physical space that the VV uses.

VVs are implemented using 3 “Spaces”: User, Snap, Admin.

The LD regions mapped to these spaces are what adds up to Reserved space, Reserved space is logical. The Raw Reserved space includes the RAID overhead used by the reserved space. This space is called Reserved because it is reserved for that VV and its snapshots. Depending on the VV type, the spaces may grow on demand. More space may be mapped in (i.e. reserved) from LD space in the CPG associated with the VV. Note that all of an LD’s space may not be Reserved, some of it may be free (it could get mapped to a space later). Not all of the Reserved space is used. As the VV’s pages are written, pages in the User/Snap/Admin space(s) get actually used and this is counted as Used space.

Thus Used space is a subset of the Reserved space.

Allocated space is all of the chunklets that are used, either in LDs or for spares.

Capacity Management in SSMC

Given how space is allocated and reserved the best metric to monitor space allocation is looking at the Physical Drives free space.

For this we can use the System Capacity and Physical Drive Reports.

The VV – Capacity report can be used to track virtual volumes space allocation efficiency.

The CPG – Capacity is designed to show how the space consumed in the CPG has grown or shrunk over time.


System Capacity• This report is a good way to check the system or tier overall historical allocation and space distribution.

• When multiple tiers are present it makes sense to create a System Report for any given tier.

In SSMC 2.2 the free and allocated order will be inverted


Physical Drives Capacity• This provides in depth information about the Chunklet utilization from the various drives in a system

• Most customers will be happy with the System Capacity report, this just provides more insight around what kind of Chunklet type is allocating space


VV – Capacity • The VV – Capacity Space efficiency is a good way to monitor how much space volumes are consuming overtime

• Total Raw Reserved is how much raw capacity is actually consumed and is probably the most meaning full indicator as it shows how much physical capacity the VVs are consuming.

CPGs and Space Management

On a 3PAR system space is allocated on-demand from a CPG.

The amount of usable space that can be allocated can is a factor of the CPG characteristics and the available free physical space at any given point-in time.

• A CPG will grow based on it’s growth settings, growth will trigger creation or expansion of Logical Disk (LD) and the space consumed by the LDs will account as Allocated to the CPG.

• As new 16KB pages of writes are allocated to the LDs these will start consuming space and account as Used space.

• The Free space shows how many more pages can be allocated before the next CPG growth.

• The maximum amount of space a CPG can allocate is estimated and exposed to the user.


CPG – Space (SSMC 2.1)

• Once selected the CPG of interested the most significant options to pick are :

• Remaining Space (misleading label) that is the CPG Allocation space over time.

• Growth Space (will be relabeled to CPG Growth) that is the CPG allocation vs it’s possible growth space

• Capacity Efficiency, that shows historical Compaction and de-duplication ratios


CPG – Space

• The Remaining Space graph is useful to see if the CPG has grown and shrunk over time

• The Growth Space shows the estimate max usable capacity that that CPG could of used


CPG – Space

• To have an exact overview of the overall amount of usable space when multiple tiers and CPGs are present you can use the default template and then use the AT-Time report to have an overview of the estimated usable for all configured CPGs


Backup

Technology

HP 3PAR SSMC 2.1