vv
Displays Virtual Volumes (VV) that are not optimal. Checks for VVs and Common Provisioning
Groups (CPG) whose State is not normal.
Format of Possible vv Exception Messages
VV vv:<vvname> "IO to this volume will fail due to no_stale_ss policy"
VV vv:<vvname> "Volume has reached snapshot space allocation limit"
VV vv:<vvname> "Volume has reached user space allocation limit"
VV vv:<vvname> "VV has expired"
VV vv:<vvname> "Detailed State: <state>" (failed or degraded)
VV cpg:<cpg> "CPG is unable to grow SA (or SD) space"
VV cpg:<cpgname> "CPG growth increment is below threshold"
vv Suggested Action
Check status with CLI commands such as showvv, showvv -d, showvv -cpg.
Troubleshooting Storage System Setup
If you are unable to access the SP setup wizard, SP, or the Storage System Setup wizard:
1. Collect the SmartStart log files. See “Collecting SmartStart Log Files” (page 72).
2. Collect the SP log files. See “Collecting Service Processor Log Files” (page 72).
3. Contact HP support and request support for your HP 3PAR StoreServ 7000 or 7000c Storage
system. See “Contacting HP Support about System Setup” (page 73).
Storage System Setup Wizard Errors
This section describes possible error messages that may display while using the Storage System
Setup Wizard.
Common error strings that appear in multiple places
• The specified system is currently in the storage system
initialization process. Only one initialization process can run at
one time.
This message displays when the wizards of two users try to initialize the same storage system
on the same SP. Only one wizard can initialize a storage system.
Two options are available when this error displays in a dialog box; you can click Retry or
Cancel. When the error does not display in a dialog box, look for another SP by serial number
or wait a while and try again later.
• Could not communicate with the server. Make sure you are currently
connected to the network.
This message displays when the client computer that is running the wizard cannot communicate
with the SP, such as when network connectivity is lost.
The error can occur for one of the following reasons:
◦ Network connectivity is lost.
◦ The SP is no longer running.
66 Troubleshooting