3PARdata Inc.

Confidential

SQA Test Plan for 3PAR Secure

Service
Revision History
Version

Date

Author

Description

1.0

05/28/09

Gomathi Venkatesan

Initial Draft

This test report contains information that is confidential and proprietary to 3PARdata Inc. 2009

Page: 1

3PARdata Inc. Confidential

Table of Contents
SQA Test Plan for 3PAR Secure Service...............................................................................................1
1 Introduction......................................................................................................................................... 3
2 Scope & Objective.............................................................................................................................. 3
3 Hardware Requirements..................................................................................................................... 3
4 Software Requirements...................................................................................................................... 3
5 Test Approach..................................................................................................................................... 4
6 Test Configuration............................................................................................................................... 5
7 Features to be tested.......................................................................................................................... 6
7.1 Installation and Configuration.......................................................................................................6
7.2 Security........................................................................................................................................ 6
7.2.1 Internet Security.................................................................................................................... 6
7.2.2 Product Specific Security.......................................................................................................7
7.3 Policy Manager............................................................................................................................ 7
7.4 Custodian Commands.................................................................................................................. 7
7.5 STaTs........................................................................................................................................... 8
7.6 Remote Monitoring and Operation...............................................................................................8
8 Features not to be tested.................................................................................................................... 9
8.1 Axeda........................................................................................................................................... 9
9 Entry/Exit Criteria................................................................................................................................ 9
9.1 Entry Criteria................................................................................................................................ 9
9.2 Exit Criteria.................................................................................................................................. 9
10 Testing Deliverables......................................................................................................................... 9
11 Schedule........................................................................................................................................... 9
12 Test Review Notes............................................................................................................................ 9

Page: 2

3PARdata Inc. Confidential

1 Introduction
This document is the test plan for the components that comprise the product, 3PAR Secure Service. This
document lays out the test strategy, test approach, test areas, and test configuration.

2 Scope & Objective

This product consists of the following distinct but interworking software modules.

Secure Service Custodian (SSC)

Policy Manager (PM)

Service Processor (SP)

Enterprise Server

STaT

SPOCC

The objective of this testing is to validate all the components that comprise 3PAR secure service. These
components are as follows.

Security

Policy Manager

Custodian Maintenance (cpmaint commands)

Remote Monitoring and Operation

Outside the scope:

Third party products that are integrated, e.g. Axeda

3 Hardware Requirements
We need the following hardware.
Multiple InServs
Multiple SPs
A Super Micro server for running Custodian
A Windows XP Server for running Policy Manager

We will use existing lab common infrastructure (like the network) to interconnect the
above hardware.

4 Software Requirements
We need the following software.
Custodian Base Image CD
Custodian Software ( CD or server location where it can be downloaded from)
Policy Manager Software

We will need licensing information, if any, for the above software.

Page: 3

3PARdata Inc. Confidential

5 Test Approach

3PAR Central

Collector
Server

Stat

Internet
Internet

Customer site / QA setup

Firewall

Policy
Manager

SSC

SSC

Inser
v

Inser
v

Inser
v

SP

SP

Inser
v

SP

SP

Inser
v

SSC
C

Page: 4

SP

3PARdata Inc. Confidential

The purpose of this product is to monitor and control 3PAR InServs at customer sites from 3PARs customer
service center called 3PAR Central. Naturally testing of this product involves setting up, configuring and
running tests from both these places.
3PAR Central is managed by 3PAR IT. This test plan assumes that all the installation, setting up and
configuration on the side of 3PAR Central relating to use of this product will be done 3PAR IT. SQA will only
use these facilities to run tests on components of this product resident at customer site.
The focus then for SQA is the product components located at customer sites. SQA will set up multiple
customer sites in SQA lab. There will be tests covering monitoring and controlling of multiple customer sites.
There will be three kinds of testing in testing this product.

Tests that are run entirely in SQA setup

o

Tests on SSC

Tests on PM

Tests that are run or verified at 3PAR Central

o

Remote Monitoring of Logs

Remote connections to Inserv

6 Test Configuration
The following configurations of the different software modules of the product will be used in this testing.

One SP and one InServ

One SSC and five SPs

One PM and one SSC

SSC configured to talk to ES

SSC configured to talk to ES without PM

SSC configured to talk to ES with PM

SSC configured to talk to ES with PM and HTTP Proxy without authentication.

SSC configured to talk to ES with PM and HTTP Proxy with authentication

SSC configured to talk to ES with PM and Socks5 Proxy without authentication

SSC configured to talk to ES with PM and Socks5 Proxy with authentication

SSC configured to talk to ES with HTTP Proxy without authentication.

SSC configured to talk to ES with HTTP Proxy with authentication

SSC configured to talk to ES with Socks5 Proxy without authentication

SSC configured to talk to ES with Socks5 Proxy with authentication

The following types of hardware for SP will be used in this testing.

Wintech

Dell

Super Micro

The hardware used for running SSC will be the one from Super Micro.

Page: 5

3PARdata Inc. Confidential

Different software versions of SP will be used in the testing, including the version 2.2.4.
Windows XP and Windows 2000 will be used for running Policy Manager.
Different browser types and versions will be used for running SPOCC and STaTS.
ES server will be tested using IE7.

7 Features to be tested
The components or functionality areas of the product that will be tested are as follows.

Installation and Configuration

Security

Policy Manager

Custodian Commands (cpmaint)

SPOCC

Remote Monitoring and Operation

The specific features that will be tested under each of the above components or functionality areas are as
follows.

7.1 Installation and Configuration

SSC Reimage/MOB
Verify that the Base image install passes without any errors
Verify that the SSC can be installed without any error via the CD
Is there a way to do this via the net?

SCC Rebuild
Verify that the SSC can be rebuilt with the CP backup file

Upgrade of SSC via Axeda package from ES

Axeda package will be generated and made available on ES | Software | Deploy
User will have to select the package to be deployed

Upgrade of SSC via CD via cpmaint

Download SP patch to SP via Axeda package from ES

Axeda package will be generated and made available on ES | Software | Deploy
Once the package is deployed on SSC, this will be automatically uploaded to SP.

Download InServ patch via Axeda package from ES

Download InServ MU to SP via Axeda package from ES.

7.2 Security
7.2.1 Internet Security

Proxy HTTP

Page: 6

3PARdata Inc. Confidential

Without Authentication

With Authentication

Proxy SOCKS5
o

Without Authentication

With Authentication using GSSAPI

With Authentication using Username/Password

With Other Supported Authentications

For all of the above configuration between the SSC and Collector Server:
Verify that the CPSplor can be launched
Verify that CPBackup can be performed
Verify that the files a re being transferred successfully to sTats

7.2.2 Product Specific Security ( controlled by 3PAR IT )

Authentication (between 3PAR Central and Customer Site)

Operate with 3PARs Active Directory

Authorization (implemented in Policy Manager)

Audit Logging (implemented in Policy Manager)

7.3 Policy Manager

Installation and setup

Install at admin
Install as non admin
Verify installation on Windows XP, 2K and 2003
Verify that multiple SSC can talk to the policy manager

Add/Delete/Change Policies
Verify various permission levels for each of the policies
Verify that a global policy can be set

Verification of actions per access rights

Policy Inheritance and Hierarchy

Verification of notifications

7.4 Custodian Commands

Configuration Backup

Page: 7

3PARdata Inc. Confidential

Verify backups form the same SSC

Verify backup from a different SSC
Verify installation of corrupted backup file fails
Verify that backup with missing file fails

CPSPLOR

Display networks settings

Test Network

Test Connection to Collector

Reconfig network settings

Network interface speed

NTP server addresses

Reset date

Remove SP from device list

Start/Stop Custodian Agent

Display Custodian SW levels

Update Custodian SW

Reboot Custodian

Reconfigure PM

7.5 STaTs
7.6 Remote Monitoring and Operation

Configuration information

Status

Event log

Alerts

Events

InSplore

SPLOR

File Transfer
o

Transfer to designated location (for the user ) on ES.

In order arrival of data files for a given device.

Dumps

Device discovery

Device site association

Missing devices

Page: 8

3PARdata Inc. Confidential

SP upgrade

InServ upgrade / downgrade

8 Features not to be tested

SP

8.1 Axeda

9 Entry/Exit Criteria
9.1 Entry Criteria
The product must satisfy the following criteria before it will be accepted for testing.

The product must install without any errors.

The product must not have any crashes.

The development team must have completed unit testing on all components of the product.

The development team must have done integration testing on the product as a whole.

9.2 Exit Criteria

The product must satisfy the following criteria before the testing can be stopped.

There must not be any P1 or P2 bugs in the product. In other words, any discovered P1 or P2 bugs must
be fixed by the development team and the fix verified by the SQA team.

10 Testing Deliverables
The following deliverables will be made by the SQA team while testing this product.

A document describing the test plan

A document describing the test cases

A document describing the results of running the above test cases

Test Closure Report

A schedule for this testing

11 Schedule
12 Test Review Notes

Page: 9