H9p97s.a.00 Stu - Part2

Managing HP 3PAR
StoreServ III
Student guide
(2 of 2)
Use of this material to deliver training without prior written permission from HP is prohibited.
H9P97S A.00
 Copyright 2015 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
This is an HP copyrighted work that may not be reproduced without the written permission of HP. You
may not use these materials to deliver training to any person outside of your organization without the
written permission of HP.
Microsoft®, Windows®, Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
All other product names mentioned herein may be trademarks of their respective companies.
Export Compliance Agreement
Export Requirements. You may not export or re-export products subject to this agreement in violation of
any applicable laws or regulations.
Without limiting the generality of the foregoing, products subject to this agreement may not be
exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries under
U.S. economic embargo and/or sanction including the following countries:
Cuba, Iran, North Korea, Sudan and Syria.
This list is subject to change.
In addition, products subject to this agreement may not be exported, re-exported, or otherwise
transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List; U.S.
Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department
Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to parties
directly or indirectly involved in the development or production of nuclear, chemical, or biological
weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export
Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the financing,
commission or support of terrorist activities.
By accepting this agreement you confirm that you are not located in (or a national or resident of) any
country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce Denied
Persons List, Entity List, US State Department Debarred Parties List or Treasury Department Designated
Nationals exclusion list; not directly or indirectly involved in the development or production of nuclear,
chemical, biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S.
Export Administration Regulations (15 CFR 744), and not directly or indirectly involved in the financing,
commission or support of terrorist activities.
Printed in US
Managing HP 3PAR StoreServ III

Student guide (2 of 2)
May 2015
Contents
Module 6 – Upgrading HP 3PAR .............................................................................................. 6-1

Module objectives ...................................................................................................... 6-2
Recommended hardware configuration steps .......................................................... 6-3
Adding new components to existing system ............................................................ 6-4
Controller node upgrade ............................................................................................ 6-5
Disk enclosure upgrade ............................................................................................. 6-6
Servicing the storage system .................................................................................... 6-7
Service Processor Onsite Customer Care (SPOCC) .................................................... 6-8
Types of CSR............................................................................................................... 6-9
Getting recommended actions ................................................................................6-10
Repair/replace disk procedures ...............................................................................6-11
Upgrading the storage system hardware................................................................6-16
Configuration general best practices ......................................................................6-17
Configuration general best practices ......................................................................6-18
Recommended configuration rules .........................................................................6-19
Upgrade disk drives – SFF drives .............................................................................6-20
Upgrade disk drives – LFF drives .............................................................................6-21
Upgrade disk drives – Mixed types ..........................................................................6-22
Disk drive upgrade ...................................................................................................6-23
7000 upgrade best practice scenarios ....................................................................6-28
HA disk......................................................................................................................6-29
HA disk......................................................................................................................6-30
HA disk......................................................................................................................6-31
HA enclosure ............................................................................................................6-32
HA enclosure ............................................................................................................6-33
HA enclosure ............................................................................................................6-34
7000 minimum upgrade scenarios ..........................................................................6-35
HA disk......................................................................................................................6-36
HA disk......................................................................................................................6-37
HA disk......................................................................................................................6-38
HA enclosure ............................................................................................................6-39
HA enclosure ............................................................................................................6-40
HA enclosure ............................................................................................................6-41
Other scenarios to consider .....................................................................................6-42
Larger systems and set sizes/RAID levels ...............................................................6-43
Tiered systems and Adaptive Optimization ............................................................6-45
All flash array considerations ..................................................................................6-46
Mixed-drive capacities and speeds ..........................................................................6-47
Upgrading the storage system software – Pre-planning........................................6-48
3PAR OS upgrade .....................................................................................................6-49
3PAR OS upgrade .....................................................................................................6-50
3PAR OS upgrade .....................................................................................................6-51
3PAR OS upgrade .....................................................................................................6-52
H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. i
Planning information for online HP 3PAR OS upgrades ..........................................6-53

Online upgrade general guidelines ..........................................................................6-54
Online upgrade host configuration guidelines (1 of 3) ...........................................6-55
HP 3PAR StoreServ storage configuration guidelines ............................................6-58
Remote versus local methods for an HP 3PAR OS upgrade ....................................6-59
Upgrading the storage system software – Upgrade ...............................................6-60
Supported update types and paths .........................................................................6-61
Preinstallation requirements ..................................................................................6-62
Pre-update tasks .....................................................................................................6-63
Installing the HP 3PAR OS ........................................................................................6-64
Learning check .........................................................................................................6-71
Module 7 – Alerts .................................................................................................................... 7-1

Module objectives ...................................................................................................... 7-2
3PAR events and alerts .............................................................................................. 7-3
Alerts overview .......................................................................................................... 7-4
Alert message codes .................................................................................................. 7-5
Sample 3PAR OS message ......................................................................................... 7-6
Viewing alerts using the InForm GUI.......................................................................... 7-7
Responding to 3PAR alerts ........................................................................................ 7-8
Managing alerts ......................................................................................................... 7-9
Viewing the alert summary......................................................................................7-10
Viewing alerts for connected systems ....................................................................7-11
Removing system alerts ..........................................................................................7-12
Managing alerts with the CLI ...................................................................................7-13
Managing alerts with the CLI ...................................................................................7-14
Setting system alerts ...............................................................................................7-16
Managing events ......................................................................................................7-17
Monitoring and managing the event log .................................................................7-18
Viewing events .........................................................................................................7-19
Filtering events ........................................................................................................7-20
Monitoring and managing event log operations (CLI) .............................................7-21
External System Reporter performance alerts .......................................................7-22
External System Reporter: Email alerts (1 of 2)......................................................7-23
External System Reporter: Email alerts (2 of 2)......................................................7-24
On-Node System Reporter performance alerts ......................................................7-25
On-Node SR: Performance alerts ............................................................................7-26
ii © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00
Student Guide Contents

Troubleshooting ......................................................................................................7-42
SNMP ........................................................................................................................7-43
About SNMP..............................................................................................................7-44
SNMP managers and HP 3PAR SNMP agent ............................................................7-45
Supported MIBs ........................................................................................................7-47
MIB-II ........................................................................................................................ 7-48
HP 3PAR MIB .............................................................................................................7-49
alertNotify traps example .......................................................................................7-50
alertNotify traps – State change .............................................................................7-51
alertNotify traps – State change example ..............................................................7-52
Registering an SNMP manager ................................................................................7-53
Editing an SNMP manager........................................................................................7-54
View and remove SNMP managers ..........................................................................7-55
Agent community strings ........................................................................................7-56
Testing SNMP managers ..........................................................................................7-57
Creating SNMPv3 users ............................................................................................7-58
Viewing and removing SNMPv3 users .....................................................................7-59
SNMP infrastructure and summary .........................................................................7-60
HP 3PAR CIM API .......................................................................................................7-61
Overview ..................................................................................................................7-62
About SMI-S..............................................................................................................7-63
CIM standard ............................................................................................................7-65
Service processor – Local notification service ........................................................7-67
Introduction .............................................................................................................7-68
Local notification types ...........................................................................................7-69
Setting up local notification.....................................................................................7-70
Enabling local notification access ...........................................................................7-71
Using the Notification Maintenance Utilities menu .................................................7-72
Configuring Sendmail...............................................................................................7-73
Editing the Sites table ..............................................................................................7-74
Editing the Product table .........................................................................................7-75
Predefining symptoms ............................................................................................7-76
Using prime shift patterns and exceptions .............................................................7-77
Enabling and disabling RAP forwarding ..................................................................7-78
Managing user profiles ............................................................................................7-79
Managing local notification records ........................................................................7-80
Learning check .........................................................................................................7-82
Training from HP Education Services .....................................................................7-83
H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. iii

iv © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Managing HP 3PAR StoreServ III Upgrading HP 3PAR
H9P97S A.00 6–1

H9P97S A.00 6–2

H9P97S A.00 6–3

NOTICE: When performing any upgrade while the customer is concurrently using the system, exercise
extreme caution because any incorrect action taken during an upgrade might cause the system to fail. Before
performing any upgrade or expansion, verify with the system administrator if a complete backup of all data
on the storage system has been performed.
Make sure that the system is fully operationally and does not have any failed components. Use the
checkhealth command to verify the operational state. The checkhealth command checks the status of
system hardware and software components, and reports any issues.
checkhealth [<options> | <component>]
[options]
–list Lists all components that checkhealth can be run on.
–quiet Does not display which component is currently being checked.
–detail Displays detailed information regarding the status of the system.
<component> indicates the component to check. Use the -list option to get the list of components (alert,
cage, date, ld, license, network, node, pd, pdch, port, rc, snmp, task, vlun, vv).
CAUTION: Storage systems are susceptible to failure caused by electrostatic discharge (ESD). Electrostatic
charges can accumulate on people and furniture because of direct contact with floor coverings or movement
while in contact with furniture coverings. Discharge of static electricity to a metal surface on server cabinets
can interfere with system operation and cause discomfort to anyone who comes in contact with it. To prevent
damage from ESD, you must wear an ESD wrist-grounding strap during installation and maintenance of the
storage system. Place all components during removal and replacement on an ESD-safe work surface.
H9P97S A.00 6–4

H9P97S A.00 6–5

H9P97S A.00 6–6

CAUTION:
• Before servicing any component in the storage system, prepare a safe work surface, free of
electrostatic discharge (ESD), by placing an antistatic mat on the floor or table near the storage
system
• Attach the ground lead of the mat to an unpainted surface of the rack
• Always use the wrist-grounding strap provided with the storage system
• Attach the grounding strap clip directly to an unpainted surface of the rack
H9P97S A.00 6–7

• Use SPOCC to access Guided Maintenance or Service Processor Maintenance (SPMAINT) in the CLI, where you perform
various administrative and diagnostic tasks to support both the storage system and the SP.
• To open SPOCC, enter the SP IP address in a web browser and enter your user name and password.
To access SPMAINT from SPOCC:

1. On the left side of the SPOCC homepage, click Support
2. On the Service Processor - Support page, under Service Processor, click SPMAINT on the Web in the Action
column
3. Select option 7, Interactive CLI for a StoreServ and then select the desired system
Use SPMAINT if you are servicing a storage system component or when you need to run a CLI command
H9P97S A.00 6–8

NOTE
In some instances, remote support by an HP Authorized Service Provider might be needed to fully diagnose a part failure.
Parts-only warranty service
• Your HP Limited Warranty might include a parts-only warranty service
• Under the terms of parts-only warranty service, HP provides replacement parts free of charge
• For parts-only warranty service, customer self-repair (CSR) part replacement is mandatory
• If you ask HP to replace these parts, you are charged for the travel and labor costs of this service
Identifying a replaceable part
• Parts have a nine-character spare part number on the label.
• For some spare parts, the part number is available in the system.
• Alternatively, the HP call center can assist in identifying the correct spare part number.
H9P97S A.00 6–9

1. At the HP Storage Systems Guided Troubleshooting website, follow the link for your product
2. At the bottom of the HP 3PAR product page, click the link for HP 3PAR Alert Messages.
3. At the bottom of the Alert Messages page, choose the correct message code series based on the first four
characters of the alert message code.
4. Choose the next digit in the code to narrow the message code series.
5. On the next page, select the message code that matches the one that appeared in the alert.
6. The next page shows the message type based on the message code selected and provides a link to the suggested
action. Follow the link.
7. On the suggested actions page, scroll through the list to find the message state listed in the alert message. The
recommended action is listed next to the message state.
H9P97S A.00 6 – 10
WARNING!
• If the StoreServ is enabled with HP 3PAR Data Encryption feature, only use the self-encrypting drives (SED).
• Using a non-self-encrypting drive can cause errors during the repair process.
CAUTION
• If you require more than 10 minutes to replace a disk drive, install a disk drive blank cover to prevent overheating
while you are working.
• To avoid damage to hardware and the loss of data, never remove a disk drive without confirming that the disk fault
LED is lit.
H9P97S A.00 6 – 11
Repairing a disk drive—Identifying a disk drive

1. Under the Systems tree in the left panel of HP 3PAR Management Console, select the storage system to be serviced.
The Summary tab should appear, indicating the failed drive.
2. On the Summary tab, select the Failed link in the Physical Disk row next to the red X icon.
WARNING!
• The physical disks might indicate “degraded,” which means that the disk drive is not yet ready for replacement.
• It might take several hours for the data to be vacated; do not proceed until the status is “failed.”
• Removing the failed drive before all the data is vacated causes loss of data.
3. A filtered table appears, showing only failed or degraded disk drives
CAUTION:
If more than one disk drive is failed or degraded, contact your authorized service provider to determine whether the
repair can be done in a safe manner, preventing downtime or data loss.
H9P97S A.00 6 – 12
Repairing a disk drive—Disk drive location

1. Select the Cage link for the failed drive.
2. Select the Locate icon in the top toolbar of the Management Console.
6. In the Locate Cage dialog box, enter an appropriate time to allow service personnel to view the LED
status of the drive enclosure (cage).
An icon with a flashing LED will appear next to the cage, which flashes all drives in this cage except the
failed drive.
7. Replace a disk.
8. Use checkhealth command to verify the system is working properly
H9P97S A.00 6 – 13
Repairing a disk drive—Removing a disk
1. Pinch the handle latch to release the handle into open position.
2. Pull the handle away from the enclosure and wait 30 seconds.
3. Slowly slide the disk drive out of the enclosure and set aside
4. Remove the replacement disk drive from its packaging. To reinstall a new disk drive, see the next slide.
Removing a 2.5 inch disk Removing a 3.5 inch disk

Repairing a disk drive—Installing a disk drive
1. Press the handle latch to open the handle.

2. Insert the disk drive into the enclosure with the handle opened. Slide the disk drive into the enclosure
until it engages. Push firmly until it clicks.
3. Observe the newly installed disk drive for 60 seconds to verify the amber LED turns off and remains off
for 60 seconds.
Installing a 2.5 inch disk Installing a 3.5 inch disk

CAUTION:
Blank disk drive carriers are provided and must be used if all slots in the enclosure are not filled with disk drives.
To avoid potential damage to equipment and loss of data, handle disk drives carefully.
H9P97S A.00 6 – 14
Repairing a disk drive—Verifying disk drives
1. Verify the disk drive has been successfully replaced.

2. Display the physical disks to monitor. Open the system in the Systems tab and select Physical Disks.
3. The new drive displays in the same position as the failed drive, and the state is listed as normal.
4. Open a CLI session. Enter the checkhealth command to verify the system is working properly.
Notes:
To sort the disks, select the State column header.
Until data has been restored, the original disk drive will display as failed, and the replacement disk drive will
display as degraded.
The drive that was replaced continues to display in the table as failed until the disk rebuild is complete, which
might take several hours. When the process is complete, the failed drive is dismissed and dropped from the
display.
H9P97S A.00 6 – 15
H9P97S A.00 6 – 16
H9P97S A.00 6 – 17
H9P97S A.00 6 – 18
H9P97S A.00 6 – 19
• For the HP M6710 Drive Enclosure, drives must be added in identical pairs, starting from slot 0 on the left and filling to
the right, leaving no empty slots between drives.
• The best practice for installing or upgrading a system is to add the same number of identical drives to every drive
enclosure in the system, with a minimum of three disk drive pairs in each drive enclosure.
• This ensures a balanced workload for the system.
H9P97S A.00 6 – 20
• For the HP M6720 Drive Enclosure, drives must be added by pairs of the same drive type (NL, SAS, or SSD) with a
minimum increment of four drives, starting at the bottom of a column, leaving no empty slots between drives in the
column.
• Columns of drives must be of the same type and rotational speed. You can have empty columns between columns
containing drives; different columns do not have to contain the same number of drives.
• Start adding drives in the left column, bottom to top, and then continue filling columns from left to right beginning at
the bottom of the column.
• The best practice when installing or upgrading a system is to add the same number of identical drives to every drive
enclosure in the system, with a minimum of two drives added to each enclosure.
• An all-LFF drive configuration is permitted, leaving the storage base enclosure empty.
H9P97S A.00 6 – 21
H9P97S A.00 6 – 22
Disk drive upgrade - GUI
Checking initial status

Under Systems, select Physical Disks, and in the right pane, select the Physical Disks tab
H9P97S A.00 6 – 23
Inserting hard drives and checking status

Two hard drives are added to each of the three enclosures
The display refreshes periodically, and you should see the inserted hard drives as New in the State column. They are
ready to be admitted into the system, which occurs automatically.
Within six minutes (depending on the system load and the size of the upgrade), the state of the new hard
drives changes to Normal, and the system starts to initialize the chunklets to ready for use. Output indicates
that each of the six added hard drives still have normal and spare chunklets to be initialized.
Checking progress
On the Physical Disks tab, in the drop-down list, select Chunklet Usage.
H9P97S A.00 6 – 24
Completing the upgrade

In the Systems pane, select StorageSystem - Physical Disks, and then select the Physical Disks tab
On the Physical Disks tab, in the drop-down list, select Chunklet Usage
NOTE: The system can be used normally, but newly added capacity must be initialized before it can
be allocated.
H9P97S A.00 6 – 25
Disk drive upgrade – CLI

Check initial status
Enter the showpd command (remember to log your session):
Installation and check

Insert disk drives. Enter the showpd command. Each of the inserted disk drives has a new state and is ready
to be admitted into the system.
H9P97S A.00 6 – 26
Check progress
Enter the showpd -c command to check chunklet initialization status:
Upgrade completion
When chunklet initialization is complete, enter the showpd -c command to display the available capacity:
H9P97S A.00 6 – 27
H9P97S A.00 6 – 28
• This is a 2-node 7200c system with 1 enclosure running R1 and R5 3+1 with 8 installed drives.
• In this instance, 8 drives or an increment in multiples of 8 drives would be the best practice, depending on the capacity
needed go to 16 or 24 drives.
− 8 disks are recommended so each of 2 nodes would have a full set size (2x[3+1]). For SSZ=5, 10 disks would be
recommended
• You will be able to create new LD space as needed and, in the end, have the best capacity utilization possible with no
performance implications.
The lighter drives are the originals and the darker drives are the upgrade
drives.
H9P97S A.00 6 – 29
needed go to 32 or 40 drives plus the additional enclosure.
performance implications.
The lighter components are the originals and the darker components are the upgrade
components.
H9P97S A.00 6 – 30
• In this instance, matching the existing node pair would be the best practice, depending on the capacity needed go to
48 drives.
performance implications. You will also maintain balance across the node pairs.
Upg NP 2:3
The lighter components are the originals and the darker/blue components are the
upgrades.
H9P97S A.00 6 – 31
• This is a 2-node 7200c system with 4 enclosures running R1 and R5 3+1 with 16 installed drives.
needed go to 24 or 32 drives.
performance implications. You will also maintain the HA enclosure.
The lighter drives are the originals and the darker drives are the upgrade
drives.
H9P97S A.00 6 – 32
• In this instance, a new enclosure with 24 drives and a change to R5 4 + 1 would be the best practice.
• You will need to have workspace on the existing enclosures to run tunesys.
• Staying with 3 + 1 and letting tunesys balance across 5 enclosures or adding 4 more enclosures with fewer drives are
other good options.
components.
H9P97S A.00 6 – 33
• In this instance, matching the existing node pair would be the best practice.
− The advantage of this approach is that capacity utilization or timeframe concerns do not come into play while
scheduling or completing tunesys.
performance implications. You will also maintain balance across the node pairs.
Upg
NP
DC 3 DC 2 DC 1
upgrades.
H9P97S A.00 6 – 34
H9P97S A.00 6 – 35
• This is a 2-node 7200c system with 1 enclosure running R1 and R5 3+1 with 8 installed drives. In this instance, 2 drives
or a increment of 2 drives would be supported, depending on the capacity needed go to 10 to 24 drives in 2-drive
increments.
• With this approach, you can support smaller upgrade increments.
• When you run tunesys, you will need to have space on 4 drives per node to be able to create new LD space as needed
and, in the end, have good capacity utilization with no performance implications.
The lighter drives are the originals and the darker drives are the upgrade drives.
H9P97S A.00 6 – 36
• In this instance, 2 drives or a increment of 2 drives plus the additional enclosure would be the minimum upgrade,
depending on the capacity needed go to 28 or 48 drives in increments of 2.
• With this approach, you can support smaller upgrade increments.
• When you run tunesys, you will need to have space on 4 drives per node to be able to create new LD space as needed
and, in the end, have good capacity utilization with no performance implications.
The lighter components are the originals and the darker components are the upgrades.
H9P97S A.00 6 – 37
• In this instance, matching the existing node pair would be the minimum, depending on the capacity needed go to 48
drives.
− With a configuration of this size, it is too easy to create a large performance imbalance.
• The advantage of this approach is that no matter what the current capacity utilization or timeframe allowed to
schedule or complete tunesys, you will be able to create new LD space as needed and, in the end, have the best
capacity utilization possible with no performance implications and balance across the node pairs.
• With smaller systems, or for all SSD systems, it is easier to create an imbalance with more negative impact. With larger
systems that have, say, 200 drives behind one node pair and 100 drives behind the other, the imbalance would be less
of a impact, especially with some extra management effort.
upgrades.
H9P97S A.00 6 – 38
• Because of the HA enclosure requirement in this instance, the best practice and the minimum upgrade are the same.
• In this instance, 8 drives or a increment of 8 drives across the enclosures would be the minimum, depending on the
capacity needed go to 24 or 32 drives.
schedule/complete tunesys you will be able to create new LD space as needed maintaining HA-Enclosure and, in the
end, have the best capacity utilization possible with no performance implications.
The lighter drives are the originals and the darker drives are the upgrade drives.
H9P97S A.00 6 – 39
• In this instance, a new enclosure with 24 drives and a change to R5 4 + 1 would be the best practice.
• You will need to have workspace on the existing enclosures to run tunesys.
• Staying with 3 + 1 and letting tunesys balance across 5 enclosures with fewer than 24 drives in the fifth enclosure or
adding 4 more enclosures with fewer drives are other good options.
components.
H9P97S A.00 6 – 40
• This is a 2-node 7400c system with 4 enclosures running R1 and R5 3+1 with 64 installed drives
• In this instance, matching the existing node pair would be the minimum, depending on the capacity needed go to
higher drive counts in 16-drive increments
− With a configuration of this size, it is too easy to create a large performance imbalance
schedule or complete tunesys, you will be able to create new LD space as needed and, in the end, have the best
capacity utilization possible with balance across the node pairs and no performance implications.
upgrades.
H9P97S A.00 6 – 41
H9P97S A.00 6 – 42
• If you are adding a new drive type to the system as part of a upgrade you have to add the minimum needed for that
drive type in a system. This is 8 for SSD or FC drives and 12 for NL drives.
• For HA enclosure support with R6 set sizes, you can divide the set size by 2 to determine the required enclosure count.
As a example R6 6 + 2 only requires 4 enclosures per node pair.
• In the best practice sections, R5 3 + 1 was used to illustrate the examples.
− For a different set size like R6 6 + 2, instead of adding drives in increments of 8 you would use increments of 16.
− After the initial quantity of drives needed for a drive tier is in place, the minimum scenarios stay the same.
• After tuneld is run, a new row size will be available. Before and after upgrade the rows in each ld could have every disk
on that node included.
• Earlier in the best practice and minimum upgrade scenarios when additional node pairs were being added, the nodes
were kept in balance.
− This is not to say that there are no scenarios where running unbalanced node pairs is acceptable for time periods as
systems grow over time.
− No standard amount of imbalance is supported. It depends on the configuration and the workloads being supported.
− As an example, a system with only 16 drives per node pair can easily have a large imbalance that causes issues,
while a system with 200 drives behind 1 node pair and 100 drives behind the other node pair will be fine.
• With large systems, you can work with multiple groups of enclosures per node pair to maintain best practice with
smaller upgrade increments.
• See the example on the next slide.
H9P97S A.00 6 – 43
Larger systems before upgrade
Larger systems after upgrade
H9P97S A.00 6 – 44
H9P97S A.00 6 – 45
• For 4-node systems with SSDs, it is especially important that the number and capacities of the SSDs be evenly
distributed between node pairs.
− The number of SSDs and the total capacities of those SSDs should be balanced.
− This is due to the fact that a small amount of difference in drive count or capacity can make a large imbalance which
can cause the system to not deliver the full performance of the hardware.
• The SFF and LFF SSDs allow you to create SSD volumes that stripe across SFF and LFF enclosures.
• Mixing same type drives of different capacities leads to depletion of extra capacity in creating additional spare space
capacity.
• It is best to use same capacity drives, but different capacity drives can be mixed. If mixing capacities best to add in
increments of the set size per node pair.
− Because of the increased cost per GB of SSD space, it is best to make the most utilization of these drives.
• All the best practice and minimum scenarios for upgrades based on the set size remain the same, except you must be
careful when adding the first cMLC drives to a system with only eMLC drives. Differences in performance can occur
because of the differences in write performance.
You can read more about different MLC technologies below:

http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/cMLC-SSDs-in-HP-3PAR-StoreServ-Embrace-with-
confidence/ba-p/176624#.VSUbCJPsx-5
H9P97S A.00 6 – 46
• When you have mixed-drive capacities in the same tier sharing the same CPG characteristics, you have two choices:
− Stay with one CPG.
− Your other option is to create a second CPG with a disk filter for the larger drives only. For volumes that have lower
performance requirements, use the CPG with the disk filter, saving the wider stripe for the volumes that have high-
performance requirements. This does require an extra decision point when provisioning volumes.
• If mixing drives in the same tier that have different speeds, such as 10K and 15K SAS drives, you should assume that a
volume will get the 10K performance.
• When mixing different SSD drives, be aware that the different capacities can have more impact because of the smaller
drive counts and the impact to sparing levels.
• When mixing different SSD drives that are eMLC and cMLC, be aware of the delta in write performance between these
drive types and how it could affect the existing performance of volumes currently only on eMLC drives.
− It might be better to stay with all eMLC drives or have separate CPGs, depending on the application workloads being
supported.
− The smaller cMLC drives are more of a issue than the larger ones.
H9P97S A.00 6 – 47
H9P97S A.00 6 – 48
Before you begin with 3PAR OS upgrade, you should always check the respective HP 3PAR Operating System Upgrade
Pre-Planning Guide. It includes information about:
• An overview of the online and offline upgrade processes for the HP 3PAR OS
• Prerequisites for online upgrades
• Guidelines for online upgrades
• Planning information needed for online upgrades
• Veritas Dynamic MultiPathing (DMP) prerequisites for online upgrades
• Remote versus local methods of upgrading
Notes
The HP 3PAR StoreServ Storage supports two different methods for upgrading the HP 3PAR OS: online and offline. The
upgrades can be performed with a service representative on-site or remotely (from HP). Remote upgrades require that
remote operations are available.
See the HP Storage Single Point of Connectivity Knowledge (SPOCK) at http://www.hp.com/storage/spock for HP 3PAR
support matrixes for HP 3PAR OS versions supported by each array model.
HP recommends updating host drivers to a supported level of the targeted HP 3PAR OS upgrade version before
attempting an online upgrade. For this information, see the HP SPOCK website. These documents are provided to help
you set up hosts with HP supported configuration information.
In addition to this planning document, see the HP 3PAR host OS implementation guides available from the HP Storage
Information Library at http://www.hp.com/go/storage/doc.
H9P97S A.00 6 – 49
H9P97S A.00 6 – 50
H9P97S A.00 6 – 51
Supported upgrade types example for 3PAR OS 3.2.1 MU1
NOTICE
For an upgrade from HP 3PAR OS 3.1.1 MU1 to HP 3PAR OS 3.1.2 GA or later, it is no longer necessary to stop HP 3PAR
Remote Copy groups when doing an online upgrade.
For an upgrade from HP 3PAR OS 3.1.1 GA to a later version, Remote Copy groups must be stopped.
H9P97S A.00 6 – 52
• The host connectivity environment must adhere to the qualified and supported environments.
• For more information, see the interoperability information on the HP SPOCK website
• HP service representatives will request this information for review before performing an online upgrade. Relevant
details include:
− Host platform
− Architecture (for example, SPARC/x86)
− Operating system (version and patch level)
− Host multipath software
− HBA and CNA
− Switch
− Information on host software provided by HP
Examples include:
HP 3PAR Recovery Manager (SQL, Exchange, Oracle)
HP 3PAR VSS Provider
HP 3PAR MPIO for Microsoft Windows
HP 3PAR ODM Definition for IBM AIX
HP 3PAR System Reporter
• In addition to verifying that the driver and firmware levels match the information in HP SPOCK, host configuration
settings might be needed as documented in the HP 3PAR host OS implementation guides. Verify these settings before
performing an online upgrade.
H9P97S A.00 6 – 53
• Do not perform hardware and configuration changes on the HP 3PAR StoreServ Storage during the update.
− For example, software operations (such as servicemag, createvv, or use of the HP 3PAR StoreServ Storage tuner
commands) and hardware operations (such as adding or removing drives and cages) are prohibited during the online
update process.
− All logical disk growth operations for common provisioning groups continue uninterrupted as under normal
operation.
• Host and environment changes are not allowed during an online upgrade (for example, restarting, applying patches, or
rezoning switches).
− The upgrade software checks for the existence of hosts before and after each step, and if host connections do not
reappear after each step, the upgrade process reverts to the original level.
• Any automated processes that communicate with the HP 3PAR StoreServ Storage management interface (scripting)
must be stopped before performing an online upgrade.
• Online upgrades should be scheduled and performed during periods of low I/O activity.
− System resources are placed offline to be upgraded, system utilization must be lower than 50% for each node and
I/O port.
H9P97S A.00 6 – 54
H9P97S A.00 6 – 55
• A host definition must not contain initiators from multiple hosts. For example, host cluster configurations must use a
separate host definition for each host in the host cluster.
• Stop all system administration activities during an HP 3PAR OS online upgrade.
− Complete or stop all active tasks before proceeding.
− Stop any automated administration scripts such as Recovery Manager and VSS Provider for Microsoft Windows.
• iSCSI hosts must have active I/O on all paths during the upgrade.
• The upgrade process restarts nodes and checks that all hosts are reconnected after each node restarts.
− The upgrade will not advance until all hosts re-establish connection.
− An idle iSCSI host will not reconnect; it is important to have I/O on all paths during the upgrade.
• The recovery manager for Oracle, SQL, Exchange or VMware might require a newer version to be compatible to HP
3PAR OS 3.1.1 or later. For interoperability information, see the HP SPOCK website.
• An upgraded CLI client for HP 3PAR OS 3.1.1 MU1 or later must be installed on the recovery manager host. See the HP
SPOCK website.
H9P97S A.00 6 – 56
• Verify compatibility of any host third-party software to the HP 3PAR OS release.

• The HP 3PAR System Reporter requires an upgrade to be compatible with HP 3PAR OS 3.1.x.
• When you upgrade the HP 3PAR StoreServ Storage to HP 3PAR OS 3.1.x, upgrade the HP 3PAR System Reporter
application compatible with 3.1.x with the bundled HP 3PAR System Reporter CLI Remote Client. (See the HP SPOCK
website.)
• The HP 3PAR Management Console is generally compatible with all HP 3PAR OS 3.1.1, 3.1.2, and 3.1.3 MU1 versions.
For the latest features and fixes, you should upgrade to the current HP 3PAR Management Console release.
• Always check the HP 3PAR Operating System Upgrade Pre-Planning Guide for special notes on Remote Copy, CLX, Peer
Persistence, and possible Host Persona changes.
• also verify guidelines for respective operating systems. You can find them in the HP 3PAR Operating System Upgrade
Pre-Planning Guide.
H9P97S A.00 6 – 57
• The HP 3PAR StoreServ Storage must be in a “healthy” state (with no failed or degraded physical disks, cages, FCALs,
nodes, and so on).
• The HP 3PAR OS upgrade software performs an automated check and, if the system is not in a healthy condition,
causes the upgrade to fail.
• HP 3PAR software applications running on the HP 3PAR StoreServ Storage must be shut down.
• Ensure that no HP 3PAR Virtual Copy promotes are in progress.
− To confirm, check that no volumes are in the started, cpp state.
− If any promotes are in progress, wait until the promote finishes to begin the online upgrade.
• Verify all the HP 3PAR Remote Copy guidelines in the HP 3PAR Operating System Upgrade Pre-Planning Guide.
H9P97S A.00 6 – 58
Remote HP 3PAR OS upgrades

• Remote HP 3PAR OS upgrades are achieved by using HP Remote Operations Service Tools (RemOps) (for example, by
Ethernet or modem).
• The process used for remote HP 3PAR OS upgrades depends on the connectivity model allowed for remote upgrades.
There are two connectivity models:
− Ethernet RemOps—Service processor software updates can be downloaded, staged, and performed remotely
through a secure channel.
− Temporary RemOps—In some cases, customers will temporarily open up connectivity to the service processor for
remote operations for software updates. If temporary remote operations access can be granted, we can perform the
update remotely.
Local HP 3PAR OS upgrades
• Local HP 3PAR OS upgrades are achieved by using an on-site service representative to perform the upgrade.
• Typically, local HP 3PAR OS upgrades are performed when there is no remote connection to the service processor.
• Additionally, a local HP 3PAR OS upgrade can be combined with other on-site activities, such as hardware upgrades or
maintenance.
H9P97S A.00 6 – 59
H9P97S A.00 6 – 60
H9P97S A.00 6 – 61
The service processor (SP) must be updated to the required SP software.

To verify the level of SP software running on the SP for the system you are updating, log on to the SPMAINT
utility to display the SP level:
1. Connect to the SP.
2. From the SPMAINT main menu, enter =1.1 (Display SP Version).
3. Verify that the SP version entry displays SP-4.3.0.GA-17 or later.
If the SP software level does not meet the requirements for this HP 3PAR OS update, you must
update the SP software before continuing with the HP 3PAR OS update installation.
4. From the SPMAINT main menu, enter =1.13 (Display SP Status). Save the SP status output.
You will need this output to compare it with the post upgrade SP status after you install the OS.
H9P97S A.00 6 – 62
To verify the HP 3PAR OS level currently running on the storage system:

1. Start a CLI session from the SPMAINT main menu, enter: =7 and then press Enter
2. Select the desired storage system (StoreServ)
3. To display the HP 3PAR OS version, patch information, and the version numbers of other system components,
enter: showversion -a -b
4. Enter exit and then press Enter to return to the SPMAINT main menu
To start a health check:

1. From the SPMAINT main menu, enter: =4.4 and then press Enter
2. Enter the number corresponding to the storage system (StoreServ) you want to run the Health Check on and press
Enter
3. Enter y to retrieve and transfer the check health data and press Enter
4. After the health check completes gathering the data, the SP displays a list of files to view
5. Review and correct any exceptions before performing an HP 3PAR OS update
H9P97S A.00 6 – 63
Installing the HP 3PAR OS onto the SP using the CD
1. Insert the HP 3PAR OS 3.2.1 Software CD into the SP media drive.

2. From the SPMAINT main menu, enter: =1.16.2 (Update SP Software Revision).
3. Enter the number corresponding to CDROM.
4. After the message “Stage successfully completed” appears, press Enter to return to the SPMAINT main menu.
5. Enter: =1.1 (Display SP Version)
6. Verify that the HP 3PAR OS release (3.2.1) entry displays 3.2.1.46–GA.
7. Enter: =1.13 (Display SP status)
8. Compare the post-upgrade SP processes with the pre-upgrade SP processes listed before you applied the OS. For
an example of the basic list, see the Example of Basic SP Processes table in the HP 3PAR OS 3.x.x Upgrade
Instructions document.
If the basic SP processes are running, you can now install the OS on the storage system.
H9P97S A.00 6 – 64
Updating the HP 3PAR OS online
Performing an online update requires extensive planning. Review the HP 3PAR Upgrade Pre-Planning Guide before
performing an online update.
The online update checks the HP 3PAR OS versions for update compatibility requirements and installs any required
patches.
The update script is interactive and requires user input before performing the update.
1. From the SPMAINT main menu, enter =4.7.3 and select the storage system to be upgraded.
2. Select the appropriate option for Simple Upgrade or Advanced Upgrade, and then press Enter.
• HP recommends that Advanced Upgrade be used only by qualified technicians authorized by HP to upgrade
storage system software.
3. Select the new HP 3PAR OS version to use to update the system, select menu option for 3.2.1.46-GA, and press
Enter. To proceed with the update, enter y and enter the five digit number when prompted.
4. The online update tests run and display the results.
5. If any tests fail, you must enter the displayed five-digit number to confirm and continue.
NOTICE: Any test failure must be corrected before proceeding with the HP 3PAR OS upgrade. Bypassing any test
error is not recommended, and should only be done if the test results, and any potential impact on the system
upgrade and hosts, is clearly understood and acknowledged.
6. Read all prompts. Answer yes at the final prompt to begin the update process.
NOTICE: After you answer yes at the final prompt, you cannot stop the update process.
7. After the update process is completed, press Enter to return to the SPmaint menu. Verify the health of
the storage system.
8. Start a CLI session from the SPMAINT main menu. To verify that all nodes are in an OK state and
InCluster, enter the shownode command.
H9P97S A.00 6 – 65
9. Enter the showversion -a -b command to verify the system is running HP 3PAR OS 3.2.1.46.
10. Enter exit and then press Enter to return to the SPMAINT main menu.
11. Wait at least for five minutes before running the system health check process to ensure that the
upgrade fully completes all associated tasks.
12. Post update task is run automatically after the upgrade for customer users on StoreServ 7000 series.
For the other storage systems, post-update tasks are to be run manually. Check the status of post-
update task details in the upgrade log.
H9P97S A.00 6 – 66
Updating the HP 3PAR OS offline
• Verify all pre-planning tasks are completed before proceeding with the offline update.
• The offline update checks the HP 3PAR OS versions for update compatibility requirements and installs any required
patches.
• The update script is interactive and requires user input before performing the update.
• This is an offline update. All nodes are updated and then rebooted at the same time.
NOTICE: No host I/O activity is permitted during an offline update.
1. To start a CLI session from the SPMAINT main menu, enter 7 and press Enter.
2. To verify that the host is inactive, enter statport -host -ni. There should be no host port entries in the list.
3. To verify that physical copies are not in progress, enter the showtask –all command.
4. To return to the SPMAINT main menu, enter the exit command.

a. Enter =4.5 and select the storage system (StoreServ) to reboot.
b. Enter a to reboot all controller nodes and press Enter.
c. Enter y to confirm system reboot and press Enter.
d. Enter y to stop all I/O and reboot the system and press Enter.
5. After the system successfully reboots, enter 7 and press Enter to start a CLI session from the SPMAINT
main menu.
6. Enter the statport -host -ni command to verify the host is inactive. Host ports should not be
listed.
7. Enter exit and press Enter to exit the interactive CLI and return to SPMAINT main menu to begin an
HP 3PAR OS offline update.
H9P97S A.00 6 – 67
8. From the SPMAINT main menu, enter =4.7.3, select the menu number corresponding to the system
to update, and then press Enter.
9. Choose option 3 for offline upgrade type and press Enter.
10. Select the menu number corresponding to 3.2.1.46-GA and press Enter. To verify that physical copies
are not in progress, enter the showtask –all command.
11. The following confirmation message is appears:
Enter y and then press Enter.

12. Enter the five-digit number that is displayed to confirm update and press Enter.
The duration of the update process varies depending on the system configuration.
13. When the update process completes, press Enter to return to the SPMAINT main menu.
14. Verify the health of the storage system.
15. From the SPMaint menu, enter =7 and then press Enter to start a CLI session from the SPMAINT main
menu. Enter the shownode command to verify all controller nodes have rejoined the cluster.
16. Enter the showversion -a -b command to verify the system is running HP 3PAR OS 3.2.1.x.
17. Enter exit and press Enter to exit the CLI session and return to the SPMAINT main menu.
18. Wait five minutes before running the system health check process to ensure the upgrade fully
completes all associated tasks.
The post-update task is run automatically after the upgrade for customer users on the StoreServ 7000
series. For the other storage systems, post-update tasks are to be run manually. Check the status of
post-update task details in the upgrade log.
H9P97S A.00 6 – 68
Updating the HP 3PAR OS using SPOCC
1. Log in to SPOCC with the SP IP address. Enter the SP IP address into a supported browser.
https://<SP_IP_address>
2. Click the Support tab and then click Health Check. A system health check is performed. View the report and
resolve issues, if any.
3. To return to the SPOCC main page, click the Home tab.
4. Click the Update tab and then click Update HP 3PAR OS.
5. On the Start step, click Next.
TIP: To exit the update interface at any time, click any of the tabs in the left navigation pane, or click Cancel to return to
the SPOCC home page.
6. On the Select OS version step, select one of the following options, depending on the location of the OS version
that you want to upgrade to:
• Pre-loaded—By default, this option is selected and populated with the latest OS version that is available. The
list includes all loaded updates and patches in addition to a Revert last patch option.
• ISO image—This option enables you to browse to a local ISO image file.
• Service Processor DVD drive—This option enables you to import the update from the physical media drive on
the SP.
• Location path—(HP Authorized Users only) This option enables HP Authorized Users to specify the location
path of a directory that contains the software RPMs. Click Next.
NOTE: If you selected the ISO image, Service Processor DVD drive, or Location path option, the load operation occurs
automatically, and the OS software version appears as the Pre-loaded default option.
7. The Review documentation and responsibilities page appear with links to the current HP 3PAR OS release notes
and the HP Support Center. Review the recommended documentation and best practices information. After
reviewing the information, click the acknowledgement check box and then click Next.
8. On the Select update method step, select either Online or Offline, and then click Next.
NOTE:
• HP recommends that you use the online update method. The offline update method causes service to be interrupted.
• The Offline option is unavailable when applying a patch to the OS or reverting a patch. The Online option is unavailable
when reverting to the prior OS version.
9. On the Check hosts step, review the Persistent Ports setting to verify that it is configured, and then click Next.
NOTE:
• The Persistent Ports feature helps to ensure that connectivity is not lost as nodes are rebooted during the online
upgrade process. HP recommends that this feature be configured.
• If the Persistent Ports feature is not configured correctly and you are performing an online update, you will need to
compare your host configuration to the supported configurations that are listed on the SPOCK site.
• To export host data information in a CSV format that can be loaded into a spreadsheet, click Export Host Data.
• For more information about your Persistent Ports configuration, click More on Persistent Ports.
H9P97S A.00 6 – 69
10. On the Validate StoreServ readiness step, allow the checks to run, and review the results. You can view detailed
results of the checks by clicking the details links. If issues are detected, you can resolve them and then click Re-
run Validation to run the checks again without exiting this update interface. Click Next.
11. On the Install update step, review the update version and options you selected, and then click Install.
On the Updating HP 3PAR OS status page, you can monitor the status of the update: in progress, successful, or
failed. If the update fails, contact HP Support.
NOTE:
• The post-update task is run automatically after the upgrade for customer users on HP 3PAR StoreServ
7000 series.
• For the other storage systems, post-update tasks are to be run manually.
H9P97S A.00 6 – 70
H9P97S A.00 6 – 71
H9P97S A.00 6 – 72
Learning check answers

1. Is it possible to upgrade a 72xx model to a 74xx model?
No
2. Is it required for both controllers from the same pair to have identical HBAs?
Yes
3. How much time do you have to replace a disk drive? What should you do if you require more time?
You have 10 minutes. If you require more than 10 minutes to replace a disk drive, install a disk drive blank cover to
prevent overheating while you are working.
4. What is the best practice regarding disk drives when upgrading capacity in a four-node configuration?
When upgrading capacity in a four‐node configuration, the best practice is to add equal quantities and types of
drives to both node pairs.
5. Which document you should always consult before you begin a 3PAR OS upgrade? What does it include?
Before you begin a 3PAR OS upgrade, you should always consult the respective HP 3PAR Operating System Upgrade
Pre-Planning Guide. It includes information about:
• An overview of the online and offline upgrade processes for the HP 3PAR OS
• Prerequisites for online upgrades
• Guidelines for online upgrades
• Planning information needed for online upgrades
• Veritas Dynamic MultiPathing (DMP) prerequisites for online upgrades
• Remote versus local methods of upgrading
H9P97S A.00 6 – 73
H9P97S A.00 6 – 74
Managing HP 3PAR StoreServ III Alerts
H9P97S A.00 7–1

H9P97S A.00 7–2

H9P97S A.00 7–3

H9P97S A.00 7–4

Alert severity levels
H9P97S A.00 7–5

H9P97S A.00 7–6

H9P97S A.00 7–7

H9P97S A.00 7–8

To apply an action to an alert:

If you accessed the alert from the Alerts, Tasks, and Connection Pane, right-click the alert and select Acknowledge, Mark
as Fixed, Remove, or Show Details
If you accessed the alert from the Alerts tab on the Systems screen, right-click the alert and select Acknowledge, Mark
as Fixed, Mark as New, Remove, or Show Details
H9P97S A.00 7–9

H9P97S A.00 7 – 10
The information displayed in the Alerts tab is nearly identical to the information displayed for all connected
systems and information displayed for a single system, except that an additional System column appears in
the list pane for all connected systems
H9P97S A.00 7 – 11
H9P97S A.00 7 – 12
H9P97S A.00 7 – 13
where <alert_ID> is the alert whose status you wish to acknowledge/remove.
Alerts are system events that require your immediate attention.

An alert can be triggered by a single event, a combination of events, or by repeated occurrences of the same event.
The system administrator is responsible for responding to alerts. You can view, set state, and remove an alert.
H9P97S A.00 7 – 14
Examples:
The following example displays new customer alerts on a system.
The following example displays all alerts from the system with the option to remove individual alerts.
H9P97S A.00 7 – 15
While most system alerts are generated automatically without any need for user configuration, there are several types
of alerts that you can specifically configure.
• Limits relating to CPGs can be set by the user when creating a CPG and can later trigger alerts.
• Limits for virtual volumes capable of allocating space on demand are also user configurable and can trigger alerts.
• The raw space alert is a global threshold that can be set for the storage system to alert administrators when available
space on the system falls below a user-specified level. When the available space on the storage system falls below
this user-specified threshold, an alert is generated.
Four default system thresholds that alert you when the available space on the system falls below 50%, 75%, 85%, and
95% of the total available space on the system.
When the user-defined threshold is set, alerts for system thresholds below the user-defined threshold are suppressed.
To set a raw space alert for a storage system with nearline (NL) drives
Enter the setsys RawSpaceAlertNL <threshold> command
To set a raw space alert for a storage system with Fibre Channel (FC) drives
Enter the setsys RawSpaceAlertFC <threshold> command
To set a raw space alert for a storage system with Solid State Drives (SSDs)
Enter the setsys RawSpaceAlertSSD <threshold> command
For each command above, <threshold> is an integer from 100 to 100,000 that represents the total available
space on the system in gigabytes
A value of 0 effectively disables the raw space alert safety feature
Any alerts for system thresholds below the user-defined thresholds are suppressed
H9P97S A.00 7 – 16
H9P97S A.00 7 – 17
The event log has information about all notable occurrences on the system.
System events include all alerts the system has generated and alerts marked as acknowledged or fixed.
These system events are generated and logged in the system event log.
By default, the HP 3PAR Storage System reserves 3 MB for event log entries.
• However, the actual default size is 30 MB because the storage system maintains 11 versions of the event log: the
current version, for writing new events to the log, and the past 10 versions for reading past events.
• When 11 versions have been written, the oldest event log is deleted.
• The 3 MB log size default value can be changed by administrators using the CLI setsys command EventLogSize
parameter.
An event is logged if the event log size is changed.
The current event log size can be obtained using the CLI showsys –param command.
H9P97S A.00 7 – 18
H9P97S A.00 7 – 19
H9P97S A.00 7 – 20
H9P97S A.00 7 – 21
H9P97S A.00 7 – 22
You can configure System Reporter to send email alerts when certain metrics meet specified conditions. For example,
suppose you want to receive an email alert when any VLUN has an average read service time of more than 100 ms in any
high-resolution sampling interval. To do this, all you need to do is fill in a form with the specified details and then submit
the query.
To add an alert rule:
1. Point your browser at the web server where Apache HTTP Server and the HP 3PAR System Reporter Web server
scripts are installed. The 3PAR System Reporter main window appears.
2. Click Policy Settings in the Extras menu area. The 3PAR System Reporter Policies window appears.
3. Choose the Alert Rules tab.
4. Click Add Alert.
H9P97S A.00 7 – 23
1. Choose the data table to which the rule applies from the drop-down list.
2. Choose the resolution of the samples to which the rule applies from the drop-down list. The rule will be evaluated
for each sample of the chosen resolution.
3. Choose the system to which the rule applies from the drop-down list. Leave this blank if you want the rule to apply
to all systems.
4. Choose the metric that the rule should calculate from the down-list. The available metrics depend on the chosen
data table, and changing the data table will reset the selected metric.
5. Choose the direction that determines how the metric is compared to the limit value from the drop-down list. The
available values are > (greater than) and < (less than).
6. Enter the limit value as a number. The metric is compared against this number.
7. Enter the limit count as an integer (zero or larger). For each sample interval, an alert email is only generated if the
metric exceeds the limit value (as compared by direction) for more than limit count objects.
8. Enter the condition (min_read_iops, min_write_iops, or min_total_iops) to indicate the type of condition that is to be
monitored.
9. Enter the condition value to specify the minimum amount that is to be met for the associated condition.
10. Enter the recipient email address to whom the alert for this rule should be sent.
11. Click Submit Query. An alert window appears confirming that the alert rule was added.
12. Click OK to return to the Sampling Policies window.
H9P97S A.00 7 – 24
H9P97S A.00 7 – 25
A new feature that was introduced in the HP 3PAR OS 3.1.3 allows you to set up custom alerting with the On-Node
System Reporter. The feature is only be enabled if a valid System Reporter license is installed on the array.
Using the CLI, the administrator can create customizable alerts to identify performance issues that the array might be
experiencing. There are no predefined values or alerts within the tool, so you must identify your own standards on which
they will alert. You should set values on observances that were made during the monitoring of the array using the
performance reporting
Performance alerting CLI commands

Create an alert—Createsralertcrit
AO (AO movement)—sraomoves, srrgiodensity
History (historical histograms for various performance collections)—srhistld, srhistpd, srhistport, srhistvlun
Space (data space consumed or free in different categories)—srcpgspace, srldspace, srpdspace, srvvspace
Stat (historical performance statistics over a measured period )—srstatcmp, srstatcpu, srstatld, srstatlink, srstatpd,
srstatport, srstatqos, srstatvlun
H9P97S A.00 7 – 26
Alerts are generated using the srsampler command

Each time srsampler takes a sample
• All existing alerts are cleared for each object on which alerts have already been set
• Checks all current criteria created with createsralercrit
• Data sample compared against each alert
• If criteria for alert is met, alert is generated using existing mechanisms
− SNMP traps
− Email alerts
H9P97S A.00 7 – 27
H9P97S A.00 7 – 28
cli% createsralertcrit -h
createsralertcrit - Create a System Reporter alert criterion.
Syntax
createsralertcrit <type> [options <arg>] <condition>[,<condition>...] <name>
Description
The createsralertcrit command creates a criterion that System Reporter evaluates to determine whether a
performance alert should be generated.
Authority
Super, Service, and any role granted the sralertcrit_create right
Options
Note that many of these options depend upon the type specifier, below. Options common to all types:
• -daily
This criterion is evaluated on a daily basis at midnight.
• -hourly
This criterion is evaluated on an hourly basis.
• -hires
This criterion is evaluated on a high-resolution (5-minute) basis. This is the default.
• -count <number>
The number of matching objects that must meet the criteria for the alert to be generated. Note that only one alert is
generated in this case, and not one alert per affected object.
• -major
This alert should require urgent action.
• -minor
This alert should not require immediate action.
• -info
This alert is informational only. This is the default.
H9P97S A.00 7 – 29
H9P97S A.00 7 – 30
H9P97S A.00 7 – 31
Extra examples
createsralertcrit pd -hourly -major -disk_type NL -count 4

total_iops>50,total_kbps>512,total_svctms>80 pdMajorAlertNL80ms
A major severity alert is generated if an hourly sample shows at least 4 NL drives that have total service
times over 80 ms with a minimum total IOPS over 50 and minimum throughput of .5 MB to avoid triggering on
idle PDs.
createsralertcrit port -hires -major -port_type host total_svctms>120

portMajorAlertHostPortsTotalSvctms120
A major severity alert is generated if a high-resolution sample shows that the total service times on any host
port is greater than 120 ms.
createsralertcrit cpu –hourly -minor idle_pct<20 cpuMinorAlertIdle20pct

A minor severity alert is generated if an hourly sample shows the CPU idle is less than 20%.
createsralertcrit vlun -hires -minor write_svctms>80,write_iops>100

vlunMinorAlertWriteSvctms80
A minor severity alert is generated if a high-resolution sample finds any VLUN with write service time greater
than 80ms with at least 100 write IOPS.
H9P97S A.00 7 – 32
showsralertcrit [-daily|-hourly|-hires] [-enabled|-disabled]

By default, displays all alert criteria shown.
Type can be cpgspace, ldspace, vvspace, pdspace, ld, pd, port, vlun, cmp, cpu, link, or qos.
Name can be a glob-style pattern
-daily, -hourly, or -hires can be used to show criteria only checked when the respective samples are
collected.
-enabled and -disabled can be set to only show the enabled or disabled criteria.
removesralertcrit [-f] <name>

Removes an alert criteria.
setsralertcrit –enable|-disable <name or pattern of criteria>

Enables or disables the specified alert criteria.
H9P97S A.00 7 – 33
H9P97S A.00 7 – 34
NOTE: You might need different thresholds for SLC versus MLC, to answer the question: Is response time affected by
port/bus bandwidth? (Not a drive limitation.)
H9P97S A.00 7 – 35
H9P97S A.00 7 – 36
Possible PD alerting scenario: “busydrives”

Set up multiple conditions, but note the alert only triggers if all criteria are met.
Use a min total_iops and total_kbps to avoid false trigger on high response times for idle PDs. (Note: kbps is
kilobytes not kilobits!)
Set -count to minimize the alert to only when a number of (n% of all) disks reaches the sustained levels to generate a
single alert.
Three alert criteria are defined with a threshold at increasing levels and corresponding severity (–info/-minor/-
major) based on total_svctms.
H9P97S A.00 7 – 37
H9P97S A.00 7 – 38
Two events using hires on NL with a synthetic load generated—as the response times spike for the first few
minutes.
cli%> showalert
Id : 146
State : New
Message Code: 0x006000b
Time : 2014-02-05 20:25:02 CST
Severity : Informational
Type : System Reporter PD performance alert
Message : System Reporter alert criterion infoalertNL with condition
total_iops>50,total_kbps>500,total_svctms>40 has been satisfied by pd count
>= 4 with value(s) 16
Id : 161
State : New
Message Code: 0x0030015
Time : 2014-02-13 18:55:03 CST
Severity : Informational
Type : System Reporter port performance alert
Message : System Reporter alert criterion portinfoalertHostPorts152MB
with condition sum_total_kbps>155648 has been satisfied by port (all
selected) with value(s) 171482.5
H9P97S A.00 7 – 39
H9P97S A.00 7 – 40
100 ms,
H9P97S A.00 7 – 41
H9P97S A.00 7 – 42
H9P97S A.00 7 – 43
H9P97S A.00 7 – 44
An SNMP manager can send four types of requests to an agent:

• SET—Writes an object value in the agent.
− The SET request includes the object ID and a new value for the object.
− The agent changes the value of the object and saves it in the persistent store.
− Not all objects are changeable. The management information base (MIB) contains access information.
• GET—Reads an object value in the agent.
− The GET request includes the object ID to be retrieved.
− The agent returns the value of the object.
• GETNEXT—Reads the object instance that is next in lexicographical order to the object ID in the request.
− For example, if the object ID specified in the request is .12925.0, the returned object ID should be .12925.1, if it
exists.
• GETBULK—An optimization of the GETNEXT operation that allows multiple instances of objects to be returned.
The manager can also register with the agent to receive notifications (traps) for critical events (alerts) and alert state
changes. Before an SNMP manager can receive the traps generated by the SNMP agent, you must register your manager
with the agent.
The HP 3PAR SNMP agent runs on the system and provides a management interface to enable other software products
to manage HP hardware using SNMP.
The SNMP agent responds to GET, SET, GETNEXT, and GETBULK SNMP requests and generates traps for alerts and alert
state changes.
H9P97S A.00 7 – 45
The SNMP agent converts all system alerts and alert state changes into SNMPv2 traps and forwards them to all SNMP
management stations that are registered with the agent.
• These notifications, which contain detailed information that describe critical events, are generated for every alert and
alert state change issued by the system.
• The exact message formats are described in the HP 3PAR MIB.
The HP 3PAR SNMP agent supports the following standards:
• SNMPv2c
− This version refers to a widely used administrative framework for SNMPv2, also known as “community-based
SNMPv2.”
− Although this version includes SNMPv2 enhancements, such as notification and GETBULK requests, it relies on the
SNMPv1 community concept for security.
• Structure of Management Interface-v2 (SMIv2)
− This standard specifies the format of the MIB.
− The HP 3PAR MIB definition uses SMIv2 conventions.
• SNMPv3
− This version provides stronger security with user-based authentication and protocol data unit (PDU) or packet
encryption.
H9P97S A.00 7 – 46
*A varbind or variable binding is a sequence of two specific fields. The first field is an OID, which addresses a
specific parameter. The second field contains the value of the specified parameter.
H9P97S A.00 7 – 47
MIB-II defines several groups of standard information to be provided by the agent.

The SNMP agent supports only the system group objects.
The following table summarizes the MIB-II information provided by the SNMP agent. For details, consult the HP 3PAR
StoreServ Storage Concepts Guide.
H9P97S A.00 7 – 48
The following table summarizes the contents of this trap.
H9P97S A.00 7 – 49
The following example shows an alertNotify trap translated from an alert.
H9P97S A.00 7 – 50
H9P97S A.00 7 – 51
The following example shows an alertNotify trap translated from an alert status change event.
H9P97S A.00 7 – 52
To register the SNMP manager with the agent, use the addsnmpmgr command followed by the manager’s IP address.
If you need to use one of the following options, enter it after the command and before the IP address:
• -p <port_number>—Specifies the port number where the manager receives traps. The default port is 162.
• -pw <password>—Specifies the manager’s access password, if the manager has one.
• -r <number> —Specifies the number of times the system will attempt to resend the trap if the manager is not
available. You can specify from 1 to 15 retries. The default is 2.
• -t <seconds>—Specifies the number of seconds to wait between retries. You can set this timeout interval from 1
to 300 seconds. The default is 200.
NOTE: The HP 3PAR OS supports a maximum of 10 registered SNMP managers.
For detailed information about all HP 3PAR CLI commands described in this section, see the HP 3PAR Command Line
Interface Reference for additional information and examples.
The following example displays the addition of SNMP manager IPv4 address 123.45.67.89 with the assigned password of
alpha1:
cli% addsnmpmgr –pw alpha1 123.45.67.89
The following example displays the addition of SNMP manager IPv6 address 5def:2008:abcd::161a with port number
9162:
cli% addsnmpmgr –p 9162 5def:2008:abcd::161a
H9P97S A.00 7 – 53
To change the SNMP manager’s properties, use the setsnmpmgr command followed by the manager’s IP address.
If you need to edit following options, enter them after the command and before the IP address:
• -p <port_number>—Specifies the port number where the manager receives traps. The default port is 162.
• -pw <password>—Specifies the manager’s access password, if the manager has one.
• -r <number>—Specifies the number of times the system will attempt to resend the trap if the manager is not
available. You can specify from 1 to 15 retries. The default is 2.
For detailed information about all HP 3PAR CLI commands described in this section, see the HP 3PAR Command Line
Interface Reference for additional information and examples.
The following example modifies the SNMP manager IPv4 address 123.45.67.89 with the assigned password of alpha1.
cli% setsnmpmgr –pw alpha1 123.45.67.89
H9P97S A.00 7 – 54
Viewing registered managers

Use the HP 3PAR CLI showsnmpmgr command to see which managers are already registered with the SNMP agent.
NOTE: If the manager that monitors the system has changed, remove the old manager and register the new one.
Removing a manager
To remove a manager from the agent’s list of registered managers, thus preventing that manager from receiving traps,
use the removesnmpmgr command.
If more than one manager is running on the same server, you can distinguish between them by using the -p option
followed by the port to which the manager is listening.
Follow the command (and the option and its argument, if applicable) with the IP address of the manager’s server.
For more information about the removesnmpmgr command, see the HP 3PAR Command Line Interface Reference.
H9P97S A.00 7 – 55
For the SNMP Manager to communicate with the HP 3PAR SNMP agent, it must pass the agent the correct community
string.
• To do this, the manager needs to know the agent community string.
• The system comes with the single default community string, “public” with reading permissions for the agent.
• You can add read-only and write-only community strings, and you can change or remove any of the community
strings.
To see community strings that are currently available on the system, use the HP 3PAR CLI showsnmppw command.
• By default, this command shows the read/write community string.
• If the community string you are requesting does not exist, you will get an error message.
To add or update a community string, use the setsnmppw command followed by the new community string.
• By default, this command changes the read/write community string.
To remove a community string, use the removesnmppw command.
• After the community string is removed, the manager can no longer send requests to the SNMP agent. By default, this
command removes the read/write community string.
For the three previously mentioned HP 3PAR CLI commands (showsnmppw, setsnmppw, and removesnmppw), you
can follow the command with one or more of the following options to specify the community string to which the
command applies:
• -r for the read-only community string
• -w for the write-only community string
• -rw for the read/write community string
H9P97S A.00 7 – 56
To send a test trap to all SNMP managers displayed with the showsnmpmgr command, enter the checksnmp
command.
• The CLI displays the IP addresses of the tested mangers.
• For details about the test trap sent by the checksnmp command, see the HP 3PAR Command Line Interface Reference
and the HP 3PAR CLI Help.
H9P97S A.00 7 – 57
To create SNMPv3 users, you must have Super role user rights, or any role that has been granted the
snmpuser_create right.
• The createsnmpuser command creates the SNMPv3 user secret key, which is used for generating authentication and
privacy keys.
• The user name must be an existing HP 3PAR OS local user.
• To create an SNMPv3 user, enter the createsnmpuser -p <password> <user_name> command, where:
− <password> represents the password of the HP 3PAR OS local user. The password is converted to an SNPMv3
secret key. If a password is not specified with the -p option, the system prompts you to enter the password of the
local user.
− <user_name> represents the HP 3PAR OS local user name. This user name is used as the SNMPv3 user name.
• You can verify the creation of a new user by using the showsnmpuser command.
• For more information about the createsnmpuser command, see the HP 3PAR Command Line Interface Reference.
Example
cli% createsnmpuser <joe>
Please enter the password below. The password will be used to generate both
authentication and privacy secret keys for use in SNMPv3.
Password for user <joe>:
H9P97S A.00 7 – 58
To display information about SNMPv3 users and privacy protocols, use the showsnmpuser command.
• To display all the SNMPv3 users of a system, enter the showsnmpuser command.
• To display information for a specific showsnmpuser user, enter the showuser <user_name> command, where
<user_name> is the name of the user.
NOTE: Users with Browse or Service roles are limited to viewing the information for their own accounts.
To remove an SNMPv3 user from the system, enter the removesnmpuser <user_name> command, where
<user_name> is the name of the user.
• You can verify the removal of a user with the showsnmpuser command.
NOTE:
After an SNMPv3 user is removed with the removesnmpuser command, an SNMPv3 manager can no longer use that
user name to send requests to the SNMP agent.
The HP 3PAR OS local user name remains valid unless it is removed with the removeuser <user_name> command.
Removing a local user name with the removeuser command also removes the SNMPv3 user name from the system.
For more information see the HP 3PAR Command Line Interface Reference.
H9P97S A.00 7 – 59
The HP 3PAR SNMP agent runs on the system and provides a management interface to enable other software products
to manage HP hardware using SNMP. The SNMP agent responds to GET, SET, GETNEXT, and GETBULK SNMP requests and
generates notification messages (traps) for critical events (alerts) and alert state changes. The SNMP agent converts all
system alerts and alert state changes into SNMPv2 traps and forwards them to all SNMP management stations that have
previously registered with the agent. These notifications contain detailed information describing critical events and are
generated for every alert and alert state change issued by the system. The exact message formats are described in the
HP 3PAR MIB.
The HP 3PAR SNMP agent supports SNMPv3, SNMPv2c, SMI-v2 standards, and the SNMPv2-MIB and a proprietary HP
3PAR MIB.
The HP 3PAR MIB is located on the 3PAR OS CLI and SNMP CD.
All alerts generated by the system and all alert status change events are translated into alertNotify traps.
If you receive a trap with messageCode = 1245186, this is to notify you that an alert has changed state. To
determine which alert has changed state, you must extract the alert ID from the id trap field.
H9P97S A.00 7 – 60
H9P97S A.00 7 – 61
H9P97S A.00 7 – 62
SMI-S enables you to manage SANs in a heterogeneous multivendor environment.

SMI-S uses an object-oriented model based on the CIM to define objects and services that comprise a SAN. By leveraging
vendor and technology independent standards, SMI-S allows management application vendors to create applications
that work across products from multiple vendors.
The SMI-S model is divided into several profiles, each of which describes a particular class of SAN entities, such as disk
arrays. These profiles allow for differences in implementations but provide a consistent approach for clients to discover
and manage SAN resources and facilitate interoperability across vendor products within the SAN.
SMI-S also defines an automated resource discovery process using Service Location Protocol version 2 (SLPv2). This
allows management applications to automatically find SAN resources, and then probe them to determine which of the
SMI-S profiles and features they support.
For more information about SMI-S, see the SMI website: http://www.snia.org/smi/home
SMI-S is based on the Web-Based Enterprise Management (WBEM) initiative, which is defined by the Distributed
Management Task Force (DMTF). WBEM is a set of management and Internet standard technologies developed to unify
the management of distributed computing environments.
The DMTF has developed a core set of standards that make up WBEM including:
• CIM standard—The data model for WBEM. CIM provides a conceptual framework for describing management data for
systems, networks, applications, and services, and it allows for vendor extensions. SMI-S uses CIM to model the
objects and relationships that comprise a SAN.
• WBEM discovery using SLP—A method for applications to identify WBEM-based management systems.
For more information about WBEM and CIM, see the DMTF website: http://www.dmtf.org
H9P97S A.00 7 – 63
HP 3PAR CIM support

Standard compliance
• The HP 3PAR CIM Server supports SMI-S version 1.5.
• The HP 3PAR CIM API passes SNIA-CTP conformance.
SMI-S profiles
• SMI-S defines profiles that are used to manage the elements of a SAN.
• These SMI-S profiles are described in detail in the HP 3PAR CIM API Programming Reference.
Supported extensions
• The HP 3PAR CIM server supports additional classes that provide management for system-specific features not
covered by SMI-S.
• For more information, see the HP 3PAR CIM API Programming Reference.
CIM indications
• SMI-S provides for asynchronous notification of events that indicate changes in the CIM server or the managed
elements that are controlled by the CIM server.CIM indications are the mechanism for delivery of such events.
• A CIM client must subscribe to indications that it wants to receive the event notifications from the CIM server. The HP
3PAR CIM Server currently supports indication subscriptions for changes in the operational status of FC ports.
• For more information, see the HP 3PAR CIM API Programming Reference.
H9P97S A.00 7 – 64
Commands
startcim
• Starts the CIM server to service CIM requests.
• By default, the CIM server is not started until you enter this command
stopcim
• Stops the CIM server from servicing CIM requests.
• Options:
–f: Specifies that the operation is forced. If this option is not used, the command requires confirmation before
proceeding with its operation.
-x: Specifies that the operation terminates the server immediately without graceful shutdown notice.
H9P97S A.00 7 – 65
showcim
• Displays the CIM server current status, either active or inactive.
• Also displays the current status of the HTTP and HTTPS ports and their port numbers. In addition, it shows the current
status of the SLP port, which is either enabled or disabled.
• Options:
–pol: Shows CIM server policy information.
setcim
• Sets the properties of the CIM server, including options to enable or disable the HTTP and HTTPS ports for the CIM
server
• Also lets you configure the port numbers associated with these two protocols
• In addition, it lets you enable or disable the SLP port, and set the CIM server policy
• Options:
-f: Forces the operation of the setcim command, bypassing the typical confirmation message.
At least one of the following options is required when entering the setcim command:
-slp enable|disable
− Enables or disables the SLP port.
-http{s} enable|disable
− Enables or disables the HTTP{S} port. This option is deprecated and will be removed in a subsequent release.
-httpport <int>
− Sets the HTTP port (49152 - 65535). The default value is 5988.
-httpsport <int>
− Sets the HTTPS port (49152 - 65535). The default value is 5989.
-pol {no_replica_entity | replica_entity}
− Sets the CIM server policy to one of the following:
− replica_entity (default setting)—Complies with SMI-S standard for usage of Replication Entity objects in
associations.
− no_replica_entity—Does not comply with SMI-S standard for Replication Entity usage.
− Use only as directed by HP support personnel or release notes.
H9P97S A.00 7 – 66
H9P97S A.00 7 – 67
• This section describes how to set up and manage local notification, which requires you to use the Service Processor
Onsite Customer Care (SPOCC) interface.
• It also includes instructions on enabling local notification access, setting up local notification, and managing local
notification records and user profiles.
• Some of these tasks, including managing local notification records and user profiles, are not typically performed by
service providers.
• You can also use the HP 3PAR Service Processor Onsite Customer Care (SPOCC) User’s Guide for instructions on
managing local notification and user profiles.
• The local notification features of the service processor allow you to be notified of important storage system events
and alerts on a subscription basis.
• Notifications are sent through email to all subscribers, with each subscriber specifying up to three email addresses.
• When Real-time Alert Processing (RAP) forwarding is enabled, copies of all notification messages sent to subscribers
are automatically forwarded to HP 3PAR Central as well.
H9P97S A.00 7 – 68
There are two types of local notification messages that you might receive:
• Standard notification messages—A text-based email message that alerts you to an important event or alert
generated by a storage system.
• Grouped low urgency notification messages—A text-based email message that informs you of noncritical events
generated by a storage system.
Low-urgency notification messages are informational and do not typically require you to take any corrective action.
When a situation or event reported in a low urgency notification message becomes urgent, a standard notification
message is issued to alert subscribers.
Before you can subscribe to local notification and receive notification email, local notification access must be enabled.
Enabling local notification access can only be done by an authorized service provider. After local notification access is
enabled, you can create and edit local notification records and user profiles as described in the appropriate HP 3PAR OS
guide.
H9P97S A.00 7 – 69
• The following slides describe how to enable local notification access and then guide you through the initial
configuration process for local notification.
• During this initial configuration, you have the option of configuring sendmail, enabling RAP forwarding, updating site
information, and creating profiles and site notification records for up to three users.
H9P97S A.00 7 – 70
NOTE: Currently, the customer login does not support enabling local notification.
Contact your HP 3PAR Authorized Support Provider to enable local notification before configuring local notification.
During this process, your HP 3PAR Authorized Support Provider will:
• Configure sendmail
• Enter site information
• Create user profiles for up to three users
H9P97S A.00 7 – 71
H9P97S A.00 7 – 72
H9P97S A.00 7 – 73
• The Sites table is a list of configured customer sites. This table shows the site name, site number, and time zone for
each site.
• Use the Editing Sites Table option on the Notification Maintenance Utilities menu to edit information for currently
defined sites or to add additional sites to the table.
• For details, consult the HP 3PAR Service Processor Onsite Customer Care (SPOCC) User's Guide and HP 3PAR Service
Processor Software User's Guide.
H9P97S A.00 7 – 74
• The Product table is a list of installed storage systems where the service processor resides.
• During installation activities, new storage systems and other equipment are automatically added to this table.
• They are not deleted automatically as part of a deinstallation.
• You must update this table after deinstalling a storage system or service processor.
• Deleting an item from this table also deletes all notification records for that system.
H9P97S A.00 7 – 75
To add a new symptom to the list of predefined symptoms available for use in creating symptom notification records:
1. On the SPOCC screen, click Setup.
2. Under Notification Maintenance Utilities, click the Predefine Symptoms option. The Predefined Symptoms screen appears.
3. On the Predefined Symptoms screen, click the Add Record option. The Add Predefined Symptom screen appears.
4. On the Add Predefined Symptom screen:
a. Type a regular expression in the symptom field. NOTE: Click the Regular expressions link to the right of the symptom field
to open a dialog box that enables you to test expressions.
b. (Optional) Type a description for that symptom in the description field.
5. Click Add Record to add the new symptom.
6. Click Back to Menu to return to the Notification Maintenance Utilities menu.
To edit the list of predefined symptoms available for use in creating a symptom notification record:
2. Under Notification Maintenance Utilities, click the Predefine Symptoms option. The Predefined Symptoms screen appears.
3. On the Predefined Symptoms screen, click the Edit icon for the symptom record to be edited. The Edit Predefined Symptom
screen appears.
4. On the Update Predefined Symptom screen, edit the symptom and description fields as necessary.
5. Click Update Record to apply the new settings.
To delete a symptom from the list of predefined symptoms available for use in creating a symptom notification record:
2. Under Notification Maintenance Utilities, click the Predefine Symptoms option. The Predefine Symptoms screen appears.
3. On the Predefined Symptoms screen, click the Delete icon for the symptom to be deleted.
4. When prompted, click OK to confirm.
H9P97S A.00 7 – 76
• The prime shift pattern defines the normal work pattern for you as a local notification subscriber, as recorded in your
user profile.
− For example, your prime shift pattern might be Monday through Friday, 8 a.m. to 5 p.m.
− Your prime shift pattern was defined when you created your user profile.
• A prime shift exception notes any deviations from your usual workday or workweek, as defined by the prime shift.
• Prime shift exceptions for individual users override default prime shift exceptions.
− The global default shift pattern is the default prime shift pattern that is applied whenever your user profile does not
have a specific prime shift pattern defined.
− For example, if you delete all prime shift patterns associated with your user profile, the global default shift pattern
must be applied.
− You can edit the global default prime shift pattern but you cannot delete this default or add additional defaults.
• This feature might be useful for company holidays where no subscribers work a prime shift.
• You can add as many default prime shift exceptions as needed.
• You can also edit and delete these prime shift exceptions after creating them.
• However, because default prime shift exceptions are automatically applied to all user profiles, both new and existing,
in most cases it is preferable to add prime shift exceptions to individual user profiles on a case-by-case basis.
H9P97S A.00 7 – 77
To enable or disable RAP forwarding:

1. On the SPOCC screen, click Setup
2. Under Notification Maintenance Utilities, click the RAP forwarding link to toggle between enabled and disabled
states. The Status field to the right of the link displays the new state (Enabled or Disabled).
H9P97S A.00 7 – 78
Adding a user profile

1. On the SPOCC screen, click Notify. The List Notification Records table appears.
2. At the bottom of the List Notifications Records table, click User Profiles. The Local Notification: User Profiles table
appears.
3. At the top of the Local Notification: User Profiles table, click Add User. The Add ST_USER Record screen appears.
4. On the Add ST_USER Record screen, type your first name in the First Name field and your last name in the Last Name
field (us only lowercase letters when creating the account name).
5. Type up to three email addresses using the Email 1, Email 2, and Email 3 fields.
6. On the Category list, select the type of user you are.
7. In the Company field, type your company name or description.
8. (Optional) Edit the prime shift definition as needed. The prime shift definition establishes the normal working days
and hours that you should receive notifications. To edit the prime shift definition:
a. Click to select or deselect days from the calendar week. The calendar week begins with Monday and ends with
Sunday.
b. On the Start Time list, click to select a start time for the workdays selected on the calendar week.
c. On the End Time list, click to select an end time for the workdays selected on the calendar week.
9. When finished, click Add Record to add your new user profile. The Update ST_USER Record screen appears. Then, a
confirmation message appears at the top of the screen to indicate that your user profile has been added.
10. Click Notification List to return to the List Notification Records table.
H9P97S A.00 7 – 79
After one or more user profiles have been defined, you can use those profiles to create local notification records.
Depending on how local notification was initially set up, one or more notification records might already exist on the
service processor.
Use the features available through the Notify bezel on the SPOCC screen to create additional notification records and to
edit or delete existing ones.
There are three types of local notification records:
• Normal—Used when you want to be notified of events and alerts concerning a particular storage system.
• Symptom—Used when you want to be notified of a particular symptom concerning a particular storage system.
• Suppression—Allows you to selectively suppress notifications generated as a result of a specific symptom.
− Suppression allows you to define a symptom for which you do not want to be notified. It is generally used when a
system is generating many of the same types of events and you do not want to keep getting notifications for them.
Suppression allows notifications to continue for the site, product, or group on all but the identified suppression
record.
H9P97S A.00 7 – 80
To add a standard or normal notification record:

1. On the SPOCC screen, click Notify to display a list of all currently defined notification records for the service
processor.
2. On the List Notification Records screen, click the Add Record button. The Service Processor - Select User screen
appears.
3. On the Service Processor - Select User screen:
a. Choose a user profile from the User list.
b. Choose a notification record type as follows:
i. To add a normal notification record, click Normal and continue to step 4.
ii. To add a symptom notification record, a record that includes a specific symptom, click Symptom.
iii. To add a suppression notification record that suppresses notification for a specific symptom, click
Suppression.
4. Click Select.
5. On the Add Notification Record screen that appears, complete the following steps:
a. Chose either a site name from the Site list or a storage system serial number from the Product list. You cannot
choose both.
b. Type a starting date for the notification record in the Starting Date field and an ending date for the notification
record in the Ending Date field.
c. For each email address defined for this user profile, use the Prime/Off-Shift and High/ Low check boxes to
define which types of system events trigger notifications while the user is both on-shift and off-shift.
6. When finished, click Submit to create the new record and return to the List Notification Records screen.
Edit normal, symptom, and suppression notification records as follows:
1. On the SPOCC screen, click Notify to display a list of all currently defined notification records.
2. On the Local Notification Records screen, click the Edit icon for the notification record to be edited.
3. In the Update Notification Record screen that appears, make changes as necessary.
4. When finished, click Submit to return to the List Notification Records screen.
To delete a notification record:
1. On the SPOCC screen, click Notify to display a list of all currently defined notification records.
2. On the Local Notification Records screen, click the Delete icon for the notification record to be deleted.
3. When prompted, click OK to confirm and return to the List Notification Records screen.
H9P97S A.00 7 – 81
H9P97S A.00 7 – 82
H9P97S A.00 7 – 83
Learning check answers

1. Describe the structure of alert message codes.
• Alert message codes have seven digits in the following schema AAABBBB, where:
− AAA is a three-digit major code
− BBBB is a four-digit subcode
2. Describe four default system thresholds for space oriented alerts.
• 50%, 75%, 85%, 95%
3. Which command displays new customer alerts on a system?
• cli% showalert -n
4. How do you set a raw space alert for a storage system with NL drives?
• cli% setsys RawSpaceAlertNL <threshold>
5. Describe the SMI-S standard.
• SMI-S enables you to manage SANs in a heterogeneous, multivendor environment.
• SMI-S uses an object-oriented model based on the CIM to define objects and services that comprise a SAN.
H9P97S A.00 7 – 84
H9P97S A.00 7 – 85
H9P97S A.00 7 – 86

H9p97s.a.00 Stu - Part2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

H9p97s.a.00 Stu - Part2

Uploaded by

Copyright:

Available Formats

Managing HP 3PAR

Managing HP 3PAR StoreServ III

Module 6 – Upgrading HP 3PAR .............................................................................................. 6-1

Planning information for online HP 3PAR OS upgrades ..........................................6-53

Module 7 – Alerts .................................................................................................................... 7-1

On-Node SR: Performance alerts ............................................................................7-35

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. iii

iv © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 6–1

H9P97S A.00 6–2

H9P97S A.00 6–3

H9P97S A.00 6–4

H9P97S A.00 6–5

H9P97S A.00 6–6

H9P97S A.00 6–7

To access SPMAINT from SPOCC:

H9P97S A.00 6–8

H9P97S A.00 6–9

Repairing a disk drive—Identifying a disk drive

3. A filtered table appears, showing only failed or degraded disk drives

Repairing a disk drive—Disk drive location

Repairing a disk drive—Removing a disk

Removing a 2.5 inch disk Removing a 3.5 inch disk

1. Press the handle latch to open the handle.

Installing a 2.5 inch disk Installing a 3.5 inch disk

Repairing a disk drive—Verifying disk drives

1. Verify the disk drive has been successfully replaced.

Disk drive upgrade - GUI

Checking initial status

Inserting hard drives and checking status

Completing the upgrade

Disk drive upgrade – CLI

Installation and check

Larger systems before upgrade

Larger systems after upgrade

You can read more about different MLC technologies below:

Supported upgrade types example for 3PAR OS 3.2.1 MU1

• Verify compatibility of any host third-party software to the HP 3PAR OS release.

Remote HP 3PAR OS upgrades

The service processor (SP) must be updated to the required SP software.

To verify the HP 3PAR OS level currently running on the storage system:

To start a health check:

Installing the HP 3PAR OS onto the SP using the CD

1. Insert the HP 3PAR OS 3.2.1 Software CD into the SP media drive.

Updating the HP 3PAR OS online

Updating the HP 3PAR OS offline

NOTICE: No host I/O activity is permitted during an offline update.

4. To return to the SPMAINT main menu, enter the exit command.

11. The following confirmation message is appears:

Enter y and then press Enter.

Updating the HP 3PAR OS using SPOCC

Learning check answers

H9P97S A.00 7–1

H9P97S A.00 7–2

H9P97S A.00 7–3

H9P97S A.00 7–4

Alert severity levels

H9P97S A.00 7–5

H9P97S A.00 7–6

H9P97S A.00 7–7

H9P97S A.00 7–8

To apply an action to an alert:

H9P97S A.00 7–9