Hitachi VSP 5000 Series Notification Manual

Hitachi VSP 5000 Series Notification Manual

Virtual storage platform alert notification
Table of Contents

Advertisement

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

Advertisement

Table of Contents
loading

Summary of Contents for Hitachi VSP 5000 Series

  • Page 1 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.
  • Page 2 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.
  • Page 3: Table Of Contents

    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 Notification Guide for VSP5000 Series...
  • Page 4 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 Notification Guide for VSP5000 Series...
  • Page 5: Preface

    ■ 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 ■...
  • Page 6: Changes In This Revision

    Changes in this revision Changes in this revision Added information and specifications for VSP 5000 series. ■ Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text in a window, including window titles, menus, ■ menu options, buttons, fields, and labels. Example: Click OK.
  • Page 7: Conventions For Storage Capacity Values

    Logical capacity values (for example, logical device capacity, cache memory capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 cylinder Mainframe: 870 KB Preface Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 8: Accessing Product Documentation

    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.
  • Page 9: Chapter 1: Failure Monitoring

    Chapter 1: Failure monitoring By using the Hitachi Device Manager - Storage Navigator, you can use alert notification email, Syslog, and SNMP for failure monitoring. Alert notification email The following gives an example of an alert notification email that is sent from a storage system to the mail server.
  • Page 10: Syslog

    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 Notification Guide for VSP5000 Series...
  • Page 11 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 Notification Guide for VSP5000 Series...
  • Page 12 Authentication of RMI, FC-SP, or Device Manager - Storage ■ Navigator. ConfigurationAccess indicates setting from Device ■ Manager - Storage Navigator, SVP or host. Maintenance indicates SVP operations. ■ Chapter 1: Failure monitoring Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 13 FC-SP authentication. No output. No output. No output. Collective operation identifier. This is a serial number that identifies those multiple lines displayed by one operation are the same operation. Chapter 1: Failure monitoring Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 14 *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 Notification Guide for VSP5000 Series...
  • Page 15 6: Informational. The operation has ended normally. ■ For example, <12> indicates the priority when the severity is error. Version The version (1). Chapter 1: Failure monitoring Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 16 Success: Normal end. The operation has ended normally. ■ event 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 Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 17 "AnomalyEvent". The same information contained in the detailed information of the audit log file. No serial number is output when the category name is "AnomalyEvent". Chapter 1: Failure monitoring Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 18: Snmp

    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 Notification Guide for VSP5000 Series...
  • Page 19: Chapter 2: Setting Alert Notification Email

    Chapter 2: Setting alert notification email By using the Hitachi Device Manager - Storage Navigator, you can manage the alert notificatrion email settings. Editing alert notification email settings This topic describes how to specify the email settings necessary to report failure trap reference codes (SIMs).
  • Page 20 -, *, ', {, }, _, 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 notification email Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 21 13. Confirm the settings in the Confirm 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 notification email Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 22: Chapter 3: Setting Syslog

    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 Configuration) role to perform this ■...
  • Page 23 13. Confirm the settings in the Confirm 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 Notification Guide for VSP5000 Series...
  • Page 24: Chapter 4: Setting Snmp

    Chapter 4: Setting SNMP By using the Hitachi Device Manager - Storage Navigator, you can manage alert settings, SNMP trap notification, SNMP request authentication, and test SNMP trap reports. Editing alert settings This topic describes how to set the Edit Alert Settings.
  • Page 25: Adding Trap Notification For Snmp V1 And Snmp V2C

    The IP address and community you entered are added to the Registered Sending Trap Settings table. 10. Click Finish. 11. In the Confirm window, enter a name for the task, confirm the settings, and then click Apply. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 26: Adding Trap Notification For Snmp V3

    For Re-enter Key, enter the same key for confirmation. 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 Notification Guide for VSP5000 Series...
  • Page 27: Changing Trap Notification For Snmp V1 And Snmp V2C

    (:) using a maximum of 4 digits from zero (0) to FFFF inclusive. The default form of the IPv6 address can be specified. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 28: Changing Trap Notification For Snmp V3

    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 Notification Guide for VSP5000 Series...
  • Page 29: Deleting Snmp Trap Notification

    IP address and community or user, and then click Delete. 7. Click Finish. 8. In the Confirm window, enter a name for the task, confirm the settings, and then click Apply. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 30: Managing Snmp Request Authentication

    ", \, ;, :, ,, *, ?, <, >, |, /, ^, &,', and %. Do not use a space either at the beginning or the end. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 31: Adding Request Authentication For Snmp V3

    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 Notification Guide for VSP5000 Series...
  • Page 32: Changing Request Authentication For Snmp V1 And Snmp V2C

    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 Notification Guide for VSP5000 Series...
  • Page 33: Changing Request Authentication For Snmp V3

    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 Notification Guide for VSP5000 Series...
  • Page 34: 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 Configuration) role to perform this task. For more information, see the System Administrator Guide. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 35: Testing The Snmp Trap Report

    Finish and apply to the storage system, and then report the test SNMP trap. 5. Verify whether the SNMP trap report (reference code 7fffff) is received by the SNMP manager registered in the community. Chapter 4: Setting SNMP Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 36: Chapter 5: Troubleshooting

    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 specified in SNMP settings.
  • Page 37: Chapter 6: Snmp Overview

    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.
  • Page 38: Management Information Base Overview

    The storage system has an exclusive LAN for communications with the SVP and a separate LAN for SNMP. The configuration of each Network Management Station is determined by the type of SNMP manager. The following figure illustrates the SNMP environment. Chapter 6: SNMP overview Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 39: Snmp Agent Overview

    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 identifier of the component. Chapter 6: SNMP overview Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 40: Snmp Agent Operations

    Several different 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 Notification Guide for VSP5000 Series...
  • Page 41: Component Status Information From Snmp Manager

    The following table lists the components for which the status can be obtained. Area Component name Storage System Processors Cache Shared memory Power supplies Batteries Fans Others Disk Unit Power supplies Fans Environments Drives Chapter 6: SNMP overview Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 42 All operations in a storage system stopped. Serious failure detected Operation in a component where a failure occurred stopped. Moderate failure Partial failure. detected Service failure detected Minor failure. Chapter 6: SNMP overview Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 43: Chapter 7: Snmp Supported Mibs

    The area where IDENTIFIER the failure occurred.* eventTrapDate .1.3.6.1.4.1.116.5.11.4.2.5 DisplayString Failure occurrence date. eventTrapTime .1.3.6.1.4.1.116.5.11.4.2.6 DisplayString Failure occurrence time. eventTrapDescri .1.3.6.1.4.1.116.5.11.4.2.7 DisplayString Detailed ption information of a failure. Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 44: Snmp Agent Extension Trap Types

    (MIB) that is not supported, you will receive NoSuchName as a GET RESPONSE. The following table lists MIBs and indicates whether they are supported. Supported? Standard MIB: MIB-II system group interface group at group ip group icmp group Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 45: Snmp Agent Mib Access Mode

    SNMP Agent supports two MIB mounting specifications. The supported MIB mounting specifications 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 Notification Guide for VSP5000 Series...
  • Page 46: Extension Mib Specifications

    ├-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 figures show an example extension MIB configuration. Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 47 Extension MIB configuration Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 48: Raidexmibname

    "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 Notification Guide for VSP5000 Series...
  • Page 49: Raidexmibagentversion

    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 Notification Guide for VSP5000 Series...
  • Page 50: Raidexmibdkchwtable

    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 Notification Guide for VSP5000 Series...
  • Page 51 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. Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 52: Raidexmibdkuhwtable

    INTEGE Status of power supply. See Note read-only ::=raidExMibDKUHWEntry(2 dkuHWFan INTEGE Status of fan. See Note read-only ::=raidExMibDKUHWEntry(3 dkuHWEnvironment INTEGE Status of environment See Note read-only monitor. ::=raidExMibDKUHWEntry(4 Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 53: Raidexmibtraplisttable

    The following table lists the information displayed for each failure. Name Type Description MIB value Attribute eventListIndexSerialNu INTEGER Storage system 1 - 99,999 read-only mber product number (index). Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 54 Time when the hh:mm:ss read-only ring failure occurred. ::=raidExMibTrapListEn (8 characters) try (6) eventListDescription DisplaySt Detailed 256 characters read-only ring information maximum ::=raidExMibTrapListEn about the try (7) failure. Chapter 7: SNMP supported MIBs Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 55: Chapter 8: Sim Codes

    X path blocking Cache MODERAT HIE warning Cache MODERAT X path warning Cache MODERAT Logical path(s) on the remote Processor MODERAT copy connections was logically blocked (Due to an error condition) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 56 Data Migration Path Recovery Processor SERVICE CHK1A THRESHOLD OVER Processor SERVICE CHK1B THRESHOLD OVER Processor SERVICE CHK3 THRESHOLD OVER Processor SERVICE PROCESSOR BLOCKING Processor MODERAT FM ERROR Processor MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 57 SMA SLAVE ERROR Processor SERVICE CPU frequency setting failure Processor SERVICE LDEV Blockade (Effect of Processor MODERAT microcode error) CHB/DKB Type disagreement Processor MODERAT iSCSI firmware update warning Processor MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 58 Drive SERVICE CORRECTION COPY NORMAL Drive SERVICE CORRECTION COPY Drive SERIOUS ABNORMAL END CORRECTION COPY Drive SERVICE DISCONTINUED Correction copy warning Drive SERVICE end(With blockade LDEV or some error) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 59 Forcible suspend by SM Failure MODERAT volatile (SIMF/SI) with paired volumes Thin Image ABNORMAL END Failure MODERAT BY SM VOLATILE with paired volumes Volume Migration Abnormal Volume MODERAT Migration Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 60 Correction copy abnormal end Failure SERIOUS with paired volumes Correction copy abnormal end Failure SERIOUS with paired volumes Correction copy discontinued Failure SERVICE with paired volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 61 Dynamic sparing abnormal Drive MODERAT end (Drive copy) Dynamic sparing abnormal Drive MODERAT end (Drive copy) Dynamic sparing discontinued Drive SERVICE (Drive copy) Dynamic sparing discontinued Drive SERVICE (Drive copy) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 62 Flash module drive micro- Drive MODERAT program version warning Pool blocking Thin Image MODERAT pool SM Space Warning MODERAT Exceeded Threshold of pool Thin Image MODERAT use rate pool Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 63 Provisionin g pool Exceeded Depletion Threshold Dynamic MODERAT of DP pool use rate Provisionin g pool Exceeded Fixed outage Dynamic MODERAT Threshold of DPpool use rate Provisionin g pool Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 64 SVP failure MODERAT File error SVP failure MODERAT LAN error SVP failure MODERAT SSVP error SVP failure MODERAT Windows error SVP failure MODERAT CUDG3 detected error SVP failure MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 65 Audit Log failure of Host SVP failure MODERAT instruction configuration change Audit Log FTP Transfer failed SVP failure MODERAT Dump Tool failed SVP failure SERVICE Invalid SIM data detection SVP failure SERVICE Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 66 Bad CRC Count(Fibre) Excess Monitor MODERAT Protocol Error Count(Fibre) Monitor MODERAT Excess Expired Frame Count (Fibre) Monitor MODERAT Excess HTP/FNP Multiplicity Excess Monitor MODERAT FEC Un-correctable Monitor MODERAT Count(Fibre) threshold exceeded Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 67 Error Cache MCU Side File Use Ratio Monitor MODERAT Error TCMF/TC SVP failure SERVICE SIMF/SI SVP failure SERVICE URMF/UR SVP failure SERVICE SVP failure SERVICE FlashCopy(R) SVP failure SERVICE Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 68 Injustice JP Warning Environme MODERAT ntal error MP Temperature abnormality Environme MODERAT warning ntal error External temperature warning Environme MODERAT ntal error External temperature alarm Environme MODERAT ntal error Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 69 MODERAT DBPS-1 input voltage PS(DKU) MODERAT abnormality DBPS-2 input voltage PS(DKU) MODERAT abnormality DB External temperature Environme MODERAT warning ntal error DB External temperature Environme MODERAT Alarm ntal error Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 70 Battery charge EMPTY Battery MODERAT CM Backup mounting warning Cache MODERAT SSW data disagreement MODERAT environme GUM warning Environme MODERAT ntal error CFM error Processor MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 71 DKCPS warning PS(DKC) MODERAT DKCPS input voltage PS(DKC) MODERAT abnormality DKCFAN warning Fan(DKC) MODERAT JP remains Environme MODERAT JP remains Environme MODERAT Communication Error between MODERAT SSVP and MN environme Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 72 SYSON I/F disagreement MODERAT environme DKCPS I/F disagreement MODERAT environme DKCPS I/F disagreement MODERAT environme DKCPS I/F disagreement MODERAT environme DKCPS I/F disagreement MODERAT environme DKCPS I/F disagreement MODERAT environme Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 73 PCTL/PNL abnormally MODERAT environme DKC ALARM LED light on SERIOUS environme Duplex SVP Setup fail SVP failure MODERAT SVP FAN0 error SVP failure MODERAT SVP FAN1 error SVP failure MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 74 TCMF/TC completed the initial Failure SERVICE copy for this volume with paired volumes TCMF/TC for this volume was Failure SERVICE deleted(Operation from an with paired SVP/Web Console or a host volumes processor) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 75 SERVICE change (MCU Command) with paired (From Suspend to Duplex volumes Pending) Remote Copy pair status Failure SERVICE change (MCU Command) with paired (From Duplex Pending to volumes Suspend(continue)) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 76 (Due to an unrecoverable with paired failure on the remote copy volumes connections) The S-VOL has suspended Failure SERIOUS (Due to an unrecoverable with paired failure on the S-VOL) volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 77 SERVICE URMF/UR was defined (placed with paired in the PSUS status volumes immediately) A Delta volume to be used by Failure SERVICE the URMF/UR was defined with paired volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 78 MCU (From with paired Suspend to Duplex Pending) volumes A change to an S-VOL was Failure SERVICE received from the MCU (HOLD with paired -> PAIR) volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 79 A change to an S-VOL was Failure SERVICE received from the RCU (An with paired instruction to delete a pair was volumes received in the Duplex Pending status.) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 80 LDEV blockade (Effect of Drive Drive error SERIOUS port blockade) LDEV blockade (Effect of Drive Drive error SERIOUS port blockade) Drive Link Rate Abnormality Drive error SERVICE Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 81 MCU side was volumes detected) ERASE FAIL Failure SERIOUS with paired volumes Pair suspend (Spread by error Failure SERIOUS of another Affiliate) with paired volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 82 RCU side was volumes detected) URMFxURMF/URxUR M-JNL Failure MODERAT Meta full Warning with paired volumes URMFxURMF/URxUR M-JNL Failure MODERAT Data full Warning with paired volumes Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 83 LDEV blockade(Drive path: Drive SERIOUS Boundary 1/Effect of Drive port blockade) Drive Link Rate Abnormality Drive SERVICE (Path 0) Drive Link Rate Abnormality Drive SERVICE (Path 1) Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 84 Drive blockade (drive) (without Drive SERIOUS redundancy) DRIVE BLOCKADE(EFFECT OF Drive SERVICE DRIVE COPY NORMAL END) PINNED SLOT Drive MODERAT Abnormal end of Write Drive MODERAT processing in External storage system Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 85 Cache SSD mounting capacity Cache SERIOUS shortage No CHB mounted Cache SERIOUS LANB blocking Processor MODERAT PINNED SLOT Cache MODERAT Abnormal end of Read Drive MODERAT processing in External storage system Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 86 DIMM Correctable error Cache SERVICE PACKAGE BLOCKING Cache MODERAT AREA BLOCKING Cache SERIOUS AREA BLOCKING Cache SERIOUS Both areas failed Cache MODERAT CM Injustice dc voltage control Cache MODERAT Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 87 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...
  • Page 88: Converting Db And Rdev Numbers To The Hdd Location Number

    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 Notification Guide for VSP5000 Series...
  • Page 89 DB-001 HDD001-00 0021 HDD001-01 0022 HDD001-02 0023 HDD001-03 0024 HDD001-04 0025 HDD001-05 0026 HDD001-06 0027 HDD001-07 0028 HDD001-08 0029 HDD001-09 002A HDD001-10 002B HDD001-11 17C0 DB-190 HDD190-00 17C1 HDD190-01 Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 90 17CA HDD190-10 17CB HDD190-11 17E0 DB-191 HDD191-00 17E1 HDD191-01 17E2 HDD191-02 17E3 HDD191-03 17E4 HDD191-04 17E5 HDD191-05 17E6 HDD191-06 17E7 HDD191-07 17E8 HDD191-08 17E9 HDD191-09 17EA HDD191-10 17EB HDD191-11 Chapter 8: SIM codes Hitachi Alert Notification Guide for VSP5000 Series...
  • Page 91: Glossary

    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 Notification Guide for VSP5000 Series...
  • Page 92 Hitachi Vantara Corporate Headquarters Contact Information 2535 Augustine Drive USA: 1-800-446-0744 Santa Clara, CA 95054 USA Global: 1-858-547-4526 HitachiVantara.com | community.HitachiVantara.com HitachiVantara.com/contact...

Table of Contents