Documente Academic
Documente Profesional
Documente Cultură
THC2887
© Hitachi Data Systems Corporation 2016. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. Hitachi Content Platform Anywhere, Hitachi Live
Insight Solutions, ShadowImage, TrueCopy, Universal Storage Platform, Essential NAS Platform, Hi-Track, and Archivas are trademarks or registered trademarks of Hitachi Data
Systems Corporation. Pentaho is a trademark or registered trademark of Hitachi Data Systems Corporation and Pentaho. IBM, S/390, XRC, z/OS, VTF, ProtecTIER,
HyperFACTOR, and Flashcopy are trademarks or registered trademarks of International Business Machines Corporation. Microsoft, SQL Server, Hyper-V, PowerShell,
SharePoint, and Windows are trademarks or registered trademarks of Microsoft Corporation. All other trademarks, service marks, and company names are properties of their
respective owners.
ii
Table of Contents
1. Overview........................................................................................................... 1-1
Workshop Objectives ............................................................................................................................. 1-1
Acronyms ............................................................................................................................................. 1-2
Prerequisites ......................................................................................................................................... 1-3
Hands-On Labs Objectives ..................................................................................................................... 1-4
3. VSP Gx00 and VSP Fx00 HNAS Platform Documentation ................................. 3-1
HM800/VSP Gx00/VSP Fx00 Documentation ............................................................................................ 3-2
One Person’s Approach to Navigating the HM800 Maintenance Manual....................................................... 3-3
HM800 to RAID800 Documentation Comparison ....................................................................................... 3-4
Getting the NAS Platform Documentation ................................................................................................ 3-5
HM800 to HNAS Documentation Comparison ........................................................................................... 3-6
iii
Table of Contents
iv
Table of Contents
8. Troubleshooting................................................................................................ 8-1
Always Check for Pinned Data ................................................................................................................ 8-1
Multiple Concurrent Failures Requires Careful Planning ............................................................................. 8-2
Replacing a Memory DIMM ..................................................................................................................... 8-3
Block Environment SIM Messages and RC Codes ...................................................................................... 8-4
Collect Dump Using the SVP ................................................................................................................... 8-5
Troubleshooting for the Maintenance Utility ............................................................................................. 8-5
Management Interface Connectivity Problems – Rebooting the GUM From the BEM ..................................... 8-6
Rebooting the GUM From the Maintenance Utility ..................................................................................... 8-7
Forceful Hardware Reset of the GUM....................................................................................................... 8-8
v
Table of Contents
vi
1. Overview
Welcome to the prerequisites training for VSP Gx00 and VSP Fx00 With NAS Modules Hands-On
Workshop for CS&S and Field Support Professionals.
This training is the basis for your participation in the on-site, hands-on workshops where you
will get the opportunity to directly interact with and perform maintenance tasks on a Hitachi
Virtual Storage Platform (VSP) Gx00 or VSP Fx00 system.
Workshop Objectives
This presentation also covers the knowledge and skills that workshop
participants are expected to learn
*At the time this material was created, HDS intended to offer VSP Fx00 with NAS Modules in the future.
As of October, 2016, this line of storage models was not yet officially available.
This prerequisites guide will prepare you for the Hands-On Workshop for CS&S (Field Support
staff) for VSP Gx00 and VSP Fx00 With NAS Modules.
Page 1-1
Overview
Acronyms
When you are comfortable with the information in this prerequisites guide, you will be ready to
start immediately after you arrive for the workshop sessions. You will get the most out of the
limited hands-on time in the lab.
The majority of information in this pre-requisites guide is referenced to other related or pre-
requisite training courses. The training course or courses in which information is found will be
identified, if applicable. References to locations in the documentation, particularly the storage
system maintenance manual, are also included.
Acronyms
Here are some of the acronyms used in this module. Please familiarize yourself with them
before continuing.
Page 1-2
Overview
Prerequisites
Prerequisites
This guide covers how to:
• Access and use VSP Gx00 and VSP Fx00 Device Manager Storage Navigator GUI (Block Element
Manager or BEM)
• Connect and use the VSP Gx00 and VSP Fx00 Maintenance PC
• Access and use the MPC (formerly the SVP Application) GUI
• Obtain and use the VSP Gx00 and VSP Fx00 Maintenance Manual
• Obtain and use the Hitachi NAS Platform (HNAS) Platform Documentation
• Obtain and use the VSP Gx00 and VSP Fx00 Microcode Exchange Wizard Tool (83-MCTool)
You should also have 20-50GB of free space on the C:\ drive of your laptop
• This is required in order to install the Maintenance PC software on your laptop
These hands-on workshop sessions are brief and have a very specific objective of providing a
“learning by doing” experience.
During the workshops, very little time will be spent on lectures or PowerPoint presentations.
This prerequisite web-based training is provided so that classroom lectures can be eliminated or
minimized during the workshops. This prerequisite training covers information that you can get
from other Hitachi Data Systems Academy courses including:
• THI2651 – Installing and Supporting Hitachi Virtual Storage Platform Midrange Family (3
day ILT)
• THC2794 – Hitachi Virtual Storage Platform Gx00 With NAS Modules Differences (3 day
ILT)
This prerequisites guide covers how to:
• Use the Device Manager Storage Navigator user interface. This is now frequently called
the Block Element Manager or BEM
• Connect the maintenance laptop to the VSP Gx00 and VSP Fx00 system for maintenance
activities
• Use the Maintenance PC GUI
• Use the Maintenance Manual documentation
• Use the VSP Gx00 and VSP Fx00 Microcode exchange wizard tool (83-MCTool)
Be aware that, if you want to install the Maintenance PC software on your laptop, you need 20
to 50 gigabytes of free disk space.
Page 1-3
Overview
Hands-On Labs Objectives
Upgrade the firmware of a VSP Gx00, VSP Fx00, VSP Gx00 with NAS modules,
or VSP Fx00 with NAS modules
Develop an understanding of the VSP Gx00, VSP Fx00, VSP Gx00 with NAS modules,
and VSP Fx00 with NAS modules architecture in a way that will be useful to Field Support
personnel
When you attend the hands-on workshop, you will connect and use the Maintenance PC. You
will perform a VSP Gx00/VSP Fx00 to VSP Gx00/VSP Fx00 with NAS modules upgrade. Based
on that experience, you should be able to understand and perform a VSP Fx00 to VSP Fx00
with NAS modules upgrade, too. You will access and navigate using the NAS Manager GUI.
This is also referred to and is comparable to the SMU of the NAS gateway configuration. You
will perform a unified firmware upgrade, including both the block system and NAS OS upgrade.
Finally, you will learn about the VSP Gx00, VSP Fx00, and VSP Fx00 with NAS module
architecture and operation in a way that should be helpful when you are called on to perform
maintenance on such a system.
Page 1-4
2. Terminology and Cross-Reference
In the next few slides, we will review some terminology related to the VSP Gx00 and VSP Fx00
storage systems.
This table shows the different models in the VSP Gx00, VSP Fx00, VSP Gx00 with NAS modules,
and VSP Fx00 with NAS modules families.
Notice that the VSP G200 does not support the option with NAS modules. VSP G200 is available
for block-only storage support.
A customer could configure a VSP G200 behind Hitachi NAS (HNAS) Platform. The VSP G200
does not support unified storage configuration.
Page 2-1
Terminology and Cross-Reference
Translation and Cross-Reference of Storage System Names
This table also shows a terminology translation that you may encounter when using the product
technical documentation, particularly the maintenance manual.
The engineering organization refers to the family of storage systems as “HM800.” Extra letters
at the end of HM800 are used to differentiate the controller options – small, medium or large –
that correspond to VSP Gx00, VSP F400, VSP F600, or VSP F800.
Other important information is that only the “large” models—the VSP G800 and VSP F800—
support the additional channel host expansion chassis (CHBB) component. The CHBB can be
added to the CBLH controller to increase the number of available front-end channel host ports.
Notice that VSP G400, VSP G600, VSP F400 and VSP F600 do not support the addition of the
CHBB.
Page 2-2
Terminology and Cross-Reference
Hitachi Midrange Storage System Configuration References
The approved references or names for the new “unified” storage systems are “VSP Gx00 With
NAS Modules” and “VSP Fx00 With NAS Modules.”
It is never correct to use the descriptor “Unified storage” with a capital “U.”
In these training materials, we will mostly use the correct “VSP Gx00 with NAS modules” or
“VSP Fx00 with NAS modules.” Sometimes we may use the shortened, more informal “VSP
Gx00 and VSP Fx00 unified,” with lower case “u.”
When we want to indicate a VSP Gx00 or VSP Fx00 that is not configured with NAS modules,
we will include the descriptor “block-only.”
If you see the specific phrase, “Hitachi Unified Storage (HUS),” know that it refers to the older
modular, mid-range storage family that includes the HUS 110, 130 and 150. It is not correct to
use the phrase “Hitachi Unified Storage” when referring to VSP Gx00 or VSP Fx00 with NAS
modules. The VSP Gx00 and VSP Fx00 series are sometimes called “midrange” storage. The
VSP Fx00 series of storage systems is part of the Hitachi all flash array offerings.
Page 2-3
Terminology and Cross-Reference
MPC Definition
MPC Definition
10.0.0.99
“MPC” is sometimes used as the acronym for “Maintenance PC.” However, there is also a
special user interface that is labeled “MPC.” In these training materials, we will always refer to
the Maintenance PC as such, and will not use the acronym to refer to it. We will refer to the
MPC GUI as the MPC GUI to eliminate any confusion over the use of the MPC acronym.
Another note: In the Japanese market, the HM800 storage systems do not include a Service
Processor (or SVP). Thus the HM800 Maintenance Manual specifies that the IP address of the
Maintenance PC should be set to 10.0.0.15 and it is shown as a strikethrough with a red line.
In the rest of world (ROW) markets – countries outside Japan – the VSP Gx00 and VSP Fx00
systems can be ordered with the SVP. When the SVP is provided with the system from the
Hitachi Distribution Center, the SVP maintenance network IP address is set to 10.0.0.15.
Therefore that IP address cannot also be used for the Maintenance PC.
A different IP address must be used for the Maintenance PC. The recommended address is
10.0.0.99, as shown.
Page 2-4
3. VSP Gx00 and VSP Fx00 HNAS Platform
Documentation
In this section, we will identify the various sets of documentation that are used when working
with VSP GX00 and VSP FX00 storage systems.
Page 3-1
VSP Gx00 and VSP Fx00 HNAS Platform Documentation
HM800/VSP Gx00/VSP Fx00 Documentation
There are two main documentation libraries for the VSP Gx00 and VSP Fx00 series and for VSP
Gx00 and VSP Fx00 with NAS modules.
These include the Maintenance Documentation Library (MDL) and the Product Documentation
Library (PDL).
For the unified configurations, you will also need the Hitachi NAS documentation.
The libraries and documents are available from TISC and Hitachi Data Systems Support Connect.
These workshops focus on the information contained in the MDL but occasionally also need to
reference the PDL and the NAS documentation.
Because the unified NAS Platform functionality is delivered by the same HNAS code that is used
in the HNAS gateway offerings, you will also need to become familiar with the content and
organization of the HNAS documentation.
Page 3-2
VSP Gx00 and VSP Fx00 HNAS Platform Documentation
One Person’s Approach to Navigating the HM800 Maintenance Manual
• Download the .iso file. For the HM800 Maintenance Manual, this is file HM056-nn.iso.
• This folder will then contain an index.html file. Use this index.html file to launch the
HM800 Maintenance Manual. This process opens a page with the list of all the separate
sections. You can then navigate and launch the section of the Maintenance Manual you
need.
In the example shown on this slide, the Firefox browser was used. A new browser tab is opened
for each new document selected. You can keep multiple documents open in the same browser
session. Document links within pdf sections of the Maintenance Manual work only in that
document. If a link takes you to another pdf, you will have to be sure that the other pdf is open
in another tab and you will need to manually navigate between the different sections.
If you get confused or lost, you can close all browser tabs and return to the main index.html
page and start again.
The more familiar you become with the HM800 Maintenance Manual and where the information
is in the different sections, the easier it will be for you to use this important reference when you
need it for field tasks.
Page 3-3
VSP Gx00 and VSP Fx00 HNAS Platform Documentation
HM800 to RAID800 Documentation Comparison
Here are the index.html pages from DW800 (VSP Gx00 and VSP Fx00) on the left and RAID800
(VSP G1500 and VSP F1500) on the right. You can see they are very similar, but there are some
differences.
If you are a field support professional who is already familiar with VSP G1500, VSP F1500 and
how to use the RAID800 Maintenance Manual, comparing the documentation differences to the
newer VSP Gx00 and VSP Fx00 Maintenance Manual may help your learning.
• Compare the contents of the DW800 HDS SVP section to the DCK810I SVP Section
• Notice that the DKC810I Maintenance Manual does not contain a Maintenance PC
section
Here is a challenge. Locate the procedure for recording a block environment configuration
backup in these two different types of storage systems. In which section of the maintenance
manual is this procedure found for the two different systems?
Page 3-4
VSP Gx00 and VSP Fx00 HNAS Platform Documentation
Getting the NAS Platform Documentation
Many colleagues still rely on TISC, rather than Hitachi Data Systems Support Connect, to locate
and download the documentation.
To locate the relevant NAS Platform documentation that applies to the VSP Gx00 and VSP Fx00
with NAS modules unified NAS implementation, select HNAS 4000 series as the Hitachi Data
Systems Product Family in the TISC selection screen.
Page 3-5
VSP Gx00 and VSP Fx00 HNAS Platform Documentation
HM800 to HNAS Documentation Comparison
Offers the
consolidated “libraries”
in .iso format
NAS Platform
The NAS functionality of the VSP Gx00 and VSP Fx00 unified storage systems is delivered by the
same NAS OS code that runs on the HNAS gateway implementations. Therefore, HNAS
documents that describe software features, functionality, GUIs and interfaces, and user
interaction apply both to the Hitachi NAS gateway offerings and also to the VSP Gx00 and VSP
Fx00 unified systems.
If you are an experienced Hitachi block storage professional, you will need to think outside the
traditional set of VSP Gx00 and VSP Fx00 documents. Some essential information is in NAS
documentation.
If you are an experienced NAS professional, you will need to learn to use the VSP Gx00 and VSP
Fx00 documentation.
People who are familiar with either the HM800 or HNAS can benefit from some information
about the differences in approach to documentation.
Because the block storage documentation was developed by the GISD (formerly ITPD) group in
Japan and the NAS Platform documentation originated with the underlying BlueArc NAS
products, they are organized quite differently.
Now that you will be dealing with “unified” systems, it will be very helpful for you to become
familiar with both the block storage and the NAS Platform documentation.
While the relevant documentation and instructions for field support personnel about storage
systems is found in “FE-” Hitachi Data Systems internal documents, there are very few “FE-”
documents for the NAS Platforms.
Page 3-6
4. User Interfaces Used by Field Support
In this section, we will identify and review the purpose and function of the various user
interfaces for VSP Gx00 and VSP Fx00 systems.
Page 4-1
User Interfaces Used by Field Support
User Interfaces and Their Uses
Rack- Initial Initial Setup H/W addition, Provisioning, Failure Parts Upgrading Down-
mounting, Startup S/W installation setting replacement grading
Cabling, and setup changes, etc. Hardware Software
etc.
2 Unified CE & Partner BECK IST MU, SMU MU, SMU N/A MU MU SDL MU
End-User N/A N/A N/A N/A HCS, HSA MU N/A SDL N/A
4 Unified CE & Partner BECK IST MU, SMU MU, SMU N/A MU MU SDL MU
End-User N/A N/A N/A N/A HCS, HSA MU (*) N/A SDL (*) N/A
6 Unified CE & Partner BECK IST MU, SMU MU, SMU N/A MU MU SDL MU
End-User N/A N/A N/A N/A HCS, HSA MU N/A SDL N/A
This table was created for the block-only configurations, so the NAS Platform interfaces are not
included. It shows various user interfaces and their intended uses.
• IST: Initial Startup Tool. This is installed in the VSP Gx00 and VSP Fx00 SVP
• MU: Maintenance Utility. This can be found in the Gateway for Unified Management
(or GUM) GUI
• HSA: Hitachi Storage Advisor. This product name replaced Hitachi Infrastructure Director
(or HID)
Page 4-2
User Interfaces Used by Field Support
Maintenance Interfaces and Network Connections
Maintenance PC
MPC software
SVP
GUM
Internal LAN
Management LAN
Maintenance Port
This diagram is found in the HM800 Maintenance Manual Firmware section on page FIRM01-20.
It shows which user interfaces are available, on which platform they run, how they are
interconnected and how you access them.
The MPC GUI runs on the Maintenance PC platform. When it is used, the Maintenance PC must
be connected to the maintenance port on one of the storage system controllers. Normally, the
Maintenance PC is connected to the maintenance port on Controller 1. The Controller 1
maintenance port IP address is 10.0.0.16. Set the IP address of the Maintenance PC to
10.0.0.99 with subnet mask 255.255.255.0.
This diagram shows the SVP. In the documented maintenance procedures, the Maintenance PC
is normally shown as the way to access the Maintenance Utility. However, it is also possible to
access the Maintenance Utility through the SVP.
Page 4-3
User Interfaces Used by Field Support
The Maintenance PC and the MPC GUI
In the VSP Gx00 and VSP Fx00 architecture, the ability to access certain sensitive maintenance
operations has been removed from the Service Processor. Many maintenance tasks, including
replacement of failed hardware components are now managed through the Maintenance Utility
which runs on the controller.
The Maintenance PC is always connected to the maintenance port on one of the storage system
controllers. You can revisit the previous slide which shows the network and connection points
for the different system components, including the Maintenance PC.
Because this training covers all three of these CS&S tasks, you must understand the
Maintenance PC and how to access the MPC GUI that runs there.
In the hands-on workshop, the lab environment includes a configured and working Maintenance
PC.
However, we have heard reports from CS&S early adopters that installing and configuring the
MPC software on the CE laptop consistently has been a problem.
One challenge is that the CE laptop must have sufficient hard disk free space. The specifications
indicate 50 gigabytes of free space. However, one colleague did successfully install the
Maintenance PC software with a little more than 20 gigabytes of free space.
Page 4-4
User Interfaces Used by Field Support
The Storage Device List on the Maintenance PC
The Maintenance PC software also installs a range of utility software including Java, Flash,
PuTTY, and others. We have all faced the “Java” challenges when configuring our laptops and
servers.
Information about the Maintenance PC is found in the HM800 Maintenance Manual Maintenance
PC Section.
Before you can use the Maintenance PC to communicate with the storage system, you must
register the storage system to the Maintenance PC Storage Device List.
In order to register a VSP Gx00 or VSP Fx00 to the Storage Device list on the Maintenance PC,
the Maintenance PC MUST be connected to the storage system’s controller 1 maintenance port.
If you look closely at the Storage Device List image shown here, you will see that the MPC
address is shown as 10.0.0.15.
The Storage Device List on the Maintenance PC can be used differently from the Storage Device
List on the SVP. The SVP is tightly integrated into the specific VSP Gx00 and VSP Fx00 storage
arrays. Therefore the Storage Device List on the SVP can communicate only with that one
specific array. Attempts to register any other storage array to the Storage Device List on an SVP
will fail.
Page 4-5
User Interfaces Used by Field Support
Web Console on the Maintenance PC
The Web Console requires starting a set of services on the Maintenance PC. You can start, stop
and monitor the status of these services from the Storage Device List. This information is found
in the MPC section of the Maintenance Manual.
Page 4-6
User Interfaces Used by Field Support
On the Maintenance PC, the Storage Device List Opens the MPC Software Screen
On the Maintenance PC, the Storage Device List Opens the MPC
Software Screen
The Storage Device List on the Maintenance PC operates differently than the Storage Device
List on the SVP. When you click the storage system icon in the Storage Device List on the
Maintenance PC, the MPC Software window is displayed.
Depending on how you interact with this window, you can navigate either to the Web Console
or to the MPC GUI.
To access either interface from the MPC software, you must enter the User Name and Password
credentials at the top of the screen.
After you enter the user name and password, the “Go to MPC” button becomes active.
If you want to access the MPC GUI, you must click the “Go to MPC” button quickly before the
Web Console opens.
Page 4-7
User Interfaces Used by Field Support
Web Console – Version of BEM That Runs on the Maintenance PC
The term “Web Console” should be used for a very specific meaning. The Web Console is the
version of the Block Element Manager that runs on or from the Maintenance PC.
This can be confusing. The Web Console looks and behaves exactly like the Hitachi Device
Manager Storage Navigator interface that runs on the SVP. But notice that in the very top bar of
the GUI, you see the words “Web Console.”
In the VSP G1500 and VSP F1500 enterprise storage system architecture, there are two
separate running versions of the Block Element Manager. In the VSP G1500 and VSP F1500
enterprise storage architecture these both run on the SVP.
The Web Console is displayed when the user connects to the SVP with remote desktop protocol
(RDP). In the newest VSP midrange systems, you can display the Device Manager Storage
Navigator GUI when using a browser to connect to the SVP IP address. However only a few
administrative functions are active. This configuration has been implemented to enforce the
use of other storage management software such as Hitachi Command Suite or Hitachi Storage
Advisor.
In the enterprise system architecture, there are operations you can perform with Storage
Navigator that are not supported from the Web Console.
However, again, be careful in your terminology and do not use “Web Console” and “Storage
Navigator” as synonyms because they are two different GUIs in VSP Gx00 and VSP Fx00
architecture, even though they look and behave the same.
Page 4-8
User Interfaces Used by Field Support
Multiple Paths to Access the Maintenance Utility GUI
The Maintenance Utility GUI runs on the controller. Each of the two controllers runs an instance
of the Maintenance Utility GUI. The system architecture takes care of the communication to the
other controller when operations are performed through the Maintenance Utility GUI.
This diagram shows the two access paths to the Maintenance Utility GUI from the Maintenance
PC.
On the Maintenance PC, you can first access the MPC GUI and then access the Maintenance
Utility GUI from there.
Or you can access the Block Element Manager or Web Console (Storage Navigator instance)
that runs on the Maintenance PC and then access the Maintenance Utility GUI from there.
Although it is not shown in this diagram, the third option is to access the Block Element
Manager or Storage Navigator on the SVP and then access the Maintenance Utility GUI from
there.
Page 4-9
User Interfaces Used by Field Support
Accessing the Maintenance Utility From the Web Console or Storage Navigator
You can access the Maintenance Utility GUI from the Web Console (which runs on the
Maintenance PC) or from the Block Element Manager or Storage Navigator which runs on the
SVP. This slide shows screen images of the navigation path to open the Maintenance Utility GUI
from Storage Navigator.
Instructions for using the Maintenance Utility GUI tell you to connect the Maintenance PC to the
maintenance port on Controller 1.
You use the Maintenance Utility GUI to perform many CS&S tasks including the maintenance
replacement of failed hardware components.
The Web Console runs on the Maintenance PC which is connected to the Controller 1
maintenance port. Therefore the access to the Maintenance Utility GUI is across the
maintenance LAN.
Page 4-10
User Interfaces Used by Field Support
Accessing the Maintenance Utility GUI From the MPC GUI
You can also access the Maintenance Utility GUI from the MPC GUI.
This slide shows the navigation path to open the Maintenance Utility from the MPC GUI.
Because the MPC GUI runs on the Maintenance PC and the Maintenance PC is connected to the
Controller 1 maintenance port, this communication path is across the maintenance LAN.
Page 4-11
User Interfaces Used by Field Support
The “GUM” GUI – Block-Only Configuration
Management IP
address of
Controller1
If the VSP Gx00 or VSP Fx00 is configured for block only and NAS nodules have not been
installed, when the administrator connects to the controller web service with a browser, as
shown here, the login screen for the Maintenance Utility is displayed.
Because no NAS platform or services are running, there is no option available for accessing any
NAS features.
The Gateway for Unified Management (GUM) GUI for VSP Gx00 and VSP Fx00 with NAS
modules is shown on the next slide so you can see the difference when NAS modules are
installed.
Page 4-12
User Interfaces Used by Field Support
When To Use Which User Interface
A very important and informative table is found in the HM800 Maintenance Manual Maintenance
PC section starting on page MPC01-221.
This table tells you which interface to use to perform different tasks and operations in the VSP
Gx00 and VSP Fx00 systems.
Page 4-13
User Interfaces Used by Field Support
MPC GUI (Formerly the SVP Application)
There are just a few CS&S tasks that can be performed only from the MPC GUI on the
Maintenance PC. You will find these when the MPC GUI is in Modify Mode or in Mode Mode.
With the MPC GUI in Modify Mode, you can record a block environment configuration backup.
With the MPC GUI in Mode Mode, you can set System Option Modes (SOMs).
Notice that the Install button becomes active when the MPC GUI is set into either Modify Mode
or Mode Mode. You can also access the Maintenance Utility GUI from the MCP GUI, even when
the MPC GUI is in View Mode.
Page 4-14
User Interfaces Used by Field Support
Why Have an SVP in the Non-Japan Markets?
Ability to register multiple storage Ability to register only one array, the
systems to one Maintenance PC one to which the SVP is connected
The Hitachi Data Systems management software offerings are not used in the Japanese market.
Hitachi Command Suite and Hitachi Storage Advisor are offered and encouraged only outside of
Japan. Therefore, the system architecture does not need a management software interface
point in the Japanese market.
In order to enable the integration and use of the Hitachi Data Systems management software
offerings, the HM800 architecture was modified to provide an integration point for the
communication between one or more storage systems and the management software
environments which can support many different types of storage arrays, including Hitachi
Content Platform (HCP) and HNAS systems.
This modification potentially causes confusion for access and navigation in the rest of world
(ROW) implementations. The SVP is basically a Maintenance PC with some functionality omitted.
However, both the Maintenance PC and the SVP run instances of the Block Element Manager
(Device Manager Storage Navigator).
Page 4-15
User Interfaces Used by Field Support
The Service Processor (SVP)
VSP Gx00 and VSP Fx00 Hardware Installation and Reference Guides
VSP G200 Installation and Reference Guide (FE-94HM8020-nn)
The VSP Gx00 and VSP Fx00 SVP is a component that is not part of the standard system
architecture in the Japanese market. It was added for the rest of world (ROW) distribution.
Therefore, the SVP is not documented in the traditional sections of the HM800 Maintenance
Manual.
In the VSP Gx00 and VSP Fx00 architecture, the SVP provides certain functions.
It is the interface between Hitachi Command Suite (HCS) or Hitachi Storage Advisor (HSA) and
the storage system. The user management software communicates with the Block Element
Manager (BEM) that runs on the SVP and the BEM, in turn, communicates with the storage
system controllers across the management network.
Notice that the GUM runs on the controller and communicates across the internal LAN. This is
an important feature of the VSP Gx00 and VSP Fx00 With NAS Modules architecture.
The Block Element Manager is labeled Hitachi Device Manager - Storage Navigator. The user
interfaces never carry the label Block Element Manager or BEM.
If you would like more information about the Service Processor (SVP), please refer to the
documents listed here.
Page 4-16
User Interfaces Used by Field Support
Service Processor Rear View
Note: Local Area Connection numbers are assigned randomly for each SVP unit, so there is no
relation between physical port assignment (LAN1/2/3/4) and Local Area Connection numbering
A Hitachi-provided SVP runs Windows 7 Embedded operating system. The primary function of
the Service Processor is to be the interface point between the customer management software,
Hitachi Command Suite or Hitachi Storage Advisor, and the storage system.
Because the SVP must be connected to both VSP Gx00 and VSP Fx00 controllers, a network
bridge is configured to join three of the four NICs on the SVP for the management network
connections.
Check the bridge relation by connecting a LAN cable to each port one-by-one before configuring
the bridge.
Another option is for the customer to provide their own SVP laptop or server.
Page 4-17
User Interfaces Used by Field Support
Service Processor LAN Configuration
Here is the SVP Windows OS configuration view of the network interfaces configuration.
Page 4-18
User Interfaces Used by Field Support
Storage Device List on the SVP
It can be a challenge to keep track of where you are and where you want to be or need to be
when deciding which interface to use for your VSP Gx00 or VSP Fx00 task.
Here you see an example of the Storage Device List running on the SVP. To get this interface,
you must RDP to the SVP.
This software is installed and configured as part of the VSP Gx00 or VSP Fx00 Configure to
Order process at the Distribution Center when the SVP is ordered with the system.
If you look closely in the upper right hand corner, you can see that it identifies the SVP IP
address. Just like the Storage Device List that runs on the Maintenance PC, the storage system
must be registered to the Storage Device List. An SVP manages only one storage system. The
storage system should be registered to the Storage Device List on the SVP as part of the
Configure to Order process.
In order to access the Block Element Manager running on the SVP, the services must be
running and the system’s status must show “Ready” in its Storage Device List entry. You can
stop, start and monitor the status of the Block Element Manager services on the SVP from the
Storage Device List entry as shown here. If you ever need to replace or rebuild a VSP Gx00 or
VSP Fx00 SVP, you will have to install and configure the SVP software. Replacing or rebuilding
the SVP is outside the scope of this workshop. Instructions on how to recover and rebuild the
SVP are found in the HM800 Maintenance Manual SVP Technical Reference.
Page 4-19
User Interfaces Used by Field Support
Browser Access to the SVP – User Management Only
Warning Notice:
You can use the initial setting functions of the storage system such as account management
and program product management after you log on. Use Hitachi Command Suite for applying
the configuration setting of the storage system after the initial setting.
If you use a browser to go directly to the SVP management IP address, you will get what
appears to be the Storage Navigator GUI. However, you will quickly find that the only
operations you can perform are in the User Management area.
You must remember to RDP to the SVP and then use the Device List entry to access the fully
functional Storage Navigator interface.
If you have experience with Hitachi RAID storage systems and are accustomed to browsing to
the SVP IP address to access Storage Navigator, you need to understand the Block Element
Manager (BEM) architecture differences in the VSP Gx00 and VSP Fx00 platforms. On a VSP
Gx00 or VSP Fx00, when you use a browser to access the SVP web server, a Device Manager
Storage Navigator (BEM) login screen is displayed. You may think that you will gain access to
the Storage Navigator GUI. However, in the VSP Gx00 and VSP Fx00 architecture, the Storage
Navigator version has very limited functionality. You can only run initial setting and user
account management operations from this interface.
Page 4-20
User Interfaces Used by Field Support
VSP Gx00 and VSP Fx00 Networks Diagram
This diagram is found in the HM800 Maintenance Manual SVP Technical Reference section. It
shows more detail about the network connections and software components of the Service
Processor (SVP).
If a VSP Gx00 or VSP Fx00 system is configured as block only, when you access the controller
IP address with a supported browser, the Maintenance Utility GUI login page is displayed.
Page 4-21
User Interfaces Used by Field Support
Storage Management GUIs for the Customer
Hitachi Data Systems strongly encourages customers to move in the direction of our
management software offerings, such as Hitachi Command Suite (HCS) which includes Hitachi
Device Manager (HDvM) or Hitachi Storage Advisor (HSA).
The Block Element Manager - Storage Navigator interface is hidden and is difficult to access
directly.
Hitachi Storage Advisor was previously named “Hitachi Infrastructure Director” or HID. You may
find some references to HID in these training materials because the diagrams have not been
updated to reflect the new name.
As mentioned in the description of the purpose and function of the Service Processor or SVP, all
storage provisioning, management and administration should be performed either through
Command Suite or Storage Advisor.
Part of the integration of a VSP Gx00 or VSP Fx00 system into a customer environment includes
installing and configuring the management software to recognize and register the new storage
array. The SVP management IP address is specified to the management software. The
management software queries the storage array, retrieves its components and configuration
and registers the storage array fully into the management software database.
Because these workshops are focused on the storage system setup tasks that would be
performed before an array was registered to the management software, we only mention that
these management tools are meant to be part of each customer environment where VSP Gx00
or VSP Fx00 systems are installed.
Page 4-22
User Interfaces Used by Field Support
Register the Hitachi VSP Gx00 or VSP Fx00 Module to HCS
The added value of these management tools is that they can manage multiple and complex
storage environments and they implement “wizard” or best practice configuration options.
If you want to learn more about storage provisioning and storage administration, please attend
the available training courses.
This slide shows an overview of the steps to register the VSP Gx00 or VSP Fx00 storage
systems (block) to Hitachi Command Suite v8.4.1.
If the VSP Gx00 or VSP Fx00 is configured with NAS modules, you only need to register the
system to Command Suite one time. There is no need to separately register the NAS
environment. Command Suite will detect the unified NAS Platform.
In a lab test, Command Suite automatically detected the NAS Platform as part of the registered
VSP Gx00 and VSP Fx00 systems. However, Command Suite displayed a message that some
configuration is required in the NAS Manager itself. In the NAS Manager you tell the NAS
Modules to which HCS system to report its configuration and other information.
Page 4-23
User Interfaces Used by Field Support
Hitachi Storage Advisor (HSA)
Here is an example of the Hitachi Storage Advisor GUI. You can see its graphic, high-level,
easy-to-use, simplified approach to storage administration. The GUI is job-role driven, wizard-
architected and integrates best practice storage provisioning and SAN management. If you want
to learn more about Hitachi Storage Advisor, look into related training courses available from
the Hitachi Data Systems Academy.
Page 4-24
5. Initial System Assessment
Let’s take a look at how to perform an initial system assessment of a newly installed VSP Gx00
or VSP Fx00 system.
Use the
Maintenance
Utility to confirm
the installed
hardware
There are several ways you can identify or confirm the installed hardware components of VSP
Gx00 or VSP Fx00 systems.
• First, you can use the Block Element Manager (BEM) running on the SVP.
Page 5-1
Initial System Assessment
Checking Installed Software and Firmware
Here is a screen example of the Maintenance Utility. Within the Hardware section in the left
menu tree, you can navigate to the Controller Chassis and any installed Drive Box. On those
screens, you can review which specific hardware components are installed.
The Maintenance Utility is used to identify and replace failed hardware components. You will get
the opportunity to practice maintenance procedures when you attend the workshop.
Be sure to confirm the installed firmware components against the Engineering Change Notice
(ECN).
The Engineering Change Notice is available in TISC and is delivered also on the Documents and
Programs CD/DVD/.iso file that accompanies the microcode.
Page 5-2
6. Standard CS&S Tasks
Now we will identify and review the standard VSP Gx00 and VSP Fx00 maintenance tasks
expected of CS&S field support professionals.
Page 6-1
Standard CS&S Tasks
Storage Capacity Upgrade – Adding Disk Boxes
Performing a VSP Gx00 or VSP Fx00 storage capacity upgrade is a standard CS&S task. A
storage capacity upgrade involves adding more disks to an existing system. Adding disks may
also require adding more Disk Boxes (DBs).
This slide shows the screen Maintenance Utility screen navigation and identifies the steps to add
new Disk Boxes.
Adding disks to a VSP Gx00 or VSP Fx00 system may be required when configuring a VSP Gx00
or VSP Fx00 block-only system to a unified system, with NAS modules.
Page 6-2
Standard CS&S Tasks
Adding Components – Drives
Install drives
1. Select the newly added
drive box (in this case,
Drive Box – 00).
2. Select Drives.
3. Click Install.
Performing a VSP Gx00 or VSP Fx00 storage capacity upgrade is a standard CS&S task.
This slide shows the Maintenance Utility screen navigation for adding Drives.
Adding drives to a VSP Gx00 or VSP Fx00 may be required in the case of a VSP Gx00 or VSP
Fx00 block-only system to a unified, with NAS modules, configuration.
The bulleted text steps on this slide identify how to add additional disk drives to the disk boxes.
After the new drives are inserted, the system detects them and adds the new drives to the
available inventory. They are then available to configure into Parity Groups.
Page 6-3
Standard CS&S Tasks
Create New Parity Groups – Storage Navigator
A member of the Administrators user group can access the SVP and login directly to the Storage
Navigator (Block Element Manager or BEM) GUI. When there are disk drives available and not
yet assigned to any parity group, use this interface to create new parity groups.
Use the left side of the Create Parity Groups screen to configure one or more new parity groups
and add them to the Selected Parity Groups list on the right side of the screen. When the Auto
Drive Selection option is chosen, you can select the check box and click the Detail button to
view which disk drives have been selected for the new parity groups.
Page 6-4
Standard CS&S Tasks
Create LDEVs
Create LDEVs
Creating LDEVs is considered part of block storage provisioning. There are times when this may
be a CS&S task.
If you have to perform a block-only to NAS upgrade for VSP Gx00 and VSP Fx00 with NAS
modules, the documented procedure requires you to manually create one LDEV.
You can create LDEVs using Device Manager Storage Navigator GUI, as shown.
There are many parameter configurations for LDEVs. To learn more, consult the VSP Gx00 and
VSP Fx00 Provisioning Guide, MK-94HM8014-nn.
Page 6-5
Standard CS&S Tasks
Create a Cache Logical Partition (CLPR)
A separate Cache Logical Partition (CLPR) is required in the “with NAS modules” configuration.
This CLPR is dedicated to the I/O for the NAS System LUNs.
When an existing VSP Gx00 or VSP Fx00 system is converted to a unified configuration, a CLPR
for the NAS System disks must be manually created.
The NAS System LUs CLPR should be given the CLPR name “NASSystemCLPR.” The precise
CLPR name is important but the CLPR number does not matter.
The information about how to create a CLPR is found in the VSP Gx00 and VSP Fx00
Performance Guide, MK-94HM8012-nn.
If you want to know more about Cache Logical Partitions and when and why to use them, you
can find more information in the Performance Guide.
Page 6-6
Standard CS&S Tasks
Create a Resource Group (RSG or RG)
Resource Groups (RSG) are supported in the SVOS operating system. Resource Groups are used
to group and provide security to limit access to sets of storage resources.
In the VSP Gx00 and VSP Fx00 with NAS modules unified configuration, a Resource Group is
created to isolate and protect the NAS system resources. This RSG is created by the NAS OS
installation scripts . There are no manual steps you need to take even if you are performing a
NAS upgrade to a VSP Gx00 or VSP Fx00 block-only system.
When working with VSP Gx00 or VSP Fx00 with NAS modules systems, it is important to
understand what are Resource Groups, how they can be manually created and managed. This
is important so that you can review and verify the “with NAS modules” configuration.
Instructions on how to create a Resource Group are found in the VSP Gx00 and VSP Fx00
Provisioning Guide, MK-94HM8014-nn.
Page 6-7
Standard CS&S Tasks
Set Host Mode Options
Host Mode Option settings are an attribute of Host Groups within the front end channel ports in
Hitachi storage systems. Host Mode Options are set with the Edit Host Groups process.
Two new and specific Host Mode options are used when configuring a unified system. Host
Mode Options 7 and 58 are set for ports CL1-A and CL2-A in a VSP Gx00 or VSP Fx00 with NAS
modules. The process for setting Host Mode Options can be found in several places in the
documentation.
For the specific setting of the Host Mode Options required for the unified NAS Platform, refer to
the HM800 Maintenance Manual Installation Section on page INST07-01-140. This shows how
to set Host Mode Options using Storage Navigator, the Block Element Manager.
You can also refer to the VSP Gx00 and VSP Fx00 Provisioning Guide, MK-94HM8014-nn.
Page 6-8
Standard CS&S Tasks
Set a System Option Mode (SOM)
Setting System Option Modes (SOMs) can be done only through the MPC GUI. This GUI can be
run only from the Maintenance PC, so only Hitachi Data Systems or partner staff can set SOMs.
Traditionally setting SOMs has been a CS&S task.
If your experience is primarily with earlier NAS systems, you may not yet be familiar with
System Option Modes on the Hitachi storage arrays.
The ability to set SOMs is required when upgrading a VSP Gx00 or VSP Fx00 block-only to
unified configuration. System Option Mode 318 is specified to be set for VSP Gx00 or VSP Fx00
With NAS Modules.
Information on how to access the MPC Utility “gray box” maintenance interface (formerly known
as the SVP application) is in the HM800 Maintenance Manual Maintenance PC section. See
pages MPC05-800 through MPC05-840.
Page 6-9
Standard CS&S Tasks
System Option Modes
System Option Modes supported for each VSP Gx00 and VSP Fx00 model are documented in the
respective Hardware and Installation Reference Guides.
VSP Gx00 and VSP Fx00 Hardware Installation and Reference Guides:
Page 6-10
Standard CS&S Tasks
Setting CEMD (Virtual) Jumper
To set or enable the CE mode CEMD (virtual) jumper setting, access the Maintenance Utility
GUI and navigate to Menu > System Management > Edit System Parameters.
On the Edit System Parameters screen, there are 4 check boxes. These are the “virtual”
jumpers. [In other systems, physical jumpers are set on pins on one or more printed circuit
boards (PCBs)]. In the VSP Gx00 and VSP Fx00 architecture, jumper-enabled functions are
controlled by “virtual jumpers” or check boxes accessed through one of the management
interfaces.
The virtual jumpers can only be enabled and disabled through the Maintenance Utility GUI.
These virtual jumpers are not supported in any other GUI interface or in the CLI.
Page 6-11
Standard CS&S Tasks
Checking Installed Firmware Versions With the Maintenance Utility GUI
You can view the installed firmware component versions using the Maintenance Utility GUI. To
view the firmware versions, access the Maintenance Utility GUI. Navigate to Administration >
Firmware. A list of firmware components with the installed version is displayed.
Page 6-12
Standard CS&S Tasks
Collect Dump With the Dump Tool – .bat File on the SVP
Collect Dump With the Dump Tool – .bat File on the SVP
The correct way to collect diagnostic dumps on a VSP Gx00 or VSP Fx00 system is to run the
appropriate Dump Tool .bat file from a command prompt window on the SVP.
Instructions for collecting either a normal or a detailed dump using the Dump Tool .bat script is
found in the VSP Gx00 and VSP Fx00 Storage Administrator Guide, MK-94HM8016-nn.
In the command prompt session, set the current directory path on the SVP to:
C:\mapp\wk\<serial number>\DKC200\mp\pc
After you launch the .bat file, the system will do all the rest. Collecting a detailed dump takes
about 5 to 10 minutes.
Page 6-13
Standard CS&S Tasks
Do Not Collect Dump Through the GUI
Warning:
The Download System
Dump function of the
GUI collects
incomplete data
The HM800 Maintenance Manual Maintenance PC section on page MPC03-880 provides the
documentation for collecting a VSP Gx00 and VSP Fx00 system dump through the Maintenance
Utility GUI.
At the time this training material was created, this dump collection procedure did not collect all
the diagnostics needed by Hitachi Global Support Center.
When you need to collect a dump, be sure to follow the procedure documented in the System
Administrator Guide, MK-94HM8016-nn as presented on the previous slide. You can search this
PDF file for the phrase, “Dump Tool.”
Page 6-14
Standard CS&S Tasks
Record a Block Environment Config Backup
There are two ways to record a VSP Gx00 and VSP Fx00 block environment configuration
backup. The System Administrator Guide, MK-94HM8016-nn, documents the procedure
using .bat file on the SVP. Some information from this document is shown on this slide.
In the VSP Gx00 or VSP Fx00 architecture, the MPC GUI running on the Maintenance PC can be
used to record a block environment configuration backup. Use of the Maintenance PC is limited
to Hitachi Data Systems personnel or partner staff.
Page 6-15
Standard CS&S Tasks
Cross-Controller Internal Network
10.251.0.15/4.15
10.1.0.15/4.15
172.24.0.15/4.15
172.24.0.15/4.15
10.198.0.15/4.15
10.17.0.15/4.15
10.97.0.15/4.15
10.251.0.15/4.15
172.17.0.15/4.15
172.31.0.15/4.15
192/168.0.15/4.15
You can manually configure the IP address values of the VSP Gx00 or VSP Fx00 internal
network through the Maintenance Utility GUI. The default IP values for the internal network are
different depending on whether the system is configured for block-only or with NAS modules.
The installation of the NAS modules changes the internal network IP addresses of the two
controllers to 10.251.0.15 and 10.251.4.15 respectively. Remember: Do not change these
values.
In the training labs, when we want to reset a system from unified back to block-only
configuration, we must manually change the internal network IP addresses back to the block-
only default values. Remember: This is the only time that you would manually change the
internal network IP addresses.
Page 6-16
Standard CS&S Tasks
Internal Networking – Block-Only
172.16.25.50 172.16.25.60
Maintenance port Management port Management port Maintenance port
NAT NAT
eth1.4001 eth1.4002 eth1.4002 eth1.4001
Internal LAN
126.255.0.0/16
CTL#1 CTL#2
The Internal and maintenance LANs have five selectable subnets, but these cannot be freely
configured. The IP addresses are assigned into subnet external management LAN IP addresses,
and can be configured to be compatible with the connection to the customer’s datacenter
management network. While IPv6 is also supported, it is not shown here.
The default internal LAN IP addresses for a VSP Gx00 or VSP Fx00 block-only configuration are
126.255.0.15 and 126.255.4.15 for controller 1 and controller 2, respectively. Note: These
values are changed during the NAS code installation when installing the NAS modules.
Page 6-17
Standard CS&S Tasks
Fan Chassis With Batteries (4U Controller)
BAT-O11
BAT-B11
BKMF-11
These diagrams are taken from the HM800 Maintenance Manual Location section. Hitachi
storage system components are sometimes identified as being “Basic” or “Optional.” You can
think of it this way: “Basic” means “required.”
All the battery components with a “B” before their two digit identification number are required
and are found in every VSP Gx00 and VSP Fx00 system. The batteries with an “O” before the
two digit ID number are optional. They are installed depending on the cache or NAS modules
configuration of the specific VSP Gx00 or VSP Fx00 system.
The “rear side” batteries in BKMF-10 and BKMF-20 are two batteries that are required for the
“with NAS module” configuration.
Here, BKMF stands for Backup Module Fan and BAT stands for battery.
Page 6-18
Standard CS&S Tasks
Battery Naming Scheme
BAT-XYY
Type Location
• B – Basic • 1Y – CTL1
• O – Optional • 2Y – CTL2
• F – File • Y1 – Fan #
The battery component ID indicates whether a battery is basic (required), optional, or required
for the file (with NAS module) configuration.
Page 6-19
Standard CS&S Tasks
Block Configuration With CHBs Only
When they are added, the NAS modules must be installed in the A, B, C and D positions in both
controllers. That means that any CHBs already installed in those slots must be relocated to
make room in the A, B, C and D slots. Migration of the block workload can be done
nondisruptively, but it is a multi-step process and is not discussed during these workshops.
Page 6-20
Standard CS&S Tasks
VSP G800 Only – FE Expansion Chassis in Unified Configuration
SW PK (2 PKs-
upper and
lower)
CHB
2xPSU
LANB DKB
PCI cables
In the case of a VSP G800 or VSP F800, the optional FE Expansion Chassis is supported. This is
also called the Channel Board Box, CHB Box or CHBB. The CHBB provides the ability to expand
the number of front end (FE) ports on the large, VSP G800 system.
Page 6-21
Standard CS&S Tasks
VSP G800 Only – CHBB Slot Locations (Rear)
PCP Package x 2
Slots CTL2
Slots CTL1
The CHBB front end expansion chassis is supported only for use with HM800H (VSP G800 or
VSP F800). It doubles the number of available FE ports. The CHBB holds up to 8 additional CHB
PCBs, four per controller. CHBs in the CHBB must be installed in pairs. It is connected to the
CBX via two PCIe cables per controller. It requires two additional rack unit slots. Only one CHBB
per CBX is supported. It offers four additional external slots per controller for CHB installation.
At the time this training material was created, the 16/32 gigabit per second CHBs were not
supported in the CHBB. Be sure to check the supported configurations.
Page 6-22
Standard CS&S Tasks
Verify Block Licenses Are Installed
The three Program Product (PP) License Keys required in the block environment to support the
NAS Platform are all included in the base SVOS licenses set. They are:
Resource Partition Manager (which has the ability to create and manage Resource Groups),
And Virtual Partition Manager (which has the ability to create and manage Cache Logical
Partitions or CLPRs).
The need for these three PP licenses for the “with NAS modules” configuration is documented in
the HM800 Maintenance Manual Installation Section on page INST07-01-10.
The customer should receive these license keys along with their VSP Gx00 or VSP Fx00 system,
even if the system was originally ordered in block-only configuration. Review the installed
licenses and confirm that these three license keys are installed. The instructions for installing
license keys are found in the HM800 Maintenance Manual Maintenance PC section on page
MPC03-380.
Page 6-23
Standard CS&S Tasks
Check Installed Firmware Versions
VSP Gx00 and VSP Fx00 installed firmware versions can be viewed through the MPC GUI,
formerly called the SVP Application. Here is an example of the MPC GUI Versions view. The
process to view installed firmware versions using the MPC GUI is documented in the HM800
Maintenance Manual Maintenance PC Section.
Page 6-24
7. Firmware Upgrade
Now we will review information about VSP Gx00 and VSP Fx00 firmware upgrades.
https://support.hds.com/en_us/user/tech-tips/e/2016july/T2016071201.html
You must know how to get and use the Microcode Exchange Wizard Tool. The VSP Gx00 and
VSP Fx00 Microcode Exchange Wizard Tool is also known as 83-MCTool.
This version was obtained from the link shown on this slide.
Page 7-1
Firmware Upgrade
Firmware Upgrade Checklist
Action MM Reference
1 Confirm current firmware component versions <good practice>
2 Clear browser caches; close all browsers FIRM03-51 (1)
3 Run setup.exe – run as administrator FIRM03-51 (3)
4 Continue with firmware upgrade process FIRM03-52 through FIRM03-66
5 Verify “From” and “To” firmware versions FIRM03-67
6 GUM reboots (*) FIRM03-68 (5)
7 Wait for the firmware update processing to complete FIRM03-68 17
(**)
8 Confirm component firmware versions 83-MCTool
9 Confirm all hardware normal status 83-MCTool
10 Confirm HCS and HSA access <good practice>
This table presents a shortened, step-wise view of the firmware upgrade procedure with links to
pages in the HM800 Maintenance Manual Firmware Section. Some of the steps are common
sense and are not explicitly specified in the documented instructions.
The 83-MCTool refers to the instructions you will get from the VSP Gx00 and VSP Fx00
Microcode Exchange Wizard Tool.
The one asterisk note indicates that you will not lose connection when the GUM reboots
because you are not communicating through the GUM.
The two asterisk note indicates the installation of a firmware update in a system with NAS
modules can run up to 540 minutes (9 hours). The time required for a unified system firmware
upgrade is somewhat shorter with SVOS 7.0, released in October, 2016.
Page 7-2
Firmware Upgrade
Maintenance Interfaces and Network Connections
Maintenance PC
MPC software
SVP
GUM
Internal LAN
Management LAN
Maintenance Port
You saw this diagram earlier in the training materials. We present it again, because it is actually
found in the HM800 Maintenance Manual Firmware section.
The Firmware section includes the instructions for firmware upgrades. When you read the
firmware upgrade instructions, you will notice that the instructions seem to specifically say to
run the firmware upgrade from the Maintenance PC. However the instructions also seem to say
that it is possible to run the firmware upgrade from the SVP. This diagram does not show the
process of running a firmware upgrade from the SVP. However, the supported Hitachi Data
Systems procedure is to run the firmware upgrade from the SVP.
Page 7-3
Firmware Upgrade
Run the Firmware Upgrade From the SVP
All the instructions in the HM800 Maintenance Manual Firmware Section specify running
firmware updates from the MPC. However, Hitachi Data Systems Product Support has informed
us that firmware upgrades can and should be run from the SVP. Be sure to upgrade Storage
Navigator on the Maintenance PC.
Page 7-4
Firmware Upgrade
Check Installed Firmware Versions Before Firmware Upgrade
The instructions in the Maintenance Manual do not specify checking the current firmware
versions. This is, however, a common sense thing to do.
Take time to review and confirm the installed firmware component versions against the current
ECN. There is a documented procedure to correct mismatching firmware. Refer to TRBL02-370.
If you identify a firmware mismatch in a running system, be sure to report this condition to
Hitachi Global Support Center (GSC) and get their advice and support as you correct the
mismatch. The system must also be clean of any outstanding hardware maintenance issues
before starting a firmware upgrade.
Page 7-5
Firmware Upgrade
Start Upgrade – Run setup.exe on the SVP
This screen image was taken from an MPC. You should run the firmware upgrade from the SVP.
Here is the outline of a firmware upgrade process on a VSP Gx00 or VSP Fx00 system.
2. Take care to use the correct .iso file (file name H8-SVP-xxx-yy) for mounting.
If there is no DVD drive mounted on SVP, copy all files to a work folder on the SVP. Here are
the software locations:
Page 7-6
Firmware Upgrade
Firmware Upgrade: Confirm License Agreement
Here are examples of the first screens displayed after the firmware upgrade setup.exe is started.
Refer to the Firmware section of the Maintenance Manual. See page FIRM03-52.
This slide shows the dialog sequence screens that you will encounter during the firmware
upgrade. Refer to FIRM03-51 through FIRM03-67.
Page 7-7
Firmware Upgrade
Environmental Settings I
Environmental Settings I
This slide shows the Environmental Settings screen you will see in the firmware upgrade
process.
After the Environmental Settings screen, you will be presented with the Select Update Objects
screen. Select both check boxes. This will apply updated Storage Navigator GUI software and all
the storage system firmware.
Page 7-8
Firmware Upgrade
Environmental Settings II
Environmental Settings II
After you complete the Select Update Objects screen, the system returns to the Environmental
Settings screen. Click Apply to continue.
Next, the Environmental Settings screen reports that Storage Navigator update has been
successful. Then, click the Update button to apply the controller firmware.
Page 7-9
Firmware Upgrade
Update Firmware Screen
The screen example shows the Update Firmware Screen for the unified model.
List of Firmware
components
Phase I uploads files
Phase II updates
firmware
Be sure to check the firmware status after the update is completed in Maintenance Utility. A
firmware upgrade for a VSP Gx00 or VSP Fx00 with NAS modules can run for many hours. Be
sure to schedule unified system firmware upgrades carefully in collaboration with the customer.
Refer to the Firmware section of the Maintenance Manual section FIRM03-68 which indicates
run time durations for firmware upgrades for block-only and unified systems.
Page 7-10
8. Troubleshooting
In this section we will review some basic troubleshooting concepts and practices.
This button
will blink
It is important to check the storage system for the existence of pinned data before performing
any maintenance tasks. Pinned data is data updates that are stranded in the data cache and the
system has not successfully recorded the data to the physical disk. Indication of the existence
of pinned data is shown by the “Pin…” button blinking in the Maintenance view from the MPC
GUI.
Page 8-1
Troubleshooting
Multiple Concurrent Failures Requires Careful Planning
If a system has multiple concurrent component failures, you will need guidance and direction
from the Global Support Center.
Page 8-2
Troubleshooting
Replacing a Memory DIMM
When asked to perform a memory DIMM replacement, be very careful to locate the correct
DIMM position because the mainboards do not have indicator LEDs for failed memory DIMMs.
Use the error message information and the DIMM position layout diagrams in the Technical
Guide and also as marked on the mainboard. Press the memory module locking latches to
release the memory module.
Here is an important hint from a server maintenance expert. To help verify that the DIMM has
failed and not a slot, take one of the good DIMMs and move it to the slot where the DIMM
failure occurred. Then, install the replacement DIMM into the now empty slot. This provides
double confirmation that the DIMM has failed and not the DIMM slot.
To install a DIMM, set the replacement DIMM into the empty slot. Apply even pressure across
the top of the DIMM module until it clicks into the slot. Make sure the locking latches are
engaged.
It is best practice to insert, remove and re-insert a new DIMM module. This ensures that any
coating applied to the contacts is scratched and that good contact is made between the
connectors in the slot and the connectors on the DIMM module.
Page 8-3
Troubleshooting
Block Environment SIM Messages and RC Codes
This diagram shows how System Sense Bytes (SSBs), System Information Messages (SIMs) and
Action Codes (ACCs) are used when the VSP Gx00 or VSP Fx00 block environment detects a
hardware error or failure. Because the NAS modules are now integrated hardware components,
hardware errors of the NAS SFPs, NAS module DIMMs or the NAS modules themselves are
detected through internal SSBs and are reported through SIM messages and the system’s Alert
status.
This internal hardware error detection does not recognize NAS logical errors which are reported
through the NAS Platform.
This troubleshooting flow diagram is found in the Troubleshooting section of the Maintenance
Manual. See page TRBL01-10.
Page 8-4
Troubleshooting
Collect Dump Using the SVP
4. Move the current directory to the folder where the tool is available.
5. Execute Dump_Detail.bat and specify the output directory for the dump file.
6. A completion message box displays. Press any key to acknowledge the message and
close the message box.
Note: NAS logs and diagnostics must be collected separately from the NAS Manager GUI or command line.
Hitachi Global Support Center requires that storage system dumps be collected by running the
executable dump tool from the SVP. This tool creates a single diagnostic bundle that contains
block storage system logs and diagnostics only including Block dump and Maintenance Utility
and SVP diagnostics. Here are the steps in the dump collection process.
Page 8-5
Troubleshooting
Management Interface Connectivity Problems – Rebooting the GUM From the BEM
If you cannot access the Maintenance Utility, then you must troubleshoot the Maintenance
Utility and its access. A table of different Maintenance Utility access problems is found in the
HM800 Maintenance Manual Maintenance PC Section starting on page MPC01-530. The
Maintenance Utility is served by the GUM which runs on the controller.
The GUM component alone can be rebooted using the Block Element Manager – Device
Manager Storage Navigator. Select Maintenance Utility > Hardware > GUM reboot > entry of
the controller whose GUM you want to reboot. Recall that the GUM runs on the controller and
that the Block Element Manager runs on the SVP. If rebooting the GUM does not resolve
connectivity issues, you can perform the GUM Reset. This is covered on the next slide.
Page 8-6
Troubleshooting
Rebooting the GUM From the Maintenance Utility
It is also possible to reboot the GUM from the Maintenance Utility. However, this may seem
somewhat illogical because the Maintenance Utility is accessed through the GUM. So, if you can
still log onto the Maintenance Utility but it is not behaving correctly, you may want to reboot
the GUM. You will lose the connection to the Maintenance Utility and will have to reconnect
after the GUM has rebooted.
In the Menu section of the left pane on the Maintenance Utility GUI, select System
Management > Reboot GUM. The instructions for rebooting the GUM from the Maintenance
Utility are found in HM800 Maintenance Manual Maintenance PC Section on page MPC03-730.
Page 8-7
Troubleshooting
Forceful Hardware Reset of the GUM
The diagram shown on this slide is taken from the HM800 Maintenance Manual Location Section.
Item 1-5 in the diagram is the LAN Reset button found in the center of the front of the VSP
Gx00 and VSP Fx00 chassis (VSP G400, VSP G600, and VSP G800).
If the GUM cannot be contacted through any of its software interfaces, the GUM can be forcibly
reset by pressing the hardware reset button for 1 second. Instructions for using the LAN-RST
button are found in HM800 Maintenance Manual Maintenance PC Section on page MPC03-870.
Page 8-8
9. Hi-Track for Unified Systems
Here is a quick review of Hi-Track Remote Monitoring and what you need to know when
configuring and using Hi-Track with VSP Gx00 or VSP Fx00 with NAS modules systems.
Page 9-1
Hi-Track for Unified Systems
Register the Storage Array With Hi-Track Agent
Inbound
Customer Site remote access
Hi-Track
Site Manager
SVP running on
Agent SVP or
standalone
PC
Outbound HDS
SVP
communication Hi-Track
Agent to Hitachi Data Center
Systems
through FTP,
Older Model https or dial-up
To set up a VSP Gx00 or VSP Fx00 with NAS modules for Hi-Track monitoring, register the block
storage array using the Hi-Track Agent. The NAS platform is registered with Hi-Track Monitor.
See more information on the next slide.
For full instructions and the correct version of Hi-Track, consult the documentation
from http://hitrack.hds.com.
Page 9-2
Hi-Track for Unified Systems
Register the NAS SMU to Hi-Track Monitor
Hi-Track support for VSP Gx00 and VSP Fx00 with NAS modules unified systems requires that
the block “side” is registered to Hi-Track and that the NAS Platform is registered with Hi-Track
Monitor. The VSP Gx00 and VSP Fx00 With NAS Modules Differences course, THC2794, contains
information about Hi-Track for unified systems.
Page 9-3
Hi-Track for Unified Systems
Workshop Prerequisite Materials Review Summary
By reviewing and understanding the information in this prerequisite training, you should now be
able to perform these tasks.
This ends the prerequisite review for the VSP Gx00 and VSP Fx00 With NAS Modules Hands-On
Workshop for CS&S.
Page 9-4
Training Course Glossary
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
ACC — Action Code. A SIM (System Information AL-PA — Arbitrated Loop Physical Address.
Message). AMS — Adaptable Modular Storage.
ACE — Access Control Entry. Stores access rights APAR — Authorized Program Analysis Reports.
for a single user or group within the APF — Authorized Program Facility. In IBM z/OS
Windows security model. and OS/390 environments, a facility that
ACL — Access Control List. Stores a set of ACEs permits the identification of programs that
so that it describes the complete set of access are authorized to use restricted functions.
rights for a file system object within the API — Application Programming Interface.
Microsoft Windows security model.
APID — Application Identification. An ID to
ACP ― Array Control Processor. Microprocessor identify a command device.
mounted on the disk adapter circuit board
(DKA) that controls the drives in a specific Application Management — The processes that
disk array. Considered part of the back end; manage the capacity and performance of
it controls data transfer between cache and applications.
the hard drives. ARB — Arbitration or request.
ACP Domain ― Also Array Domain. All of the ARM — Automated Restart Manager.
array-groups controlled by the same pair of Array Domain — Also ACP Domain. All
DKA boards, or the HDDs managed by 1 functions, paths and disk drives controlled
ACP PAIR (also called BED). by a single ACP pair. An array domain can
ACP PAIR ― Physical disk access control logic. contain a variety of LVI or LU
Each ACP consists of 2 DKA PCBs to configurations.
provide 8 loop paths to the real HDDs. Array Group — Also called a parity group. A
Actuator (arm) — Read/write heads are attached group of hard disk drives (HDDs) that form
to a single head actuator, or actuator arm, the basic unit of storage in a subsystem. All
that moves the heads around the platters. HDDs in a parity group must have the same
AD — Active Directory. physical capacity.
ADC — Accelerated Data Copy. Array Unit — A group of hard disk drives in 1
RAID structure. Same as parity group.
Address — A location of data, usually in main
memory or on a disk. A name or token that ASIC — Application specific integrated circuit.
identifies a network component. In local area ASSY — Assembly.
networks (LANs), for example, every node Asymmetric virtualization — See Out-of-Band
has a unique address. virtualization.
ADP — Adapter. Asynchronous — An I/O operation whose
ADS — Active Directory Service. initiator does not await its completion before
CLPR — Cache Logical Partition. Cache can be Cloud Fundamental —A core requirement to the
deployment of cloud computing. Cloud
divided into multiple virtual cache
memories to lessen I/O contention. fundamentals include:
RPC — Remote procedure call. SAN ― Storage Area Network. A network linking
computing devices to disk or tape arrays and
RPO — Recovery Point Objective. The point in other devices over Fibre Channel. It handles
time that recovered data should match. data at the block level.
RPSFAN — Rear Power Supply Fan Assembly. SAP — (1) System Assist Processor (for I/O
RRDS — Relative Record Data Set. processing), or (2) a German software
RS CON — RS232C/RS422 Interface Connector. company.
RSD — RAID Storage Division (of Hitachi). SAP HANA — High Performance Analytic
Appliance, a database appliance technology
R-SIM — Remote Service Information Message. proprietary to SAP.
RSM — Real Storage Manager. SARD — System Assurance Registration
RTM — Recovery Termination Manager. Document.
RTO — Recovery Time Objective. The length of SAS —Serial Attached SCSI.
time that can be tolerated between a disaster SATA — Serial ATA. Serial Advanced Technology
and recovery of data. Attachment is a new standard for connecting
R-VOL — Remote Volume. hard drives into computer systems. SATA is
R/W — Read/Write. based on serial signaling technology, unlike
current IDE (Integrated Drive Electronics)
-back to top-
hard drives that use parallel signaling.
—S— SBM — Solutions Business Manager.
SA — Storage Administrator. SBOD — Switched Bunch of Disks.
SA z/OS — System Automation for z/OS. SBSC — Smart Business Storage Cloud.
SAA — Share Access Authentication. The process SBX — Small Box (Small Form Factor).
of restricting a user's rights to a file system
SC — (1) Simplex connector. Fibre Channel
object by combining the security descriptors
connector that is larger than a Lucent
from both the file system object itself and the
connector (LC). (2) Single Cabinet.
share to which the user is connected.
SCM — Supply Chain Management.
SaaS — Software as a Service. A cloud computing
SCP — Secure Copy.
business model. SaaS is a software delivery
model in which software and its associated SCSI — Small Computer Systems Interface. A
data are hosted centrally in a cloud and are parallel bus architecture and a protocol for
typically accessed by users using a thin transmitting large data blocks up to a
client, such as a web browser via the distance of 15 to 25 meters.
Internet. SaaS has become a common SD — Software Division (of Hitachi).
WAN — Wide Area Network. A computing XFI — Standard interface for connecting a 10Gb
internetwork that covers a broad area or Ethernet MAC device to XFP interface.
region. Contrast with PAN, LAN and MAN.
XFP — "X"=10Gb Small Form Factor Pluggable.
WDIR — Directory Name Object.
XML — eXtensible Markup Language.
WDIR — Working Directory.
XRC — Extended Remote Copy.
WDS — Working Data Set. -back to top-
https://learningcenter.hds.com/Saba/Web/Main
Page E-1
Evaluating This Course
Page E-2