01_056601

HDS Confidential: For distribution only to authorized parties. Page i

Installing, Configuring and Maintaining Hitachi Universal Storage Platform™ V and Universal Storage Platform™ VM THI1570 Book 1 of 2

Courseware Version 1.0

Page ii HDS Confidential: For distribution only to authorized parties.

Notice: This document is for informational purposes only, and does not set forth any warranty, express or implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems. This document describes some capabilities that are conditioned on a maintenance contract with Hitachi Data Systems being in effect, and that may be configuration-dependent, and features that may not be currently available. Contact your local Hitachi Data Systems sales office for information on feature and product availability.

Hitachi Data Systems sells and licenses its products subject to certain terms and conditions, including limited warranties. To see a copy of these terms and conditions prior to purchase or license, please call your local sales representative to obtain a printed copy. If you purchase or license the product, you are deemed to have accepted these terms and conditions.

THE INFORMATION CONTAINED IN THIS MANUAL IS DISTRIBUTED ON AN "AS IS" BASIS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL HDS BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS MANUAL, INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL OR LOST DATA, EVEN IF HDS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

Hitachi Data Systems is registered with the U.S. Patent and Trademark Office as a trademark and service mark of Hitachi, Ltd. The Hitachi Data Systems logotype is a trademark and service mark of Hitachi, Ltd.

The following terms are trademarks or service marks of Hitachi Data Systems Corporation in the United States and/or other countries:

Hitachi Data Systems Registered Trademarks Hi-Track ShadowImage TrueCopy Hitachi Data Systems Trademarks Essential NAS Platform HiCard HiPass Hi-PER Architecture Hi-Star Lightning 9900 Lightning 9980V Lightning 9970V Lightning 9960 Lightning 9910 NanoCopy Resource Manager SplitSecond Thunder 9200 Thunder 9500 Thunder 9585V Thunder 9580V Thunder 9570V Thunder 9530V Thunder 9520V Universal Star Network Universal Storage Platform

All other trademarks, trade names, and service marks used herein are the rightful property of their respective owners.

NOTICE:

Notational conventions: 1KB stands for 1,024 bytes, 1MB for 1,024 kilobytes, 1GB for 1,024 megabytes, and 1TB for 1,024 gigabytes, as is consistent with IEC (International Electrotechnical Commission) standards for prefixes for binary and metric multiples.

©2008, Hitachi Data Systems Corporation. All Rights Reserved

HDS Academy 0078

Contact Hitachi Data Systems at www.hds.com.

HDS Confidential: For distribution only to authorized parties. Page iii

Contents Book 1 of 2

INTRODUCTION ............................................................................... IX Welcome......................................................................................................ix HDS Academy – HDS Employee Learning Path......................................... x HDS Academy – Partner Learning Path .....................................................xi Course Description.....................................................................................xii Prerequisites.............................................................................................. xiii Course Objectives .....................................................................................xiv Course Topics ...........................................................................................xvi Summary .................................................................................................. xvii

1. FOUNDATION CONCEPTS...........................................................1-1 Module Objectives.................................................................................... 1-1 Product Position ....................................................................................... 1-2 Product Features ...................................................................................... 1-4 Universal Storage Platform V ................................................................... 1-6 Universal Storage Platform VM................................................................ 1-7 What Attribute Makes a Storage System “Enterprise?” ........................... 1-8 Hitachi Enterprise Storage Families: Present and Past ........................... 1-9 Hardware and Program Product Documentation ................................... 1-10 ECN– “READ ME FIRST”....................................................................... 1-11 ECN– Engineering Change Notice......................................................... 1-12 Identifying the Correct Manual Version .................................................. 1-13 Maintenance Manual and its sections .................................................... 1-14 HiSource................................................................................................. 1-16 Delivering High-availability Storage Services......................................... 1-17 ESD Protection is Mandatory ................................................................. 1-18 Summary ................................................................................................ 1-19 Review Questions...................................................................................1-20

2. BACK-END ARCHITECTURE........................................................2-1 Module Objectives.................................................................................... 2-1 Virtualization – The Big “V” of Storage..................................................... 2-2 RAID Groups and PDEVs ........................................................................ 2-3 Supported RAID Structures...................................................................... 2-5 Emulation.................................................................................................. 2-6 PDEVs and VDEVs .................................................................................. 2-8 LDEV– The Unit of Virtualized Back-end Storage.................................... 2-9 VDEV– LDEVs or Free Space................................................................ 2-11 Shared Memory Stores Control Unit Tables .......................................... 2-12 Control Unit - A Shared Memory table ................................................... 2-13 Parity Group-> PDEV-> VDEV-> LDEV ................................................. 2-14 Parity Group Identifier ............................................................................ 2-15 Universal Storage Platform V ................................................................. 2-16 Parity Group to HDD Cross Reference .................................................. 2-17 Storage Physical Architecture ................................................................2-18 Four-drive RAID Groups, HDUs and B4s............................................... 2-19 Eight-drive RAID Groups, HDUs and B4s.............................................. 2-21 How DKA Pairs Connect to B4s ............................................................. 2-23 Back-end Loop Speed............................................................................2-25 Disk Unit Architecture............................................................................. 2-27 Universal Storage Platform VM.............................................................. 2-28 Physical Storage Architecture ................................................................2-29 Four-drive RAID Groups, HDUs and B4s............................................... 2-30

Contents Install, Configure and Maintain USP V and VM

Page iv HDS Confidential: For distribution only to authorized parties.

Eight-drive RAID Groups ....................................................................... 2-32 How DKA Pairs Connect to B4s............................................................. 2-33 Back-end Comparison ........................................................................... 2-34 Back-end Loop Enhanced Design ......................................................... 2-35 Summary................................................................................................ 2-36

3. COMPONENTS...........................................................................3-1 Module Objectives ....................................................................................3-1 Hardware Block Diagram..........................................................................3-2 Data Movement Components ...................................................................3-4 Data Components Chart ...........................................................................3-5 Support Components ................................................................................3-6 Overall Component Schematic .................................................................3-8 Universal Storage Platform V....................................................................3-9 Cabinet Overview................................................................................... 3-10 Logic Box ............................................................................................... 3-11 Power Supply Section............................................................................ 3-12 Setting the Frame ID.............................................................................. 3-13 Back-end Cabling and B4s .................................................................... 3-14 DKU Component ID ............................................................................... 3-15 CHA Ports– One Port per Microprocessor............................................. 3-16 CHA Ports– High Density....................................................................... 3-17 SFP Transceivers .................................................................................. 3-18 PCB Shutdown Jumpers........................................................................ 3-19 CE JUMPERS on CSW PCB................................................................. 3-20 Other LEDs and Switches...................................................................... 3-21 SVP Jumpers ......................................................................................... 3-22 Other Components................................................................................. 3-23 Shared Memory PCBs and DIMMs........................................................ 3-24 Cache Memory PCBs and DIMMs......................................................... 3-25 Operator Panel and Jumpers................................................................. 3-26 Universal Storage Platform VM.............................................................. 3-27 Rack Overview....................................................................................... 3-28 DKCBOX................................................................................................ 3-29 Back-end Cabling................................................................................... 3-30 Back-end B4s......................................................................................... 3-31 Power Supply Section............................................................................ 3-32 Component ID........................................................................................ 3-33 Diskless.................................................................................................. 3-34 Channel Adaptor (CHA) Ports – High Density ....................................... 3-35 Other Components................................................................................. 3-36 Part Numbers......................................................................................... 3-37 Summary................................................................................................ 3-38

4. USER INTERFACES ....................................................................4-1 Module Objectives ....................................................................................4-1 Service Processor PC – SVP PC .............................................................4-2 Functions Provided by SVP PC ................................................................4-3 GUI Comparison .......................................................................................4-4 SVP Monitor ..............................................................................................4-5 When the SVP is Unavailable...................................................................4-6 Service Processor Architecture ................................................................4-7 High Availability Kit ...................................................................................4-8 High Reliability Kit .....................................................................................4-9 Connecting Maintenance PC ................................................................. 4-10 Maintenance PC Specifications ............................................................. 4-11

Install, Configure and Maintain USP V and VM Contents

HDS Confidential: For distribution only to authorized parties. Page v

Connecting Maintenance PC.................................................................. 4-12 SVP Connect Utility ................................................................................4-13 Remote Desktop Utility........................................................................... 4-14 SVP User Registration Screen ............................................................... 4-15 SVP Application – Main Screen ............................................................. 4-16 Web Console Application ....................................................................... 4-17 Storage Navigator Application................................................................ 4-18 Device Manager Software ...................................................................... 4-19 Summary ................................................................................................ 4-20

5. LOGS AND LICENSE KEYS ........................................................5-1 Module Objectives.................................................................................... 5-1 Modify Mode and Information Log Files ................................................... 5-2 Using and Managing the SVP Logs ......................................................... 5-3 Levels of Error Detection and Logging..................................................... 5-4 The Maintenance Manual and its Sections .............................................. 5-5 Using the System Sense Bytes Manual Section ...................................... 5-6 SIM RC Reference Codes........................................................................ 5-7 Action Codes and Replacement Procedures ........................................... 5-8 SIM-> Content-> Refer to View the SSB.................................................. 5-9 Completing Log Entries .......................................................................... 5-10 Deleting the Logs.................................................................................... 5-11 Audit Log ................................................................................................ 5-12 Downloading the SYSLOG..................................................................... 5-13 License Keys Enable the Software Products ......................................... 5-14 License Management Policy Change.....................................................5-15 New Licensing Bundles - BOS ............................................................... 5-16 Licensing Bundle – BOS V ..................................................................... 5-17 Additional Software Bundles .................................................................. 5-18 Attributes of License Keys...................................................................... 5-19 License Keys Delivered in Text File ....................................................... 5-20 License Keys on the SVP....................................................................... 5-21 Storage Navigator- When Keys not yet Installed ................................... 5-22 Using Web Console/Storage Navigator for Keys ................................... 5-23 License Keys Status after Install and Apply ........................................... 5-24 Entering Individual Key Codes ............................................................... 5-25 Accessing License Key Management ....................................................5-26 Summary ................................................................................................ 5-27 Review Questions...................................................................................5-28

6. POWER SUPPLY ARCHITECTURE................................................6-1 Module Objectives.................................................................................... 6-1 Universal Storage Platform V ................................................................... 6-2 Power Supply Section .............................................................................. 6-3 DKC Power Supplies and Batteries.......................................................... 6-4 Power Supply Section .............................................................................. 6-5 Power Cabling and Boundaries................................................................ 6-6 SVR DC/DC PCBs.................................................................................... 6-7 SVR Backup ............................................................................................. 6-8 Additional Power Supply Options ............................................................. 6-9 Optional Power Supplies ........................................................................ 6-10 Destage Mode and Optional Batteries ................................................... 6-11 Additional Battery Options...................................................................... 6-12 AC Power Configuration Options ........................................................... 6-13 AC Power Jumper ..................................................................................6-14 Power on Sequence ...............................................................................6-15 Universal Storage Platform VM.............................................................. 6-16


Page vi HDS Confidential: For distribution only to authorized parties.

Power Supplies and Batteries................................................................ 6-17 Power Cabling and Boundaries ............................................................. 6-18 Single Phase AC Power Only ................................................................ 6-19 Backup Mode Only and Additional Batteries ......................................... 6-20 Summary................................................................................................ 6-21

7. CONFIGURATION AND OFFLINE SVP...........................................7-1 Module Objectives ....................................................................................7-1 Viewing the Configuration .........................................................................7-2 Configuration Data ....................................................................................7-3 Refer Configuration...................................................................................7-5 System Option ..........................................................................................7-6 Power Supply Configuration – Universal Storage Platform V...................7-7 Usable CUs...............................................................................................7-8 Mode Settings ...........................................................................................7-9 LDEV Synchronous Destage– Write Through ....................................... 7-10 Internal IP Address of the SVP .............................................................. 7-11 Specified IP Address.............................................................................. 7-12 Cache Configuration – Universal Storage Platform VM ........................ 7-13 Cache Configuration – Universal Storage Platform V ........................... 7-14 Setting Dynamic Cache Residency Cache ............................................ 7-15 Cache Logical Partitions ........................................................................ 7-16 CHA/DKA Configuration – Universal Storage Platform VM................... 7-17 CHA/DKA Configuration – Universal Storage Platform V...................... 7-18 CHA Fibre PCB Configuration ............................................................... 7-19 Fibre PCB Mode for CHA Ports ............................................................. 7-20 Architecture of High-density CHA PCBs................................................ 7-21 Port Initiator or Target Behavior............................................................. 7-22 Port Behavior Affects Two Ports............................................................ 7-23 DKA Configuration – Back-end Loop Speed ......................................... 7-24 Rules for 4Gbit/sec Back-end Loops ..................................................... 7-25 Rules for Sparing out a Failed HDD ...................................................... 7-26 DKUs Installed ....................................................................................... 7-27 RAID Groups in B4s............................................................................... 7-28 Remaining Capacity View...................................................................... 7-30 Concatenated Parity Groups.................................................................. 7-31 Variable Volume Size LDEV Definition .................................................. 7-32 LDEV Detail of a Parity Group ............................................................... 7-33 Assigning LDEV ID ................................................................................ 7-34 SSID for Each CU .................................................................................. 7-35 Assigning LDEVs for DCR ..................................................................... 7-36 Shared Memory Configuration – Universal Storage Platform VM ......... 7-37 Battery Configuration ............................................................................. 7-39 LUN Management – Port and Host Group Settings............................... 7-40 LUN Management – LUNs and LUSE ................................................... 7-41 LUN Management – LDEV View ........................................................... 7-42 Complete the Configuration ................................................................... 7-43 Refer Configuration Completed ............................................................. 7-44 Create Configuration Backup................................................................. 7-45 No Formatting of Configuration Media Required ................................... 7-46 Offline SVP............................................................................................. 7-47 Install the Offline SVP Tool .................................................................... 7-48 Installation Progress and Completion Message .................................... 7-49 Offline SVP Tool .................................................................................... 7-50 Value of an Offline SVP Application ...................................................... 7-51 Summary................................................................................................ 7-52

Install, Configure and Maintain USP V and VM Contents

HDS Confidential: For distribution only to authorized parties. Page vii

8. HARDWARE MAINTENANCE........................................................8-1 Module Objectives.................................................................................... 8-1 What is Maintenance?.............................................................................. 8-2 When is Maintenance Required? ............................................................. 8-3 Automated Notification using Hi-Track® Monitor ...................................... 8-4 Field Replaceable Units ........................................................................... 8-5 Accessing the Maintenance Interface ...................................................... 8-6 Maintenance View .................................................................................... 8-7 Maintenance View – Logic Box .............................................................. 8-11 PCBs in the Logic Box............................................................................ 8-12 Follow the Instructions............................................................................ 8-14 Cache Memory and Shared Memory .....................................................8-16 Status LEDs for PCBs ............................................................................ 8-17 Maintenance – CHA PCBs ..................................................................... 8-18 SFP Replacement ..................................................................................8-19 Maintenance – DKA PCBs ..................................................................... 8-20 Status LED for HDD and SVR................................................................ 8-22 HDD Status Light for Universal Storage Platform VM............................ 8-23 Maintenance – Parity Groups................................................................. 8-24 Parity Group Maintenance without HDD Removal ................................. 8-25 Quick Format Specifications................................................................... 8-26 Setting the System Disk ......................................................................... 8-27 Completing the Maintenance Task......................................................... 8-28 HDD Replacement.................................................................................. 8-29 Using the Documentation ....................................................................... 8-30 Identifying the Correct Procedures......................................................... 8-31 HDD Replacement.................................................................................. 8-32 View of Internal Paths ............................................................................ 8-33 IMPL Status ............................................................................................ 8-34 Using the Start Section of the Maintenance Manual .............................. 8-35 Troubleshooting...................................................................................... 8-36 Summary ................................................................................................ 8-37

9. PRESTAGING AND SITE INSTALL.................................................9-1 Module Objectives.................................................................................... 9-1 Prestaging Overview ................................................................................ 9-2 Prestaging Benefits .................................................................................. 9-3 Prestaging Tasks...................................................................................... 9-4 Preparing for the Site Install ..................................................................... 9-5 Site Install Overview................................................................................. 9-6 Unpack and Set into Position ................................................................... 9-7 Connect, Power On and Check................................................................ 9-8 SVP Configuration.................................................................................... 9-9 SVP Secure Communication.................................................................. 9-10 Configuration Check............................................................................... 9-11 Customer Specific Configuration............................................................ 9-12 Install License Keys................................................................................ 9-13 Set Customer LAN IP Address............................................................... 9-14 Install and Test Hi-Track Monitor ........................................................... 9-15 Prestaging and Site Install Summary .....................................................9-16 Site Install Summary............................................................................... 9-17 Summary ................................................................................................ 9-18


Page viii HDS Confidential: For distribution only to authorized parties.

Book 2 of 2

10. NEW INSTALLATION...............................................................10-1

11. HI-TRACK® MONITOR ............................................................11-1

12. CHANGE CONFIGURATION......................................................12-1

13. MICROCODE EXCHANGE ........................................................13-1

14. STORAGE ADMINISTRATION ...................................................14-1

15. SVP MONITOR......................................................................15-1

APPENDIX A: HITACHI ENTERPRISE STORAGE SYSTEMS DIFFERENCES

APPENDIX B: HI-TRACK MONITOR

GLOSSARY

EVALUATING THIS COURSE

HDS Confidential: For distribution only to authorized parties. Page ix

Introduction

Welcome

2

• Student Introductions– Name– Position– Experience– What you expect from the course?

Introduction HDS Academy – HDS Employee Learning Path

Page x HDS Confidential: For distribution only to authorized parties.

HDS Academy – HDS Employee Learning Path

3

Storage administration: Enterprise storage: Implementation & support

2h WBT THC1370Free

Hitachi USP VMTechnical differences from NSC

2-day ILT THI1115

Hitachi USP VHardware & software differences

2h WBT CHC1450Free

Hitachi Universal Storage Platform V & VMTechnical overview

Upgrade path toUSP V & VM

USP V & VM

2h WBT CHC1450Free


5-day ILT TSI1315

Hitachi EnterpriseSoftware fundamentals

5-day ILT THI1570

Hitachi USP V & VMInstallation & maintenance

USP & NSC

2h WBT CHC0500Free

Hitachi Universal Storage PlatformTechnical overview

2h WBT THC0395Free

Hitachi Network Storage ControllerTechnical overview

5-day ILT TSI0556


5-day ILT THI0345

Hitachi USP & NSCInstallation & maintenance

or

5-day ILT THI0750

Hitachi USP & NSCInstallation & maintenance for mainframe

Course is part of the HDS ImplementerCertification track www.hds.com/certification

Certified ImplementerHitachi Data Systems

LP #

6-10

Please contact your local training administrator if you have any questions regarding Learning Paths or visit http://www.hds.com/services/education/.

Introduction HDS Academy – Partner Learning Path

HDS Confidential: For distribution only to authorized parties. Page xi

HDS Academy – Partner Learning Path

4

Storage administration: Enterprise storage: Implementation & support

2h WBT THC1370Free

Hitachi USP VMTechnical differences from NSC

2-day ILT THI1115

Hitachi USP VHardware & software differences

2h WBT CHC1450Free


Upgrade path toUSP V & VM

USP V & VM

2h WBT CHC1450Free


5-day ILT TSI1315


5-day ILT THI1570

Hitachi USP V & VMInstallation & maintenance

USP & NSC

2h WBT CHC0500Free

Hitachi Universal Storage PlatformTechnical overview

2h WBT THC0395Free

Hitachi Network Storage ControllerTechnical overview

5-day ILT TSI0556


5-day ILT THI0345

Hitachi USP & NSCInstallation & maintenance

or

5-day ILT THI0750

Hitachi USP & NSCInstallation & maintenance for mainframe

Course is part of the HDS ImplementerCertification track www.hds.com/certification

Certified ImplementerHitachi Data Systems

LP #

7-8

Please contact your local training administrator if you have any questions regarding Learning Paths or visit http://www.hds.com/services/education/.

Introduction Course Description

Page xii HDS Confidential: For distribution only to authorized parties.

Course Description

5

• This five day instructor-led course details the installation and maintenance of Hitachi Universal Storage Platform™ V and Hitachi Universal Storage Platform™ VM for both mainframe and open systems.

• In addition, hardware architecture and associated software utilities of Universal Storage Platform V and Universal Storage Platform VM are also discussed.

• Classroom presentation is supported by an extensive set of lab activities on installing, configuring and maintaining Universal Storage Platform V and Universal Storage Platform VM.

Introduction Prerequisites

HDS Confidential: For distribution only to authorized parties. Page xiii

Prerequisites

6

• CHC1450 - Hitachi Universal Storage Platform™ V and Hitachi Universal Storage Platform™ VM Technical Overview

• General knowledge of terms and concepts associated with basic storage and open systems operating environments along with a working knowledge of the English language are required.

• Important: Refer to the most current Hitachi product Alerts, Tech Tips and Maintenance Manuals for the Universal Storage Platform V and VM.These documents and any Release Notes and StorFlashes for the product updates contain the current procedures.

Notes:

This course was developed based upon DKC610/DKU6051 Maintenance Manual Rev 4, and Rev 5, and DKC615I Maintenance Manual Rev4 and Rev5, and Microcode versions DKCMAIN 60-02-48 and 60-03-05-A.

This course is not a replacement for the product documentation. Please always refer to product Alerts, and the relevant Maintenance manual for step by step procedures and current specifications and requirements.

Introduction Course Objectives

Page xiv HDS Confidential: For distribution only to authorized parties.

Course Objectives

7

• Upon completion of this course, the learner should be able to:– Describe the key features of Hitachi Universal Storage Platform™ V and VM

within the Hitachi storage product family– Identify all the major components of storage systems including location names

and feature names – Perform the initial factory bring-up procedures and key prestaging activities

using the subsystem configuration screens and performing common onsite activities

– Replace components by following maintenance manual procedures– Implement subsystem hardware upgrades and demonstrate a new upgrade

using the appropriate Maintenance manual sections and other relevant documents

– Perform a microcode exchange to update firmware– Describe and install Hi-Track® Monitor for problem tracking

Note: The terms upgrade, new upgrade, reconfiguration, feature upgrade, feature addition, capacity increase all indicate hardware maintenance activities which increase the storage and/or access capacity of a storage system.

Introduction Course Objectives

HDS Confidential: For distribution only to authorized parties. Page xv

8

• Upon completion of this course, the learner should be able to (continued):– Describe the subsystem configuration and setup requirements for installing

the subsystems– Install and manage Maintenance PC connection to service processor (SVP)

on the private LAN to perform maintenance activities– Use the SVP to perform logical unit (LUN) Mapping, LUSE*, Virtual LVI/LUN

(VLL) and Dynamic Cache Residency– Install license keys to enable software program products

*LUSE is Logical Unit Size Expansion

Note: Read the Appendix section A to understand the differences between Universal Storage Platform V and VM for all of the functions and specifications covered in the course.

Introduction Course Topics

Page xvi HDS Confidential: For distribution only to authorized parties.

Course Topics

9

Lab 1: Universal Storage Platform V and VM Foundations

Lab 2: Back-end ArchitectureLab 3: Component IdentificationLab 4: User InterfacesLab 5: Logs and License KeysLab 6: Power Connections Lab 7: Configuration and Offline SVP ToolLab 8: MaintenanceLab 9: Prestaging and Site InstallLab 10: New Installation without Pre-InstallLab 11: Hi-Track MonitorLab 12: Change ConfigurationLab 13: Microcode ExchangeLab 14: Storage Administration using SVPLab 15: SVP Monitor

IntroductionModule 1: Foundation ConceptsModule 2: Back-end ArchitectureModule 3: ComponentsModule 4: User InterfacesModule 5: Logs and Licenses Module 6: Power Supply Specifications Module 7: Configuration and Offline SVPModule 8: Hardware MaintenanceModule 9: Prestaging and Site InstallModule 10: New InstallationModule 11: Hi-Track® MonitorModule 12: Change Configuration Module 13: Microcode ExchangeModule 14: Storage AdministrationModule 15: SVP MonitorAppendix A: Hitachi Enterprise Storage

Systems DifferencesAppendix B: HI-Track Monitor

Learning ActivitiesContent

Introduction Summary

HDS Confidential: For distribution only to authorized parties. Page xvii

Summary

10

• You will get an opportunity to learn about and practice correct procedures for installing and maintaining Universal Storage Platform V and VM enterprise storage systems in a customer environment.

• You will learn and practice how to perform basic storage provisioning tasks using the SVP application.

• You will learn about and be able to locate and use the appropriate reference documentation.

Introduction Summary

Page xviii HDS Confidential: For distribution only to authorized parties.

HDS Confidential: For distribution only to authorized parties. Page 1-1

1. Foundation Concepts

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Describe the range of Hitachi enterprise and modular storage systems– Discuss the key features of Hitachi Universal Storage Platform™ V and

Universal Storage Platform™ VM enterprise storage systems– Use the Maintenance manual and other relevant documents– Identify mandatory steps for protecting hardware during maintenance

activities

In this module, you will learn where Hitachi’s newest storage systems, the Universal Storage Platform (USP) V and the Universal Storage Platform VM, fit in the range of storage systems product family. You will identify the key features of these largest commercial storage systems and also what qualifies a storage system to be described as an enterprise system. You will also learn about the important product documentation that you will need in your role involved in maintaining storage systems. This module will remind you about the importance of always using anti-ESD protective equipment when you are working on storage system hardware.

Foundation Concepts Product Position

Page 1-2 HDS Confidential: For distribution only to authorized parties.

Product Position

3

• All product families are managed from one integrated software suite

• All models are designed for tiered storage

• Universal Storage Platform V and Universal Storage Platform VM

Func

tiona

lity

Dem

ande

d

WMS100AMS200

AMS500 AMS1000

Advanced Midrange Storage

Systems

Intelligent Virtual Storage Controllers

Size of Organization Served

Small Business or Department

Large BusinessMid-size Business or Department

Universal Storage

Platform VM

Universal Storage Platform V

Product Position

Universal Storage Platform V (USP V) belongs to the Hitachi enterprise storage product family with configurations ranging from entry level to high-end performance. The Universal Storage Platform VM (USP VM) is positioned between the high-end of our modular storage family, the Hitachi Thunder 9585V™ ultra high-end modular storage, and the low-end of our enterprise storage family, the Hitachi Universal Storage Platform™, model USP100. The Universal Storage Platform VM is a scaled down version of the Universal Storage Platform V, including its Hi-Star crossbar architecture for high availability and performance, large scale controller-based virtualization layer for ease of management, logical partitioning for application quality of service, storage-agnostic universal replication for business continuity, and a rich set of software tools-all united in a powerful, rack-mounted, modular form factor at a midrange price.

Universal Storage Platform V is the third-generation of enterprise storage following the Hitachi Lightning 9900™ Series enterprise storage systems and the Lightning 9900™ V Series enterprise storage systems. It is also the foundation for Application Optimized Storage™ solutions from Hitachi Data Systems, enabling storage managers to logically partition storage resources to maximize application Quality of Service (QOS), move data across tiers of storage to match application attributes,

Foundation Concepts Product Position


establish enterprise-wide business continuity, and manage it all from a single pane of glass.

Hitachi Adaptable Modular Storage (AMS) and Hitachi Workgroup Modular Storage lines ensure that companies of all sizes can realize the business benefits of Application Optimized Storage solutions from Hitachi Data Systems.

Adaptable Modular Storage offers two lines (currently) for small and midsize businesses, supporting high-performance FC or cost-efficient SATA intermix drives.

Workgroup Modular Storage is for small businesses and offers Application Optimized Storage solutions built on a new modular, SATA-based storage system.

Hitachi Thunder 9585V™ modular storage systems are designed for small to medium sized businesses or departments of large organizations, delivered using a more affordable and smaller footprint. Note:

In the above chart,

WMS100 is Hitachi Workgroup Modular Storage, model WMS100

AMS200 is Hitachi Adaptable Modular Storage, model AMS200



Foundation Concepts Product Features


Product Features

4

• Universal Storage Platform V and Universal Storage Platform VM– Key Features

• Scalability• High performance• Large capacity• Connectivity • High availability• Nondisruptive service and upgrades

– Other Features • Universal replication and data mobility• Power outage destaging for Universal Storage Platform V/VM• Heterogeneous storage virtualization and aggregation• Storage partitioning for quality of service• RoHS Compliance

Universal Storage

Platform VM


Scalability:

The Universal Storage Platform V and Universal Storage Platform VM are capable of providing large-capacity and seamless growth storage systems that fit customer's needs. Components for each storage system including channel adapters, Cache Memory, disk drives and Back-end data access are installed according to specifications based on that customer’s.

Number of Installed Channel Options: 1-11 sets for Universal Storage Platform V

Capacity of Cache Memory: 4GB to 512GB for Universal Storage Platform V

Number of Disk Drives: Up to 256 HDDs/16 disk paths (One DKA pair model) Up to 640 HDDs/32 disk paths (Two DKA pairs model) or Up to 1,152 HDDs/64 disk paths (Four DKA pairs model)

Foundation Concepts Product Features


High Performance: Supports two kinds of high-speed disk drives with a speed of 10 kmin-1 or 15 kmin-1

Both fibre channel (FC) and SATA interface technology drives are supported. Realizes high-speed data transfer: between the DKA and HDDs at a rate of 4GB/sec with the fibre channel (FC-AL) for Universal Storage Platform V

Performance of the microprocessor: installed in the DKA/CHA is twice as fast as the RAID510/515 Universal Storage Platform /Network Storage Controller

Further improvement of Hi-Star™ crossbar switch architecture provides a bandwidth of 68GB/sec for Universal Storage Platform V

Large Capacity: Supports three kinds of disk drives with various capacities: 72GB, 146GB and 300GB, 400GB fibre channel drives and 750GB and 1TB SATA drives

Controls up to 65,280 logical volumes and up to 1,152 disk drives, so that it realizes a maximum raw physical disk capacity between 332TB and 1.1PB per Universal Storage Platform V.

Connectivity:

The Universal Storage Platform V and Universal Storage Platform VM storage systems are capable of providing storage for both Open systems and mainframe operating systems. They provide heterogeneous storage that integrates with heterogeneous system environments common in many large and complex computing environments.

High Availability: The Universal Storage Platform V supports RAID6 (6D + 2P), RAID5 (3D + 1P/7D+1P) and RAID1 (2D + 2D/4D+4D).

Main components are implemented with a duplex or redundant configuration, so even when single point of the component failure has occurred, the storage system can continue non-stop operation.

Nondisruptive Service and Upgrades: Hardware components can be added, removed, and replaced without stopping I/O operations.

An SVP (service processor), mounted on the disk controller (DKC), monitors the running condition of the system. Connecting the SVP with a service center enables remote maintenance.

The microcode can be upgraded without shutting down the system.

Foundation Concepts Universal Storage Platform V



5

• Newest Generation of Enterprise Storage– Improved Hitachi Universal Star Network™ V massively parallel crossbar

switch architecture– 4Gbit/sec Back-end data loop speed

• Split PCB Slots– Configuration flexibility– More granular, minimized impact

maintenance• Improved software product bundles• Extends Enterprise Storage Capabilities

– Performance– Capacity (support for larger SATA drives)– Thin provisioning – Hitachi Dynamic Provisioning software

Multi-cabinet Configuration

Single-cabinet Configuration

Announced May, 2007

Foundation Concepts Universal Storage Platform VM


Universal Storage Platform VM

6

• All of the unique, industry-leading functionality of the Universal Storage Platform V

– Hitachi Universal Star Network™massively parallel crossbar switch architecture

– In a 19” rack with 200V single phase power

• Same microcode, software, interoperability, external storage support as the Universal Storage Platform V

• Only differs from the Universal Storage Platform V in:

– Capacity– Performance– Diskless configuration supported

Dual-Rack Configuration

Secondary Rack

Primary Rack

Primary Rack

Single-Rack Configuration

Announced September, 2007

Note: Universal Storage Platform VM 19” rack is slightly deeper than the Network Storage Controller (NSC). Therefore, the Universal Storage Platform VM will use more floor space than the Network Storage Controller.

Foundation Concepts What Attribute Makes a Storage System “Enterprise?”


What Attribute Makes a Storage System “Enterprise?”

7

One major feature that identifies “enterprise storage” is its ability to be connected to and serve storage to mainframes. This means IBM mainframes running a mainframe operating system like IBM® z/OS®. Connecting storage systems to mainframe systems requires the ability to support mainframe connectivity technology and protocols which include ESCON and FICON. Hitachi enterprise storage systems support ESCON and FICON channel connectivity options. Traditionally, what categorizes “enterprise” storage is its mainframe connectivity.

Another new feature that distinguishes enterprise systems is the storage virtualization technology which allows other, distinct storage systems to be connected to the enterprise system and have the external storage be managed as though it was physically inside the enterprise system.

Enterprise storage leads other storage systems categorized as mid-range or modular in other characteristics: redundant architecture, high availability, non-disruptive maintenance, capacity, scalability and performance.

Foundation Concepts Hitachi Enterprise Storage Families: Present and Past


Hitachi Enterprise Storage Families: Present and Past

8

R600

R500

R450

USP V

USP VM

USP

NSC

9980V

9970V

DKC610

DKC615

DKC510

DKC515

05

15

04

14

03

03

SystemTypeCode

Hitachi RaidStorage DivisionProduct Code

Hitachi ProductName

SunProductName

HP ProductName

SE9985

SE9990

SE9970

SE9980

SE9990V

XP128

XP1024

XP12000

HitachiProductCode

2007 -

2005 - 2007

Product imagesand dates for

Lightning 9900V products

“TagmaStore”

“Lightning V”

XP10000

XP24000

XP20000SE9985VM

DKC460

DKC465

The table shows the current and previous Hitachi enterprise storage system families. The table shows the Hitachi Raid Storage Division (RSD) product identification, the storage system models in the family and the Sun and HP product names for their versions of the products.

Foundation Concepts Hardware and Program Product Documentation


Hardware and Program Product Documentation

9

• Documentation– The Maintenance manuals, hardware documentation is delivered on the

microcode CD set• Engineering Change Notice – ECN

– Provides information about corrections, changes and enhancementssupported in the new microcode

– Includes the microcode exchange procedures for this microcode version• Maintenance manual for the Universal Storage Platform V • Maintenance manual for the Universal Storage Platform VM

– Software documentation is delivered using Hi-Source libraries• Product Documentation Library (PDL)

All hardware maintenance operations on the Universal Storage Platform V and Universal Storage Platform VM are controlled through the SVP. Carefully read the Maintenance manual when taking maintenance actions to avoid errors. The Maintenance manual also defines and explains installing/de-installing and troubleshooting procedures.

The Engineering Change Notice (ECN) contains the table of all the microcode components that make up a microcode release and the correct version number for each component. In any specific microcode release only a subset of microcode components may have been modified. Some microcode components may still have the same version and version number as one or more previous releases. The microcode component and version table at the beginning of the ECN document identifies the correct component versions for that release.

At this time, the microcode is distributed on 3 CDs: the DKCMAIN code, a CD labeled “OSS” for Other System Software, and a CD that contains the Documents and Tools. The OSS CD contains Java, Apache and Perl. This is the “second” CD that is called for during the New Installation procedure.

Locate and read the correct ECN documents that correspond to the microcode levels for the supported storage systems.

Foundation Concepts ECN– “READ ME FIRST”


ECN– “READ ME FIRST”

10

Reference: ECN-readmefirst

The microcode CD set for Universal Storage Platform V and Universal Storage Platform VM contains a folder named ECN. That folder contains the “READ ME FIRST” document.

The MDL Documentation Library is microcode release dependent. You can see in the READ ME FIRST file that you are reminded to always use the correct version of the documentation for the microcode release of the storage system on which you will be performing maintenance.

This presents a challenge for you as a maintenance engineer as you will most probably be supporting storage systems at different microcode levels. You will have to devise an approach for ensuring that you always have access to the correct manuals for the microcode level of your systems.

Never make any assumptions that a different version of the manual will be “good enough”. The procedure variations from release level to release level can be minor. It is part of your responsibility to be sure you identify and follow the correct maintenance procedures.

Foundation Concepts ECN– Engineering Change Notice


ECN– Engineering Change Notice

11

• Each microcode release inherits all the features, functionality and fixes from previously released microcode.

• Only newly released features, functions and fixes are identified in the ECN. If you need to confirm particular functionality, you may need to refer to previous ECN documents and/or the Maintenance manual or HiSource documentation.

• Refer to ECN Appendix A for the list of new features. Refer to ECN Appendix E for the list of fixes.

A sample first page of the ECN document is shown above. It includes the Date of Issue and the Equipment identification. You can see that this is the ECN for the Universal Storage Platform V and Universal Storage Platform VM as identified by the Equipment Model No. DKC610I and DKC615I. The ECN title section identifies the DKCMAIN component version and SVP version. In this case the DKCMAIN version is 60-02-05-00/00. You can see from the ECN that both the Universal Storage Platform V and Universal Storage Platform VM both use exactly the same microcode, from the exact same set of CDs. So, while you will learn about some differences between the Universal Storage Platform V and Universal Storage Platform VM systems, the microcode and functionality of both these storage systems is identical. It is common to refer to a microcode release by the first three parts of the DKCMAIN version such as “60-02-05.” On the first page of the ECN document, just below the heading section, the table of individual microcode components with their respective component version numbers appears. Notice that the different components may be at different code levels. Whenever you perform any maintenance task that involves installing or exchanging (upgrading) microcode, you should always check the component versions against the ECN at both the start and end of the maintenance procedure. You will get a chance to practice this verification several times in your lab activities.

Foundation Concepts Identifying the Correct Manual Version


Identifying the Correct Manual Version

12

• Appendix B of the ECN identifies the correct Revision version of the Maintenance manual.

Appendix B of the ECN identifies the revision number for the correct version of the Maintenance manual for the microcode version. Always use the correct version of the Maintenance manual that corresponds to the microcode version of the storage system.

Also, if you are a Hitachi Data Systems CE, make sure that you register for the Alerts distribution list. If you work for an HDS partner, use Partner Exchange to keep up-to-date on product Alerts. Accessing and keeping current with Product Alerts and Technical Tips documents is critical as these documents may override instructions in the Maintenance manual.

Foundation Concepts Maintenance Manual and its sections


Maintenance Manual and its sections

13

• Maintenance Manuals are delivered on the microcode CD.

Maintenance Manual Overview Each microcode CD contains a Manuals folder. There is a Universal Storage Platform V subfolder and a Universal Storage Platform VM subfolder. The set of pdf files make up the Maintenance Manual for the respective storage system. Each of the two Maintenance manual folders contains a set of pdf files. Taken altogether, these pdf files comprise the Maintenance manual. Each pdf file represents a section of the Maintenance manual.

01safety.pdf: Reviews general safety procedures, particularly in regard to electrical hazards, grounding, and use of the EPO switch.

02start.pdf: Presents a list of hyperlinks to various other manual sections based on topic. Provides a starting point.

03loc.pdf: Specifies the location-name for every component in a certain space of the subsystem. You’ll use this manual section heavily today. The location-name is NOT the same as a package or feature name (marketing), and is not the same as a part-number (maintenance).

04inst.pdf: Documents available component packages for subsystem (an inventory), and also installation (upgrades) and de-installation (downgrades) for various components or packages. This is not the same thing as doing maintenance (replacement of failed components). Upgrades and downgrades affect the capacity of the subsystem to perform work, replacing a bad component

Foundation Concepts Maintenance Manual and its sections


merely restores the subsystem back to its originally configured capacity. Used heavily for “change configuration” activity.

05micro.pdf: Describes general microcode exchange options and activities. It is used as a reference in conjunction with microcode ECN and other revision-specific instructions.

06trbl.pdf: Reviews advanced trouble-shooting procedures, possibly needed if an unusual problem arises that isn’t being caught by the normal error handling messages.

07replace.pdf: Used to look up the replacement procedures for failed components. It is used in conjunction with SIM error messages and the action code (14acc.pdf) manual section. Both these manual sections are used in the hardware maintenance class.

08diag.pdf: Reviews advanced diagnostic messaging, possibly needed if an unusual problem arises that isn’t being caught by the normal error handling messages.

09priod.pdf: Small manual reviewing periodic maintenance chores, including air filter locations, battery rotation, and power supply output voltage testing.

10svp.pdf: Large section that documents SVP screens and dialogue boxes. 11parts.pdf: When ordering a replacement part, this is where you look up the part number to give to the support center. Remember, package names are in the 04inst.pdf, location names are in the 03loc.pdf.

12theory.pdf: Contains some useful tidbits about how the subsystem operates. 13glossa.pdf: Small glossary of subsystem acronyms. 14acc.pdf: The Action Code manual section is heavily used. When you receive a SIM (system information message) you look up action-code info which will link you to the correct replacement procedures in the 07replace.pdf manual section. Both these manual sections are used in the hardware maintenance class.

15simrc.pdf: Documents SIM message categories. 16open.pdf: Documents multi-platform (host) considerations/issues. When implementing a specific host like Sun Solaris or Microsoft® Windows® NT, this manual section should be looked at. There are also host-specific connection guides for the various platforms that are part of the PDL.

17ssdopt.pdf: Documents CVS and DCR details (ssd means solid-state-disk). 18ssb.pdf: Documents “System Sense Bytes,” which are the foundation for SIM messages used to perform maintenance activities. Used for exception conditions.

19ssblog.pdf: More detail on SSB formatting. Used for exception conditions. 20svpmsg.pdf: SVP messaging details. Used for exception conditions. 21web.pdf: Documents the procedure for installing/configuring the Web Console.

22nas.pdf: Documents the procedure for installing/configuring NAS Software. 23esm.pdf: Documents the considerations when doing maintenance or failure recovery actions for external storage.

24optver.pdf: Documents the micro-program version required for installing certain options.

Foundation Concepts HiSource


HiSource

14

HiSource is the Hitachi Data Systems application that contains the Bookshelves for the program products that run on the range of Hitachi Data Systems storage systems. Updated HiSource product documentation is issued twice per year, Spring and Fall.

Foundation Concepts Delivering High-availability Storage Services


Delivering High-availability Storage Services

15

• Installation and De-Installation Procedures– “Nondisruptive” means that the subsystem remains connected to the host

(OS) and continues to serve I/O. Nondisruptive Installation is done with the subsystem power on.

– “Disruptive” means that the subsystem or portion of the subsystem is disconnected from the host (OS). Disruptive Installation is done with the subsystem power off. There is a possibility that the reformatting is required and data lost.

– Nondisruptive procedures are preferred

– The ability to implement non-disruptive maintenance is also dependent on multi-path mapping decisions made by the customer. Multiple paths to the same storage must include distribution across both clusters of the storage system.

For customer environments designed for high-availability, nondisruptive maintenance is required.

As this course continues, you will learn how to determine what impact, if any, a particular maintenance task will have on the system’s availability and/or performance.

Note:

You should identify and follow the nondisruptive maintenance procedures whenever possible. Plans for nondisruptive maintenance should be reviewed with the customer. Verify that the customer’s multipath I/O implementation splits the I/O access among paths that will not be interrupted at the same time during the maintenance task.

Foundation Concepts ESD Protection is Mandatory


ESD Protection is Mandatory

16

Whenever you are working on the hardware, ESD protection is a mandatory precaution.

Whenever you touch any component inside the cabinet of a Hitachi Data Systems enterprise storage system, you must use anti-ESD protection. It is more commonly known as a grounding strap.

ESD damage can occur even if you do not detect any electricity transfer. ESD damage can be subtle and resulting problems may only be recognized later. Hitachi is able to analyze failed parts and identify when ESD damage is the cause.

Always use ESD protection when working on hardware. Make sure to use the correct ESD connection for the type of component being handled.

Use the search term “wrist” to locate instructions for where to connect the anti-static wrist strap.

Foundation Concepts Summary


Summary

17

• In this module on the Universal Storage Platform V Product Family and Documentation you learned about:

– New features of the Universal Storage Platform V and Universal Storage Platform VM enterprise storage systems

– Where to find the correct hardware documentation and maintenanceprocedures

– What functionality distinguishes enterprise storage systems – Why the use of anti-ESD protective equipment is mandatory when performing

hardware maintenance

This module has covered important information that you need to know in your role as a maintenance engineer for Hitachi Data Systems storage systems.

Foundation Concepts Review Questions


Review Questions

19

1. What is the characteristic that entitles a storage system to be categorized as “enterprise?”

2. What additional feature is available on enterprise storage systems that is not available on mid-range or modular storage?

3. Name the two important sources of documentation and information required by the maintenance engineer.

4. What is the third documentation component for the Universal Storage Platform V and Universal Storage Platform VM ?

5. Why is it mandatory to always use anti-ESD protection when performing hardware maintenance?


2. Back-end Architecture

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Identify the three different areas in which Hitachi implements virtualization in

the enterprise storage architecture– Describe back-end storage virtualization using the correct terms and

progression from physical storage at the RAID group level to the definition of an LDEV (logical device)

– Describe the back-end physical architecture of both the Hitachi Universal Storage Platform™ V (USP V) and Universal Storage Platform™ VM (USP VM), including the similarities and differences

– Define the terms RAID Group, Parity Group, Array Group, ECC Group, Emulation, PDEV, VDEV, LDEV, LDKC, CU, HDU, B4

– Describe how eight-drive Parity Groups are constructed in both the Universal Storage Platform V and Universal Storage Platform VM

– Describe the improved architecture of the back-end data loops

Back-end Architecture Virtualization – The Big “V” of Storage


Virtualization – The Big “V” of Storage

3

Virtualization External Storage (HitachiUniversal Volume Manager)

Virt

ualiz

atio

nH

ost/s

erve

r sto

rage

(LU

Ns)

Virtu

aliz

atio

n In

tern

al o

r Bac

k-en

d st

orag

e(L

DE

Vs)

LUN Address

Port Host Group LUN

LDEV Identifier

LDKC Control Unit LDEV

Storage System Serial NumberPortLUN

Hitachi has“wrapped” the physical storagein Virtualization layers on three sides

Back-endFront-end

External

Virtualization architecture inserts a logical address layer between the physical resource and how the consumer accesses that resource.

In the enterprise storage systems, Hitachi has implemented virtualization in multiple ways. The back-end and front-end virtualizations were introduced starting with the Hitachi Lightning 9900™ V series enterprise storage systems. Virtualization of external storage is first delivered through the Hitachi Universal Volume Manager software on the Hitachi Universal Storage Platform™ and Hitachi Network Storage Controller.

It is important for you to understand the concepts and structures of the back-end virtualization for maintenance purposes. It is possible that the customer data is damaged or destroyed when back-end components are replaced or installed in a Universal Storage Platform V (USP V) or a Universal Storage Platform VM (USP VM), when procedures are not properly followed.

Understanding the architecture and operation of these storage systems is important when performing maintenance tasks in the field.

Back-end Architecture RAID Groups and PDEVs


RAID Groups and PDEVs

4

RAID GroupParity GroupArray GroupECC Group

Supported RAID configurations

RAID 1+0 (2D, 2D)(4D, 4D)

RAID 5 (3D, 1P0(7D, 1P) also x2 or x4

RAID6 (6D, 2P)

Supported HDDs72 GB 15k rpm

146 GB 10K 15K

300 GB 10K15K

400 GB 10k750 gb SATA (7.5K rpm)

1 TB SATA (7.5K rpm)

PDEV

Physical Devicerefers to the total orraw capacity of all theHDDs in a RAID group

A set of HDDsconfigured to work together

EmulationMainframe or Open Systems

3390-3 OPEN-33390-9 OPEN-9

OPEN-V

HDD-1

HDD-2

HDD-3

HDD-4

HDD-1

HDD-2

HDD-3

HDD-4

Note: The terms and meanings covered here are the appropriate vocabulary for describing and discussing Hitachi enterprise storage. Other technologies, such as modular storage, or other vendors may use these terms in different ways.

At the physical level, individual hard disk drive (HDD) canisters work together in RAID group structures. Hitachi has determined a few RAID structures to be supported in the Universal Storage Platform V and Universal Storage Platform VM storage systems. A limited number of HDD canister types are also supported. Any supported HDD canister type can be used in any supported RAID structure. All the individual HDD canisters in one RAID group structure must be the same capacity and rotation speed.

In Universal Storage Platform V and Universal Storage Platform VM enterprise storage systems’ context, the terms RAID Group, Parity Group, Array Group and ECC (Error Correction Code) Group all have the same meaning. A RAID, Parity, Array or ECC Group is a set of 4 or 8 HDDs configured to work together to form hardware and firmware protected physical disk storage.

Note: There is more detailed information about the different RAID architectures and how they work to protect data at the physical storage layer in the Theory manual section of the Maintenance manual.

Back-end Architecture RAID Groups and PDEVs


Hitachi Data Systems supports only a few RAID structures: RAID 1+0 (2D,2D) or (4D,4D) RAID5 (3D,1P) or (7D,1P) also x2 or x4 for high read performance RAID6 (6D,2P)

Hitachi Data Systems supports a limited selection of HDD capacity and rotation speed combinations. You should review Hitachi Data Systems product announcements and documentation for expanded and retired HDD types.

Every RAID group also has an emulation attribute setting that must be defined when the RAID group drives are installed in the storage system and are configured as a RAID group. The emulation determines the maximum size of the logical device (LDEV) slices on that RAID group and also determines how the data is stored and accessed on the LDEV slices.

A little later in this course, the sparing out behavior of failed HDDs will be discussed.

The storage capacity described as PDEV (Physical Device) capacity includes the total, raw storage capacity of all the HDDs in the RAID group.

Note: Support for the 1TB SATA drives was announced in February 2008. The microcode 60-02-05 on which this course was based does not include the 1TB SATA drives.

SATA volumes can be used for Open-V and 3390-M devices. (3390-M is supported as of microcode release 60-03-05)

Use the appropriate documentation for the system on which you are performing maintenance.

Some of the SVP Application Maintenance dialogs use the term “PDEV” to mean the same as disk drive, HDD or canister. You may notice this use of the term PDEV when you learn about and practice maintenance procedures later in this course.

Back-end Architecture Supported RAID Structures


Supported RAID Structures

5


Four-drive RAID groups may be either

RAID 1+0 (2D, 2D)

RAID 5 (3D, 1P)

Two four-driveRAID groups may beconcatenatedto form an eight-drive group

RAID 1+0 (4D, 4D)

RAID 5 (7D, 1P)

RAID6 (6D, 2P)

Four HDDs always in the same B4Always within the same back-end domainor DKA feature

Eight HDDs always in two paired B4s in USP V, within the same B4 in USP VM. Always within the same back-end domain or DKA feature.

Hitachi has already determined which setsof HDDs may work together to formRAID groups. There is no flexibility in the choice of which HDDs form RAID groups.

The architecture of the Hitachi enterprise storage systems, including the Universal Storage Platform V and Universal Storage Platform VM, has a defined set of HDDs which can work together to form RAID groups.

A RAID group can be four or eight drives. To create an eight-drive RAID group, you concatenate two four-drive groups. The pairs of four-drive groups, that may be concatenated, have already been determined by Hitachi at the hardware architecture level. There is no flexibility or choice in which HDDs form the RAID groups.

When an eight-drive RAID group is constructed, the corresponding four-drive RAID groups in two different B4s are concatenated. You will learn about B4s in the module on Components.

All the drives in a RAID group, whether it is a four-drive group or an eight-drive group, are served by the same DKA feature.

Back-end Architecture Emulation


Emulation

6

• Emulation determines two LDEV attributes:– Maximum LDEV size– How the data is stored and accessed

on the LDEV

• Emulation is a hardware installation attribute.– It must be set at the time when the disk

drives of the RAID group are installedin the system by the maintenanceengineer.

• OPEN-V emulationdelivers the maximum storageutilization andthe best performance.

3390-9

OPEN-9

OPEN-V

metadata

7.384GB

8.514GB

48MB to entire VDEV

LDEV metadataNot used for OPEN-V

The emulation attribute determines the maximum size of LDEVs and how the data is stored and accessed within LDEVs. Emulation is set at the RAID group level and must be specified at the time the RAID group is installed in the storage system. It defines characteristics of the LDEVs yet it is a hardware attribute.

As of microcode 60-02-51 and 60-03-05-A, the RAID and/or emulation attributes of Parity Groups can be changed and there is no need to remove the HDDs from their slots. This process is documented and requires the setting of mode bit 721.

Before microcode 60-02-51 or 60-03-05A, on earlier enterprise storage systems or if mode 721 is not used, changing RAID structure or emulation requires the physical removal of the HDDs in the affected parity group(s).

Any of these maintenance procedures requires the Hitachi Data Systems CE or other field maintenance engineer. Customers are not permitted to perform hardware or disruptive procedures on the storage system.

LDEVs of all emulation except OPEN-V must allocate a small amount of the LDEV capacity to store metadata about the size and structure of the LDEV. Also, for all emulation except OPEN-V, every I/O must go through the LDEV metadata translation to get the correct data from or to the correct location within the LDEV.

Back-end Architecture Emulation


This adds a bit of performance overhead to every I/O operation. For OPEN-V emulation, this logic is provided within the system’s microcode.

Thus, Hitachi supports the fact that OPEN-V emulation provides the maximum available usable data capacity and always performs at least as well as any other emulation. The newer functions of Hitachi’s enterprise storage systems, pools for Hitachi Universal Replicator software, Hitachi Copy on Write Snapshot software and Hitachi Dynamic Provisioning software as well as the Universal Volume Manager software functionality are all based on OPEN-V LDEVs.

While you may encounter some customers who are using other emulations, particularly when providing mainframe storage, OPEN-V is likely to be the predominant configuration for open systems storage and newly delivered storage systems.

Back-end Architecture PDEVs and VDEVs


PDEVs and VDEVs

7

Virtual Device refers to theusable data capacityof a RAID group or PDEV

VDEV capacity depends on theHDD capacity, the RAID structureand the emulation

PDEV VDEV

Physical Devicerefers to the total orraw capacity of all theHDDs in a RAID group

The storage capacity described as PDEV capacity includes the total, raw storage capacity of all the HDDs in the RAID group.

The acronym VDEV stands for Virtual Device. Storage capacity described at the VDEV level is the customer’s usable data capacity and these numbers subtract the reported capacity by the storage that is required to keep the mirror copy of data in the RAID 1+0 configuration or by the capacity required to store the parity data in RAID5 and RAID6 structures.

Back-end Architecture LDEV– The Unit of Virtualized Back-end Storage


LDEV– The Unit of Virtualized Back-end Storage

8

VDEV

• At the Logical Device (LDEV) Level:

– Unit of storage administration for all Program Products

– Unit for provisioning– Unit for Replication – Unit for Volume

Migration– Unit for Data Retention– Definition unit for

external storageLDEV

PDEV

00:00:00

• The maintenance engineer may be responsible to define the LDEV structure of newly installed RAID groups.

• Storage must be formatted at the LDEV level before it can be used by programs or hosts.

What is an LDEV?

The LDEV is the basic or most granular unit of storage in the back-end of an Hitachi enterprise storage system.

An LDEV is a: Mappable set of physical data blocks, allocated out of a VDEV Physically stored on a RAID Group Has an emulation and size (in 512 byte data blocks) Identified by an LDKC:CU:LDEV number Looks like 00:00:00 Falls between 00:00:00 and 00:FE:FF

Up until the time this course material was developed, only LDKC 00 was supported. You should continue to review the Alerts and ECNs to determine if and when the extended LDKC becomes available.

It is important for maintenance engineer and/or storage administrators to understand the concept and structures of the back-end storage architecture to be

Back-end Architecture LDEV– The Unit of Virtualized Back-end Storage


able to define the LDEV structure when installing new RAID groups in a customer’s storage system.

The last step of installing new RAID groups is the formatting of the LDEVs. A new, Quick format option allows the storage to be used as LUNs while the actual formatting completes in the background. The Quick format requires one or more LDEVs to be specifies as “system disk.” System disk LDEVs can only be created through the SVP application interface. If normal, “slow” formatting is used, the storage cannot be used by any software or hosts until the LDEVs have been formatted.

LDEV is the foundation element in the back end of a Hitachi enterprise storage system. All the microcode products manage storage at the LDEV level including LUN Mapping, Dynamic Cache Residency, Volume Migration, Data Retention Utility and the range of replication products including Hitachi ShadowImage® Heterogeneous Replication software, Copy on Write Snapshot software, Hitachi TrueCopy® software products and Universal Replicator software. Hitachi Dynamic Provisioning software also relies on the concept and structure of LDEV for both its dynamic provisioning (DP) Pool volumes and its defined DP Virtual volumes (V-VOLs).

The addition of the logical disk controller (LDKC) structure to the identification of LDEVs has expanded the number of LDEVs that can be identified from 16,384 on Universal Storage Platform and Network Storage Controller to 65,280 on the Universal Storage Platform V and Universal Storage Platform VM storage systems.

Even though Hitachi Data Systems has defined an LDEV as a mappable set of physical data blocks that reside on physical storage, an LDEV, with its LDEV identity, is a virtual component. It is possible to move or migrate an LDEV from one physical location to another. This makes the LDEV address, identity or pointer a virtual identifier that sits between the user of the data and the keeper of the data.

There are some additional structures and concepts we need to define regarding the structure and identification of back-end storage.

Note: Hitachi will support more LDKC values in the future. (As of Universal Storage Platform V/VM GA1, only LDKC 00 is supported.)

One way of implementing virtualization in the back-end storage architecture is by using Shared Memory tables, Control Units to identify LDEVs.

More detail about how data is identified, managed and stored within the storage system can be checked in the Theory section of the Maintenance manual.

Back-end Architecture VDEV– LDEVs or Free Space


VDEV– LDEVs or Free Space

9

OPEN-V

48MB to entire VDEV

OPEN-V

OPEN-V

48MB to entire VDEV

Free space

EitherLDEV(s)orFree spaceor both

VDEV48MB to entire VDEV

Installed Parity Groups can be formatted as one or more LDEVs, or part or all of the VDEV capacity may be left as free space.

The customer’s storage administrator can create LDEVs out of free space after the storage system is in production. There are trade-offs to this approach to provisioning. This will be covered in detail later.

Free space is not given back-end or an LDEV address. It is just “free space on a VDEV.”

Back-end Architecture Shared Memory Stores Control Unit Tables


Shared Memory Stores Control Unit Tables

10

1. Configuration2. Cache Pointers3. Control Unit Tables (CU)4. I/O Instruction Queues5. Copy product delta bitmap tables6. Virtual Volume DMT

(Dynamic Mapping Tables)

Shared Memory

Cache Memory

DIMMS on the SMA DIMMS on the CMA

As you know, LDEVs get identifiers that consist of LDKC, CU and LDEV. The terms and concepts of LDKC have been covered earlier. Let’s examine what is a control unit (CU) to completely understand the assignment of LDEV numbers.

CU assigns unique identity to the mappable slices of disk storage that we refer to as LDEVs. It is a table in the Shared Memory.

What is a Shared Memory?

One of the strengths of Hitachi’s enterprise storage architecture is the total separation between customer data and the data and information that is necessary to operate the storage system. The information needed to cause the “wires and metal” of the storage system to move and store data is called control information. The area of memory used to store, access and manipulate this control information is sometimes referred to as control memory or shared memory (SM).

Hitachi enterprise storage systems always store the customer application data in data cache or cache memory. Cache memory and shared memory are separated at the hardware level. The memory DIMMS for cache memory and shared memory are physically separate and are installed on physically separate printed circuit boards in the system’s logic box slots.

Back-end Architecture Control Unit - A Shared Memory table


Control Unit - A Shared Memory table

11

• On a USP V and VM, it is possible – To identify up to “64k” LDEVS – LDKC 00– CU 00 – FE (255)– Each CU maps 256 LDEVs– 255 x 256 = 65,280

• LDEV ID assignment is required for each internal and external (virtual) LDEV

x x x x x x x x xx x x x x x x x x

CU 00

x x x x x x x x xx x x x x x x x x

CU FE

CU FF

Reserved for system use

Not available for LDEVs

Shared Memory – Control Unit (CU) Tables

LDKC 00OtherShared Memorydata

LDEV 00:00:07

A Control Unit is a table in Shared Memory. Each Control Unit table has 256 (hex FF) entries. Control Unit tables are used to identify LDEVs. Each entry in a Control Unit table is referred to as an LDEV number.

Universal Storage Platform V and Universal Storage Platform VM have a logical structure called the Logical Disk Controller or LDKC. An LDKC is a set of Control Unit tables. Each LDKC contains 256 (hex FF) control unit tables. However the highest or “FF” CU table is reserved for system use and cannot be used to identify LDEVs. Within one LDKC, 256 LDEVs in each of 255 CU tables can be identified. One LDKC can identify 255 x 256 or 65,280 LDEVs. This is four times as the maximum number of 16,384 LDEVs that can be identified by the 64 CUs on a Universal Storage Platform or Network Storage Controller.

Back-end Architecture Parity Group-> PDEV-> VDEV-> LDEV


Parity Group-> PDEV-> VDEV-> LDEV

12

• Universal Storage Platform V and Universal Storage Platform VM Virtual back-end Structure Review

VDEV LDEVPDEV

Parity GroupRAID GroupArray GroupECC Group

PG(1-1)

(1-1)-1

LDKC:CU:LDEV

00:00:00through00:FE:FF

This page and the following pages identify the different structures that make up the back-end of a Universal Storage Platform V and Universal Storage Platform VM enterprise storage system. This virtual architecture is identical to what was implemented on the Universal Storage Platform and Network Storage Controller. The primary difference is the addition of the logical LDKC as a component of the LDEV identifier. This allows more LDEVs to be identified and used on Universal Storage Platform V and Universal Storage Platform VM.

This page presents a summary of the Parity Group to PDEV to VDEV to LDEV structures. You should now understand the meaning and use of these terms, in terms of Universal Storage Platform V and Universal Storage Platform VM enterprise storage systems.

Now, let’s get back to the hardware architecture to understand Maintenance and Installation operations better.

Back-end Architecture Parity Group Identifier


Parity Group Identifier

13

• In order to know which HDDs are part of the Parity Group, you must also know the RAID structure, particularly whether it is a four-drive or an eight-drive group.

• When you know the Parity Group identifier and the number of HDDs in the Parity Group, you can go to the storage system and physically locate all the HDDs that make up the Parity Group. (The Locations section of the Maintenance manual may help.)

In the SVP Application, Web Console and Storage Navigator, Parity Groups are identified by a number that looks like PG(1-1) or PG(4-3). The first number on the left of the dash identifies the B4. The second number, after the dash, identifies the Parity Group within the B4.

Each ‘four-drive’ parity group is identified even if the customer is using the storage in eight-drive parity groups.

At this point, it is important to remember that the RAID group and Parity Group describe the same components from the maintenance engineer’s perspective. When you are adding additional storage to a customer’s system, you will specify how many RAID groups of what structure are to be added. Then the SVP application, in the Change Configuration --> Install --> DKA + ECC Group + LDEV dialog box will tell you which Parity Groups will be created.

Back-end Architecture Universal Storage Platform V



14


Back-end Architecture Parity Group to HDD Cross Reference


Parity Group to HDD Cross Reference

15

• Universal Storage Platform V

A set of tables in section: Theory 05-30 in the Universal Storage Platform V Theory manual: 12theory.pdf identifies which Parity Group an HDD belongs to, depending on the RAID structure of the Parity Group. This page shows the table for the HDDs in HDU4 in the R0 cabinet.

Notice that these HDDs become part of the parity group from B4(1) when the RAID structure is eight-drives.

Back-end Architecture Storage Physical Architecture


Storage Physical Architecture

16


Here is a diagram of a five cabinet Universal Storage Platform V. This diagram is taken from the Locations section (03loc.pdf), page LOC01-10.

Over the next few pages, the components in the physical back-end storage architecture of the Universal Storage Platform V will be covered.

This includes the physical structures of the HDU, HDU Box, DKU and B4.

The physical and logical architectures merge in the Parity Group structure.

Back-end Architecture Four-drive RAID Groups, HDUs and B4s


Four-drive RAID Groups, HDUs and B4s

17

• Universal Storage Platform VB4-2

HDU0

HDU1

HDU2

HDU3

HDU4

HDU5

HDU6

HDU7

B4-1B4-1 B4-2

In the Universal Storage Platform V (USP V), an HDU is a set of 16 HDDs, served by the same set of DKA back-end data loops and served by a pair of Fabric Switch Module (FSW)s and a pair of SVRs.

Four HDUs make a “B4” or “Box of 4.” The four HDDs that make up a four-drive RAID group exist within one B4, with each of the four HDDs coming from a different HDU within the B4.

Another way to identify the HDDs that make up a four-drive RAID group is: The set of corresponding HDDs in four HDUs that constitute a B4. “Corresponding” means the drives in the HDD slots that have matching HDD slot ID numbers in each of the HDUs in the B4.

Remember that the four-drive RAID group structures are RAID 1+0 (2D,2D) and RAID5 (3D,1P). If the customer back-end RAID group configuration is made entirely into four-drive RAID groups, each B4 can have 15 four-drive RAID groups.

The sets of HDUs that make up the B4s are prescribed by the back-end data loop architecture. This cannot be changed.

The first four-drive RAID group would be built in B4 1 which is made of HDU0, HDU1, HDU2 and HDU3. HDU0 and HDU1 are found in the front of the R0 cabinet



of the Universal Storage Platform V. HDU2 and HDU3 are found in the rear of the R0 cabinet.

The HDD component ids for the drives in the first four-drive RAID group are HDDR00-00, HDDR01-00, HDDR02-00 and HDDR03-00.

You can see the HDU number and the drive number within the HDU in the HDD component identifier.

HDU4, HDU5, HDU6 and HDU7 make up B4-2.

RAID groups must always be added in sequential order, filling the next set of HDD slots within the B4 without leaving any gaps. RAID groups may be added in any connected B4 but there may not be skipped HDD slots within a B4 or set of HDUs.

If a drive is installed in HDD slot 0F in any HDU is always behaves as a spare; HDDs in the 0F slots may not be configured into RAID groups.

As a maintenance engineer, you need to understand both the naming pattern and locations of individual HDD units. If an HDD fails, the maintenance process requires that you identify and replace the failed HDD unit. In the SVP interface, the failed HDD will be identified by its HDD location ID such as HDDR00-00 or HDDR17-0C.You should use the Locations section of the Maintenance manual to identify and/or confirm the location of any HDD that you intend to replace.

As a maintenance engineer, if you are called on to add storage capacity at a customer site, you will “install new RAID groups” which will include the installation of additional HDD units in the correct HDD slots.

Different methods are used for maintenance storage capacity versus installation (or De-Installation) storage capacity. Maintenance procedures identify HDDs, Installation procedures identify RAID groups (which in turn determine the specific HDD units).

This is why you must understand the storage system architecture including which HDDs comprise which RAID groups. And this is why the concept and definition of the B4s is important for you to understand.

Note:

The above diagram is taken from Locations section (03loc.pdf), page LOC02-10. The Locations section identifies the individual HDDs, HDUs and HDU boxes. At this time, the B4 layout is not identified in the manual.

Back-end Architecture Eight-drive RAID Groups, HDUs and B4s


Eight-drive RAID Groups, HDUs and B4s

18


HDU0

HDU1

HDU2

HDU3

HDU4

HDU5

HDU6

HDU7

B4-1B4-1 B4-2B4-2

An eight-drive parity group is composed of the two corresponding four-drive parity groups across the two B4s that work together. Eight-drive parity groups can be built across B4-1 and B4-2, B4-3 and B4-4, B4-5 and B4-6, and more.

Nobody individually has a choice in which HDDs make up the parity groups! The customer along with Hitachi decides what and how many RAID structure are needed. When the RAID structure is specified, including number of drives in the RAID group, the SVP configuration interface will calculate which parity groups will be installed. As the maintenance engineer, it is up to you to confirm that HDD units are installed in the corresponding HDD slots in the correct HDUs.

Since eight-drive Parity Group is built from the two corresponding four-drive Parity Groups across two B4s, the Parity Group identifier of an eight-drive group will be:

PG(1-1)(2-1)

Only corresponding four-drive Parity Groups across two B4s can be used to construct RAID5 (7D,1P) or RAID6 (6D,2P).

If a customer has installed three four-drive Parity Groups in B4(1). These Parity Groups would be PG(1-1), PG(1-2) and PG(1-3).

Back-end Architecture Eight-drive RAID Groups, HDUs and B4s


Now, the customer wants three eight-drive Parity Groups. What Parity Groups and HDDs will have to be installed?

Since Parity Groups 1-1, 1-2 and 1-3 are four-drive groups, four-drive groups must also be installed for Parity Groups 2-1, 2-2 and 2-3. Only then, can three eight-drive Parity Groups be added at PG(1-4)(2-4), PG(1-5)(2-5) and PG(1-6)(2-6). No skipped HDD slots in any B4.

Note:

The above diagram is taken from Locations section of the Maintenance Manual, page LOC02-10.

Back-end Architecture How DKA Pairs Connect to B4s


How DKA Pairs Connect to B4s

19

• Universal Storage Platform V Domain

B4

DKU-R0B4

DKC610IDKU-L2

L1 (Upper)

B4B4

L1 (Lower)

B4B4

L2 (Upper)

B4

L2 (Lower)

B4B4

R1 (Upper)

B4B4

R1 (Lower)

B4B4

R2 (Upper)

B4B4

R2 (Lower)

B4B4

DKU-L1 DKU-R1 DKU-R2

1st2nd

3rd4th

5th6th

7th8th

DKA

DKA

DKA

DKA

B4

12

4 3

6 5

8 7

10 9

12 11

14 13

16 15

18 17

Each set of back-end data loops and the storage it serves is called a “domain”

A Universal Storage Platform Vcan have between one and four domains

A fully populated Universal Storage Platform V will have 18 B4s. Each B4 has 4 HDUs so there are 72 HDUs in a fully populated Universal Storage Platform V.

The HDUs within a B4 will all be served by the same set of back-end data and control loops. For eight-drive parity groups which span two B4s, the two B4s are served by the data loops on the set of Disk Adaptors (DKA) PCBs (pair of pairs) that work together.

The term “domain” is sometimes used to describe a set of back-end loops and the storage served by them. A Universal Storage Platform V can have between one and four back-end domains.

The diagram on this page shows how the fully extended DKA back-end loops serve the B4s as the storage system grows to its full capacity. Notice that the first set of back-end loops serve the two B4s in the top of the DKC, R0 cabinet. Then, when more storage is needed, the R1 cabinet is added and the data loops from the first set of DKA PCBs are extended to serve the B4s in the bottom half of the R1 cabinet. When the R2 cabinet is added, these same data loops will serve the two B4s in the bottom of the R2 cabinet.



When parity groups are added to the top of R1 and/or R2, these second set of DKA adapters, DKA pairs 3 and 4 will be added. The back-end data and control loops from these DKAs will serve the B4s in the top half of R1 and R2.

Following the schematic connections from DKA pairs 5 and 6 you can see that these back-end loops will serve the B4s in the bottom half of L1 and L2 cabinets. The last set of DKAs, pairs 7 and 8 will serve the B4s in the top half of cabinets L1 and L2.

Back-end Architecture Back-end Loop Speed


Back-end Loop Speed

20


Power supply boundary

Rear / Cluster 2

1LU 1KU 1JU 1HU 1GU 1CE 1SA 1CA 1FU 1EU 1DU 1BU 1AU

DKA1

CHA6

CHA1

CHA5

CHA2

DKA6/CHA11

CSW2

CSW0

DIMMDIMM

DIMM DIMMDKA5/CHA12

Front / Cluster 1

SMA1

DIMM

DIMMCMA3

CMA1

DKA2

Logic PL

PCB Location

PCB Location

DKA3/CHA14

CHA8

CHA3

CHA7

CHA4

DKA8/CHA9

CSW3

CSW1

DKA7/CHA10

SMA2

CMA4

CMA2

DKA4/CHA13

2XL 2WL 2VL 2UL 2TL 2CD 2SB 2CH 2RL 2QL 2PL 2NL 2ML

CHA7

CHA8

DKA4/CHA13

CHA3

CHA4

DKA7/CHA10

CSW3

CSW1

DKA8/CHA9

CMA2

CMA4

DKA3/CHA14

SMA1

2XU 2WU 2VU 2UU 2TU 2CC 2SD 2CG 2RU 2QU 2PU 2NU 2MU

CHA5

CHA6

DKA2

CHA1

CHA2

DKA5/CHA12

CSW2

CSW0

DKA6/CHA11

CMA1

CMA3

DKA1

SMA2

Option5 Option6 Option2 Option6 Option5 Option1 Option2 Option3 Option2 Option1 Basic Option2 Option1

PCB Location

1LL 1KL 1JL 1HL 1GL 1CF 1SC 1CB 1FL 1EL 1DL 1BL 1AL

Upper

Lower

Lower

Upper

PCB Location

Option7 Option8 Option3 Option8 Option7 Option2 Option1 Option4 Option4 Option3 Option1 Option4 Option3

Option5 Option6 Option2 Option6 Option5 Option3 Option1 Option1 Option2 Option1 Basic Option2 Option1

Option7 Option8 Option3 Option8 Option7 Option4 Option2 Option2 Option4 Option3 Option1 Option4 Option3

DK

A pair 1&

2D

KA

pair 3&4

DKA pair 5and 6

DKA pair 7and 8

USP V back-end loop speed must be set toeither 2Gbit/sec or 4Gbit/sec at DKA installation

In the Universal Storage Platform V (USP V), back-end data loops now have the ability to operate at 4 gigabits per second (Gbit/sec). The Universal Storage Platform and Network Storage Controller back-end loops operated at 2Gbit/sec.

There are some requirements for operating the Universal Storage Platform V back-end loops at 4Gbit/sec.

First, the back-end data loop speed attribute must be selected when the DKA PCBs are installed into the Logic Boxes. If the back-end loop speed is selected to be the lower 2Gbit/sec, then HDDs that are capable of 4Gbit/sec data transfer will operate satisfactorily but will run at the lower 2Gbit/sec speed.

If the back-end loops of the DKA are configured for 4Gbit/sec operation, then you and the customer must ensure that only HDDs capable of operating on 4Gbit/sec loops are installed on those loops. If you install HDDs that are only capable of 2Gbit/sec operation on 4Gbit/sec loops, the HDDs will fail.

Also, only one back-end loop speed may be selected for a set of DKAs (pair of pairs) that get installed as a unit. All eight sets of back-end loops on a pair of DKA pairs must be configured to operate at the same speed, either 2Gbit/sec or 4Gbit/sec. It is permitted to mix 2Gbit/sec and 4Gbit/sec back-end loops in one Universal Storage

Back-end Architecture Back-end Loop Speed


Platform V, but the configuration granularity is at the DKA unit of installation or a set of eight back-end data loops.

The option for two different backend data loop speeds in the Universal Storage Platform V adds restrictions to which spare drives are available to hold the data of a failed or failing data drive. The Universal Storage Platform V rules for sparing are that a failed or failing HDD can be spared out to spare drive of:

Same interface type (FC or SATA) Equal or greater capacity Same rotation speed Same backend data loop speed

Back-end Architecture Disk Unit Architecture


Disk Unit Architecture

21


HDU Box

HDU Box

The diagram on this page shows the HDU numbering for the DKU cabinets in an Universal Storage Platform V. This diagram is taken from the Locations section of the Maintenance manual (03loc.pdf) page LOC02-10.

In the physical architecture of the Universal Storage Platform V, an HDU box is a physical component that holds four HDUs for a total of 64 HDDs, either in the front or rear of the R0 cabinet. Each DKU cabinet can hold up to four HDU boxes.

The HDU box is different from a B4. A B4 is made up of two HDUs from two different HDU boxes.

The HDU boxes do not have separate component IDs. When a DKU is added, the lower two HDU boxes are part of the standard configuration. An expansion kit component must be ordered when the upper HDU boxes are added.

The definition of the HDU box can be found in the Theory section of the Maintenance manual.

Back-end Architecture Universal Storage Platform VM



22


Back-end Architecture Physical Storage Architecture


Physical Storage Architecture

23

• Universal Storage Platform VM

Here is a diagram of a Universal Storage Platform VM showing the full, two rack configuration. This diagram is taken from the Location section of the Maintenance manual (03loc.pdf) page LOC01-10.

On the next few pages, the HDU and B4 of the Universal Storage Platform VM are covered. These are different as compared to the structure and definition for the larger, Universal Storage Platform V system.

All the HDDs in a Universal Storage Platform VM are installed and accessed from the front of the racks, only. There are no HDDs in the rear of the Universal Storage Platform VM racks. The rear section of the Universal Storage Platform VM racks, behind the DKU Boxes, has the Power Supplies and FSWs.

Let’s examine how four-drive and eight-drive Parity Groups are constructed in the Universal Storage Platform VM.



Four-drive RAID Groups, HDUs and B4s

24

B4


PG(1-1) a four-drive Parity Group

B4

The physical architecture of the Universal Storage Platform VM is different from the Universal Storage Platform V.

For the Universal Storage Platform VM, an HDU is a “tray” of 15 HDDs.

Two HDUs are served by two FSWs. In a Universal Storage Platform VM, 30 HDDs are served by two FSWs as compared to 16 in the Universal Storage Platform V.

The Universal Storage Platform VM does not use the SVR HDD power supply component.

The documents in the MDL for the Universal Storage Platform VM also use the terms HDU Box and Disk Chassis to describe the component that holds four HDUs. In the diagram on this slide that is taken from the Locations section of the Maintenance manual (03loc.pdf) page LOC02-30, the set of four HDUs has a component identifier of DKU-Rx. A fully populated Universal Storage Platform VM can have four DKUs, each with 60 HDDs.

The Universal Storage Platform VM has only one set of DKA which support eight back-end data loops. Like the Universal Storage Platform V, the back-end data loops are configurable to operate at either 2Gbit/sec or 4Gbit/sec. This must be



determined when the DKAs are installed. Changing the back-end loop speed is a disruptive change.

Four-drive Parity Groups are built in the same way as in the Universal Storage Platform V. A four-drive Parity Group is made up of the four corresponding HDDs in the four HDUs that are configured to work together as a B4. In the Universal Storage Platform VM, each DKU also directly corresponds to a B4. So, the diagram on this page showing the four HDUs within a DKU also represents the four HDUs in a B4.

In the Universal Storage Platform VM, Parity Groups are identified in the same way as on the Universal Storage Platform V: PG(1-1). The Parity Group identifier is the B4 followed by the four-drive Parity Group within the B4.

So, Parity Group PG(1-) would be made up of HDDs HDD00-00, HDD01-00, HDD02-00 and HDD03-00. Notice that the identifiers of the individual HDDs are different from the Universal Storage Platform V.

Back-end Architecture Eight-drive RAID Groups


Eight-drive RAID Groups

25

B4

PG(1-1)(1-2) An Eight-drive Parity Group


B4

Eight-drive Parity Groups are also constructed differently as compared to the Universal Storage Platform V.

Eight-drive Parity Groups are built using two contiguous four-drive Parity Groups, starting with an odd-numbered Parity Group. This means that PG(1-1) and PG(1-2) can be configured to work together as an eight-drive Parity Group. However, contiguous four-drive groups cannot be used together if the first Parity Group is an even numbered group.

The valid sets of four-drive Parity Groups that may be used together as eight-drive Parity Groups are (1-1)(1-2), (1-3)(1-4), (1-5)(1-6), and more.

If the customer has configured a four-drive Parity Group in an odd numbered slot, then the next even numbered four-drive group must also be installed as a four-drive Parity Group, only. After that, the customer may configure eight-drive Parity Groups in the permitted sets of slots.

A Universal Storage Platform VM will support up to four B4s.

Note:

The above diagram is taken from Locations section of the Maintenance manual: 03loc.pdf page LOC02-30



How DKA Pairs Connect to B4s

26


The Universal Storage Platform VM supports only one set of eight back-end data loops, four from Cluster 1 and four from Cluster 2. This means that when fully populated, each loop supports 60 HDDs.

In the Universal Storage Platform VM, the back-end data loops operate only at 4Gbit/sec.

Back-end Architecture Back-end Comparison


Back-end Comparison

27

USP V USP VM

Maximum number of B4s 18 4

HDDs per B4 64 60

Maximum back-end data loops 64 8

Maximum HDDs including spares 1152 240

Maximum HDDs per data loop 48, 32 60

Diskless configuration supported no yes

Universal Storage Platform V and Universal Storage Platform VM

This page summarizes the physical back-end storage architecture comparison between the Universal Storage Platform V and Universal Storage Platform VM systems.

The logical architecture of the storage is the same between the Universal Storage Platform V and Universal Storage Platform VM but there are significant differences in the way the physical components are installed and configured. The physical back-end storage structures make it possible to create, identify and use the LDEVs.

Back-end Architecture Back-end Loop Enhanced Design


Back-end Loop Enhanced Design

28

• Universal Storage Platform V FSW Loop Switch Improvement to the Intelligent Port Bypass Circuit

DKF

HDD1 HDD2 HDD3 HDD4

FSWSWITCH

On of the architecture changes in the Universal Storage Platform V and Universal Storage Platform VM is the addition of switched architecture on the back-end data loops. This improves the performance of the back-end data loops and also improves the stability of the back-end loops when an HDD fails.

The switch layer did not exist in the Universal Storage Platform and Network Storage Controller architecture.

Back-end Architecture Summary


Summary

29

• You have Learned– Hitachi has implemented storage virtualization in the back-end, front end and

also for externally attached storage.– There are logical and physical architectures in the back-end storage of

Universal Storage Platform V and Universal Storage Platform VM storage systems

– The physical back-end storage architectures of the Universal Storage Platform V and Universal Storage Platform VM are different

• You should be able to – Correctly define and use the terms RAID Group, Parity Group, Array Group,

ECC Group, PDEV, VDEV, LDEV, B4, HDU for both the Universal Storage Platform V and Universal Storage Platform VM storage systems

– Use the Locations section, the Theory section and the Table of Contents in the 04inst3.pdf Installation section for both the Universal Storage Platform V and Universal Storage Platform VM


3. Components

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Identify the hardware components of a Hitachi Universal Storage Platform™ V

and Hitachi Universal Storage Platform™ VM storage systems– Describe the multi-cabinet structure of a Universal Storage Platform V– Describe the two rack structure of a Universal Storage Platform VM– Identify the options and features in the logic box– List the printed circuit board (PCB) options and the respective slot locations

for the Universal Storage Platform V and VM– Use the Maintenance manual to identify and locate all components in a

Universal Storage Platform V and VM storage system

Components Hardware Block Diagram


Hardware Block Diagram

3

• Universal Storage Platform VCluster1 Cluster2

Hi-StarInternalCrossbarnetwork

This hardware block diagram, taken from the Theory section of the Maintenance manual, is for a Universal Storage Platform V storage system. The main components represented include the disk controller (DKC), disk adaptor (DKU) and Power Supply sections. The DKC and DKU represent the components that “move the data” through the storage system. The Power Supply section delivers the power that enables the storage system to function. The main components of the DKC are the five PCB types that are installed in the Logic box slots: 1. Shared Memory SMA 2. Cache Memory CMA 3. Cache Switch CSW 4. Disk Adapters DKA 5. Channel Host Adapters CHA

The internal paths that connect the DKC components constitute the internal Hi-Star™ crossbar switch architecture.

The Power Supply section includes the AC Boxes, Power Supplies and Batteries. Remember, a cluster is a set of components that share the same power source. The Universal Storage Platform V supports multiple CMA, SMA and CSW features.

Components Hardware Block Diagram


4

• Universal Storage Platform VMCluster1 Cluster2

Hi-StarInternalCrossbarnetwork

The hardware block diagram for a Universal Storage Platform VM storage system from the Theory section (12theory.pdf) in the Maintenance manual is shown above. Like Universal Storage Platform V, the main components represented include the DKC, DKU and Power Supply sections as well.

The Universal Storage Platform VM supports only one feature for the SMA, CMA and CSW.

Components Data Movement Components


Data Movement Components

5


External storage

Remote replication

Host I/O

Control Data

Customer Application DataHDDs

Shared Memory

Cache Memory

CHADKA

CSW

CHA Ports

Logic Box

microcode

DKC

The storage system moves customer data to and from the HDDs. Data moves through components in the back-end and front-end of the storage system. The back-end includes the DKA PCBs which include the DKP microprocessors. The DKA data cables connect to the fibre switch modules (FSWs) which connect to the HDDs. The data moves through the Cache Switches (CSWs) into the Cache Memory. From there, data moves through the CHA and CHA Front-end ports, out to the SAN and hosts. Shared Memory contains the control information that controls the movement of data in the storage system.

Components Data Components Chart


Data Components Chart

6

Micro-programDistributed across multiple components throughout the storage system

Microcode

canisterIndividual data storage canisters

Hard Disk DriveHDD

BED – Back-End Director ACP – Array Control PairDKF – Disk Control FeatureDKP – Disk Control Processor

PCB in the Logic BoxDisk AdapterDKA

FED – Front-End DirectorCHF – Channel Host FeatureCHP – Channel Host Processor

PCB in the Logic BoxChannel Host AdapterCHA

PCB in the Logic BoxShared Memory AdapterSMA

PCB in the Logic BoxCache SwitchCSW

PCB in the Logic BoxCache Memory AdapterCMA

SynonymsLocationComponent NameCOMPONENT Abbreviated Name

This chart shows the component name, abbreviated name, physical location of the component and any synonym names for the data movement components of both a Universal Storage Platform V and Universal Storage Platform VM storage system.

Components Support Components


Support Components

7


Maintenance PC connection port

Support components deliver the power, cooling and management control options to the data movement functionality of the storage system.

Support components include: Power Supplies

SVR power supply for the HDD Power Cables Batteries Fans SVP Operator Panel EPO Switch Maintenance PC connection port

Components Support Components


8

Maintenance PC connection port


LEDPNL

LEDPNL

LEDPNL

LEDPNL

A Universal Storage Platform VM (USP VM) has most of the support components available as in a Universal Storage Platform V. They are found in different physical locations due to the different physical configuration of the Universal Storage Platform VM as compared to a Universal Storage Platform V. Use the Locations section of the Maintenance manual for the Universal Storage Platform VM to locate the physical components.

The Universal Storage Platform VM does not use the SVR.

In Universal Storage Platform VM, power for the HDDs is delivered directly by the DKUPS Power Supplies. It uses the LEDPNL component to house the HDD status lights.

Components Overall Component Schematic


Overall Component Schematic

9

The support components make it possible for the data movement components to deliver the I/O functionality of the storage system.

Both, data movement and support components, are integrated into the physical architecture. The Locations section of the Maintenance manual is the guide to finding the specific component in either type of storage system, Universal Storage Platform V or Universal Storage Platform VM. Both systems have the same components, just in different locations.

One exception is that the Universal Storage Platform VM does not use the SVR component for supplying power to the HDDs.

It uses the LEDPNL component for the HDD status LEDs.

The Channel Host Adapter ports and the fibre channel connections to the SAN, hosts, servers and possibly other storage systems constitute the Front-end. Disk Adapters, back-end data and control cables, Fibre Switches and the HDDs themselves, and the LDEVs constitute the Back-end.

Components Universal Storage Platform V



10


Components Cabinet Overview


Cabinet Overview

11


A Universal Storage Platform V storage system may consist of between one and five cabinets. The first cabinet always contains the DKC and the first DKU is identified as DKU-R0.

The DKC cabinet holds the front and rear Logic Boxes. The front Logic Box is also identified as Cluster1. The rear Logic Box is identified as Cluster2.

Each cluster constitutes a fully functioning storage system. It is the two clusters working together for redundant data access paths that deliver the high availability that is one of the strongest features of the Universal Storage Platform V system.

Components Logic Box


Logic Box

12


•

UPPER

LOWER

The Locations section of the Maintenance manual has diagrams of the Logic Boxes, the Logic Box Slot identifications, which kind of PCB is installed in the respective slots and in which sequence the Logic Box slots are filled.

When a Logic Box slot is identified as “Basic,” the PCB component that goes in this slot is part of the Base Minimum Configuration. This means that there must be a PCB in this slot whenever the storage system is in operation.

It is important to know how to interpret the information on the Logic Box PCB Location diagrams.

Components Power Supply Section


Power Supply Section

13


In a Universal Storage Platform V, the ACBoxes are found in the rear. There are Power Supplies in both the front and rear. The Batteries are found in the front of the DKC cabinet.

Components Setting the Frame ID


Setting the Frame ID

14


When a Universal Storage Platform V has multiple cabinets, each cabinet must be configured for its position within the overall system.

A cabinet’s position is determined by a combination of jumper settings on the PSPNL and switch position of the toggle switches on the Fibre Switch boards.

Whether a cabinet is part of the original system configuration or is being added in the field, the cabinet should have been correctly configured before shipping. However, it is imperative that you check and verify the PSPNL jumper settings and Fibre Switch toggle setting for the cabinet identification. Use the Locations section of the Maintenance manual to review and confirm the jumper and switch settings.

Components Back-end Cabling and B4s


Back-end Cabling and B4s

15


The concept of a B4 is important because this is the part of the identity of a parity group. In a Universal Storage Platform V, the first two B4s are in the DKC cabinet. Each DKU cabinet can contain four B4s. A fully populated Universal Storage Platform V can have 18 B4s.

In the above diagram, the B4 numbering and layout is shown for a Universal Storage Platform V.

Components DKU Component ID


DKU Component ID

16


HDDRnx_dd

HDDLnx-dd

n = Cabinetx = HDU numberdd = HDD number

Individual HDD canisters, SVRs, FSWs, Power Supplies and Batteries are identified by Component IDs.

The Cabinet ID, R0, R1, R2, L1, L2 identify the cabinet in which the component is located.

The HDU number is part of the component identifier of an FSW, SVR or HDD.

Use the Locations section of the Maintenance manual to help identify the component and its location.

Components CHA Ports– One Port per Microprocessor


CHA Ports– One Port per Microprocessor

17

1A

3A

1B

3B


Channel Host Port identification diagrams are found in the Locations section of the Maintenance manual. Cluster1 and Cluster2 CHA Port diagrams for a Universal Storage Platform V are shown above. This page shows the four-port CHA PCB. These CHA PCBs are used in both the Universal Storage Platform V and Universal Storage Platform VM. On a four-port CHA PCB, each port is served by one microprocessor. The ratio of microprocessors to ports is 1:1. The top two ports share the same letter label and these two ports constitute a port block. The lower two ports also share the same letter label and also constitute a separate port block. Channel Host Port identification diagrams are found in the Locations section of the Maintenance manual. Cluster1 and Cluster2 CHA Port diagrams for a Universal Storage Platform V are shown above. On four-port CHA cards, one DKP microprocessor performs the I/O for one port. The microprocessor to port connections are shown on the left. The first CHA feature is described as “Basic.” These PCBs will be installed in Logic Box slots 1EU in Cluster1 and 2QU in Cluster2. A set of two CHA ports makes up a CHA port block. The ports in a port block share the same letter.

Components CHA Ports– High Density


CHA Ports– High Density

18

1A

3A

5A

7A

1B

3B

5B

7B


This diagram describes the high-density CHA PCBs that are supported for both the Universal Storage Platform V and Universal Storage Platform VM.

On eight-port, high-density cards, one DKP microprocessor performs the I/O for two ports. The microprocessor to port connections are shown on the left.

The first CHA feature is described as “Basic.” These PCBs will be installed in Logic Box slots 1EU in Cluster1 and 2QU in Cluster2.

A set of four CHA ports makes up a CHA port block. The ports in a port block share the same letter.

Components SFP Transceivers


SFP Transceivers

19

SFP Transceivers are field replaceable. CHA PCBs are delivered with short wavelength SFPs. Short wavelength SFPs are identified by the black band on the SFP latch. Long wavelength SFPs have blue on the latch. If the customer wants to replace short wavelength SFPs with long wavelength SFP, the SFP batch replacement procedure is used.

Components PCB Shutdown Jumpers


PCB Shutdown Jumpers

20


Each PCB has a shutdown jumper pin block. If during a maintenance operation, power is not removed from the PCB, setting the shutdown jumper will force power off the PCB so it can be removed.

The shutdown jumper location and behavior is the same in both the Universal Storage Platform V and Universal Storage Platform VM.

Please make sure that the shutdown jumper is always available in all DKCs.

Components CE JUMPERS on CSW PCB


CE JUMPERS on CSW PCB

21


In addition to the PCB Shutdown jumper pin block, the Cache Switch has additional jumper settings. These are called the CE Mode connectors. Jumpers are set on these pins during the New Installation process. Again, they are found in the same location on the Universal Storage Platform V and Universal Storage Platform VM.

Components Other LEDs and Switches


Other LEDs and Switches

22

In addition to the status LEDs on the Operator Panel, there are status LEDs on other components throughout the storage system.

Check the Locations section of the Maintenance manual for the appropriate system to interpret the LED patterns.

During the New Installation process, the Battery toggle switches will be turned off to take all power off the storage system.

Components SVP Jumpers


SVP Jumpers

23


There are two jumper pin blocks on the SVP. In particular, jumpers are placed on these pins when the SVP is being initialized. The JP1 SVP jumper setting is used during the New Installation procedure.

The SVP jumper locations and use are the same for both the Universal Storage Platform V and Universal Storage Platform VM.

Components Other Components


Other Components

24


Other components that are critical to the operation of the storage system include the Fans, Thermostats, SSVP, PCICON.

The EPO switch is provided on both the Universal Storage Platform V and Universal Storage Platform VM. On the Universal Storage Platform V, the EPO switch is found on the upper right corner of the DKC cabinet rear cover.

Components Shared Memory PCBs and DIMMs


Shared Memory PCBs and DIMMs

25


Shared Memory DIMMS are either 512MB or 1GB. The Locations section of the Maintenance manual identifies the sequence in which the DIMMs are installed in the slots on the Shared Memory PCB.

A Universal Storage Platform VM can support a minimum of 2GB and a maximum of 16GB of Shared Memory.

Since a Universal Storage Platform V can support two Shared Memory features, a Universal Storage Platform V can support a minimum of 2GB and a maximum of 32GB of Shared Memory.

Components Cache Memory PCBs and DIMMs


Cache Memory PCBs and DIMMs

26

Cache Memory DIMMS are either 512MB or 1GB. The Locations section of the Maintenance manual specifies the sequence in which the DIMMs are installed in the slots on the Cache Memory PCB.

A Universal Storage Platform VM can support a minimum of 4GB and a maximum of 64GB of Shared Memory.

Since a Universal Storage Platform V can support up to four Cache Memory features, a Universal Storage Platform V can support a minimum of 8GB and a maximum of 256GB of Shared Memory.

Components Operator Panel and Jumpers


Operator Panel and Jumpers

27



Operator Panel:

Has the same face for both the Universal Storage Platform V (USP V) and Universal Storage Platform VM (USP VM).

Includes status LEDs and switches. Is secured to the inside of the front cover of both the USP V and USP VM. Four screws hold the Operator Panel unit to the cover.

Houses a series of jumper pin blocks. These are not visible when the Operator Panel is attached to the cover. Remove the Operator Panel unit from the cover to access the jumper locations. The jumper locations are different between the USP V and USP VM.

Make sure to refer to the Locations section of the Maintenance manual for the storage system for identification of the specific Operator Panel jumper locations.

Components Universal Storage Platform VM



28


Components Rack Overview


Rack Overview

29


A Universal Storage Platform VM can consist of one or two racks. The term “rack” is used to identify the Universal Storage Platform VM structures. The primary rack contains the DKCBOX. For the Universal Storage Platform VM, the term DKCBOX is used to identify the component where the PCB Slots are found. (The terms Front Logic Box and Rear Logic Box are used for Universal Storage Platform V).

While the Universal Storage Platform VM also has both a Cluster1 and Cluster2, they are not split front and rear. Make sure to use the Locations section of the Maintenance manual to identify which PCB slots comprise the two clusters.

Components DKCBOX


DKCBOX

30


The DKCBOX of the Universal Storage Platform VM contains the PCB slots for the Cache Memory, Cache Switch, Shared Memory, CHA and DKA PCBs.

The individual slots are the same size as in the Universal Storage Platform V. The Universal Storage Platform VM has only one layer of slots in the front of the primary rack and one layer of slots in the rear of the primary rack.

The Universal Storage Platform VM also has Cluster1 and Cluster2.

DKA PCBs are optional in a Universal Storage Platform VM. A Universal Storage Platform VM may be sold as diskless. In this case, the storage system does not need any back-end components. In the customer environment, a diskless Universal Storage Platform VM will be deployed using some of its CHA ports to connect external storage.

The data will physically be stored in the other, external storage systems. However, all the I/O will flow through the data movement components of the Universal Storage Platform VM, taking advantage of the local cache and its performance. All the software products on the Universal Storage Platform VM will be available to manage the data and storage, even though the physical storage is in other storage systems.

Components Back-end Cabling


Back-end Cabling

31


The back-end cabling includes data cable and control cables. Both these cable types connect from the DKA PCBs in the DKCBOX to the FSWs in DKU-R0. When additional DKUs exist in the storage system, the back-end data loops are extended by connecting the FSWs in DKU-R0 to the FSWs in DKU-R1.

This page shows the DKU-R0 and DKU-R1 cabling diagrams for a Universal Storage Platform VM. These are found in the Locations section of the Maintenance manual.

Cables are labeled at the factory. If you need to add a DKU at the customer site, make sure that you connect the cable end to the correct location on the FSW.

Components Back-end B4s


Back-end B4s

32


Each DKU equals one B4

Just like the Universal Storage Platform V, parity groups are built within a B4 in the Universal Storage Platform VM. Due to the different physical structure of the Universal Storage Platform VM, an HDU has 15 drives. Four HDUs comprise a B4.

A Universal Storage Platform VM can have a maximum of four B4s. The first two B4s exist in the primary rack. The third and fourth B4s are in the secondary rack.

The Universal Storage Platform VM does not use the SVR component. So, the Universal Storage Platform VM uses the LEDPNL component for the individual HDD status LEDs.

This is one component and architecture difference between the Universal Storage Platform V and Universal Storage Platform VM.

The DKUBOX describes the area of the storage system where the DKC PCB slots, power supplies, batteries, fans and SVPs are located. Universal Storage Platform VM does not use the ACBOX component.

Components Power Supply Section



33


In the Universal Storage Platform VM, the components of the Power Supply section are split between the front and rear of the rack. The Batteries are found in the front and the Power Supplies are found in the rear.

Components Component ID


Component ID

34


A Universal Storage Platform VM does not use cabinet or rack ID in the Component ID.

A fully populated Universal Storage Platform VM has four B4s. The HDU number is used in the identification of HDDs, LEDPNL, Power Supplies and FSWs in a Universal Storage Platform VM.

Components Diskless


Diskless

35


The Universal Storage Platform VM supports a diskless implementation. The components would include the DKC but would not have any DKUs. The DKCBOX will hold Cache, Cache Switches, Shared memory and CHA PCBs. As a diskless implementation has no disks, DKAs and the back-end data loops are not needed. External storage systems are connected using front-end CHA ports. The external storage is virtualized using the Universal Volume Manager.

More information about the diskless configuration of a Universal Storage Platform VM is found in the Installation section (04inst3.pdf) of the Maintenance manual.

Components Channel Adaptor (CHA) Ports – High Density


Channel Adaptor (CHA) Ports – High Density

36


1A

3A

5A

7A

1B

3B

5B

7B

In the above diagrams, Cluster1 and Cluster2 CHA Port for a Universal Storage Platform VM are shown. They show the microprocessor-to-port architecture for the high density CHA PCBs. The port identification diagrams are also shown.

Channel Host Port identification diagrams are found in the Locations section of the Maintenance manual.

CHA features are now either 16 ports or 8 ports. A CHA feature consists of two PCBs, one installed in Cluster1 and one installed in Cluster2. A 16 port CHA feature consists of two PCBs, each with eight ports. These are the high density CHA features.

In a Universal Storage Platform VM, the first set of CHA PCBs is installed in Logic Box slots 1G in Cluster1 and 2L in Cluster2.

A set of four CHA ports that share two microprocessors constitutes a CHA port block. The ports in a port block share the same letter.

Components Other Components


Other Components

37


Other components that are critical to the operation of the storage system include the Fans, Thermostats, SSVP, PCICON.

The EPO switch is provided on both the Universal Storage Platform V and Universal Storage Platform VM. On the Universal Storage Platform V, the EPO switch is found on the upper right corner of the DKC cabinet rear cover. On a Universal Storage Platform VM, the EPO switch is on the front cover of the primary rack.

Both the Universal Storage Platform V and Universal Storage Platform VM have an easy-access LAN port for the Maintenance PC.

The SVP PC is the component that supports the GUI applications so that the storage system can be monitored, administered and maintained.

Both the Universal Storage Platform V and Universal Storage Platform VM provide the option to configure a second, standby SVP known as the High Reliability Kit. When the High Reliability Kit is added to a Universal Storage Platform VM, the SBBOX must be added.

Components Part Numbers


Part Numbers

38

Use the Locations section of the Maintenance manual to translate Component IDs to Part Names. Then use the Parts section of the Maintenance manual to translate Part Names to Part Numbers.

Components Summary


Summary

39

• DKC– Logic Box or

DKCBOX– PCB– SMA– CMA– DIMM– CSW– DKA– CHA– SFP

• DKU– HDU– FSW– SVR– HDD– LEDPNL– DATA CABLE– CONTROL CABLE

• Power Supply Section– POWER CABLES– ACBOX– POWER SUPPLY– BATTERY

• Other Components– Fans– Thermostats– Operator panel– SVP– Jumpers– Toggles

• Cabinet• Rack• Hi-Star Network

You should now be able to describe each of the storage system components listed on this slide. You should be able to identify whether it is found in the Universal Storage Platform V, Universal Storage Platform VM or both. You should be able to use the Locations section of the Maintenance manual for each storage system and also locate each component in a real storage system.

You should be able to use the Parts section of the Maintenance manual to identify or confirm the correct part ordering number for replacement components.


4. User Interfaces

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Identify the three main functions of the service processor (SVP) PC– Explain why a customer would chose to install the SVP High Reliability Kit

option on either the Hitachi Universal Storage Platform™ V or Universal Storage Platform™ VM

– Identify three GUI interfaces which run on the SVP PC– Describe the differences and dependencies among the three GUIs– Describe when and who would use each of the three different GUIs– Describe the Hitachi Device Manager software application– Describe how to connect the Maintenance PC– Connect a Maintenance PC and establish connection to the SVP and the SVP

Application– Launch the Web Console Application– Launch the Storage Navigator Application

User Interfaces Service Processor PC – SVP PC


Service Processor PC – SVP PC

3

SVP Blade in a Universal Storage Platform V

USB2 Port

An SVP is a blade PC that is integrated into the architecture of the Universal Storage Platform V and Universal Storage Platform VM. The SVP PC does not have a monitor, a keyboard, a mouse, a CD drive or a floppy drive. It has one USB2 port available for the maintenance engineer. The intended use of the USB2 ports is for USB memory drives for collecting dump information and for capturing backup of the storage system’s configuration information.

Because the SVP PC does not have any human interface devices, the maintenance engineers are expected to provide their own maintenance PC. There are minimum requirements for both the SVP PC and the maintenance PC. The SVP PC is a custom component manufactured and provided by Hitachi. Information about the SVP PC part is available in the Theory section of the Maintenance manual.

User Interfaces Functions Provided by SVP PC


Functions Provided by SVP PC

4

• SVP PC is the platform that – Runs three GUI applications– Monitors and reports component

status– Collects and reports monitoring data

The SVP PC provides three main functions in support of the Universal Storage Platform V and Universal Storage Platform VM’s data storage and access functions. First function of SVP is enabling the people to ‘talk’ to the storage system. Three GUI applications that permit people to “talk to” the storage system are:

SVP Application Web Console application Storage Navigator application

The SVP PC also includes functionality for monitoring the health and performance of the storage system. If the SVP becomes unavailable, the Universal Storage Platform V and Universal Storage Platform VM will continue to process I/O. It’s just that the maintenance engineers, storage administrators and other people responsible for maintenance, administration and use of the system will not be able to view or change the system. SVP PC and its SVP application also provide the support for connecting a Universal Storage Platform V/ Universal Storage Platform VM to a customer’s SNMP environment for trapping and forwarding information about situations that may need action to be taken. So, if the SVP is rebooted or failed, the Universal Storage Platform V and Universal Storage Platform VM will continue to process I/O. Human communication with the storage system will not be possible during the time period that the SVP is unavailable. Hitachi has configured both the Universal Storage Platform V and Universal Storage Platform VM to support an optional, second SVP. This is described as the SVP High Reliability Kit.

User Interfaces GUI Comparison


GUI Comparison

5

This table compares the four main GUI applications that are used to view and manage the Universal Storage Platform V and Universal Storage Platform VM storage systems. Three of the GUI applications run on the SVP PC: The SVP Application, Web Console and Storage Navigator. The fourth GUI interface is Hitachi Device Manager software. This application is installed and runs on a Microsoft® Windows® or Sun® Solaris host other than the SVP PC. This course focuses on the SVP Application and the Web Console application as these are the two applications that are primarily used by the maintenance engineer.

Hitachi Storage Navigator program and Device Manager software are identified and discussed so that you will know about them and when it is appropriate to use them.

User Interfaces SVP Monitor


SVP Monitor

6

The second function of the SVP is to collect and report monitoring information about the Universal Storage Platform V and Universal Storage Platform VM storage system. This includes the internal log files: SIM, SSB, Power Event and others.

The SVP also collects and reports environmental conditions related to the temperature. If an environmental alarm is detected, the red alarm LED on the Operator Console will be lighted.

The SVP is the place where Hi-Track® Monitor is installed and configured for connectivity of the storage system to the remote Hi-Track Monitor’s central database and Hitachi’s support organization. Hi-Track can be configured to communicate using a dial-up phone modem connection or over an ftp connection.

On the Universal Storage Platform V and Universal Storage Platform VM, the SVP Monitor is automatically activated and runs all the time, unlike in earlier storage systems where the monitor had to be started every time to collect performance metrics. A detail dump is taken to support viewing any data on the monitor.

User Interfaces When the SVP is Unavailable


When the SVP is Unavailable

7

SVP PC

X X X

I/O continues

I/O continues

Hitachi offers SVP High Reliability through the configuration of an optional/second/standby SVP. The SVP High Reliability Kit is supported on both the Universal Storage Platform V and also on the Universal Storage Platform VM.

This is for customers who are unwilling or cannot accept the risk of being unable to view or manage the storage system in case of an SVP failure. The monitoring functions of the SVP would also be unavailable during the time that the primary SVP was down. This, perhaps, is the greater risk for a high availability and/or high performance customer environment.

If the SVP is unavailable, SIMs cannot be detected and reported. Conditions such as suspension of remote replication pairs would also go undetected in the case of the SVP not being functional.

User Interfaces Service Processor Architecture


Service Processor Architecture

8

• SVP Improvements– Special PC board -- This board is made using select parts. – Dual SVP configuration available. Failover time is shortened by hot standby

failover scheme.

Special PC boardfor industrial use

Microsoft Windows XP Professional

SVP Application

SVP

DKC internal LAN

Special LAN Port

for CE Laptop


3.5"IDEHDD

CE Laptop-Microsoft® Windows® 9x/2000 Pro./XP Pro. with Remote Desktop

For External LAN and

Hitachi Storage Command Suite

The SVP runs a Hitachi-modified version of the Windows operating system. Windows has been modified to remove some components that are not needed. One of the SVP’s main functions is to run the SVP application. Whenever the SVP PC is running, the SVP Application should also be running. The SVP Application is configured so that it cannot be closed.

An internal LAN cabling diagram for the SVP and optional SVP can be found in the Locations section of the Maintenance manual.

User Interfaces High Availability Kit


High Availability Kit

9


An SVP is a built-in custom PC that is used to provide the human interface to the storage system. In the Universal Storage Platform V and Universal Storage Platform VM, the SVP does not have a screen, keyboard, or mouse. The SVP in the Universal Storage Platform V and Universal Storage Platform VM does not have a CD ROM drive and it does not have a floppy drive. It does have one USB port that the engineer can use.

Universal Storage Platform V and Universal Storage Platform VM provide the option for a second, standby SVP. When you install the SVP High Reliability Support Kit, the basic SVP is duplicated and these two operate as the Active and Hot Standby SVPs, respectively. When a failure occurs in the basic SVP, the additional SVP quickly takes on the SVP tasks.

The Hitachi Network Storage Controller did not support a second SVP.

.

User Interfaces High Reliability Kit


High Reliability Kit

10


Primary SVP

SBBOXSecond SVP Installed here

You will need to open the back cover of the Universal Storage Platform VM to access the LAN connections for the maintenance PC.

The Network Storage Controller did not support a second SVP. The Universal Storage Platform VM does support the second SVP.

User Interfaces Connecting Maintenance PC


Connecting Maintenance PC

11


The SVP in Universal Storage Platform V has a Connector panel (SVP-CON) mounted on the rear bottom of the DKC. This Connector panel is the centralized location to connect the SVP with the following:

Customer LAN (Hitachi Storage Navigator program, Hitachi Storage Command Suite, SNMP, Graph-Track™ performance monitor feature, replaced by the Hitachi Performance Monitor feature))

Hi-Track® Monitor Phone line Connection to HUB DKC to DKC for Hi-Track Monitor (front and back DKCs) Maintenance PC The port where you have to connect your Maintenance PC (CE Laptop) is a crossed RJ45 connection, so you can use a normal straight Ethernet cable.

On the Universal Storage Platform V, there is also a LAN connection for the Maintenance PC or Console PC that is located just below the EPO switch on the back cover of the DKC cabinet. Normally, this LAN connection is covered by a small metal plate which is not shown in this picture above.

User Interfaces Maintenance PC Specifications


Maintenance PC Specifications

12

Hitachi has included minimum specifications for the Maintenance PC. This information is found in the Theory section of the Maintenance manual.

Since there is no CD drive in the SVP, the Maintenance PC must have a functioning CD drive.

Note: At the time this course was developed, Windows Vista operating system was not supported for the Maintenance PC. A Maintenance PC running Windows Vista can access the SVP using the Remote Desktop connection to the SVP’s external LAN address. A Maintenance PC running Windows Vista will not successfully connect through the direct connection to the Console PC LAN interface.

You should check the Universal Storage Platform V and Universal Storage Platform VM documentation before migrating to Maintenance PC running operating systems other than those shown above.

User Interfaces Connecting Maintenance PC


Connecting Maintenance PC

13

• Connect to Universal Storage Platform V and Universal Storage Platform VM with Remote Desktop

– If the internal IP addresses have been calculated using the serial number, the set that the Maintenance PC TCP/IP address as

• Use IP address 126._ _ _._ _ _.13, recommended • On the internal LAN, IP addresses “dot 1” through “dot 13” are not

assigned to any of the storage system’s internal microprocessors• Range 126._ _ _._ _ _.1 126._ _ _._ _ _.13 is available

– If the customer has specified the range of IP addresses on the storage system’s internal LAN, they will most probably not start with 126 and you will have to be given the first three node values

To communicate with the storage system, it is necessary to connect a keyboard, monitor and mouse, at a minimum. In most cases, a laptop will be connected using the Maintenance PC or Console PC connection. Maintenance PC and Console PC have the same meaning. As the LAN port is a cross-over port, you do not need a cross-over LAN cable. Connect the Maintenance PC LAN port to one of the Maintenance PC ports on the storage system. There is a Maintenance PC connection port on the SVP itself. On both the Universal Storage Platform V and Universal Storage Platform VM, there is also an external Maintenance PC LAN port that is likely easier to access. Universal Storage Platform V also provides a removable support platform inside the front cover. To allow the Maintenance PC to communicate with the SVP, the IP address of the Maintenance PC must be set to communicate on the storage system’s internal LAN. You will need to know the range of IP addresses on the storage system’s internal LAN. Set the IP address of the Maintenance PC to one of the unused addresses. The documentation suggests using the IP address with the lowest node value of .12 or .13. Do not use any other low end node value as these are likely assigned to other microprocessors in the storage system.

User Interfaces SVP Connect Utility


SVP Connect Utility

14

• The SVP Connect Utility, rdpexe, is found on the Documents and Tools CD of the microcode distribution kit

Hitachi now delivers the SvpConnectUtility on the microcode CD. The SvpConnectUtility will scan the LAN and will identify the IP address of any SVP and will include the IP address and serial number in the list of detected storage systems. From here, you can select and connect to the desired SVP.

You can identify the IP address of the basic SVP using the following methods: Search/browse the IP address using SvpConnectUtility - rdpexe.exe Manually calculate the IP address based on the subsystem serial number Use the offline SVP tool to read storage system configuration floppy and identify the IP address

Use the offline SVP tool with a dummy configuration and identify the IP address Keep a record of the IP addresses for the storage systems you support. You should also be able to get this information from Hi-Track if the storage system is configured to periodically report its configuration.

User Interfaces Remote Desktop Utility


Remote Desktop Utility

15

To perform any maintenance using the SVP, connect to the SVP using Remote Desktop Connection software on the Maintenance PC. This software is installed by default with Microsoft Windows XP.

To connect through a remote desktop:

Click Start -> Programs -> Accessories -> Communications -> Remote Desktop Connection.

The Remote Desktop Utility is a Microsoft program that is provided as part of the Windows operating system. You will need a Windows image on the Maintenance PC, even if the core OS is something other than Windows.

User Interfaces SVP User Registration Screen


SVP User Registration Screen

16

After entering the SVP Windows Administrator account and password, you will see the SVP User Registration screen.

Click History. Enter the appropriate information in each of the four fields, and then click Register.

User Interfaces SVP Application – Main Screen


SVP Application – Main Screen

17

After you have successfully been authenticated to the SVP, you will see the SVP application main screen.

The serial number of the storage system is displayed.

User Interfaces Web Console Application


Web Console Application

18

The Web Console application can only be accessed from the Web Console tab on the SVP application. Web Console is intended to be used by the hardware maintenance engineer in the case that she/he is called on to perform any tasks not supported by the SVP Application.

When you launch Web Console, you can see that the system invokes Web Console by using the URL 127.0.0.1 or localhost.

The other indication that this is Web Console and not Storage Navigator is that the User ID is DKCMaintenance.

Most of the management applications that are accessible from Storage Navigator are also available through Web Console. Web Console does not require any license keys although you can install license keys using Web Console.

LUN Management, VLL and LUSE are not available in Web Console.

User Interfaces Storage Navigator Application


Storage Navigator Application

19

Storage Navigator GUI provides the interface to the storage administration products. The Storage Navigator application runs on the SVP PC. Storage Navigator can be accessed over the customer’s network, using the external IP address of the SVP.

The URL for Storage Navigator is http://<ip address of the SVP>

License Keys must be installed in order to use Storage Navigator. Storage Navigator displays the User ID. In this example, the Storage Administrator account “root” is signed-on.

User Interfaces Device Manager Software


Device Manager Software

20

Device Manager software is now included in the Basic Operating System (BOS) software bundle when a customer acquires a Universal Storage Platform V and Universal Storage Platform VM enterprise storage system.

Device Manager is a software product that is installed on a separate server. It is not part of the storage system itself. Device Manager provides a human interface to one or more Hitachi storage systems of any class and type. Device Manager can be used to view and modify the configuration of modular and enterprise storage systems with connectivity across the customer’s TCP/IP LAN.

Device Manager contributes to Hitachi’s objective of Services Oriented Storage Solutions (SOSS) by enabling a single management interface for multiple Hitachi storage systems. Device Manager helps customers address cost and complexity issues by providing a common interface and set of processes for the storage administrator to manage multiple and different classes and generations of Hitachi storage systems.

This page shows an example of the Device Manager application. Device Manager executes as a thin-client, internet browser-based application on any client PC which has a supported browser and can connect to the Device Manager server on the customer’s LAN.

User Interfaces Summary


Summary

21

• The SVP PC provides three main functions– Human Interfaces– Storage system health monitoring and reporting– Performance monitor capabilities

• The SVP PC is the platform on which three of the GUI applications run• The SVP Application, Web Console and Storage Navigator applications

run on the SVP PC• If the SVP PC fails or is unavailable, the movement of I/O is not affected• Both the Universal Storage Platform V and Universal Storage Platform VM

support the High Reliability Kit second SVP• A Maintenance PC is used to connect to the SVP for storage system

management and administration• In the Universal Storage Platform V and Universal Storage Platform VM

the SVP does not include a CD ROM drive or a floppy disk drive


5. Logs and License Keys

Module Objectives

• Upon completion of this module, the learner should be able to:– Describe the different log files that are recorded by the service processor

(SVP)– Check the contents of the SVP log files– Collect the information necessary to investigate error conditions reported in

the SVP logs– Close log messages– Delete logs – Identify the purpose of Program Product License Keys– Describe the four major attributes of a Product License Key– Describe how to identify a Product License Key file– Describe the two interfaces through which license keys may be installed– Install License Keys on an enterprise storage system

This module will cover information about the various logs collected by the Hitachi Universal Storage Platform™ V or Universal Storage Platform™ VM. You will learn about ten different logs, how to view them, how to complete open messages so that the status LEDs turn off, and how to clean up the logs. The second part of this module will present the information on how to enable the microcode Program Products by installing Product License Keys provided by Hitachi.

Logs and License Keys Modify Mode and Information Log Files


Modify Mode and Information Log Files

3

In the SVP application, let us look at the available system logs that can be viewed and managed through the Information tab.

The Information tab is active for any operation mode of the SVP application.

You will only be able to complete or delete the logs if the SVP application is in Modify Mode.

Select the Information tab or use the Information option in the drop down menu to access the various logs that are recorded by the SVP.

Logs and License Keys Using and Managing the SVP Logs


Using and Managing the SVP Logs

4

1

2

3

4

The SVP collects error and event information in a number of different logs. Select the Log… tab to display the logs. The available logs are SIM, SSB, Reset, Power Event, Detail, Incident, LCP/HTP, Diagnosis and Copy History.

If the log is empty, it will be grayed-out and you will not be able to select its radio button. If there are log entries in a log, select the radio button and then select the List… tab. This will display a list of the log entry summary header data.

Highlight the log entry for which you want to see the detailed information, then click the Content… tab. This is the lowest level of detail you can view through the SVP.

From this display, you can make notes about the Action Code(s) and Reference Code reported by the event. You need the Action Code (ACC) and Reference Codes to find the correct instructions in the MDL.

SSB codes can be found in the SSB section (18ssb.pdf) of the Maintenance manual in the MDL library. SIM Return Codes can be found in the SIM section (15simrc.pdf) of the Maintenance manual.

The next page shows the relationship between System Sense Bytes and SIM messages.

Logs and License Keys Levels of Error Detection and Logging


Levels of Error Detection and Logging

5

• Overview– Microprocessor(s) send error data to SSVP– SSVP forwards SSB to SVP– SVP converts SSB into one

or more SIMs– Messages are categorized in SIM log

• Service• Moderate• Serious• Acute

– Hi-Track® monitor notifies support center– SNMP can forward SIMs to host– Engineer takes action based

on the Action Code(s)

SSB SIM

SSB log SIM log

ACC

HOST

SSBSection

SIM RCSection

ACCSection

Technical supportCenter *

Diagnostics

Failure

This diagram is taken from the Troubleshooting section (06trbl.pdf) of the Maintenance manual.

The lowest level of log information is presented in the System Sense Byte (SSB) log. The diagram and description show how the SVP translates SSB codes into higher level System Information Message (SIM) code(s).

The SSB Log section of the Maintenance manual describes the different kinds of SSBs and their structure. The SSB section of the Maintenance manual contains the SSB codes.

Understanding the SSB codes, SIM codes, ACC codes and Work ID codes is important for determining how to resolve storage system errors.

Often, the SVP Maintenance interface will identify and guide you to the failed component. If a problem situation is not straightforward, you may need to investigate the system’s condition by looking up information in the Maintenance manual using any available SSB or SIM codes.

Note: The Technical Support Center or Technical Resource Center is now known as Global Support Center, GSC.

Logs and License Keys The Maintenance Manual and its Sections


The Maintenance Manual and its Sections

6

• From the ECN

This is a reminder that the Maintenance Manual for each system, the Universal Storage Platform V and the Universal Storage Platform VM, is delivered on the Documentation CD of each microcode release. Later, we will look at some of these documents and its sections in more detail as they relate to investigating incidents or conditions reported in the various SVP logs.

As with the Hitachi Universal Storage Platform™ and Hitachi Network Storage Controller, the exact same microcode distribution media is used to build Universal Storage Platform V or VM. The Maintenance manuals for both the Universal Storage Platform V and VM are delivered in the Manuals folder on the microcode CD labeled “Documents and Programs associated with microcode 06-nn-nn-nn/00.”

Make sure that you set up a process that lets you keep and manage multiple copies of the Maintenance manual for the different microcode levels of the systems you are supporting. The files do not identify the version of microcode to which they apply. The ECN for the microcode version identifies the correct revision of the Maintenance manual.

Logs and License Keys Using the System Sense Bytes Manual Section


Using the System Sense Bytes Manual Section

7

As System Sense Bytes (SSB) are the lowest level of error and diagnostic data collected and reported by the storage system. The SSB section (18ssb.pdf) of the Maintenance manual provides information for how to research SSB codes if necessary. The process distinguishes between hardware related errors and non-hardware related errors and also distinguishes between errors related to the DKC or DKU.

If you are debugging storage system errors at the SSB level, you may be working with Hitachi Data Systems advanced technical support from one of the TRC locations.

Logs and License Keys SIM RC Reference Codes


SIM RC Reference Codes

8

SIM RC codes are identified in the SIMRC section (15simrc.pdf) of the Maintenance manual. You will find the simrc code in the SIM log record. You can search this simrc code in the manual which will contain more information and/or Adobe document links to other sections manuals in the Maintenance manual.

Logs and License Keys Action Codes and Replacement Procedures


Action Codes and Replacement Procedures

9

The Action Code (ACC code) reported in the SIM message can be looked up in the ACC section (14acc.pdf) of the Maintenance manual. The ACC code will include an Adobe document link to the Work ID in the 07rep.pdf Replacement Procedures section. The Work ID table will have Adobe document links to Pre-procedure, Hardware procedure and Post-procedure codes. Following these Adobe document links will take you to the instructions for capturing dump data, the actual physical component replacement and the updating of the configuration data.

Logs and License Keys SIM-> Content-> Refer to View the SSB


SIM-> Content-> Refer to View the SSB

10

Logging in the SVP connects the entries of the SIM log and the SSB log. You can select the SIM message, display the content and then click Refer. This will display a list of logs that may contain related entries. Select the radio button next to the log whose related entry you want to see, and then click OK. In the above example, the SSB log entry that corresponds to the selected SIM is displayed.

Locate these messages in the SIM, SSB and ACC manual sections.

Logs and License Keys Completing Log Entries


Completing Log Entries

11

When a SIM or log entry is first detected, it is recorded to the appropriate log with status as ‘Initial”.

When the SIM log contains one or more messages in “Initial’ status, the amber SIM LED will be on.

In order to turn off the amber SIM LED, all log messages must be closed or completed. In order to complete and delete log messages, the SVP must be in Modify mode. With the SVP in Modify mode, highlight the log message(s) that you want to complete, and then select the Complete… tab. You will get a confirmation prompt to verify that you want to take this action.

The status of the log entry is changed from Initial to Completed.

When all log entries are completed, the log can be deleted. Select the radio button for the log to be deleted, and then select Delete tab. Confirmation prompts will be displayed.

Logs and License Keys Deleting the Logs


Deleting the Logs

12

There are times when it is helpful to delete the log entries to put the logs in a clean and empty status. You will be instructed to delete all the log records at several points during the New Installation procedure which will be covered later in this course.

In order to delete all the messages from one of the logs, select the radio button for that log, then select the Delete… tab. You will get a confirmation prompt to verify that you want to delete all the messages from the log. Once you delete a log, the deleted messages are not recoverable through the SVP.

Logs and License Keys Audit Log


Audit Log

13

There is one additional log, the Audit Log, is managed through the Storage Navigator interface.

The Audit Log is saved to the hard drive on the SVP. It is written to the SVP drive in .tgz compressed format. In certain troubleshooting cases, the Hitachi Data Systems TRC may request that the audit log file be submitted as part of the investigation.

As the Audit Log is stored in compressed format, in order to read and analyze the Audit Log, it must be transferred to a server that supports a file compress/uncompress utility. Do not install any software on the SVP unless directed to do so by Hitachi.

From time to time, the Audit Log will fill and Storage Navigator will indicate a warning. By simply selecting the Audit Log tab, the audit log will be written to the hard drive of the SVP and the warning message will no longer appear.

Logs and License Keys Downloading the SYSLOG


Downloading the SYSLOG

14

You access the interface to download the Audit Log or Syslog by using the Go-> Security menu path.

If directed by Hitachi, you may need to download the syslog and/or audit log to submit to Hitachi for issue resolution purposes. On the SVP screen, as shown above, you can configure information about the server(s) to which you want the downloaded Syslog file to be written.

This concludes the identification and discussion of the different log files written by a Universal Storage Platform V and Universal Storage Platform VM.

Logs and License Keys License Keys Enable the Software Products


License Keys Enable the Software Products

15

• Managing customer software access and storage

capacity management using a license key approach

– Protects Hitachi Ltd.

– Ensures customers use supported configurations

• License keys become a valuable resource that must

be protected and managed by the customer

A storage system can be fully installed and configured using only the features that are available through the SVP.

Product License Keys must be installed to enable the functionality of the microcode enabled Program Products. This will then allow the customer staff to take over management and use of the storage system.

License keys protect Hitachi. Requiring license keys to be installed at the customer site ensures legal use of products and functionality licensed and paid for by the customer. Hitachi offers flexibility for emergency situations and to enable product trials or evaluations.

With the Universal Storage Platform V and Universal Storage Platform VM, the bundling of Program Products has been simplified.

Logs and License Keys License Management Policy Change


License Management Policy Change

16

• Objective– Meet and challenge our competitors pricing strategies– Improve back-end operation (Portability and others)

• Pricing Strategy is: – Simple to price– Simple to understand– Simplify the back-end processes (Portability and others)

• Benefits– Reduce complexity of the back-end operation and processes– Increase customer satisfaction

Hitachi has revised implemented product bundling and license management policies effective with Universal Storage Platform V and Universal Storage Platform VM.

The objective is to simplify the licensing process and to eliminate licensing issues from the customer’s perspective.

Logs and License Keys New Licensing Bundles - BOS


New Licensing Bundles - BOS

17

• Basic Operating System (BOS)– Hitachi Resource Manager™

Utility package• Virtual LVI/LUN software• LUN Manager• Logical Unit Size Expansion• Cache Residency Manager

feature• Performance Monitor feature• Storage Navigator program• Configuration File Loader • SNMP Agent • Java API• Data Retention utility • Hitachi Volume Retention Utility

for IBM® z/OS®

• Volume Shredder software

• Basic Operating System (BOS)Resource Manager utility (contd.)

• Database Validator software• Volume Security feature for

IBM® S/390®

• Hitachi Volume Security Port Option

• Cache Partition Manager feature– Hitachi Server Priority Manager

software– Hitachi Virtual Partition Manager

software• With support for up to four

partitions– Hitachi Storage Command Suite

Device Manager software

Notes:

The Base Operating System (BOS) bundle includes all the products that constitute Resource Manager as well as Server Priority Manager, Virtual Partition Manager for up to four partitions.

Device Manager software is included in the BOS bundle.

SAN Security software [includes software formally known as Hitachi SANtinel port security software (for open systems) or Hitachi Volume Security Port Option (for mainframe)]

Use these web links to remain updated on the status and contents of the BOS and BOS V:

http://www.hds.com/products/storage-software/basic-operating-system-software.html

http://www.hds.com/products/storage-software/basic-operating-system-v-software.html

Logs and License Keys Licensing Bundle – BOS V


Licensing Bundle – BOS V

18

• Basic Operating System V (BOS V)– Includes Virtual Partition Manager software for more than four partitions– Includes Universal Volume Manager software

The BOS V bundle adds the functionality of virtualized external storage through the Universal Volume Manager software and also extends partition support for more than four partitions.

Logs and License Keys Additional Software Bundles


Additional Software Bundles

19

• Disaster Recovery– Hitachi TrueCopy® software products– Hitachi TrueCopy software for IBM® z/OS®

– Hitachi Universal Replicator software– Hitachi Universal Replicator software for IBM® z/OS®

• Disaster Recovery Extended– TrueCopy Synchronous software and full function Universal Replicator software with 3DC and 4x4

• Hitachi ShadowImage® Heterogeneous In-System Replication software– ShadowImage software – Hitachi ShadowImage software for IBM® z/OS®

– Hitachi Copy-on-Write Snapshot software for Open only• Business Continuity Manager with Extended CTG

– Hitachi Business Continuity Manager software– Hitachi Business Continuity Manager Extended CT Group software

• Business Continuity Manager HUR 4x4 Extended CTG– Hitachi Business Continuity Manager Universal Replicator 4x4 Extended CTG

• Compatible Function for Mainframe– Compatible Mirroring for IBM FlashCopy Version 2– Hitachi Compatible PAV software for IBM® z/OS®

– Hitachi Compatible Replication software for IBM® z/OS®

TrueCopy Asynchronous is not included in the list of licensed products. Hitachi is retiring TrueCopy Asynchronous remote replication. Universal Replicator software is now the defacto asynchronous remote replication solution.

Hitachi is also retiring Cross System Copy and Auto Plan Volume Migrator.

Cross System Copy had been bundled with Universal volume Manager but had the disadvantage of requiring that both the source and target volume be offline during the copy process. Cross System Copy was intended to be an offline migration tool. However, consultants and customers learned that a data migration could be accomplished with the production data still online. There was little use or interest in a disruptive data migration tool.

Automated data migration functionality has been integrated into the Hitachi Storage Command Suite Tiered Storage Manager software.

Logs and License Keys Attributes of License Keys


Attributes of License Keys

20

• License Keys are delivered in text format in a file with the .plk extension• License keys have four dimensions

– Program Product (PP)– Serial Number of the storage system– Time duration– Storage capacity permitted to be managed in GB or TB

Storage Navigator must be license key enabled. When the customer or engineer accesses Storage Navigator with no license keys installed, Storage Navigator will open the License Key interface by default. No other Storage Navigator functions will be possible until the license keys have been installed.

Logs and License Keys License Keys Delivered in Text File


License Keys Delivered in Text File

21

• Overview– Check subsystem capacity– Locate ASCII *.PLK file– Copy *.PLK to DKC200\home\java– Select products to license– WebConsole requires “Webconsole, SNMP and RMI”

The customer’s product license keys should be delivered in a *.plk file on a CD. If not, the customer’s Hitachi Data Systems’ representative can request license keys through email.

The customer’s initial set of license keys should be part of the information included with the delivery of the new storage system.

It is important to protect the license keys for the customer. Even the initial license keys may be needed in the future.

Logs and License Keys License Keys on the SVP


License Keys on the SVP

22

On the SVP PC, look for a copy of the basic *.plk file in the C:\DKC200\home\java directory.

License keys are clear text. There is an intelligence built into the keys but they are tied to the serial number of the storage system for which they were generated.

Logs and License Keys Storage Navigator- When Keys not yet Installed


Storage Navigator- When Keys not yet Installed

23

Before product license keys are installed, none of the products are available through Storage Navigator. You can still start a Storage Navigator session but the system knows that the keys have not yet been installed. Storage Navigator will automatically open to the License Keys interface so that you can proceed with the installation of the keys.

Storage Navigator must be in Modify mode in order to be able to install the keys.

Logs and License Keys Using Web Console/Storage Navigator for Keys


Using Web Console/Storage Navigator for Keys

24

License keys can be installed either through the Web Console interface or through the Storage Navigator. You can identify a Web Console session by the User “DKCMaintenance”. Otherwise, Web Console and Storage Navigator look the same. Key Type and Status columns display Not Installed for products which have not yet been enable by the installation of a license key. You can install individual KeyCodes or groups of license keys that have been consolidated in a Product License Key *.plk file. Select the correct radio button option depending on whether you will install individual keys or .plk files. The radio button selection makes the corresponding data entry window active. If you have selected the File radio button, the Browse tab will also be activated and you can browse the available data locations for the *.plk file. When you have navigated to the file, highlight it and click Open. This will populate the file name in the Filename field. The next step is to install the key(s). Select Install tab and wait. The keys get verified against the system serial number and other attributes during this time. When the keys have been verified, the key data will be updated and displayed in blue italics font. Click Apply to complete the installation of the License Keys. All product functionality is active by default through the Web Console interface.

Logs and License Keys License Keys Status after Install and Apply


License Keys Status after Install and Apply

25

When the license keys have been successfully installed, the Key Type will display the key duration or time attribute.

The Permitted Volumes show how much storage capacity the customer is permitted to access and manage with the product. And the Status shows whether the key is installed and possibly disabled.

Key Type describes the time duration of the installed key:

Permanent keys with a capacity limit are normal. Permanent keys will install right over temporary keys

Temporary keys with a life of 120 days are used for transient licensing, both internally at Hitachi Data Systems and with customers

Emergency keys are typically seven days, and are used to solve a licensing problem, or as a very short-term key

You cannot install a temporary key over an existing temporary key

Logs and License Keys Entering Individual Key Codes


Entering Individual Key Codes

26

If necessary, you can enter key strings manually instead of a .plk file, such as when getting an email. Keys are tied to subsystem serial number so they are unique to a specific subsystem. Select the program product to install from the Product Name column. Select the KeyCode radio button and type or cut and paste the 48 character code in the space provided.

Logs and License Keys Accessing License Key Management


Accessing License Key Management

27

After the initial installation of license keys, if you need to access the License Key interface later, use the Go-> Environmental Settings-> License Key menu path of Storage Navigator.

Logs and License Keys Summary


Summary

28

• There are a number of different types of log files that are managed on the SVP PC

• Use the SVP Application Information tab to access the logs, complete open log messages and delete or clean out the log files when needed

• Understand the relationship between System Sense Byte (SSB) codes, System Information Message (SIM) codes and Action Codes (ACC) codes and how to research them in the Maintenance manual

• Understand the purpose of Product License Keys• Know the four main attributes of a Product License Key• Be able to install license keys on a customer storage system

Logs and License Keys Review Questions


Review Questions

30

1. List the ten types of logs that are recorded by a Universal Storage Platform V and VM.

2. What management tasks are available for the log files?

3. What are the four attributes of product license keys?

4. What are the ways to apply license keys?


6. Power Supply Architecture

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Identify the components of the Power Supply section in a Hitachi Universal

Storage Platform™ V (USP V) or a Universal Storage Platform™ VM (USP VM)– Describe the only AC power configuration option for a Universal Storage

Platform VM– List the different AC power configuration options for a Universal Storage

Platform V – Locate the correct configuration for the AC power jumper on a Universal

Storage Platform V– Recognize the correct configuration for the AC power jumper on a Universal

Storage Platform V– Discuss the requirement to check the power configuration and system options

setting for the AC power before connecting a storage system at the customer site

Power Supply Architecture Universal Storage Platform V



3

Power Supply Section for


Power Supply Architecture Power Supply Section



4

Operator Panel

The Power Supply section of a Universal Storage Platform V is made up of the AC Boxes, the Power Supplies and the Batteries. The design of the Power Supply section of the system establishes two separate electrical power delivery zones, setting the power boundary between Cluster 1 and Cluster 2.

Disk controller (DKC) and disk adaptor (DKU) cabinets have Power Supply sections.

Notice that the Power Supply section components themselves are not divided between the front and the rear of the frame. This is true for both the DKC frame and the DKU frames.

The diagrams on this page are found in the Locations section of the Maintenance manual. Use the Locations section of the Maintenance manual to identify the correct component when necessary for maintenance or capacity increases at the customer site.

Power Supply Architecture DKC Power Supplies and Batteries


DKC Power Supplies and Batteries

5

These diagrams of the Universal Storage Platform V DKC cabinet show, in particular, the AC Boxes, the Power Supplies and the Batteries. These components are found under the Cluster1 and Cluster2 Logic Boxes in the front and rear of the DKC cabinet.

These diagrams are found in the Locations section of the Maintenance manual. You can also refer to the Locations section of the Maintenance manual for the component location diagrams for the Universal Storage Platform V DKU cabinets.

Power Supply Architecture Power Supply Section



6

Source: 03loc.pdf

Here is the lower rear of a Universal Storage Platform V DKC cabinet. You can see the AC power cables coming into the cabinet from the floor. You can see the two AC Boxes and the Power Supplies.

Power Supply Architecture Power Cabling and Boundaries


Power Cabling and Boundaries

7

Source: 03loc.pdf

This diagram of the Universal Storage Platform V power cabling is taken from the Locations section of the Maintenance manual. It shows the CL1 CL2 cluster boundaries and also the two, separate AC power supplies and how they deliver power to the system.

Power Supply Architecture SVR DC/DC PCBs


SVR DC/DC PCBs

8

• Nine SVR PCBs are installed per HDU box• One SVR PCB is spare• SVR PCB also include HDD status led’s

SVR(Spare)

Failure

SVR (Spare) can give power to 8HDDs.

FSWR00-UFSWR00-L

SVRR04-L HD

DR

04-0CH

DD

R04-0A

HD

DR

04-08H

DD

R04-06

HD

DR

04-04H

DD

R04-02

HD

DR

04-00H

DD

R00-0E

HD

DR

00-0CH

DD

R00-0A

HD

DR

00-08H

DD

R00-06

HD

DR

00-04H

DD

R00-02

HD

DR

00-00

HD

DR

04-0E

SVRR00-L

SVRR04-U SVRR00-U

FSWR01-UFSWR01-L

SVRR05-L SVRR01-L

SVRR05-U SVRR01-U

HD

DR

04-0DH

DD

R04-0B

HD

DR

04-09H

DD

R04-07

HD

DR

04-05H

DD

R04-03

HD

DR

04-01H

DD

R00-0F

HD

DR

00-0DH

DD

R00-0B

HD

DR

00-09H

DD

R00-07

HD

DR

00-05H

DD

R00-03

HD

DR

00-01

HD

DR

04-0FH

DD

R05-0C

HD

DR

05-0AH

DD

R05-08

HD

DR

05-06H

DD

R05-04

HD

DR

05-02H

DD

R05-00

HD

DR

01-0EH

DD

R01-0C

HD

DR

01-0AH

DD

R01-08

HD

DR

01-06H

DD

R01-04

HD

DR

01-02H

DD

R01-00

HD

DR

05-0EH

DD

R05-0D

H

DD

R05-0B

H

DD

R05-09

HD

DR

05-07 H

DD

R05-05

HD

DR

05-03 H

DD

R05-01

HD

DR

01-0F H

DD

R01-0D

H

DD

R01-0B

H

DD

R01-09

HD

DR

01-07 H

DD

R01-05

HD

DR

01-03 H

DD

R01-01

HD

DR

05-0F

SVRR05-EX

Source: 03loc.pdf

SVR (spare) is always on. SVR (spare) can give power to eight (8) HDDs when another power unit fails. SVR (spare) is always checked whether it has errors or a failure.

Power Supply Architecture SVR Backup


SVR Backup

9

• What Happens if Two SVR PCBs Fail?

SVR(Spare)

Failure

SVR (Spare) can give power to more than ７HDDs.

Failure

7HDDs(less than 8 HDDs) are OK.

SVR(Spare)

Failure

SVR (Spare) can not give power to more than 8HDDs.

Failure

16HDDs(more than 8 HDDs) are not OK.

SVR can give power up to eight HDDs.

If more than two SVRs fail, the remaining SVRs cannot give power to more than eight HDDs.

If two failed SVR cover more than eight HDDs, all HDDs are stopped. For example, if two failed SVRs cover 16 HDDs, all 16 HDDs are stopped.

If two-failed SVR cover seven HDDs, SVR (spare) can give power to all seven HDDs.

Power Supply Architecture Additional Power Supply Options


Additional Power Supply Options

10

• Cluster Additional Power Supplies for Universal Storage Platform V– Addition of the First Set

• When the total of the disk adaptor (DKA) and Channel Adaptors (CHA) options is five sets or more

• When two sets or more of DKC-F610I-CX are installed• When two sets or more of DKC-F610I-SX are installed

– Addition of the Second Set• When the total of the DKA and CHA options is 11 sets or more• When three sets or more of DKC-F610I-CX are installed

Front View of DKC BATTER

Y11

BATTER

Y-UR

00

BATTERY12

BATTERY13

BATTERY14

BATTERY15

BATTERY21

BATTERY22

BATTERY23

BATTERY24

BATTERY25

BATTER

Y-UR

01

BATTER

Y-UR

02

BATTER

Y-UR

03

DKUPS -R01

DKUPS -R00

PS2 5

P S 2 3

P S 2 1

P S 1 5

P S 1 3

P S 1 1

Rear View of DKC

AC BOX-2

S S V P/ M N

P S 1 2

P S 1 4

P S 1 6

P S 2 2

P S 2 4

PS2 6

AC BOX-1

PCI-CON

FUSE- 02

FUSE- 01

B A T - R E G 2

B A T - R E G 1

Shown here is the configuration of the DKC Logic Box and the amount of Power Supplies needed in the system.

As a customer grows the Universal Storage Platform V by adding PCBs in the DKC, the system will need additional power supplies. The configuration engineer must be aware as to when the customer configuration also needs additional batteries. As a maintenance engineer, you may need to install additional batteries as part of a Change Configuration procedure to add the additional PCBs.

Power Supply Architecture Optional Power Supplies


Optional Power Supplies

11

• Up to two additional CL Additional Power Supply options• Two Different type of 3-phase AC-Boxes and three for 1-phase

When setting the configuration for a Universal Storage Platform V DKC or DKU frame, any additional Power Supplies must be specified along with the correct AC-Box Type.

Power Supply Architecture Destage Mode and Optional Batteries


Destage Mode and Optional Batteries

12

If a customer wants to configure the Universal Storage Platform V for Destage Mode in case of the loss of the main AC power, optional batteries will be required.

The Power Supply architecture has been changed to make several batteries optional.

Conditions that cause additional batteries to be needed are: Larger amounts of cache memory Larger amounts of shared memory More PCBs in the Logic Box The setting of Destage Mode

Refer to the Theory section of the Maintenance manual for the conditions under which additional Battery options must be added.

Power Supply Architecture Additional Battery Options


Additional Battery Options

13

2set-・Destage is selected.・When DKC-F610I-AKT is installed.

1set-・Destage is selected.・When DKC-F610I-AKT is not installed.

DKC-F605I1set-・Destage is selected.

-3set・CM Capacity is 104GB or more.

-2set・CM Capacity is 72GB or more.・When the 2nd set of the DKC-F610I-APC is installed

-1set・Cache Memory (CM) Capacity is 56GB or more.・Shared Memory Capacity is 14GB or more.・When the 1st set of DKC-F610I-APC is installed.

DKC610IDKC-F610I-ABXDKC-F610I-AB

Required OptionAdditional conditionsModel

F ro n t V ie w o f D K C

BATTE

RY

11

BATTE

RY

-UR

00

BATTE

RY

12

BATTE

RY

13

BATTE

RY

14

BATTE

RY

15

BATTE

RY

21

BATTE

RY

22

BATTE

RY

23

BATTE

RY

24

BATTE

RY

25

BATTE

RY

-UR

01

BATTE

RY

-UR

02

BATTE

RY

-UR

03

D K U P S -R 0 1

D K U P S -R 0 0

P S 2 5

P S 2 3

P S 2 1

P S 1 5

P S 1 3

P S 1 1

Front View of DKU

DKUPS

-xx3

DKUPS

-xx2

DKUPS

-xx1

DKUPS

-xx0

BATTE

RY

-Uxx0

BATTE

RY

-Uxx1

BATTE

RY

-Uxx2

BATTE

RY

-Uxx3

BATTE

RY

-Uxx4

BATTE

RY

-Uxx5

BATTE

RY

-Uxx6

BATTE

RY

-Uxx7

The new features of the Universal Storage Platform V have enabled different system configuration allowing the customers to choose how the system would behave if the main electrical power is lost. This is the Power Lost setting within the System Options in the configuration.

The default behavior is now Backup mode, only. If a customer wants to configure a system to behave in Destage mode in the case of the loss of main electrical power, then additional batteries will be required for the system.

Power Supply Architecture AC Power Configuration Options


AC Power Configuration Options

14

The Universal Storage Platform V has AC power options that are not available on the Universal Storage Platform VM. In Universal Storage Platform V, the DKC and the DKUs have the option of being connected to either 1Phase or 3Phase AC power. 1Phase and 3Phase power connections can be mixed within a single Universal Storage Platform V system.

Even if all the cabinets of a Universal Storage Platform V are connected to the same input power phase, different breaker ratings may be used on separate cabinets.

It is critical for a Universal Storage Platform V that the AC Power Jumpers be set correctly for each cabinet depending on the type of AC Power connections configured for that cabinet.

Power Supply Architecture AC Power Jumper


AC Power Jumper

15

• Universal Storage Platform V Only

3Phase1Phase

The diagrams are taken from the Universal Storage Platform V Locations section of the Maintenance manual. You must verify the AC power configuration of a new Universal Storage Platform V storage system before connecting it to the power at the customer site. Use the Locations section of the Maintenance manual as your reference.

Note: Only the USP V has the AC Power Jumper.

Power Supply Architecture Power on Sequence


Power on Sequence

16

1

2

3

Turn on breakers

Turn on batteries

When performing power-on procedure for a storage system that has been entirely powered down, follow this sequence:

1. Turn on the breaker switches for the DKC and DKU cabinets.

2. Turn on all the batteries.

3. Power on the DKC.

When the breakers are turned on, the SVP should start and boot up.

The system will operate with the batteries turned off. The purpose of the batteries is to provide power to maintain the cache and shared memory in case of main power loss. Turn on the batteries before powering on the DKC.

Powering on the DKC from the Operator Panel will start the power-up of the entire storage system.

Wait for the Ready LED to light.

Power Supply Architecture Universal Storage Platform VM



17

Power Supply Section for


Power Supply Architecture Power Supplies and Batteries


Power Supplies and Batteries

18

These diagrams for the Universal Storage Platform VM showing the Power Supplies and batteries located in the DKCBox are taken from the Locations section of the Maintenance manual.

The SBBOX is an optional component that is needed only in the cases where the Universal Storage Platform VM is configured with the optional, second SVP and/or the system is configured with 80GB or more cache memory. If the Universal Storage Platform VM is configured with 80GB or more of cache, then additional batteries are needed in case of all the AC power being lost.

You should refer to the Locations section of the Maintenance manual for supporting information that 2U just above the DKCBox in the primary rack must be left open in case the SBBOX needs to be added later.

Power Supply Architecture Power Cabling and Boundaries


Power Cabling and Boundaries

19

This diagram is taken from the Theory section of the Maintenance manual showing the AC power cabling of a Universal Storage Platform VM and also shows the Cluster power boundaries. It shows how redundant electrical power is delivered to both Clusters and also to each HDU.

A Cluster is a set of Logic Box components fed by one of the two separate power supplies. The Universal Storage Platform VM has two Clusters, just like the Universal Storage Platform V.

Every power supply is field replaceable.

Remember, the Universal Storage Platform VM does not use the SVR component found in the Universal Storage Platform V. The HDD status LEDs are located on the LEDPNL component in the Universal Storage Platform VM.

Power Supply Architecture Single Phase AC Power Only


Single Phase AC Power Only

20

The information on this page is taken from the Theory section of the Maintenance manual. It shows that only 1 Phase AC power input is supported for the Universal Storage Platform VM.

Because only single phase AC power is supported for the Universal Storage Platform VM, there is no need for the AC power configuration jumper.

Power Supply Architecture Backup Mode Only and Additional Batteries


Backup Mode Only and Additional Batteries

21

Source: 12theory.pdf

The Universal Storage Platform VM is only configurable for Backup Mode in the case the main power is lost. Destage Mode is not supported for the Universal Storage Platform VM.

Hitachi has modified the architecture of this smaller storage system to make some of the batteries optional. The optional batteries are required when the Cache Memory and/or Shared Memory capacities reach certain limits.

The information on this page is taken from the Universal Storage Platform VM Theory section of the Maintenance manual. This should be a reminder for you to verify battery configurations in the version of the Maintenance manual that is appropriate for the system and level of microcode. Always check the manual.

Power Supply Architecture Summary


Summary

22

• The Universal Storage Platform V has electrical power supply configuration options

• Hitachi, the customer and the staff performing the site installation must carefully review the Universal Storage Platform V power configuration and the power supply at the site

• The Universal Storage Platform VM has only one electrical power configuration

• The Universal Storage Platform V and Universal Storage Platform VM have different behavior when the main power is lost

• On a Universal Storage Platform V, additional batteries are required when the customer wants the storage system configured in Destage mode

• There is a specific sequence for power on and power off

Power Supply Architecture Summary



7. Configuration and Offline SVP

Module Objectives

• Upon completion of this module, the learner should be able to:– Describe the role and importance of storage system configuration data– Identify three different ways to view configuration data for a storage system– Install the Offline SVP program– Use the Offline SVP program– Describe when it is useful to use the Offline SVP to view, change or create

configuration data– Perform the tasks necessary to create configuration data backup using the

SVP Application

Refer Configuration versus Change Configuration

This module shows the configuration screens for both the Hitachi Universal Storage Platform™ V (USP V) and Universal Storage Platform™ VM (USP VM).

A series of configuration screens for a USP VM are shown. These were captured from the SVP Application Refer Configuration dialog.

Where it is informative to also show USP V configuration, the comparative image is shown. This is sometimes on the same slide and sometimes on a separate slide. The USP V configuration images were captured from the Offline SVP application.

As you become familiar with the configuration information you will also learn the differences between the USP V and USP VM. You will also learn to recognize the differences between a Refer Configuration, a Change Configuration and the Offline SVP.

Configuration and Offline SVP Viewing the Configuration


Viewing the Configuration

3

SVP

CHPsDKPs

Refer Configuration

Change Configuration

Offline SVP

There are several different ways to view a storage system’s configuration.

The Refer Configuration dialog is accessed through the SVP Application. This series of information displays allows you to look at the configuration. No changes are permitted in the Refer Configuration interface. “Refer” means browse.

When performing a Change Configuration with the SVP Application in Modify Mode, the dialog still displays all the screens of the configuration options. When you have initiated a Change Configuration procedure, you will only be allowed to change the component or type of component that was selected when the Change Configuration was started.

The Offline SVP utility can be used to view the configuration of a storage system using a Backup Configuration file. The Configuration Backup file can be accessed from any type of storage media. The Offline SVP must be installed on the Maintenance PC or other host or server separate from the SVP.

Another option for seeing a storage system’s configuration would be to look at the configuration data stored in Hi-Track™ Monitor.

Configuration and Offline SVP Configuration Data


Configuration Data

4

• Configuration data is what determines how the microcode will recognize and drive the physical hardware components of a Hitachi Universal Storage Platform™ V/VM storage system.

• Configuration data must accurately describe the exact physical components that are installed.

• Configuration data describes the logical device (LDEV) structures, location and mappings.

– The Configuration definition of the DKC must exactly match the installed components– A range of configurations can be “valid” for any given storage system

• LUN Mapping, LUSE, VLL, Virtual Partitions choices are customer-dependent– There is no single correct set of configuration for LDEVs and mappings. At this level,

the configuration data must be valid.• The initial configuration is installed in the storage system during the New

Installation process.• Once a Universal Storage Platform V/VM is put into production, the configuration

data must be periodically backed-up.

Configuration data describes the physical components that are installed in the Universal Storage Platform V/VM storage system. In order to function as a storage system, a valid configuration is required. The initial configuration is done during the New Installation process.

The configuration defines what physical components are installed in the cabinets: how many and what kinds of PCBs are installed in the Logic Box, how many and what size and rotation speed HDDs are installed in the HDUs, the RAID group and emulation configurations, the LDEV structure. Once the storage system is put into production, LUN Mapping, replication pairs, external storage, connected network attached storage (NAS) all become part of the configuration.

In the configuration, the specification for the type and number of physical components must exactly match the installed components.

There are many possible LDEV definitions that would be valid. The configuration must match the customer’s specification.

Once the storage system has gone into production, it is important to protect the configuration data by taking periodic backups.

Configuration and Offline SVP Configuration Data


When a configuration change is made through the SVP Application, the last phase of the process will prompt you to create an updated backup of the configuration data.

A configuration backup can be created at any time by using the Create Config Backup option from the SVP Application.

If the storage system is configured to do so using HiTrack® Monitor, the system will upload its configuration to the HiTrack database once per week.

Configuration and Offline SVP Refer Configuration


Refer Configuration

5

• Refer Configuration for a Universal Storage Platform VM

The system’s configuration can be viewed through the SVP Application. With the SVP Application in Modify Mode, select the Install option and then select the Refer Configuration tab.

Notice that even though the SVP Application is in Modify Mode, the Refer Configuration dialog operates in view mode, only. The configuration data specific to the system will be shown in grayed out font, only. This indicates that the data can be viewed but not changed.

The first screen in Refer Configuration shows the Serial Number, the number of Control Unit tables that are usable, the internal IP address and subnet mask of the SVP and the summary of the Cache configuration. There is also the access button for the System Option settings.

On this view of the configuration data, you can determine whether the system is a Universal Storage Platform V or Universal Storage Platform VM. A Universal Storage Platform VM has only the Basic Cache option. This configuration data shown on this page was taken from a Universal Storage Platform VM system. You can see that only the Cache Basic configuration is available.

Configuration and Offline SVP System Option


System Option

6

Universal Storage Platform V Universal Storage Platform VM

This page shows a DKC Configuration main screen from a Universal Storage Platform V, on the left, and also from a Universal Storage Platform VM, on the right. The Universal Storage Platform V has more Cache Options available which makes it possible to immediately determine whether you are looking at the configuration for a Universal Storage Platform V or a Universal Storage Platform VM.

Select the System Option tab to view the configuration settings for Spare Disk Recover behavior, Disk Copy Pace and Copy Operation.

The other important setting in the System Options is the setting for Power Lost Mode. Memory Backup Mode is the default.

The System Option screen has the Mode.. and Write Through buttons to view the Mode settings and Write Through settings at the LDEV level.

Configuration and Offline SVP Power Supply Configuration – Universal Storage Platform V


Power Supply Configuration – Universal Storage Platform V

7

Another indication that the configuration is from a Universal Storage Platform V is that there will be Power Supply configuration options. These can be viewed or set by selecting on the Power Supply tab.

The AC power configuration options are presented in the drop-down list. The optional Power Supplies are identified by checking the box(es) according to which Power Supplies are installed.

As there is only one Power Supply configuration for the Universal Storage Platform VM, there is no information displayed about the Universal Storage Platform VM Power Supply in the configuration screens.

Configuration and Offline SVP Usable CUs


Usable CUs

8

This page shows the maximum number of configurable CUs in the expanded drop down list and also only 64 CUs that are available in the current configuration.

In either the Change Configuration dialog or in the Offline SVP, you can use the drop-down list of how many control units have been configured to be usable. Recall that within one logical disk controller (LDKC), up to 255 control units can be used by the customer to define LDEVs.

At the time when this course was developed, on LDKC 00 was supported. Hitachi has announced the intent to expand the architecture to include a second LDKC, LDKC 01. Refer to the documentation for the microcode version to determine which LDKCs are supported.

Configuration and Offline SVP Mode Settings


Mode Settings

9

Clicking on the Mode tab will open the screen where you can see which mode bit settings are set. Mode bit settings control the behavior of the microcode.

The Mode settings are a series of 1024 bit switches. Use the <<Down and Up>> buttons to scroll through the individual Modes from 0 through 1023. Again, you can only view but not change the Mode settings.

Configuration and Offline SVP LDEV Synchronous Destage– Write Through


LDEV Synchronous Destage– Write Through

10

Write Through or Synchronous Destage Mode can be changed on an individual LDEV basis. The default is Synchronous Destage Mode ON. This setting would be changed only on discussion with the customer and Hitachi Ltd. Recommendation.

Configuration and Offline SVP Internal IP Address of the SVP


Internal IP Address of the SVP

11

After looking at the System Options, return to the DKC Configuration screen.

The next section of Configuration data is the setting of the internal IP address and subnet mask for the SVP. This is set during the New Installation process.

The internal IP address of the SVP and other microprocessors can be determined either based on the Serial Number of the storage system or as specified by the customer. Some customers will be unwilling to accept IP addresses that can be calculated based on an algorithm. Once the internal IP address range it set, it is a disruptive process to change it. The IP address of the primary SVP always uses the lowest node value of 15.

If a second SVP is configured, its IP address lowest node will be 14.

The specific internal IP addresses of the other microprocessors in the system can be seen by viewing the hosts file on the SVP. The range of IP addresses for all possible microprocessors is defined in the hosts file. The microprocessors may not yet exist in the storage system. This depends on which disk adaptor (DKA) and channel adaptor (CHA) PCBs are installed.

Configuration and Offline SVP Specified IP Address


Specified IP Address

12

• If using a specified internal IP address range, be sure that someone documents and remembers the internal IP address. Otherwise, the CE will not be able to connect the CE laptop.

When you are in a mode that permits configuration changes and you select Specified for the internal IP address and subnet mask of the primary SVP, you will be allowed to manually enter the highest three nodes of the IP address and subnet mask.

One step of the New Installation procedure requires that a Specified IP address and Subnet mask is set for the SVP.

Configuration and Offline SVP Cache Configuration – Universal Storage Platform VM


Cache Configuration – Universal Storage Platform VM

13

The cache configuration summary is shown on the main configuration screen. Access the cache configuration detail by clicking on the Cache Configuration.

The Cache Configuration detail screen shows the cache DIMM size, whether any cache has been configured for On-Demand access, and the amount of cache that has been configured for Dynamic Cache Residency (DCR).

The lower section of the Cache Configuration detail shows how the cache is allocated across multiple Cache Logical Partitions (CLPRs).

Configuration and Offline SVP Cache Configuration – Universal Storage Platform V


Cache Configuration – Universal Storage Platform V

14

The configuration screen for cache configuration of a Universal Storage Platform V includes the Cache Options 1, 2 and 3 that are available for the larger system.

Configuration and Offline SVP Setting Dynamic Cache Residency Cache


Setting Dynamic Cache Residency Cache

15

This screen shows the options for setting DCR cache. The size of the amount of cache available for DCR is configured by clicking DCR Change.

The amount of DCR cache can be increased only during the Change Configuration process that increases the total amount of cache on a system.

The amount of DCR cache can be decreased only during the Change Configuration process that decreases the total amount of cache on a system.

Cache Logical Partitions are supported on both the Universal Storage Platform V and Universal Storage Platform VM.

The ability to configure and adjust CLPRs is also made possible through the Web Console application and Storage Navigator.

Configuration and Offline SVP Cache Logical Partitions


Cache Logical Partitions

16

Separate Cache Logical Partitions (CLPRs) can be created or increased during a Change Configuration that adds cache to a system. When adding cache, the CLPR(s) to which the new cache should be allocated can be specified.

The screen above shows how to specify a Cache Logical Partition other than the default CLPR0.

Note:

This screen example was taken from a Universal Storage Platform V but this applies to the Universal Storage Platform VM as well.

Configuration and Offline SVP CHA/DKA Configuration – Universal Storage Platform VM


CHA/DKA Configuration – Universal Storage Platform VM

17

Clicking Next displays the CHA/DKA configuration.

A Universal Storage Platform VM will have only one pair of DKA PCBs in Logic Box slots 1A and 2F.

The CHA/DKA Configuration shows which Logic Box slots contain CHA or DKA PCBs.

Because this is a Refer Configuration, the Change button is not active.

Configuration and Offline SVP CHA/DKA Configuration – Universal Storage Platform V


CHA/DKA Configuration – Universal Storage Platform V

18

This screen shows a CHA/DKA Configuration screen from a Universal Storage Platform V. Universal Storage Platform V configuration must have a minimum of four DKA PCBs, two in Cluster1 and two in Cluster2.

Configuration and Offline SVP CHA Fibre PCB Configuration


CHA Fibre PCB Configuration

19

The screen shows the detail of the CHA Fibre PCBs and individual ports. Configurable attributes of the CHA PCBs and ports include the Fibre Mode setting for each port block, the port behavior, channel speed and range of LDEV addresses that can be accessed through the port.

Configuration and Offline SVP Fibre PCB Mode for CHA Ports


Fibre PCB Mode for CHA Ports

20

Setting of the Fibre PCB Mode setting for the front-end CHA ports is accessed by clicking the Fibre Mode tab.

Front-end CHA ports can be configured to operate in either Standard or in High Speed/MIX mode.

Configuration options for front-end ports apply to both Universal Storage Platform V and Universal Storage Platform VM.

‘Standard versus High Speed/Mix’ is a configuration decision that affects I/O performance through the front-end ports and the associated microprocessors. This decision depends on characteristics of the I/O workload being handled by the ports. If you are interested in more information, you might be interested in courses on I/O Performance and Tuning.

Configuration and Offline SVP Architecture of High-density CHA PCBs


Architecture of High-density CHA PCBs

21

1A

3A

5A

7A

1B

3B

5B

7B

High-density CHA PCBs are configured such that each microprocessor handles the I/O for two ports. This is the default configuration for the high-density CHA PCBs and is described by the Fibre Mode of Standard. In cases where the customer wants one CHP microprocessor to drive the workload for only one port, the alternate Fibre Mode setting of High Speed/MIX would be selected. In order to change the Fibre Mode setting, there must be no I/O flowing through the port. Because two microprocessors are configured to support four ports in a crossed pattern, the Fibre Mode setting applies to a set of two microprocessors and four ports. This group of microprocessors and ports is called a Port Block. The diagram above shows the two-port-to-one-microprocessor architecture. It also shows the crossed support of a Port Block in Standard Fibre Mode with the first microprocessor serving the first and third ports and the second microprocessor serving the second and fourth ports. The configuration screen image on the right shows how four ports in the A block are changed to High Speed/MIX mode when the Fibre Mode is changed. It is not obvious from the Configuration screen that the third and fourth ports are not usable when the port block is operated in High Speed/MIX Fibre mode.

Configuration and Offline SVP Port Initiator or Target Behavior


Port Initiator or Target Behavior

22

Another configurable attribute of the CHA ports is whether the port operates as a Target, RCU Target, Initiator or External port. The default behavior for all CHA ports is Target.

External port behavior is used when connecting external storage systems for virtualization.

RCU Target and Initiator ports are used when the Remote Replication products, Hitachi TrueCopy® products or Hitachi Universal Replicator software, are configured between two Hitachi Enterprise Storage Systems.

The port behavior can be set during the Change Configuration process to add the new CHA PCBs.

This architecture and configuration is the same for both Universal Storage Platform V and Universal Storage Platform VM.

Configuration and Offline SVP Port Behavior Affects Two Ports


Port Behavior Affects Two Ports

23

This configuration screen shows the result of changing the behavior of one CHA port. While this setting is described as the “Port Attribute”, it really controls the behavior of the microprocessor. When a port block is set to Standard Fibre Mode, one microprocessor is serving two ports. Changing the port attribute on either of the two ports changes the behavior of the microprocessor and thus also changes the behavior of the second port. The image on this page shows the result of two ports being changed.

It is important to observe that changing CHA settings for one cluster does not affect the other cluster. It is up to the architect and engineers to design and implement multipath access across both clusters.

The storage system, its architecture and microcode implement the multipathing within the customer’s SAN in which the storage system is deployed. The customer’s implementation of the storage system must deliver the multipath access up to and including the front-end CHA ports.

Configuration and Offline SVP DKA Configuration – Back-end Loop Speed


DKA Configuration – Back-end Loop Speed

24

Universal Storage Platform VMUniversal Storage Platform V

One of the major architecture changes implemented with the Universal Storage Platform V/VM systems is the back-end loop speed of 4Gbit/sec (gigabits per second). This is also a part of the configuration where there are differences between the Universal Storage Platform V and Universal Storage Platform VM.

The Universal Storage Platform V has a separate set of back-end data loops that can be configured to operate at either 2Gbit/sec or 4Gbit/sec. In a fully populated Universal Storage Platform V, there will be four sets of back-end DKA loops.

The Universal Storage Platform VM has only one set of back-end DKA loops and these will operate at 4Gbit/sec. There is back-end loop speed configuration choice for the Universal Storage Platform VM.

Configuration and Offline SVP Rules for 4Gbit/sec Back-end Loops


Rules for 4Gbit/sec Back-end Loops

25

• In order to operate the back-end data loops at 4Gbit/sec, these requirements must be met:

– Back-end loops must be configured to operate at 4Gbit/sec when the DKA PCBs are installed.

• This is the only option for the Universal Storage Platform VM.• Changing the back-end loop speed is a disruptive process on the

Universal Storage Platform V.– In order to operate at 4Gbit/sec, all HDDs on the loops must be capable of

operating on a 4Gbit/sec loop.• Installing a slower performance 2Gbit/sec drive on a 4Gbit/sec loop will

damage the drive.– 4Gbit/sec drives can be installed on 2Gbit/sec back-end loops but the drives

will perform at the lower data transfer rate.– Failed HDDs can only spare out to a drive on a back-end loop of the same

speed.• Previous drive failure requirements also still apply

– Equal or larger capacity– Same rotation speed

For the enhancement of the back-end data loop architecture to accommodate the higher 4Gbit/sec performance, some additional architecture constraints are introduced: Only HDDs capable of operating on a 4Gbit/sec loop can be installed on back-end loops configured to operate at 4Gbit/sec. All HDDs in a Universal Storage Platform VM must be 4Gbit/sec drives. The 750GB and 1TB SATA drives themselves are rated at 3Gbit/sec but have a 4Gbit/sec interface so that they can be used on Universal Storage Platform V and Universal Storage Platform VM 4Gbit/sec back-end loops. All the 15k rpm rotation drives run a 4Gbit/sec interface. In a Universal Storage Platform V, it is possible to have a mix of 2Gbit/sec and 4Gbit/sec back-end loops. This setting must be consistent across the set of back-end loops that are implemented on a set of 4 DKA PCBs that work together as a unit. The 4Gbit/sec back-end architecture adds an additional rule to the sparing out of failed HDDs:-A failed HDD can only spare out to a spare operating on a back-end loop of the same speed as the failed HDD. However, the architecture’s former sparing requirements still must be met:- A failed drive can spare out to any available spare of equal or greater capacity, same rotation speed and same drive interface type (FC or SATA). Note: The information is taken from USP V INST01-430 ~ INST01-433 and USP VM INST01-250 ~ INST01-280.

Configuration and Offline SVP Rules for Sparing out a Failed HDD


Rules for Sparing out a Failed HDD

26

On Universal Storage Platform V, the back-end data loop speed option introduces some additional requirements to how the storage system will identify an available spare in the case of a failed or failing HDD.

Configuration and Offline SVP DKUs Installed


DKUs Installed

27


When HDDs are installed beyond DKUR0, the DKU Equipment Configuration screen will identify which additional DKUs are installed.

The Configuration for additional DKUs varies between the Universal Storage Platform V and the Universal Storage Platform VM.

Universal Storage Platform VM houses the DKU-R1 within the same rack as the DKU-R0.

Universal Storage Platform V houses any DKUs beyond DKU-R0 in a different cabinet, starting with the R1 cabinet and later filling the R2, L1 and L2 cabinets.

Remember that as DKUs are added, the lower section of the R1, R2, L1 and L2 cabinets are populated before the upper section of each respective cabinet.

The configuration screens for the Universal Storage Platform V, on the left of the page, show that the fibre switch module (FSWs) in the upper section of the R0 cabinet are the ones that are installed.

Configuration and Offline SVP RAID Groups in B4s


RAID Groups in B4s

28

The next set of screens in the Configuration dialog allow you to view the RAID groups within the B4s. Highlight the B4 then select the Detail tab.

The Parity Group Configuration screen shows the RAID structure, number of HDDs in the RAID/Parity Group, the Drive Type and the individual four-drive parity group IDs, and the number and Drive Type for installed Spare drives.

For the eight-drive Parity Groups, you can see the corresponding Parity Groups that work together to form these groups.

If the storage system includes eight drive parity groups, you should be able to determine whether you are looking at the configuration for a Universal Storage Platform V or a Universal Storage Platform VM.

How can you tell? In a Universal Storage Platform VM, eight drive parity groups are constructed from two adjacent four drive parity groups in the same B4. In a Universal Storage Platform V, eight drive parity groups are constructed from the same numbered parity groups in two different B4s.

Apply this logic to the configuration shown on this page. Is this storage system a Universal Storage Platform V or Universal Storage Platform VM?

Configuration and Offline SVP RAID Groups in B4s


29

Here is the image for the second B4.

Configuration and Offline SVP Remaining Capacity View


Remaining Capacity View

30

The Device Emulation Configuration screen shows the emulation for the Parity Groups. When the Parity Group’s LDEV configuration has been defined, this screen displays the number of LDEVs per Parity Group and if they have been configured using the VLL interface (CVS).

The Remain tab will display information about the remaining capacity in the system and allows you to display the remaining capacity with different HDD types.

Configuration and Offline SVP Concatenated Parity Groups


Concatenated Parity Groups

31

The RAID Concatenation Configuration screen shows which parity groups have been concatenated to form RAID1 (4D,4D) or RAID5 (7D,1P) x2 or x4 structures.

Concatenated parity groups are supported on both the Universal Storage Platform V and Universal Storage Platform VM.

Configuration and Offline SVP Variable Volume Size LDEV Definition


Variable Volume Size LDEV Definition

32

The next Configuration information view shows the individual LDEVs on a parity group. For parity groups set for OPEN-V emulation, the LDEV structure can be defined using this Variable Volume Size Define interface.

If the OPEN-V LDEVs are defined using the Offline SVP or using the Configuration dialog during the New Installation process, the LDEVs will be created when the parity groups are formatted. The parity groups can also be installed as free space and the customer’s storage administrator can use VLL through Storage Navigator to format the LDEVs later.

Configuration and Offline SVP LDEV Detail of a Parity Group


LDEV Detail of a Parity Group

33

Highlight Parity Group and select the Detail tab to see the LDEV ID assignments and any LUSEs that have been defined.

Configuration and Offline SVP Assigning LDEV ID


Assigning LDEV ID

34

Select an individual LDEV and select the ID tab. Again, in the Refer Configuration, you can only view the LDEV ID table.

In a Change Configuration dialog, you select the LDEV ID assignment for any new LDEVs.

Configuration and Offline SVP SSID for Each CU


SSID for Each CU

35

The Subsystem ID Configuration screen shows the SSID assigned to the Control Units. Every Control Unit that is used to identify LDEVs must also have an SSID assigned.

Configuration and Offline SVP Assigning LDEVs for DCR


Assigning LDEVs for DCR

36

Any LDEVs that are identified to be held in cache are displayed in the DCR Configuration.

Configuration and Offline SVP Shared Memory Configuration – Universal Storage Platform VM


Shared Memory Configuration – Universal Storage Platform VM

37

The Shared Memory Size Configuration is displayed next.

It is easy to identify that this configuration is for a Universal Storage Platform VM as there are no Shared Memory options for a Universal Storage Platform VM.

You can see the DIMM sizes installed in the respective shared memory slots on the Shared Memory PCBs.

You can also see what replication functions have been selected.

Configuration and Offline SVP Shared Memory Configuration – Universal Storage Platform VM


38

The next Configuration screen shows the Shared Memory. The example here shows the Shared Memory configuration of a Universal Storage Platform VM. On this screen you can view or set how many Shared Memory PCB pairs are installed in the storage system. The number and size of Shared Memory DIMMs is also viewed or set through this screen. The required number of Shared Memory DIMMs will change depending on which functions are selected.

Configuration and Offline SVP Battery Configuration


Battery Configuration

39


The Battery Configuration screen for the Universal Storage Platform V is shown on the left. There are optional batteries in each cabinet. The optional batteries in the DKC-R0 cabinet are required if the cache memory equals or exceeds 80GB and/or if the customer selects to operate the storage system in Destage Mode in case of the loss of power.

The configuration on the right is for a Universal Storage Platform VM. It has the optional SB Battery configuration.

Configuration and Offline SVP LUN Management – Port and Host Group Settings


LUN Management – Port and Host Group Settings

40

The last screen in the Configuration dialog allows you to view or set the LUN configuration. This includes the front-end port settings, host groups, WWNs in host groups and LUNs.

Configuration and Offline SVP LUN Management – LUNs and LUSE


LUN Management – LUNs and LUSE

41

LUN mapping and Logical Unit Size Expansion (LUSE) can be managed from the LUN Management screen at the end of the Configuration dialog.

After the port settings, host groups and host WWPNs have been configured, change the Display view to LUN. From the LUN menu, you can add LUNs to Host Groups.

The LUSE menu option will allow you to build LUSE volumes.

Configuration and Offline SVP LUN Management – LDEV View


LUN Management – LDEV View

42

The Logical Device view shows the LDEVs by CU. In the LDEV detail window at the lower right, the emulation, creation method, Command Device setting, Data Retention Utility setting (formerly known as LDEV Guard) and in which SLPR-CLPR the I/O is managed.

Configuration and Offline SVP Complete the Configuration


Complete the Configuration

43

The LUN Management screen is the last in the Configuration dialog. Whether you are changing or simply reviewing the configuration, when you are done, click the Exit icon (red door icon) to complete the Configuration dialog. The LUN Management completion prompt will be displayed.

Configuration and Offline SVP Refer Configuration Completed


Refer Configuration Completed

44

The completion message will be displayed.

Configuration and Offline SVP Create Configuration Backup


Create Configuration Backup

45

1

2

3

4

In order to take a backup of the configuration data,

Put the SVP Application into Modify Mode

1. Click Install.

2. Click Copy Config Files.

3. Click Create Configuration Backup

Respond to the next screen and specify whether the backup will be taken to a USB memory drive on the SVP or to a drive on the Management PC.

Confirm any prompts. If using a USB memory drive, be sure to follow the steps to remove the drive safely.

Configuration and Offline SVP No Formatting of Configuration Media Required


No Formatting of Configuration Media Required

46

For the Universal Storage Platform V and Universal Storage Platform VM, configuration backup can be recorded on a USB drive attached to the SVP or to the Maintenance PC. Configuration backup can also be taken to a writeable CD or to the hard drive of the Maintenance PC.

If you are familiar with Universal Storage Platform and Network Storage Controller, you may recall that the configuration backup floppy diskette had to be formatted with a special utility file that was provided on the microcode CD. This procedure has been eliminated and there is no pre-formatting required for the configuration backup media for Universal Storage Platform V/VM systems.

The configuration backup process will create a directory structure of \DKC200\CONFIG\<serial number> if it does not exist.

If this directory path exists, a prompt will be displayed warning that the existing data will be overwritten.

The other benefit of the new structure for configuration backup is that multiple configurations for different systems can be kept on the same media. For example, it is possible to keep multiple configurations on one USB memory drive.

Configuration and Offline SVP Offline SVP


Offline SVP

47

The Offline SVP application is a software utility that is delivered on the microcode CD. The Offline SVP needs to be installed on a Windows PC other than the SVP. The Offline SVP can be used to view, change or create valid configuration definitions for Universal Storage Platform V or Universal Storage Platform VM storage systems.

For the Universal Storage Platform V/VM, the documentation and tools are delivered on the third CD in the set. The Offline SVP is found in the Tools_Pack\CNF_TOOL\off_svp folder.

Install and use the correct version of the Offline SVP tool. The Offline SVP tool has a component version that is directly tied to the version of the microcode.

Insert the CD in the CD drive and execute the setup.exe to install the Offline SVP application. If setup.exe seems not to execute, check to see if you have registered this executable with the Windows Data Executable Program (DEP) interface.

Configuration and Offline SVP Install the Offline SVP Tool


Install the Offline SVP Tool

48

Check the current documentation to confirm that the Maintenance PC is supported, particularly the version of Windows.

Note: At the time this course version was developed, Windows Vista was not yet supported. As of Universal Storage Platform V/Universal Storage Platform VM microcode release 60-02-48, future support for Windows Vista on the SVP was announced. The implementation of IPv6 will require Windows Vista. You can expect that Windows Vista for the Maintenance PC will also be supported at that time.

There can be only one version of the RAID600 Offline SVP installed at any given time. You may be prompted to confirm that you know the C:\DKC200 directory will be overwritten when you install a newer version of the Offline SVP tool. At the time this course was developed, the Offline SVP installation did not provide the option to specify on which drive to install the utility. It was always installed on the C:\ drive.

Confirm the prompts to complete the installation of the Offline SVP.

Configuration and Offline SVP Installation Progress and Completion Message


Installation Progress and Completion Message

49

The installation of the Offline SVP application is quick. The Setup Complete window is displayed.

Confirm the prompt and remove the microcode CD.

Configuration and Offline SVP Offline SVP Tool


Offline SVP Tool

50

• Using the Offline SVP tool on the Maintenance PC

After the Offline SVP has been installed, you can start it from the Windows: Start > Programs menu. Select the RAID600 Offline SVP > Desktop Define Install option.

Configuration and Offline SVP Value of an Offline SVP Application


Value of an Offline SVP Application

51

• The Offline SVP is a tool that is useful:– To review a storage system configuration when you have the configuration

data but do not have access to the SVP– To build a new configuration for a new storage system

• In preparation for a new installation if a configuration is not available

• Source: ECN

Hitachi provides the Offline SVP tool that enables review and creation of the configuration specifications for a storage system. The Offline SVP tool is delivered with the microcode CD set. The Offline SVP tool is found on the Documentation and Tools CD.

In the ECN, this utility program is identified as the Offline Configuration and Print Out Tool: Special Tool for CE. The program name is CONFUTL. The Offline SVP tool has a version. It is important to install and use the correct version of the Offline SVP that corresponds to the microcode version of the storage system.

Configuration and Offline SVP Summary


Summary

52

• Different ways to view, change or create a valid configuration for a Universal Storage Platform V or Universal Storage Platform VM storage system

• Screens of the Configuration dialog• How to make a backup of a storage system’s configuration data• What is the Offline SVP tool• How to locate, install and use the correct version of the Offline SVP tool


8. Hardware Maintenance

Module Objectives

• Upon completion of this module, the learner should be able to:– Describe the use of the SVP Application Maintenance interface to identify

and replace failed components– Use the Maintenance manual and other documentation– Plan the replacement of physical components– Execute the replacement of physical components– Perform self-replace of any field replaceable component in the storage

system

By the end of this module, you should be able to describe and complete the replacement of any of the field replaceable components.

You should be able to locate the correct location in the Maintenance interface to select the component to replace. You should know how to establish the conditions required enabling the removal of the component.

You should understand the importance of reading the messages that are displayed by the Maintenance Dialogs and the importance of performing the correct actions in the correct sequence.

Hardware Maintenance What is Maintenance?


What is Maintenance?

3

Maintenance is:

A process of performing maintenance for Hitachi Universal Storage Platform™ V or Universal Storage Platform VM at the customer site

A set of procedures to replace failed or failing components with new components. Parts are not modified or maintained in the field, only replaced.

The SVP application is used to prepare the system for a component replacement. This is a critical part of the maintenance process. Because of the duplex architecture and multipath I/O flow within the storage system, the maintenance procedures allow the microcode to reroute I/O tasks on alternate paths and components so that the component can be removed and replaced.

The Maintenance interface is designed to guide you directly to the component needing maintenance. In order to successfully perform a Hot Replace or nondisruptive maintenance, it is vitally important to use the correct maintenance dialog and to follow the instructions exactly.

Adding or removing capacity is accomplished through the Install interface of the SVP application. Adding capacity is performed using the Change Configuration process, removing capacity is performed using the De-install process.

Hardware Maintenance When is Maintenance Required?


When is Maintenance Required?

4

• Maintenance or replacement of components is required when– A bad or failed part is detected and reported by the storage system

• A Systems Insight Manager (SIM) is reported that involves replacing a component

– Batteries have reached their life expectancy– Periodic cleaning or replacement of the air filters needs to be done

• Microcode exchange (upgrade) is also considered to be a maintenance activity and is managed using the maintenance dialogs

Under normal conditions, the Universal Storage Platform V or Universal Storage Platform VM will be installed at the customer site, the cabinets will be closed, the system will be put into operation and it will function normally, without error.

Battery life expectancy is three years. Battery replacement SIMs will be raised when the batteries reach their end of life. Replacement batteries are charged before they are shipped. Mandatory battery management procedures are documented in the Parts section of the Maintenance manual. See page Parts06-90.

Consult the Periodic Maintenance section (09period.pdf) of the Maintenance manual. This manual section also describes the removal and reinstallation of the air filters. Periodic cleaning of the air filters is prescribed. As the air filters are not part of the hardware architecture, the SVP is not needed for the completion of this task.

Hardware Maintenance Automated Notification using Hi-Track® Monitor


Automated Notification using Hi-Track® Monitor

5

• Hitachi Data Systems Centralized Support – Applies to all storage systems

• Centralized Support is available for all types of Hitachi Data Systems’storage systems including enterprise, modular, Hitachi Content Archive Program, NAS, Simple Modular Storage

• Centralized Support is available for all Hitachi Data Systems and Sun branded systems even those sold, installed and supported by Partner organizations.

• Assumes Hi-Track Monitor is Installed– Known as “Call Home on Error”– Requires a phone line (FTP option also available)– Reports maintenance problems through phone line to Hitachi Data Systems– Email forwarded to Sun Support for FE dispatch– Or email forwarded to Global Support Center (GSC) to dispatch Customer

Engineer (CE) from Hitachi Data Systems– CE performs maintenance action– CE closes the case– CE returns bad parts to Hitachi

If the storage system is configured to report on-error through Hi-Track Monitor, you may receive electronic notification that the storage system requires maintenance.

Maintenance may be indicated by a SIM detected at the customer site, if the storage system is not configured for Hi-Track Monitor.

Hardware Maintenance Field Replaceable Units


Field Replaceable Units

6

• Field Replaceable Components Include:– PCBs and DIMMs

• Shared Memory– Shared Memory DIMMs

• Cache Memory– Cache Memory DIMMs

• Cache Switch• Channel Adaptor (CHA) and/or CHF• SFP• Disk Adaptor (DKA)• Cables

– Power Supply Section Components• Batteries• Power Supplies

– DKU Components• Servers (SVRs)• Fibre Switch Module

(FSWs)• HDDs

– Data– Spare(s)

– Other Components• Service Processors

(SVP)• SSVP• Operator Panel

For maintenance on any of the field replaceable components, navigate to that component in the Maintenance interface, select the component and select the Replace option. Confirm the prompts and take the actions prescribed by the Maintenance dialog.

Hardware Maintenance Accessing the Maintenance Interface


Accessing the Maintenance Interface

7

To access the Maintenance dialog interface, the SVP Application must be in Modify Mode.

Select Maintenance tab or select the Maintenance option from the Execute drop-down menu.

Hardware Maintenance Maintenance View


Maintenance View

8


Hitachi has re-designed the SVP Maintenance interface with the release of the Universal Storage Platform V and Universal Storage Platform VM storage systems.

Maintenance means replacement. The storage system may report a maintenance or replacement issue if a component is not installed correctly or fully into its slot within the storage system hardware architecture. If a component has been functioning and subsequently indicates the need for maintenance, then, this part needs to be replaced with a new part supplied by Hitachi.

Maintenance does not mean fixing the part and reinstalling it at the customer site. Failed parts are returned to Hitachi for analysis.

Some of the improved features are that all the information views are maintained as the maintenance engineer navigates to more detailed levels of system information. The older versions of the SVP maintenance interface included sub-windows which opened in front of the higher level windows, making it challenging to keep track of information that was presented on earlier panes.

The SVP Application Maintenance interface indicates which components are installed in the storage system, all the way from the cabinet configuration down to individual HDD canisters.



If there is a failed part, the entire installation path on which that component exists will blink when displayed in the Maintenance interface. Click on the path of blinking icons to locate the part that requires replacement.

This page shows the maintenance view of a Universal Storage Platform V with the DKC cabinet and one DKU cabinet in the R1 position. Notice that the DKU cabinets R2, L1 and L2 display as “Not equip.”

Any failed part in the DKC cabinet will cause the DKC cabinet icon to blink. Click on the DKC cabinet icon to navigate to the next component level within the DKC.

Any failed part in the DKU R1 cabinet will cause the R1 icon to blink. Click on the R1 cabinet icon to navigate to the next component level with that DKU.



9

• Universal Storage Platform V DKC

This screen shows the Disk Controller Maintenance view for a Universal Storage Platform V. The cabinet view is maintained and is shown at the bottom of the right-hand pane of this interface. This view also shows the Front Side, Cluster 1 and the Rear Side, Cluster 2 on one view.

The blue information area with white text displays the “bread crumb trail.” This shows “where you are and how you got there” in your navigation. You can move back up to a previous view by clicking on that entry in the bread crumb trail. This is a common web interface navigation feature that Hitachi has integrated into the new SVP Maintenance application design.

If there is a component that needs maintenance, the corresponding icon would blink on this screen.

The following components are field replaceable: Operator Panel SVP Fans Thermostats



10


The Maintenance view for Universal Storage Platform VM is slightly different from Universal Storage Platform V due to the different physical arrangement of the replaceable components.

Hardware Maintenance Maintenance View – Logic Box


Maintenance View – Logic Box

11

Universal Storage Platform V Universal Storage Platform VM

This screen shows the Logic Box maintenance interface for both a Universal Storage Platform V and a Universal Storage Platform VM. The Logic Box view is where you would indicate the maintenance or replacement of any installed PCB. This includes Shared Memory, Cache Memory, Cache Switch, CHA or DKA.

When you click on one of the Logic Box icons, the next view shows the individual slots within the Logic Box and whether or not there is a PCB in the slot. If a PCB or component on a PCB needs maintenance, that icon will blink.

For the Universal Storage Platform V, the Front and Rear Logic Box configuration is added to the bottom of the screen.

These components are field replaceable: Shared Memory PCBs Cache Memory PCBs Cache Switch PCBs DKA PCBs CHA PCBs

Use the radio button selection to identify the component to be replaced.

Hardware Maintenance PCBs in the Logic Box


PCBs in the Logic Box

12

Bread crumb trail


This screen shows one specific Shared Memory PCB in the Cluster 1 Logic Box has been selected. Notice that a detailed view of this Shared Memory PCB is displayed with a Replace tab and Other tab. This screen shows that the PCB status and Logical Path Status are “Normal.”

It is not possible to simulate a failed component in an enterprise storage system. These systems will not accept a bad or failed part into the configuration. It is simply not possible to install a bad part and then debug and correct the situation.

If the Replace tab is selected on this screen, the next screen will provide the option to (self) replace Shared Memory PCB. If an individual Shared Memory DIMM is reporting an error, that is, it is blinking; you would click on that icon. In order to access memory DIMMs either for Shared Memory or Cache Memory, the PCB must be removed.

If you expand the Other tab you will see the options to Blockade or Restore the paths.

Note: In the maintenance lab, you will practice a “dummy self-replace” of components.

Hardware Maintenance PCBs in the Logic Box


13


Selecting the radio button for one of the installed memory PCBs will display a detailed view of the PCB and its DIMM slots. If the system has detected that one or several specific DIMMs have failed, then only the icons for these components will appear as blinking. Still, to replace a memory DIMM, the entire PCB must be removed.

Start the component replacement process by selecting the Replace tab. You will see a series of confirmation prompts and action instructions.

Hardware Maintenance Follow the Instructions


Follow the Instructions

14

The maintenance procedure for any PCB component within either Logic Box is the same. Using the Maintenance interface of the SVP Application, navigate to the blinking component and select Replace.

Note:

It is imperative that the instructions presented by the Maintenance dialogs must be followed in the same sequence.

In the situation where the dialog box has “Check that the LED of the component is lit, then Click OK”, you must go to the storage system and visually confirm that the correct LED is lighted.

In the situation where the dialog instructs you to replace component, then click OK:

You must physically remove (unseat) the component, the reinstall the same or new component, then return to the Maintenance PC and click OK.

Clicking OK before the action is taken will cause the Maintenance task to not complete successfully.

If you click OK and then replace the component.

Hardware Maintenance Follow the Instructions


If you do not remove and reinstall the part, leaving the component as is and just click OK.

The storage system knows whether or not the component has actually been removed and subsequently (re) installed.

Make sure to use anti-ESD protection whenever you touch or handle these electronically sensitive components.

Hardware Maintenance Cache Memory and Shared Memory


Cache Memory and Shared Memory

15

• Memory Maintenance– Replacing DIMMs

• One or several DIMMs will be blinking• Possibly only one board will be affected• Customer may want to wait till “quiet” time• Use static mat to safeguard DIMMs

– Replacing Boards• All DIMMs will probably be blinking• Performance will probably be degraded

– Duplexing is affected, write-through enabled• Customer probably will want service ASAP• May use existing DIMMs

If the PCB component has failed, you may be directed to use the existing DIMMs and install them on a replacement PCB. Any hardware maintenance task which is performed while the storage system is “up”, continuing to process I/O, is considered nondisruptive. When it comes to Cache memory maintenance, any time half of the cache is unavailable, the storage system operates in Write Through mode. Write I/O is not confirmed to the application until it has been physically written to the disk. The Universal Storage Platform V and Universal Storage Platform VM achieve full assurance of customer data by enforcing the rule of “two copies of all data, at all times.” If half of Cache is unavailable, then data updates cannot be duplexed in cache; two copies cannot be recorded in memory. In order to comply with the “two copies at all times” rule, one copy of the write data is written to the available half of cache but the second copy can only be recorded on the disk, itself. Write Through mode takes longer to confirm the write I/O to the application and the customer can expect this slowdown to affect the application performance. In the event of cache errors the customer will probably need immediate maintenance on the storage system. The maintenance dialog behavior for failed memory whether it is Cache Memory or Shared Memory will be the same. If either a memory PCB or DIMM fails, the icon for the PCB will blink in the Maintenance view on the SVP.

Hardware Maintenance Status LEDs for PCBs


Status LEDs for PCBs

16

Source: 03loc.pdf

The diagram on this slide is taken from the Locations section of the Maintenance manual. The location of the individual component status LED lights is different from other enterprise storage systems. Most of the field replaceable units (FRU) have status LED lights. SFPs do not have status LEDs.

When the part has failed or the I/O traffic has been rerouted and the component has been blocked and is ready for removal, the red LED status light will be lit. The Maintenance dialog will ask you “Is the LED lit?” This means “is the red light on?” Again, you must visually confirm that the correct LED is lighted, and then confirm the Maintenance dialog.

In the case that the removal LED does not get lit during the Maintenance procedure, there is a jumper block on each PCB for forcible removal of the component. You must be extremely careful when deciding to insert a Shut Down jumper for a forcible replacement. A mistake could cause data loss. Do not use Shut Down jumpers unless instructed in the Replace dialog box or by the Support Center.

Hardware Maintenance Maintenance – CHA PCBs


Maintenance – CHA PCBs

17

• Channel Replacements– Path Failover

• A port failure requires board replace or GBICs (SFP)• Have Storage Administrator (SA) force all hosts on bad board to other

HBA port• Single-ported hosts may have to be disrupted or re-configured

– Fibre Cabling• Direct from host, or from Fibre Channel switch• Cabling must be disconnected for replace• In order to restore the correct LUN access paths, you must ensure that

the fibre cables are connected to the correct ports• If cabling is not clearly labeled in some way, STOP• Get local SA to label cables, or be responsible

If you have to replace a channel host SFP or an entire PCB, you will have to disconnect the cable(s).

Leading practices support complete and accurate labeling of physical components in the data center. Ensure that you are able to reconnect the cables to the correct locations.

If the customer’s storage administrator has mapped multiple paths between the storage and the hosts, there should be no I/O interruption to the applications. There may be performance degradation. Make sure that you work with the customer’s staff to ensure that the I/O traffic is successfully re-routed before performing maintenance on channel host PCBs or SFPs.

Hardware Maintenance SFP Replacement


SFP Replacement

18

• Source: 03loc.pdf

Individual SFPs can be replaced without the need to remove or replace the CHA PCB. The fibre cable will have to be disconnected from the SFP. SFPs do not have status LEDs.

When replacing one or several individual SFPs, perform the following steps when instructed by the maintenance dialog:

1. Disconnect the fibre cable.

2. Raise the lever to release the SFP. Remove it.

3. Insert the new SFP and engage the lever.

4. Reconnect the fibre cable.

To perform a batch SFP replacement, put the SVP Application into SFP Mode by clicking the key combination Ctrl+Shift+s

Hardware Maintenance Maintenance – DKA PCBs


Maintenance – DKA PCBs

19

DKA PCBs

Source: 03loc.pdf

The failure of one DKA PCB does not affect the duplexing of customer data in Cache or the duplexing of control information in Shared Memory. It will affect the back-end performance of physical I/O to the parity group disks. Due to the new smaller PCB architecture in the Universal Storage Platform V, failure of one DKA PCB affects only half the back-end loop capacity as compared to the Hitachi Universal Storage Platform™.

DKA architecture still has two back-end data loops supported by one control data loop as shown above. Each DKA PCB contains four data loops and two control loops. The photo on the left shows the pair of DKA PCBs in Cluster 2 of a Universal Storage Platform V. (Cluster 2 has blue cables.) If you look closely, you can see the two sets of two “round” data cables and one “flattened” or ribbon control cable on each of the DKA PCBs.

(The schematic is shown “upside down” relative to how the PCB is installed in its Logic Box slot; this is taken directly from the Locations section of the Maintenance manual.)

Loss of a DKA PCB will affect performance. The extent to which this is noticed in the customer’s environment will depend on the I/O demand during the period when these data loops are unavailable. The storage system architecture and the customer’s

Hardware Maintenance Maintenance – DKA PCBs


implementation of multipath access permit the applications to continue to function until the maintenance is performed.

As with performing maintenance on a CHA PCB, it is critical that you reconnect the DKA cables to the correct locations. For the back-end data loops, the cables are labeled by Hitachi at the time of manufacturing. The information to correctly reconnect the cables is on the cable ends. Use caution and refer to the Locations section of the Maintenance manual to verify the correct connection points.

Hardware Maintenance Status LED for HDD and SVR


Status LED for HDD and SVR

20

HDD

SVR• Universal Storage Platform V

The HDD status LED is on the SVR power supply component. The status light for the SVR itself is also on the SVR and it is present between the status LEDs for the first two HDDs in the HDU.

The above pictures show both HDD and SVR with their removal LEDs lit. The HDD picture is shown with the FSW cover still in-place, the LED lights visible through the magnifier. In order to perform SVR maintenance, the FSW cover must be removed. The location of the SVR status LED could be easily confused with the HDD LEDs.

Be very careful with the location of the HDD and SVR component status LEDs when performing Maintenance on these components.

Ensure that you check the Locations section of the Maintenance manual for the location of the correct status LED for the component you are replacing.

Hardware Maintenance HDD Status Light for Universal Storage Platform VM


HDD Status Light for Universal Storage Platform VM

21

LEDPNLStatus LED

Source: 03loc.pdf

The Universal Storage Platform VM does not use the SVR component for providing power to the HDDs. The DKUPS power supply components deliver the power to the HDDs in the Universal Storage Platform VM. As the Universal Storage Platform VM does not use the SVR component, it has a different component for the status LED s for the individual HDDs. The LEDPNL components are located between the HDU boxes in the DKU-Rx sections of the Universal Storage Platform VM.

There is also a status LED on the LEDPNL for the LEDPNL component itself.

Hardware Maintenance Maintenance – Parity Groups


Maintenance – Parity Groups

22

• LDEV Formats Are Needed– During New Installation– When new array groups are added– When new LDEVs are created using VLL

• Device Blockades Should Occur Only – During subsystem installation, maintenance, upgrade, and de-installation as

stated in the maintenance manual• Configuration change for the DKC is performed

– During subsystem installation, upgrade, and de-installation as stated in the maintenance manual

Devices with a status of “Blocked” are unavailable. This occurs normally during a new installation.

This is also the status of newly added parity groups before the LDEV Format has been performed.

If the Maintenance activity involves de-installing and re-installing any components on the back-end paths, parity groups and/or LDEVs may become blocked. Formatting the storage will make the storage usable and change the status to “Normal.”

Hardware Maintenance Parity Group Maintenance without HDD Removal


Parity Group Maintenance without HDD Removal

23

• As of microcode 60-02-51 or 60-03-05-A, this new procedure is supported.• This Appendix A information is taken from the ECN.

A new maintenance procedure is supported to permit the change of RAID structure or emulation of a parity group without the need to physically remove the individual HDDs from the drive slots.

Set the public mode setting 721 to “on” or checked. Then, perform the Change Configuration> Deinstall of the parity group(s). The Change Configuration dialog will not require the physical removal of the HDD units. The HDD red status LEDs will not be lit. Then, turn “off” mode 721; that is, set it to unchecked. Then perform a Change Configuration > Install for the parity group(s). Specify the desired RAID configuration and emulation. As the HDDs will already be in the correct HDD slots, just click “OK” when prompted in the Change Configuration dialog.

The Parity Group Maintenance lab activity in this course will let you perform this newly supported procedure.

Hardware Maintenance Quick Format Specifications


Quick Format Specifications

24

As of microcode 60-02-51 and 60-03-05A, LDEV Quick format is supported.

Quick format allows the LDEVs to be mapped and used as LUNs before the actual format has completed.

Quick format requires one or more LDEVs to be set as System Disk. Setting the System Disk attribute for an LDEV can only be done through the SVP application.

This functionality is not available through Storage Navigator. LDEVs set as System Disk are not available to be LUN mapped.

Hardware Maintenance Setting the System Disk


Setting the System Disk

25

The LDEVs to be used as system disk space can only be set through the SVP application, Change Configuration dialog.

Setting the system disk space must be performed when the LDEV is defined and formatted. It may be necessary to perform a Volume to Space operation and then perform Install CV to set up the system disk capacity.

LDEVs set to System Disk can only be formatted with a normal (“slow) format operation. System Disk space cannot be formatted using Quick Format.

Hardware Maintenance Completing the Maintenance Task


Completing the Maintenance Task

26

• To complete the maintenance task– Check Maintenance Status

• Look at alert and message lights• Use maintenance to look for blinking parts• Complete the SIMs

– SVP• Make sure to set the SVP application to View Mode• Take a configuration backup if prompted by the storage system

– Close Clarify Case• Notify customer of subsystem status

– Package failed component(s) and collected dump information and return to Hitachi

To complete the maintenance task:

Pack up parts for return: Bad parts are returned Keep packing materials Follow Current Return Procedure:

Fill out the Online Parts Return Tag (Hitachi Data Systems) completely noting all applicable reference codes and any damage or missing parts returned.

When asked, please return the USB memory stick containing Error Logs per the Maintenance manual procedures.

Hardware Maintenance HDD Replacement


HDD Replacement

27

• Drive Replacements– Activities Vary Depending On

• Spare versus data-disk failure• Warning versus blocked status• Presence of spares or not

– SIM Action Code (106x) Leads to RDKn Work ID• RDKn work ID leads to different …• Pre procedures• Hardware procedures• Post procedures

… it just depends on the conditions

Activities vary depending on the state of the disk environment.

Caution:

Follow Anti-Static procedure in Alert "Electrostatic discharge may cause online HDDs to become blocked when inserting HDDs into DKU frames“.

Hardware Maintenance Using the Documentation


Using the Documentation

28

• Drive Replacement Work ID

460XX indicates drive type

Source: 14acc.pdf

No matter where a drive is located, the same work ID is used.

Hardware Maintenance Identifying the Correct Procedures


Identifying the Correct Procedures

29

• Drive Replacement Variables

REP 01-160Source: 07rep.pdf

For a drive related problem, determine the variables:

Data-drive versus spare-drive Seriousness of SIM Presence of a spare

Note that the procedures are generally the same, so study the differences as circled above.

Hardware Maintenance HDD Replacement


HDD Replacement

30

A failed HDD will normally cause a SIM to be generated.

Typical Drive Replacement:

1. Drive fails, SIM generated

2. Correction-copy started

3. Hi-Track tool does “Call Home on Error”

4. IRC opens clarify database case

5. CE dispatched, upon arrival:

1. CE confirms copy status completion

2. CE performs drive replace

a. Diagnostic data written to CD R/W or USB memory

b. Dialogue asks to “Copy Back”

c. CE confirms

3. CE closes clarify case

4. CE boxes up bad part and collected dump information for return

Hardware Maintenance View of Internal Paths


View of Internal Paths

31

If SIMs or blinking icons in the Maintenance views indicate errors in the Hi-Star™ crossbar switch architecture, the CM/SM Path… button is used to view the status of the internal paths.

In the view on this page, all the paths are normal.

Hardware Maintenance IMPL Status


IMPL Status

32

The IMPL function displays the status of the DKP and CHP internal microprocessors. This page shows the normal operating status.

During a non-stop SCSI microcode upgrade, the IMPL status will show the microprocessors during their reboot phase.

Hardware Maintenance Using the Start Section of the Maintenance Manual


Using the Start Section of the Maintenance Manual

33

The Maintenance manual from the microcode CD is a mandatory resource for you to have and use.

If you are not sure which manual section to use, start with the Start section. It has the Start Entry Table that provides “hot links” directly to the appropriate section of the Maintenance manual. Use the navigation tools in Adobe to speed your access to the information you need.

Ensure that you know where to get the correct manuals for the microcode version of the storage system. Each Maintenance manual revision (version) is specific to the type of storage system and microcode version.

Hardware Maintenance Troubleshooting


Troubleshooting

34

• Troubleshooting Manual

The 06trbl.pdf Troubleshooting section of the Maintenance manual can be used as a guide for determining necessary actions in complex situations.

Hardware Maintenance Summary


Summary

35

• Follow Maintenance Manual Procedures– The SVP Application Maintenance interface provides guidance via the

blinking icons– The maintenance manual and its sections provide the supported procedures

• If in doubt, call support• Practice “good form”

– Always check the Logs for existing maintenance issues• Do not rely only on the SIM message light

– Use anti-ESD protection when handling components– Complete SIMs when done– Verify message light is off– Close open calls with support– Make sure to put the SVP Application in View Mode when completed

Hardware Maintenance Summary



9. Prestaging and Site Install

Module Objectives

2

• Upon completion of this module, the learner should be able to:– Identify the tasks that are completed in the Prestaging process– Describe the benefits of prestaging– Explain how prestaging fits into the sales cycle– List specific tasks normally performed when installing a subsystem

at the customer site, including:• Setup• Initial power up• Maintenance checks• Configuration checks

– Determine when a newly installed storage system needs New Installation at the customer site

Prestaging and Site Install Prestaging Overview


Prestaging Overview

3

• Purpose of Prestaging– Assemble Storage System Hardware

• Account team and customer create specification• Build-Center assembles, configures, and then the customer ships

– Hitachi Trucks– Public Carriers

– Configuration Through the “New Installation” Procedure• Load SVP applications and microcode• Write flash-memories of microprocessors• Software configuration (per customer spec or factory default)

– Subsystem is Shipped to the Customer Site• Local Techs Position, Power Up, Finalize Configuration

Prestaging describes the tasks that are performed before the storage system is installed at the customer site. Hitachi Universal Storage Platform™ V and Universal Storage Platform™ VM storage systems are assembled at the appropriate Distribution Center. Each storage system receives new installation which deploys microcode and a valid configuration. The New Installation procedure allows the system to be initially tested and verified to function as a storage system. Any maintenance issues can be identified and corrected before the storage system is shipped to the customer site. The storage system is carefully packed, transported and delivered. Once at the customer site, the Site Installation process includes removing the packaging, setting the storage system into position, connecting the A/C power, powering up the storage system, checking for any hardware maintenance issues and performing a Refer Configuration. If the delivered configuration does not match the customer’s needs, new installation procedure may be executed after the storage system has been installed at the customer site. The Site Installation may include installing, configuring and testing Hi-Track® Monitor, installing license keys, setting the external IP address of the SVP, and setting the Date/Time.

Prestaging and Site Install Prestaging Benefits


Prestaging Benefits

4

• Benefits to Hitachi Data Systems and customers– Single point-of-contact for Hitachi Data Systems by region.

• Subsystems are assembled, configured and tested at one of two sites– IDC in Indianapolis (Americas)– EDC in Waardenburg, Netherlands (EMEA)

– Faster Delivery• Assembly and Configuration Specialists

– Reduced Lead Time from order to arrival– Experts performing new installation regularly– Immediate access to Spare Parts – Universal Storage Platform V and Universal Storage Platform VM

systems that are shipped have been proven to be functioning storage systems

Prestaging provides multiple benefits.

Every Universal Storage Platform V and Universal Storage Platform VM are assembled, configured and tested at a regional Distribution Center. Members of the Distribution Center staff are experts at the new installation process for installing microcode and configuration.

Because the storage systems are assembled and tested at the Distribution Center, it provides immediate access to spare or replacement parts if they are needed. Again, this contributes to short time between customer order and delivery of the storage system. In other words, Prestaging approach contributes to a faster delivery. The storage systems have been tested and verified before being delivered to the customer.

Prestaging and Site Install Prestaging Tasks


Prestaging Tasks

5

• Built-to-Specification– Identify the following from the Prestaging Center

• Frame layout• Power requirements• Channels (number and type), Disk Adaptor (DKA) pairs (how many)• Number of array-groups, number of spares, disk models• RAID and emulations• Cache memory and shared memory amounts

Universal Storage Platform V and Universal Storage Platform VM are built to the specification sold to the customer. This includes number of cabinets or racks, the power connectivity and the configuration of the DKC components in the Logic Boxes.

Prestaging and Site Install Preparing for the Site Install


Preparing for the Site Install

6

• Site Install Checklist – Microcode CDs– USB memory drive for configuration backup– Confirm with the Customer that:

• Position has been identified• Floor tiles/cutouts have been prepared• Power lines are installed • IP address for the storage system on the customer LAN

– Is a new installation required at the customer site?– Should the Hi-Track Monitor be installed?

• Get the Hi-Track installation Software– Hi-Track is distributed separately from the microcode– Hi-Track is not on the microcode CDs

• Will Hi-Track connectivity use analog phone modem or ftp?• What will be the phone number?

Before you go to the customer site to perform a site install of a new Universal Storage Platform V or VM, ensure that you have all the materials and information you need to perform the install.

Someone should be able to help determine whether or not a new installation will be required after the storage system has been installed at the customer site.

Check if the customer wants Hi-Track Monitor installed and configured.

Prestaging and Site Install Site Install Overview


Site Install Overview

7

• Site Install Tasks– Location selection– Unwrapping and positioning– Initial power up– Configuration check– Minor configuration tasks– Licensing– Customer LAN– Verify version dependencies for additional tools

• Hi-Track Monitor• Offline SVP• Export Tool

– Install and test Hi-Track Monitor

Once the storage system is delivered to the customer site, it is unwrapped and moved into the location determined by the customer.

Review the A/C power configuration before applying power to the storage system. A mistake or mismatch between the power at the customer site and how the storage system was configured could damage or ruin the system.

Connect the A/C power and power on the system. Check the status of the BS-ON LED and the PS-ON LED. Check the battery lights. They should be on, blinking or not blinking to indicate fully charged or charging status.

Wait for the Ready LED to light. Check the SIM LED. If an SIM is indicated, investigate the Logs. Resolve any Maintenance situations.

Perform a Refer Configuration. Compare the delivered configuration to the configuration expected by the customer.

If the delivered configuration differs from that expected by the customer, determine whether the correct configuration can be deployed using Change Configuration. The other option is to plan and carry out a New Installation at the customer site.

Prestaging and Site Install Unpack and Set into Position


Unpack and Set into Position

8

• Location Selection Overview– Customer selects location, runs power lines– Customer provides one cutout tile per frame

• Unwrapping and Positioning Overview– Remove sheeting, tape, and cardboard– Position disk controller (DKC) over sub-floor tile– Un-tape and lower the feet so that the DKC can not move easily– Remove tags from jumpers, and then clip jumpers in a convenient location– Remove front Logic Box cover (for host connectivity)– Save all paperwork (packing slip, serial no, and others)

Once the storage system is delivered to the customer site, it is unwrapped and moved into the location determined by the customer.

One floor tile cutout must be supplied for each cabinet or rack.

A Universal Storage Platform V cabinet or Universal Storage Platform VM rack is very heavy. Be extremely careful when moving and positioning the frames.

Prestaging and Site Install Connect, Power On and Check


Connect, Power On and Check

9

• Overview– Verify AC-Box breakers are OFF. – Feed disk controller (DKC) pigtail through tile (two people recommended).– Attach all pigtail leads to correct AC-Box locations.– Triple check pigtail lead connections … don’t guess!– All clear? Plug pigtail connectors into power lines.– Turn ON one breaker and then the other breaker.– BS ON should be AMBER (this is normal).– Check Local/Remote, Enable/On and wait for Ready light.– Check SIM LED.– Check Maintenance interface for issues.

Connect the A/C power and power on the system. Check the status of the BS-ON LED and the PS-ON LED. Check the battery lights. They should be on, blinking or not blinking to indicate fully charged or charging status.

Wait for the Ready LED to light. Check the SIM LED. If an SIM is indicated, investigate the Logs. Resolve any Maintenance situations.

Prestaging and Site Install SVP Configuration


SVP Configuration

10

• Configuring the SVP– Install SVP Security Patches and if required Anti-Virus software per Alert

"Security Upgrades, Hot fixes/patches and Virus Control for the RAID600 SVP Laptop"

– Ensure you have reviewed all TechAlerts and TechTips– Ensure that you have the Maintenance documents from the microcode CD– Ensure that the customer has all applicable Configuration and

Users Guides

• Note: Even though the Trend Micro anti-virus solution is included in the Maintenance Manual by the factory, this anti-virus option is not supported.

• This Anti-Virus Software support table is taken from the ECN

Information about the anti-virus configuration for the SVP is found in the ECN. Tech Tips are also released periodically about anti-virus recommendations from Microsoft. Keep current with the recommendations from Hitachi and work with the customer to identify and implement the necessary anti-virus solutions on the SVP.

Prestaging and Site Install SVP Secure Communication


SVP Secure Communication

11

https://

If the customer needs the SVP to be configured for secure communication, review the ECN and the Maintenance manual and follow the instructions for setting up SSL.

Prestaging and Site Install Configuration Check


Configuration Check

12

• Refer Configuration– Compare the storage system microcode versions with the ECN.– Use “Refer Configuration” to check installed equipment.– Check Control Unit (CU) count and subsystem IP.– Check Array Groups, Emulations.– Check SSIDs … conflicts with current subsystems?– Issues … Yes → Perform Change Configuration!– Issues … No → Re-Install Covers and Panels.

Perform a Refer Configuration. Compare the delivered configuration to the configuration expected by the customer.

If the delivered configuration differs from that expected by the customer, determine whether the correct configuration can be deployed using Change Configuration. The other option is to plan and carry out a New Installation at the customer site.

Prestaging and Site Install Customer Specific Configuration


Customer Specific Configuration

13

Overview

Checks/sets Time of Day (TOD) Provides the above functionality for all Hitachi Data System-serviced Hitachi products as well as a number of third-party products such as switch and NAS products from Brocade, Cisco, and Netapp

TOD setting is important for Hi-Track Monitor reporting later Checks/sets Battery Expiration

Turning on the battery expiration alert is important for battery rotation (periodic maintenance)

Makes valid Configuration Backup

Prestaging and Site Install Install License Keys


Install License Keys

14

• Overview– Check subsystem capacity.– Locate ASCII *.PLK file.– Copy *.PLK to DKC200\MP\PC. – Select products to license.– WebConsole requires “Webconsole, SNMP and RMI”.

Important: You should receive a product license key (PLK) CD or floppy with the subsystem. If not, you can request license keys through email.

The license keys must be installed before the customer can begin to use and administer the storage system.

Prestaging and Site Install Set Customer LAN IP Address


Set Customer LAN IP Address

15

Overview

Set IP Addressing for customer LAN (provided by customer) Static IP, DNS, WINS, and Gateway; all possibly needed Customer responsible for security issues (firewalls and others)

Important: It is the customer responsibility to provide the customer engineer with LAN address information. Additionally, they are responsible for restricting access to the SVPs through their public LAN to authorized persons. It is also important to set the customer or external LAN address using the SVP configuration dialog, too.

If Remote Maintenance is enabled at the customer site, Hitachi support will use the same account(s) for SVP access.

When using Remote Desktop, the most recent connection request is honored. If a user is currently logged on to the SVP and another user makes a connection request via Remote Desktop, the current user’s request will be “bumped” off and the most recent request will be honored. If multiple people are involved in a support or analysis task, they must coordinate among each other to avoid unexpected SVP session termination.

Prestaging and Site Install Install and Test Hi-Track Monitor


Install and Test Hi-Track Monitor

16

If the customer wants the storage system configured for Hi-Track reporting, the Hi-Track software must be installed. After Hi-Track is installed, it must be configured and tested.

Prestaging and Site Install Prestaging and Site Install Summary


Prestaging and Site Install Summary

17

• New Installation Done at Build-Center – Under proper circumstances a new installation is required– Lengthy procedure (50 Steps)– Loads SVP, microcode, and writes FMs of all MPs– Change Configuration is How You

• Add/remove shared memory or cache• Add/remove channels• Add/remove array groups, or ACP pairs• Make certain other configuration changes

– Maintenance is How You • Replace a failed part with a new part of the same exact type

• Site Install– Position the storage system, connect the A/C power– Confirm no SIMs or maintenance issues– Install, configure, test Hi-Track Monitor

Every new Universal Storage Platform V and Universal Storage Platform VM goes through the new installation process at the regional Distribution Center.

This turns the assembled components into a storage system that can be “burned in” and verified that all the components are functioning.

After the New Installation and testing, the storage system is packaged and transported to the customer site where the steps of the Site Install are performed.

If any failed parts are detected after site installation at the customer site, perform the appropriate Maintenance process to replace the failed parts.

If the customer’s configuration requirement is different from the configuration installed at the Distribution Center, it must be determined whether it is better to deploy the configuration changes with the Change Configuration or New Installation procedures.

After the storage system is positioned, connected to A/C power and powered-up, Hi-Track Monitor is installed, configured and tested.

Prestaging and Site Install Site Install Summary


Site Install Summary

18

• Site Install Tasks – Unwrapping and positioning– Initial power up and maintenance checks– Configuration check and change configuration– Minor configuration tasks– Hi-Track Monitor install, configuration, and test– If the machine is newly delivered please let it acclimate to the customers

environment before powering it up• Site Install Checklist

– Microcode media and configuration backup media (USB memory drive)– Floor position determined– Floor tiles prepared– Power lines installed– Phone line available– LAN connection available

Be prepared before going on-site. Contact the customer and let them know what is required of them, and what you will be doing. Get appropriate information from the account team. Support will help you by phone in the field, if necessary.

Prestaging and Site Install Summary


Summary

19

• Defined the process known as Prestaging• Identified the tasks performed as part of the Prestaging process• Identified how Prestaging ensures delivery of a fully functioning storage

system that meets the customer’s expectations• Defined the tasks that are performed during the Site Install of a storage

system at the customer’s location• Identified additional minor configuration tasks that are performed in

preparation for the customer’s use of the storage system

01_056601

Documents

Transcript of 01_056601