3PAR InForm OS 2.3.1 Upgrade Pre-Planning Guide

5
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide
software on all the nodes in an alternate location designated as the new software repository.
The update proceeds by loading the new revision of the software on all of the controller nodes
within the system simultaneously. The update process is considered complete and successful
once all the nodes have re-initialized using the new revision of the software. After this is
complete, hosts connected to the InServ Storage Server can be re-started.
3.0 Guidelines for Online Updates
Several guidelines need to be followed for online InForm OS updates. The guidelines are
divided into several categories: general, host configuration, and storage server configuration
guidelines.
3.1 General Guidelines
Observe the following general guidelines in respect to online InForm OS updates:
■ Hardware and configuration changes should not be performed on the InServ Storage
Server during the update. For example, software operations (such as servicemag,
createaldvv, or use of the 3PAR System Tuner commands) and hardware operations (such
as adding/removing drives, cages, etc.) are prohibited during the online update process. All
logical disk growth operations for Common Provisioning Groups continue uninterrupted as
under normal operation.
■ The storage server must be in a “healthy” state (e.g. no failed or degraded physical disks,
cages, FCALs, nodes, etc.). The InForm OS update software performs an automated check.
■ No host or environment changes are allowed during an online update (for example,
rebooting, applying patches, or re-zoning switches). The update software checks for the
existence of hosts before and after each step, and if host connections do not reappear after
each step, the update process reverts to the original level.
■ Any automated processes that communicate with the InServ Storage Server’s management
interface (scripting) must be stopped before performing an online update.
■ Online updates should be scheduled and performed during periods of low I/O activity. As
system resources are placed offline to be updated, system utilization must be lower than
50% for each node and IO port.
■ All hosts must be compliant with the current applicable Implementation Guides for the
target InForm OS level.