ETERNUS DX80 S2/DX90 S2 Disk storage system User's …storage-system.fujitsu.com/global/doc/pdf/p3am-4842-en.pdf · Disk storage system User's Guide -Operation- ... of the ETERNUS

ETERNUS DX80 S2/DX90 S2 Disk storage system

User's Guide -Operation-

P3AM-4842-12ENZ0

This page is intentionally left blank.

ETERNUS DX80 S2/DX90 S2 Disk storage system User’s Guide -Operation-

Copyright 2013 FUJITSU LIMITED P3AM-4842-12ENZ0

3

Preface

Fujitsu would like to thank you for purchasing our ETERNUS DX80 S2/DX90 S2 Disk storage system.The ETERNUS DX80 S2/DX90 S2 Disk storage system is designed to be connected to a Fujitsu (PRIMEQUEST orPRIMERGY) or non-Fujitsu servers.This manual describes operation management and maintenance for the ETERNUS DX80 S2/DX90 S2 Diskstorage system.This manual is intended for use of ETERNUS DX Disk storage system in regions other than Japan.Please carefully review the information outlined in this manual.

Twelfth EditionJune 2013

Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries.IBM, AIX, and Tivoli are trademarks of International Business Machines Corporation, registered in manyjurisdictions worldwide. The company names, product names and service names mentioned in this document are registeredtrademarks or trademarks of their respective companies.

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.

About this Manual

Organization

This document is composed of the following seven chapters and three appendices:

● Chapter 1 Components

This chapter describes the components of the ETERNUS DX80 S2/DX90 S2 Disk storage system.

● Chapter 2 Basic Operation

This chapter explains how to turn on and off the ETERNUS DX80 S2/DX90 S2 Disk storage system and howto operate the FUNCTION button on the controller enclosure.

● Chapter 3 Setup

This chapter describes the required settings for operation of the ETERNUS DX80 S2/DX90 S2 Disk storagesystem and provides notes for setting up each function of the ETERNUS DX80 S2/DX90 S2 Disk storagesystem.

● Chapter 4 Operations

This chapter describes the control of the LAN for operation management of the ETERNUS DX80 S2/DX90 S2Disk storage system, and the monitoring the status of the ETERNUS DX80 S2/DX90 S2 Disk storage system.

● Chapter 5 Maintaining Optional Products

This chapter explains how to install optional products in the ETERNUS DX80 S2/DX90 S2 Disk storagesystem.

● Chapter 6 Maintenance

This chapter describes maintenance for the ETERNUS DX80 S2/DX90 S2 Disk storage system.

● Chapter 7 Troubleshooting

This chapter explains troubleshooting when errors occur in the ETERNUS DX80 S2/DX90 S2 Disk storagesystem.

"Event Notification Message List", "Audit Log List", and "Event (SNMP Trap) Display When Using ServerViewOperation Manager" are described as appendices.



4

About this Manual

Warning Notations

Warning signs are shown throughout this manual in order to prevent injury to the user and/or materialdamage. These signs are composed of a symbol and a message describing the recommended level of caution.The following section explains the symbols, their levels of caution, and their meanings as used in this manual.

The following symbols are used to indicate the type of warnings or cautions being described.

WARNINGThis symbol indicates the possibility of serious or fatal injury if the ETERNUS DX80 S2/DX90 S2 Disk storage system is not used properly.

CAUTIONThis symbol indicates the possibility of minor or moderate personal injury, as well as damage to the ETERNUS DX Disk storage system and/or to other users and their property, if the ETERNUS DX80 S2/DX90 S2 Disk storage system is not used properly.

This symbol indicates IMPORTANT information for the user to note when using the ETERNUS DX80 S2/DX90 S2 Disk storage system.

Electric Shock The triangle emphasizes the urgency of the WARNING and CAUTION

contents. Inside the triangle and above it are details concerning the symbol (e.g. Electrical Shock).

No Disassembly The barred "Do Not..." circle warns against certain actions. The action

which must be avoided is both illustrated inside the barred circle and written above it (e.g. No Disassembly).

Unplug The black "Must Do..." circle indicates actions that must be taken. The

required action is both illustrated inside the black disk and written above it (e.g. Unplug).



5

About this Manual

How Warnings are Presented in this Manual

A message is written beside the symbol indicating the caution level. This message is marked with a verticalribbon in the left margin, to distinguish this warning from ordinary descriptions.An example is shown here.

Additional Information

Symbols Used in This Manual

The following is a symbol used throughout this manual:

Abbreviations Used in This Manual

• "ETERNUS DX Disk storage system" refers to the DX80 S2/DX90 S2 Disk storage system.• "CA" refers to a host interface module that is used in an ETERNUS DX Disk storage system to connect to a

server.• "Host Bus Adapter (HBA)" refers to the interface module that is normally used by the server to connect to

ETERNUS DX Disk storage systems. An "FC card", "LAN card", "Network Interface Card (NIC)", "Converged Network Adapter (CNA)", or "SAS card" may be used instead, depending on the server and interface.

• Trademark symbols such as ™ and ® are omitted in this document.

Warning Level Indicator

Warning Type Indicator

Warning Details

To avoid damaging the ETERNUS DX80 S2/DX90 S2 Disk storage system, pay attention to the following points when cleaningthe ETERNUS DX80 S2/DX90 S2 Disk storage system:

- Make sure to disconnect the power when cleaning.- Be careful that no liquid seeps into the ETERNUS DX80 S2/DX90 S2

Disk storage system when using cleaners, etc.- Do not use alcohol or other solvents to clean

the ETERNUS DX80 S2/DX90 S2 Disk storage system.

Warning Layout Ribbon

Example Warning

Functions and know how which can be useful when setting up or operating the ETERNUS DX80 S2/DX90 S2 Disk storage system.



6

Table of Contents

Chapter 1 Components 12

1.1 Controller Enclosure .......................................................................................................... 121.1.1 Front .............................................................................................................................................................. 121.1.2 Rear ............................................................................................................................................................... 131.1.3 Components (Front) ...................................................................................................................................... 141.1.4 Components (Rear) ....................................................................................................................................... 17

1.2 Drive Enclosures ................................................................................................................ 231.2.1 Front .............................................................................................................................................................. 231.2.2 Rear ............................................................................................................................................................... 241.2.3 Components (Front) ...................................................................................................................................... 241.2.4 Components (Rear) ....................................................................................................................................... 27

1.3 Power Distribution Units (for Regions other than EMEA&I) ............................................... 291.3.1 Power Distribution Units (1U) ........................................................................................................................ 291.3.2 Power Distribution Units (2U) ........................................................................................................................ 30

Chapter 2 Basic Operation 32

2.1 Powering On and Off ......................................................................................................... 322.1.1 Switching On and Off the Main Line Switch on the Power Distribution Unit

(for Regions Other than EMEA&I) .................................................................................................................. 322.1.2 Switching On and Off the PSU Switch on the Power Supply Unit .................................................................... 352.1.3 Powering On .................................................................................................................................................. 362.1.4 Powering Off .................................................................................................................................................. 38

2.2 Using the FUNCTION Button .............................................................................................. 39

Chapter 3 Setup 41

3.1 Thin Provisioning Setup .................................................................................................... 413.1.1 Registering the Thin Provisioning Feature License ........................................................................................ 413.1.2 Thin Provisioning Setup ................................................................................................................................. 423.1.3 Restrictions and Notes When Using the Thin Provisioning Function .............................................................. 42

3.2 Flexible Tier (Auto Storage Layering) Setup ...................................................................... 443.2.1 Registering the Thin Provisioning Feature License ........................................................................................ 443.2.2 Flexible Tier Setup ......................................................................................................................................... 453.2.3 Restrictions and Notes ................................................................................................................................... 45

3.3 Storage Migration ............................................................................................................. 47



7

Table of Contents

3.4 Data Encryption ................................................................................................................ 48

3.5 Key Management Server Linkage ...................................................................................... 50

3.6 Eco-mode .......................................................................................................................... 51

3.7 Optimizing Volume Configurations ................................................................................... 533.7.1 RAID Migration .............................................................................................................................................. 543.7.2 Logical Device Expansion (LDE) ..................................................................................................................... 553.7.3 LUN Concatenation ........................................................................................................................................ 563.7.4 Wide Striping ................................................................................................................................................. 57

Chapter 4 Operations 58

4.1 LAN for Operation Management ....................................................................................... 58

4.2 Monitoring ETERNUS DX Disk Storage System Status ........................................................ 604.2.1 LED Status Check ........................................................................................................................................... 604.2.2 Displaying Status via ETERNUS Web GUI ........................................................................................................ 614.2.3 Event Notification .......................................................................................................................................... 624.2.4 Audit Log ....................................................................................................................................................... 63

Chapter 5 Maintaining Optional Products 64

5.1 Installing Drives ................................................................................................................ 645.1.1 Installation Rules for Drives ........................................................................................................................... 655.1.2 Installable Drives ........................................................................................................................................... 655.1.3 Drive Handling Instructions ........................................................................................................................... 665.1.4 Additional Drive Installation Procedure ......................................................................................................... 67

5.2 Installing Drive Enclosures ................................................................................................ 725.2.1 Installation Rules for Drive Enclosures ........................................................................................................... 725.2.2 Installable Drive Enclosures ........................................................................................................................... 725.2.3 Drive Enclosure Handling Instructions ........................................................................................................... 725.2.4 Additional Drive Enclosure Installation .......................................................................................................... 73

5.3 Installing Host Interfaces .................................................................................................. 855.3.1 Installation Rules for Host Interfaces ............................................................................................................. 855.3.2 Installable Host Interfaces ............................................................................................................................. 865.3.3 Host Interface Handling Instructions ............................................................................................................. 86

5.4 Installing Long Wave SFP+ Modules (16Gbit/s) ................................................................. 875.4.1 Installation Rules for Long Wave SFP+ Modules (16Gbit/s) ............................................................................ 875.4.2 Installable Long Wave SFP+ Modules (16Gbit/s) ............................................................................................ 885.4.3 SFP+ Module Handling Instructions ............................................................................................................... 885.4.4 Long Wave SFP+ Modules (16Gbit/s) Installation Procedure .......................................................................... 89



8

Table of Contents

Chapter 6 Maintenance 93

6.1 Periodic Backup ................................................................................................................ 93

6.2 Volume Formatting Time .................................................................................................. 93

6.3 Rebuild/Copyback Process Time ........................................................................................ 94

6.4 Maintenance Service ......................................................................................................... 956.4.1 Maintenance Support Period ......................................................................................................................... 956.4.2 Related Service .............................................................................................................................................. 95

Chapter 7 Troubleshooting 96

7.1 Check List .......................................................................................................................... 96

7.2 Required Information for Inquiries .................................................................................. 102

Appendix A Event Notification Message List 103

A.1 Message Format .............................................................................................................. 103A.1.1 E-mail.......................................................................................................................................................... 103A.1.2 Syslog .......................................................................................................................................................... 105A.1.3 SNMP........................................................................................................................................................... 107A.1.4 Host Sense................................................................................................................................................... 111

A.2 Message List .................................................................................................................... 112A.2.1 Common Terms............................................................................................................................................ 112A.2.2 Error Messages ............................................................................................................................................ 113A.2.3 Warning Messages ...................................................................................................................................... 133A.2.4 Informational Messages .............................................................................................................................. 143A.2.5 Test Messages ............................................................................................................................................. 149A.2.6 Sense Codes................................................................................................................................................. 149

Appendix B Audit Log List 154

Appendix C Event (SNMP Trap) Display When Using ServerView Operation Manager 183



9



10

List of Figures

Figure 1.1 Front view of a 2.5" type controller enclosure.............................................................................................. 12Figure 1.2 Front view of a 3.5" type controller enclosure.............................................................................................. 12Figure 1.3 Rear view of a controller enclosure (single-controller type) ........................................................................ 13Figure 1.4 Rear view of a controller enclosure (dual-controller type) ........................................................................... 13Figure 1.5 Operation panel (2.5" type controller enclosure)......................................................................................... 14Figure 1.6 Operation panel (3.5" type controller enclosure)......................................................................................... 14Figure 1.7 2.5" drive..................................................................................................................................................... 16Figure 1.8 Drive slot numbers (2.5" type controller enclosure)..................................................................................... 16Figure 1.9 3.5" drive..................................................................................................................................................... 16Figure 1.10 Drive slot numbers (3.5" type controller enclosure)..................................................................................... 16Figure 1.11 Controller .................................................................................................................................................... 17Figure 1.12 Host interface (FC, iSCSI 10Gbit/s, FCoE (for FC cable connection)).............................................................. 19Figure 1.13 Host interface (iSCSI 10Gbit/s, FCoE (for Copper Twinax cable connection)) ................................................ 20Figure 1.14 Host interface (iSCSI 1Gbit/s)....................................................................................................................... 20Figure 1.15 Host interface (SAS) .................................................................................................................................... 21Figure 1.16 Power supply unit........................................................................................................................................ 21Figure 1.17 Front view of a 2.5" type drive enclosure ..................................................................................................... 23Figure 1.18 Front view of a 3.5" type drive enclosure ..................................................................................................... 23Figure 1.19 Rear view of a drive enclosure (single-IOM type) ........................................................................................ 24Figure 1.20 Rear view of a drive enclosure (dual-IOM type) ........................................................................................... 24Figure 1.21 LEDs on the front side of the drive enclosure .............................................................................................. 25Figure 1.22 2.5" drive..................................................................................................................................................... 25Figure 1.23 Drive slot numbers (2.5" type drive enclosure)............................................................................................ 26Figure 1.24 3.5" drive..................................................................................................................................................... 26Figure 1.25 Drive slot numbers (3.5" type drive enclosure)............................................................................................ 26Figure 1.26 I/O module .................................................................................................................................................. 27Figure 1.27 Power supply unit........................................................................................................................................ 28Figure 1.28 Power distribution unit for DX80 S2/DX90 S2 (AC200-240V, 1U, Max 2 enclosures connection) .................. 29Figure 1.29 Power distribution unit for DX80 S2/DX90 S2 (AC200-240V, 2U, Max 6 enclosures connection) .................. 30Figure 1.30 Power distribution unit for DX80 S2/DX90 S2 (AC200-240V, 2U, Max 8 enclosures connection) .................. 31Figure 2.1 ON position (marked "|") of the main line switches on a 1U power distribution unit................................... 32Figure 2.2 ON position (marked "|") of the main line switches on a 2U power distribution unit................................... 33Figure 2.3 OFF position (marked "O") of the main line switches on a 1U power distribution unit................................. 33Figure 2.4 OFF position (marked "O") of the main line switches on a 2U power distribution unit................................. 34Figure 2.5 ON position (marked "|") of the PSU switch on a power supply unit ............................................................ 35Figure 2.6 OFF position (marked "O") of the PSU switch on a power supply unit .......................................................... 36Figure 3.1 System configuration for linking with the key management server............................................................. 50Figure 4.1 LAN control (switching of the Master CM) ................................................................................................... 59Figure 4.2 LAN control (when the IP address of the Slave CM is set) ............................................................................ 59Figure 4.3 ETERNUS Web GUI screen ............................................................................................................................ 61Figure 4.4 Event notification ........................................................................................................................................ 63Figure 4.5 Audit logs .................................................................................................................................................... 63Figure 5.1 Positions of 2.5" drive slots.......................................................................................................................... 65Figure 5.2 Positions of 3.5" drive slots.......................................................................................................................... 65Figure 5.3 Installation diagram for a host interface (single-controller type)................................................................ 85Figure 5.4 Installation diagram for host interfaces (dual-controller type).................................................................... 86



11

List of Tables

Table 1.1 Status and meanings of each LED (operation panel (controller enclosure))................................................ 15Table 1.2 Status and meanings of each LED (drive).................................................................................................... 17Table 1.3 Status and meanings of each LED (controller) ............................................................................................ 18Table 1.4 Status and meanings of each LED (power supply unit) ............................................................................... 22Table 1.5 Status and meanings of each LED (in front of drive enclosure) ................................................................... 25Table 1.6 Status and meanings of each LED (drive).................................................................................................... 26Table 1.7 Status and meanings of each LED (I/O module) .......................................................................................... 27Table 1.8 Status and meanings of each LED (power supply unit) ............................................................................... 28Table 4.1 General status of ETERNUS Web GUI ............................................................................................................ 61Table 6.1 Time for volume formatting (disk) .............................................................................................................. 93Table 6.2 Rebuild process time (disk) ......................................................................................................................... 94Table 6.3 Copyback process time (disk) ...................................................................................................................... 94

Chapter 1

Components

This chapter describes the components of the ETERNUS DX Disk storage system.

1.1 Controller Enclosure

An operation panel and drives are installed in the front of the controller enclosure. Controllers and powersupply units are installed in the rear.

1.1.1 Front

■ 2.5" type

Figure 1.1 Front view of a 2.5" type controller enclosure

■ 3.5" type

Figure 1.2 Front view of a 3.5" type controller enclosure

Operation panel 2.5" disk or 2.5" Solid State Drive (SSD)

Flange cover Flange cover

Operation panel


3.5" disk or 3.5" Solid State Drive (SSD)



12

Chapter 1 Components 1.1 Controller Enclosure

1.1.2 Rear

■ Single-controller type

Figure 1.3 Rear view of a controller enclosure (single-controller type)

● Part explanation

• CoverRemove this when installing an additional controller (optional).

■ Dual-controller type

Figure 1.4 Rear view of a controller enclosure (dual-controller type)

Power supply unit (PSU#0) Power supply unit (PSU#1)

Controller (CM#0) Cover


Controller (CM#0) Controller (CM#1)



13


1.1.3 Components (Front)

This section describes the operation panel and the drives in the front of the controller enclosure.

■ Operation panel

An operation panel has LEDs, a Power switch, and a FUNCTION button.

● 2.5" type

Figure 1.5 Operation panel (2.5" type controller enclosure)

● 3.5" type

Figure 1.6 Operation panel (3.5" type controller enclosure)

With a flange cover

CACHE LEDMAINT/ID LEDFAULT LEDREADY LED

Power switch

POWER LED

Without a flange cover

FUNCTION button

With a flange cover

Power switch

CACHE LEDMAINT/ID LEDFAULT LEDREADY LEDPOWER LED

Without a flange cover

FUNCTION button



14



• Power switchThis switch is used to turn on or off the ETERNUS DX Disk storage system.

• FUNCTION buttonHold down the button for three seconds during maintenance to stop the maintenance operation. Holddown the button for three seconds while a maintenance operation is not performed to start themaintenance operation.For a dual-controller type, press the button twice within three seconds during maintenance to switch theMaster CM to the other controller.Press the button three times within three seconds during maintenance to restore the factory defaultsettings of the LAN ports.

• LEDsThe states of LEDs are listed below.

Table 1.1 Status and meanings of each LED (operation panel (controller enclosure))

LED name LED status ETERNUS DX Disk storage system status

POWER(green)

DC power is supplied to the controller enclosure.

READY(green)

The ETERNUS DX Disk storage system is available for use.

FAULT(amber)

The ETERNUS DX Disk storage system is in error status.

(blinks amber)A part of the ETERNUS DX Disk storage system requires preventive maintenance.

MAINT/ID(green)

Maintenance for the ETERNUS DX Disk storage system is in progress.

(blinks green)• As ordered via ETERNUS Web GUI or ETERNUS CLI, the location

of the controller enclosure is identified.

• Maintenance or a status check via ETERNUS Web GUI or ETERNUS CLI is necessary.

CACHE(green)

There is data in the ETERNUS DX Disk storage system cache memory.



15


■ Drives

● 2.5" drives

Figure 1.7 2.5" drive

Figure 1.8 shows the slot number of each drive.

Figure 1.8 Drive slot numbers (2.5" type controller enclosure)

● 3.5" drives



Figure 1.10 Drive slot numbers (3.5" type controller enclosure)

DRIVE READY LED DRIVE FAULT LED

Slo

t#8

Slo

t#9

Slo

t#10

Slo

t#11

Slo

t#12

Slo

t#13

Slo

t#14

Slo

t#15

Slo

t#0

Slo

t#1

Slo

t#2

Slo

t#3

Slo

t#4

Slo

t#5

Slo

t#6

Slo

t#7

Slo

t#16

Slo

t#17

Slo

t#18

Slo

t#19

Slo

t#20

Slo

t#21

Slo

t#22

Slo

t#23

DRIVE READY LED

DRIVE FAULT LED

Slot#0

Slot#4

Slot#8

Slot#1

Slot#5

Slot#9

Slot#2

Slot#6

Slot#10

Slot#3

Slot#7

Slot#11



16




Table 1.2 Status and meanings of each LED (drive)

1.1.4 Components (Rear)

This section describes the controllers and the power supply units in the rear of the controller enclosure.

1.1.4.1 Controllers

The controller contains a CPU, cache memory, System Capacitor Unit (SCU), host interfaces, drive interface (DI)ports, and LAN ports. The controller controls all operations in the ETERNUS DX Disk storage system.

Figure 1.11 Controller

LED name LED status Drive status

DRIVE READY(green)

The drive is in normal status.

(blinks green)

DRIVE FAULT(amber)

• The drive is in error status.

• In response to commands from ETERNUS CLI, the location of the drive is identified.

LAN (MNT) port

ACT LEDsLINK LEDs

DI (OUT) LINKUP LEDREADY/FAULT LED

MASTER LEDUNIT ID LED

CA#0 FAULT LED

PWC port

LINK/FAULT LEDs

DI (OUT) portLAN (RMT) port

Host interface (CA#0) Host interface (CA#1)

CA#1 FAULT LED



17



• LAN (RMT) port, LAN (MNT) portThese ports are RJ-45 connectors for LAN cables.

• Host interface (CA#0), host interface (CA#1)Install host interfaces. For details, refer to "Host interfaces" (page 19).

• DI (OUT) portThis port is used to connect a controller enclosure to a drive enclosure with a QSFP cable.

• PWC portThis port is used to connect a power synchronization unit with an RS232C cable.


Table 1.3 Status and meanings of each LED (controller)

LED name LED status Controller status

READY/FAULT(green)

The controller is in normal status.

(amber)• The controller is performing the initial setup after the power

is turned on.

• The controller is in error status.(blinks amber)

MASTER(green)

The controller is set as a Master CM.

UNIT ID(blinks green)

• As ordered via ETERNUS Web GUI or ETERNUS CLI, the location of the controller is identified.

• System Capacitor Unit (SCU) is charging.

CA FAULT(amber)

The host interface is in error status.

LINK/FAULT(green)

The link between the host interface port and the destination has been established.

(amber)The host interface port is in error status.

DI (OUT) LINKUP(green)

The link between the DI (OUT) port and the destination port has been established.

ACT(green)

The controller is sending or receiving data via the LAN port (for operation management).

LINK(green)

The link between the LAN port (for operation management) and the destination has been established.



18


■ Host interfaces

A host interface is a board that has interface ports to connect a controller to the server.There are six types of host interfaces: FC 16Gbit/s, FC 8Gbit/s, iSCSI 10Gbit/s, iSCSI 1Gbit/s, FCoE, and SAS.

● FC, iSCSI 10Gbit/s, FCoE (for FC cable connection)

Figure 1.12 Host interface (FC, iSCSI 10Gbit/s, FCoE (for FC cable connection))

• Part explanation

- Host interface ports (FC, iSCSI 10Gbit/s, FCoE (for FC cable connection)) (from left to right: Port#0 and Port#1 in CA#0, Port#0 and Port#1 in CA#1)These are the Dual LC connectors to connect FC cables.

Port#0 Port#1 Port#0 Port#1

FC iSCSI 10Gbit/s FCoE

Installed host interfaces in the controller




19


● iSCSI 10Gbit/s, FCoE (for Copper Twinax cable connection)

Figure 1.13 Host interface (iSCSI 10Gbit/s, FCoE (for Copper Twinax cable connection))


- Host interface ports (iSCSI 10Gbit/s, FCoE (for Copper Twinax cable connection)) (from left to right: Port#0 and Port#1 in CA#0, Port#0 and Port#1 in CA#1)These are the connectors to connect Copper Twinax cables.

● iSCSI 1Gbit/s

Figure 1.14 Host interface (iSCSI 1Gbit/s)


- Host interface ports (iSCSI) (from left to right: Port#0 and Port#1 in CA#0, Port#0 and Port#1 in CA#1)These are the RJ-45 connectors to connect LAN cables.

Port#0 Port#1 Port#0 Port#1

iSCSI 10Gbit/s, FCoE



iSCSI 1Gbit/s

Port#0 Port#1Port#0 Port#1





20


● SAS

Figure 1.15 Host interface (SAS)


- Host interface ports (SAS) (from left to right: Port#0 and Port#1 in CA#0, Port#0 and Port#1 in CA#1)These are the SFF-8088 connectors to connect miniSAS cables.

■ System Capacitor Unit (SCU)

A SCU is installed in a controller as a backup power source in case of power outage.

The SCU is charged from an external power source while the ETERNUS DX Disk storage system is runningnormally. If a power outage is detected, data in the cache memory is saved to the non-volatile memory in thecontroller using the SCU. The saved data is retained in the non-volatile memory indefinitely.

1.1.4.2 Power Supply Units

The power supply unit transforms input AC power from a power socket to DC power and supplies power to eachcomponent.Each power supply unit contains fans.

Figure 1.16 Power supply unit

SAS

Port#0 Port#1Port#0 Port#1



InletPSU switchPSU FAIL LED

AC MISSING LED

POWER LED

FAN FAIL LED



21



• InletThis inlet is used to connect a power cord.

• PSU switchThis switch is used to turn on and off the AC power supply.


Table 1.4 Status and meanings of each LED (power supply unit)

LED name Power supply unit status

POWER PSU FAIL AC MISSING FAN FAIL

(blinks green) (off) (off) (off)

AC power is supplied to the power supply unit but the ETERNUS DX Disk storage system (DC power) is not turned on.

(green) (off) (off) (off)

The power of the ETERNUS DX Disk storage system (DC power) is turned on and the power supply unit is operating normally.

(off) (off) (off) (off)

AC power is not supplied to power sup-ply units.

(off) (amber) (amber) (off or amber)

AC power is not supplied to this power supply unit, but AC power is supplied to the other power supply unit.

(off) (amber) (amber) (amber)

The power supply unit or the fan in the power supply unit is in error status.



22

Chapter 1 Components 1.2 Drive Enclosures

1.2 Drive Enclosures

LEDs, a DE-ID (drive enclosure number) display panel, and drives are installed on the front side of the driveenclosure. I/O modules and power supply units are installed in the rear.

There are two types of drive enclosures: a 2.5" type and a 3.5" type.

1.2.1 Front

■ 2.5" type

Figure 1.17 Front view of a 2.5" type drive enclosure

■ 3.5" type

Figure 1.18 Front view of a 3.5" type drive enclosure

LED


2.5" disk or 2.5" Solid State Drive (SSD)

DE-ID (drive enclosure number) display panel

Flange cover

3.5" disk or 3.5" Solid State Drive (SSD)LED

DE-ID (drive enclosure number) display panelFlange cover



23


1.2.2 Rear

■ Single-IOM type

Figure 1.19 Rear view of a drive enclosure (single-IOM type)


• CoverRemove this when installing an additional I/O module (optional).

■ Dual-IOM type

Figure 1.20 Rear view of a drive enclosure (dual-IOM type)

1.2.3 Components (Front)

This section describes LEDs, a DE-ID (drive enclosure number) display panel, and drives of the front of thedrive enclosure.

■ DE-ID (drive enclosure number) display panel

The DE-ID (drive enclosure number) of the drive enclosure is displayed.

I/O module (IOM6#0)


Cover

I/O module (IOM6#0)

Power supply unit (PSU#0)

I/O module (IOM6#1)

Power supply unit (PSU#1)



24


■ LEDs

Figure 1.21 LEDs on the front side of the drive enclosure

The states of LEDs are listed below.

Table 1.5 Status and meanings of each LED (in front of drive enclosure)

■ Drives

● 2.5" drives


LED name LED status Drive enclosure status

LINE(green)

AC power is supplied to the drive enclosure.

FAULT(amber)

The drive enclosure is in error status.

POWER(green)

The drive enclosure is operating normally.

2.5" type 3.5" type

LINE LED

POWER LED

FAULT LED

LINE LED

POWER LED

FAULT LED

DRIVE READY LED DRIVE FAULT LED



25



Figure 1.23 Drive slot numbers (2.5" type drive enclosure)

● 3.5" drives



Figure 1.25 Drive slot numbers (3.5" type drive enclosure)



Table 1.6 Status and meanings of each LED (drive)

LED name LED status Drive status

DRIVE READY(green)

The drive is in normal status.

(blinks green)

DRIVE FAULT(amber)

• The drive is in error status.

• In response to commands from ETERNUS CLI, the location of the drive is identified.

Slo

t#8

Slo

t#9

Slo

t#10

Slo

t#11

Slo

t#12

Slo

t#13

Slo

t#14

Slo

t#15

Slo

t#0

Slo

t#1

Slo

t#2

Slo

t#3

Slo

t#4

Slo

t#5

Slo

t#6

Slo

t#7

Slo

t#16

Slo

t#17

Slo

t#18

Slo

t#19

Slo

t#20

Slo

t#21

Slo

t#22

Slo

t#23

DRIVE READY LED

DRIVE FAULT LED

Slot#0

Slot#4

Slot#8

Slot#1

Slot#5

Slot#9

Slot#2

Slot#6

Slot#10

Slot#3

Slot#7

Slot#11



26


1.2.4 Components (Rear)

This section describes the I/O modules and the power supply units in the rear of the drive enclosure.

■ I/O module

The I/O module is a component that controls how the controller and the drives interact.

Figure 1.26 I/O module


• DI (OUT) port, DI (IN) portThese ports are connectors for QSFP cables.


Table 1.7 Status and meanings of each LED (I/O module)

LED name LED status I/O module status

FAULT(amber)

The I/O module is in error status.

DI (OUT) LINKUP(green)

The link between the DI (OUT) port and the destination port has been established.

DI (IN) LINKUP(green)

The link between the DI (IN) port and the source port has been established.

DI (OUT) LINKUP LED

DI (OUT) port

DI (IN) LINKUP LED

DI (IN) portFAULT LED

These are not used.



27


■ Power supply units

The power supply unit transforms input AC power from a power socket to DC power and supplies power to eachcomponent.Each power supply unit contains fans.

Figure 1.27 Power supply unit


• InletThis inlet is used to connect a power cord.

• PSU switchThis switch is used to turn on and off the AC power supply.


Table 1.8 Status and meanings of each LED (power supply unit)

LED name Power supply unit status

POWER PSU FAIL AC MISSING FAN FAIL

(green) (off) (off) (off)

AC power is supplied to the power supply unit.

(off) (off) (off) (off)

AC power is not supplied to the power supply unit.

(off) (amber) (amber) (off or amber)

AC power is not supplied to this power supply unit, but AC power is supplied to the other power supply unit.

(off) (amber) (amber) (amber)

The power supply unit or the fan in the power supply unit is in error status.

InletPSU switchPSU FAIL LED

AC MISSING LED

POWER LED

FAN FAIL LED



28

Chapter 1 Components 1.3 Power Distribution Units (for Regions other than EMEA&I)

1.3 Power Distribution Units (for Regions other than EMEA&I)

There are two sizes for power distribution units: 1U and 2U.

1.3.1 Power Distribution Units (1U)

The 1U power distribution unit has four outlets and two inlets.

■ Power distribution unit for DX80 S2/DX90 S2 (AC200-240V, 1U, Max 2 enclosures connection)

Figure 1.28 Power distribution unit for DX80 S2/DX90 S2 (AC200-240V, 1U, Max 2 enclosures connection)


• Outlet (OUTPUT)This is a socket (IEC60320-C13) for outgoing power supply. This socket is used to connect a power cord (ACoutput cable).

• Inlet (INPUT)This is a socket (IEC60320-C14) for incoming power supply. This socket is used to connect a power cord (ACinput cable).

• Main line switchThis turns on and off the power distribution unit.

Inlets (INPUT)

Outlets (OUTPUT)

Main line switches



29


1.3.2 Power Distribution Units (2U)

There are 2U power distribution units that can connect up to six enclosures and 2U power distribution unitsthat can connect up to eight enclosures.


There are 12 outlets.





Main line switches

Outlets (OUTPUT)



30



There are 16 outlets.





Outlets (OUTPUT)

Main line switches



31

Chapter 2

Basic Operation

This chapter explains how to turn on and off the ETERNUS DX Disk storage system and how to operate theFUNCTION button on the controller enclosure.

2.1 Powering On and Off

This section explains how to turn on and off the ETERNUS DX Disk storage system.

2.1.1 Switching On and Off the Main Line Switch on the Power Distribution Unit (for Regions Other than EMEA&I)

This section explains how to switch the main line switch of the power distribution unit to ON and OFF.

■ To switch to ON

Turn the main line switch of the power distribution unit to the ON position (marked "I").

● For 1U power distribution unit

Figure 2.1 ON position (marked "|") of the main line switches on a 1U power distribution unit

Make sure to turn all the main line switches to the ON position.

Main line switch



32

Chapter 2 Basic Operation 2.1 Powering On and Off


Figure 2.2 ON position (marked "|") of the main line switches on a 2U power distribution unit

■ To switch to OFF

Turn the main line switch of the power distribution unit to the OFF position (marked "O").


Figure 2.3 OFF position (marked "O") of the main line switches on a 1U power distribution unit

Main line switch

If the ETERNUS DX Disk storage system must be turned off, such as before any inspections of power supply devices are performed, turn off the ETERNUS DX Disk storage system by using the procedure described in "2.1.4 Powering Off" (page 38), turn all the PSU switches of the power supply unit to the OFF position, and turn the main line switch to the OFF position.

Main line switch



33



Figure 2.4 OFF position (marked "O") of the main line switches on a 2U power distribution unit

When turning the main line switch to ON (marked "I") right after turning the main line switch to OFF (marked "O"), turn it back to ON (marked "I") after the POWER LED of the power supply unit has turned off completely.

Main line switch



34


2.1.2 Switching On and Off the PSU Switch on the Power Supply Unit

This section explains how to switch the PSU switch of the power supply unit to ON and OFF in each enclosure.

■ To switch to ON

Turn the PSU switch of the power supply unit to the ON position (marked "|").

Figure 2.5 ON position (marked "|") of the PSU switch on a power supply unit

AC power is supplied to an enclosure.• For the controller enclosure, the POWER LED on the power supply unit blinks green.• For the drive enclosure, the POWER LED on the power supply unit and the LINE LED on the front emit green

lights and the fan revolves at high speed for 30 seconds.

Make sure all of the PSU switches are in the ON position.


Drive enclosure

Controller enclosure



35


■ To switch to OFF

Turn the PSU switch of the power supply unit to the OFF position (marked "O").

Figure 2.6 OFF position (marked "O") of the PSU switch on a power supply unit

Check that the POWER LED of the power supply unit is off.

2.1.3 Powering On

This section explains how to turn on the ETERNUS DX Disk storage system.

The following methods can be used to turn the power on:

• Via the Power switchPress the Power switch to turn on the ETERNUS DX Disk storage system.

• Via the power synchronized unitUse the power synchronized unit to turn on the ETERNUS DX Disk storage system.

• Via the Wake On LAN functionUse the Wake On LAN function to turn on the power.

For normal operation, there is no need to switch to OFF position.

Drive enclosure


Power Supply Unit PSU#0 Power Supply Unit PSU#1



36


This section explains how to use the Power switch to turn on the ETERNUS DX Disk storage system. For otherprocedures, refer to the related manuals.

Procedure

1 Press the Power switch of the controller enclosure.

The POWER LEDs on the controller enclosure and the drive enclosures are turned on.

Before turning on the ETERNUS DX Disk storage system, make sure that the main line switches of the power distribution units and the PSU switches on the power supply units of the ETERNUS DX Disk storage system are "ON".Do not turn the main line switches of the power distribution units and the PSU switches on the ETERNUS DX Disk storage system to the OFF position.

• After turning the power on, it takes about two minutes for the ETERNUS DX Disk storage system to become READY (i.e. the READY LED turns on). If an error is detected during the initial power-on diagnostic phase, a longer time (up to ten minutes) may be required before the READY LED turns on.

• Before turning the server on, check that the ETERNUS DX Disk storage system and the network devices that connect the ETERNUS DX Disk storage system and the server are all in READY status. If the server is turned on while any of these devices are not in READY status, the server may not be able to recognize the ETERNUS DX Disk storage system.

• When turning on the power in conjunction with the power synchronized unit, perform the appropriate waiting process so that the ETERNUS DX Disk storage system is in the READY status before the server is turned on. Since it takes up to ten minutes before the ETERNUS DX Disk storage system change to READY status when an error is detected for a component during the initial power-on diagnostic phase, take this into consideration and specify an appropriate waiting process that is sufficient.

• If the Auto Power function is enabled via ETERNUS Web GUI or ETERNUS CLI, the ETERNUS DX Disk storage system is automatically turned on when power is supplied to the ETERNUS DX Disk storage system.

• If the Power Resume function is enabled via ETERNUS Web GUI or ETERNUS CLI, the ETERNUS DX Disk storage system is automatically turned on after the power is restored.

Before turning on the ETERNUS DX Disk storage system, check that the LINE LEDs of the drive enclosures are green.


Drive enclosure

Drive enclosure

Power switch



37


2 After about two minutes, check that the READY LED of the controller enclosure is lit up.

End of procedure

2.1.4 Powering Off

This section explains how to turn off the ETERNUS DX Disk storage system.

The following methods can be used to turn the power off:

• Via the Power switchPress the Power switch to turn off the ETERNUS DX Disk storage system.

• Via the power synchronized unitUse the power synchronized unit to turn off the ETERNUS DX Disk storage system.

• Via ETERNUS Web GUI or ETERNUS CLIUse ETERNUS Web GUI or ETERNUS CLI to turn off the ETERNUS DX Disk storage system.

This section explains how to use the Power switch to turn off the ETERNUS DX Disk storage system. For otherprocedures, refer to the related manuals.


Drive enclosure

Drive enclosure

POWERREADYFAULT

MAINT/IDCACHE

LINEFAULT

POWER

• When turning off the ETERNUS DX Disk storage system, the power shuts off after the data in the cache memory is written to the drives. Therefore, it may take one minute (maximum six minutes) for the power supply to be completely turned off.

• Do not turn off the power of the ETERNUS DX Disk storage system, the network devices that connect the ETERNUS DX Disk storage system and the server while the server is operating, as this may result in the loss of data or prevent data from being saved.

• When using a power synchronized unit for power control, make sure to turn off the power with the server. Even if the ETERNUS DX Disk storage system is turned off by using the Power switch, the power synchronization function automatically turns on the power.



38

Chapter 2 Basic Operation 2.2 Using the FUNCTION Button

Procedure

1 Press and hold the Power switch of the controller enclosure for four seconds or more.

The READY LED of the controller enclosure is turned off.

2 The ETERNUS DX Disk storage system power is turned off.The POWER LEDs on the controller enclosure and the drive enclosures are turned off.

End of procedure

2.2 Using the FUNCTION Button

This section explains how to use the FUNCTION button of the controller enclosure.The following settings can be performed by using the FUNCTION button:

• Switching the Master CM to the other controller for a dual-controller type

• Restoring the factory default settings (network environment settings and firewall settings) of the LAN ports

Press the Power switch only once. If the Power switch is pressed again between the time of the READYLED turning off and the POWER LED turning off, the ETERNUS DX Disk storage system power may turnon.


Drive enclosure

Drive enclosure

Power switch

For a dual-controller type, the controller through which the ETERNUS DX Disk storage system is set up and operated is called the "Master CM", while the other controller is called the "Slave CM".The single-controller type only has a "Master CM" controller.



39

Chapter 2 Basic Operation 2.2 Using the FUNCTION Button

The following procedure explains how to use the FUNCTION button.

Procedure

1 Remove the flange cover of the controller enclosure.

2 Change the status of the ETERNUS DX Disk storage system to maintenance status.Use the pin that is provided with the ETERNUS DX Disk storage system to push down the FUNCTIONbutton for three seconds.

The ETERNUS DX Disk storage system is in maintenance status when the MAINT/ID LED is green.

3 Use the FUNCTION button to change the following settings:

• Switching the Master CM to the other controller for a dual-controller typeUse the pin to push down the FUNCTION button twice within three seconds.The MASTER LED for the controller that is set as the Master CM is green.

• Restoring the factory default settings of the LAN portsUse the pin to push down the FUNCTION button three times within three seconds.After the default settings of the LAN ports are restored, the MAINT/ID LED blinks green for a fewseconds.

4 Release maintenance status.Use the pin to push down the FUNCTION button for three seconds. The ETERNUS DX Disk storage system is not in maintenance status when the MAINT/ID LED is off.

5 Attach the flange cover.

End of procedure



40

Chapter 3

Setup

This chapter describes the required settings for operation of the ETERNUS DX Disk storage system and providesnotes for setting up each function of the ETERNUS DX Disk storage system. Note that the Thin Provisioningfunction cannot be used for a single-controller type.

3.1 Thin Provisioning Setup

The Thin Provisioning function virtualizes and allocates storage capacity. This reduces physical storagecapacity and unused capacity can be used more efficiently.The user can start operation of the ETERNUS DX Disk storage system with a small disk capacity by allocatinglarge virtual disks to the server. Physical disks can be added according to the required capacity withoutaffecting the server.The Thin Provisioning balancing function can be used to balance the physical allocation capacity of a ThinProvisioning Volume (TPV) among RAID groups and to distribute I/O access for the TPV to the RAID groups inthe pool.In addition, the Thin Provisioning function can be used more efficiently by using the Zero Reclamationfunction. The Zero Reclamation function releases physical areas with all zero bits.

To use the Thin Provisioning function, register the Thin Provisioning Feature License in the ETERNUS DX Diskstorage system and set up the Thin Provisioning function.

3.1.1 Registering the Thin Provisioning Feature License

■ For the EMEA&I region

After the Thin Provisioning Feature License is purchased, it is activated by registering a Thin ProvisioningFeature license key in the ETERNUS DX Disk storage system.When purchasing the Thin Provisioning Feature, a Transaction Authentication Number (TAN) and the URL ofthe web-site from which the license key may be obtained are notified by e-mail.

■ For regions other than EMEA&I

When the Thin Provisioning Feature License is purchased separately, register the Thin Provisioning FeatureLicense in the ETERNUS DX Disk storage system. For details on how to register the license, refer to the "Feature activation licenses" document that is providedwith the Thin Provisioning Feature License.

The Thin Provisioning Feature License is a unique license to each ETERNUS DX Disk storage system. This license cannot be registered in other ETERNUS DX Disk storage systems.



41

Chapter 3 Setup 3.1 Thin Provisioning Setup

3.1.2 Thin Provisioning Setup

For details on the setup and operation management of the Thin Provisioning function, refer to "ETERNUS WebGUI User’s Guide" or "ETERNUS CLI User’s Guide".For details on operation management when using ETERNUS SF Storage Cruiser, refer to "ETERNUS SF StorageCruiser Operation Guide".

3.1.3 Restrictions and Notes When Using the Thin Provisioning Function

The restrictions and points to note when using the Thin Provisioning function are as follows:• Storage capacity virtualization

- The maximum number of Thin Provisioning Pools (TPP) is 60 for the ETERNUS DX80 S2 and 120 for the ETERNUS DX90 S2.

- The maximum TPP capacity is 128TB.- The maximum Thin Provisioning Volume (TPV) capacity is 128TB. Note that the total TPV capacity must

be smaller than the maximum capacity of the TPP.- Physical allocation to the created virtual volume is performed in units of 32MB when write operations

from a host to a TPV is performed.- If the usage of a TPP exceeds the threshold, a notification is sent to the address (SNMP Trap, e-Mail, or

syslog) that is specified by the event notification function of ETERNUS Web GUI or ETERNUS CLI. In addition, the used capacity can be checked with ETERNUS SF Storage Cruiser. Make sure to add drives to expand the TPP capacity before insufficient TPP capacity is detected.

- The Thin Provisioning function is unsuitable for using with OSes that write meta-information to all of the LUNs when creating a file system.

- It is recommended that backing up of a TPV is performed in file units. If a complete backup is performed, areas that are not allocated to the drives are also backed up as dummy data. The dummy data is also restored when backed up data is restored for a TPV. If this occurs, drive allocation for the entire volume capacity is required and the Thin Provisioning function does not work.

- Do not use the Thin Provisioning function when tuning performance.- The encryption status of a TPP cannot be changed once the TPP is created. To create an encrypted TPP,

specify encryption by firmware when creating the TPP or use Self Encrypting Drives (SED) to configure the TPP.

• When the Thin Provisioning Feature License is purchased as a factory-installed option, the license is registered as a factory setting.Attach the license label plate provided with the Thin Provisioning Feature License to the rack rail near the ETERNUS DX Disk storage system which holds its license, for future reference.

• Check whether the license has already been registered using the provided license label plate or the ETERNUS Web GUI screen. In the following conditions, the license is registered.

- The license key (barcode and 16-character alphanumerical string) is printed on the "LicenseKey" field of the license label plate.

- In the Thin Provisioning [License] screen of ETERNUS Web GUI, "Registered" is shown in "Status".



42

Chapter 3 Setup 3.1 Thin Provisioning Setup

- Caution should be taken when re-recognizing volume capacity dynamically from a server system after performing TPV capacity expansion with the Thin Provisioning Volume capacity expansion function. Some platform types (server OS) and versions cannot recognize the expanded volume capacity. To expand capacity dynamically, refer to the relevant manuals of each OS and file system.This caution does not apply when creating a new system after TPV capacity expansion.

• Balancing TPV allocation- Balancing TPV allocation can be performed for TPVs in the same TPP.- The total number of TPV balancing, FTRP balancing, RAID Migration, and Flexible Tier Migration pro-

cesses that can be performed at the same time is 32.- TPV balancing cannot be performed at the same time as RAID Migration to a different TPP for which the

target TPV does not belong.- If RAID groups that cannot perform balancing (such as RAID groups without free capacity) exist in a TPP,

balancing of physical allocation capacity is performed among the other RAID groups in the TPP. If this occurs, the balancing level after the balancing process is complete may not be "High".

- When TPV balancing is performed, an area for the work volume (the destination TPV which has the same capacity as the source TPV) is secured in the TPP to which the TPV belongs. As a result, the status of the TPP may temporarily become alarm status (the TPP usage exceeds the "Caution" or "Warning" threshold). The alarm status is released when balancing is completed successfully.

- If the capacity of the TPP to which the target TPV belongs is expanded during a TPV balancing process, the balancing level might be less than before.

- TPV balancing cannot be performed for volumes that are undergoing Zero Reclamation.• Zero Reclamation

- Zero Reclamation cannot be performed for volumes that are undergoing RAID Migration.- Zero Reclamation cannot be performed for volumes that are undergoing TPV balancing.



43

Chapter 3 Setup 3.2 Flexible Tier (Auto Storage Layering) Setup

3.2 Flexible Tier (Auto Storage Layering) Setup

The automatic storage layering function automatically reallocates data in the ETERNUS DX Disk storagesystem according to the data access frequency to optimize performance and costs. This function performsstorage layering by moving frequently accessed data to high speed drives such as SSDs and less frequentlyaccessed data to cost effective disks with large capacities.Data is reallocated in smaller units (blocks) than volumes.Data is redistributed based on the performance information that is monitored and obtained by ETERNUS SFStorage Cruiser. This function enables Nearline disks to be used while maintaining performance, reducing thestartup cost.When drives are added to a pool, the physical capacity is allocated unevenly among the RAID groups in thepool. By using the Flexible Tier Pool balancing function, the allocated physical capacity as well as the usagerate of the physical disks in the pool can be balanced.

To use the Flexible Tier (auto storage layering) function, register the Thin Provisioning Feature License in theETERNUS DX Disk storage system and enable the Flexible Tier function.

3.2.1 Registering the Thin Provisioning Feature License


After the Thin Provisioning Feature License is purchased, it is activated by registering a Thin ProvisioningFeature license key in the ETERNUS DX Disk storage system.When purchasing the Thin Provisioning Feature, a Transaction Authentication Number (TAN) and the URL ofthe web-site from which the license key may be obtained are notified by e-mail.


When the Thin Provisioning Feature License is purchased separately, register the Thin Provisioning FeatureLicense in the ETERNUS DX Disk storage system. For details on how to register the license, refer to the "Feature activation licenses" document that is providedwith the Thin Provisioning Feature License.

The Thin Provisioning Feature License is a unique license to each ETERNUS DX Disk storage system. This license cannot be registered in other ETERNUS DX Disk storage systems.



44


3.2.2 Flexible Tier Setup

Settings and operation management for the Flexible Tier function are performed with ETERNUS SF StorageCruiser. For details on settings and operation management when using Flexible Tier, refer to "ETERNUS SF StorageCruiser Operation Guide for Optimization Option".

3.2.3 Restrictions and Notes

■ When using the Flexible Tier function

The restrictions and points to note when using the Flexible Tier function are as follows:• Up to 30 Flexible Tier Pools (FTRP) can be registered in an ETERNUS DX Disk storage system.• Two or three Flexible Tier Sub Pools (FTSP) can be registered in an FTRP. The maximum number of tiers is

three.• Up to 90 FTSPs can be registered in an ETERNUS DX Disk storage system. Note that the total maximum

number of TPPs and FTSPs is 120. The maximum capacity of an FTSP is 128TB.• The maximum capacity of a Flexible Tier Volume (FTV) is 128TB. Note that the total capacity of FTVs must

be less than the maximum capacity of FTSPs.• 32 work volumes (with a physical capacity of 0MB) are created when the Flexible Tier function is enabled.

The maximum number of volumes that can be created in the ETERNUS DX Disk storage system is reduced by 32.

• To encrypt data, specify encryption for FTRP when creating an FTRP or use Self Encrypting Drives (SED) to configure the FTSP.

• If usage of an FTRP or an FTV exceeds the threshold, a notification is sent. For FTRPs, a notification (SNMP Trap, e-mail, or syslog) is also sent to the address that is specified by the event notification setting of ETERNUS Web GUI or ETERNUS CLI. Make sure to add drives to expand the FTSP capacity by using ETERNUS SF Storage Cruiser before insufficient FTRP capacity is detected.

• When the Thin Provisioning Feature License is purchased as a factory-installed option, the license is registered as a factory setting.Attach the license label plate provided with the Thin Provisioning Feature License to the rack rail near the ETERNUS DX Disk storage system which holds its license, for future reference.

• Check whether the license has already been registered using the provided license label plate or the ETERNUS Web GUI screen. In the following conditions, the license is registered.

- The license key (barcode and 16-character alphanumerical string) is printed on the "LicenseKey" field of the license label plate.

- In the Thin Provisioning [License] screen of ETERNUS Web GUI, "Registered" is shown in "Status".



45


■ When using the FTRP balancing

The restrictions and points to note when using the FTRP balancing function are as follows:• Balancing FTRP can be performed for FTSPs in the same TPP.• The total number of TPV balancing, FTRP balancing, RAID Migration, and Flexible Tier Migration processes

that can be performed at the same time is 32.• The FTRP balancing function equalizes unevenly allocated physical area in the RAID groups that configure

an FTSP. Note that migrating a physical area to a different FTSP is not available.• If the free capacity in the FTSP becomes insufficient while FTRP balancing is being performed, an error

occurs and the balancing session ends abnormally. Note that insufficient physical capacity cannot be replaced by other FTSPs.

• When FTRP balancing is performed, an area for the work volume (the destination FTV which has the same capacity as the source FTV) is secured in the FTRP to which the FTV belongs. As a result, the status of the FTRP may temporarily become alarm status (the FTRP usage exceeds the "Caution" or "Warning" threshold). The alarm status is released when balancing is completed successfully.

• If the capacity of the FTRP is expanded during an FTRP balancing process, the balancing level might be less than before.

• FTRP balancing cannot be performed for volumes that are undergoing Zero Reclamation.• FTRP balancing may not be performed regardless of what FTRP balancing level is used. FTRP balancing

availability depends on the physical allocation status of FTVs.



46

Chapter 3 Setup 3.3 Storage Migration

3.3 Storage Migration

Storage Migration is a function that migrates the volume data from an old storage system to volumes in anew storage system without using a server in cases such as when replacing a storage system.The source storage system and destination ETERNUS DX Disk storage system are physically connected usingcables. Data read from the target volume in the Migration Source is written to the Destination volume in theETERNUS DX Disk storage system.Since Storage Migration is controlled by ETERNUS DX Disk storage system controllers, no additional softwarefunctions are required.

This section describes the restrictions and notes on using Storage Migration.For details on the Storage Migration procedure, refer to "ETERNUS Web GUI User's Guide".

• Data migration is performed in units of volumes.• Up to 16 migration source devices can be specified.• Up to eight migration paths can be created for each migration source device.• The maximum number of migration volumes for each migration path is 512.• Storage Migration can be performed when the migration destination device has a larger volume capacity

than the migration source device.• Volumes for which the volume type (Standard/Open, TPV, or SDV) is available for the host affinity settings

can be specified as migration source volumes.Standard/Open, WSV, TPV, or FTV type volumes can be specified as migration destination volumes.

• Storage Migration can be performed if the following conditions are satisfied:- Stop server access to the migration source volumes and the migration destination volumes.

When "Migration + Full Compare" or "Full Compare" is specified for the operation mode, stop the host access to all of the volumes in the migration destination device.

- Do not specify volumes with existing copy sessions as migration source or migration destination volumes.

- Do not specify volumes that are being formatted as migration source volumes.- Do not perform the [Start RAID Group Diagnosis] function or the [Start Disk Diagnosis] function in a

migration source device.• The FC port mode of the migration destination device must be changed to "Initiator" and the port

parameters must be set.• The migration paths must be deleted after Storage Migration is complete.

When deletion of the migration paths is complete, change the FC port mode from "Initiator" to "CA" and set the port parameters. Set the host affinity setting to recognize migration destination volumes from the server.



47

Chapter 3 Setup 3.4 Data Encryption

3.4 Data Encryption

Encrypting data as it is being written to the drive prevents information leakage caused by fraudulentdecoding.Even if a drive is removed and stolen by malicious third parties, data cannot be decoded.The encryption function only encrypts the data stored on the drives, so server access results in thetransmission of plain text. Therefore, this function is effective against leakage of data being transferred viasneaker net, but has no effect on data leakage via server access.

The following two types of data encryption are supported:• Self Encrypting Drive function

This function encrypts data by using Self Encrypting Drives (SEDs).SEDs are locked the instant that they are removed from the storage system, which ensures no data is reador written with these drives. This encryption prevents information leakage from drives that are stolen orreplaced for maintenance. This function also reduces discarding costs because SEDs do not need to bephysically destroyed.

• Volume conversion encryption functionThis function encrypts data on a volume basis by using the firmware of the ETERNUS DX Disk storagesystem.Encryption can be performed in volume units according to the importance of the data. No additionalhardware is required to perform volume encryption.

The restrictions and notes on encrypting data are described below.

■ Self Encrypting Drive function

For the procedure to perform data encryption using Self Encrypting Drives (SEDs), refer to "ETERNUS Web GUIUser’s Guide" or "ETERNUS CLI User’s Guide".

• Register the SED authentication key before installing SEDs in the ETERNUS DX Disk storage system. If a SED is installed without registering the SED authentication key, data leakage in a SED that is removed may occur.

• The common key can only be set once in the ETERNUS DX Disk storage system. This key can be used for all the SEDs that are installed in the ETERNUS DX Disk storage system. The common key cannot be changed or deleted after being set. The common key is used to authenticate RAID groups when key management server linkage is not used.



48

Chapter 3 Setup 3.4 Data Encryption

■ Volume conversion encryption function

For details on the data encryption procedure, refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLI User’sGuide".

• The encryption method for encrypted volumes cannot be changed. Encrypted volumes cannot be changed to unencrypted volumes. To change the encryption method or cancel the encryption for a volume, back up the data in the encryptedvolume, delete the encrypted volume, and restore the backed up data.

• It is recommended that the copy source volume and the copy destination volume use the same encryption method for remote copy between encrypted volumes.

• When copying encrypted volumes (using Advanced Copy or copy operations via server), transfer performance may not be as good as when copying unencrypted volumes.

• SDPVs cannot be encrypted after they are created. To create an encrypted SDPV, set encryption when creating a volume.

• Thin Provisioning Volumes (TPVs) cannot be encrypted individually. Rather, the encryption status of TPVs depends on that of the TPP to which the TPVs belong.

• Flexible Tier Volumes (FTVs) cannot be encrypted individually. Rather, the encryption status of TPVs depends on that of the Flexible Tier Pool (FTRP) to which the FTVs belong.



49

Chapter 3 Setup 3.5 Key Management Server Linkage

3.5 Key Management Server Linkage

By linking with the key management server, the SEDs and the SED authentication key can be managedseparately and makes it possible to manage the authentication key more securely. Security requirements canbe satisfied by regularly changing the authentication key.Note that ETERNUS SF KM is required when linking with the key management server.

Figure 3.1 System configuration for linking with the key management server

• To use the authentication key in a key server, a key group needs to be created. Multiple RAID groups can be registered in a key group. Note that only one key group can be created in each ETERNUS DX Disk storage system. Only one authentication key can be specified for each key group. The authentication key for a key group can be changed.

• Setting a period of time for the validity of the authentication key in the key server by using the ETERNUS DX Disk storage system enables the key to be automatically updated by obtaining a new authentication key from the key server before the validity of the key expires. Access from the host (server) can be maintained even if the SED authentication key is changed during operation.

• When linking with the key management server, the ETERNUS DX Disk storage system obtains the SED authentication key from the key server and performs authentication when key management settings are performed, key management information is displayed, and any of the following operations are performed.

- Turning on the ETERNUS DX Disk storage system- Expanding the RAID group capacity (Logical Device Expansion)- Forcibly enabling a RAID group- Creating the key group- Recovering SEDs- Performing maintenance of drive enclosures- Performing maintenance of disks- Applying disk firmware- Registering Dedicated Hot Spares- Rebuilding and performing copy back (when using Global Hot Spares)- Performing a redundant copy (when using Global Hot Spares)- Turning on the disk motor with the Eco-mode

LAN

Business server Business server

ETERNUS DX Disk storage system

Key management server (Master server)

Key management server (Slave server)

Replication

SAN



50

Chapter 3 Setup 3.6 Eco-mode

3.6 Eco-mode

Eco-mode is a function that is specifically designed to reduce the power consumption that is characteristic ofMassive Arrays of Idle Disks (MAID).Eco-mode saves power by managing the scheduled operation times of specified disks and stopping themotors of disks during periods when they are not required.The scheduled operation times can be set for each RAID group, Thin Provisioning Pool (TPP), or Flexible TierPool (FTRP) and for operations such as backing up.If an access occurs while a motor is stopped, the disk is immediately spun up and access proceeds normallyafter approximately one to five minutes.

The disk motors can be turned on and off as required by linking the following Storage Foundation SoftwareETERNUS SF to Eco-mode.

• ETERNUS SF Storage Cruiser• ETERNUS SF AdvancedCopy Manager

The following hierarchical storage management software can be also linked with Eco-mode. When using theEco-mode function with these software, an Eco-mode disk operating schedule does not need to be set, sincethese software turns on the disk motors when stopped disks are accessed.

• IBM Tivoli Storage Manager for Space Management• IBM Tivoli Storage Manager HSM for Windows• Dynamic Storage Tiering (DST) function in Symantec Veritas Storage Foundation

The restrictions and notes on using Eco-mode are described below. For details on the Eco-mode procedure,refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLI User’s Guide".

• To set Eco-mode schedule, use ETERNUS Web GUI, ETERNUS CLI, ETERNUS SF Storage Cruiser, or ETERNUS SF AdvancedCopy Manager (hereinafter, referred to as Storage Foundation Software ETERNUS SF). Note that schedules that are created by ETERNUS Web GUI or ETERNUS CLI and schedules that are created by Storage Foundation Software ETERNUS SF cannot be shared. Make sure to use only one type of software to manage a RAID group.

• Use ETERNUS Web GUI or ETERNUS CLI to set Eco-mode for TPPs and FTRPs. Storage Foundation Software ETERNUS SF cannot set Eco-mode for TPPs and FTRPs.

• Eco-mode cannot be used for the following drives:- Global Hot Spares (Eco-mode can be used for Dedicated Hot Spares)- SSDs- Unused drives (that are not used by RAID groups)

• For RAID groups, TPPs, or FTRPs disk motors in the following conditions, the Eco-mode schedule cannot be specified:

- No volumes are registered- Configured by SSDs- The RAID group is a RAID group to which the volume with Storage Migration path belongs- The RAID group is a RAID group that is registered as an REC disk buffer

• For RAID groups in the following conditions, the Eco-mode schedule can be set but the drive motors cannot be stopped:

- SDPVs are registered- ODX Buffer volumes are registered



51

Chapter 3 Setup 3.6 Eco-mode

• Specify the same Eco-mode schedule for the RAID groups that configure a WSV. If different Eco-mode schedules are specified, activation of stopped drives when host access is performed occurs and the response time may increase.

• The operation time of disks varies depending on the Eco-mode schedule and the disk access.- Access to a stopped disk outside of the scheduled operation time period causes the motor of the

stopped disk to be spun up, allowing normal access in about one to five minutes. When a set time elapses since the last access to a disk, the motor of the disk is stopped.

- If a disk is activated from the stopped state more than a set amount of times in a day, the Eco-mode schedule is not applied and disk motors are not stopped by the Eco-mode.(Example 1) Setting the Eco-mode schedule via ETERNUS Web GUI

Operation schedule is set as 9:00 to 21:00 and there are no accesses outside of the scheduled period

(Example 2) Setting the Eco-mode schedule via ETERNUS Web GUIOperation schedule is set as 9:00 to 21:00 and there are accesses outside of the scheduled period

• Eco-mode schedules are executed according to the date and time that are set in the ETERUS DX Disk storage system. To turn on and turn off the disk motors according to the schedule that is set, use the Network Time Protocol (NTP) server in the date and time setting in ETERNUS Web GUI or ETERNUS CLI to set automatic adjustment of the date and time.

• Up to eight 2.5" drives or four 3.5" drives can be activated at the same time in a single drive enclosure. When these maximums are exceeded, the first eight 2.5" drives or four 3.5" drives are activated, followed by the rest of the drives in matching increments for each size. If the number of drives that are activated in a single drive enclosure is increased, the time for drive activation takes longer, causing the response times for the server to increase, which may result in access paths being lost. To prevent this from occurring, the RAID configuration and drive installation must be taken into consideration.

21:009:001:00 0:00

Stopped Scheduled Operation Stopped

Disk motors are stoppedten minutes after the end ofthe scheduled operation

Disk motors are spun upten minutes before the start ofthe scheduled operation

Disk Motors Running

StoppedScheduled Operation Stopped Operation

21:009:001:00

Disk Motors RunningDisk Motors Running

AccessAccess finishes

Disk motors arestopped ten minutesafter the end ofthe scheduled operation

Disk motors are spun upten minutes before the start ofthe scheduled operation

Access OK inone to five minutes



52

Chapter 3 Setup 3.7 Optimizing Volume Configurations

3.7 Optimizing Volume Configurations

The ETERNUS DX Disk storage system allows for the expansion of volumes and RAID group capacities,migration among RAID groups, and the changing of RAID levels when the volumes are defined.Exact details depend on the desired operation. Select from the following procedures.This section describes the restrictions on using each function of the ETERNUS DX Disk storage system and thenotes on setting up each function of the ETERNUS DX Disk storage system.For details on the above procedures, refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLI User’s Guide".

■ Expansion of volume capacity

• RAID Migration (with increased migration destination capacity)When volume capacity is insufficient, a volume can be moved to a RAID group that has enough free space. This function is recommended for use when the desired free space is available in the destination.

• LUN ConcatenationAdds areas of free space to an existing volume to expand its capacity. This uses existing free area to efficiently expand the volume.

■ Expansion of RAID group capacity

• Logical Device ExpansionAdds new drives to an existing RAID group to expand the RAID group capacity. This is used to expand the existing RAID group capacity instead of adding new RAID group to add the volumes.

■ Migration of RAID groups

• RAID MigrationIf the performance of the current RAID groups is not satisfactory due to conflicting volumes, RAID Migration may be used to improve the performance by redistributing the RAID group configuration.

■ Changing the RAID level

• RAID Migration (to a RAID group with a different RAID level)Migrating to a RAID group with a different RAID level changes the RAID level of volumes. This is used to convert the RAID level of all the volumes belonging to a given RAID group.

• Logical Device Expansion (and changing RAID levels when adding the new drives)The RAID level may also be changed when adding new drives to a RAID group. This is used to convert the RAID level of all the volumes belonging to a given RAID group.

■ Striping for multiple RAID groups

• Wide StripingDistributing a single volume to multiple RAID groups makes I/O access from the server more efficient and improves the performance.



53


3.7.1 RAID Migration

RAID Migration is a function that transfers a volume to a different RAID group while guaranteeing theintegrity of the data. By using RAID Migration, RAID groups and volumes can be hot switched. This allows easyredistribution of volumes among RAID groups in response to customer needs. The redistribution of volumesand reconfiguration of RAID groups (e.g. changing the RAID level from RAID5 to RAID1+0) can be performedwhile the system is running.

This section describes the restrictions and notes on using RAID Migration.For details on the RAID Migration procedure, refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLI User’sGuide".

• Volumes can be specified as a target for RAID Migration.• The total number of RAID Migration, Flexible Tier Migration, TPV balancing, and FTRP balancing processes

that can be performed at the same time is 32.• The total capacity for RAID Migration, Flexible Tier Migration, TPV balancing, and FTRP balancing processes

that can be performed in at the same time is 128TB.• The volume types that can be migrated are Standard/Open, TPV, FTV, and WSV. RAID groups, TPPs, FTRPs,

and WSVs can be selected as the RAID Migration destination. If a volume is migrated to a RAID group, it becomes a Standard/Open volume. If a volume is migrated to a TPP, it becomes a TPV. If a volume is migrated to an FTRP, it becomes an FTV. If a volume is migrated to a WSV, it becomes a WSV.

• Capacity expansion can be performed at the same time as RAID migration when the RAID Migration source is a RAID group (Standard/Open) or a WSV and the RAID Migration destination is also a RAID group (Standard/Open) or a WSV.Also note that when the RAID Migration source and destination are both WSVs, the number of concatena-tions for existing RAID groups can be changed.

• Capacity expansion cannot be performed at the same time as RAID migration when the RAID Migration source is a TPV or an FTV or when the RAID Migration destination is a TPP or an FTRP. To expand the capacity, use the capacity expansion function of a TPV or an FTV before RAID Migration startsor after RAID Migration is complete.

• When the RAID Migration destination is a TPP or an FTRP, whether Zero Reclamation is performed after RAID Migration is complete can be set.

• RAID Migration cannot be performed for volumes that are undergoing Zero Reclamation.• RAID Migration cannot be performed when the source volume type is "SDV" or "SDPV".• Select RAID groups under any of the following conditions for the RAID Migration destination:

- The RAID group is not registered as the REC disk buffer.- The RAID group has an unused area that is more than the capacity of the RAID Migration source

volume.

• TPPs or FTRPs under any of the following conditions cannot be selected as the RAID Migration destination.

- When the capacity of TPP or FTRP is less than the capacity of the RAID Migration source volume (*1)- When the capacity of the RAID Migration source volume is equal to or larger than the maximum

capacity of TPP for each model (*2)*1: When the RAID Migration source is a TPV or an FTV, the RAID Migration source volume capacity indicates the

used capacity (physical capacity allocated from a TPP or an FTRP).*2: This is the total capacity of the TPPs and the FTRPs in the ETERNUS DX Disk storage system.

• RAID levels that are supported by the ETERNUS DX Disk storage system can be set for the source and destination RAID groups.

• The final volume number (LUN) will be the same as the initial volume number, and from the point of view of the server, pre-migration, migrating and post-migration volumes are accessed indistinguishably.



54


• During RAID Migration, the access performance for the RAID groups that are specified as the RAID Migration source and RAID Migration destination may be reduced.

• If the power is turned off or an electrical power outage occurs during RAID Migration, the process will simply continue when the power is restored.

• When RAID Migration is used to increase the volume (LUN) capacities, note that the increased size of the expanded volumes may not always be dynamically re-recognized by the server, depending on the server-side OS (type and version) being used. Refer to the applicable OS and file system documentation before dynamically expanding the volume capacity.This is not necessary when building a new system after the volume capacity has been expanded.

3.7.2 Logical Device Expansion (LDE)

Logical Device Expansion (LDE) allows the capacity of an existing RAID group to be dynamically expanded bythe addition of extra drives. By expanding the capacity of existing RAID group, a new volume can be addedwithout having to add new RAID groups.

This section describes the restrictions and notes on using LDE.For details on the LDE procedure, refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLI User’s Guide".

• A RAID group can be specified as a target for LDE.• Multiple LDEs cannot be performed simultaneously.• LDE can be performed if the new RAID group capacity is the same or larger than the old capacity.• Capacity expansion and changing the level of a RAID group can be performed at the same time.• When adding drives, use drives that have the same capacity and speed as the drives that configure the

target RAID group. If drives of different capacities exist in a RAID group, the smallest capacity becomes the standard for the RAID group after expansion, and all other drives are regarded as having the same capacity as the smallest drive. In this case, the remaining drive space is not used. In addition, if drives of different speeds exist in a RAID group, the access performance of the RAID group is reduced by the slower drives.

• If the drives that configure the target RAID group are SSDs, SSDs must be used when adding drives.• If the drives that configure the target RAID group are SEDs, SEDs must be used when adding drives.• LDE can be performed on a RAID group that contains an Advanced Copy target (copy source or copy

destination) volume.• LDE cannot be performed on a RAID group that belongs to a Thin Provisioning Pool (TPP) or a Flexible Tier

Pool (FTRP).• LDE cannot be performed for a RAID group in which a Wide Striping Volume (WSV) belongs.• Since the data cannot be recovered after the failure of LDE, back up all the data of the volumes in the

target RAID group to another area before performing LDE. If LDE fails, recover using this backup data.• Volumes cannot be added to the target RAID groups while LDE is running. Volumes can be added after LDE

is complete. Volumes cannot be deleted from the target RAID groups while LDE is running.• If the power is turned off or an electrical power outage occurs during LDE, the process will simply continue

when the power is restored.



55


3.7.3 LUN Concatenation

LUN Concatenation is a function that is used to add new area to a volume and so expand the volume capacityavailable to the server. The ability to concatenate widely distributed free areas in the ETERNUS DX Diskstorage system allows efficient use of the drive capacity.Unused areas, which may be either part or all of a RAID group, are used to create new volumes that are thenadded together (concatenated) to form a single large volume.

This section describes the restrictions and notes on using LUN Concatenation.For details on the LUN Concatenation procedure, refer to "ETERNUS Web GUI User’s Guide" or "ETERNUS CLIUser’s Guide".

• Volumes can be specified as a target for LUN Concatenation.• Multiple volumes can be concatenated. Up to 16 volumes can be concatenated.• Maximum concatenated volume capacity is 128TB (*1).

*1: The maximum volume capacity of an ODX Buffer volume is 1TB.

• The minimum required capacity of each volume being concatenated is 1GB.• Conditions for volumes to be concatenated are as follows:

- Only Standard/Open type volumes can be used for LUN Concatenation. SDV cannot be concatenated. The encryption status of a concatenated volume is the same status as a volume that is to be concatenated.

- The RAID levels may be any that are supported by the ETERNUS DX Disk storage system with no need for all to be the same or any other limitation. It is also possible to connect up volumes with different RAID levels. Volumes in RAID groups with different types (such as capacity or speed) of drives can be concat-enated. However, RAID groups with the same RAID level and same drive type are recommended for con-catenated volumes to ensure that performance is not affected.

- LUN Concatenation cannot be performed when the drive type for the RAID group to which the concatenation source volume belongs and the drive type to which the concatenation target volume belongs do not match.

• When the concatenation source volume is configured with SAS disks or Nearline SAS disks, volumes that are configured with SAS disks or Nearline SAS disks can be concatenated.

• When the concatenation source volume is configured with SSDs, volumes that are configured with SSDs can be concatenated.

• When the concatenation source volume is configured with SEDs, volumes that are configured with SEDs can be concatenated.

- The same key group setting is recommended for the RAID group to which the concatenation source volumes belong and the RAID group to which the concatenation destination volumes belong if the RAID groups are configured with SEDs.

• LUN Concatenation cannot be performed under the following conditions:- When the volume to be concatenated contains an Advanced Copy session for which the copy range is

"Totally".- When the volume to be concatenated is a TPV or an FTV.- When the number of volumes to be concatenated is fewer than the maximum number of volumes that

can be concatenated but the resulting capacity exceeds the maximum single LUN capacity allowed by the ETERNUS DX Disk storage system.

- When the logical volume to be concatenated is a WSV.

• The encryption status after concatenation is the same as the concatenation source volume.• It is possible to add extra volumes to an already concatenated volume.• After concatenation, any number of formatting processes can be started at once.



56


• Because the server-side LUNs are not changed by volume concatenation, an OS reboot is not required. However, this function only expands the volumes in the ETERNUS DX Disk storage system. Server-side recognition and capacity expansion is OS dependent.

• The logical unit number of each concatenated volume does not change and remains accessible from the server before, during, and after the concatenation.

• If the power is turned off or an electrical power outage occurs during LUN Concatenation, the concatenation will simply continue the next time the power is turned on.

• It is recommended that the data on the volumes that are to be concatenated be backed up first.• When LUN Concatenation is used to increase the volume (LUN) capacities, note that the increased size of

the expanded volumes may not always be dynamically re-recognized by the server, depending on the server-side OS (type and version) being used. Refer to the applicable OS and file system documentation before dynamically expanding the volume capacity.This is not necessary when building a new system after the volume capacity has been expanded.

• A concatenated volume can be used as an OPC, EC, or QuickOPC copy source or copy destination. It can also be used as a SnapOPC/SnapOPC+ copy source.

• When a volume that is using ETERNUS SF AdvancedCopy Manager to run backups is expanded via LUN Concatenation, the volume will need to be registered with ETERNUS SF AdvancedCopy Manager again.

3.7.4 Wide Striping

Wide Striping is a function that improves performance by concatenating multiple RAID groups with stripingand using many drives at the same time. This function is especially effective for systems that require writeaccess performance.By increasing the number of drives that configure a LUN, process performance is improved by the distributionof I/O access from the server to multiple drives.

This section describes the points to note when using the Wide Striping function.For details on Wide Striping settings, refer to "ETERNUS Web GUI User's Guide" or "ETERNUS CLI User's Guide".

• The maximum volume capacity for a Wide Striping Volume (WSV) is 128TB.• From 2 to 64 RAID groups can be concatenated.• Wide Striping cannot be used for RAID groups in the following conditions:

- RAID groups that belong to TPPs or FTRPs- RAID groups that are registered as REC disk buffers

• The number of RAID groups that are to be concatenated is defined when creating a WSV. The number of concatenated RAID groups cannot be changed after creation. To change the number of RAID groups in a WSV, use the RAID Migration function and specify a WSV with a different number of RAID groups as the RAID Migration destination.

• The LUN Concatenation function cannot be used to expand the WSV capacity. To expand the WSV capacity, use the RAID Migration function and specify a larger capacity for the RAID Migration destination volume.

• The Logical Device Expansion function cannot be used for RAID groups that configure a WSV.• Different drive types (SAS, Nearline SAS, SSD, and SED) in RAID groups that configure a WSV cannot be

used.• Free areas in RAID groups that are concatenated by the Wide Striping function can be used to create other

type volumes (Standard/Open, SDV, SDPV, or WSV).• WSVs can be created by RAID groups when the stripe size is specified during WSV creation. Note that WSVs

cannot be configured by concatenating RAID groups with different stripe sizes.



57

Chapter 4

Operations

This chapter describes the control of the LAN for operation management of the ETERNUS DX Disk storagesystem, and the monitoring the status of the ETERNUS DX Disk storage system.

4.1 LAN for Operation Management

The ETERNUS DX Disk storage system must be connected to the LAN for operation management. When remotesupport is used, information on errors of the ETERNUS DX Disk storage system or other events can be notifiedto the remote support center.

This section explains how the LAN control controller of the ETERNUS DX Disk storage system operates.

■ LAN control controller (Master CM/Slave CM)

For a dual-controller type, the controller (CM) that is given the authority to manage the LAN is called theMaster CM and the other CM is called the Slave CM.When an error occurs in the Master CM or LAN, the Master CM is switched automatically.IP addresses of the LAN ports are not assigned to each controller. These IP addresses are assigned to the roleof master or slave. If the Master CM is switched, the same IP addresses are reused. Therefore, even if theMaster CM is switched and the physical port is changed, access can be maintained via the same IP addresses.

• Make sure to connect each controller to the LAN for operation management.• The LAN ports of the ETERNUS DX Disk storage system support IPv4 and IPv6.

Note that an IPv6 network is used for an ETERNUS DX Disk storage system with firmware version V10L30 or later.



58

Chapter 4 Operations 4.1 LAN for Operation Management

Figure 4.1 LAN control (switching of the Master CM)

• Each controller has an LED that lights up green to identify when it is the Master CM.• Setting the IP address of the Slave CM ensures that ETERNUS Web GUI or ETERNUS CLI can be used from

the Slave CM if an error occurs on the LAN path for the Master CM. The Master CM and the Slave CM perform different functions. The Slave CM can only switch the Master CM and display the status of the ETERNUS DX Disk storage system.The IP address of the Slave CM does not need to be set for normal operation.

Figure 4.2 LAN control (when the IP address of the Slave CM is set)


MN

TCM#0

MasterCM M

NT

CM#1

SlaveCM


MN

T

RM

TR

MT

RM

TR

MT

CM#0

SlaveCM M

NT

CM#1

MasterCM

IP address A



The Master CM is switched.

CM#0has failed

IP address A

When the Master CM isswitched, the IP addressesof the previous Master CM’sare taken over by the newMaster CM.


MN

T

CM#0

MasterCM M

NT

CM#1

SlaveCMR

MT

RM

T

IP address A IP address B


LAN patherror

The IP address of the Slave CM is usedto switch the Master CM and displaythe status of the ETERNUS DX Disk storage system.



59

Chapter 4 Operations 4.2 Monitoring ETERNUS DX Disk Storage System Status

4.2 Monitoring ETERNUS DX Disk Storage System Status

Check the system status regularly by checking the LEDs of the ETERNUS DX Disk storage system or the statusdisplay function of ETERNUS Web GUI.

In addition, setting event notification enables e-mail notification messages or SNMP Trap messages for eventsthat occur in the ETERNUS DX Disk storage system in order to monitor the status of the ETERNUS DX Diskstorage system.

4.2.1 LED Status Check

The status of the ETERNUS DX Disk storage system can be checked by the LEDs.If the FAULT LED in front of the ETERNUS DX Disk storage system is amber, contact your maintenanceengineer.

CAUTIONImpending trouble may be indicated by the warning message FAULT LEDs of the ETERNUS DX Disk storage system. The LEDs and the general status of ETERNUS Web GUI should be checked regularly to prevent any serious trouble from occurring.

Event notification and status display for the ETERNUS DX Disk storage system can be performed by ETERNUSCLI. When ETERNUS CLI is used, refer to "ETERNUS CLI User’s Guide".



60


4.2.2 Displaying Status via ETERNUS Web GUI

The status of the ETERNUS DX Disk storage system and the usage status of RAID groups, TPPs, and SDPs can bechecked in the Overview screen of ETERNUS Web GUI.

Figure 4.3 ETERNUS Web GUI screen

Table 4.1 shows the general status.

Status of each component in the ETERNUS DX Disk storage system is monitored periodically, and the result isdisplayed as a general status image with character strings.

Table 4.1 General status of ETERNUS Web GUI

Refer to "ETERNUS Web GUI User’s Guide" for details.

General status ETERNUS DX Disk storage system status

Normal (Green)The ETERNUS DX Disk storage system is in normal state.

Not Ready (Red)"Not Ready" is a status where an abnormality is detected at a power-off, and I/O access from the server cannot be received.

Error (Red)The ETERNUS DX Disk storage system is in error state.

Maintenance (Orange)The ETERNUS DX Disk storage system is under maintenance.

Warning (Yellow)The ETERNUS DX Disk storage system is in warning state.



61


4.2.3 Event Notification

By setting event notification, if an error (event) occurs in the ETERNUS DX Disk storage system, the eventinformation is notified.

The methods that can be used to notify an event are "e-mail", "SNMP Trap", "syslog", "remote support", and"host sense".

For the procedure on setting event notification, refer to "User’s Guide -Installation-".

■ E-mail

When an event occurs in the ETERNUS DX Disk storage system, an e-mail is sent to the specified e-mailaddress.For more details on notified event information, refer to "Appendix A Event Notification Message List" (page103).

■ SNMP Trap

When an event occurs in the ETERNUS DX Disk storage system, an SNMP Trap is sent to the SNMP Manager(monitoring server). For more details on event information notified by SNMP Trap, refer to "Appendix A Event Notification MessageList" (page 103).

■ Syslog

When an event occurs in the ETERNUS DX Disk storage system, the event log can be sent to the external server(syslog server).For the notified syslog messages, refer to "Appendix A Event Notification Message List" (page 103).

■ Remote Support

The information for errors that occur in the ETERNUS DX Disk storage system is notified to the remote supportcenter.

■ Host Sense

When an event occurs in the ETERNUS DX Disk storage system, host senses (sense codes) are sent to theserver. For details on sense codes, refer to "Appendix A Event Notification Message List" (page 103).



62


Figure 4.4 Event notification

4.2.4 Audit Log

By setting audit log, audit trail logs (hereinafter referred to as "audit log") that record performed operationsby using the ETERNUS DX Disk storage system and the system actions that are associated with theseoperations can be sent to the syslog server.

For the procedure on setting audit logs, refer to "User’s Guide -Installation-". For audit log information, refer to"Appendix B Audit Log List" (page 154).

Figure 4.5 Audit logs

SNMPmanager

Mailserver

Syslogserver

ETERNUS DX Diskstorage system

Remotesupportcenter

REMCS / AIS Connect

Host senseServer(host)

SyslogSNMP TrapE-mail

Syslog serverETERNUS DX Disk storage system

System administrator

Login

Logout

Change settings↓

↓

Storage system nameUser/Role

Operation timeOperation detailsOperation result

etc.

Audit log



63

Chapter 5

Maintaining Optional Products

The following optional products can be installed in the ETERNUS DX Disk storage system:

• Drives• Drive enclosures• Host interfaces• Long wave SFP+ modules

This chapter explains the installation rules, handling instructions, and installation procedures for theseoptional products.

Disks, drive enclosures, and Long wave SFP+ modules can be added by users. Users can also replace Shortwave SFP+ modules with Long wave SFP+ modules.However, make sure to read the manual that contains the safety precautions before performing any of theseprocedures.

5.1 Installing Drives

Optional drives can be installed while the ETERNUS DX Disk storage system is running without affecting thesystem.This section explains how to install optional drives.

CAUTIONDo Not

• Do not uninstall or move a drive that is already installed.Contact your sales representative or maintenance engineer if a drive needs to be uninstalled or moved.



64

Chapter 5 Maintaining Optional Products 5.1 Installing Drives

5.1.1 Installation Rules for Drives

This section explains the installation rules for drives.

■ 2.5" drives

2.5" drives can be installed in the front side of a 2.5" type controller enclosure or a 2.5" type drive enclosure.Different types of drives can be installed in the same enclosure. Drives can be installed in any slots of anenclosure.Figure 5.1 shows the positions of 2.5" drive slots.

Figure 5.1 Positions of 2.5" drive slots

■ 3.5" drives

3.5" drives can be installed in the front side of a 3.5" type controller enclosure or a 3.5" type drive enclosure.Different types of drives can be installed in the same enclosure. Drives can be installed in any slots of anenclosure.Figure 5.2 shows the positions of 3.5" drive slots.

Figure 5.2 Positions of 3.5" drive slots

5.1.2 Installable Drives

For installable drives, refer to "Product List".

Slo

t#8

Slo

t#9

Slo

t#10

Slo

t#11

Slo

t#12

Slo

t#13

Slo

t#14

Slo

t#15

Slo

t#0

Slo

t#1

Slo

t#2

Slo

t#3

Slo

t#4

Slo

t#5

Slo

t#6

Slo

t#7

Slo

t#16

Slo

t#17

Slo

t#18

Slo

t#19

Slo

t#20

Slo

t#21

Slo

t#22

Slo

t#23

Slot#0

Slot#4

Slot#8

Slot#1

Slot#5

Slot#9

Slot#2

Slot#6

Slot#10

Slot#3

Slot#7

Slot#11



65


5.1.3 Drive Handling Instructions

■ About condensation

■ About static electricity

CAUTIONDo

• When moving a drive from a cold place, such as an un-conditioned store house in winter, to a warmer place such as an air-conditioned room, the severe temperature change may result in condensation forming.To avoid this, allow the packed drive sufficient time in the warmer place (one hour for each 15°C of temperature difference) to adapt to the new temperature.

CAUTIONDo Not

• Do not touch the surface of the board of the drives.

Do

• When handling drives, make sure to wear a wrist strap or touch a metal part to discharge the human body's natural static electricity. Failure to discharge static electricity may cause device failure.

• Leave the drive in its package until ready to install it.



66


■ About shock

5.1.4 Additional Drive Installation Procedure

This section describes how to install additional drives in the ETERNUS DX Disk storage system.

■ For 2.5" drives

Procedure

1 In the [Storage] screen of [Component] on the ETERNUS Web GUI screen, check that all components of the ETERNUS DX Disk storage system are in normal status.

2 Wear a wrist strap or touch a metal part to discharge the human body’s natural static electricity.

CAUTIONDo Not

• Do not lay the drives directly on a desk or similar hard surface. Always use a rubber mat or other soft material to cushion the drives against physical shocks.

• Do not stack drives or stand drives on end.

• Do not apply external force to the interface connectors.• Do not knock or drop the drives on hard objects.

CAUTIONDo

• If additional drives are installed in a way other as described here, damage and/or device failure or electrical shock may occur.

Do Not

• Do not install drives that are for use in other devices.



67


3 Remove the dummy drive unit from the slot in which the drive is to be installed.Push into the tab of the dummy drive unit and pull it straight out of the drive slot.

4 Install the new drive.

4-1 Press the catch on the drive lock lever to unlock it.

4-2 Insert the drive all the way into in the slot, making sure that it is firmly seated and keeping the lock lever open.

The removed dummy drive unit should be retained for future use.

Tab

Dummy drive unit

Catch

Lock lever



68


4-3 Swing the lock lever in the direction of the arrow, until the lock clicks shut.

4-4 Check that the newly installed drive's DRIVE READY LED lights up green.

5 Repeat Step 3 and Step 4 for each additional drive.

6 If a wrist strap is used, remove the wrist strap.

7 In the [Disks] screen of [Component] on the ETERNUS Web GUI screen, check that the added drives have been recognized.

8 Set up RAID groups, volumes, hot spares, and Host Affinity settings on the new drives, as required.

End of procedure

■ For 3.5" drives

Procedure

1 In the [Storage] screen of [Component] on the ETERNUS Web GUI screen, check that all components of the ETERNUS DX Disk storage system are in normal status.


WARNINGDo

• Hold the drive with both hands to protect against jarring.

Lock lever



69


3 Remove the dummy drive unit from the slot in which the drive is to be installed.Push into the tab of the dummy drive unit and pull it straight out of the drive slot.

4 Install the new drive.

4-1 Press the catch on the drive lock lever to unlock it.

4-2 Insert the drive all the way into in the slot, making sure that it is firmly seated and keeping the lock lever open.

The removed dummy drive unit should be retained for future use.

WARNINGDo

• Hold the drive with both hands to protect against jarring.

Dummy drive unitTab

Catch

Lock lever



70


4-3 Swing the lock lever in the direction of the arrow, until the lock clicks shut.

4-4 Check that the newly installed drive's DRIVE READY LED lights up green.

5 Repeat Step 3 and Step 4 for each additional drive.


7 In the [Disks] screen of [Component] on the ETERNUS Web GUI screen, check that the added drives are recognized.

8 Set up RAID groups, volumes, hot spares, and Host Affinity settings on the new drives, as required.

End of procedure

Lock lever



71

Chapter 5 Maintaining Optional Products 5.2 Installing Drive Enclosures

5.2 Installing Drive Enclosures

Optional drive enclosures can be installed while the ETERNUS DX Disk storage system is running withoutaffecting the system.This section explains how to install optional drive enclosures.

5.2.1 Installation Rules for Drive Enclosures

Up to nine drive enclosures can be installed in the ETERNUS DX Disk storage system. 3.5" type drive enclosuresand 2.5" type drive enclosures can be installed in the ETERNUS DX Disk storage system together.In this case, the maximum number of drives allowed determines the maximum number of drive enclosuresthat may be installed.

5.2.2 Installable Drive Enclosures

For installable drive enclosures, refer to "Product List".

5.2.3 Drive Enclosure Handling Instructions


CAUTIONDo Not

• Do not uninstall or move a drive enclosure that is already installed.Contact your sales representative or maintenance engineer if a drive enclosure needs to be uninstalled or moved.

CAUTIONDo

• When moving a drive enclosure from a cold place, such as an un-conditioned store house in winter, to a warmer place such as an air-conditioned room, the severe temperature change may result in condensation forming.To avoid this, allow the packed drive enclosure sufficient time in the warmer place (one hour for each 15°C of temperature difference) to adapt to the new temperature.



72



■ About shock

5.2.4 Additional Drive Enclosure Installation

This section explains how to install additional drive enclosures in the ETERNUS DX Disk storage system.

Procedure

1 In the [Storage] screen of [Component] on the ETERNUS Web GUI screen, check that all components of the ETERNUS DX Disk storage system are in normal status.In addition, check the DE-IDs (drive enclosure numbers) of the installed enclosures in the [Drive Enclosure] screen.

CAUTIONDo

• When handling drive enclosures, make sure to wear a wrist strap or touch a metal part to discharge the human body's natural static electricity. Failure to discharge static electricity may cause device failure.

CAUTIONDo Not

• Do not handle the drive enclosure roughly or subject it to physical shocks when laying it down.

• Do not stack the drive enclosures.• Do not knock or drop the drive enclosure on hard objects.

CAUTIONDo

• If drive enclosures are installed in a way other as described here, damage and/or device failure or electrical shock may occur.

• Do not install drive enclosures with cables, such as power cords, connected.• Do not knock the other devices installed in the rack when installing drive

enclosures.



73


2 Display the [Add Drive Enclosure] screen.

2-1 In the [Storage] screen of [Component], click "Add Drive Enclosure" in [Action].The [Add Drive Enclosure] screen appears.

2-2 Check the DE-ID (drive enclosure number) for the drive enclosure that is to be added in "Target Drive Enclosure", and click the [Next>>] button.

A screen to show how to install the drive enclosure appears.




74


4 Install the drive enclosure in the rack.

4-1 Attach the rack rails to the rack.


(1) Attach the 2U rack rail to the left rear rack pillar.The M5 centering screws should be inserted in the 1st and 6th holes above the base line of thecontroller enclosure.

(2) Insert the pins of the left slide rail in the 1st and 3rd holes from the bottom of the 2U rack rail.

(3) Secure the left slide rail to the front pillar using the M5 centering screw and M5 pan head screw.

(4) For the right slide rail, insert the pins in the holes of the rear pillar, and secure the other side of the slide rail to the front pillar in the same way as the left slide rail.

M5 Centering screws (10mm)

2U rack rail

M5 Centering screw (10mm)

M5 Cage nut

M5 Pan head screw (10mm)



75


(5) Push the M5 cage nuts into the 2nd holes of the front rack pillars above the base line of the drive enclosure.The M5 centering screw and M5 pan head screw positions for the slide rails and 2U rack rail aredetermined relatively to the base line of the drive enclosure. Tighten the screws referring to the following figure.


(1) Adjust the sizes of the rack rail (for left side) and the rack rail (for right side) to fit the rack.Loosen the M4 screws to adjust the length of the rack rails to match the distance between the frontand rear rack pillars. Leave the M4 screws slightly unscrewed, as the rack rail must be attached tothe rack before they can be completely tightened.

Drive enclosure

1st position(M5 pan head screw)

3rd position(M5 centering screw)

1st position(M5 pan head screw)

3rd position(M5 centering screw)

2U

Rack rails

Base line ofdrive enclosure

[Left] [Right]

2nd position(M5 cage nut)

2nd position(M5 cage nut)

(Front rack pillars)

(Rear rack pillars)

Rack rail (for right side)"R" is stamped on the innerside of the rack rail(for right side).

Loosen the M4 screws, andadjust the rack rails to the depthof the rack.

[Left]

[Right]

Rack rail (for left side)"L" is stamped on the innerside of the rack rail(for left side).



76


(2) Attach the rack rails to the rack.Use the two plates to fasten the rack rails to the front rack pillars. Use the four washers to fasten therack rails to the rear rack pillars.

The M5 screw positions for the rack rails are determined by the drive enclosure base line.Insert the M5 screws in the 1st and 6th holes on the front rack pillars above the base line and in the2nd and 5th holes on the rear rack pillars above the base line to fasten the rack rails.

(3) Tighten the M4 screws of the rack rails that were slightly unscrewed in Step (1).

Make sure to attach the rack rails and rack pillars so that they fit exactly together without any space between them.

(Front rack pillars)

(Rear rack pillars)

Washers

M5 screws

M5 screws

Washers

M5 screws

Plate

M5 screws

Plate

Rack rail (for right side)

Rack rail (for left side)

Front of drive enclosure

Rear of drive enclosure

[Left]6th position(M5 screw)

[Left]

1st position(M5 screw)

5th position(M5 screw)

2nd position(M5 screw)

2U

2U



Rack rails

Rack rails

[Right]

[Right]


1st position(M5 screw)


2nd position(M5 screw)



77


4-2 Install the drive enclosure in the rack.

4-3 Fasten the drive enclosure in the rack.


Use two M5 screws to fasten it in the rack pillar.

CAUTIONDo

• When installing or removing the drive enclosure to or from the rack, make sure that the sides and the bottom of the drive enclosure are held by two or more people. Failure to do so may cause injury.

M5 screw

M5 screw



78



Use four M5 screws to fasten it in the rack pillar.

4-4 Attach the "DE_No." labels to the positions shown below.Attach the labels in the same installation order as the drive enclosures (QSFP cable connectionorder).

The DE_No. labels are supplied with the ETERNUS DX Disk storage system.

M5 screws

M5 screws

Right front side of the drive enclosure Upper rear side of the drive enclosure

DE_No. label



79


4-5 Attach the flange cover that is provided with the ETERNUS DX Disk storage system.

4-6 For regions other than EMEA&I, attach the brackets to the rack rails (for the left and right sides).Use the thumb screws to attach the brackets at the specified locations on the rear side.

Right

3.5" type drive enclosure


Left

Attachment location of the bracket



Bracket

Thumb screw



80


5 Connect the added drive enclosure to the previous enclosure with the QSFP cable that is pro-vided with the ETERNUS DX Disk storage system.The following figures show the connection paths for QSFP cables when drive enclosure 1 is added.

• For a single-controller type

• For a dual-controller type

• To help with QSFP cable management and prevent incorrect connections, make sure to attach the destination labels that are supplied with the ETERNUS DX Disk storage system to the connectors of the QSFP cables.

• When connecting QSFP cables, check the connector orientation and then firmly push it all the way in.When disconnecting QSFP cables, use the pull-tab to extract the connector.


Drive enclosure 1(Added drive enclosure)



Tab



81


5-1 Attach the destination labels to the connectors of the QSFP cables.

(1) Before attaching the destination labels, check the connection destination of the QSFP cables.

• The connectors on which the "●" symbol is printed are connected to the DI (IN) ports on the added enclosure.

• The connectors on which the "■" symbol is printed are connected to the DI (OUT) ports on the enclosure below the added drive enclosure.

(2) Attach the destination labels to the connectors of the QSFP cables."Controller number" or "Drive enclosure number - IOM number" is printed on the destinationlabels in the "Connection origin DI port → Connection destination DI port" format. The "■" or "●"symbol is also printed on the destination labels.Carefully check the connection origin and connection destination. Attach the destination labelsas shown below:

The following figure shows an example of attaching destination labels on the QSFP cables thatconnect the controller enclosure to drive enclosure 1.

Destination labelIOM (I/O module) number

Drive enclosure number

CM (controller) number





82


5-2 Connect the DI (OUT) port of CM#0 or IOM#0 in the enclosure that has the highest DE-ID (drive enclosure number) to the DI (IN) port of IOM6#0 in the drive enclosure that is to be added.

5-3 Connect the DI (OUT) port of CM#1 or IOM#1 in the enclosure that has the highest DE-ID (drive enclosure number) to the DI (IN) port of IOM6#1 in the drive enclosure that is to be added.Perform the same operation as Step 5-2 to connect the QSFP cable.

6 Connect the power cord.

6-1 Connect the power cord to the drive enclosure.

6-2 Connect the power cord plugs to the inlets of the power supply units.

Do not connect any cable to the last DI (OUT) port on the end.

Each enclosure has two power supply units (PSU#0 and PSU#1). The power cords must be connected to the inlets of both power supply units.

Drive enclosureto be added

Drive enclosure that hasthe highest DE-ID



83


6-3 Fasten the plug of the power cord with the release tie.Wrap the release tie around the power cord and fasten the release tie from either side. Make surethat the release tie is not loose.

6-4 Connect the power cord on the power socket side.Connect the other end of the power cord plug to a power socket or an inlet on the power distributionunit.

7 Turn the PSU switches of the power supply units (PSU#0 and PSU#1) in the drive enclosure to the ON position (marked "|").The power of the drive enclosure is turned on and the fan revolves at high speed for about 30 seconds.

8 Check that the LINE LED and the POWER LED on the drive enclosure are lit up.

9 In the [Add Drive Enclosure] screen, click the [Next>>] button.The added drive enclosures are recognized and the installation completion screen appears.

10 Click the [Done] button.The [Add Drive Enclosure] screen closes and the screen display returns to the [Drive Enclosure] screen.

11 In the [Storage] screen of [Component], check that the added drive enclosure is displayed.

12 To install more additional drive enclosures, repeat Step 1 to Step 11.

13 Install the drives.For details on drive installation, refer to "5.1.4 Additional Drive Installation Procedure" (page 67).


End of procedure


Drive enclosurePOWERFAULT

FAULT

LINE



84

Chapter 5 Maintaining Optional Products 5.3 Installing Host Interfaces

5.3 Installing Host Interfaces

Optional host interfaces can be installed while the ETERNUS DX Disk storage system is running withoutaffecting the system.

5.3.1 Installation Rules for Host Interfaces

This section explains the installation rules for host interfaces.

One or two host interfaces that have two host interface ports can be installed for each controller.

Figure 5.3 and Figure 5.4 show the installation diagrams for host interfaces.Install the host interfaces for CA#0 first, and then CA#1. Host interfaces that have different interfaces can beinstalled in CA#0 and CA#1.For a dual-controller type, the configuration is the same for Controller 0 (CM#0) and Controller 1 (CM#1).

■ For a single-controller type

Figure 5.3 Installation diagram for a host interface (single-controller type)

CAUTIONDo Not

• Do not uninstall or move a host interface that is already installed.Contact your sales representative or maintenance engineer if a host interface needs to be uninstalled or moved.

Do

• Contact your maintenance engineer when a host interface is installed in the host interface 1 (CA#1) of the ETERNUS DX80 S2/DX90 S2.

Host interface 1 (CA#1)

Controller 0 (CM#0)

Expansion



85

Chapter 5 Maintaining Optional Products 5.3 Installing Host Interfaces

■ For a dual-controller type

Figure 5.4 Installation diagram for host interfaces (dual-controller type)

5.3.2 Installable Host Interfaces

For installable host interfaces, refer to "Product List".

5.3.3 Host Interface Handling Instructions



Expansion Expansion


Controller 0 (CM#0) Controller 1 (CM#1)

CAUTIONDo

• When moving a host interface from a cold place, such as an un-conditioned store house in winter, to a warmer place such as an air-conditioned room, the severe temperature change may result in condensation forming.To avoid this, allow the packed host interface sufficient time in the warmer place (one hour for each 15°C of temperature difference) to adapt to the new temperature.

CAUTIONDo

• When handling host interfaces, make sure to wear a wrist strap or touch a metal part to discharge the human body's natural static electricity. Failure to discharge static electricity may cause device failure.

• Leave the host interface in its package until ready to install it.



86

Chapter 5 Maintaining Optional Products 5.4 Installing Long Wave SFP+ Modules (16Gbit/s)

■ About shock

5.4 Installing Long Wave SFP+ Modules (16Gbit/s)

The Short wave SFP+ module (16Gbit/s) in the host interface (FC 16Gbit/s) can be replaced with an optionalLong wave SFP+ module (16Gbit/s) for an ETERNUS DX Disk storage system.

This section explains the installation rules, handling instructions, and replacement procedure for Long waveSFP+ modules.

Make sure to read "Safety Precautions" before performing replacement of Long wave SFP+ modules.

5.4.1 Installation Rules for Long Wave SFP+ Modules (16Gbit/s)

One or two Short wave SFP+ modules (16Gbit/s) in a host interface (FC 16Gbit/s) can be replaced with Longwave SFP+ modules (16Gbit/s).

Short wave SFP+ modules (16Gbit/s) and Long wave SFP+ modules (16Gbit/s) can be mixed in the same hostinterface (FC 16Gbit/s).

For the dual controller type, the SFP+ module configurations for controller 0 (CM#0) and controller 1 (CM#1)must be the same.

CAUTIONDo Not

• Do not handle the host interface roughly or subject it to physical shocks when laying it down.

• Do not place any objects on top of the host interface.• Do not knock or drop the host interface on hard objects.

Make sure to turn off the ETERNUS DX Disk storage system before replacing SFP+ modules (16Gbit/s).Contact your sales representative or maintenance engineer to replace SFP+ modules (16Gbit/s) during system operation.

Long wave SFP+ modules (16Gbit/s) can be installed in an ETERNUS DX Disk storage system with firmware version V10L50 or later.



87


5.4.2 Installable Long Wave SFP+ Modules (16Gbit/s)

For installable Long wave SFP+ modules (16Gbit/s), refer to "Product List".

5.4.3 SFP+ Module Handling Instructions



■ About shock

CAUTIONDo

• When moving an SFP+ module from a cold place, such as an un-conditioned store house in winter, to a warmer places such as an air-conditioned room, the severe temperature change may result in condensation forming.To avoid this, allow the packed SFP+ modules sufficient time in the warmer place (one hour for each 15°C of temperature difference) to adapt to the new temperature.

CAUTIONDo

• When handling SFP+ modules, make sure to wear a wrist strap or touch a metal part to discharge the human body's natural static electricity.Failure to discharge static electricity may cause device failure.

• Leave the SFP+ module in its package until ready to install it.

CAUTIONDo Not

• Do not handle SFP+ modules roughly or subject them to physical shocks when laying them down.

• Do not place any objects on top of SFP+ modules.• Do not knock or drop SFP+ modules on hard objects.



88


5.4.4 Long Wave SFP+ Modules (16Gbit/s) Installation Procedure

This section describes how to replace a Short wave SFP+ module (16Gbit/s) in the host interface (FC 16Gbit/s)with a Long wave SFP+ module (16Gbit/s).

Procedure

1 Check that all components of the ETERNUS DX Disk storage system are in normal status, using the [Storage System Status] screen of ETERNUS Web GUI.

2 Check the port location of the Short wave SFP+ module (16Gbit/s) that is to be replaced by using the Internal Parts information in the [Channel Adapter Detail] screen.Note that a Short wave SFP+ module (16Gbit/s) is displayed as "16G SFP+(MMF)" in the "SFP Type" field.

3 Turn off the ETERNUS DX Disk storage system.Refer to "2.1.4 Powering Off" (page 38) for details on how to turn off the ETERNUS DX Disk storagesystem.

4 Wear a wrist strap or touch a metal part to discharge the human body's natural static electricity.

5 Disconnect the FC cable that is connected to the FC port in the Short wave SFP+ module (16Gbit/s) that is to be replaced.Push the tab on the FC cable connector and pull out the cable.

CAUTIONDo

• If SFP+ modules are installed in a way other as described here, damage and/or device failure or electrical shock may occur.

Make sure to record the connecting port for the disconnected FC cable.



89


6 Remove the Short wave SFP+ module (16Gbit/s).

6-1 Pull down the Short wave SFP+ module (16Gbit/s) lever.

6-2 Pull the Short wave SFP+ module (16Gbit/s) straight out of the port cage.

7 Install the Long wave SFP+ module (16Gbit/s).

7-1 Remove the connector cover that is attached to the Long wave SFP+ module (16Gbit/s) port and pull down the lever.

Make sure to store the removed Short wave SFP+ module (16Gbit/s) with the fixing lever and the connector cover attached.

Keep the removed connector cover in a safe place where they will not be lost.

��



90


7-2 Insert the Long wave SFP+ module (16Gbit/s) all the way into in the port cage.

7-3 Push up the Long wave SFP+ module (16Gbit/s) lever until it clicks into place.

8 Connect the FC cable that is disconnected in Step 5.Connect the FC cable connector to the FC port on the Long wave SFP+ module (16Gbit/s).

9 Repeat Step 5 through Step 8 to replace multiple SFP+ modules (FC 16Gbit/s).

CAUTIONDo

• When connecting the FC cables, position them so that they will not obstruct replacement of the power supply unit or controllers by the maintenance engineer.

��



91



11 Turn on the ETERNUS DX Disk storage system.Refer to "2.1.3 Powering On" (page 36) for details on how to turn on the ETERNUS DX Disk storagesystem.

12 Check that the LINK/FAULT LED for the FC port on the replaced Long wave SFP+ module (16Gbit/s) turns off or lights up green.

13 Start ETERNUS Web GUI to check the status of the newly added Long wave SFP+ module (16Gbit/s).On the Internal Parts information in the [Channel Adapter Details] screen of ETERNUS Web GUI, checkthat the FC port status is Normal and the SFP type is changed to "16G SFP+(SMF)". In addition, confirmthat all of the other components are in normal status.

End of procedure



92

Chapter 6

Maintenance

This chapter describes maintenance for the ETERNUS DX Disk storage system.

6.1 Periodic Backup

In case of a system failure, important data should be regularly backed up.

6.2 Volume Formatting Time

Table 6.1 shows the time for volume formatting (when the volume capacity is 100GB).

Table 6.1 Time for volume formatting (disk)

*1: The value shows the time required for volume formatting when the volume capacity is 100GB and there is no serverI/O. The time that is required depends on the type and configuration of the disk.

CAUTIONDo

• We recommend that you backup important data regularly. If the ETERNUS DX Disk storage system fails and the data has not been backed up, it may be lost.

RAID level Number of disks

Volume formatting time (*1)

2.5" SAS disks 3.5" SAS disks Nearline SAS disks

RAID1 2 Approx. 40 minutes/100GB

Approx. 35 minutes/100GB


RAID1+0 8 Approx. 30 minutes/100GB














93

Chapter 6 Maintenance 6.3 Rebuild/Copyback Process Time

6.3 Rebuild/Copyback Process Time

This section explains the time required for Rebuild/Copyback.

■ Rebuild process time

Table 6.2 shows the time required for the rebuild process (when the volume capacity is 100GB).

Table 6.2 Rebuild process time (disk)

*1: The value shows the rebuild process time when the volume capacity is 100GB and there is no server I/O. The timethat is required depends on the type and configuration of the disk.

■ Copyback process time

Table 6.3 shows the time required for the copyback process (when the volume capacity is 100GB).

Table 6.3 Copyback process time (disk)

*1: The value shows the copyback process time when the volume capacity is 100GB and there is no server I/O. The timethat is required depends on the type and configuration of the disk.


Rebuild process time (*1)


















Copyback process time (*1)



















94

Chapter 6 Maintenance 6.4 Maintenance Service

6.4 Maintenance Service

This section explains the ETERNUS DX Disk storage system maintenance service.

6.4.1 Maintenance Support Period

The standard maintenance support period for ETERNUS DX Disk storage system is five years from the date ofpurchase, or is defined in your service level agreement (SLA). Contact your sales representative for details ifyou prefer to extend the period.

6.4.2 Related Service

■ Remote support

If a possible error that may occur is detected or an error occurs when remote support service is used, thecontents of events are automatically sent to the remote support center and notified to the user.

When performing maintenance service, the maintenance engineer connects a PC used for maintenance to the ETERNUS DX Disk storage system. Also, the maintenance engineer may require information that is necessary for performing maintenance operations.If the maintenance engineer has any requirement, we ask that they be handled.



95

Chapter 7

Troubleshooting

This chapter explains troubleshooting when errors occur.

If something unusual occurs during operation (such as the instances listed below), refer to "7.1 Check List"(page 96) to check the ETERNUS DX Disk storage system status, and contact your maintenance engineeraccording to "7.2 Required Information for Inquiries" (page 102).

• When the ETERNUS DX Disk storage system is turned off

• When the ETERNUS DX Disk storage system refuses to turn on

• When the READY LED is not on

• When the FAULT LED is on

• When the FAULT LED blinks

• When the ETERNUS DX Disk storage system cannot be connected via a network service

• When the license key cannot be registered

• When I/O access is slow

• When the server does not recognize the volumes

7.1 Check List

■ When the ETERNUS DX Disk storage system is turned off

Check the following points. If none of these resolve the problem, leave the ETERNUS DX Disk storage systemalone and contact your maintenance engineer.

• Is the ETERNUS DX Disk storage system's power cord disconnected?

• Is PSU switch of the power supply unit turned to OFF (O)?

• Has the server been turned off?If the ETERNUS DX Disk storage system power is in conjunction with the power synchronized unit, thepower of the ETERNUS DX Disk storage system will turn off when the server is turned off.

• Is the main line switch of the power distribution unit turned OFF (O)?

• Is there a power failure?

• Has there been a recent main power failure?If the Power Resume function is enabled, the ETERNUS DX Disk storage system turns on automatically afterthe power is restored.



96

Chapter 7 Troubleshooting 7.1 Check List

■ When the ETERNUS DX Disk storage system refuses to turn on


• Is the ETERNUS DX Disk storage system's power cord disconnected?

• Is PSU switch of the power supply unit turned to OFF (O)?

• Is the main line switch of the power distribution unit turned OFF (O)?

• Is there a power failure?

• Is the QSFP cable disconnected?

■ When the READY LED is not on

If more than ten minutes have passed since the ETERNUS DX Disk storage system's power was turned on andthe READY LED still has not turned on, contact your maintenance engineer.

■ When the FAULT LED is on

Check the general status and the system messages in ETERNUS Web GUI. Perform the necessary actions tocorrect the problem. If the problem cannot be resolved, leave the ETERNUS DX Disk storage system alone andcontact your maintenance engineer.

• When the general status of ETERNUS Web GUI is

- Check whether one side of the QSFP cable is disconnected. If so, install the connector in the DI port.

- Check if the QSFP cable is connected. If the QSFP cable is not connected, use the following procedure to connect the QSFP cable.

Procedure

1 Press the controller enclosure’s Power switch for four seconds or more to turn off the ETERNUS DX Disk storage system.Drive enclosures with no QSFP cables connected will remain on.

2 Connect the QSFP cable while the drive enclosure is on.

3 Press the controller enclosure’s Power switch to turn on the ETERNUS DX Disk storage system.

End of procedure

When checking the general status via ETERNUS CLI, refer to "ETERNUS CLI User’s Guide".



97


- Check that the "●" (IN) and "■" (OUT) side of the QSFP cable is connected correctly. If the QSFP cable is connected incorrectly, use the following procedure to reconnect the QSFP cable.

Procedure

1 Press the controller enclosure’s Power switch for four seconds or more to turn off the ETERNUS DX Disk storage system, and turn off the AC power.

2 Reconnect the QSFP cable.

3 Make sure that power is being supplied, then turn the ETERNUS DX Disk storage system on.

End of procedure

• When the general status of ETERNUS Web GUI is Check whether the QSFP cables are connected in the correct order or check that the "●" (IN) and "■" (OUT)side of the QSFP cable is connected correctly. If not, use the following procedure to reconnect the QSFPcables.

Procedure

1 Press the controller enclosure’s Power switch for four seconds or more to turn off the ETERNUS DX Disk storage system, and turn off the AC power.

2 Reconnect the QSFP cable.

3 Make sure that power is being supplied, then turn the ETERNUS DX Disk storage system on.

End of procedure

■ When the FAULT LED blinks

Check the general status and the system messages in ETERNUS Web GUI. A general status of indicates that the ETERNUS DX Disk storage system contains a component that requires preventivemaintenance.

In the details screen for each component, check the detailed information for each component with a andcontact your maintenance engineer.

When checking the general status via ETERNUS CLI, refer to "ETERNUS CLI User’s Guide".



98


■ When the ETERNUS DX Disk storage system cannot be connected via a network service

Check the following points. If none of these resolve the problem, contact your maintenance engineer.

• Is the ETERNUS DX Disk storage system turned off?

• Has the LAN cable become disconnected? For a dual-controller type, does the controller to which the LAN cable is connected have an unlit MASTER LED?

• Have any network devices (such as LAN switch or router) failed? Are the network device settings invalid?

• Are the environment settings for the network service invalid?

• Is the IP address incorrect?

• Are the settings for the ETERNUS DX Disk storage system LAN ports (firewall) invalid?

If the problem is not resolved, follow the procedure below to restore the default values for the ETERNUS DXDisk storage system network environment settings and the firewall settings.

Procedure

1 Remove the flange cover of the controller enclosure.

2 Change the status of the ETERNUS DX Disk storage system to maintenance status.Use the pin that is provided with the ETERNUS DX Disk storage system to push down the FUNCTIONbutton for three seconds.

The ETERNUS DX Disk storage system is in maintenance status when the MAINT/ID LED is green.

Note that the settings (network environment settings and firewall settings) for all of the LAN ports are initialized after the following procedure is performed.



99


3 Use the pin to push down the FUNCTION button three times within three seconds.After the default settings of the LAN ports are restored, the MAINT/ID blinks green for a few seconds.

4 Release maintenance status.Use the pin to push down the FUNCTION button for three seconds. The MAINT/ID LED turns off.

5 Access ETERNUS Web GUI or ETERNUS CLI by using the default IP address to perform the network environment settings and the firewall settings.

6 Check whether the ETERNUS DX Disk storage system can connect to each service.If it cannot connect, contact your maintenance engineer.

End of procedure

■ When the license key cannot be registered

A wrong serial number may have been input when issuing the license key. If the problem persists, contactyour sales representatives.When issuing the license key again, make sure to check that the [Serial number] (ETERNUS DX Disk storagesystem serial number) that is described in the notification e-mail is correct.

■ When I/O access is slow

Check the following points. When the cause is not identified, contact your maintenance engineer.

• Check that the ambient temperature does not exceed the operating environment conditions.If so, Nearline SAS drive performance may be reduced.

• Click the icon of each part on the [Storage] screen of [Component] of ETERNUS Web GUI to check if an abnormality is detected in ETERNUS DX Disk storage system parts.If an abnormality is detected, contact your maintenance engineer.

Make sure to enable the firewall setting for the protocol that is used for each service.• To use ETERNUS Web GUI, enable the http or https connection. If not, the ETERNUS DX Disk storage

system cannot connect to the network via GUI.• To use ETERNUS CLI, enable the telnet or SSH connection. If not, the ETERNUS DX Disk storage

system cannot connect to the network via CLI.• To use the "ping" command for the ETERNUS DX Disk storage system, enable the ICMP connection.

If not, the ETERNUS DX Disk storage system does not respond to the "ping" command.• To use monitoring software, enable the Maintenance Secure connection. If not, the ETERNUS DX

Disk storage system cannot connect to the network via monitoring software.• To use the SNMP Manager, enable the SNMP connection. If not, the ETERNUS DX Disk storage

system does not respond to SNMP access.



100


• Check the path status.

- When using the ETERNUS Multipath Driver, start ETERNUS Multipath Manager.If an abnormality is detected in a path, refer to the ETERNUS Multipath Driver manuals and follow thedirection given in the manuals.

- When not using the ETERNUS Multipath Driver, use the path management tool and check the path status that each software provides, and handle the problem if necessary.

• Check the loading of the ETERNUS DX Disk storage system. If the load is out of balance because of operation content changing or for other reasons, review the configuration and settings.

• Check the transfer speed of the FC port.If the transfer speed for the ETERNUS DX Disk storage system is different from the server or the FC switch,set the same transfer speed as the server or FC switch.

• Check the number of command queues in the server.When there are no problems in the process capacity of the server, adjust the number of command queuesso that the I/Os are issued for the appropriate number.For details on the number of command queues, refer to "User's Guide -Server Connection-".

• Check the status of the RAID group.When rebuild, copyback, or redundant copy is being performed in a RAID group with a "High" rebuildpriority, the performance may be reduced until the operation is complete.

• Check the cache parameter settings of the volumes.If the Force Prefetch mode of the volumes that are used for image distribution is disabled, performancemay be reduced. Enable the Force Prefetch mode and specify the appropriate value for the Prefetch Limit. Note that the Force Prefetch mode for volumes that are not used for image distribution must be disabled.

■ When the server does not recognize the volumes


• Check the status of the ETERNUS DX Disk storage system and other devices such as network devices connecting the server and the ETERNUS DX Disk storage system, and ensure that there are no problems with the power supply.

• Check if an error occurs in a path by using a path management tool such as ETERNUS Multipath Manager. Refer to the relevant manuals and take the required actions.



101

Chapter 7 Troubleshooting 7.2 Required Information for Inquiries

7.2 Required Information for Inquiries

Before contacting your maintenance engineer when trouble occurs, prepare the following information: Fordetails on the maintenance service, refer to "6.4 Maintenance Service" (page 95).

● The model name and the serial number of the ETERNUS DX Disk storage system

This information can be checked by using a device ID label, ETERNUS Web GUI, or ETERNUS CLI.

● Details about the trouble, any actions taken, and the results of these actions.

● The devices that are connected to the ETERNUS DX Disk storage system

- The models of the server and network devices- The power synchronized unit model- The UPS model

● Log/dump information for the ETERNUS DX Disk storage system

When your maintenance engineer asks for the log/dump information of the ETERNUS DX Disk storagesystem, obtain the required log/dump information using the log/dump collection function of ETERNUS WebGUI.Refer to "ETERNUS Web GUI User’s Guide" for how to obtain this information.

Device ID label

MODEL. ETxxxxx

SERIAL. xxxxxxxxxx

Model name

Serial number

ETERNUS Web GUI screenModel name-Serial number

CLI> show enclosure-status

Enclosure View

Name [ETERNUS DX90 S2]

Model Upgrade Status [Upgraded]

Model Name [ETxxxxxx]

Serial Number [xxxxxxxxxx]

:

ETERNUS CLI ("show enclosure-status" command)

Model name

Serial number



102

Appendix A

Event Notification Message List

This appendix describes the messages that are notified when event notification is enabled in the e-mailnotification settings of ETERNUS Web GUI or ETERNUS CLI.

A.1 Message Format

This section describes the format and content of the event notification messages listed below.

• E-mail• Syslog• SNMP• Host Sense

A.1.1 E-mail

An example of event notification by e-mail and its contents are shown below:

■ Output example of event notification

The number under each underline indicates an item in the table below. A description is provided for eachitem.

• Subject

• Message

This is ETxxxxx notification message. Serial No: 0000000000 (Information)1 2 3

user comment.

EVENT:3 volume(s) created

EVENT CODE: I 01030010

SEVERITY: Information

REPORT NO: 0-0005

DATE: JAN 26 11:16:00 2011

DETAIL:No=23 Name=vol2 Type=Open Capacity=256MB RAID_Group_No=0 RAID_Group_Name=RG00No=24 Name=vol3 Type=Open Capacity=256MB RAID_Group_No=1 RAID_Group_Name=RG01No=25 Name=vol4 Type=Open Capacity=256MB RAID_Group_No=2 RAID_Group_Name=RG02

4

5

6

7

8

9

10



103

Appendix A Event Notification Message List A.1 Message Format

■ Descriptions of the event notification contents

Number Description

Subject 1 The model name of the ETERNUS DX Disk storage system is displayed.

2 The serial number of the ETERNUS DX Disk storage system is displayed.

3 The Severity of the event is displayed. One of the following items is displayed for the message:

Error: indicates an errorWarning: indicates a warningInformation: indicates that information is providedTest: indicates a test mail

Message 4 A comment that is set using the e-mail notification setting of ETERNUS Web GUI or ETERNUS CLI is displayed.

5 A message that indicates the event is displayed.For more details, refer to "A.2 Message List" (page 112).

6 The message event type and the event code that are separated by a blank are displayed.One of the following letters is output as an event type:

"P", "J", "M", "I", "R"Event code is an 8-digit hexadecimal number according to the message.For more details, refer to "A.2 Message List" (page 112).

7 The Severity of the event is displayed. One of the following items is displayed for the message:

Error: indicates an errorWarning: indicates a warningInformation: indicates that information is providedTest: indicates a test mail

8 The event serial number, which increases from the startup of the ETERNUS DX Disk storage system, is displayed in the "x-yyyy" format.

x: Controller number (0 or 1)yyyy: Serial number

The event serial number is reset when the ETERNUS DX Disk storage system is turned on or restarted.

9 The time when the event occurred is displayed in the "Mmm dd hh:mm:ss yyyy" format.Mmm: Abbreviation of each month (Jan – Dec)dd: Date. If the date is a single digit, "0" is output before the date number.hh:mm:ss: "hh" indicates the hour (00 – 23), "mm" indicates minutes (00 – 59), and "ss" indicates seconds (00 – 59).yyyy: The year is display with four digits.

10 The detailed information of the event is displayed. For multiple process results, each process result is displayed on a separate line.



104


A.1.2 Syslog

The following formats are available for notification of syslog: "RFC3164" and "RFC5424". The notificationformat is specified in ETERNUS Web GUI or ETERNUS CLI.

This section describes examples of syslogs and the details of formats that are output.

■ Output example of a syslog


• "RFC3164" format

• "RFC5424" format

■ Description of each syslog item

<14>Jan 26 11:26:08 10.21.138.81 Storage: 00, 4, I 01030020 5 volume(s) deleted

[No=38 Name=VOL40#0] [No=39 Name=VOL40#1] [No=40 Name=VOL40#2]

[No=41 Name=VOL40#3] [No=42 Name=VOL40#4]

1 2 3 4 5 6 7 8

8

8

<14>1 2011-01-26T11:26:08+09:00 10.21.138.81 Storage 00 4 - I 01030020

5 volume(s) deleted [No=38 Name=VOL40#0] [No=39 Name=VOL40#1]

[No=40 Name=VOL40#2] [No=41 Name=VOL40#3] [No=42 Name=VOL40#4]

8

8

1 2 3 4 5 6 7

No. Item Description

1 Priority Priority of the message is output in the following format:<Priority>Priority value indicates the facility and severity of the message. The Priority value is calculated by "Facility value × 8 + Severity value".Facility value for messages is always "1".Severity values for messages are one of the following values:3: Error4: Warning6: InformationalFor the "RFC3164" format, the HEADER part follows the PRI part.For the "RFC5424" format, "1" and then a blank follow the PRI part.



105


2 Time stamp The local time when the event is detected is output in the following format:

• For RFC3164Mmm dd hh:mm:ss

- MmmAbbreviation of each month (Jan - Dec)

- ddDate. If the date is a single digit, a blank is output before the date number.

- hh:mm:ssLocal time. "hh" indicates the hour (00 – 23), "mm" indicates minutes (00 – 59), and "ss" indicates seconds (00 – 59). A blank follows this item.

• For RFC5424yyyy-mm-ddThh:mm:ss±hh:mm

- yyyyThe year is displayed with four digits.

- mmThe month is displayed with two digits (01 – 12).

- ddThe date is displayed with two digits (01 – 31). "T" follows this item.


- ±hh:mmTime differences between the local time and the GMT. The value for the time zone specified in the date and time setting of ETERNUS Web GUI or ETERNUS CLI is displayed. "hh" indicates the hour (00 – 23) and "mm" indicates minutes (00 – 59). A blank follows this item.

3 Host name The IP address of the sender port (MNT or RMT) for the ETERNUS DX Disk storage system is output in IPv4 or IPv6 format:

• IPv4xxx.xxx.xxx.xxxThe IPv4 address is output based on the "IETF STD13, RFC 1035" specification.

• IPv6xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxxThe IPv6 address is output based on the "RFC 4291" specification.

A blank follows this item.

4 Program or process The name of the program or process that generates the message is output."Storage" is output for all the messages. For the "RFC3164" format, a colon [:] and then a blank, which indicate the end of the TAG field, follow this item.For the "RFC5424" format, a blank follows this item.

5 CM No. and message type

The CM number of the controller that outputs the message and the message type are output."0" or "1" is output according to the message for the CM No."0" is output for the message type.For the "RFC3164" format, a comma and then a blank follow this item.For the "RFC5424" format, a blank follows this item.

6 Message serial number

The message serial number is displayed for each controller.For the "RFC3164" format, a comma and then a blank follow this item.For the "RFC5424" format, a blank, a hyphen, and a blank follow this item in this order.




106


A.1.3 SNMP

The ETERNUS DX Disk storage system supports three versions of SNMP: SNMPv1, SNMPv2c, and SNMPv3.SNMPv3 supports MD5 and SHA as the authentication method and DES as the encryption method.To monitor the ETERNUS DX Disk storage system using SNMP Trap, software that can receive and analyzeSNMP Traps must be used on the network.This section describes the type and the notification format of Traps. For details on the messages that arenotified by SNMP Trap, refer to "A.2 Message List" (page 112).For the display contents of events (SNMP Traps) when using the server management software "ServerViewOperation Manager" for monitoring the ETERNUS DX Disk storage system, refer to "Appendix C Event (SNMPTrap) Display When Using ServerView Operation Manager" (page 183).

■ Trap type

There are two types of Traps: Generic Trap (standard Trap) and Specific Trap (extended Trap). Generic Trap is aTrap that is defined by the SNMP protocol. Specific Trap is a Trap that has been created specifically for theETERNUS DX Disk storage system. The ETERNUS DX Disk storage system supports the following types of Traps:

● Generic Trap (standard Trap)

7 Event type and event code

The message event type and the event code that are separated by a blank are output.One of the following letters is output as an event type: "P", "J", "M", "I", "R"Event code is an 8-digit hexadecimal number according to the message.Refer to "A.2 Message List" (page 112) for details.

8 Message A message that indicates the event and its detailed information are output in text format. For multiple process results, each process result is enclosed by brackets.Refer to "A.2 Message List" (page 112) for details.


Trap No. Name Description

0 coldStart For an ETERNUS DX Disk storage system, this Trap is sent when the controller starts up or restarts and when SNMP is set.

4 authentictionFailure An unauthorized access occurred.

6 enterpriseSepecific Extended Trap



107


● Specific Trap (extended Trap)

■ Trap notification format

The notification format of SNMPv1, SNMPv2c and SNMPv3 are shown below.

● Generic Trap (standard Trap)

• SNMPv1

• SNMPv2c and SNMPv3

Trap No. Name Description

2 fjdarye100ItemFault This Trap is sent to notify that a component fails or degrades.

5 fjdarye100ItemWarning This Trap is sent to notify that a component requires preventive maintenance.

6 fjdarye100SensorStatusChange This Trap is sent to notify that a temperature error is detected.

7 fjdarye100MaintenanceRequired This Trap is sent to notify that an event requires maintenance or preventive maintenance.

9 fjdarye100Information This Trap is sent to notify Information-level events.

10 fjdarye100CaPortLinkStatusChange This trap is sent to notify that the link status of a CA port is changed.

22 fjdarye100ItemFaultToNormal This Trap is sent to notify that an event notified by Trap No. 2 returns to normal status.

25 fjdarye100ItemWarningToNormal This Trap is sent to notify that an event notified by Trap No. 5 returns to normal status.

26 fjdarye100SensorStatusChangeToNormal This Trap is sent to notify that an event notified by Trap No. 6 returns to normal status.

Trap type enterprise agent-address generic- trap

specific- trap

time-stamp variable-bindings

coldStart 1.3.6.1.6.3.1.1.5 The IP address of the Master CM for the port (MNT or RMT) that is specified in the SNMP Agent environment setting.

0 0 The operation time of the SNMP Agent (centiseconds)The operation time is reset when the SNMP Agent starts or restarts.

N/A

authenticationFailure 4 N/A

Trap typevariable-bindings

Information [1]:sysUpTimeInformation

[2]:snmpTrapOID Information [3] or later

coldStart The operation time of the SNMP Agent (centiseconds)The operation time is reset when the SNMP Agent starts or restarts.

1.3.6.1.6.3.1.1.5.1 N/A

authenticationFailure 1.3.6.1.6.3.1.1.5.5 N/A



108


● Specific Trap (extended Trap)

• SNMPv1

Trap type

ente

rpris

e

agen

t-ad

dres

s

gene

ric-t

rap

spec

ific-

trap

time-

stam

p

varia

ble-

bind

ings

Trap

No.

Nam

e

Des

crip

tion

2 fjdarye100ItemFault

Notification of component failure or component degradation

1.3.6.1.4.1.211.4.1.1.126.1.100

The IP address of the Master CM for the port (MNT or RMT) that is specified in the SNMP Agent environment setting

6 2 The operation time of the SNMP Agent (centiseconds)The operation time is reset when the SNMP Agent starts or restarts.

Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapMessage

5 fjdarye100ItemWarning

Notification of events that require preventive maintenance

5 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapMessageInformation [4]:fjdaryTrapWarningInfo

6 fjdarye100SensorStatusChange

Notification of temperature error

6 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapSensorInfoInformation [4]:fjdaryTrapMessage

7 fjdarye100MaintenanceRequired

Notification of events that require maintenance or preventive maintenance

7 Information [1]:fjdarySspMachineIdInformation [2]:fjdaryTrapMaintenanceInfoInformation [3]:fjdaryTrapMessage

9 fjdarye100Information

Information notification

9 Information [1]:fjdarySspMachineIdInformation [2]:fjdaryTrapMessage

10 fjdarye100CaPortLinkStatusChange

Notification of a change in the CA port link status

10 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapLinkStatusInfoInformation [4]:fjdaryTrapMessage

22 fjdarye100ItemFaultToNormal

Notification of alarm cancel for TRAP No. 2

22 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapMessage

25 fjdarye100ItemWarningToNormal


25 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapMessageInformation [4]:fjdaryTrapWarningInfo

26 fjdarye100SensorStatusChangeToNormal


26 Information [1]:fjdaryTrapItemIdInformation [2]:fjdarySspMachineIdInformation [3]:fjdaryTrapSensorInfoInformation [4]:fjdaryTrapMessage



109


• SNMPv2c and SNMPv3

Trap type variable-bindings

Trap

No.

Nam

e

Des

crip

tion

Info

rmat

ion

[1]:

sysU

pTim

e

Info

rmat

ion

[2]:

snm

pTra

pOID

Info

rmat

ion

[3]

or la

ter

2 fjdarye100ItemFault

Notification of component failure or component degradation

The operation time of the SNMP Agent (centiseconds)The operation time is reset when the SNMP Agent starts or restarts.

1.3.6.1.4.1.211.4.1.1.126.1.100.0.2


5 fjdarye100ItemWarning

Notification of events that require preventive maintenance

1.3.6.1.4.1.211.4.1.1.126.1.100.0.5

Information [3]:fjdaryTrapItemIdInformation [4]:fjdarySspMachineIdInformation [5]:fjdaryTrapMessageInformation [6]:fjdaryTrapWarningInfo

6 fjdarye100SensorStatusChange

Notification of temperature error

1.3.6.1.4.1.211.4.1.1.126.1.100.0.6

Information [3]:fjdaryTrapItemIdInformation [4]:fjdarySspMachineIdInformation [5]:fjdaryTrapSensorInfoInformation [6]:fjdaryTrapMessage

7 fjdarye100MaintenanceRequired

Notification of events that require maintenance or preventive maintenance

1.3.6.1.4.1.211.4.1.1.126.1.100.0.7

Information [3]:fjdarySspMachineIdInformation [4]:fjdaryTrapMaintenanceInfoInformation [5]:fjdaryTrapMessage

9 fjdarye100Information

Information notification

1.3.6.1.4.1.211.4.1.1.126.1.100.0.9

Information [3]:fjdarySspMachineIdInformation [4]:fjdaryTrapMessage

10 fjdarye100CaPortLinkStatusChange

Notification of a change in the CA port link status

1.3.6.1.4.1.211.4.1.1.126.1.100.0.10

Information [3]:fjdaryTrapItemIdInformation [4]:fjdarySspMachineIdInformation [5]:fjdaryTrapLinkStatusInfoInformation [6]:fjdaryTrapMessage

22 fjdarye100ItemFaultToNormal


1.3.6.1.4.1.211.4.1.1.126.1.100.0.22


25 fjdarye100ItemWarningToNormal


1.3.6.1.4.1.211.4.1.1.126.1.100.0.25

Information [3]:fjdaryTrapItemIdInformation [4]:fjdarySspMachineIdInformation [5]:fjdaryTrapMessageInformation [6]:fjdaryTrapWarningInfo

26 fjdarye100SensorStatusChangeToNormal


1.3.6.1.4.1.211.4.1.1.126.1.100.0.26

Information [3]:fjdaryTrapItemIdInformation [4]:fjdarySspMachineIdInformation [5]:fjdaryTrapSensorInfoInformation [6]:fjdaryTrapMessage



110


● variable-bindings meanings

A.1.4 Host Sense

The ETERNUS DX Disk storage system returns the host sense (sense code) to the server when an error occurs inthe ETERNUS DX Disk storage system.

The cause of the error can be determined by using SK (Sense Key), ASC (Additional Sense Code), and ASCQ(Additional Sense Code Qualifier) as the host sense.

The conversion pattern of the sense code that is notified to the server is set by using the host responsesettings of ETERNUS Web GUI or ETERNUS CLI.For details on the sense code that is notified to the server, refer to "A.2.6 Sense Codes" (page 149).

MIB object name MIB object ID Description

sysUpTime 1.3.6.1.2.1.1.3.0 Indicates the operation time of the SNMP Agent (centiseconds).The operation time is reset when the SNMP Agent starts or restarts.

snmpTrapOID 1.3.6.1.6.3.1.1.4.1.0 Indicates the Object ID that identifies the type of Trap.

fjdarySspMachineId 1.3.6.1.4.1.211.1.21.1.100.1.1.0 Indicates the ID of the ETERNUS DX Disk storage system.

fjdaryTrapMessage 1.3.6.1.4.1.211.1.21.1.100.11.0 Indicates the message (event type code + ' ' (blank) + message).

fjdaryTrapItemId 1.3.6.1.4.1.211.1.21.1.100.7.0 Indicates the value that identifies the component.

fjdaryTrapWarningInfo 1.3.6.1.4.1.211.1.21.1.100.10.0 Indicates additional information for an event that is used by Specific Trap No. 5 and Trap No. 25.

fjdaryTrapSensorInfo 1.3.6.1.4.1.211.1.21.1.100.8.0 Indicates additional information for an event that is used by Specific Trap No. 6 and Trap No. 26.

fjdaryTrapMaintenanceInfo 1.3.6.1.4.1.211.1.21.1.100.9.0 Indicates additional information for an event that is used by Specific Trap No. 7.

fjdaryTrapLinkStatusInfo 1.3.6.1.4.1.211.1.21.1.100.15.0 Indicates additional information for an event that is used by Specific Trap No. 10.



111

Appendix A Event Notification Message List A.2 Message List

A.2 Message List

This section describes the event notification messages for each severity.

A.2.1 Common Terms

The following table shows components and terms that are used in "A.2.2 Error Messages" (page 113) to "A.2.4Informational Messages" (page 143).

Abbreviation Meaning Description

CM Controller Module Units that control all the operations in the ETERNUS DX Disk storage system.

CA Channel AdapterHost interfaces between the ETERNUS DX Disk storage system and server.

CE Controller Enclosure Cabinets for installing CMs and CAs.

DE Drive Enclosure Cabinets for installing drives.

DI Drive Interface Back-end interface modules in CMs.

BUDBootup and Utility Device

A device in a CM in which the system area is allocated.

IOM I/O module Units that control the connection between CM and drives.

EXP Expander Expander chips in a CM that are used for SAS connection.

SCU System Capacitor Unit A device in a CM that supplies power to back up the cache memory data in the non-volatile memory when a power failure occurs.

CA SFPCA Small Form Factor Pluggable

SFP modules that are installed in CAs.

CA SFP+CA Small Form Factor Pluggable+

SFP+ modules that are installed in CAs.

PSU Power Supply Unit Power supply units for units in CEs or DEs.

Abbreviation Meaning

HS Hot spares

TPV Thin Provisioning Volume(s)

TPP Thin Provisioning Pool

SMART Self-Monitoring Analysis and Reporting Technology

F/W Firmware

HDD Hard Disk Drive

SSD Solid State Drive

DMA Direct Memory Access



112


A.2.2 Error Messages

This section describes the messages that are sent when the severity is Error for each type of event.

■ Error message list

● When the event type is "P"

The following messages are sent when components fail or degrade or when a temperature error isdetected.

Event type code

SNMP Trap Upper: Message

RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description

P 01SSMM00 2 0100MM00 - Controller Module#m(zz) Fault <pppppppppppp ssssssssss rrrrr>

These messages are notified when "Parts Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

CM is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

P 02SSMM0p 2 0200MM0p - Controller Module#m(zz) DMA PORT#p Fault <pppppppppppp ssssssssss rrrrr>

CM DMA port is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 03SSMM0v 2 0300MM0v - Controller Module#m(zz) BIOS#v Fault <pppppppppppp ssssssssss rrrrr>

CM BIOS is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)v: Device number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 04SSMM00 2 0400MM00 - Controller Module#m(zz) RTC Fault <pppppppppppp ssssssssss rrrrr>

CM RTC is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version



113


P 05SSMM00 2 0500MM00 - Controller Module#m(zz) NVRAM Fault <pppppppppppp ssssssssss rrrrr>


CM NVRAM is disconnected.SS: Component subtypeMM: CM module ID (10 - 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

P 06SSMM0v 2 0600MM0v - Controller Module#m(zz) EXP#v Fault <pppppppppppp ssssssssss rrrrr>

CM EXP is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)v: EXP number (0)pp...: Component numberss...: Serial numberrr...: Version

P 08SSMMvp 2 0800MMvp - Controller Module#m(zz) DI Port#P Fault <pppppppppppp ssssssssss rrrrr>

CM DI port is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)v: Device number (0)p: Device port number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 09SSMMvp 2 0900MMvp - Controller Module#m(zz) EXP#v In Port#p Fault <pppppppppppp ssssssssss rrrrr>

CM EXP IN port is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)v: EXP number (0)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



114


P 0ASSMMvp 2 0A00MMvp - Controller Module#m(zz) EXP#v Out Port#p Fault <pppppppppppp ssssssssss rrrrr>


CM EXP Out port is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)v: EXP number (0)p: Port number (0)pp...: Component numberss...: Serial numberrr...: Version

P 0BSSMMnn 2 0B00MMnn - Controller Module#m(zz) Cache(MEM #xGB) Slot#nn Fault <pppppppppppp ssssssssss rrrrr>

CM memory is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)x: Capacity of the cache memory (2 or 4)nn: Slot number of the cache memory (0)pp...: Component numberss...: Serial numberrr...: Version

P 0CSSMM0v 2 0C00MM0v - Controller Module#m(zz) BUD#v (#xxGB) Fault <pppppppppppp ssssssssss rrrrr>

CM BUD is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)v: Device number (0)xx: Capacity of BUD (2)pp...: Component numberss...: Serial numberrr...: Version

P 0ESSMM00 2 0E00MM00 - Controller Module#m(zz) NAND Controller Fault <ppppppppppppp ssssssssss rrrrr>

CM NAND Controller is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



115


P 0FSSMM00 2 0F00MM00 - Controller Module#m(zz) SCU Fault <pppppppppppp ssssssssss rrrrr>


CM SCU is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

P 10SSMM00 2 1000MM00 - CA Slot#S-V(zz) (on CM#m) Fault <pppppppppppp ssssssssss rrrrr>

CA is disconnected.SS: Component subtypeMM: CA module ID (40 – 7F)S: CA slot number (0 – 1)V: Device number (0 – 1)zz: CA typem: CM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 11SSMM0p 2 1100MM0p - CA Slot#S-V(zz) (on CM#m) Port#P Fault <pppppppppppp ssssssssss rrrrr>

CA port is disconnected.SS: Component subtypeMM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)V: Device number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 1700MM0p 2 1700MM0p - FC16G SFP+ CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>

CA SFP+ is disconnected.MM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Versionoo...: Additional information

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



116


P 1900MM0p 2 1900MM0p - FC SFP+ Longwave CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>



P 1A00MM0p 2 1A00MM0p - FC SFP CA Slot#S(zz) (on CM#m) Port#P Fault <ppppppppppppppppp ssssssssssssssss rrrr oooooooo>

CA SFP is disconnected.MM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Versionoo...: Additional information

P 1C00MM0p 2 1C00MM0p - FC SFP+ CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>


P 1D00MM0p 2 1D00MM0p - iSCSI FCoE SFP+ CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>


Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



117


P 1E00MM0p 2 1E00MM0p - iSCSI FCoE SFP+Cp CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>


Copper CA SFP+ is disconnected.MM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Versionoo...: Additional information

P 1F00MM0p 2 1F00MM0p - SFP(Type Unknown) CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>

CA SFP is disconnected due to an SFP type that cannot be recognized.

MM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Versionoo...: Additional information

P 1E00MM0p 2 1E00MM0p - iSCSI FCoE SFP+Cp CA Slot#S(zz) (on CM#m) Port#P Fault <pppppppppppppppp ssssssssssssssss rrrr oooooooo>

Copper CA SFP+ is disconnected.MM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Versionoo...: Additional information

P 21SSMM00 (When SS is not 83)

2 2100MM00 - Controller Module#m(zz) FPGA Fault <pppppppppppp ssssssssssss rrrr>

CM FPGA is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



118


P 21830xxx 2 21830xxx - Disk Drive DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Redundant Copy end <pppppppppppp ssssssssssss rrrr>

These messages are notified when "Complete Redundant Copy" is enabled for Error Severity Level in the event notification setting.These messages are not notified during maintenance operations.

Redundant copy of a HDD is complete.xxx: RAID group numberuu: DE-IDnn: Disk slot number (decimal)

3.5" drives: 00 - 112.5" drives: 00 - 23

xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk type (RAID level)pp...: Component numberss...: Serial numberrr...: Version

P 21830xxx 2 21830xxx - SSD 3.5 DE#uu-Slot#nn(SAS xxxGB ccccccc) Redundant Copy end <pppppppppppp ssssssssssss rrrr>

Redundant copy of a 3.5" SSD is complete.xxx: RAID group numberuu: DE-IDnn: Drive slot number (0 - 11 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive type (RAID level)pp...: Component numberss...: Serial numberrr...: Version

P 21830xxx 2 21830xxx - SSD 2.5 DE#uu-Slot#nn(SAS xxxGB ccccccc) Redundant Copy end <pppppppppppp ssssssssssss rrrr>

Redundant copy of a 2.5" SSD is complete.xxx: RAID group numberuu: DE-IDnn: Drive slot number (0 - 23 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive type (RAID level)pp...: Component numberss...: Serial numberrr...: Version

P 22SSMM0p 2 2200MM0p - Controller Module#m(zz) LAN PORT#p Fault <pppppppppppp ssssssssssss rrrr>


CM LAN port is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)p: Port number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



119


P 2ASSMMvp 2 2A00MMvp - Controller Module#m(zz) QSFP#P Fault <pppppppppppp ssssssssssss rrrr>


CM QSFP is disconnected.SS: Component subtypeMM: CM module ID (10 – 11)v: Device number (0)p: Device port number (0 – 1)P: Port number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

P 80SSuu0N 2 8000uu0N - HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>

These messages are notified when "Disk Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

HDD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 80SSuu0N 2 8000uu0N - HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) Failed Usable <pppppppppppp ssssssssssss rrrr tttttt qq>


Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



120


P 80SSuu0N 2 8000uu0N - HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) Slow Down <pppppppppppp ssssssssssss rrrr tttttt qq>


Disk performance error is detected. HDD is disconnected.

SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 81SSuuNN 2 8000uuNN - HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>

HDD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 81SSuuNN 2 8000uuNN - HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Failed Usable <pppppppppppp ssssssssssss rrrr tttttt qq>

HDD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



121


P 81SSuuNN 2 8000uuNN - HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Slow Down <pppppppppppp ssssssssssss rrrr tttttt qq>


Disk performance error is detected. HDD is disconnected.

SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 84SSuu0N 2 8000uu0N - SSD 3.5 DE#uu-Disk#n(SAS xxxGB ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>

SSD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Drive slot number (0 – b (hexadecimal))n: Drive slot number (0 – 11 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 84SSuu0N 2 8000uu0N - SSD 3.5 DE#uu-Disk#n(SAS xxxGB ccccccc) Failed Usable <pppppppppppp ssssssssssss rrrr tttttt qq>


Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



122


P 85SSuuNN 2 8000uuNN - SSD 2.5 DE#uu-Disk#nn(SAS xxxGB ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>


SSD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Drive slot number (0 – 17 (hexadecimal))nn: Drive slot number (0 – 23 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 85SSuuNN 2 8000uuNN - SSD 2.5 DE#uu-Disk#nn(SAS xxxGB ccccccc) Failed Usable <pppppppppppp ssssssssssss rrrr tttttt qq>


P 88SSdd0N 2 8000uu0N - HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>


Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



123


P 88SSddNN 2 8000uuNN - HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>


HDD is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)cc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

P 88SSdd0N 2 8000uu0N - SSD 3.5 DE#uu-Disk#n(SAS xxxGB ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>


P 88SSddNN 2 8000uuNN - SSD 2.5 DE#uu-Disk#nn(SAS xxxGB ccccccc) Fault <pppppppppppp ssssssssssss rrrr tttttt qq>


Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



124


P 90SSuu0n 2 9000uu0n - IOM6 DE#uu/IOM#n Fault <pppppppppppp ssssssssss rrrrr>


IOM is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: IOM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 91SSuunp 2 9100uunp - IOM6 Port DE#uu/IOM#n/Port#p Fault <pppppppppppp ssssssssss rrrrr>

IOM port is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: IOM number (0 – 1)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P 9ASSuunp 2 9A00uunp - IOM6 QSFP DE#uu/IOM#n/Port#p Fault <pppppppppppp ssssssssss rrrrr>

IOM QSFP is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: IOM number (0 – 1)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P D2SSuu0n 2 D200uu0n - Power Supply Unit DE#uu/PSU#n Fault <pppppppppppp ssssssssss rrrr>

PSU is disconnected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: PSU slot number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

P DASSuu00 6 DA00uu00 2 DE Exhaust temperature DE#uu Fatal This message is noti-fied when "Tempera-ture Error" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

Exhaust temperature error (fatal error) is detected in CE or DE.

SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



125


● When the event type is "M"

The following messages are sent when an event that requires maintenance occurs:

P DASSuu00 2 DA00uu00 - DE Exhaust temperature sensor DE#uu Fault These messages are notified when "Parts Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

Exhaust temperature error (sensor failure) is detected in CE or DE.


P DBSSuu00 2 DB00uu00 - DE Intake temperature sensor DE#uu Fault

Intake temperature error (sensor failure) is detected in CE or DE.


Event type code


RemarksTrapNo.

TrapMaintenance

InfoLower: Description

M 0732MMPP 7 0732MMPP Remote Copy Path (CM#xx CA#yy PORT#zz) Not Available This message is noti-fied when "Remote Path Error" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

Disconnection of a REC path between cabinets is detected.MM: CA module IDPP: 00 or 01xx: CM numberyy: CA slot number (0 – 1)zz: Port number (0 – 1)

M 13CE0001 7 13CE0001 Error session was detected. (Local:xxxxx Remote:xxxxx) These messages are notified when "Copy Session Error" is enabled for Error Severity Level in the event notification set-ting. They are not notified during maintenance operations.

Errors were detected in the copy sessions. xxxxx: Number of copy sessions in error status

M 13CE0002 7 13CE0002 Foreseen error session was detected. (Local:xxxxx Remote:xxxxx)

Errors were detected in the copy sessions during suspension.xxxxx: Number of copy sessions in error status during

suspension

M 13CE0003 7 13CE0003 Halt session was detected. (Remote:xxxxx)

The copy sessions are in halt status.xxxxx: Number of copy sessions that are halted

M 13CE0004 7 13CE0004 Error session was cleared.

Errors in the copy sessions were cleared. The copy sessions are in normal status.

M 13CE0005 7 13CE0005 Foreseen error session was cleared.

Errors during suspension in the copy sessions were cleared. The copy sessions are in normal status.

M 13CE0006 7 13CE0006 Halt session was cleared.

Halt status in the copy session was removed. The copy ses-sionsares in normal status.

Event type code


RemarksTrap No.

TrapItemIDTrap

SensorInfo

Lower: Description



126


M 13CF11xx 7 13CF11xx REC Buffer HALT occured.(xx) These messages are notified when the fol-lowing items are enabled for Error Severity Level in the event notification setting:

• REC Buffer Halt (Path Error)

• REC Buffer Halt (Overload)

• REC Buffer Halt (Other Error)

These messages are not notified during maintenance opera-tions.

Occurrence of HALT in the REC Buffer is detected.xx: 00, 01, or 0200: Path error01: Overload02: Error

M 21810xxx 7 21810xxx RAID Group#0xxx recovered end of Rebuild processing This message is noti-fied when "Complete rebuild" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

Rebuild to the hot spare or the replaced drive is complete, but Bad Data (data lost identifier) exists.

xxx: RAID group number (hexadecimal)

M A0110xxx 7 A0110xxx RAID Group#0xxx start failure of Rebuild processing These messages are notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

Rebuild to the hot spare has not started.xxx: RAID group number

M A0410xxx 7 A0410xxx RAID Group#0xxx start procedure of Rebuild processing

Rebuild to the hot spare has started.xxx: RAID group number (hexadecimal)

M A0810xxx 7 A0810xxx RAID Group#0xxx normal end of Rebuild processing This message is noti-fied when "Rebuild/Copyback w/ redun-dant" is enabled for Error Severity Level in the event notification setting. This is not notified during main-tenance operations.

Rebuild to the hot spare is complete.xxx: RAID group number (hexadecimal)

Event type code


RemarksTrapNo.

TrapMaintenance




127


M A0A10xxx 7 A0A10xxx RAID Group#0xxx abnormal end of Rebuild processing because of source disk problem

These messages are notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

Rebuild to the hot spare is halted because an error is found in the copy source drive.


M A0B10xxx 7 A0B10xxx RAID Group#0xxx abnormal end of Rebuild processing

Rebuild to the hot spare is halted.xxx: RAID group number (hexadecimal)

M A0C10xxx 7 A0C10xxx RAID Group#0xxx retry procedure of Rebuild processing

Rebuild to the hot spare is retried.xxx: RAID group number (hexadecimal)

M A1410xxx 7 A1410xxx RAID Group#0xxx start procedure of Rebuild processing These messages are notified when "Rebuild/Copyback w/ redundant" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

Rebuild to the replaced drive has started.xxx: RAID group number (hexadecimal)

M A1810xxx 7 A1810xxx RAID Group#0xxx normal end of Rebuild processing

Rebuild to the replaced drive is complete.xxx: RAID group number (hexadecimal)

M A1A10xxx 7 A1A10xxx RAID Group#0xxx abnormal end of Rebuild processing because of source disk problem

These messages are notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

Rebuild to the replaced drive is halted because an error is found in the copy source drive.


M A1B10xxx 7 A1B10xxx RAID Group#0xxx abnormal end of Rebuild processing

Rebuild to the replaced drive is abnormally ended.xxx: RAID group number (hexadecimal)

M A1C10xxx 7 A1C10xxx RAID Group#0xxx retry procedure of Rebuild processing

Rebuild to the replaced drive is retried.xxx: RAID group number (hexadecimal)

M A3420xxx 7 A3420xxx RAID Group#0xxx start procedure of Copyback processing These messages are notified when "Rebuild/Copyback w/ redundant" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

Copyback to the replaced drive is being performed.xxx: RAID group number (hexadecimal)

M A3820xxx 7 A3820xxx RAID Group#0xxx normal end of Copyback processing

Copyback to the replaced drive is complete.xxx: RAID group number (hexadecimal)

Event type code


RemarksTrapNo.

TrapMaintenance




128


M A3A20xxx 7 A3A20xxx RAID Group#0xxx abnormal end of Copyback processing because of source disk problem

These messages are notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

Copyback to the replaced drive is halted because an error is found in the copy source drive.


M A3B20xxx 7 A3B20xxx RAID Group#0xxx abnormal end of Copyback processing

Copyback to the replaced drive is halted.xxx: RAID group number (hexadecimal)

M A3C20xxx 7 A3C20xxx RAID Group#0xxx retry procedure of Copyback processing

Copyback to the replaced drive is retried.xxx: RAID group number (hexadecimal)

M A4130xxx 7 A4130xxx RAID Group#0xxx start failure of Redundant Copy processing These messages are notified when "Redundant" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

Redundant copy has not started.xxx: RAID group number (hexadecimal)

M A4430xxx 7 A4430xxx RAID Group#0xxx start procedure of Redundant Copy processing

Redundant copy is being performed.xxx: RAID group number (hexadecimal)

M A4A30xxx 7 A4A30xxx RAID Group#0xxx abnormal end of Redundant Copy processing because of source disk problem

Redundant copy to the replaced drive is halted because an error is found in the copy source drive.


M A4B30xxx 7 A4B30xxx RAID Group#0xxx abnormal end of Redundant Copy processing

Redundant copy is halted.xxx: RAID group number (hexadecimal)

M A4C30xxx 7 A4C30xxx RAID Group#0xxx retry procedure of Redundant Copy processing

Redundant copy is retried.xxx: RAID group number (hexadecimal)

M E0050nxx 7 E0050xxx WRITE BAD DATA This message is notified when "Bad data" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

Writing of Bad Data (data lost identifier) occurs.xxx: RAID group number (hexadecimal)

M E10300xx 7 E10300xx PINNED DATA was created CM#m-CPU#v This message is notified when "Pinned data" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

The pinned data occurs.xx: CM module ID (10 – 11) in which the pinned data occurredm: CM number (0 – 1) in which the pinned data occurredv: CPU number in CM

Event type code


RemarksTrapNo.

TrapMaintenance




129


M E1FF00xx 7 E1FF00xx PINNED DATA was cleared CM#m-CPU#v This message is notified when "Pinned data" is enabled for Error Severity Level in the event notification setting. Although this message is notified as an error message, no further action is required because this message simply means that pinned data has been cleared (normal).This is not notified during maintenance operations.

The pinned data was cleared.xx: CM module ID (10– 11) from which the pinned data was clearedm: CM number (0 – 1) from which the pinned data was clearedv: CPU number in CM

M E2070001 7 E2070001 NOT READY(01:Configuration Error) These messages are notified when "Not ready" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

The device is in Not Ready status.Shipment settings (model setting) and configurations are not applied.

M E2070002 7 E2070002 NOT READY(02:CM F/W Version Error)

The device is in Not Ready status.Firmware version for the CM is not correct.

M E2070004 7 E2070004 NOT READY(04:Restore Fail)

The device is in Not Ready status.Backup is successfully complete, but the restoration cannot be performed.

M E207000B 7 E207000B NOT READY(11:Power Off/Fail Incomplete)

The device is in Not Ready status.Failed to power off. Or the device power turns off immediately after the device powers on.

M E207000C 7 E207000C NOT READY(12:Backup Fail)

The device is in Not Ready status.Backup failed.

M E207000D 7 E207000D NOT READY(13:Multi CM Down)

The device is in Not Ready status.Adjoining CMs with LUs are degraded.

M E207000E 7 E207000E NOT READY(14:Machine Down Recovery End)

The device is in Not Ready status.Machine down recovery is performed.

M E207000F 7 E207000F NOT READY(15:Machine Down Recovery Failed)

The device is in Not Ready status.Failed to perform machine down recovery.

M E2070010 7 E2070010 NOT READY(16:DE Build Error)

The device is in Not Ready status.Failed to configure DE because of QSFP cable errors or FC cable errors.

Event type code


RemarksTrapNo.

TrapMaintenance




130


M E2070011 7 E2070011 NOT READY(17:CM Memory Shortage) These messages are notified when "Not ready" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

The device is in Not Ready status.Memory capacities are smaller than the minimum value in multiple CMs.

M E2070015 7 E2070015 NOT READY(21:Auto CFD)

The device is in Not Ready status.Automatic CFD is performed.

M E2070016 7 E2070016 NOT READY(22:No Version)

The device is in Not Ready status.The version table is invalid.

M E2070017 7 E2070017 NOT READY(23:AC Input Shortage)

The device is in Not Ready status.AC power input is insufficient.

M E2070018 7 E2070018 NOT READY(24:Configuration Data restored from System Disk)

The device is in Not Ready status.Configuration information is restored using the backup area due to the replacement of a CM (including BUD).

M E2070019 7 E2070019 NOT READY(25:BUD Capacity Shortage)

The device is in Not Ready status.BUD capacity is insufficient.

M E207001A 7 E207001A NOT READY(26:TPV Table Restore Fail from System Area)

The device is in Not Ready status.TPV table cannot be restored from the system area.

M E207001B 7 E207001B NOT READY(27:TPV Table Restore Fail to BUD)

The device is in Not Ready status.TPV table cannot be restored to BUD.

M E8010xxx 7 E8010xxx TPP#xxx turned to CAUTION(decrease of available capacity) These messages are notified when "Thin Provisioning Pool Rate" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

Usage status of the Thin Provisioning Pool is changed:Normal to Caution

xxx: TPP number (hexadecimal)

M E8020xxx 7 E8020xxx TPP#xxx turned to WARNING(decrease of available capacity)

Usage status of the Thin Provisioning Pool is changed:Normal to Warning or Caution to Warning


M E8050xxx 7 E8050xxx TPP#xxx was all allocated

There is no more available capacity in the Thin Provisioning Pool.


M E8070xxx 7 E8070xxx FTRP#xxx turned to CAUTION(decrease of available capacity)

Usage status of the Flexible Tier Pool is changed:Normal to Attention

xxx: FTRP number (hexadecimal)

M E8080xxx 7 E8080xxx FTRP#xxx turned to WARNING(decrease of available capacity)

Usage status of the Flexible Tier Pool is changed:Normal to Warning or Attention to Warning

xxx: FTRP number (hexadecimal)

Event type code


RemarksTrapNo.

TrapMaintenance




131


M E8090xxx 7 E8090xxx FTRP#xxx was all allocated These messages are notified when "Thin Provisioning Pool Rate" is enabled for Error Severity Level in the event notification setting. They are not notified during maintenance operations.

There is no more available capacity in the Flexible Tier Pool.xxx: FTRP number (hexadecimal)

M E928xxyy 7 E928xxyy Key Management Server communication Error (Key Server ID #xx)(Key Group ID#yy)

This message is notified when "SED Network Error" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

A communication error with the key server occurred.xx: Key server IDyy: Key group ID

Event type code


RemarksTrapNo.

TrapMaintenance




132


A.2.3 Warning Messages

This section describes the messages that are sent when the severity is Warning.

■ Warning message list

The following messages are sent when components require maintenance or preventive maintenance, whenthe battery reaches its expiration date, for unusual temperatures, and for other warning events.

Event type code

SNMP Trap Upper: MessageRemarksTrap

No.TrapItemID (*1) Lower: Description

J 01SSMM00 5 0100MM00 0xww Controller Module#m(zz) Warning factor(ww) <pppppppppppp ssssssssss rrrrr>

These messages are notified when "Parts Warning" is enabled for Warning Level in the event notification setting. They are not notified during maintenance operations.

CM error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)ww: Factor codepp...: Component numberss...: Serial numberrr...: Version

J 02SSMM0p 5 0200MM0p 0 Controller Module#m(zz) DMA PORT#p Warning <pppppppppppp ssssssssss rrrrr>

CM DMA port error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)p: Port number (0)pp...: Component numberss...: Serial numberrr...: Version

J 03SSMM0v 5 0300MM0v 0 Controller Module#m(zz) BIOS#v Warning <pppppppppppp ssssssssss rrrrr>

CM BIOS error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: BIOS number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 04SSMM00 5 0400MM00 0 Controller Module#m(zz) RTC Warning <pppppppppppp ssssssssss rrrrr>

CM RTC error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version



133


J 05SSMM00 5 0500MM00 0 Controller Module#m(zz) NVRAM Warning <pppppppppppp ssssssssss rrrrr>


CM NVRAM error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 06SSMM0v 5 0600MM0v 0 Controller Module#m(zz) EXP#v Warning <pppppppppppp ssssssssss rrrrr>

CM EXP error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: EXP number (0)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 08SSMMvp 5 0800MMvp 0 Controller Module#m(zz) DI Port#P Warning <pppppppppppp ssssssssss rrrrr>

CM DI port error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: Device number (0)p: Device port number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J 09SSMMvp 5 0900MMvp 0 Controller Module#m(zz) EXP#v In Port#p Warning <pppppppppppp ssssssssss rrrrr>

CM EXP IN port error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: EXP number (0)p: Port number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

Event type code





134


J 0ASSMMvp 5 0A00MMvp 0 Controller Module#m(zz) EXP#v Out Port#p Warning <pppppppppppp ssssssssss rrrrr>


CM EXP OUT port error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: EXP number (0)p: Port number (0)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 0CSSMM0v 5 0C00MM0v 0 Controller Module#m(zz) BUD#v(#xxGB) Warning <pppppppppppp ssssssssss rrrrr>

CM BUD error is detected.SS: Component subtypeMM: CM module ID (10 – 11)v: BUD number (0 – 1)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)xx: Capacity of BUD (2)pp...: Component numberss...: Serial numberrr...: Version

J 0ESSMM00 5 0E00MM00 0 Controller Module#m(zz) NAND Controller Warning <pppppppppppp ssssssssss rrrrr>

CM NAND Controller error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 0FSSMM00 5 0F00MM00 0 Controller Module#m(zz) SCU Warning <pppppppppppp ssssssssss rrrrr>

CM SCU error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 10SSMM00 5 1000MM00 0 CA Slot#S-V(zz) (on CM#m) Warning <pppppppppppp ssssssssss rrrrr>

CA error is detected.SS: Component subtypeMM: CA module ID (40 – 7F)S: CA slot number (0 – 1)V: Device number (0 – 1)zz: CA typem: CM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

Event type code





135


J 11SSMM0p 5 1100MM0p 0 CA Slot#S-V(zz) (on CM#m) Port#P Warning <pppppppppppp ssssssssss rrrrr>


CA port error is detected.SS: Component subtypeMM: CA module ID (40 – 7F)p: Device port number (0 – 1)S: CA slot number (0 – 1)V: Device number (0 – 1)zz: CA typem: CM number (0 – 1)P: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J 21SSMM00 5 2100MM00 0 Controller Module#m(zz) FPGA Warning <pppppppppppp ssssssssss rrrrr>

CA FPGA error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

J 22SSMM0p 5 2200MM0p 0 Controller Module#m(zz) LAN PORT#p Warning <pppppppppppp ssssssssss rrrrr>

CM LAN port error is detected.SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J 7A000000 6 7A000000 1 CE Exhaust temperature Warning These messages are notified when "Tem-perature Warning" is enabled for Warning Level in the event notification setting. They are not notified during maintenance operations.

CE exhaust temperature error (Warning) is detected.

J 7B000000 6 7B000000 1 CE Intake temperature Warning

CE intake temperature error (Warning) is detected.

Event type code





136


J 80SSuu0N 5 8000uu0N 0 HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) SMART <pppppppppppp ssssssssssss rrrr tttttt qq>

These messages are notified when "Disk Warning" is enabled for Warning Level in the event notification setting. They are not notified during maintenance operations.

SMART is reported from the HDD.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 80SSuu0N 5 8000uu0N 0 HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) Warning <pppppppppppp ssssssssssss rrrr tttttt qq>

HDD error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 80SSuu0N 5 8000uu0N 0 HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) WarnSlow <pppppppppppp ssssssssssss rrrr tttttt uu>

SMART occurs because of disk performance error in the HDD.

SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

Event type code





137


J 80SSuu0N 5 8000uu0N 0 HDD 3.5 DE#uu-Disk#n(SAS xxxGB yykrpm ccccccc) SlowDown <pppppppppppp ssssssssssss rrrr tttttt qq>


Disk performance error in the HDD is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Disk slot number (0 – b (hexadecimal))n: Disk slot number (0 – 11 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 81SSuuNN 5 8000uuNN 0 HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) SMART <pppppppppppp ssssssssssss rrrr tttttt qq>

SMART is reported from the HDD.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 81SSuuNN 5 8000uuNN 0 HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) Warning <pppppppppppp ssssssssssss rrrr tttttt qq>

HDD error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

Event type code





138


J 81SSuuNN 5 8000uuNN 0 HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) WarnSlow <pppppppppppp ssssssssssss rrrr tttttt qq>


SMART occurs because of disk performance error in the HDD.

SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 81SSuuNN 5 8000uuNN 0 HDD 2.5 DE#uu-Disk#nn(SAS xxxGB yykrpm ccccccc) SlowDown <pppppppppppp ssssssssssss rrrr tttttt qq>

Disk performance error in the HDD is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Disk slot number (0 – 17 (hexadecimal))nn: Disk slot number (0 – 23 (decimal))xxx: Disk capacity (GB/TB)yy: Disk speedcc...: Disk information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 84SSuu0N 5 8000uu0N 0 SSD 3.5 DE#uu-Disk#n(SAS xxxGB ccccccc) SMART <pppppppppppp ssssssssssss rrrr tttttt qq>

SMART is reported from the SSD.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Drive slot number (0 – b (hexadecimal))n: Drive slot number (0 – 11 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

Event type code





139


J 84SSuu0N 5 8000uu0N 0 SSD 3.5 DE#uu-Disk#n(SAS xxxGB ccccccc) Warning <pppppppppppp ssssssssssss rrrr tttttt qq>


SSD error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)N: Drive slot number (0 – b (hexadecimal))n: Drive slot number (0 – 11 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 85SSuuNN 5 8000uuNN 0 SSD 2.5 DE#uu-Disk#nn(SAS xxxGB ccccccc) SMART <pppppppppppp ssssssssssss rrrr tttttt qq>

SMART is reported from the SSD.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Drive slot number (0 – 17 (hexadecimal))nn: Drive slot number (0 – 23 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

J 85SSuuNN 5 8000uuNN 0 SSD 2.5 DE#uu-Disk#nn(SAS xxxGB ccccccc) Warning <pppppppppppp ssssssssssss rrrr tttttt qq>

SSD error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)NN: Drive slot number (0 – 17 (hexadecimal))nn: Drive slot number (0 – 23 (decimal))xxx: Drive capacity (GB/TB)cc...: Drive information (RAID level or hot spare (Spare))pp...: Component numberss...: Serial numberrr...: Versiontt...: Data codeqq: Configuration code

Event type code





140


J 90SSuu0n 5 9000uu0n 0 IOM6 DE#uu/IOM#n Warning <pppppppppppp ssssssssss rrrrr>


DE IOM error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: IOM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J 91SSuunp 5 9100uunp 0 IOM6 Port DE#uu/IOM#n/Port#p Warning <pppppppppppp ssssssssss rrrrr>

DE port error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)p: Port number (0 – 1)n: IOM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J 9ASSuunp 5 9100uunp 0 IOM6 QSFP DE#uu/IOM#v/Port#p Warning <pppppppppppp ssssssssss rrrrr>

DE QSFP port error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)v: IOM number (0 – 1)p: Port number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J C1MM0000(When MM is 10 or 11)

5 0100MM00 0 Controller Module#m(zz) Reboot <pppppppppppp ssssssssss rrrrr>

CM is rebooted.MM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)pp...: Component numberss...: Serial numberrr...: Version

Event type code





141


*1: This row indicates TrapWarningInfo for Trap No. 5 and TrapSensorInfo for Trap No. 6.

J C1MM0000(When MM is 40 – 7F)

5 0100MM00 0 CA Slot#S-V(zz) (on CM#m) Reboot <pppppppppppp ssssssssss rrrrr>


CA is rebooted.MM: CA module ID (40 – 7F)S: CA slot number (0 – 1)V: Device number (0 – 1)zz: CA typem: CM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J C190uu0n 5 9000uu0n 0 IOM6 DE#uu/IOM#n Reboot <pppppppppppp ssssssssss rrrrr>

IOM is rebooted.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: IOM number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J C3SSMM00 5 0B00MMnn 0 Controller Module#m(zz) Cache(MEM #xGB) Slot#nn Correctable Error <pppppppppppppppppp ssssssssssss rrrrrr>

Many correctable errors occurred in the CM memory.

SS: Component subtypeMM: CM module ID (10 – 11)m: CM number (0 – 1)zz: Model name (DX80S2 or DX90S2)x: Capacity of the cache memory (2 or 4)nn: Slot number of the cache memory (0 – 5)pp...: Component numberss...: Serial numberrr...: Version

J D2SSuu0n 5 D200uu0n 0 Power Supply Unit DE#uu/PSU#n Warning <pppppppppppp ssssssssss rrrr>

PSU error is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)n: PSU number (0 – 1)pp...: Component numberss...: Serial numberrr...: Version

J DASSuu00 6 DA00uu00 1 DE Exhaust temperature DE#uu Warning These messages are notified when "Tem-perature Warning" is enabled for Warning Level in the event notification setting. They are not notified during maintenance operations.

DE exhaust temperature error (Warning) is detected.


J DBSSuu00 6 DB00uu00 1 DE Intake temperature DE#uu Warning

DE intake temperature error (Warning) is detected.SS: Component subtypeuu: DE-ID ("00" for a controller enclosure)

Event type code





142


A.2.4 Informational Messages

This section describes the messages that are sent when the severity is Info.

■ Informational message list

● When the event type is "I"

The following messages are sent when an information-level event occurs:

Event type code

SNMP TrapUpper: Message

RemarksMiddle: Detail information

Trap No.

TrapItemIdTrapLink

StatusInfoLower: Description

I 00000011 9 – – The usage rate of SDP(normal) exceeded the threshold (Level1) value $a% and currently is at $b%.

These messages are notified when "SDP Usage Rate Over Lv1" is enabled for Informational Level in the event notification setting.

Detail information is not displayed.

Snap Data Pool (unencrypted) usage rate exceeds the threshold (Level1) $a% and reaches $b%.

$a: Threshold of Snap Data Pool$b: Usage rate of Snap Data Pool

I 00000011 9 – – The usage rate of SDP(encryption) exceeded the threshold (Level1) value $a% and currently is at $b%.


Snap Data Pool (encrypted) usage rate exceeds the threshold (Level1) $a% and reaches $b%.













143











I 00000014 9 – – The usage rate of copy table exceeded the threshold value $a and currently is at $b.

This message is notified when "Copy Table Size Usage Rate Over" is enabled for Informational Level in the event notification setting.


Usage rate of the copy table exceeds the threshold $a% and reaches $b%.

$a: Threshold of copy table$b: Usage rate of copy table

I 00000015 9 – – The trial license(Local Copy) will expire on YYYY-MM-DD.

These messages are notified when "Trial copy license expired" is enabled for Informational Level in the event notification setting.


The trial license (local copy) expires on YYYY-MM-DD.

I 00000015 9 – – The trial license(Remote Copy) will expire on YYYY-MM-DD.


The trial license (remote copy) expires on YYYY-MM-DD.

I 00000016 9 – – The trial license(Local Copy) has expired.


The trial license (local copy) has expired

I 00000016 9 – – The trial license(Remote Copy) has expired.


The trial license (remote copy) has expired.

I 00000018 9 – – No free space on Offloaded Data Transfer(ODX) Buffer Volume (Volume No.xxx)

This message is notified when "No Free Space on ODX Buffer Volume" is enabled for Informational Level in the event notification setting.


No free space in the ODX Buffer volume.xxx: ODX Buffer volume No.

Event type code



Trap No.

TrapItemIdTrapLink




144


I 01000010 9 – – User &a Logged in from &b (&c) These messages are notified when "User login/logout" is enabled for Informational Level in the event notification setting.


Logged in to the storage system.&a: User name&b: IP address&c: GUI or CLI

I 01000020 9 – – User &a Logged out from &b (&c)


Logged out from the storage system.&a: User name&b: IP address&c: GUI or CLI

I 01010010 9 – – %d RAID group(s) created These messages are notified when "Operated RAID Group" is enabled for Informational Level in the event notification setting.

No=&a Name=&b Level=&c CM=&d Capacity=&e Disk_Count=&f

%d RAID groups are registered.%d: Quantity&a: RAID group number&b: RAID group name&c: RAID level&d: Assigned CM&e: Capacity&f: Number of drives

I 01010020 9 – – %d RAID group(s) deleted

No=&a Name=&b

%d RAID groups are deleted.%d: Quantity&a: RAID group number&b: RAID group name

I 01020010 9 – – %d hot spare(s) assigned These messages are notified when "Added/Released Hot Spare" is enabled for Informational Level in the event notification setting.

Enclosure=&a Slot=&b Type=&c RAID_Group_No=&d RAID_Group_Name=&e

%d hot spares are registered.%d: Quantity&a: DE-ID ("00" for a controller enclosure)&b: Slot number&c: Type (Global or Dedicated)&d: RAID group number (only for Dedicated Hot Spares)&e: RAID group name (only for Dedicated Hot Spares)

Event type code



Trap No.

TrapItemIdTrapLink




145


I 01020020 9 – – %d hot spare(s) released These messages are notified when "Added/Released Hot Spare" is enabled for Informational Level in the event notification setting.

Enclosure=&a Slot=&b Type=&c RAID_Group_No=&d RAID_Group_Name=&e

%d hot spares are deleted.%d: Quantity&a: DE-ID ("00" for a controller enclosure)&b: Slot number&c: Type (Global or Dedicated)&d: RAID group number (only for Dedicated Hot Spares)&e: RAID group name (only for Dedicated Hot Spares)

I 01030010 9 – – %d volume(s) created These messages are notified when "Operated Volume" is enabled for Informational Level in the event notification setting.

• For Standard volumes, SDVs, or SDPVsNo=&a Name=&b Type=&c Capacity=&d RAID_Group_No=&e RAID_Group_Name=&f

• For TPVsNo=&a Name=&b Type=&c Capacity=&d Pool_No=&g Pool_Name=&h

%d volumes are created.%d: Quantity&a: Volume number&b: Volume name&c: Volume type&d: Capacity&e: RAID group number (only for Standard/Open volume, SDV, or SDPV)&f: RAID group name (only for Standard/Open volume, SDV, or SDPV)&g: TPP number (only for Standard/Open volume or TPV)&h: TPP name (only for Standard/Open volume or TPV)

I 01030020 9 – – %d volume(s) deleted

No=&a Name=&b

%d volumes are deleted.This message is not notified when the deletion reservation function is used to delete the SDPV.

%d: Quantity&a: Volume number&b: Volume name

I 01050010 9 – – Power on completed ($a) These messages are notified when "Power off/on Apply Firmware" is enabled for Informational Level in the event notification setting.


The device status is changed to Ready.$a: VxxLxx-xxxx (Firmware version)

I 01050020 9 – – Shutdown started


Device shutdown has started.

I 01050030 9 – – Controller firmware updated ($a)


Controller firmware version is updated.$a: VxxLxx-xxxx (Firmware version)

Event type code



Trap No.

TrapItemIdTrapLink




146


I 0200XXYY 9 – – Key Management Server communication Error was cleared (Key Server ID #xx)(Key Group ID#yy)

This message is notified when "SED Network Error Recovered" is enabled for Informational Level in the event notification setting.


The communication error with the key server is resolved.

xx: Key server IDyy: Key group ID

I 03000001 10 1100MM0p 1 (LinkUp)2 (Linkdown)

The status of Link became $a in CM#$b CA#$c Port#$d.

This message is notified when "FC CA Port Link Status Changed" is enabled for Informational Level in the event notification setting.


The link status of the CA port changed to $a.MM: CA module ID (40 – 7F)p: Device port number (0 – 1)$a: Link status (LinkUp or LinkDown)$b: CM number (0 – 1)$c: CA number (0 – 1)$d: Port number (0 – 1)

I 03000002 9 – – The number of login host exceed the acceptable login count in CM#$b CA#$c Port#$d.

This message is notified when "Host Login Over" is enabled for Informational Level in the event notification setting.


The number of hosts that are connected to the CA port exceeds the maximum.

$b: CM number (0 – 1)$c: CA number (0 – 1)$d: Port number (0 – 1)

Event type code



Trap No.

TrapItemIdTrapLink




147


● When the event type is "R"

The following messages are sent when a normal state is restored for Error or Warning level events.

• Meaning of symbols

• Message list

*1: This row indicates TrapWarningInfo for Trap No. 25 and TrapSensorInfo for Trap No. 26.

Symbol Meaning

SS Component subtype

MM CM module ID (10 – 11)

m CM number (0 – 1)

zz Model name (DX80S2 or DX90S2)

pp... Component number

ss... Serial number

rr... Version

e EXP number (0)

i IOM number (0 – 1)

d PSU number (0 – 1)

uu DE-ID ("00" for a controller enclosure)

Event type code



R 01SSMM00 25 0100MM00 0 Controller Module#m(zz) Normal <pppppppppppp ssssssssss rrrrr>

These messages are notified when "Recov-ery module" is enabled for Informa-tional Level in the event notification setting.

Normal status is restored for a CM error.

R 06SSMM0v 25 0600MM0v 0 Controller Module#m(zz) EXP#e Normal <pppppppppppp ssssssssss rrrrr>

Normal status is restored for a CM EXP error.

R 90SSuu0n 25 9000uu0n 0 IOM6 DE#uu/IOM#i Normal <pppppppppppp ssssssssss rrrrr>

Normal status is restored for a DE IOM error.

R D2SSuu0n 22 D200uu0n - Power Supply Unit DE#uu/PSU#d Normal <pppppppppppp ssssssssss rrrrr>

Normal status is restored for a PSU error.

R DASSuu00 26 DA00uu00 0 DE Exhaust temperature DE#uu Normal These messages are notified when "Tem-perature restoration" is enabled for Infor-mational Level in the event notification setting.

Normal status is restored for an exhaust temperature error in CE or DE.

R DBSSuu00 26 DB00uu00 0 DE Intake temperature DE#uu Normal

Normal status is restored for an intake temperature error in CE or DE.



148


A.2.5 Test Messages

The messages that are sent when the test notification of an event is performed in ETERNUS Web GUI orETERNUS CLI are described below.

■ Test mail transmission

The message is notified when the test notification of e-mail is performed in ETERNUS Web GUI or ETERNUS CLI.

■ Test Trap transmission

The message is notified when the test notification of the SNMP Trap is performed in ETERNUS Web GUI orETERNUS CLI.

A.2.6 Sense Codes

This section describes the sense codes that are notified to the server.

Event type code Message

T FFFFFFFF Test e-mail Message

Trap No. TrapItemId TrapMessage

2 0x80000000 SNMP Trap Test

The Trap No. and ItemId in the test Trap are the same as the notification that is sent when a drive in Slot#0 in CE is in Fault status. A drive is not actually disconnected when a test Trap is notified.

Sense codeDescription Remarks

SK ASC ASCQ

02 04 00 The device is in Not Ready status. This sense code is notified when "Not ready" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.



149


04 F1 01 CM is disconnected. These sense codes are notified when "Parts Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

04 F1 0B CM memory is disconnected.

04 F1 0C CM BUD is disconnected.

04 F1 0D CM FAN is disconnected.

04 F1 10 CA is disconnected.

04 F1 11 CA Port is disconnected.

04 F1 17 CA SFP+ is disconnected.

04 F1 19 CA SFP+ is disconnected.

04 F1 1A CA SFP is disconnected.

04 F1 1C CA SFP+ is disconnected.

04 F1 1D CA SFP+ is disconnected.

04 F1 1E Copper CA SFP+ is disconnected.

04 F1 1F CA SFP is disconnected due to an SFP type that cannot be recognized.

04 F1 2A CM QSFP is disconnected.

04 F1 80 3.5" HDD is disconnected. These sense codes are notified when "Disk Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

04 F1 81 2.5" HDD is disconnected.

04 F1 84 3.5" SSD is disconnected.

04 F1 85 2.5" SSD is disconnected.

04 F1 88 Drive is disconnected because an error occurred during the Write check of the disk patrol.

04 F1 90 IOM is disconnected. These sense codes are notified when "Parts Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

04 F1 91 IOM Port is disconnected.

04 F1 9A IOM QSFP is disconnected.

04 F1 D2 DPSU is disconnected.

04 F1 DA CE or DE exhaust temperature error is detected. This sense code is notified when "Temperature Error" or "Parts Error" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

04 F1 DB CE or DE intake temperature error (sensor failure) is detected.

These sense codes are notified when "Parts Error" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

04 F2 02 CM DMA Port is disconnected.

04 F2 03 CM BIOS is disconnected.

04 F2 04 CM RTC is disconnected.

04 F2 05 CM NVRAM is disconnected.

04 F2 06 CM EXP is disconnected.

04 F2 08 CM DI Port is disconnected.

04 F2 09 CM EXP IN port is disconnected.

04 F2 0A CM EXP Out port is disconnected.

04 F2 0E CM NAND Controller is disconnected.

04 F2 0F CM SCU is disconnected.

04 F2 11 CA port is disconnected.

04 F2 21 CM FPGA is disconnected.

04 F2 22 CM LAN Port is disconnected.


SK ASC ASCQ



150


04 F8 00 The pinned data occurs. This sense code is notified when "Pinned data" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 11 90 Writing of Bad Data (data lost identifier) occurs. This sense code is notified when "Bad data" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 C1 01 CM is rebooted. These messages are notified when "Remote Path Error" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 C1 10 CA is rebooted.

06 C1 90 IOM is rebooted.

06 E2 92 Disconnection of a REC path between cabinets is detected. This sense code is notified when "Remote Path Error" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 80 Rebuild has started. This sense code is notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 80 Redundant copy is being performed. This sense code is notified when "Redundant" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

06 F2 81 Rebuild to the drive has started. These sense codes are notified when "Rebuild/Copyback w/ redundant" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

06 F2 82 Rebuild to the hot spare is complete.

06 F2 82 Redundant copy is complete. This sense code is notified when "Complete Redundant Copy" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 83 Rebuild to the drive is complete. These sense codes are notified when "Rebuild/Copyback w/ redundant" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.

06 F2 84 Copyback is being performed.

06 F2 85 Copyback is complete.

06 F2 88 Rebuild to the hot spare or the replaced drive is complete, but Bad Data (data lost identifier) exists.

These sense codes are notified when "Complete rebuild" is enabled for Error Severity Level in the event notification setting.They are not notified during maintenance operations.


SK ASC ASCQ



151


06 F2 89 Rebuild has not started. This sense code is notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 89 Redundant copy has not started. This sense code is notified when "Redundant" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

06 F2 8A Rebuild is halted. This sense code is notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 8A Redundant copy is halted. This sense code is notified when "Redundant" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

06 F2 8B Rebuild is halted. This sense code is notified when "Rebuild/Copyback w/o redundant" is enabled for Error Severity Level in the event notification setting.This is not notified during maintenance operations.

06 F2 8C Copyback is halted.

06 F2 8D Copyback is halted because an error is found in the copy source drive.

06 F2 8D Redundant copy is halted because an error is found in the copy source drive.

This sense code is notified when "Redundant" is enabled for Error Severity Level in the event notification setting. This is not notified during maintenance operations.

06 FB 01 CM error is detected. These messages are notified when "Parts Warning" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 FB 02 CM DMA port error is detected.

06 FB 03 CM BIOS error is detected.

06 FB 04 CM RTC error is detected.

06 FB 05 CM NVRAM error is detected.

06 FB 06 CM EXP error is detected.

06 FB 08 CM DI port error is detected.

06 FB 09 CM EXP IN port error is detected.

06 FB 0A CM EXP OUT port error is detected.

06 FB 0B Many correctable errors occurred in the CM memory.

06 FB 0C CM BUD error is detected.

06 FB 0D CM FAN error is detected.

06 FB 0E CM NAND Controller error is detected.

06 FB 0F CM SCU error is detected.

06 FB 10 CA error is detected.

06 FB 11 CA port error is detected.

06 FB 21 CM FPGA error is detected.

06 FB 22 CM LAN port error is detected.


SK ASC ASCQ



152


06 FB 7A CE exhaust temperature error is detected. These messages are notified when "Temperature Warning" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 FB 7B CE intake temperature error is detected.

06 FB 80 SMART is reported from the 3.5" HDD. These messages are notified when "Disk Warning" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 FB 81 SMART is reported from the 2.5" HDD.

06 FB 84 SMART is reported from the 3.5" SSD.

06 FB 85 SMART is reported from the 2.5" SSD.

06 FB 90 DE IOM error is detected. These messages are notified when "Parts Warning" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 FB 91 DE port error is detected.

06 FB 9A DE QSFP port error is detected.

06 FB D2 PSU error is detected.

06 FB DA DE exhaust temperature error is detected. These messages are notified when "Temperature Warning" is enabled for Warning Level in the event notification setting.They are not notified during maintenance operations.

06 FB DB DE intake temperature error is detected.


SK ASC ASCQ



153

Appendix B

Audit Log List

This appendix describes the audit logs that are notified to a syslog server when this function is enabled in theaudit log settings of ETERNUS Web GUI or ETERNUS CLI.

■ Audit Log Format

The following formats are available for audit log: "RFC3164" and "RFC5424". The notification format isspecified in ETERNUS Web GUI or ETERNUS CLI.

This section describes examples of audit logs and the details of formats that are output.

● Output example of an audit log


- "RFC3164" format

- "RFC5424" format

● Description of each audit log item


1 Priority Priority of the message is output in the following format:<Priority>

Priority value indicates the facility and severity of the message.The Priority value is calculated by "Facility value × 8 + Severity value".

• Facility value for messages is always "13".

• Severity value for messages is always "6"."110" is output as a priority value for an audit log.For the "RFC3164" format, the HEADER part follows the priority part.For the "RFC5424" format, "1" and then a blank follow the priority part.

Create RAID Group., [No=4 Name=RLU#1 Level=RAID1 Disk=0000,0001 CM=cm0cpu0]

1, ETERNUS#1, 0, 123, 02010001, Success, , root, Admin, GUI, 192.168.0.10,

<110>Apr 1 11:26:08 192.168.0.20 Storage: 01, 4, 1, 2012-04-01 11:26:08 +09:00,

20 21

9 10 11 12 13 14 15 16 17 18 19

1 2 3 4 5 6 7 8

2012-04-01 11:26:08 +09:00, 1, ETERNUS#1, 0, 123, 02010001, Success, , root,

<110>1 2012-04-01T11:26:08+09:00 192.168.0.20 Storage 01 4 - 1,

Admin, GUI, 192.168.0.10, Create RAID Group., [No=4 Name=RLU#1 Level=RAID1

Disk=0000,0001 CM=cm0cpu0]

20 211917 18

21

98 10 11 12 13 14 15 16

1 2 3 4 5 6 7



154

Appendix B Audit Log List

2 Time stamp The local time when the event is detected is output in the following format:

• For RFC3164Mmm dd hh:mm:ss

- MmmAbbreviation of each month (Jan - Dec)

- ddDate. If the date is a single digit, a blank is output before the date number.


• For RFC5424yyyy-mm-ddThh:mm:ss±hh:mm



- ddThe date is displayed with two digits (01 – 31). "T" follows this item.


- ±hh:mmTime differences between the local time and the GMT. The value for the time zone specified in the date and time setting of ETERNUS Web GUI or ETERNUS CLI is displayed. "hh" indicates the hour (00 – 23) and "mm" indicates minutes (00 – 59). A blank follows this item.

3 Host name The IP address of the sender port (MNT or RMT) for the ETERNUS DX Disk storage system is output in IPv4 or IPv6 format:



A blank follows this item.

4 Program or process The name of the program or process that generates the message is output."Storage" is output for all the messages. For the "RFC3164" format, a colon [:] and then a blank, which indicate the end of the TAG field, follow this item.For the "RFC5424" format, a blank follows this item.

5 CM No. and message type

The CM number of the controller that outputs the message and the message type are output."0" or "1" is output according to the message for the CM No. "1" is output for the message type.For the "RFC3164" format, a comma, and then a blank follow this item.For the "RFC5424" format, a blank follows this item.

6 Message serial number

The message serial number is displayed for each controller.For the "RFC3164" format, a comma and then a blank follow this item.For the "RFC5424" format, a blank, a hyphen, and a blank follow this item in this order.




155


7 Format version Format version of the audit log is displayed."1" is output for all the messages.A comma, and then a blank follow this item.

8 Time stamp The local time when the processing result for the target event is defined is output.A comma, and then a blank follow this item.

yyyy-mm-dd hh:mm:ss ±hh:mm



- ddThe date is displayed with two digits (01 – 31). "T" and a blank follow this item.


- ±hh:mmTime differences between the local time and the GMT. The value for the time zone specified in the date and time setting of ETERNUS Web GUI or ETERNUS CLI is displayed. "hh" indicates the hour (00 – 23) and "mm" indicates minutes (00 – 59).

9 Processing time The time (seconds) it takes between starting the process for the target event and obtaining the result is output."0" is output if this process takes less than 1 second. If this process takes 1 second or longer, the value (seconds) is rounded off to the nearest whole number.A comma, and then a blank follow this item.

10 Storage system name

A friendly name for the ETERNUS DX Disk storage system is output.If a friendly name is not specified, no values are displayed.A comma, and then a blank follow this item.

11 CM No. The CM number of the controller that detects the event is output.A comma, and then a blank follow this item.

12 Sequence number The message serial number is displayed for each controller.A comma, and then a blank follow this item.

13 Audit event code The event code is displayed as the 8-digit hexadecimal number.A comma, and then a blank follow this item.Refer to "Message List" (page 157) for details.

14 Audit event result The processing result for the event is output.Detection: The processing result is detected.Success: The process is succeeded.Error: The process is failed.

A comma, and then a blank follow this item.

15 Event result code The event result factor code is output as the 8-digit hexadecimal number.If the audit log result is "Success", no values are output.When the event result is "Detection" or "Error", the error code of the interface which performed the target event process is output.

For ETERNUS Web GUI: Error code for the ETERNUS Web GUIETERNUS CLI or Storage Foundation Software ETERNUS SF: Error code for the ETERNUS CLI

A comma, and then a blank follow this item.

16 User name The user name of the account which performed the target event process is output. If the user which performed the target event cannot be specified, no values are output.A comma, and then a blank follow this item.




156


■ Message List

The table below shows the audit event code, audit event details, and output message for detailed audit loginformation that are described in "Audit Log Format" (page 154).

17 Role The user role is output.If the user which performed the target event cannot be specified, no values are output.A comma, and then a blank follow this item.

18 Interface The interface that performed the target event process is output.GUI: ETERNUS Web GUICLI: ETERNUS CLISOFT: Storage Foundation Software ETERNUS SF (including CLI and SLI-S for the Storage Foundation Software ETERNUS SF)

If the interface that performed the target event cannot be specified, no values are output.A comma, and then a blank follow this item.

19 IP address The IP address of the ETERNUS DX Disk storage system that performs the target event process is output in IPv4 or IPv6 format:



If the storage system that performs the target event cannot be specified, no values are output.A comma, and then a blank follow this item.

20 Overview of audit log

A message that indicates the event overview is output.A comma, and then a blank follow this item.Refer to "Message List" (page 157) for details.

21 Detailed information of audit log

The detailed information of the event is displayed in text format and is enclosed by brackets ("[" and "]").If the event result is not "Success" or no detailed information exists for the audit event, no values are output.Refer to "Message List" (page 157) for details.


• Note that some of the detailed information may not be displayed. The detailed information that is displayed depends on the interface that is used and the processing contents.

• When multiple processing targets exist, the related display items are separated by "," (commas), and displayed.

Event codeUpper: Message

DescriptionLower: Detailed information

01010001 Login Logged in to the storage system.


01010002 Logout Logged out from the storage system.




157


01010004 Login failed Login to the storage system is failed.


02010001 Create RAID Group The RAID group is created.$a: RAID group number$b: RAID group name$c: RAID level (RAID0, RAID1, RAID1+0, RAID5, RAID5+0, RAID6)$d: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$e: Assigned CM (0, 1)$f: Stripe Depth (64KB, 128KB, 256KB, 512KB, 1024KB)

[No=$a Name=$b Level=$c Disk=$d CM=$e Stripe_Depth=$f]

02010002 Set RAID Group The RAID group settings are changed.$a: RAID group number$b: RAID group name$c: Assigned CM (0, 1)$d: Key Group (Enable, Disable)

[No=$a Name=$b CM=$c Key_Group=$d]

02010003 Delete RAID Group The RAID group is deleted.$a: RAID group number[No=$a]

02010004 Expand RAID Group The RAID group capacity is expanded.$a: RAID group number$b: RAID group name$c: RAID level (RAID0, RAID1, RAID1+0, RAID5, RAID5+0, RAID6)$d: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))

[No=$a Name=$b Level=$c Disk=$d]

02010005 Set RAID Tuning The RAID group tuning parameters are set.$a: RAID group number$b: DCMF (1 – 10)$c: Rebuild priority (Low, Middle, High)$d: Tuning parameter setting (Enable, Disable)$e: Throttle [%] (10, 20, 30, 40, 50, 60, 70, 80, 90, 100)$f: Ordered cut (0 – 65535)

[No=$a DCMF=$b Rebuild_Priority=$c Disk_Tuning=$d Throttle=$e Ordered_Cut=$f]

02020001 Set Global Hot Spare The Global Hot Spare is registered.$a: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))

[Disk=$a]

02020002 Release Global Hot Spare The Global Hot Spare is released.$a: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))

[Disk=$a]

02020003 Set Dedicated Hot Spare The Dedicated Hot Spare is registered.$a: RAID group number$b: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))

[No=$a Disk=$b]

02020004 Release Dedicated Hot Spare The Dedicated Hot Spare is released.$a: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))

[Disk=$a]

02030001 Register Thin provisioning License The Thin Provisioning license is registered.






158


02030002 Delete Thin provisioning License The Thin Provisioning license is deleted.


02030003 Create Thin provisioning Pool The Thin Provisioning Pool is created.$a: Pool number$b: Pool name$c: Drive type (Online, Nearline, SSD, SED, Online/Nearline)$d: RAID level (RAID0, RAID1, RAID1+0, RAID5, RAID5+0, RAID6)$e: Encryption by CM (Enable, Disable)$f: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$g: Assigned CM (0, 1)$h: Stripe Depth (64KB, 128KB, 256KB, 512KB, 1024KB)$i: Warning threshold [%] (5 – 99)$j: Attention threshold [%] (5 - 80, None)

[No=$a Name=$b Type=$c Level=$d Encryption=$e [Disk=$f CM=$g Stripe_Depth=$h] Warning=$i Attention=$j]

02030004 Set Thin provisioning Pool The Thin Provisioning Pool settings are changed.$a: Pool number$b: Pool name$c: Warning threshold [%] (5 – 99)$d: Attention threshold [%] (5 - 80, None)

[No=$a Name=$b Warning=$c Attention=$d]

02030005 Delete Thin provisioning Pool The Thin Provisioning Pool is deleted.$a: Pool number[No=$a]

02030006 Expand Thin provisioning Pool The Thin Provisioning Pool capacity is expanded.$a: Pool number$b: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$c: Assigned CM (0, 1)

[No=$a [Disk=$b CM=$c]]

02030007 Format Thin provisioning Pool The Thin Provisioning Pool is formatted.$a: Pool number$b: Mode (All, Unformatted)

[No=$a Mode=$b]

02040001 Set Eco-mode The Eco-mode is set or released.$a: Eco-mode (Enable, Disable)$b: Host I/O monitoring interval (10, 20, 30, 40, 50, 60) $c: Disk motor spin-down limit count (1 – 25)

[Mode=$a Time=$b Limit=$c]

02040002 Create Eco-mode Schedule The Eco-mode schedule is created.$a: Eco-mode schedule number$b: Eco-mode schedule name

[No=$a Name=$b]

02040003 Set Eco-mode Schedule The Eco-mode schedule settings are changed.$a: Eco-mode schedule number$b: Eco-mode schedule name

[No=$a Name=$b]

02040004 Delete Eco-mode Schedule The Eco-mode schedule is deleted.$a: Eco-mode schedule number[No=$a]

02040005 Set RAID Group Eco-mode The Eco-mode schedule is assigned to or released from the RAID group.

$a: RAID group number$b: Eco-mode schedule number$c: Eco-mode action (OFF, ON)

[No=$a Schedule_No=$b Action=$c]





159


02040006 Set Thin provisioning Pool Eco-mode The Eco-mode schedule is assigned to or released from the Thin Provisioning Pool.

$a: Pool number$b: Eco-mode schedule number$c: Eco-mode action (OFF, ON)

[No=$a Schedule_No=$b Action=$c]

02050001 Create Volume The volume is created.$a: Volume number$b: Volume name$c: Volume type (Standard, SDV, SDPV, TPV, FTV, WSV)$d: Capacity [MB] (example: 136704MB)$e: RAID group number$f: Pool number$g: Copy protection (Enable, Disable)$h: Encryption by CM (Enable, Disable)$i: Attention threshold [%] (1 – 200)$j: Allocation priority (FTSP number, Auto)$k: Wide stripe size (Normal, Small)

[No=$a Name=$b Type=$c Capacity=$d RAID_No=$e Pool_No=$fProtection=$g Encryption=$h Attention=$i Priority=$j Wide_Stripe_Size=$k]

02050002 Set Volume The volume settings are changed.$a: Volume number$b: Volume name$c: Copy protection (Enable, Disable)$d: Attention threshold [%] (1 – 200)$e: Allocation priority (FTSP number, Auto)

[No=$a Name=$b Protection=$c Attention=$d Priority=$e]

02050003 Delete Volume The volume is deleted.$a: Volume number[No=$a]

02050004 Format Volume The volume is formatted.$a: Volume number[No=$a]

02050005 Expand Volume The volume capacity is expanded.$a: Volume number that is to be expanded.$b: RAID group number in which the expanded volume belongs.$c: Additional capacity (example: 1000MB)$d: Capacity after expansion (example: 136704MB)

[No=$a RAID_No=$b Expand_Capacity=$c Total_Capacity=$d]

02050006 Start Migration The RAID migration is started.$a: Volume number that is to be migrated$b: Migration destination RAID group number$c: Pool number$d: Volume capacity (example: 136704MB)$e: Encryption by CM (Enable, Disable)$f: Priority (FTSP number, Auto)$g: Zero Reclamation (Enable, Disable)$h: Wide stripe size (Normal, Small)

[No=$a RAID_No=$b Pool_No=$c Capacity=$d Encryption=$e Priority=$f Zero_Reclamation=$g Wide_Stripe_Size=$h]

02050007 Stop Migration The RAID migration is stopped.$a: Migration source volume number[No=$a]

02050008 Start Balancing Thin provisioning Volume The balancing of the Thin Provisioning Volume is started.

$a: Volume number[No=$a]





160


02050009 Stop Balancing Thin provisioning Volume The balancing of the Thin Provisioning Volume is stopped.

$a: Volume number[No=$a]

0205000A Set Cache Parameter The cache parameters are set.$a: Volume number$b: Pool number$c: Force Prefetch Mode (Enable, Disable)$d: Prefetch Limit (0 – 64)$e: Multi Writeback Count (1 – 16)$f: Prefetch Sequential Detect Count (1 – 255)$g: Sequential Dirty Detect Count (1 – 255)$h: Sequential Slope (0 – 4096)$i: Sequential Dirty Slope (0 – 4096)$j: Upper limit of the cache memory capacity (32.5, 65, 130, 260, 520, 1040, 2080, No Limit)

[No=$a POOL_No=$b FP=$c PL=$d MWC=$e PSDC=$f SDDC=$g SS=$h SDS=$i Cache_Limit=$j]

0205000B Create ODX Buffer Volume The ODX Buffer Volume is created.$a: Volume number$b: Volume name$c: Volume type (Standard, TPV, FTV)$d: Capacity [MB] (example: 136704MB)$e: RAID group number$f: Pool number$g: FTRP number$h: Encryption by CM (Enable, Disable)$i: Attention threshold [%] (1 – 200)$j: Priority (FTSP number, Auto)

[No=$a Name=$b Type=$c Capacity=$d RAID_No=$e Pool_No=$f Ftrp_No=$g Encryption=$h Attention=$i Priority=$j]

0205000C Start Zero Reclamation The Zero Reclamation process is started.$a: Volume number[No=$a]

0205000D Stop Zero Reclamation The Zero Reclamation process is stopped.$a: Volume number[No=$a]

0205000E Set Volume Encrypt The encryption setting of the volume is changed.$a: Volume number$b: Encryption by CM (Enable, Disable)

[No=$a Encryption=$b]





161


02060001 Set FC Port Parameter The FC port parameters are set.$a: Port number (example: 001, 002, or "All")$b: Host Affinity (Enable, Disable)$c: Connection type (Loop, Fabric)$d: Transfer rate (1Gb, 2Gb, 4Gb, 8Gb, 16Gb, Auto)$e: Loop ID (0x00-0x7D, Auto)$f: Frame size [Byte] (512, 1024, 2048)$g: Host response name$h: Reset Scope (Initiator, Target)$i: Release Reservation if Chip is Reset (Enable, Disable)$j: Port name$k: Node name$l: REC Line No.(0 – 127)$m: REC Sync transfer mode (Enable, Disable)$n: REC Stack transfer mode (Enable, Disable)$o: REC Consistency transfer mode (Enable, Disable)$p: REC Through transfer mode (Enable, Disable)

[Port=$a Affinity=$b Connect=$c Rate=$d LoopID=$e Frame_Size=$f Host_Response=$g Reset_Scope=$h Reserve_Cancel=$i Port_Name=$j Node_Name=$k REC_Line_No=$l REC_Transfer_Mode_Sync=$m REC_Transfer_Mode_Stack=$n REC_Transfer_Mode_Consistency=$o REC_Transfer_Mode_Through=$p]

02060002 Set SAS Port Parameter The SAS port parameters are set.$a: Port number (example: 001, 002, or "All")$b: Host Affinity (Enable, Disable)$c: Transfer rate (1.5Gb, 3Gb, 6Gb, Auto)$d: Host response name$e: Reset Scope (Initiator, Target)$f: Release Reservation if Chip is Reset (Enable, Disable)

[Port=$a Affinity=$b Rate=$c Host_Response=$d Reset_Scope=$e Reserve_Cancel=$f]





162


02060003 Set iSCSI Port Parameter The iSCSI port parameters are set.$a: Port number (example: 001, 002)$b: Host Affinity (Enable, Disable)$c: iSCSI Name$d: Alias Name$e: Host response name$f: Reset Scope (Initiator, Target)$g: Release Reservation if Chip is Reset (Enable, Disable)$h: IP address (example: 10.21.134.111)$i: Subnet Mask$j: IPv4 address for the gateway server$k: IPv6 Link Local Address$l: IPv6 Connect IP Address$m: IPv6 address for the gateway$n: TCP port number (0 – 28671)$o: TCP Window Scale Expansion (0 – 14)$p: Congestion Control Option (Enable, Disable)$q: iSNS Server (Enable, Disable)$r: iSNS server address (example: 10.21.134.111 or IPv6 notation)$s: iSNS server port number (0 – 65535)$t: CHAP for CA (Enable, Disable)$u: CHAP User for CA$v: CHAP for RA (Enable, Disable)$w: CHAP User for RA$x: Header Digest (Enable, Disable)$y: Data Digest (Enable, Disable)$z: Jumbo Frame (Enable, Disable)$A: Transfer rate (1GbAuto, 10GbAuto, 1GbFull, 100MbFull, Auto)$B: CmdSN Count (20, 40, 80, 120, 180, Unlimited)$C: VLAN ID (Enable, Disable)$D: VLAN ID value (0 – 4095)$E: MTU size$F: Limit Band Width (10 – 400)$G: REC Line No. (0 – 127)$H: REC Sync transfer mode (Enable, Disable)$I: REC Stack transfer mode (Enable, Disable)$J: REC Consistency transfer mode (Enable, Disable)$K: REC Through transfer mode (Enable, Disable)

[Port=$a Affinity=$b iSCSI_Name=$c Alias_Name=$d Host_Response=$e Reset_Scope=$f Reserve_Cancel=$g IP=$h Netmask=$i Gateway=$j Local=$k Connect=$l IPv6_Gateway=$m Tcp_Port=$n Window_Scale=$o Congestion=$p iSNS=$q iSNS_IP=$r iSNS_Port=$s Chap=$t Chap_User=$u Chap_Ra=$v Chap_User_Ra=$w Header=$x Data=$y Jumbo_Frame=$z Rate=$A Cmdsn=$B Vlan=$C Vlan_value=$D Mtu=$E Bandwidth=$F REC_Line_No=$G REC_Transfer_Mode_Sync=$H REC_Transfer_Mode_Stack=$I REC_Transfer_Mode_Consistency=$J REC_Transfer_Mode_Through=$K]





163


02060004 Set FCoE Port Parameter The FCoE port parameters are set.$a: Port number (example: 001, 002, or "All")$b: Host Affinity (Enable, Disable)$c: Transfer rate (10Gb)$d: Frame size [Byte] (512, 1024, 2048)$e: Host response name$f: Reset Scope (Initiator, Target)$g: Release Reservation if Chip is Reset (Enable, Disable)$h: FCF VLAN ID (Enable, Disable)$i: FCF VLAN ID value (0 – 4095)$j: FCF fabric name setting (Enable, Disable)$k: FCF fabric name (example: 0001000100010001)

[Port=$a Affinity=$b Rate=$c Frame_Size=$d Host_Response=$e Reset_Scope=$f Reserve_Cancel=$g Vlan=$h Vlan_value=$i Fcf_Fabric=$j Fabric_Name=$k]

02060006 Set FC/FCoE Host The FC host or the FCoE host settings are changed.$a: Host number$b: Host name$c: WWN$d: Host response name$e: Host group name

[No=$a Name=$b WWN=$c Host_Response=$d Host_Group=$e]

02060007 Delete FC/FCoE Host The FC host or the FCoE host is deleted.$a: Host name[Name=$a]

02060009 Set SAS Host The SAS host settings are changed.$a: Host number$b: Host name$c: SAS address$d: Host response name$e: Host group name

[No=$a Name=$b Address=$c Host_Response=$d Host_Group=$e]

0206000A Delete SAS Host The SAS host is deleted.$a: Host name[Name=$a]

0206000C Set iSCSI Host The iSCSI host settings are changed.$a: Host number$b: Host name$c: iSCSI name$d: Alias name$e: IP address type (IPv4, IPv6)$f: IP address (example: 192.168.1.10 or IPv6 notation)$g: CHAP user name$h: Host response name$i: CmdSN Count (20, 40, 80, 120, 180, Unlimited)$j: Host group name

[No=$a Name=$b Iscsi_Name=$c Alias_Name=$d IP_Type=$e IP=$f Chap_User=$g Host_Response=$h Cmdsn=$i Host_Group=$j]

0206000D Delete iSCSI Host The iSCSI host is deleted.$a: Host name[Name=$a]

0206000E Create LUN Group The affinity group or the LUN group is created or copied.

$a: Affinity group name or LUN group name$b: Affinity group number or LUN group number$c: Host LUN$d: Volume number

[Name=$a No=$b [LUN=$c Volume=$d]]





164


0206000F Set LUN Group The affinity group or the LUN group settings are changed.

$a: Affinity group name or LUN group name$b: New affinity group name or new LUN group name$c: Host LUN$d: Volume number$e: Host LUN that is to be deleted$f: Host LUN that is to be added or changed$g: Volume number that is to be added or changed

[Name=$a New_Name=$b [LUN=$c Volume=$d] Remove_LUN=$e [Change_LUN=$f Volume=$g]]

02060010 Delete LUN Group The affinity group or the LUN group is deleted.$a: Affinity group name or LUN group name[Name=$a]

02060011 Set Host Affinity The host affinity is set or copied.$a: Host group name$b: Port group name$c: LUN group name$d: Host name$e: Port number

[Host_Group=$a Port_Group=$b LUN_Group=$c [Host=$d Port=$e]]

02060012 Release Host Affinity The host affinity setting is released.$a: Host group name$b: Host name$c: Port group name$d: Port number

[Host_Group=$a Port_Group=$c [Host=$b Port=$d]]

02060013 Set Mapping LUN mapping is set or copied.$a: Host response name$b: Port group name$c: Port number$d: LUN group name$e: Host LUN that is to be deleted$f: Host LUN that is to be added or changed$g: Volume number that is to be added or changed

[Host_Response=$a Port_Group=$b Port=$c LUN_Group=$d Remove_LUN=$e [Change_LUN=$f Volume=$g]]

02060014 Release Mapping The LUN mapping setting is released.$a: Port group name$b: Port number

[Port_Group=$a Port=$b]





165


02060015 Set Host Response The host response parameters are set or changed.$a: Host response name$b: Host response number$c: Load Balance Response (Busy, Queue-Full, Unit-Attention)$d: Byte-0 of Inquiry Response (Disable, 7F, 20)$e: Inquiry VPD ID Type (Type1, Type1-3, Type3)$f: Reservation Conflict Response (Enable, Disable)$g: Command Timeout Interval [sec] (10 – 255)$h: Standard Data Version (3, 4, 5)$i: Host Specific Mode (Normal, AIX, HP-UX, Linux, BS2000)$j: Symmetrical Access (Active, Passive)$k: Report of volume mapping modification (Enable, Disable)$l: Report of expansion volume capacity modi-fication (Enable, Disable)$m: Vendor Unique Sense Code (Enable, Disable)$n: iSCSI Discovery Reply Mode (Port, All)$o: Sense Data Conversion (None, Linux, Windows, Custom)$p: Sense Key for sense information before conversion (0 – F or *)$q: Sense Code for sense information before conversion (00 – FF or *)$r: Additional Sense Code for sense information before conversion (00 – FF or *)$s: Sense Key for sense information after conversion (0 – F or *)$t: Sense Code for sense information after conversion (00 – FF or *)$u: Additional Sense Code for sense information after conversion (00 – FF or *)$v: TPGS Mode (Enable, Disable)$w: TPG Referrals (Enable, Disable)$x: iSCSI Reservation Range (Port, System)

[Name=$a No=$b Status=$c Inquiry=$d Vpd=$e Conflict=$f Timeout=$g Version=$h Mode=$i Symmetric=$j LUN_Change=$k LUN_Expand=$l Unique_Sense=$m iSCSI_Response=$n Sense_Preset=$o [Sense_From=$p/$q/$r Sense_To=$s/$t/$u] Tpgs_Mode=$v Tpg_Referrals=$w iSCSI_Rsv_Range=$x]

02060016 Delete Host Response The host response is deleted.$a: Host response name[Name=$a]

02060017 Set CA Reset Group The CA Reset Group parameter is set or deleted.$a: Port number (example: 001, 002)[Port=$a]

02060018 Create Port Group The port group is created.$a: Port group name$b: Port group number$c: Port number (example: 001, 002)

[Name=$a No=$b Port=$c]

02060019 Set Port Group The port group settings are changed.$a: Port group name$b: New port group name$c: Port number (example: 001, 002)

[Name=$a New_Name=$b Port=$c]





166


0206001A Delete Port Group The port group is deleted.$a: Port group name[Name=$a]

0206001B Create Host Group The host group is created.$a: Host group name$b: Host group number$c: Host name$d: Host response name

[Name=$a No=$b Host=$c Host_Response=$d]

0206001C Set Host Group The host group settings are changed.$a: Host group name$b: New host group name$c: Host name$d: Host response name

[Name=$a New_Name=$b Host=$c Host_Response=$d]

0206001D Delete Host Group The host group is deleted.$a: Host group name[Name=$a]

0206001E Set Host LU Qos mode The Host-LU QoS mode is enabled or disabled.$a: Host LU-QoS mode (Enable, Disable)[Mode=$a]

0206001F Set LU QoS Group The LU QoS group is set.$a: LU-QoS group number$b: Host LUN$c: Band width limit (0 – 15)

[No=$a [LUN=$b Limit=$c]]

02060020 Delete LU QoS Group The LU QoS group is deleted.$a: LU QoS group number[No=$a]

02060021 Set Port QoS The bandwidth limit for the port is set.$a: Port number (example: 001 or "All")$b: Band width limit (0 – 15)$c: Event number (1 – 7) $d: Schedule number (0 – 2047 or "None")

[Port=$a Limit=$b Event_No=$c Schedule_No=$d]

02060022 Set Host QoS The bandwidth limit for the host is set.$a: Host name$b: Band width limit (0 – 15)$c: Event number (1 – 7)$d: Schedule number (0 – 2047 or "None")

[Host=$a Limit=$b Event_No=$c Schedule_No=$d]

02060023 Set LU QoS The bandwidth limit for the host LUN is set or released.

$a: Port number (example: 001, 002) $b: Host name$c: LU QoS group number or "Clear"$d: Event number (1 – 7)$e: Schedule number (0 – 2047 or "None")

[Port=$a Host=$b Qos_Group=$c Event_No=$d Schedule_No=$e]

02060028 Start Host LU QoS Performance Performance information collection for the Host-LU QoS is started.

$a: Port number (example: 001, 002, or "All")[Port=$a]

02060029 Stop Host LU QoS Performance Performance information collection for the Host-LU QoS is stopped.

$a: Port number (example: 001, 002, or "All")[Port=$a]

0206002A Set Host path State The access settings from the host is changed.$a: Port number (example: 001, 002)$b: Host name$c: State (Online, Offline)

[Port=$a Host=&b State=$c]





167


0206002B Set LU QoS Schedule The LU QoS schedule is created, changed, or deleted.

$a: Schedule number (0 – 2047)$b: Mode (Set, Delete)

[No=$a Mode=$b]

02070001 Set Role The custom role is created or the custom role settings are changed.

$a: Role name$b: Policy (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)

[Name=$a Policy=$b]

02070002 Delete Role The custom role is deleted.$a: Role name[Name=$a]

02070003 Set User The user account is created or the user account settings are changed.

$a: User name$b: Role name $c: Whether the created/changed account is enabled or disabled (Enable, Disable)$d: Password

[Name=$a Role=$b Function=$c Passwd=$d]

02070004 Delete User The user account is deleted.$a: User name[Name=$a]

02070005 Initialize User All of the user accounts in the storage system are deleted and the account settings are initialized.Detail information is not displayed.

02070006 Set SSH Public Key The SSH public key is imported or the existing SSH public key is deleted.

$a: SSH public key (*, -)[Key=$a]

02080001 Set Advanced Copy License The Advanced Copy license is set.


02080002 Delete Advanced Copy License The Advanced Copy license is deleted.


02080003 Set Advanced Copy policy The pool policy for the Advanced Copy is set.$a: Notification threshold [%] (1 – 97)$b: Warning threshold [%] (2 – 98)$c: Error threshold [%] (3 – 99)

[Information=$a Warning=$b Error=$c]

02080004 Set SDPE The SDPV resolution is set.$a: Resolution for SDPV (1GB, 2GB, 4GB)[SDPE=$a]

02080005 Set Advanced Copy Table Size The copy table size is set.$a: Resolution (1, 2, 4, 8, 16)$b: Copy table size (example: 8MB, 16MB)$c: Copy table size threshold [%] (1 – 100)

[Resolution=$a Size=$b Warning=$c]

02080006 Set EC/OPC Rate The EC/OPC priority and the copy schedule mode are set.

$a: EC/OPC priority (Auto, High, Low, Very Low, Middle)$b: Copy schedule mode (Session Balancing, Dst RG Balancing)

[Rate=$a Sch_Mode=$b]

02080007 Initialize Snap Data Volume The SDV is initialized.$a: SDV number[No=$a]





168


02080008 Delete Snap Data Pool Volume The SDPV is deleted.$a: SDPV number$b: Mode (Force, Reservation)

[No=$a Mode=$b]

02080009 Start Advanced Copy The SnapOPC+ is started.$a: Type (SnapOPC+)$b: Copy source volume number$c: Copy destination volume number

[Type=$a Source_No=$b Destination_No=$c]

0208000A Delete Advanced Copy The copy session is stopped.$a: Session ID$b: Deletion mode (Force, Normal)

[ID=$a Mode=$b]

0208000B Set Host Port Mode The port mode for the host interface port is changed.

$a: Port number (example: 001 or "All") $b: Port mode after changing (CA, RA, Initiator, CA/RA, CH, CU)

[Port=$a Mode=$b]

0208000C Modify REC path The REC copy path information is set, imported, or deleted.Detail information is not displayed.

0208000D Set REC Round Trip Time The round trip time for the REC is set.$a: Box ID for the remote device$b: Round trip time for the REC [msec] (1 – 65535)

[Box_ID=$a Time=$b]

0208000E Set REC Multiplicity The REC multiplicity is set.$a: Box ID for the remote device$b: REC Multiplicity (1 - 1024, Auto)$c: Priority level (1 - 8, Auto)$d: Copy schedule mode (Session Balancing, Dst RG Balancing)

[Box_ID=$a Multiplicity=$b Priority_Level=$c Sch_Mode=$d]

0208000F Set REC Buffer The REC Buffer is set.$a: Group number (REC Buffer number)$b: Volume type (Open)$c: Box ID for the remote device $d: REC Buffer size [MB]$e: Buffer type (Receive, Send) $f: Forwarding Interval [sec]$g: HALT Wait Timer [sec] (0, 5, 10, 15)$h: Monitoring Time [sec] (0 – 15) $i: I/O Priority Mode (Enable, Disable)$j: HALT Priority Mode (Enable, Disable)

[No=$a Vol_Type=$b Box_ID=$c Size=$d Type=$e Interval=$f Wait_Timer=$g Monitor=$h IO_Response_Priority=$i HALT_Priority=$j]

02080010 Delete REC Buffer The REC Buffer is deleted.$a: Group number (REC Buffer number)[No=$a]

02080011 Create REC Disk Buffer The REC Disk Buffer is created.$a: RAID group number$b: RAID group name$c: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$d: Assigned CM (0, 1)$e: Encryption by CM (Enable, Disable)$f: Stripe Depth (64KB, 128KB, 256KB, 512KB, 1024KB)

[No=$a Name=$b Disk=$c CM=$d Encryption=$e Stripe_Depth=$f]





169


02080012 Set REC Disk Buffer The REC Disk Buffer allocation for the REC Buffer is changed.

$a: Group number (REC Buffer number)$b: RAID group number

[Group_No=$a No=$b]

02080013 Delete REC Disk Buffer The REC Disk Buffer is deleted.$a: RAID group number[No=$a]

02080014 Format REC Disk Buffer The REC Disk Buffer is formatted.$a: RAID group number[No=$a]

02080015 Export Storage Info The storage system information is exported.


02080016 Export Backup REC Path The copy path information is exported.


02090001 Set Network The network environment is set.$a: IP address format (IPv4, IPv6)$b: LAN port (MNT, RMT, FST)$c: Transfer Rate (1000Mb, 100MbFull, 100MbHalf, 10MbFull, 10MbHalf, Auto)$d: Master IP Address$e: Slave IP Address$f: Subnet Mask$g: Master IP Link Local Address$h: Slave IP Link Local Address$i: Master Connect IP Address$j: Slave Connect IP Address$k: Length of Subnet Prefix [bit] (3 – 128)$l: Gateway Address$m: Primary DNS IP Address$n: Secondary DNS IP Address$o: Wake on LAN (Enable, Disable)$p: Allowed IP Address$q: Allowed IP Offset (1 – 16)

[Format=$a Port=$b $Speed=$c Master=$d Slave=$e Netmask=$f Master_Local=$g Slave_Local=$h Master_Connect=$i Slave_Connect=$j Prefix_Length=$k Gateway=$l Primary_DNS=$m Secondary_DNS=$n Wake_On=$o [Allow=$p Allow_Offset=$q]]

02090002 Set Firewall The firewall setting is changed$a: LAN port (MNT, RMT, FST)$b: HTTP (Open, Close)$c: HTTPS (Open, Close)$d: Telnet (Open, Close)$e: SSH (Open, Close)$f: Maintenance Secure (Open, Close)$g: ICMP (Open, Close)$h: SNMP (Open, Close)$i: RCIL (Open, Close) $j: IP Redirect Test (Open, Close)

[Port=$a Http=$b Https=$c Telnet=$d Ssh=$e Mnt_Secure=$f Icmp=$g Snmp=$h RCIL=$i IP_Redirect_Test=$j]

02090003 Set SNMP The SNMP is set.$a: SNMP function (Enable, Disable)$b: LAN port (MNT, RMT)$c: Authentication Failure Trap (Enable, Disable)$d: Engine ID (example: 12, 13 ... or "Default")$e: MIB-II version (RFC1213, RFC4293)

[Function=$a Port=$b Failure_Trap=$c Engine_ID=$d Version=$e]





170


02090004 Set SNMP Manager The SNMP manager settings are added, changed, or deleted.

$a: Manager number (1 – 10)$b: IP address

[No=$a IP=$b]

02090005 Set SNMP View The SNMP view settings are added, changed, or deleted.

$a: View name$b: Subtree$c: Type (Include, Exclude)

[Name=$a [Subtree=$b($c)]]

02090006 Set SNMP User The SNMP user settings are added, changed, or deleted.

$a: User name$b: SNMP View name$c: Authentication (Enable, Disable)$d: Authentication method (MD5, SHA)$e: Encryption (Enable, Disable)

[Name=$a View=$b Authentication=$c Method=$d Encryption=$e]

02090007 Set SNMP Community The SNMP community settings are added, changed, or deleted.

$a: SNMP community name$b: SNMP MIB view name$c: SNMP manager number (1 – 10)

[Name=$a View=$b Manager=$c]

02090008 Set SNMP Trap The SNMP Trap settings are added, changed, or deleted.

$a: SNMP trap number (1 – 10)$b: SNMP manager number (1 – 10)$c: IP address$d: SNMP version (v1, v2c, v3)$e: Community name$f: User name$g: Port number (example: 162)

[No=$a Manager=$b IP=&c Version=$d Community=$e User=$f Port=$g]

02090009 Export Enhanced MIB The MIB file is exported.


020A0001 Set Email Notification The email notification settings are changed.$a: Email notification (Enable, Disable)$b: Used LAN port (MNT, RMT, FST)$c: SMTP port number (example: 25)$d: SMTP server address$e: Authentication method (None, Auto, Cram-MD5, Plain, Login)$f: User account name$g: Comments when sending an email$h: Destination email address$i: Retry count (0, 1)$j: Retry interval [sec] (1 – 5)$k: Timeout [sec] (1 – 30)$l: Split mode (Enable, Disable)$m: Split size (example: 128KB)$n: Email log (Enable, Disable)$o: I/O module log (Enable, Disable)$p: Customer information (Enable, Disable)

[Function=$a Port=$b Port_No=$c Server=$d Authentication=$e User=$f From=$g To=$h Retry_Count=$i Retry_Interval=$j Timeout=$k Partial=$l Size=$m Send_Log=$n Iom=$o Customer=$p]





171


020A0002 Set Event Notification The event notification settings are changed.$a – $M: Notification method (None, Host Sense, Host Sense (HS=0), Host Sense (Ope Msg Enable), REMCS, SNMP Trap, SNMP Trap (HS=0), Mail, Mail (HS=0), Syslog, Syslog (HS=0), AIS, AIS(HS=0))$N: Preset (System, REMCS)

[Parts_Error=$a Disk_Error=$b Temperature_Error=$c Battery_Life_Error=$d Rebuild_Copyback_With_Redundant=$e Rebuild_Copyback=$f Complete_Redundant_Copy=$g Complete_Rebuild=$h Bad_Data=$i Pinned_Data=$j Not_Ready=$k Remote_Path=$l Halt_Path=$m Halt_Overload=$n Halt_Other=$o Tp_Pool_Ratio=$p Redundant=$q Copy_Error=$r SED_Network_Error=$s Parts_Warning=$t Disk_Warning=$u Temperature_Warning=$v Battery_Life_Warning=$w Recovery_Module=$x Temperature_Restoration=$y User_Logon_Logoff=$z Operate_Raid_Group=$A Add_Release_Hot_Spare=$B Operate_Volume=$C Power_Off_On_Cfl=$D Sdp_Policy_Level1=$E Sdp_Policy_Level2=$F Sdp_Policy_Level3=$G Limit_Copy_Table=$H Expire_Trial_Copy_License=$I ODX=$J SED_Network_Recovered=$K Change_FC_CA_Port_Link_Status=$L Limit_Host_Login=$M Preset=$N]

020B0001 Create SSH Server Key The SSH server key is created.$a: Key Length [bit] (1024, 2048, 4096)$b: SSH Version1 (Enable, Disable)

[Length=$a Version1=$b]

020B0002 Create SSL Certificate The SSL server key and the SSL certificate are created.

$a: Key Length [bit] (1024, 2048, 4096)$b: Common Name$c: Subject Alt Name

[Length=$a Common=$b Subject_Alt=$c]

020B0003 Import SSL Certificate The SSL server key and the SSL certificate are registered.Detail information is not displayed.





172


020B0004 Set RADIUS The RADIUS authentication settings are changed.$a: RADIUS authentication (Enable, Disable)$b: Recovery mode (Enable, Enable (Network), Disable)$c: IP address or FQDN for the primary server$d: LAN port that is used by the primary server (MNT, RMT)$e: Port number for the primary server$f: Authentication mode for the primary server (CHAP, PAP)$g: Common key with the primary server$h: Retry timeout value for the primary server [sec] (10, 20, 30, 40, 50, 60)$i: IP address or FQDN for the secondary server$j: LAN port that is used by the secondary server (MNT, RMT)$k: Port number for the secondary server$l: Authentication mode for the secondary server (CHAP, PAP)$m: Common key with the secondary server$n: Retry timeout value for the secondary server [sec] (10, 20, 30, 40, 50, 60)

[Function=$a Recovery=$b Pri_Server=$c Pri_Port=$d Pri_Port_No=$e Pri_Authentication=$f Pri_Secret=$g Pri_Timeout=$h Sec_Server=$i Sec_Port=$j Sec_Port_No=$k Sec_Authentication=$l Sec_Secret=$m Sec_Timeout=$n]

020B0005 Set Syslog The syslog notification settings are changed.$a: Log sending function for syslog server 1 (RFC3164, RFC5424, Disable)$b: IP address for syslog server 1$c: Port that is used by syslog server 1 (MNT, RMT)$d: Port number for syslog server 1$e: Log sending function for syslog server 2 (RFC3164, RFC5424, Disable)$f: IP address for syslog server 2$g: Port that is used by syslog server 2 (MNT, RMT)$h: Port number for syslog server 2

[Function1=$a Server1=$b Port1=$c Port_No1=$d Function2=$e Server2=$f Port2=$g Port_No2=$h]

020B0006 Set Audit The audit log settings are changed.$a: Audit log function (Enable, Disable)$b: Audit log function for syslog server 1 (RFC3164, RFC5424, Disable)$c: IP address for syslog server 1$d: Port that is used by syslog server 1 (MNT, RMT)$e: Port number for syslog server 1$f: Log sending function for syslog server 2 (RFC3164, RFC5424, Disable)$g: IP address for syslog server 2$h: Port that is used by syslog server 2 (MNT, RMT)$i: Port number for syslog server 2

[Audit=$a Function1=$b Server1=$c Port1=$d Port_No1=$e Function2=$f Server2=$g Port2=$h Port_No2=$i]

020B0007 Set SED Key Machine Name The key management machine name is set.$a: Key management machine name[Machine_Name=$a]





173


020B0008 Set SED Key Server The key server is set.$a: Server ID (1, 2)$b: IP address or domain name for the server$c: LAN port (MNT, RMT)$d: Port number

[ID=$a Server=$b Port=$c Port_No=$d]

020B0009 Import SSL/KMIP Certificate The SSL/KMPI server certification is imported.

–

020B000A Create SED Key Group The key group is created.$a: Key group name$b: Storage system group name$c: Security level (Low, High)$d: Recovery mode (Auto, Manual)$e: Key valid period (1 - 12, or "Unlimited")$f: Master server ID (1 - 2, or "None")$g: Slave server ID (1 - 2, or "None")

[Name=$a Machine_Group_Name=$b Security_Level=$c Recovery_Mode=$d Period=$e Master_ID=$f Slave_ID=$g]

020B000B Set SED Key Group The key group settings are changed.$a: Key group name$b: Storage system group name$c: Security level (Low, High)$d: Recovery mode (Auto, Manual)$e: Key valid period (1 - 12, or "Unlimited")$f: Master server ID (1 - 2, or "None")$g: Slave server ID (1 - 2, or "None")

[Name=$a Machine_Group_Name=$b Security_Level=$c Recovery_Mode=$d Period=$e Master_ID=$f Slave_ID=$g]

020B000C Delete SED Key Group The key group is deleted.

–

020B000D Change SED Key The SED authentication key is changed.$a: Mode (Reuse, Delete, New)[Mode=$a]

020B000E Recover SED Key Group The key group that is in locked status can now be accessed.–

020C0001 Set Date The date, time, and time zone of the storage system are set.

$a: Date and time (example: 2011-12-28 00:27:49)$b: Time zone (example: -9:00, +1:00)$c: DST setting (Enable, Disable)$d: Start of DST (example: 12-28 00:00, 12-1st-mon 07:00)$e: End of DST (example: 12-28 00:00, 12-1st-mon 07:00)$f: NTP function (Enable, Disable)$g: IP address for the NTP server$h: Port that is used for the NTP connection (MNT, RMT)

[Time=$a Time_Zone=$b DST=$c From=$d To=$e NTP_Function=$f NTP_Server=$g NTP_Port=$h]

020C0002 Set Storage System Name The storage system name is set.$a: Storage system name$b: Installation location$c: Administrator information$d: Description for the storage system

[Name=$a Site=$b Contact=$c Description=$d]

020C0003 Set Encryption The encryption mode is enabled or disabled.$a: Encryption mode (Fujitsu, AES, Disable)[Mode=$a]





174


020C0004 Set Box ID The Box ID is set.$a: Box ID[ID=$a]

020C0005 Set Power Synchronization The power synchronization settings are changed.$a: Controller module that is managed with the power synchronization function (None, CM0, CM1)$b: Auto Power function (Enable, Disable)$c: Power Resume function (Enable, Disable)$d: Delay until shutdown [sec]$e: Power failure signal logic (Positive, Negative)$f: Low battery signal logic (Positive, Negative)$g: UPS shutdown signal logic (Positive, Negative)$h: UPS shutdown signal (Enable, Disable)

[Connect=$a Auto=$b Resume=$c Timer=#d Power_Fail=$e Low_Battery=$f UPS_Shutdown_Signal=$g UPS_Shutdown=$h]

020C0006 Set SED Authentication The SED authentication key is registered.


020C0007 Set SMI-S The SMI-S function is enabled or disabled.$a: SMI-S function (Enable, Disable)[Function=$a]

020C0008 Set Subsystem Parameter The subsystem parameters are set.$a: Load Balance (Enable, Disable) $b: 1CM Write Through (Enable, Disable)$c: Highland Mode (Enable, Disable)$d: Read Sequential (Enable, Disable)$e: Write Sequential (Enable, Disable)$f: Reject INQUIRY from Unauthorized Host (Enable, Disable)$g: Critical Disk Mode (Enable, Disable)$h: Disk Media Error Check (Mode1, Mode2)$i: Read Compare Mode for Online Disks (0 – 255)$j: Read Compare Mode for Nearline Disks (0 – 255)$k: All LBAs (Enable, Disable)$l: Thin Provisioning Allocation Mode (TPP Balancing, TPV Balancing) $m: Check BID after Write Command (Enable, Disable)$n: Reduce the Timeout Period for Nearline Disks (Enable, Disable)$o: Cache Mirroring (Enable, Disable) $p: Skip Retry when Failed to Access Disks (Enable, Disable)$q: Check the checkcodes of all the data blocks (Enable, Disable)$r: Early detection-and-isolation of a failed disk (Enable, Disable)$s: Use "Add Host Group" (Enable, Disable)$t: Use "Add Host" (Enable, Disable)

[Load_Balance=$a 1cm_Write_Through=$b High_Altitude=$c Read_Sequential=$d Write_Sequential=$e Reject_Inquiry=$f Critical_Disk_Mode=$g Disk_Media_Error_Check=$h Rd_Compare_Online_Count=$i Rd_Compare_Nrline_Count=$j All_LBAs=$k TPP_Alloc_Mode=$l Chk_BID_After_Write=$m Reduce_Timeout_Nrline=$n Cache_Mirroring=$o Skip_Retry_Access_Disks=$p Checkcode_Enforce_Mode=$q Disk_Fail_Early_Detect=$r Use_Add_Host_Group=$s Use_Add_Host=$t]





175


020C0009 Set Disk Patrol The disk patrol parameters are set.$a: Target disk type (None, Data, Spare, Unused)$b: Write Check (Enable, Disable)$c: Check Code Check (Enable, Disable)$d: Disk Port Check (Enable, Disable)$e: Interval between each test increment [sec] (1, 2, 3, 4, 5, 6, 7, 8, 9, 10)$f: Operation Size [MB] (0.5, 1.0, 2.0, 4.0, 8.0, 16.0)$g: Verify Check for Unused Area of Data Disk (Enable, Disable)

[Disk_Type=$a Write_Check=$b Check_Code_Check=$c Disk_Port_Check=$d Interval=$e Operation_Size=$f Free_Area_Check=$g]

020C000A Release Reservation The reservation status of the volume is released.$a: Volume number[Volume_No=$a]

020C000B Set Disk Performance Monitor The disk performance monitoring parameters are changed.

$a: Monitoring function (Enable, Disable)$b: Disk isolation (Enable, Disable)$c: Error monitoring factor [%] (0.1 – 10.0)$d: Threshold of allowable error (7.2 – 720.0)$e: Monitoring time [hour]$f: Event notification (Enable, Disable)

[Monitoring=$a Disk_Isolation=$b Factor=$c Threshold=$d Interval=$e Event_Notification=$f]

020C000E Set Debug Mode The debug mode is set.$a: Trace level (example: 00-FF)$b: Collection mode of the panic dump (Nose and Tail, Fortnight, Disable)

[Trace_Level=$a Panic=$b]

020C000F Start Performance Performance information collection is started.$a: Collection interval [sec] (30, 60, 90, 120, 150, 180, 210, 240, 270, 300)

[Interval=$a]

020C0010 Stop Performance Performance information collection is stopped.


020C0011 Set Bind In Cache The Bind-in-Cache memory size is changed.$a: New capacity (example: 256MB)[Size=$a]

020C0012 Delete Event All of the event logs are deleted.


020C0013 Initialize System Disk The BUD is initialized.


020C0014 Change Master The master CM is changed.


020C0015 Write Back Pinned Data The pinned data is written back to the volume.$a: Volume number[No=$a]

020C0016 Clear Pinned Data The pinned data in the cache memory is deleted.$a: Volume number[No=$a]

020C0017 Forced Write Back Write back is forcibly performed.


020C0018 Forced Restore Restoration is forcibly performed.






176


020C0019 Recover Backup Restore Fail The storage system is recovered from Backup Fail status or Restore Fail status.Detail information is not displayed.

020C001A Recover Machine Down Recovery The Machine Down Recovery Fail status is reset.


020C001B Reset All Controller Module All of the controllers are rebooted.


020C001C Recover RAID Group The RAID group is forcible recovered.$a: RAID group number$b: Recovery mode (Force, Disk)

[No=$a Mode=$b]

020C001D Diagnose Disk The disk diagnosis is started.$a: Disk (DE-ID + Slot number (example: 0000, 0001, 0002))$b: Count (1 - 65535)$c: Mode (Read Only, Write/Read/Compare)

[Disk=$a Count=$b Mode=$c]

020C001E Diagnose RAID Group The RAID group diagnosis is started.$a: RAID group number$b: Recovery mode (Enable, Disable)

[No=$a Auto_Recovery=$b]

020C001F Stop Diagnosis The diagnosis process is stopped.$a: Type (Disk, RAID Group)$b: RAID group number

[Type=$a RAID_No=$b]

020C0020 Clear Diagnosis The diagnosis is complete.$a: Type (Disk, RAID Group)$b: RAID group number

[Type=$a RAID_No=$b]

020C0021 Set LED The LED of the target component is turned on, blinked, or turned off.

$a: Target component (CE, Disk)$b: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$c: LED (ON, OFF)

[Target=$a Disk=$b LED=$c]

020C0022 Set Event Parameter The LED display (turning on or blinking) settings when an event occurs are set.

$a: Blink Fault LED at warning (Enable, Disable) $b: Turn on Fault LED when redundant copy is completed (Enable, Disable)

[Warning_LED=$a Comp_Redundant_Copy_LED=$b]

020C0023 Shutdown The storage system is off or rebooted.$a: Mode (Shutdown, Restart)[Mode=$a]

020C0024 Set Differential Backup The differential backup function is enabled or disabled.

$a: Differential Backup (Enable, Disable)[Differential_Backup=$a]

020C0025 Set ODX Mode The ODX function is enabled or disabled.$a: Mode (Enable, Disable)[Mode=$a]

020C0026 Set CLI Idle Timeout The idle timeout limit when using ETERNUS CLI is set or displayed.

$a: Timeout limit [minute] (5 – 60)[Timeout=$a]

020D0001 Update Customer Information The customer information is registered or updated.

$a: Deletion of the customer information in the storage system (Yes, No)

[Delete_Customer_Identity_Info=$a]





177


020D0002 Set Communication Environment The communication environment settings are registered or updated.Detail information is not displayed.

020D0003 Configure Automatic Log Transmission The automatic log transmission settings are changed.

$a: Send Log based on Events (Enable, Disable)$b: Periodic Log Transmission (Enable, Disable)$c: Time for periodic log transmission (example: 00:00)$d: Schedule for periodic log transmission (Once per Week, Every Day)$e: Day of the week when the periodic logs are sent (example: Monday)

[Send_Log_Error_Occur=$a Period_Transmission_Log=$b Time=$c Period=$d Day=$e]

020D0004 Send Log Manually The log is sent manually.$a: Incident Number$b: Time Range Specified (Enable, Disable)

[Incident_No=$a Time_Range=$b]

020D0005 Stop Restart Remote Support The remote support is stopped or restarted.$a: Mode (Stop, Restart)[Mode=$a]

020D0006 Set Download Controller Firmware The download parameters for the controller firmware are set.

$a: Download Destination (REMCS, Peer level Storage System)$b: Automatic Download (Enable, Disable)$c: Download Schedule (Same as Connection Period, Once per Week) $d: Download Date (example: Sunday 00:00) $e: Automatic Controller Firmware Update (Enable, Disable)$f: Bandwidth Limit (Enable, Disable)$g: Download speed [Kbit/s] (100 – 999)

[Destination=$a Auto_DownLoad=$b Download_Schedule=$c Download_Date=$d Auto_Update=$e Bandwidth_Limit=$f Speed=$g]

020D0007 Remote Download Controller Firmware The controller firmware is downloaded from the remote support center.Detail information is not displayed.

020D0008 Site Download Controller Firmware The controller firmware is downloaded from a dif-ferent storage system.Detail information is not displayed.

020D0009 Stop Download Controller Firmware Downloading of the controller firmware is stopped.Detail information is not displayed.

020D000A Set Firmware Update from Peer Storage The settings for downloading controller firmware from a different storage system are set.

$a: IP address of the storage system that contains the downloaded firmware (example: 192.168.1.1) $b: LAN port for connecting to the different storage system (MNT, RMT)

[IP=$a Port=$b]

020D000B Set Remote Support The remote support parameters are set.$a: Deletion of the customer information in the storage system (Yes, No)

[Delete_Customer_Identity_Info=$a]





178


020D000C Set AIS Connect The AIS Connect settings are changed.$a: AIS Connect function (Enable, Disable)$b: Port (MNT, RMT)$c: Auto Send Log (Enable, Disable)$d: Country code$e: Service contract$f: Server Certification (Enable, Disable)$g: Proxy server IP address or FQDN$h: Proxy server port number (0 – 65535)$i: Proxy type (HTTP, SOCKS)$j: User name

[Function=$a Port=$b Send_Log=$c Country_Code=$d Service_Contract=$e Server_Certification=$f Proxy_Server=$g Proxy_Port_No=$h Type=$i User_Name=$j]

020D000E Send AIS Connect Log The AIS Connect log is sent.


020D000F Set AIS Connect Remote Session The remote sessions for AIS Connect are set.$a: Remote session (Permit, Forbid)$b: Remote session timeout[hour] (1 – 24, or "Unlimited")

[Remote_Session=$a Timeout=$b]

020D0010 Import AIS SSL Certificate The SSL certificate is imported.


020E0001 Start Maintenance The maintenance operation is started.


020E0002 Stop Maintenance The maintenance operation is stopped.


020E0003 Forced Degradation The component is forcibly disabled.$a: Component (example: cm0-ca0)[Component=$a]

020E0004 Forced Online The component is forcibly enabled.$a: Component (example: cm0-ca0)[Component=$a]

020E0005 Preventive Maintenance Preventive maintenance of the component is performed.

$a: Component (example: cm0-ca0)[Component=$a]

020E0006 Hot Expansion Hot expansion of the component is performed.$a: Component (example: cm0-ca0)$b: Change of assigned CM (Enable, Disable)$c: Mode (Canceled)

[Component=$a Change_CM=$b Mode=$c]

020E0007 Hot Deletion Hot removal of the component is performed.$a: Component (example: cm0-ca0)$b: Mode (Canceled)

[Component=$a Mode=$b]

020E0008 Delete Sense The sense information is deleted.


020E0009 Set BTU Date The battery expiration date is set.$a: Component (example: bbu0-btu)$b: Expiration date (example: 201102)

[Component=$a Date=$b]

020E000A Set Host Port License The license for the additional host interface port is registered.Detail information is not displayed.

020E000B Upgrade Storage System Model The storage system model is upgraded.$a: Mode (Canceled)[Mode=$a]





179


020E000C Export Config Information The configuration information is exported.


020E000D Change Assigned CM The assigned CM is changed.


020F0001 Register Controller Firmware The controller firmware is registered.$a: Generation (1 – 4)$b: Firmware version (VxxLxx-xxxx)

[Generation=$a Version=$b]

020F0002 Start CFD Application of the controller firmware (enabled at the next power cycle) is started.

$a: Firmware version (VxxLxx-xxxx, none)[Version=$a]

020F0003 Start CFL Changing of the current controller firmware is started.

$a: Firmware version (VxxLxx-xxxx, none)[Version=$a]

020F0004 Register Disk Firmware The disk firmware is registered.$a: Vender ID$b: Product ID$c: Firmware version

[Vendor=$a Product=$b Revision=$c]

020F0005 Update Disk Firmware The disk firmware is applied.$a: Product ID$b: Firmware version$c: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$d: Apply Mode (Offline, Online)

[Product=$a Revision=$b Disk=$c Application_Type=$d]

020F0006 Delete Disk Firmware The disk firmware is deleted.$a: Product ID[Product=$a]

02100001 Clear Log The log is deleted.


02100002 Clear Panic Dump The panic dump is deleted.


02100003 Apply Config Information The configuration information is applied.$a: Apply Mode (Initialize, Restore)$b: Backup file to be applied (1 – 4)$c: File to be applied (Latest, One-before, Two-before)

[Mode=$a Generation=$b File=$c]

02100004 Clear Disk Error The drive error is deleted.$a: Drive (example: 0000, 0001, 0002, 1000, 1001..., All)

[Disk=$a]

02100005 Delete Bad Data Info The bad data information is deleted.$a: Volume number[No=$a]

02100006 Export Panic Dump The panic dump file is exported.


02100007 Export Log The log file is exported.$a: Customer Information (Enable, Disable)[Customer_Info=$a]

02100008 Export Pinned Data The pinned data is exported.






180


02110001 Set Flexible Tier Mode The Flexible Tier function is enabled or disabled.$a: Mode (Enable, Disable)[Mode=$a]

02110002 Create Flexible Tier Pool The Flexible Tier Pool is created.$a: Flexible Tier Pool number$b: Flexible Tier Pool name$c: Warning threshold [%] (5 – 99)$d: Attention threshold [%] (5 - 80, None)$e: Encryption mode (Enable, Disable)

[No=$a Name=$b Warning=$c Attention=$d Encryption=$e]

02110003 Set Flexible Tier Pool The Flexible Tier Pool settings are changed.$a: Flexible Tier Pool number$b: Flexible Tier Pool name$c: Warning threshold [%] (5 – 99)$d: Attention threshold [%] (5 - 80, None)

[No=$a Name=$b Warning=$c Attention=$d]

02110004 Format Flexible Tier Pool The Flexible Tier Pool is formatted.$a: Flexible Tier Pool number$b: Mode (All, Unformatted)

[No=$a Mode=$b]

02110005 Delete Flexible Tier Pool The Flexible Tier Pool is deleted.$a: Flexible Tier Pool number[No=$a]

02110006 Create Flexible Tier Sub Pool The Flexible Tier Sub Pool is created.$a: Flexible Tier Sub Pool number$b: Flexible Tier Sub Pool name$c: Flexible Tier Pool number $d: Drive type (Online, Nearline, SSD, SED)$e: RAID level (RAID0, RAID1, RAID1+0, RAID5, RAID5+0, RAID6)$f: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$g: Assigned CM (0, 1)$h: Stripe Depth (64KB, 128KB, 256KB, 512KB, 1024KB)

[No=$a Name=$b FTRP_No=$c Attribute=$d Level=$e [Disk=$f CM=$g] Stripe_Depth=$h]

02110007 Set Flexible Tier Sub Pool The Flexible Tier Sub Pool settings are changed.$a: Flexible Tier Sub Pool number$b: Flexible Tier Sub Pool name$c: Assigned CM (0, 1)

[No=$a Name=$b CM=$c]

02110008 Expand Flexible Tier Sub Pool The Flexible Tier Sub Pool capacity is expanded.$a: Flexible Tier Sub Pool number$b: Drive (DE-ID + Slot number (example: 0000, 0001, 0002))$c: Assigned CM (0, 1)

[No=$a [Disk=$b CM=$c]]

02110009 Start FTRPE Migration FTRPE migration is started.$a: FTRPE ID$b: Flexible Tier Sub Pool number

[ID=$a FTSP_No=$b]

0211000A Stop FTRPE Migration All of the waiting FTRPE migrations are deleted.$a: Delete FTRPE migration in error status (Enable, Disable)

[Stop_Error=$a]

0211000B Start Balancing Flexible Tier Pool Balancing of Flexible Tier Pool is started.$a: Flexible Tier Pool number[No=$a]

0211000C Stop Balancing Flexible Tier Pool Balancing of Flexible Tier Pool is stopped.$a: Flexible Tier Pool number[No=$a]





181


02120001 Start Storage Migration Storage Migration is started.$a: Path group number$b: Type (Open)$c: Vender ID$d: Product ID$e: Serial number$f: Operation mode (M, M+QC, M+FC, QC, FC)

[No=$a Type=$b Vendor=$c Product=$d Serial=$e Ope_Mode=$f]

02120002 Suspend Storage Migration Storage Migration is suspended.$a: Path group number$b: LUN (hexadecimal number (example: 0x0000, 0x8000000000000000))

[No=$a LUN=$b]

02120003 Restart Storage Migration Storage Migration is restarted.$a: Path group number$b: LUN (hexadecimal number (example: 0x0000, 0x8000000000000000))

[No=$a LUN=$b]

02120004 Stop Storage Migration Storage Migration is stopped.$a: Path group number$b: LUN (hexadecimal number (example: 0x0000, 0x8000000000000000))

[No=$a LUN=$b]

02120005 Delete Storage Migration Path Group The path group for Storage Migration is deleted.$a: Path group number[No=$a]

03010001 Force Unlock The exclusive resources are forcibly released.






182

Appendix C

Event (SNMP Trap) Display When Using ServerView Operation Manager

This appendix describes the display contents of events (SNMP Traps) that are notified to the SNMP manager(monitoring server) when using the server management software "SeverView Operation Manager" formonitoring the ETERNUS DX Disk storage system.

• This appendix describes the display contents of events (SNMP Traps) when using the MIB definition file for ServerView monitoring that is downloaded from the ETERNUS DX Disk storage system.

• For detailed information about ServerView Operation Manager, refer to the ServerView Operation Manager manuals.

Display contents of the ServerView Operation Manager SNMP Trap type

Alarm type (--#TYPE)

Severity(--#SEVERITY)

Details (--#SUMMARY) specific trap No.

Meaningvariable-bindings (*1) for %s, %x

Item fault CRITICAL Item fault event from %s, id: %x, message: %s 2 A component has failed or degraded

%s: fjdarySspMachineId%x: fjdaryTrapItemId%s: fjdaryTrapMessage

Item warning

MAJOR Item warning event from %s, id: %x[%x], message: %s

5 A component requiring preventive maintenance is detected

%s: fjdarySspMachineId%x: fjdaryTrapItemId%x: fjdaryTrapWarningInfo%s: fjdaryTrapMessage

Sensor status changed

CRITICAL Sensor status changed event from %s, id: %x[%x], message: %s

6 Temperature error is detected

%s: fjdarySspMachineId%x: fjdaryTrapItemId%x: fjdaryTrapSensorInfo%s: fjdaryTrapMessage

Maintenance required

CRITICAL Maintenance required event from %s, id: %x, message: %s

7 An event requiring maintenance or preventive maintenance is detected

%s: fjdarySspMachineId%x: fjdaryTrapMaintenanceInfo%s: fjdaryTrapMessage

Information event (*2)

INFORMATIONAL Information event from %s, message: %s 9 An information-level event is detected

%s: fjdarySspMachineId%s: fjdaryTrapMessage



183

Appendix C Event (SNMP Trap) Display When Using ServerView Operation Manager

*1: For variable-bindings values, refer to "variable-bindings meanings" (page 111) in "A.1.3 SNMP" (page 107).*2: The default setting is "Disable" (no notification).

Information event (*2)

INFORMATIONAL CA port link status changed event from %s, id: %x[%x], message: %s

10 A change in the CA port link status is detected.

%s: fjdarySspMachineId%x: fjdaryTrapItemId%x: fjdaryTrapLinkStatusInfo%s: fjdaryTrapMessage

Item fault to normal (*2)

INFORMATIONAL Item fault to normal, from %s, id: %x, message: %s

22 An event notified by "Item fault" returns to normal status

%s: fjdarySspMachineId%x: fjdaryTrapItemId%s: fjdaryTrapMessage

Item warning to normal (*2)

INFORMATIONAL Item warning to normal, from %s, id: %x[%x], message: %s

25 An event notified by "Item warning" returns to normal status

%s: fjdarySspMachineId%x: fjdaryTrapItemId%x: fjdaryTrapWarningInfo%s: fjdaryTrapMessage

Sensor status change to normal (*2)

INFORMATIONAL Sensor status changed to normal, from %s, id: %x[%x], message: %s

26 An event notified by "Sensor status changed" returns to normal status

%s: fjdarySspMachineId%x: fjdaryTrapItemId%x: fjdaryTrapSensorInfo%s: fjdaryTrapMessage

Display contents of the ServerView Operation Manager SNMP Trap type

Alarm type (--#TYPE)

Severity(--#SEVERITY)

Details (--#SUMMARY) specific trap No.

Meaningvariable-bindings (*1) for %s, %x



184

ETERNUS DX80 S2/DX90 S2 Disk storage systemUser's Guide -Operation-

P3AM-4842-12ENZ0

Date of issuance: June 2013Issuance responsibility: FUJITSU LIMITED

• The content of this manual is subject to change without notice.

• This manual was prepared with the utmost attention to detail.However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the use of information in this manual.

• Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.

• The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from Fujitsu.

Documents

ETERNUS DX80 S2/DX90 S2 Disk storage system User's …storage-system.fujitsu.com/global/doc/pdf/p3am-4842-en.pdf · Disk storage system User's Guide -Operation- ... of the ETERNUS