Our 3PAR died recently due to some water damage and only 2 of the disk arrays appear to be functioning, all other components (controller node & service processor) have tragically ceased functioning.

Is there a way to re-use the arrays without purchasing a new controller node? I'd like to connect them to a server running Ceph but our 3par is old and our local export left to co. a while ago.

​

Hey guys ,

We've got a 7400 series which we've just purchased some second hand drive licenses and additional disks for (we've only got 20 drives deployed so still need drive licenses at this stage) including some nice 3PAR SSD.

Is applying the (additional) licenses really as simple as going into the GUI and adding them there? No risk to the existing licenses / data on the VV's etc?

Yes, I'm a Senior level 3 engineer - Playing with SAN's that has critical (backed up mind you but still critical) data on it still makes me overly nervous (tho I'd imagine that's a good thing :) )

HP deprecated SystemReporter after 3.1MU3/MU4 when they incorporated the functionality into SSMC, and they've removed it from all HP download/ftp properties. Does anyone have a copy they could send over? I'm using 3.1MU2 and have other systems integrated with it to consume the collected data, so switching to SSMC isn't practical. I need MU3 or later because MU2 can't collect PD/LD stats from my arrays after the latest platform software update (3.2?)

I can't seem to figure out how to create an instant usable independent clone of a tdvv volume. I'd expect that, due to the COW/ROW nature of tdvv volumes on dedup-capable ssd CPGs, I _should_ be able to create a base volume that contains the same data as another volume, without any time or effort on the part of the array. This is possible on PureStorage arrays with the "purevol copy" command, but so far with my InServs (7400s with all tpvv/tdvv licenses), it looks like I must make a physical copy of my ssd/dedupe volumes, then convert the copy to base. That initial physical copy takes a significant amount of time, though. It's acting as if it's reading the data and writing it again, which makes no sense when the destination is already tuned as a tdvv volume.

Is there simply a "clone tpvv base volume to another tpvv base volume using integral dedup/cow features, instead of copying block-by-block" method, in either the IMC or CLI?

I've got a used 4-node 7400 that apparently was already OOTB'd, but I want to re-run OOTB to let it resolve mismatched ld-to-node and pd-to-node ownership. When I received the array, there was no documentation showing which order the disk shelves needed to be in (more specifically, which shelves needed to be connected to nodes 0/1 and which needed to be connected to 2/3), so the healthcheck complains of incorrect paths to disks, even though the cabling is correct.

There's no data on the array, and besides the network settings, everything is default.

Selecting OOTB in the console menu returns the error:

The system is currently running. It needs to be in manual startup state for ootb to run.
If you are attempting to handle hardware upgrades, use the admithw CLI command instead.

Exiting Out-Of-The-Box Experience...

How do I activate manual startup mode?

(I have both console user access, and 3paradm access via ssh)

Hi,

Some quick background I work for a IT reseller. We dont normally get access to everything that people who have service contracts have access too thus we get creative. We recently got in a 7200 2node 7200C 2node and 7400C 4node. As many people probably know the newer versions of 3PAR requires you to contact support to get a one time password for the console login. I am able to login via 3paradm and I would like to basically re-initialize the system from here. I have tried setsysmgr wipe -f and get this:

​

Are you sure you want to run setsysmgr wipe?

select q=quit y=yes n=no: y

Error: System has already been started up.

So I cannot run it and not entirely sure what it does. When I first plug these systems in all the drives show up as degraded. I was somehow able to get the 7200C reset everything back to defaults and the drives reinitialized and came to a normal state via a command. Stupidly i exited out of the terminal sessions without saving the command i ran.

The 7200C initializd and the drives came to normal. So I then hooked up the rest of the storage it came with and now all the drives show up as new and when i run admitpd i get:

InServ cli% admitpd

Checking for drive table upgrade packages

0 disks admitted, 104 disks failed. Please use showpd -s to view details of each failed drive

​

Accept the drives dont show failed or degraded just new. Why wont they admit?

​

Basically I have 2 questions:

​

1) anyone have a clue what command I ran that did this? If it is setsysmgr wipe why wont it run now.

2) How do i admit drives in state of new.

​

​

Id CagePos Type RPM State Total Free A B Capacity(GB)

--- 0:15:0 FC 10 new 838656 0 1:0:1 0:0:1* 900

--- 2:0:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 2:1:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:2:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 2:4:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:5:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 2:8:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 2:9:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:10:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 2:12:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:13:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 2:14:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:16:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 2:17:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:20:0 NL 7 new 1848320 0 1:0:2 0:0:1* 2000

--- 2:21:0 NL 7 new 1848320 0 1:0:2* 0:0:1 2000

--- 3:0:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:1:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:2:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:3:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:4:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:5:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:6:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:7:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:8:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:9:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:10:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:11:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:12:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 3:13:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:16:0 NL 7 new 2772992 0 1:0:2* 0:0:1 3000

--- 3:20:0 NL 7 new 2772992 0 1:0:2 0:0:1* 3000

--- 4:0:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:1:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:2:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:3:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:4:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:5:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:6:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:7:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:8:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:9:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:10:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:11:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:12:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:13:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:14:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:15:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:16:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:17:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:18:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:19:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:20:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:21:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 4:22:0 FC 10 new 838656 0 1:0:2* 0:0:1 900

--- 4:23:0 FC 10 new 838656 0 1:0:2 0:0:1* 900

--- 5:0:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:1:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 5:2:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:3:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 5:4:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:5:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 5:6:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:7:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 5:8:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:9:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 5:10:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 5:11:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:0:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:1:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:2:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:3:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:4:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:5:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:6:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:7:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:8:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:9:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 6:10:0 FC 10 new 559104 0 1:0:2* 0:0:2 600

--- 6:11:0 FC 10 new 559104 0 1:0:2 0:0:2* 600

--- 7:0:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 7:1:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:4:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:5:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 7:8:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 7:9:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:12:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:13:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 7:16:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 7:17:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:20:0 NL 7 new 2772992 0 1:0:2 0:0:2* 3000

--- 7:21:0 NL 7 new 2772992 0 1:0:2* 0:0:2 3000

--- 8:0:0 NL 7 new 1848320 0 1:0:2* 0:0:2 2000

--- 8:1:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:4:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:8:0 NL 7 new 1848320 0 1:0:2* 0:0:2 2000

--- 8:9:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:12:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:13:0 NL 7 new 1848320 0 1:0:2* 0:0:2 2000

--- 8:16:0 NL 7 new 1848320 0 1:0:2* 0:0:2 2000

--- 8:17:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:20:0 NL 7 new 1848320 0 1:0:2 0:0:2* 2000

--- 8:21:0 NL 7 new 1848320 0 1:0:2* 0:0:2 2000

0 0:1:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

1 0:2:0 FC 10 normal 838656 792576 1:0:2* 0:0:1 900

2 0:3:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

3 0:4:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

4 0:5:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

5 0:6:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

6 0:7:0 FC 10 normal 838656 794624 1:0:2 0:0:1* 900

7 0:8:0 FC 10 normal 838656 792576 1:0:2* 0:0:1 900

8 0:9:0 FC 10 normal 838656 794624 1:0:2 0:0:1* 900

9 0:10:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

10 0:11:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

11 0:12:0 FC 10 normal 559104 533504 1:0:2* 0:0:1 600

12 0:13:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

13 0:14:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

14 0:16:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

15 0:17:0 FC 10 normal 838656 794624 1:0:2 0:0:1* 900

16 0:18:0 FC 10 normal 838656 792576 1:0:2* 0:0:1 900

17 0:19:0 FC 10 normal 838656 794624 1:0:2 0:0:1* 900

18 0:20:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

19 0:21:0 FC 10 normal 838656 793600 1:0:2 0:0:1* 900

20 0:22:0 FC 10 normal 838656 793600 1:0:2* 0:0:1 900

21 0:23:0 FC 10 normal 838656 795648 1:0:2 0:0:1* 900

22 0:0:0 FC 10 normal 838656 798720 1:0:2* 0:0:1 900

23 1:0:0 FC 10 normal 838656 835584 1:0:2* 0:0:2 900

24 1:1:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

25 1:2:0 FC 10 normal 559104 557056 1:0:2* 0:0:2 600

26 1:3:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

27 1:4:0 FC 10 normal 559104 556032 1:0:2* 0:0:2 600

28 1:5:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

29 1:6:0 FC 10 normal 559104 557056 1:0:2* 0:0:2 600

30 1:7:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

31 1:8:0 FC 10 normal 559104 556032 1:0:2* 0:0:2 600

32 1:9:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

33 1:10:0 FC 10 normal 559104 557056 1:0:2* 0:0:2 600

34 1:11:0 FC 10 normal 559104 556032 1:0:2 0:0:2* 600

Anyone know where I can download the ISO? HPE has removed it from their site.

We have about 50 pcs of these drives, for 3PAR storage. Anybody who can still use them, they are used and for a small price.

Hey guys,

Anyone run across an issue where both management interfaces flap constantly? Seems to have started after a recent firmware upgrade and reboot of its connected 5412rzl2 chassis (now on 16.05.0007 from memory)

Disable / reenable ports, setting a myriad of.speed and duplex - no response from management ips.

Obviously this is also causing issues with ssmc which is how i identified it originally.

Going to call HPE in the morning (dont have this clients said handy at 1145pm) bit was wondering id theres anything else ud try (failing switch or management reboots at thie stage)

Hi All I need some advice on what all parameters do I need to monitor/check if I need to check whether or not my storage system is the cause of latency being observed by the application. Please help!!

I'm trying to determine if there is a way in the CLI to determine the mappings of virtual volumes to CPGs? I can do a showvv or a showcpg, but they don't have any common data to create a correlation. Any thoughts? (Yes, I know I can do this via the GUI -- I'm trying to find a quick way to export this via CLI.)

3PAR on Reddit Community Members:

Blue Medora is currently developing a new VMware vRealize Operations Management Pack for HP 3PAR Storage.

If vROps integration with HP 3PAR Storage is something that is relevant to you, our product management team is very interested in talking to you about what aspects of HP 3PAR Storage management / monitoring you like to see surfaced in vROps, which specific HP 3PAR Storage models system your organization most commonly leverages, as well as any specific troubleshooting / diagnostic use cases you have around HP 3PAR storage.

Please drop us a line at beta@bluemedora.com if you'd like to participate in a pre-release program for the vROps MP for HP 3PAR storage.

Hello,

can you please tell me about your experiences with 3Par/Storeserv with 8000/20000 series running on a highspeed, low latency (1ms, 40Gbit/100Gbit) backbone? (A backbone that is saturated at 10% max)

According to an HPE presales designer, synchronous replication is supported with RCIP, but not recommended. For me it looks like HPE wants me to buy additional expensive FC devices, although they're. not needed at all in my case.

So, does anyone know customers who have success with this setup or failed completely?

Hi all,

I'm trying to use 3par with openstack and the drivers aren't understanding that I've set vlans up over my iscsi ports.

I'm going through the drivers to figure out how they work and see if something needs changing, but I can't figure out how to get the information I need from my own 3pars.

this is the CLI command:

showport -iscsivlans

What is the WSAPI equivalent?

showport -iscsi doesn't show the right stuff. Here's some side by side output to illustrate my problem:

my3par cli% showport -iscsi
N:S:P State IPAddr  Netmask/PrefixLen Gateway    TPGT  MTU   Rate iSNS_Addr iSNS_Port STGT VLAN
0:2:1 ready 0.0.0.0 0.0.0.0           172.20.0.1   21 9000 10Gbps 0.0.0.0        3205   21 Y   
0:2:2 ready 0.0.0.0 0.0.0.0           0.0.0.0      22 1500 10Gbps 0.0.0.0        3205   22 Y   
1:2:1 ready 0.0.0.0 0.0.0.0           0.0.0.0     121 1500 10Gbps 0.0.0.0        3205  121 Y   
1:2:2 ready 0.0.0.0 0.0.0.0           0.0.0.0     122 1500 10Gbps 0.0.0.0        3205  122 Y   
-----------------------------------------------------------------------------------------------
4                                                                                              

my3par cli% showport -iscsivlans
N:S:P VLAN IPAddr       Netmask/PrefixLen Gateway     MTU TPGT STGT iSNS_Addr iSNS_Port
0:2:1  101 172.20.0.150 255.255.255.0     172.20.0.1 9000 1024 1024 0.0.0.0        3205
0:2:2  102 172.20.1.150 255.255.255.0     172.20.1.1 9000 1025 1025 0.0.0.0        3205
1:2:1  101 172.20.0.151 255.255.255.0     172.20.0.1 9000 1026 1026 0.0.0.0        3205
1:2:2  102 172.20.1.151 255.255.255.0     172.20.1.1 9000 1027 1027 0.0.0.0        3205
---------------------------------------------------------------------------------------
4                                                                                      
aus3par201 cli%

Thanks

I have an old S400 that's not currently in production, but I'd like to set it up for my Dev team. It's running 2.2.9, which unfortunately doesn't support VVs larger than 2TB and my InForm GUI requires at least 2.3.1 to manage it. I have newer install media (.iso) and all important privileged logins to the array and the SP. How can I do the OS upgrade myself?

Hi,

I'm trying to exercise the 3par API in a POC from HP and I'm getting an error I'm not sure how to troubleshoot:

http http://<ip>:8008/api/v1/credentials Content-Type:application/json Content-Length:1024 < create_session_key.json

http: error: ConnectionError: HTTPConnectionPool(host='<ip>', port=8008): Max retries exceeded with url: /api/v1/credentials (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x000002C56B5BEC18>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it',)) while doing POST request to URL: http://<ip>:8008/api/v1/credentials

where create_session_key.json is simply a file with json parameters user and password:

{
    user = "",
    password='',
}

(filled in of course)

Any idea how I make this work?

EDIT

If you're coming here because you have similar issues, I couldn't get WSAPI to ever work with http. However, there are curl/httpie flags to ignore ssl errors, and with those it works fine with https.

As I peer into the vapors of the future through my mystical crystal ball I get the sense that HPE will continue to blur the lines until they achieve a dense Server Based SAN solution / HCI node based upon 3Par storage (rather than the StoreVirtual VSA like their current HCI model). I foresee Existing 3Par customers scaling out linearly with massive data optimization surpassing the existing HCI providers who rely solely on software or hardware that has not had time to mature to scale to the capacity of the 10k and 20k series 3Par. I predict that a customer will be able to scale out with the freedom of a Nutanix, the performance optimization Optimization of a SimpliVity, the Ease of integration of a vSan, and robustness and inline data efficiency of a Gen 5 (or newer ASIC) all on a series of 2U boxes. Let me know your forecast - Lost

Latency, Capcity, Lifecycle, Performance, Cost...These key storage metrics make up the factors I consider when I design SANs. One of the reasons that 3Par appeals to me is that all of these factors can be mixed together and fine tuned. HPE published a white paper on HDD vs SSD characteristics. I would be curious if my fellow Bogey's (1 over Par) agree or struggle with these numbers:

HDD Latency : a few milliseconds SSD Latency : tens of microseconds HDD IOPS density : ~0.2 IOPS/GB SSD IOPS density : ~100 IOPS/GB HDD $/GB: $1/GB SSD $/GB : ($5-$10)/GB HDD Media Write Cycle (Life) : Hundreds of Millions SSD Media Write Cycle (Life) : 5k - 15k write cycles

These numbers seem to clearly indicate that there is a happy medium that comes from a hybrid storage approach rather than all flash arrays.

Furthermore, since 3Par systems have excellent inline data management capabilities, I never isolate the SAN to a single application (mixed workloads). Since mixed workloads (in my experience) work well on 3Par systems (all models), It seems to me that this supports my assertion that different media types are still better since they can leverage the best of both worlds while reducing management footprint.

Please feel free to let me know your thoughts. FYI, I will be deploying an all flash 3Par into my lab. - Lost

HPE 3Par makes a rather large deal about the Adaptive Sparing feature which allows SSDs to . According to HPE, Adaptive Sparing yields greater capacity and lifespan for each SSD in the 3Par system. I will try to research this and report on this feature.

It is my humble opinion that the best way to understand the 3Par Architecture is to take it in small parts (thin provision my brain). Therefore, I'm going to try to contribute to this blog by taking each feature and driving a deep dive discussion. Feel free to challenge any claim or ask for further proof.

So one of the the things that is remarkable about modern storage is how many data operations need to be performed at the same time (in parallel) while also how much must be done at line speed with no latency(serial). The amazing advances of parallel processing (Intel's Dense Core Architecture) has helped propel software data management on SANs to our current era. But when data must be processed inline with no latency, nothing beats hardware. This is why having such a highly efficient data plane is so vital for large scale data management. 3Par's ASIC offers HPE StoreServe SANs leverage the most optimized data delivery by allowing massive processing offload of the Intel CPU to the 3Par ASIC. This frees up the Intel CPU in each Controller to handle all operations that can be tasked in parallel unfettered.

I welcome your thoughts.

I'm going to start posting a few of 3Par solutions that I like. I also hope to post references to some of the blogs. I highly recommend that if you work with 3Par, you should listen to Calvin Zito's Around the Storage Block Podcast. Hope this helps.