Deploy and Set Up a 3PAR Virtual Service Processor (SP 5.0.5 Example)

This archived example deploys a VMware virtual Service Processor (VSP), configures its network, initializes the Service Processor, and then sets up a 3PAR StoreServ system. The source package and console show SP 5.0.5.0-26662 with legacy vSphere Client screens. Treat the pictured versions, names, addresses and capacity values as historical examples; check the support matrix and matching setup guide for the actual array and hypervisor.

Readable original English console images are retained. Other views are replaced by English instructional reconstructions, with simplified layouts and illustrative inventory labels. They are not literal screenshots of a new installation. Source credentials, saved password fields and personal contact details are omitted. No virtual machine, SP, array, account or network configuration was changed to prepare this edition.

1. Prepare and deploy the OVF package

Obtain the appropriate VSP package through the authorized product distribution channel and extract it. Keep the OVF descriptor and its associated virtual disk and manifest files together. The historical descriptor is SP-5.0.5.0-26662.ovf. Confirm the actual prerequisites before deployment; the versioned guide cautions against placing the VSP on storage provided by the same array it manages.

Fresh English extracted-package illustration. Descriptor, disk and manifest filenames are historical examples, with no license data reproduced.

In the appropriate vCenter/vSphere client, start Deploy OVF Template and browse to the extracted OVF descriptor. The original selection and Source screens are represented by the same simplified English excerpt below. Its compact navigation is illustrative; follow the actual wizard and all placement steps described here.

Fresh English OVF file-selection excerpt; select the package descriptor, not an unrelated file.

Same English source-selection excerpt at the original Source confirmation step.

Review the template details and continue. The pictured package reports a 1.0 GB download and 2.0 GB thin versus 512.0 GB thick disk usage. These are the original wizard values, not a current VSP sizing recommendation or an allowance to under-provision the appliance.

Fresh English template-details excerpt for SP-5.0.5.0-26662, with the original package capacity values scoped as historical.

Assign a suitable VM name and inventory location, then select the approved host or cluster and resource pool. The source example uses VSP-7200c and Cluster4. Choose actual placement according to the supported VSP configuration; illustrative rows in the reconstructed figures do not describe a real inventory.

Fresh English Name and Location excerpt with historical VM name VSP-7200c and a location to select.

Fresh English host/cluster selection illustration. Cluster4 is the historical selected example; other inventory rows are illustrative.

Fresh English resource-pool selection excerpt replacing personal inventory labels.

Select the destination datastore, verify capacity and supported storage placement, and choose the supported virtual disk format. The source selects Thin Provision. That example does not establish a universal thin-provisioning requirement. Map the appliance network to the intended destination port group and verify the management network design.

Fresh English datastore selection excerpt without fabricated free-space or capacity results.

Fresh English disk-format excerpt with Thin Provision selected as in the historical example.

Fresh English network mapping: VM Network to VM Network is the source example, not a required port-group name.

Review the deployment summary before Finish. The source leaves Power on after deployment unchecked, waits for the deployment task to finish, and then starts the VM from its console. A successful OVF deployment creates the appliance VM; it does not complete SP or StoreServ initialization.

Fresh English pre-deployment summary. Finish starts the deployment; the power-on option is unchecked.

Fresh English in-progress view retaining the source 3% deployment stage, not a successful result.

Fresh English deployment-completed message, explicitly limited to the OVF deployment stage.

The original English console login excerpt is reused here in place of the wider Chinese vSphere console capture. Power on the deployed VM and wait for its console.

2. Configure the initial SP network

Use the appliance console and the authorized setup access for its actual state. The source enters the admin account on an uninitialized SP. Do not assume that a previously configured appliance accepts the same initial access; use the credentials established for that appliance. The following original English screens show the SP 5.0.5 text interface before initialization.

Original English SP console login excerpt. It shows the admin account name and no password value.

Select 1, Configure Network. Read the preparation screen and continue. Enter the approved hostname, IP address, subnet mask and gateway. The historical example uses hostname SP7200C, address 10.12.174.170, mask 255.255.252.0 and gateway 10.12.172.1. These settings belong to the source environment and must not be copied into another network without verification.

Original English SP Service Console main menu with Configure Network selected.

Original English network-configuration introduction.

Original English hostname entry: historical example SP7200C.

Original English IPv4 entry: historical example 10.12.174.170.

Original English subnet-mask entry: historical example 255.255.252.0.

Original English default-gateway entry: historical example 10.12.172.1.

The source chooses Y to validate the gateway connection, reviews the summary, and confirms with Y. Check the result rather than assuming that selecting validation proves connectivity. When Network configuration successful appears, return to the main menu and use the displayed HTTPS address for the browser setup.

Original English gateway-validation question, with Y selected in the source.

Original English network summary before confirmation; verify each field before accepting it.

Original English successful network-configuration acknowledgement and browser address https://10.12.174.170:8443.

3. Review the remote-support choice

The source optionally selects Disable Remote Support on initial SP Setup and confirms it. This is a documented source choice, not a default recommendation. HPE warns that disabling remote support affects support data, alerts and remote service functions. Apply the actual support agreement and network/data-transfer policy before changing these settings.

Original English main menu with the initial remote-support-disable option selected; do not select it automatically.

Original English confirmation question explaining remote support before disabling it.

Original English acknowledgement that remote support will be disabled during initial SP setup.

Original English main menu after the change; the option now offers to enable remote support, reflecting the source example state.

4. Initialize the Service Processor in the browser

Browse to the actual SP HTTPS address on port 8443. The source encounters a browser certificate warning. Verify that the endpoint and certificate belong to the intended appliance before proceeding through the approved local setup process, and install an appropriate trusted certificate. The English figure explains this check rather than reproducing a generic bypass instruction.

Fresh English certificate-warning explanation. The address is the historical example, and certificate verification is required.

Read the displayed end-user agreement and accept it only when appropriate. Continue from Guided Setup, then choose Setup Service Processor. The source has completed network connection at this point; SP initialization and StoreServ setup are still separate remaining steps.

Fresh English agreement prompt explanation; actual agreement text and license information are not reproduced.

Fresh English three-stage Guided Setup view with only network connection complete, followed by the SP setup action.

Same combined English Guided Setup/action illustration at the original Setup Service Processor button position.

Choose the appropriate SP setup type: a new uninitialized SP or restoration using an approved recovery file. Verify the network fields and configure the actual DNS, date/time, email and other required settings. The reconstructed network view omits the original domain and DNS server examples; blank fields mean values must be supplied where required, not that DNS should be left unconfigured.

Fresh English SP setup/network excerpt. New-SP setup is the historical example; DNS values are intentionally blank for local entry.

Set the required admin and authorized support-account credentials locally and confirm each entry. The source shows admin and hpepartner credential sections. No original password, password hint or saved masked value is reproduced. Review the support options separately; the source disables support, while the actual installation must use its approved policy.

Fresh English SP credential excerpt with empty admin and hpepartner password/confirmation fields.

Fresh English remote-support review card replacing the source settings view; it does not recommend disabling support.

Review the settings before starting setup. Continue to the progress page and inspect the actual checklist. The source first shows completed and pending tasks, then a later completed SP checklist. Resolve failed or incomplete items before the required SP reboot. The progress illustration retains only reliably established status pairs; the DNS row is omitted because its captured status is not reliably established.

Fresh English SP setup confirmation; continuing opens progress and does not itself prove completion.

Fresh English status excerpt: Configure Network completed; Configure Email and Configure Strong Password pending. Other source tasks are omitted.

Fresh English explanation of the later completed SP setup stage; StoreServ setup remains separate.

5. Reconnect and select the correct StoreServ workflow

Wait while the SP reboots and the Service Console returns to the login page. Sign in using the admin credentials assigned during SP setup. The original saved login view is replaced by an empty English form.

Fresh English Rebooting Service Processor status, without claiming the reboot has already finished.

Fresh English login form with empty fields; use the credentials assigned to the actual SP.

When no system is attached, the source opens Setup StoreServ and the guided introduction. Continue through the explanation, review the validation checks and resolve failures. Select the workflow that matches the actual array: a new uninitialized StoreServ or an already initialized StoreServ. Do not apply new-system initialization to an existing production array.

Original English StoreServ guided introduction explaining setup validation checks and error details.

Original English next-step explanation for the new-system setup flow; it is not permission to initialize an existing array.

Fresh English system-type/discovery excerpt with both workflows unselected and the serial field empty. It does not invent a discovery result.

Identify the intended array and provide the applicable system settings, date/time and authorized array credentials in the matching workflow. SP login credentials and array administrator credentials are separate. The original credential-bearing configuration views are represented by explanatory English figures rather than copied credentials or invented system identifiers.

Fresh conceptual array-credential entry illustration. Field layout is explanatory rather than a claim that every setup workflow requires these exact fields.

6. Add installation-site and support-contact information

Review the installation-site details and actual support provider. Use Add Contact to enter an authorized technical contact with the appropriate preferred language, company, email and telephone details. The original empty English installation-site page is retained; the populated personal-contact view is replaced by a blank form. Review optional analytics/vCenter configuration under its applicable requirements rather than assuming it is necessary to finish every deployment.

Original English installation-site/support-contact page before contact entry. Empty fields are shown without a saved contact.

Fresh English Add Contact form with personal details removed and empty contact fields.

Review the contact and site settings before submitting the StoreServ setup. The source uses Add and then Continue on its guided confirmation; exact button names and sequence can vary with the selected new-system or existing-system workflow.

Fresh English site/contact review illustration replacing the populated personal-information page.

Fresh English StoreServ setup confirmation. Continue starts or opens the process; it is not completion evidence.

7. Verify the actual result

Monitor the StoreServ setup checklist and investigate errors or pending items. The source first shows tasks pending and later a Guided Setup panel with all three stages complete. The final panel documents that historical setup result; it is not a new test of this installation, a host-I/O test or a proof of application recovery.

Fresh English progress explanation preserving the source pending state without inventing task results.

Fresh English reconstruction of the final source Guided Setup panel: network, SP and StoreServ setup complete.

Check the actual SP and array status, intended connectivity and support configuration before proceeding. Follow the version-matched SSMC guidance for host creation, virtual-volume provisioning and presentation as applicable. Service Console setup and storage provisioning are distinct tasks; the VSP is not evidence that those later tasks have been completed.

English references and image scope

The source already contains English console and setup figures, which are used where readable and free of credential data. An identical public English version of the protected walkthrough was not established. The matching HPE-authored 5.0.5 guide and related official 5.x references were checked; later 5.x material is not treated as a current support statement for the legacy hypervisor or as an exact replacement screenshot.