serving information 3par hardware overview 3par virtual volume concepts 3par virtual copy 3par...

Serving Information

• 3PAR Hardware Overview• 3PAR Virtual Volume Concepts• 3PAR Virtual Copy • 3PAR Dynamic Optimization• 3PAR System Reporter and Adaptive Optimization• 3PAR Customer Support Information

• Hands-on session• 3PAR Inform Management Console (IMC) Installation• 3PAR Single Initiator -> Single Port Target zoning • Virtual Volume creation • Exporting Virtual LUN to hosts• Virtual Copy creation • Exporting Virtual Copy to hosts• Dynamic Optimization• Wrap up

3PAR Company Confidential

Agenda

Serving Information®. Simply.

Serving Information™. Simply.

3PAR

3PAR Hardware Overview

Serving Information3PAR Company Confidential

F200 F400 T400 T800

Controller Nodes 2 2 – 4 2 – 4 2 – 8

3PAR Gen3 ASIC Yes Yes Yes Yes

Fibre Channel Host Ports

Optional iSCSI Host Ports

Built-in Remote Copy Ports

0 – 12 0 – 8

2

0 – 24 0 – 16

2 – 4

0 – 64 0 – 16

2 – 4

0 – 128 0 – 32

2 – 8

GBs Control Cache

GBs Data Cache8 12

8-16 12-24

8-1624-48

8-3224-96

Disk Drives 16 - 192 16 - 384 16 – 640 16 – 1,280

Drive Types 146GB, 300GB, 400GB FC and/or

1TB NL

146GB, 300GB, 400GB FC and/or

1TB NL


750GB, 1TB NL


750GB, 1TB NL

Max Capacity 125TB 250TB 300TB 600TB

Throughput/

IOPS (from disk)1,300 (MB/s) /

46,800

2,600 (MB/s) /

93,600

3,200 (MB/s) /

156,000

6,400 (MB/s) /

312,000

SPC-1 BenchmarkResults

SPC-1 TBD 224,990

SPC-1 IOPS

3PAR InServ Storage ServersScalability


Redundant Power

Supplies (Drive Cage)

Drive MagazineRedundant

Power Supplies

Backplane

Redundant Batteries

Redundant PDUs

Drive Chassis (4U)

Controller Node

(4U)

Service Processor

Cabinet

Cabinet

• Standard 19” rack footprint• 40 EIA units• Built-in cable management• No Need to reserve for expansion

3PAR InSpire architecture: Cabinet

Serving Information5

3PAR F-Class Architecture Basics

• Same underlined architecture as the T-Class – tailored for the midrange– Cache coherent & massively load

balanced– Mixed workload & Fast RAID– Thin Built In

• Same advanced 3PAR software as in the T-Class– InForm OS – Thin Provisioning & Virtual Copy– Dynamic Optimization– Virtual Domains– Remote Copy (connect to other InServ

models)


3PAR InServ F-Class Storage Server Specifications

F-Class Drive Chassis (frontview)

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

3U

F-Class Controllers (Rearview)

Integrated Power

Supply & Battery

Integrated Power

Supply & Battery

Optional Adapter Slots Built-in Fibre Channel

(4Gb/s) ports

Built-in GigE port for Remote Copy

4U

Serving Information7

3PAR InServ F-Class Storage Server Specifications

F-Class Controllers (Rearview)

F-Class Drive Chassis (frontview)

Integrated Power

Supply & Battery

Integrated Power

Supply & Battery

• One Xeon Quad-Core 2.33GHz CPU per node• One 3PAR Gen3 ASIC per node• 4GB Control & 6GB Data Cache per node• Built-in I/O ports per node

– 4 FC (4Gb/s) ports (host or backend connectivity)

– Gigabit Ethernet port for Remote Copy• Optional I/O adapter slots per node

– Up to 2 slots per node (or up to 4 more FC and/or iSCSI ports per node

• 4U Form Factor• Cabinet Options: 2M Cabinet or 3rd party rack

mountable

• 4Gb/sec internally switched FC Drive Chassis• 16 drives in 3U• Up to 384 drives across 24 Drive Chassis• Mixable FC and Nearline drives• Cabinet Options: 2M Cabinet or 3rd party rack

mountable

Optional Adapter Slots Built-in Fibre Channel

(4Gb/s) ports

Built-in GigE port for Remote Copy

4U

3U

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD


InServ Numbering Systems

• The Administrator should know the numbering systems for:

• Nodes

• Drive Chassis

• Drive Magazines

• PCI slots

General Rule: Top = Starts with 0

Left = Starts with 0


Node Numbering

For Example:

If a T800 has only “TWO” nodes then they are located at the bottom of cabinet and numbered “6” and “7”

D

T800 - Front

SP

0 1

0

C

B

A

2 3

4 5

6 7

T400 - Front

D

0 1

C

B

A

2 3

F

E

SP



3PAR

Thank You



3PAR

3PAR Virtual Volume (VV) Concepts


Objectives:

– Understand InForm OS RAID concepts

– Understand concepts of InServ Chunklets

– Understand InForm OS Logical Disks (LDs)


InServ Concepts for Volume Management

Section Content covers:

– InServ Chunklet/Physical disk– InServ RAID 1 – InServ RAID 5 – InServ RAID MP (RAID 6)– Virtual Volumes, VLUNS (LUNS)– Logical disks (LDs)


Physical Disk – Chunklets (256 MB)

C = 256 MB Data Chunklet

SC = 256 MB Spare Chunklet

C C

C C C C

Physical Disk

SCSCSC

Each InServ Physical disk is initialized with data chunklets and spare chunklets.


3PAR RAID 1 Concepts

• RAID 1 is “mirrored” data

• Data is written as “paired” chunklets

• Each “chunklet” on the RAID set is on a different physical disk

Setsize = 2

Default size (RAID 1)

Usable space = 256 MB

C C


3PAR RAID 5 Concepts

• RAID 5 uses parity to reconstruct data• RAID 5 uses a setsize of 4 by default

Setsize = 4 (3+1)

Default size (RAID 5)

Usable space = 768 MB (3*256)

C C C p

Setsize = 6 (5+1)


C C C c c p

C C p C

Cp CC


3PAR RAID 5 Concepts Cont’d

C C C c c pCCC

Setsize = 9 (8+1)

What is the usable space for this setsize?



3PAR RAID Multi Parity (MP) Concepts

• RAID MP uses parity (double parity – can deliver data in a double disk failure) to reconstruct data and performed in the ASIC XOR engine

• RAID MP only supports two setsizes ( 8 and 16)

• The default set size of 8 has the same data to parity ratio as the default RAID-5 set size of 4 -- 3:1 in both cases.

Serving Information3PAR Company Confidential 1919

Usage – Meaning of “-ha cage” For RAID MP

• The system defines "-ha cage" as "will tolerate the failure of ONE cage”. This means:

– Up to two chunklets are allowed to share the same cage.

– The default R6 “-ha cage” set size 8 requires 4 cages per node-pair, just like the default R5 set size 4.

– If 8 cages are available, the layout will use one chunklet per cage.

– The same rules apply to “-ha mag” – up to two chunklets are allowed per mag but the system will place only one chunklet per mag if possible.


3PAR Volume Management View

Logical disksPhysical Disks Chunklets

• The 3PAR InForm OS manages the above automatically 3PAR VM manages and presents volumes to server farms

Virtual Volumes

OLTP

D.W.


3PAR InServ Virtual Volume

The only storage component visible to Hosts

Virtual Volume

Host Sees Virtual Volume

as a LUN


Building a Virtual Volume

Physical Drive

Chunklets

• Starts with Physical drives

• Divided into “Chunklets”


Chunklets: Foundation of Virtual Volume


Start with a Raid Set as the Building Block

Raid 5 (4+1) Raid Set

• Chunklets: – Selected from

separate physical drives

– Selected from separate chassis


Logical Disk

• A collection of physical disk chunklets (256 MB)

• Arranged as rows of RAID sets

• Each RAID set is made up of chunklets from different physical disks

• A chunklet can only be assigned to one logical disk


InServ Virtual Volume For RAID 5

Virtual Volume

Node Node

Logical Disk

Logical Disk

6 GB VV

3072 MB per Node/LD

C = 256 MB Chunklet

C

C

C

P

C

C

P

C

C

P

C

C

P

C

C

C

4 RAID Sets * 768 MB usable data = 3072 MB

3072 MB per Node/LD

C

C

P

P

C

C

C C

C

P

P

C

C

CC

C

RAID Set RAID Set

1

3

2

4

1

3

2

4


Default InServ Layout of 2 Node 6 GB Logical Disk

• InServ will place “chunklets” on separate physical disks

• InServ will insure physical disks are on separate drive magazines

• InServ will try to have each drive magazine on a separate drive chassis

• InServ will try to make each Logical Disk owned by each node the same size



3PAR

Thank You



3PAR

3PAR Virtual Copy


3PAR Virtual Copy

A snapshot of another Virtual Volume (a base volume or another Virtual Copy) created using copy-on-write techniques available only with a 3PAR Virtual Copy license.


Virtual Copy Characteristics

• Records only the changes to the original volume

• Administrator can make hundreds of Virtual Copies of a Virtual Volume assuming there is enough storage space

• Virtual Copy volumes use CPG space

• Using the InForm GUI to create Virtual Copies automatically enforces “relationship” rules


Virtual Copy Limits 2.3.1Maximum number of virtual volumes (base and virtual copies) 8192

Maximum number of base virtual volumes 4096

Maximum number of snapshots per base virtual volume 2048

Maximum number of read-write copies per read-only copy 256


Dual SD Space – TPVV/Base and VC

Dual SD Space provides the following benefits,

– The base virtual volume and the virtual copies can be mapped to different CPG’s. This means that they can have different quality of service characteristics. For example, the base SD space can be derived from a RAID 1 CPG and the virtual copy SD space from a RAID 5 CPG.

– The base SD space and the virtual copy SD space can grow independently without impacting each other (each SD space has it’s own allocation warning and limit).

– Dynamic optimization can tune the base SD space and the virtual copy SD space independently.


Virtual Copy 2.3.1

• Prior to 2.3.1, only one read-write virtual copy per read-only virtual copy was permitted.

• This was burdensome to customers who wanted multiple read-write copies from a single golden read-only copy.

• Prior to 2.3.1, a virtual copy could only be promoted back to the base volume.

• From 2.3.1 a snapshot can be promoted to any read-write parent within the same virtual volume family tree providing greater flexibility to the user.


Virtual Copy Promotion

• From 2.3.1 a virtual copy (snapshot) can be promoted to any read-write parent within the same virtual volume family tree.

• The promotion detects the differences between the snapshot and the read-write parent and then copies these differences back to the read-write parent.

• By default, a promotion will promote back to the base volume. However, the “-target” option can be used to specify any read-write parent within the same virtual volume tree.


Virtual Copy Relationships

• Virtual Copy can be read-only or read/write

• The rules that enforce relationships between a base volume and its Virtual Copy revolve around read-only or read/write

• Read-only and read/write (up to 256) Can make as many R/W VCs per R/O as needed. Base volumes are always read/write


Virtual Copy Relationships Cont’d

• A read-only copy can have up to 256 read/write Virtual Copys

• A read/write Virtual Copy can have many read-only copies


Virtual Copy Relationships Cont’d

• The following shows a more complex relationship scenario


Virtual Copy – Copy-on-Write Function (Data Written)

Base Volume

Snapshot Admin (SA) Space Timestamp 5/25/06 14:35

1. Pointer to data

2. P

3. P

4. P

Snapshot Data (SD) Space – Stores Original Base Volume

changes

1. A

2. B

3. C

5. E

6. F

7. G

4. D’4. D4. D

4. D’

New

Copy-on-write to SD

Write Data


Suggested Virtual Copy Naming Convention

• The InServ InForm OS does not impose a naming convention on Virtual Copies

• The Administrator names the Virtual Copy at the time of creation


InForm GUI View of Virtual Copies

• The GUI gives a very easy to read graphical view of VCs:•

Read OnlyRead Write


Virtual Copy Policy Settings

• Possible Scenario: Not enough space remains to record changes in SA or SD space which would make the snapshots “stale”

• The Admin can choose:


Creating a Virtual Copy Using The GUI

Right Click and select “Create Virtual Copy”

Specify a Name and “R/O or R/W” then click “OK”


Creating a Virtual Copy Using CLI

<createsv> command

Task: Create a R/O snapshot from a base volume

cli% creaetesv –ro svr0_vv0 vv0


Consistency Groups - VC

<creategroupsv> command

Creates consistency group snapshots of a group of VVs. Consistent group snapshots are created at the “same point in time” to ensure group VV consistency. The default is R/W.

cli% creategroupsv –ro VV1 VV2 VV3 VV4


Promoting a Virtual Copy

• The data on a snapshot can be “rolled” back to a base volume

• The base volume and the snapshot cannot be exported during this operation

• You can use the InForm GUI or <promotesv> command• Promote using GUI (right click on VC):

Promote using CLI:1. Cli% promotesv <virtual copy name>



3PAR

Thank YouThank You



3PAR

3PAR Dynamic Optimization


Objectives

– Explain the benefits of Dynamic Optimization (DO)– Change Volume RAID level– Change Volume Availability level– Change Volume Service level– Reclaim Unused LD Space



An optional InForm OS feature that enables you to dynamically tune volumes by changing volume parameters. 3PAR Dynamic Optimization (DO) requires the use of the InForm CLI and also requires a 3PAR Dynamic Optimization license



A Software Solution that offers:

• A Single-command for online and non-disruptive service level optimization

• A cost-effective approach to manage a massive scalable tiered storage array

• Flexibility for all stages of the disk-based data lifecycle


Dynamic Optimization - Data Service Level Control

• RAID 10

• RAID 50 (2 to 8+1)

Massive versus restricted use of:

• drives

• processors

• ports / loops

Selection of inner versus outer tracks on disk platters

Various sizes and speeds of FC or Nearline

RAID Type

System Resource

ApplicationRadial

Placement Drive Type


3PAR Dynamic Optimization Benefit For Storage Administration

• Allows for a non-disruptive re-layout of Virtual Volumes on the 3PAR InServ (move volumes to different physical disks to accommodate new user demands)

• Promotes system optimization through improved utilization of all physical resources for the current configuration (Take advantage of a H/W upgrade)

• Allows for altering of “service levels” associated to a Virtual Volume (change RAID levels, set sizes, spare chunklets)


1. Proactively ensure data service levels during expected peak demand periods (Quarter End, Holiday Shopping Season, High volume trading days)

2. Meet service level or SLA change orders on demand.

Dynamic Optimization – Potential Uses

Unused Buffer

App B(RAID 5)

App C(RAID 5)

Unused Buffer

App B(RAID 5)

App C(RAID 5)

Peak PeriodNormal Period Normal Period

App A(RAID 10)

GreaterRevenue

GreaterRevenue

RAID 10Striped massively

RAID 50 (3+1)Greater resources

RAID 50 (7+1)Restricted resources

App A(RAID 5)

App A(RAID 5)

Silver Gold Platinum

App C(RAID 5)

App B(RAID 5)

Unused Buffer

Performance, Port Resources

Spindle, Loop Resources


3. Deliver the required service levels for the lowest possible cost throughout the data lifecycle

4. Accommodate rapid or unexpected, application growth on demand by freeing raw capacity

Dynamic Optimization – Potential Uses

Create 7.5 TBs of useable capacity on demand !10 Useable TBs

+ 7.5 Useable TBs

20 Raw TBs, RAID 10 20 Raw TBs, RAID 50

10 Useable TBs

10TB Useable

50% Savings

80% Savings*

RAID 10147GB FC Drives

RAID 50 (3+1)300GB FC Drives

RAID 50 (7+1)500GB ATA-Class Drives


3PAR Dynamic Optimization at a Customer

Before Dynamic Optimization

0

100

200

300

400

500

600

1 20 39 58 77 96

Physical Disks

Ch

un

klet

s

Free

Used

After Dynamic Optimization

0

100

200

300

400

500

600

1 20 39 58 77 96

Physical Disks

Ch

un

klet

s

Free

Used

Data layout after a series of capacity upgrades

Data layout after Dynamic

Optimization (non-disruptive)


Re-layout of a Volume Following Hardware Upgrade

• Scenario:• 2 nodes have been added (nodes 2 and 3)

• cli% tunealdvv –nd 2,3 <volume name>

• To verify results use showld –vv


Change Volume RAID Level

• Scenario:

• Volume was originally created as RAID 1. Customer elects to save disk space and wants RAID 5.

• cli% tunealdvv –t r5 <volume name>



Change Volume Availability Level

• Scenario:• You have added some cages and now would like to

take advantage of added cage availability

• cli% tunealdvv <volume name> (default is cage availability)





3PAR Customer Training:

System Reporter


Course Objectives

• At the end of this presentation the student should be able to :

– Understand the Components of System Reporter– Know where to find Install and Configuration

documentation for System Reporter– Use System Reporter User Manual– Produce reports– Use “Quick Reports”


Available Documentation

• Customer documentation

– Release Notes – Available on CD

– User Guide – Available from the web client and separately on the CD

– White Paper – Ashok Singhal (developer of System Reporter & CTO)


View Of SR Documentation - DCS


System Reporter is Historical Reporting Tool

• Administration and Debugging– Identify performance problems that may have

happened a short while ago– Drill-down on performance changes

• Capacity Planning

– Space usage trends– Performance capacity trends

• Active Monitoring– Email Alerts


System Reporter Report Types


System Reporter Requirements


Installing System Reporter

3 Basic Steps –

Less than 30 minutes to install in most cases

1. 3PAR CLI

2. Apache Server

3. Run System Reporter


SR and User Interface Components


Theory of Operation: Database

• Database server can be on different machine for MySQL and Oracle.– SQLite database is just files in a directory.

• Sampler and web server communicate only via the DB– Exception: When adding InServ to be sampled, web server creates

password file that the sampler then uses.• The “sampleinserv” table in the DB tells sampler which InServ

systems to sample.• The policy table in the DB tells sampler

– where the CLI password files for InServs are– how often to sample– how long to keep the samples– when to compact the DB

• The “alertconfig” table in the DB tells sampler what metrics to compute to see if an alert should be generated.


Theory of Operation: Database Schema

• Database Schema documented in User Guide chapter 9• Naming convention:

– Administrative: <base>_<version>. Eg: policy_1– Data and inventory: <base>_<res>_<version>. Eg:

pdspace_hourly_2• Three types of tables: administrative, data, inventory• Administrative tables:

– policy– sampleinserv– system– alertconfig

• Data tables– Space– Performance

• Inventory Tables


Implementation: Database

• Separate HiRes, Hourly, Daily tables– <table>_hourly_<version> (eg. pdspace_hourly_1)

• Two types of samples: Space & Performance– Space sampled slower than performance (ratio is programmable in

policy table).– But hourly and daily samples always contain both space and

performance.

• Space tables– pdspace (showpd info)– vvspace (showvv info)

• Performance tables– statpd– statvvlun– statcpu


Implementation: Reports

Report naming convention <object>_<yaxis>_<xaxis>

<xaxis> is either:• time : The report plots the <yaxis> measures of <object> versus time• group: The report plots the <yaxis> measures of <object> versus various groups

– Groups specified by “groupby” parameter

<yaxis> is either:• perf: The measures are performance-related (IOPs, benadwidth, service time etc)• space: The measure are space-related

Currently implemented <object>_<yaxis> combinations:

<object> perf space

vv Raw, LD and virtual space

vlun IOPs, bandwidth, service time, IO Size

pd IOPs, bandwidth, service time, IO Size Chunklet usage

cpu User/System/Idle time, interrupts/s context switches/s


Files That You Might Want to Password Protect

• All files created by System Reporter have default permissions. Anyone can READ the files

• For MySQL and Oracle the following files contain password information which you might want to change permissions:

C:\Program Files\3par\System Reporter\dbpwfile

C:\Program Files\Apache Group\Apache2\cgi-bin\

3par-policy\config.tcl

C:\Program Files\Apache Group\Apache2\cgi-bin\

3par-rpts\config.tcl


System Reporter Web Interface


Quick Reports


Scheduled Reports

See 5.5 Scheduling Reports for complete details on scheduling a report


Custom Reports

In general, there are two steps involved in generating a report:

1 Choose a report, select the sample resolution, select the InServ system(s) and/or domain(s)and click on the Build Report Menu button. This will generate the report menu for thatreport in a new window (or tab).

2 Set the appropriate controls in the report menu and click on the Generate Report button (next slide).The report will be generated in a new window (or tab).


Generate Report


System Reporter Panes

• Report Selection Pane– Click on a link to a report in this pane to generate the

form for setting parameters for the report in the Query Pane

• Query Pane– Contains the form for selecting the parameters for the

report– Once parameters are selected click “Submit Query”

• Results Pane– Where output is displayed


System Reporter Sampling

• 3 Sampling Resoulutions1. Daily2. Hourly3. High-resolution

• Daily and Hourly data samples are as close to the beginning of each day and hour as possible

• High-Resolution are taken at user-specified interval that can be one or more minutes

• User sets retention policies for how long samples are kept


Producing Reports

• Easy to use GUI

• Can report on:– Hosts– LDs– VVs– VLUNS– PDs

• Configure Alerts


VLUN Performance Query Pane


Daily VLUN Performance


Hourly VLUN Performance - Details

• By default, all VLUNS on the sampled InServs are included in the report – the preceding slide shows the “aggregate” of all VLUNS

• You can select a “specific” set of VLUNS using the Query Pane

• You can also select a specific InServ as well

• Notice that separate metrics for “reads’ and “writes” are shown for most metrics in aggregate performance charts


Compare Systems - VLUN


Hourly VLUN Performance at Time


VLUN Performance – Histogram


Aggregate VV Cache Performance over Time

Reason to use:

– Suppose different workloads are run on a system at different times

– Storage performance (service time) differs across workloads

– The IOPs and bandwidth view does not shed any light on why the differences

– Often, these differences can be explained by different cache performance for the specific workloads

– One sees this by plotting aggregate VV cache performance versus time and observe the different cache behavior during different periods


Hourly VV Cache Performance


System Compare – VLUN Performance

Purpose:

– Compare performance of all systems with respect to VLUN performance

– Select “System” in the “Compare” menu in the “Report Selection”

– Produces a separate line for each system that you can compare each relative to the others

– Each line represents the aggregate for all the VLUNs in that InServ system


System Compare – VLUN Performance


Performance at a Specific Time

• Select the “At Time” option in the “Report Type” menu in the “Report Selection”

• With “At Time” the X-axis is the object name – separate set of data points for each object

• In the Query Pane when “At Time” is selected, the “Group By” and “Order By” menus are enabled

• The “Group By” allows much flexibility when comparing objects since multiple items in the “Group By” can be selected at the same time


Hourly VLUN Performance at Time - Domains

No Domain -


Hourly PD Performance At Time

• A common use of “At Time” reports is to compare a large number of objects

• Looking at all the Physical Disks (PDs) for their performance can be accomplished by:

– Select only one system from “Select Systems”

– Select “PDID” from the “Group By” menu

– Select “IOPs” from the “Order By” menu


Hourly PD Performance At Time


VV Cache Performance

Scenario: Some VVs are showing “higher” service times to other VVs that have similar characteristics.

Possible Reason: The VVs with the higher service times may be experiencing different cache performance.

Generate Report: Use “At Time” option for “Report Type” and VV in the “Group By” menu. The “Order By” is set to TotalAccesses.


VV Cache Performance


Other Reports

• The types of reports available are many with System Reporter

• Of course, remember you are displaying “historical” data based upon the retention policy you set.

• 3PAR Engineering can “get” a copy of your System Reporter database to help study your environment

• The following slides contain report examples that System Engineers and Engineers use to learn about InServ installations


PD Performance


PD Space Usage Report at Time


VLUN’s by IOP and BW


VLUN Service by Time and IO size


VLUN Queue Length


Hourly Port Performance


PD Service at Time


System Reporter Database sizing

• New system sizing spreadsheet.

– A new spreadsheet has been included on the CD to aid in sizing the system running System Reporter and database.


Configuring Email Alerts

• Email alerts can be configured when certain metrics meet specified conditions

• To add an alert:

1. Click on “Sampling Policies” link in the “Report Selection” Pane

2. Opens new window where you click on “Add Alert”


Add Alert Rule

Setting: Receive an email alert when any VLUN has an average read service time of more than 100 ms in any high-resolution interval.



3PAR

Thank YouThank You



3PAR

3PAR Customer Support Information

Serving Information

• For any issue with your InServ, call:– 1-888-372-7226– 24 x 7

• Create an iSupport account– Go to the 3PAR website

• Services, then “log in to 3PAR Central”

– Can download manuals, open service ticket

SUPPORT

119

Serving Information

3PAR Login’s

Location Username Password

3Par Node Login console cmp43pd

3Par SP After Install spvar 3parvar

3Par Inserv After Install 3paradm 3pardata

3Par SP After Install 3parcust 3parInServ

Note: I and S are Caps.




3PAR

Thank YouThank You

serving information 3par hardware overview 3par virtual volume concepts 3par virtual copy 3par...

Documents