E DX60 DX80 DX90 Fwup - V10L50

ETERNUS DX60 / DX80 / DX90
Disk Array Unit
Firmware Updating Instructions
Storage System Development Division, Storage Systems Unit,

Storage Quality Assurance Department, Storage Systems Unit
FUJITSU LIMITED
2
ETERNUS DX60 / DX80 / DX90 Firmware Updating Instructions
History of Revision
Version Date Author Content
1 Oct. 10, 2009 First edition
2 Nov. 11, 2009 Amendments, Modifications in Chapter 2 & Appendices 3 &
4, etc
3 Mar. 02, 2010 Amendments, Modifications in Chapter 1.1 & Appendices
4, etc
4 Apr. 27, 2010 Amendments, Additiolal DX90, etc
Before Starting the Procedure
Note
The purpose of this manual is to upgrade Controller Firmware for ETERNUS DX60/DX80/DX90.
This manual can’t be used for other purpose and for other systems.
4
Outline of Flow for the Instructions (Entire Flow)

This manual is divided into following two Steps.
z Updating Procedure of Firmware (Chapter 1)
z Confirmation before Delivery (Chapter 2)
START
Updating of Firmware
(See Chapter 1)
Confirmation before Delivery

(See Chapter 2)
END
5
Outline of the Feature

Replacement of Controller Firmware working in a System is done by registering the New Controller
Firmware to the System Disk (Registration of Controller Firmware) and downloading it from the System
Disk to each Module of the System (Application of Controller Firmware). Flash-ROM is mounted on each
Module that keeps two generations of Firmware. On one side is kept the currently working Firmware and
on the other side is kept the waiting Firmware. Downloading of Firmware from the System Disk to each
Module is done always to the Flash-ROM region of the Firmware of waiting side.
There are two ways of having the Firmware downloaded to the Flash-ROM region start working. One is
the Hot Firmware Replacement (CFL) and the other is OFF-ON Switching of the System Power Supply.
(Non-hot Application of Controller Firmware)
CFL is the Feature of switching over the working Version No. by dividing the Module to the first and the
second phases while maintaining the Hot Working Status by replacing duplicated module through the use
of system redundant configuration.
z Non-hot mode [Controller firmware download] (CFD)]

¾ Switching over of Working Controller Firmware by Power Off/On
z Hot mode [Concurrent firmware loading (CFL)]
¾ Automatic/Manual Application Modes are selectable.
6
[Work Check Sheet]

Hot application
Version No. Hot application Non-hot
Item Work outline (Cooperation
before update (Auto) application
with operator)
1 ( ) Carefully read this manual --- --- ---
2 ( ) Procedure outline 1 Procedure outline
3 ( ) Checking of Key Items 2 Work flow 3 Work flow 4 Work Flow of
and cautions in and cautions in Firmware
Hot Application Hot (automatic) Replacement in
(cooperation Non-Hot
with operator)
4 ( ) Preparation of FST 5.1 Preparation of FST
5 ( ) Acquisition of Firmware from RIS 5.2 Acquisition of Firmware
6 ( ) Acquisition of IP address of the device 5.3 Acquisition of IP address of the device
7 ( ) Check & acquisition of Account of 5.4 On the Account of Maintenance Personnel
Maintenance Personnel
8 ( ) Confirmation of System Status (External View) 5.5 Confirmation of System Status (External View)
before the Execution
9 ( ) FST Connection 6.2 FST Connection
10 ( ) Logon (Start GUI) 6.3 Logon (Start GUI)
11 ( ) Check System Status (GUI) prior to the 6.4 Check System Status (GUI) prior to the operation
operation
12 ( ) Start of maintenance work 6.5 Start of maintenance work
13 ( ) Download of configuration information 6.6 Download of configuration information
14 ( ) Check of version number of EC Firmware in 6.7 Check of version number of EC Firmware in
Working/ Non-Working Working/ Non-Working
15 ( ) Firmware registration 6.8 Firmware registration
16 ( ) Application in Hot (cooperation with operator) 6.9 Application
in Hot
(cooperation
with operator)
17 ( ) Hot Application (Automatic) 6.10 Hot
Application
(Automatic)
18 ( ) Non-Hot Application 6.11 Non-Hot
Application
19 ( ) Confirmation of F/W Ver. No. on 6.12 Confirmation of F/W Ver. No. on
Working/Non-Working EC after Application Working/Non-Working EC after Application
20 ( ) Confirmation of System Status after 6.13 Confirmation of System Status after Application
Application (GUI) (GUI)
21 ( ) End of Maintenance Work 6.14 End of Maintenance Work
22 ( ) Logoff (End of GUI) 6.15 Logoff (End of GUI)
23 ( ) Disconnection of FST 6.16 Disconnection of FST
24 ( ) Confirmation of System Status (External View) 6.17 Confirmation of System Status (External View)
after Application after the Application
Check before Delivery
25 ( ) Asking Items to Users or SE Chapter 2. 1 Asking Items to Users or SE
Note 1.: [Item No.] are representative ones. Read the entire manual carefully.
Note 2.: Marked with ( ) as above are the Work Items.
7
Content
History of Revision 3
Before Starting the Procedure 4
Outline of Flow for the Instructions (Entire Flow) 5
Outline of the Feature 6
Chapter 1. Procedure of firmware update 10
1. Procedure outline 10
1.1. Procedure selection 10
1.2. Time Requirement 11
1.3. Application of Patches to ETERNUS SF (Middleware) 11
1.4. Attention in the ETERNUS DX80 firmware Updating 11
2. Work flow and cautions in Hot Application (cooperation with operator) 12
2.1. Work flow in Hot Application (cooperation with operator) 12
2.2. Precautions for Hot (cooperation with operator) 13
2.3. Cautions for Hot (cooperation with operator) during the operation 13
2.4. Monitoring software 13
3. Work flow and cautions in Hot (automatic) 14
3.1. Work flow in Hot (automatic) 14
3.2. Precautions for Hot (automatic) 15
3.3. Cautions for Hot (automatic) during the operation 15
3.4. Monitoring software 15
4. Work Flow of Firmware Replacement in Non-Hot Status 16
5. Preparations 17
5.1. Preparation of FST 17
5.2. Acquisition of Firmware 17
5.3. Acquisition of IP address of the device 17
5.4. On the Account of Maintenance Personnel 17
5.5. Confirmation of System Status (External View) before the Execution 18
6. Work procedure 19
6.1. Preliminary Confirmation at the side of Host 19
6.2. FST Connection 19
6.3. Logon (Start GUI) 20
6.4. Check System Status (GUI) prior to the operation 22
6.5. Start of maintenance work 28
6.6. Download of configuration information 30
6.7. Check of version number of EC Firmware in Working/ Non-Working 31
6.8. Firmware registration 33
6.9. Application in Hot (cooperation with operator) 37
6.10. Hot Application (Automatic) 50
6.11. Non-Hot Application 54
6.12. Confirmation of F/W Ver. No. on Working/Non-Working EC after Application 59
6.13. Confirmation of System Status after Application (GUI) 60
6.14. End of Maintenance Work 61
6.15. Logoff (End of GUI) 63
6.16. Disconnection of FST 64
6.17. Confirmation of System Status (External View) after the Application 64
Chapter 2. Check before Delivery 65
1. Asking Items to Users or SE 65
8
Appendix 1. Operating Conditions 66

Appendix 2. IP Address Setting of FST 67
Appendix 3. Operating Procedures at Host 71
1. Procedures in Host (Windows ETERNUS Multi-Path Driver) 71
1.1. Procedure of Preliminary Confirmation 71
1.2. Procedure of Path Offline Operation 73
1.3. Procedure of Path Online Operation 75
2. Procedure of Host Operation when using ETERNUS Multipath Driver of Linux Version 78
2.1. Operation Procedure of Preliminary Confirmation 78
2.2. Procedure of making a Path Offline 79
2.3. Procedure of making Path Online 80
2.4. Message given at the Hot (Automatic) Application 80
3. Procedure of Host Operation when using ETERNUS Multipath Driver of Solaris Version 81
3.1. Operation Procedure of Preliminary Confirmation 81
3.2. Procedure of Path Offline Operation 81
3.3. Procedure of Path Online Operation 82
3.4. Output message when Hot (Automatic) application is applied 83
Appendix 4. Server Operation when VMware ESX Server is connected 84
Appendix 5. Downgrading the Version of Firmware 85
Appendix 6. Shutdown/Rebooting of Power Supply for the System with GUI 86
Appendix 7. Patches required applying to ETERNUS SF (Middleware) 88
7.1. ETERNUS SF AdvancedCopy Manager 88
7.2. ETERNUS SF Storage Cruiser 89
Appendix 8. CFL Target Modules of each Model (for reference) 90
9
1 Procedure outline
Chapter 1. Procedure of firmware update
1. Procedure outline
1.1. Procedure selection
The features of application mode (procedure) follow below;

(1) Application of Firmware in Hot (under the mode of cooperation with operator)
(Firmware Application in the Working Status)
This is the standard procedure of applying firmware in Hot status.
Operation can be performed under the Multipath connection environment of Windows、Linux、Solaris.
Firmware application can be performed in parallel with Host IO.
(2) Hot (Automatic) Application of Firmware (Hot without Host Access Firmware Application)
Operation can be performed under thefollowing conditions in applying firmware in Hot.
FC Connection under the Multipath connection environment of Solaris or Linux and stop of Host IO
operation.
Note The Hot/Automatic mode in ETERNUS DX60/DX80/DX90 has the same functions as
Hot/normal mode of ETERNUS2000.
(3) Application of Firmware in Non-Hot (Firmware Application by System OFF/ON)
This is a procedure to apply firmware turning the system off. A firmware application can be
performed switching the power of the system OFF/ON.
In upgrading firmware, select the application mode (procedure) in consideration of the following table.
Application mode
Firmware Hot w/o Host Access or System On/Off
Application in the Firmware Application
Class of
Host Connection mode Working Status (Application in No Working Status)
connection
Hot (1)
Hot (2)
(Cooperation with Non-hot (3)
(Automatic)
operator)
Single Path -- -- 3
ETERNUS FC connection 3 -- 3
Multi Path iSCSI connection 3 -- 3
Windows (The connection
constitution of the
SAS connection 3 -- 3
VMware ESX
server is included)
Single Path -- -- 3
ETERNUS FC connection 3 3 3
Multi Path iSCSI connection 3 -- 3
Linux (The connection
constitution of the
VMware ESX
server is included)
Single Path -- -- 3
FC connection 3 3 3
Solaris ETERNUS
iSCSI connection 3 -- 3
Multi Path
Note: 3: Available,
--: Not available
10
1 Procedure outline
1.2. Time Requirement

Necessary length of time (reference) for firmware application of each module is as follows;
z Firmware application (Operation of downloading)

CM Ca. 5 min.
BE Expander Ca. 5 sec. Execution at the same time Ú1
Expander Ca. 5 sec.
z Firmware replacement in Hot Status (Necessary time for old and new Firmware)
Per 1 CM (Including BE Expander) Ca. 5 min. Execution in two groups, 1st & 2nd Ú2
Execution in two groups, 1st & 2nd Ú2
Per 1 Expander group Ca. 10 min. (Time required for replacement is calculated on
the condition of 5 DE)
Ú1 Perform all the targeted modules in the system at the same time
Ú2 Perform dividing two groups (before/after) per module.
1.3. Application of Patches to ETERNUS SF (Middleware)

Application of Correction Patches is required to ETERNUS SF products introduced to the System at the
firmware Upgrading.
Foe details refer to “Appendix 7 Patches required applying to ETERNUS SF (Middleware)”.
1.4. Attention in the ETERNUS DX80 firmware Updating

In the case of the condition in the following, I become the firmware updating by the non-activity.
For details, please refer to follows.
CE Technical Report (TA9C020#xx： About instructions in ETERNUS DX80 Firmware Updating)
A condition
* An ETERNUS DX80 FC-8G model (ET08E21A) wins,
* AIX or HP-UX stands out in a connected server,
* When a firmware improves after V10L31 from V10L11 or V10L20.
11
2 Work flow and cautions in Hot Application (cooperation with operator)
2. Work flow and cautions in Hot Application (cooperation with operator)

In this section, the workflow in Hot (cooperation with operator) (Figure 1) and cautions in the application
are explained.
As to the procedure of operation in cooperation with operator, also refer to the operation procedure in Host
in the Appendix 3 Operating Procedures at Host.
2.1. Work flow in Hot Application (cooperation with operator)

Figure 1: Work flow in Hot (cooperation with operator)
START
FST Connection
Gathering to one-side works of Host path
Logon（ GUI Booting）
(Due to excuting application from the
controller at the slave side, make the path
System status (GUI) check connected to the controller at the slave
side Offline.)
System status (External view) check
Application of firmware for the controller at
Start of maintenance works the slave side to to non-operating side EC.
Start of maintenance works

Separating back works of host path
Version number check of firmware (Make the gathered to one-side path
Online.)
Firmware registration
Firmware application replacement of LAN Cable for FST

(Manual) (Repllace the FST when it is directly
connected to the master controller.
Version number check of firmware

Gathering to one-side works of Host path
System status (GUI) check (Due to excuting application to the
controller once being the master before
System status (External view) check applicationat, make the path connected to
the controller Offline.)
Completion of maintenance works
Application of firmware for the controller
Logoff (GUI completion) once being the master to to non-operating
side EC.
Removing FST
Separating back works of host path
END (Make the gathered to one-side path
Online.)
12
2 Work flow and cautions in Hot Application (cooperation with operator)
2.2. Precautions for Hot (cooperation with operator)

Ú Note: In replacing firmware in Hot, try to perform as much as possible when IO load is very small.
Ú Note: In replacing firmware in Hot, the redundancy of connection path is necessary. In case that a Host,
the connection of which with ETERNUS is single path connection, is existing, the operation will not
be possible.
Ú As to the detailed conditions of operation, refer to “Appendix 1 Operating Conditions”.
2.3. Cautions for Hot (cooperation with operator) during the operation
(1) Be sure to make a preliminary confirmation of Path (Separation of the side to apply and normal
connection of the side not to apply).
(2) In replacement of firmware in Hot, prior to the replacement of firmware of controller (CM), the Cache
mode shall be changed into light through mode internally. The time for the change of mode is variable
according to the I/O load and it takes 20- minutes at maximum. In case it takes more than 20
minutes, time will be out and the replacement of controller firmware will be canceled.
(3) During the replacement operation of firmware, try not to reboot the connected servers. In case that
the server is rebooted during the replacement operation of firmware, the server device can’t be
recognized and may not be built in.
2.4. Monitoring software

In case the following monitoring software is used, it is not necessary to stop the software. But from the
software some messages may be issued during the application of firmware. These messages can be ignored
because the connection to the system is disrupted provisionally but no problem is occurred.
z ETERNUSmgr
¾ Polling with interval of 300 seconds (http communication) and the status of no communication with
the device is detected the status of offline will be notified by mail, registered by log and will be
indicated on top menu.
z Storage Cruiser (Resource Coordinator)

¾ Polling with interval of 1 minute (SNMP communication) and the status of no communication with
the device is detected, the event message ("Connection Timeout") of warning level is issued and the
color of icon changes into gray. In case that the event is associated with Systemwalker Centric
Manager, the event will be notified to the Centric Manager.
¾ When the quality function is in use, the quality information can’t be obtained during the replacement
of firmware. Therefore, the event message ("Performance data re-collecting start") of information
level is issued and the color of P mark of icon changes into yellow. After the completion of the
replacement of firmware, when quality information can be obtained, the event message
("Performance data re-collecting success") of information level is issued and the color of P mark of
icon changes into green.
13
3 Work flow and cautions in Hot (automatic)
3. Work flow and cautions in Hot (automatic)

In this section, the workflow in Hot (automatic) (Figure 2) and cautions in the application are explained.
3.1. Work flow in Hot (automatic)

Figure 2: Work flow in Hot (automatic)
START
FST Connection
Logon（ GUI Booting）
System status (GUI) check
Saving configuration information
Version number check of firmware Halting works of Host IO
Firmware application
(Automatic) Hot replacement of firmware

Re-execution works of Host IO
Logoff (GUI completion)
Removing FST
END
14
3 Work flow and cautions in Hot (automatic)
3.2. Precautions for Hot (automatic)

Note: This procedure is used in replacing firmware as system in itself in Hot. The IO operation of Host
during firmware replacement can’t be guaranteed.
In replacing firmware in parallel with the IO operation of Host, perform the operation with the mode
of “Hot (cooperation with operator)”.
As to the procedure of detailed operation, refer to “Appendix 1 Operating Conditions”.
3.3. Cautions for Hot (automatic) during the operation

(1) Even if Path Switchover (Offline/Online Operation) by way of Management Screen or Command of
Multipath Driver during the Hot Replacement of Firmware is not done, Path Control is executed
thanks to the Path Failover Feature of Multipath Driver.
(2) In replacement of firmware in Hot, the Cache mode of internal controller (CM) shall be changed into
light through mode. The time for the change of mode is variable according to the I/O load and it takes
20- minutes at maximum. In case it takes more than 20 minutes, time will be out and the
replacement of controller firmware will be canceled. I/O
(3) During the replacement of firmware, try not to reboot the connected servers. If the server is rebooted,
the device may not be built in
3.4. Monitoring software

In case the following monitoring software is used, it is not necessary to stop the software. But from the
software some messages may be issued during the application of firmware. These messages can be ignored
because the connection to the system is disrupted provisionally but no problem is occurred.
z ETERNUSmgr
¾ Polling with interval of 300 seconds (http communication) and the status of no communication with
the device is detected the status of offline will be notified by mail, registered by log and will be
indicated on top menu.
z Storage Cruiser (Resource Coordinator)

¾ Polling with interval of 1 minute (SNMP communication) and the status of no communication with
the device is detected, the event message ("Connection Timeout") of warning level is issued and the
color of icon changes into gray. In case that the event is associated with Systemwalker Centric
Manager, the event will be notified to the Centric Manager.
¾ When the quality function is in use, the quality information can’t be obtained during the replacement
of firmware. Therefore, the event message ("Performance data re-collecting start") of information
level is issued and the color of P mark of icon changes into yellow. After the completion of the
replacement of firmware, when quality information can be obtained, the event message
("Performance data re-collecting success") of information level is issued and the color of P mark of
icon changes into green.
15
4 Work Flow of Firmware Replacement in Non-Hot Status
4. Work Flow of Firmware Replacement in Non-Hot Status

In this section, the workflow in “Non-Hot” (Figure 3)
Figure 3: Workflow in Non-Hot
START
FST Connection
Logon (GUI Booting)
Saving configuration information
Firmware application Applying firmware to Non-operating side

(Non-hot) EC
System Power OFF/ON
Logon (GUI Booting)
Removing FST
END
16
5 Preparations
5. Preparations
Prior to the controller firmware application, the followings should be observed;
5.1. Preparation of FST

Please note that the following conditions are required for the FST of ETERNUS;
Browser Microsoft Internet Explorer 6.0/7.0/8.0

Mozilla Firefox 3.0.x/3.5.x/3.6.x
Ú An illustration that is Microsoft Internet Explorer 6.0 is used in this manual.
Please set up as follows from “tool” menu of with Internet Explorer to “Internet option”.
z Specify “confirm when page is shown” at “Overall”, “Internet temporary file” and “Set up”.
z Specify as not using proxy server at “Connection” and “setting of local area network (LAN).
JavaScript and style sheet should be valid.

z Specify “Script”, “Active script” and “Enable” at “Security” “Level Customize”.
5.2. Acquisition of Firmware

Download firmware archive from RIS and copy the firmware archive to any location of FST (Example:
under C: ¥).
z Storage
+ETERNUS_DX60_DX80_DX90_FIRM
+VnnLnn (VnnLnn should be the latest version)
5.3. Acquisition of IP address of the device

IP address of device-side MNT port, which corresponds with FST, cannot be known from appearance since
ETERNUS has no LCD panel. Therefore IP address set at MNT port needs to be gained by SE in charge or
customers in advance.
5.4. On the Account of Maintenance Personnel

This system is provided with the feature of nullifying Account of Maintenance Personnel (f.ce), changing
or deletion of Password for the purpose of security. If any of such operations applied by the user, Logon is not
possible. In such a case ask the user to make Logon.
17
5 Preparations
5.5. Confirmation of System Status (External View) before the Execution

Check the followings by each LED Lamp of the System
z CE: FAULT LED Lamp is off. DISK LED Lamp is on in green/blinking

z DE: FAULT LED Lamp is off. DISK LED Lamp is on in green/blinking
18
6 Work procedure
6. Work procedure
6.1. Preliminary Confirmation at the side of Host

Execute the “Procedure of Preliminary Confirmation” meeting the OS working on Host by referring to
“Appendix 3 Operating Procedures at Host”.
6.2. FST Connection

Use the LAN cable to connect MNT port of the system to FST. For connecting the controller module (CM)
of the system to FST directly, connect the LAN cable to the CM with Master LED ON in green. For the LAN
cable to be connected directly, both types, straight and cross, can be used
(As to the setting method of IP address of FST, refer to “Appendix 2 IP Address Setting of FST”.)
Figure 4: Locations of MNT Port and Master LED
MNT Port
19
6 Work procedure
6.3. Logon (Start GUI)

1) Start up Microsoft Internet Explorer browser on FST and input the IP address of MNT port set up for
ETENUS according to the specified address indicated below to access the system in HTTP. Default
value of IP address of MNT port is 192.168.1.1. Screen in Figure 5.2 is displayed upon normal
completion of HTTP access. Input user name (f.ce) and password as account to logon.
Ú MNT Port IP address may be changed after the installation at site. Check the content in Network
Setting Sheet or confirm to the customer.
Ú In this device, invalidation of account for maintenance staff (f.ce), change or deletion of password can
be performed under the consideration of the security. In case that any operation is already set in
customer side, the logon is impossible. In this case, ask the customer to logon.
Specified address: "http://xxx.xxx.xxx.xxx" (xxx.xxx.xxx.xxx is MNT port IP address)
Figure 5: Start GUI
Input the Account and then Logon
20
6 Work procedure
2) Upon the completion of Logon, the operation of GUI will be possible. The following Figure 6 is an
example of “initial setup” window. As the purpose here is updating firmware, click the “Chancel”
button to see the screen.
Ú “Setup status indication” window may be appeared after the installation at site setup.
Figure 6: Initial setup window
21
6 Work procedure
6.4. Check System Status (GUI) prior to the operation

1) Check the overall status lamp and overall status of the system. Check if the overall status lamp turns
on in Green and overall status is Normal in upper left on the GUI screen. (Figure 7)
2) Check each part in the system. Click “System status indication” of GUI. Access to the tree for parts
composing the system and make each part indicated. (Click to the + located at the left side of each
part.)
Figure 7: Overall Status Lamp Status Confirmation Window
Overall Status Lamp/ Status
Tree of composing parts of the system
22
6 Work procedure
3) Accessing to the tree of composing parts, the indication at the left side of the screen will be appeared
(Figure 8) Check if the lamp indicating the malfunction of each part is not blinking. In case that the
lamp is not blinking, the system shall be normal. Clicking to the part, the detailed information will be
indicated at the right side of the screen enabling the check of detailed status.
Ú In the tree of composing parts, blue lamp may be indicated in Disk. This means the Disk not in use
without setup of RAID Volume and HS. This does not mean any problem. Overall Status Lamp
shall be indicated in green and overall Status will be indicated as normal.
Ú In detailed window at right side, the icon of enclosure may be indicated with blue lamp. This
means that unused disk, the volume and HS of which is not set, is mounted. This is not a problem.
The enclosure indicated by blue lamp will be indicated as Undefined. This does not mean any
problem.
Figure 8: Check of parts inside the device (normal)
“Undefined” is shown
including “not in use”
Tree of component inside the system Detailed information of component
23
6 Work procedure
4) If a failing component exists in the system, Overall Status Lamp will be indicated in color not in
green and overall Status will be indicated as “No Other Normal”. (Figure 9) To the failed component
and device to which failed component is mounted are indicated by the lamp of failure in the tree of
comments at the left side of the screen. By clicking to the failed component, you can check the
detailed status because the detailed information will be indicated at the right side of the screen. In
this case, after the maintenance of failed component, restore the setup.
Figure 9: Check of parts inside the device (abnormal)
Overall Status Lamp/ Status
Tree of component inside the system Detailed information of component
24
6 Work procedure
5) Check the status of RAID Group and RAID Volume. Click to “Indication of the status of RAID Group”
and “Indication of Volume status” at GUI. Check the status indicated in the list of each status. Check
if the status is as follows; (Figure 10) to (Figure 14)
z Rebuild/Copyback is not in operation. (Figure 10), (Figure 11)

(During the operation, Rebuild or Copyback will be indicatded in the item of status at the
“Indication of the status of RAID Group” and the status of progress is indicated at the status item
of Rebuild/Copyback.
z Volume Format is not in operation. (Figure 12)
(During the operation, the status of progress is indicated at the format of the status in “Indication
of Volume status”)
z Concatenation is not in operation. (Figure 12)
(During the operation, the status of progress is indicated at the section of format progress in
“Indication of Volume status”)
z Logical Device Expansion is not in operation. (Figure 13)
(During the operation, the status of progress is indicated at the section of expansion progress of
“Indication of the status of RAID Group”.
z Migration is not in operation. (Figure 14)
(During the operation, the status of progress is indicated at the section of format progress or at the
section of migration progressing “Indication of Volume status”)
z RAID Group Status is available. (Figure 12), (Figure 13), (Figure 14)
(Available will be indicated at the section of status in the “Indication of the status of RAID Group”)
Figure 10: Check of Rebuild status
Rebuild progress
RAID Group Status
25
6 Work procedure
Figure 11: Check of Copyback status
Copyback Progress
RAID Group Status
Figure 12: Check of Format status
Format or Concatenation progress
26
6 Work procedure
Figure 13: Check of LDE status
LDE Progress
Figure 14: Check of migration status
Migration progress
27
6 Work procedure
6.5. Start of maintenance work

1) Start the maintenance work to keep the system in operation mode. Click “Start/end maintenance
work” on the “Maintenance” of GUI. After a screen of “Start/end maintenance work” is appeared, click
the “Start button”. (Figure 15)
Figure 15: Start of maintenance work
2) Check window is appeared. (Figure 16) Click “OK” Button.
Figure 16: Confirmation on the Start of Maintenance Work
28
6 Work procedure
3) The status that the system is maintained is indicated. (Figure 17)
Figure 17: Indication of maintenance
4) Check if the operation mode of the system is “Maintenance” in the system status window. (Figure 18)
Figure 18: Indication of maintenance
29
6 Work procedure
6.6. Download of configuration information

1) If a system fails, save the system configuration information to be used at the restoration of the
system. Click “Export Configuration” from “Log/Dump” at GUI. (Figure 19) Clicking to the Download,
the information will be saved.
Figure 19: Start to download configuration information
2) A screen to designate the place where configuration file is stored is appeared. (Figure 20) Save the
configuration file at any place in FST.
Figure 20: A screen to designate for the configuration file
30
6 Work procedure
6.7. Check of version number of EC Firmware in Working/ Non-Working

1) Check of version number of EC controller Firmware of system in Operation/Not in Operation.
First, check if the system is in maintenance mode. Click to “System status indication” in “Status
indication” of GUI. Check that “Maintenance” is indicated. If the “Active” is indicated, start the
maintenance work. After the confirmation of the maintenance operation mode, click to the
“Maintenance” of GUI. (Figure 21)
Figure 21: Confirmation of operation mode
Click “Maintenance”
Confirmation of “Maintenance”
31
6 Work procedure
2) Clicking to “Controller Firmware Update” in “Firmware Maintenance” the following screen is

appeared. (Figure 22)
In controller firmware information section, the Current Firmware and the Firmware to be active for
next time can be confirmed.
In the Setting Column for upgrading Controller Firmware, Version No. of up to 3 generations of
registered firmware and the Working Status (status of EC#1 and EC#2) can be confirmed.
Displayed are the status of EC#1 and EC#2. The EC displayed as “Active” is the working side and the
EC displayed as “Active at next cycle” is the Non-working EC which starts working at the next
PowerOn.
Ú In Figure 22, EC#1 is in operation (shown in “Active”), EC which will be active at the next Power
Cycle is shown “Active at next Power Cycle”. EC#2 is not in operation (not described).
And the EC#1 and EC#2 are applied to overall version number V10L20-0000.
Figure 22: Confirmation of registered Controller Firmware
Overall version No. of Firmware
This shows EC#2 is not in operation
EC#1 is in operation and in

operation of next power cycle
Registered firmware version No.
32
6 Work procedure
6.8. Firmware registration

1) The screen of Apply Controller Firmware is indicated. (Figure 23) In “Firmware Version” is indicated
registered Control Firmware registered in System Disk. In registering new Controller Firmware to
System Disk, click “Reference button” and designate the place (in the folder which are connected in
FST) where firmware archive is located.
Ú The same version number of controller firmware already registered can’t be registered for the
different generation.
Figure 23: Storage of Controller Firmware & Selection of Registerable Generation
Click “Reference button (See)”
Registerable generation
2) Select the registered generation and click to the “Next” button. The registerable generations to be
selected are the following;
z Generation not registered
“Not Registered” in “Status”.
or
z Generation of Controller Firmware other than the one used by Working/Non-Working EC.
(Generations EC1 and EC2 is not displayed in (“Working”) Column.
Upon the Display of the message as given below, click “OK” and go forward.
Figure 24: Check of overwriting of Controller Firmware
33
6 Work procedure
3) A screen of Firmware archive file selection is indicated (Figure 25). Select Firmware archive file and
click “Open” button.
Figure 25: A screen of firmware archive file selection
4) Specify the firmware archive location and then click “Next” button.
Figure 26: Start of Controller Firmware registration
34
6 Work procedure
5) A confirmation screen is indicated. (Figure 27) Click “OK” button.
Ú In the case of selecting “Upgrading Mode” for “Registration and Application” at Figure 23, by
clicking “OK” here leads to the selection from the list as below to meet the purpose.
“6.9 Application in Hot (cooperation with operator)”
“6.10 Hot Application (Automatic)”
“6.11 Non-Hot Application”
Figure 27: Check of controller firmware registration
6) A screen of completion of registration is indicated. (Figure 28)
Figure 28: Completion for registration of Controller Firmware
35
6 Work procedure
(7) Select “Apply Controller Firmware” and the check if the controller firmware is registered duly to the
designated generation and confirm the version No. by firmware versions numbers and check if it is
“Valid” by status. Then the registration of controller firmware is completed. (Figure 29)
Figure 29: Confirmation of Registered Controller Firmware
Check if version No. is correct and the status is valid
In case of continuous applying the firmware, select “only Update” of “Update Mode”, and click “Next”
here leads to the selection from the list as below to meet the purpose..
“6.9 Application in Hot (cooperation with operator)”
“6.10 Hot Application (Automatic)”
“6.11 Non-Hot Application”
36
6 Work procedure
6.9. Application in Hot (cooperation with operator)

1) Select and set up the information to be applied in the section of “set up of controller firmware update”
in the screen of “Apply Controller Firmware”. (Figure 30) Select “Active” in “operation mode” and
select “Manual” in “Dynamic Apply (switch host path operation) mode click the “Apply Firmware”
button and click “OK” button in reconfirmation screen.
Figure 30: Selection of active/ manual (cooperation with operator)
Figure 31: Application check
37
6 Work procedure
2) A screen of progress in Firmware application is indicated. (Figure 32) When the application progress
“Completes”, the application process (Firmware loading to EC of not operation) will end.
Figure 32: Progress of firmware loading to EC of not operation
Target module
Processing status of target module
38
6 Work procedure
3) In the “Message” section of “Apply Controller Firmware” screen, the application order of firmware and
information of work to disable/enable path regarding the application are indicated. (Figure 33) If you
save the application order of controller, click “Save” button In case you find no problem in the content
of the Message, click the “Next” button. To cancel the application process of controller firmware in Hot,
click the “Cancel” button.
Ú The work starts from the Controller on the side of Slave (shown as “First” in the Fig.). Be careful of
it at the time of breaking Pass, as it not necessarily starts with CM #0.
Figure 33: A confirmation screen of application order during controller firmware application in Hot
39
6 Work procedure
(Reference)
In case that drive enclosure is mounted, the progress of the first half of component (EXP) is updated
in the progress of firmware. The progress status of the first half of component (components in CM)
still is in preparation.
Figure 34: Progress in case a drive enclosure is mounted
40
6 Work procedure
4) In the “Message” section of “Controller Firmware Update” screen, a message instructing to disable
the path connected to the relevant controller will be indicated. (Figure 35)
Execute the “Pass Offline Procedure” corresponding to OS working on the Host by referring to
Disable the relevant path, after the check of the completion of this work, click the “Next” button. To
cancel the application process of controller firmware in Hot, click the “Cancel” button. Then the
confirmation of path will be performed.
Figure 35: A screen to disable the first half of path during firmware application in Hot
Figure 36: A screen to disable the first half of path during firmware application in Hot
41
6 Work procedure
5) If the path is not in offline in item 4), a “Message” that the path is connected may be indicated in a
screen of “Controller Firmware Update”. (Figure 37) This indicates that from WWN Host indicated in
the relevant controller side, I/O is received. After the confirmation that the work to disable the path is
completed, click the “Next” button.
In switching the path automatically by multipath driver at the Host side, the work can be performed
forcibly clicking to “Forcible” button. To cancel the application process of controller firmware in Hot,
click the “Cancel” button.
Figure 37: A screen-2 to disable the first half of path during firmware application in Hot
6) By clicking to the “Next” or “Forcible” button, the progress of switching of firmware is indicated.
The progress of the first half of component (component in CM) is updated.
Figure 38: A screen-2 to disable the first half of path during firmware application in Hot
42
6 Work procedure
7) If the replacement in Hot of firmware in the first half of the controller is performed normally, in the
section of “Message” in the screen of “Controller Firmware Update” a message requiring the
connection of the path, which was disabled, will be indicated. (Figure 39)
Execute the “Pass Online Procedure” corresponding to OS working on the Host by referring to
After the confirmation that the work to connect the path is completed, click the “Next” button. To
cancel the application process of Firmware in Hot, click the “Cancel” button.
Figure 39: A screen to connect the first half of path during firmware application in Hot
43
6 Work procedure
8) In the section of “Message” in the screen of “Controller Firmware application process in Hot”, a
message requiring the replacement of LAN cables. After the confirmation of the lighting of MST LED,
replace LAN cables.
Figure 40: A screen of LAN Switchover during controller firmware application process in Hot
Ú Note: In case it is possible to get access to LAN Ports of both CMs over the Switching Hub, etc. from
FST, changing of LAN Cable is not required. Depending on the network environment, there are
cases where ARP Table of FST not changed, Under such circumstances, there are cases of Message
as shown below appears upon clicking “Continue” Button interrupting the communication with the
System for a certain period of time.
Message:
Cannot make connection with the System.
After changing the LAN Cable on CM Module with LED turned On, press
[Continue] Button and restart Hot Application.
After a while communication becomes possible but in case IP Address of FST and the System are
on the same Network, can immediately start communication ay clearing ARP Table of FST.
Method of clearing ARP Table

Start up the Command Prompt of FST (Windows) and enter as given below.
[Deletion of ARP Table]
Deletion of System IP only: arp -d System IP
Total Deletion: arp -d
Method of displaying ARP Table
Start up the Command Prompt of FST (Windows) and enter as given below.
[Display of ARP Table]
Total Display: arp -a
44
6 Work procedure
9) When the Button “Confirmation of Connection” enabled after a while, click the Button.
Figure 41: Screen of LAN Switchover during Hot Application of Firmware
10) Upon normal completion of Connection, “Next” button is enabled. Click it to go further.
Figure 42: Screen of LAN Switchover during Hot Application of Firmware
45
6 Work procedure
11) In the “Message” Column of “Controller Firmware Update” Screen is given the Message instructing
the Break of Path connected to the target Controller.
Execute the “Pass Online Procedure” corresponding to OS working on the Host by referring to
After confirming the completion of Path Break, click “Next” Button. To discontinue the work of
Controller Firmware Hot Application, click “Cancel” Button.
Figure 43: Screen of Path Break during Hot Application of Firmware
Figure 44: Screen of Path Break during Hot Application of Firmware
46
6 Work procedure
12) In case the Path is not offline at 11) above, Message of Path Connection may be given in the
“Message” Column of “Controller Firmware Update” Screen (Figure 45). It implies that I/O is
received from the Host of WEN displayed at the side of target Controller. Give further instruction to
SE for the breaking of the targeted Path. After confirming the Path Break, click “Next” Button.
In the case of automatic Path Switch-over by Multi Path Drover of Host side, it is possible to
forcefully precede the work by clicking “Compulsory Continuation” Button. To discontinue the work of
Controller Firmware Hot Application, click “Cancel” Button.
Figure 45: Screen 2 of Path Break during Hot Application of Firmware
13) By clicking “Next” Button, the Progress of Firmware Switch-over is displayed.

Renewal is given on the Progress with further components (components within CM) is shown.
Figure 46: Screen 2 of Path Break during Hot Application of Firmware
47
6 Work procedure
14) When the latter work of Hot Switch-over of Controller Firmware, a message instructing the
reconnection of broken Path to the relevant Controller comes up in the “Message” column of
“Controller Firmware Update” Screen (Figure 47).
Execute the “Pass Offline Procedure” corresponding to OS working on the Host by referring to
After confirming the completion of Path Connection, click “Next” Button.
Figure 47: Screen of back Path Connection during Hot Application of Firmware
15) Upon the completion of Controller Switch-over by the end of upgrading the components in the back,
Screen of (Figure 48) comes up. “Completed” with all Components indicates that the process of
Firmware Update is completed.
Figure 48: Screen of front Path Connection during Hot Application of Firmware
48
6 Work procedure
(Reference)
In case Drive Enclosure is mounted, the Renewal of back components (EXP) is processed after the
completion of the work with back Components (in CM).
Figure 49: Progress when Drive Enclosure is mounted.
18) Upon normal completion of Hot Replacement of Firmware, a Message “Process is normally
completed” in the “Result” Column on the Screen of Firmware Hot Application Process as shown in
(Figure 50).
Figure 50: Screen 2 of Hot Application of Firmware
Confirm the Message.
Please proceed to “6.12 Confirmation of F/W Ver. No. on Working/Non-Working EC after Application”.
49
6 Work procedure
6.10. Hot Application (Automatic)

1) Select/Set the Information to apply at the column of “Controller Firmware Application Information”
of “Controller Firmware Update” Screen (Figure 51). Select “Hot” for Execution Mode, set “Setting
Time” for the Waiting Time after the establishment of Path and select “Automatic” for Hot
Application Mode. Finally click “Firmware Update” Button and click “OK” on the Reconfirmation
Screen.
Ú Note: Waiting Time after the Establishment of Path

During the Hot Replacement of Controller Module (CM), the Host Interface link down/up. After the
Linkup, set the time for Host to recognize the Volume of ETERNUS. Note that there is the
possibility of Host I/O stops if the Time set is too showt.
During Hot application, Message will be issue on the Host. On the Message refer to the “Appendix
3 Operating Procedures at Host” corresponding to OS working on the Host by referring to “3.4
Output message when Hot (Automatic) application is applied”.
Figure 51: Selection of Hot/ Automatic (without cooperation)
Figure 52: Confirmation Screen
50
6 Work procedure
2) This Screen comes up. This Progress of Firmware Switch-over (1/2) shows the progress of applying
Controller Firmware to each Component (Write-in of Firmware to Standby Flash ROM) is shown.
Figure 53: Firmware Loading process to Non-working EC
Target Module
Progress with Target Module
51
6 Work procedure
3) Hot Replacement is automatically carried on. At this Progress of Firmware Switch-over (2/2), the
Progress of switching Firmware at each Component (Switch-over of Active Flash ROM by Reboot) is
renewed. (Figure 54)
Figure 54: Screen 1 of Hot Application of Firmware under Process
52
6 Work procedure
Ú If the work is done by connecting LAN Cable directly from FST to ETERNUS, ignore the message
given in the Screen as below. It is not necessary to reconnect the LAN Cable to MNT Port of
another CM.
Figure 55: Status of LAN Cable
4) Upon normal completion of Hot Application with Controller Firmware, Screen reporting the
Completion comes up (Figure 56).
Figure 56: Screen 2 of Hot Application of Firmware under Process
Proceed to “6.12 Confirmation of F/W Ver. No. on Working/Non-Working EC after Application.
53
6 Work procedure
6.11. Non-Hot Application

1) Select and set up the information to be applied in the section of “Set up of controller firmware
update” in the screen of “Controller Firmware Update”. (Figure 57) Select “Statistically” at “Apply
Mode” click the “Update Firmware” Button and click “OK” Button at the further Application
Confirmation Screen.
Figure 57: Selection of Non-Hot application
Figure 58: Confirmation of Application
54
6 Work procedure
2) The Progress is displayed in the Column of Firmware Upgrade Progress (Figure 59). Upon the
Display of Completion, Application Process (Firmware Loading to Non-Working EC) is completed.
Figure 59: Screen 3 of Application of Firmware under Process
Figure 60: Screen 3 of Application of Firmware under Process
55
6 Work procedure
3) Confirm on the “Controller Firmware Update” Screen that the Firmware applied to the Non-Working
side is correct by “Firmware Version No.” column, and then confirm also that Next Working at
Power-ON is displayed for the EC of Non-Working side.
Figure 61: Firmware Screen 6
Confirm that the Firmware of Correct Version No. is applied the

Non-Working EC and that there is display of Next Working.
(Reference) Reboot Operation by GUI Menu

Select in the order of “Utility” - “System Power Supply Off/On” and click “Reboot”. The DC Power
Supple of the System turned off in ca. 1 min. upon this operation (This is same as the operation by
the Power Button on the Panel.). Further after ca. 1 min. of Off Status, it turns to On. (This is same
as the operation by the Power Button on the Panel.).
As to the Operation Method, refer to “Appendix 6 Shutdown/Rebooting of Power Supply for the
System with GUI”.
When this operation is done, the operation under 6) is not required.
56
6 Work procedure
4) In order to execute Power OFF/ON to the System, execute Log Off. Click “Log Off” at GUI (Figure
62).
Ú Depending on the necessity, execute Power Off/On or Recognition Work at the Connected Server
meeting the Power Supply Off/On of ETERNUS DX System.
Figure 62: Start of Logoff
5) Screen for Confirming Log Off appears (Figure 63). Click “OK” Button. CUI terminates.
Figure 63: Confirmation of Logoff
57
6 Work procedure
6) In order to change Working/ Non-Working EC by Off/ On of the System, operate the System Power
Button from the Panel of CE (Controller Enclosure).
Off Operation: Press the Power Button of CE Panel for a longer time (ca. 4 sec.).
On Operation: Press the Power Button of CE Panel.
Execute the On Operation after the lapse of 3 min. upon Ready LED went off at Off Opertion.
7) Confirm that Master LED is ON at Controller connected with LAN Cable. In case MST LED is Off,
connect LAN Cable to the MNT Port of Controller with Master LED ON.
8) By starting up Microsoft Internet Explorer Browser on FST and enter MNT Port Address set at
ETERNUS as the Address designated as below and make an HTTP Access to the System.
Designated Address: "http://xxx.xxx.xxx.xxx" (“xxx.xxx.xxx.xxx” is IP Address of MNT Port.)
58
6 Work procedure
6.12. Confirmation of F/W Ver. No. on Working/Non-Working EC after Application

1) Select “Firmware Maintenance” at “Maintenance” and click “Controller Firmware Upgrade” (Figure
64). Version No. of Working Firmware and Next Start Firmware can be confirmed at the Column of
“Controller Firmware Information”.
At the “Upgrading of Controller Firmware”, up to 3 generations of Firmware Version No. to register
and the working status (Status of EC#1 and EC#2) can be confirmed.
Displayed as working represents the status of EC#1 and EC#2 and the side (EC) shown as “Working”
being the EC of Working Side and the side shown as [Working Next] being the EC working next at
the Power On. The side (EC) is the EC of Non-working side.
Check that the displays the correct Version Nos.
Ú In the case of (Figure 64), EC#2 is the working side (shown as [Working]). It is also the EC working
next (given as [Next Working EC]). EC#1 is Non-Working (not shown).
To EC#1 is applied with Ver. No. V10L20-0000 and to EC#2 is applied with Ver. No. V10L31-0000.
Figure 64: Firmware Screen 7
Firmware Version No.
Working/ Non-Working EC &

Working EC at the Next
Power ON
Ú Note:
When failed with the process of Controller Application, there are cases of Working EC being
same as the EC confirmed at [Confirmation of F/W Ver. No. on Working/Non-Working EC after
Application]. In this case, apply [Confirmation of System Status (External View) after the
Application] after maintaining erred parts at [System Status (GUI) after application] and
execute again by following the applicable mode of either [Application in Hot (cooperation with
operator)] or [Hot Application (Automatic)].
59
6 Work procedure
6.13. Confirmation of System Status after Application (GUI)

1) Confirm the Total Status Lamp and Total Status of the System. Confirm that the Total Status Lamp
on upper left of GUI Screen is Green and the Total Status is Normal (Figure 65).
Figure 65: Total Status Lamp/Total Status Confirmation Screen 3
Total Status Lamp/ Status
60
6 Work procedure
6.14. End of Maintenance Work

1) At the completion of Firmware Application Work, set End of Maintenance Work. Click “Start/ End of
Maintenance Work” at “Maintenance” of GUI. Upon the display of Screen [Start/End of Maintenance],
click [End] Button. (Figure 66)
Upon the display of Screen [Start/End of Maintenance], click [End] Button.
Figure 66: End of Maintenance Work
2) Confirming screen appears (Figure 67). Click “OK” Button.
Figure 67: Confirmation of End of Maintenance Work
61
6 Work procedure
3) Status of End to the Maintenance Work of the System is displayed. (Figure 68)
Figure 68: End Notice of Maintenance Work
４) Confirm on the Screen of “System Status Display” that the System Operation Mode is being “Active”.
Figure 69: Confirmation of End Status of Maintenance
Confirm the Active
62
6 Work procedure
6.15. Logoff (End of GUI)

1) Apply Logoff. Click. “Logoff” of GUI. (Figure 70)
Figure 70: Start of Log Off
2) Confirmation Screen comes on display. (Figure 71) Click “OK” Button.
Figure 71: Confirm the Logoff
63
6 Work procedure
6.16. Disconnection of FST

Disconnect FST.
6.17. Confirmation of System Status (External View) after the Application

1) Confirm the followings by the External View.
z CE: FAULT LED Lamp is off. DISK LED Lamp is on in green/blinking
z DE: FAULT LED Lamp is off. DISK LED Lamp is on in green/blinking
Ú Note:
When failed with the process of Controller Application and in case the Working EC is same as confirmed
by “Check of version number of EC Firmware in Working/ Non-Working” at “Confirmation of F/W Ver. No.
on Working/Non-Working EC after Application”, execute again from “Application in Hot (cooperation with
operator)” or “Hot Application (Automatic)” depending on the Mode to apply.
64
Chapter 2. Check before Delivery
In this chapter, final operating items and asking items prior to making delivery to users or SE are
described.
1. Asking Items to Users or SE

Asking items to users or SE are described in this section.
When halting the following monitoring software, resume it.

z ETERNUSmgr
z Resource Coordinator
After the above procedures, all of works based on the revising procedures are completed
Appendix 1 Operating Conditions
Appendix 1. Operating Conditions

For performing the application of Hot Controller Firmware (execution mode), the required items are
shown as follows. For the concrete judging method, refer to “Work flow and cautions in Hot (automatic)“,
“Work flow and cautions in Hot Application (cooperation with operator)“.
For the environment of Windows ETERNUS multi driver, do not fail to perform the cooperation with
operator mode.
Conditions Procedures Guard Schedule for

Function Releasing
Conditions
After restoring with hot maintenance, apply the | No
No alarm components
controller firmware.
LU formatting is not After completing formatting, apply the controller | No
executed. firmware.
Rebuild/Copyback is not After completing Rebuild/Copyback, apply the | No
executed. controller firmware.
Logical Device Expansion After completing Logical Device Expansion, apply | No
is not executed. the controller firmware.
I/O loading of the server is low. ° No
[Notes] In the case that the system errors occur
I/O loading of the server is when loading is high at batch treating or backup
low. treating, the volume separating failure may occur.
Wherever possible, execute at the status that I/O
loading is low.
|: There is a guard function during executing hot replacement of firmware.
°: There is not a guard function during executing hot replacement of firmware.
66
Appendix 2 IP Address Setting of FST
Appendix 2. IP Address Setting of FST

This procedure is described using Windows XP and Internet Explorer 6.0.
(1) Boot up the Windows and open “Control Panel” of “Start”.
(2) Click “Network and dialup connection” on the control pane.
Figure 72: Control Panel (Select network and dialup connection)
Click here
(3) Select “Local area connection”.
Figure 73: Network and Dialup Connection
Click here
67
(4) Select and click “Properties” of General in the local area connection status screen.
Figure 74: Local Area Connection Properties
Click here
(5) Select “Internet protocol (TCP/IP)” on the local area connection property screen and click
“Properties” button.
Figure 75: Local Area Connection Properties
1. Select here
2. Click here
68
(6) Check “Use following IP address” as shown in Figure 76, and input “192.168.1.10” in “IP Address”
and “255.255.255.0” in “Subnet mask”.
(7) Click “OK” button and reflect the change of IP address.

Figure 76: Internet Protocol Properties
2. Input the address
1. Select here
(8) Click “OK” button to close “Local area connection properties” screen as shown in Figure 77. “Local
area connection status” will close.
(9) Click “Internet option” on the control panel.
Figure 77: Control Panel (Selection of Internet Option)
Click here
69
(10) Select “Connection” tab on the Internet property screen as shown in Figure 78 and click “LAN
setting” button.
Figure 78: Internet Properties
1. Select here
2. Click here
(11) In the Local Area Network (LAN) setting, uncheck the “Proxy for LAN” of the proxy server. Finally,
click “OK” button.
Figure 79: Local area network (LAN) setting: No proxy server
1. Uncheck here
2. Click here
(12) In Figure 79 “Internet Properties”, click “OK” button to close.
70
Appendix 3 Operating Procedures at Host
Appendix 3. Operating Procedures at Host
1. Procedures in Host (Windows ETERNUS Multi-Path Driver)

With Windows Version, execute [Hot Application (Cooperation with Operator)]. [Hot Application
(Automatic)] is not executable.
1.1. Procedure of Preliminary Confirmation

1) Select [ETERNUS Multipath Manger] in the Start Menu and open the Screen of ETERNUS
Multipath Manager.
Figure 80: Startup of ETERNUS Multipath Manager
2) Click “CAID and Connecting Position” on the Help Menu of ETERNUS Multipath Manager and click
“ETERNUS DX60, DX80,” in the Screen displayed.
Figure 81: Help Display
71
Confirm on the Display of ETERNUS Multipath Manager that CAID of CM for both CM0 and CM1
are on Display. The relation of CAID and CM can be confirmed on the Screen for CAID and
Connecting Position shown under 2).
Figure 82: Confirmation of CAID and Connecting Position
Confirm that CM of CAID

for both CM0 and CM1 are
on display.
3) Point the Cursor to Server in the Screen of ETERNUS Multipath Manager and click “Path
Diagnosis” of “Tool Menu”. Diagnostic Data is sent to each Path between Server and Disk Array
System for confirming the connection status.
Figure 83: Execution of Path Diagnosis
72
4) Confirm that “Path Diagnosis is normally completed” is displayed.
Figure 84: Confirmation on the result of Path Diagnosis
1.2. Procedure of Path Offline Operation

1) (This is the Screen for the instruction of making either path, CM0 (Chapter 6, Fig. 6-40) or CM1
(Chapter 6, Fig. 6-32), Offline. The example below is the Screen for the instruction of making Offline
the Path on the side of CM1.)
Figure 85: ETERNUS Web GUI Path Breaking Screen 1
2) Make the Path of CM displayed on the above Screen at Offline on the Screen of ETERNUS Multipath
Manager. Select Offline by pointing and clicking the Cursor to the Path for making it Offline.
(Here is the side of CM1 made Offline. In the case of DX60/DX80/DX90, CAID=02 is CM1.)
Figure 86: Selection of Offline Path with ETERNUS Multipath Manager
Makes Offline the Path of

CAID=02 corresponding
CM1.
Confirm that CM of CAID for both CM0 and CM1 are on display.
73
3) Click “OK” on the Confirmation Screen and confirm that the Signaling Icon of Path made Offline
disappeared.
Figure 87: Offline Process of ETERNUS Multipath Manager
4) Click “Next” on the ETERNUS Web GUI Screen.
Figure 88: ETERNUS Web GUI Path Break Screen 2
74
1.3. Procedure of Path Online Operation

1) Confirm that the Screen as below is displayed on the ETERNUS Web GUI Screen.
This is the Screen for the instruction of making either path (CM0 (Chapter 6, Fig. 6-44) or CM1
(Chapter 6, fig. 6-36). The example below is the screen for making Offline the Path on the side of
CM1.)
Figure 89: ETERNUS Web GUI Path Connection Screen 1
2) On the screen of ETERNUS Multipath Manger, make the Path Online which was made Offline at
“1.2 Path Offline Procedure”. Point the Path to make Online by Cursor, right-click it to select “Online”.
Click “OK” at the Confirmation Screen and confirm that the Signaling Icon on the side of Path made
Online is displayed.
Figure 90: Online Procedure of ETERNUS Multipath Manager
75
There are cases of showing only the sigle CM path as below at 2).
Figure 91: Confirming the Result of ETERNUS Multipath Manger Online Execution
Shows only the CM

of single side.
In this case have Path of both CMs displayed through scanning operation at Device Manager. For
Scanning Operation, point the “Disk Drive” of “Device Manager” by the Cursor, right click it, then
click “Scan of Hardware Change”.
Figure 92: Device Manager Path Scan Process
3) Execute Path Diagnosis on the Screen of ETERNUS Multipath Manager and confirm that there is no
problem with the paths of both CMx.
Figure 93: Confirmation of ETERNUS Multipath Manger Path
76
4) Click “Next” on the ETERNUS Web GUI Screen of 1).
Figure 94: ETERNUS Web GUI Path Connection Screen 2
77
2. Procedure of Host Operation when using ETERNUS Multipath Driver

of Linux Version
2.1. Operation Procedure of Preliminary Confirmation

1) Confirm that number of passes from the Server are connected to different CMs of ETERNUS Disk
Array System.
Execute the Command “/opt/FJSVmpd/bin/iompadm info”.
Examples of “Hot Application”

# /opt/FJSVmpd/bin/iompadam info
IOMP: vhba0
Element:
DISK: ETERNUS_DXL- 000B4F-0000-0000 (sdb)
PATH:
sdb 0000:04:00.0 active "online" 10, 10, 0
sdb 0000:03:00.0 standby "online" 11, 11, 2
“PATH:” and subsequent entries show the status of the path every other line. The last three figures of
each line show “Group No.”-”Replacing Unit No.”-”Adapter Port No.”.
Their relationships with the ETERNUS DX60/DX80/DX90 FC Interface Model are as given in the
table below.
When the groupo number has two kinds or more, it can be checked of being connected to the
different.
Table 1: Relationships of CM and Group Nos., etc.
Unit of Group No. of Replacing Unit No. of Adapter Port
CM#0 10 10 0, 1
CM#1 11 11 2, 3
Examples of “Hot Application” being ruled out.

# /opt/FJSVmpd/bin/iompadam info
IOMP: vhba0
Element:
PATH:
All the Paths have the identical Group No., which shows that they are connected to the same CM. In
this case Work of Hot Application is not possible.
78
2) Confirm that all the Paths are in the status of Online.

Execute the Command as below and confirm that nothing comes on display.
# /opt/FJSVmpd/bin/iompadm info | egrep “(fail|stop|warning)”

#
When the status of the Path is “fail”, “stop” or “online warning”, work of Hot Application for
Controller Firmware is not possible. Check the connectivity of the Path.
2.2. Procedure of making a Path Offline

1) Confirm the Name of Disk Device and the No. of Adapter Port No. to be made Offline.
# /opt/FJSVmpd/bin/iompadm info
IOMP: vhba0
Element:
PATH:
In the above examples, the part boxed by Blue Line is the Name of Disk Device for “/dev/sdb”.
In the case of Controller for upgrading its Firmware is CM#0, check the line of Group No. being 10.
In the above case, “0” is the No. of the Adapter Port.
In the case of Controller for upgrading its Firmware is CM#1, check the line of Group No. being 11. In
the above case, “2” is the No. of the Adapter Port.
2) Execute by specifying the Name of Disk Device and Adapter Port No. as above to the Command
“/opt/FJSVmpd/bin/iompadm change g”. Shown below is the example of such command for making
Offline the Path on the side of CM#1.
# /opt/FJSVmpd/bin/iompadm change g /dev/sdb 2
3) Confirm that the Path has become Offline status.

IOMP: vhba0
Element:
PATH:
sdb 0000:03:00.0 stop "stop by command" 11, 11, 2
Confirm as above that the status of the Path made Offline is given as “stop”.
79
2.3. Procedure of making Path Online

1) Confirm the Name of Disk Device and the No. of Adapter Port No. to be made Online.
IOMP: vhba0
Element:
PATH:
sdb 0000:03:00.0 stop "stop by command" 11, 11, 2
Use the Name of Disk Device and the Adapter Port No. of the Path, whose status is “stop”.
2) Make the Path Online.

Execution by specifying the Name of Disk Device and Adapter Port No. confirmed at under 1) above
to the Command “/opt/FJSVmpd/bin/iompadm restart groupmodule”. Shown below is the example of
such command for making Online the Path on the side of CM#1.
# /opt/FJSVmpd/bin/iompadm restart g /dev/sdb 2
3) Confirm that the Path has become Online status.

IOMP: vhba0
Element:
PATH:
Confirm as above that the status of the Path made Offline is given as “online”.
2.4. Message given at the Hot (Automatic) Application

At the time of Hot (Automatic) Application, there may comes up a message as below. There is no problem
with the operation. (In the positions of “%u” are given figures).
SCSI%u (%u,%u,%u): ERROR=0x1: no connect
80
3. Procedure of Host Operation when using ETERNUS Multipath Driver

of Solaris Version
3.1. Operation Procedure of Preliminary Confirmation

1) Confirm that all the paths are Normal.
Execute the Command as below and confirm that there comes nothing on the display.
# /usr/opt/FJSViomp/bin/iompadm -c mplb info | egrep “(fail|stop|warning)”
When the status of the Path is “fail”, “stop” or “online warning”, work of Hot Application for
Controller Firmware is not possible. Check the connectivity of the Path.
3.2. Procedure of Path Offline Operation

1) Confirm the Physical Node Name of the Path to be made Offline.
Execute the Command as below.
# /usr/opt/FJSViomp/bin/iompadm –c mplb info

/dev/rdsk/c2t0d0s2 online active block “good status with active
[ETERNUS_DXL- 010000-CM10-CA10-PORT00](mplb1)
The part boxed by Blue Line is the Name of Physical Device Node.
The relationship of CM, CA and PORT Display boxed by Red Line and CM display of ETERNUS Web
GUI is given as below with the FC Interface Model of ETERNUS DX60/DX80/DX90.
Table 2: Relations of CM and CM/CA/PORT Display

CM Display CA Display PORT Display
CM#0 10 10 0, 1
CM#1 11 11 2, 3
In case the Controller for replacing its Firmware is CM#0, confirm the line of CM10 boxed in Red
Line. In the above case, “/dev/rdsk/c2t0d0s2” boxed in Blue Line is the Name of the Physical Device
Node.
In the case of Controller for upgrading its Firmware is CM#1, check the line of Group No. being 11
boxed by Red Line. In the above case, “/dev/rdsk/c3t0d0s2” boxed in the Blue Line is the Name of the
Physical Device Node.
81
2) Make the Path Offline.

This is the example of command for making Offline the Path on the side of CM#1.
# /usr/opt/FJSViomp/bin/iompadm –c mplb change cu /dev/rdsk/c3t0d0s2
3) Confirm that the Path turned to Offline.

# /usr/opt/FJSViomp/bin/iompadm -c mplb info

/dev/rdsk/c3t0d0s2 offline stop block “stop status by software indication
As given above confirm that the status of the Path made Offline is given as “offline stop”.
3.3. Procedure of Path Online Operation

1) Confirm the Physical Node Name of the Path to be made Online.
# /usr/opt/FJSViomp/bin/iompadm –c mplb info

/dev/rdsk/c3t0d0s2 offline stop block “stop status by software indication
When the status of the Path is “offline stop” use the Physical Node Name of the Path (Blue Line).
2) Make the Path Online.

This is the example of command for making Online the Path on the side of CM#1.
# /usr/opt/FJSViomp/bin/iompadm -c mplb restart cu /dev/rdsk/c3t0d0s2
Note: Depending on processing “restart Command”, the processing of ”restart Command” may fail
(indicating IO Error). In such a case, execute “restart Command” again.
3) Confirm that the Path turned to Online.

# /usr/opt/FJSViomp/bin/iompadm -c mplb info

82
As given above confirm that the status of the Path made Offline is given as “online”.
3.4. Output message when Hot (Automatic) application is applied

During applying firmware with hot maintenance, the following error messages for the multipath driver
may output. But there is no problem because I/O is continued with the function of fail-over of the path.
In case of GR Multi-path driver, ETERNUS Multi-path driver (for Solaris 9 OS, Solaris 8 OS, Solaris 7
OS, Solaris 2.6 OS driver)
Example) WARNING: /pci@15,4000/fibre-channel@5/hddv@10,7 (hddv775):

SCSI transport failed: reason 'XXXXX': retrying command
Part of 'XXXXX' is shown the sort of path error (reset、incomplete etc.).
WARNING: /pci@15,4000/fibre-channel@5/hddv@10,9 (hddv777): disk not responding to selection
In case of ETERNUS Multi-path driver (for Solaris 10 OS、Solaris 9 OS driver)合
Example) /pci@15,4000/fibre-channel@5/mplbt@10,9 (mplbt777):

SCSI transport failed: reason 'XXXXX': giving up
Part of 'XXXXX' is shown the sort of path error (reset、incomplete etc.).
WARNING: /pci@15,4000/fibre-channel@5/mplbt@10,0 (mplbt768): disk not responding to selection
83
Appendix 4 Server Operation when VMware ESX Server is connected
Appendix 4. Server Operation when VMware ESX Server is

connected
Attention is required as below to the Server Operation in the case of SAS Connection of ETERNUS
DX60/DX80/DX90 with the Server working at VMware ESX. For details refer to the document given below.
[ETERNUS Disk Array SAS Connection Procedure (for VMware® ESX)]
1. Execution of Hot Operation (with Coalition with Operator)

1.1 Massage is displayed for making the Path connected to CM0 (or CM1) is Offline. (Text and the Fig.
6-32)
２. Selection of [Configuration] Tab at VMware (vSphere) Client.

2.1 Select [Details] -> [Display] -> [Path] Tabs of [Hardware] Frame.
2.2 Change the pertinent Path from “Valid” to “Invalid”.
3. Start of Firmware Replacement for CM0 (or CM1).

3.1 Upon the completion of Firmware Replacement for CM0 (or CM1), Massage of making Online the
Path connected to CM0 (or CM1) is given. (Text, Fig. 6-40)
４. Selection of [Config.] Tab for VMware (vSphere) Client

4.1 Select [Details] -> [Display] -> [Path] Tabs of [Hardware] Frame.
4.2 Change the pertinent Path from “Valid” to “Invalid”.

Execute the same Procedure with CM1 (or CM0).
84
Appendix 5 Downgrading the Version of Firmware
Appendix 5. Downgrading the Version of Firmware

Downgrading the currently operating firmware to the previous version is cannot be done Hot. The time
required for the work and the operating procedure are same as the works in the main chapters.
Note that New Features available with the currently working Firmware are in use, downgrading not only
makes them unavailable but there are also possibilities of giving influence to the total operation of the
system.
Figure 95: Downgrading Version of Firmware
85
Appendix 6 Shutdown/Rebooting of Power Supply for the System with GUI
Appendix 6. Shutdown/Rebooting of Power Supply for the System with

GUI
(1) Start up Web GUI to open “Shutdown/Rebooting of Power Supply for the System” in “Utility”. Click
“Rebooting” at the lower right of the screen.
Figure 96: Selecting Shutdown/Rebooting of Power Supply for the System
(2) Click “OK” in the executing confirmation screen.
86
Appendix 6 Shutdown/Rebooting of Power Supply for the System with GUI
(3) Rebooting is received and the logon after rebooting is urged once again.
87
Appendix 7 Patches required applying to ETERNUS SF (Middleware)
Appendix 7. Patches required applying to ETERNUS SF (Middleware)

In case ETERNUS SF Products as listed below are introduced to a system, it is necessary to have the
Middleware Version and the Patch Level compliant to the Firmware Version of ETERNUS
DX60/DX80/DX90.
7.1. ETERNUS SF AdvancedCopy Manager

Patch Nos. required to apply to ETERNUS SF AdvancedCopy Manager in the case of using Firmware Ver.
V10L20 or later of ETERNUS EX60/DX80/DX90 are as given below.
z ETERNUS SF AdvancedCopy Manager 14.0

[Copy Control Module Server]
Platform Patch No.
Solaris OS T003376SP-01 or later
Windows Windows Server 2003 T003373WP-01 or later
Windows Server 2008 Standard (32-bit)(64-bit) T003374WP-01 or later
Windows Server 2008 Enterprise (32-bit)(64-bit)
Windows Server 2008 Datacenter (32-bit)(64-bit)
Windows Server 2008 for Itanium-Based Systems T003375IP-01 or later
Linux Red Hat Enterprise Linux 5 (for x86) T003377LP-01 or later
Red Hat Enterprise Linux 5 (for Intel64)
Red Hat Enterprise Linux 5 (for Itanium) T003378QP-01 or later
(Codicil)
When Energy Saving Operation is applied to ETERNUS DX60/DX80/DX90 without using ETERNUS
SF Storage Cruiser, it is necessary to apply the above Path to Copy Control Module installed to the
Server executing the Ebergy Saving Operation.
z ETERNUS SF AdvancedCopy Manager 13.4/13.4.1

It is necessary to apply the Patch as given below in addition to the Firmware Ver. V10L11 Support
Patch of ETERNUS SF AcvancedCopy Manager 13.4/13.4.1.
[Copy Control Module Server]

Platform Patch No.
Solaris OS T002855SP-02 or later
Windows Windows Server 2003 T002873WP-02 or later
Windows Server 2008 Standard (32-bit)(64-bit) T002874WP-02 or later
Windows Server 2008 Enterprise (32-bit)(64-bit)
Windows Server 2008 Datacenter (32-bit)(64-bit)
Windows Server 2008 for Itanium-Based Systems T002875IP-02 or later
Linux Red Hat Enterprise Linux 5 (for x86) T002856LP-02 or later
Red Hat Enterprise Linux 5 (for Intel64)
Red Hat Enterprise Linux 5 (for Itanium) T002857QP-02 or later
(Codicil)
When Energy Saving Operation is applied to ETERNUS DX60/DX80 without using ETERNUS SF
Storage Cruiser, it is necessary to apply the above Path to Copy Control Module installed to the Server
executing the Ebergy Saving Operation.
88
Appendix 7 Patches required applying to ETERNUS SF (Middleware)
z ETERNUS SF AdvancedCopy Manager 13.0/13.1/13.2/13.3

It is not supported without respect to the Firmware Ver. No. of ETERNUS DX60/DX80/DX90.
7.2. ETERNUS SF Storage Cruiser

Given below are the Patch Nos. required to apply to ETERNUS SF Storage Cruiser in the case of using
Firmware Ver. No. V10L20 or later of ETERNUS DX60/DX80/DX90.
z ETERNUS SF Storage Cruiser 14.0
Scope of Targets to apply Patch No.

Solaris Manager T003439SP-02
Windows Manager T003442WP-02
Linux Manager (for x86, Intel64) T003440LP-02
Linux Manager (for Intel Itanium) T003441QP-02
Windows Client T003458WP-02
89
Appendix 8 CFL Target Modules of each Model (for reference)
Appendix 8. CFL Target Modules of each Model (for reference)

There are three patterns of model for ETERNUS DX/60/DX80. CFL Target Module is different depending
on the Model.
(1) FC Model
Target Modules are of three types, CM, BE Expander and EXP.
(2) SAS Model

Target Modules are of four types, CM, BE Expander, BE Expander and EXP.
90
(3) SCSI Model

Target Modules are of three types, CM (iSCSI), BE Expander and EXP.
List of CFL Target Modules

FC Model CM
BE Expander
EXP
SAS Model CM
FE Expander
BE Expander
EXP
SCSI Model CM (iSCSI)
BE Expander
EXP
(Reference) Sequence of CFL Movement

CFL is executed by dividing Modules mounted on the System into two [Fist Half] and [Second Half].
CFL Target Modules and the Sorting of First Half and Second Half as shown in the table below.
First half Second half
1 2 3 4
EXP#1 System |
CM#1 |
iSCSI#1 |
FE Expander#1 |
BE Expander#1 |
CM#0 |
iSCSI#0 |
FE Expander#0 |
BE Expander#0 |
EXP#0 System |
|: CFL Execution
Ú The Module with vertically continuous | Marks are for simultaneous CFL.
Ú Mounting/Non-mounting of iSCSI and FE Expander are different depending on the Model.
Ú This is the sequence when CM#0 is the Master CM. When CM#1 is the Master CM, #0 and
#1 are reversed.
91
(1) FC Model
(1) Start CFL (2) CFL of #1 system EXP
Old Ver. No. Old Ver. No. Old Ver. No. Old Ver. No.
Old Ver. No. Old Ver. No. Old Ver. No. New Ver. No.
(3) CFL of #1 system CM, BE Expander (4) Sw itch over Master CM
Old Ver. No. New Ver. No. Old Ver. No. New Ver. No.
(5) CFL of #0 system CM, BE Expander (6) Sw itch back Master CM
New Ver. No. New Ver. No. New Ver. No. New Ver. No.
92
(7) CFL of #0 system EXP (8) End of CFL
93
(2) SAS Model
(3) CFL of #1 system CM, FE Expander, BE Expander (4) Sw itch over Master CM
(5) CFL of #0 system CM, FE Expander, BE Expander (6) Sw itch back Master CM
94
95
(3) iSCSI Model
(3) CFL of #1 system CM, iSCSI, BE Expander (4) Sw itch over Master CM
(5) CFL of #0 system CM, iSCSI, BE Expander (6) Sw itch back Master CM
96
97

E DX60 DX80 DX90 Fwup - V10L50

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

E DX60 DX80 DX90 Fwup - V10L50

Hochgeladen von

Copyright:

Verfügbare Formate

ETERNUS DX60 / DX80 / DX90

Disk Array Unit

Firmware Updating Instructions

Storage System Development Division, Storage Systems Unit,

 Before Starting the Procedure

 Outline of Flow for the Instructions (Entire Flow)

Confirmation before Delivery

 Outline of the Feature

z Non-hot mode [Controller firmware download] (CFD)]

[Work Check Sheet]

Appendix 1. Operating Conditions 66

Chapter 1. Procedure of firmware update

1.1. Procedure selection

The features of application mode (procedure) follow below;

1.2. Time Requirement

z Firmware application (Operation of downloading)

1.3. Application of Patches to ETERNUS SF (Middleware)

1.4. Attention in the ETERNUS DX80 firmware Updating

2. Work flow and cautions in Hot Application (cooperation with operator)

2.1. Work flow in Hot Application (cooperation with operator)

Start of maintenance works

Firmware application replacement of LAN Cable for FST

Version number check of firmware

2.2. Precautions for Hot (cooperation with operator)

Ú As to the detailed conditions of operation, refer to “Appendix 1 Operating Conditions”.

2.4. Monitoring software

z Storage Cruiser (Resource Coordinator)

3. Work flow and cautions in Hot (automatic)

3.1. Work flow in Hot (automatic)

Logon（ GUI Booting）

System status (GUI) check

System status (External view) check

Start of maintenance works

Saving configuration information

Version number check of firmware Halting works of Host IO

Version number check of firmware

System status (External view) check

Completion of maintenance works

Logoff (GUI completion)

3.2. Precautions for Hot (automatic)

As to the procedure of detailed operation, refer to “Appendix 1 Operating Conditions”.

3.3. Cautions for Hot (automatic) during the operation

3.4. Monitoring software

z Storage Cruiser (Resource Coordinator)

4. Work Flow of Firmware Replacement in Non-Hot Status

Logon (GUI Booting)

System status (GUI) check

System status (External view) check

Start of maintenance works

Saving configuration information

Version number check of firmware

Firmware application Applying firmware to Non-operating side

Logoff (GUI completion)

System Power OFF/ON

Logon (GUI Booting)

Version number check of firmware

System status (GUI) check

System status (External view) check

Completion of maintenance works

Logoff (GUI completion)

5.1. Preparation of FST

Browser Microsoft Internet Explorer 6.0/7.0/8.0

Before Starting the Procedure

Outline of Flow for the Instructions (Entire Flow)

Outline of the Feature