Hitachi Virtual Storage Platform 5000 Series
SVOS RF 9
Hitachi Alert Notification Guide
The Alert Notification feature provides failure monitoring functions (which include monitoring of your
storage systems by using SNMP), enabling you to recognize and fix failures in your storage system.
MK-98RD9011-00
October 2019
© 2019 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and
recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or
Hitachi Vantara Corporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as an
essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not
make any other copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, video and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials
contain the most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for
information about feature and product availability, or contact Hitachi Vantara Corporation at
us.html.
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of
Hitachi products is governed by the terms of your agreements with Hitachi Vantara Corporation.
By using this software, you agree that you are responsible for:
1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other
individuals; and
2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including
the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader
agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or
import the Document and any Compliant Products.
Hitachi and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/390,
PowerHA, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z14, z/VM, and z/VSE are registered trademarks or
trademarks of International Business Machines Corporation.
Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS,
Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,
Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks
of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found at
www.hitachivantara.com/en-us/company/legal.html.
https://support.hitachivantara.com/en_us/contact-
https://
Hitachi Alert Notication Guide for VSP5000 Series 2
Contents
Preface..................................................................................................... 5
Intended audience............................................................................................... 5
Product version....................................................................................................5
Release notes......................................................................................................5
Changes in this revision.......................................................................................6
Document conventions........................................................................................ 6
Conventions for storage capacity values............................................................. 7
Accessing product documentation.......................................................................8
Getting help..........................................................................................................8
Comments............................................................................................................8
Chapter 1: Failure monitoring................................................................9
Alert notification email..........................................................................................9
Syslog................................................................................................................ 10
SNMP.................................................................................................................18
Chapter 2: Setting alert notification email..........................................19
Editing alert notification email settings...............................................................19
Chapter 3: Setting Syslog.................................................................... 22
Editing Syslog settings.......................................................................................22
Chapter 4: Setting SNMP......................................................................24
Editing alert settings...........................................................................................24
Managing SNMP trap notification...................................................................... 24
Adding trap notification for SNMP v1 and SNMP v2c.................................. 25
Adding trap notification for SNMP v3........................................................... 26
Changing trap notification for SNMP v1 and SNMP v2c.............................. 27
Changing trap notification for SNMP v3....................................................... 28
Deleting SNMP trap notification................................................................... 29
Managing SNMP request authentication........................................................... 30
Adding request authentication for SNMP v1 and SNMP v2c....................... 30
Adding request authentication for SNMP v3................................................ 31
Changing request authentication for SNMP v1 and SNMP v2c................... 32
Changing request authentication for SNMP v3............................................ 33
Deleting SNMP request authentication........................................................ 34
Contents
Hitachi Alert Notication Guide for VSP5000 Series 3
Testing the SNMP trap report.............................................................................35
Chapter 5: Troubleshooting................................................................. 36
Solving SNMP problems....................................................................................36
Chapter 6: SNMP overview...................................................................37
SNMP Manager overview.................................................................................. 37
How SNMP works.........................................................................................37
Management Information Base overview..................................................... 38
SNMP Agent configuration................................................................................ 38
SNMP Agent overview.......................................................................................39
SNMP traps.................................................................................................. 39
SNMP Agent operations...............................................................................40
SNMP Agent reported errors........................................................................40
Component status information from SNMP Manager........................................ 41
Chapter 7: SNMP supported MIBs.......................................................43
SNMP Agent failure report trap contents........................................................... 43
SNMP Agent extension trap types.....................................................................44
Standard MIB specifications.............................................................................. 44
MIBs supported by SNMP Agent..................................................................44
SNMP Agent MIB access mode................................................................... 45
Example object identifier system..................................................................45
MIB mounting specifications supported by SNMP Agent............................. 45
Extension MIB specifications............................................................................. 46
Extension MIB configuration.........................................................................46
raidExMibName............................................................................................48
raidExMibVersion..........................................................................................48
raidExMibAgentVersion................................................................................49
raidExMibDkcCount......................................................................................49
raidExMibRaidListTable................................................................................49
raidExMibDKCHWTable............................................................................... 50
raidExMibDKUHWTable............................................................................... 52
raidExMibTrapListTable................................................................................ 53
Chapter 8: SIM codes ...........................................................................55
Failure trap reference codes..............................................................................55
Converting DB and RDEV numbers to the HDD location number..................... 88
Glossary............................................................................................. 91
Contents
Hitachi Alert Notication Guide for VSP5000 Series 4
Preface
The Alert
monitoring of your storage systems by using SNMP), enabling you to recognize and x
failures in your storage system.
Please read this document carefully to understand how to use this product, and maintain
a copy for reference purposes.
Notication feature provides failure monitoring functions (which include
Intended audience
This document is intended for system administrators, Hitachi Vantara representatives,
and authorized service providers who install, congure, and operate Hitachi Virtual
Storage Platform 5000 series storage systems.
Readers of this document should be familiar with the following:
■
Data processing and RAID storage systems and their basic functions.
■
Hitachi Virtual Storage Platform 5000 series storage systems and the Product
Overview.
■
The Device Manager - Storage Navigator software for the Hitachi Virtual Storage
Platform 5000 series, and the System Administrator Guide.
Product version
This document revision applies to the following product versions:
■
VSP 5000 series: irmware 90-01-4x or later
■
SVOS RF 9 or later
Release notes
Read the release notes before installing and using this product. They may contain
requirements or restrictions that are not fully described in this document or updates or
corrections to this document. Release notes are available on Hitachi Vantara Support
Connect:
https://knowledge.hitachivantara.com/Documents.
Preface
Hitachi Alert Notication Guide for VSP5000 Series 5
Changes in this revision
■
Added information and specications for VSP 5000 series.
Document conventions
This document uses the following typographic conventions:
Convention Description
Changes in this revision
Bold
Italic
Monospace
< > angle
brackets
■
Indicates text in a window, including window titles, menus,
menu options, buttons, elds, and labels. Example:
Click OK.
■
Indicates emphasized words in list items.
■
Indicates a document title or emphasized words in text.
■
Indicates a variable, which is a placeholder for actual text
provided by the user or for output by the system. Example:
pairdisplay -g group
(For exceptions to this convention for variables, see the entry for
angle brackets.)
Indicates text that is displayed on screen or entered by the user.
Example: pairdisplay -g oradb
Indicates variables in the following scenarios:
■
Variables are not clearly separated from the surrounding text or
from other variables. Example:
Status-<report-name><file-version>.csv
■
Variables in headings.
[ ] square
brackets
Indicates optional values. Example: [ a | b ] indicates that you can
choose a, b, or nothing.
{ } braces Indicates required or expected values. Example: { a | b } indicates
that you must choose either a or b.
| vertical bar Indicates that you have a choice between two or more options or
arguments. Examples:
[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.
Preface
Hitachi Alert Notication Guide for VSP5000 Series 6
Conventions for storage capacity values
This document uses the following icons to draw attention to information:
Icon Label Description
Note Calls attention to important or additional information.
Tip Provides helpful information, guidelines, or suggestions for
performing tasks more eectively.
Caution Warns the user of adverse conditions and/or consequences
(for example, disruptive operations, data loss, or a system
crash).
WARNING Warns the user of a hazardous situation which, if not
avoided, could result in death or serious injury.
Conventions for storage capacity values
Physical storage capacity values (for example, disk drive capacity) are calculated based
on the following values:
Physical capacity unit Value
1 kilobyte (KB) 1,000 (103) bytes
1 megabyte (MB) 1,000 KB or 1,0002 bytes
1 gigabyte (GB) 1,000 MB or 1,0003 bytes
1 terabyte (TB) 1,000 GB or 1,0004 bytes
1 petabyte (PB) 1,000 TB or 1,0005 bytes
1 exabyte (EB) 1,000 PB or 1,0006 bytes
Logical capacity values (for example, logical device capacity, cache memory capacity) are
calculated based on the following values:
Logical capacity unit
1 block 512 bytes
1 cylinder Mainframe: 870 KB
Preface
Hitachi Alert Notication Guide for VSP5000 Series 7
Value
Accessing product documentation
Logical capacity unit Value
Open-systems:
■
OPEN-V: 960 KB
■
Others: 720 KB
1 KB 1,024 (210) bytes
1 MB 1,024 KB or 1,0242 bytes
1 GB 1,024 MB or 1,0243 bytes
1 TB 1,024 GB or 1,0244 bytes
1 PB 1,024 TB or 1,0245 bytes
1 EB 1,024 PB or 1,0246 bytes
Accessing product documentation
Product user documentation is available on Hitachi Vantara Support Connect: https://
knowledge.hitachivantara.com/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release
of the product.
Getting help
Hitachi Vantara Support Connect is the destination for technical support of products and
solutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi Vantara
Support Connect for contact information: https://support.hitachivantara.com/en_us/
contact-us.html.
Hitachi Vantara Community is a global online community for Hitachi Vantara customers,
partners, independent software vendors, employees, and prospects. It is the destination
to get answers, discover insights, and make connections. Join the conversation today!
Go to community.hitachivantara.com, register, and complete your prole.
Comments
Please send us your comments on this document to
doc.comments@hitachivantara.com. Include the document title and number, including
the revision level (for example, -07), and refer to specic sections and paragraphs
whenever possible. All comments become the property of Hitachi Vantara Corporation.
Thank you!
Preface
Hitachi Alert Notication Guide for VSP5000 Series 8
Chapter 1: Failure monitoring
By using the Hitachi Device Manager - Storage Navigator, you can use alert notication
email, Syslog, and SNMP for failure monitoring.
Alert notification email
The following gives an example of an alert notication email that is sent from a storage
system to the mail server.
VSP 5100 Report
//RAID900 //VSP //////////////////////////////
//e-Mail Report
//////////////////////////////
Date : 20/04/2018
Time : 00:20:00
Machine : VSP 5100(Serial# 64019)
RefCode : 7fffff
Detail: This is Test Report.
The following table describes the components of an alert notication email.
Component Item in the example Description
Title VSP 5100 Report The product name of the
storage system + "Report"
Additional
information
Date Date : 20/04/2018 The date when the error
Time Time : 00:20:00 The time when the error
Hardware
identication
//RAID900 //
VSP //////////////////////////////
//e-Mail Report
//////////////////////////////
Machine : VSP 5100(Serial#
64019)
The information set in Editing
alert notication email settings
(on page 19)
Nothing appears if no
information is set.
occurred
occurred
The storage system name that is
set in Storage Navigator +
"(Serial#" + Serial number + ")"
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 9
Syslog
Syslog
Component Item in the example Description
Failure code RefCode : 7f The reference code that appears
in the alert window
Failure detail Detail: This is Test Report. Information of failure locations
that need maintenance
Information of a maximum of
eight failure locations appears.
Each information item includes
the following items: action code,
assumed failure part, and
location.
The following gives examples of Syslog data that is sent from a storage system to the
syslog server.
You can use the maintenance utility to select either of the following message formats:
RFC3164-compliant or RFC5424-compliant.
For details, see
Editing Syslog settings (on page 22)
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 10
Syslog le format (RFC3164-compliant)
Syslog
Item 29 and 30 are output either one of them in one syslog information.
No. Item Description
1 Priority The priority of an item in the syslog le is determined
according to the following formula, enclosed by brackets (< >):
Priority = 8 X Facility + Severity
Facility is 1 (xed).
Severity depends on the type of log information:
■
4: Error or Warning. Error means the operation has ended
abnormally. Warning means the operation has partly
ended abnormally or was canceled during the operation.
■
6: Informational. The operation has ended normally.
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 11
No. Item Description
For example, <12> indicates the priority when the severity is
error.
2 Date, time* The date and time in the format of "MMM DD HH:MM:SS"
(MMM: month such as Jan or Dec, DD: day, HH: hour, MM:
minute and SS: second).
If the "DD" is a single digit (for example, 1), it is displayed as "
1" (with a blank space before "1") and not as "01".
Syslog
3 Detected
The host name (SVP).
location
4 Program name The detection entity identier (Storage).
5 Unied
The Unied specication identier (CELFSS).
specication
6 The revision number of the Unied specication document
identication
(1.1).
7 Message
The serial number of the syslog header information.
identication
8 No output
9 Date, time#2* The date, time and the time dierence between UTC and the
local time in the format of "YYYY-MM-DD-Thh:mm:ss.s ±
hh:mm".
■
YYYY: year, MM: month, DD: day
■
hh: hour, mm: minute, ss.s: second in one decimal place.
■
± hh:mm: hours and minute of the time dierence. "Z" is
displayed instead of "± hh:mm" when there is no time
dierence between UTC and the local time, such as
"2005-12-26T:23:06:58.0Z".
10 Detection entity The detection entity identier (Storage).
11 Detected
The host name (SVP).
location
12 Type of audit
event
The category name of the event.
■
Authentication of RMI, FC-SP, or Device Manager - Storage
Navigator.
■
CongurationAccess indicates setting from Device
Manager - Storage Navigator, SVP or host.
■
Maintenance indicates SVP operations.
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 12
No. Item Description
■
AnomalyEvent indicates reached the maximum of the
Audit Log, etc.
■
ExternalService indicates remote maintenance operations
through SVP.
Syslog
13 Result of audit
event
14 Subject
identication
15 Hardware
identication
16 Generated
location
17 Related
information
■
Success: Normal end. The operation has ended normally.
■
Failed: Error (xxxx-yyyy). The operation has ended
abnormally.
■
Failed: Warning (xxxx-yyyy). The operation has partly ended
abnormally or was canceled during the operation.
"xxxx-yyyyy" indicates error codes and it is output only for
Device Manager - Storage Navigator operations.
The user name in the format of "uid=user name".
■
<system> is output when the category name is
AnomalyEvent.
■
<DKCMaintenance> is output for SVP operations.
■
<Host> is output for commands from host.
The ID (R900) to identify the model name of the product and
the serial number divided by a colon.
No output.
The location identication name set by the user in the Syslog
tab on Edit Audit Log Settings window.
18 No output.
19 No output.
20 Agent
No output.
information
21 Detailed
information
Identication of the host sending the request.
This information is output when a command is received from
the host unless it is FC-SP authentication.
22 No output.
23 No output.
24 No output.
25 Collective operation identier. This is a serial number that
identies those multiple lines displayed by one operation are
the same operation.
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 13
Syslog
No. Item Description
Outputs only if the log type information is "BasicLog" and the
category name is other than "AnomalyEvent".
26 Log type information:
■
BasicLog: basic information
■
DetailLog: detailed information
No output when the category name is "AnomalyEvent".
27 Identication of the application. This information is output
when commands are sent from the host.
28 No output.
29 The same information contained in the basic information of
the audit log le, such as interface, task name, function name,
operation name, parameter, result, and serial number. Task
name is output only when a task is registered using Device
Manager - Storage Navigator. No parameter is output if the
operation has no parameters. No serial number is output
when the category name is "AnomalyEvent".
30 The same information contained in the detailed information
of the audit log le.
*A date and time being set on SVP are output as log data. If a failure, such as a SVP
failure and a LAN failure, occurs in the storage system, the data and time may be
output of the accumulated date and time since January 01, 1970.
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 14
Syslog le format (RFC5424-compliant)
Syslog
Item 21 and 22 are output either one of them in one syslog information.
No. Item Description
1 Priority The priority of an item in the syslog le is determined
according to the following formula, enclosed by brackets (< >):
Priority = 8 X Facility + Severity
Facility is 1 (xed).
Severity depends on the type of log information:
■
4: Error or Warning. Error means the operation has ended
abnormally. Warning means the operation has partly
ended abnormally or was canceled during the operation.
■
6: Informational. The operation has ended normally.
For example, <12> indicates the priority when the severity is
error.
2 Version The version (1).
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 15
Syslog
No. Item Description
3 Date, time* The date, time and the time dierence between UTC and the
local time in the format of "YYYY-MM-DD-Thh:mm:ss.s ±
hh:mm".
■
YYYY: year, MM: month, DD: day
■
hh: hour, mm: minute, ss.s: second in one decimal place.
■
± hh:mm: hours and minute of the time dierence. "Z" is
displayed instead of "± hh:mm" when there is no time
dierence between UTC and the local time, such as
"2005-12-26T:23:06:58.0Z".
4 Detected
The host name (SVP).
location
5 Program name The detection entity identier (Storage).
6 Process name The process name (-).
7 Message ID The message ID (-).
8 Structured data The structured data (-).
9 Unied
The unied specication identier (CELFSS).
specication
10 The revision number of the unied specication document
identication
(1.1).
11 Message
The serial number of the syslog header information.
identication
12 Type of audit
event
The category name of the event.
■
Authentication of RMI, FC-SP, or Device Manager - Storage
Navigator.
■
CongurationAccess indicates setting from Device
Manager - Storage Navigator, SVP or host.
■
Maintenance indicates SVP operations.
■
AnomalyEvent indicates reached the maximum of the
Audit Log, etc.
■
ExternalService indicates remote maintenance operations
through SVP.
13 Result of audit
event
Hitachi Alert Notication Guide for VSP5000 Series 16
■
Success: Normal end. The operation has ended normally.
■
Failed: Error (xxxx-yyyy). The operation has ended
abnormally.
■
Failed: Warning (xxxx-yyyy). The operation has partly ended
abnormally or was canceled during the operation.
Chapter 1: Failure monitoring
No. Item Description
"xxxx-yyyyy" indicates error codes and it is output only for
Device Manager - Storage Navigator operations.
Syslog
14 Account
identication
The user name in the format of "uid=user name".
■
<system> is output when the category name is
AnomalyEvent.
■
<DKCMaintenance> is output for SVP operations.
■
<Host> is output for commands from host.
15 Hardware
identication
16 Related
information
17 Detailed
information
The ID (R900) to identify the model name of the product and
the serial number divided by a colon.
The location identication name set by the user in the Syslog
tab of Edit Audit Log Settings window.
Identication of the host sending the request.
This information is output when a command is received from
the host unless it is FC-SP authentication.
18 Collective operation identier. This is a serial number that
identies those multiple lines displayed by one operation are
the same operation.
Outputs only if the log type information is "BasicLog" and the
category name is other than "AnomalyEvent".
19 Log type information:
■
BasicLog: basic information
■
DetailLog: detailed information
No output when the category name is "AnomalyEvent".
20 Identication of the application. This information is output
when commands are sent from the host.
21 Detailed
information
The same information contained in the basic information of
the audit log le, such as interface, task name, function name,
operation name, parameter, result, and serial number. Task
name is output only when a task is registered using Device
Manager - Storage Navigator. No parameter is output if the
operation has no parameters. No serial number is output
when the category name is "AnomalyEvent".
22 The same information contained in the detailed information
of the audit log le.
No serial number is output when the category name is
"AnomalyEvent".
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 17
SNMP
SNMP
No. Item Description
*A date and time being set on SVP are output as log data. If a failure, such as a SVP
failure and a LAN failure, occurs in the storage system, the data and time may be
output of the accumulated date and time since January 01, 1970.
SNMP data is sent from a storage system to an SNMP agent. The following table
describes an example of event details that are contained in SNMP data.
Component Example Description
TRAP type raideventUsermoderate Failure level
eventTrapSerialNumber 1 Serial number of the
product
eventTrapNickname VSP5000 Product name
eventTrapREFCODE 212051 The reference code that
appears in the alert
window
eventTrapPartsID dkcHWProcessor Failure location
eventTrapDate 2018/12/21 The date the SNMP Agent
received the SNMP data
eventTrapTime 08:27:50 The time the SNMP Agent
received the SNMP data
eventTrapDescription "Channel port blocking" Information of the failure
locations that need
maintenance
Chapter 1: Failure monitoring
Hitachi Alert Notication Guide for VSP5000 Series 18
Chapter 2: Setting alert notification email
By using the Hitachi Device Manager - Storage Navigator, you can manage the alert
noticatrion email settings.
Editing alert notification email settings
This topic describes how to specify the email settings necessary to report failure trap
reference codes (SIMs).
Before you begin
■
You must have the Storage Administrator (Initial Conguration) role to perform this
task.
■
You must install a mail server that supports Simple Mail Transfer Protocol (SMTP).
■
You must release Port 25 if a rewall is used.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. For Notication Alert, select one of the following:
■ All (Sends alerts of all SIMs.)
■ Host Report (Sends alerts only of SIMs that report to hosts.)
Alert destinations are common to Syslog, SNMP, and Email.
4. Click the Email tab.
5. For Mail Notice, select Enable to enable that option.
Chapter 2: Setting alert notication email
Hitachi Alert Notication Guide for VSP5000 Series 19
Editing alert
notication email settings
6. In Email Settings, enter the destination email address and the attribute (To, Cc,
Bcc).
■ To add an email address, click Add and then specify the email address and
attribute in the Add Address window.
■ To change an email address and the attribute, select the check box for the email
address you want to change, and then click Change. You can change the email
address and attribute in the Change Settings window.
You can select multiple email addresses. If you select multiple email addresses,
you can change their attributes only.
■ To delete email addresses, select the check boxes for the email addresses you
want to delete, and then click Delete.
Make sure that you specify these settings if Mail Notice is set to Enable.
7. Enter the source email address (required) and the return email address (option).
You can enter up to 255 alphanumeric characters and allowed symbols (!, #, $, %, &,
`, +, -, *, /, ', ^, {, }, _, and .).
8. Enter the information of the email server.
■ Identier
To specify the host name, select Identier and then enter up to 63
alphanumeric characters and allowed symbols (!, #, $, `, +, -, *, ', {, }, _, and .).
■ IPv4
To specify an IPv4 address, select IPv4 and then enter four numbers (0 to 255) in
the following format:
XXX.XXX.XXX.XXX (Each XXX indicates a number.)
■ IPv6
To specify an IPv6 address, select IPv6 and then enter eight hexadecimal
numbers (0 to FFFF) in the following format:
YYYY:YYYY:YYYY:YYYY:YYYY:YYYY:YYYY:YYYY (Each YYYY indicates a hexadecimal
number.)
You can also specify the abbreviated format of IPv6 addresses.
Make sure that you specify these settings if Mail Notice is set to Enable.
9. In SMTP Authentication, select Enable (to use SMTP authentication) or Disable (to
not to use SMTP authentication). If you select Enable, also enter the account name
and password that you use for SMTP authentication.
You can enter up to 255 alphanumeric characters and allowed symbols (!, #, $, `, +,
-, *, ', {, }, _, and .).
Make sure that you specify these settings if Mail Notice is set to Enable.
10. Click Send Test Email, if necessary, to test the settings.
Chapter 2: Setting alert notication email
Hitachi Alert Notication Guide for VSP5000 Series 20
Editing alert notication email settings
11. Conrm that you received the test email.
12. Click Finish.
13. Conrm the settings in the Conrm window, and then enter the task name in Task
Name.
14. Click Apply.
The task will be registered. If the check box for Go to tasks window for status is
selected, the Tasks window opens.
Chapter 2: Setting alert notication email
Hitachi Alert Notication Guide for VSP5000 Series 21
Chapter 3: Setting Syslog
By using the Hitachi Device Manager - Storage Navigator, you can manage Syslog
settings.
Editing Syslog settings
This topic describes how to specify the Syslog settings necessary to report a failure in the
storage system.
Before you begin
■
You must have the Storage Administrator (Initial Conguration) role to perform this
task.
■
You must install a server that supports Syslog.
■
You must release the port to be used for sending Syslog data if a rewall is used.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. For Notication Alert, select one of the following:
■ All (Sends alerts of all SIMs.)
■ Host Report (Sends alerts only of SIMs that report to hosts.)
Alert destinations are common to Syslog, SNMP, and Email.
4. Click the Syslog tab.
5. For Transfer Protocol, select the protocol you want to use for sending Syslog data.
6. To send Syslog data to the primary server, select Enable for Primary Server and
then specify the following items:
■ IP Address
■ Port Number
■ Client Certicate File Name, Password, and Root Certicate File Name
Specify this setting only when New Syslog Protocol (TLS1.2/RFC5424) is
selected for Transfer Protocol.
Chapter 3: Setting Syslog
Hitachi Alert Notication Guide for VSP5000 Series 22
Editing Syslog settings
7. To send Syslog data to the alternative server (secondary server), select Enable for
Secondary Server and then specify the following items:
■ IP Address
■ Port Number
■ Client Certicate File Name, Password, and Root Certicate File Name
Specify this setting only when New Syslog Protocol (TLS1.2/RFC5424) is
selected for Transfer Protocol.
8. Specify a name you want for Location Identication Name to identify the storage
system.
9. If New Syslog Protocol (TLS1.2/RFC5424) is selected for Transfer Protocol, specify
the values for Timeout, Retry Interval, and Number of Retries.
10. Click Send Test Message to Syslog Server, if necessary, to test the settings.
11. Conrm that the Syslog server received the log message (detailed data: "RefCode:
7FFFFF, This is Test Report.").
12. Click Finish.
13. Conrm the settings in the Conrm window, and then enter the task name in Task
Name.
14. Click Apply.
The task will be registered. If the check box for Go to tasks window for status is
selected, the Tasks window opens.
Chapter 3: Setting Syslog
Hitachi Alert Notication Guide for VSP5000 Series 23
Chapter 4: Setting SNMP
By using the Hitachi Device Manager - Storage Navigator, you can manage alert settings,
SNMP trap notication, SNMP request authentication, and test SNMP trap reports.
Editing alert settings
This topic describes how to set the Edit Alert Settings.
Caution: Be sure to document your storage system name before this
process, because the settings will be cleared when the SVP is replaced.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. For Notication Alert, select one of the following:
■ All (Sends alerts of all SIMs.)
■ Host Report (Sends alerts only of SIMs that report to hosts. Alert destinations
are common to Syslog, SNMP, and Email.)
4. Select the SNMP tab.
5. For Extension SNMP, select Enable to enable that option.
6. In System Group Information, enter the Storage System Name, Contact, and
Location.
Changes made to information here are also reected in the Storage System
window in Device Manager - Storage Navigator.
7. Click Finish.
8. Enter a name for the task in the Conrm window, conrm the settings, and then
click Apply.
Managing SNMP trap notification
Use the procedure for the SNMP version you use to set SNMP trap notication. The items
to specify are dierent depending on the SNMP version.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 24
Adding trap
notication for SNMP v1 and SNMP v2c
Adding trap notification for SNMP v1 and SNMP v2c
This topic describes the procedure to add IP addresses and communities to trap
notication for SNMP v1 and SNMP v2c.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v1 or v2c.
6. Under Registered Sending Trap Settings, click Add.
7. In the Add Sending Trap Setting window, under Community, enter a community
name or select from the list of existing community names.
You can enter up to 180 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &,', and %.
Do not use a space either at the beginning or the end.
8. Under Send Trap To, perform one or more of the following steps:
■ To enter a new IP address, select IPv4 or IPv6, and then enter the IP address.
■ To use an existing IP address, select from the list of existing IP addresses.
■ To add more than one IP address, click Add IP Address to add additional input
elds.
■ To delete an IP address from Send Trap To, click the minus (-) button next to the
IP address.
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering
eight hexadecimal numbers that are separated by colons (:) using a
maximum of 4 digits from zero (0) to FFFF inclusive. The default form of
the IPv6 address can be specied.
9. Click OK.
The IP address and community you entered are added to the Registered Sending
Trap Settings table.
10. Click Finish.
11. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 25
Adding trap notification for SNMP v3
This topic describes the procedure to add IP addresses and users to trap notication for
SNMP v3.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v3.
6. Under Registered Sending Trap Settings, click Add.
7. In the Add Sending Trap Setting window, under Send Trap To, select IPv4 or IPv6,
and enter an IP address.
Adding trap
notication for SNMP v3
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering
eight hexadecimal numbers that are separated by colons (:) using a
maximum of 4 digits from zero (0) to FFFF inclusive. The default form of
the IPv6 address can be specied.
8. Under User Name, enter a user name.
You can enter up to 32 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &, and %.
Do not use a space either at the beginning or the end.
9. Under Authentication, select whether to Enable or Disable authentication.
If you select Enable, complete the following steps:
a. For Protocol, select an authentication type.
b. For Password, enter a password.
10. Under Encryption, select whether to Enable or Disable encryption.
Note: If you select Disable for Authentication, Encryption is
automatically disabled.
If you select Enable, complete the following steps:
a. For Protocol, select an encryption type.
b. For Key, enter a key.
c. For Re-enter Key, enter the same key for conrmation.
11. Click OK.
The IP address and user you entered are added to the Registered Sending Trap
Settings table.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 26
Changing trap notication for SNMP v1 and SNMP v2c
12. Click Finish.
13. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Changing trap notification for SNMP v1 and SNMP v2c
This topic describes the procedure to change the IP addresses and communities for trap
notication for SNMP v1 and SNMP v2c.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v1 or v2c.
6. Under Registered Sending Trap Settings, select the trap setting you want to
change, and then click Change.
The Change Sending Trap Setting window opens.
7. If you want to change the Community, select the Community check box, and then
enter a community name or select from the list of existing community names.
You can enter up to 180 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &,', and %.
Do not use a space either at the beginning or the end.
8. If you want to make changes under Send Trap to, select the Send Trap to check
box, and then perform one or more of the following steps:
■ To enter a new IP address, select IPv4 or IPv6, and then enter the IP address.
■ To use an existing IP address, select from the list of existing IP addresses.
■ To add more than one IP address, click Add IP Address to add additional input
elds.
■ To delete an IP address from Send Trap To, click the minus (-) button next to the
IP address.
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering
eight hexadecimal numbers that are separated by colons (:) using a
maximum of 4 digits from zero (0) to FFFF inclusive. The default form of
the IPv6 address can be specied.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 27
9. Click OK.
The IP address and community you entered are changed in the Registered Sending
Trap Settings table.
10. Click Finish.
11. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Changing trap notification for SNMP v3
This topic describes the procedure to change the IP addresses and users for SNMP v3
trap notication.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v3.
6. Under Registered Sending Trap Settings, select the trap setting you want to
change, and then click Change.
The Change Sending Trap Setting window opens.
7. If you want to make changes under Send Trap to, select the Send Trap to check
box, select IPv4 or IPv6, and then enter an IP address.
Changing trap
notication for SNMP v3
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering 8
hexadecimal numbers that are separated by colons (:) using a maximum
of 4 digits from zero (0) to FFFF inclusive. The default form of the IPv6
address can be specied.
8. If you want to change the User Name, select the User Name check box, and then
enter a user name.
You can enter up to 32 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &, and %.
Do not use a space either at the beginning or the end.
9. If you want to make changes under Authentication, select the Authentication
check box, and then select whether to Enable or Disable authentication.
If you select Enable, perform the following steps:
a. To change the Protocol, select the Protocol check box, and then select an
authentication type.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 28
Deleting SNMP trap
b. To change the Password, select the Password check box, and then enter a
password.
10. If you want to make changes under Encryption, select the Encryption check box,
and then select whether to Enable or Disable encryption.
Note: If you select Disable for Authentication, Encryption is
automatically disabled.
If you select Enable, perform the following steps:
a. To change the Protocol, select the Protocol check box, and then select an
encryption type.
b. To change the Key, select the Key check box, enter a key, and then enter the
key again under Re-enter Key for conrmation.
11. Click OK.
The IP address and user you entered are changed in the Registered Sending Trap
Settings table.
12. Click Finish.
13. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
notication
Deleting SNMP trap notification
This topic describes the procedure to delete IP addresses and communities or users
from SNMP trap notication.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select your SNMP version.
6. Under Registered Sending Trap Settings, select one or more specic combinations
of IP address and community or user, and then click Delete.
7. Click Finish.
8. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 29
Managing SNMP request authentication
Managing SNMP request authentication
Use the procedure for the SNMP version you use to set SNMP request authentication.
The items to specify are dierent depending on the SNMP version.
Adding request authentication for SNMP v1 and SNMP v2c
This topic describes how to add IP addresses and communities for request
authentication for SNMP v1 and SNMP v2c.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v1 or v2c.
6. Under Registered Request Authentication Settings, click Add.
7. In the Add Request Authentication Setting window, under Community, enter a
community name or select from the list of existing community names.
You can enter up to 180 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &,', and %.
Do not use a space either at the beginning or the end.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 30
Adding request authentication for SNMP v3
8. Under Request Permitted, complete one of the following steps:
■ If you want to allow REQUEST operations from all managers, select the All check
box.
■ If you want to allow REQUEST operations only from specied managers, perform
one or more of the following steps:
- To enter a new IP address, select IPv4 or IPv6, and then enter the IP address.
- To use an existing IP address, select from the list of existing IP addresses.
- To add more than one IP address, click Add IP Address to add additional input
elds.
- To delete an IP address from Send Trap To, click the minus (-) button next to the
IP address.
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering
eight hexadecimal numbers that are separated by colons (:) using a
maximum of 4 digits from zero (0) to FFFF inclusive. The default form
of the IPv6 address can be specied.
9. Click OK
The community and IP address that you entered are added to the Registered
Request Authentication Settings table.
10. Click Finish.
11. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Adding request authentication for SNMP v3
This topic describes how to add users for SNMP v3 request authentication.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v3.
6. Under Registered Request Authentication Settings, click Add.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 31
Changing request authentication for SNMP v1 and SNMP v2c
7. In the Add Request Authentication Setting window, under User Name, enter a
user name.
You can enter up to 32 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &, and %.
Do not use a space either at the beginning or the end.
8. Under Authentication, select whether to Enable or Disable authentication.
If you select Enable, complete the following steps:
a. For Protocol, select an authentication type.
b. For Password, enter a password.
9. Under Encryption, select whether to Enable or Disable encryption.
Note: If you select Disable for Authentication, Encryption is
automatically disabled.
If you select Enable, complete the following steps:
a. For Protocol, select an encryption type.
b. For Key, enter a key.
c. For Re-enter Key, enter the same key for conrmation.
10. Click OK.
The user you entered is added to the Registered Request Authentication
Settings table.
11. Click Finish.
12. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Changing request authentication for SNMP v1 and SNMP v2c
This topic describes how to change IP addresses and communities for request
authentication for SNMP v1 and SNMP v2c.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v1 or v2c.
6. Under Registered Request Authentication Settings, select the authentication
setting you want to change, and then click Change.
The Change Request Authentication Setting window opens.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 32
Changing request authentication for SNMP v3
7. If you want to make changes under Community, select the Community check box,
and then enter a community name or select from the list of existing community
names.
You can enter up to 180 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &,', and %.
Do not use a space either at the beginning or the end.
8. If you want to make changes under Request Permitted, select the Request
Permitted check box, and then complete one of the following steps:
■ If you want to allow REQUEST operations from all managers, select the All check
box.
■ If you want to allow REQUEST operations only from specied managers, perform
one or more of the following steps:
- To enter a new IP address, select IPv4 or IPv6, and then enter the IP address.
- To use an existing IP address, select from the list of existing IP addresses.
- To add more than one IP address, click Add IP Address to add additional input
elds.
- To delete an IP address from Send Trap To, click the minus (-) button next to the
IP address.
Note: Any IP address that has all values set to zero (0) cannot be
specied for IPv4 and IPv6. The IPv6 address is specied by entering 8
hexadecimal numbers that are separated by colons (:) using a
maximum of 4 digits from zero (0) to FFFF inclusive. The default form
of the IPv6 address can be specied.
9. Click OK.
The community and IP address that you entered are changed in the Registered
Request Authentication Settings table.
10. Click Finish.
11. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Changing request authentication for SNMP v3
This topic describes how to change users and authentication settings for SNMP v3
request authentication.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 33
Deleting SNMP request authentication
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select v3.
6. Under Registered Request Authentication Settings, click Change.
The Change Request Authentication Setting window opens.
7. If you want to change the User Name, select the User Name check box, and then
enter a user name.
You can enter up to 32 alphanumeric characters. The following special characters
are not allowed: ", \, ;, :, ,, *, ?, <, >, |, /, ^, &, and %.
Do not use a space either at the beginning or the end.
8. If you want to make changes under Authentication, select the Authentication
check box, and then select whether to Enable or Disable authentication.
If you select Enable, perform the following steps:
a. To change the Protocol, select the Protocol check box, and then select an
authentication type.
b. To change the Password, select the Password check box, and then enter a
password.
9. If you want to make changes under Encryption, select the Encryption check box,
and then select whether to Enable or Disable encryption.
Note: If you select Disable for Authentication, Encryption is
automatically disabled.
If you select Enable, perform the following steps:
a. To change the Protocol, select the Protocol check box, and then select an
encryption type.
b. To change the Key, select the Key check box, enter a key, and then enter the
key again under Re-enter Key for conrmation.
10. Click OK.
The user you entered is added to the Registered Request Authentication
Settings table.
11. Click Finish.
12. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Deleting SNMP request authentication
This topic describes how to delete IP addresses and communities or users from request
authentication.
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 34
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Under SNMP Agent, click Enable.
5. Under SNMP Version, select your SNMP version.
6. Under Registered Request Authentication Settings, select one or more specic
combinations of IP address and community or user, and then click Delete.
7. Click Finish.
8. In the Conrm window, enter a name for the task, conrm the settings, and then
click Apply.
Testing the SNMP trap report
This topic describes the procedure to test the SNMP trap report.
Testing the SNMP trap report
Before you begin
You must have the Storage Administrator (Initial Conguration) role to perform this task.
For more information, see the System Administrator Guide.
Procedure
1. Display the Device Manager - Storage Navigator main window.
2. From the Settings menu, select Environmental Setting > Edit Alert Settings.
3. Select the SNMP tab.
4. Click Send Test SNMP Trap.
Reports the test SNMP trap to the IP address registered in the storage system.
Reports the events registered in the storage system instead of the events that are
set on the SNMP tab. If you want to test the events set on the SNMP tab, click
Finish and apply to the storage system, and then report the test SNMP trap.
5. Verify whether the SNMP trap report (reference code 7f) is received by the SNMP
manager registered in the community.
Chapter 4: Setting SNMP
Hitachi Alert Notication Guide for VSP5000 Series 35
Chapter 5: Troubleshooting
This chapter provides troubleshooting information for the Hitachi SNMP Agent.
Solving SNMP problems
This topic describes some problems that can occur with SNMP. You should install a
secondary SVP. Otherwise, traps could be reported to an IP address that is not specied
in SNMP settings.
The following problems can occur:
SNMP security function
If the SNMP security function is working, and a command is executed from an IP
address that is not entered, you will get a "no reply" return, and a certication
error is received for a trap.
SNMP cold trap function
■
Depending on your network environment, you might not receive SNMP agent
cold traps when the SVP is rebooted.
■
The SNMP agent might report Link up/Link down Trap when the SVP reboots.
■
A number of Link up/Link down Traps may be reported when the SVP OS is
Windows 7.
Abnormal response to SNMP command
If an error occurs in the SVP, traps might not be sent.
Problems inputting MIB denition les
If you cannot input two or more MIB denition les because of the specications
of the SNMP manager software, use the MIB denition les for your storage
system. Error reports include storage system nicknames, which can be used to
identify each storage system.
Chapter 5: Troubleshooting
Hitachi Alert Notication Guide for VSP5000 Series 36
Chapter 6: SNMP overview
This chapter provides an overview of the SNMP implementation for monitoring Hitachi
Virtual Storage Platform 5000 series storage systems, including the agent and
management functions.
SNMP Manager overview
SNMP Manager is installed in the network management station. It collects and manages
information from SNMP agents installed in the managed devices on the network.
The SNMP Manager graphically displays information collected from two or more SNMP
agents, accumulates the information in the database, and analyzes problems discovered
while accumulating this information.
Note:
■
SNMP versions v1, v2c, and v3 are supported.
■
An RFC-compliant encryption algorithm is adopted for User-based Security
Model (USM) authentication.
How SNMP works
Simple Network Management Protocol (SNMP) is an industry-standard protocol for
managing and monitoring network devices, including disk devices, routers, and hubs.
SNMP uses Simple Gateway Management Protocol (SGMP) to manage TCP/IP gateways.
The following gure shows an example SNMP environment.
Chapter 6: SNMP overview
Hitachi Alert Notication Guide for VSP5000 Series 37
Management Information Base overview
An SNMP manager monitors the devices, which are referred to as managed nodes.
Typically, an SNMP Manager polls the SNMP agents on a periodic basis. The manager
receives the reports from the agents and determines whether the devices are operating
normally. If an abnormal event occurs, an SNMP Agent can report the condition without
a request from the manager, by using a trap message.
When an SNMP manager polls an agent, the following dialogue takes place:
■
An SNMP Manager sends a request packet to an SNMP Agent, which requests data
regarding the status of the managed node.
■
The SNMP Agent sends a response packet back to the SNMP Manager.
■
SNMP uses the TCP/IP User Datagram Protocol (UDP). If the SNMP Agent does not
respond within a specied time period, the SNMP Manager re-sends the request
packet. That time period is set by the system administrator, taking into account the
network trac and operation policy.
■
If an SNMP Agent again does not respond to the resent packet, the SNMP Manager
assumes that an error has occurred. Depending on the times set for polling and
response, this dialogue can take several seconds.
If an SNMP Agent detects an abnormal event, it sends a trap to the SNMP Manager.
However, if a trap is dropped in transmission, the SNMP Manager does not know that it
was sent. For this reason, you should use both polling and traps to determine whether
an abnormal event has occurred.
Management Information Base overview
The standardized conguration and database of network management information is
called a Management Information Base (MIB). A standard MIB is common to all SNMP
interfaces. An extension MIB is dened by the particular managed device or protocol.
A MIB is a collection of standardized conguration and network management
information that is contained in each device on the network. Each MIB contains a set of
parameters called managed objects. Each managed object consists of a parameter
name, one or more parameters, and a group of operations that can be executed with the
object. The MIB denes the type of information that can be obtained from a managed
device, and the device settings that can be controlled from a management system.
The MIB denition le, VSP5KMIB.txt, is located in the program\SNMP folder of the
software media kit.
SNMP Agent configuration
The SNMP Agent is installed on the service processor (SVP), which is the computer within
the storage system that manages the storage system.
The storage system has an exclusive LAN for communications with the SVP and a
separate LAN for SNMP. The conguration of each Network Management Station is
determined by the type of SNMP manager.
The following gure illustrates the SNMP environment.
Chapter 6: SNMP overview
Hitachi Alert Notication Guide for VSP5000 Series 38
SNMP Agent overview
The following gure shows an example of SNMP operations using an SNMP manager.
SNMP Agent overview
The SNMP Agent is mounted on a managed device (such as a hard disk) in the network. It
collects error information, the usage condition, and other information about the device,
and forwards the information to the SNMP Manager.
The SNMP Agent reports disk storage system failures to the manager using the SNMP
trap function.
SNMP traps
An SNMP Agent reports storage system errors to the SNMP Manager using the SNMP
trap function.
When an error occurs, the SNMP Agent issues an SNMP trap to the SNMP Manager that
includes the product number, nickname, reference code, and an identier of the
component.
Hitachi Alert Notication Guide for VSP5000 Series 39
Chapter 6: SNMP overview
SNMP Agent operations
The following table lists the types of events that trigger an SNMP Agent trap.
Events Description
Acute failure detected. All operations in a storage system stopped.
Serious failure detected. Operation in a component where a failure occurred
stopped.
Moderate failure
detected.
Service failure detected. Minor failure.
An SNMP Agent logs the most recent 10,000 traps, so you can see the trap history of a
particular device.
SNMP Agent operations
Operations that an SNMP Agent can perform fall into the categories GET REQUEST,
GETNEXT REQUEST, GETBULK REQUEST, and TRAP.
The following table describes the types of SNMP Agent operations.
Operation Description
GET
REQUEST
GETNEXT
REQUEST
Obtains a specic MIB object value.
GET REQUEST is the request from an SNMP Manager, and GET RESPONSE
is the agent's response to that request.
Continuously nds a MIB object.
GETNEXT REQUEST is the request from an SNMP Manager, and GET
RESPONSE is the agent's response to that request.
Partial failure.
GETBULK
REQUEST
TRAP Reports an event (failure) to an SNMP Manager.
Continuously nds specied MIB objects only.
GETBULK REQUEST is the request from an SNMP Manager, and GET
RESPONSE is the agent's response to that request.
TRAP occurs without a request from the SNMP Manager.
SNMP Agent reported errors
Several dierent types of errors can be reported when GET REQUEST, GETNEXT
REQUEST, and GETBULK REQUEST operations are sent to an SNMP Agent.
The following table describes the errors that can be reported and suggests corrective
action.
Chapter 6: SNMP overview
Hitachi Alert Notication Guide for VSP5000 Series 40
Component status information from SNMP Manager
Error Description Corrective action
noError (0) Normal N/A
noSuchName
(2)
■
There are no MIB objects that are
required. (Not supported.)
■
The GETNEXT REQUEST command
Verify that the name of the
requested object is correct.
that is specied for the following
object identier of the last supported
MIB object is received.
SET REQUEST is received. SET REQUEST operation is
not supported.
genErr (5) Error occurred for other reasons. Retry the operation.
Component status information from SNMP Manager
You can obtain the status information of certain storage system components from the
SNMP Manager.
The following table lists the components for which the status can be obtained.
Area Component name
Storage System Processors
BUS
Cache
Shared memory
Power supplies
Batteries
Fans
Others
Disk Unit Power supplies
Fans
Environments
Drives
Chapter 6: SNMP overview
Hitachi Alert Notication Guide for VSP5000 Series 41
Component status information from SNMP Manager
The following table lists the status of storage system components, as well as the trap
report functions.
Status Description
Normal Normal operation.
Acute failure detected All operations in a storage system stopped.
Serious failure detected Operation in a component where a failure occurred
stopped.
Moderate failure
detected
Service failure detected Minor failure.
Partial failure.
Chapter 6: SNMP overview
Hitachi Alert Notication Guide for VSP5000 Series 42
Chapter 7: SNMP supported MIBs
You can use the SNMP supported MIBs reference to nd information on the standard
and extension MIB specications, and trap conguration.
SNMP Agent failure report trap contents
A standard extension trap protocol data unit (PDU) includes the product number of the
device that experienced the failure, the device nickname, and a failure reference code. A
failure report trap contains additional information about the failure, such as the area,
date, and time of the failure.
If you obtain the information with the GetRequest command, access the MIB by using
the product number of the device as an index.
The following table shows the failure report trap.
Name Object identifier Type Description
eventTrapSerial
Number
eventTrapNickn
ame
eventTrapREFCODE.1.3.6.1.4.1.116.5.11.4.2.3 DisplayString The failure
eventTrapPartsID.1.3.6.1.4.1.116.5.11.4.2.4 OBJECT
eventTrapDate .1.3.6.1.4.1.116.5.11.4.2.5 DisplayString Failure occurrence
eventTrapTime .1.3.6.1.4.1.116.5.11.4.2.6 DisplayString Failure occurrence
eventTrapDescri
ption
.1.3.6.1.4.1.116.5.11.4.2.1 INTEGER The product
number of the
device that
experienced the
failure.
.1.3.6.1.4.1.116.5.11.4.2.2 DisplayString The device
nickname .
reference code.
The area where
IDENTIFIER
.1.3.6.1.4.1.116.5.11.4.2.7 DisplayString Detailed
the failure
occurred.*
date.
time.
information of a
failure.
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 43
Name Object identifier Type Description
*The object identier for a failure in a storage system processor would be
.1.3.6.1.4.1.116.5.11.4.1.1.6.1.2.
SNMP Agent extension trap types
SNMP Agent extension trap types are set according to the severity. The character strings
following "RaidEventUser" indicate their severity.
The following table describes the SNMP Agent extension trap types.
Specific Trap
Code Trap Description
1 RaidEventUserAcute All operations in a storage system stopped.
SNMP Agent extension trap types
2 RaidEventUserSerious Operation in a component where a failure
3 RaidEventUserModerate Partial failure.
4 RaidEventUserService Minor failure.
Standard MIB specifications
MIBs supported by SNMP Agent
SNMP Agent supports a limited number of MIBs. If you send a GET request for an object
(MIB) that is not supported, you will receive NoSuchName as a GET RESPONSE.
The following table lists MIBs and indicates whether they are supported.
MIB Supported?
Standard MIB: MIB-II system group Yes
occurred stopped.
interface group No
at group No
ip group No
icmp group No
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 44
MIB Supported?
Extension MIB Yes
SNMP Agent MIB access mode
The access mode for MIB in all communities is read only. If you send a GET request for a
SET REQUEST operation, you will receive NoSuchName as a RESPONSE.
Example object identifier system
SNMP Agent MIB access mode
tcp group No
udp group No
egp group No
snmp group No
The following gure shows an example object system supported by SNMP Agent.
Execute snmpwalk as follows to obtain all MIB objects:
1. Specify object identier 1.3.6.1.2.1 to obtain the information shown in 1.
2. Specify object identier 1.3.6.1.4.1.116 to obtain the information shown in 2.
MIB mounting specifications supported by SNMP Agent
SNMP Agent supports two MIB mounting specications.
The supported MIB mounting specications are as follows:
■
mgmt OBJECT IDENTIFIER ::= {iso(1) org(3) dod(6) internet(1) 2 }
■
mib-2 OBJECT IDENTIFIER ::= {mgmt 1}
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 45
Extension MIB
specications
An SNMP Agent mounts only system groups in mib-2, as shown in the following table.
Name Description Mounted value
sysObjectID
{system 2}
This is the product
identication number.
Fixed value. See Object identier system
(on page 45) .
1.3.6.1.4.1.116.3.11.4.1.1
sysUpTime
{system 3}
sysContact
{system 4}
An accumulated time from
an SNMP agent.
A manager who manages an
agent or a contact address.
Unit: 100 ms
Maximum 180 characters in an ASCII
characters string. Input by a user from an
SNMP setting window.*
sysName
{system 5}
The name of an agent
manager
Maximum 180 characters in an ASCII
characters string. Input by a user from an
SNMP setting window.*
sysLocation
{system 6}
An agent setup location. Maximum 180 characters in an ASCII
characters string. Input by a user from an
SNMP setting window.*
sysService
Value indicating a service. Fixed value 76 (decimal)
{system 7}
*The following symbols cannot be used: \ , / : ; * ? " < > | & % ^
Extension MIB specifications
Extension MIB configuration
The following shows the extension MIB object system for the storage system.
raidExMibRoot(1)
├-raidExMibName(1) SVP product name
├-raidExMibVersion(2) SVP Micro-program version
├-raidExMibAgentVersion(3) Extension MIB internal version
├-raidExMibDkcCount(4) Number of DKC under the control of SVP
├-raidExMibRaidListTable(5) List of DKC under the control of SVP
├-raidExMibDKCHWTable(6) Disk control device information
├-raidExMibDKUHWTable(7) Disk device information
├-raidExMibTrapListTable(8) Error information list
The following gures show an example extension MIB conguration.
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 46
Extension MIB conguration
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 47
raidExMibName
raidExMibName
raidExMibName indicates the SVP product name.
raidExMibName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "SVP product name."
::={ raidExMibRoot 1 }
raidExMibVersion
raidExMibVersion indicates the micro-program version.
raidExMibVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "SVP Micro-program version."
::= { raidExMibRoot 2 }
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 48
raidExMibAgentVersion
raidExMibAgentVersion indicates the internal version of the extension MIB.
raidExMibAgentVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "Extension agent version."
::= { raidExMibRoot 3 }
raidExMibDkcCount
raidExMibDkcCount suggests the number of a storage system under the control of the
SVP.
raidExMibDkcCount OBJECT TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION "Number of DKC which is registered
on the SVP"
::={ raidExMibRoot 4}
raidExMibAgentVersion
raidExMibRaidListTable
raidExMibRaidListTable indicates the storage system under the control of the SVP.
raidExMibRaidListTable OBJECT TYPE
SYNTAX SEQUENCE OF raidExMibRaidListEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "List of DKC which is registered
on the SVP."
::={ raidExMibRoot 5}
raidExMibRaidListEntry OBJECT TYPE
SYNTAX RaidExMibRaidListEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Entry of DKC list."
INDEX { raidlistSerialNumber }
::={ raidExMibRaidListTable 1}
The following table lists the information displayed for each storage system
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 49
Name Type Description
raidExMibDKCHWTable
Mounted
value Attribute
raidlistSerialNumber
::=RaidExMibRaidListEntr
y(1)
raidlistMibNickName
::=RaidExMibRaidListEntr
y(2)
raidlistDKCMainVersion
::=RaidExMibRaidListEntr
y(3)
raidlistDKCProductName
::=RaidExMibRaidListEntr
y(4)
* VSP5000 will be used as storage system product type raidlistDKCProductName.
raidExMibDKCHWTable
raidExMibDKCHWTable indicates the status of the storage system components.
INTEGER Storage system
product number
(index).
DisplaySt
ring
DisplaySt
ring
DisplaySt
ring
Storage system
nickname.
Microcode
version.
Storage system
product type.
1 - 99,999 read-only
(Max. 18
read-only
characters)
Max. 10
read-only
characters
7
read-only
characters*
raidExMibDKCHWTable OBJECT TYPE
SYNTAX SEQUENCE OF RaidExMibDKCHWEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Error information of the DKC."
::={ raidExMibRoot 6}
raidExMibDKCHWEntry OBJECT TYPE
SYNTAX RaidExMibDKCHWEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Entry of DKC information."
INDEX {dkcRaidListIndexSerialNumber}
::={ raidExMibDKCHWTable 1}
The following table lists the information displayed for each storage system component.
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 50
raidExMibDKCHWTable
Name Type Description MIB value Attribute
dkcRaidListIndexSerialNu
mber
::=raidExMibDKCHWEntr
y(1)
dkcHWProcessor
::=raidExMibDKCHWEntr
y(2)
dkcHWCSW
::=raidExMibDKCHWEntr
y(3)
dkcHWCache
::=raidExMibDKCHWEntr
y(4)
dkcHWSM
::=raidExMibDKCHWEntr
y(5)
dkcHWPS
::=raidExMibDKCHWEntr
y(6)
INTEGER Storage system
product number
(index).
INTEGER Status of processor. See Note read-only
INTEGER Status of internal star. See Note read-only
INTEGER Status of cache. See Note read-only
INTEGER Status of shared
memory.
INTEGER Status of power
supply.
1 - 99,999 read-only
See Note read-only
See Note read-only
dkcHWBattery
::=raidExMibDKCHWEntr
y(7)
dkcHWFan
::=raidExMibDKCHWEntr
y(8)
dkcHWEnvironment
::=raidExMibDKCHWEntr
y(9)
Note:
The status of each component is a single digit which shows the following:
1: Normal.
2: Acute failure detected.
3: Serious failure detected.
4: Moderate failure detected.
INTEGER Status of battery. See Note read-only
INTEGER Status of fan. See Note read-only
INTEGER Information of an
operational
environment.
See Note read-only
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 51
Name Type Description MIB value Attribute
5: Service failure detected.
raidExMibDKUHWTable
raidExMibDKUHWTable indicates the status of the storage system components.
raidExMibDKUHWTable OBJECT TYPE
SYNTAX SEQUENCE OF RaidExMibDKUHWEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Error information of the DKU."
::={ raidExMibRoot 7}
raidExMibDKUHWEntry OBJECT TYPE
SYNTAX RaidExMibDKUHWEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Entry of DKU information."
INDEX { dkuRaidListIndexSerialNumber }
::={ raidExMibDKUHWTable 1}
raidExMibDKUHWTable
The following table lists the information displayed for each disk device component.
MIB
Name Type Description
dkuRaidListIndexSerialNum
ber
INTEGERStorage system product
number (index).
value Attribute
1 -
read-only
99,999
::=raidExMibDKUHWEntry(1
)
dkuHWPS
INTEGERStatus of power supply. See Note read-only
::=raidExMibDKUHWEntry(2
)
dkuHWFan
INTEGERStatus of fan. See Note read-only
::=raidExMibDKUHWEntry(3
)
dkuHWEnvironment
::=raidExMibDKUHWEntry(4
INTEGERStatus of environment
monitor.
See Note read-only
)
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 52
Name Type Description
raidExMibTrapListTable
MIB
value Attribute
dkuHWDrive
::=raidExMibDKUHWEntry(5
)
Note:
The status of each component is a single digit which shows the following:
1: Normal.
2: Acute failure detected.
3: Serious failure detected.
4: Moderate failure detected.
5: Service failure detected.
raidExMibTrapListTable
raidExMibTrapListTable shows the history of the failure traps.
raidExMibTrapListTable OBJECT TYPE
SYNTAX SEQUENCE OF RaidExMibTrapListEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Trap list table."
::={ raidExMibRoot 8 }
INTEGERStatus of drive. See Note read-only
raidExMibTrapListEntry OBJECT TYPE
SYNTAX RaidExMibTrapListEntry
ACCESS non-accessible
STATUS mandatory
DESCRIPTION "Trap list table index."
INDEX { eventListIndexSerialNumber ,
eventListIndexRecordNo }
::={ raidExMibTrapListTable 1 }
The following table lists the information displayed for each failure.
Name
eventListIndexSerialNu
mber
Type Description MIB value Attribute
INTEGER Storage system
1 - 99,999 read-only
product number
(index).
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 53
Name Type Description MIB value Attribute
::=raidExMibTrapListEn
try(1)
raidExMibTrapListTable
eventListNickname
::=raidExMibTrapListEn
try (2)
eventListIndexRecord
No
::=raidExMibTrapListEn
try (3)
eventListREFCODE
::=raidExMibTrapListEn
try (4)
eventListData
::=raidExMibTrapListEn
try (5)
eventListTime
::=raidExMibTrapListEn
try (6)
eventListDescription
::=raidExMibTrapListEn
try (7)
DisplaySt
ring
Counter Number of
DisplaySt
ring
DisplaySt
ring
DisplaySt
ring
DisplaySt
ring
Storage system
nickname.
records.
Reference code
(index).
Date when the
failure occurred.
Time when the
failure occurred.
Detailed
information
about the
failure.
18 characters
maximum
1-256 read-only
6 characters read-only
yyyy/mm/dd
(10 characters)
hh:mm:ss
(8 characters)
256 characters
maximum
read-only
read-only
read-only
read-only
Chapter 7: SNMP supported MIBs
Hitachi Alert Notication Guide for VSP5000 Series 54
Chapter 8: SIM codes
You can use the failure trap reference to identify trap reference codes (SIM codes) to see
what section it aects and the alert levels.
Failure trap reference codes
The following table lists and describes the failure trap reference codes.
For details on alert levels, see the System Administrator Guide.
Trap reference
code
SIM22SIM23SIM
13
Description Section Alert level
Host
report
1
18 00 00 AuditLog lost DKC
environme
nt
21 20 xx Channel port blocking Processor MODERATEYes
21 60 xx HIE blocking Cache MODERATEYes
21 61 xx ISW blocking Cache MODERATEYes
21 62 xx X path blocking Cache MODERATEYes
21 63 xx HIE warning Cache MODERATEYes
21 64 xx X path warning Cache MODERATEYes
21 80 xx Logical path(s) on the remote
copy connections was logically
blocked (Due to an error
condition)
Processor MODERATEYes
MODERATEYes
2
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 55
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
21 81 xx RIO PATH AUTOMATICALLY
Processor SERVICE Yes
RECOVERED
21 90 xx AL_PA VALUE CONFLICT Processor SERVICE No
21 93 xx LINK FAILURE Processor SERIOUS Yes
21 94 xx LINK FAILURE2 Processor SERIOUS Yes
21 a3 xx HTP blocking Processor MODERATEYes
21 a4 xx Fiber Cable Failure Processor SERVICE No
21 a8 xx SFP wrong type Processor MODERATENo
21 aa xx SFP TxFault Processor MODERATENo
21 bx xx HTP hard error Processor MODERATEYes
21 d0 xx External storage system
Processor MODERATEYes
connection path blocking
21 d1 xx External storage system
Processor SERVICE No
connection path restore
21 d2 xx Threshold over by external
Processor SERVICE Yes
storage system connection
path response time-out
21 d4 xx Blocking the Data Migration
Processor MODERATENo
path
21 d5 xx Data Migration Path Recovery Processor SERVICE No
30 70 xx CHK1A THRESHOLD OVER Processor SERVICE No
30 71 xx CHK1B THRESHOLD OVER Processor SERVICE No
30 72 xx CHK3 THRESHOLD OVER Processor SERVICE No
30 73 xx PROCESSOR BLOCKING Processor MODERATEYes
30 75 xx FM ERROR Processor MODERATEYes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 56
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
30 76 xx Incorrect SUM value of FM Processor SERVICE No
1
30 77 xx PROCESSOR MEMORY
Processor SERVICE No
TEMPORARY ERROR
30 80 xx WCHK1 dump Processor MODERATENo
30 a1 00 DKC Blockade Processor ACUTE Yes
38 8f 00 P/S OFF IMPOSSIBLE PS(DKC) MODERATENo
38 9f 00 P/S OFF IMPOSSIBLE(DEVICE
PS(DKC) MODERATENo
RESERVED)
39 90 xx Undened Package is
Processor MODERATENo
mounted
39 91 xx V-R OR SERIAL NUMBER IS
Processor MODERATENo
INCONSISTENT
39 93 xx REPLACE FAILED Processor MODERATENo
39 9d xx Injustice DC voltage control Processor MODERATEYes
39 9e xx Injustice CEMODE Processor MODERATEYes
39 9f xx Injustice CEDT Processor MODERATEYes
39 b0 xx SMA SLAVE ERROR Processor SERVICE No
39 b2 00 CPU frequency setting failure Processor SERVICE No
3a 0x xx LDEV Blockade (Eect of
Processor MODERATEYes
microcode error)
3c 95 00 CHB/DKB Type disagreement Processor MODERATENo
3c 97 xx iSCSI rmware update warning Processor MODERATEYes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 57
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
3c cd xx CHA Injustice dc voltage
Processor MODERATENo
control
3c ce xx CHA temperature abnormality Processor MODERATENo
3d cd xx DKA Injustice dc voltage
Processor MODERATENo
control
3d ce xx DKA temperature abnormality Processor MODERATENo
41 00 xx Format complete Drive SERVICE No
41 01 00 Quick Format nish Drive SERVICE No
43 4x xx DRIVE MEDIA ERROR
6
Drive SERVICE No
43 5x xx Drive media error Drive SERVICE Yes
43 ax xx Drive blockade (media)(with
Drive SERIOUS Yes
redundancy)
43 bx xx Drive blockade (media)(with
redundancy)
6
Drive SERIOUS Yes
43 cx xx Drive blockade (media)
(without redundancy)
6
43 dx xx Drive blockade (media)
(without redundancy)
45 1x xx CORRECTION COPY START
6
45 2x xx CORRECTION COPY NORMAL
6
END
45 3x xx CORRECTION COPY
ABNORMAL END
6
45 4x xx CORRECTION COPY
DISCONTINUED
6
45 5x xx Correction copy warning
end(With blockade LDEV or
some error)
6
Drive SERIOUS Yes
Drive SERIOUS Yes
Drive SERVICE Yes
Drive SERVICE Yes
Drive SERIOUS Yes
Drive SERVICE No
Drive SERVICE Yes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 58
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
46 1x xx DYNAMIC SPARING(DRIVE
COPY)START
6
46 2x xx DYNAMIC SPARING(DRIVE
COPY)NORMAL END
6
46 3x xx DYNAMIC SPARING(DRIVE
COPY)ABNORMAL END
6
46 4x xx DYNAMIC SPARING(DRIVE
COPY)DISCONTINUED
6
46 5x xx Dynamic sparing warning
end(With blockade LDEV or
some error)(Drive copy)
6
46 8x xx Collection Copy/Copyback
disabled(drive replace)
46 9x xx Collection Copy/Copyback
disabled(drive replace)
46 ax xx Drive Copy/Correction Copy
delay
Drive SERVICE Yes
Drive SERVICE Yes
Drive MODERATEYes
Drive SERVICE No
Drive SERVICE Yes
Drive MODERATENo
Drive MODERATENo
Drive MODERATEYes
46 bx xx Drive Copy/Correction Copy
Drive MODERATEYes
delay
47 dx xx SIMF/SI Copy abnormal end Failure
with paired
volumes
47 e5 00 All FlashCopy(R) Option
abnormal end by SM volatile
Failure
with paired
volumes
47 e7 00 Forcible suspend by SM
volatile (SIMF/SI)
Failure
with paired
volumes
47 ec 00 Thin Image ABNORMAL END
BY SM VOLATILE
Failure
with paired
volumes
47 fx xx Volume Migration Abnormal
End
Volume
Migration
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATENo
3
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 59
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
49 10 00 CACHE WRITE PENDING RATIO
Cache SERVICE No
IS OVER 65%
4a 80 xx Expander Micro Exchange
Processor MODERATENo
failed
4b 2x xx Compatible FlashCopy(R)
ABNORMAL END
Failure
with paired
volumes
4b 3x xx Thin Image ABNORMAL END Failure
with paired
volumes
4b 4x xx FlashCopy(R) Hierarchical
memory access error
Failure
with paired
volumes
4b 6x xx Correction copy start Failure
with paired
volumes
4b 7x xx Correction copy start Failure
with paired
volumes
MODERATEYes
MODERATEYes
MODERATEYes
SERVICE Yes
SERVICE Yes
4b 8x xx Correction copy normal end Failure
with paired
volumes
4b 9x xx Correction copy normal end Failure
with paired
volumes
4b ax xx Correction copy abnormal end Failure
with paired
volumes
4b bx xx Correction copy abnormal end Failure
with paired
volumes
4b cx xx Correction copy discontinued Failure
with paired
volumes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 60
SERVICE Yes
SERVICE Yes
SERIOUS Yes
SERIOUS Yes
SERVICE No
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
4b dx xx Correction copy discontinued Failure
SERVICE No
with paired
volumes
4b ex xx Correction copy warning end
(With blockade LDEV or some
error)
4b fx xx Correction copy warning end
(With blockade LDEV or some
error)
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
4c 10 xx PDEV Erase Start Drive SERVICE No
4c 20 xx PDEV Erase Normal End Drive SERVICE No
4c 30 xx PDEV Erase Abnormal End Drive SERVICE No
4c 4x xx Flash module drive
Drive MODERATEYes
initialization failed
4c 5x xx Flash module drive
Drive MODERATEYes
initialization failed
4c 6x xx Dynamic sparing start (Drive
Drive SERVICE Yes
copy)
4c 7x xx Dynamic sparing start (Drive
copy)
4c 8x xx Dynamic sparing normal end
(Drive copy)
4c 9x xx Dynamic sparing normal end
(Drive copy)
4c ax xx Dynamic sparing abnormal
end (Drive copy)
4c bx xx Dynamic sparing abnormal
end (Drive copy)
4c cx xx Dynamic sparing discontinued
(Drive copy)
4c dx xx Dynamic sparing discontinued
(Drive copy)
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 61
Drive SERVICE Yes
Drive SERVICE Yes
Drive SERVICE Yes
Drive MODERATEYes
Drive MODERATEYes
Drive SERVICE No
Drive SERVICE No
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
4c ex xx Dynamic sparing warning end
Drive SERVICE Yes
(With blockade LDEV or some
error) (Drive copy)
4c fx xx Dynamic sparing warning end
Drive SERVICE Yes
(With blockade LDEV or some
error) (Drive copy)
4d 1x xx Dierential area blocking Drive SERIOUS Yes
4d 6x xx PDEV Erase Start Drive SERVICE Yes
4d 7x xx PDEV Erase Start Drive SERVICE Yes
4d 8x xx PDEV Erase Normal End Drive SERVICE Yes
4d 9x xx PDEV Erase Normal End Drive SERVICE Yes
4d ax xx PDEV Erase Abnormal End Drive SERVICE Yes
4d bx xx PDEV Erase Abnormal End Drive SERVICE Yes
50 0x xx Drive temporary error Drive SERVICE No
50 1x xx DRIVE TEMPORARY ERROR Drive SERVICE No
50 2x xx DRIVE MEDIA ERROR
6
Drive SERVICE No
50 3x xx Drive media error Drive SERVICE No
50 ax xx Flash drive End of life Drive SERVICE Yes
50 bx xx Flash drive End of life
6
Drive SERVICE Yes
50 cx xx Flash module drive End of life6Drive SERVICE Yes
50 dx xx Flash module drive End of life Drive SERVICE Yes
50 f0 00 Flash module drive micro-
Drive MODERATENo
program version warning
60 2x xx Pool blocking Thin Image
MODERATEYes
pool
60 30 00 SM Space Warning SM MODERATEYes
60 4x xx Exceeded Threshold of pool
use rate
Thin Image
pool
MODERATEYes
4
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 62
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
60 5x xx Actual pool use rate reaches
upper limit
60 6x xx Exceeded Fixed outage
Threshold of pool use rate
61 00 xx BACKUP/RESTORE SM
Thin Image
pool
Thin Image
pool
SM MODERATENo
INFORMATION FAILED
62 3x xx The DP POOL error is detected
(XXX : Pool ID)
Dynamic
Provisionin
g pool
62 40 00 SM(DP/TI) AREA DEPLETION Dynamic
Provisionin
g pool
62 7x xx The DP POOL LDEV blockade Dynamic
Provisionin
g pool
62 80 00 DP Protect attribute setting of
DRU
Dynamic
Provisionin
g pool
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
SERIOUS Yes
SERIOUS Yes
62 9x xx Exceeded Warning Threshold
of DP pool use rate
62 ax xx DP pool use rate reaches
upper limit
62 b0 00 Threshold of DP pool use rate
remains exceeded
62 cx xx Exceeded Depletion Threshold
of DP pool use rate
62 dx xx Exceeded Fixed outage
Threshold of DPpool use rate
Dynamic
Provisionin
g pool
Dynamic
Provisionin
g pool
Dynamic
Provisionin
g pool
Dynamic
Provisionin
g pool
Dynamic
Provisionin
g pool
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 63
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
62 ex xx Exceeded DP pool depletion
threshold for TI pairs
Dynamic
Provisionin
g pool
64 1x xx Tier relocation is not
completed
Dynamic
Tiering
pool
66 01 00 No free encryption key Encryption
key
66 02 00 Remaining free encryption key
warning
66 10 xx Acquisition of encryption key
from KMS failed
66 20 xx Encryption key setting
Encryption
key
Encryption
key
Processor SERIOUS Yes
abnormality
67 00 00 Warning for depletion of cache
Thin Image MODERATEYes
management devices
68 00 xx Dedupe and compression
abnormality detect
DKC
environme
nt
MODERATEYes
SERVICE Yes
MODERATEYes
SERVICE Yes
MODERATEYes
MODERATEYes
70 xx 00 Logical inconsistency SVP failure MODERATENo
71 xx 00 Heap error SVP failure MODERATENo
72 xx 00 File error SVP failure MODERATENo
73 xx 00 LAN error SVP failure MODERATENo
74 xx xx SSVP error SVP failure MODERATEYes
75 xx 00 Windows error SVP failure MODERATENo
76 00 00 CUDG3 detected error SVP failure MODERATENo
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 64
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
76 04 00 CUDG3 detected error SVP failure MODERATENo
76 10 00 LCDG3 detected error SVP failure MODERATENo
7a 00 00 NORMAL END SVP failure SERVICE No
7a 01 00 ABNORMAL END(SVP) SVP failure SERVICE No
7a 02 00 ABNORMAL END(MP) SVP failure SERVICE No
7a 03 xx VERSION CHK ERROR SVP failure SERVICE No
7a 04 xx Sum check error SVP failure SERVICE No
1
7a 05 xx HTP patch error SVP failure SERVICE No
7a 10 00 WARNING(CONFIGURATION
SVP failure SERVICE No
INCONSISTENCY)
7a 11 00 WARNING(S-SVP BUSY) SVP failure SERVICE No
7a 12 xx Warning (HTP busy) SVP failure SERVICE No
7a 20 00 INTERNET DOWNLOAD ERROR SVP failure SERVICE No
7a 23 00 Discontinuation by the user SVP failure SERVICE No
7b 00 03 ISDN Router failure SVP failure MODERATEYes
7c 00 00 SVP reboot stop (FD Inserted) SVP failure MODERATENo
7c 01 0x Battery replacement should be
Battery SERVICE No
scheduled
7c 02 00 Audit Log failure of Host
SVP failure MODERATENo
instruction conguration
change
7c 03 00 Audit Log FTP Transfer failed SVP failure MODERATEYes
7c 04 00 Dump Tool failed SVP failure SERVICE Yes
7c 05 00 Invalid SIM data detection SVP failure SERVICE No
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 65
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
7c 08 00 Dump collection starts SVP failure SERVICE No
1
7c 09 00 Dump collection ends
SVP failure SERVICE No
normally
7c 0a 00 Dump collection ends
SVP failure SERVICE No
abnormally
7c 0b 00 Cancellation of the dump
SVP failure SERVICE No
collection completed
7e 12 xx MP Operating Ratio Error Monitor MODERATEYes
7e 20 xx Loss Of Signal Count(Fibre)
Monitor MODERATENo
Excess
7e 21 xx Bad Received Character
Monitor MODERATENo
Count(Fibre) Excess
7e 22 xx Loss Of Synchronization
Monitor MODERATENo
Count(Fibre) Excess
7e 23 xx Link Failure Count(Fibre)
Monitor MODERATENo
Excess
7e 24 xx Received EOFa Count(Fibre)
Monitor MODERATENo
Excess
7e 25 xx Discarded Frame Count(Fibre)
Monitor MODERATENo
Excess
7e 26 xx Bad CRC Count(Fibre) Excess Monitor MODERATENo
7e 27 xx Protocol Error Count(Fibre)
Monitor MODERATENo
Excess
7e 28 xx Expired Frame Count (Fibre)
Monitor MODERATENo
Excess
7e 29 xx HTP/FNP Multiplicity Excess Monitor MODERATENo
7e 2a xx FEC Un-correctable
Monitor MODERATENo
Count(Fibre) threshold
exceeded
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 66
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
7e 2c xx HTP/FNP Read Data Transfer
Monitor MODERATENo
Ratio Error
7e 2d xx HTP/FNP Write Data Transfer
Monitor MODERATENo
Ratio Error
7e 2e xx HTP/FNP Operating Ratio Error Monitor MODERATENo
7e 30 00 Read Hit Ratio Excess Monitor MODERATENo
7e 50 xx MAC CRC Error Count(iSCSI)
Monitor MODERATENo
threshold exceeded
7e 51 xx IP Error Packet Count(iSCSI)
Monitor MODERATENo
threshold exceeded
7e 52 xx IPv6 Error Packet Count(iSCSI)
Monitor MODERATENo
threshold exceeded
7e 53 xx TCP Retransmit Timer Expired
Monitor MODERATENo
Count(iSCSI) exceeded
7e 54 xx iSCSI Header Digest Error
Monitor MODERATENo
Count(iSCSI) exceeded
7e 55 xx iSCSI Data Digest Error
Monitor MODERATENo
Count(iSCSI) exceeded
7e ax xx Cache Use Ratio Error Monitor MODERATENo
7e bx xx Cache Write Pending Ratio
Monitor MODERATENo
Error
7e cx xx Cache MCU Side File Use Ratio
Monitor MODERATENo
Error
7f f1 00 TCMF/TC SVP failure SERVICE No
7f f1 02 SIMF/SI SVP failure SERVICE No
7f f1 03 URMF/UR SVP failure SERVICE No
7f f1 04 TI SVP failure SERVICE No
7f f1 05 FlashCopy(R) SVP failure SERVICE No
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 67
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
7f f1 06 Volume Migration SVP failure SERVICE No
7f f2 xx STANDBY SVP FAIL SVP failure MODERATENo
7f f3 xx SVP FAIL OVER SVP failure MODERATENo
7f f7 xx The term of validity is over License key MODERATEYes
7f f8 xx The capacity of validity is over License key MODERATEYes
1
7f f9 xx The PP is invalid by
License key MODERATEYes
assumption PP invalidity
7f fa 0x Synchronization time failure SVP failure SERVICE Yes
ac 50 xx DB power o PS(DKU) MODERATEYes
ac 60 00 DKC was set to power error
PS(DKC) MODERATENo
mode
ac 61 00 DKC was released from power
PS(DKC) SERVICE No
error mode
ac 62 00 When DKC was set to power
PS(DKC) SERVICE No
error mode, Urgent Destaging
start succeeded
ac 63 00 When DKC was set to power
PS(DKC) MODERATENo
error mode, Urgent Destaging
start failed.
af 00 xx Injustice JP Warning Environme
MODERATEYes
ntal error
af 10 xx MP Temperature abnormality
warning
Environme
ntal error
af 11 xx External temperature warning Environme
ntal error
af 12 xx External temperature alarm Environme
ntal error
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 68
MODERATEYes
MODERATEYes
MODERATEYes
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
af 13 xx Thermal monitor warning Environme
ntal error
af 20 xx DKCPS warning Environme
ntal error
af 21 xx DKCPS input voltage
abnormality
af 30 xx Environmental microcontroller
warning
af 31 xx Device movement mode
warning
af 33 xx Voltage change setting
warning
Environme
ntal error
Environme
ntal error
Environme
ntal error
Environme
ntal error
af 40 xx BKM/BKMF warning Environme
ntal error
af 41 xx Battery replacement should be
scheduled
Environme
ntal error
af 4d xx Panel switch warning Environme
ntal error
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
af 4e xx Invalid PS ON warning Environme
MODERATEYes
ntal error
af 51 xx DBPS-1 warning PS(DKU) MODERATEYes
af 52 xx DBPS-2 warning PS(DKU) MODERATEYes
af 61 xx DBPS-1 input voltage
PS(DKU) MODERATEYes
abnormality
af 62 xx DBPS-2 input voltage
PS(DKU) MODERATEYes
abnormality
af 70 00 DB External temperature
warning
af 71 00 DB External temperature
Alarm
Environme
ntal error
Environme
ntal error
MODERATEYes
MODERATEYes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 69
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
af 81 xx ENC-1 warning Environme
ntal error
af 82 xx ENC-2 warning Environme
ntal error
af b0 xx HSNBX ambient temperature
warning
Environme
ntal error
af b1 xx ISW PS warning Environme
ntal error
af b2 xx ISW FAN warning Environme
ntal error
af b3 xx ISW PS input voltage
abnormality
Environme
ntal error
af b4 xx ISW warning Environme
ntal error
af b5 xx HSNBX thermal monitor
warning
af b6 xx HSNBX PANEL JP setting
abnormality
Environme
ntal error
Environme
ntal error
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
MODERATEYes
af b7 xx HSNBX PANEL JP setting
warning
af b8 xx HSNBX PSONOFF I/F
inconsistent
Environme
ntal error
Environme
ntal error
MODERATEYes
MODERATEYes
af d1 xx Battery charge EMPTY Battery MODERATENo
af d4 xx CM Backup mounting warning Cache MODERATENo
af f0 xx SSW data disagreement DKC
MODERATENo
environme
nt
af f1 xx GUM warning Environme
MODERATEYes
ntal error
af f2 xx CFM error Processor MODERATEYes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 70
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
af f3 xx FAN warning Environme
MODERATEYes
ntal error
bf 10 1x External temperature alarm Environme
MODERATEYes
ntal error
bf 11 1x External high temperature
warning
bf 12 1x External low temperature
warning
bf 13 1x Internal temperature alarm Environme
Environme
ntal error
Environme
ntal error
MODERATEYes
MODERATEYes
MODERATEYes
ntal error
bf 14 1x Internal temperature
warning_2
bf 15 1x Internal temperature
warning_1
bf 16 1x External high temperature
warning (40 degrees C)
Environme
ntal error
Environme
ntal error
Environme
ntal error
MODERATEYes
MODERATEYes
MODERATEYes
bf 22 xx SSVP voltage warning (PS_SUB) PS(DKC) MODERATEYes
bf 23 xx SSVP voltage warning (SVP
PS(DKC) MODERATEYes
supply)
bf 4x 1x DKCPS warning PS(DKC) MODERATEYes
bf 6x 1x DKCPS input voltage
PS(DKC) MODERATEYes
abnormality
bf 7x 1x DKCFAN warning Fan(DKC) MODERATEYes
bf 85 a3 JP remains EnvironmentMODERATEYes
bf 86 a3 JP remains EnvironmentMODERATEYes
bf 9x ax Communication Error between
SSVP and MN
DKC
environme
MODERATENo
nt
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 71
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
bf a0 ax Logic PS voltage alarm
PS(DKC) MODERATENo
disagreement
bf a2 ax External temperature
disagreement
DKC
environme
nt
bf a3 ax Internal temperature alarm
disagreement
DKC
environme
nt
bf a4 ax Internal temperature warning
disagreement
DKC
environme
nt
bf a5 ax PSOFFREQ I/F disagreement DKC
environme
nt
bf a6 ax PSOFFOK I/F disagreement DKC
environme
nt
bf a7 ax SYSON I/F disagreement DKC
environme
nt
MODERATENo
MODERATENo
MODERATENo
MODERATENo
MODERATENo
MODERATENo
bf a8 ax DKCPS I/F disagreement DKC
environme
nt
bf a9 ax DKCPS I/F disagreement DKC
environme
nt
bf aa a0 DKCPS I/F disagreement DKC
environme
nt
bf aa a4 DKCPS I/F disagreement DKC
environme
nt
bf ab a0 DKCPS I/F disagreement DKC
environme
nt
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 72
MODERATENo
MODERATENo
MODERATENo
MODERATENo
MODERATENo
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
bf ab a4 DKCPS I/F disagreement DKC
MODERATENo
environme
nt
bf ac a0 Communication Error between
EnvironmentMODERATENo
MN and MN
bf ac a1 Communication Error between
EnvironmentMODERATENo
MN and MN
bf ac a4 Communication Error between
EnvironmentMODERATENo
MN and MN
bf ac a5 Communication Error between
EnvironmentMODERATENo
MN and MN
bf ad a3 Cable connection error EnvironmentMODERATENo
bf ad a4 Cable connection error EnvironmentMODERATENo
bf ae a1 Cable connection error EnvironmentMODERATENo
bf af a0 PCTL/PNL abnormally EnvironmentMODERATENo
bf af a4 PCTL/PNL abnormally EnvironmentMODERATENo
bf bx ax PCTL/PNL abnormally DKC
MODERATENo
environme
nt
bf c0 10 DKC ALARM LED light on DKC
SERIOUS Yes
environme
nt
bf e3 a2 Duplex SVP Setup fail SVP failure MODERATEYes
bf e4 00 SVP FAN0 error SVP failure MODERATENo
bf e4 01 SVP FAN1 error SVP failure MODERATENo
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 73
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
bf e4 02 SVP FAN2 error SVP failure MODERATENo
bf e4 06 EXTENDER Hardware error SVP failure MODERATENo
1
bf e4 07 USB interface error Environme
MODERATENo
ntal error
bf e4 08 SVP receiving voltage error
SVP failure MODERATENo
(CL1)
bf e4 09 SVP receiving voltage error
SVP failure MODERATENo
(CL2)
cf 10 xx SAS CTL blocking Processor MODERATEYes
cf 11 xx SAS Port (WideLink) is partially
Processor SERVICE No
blocked
cf 12 xx SAS PORT blocked Processor MODERATEYes
cf 13 xx SAS-CTL Error detection Processor SERIOUS Yes
cf 20 xx PSW blockade Processor MODERATEYes
cf 22 xx NVMe port blockade Processor MODERATEYes
cf 88 xx CTL blocking Processor MODERATEYes
d0 0x xx TCMF/TC started the initial
copy or out of sync for this
volume
d0 1x xx TCMF/TC completed the initial
copy for this volume
Failure
with paired
volumes
Failure
with paired
SERVICE Yes
SERVICE Yes
volumes
d0 2x xx TCMF/TC for this volume was
deleted(Operation from an
SVP/Web Console or a host
Failure
with paired
volumes
SERVICE Yes
processor)
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 74
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
d1 0x xx Remote Copy pair status
change (MCU Command)
(From Simplex to Duplex
Pending)
d1 1x xx Remote Copy pair status
change (MCU Command)
(From Simplex to Duplex)
d1 2x xx Remote Copy pair status
change (MCU Command)
(From Duplex Pending to
Duplex)
d1 3x xx Remote Copy pair status
change (MCU Command)
(From Duplex Pending to
Suspend)
d1 4x xx Remote Copy pair status
change (MCU Command)
(From Duplex to Suspend)
d1 5x xx Remote Copy pair status
change (MCU Command)
(From Duplex to Simplex)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
d1 6x xx Remote Copy pair status
change (MCU Command)
(From Duplex Pending to
Simplex)
d1 7x xx Remote Copy pair status
change (MCU Command)
(From Suspend to Simplex)
d1 8x xx Remote Copy pair status
change (MCU Command)
(From Suspend to Duplex
Pending)
d1 9x xx Remote Copy pair status
change (MCU Command)
(From Duplex Pending to
Suspend(continue))
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 75
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
d1 ax xx Remote Copy pair status
change (MCU Command)
(From Duplex Pending to
Suspend(complete))
d1 bx xx Remote Copy pair status
change (MCU Command)
(From Suspend (continue) to
Suspend)
d4 0x xx TCMF/TC for this volume was
suspended (Due to an
unrecoverable failure on the
remote copy connections)
d4 1x xx TCMF/TC for this volume was
suspended (Due to an
unrecoverable failure on the PVOL or the remote copy
connections)
d4 2x xx TCMF/TC for this volume was
suspended (Due to an
unrecoverable failure on the SVOL)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
d4 4x xx TCMF/TC for this volume was
suspended (Due to an internal
error condition detected by
the RCU)
d4 5x xx TCMF/TC for this volume was
suspended (Caused by Delete
pair operation was issued to
the S-VOL)
d4 6x xx The S-VOL has suspended.
(Due to an unrecoverable
failure on the remote copy
connections)
d4 7x xx The S-VOL has suspended
(Due to an unrecoverable
failure on the S-VOL)
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 76
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
d4 fx xx Status of the P-VOL was not
consistent with the S-VOL
d5 7x xx Command device operation
execution of command device
in state of ONLINE
d8 0x xx A volume to be used by the
URMF/UR was dened
d8 1x xx The volume being used by the
URMF/UR began a copying
d8 2x xx The volume being used by the
URMF/UR completed a copying
d8 3x xx The volume being used by the
URMF/UR received a request
for suspension
d8 4x xx The volume being used by the
URMF/UR completed a
suspension transaction
Failure
SERIOUS Yes
with paired
volumes
Drive SERVICE No
Failure
SERVICE Yes
with paired
volumes
Failure
SERVICE Yes
with paired
volumes
Failure
SERVICE Yes
with paired
volumes
Failure
SERVICE Yes
with paired
volumes
Failure
SERVICE Yes
with paired
volumes
5
5
5
5
5
d8 5x xx The volume being used by the
URMF/UR received a request
for deletion
d8 6x xx The volume being used by the
URMF/UR completed the
deletion
d8 7x xx The volume being used by the
URMF/UR was dened (placed
in the PSUS status
immediately)
d8 8x xx A Delta volume to be used by
the URMF/UR was dened
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 77
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
5
5
5
5
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
d8 9x xx A Delta volume to be used by
the URMF/UR was redened
d9 0x xx A change to an S-VOL was
received from the MCU (From
Simplex to Duplex Pending)
d9 1x xx A change to an S-VOL was
received from the MCU (From
Simplex to Duplex)
d9 2x xx A change to an S-VOL was
received from the MCU (From
Duplex Pending to Duplex)
d9 3x xx A change to an S-VOL was
received from the MCU (From
Duplex Pending to Suspend)
d9 4x xx A change to an S-VOL was
received from the MCU (From
Duplex to Suspend)
d9 5x xx A change to an S-VOL was
received from the MCU (From
Duplex to Simplex)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
5
5
5
5
5
5
5
d9 6x xx A change to an S-VOL was
received from the MCU (From
Duplex Pending to Simplex)
d9 7x xx A change to an S-VOL was
received from the MCU (From
Suspend to Simplex)
d9 8x xx A change to an S-VOL was
received from the MCU (From
Suspend to Duplex Pending)
d9 9x xx A change to an S-VOL was
received from the MCU (HOLD
-> PAIR)
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 78
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
5
5
5
5
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
d9 ax xx A change to an S-VOL was
received from the MCU (HOLD
-> COPY)
d9 bx xx A change to an S-VOL was
received from the MCU (HOLD
-> SMPL)
d9 cx xx A change to an S-VOL was
received from the MCU (From
Simplex to Suspend)
d9 dx xx A change to an S-VOL was
received from the MCU (SMPL
-> HOLD)
d9 ex xx A change to an S-VOL was
received from the MCU
(PSUx(Suspend) -> HOLD)
d9 fx xx A change to an S-VOL was
received from the MCU (From
Duplex to Duplex Pending)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
SERVICE Yes
5
5
5
5
5
5
da 0x xx A change to an S-VOL was
received from the RCU (A
request for suspension was
received.)
da 1x xx A change to an S-VOL was
received from the RCU (A
suspension transaction was
completed.)
da 2x xx A change to an S-VOL was
received from the RCU (An
instruction to delete a pair was
received in the Suspend
status.)
da 3x xx A change to an S-VOL was
received from the RCU (An
instruction to delete a pair was
received in the Duplex
Pending status.)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE No
SERVICE No
SERVICE No
SERVICE No
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 79
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
da 4x xx A change to an S-VOL was
received from the RCU (An
instruction to delete a pair was
Failure
with paired
volumes
SERVICE No
received in the Duplex status.)
da 5x xx A change to an S-VOL was
received from the RCU (A pair
deletion was completed.)
da 6x xx A change to an S-VOL was
received from the RCU (An
instruction to delete a pair was
Failure
with paired
volumes
Failure
with paired
volumes
SERVICE No
SERVICE No
received in the Hold status.)
db 0x xx Drive port temporary error Drive error SERVICE Yes
db 1x xx Drive port temporary error Drive error SERVICE Yes
db 2x xx Drive port temporary error Drive error SERVICE Yes
db 3x xx Drive port temporary error Drive error SERVICE Yes
db 4x xx Drive port blockade Drive error MODERATEYes
db 5x xx Drive port blockade Drive error MODERATEYes
db 6x xx Drive port blockade Drive error MODERATEYes
db 7x xx Drive port blockade Drive error MODERATEYes
db 8x xx LDEV blockade (Eect of Drive
Drive error SERIOUS Yes
port blockade)
db 9x xx LDEV blockade (Eect of Drive
Drive error SERIOUS Yes
port blockade)
db ax xx LDEV blockade (Eect of Drive
Drive error SERIOUS Yes
port blockade)
db bx xx LDEV blockade (Eect of Drive
Drive error SERIOUS Yes
port blockade)
db cx xx Drive Link Rate Abnormality Drive error SERVICE Yes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 80
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
db dx xx Drive Link Rate Abnormality Drive error SERVICE Yes
db ex xx Drive Link Rate Abnormality Drive error SERVICE Yes
db fx xx Drive Link Rate Abnormality Drive error SERVICE Yes
1
dc 0x xx PAIR SUSPEND(RIO PATH
CLOSE)
Failure
with paired
volumes
dc 1x xx PAIR SUSPEND(MVOL ERROR) Failure
with paired
volumes
dc 2x xx PAIR SUSPEND(RVOL ERROR) Failure
with paired
volumes
dc 4x xx PAIR SUSPEND(SUSPEND
REPORT)
Failure
with paired
volumes
dc 5x xx PAIR SUSPEND(SIMPLEX
REPORT)
Failure
with paired
volumes
dc 6x xx PAIR
SUSPEND(COMMUNICATION
ERROR AT RCU)
dc 7x xx PAIR SUSPEND(ERROR
DETECTED AT RCU)
Failure
with paired
volumes
Failure
with paired
volumes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
5
5
5
5
5
5
5
dc 8x xx A volume being used by an S-
VOL was suspended (PS OFF
on the MCU side was
Failure
with paired
volumes
detected)
dc 9x xx ERASE FAIL Failure
with paired
volumes
dc ax xx Pair suspend (Spread by error
of another Aliate)
Failure
with paired
volumes
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 81
SERVICE No
SERIOUS Yes
SERIOUS Yes
5
5
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
dc e0 xx URMF/UR M-JNL Meta
overow warning
dc e1 xx URMF/UR M-JNL Data overow
warning
dc e2 xx URMF/UR R-JNL Meta overow
warning
dc e3 xx URMF/UR R-JNL Data overow
warning
dc f0 xx The URMF/UR Read JNL was
interrupted for one minute (A
failure on the MCU side was
detected)
dc f1 xx The URMF/UR Read JNL was
interrupted for ve minutes (A
failure on the MCU side was
detected)
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
MODERATENo
MODERATENo
MODERATENo
MODERATENo
MODERATENo
SERIOUS No
dc f2 xx The URMF/UR Read JNL was
interrupted for one minute (A
failure on the RCU side was
detected)
dc f3 xx The URMF/UR Read JNL was
interrupted for ve minutes (A
failure on the RCU side was
detected)
dc f4 xx URMFxURMF/URxUR M-JNL
Meta full Warning
dc f5 xx URMFxURMF/URxUR M-JNL
Data full Warning
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 82
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
volumes
MODERATENo
SERIOUS No
MODERATENo
MODERATENo
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
dd 0x xx GAD for this volume was
suspended (Due to an
unrecoverable failure on the
Failure
with paired
volumes
SERIOUS Yes
remote copy connections)
dd 1x xx GAD for this volume was
suspended (Due to a failure on
the volume)
dd 2x xx GAD for this volume was
suspended (Due to an internal
error condition detected)
dd 3x xx Status of the P-VOL was not
consistent with the S-VOL
Failure
with paired
volumes
Failure
with paired
volumes
Failure
with paired
SERIOUS Yes
SERIOUS Yes
SERIOUS Yes
volumes
de e0 xx Quorum Disk Restore Drive SERVICE Yes
de f0 xx Quorum Disk Blocked Drive SERIOUS Yes
df 6x xx Drive port temporary error
(Drive path: Boundary 0)
6
df 7x xx Drive port temporary error
(Drive path: Boundary 1)
6
Drive SERVICE No
Drive SERVICE No
df 8x xx DRIVE PORT BLOCKADE(PATH
6
0)
df 9x xx DRIVE PORT BLOCKADE(PATH
6
1)
df ax xx LDEV blockade(Drive path:
Boundary 0/Eect of Drive
port blockade)
6
df bx xx LDEV blockade(Drive path:
Boundary 1/Eect of Drive
port blockade)
6
df cx xx Drive Link Rate Abnormality
(Path 0)
6
df dx xx Drive Link Rate Abnormality
(Path 1)
6
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 83
Drive MODERATEYes
Drive MODERATEYes
Drive SERIOUS Yes
Drive SERIOUS Yes
Drive SERVICE Yes
Drive SERVICE Yes
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
df ex xx Response late Drive Drive SERVICE Yes
1
df fx xx Response late Drive
eb 0x xx Drive blockade (drive)(with
6
Drive SERVICE No
Drive SERIOUS Yes
redundancy)
eb 1x xx Drive blockade (drive)(with
Drive SERIOUS Yes
redundancy)
eb 2x xx Drive blockade (drive)(without
Drive SERIOUS Yes
redundancy)
eb 3x xx Drive blockade (drive)(without
Drive SERIOUS Yes
redundancy)
eb 4x xx Drive blockade (Eect of
Drive SERVICE Yes
Dynamic sparing normal end)
eb 5x xx Drive blockade (Eect of
Drive SERVICE Yes
Dynamic sparing normal end)
eb 6x xx Correction access occurred Drive SERIOUS Yes
eb 7x xx Correction access occurred Drive SERIOUS Yes
eb 8x xx Reboot stopped due to much
Drive SERVICE No
write pending data
eb 9x xx Reboot stopped due to much
Drive SERVICE No
write pending data
ef 0x xx Drive blockade (drive)(with
redundancy)
6
ef 1x xx Drive blockade (drive) (without
redundancy)
6
ef 2x xx DRIVE BLOCKADE(EFFECT OF
DRIVE COPY NORMAL END)
Drive SERIOUS Yes
Drive SERIOUS Yes
Drive SERVICE Yes
6
ef 4x xx PINNED SLOT Drive MODERATENo
ef 5x xx Abnormal end of Write
Drive MODERATENo
processing in External storage
system
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 84
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
ef 8x xx LDEV blockade (Eect of drive
Drive SERIOUS Yes
blockade)
ef 9x xx LDEV blockade (Eect of drive
blockade)
6
ef ax xx DRIVE TEMPORARY ERROR
Drive SERIOUS Yes
6
Drive SERVICE No
ef bx xx Drive temporary error Drive SERVICE Yes
ef cx xx Correction access occurred
ef d0 00 External storage system
6
Drive SERIOUS Yes
Drive SERIOUS Yes
connection device blockade
ef d4 00 Blocking the Data Migration
Drive MODERATENo
source device
ef fd xx Expander failure Environme
SERIOUS Yes
ntal error
ef fe xx UNIT CONNECTION ERROR DKC
MODERATEYes
environme
nt
fe 00 00 Cache battery is being charged Cache SERIOUS Yes
fe 01 0x End of Cache Write Through Cache SERVICE No
fe 02 0x Start of Cache Write Through Cache MODERATEYes
fe 03 0x Cache SSD mounting capacity
Cache SERIOUS No
shortage
fe 04 xx No CHB mounted Cache SERIOUS Yes
21 xx LANB blocking Processor MODERATEYes
4x xx PINNED SLOT Cache MODERATENo
5x xx Abnormal end of Read
Drive MODERATENo
processing in External storage
system
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 85
Trap reference
code
SIM22SIM23SIM
13
Failure trap reference codes
Description Section Alert level
Host
report
1
c3 0x CACHE PACKAGE BLOCKADE
Cache SERVICE Yes
PROCESSING END
cb xx CTL patrol check error Cache SERVICE No
cc 0x CM/CMA patrol check error Cache SERVICE No
cd 0x Area is volatilized Cache SERVICE No
cf xx Package is volatilized Cache SERVICE No
d4 xx Constitution denition error Processor MODERATENo
de xx WDCP loss of duplicated
SM SERVICE No
information
e4 0x REPLACE FAILED Cache SERIOUS No
e7 00 Rebooted with volatilization
SM SERIOUS Yes
after an instantaneous down
e8 00 Denition/Installation
SM ACUTE No
mismatch
ea 0x RECOVERY OF AREA BLOCKED
SM SERVICE Yes
TEMPORARILY WAS
COMPLETED
ee 0x AREA TEMPORARY BLOCKING SM SERVICE Yes
ef 00 Rebooted without
SM SERVICE No
volatilization after an
instantaneous down
f0 xx DIMM Correctable error Cache SERVICE No
f3 0x PACKAGE BLOCKING Cache MODERATEYes
f4 00 AREA BLOCKING Cache SERIOUS Yes
f4 01 AREA BLOCKING Cache SERIOUS Yes
f5 0x Both areas failed Cache MODERATENo
f6 xx CM Injustice dc voltage control Cache MODERATENo
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 86
Failure trap reference codes
Trap reference
code
Host
SIM22SIM23SIM
13
Description Section Alert level
report
f7 xx GUM blocking Cache MODERATEYes
f9 0x REPLACE FAILED Cache SERVICE No
fa xx Battery warning Battery MODERATENo
fb xx CMBK warning Cache MODERATENo
1
fc xx CM Temperature abnormality
Cache MODERATENo
warning
fe xx Warning for forcible volatile
Cache MODERATENo
mode
Legend:
■
Yes: This SIM performs the host report.
■
No: This SIM does not perform the host report.
■
x: A hexadecimal number between 0 and f.
1. If you select All for Notication Alert in the Edit Alert Settings window, the SNMP
agent reports all SIMs. If you select Host Report, the SNMP agent reports only
SIMs that perform the host report.
2. If the DKC emulation type is I-2105 or I-2107, SIMs are reported to the host only if
SOM 308 is enabled. However, SOM 308 is disabled by default.
3. This SIM is not reported to the host, but the SNMP agent reports the SIM when
Host Report is selected for Notication Alert in the Edit Alert Settings window.
4. The SNMP agent does not report this SIM when Host Report is selected for
Notication Alert in the Edit Alert Settings window, because the SIM is reported
to the host, but not to the SVP.
5. SIMs are not reported to the host by default. To enable reporting of service SIMs,
see the Hitachi Universal Replicator for Mainframe User Guide.
6. xxx: Drive location. For details, see Converting DB and RDEV numbers to the HDD
location number (on page 88) .
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 87
Converting DB and RDEV numbers to the HDD location number
Converting DB and RDEV numbers to the HDD location
number
To identify the location of an error, convert drive box (DB) and RDEV numbers to the
HDD location number.
The following describes the bit alignment of DB and RDEV numbers (which are expressed
by 13 bits of a SIM reference code) and the relationship between the DB and RDEV
numbers and the HDD location.
■
Format of the DB and RDEV numbers
W (4 bits) X (4 bits) Y (4 bits) Z (4 bits)
w w w w x x x x y y y y z z z z
DB number (8 bits) RDEV number (5 bits)
Example:
When SIM code = eb75a5 (Correction access occurred [eb7xxx]):
WXYZ = 75a5 (hexadecimal)
7 5 a 5
0 1 1 1 0 1 0 1 1 0 1 0 0 1 0 1
DB number = AD (hexadecimal)
173 (decimal)
■
Relationship between the DB and RDEV numbers and the HDD location number
Example:
When WXYZ = 75a5 (hexadecimal):
RDEV number = 05 (hex)
5 (decimal)
HDD location number: HDD173-05
The following table describes the relationship between the DB and RDEV numbers (13
bits of a reference code), drive box number, RDEV number, and HDD location number,
taking the example of drive boxes DB-000, DB-001, DB-190, and DB-191.
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 88
Converting DB and RDEV numbers to the HDD location number
Reference code
(DB#/RDEV#(hex))
0000 DB-000 00 HDD000-00
0001 01 HDD000-01
0002 02 HDD000-02
0003 03 HDD000-03
0004 04 HDD000-04
0005 05 HDD000-05
0006 06 HDD000-06
0007 07 HDD000-07
0008 08 HDD000-08
0009 09 HDD000-09
000A 10 HDD000-10
000B 11 HDD000-11
Drive box number
(DB#)
RDEV number
(R#)
HDD location
number
0020 DB-001 00 HDD001-00
0021 01 HDD001-01
0022 02 HDD001-02
0023 03 HDD001-03
0024 04 HDD001-04
0025 05 HDD001-05
0026 06 HDD001-06
0027 07 HDD001-07
0028 08 HDD001-08
0029 09 HDD001-09
002A 10 HDD001-10
002B 11 HDD001-11
... ... ... ...
17C0 DB-190 00 HDD190-00
17C1 01 HDD190-01
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 89
Converting DB and RDEV numbers to the HDD location number
Reference code
(DB#/RDEV#(hex))
17C2 02 HDD190-02
17C3 03 HDD190-03
17C4 04 HDD190-04
17C5 05 HDD190-05
17C6 06 HDD190-06
17C7 07 HDD190-07
17C8 08 HDD190-08
17C9 09 HDD190-09
17CA 10 HDD190-10
17CB 11 HDD190-11
17E0 DB-191 00 HDD191-00
17E1 01 HDD191-01
Drive box number
(DB#)
RDEV number
(R#)
HDD location
number
17E2 02 HDD191-02
17E3 03 HDD191-03
17E4 04 HDD191-04
17E5 05 HDD191-05
17E6 06 HDD191-06
17E7 07 HDD191-07
17E8 08 HDD191-08
17E9 09 HDD191-09
17EA 10 HDD191-10
17EB 11 HDD191-11
Chapter 8: SIM codes
Hitachi Alert Notication Guide for VSP5000 Series 90
Glossary
community name
An SNMP entity in which up to 32 names and up to 32 IP addresses can be registered.
extension trap
An error message generated by a third-party node and sent to the SNMP agent.
failure trap
An error message that indicates a problem within a managed node.
IPv4
Internet Protocol, Version 4
IPv6
Internet Protocol, Version 6
managed device
A network node on which the SNMP Agent software is installed. Using the agent, managed
devices exchange node-specic information with the SNMP management software.
managed node
See managed device.
management information base (MIB)
A virtual database of objects that can be monitored by a network management system. SNMP
uses standardized MIBs that allow any SNMP-based tool to monitor any device dened by a
MIB le.
Simple Network Management Protocol (SNMP)
An industry-standard protocol that is used to manage and monitor network-attached devices
for conditions that warrant administrative attention. The devices can include disk devices,
routers, and hubs. SNMP uses Simple Gateway Management Protocol (SGMP) to manage
TCP/IP gateways.
SNMP Agent
Software that is installed on the SVP and responds to queries from SNMP Manager.
SNMP Manager
Software that is installed on the network management station that collects and manages
information from SNMP agents installed in the managed devices on the network.
SNMP trap
An event generated by an SNMP agent from the managed resource that communicates an
event, such as an error or failure.
user datagram protocol (UDP)
Software that requests data regarding the status of a managed node.
Glossary
Hitachi Alert Notication Guide for VSP5000 Series 91
Hitachi Vantara
Corporate Headquarters
2535 Augustine Drive
Santa Clara, CA 95054 USA
HitachiVantara.com | community.HitachiVantara.com
Contact Information
USA: 1-800-446-0744
Global: 1-858-547-4526
HitachiVantara.com/contact
Loading...