22 Nas

Hitachi Proprietary SC01486Z
NAS00-00 DKC515I
Rev.0 / May.2005 Copyright © 2005, Hitachi, Ltd.
NAS Software Section
NAS00-00
NAS00-10 DKC515I
Rev.1 / May.2005, Dec.2005 Copyright © 2005, Hitachi, Ltd.
Contents
NAS01-10 1. Overview
NAS01-10 1.1 Maintenance Tasks and Reference Locations
NAS01-40 1.2 Related Manuals
NAS01-50 1.3 Overview of Each Chapter
NAS02-10 2. NAS Blade System Device Explanation

NAS02-10 2.1 Overview
NAS02-20 2.2 NAS Blade System Hardware Configuration
NAS02-30 2.3 NAS Blade System Software Configuration and
Operating Environment
NAS02-70 2.4 Minimum and Maximum Configurations
NAS02-80 2.5 Maintenance Personnel
NAS02-80 2.5.1 Roles of the Maintenance Personnel and System Administrators
NAS02-100 2.5.2 Maintenance Terminal (Not Required for Ordinary Operations)
NAS02-110 2.5.3 SSH Account for Maintenance Personnel and System Administrators
(Not Required for Ordinary Operations)
NAS03-10 3. NAS Installation

NAS03-10 3.2 Prerequisites
NAS03-20 3.2.1 Creating NAS System LUs
NAS03-40 3.2.2 Defining the Paths to NAS System LUs
NAS03-40 [1] Defining paths to the NAS OS LU and the dump LU
NAS03-60 [2] Defining paths to a command device, error information LU, NAS
Cluster Management LU, and backup LU of NAS Cluster Management
LU
NAS03-70 3.2.3 Defining Paths to User LUs
NAS03-71 3.2.4 Set up the NAS Time Zone
NAS03-80 3.3 New Installation (Setup Performed By the Manufacturer)
NAS03-90 3.4 On-Site Installation (On-Site Setup)
NAS03-100 3.5 Operations on the SVP
NAS03-100 3.5.1 Overview of Setup on SVP
NAS03-110 3.5.2 Implementing Setup on SVP
NAS03-110 [1] Installing Setup on SVP
NAS03-180 [2] Starting and stopping Setup on SVP
NAS03-200 [3] Uninstalling Setup on SVP
NAS03-251 [4] Checking the Setup on SVP version
NAS03-260 3.5.3 NAS Package Status
NAS00-10
NAS00-20 DKC515I
Rev.1 / May.2005, Jun.2005 Copyright © 2005, Hitachi, Ltd.
NAS03-290 3.5.4 Installing the NAS OS and Related Program Products

NAS03-310 [1] NAS OS installation for the first time
NAS03-400 [2] NAS OS expansion installation
NAS03-490 [3] Optional program product installation
NAS03-521 [4] NAS OS installation for the first time (Multi-Installation)
NAS03-522 [5] NAS OS expansion installation (Multi-Installation)
NAS03-523 [6] Optional program product installation (Multi-Installation)
NAS03-530 [7] Installation Containing LU Initialization (Use this procedure by
developers' instruction only when the error cannot be corrected)
NAS03-590 3.5.5 Uninstalling Optional Program Products
NAS03-620 3.5.6 Setting Up the Network Environment
NAS03-630 [1] Setting up the network for the control port
NAS03-632 [2] Adding routing informaiton to the control port
NAS03-641 [3] Deleting routing information
NAS03-650 3.5.7 Setting Up a License
NAS03-650 [1] Setting up licenses individually
NAS03-690 [2] Setting up licenses in the batch mode
NAS03-730 [3] Checking or changing license information
NAS03-750 [4] Deleting licenses
NAS03-780 3.5.8 Controlling the NAS OS (Stopping, Starting, and Restarting)
NAS03-780 [1] Stopping the NAS OS
NAS03-820 [2] Starting the NAS OS
NAS03-840 [3] Restarting the NAS OS
NAS03-880 3.5.9 Resetting CHA
NAS03-910 3.5.10 Collecting the Hibernation Dump
NAS03-910 [1] Collecting the hibernation dump
NAS03-940 [2] Canceling collection of the hibernation dump
NAS03-960 3.5.11 Viewing the Settings (Refer Configuration Button)
NAS03-990 3.5.12 Restoring a NAS OS LU
NAS03-1040 3.5.13 Restoring a NAS Cluster Management LU
NAS03-1075 3.5.14 Selecting the Install Device
NAS03-1080 3.5.15 Downloading Dump Files
NAS03-1290 3.6 Operations Using the NAS Blade Manager GUI
NAS03-1290 3.6.1 Registering System Administrators
NAS03-1290 3.6.2 Setting Up the NAS Package Cluster Configuration
NAS03-1290 3.6.3 Setting Up the Configuration For Services
NAS03-1300 3.6.4 Setting Up the Network for the control port and data port
NAS03-1300 3.6.5 Setting Up the Network (DNS, NIS)
NAS03-1300 3.6.6 Setting Up Users and Groups
NAS03-1310 3.6.7 Creating File Systems
NAS03-1310 3.6.8 Setting Up File Shares (NFS, CIFS)
NAS03-1320 3.6.9 Specifying Settings Related to Error-Monitoring Functionality
NAS03-1320 3.6.10 Settings Related to the Save Function for NAS System LUs
(NAS OS LU and NAS Cluster Management LU)
NAS00-20
NAS00-30 DKC515I
NAS04-10 4. NAS Hardware Replacement

NAS04-20 4.2 Types of Hardware Replacement Operations
NAS04-30 4.2.1 Flowcharts for Replacing Hardware
NAS04-40 (1) Replacing the NAS Package (During Preventive Replacement)
NAS04-80 (2) Replacing Data LAN Fiber Optic Cables (During Preventive
Replacement)
NAS04-111 (3) Replacing Control LAN Fiber Optic Cables (During Preventive
Replacement)
NAS04-115 (4) Maintaining and Replacing External Devices (During Preventive
Replacement)
NAS04-120 (5) Hot-replacing Hardware Other Than the NAS Package
NAS05-10 5. NAS Software FC

NAS05-20 5.2 Preparing for Software Upgrade Operations (System LU Backup)
NAS05-30 5.3 Types of Software Upgrade Operations
NAS05-60 5.3.1 Flowcharts for Upgrading NAS Software
NAS05-60 (1) Upgrading Setup on SVP
NAS05-70 (2) Upgrading NAS OS by an Updated Version
(Preventive Upgrade: While Operating)
NAS05-130 (3) Replacing the NAS OS By a Patch Version  Restarting the NAS OS
Is Not Required (Preventive Upgrade: While Operating)
Is Required (Preventive Upgrade: While Operating)
NAS05-320 (5) Upgrading NAS OS by an Updated Version (Preventive Upgrade:
While the Cluster is Stopped)
Is Not Required (Preventive Upgrade: While the Cluster is Stopped)
Is Required (Preventive Upgrade: While the Cluster is Stopped)
NAS05-500 (8) Upgrading NAS Blade Manager (Preventive Upgrade)
NAS05-520 (9) Upgrading an Optional Program Product (Preventive Upgrade)
NAS05-550 5.3.2 Procedures for Upgrading the NAS OS and Related Program
Products
NAS05-570 [1] Upgrading the NAS OS (update version)
NAS05-670 [2] Upgrading the NAS OS (patch version)
NAS05-720 [3] Upgrading the NAS Blade Manager
NAS05-760 [4] Upgrading the optional program product
NAS05-800 5.3.3 Going Back To an Earlier Software Version
NAS05-800 (1) To Go Back To an Earlier Version of the NAS OS
NAS05-800 (2) To Go Back To an Earlier Version of NAS Blade Manager
NAS05-800 (3) To Go Back To an Earlier Version of an Optional Program Product
NAS00-30
NAS00-40 DKC515I
Rev.1 / May.2005, Nov.2005 Copyright © 2005, Hitachi, Ltd.
NAS06-10 6. NAS Configuration (Reconfiguration)

NAS06-20 6.2 Reconfiguring Hardware
NAS06-20 6.2.1 Types of Hardware Reconfiguration
NAS06-30 6.2.2 Flowcharts for Reconfiguring Hardware
NAS06-40 (1) Adding a RAID Group (User LU)
NAS06-60 (2) Removing a RAID Group (User LU)
NAS06-80 (3) Adding or Removing RAID Cache Memory or Reconfiguring (DCR)
NAS06-90 (4) Adding a NAS Package
NAS06-130 (5) Removing a NAS Package
NAS06-150 (6) Increasing LU Capacity (User LU)
NAS06-180 (7) Decreasing LU Capacity (User LU)
NAS06-210 6.3 Reconfiguring Software
NAS06-210 6.3.1 Types of Software Reconfiguration
NAS07-10 7. NAS Troubleshooting

NAS07-30 7.2 Detecting and Identifying Failures
NAS07-40 7.2.1 Detecting Failures
NAS07-40 (1) Failure Detection By Maintenance Personnel
NAS07-50 (2) Failure Detection By System Administrators
NAS07-60 7.2.2 Identifying Failures and Taking Countermeasures
NAS07-70 7.2.3 Obtaining Detailed Information about a Failure
NAS07-70 (1) Detailed Information for Maintenance Personnel
NAS07-90 (2) Detailed Information for System Administrators
NAS07-100 7.2.4 Preparing for Failure Recovery Operations (System LU Backup)
NAS07-110 7.3 Lists of Failures
NAS07-110 7.3.1 Hardware Failures
NAS07-160 7.3.2 Software Failures
NAS07-210 7.4 Identifying Troubleshooting Procedures from Failure Phenomena
NAS07-350 7.5 Hardware Troubleshooting Procedures
NAS07-360 7.5.1 NAS Package Failure Detected By a Processor
in the NAS Package
NAS07-380 7.5.2 NAS Package Failure Detected By a NAS OS Driver or Kernel
NAS07-400 7.5.3 RAID Failure (2PDEVs: User LUs)
NAS07-411 7.5.4 External Device Failure
NAS07-420 7.5.5 RAID Failure (2 PDEVs: NAS System LUs  NAS OS LUs
in the Cluster Belong to Different RAID groups)
NAS07-440 7.5.6 RAID Failure (2 PDEVs: NAS System LUs  NAS OS LUs
in the Cluster Belong to the Same RAID Group)
NAS07-460 7.5.7 RAID Failure (2 PDEVs: NAS Cluster Management LUs)
NAS07-480 7.5.8 RAID Failure (2 PDEVs: Dump LUs)
NAS00-40
NAS00-50 DKC515I
Rev.2 / Jun.2005, Nov.2005 Copyright © 2005, Hitachi, Ltd.
NAS07-500 7.5.9 RAID Failure (2 PDEVs: Error Information LUs)

NAS07-520 7.5.10 RAID Failure (2 PDEVs: Command Devices)
NAS07-540 7.5.11 RAID Failure (2 PDEVs: Backup LUs of NAS Cluster
Management LUs)
NAS07-560 7.5.12 Hardware Failure (Correctable)
NAS07-580 7.5.13 Network Failure (Network Settings Failed)
NAS07-615 7.5.14 Fiber Optic Cable (LAN Cable) Link Down, Switch Failure, or
Failure in Entire Trunking
NAS07-619 7.5.15 Internal Error in a Data LAN Network Board (Partial Failure, Able
to Continue Operation)
NAS07-619B 7.5.16 Disk I/O Timeout Error in an LU Other Than a NAS OS LU
(Response from Target MP, Retry Unsuccessful)
NAS07-620 7.6 Software Troubleshooting
NAS07-630 7.6.1 NAS OS Failure (Panic)
NAS07-650 7.6.2 NAS OS Failure (Hangup)
NAS07-680 7.6.3 NAS OS Failure (Slowdown)
NAS07-710 7.6.4 Application Failure (Failover Provided)
NAS07-740 7.6.5 Application Failure in Something Other Than the Web Server
(Failover Not Provided)
NAS07-770 7.6.6 Application Failure in the Web Server (Failover Not Provided)
NAS07-800 7.6.7 NAS OS Failure (In Start/Stop Processing)
NAS07-830 7.6.8 Failure When a NAS OS LU is Full
NAS07-860 7.6.9 NAS OS File System Failure
NAS07-900 7.6.10 NAS OS Failure During Startup or Stop (Invalid Dump LU)
NAS07-920 7.6.11 NAS OS Failure During Startup or Stop (Unable to Connect NTP
Server)
NAS07-960 7.6.12 NAS OS Application Failure (Unable to Set Internal IP Address)
NAS07-1001 7.6.13 Failure During NAS Dump Collection
NAS07-1003 7.6.14 NAS Cluster Management LU Failure (in NAS OS Start/Stop
Processing)
NAS07-1005 7.6.15 Failure in Preliminary Processing for NFS Share (in NAS OS
Start/Stop Processing)
NAS07-1009 7.6.16 User LU Failure (in NAS OS Start/Stop Processing)
NAS07-1009C 7.6.17 Failure in Setting or Releasing NFS Share (in NAS OS Start/Stop
Processing)
NAS07-1009F 7.6.18 Service IP Up/Down Failure (in NAS OS Start/Stop Processing)
NAS07-1009J 7.6.19 Failure in Setting or Releasing CIFS (in NAS OS Start/Stop
Processing)
NAS07-1009N 7.6.20 NAS OS or Application Failure (in NAS OS Start/Stop Processing)
NAS07-1009R 7.6.21 File System for a User LU is Blocked
NAS07-1009U1 7.6.22 User LU File System is Blocked (When Automatic Failover
Function is Enabled)
NAS07-1009V 7.6.23 NAS OS System File Failure (in NAS OS Start/Stop Processing)
NAS00-50
NAS00-60 DKC515I
NAS07-1010 7.7 NAS Hardware Replacement When a Failure Occurs

NAS07-1020 [1] Types of Hardware Replacement Operations
NAS07-1040 [2] Procedures for Replacing Hardware
NAS07-1050 7.7.1 Replacing the NAS Package (When a Failure Occurs)
NAS07-1080 7.7.2 Hot-replacing Hardware Other Than the NAS Package
NAS07-1100 7.7.3 Replacing Two PDEVs (User LUs)
NAS07-1131 7.7.4 Recovering External Subsystem Device Status
NAS07-1140 7.7.5 Replacing Two PDEVs (NAS OS LU: When the NAS OS LU
and the Dump LU Belong to Different RAID Groups)
NAS07-1180 7.7.6 Replacing Two PDEVs (NAS OS LU: When the NAS OS LUs
for CL1-CHA and CL2-CHA Belong to the Same RAID Group)
NAS07-1200 7.7.7 Replacing Two PDEVs (NAS Cluster Management LUs)
NAS07-1220 7.7.8 Replacing Two PDEVs (Dump LUs)
NAS07-1270 7.7.9 Replacing Two PDEVs (Error Information LUs)
NAS07-1290 7.7.10 Replacing Two PDEVs (Command Device)
NAS07-1310 7.7.11 Replacing Two PDEVs
(Backup LUs of NAS Cluster Management LUs)
NAS07-1340 7.7.12 Replacing Data LAN Fiber Optic Cables (LAN Cable) or a Switch
(When a Failure Occurs)
NAS07-1360A 7.7.13 Replacing Control LAN Fiber Optic Cables (LAN Cable) or a
Switch (When a Failure Occurs)
NAS07-1360C 7.7.14 Failure in Part of Trunking
NAS07-1361 7.7.15 Failback (When a Failure Occurs)
NAS07-1370 7.8 Upgrading Software
NAS07-1370 [1] Types of Software Upgrade Operations
NAS07-1390 [2] Procedures for Upgrading Software
NAS07-1400 7.8.1 Upgrading the NAS OS By an Update Version (When a Failure
Occurs)
NAS07-1440 7.8.2 Upgrading the NAS OS By a Patch Version  Restarting the NAS
OS Is Not Required (When a Failure Occurs)
NAS07-1500 7.8.3 Upgrading the NAS OS By a Patch Version  Restarting the NAS
OS Is Required (When a Failure Occurs)
NAS07-1560 7.8.4 Upgrading NAS Blade Manager (When a Failure Occurs)
NAS07-1580 7.8.5 Upgrading an Optional Program Product (When a Failure Occurs)
NAS07-1600 7.9 Going Back To an Earlier Software Version (When Upgrade Failed)
NAS07-1600 7.9.1 To Go Back To an Earlier Version of the NAS OS
NAS07-1600 (1) When the NAS OS LU, NAS Cluster Management LU and user LU
Have Been Backed Up
NAS07-1600 (2) When the NAS OS LU, NAS Cluster Management LU and user LU
Have Not Been Backed Up
NAS07-1600 7.9.2 To Go Back To an Earlier Version of NAS Blade Manager
NAS07-1600 7.9.3 To Go Back To an Earlier Version of an Optional Program Product
NAS00-60
NAS00-70 DKC515I
NAS08-10 8. Setup Procedures When Implementing NAS Blade System for the First Time
NAS08-20 8.1 Operations Using the SVP
NAS08-20 [1] Setting up the network environment
NAS08-160 [2] Setting the license of NAS Blade Manager
NAS08-210 8.2 Operations Using the NAS Blade Manager GUI
NAS08-210 [1] Confirming that Setup on SVP is stopped
NAS08-220 [2] Connecting Fibre optic cables (LAN cables)
NAS08-230 [3] Registering system administrators
NAS08-330 [4] Setting up the NAS Package cluster configuration
NAS08-400 8.3 Confirmation of the settings
NAS08-400 [1] Connection of Fibre optic cable (LAN cable)
NAS08-420 [2] Starting the cluster
NAS08-500 [3] Confirmation of the connection from a client
NAS09-10 9. Appendixes
NAS09-10 9.1 Appendix A Using the Command Line To Obtain Error Information
NAS09-10 9.1.1 Overview
NAS09-10 9.1.2 Types of Error Information
NAS09-30 9.1.3 How to Obtain a Crash Dump
NAS09-80 9.1.4 How to Obtain a Hibernation Dump
NAS09-150 9.1.5 How to Obtain an LM Dump
NAS09-180 9.1.6 How to Obtain an Event Trace
NAS09-250 9.2 Appendix B Initializing Dump LUs
NAS09-280 9.3 Appendix C How to Obtain Error Information When the NAS OS Has Not
Started
NAS09-280 9.3.1 Overview
NAS09-280 9.3.2 Confirming that NAS OS is stopped
NAS09-280 9.3.3 How to Obtain an Auto Dump
NAS09-300 9.3.4 How to Collect a Dump File
NAS09-330 9.4 Appendix D Setting NAS Time Zone
NAS00-70
NAS01-10 DKC515I
1. Overview
1.1 Maintenance Tasks and Reference Locations
The maintenance tasks and corresponding reference locations in this NAS Software Section are as
follows:
Table 1.1-1 Maintenance Tasks and Corresponding Reference Locations in this

Document
# Classification Task Reference location in NAS
Software Section
1 NAS Blade system Performing a new installation 3.2 Prerequisites [NAS03-10]
initial build 3.3 New Installation (Setup
Performed By the Manufacturer)
[NAS03-80]
3.5 Operations on the SVP
[NAS03-100]
Performing on-site installation 3.2 Prerequisites [NAS03-10]
3.4 On-Site Installation (On-Site
Settings) [NAS03-90]
[NAS03-100]
Testing settings (new and on-site 8. Setup Procedures When
installation) Implementing NAS Blade System for
the First Time [NAS08-10]
2 Replacing - Replacing NAS Packages 4. NAS Hardware Replacement

hardware - Replacing PDEVs [NAS04-10]
3 Adding/removing - Adding/removing a RAID group 6.2 Reconfiguring Hardware
hardware - Adding/removing RAID cache [NAS06-20]
memory
- Adding/removing a NAS package
- Increasing/decreasing LU
capacity
4 Upgrading and - Upgrading and downgrading the 5. NAS Software FC [NAS05-10]
downgrading NAS OS version
software version - Upgrading and downgrading the
(updated or patch NAS Blade Manager version
version) - Upgrading and downgrading the
optional program product version
5 Software - 6.3 Reconfiguring Software
reconfiguration [NAS06-210]
(Continues on the next page.)
NAS01-10
NAS01-20 DKC515I
(Continued from the previous page.)

# Classification Task Reference location in NAS
Software Section
6 Failure detection Identifying failures 7.2 Detecting and Identifying
and Failures [NAS07-30]
countermeasure
Troubleshooting hardware 7.3 Lists of Failures [NAS07-110]
7.5 Hardware Troubleshooting
Procedures [NAS07-350]
Troubleshooting software 7.3 Lists of Failures [NAS07-110]
7.6 Software Troubleshooting
[NAS07-620]
Obtaining error information 7.2.3 Obtaining Detailed Information
about a Failure [NAS07-70]
9.1 Appendix A Using the Command
Line to Obtain Error Information
[NAS09-10]
9.2 Appendix B Initializing Dump
LUs [NAS09-250]
9.3 Appendix C How to Obtain Error
Information When the NAS OS Has
Not Started [NAS09-280]
7 Other Setting NAS Time Zone 9.4 Appendix D Setting NAS Time
Zone [NAS09-330]
NAS01-20
NAS01-30 DKC515I
The reference locations in other sections are as follows:
Table 1.1-2 Reference Locations in Other Sections

# Task item Section to be referenced
1 Performing the NAS initial build INSTALLATION Section [INST01-10]
2 Replacing hardware REPLACE Section [REP01-10]
3 Adding/removing hardware INSTALLATION Section [INST01-10]
SVP Section [SVP01-10]
4 Troubleshooting hardware TROUBLE SHOOTING Section [TRBL01-10]
5 Troubleshooting software
This NAS Software Section uses the following abbreviations to refer to software products and
components.
Table 1.1-3 Abbreviations for Software Products and Components

# Abbreviation Full name Note
1 Anti Virus Agent NAS Anti Virus Agent
2 Backup Restore NAS Backup Restore
3 Data Control NAS Data Control
4 File Sharing NAS File Sharing
5 NAS Manager NAS Blade Manager
6 NAS OS A generic name referring to both NAS Data Control Linux-based product.
and NAS File Sharing.
7 Sync Image NAS Sync Image
NAS01-30
NAS01-40 DKC515I
1.2 Related Manuals

The related manuals are the user's guide for disk subsystems (Table 1.2-1) and the user's guide for
NAS Blade Manager software products (Table 1.2-2).
Table 1.2-1 User's guide for disk subsystems

# Manual Contents
1 Storage Navigator User’s Guide Describes Remote Console GUI operations in general,
and how to install program products into a disk
subsystem, etc.
2 LUN Manager User’s Guide Describes functionality and operations of LU creation and
path/port settings, etc.
3 Cache Residency Manager User’s Describes functionality and operations of Partial Cache
Guide Residence and Dynamic Cache Residence, etc.
4 LUN Expansion (LUSE)/Virtual Describes functionality and operations of LUSE volumes.
LVI/LUN (VLL) User’s Guide
Table 1.2-2 User's guide for the NAS software products

# Manual Contents
1 NAS Blade Manager User's Guide Describes functionality and operations of NAS Blade
Manager.
2 NAS Backup Restore User's Guide Describes functionality and operations of NAS Backup
Restore (snapshot, backup).
3 NAS Sync Image User's Guide Describes functionality and operations of NAS Sync
Image (differential-data snapshot).
4 NAS Blade Error Codes Describes messages for NAS related software.
NAS01-40
NAS01-50 DKC515I
1.3 Overview of Each Chapter
The chapters in this NAS Software Section are as follows:
Chapter 1. Overview
This chapter gives an overview of each chapter in the NAS Software Section.
Chapter 2. NAS Blade System Device Explanation

Explains the NAS Blade system hardware configuration, software configuration, and operating
environment. This chapter also explains and lists the major tasks for which the maintenance
personnel and system administrators are responsible.
Chapter 3. NAS Installation

Explains the procedures for the NAS Blade system initial build from installing hardware to
providing file services to end users.
Section 3.2 Prerequisites outlines how to create NAS system LUs and user LUs, and how to
define paths.
Two tables list the steps in the installation procedures:

Table 3.3-1 Procedure for Installing NAS for the First Time (Setup Performed by the
Manufacturer) and Table 3.4-1 Procedure for NAS On-Site Installation.
The shaded parts in the tables indicate the tasks for which maintenance personnel are
responsible.
Section 3.5 Content and Procedure of Each Task describes the contents and procedure for each
task listed in the tables mentioned above. The subsection gives only an outline of the tasks for
which system administrators are responsible.
NAS01-50
NAS01-60 DKC515I
Chapter 4. NAS Hardware Replacement

Explains the procedure for replacing NAS Blade system hardware if a failure occurs or when
preventive replacement is performed. This chapter also explains the procedure for upgrading
the software.
Table 4.X-1 Types of Hardware Replacement Operations lists the contents of tasks and
conditions for each part of replacement.
In subsection 4.x.x Flowcharts For Replacing Hardware, the flowcharts illustrate the
procedures for each part of the replacements listed in the table mentioned above. Each
description of a procedure consists of the following:
• a figure giving an outline of the procedure,
• a table listing the steps in the procedure, and
• a detailed flowchart of the procedure.
The area of a detailed flowchart is divided into three columns:

• the left column shows the task of maintenance personnel,
• the mid-column shows the task of system administrators, and
• the right-column shows the status of the NAS Blade system.
The following shows a sample description of a procedure.
NAS01-60
NAS01-70 DKC515I
<Sample Description of a Procedure>

---------------------------------------------------------------------------------------------------------------------
(2) Replacing the NAS Package (Preventive Replacement)
Replacement
NAS Package
CL1-CHA CL2-CHA
Pentium
Pentium Pentium MP MP
MP MP MP MP
Backup LU of NAS CM LU
NAS OS LU for CL1-CHA NAS OS LU for CL2-CHA
SVP Dump LU for CL1-CHA Dump LU for CL2-CHA
Error Information LU
User LU Command Device

User LU
User LU
: Failover (manually)
: Failback
: Monitoring
Step Procedure Notes

1 Check the operating status of the
NAS Blade system.
2 Perform the failover.
3 Stop the NAS OS. Stop the NAS OS while the target NAS
Package is running.
4 Replace the NAS Package.
5 Perform the failback.
NAS01-70
NAS01-80 DKC515I
Maintenance personnel System administrators NAS Blade system
Replacing the NAS package

(on preventive replacement)
Phone, E-mail: Phone, E-mail:

Request a system administrator Request ordinary users to check
to check the NAS operating the NAS operating state.
state.

Confirm the NAS operating state. Notify maintenance personnel
about whether the NAS is
operating.
Is CL1-CHA NO
operating?
YES
:
:
: :
: : CL1-CHA: Operating
: CL2-CHA: Operating
: Failing over from CL1-CHA to CL2-CHA
Failover notification
- NAS Blade Manager GUI
(CL2-CHA notification)
:
:
:
Examples of the NAS conditions shown in procedures is below:

Operating: NAS services are provided to users.
Running: NAS services are not provided to users although NAS
OS has been started.
Not running: NAS services are not provided to users and NAS
OS has been stopped.
---------------------------------------------------------------------------------------------------------------------
NAS01-80
NAS01-90 DKC515I
Chapter 5. NAS Software FC

Explains the procedure for upgrading the software on preventive replacement.
Table of Types of Software Upgrading Procedures lists the contents of tasks and conditions for
each program.
In subsection 5.x.x Flowcharts for Software Upgrading, the flowcharts illustrate the procedures
or each program listed in Table 5.X-1. The format of the descriptions is the same as that for
hardware replacement in Chapter 4.
Chapter 6. NAS Configuration (Reconfiguration)
Explains the procedures for reconfiguring a NAS Blade system, which may become necessary
due to an increase in the volume of data or changes in the type of work.
Table 6.2-1 Types of Hardware Reconfiguration lists the contents of tasks and conditions for
each part of reconfiguration.
In subsection 6.2.2 Flowcharts For Reconfiguring Hardware, the flowcharts illustrate the
procedures for each task listed in the table mentioned above. Each description of a procedure
consists of the following:
a figure giving an outline of the procedure,
a table listing the steps in the procedure, and
a detailed flowchart of the procedure.
The format of the descriptions is the same as that of the flowcharts describing replacement
procedures in chapter four.
Table 6.3-1 Types of Software Reconfiguration lists the classifications of software

reconfigurations according to software components and functionality.
NAS01-90
NAS01-100 DKC515I
Chapter 7. NAS Troubleshooting
Explains how to detect a failure, how to identify the type of failure, and how to troubleshoot.
Section 7.2 Detecting and Identifying Failures uses tables to list the types of errors that might
occur and the error information that is reported by the system.
Subsection 7.2.1 Detecting Failures uses a table to list the NAS-specific error information
from the various types of error information reported by SIM.
Subsection 7.2.3 Detailed Information about a Failure lists the error information (log, dump,
trace) managed by maintenance personnel and outlines when and how to produce it.
Tables 7.3-1 Hardware Failures and 7.3-2 Hardware Failure Classifications and
Countermeasure Overview list the types of hardware failures and give an overview of the
corresponding countermeasures.
Tables 7.3-3 Software Failures and 7.4-4 Software Failure Classifications and
Countermeasure Overview list the types of software failures and give an overview of the
corresponding countermeasures.
NAS01-100
NAS01-110 DKC515I
In section 7.4 Flowcharts For Troubleshooting, the flowcharts illustrate the procedures for
each task listed in the tables mentioned above. Each description of a procedure consists of the
following:
a figure giving an outline of the procedure,
a table listing the steps in the procedure, and
a detailed flowchart of the procedure.
The format of the descriptions is the same as that of the flowcharts describing replacement
procedures in Chapter 4.
Chapter 8. Setup Procedures When Implementing NAS Blade System for the First Time
Explains how to set up the settings for both new and on-site installations.
Chapter 9. Appendixes
Appendix A. Using the Command Line to Obtain Error Information explains how to obtain a
crash dump, hibernation dump, LM dump, and event trace.
Appendix B. Initializing Dump LUs explains how to initialize dump LUs.
Appendix C. How to Obtain Error Information When the NAS OS Has Not Started explains the
procedure for obtaining the error information of the NAS Package where the NAS OS has not
started from other NAS Package where the NAS OS has started.
Appendix D. Setting NAS Time Zone explains how to set NAS time zone from Setup on SVP.
NAS01-110
NAS02-10 DKC515I
2. NAS Blade System Device Explanation

2.1 Overview
This chapter describes the device configuration (including devices, programs, and limit values) for
the NAS Blade system, and also describes the NAS Blade system operating environment.
NAS02-10
NAS02-20 DKC515I
2.2 NAS Blade System Hardware Configuration

Figure 2.2-1 shows the hardware configuration of the NAS Blade system.
Technical Support Maintenance server

Division
Performance monitoring
/Maintenance program
NAS management console

Maintenance
terminal *1 Web browser
Data & control LAN
Data LAN
NAS Package CL1-CHA NAS Package CL2-CHA
Pentium Pentium
...
MP MP MP MP
Backup LU of
NAS CM LU
SVP
Internal LAN
Setup on SVP NAS Cluster
Management LU
Storage
Navigator
Error information
Dump LU NAS OS LU NAS OS LU Dump LU LU
Public LAN
Storage
Navigator PC Command
User LU User LU device
NAS
Web browser
: Monitoring each other

*1: Not required for ordinary operations.
Figure 2.2-1 Hardware Configuration of the NAS Blade System
The Pentium processor and micro-processors (MPs) on a NAS Package are connected via the
internal LAN to the SVP. The NAS Package is equipped with 4 ports, among which the eth1 is set
for the control port to control the NAS Blade system. The other 3 ports are set for the data port to
connect to the application server and provide the disk subsystem as the file server. The eth1 can also
be shared by the control port and data port.
A NAS Package requires the following five NAS system LUs:
• NAS OS LU to store programs necessary for operation
• NAS Cluster Management LU (including a backup LU of NAS Cluster Management LU) to store
programs necessary for operation
• Dump LU to store error information
• Error information LU to store the edited error information
• Command device to operate RAID programs such as ShadowImage in-system replication
NAS02-20
NAS02-30 DKC515I
2.3 NAS Blade System Software Configuration and Operating Environment

Figure 2.3-1 shows the basic configuration of the NAS Blade system.
Maintenance servern Application server no

Performance monitoring
NAS Management Console no /Maintenance PP n User applications n
Web browser n Virus

Operating system n
SNMP scan server
https Virus
NTP serverno scan software
NTP server n
NTP protocol
NAS Blade system
(NAS Package)
Web(S)
NAS NAS NAS

Maintenance Backup Restore Anti Virus Agent Sync Image
terminal *1
ftp(S) n NAS Blade Manager
ftp
NTP(C) NFS(S) CIFS(S)
ftp(C) SNMP Agent XFS

Storage Navigator n
DNS(C) NIS(C) LVM
Web browser n
Failover
http
NAS File Sharing Installer
SVP Web server NAS Data Control
RAID Driver Internode Comm

Setup on SVP
Disk subsystem
Storage Navigator Legend: (S): server
(C): client
Windows n: Must be prepared by the user
o: Server required for NAS operations
: Maintenance engineer : System administrator
Figure 2.3-1 Basic Configuration of the NAS Blade System
NAS02-30
NAS02-40 DKC515I
The NAS Blade system operation/management software consists of:

Software on the SVP: Software on the SVP includes Setup on SVP and Storage Navigator.
This software is basically used for operations and management (of the NAS OS and the disk
subsystem) at or below the NAS OS level.
NAS Blade Manager: The software NAS Blade Manager is basically used for operations and
management (of file systems and failover functionality) above the NAS OS level.
Note that the NAS OS includes NAS File Sharing and NAS Data Control.
The system administrator (the customer's operations administrator) uses a Web browser from the
NAS Management Console to give operating instructions to NAS Blade Manager. NAS Blade
Manager receives the instructions, and executes them in accordance with the NAS OS and
application programs in use.
Table 2.3-1 lists the servers and PCs used for the NAS Blade system.
Table 2.3-1 List of NAS Servers and PCs

# Server/PC Description Set up by Mandatory
system
administrator
1 Application server Machine that uses the disk subsystem as the file Yes Yes
server
2 Maintenance server Server that monitors error and performance Yes 
information.
3 NTP server Works with the NTP client of each NAS Yes Yes
Package to synchronize the clock of each NAS
Package.
4 Virus scan server Server running a virus scan software. The file Yes 
that a client accessed is transmitted, and the
virus check and the extermination processing
are performed as required.
5 SVP Server used for maintenance. The SVP is  Yes
incorporated into the disk subsystem and is
operated by the maintenance personnel.
6 Client PC Notebook computer used as a monitor and  Yes
keyboard for SVP.
7 NAS Management PC used by the system administrator to operate Yes Yes
Console NAS Blade Manager.
A Web browser runs on this PC.
8 Storage Navigator PC used by the system administrator to operate Yes 
PC Storage Navigator.
A Web browser runs on this PC.
9 Maintenance When error information cannot be obtained, or Yes 
terminal *1 failure recovery is unsuccessful by regular
procedures, use the command line to obtain
error information, or to recover from the error.
*1: Required when error information cannot be obtained, or regular failure recovery
operations have failed and when requested to use by the developer. Not required for
ordinary operations.
NAS02-40
NAS02-50 DKC515I
Table 2.3-2 lists the programs that make up the NAS.
Table 2.3-2 List of Programs that Make Up the NAS Blade System
1
# Program Description Shipped with NAS Mandatory *
1 Web server Provides browsing functionality via Web Yes Yes
browsers that are compatible with NAS Blade
Manager.
2 NAS Blade Provides basic functionality in the NAS Yes Yes
Manager environment.
3 NAS Backup Provides snapshot and backup/restore Yes 
Restore functionality in the NAS environment. (key management)
4 NAS Anti Virus Provides the functionality for Yes 
Agent protecting data in the disk subsystem (key management)
from viruses, linking with the virus
scan server.
5 NAS Sync Image Provides the differential-data Yes 
snapshot functionality in the NAS (key management)
environment.
6 Setup on SVP Provides NAS OS installation and other setup Yes Yes
functionality when a NAS Package is
installed.
7 SNMP agent Sends error and performance information to Yes 
the maintenance server by using SNMP.
8 NTP client Works with the NTP server to synchronize Yes Yes
the clock of each NAS Package.
9 FTP server Provides an FTP service to maintenance Yes Yes
personnel and system administrators.
10 FTP client Provides an FTP service to maintenance Yes Yes
11 NIS client Works with an NIS server to enable Yes 
management of NFS users, based on the NIS
server
12 DNS client Works with a DNS server to provide DNS Yes 
functionality.
13 Failover Implements failover functionality between Yes Yes
NAS Packages.
14 Installer Performs the initial installation of the NAS Yes Yes
OS in conjunction with the BIOS. Also,
performs installation of various service
programs, and provides license key
management.
15 NFS server Provides file sharing functionality for UNIX Yes Yes*2
clients.
16 CIFS server Provides file sharing functionality for Yes Yes*2
Windows clients.
17 XFS Provides an XFS file system: an enhanced Yes Yes
XFS optimized for NAS. XFS has journaling
functionality.
18 LVM Provides functionality to manage volumes Yes 
flexibly by hiding the physical volume
configuration.
19 NAS Data Control NAS Blade system basic functionality Yes Yes
NAS02-50
NAS02-60 DKC515I

1
# Program Description Shipped with NAS Mandatory *
20 NAS File Sharing NAS operating system Yes Yes
(NAS OS kernel)
21 RAID Driver Driver suitable for RAID functionality. Yes Yes
22 Internode Comm Provides inter-NAS Package communication Yes Yes
functionality, such as Starnet IP.
*1: Yes: Program required for NAS Blade system operation
: Program that might not be used depending on the system.
*2: Either an NFS server or a CIFS server is required.
NAS02-60
NAS02-70 DKC515I
2.4 Minimum and Maximum Configurations

Table 2.4-1 lists the devices and components managed by NAS Blade Manager and the specific
quantities for the minimum and maximum configuration requirements.
Table 2.4-1 Minimum and Maximum Configurations

# Device/component Minimum Maximum Remarks
configuration configuration
1 Disk array device 1 1 
2 NAS boards 2 8 (for flexible cabinet One cluster consists of two NAS
(NAS Packages) model) boards.
Cluster configuration:
A minimum of 1 to a maximum of
4
2 (for rack-mount One cluster consists of two NAS
model) boards.
Cluster configuration: 1
3 Cluster configuration 2 2 Number of boards (NAS Packages)
per cluster
4 Device files 1 *1 256 Limit set to NAS Blade Manager
according to the RAID function
specifications.
(Number of device files per
cluster)
5 Logical volumes 1 *2 256 Limit set by NAS Blade Manager
according to the RAID function
specifications.
(Number of logical volumes per
cluster)
6 XFS file systems 1 *1 256 Limit set by the failover
functionality.
(Number of XFS file systems per
cluster)
7 NFS shares 0 *3 256 Limit set by the failover
functionality.
(Number of NFS shares per
cluster.)
8 CIFS shares 0 *3 256 
(Number of CIFS shares per
cluster)
*1: Although NAS Blade system is operable even if there are no such device or component,
you need at least one in order to use file shares.
*2: NAS Blade system is operable when you use logical volumes, even if there are no such
device or component. However, you need at least one in order to share files.
When you do not use logical volumes, there is no such device or component.
*3: In order to share files, there must be at least one NFS or CIFS share.
NAS02-70
NAS02-80 DKC515I
2.5 Maintenance Personnel

2.5.1 Roles of the Maintenance Personnel and System Administrators
Basically, the maintenance personnel use the SVP (Setup on SVP) and the maintenance terminal to
operate and service the hardware (disk subsystem functionality) and the NAS OS in a NAS Package.
System administrators (NAS Blade system managers) use the NAS Management Console (NAS
Blade Manager) and the Storage Navigator PC to operate and service the functionality above the
NAS OS of the NAS Package. However, system administrators who have already purchased certain
functionality of Storage Navigator can operate and service most of the disk subsystem functionality.
For convenience, system administrators are also capable of operating some of the NAS OS
functionality (for example, specifying network settings or using syslog).
Table 2.5-1 lists key operations performed by the maintenance personnel and system administrators.
NAS02-80
NAS02-90 DKC515I
Table 2.5-1 Key Operations by Maintenance Personnel and System Administrators

# Key operation Maintenance personnel System administrator
SVP Maintenance NAS Remote
terminal *3 Management Console
Console PC
1 Implementing NAS system LUs Available
2 Configuring NAS user LUs Available
3 Installing Setup on SVP Available
4 Installing the NAS OS Available
5 Installing patch versions of the NAS OS Available Available
6 Booting/shutting down/rebooting the NAS OS Available Available*8 Available
7 Installing NAS Blade Manager Available Available
8 Installing/uninstalling optional program Available Available
products of NAS Blade Manager
9 Setting up the license Available Available
10 Setting up the network (fixed IP address or Available*6 Available
NTP)
11 Setting up Partial Cache Residence Available
functionality
12 Setting up the NAS Package cluster Available
configuration
13 Defining configuration of services Available
14 Setting up the network (routing) Available*7 Available
15 Setting up the network (DNS and NIS) Available
16 Creating file systems Available
17 Setting up file shares Available
18 Managing users and groups Available
19 Setting up error monitoring Available
20 Setting up system administrators Available
21 Backing up and recovering system information Available*1 Available*2
22 Performing manual failover or failback Available
23 Obtaining log files Available*4 Available Available
24 Obtaining core dump files Available
25 Obtaining event traces Available*4 Available
26 Obtaining crash dumps Available*5 Available
27 Obtaining hibernation dumps Available*5 Available
28 Obtaining LM dumps Available
*1: The recovery processing only can be executed.
*2: The save processing only can be executed.
*3: Required when ordinary failure recovery operations have failed and when requested to
use by the developer. Not required for ordinary operations.
*4: Obtained by auto dump [NAS07-70].
*5: Obtained by NAS dump [NAS07-70].
*6: Only for the control port.
*7: Only for the control port. The setting for the data port can only be deleted.
*8: Only reboot can be executed when you upgrade the NAS OS.
NAS02-90
NAS02-100 DKC515I
2.5.2 Maintenance Terminal (Not Required for Ordinary Operations)

The maintenance terminal is used to operate the dumps and logs it receives when an error occurs in
the NAS OS. The maintenance personnel use SSH to log in to the NAS Package, and enter
commands on the command line to perform operations in Table 2.5-1 on the dumps and logs.
The FTP protocol is used to send dumps and logs to the maintenance terminal. Thus, an FTP server
should be active at this terminal. If an error occurs, a vast amount of information is stored on the
storage medium. This requires the maintenance terminal to have a storage device with enough space
to accommodate all the information. Table 2.5-2 shows the operating environment recommended
for the maintenance terminal.
Table 2.5-2 Operating Environment Recommended for the Maintenance Terminal

# Item Specifications
1 CPU Environment for operating the FTP server
and CUI interface console
2 Memory Same as above
3 Available hard disk space 40 GB or more
4 Resolution and maximum color Environment for operating the FTP server
count and CUI interface console
5 Keyboard and mouse Need not satisfy any particular conditions.
6 LAN card for TCP/IP networks 10 Base-T or better
7 Operating system Environment for operating the FTP server
and CUI interface console
8 Storage device DAT, DVD-RW, CD-RW, or any other
storage device that can store 4.0 GB or more
data.
9 Others Requires that an FTP server be operating.
NAS02-100
NAS02-110 DKC515I
2.5.3 SSH Account for Maintenance Personnel and System Administrators (Not Required for
Ordinary Operations)
The maintenance personnel and system administrators are provided with one fixed account to log in
to the NAS Package via SSH and execute the commands provided by NAS functionality. This
account is shared in common among the maintenance personnel and system administrators. Without
this account, they cannot perform operations using SSH. Table 2.5-3 shows details of the SSH
account.
Table 2.5-3 SSH Account

# Item Value Remarks
1 User name nasroot Unchangeable
2 User ID 99 Unchangeable
3 Group ID 99 Unchangeable
4 Password - No initial password
5 Comment nasroot
6 Home directory /home/nasroot
7 Shell /bin/bash
NAS02-110
NAS03-10 DKC515I
3. NAS Installation
3.1 Overview
This chapter describes the initial implementation steps from setting up the NAS Blade system
hardware to providing file services to customers. This chapter describes, in detail, the operations
required at or above the level for installing the NAS OS into the NAS Packages (that is, the
operations for software-related functionality), and the functions used by maintenance personnel.
This chapter also gives an overview of the operations required at or below the level for creating
LUs for the disk subsystem (that is, the operations for hardware-related functionality) and the
functionality used by system administrators. For details, see the INSTALLATION Section [INST01-
10].
Table 3.1-1 lists the initial implementation patterns for NAS Blade system. The sections below
describe the operations for each pattern.
Table 3.1-1 Initial Implementation Patterns for NAS Blade system

# Pattern Content
1 New installation The manufacturer (or the supplier in charge of shipment) will be
responsible for setting up the NAS Blade system, up to and including
the installation of the program products (these are operations required
for performing a new installation).
2 On-site installation The manufacturer (or the supplier in charge of shipment) will be
responsible for setting up the hardware only (these are operations
required for installing additional NAS Packages).
3.2 Prerequisites
The following settings are specific to NAS functionality, and must be completed by the time the
setup work required up to the level of creating LUs for the disk subsystem (or, the setup of
hardware-related functionality) is through. Table 3.2-1 lists the items to be set. For details, see the
INSTALLATION Section [INST05-1400].
Table 3.2-1 Hardware-Related Functionality

# Pattern Operated Operated by Content
with
1 Creating NAS SVP Vendor, Creating the LUs for NAS
system LUs maintenance management.
personnel
2 Defining the paths to SVP Vendor, Setting up the paths to the NAS
the NAS system LUs maintenance system LUs in order to make the
personnel NAS Packages recognize the NAS
system LUs.
3 Defining the paths to SVP, Vendor, Setting up the paths to the user
the user LUs Storage maintenance LUs. Defining paths that take into
Navigator personnel account the cluster configuration.
NAS03-10
NAS03-20 DKC515I
3.2.1 Creating NAS System LUs

Unlike other CHAs, a NAS Package requires the following six NAS system LUs:
NAS OS LU to store programs necessary for operation,

NAS Cluster Management LU to store programs necessary for operation,
LU to store a backup of NAS Cluster Management LU,
Dump LU to store error information,
Error information LU to store the edited error information, and the
Command device to operate RAID programs such as ShadowImage.
For information on (the minimum values of) NAS system LU capacities, see the INSTALLATION
Section [INST05-1400].
To prepare NAS system LUs, you must first generate LDEVs by emulating volumes of emulation
types (such as OPEN-8, OPEN-9, OPEN-E, or OPEN-L) on one or more RAID groups, and let the
NAS Blade system use those LDEVs as NAS system LUs.
Table 3.2-2 and Table 3.2-3 show the relationship between the number of clusters and the number
of NAS system LUs for the flexible cabinet model and rack-mount model.
Table 3.2-2 Relationship between the number of clusters and the number of NAS
system LUs (for the flexible cabinet model)
# Cluster NAS Dump Error NAS Cluster Backup LU of Command NAS
OS LU information Management NAS Cluster device system
(Number of NAS
LU LU LU Management LU
Packages)
LU
1 1 (2) 2 2 1 1 2 1 9
2 2 (4) 4 4 1 1 2 1 13
3 3 (6) 6 6 1 1 2 1 17
4 4 (8) 8 8 1 1 2 1 21
Table 3.2-3 Relationship between the number of clusters and the number of NAS
system LUs (for the rack-mount model)
# Cluster NAS Dump Error NAS Cluster Backup LU of Command NAS
OS LU information Management NAS Cluster device system
(Number of NAS
LU LU LU Management LU
Packages)
LU
1 1 (2) 2 2 1 1 2 1 9
NAS03-20
NAS03-30 DKC515I
Either of the following two configurations is applied according to the customer’s request: a
configuration in which NAS system LUs are dispersed among multiple RAID groups, or the
configuration in which the NAS system LUs are put together in one RAID group. Figure 3.2-1
shows an example of how NAS system LUs are configured (the former case showing NAS system
LUs dispersed among multiple RAID groups).
Flexible Cabinet Model

RAID group RAID group RAID group RAID group
NAS OS LUs Dump LUs NAS OS LUs Dump LUs
for CHA-1E for CHA-1E for CHA-2Q for CHA-2Q

NAS Cluster
Management LU Backup LU of
NAS CM LU
for CHA-1F for CHA-1F for CHA-2R for CHA-2R
Error Information
LU
for CHA-1G for CHA-1G for CHA-2T for CHA-2T Backup LU of
NAS CM LU
Command device
for CHA-1H for CHA-1H for CHA-2U for CHA-2U
Rack-mount Model
RAID group RAID group RAID group RAID group
NAS OS LUs Dump LUs NAS OS LUs Dump LUs
NAS Cluster
Management LU Backup LU of
NAS CM LU
for CHA-1B for CHA-1B for CHA-2E for CHA-2E Error Information
LU
Backup LU of
NAS CM LU
Command device
Figure 3.2-1 Examples of NAS System LU Configurations
NAS03-30
NAS03-40 DKC515I
3.2.2 Defining the Paths to NAS System LUs

The path to a NAS system LU is defined by setting the IID and LUN respectively with the values
shown in the tables below.
An IID (initiator ID) is an ID that indicates that the LU indicated by the LU-number is either a NAS
system LU or a user LU. One of the following numbers appears:
0: Displays when the target LU is an NAS system LU.
1: Displays when the target LU is a user LU.
[1] Defining paths to the NAS OS LU and the dump LU

The following paths to a NAS OS LU and a dump LU need to be defined separately:
from a local NAS Package
from other NAS Packages
Such paths from other NAS Packages are defined so that various types of information (such as
error information and definitions) can be collected from the other NAS Package in the same
cluster when one NAS Package goes down.
Table 3.2-4 and Table 3.2-5 show definitions of paths from its own NAS Package to the NAS
system LU, and from other NAS Packages to the NAS system LU.
Table 3.2-4 shows that a path from a local NAS Package to its own NAS OS LU or own dump
LU is always defined by the IID and LUN.
Table 3.2-4 Definitions of Paths from a NAS Package to NAS System LUs (When
the NAS System LUs Are The NAS Package’s Own NAS System LUs)
# NAS System LU IID LUN
1 NAS OS LU 0 00
2 Dump LU 0 01
Table 3.2-5 shows that paths from a NAS Package to other NAS OS LUs or other dump LUs
(that is, these NAS system LUs are not the NAS Package’s own system LUs) are defined by
the NAS Package-specific IID and LUN.
NAS03-40
NAS03-50 DKC515I
You need not manually define paths from a NAS Package to other NAS OS LUs or other dump
LUs, because the paths shown in Table 3.2-5 are defined automatically after you have defined
the paths from a NAS Package to its own NAS OS LU or dump LU.
Table 3.2-5 Definitions of Paths from a NAS Package to NAS System LUs (When
the NAS System LUs Are Not the NAS Package’s Own NAS System LUs)
Flexible Cabinet Model

# NAS system LU IID LUN
1 NAS OS LU for CHA-1E 0 0B
2 NAS OS LU for CHA-1F 0 0C
3 NAS OS LU for CHA-1G 0 0D
4 NAS OS LU for CHA-1H 0 0E
5 NAS OS LU for CHA-2Q 0 0F
6 NAS OS LU for CHA-2R 0 10
7 NAS OS LU for CHA-2T 0 11
8 NAS OS LU for CHA-2U 0 12
9 Dump LU for CHA-1E 0 1B
10 Dump LU for CHA-1F 0 1C
11 Dump LU for CHA-1G 0 1D
12 Dump LU for CHA-1H 0 1E
13 Dump LU for CHA-2Q 0 1F
14 Dump LU for CHA-2R 0 20
15 Dump LU for CHA-2T 0 21
16 Dump LU for CHA-2U 0 22
Rack-mount Model
# NAS system LU IID LUN
1 NAS OS LU for CHA-1B 0 0C
2 NAS OS LU for CHA-2E 0 10
3 Dump LU for CHA-1B 0 1C
4 Dump LU for CHA-2E 0 20
NAS03-50
NAS03-60 DKC515I
[2] Defining paths to a command device, error information LU, NAS Cluster Management LU,
and backup LU of NAS Cluster Management LU
The paths to a command device, error information LU, and NAS Cluster Management LU are
respectively defined by the IID and LUN as shown in Table 3.2-6.
Table 3.2-6 Definitions of Paths to a Command Device, Error Information LU, and
NAS Cluster Management LU
# NAS System LU IID LUN
1 Command device 0 05
2 Error information LU 0 06
3 NAS Cluster Management LU 0 08
4 Backup LU of NAS Cluster 0 09
Management LU
5 Backup LU of NAS Cluster 0 0A
Management LU
CAUTION
To delete a path to a NAS system LU, you must first stop the NAS OS on the NAS
Package that has the NAS system LU. Use Setup on SVP to stop the NAS OS, and then
delete the path.
NAS03-60
NAS03-70 DKC515I
Rev.2 / Nov.2005, Jun.2006 Copyright © 2005, 2006, Hitachi, Ltd.
3.2.3 Defining Paths to User LUs

The value 1 is used for the IID to define a path to a user LU.
Each user LU must be shared by the two NAS Packages in the cluster, and its path from any NAS
Package must be defined using the same LUN.
Note: To define the paths to user LUs, you must specify the LUNs by using odd numbers and even
numbers evenly. This definition is required to obtain adequate I/O processing performance of an
NAS Package. If you specify the LUNs by using either odd numbers only or even numbers only,
I/O processing performance might be inadequate because one of the MPs in the NAS Package
processes even-numbered LUNs, and the other MP processes odd-numbered LUNs. (If an error
occurs, the MPs might process LUNs differently.)
Figure 3.2-2 shows an example of defined paths to user LUs.
cluster1 cluster2
CL1-CHA CL2-CHA CL1-CHA CL2-CHA
LUN=0 LUN=0 LUN=0 LUN=0

The LU which has same
LUN of CL1-CHA and
CU#0 CU#0 CL2-CHA must be
LDEV#0 LDEV#3 defined for the same CU.
LUN=1 LUN=1 LUN=1 LUN=1 Do not define the same

CU#:LDEV# over
CU#0 CU#1 clusters. (CU#:LDEV#
LDEV#1 LDEV#0 must be unique among
clusters.)
Figure 3.2-2 Example of How Paths to User LUs are Defined
CAUTION
The path to a user LU that is used as a file system by the NAS Blade system (that is, the
LUN assigned to a user LU) cannot be deleted.
NAS03-70
NAS03-71 DKC515I
Rev.0 / Dec.2005 Copyright © 2005, Hitachi, Ltd.
3.2.4 Set up the NAS Time Zone

Set NAS time zone as described below.
(1)
Change the mode to [Modify Mode] (CL).
(2)
Select (CL) [Install].
(3)
Select (CL) [Set Subsystem Time] in the
‘Install’ window.
(4)
Select (CL) [NAS Time Zone] in the ‘TOD change’
window.
NAS03-71
NAS03-72 DKC515I
Rev.0 / Dec.2005 Copyright © 2005, Hitachi, Ltd.
(5)
The ‘TOD change (NAS Time Zone)’ window
appears.(The current NAS time zone is
displayed.)Select the desired NAS time zone
from the drop-down list and select (CL) [OK].
The details of the setting will be provided.
Please follow the instruction.
(6)
After selecting the NAS time zone, select (CL)[OK]
in the ‘TOD change’ window.
(7)
Close the ‘Install’ window.
NAS03-72
NAS03-80 DKC515I
3.3 New Installation (Setup Performed By the Manufacturer)

Table 3.3-1 lists the procedure for installing a NAS Blade system for the first time. The shaded
parts in the table indicate tasks for which the maintenance personnel are responsible.
Table 3.3-1 Procedure for Installing NAS Blade system for the First Time
(Setup Performed by the Manufacturer)
Step Process Location Operated with Operated by Task Description Reference
1 CT0 (RSD) SVP Vendor Create NAS system LUs *1
2 Install Setup on SVP 3.5.2 [1]
[NAS03-110]
3 Set up the NAS Time Zone 3.2.4
[NAS03-71]
4 Install the NAS OS and related 3.5.4
Setup on SVP Vendor
program products [NAS03-290]
5 NAS setup Setup on SVP Vendor Set up the control port network 8.1[1]
(fixed IP address, routing, NTP) [NAS08-20]
6 Set up the license 8.1[2]
[NAS08-160]
7 SVP Set up the cluster configuration 8.2[1]
(NAS Blade Manager) [NAS08-210]
8 On-site Maintenance Confirm the settings 8.3
personnel [NAS08-400]
9 Web Console System Set up the Partial Cache Residence ---
administrator functionality
10 NAS Blade Manager Account Set up system administrator(s) 3.6.1
administrator [NAS03-1290]
11 System Define the configuration for the 3.6.3
administrator services (e.g., NFS, CIFS) [NAS03-1290]
[Service management]
12 Set up the control port and data port 3.6.4
network (fixed and service IP [NAS03-1300]
addresses, routing)
13 Set up the network (DNS, NIS) 3.6.5
[NAS03-1300]
14 Manage users and groups [User 3.6.6
management] [NAS03-1310]
15 Create the file systems 3.6.7
[File sharing management] [NAS03-1310]
16 Set up file shares (NFS/CIFS) 3.6.8
17 Specify settings related to error- 3.6.9
monitoring functionality [Error [NAS03-1320]
information (RAS) management]
*1: (1) See [INST05-520] in the INSTALLATION Section to select LUN Manager.
(2) See [INST05-1360] in the INSTALLATION Section to create a NAS system LU.
For more information on the content and procedures of each task, see 3.5 Operations on the SVP
[NAS03-100], 8. Setup Procedures When Implementing NAS Blade System for the First Time
[NAS08-10], and 3.6 Operations Using the NAS Blade Manager GUI [NAS03-1290].
NAS03-80
NAS03-90 DKC515I
3.4 On-Site Installation (On-Site Setup)

Table 3.4-1 lists the procedure for the NAS Blade system on-site installation (on-site setup). On-site
installation applies when additional NAS Packages need to be installed. On-site installation differs
from a new installation in the settings (from “Create NAS system LUs” to “Set up the network
(Fixed IP address, NTP) provisionally”) that are performed on site by the maintenance personnel.
The shaded parts in the table indicate the tasks for which maintenance personnel are responsible.
Table 3.4-1 Procedure for NAS Blade System On-Site Installation (On-Site Setup)
Step Process Location Operated with Operated by Task Description Reference
1 NAS Setup On-site SVP Maintenance Create NAS system LUs *1
personnel
2 Install Setup on SVP 3.5.2 [1]
[NAS03-110]
3 Set up the NAS Time Zone 3.2.4
[NAS03-71]
4 Setup on SVP Maintenance Install the NAS OS and related 3.5.4
personnel program products [NAS03-290]
5 Set up the control port network 8.1[1]
(Fixed IP address, routing, NTP) [NAS08-20]
6 Set up the license 8.1[2]
[NAS08-160]
7 SVP Setup the cluster configuration 8.2[1]
(NAS Blade Manager) [NAS08-210]
8 Confirm the settings 8.3
[NAS08-400]
9 Web Console System Set up the Partial Cache Residence ---
administrator functionality
10 NAS Blade Manager Account Set up the system administrator(s) 3.6.1
administrator [NAS03-1290]
11 System Define the configuration for 3.6.3
administrator services (e.g., NFS, CIFS) [NAS03-1290]
[Service management]
12 Set up the control port and data port 3.6.4
network (Fixed and service IP [NAS03-1300]
addresses, routing)
13 Set up the network (DNS, NIS) 3.6.5
[NAS03-1300]
14 Manage users/groups 3.6.6
[User management] [NAS03-1310]
15 Create the file systems 3.6.7
16 Set up file shares (NFS/CIFS) 3.6.8
17 Specify settings related to error- 3.6.9
monitoring functionality [Error [NAS03-1320]
information (RAS) management]
18 Specify settings related to the 3.6.10
save function for NAS [NAS03-1320]
system LUs
NAS03-90
NAS03-91 DKC515I
*1: (1) See [INST05-520] in the INSTALLATION Section to select LUN Manager.
(2) See [INST05-1360] in the INSTALLATION Section to create a NAS system LU.
For more information on the content and procedures of each task, see 3.5 Operations on SVP
[NAS03-100], 8. Setup Procedures When Implementing NAS Blade System for the First Time
[NAS08-10], and 3.6 Operations Using the NAS Blade Manager GUI [NAS03-1290].
NAS03-91
NAS03-100 DKC515I

This section describes maintenance personnel operations on the SVP.
3.5.1 Overview of Setup on SVP

Setup on SVP is used to install programs (such as the NAS OS and related program products) to the
NAS Packages and to set up a basic network for accessing the NAS Packages from a public LAN.
The following figure shows the entire configuration of Setup on SVP.
Disk subsystem
CHA-2U
CHA-1F
CHA-1E
Optional program product
NAS Blade Manager

for CHA-2U
NAS OS
Maintenance for CHA-1F
personnel
for CHA-1E NAS OS LU
SVP
Setup on SVP
Media supplied
(Setup on SVP installer,
NAS Blade system programs)
Figure 3.5-1 Entire Configuration of Setup on SVP (for a Flexible Cabinet Model)
NAS03-100
NAS03-110 DKC515I
3.5.2 Implementing Setup on SVP

[1] Installing Setup on SVP ------------------------------------------------------------------ NAS03-110
[2] Starting and stopping Setup on SVP ---------------------------------------------------- NAS03-180
[3] Uninstalling Setup on SVP --------------------------------------------------------------- NAS03-200
[4] Checking the Setup on SVP version ---------------------------------------------------- NAS03-251
[1] Installing Setup on SVP

When you install Setup on SVP, the following two programs are installed:
PXE Server Suite
Setup on SVP
Note: Installing Setup on SVP:

If you use the SVP high availability kit, keep the following points in mind when installing Setup on
SVP:
Make sure that you install Setup on SVP on both SVPs.
When you upgrade Setup on SVP, make sure that you upgrade Setup on SVP on both SVPs.
If you replace one of the SVPs due to some failure, make sure that you install Setup on SVP on
the new SVP.
When the Web Console is being used, it must be stopped in advance because SVP is rebooted.
To install Setup on SVP:
(1) Make sure that the NAS Setup button is not displayed in the ‘SVP’ window.
If the NAS Setup button is displayed, see 3.5.2 [3] Uninstalling Setup on SVP and
uninstall Setup on SVP [NAS03-200].
(2) Insert the Setup on SVP installer (CD-ROM) into the CD drive of the SVP.
(3) Close all windows except for the ‘SVP’ window.
(4) Click the Start button to display the Start menu, and then choose Run.
NAS03-110
NAS03-120 DKC515I
(5) Type e:\setup.bat in Open:, and then click the OK button.
(6) The following window appears.

Press any key to continue.
(7) The following window appears temporarily.

PXE Server Suite Installer will execute automatically.
Do not perform any operation on this window, and go to step (8).
Note: Do not use the mouse or keyboard during this step.
NAS03-120
NAS03-130 DKC515I
(8) The following window appears temporarily before PXE Server Suite Installer starts.
(9) When PXE Server Suite Installer is ready to start, the following window appears.
Click the Next button.
NAS03-130
NAS03-140 DKC515I
(10) Click the [Install] button to start installation of PXE Server Suite.
(11) Installation of PXE Server Suite starts, and the progress of installation is displayed.
NAS03-140
NAS03-141 DKC515I
(12) When the installation of PXE Server Suite finishes, the following window appears.
Click the Finish button.
Note: When the message "You must restart your system for the configuration changes
made to PXE Server Suite to take effect." appears, click the No button.
NAS03-141
NAS03-150 DKC515I

Follow the message displayed in the window, and wait for about 10 seconds.
(14) The message “Starting installation of [Setup on SVP].” appears.

When the message “Press any key to continue...” appears, press any key.
NAS03-150
NAS03-160 DKC515I
(15) Installation of Setup on SVP starts.

Go to step (16).
Note: Setup on SVP Installer runs in the background, and so no messages or dialog boxes
will be displayed during the installation.
(16) The message “The NAS Setup on SVP installation has finished successfully.” is
displayed.
Click the OK button in the message window.

NAS03-160
NAS03-170 DKC515I
(18) The message “End of the installation of [PXE Server Suite] and [Setup on SVP].” appears.
(19) The command prompt window closes automatically.

Remove the Setup on SVP installer (CD-ROM) from the CD drive of the SVP.
(20) Follow the procedures in the SVP Section:

(19-1) First, perform the <Power Off> operation in 1.8 [SVP01-110].
(19-2) Next, perform the <Power On> operation in 1.7 [SVP01-100].
(19-3) Last, perform the <Connecting the PC to the SVP> operation in 1.4 [SVP01-60].
(21) Make sure that the NAS Setup button is displayed on the ‘SVP’ window.
(22) Installation of Setup on SVP finishes.
NAS03-170
NAS03-180 DKC515I
[2] Starting and stopping Setup on SVP

To start and stop Setup on SVP:
(1) In the ‘SVP’ window, change View Mode to Modify Mode.
(2) Click the NAS Setup button to start Setup on SVP.
Note: The NAS Setup button can be used in Modify Mode only.
NAS03-180
NAS03-190 DKC515I
(3) Make sure that ‘NAS Setup on SVP (Main)’ window appears.
<Flexible Cabinet Model>
<Rack-mount Model>
NAS03-190
NAS03-195 DKC515I
Rev.0 / Jun.2005 Copyright © 2005, Hitachi, Ltd.
(4) To stop Setup on SVP (the NAS Setup program); click the Close button in the ‘NAS
Setup on SVP (Main)’ window.
Note: To finish Setup on SVP (the NAS Setup program), you must close all windows that
have been opened by using the buttons of the ‘NAS Setup on SVP (Main)’ window.
(5) If you are using SVP High Reliability Kit:

After setting up the basic SVP (basic); perform the SVP switching procedure described in
SVP Section [SVP02-1150], and then perform step (1) to (21) in [1] [NAS03-110] and step
(1) to (5) in [2] [NAS03-180] for the additional SVP (optional). After setting up the
additional SVP (optional), switch the SVP to operate to the basic SVP (basic) according to
the SVP switching procedure in SVP Section [SVP02-1150].
NAS03-195
NAS03-200 DKC515I
[3] Uninstalling Setup on SVP

When you uninstall Setup on SVP, the following two programs are uninstalled:
PXE Server Suite
Setup on SVP
Note: Uninstalling Setup on SVP:

Keep the following points in mind when uninstalling Setup on SVP:
If you want to remove the NAS functionality from the DKC, make sure that you delete all NAS
Packages first, and then perform this operation (uninstallation).
If you use the SVP high availability kit, make sure that you uninstall Setup on SVP from both
SVPs.
To uninstall Setup on SVP:
(1) Make sure that the NAS Setup button is displayed in the ‘SVP’ window.
If the NAS Setup button is not displayed, Setup on SVP has already been uninstalled, and
so this operation (uninstallation) is unnecessary.
(2) Insert the Setup on SVP installer (CD-ROM) into the CD drive of the SVP.
(3) Close all windows except the ‘SVP’ window.
(4) Make sure that Setup on SVP is not running.

If it is running, stop Setup on SVP.
(5) Click the Start button to display the Start menu, and then choose Run.
(6) Type e:\setup.bat in Open:, and then click the OK button.
NAS03-200
NAS03-210 DKC515I

(8) Pre-processing of the PXE Server Suite uninstallation is executed, and the following
window appears.
Note: Do not use the mouse or keyboard during this step
NAS03-210
NAS03-220 DKC515I
(9) Click the Start button to display the Start menu, and then choose Control Panel.
(10) The ‘Control Panel’ window appears.

Double-click (execute) Add/Remove Programs.
NAS03-220
NAS03-230 DKC515I
(11) The ‘Add/Remove Programs’ window appears.

From Change or Remove Programs, select PXE Server Suite, and then click the
Remove button.
Note: If you remove an inappropriate program, the SVP might not run properly.
(12) The message “Are you sure you want to remove PXE Server Suite from your computer?”
is displayed.
Click the Yes button in the message window.
(13) Uninstallation of PXE Server Suite starts (this is the post-processing of this uninstallation
procedure), and the progress is displayed.
Got to step (14).
NAS03-230
NAS03-240 DKC515I
(14) Make sure that PXE Server Suite is not displayed in Change or Remove Programs in
the ‘Add/Remove Programs’ window.
(15) Click the 7 button in the ‘Add/Remove Programs’ window to close the ‘Add/Remove
Programs’ window.
(16) Click the 7 button in the ‘Control Panel’ window to close the ‘Control Panel’ window.

NAS03-240
NAS03-250 DKC515I
(18) The message “End of the uninstall of [PXE Server Suite] and [Setup on SVP].” appears.
(19) The window closes.

Remove the Setup on SVP installer (CD-ROM) from the CD drive of the SVP.
(20) Follow the procedures in the SVP Section:

(20-1) First, perform the <Power Off> operation in 1.8 [SVP01-110].
(20-2) Next, perform the <Power On> operation in 1.7 [SVP01-100].
(20-3) Last, perform the <Connecting the PC to the SVP> operation in 1.4 [SVP01-60].
(21) Make sure that the NAS Setup button is not displayed in the ‘SVP’ window.
(22) Right-click the Start button, start Explorer, and then make sure that the C:\CHNMGR
folder and C:\dhcp.ini file do not exist.
Uninstallation of Setup on SVP finishes.
NAS03-250
NAS03-251 DKC515I
[4] Checking the Setup on SVP version

To check the version of Setup on SVP:
(3) Right-click on the title bar of the ‘NAS Setup on SVP (Main)’ window, and then click
About Setup on SVP.
NAS03-251
NAS03-252 DKC515I
<Rack-mount Model>
(4) The ‘About Setup on SVP’ window is displayed.
(Display example)
NAS03-252
NAS03-260 DKC515I
3.5.3 NAS Package Status

When the NAS Setup button is selected in Modify Mode in the ‘SVP’ window, the ‘NAS Setup on
SVP (Main)’ window appears.
This section describes the related statuses of the NAS Package and the function buttons.
Figure 3.5-2 shows the ‘NAS Setup on SVP (Main)’ window.
Note: The status displayed in the ‘Setup on the SVP (Main)’ Window is refreshed approximately
every 20 seconds. The displayed status of the NAS Package can be different from the actual one
because of this time lag.
NAS Package buttons (radio

buttons)
Clicking the button of an installed
NAS Package selects the NAS
Package.
Only one NAS Package can be
selected at one time.
Function buttons (push buttons) for

the particular NAS Package
These buttons become
active/inactive according to the
status of the selected NAS Package.

all NAS Packages in the NAS Blade
system
status of the NAS Packages.
<Rack-mount Model>
NAS Package buttons (radio buttons)

Clicking the button of an installed
NAS Package selects the NAS
Package.
Only one NAS Package can be
selected at one time.

the particular NAS Package
active/inactive according to the status
of the selected NAS Package.

all NAS Packages in the NAS Blade
system
status of the NAS Packages.
Figure 3.5-2 ‘NAS Setup on SVP (Main)' Window

NAS03-260
NAS03-270 DKC515I
Table 3.5-1 shows the relationship between the string in the status displayed ‘NAS Setup on SVP
(Main)’ window, the status of the NAS Package, and the action by maintenance personnel.
Table 3.5-1 Relationships among the String in the Status Area, the Status of the
NAS Package, and the Action by Maintenance Personnel
String Displayed in Status of the NAS Package Action by maintenance personnel
Status Area
NEW The NAS OS is not installed. ---
INST The NAS OS is being installed. ---
ACTIVE Both the NAS OS and node is ---
running
STOP The NAS OS has stopped
normally.
DOWN The NAS OS has stopped Acquire detailed information by using Auto Dump and
abnormally. ask the developer for an investigation. For the
procedures, see the NAS Section [NAS07-70].
BOOT The NAS OS is being started.
SHUTDOWN The NAS OS is being stopped. ---
INACTIVE The NAS OS is running and the ---
node is stopped
(including when the cluster is
not configured or the cluster
service to which the node belong
is stopped).
DUMP The hibernation dump is being ---
collected.
DUMPSKIP The collection of the hibernation ---
dump is being skipped.
HUNGUP The NAS OS is in hung-up state. (1) Ask the system administrator about the NAS OS
status. If it is running, perform (2). If not, perform (3).
(2) Obtain the hibernation dump according to the
procedure in subsection 3.5.10 Collecting the
Hibernation Dump [NAS03-910]. Acquire detailed
information by using Auto Dump and ask the
developer for an investigation. For the procedures, see
page [NAS07-70].
(3) Take the following action when users are not
accessing the NAS Package.
- Reset the CHA according to the procedure in
subsection 3.5.9 Resetting CHA [NAS03-880].
- Start the NAS OS according to the procedure in
subsection 3.5.8 Controlling the NAS OS (Stopping,
Starting, and Restarting) [NAS03-780].
- Acquire detailed information by using Auto Dump
and ask the developer for an investigation. For the
procedures, see page [NAS07-70].
NAS03-270
NAS03-271 DKC515I
Rev.1 / May.2005, Jun.2006 Copyright © 2005, 2006, Hitachi, Ltd.

String Displayed in Status of the NAS Package Action by maintenance personnel
Status Area
PANIC The NAS OS is in an abnormal After the status changes to DOWN, obtain a crash
state. dump according to the procedure in subsection
(The crash dump is being 3.5.15 Downloading Dump Files [NAS03-1080].
collected.) Get the detailed information by executing the Auto
Dump (see page NAS07-70) and request the
Technical Support Division to examine the cause of
the trouble.
WARN (1) NAS Blade Manager is not (1) Check if NAS Blade Manager is installed in the
installed. Program Install window. If so, perform (2). If not,
(2) The NAS OS is running and install NAS Blade Manager.
the node status is unknown. (2) Acquire detailed information by using Auto
Dump and ask the developer for an investigation.
For the procedures, see page [NAS07-70].
UNKNOWN The NAS OS cannot Acquire detailed information by using Auto Dump
communicate with Setup on and ask the developer for an investigation. For the
SVP. procedures, see page [NAS07-70].
FATAL No operation can be performed. Acquire detailed information by using Auto Dump and
ask the developer for an investigation. For the
procedures, see page [NAS07-70].
Check the subsystem status in the Maintenance
window, and the error logs in the Information window.
For the procedures, see the SVP Section [SVP02-30]
[SVP03-10].
Setup on SVP must be restarted after the error cause is
removed.
NAS03-271
NAS03-280 DKC515I
Using the ‘NAS Setup on SVP (Main)’ window enables you to select the NAS Package on which an
operation is to be performed, and choose desired function buttons. Table 3.5-2 shows the function
buttons in the ‘NAS Setup on SVP (Main)’ window.
Table 3.5-2 Function Buttons in the ‘NAS Setup on SVP (Main)’ Window
Button name Description Reference
Program Install A Window for installing and uninstalling the NAS OS and 3.5.4
program products appears. You can install the NAS OS and [NAS03-290]
NAS Blade Manager, or install and uninstall optional program 3.5.5
products for the selected NAS Package. [NAS03-590]
Setting A window for setting network information appears. You can 3.5.6
specify network settings, such as the fixed IP address of the [NAS03-620]
NAS Package, and NTP server.
Boot Management A window for controlling the NAS OS appears. You can start, 3.5.8
stop, or restart the NAS OS (the OS for the NAS Blade system). [NAS03-780]
You can also reset CHA. 3.5.9
[NAS03-880]
Hibernation Dump A window for collecting the hibernation dump appears. You can 3.5.10
also stop dump collection by clicking the Cancel button. [NAS03-910]
Download Dump A window for downloading dump files appears. 3.5.15
[NAS03-1080]
Restore NAS OS LU A window for restoring data in the NAS OS LU appears. 3.5.12
[NAS03-990]
Install Device A window for selecting the install device appears. 3.5.14
[NAS03-1075]
Multi Install A window for installing the NAS OS and relevant program 3.5.4
products appears. You can install the NAS OS, NAS Blade [NAS03-290]
Manger, or optional program products for the selected multiple
NAS Packages in one operation.
License Management A Window for setting the licenses for optional program products 3.5.7
appears. [NAS03-650]
Refer Configuration Information on program products installed on the NAS Package 3.5.11
and network settings is displayed one by one in view mode. [NAS03-960]
(You can view, but not modify, the settings.)
Restore NAS CM LU A window for restoring data in the NAS Cluster Management 3.5.13
LU appears. [NAS03-1040]
Close The Main window closes and Setup on SVP ends. ---
CAUTION
Do not minimize the remote desktop while operating the Setup on SVP. If the remote
desktop is minimized during the operation, the message dialog box may not be displayed
at the forefront. If you choose to minimize remote desktop, check the task bar often to
make sure that a dialog box is not hidden.
NAS03-280
NAS03-290 DKC515I
3.5.4 Installing the NAS OS and Related Program Products

You can install the NAS OS (NAS Data Control and NAS File Sharing), NAS Blade Manager, and
related optional program products to a NAS Package.
There are four types of installation as shown in [1] to [4].
[1] NAS OS installation for the first time--------------------------------------------------- NAS03-310

[2] NAS OS expansion installation---------------------------------------------------------- NAS03-400
[3] Optional program product installation-------------------------------------------------- NAS03-490
[4] NAS OS installation for the first time (Multi-Installation)--------------------------- NAS03-521
[5] NAS OS expansion installation (Multi-Installation)---------------------------------- NAS03-522
[6] Optional program product installation (Multi-Installation)-------------------------- NAS03-523
[7] Installation Containing LU Initialization (Use this procedure by developers' instruction only
when the error cannot be corrected) ------------------------------------------------------- NAS03-530
Table 3.5-3 shows the installation types and meaning.
Table 3.5-3 NAS OS installation, related program product installation, and related
tasks
Installation type Meaning
[1] NAS OS installation for the first time Install the NAS OS and NAS Blade Manager on the disk
subsystem for the first time.
[2] NAS OS expansion installation Install the NAS OS and NAS Blade Manager, in the
NAS Package added on the disk subsystem that has the
NAS functionality.
[3] Optional program product installation Install the optional program product (for the first time or
for expansion).
[4] NAS OS installation for the first time Install the NAS OS and NAS Blade Manager on the disk
(multi-installation) subsystem for the first time. You can install them on
multiple NAS Packages in one operation.
[5] NAS OS expansion installation Install the NAS OS and NAS Blade Manager, in the
(multi-installation) NAS Package added on the disk subsystem that has the
NAS functionality. You can install them on multiple
NAS Packages in one operation.
[6] Optional program product installation Install the optional program product (for the first time or
(multi-installation) for expansion). You can install them on multiple NAS
Packages in one operation.
[7] Installation Containing LU Initialization Initialize the LU and install the NAS OS when the error
(Use this procedure by developers' instruction cannot be corrected. Developers' instruction is required
only when the error cannot be corrected) to perform this procedure.
Notes:
As a rule, you must install the same program products and versions into NAS Packages (e.g. CHA-
1E and CHA-2Q or CHA-1F and CHA-2R for a flexible cabinet model, and CHA-1B and CHA-2E
for a rack-mount model) on the same cluster.
NAS03-290
NAS03-295 DKC515I
CAUTION
If you plan to expand or reduce a NAS Package, first close the NAS Setup on SVP
window, and then re-open it.
CAUTION
If you install NAS PP with a client PC drive set for the Install Device, keep the other PCs
from accessing SVP as client PCs during installation. If any other PC accesses SVP,
installation might fail and the system might not be able to start.
NAS03-295
NAS03-300 DKC515I
Before starting installation, choose an appropriate installation type based on the flow chart shown
below. Once the installation type is determined, perform installation from the SVP and the Setup on
SVP window according to the installation procedures.
Installing the NAS software.

Is NAS OS installed in the subsystem for the first time?
NO
Is NAS OS installed? *1
YES
[3] Optional program product

installation
[NAS03-490]
NO
Is NAS OS installed in
the subsystem for the
first time?
YES
[Install NAS OS in
[2] NAS OS expansion installation
subsystem for the first time]
Make sure that the status of all [NAS03-400]
NAS Packages in the
subsystem is NEW.
[NAS03-260]
[1] NAS OS installation for the first

time [NAS03-310]
*1 Install the NAS Blade Manager concurrently.
Figure 3.5-3 Installation Type Flowchart
NAS03-300
NAS03-310 DKC515I
[1] NAS OS installation for the first time
To install the NAS OS:
(1) Insert the NAS OS media (CD-ROM) into the CD drive of the SVP.
Note: If you want to use the CD-ROM drive of another machine (SVP or client PC), see
3.5.14 Selecting the Install Device [NAS03-1075] to change the machine and drive that
you insert the media into.
Note: Close all windows except for the ‘SVP’ window during ‘NAS Setup on SVP’ is
running.
NAS03-310
NAS03-311 DKC515I
(4) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package to be installed, and
then click the Program Install button.
Note: If you use SVP as the machine that you insert the media into, we recommend that
you install the NAS OS on 4 or less NAS Packages at the same time. If you use a client
PC, we recommend that you install the NAS OS on 2 or less NAS Packages at the same
time.
CAUTION
When the NAS OS is to be installed to the subsystem for the first time, the NAS Cluster
Management LU is initialized. Therefore you must first install the NAS OS only. When the
NAS OS is installed to the first NAS Package successfully, you can install the NAS OS on
another NAS Package in parallel. (While you are installing the NAS OS on one NAS
package, you can install it on any other ones.) The message "Installation will be canceled
because the NAS Cluster Management LU and the Error Information LU are being
initialized by another task." appears if any other NAS OS installation is attempted during
the NAS OS installation on the first NAS Package, and these installations for other NAS
packages are rejected. After the NAS OS installation for the first NAS Package finishes,
install the NAS OS on the other NAS packages.
NAS03-311
NAS03-320 DKC515I
(5) The ‘NAS Setup on SVP (Program Install)’ window appears.

From a list of the program products displayed in Program Product in Media, select the
program product to be installed (NAS OS (NAS Data Control, NAS File Sharing), and
NAS Blade Manager).
Note: You can install NAS OS and NAS Blade Manager concurrently when you install
NAS OS for the first time.
A list of the installed

program products is
displayed. You can select
only one program product,
and cannot select multiple
program products.
Becomes active when an

item in the above list is
selected. Clicking this
button uninstalls the
selected optional program
product.
The program products

stored in the supplied NAS
OS media are displayed.
You can select m ultiple
items at one time.
If you select an item from

the above list, this button
becomes active. Clicking
this button installs the
selected program product.
(Display example)
CAUTION
Except for failure recovery purposes, you do not need to select NAS Cluster
Management LU and Error Information LU in the Initialize area.
You need to enter a password to select these check boxes and continue the operation.
Contact the Technical Support Division (TSD) to confirm the validity of the operation and
obtain the password.
NAS03-320
NAS03-330 DKC515I
(6) The message “The NAS OS will be installed for the first time. …” appears.
(7) The message “You are installing the NAS OS on the disk subsystem for the first time. …”
appears.
The installation starts.
NAS03-330
NAS03-340 DKC515I
(8) The ‘NAS Setup on SVP (Install Progress)’ window appears, and then the installation
progress for the selected program product is displayed. If you selected multiple program
products, the installation starts in descending order from the top item.
When installation finishes successfully, go to step (10).
Note: It takes approximately 10 minutes to install the NAS OS in one NAS Package, and
up to 90 minutes to install it in more than one NAS Package at the same time.
Note: Select (CL) [Cancel (the leftover products)] if you want to cancel subsequent PP
installation.
(Display example)
(9) If installation of the NAS OS finished abnormally:
(9-1)
If a message whose ID is ENSxxxxx appears, see the SVP MESSAGE Section for the
corresponding action to take.
(9-2)
Make sure that there is no blocked part or error in the ‘SVP (Maintenance)’ window. If
there is a blocked part or an error, see the SVP Section [SVP02-30] [SVP03-10], and then
take action.
(9-3)
If the Status area in the ‘Install Progress’ window remains at 1%, and then installation
finishes abnormally, use the following procedure to check the Event Viewer of the SVP.
NAS03-340
NAS03-350 DKC515I
Rev.1 / May.2005, Jul.2006 Copyright © 2005, 2006, Hitachi, Ltd.
(9-3-1)
Click the Start button to display the Start menu, and then choose Control Panel.
(9-3-2)
The ‘Control Panel’ window appears.
Double-click Administrative Tools.
NAS03-350
NAS03-360 DKC515I
(9-3-3)
Double-click Event Viewer.
(9-3-4)
From the tree display, click Application Log.
NAS03-360
NAS03-370 DKC515I
(9-3-5)
In the Event column, check if DHCP Server error 1009 was reported at the time the
installation failed.
(9-3-6)
If there is a DHCP error 1009, double-click the error and check the description.
If the above error does not exist, remove the NAS OS media (CD-ROM) from the CD
drive of the SVP, reboot the SVP PC, and then install the NAS OS from step (1).
If the same phenomenon occurs three times, contact the Technical Support Division
(TSD).
NAS03-370
NAS03-380 DKC515I
(9-3-7)
Check if the error description includes the following sentence:
IP address requested different than IP address offered.
(9-3-8)
A DHCP server other than the SVP may be operating.
Although a user LAN is not supposed to be able to connect to a DKC internal HUB
(internal LAN), this error might occur if the user LAN (excluding a LAN for ASSIST or
Hi-Track) is mistakenly connected to the internal LAN. See the LOCATION Section
[LOC05-40] and check if the user LAN is connected to HUB EXP-1 or EXP-2. If the user
LAN is connected, disconnect it.
(9-3-9)
Re-execute installation.
If the same phenomenon occurs three times or more, contact the Technical Support
Division (TSD).
(10) When all the statuses of the program products displayed in the ‘NAS Setup on SVP
(Install Progress)’ window become Completed, the installation has finished.
Click the Close button in the ‘NAS Setup on SVP (Install Progress)’ window.
(Display example)
NAS03-380
NAS03-390 DKC515I

Make sure that the installed program products are listed in Available Program Product,
and that their versions match to that of the NAS OS media (CD-ROM), and then click the
Close button.
Installation now finishes.
Note: Although you selected one NAS OS, either NAS Data Control or NAS File Sharing
in Program Product in Media of the NAS Setup on SVP (Program Install) window when
installing a NAS OS, after installation, Available Program Product lists two items, NAS
Data Control and NAS File Sharing.
(Display example)
NAS03-390
NAS03-400 DKC515I
[2] NAS OS expansion installation

running.
Note: Make sure that the status of the NAS OS in the target NAS Package that you want
to install a NAS OS on is NEW.
time.
NAS03-400
NAS03-410 DKC515I
CAUTION
If there exists a NAS Package (other than the NAS Package on which the operation is
being performed) for which a NAS OS has been installed, selecting these check boxes
might cause a fatal error such as a system crash. You need to enter a password to
select these check boxes and continue the operation. Contact the Technical Support
Division (TSD) to confirm the validity of the operation and obtain the password.
For more information on the operating procedure, see 3.5.4 [7] Installation Containing LU
Initialization (Use this procedure by developers' instruction only when the error cannot be
corrected) [NAS03-530].
program product to be installed (NAS OS (NAS Data Control, NAS File Sharing), NAS
Blade Manager).
If you want to install multiple program products, select the program products while
holding down the Ctrl key.
Click the Install button to continue.
Note: You can install NAS OS and NAS Blade Manager concurrently in a NAS OS
expansion installation.
A list of the installed program

products is displayed. You
can select only one program
product, and cannot select
multiple program products.


stored in the supplied the
NAS OS media are
m ultiple items at one time.

becom es active. Clicking
(Display example)
NAS03-410
NAS03-420 DKC515I
(6) The message “The NAS OS will be installed for the first time. …” appears.
products, the installation starts in descending order from the top item on the list.
(Display example)
You can install the NAS OS on another NAS Package in parallel. (While you are
installing the NAS OS on one NAS package, you can install it on any other ones.) Install
the NAS OS in the NAS Package (NEW status) that was added.
If installation finishes successfully, go to step (9).
Note: Select (CL) [Cancel (the leftover products)] if you want to cancel subsequent PP
installation.
NAS03-420
NAS03-430 DKC515I
Rev.2 / Jun.2005, Jul.2006 Copyright © 2005, 2006, Hitachi, Ltd.
(8-1)
(8-2)
take action.
(8-3)
(8-3-1)
NAS03-430
NAS03-440 DKC515I
(8-3-2)
(8-3-3)
NAS03-440
NAS03-450 DKC515I
(8-3-4)
(8-3-5)
Under Event, check if DHCP Server error 1009 was reported at the time the installation
failed.
NAS03-450
NAS03-460 DKC515I
(8-3-6)
(8-3-7)
If so, go to step (8-3-8).
drive of the SVP, reboot the SVP, and then install the NAS OS from step (1).
(TSD).
(8-3-8)
(8-3-9)
Division (TSD).
NAS03-460
NAS03-470 DKC515I
(Display example)
NAS03-470
NAS03-480 DKC515I

Make sure that the version displayed in Ver. corresponds with the version of the NAS OS
media (CD-ROM) and also the program product name in Name in Available Program
Product corresponds with the program product name of the NAS OS media (CD-ROM),
and then click the Close button.
The installation finishes.
Note: When NAS OS is installed, you select “NAS OS (NAS Data Control, NAS File
Sharing))” from Program Product in Media in the ‘NAS Setup on SVP (Program
Install)’ window, however, after the installation finishes, two program products (“NAS
Data Control” and “NAS File Sharing”) are displayed in Available Program Product.
(Display example)
NAS03-480
NAS03-490 DKC515I
[3] Optional program product installation
To install the optional program products:
(1) Insert the NAS PP media (CD-ROM) into the CD drive of the SVP.
running.
to install a NAS OS on is ACTIVE or INACTIVE.
NAS03-490
NAS03-500 DKC515I

program product to be installed.
If you want to install multiple program products, select the program product while holding
down the Ctrl key.
Note: In the window example below, NAS Backup Restore is installed from the optional
program products stored in the NAS PP media.
A list of the installed

program products is
only one program
product, and cannot
select multiple program
products.
Becom es active when an

selected optional
program product.

stored in the supplied
NAS PP media are
multiple items at one
time.

becom es active. Clicking
selected program
product.
(Display example)
CAUTION
When you install the optional program product, you cannot select either the NAS Cluster
Management LU or Error Information LU in the Initialize area.
NAS03-500
NAS03-510 DKC515I
products, the installation starts in the order from the top item.
(Display example)
You can install the optional program product on the other NAS Package in parallel.
(While you are installing the NAS OS on one NAS package, you can install it on any other
ones.)
Note: Select (CL) [Cancel (the leftover products)] if you want to cancel next and
consecutive PP installation.
(7) When the optional program product installation has ended abnormally:
(7-1)
When a message whose ID is ENSxxxxx appears, see the SVP MESSAGE Section for the
(7-2)
In the ‘SVP (Maintenance)’ window, make sure that no blocked part or failure is
displayed. If there is a blocked part or failure, see the SVP Section [SVP02-30] [SVP03-
10] for the corresponding action to take.
NAS03-510
NAS03-520 DKC515I
(Display example)

Make sure that the version displayed in Ver. corresponds with the version of the NAS PP
media (CD-ROM) and also the program product name in Name in Available Program
Product corresponds with the program product name of the NAS PP media (CD-ROM),
(Display example)
NAS03-520
NAS03-521 DKC515I
[4] NAS OS installation for the first time (Multi-Installation)
running.
NAS03-521
NAS03-521A DKC515I
then click the Multi Install button.
NAS03-521A
NAS03-521B DKC515I
(5) The ‘NAS Setup on SVP (Multi Install)’ window appears.

From a list of the program products displayed in Program Product Name, select the
program product to be installed (NAS OS (NAS Data Control, NAS File Sharing), and
NAS Blade Manager). If you want to install multiple program products, select the program
products while holding down the Ctrl key.
Make sure that the program products have been selected correctly, and then go to the next
step.
Note: You can install NAS OS and NAS Blade Manager concurrently when you install
NAS OS for the first time.
time.
The program products stored in A list of the installed program If you select a program product
the supplied NAS OS media products and installation to be installed and the NAS
are displayed. You can select progress is displayed. Package, this button becomes
multiple items at one time. active. Clicking this button
Select the program products for Becomes active when the NAS installs the program product in
which the license keys are OSs are stopped in all the NAS the selected NAS Package.
provided. Packages.
(Display example)
CAUTION
You need to enter a password to select these check boxes and continue the operation.
Contact the Technical Support Division (TSD) to confirm the validity of the operation and
obtain the password.
NAS03-521B
NAS03-521C DKC515I
(6) From the list of the NAS Packages displayed in Select Install Node, select the NAS
Package to be installed.
Click Install and go to the next step.
(Display example)
(7) The message “You are installing the NAS OS on the disk subsystem for the first time. …”
appears.
NAS03-521C
NAS03-521D DKC515I
(8) The installation progress for the selected program product is displayed in Install Program
Product. If you selected more than one program product, the installation starts in
descending order from the top item.
When installation finishes successfully, go to step (11).
(Display example)

(9-1)
(9-2)
take action.
(9-3)
NAS03-521D
NAS03-521E DKC515I
(9-3-1)
(9-3-2)
NAS03-521E
NAS03-521F DKC515I
(9-3-3)
(9-3-4)
NAS03-521F
NAS03-521G DKC515I
(9-3-5)
(9-3-6)
(TSD).
NAS03-521G
NAS03-521H DKC515I
(9-3-7)
(9-3-8)
(9-3-9)
Division (TSD).
NAS03-521H
NAS03-521I DKC515I
(10) The message “All installation processing has finished.” appears.

(11) Confirm that all the statuses of the program products displayed in the ‘NAS Setup on SVP
(Install Progress)’ window are Completed, and then click the Close button.
(Display example)
NAS03-521I
NAS03-521J DKC515I
(12) In the ‘NAS Setup on SVP (Main)’ window, click Multi Install.

Click the NAS Package that you installed the program products on in Select Install Node.
(Display example)
NAS03-521J
NAS03-521K DKC515I
(14) The installed program products are displayed in Available Program Product.
Make sure that the displayed versions correspond with the version of the NAS PP media (CD-
ROM) for the installed NAS Packages, and then click the Close button.
This will end the installation process.
Note: Although you selected one NAS OS, either NAS Data Control or NAS File Sharing in
Program Product in Media of the NAS Setup on SVP (Program Install) window when
installing a NAS OS, Available Program Product lists two items, NAS Data Control and
NAS File Sharing after installation.
(Display example)
NAS03-521K
NAS03-522 DKC515I
[5] NAS OS expansion installation (Multi-Installation)
running.
to install a NAS OS on is NEW.
NAS03-522
NAS03-522A DKC515I
CAUTION
might cause a fatal error such as a system crash. You need to enter a password to
select these check boxes and continue the operation. Contact the Technical Support
Division (TSD) to confirm the validity of the operation and obtain the password.
Initialization (Use this procedure by developers' instruction only when the error cannot be
corrected) [NAS03-530].
program product to be installed (NAS OS (NAS Data Control, NAS File Sharing), NAS
Blade Manager). If you want to install multiple program products, select the program
products while holding down the Ctrl key. Make sure that the program products have
been selected correctly, and then go to the next step.
Note: You can install NAS OS and NAS Blade Manager concurrently in a NAS OS
installation for the first time.
time.
The program products stored in A list of the installed program If you select a program product
the supplied NAS OS media are products and installation to be installed and the NAS
displayed. You can select progress is displayed. Package, this button becomes
multiple items at one time. Select active. Clicking this button
Becomes active when the
the program products for which installs the program product in
NAS OSs are stopped in all
the license keys are provided. the selected NAS Package.
the NAS Packages
(Display example)
NAS03-522A
NAS03-522B DKC515I
(Display example)
NAS03-522B
NAS03-522C DKC515I
(7) The message “The NAS OS will be installed for the first time. If program products are
installed on the specified NAS Package, the program products will be uninstalled. Are you
sure you want to install the NAS OS?” is displayed.
products, the installation starts in the descending order from the top item.
(Display example)
a maximum of 90 minutes to install it in more than one NAS Package at the same time.
NAS03-522C
NAS03-522D DKC515I
(9-1)
(9-2)
take action.
(9-3)
(9-3-1)
NAS03-522D
NAS03-522E DKC515I
(9-3-2)
(9-3-3)
NAS03-522E
NAS03-522F DKC515I
(9-3-4)
(9-3-5)
NAS03-522F
NAS03-522G DKC515I
(9-3-6)
(9-3-7)
If the above error exists, go to step (9-3-8).

(TSD).
(9-3-8)
(9-3-9)
Division (TSD).
NAS03-522G
NAS03-522H DKC515I

(Display example)
NAS03-522H
NAS03-522I DKC515I

Select the NAS Package that you installed the program products on in Select Install Node.
(Display example)
NAS03-522I
NAS03-522J DKC515I
(14) The installed program products are displayed in Available Program Product.
Make sure that the displayed versions correspond with the version of the NAS PP media
(CD-ROM) for the installed NAS Packages, and then click the Close button.
This will end the installation procedure.
Note: Although you selected one NAS OS, either NAS Data Control or NAS File Sharing
in Program Product in Media of the NAS Setup on SVP (Program Install) window when
installing a NAS OS, Available Program Product lists two items, NAS Data Control and
NAS File Sharing after installation.
(Display example)
NAS03-522J
NAS03-523 DKC515I
[6] Optional program product installation (Multi-Installation)
running.
(4) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package to be installed, and
Note: Make sure that the status of the NAS OS in the target NAS Package that you want to
install a NAS OS on is ACTIVE or INACTIVE.
NAS03-523
NAS03-523A DKC515I

program product to be installed.
If you want to install multiple program products, select the program product while holding
down the Ctrl key.
Make sure that the program products have been selected correctly, and then go to the next
step.
The program products stored in Becomes active when the If you select a program product
the supplied NAS OS media NAS OSs are stopped in all to be installed and the NAS
are displayed. You can select the NAS Packages Package, this button becomes
multiple items at one time. active. Clicking this button
Select the program products for A list of the installed program installs the program product in
which the license keys are products and installation the selected NAS Package.
provided. progress is displayed.
When you install optional program products

only, the buttons for the NAS Packages on
which the NAS OSs are stopped are inactive.
(Display example)
CAUTION
When you install the optional program product, you cannot select either the NAS Cluster
Management LU or Error Information LU in the Initialize area.
NAS03-523A
NAS03-523B DKC515I
(Display example)
products, the installation starts in the descending order from the top item.
(Display example)
NAS03-523B
NAS03-523C DKC515I
(8-1)
(8-2)
take action.

(Display example)
NAS03-523C
NAS03-523D DKC515I

Select the NAS Package that you installed the program products on in Select Install Node.
(Display example)
NAS03-523D
NAS03-523E DKC515I
(13) The installed program products are displayed in Available Program Product. Make sure that
the displayed versions correspond with the version of the NAS PP media (CD-ROM) for the
installed NAS Packages, and then click the Close button.
This will end the installation procedure.
(Display example)
NAS03-523E
NAS03-530 DKC515I
[7] Installation Containing LU Initialization (Use this procedure by developers' instruction only
when the error cannot be corrected)
A NAS Cluster Management LU (NAS Cluster Management LU) and error information
LU (Error Information LU) can be initialized concurrently when the NAS OS is
installed.
This operation can be performed only when the NAS OS is installed for the first time.
When the NAS OS is being upgraded, this operation cannot be performed.
Note: If all the statuses of the NAS Packages are NEW in the ‘NAS Setup on SVP
(Main)’ window, follow the procedure in 3.5.4 [1] NAS OS installation for the first time
[NAS03-310].
CAUTION
Make sure that you stop all of the NAS OSs running in the disk subsystem before
performing this operation. (3.5.8 [1] Stopping the NAS OS (NAS03-780))
This operation might cause a fatal error such as a system crash. Before performing this
operation, you need to enter a password. Contact the Technical Support Division (TSD)
to confirm the validity of this operation and receive an approval.
To install the NAS OS containing LU initialization:
running.
NAS03-530
NAS03-540 DKC515I

NAS OS to be installed. If you want to install multiple program products, select the
program product while holding down the Ctrl key.
Check the LU that you want to initialize, and then click the Install button.
(Display example)
(6) The message “The NAS OS will be installed for the first time. If program products are
installed on the specified NAS Package, the program products will be uninstalled. Are you
sure you want to install the NAS OS?” is displayed.
NAS03-540
NAS03-541 DKC515I
Rev.0 / Nov.2005 Copyright © 2005, Hitachi, Ltd.
(7) The message “To perform a new installation on a node where...” is displayed.
(8) The NAS Setup on SVP (Password) window appears.

Enter the password, and then click the OK button.
Note: Contact the Technical Support Division (TSD) to confirm the validity of this
operation, and obtain the password as necessary.
NAS03-541
NAS03-550 DKC515I
(9) Depending on the LU selected in the ‘NAS Setup on SVP (Program Install)’ window, the
following message appears:
When only NAS Cluster Management LU is selected, the message “NAS Cluster
Management LU: ON, Error Information LU: OFF The LU that you selected will be
initialized. But then the running NAS Blade system may be affected by this process. Is this
OK?” appears.
When only Error Information LU is selected, the message “NAS Cluster Management
LU: OFF, Error Information LU: ON The LU that you selected will be initialized. But
then the running NAS Blade system may be affected by this process. Is this OK?” is
displayed.
When both NAS Cluster Management LU and Error Information LU are selected, the
message “NAS Cluster Management LU: ON, Error Information LU: ON The LU that you
selected will be initialized. But then the running NAS Blade system may be affected by
this process. Is this OK?” is displayed.
NAS03-550
NAS03-560 DKC515I
(10) The ‘NAS Setup on SVP (Password)’ window appears.

The installation including LU initialization starts.
products, the installation starts in the order from the top item.
(Display example)
Note: It takes approximately 10 minutes to install the NAS OS in one NAS Package, and a
maximum of 90 minutes to install it in more than one NAS Package at the same time.
NAS03-560
NAS03-570 DKC515I
(12) When an installation of NAS OS finishes abnormally:
(12-1)
(12-2)
Make sure that there is no blocked part or error in the ‘NAS Setup on SVP (Maintenance)’
window. If there is a blocked part or an error, see the SVP Section [SVP02-30] [SVP03-
10], and then take actions.
(12-3)
Perform the procedure for installing NAS OS containing LU initialization.
(Install Progress)’ window become Completed, the installation finishes.
(Display example)
NAS03-570
NAS03-580 DKC515I

Make sure that the version displayed in Version corresponds with the version of the NAS
OS media (CD-ROM) and also the program product name in Program Product Name in
Available Program Product corresponds with the program product name of the NAS OS
media (CD-ROM), and then click the Close button.
Note: When NAS OS is installed, you select “NAS OS (NAS Data Control, NAS File
Install)’ window. However, after the installation finishes, two program products (“NAS
Data Control” and “NAS File Sharing”) are displayed in Available Program Product.
(Display example)
NAS03-580
NAS03-590 DKC515I
3.5.5 Uninstalling Optional Program Products
To uninstall the optional program products:
(1) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package (ACTIVE or
INACTIVE status) on which the operation is to be performed, and then click the
Program Install button.

From a list of the program products in Available Program Product, select the optional
program product to be uninstalled, and then click the Uninstall button.
Note: You can uninstall optional program products only.
(Display example)
NAS03-590
NAS03-600 DKC515I
(3) The message “Are you sure you want to uninstall XXXXX?” is displayed.
The uninstallation starts.
Note: XXXX indicates a program product name.
(4) When uninstallation finishes, the message “The process ended normally.” is displayed.
NAS03-600
NAS03-610 DKC515I
(5) ‘NAS Setup on SVP (Program Install)’ window, make sure that the program product that
was uninstalled is not displayed in Available Program Product, and then click the Close
button.
(Display example)
NAS03-610
NAS03-620 DKC515I
3.5.6 Setting Up the Network Environment

[1] Setting up the network for the control port------------------------------------------------ NAS03-630
[2] Adding routing information to the control port-------------------------------------------- NAS03-632
[3] Deleting routing information----------------------------------------------------------------- NAS03-641
You can configure the network information for the control port, such as the fixed IP address of the
NAS Package NIC, routing information, and the NTP server corresponding to the NAS Package.
You can also delete the routing information for the control port and data port.
Note when setting the network:

• If you changed the network environment configuration according to this procedure after setting up
the license of NAS Backup Restore, you need to ask the system administrator to restart the NDMP
server. For details, see the NAS Backup Restore User’s Guide (3.5.3 Restarting the NDMP
server).
• The IP addresses of the following networks must not be used. The following networks are
reserved in the subsystem. Please contact the Technical Support Division if you need to use these
IP addresses.
- from 172.29.1.0/24 to 172.29.4.0/24, and
- the networks of the IP addresses set for the SVP.
• The reserved words for NAS Blade systems cannot be used for a channel adapter name.
Note that these words are not case-sensitive.
Table 3.5-4 shows the reserved words for NAS Blade systems.
Table 3.5-4 List of Reserved Words in NAS Blade Systems

Classification Reserved words
A add, admin
C CLU_partition, cluster
D define, delete
F Failover_policy, Filesystem, for, force
H ha_parameter, ha_services, hostname
I in, IP_address
L localhost, log_group, LVM_volume
M maintenance_off, maintenance_on, modify, move
N nasos, NFS, NFS_admin, node
O offline, online
R remove, resource, resource_group, resource_type
S set, show, start, status, stnet_xxx*1, stop
T to
Symbol . (one period), .. (two periods)
*1: Any word starts with stnet_
NAS03-620
NAS03-625 DKC515I
Figure 3.5-4 describes a NAS network configuration example. The numbers [1]-[10] assigned to the
setting values in the figure correspond to the numbers indicated for the items described in [1]
Setting up the network for the control port [NAS03-630] and [2] Adding routing information to the
control port [NAS03-632].
[5] NTP Server (Server1): 192.168.5.5
[6] NTP Server (Server2): --

Technical Support
NTP Server NTP Server
Division (TSD)
(Server1) (Server2)
NAS
Management Client Client
Console Router Router
Data & Control LAN
Data LAN [7] Routing target: 192.168.100.0

[8] Subnet mask: 255.255.255.0
[4] MTU value: Default (1500)
[10] MSS value: Default (40)
Router
Router
[9] Gateway: 192.168.10.1
Switch for CL1-CHA Switch for CL2-CHA
NIC NIC NIC NIC

(eth1) ... (eth4) (eth1) ... (eth4)
SVP
...
NAS Package CL1-CHA NAS Package CL2-CHA
Setup on SVP
Storage
Navigator Internal LAN
[1] Channel adapter name: RAID7-1E
External LAN
[2] Fixed IP address: 192.168.10.11
[3] Subnet mask: 255.255.255.0
PC operating
Storage
Navigator
Web browser Disk subsystem
Figure 3.5-4 NAS Network Configuration Example
NAS03-625
NAS03-630 DKC515I
[1] Setting up the network for the control port

To set up the network environment such as the IP address for the control LAN and the NTP
server for the NAS Package:
(1) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package (INACTIVE status),
and then click the Setting button.
(2) The ‘NAS Setup on SVP (Setting)’ window appears. The current setting is displayed in
each item.
Enter the desired value for each item, and then click the Setup button.
Note:
In CHA Name, specify a unique name in the disk subsystem.
Be sure to enter all the items except Server 2 in NTP Server.
In NTP Server, specify the same value for each NAS Package comprising the cluster.
The NAS OS needs to be restarted to put the setting changes on NTP Server into effect.
The NTP server to be specified for NTP Server must be in a network that can
communicate within 90 seconds after each port is linked up.
Check with the system administrator beforehand to make sure that the NTP server is
placed in a network that can communicate within 90 seconds after the ports are linked up.
Set the Channel Adapter name. Specify a name that is
unique in the disk subsystem (Required: After the
cluster is defined, you cannot change the value from
this window. However, you can change it using the
NAS Blade Manager function while the cluster is
stopped, even after the cluster is defined.). (Indicated
as [1] in Figure 3.5-4 [NAS03-625])
Set the IP address for the control port (Required). The

value can be modified only when the cluster is stopped,
after the cluster is defined. (Indicated as [2] in Figure
3.5-4 [NAS03-625])
Set the network mask for the above IP address

(Required). The value can be modified only when the
cluster is stopped, after the cluster is defined.
(Indicated as [3] in Figure 3.5-4 [NAS03-625])
Displays the currently set MTU value (specifiable

range: 1500-16110, the default is 1500.) (Required).
The value can be modified only when the cluster is
stopped, after the cluster is defined. (Indicated as [4]
in Figure 3.5-4 [NAS03-625])
The window for setting The specified Set the IP address (recommended) or host name for the NTP
routing information is information is set up. server (Server 1 is required: After the cluster is defined, you cannot
displayed. change the value from this window. However, you can change it
using the NAS Blade Manager function while the cluster is stopped,
even after the cluster is defined.). To make the setting changes
effective, the NAS OS needs to be restarted. You must specify an
IP address if no DNS server is set at the initial configuration.
(Indicated as [5], [6] in Figure 3.5-4 [NAS03-625])
NAS03-630
NAS03-631 DKC515I
(3) The message “Are you sure you want to apply the setting to the NAS OS?” is displayed.
Confirm the setting contents again, and then click the OK button in the message window.
The settings are applied.
(4) When the setting contents are changed, the message “The setup ended normally.” is
displayed.
(5) Click the Close button in the ‘NAS Setup on SVP (Setting)’ window.
(6) Restart the NAS OS of the operated NAS Package. For details, see 3.5.8 [3] Restarting the
NAS OS [NAS03-840].
NAS03-631
NAS03-632 DKC515I
[2] Adding routing information to the control port

This subsection explains how to add routing information for the control LAN and data LAN.
(1) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package (in INACTIVE state)
that you want to set information for, and click the Setting button.
(2) The ‘NAS Setup on SVP(Setting)’ window is displayed.

Click the Routing button.
(3) The ‘List of Routing’ window of ‘NAS Setup on SVP(Routing)’ is displayed.

Click the Add button.
NAS03-632
NAS03-640 DKC515I
(4) The routing information setting window of ‘NAS Setup on SVP (Add Routing)’is
displayed. Specify a value for each item, click the Add button, and then click the Close
button.
Set how to specify the target.

Network: Sets the specific target
Default: Uses the default route
Select either to allow or reject the

access from the specified route.
Allow: Allows the target
Reject: Rejects the target
Set the routing target address.

(Required if Network is specified in
How to Specify Target) (Indicated
as [7] in Figure 3.5-4 [NAS03-625])
Specify the netmask address.

(Required if Network is specified in
How to Specify Target) (Indicated
Sets the specified routing Closes the window. as [8] in Figure 3.5-4 [NAS03-625])
information.
Specify the gateway address
Specify the maximum segment size for the TCP connection. (Required if Default is specified in
(Specifiable range: 64-65536, Default: MSS value - 40) How to Specify Target) (Indicated
(Indicated as [10] in Figure 3.5-4 [NAS03-625]) as [9] in Figure 3.5-4 [NAS03-625])
(5) Make sure that the routing information is added to the list in List of Routing window of
‘NAS Setup on SVP (Routing)’, and then click the Close button.
NAS03-640
NAS03-641 DKC515I
[3] Deleting routing information

This subsection explains how to delete routing information for both the control LAN and data
LAN. You can delete the routing information for the control LAN when you want to change
the routing. You can delete the routing information for the data LAN in cases such as when the
system administrator set the routing incorrectly and cannot connect to the NAS Blade Manger.
Delete the information for the data LAN following the system administrator’s instruction.
(1) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package (in INACTIVE state)
that you want to set, and click the Setting button.
(2) The ‘NAS Setup on SVP(Setting)’ window is displayed.

Click the Routing button.
(3) The List of Routing window of ‘NAS Setup on SVP(Routing)’ is displayed.

Click the Delete button.
NAS03-641
NAS03-642 DKC515I
(4) Make sure that the routing information is deleted from the list, and then click the Close button.
NAS03-642
NAS03-650 DKC515I
3.5.7 Setting Up a License

[1] Setting up licenses individually----------------------------------------------------- NAS03-660
[2] Setting up licenses in the batch mode---------------------------------------------- NAS03-690
[3] Checking or changing license information---------------------------------------- NAS03-730
[4] Deleting licenses --------------------------------------------------------------------- NAS03-750
You can set and delete the licenses of NAS Blade Manager and optional program products for each
cluster.
A license key is a password necessary for using the NAS Blade Manager and optional program
product. A license key is issued for each NAS Blade Manager and optional program product with a
purchased license. Table 3.5-5 shows the license types.
Table 3.5-5 License types

Type Description
Permanent The function is available for an unlimited period. Within the scope of the license,
you can transfer the usage right to the optional program product to another cluster.
Temporary The function is available to be used in all clusters for a predetermined period of
time. The final availability date is determined by the license's duration and its initial
date. Once the final availability date is reached, the license cannot be set again.
Emergency The function is available to be used in the cluster for 30 days. The final availability
date is determined by the license's duration and its initial date.
The license can be set again after the final availability date.
Note: If there is no NAS Package whose status is ACTIVE, INACTIVE, or WARN (NAS Blade
Manager is not installed), no license can be set.
Table 3.5-6 shows relationship between the types of licenses that are already set and the ones that
can be set for the same program products on the NAS Package.
Table 3.5-6 Relationship between the types of licenses that are already set and the
ones that can be set for the program products on the NAS Package
Types of licenses to be set
Permanent Temporary Emergency
No license Yes Yes *1 Yes *2
Types of Permanent Yes No No
licenses
already set Temporary Yes No Yes
Emergency Yes No Yes
Legend:
Yes: The license can be set.
No: The license cannot be set.
*1: You cannot set the temporary license for the program product on the node that the
permanent or emergency license has ever been set on.
*2: You cannot set the emergency license for the program product on the node that the
permanent license has ever been set on.
NAS03-650
NAS03-660 DKC515I
[1] Setting up licenses individually
To use the license key to set up the license for a NAS Blade Manager or optional program product:
(1) In the ‘NAS Setup on SVP (Main)’ window, click the License Management button.
(2) The ‘NAS Setup on SVP (License Management)’ window appears.

In the ‘NAS Setup on SVP (License Management)’ window, enter the license key in Key
Code:, and then click the Accept button.
The existing licenses are
listed.
Double-clicking the first item
or clicking the Detail button
displays the License Setting
window.
Entering a license key enables

this button. Clicking this button
displays the License Setting
window.
Clicking this button displays

the Select a License Key File
window.
This button is enabled when Enter a license key.

you select a program product
with a Permanent-type license.
Clicking this button deletes the
license.
NAS03-660
NAS03-670 DKC515I
(3) The ‘NAS Setup on SVP (License Setting)’ window appears.

In the ‘NAS Setup on SVP (License Setting)’ window, in Distribution select (switch the
status to ON) the cluster to which you want to apply the license, and then click the Accept
button.
Note: To set a permanent license, the number of remaining licenses displayed in
Remaining License should be 2 or greater.
Note: When you set temporary or emergency licenses, select only the nodes on which you
want to set the licenses for the program products.
NAS03-670
NAS03-675 DKC515I

Displays product name and the type
that are either selected in the
License List window or specified by
entering the license key.
For a permanent license, the Term

of validity box displays "-" and the
Remaining License box displays
the remaining licenses.
For temporary and emergency
licenses, the Term of validity box
displays the time limit for usage and
the Remaining License box
displays "-".
Click this button to set the

information of the entered
Distribution buttons:
(displayed) license.
Switching the selection (ON indicates that the target
cluster is selected and OFF indicates that the target
cluster is not selected) enables the license to be set
and enables you to check which clusters have a
license, etc.
<Rack-mount Model>
Displays product name and the type

that are either selected in the
License List window or specified by
entering the license key.
For a permanent license, the Term

of validity box displays "-" and the
Remaining License box displays
the remaining licenses.
For temporary and emergency
licenses, the Term of validity box
displays the time limit for usage and
the Remaining License box
displays "-".
Click this button to set the

information of the entered
Distribution buttons:
Switching the selection (ON indicates that the target
cluster is selected and OFF indicates that the target
cluster is not selected) enables the license to be set
and enables you to check which clusters have a
license, etc.
NAS03-675
NAS03-680 DKC515I
Confirm that the selected cluster is the one to which you want to apply the license, and
then click the OK button in the message window.
The setting is applied.
(5) When the settings finish, the message “The License is accepted.” is displayed.

(6) Click the Close button in the ‘NAS Setup on SVP (License Setting)’ window to close the
‘NAS Setup on SVP (License Setting)’ window.
(7) Confirm that the license that was set is displayed in License List of the ‘NAS Setup on
SVP (License Management)’ window, and then click the Close button.
NAS03-680
NAS03-690 DKC515I
[2] Setting up licenses in the batch mode
To set up the licenses for the NAS Blade Manager or multiple optional program products by means
of a license key file:

In the ‘NAS Setup on SVP (License Management)’ window, click the Key File button.
(3) The ‘Select a License Key File’ window is displayed.

Select a license key file, and then click the Open button.
NAS03-690
NAS03-700 DKC515I
(4) The ‘NAS Setup on SVP (License Key File)’ window appears.
In the ‘NAS Setup on SVP (License Key File)’ window, select from License Key List a
license to be set up, and then click the Accept button.

In the ‘NAS Setup on SVP (License Setting)’ window, under Distribution, select the
cluster to which the license is to be assigned, and then click the Accept button.

Note: When you set temporary or emergency licenses, select only the nodes on which you
want to set the licenses for the program products.
NAS03-700
NAS03-710 DKC515I
Recheck the cluster to which the license is to be assigned, and then click the OK button.
The setting is applied.
(7) The message “The license is accepted” is displayed.

Click the OK button.
NAS03-710
NAS03-720 DKC515I
In the ‘NAS Setup on SVP (License Key File)’ window, click the Close button to close
the window.
When setting up multiple licenses:

Repeat steps (4) through (8).
When all needed licenses have been set up:

In the ‘NAS Setup on SVP (License Key File)’ window, click the Close button to close
the window.

Check that the licenses that were set up in the NAS Setup on SVP (License Key File)
window are displayed, and then click the Close button.
NAS03-720
NAS03-730 DKC515I
[3] Checking or changing license information
To check or change license information:
(1) Click the License Management button in the ‘NAS Setup on SVP (Main)’ window.

From License List in the ‘NAS Setup on SVP (License Management)’ window, select the
license for which detailed information is to be displayed, and then click the Detail button.
NAS03-730
NAS03-740 DKC515I

Make sure that license information is to be displayed, and then click the Close button to
close the ‘NAS Setup on SVP (License Setting)’ window.
When changing the setting of a permanent license:

Perform the procedure from step (3) in 3.5.7 [1] Setting up licenses individually [NAS03-
650].
(4) Click the Close button in the ‘NAS Setup on SVP (License Management)’ window.
NAS03-740
NAS03-750 DKC515I
[4] Deleting licenses
You can delete the licenses for each disk subsystem. The licenses are deleted from all clusters in a
disk subsystem and the corresponding program products become unavailable.
Note: If you deleted a license, you cannot change the configuration or settings for the program
product for which the license was deleted, but the existing configuration and settings are not
deleted.
You can You can delete the license key for a program product whose license type is Permanent.
You cannot delete a license whose type is Temporary or Emergency.
To delete a license:

In the ‘NAS Setup on SVP (License Management)’ window, select from License List the
license to be deleted, and then click the Delete button.
NAS03-750
NAS03-760 DKC515I
(3) The message “The license (XXXX) will be removed. You will be unable to use the
function corresponding to this license. Are you sure you want to remove the license?” is
displayed.
The license is removed.
Note: XXXX indicates a program product name.
(4) When license deletion has been completed, the message “The license was removed.” is
displayed.
(5) In the ‘NAS Setup on SVP (License Setting)’ window, click the Close button to close
window.
NAS03-760
NAS03-770 DKC515I
(6) In the ‘NAS Setup on SVP (License Management)’ window, check that the deleted license
is no longer listed under License List, and then click the Close button.
NAS03-770
NAS03-780 DKC515I
3.5.8 Controlling the NAS OS (Stopping, Starting, and Restarting)

[1] Stopping the NAS OS -------------------------------------------------------------------- NAS03-780
[2] Starting the NAS OS --------------------------------------------------------------------- NAS03-820
[3] Restarting the NAS OS ------------------------------------------------------------------ NAS03-840
This section describes the procedures for controlling the NAS OS.
[1] Stopping the NAS OS
CAUTION
Before stopping the NAS OS, switch the services running on the target NAS Package
(node) to be stopped to run on an alternative node, and then request the system
administrator to stop the target node.
To stop the NAS OS:
(1) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package on which the
operation is to be performed, and then click the Boot Management button.
(2) The ‘NAS Setup on SVP (Boot Management)’ window appears.

Make sure that Status is INACTIVE or WARN, and then click the Shutdown button.
While one NAS OS is being stopped, other NAS Packages can also be stopped.
NAS03-780
NAS03-790 DKC515I
(3) The message “Are you sure you want to shut down the NAS OS?” is displayed.
(3-1)
If the node is stopped, the shutdown processing starts.
Go to step (4).
(3-2)
If the node is running, the message “This node is active. Please ask a system administrator
to switch the service to the alternative node and stop this node...” appears.
Click the Cancel button to stop the operation, and then request the system administrator to
switch the services to an alternative node and stop the target node.
To forcibly shut down the NAS OS, click the OK button.
Go to step (3-4).
Note: If the node is running, the password is required to stop the NAS OS. The NAS OS is
not stopped until you finish entering the password in the ‘NAS Setup on SVP (Password)’
window.
NAS03-790
NAS03-800 DKC515I
(3-3)
If the system is unable to recognize the status of the cluster, the message “Failed to get the
cluster status. Please select the Cancel button, and then retry the operation...” appears.
Click the Cancel button to stop the operation, and then go back to step (2) to retry the
operation.
If the same message appears repeatedly, click the OK button to forcibly shut down the
NAS OS.
Go to step (3-4).
(3-4)
The message “The cluster system may be affected by this process. Do you want to
continue the processing?” appears.
(3-5)
The ‘NAS Setup on SVP (Password)’ window appears.
Shutdown processing of the NAS OS starts.
NAS03-800
NAS03-810 DKC515I
(4) In the middle of the processing, Status changes to SHUTDOWN in the ‘NAS Setup on
SVP (Boot Management)’ window.
(5) When the processing finishes, the message “NAS OS has shut down.” is displayed.
(6) Make sure that Status is STOP in the ‘NAS Setup on SVP (Boot Management)’ window,
NAS03-810
NAS03-820 DKC515I
[2] Starting the NAS OS
To start the NAS OS:

Make sure that Status is STOP, and then click the Boot button.
While one NAS OS is being started, other NAS Packages can also be started.
(3) The message “Are you sure you want to boot the NAS OS?” is displayed.
The start processing is performed.
NAS03-820
NAS03-830 DKC515I
(4) In the middle of the processing, Status changes to BOOT in the ‘NAS Setup on SVP
(Boot Management)’ window.
(5) The message “NAS OS has booted.” is displayed.

(6) Make sure that Status is ACTIVE, INACTIVE, or WARN (NAS Blade Manager is not
installed) in the ‘NAS Setup on SVP (Boot Management)’ window, and then click the
Close button.
NAS03-830
NAS03-840 DKC515I
[3] Restarting the NAS OS
CAUTION
Before restarting the NAS OS, switch the services running on the target NAS Package
(node) to be restarted to run on an alternative node, and then request the system
To restart the NAS OS:
operations is to be performed, and then click the Boot Management button.

Make sure that Status is INACTIVE, or WARN, and then click the Reboot button.
While one NAS OS is being restarted, other NAS Packages can also be restarted.
NAS03-840
NAS03-850 DKC515I
(3) The message “Are you sure you want to reboot the NAS OS?” is displayed.
(3-1)
If the node is stopped, the restart processing starts.
Go to step (4).
(3-2)
If the node is running, the message “This node is active. Please ask a system administrator
to switch the service to the alternative node and stop this node...” appears.
Click the Cancel button to stop the operation, and then request the system administrator to
switch the services to an alternative node and stop the target node.
To forcibly restart the NAS OS, click the OK button.
Go to step (3-4).
NAS03-850
NAS03-860 DKC515I
(3-3)
If the system is unable to recognize the status of the cluster, the message “Failed to get the
cluster status. Please select the Cancel button, and then retry the operation...” appears.
Click the Cancel button to stop the operation, and then go back to step (2) to retry the
operation.
If the same message appears repeatedly, click the OK button to forcibly shut down the
NAS OS.
Go to step (3-4).
(3-4)
The message “The cluster system may be affected by this process. Do you want to
continue the processing?” appears.
(3-5)
The NAS OS is restarted.
NAS03-860
NAS03-870 DKC515I
(4) In the middle of the processing, Status changes to SHUTDOWN, then to BOOT in the
‘NAS Setup on SVP (Boot Management)’ window.
(5) The message “NAS OS has rebooted.” is displayed.

(6) Make sure that Status is ACTIVE, INACTIVE, or WARN (NAS Blade Manager is not
installed) in the ‘NAS Setup on SVP (Boot Management)’ window, and then click the
Close button.
NAS03-870
NAS03-880 DKC515I
3.5.9 Resetting CHA
CAUTION
Regardless of the NAS OS status, this operation forces the NAS OS to stop instantly.
Before performing this operation, contact the Technical Support Division (TSD) to confirm
the validity of this operation.
Also make sure that, before resetting CHA, you request the system administrator to stop
the cluster.
To reset CHA:
(1) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package on which the

Click the CHA Reset button in the ‘NAS Setup on SVP (Boot Management)’ window.
(3) The message “Are you sure you want to reset the CHA?” is displayed.
NAS03-880
NAS03-890 DKC515I
(4) The message “This processing will stop the NAS OS forcibly and immediately, regardless
of the NAS OS status. Do you want to continue the processing?” is displayed.

The CHA is reset.
Note: CHA reset usually takes about one minute.
NAS03-890
NAS03-900 DKC515I
(6) When the CHA reset operation finishes, the message “The process ended normally.” is
displayed.
(7) Make sure that Status is DOWN in the ‘NAS Setup on SVP (Boot Management)’
window, and then click the Close button.
NAS03-900
NAS03-910 DKC515I
3.5.10 Collecting the Hibernation Dump

[1] Collecting the hibernation dump -------------------------------------------------------- NAS03-910
[2] Canceling collection of the hibernation dump ---------------------------------------- NAS03-940
This section describes the procedure for collecting the hibernation dump and canceling the
collection.
CAUTION
Regardless of the NAS OS status, this operation forces the NAS OS to stop instantly.
Before performing this operation, contact the Technical Support Division (TSD) to confirm
the validity of this operation.
[1] Collecting the hibernation dump
To collect the hibernation dump:
Note: When you cancel collection of the hibernation dump, the SIM=ac84x0 (NAS OS failure) is
reported. Complete this SIM [SVP02-520] because this is caused by the processing to stop the NAS
OS when you collect the hibernation dump, and there is no problem.
(1) In the ‘NAS Setup on SVP (Main)’ window select a NAS Package whose status is
ACTIVE, INACTIVE, WARN, SHUTDOWN, BOOT, or PANIC, and then click the
Hibernation Dump button.
(2) The ‘NAS Setup on SVP (Hibernation Dump)’ window appears.

Click the Dump button in the ‘NAS Setup on SVP (Hibernation Dump)’ window.
NAS03-910
NAS03-911 DKC515I
Rev.0 / Apr.2006 Copyright © 2006, Hitachi, Ltd.
(3) The message “This operation will erase the data obtained in the previous operation...” is
displayed. If you have retrieved the dump file collected for the last time, click the OK
button.
Note: If you need to check the previous dump file, click the Cancel button, click the Close
button in the ‘NAS Setup on SVP (Hibernation Dump)’ window, and then check and
retrieve the dump file according to the procedure described in 3.4.15 Downloading Dump
Files.
NAS03-911
NAS03-920 DKC515I
Rev.1 / May.2005, Apr.2006 Copyright © 2005, 2006, Hitachi, Ltd.
(4) The message “Collection of the hibernation dump might take up to 90 minutes. Are you
sure you want to collect the hibernation dump?” is displayed.
Note: Normally, it takes about 10 minutes.
(5) The message “This processing will stop the NAS OS forcibly and immediately, regardless
of the NAS OS status. Do you want to continue the processing?” is displayed.

The hibernation dump is collected.
NAS03-920
NAS03-930 DKC515I
Rev.1 / May.2005, Apr.2006 Copyright © 2005, 2006, Hitachi, Ltd.
(7) Click the Close button in the ‘NAS Setup on SVP (Hibernation Dump)’ window.
Note: Click Close button to check the status of the NAS Package being operated via ‘NAS
Setup on SVP’. You do not have to wait until hibernation dump finishes.
(8) In the ‘NAS Setup on SVP (Main)’ window, make sure that the status of the NAS Package
for which the operation is being performed is DUMP.
(9) When the status of the NAS Package changes from DUMP to ACTIVE, INACTIVE, or
WARN (NAS Blade Manager is not installed) in the ‘NAS Setup on SVP (Main)’
window, collection of the hibernation dump has finished. Obtain a hibernation dump
(follow the procedure in 3.5.15 Downloading Dump Files) [NAS03-1080].
NAS03-930
NAS03-940 DKC515I
[2] Canceling collection of the hibernation dump
To cancel collection of the hibernation dump:
(1) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package that has the DUMP
status, and then click the Hibernation Dump button.
(2) The ‘NAS Setup on SVP (Hibernation Dump)’ window appears.

Click the Cancel button in the ‘NAS Setup on SVP (Hibernation Dump)’ window.
(3) The message “Are you sure you want to cancel collection of the hibernation dump?” is
displayed.
The cancel operation is performed.
NAS03-940
NAS03-950 DKC515I
(4) When the cancel operation for the hibernation dump finishes, the message “The process
ended normally.” is displayed.
(5) Click the Close button in the ‘NAS Setup on SVP (Hibernation Dump)’ window.
(6) In the ‘NAS Setup on SVP (Main)’ window, make sure that the status of the selected NAS
Package is DOWN.
(7) Start NAS OS of the NAS Package (See 3.5.8 [2] Starting the NAS OS) [NAS03-820]
.
(8) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package in which the error
occurred, and then select Download Dump (See 3.5.15 Downloading Dump Files)
[NAS03-1080]. Make sure that ‘NAS Setup on SVP (Download Dump)’ does not appear.
If ‘NAS Setup on SVP (Download Dump)’ appears, make sure that Download Status
indicating the dump acquisition status is Normal and also the same date is not displayed
in Last Save Date. After confirmation, make sure that collection of the hibernation dump
has been canceled.
NAS03-950
NAS03-960 DKC515I
3.5.11 Viewing the Settings (Refer Configuration Button)

NAS Package information can be confirmed in View Mode.
The NAS Package information is displayed in sequence. First information about the installed
program products is displayed. Second, information about the configured network is displayed.
Only NAS Packages whose statuses are ACTIVE, INACTIVE, or WARN (NAS Blade Manager is
not installed) are displayed. Finally, configured license information is displayed.
Note: If there is no NAS Package whose status is ACTIVE, INACTIVE, or WARN (NAS Blade
Manager is not installed), this function cannot be used.
(1) Click the Refer Configuration button in the ‘NAS Setup on SVP (Main)’ window.
(2) The ‘NAS Setup on SVP (Program Install)’ window for each CHA appears in View Mode.
Click the >> Next button in the ‘NAS Setup on SVP (Program Install)’ window.
(Display example)
NAS03-960
NAS03-970 DKC515I
(3) The ‘NAS Setup on SVP (Setting)’ window for each CHA appears in View Mode.
Click the >> Next button in the ‘NAS Setup on SVP (Setting)’ window.
(4) When you repeat steps (2) and step (3), the NAS Package information is displayed in
order.
For a NAS Package whose status is not ACTIVE, INACTIVE, or WARN (NAS Blade
Manager is not installed), the message “You cannot refer to configuration information
about CHA-XX, because the status is YYYY.” is displayed.
When you click the OK button, the next NAS Package information is displayed.
Note: XX indicates a NAS Package location.

YYYY indicates a NAS Package status (INST, STOP, DOWN, BOOT,
SHUTDOWN, DUMP, DUMPSKIP, HUNGUP, PANIC, UNKNOWN, or
FATAL).
NAS03-970
NAS03-980 DKC515I
(5) When all the NAS Package information is displayed, the ‘NAS Setup on SVP (License
Management)’ window is displayed in View Mode.
Select the license from License List for which detailed information is to be displayed, and
then click the Detail button.
(6) The ‘NAS Setup on SVP (License Setting)’ window is displayed in View Mode.
Confirm that the license information is correct, and then click the Close button to close the
‘NAS Setup on SVP (License Setting)’ window.
(7) When the Close button is clicked in the ‘NAS Setup on SVP (License Management)’
window, the window is closed.
NAS03-980
NAS03-990 DKC515I
3.5.12 Restoring a NAS OS LU

If an error occurs on a NAS OS LU, the NAS OS may not function correctly and the system may
not recognize the correct NAS Blade system configuration information (file systems and NFS/CIFS
shares). On request from the system administrator, the maintenance personnel will recover the NAS
OS LU using backup data collected by the system administrator who uses the NAS Blade Manager
GUI.
CAUTION
If an error occurs in a system LU, make sure to obtain the auto dump and send it to the
developer. The instructions to restore the system LU will be given by the developer,
determined from the analysis result of the auto dump.
If the configuration of the NAS Blade system has been changed since the NAS OS LU was saved,
restoring the NAS OS LU may not restore the NAS Blade system. If the configuration has been
changed since a backup was made but the initial status is restored, the NAS OS LU can be restored
(for example, if you constructed a file system after saving the NAS OS LU, you can restore the
NAS OS LU if that file system has already been deleted).
CAUTION
Do not restore a NAS OS LU while the NAS OS LU and NAS Cluster Management LU
are being saved or restored.
CAUTION
Ensure that except from the maintenance personnel executing this operation, no
maintenance personnel, account administrator, or system administrator logs on to or
operates with shell scripts any NAS Package in the disk subsystem until the NAS OS LU
is restored.
NAS03-990
NAS03-1000 DKC515I
Before restoring a NAS OS LU, the maintenance personnel must complete the following tasks:
Check that failover to the normal node has been completed. If failover has not been completed, ask
the system administrator to change the execution node for the resource group (manual failover).
See 4.5.11 Changing the execution node of a resource group in the manual NAS Blade Manager
User’s Guide.
Eliminate the cause of the error.
See Chapter 7. NAS Troubleshooting [NAS07-10].
Install the NAS OS and the related program products on the NAS OS LU whose error has been
eliminated. Install the same program products as the ones installed before the error occurs.
See 3.5.4 Installing the NAS OS and Related Program Products [NAS03-290].
A warning message appears and prompts you to enter a password during installation. Ignore the
message and enter a password.
Set up the network environment in the NAS Package where the error cause has been removed. You
must save the NAS OS LU after changing the network environment because the setting contents
that you saved must match the setting contents before the error occurs.
See 3.5.6 Setting Up the Network Environment [NAS03-620]. Also in this section, the setting
contents that you saved must match the setting contents before the error occurs.
When the NAS OS LU has been restored, restart the NAS OS using the procedure described in [3]
in Section 3.5.8[NAS03-840], and then ask the system administrator to perform the following tasks.
- Failback
- Resetting the password for the NDMP server
NAS03-1000
NAS03-1010 DKC515I
To restore a NAS OS LU:
(1) In the ‘NAS Setup on SVP (Main)’ window, select the NAS Package for which the NAS
OS LU is to be restored, and then click the Restore NAS OS LU button.
(2) The ‘NAS Setup on SVP (Restore NAS OS LU)’ window appears.
In the ‘NAS Setup on SVP (Restore NAS OS LU)’ window, make sure that NAS OS LU
Status is Normal, the saved date is shown in Last Save Date, and then click the Restore
button.
Note: You cannot restore the NAS OS LU when the status is other than Normal.
(3) The message ‘Before recovering the NAS OS LU, perform the following actions for the
NAS Package to be recovered...’ is displayed
Make sure that the processing is finished, and then click the OK button.
NAS03-1010
NAS03-1020 DKC515I
(4) The message “To restore the NAS OS LU of CHA-XX, you must enter the password. Do
you want to continue the processing?” is displayed.
Note: XX indicate a NAS Package location.

The NAS OS LU begins to be restored.
Note: If the NAS OS LU and NAS Cluster Management LU are being saved, only clicking
the OK button results in an error.
NAS03-1020
NAS03-1030 DKC515I
(6) In the NAS Setup on SVP (Restore NAS OS LU) window, NAS OS LU Status changes
to Now restoring....
(7) When restoration processing has been completed, the message “The NAS OS LU of CHA-
XX has been restored successfully.” is displayed.
(8) Reboot the NAS OS according to the procedure described in 3.5.8 [3] Restarting NAS OS
[NAS03-840].
(9) In the ‘NAS Setup on SVP (Restore NAS OS LU)’ window, make sure that NAS OS LU
Status is Normal, and then click the Close button.
NAS03-1030
NAS03-1040 DKC515I
3.5.13 Restoring a NAS Cluster Management LU

If an error occurs on a NAS Cluster Management LU, the NAS OS may not function correctly and
the system may not recognize the correct NAS Blade system configuration information (file
systems and NFS/CIFS shares). On request from the system administrator, the maintenance
personnel will recover the NAS Cluster Management LU using backup data collected by the system
administrator who uses the NAS Blade Manager GUI.
CAUTION
If an error occurs in a system LU, make sure to obtain the auto dump and send it to the
developer. The instructions to restore the system LU will be given by the developer,
determined from the analysis result of the auto dump.
If the configuration of the NAS Blade system has been changed since the NAS Cluster Management
LU was saved, restoring the NAS Cluster Management LU may not restore the NAS Blade system.
If the configuration has been changed since a backup was made but the initial status is restored, the
NAS Cluster Management LU can be restored (for example, if you constructed a file system after
saving the NAS Cluster Management LU, you can restore the NAS Cluster Management LU if that
file system has been deleted during the restoration processing).
CAUTION
Do not restore a NAS OS LU while the NAS OS LU and NAS Cluster Management LU
are being saved or restored.
CAUTION
Ensure that except from the maintenance personnel executing this operation, no
maintenance personnel, account administrator, or system administrator logs onto any
NAS Package in the disk subsystem until the NAS OS LU is restored.
To restore a NAS Cluster Management LU, all NAS Packages in the disk subsystem must be in the
ACTIVE, INACTIVE, or WARN (NAS Blade Manager is not installed) status.
Note: Before the NAS Cluster Management LU restoration is started and after it is finished, you
restart all the NAS OSs in all the NAS Packages in the NAS Blade system frame. Ask the system
administrator to define the clusters again after the NAS OSs are restarted.
NAS03-1040
NAS03-1050 DKC515I
To restore a NAS Cluster Management LU:
(1) In the ‘NAS Setup on SVP (Main)’ window, click the Restore CM LU button.
(2) The ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window appears.
In the ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window, make sure
that Status is Normal and the saved date is shown in Last Save Date, and then click the
Reboot all button.
Note: You cannot reboot the NAS OS when the status is other than Normal.
(3) The message “All the NAS OSs will be restarted.:.” is displayed.
If ‘NAS Setup on SVP (Password)’ is displayed, go to step (4), if it is not displayed, go to
step (5).
Note: There is no problem whether ‘NAS Setup on SVP (Password)’ window is displayed
or not. Follow the above instruction.
Note: You need to enter the password if there is a NAS OS whose status is Active.
NAS03-1050
NAS03-1051 DKC515I

Restart of all the NAS OSs starts.
(5) The Status of ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ is changed to
Now Rebooting all NAS OSs....
(6) The message “All NAS OSs have restarted successfully.” is displayed.
Note: Though SIM ac84x2 occurs when NAS OS is rebooted, there is no problem.
Perform SIM completion [SVP02-610].
NAS03-1051
NAS03-1051A DKC515I
(7) Replace the failed P-DEV in the NAS Cluster Management LU [TRBL05-150] and
release the RAID group’s blocked state.
(8) Repeat step (2) to (6) until you reboot all the NAS OSs.
NAS03-1051A
NAS03-1052 DKC515I
(9) The ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window appears.
In the ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window, make sure
that the Status is Normal, and then click the Restore button.
Note: You cannot restore the NAS Cluster Management LU when the Status is other than
Normal.
(10) The message “Before recovering the NAS Cluster Management LU, click the [Reboot all]
button to restart all NAS OSs in the disk subsystem...” is displayed.
(11) The message “The NAS Cluster Management LU will be restored. Execute the following
procedures:...” is displayed.
NAS03-1052
NAS03-1060 DKC515I
(12) The message “To restore the NAS Cluster Management LU, you must enter the password.
Do you want to continue the processing?” is displayed.

Restoration of the NAS Cluster Management LU starts.
Note: If the NAS OS LU and NAS Cluster Management LU are being saved or restored,
only clicking the OK button results in an error.
NAS03-1060
NAS03-1070 DKC515I
(14) In the ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window, the Status
changes to Now stopping the cluster..., and then to Now restoring..., and then to Now
removing the cluster....
(15) When restoration processing has been completed, the message “The NAS Cluster
Management LU has been restored successfully.” is displayed. Click the OK button.
Note: If recovery of NAS Cluster Management LU failed with [ENS3556E], take the
following action if the code values match.
0x01000002: NAS Blade Manager is not installed. Start the recovery procedure for NAS
Cluster Management LU over.
Note: If the waning message [ENS3939W] is displayed instead of [ENS3622i], take action
according to the message.
(Display example)
NAS03-1070
NAS03-1071 DKC515I
(16) Repeat step (2) to (6) until you reboot all the NAS OSs.
(17) In the ‘NAS Setup on SVP (Restore NAS Cluster Management LU)’ window, make sure
that the Status changes to Normal, and then click the Close button.
NAS03-1071
NAS03-1075 DKC515I
3.5.14 Selecting the Install Device

You can choose the machine (SVP or client PC) whose drive you insert the installation media into.
The procedure to select the Install Device is as follows.
Note: You cannot use this function when ‘NAS Setup on SVP (Program Install)’ is displayed.
Note: If you choose to use a client PC drive as the Install Device to install a NAS PP, use a line with
the connection speed faster than 100Mbps for connecting the SVP with the client PC.
Note: While you install NAS PP from a client PC drive, keep the other PCs from accessing SVP as
client PCs. If any other PC accesses SVP, installation might fail and the system might not be able to
start.
(1) Click the Install Device button in the ‘NAS Setup on SVP (Main)’ window.
(2) The ‘NAS Setup on SVP (Install Device)’ window is displayed.

Set each item, and then click the OK button.
Select the machine that you are
using for installation.
SVP: Select if you use the
CD-ROM drive of the SVP
(Default).
Client PC: Select if you use the
CD-ROM drive of the client PC.
Select a drive name from

the list if you choose Client
PC as the Install Device.
Applies the setting and goes Cancels the setting and goes
back to the ‘Setup on SVP back to the ‘Setup on SVP
(Main)’ window. (Main)’ window.
(3) Select the target NAS Package for installation in ‘NAS Setup on SVP (Main)’ window,
and then click the Program Install button.
NAS03-1075
NAS03-1076 DKC515I
(4) The ‘NAS Setup on SVP (Program Install)’ window is displayed.

Make sure that the Install Device and its drive that you set is displayed for the Install
from and the Drive, and then click the Close button.
(Display example)
NAS03-1076
NAS03-1080 DKC515I
3.5.15 Downloading Dump Files
To download dump files (NAS Dump (See Table 7.2-5 [NAS07-70])):
Note: The dump file might be still being generated immediately after the NAS OS is started.
Wait for about 30 minutes after the NAS OS is started, and then start downloading dump
files.
(1) If USB Memory is available, go to (2). Otherwise go to (10). USB Memory may not be
available, for example, when the dump has been collected but has not been transferred to
the manufacturer yet.
NAS03-1080
NAS03-1090 DKC515I
(2) Insert the USB Memory in USB port on the SVP.
Basic SVP Additional SVP
Rear View
of DKC
USB port
USB Memory
USB connector
(Insert the USB Memory
in USB port)
NAS03-1090
NAS03-1100 DKC515I
Blank Sheet
NAS03-1100
NAS03-1110 DKC515I
(3) NAS dump preparation
(3-1) Setting a password of USB Memory

(i) Select 'Run' from the Start menu.
(ii) Run ”G:\KeySafe.exe”.

Input characters can be in either upper or lower case.
(iii) Select ”English[U.S.]” and press ”OK".

”English [U.S.]” must be chosen here.
Check box should be left unchecked.
NAS03-1110
NAS03-1120 DKC515I
(iv) Press 'OK' when the message box appears.
(v) Set Password and Zone Size then select 'OK'. Password and Zone Size should be set as
follows:
(a) RAID-NAS
Note: All characters must be in uppercase.
(b) Expand the Zone Size as large as Maximum Privacy Zone (902.00MB). (The expanded
area is shown in orange.)
(a) (b)
(vi) Select 'OK' when message appears.
Formatting starts.
NAS03-1120
NAS03-1130 DKC515I
(vii) Press 'OK' when the completion message appears.
(viii) Input the password set at the procedure (v) (RAID-NAS).
(ix) Press 'OK' when the message appears.

(x) The preparation of dump correction has been finished when the folder window appears.
Select [x] on the upper-right side of the window to close the window.
NAS03-1130
NAS03-1140 DKC515I
(4) In the ‘NAS Setup on SVP (Main)’ window, select a NAS Package that you want to
download the dump files, and then click the Download Dump button.
(5) The ‘NAS Setup on SVP (Download Dump)’ window appears.

In the ‘NAS Setup on SVP (Download Dump)’ window, make sure that Download Status
is Normal, and Last Save Date shows the target date, and then click the Download
button.
Note: You cannot download dump files when Download Status is other than Normal.
(6) The message “The dump files for the CHA-XX will be downloaded. Are you sure you want
to continue the operation?” is displayed.
The dump files will be downloaded.
NAS03-1140
NAS03-1150 DKC515I
(7) In the ‘NAS Setup on SVP (Download Dump)’ window, the status in Download Status
changes to Now downloading....
(8) When the dump files are downloaded, the message “The dump files of CHA-XX have been
downloaded successfully...” and the location of the dump files are displayed in the
message.
Note: When there is no USB memory, downloaded dump files are stored to D drive of
SVP. When there is USB memory, download dump files are stored to USB, which is G
drive of SVP.
NAS03-1150
NAS03-1160 DKC515I
(9) In the ‘NAS Setup on SVP (Download Dump)’ window, make sure that Download Status
is Normal, and then click the Close button.
Go to (19).
NAS03-1160
NAS03-1170 DKC515I
(10) In the ‘NAS Setup on SVP (Main)’ window, select a NAS Package that you want to
download the dump files, and then click the Download Dump button.
(11) The ‘NAS Setup on SVP (Download Dump)’ window appears.

In the ‘NAS Setup on SVP (Download Dump)’ window, make sure that Download Status
is Normal, and Last Save Date shows the target date, and then click the Download
button.
Note: You cannot download dump files when Download Status is other than Normal.
(12) The message “The dump files for the CHA-XX will be downloaded. Are you sure you want
to continue the operation?” is displayed.
The dump files will be downloaded.
NAS03-1170
NAS03-1180 DKC515I
(13) In the ‘NAS Setup on SVP (Download Dump)’ window, the status in Download Status
changes to Now downloading....
(14) When the dump files are downloaded, the message “The dump files of CHA-XX have been
downloaded successfully...” and the location of the dump files are displayed in the
message.
Note: When there is no USB memory, downloaded dump files are stored to D drive of
SVP. When there is USB memory, download dump files are stored to USB, which is G
drive of SVP.
NAS03-1180
NAS03-1190 DKC515I
(15) In the ‘NAS Setup on SVP (Download Dump)’ window, make sure that Download Status
is Normal, and then click the Close button.
The procedure is suspended here if USB memory is not available. Resume the procedure from
(16) when the UBS memory becomes available.
NAS03-1190
NAS03-1200 DKC515I
(16) Insert the USB Memory in USB port on the SVP.
Rear View
of DKC
USB port
USB Memory
USB connector
(Insert the USB Memory
in USB port)
NAS03-1200
NAS03-1210 DKC515I
Blank Sheet
NAS03-1210
NAS03-1220 DKC515I
(17) NAS dump preparation
(17-1) Setting a password of USB Memory
(i) Select 'Run' from the Start menu.
(ii) Run ”G:\KeySafe.exe”.

Input characters can be in either upper or lower case.
(iii) Select ”English [U.S.]” and press ”OK".
”English [U.S.]” must be chosen here.

NAS03-1220
NAS03-1230 DKC515I
(iv) Press 'OK' when the message box appears.
(v) Set Password and Zone Size then select 'OK'. Password and Zone Size should be set as
follows:
(a) RAID-NAS
Note: All characters must be in uppercase.
(b) Expand the Zone Size as large as Maximum Privacy Zone (902.00MB). (The expanded
area is shown in orange.)
(a) (b)
(vi) Select 'OK' when message appears.
Formatting starts.
NAS03-1230
NAS03-1240 DKC515I
(vii) Press 'OK' when completion message appears.
(viii) Input the password set at the procedure (v) (RAID-NAS).
(ix) Press 'OK' when the message appears.

(x) When the folder window appears, the preparation of dump correction has been
finished. Select [x] on the upper-right side of the window to close the window.
NAS03-1240
NAS03-1250 DKC515I
(18) Copying NAS dumps
(i) Select 'Run' on Start menu.
(ii) Run ”C:\DKC200\MP\PC\CPNASDM.BAT” on the 'Run' window.
(iii) A window appears and file copy starts.

Press any key when the message "Are you sure you want to delete the files which the copy
ended?" appears.
NAS03-1250
NAS03-1260 DKC515I
(iv) Input 'y' then press the enter key to respond the message "d:\chndump\…, Delete
(Y/N)?" for all files.
(v) Press any key when the message "Please press any key." appears.
The window is closed.
(19) Pre-Procedure of removal of USB Memory
(i) Choose the icon of “Safely Remove Hardware” on the task bar. When the menu bar is
displayed, choose "Safely remove USB Mass Storage Device - Drive (G:)”
Note: Don't choose any messages other than "Stop USB Mass Storage Device (G:)."
Otherwise, the selected device will stop. In this case, please re-install the stopped device.
NAS03-1260
NAS03-1270 DKC515I
(ii) Confirm that the following message appears, then select 'OK'.
"The 'USB Mass Storage Device' device can now be safely removed from the system."
If any other message appears, the wrong device has been stopped. In this case, install the
device again then start over from (19).
Go to (20) to remove the USB Memory.
(20) Removement of USB Memory

(20-1) Pull out the USB Memory from SVP.
Rear View
of DKC
USB port
USB Memory
USB connector
(20-2) Attach the connector cover to USB connector.
USB Memory Connector cover
USB connector
NAS03-1270
NAS03-1280 DKC515I
This is the end of the procedure of collecting dumps.
NAS03-1280
NAS03-1290 DKC515I
3.6 Operations Using the NAS Blade Manager GUI

3.6.1 Registering System Administrators
The account administrator registers system administrators. The account administrator can change
and view the user information for all the registered system administrators.
The account administrator uses his or her own account to log in to NAS Blade Manager, creates one
or more authorized accounts for system administrators.
3.6.2 Setting Up the NAS Package Cluster Configuration

A system administrator (or vendor or maintenance personnel when setting up the NAS Package
according to the System Assurance Documentation) uses the NAS Blade Manager GUI to perform
manual failover or failback. To define the cluster configuration among NAS Packages, a system
administrator uses it. To define a tentative cluster configuration among NAS Packages, a
maintenance personnel or the manufacturer uses it.
When the cluster configuration is being defined, the path definitions to the user LUs must be all the
same among the target nodes. If the path definitions and program versions are changed after
operation has started, these path definitions and program versions in the cluster must be made the
same.
When the NAS Cluster Management LU is saved and recovered, fix the NAS Package where a
cluster configuration was defined. When the NAS Cluster Management LU is recovered, the NAS
Package where a cluster configuration is defined must be matched.
When replacing hardware or upgrading/downgrading software for the NAS Packages in a cluster, a
system administrator performs a manual failover and failback.
3.6.3 Setting Up the Configuration For Services

Set up the configuration for the services. This configuration includes settings for controlling the
starting and stopping of NFS, settings for performance-related features such as the number of
processes, settings for controlling the starting and stopping of CIFS, settings for user authentication,
and settings for ssh security.
The following table lists the services managed by the service management.
Table 3.6-1 Service Management

# Service name Configurable Start up control
1 nfs_service Yes Yes
2 cifs_service Yes Yes
3 ssh_service Yes ---
Legend:
Yes: Supported.
---: Not supported.
A system administrator can use the NAS Blade Manager GUI to perform operations such as starting
or stopping the services.
NAS03-1290
NAS03-1300 DKC515I
3.6.4 Setting Up the Network for the control port and data port
This subsection explains how to set up the network configuration for the control and data port and
routing for the NAS Packages.
The system administrator can use the NAS Blade Manager GUI to set and view the network
information such as the fixed and service IP addresses for the control port and data port, view the
list of network routing, and add and delete routings. The routings for the internal LAN cannot be
viewed or set.
The following items can be set for the network.
• Interface (the target NIC, whether VLAN is used)
• Fixed IP address
• Service IP addresses (only for the data port)
• Netmask
• MTU values
The following items can be set for the routing.

• Interface (the target NIC, whether VLAN is used)
• Method for specifying the target (network or host)
• Routing target
• Gateway
• Netmask
• Routing to be rejected
• Metric
• MSS
3.6.5 Setting Up the Network (DNS, NIS)

Set the IP address of the DNS server when using DNS, and set the IP address of the NIS server
when using NIS.
The following items related to the DNS server can be set:

• Default domain name
• Primary DNS server
• Secondary DNS server
The following items related to the NIS server can be set:

• NIS domain name
• NIS server
NAS03-1300
NAS03-1310 DKC515I
3.6.6 Setting Up Users and Groups

Set up the general users who will use the NFS environment and the CIFS environment. For details
about setup for system administrators, see 3.6.1 Registering System Administrators. [NAS03-1290]
A system administrator can use the NAS Blade Manager GUI to perform operations such as adding
a new general user, and editing or deleting information about general users. In addition, the
administrator can add a new group, and edit or delete the group information for the general users
who use the CIFS environment.
3.6.7 Creating File Systems

You can create a file system that can be used in NAS Blade system and expand the size of an
existing file system.
A system administrator can use the NAS Blade Manager GUI to perform operations such as listing
the file systems, creating and deleting a file system that can be used on the NAS Blade system, and
expanding existing file systems. In addition, the administrator can mount or unmount existing file
systems.
3.6.8 Setting Up File Shares (NFS, CIFS)

A system administrator can use the NAS Blade Manager GUI to specify settings for the NFS and
CIFS environments. The following table lists the items to be set or viewed.
Table 3.6-2 File Sharing Management

# Item NFS environment CIFS environment
1 Viewing file shares Yes Yes
2 Setting up file shares Yes Yes
3 Changing the contents of file shares Yes Yes
4 Releasing settings for file shares Yes Yes
Legend:
Yes: Configurable.
No: Not configurable.
The following major items can be specified when setting up file sharing:
• Shared directories (paths to public directories)
• Whether or not to create a new directory (when a specified shared directory does not exist)
• The owner and access permissions for a directory (when a new directory is created)
• The group and access permissions for a directory (when a new directory is created)
• The access mode for a file share (Read only or Read/Write)
• The host or network on which an NFS share is made public
• The host or network on which a CIFS share is made public
NAS03-1310
NAS03-1320 DKC515I
3.6.9 Specifying Settings Related to Error-Monitoring Functionality

Specify the settings related to error-monitoring functionality: for example, settings for log files,
message files, dump files, and SNMP.
When installing a NAS Blade system device or when increasing the number of NAS boards, a
system administrator might need to change the settings of the following items using the NAS Blade
Manager GUI to enable error monitoring for these devices.
Table 3.6-3 Settings Related to Error-Monitoring Functionality

# Item Setting
1 syslog files Settings related to syslog.conf, such as the output level and output
destination of the syslog file.
2 SNMP Settings related to the SNMP Manager server, such as its address and
security.
3 Automatic deletion of core Settings related to automatic deletion of core files.
files
4 Log files, etc. Settings related to log files, such as the file size and number of
wraparounds.
3.6.10 Settings Related to the Save Function for NAS System LUs (NAS OS LU and NAS
Cluster Management LU)
You can perform necessary settings for saving data in the NAS OS LU and NAS Cluster
Management LU automatically, or save them manually.
If the NAS Blade system configuration has been changed, the system administrator must use the
NAS Blade Manager GUI to save data in the NAS OS LU and NAS Cluster Management LU. As a
general rule, data in the NAS OS LU and NAS Cluster Management LU needs to be saved at the
following times:
• When a file system is constructed or deleted

• When a copy device is defined or released*1
• When a snapshot is created*1
• When a differential-data storage device is set or released*2
• When a differential-data snapshot is created or deleted*2
*1: Applicable when the NAS Backup Restore is used.

*2: Applicable when the NAS Sync Image is used.
CAUTION
When you change the NAS Blade system configuration, the NAS OS LU and NAS Cluster
Management LU might not be able to be recovered if you do not save data on the NAS
OS LU and NAS Cluster Management LU.
NAS03-1320
NAS04-10 DKC515I
4. NAS Hardware Replacement
This chapter describes the procedure of maintenance personnel and system administrators for
replacing the NAS Blade system hardware.
4.1 Overview
This section describes replacement procedures when a failure occurs or after preventive diagnostics
are performed.
You can perform hot replacement of the hardware in a disk subsystem without stopping user
services (except for cases such as when a RAID group is not usable because of a PDEV failure).
Also, by using failover, you can replace NAS Packages in the NAS Blade system, without stopping
user services. When replacing NAS Packages, maintenance personnel and system administrators
need to consider whether the NAS OS needs to be stopped and whether to perform a failover.
NAS04-10
NAS04-20 DKC515I
4.2 Types of Hardware Replacement Operations

Hardware is replaced in the following two situations:
• Replacement when a hardware failure occurs

This replacement operation replaces the failed hardware.
• Replacement when preventive replacement is performed

This replacement operation replaces hardware based on the results, for example, of periodic
diagnostics or correctable errors.
This section describes replacement when preventive replacement is performed.
Such replacement operations are classified based on the operations performed by maintenance
personnel or system administrators and the NAS Blade system behavior, as follows.
Table 4.2-1 Types of Hardware Replacement Operations

# Target hardware Corresponding Restart Perform Can ordinary Reference info.
tasks the NAS a users continue for preventive
1
OS? failback? operations? * replacement
1 NAS Package Replace the NAS Yes Yes Yes Figure 4.2-1
Package. [NAS04-40]
2 Fiber optic cable for Replace the data No Yes Yes Figure 4.2-2
the data LAN (LAN LAN fiber optic [NAS04-80]
cable) *2 cable*2
3 Fiber optic cable for Replace the control No No Yes Figure 4.2-3
the control LAN LAN fiber optic [NAS04-111]
(LAN cable) cable
4 External devices Maintain and Yes No No Figure 4.2-4
(disk subsystems) replace the external [NAS04-115]
devices
5 Hardware other than Replace the No No Yes Figure 4.2-5
NAS Package*3 hardware (hot [NAS04-120]
replacement).
*1: Yes: Business tasks continue except for a double failure. However, if the application
server is connected with Windows client (CIFS share) when a failover and a failback
occur, the CIFS share is released. Therefore you must reconnect the server with CIFS
share.
No: Ordinary users cannot perform operations related to the failed PDEV(s).
*2: This includes the cable shared by the control LAN and data LAN.
*3: For details, see the REPLACE Section [REP01-10].
NAS04-20
NAS04-30 DKC515I
4.2.1 Flowcharts for Replacing Hardware
In this section, the cluster is assumed to consist of CL1-CHA and CL2-CHA, and Figure
4.2-1 through Figure 4.2-5 show examples of flowcharts of hardware replacement on
CL1-CHA.
Make sure that CL2-CHA is properly referred to as the actual location when replacing the
CHA location.
Table 4.2-2 shows the actual CHA locations in the NAS cluster configuration.
Table 4.2-2 CHA Location in the NAS Cluster Configuration

Model CHA location CL1-CHA CL2-CHA
Flexible cabinet Basic 1E 2Q
model Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
Rack-mount model Option 1 1B 2E
# Hardware replacement Reference

(1) Replacing the NAS Package (during preventive replacement) Figure 4.2-1
[NAS04-40]
(2) Replacing the data LAN fiber optic cables (during preventive replacement) Figure 4.2-2
[NAS04-80]
(3) Replacing the control LAN fiber optic cables (during preventive replacement) Figure 4.2-3
[NAS04-111]
(4) Maintaining and replacing the external devices Figure 4.2-4
[NAS04-115]
(5) Hot-replacing hardware other than the NAS Package Figure 4.2-5
[NAS04-120]
NAS04-30
NAS04-40 DKC515I
(1) Replacing the NAS Package (During Preventive Replacement)
Replacement
NAS Package
CL1-CHA CL2-CHA
Pentium
MP MP MP MP Backup LU of NAS CM LU
NAS OS LU for CL1-CHA NAS OS LU for CL2-CHA NAS Cluster Management LU

SVP Dump LU for CL1-CHA Dump LU for CL2-CHA NAS Cluster Management LU
: Failover (performed manually)

: Failback
: Monitoring
Figure 4.2-1 Replacing the NAS Package (During Preventive Replacement) (1/4)

1 Check the operating status of the
NAS Blade system.
3 Stop the node.
4 Stop the NAS OS. Stop the NAS OS while the target NAS Package
(CL1-CHA) is running
6 Start the node.
7 Perform failback.
NAS04-40
NAS04-50 DKC515I
Replacing the NAS Package

(during preventive replacement)
YES
Is the NAS OS of the
CL1-CHA stopped?
NO [Is NAS OS stopped?]

See the 'Main' window 2
in 3.5.3 [NAS03-260]
[NAS04-70]
Phone, E-mail: Phone, E-mail: CL1-CHA: Operating

Notify a system administrator of Notify ordinary users of the CL2-CHA: Operating
the NAS Package location that failover and get permission for it.
requires a failover, and ask to
perform a failover and stop the
CL1-CHA node.
Failing over from CL1-CHA to CL2-CHA
NAS Management Console:
Use the NAS Blade Manager
functionality to perform a failover Failover notification
from CL1-CHA to CL2-CHA, and - NAS Blade Manager GUI
confirm that the failover has been (CL2-CHA notification)
completed. - syslog (CL2-CHA notification)

By using the NAS Blade
Manager functionality, stop the
CL1-CHA node.
Phone, E-mail: CL1-CHA:NAS OS running

Phone, E-mail: Notify maintenance personnel CL2-CHA:Operating (Performing the
Acknowledge that the failover and ordinary users of the operations of both
has been completed and that the completion of failover and the CL1-CHA and CL2-CHA)
CL1-CHA node has stopped. NAS Package location.
[Acknowledge that the node has [NAS Package location]
stopped]
Check CHA-xx displayed in
Confirm that the NAS Package the 'Browse Cluster Status'
status is INACTIVE in the ‘Main’
window of NAS Blade
window. See 3.5.3 [NAS03-260].
Manager GUI.
1 Monitor the CL2-CHA's
operations.
[NAS04-60]
NAS04-50
NAS04-60 DKC515I
Setup on SVP:
Stop the NAS OS of the
CL1-CHA.
[Stop of the NAS OS]
See 3.5.8 [1] [NAS03-780].
CL1-CHA:NAS OS is not running
The NAS OS starts CL2-CHA:Operating (Performing
NAS frame: automatically when the the operations of both
Replace the board for CL1-CHA. replacement is finished. CL1-CHA and CL2-CHA)
[Replace the NAS

Package]
See [REP01-280].
NAS frame:
By checking the CHL lamp, make
sure that the NAS OS has
started.
Phone, E-mail:
Notify a system administrator of
the NAS Package location that
requires a failback, and ask to
perform a failback and start the
CL1-CHA node.
[NAS04-70]
NAS04-60
NAS04-70 DKC515I
Phone, E-mail: CL1-CHA:NAS OS running

Notify ordinary users of the CL2-CHA:Operating (Performing
failback and get permission for it. the operations of both
CL1-CHA and CL2-CHA)

Manager functionality, start the
CL1-CHA node.
Failing back from CL2-CHA to
CL1-CHA
NAS Management Console: Failback notification

Use the NAS Blade Manager - NAS Blade Manager GUI
functionality to perform a failback (CL2-CHA notification)
from CL2-CHA to CL1-CHA, and - syslog (CL1-CHA notification)
confirm that the failback has
been completed successfully.

Acknowledge that the failback Notify maintenance personnel CL2-CHA: Operating
has been completed and the and ordinary users of the
CL1-CHA node has started. completion of failback and the
NAS Package location.
[Acknowledge that the [NAS Package location]
node has started] Check CHA-xx displayed in
Confirm that the NAS the 'Browse Cluster Status'
Package status is ACTIVE window of NAS Blade
in the ‘Main’ window. See Manager GUI.
3.5.3 [NAS03-260].
End Monitor the CL1-CHA 's
operations.
NAS04-70
NAS04-80 DKC515I
(2) Replacing Data LAN Fiber Optic Cables (During Preventive Replacement)
Replacement
Data LAN fiber

optic cable
CL1-CHA CL2-CHA
Pentium Pentium
NAS OS LU for CL1-CHA NAS OS LU of CL2-CHA NAS Cluster Management LU
SVP Dump LU for CL1-CHA Dump LU of CL2-CHA
User LU
Command Device
User LU
User LU
: Manual failover
: Failback
: Monitoring
Figure 4.2-2 Replacing Data LAN Fiber Optic Cables (During Preventive
Replacement) (1/4)

1 Check the operating status of the Data LAN fiber optic cable (LAN cable) includes
NAS Blade system. the one shared by the control LAN and data LAN.
3 Replace fiber optic cable (LAN
cable) for the data LAN.
4 Check the network status.
NAS04-80
NAS04-90 DKC515I
Replacing Data LAN Fiber

Optic Cables

perform a failover.
NAS Management Console: Failing over from CL1-CHA to

Use the NAS Blade Manager CL2-CHA
functionality to fail over from
CL1-CHA to CL2-CHA and Failback notification
confirm the failover has finished - NAS Blade Manager GUI
successfully. (CL2-CHA notification)
- syslog (CL1-CHA notification)

Acknowledge that the failover Notify maintenance personnel CL1-CHA: NAS OS running
has been completed. and ordinary users of the CL2-CHA: Operating (Performing
completion of the failover and the the operations of both CL1-CHA
NAS Package location. and CL2-CHA)
[NAS Package location]

the 'Browse Cluster Status'
window of NAS Blade
Manager GUI.
1 NAS Management Console:

Monitor the CL2-CHA 's
operations.
[NAS04-100]
Replacement) (2/4)
NAS04-90
NAS04-100 DKC515I
CL1-CHA:NAS OS running
CL2-CHA:Operating (Performing
the operations of both
NAS frame:
Replace the data LAN fiber optic
cable for CL1-CHA.
SVP:
Make sure that the Port Status is
Link Up in the System
Equipment Status window of the
Web Console.
Phone, E-mail: Client:

Ask a system administrator to Confirm that ping to the NAS
check the network status. Package is successful. *1

Acknowledge that the failback Notify maintenance personnel of
has been completed and the the completion of the network
CL1-CHA node has started. status check.
2
*1: Check if you can communicate
[NAS04-110] using the fixed IP address.
Replacement) (3/4)
NAS04-100
NAS04-110 DKC515I
2
CL1-CHA: NAS OS running
CL2-CHA: Operating (Performing
the operations of both CL1-CHA
and CL2-CHA)
Notify a system administrator of Notify ordinary users of the CL1-CHA: NAS OS running
the NAS Package location that failback and get permission for it. CL2-CHA: Operating (Performing
requires a failback, and ask to the operations of both CL1-CHA
perform a failback. and CL2-CHA)
NAS Management Console: Failing back from CL1-CHA to

functionality to fail back from
CL2-CHA to CL1-CHA and Failback notification
confirm the failback has finished - NAS Blade Manager GUI
successfully. (CL2-CHA notification)
- syslog (CL1-CHA notification)

has been completed. and ordinary users of the CL2-CHA: Operating
completion of the failback and
the NAS Package location.
window of NAS Blade
Manager GUI.
End NAS Management Console:

operations.
Replacement) (4/4)
NAS04-110
NAS04-111 DKC515I
(3) Replacing Control LAN Fiber Optic Cables (During Preventive Replacement)
Replacement
Control LAN fiber

optic cable
CL1-CHA CL2-CHA
Pentium Pentium
NAS OS LU for CL1-CHA NAS OS LU of CL2-CHA NAS Cluster Management LU
User LU
Command Device
User LU
User LU
: Manual failover
: Failback
: Monitoring
Figure 4.2-3 Replacing Control LAN Fiber Optic Cables (During Preventive
Replacement) (1/2)

1 Check the operating status of the Control LAN is connected to the port eth1 which
NAS Blade system. is not used for user oprations (The service IP is
not set).
2 Replace fiber optic cable (LAN
cable) for the control LAN.
NAS04-111
NAS04-112 DKC515I
Replacing Control LAN Fiber

Optic Cables
NAS frame:
Replace the control LAN fiber
optic cable for CL1-CHA.
SVP:
Web Console.

Ask a system administrator to Confirm that ping to the NAS
check the network status. Package is successful. *1

Acknowledge that the failback Notify maintenance personnel of
has been completed and the the completion of the network
CL1-CHA node has started. status check.
End *1: Check if you can communicate

using the fixed IP address.
Figure 4.2-3 Replacing Control LAN Fiber Optic Cables (During Preventive
Replacement) (2/2)
NAS04-112
NAS04-115 DKC515I
(4) Maintaining and Replacing External Devices (During Preventive Replacement)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP Command Device
NAS OS LU for CL1-CHA NAS OS LU of CL2-CHA Backup LU of NAS CM LU
User LU External Subsystem Device

: Manual failover
: Failback Maintenance,
: Monitoring Replacement
Figure 4.2-4 Maintaining and Replacing External Devices (During Preventive

Replacement) (1/3)

1 Specify the LDEVs that are defined as external
subsystem devices.
2 Specify the NAS Packages that use those LDEVs.
3 Stop the clusters of the NAS Packages.
4 Stop the NAS OS of the NAS Packages.
5 Maintain and replace the external subsystem devices.
6 Start the NAS OS of the NAS Packages.
7 Start the clusters of the NAS Packages.
NAS04-115
NAS04-116 DKC515I
Maintaining and Replacing External Devices

(During Preventive Replacement)
SVP:
Specify the LDEVs that use
external subsystem devices.
[Specify the LDEVs]

See [SVP02-770].
Phone, E-mail: NAS Management Console:

Notify the LDEV numbers, and Use the NAS Blade Manager CL1-CHA:Operating
ask a system administrator to functionality to specify the CL2-CHA:Operating
specify the NAS Packages that CL1-CHA and CL2-CHA and the
use the LDEVs, and to stop the clusters of the NAS Packages.*1
clusters of the NAS Packages
and NAS OSs.
functionality to stop the clusters CL1-CHA:Running
of CL1-CHA and CL2-CHA. CL2-CHA:Running
Storage Navigator: CL1-CHA:Stopped

Stop the NAS OSs of CL1-CHA CL2-CHA:Stopped
and CL2-CHA using Storage
Navigator.
Setup on SVP: Phone, E-mail:

Stop the NAS OS of CL1-CHA Notify that the NAS OSs of
and CL2-CHA. CL1-CHA and CL2-CHA have
been stopped and the NAS
[Maintenance and Package location, and then ask
replacement of external maintenance personnel for
subsystem] maintenance and replacement.
See [TRBL15-10].
Check CHA-xx displayed in the
'Browse Cluster Status' window of
1 NAS Blade Manager GUI.
[NAS04-117] *1: If the file system in the external subsystem device is a destination file
system of ShadowImage in-system replication or TrueCopy remote
replication/TrueCopy asynchronous extension, release the copy pair, check
and replace the external device as necessary, and recreate the copy pair.

Replacement) (2/3)
NAS04-116
NAS04-117 DKC515I
1 CL1-CHA: Stopped
CL2-CHA: Stopped
Phone, E-mail: Storage Navigator: CL1-CHA: Running

Inform that check and Start the NAS OSs of CL1-CHA CL2-CHA: Running
replacement of external and CL2-CHA using Storage
subsystem has been completed Navigator.
and ask to restart the cluster.
NAS Management Console: CL1-CHA: Operating

Use the NAS Blade Manager CL2-CHA: Operating
functionality to start the clusters
of CL1-CHA and CL2-CHA.*1

Acknowledge that the clusters of Notify maintenance personnel
CL1-CHA and CL2-CHA have that the clusters of CL1-CHA and
been started. CL2-CHA have been started.
End
*1: If the file system in the external subsystem device is a destination file
system of ShadowImage in-system replication or TrueCopy remote
replication/TrueCopy asynchronous extension, release the copy pair, check
and replace the external device as necessary, and recreate the copy pair.

Replacement) (3/3)
NAS04-117
NAS04-120 DKC515I
(5) Hot-replacing Hardware Other Than the NAS Package
Replacement
Target Hardware
CL1-CHA CL1-CHA
Fan, Power
Supply, etc.
Pentium Pentium

User LU
Command Device
User LU
User LU
: Monitoring
: Failed part
Figure 4.2-5 Hot-Replacing Hardware Other than the NAS Package (1/2)

1 Replace the target hardware.
NAS04-120
NAS04-130 DKC515I
Hot-replacing the hardware
CL1-CHA: Operating
CL2-CHA: Operating
The NAS Package status

depends on the hardware to be
replaced.
SVP, Target hardware:
Hot-replace the target hardware.
[Hot replace]
See [REP01-10].
End
NAS04-130
NAS05-10 DKC515I
5. NAS Software FC
This chapter describes operations for maintenance personnel and system administrators on NAS
software FC (upgrade).
5.1 Overview
This section describes software upgrade procedure for the NAS Blade system when a failure occurs
or during preventive maintenance.
You can perform online replacement of micro-programs in a disk subsystem without stopping user
services (except for cases such as when a RAID group is not usable because of a PDEV failure).
NAS05-10
NAS05-20 DKC515I
5.2 Preparing for Software Upgrade Operations (System LU Backup)

In preparation for failing to upgrade the NAS Package program, ask the system administrator to
back up the system LUs (NAS OS LU and NAS Cluster Management LU) when the settings are
added, deleted, or changed by the NAS Blade Manager GUI.
CAUTION
Recovery might not be correct if the state of the NAS Cluster Management LU at the time
of the NAS OS LU recovery differs from the state at the time of the backup.
Ask system administrators to make sure that the following condition is met when a NAS
OS LU recovery is performed:
• Software has not been reconfigured (for example, file systems have not been created or
removed, and NFS or CIFS shares have not been created, removed or changed) since
the last NAS OS LU backup.
NAS05-20
NAS05-30 DKC515I
5.3 Types of Software Upgrade Operations

Software is upgraded in the following two situations (Note that all instances of the same software in
a cluster are upgraded because all the software running on NAS Packages in the same cluster must
be the same version.):
• Upgrade when a software failure occurs

This upgrade operation upgrades the failed software.
• Software preventive upgrade

This upgrade operation is performed for preventive maintenance.
This section describes software preventive upgrade.
Such upgrade operations are classified based on the operations performed by maintenance
personnel or system administrators and the NAS Blade system behavior, as shown in Table 5.3-1.
To perform upgrade operations, always start from the number (#) 1, regardless of whether all target
software must be upgraded or not.
NAS05-30
NAS05-40 DKC515I
Table 5.3-1 Types of NAS Software Upgrade Operations

# Target Can Explanation Installation Provided Upgrade Can Restart Perform Reference
software ordinary procedure by opera- NAS the a for
users tion Manage NAS failback preventive
continue target ment OS? ? upgrade
opera- console
tions? be
*1
used?
1 Setup on Yes FC of Setup on Setup on CD Setup on No No No 3.5.2 [1]
SVP SVP. SVP provided SVP [NAS03-110]
Perform installation by the 3.5.2 [3]
and FC after software [NAS03-200]
uninstallation. developer
2 NAS OS Yes *2 FC of NAS OS. Upgrading CD Setup on No Yes Yes Figure 5.3-1
(upgrade Failover , NAS OS NAS OS provided SVP [NAS05-70]
while FC, and failback are by the NAS
operating) performed. by an software Blade
Windows clients Updated developer Manager
must be Version
reconnected
because services are Upgrading CD Setup on Yes No Yes Figure 5.3-2
stopped. NAS OS provided SVP [NAS05-130]
The same FC is by the NAS
required for all by a Patch software Blade
NAS Packages in Version developer Manager
the same cluster. (restart not
See the ECN for the required)
procedures.
Upgrading CD Setup on Yes Yes Yes Figure 5.3-3
NAS OS provided SVP [NAS05-220]
by the NAS
by a Patch software Blade
Version developer Manager
(restart
required)
3 NAS OS Yes FC of NAS OS. Upgrading CD Setup on No Yes*3 No Figure 5.3-4
(upgrade All services are NAS OS provided SVP [NAS05-320]
while the stopped, NAS OS by the NAS
cluster is FC is performed, by an software Blade
stopped) and the cluster is Updated developer Manager
started. Version
The same FC is Upgrading CD Setup on Yes No No Figure 5.3-5
required for all provided SVP
NAS Packages in
NAS OS [NAS05-360]
by the NAS
the same cluster. by a Patch software Blade
See the ECN for the Version developer Manager
procedures. (restart not
required)
Upgrading CD Setup on Yes Yes No Figure 5.3-6
NAS OS provided SVP [NAS05-430]
by the NAS
by a Patch software Blade
Version developer Manager
(restart
required)
NAS05-40
NAS05-50 DKC515I

# Target Can Explanation Installation Provided Upgrade Can Restart Perform Reference
software ordinary procedure by opera- NAS the a for
users tion Manage NAS failback preventive
continue target ment OS? ? upgrade
opera- console
tions? be
*1
used?
4 NAS Blade Yes FC of NAS Blade Upgrading CD Setup on Yes No No Figure 5.3-7
Manager Manager. NAS Blade provided SVP [NAS05-500]
The same FC is Manager by the NAS
required for all software Blade
NAS Packages in developer Manager
the same cluster.
5 Optional Yes *3 FC of optional Upgrading CD Setup on Yes No No Figure 5.3-8
program program product. an provided SVP [NAS05-520]
product The same FC is by the NAS
required for all Optional software Blade
NAS Packages in Program developer Manager
the same cluster. Product
The target
optional
program product
must be
stopped.
*1: This is the upgrade operation that a system administrator performs using the NAS Management
Console.
*2: Yes: Operations is possible while online.
However, CIFS share is released when a failover or failback occur. Therefore you must
reconnect the server with CIFS share if there are windows clients (CIFS share) connecting the
application server.
Also, when you update the NAS OS in an environment where the CIFS service configuration is
defined to use user mapping, you must once change the CIFS service configuration definition
not to use user mapping, and then redefine the CIFS service configuration to use user mapping.
No: Offline. All applications must be stopped.
*3: However, the target optional program product must be stopped.
NAS05-50
NAS05-60 DKC515I
5.3.1 Flowcharts for Upgrading NAS Software
In this section, the cluster is assumed to consist of CL1-CHA and CL2-CHA, and Figure
5.3-1 through Figure 5.3-8 show examples of flowcharts of upgrading software on CL1-
CHA.
Make sure that CL2-CHA is properly referred to as the actual location when upgrading
software on the CHA location.

Flexible cabinet model Basic 1E 2Q
Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
(1) Upgrading Setup on SVP
The procedures for upgrading Setup on SVP are the same as installing Setup on SVP.
For the procedures for upgrading Setup on SVP, see 3.5.2 [1] Installing Setup on SVP [NAS03-
110].
NAS05-60
NAS05-70 DKC515I
(2) Upgrading NAS OS by an Updated Version (Preventive Upgrade: While Operating)
CL1-CHA CL2-CHA
Upgrade Optional Program Optional Program

by an Product
Pentium Product
Pentium
updated
NAS Blade Manager NAS Blade Manager
version
MP NAS OS MP MP NAS OS MP
SVP Dump LU for CL1-CHA Dump LU for CL2-CHA NAS Cluster Management
Error Information LU LU
Command Device
Command Device
User LU
Command Device
User LU
New User LU
version

: Failback
: Monitoring
Figure 5.3-1 Upgrading NAS OS by an Updated Version

(Preventive Upgrade: While Operating) (1/6)

1 Obtain the corrected version (NAS OS).
2 Back up NAS OS LU and NAS Cluster
Management LU.
3 Check the operating status of the NAS Blade
system.
5 Stop the node.
6 Upgrade NAS OS by an updated version.
7 Upgrade NAS Blade Manager.
8 Start the node.
9 Perform failback.
NAS05-70
NAS05-80 DKC515I
Upgrading NAS OS by an updated version

(preventive upgrade: While Operating)
Postal service: CL1-CHA: Operating

Obtain the new version from the CL2-CHA: Operating
software developer.
Phone, E-mail: NAS Management console:

Ask a system administrator to Back up the NAS OS LU and NAS
back up the NAS OS LU and NAS Cluster Management LU
Cluster Management LU.

Acknowledge that the NAS OS LU Notify the maintenance personnel
and NAS Cluster Management LU of the completion of NAS OS LU
have been backed up. and NAS Management LU
backup.
YES
Is NAS OS on
CL1-CHA
stopped? NAS Blade Manager
starts with the NAS OS.
See the 'Main' window
in 3.5.3 [NAS03-260].
Setup on SVP:
Start NAS OS on CL1-CHA.
[Start NAS OS]

See 3.5.8 [2] [NAS03-820].
1 2
[NAS05-90] [NAS05-100]

NAS05-80
NAS05-90 DKC515I

perform a failover.
Is the failover
permitted?
NO
YES Failing over from CL1-CHA to

CL2-CHA
Use the NAS Blade Manager Failover notification
functionality to perform a failover - NAS Blade Manager GUI
from CL1-CHA to CL2-CHA, and (CL2-CHA notification)
confirm that the failover has been - syslog (CL2-CHA notification)
completed.

CL1-CHA node.
Phone, E-mail:
Phone, E-mail: Notify maintenance personnel
Acknowledge that the failover and ordinary users of the
has been completed and that the completion of failover and the
CL1-CHA node has stopped. the operations of both
[Acknowledge that the node has
stopped] [NAS Package location]
Confirm that the NAS Package Check CHA-xx displayed in
status is INACTIVE in the ‘Main’ the 'Browse Cluster Status'
window. See 3.5.3 [NAS03-260]. window of NAS Blade
Manager GUI.
2 Monitor the CL2-CHA's
operations.
[NAS05-100]

NAS05-90
NAS05-100 DKC515I
[NAS05-100]
YES
Is CL1-CHA node
stopped? 3
NO [Is the node stopped?]

Check if the NAS Package

Ask a system administrator to Use the NAS Blade Manager
stop the CL1-CHA node. functionality to stop the CL1-CHA node.

Acknowledge that stopping the Notify the maintenance
CL1-CHA node has been personnel of the completion of
completed. stopping the CL1-CHA node.
stopped]
3 Confirm that the NAS Package
Setup on SVP:
Upgrade NAS OS by an updated
version on CL1-CHA *1
[Upgrading NAS OS
by an updated
version] Perform an upgrade
See 5.3.2 [1] operation again.
[NAS05-570].
Has the upgrade

NO
operation been
completed
successfully?
YES CL1-CHA:NAS OS running

[Has the upgrade operation been
completed successfully?]
The status in the 'Install Progress'
window becomes 'Completed'.
See 5.3.2 [1] (9) [NAS05-660].
4
*1: NAS OS and NAS Blade Manager
[NAS05-110] can be upgraded concurrently.

NAS05-100
NAS05-110 DKC515I
4
Setup on SVP:
Upgrading NAS Blade Manager
on CL1-CHA. *1
[Upgrading NAS Blade

Manager]
See 5.3.2 [3] [NAS05-720].
Phone, E-mail:
Notify that CL1-CHA has been
started.
5
*1: NAS OS and NAS Blade Manager can
be upgraded concurrently.
[NAS05-120]

NAS05-110
NAS05-120 DKC515I
Phone, E-mail:
Notify ordinary users of a failback
and get permission for it.
[NAS05-80] NAS Management Console:

a Manager functionality, start the
CL1-CHA node.
Perform the same Failing back from CL2-CHA to

operations for CL2-CHA. NAS Management Console: CL1-CHA
functionality to perform a manual Failback notification
failback from CL2-CHA to - NAS Blade Manager GUI
CL1-CHA, and confirm that the (CL1-CHA notification)
failback has been completed. - syslog (CL1-CHA notification)

Acknowledge that the failback Notify maintenance personnel
has been completed and that the and ordinary users of the CL1-CHA: Operating
CL1-CHA node has started. completion of failback and the CL2-CHA: Operating
[Acknowledge that the NAS Package location.
node has started]
Confirm that the NAS [NAS Package location]
Package status is Check CHA-xx displayed in
ACTIVE in the ‘Main’ the 'Browse Cluster Status'
window. See 3.5.3 window of NAS Blade
[NAS03-260]. Manager GUI.
NO
Have the tasks NAS Management Console:
been completed for both Monitor the CL1-CHA 's
NAS Packages? operations.
YES
[Finish the NAS OS by a
regular or corrected
version]
See the 'Install Progress'
window in 5.3.2 [1] (10)
[NAS05-660].
End

NAS05-120
NAS05-130 DKC515I
(3) Replacing the NAS OS By a Patch Version  Restarting the NAS OS Is Not Required
(Preventive Upgrade: While Operating)
New
version
CL1-CHA CL2-CHA
NAS
Management
Console Optional Program Optional Program
Product
Pentium Product
Pentium

Upgrade by MP NAS OS MP MPNAS OS MP Backup LU of NAS CM LU
a patch
version Backup LU of NAS CM LU

Dump LU for CL1-CHA Dump LU for CL2-CHA NAS Cluster Management LU
SVP Error Information LU
(Maintenance
Personnel)
New User LU Command Device
version
: Failback
: Monitoring
Figure 5.3-2 Upgrading NAS OS By a Patch Version 
Restarting the NAS OS Is Not Required (Preventive Upgrade: While Operating) (1/9)

1 Obtain the corrected version (NAS
OS).
2 Back up the NAS OS LU and NAS
3 Check the operating status of the NAS
Blade system.
5 Start the NAS OS. Do this only if the NAS OS of the target NAS
Package is not running.
6 Upgrade NAS OS by a patch version.
7 Perform failback.
NAS05-130
NAS05-140 DKC515I
Replacing the NAS OS by a patch version  Restarting the

NAS OS is not required (preventive upgrade: While Operating)
Are program
products managed by
maintenance NO
personnel?
YES
Postal service:
1
Obtain the new version from the
software developer.
[NAS05-170]


backup.
YES
Is NAS OS on
CL1-CHA stopped?
NAS Blade Manager
starts with the NAS OS.
in 3.5.3 [NAS03-260].
Setup on SVP:
[Start NAS OS]

See 3.5.8 [2] [NAS03-820].
2 3
[NAS05-150] [NAS05-160]

NAS05-140
NAS05-150 DKC515I

perform a failover.
Failing over from CL1-CHA to

NAS Management Console: CL2-CHA
Phone, E-mail:
Phone, E-mail: Notify maintenance personnel CL1-CHA:NAS OS running
Acknowledge that the failover and ordinary users of the CL2-CHA:Operating (Performing
has been completed. completion of failover and the the operations of both
NAS Package location. CL1-CHA and CL2-CHA)
window of NAS Blade
3 Manager GUI.

[NAS05-160] Monitor the CL2-CHA's
operations.

NAS05-150
NAS05-160 DKC515I
[NAS05-200]
YES
Is CL1-CHA node
running? 4
NO [Is the node running?]

status is ACTIVE in the ‘Main’

start the CL1-CHA node. functionality to start the
CL1-CHA node.

Acknowledge that starting the Notify the maintenance
CL1-CHA node has been personnel of the completion of
completed. starting the CL1-CHA node.
[Acknowledge that the node

has started]
Confirm that the NAS Package
window. See 3.5.3
[NAS03-260].
[NAS05-200]

NAS05-160
NAS05-170 DKC515I
Postal service:
software developer.

Check if NAS OS on CL1-CHA is Ask maintenance personnel to
running. check if NAS OS on CL1-CHA is
running.
[Is NAS OS stopped?]

in 3.5.3 [NAS03-260].
Phone, E-mail:
Notify a system administrator
that NAS OS on CL1-CHA is
running or not.
Is NAS OS on YES
CL1-CHA stopped?
NO
Setup on SVP:
Start NAS OS on CL1-CHA. Phone, E-mail:
Ask maintenance personnel to
start NAS OS on CL1-CHA.
Start NAS OS
See 3.5.8 [2] [NAS03-820].
6 5
[NAS05-190] [NAS05-180]

NAS05-170
NAS05-180 DKC515I
Phone, E-mail:
Notify ordinary users of a failover
CL1-CHA: Operating
functionality to perform a failover Failing over from CL1-CHA to
from CL1-CHA to CL2-CHA, and CL2-CHA
confirm that the failover has
been completed. Failover notification
Phone, E-mail: Phone, E-mail: - syslog (CL2-CHA notification)
Acknowledge that the failover Notify maintenance personnel
has been completed. and ordinary users of the
completion of failover and the
[NAS Package location] CL1-CHA:NAS OS running
Check CHA-xx displayed in CL2-CHA:Operating (Performing
the 'Browse Cluster Status' the operations of both
window of NAS Blade CL1-CHA and
Manager GUI. CL2-CHA)
operations.
[NAS05-210]

NAS05-180
NAS05-190 DKC515I
[NAS05-210]
YES
Is CL1-CHA node
running? 7
NO [Is the node running?]

Check if that the NAS Package

start the CL1-CHA node. functionality to start the CL1-CHA
node.

Acknowledge that starting the Notify the maintenance personnel
CL1-CHA node has been of the completion of starting the
completed. CL1-CHA node.

started]
7
[NAS05-210]

NAS05-190
NAS05-200 DKC515I
Setup on SVP:
Upgrading NAS OS by a patch
version on CL1-CHA from SVP.
[Upgrading NAS OS by a
patch version]
See 5.3.2 [2] [NAS05-670].
Has the upgrade NO CL1-CHA:Operating (Performing
operation been completed the operations of both
successfully? Perform an upgrade
operation again.
YES [Has the upgrade operation been
completed successfully?]
See 5.3.2 [2] (8) [NAS05-700].
Request
Notify a system
a systemadministrator
administrator
of Notify ordinary users of the
to perform
the a failback.
NAS Package location that failback and gets permission for it.
perform a failback. Failing back from CL2-CHA to
[NAS05-140] Use the NAS Blade Manager
a CL1-CHA, and confirm that the (CL1-CHA notification)
Perform the same
operations for CL2-CHA.

completion of failback and the
Have the tasks
been completed for both
NO NAS Packages?
window of NAS Blade
Manager GUI.
[Finish the NAS Package by a
YES regular or corrected version]
See the 'Program Install'
window in 5.3.2 [2] (9)
[NAS05-710].
End

NAS05-200
NAS05-210 DKC515I

functionality to upgrade NAS OS
by a patch version on CL1-CHA.
Perform an upgrade
operation again.
Has the upgrade CL2-CHA:Operating (Performing
operation been completed the operations of both
successfully? NO CL1-CHA and CL2-CHA)
YES
Phone, E-mail: CL2-CHA:Operating (Performing
Notify ordinary users of the the operations of both
failback and gets permission for CL1-CHA and CL2-CHA)
it.
Failing back from CL2-CHA to


Acknowledge that the failback Notify maintenance
Notify maintenance personnel
personnel and
has been completed. and ordinary users that the
ordinary users of the completion of CL1-CHA: Operating
failback has been completed. CL2-CHA: Operating
failback and the NAS Package location.
[NAS05-170] [NAS Package location]
b the 'Browse Cluster Status'
window of NAS Blade
Manager GUI.
Perform the same
operations for Have the tasks
CL2-CHA. been completed for both
NO NAS Packages?
YES
End

Restarting the NAS OS Is Not Required (Preventive Upgrade: While Operating)
(9/9)
NAS05-210
NAS05-220 DKC515I
(4) Replacing the NAS OS By a Patch Version  Restarting the NAS OS Is Required (Preventive
Upgrade: While Operating)
New
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium

Upgrade by MP NAS OS MP MPNAS OS MP Backup LU of NAS CM LU
a patch
version Backup LU of NAS CM LU

Dump LU for CL1-CHA Dump LU for CL2-CHA NAS Cluster Management LU
(Maintenance
Personnel)
New User LU Command Device
version
: Failback
: Monitoring
Restarting the NAS OS Is Required (Preventive Upgrade: While Operating) (1/10)

2 Back up the NAS OS LU and NAS Cluster
Management LU.
3 Check the operating status of the NAS Blade
system.
5 Stop the node.
6 Start the NAS OS. Do this only if the NAS OS of the target
NAS Package is not running.
7 Operate the software according to the relevant Do this only if NAS OS definitions have
documentation provided with the software. changed.
8 Upgrade NAS OS by a patch version.
9 Restart the NAS OS. Use the NAS Blade Manager functionality to
perform NAS OS upgrade by a patch version.
10 Start the node.
11 Perform failback.
NAS05-220
NAS05-230 DKC515I
Replacing the NAS OS by a patch version  Restarting the NAS OS is

required (preventive upgrade: While Operating)
Are program
products managed by
maintenance NO
personnel?
YES
Postal service:
Obtain the new version from the 1
software developer.
[NAS05-260]
a


backup.
Is NAS OS on YES
CL1-CHA stopped?
NO [Is NAS OS stopped?] NAS Blade Manager

See the 'Main' window starts with the NAS OS.
in 3.5.3 [NAS03-260].
Setup on SVP:
[Start NAS OS]

See 3.5.8 [2] [NAS03-820].
2 3
[NAS05-240] [NAS05-250]

NAS05-230
NAS05-240 DKC515I

Notify ordinary users of the CL2-CHA: Operating
failover and get permission for it.
perform a failover.
Failing over from CL1-CHA to


CL1-CHA node.
Phone, E-mail: Phone, E-mail: CL1-CHA:NAS OS running

Acknowledge that the failover Notify maintenance personnel CL2-CHA:Operating (Performing the
has been completed and that the and ordinary users of the operations of both
CL1-CHA node has stopped. completion of failover and the CL1-CHA and CL2-CHA)
[Acknowledge that the
node has stopped] [NAS Package location]
Confirm that the NAS Check CHA-xx displayed in
Package status is the 'Browse Cluster Status'
INACTIVE in the ‘Main’ window of NAS Blade
window. See 3.5.3 Manager GUI.
[NAS03-260].
4 Monitor the CL2-CHA 's
operations.
[NAS05-290]

NAS05-240
NAS05-250 DKC515I
[NAS05-290]
YES
Is CL1-CHA node
stopped? 4

Confirm that the NAS
Package status is INACTIVE
in the ‘Main’ window. See
3.5.3 [NAS03-260].

stop the CL1-CHA node. functionality to stop the CL1-CHA
node if it is active.

Acknowledge that stop of the Notify the maintenance personnel
CL1-CHA node has been of the completion of stopping the
[Acknowledge that the node is
stopped]
status is INACTIVE in the
‘Main’ window. See 3.5.3
[NAS03-260].
[NAS05-290]

NAS05-250
NAS05-260 DKC515I
Postal service:
software developer.

Check if NAS OS on CL1-CHA is Ask maintenance personnel to
running. check if NAS OS on CL1-CHA is
running.

in 3.5.3 [NAS03-260].
Phone, E-mail:
Notify a system administrator
that NAS OS on CL1-CHA is
running or not.
Is NAS OS on YES
CL1-CHA stopped?
NO
Setup on SVP:
Start NAS OS on CL1-CHA. Phone, E-mail:
start NAS OS on CL1-CHA.
Start NAS OS
See 3.5.8 [2] [NAS03-820].
6 5
[NAS05-280] [NAS05-270]

NAS05-260
NAS05-270 DKC515I
Phone, E-mail:
Notify ordinary users of a failover
CL1-CHA: Operating
functionality to perform a failover Failing over from CL1-CHA to
from CL1-CHA to CL2-CHA, and CL2-CHA
confirm that the failover has
been completed. Failover notification
NAS Management Console: - syslog (CL2-CHA notification)
CL1-CHA node.
Phone, E-mail: Phone, E-mail: CL1-CHA:NAS OS running

Acknowledge that the failover Notify maintenance personnel CL2-CHA:Operating (Performing
has been completed and that and ordinary users of the the operations of both
the CL1-CHA node has completion of failover and the CL1-CHA and
stopped. NAS Package location. CL2-CHA)
node has stopped] Check CHA-xx displayed in
Package status is window of NAS Blade
INACTIVE in the ‘Main’ Manager GUI.
window. See 3.5.3
[NAS03-260]. NAS Management Console:
operations.
[NAS05-310]

NAS05-270
NAS05-280 DKC515I
[NAS05-310]
YES
Is CL1-CHA node
stopped? 7

[NAS03-260].

stop the CL1-CHA node. functionality to stop the CL1-CHA
node.

Acknowledge that stopping the Notify the maintenance personnel
CL1-CHA node has been of the completion of stopping the
[Acknowledge that the node

has stopped]
[NAS03-260]. 7
[NAS05-310]

NAS05-280
NAS05-290 DKC515I
Setup on SVP:
Upgrading NAS OS by a patch
version on CL1-CHA from SVP.
Upgrading NAS OS by a
patch version Perform an upgrade
See 5.3.2 [2] [NAS05-670]. operation again.
NO
Has the upgrade
operation been
completed
Has the upgrade operation been

YES completed successfully?
See 5.3.2 [2] (8) [NAS05-700].
Setup on SVP: the operations of both
Reboot NAS OS on CL1-CHA. CL1-CHA and CL2-CHA)
[Reboot NAS OS]
See 3.5.8 [3] [NAS03-840]

Notify a system administrator that Notify ordinary users of the
the NAS OS on CL1-CHA has been failback and get permission for it.
rebooted, and request the system CL1-CHA Restarting
administrator to perform a failback. CL2-CHA:Operating (Performing
NAS Management Console: the operations of both
Use the NAS Blade Manager CL1-CHA and
functionality to start the CL2-CHA)
CL1-CHA node.
[NAS05-300]

NAS05-290
NAS05-300 DKC515I
[NAS05-230] NAS Management Console: Failing back from CL2-CHA to

a
Perform the same
operations for
CL2-CHA.

has been completed and that and ordinary users of the CL1-CHA: Operating
the CL1-CHA node has started. CL2-CHA: Operating
node has started] [NAS Package location]
Confirm that the NAS Check CHA-xx displayed in
Package status is ACTIVE the 'Browse Cluster Status'
in the ‘Main’ window. See window of NAS Blade
3.5.3 [NAS03-260]. Manager GUI.
Have the tasks

NO NAS Packages?
YES Finish the NAS Package by a

regular or corrected version
See the 'Program Install' window
in 5.3.2 [2] (9) [NAS05-710].
End

NAS05-300
NAS05-310 DKC515I

functionality to upgrade NAS OS
by a patch version on CL1-CHA.
Perform an upgrade
operation again.
Has the upgrade the operations of both
operation been completed CL1-CHA and CL2-CHA)
successfully? NO
YES
Reboot the NAS OS on CL1-CHA.
Phone, E-mail:
Notify ordinary users of the
failback and get permission for it.
CL1-CHA:Restarting
NAS Management Console: the operations of both
Use the NAS Blade Manager CL1-CHA and CL2-CHA)
functionality to start the
CL1-CHA node. Failing back from CL2-CHA to
CL1-CHA
Use the NAS Blade Manager Failback notification
functionality to perform a manual - NAS Blade Manager GUI
failback from CL2-CHA to (CL1-CHA notification)
CL2-CHA, and confirm that the - syslog (CL1-CHA notification)
failback has been completed.

Acknowledge that the failback Notify maintenance personnel and
has been completed and that the ordinary users of the completion CL1-CHA: Operating
CL1-CHA node has started. of failback and the NAS Package CL2-CHA: Operating
[Acknowledge that the node [NAS05-260] location.
has started] [NAS Package location]
Confirm that the NAS Package b Check CHA-xx displayed in the
status is ACTIVE in the ‘Main’ 'Browse Cluster Status' window of
window. See 3.5.3 NAS Blade Manager GUI.
[NAS03-260].
Have the tasks
Perform the same been completed for both
operations for NO
NAS Packages?
CL2-CHA.
YES
End

NAS05-310
NAS05-320 DKC515I
(5) Upgrading NAS OS by an Updated Version (Preventive Upgrade: While the Cluster is
Stopped)
CL1-CHA CL2-CHA
Optional Program Optional Program

Product
Pentium Product
Pentium
MP NAS OS MP MPNAS OS MP Backup LU of NAS CM LU
Upgrade by Backup LU of NAS CM LU

an updated
version

User LU
New User LU
version
: Monitoring
Figure 5.3-4 Upgrading NAS OS by an Updated Version (Preventive Upgrade:

While the Cluster is Stopped) (1/4)

Management LU.
3 Stop the cluster.
4 Upgrade NAS OS by an updated version.
6 Start the cluster.
NAS05-320
NAS05-330 DKC515I
Upgrading NAS OS by an updated version (offline) (preventive

upgrade: While the Cluster is Stopped)
Postal service:
software developer.

Ask a system administrator to Back up the NAS OS LU and
back up the NAS OS LU and NAS NAS Cluster Management LU

Acknowledge that the NAS OS Notify the maintenance personnel
LU and NAS Cluster of the completion of NAS OS LU
Management LU have been and NAS Cluster Management
backed up. LU backup.

Ask a system administrator to Notify ordinary users of stopping CL2-CHA: Operating
stop the cluster of CL1-CHA and the cluster and get permission
CL2-CHA. for it.
Permitted?
NO
YES

Manager functionality, stop the CL1-CHA:NAS OS running
cluster of CL1-CHA and CL2-CHA:NAS OS running
CL2-CHA.
Phone, E-mail:
Acknowledge that stopping the
cluster of CL1-CHA and Phone, E-mail:
CL2-CHA has been completed. Notify the maintenance
personnel that stopping the
[Acknowledge that the cluster of CL1-CHA and
cluster is stopped] CL2-CHA has been completed.
Make sure that the NAS
OS Package status is
INACTIVE in Main window.
See 3.5.3 [NAS03-260].
[NAS05-340]

NAS05-330
NAS05-340 DKC515I
Setup on SVP:
Upgrading NAS OS by an
updated version on CL1-CHA
from SVP. *1
updated version
See 5.3.2 [1] [NAS05-570].
Perform an upgrade
NO operation again.
Has the
upgrade operation
been completed
successfully?
YES Finish the NAS OS installation.

The status in the 'Install
Perform the same Progress' window becomes
operations for 'Completed'.
CL2-CHA. See 5.3.2 [1] (9) [NAS05-660].
NO Have the
tasks been completed for
both NAS Packages?
YES
2
[NAS05-350] can be upgraded concurrently.

NAS05-340
NAS05-350 DKC515I
Setup on SVP: CL1-CHA:NAS OS running

Upgrading NAS Blade Manager CL2-CHA:NAS OS running
on CL1-CHA *1

See 5.3.2 [3] [NAS05-720].
Perform the same

operations for
CL2-CHA.
NO Have the
both NAS Packages?
YES Finish the NAS Package by a

See the ‘Program Install’ window
in 5.3.2 [1] (10) [NAS05-660].
Phone, E-mail: NAS Management Console: CL1-CHA: Operating

Ask a system administrator to By using the NAS Blade Manager CL2-CHA: Operating
start the cluster of CL1-CHA and functionality, start the cluster of
CL2-CHA. CL1-CHA and CL2-CHA.
*1: NAS OS and NAS Blade

Manager can be upgraded
End
concurrently.

NAS05-350
NAS05-360 DKC515I
(6) Replacing the NAS OS By a Patch Version  Restarting the NAS OS Is Not Required
(Preventive Upgrade: While the Cluster is Stopped)
New
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium
Upgrade NAS Blade Manager NAS Blade Manager
MP NAS OS MP MPNAS OS MP Backup LU of NAS CM LU


Dump LU for CL1-CHA Dump LU for CL2-CHA
(Maintenance
Personnel)

User LU
New User LU
version
: Monitoring
Figure 5.3-5 Replacing the NAS OS By a Patch Version  Restarting the NAS OS
Is Not Required (Preventive Upgrade: While the Cluster is Stopped) (1/5)

Management LU.
3 Stop the cluster.
4 Upgrade NAS OS by a Patch Version.
NAS05-360
NAS05-370 DKC515I
Replacing the NAS OS By a Patch Version  Restarting the NAS OS

Is Not Required (Preventive Upgrade: While the Cluster is Stopped)
Are program
products managed by
maintenance personnel?
NO
YES
Postal service:
software developer.
[NAS05-390]

Ask a system administrator to Back up the NAS OS LU and
back up the NAS OS LU and NAS NAS Cluster Management LU

Acknowledge that the NAS OS Notify the maintenance personnel
LU and NAS Cluster of the completion of NAS OS LU
Management LU have been and NAS Management LU
backed up. backup.

Ask a system administrator to Notify ordinary users of stopping CL2-CHA: Operating
stop the cluster of CL1-CHA and the cluster and get permission
CL2-CHA. for it.
Permitted?
NO
YES
NAS Management Console: CL1-CHA:NAS OS running

By using the NAS Blade Manager CL2-CHA:NAS OS running
functionality, stop the cluster of
CL1-CHA and CL2-CHA.
[NAS05-380]
NAS05-370
NAS05-380 DKC515I

Acknowledge that stopping the Notify the maintenance personnel
cluster of CL1-CHA and that stopping the cluster of
CL2-CHA has been completed. CL1-CHA and CL2-CHA has been
completed.
cluster is stopped] CL1-CHA:NAS OS running
Make sure that the NAS CL2-CHA:NAS OS running
OS Package status is
INACTIVE in Main window.
See 3.5.3 [NAS03-260].
Setup on SVP:
from SVP. *1
updated version
See 5.3.2 [2] [NAS05-670].
Perform an upgrade
NO operation again.
Has the
upgrade operation
been completed
successfully?
Perform the same
operations for
See 5.3.2 [2] (8) [NAS05-700].
CL2-CHA.
NO Have the
both NAS Packages?
YES
CL1-CHA: Operating
CL2-CHA: Operating
Ask a system administrator to By using the NAS Blade Manager
End *1: NAS OS and NAS Blade Manager

can be upgraded concurrently.
NAS05-380
NAS05-390 DKC515I
Postal service:
software developer.
Phone, E-mail:
Notify ordinary users of stopping CL1-CHA: Operating
the cluster of CL1-CHA and CL2-CHA: Operating
CL2-CHA, and get permission for
it.
Permitted?
NO
YES

By using the NAS Blade Manager CL1-CHA:NAS OS running
functionality, stop the cluster of CL2-CHA:NAS OS running
[NAS05-400]
NAS05-390
NAS05-400 DKC515I
Setup on SVP:
from SVP. *1
Has the NO Perform an upgrade

upgrade operation been operation again.
completed successfully?
YES
Perform the same
operations for
CL2-CHA.
NO Have the
both NAS Packages?
YES
CL1-CHA: Operating
CL2-CHA: Operating

Manager functionality, start the
cluster of CL1-CHA and

End
NAS05-400
NAS05-410 DKC515I
Blank Sheet
NAS05-410
NAS05-420 DKC515I
Blank Sheet
NAS05-420
NAS05-430 DKC515I
(7) Replacing the NAS OS By a Patch Version  Restarting the NAS OS Is Required (Preventive
Upgrade: While the Cluster is Stopped)
New
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium

MP NAS OS MP MPNAS OS MP


(Maintenance
Personnel)
User LU
User LU
New
version
: Monitoring
Is Required (Preventive Upgrade: While the Cluster is Stopped) (1/6)

Management LU.
3 Stop the cluster.
4 Upgrade NAS OS by a Patch Version.
5 Reboot NAS OS.
NAS05-430
NAS05-440 DKC515I
Replacing the NAS OS By a Patch Version  Restarting the NAS OS

Is Required (Preventive Upgrade: While the Cluster is Stopped)
Are program
products managed by
maintenance NO
personnel?
YES
Postal service:
software developer.
[NAS05-470]


backup.

Ask a system adminisrator to Notify ordinary users of stopping CL2-CHA: Operating
stop the cluster of CL1-CHA and the cluster ang get permission
CL2-CHA. for it.
Permitted?
NO
YES

By using the NAS Blade Manager
functionality, stop the cluster of CL1-CHA:NAS OS running
CL1-CHA and CL2-CHA. CL2-CHA:NAS OS running
[NAS05-450]
NAS05-440
NAS05-450 DKC515I

Acknowledge that stopping the Notify the maintenance
cluster of CL1-CHA and personnel that stopping the
CL2-CHA has been completed. cluster of CL1-CHA and
CL2-CHA has been completed.
[Acknowledge that the cluster
is stopped]
Make sure that the NAS OS
Package status is INACTIVE CL2-CHA:NAS OS running
in Main window. See 3.5.3
[NAS03-260].
Setup on SVP:
Upgrading
Install NASOS
the NAS OSon
byCL1-CHA
an
updated
from the version
SVP. on CL1-CHA
from SVP. *1
Upgrading NAS OS by a
patch version
See 5.3.2 [2] [NAS05-670].
Perform an upgrade
Has the operation again.
upgrade operation been NO

Progress' window becomes
'Completed'.
See 5.3.2 [2] (8) [NAS05-700].
Setup on SVP:
Reboot NAS OS on CL1-CHA.
[Reboot NAS OS]

Perform the same See 3.5.8 [3] [NAS03-840]
operations for
CL2-CHA.
NO Have the
both NAS Packages?
YES
[NAS05-460]
NAS05-450
NAS05-460 DKC515I
CL1-CHA: Operating
CL2-CHA: Operating

Ask a system administrator to By using the NAS Blade Manager
End
NAS05-460
NAS05-470 DKC515I
Postal service:
software developer.
Phone, E-mail:
Notify ordinary users of stopping CL1-CHA: Operating
the cluster of CL1-CHA and CL2-CHA: Operating
CL2-CHA, and get permission for
it.
Permitted?
NO
YES

functionality, stop the cluster of
[NAS05-480]
NAS05-470
NAS05-480 DKC515I
Setup on SVP:
from SVP. *1
Has the NO Perform an upgrade

upgrade operation operation again.
been completed
successfully?
YES
Setup on SVP:
Reboot NAS OS on CL1-CHA.
Perform the same

operations for
CL2-CHA.
NO Have the
both NAS Packages?
CL1-CHA: Operating
YES CL2-CHA: Operating

functionality, start the cluster of

End can be upgraded concurrently.
NAS05-480
NAS05-490 DKC515I
Blank Sheet
NAS05-490
NAS05-500 DKC515I
(8) Upgrading NAS Blade Manager (Preventive Upgrade)
New
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium



(Maintenance
Personnel)
User LU
User LU
New
version
: Monitoring
Figure 5.3-7 Upgrading NAS Blade Manager

(Preventive Upgrade) (1/2)

1 Obtain the corrected version (NAS Blade
Manager).
NAS05-500
NAS05-510 DKC515I

(preventive upgrade)
Are program
products managed by
maintenance NO
personnel?
YES
CL1-CHA: Operating
Postal service: Postal service: CL2-CHA: Operating
Obtain the new version from the Obtain the new version from the
software developer. software developer.
Setup on SVP: NAS Management Console:

Update NAS Blade Manager on Update NAS Blade Manager on
CL1-CHA by installing it from the CL1-CHA by using the NAS
SVP. Blade Manager functionality to
install it.
Update NAS Blade
Manager
See 5.3.2 [3]
[NAS05-720].
Perform an upgrade Perform an upgrade
operation again. operation again.
Has the upgrade Has the upgrade

NO NO
operation been completed operation been completed
successfully? successfully?
YES Has the upgrade operation YES

been completed successfully?
Perform the 'Completed'. Perform the same
same operations See 5.3.2 [3] (8) operations for
for CL2-CHA [NAS05-750]. CL2-CHA.
Have the tasks Have the tasks

been completed for both been completed for both
NAS Packages? NO NAS Packages?
NO
Finish the NAS Package by a
YES YES
See the 'Program Install' window
in 5.3.2 [3] (9) [NAS05-750].
End End
Figure 5.3-7 Upgrading NAS Blade Manager

NAS05-510
NAS05-520 DKC515I
(9) Upgrading an Optional Program Product (Preventive Upgrade)
New
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium



(Maintenance
Personnel)
User LU
User LU
New
version
: Monitoring
Figure 5.3-8 Upgrading an Optional Program Product


1 Obtain the corrected version (optional program
product).
2 Stop the function of an optional program
product.
3 Upgrade an optional program product.
NAS05-520
NAS05-530 DKC515I
Upgrading an optional program product (preventive upgrade)
Are program CL1-CHA: Operating

products managed by CL2-CHA: Operating
maintenance NO
personnel?
YES
Postal service:
software developer.
[NAS05-540]

Request a system administrator Request ordinary users to stop
to stop the optional program the optional program product.
product.
Is the optional NO
program product on CL1-CHA
running?
YES
CL1-CHA: Operating
NAS Management Console: (The optional features are not
Stop the optional program operating.)
product on CL1-CHA. CL2-CHA:Operating

Upgrade the optional program Notify maintenance personnel
product by an updated version, on that the optional program product
CL1-CHA. has been stopped.
Update optional program
products
See 5.3.2 [4] [NAS05-760].
Perform an upgrade
Has the upgrade operation again.
operation been completed
successfully? NO
YES Has the upgrade operation been
Perform the The status in the 'Install Progress'
same operations window becomes 'Completed'.
for CL2-CHA. See 5.3.2 [4] (8) [NAS05-790].
Have the tasks
NO NAS Packages?
Finish the NAS Package by a regular or
YES corrected version
See the 'Program Install' window in 5.3.2
[4] (9) [NAS05-790].
End

NAS05-530
NAS05-540 DKC515I
1
CL1-CHA: Operating
CL2-CHA: Operating
Postal service:
software developer.
Is the optional NO
program product on CL1-CHA
running?
YES
Phone, E-mail:
Request ordinary users to stop
the optional program product.
NAS Management Console: CL1-CHA:Operating

Stop the optional program (The optional features
product on CL1-CHA. are stopping.)
CL2-CHA:Operating

functionality to upgrade an
optional program product.
Perform an upgrade
operation again.
Has the upgrade

operation been completed
successfully? NO
Perform the same
operations for YES
CL2-CHA.
Have the tasks

NO
NAS Packages?
YES
End

NAS05-540
NAS05-550 DKC515I
5.3.2 Procedures for Upgrading the NAS OS and Related Program Products
You can upgrade, in the NAS Package, the NAS OS (NAS Data Control, NAS File Sharing) and the
related program product such as NAS Blade Manager.
Upgrading the NAS OS and related program products is categorized into four sections. Table 5.3-3
illustrates the related tasks for each upgrade method.
Table 5.3-3 Related tasks for upgrading the NAS OS and the related program
product
Upgrade method Description
[1] Upgrading the NAS OS (update Upgrade the NAS OS for changes such as additional NAS OS
version) functions.
[2] Upgrading the NAS OS (patch Upgrade the NAS OS for emergency measures such as security
version) updates.
[3] Upgrading the NAS Blade Upgrade the NAS Blade Manager.
Manager (update version)
[4] Upgrading the optional program Upgrade the optional program product.
product
Notes:
As a rule, you must upgrade the same program products and versions into NAS Packages (e.g.
CHA-1E and CHA-2Q or CHA-1F and CHA-2R for a flexible cabinet model, and CHA-1B and
CHA-2E for a rack-mount model) on the same cluster.
CAUTION
If you plan to expand or reduce a NAS Package, first close the NAS Setup on SVP
window, and then re-open it.
CAUTION
If you install NAS PP with a client PC drive set for the Install Device, keep the other PCs
from accessing SVP as client PCs during installation. If any other PC accesses SVP,
installation might fail and the system might not be able to start.
NAS05-550
NAS05-560 DKC515I
Before starting upgrade, determine appropriate upgrade type based on the flow chart shown below.
Once the upgrade type is determined, perform upgrade from the SVP and the Setup on SVP window
according to the upgrade procedures.
Upgrading the NAS software
Is NAS OS NO
upgraded?
YES
Is NAS NO
Blade Manager upgraded?
YES
[4] Upgrading the optional program
product [NAS05-760]
[3] Upgrading the NAS Blade

Manager [NAS05-720]
Is NAS OS NO
upgraded by a update
version?
YES
[1] Upgrading the NAS OS (update [2] Upgrading the NAS OS (patch
version) [NAS05-570] version)
[NAS05-670]
Figure 5.3-9 Installation Type Flowchart
NAS05-560
NAS05-570 DKC515I
[1] Upgrading the NAS OS (update version)---------------------------------------------- NAS05-570

[2] Upgrading the NAS OS (patch version)----------------------------------------------- NAS05-670
[3] Upgrading the NAS Blade Manager --------------------------------------------------- NAS05-720
[4] Upgrading the optional program product---------------------------------------------- NAS05-760
[1] Upgrading the NAS OS (update version)

To upgrade the NAS OS:
CAUTION
Before upgrading the NAS OS, switch the services running on the target NAS Package
(node) to be upgraded to run on an alternative node, and then request the system

(4) In the ‘NAS Setup on SVP (Main)’ window select the NAS Package to be upgraded, and
Note: You can install multiple NAS OS by doing following procedure. If you insert the
media into SVP, recommended number of simultaneous installation is 4 NAS OSs at the
maximum. If you insert the media into client PC, recommended number of it is 2 at the
maximum.
NAS05-570
NAS05-580 DKC515I
(5) The ‘NAS Setup on SVP(Program Install)’ window appears.
CAUTION
might cause a fatal error such as a system crash. You need to enter a password to select
these check boxes and continue the operation. Contact the Technical Support Division
(TSD) to confirm the validity of the operation and obtain the password.
Initialization [NAS03-530].
program product to be upgraded (NAS OS (NAS Data Control, NAS File Sharing)).
If you want to upgrade multiple program products, select the program product while
Note: In the window example below, the NAS OS stored in the NAS OS media is
upgraded.

products is displayed. You can
select only one program
Becomes active when an item

in the above list is selected.
Clicking this button uninstalls
the selected optional program
product.
The program products stored in

the supplied the NAS OS media
are displayed. You can select
multiple items at one time.
If you select an item from the

above list, this button becomes
active. Clicking this button
installs or upgrades the
(Display example)
NAS05-580
NAS05-590 DKC515I
(6) The message “Are you sure you want to update the NAS OS?” appears.
Click the Yes button in the message window.
(6-1)
When the node is stopped:
The NAS OS is installed.
Go to step (7).
(6-2)
When the node is active.
The message “This node is active...” appears.
Click the Cancel button in the message window to cancel the processing. Ask a system
administrator to switch the service to the alternative node and stop the node.
If you want to forcibly continue the processing, click the OK button.
Go to step (6-4).
NAS05-590
NAS05-600 DKC515I
(6-3)
When the system could not recognize the cluster status:
The message “Failed to get the cluster status...” appears.
Click the Cancel button in the message to stop the processing, and then go back to step
(5).
If the same message appears repeatedly, click the OK button to forcibly continue the
processing.
Go to step (6-4).
NAS05-600
NAS05-610 DKC515I
(6-4)
The message “The cluster system may be affected by this process...” appears.
Click the OK button in the message.
(6-5)
The NAS OS is installed.
NAS05-610
NAS05-620 DKC515I
(7) The ‘NAS Setup on SVP (Install Progress)’ window appears, and then the upgrade
products, the upgrade starts in the order from the top item.
(Display example)
When you upgrade the NAS OS on the other NAS Package, before the upgrade starts,
make sure whether failover was performed on the NAS Package for which the NAS OS is
to be installed. See the flowcharts in Chapter 5 and Chapter 7, and then go back to step
(2) to continue.
Note: It takes approximately 10 minutes to upgrade the NAS OS in one NAS Package, and
a maximum of 90 minutes to upgrade it in more than one NAS Package at the same time.
NAS05-620
NAS05-630 DKC515I
Rev.1 / May.2005, Jul.2006 Copyright © 2005, 2006, Hitachi, Ltd.
(8) When upgrade of the NAS OS finished abnormally:
(8-1)
(8-2)
10], and then take action.
(8-3)
(8-3-1)
NAS05-630
NAS05-640 DKC515I
(8-3-2)
(8-3-3)
NAS05-640
NAS05-650 DKC515I
(8-3-4)
(8-3-5)
If so, go to step (8-3-6).
drive of the SVP, reboot the SVP PC, and then install the NAS OS from step 1.
(TSD).
(8-3-6)
(internal LAN), if the user LAN (excluding a LAN for ASSIST or Hi-Track) is mistakenly
connected to the internal LAN, this error might occur. See the LOCATION Section
(8-3-7)
Re-execute upgrade.
Division (TSD).
NAS05-650
NAS05-660 DKC515I
(Install Progress)’ window become Completed, the upgrade has finished.
(Display example)
Make sure that the upgraded version displayed in Version corresponds with the version of
the NAS OS media (CD-ROM) and also the program product name in Name in Available
Program Product corresponds with the program product name of the NAS OS media
(CD-ROM), and then click the Close button.
The upgrade finishes.
Note: When NAS OS is upgraded, you select “NAS OS (NAS Data Control, NAS File
Install)’ window, however, after the upgrade finishes, upgraded version of two program
products (“NAS Data Control” and “NAS File Sharing”) are displayed in Available
Program Product.
(Display example)
NAS05-660
NAS05-670 DKC515I
[2] Upgrading the NAS OS (patch version)
Note: The NAS OS is upgraded to a patch version by installing the SUT (the file that
contains only differential data between the new version and the previous version for
updating). Read ECN that comes with the SUT carefully while upgrading.
To upgrade the NAS OS:
(1) Insert the SUT media (CD-ROM) into the CD drive of the SVP.
upgrade is ACTIVE, INACTIVE, or WARN (NAS Blade Manager is not installed).
NAS05-670
NAS05-680 DKC515I

SUT to be installed.
If you want to install multiple SUTs, select the SUT while holding down the Ctrl key
(Refer to ECN for the SUTs to be installed and the procedures for the upgrade).
Note: In the window example below, the NAS OS media is upgraded with the SUT stored
in the SUT.

products is displayed. You
can select only one program

product.
The SUTs stored in the SUT

m edia are displayed.

becomes active. Clicking
selected SUT.
(Display example)
CAUTION
When you upgrade the NAS OS (patch version), you cannot click both the NAS Cluster
NAS05-680
NAS05-690 DKC515I
progress of the selected program product for the SUT is displayed.
(Display example)
When you upgrade the NAS OS on the other NAS Package, upgrade the NAS OS on the
NAS Package of the same cluster. Before the upgrade starts, make sure whether failover
was performed on the NAS Package for which the NAS OS is to be installed. See the
flowcharts in Chapter 5 and Chapter 7, and then go back to step (2) to continue.
Note: It takes approximately 1 minute to upgrade the NAS OS (corrected patch version) in
one NAS Package, and several minutes to upgrade it in more than one NAS Package at the
same time.
NAS05-690
NAS05-700 DKC515I
(7) When upgrade of the NAS OS finished abnormally:
(7-1)
(7-2)
10], and then take action.
(8) When the status of the SUT displayed in the ‘NAS Setup on SVP (Install Progress)’
window becomes Completed, the upgrade has finished.
(Display example)
NAS05-700
NAS05-710 DKC515I

the SUT media (CD-ROM) and also the program product name in Name in Available
Program Product corresponds with the program product name of the SUT media (CD-
ROM), and then click the Close button.
(Display example)
NAS05-710
NAS05-720 DKC515I
[3] Upgrading the NAS Blade Manager
To upgrade the NAS Blade Manager:
upgrade is ACTIVE or INACTIVE.
NAS05-720
NAS05-730 DKC515I

Select the program product that you want to upgrade (“NAS Blade Manager”)) from a list
of program products displayed in the Program Product in Media field.


product.

the supplied the NAS OS media

(Display example)
CAUTION
When you upgrade the NAS Blade Manager, you cannot select both the NAS Cluster
NAS05-730
NAS05-740 DKC515I
products, the upgrade starts in descending order from the top item.
(Display example)
NAS Package of the same cluster. See the flowcharts in Chapter 5 and Chapter 7, and
then go back to step (2) to continue.
(7) When the NAS Blade Manager upgrade has ended abnormally:
(7-1)
(7-2)
NAS05-740
NAS05-750 DKC515I
(Display example)

the NAS OS media (CD-ROM) and also the program product name in Name in Available
Program Product corresponds with the program product name of the NAS OS media
(Display example)
NAS05-750
NAS05-760 DKC515I
[4] Upgrading the optional program product
To upgrade the optional program product:
(1) Insert the NAS PP media (CD-ROM) into the CD drive of the SVP.
upgrade is ACTIVE or INACTIVE.
NAS05-760
NAS05-770 DKC515I

program product to be upgraded.
If you want to upgrade multiple program products, select the program product while


product.

the supplied the NAS PP media

(Display example)
CAUTION
When you upgrade the optional program product, you cannot select both the NAS
Cluster Management LU and Error Information LU in the Initialize area.
NAS05-770
NAS05-780 DKC515I
products, the upgrade starts in descending order from the top item.
(Display example)
NAS Package of the same cluster. See the flowcharts in Chapter 5 and Chapter 7, and
then go back to step (2) to continue.
(7) When the optional program product upgrade has ended abnormally:
(7-1)
(7-2)
NAS05-780
NAS05-790 DKC515I
(Display example)

the NAS PP media (CD-ROM) and also the program product name in Name in Available
Program Product corresponds with the program product name of the NAS PP media
(Display example)
NAS05-790
NAS05-800 DKC515I
5.3.3 Going Back To an Earlier Software Version

Before updating, and when the settings are added, deleted, or changed by the NAS Blade Manager
GUI, you should make a backup of the NAS OS LU by using the NAS OS LU save/recovery
functionality of NAS Blade Manager. If the upgrade fails, use the following procedure to go back to
the previous version.
CAUTION
When you downgrade software, contact the Technical Support Division (TSD) and
perform operations according to its instructions.
The NAS Blade system does not provide the functionality to go back to an earlier update version.
To go back to a previous software version:
(1) To Go Back To an Earlier Version of the NAS OS

(a) When the NAS OS LU, NAS Cluster Management LU and user LU Have Been Backed Up
Restore NAS OS LU [NAS03-990] and NAS Cluster Management LU [NAS03-1040] by
using the NAS OS LU save/recovery functionality. Ask a system administrator to restore
user LU.
You can go back to an earlier version of NAS Blade Manager and an optional program
product by this procedure.
(b) When the NAS OS LU, NAS Cluster Management LU and user LU Have Not Been Backed
Up
Perform an expansion installation of the NAS OS [NAS03-400] to install the earlier
version to overwrite the current version [NAS05-130][NAS05-220], until you reach the
target version you want.
Upgrade the version of NAS Blade Manager and an optional program product to an earlier
version [NAS05-500][NAS05-520] at this time.
Note: You can install multiple NAS OS by doing following procedure. If you insert the
media into SVP, recommended number of simultaneous installation is 4 NAS OSs at the
maximum. If you insert the media into client PC, recommended number of it is 2 at the
maximum. If the same phenomenon occurs three times or more, contact the Technical
Support Division (TSD).
(2) To Go Back To an Earlier Version of NAS Blade Manager

Upgrade the version of NAS Blade Manager to an earlier version [NAS05-500].
To go back to an earlier version of NAS Blade Manager, you also need to go back to an earlier
version of the NAS OS. After going back to an earlier version of the NAS OS, as described in
(1), upgrade the target version of NAS Blade Manager.
(3) To Go Back To an Earlier Version of an Optional Program Product

Upgrade the version of an optional program product to an earlier version [NAS05-520].
To go back to an earlier version of an optional program product, you also need to go back to an
earlier version of the NAS OS. After going back to an earlier version of the NAS OS, as
described in (1), upgrade the target version of an optional program product.
NAS05-800
NAS06-10 DKC515I
6. NAS Configuration (Reconfiguration)

6.1 Overview
This chapter describes the procedures for reconfiguring a NAS Blade disk subsystem. Such
reconfiguration may become necessary due to increases in data volumes or changes in the type of
work. When reconfiguring a NAS Blade disk subsystem, maintenance personnel or system
administrators need to take into consideration such factors as the necessity of stopping the NAS
OS, the necessity of performing a backup, and the interrelationships among the LUs, device files,
and file systems.
NAS06-10
NAS06-20 DKC515I
6.2 Reconfiguring Hardware

In this section, the cluster is assumed to consist of CL1-CHA and CL2-CHA, and this
section shows operations of maintenance personnel and system administrators when
reconfiguring hardware.
Also, the cluster is assumed to consist of CL1-CHA2 and CL2-CHA2 when adding or
removing a NAS Package.
Make sure that CL2-CHA, CL1-CHA2 or CL2-CHA2 is properly referred to as the actual
location when reconfiguring hardware.

Model CHA location CL1-CHA (CHA2) CL2-CHA (CHA2)
Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
6.2.1 Types of Hardware Reconfiguration

The following table shows how hardware reconfiguration procedures are classified depending on
the type of the target hardware, the reason for reconfiguration, and the operations of the
maintenance personnel and system administrator.
Table 6.2-2 Types of Hardware Reconfiguration

# Major Minor Reason for Target Device Restart Operation See:
Classification Classification Reconfiguration NAS OS? status *1
1 RAID group Adding Data added due to SVP (Storage No Yes Figure 6.2-1
an increase in data Navigator) [NAS06-40]
capacity
2 Removing Data deleted SVP (Storage No No Figure 6.2-2
because related Navigator), [NAS06-60]
work became Setup on SVP,
unnecessary NAS Blade
Manager
3 RAID cache Adding Performance SVP No Yes –*2
memory enhancement due to
increase in loads of
related work
4 Removing Due to decrease in SVP No Yes –*2
loads of related
work
NAS06-20
NAS06-30 DKC515I

# Major Minor Reason for Target Device Restart Operation See:
Classification Classification Reconfiguration NAS OS? status *1
5 RAID cache Reconfiguring Performance SVP No Yes –*2
memory (DCR) enhancement
undertaken when
there are high-
access LUs
6 NAS Package Adding Related work SVP (Storage No Yes Figure 6.2-3
became necessary Navigator), [NAS06-90]
Setup on SVP,
NAS Blade
Manager
7 Removing Related work SVP (Storage No Yes Figure 6.2-4
became unnecessary Navigator), [NAS06-130]
Setup on SVP,
NAS Blade
Manager
8 LU Increasing Data capacity SVP (Storage No No Figure 6.2-5
capacity increased. Navigator), [NAS06-150]
(LUN Involves LU Setup on SVP,
Expansion) reconfiguration. NAS Blade
(Change of Manager
emulation type)
9 Decreasing Data capacity SVP (Storage No No Figure 6.2-6
capacity decreased. Navigator), [NAS06-180]
(Change of Involves LU Setup on SVP,
emulation type) reconfiguration. NAS Blade
(CVS) Manager
10 MP memory (PCR) Reconfiguring Performance Storage No Yes –*3
enhancement Navigator
Yes: Required. No: Not required.

*1: Yes: Ordinary users can continue their operations.
No: Some applications of ordinary users related to reconfiguration are stopped.
*2: For more information, see the REPLACE Section [REP01-10], SSD Optional Function
[SSDOPT02-10]
*3: For more information, see the Cache Residency Manager User’s Guide.
6.2.2 Flowcharts for Reconfiguring Hardware

The following table lists general procedures for reconfiguring hardware:
# General procedure for reconfiguration For details, see ...

(1) Adding a RAID group (user LU) Figure 6.2-1 [NAS06-40]
(2) Removing a RAID group (user LU) Figure 6.2-2 [NAS06-60]
(3) Adding or removing RAID cache memory or [REP01-10]
reconfiguring (DCR) [SSDOPT02-10]
Adding CM: from [INST03-09B-10]
Removing CM: from [INST04-03B-10]
(4) Adding a NAS Package Figure 6.2-3 [NAS06-90]
(5) Removing a NAS Package Figure 6.2-4 [NAS06-130]
(6) Increasing LU capacity (user LU) Figure 6.2-5 [NAS06-150]
(7) Decreasing LU capacity (user LU) Figure 6.2-6 [NAS06-180]
NAS06-30
NAS06-40 DKC515I
(1) Adding a RAID Group (User LU)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP
Command Device
Create LU User LU User LU
Command Device
and set User LU
path. Command Device
User LU
Addition
: Monitoring
Figure 6.2-1 Adding a RAID Group (User LU)(1/2)

1 Add a RAID group (PDEV).
2 Define the user LU. (Create the LU and set the path).
NAS06-40
NAS06-50 DKC515I
Adding a RAID group (user LU)

CL1-CHA and CL2-CHA
are operating.
NAS frame, SVP: Phone, E-mail:

Call maintenance personnel for PDEV added.
Add PDEV and create LU.
adding PDEV.
Notify ordinary users of addition
Add PDEV of PDEV.
See [INST03-10A-10].
SVP: NAS Management console:

Set paths. Use NAS Blade Manager to
create file systems.
Set the path
See [INST05-1360].
Phone, E-mail:
Notify system administrator of NAS Management console:
completion of LU creation and Use NAS Blade Manager to
path setup. create file shares.
Phone, E-mail:
Notify ordinary users of
completion of PDEV addition.
End
Figure 6.2-1 Adding a RAID Group (User LU)(2/2)
NAS06-50
NAS06-60 DKC515I
(2) Removing a RAID Group (User LU)
CL1-CHA CL2-CHA
Pentium Pentium
SVP Dump LU for CL1-CHA Dump LU for CL2-CHA NAS Cluster Management LU
Command Device
User LU User LU Command Device
User LU
Removal
: Monitoring
Figure 6.2-2 Removing a RAID Group (User LU)(1/2)

1 Delete all the file shares on the RAID Delete unnecessary setting information.
group to be removed.
2 Delete all the file systems on the RAID Delete unnecessary setting information.
group subject to be removed.
3 Stop the cluster on the NAS Package
subject to be removed.
4 From the LUNs set for the file systems to From these LDEV numbers, maintenance
be deleted, specify the LDEV numbers of personnel specify the RAID group (PDEV) to be
the RAID group to be removed. removed.
5 Stop the NAS OS.
6 Delete all the paths to and from the RAID Delete unnecessary setting information.
group to be removed.
7 Remove the RAID group (PDEVs).
NAS06-60
NAS06-70 DKC515I
Removing a RAID group (user LU)
Phone, E-mail: CL1-CHA and CL2-CHA

Notify ordinary users of removal of PDEV. are operating

Check the file systems in the RAID group
subject to deletion, and then cancel the
relevant file sharing.

Check the device files composing the file
systems checked in the above step, and
then delete the relevant file systems. CL1-CHA and CL2-CHA
are not operating
Stop the cluster of CL1-CHA and CL2-CHA.
Storage Navigator: For details, see the LUN

Specify the LDEV No. of the LDEVs Manager User's Guide.
composing the device files checked in
the above step from the LUN set to
the each relevant file system.
Setup on SVP:
Stop the NAS OSs on CL1-CHA
and CL2-CHA NAS Packages. Phone, E-mail:
Notify maintenance personnel of LDEV
Perform a stop of the NAS OS number and call for removing PDEV.
See 3.5.8 [1] [NAS03-780].
SVP:
Identify RAID group and PDEV
from LDEV number.
Identify RAID group and
PDEV from LDEV number
See [SVP02-770].
SVP:
Delete paths.
Delete paths
See [INST05-1430].
NAS frame, SVP:
PDEV removed.
Remove RAID group and PDEV.
Remove PDEV
See [INST04-01A-10]. Phone, E-mail:
Notify ordinary users of
Phone, E-mail: completion of PDEV removal.
Notify system administrator of
completion of PDEV removal.
End
Figure 6.2-2 Removing a RAID Group (User LU)(2/2)
NAS06-70
NAS06-80 DKC515I
(3) Adding or Removing RAID Cache Memory or Reconfiguring (DCR)
For details, refer to the REPLACE Section [REP01-10], SSD OPTIONAL FUNCTION
SECTION [SSDOPT02-10].
For details about adding cache memory, refer to the INSTALLATION Section (from [INST03-
09B-10]).
For details about removing cache memory, refer to the INSTALLATION Section (from
[INST04-03B-10]).
NAS06-80
NAS06-90 DKC515I
(4) Adding a NAS Package
Addition
NAS Package
NAS Package
Cluster 1
Cluster 2 CL2-CHA
Installation CL1-CHA2 CL2-CHA2 Pentium
Pentium
Optional Program Optional Program Pentium
Pentium
Product Pentium
Product
MP MP
NAS Blade Manager NAS Blade Manager MP MP
MP
NAS OS LU for CL1-CHA NAS OS LU for CL2-CHA Backup LU of NAS CM LU
Create NAS Cluster Management LU

LU
and Error Information LU
set NAS OS LU for CL1-CHA2 User LU Error Information LU
path. Command Device
Dump LU for CL1-CHA2 User LU
Command Device
User LU
Command Device
Supplied
Media
: Monitoring
Figure 6.2-3 Adding a NAS Package (1/4)

1 Add the NAS Package to the NAS Blade
system frame.
2 Create the NAS system LUs for the added
NAS Package, set the paths and define the
user LU.
3 Build the system. Carry out the series of tasks from reinstalling the
NAS OS to setting up the functionality related to
error monitoring.
NAS06-90
NAS06-100 DKC515I
Adding a NAS Package
NAS frame, SVP: Phone, E-mail: CL1-CHA and CL2-CHA

Install NAS Package for Call maintenance personnel for operating
CL1-CHA2 and CL2-CHA2 installing NAS Package and
notify ordinary users accordingly.
Increase NAS Package
See [INST03-07D-10].
SVP:
Create LU for CL1-CHA2 and
CL2-CHA2 and set path (system
LU construction/path setup, user
LU definition).
Set the path
See [INST05-1360].
SVP:
Set NAS time zone
Setting NAS time zone

See 9.4 [NAS09-330].
Setup on SVP:
Install NAS OS on CL1-CHA2 and
CL2-CHA2.
Install NAS OS
See 3.5.4 [NAS03-290].
Setup on SVP:
Install NAS Blade Manager on
CL1-CHA2 and CL2-CHA2.
Install NAS Blade Manager

See 3.5.4 [NAS03-290].
Setup on SVP:
Install optional program products
for NAS Blade Manager on
CL1-CHA2 and CL2-CHA2 (*1).
Install optional program

products for NAS Blade
Manager
See 3.5.4 [3] [NAS03-490].
[NAS06-110]
(*1) Required only when optional program products are used.
NAS06-100
NAS06-110 DKC515I
Setup on SVP:
Set CL1-CHA2 and CL2-CHA2license.
[Setting Up a License]
See 3.5.7 [NAS03-650].
Setup on SVP:
Set up the network configuration (the fixed
IP address, routing, NTP) for the control
port on CL1-CHA2 and CL2-CHA2.
[Setting up the network]
See 3.5.6 [NAS03-630]. Storage Navigator:
Set up CL1-CHA2 and CL2-CHA2
PCR functionality (see the Cache
Phone, E-mail: Residency Manager User's Guide).
completion of maintenance Account administrator
personnel's setup procedure.
Use NAS Blade Manager
functionality to set up CL1-CHA2
and CL2-CHA2 system

Use NAS Blade Manager functionality
to configure the CL1-CHA2 and
CL2-CHA2 cluster.

Start the cluster and the resource
groups of CL1-CHA2 and CL2-CHA2
using the cluster management
function of NAS Blade Manager.

to define configuration for CL1-CHA2
and CL2-CHA2 services.

to define the network configuration
(the fixed and service IP addresses,
routing) for the control and data ports
on CL1-CHA2 and CL2-CHA2.
[NAS06-120]
NAS06-110
NAS06-120 DKC515I

to set up the CL1-CHA2 and
CL2-CHA2 network (DNS, NIS).

to set up the CL1-CHA2 and
CL2-CHA2 users/groups.

to create the CL1-CHA2 and
CL2-CHA2 file systems.

to set up CL1-CHA2 and CL2-CHA2
file shares.

to specify error check settings for
Phone, E-mail:
Notify maintenance personnel and
ordinary users of completion of NAS
Package addition.
End
NAS06-120
NAS06-130 DKC515I
(5) Removing a NAS Package
Removal NAS Package

NAS Package
Cluster 1
Cluster 2
CL2-CHA
CL1-CHA2 CL2-CHA2 Pentium
Pentium
Pentium
Pentium Pentium
MP MP
MP MP
MP
MP MP MP MP
NAS Cluster Management
Error Information LU LU
NAS OS LU for CL1-CHA2 User LU Error Information LU
Delete Command Device
path. Dump LU for CL1-CHA2 User LU
Command Device
User LU User LU
Command Device
: Monitoring
Figure 6.2-4 Removing a NAS Package (1/2)

1 Stop operation of the NAS Package that is
to be removed.
2 Delete all file shares on the NAS Package Delete unnecessary setting information.
that is to be removed.
3 Delete all file systems on the NAS Delete unnecessary setting information.
Package that is to be removed.
4 Stop the cluster on the NAS Package that
is to be removed.
5 Stop the NAS OS on the NAS Package
that is to be removed.
6 Delete the NAS system LUs and user LUs Delete unnecessary setting information.
on the NAS Package that is to be
removed. (Delete their paths.)
7 Remove the NAS Package that is to be
removed.
NAS06-130
NAS06-140 DKC515I
Removing a NAS Package
Phone, E-mail: CL1-CHA and CL2-CHA:

Notify ordinary users of removal of operating.
NAS Package, and stop operation CL1-CHA2 and CL2-CHA2: not
of NAS Package to be removed. operating.

functionality to cancel CL1-CHA2 and
CL2-CHA2 file shares (NFS, CIFS).

functionality to delete CL1-CHA2
and CL2-CHA2 file systems.

Stop the cluster of CL1-CHA and CL1-CHA and CL2-CHA: not
CL2-CHA. operating
Setup on SVP:
Phone, E-mail:
Stop the NAS OSs on CL1-CHA2
and CL2-CHA2 NAS Packages.
perform a normal stop of the NAS
[Stop NAS OS] OS, and remove NAS Packages for
See 3.5.8 [1] [NAS03-780]. CL1-CHA2 and CL2-CHA2.
SVP:
Remove CL1-CHA2 and CL2-CHA2
LUs, and delete the path settings.
[Delete the path settings]
See [INST05-1430].
NAS frame, SVP: NAS Packages: removed
Remove NAS Packages for
[Remove NAS Package]
See [INST04-04D-10].
Notify system administrator of Notify ordinary users of completion
completion of maintenance work. of NAS Package removal.
End
Figure 6.2-4 Removing a NAS Package (2/2)
NAS06-140
NAS06-150 DKC515I
(6) Increasing LU Capacity (User LU)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

SVP Dump LU for CL1-CHA Dump LU for CL2-CHA Error Information LU
Command Device
Increase LU User LU
capacity, and
reset path.
User LU
Backup/Restoration
Backed
: Monitoring up Data
Figure 6.2-5 Increasing LU Capacity (User LU) (1/3)

1 Stop the operation of the user LU to which
capacity is to be added.
2 Back up the data on the user LU to which
capacity is to be added.
3 Delete the file shares on the user LU to
which capacity is to be added.
4 Delete the file systems on the user LU to
which capacity is to be added.
5 Increase the PDEVs in the NAS Blade Execute this step when the remaining capacity of
system frame. the existing PDEVs becomes insufficient.
6 Increase the LU capacity and reset the
paths.
7 Re-create the file systems.
8 Renew the file shares.
9 Restore the data in the user LU.
NAS06-150
NAS06-160 DKC515I
Increasing LU capacity (user LU)
Phone, E-mail: CL1-CHA and CL2-CHA

Notify ordinary users of LU are not operating
capacity increase and call for
stopping operation of target LU.

Use NAS Blade Manager Required
functionality to get user LU User LU backed up.
backup (on file basis).

functionality to cancel file shares.

functionality to remove file
systems.
[NAS06-170]
NAS06-160
NAS06-170 DKC515I
NAS frame, SVP: Phone, E-mail:

Add PDEV (*1). Notify maintenance personnel and
ordinary users of completion of file
Add PDEV system removal and backup, and
See [INST03-10A-10]. call maintenance personnel to
increase LU capacity.
SVP:
Increase LU capacity (change
LUN Expansion and emulation
type), and set path.
Increase LU capacity
See [SVP03-380].

Notify system administrator of Use NAS Blade Manager
completion of LU capacity functionality to create file systems.
increase and path setup.
Set the path

See [INST05-1360]. NAS Management Console:
functionality to reset file shares.
NAS Management Console: User LU restored.

functionality to restore user LU list
(in file units).
Phone, E-mail:
Notify ordinary users of completion
of LU capacity increase.
End
(*1) Required only when necessary.
NAS06-170
NAS06-180 DKC515I
(7) Decreasing LU Capacity (User LU)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

SVP Dump LU for CL1-CHA Dump LU for CL2-CHA Error Information LU
Command Device
Decrease LU User LU
capacity, and
reset path.
User LU
Backup/Restoration
Backed
: Monitoring up Data
Figure 6.2-6 Decreasing LU Capacity (User LU) (1/3)

1 Stop the operation of the user LU to be
removed.
2 Obtain the backup data of the user LU to be
removed.
3 From the LUNs, specify the LDEV From the LUNs, the maintenance personnel
numbers of the user LU to be removed. specify the LDEV numbers of the user LU to be
removed.
4 Delete, all at once, the file shares on the
user LU subject to be removed.
5 Delete, all at once, the file systems in the
user LU to be removed.
6 Remove the LU capacity and reset the path.
7 Re-create the file systems.
8 Reset the file shares.
9 Restore the data in the user LU.
NAS06-180
NAS06-190 DKC515I
Decreasing LU capacity (user LU)
Phone, E-mail: CL1-CHA and CL2-CHA are

Notify ordinary users of LU capacity not operating
decrease, and call to stop operation
of target LU.
NAS Management Console: Required.

to back up user LU (in file units). User LU backed up.
Storage Navigator:
Identify, from LUN, number of LDEV
on which data to be deleted exists.

functionality to cancel file shares.

functionality to remove file systems.
[NAS06-200]
NAS06-190
NAS06-200 DKC515I
Phone, E-mail:
Notify maintenance personnel and
ordinary users of completion of file
system removal and backup.
NAS frame, SVP:

Identify RAID group and PDEV Phone, E-mail:
from LDEV number. Notify maintenance personnel of LDEV
number and call for decreasing LU capacity.
Identify RAID group and
PDEV from LDEV number
See [SVP02-770].
SVP:
Delete paths.
Delete paths
See [INST05-1360].
SVP:
Decrease LU capacity (reset
LUN Expansion, change
emulation type, CVS), and set
th
Decrease LU capacity
See [SVP03-380].

Notify system administrator of Use NAS Blade Manager functionality
completion of LU capacity to recreate the file systems.
decrease and path setup.

to reset file shares.
NAS Management Console: User LU restored.

to restore user LUs (in file units).
Phone, E-mail:
Notify ordinary users of completion of
LU capacity decrease.
End
NAS06-200
NAS06-210 DKC515I
6.3 Reconfiguring Software

6.3.1 Types of Software Reconfiguration
The following table shows how software reconfiguration procedures are classified depending on the
type of the software, and the operations of the maintenance personnel and system administrator.
You can configure software by using the NAS Blade Manager GUI. You do not need to operate
the SVP or Storage Navigator, or restart the NAS OS. For details on using the NAS Blade Manager
GUI, see the NAS Blade Manager User’s Guide.
Table 6.3-1 Types of Software Reconfiguration

2
# Major Minor Classification Target Perform Restart See: *
Classification NAS the NAS
*1
Backup? OS?
1 File system Expanding file system NAS Blade Manager No No File System
capacity*3 Management
2 Deleting a file system*3 NAS Blade Manager No No
3 Network Fixed IP address Setup on SVP*4, No No System Settings
reconfiguration NAS Blade Manager
4 Service IP address NAS Blade Manager No No Cluster Management
5 Routing information Setup on SVP*4, No No System Settings
NAS Blade Manager
6 DNS NAS Blade Manager No No
7 NTP Setup on SVP (server No Yes
specification only),
NAS Blade Manager
8 NIS NAS Blade Manager No No
9 PDC NAS Blade Manager No No Service Management
10 Error checking (syslog) NAS Blade Manager No No System Settings
11 Error checking (SNMP) NAS Blade Manager No No
12 System administrator NAS Blade Manager No No Administrator Setup
13 Ordinary user NAS Blade Manager No No User Management
14 File sharing Setting up shares NAS Blade Manager No No File Sharing
(NFS, CIFS) Management
15 File sharing Canceling shares NAS Blade Manager No No
(NFS, CIFS)
Yes: Required. No: Not required.
*1: Backup in directory or file units is used.
*2: These correspond to chapters or subsections in the NAS Blade Manager User’s Guide.
*3: Involves no hardware reconfiguration operations such as adding or removing LUs.
*4: You can only change the configuration of the control port.
NAS06-210
NAS07-10 DKC515I
7. NAS Troubleshooting
7.1 Overview
This chapter describes how to detect and identify failures, and countermeasures to take when a
failure occurs.
Maintenance personnel should use information such as SIM logs, SSB logs, and ACC reports from
the SVP to detect triggers of failover and NAS OS failures due to hardware or software failures. See
the flowchart for software troubleshooting given in section 7.4 Identifying Troubleshooting
Procedures from Failure Phenomena [NAS07-210], and take the appropriate action.
System administrators should use the NAS Blade Manager GUI, SNMP, and information such as
logs to detect NAS functionality failures, and then report the failures to maintenance personnel.
Maintenance personnel should decide the appropriate course of action based on the information
from the system administrators and from the SVP, and should cooperate with the system
administrators to take the appropriate action.
Figure 7.1-1 gives an overview of detecting failures and obtaining error information.
NAS07-10
NAS07-20 DKC515I
Technical Support System

Division (TSD) administrators
Maintenance Maintenance NAS Management
Maintenance terminal *1 server Console
personnel
NAS OS SNMP error

-related dump LAN messages
Error Logs
CL2-CHA messages
CL1-CHA Failover via GUI
Core dump
Failback
SIM, ACC
error report
Pentium Pentium
Maintenance
personnel Backup LU of NAS CM LU
SVP
SIM, ACC NAS Cluster Management LU
error
report NAS Cluster Management LU
SIM logs Dump LU for CL1-CHA Dump LU for CL2-CHA
SSB logs Error Information LU
Core dump Error Information LU

Logs of NAS
OS and PP User LU Command Device
System
administrator User LU Command Device
Event Crash Hibernation
trace dump dump User LU Command Device
Storage
Navigator PC Auto dump Nas dump
(Legend) : Monitoring each other : Failed part
Figure 7.1-1 Detecting Failures and Obtaining Error Information
NAS07-20
NAS07-30 DKC515I
7.2 Detecting and Identifying Failures

The following table shows the major types of failures that might occur.
Table 7.2-1 Types of Failures

Type of Failed part Description
failures
Hardware NAS Package Failures in processors and microprograms in
the NAS Package
RAID RAID disk failures
Other hardware Disk subsystem hardware failures: for

example, in cache memory, power supply
equipment, or fans.
Software NAS OS (kernel) NAS OS panic/hangup (fatal), slowdown, etc.
Some NAS OS applications (part of the Abnormal termination of applications
NAS OS applications: for example, NFS
and CIFS)
NAS Blade Manager Failures related to the management
functionality of NAS Blade Manager
Optional program products Failures related to optional program products
such as NAS Backup Restore
Hardware failures, NAS OS kernel failures, failover failures, triggers of failover, failed part
locations that are unable to use at service startup, are reported to the SVP. Other software failures
are monitored by NAS Blade Manager in the NAS Package and reported to the NAS management
console.
Maintenance personnel and system administrators should detect failures by examining the failure
information received at the SVP, NAS Management console, and maintenance server. The
following table shows this information.
Table 7.2-2 Failure Information Received

Staff Receiving device Failure information received
Maintenance personnel SVP SIM, SIM log, and ACC
System administrators NAS management console Messages on the NAS Blade Manager GUI,
Management log
Maintenance server SNMP report and MIB information
Also, maintenance personnel and system administrators should identify the failure by the above
information, take the emergency measures described in section 7.4 Identifying Troubleshooting
Procedures from Failure Phenomena [NAS07-210], and at the same time, obtain details about the
failure.
NAS07-30
NAS07-40 DKC515I
7.2.1 Detecting Failures

(1) Failure Detection By Maintenance Personnel:
If a failure message appears on the SVP, find out the nature and location of the failure by
examining the SIM, SIM log, and ACC.
SIM includes failure information that is unique to the NAS functionality.

For details, see SIM-RC Section [SIM-RC02-20].
Table 7.2-3 SIM Information Unique to the NAS Functionality

# SIM code/ACC Failure Occurrence conditions Recovery method
1 AC82xx (moderate) NAS OS processor - Pentium WCHK1 - Replace the NAS Package.
ACC=102Exxxx failure - BIOS failure
(processor) NAS OS bus failure - PCI bus failure (between
Pentium and MP)
- Pentium memory / hub
interface B / P64H2 failure
- ECC uncorrectable error
- Pentium cache ECC
correctable / uncorrectable /
parity error
2 AC83xx (moderate) NAS OS processor - Pentium heat failure - Replace the fan.
ACC=102Exxxx environment - Replace the NAS Package.
(processor) abnormality failure
3 AC84x0 (moderate) NAS OS failure - NAS OS panic - Upgrade the NAS OS.
ACC=102Exxxx - NAS OS boot timeout - Replace the NAS Package.
(processor) - NAS OS shutdown timeout
- Timeout during a health check
on the PCI bus between Pentium
and MP
4 AC84x2 (moderate) Failover notification - Failover startup - Replace the NAS Package.
ACC=102Exxxx - Upgrade the NAS OS.
(processor) - Check the network cables.
5 AC84x4 (moderate) NAS OS - NAS cluster management LU - Replace the NAS cluster
ACC=102Exxxx startup/shutdown failure: management LU.
(processor) failure • When failover is started - Upgrade the NAS OS.
• When NAS OS is started
• When NAS OS is shut down
6 AC84x5 (moderate) NAS OS - Failure in preliminary - Upgrade the NAS OS.
ACC=102Exxxx startup/shutdown processing for NFS share (OS
(processor) failure failure, application failure):
• When failover is started
• When NAS OS is started
7 AC84x6 (moderate) NAS OS - Failure in all the file systems: - Replace the NAS Package.
ACC=102Exxxx startup/shutdown • When failover is started - Upgrade the NAS OS.
(processor) failure • When NAS OS is started - Replace the NAS user LU.
- Failure in a file system:
NAS07-40
NAS07-41 DKC515I
Rev.2 / Jun.2005, Jul.2005 Copyright © 2005, Hitachi, Ltd.
(Continued from the previous page)

8 AC84x7 (moderate) NAS OS - Failure in all the NFS shares: - Replace the NAS Package.
(processor) failure • When NAS OS is started - Replace the NAS user LU.
- Failure in an NFS share
9 AC84x8 (moderate) NAS OS - Service IP Failure: - Check the network cable.
ACC=102Exxxx startup/shutdown • When failover is started - Replace the NAS Package.
(processor) failure • When NAS OS is started - Upgrade the NAS OS.
10 AC84x9 (moderate) NAS OS - CIFS Failure: - Replace the NAS Package.
(processor) failure • When NAS OS is started - Replace the NAS cluster
• When NAS OS is shut down management LU.
11 AC84xB (moderate) NAS OS - Failure in common or other parts: - Upgrade the NAS OS.
ACC=102Exxxx startup/shutdown • When failover is started - Replace the NAS system LU.
(processor) failure • When NAS OS is started
12 AC84xC (moderate) Network failure - Link down at GbENIC for more - Check the network cables.
ACC=102Exxxx than 60 seconds, failure in entire - Replace the NAS Package.
(processor) trunking: - Upgrade the NAS OS.
• During normal operation
13 AC84xE (moderate) Failover failure - Failover failed - Replace the NAS Package.
ACC=102Exxxx - Upgrade the NAS OS.
14 AC84xF (moderate) Failover - Failover succeeded - Replace the NAS Package.
ACC=102Exxxx notification - Upgrade the NAS OS.
15 AC84x2 (moderate) Failover failure - Failover startup/stop - Replace the NAS Package.
ACC=102Exxxx - Failed part due to failover startup - Upgrade NAS OS.
(processor) - Failed part due to service startup - Check the fiber optic cables
(LAN cables).
16 AC85xx (moderate) NAS OS bus - Pentium memory / hub interface B - Replace the NAS Package.
ACC=102Exxxx failure / P64H2 failure
(processor) - ECC correctable error
17 AC86xx (moderate) Network port - Network failure - Check the fiber optic cables
ACC=102Exxxx failure (LAN cables).
(processor) - Replace the NAS package.
18 AC88x1 Failure in part of - Network port link down detected - Check the fiber optic cables
ACC=102Exxxx trunking in a trunking (LAN cables).
(processor)
19 AC89x1 Recovery from - Network port link up detected in a -
ACC=102Exxxx failure in part of trunking
(processor) trunking
20 AC8Ux2 NAS-related file - Failure in NAS OS - Reboot the NAS OS.
ACC=102Exxxx system failure - Failure in the file system to which - Reinstall the NAS OS.
(processor) the service is provided (*1) - Restore the target volume
from the backup data.
NAS07-41
NAS07-42 DKC515I
Rev.0 / Jul.2005 Copyright © 2005, Hitachi, Ltd.
(Continued from the previous page)

21 AC8Ux3 NAS OS - Abnormal ending of NAS OS - Reboot the NAS OS.
ACC=102Exxxx application (NFS, applications - Upgrade the NAS OS.
(processor) CISF, etc) failure
22 AC8Ux4 NAS Blade - Unable management operation due - Reboot the NAS OS.
ACC=102Exxxx Manager failure to NAS Blade Manager failure - Reinstall the NAS OS.
(processor)
23 AC8Uxa NAS OS failure - Failure detected during NAS OS - Reboot the NAS OS.
ACC=102Exxxx during startup or startup or stop - Backup the NAS OS LU.
(processor) stop
24 AC8Uxf I/O failure detected - Failure in which a recovery did - Replace the NAS Package.
ACC=102Exxxx by a NAS OS not occur within the specified retry
(processor) count in the event of a disk I/O
timeout.
*1: This SIM may be reported if a subsystem shutdown process has been executed because of
a PS/OFF or power failure during TC/UR operation.
In these cases NAS OS may detect I/O error since microprocessors on CHT utilized for
TC/UR are shutdown earlier than those of CHN.
Even NAS OS reports this SIM, it will not be affected and be shutdown normally.
There is no problem in these cases.
NAS07-42
NAS07-50 DKC515I
Rev.2 / Jun.2005, Jul.2005 Copyright © 2005, Hitachi, Ltd.
Note: xxxx displayed for ACC indicates the failed part.

U represents the fourth byte of the SIM, numbered from 7 to 9 according to the level of
importance.
7: serious, 8: moderate, 9: service.
x represents the fifth byte of the SIM, numbered from 0 to 3 and 8 to B for a flexible
cabinet model, and numbered 5 or D for a rack-mount model. It indicates the location of
a failed NAS Package.
Table 7.2-4 indicates mapping of x values in relation to NAS Package locations.
Table 7.2-4 Mapping of x Values in Relation to NAS Package Locations

Model Location of NAS x (Fifth byte of SIM)
Package
Flexible cabinet model 1E 0
1F 1
1G 2
1H 3
2Q 8
2R 9
2T A
2U B
Rack-mount model 1B 5
2E D
For other SIM information about the RAID device and for details about how to read the SIM,
SIM logs, and ACC, see the SIM-RC Section [SIM-RC01-10], ACC (ACTION CODE) Section
[ACC01-10], and TROUBLESHOOTING Section [TRBL01-10].
(2) Failure Detection By System Administrators:

Find out the nature and location of a failure by examining both the list of NAS Blade Manager
GUI messages and the management logs.
Find out the nature and location of a failure by examining the failure information (MIB
information) provided to the maintenance server.
NAS07-50
NAS07-60 DKC515I
7.2.2 Identifying Failures and Taking Countermeasures

Maintenance personnel should work with the system administrators to identify the failure, select an
appropriate countermeasure, and carry out the countermeasure. This countermeasure is intended to
keep the customer business running as long as possible in the face of a failure. It is also intended to
obtain detailed information while exerting a minimum influence on the customer business.
To identify the failure and carry out the countermeasure, maintenance personnel should follow
these steps:
1. If the failures or failed parts detected by SIMs, SIM logs, and ACCs are related to the NAS
Blade system, see Figure 7.4-1 Flowcharts for Troubleshooting Related to Failure Phenomena
to decide the corresponding countermeasures.
2. By cooperating with the system administrators, the maintenance personnel should follow the
troubleshooting procedures of the flowchart decided in step 1, obtain necessary logs and dumps
about failure information, take an emergency measure, and then report to the system
administrators.
3. The maintenance personnel will receive appropriate countermeasures investigated by the
failure information obtained in step 2. When the failed parts become replaceable, or the
software becomes able to be upgraded, by the emergency measure, the maintenance personnel
should replace the failed parts by following the replacement or upgrade procedures and by
cooperating the system administrators.
Depending on the error information obtained from NAS Blade Manager and SNMP, the system
administrator checks the nature and location of the failure, and, working with maintenance
personnel, obtains error information such as logs and dumps, takes remedial actions, and performs
software upgrade operations.
NAS07-60
NAS07-70 DKC515I
7.2.3 Obtaining Detailed Information about a Failure

To correctly determine the cause and location of a failure, obtain detailed information.
(1) Detailed Information for Maintenance Personnel:

Maintenance personnel should obtain the following information.
Table 7.2-5 Failure Information Obtained by Maintenance Personnel

# Detailed Content Output How to obtain
information source
1 Auto Dump Information on disk subsystem SVP In the ‘SVP’ window, click
This is part of the information obtained in the Auto Dump button.
Table 2.5-1 Key Operations by Maintenance [SVP02-540].
Personnel and System Administrators (#23,
#25, #26 and #27) [NAS02-90]. Clicking the Auto Dump
The number of generations of NAS-related button collects logs from all
logs to be collected depends on the dump NAS packages.
type (Manual Dump or Auto Dump), or the To collect them from a
Auto Dump type (Rapid, Normal, or Detail). specific NAS package, click
- For Manual Dump: 3 generations the Dump button in the SVP
- For Auto Dump (Rapid): Not to be collected window and download them
- For Auto Dump (Normal): 1 generation by specifying the adapter of
- For Auto Dump (Detail): 3 generations the CHN, then acquire FD
Copy [SVP02-540].
2 Nas Dump Information on NAS Packages SVP In the ‘Setup on SVP’
This is part of the information obtained in NAS window, click the Download
Table 2.5-1 Key Operations by Maintenance Blade Dump button.
Personnel and System Administrators (#26 Manager See 3.5.15 [NAS03-1080]
and #27) [NAS02-90]. The level of GUI
information ranges from 1 to 4. You can For details on using the NAS
obtain Level 1 and Level 2 information using Blade Manager GUI, see the
SVP. Level 3 includes data being accessed NAS Blade Manager User’s
via NFS and CIFS (Windows client). Level 4 Guide.
is about the memory area available for NAS
OS at the time of dump acquisition. Since
both Level 3 and 4 include user data, they are
obtained by system administrators using NAS
Blade Manager GUI.
Only one generation of NAS-related logs is
acquired.
Note: Nas Dump can be collected only when both NAS OS LU and dump LU are in normal
state (If PDEVs used by those LUs are blocked, Nas Dump cannot be collected).
Note: Nas Dump file is named in the following format:

dump_<CHA-location-name>_<dump-acquisition-date>.lv<level>.gz.<split-identifier>
<CHA-location-name> is a 6-byte string in the format of CHA-??.
<dump-acquisition-date> is a 14-byte string in the format of YYYYMMDDhhmmss.
<level> is a one-byte string of either 1, 2, 3, or 4.
<split-identifier> is a letter used for managing file split.
NAS07-70
NAS07-80 DKC515I
Figure 7.2-1 shows the flowchart for obtaining detailed information on failures.
Flowchart of procedures for obtaining failure information

Start
Is the failed NAS NO Start the failed NAS Package.

Package running? See 3.5.8 [2] [NAS03-820].
In the 'NAS Setup on SVP

YES (Main)' window, make sure that
the NAS Package status is
ACTIVE, INACITVE, or WARN.
For details, see [NAS03-260].
In the 'NAS Setup on SVP (Main)' YES Is the failed NAS

window, select the failed NAS
Package running?
Package, and then click Download
Dump. See 3.5.15 [NAS03-1080].
NO
Do dump NO
files exist? (Is the 'NAS Setup on
SVP (Main)' window
displayed?)
YES
Install USB memory on SVP.

[NAS03-1080]
In the 'NAS Setup on SVP (Download

Dump)' window, make sure that
Download Status shows Normal, and
Last Save Date shows the desired
date, and then collect the dump files.
See 3.5.15 [NAS03-1080] Obtain auto dump. [SVP02-540]
Remove USB memory from SVP.

[NAS03-1270]
Send auto dump to developers.
Obtain auto dump. [SVP02-540]
Send both auto dump and NAS dump

to developers.
Figure 7.2-1 Flowchart of Procedures for Obtaining Failure Information
If the developer clears up the cause of a failure by analyzing the detailed information, the failure
recovery method can be determined. Failure recovery usually involves hardware replacement and
software upgrade.
NAS07-80
NAS07-90 DKC515I
(2) Detailed Information for System Administrators:

System administrators should obtain operation information and failure information (log files and
core files) from the NAS Blade Manager GUI window. They should send the error messages, log
files, and core files to maintenance personnel and ask the personnel to determine the cause of the
failure.
NAS07-90
NAS07-100 DKC515I
7.2.4 Preparing for Failure Recovery Operations (System LU Backup)

In preparation for failing to access the system LU (NAS OS LU and NAS Cluster Management LU)
due to a disk failure, or upgrade the NAS Package program, ask the system administrator to back up
the system LU (NAS OS LU and NAS Cluster Management LU) when the settings are added,
deleted, or changed by the NAS Blade Manager GUI.
CAUTION
Recovery might not be correct if the state of the NAS cluster management LU at the time
of the NAS OS LU recovery differs from the state at the time of the backup. Make sure
that the following condition is met when you perform a NAS OS LU recovery:
• Software has not been reconfigured (for example, file systems have not been created or
removed, and NFS or CIFS shares have not been created, removed or changed) since
the last NAS OS LU backup.
NAS07-100
NAS07-110 DKC515I
7.3 Lists of Failures
In this section, the cluster is assumed to consist of CL1-CHA and CL2-CHA, and Table
7.3-2 and Table 7.3-3 list items related to NAS functionality failures by hardware and by
software respectively. The listed items also include necessity of failover, destination of
failure report, and major dumps obtained at the time of failures.

Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
7.3.1 Hardware Failures

Table 7.3-2lists NAS functionality hardware failures.
Depending on the failure item, see the subsections for troubleshooting that describe
countermeasures (7.4 Identifying Troubleshooting Procedures from Failure Phenomena [NAS07-
210]). For the upgrade operations, see 7.7 NAS Hardware Replacement When a Failure Occurs
[NAS07-1010].
In this table, information about each failure specifies:

whether failover occurs,
whether the failure report is from the SVP and/or from NAS Blade Manager,
whether dumps can be obtained, and
whether the business tasks continue or are partly disabled.
NAS07-110
NAS07-120 DKC515I
Table 7.3-2 Hardware Failures

# Phenom- Failure Failure report Failure information NAS status Trouble- For details
enon shooting on replace-
procedure ment, see ...
Report Report Core Crash Hiber- Fail- Opera
from from dump dump nation over tion
SVP NAS dump status
*1
Blade *16
Manag-
*10
er
1 NAS OS Pentium internal error Yes No No No No Yes Yes Figure 7.5-1 Figure 7.7-1
processor Machine check exception [NAS07-360] [NAS07-1050]
2 failure Failure in PCI bus Yes No No No No Yes Yes Figure 7.5-1 Figure 7.7-1
(MCH, ICH3) [NAS07-360] [NAS07-1050]
3 Failure in PCI bus Yes No No No No Yes Yes Figure 7.5-1 Figure 7.7-1
(between Pentium and [NAS07-360] [NAS07-1050]
MP)
4 Failure in PCI bus Yes No No No No Yes Yes Figure 7.5-1 Figure 7.7-1
(between Pentium and [NAS07-360] [NAS07-1050]
network board)
5 Failure at startup of BIOS Yes No No No No Yes Yes Figure 7.5-1
(FWH failure) *12 [NAS07-360] [MICRO-FC01-
10]
6 NAS OS Temperature rise in Yes Yes No No *15 Yes Yes Figure 7.5-2 Figure 7.7-1
Yes
processor Pentium *16 [NAS07-380] [NAS07-1050]
environme
nt failure
7 NAS OS Internal error hangup in Yes No No No *16 Yes Yes Figure 7.6-2 Figure 7.8-1
Yes
failure Pentium (MP health [NAS07-650] [NAS07-1400]
check expired) Figure 7.8-2
[NAS07-1440]
Figure 7.8-3*3
[NAS07-1500]
8 Internal error hangup in Yes No No No *16 Yes Yes Figure 7.6-2 Figure 7.8-1
Yes
Pentium (heartbeat [NAS07-650] [NAS07-1400]
disconnected between Figure 7.8-2
Pentiums) [NAS07-1440]
Figure 7.8-3*3
[NAS07-1500]
9 NAS OS Correctable memory/hub No Yes No No No No Yes No action No action
memory interface required *2
required
failure and B/P64H2/Pentium cache
NAS OS ECC error (1st, 2nd, and
bus failure 3rd time)
10 Correctable memory/hub Yes *11 No No No Yes Yes Figure 7.5-2 Figure 7.7-1
Yes
interface [NAS07-380] [NAS07-1050]
B/P64H2/Pentium cache
ECC error (4th time)
11 Pentium cache parity Yes *11 No No No Yes Yes Figure 7.5-2 Figure 7.7-15
Yes
error [NAS07-380] [NAS07-1361]
12 Uncorrectable memory Yes No No No No Yes Yes Figure 7.5-2 Figure 7.7-1
/hub interface [NAS07-380] [NAS07-1050]
B/P64H2/Pentium cache
ECC error
13 Network Internal error in network *17 *9*17 No No No Yes Yes Figure 7.5-2 Figure 7.7-1
Yes Yes
port board of data LAN [NAS07-380] [NAS07-1050]
failure
(inaccessi-
ble)
NAS07-120
NAS07-130 DKC515I

Report Report Core Crash Hiber- Fail- Opera-
from from NAS dump dump nation over tion
SVP Blade dump status
*1
Manag-
*10
er
13A Network Internal error in a *17 *9*17 No No No No Yes Figure 7.5-15 Figure 7.7-1
Yes Yes
port failure data LAN network [NAS07-619] [NAS07-1050]
(inaccessi- board (partial
ble) failure, able to
continue
*19
operation)
13B Link down of data *17 *9*17 No No No Yes Yes Figure 7.5-14 Figure 7.7-12
Yes Yes
LAN fiber optic [NAS07-615] [NAS07-1340]
cable (LAN
*18
cable) , switch
failure, or failure in
entire trunking
14 Link down of Yes No No No No No Yes -- Figure 7.7-13
control LAN fiber [NAS07-1360A]
optic cable (LAN
cable) or switch
failure
14A Failure in part of Yes *9 *17 No No No No Yes -- Figure 7.7-14
Yes
trunking [NAS07-1360C]
15 NAS OS Timeout of disk I/O No Yes No No No No Yes Figure 7.5-12 Figure 7.7-1*2
slowdown (response from [NAS07-560] [NAS07-1050]
occurred. target MP, retry
successful)
16 RAID internal error Yes No No No No No Yes Figure 7.5-12 Figure 7.7-1*2
(except MP) [NAS07-560] [NAS07-1050]
(recoverable)
17 One MP is MP failure (only 1 Yes Yes No No No No Yes Figure 7.5-12 Figure 7.7-1*2
blocked. unit down) detected [NAS07-560] [NAS07-1050]
NAS OS by MP monitoring
18 slowdown Timeout of disk I/O Yes Yes No No No No Yes Figure 7.5-12 Figure 7.7-1*3
occurred. (no response from [NAS07-560] [NAS07-1050]
target MP, other
MP unblocked)
19 Failover MP failure (2 units Yes No No No *13 Yes Yes Figure 7.5-1 Figure 7.7-1
No
occurred down at the same Other [NAS07-360] [NAS07-1050]
due to MP time) NAS
failure. Pack-
age
20 Timeout of disk I/O No Yes No No *13 Yes Yes Figure 7.6-2 Figure 7.7-1
No
(no response from [NAS07-650] [NAS07-1050]
target MP, other
MP blocked)
21 RAID internal Yes No No No *13 Yes Yes Figure 7.5-1 Figure 7.7-1
No
(MP) error [NAS07-360] [NAS07-1050]
(unrecoverable)
22 I/O error Timeout error of Yes Yes No No *4 No  *5 Figure 7.6-3 Figure 7.8-1
Yes
occurred in disk I/O in a user [NAS07-680] [NAS07-1400]
a user LU. LU (response from Figure 7.8-2
target MP, retry [NAS07-1440]
unsuccessful) Figure 7.8-3*3
[NAS07-1500]
NAS07-130
NAS07-140 DKC515I

Report Report Core Crash Hiber- Fail- Opera
from from dump dump nation over tion
SVP NAS dump status
*1
Blade
Manager
*10
23 I/O error RAID failure Yes Yes No No No No No Figure 7.5-3 Figure 7.7-3
occurred in (2 PDEVs: [NAS07-400] [NAS07-1100]
user LU. User LUs) *20
24 External device Yes Yes No No No No No Figure 7.5-4 Figure 7.7-4
failure [NAS07-411] [NAS07-1131]
25 I/O error RAID failure Yes No No No No No  *7 Figure 7.5-7 Figure 7.7-7
occurred in an (2 PDEVs: NAS [NAS07-460] [NAS07-1200]
LU other than cluster management
a NAS OS LUs) *20
26 LU. RAID failure Yes Yes No No No No Yes Figure 7.5-8 Figure 7.7-8
(2 PDEVs: Dump [NAS07-480] [NAS07-1220]
LUs) *20
27 RAID failure Yes Yes No No No No Yes Figure 7.5-9 Figure 7.7-9
(2 PDEVs: error [NAS07-500] [NAS07-1270]
information LUs)
*20
28 RAID failure Yes Yes No No No No *8 Figure 7.5-10 Figure 7.7-10
Yes
(2 PDEVs: [NAS07-520] [NAS07-1290]
command devices)
*20
29 RAID failure Yes Yes No No No No Yes Figure 7.5-11 Figure 7.7-11
(2 PDEVs: Backup [NAS07-540] [NAS07-1310]
LUs of NAS CM
LUs) *20
29 Timeout error of Yes Yes No No No No Yes Figure 7.5-16 Figure 7.8-1
A disk I/O in an LU [NAS07-619B] [NAS07-1400]
other than a NAS Figure 7.8-2
OS LU (response [NAS07-1440]
from target MP, Figure 7.8-3*3
retry unsuccessful) [NAS07-1500]
30 I/O error RAID failure Yes Yes No No No Yes  *6 Figure 7.5-5 Figure 7.7-5
occurred in a (2 PDEVs: NAS [NAS07-420] [NAS07-1140]
NAS OS. OS LUs in the
cluster belong to
different RAID
groups.) *20
31 RAID failure Yes No No No No No No Figure 7.5-6 Figure 7.7-6
(2 PDEVs: NAS [NAS07-440] [NAS07-1180]
OS LUs in the
cluster belong to
the same RAID
group.) *20
32 Timeout error of Yes No No No No Yes Yes Figure 7.6-2 Figure 7.8-1
disk I/O in NAS OS [NAS07-650] [NAS07-1400]
LU (response from Figure 7.8-2
target MP, retry [NAS07-1440]
unsuccessful) Figure 7.8-3*3
[NAS07-1500]
14
33 Network failure No No No No No No No * Figure 7.5-13 --
(Failed to set [NAS07-580]
network settings)
NAS07-140
NAS07-150 DKC515I
*1: Yes: Business tasks continue.

However, if the application server is connected with Windows client (CIFS share) when a
failover occurs, the CIFS share is released. Therefore, you must reconnect the server with CIFS
share.
No: Business tasks partially stop.
*2: To cope with the failure, only alarm notification is carried out while business tasks continue.
Other countermeasures should be taken immediately.
*3: Possible abnormalities include NAS OS driver failure, MP microprogram failure, and
performance problems (with an application).
If an MP microprogram failure is detected, see the MICRO-FC Section [MICRO-FC01-10].
If a performance problem is detected, determine the countermeasure for the application from
the obtained performance information.
*4: A hibernation dump should be obtained manually as failure information.
*5: There is no response until a hibernation dump is manually obtained.
*6: Operation status depends on the location of user LUs and NAS OS LUs in the RAID groups.
*7: NAS Blade Manager is not operational (depending on the NAS cluster management LU status).
*8: Backup Restore operations have stopped.
*9: If the NIC of the management LAN has failed, no report can be sent to the NAS Blade
Manager.
*10: If the system is heavily loaded, NAS Blade Manager performance might become slow, and a
report might be delayed. Also, if the system goes down, it is possible that no report will be
sent.
*11: If a system goes down repeatedly because of failures, it is possible that no report will be sent to
NAS Blade Manager for the fourth time.
*12: When the BIOS startup program starts, failover will not occur if the NAS Package of the same
cluster is not operating.
*13: A hibernation dump might be produced, depending on the error.
*14: Business tasks that are not related to the failed network can continue.
*15: A hibernation dump will be collected until the Pentium stops automatically due to a
temperature rise.
*16: A hibernation dump will not be collected when NAS OS LU failure or dump LU failure
occurred.
*17: The failover function reports the failure as failed part to the SVP or NAS Blade Manager when
a failure occurs in the resources managed by the failover function, such as LVM, file systems,
and NFS public directories, at the startup of such services. The failover function reports the
failed part (location) where services cannot be provided due to a hardware or software failure,
to the system administrators via the NAS Blade Manager GUI, and to the maintenance
personnel via the SVP. The failover function also reports the start and completion of failover to
the maintenance personnel and system administrators via the SVP and NAS Blade Manager
GUI respectively. Table 7.3-4 shows the types of failures reported by the failover function.
*18: This includes the cable shared by the control LAN and data LAN.
*19: If link degeneration and link alternation are performed after trunking is set for the port that is
related to the failed network board, business tasks continue without a failover.
*20: These failures are regarded as failures in 3 PDEVs if RAID 6 (6D + 1P) is implemented.
NAS07-150
NAS07-160 DKC515I
7.3.2 Software Failures

Table 7.3-3 lists NAS functionality software failures.
Depending on the failure item, see the subsections for troubleshooting that describe
countermeasures (7.4 Identifying Troubleshooting Procedures from Failure Phenomena [NAS07-
210]). For the replacement and upgrade operations, see 7.7 NAS Hardware Replacement When a
Failure Occurs [NAS07-1010].
In this table, information about each failure specifies:

whether system administrators can perform operations from the NAS management console,
whether failover occurs,
whether failure reports are from the SVP or from the NAS Blade Manager,
whether dumps can be obtained, and
whether business tasks are continued or partly disabled.
NAS07-160
NAS07-170 DKC515I
Table 7.3-3 Software Failures

# Failure Failure report Failure information NAS status Trouble- For upgrade,
shooting see ...
Report Report Core Crash Hiber- Opera- Fail- Opera procedure
from from dump dump nation tions over tion
SVP NAS dump from the status
*2
Blade NAS
Manager manage-
ment
*1
console
*3
34 NAS OS panic Yes No No Yes No Yes Yes Yes Figure 7.6-1 Figure 7.8-1
[NAS07-630] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
*3
35 NAS OS hangup Yes No No No Yes Yes Yes Yes Figure 7.6-2 Figure 7.8-1
[NAS07-650] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
*4  *5
36 NAS OS No No No No No Yes Yes Figure 7.6-3 Figure 7.8-1
slowdown [NAS07-680] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
*3 8 8
37 Application No * Yes* Yes No No Yes Yes Yes Figure 7.6-4 Figure 7.8-1
failure (failover [NAS07-710] [NAS07-1400]
provided) Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
38 Application No Yes Yes No No Yes No Yes Figure 7.6-5 Figure 7.8-1
not provided, Figure 7.8-2
other than web [NAS07-1440]
server) Figure 7.8-3
[NAS07-1500]
Figure 7.8-4
[NAS07-1560]
Figure 7.8-5
[NAS07-1580]
*6
39 Application No Yes Yes No No No No Yes Figure 7.6-6 Figure 7.8-1
not provided, web Figure 7.8-2
server) [NAS07-1440]
Figure 7.8-3
[NAS07-1500]
NAS07-170
NAS07-180 DKC515I

shooting see ..
Report Report Core Crash Hiber- Opera- Fail- Opera- procedure
from from dump dump nation tions over tion
*2
Blade NAS
Manager manage-
ment
*1
console
*8 *8
40 Failure in start Yes Yes No No Yes No No No Figure 7.6-7 Figure 7.8-1
processing [NAS07-800] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
*8 *8
41 Failure in stop Yes Yes No No Yes No No No Figure 7.6-7 Figure 7.8-1
processing [NAS07-800] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
Failure when NAS *9 *9
42 No Yes No No No No No No Figure 7.6-8 Figure 7.8-1
OS LU is full [NAS07-830] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
43 Failure in NAS Yes No No No No No Yes Yes Figure 7.6-9 Figure 7.8-1
OS file system [NAS07-860] [NAS07-1400]
Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
44 Failure during Yes No No No No No No Yes Figure 7.6-10 -
NAS OS startup [NAS07-900]
or stop (invalid
dump LU)
45 Failure during Yes No No No No No No Yes Figure 7.6-11 -
NAS OS startup [NAS07-920]
or stop (unable to
connect NTP
server)
46 NAS OS Yes No No No No No No Yes Figure 7.6-12 -
application [NAS07-960]
failure (unable to
set internal IP
address)
47 Failure during Yes No No No No No No Yes Figure 7.6-13 Figure 7.8-1
NAS Dump [NAS07-1001] [NAS07-1400]
collection Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
48 NAS cluster Yes Yes No No No No No
*10
No Figure 7.6-14 Figure 7.8-1
management LU [NAS07-1003] [NAS07-1400]
failure (in NAS Figure 7.8-2
OS start/stop [NAS07-1440]
processing) Figure 7.8-3
[NAS07-1500]
NAS07-180
NAS07-181 DKC515I

Report Report Core Crash Hiber- Opera- Fail- Opera- shooting see ..
from from dump dump nation tions over tion procedure
Blade NAS *2
Manager manage-
ment
*1
console
49 Failure in Yes Yes No No No No No
*10
preliminary [NAS07-1005] [NAS07-1400]
processing for Figure 7.8-2
NFS share (in [NAS07-1440]
NAS OS start/stop Figure 7.8-3
processing) [NAS07-1500]
50 User LU failure Yes Yes No No No No No
*10
(in NAS OS [NAS07-1009] [NAS07-1400]
start/stop Figure 7.8-2
processing) [NAS07-1440]
Figure 7.8-3
[NAS07-1500]
51 Failure in setting Yes Yes No No No No No
*10
or releasing NFS [NAS07- [NAS07-1400]
share (in NAS OS 1009C] Figure 7.8-2
start/stop [NAS07-1440]
[NAS07-1500]
52 Service IP Yes Yes No No No No No
*10
up/down failure [NAS07-1009F] [NAS07-1400]
(in NAS OS Figure 7.8-2
[NAS07-1500]
53 Failure in setting Yes Yes No No No No No
*10
or releasing CIFS [NAS07-1009J] [NAS07-1400]
(in NAS OS Figure 7.8-2
[NAS07-1500]
54 NAS OS or Yes Yes No No No No No
*10
application failure [NAS07- [NAS07-1400]
(in NAS OS 1009N] Figure 7.8-2
[NAS07-1500]
*4 *11
55 File system for a Yes Yes No No Yes No Yes No Figure 7.6-21 Figure 7.8-1
user LU is [NAS07- [NAS07-1400]
blocked 1009R] Figure 7.8-2
[NAS07-1440]
Figure 7.8-3
[NAS07-1500]
55 User LU file Yes Yes No Yes No No Yes Yes *11 Figure 7.6-22 Figure 7.8-1
system is blocked [NAS07- [NAS07-1400]
A 1009U1] Figure 7.8-2
(when automatic
failover function [NAS07-1440]
is enabled) Figure 7.8-3
[NAS07-1500]
56 NAS OS System Yes Yes No No Yes No No
*10
No Figure 7.6-23 -
File Failure (in [NAS07-
NAS OS 1009V]
Start/Stop
Processing)
NAS07-181
NAS07-190 DKC515I
*1: This operations are performed from the NAS management console until necessary data is
obtained.
*2: Yes: Business tasks continue.
However, if the application server is connected with Windows client (CIFS share) when a
failover occurs, the CIFS share is released. Therefore, you must reconnect the server with
CIFS share.
No: Business tasks are (partly) disabled.
*3: Only the start and end of the failover are reported.
*4: To obtain failure information, you might need to obtain a hibernation dump manually.
*5: The NAS OS does not respond until you obtain a hibernation dump or the performance is
degraded until you restore the performance following the developer's instructions.
*6: The command line should be used because NAS Blade Manager is not operational.
*7: Operation status depends on the way in which failback abnormally terminates. See the NAS
Blade Manager User’s Guide (9.4.3Viewing error information in the Browse Cluster Status
window and taking recovery action).
*8: The failover function reports resource names to the SVP or NAS Blade Manager when a
failure occurs in the services such as LVM, file systems, and NFS public directories, at the
startup of such services. The failover function reports the failed part (location) where services
cannot be provided due to a hardware or software failure, to the system administrators via the
NAS Blade Manager GUI, and to the maintenance personnel via the SVP. The failover
function also reports the start and completion of failover to the maintenance personnel and
system administrators via the SVP and NAS Blade Manager GUI respectively. Table 7.3-4
lists the types of failures reported by the failover function.
*9: Depending on the available space and condition of the NAS OS LU, failover might occur. In
this case, hibernation dump will be collected.
*10: The failure can cause an error in failover processing.
*11: You can perform operations that do not access the blocked file system.
NAS07-190
NAS07-200 DKC515I
Table 7.3-4 Failures Reported by the Failover Function

# Report Report to Explanation Failed part
to SVP NAS Blade Hardware Software
(SIM Manager
code)
1 -- KAQG72006-E A failure is detected in LVM when services start. Yes Yes

2 ac84x4 A failure is detected in the NAS Cluster Yes Yes
Management LU used by the failover function when
services start.
3 ac84x5 A failure is detected in NFS when services start. - Yes
4 ac84x6 KAQG72006-E A failure is detected in all the file systems when Yes Yes
services start.
5 ac84x7 KAQG72006-E A failure is detected in all the NFS shares when Yes Yes
services start.
6 ac84x8 KAQG72007-E A failure is detected in the up of a service IP address Yes Yes
when services start.
7 ac84x9 A failure is detected in starting a CIFS service when Yes Yes
services start.
8 ac84xB A failure is detected in the OS or application when - Yes
services start.
9 ac84x4 A failure is detected in the NAS Cluster Yes Yes
Management LU used by the failover function when
services stop.
10 ac84x5 A failure is detected in NFS when services stop. - Yes
11 ac84x6 KAQG72009-E A failure is detected in the file system when it is Yes Yes
unmounted.
12 ac84x7 A failure is detected in the release of NFS share Yes Yes
when services stop.
13 ac84x8 A failure is detected in the down of a service IP Yes Yes
address when services stop.
14 ac84x9 A failure is detected in stopping a CIFS service Yes Yes
when services stop.
15 ac84xB A failure is detected in the OS of application when - Yes
services stop.
16 ac84x2 KAQG70000-E An automatic failover has started. Yes Yes
17 ac84xE *1 An automatic failover has failed. Yes Yes
18 ac84xF KAQG70001-E An automatic failover has completed. - -
19 ac84xC The network interface has been in the link down Yes -
state for more than 60 seconds.
*1: One of the messages from KAQG72000-E to KAQE72005-E will be reported.
NAS07-200
NAS07-210 DKC515I
7.4 Identifying Troubleshooting Procedures from Failure Phenomena
Figure 7.4-1 shows the flowchart for software troubleshooting related to the failure phenomena
listed in Table 7.3-3. The numbers from 1 to 56 in the following figures correspond to the
phenomena listed in and Table 7.3-2 [NAS07-120] and Table 7.3-3 [NAS07-170].
NAS07-210
NAS07-220 DKC515I
An error occurred. 7.5.x and 7.6.x shows failures that require immediate actions, and procedures for
obtaining dumps.
7.7.x and 7.8.x shows procedures for applying the corrected version of NAS OS after
investigations by the developer, or procedures after the hardware to be replaced
becomes available.
First resolve the SIM code

YES other than the SIM code
Check the SIM code. whose format is SIM=ac8xxx.
Does any SIM code other
than ac8xxxexist?
Select DKC (Controller) from
Maintenance window and check the
NO NAS OS processor status of MP (CHPx-xx) in CHA Status.
or memory failure For details, see [SVP03-100].
MP failure
Check the SIM code. YES
The NAS OS processor failure YES
might have occurred 3 Is it an MP 1
(SIM code ac82xx).*1 failure?
[NAS07-280] [NAS07-260]
NO
Check the YES
SIM code. Is it an RAID
internal error (other than MP)?
(SIM code 32xxxx)
Check the SIM code. #16. Flowcharts for the RAID
The NAS OS processor YES internal error (other than MP)
environment failure might have NO Troubleshooting (if
occurred (SIM code correctable):
ac83xx).*1
#6. Flowcharts for the NASOS 7.5.12 [NAS07-560]
processor environment failure Replacement:
*2
Troubleshooting: 7.7.1 [NAS07-1050]
7.5.2 [NAS07-380]
Replacement: External device
7.7.1 [NAS07-1050] failure
Check the YES
SIM code. Is it an external
device error? (SIM code 13
21Dxxx, EFD000)
[NAS07-271]
NO
Select Logical Device window from
the Maintenance window and check
5 the logical device status. For details,
[NAS07-230] see [SVP03-240].
2-PDEV failure
NAS OS memory failure, bus failure, or YES

network port failure Is this a logical device failure
NAS OS failure during startup or stop 2
(in two PDEVs)?
NAS OS application failure
NAS OS failure and application failure [NAS07-270]
NO
*1: The code ac82xx, ac83xx, ac85xx, or ac86xx might appear at the same time Flowcharts for the hardware
when the code ac84xx appears. In that case, first resolve the code ac82xx, failure not related to NAS
ac83xx, ac85xx, or ac86xx. See REPLACE Section.
*2: The warning appears, however, operations continue. Take action promptly.
Figure 7.4-1 Flowcharts for Troubleshooting Related to Failure Phenomena (1/19)
NAS07-220
NAS07-230 DKC515I
Flowchart for NAS OS memory, bus, or

5 network port failure
Check the SIM code.

The NAS OS memory failure YES
or bus failure might have
occurred (SIM code
ac85xx).*1
4 [NAS07-290]
NO
NAS OS memory failure or

NAS OS bus failure
Check the SIM code. YES
The network port failure might
have occurred Check if the SIM code ac84x2 was
(SIM code ac86xx).*1 output after the ac86xx was output
for the same NAS Package.
NO Check the SIM code. NO

Did a failover occurred (SIM
code ac84x2) ?
#13A. Flowcharts for an internal error

YES in a data LAN network board (partial
failure, able to continue operation)
Replacement: 7.7.1 [NAS07-1050]
#13. Flowcharts for an internal error

in a data LAN network board
6 [NAS07-240] *1: The code ac82xx, ac83xx, ac85xx, or

ac86xx, ac8xxx might appear at the same
time when the code ac84xx appears. In
NAS OS failure during startup or stop
that case, first resolve the code ac82xx,
NAS OS application failure
ac83xx, ac85xx, or ac86xx.
NAS OS failure and application failure
NAS07-230
NAS07-240 DKC515I
Flowchart for NAS OS application failure

6
Click Refer button in the

Content-SIM window for the
Check the SIM code. YES ac88x3 SIM subject to SIM log,
NAS OS application failure might have and then select SSB and click OK
occurred. button in the Refer window. Check
(SIM code ac88x3). the internal data 0x44-0x47.
For details, see [SVP02-60].
NO YES
Check the subcode.
Failure might have occurred during
NAS Dump collection.
(subcode 0x06xxxxxx)
NO
#47 Flowcharts for failure during NAS
Dump collection
Upgrade: 7.8.1 [NAS07-1400]
7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]

ac88x3 SIM subject to SIM log,
and then select SSB and click OK
button in the Refer window. Check
the internal data 0x44-0x47.
Check the subcode. YES

NAS OS system file failure
(subcode 0x04080101)
NO
#56 Flowcharts for NAS OS system file
failure (in NAS OS start/stop
processing)
Troubleshooting and replacement:
7.6.23 [NAS07-1009V]
7 #46 Flowcharts for the NAS OS

application failure (unable to set
[NAS07-250] internal IP address)
*1
NAS OS failure during startup or stop
NAS OS and application failure
*1: The warning appears, however, operations continue. Take action promptly.
*2: The types of NAS OS upgrades are:

7.8.1 Upgrading the NAS OS By an Update Version (When a Failure Occurs)
7.8.2 Upgrading the NAS OS By a Patch Version --
Restarting the NAS OS Is Not Required (When a Failure Occurs)
7.8.3 Upgrading the NAS OS By a Patch Version -- Restarting the NAS OS Is
Required (When a Failure Occurs)

NAS07-240
NAS07-250 DKC515I
Flowchart for NAS OS failure during startup or stop

7

ac88xa SIM subject to SIM log,
and then select SSB and click OK
button in the Refer window. Check
Check the SIM code. YES Check the subcode if YES

NAS OS failure during startup or dump LU is invalid.
stop might have occurred (SIM (subcode: 0x00020002)
code ac88xa).
NO NO
#44 Flowcharts for the NAS OS

failure during startup or stop (Invalid
(Subcode dump LU)
0x00030001) Troubleshooting and replacement:
*1
7.6.10 [NAS07-900]
#45 Flowcharts for the NAS OS

[NAS07-300] failure during startup or stop
8 (Unable to connect NTP server)
*1
NAS OS and application failure 7.6.11 [NAS07-920]
*1: The warning appears, however, operations continue.

Take action promptly.
NAS07-250
NAS07-260 DKC515I
Flowchart for the MP failure

1
YES #19 Flowcharts for the failover due to MP

Are both MPs failed? failure (two MPs failed)
NO
Check the SIM code. NO #17 and #18. Flowcharts for NAS slowdown
Failover might have failure (due to MP failure)
occurred (SIM code Troubleshooting: 7.5.12 [NAS07-560]
*1
ac84x2). Replacement: 7.7.1 [NAS07-1050]
YES
#21 Flowcharts for the RAID internal (MP)
error (unrecoverable)
*1: The warning appears, however, operations

continue. Take action promptly.
NAS07-260
NAS07-270 DKC515I
Flowchart for the 2-PDEV failure

2
The failed PDEV YES #31. Flowchart for the RAID

is the NAS OS LU (See the failure (2 PDEVs: NAS
user LU configuration). System LUs - NAS OS LUs
in the cluster belong to the
same RAID group)
The NAS OS LUs in YES Troubleshooting:
NO the cluster belong to the same 7.5.6 [NAS07-440]
RAID group (See the user LU Replacement:
configuration). 7.7.6 [NAS07-1180]
NO #30. Flowchart for the RAID

failure (2 PDEVs: NAS
The failed PDEV is the YES System LUs - NAS OS LUs
#25. Flowchart for the RAID failure (2
NAS Cluster Management LU (See in the cluster belong to
PDEVs: NAS Cluster Management LUs)
the user LU configuration). different RAID group)
Replacement: 7.7.7 [NAS07-1200] Troubleshooting:
7.5.5 [NAS07-420]
NO
Replacement:
7.7.5 [NAS07-1140]
YES #26. Flowchart for the RAID failure (2
The failed PDEV PDEVs: Dump LUs)
is the dump LU (See the user LU Troubleshooting: 7.5.8 [NAS07-480]
configuration). Replacement: 7.7.8 [NAS07-1220]
NO
The failed YES #27. Flowchart for the RAID failure (2

PDEV is the error PDEVs: Error information LUs)
information LU (See the user LU Troubleshooting: 7.5.9 [NAS07-500]
NO
YES #28. Flowchart for the RAID failure (2

The failed PDEV
PDEVs: Command devices)
is the command device (See the user
LU configuration).
NO
#29. Flowchart for the RAID failure (2
YES PDEVs: Backup LU of NAS Cluster
The failed PDEV
is the backup LU of NAS
Management LUs)
CM LU (See the user LU Troubleshooting: 7.5.11 [NAS07-540]
NO #23. Flowchart for the RAID failure (2

PDEVs: User LUs)
NAS07-270
NAS07-271 DKC515I
Flowchart for the external device failure

13
#24. External device failure:

NAS07-271
NAS07-280 DKC515I
Flowchart for the NAS OS

3 memory failure and NAS OS bus
Click Refer button in the failure
ac82xx SIM subject to SIM log.
Check the subcode. YES

The Pentium cache parity
error might have occurred
(Error code 1b14).
NO
#11. Flowcharts for the Pentium
cache parity error

ac82xx SIM subject to SIM log.
Check the
subcode. The NAS
OS memory failure or bus failure YES
might have occurred (Error code: 1b12,
1b13, 1b15, 1b16, 1b17,
1b18, 1ac4).
#10 and #12. Flowcharts for the NAS
OS memory failure or bus failure
NO Troubleshooting: 7.5.2 [NAS07-380]
#1, #2, #3, and #4. Flowcharts for

the NAS OS processor failure
NAS07-280
NAS07-290 DKC515I
Flowchart for the NAS OS

4 memory failure and NAS OS bus
failure
#10. Flowchart for the NAS OS memory failure

and NAS OS bus failure (ECC uncorrectable
error) (4th time)
NAS07-290
NAS07-300 DKC515I
Flowchart for the NAS OS or application failure

8
Check the SIM. Check the SIM. YES

NO The I/O failure detected by a
The NAS OS failure might
have occurred (SIM code NAS OS might have occurred
ac84x0). (SIM code ac88xf).
Select the ac84x0 code of the

YES 17
SIM logs, and then click the NO
Refer button in the Content-SIM
window. Disk I/O timeout failure
[NAS07-301]
Check the SSB. Check the SIM.

The Linux panic might have
YES The NAS OS file system
occurred (Error code 1af4). failure might have occurred
(SIM code ac88x2).
YES
NO #34. Flowcharts for the NAS OS panic
16
failure NO [NAS07-345]
Upgrade *1: 7.8.1 [NAS07-1400], NAS related file system failure
7.8.2 [NAS07-1440], and
Did YES
The NAS OS boot or YES system administrator report
shutdown timeout has occurred that the operational speed 10
(Error code 1a41, 1a51, 1a6a, and was decreased?
1a71).*3 [NAS07-320]
NO #40, #41. Flowcharts for the NAS OS failure NO

Slowdown failure
(in start/stop processing)
Upgrade *1: 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
9 [NAS07-310] 12
[NAS07-302]
Flowcharts for the NAS OS hangup failure, Flowcharts for the network application failure
failure when BIOS is started (FWH failure), or
NAS OS application failure (unable to set
internal IP address)
*1 The types of upgrade (NAS OS) are:

7.8.1: Upgrading the NAS OS by an Update Version (When a Failure Occurs)
7.8.2: Upgrading the NAS OS by a Patch Version – Restarting the NAS OS is not
7.8.3: Upgrading the NAS OS by a Patch Version – Restarting the NAS OS is Required
*2 The types of upgrading (NAS Blade Manager, optional program products) are:
7.8.4: Upgrading NAS Blade Manager (When a Failure Occurs)
7.8.5: Upgrading an Optional Program Product (When a Failure Occurs)
*3 A timeout occurs:
- After 10 minutes if NAS OS is booted.
- After 60 minutes if NAS OS is shut down.
NAS07-300
NAS07-301 DKC515I
Flowchart for the disk I/O timeout failure

17
Select the code ac88xa in the
SIM logs, and then click the Refer
button in the Content-SIM
window. Select SSB in the Refer
window and then click OK. Check
Check the
subcode. The timeout YES
error of disk I/O might have occurred
in a NAS OS LU. (Subcode
0x01010101) #32. Flowcharts for the disk I/O timeout
error in a NAS OS LU (response from
NO target MP, retry unsuccessful):
Upgrade *1: 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
Select the code ac88xa in the SIM

logs, and then click the Refer
button in the Content-SIM window.
Select SSB in the Refer window
and then click OK. Check the
internal data 0x44-0x47.
Check the
subcode. The disk I/O YES
timeout error might have occurred
in a user LU. (Subcode
0x01010103)
NO
#22. Flowcharts for the disk I/O timeout error in
a user LU (response from target MP, retry
unsuccessful):
Upgrade *1: 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
#29A. Flowcharts for the disk I/O timeout error in

(Subcode an LU other than a NAS OS LU (response from
0x01010102) target MP, retry unsuccessful):
Troubleshooting: 7.5.16 [NAS07-619B]
Upgrade *1: 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]

7.8.3: Upgrading the NAS OS by a Patch Version – Restarting the NAS OS is
NAS07-301
NAS07-302 DKC515I
Flowchart for the network and application failures

12
Check the SIM. YES

Has a failover occurred 11
(SIM code ac84x2)?
Flowcharts for the network port failure (communication

NO
impossible) – data LAN link down, switch failure, or failure
in entire trunking.
Failure in NAS OS start/stop processing.
Failure other than the NAS OS failure (such as the
application failure).
[NAS07-330]
18
Flowcharts for the network failure in CHA setting (network

settings failed), the network port failure (control LAN fiber
optic cable (LAN cable) link down or switch failure), failure
in part of trunking, or the application failure
[NAS07-340]
NAS07-302
NAS07-310 DKC515I
Flowchart for the NAS OS hangup failure, failure when

9 BIOS is started (FWH failure), or the NAS OS application
failure (unable to set internal IP address)
Select (CL) [Refer] in the

“Content-SIM” window of the
SIM, ac84xx, that is an object of
the SIM log. For the details, see
page SVP02-60.
YES
Unable to set internal
IP address? (Error code
1ad5, 1ad6, and 1ad7)
NO #46. Flowchart for the NAS OS application

failure (unable to set internal IP address):
Troubleshooting*1: 7.6.12 [NAS07-960]
Check
the relevant SSB to YES
see if BIOS startup failure
occurred. (Error code: 1a30,
1a31, and 1a32)
#5. Flowchart for failure when BIOS is

started:
Replacement: -- [MICRO-FC01-10]
#7, #8, #35. NAS OS hangup failure:

Upgrade*1 : 7.8.1 [NAS07-1400]
7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]

NAS07-310
NAS07-320 DKC515I
Flowchart for the slowdown failure

10
Ask system administrator about

the status of user operations.
YES #15. Flowcharts for NAS OS slowdown

The error is recoverable (timeout of disk I/O response from target MP,
*1
and operations can be retry successful): 7.5.12 [NAS07-560]
*2
continued. Replacement: 7.7.1 [NAS07-1050]
NO
#36. Flowcharts for the OS slowdown failure:
*3
Replacement : 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
*1 SIM is not reported, but the SSB code 1699 is reported.

*2 The warning appears, however, operations continue. Take action
not Required (When a Failure Occurs)
NAS07-320
NAS07-330 DKC515I
Flowchart for the network port failure (communication

11 impossible) – data LAN fiber optic cable (LAN cable) link
down, switch failure or failure in entire trunking, failure in
NAS OS start/stop processing, and failure other than NAS
OS failure when failover occurred (such as application
failure)
#13B Flowchart for network port failure

Check the YES
(communication impossible) – data LAN fiber optic
SIM. Has link down occurred? cable (LAN cable)*2, link down, switch failure, or
(SIM code: ac84xc) failure in entire trunking
Replacement*1: 7.7.12 [NAS07-1340]
NO
YES #48 Flowchart for NAS cluster management LU

Check the SIM. failure (in NAS OS start/stop processing)
Has NAS cluster management Troubleshooting: 7.6.14 [NAS07-1003]
LU failure occurred? Upgrade*1 : 7.8.1 [NAS07-1400]
(SIM code: 7.8.2 [NAS07-1440]
ac84x4) 7.8.3 [NAS07-1500]
NO
#49 Flowchart for failure in preliminary processing

Check YES for NFS share (in NAS OS start/stop processing)
the SIM. Has failure in Troubleshooting: 7.6.15 [NAS07-1005]
preliminary processing for NFS Upgrade*1 : 7.8.1 [NAS07-1400]
share occurred? (SIM code: 7.8.2 [NAS07-1440]
ac84x5) 7.8.3 [NAS07-1500]
NO
#50 Flowchart for user LU failure (in NAS OS

Check the YES start/stop processing)
SIM. Has user LU Troubleshooting: 7.6.16 [NAS07-1009]
failure occurred? Upgrade*1 : 7.8.1 [NAS07-1400]
(SIM code: ac84x6) 7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
NO
14
Flowcharts for the network port failure

(communication impossibe) (dataLAN
fiber optic cable (LAN cable) link down), *1 The types of upgrade (NAS OS) are:
NAS OS failure in start/stop porcessing, 7.8.1: Upgrading the NAS OS by an Update Version (When a Failure
failure other than NAS OS failure when Occurs)
failover occurred (such as application 7.8.2: Upgrading the NAS OS by a Patch Version – Restarting the NAS
failure) OS is not Required (When a Failure Occurs)
7.8.3: Upgrading the NAS OS by a Patch Version – Restarting the NAS
[NAS07-331] OS is Required (When a Failure Occurs)
*2 Includes the cable shared by the data LAN and control LAN.
NAS07-330
NAS07-331 DKC515I
Flowchart for the network port failure (communication

14 impossible) – data LAN fiber optic cable (LAN cable) link
down, failure in NAS OS start/stop processing, and
failure other than NAS OS failure when failover occurred
(such as application failure)
#51 Flowchart for failure in setting or releasing

Check the YES NFS share
SIM. Has failure in setting Troubleshooting: 7.6.17 [NAS07-1009C]
or releasing NFS share occurred? Upgrade*1 : 7.8.1 [NAS07-1400]
(SIM code: ac84x7) 7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
NO
YES #52 Flowchart for service IP up/down failure

Check the SIM.
Troubleshooting: 7.6.18 [NAS07-1009F]
Has service IP up/down
Upgrade*1 : 7.8.1 [NAS07-1400]
failure occurred? (SIM code:
7.8.2 [NAS07-1440]
ac84x4)
7.8.3 [NAS07-1500]
NO
#53 Flowchart for failure in setting or releasing

Check YES CIFS (in NAS OS start/stop processing)
the SIM. Has failure in
Troubleshooting: 7.6.19 [NAS07-1009J]
setting or releasing CIFS
Upgrade*1 : 7.8.1 [NAS07-1400]
occurred? (SIM code:
7.8.2 [NAS07-1440]
ac84x5) 7.8.3 [NAS07-1500]
NO
#54 Flowchart for NAS OS or application failure

Check the YES (in NAS OS start/stop processing)
SIM. Has NAS OS or Troubleshooting: 7.6.20 [NAS07-1009N]
application failure occurred? Upgrade*1 : 7.8.1 [NAS07-1400]
(SIM code: ac84x6) 7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
NO
15
Flowchart for the failure other than NAS

OS failure when failover occurred (such
as application failure) *1 The types of upgrade (NAS OS) are:
7.8.1: Upgrading the NAS OS by an Update Version (When a Failure
[NAS07-332]
Occurs)
OS is not Required (When a Failure Occurs)
OS is Required (When a Failure Occurs)
NAS07-331
NAS07-332 DKC515I
Flowchart for the failure other than NAS OS failure when

15 failover occurred (such as an application failure)
Select DKC (Controller) from the

Maintenance window and check the
status of MP (CHPx-xx) in CHA Status
#19 and #21 Flowcharts for the MP

Has an MP failure YES failure (failover)
occurred? Troubleshooting: 7.5.1 [NAS07-360]
NO
In the ‘NAS Setup on SVP (Main)’

window, make sure that the NAS
Package status is ACTIVE or
INACTIVE. For details see [NAS03-260].
#37. Flowcharts for the application failure

(failover occurred)
YES Upgrade*1 : 7.8.1 [NAS07-1400]
Is the NAS Package
status ACTIVE or INACTIVE? 7.8.2 [NAS07-1440]
(Is NAS OS running?) 7.8.3 [NAS07-1500]
#32 Flowcharts for the timeout error of disk I/O in NAS OS

NO LU (response from target MP, retry unsuccessful)
Upgrade*1: 7.8.1 [NAS07-1400]
7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
*1 The types of upgrades (for NAS OS) are:

NAS07-332
NAS07-340 DKC515I
Troubleshooting flowchart for the network failure in CHA setting

18 (network settings failed), network port failure (control LAN fiber optic
cable (LAN cable) link down or switch failure), application failure, or
failure when NAS OS LU is full.
#38. Flowcharts for the application

failure in something other than the
Did the system NO
administrator inform you that Web server (failover not provided)
the NAS Blade Manager GUI Troubleshooting: 7.6.5 [NAS07-740]
cannot be used? Upgrade *1, *2: 7.8.1 [NAS07-1400]
7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
YES 7.8.4 [NAS07-1560]
7.8.5 [NAS07-1580]
Has a failure occurred YES #13A. Flowchart for the failure in part
in part of trunking (link down) of trunking:
(SIM code: ac88x1)? Troubleshooting and replacement:
7.7.14 [NAS07-1360C]
NO
Check the Port Status in the

System Equipment Status
window.
YES
#14.Flowchart for the link down for
Has link down occurred? fiber optic cable (LAN cable) for
control LAN or switch failure
7.7.13 [NAS07-1360A]
NO
Have system
YES #42.Flowcharts for the failure when
administrators reported that
KAQM15022-E error occurs in the NAS OS LU is full
procedure of Troubleshooting and replacement:
GUI login? 7.6.8 [NAS07-830]
NO
#39. Application failure in the web

server (failover not provided)
Have system
administrators and users
reported that I/Os from the client Upgrade *1: 7.8.1 [NAS07-1400]
were impossible? 7.8.2 [NAS07-1440]
7.8.3 [NAS07-1500]
*1 The types of upgrades (for NAS OS) are:

YES
#33. Flowchart for the network failure Required (When a Failure Occurs)
(network settings failed) 7.8.3: Upgrading the NAS OS by a Patch Version – Restarting the NAS OS is
Troubleshooting and replacement: Required (When a Failure Occurs)
7.5.13 [NAS07-580] *2 The types of upgrades (for NAS Blade Manager, optional program products) are:
7.8.4: Upgrading NAS Blade Manager (When a Failure Occurs)
7.8.5: Upgrading an Optional Program Product (When a Failure Occurs)
NAS07-340
NAS07-345 DKC515I
Flowchart for NAS-related file system failure

16
Click Refer in the ‘Content-SIM’

window of the SIM ac88x2, that
is an object of the SIM log.
Select SSB in the ‘Refer’
window and then click OK.
Check the data 0x44 to 0x47 of
the internal data. For details,
see [SVP02-60].
Check the subcode. Yes #43. Flowchart for the NAS OS

Did a NAS OS file system file system failure
failure occurred (subcode: Troubleshooting:
0x00000001) ? 7.6.9 [NAS07-860]
*1
Upgrade :
No 7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
(Subcode:
0x00000002)
Check the SIM. Yes #43. Flowchart for the NAS OS

Has a failover occurred? file system blockage (when
(SIM code: ac84x2) automatic failover function is
enabled)
Troubleshooting:
No 7.6.22 [NAS07-1009U1]
*1
Upgrade :
7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
#55. Flowchart for a locked user

LU file system
Troubleshooting:
7.6.21 [NAS07-1009R]
*1
Upgrade :
7.8.1 [NAS07-1400],
7.8.2 [NAS07-1440], and
7.8.3 [NAS07-1500]
*1 The types of upgrades (NAS OS) are:

NAS07-345
NAS07-350 DKC515I
7.5 Hardware Troubleshooting Procedures
In this section, the cluster is assumed to consist of CL1-CHA and CL2-CHA, and the
following tables show the flowcharts for hardware troubleshooting from Figure 7.5-1 to
Figure 7.5-16.
Make sure that CL2-CHA is properly referred to as the actual location for hardware
troubleshooting when a software failure occurs on the CHA location.

Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
# Failure Figure No.

1 NAS Package failure detected by a processor in the NAS Package Figure 7.5-1 [NAS07-360]
2 NAS Package failure detected by a NAS OS driver or kernel Figure 7.5-2 [NAS07-380]
3 RAID failure (2 PDEVs: user LUs) Figure 7.5-3 [NAS07-400]
4 External device failure Figure 7.5-4 [NAS07-411]
5 RAID failure (2 PDEVs: NAS System LUs  NAS OS LUs in the Figure 7.5-5 [NAS07-420]
cluster belong to different RAID groups)
6 RAID failure (2 PDEVs: NAS System LUs  NAS OS LUs in the Figure 7.5-6 [NAS07-440]
cluster belong to the same RAID group)
7 RAID failure (2 PDEVs: NAS Cluster Management LUs) Figure 7.5-7 [NAS07-460]
8 RAID failure (2 PDEVs: dump LUs) Figure 7.5-8 [NAS07-480]
9 RAID failure (2 PDEVs: error information LUs) Figure 7.5-9 [NAS07-500]
10 RAID failure (2 PDEVs: command devices) Figure 7.5-10 [NAS07-520]
11 RAID failure (2 PDEVs: Backup LUs of NAS Cluster Management Figure 7.5-11 [NAS07-540]
LUs)
12 Hardware failure (correctable) Figure 7.5-12 [NAS07-560]
13 Network failure (network settings failed) Figure 7.5-13 [NAS07-580]
14 Fiber optic cable (LAN cable) link down, switch failure, or failure in Figure 7.5-14 [NAS07-615]
entire trunking
15 Internal error in a data LAN network board (partial failure, able to Figure 7.5-15 [NAS07-619]
continue operation)
16 Timeout error of disk I/O in an LU other than a NAS OS LU Figure 7.5-16 [NAS07-619B]
(response from target MP, retry unsuccessful)
NAS07-350
NAS07-360 DKC515I
7.5.1 NAS Package Failure Detected By a Processor in the NAS Package
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-1 NAS Package Failure Detected By a Processor in the NAS Package
(1/2)

1 Examine the messages to determine whether a hardware
failure and a failover occurred.
2 Check that the failover finished.
3 Notify ordinary users of the hardware failure.
NAS07-360
NAS07-370 DKC515I
NAS Package failure detected by a

processor in NAS Package.
Hardware failure in failure CHA
SVP/maintenance center: NAS management console: Failure report

By checking SIM, ACC, and SSB, By checking NAS Blade Manager - SVP (failure CHA MP report)
determine whether a hardware failure GUI messages, etc., determine
occurred. whether a failover occurred.
Phone, E-mail: NAS management console:

Notify system administrator of Check that failover from failure CHA
Failover from failure CHA to
details about hardware to normal CHA has finished. normal CHA
failure.
Failover report
(normal CHA report)
SIM, SNMP, E-mail report: Phone, E-mail: - SNMP server (normal CHA
Recognize that failover has Notify maintenance personnel of the report)
finished. completion of failover and the NAS - syslog (normal CHA report)
Package location and, notify ordinary - NAS message (normal CHA
users of the hardware failure. report)
[Recognize that failover has finished.] -SVP(SIM code ac84x2)
If the system administrator does not
contact you, first look for the SIM code Failure CHA: NAS Package
[NAS Package location] failure
ac84x2 issued when the failover started,
Check CHA-xx displayed Normal CHA: Operating
and then look for the subsequent SIM
in the 'Browse Cluster (performing the operations of
code ac84xF to make sure that failover
Status' window of NAS both CL1-CHA and CL2-CHA).
has been completed successfully.
Blade Manager GUI.
NAS management console:

End Monitor normal CHA operation.
Figure 7.5-1 NAS Package Failure Detected By a Processor in the NAS Package
(2/2)
NAS07-370
NAS07-380 DKC515I
7.5.2 NAS Package Failure Detected By a NAS OS Driver or Kernel
CL1-CHA CL2-CHA
Web server
Applications Pentium
OS kernel Backup LU of NAS CM LU
OS driver MP MP
NAS OS LU for CL1-CHA NAS OS LU for CL2-CHA Error Information LU

Command Device
User LU
User LU
User LU
Figure 7.5-2 NAS Package Failure Detected By a NAS OS Driver or Kernel (1/2)

1 Examine messages to determine whether a hardware
failure and a failover occurred.
3 Notify ordinary users of the hardware failure.
NAS07-380
NAS07-390 DKC515I
MMMaintenance personnel System administrators NAS Blade system
NAS Package failure

detected by a NAS OS driver.

SVP, maintenance center: Failure report
By checking NAS Blade
By checking SIM,ACC and - SVP (failure CHA MP report)
Manager GUI messages, etc., - NAS Blade Manager GUI
SSB, determine whether a determine whether a (failure CHA report)
hardware failure occurred. hardware failure and failover - SNMP server (failure CHA
occurred. report)

Notify system administrator of Check that failover from failure
details about hardware CHA to normal CHA has finished. normal CHA
failure.
(Ask Manual Failover) Failover report
Network port failure may not - NAS Blade Manager GUI
cause auto failover depending on (normal CHA report)
its failure factor. - SNMP server (normal CHA
report)
- syslog (normal CHA report)
- NAS message
SIM,SNMP, E-mail report: Phone,
Phone,E-mail:
E-mail:
Notify (normal CHA report)
Recognize that failover has Notifymaintenance
maintenance personnel
personnelof of the
- SVP(SIM code ac84x2)
finished. failover completion,
completion and and
of failover notifythe NAS
ordinary
Packageusers of hardware
location and, notify ordinary
failure occurrence.
users of the hardware failure.
[Recognize that failover has [NAS Package
Failure CHA: NAS Package
finished.] location] failure
If the system administrator does not Check CHA-xx normal CHA: Operating
contact you, first look for the SIM displayed in the (performing the operations of
code ac84x2 issued when the 'Browse Cluster Status' both CL1-CHA and CL2-CHA).
failover started, and then look for window of NAS Blade
the subsequent SIM code ac84xF to Manager GUI.
make sure that failover has been
completed successfully.

Figure 7.5-2 NAS Package Failure Detected By a NAS OS Driver or Kernel (2/2)
NAS07-390
NAS07-400 DKC515I
7.5.3 RAID Failure (2PDEVs: User LUs)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-3 RAID Failure (2PDEVs: User LUs) (1/2)

1 Determine whether a failure occurred in the RAID in
which a user LU exists.
2 Check that the file system is deleted in the user LU on
which the error occurred.
3 Notify ordinary users of the RAID failure.
NAS07-400
NAS07-410 DKC515I
RAID failure (user LU)

RAID failure in user LU
Failure report
SVP, maintenance center: NAS management console: - SVP (drive failure report)
By checking SIM, ACC, and SSB, By checking NAS Blade - NAS Blade Manager GUI
determine whether a RAID failure Manager GUI messages, etc., (CL1or2-CHA report)
occurred. determine whether a RAID - SNMP server (CL1or2-CHA
failure occurred. report)
- SVP (failover failure report):
LVM and file system cannot
be used when services start.
SVP:
Identify LDEV from the failed
PDEV
[Identify LDEV from the
failed PDEV]
See [SVP02-770].
SVP:
Identify the LU and the defined
NAS Package from the LDEV
[Identify the LU and the

defined NAS Package
from the LDEV]
See [SVP03-380].
CL1-CHA: Target operation is
Phone, E-mail: NAS management console: stopped.
Notify system administrator of Delete the failed file system. CL2-CHA: Target operation is
details about hardware failure. stopped.

Check that the failed file Notify maintenance personnel
system is deleted. that the deletion of the failed
file system is finished.
Notify ordinary users of RAID
failure occurrence.
End
Figure 7.5-3 RAID Failure (2PDEVs: User LUs) (2/2)
NAS07-410
NAS07-411 DKC515I
7.5.4 External Device Failure
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device

Figure 7.5-4 External Device Failure (1/2)

1 Determine whether a failure occurred in the external
subsystem in which a user LU exists.
2 Identify the NAS Package that uses the external
subsystem in which the error occurred.
3 Notify ordinary users that the external subsystem
device failure occurred.
NAS07-411
NAS07-412 DKC515I
External device failure External device failure
Failure report
SVP, maintenance center: NAS management console: - SVP (External subsystem
By checking SIM, ACC, and SSB, By checking NAS Blade failure report)
determine whether a RAID failure Manager GUI messages, etc., - NAS Blade Manager GUI
occurred. determine whether a RAID (CL1 or 2-CHA report)
failure occurred. - SNMP server (CL1 or
2-CHA report)
- SVP (failover failure report):
LVM and file system cannot
SVP: be used when services start.
Identify LDEV from the failed
external subsystem.
[Identify LDEV from the
failed external subsystem]
See [SVP02-770].
SVP:
Identify the LU and the defined
NAS Package from the LDEV
[Identify the LU and the

defined NAS Package
from the LDEV]
See [SVP03-380].
CL1-CHA: Target service is
Phone, E-mail: NAS management console: stopped.
Notify system administrator of Notify the users that the CL2-CHA: Target service is
details about hardware failure. external subsystem failure stopped.
occurred.
End
Figure 7.5-4 External Device Failure (2/2)
NAS07-412
NAS07-420 DKC515I
7.5.5 RAID Failure (2 PDEVs: NAS System LUs  NAS OS LUs in the Cluster Belong to
Different RAID groups)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

SVP
Command Device
Dump LU for CL1-CHA User LU

User LU
Figure 7.5-5 RAID Failure (2 PDEVs: NAS System LUs  NAS OS LUs in the
Cluster Belong to Different RAID groups) (1/2)

which a NAS OS LU exists, and whether a failover
occurred.
3 Notify ordinary users of the RAID failure.
NAS07-420
NAS07-430 DKC515I
RAID failure (2 PDEVs: NAS system LUs -

NAS OS LUs in the cluster belong to
different RAID groups)
RAID failure in NAS OS LU for
failure CHA
SVP, maintenance center: By checking NAS Blade Failure report
By checking SIM, ACC, and Manager GUI messages, etc., - SVP (failure CHA MP report)
SSB, determine whether a determine whether a - NAS Blade Manager GUI
hardware failure occurred. hardware failure and failover (failure CHA report)
occurred. - SNMP server (failure CHA
report)

Notify system administrator of Check that failover from
details about hardware failure CHA to normal CHA
normal CHA
failure. has finished.
Failover report
SIM, SNMP, E-mail report: Phone, E-mail: (normal CHA report)
Recognize that failover has Notify maintenance personnel - SNMP server (normal CHA
finished. of the completion of failover report)
and the NAS Package - syslog (normal CHA report)
location and, notify ordinary - NAS message
users of the hardware failure. (normal CHA report)
- SVP (SIM code ac84x2)
[Recognize that failover has [NAS Package Failure CHA: NAS Package
finished.] location] failure
If the system administrator does not Check CHA-xx Normal CHA: Operating
contact you, first look for the SIM displayed in the (performing the operations of
code ac84x2 issued when the 'Browse Cluster both CL1-CHA and CL2-CHA).
failover started, and then look for Status' window
the subsequent SIM code ac84xF to of NAS Blade
make sure that failover has been Manager GUI.
completed successfully.

Cluster Belong to Different RAID groups)(2/2)
NAS07-430
NAS07-440 DKC515I
7.5.6 RAID Failure (2 PDEVs: NAS System LUs  NAS OS LUs in the Cluster Belong to the
Same RAID Group)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP
NAS OS LU for CL1-CHA

SVP NAS OS LU for CL2-CHA
Command Device

User LU
Cluster Belong to the Same RAID Group) (1/2)

which NAS OS LUs exist, and whether a failover
occurred.
NAS07-440
NAS07-450 DKC515I
RAID failure (2 PDEVs: NAS

system LUs - NAS OS LUs in
the cluster belong to the same
RAID group)
RAID failure in NAS OS LU
for CL1-CHA and CL2-CHA
SVP, maintenance center: Maintenance server: Failure report
By checking SIM,ACC and By checking messages from - SVP (Drive failure report)
SSB, determine whether a SVP, etc., determine whether - SNMP server (CL1/2-CHA
RAID failure occurred. a RAID failure occurred. report)

Notify system administrator of Recognize that a RAID failure
details about hardware has occurred.
failure. CL1-CHA: Stopped by NAS
Package failure.
CL2-CHA: Stopped by NAS
Package failure.
End
Cluster Belong to the Same RAID Group) (2/2)
NAS07-450
NAS07-460 DKC515I
7.5.7 RAID Failure (2 PDEVs: NAS Cluster Management LUs)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-7 RAID Failure (2 PDEVs: NAS Cluster Management LUs) (1/2)

which a NAS cluster management LU exists, and
whether a failover occurred.
NAS07-460
NAS07-470 DKC515I
RAID failure (2 PDEVs: NAS

cluster management LUs)
RAID failure in NAS cluster
management LU
SVP, maintenance center: NAS management console: Failure report
By checking SIM, ACC, and By checking NAS Blade - SVP (Drive failure report)
SSB, determine whether a Manager GUI messages (*1), - NAS Blade Manager
RAID failure occurred. etc., determine whether a GUI (CL1/2-CHA report) *1
RAID failure occurred. - SNMP server (CL1/2-CHA
report) *1

Notify system administrator of Recognize that a RAID failure
CL1-CHA: NAS Package failure.
(File service can be continued)
failure.
CL2-CHA: NAS Package failure.
(File service can be continued)
*1: Depending on the NAS cluster management LU

End status, a failure might not be reported.
Figure 7.5-7 RAID Failure (2 PDEVs: NAS Cluster Management LUs) (2/2)
NAS07-470
NAS07-480 DKC515I
7.5.8 RAID Failure (2 PDEVs: Dump LUs)
CL1-CHA CL2-CHA User LU

User LU
User LU
Pentium Pentium
MP MP Backup LU of NAS CM LU
MP MP

SVP
Dump LU for CL1-CHA Dump LU for CL2-CHA Command Device
Figure 7.5-8 RAID Failure (2 PDEVs: Dump LUs) (1/2)

1 Determine whether a failure occurred in the RAID
in which a dump LU exists.
NAS07-480
NAS07-490 DKC515I
RAID failure (dump LU)

RAID failure in NAS dump LU
for failure CHA
By checking SIM,ACC and By checking NAS Blade - SVP (drive failure report)
SSB, determine whether a Manager GUI messages, etc., - NAS Blade Manager GUI
RAID failure occurred. determine whether a RAID (failure CHA report)
failure occurred. - SNMP server (failure CHA
report)
CL1-CHA: Operating.
Phone, E-mail: Phone, E-mail: CL2-CHA: Operating.
Notify system administrator of Recognize that RAID failure
failure.
End
Figure 7.5-8 RAID Failure (2 PDEVs: Dump LUs) (2/2)
NAS07-490
NAS07-500 DKC515I
7.5.9 RAID Failure (2 PDEVs: Error Information LUs)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-9 RAID Failure (2 PDEVs: Error Information LUs) (1/2)

1 Determine whether a failure occurred in the RAID in which
an error information LU exists.
NAS07-500
NAS07-510 DKC515I
RAID failure
(2PDEVs: error information LUs)
RAID failure in error
information LU
RAID failure occurred. determine whether a RAID (CL1/2-CHA report)
failure occurred. - SNMP server (CL1/2-CHA
report)

Notify system administrator of Recognize that a RAID failure CL2-CHA: Operating.
failure.
End
Figure 7.5-9 RAID Failure (2 PDEVs: Error Information LUs) (2/2)
NAS07-510
NAS07-520 DKC515I
7.5.10 RAID Failure (2 PDEVs: Command Devices)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-10 RAID Failure (2 PDEVs: Command Devices) (1/2)

which a command device exists.
NAS07-520
NAS07-530 DKC515I
RAID failure (2PDEVs:

command devices)
RAID failure in command
device LU
failure occurred. - SNMP server (CL1/2-CHA report)
CL1-CHA: Operating.
Notify system administrator of Recognize that RAID failure CHA-1P~CHA-2Y: Snapshot
details about hardware has occurred. tasks are stopped.
failure.
End
Figure 7.5-10 RAID Failure (2 PDEVs: Command Devices) (2/2)
NAS07-530
NAS07-540 DKC515I
7.5.11 RAID Failure (2 PDEVs: Backup LUs of NAS Cluster Management LUs)

User LU
User LU
Pentium Pentium
MP MP

SVP
Figure 7.5-11 RAID Failure (2 PDEVs: Backup LUs of NAS Cluster Management
LUs) (1/2)

which a backup LU of NAS Cluster Management LU
exists.
NAS07-540
NAS07-550 DKC515I
RAID failure
(2 PDEVs: backup LU of NAS CM LU)
RAID failure in backup LU of
NAS CM LU
failure occurred. - SNMP server (CL1/2-CHA
report)

Notify system administrator of Recognize that RAID failure
details about hardware has occurred. CL1-CHA: Operating.
failure. CL2-CHA: Operating.
End
Figure 7.5-11 RAID Failure (2 PDEVs: Backup LUs of NAS Cluster Management
LUs) (2/2)
NAS07-550
NAS07-560 DKC515I
7.5.12 Hardware Failure (Correctable)
(Note) Correctable error occurred in

NAS Package or RAIID.
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP

Command Device
User LU
User LU
User LU
Figure 7.5-12 Hardware Failure (Correctable) (1/2)

1 Examine messages to determine whether a correctable
hardware failure occurred.
NAS07-560
NAS07-570 DKC515I
Hardware failure (correctable)

Hardware failure (correctable)
in failure CHA
By checking SIM, ACC, and By checking NAS Blade - SVP (failure CHA MP
SSB, determine whether a Manager GUI messages, etc., report)
hardware failure occurred. determine whether a - NAS Blade Manager GUI
hardware failure occurred. (failure CHA report)
- SNMP server (failure CHA
report)
Business tasks are continued
by failure CHA.
Report details about Monitor failure CHA CL1-CHA: Operating.
hardware failure. operation. CL2-CHA: Operating.
End
Figure 7.5-12 Hardware Failure (Correctable) (2/2)
NAS07-570
NAS07-580 DKC515I
7.5.13 Network Failure (Network Settings Failed)
CL1-CHA CL2-CHA
Web server
Pentium
Application
NAS OS kernel Backup LU of NAS CM LU
MP MP
NAS OS driver

Command Device
User LU
User LU
User LU
Figure 7.5-13 Network Failure (Network Settings Failed) (1/4)

1 Make sure that this is not a CHA failure.
2 Make sure that the network is working correctly.
3 Check if the MTU value is compatible with the The cluster needs to be stopped and
peripheral devices, and if not, reset the MTU restarted when setting the MTU
value. value using Setup on SVP.
4 Make sure that the communication is successful.
NAS07-580
NAS07-590 DKC515I
Network failure (network settings failed)

Failure CHA: Being activated.
Normal CHA: Operating.
SVP:
By checking SIM and ACC,
recognize that no boot timeout NAS OS no-response state in
or shutdown timeout has failure CHA.
occurred in the NAS OS.*1
No failure report
Phone, E-mail:
Ask system administrators to
check the network status. NO
Client:
Is ping successful
for the NAS
Package?
Client:
Is ping successful for
the NAS Package in
NO the same segment?
YES Client:
Use the traceroute (or tracert YES
for Windows) command to
detect to which point the
network is available.
Client:
Check the network and
intermediate network, and
correct the settings.
SVP: Phone, E-mail: NAS management console:

Make sure that the Port Status is Ask maintenance personnel Correct the network settings,
Link Up in the System to check that the Port Status such as IP address, net mask,
Equipment Status window of the is Link Up in the System default gateway, routing, etc.
Web Console. Equipment Status window of
the Web Console.
Setup on SVP:
Check the network settings, such
as IP address, net mask, default
gateway, etc.
See 3.5.6 [NAS03-620].
*1 A timeout occurs:
1 - After 10 minutes if NAS OS is booted.
- After 60 minutes if NAS OS is shut down.
[NAS07-600]
NAS07-590
NAS07-600 DKC515I
Failure CHA: Starting

Normal CHA: Operating
Phone, E-mail:
Check and notify MTU values Peripheral devices: NO
for failure CHA and normal Are connected devices
CHA. compatible to JumboFrame?
check if devices compatible to
JumboFrame are used. YES
3.5.6 [NAS03-620] NO
Is MTU set for Jumbo
Frame (>1500)?
NAS Management Console,
Peripheral devices: YES
Confirm that the MTU values
are the same. 2
YES [NAS07-610]
Are the MTU values

the same?
NO
2
[NAS07-610]

functionality to stop the cluster on
failure CHA and normal CHA

Set MTU values for failure Notify the completion of stop
CHA and normal CHA. processing of the cluster and
3.5.6 [NAS03-620] MTU values to be set, and ask
to set MTU values.
[NAS07-610]
NAS07-600
NAS07-610 DKC515I

Notify that setting MTU Use NAS Blade Manager
values for failure CHA and functionality to start the cluster
normal CHA has finished. for failure CHA, normal CHA
Client: NO
Is ping
successful?
NAS Management Console,

YES Peripheral devices:
Collect detailed information
Phone, E-mail: and investigate, or ask the
Phone, E-mail: developer to investigate. Investigate or to
Notify the maintenance
Acknowledge that the the developer.
personnel that ping is
network is working.
successful.
END
NAS07-610
NAS07-615 DKC515I
7.5.14 Fiber Optic Cable (LAN Cable) Link Down, Switch Failure, or Failure in Entire Trunking
Switch
CL1-CHA CL2-CHA
Web server
Pentium
Application
MP MP
NAS OS driver

Command Device
User LU
User LU
User LU
Figure 7.5-14 Fiber Optic Cable (LAN Cable) Link Down, Switch Failure, or Failure
in Entire Trunking (1/4)

1 Check that link down for fiber optic cable If the failover finished normally, go to step
(LAN cable) or switch failure, and 2. If the failover did not finish normally
failover occurred. (link-down occurred for the both CHAs), go
to step 2a.
2 Check that the failover is completed.
3 Notify ordinary users that link-down for
the fiber optic cable (LAN cable) or
switch failure occurred.
Recovery procedure when the failover did not finish normally (the both CHAs are link-down)
2a Notify ordinary users that link-down for
the fiber optic cable (LAN cable) or
NAS07-615
NAS07-616 DKC515I
Data LAN fiber optic cable (LAN

cable) link down, switch failure,
or failure in entire trunking
Fiber optic cable (LAN cable)

SVP: link-down or switch failure
From failure report by SIM, ACC, or
SSB, recognize that link-down for Failure report
the fiber optic cable (LAN cable) or - SVP (failure CHA MP report)
switch failure occurred. - NAS Blade Manager GUI
(failure CHA report)
- SNMP server (failure CHA
[Failover finished normally] report)
contact you, check if the SIM code
ac84xF, which is sent when a
failover finishes successfully, or
ac84xE, which is sent when a
failover finishes unsuccessfully, was
issued following ac84x2, which is
sent when a failover starts.
NO
Did the failover
finish normally? Port link-down
occurred for the both
CHAs in the cluster.
YES
[NAS07-618]
[NAS07-617]
Figure 7.5-14 Fiber Optic Cable (LAN Cable) Link Down, Switch Failure, or Failure
in Entire Trunking (2/4)
NAS07-616
NAS07-617 DKC515I

Check if fiber optic cable (LAN
cable) link-down or switch
failure, and failover occurred
through NAS Blade Manager
GUI messages.
NAS Management Console: Failover from failure CHA to

Phone, E-mail:
Confirm that the failover from normal CHA
Notify that fiber optic cable
(LAN cable) link-down or the failure CHA to the normal
switch failure occurred. CHA finished. Failover report
(normal CHA notification)
Phone, E-mail: - SNMP server (normal CHA
SIM, SNMP, E-mail Notify maintenance personnel of report)
the completion of failover and the - syslog (normal CHA
notification:
NAS Package location and report)
Recognize that the failover - System message (normal
ordinary users of fiber optic cable
finished. (LAN cable) link-down or switch CHA report)
failure. - SVP (SIM code ac84x2)
[Checking if failover finished] [Location of NAS
If the system administrator does Package]
Failure CHA: NAS Package
not contact you, check if the Check CHA-xx failure
SIM code ac84xF, which is sent displayed in the Normal CHA: Operating
when a failover finishes Browse Cluster (performing the operations
successfully, was issued Status window of of both CL1-CHA and
following ac84x2, which is sent NAS Blade CL2-CHA)
when a failover starts. Manager.

End Monitor the operation of
CL1-CHA
Figure 7.5-14 Fiber Optic Cable (LAN Cable), Switch Failure, or Failure in Entire
Trunking (3/4)
NAS07-617
NAS07-618 DKC515I

Check if fiber optic cable (LAN
cable) link-down or switch
failure, and failover occurred
through NAS Blade Manager
GUI messages.

Notify that fiber optic cable Notify ordinary users that fiber
optic cable (LAN cable) link-down
(LAN cable) link-down or or switch failure occured.
SIM, SNMP, E-mail Phone, E-mail:

Notify maintenance personnel of
notification: the fiber optic cable (LAN cable)
Recognize the fiber optic link-down or switch failure, and
cable (LAN cable) the NAS Package location.
link-down or switch failure
and NAS Package location. [Location of NAS
Package]
Check CHA-xx
displayed in the Failure CHA: Business tasks
Browse Cluster stopped (for both CL1-CHA
Status window of and CL2-CHA)
NAS Blade Manager.
End
Figure 7.5-14 Fiber Optic Cable (LAN Cable), Switch Failure, or Failure in Entire
Trunking (4/4)
NAS07-618
NAS07-619 DKC515I
7.5.15 Internal Error in a Data LAN Network Board (Partial Failure, Able to Continue Operation)
Switch
CL1-CHA CL2-CHA
Manual failover
Web server
Pentium NAS Cluster Management LU
Application
NAS OS kernel
MP MP
NAS OS driver
Command Device
User LU
User LU
User LU
Figure 7.5-15 Internal Error in a Data LAN Network Board (Partial Failure, Able to
Continue Operation) (1/3)

1 Determine whether a hardware failure
occurred.
2 Notify the ordinary users that a hardware
failure occurred.
3 Manually perform a failover.
NAS07-619
NAS07-619A DKC515I
Internal error in a data LAN network board

(partial failure, able to continue operation)

By checking failure reports such - SVP (failure CHA MP report)
as SIM, ACC, and SSB,
- NAS Blade Manager GUI (failure
acknowledge that a hardware
failure has occurred. CHA report)
- SNMP server (failure CHA report)
stopped]
Check if NAS Package is
INACTIVE in the Main window.
See 3.5.3 [NAS03-260].
Is the node
of the failure
CHA stopped? YES
NO
2
[NAS07-619A1]

Ask the system administrator Check if there is a resource
to check if there is a group running on the failure
resource group running of CHA.
the failure CHA.
Phone, E-mail:
Phone, E-mail:
Acknowledge whether there
personnel whether there is a
is a resource group running
resource group running on
on the failure CHA.
the failure CHA.
Is NO
there a resource
group running on the Failure CHA: Operating
failure CHA? Normal CHA: Operating
(performing the operations of
YES both CL1-CHA and CL2-CHA)
1 2
[NAS07-619A1] [NAS07-619A1]
NAS07-619A
NAS07-619A1 DKC515I
1
Failure CHA: Operating
Phone, E-mail: Phone, E-mail: Failover from the failure

Notify the system administrator Notify the ordinary users and CHA to the normal CHA
of details on the hardware acquire permission for a
failure and the normal CHA failover.
location, and then ask the
system administrator to
node of the failure CHA. NAS Management Console:
Perform a failover from the
failure CHA to the normal CHA
by using NAS Blade Manager
and then confirm that the
failover finished.

Stop the node of the failure
CHA by using NAS Blade
Manager.
Failure CHA: NAS OS running

Phone, E-mail: Normal CHA: Operating
SIM, SNMP, E-mail report: Notify maintenance personnel (Performing the operations of
Acknowledge that the failover and ordinary users of the both CL1-CHA and CL2-CHA)
has finished. completion of the failover and
[Acknowledge that the node [NAS Package location]

has stopped] Check CHA-xx displayed in
Package status is INACTIVE window of NAS Blade
in the 'Main' window. See Manager GUI.
3.5.3 [NAS03-260].

END Monitor normal CHA operation.
NAS07-619A1
NAS07-619B DKC515I
7.5.16 Disk I/O Timeout Error in an LU Other Than a NAS OS LU (Response from Target MP, Retry
Unsuccessful)
CL1-CHA CL2-CHA
Web server Manual failover
Application Pentium
NAS OS kernel Error Information LU
NAS OS driver MP MP
Command Device

Logs of NAS OS
and PP
User LU
Event Hibernation User LU

trace dump User LU

Auto dump NAS dump
Figure 7.5-16 Disk I/O Timeout Error in an LU Other Than a NAS OS LU (Response from
Target MP, Retry Unsuccessful) (1/2)

1 Confirm that a disk timeout error occurred
in an LU other than a NAS OS LU.
2 Manually collect a hibernation dump. Before collecting a hibernation dump,
acquire ordinary users’ permissions because
operations are continuing.
3 Collect the detailed information and send
it to the developer.
NAS07-619B
NAS07-619C DKC515I
Timeout error of disk I/O in an LU other than a NAS OS

LU (response from target MP, retry unsuccessful)
I/O timeout in failure CHA

By checking failure reports such - SVP (Driver report)
as SIM, ACC, and SSB, - NAS Blade Manager GUI
acknowlege that a timeout error (failure CHA report)
of disk I/O occurred. - SNMP server
Phone, E-mail: Failure CHA: Operating
Manager GUI messages,
Notify system administrator of Normal CHA: Operating
etc., determine whether the
details about the failure.
failure occurred.

Check for the permissions for Acquire ordinary user
collecting the hibernation dump. permissions for collecting the
hibernation dump from and
contact maintenance personnel.
SVP:
Identify the failed NAS Package
from the SIM of the I/O timeout
error (ac88xf).
SVP: Collect the hibernation dump.

Collect the hibernation dump.
3.5.10 [1][NAS03-910]
SVP:
Send the detailed information to
the developer and request to
(Performing the operations of both
investigate the dump for a CL1-CHA and CL2-CHA)
primary scan.
To developer
End
Figure 7.5-16 Disk I/O Timeout Error in an LU Other Than a NAS OS LU (Response from
Target MP, Retry Unsuccessful) (2/2)
NAS07-619C
NAS07-620 DKC515I
7.6 Software Troubleshooting

following tables show the flowcharts for software troubleshooting from Figure 7.6-1 to
Figure 7.6-23.

Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
# Failure Figure No.

1 NAS OS failure (panic) Figure 7.6-1 [NAS07-630]
2 NAS OS failure (hangup) Figure 7.6-2 [NAS07-650]
3 NAS OS failure (slowdown) Figure 7.6-3 [NAS07-680]
4 Application failure (failover provided) *1 Figure 7.6-4 [NAS07-710]
5 Application failure in something other than the Web server Figure 7.6-5 [NAS07-740]
(failover not provided) *1
6 Application failure in the Web server (failover not provided) *1 Figure 7.6-6 [NAS07-770]
7 NAS OS failure (in start/stop processing) Figure 7.6-7 [NAS07-800]
8 Failure when a NAS OS LU is full Figure 7.6-8 [NAS07-830]
9 NAS OS file system failure Figure 7.6-9 [NAS07-860]
10 Failure during NAS OS startup or stop (invalid dump LU) Figure 7.6-10 [NAS07-900]
11 Failure during NAS OS startup or stop (unable to connect NTP Figure 7.6-11 [NAS07-920]
server)
12 NAS OS application failure (unable to set internal IP address) Figure 7.6-12 [NAS07-960]
13 Failure during NAS Dump collection Figure 7.6-13 [NAS07-1001]
14 NAS cluster management LU failure (in NAS OS start/stop Figure 7.6-14 [NAS07-1003]
processing)
15 Failure in preliminary processing for NFS share (in NAS OS Figure 7.6-15 [NAS07-1005]
start/stop processing)
16 User LU failure (in NAS OS start/stop processing) Figure 7.6-16 [NAS07-1009]
17 Failure in setting or releasing NFS share (in NAS OS start/stop Figure 7.6-17 [NAS07-1009C]
processing)
18 Service IP up/down failure (in NAS OS start/stop processing) Figure 7.6-18 [NAS07-1009F]
19 Failure in setting or releasing CIFS (in NAS OS start/stop Figure 7.6-19 [NAS07-1009J]
processing)
20 NAS OS or application failure (in NAS OS start/stop processing) Figure 7.6-20 [NAS07-1009N]
21 File system for a user LU is blocked Figure 7.6-21 [NAS07-1009R]
22 User LU file system is blocked (when automatic failover function Figure 7.6-22 [NAS07-1009U1]
is enabled)
23 NAS OS System File Failure (in NAS OS start/stop processing) Figure 7.6-23 [NAS07-1009V]
*1 Operations performed by system administrators. For details, refer to the NAS Blade
Manager User's Guide (9.1 General procedure for troubleshooting).
NAS07-620
NAS07-630 DKC515I
7.6.1 NAS OS Failure (Panic)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Logs of NAS
OS and PP User LU
User LU
Event Crash dump
trace User LU
Auto dump Nas dump

Figure 7.6-1 NAS OS Failure (Panic) (1/3)

1 Examine the messages to determine whether a NAS OS
panic and a failover occurred.
3 Notify ordinary users of the failure and failover
completion.
4 Send the detailed information to developers.
5 Disable the automatic save settings of the NAS OS LU
and NAS Cluster Management LU.
NAS07-630
NAS07-640 DKC515I
NAS OS failure (panic)
NAS management console: NAS OS panic in failure CHA

SVP, maintenance center: By checking NAS Blade
Recognize NAS OS panic by Manager GUI messages,
failure reports such as SIM etc., determine whether a Failure report
(ac84x0), ACC, and SSB (1af4). NAS OS panic occurred. - SVP (failure CHA MP report)
(normal CHA report)
- SNMP server (normal CHA
NAS management console: report)
Check that failover from
failure CHA to normal CHA
has finished. Failover from failure CHA to
normal CHA
SIM, SNMP, E-mail report: Phone, E-mail: Failover report

Recognize that failover has Notify maintenance - NAS Blade Manager GUI
finished. personnel and ordinary (normal CHA report)
users of the completion of - SNMP server (normal CHA
failover and the NAS report)
Package location. - syslog (normal CHA report)
- NAS message
[Recognize that failover has finished.] [NAS Package (normal CHA report)
If the system administrator does not location] - SVP(SIM code ac84x2)
contact you, first look for the SIM code Check CHA-xx
ac84x2 issued when the failover started, displayed in the Failure CHA: Stopped by failure.
and then look for the subsequent SIM 'Browse Cluster Normal CHA: Operating
code ac84xF to make sure that failover Status' window of (performing the operations
has been completed successfully. NAS Blade Manager of both CL1-CHA and
GUI. CL2-CHA).

Monitor normal CHA
operation.
(NAS07-641)
NAS07-640
NAS07-641 DKC515I
SVP:
Obtain the detailed information on
the failure. See 7.2.3 [NAS07-70]
SVP:
investigate the dump for a primary
scan. To developer

Ask the system administrator to Use NAS Blade Manager
check the automatic save settings functionality to check the automatic
of the NAS OS LU and NAS save settings of the NAS OS LU
Cluster Management LU. and NAS Cluster Management LU.
YES
Are the automatic save
settings enabled?
NO Use NAS Blade Manager
functionality to disable the automatic
save settings of the NAS OS LU and
NAS Cluster Management LU.

Confirm that the automatic save of Notify the maintenance
the NAS OS LU and NAS Cluster personnel of the automatic save
Management LU is disabled (*1). settings of the NAS OS LU and
*1 If the NAS OS was not upgraded at the event of the failure

End
recovery, ask the system administrator to set the settings back to the
ones before the failure occurred.
NAS07-641
NAS07-650 DKC515I
7.6.2 NAS OS Failure (Hangup)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Logs of NAS
OS and PP User LU
User LU
Event Hibernation
trace dump User LU
Auto dump Nas dump : Failed part

(Legend) : Monitoring each other
Figure 7.6-2 NAS OS Failure (Hangup) (1/3)

1 Examine the messages to determine whether a hangup
and a failover occurred.
3 Notify ordinary users of the failure and failover
completion.
NAS07-650
NAS07-660 DKC515I
NAS OS failure (hangup)

NAS OS no-response state in
failure CHA.
SVP, maintenance center: NAS management console: Failure report (heart beat
By checking failure reports such By checking NAS Blade disabled)
as SIM, ACC, and SSB, Manager GUI messages, etc., - SVP (failure CHA MP report)
recognize that NAS OS has not - Event trace produced
determine whether a Linux
responded. no-response state exists. (normal CHA report)
report)
Check that failover from
failure CHA to normal CHA Perform failover from failure CHA
has finished. to normal CHA.
Failover report
SIM,SNMP, E-mail report: Phone, E-mail: - NAS Blade Manager GUI
Recognize that failover has Notify maintenance personnel (normal CHA report)
finished. and ordinary users of the - SNMP server (normal CHA
completion of failover and the report)
- NAS message (normal CHA
report)
[Recognize that failover has finished.] - SVP(SIM code ac84x2)
If the system administrator does not [NAS Package location]
contact you, first look for the SIM code Check CHA-xx displayed Failure CHA: Stopped by failure.
ac84x2 issued when the failover started, in the 'Browse Cluster Normal CHA: Operating
and then look for the subsequent SIM Status' window of NAS (performing the
code ac84xF to make sure that failover Blade Manager GUI. operations of both
CL1-CHA and
CL2-CHA).

Monitor normal CHA operation.
1
[NAS07-670]
NAS07-660
NAS07-670 DKC515I
EndMaintenance personnel System administrators NAS Blade system
SVP:
By the SIM code ac84x0 for Hibernation dump is collected.
failover, specify the NAS Package
where a failover has occurred.
SVP:
the failure. See 7.2.3 [NAS07-70].
SVP:
investigate the dump for a primary
scan.
To developer

of the NAS OS LU and NAS save settings of the NAS OS LU and
cluster management LU. NAS cluster management LU.
YES
settings enabled?
NO functionality to disable the automatic
NAS cluster management LU.

the NAS OS LU and NAS cluster personnel of the automatic save
management LU is disabled (*1). settings of the NAS OS LU and
NAS cluster management LU.

End recovery, ask the system administrator to set the settings back to the
NAS07-670
NAS07-680 DKC515I
7.6.3 NAS OS Failure (Slowdown)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Logs of NAS Event
OS and PP trace User LU
User LU
Event Hibernation
trace dump User LU
Auto dump Nas dump

Figure 7.6-3 NAS OS Failure (Slowdown) (1/4)

1 Check if there is no response from the processing of Act on messages if they have
business tasks, or the performance is severely degraded, been issued.
and then determine whether a slowdown occurred.
2 Obtain performance information and either investigate it
or send it to developer.
3 If there is a response, obtain the auto dump and send it to
developers.
4 If there is no response, obtain the auto dump and
manually obtain the hibernation dump.
5 Send the detailed information to developer.
NAS07-680
NAS07-690 DKC515I
NAS OS failure (slowdown)
NAS OS is in a no-response
state in failure CHA or the
Phone, E-mail:
performance is severely
Hear from the user that business
degraded.
tasks have stopped.
No failure report
SNMP, E-mail report: Phone, E-mail:

Recognize slowdown Inform maintenance personnel
occurrence. that slowdown has occurred, and
in which NAS Package the
slowdown has occurred.
NAS Blade Manager, SNMP, or Failure CHA: No response or the

E-mail: Check whether performance is severely
messages were issued. degraded.
Was any message

reported? YES
NO
SVP, maintenance center: Phone, E-mail:

Check whether SIM, ACC, SSB, Inform maintenance personnel
and SVP messages were issued. that no message was reported.
NAS Blade Manager, SNMP, or

Was any message
E-mail: Act on messages.
reported? YES
NO
Phone, E-mail: Maintenance server:

Inform system administrators that Get the performance information
no message was reported. using the SNMP.
To investigator
SVP: or developer
Act on messages. Phone, E-mail:
Inform maintenance personnel
that performance information
was obtained.
[NAS07-700]
NAS07-690
NAS07-695 DKC515I
Phone, E-mail: Acknowledge that

the performance information was
obtained.
NO
Does the NAS OS
respond?
YES
[NAS07-700]
Setup on SVP: Obtain the auto

dump.
[Obtain the auto

dump.] To
See [SVP02-540]. developer.
Did the NO
developer instruct you to
obtain the hibernation
dump?
Setup on SVP, etc: Restore the

performance by following the
YES developer’s instructions.
2 3
[NAS07-700] [NAS07-700]
NAS07-695
NAS07-700 DKC515I
SVP:
Obtain the hibernation dump.
See 3.5.10 [1] [NAS03-910].
SVP:
Send the detailed information
to the developer and request
to investigate the dump for a
primary scan. To developer

of the NAS OS LU and NAS save settings of the NAS OS LU
Cluster Management LU. and NAS Cluster Management LU.
YES
settings enabled?
NO functionality to disable the automatic

the NAS OS LU and NAS Cluster personnel of the automatic save
Management LU is disabled (*1). settings of the NAS OS LU and
End
recovery, ask the system administrator to set the settings back to the
NAS07-700
NAS07-710 DKC515I
7.6.4 Application Failure (Failover Provided)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Core dump
User LU
User LU
Logs of
NAS OS User LU
and PP
Figure 7.6-4 Application Failure (Failover Provided) (1/3)

1 Determine whether an application failure occurred, and
whether a failover occurred.
3 Obtain the logs of the NAS OS and program products
and the core dump, and then send it to developers.
NAS07-710
NAS07-720 DKC515I
Application failure (failover Application failure in CHA.

provided)
Failure report
NAS management console: - NAS Blade Manager GUI
By checking NAS Blade (failure CHA report)
Manager GUI messages, etc., - SNMP server (failure CHA
determine whether an report)
application failure occurred.
NAS management console: Failover from failure CHA to

Check that failover from failure normal CHA
CHA to normal CHA has finished.
Phone, E-mail: Failover report

SIM,SNMP, E-mail: - NAS Blade Manager GUI
Recognize that failover has (normal CHA report)
and ordinary users of the
finished. - SNMP server (normal CHA
completion of failover and the
NAS Package location. report)
[Recognize that failover has finished]
[NAS Package location] - NAS message
Check CHA-xx (normal CHA report)
contact you, first look for the SIM code
displayed in the 'Browse - SVP(SIM code ac84x2)
ac84x2 issued when the failover started,
Cluster Status' window
and then look for the subsequent SIM
of NAS Blade Manager
code ac84xF to make sure that failover
GUI. Core dump is collected.
Determine that core dump is Failure CHA: Being activated.
already collected. Normal CHA: Operating
(performing the
operations of both
CL1-CHA and
CL2-CHA).
[NAS07-730]
NAS07-720
NAS07-730 DKC515I

To obtain the logs of NAS OS, PP,
and a core dump using the NAS
Blade Manager functionality.
E-mail, Postal service, Web site,

etc.:
Send the logs of NAS OS and PP
E-mail, Postal service, Web and the core dump to maintenance
site, etc.,: personnel for investigation.
Send core dump to developer
for investigation.
To developer

Delete core dump.
End
NAS07-730
NAS07-740 DKC515I
7.6.5 Application Failure in Something Other Than the Web Server (Failover Not Provided)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Core dump
User LU
Logs of User LU
NAS OS User LU
and PP
Figure 7.6-5 Application Failure in Something Other Than the Web Server
(Failover Not Provided) (1/3)

1 Determine whether an application failure
occurred.
2 Notify ordinary users of the failure. In case the failure affects user tasks.
3 Obtain the logs of the NAS OS and program
products and the core dump, and then send it to
developers.
NAS07-740
NAS07-750 DKC515I
Application failure in something other

than the Web server (failover not Application failure in CHA.
provided)
Failure report
Manager GUI messages, etc.,
determine whether an
application failure occurred.
Phone, E-mail:
SNMP, E-mail: Notify maintenance personnel
Recognize application failure. Core dump is collected.
of failure occurrence. If user
tasks are affected, notify
ordinary users of failure
occurrence.
NAS management console: Failure CHA: Operating (for

Determine that core dump is continuous operation).
already collected. Normal CHA: Operating.
[NAS07-760]
NAS07-750
NAS07-760 DKC515I

To obtain the logs of NAS OS
and PP and a core dump
using the NAS Blade
Manager functionality.
E-mail, Postal service, Web

site, etc.,:
Send the logs of NAS OS and
E-mail, Postal service, Web PP and the core dump to
site, etc.,: maintenance personnel for
Send core dump to developer investigation.
for investigation.
To developer

Delete core dump.
End
NAS07-760
NAS07-770 DKC515I
7.6.6 Application Failure in the Web Server (Failover Not Provided)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Logs of NAS
User LU
OS and PP
User LU
Core Dump User LU
Auto dump (Legend) : Monitoring each other : Failed part
Figure 7.6-6 Application Failure in the Web Server (Failover Not Provided) (1/3)

1 Determine whether the application failure
occurred in a Web server.
NAS07-770
NAS07-780 DKC515I
Application failure in the Web

server (failover not provided) Application failure in CHA
File service to users can NAS management console:

continue. NAS Blade Manager does not
Adjust failover time by operate.
consulting with customer.
SNMP, E-mail report: Phone, E-mail:

Recognize application Notify maintenance personnel
failure. of failure occurrence.
Failure CHA: Being activated

(for continuous
operation).
YES
Is failure CHA
stopped?

in 3.5.3 [NAS03-260].
Setup on SVP:
Start the NAS OS on failure CHA
[Start NAS OS]

See 3.5.8[2] [NAS03-820].
[NAS07-790]
NAS07-780
NAS07-790 DKC515I
SVP:
Obtain the detailed information
on the failure. See7.2.3
[NAS07-70]
SVP:
End
NAS07-790
NAS07-800 DKC515I
7.6.7 NAS OS Failure (In Start/Stop Processing)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
Logs of NAS
OS and PP User LU
User LU
Hibernation
dump User LU
Nas dump Auto dump

Figure 7.6-7 NAS OS Failure (In Start/Stop Processing) (1/3)

1 Determine whether there is any response from a The NAS OS is in the process of
NAS OS. starting or stopping.
NAS07-800
NAS07-810 DKC515I
NAS OS failure
(in start/stop processing)
Setup on SVP: Failure CHA: Being

Stop/start NAS OS. activated/stopped.
NAS OS no-response state in

failure CHA.
SVP, maintenance center:
Check that there is no No failure report
response from NAS OS. - SVP (MP report)
- Event trace produced
- SNMP server
Make sure that there is no
- NAS message (normal CHA
SIM about SVP failure or no
report)
message informing start or
stop of the NAS OS.
YES
Was any message
reported?
NO

Inform system administrators Recognize that NAS OS
that messages were not failure has occurred in NAS
issued. OS start/stop processing.
SVP:
Act on messages.

By checking SIM and ACC,
check whether a boot timeout Hibernation dump is collected.
or a shutdown timeout
occurred in the NAS OS.*1
1 *1 A timeout occurs:
- After 10∼30 minutes if NAS OS is booted.
[NAS07-820] - After 60 minutes if NAS OS is shut down.
NAS07-810
NAS07-820 DKC515I
SVP:
From the SIM code ac84x0 for
failover, identify the NAS
Package where a failover has
occurred.
SVP:
Obtain the detailed information
on the failure. See 7.2.3
[NAS07-70].
SVP:
End
NAS07-820
NAS07-830 DKC515I
7.6.8 Failure When a NAS OS LU is Full
CL1-CHA CL2-CHA
CHA reset Web server Auto failover
NAS OS kernel
NAS OS driver MP MP

Command Device
Core dump
User LU
User LU
User LU
Figure 7.6-8 Failure when NAS OS LU is full (1/4)

1 Determine whether the failure occurred in a Web server Depending on the available
when NAS OS LU is full. space and condition of the
NAS OS LU, reset might be
performed automatically by
the other CHA in the same
cluster, and then automatic
failover might occur.
2 Notify ordinary users of the failure in case the failure
affects user tasks.
3 Obtain an auto dump and send it to developers.
4 Perform the CHA reset, and then boot the CHA. Reset normally causes
automatic failover.
5 Ask system administrators to log in to the NAS If you cannot log in by using
management console and delete log files using the GUI, ask to log in via SSH
(RAS) management functionality. and delete the padding file.
6 Restart the NAS OS.
7 Perform failback.
NAS07-830
NAS07-840 DKC515I
Failure occurred in failure

Failure occurred when NAS
CHA when NAS OS LU is full.
OS LU is full.
File service to users cannot NAS management console: Failure report

continue. By using SNMP, recognize that - SNMP server (failure CHA
failure occurred when NAS OS report)
LU is full.
Impossible to log in to NAS
Blade Manager (KAQM15022-E
Error occurs).
SNMP, E-mail report:

Recognize that failure occurred Phone, E-mail:
when NAS OS LU is full. Notify maintenance personnel of
failure occurrence.
failure in case the failure affects
Setup on SVP: user tasks.
Obtain auto dump.
Auto dump is obtained.
[Obtain auto dump]
See [SVP02-540].
Setup on SVP: To developer

Reset the CHA, and then boot
the CHA.
Auto failover from failure CHA to
[Reset and boot CHA] normal CHA
See 3.5.8 [3] [NAS03-880],
[NAS03-820]. Boot failureCHA
Setup on SVP:
Check that CHA boot has
finished.
[Finish the NAS OS boot]

The ENS3541i message
appears.
Ask system administrators to NAS management console:
delete log files. Log in to failure CHA GUI.
[NAS07-850]
NAS07-840
NAS07-850 DKC515I
NO
Has the
login been
completed?
YES
NAS Management Console Failure CHA: NAS OS running

(failure CHA): Normal CHA: Operating
Delete log and core files using (Performing the operations of both
the (RAS) management CL1-CHA and CL2-CHA)
functionality.
YES
Has the
deletion been
completed?
NO
NAS Management Console

(failure CHA):
Log in via SSH and delete the
padding file under
/home/nasroot/.padding.
NAS Management Console

(failure CHA):
Log in again via GUI, and delete
log and core files using the
(RAS) management functionality.

Restart the NAS OS of the failure Ask the maintenance personnel
CHA. to restart the NAS OS of the
failure CHA.

Inform the system administrator Recognize that the NAS OS on
that the NAS OS of the failure the failure CHA has been
CHA has been rebooted and ask rebooted.
to start the node of the failure
CHA.
(NAS07-851)
NAS07-850
NAS07-851 DKC515I
NAS Management Console Failure CHA: NAS OS running

(failure recovery CHA): Normal CHA: Operating
Start the node on failure recovery (Performing the operations of the
CHA. both CL1-CHA and CL2-CHA)
NAS Management Console manual failing back from normal CHA

(failure recovery CHA): to failure recovery CHA
Perform a manual failback from
normal CHA to failure recovery
CHA.

Acknowledge that the failback has Notify maintenance personnel CL2-CHA: Operating
been completed. and ordinary users of the
recovery.
End
NAS07-851
NAS07-860 DKC515I
7.6.9 NAS OS File System Failure
CL1-CHA CL2-CHA
Web server
NAS CM LU for backup
NAS OS kernel NAS CM LU for backup
NAS OS driver MP MP

Command Device
Logs of NAS
OS and PP User LU
User LU
User LU
Auto dump
Figure 7.6-9 NAS OS File System Failure (1/4)

1 Determine whether NAS OS file system
failure occurred.
2 Check that the failover has completed.
3 Reset and boot the CHA.
4 Determine whether NAS OS file system Go to step 5 if the file system has recovered from
has recovered from the failure. the failure.
Go to step 5a if the file system has not recovered
from the failure.
5 Obtain the auto dump and send it to
developers.
6 Perform failback.
NAS07-860
NAS07-870 DKC515I
Procedure when the file system has not recovered from the failure by CHA reset and boot
5a Stop NAS Package by resetting CHA.
6 Install NAS OS. After the expansion installation, recover from the
failure by upgrading the NAS OS to the version at
the time of failure occurrence.
7 Install NAS Blade Manager and optional Upgrade to the version at the time of failure
program products. occurrence.
8 Set up the network information (fixed IP Use the settings that were used at the time of failure
address, NTP). occurrence.
9 Restore the NAS OS LU. Do so only if the backup data of the NAS OS LU
already exists.
10 Start the NAS OS.
11 Obtain auto dump and send it to
developers.
12 Perform failback.
NAS07-870
NAS07-880 DKC515I
NAS OS File System Failure

Failing over from failure CHA to
normal CHA
Failure CHA: Running
SVP/maintenance center: Normal CHA: Operating
By checking SIM, ACC and (Performing the operations of
SSB, determine whether a both CL1-CHA and CL2-CHA)
Failure report
- SVP (failure CHA MP report)
SVP:
By the SIM code ac88x2,
specify the NAS Package
where the failure has occurred.
Setup on SVP:
Perform the CHA reset and
boot.
[Reset and boot CHA]
See 3.5.9 [NAS03-880],
3.5.8[3] [NAS03-840].
Setup on SVP:
Check that CHA boot has
finished.
[Finish the NAS OS boot]
The ENS3541i message
appears.
NO
Has CHA boot
finished? 1
YES [NAS07-890]
SVP:
the failure. See 7.2.3 [NAS07-70]
SVP:
investigate the dump for a
End
NAS07-880
NAS07-890 DKC515I
1
normal CHA
SVP/maintenance center: Failure CHA: Running
By checking SIM, ACC and SSB, determine Normal CHA: Operating
whether a hardware failure occurred.
(Performing the operations of
both CL1-CHA and CL2-CHA)
SVP:
By the SIM code ac88x2, specify the NAS Failure report
Package where the failure has occurred. - SVP (failure CHA MP report)
Setup on SVP: Perform the CHA reset

[Reset CHA] See 3.5.9 [NAS03-880].
Setup on SVP:
Perform NAS OS expansion installation on failure CHA. *1
[NAS OS expansion installation]
See 3.5.4 [2] [NAS03-400]
Setup on SVP:
Install NAS Blade Manager on failure CHA.
[NAS Blade Manager installation]
See 3.5.4 [2] [NAS03-400]
Setup on SVP:
Install optional program products on failure CHA. *1
[Optional program product Installation]
See 3.5.4 [3] [NAS03-490].
Setup on SVP:
Set up the network settings (fixed IP address, NTP).
[Set up the network settings (fixed IP address, NTP)]
See 3.5.6 [NAS03-620]
Setup on SVP: Provided that the NAS OS LU is backed up when it is to be
Restore the NAS OS LU. updated.
If restoration is aborted with the error ENS3556E, take one
of the following actions according to the error code.
0x01000002:
NAS Blade Manager is not installed. Start the restoration
procedure over.
0x01000008 or 0x01000060:
The network configuration is incorrect. Check the
configuration and start the restoration procedure over.
[Restore NAS OS LU]

See 3.5.12[NAS03-990].
2 *1 After the expansion installation, recover from the

[NAS07-891] the time of failure occurrence.
NAS07-890
NAS07-891 DKC515I
Setup on SVP: Restart the NAS OS even if the

Restart NAS OS on failure CHA. NAS OS status is ACTIVE.
[Restart NAS OS]
See 3.5.8 [3] [NAS03-840]
SVP: Obtain the detailed
information on the failure. See
7.2.3 [NAS07-70]
SVP: Send the detailed

information to the developer and
request to investigate the dump
for a primary scan.
To developer
End *1 After the expansion installation, recover from the

NAS07-891
NAS07-900 DKC515I
7.6.10 NAS OS Failure During Startup or Stop (Invalid Dump LU)

User LU
User LU
Pentium Pentium

MP MP MP MP

SVP
Backup
Figure 7.6-10 NAS OS Failure During Startup or Stop (Invalid Dump LU) (1/2)

1 Determine whether the content of the
dump LU was invalid while starting or
stopping NAS OS.
2 Start NAS OS. Execute if the failure occurred while NAS OS is
stopped.
3 Backup NAS OS LU in the same cluster
as the failure CHA.
NAS07-900
NAS07-910 DKC515I
NAS OS failure during startup or

stop (invalid dump LU)
SVP/maintenance center: Failure CHA: NAS OS

By checking SIM, ACC, and Starting or Stopping
SSB, determine whether a Normal CHA: Operating
SVP: Failure report

By the SIM code ac88xa, - SVP (CL1-CHA MP report)
specify the NAS Package - SVP(SIM code ac88xa)
where the failure has occurred. subcode (0x00020002)
YES
Has NAS OS of failure CHA
stopped?
NO [Has NAS OS stopped?]

See 3.5.3 [NAS03-260] in
the ‘Main’ window.
Setup on SVP:
Restart NAS OS on failure CHA.
[Start NAS OS]

See 3.5.8 [2] [NAS03-820]. CL1-CHA: Operating
CL2-CHA: Operating

Ask the system administrator Back up NAS OS LU which is
to backup NAS OS LU which in the same cluster as the
is in the same cluster as the failure CHA.
failure CHA.

Acknowledge that the backup Report that the backup of NAS
of NAS OS LU has completed. OS LU has completed.
End
Figure 7.6-10 NAS OS Failure During Startup or Stop (Invalid Dump LU) (2/2)
NAS07-910
NAS07-920 DKC515I
7.6.11 NAS OS Failure During Startup or Stop (Unable to Connect NTP Server)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
User LU
User LU
User LU
Figure 7.6-11 NAS OS Failure During Startup or Stop (Unable to Connect NTP
Server) (1/4)

1 Determine whether the NTP server can be
connected while starting or stopping NAS OS.
2 Check the NTP server settings and network
configuration, and then change them if
necessary.
3 Restart NAS OS.
NAS07-920
NAS07-930 DKC515I
NAS OS failure during startup or

stop (unable to connect NTP server)
SVP/maintenance center: Failure CHA: Starting

By checking SIM, ACC, and Normal CHA: Operating
SSB, determine whether a
SVP: Failure report

By the SIM code ac88xa, specify - SVP (CL1-CHA MP report)
the NAS Package where the - SVP(SIM code ac88xa)
failure has occurred. subcode (0x00030001)
NO [Is IP address correct?]

Is the IP address for See 3.5.6 [1] (2)
NTP server set [NAS03-630] in the ‘Setting’
correctly? window
YES Setup on SVP:

Correct the IP address for the
NTP server.
2 [NAS07-950]
Phone, E-mail:
Ask the system administrator to
check the network configuration
for the NTP server.
NO
Is GbE switch connected
correctly?
GbE switch:
YES
Connect GbE switch correctly.
2 [NAS07-950]
NO
Has NTP server started?
YES NTP server:

Start NTP server.
1 [NAS07-940] 2 [NAS07-950]
Server) (2/4)
NAS07-930
NAS07-940 DKC515I

1 Normal CHA: Operating
GbE switch:
Check if it can communicate within
90 seconds after NAS Package is
linked up via GbE port.
NO
Able to
communicate in
90 seconds?
GbE switch:
Change settings for GbE switch
YES so that it can communicate within
90 seconds.
Network:
Check if the network can
communicate with NTP server at 2
least once per second (ping
response from NTP server within [NAS07-950]
1 second after the request).
Able to NO
communicate
in 1 second?
YES Network:
Change GbE switch settings so
that the network can communicate
within 1 second.
Phone, E-mail: Phone, E-mail: 2

Request an investigation to Contact maintenance personnel
developers. to ask developers to investigate
the problem. [NAS07-950]
END
Server) (3/4)
NAS07-940
NAS07-950 DKC515I

2 Normal CHA: Operating
Setup on SVP: Phone, E-mail: Failure CHA: Restarting

Restart NAS OS of failure Ask maintenance personnel to Normal CHA: Operating
CHA. restart NAS OS of failure CHA.
[Restart NAS OS] CL1-CHA: Operating
See 3.5.8[3] [NAS03-840]. CL2-CHA: Operating
END
Server) (4/4)
NAS07-950
NAS07-960 DKC515I
7.6.12 NAS OS Application Failure (Unable to Set Internal IP Address)
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

Command Device
NAS OS,
PP log User LU
User LU
User LU

Auto Dump
Figure 7.6-12 NAS OS Application Failure (Unable to Set Internal IP Address) (1/5)

1 Determine whether the internal IP address can be set.
2 Ask the system administrator to acquire all the log
data by using error information management
functionality of NAS Blade Manager and to request
an investigation to the developer.
3 Set the IP address back to the one before the change,
collect detailed information, and send it to the
developer.
4 Reset the internal IP address to the new IP address.
5 Perform failover.
6 Restart NAS OS.
7 Perform failback.
NAS07-960
NAS07-970 DKC515I
NAS OS Application Failure (Unable to Set Internal IP Address)
Failure report
SVP/maintenance center:
- SVP (CL1-CHA MP report)
By checking SIM, ACC and SSB,
-SVP(SIM code ac84x0)
determine whether a hardware
Error Code(1ad5, 1ad6, 1ad7)
failure occurred.
- SVP (CL1-CHA NAS OS report)
-SVP(SIM code ac88x3)
SVP:
By the SIM code (ac84x0, ac88x3), Failure CHA: Operating
specify the NAS Package where Normal CHA: Operating
the failure has occurred.

Ask the system administrator to use Use NAS Blade Manager error
NAS Blade Manager error information management
information management functionality to collect all the log
functionality to acquire all the log data.
data and to request an investigation
to the developer.

Acknowledge that the collection of Notify the maintenance personnel
all the log data has been that the collection of all the log
completed. data has been completed.
SVP: Phone, E-mail, etc.:

Set the internal IP address back to Send the developer all the log data
the one set before. and ask for a primary scan.
[Set internal IP address]
See [INST05-60]. To developer
SVP:
Collect detailed information on the
failure. See 7.2.3 [NAS07-70].
[NAS07-980]
NAS07-970
NAS07-980 DKC515I
NO
Information collection
ended successfully?
YES [Information collection

ended successfully]
See [SVP02-540]. Phone, E-mail:
Ask the developer for a primary
SVP: scan.
Send error information and ask the
developer for a primary scan. To developer
To developer
SVP:
Reset the internal IP address to the
new IP address.
[Set internal IP address]
See [INST05-60].
YES
Is the internal IP
address set
correctly?
NO [Is the internal IP
address set correctly?]
Setup on SVP
functions correctly
without communication
error [ENS3514E].
2
[NAS07-1000]
Phone, E-mail: Phone, E-mail: Failure CHA: Operating
Inform the system administrator Notify ordinary users that failover Normal CHA: Operating
of the location of NAS Package is to be performed and acquire
on which failover is to be permission.
performed, and ask her to
perform failover and stop the
failure CHA node.
[NAS07-990]
NAS07-980
NAS07-990 DKC515I
Perform failover from failure CHA

to normal CHA.
functionality to perform failover Failover report
from failure CHA to normal CHA - NAS Blade Manager GUI
and check the completion of (normal CHA report)
failover. - syslog (normal CHA report)

functionality to stop the failure
CHA node.
Phone, E-mail: Failure CHA: Running

Notify maintenance personnel Normal CHA: Operating
Phone, E-mail: and ordinary users of the (Performing the operations of
Acknowledge that the failover is completion of failover and the both CL1-CHA and CL2-CHA)
completed and the failure CHA location of NAS Package on
node has stopped. which the failover is performed.
[Acknowledge that the node has [NAS Package Location]
stopped] Check CHA-xx displayed in
Confirm that the NAS Package Browse Cluster Status
status is INACTIVE in the ‘Main’ window in NAS Blade
window. See 3.5.3 [NAS03-260]. Manager.
Phone, E-mail: Failure CHA: Restarting
Reboot the NAS OS of failure NAS Management Console: Normal CHA: Operating
CHA. Monitor the operation of normal (Performing the operations of
CHA. both CL1-CHA and CL2-CHA)
[Reboot NAS OS]
See 3.5.8 [3][NAS03-840].

Inform the system administrator Notify ordinary users that failover
of the location of NAS Package is to be performed and acquire
on which failback is to be permission.
performed, and ask her to
perform failback.
[NAS07-1000]
NAS07-990
NAS07-1000 DKC515I

functionality to start the failure
CHA node. Failure recovery CHA: Running
NAS Management Console: both CL1-CHA and CL2-CHA)
functionality to perform failback Failing back from normal CHA to
from normal CHA to failure failure recovery CHA
recovery CHA and check the
completion of failback. Failback report
(failure recovery CHA report)
- syslog (failure recovery CHA
Phone, E-mail:
report)
Phone, E-mail: and ordinary users of the
Acknowledge that the failback is completion of failback and the
completed and the failure recovery location of NAS Package on CL1-CHA: Operating
CHA node has started. which the failback is performed. CL2-CHA: Operating
node has started]
Package status is ACTIVE
3.5.3 [NAS03-260].
No
Is internal IP address set
correctly?
Yes [Is internal IP address set correctly?]

Setup on SVP functions correctly
without communication errors
[ENS3514E].
Phone, E-mail:
Request an investigation to the
developer.
2 To developer
End
NAS07-1000
NAS07-1001 DKC515I
7.6.13 Failure During NAS Dump Collection
CL1-CHA CL2-CHA
Web server
NAS OS driver MP MP

NAS Command Device

Dump
User LU
User LU
User LU
Figure 7.6-13 Failure During NAS Dump Collection (1/2)

1 Determine that the NAS Dump is not collected. NAS Dump is not collected for
NAS OS failure or in the
operation of hibernation dump
collection.
2 Acquire detailed information and request an Collect auto dump.
investigation to the developer.
NAS07-1001
NAS07-1002 DKC515I
Failure During NAS Dump Collection
SVP/maintenance center: Failure CHA: Stopped by failure*1

By checking SIM, ACC and SSB, Normal CHA: Operating
determine whether failure during (Performing the operations of both
NAS Dump collection occurred. CL1-CHA and CL2-CHA)
Collection and acquisition of NAS
Dump
SVP:
By the SIM code (ac88x3), specify Failure report
the NAS Package where the failure - SVP(SIM code ac88x3)
has occurred. Subcode(0x06xxxxxx)
Failure CHA: Stopped

SVP: Normal CHA: Operating
Collect detailed information on the (Performing the operations of
failure. See 7.2.3 [NAS07-70]. both CL1-CHA and CL2-CHA)
SVP:
Send the developer all the log data
and ask for a primary scan.
To developer
END
*1: NAS Dump is collected due to NAS OS failure or the operation

of hibernation dump collection from Setup on SVP.
Figure 7.6-13 Failure During NAS Dump Collection (2/2)
NAS07-1002
NAS07-1003 DKC515I
7.6.14 NAS Cluster Management LU Failure (in NAS OS Start/Stop Processing)
CL2-CHA NAS CM LU for backup

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-14 NAS Cluster Management LU Failure (in NAS OS Start/Stop

Processing) (1/3)

1 Confirm that NAS cluster management LU failure
has occurred.
data by using the error information management
function of NAS Blade Manager and to request an
3 Acquire detailed information and send it to the
developer.
4 Disable automatic save for NAS OS LUs and NAS
cluster management LUs.
NAS07-1003
NAS07-1004 DKC515I
NAS Cluster Management LU Failure

(in NAS OS Start/Stop Processing)
SVP/maintenance center: Failure report

By checking SIM, ACC and SSB, - SVP (CL1-CHA MP report)
determine whether a NAS cluster -SVP (SIM code: ac84x4)
management LU failure occurred. Error Code (1b31)
SVP: Failure CHA: Service stopped

By the SIM code (ac84x4), specify Normal CHA: Operating
the NAS Package where the failure
has occurred.

to the developer.

Phone, E-mail, etc.:

SVP: and ask for a primary scan.
Collect detailed information.
See 7.2.3 [NAS07-70].
To developer

To developer
[NAS07-1004A]

Processing) (2/3)
NAS07-1004
NAS07-1004A DKC515I

check the automatic save functionality to check the automatic
settings of the NAS OS LU and save settings of the NAS OS LU
NAS cluster management LU. and NAS cluster management LU.
YES
Are the automatic
save settings
enabled?
NO Use NAS Blade Manager functionality to
disable the automatic save settings of the NAS
OS LU and NAS cluster management LU.

Confirm that the automatic save Notify the maintenance
of the NAS OS LU and NAS personnel of the automatic save
cluster management LU is settings of the NAS OS LU and
disabled. NAS cluster management LU.
Follow the developer’s instruction when

END performing failure recovery procedures
such as replacement operation

Processing) (3/3)
NAS07-1004A
NAS07-1005 DKC515I
7.6.15 Failure in Preliminary Processing for NFS Share (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-15 Failure in Preliminary Processing for NFS Share (in NAS OS
Start/Stop Processing) (1/4)

1 Confirm that failure in preliminary processing for
NFS share has occurred.
developer.
4 Ask the system administrator to perform corrective
action to start service.
5 Check if the service is started.
NAS07-1005
NAS07-1006 DKC515I
Failure in Preliminary Processing for NFS

Share (in NAS OS Start/Stop Processing)

determine whether a failure in preliminary -SVP (SIM code: ac84x5)
processing for NFS share occurred. Error Code (1b32)

has occurred.

to the developer.


See 7.2.3 [NAS07-70].
To developer
SVP:
To developer
[NAS07-1007]
NAS07-1006
NAS07-1007 DKC515I

Phone, E-mail: Check if the resource group of
Ask the system administrator to failure CHA has been started on the
use the cluster management remote node, using the cluster
functionality of NAS Blade management function of NAS
Manager to perform corrective Blade Manager.
action for failure preliminary
processing for NFS share.
Has YES
service been started
on the remote node?
NO
NAS Management Console: NAS Management Console:

Perform forced stop for the Fail back the resource group
resource group on the failure CHA that was moved to the remote
and then to restart it using the node using the cluster
cluster management function of management function of NAS
NAS Blade Manager. Blade Manager.
YES Is service resumed

3 on local node?
[NAS07-1008] NO
Phone, E-mail:
Notify the users and get the users’
permission to stop the service.

Stop the cluster after performing
the forced stop of the resource
group on the failure CHA.
Phone, E-mail:
Setup on SVP:
Restart the NAS OSs on the
restart the NAS OS on the both
both CHA.
CHA.
[Reboot NAS OS]
See 3.5.8 [3][NAS03-840].
2
[NAS07-1008]
NAS07-1007
NAS07-1008 DKC515I
Phone, E-mail: Phone, E-mail: Failure CHA: Restarted

Notify the system administrator Confirm that the NAS OSs on the Normal CHA: Operating
that the NAS OSs on the both both CHA are restarted. (Performing the operations of
CHA are restarted. both CL1-CHA and CL2-CHA)

Use the cluster management
function of NAS Blade Manager to
restart the cluster, and then to start
the resource group on the failure
CHA.
YES
Is service
resumed?
NO
Phone, E-mail: Failure CHA: Stopped

Phone, E-mail:
Notify that the corrective action for Normal CHA: Operating
Confirm that the corrective action
the failure in preliminary (Performing the operations of
failed.
processing for NFS share failed.. both CL1-CHA and CL2-CHA)

END Notify the developer that the
restart of the resource group and
cluster failed.
To developer
Phone, E-mail: Failure CHA: NAS OS running

Phone, E-mail: Notify that the corrective action for Normal CHA: Operating
Confirm that the corrective the failure in preliminary (Performing the operations of
action is completed. processing for NFS share is both CL1-CHA and CL2-CHA)
completed.
END NAS management console:

Monitor the normal CHA operation.
NAS07-1008
NAS07-1009 DKC515I
7.6.16 User LU Failure (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-16 User LU Failure (in NAS OS Start/Stop Processing) (1/3)

1 Confirm that user LU failure has occurred.
developer.
NAS07-1009
NAS07-1009A DKC515I
User LU Failure (in NAS OS Start/Stop

Processing)

determine whether a user LU failure -SVP (SIM code: ac84x6)
occurred. Error Code (1b33)

has occurred.

Ask the system administrator to use Use the error information
the error information management management function of NAS
function of NAS Blade Manager to Blade Manager to collect all the log
acquire all the log data and to data.
request an investigation to the
developer.


See 7.2.3 [NAS07-70].
To developer
SVP:
To developer
[NAS07-1009B]
NAS07-1009A
NAS07-1009B DKC515I

Use the error information
Phone, E-mail: management functionality of NAS
Notify the system administrator Blade Manager to pick out the
that the failure in user LU message KAQG72006-E or
operation occurred and the time KAQG72009-E that was issued
that the SIM (ac84x6) occurred. around the time the SIM (ac84x6)
occurred and to identify the file
system form the message text.

Perform the recovery procedure
explained for KAQG72006-E or
KAQG72009-E in 10.2 in NAS
Blade Manager User’s Guide
NO
Is service
resumed?
YES

Confirm that the corrective the user LU failure has been (Performing the operations of
action has been completed. completed. both CL1-CHA and CL2-CHA)

END Monitor the normal CHA operation.
Phone, E-mail: Phone, E-mail: Failure CHA: Stopped

Confirm that the corrective action Notify that the corrective action for Normal CHA: Operating
failed. the user LU failure failed.. (Performing the operations of

recovery procedure that is
explained in the message failed.
To developer
NAS07-1009B
NAS07-1009C DKC515I
7.6.17 Failure in Setting or Releasing NFS Share (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-17 Failure in Setting or Releasing NFS Share(in NAS OS Start/Stop

Processing) (1/3)

1 Confirm that failure in setting or releasing NFS share
has occurred.
developer.
NAS07-1009C
NAS07-1009D DKC515I
Failure in Setting or Releasing NFS Share

(in NAS OS Start/Stop Processing)

determine whether a failure in setting or -SVP (SIM code: ac84x7)
releasing NFS share occurred. Error Code (1b34)

has occurred.

to the developer.


See 7.2.3 [NAS07-70]
To developer
SVP:
To developer
[NAS07-1009E]

Processing) (2/3)
NAS07-1009D
NAS07-1009E DKC515I

Ask the system administrator to Notify the users and get permission to
perform corrective action for failure in stop the service on the both CHA.
setting or releasing NFS share, using
the cluster management function of
NAS Blade Manager. NAS management console:
Perform forced stop for the resource
group on the failure CHA, and then stop
the cluster using the cluster management

Restart the NAS OSs on the both CHA. Ask maintenance personnel to restart the
NAS OSs on the both CHA.
[Reboot NAS OS]
See 3.5.8 [3][NAS03-840].
Phone, E-mail: Failure CHA: Restarting

Phone, E-mail:
Notify the system administrator that the Normal CHA: Operating
Confirm that the NAS OSs on the both
NAS OSs on the both CHA has been CHA has been restarted.
restarted. both CL1-CHA and CL2-CHA)

Start the cluster and then the resource group
on the failure CHA using the cluster
management function of NAS Blade Manger.
NO
Is service
resumed?
YES
Phone, E-mail: Phone, E-mail: Failure CHA: NAS OS running

Confirm that the corrective Notify that the corrective action for the Normal CHA: Operating
action has been completed. failure in setting or releasing an NFS (Performing the operations of
share has been completed. both CL1-CHA and CL2-CHA)


Confirm that the corrective action Notify that the corrective action for the Normal CHA: Operating
failed. user LU failure failed.. (Performing the operations of

END Notify the developer that the recovery
procedure that is explained in the
message failed. To developer

Processing) (3/3)
NAS07-1009E
NAS07-1009F DKC515I
7.6.18 Service IP Up/Down Failure (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-18 Service IP Up/Down Failure (in NAS OS Start/Stop Processing) (1/4)

1 Confirm that service IP up/down failure has occurred.
data by using error information management
functionality of NAS Blade Manager. If you cannot
recover by performing step 3, request an investigation
to the developer.
developer.
4 Work with the system administrator to perform
corrective action for the service IP up/down failure.
NAS07-1009F
NAS07-1009G DKC515I
Service IP Up/Down Failure (in

NAS OS Start/Stop Processing)

determine whether a service IP -SVP (SIM code: ac84x8)
up/down failure occurred. Error Code (1b33)

has occurred.

acquire all the log data and to data.
request an investigation to the
developer.

SVP:
7.2.3 [NAS07-70]

Notify the system administrator Pick out the KAQG72007-E
that service IP up/down failure message that was issued around
occurred and of the time that the the time the SIM (ac84x8) occurred
SIM (ac84x8) occurred, and ask to using the error management
identify the failed port. function of NAS Blade Manager and
identify the failed service IP
address from the message text.
[NAS07-1009H]
NAS07-1009G
NAS07-1009H DKC515I

Identify the port that has the failed
service IP address and its real IP
2
address using the system
configuration function of NAS
Blade Manager.
SVP:
Check if the failed port link is up in Phone, E-mail:
Port Status in the System Notify the maintenance personnel
Equipment window of Web of the failed port and its real IP
Console. address.

Yes Perform the recovery procedure
Is the port link up? explained for KAQG72007-E in
Chapter 3 in NAS Blade Error
Codes.
No
NAS frame:
Check the connection of LAN
cables and the network 3
equipment.
[NAS07-1009I]
Was the Yes

failure caused by the
LAN cable or network
equipment?
No Could you Yes

remedy the failure in the
LAN cable or network
equipment?
No
2
[NAS07-1009H]
Phone, E-mail:
Send the developer the error
information that you collected and
ask for an investigation.
To developer
END
NAS07-1009H
NAS07-1009I DKC515I
NO
Is service
resumed?
YES

Confirm that the corrective the service IP up/down failure has (Performing the operations of
action has been completed. been completed. both CL1-CHA and CL2-CHA)

END Monitor the normal CHA operation.

failed. the service IP up/down failure (Performing the operations of
failed.. both CL1-CHA and CL2-CHA)

END
information that you collected and
ask for an investigation.
To developer
NAS07-1009I
NAS07-1009J DKC515I
7.6.19 Failure in Setting or Releasing CIFS (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-19 Failure in Setting or Releasing CIFS (in NAS OS Start/Stop

Processing) (1/4)

1 Confirm that CIFS failure has occurred.
developer.
action to start the service.
NAS07-1009J
NAS07-1009K DKC515I
Failure in Setting or Releasing CIFS (in

NAS OS Start/Stop Processing)

determine whether a CIFS failure -SVP (SIM code: ac84x9)
occurred. Error Code (1b36)

has occurred.

acquire all the log data. data.

SVP:
See 7.2.3 [NAS07-70].

Ask the system administrator to Perform forced stop for the
take corrective action for the CIFS resource group of the failed CHA
failure using the cluster using the cluster management
management function, service function of NAS Blade Manager.
management function, and file
sharing management function of
NAS Blade Manager.
[NAS07-1009L]

Processing) (2/4)
NAS07-1009K
NAS07-1009L DKC515I

Check if the CIFS configuration is
set correctly using the file sharing
configuration management function
of NAS Blade Manager.
YES
Is the CIFS
configuration correct?
NO
NAS Management Console: Phone, E-mail:
Correct the CIFS configuration Send the developer all log data
using the file sharing configuration and ask for an investigation.
management function of NAS
Blade Manager.
To developer

Start the resource group using the
cluster management function of
NAS Blade Manager.
Is service YES
resumed? 3
NO
[NAS07-1009M]
Phone, E-mail:
permission to stop the service on
the both CHA.
NAS management console: Failure CHA: Restarting

Perform the forced stop for the Normal CHA: Operating
resource group on the failure (Performing the operations of
CHA , and then stop the cluster. both CL1-CHA and CL2-CHA)
[NAS07-1009M]

Processing) (3/4)
NAS07-1009L
NAS07-1009M DKC515I

Restart the NAS OSs on the both Ask the maintenance personnel to
CHA. restart the NAS OSs on the both
CHA.
[Reboot NAS OS]
See 3.5.8 [3][NAS03-840].
Notify the system administrator Acknowledge that the NAS OSs on
the both CHA has been restarted.
that the NAS OSs on the both CHA
has been restarted.

Start the cluster and then start the
resource group on the failed CHA
YES
Is service
resumed?
NO

failed. the CIFS failure failed. (Performing the operations of

restart of the resource group and
cluster failed.
To developer

Confirm that the corrective the CIFS failure has been (Performing the operations of
action has been completed. completed. both CL1-CHA and CL2-CHA)


Processing) (4/4)
NAS07-1009M
NAS07-1009N DKC515I
7.6.20 NAS OS or Application Failure (in NAS OS Start/Stop Processing)

CL1-CHA
Web server

NAS OS kernel
NAS OS driver MP MP
Command Device
User LU
NAS OS,
PP log User LU
User LU

Auto Dump
Figure 7.6-20 NAS OS or Application Failure (in NAS OS Start/Stop Processing)

(1/4)

1 Confirm that NAS OS or application failure has
occurred.
data by using error information management function
of NAS Blade Manager and ask the developer for an
investigation.
developer.
action to start the service.
NAS07-1009N
NAS07-1009O DKC515I
NAS OS or application failure (in

NAS OS start/stop processing)

determine whether a NAS OS or -SVP (SIM code: ac84xB)
application failure occurred. Error Code (1b37)

By the SIM code (ac84xB), specify Normal CHA: Operating
has occurred.

Ask the system administrator to Use the error information
acquire all the log data using the management function of NAS
error information management Blade Manager to collect all the log
function of NAS Blade Manager. data.

Phone, E-mail:
SVP: Send the developer all the log data
Collect detailed information. and ask for a primary scan.
See 7.2.3 [NAS07-70] To developer
SVP:
information and ask for an primary
scan.
To developer
[NAS07-1009P]

(2/4)
NAS07-1009O
NAS07-1009P DKC515I

Ask the system administrator to Check if the resource group of
perform corrective action for failure CHA has been started on the
NAS OS or application failure remote node, using the cluster
using the cluster management management function of NAS
function of NAS Blade Manager. Blade Manager.
Has YES
service been started on
the remote node?
NO
NAS Management Console: NAS Management Console:
Use the cluster management Fail back the resource group that
function of NAS Blade Manager to was moved to the remote node
perform forced stop the resource using the cluster management
group on the failed CHA and then function of NAS Blade Manager.
to restart it.
YES Is service
3 resumed?
[NAS07-1009Q] NO
Phone, E-mail:
permission to stop the service on
the both CHA.

Perform the forced stop for the
resource group on the failure CHA
stop the cluster.
[NAS07-1009Q]

(3/4)
NAS07-1009P
NAS07-1009Q DKC515I
Phone, E-mail: Failure CHA: Restarted

Setup on SVP: Normal CHA: Restarted
Restart the NAS OSs on the
restart the NAS OS on the both
both CHA.
CHA.
[Reboot NAS OS]
See 3.5.8 [3][NAS03-840].
Notify the system administrator Confirm that the NAS OSs on the
that the NAS OSs on the both both CHA have been restarted.
CHA have been restarted.

Start the cluster, and then start the
resource group on the failed CHA
YES
Is service
resumed?
NO

failed. the NAS OS or application failure (Performing the operations of
failed.. both CL1-CHA and CL2-CHA)

recovery by restarting the cluster
failed.
To developer

Confirm that the corrective the NAS OS or application failure (Performing the operations of
action has been completed. has been completed. both CL1-CHA and CL2-CHA)
END NAS Management Console:


(4/4)
NAS07-1009Q
NAS07-1009R DKC515I
7.6.21 File System for a User LU is Blocked

CL1-CHA
Web server Manual failover

NAS OS kernel
NAS OS driver MP MP
Command Device
NAS OS, User LU

PP log
User LU
Hibernation User LU
Event
trace dump

Auto Dump NAS Dump
Figure 7.6-21 File System for a User LU is Blocked (1/8)

1 Confirm that a blockage occurred for a file system for
a user LU.
2 Perform hibernation dump collection manually.
3 Confirm that the failover finished.
developer.
5 Perform a failback.
6 Delete the failed file system.
7 Perform a failover.
8 Restart the NAS OS. Restart the failed CHA.
10 Perform a failover.
11 Restart the NAS OS. Restart the normal CHA.
13 Re-create and restore the failed file system.
NAS07-1009R
NAS07-1009S DKC515I
File system for a user LU is

blocked
User LU file system is blocked
SVP/maintenance center: NAS Management Console, Failure report

By checking SIM, ACC, and SSB, maintenance server: - SVP (CL1-CHA MP report)
confirm that a user LU file system Recognize the blockage for a file - SVP (SIM code: ac88x2)
failure occurred. system for a user LU from NAS - NAS Blade Manager GUI
Blade Manager and SNMP (Failure CHA report)
message report. - SNMP server
(Failure CHA report)
SVP:
By the SIM code (ac8xx2), identify NAS Management Console,
maintenance server: Failure CHA: Target service
the NAS Package where the failure stopped
has occurred. Identify the failed file system from
NAS Blade Manager and SNMP Normal CHA: Operating
message report.

Recognize the failed file system. Notify the failed file system of
maintenance personnel.
Failover from the failure CHA to

the normal CHA
SVP:
Collect hibernation dump.
See 3.5.10 [1] [NAS03-910] Failover report
(Normal CHA report)
- SNMP server
SVP: (Normal CHA report)
Collect detailed information. - syslog (Normal CHA report)
See 7.2.3 [NAS07-70] - System message
(Normal CHA report)
- SVP (SIM code: ac84x2)
SVP:
Send the developer the detailed
(Performing the both operations
information and ask for an primary of CL1-CHA and CL2-CHA)
scan.
To developer
[NAS07-1009T]
NAS07-1009S
NAS07-1009T DKC515I
1 Periodical backup of the

file system is required.
Phone, E-mail:
Phone, E-mail: Notify ordinary users that a failback Failure CHA: NAS OS running
Ask the system administrator to will be performed and the failed file Normal CHA: Operating
perform a failback and restore the system will be restored and ask (Performing the both operations
failed file system. them to stop tasks involving the file of CL1-CHA and CL2-CHA)
system.

Perform a failback from the normal Failing back from the normal CHA
CHA to the failure recovery CHA to the failure recovery CHA
using NAS Blade Manager, and
confirm that the failback finished.
Failback report
(Failure recovery CHA report)
- syslog
(Failure recovery CHA report)
Failure CHA: Target service

NAS Management Console: stopped
Delete the file shares (NFS, CIFS) Normal CHA: Operating
for the failed file system using NAS
Blade Manager.

Delete the failed file system using
NAS Blade Manager.
[NAS07-1009T1]
NAS07-1009T
NAS07-1009T1 DKC515I
Phone, E-mail: Failure CHA: Target service

Notify ordinary users that failover stopped
is to be performed and acquire Normal CHA: Operating
permission.

Perform failover from failure CHA
Use NAS Blade Manager to normal CHA.
functionality to perform failover
from failure CHA to normal CHA
and check the completion of Failover report
failover. - NAS Blade Manager GUI
(normal CHA report)
functionality to stop the failure
CHA node.
Phone, E-mail: Failure CHA: Target service

Notify maintenance personnel stopped
Setup on SVP: and ordinary users of the Normal CHA: Operating
Reboot the NAS OS of failure completion of failover and the
CHA. location of NAS Package on
which the failover is performed.
[Reboot NAS OS] Ask maintenance personnel to
See 3.5.8 [3][NAS03-840]. reboot the NAS OS of failure
CHA.
[NAS Package Location]
Browse Cluster Status
window in NAS Blade
Phone, E-mail: Phone, E-mail: Manager.
Inform the system administrator Acknowledge that the NAS OS
that the NAS OS of failure CHA of failure CHA has been
has been rebooted. rebooted.
[NAS07-1009T2]
NAS07-1009T1

functionality to start the node on
failure CHA. Failure CHA: Target service
stopped

functionality to perform a failback
from normal CHA to failure CHA,
and confirm that the failback has
been completed.
[NAS07-1009T3]
NAS07-1009T2

stopped
functionality to perform failover
from failure CHA to normal CHA Perform failover from normal
and check the completion of CHA to failure CHA.
failover.
Failover report
NAS Management Console: - syslog (failure CHA report)
functionality to stop the normal
CHA node.

Phone, E-mail: stopped (for failure
Notify maintenance personnel CHA)
Setup on SVP: and ordinary users of the Operating (for
Reboot the NAS OS of normal completion of failover and the normal CHA)
CHA. location of NAS Package on Normal CHA: NAS OS running
[Reboot NAS OS] Ask maintenance personnel to
See 3.5.8 [3][NAS03-840]. reboot the NAS OS of normal
CHA.
[NAS Package Location]
window in NAS Blade
Phone, E-mail: Phone, E-mail: Manager.
Inform the system administrator Acknowledge that the NAS OS
that the NAS OS of normal CHA of normal CHA has been
[NAS07-1009T4]
NAS07-1009T3

stopped (for failed
NAS Management Console: CHA)
Use the NAS Blade Manager Operating (for
functionality to start the node on normal CHA)
failure CHA. Normal CHA: NAS OS running
NAS Management Console: Failure CHA: Target service

Use the NAS Blade Manager stopped
functionality to perform a failback Normal CHA: Operating
from failure CHA to normal CHA,
and confirm that the failback has
been completed.
[NAS07-1009U]
NAS07-1009T4
NAS07-1009U DKC515I
NAS Management Console: Failure CHA: Target service

Recreate the failed file system stopped
using NAS Blade Manager. *1 Normal CHA: Operating

Mount the failed file system using
NAS Blade Manager.

Restore the file system using NAS
Backup Restore. *1

Create file shares (NFS, CIFS) for
the failed file system using NAS
Blade Manager.

Phone, E-mail: Confirm that the Notify maintenance personnel that
file system has been restored. the file system has been restored.
CL1-CHA: Operating
Then, notify ordinary users that
CL2-CHA: Operating
the file system has been restored.

Monitor the failure recovery CHA
END operation.
*1: When the file system of the failed LU is a copy-destination file system of
ShadowImage in-system replication or TrueCopy remote
replication/TrueCopy asynchronous extension, recreate the copy pair of
ShadowImage or TrueCopy/TrueCopy Async and restore the data by copying
it from the copy-source file system.
NAS07-1009U
NAS07-1009U1 DKC515I
7.6.22 User LU File System is Blocked (When Automatic Failover Function is Enabled)
CL1-CHA CL2-CHA Backup LU for NAS CM LU
Web server Backup LU for NAS CM LU
Application Pentium NAS Cluster Management LU
NAS OS kernel
NAS OS driver Error Information LU

MP MP
Command Device
NAS OS,
PP logs
User LU
User LU
Event Hibernation
trace dump User LU
Auto Dump Nas Dump (Legend) : Monitoring each other : Failed part
Figure 7.6-22 User LU File System is Blocked (When Automatic Failover Function
is Enabled) (1/8)

1 Confirm that the file system of user LUs is blocked.
2 Confirm that the failover finished.
3 Acquire detailed information and send it to the developer.
4 Fail back from the normal CHA to the failure CHA.
5 Delete the failed file system.
6 Fail over from the failure CHA to the normal CHA.
7 Reboot the NAS OS on the failure CHA.
8 Fail back from the normal CHA to the failure CHA.
9 Fail over from the normal CHA to the failure CHA.
10 Reboot the NAS OS on the normal CHA.
11 Fail back from the failure CHA to the normal CHA.
12 Re-create and restore the failed file system.
NAS07-1009U1
User LU file system is blocked

(when automatic failover function is The file system of the user
enabled) LUs is blocked.
Failure notification
• SVP (CL1-CHA MP notification)
• SVP (SIM code ac88x2)
Acknowledge the file system
failure from SIM, ACC, SSB
notification.
Failure CHA: Related

operations stopped
SVP: NAS management console: Normal CHA: Operating
Identify the failed NAS Package Confirm that the failover from the
from SIM (ac88x2). failure CHA to normal CHA has Fail over from failure CHA to
finished. normal CHA
Phone, E-mail: Phone, E-mail: notifiaction)
Acknowledge the failed file Notify maintenance personnel and - syslog (normal CHA notification)
system. ordinary users of the completion of - System message
the failover and the location of the (normal CHA notification)
NAS Package. - SVP(SIM code ac84x2)
SVP: Acquire the crush dump

Acquire detailed information. automatically
See 7.2.3 [NAS07-70].
SVP: Failure CHA: NAS OS running

Send the detailed information to Normal CHA: Operating
the developer and ask for a (Performing the operation of
primary scan. the both CL1-CHA and
CL2-CHA)
To developer
[NAS07-1009U3]
is Enabled) (2/8)
NAS07-1009U2
1
Provided that the file system is
backed up regularly.

Ask the system administrator to Notify ordinary users that a Normal CHA: Operating
delete the failed file system and failback will be performed and (Performing the operation of
to fail back. the failed file system will be the both CL1-CHA and
restored and ask to stop CL2-CHA)
performing related tasks.
Failback from the normal CHA
to failure recovery CHA
Fail back from the normal CHA to
the failure recovery CHA by using Failback notification
NAS Blade Manager and confirm - NAS Blade Manager GUI
that the failback finished. (Failure recovery CHA
notification)
- syslog (Failure recovery CHA
notification)
NAS management console: Failure CHA: Related

Release the NFS and CIFS shares operations stopped
for the failed file system by using Normal CHA: Operating
NAS Blade Manager.

Delete the failed file system by
using NAS Blade Manager.
[NAS07-1009U4]
is Enabled) (3/8)
NAS07-1009U3
Phone, E-mail: Failure CHA: Related operations

Notify ordinary users that a stopped
failback and failover will be Normal CHA: Operating
performed and acquire
permission for them.

Fail over from failure CHA to
normal CHA by using NAS Blade Fail over from failure CHA to
Manager and confirm that the normal CHA
failback finished.
NAS management console: - syslog
Stop the node on the failure CHA (normal CHA notification)
by using NAS Blade Manager.
Phone, E-mail: Failure CHA: Related operations

Setup on SVP: stopped
Reboot the NAS OS on the Normal CHA: Operating
failure CHA. and ordinary users the
completion of the failover and the
NAS Package location. Ask
maintenance personnel to reboot
the NAS OS on the failure CHA.

[Reboot the NAS OS] Check CHA-xx displayed in
See 3.5.8 [3] [NAS03-840].
the Browse Cluster window

Notify the system administrator Acknowledge that the NAS OS
that the NAS OS on the failure on the failure CHA has been
CHA has been rebooted. rebooted.
[NAS07-1009U5]
is Enabled) (4/8)
NAS07-1009U4
Failure CHA: Related operations

stopped (for failure CHA)
Operating (for normal CHA)
Normal CHA: NAS OS running
Start the node of the failure CHA
by using NAS Blade Manager.

Fail back from normal CHA to Failure CHA: Related
failure CHA by using NAS Blade operations
Manager and confirm that the stopped
failback finished. Normal CHA: Operating
[NAS07-1009U6]
is Enabled) (5/8)
NAS07-1009U5
NAS management console: Failure CHA: Related

Fail over from normal CHA to operations stopped
failure CHA and confirm that the Normal CHA: Operating
failover finished by using NAS
Blade Manager.
Fail over from normal CHA to
failure CHA
NAS management console: - NAS Blade Manager GUI
Stop the node of normal CHA by (failure CHA notification)
using NAS Blade Manager
- syslog (failure CHA
notification)
Setup on SVP: Phone, E-mail: Failure CHA: Related

Reboot the NAS OS on failure Notify maintenance personnel operations stopped (for
CHA. and ordinary users of the failure CHA)
completion of the failover and the Operating (for normal CHA)
NAS Package location. Normal CHA: NAS OS running
reboot the NAS OS on the failure
CHA.
[Reboot the NAS OS] [NAS Package location]
See 3.5.8 [3] [NAS03-840]. Check CHA-xx displayed in
the Browse Cluster Status
window of NAS Blade
Manager.

Notify the system administrator Acknowledge that the NAS OS
that the NAS OS on normal CHA on normal CHA has been
[NAS07-1009U7]
is Enabled) (6/8)
NAS07-1009U6
5
Failure CHA: Related operations
stopped (for failure CHA),
Operating (for normal
CHA)
Normal CHA: NAS OS running

Start the node on failure CHA by

Fail back from failure CHA to
normal CHA and confirm that the
failback finished by using NAS Failure CHA: Related
Blade Manager. operations stopped
[NAS07-1009U8]
is Enabled) (7/8)
NAS07-1009U7
NAS maintenance console: Failure CHA: Related

Re-create the failed file system operations stopped
by using NAS Blade Manager. *1 Normal CHA: Operating

Mount the failed file system by

Restore the failed file system by
using NAS Backup Restore. *1

Set NFS and CIFS file shares for
the failed file system by using
NAS Blade Manager.
Phone, E-mail: Phone, E-mail: Failure CHA: Operating

Confirm that the file system has Notify maintenance personnel Normal CHA: Operating
been restored. that the restore of the file system
finished and notify ordinary users
that the file system has been
restored.

Monitor the failure recovery CHA
operation.
End
*1: When the file system of the failed LU is a copy-destination file system of
replication/TrueCopy asynchronous extension, recreate the copy pair of
ShadowImage or TrueCopy/TrueCopy Async and restore the data by copying
it from the copy-source file system.
Figure 7.6-22 User LU File System is Blocked (When Automatic Failover is

Enabled) (8/8)
NAS07-1009U8
NAS07-1009V DKC515I
7.6.23 NAS OS System File Failure (in NAS OS Start/Stop Processing)

CL1-CHA
Web server Manual failback

NAS OS kernel
NAS OS driver MP MP
Command Device
NAS OS,
PP log
User LU
User LU
Event Hibernation
trace dump User LU

Auto Dump NAS Dump
Figure 7.6-23 NAS OS System File Failure (in NAS OS Start/Stop Processing) (1/3)

1 Confirm that a failure occurred in a NAS OS system
file.
2 Upgrade the NAS OS by an update version. Re-install the NAS OS of the
version used at the time the
failure occurred, by following
the procedure for upgrading
NAS OS by an update version.
developer.
NAS07-1009V
NAS07-1009W DKC515I
NAS OS system file failure (in

NAS OS start/stop processing)

By checking SIM, ACC, and SSB, - SVP (Failure CHA MP report)
confirm that a NAS OS or - SVP (SIM code: ac88x3)
application failure occurred. Subcode (0x04080101)

stopped
By the SIM code (ac88x3), identify
has occurred.
Setup on SVP: Message appears on Setup on SVP Failure CHA: Stopped

Reset the NAS OS on failure CHA. After the message ENS3596E is displayed, Normal CHA: Operating
wait until the hibernation dump has been
acquired, and then execute.
[Reset NAS OS]
See 3.5.9 [NAS03-880].
Setup on SVP: When you click Program Install,

Upgrade the NAS OS on failure the message ENS3578W appears.
CHA by an update version. Click OK, and then continue the
operation.
[Upgrade NAS OS by an
update version]
See 5.3.2 [1] [NAS05-570].
Try upgrading again.

Did the upgrade
finish successfully?
No
Yes [Did the upgrade finish successfully?] Failure CHA: NAS OS running
The status displayed in the Install Normal CHA: Operating
Progress window is Completed. See
5.3.2 [1] (9) [NAS05-660].
[NAS07-1009X]
NAS07-1009W
NAS07-1009X DKC515I
1
SVP:
Acquire detailed information. See
7.2.3 [NAS07-70].
SVP:
Send the system administrator
detailed information and ask for a
primary scan.
To developer
Failing back from normal CHA to
Phone, E-mail: Phone, E-mail: failure CHA
Ask the system administrator to Notify ordinary users and acquire Failback notification
perform a failback and start the permission to fail back.
node of failure CHA. - NAS Blade Manager GUI
- syslog (Failure CHA notification)
Start the node of failure CHA by

Manually fail back from normal
CHA to failure CHA and confirm
that the failback finished.
Acknowledge that the failback Notify ordinary users and maintenance
finished and the node of failure personnel that the failback finished and
recovery CHA has started. the location of the NAS Package on
[Acknowledge that the node [NAS Package location]
has started] Identify the location by
Confirm that the status of the checking CHA-xx
NAS Package is ACTIVE. displayed in the Browse
See 3.5.3 [NAS03-260]. Cluster Status window of
NAS Blade Manager.

End Monitor failure recovery CHA
operation.
NAS07-1009X
NAS07-1010 DKC515I
7.7 NAS Hardware Replacement When a Failure Occurs

This section shows the replacement of the hardware in the NAS Blade system and the software
replacement operations when the version of the software is updated.
You can perform hot replacement of the hardware and online replacement of micro-programs in a
disk subsystem without stopping user services (except for cases such as when a RAID group is not
usable because of a PDEV failure).
NAS07-1010
NAS07-1020 DKC515I
The following sections describe the hardware replacement operations performed by maintenance
[1] Types of Hardware Replacement Operations

Hardware is replaced in the following two situations:
Replacement when a hardware failure occurs

This replacement operation replaces the failed hardware.
Replacement during periodic hardware replacement

This replacement operation replaces hardware based on the results, for example, of periodic
diagnostics or correctable errors.
This section shows the replacement when a hardware failure occurs.
Such replacement operations are classified based on the operations performed by maintenance
personnel or system administrators and the NAS Blade system behavior, as follows.
NAS07-1020
NAS07-1030 DKC515I
Table 7.7-1 Types of Hardware Replacement Operations

# Target hardware Corresponding tasks Restart Perform a Can ordinary users Reference info.
the NAS failback? continue for when a
1
OS? operations? * failure occurs
1 NAS Package Replace the NAS Package. Yes Yes Yes Figure 7.7-1
[NAS07-1050]
2 Hardware other than Replace the hardware (hot No No Yes Figure 7.7-2
NAS Package*2 replacement). [NAS07-1080]
3 Two PDEVs Replace two PDEVs. Yes Yes No Figure 7.7-3
(user LUs)*3 Release the RAID group’s [NAS07-1100]
blocked state.
4 External subsystem Recover external subsystem Yes Yes No Figure 7.7-4
device device status [NAS07-1131]
5 Two PDEVs Replace two PDEVs. Yes Yes Yes Figure 7.7-5
(NAS OS LUs: when Release the RAID group’s [NAS07-1140]
the NAS OS LU and blocked state.
the dump LU belong Restore a NAS OS LU.
to different RAID
groups)
3
6 Two PDEVs Replace two PDEVs. Yes No* No Figure 7.7-6
(NAS OS LUs: when Release the RAID group’s [NAS07-1180]
the NAS OS LU for blocked state.
CL1-CHA and that Rebuild.
for CL2-CHA belong
to the same RAID
group)
3
7 Two PDEVs Replace two PDEVs. Yes No* No Figure 7.7-7
(NAS Cluster Release the RAID group’s [NAS07-1200]
Management LUs) blocked state.
Rebuild.
4
8 Two PDEVs Replace two PDEVs. Yes Yes Yes* Figure 7.7-8
(dump LUs) Release the RAID group’s [NAS07-1220]
blocked state.
5
9 Two PDEVs Replace two PDEVs. No No Yes* Figure 7.7-9
(error information Release the RAID group’s [NAS07-1270]
LUs) blocked state.
6
(command devices) Release the RAID group’s [NAS07-1290]
blocked state.
7
(Backup LUs of NAS Release the RAID group’s [NAS07-1310]
Cluster Management blocked state.
LUs)
12 Data LAN fiber optic Check the data LAN fiber No Yes Yes Figure 7.7-12
cable (LAN cable) optic cable (LAN cable)*8 [NAS07-1340]
and switch*8 connection, repair of the
switch, and network.
13 Control LAN fiber Check the control LAN No No Yes Figure 7.7-13
optic cable (LAN fiber optic cable (LAN [NAS07-1360A]
cable) and switch cable) connection, repair of
the switch, and network.
14 Data LAN fiber optic Check the data LAN fiber No No Yes Figure 7.7-14
cable (LAN cable) optic cable (LAN cable)*8 [NAS07-1360C]
connection, repair of the
switch, and network.
15 -- Failback Yes Yes Yes Figure 7.7-15
[NAS07-1361]
NAS07-1030
NAS07-1031 DKC515I
*1: Yes: Ordinary users can continue their operations.

However, if the application server is connected with Windows client (CIFS share) when
a failback occurs, the CIFS share is released. Therefore, you must reconnect the server
with CIFS share.
No: Ordinary users cannot perform operations related to the failed PDEV(s).
*2: For details, see the REPLACE Section [REP01-10].
*3: Failover cannot be performed.
*4: The hibernation dump and the crash dump cannot be collected when a NAS OS failure
occurred.
*5: The hibernation dump and the crash dump cannot be obtained.
*6: Snapshots and backups cannot be performed.
*7: The NAS Cluster Management LU cannot be backed up.
*8: This includes the cable shared by the data LAN and control LAN.
NAS07-1031
NAS07-1040 DKC515I
[2] Procedures for Replacing Hardware
following tables show the flowcharts for hardware replacement on CL1-CHA from Figure
7.7-1 to Figure 7.7-15.
Make sure that CL2-CHA is properly referred to as the actual location when for hardware
replacement on the CHA location.

Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
NAS07-1040
NAS07-1050 DKC515I
7.7.1 Replacing the NAS Package (When a Failure Occurs)
Replacement
NAS Package
CL1-CHA CL2-CHA
Pentium
User LU
Command Device
User LU
User LU
: Failover
: Failback
: Monitoring
: Failed part
Figure 7.7-1 Replacing the NAS Package (When a Failure Occurs) (1/3)

2 Perform failback.
NAS07-1050
NAS07-1060 DKC515I
Replacing the NAS package

(when a failure occurs)
Failure CHA: NAS OS not running
Normal CHA: Operating (Performing
SVP: CL1-CHA and CL2-CHA)
Identify the failed NAS Package
from SIM/ACC/SSB.
[Is NAS OS running?]
Is NAS OS NO in 3.5.3 [NAS03-260].
on Failure CHA
running?
YES
2 [NAS07-1070]

requires a failover, and ask her to
perform a failover. Failing over from failure CHA to
normal CHA
from failure CHA to normal CHA, - NAS Blade Manager GUI
and confirm that the failover has (normal CHA notification)
been completed. - syslog (normal CHA notification)

functionality to stop the node on
CL1-CHA.
Phone, E-mail:
Acknowledge that the failover has Phone, E-mail: Failure CHA: NAS OS running
been completed. Notify maintenance personnel Normal CHA: Operating (Performing
and ordinary users of the the operations of both
[Acknowledge that the completion of failover and the CL1-CHA and CL2-CHA)
node has stopped] NAS Package location.
Confirm that the NAS OS
Package status is Check CHA-xx
INACTIVE in the ‘Main’ displayed in the 'Browse
window. See 3.5.3 Cluster Status' window
[NAS03-260]. of NAS Blade Manager
GUI.
Monitor the normal CHA's
[NAS07-1070] operations.
NAS07-1060
NAS07-1070 DKC515I
Failure CHA: NAS OS is not running

Setup on SVP: Normal CHA: Operating (Performing
Stop the NAS OS for failure CHA. the operations of both
Stop NAS OS CL1-CHA and CL2-CHA)
2 3.5.8 [1] [NAS03-780].
NAS frame: The NAS OS starts

automatically when the Failure CHA: NAS OS is running
Replace the board for failure CHA.
replacement is finished. Normal CHA: Operating (Performing
Replace NAS the operations of both
Package CL1-CHA and CL2-CHA)
See [REP01-280].
NAS frame:
By checking the CHL lamp,
make sure that the NAS OS has
started.
Phone, E-mail:
Phone, E-mail:
perform a failback.
functionality to confirm the node
on failure recovery CHA is active. Failing back from failure recovery
If it is inactive, start it. CHA to normal CHA

Use the NAS Blade Manager - NAS Blade Manager GUI (failure
functionality to perform a failback recovery CHA notification)
from normal CHA to failure - syslog (failure recovery CHA
recovery CHA, and confirm that notification)
the failback has been completed.

has been completed and that the and ordinary users of the
failure recovery CHA node has completion of failback and the
started. NAS Package location.
node has started] [NAS Package location]
Confirm that the NAS Check CHA-xx displayed in the
Package is ACTIVE in 'Browse Cluster Status' window
the ‘Main’ window. See of NAS Blade Manager GUI.
3.5.3 [NAS03-260]. NAS Management Console:
Monitor the failure recovery
End CHA's operations.
NAS07-1070
NAS07-1080 DKC515I
7.7.2 Hot-replacing Hardware Other Than the NAS Package
Replacement
Target Hardware
CL1-CHA CL2-CHA
Fan, Power
Supply, etc.
Pentium Pentium
User LU
Command Device
User LU
User LU
: Monitoring
: Failed part

1 Replace the target hardware.
NAS07-1080
NAS07-1090 DKC515I
Hot-replacing the hardware

Failure CHA: –
The NAS Package state

depends on the hardware to
SVP, Target hardware: be replaced.
Hot-replace the target
hardware.
HOT replace
See [REP01-10].
End
NAS07-1090
NAS07-1100 DKC515I
7.7.3 Replacing Two PDEVs (User LUs)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP
NAS System LU
SVP Backup LU of NAS CM LU

User LU Restoration
Command Device
User LU
User LU
Backed
Replacement up Data
: Monitoring : Failed part
Figure 7.7-3 Replacing Two PDEVs (User LUs) (1/6)
NAS07-1100
NAS07-1101 DKC515I

1 Check that the file system is deleted in the
user LU on which the error occurred.
2 Fail over from the failure CHA to the
normal CHA.
3 Stop the node of the CHA to which the
failed user LU belongs (failure CHA).
4 Reboot the NAS OS on the failure CHA.
5 Start the node of the failure CHA.
6 Fail back from the normal CHA to the
failure CHA.
7 Fail over from the normal CHA to the
failure CHA.
8 Stop the node of the normal CHA.
9 Reboot the NAS OS on the normal CHA.
10 Start the node of the normal CHA.
11 Fail back from the failure CHA to the
normal CHA.
12 Replace the target PDEV.
13 Release the RAID group’s blocked state.
14 Re-create a file system in the user LU.
15 Restore the user data. Do so only if the backup data already exists.
NAS07-1101
NAS07-1110 DKC515I
Replacing two PDEVs

(user LU)

Request a system administrator Check that the deletion of the
to check the state of the file failed file system is finished. *1
system in the user LU on which Specify the NAS Package (the
the error occurred, to specify the failure CHA) on which the error
NAS Package on which the error LU was mounted when the error
LU was mounted, to perform a occurred.
failover and to stop the node on
failure CHA.
Phone, E-mail: CL1-CHA: Error LU service stopped
Notify ordinary users of the CL2-CHA: Error LU service stopped
normal CHA
functionality to perform a failover - NAS Blade Manager GUI
from failure CHA to normal CHA, (normal CHA notification)
and confirm that the failover has - syslog (normal CHA notification)
been completed.

failure CHA.
Phone, E-mail:
Acknowledge that the failover has
been completed, that the node on Phone, E-mail: Failure CHA: NAS OS running
failure CHA has stopped, and the Notify maintenance personnel Normal CHA: Error LU service stopped
location of the failure CHA of the and ordinary users of the (Performing the operations of
NAS Package on which the error completion of failover and the both CL1-CHA and
LU was mounted when the error location of the failure CHA of the CL2-CHA)
occurred. NAS Package.
node has stopped] Check CHA-xx displayed in the
Confirm that the NAS OS 'Browse Cluster Status' window of
Package status is NAS Blade Manager GUI.
INACTIVE in the ‘Main’ NAS Management Console:
window. See 3.5.3 Monitor the normal CHA's
[NAS03-260]. operations.
*1: When the file system of the error LU is a source file system or a
1 destination file system of ShadowImage in-system replication or
TrueCopy remote replication/TrueCopy asynchronous extension, delete
the copy pair of ShadowImage or TrueCopy/TrueCopy Async.
[NAS07-1120]
NAS07-1110
NAS07-1120 DKC515I
Setup on SVP:
Restart the NAS OS on failure
CHA.
Phone, E-mail:
[Restart NAS OS] Notify ordinary users of the
See 3.5.8 [3] failback and get permission for it.
[NAS03-840].
Normal CHA: Target LU service
stopped (Performing the
Phone, E-mail: NAS Management Console: operations of both
Ask a system administrator to Use the NAS Blade Manager CL1-CHA and CL2-CHA)
start the node on failure CHA functionality to start the node on
and to perform a failback. failure recovery CHA.
Failing back from normal CHA to
failure recovery CHA
functionality to perform a failback Failback notification
from normal CHA to failure CHA, - NAS Blade Manager GUI (failure
and confirm that the failback has recovery CHA notification)
been completed. - syslog (failure recovery CHA
notification)
Phone, E-mail:
Phone, E-mail:
Acknowledge that the failback
has been completed and that the CL1-CHA: Target LU service stopped
completion of failback.
failure recovery CHA node has CL2-CHA: Target LU service stopped
started.
node has started]
3.5.3 [NAS03-260].
2 Monitor the failure recovery
CHA's operations.
[NAS07-1121]
NAS07-1120
NAS07-1121 DKC515I
Phone, E-mail: Phone, E-mail: CL1-CHA: Stop operations on

Ask the system administrator to Notify ordinary users and acquire the target LU
fail over and stop the node of the permission for the failover. CL2-CHA: Stop operations on
normal CHA. the target LU
Fail over from normal CHA
to failure CHA
Fail over from the normal CHA to Failover notification
failure CHA and confirm that the - NAS Blade Manager GUI
failover finished by using NAS (Failure CHA notification)
Blade Manager. - syslog (Failure CHA
notification)

Stop the node of the normal CHA
by using NAS Blade Manager. Normal CHA: NAS OS running
Failure CHA: Stop operations
on the target LU.
(Performing operations for both
Phone, E-mail: Phone, E-mail: CL1-CHA and CL2-CHA)
Acknowledge that the failover Notify maintenance personnel
finished and the normal CHA is and ordinary users the
not running, and the location of completion of the failover and
the normal CHA. the location of the normal CHA.
[Acknowledge that the node is [NAS Package location]

not running] Check CHA-xx displayed in the
Confirm that the NAS Package Browse Cluster Status window of
status is INACTIVE in the Main NAS Blade Manager.
window. See 3.5.3
[NAS03-260].

Monitor the failure CHA
3 operation.
[NAS07-1122]
NAS07-1121
NAS07-1122 DKC515I
Setup on SVP:
Reboot the NAS OS on normal CHA.
[Reboot the NAS OS]

See 3.5.8 [3] [NAS03-840].

Ask the system administrator to Notify ordinary users of the
start the node of normal CHA failback and acquire permission
and to fail back. for it.

Start the node of normal CHA by
using NAS Blade Manager. Normal CHA: NAS OS running
Failure CHA: Stop operations
on the target LU
(Performing both operations for
NAS management console: CL1-CHA and CL2-CHA)
Fail back from failure recovery Fail back from failure recovery
CHA to normal CHA and confirm CHA to normal CHA
that the failback finished by
using NAS Blade Manager. Failback notification
(Normal CHA notification)
- syslog (Normal CHA
Phone, E-mail: Phone, E-mail: notification)
finshed and the node of normal and ordinary users that the
CHA is running. failback finished.
CL1-CHA: Stop operations on
the target LU.
[Acknowledge that the node CL2-CHA: Stop operations on
is running] the target LU
Package status is ACTIVE in
the Main window. See 3.5.3
[NAS03-260].

4 Monitor the normal CHA
operation.
[NAS07-1130]
NAS07-1122
NAS07-1130 DKC515I
SVP, NAS frame: CL1-CHA:Operations for target

Replace the failed PDEVs, and LU has stopped.
release the RAID group's blocked CL2-CHA:Operations for target
state. LU has stopped.
Replace the failed
PDEV This procedure assumes that
See [TRBL05-210]. backup is performed periodically.

Notify a system administrator that Use the NAS Blade Manager
the PDEV replacement has been functionality to re-create a file
completed, and request the system in the user LU. *1
system administrator to restore
user data.

Use the NAS Backup Restore
functionality to restore user data.
*1
CL1-CHA: Operations for target LU

Phone, E-mail: Phone, E-mail: has restarted.
Acknowledge that the PDEV Notify maintenance personnel CL2-CHA:Operations for target LU
replacement has been that the restore has been has restarted.
completed. completed, and ordinary users
that the RAID replacement has
been completed.
*1: When the file system of the error LU is a destination file system of
End ShadowImage in-system replication or TrueCopy remote
replication/TrueCopy asynchronous extension, re-create the copy pair of
ShadowImage or TrueCopy/TrueCopy Async to restore the data from
the source file system
NAS07-1130
NAS07-1131 DKC515I
7.7.4 Recovering External Subsystem Device Status
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP
NAS System LU
SVP Backup LU of NAS CM LU

User LU
Command Device
User LU
User LU
External Subsystem Device
Restoration
Backed
up Data
Replacement
and recovery
: Monitoring : Failed part
Figure 7.7-4 Recovering External Subsystem Device Status (1/7)
NAS07-1131
NAS07-1132 DKC515I

1 Recover the external subsystem. Check the recovery SIM.
2 If the RAID group is blocked, release
it from the blocked state.
3 Check if data loss occurred in the If data loss did not occur, go to step 4.
external subsystem. If data loss occurred, go to step 4a.
4 Perform failover.
5 Stop the node.
6 Restart the NAS OS of the user LU in
the failed external subsystem device.
7 Start the node.
8 Perform failback.
Recovery procedure for when the failed external subsystem cannot continue operation
4a Delete the file systems in the failed
external subsystem device.
5 Perform failover.
6 Stop the node.
7 Restart the NAS OS of the user LU in
the failed external subsystem device.
8 Start the node.
9 Perform failback.
10 Recreate file systems and file shares
in the external subsystem device.
11 Restore the user data to the external Do so if the backup data exists.
subsystem device.
NAS07-1132
NAS07-1133 DKC515I
Recovering external subsystem

status
Report that the external subsystem

External subsystem, SVP:
is recovered
Identify and remove the cause of - SVP (SIM code: 21d1xx)
the error in the external
subsystem (such as power
failure, bus error, and disk error).
[TRBL15-10]
SVP:
If the RAID group in the external
subsystem device is blocked,
release it from the blocked state.
[TRBL15-10]
External subsystem administrator

Phone, E-mail:
Ask the external subsystem External subsystem:
administrator to check if data Check if data loss occurred in the
loss occurred in the external external subsystem.
subsystem.
Phone, E-mail:
Acknowledge whether data loss Phone, E-mail:
occurred in the external Notify maintenance personnel
subsystem. whether data loss occurred in the
external subsystem.
NO
Did data loss occur?
YES
[NAS07-1137]
1
[NAS07-1134]
NAS07-1133
NAS07-1134 DKC515I

Ask a system administrator to Delete the file systems in the
delete the file systems in the external subsystem device. *1
failed external subsystem
device, to identify the NAS
Package that mounted the user NAS management console:
LU in the external subsystem Identify the NAS Package
device, and to perform failover (CL1-CHA, CL2-CHA) that
and failback. mounted the LU when the failure
occurred. CL1(or 2)-CHA: Target LU service
stopped
Phone, E-mail: CL2(or 1)-CHA: Target LU service
Notify ordinary users of the stopped
a Failing over from CL1(or 2)-CHA to
CL2(or 1)-CHA
function to perform a failover - NAS Blade Manager GUI (CL1(or
from CL1(or 2)-CHA to CL2(or 2)-CHA notification)
1)-CHA, and confirm that the - syslog (CL2(or 1)-CHA notification)
failover has been completed.

Phone, E-mail: Stop the node on CL1(or 2)-CHA
Acknowledge that the failover using NAS Blade Manager.
has been completed and that the
CL1(or 2)-CHA node has CL1(or 2)-CHA: NAS OS running
Phone, E-mail:
stopped. Also confirm the CL2(or 1)-CHA: Target LU service
location of the CHA of NAS stopped
personnel and ordinary users of
Package that mounted the user (Performing the operations of both
the completion of failover and the
LU in the external subsystem CL1-CHA and CL2-CHA)
location of the CL1(or 2)-CHA.
device when the failure occurred.
stopped] Check the location with CHA-xx
Confirm that the NAS Package displayed in Browse Cluster Status
status is INACTIVE in the ‘Main’ window of NAS Blade Manager
3
[NAS07-1135]
*1: When the file system of the LU in the failed subsystem device is a source
file system or a destination file system of ShadowImage in-system replication
or TrueCopy remote replication/TrueCopy asynchronous extension, delete
the copy pair of ShadowImage or TrueCopy/TrueCopy Async.
NAS07-1134
NAS07-1135 DKC515I
Storage navigator:
Restart NAS OS on CL1(or (*1)
2)-CHA with Storage Navigator
function.
Storage navigator: CL1(or 2)-CHA: NAS OS running

Start NAS OS on CL1(or 2)-CHA CL2(or 1)-CHA: Target LU service
with Storage Navigator function. stopped
(Performing the operations of both
Phone, E-mail:

Start the node on CL1(or 2)-CHA

functionality to perform a failback Failing back from CL2(or 1)-CHA to
[NAS07-1134] from CL1(or 2)-CHA to CL2(or CL1(or 2)-CHA
1)-CHA, and confirm that the Failover notification
a failback has been completed. - NAS Blade Manager GUI (CL1(or
2)-CHA notification)
- syslog (CL1(or 2)-CHA notification)
Perform the same
operation for Completed for the
CL2(or 1)-CHA. both NAS Packages?
NO
YES

Acknowledge that the failback Notify the maintenance
has been completed and that the personnel and ordinary users of
CL1(or 2)-CHA node has started. the completion of failback.
CL1(or 2)-CHA: Target LU service
stopped
[Acknowledge that the node has CL2(or 1)-CHA: Target LU service
started] stopped

Monitor CL1(or 2)-CHA
operation.
4
*1: See “3.9 Operating NAS Channel Adapters” in
[NAS07-1136] LUN Manager User’s Guide.
NAS07-1135
NAS07-1136 DKC515I
CL1-CHA: Target LU service stopped

Provided that the data is backed
up regularly
Notify the system administrator Recreate the file system in the
that the external subsystem external subsystem device using
device is recovered and ask to NAS Blade Manager. *1
restore the user data to the
external subsystem device.
External subsystem:
Restore the user data to the
external subsystem device using
the backup function of the
external subsystem. *1

Set the file sharing for the
subsystem device using NAS
Blade Manager.
Phone, E-mail:
Phone, E-mail: Notify the maintenance
Confirm that the external personnel that the restoration
subsystem device is recovered. ended and ordinary users that
the recovery of the external
subsystem device ended.
*1: If the file system in the failed LU is a destination file system of

replication/TrueCopy asynchronous extension, recreate the copy pair and
End recover data by copying it from the copy source file system.
NAS07-1136
NAS07-1137 DKC515I

Ask a system administrator to Identify the NAS Package (CL1-
identify the NAS Package that CHA, CL2-CHA) that mounted
mounted the user LU in the the LU when the failure
external subsystem device and occurred.
to perform failover and failback. CL1(or 2)-CHA:
Target LU service stopped
Phone, E-mail: CL2(or 1)-CHA:
Notify ordinary users of the Target LU service stopped
b
Failing over from CL1(or 2)-CHA to
NAS management console: CL2(or 1)-CHA
function to perform a failover - NAS Blade Manager GUI (CL2(or
from CL1(or 2)-CHA to CL2(or 1)-CHA notification)
1)-CHA, and confirm that the - syslog (CL2(or 1)-CHA notification)
failover has been completed.

Phone, E-mail: Stop the node on CL1(or 2)-CHA
Acknowledge that the failover using NAS Blade Manager.
has been completed and that the
CL1(or 2)-CHA node has
stopped. Also confirm the Phone, E-mail: CL1(or 2)-CHA:
location of the CHA of NAS Notify the maintenance Target LU service stopped
Package that mounted the user personnel and ordinary users of CL2(or 1)-CHA:
LU in the external subsystem the completion of failover and Target LU service stopped
device when the failure the location of the CL1(or
occurred. 2)-CHA.
stopped] Check the location with CHA-xx
Confirm that the NAS Package displayed in Browse Cluster Status
status is INACTIVE in the ‘Main’ window of NAS Blade Manager
5
[NAS07-1138]
NAS07-1137
NAS07-1138 DKC515I
Storage Navigator: (*1)

Restart the NAS OS on the
CL1(or 2)-CHA using Storage
Navigator.
Phone, E-mail:

Start the node on CL1(or 2)-CHA CL1(or 2)-CHA:
using NAS Blade Manager. Target LU service stopped
CL2(or 1)-CHA:
Target LU service stopped

Perform failback from CL2(or Failing back from CL2(or 1)-CHA to
[NAS07-1137] 1)-CHA to CL1(or 2)-CHA and CL1(or 2)-CHA
confirm that the failback has
been completed. Failback notification
b
- NAS Blade Manager GUI (CL1(or
2)-CHA notification)
Perform the same - syslog (CL1(or 2)-CHA notification)
operation for Completed for the
CL2(or 1)-CHA. both NAS Packages?
NO
YES
Phone, E-mail:
personnel and ordinary users
that the failback has been
completed.
CL1-CHA: Target LU service resumed
CL2-CHA: Target LU service resumed
Phone, E-mail:
Phone, E-mail:
Confirm that the external
personnel and ordinary users
subsystem device is recovered.
that the recovery of the external
subsystem device ended.
End *1: See “3.9 Operating NAS Channel Adapters” in

LUN Manager User’s Guide.
NAS07-1138
NAS07-1140 DKC515I
7.7.5 Replacing Two PDEVs (NAS OS LU: When the NAS OS LU and the Dump LU Belong to
Different RAID Groups)
CL1-CHA CL2-CHA

Product Product Dump LU for CL1-CHA
Installation
NAS OS NAS OS
Restoration Backup LU of NAS CM LU

Dump LU for CL2-CHA
(Backed Up Data for NAS OS LU) NAS Cluster Management LU
SVP
Replacement
User LU
Command Device
User LU
User LU
Supplied
Media
: Failover
: Failback
: Monitoring
: Failed part
Figure 7.7-5 Replacing Two PDEVs (NAS OS LU: When the NAS OS LU and the
Dump LU Belong to Different RAID Groups) (1/4)

2 Release the RAID group's blocked
state.
3 Install NAS OS. After the expansion installation, recover from the
4 Install NAS Blade Manager, and Upgrade to the version at the time of failure
optional program products. occurrence.
5 Set up the network information. Use the settings that were used at the time of failure
occurrence.
6 Restore the NAS OS LU. Do so only if the backup data of the NAS OS LU
already exists.
7 Restart the NAS OS.
8 Perform failback.
NAS07-1140
NAS07-1150 DKC515I
Replacing two PDEVs

(NAS OS LU: different RAID groups)
Failure CHA: NAS OS not

SVP, NAS frame: running
Replace the failed PDEVs, and release Normal CHA: Operating
the RAID group's blocked state. (Performing the operations of
Replace the failed PDEV
See [TRBL05-150]
Setup on SVP:
Perform NAS OS expansion
installation on failure CHA. *1
[NAS OS expansion
installation]
See 3.5.4 [2] [NAS03-400]
Setup on SVP:
Install NAS Blade Manager on failure CHA. *1
[NAS Blade Manager

installation]
See 3.5.4 [2] [NAS03-400]
Setup on SVP:
Install optional program products
on failure CHA. *1
[Optional program product
Installation]
See 3.5.4 [3] [NAS03-490]
Setup on SVP:
Set up the network settings for the
control port (fixed IP address, NTP).
[Set up the network settings
(fixed IP address, NTP)]
See 3.5.6 [NAS03-630]
Setup on SVP: Provided that the NAS OS LU is backed up when it is to be

Restore the NAS OS LU. updated.
If restoration is aborted with the error ENS3556E, take one
of the following actions according to the error code.
0x01000002:
NAS Blade Manager is not installed. Start the restoration
procedure over.
0x01000008 or 0x01000060:
The network configuration is incorrect. Check the
configuration and start the restoration procedure over.
[Restore NAS OS LU]

See 3.5.12[NAS03-990].
*1 After the expansion installation, recover from the
1
[NAS07-1160]
NAS07-1150
NAS07-1160 DKC515I
Setup on SVP:
Restart NAS OS on failure CHA.
[Restart NAS OS]
See 3.5.8 [3] [NAS03-840]

Notify a system administrator of Notify ordinary users of the Normal CHA: Operating
the normal CHA location and ask failback and get permission for it. (Performing the operations of
to perform a failback. both CL1-CHA and CL2-CHA)
Start the node on failure CHA.

functionality to confirm the node
on failure CHA is active. If it is
inactive, start it. Failing back from normal CHA to

Use the NAS Blade Manager - NAS Blade Manager GUI (failure
functionality to perform a failback recovery CHA notification)
from normal CHA to failure - syslog (failure recovery CHA
recovery CHA, and confirm that notification)
CL1-CHA: Operating
CL2-CHA: Operating
2
[NAS07-1170]
NAS07-1160
NAS07-1170 DKC515I
Has the
failback been
completed?
YES
NO

functionality to stop cluster in
normal CHA , and confirm that
the cluster has been stopped.

functionality to start cluster in
normal CHA , and confirm that
the cluster has been started.

has been completed and the and ordinary users of the CL2-CHA: Operating

node has started] Check CHA-xx displayed
Confirm that the NAS OS in the 'Browse Cluster
Package status is Status' window of NAS
ACTIVE in the ‘Main’ Blade Manager GUI.
window. See 3.5.3
[NAS03-260].
CHA's operations.
End
NAS07-1170
NAS07-1180 DKC515I
7.7.6 Replacing Two PDEVs (NAS OS LU: When the NAS OS LUs for CL1-CHA and CL2-CHA
Belong to the Same RAID Group)
CL1-CHA CL2-CHA
Installation Optional Program Optional Program
Product
Pentium Product
Pentium


NAS OS LU for CL1-CHA Dump LU for CL1-CHA
SVP
NAS OS LU for CL2-CHA Dump LU for CL2-CHA

Replacement User LU
Supplied User LU
Media
: Monitoring
: Failed part
Figure 7.7-6 Replacing Two PDEVs (NAS OS LUs: When the NAS OS LUs for
CL1-CHA and CL2-CHA Belong to the Same RAID Group) (1/2)

2 Release the RAID group’s blocked
state.
3 Perform the expansion installation After the expansion installation, recover from the failure
of NAS OS. by upgrading the NAS OS to the version at the time of
failure occurrence.
4 Reconfigure the system. Implement the series of tasks from upgrading the NAS
OS to setting up the functionality related to error
monitoring.
NAS07-1180
NAS07-1190 DKC515I
Replacing two PDEVs

(NAS OS LU: the same RAID group)
SVP, NAS frame:

Replace the failed PDEVs, and
release the RAID group's
blocked state.
[Replace the failed PDEV]
See [TRBL05-210].
Setup on SVP: CL1-CHA: NAS OS not running

Install NAS OS on CL1-CHA and CL2-CHA: NAS OS not running
CL2-CHA.*1
[NAS OS installation]
See 3.5.4 [2] [NAS03-400].
Setup on SVP:
Install NAS Blade Manager on
[NAS Blade Manager
installation] As in the new installation procedure,
See 3.5.4 [2] [NAS03-400]. see 3.4 On-Site Installation (On-Site
Setup) [NAS03-90], and see 3.5.2
Implementing Setup on SVP
[NAS03-110] through 3.6 Operations
NAS Management Console: Using the NAS Blade Manager GUI
Set up file sharing. [NAS03-1290] .

Set up the functionality related to
error monitoring.
Setup on SVP:
Acknowledge that the settings
have been completed, and that Phone, E-mail:
CL1-CHA has been started. Notify maintenance personnel
that the settings have been
completed, and that CL1/2-CHA
has been started.
NO Have the tasks CL2-CHA: NAS OS running
NAS Packages?
YES
Phone, E-mail: Phone, E-mail: CL1-CHA:Operations have restarted.

Notify a system administrator that Notify ordinary users that the CL2-CHA:Operations have restarted.
the PDEV replacement has been RAID replacement has been
completed. completed.
*1 After the expansion installation,
recover from the failure by upgrading
End the NAS OS to the version at the
time of failure occurrence.
Figure 7.7-6 Replacing Two PDEVs (NAS OS LU: When the NAS OS LUs for CL1-
CHA and CL2-CHA Belong to the Same RAID Group) (2/2)
NAS07-1190
NAS07-1200 DKC515I
7.7.7 Replacing Two PDEVs (NAS Cluster Management LUs)
CL1-CHA CL2-CHA
Pentium Pentium Backup LU of NAS CM LU
Restoration
MP MP MP MP Replacement

User LU
User LU
: Monitoring
: Failed part
Figure 7.7-7 Replacing Two PDEVs (NAS Cluster Management LUs) (1/4)

2 Release the RAID group’s blocked state.
3 Restart all NAS OSs. Restart NAS OS of each NAS package that makes
a cluster. CHN that has larger CHN number must
be restarted first. (CL2-CHA first, then CL1-CHA.)
Password input need at the time of OS restart.
4 Restore the NAS Cluster Management
LU.
5 Restart all NAS OSs.
6 Check whether the service IP address and If the service IP address and NFS share have not
NFS share have been restored. been restored, reset them.
NAS07-1200
NAS07-1210 DKC515I
Replacing two PDEVs (NAS Cluster Management LU)
Setup on SVP: Provided that the NAS Cluster Management LU is

Restart NAS OS of all NAS Packages. backed up when it is to be updated.
SVP, NAS frame:

Replace the failed PDEVs, and release
the RAID group's blocked state. All NAS Packages are stopped.
SIM = AC84X2
For details on the operations, see 3.5.13

Setup on SVP: Restoring NAS Cluster Management LU
Restart NAS OS of all NAS Packages. [NAS03-1040]
[Restore NAS cluster

management LU]
Setup on SVP: See 3.5.13[NAS03-1040].
Restore NAS cluster management LU.
Setup on SVP:
Restart NAS OS of all NAS Packages.
All NAS Packages are operating.
Phone, E-mail: Make sure that you use the same

Request to configure clusters. settings as the ones used to define the
Define setting information for all
Notify system administrator of NAS Package in the previous definition.
clusters.
completion of PDEV
replacement.
Check whether a failure
occurred using the
error-monitoring function of NAS
Blade Manager.
YES
Did a failure
occur?

NO Take appropriate actions
according to the message.
[NAS07-1211]
Figure 7.7-7 Replacing Two PDEVs (NAS Cluster Management LU) (2/4)
NAS07-1210
NAS07-1211 DKC515I

Make sure that, using the
interface management function
in the NAS Blade Manager
system settings, the service IP
addresses have been restored in
all clusters.
NO
The service IP
addresses have been
restored.

YES Using the interface management
function in the NAS Blade Manager
system settings, reset the service IP
address.

Using the interface management
function of NAS Blade Manager,
start the resource group of the
failure CHA after the cluster is
started.

Check whether a failure occurred
using the error-monitoring
YES
Did a failure
occur?
Take appropriate actions according
NO to the message.
[NAS07-1212]
NAS07-1211
NAS07-1212 DKC515I

Make sure that, using the file
sharing management function of
NAS Blade Manager, the NFS
shares have been restored in all
nodes.
The NFS shares NO

have been restored.

Using the file sharing management
YES function of NAS Blade Manager,
reset the NFS share.
Phone, E-mail: Phone, E-mail: Restart the operations of all

Acknowledge that the NAS Notify maintenance personnel NAS Packages.
Cluster Management LU has and ordinary users that the RAID
been restored. has been replaced.
END
NAS07-1212
NAS07-1220 DKC515I
7.7.8 Replacing Two PDEVs (Dump LUs)

User LU
User LU
Pentium Pentium
MP MP

SVP
Backup

Replacement
Figure 7.7-8 Replacing Two PDEVs (Dump LUs) (1/5)

1 Check the operating status of the NAS
Blade system.
3 Stop the node.
4 Release the setting of automatic save
of the NAS OS LU.
state.
7 Reboot the NAS OS.
8 Start the node.
9 Perform failback.
10 Back up NAS OS LU.
11 Change the setting of automatic save
of the NAS OS LU.
NAS07-1220
NAS07-1230 DKC515I
Replacing two PDEVs

(dump LU)
YES
Is failure CHA
stopped?

in 3.5.3 [NAS03-260].
[NAS07-1240]

node on failure CHA. Failing over from failure CHA to
NAS Management Console: normal CHA
from failure CHA to normal CHA, - NAS Blade Manager GUI
and confirm that the failover has (normal CHA notification)
been completed. - syslog (normal CHA notification)

failure CHA.

Acknowledge that the failover Notify maintenance personnel Normal CHA: Operating (Performing
has been completed, and the and ordinary users of the the operations of both
node on failure CHA has completion of failover and the CL1-CHA and CL2-CHA)
stopped. NAS Package location.
node has stopped] 'Browse Cluster Status' window
Confirm that the NAS OS of NAS Blade Manager GUI.
status is INACTIVE in the NAS Management Console:
‘Main’ window. See 3.5.3 Monitor the normal CHA's
[NAS03-260]. operations.
[NAS07-1240]
NAS07-1230
NAS07-1240 DKC515I

Ask the system administrator to Use NAS Blade Manager function
check the automatic save to check the automatic save
settings for the NAS OS LUs for settings for the NAS OS LUs for the
the normal CHA and failure normal CHA and failure CHA.
CHA.
Can the YES

automatic save settings
for the NAS OS LUs be checked
and are they
enabled? NAS Management Console:
Use NAS Blade Manager function to
NO disable the automatic save settings
for the NAS OS LUs for the normal
Phone, E-mail: CHA and failure CHA.
Confirm that the automatic save
settings for the NAS OS LUs on
the normal CHA and failure CHA Phone, E-mail:
have been checked. Notify the maintenance
personnel that the automatic
save settings for the NAS OS
SVP, NAS frame: LUs on the normal CHA and
Replace the failed PDEVs, and failure CHA have been checked.
release the RAID group’s
blocked state.
[Replace the failed PDEV]
See [TRBL05-210].
YES
Is the NAS OS
on failure CHA
stopped?

NO
See ‘Main’ window in
3.5.3[NAS03-260].
Failure recovery report
Setup on SVP: Setup on SVP: - SVP (CL1-CHA NAS OS report)
Reboot the NAS OS on failure CHA. Start the NAS OS on failure CHA. - SVP (SIM code ac88xa)
[Reboot NAS OS] [Start NAS OS] subcode (0x00020002)
See 3.5.8 [3][NAS03-840]. See 3.5.8 [2][NAS03-820].
Failure CHA: Restarting
SIM code (ac88xa) SIM code (ac88xa) Normal CHA: Operating
(subcode 0x00020002) (subcode 0x00020002) (Performing the operations of
appears here, but there is appears here, but there is both CL1-CHA and CL2-CHA)
no problem. no problem.
[NAS07-1250]
NAS07-1240
NAS07-1250 DKC515I
Phone, E-mail:
Notify a system administrator of Phone, E-mail:
the NAS Package location that Notify ordinary users of the
requires a failback, and ask to failback and get permission for it.
perform a failback.

failure CHA.
Failure recovery CHA:
NAS OS running
NAS Management Console: (Performing the
Use the NAS Blade Manager operations of both
functionality to perform a failback CL1-CHA and CL2-CHA)
from normal CHA to failure
recovery CHA, and confirm that Failing back from normal CHA to
the failback has been completed. failure recovery CHA
Failback notification
- NAS Blade Manager GUI (failure
Phone, E-mail: recovery CHA notification)
Phone, E-mail: - syslog (failure recovery CHA
and ordinary users of the notification)
has been completed and the
started. NAS Package location. CL1-CHA: Operating
CL2-CHA: Operating
node has started]
3.5.3 [NAS03-260].
[NAS07-1260]
NAS07-1250
NAS07-1260 DKC515I

Notify a system administrator of Notify ordinary users of the
the normal CHA location and ask storing the NAS OS LU and get
to store the NAS OS LU on permission for it.
normal CHA.*1

functionality to store the NAS OS
LU on normal CHA.

functionality to reset the existing
setting for the automatic storing
of NAS OS LU.
Phone, E-mail:
Phone, E-mail:
Acknowledge that the storing the
and ordinary users of the CL1-CHA: Operating
NAS OS LU on normal CHA has
completion of storing NAS OS CL2-CHA: Operating
been completed.
LU.
window of NAS Blade
Manager GUI.
End
CHA's operations.
*1 Request backup of the other NAS OS LU in the same

cluster as the failed NAS Package.
Figure 7.7-8 Replacing Two PDEVs (Dump LU) (5/5)
NAS07-1260
NAS07-1270 DKC515I
7.7.9 Replacing Two PDEVs (Error Information LUs)
CL1-CHA CL2-CHA
Pentium Pentium
Replacement
User LU
Command Device
User LU
User LU
: Monitoring
: Failed part
Figure 7.7-9 Replacing Two PDEVs (Error Information LUs) (1/2)

state.
NAS07-1270
NAS07-1280 DKC515I
Replacing two PDEVs

(error information LU)
CL1-CHA: Operating
CL2-CHA: Operating
SVP, NAS frame:

Replace the PDEVs, and release
the RAID group's blocked state.
End
Figure 7.7-9 Replacing Two PDEVs (Error Information LUs) (2/2)
NAS07-1280
NAS07-1290 DKC515I
7.7.10 Replacing Two PDEVs (Command Device)
CL1-CHA CL2-CHA
Pentium Pentium
User LU
Command Device
User LU
User LU
Replacement
: Monitoring
: Failed part
Figure 7.7-10 Replacing Two PDEVs (Command Devices) (1/2)

state.
3 Restart the snapshot and/or backup Restart if the snapshot and/or backup functions were
functions. running when the error occurred.
NAS07-1290
NAS07-1300 DKC515I
Replacing two PDEVs

(command device)
CL1-CHA: Operating
CL2-CHA: Operating
SVP, NAS frame:
Replace the PDEVs, and release
the RAID group's blocked state. CHA-1P to CHA-2Y:
The snapshot and backup
Replace the failed PDEV operations have stopped.
See [TRBL05-210].
Were the
snapshot and/or backup YES
functions running when the
error occurred?
Run the
NO snapshot/backup
functionality
Contact the system
administrator.

Notify a system administrator that Restart the snapshot and/or
the PDEV replacement has been backup functions.
completed, and request the system
administrator to restart the snapshot
and/or backup functions.

Confirm that the snapshot and/or Notify maintenance personnel
backup functions have been that the snapshot and/or backup
restarted and that the PDEV functions have been restarted.
replacement has been completed.
End
Figure 7.7-10 Replacing Two PDEVs (Command Device) (2/2)
NAS07-1300
NAS07-1310 DKC515I
7.7.11 Replacing Two PDEVs (Backup LUs of NAS Cluster Management LUs)
CL1-CHA CL2-CHA
Pentium Pentium
MP MP MP MP
Backup
Replacement
User LU
Command Device
User LU
User LU
: Failback
: Monitoring
: Failed part
Figure 7.7-11 Replacing Two PDEVs

(Backup LUs of NAS Cluster Management LUs) (1/3)

1 Release the setting of automatic save of
the NAS Cluster Management LU.
3 Save the NAS Cluster Management LU.
4 Change the setting of automatic save of
the NAS Cluster Management LU.
NAS07-1310
NAS07-1320 DKC515I
Replacing two PDEVs

(Backup LU of NAS Cluster Management LU)

check if the NAS Cluster functionality to check the
Management LU is automatically automatic save settings for the
saved. NAS Cluster Management LU.
Can the
settings be checked YES
and is the automatic save
for NAS CM LU
enabled? NAS Management Console:
NO Use the NAS Blade Manager
functionality to stop the automatic save
of NAS Cluster Management LU.
Phone, E-mail:
Confirm that the settings for the Phone, E-mail:
automatic save of NAS Cluster Notify maintenance personnel
Management LU have been that the settings for automatic
checked. save of NAS Cluster
Management LU have been
checked. CL1-CHA: Operating
CL2-CHA: Operating
SVP, NAS frame:
Replace the failed PDEVs.
Release the blocked state of the
RAID group.

Ask a system administrator to Notify ordinary users of the save
save the NAS Cluster of NAS Cluster Management LU
Management LU. and get permission for it.
[NAS07-1330]

NAS07-1320
NAS07-1330 DKC515I

functionality to save the NAS

functionality to reset the
automatic save of NAS

Acknowledge that NAS Notify maintenance personnel CL2-CHA: Operating
Cluster Management LU has and ordinary users of the
been saved. completion of the saving of
NAS Cluster Management
LU.
'Browse Cluster Status' window
End of NAS Blade Manager GUI.
Monitor the CL1(or 2)-CHA's
operations.

NAS07-1330
NAS07-1340 DKC515I
7.7.12 Replacing Data LAN Fiber Optic Cables (LAN Cables) or a Switch (When a Failure
Occurs)
Switch Replacement
Data LAN fiber optic cable

(LAN cable)
CL1-CHA CL2-CHA
Pentium Pentium Backup LU of NAS CM LU

MP MP MP MP NAS Cluster Management LU
NAS Error Information LU

SVP
Command Device
User LU
User LU
User LU
: Failover
: Failback
: Monitoring
Figure 7.7-12 Replacing Data LAN Fiber Optic Cables

(LAN Cables) or a Switch (When a Failure Occurs) (1/5)
1 Check the operation status of the NAS The data LAN fiber optic cables (LAN cables) here
Blade system. and switch include the cables shared by the data
LAN and control LAN.
2 Establish network connection for data Take corrective actions such as replacing the data
LAN fiber cable (LAN cable) and switch. LAN fiber optic cable (LAN cable), connecting it
to the port, repairing or replacing the switch, etc.
3 Check the network status. If the failover finished normally, perform step 4.
If the failover did not finish normally (the both
CHAs are link-down), perform step 4a.
4 Perform failback.
Recovery procedure when the failover did not finish normally (the both CHAs are link-down)
4a Perform a forced stop for the cluster and
then start them.
NAS07-1340
NAS07-1350 DKC515I
Replacing data LAN fiber optic cables (LAN

cables) or a switch (when a failure occurs)
[Failover finished normally]

If the system administrator does not contact you, check
if the SIM code ac84xF, which is sent when a failover
finishes successfully, and ac84xE, which is sent when a
failover finishes unsuccessfully, was issued following the
SIM code ac84x2, which is sent when a failover starts.
Did the failover Port link-down

finish normally? occurred for the both
NO CHAs in the cluster.
YES
NAS frame: 2 CL1-CHA: NAS OS running
Connect to the data LAN fiber CL2-CHA: Operating
optic cable (LAN cable) for (Performing the operations of
[NAS07-1360a] both CL1-CHA and CL2-CHA)
CL1-CHA to the port, replace it,
or repair or replace the switch.
SVP:
Make sure that the Port Status
is Link Up in the System
Equipment Status window of
the Web Console.

Ask the system administrator Confirm that ping to the NAS
to check the network status Package is successful. *1

Acknowledge that the Notify maintenance personnel
network status check on that the network status check
CL1-CHA has finished. has finished.
1
*1 Check that you can communicate
[NAS07-1360] using the fixed IP.
Figure 7.7-12 Replacing Data LAN Fiber Optic Cables (LAN Cables)
or a Switch (When a Failure Occurs) (2/5)
NAS07-1350
NAS07-1360 DKC515I
CL1-CHA: Stopped
CL2-CHA: Operating
Phone, E-mail: Phone, E-mail: CL1-CHA: NAS OS running

Notify a system administrator Notify ordinary users of the CL2-CHA: Operating
of the NAS Package location failback and get permission (Performing the operations of
that requires a failback and, for it. both CL1-CHA and CL2-CHA)
ask to perform a failback.
NAS Management Console: Failing back from CL2-CHA to

functionality to perform a
failback from CL2-CHA to Failback notification
CL1-CHA, and confirm that - NAS Blade Manager GUI
the failback has been (CL2-CHA notification)

and ordinary users of the CL1-CHA: Operating
has been completed. CL2-CHA: Operating
[Location of NAS Package]

window.
END NAS Management Console:
Monitor the operation of
CL1-CHA
Figure 7.7-12 Replacing Data LAN Fiber Optic Cables (LAN Cables)
NAS07-1360
NAS07-1360a DKC515I
NAS frame: CL1-CHA: NAS OS running

Connect the data LAN fiber CL2-CHA: NAS OS running
optic cables (LAN cable) for
CL1-CHA and CL2-CHA to the
ports, replace them, or repair
or replace the switch.
SVP:
the Web Console.


CL1-CHA and CL2-CHA has has finished.
finished.
3
*1 Check that you can communicate
[NAS07-1360b] using the fixed IP.

(LAN Cables) (When a Failure Occurs) (4/5)
NAS07-1360a
NAS07-1360b DKC515I


Notify a system administrator Notify ordinary users of the
of the NAS Package location forced stop and start of the
whose cluster requires forced cluster and get permission for
stop and start and ask to it.
perform a forced stop and
start.
functionality to perform a
forced stop for the cluster of
CL1-CHA and CL2-CHA and
then start it.
Phone, E-mail: CL1-CHA: Operating

Phone, E-mail: CL2-CHA: Operating
Acknowledge that the forced Notify maintenance personnel
stop and start of the cluster and ordinary users of the
has been completed. completion of the forced stop
and start of the cluster of
CL1-CHA and CL2-CHA and
[Location of NAS Package]

Browse Cluster Status window
END
Monitor the operation of

(LAN Cables) (When a Failure Occurs) (5/5)
NAS07-1360b
NAS07-1360A DKC515I
7.7.13 Replacing Control LAN Fiber Optic Cables (LAN Cable) or a Switch (When a Failure
Occurs)
Switch
Replacement
Control LAN Fiber Optic

Cable (LAN Cable)
CL1-CHA CL2-CHA
Pentium Pentium
User LU
Command Device
User LU
User LU
: Failover
: Failback
: Monitoring
Figure 7.7-13 Replacing Control LAN Fiber Optic Cables (LAN Cables)

1 Check the operation status of the NAS The control LAN is connected to the port (eth1)
Blade system. that is not used by users and therefore that a service
IP address is not set for.
2 Establish network connection for the Take corrective actions such as replacing the
control LAN fiber optic cable (LAN control LAN fiber optic cable (LAN cable),
cable) and switch. connecting it to the port, repairing or replacing the
switch etc.
NAS07-1360A
NAS07-1360B DKC515I
Replacing control LAN fiber optic

cables (LAN cables) or a switch
NAS frame: CL1-CHA: Operating

Connect to the control LAN CL2-CHA: Operating
fiber optic cable (LAN cable) for
CL1-CHA to the port, replace it,
or repair or replace the switch.
SVP:
the Web Console.


CL1-CHA has finished. has finished.
END *1 Check if you can communicate

using the fixed IP address.
Figure 7.7-13 Replacing Control LAN Fiber Optic Cables

(LAN Cables) or a Switch (When a Failure Occurs) (2/2)
NAS07-1360B
NAS07-1360C DKC515I
Rev.0 / Jun.2005 Copyright ©2005, Hitachi, Ltd.
7.7.14 Failure in Part of Trunking
Replacement
Data LAN Fiber Optic Cable

(LAN Cable)
CL1-CHA CL2-CHA
Pentium Pentium
NAS OS LU for CL1-CHA NAS Cluster Management LU


User LU
User LU
: Failover
: Failback
: Monitoring
Figure 7.7-14 Failure in Part of Trunking (1/2)

1 Check the operation status of the NAS The data LAN fiber optic cables (LAN cables) here
Blade system. and switch include the cables shared by the data
LAN and control LAN.
2 Establish network connection for the data Take corrective actions such as replacing the data
LAN fiber optic cable (LAN cable) and LAN fiber optic cable (LAN cable), connecting it
switch. to the port, repairing or replacing the switch, etc.
NAS07-1360C
NAS07-1360D DKC515I
Rev.0 / Jun.2005 Copyright ©2005, Hitachi, Ltd.
Failure recovery in partial trunking
SVP:
Identify the failed part in the Port
Status in the System Equipment CL1-CHA: Operating
Status window of the Web Console. CL2-CHA: Operating
NAS frame: Notify the completion of the

Connect to the data LAN fiber trunking recovery.
optic cable (LAN cable) for - SVP (SIM code: ac89x1)
CL1-CHA and CL2-CHA to the
port, or repair the switch.
SVP:
Web Console.
END
Figure 7.7-14 Failure in Part of Trunking (2/2)
NAS07-1360D
NAS07-1361 DKC515I
7.7.15 Failback (When a Failure Occurs)
CL1-CHA CL2-CHA
Pentium Pentium
User LU
Command Device
User LU
User LU
: Failback
: Monitoring
: Failed part
Figure 7.7-15 Failback (When a failure occurs) (1/2)

1 Start the NAS OS
2 Perform failback. The failure is automatically corrected.
NAS07-1361
NAS07-1362 DKC515I
Failback
(When a failure occurs)
Failure CHA: Stopped

Identify the failed NAS (Performing the operations of
Package from SIM/ACC/SSB. both CL1-CHA and CL2-CHA)
Setup on SVP:
Start the NAS OS of the failed
CHA.
[Start NAS OS]

See 3.5.8[2] [NAS03-820].

Notify a system administrator Notify ordinary users of the
of the NAS Package location failback and get permission Failing back from normal CHA to
that requires a failback and, for it. failure recovery CHA
ask to perform a failback.

functionality to check if the
node on the failure recovery
CHA is running. If it is not
running, start the node.

Use the NAS Blade Manager - NAS Blade Manager GUI
functionality to perform a (failure recovery CHA
failback from the normal CHA notification)
to the failure recovery CHA, - syslog
and that the failback has been (failure recovery CHA
completed. notification)

failure recovery CHA has completion of failback and the
[Acknowledge that the [Location of NAS Package]
node has started] Check CHA-xx displayed in
Confirm that the NAS Browse Cluster Status
Package status is ACTIVE window.
3.5.3 [NAS03-260].
END Monitor the operation of the
Figure 7.7-15 Failback (When a failure occurs) (2/2)
NAS07-1362
NAS07-1370 DKC515I
7.8 Upgrading Software

This section describes the software upgrade operations performed by maintenance personnel and
system administrators.
For procedures to go back to an earlier version when upgrade failed, see 7.9 Going Back to an
Earlier Software Version (When Upgrade Failed) [NAS07-1600].
[1] Types of Software Upgrade Operations
Software is upgraded in the following two situations (Note that all instances of the same software in
a cluster are upgraded because all the software running on NAS Packages in the same cluster must
be the same version.):
Upgrade when a software failure occurs

This upgrade operation upgrades the version of the failed software.
Upgrade during a preventive software upgrade

This upgrade operation upgrades during a preventive software upgrade.
This section shows the upgrade when a software failure occurs.

Such upgrade operations are classified based on the operations performed by maintenance
personnel or system administrators and the NAS Blade system behavior, as shown in Table 7.8-1.
NAS07-1370
NAS07-1380 DKC515I
Table 7.8-1 Types of Software Upgrade Operations

# Target Can Overview and Installation Distribu- Upgrade Is Restart Per- Reference
soft- ordinary Notice method tion target Operation the form a info. for
ware users method from the NAS fail- upgrade
continue NAS OS? back? during a
opera- manage- preventive
*2
tions? ment software
console upgrade
*
possible?
1
*2
1 NAS OS Yes FC of NAS OS. Upgrading CD Setup on No Yes Yes Figure
(Upgrade Failover , NAS OS NAS OS by an provided SVP 7.8-1
d while FC, and failback are Updated by the NAS
[NAS07-
running) performed. Version software Blade
1400]
Windows clients must developer Manager
be reconnected *3
Upgrading CD Setup on Yes No Yes Figure
because services are NAS OS by a provided SVP, 7.8-2
stopped. Patch Version by the NAS
[NAS07-
The same FC is (restart not software Blade
1440]
required for all NAS required) developer Manager
Packages in the same Upgrading CD Setup on Yes Yes Yes Figure
cluster. See the ECN NAS OS by a provided SVP,
for the procedures.
7.8-3
Patch Version by the NAS
[NAS07-
(restart required) software Blade
1500]
developer Manager
2 NAS Yes FC of NAS Blade NAS Blade CD Setup on Yes No No Figure
Blade Manager. Manager provided SVP, 7.8-4
Manager The same FC is upgrade by the NAS
[NAS07-
required for all NAS software Blade
1560]
Packages in the same developer Manager
cluster.
*3
3 Optional Yes FC of optional Optional CD Setup on Yes No No Figure
program program product. program provided SVP, 7.8-5
product The same FC is product by the NAS
[NAS07-
required for all NAS upgrade software Blade
1580]
Packages in the same developer Manager
cluster.
The target optional
program product must
be stopped.
*1: This is the upgrade operation that a system administrator performs using the NAS Management
Console.
*2: Yes: Operations is possible while online. However, if the application server is connected to
Windows client (CIFS share) when a failover or a failback occurs, the CIFS share is released.
Therefore, you must reconnect the server with CIFS share.
No: Offline. All applications must be stopped.
*3: Need for NAS OS restart or failback depends on the operation. See the ECN for the procedures.
NAS07-1380
NAS07-1390 DKC515I
[2] Procedures for Upgrading Software
following tables show the flowcharts for upgrading software when a software failure
occurs from Figure 7.8-1 to Figure 7.8-5.
Make sure that CL2-CHA is properly referred to as the actual location for upgrading
software when a software failure occurs on the CHA location.

Option 1 1F 2R
Option 2 1G 2T
Option 3 1H 2U
NAS07-1390
NAS07-1400 DKC515I
7.8.1 Upgrading the NAS OS By an Update Version (When a Failure Occurs)
CL1-CHA CL2-CHA

Product
Pentium Product
Pentium

Update
MP NAS OS MP MP NAS OS MP Backup LU of NAS CM LU

User LU
Corrected User LU
version
: Failover
: Failback
: Monitoring
: Failed part
Figure 7.8-1 Upgrading the NAS OS By an Update Version

(When a Failure Occurs) (1/4)

1 Obtain the corrected version of NAS OS.
2 Start the NAS OS. Do so if the NAS OS is not running.
3 Stop the node.
4 Upgrade the NAS OS by an update version.
6 Start the node.
7 Set back the automatic save settings for the
NAS OS LU and NAS Cluster Management
LU to the ones before the failure occurred.
8 Perform failback.
Before you start replacing the NAS OS for CL2-CHA by using a method similar to that for CL1-
CHA, after the CL1-CHA processing has finished you need to manually perform failover from
CL2-CHA to CL1-CHA.
NAS07-1400
NAS07-1410 DKC515I
Upgrading the NAS OS by an update

version (when a failure occurs)
Postal service, etc.:

Obtain the new version from
the software developer.
Failure CHA: NAS OS not running

Setup on SVP: (Performing the
Start the NAS OS of failure operations of both
CHA. CL1-CHA and CL2-CHA)
a Start NAS OS.
See 3.5.8 [2][NAS03-820].
YES
Is CL1(or 2)-CHA node 1
stopped?
[NAS07-1420]
NO
[Is the node stopped?]
Package status is INACTIVE
3.5.3 [NAS03-260].
Phone, E-mail: Phone, E-mail: CL1(or 2)-CHA: Operating

Notify a system administrator of Notify ordinary users of the
CL2(or 1)-CHA: Operating
perform a failback.
NO
Is the failover
permitted?
YES Failover from CL2(or 1)-CHA
NAS Management Console: to CL1(or 2)-CHA
from CL2(or 1)-CHA to CL1(or
2)-CHA, and confirm that the
failover has been completed. (CL2(or 1)-CHA notification)
- syslog (CL1(or 2)-CHA
notification)
function to stop the node on
CL2(or 1)-CHA.
[NAS07-1420]
NAS07-1410
NAS07-1420 DKC515I
Phone, E-mail:
Acknowledge that the failover Phone, E-mail:
has been completed and the Notify maintenance personnel
node on CL1(or 2)-CHA is and ordinary users of the
stopped. completion of failover and the
node has stopped] [NAS Package location]
Confirm that the NAS Check CHA-xx displayed
1 Package status is in the ‘Browse Cluster
INACTIVE in the ‘Main’ Status’ window of the
window. See 3.5.3 NAS Blade Manager.
[NAS03-260].
Setup on SVP:
Upgrade the NAS OS on NAS Management Console:
CL1(or 2)-CHA.*1 Monitor CL1(or 2)-CHA’s
operations.
[Upgrading NAS OS]
See 5.3.2 [1]
[NAS05-570].
CL1(or 2)-CHA: NAS OS
NO running
Upgraded CL2(or 1)-CHA: Operating
successfully? (Performing the
Try upgrading
operations of both
YES [Was the upgrade successful?] CL1-CHA and
Check if the status displayed in CL2-CHA)
‘Install Progress’ window in 5.3.2
[1] (9) [NAS05-660] is ‘Completed’.
Setup on SVP:
Upgrade NAS/Management
on CL1(or 2)-CHA.*1
[Upgrade NAS Blade Manager]
See 5.3.2 [3] [NAS05-720].
Phone, E-mail:
Notify that CL1(or 2)-CHA has
been started.
*1: NAS OS and NAS Blade

3 Manager can be upgraded
simultaneously.
[NAS07-1430]

NAS07-1420
NAS07-1430 DKC515I
CL1(or 2)-CHA: NAS OS running

Phone, E-mail: (Performing the operations
Notify ordinary users of a of both CL1-CHA and
failback and get permission for CL2-CHA)
it.

CL1(or 2)-CHA.

functionality to set back the
automatic save settings for the
[NAS07-1410] NAS OS LU and NAS Cluster
Management LU to the ones
a before the failure occurred.
NAS Management Console: Failing back from CL2(or 1)-CHA to

Use the NAS Blade Manager CL1(or 2)-CHA
Perform the same
operations for functionality to perform a manual Failback notification
CL2-CHA. failback from CL2(or 1)-CHA to - NAS Blade Manager GUI
CL1(or 2)-CHA, and confirm that (CL1(or 2)-CHA notification)
the failback has been completed. - syslog (CL1(or 2)-CHA notification)

has been completed and that the and ordinary users of the
CL1 (or 2)-CHA node has started. completion of failback and the CL1-CHA: Operating
NAS Package location. CL2-CHA: Operating
node has started]
window of NAS Blade
3.5.3 [NAS03-260].
Manager GUI.
NO NAS Management Console:

Have the tasks
Monitor the normal CHA's
been completed for both operations.
NAS Packages?
YES [Have both NAS

Packages completed?]
See the ‘Program
Install’ window in 5.3.2
[2] (8) [NAS05-700].
End

NAS07-1430
NAS07-1440 DKC515I
7.8.2 Upgrading the NAS OS By a Patch Version  Restarting the NAS OS Is Not Required
Corrected
version
CL1-CHA CL2-CHA
NAS
Mangement
Product
Pentium Product
Pentium
Update MP NAS OS MP MP NAS OS MP Backup LU of NAS CM LU

by a Backup LU of NAS CM LU
patch
version

SVP
(Maintenance Error Information LU
Personnel)

User LU
Corrected User LU
version
: Failover
: Failback
: Monitoring
: Failed part
Figure 7.8-2 Upgrading the NAS OS By a Patch Version 

Restarting the NAS OS Is Not Required (When a Failure Occurs) (1/5)
NAS07-1440
NAS07-1450 DKC515I
When maintenance personnel perform the upgrade operations:

1 Obtain the corrected NAS OS version (patch
version).
2 Start the NAS OS. Do this for the NAS OS of the NAS
Package in which the error occurred.
3 Upgrade to the corrected NAS OS version. Use the Setup on SVP functionality to
upgrade.
4 Set back the automatic save settings for NAS
OS LU and NAS Cluster Management LU to
the ones before the failure occurred.
5 Perform failback.
When system administrators perform the upgrade operations (operations using NAS
Management Console):
version).
2 Start the NAS OS. Do this for the NAS OS of the NAS
Package in which the error occurred.
3 Upgrade to the corrected NAS OS version Use NAS Blade Manager functionality to
(patch version). upgrade.
4 Set back the automatic save settings for NAS
OS LU and NAS Cluster Management LU to
the ones before the failure occurred.
5 Perform failback.
CHA, after the CL1-CHA processing has finished you need to manually perform failover from
CL2-CHA to CL1-CHA.
NAS07-1450
NAS07-1460 DKC515I
Upgrading the NAS OS by a patch version  Restarting

the NAS OS is not required (when a failure occurs)
Are program Failure CHA: NAS OS not

products managed by running
maintenance NO Normal -CHA: Operating
personnel? (Performing the
operations of both
YES CL1-CHA and
CL2-CHA)
Postal service, etc.: Phone, E-mail:
Obtain the new version from the Ask system administrator to
1
software developer. upgrade NAS OS by a patch
version.
Setup on SVP:
Start the NAS OS on failure
CHA, from the SVP.
[Start NAS OS] 1

See 3.5.8[2] [NAS03-820].
[NAS07-1470]
a
Setup on SVP:
Update the NAS OS on CL1(or
2)-CHA by upgrading to the
patch version from the SVP.
[Upgrade NAS OS]

See 5.3.2 [2] [NAS05-670].
Try upgrading
again.
Has the upgrade

finished successfully?
NO
[Finish the upgrade]

YES The status in ‘Install Progress’
window becomes Completed.
See 5.3.2 [1] (9) [NAS05-660].
[NAS07-1480]

NAS07-1460
NAS07-1470 DKC515I
Postal service, etc.:

software developer.

Start the NAS OS on CL1(or Ask maintenance personnel to
2)-CHA. start the NAS OS on CL1(or
2)-CHA.
[Start NAS OS]

See 3.5.8[2] [NAS03-820].
Phone, E-mail:
Notify system administrator that
the NAS OS has started CL1(or 2)-CHA: NAS OS
successfully. running
b (Performing the
operations of both
CL1-CHA and
NAS Management Console: CL2-CHA)
functionality to update the NAS
OS on CL1(or 2)-CHA by
upgrading to the patch version.
See 6.2.1 (3) in the NAS
Blade Manager User’s
Guide.
Has the upgrade NO

finished successfully? Try upgrading
again.
YES
[NAS07-1490]

NAS07-1470
NAS07-1480 DKC515I

Notify a system administrator of Set back the automatic save
the NAS Package location that settings for the NAS OS LU and
requires a failback, check the NAS Cluster Management LU to
automatic save settings for the the ones before the failure
NAS OS LU and NAS Cluster occurred.
Management LU, and ask to
perform a failback.
Phone, E-mail: CL1(or 2)-CHA: NAS OS

Notify ordinary users of the running
failback and get permission for it. CL2(or 1)-CHA: Operating
(Performing the
operations of both
[NAS07-1460] Failing back from CL2(or 1)-CHA to

CL1(or 2)-CHA
a functionality to perform a manual Failback notification
failback from CL2(or 1)-CHA to - NAS Blade Manager GUI
CL1(or 2)-CHA, and confirm that (CL1(or 2)-CHA notification)
the failback has been completed. - syslog (CL1(or 2)-CHA notification)
Perform the same
operations for CL2-CHA. [NAS Package location]
However, the failback Check CHA-xx displayed in
operation described in the 'Browse Cluster Status'
[NAS07-1480] is not window of NAS Blade
necessary. Manager GUI.
has been completed. and ordinary users of the
Have the tasks been

completed for both NAS
NO Packages?
[Have both NAS Packages been
YES upgraded?]
See the ‘Program Install’ window
in 5.3.2 [2] (8) [NAS05-700].
End

NAS07-1480
NAS07-1490 DKC515I

NAS OS LU and NAS Cluster
before the failure occurred.
Phone, E-mail: CL1(or 2)-CHA: NAS OS running

Notify ordinary users of the CL2(or 1)-CHA: Operating
failback and get permission for it. (Performing the
operations of both
CL1-CHA and
CL2-CHA)

Use the NAS Blade Manager CL1(or 2)-CHA
functionality to perform a manual
failback from CL2(or 1)-CHA to Failback notification
CL1(or 2)-CHA, and confirm that
the failback has been completed. (CL1(or 2)-CHA notification)

[NAS07-1470] NAS Package location.

b Check CHA-xx displayed
in the 'Browse Cluster
Status' window of NAS
Perform the same Blade Manager GUI.
operations for CL2-CHA.
However, the failback
operation described in Have the tasks been
[NAS07-1480] is not completed for both NAS
necessary. NO Packages?
YES
End

NAS07-1490
NAS07-1500 DKC515I
7.8.3 Upgrading the NAS OS By a Patch Version  Restarting the NAS OS Is Required (When
a Failure Occurs)
Corrected
version
CL1-CHA CL2-CHA
NAS Optional Program Optional Program

Product
Pentium Product
Pentium
Management
Console
NAS Blade Manager NAS Blade Manager Backup LU of NAS CM LU
Update MP NAS OS MP MP NAS OS MP Backup LU of NAS CM LU

by a
patch
version NAS Cluster Management LU

(Maintenance
Personnel)
Command Device
User LU
User LU
Corrected User LU
version
: Failover
: Failback
: Monitoring
: Failed part

Restarting the NAS OS Is Required (When a Failure Occurs) (1/6)

version).
2 Start the NAS OS. Do this for the NAS OS of the NAS Package in
which the error occurred.
3 Upgrade to the patch version of NAS OS.
4 Stop the node.
5 Restart the NAS OS. Do this only if it is upgraded to the patch version
using the NAS Blade Manager functionality.
6 Start the node.
7 Set back the automatic save settings for the
NAS OS LU and NAS Cluster Management
LU to the ones before the failure occurred.
8 Perform failback.
CHA after the CL1-CHA processing has finished, you need to manually perform failover from
CL2-CHA to CL1-CHA.
NAS07-1500
NAS07-1510 DKC515I
Replacing the NAS OS by a patch version  Restarting

the NAS OS is required (when a failure occurs)
Are program
products managed by Failure CHA: NAS OS not running
maintenance Normal CHA: Operating
personnel? NO (Performing the
operations of both
YES CL1-CHA and CL2-CHA)
Postal service, etc.: Phone, E-mail:

Obtain the new version from the Ask system administrator to
software developer. upgrade to the patch version of
NAS OS.
Setup on SVP:
Start the NAS OS on failure CHA.
1
[Start NAS OS]
See 3.5.8 [2] [NAS03-820].
a [NAS07-1520]
Setup on SVP:
Upgrade the NAS OS on CL1(or
2)-CHA by a patch version from
the SVP.
[Update NAS OS]

See 5.3.2 [2] [NAS05-670].
Try upgrading
again.
Has the upgrade
finished successfully?
NO
YES [Has the NAS OS been

upgraded?]
The status in ‘Install Progress’
See 5.3.2 [1] (9) [NAS05-660].
[NAS07-1530]

NAS07-1510
NAS07-1520 DKC515I
Postal service, etc.: CL1(or 2)-CHA: NAS OS not

Obtain the new version from the running
software developer. CL2(or 1)-CHA: Operating
(Performing the
operations of both
Start the NAS OS on CL1(or 2)-CHA. Ask maintenance personnel to start
the NAS OS.
[Start NAS OS]
See 3.5.8[2] [NAS03-820].
Phone, E-mail:
Notify system administrator that the
NAS OS has started.

[Finish the NAS OS startup] CL2(or 1)-CHA: Operating
The ENS3540i message (Performing the
appears. operations of both
b CL1-CHA and CL2-CHA)

functionality to upgrade the NAS
OS on CL1(or 2)-CHA to the
patch version.
See 6.2.1 (5) in the NAS
Blade Manager User’s
Guide.
Has the upgrade

finished successfully? Try upgrading
again.
NO
YES
[NAS07-1550]

NAS07-1520
NAS07-1530 DKC515I
YES
Is CL1(or 2)-CHA
node stopped? 3
[Is the node stopped?] [NAS07-1540]

NO
Check if the NAS
Package status is
INACTIVE in the ‘Main’
window. See 3.5.3
[NAS03-260].
Phone, E-mail: NAS Management Console: CL2(or 1)-CHA: Operating
Request a system administrator Use the NAS Blade Manager (Performing the
to stop the node on CL1(or functionality to stop the node on operations of both
2)-CHA. CL1(or 2)-CHA if it is active. CL1-CHA and CL2-CHA)

Confirm that the node on CL1(or Notify maintenance personnel
2)-CHA is stopped. that the node on CL1(or 2)-CHA
is stopped.
node has stopped]
Package status is
INACTIVE in the ‘Main’
window. See 3.5.3
[NAS03-260].
[NAS07-1540]
NAS07-1530
NAS07-1540 DKC515I
CL1(or 2)-CHA: NAS OS restarting

Setup on SVP:
Reboot the NAS OS on CL1 (or
(Performing the
2)-CHA.
operations of both
[Reboot the NAS OS]
See 3.5.8 [3] [NAS03-840].

Notify the system administrator Use the NAS Blade Manager
of the completion of reboot of the functionality to start the CL1 (or
NAS OS on CL1 (or 2)-CHA and 2)-CHA node.
the location of the NAS Package
to perform failback and request
failback, and check the
Management LU.

a Use the NAS Blade Manager CL1(or 2)-CHA
[NAS07-1510] functionality to perform a manual
failback from CL2(or 1)-CHA to
Perform the same CL1(or 2)-CHA, and confirm that Failback notification
operation for the failback has been completed. - NAS Blade Manager GUI
CL2-CHA. (CL1(or 2)-CHA notification)
CL1 (or 2)-CHA node has completion of failback and the
[Acknowledge that the node has [NAS Package location] CL1-CHA: Operating
started] Check CHA-xx displayed CL2-CHA: Operating
Confirm that the NAS Package in the 'Browse Cluster
status is ACTIVE in the ‘Main’ Status' window of NAS
window. See 3.5.3 [NAS03-260]. Blade Manager GUI.
Have the tasks been

NO Packages?
YES [Have both NAS Packages

been upgraded?]
See the ‘Program Install’ in
5.3.2 [2] (8) [NAS05-700].
End

NAS07-1540
NAS07-1550 DKC515I

4 CL2(or 1)-CHA: Operating
(Performing the
operations of both
NAS Management Console: CL1-CHA and CL2-CHA)
functionality to check if the node
on CL1(or 2)-CHA is stopped. If
not, Stop the node. CL1(or 2)-CHA: Restarting
(Performing the
NAS Management Console: operations of both
Reboot the NAS OS on CL1(or CL1-CHA and CL2-CHA)
2)-CHA.

CL1(or 2)-CHA from CL2(or Failing back from CL2(or 1)-CHA to
1)-CHA. CL1(or 2)-CHA

Phone, E-mail:
Phone, E-mail: Failback notification
Acknowledge that the failback has - NAS Blade Manager GUI
been completed and that the (CL1(or 2)-CHA notification)
CL1-CHA (or 2) node has started. completion of failback and the
NAS Package location. - syslog (CL1(or 2)-CHA notification)

Check CHA-xx displayed in the 'Browse Cluster
Status' window of NAS Blade Manager GUI.
Use the NAS Blade Manager CL1-CHA: Operating
[NAS07-1520] CL2-CHA: Operating
functionality to perform a manual
failback from CL2(or 1)-CHA to
b CL1(or 2)-CHA, and confirm that
Perform the
same operations
for CL2-CHA. Have the tasks
NO NAS Packages?
YES
End

NAS07-1550
NAS07-1560 DKC515I
7.8.4 Upgrading NAS Blade Manager (When a Failure Occurs)
CL1-CHA CL2-CHA

Product
Pentium Product
Pentium
Update


SVP
(Maintenance
Personnel)

User LU
Corrected User LU
version
: Monitoring
: Failed part
Figure 7.8-4 Upgrading NAS Blade Manager (When a Failure Occurs) (1/2)

1 Obtain the corrected version of NAS Blade
Manager.
2 Upgrade to the corrected version of NAS Blade
Manager.
NAS07-1560
NAS07-1570 DKC515I

System administrator operations

are not possible because of a
Postal service, Web site, etc.: CL1-CHA: Operating
NAS Blade Manager failure.
Obtain the new version from the CL2-CHA: Operating
software developer, or copy the new
version from the Web site to a CD.
Setup on SVP:
Upgrade NAS Blade Manager on
CL1(or 2)-CHA by the update version
from the SVP.
[Upgrade NAS Blade
Manager]
See 5.3.2[3] [NAS05-720].
Try upgrading
again.
Has the upgrade finished
successfully? NO
YES [Has the upgrade finished?]

The status in 'Install Progress'
Perform the same See 5.3.2 [1] (9) [NAS05-660]
operations for
CL2-CHA.
NO
Have the tasks been
Packages?
YES [Have both NAS Packages

been upgraded?]
See the ‘Program Install’ in
5.3.2 [2] (8) [NAS05-700].
Phone, E-mail:
completion of NAS Blade
Manager upgrade.
End
Recognize that NAS Blade
Manager has been upgraded.
Figure 7.8-4 Upgrading NAS Blade Manager (When a Failure Occurs) (2/2)
NAS07-1570
NAS07-1580 DKC515I
7.8.5 Upgrading an Optional Program Product (When a Failure Occurs)
Corrected
version
CL1-CHA CL2-CHA
NAS
Management
Product
Pentium Product
Pentium
Update


SVP
(Maintenance
Personnel)

User LU
Corrected User LU
version
: Monitoring
: Failed part
Figure 7.8-5 Upgrading an Optional Program Product (When a Failure Occurs) (1/2)

1 Obtain the corrected version of an optional
program product.
2 Upgrade to the new version of an optional
program product.
NAS07-1580
NAS07-1590 DKC515I
Upgrading an optional program product (when a

failure occurs)

Are program (The optional features
products managed by are not operating.)
maintenance NO Normal CHA: Operating
personnel?
YES
Postal service, etc.: Postal service, etc.:

Obtain the new version from the Obtain the new version from the
software developer. software developer.
Setup on SVP: NAS Management Console:

Upgrade the optional program Use the NAS Blade Manager
product on CL1(or 2)-CHA with functionality to upgrade the
the update version from the SVP. program product by the update
version.
Upgrade optional
program products
See 5.3.2[4]
[NAS05-760].
Try upgrading Try upgrading
again. again.
Has the upgrade
finished successfully? NO Has the upgrade
finished successfully? NO
YES [Has the upgrade finished?]
YES
The status in 'Install
Perform the same Completed. See 5.3.2[1](9) Perform the same
operations for [NAS05-660]. operations for
CL2-CHA. CL2-CHA.
Have the tasks been
completed for both NAS Have the tasks been
NO completed for both NAS
Packages? NO
Packages?
YES
Phone, E-mail: YES
Notify system
administrator of
completion of optional
program product upgrade.
Recognize that the optional program

product has been upgraded.
End End
Figure 7.8-5 Upgrading an Optional Program Product (When a Failure Occurs) (2/2)
NAS07-1590
NAS07-1600 DKC515I
7.9 Going Back To an Earlier Software Version (When Upgrade Failed)

This subsection describes the tasks of the maintenance personnel and system administrator when
they roll back to an earlier software version. Before updating software, and when the settings are
added, deleted, or changed by the NAS Blade Manager GUI, the system administrator should make
a backup of the NAS OS LU by using the NAS OS LU save/recovery functionality of NAS Blade
Manager. If the upgrade fails, use the following procedure to go back to the previous version.
CAUTION
When you downgrade software, contact the Technical Support Division (TSD) and
perform operations according to its instructions.
The NAS Blade system does not provide the functionality to go back to an earlier update version.
To go back to a previous software version:
7.9.1 To Go Back To an Earlier Version of the NAS OS

(1) When the NAS OS LU, NAS Cluster Management LU and user LU Have Been Backed Up
Restore NAS OS LU [NAS03-990] and NAS Cluster Management LU [NAS03-1040] by using
the NAS OS LU save/recovery functionality. Ask a system administrator to restore user LU.
You can go back to an earlier version of NAS Blade Manager and an optional program product
by this procedure.
(2) When the NAS OS LU, NAS Cluster Management LU and user LU Have Not Been Backed Up
Perform an expansion installation of the NAS OS [NAS03-400] to install the earlier version to
overwrite the current version [NAS05-130][NAS05-220], until you reach the target version
you want.
Upgrade the version of NAS Blade Manager and an optional program product to an earlier
version [NAS05-500][NAS05-520] at this time.
7.9.2 To Go Back To an Earlier Version of NAS Blade Manager

Upgrade the version of NAS Blade Manager to an earlier version [NAS05-500].
To go back to an earlier version of NAS Blade Manager, you also need to go back to an earlier
version of the NAS OS. After going back to an earlier version of the NAS OS, as described in
7.9.1, upgrade the target version of NAS Blade Manager.
7.9.3 To Go Back To an Earlier Version of an Optional Program Product

Upgrade the version of an optional program product to an earlier version [NAS05-520].
To go back to an earlier version of an optional program product, you also need to go back to an
earlier version of the NAS OS. After going back to an earlier version of the NAS OS, as
described in 7.9.1, upgrade the target version of an optional program product.
NAS07-1600
NAS08-10 DKC515I
8. Setup Procedures When Implementing NAS Blade System for the First
Time
In this section both new installation (the configuration is set in the factory) and on-site installation
(the configuration is set at the customer’s site) procedures are described.
The following setup procedures must have been completed before performing operations described
in this section.
• Definition of NAS system LUs
• Installation of Setup on SVP, NAS OS, and related optional program products
Each setting should be carefully entered as indicated in the System Assurance Documentation.
For new installation of DKC and NAS Blade system, procedures described in section 8.1
Operations Using the SVP [NAS08-20] and 8.2 Operations Using the NAS Blade Manager GUI
[NAS08-210] have already been performed by the manufacturer, therefore maintenance personnel
need to perform operations described in section 8.3 Confirmation of the settings [NAS08-400] only.
For on-site installation of NAS Blade system, maintenance personnel need to perform all operations
described in 8.1 Operations Using the SVP [NAS08-20] through 8.3 Confirmation of the settings
[NAS08-400].
Detailed procedures are described in the following sections.
NAS08-10
NAS08-20 DKC515I
8.1 Operations Using the SVP

[1] Setting up the network environment----------------------------------------------------- NAS08-20
[2] Setting the license of NAS Blade Manager -------------------------------------------- NAS08-160
[1] Setting up the network environment

The network information, such as the NTP server corresponding to the NAS Package and the
fixed IP address of the NAS Package NIC, will be configured.
CAUTION
-The IP addresses of the following networks must not be used. The following networks
are reserved in the subsystem. Please contact the Technical Support Division if you
need to use these IP addresses.
- from 172.29.1.0/24 to 172.29.4.0/24, and
- the networks of the IP addresses set for the SVP.
-The reserved words for NAS Blade systems cannot be used for a channel adapter name.
Note that these words are not case-sensitive.
Table 8.1-1 shows the reserved words for NAS Blade systems.
Table 8.1-1 List of Reserved Words in NAS Blade Systems

Classification Reserved words
A add, admin
C CLU_partition, cluster
D define, delete
F Failover_policy, Filesystem, for, force
H ha_parameter, ha_services, hostname
I in, IP_address
L localhost, log_group, LVM_volume
M maintenance_off, maintenance_on, modify, move
N nasos, NFS, NFS_admin, node
O offline, online
R remove, resource, resource_group, resource_type
S set, show, start, status, stnet_xxx*1, stop
T to
Symbol . (one period), .. (two periods)
*1: Any word starts with stnet_
NAS08-20
NAS08-30 DKC515I
[1-1] Connecting the Fibre optic cables (LAN cables)

Connect the Fibre optic cables (LAN cables) to the ports on the NAS Packages.
(1) Connect the Fibre optic cables (LAN cables) to the port eth1, for which the Service IP Address
is specified in the System Assurance Documentation, of all the NAS Packages composing a
cluster. When the two or more clusters exist, also connect the Fibre optic cables (LAN cables)
to all the NAS Packages that are components of all the clusters.
Table 8.1-1A shows the correspondence of eth1 and port numbers of each NAS package.
Table 8.1-1A Correspondence of eth1 and port numbers of NAS packages

NAS package eth1
Option-1 CHA-1B 1E
CHA-2E 2E
(2) Connect connectors at the opposite ends of the Fibre optic cables (LAN cables) to devices such
as the LAN switches, routers, and clients that are in operation. Then make sure that the lamps
of the ports on the NAS Packages are lit indicating that the Packages are linked up.
CAUTION
If the Fibre optic cable (LAN cable) is disconnected from the port, for which the Service IP
Address on the NAS Package has been specified, when a cluster is being configured or
after a cluster is activated, a failover will occur in the NAS cluster and it may take a long
time for recovery. Therefore, do not disconnect the Fibre optic cable (LAN cable) which
has been connected while the cluster is being configured or the cluster is activated.
NAS08-30
NAS08-40 DKC515I
[1-2] To set up the network environment:
(1) Change SVP mode from View Mode to Modify Mode.
(2) Click the NAS Setup button, and then the ‘NAS Setup on SVP (Main)’ window appears. In
the ‘NAS Setup on SVP (Main)’ window select the NAS Package (INACTIVE status), and
then click the Setting button.
(3) Enter the required information according to System Assurance Documentation, and then click
the Setup button.
CAUTION
- In CHA Name, specify a unique name in the disk subsystem.
- Specify values for IP Address so that the displayed ports are not in the same network.
- Be sure to enter all the items except Server 2 in NTP Server.
- In NTP Server, specify the same value for each NAS Package comprising the cluster.
- If a wrong IP address is specified for the NTP Server or when no NTP server is
connected to the network, the SIM (ac88xa that means that the NTP server cannot be
connected) will be issued when the NAS OS is restarted. Further, the date when
(Available From) the license to use the NAS PP becomes effective may be advanced or
delayed by one day because the time of the NAS OS may not be set correctly.
- The NTP server to be specified for NTP Server must be in a network that can
communicate within 90 seconds after each port is linked up.
Check with the system administrator beforehand to make sure that the NTP server is
placed in a network that can communicate within 90 seconds after the ports are linked up.
Table 8.1-2 shows the settings (network information) in the ‘Setting’ window.
NAS08-40
NAS08-50 DKC515I
Rev.2 / Jun.2005, Dec.2005 Copyright © 2005, Hitachi, Ltd.
Table 8.1-2 Settings in the ‘Setting’ Window

Item Description
CHA Name Specify a name that is unique in the disk subsystem. (Required) Take special care to input
CHA Name since it cannot be modified once the cluster is configured.
IP Address Set the IP address unique to the NIC of the NAS Package. Specify values in the way that
one displayed port is not in the same network as the other. (Required)
Network Mask Set network mask for the IP address. (Required)
MTU Specify a MTU value (IP packet data size). (Specifiable range: 1500-16100, the default is
1500) (Required)
NTP Server1/ The IP address and host name for the NTP server can be specified (Server 1 is required:
Server Server2 After the cluster is defined, you cannot change the value from this window. However, you
can change it using the NAS Blade Manager function while the cluster is stopped, even
after the cluster is defined.).
Confirm the setting contents again, and then click the OK button in the message window.
The settings are applied.
(5) When the setting contents are changed, the message “The setup ended normally.” is displayed.
(7) Ask the customer to confirm that access to the NTP server that was set in Step (3) is really
possible and the time of the NAS Package is in the state in which it can be synchronous with
that of the NTP server.
(8) Restart the NAS OS of the operated NAS Package. For details, see 3.5.8 [3] Restarting the
NAS OS [NAS03-840].
NAS08-50
NAS08-60 DKC515I
(9) Repeat through step (1) to step (8) to each newly installed or expanded NAS Package.
When the operation is finished, go to Item [2], “Setting the license of NAS Blade Manager (on
page [NAS08-160]).
NAS08-60
NAS08-70 DKC515I
Blank Sheet
NAS08-70
NAS08-80 DKC515I
Blank Sheet
NAS08-80
NAS08-90 DKC515I
Blank Sheet
NAS08-90
NAS08-100 DKC515I
Blank Sheet
NAS08-100
NAS08-110 DKC515I
Blank Sheet
NAS08-110
NAS08-120 DKC515I
Blank Sheet
NAS08-120
NAS08-130 DKC515I
Blank Sheet
NAS08-130
NAS08-140 DKC515I
Blank Sheet
NAS08-140
NAS08-150 DKC515I
Blank Sheet
NAS08-150
NAS08-160 DKC515I
[2] Setting the license of NAS Blade Manager

To use the license key to set up the license for an optional program product:
The ‘License Management’ window appears.
NAS08-160
NAS08-170 DKC515I

In the ‘NAS Setup on SVP (License Management)’ window, enter the license key in Key
Code:, and then click the Accept button.
Go to step (5).
To use the license key file, click the Key File button, and then go to step (3).
CAUTION
You must install the same version of optional program products in the NAS Packages
comprising the same cluster, and set the license to all NAS Packages in that cluster.
If the version or license of the installed optional program products is different between the
NAS Packages in a cluster, they cannot be used in both NAS Packages in that cluster.
Table 8.1-3 shows the information to be set in the ‘License Management’ window.
Table 8.1-3 Listed items in the ‘License Management’ window

Item Description
License List The existing licenses are listed. Double-clicking the first item or
clicking the Detail button displays the ‘License Setting‘ window.
Accept Entering a license key enables this button. Clicking this button
displays the ‘License Setting‘ window.
Key Code: Enter a license key.
Key File Clicking this button displays the ‘Select a License Key
File‘ window.
NAS08-170
NAS08-180 DKC515I
(3) In the ‘NAS Setup on SVP (License Management)’ window, click the Key File button.
The ‘Select a License Key File’ window is displayed.
Select a license key file (.plk), and then click the Open button.
In the ‘NAS Setup on SVP (License Key File)’ window, select NAS Blade Manager, and
then click the Accept button.
NAS08-180
NAS08-190 DKC515I

In the ‘NAS Setup on SVP (License Setting)’ window, under Distribution, select the
cluster to which the license is to be assigned, and then click the Accept button.
Table 8.1-4 Listed items in the ‘License Setting’ window

# Item Description
1 Program Product Name Displays product name that are either selected in the
License List window or specified by entering the
license key.
2 License Type Displays product type that are either selected in the
License List window or specified by entering the
license key.
3 Term of validity For a permanent license, the Term of validity box
displays - and the Remaining License box displays
Remaining License the remaining licenses.
For temporary and emergency licenses, the Term of
validity box displays the time limit for usage and the
Remaining License box displays -.
4 Accept Click this button to set the information of the entered
5 Distribution Switching the selection (ON/OFF) enables the
license to be set and enables you to check which
clusters have a license, etc.
NAS08-190
NAS08-200 DKC515I
Recheck the cluster to which the license is to be assigned, and then click the OK button.
(7) The message “The license is accepted” is displayed.

(8) In the ‘NAS Setup on SVP (License Setting)’ window, click the Close button to close the
window.
In the case of having multiple license keys for products such as [NAS Backup Restore],
etc. in same license file, repeat through step (4) to step (8).
(9) In the ‘NAS Setup on SVP (License Key File)’ window, click the Close button to close
the window.
In case of having each license key in different file, repeat through step (2) to step (9).
(10) Make sure the licenses that were set up in the ‘License List’ box, and then click the Close
button.
(11) In the ‘NAS Setup on SVP (Main)’ window, click the Close button to close the window.
(12) Next, you must perform operations using the NAS Blade Manager GUI. Go to next
section.
(13) Change SVP mode from Modify Mode to View Mode.
NAS08-200
NAS08-210 DKC515I
8.2 Operations Using the NAS Blade Manager GUI

[1] Confirming that Setup on SVP is stopped ---------------------------------------------- NAS08-210
[2] Connecting Fibre optic cables (LAN cables) ------------------------------------------- NAS08-220
[3] Registering system administrators ------------------------------------------------------- NAS08-230
[4] Setting up the NAS Package cluster configuration ------------------------------------ NAS08-330
This section describes the operations using the NAS Blade Manager GUI via the Internet Explorer
running on the SVP. The procedures are as follows:
[1] Confirming that Setup on SVP is stopped
(1) Make sure that Setup on SVP on the SVP has stopped.
(2) If Setup on SVP is still running, select the Close button in the ‘NAS Setup on SVP
(Main)’ window to stop the NAS Setup on SVP. If multiple Setups on SVP programs are
running, close all windows named as ‘NAS Setup on SVP (Main)’.
CAUTION
Do not perform any NAS Blade Manager operations on the SVP while Setup on SVP is
running.
NAS08-210
NAS08-220 DKC515I
[2] Connecting Fibre optic cables (LAN cables)

To connect Fibre optic cables (LAN cables) to ports on NAS Packages:
When they have already been connected, go to the step [3], “Registering system
administrators” on page NAS08-230.
(1) Connect Fibre optic cables (LAN cables) to each port that Service IP Address is defined
in the System Assurance Documentation. Also, connect Fibre optic cables (LAN cables)
to each NAS Package in a cluster.
If multiple clusters exist, connect Fibre optic cables (LAN cables) to each port that
Service IP Address is defined, in each NAS Package in all clusters.
Table 8.2-0 shows the correspondence of eth1 ∼ eth4 and port numbers of each NAS
package.
Table 8.2-0 Correspondence of eth1~eth4 and port numbers of NAS packages

NAS package eth1 eth2 eth3 eth4
Basic CHA-1E 1A 3A 5A 7A
CHA-2Q 2A 4A 6A 8A
Option-1 CHA-1F 1E 3E 5E 7E
CHA-2R 2E 4E 6E 8E
Option-2 CHA-1G 1J 3J 5J 7J
CHA-2T 2J 4J 6J 8J
Option-3 CHA-1H 1N 3N 5N 7N
CHA-2U 2N 4N 6N 8N
(2) Connect opposite sides of the Fibre optic cables (LAN cables) to available peripheral
devices, such as LAN switches, routers, clients and so on. Make sure that the port lamp on
the NAS Package is lit and indicates that the link is up.
CAUTION
When a cluster is being configured, or when a cluster is activated, disconnecting a Fibre
optic cable (LAN cable) from a port of a NAS Package that Service IP Address is
defined will cause a failover in the cluster, and it might take long to failback. Therefore, do
not disconnect Fibre optic cables (LAN cables) when a cluster is being configured, or
when a cluster is activated.
NAS08-220
NAS08-230 DKC515I
[3] Registering system administrators

To register system administrators, log in to NAS Blade Manager by an account administrator,
and then register system administrators.
To register system administrators:
(1) Start a Web browser on the SVP.

Select Start - Programs - Internet Explorer.
If address bar is already shown on the Web browser, go to step (3).

If address bar is not shown on the Web browser, go to step (2).
(2) Display the address bar on the Web browser.

Select View - Toolbars - Address Bar from the menu bar.
NAS08-230
NAS08-231 DKC515I
(3) Disable Pop-up Blocker function on WWW browser.

Select Tools-Internet Options... on menu bar.
Click (CL) the Privacy tab, then disable “Block pop-ups” check box.
Click (CL) OK button.
NAS08-231
NAS08-240 DKC515I
(4) Type the URL of the ‘Login’ window, at the address bar on the Web browser.
Enter the following URL:
https://fixed-IP-address-of-NAS-Package-for-connection/admin.cgi
The ‘Security Alert’ window appears.
Click Yes button, and then the ‘Login’ window appears.
NAS08-240
NAS08-250 DKC515I
To obtain the fixed IP address for the NAS Package, select Install - Refer Configuration
in the ‘SVP’ window.
Obtain the first 3 bytes of the IP address from the IP address displayed in ‘DKC
Configuration’ window, and obtain the lowest one byte from a value shown in Table 8.2-1
[NAS08-260] according to the NAS Package location.
NAS08-250
NAS08-260 DKC515I
Table 8.2-1 shows the lowest byte of the fixed IP address of NAS Package.
Table 8.2-1 Lowest byte of fixed IP address of NAS Package

Package Location Lowermost byte of IP address
peculiar to NAS Package
CHA-1E 54
CHA-1F 70
CHA-1G 86
CHA-1H 102
CHA-2Q 118
CHA-2R 134
CHA-2T 150
CHA-2U 166
As shown in this example, if the IP address obtained by Install – Refer Configuration on

the SVP is 126.244.22.15, the fixed IP address of NAS Package of the location on
CHA-1E for example, will become 126.244.22.54.
NAS08-260
NAS08-270 DKC515I
(5) The ‘Login’ window appears.

In User ID, enter nasmgr (the default user name of the account administrator), and in
Password, enter raid-mgr, and then click the Login button.
If NAS Packages have already been being used by the customer, the user ID and password
of the account administrator may have been changed. If so, ask the customer for the
current user ID and password to log in.
The following table lists the information to be specified in the ‘Login’ window.
Table 8.2-2 Information specified in the ‘Login (account administrator)’ window

# Item Description
1 User ID Enter the user name of the account administrator for the
NAS Blade system.
2 Password Enter the password of the account administrator.
NAS08-270
NAS08-280 DKC515I
(6) In the ‘Main Menu (account administrator)’ window, click the Administrator Setup
button.
The ‘List of Administrators’ window appears.
NAS08-280
NAS08-290 DKC515I
(7) When registering system administrator, click the Add Administrator button and go to
step (8). When adding or reducing the packages which system administrator manages,
select desired system administrator and then click the Edit Administrator and go to step
(9).
The ‘Add Administrator’ window appears.
NAS08-290
NAS08-300 DKC515I
(8) Enter the required information according to the settings in the System Assurance
Documentation, and then click the Add button.
The system administrator is added, and the ‘List of Administrators’ window reappears.
Go to step (10).
NAS08-300
NAS08-310 DKC515I
The following table lists the information to be specified in the ‘Add Administrator’ window.
Table 8.2-3 Information specified in the ‘Add Administrator’ window

# Item Description
1 Administrator name Enter the user name of the system administrator you are
registering.
Specify a maximum of 16 alphabetic characters or
numeric characters.
The first character must be an alphabetic character.
You can use any alphanumeric character, hyphen (-),
and underscore (_) after the first character.
Specify a unique user name. This user name must differ
from the name of the account administrator.
2 Comment Enter a comment for the system administrator you are
registering.
Enter a maximum of 32 characters.
You can use any alphanumeric character, number sign
(#), percent sign (%), ampersand (&), apostrophe ('),
left parenthesis ((), right parenthesis ()), asterisk (*),
plus sign (+), hyphen (-), period (.), forward slash (/),
semicolon (;), left angle bracket (<), right angle
bracket (>), question mark (?), at mark (@), left bracket
([), right bracket (]), caret (^), underscore (_), left
brace ({), vertical bar (|), right brace (}), and tilde (~).
You can also specify spaces but spaces cannot be
specified at the beginning or at the end of the character
string.
This item is optional.
3 Password Enter the password of the system administrator you are
registering.
Specify a maximum of 8 characters.
You can use any alphanumeric character, exclamation
mark (!), quote ("), number sign (#), dollar sign ($),
percent sign (%), ampersand (&), apostrophe ('), left
parenthesis ((), right parenthesis ()), asterisk (*), plus
sign (+), comma (,) hyphen (-), period (.), forward
slash (/), colon (:), semicolon (;), left angle bracket
(<), equal sign (=), right angle bracket (>), question
mark (?), at mark (@), left bracket ([), backslash (\),
right bracket (]), caret (^), underscore (_), grave
accent (`), left brace ({), vertical bar (|), right brace
(}), and tilde (~).
4 Re-enter password Re-enter the system-administrator password that you
specified in Password.
5 Managed NAS-CHAs Select the check box for the NAS Package you want to
allocate to the system administrator you are registering.
You can specify more than one NAS Package.
NAS08-310
NAS08-320 DKC515I
(9) Mark check which system administrator would like to add or reduce the packages in
‘Managed NAS-CHAs’ check box.
(10) Click Close in the menu area.

You will log out from NAS Blade Manager, and the Web browser will close.
Make sure that you log out first, and then close the Web browser. If you close the Web
browser first, you cannot log out properly.
NAS08-320
NAS08-330 DKC515I
[4] Setting up the NAS Package cluster configuration

The system administrator defines the cluster configuration of NAS Packages using the GUI of
NAS Blade Manager.
To log in to NAS Blade Manager as a system administrator and define the cluster
configuration:
(1) Type the URL of the Login window, at the address bar on the Web browser.
The fixed IP address of NAS Package should be same as you got at step (3) in 8.2 [3]
Registering system administrators [NAS08-230].
NAS08-330
NAS08-340 DKC515I
(2) The ‘Security Alert’ window appears. Click Yes button, and then the ‘Login’ window
appears.
Enter User ID and Password, and then click the Login button.
Table 8.2-4 Information specified in the ‘Login’ window

# Item Description
1 User ID Enter the user name of a system administrator
according to the System Assurance Documentation.
2 Password Enter the password of the system administrator
NAS08-340
NAS08-350 DKC515I
(3) The ‘Define Cluster Configuration’ window appears for the NAS Package you selected,
and a dialog box prompts you to define the cluster configuration. Click the OK button.
(4) The ‘Define Cluster Configuration’ window appears.

Enter the required information according to the System Assurance Documentation. and
then click the OK button.
NAS08-350
NAS08-360 DKC515I
(5) The ‘Do you want to define the cluster?’ window appears.
(6) Settings will be saved within around 10 minutes.
NAS08-360
NAS08-370 DKC515I
The following table lists the information to be specified in the ‘Define Cluster Configuration’
window.
Table 8.2-5 Information specified in the ‘Define Cluster Configuration’ window

# Item Description
1 Cluster name Enter any name to identify the cluster consisting of
nodes, that is, NAS Packages in pairs.
You can use a maximum of 22 characters.
period (.), forward slash (/), colon (:), at mark (@),
and underscore (_).
However, you cannot use an underscore (_) as the first
character.
Note that you cannot specify words reserved by the
system. For details on reserved words, see Table 8.1-1
[NAS08-20].
2 Node name Enter any name as the node name. A node name is the
name of an element that corresponds to each NAS
Package in the cluster. This node name differs from the
channel adapter name set for the NAS Package.
You can use a maximum of 22 characters.
period (.), forward slash (/), colon (:), at mark (@),
and underscore (_).
You cannot use an underscore (_) as the first character.
Note that you cannot specify words reserved by the
system. For details on reserved words, see Table 8.1-1
[NAS08-20].
NAS08-370
NAS08-380 DKC515I
(7) The cluster configuration settings are saved and the ‘Main Menu’ window appears.
(8) Click(CL) [System Setup] button.
NAS08-380
NAS08-381 DKC515I
(9) Click (CL) [Interface Management] button.
To configure eth1 port, go to (9-1).

To configure eth2~eth4 port, go to (10).
(9-1) Select eth1 radio button then select (CL) [Edit].
NAS08-381
NAS08-382 DKC515I
(9-2) Enter service IP address in each text box as indicated in the System Assurance
Documentation. After confirming each value, select(CL) [OK]. Go to (10) if there are any
more ports to be configured. Go to (13) if eth1 port was the only port to be configured.
(10) Click (CL) [Add] button.
NAS08-382
NAS08-383 DKC515I
(11) [Add Interface] window is shown.
(12) Select (SL) desired port from [Port] drop-down list, then set each value as described in the
System Assurance Documentation. Click(CL) [OK] button. Perform (10)~(12) for all
ports to be configured. Go to (13).
NAS08-383
NAS08-384 DKC515I
(13) Log out from NAS Blade Manager.

In the menu area of the window for the NAS Package from which you want to log out,
click Close.

(15) Enable Pop-up Blocker function on WWW browser.

(16) Click (CL) the Privacy tab, then enable “Block pop-ups” check box.
NAS08-384
NAS08-390 DKC515I
(17) Hide the address bar on the Web browser.

Select View - Toolbars - Address Bar from the menu bar to clear the check.
(18) Make sure that the address bar is not displayed in the Web browser.
(19) Select File - Close in the Web browser to exit.
NAS08-390
NAS08-400 DKC515I
8.3 Confirmation of the settings

Confirm the settings as following procedure.
[1] Connection of Fibre optic cable (LAN cable)--------------------------------------- NAS08-400
[2] Starting the cluster---------------------------------------------------------------------- NAS08-420
[3] Confirmation of the connection from a client--------------------------------------- NAS08-500
[1] Connection of Fibre optic cable (LAN cable)

(1) For new installation of DKC and NAS Blade system, go to step (2).
For on-site installation of NAS Blade system, go to step (4).
(2) Connect Fibre optic cable (LAN cable) to eth1 port of NAS Packages.
In case Service IP Addresses of eth2 ∼ eth4 are specified in the System Assurance
Documentation, go to step (3).
In case Service IP Addresses of eth2 ∼ eth4 are not specified in the System Assurance
Documentation, go to step (4).
(3) Connect Fibre optic cables (LAN cables) to eth2 ∼ eth4 ports of NAS Packages, the
Service IP Addresses of which are specified in the System Assurance Documentation.
NAS08-400
NAS08-410 DKC515I
(4) Make sure that the Fibre optic cables (LAN cables) are connected to ether ports of NAS
Packages according as ether ports which are described in Service IP Addresses column of
the System Assurance Documentation. Also, make sure that the opposite sides of the Fibre
optic cables (LAN cables) to available peripheral devices, such as LAN switches, routers,
clients and so on. Make sure that the port lamps on the NAS Package, the Service IP
Addresses of which are specified in the System Assurance Documentation, are lit and
indicate that the links are up. (In some installation cases, there is no need to connect Fibre
optic cable (LAN cable) to some/all of eth2 ∼ eth4 ports.)
Table 8.3-0 shows the correspondence of eth1 ∼ eth4 and port numbers of each NAS
package.
Table 8.3-0 Correspondence of eth1~eth4 and port numbers of NAS packages

NAS package eth1 eth2 eth3 eth4
Basic CHA-1E 1A 3A 5A 7A
CHA-2Q 2A 4A 6A 8A
Option-1 CHA-1F 1E 3E 5E 7E
CHA-2R 2E 4E 6E 8E
Option-2 CHA-1G 1J 3J 5J 7J
CHA-2T 2J 4J 6J 8J
Option-3 CHA-1H 1N 3N 5N 7N
CHA-2U 2N 4N 6N 8N
CAUTION
When a cluster is being configured, or when a cluster is activated, disconnecting a Fibre
optic cable (LAN cable) from a port of a NAS Package that Service IP Address is defined
will cause a failover in the cluster, and it might take long to failback. Therefore, do not
disconnect Fibre optic cables (LAN cables) when a cluster is being configured, or when a
cluster is activated.
(5) For new installation of DKC and NAS Blade system, go to 8.3 [2] Starting the cluster
[NAS08-420].
If DKC has already been installed at the customer’s site, and NAS Blade system is to be
installed or added, the clusters should have been activated by maintenance personnel
following the procedures described in section 8.1 Operations Using the SVP [NAS08-20]
and 8.2 Operations Using the NAS Blade Manager GUI [NAS08-210]. In this case, go to
8.3 [3] Confirmation of the connection from a client [NAS08-500].
NAS08-410
NAS08-420 DKC515I
[2] Starting the cluster

To start NAS cluster, log in to NAS Blade Manager using a maintenance personnel on SVP,
and then start the cluster using GUI.
To start the cluster:

If address bar is already shown on the Web browser, proceed to step (3).
If address bar is not shown on the Web browser, proceed to step (2).
(2) Display the address bar on the Web browser.

NAS08-420
NAS08-421 DKC515I
(3) Disable Pop-up Blocker function on WWW browser.

Click (CL) the Privacy tab, then disable “Block pop-ups” check box.
NAS08-421
NAS08-430 DKC515I
(4) Type the URL of the ‘Login’ window, at the address bar on the Web browser.
The ‘Security Alert’ window appears.
Click the Yes button, and then the ‘Login’ window appears.
NAS08-430
NAS08-440 DKC515I
To get the fixed IP address of NAS Package, open Install - Refer Configuration of the
SVP.
Get upper 3 bytes of the IP address from this window, and then apply Table 8.3-1
[NAS08-450] to get the lowest byte according to the location of the NAS Package.
NAS08-440
NAS08-450 DKC515I
Table 8.3-1 shows the lowest byte of the fixed IP address of NAS Package.
Table 8.3-1 Lowest byte of fixed IP address of NAS Package

Package Location Lowest byte of fixed IP address of
NAS Package
CHA-1E 54
CHA-1F 70
CHA-1G 86
CHA-1H 102
CHA-2Q 118
CHA-2R 134
CHA-2T 150
CHA-2U 166
As shown in this example, if the IP address obtained by Install – Refer Configuration on

the SVP is 126.244.22.15, the fixed IP address of NAS Package of the location on
CHA-1E for example, will become 126.244.22.54.
Table 8.3-2 Information specified in the ‘Login’ window

# Item Description
1 User ID Enter the user name of a system administrator
2 Password Enter the password of the system administrator
NAS08-450
NAS08-460 DKC515I
(5) Enter the User name and Password of a system administrator, and click Login button.
The ‘Main Menu’ window appears.
(6) In the ‘Main Menu’ window, click the Cluster Management button.
(7) Click the Start button for the appropriate cluster. (The cluster will be started within
around 10 minutes.)
NAS08-460
NAS08-470 DKC515I
(8) In the ‘Browse Cluster Status (Cluster / Node Status)’ window, make sure that Cluster
status is ‘ACTIVE’ and Node status is ‘UP’ on each node.
If Cluster status is not ‘ACTIVE’ or Node status is not ‘UP’, contact the Technical
Support Division.
(9) In the ‘Browse Cluster Status (Resource group Status)’ window, select Resource group
Status from drop down list. Click the Display button.
NAS08-470
NAS08-480 DKC515I
(10) The ‘Browse Cluster Status (Resource Group Status)’ window appears.
Make sure that Resource group status is ‘Offline / No error’.
If Resource group status is not ‘Offline / No error’, contact the Technical Support
Division.
(11) Start the resource groups.

Select the radio button for the resource group and click the Start button. In a short while
Resource group status changes to ‘Online / No error’. Click the Start button for each
resource group to start it.
If Resource group status does not change to ‘Online / No error’, contact the Technical
Support Division.
NAS08-480
NAS08-490 DKC515I
(12) Log out from NAS Blade Manager.

In the menu area of the window for the NAS Package from which you want to log out,
click Close.

(14) Enable Pop-up Blocker function on WWW browser.

(15) Click (CL) the Privacy tab, then enable “Block pop-ups” check box.
NAS08-490
NAS08-491 DKC515I
(16) Hide the address bar on the Web browser.

(17) Make sure that the address bar is not displayed on the Web browser.
(18) Select File - Close in the Web browser to exit.
(19) Go to 8.3 [3] Confirmation of the connection from a client [NAS08-500].
NAS08-491
NAS08-500 DKC515I
[3] Confirmation of the connection from a client
On the client which can reach the NAS Packages, execute the ping command for the fixed IP
addresses and Service IP addresses of all ports of NAS Packages, which have been defined in
this section.
Obtain the fixed IP addresses and service IP addresses of eth1 and eth2 port of NAS Packages
from the System Assurance Documentation.
Make sure the fixed IP addresses and service IP addresses of all installed or added NAS
Packages.
The following shows an example of the ping command:
ping Fxed-IP-Address-of-eth1-or-eth2-port-of-NAS-Package
ping Service-IP-Address-of- eth1-or-eth2-port-of-NAS-Package
The following figure shows an example of the ping command execution from the CIFS client.
In response of the ping command, if the echo Reply from indicated-IP-address: bytes=
xxx is displayed, the IP address defined at the port is confirmed to be valid.
If a message other than Reply from indicated-IP-address: bytes= xxx is displayed even
if the fibre optic cable (LAN cable) connections and the network configuration are correct,
contact the Technical Support Division.
This is the end of NAS configuration for both new installation and on-site installation.
NAS08-500
NAS09-10 DKC515I
9. Appendixes
9.1 Appendix A Using the Command Line To Obtain Error Information
9.1.1 Overview
This chapter describes the command line procedures that are needed to obtain dump information
and traces of error information generated from NAS functionality software errors.
9.1.2 Types of Error Information

Table 9.1-1 lists the error information (dumps) that the system obtains, and for which you must use
the command line, if a NAS functionality software error occurs.
Table 9.1-1 Error Information (Dumps) that Requires Use of the Command Line
# Name Error Generated Collected when Feature Write format
location by
1 Crash dump NAS NAS OS NAS detects its If an error occurs, the kernel runs raw write,
OS abnormal a program that selects the memory image,
condition. necessary parts and performs a no compression
dump automatically, before
initiating a system shutdown.
2 Hibernation BIOS Another NAS A reset is performed after the raw write,
dump (Pentium) Package detects error occurred and a full memory memory image,
a NAS OS dump is performed via the BIOS. no compression
hangup or an
error occurs
during the NAS
OS's startup or
termination
processing.
A slowdown A reset is performed as specified
occurs. by SVP and a full memory dump
is performed via the BIOS. *1
3 LM dump MP An error occurs The MP is notified of the range raw write,
(software errors of areas, in page units, where memory image,
only). dumps are performed when the no compression
NAS OS is started. After the
error occurs, the MP read the
contents of the Pentium's
memory and writes them to a
disk.
*1: Specify by using the Hibernation Dump button in the SVP’s NAS Setup on SVP
(Main) window.
NAS09-10
NAS09-20 DKC515I
Table 9.1-2 lists the error information (logs and traces) that the system obtains, and for which you
must use the command line, if a NAS functionality software error occurs.
Table 9.1-2 Error Information (Logs and Traces) that Requires Use of the
Command Line
# Name Error Generated Collected when Feature Write format
location by
1 Event trace  MP A failure A history of events such as task raw write,

(hangup or switches is stored in the memory image,
panic) occurs. Pentium's memory in no compression
wraparound mode while the
NAS OS is running. After an
error occurs, the MP reads the
contents of that memory area and
writes them to a disk.
NAS OS A slowdown A history of events such as task
occurs. switches is stored in the
Pentium's memory in
wraparound mode while the
NAS OS is running. The NAS
OS extracts the contents of that
memory area whenever the
lkstbuf command is run.
NAS09-20
NAS09-30 DKC515I
9.1.3 How to Obtain a Crash Dump

Since all operations involved in obtaining a crash dump are done only for maintenance purposes,
they must be carried out via the CUI (Console User Interface). The crash dump is obtained by
connecting a maintenance terminal (maintenance PC) to the data LAN and by using SSH from that
PC to access the failed NAS Package.
In collection of a crash dump after an error occurs, you can use the lkcd_save command to
collect the crash dump from another node (NAS Package). The dump-collection destination is a
maintenance terminal, which is assumed here to be a Linux machine. Collection is also possible
from a Windows machine running an ftp server. Figure 9.1-1 shows a flowchart of the procedure
for obtaining a crash dump, followed by a step-by-step description of the procedure.
Maintenance personnel
Obtaining a crash dump
Maintenance terminal:
Log in to the NAS Package that failed
or another NAS Package.
Prepare an error information LU.
Convert the crash dump into a file.
Transfer the crash dump file to the
maintenance terminal.
Delete the crash dump file.
Unmount the error information LU.
End
Figure 9.1-1 Flowchart for Obtaining a Crash Dump
NAS09-30
NAS09-40 DKC515I
1. Use SSH to log in to a NAS Package.

If the failed NAS Package has restarted, use SSH to connect to that NAS Package. If the failed
NAS Package has not restarted, use SSH to connect to another NAS Package. Note, however,
that you will probably be able to restart the failed NAS Package because most failures are
caused by software.
Obtaining a crash dump via another NAS Package depends on the settings of the dump
destination. Therefore, if the failed NAS Package has not restarted and you want to obtain a
crash dump via another NAS Package, contact the developers.
To perform the processing described in this subsection, you must first use the su command to
become a superuser with root privileges because operations such as mounting and unmounting
disks are required.
Note: This example shows the default password. For security reason, we recommend that you
change the password to a more difficult one when you use it for the first time.
% ssh -l nasroot xx.xx.xx.xx

The authenticity of host 'xx.xx.xx.xx (xx.xx.xx.xx)' can't be established.
RSA key fingerprint is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'xx.xx.xx.xx' (RSA) to the list of known hosts.
Password:
Linux e-nas 2.4.17-enas0100 #4 Fri Nov 1 12:46:35 JST 2002 i686 unknown
Last login: Mon Dec 9 08:56:17 2002 from xx.xx.xx.xx
enasroot@nas2q:~$ (This prompt is an example.)
enasroot@nas2q:~$ su
Passwd: ******
nas2q:/home/nasroot#
2. Prepare an error information LU for the crash dump.

Use /dev/enassys/lu06p1, which is reserved as a spare partition, as the error information LU. A
partition that is to be used for a crash dump is designed to be referenced from all NAS
Packages. However, since the partition needs to be shared by all NAS Packages, it is used as a
temporary destination of the save until its contents are placed onto a storage medium after a
crash dump is performed.
All NAS Packages can reference this partition, so make sure that no other NAS Package is
referencing the partition before you attempt to initialize the partition.
nas2q:/home/nasroot# mkfs.hixfs -f /dev/enassys/lu06p1

meta-data=/dev/enassys/lu06p1 isize=256 agcount=8, agsize=131281 blks
data = bsize=4096 blocks=1050241, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
It is likely that a file system has already been created (by NAS Blade System) in the partition.
Even in such a case, create a file system by using the mkfs.hixfs command as above.
nas2q:/home/nasroot# mkdir /var/log/dump/work

nas2q:/home/nasroot# mount -t hixfs /dev/enassys/lu06p1 /var/log/dump/work
NAS09-40
NAS09-50 DKC515I
3. Convert the crash dump to a file.

Enter the lkcd_save command. The first argument is the name of the device to which the
dump is written when a crash occurs and the second argument is the target directory in which
the dump is to be restored as an ordinary file.
The following is a sample command line for the lkcd_save command (with default
arguments) when you logged in to the failed NAS Package.
Command Syntax: lkcd_save dumpdev dumpdir
nas2q:/home/nasroot# lkcd_save /dev/vmdump /var/log/dump/work

- 10.4%
/ 64.9%
| 75.6%
When the lkcd_save command is entered, the progress of processing is displayed in

percents and with a spinner as shown above. An indication of 100% marks the end of
processing. The target files are generated in the dump-directory/0 directory. You can review
the files with the ls -l command. Three file names with a suffix 0 will appear.
nas2q:/home/nasroot# ls -l /var/log/dump/work/0
total 3552852
-rw-r--r-- 1 root root 3637503744 Apr 5 23:16 dump.0
-rw-r--r-- 1 root root 141992 Apr 5 23:16 kerntypes.0
-rw-r--r-- 1 root root 527321 Apr 5 23:16 map.0
Note: The suffix number starts at zero and is incremented (for example, dump.0 becomes
dump.1) as more dumps are obtained. However, when obtaining crush dumps, the suffix
number is always zero because multiple dumps are not kept at the dump destination.
Note: When converting crash dump file on the device on another node, ask the developer for
the name of the device to which the dump is written and specify the device name as the first
argument (<dumpdev>) for the lkcd_save command.
NAS09-50
NAS09-60 DKC515I
4. Change the directory to the dump-collection destination.
nas2q:/home/nasroot# cd /var/log/dump/work/0
5. Transfer the crash dump file to the maintenance terminal.

Use the ftp command to collect the dump file onto the maintenance terminal. Since the size
of the dump file will exceed 2 GB, make sure that the maintenance terminal is able to receive a
file of this size.
nas2q:/var/log/dump/work/0# ftp xx.xx.xx.xx (maintenance terminal)

Connected to xx.xx.xx.xx.
220 enas-devel FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.17) ready.
Name (xx.xx.xx.xx:root): guest
331 Password required for guest.
Password:
230- Linux enas-devel 2.4.17-enas0100-s970141 #3 Sat Apr 5 10:41:37 JST 2003 i686 unknown
230-
230- Most of the programs included with the Debian GNU/Linux system are
230- freely redistributable; the exact distribution terms for each program
230- are described in the individual files in /usr/share/doc/*/copyright
230-
230- Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
230- permitted by applicable law.
230 User guest logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bin
200 Type set to I.
ftp> prompt
Interactive mode off.
ftp> mput *.0
local: dump.0 remote: dump.0
200 PORT command successful.
150 Opening BINARY mode data connection for 'dump.0'.
226 Transfer complete.
local: kerntypes.0 remote: kerntypes.0
150 Opening BINARY mode data connection for 'kerntypes.0'.
141992 bytes sent in 0.75 secs (185.6 kB/s)
local: map.0 remote: map.0
150 Opening BINARY mode data connection for 'map.0'.
ftp> bye
221 Goodbye.
NAS09-60
NAS09-70 DKC515I
6. Check the size of the dump files.

Confirm that the size of the dump file that has been transferred to the maintenance terminal via
ftp is equal to that of the original one.
In the above step 5, the dump file is transferred to the direct directory /home/guest on the
maintenance terminal. Use the ls command to confirm the dump file on the maintenance
terminal.
enas-devel:/home/guest#ls –l
total 3552852
-rw-r----- 1 mary mary 3637503744 Apr 6 18:32 dump.0
-rw-r----- 1 mary mary 141992 Apr 6 18:32 kerntypes.0
-rw-r----- 1 mary mary 527321 Apr 6 18:32 map.0
The destination of the dump file is a shared partition that can be mounted by all NAS Packages
simultaneously. It is likely that the file will be destroyed if multiple NAS Packages mount the
partition simultaneously. Basically, multiple NAS Package must not convert a dump into a file
simultaneously. We recommend, however, that you make sure that the sizes agree in order to
confirm that the transfer finished successfully.
By using the lkcd_save command again, you can obtain the dump that the NAS OS
produced, even if the file system has been destroyed, because the dump that the NAS OS
produced remains on the disk. However reconfirm the mount state of the destination LU when
the file system has been destroyed.
Note: Checking the activation of the dump analyzer:

It is more reliable to confirm the transferred dump if possible.
Try to activate the dump analyzer lcrash if it is provided on the maintenance terminal.
1. Type in /sbin/lcrash -n 0
2. Confirm that the prompt (>>) of lcrash appears.
Depending on the settings, including the case in which lcrash is not provided, it is possible
that lcrash will fail to start. For details, contact the developers.
7. Unmount the error information LU of the crash dump.

Since the partition that is used as the error information LU of the dump needs to be shared by
all NAS Packages, delete the files and then unmount the error information LU
/dev/enassys/lu06p1 after collection processing with ftp has finished. Next, use the mount
command to make sure that /dev/enassys/lu06p1 is not mounted.
nas2q:/var/log/dump/work/0# rm *.0
nas2q:/var/log/dump/work/0# cd
nas2q:~# umount /dev/enassys/lu06p1
nas2q:~# mount
/dev/enassys/lu00p1 on / type hixfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/enassys/lu08p12 on /enassys/hifailsafe/CHN8 type hixfs (rw,sync)
nas2q:~#
NAS09-70
NAS09-80 DKC515I
9.1.4 How to Obtain a Hibernation Dump

A hibernation dump is obtained if a slowdown occurs or if a hangup occurs.
• If a slowdown occurs, or an error occurs during startup or termination of the NAS OS:
Maintenance personnel must use the SVP to specify that a hibernation dump is to be obtained, by
using the Hibernation Dump button in the NAS Setup on SVP (Main) window.
• If a hangup occurs:
Another NAS Package in the same cluster detects the hangup, and a hibernation dump is
performed automatically.
Since all operations involved in the obtaining of a hibernation dump are done only for maintenance
purposes in either case, they must be carried out via the CUI (Console User Interface). The
hibernation dump is obtained by connecting a maintenance terminal (maintenance PC) to the data
LAN and by using SSH from that PC to access the failed NAS Package. However, a hardware
failure might occur when the hibernation dump is collected. If no hardware failure is detected,
restart the failed NAS Package, log in to that NAS Package, and then use the /sbin/saveto
command to collect the hibernation dump. If you are not sure whether a hardware failure occurred
in the NAS Package, log in to another normal NAS Package, and use the command to collect the
hibernation dump.
Note: Executing the /sbin/saveto command places a load on the system, so do not execute the
/sbin/saveto command on heavily-loaded nodes. Also, since the size of the hibernation dump
amounts to 4 GB, it is impossible to collect the dump onto the NAS OS LU. The dump must be
collected into an error information LU that is also used by LKCD.
NAS09-80
NAS09-90 DKC515I
Figure 9.1-2 shows the flowchart for obtaining a hibernation dump.

Obtaining a hibernation dump
Log in to the failed NAS Package or another
NAS Package.
Initialize and mount the error information LU.
Convert the hibernation dump into a file.
Transfer the hibernation dump file to the
Delete the hibernation dump file.
Unmount the error information LU.
End
Figure 9.1-2 Flowchart for Obtaining a Hibernation Dump

Use SSH to connect to the failed NAS Package or another NAS Package (if no hardware
failure is detected, restart the failed NAS Package and log in to it).
To perform the processing described in this subsection, you must first change your access
privileges to become a superuser because operations such as mounting and unmounting disks
are required.
Password:
Passwd: ******
NAS09-90
NAS09-100 DKC515I
2. Initialize and mount an error information LU.

Use the /sbin/saveto command to collect hibernation dumps. Before doing this, initialize
and mount an error information LU for storing the dumped file.
All NAS Packages can reference this error information LU, so make sure that no other NAS
Package is referencing the area before you attempt to initialize the area.
nas2q:/home/nasroot# mkfs.hixfs -f /dev/enassys/lu06p1

meta-data=/dev/enassys/lu06p1 isize=256 agcount=8, agsize=131281 blks
data = bsize=4096 blocks=1050241, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
It is likely that a file system has already been created (by NAS Blade System) in the partition.
Even in such a case, create a file system by using the mkfs.hixfs command as above.
nas2q:/home/nasroot# mkdir /var/log/hibernation

nas2q:/home/nasroot# mount -t hixfs /dev/enassys/lu06p1 /var/log/hibernation/
3. Convert a hibernation dump into a file.

Enter the saveto command to convert a hibernation dump into a file.
Note: If you execute the saveto command for multiple NAS Packages simultaneously, it
might not execute successfully. Make sure that the command is not being executed for any
other NAS Package, and then execute it for the desired NAS Package.
nas2q:/home/nasroot# cd /var/log/hibernation/
nas2q:/home/nasroot# /sbin/saveto
Command (m for help): p
CHN# Status Date
1 Written - Sun Mar 30 03:02:09 2003
5 Unused
Command (m for help):
NAS Blade system reserves one area for storing hibernation dump data for each NAS Package.
The p subcommand shows the current status of hibernation entries. In the above example, the
NAS Packages are placed in slots 1 and 5, and slot 1 contains a written but unconverted
hibernation dump. Next, use the s command to convert the unconverted hibernation dump into
a real file. The system shows the latest entry and prompts you to dump that entry. Normally,
respond by typing y (the system assumes your reply is y unless you reply n).
NAS09-100
NAS09-110 DKC515I
Command (m for help): s

The current status is:
CHN# Status Date
1 Written - Sun Mar 30 03:02:09 2003
5 Unused
CHN1 is the latest hibernation dump.
Would you like to save CHN1?(Yes/No)y
save hibernation dump till the following dots reaches here ---------->|
Writing…………………………………………………………………………………………………………………………………………………………………………Done
It will take several minutes to process this command depending on conditions. These minutes
are needed for the system to write data while reading data from an area as large as 4 GB. The
progress of execution is shown by dots (.). Since one dot character represents 64 MB of data,
64 dots mark the end of processing. When processing finishes, the entry is flagged as a free
entry. Quit with the q command.
Table 9.1-3 summarizes the suboptions of the saveto command. There are few cases in
which you need to use subcommands other than s, p, and q.
Table 9.1-3 saveto Suboptions

# Suboption Description
1 p (print): Shows the status of the hibernation entries for each NAS Package. The
items shown include the CHA number, used/unused state, and the time
written, on one line for each NAS Package.
2 c (change): Changes the magic number of the specified entry and toggles the
t (turn): used/unused state.
3 d (delete): Deletes a given entry. The hibernation entry associated with the specified
NAS Package is removed.
4 n (new): Creates a new entry. This option is valid only when there is no entry
associated with the specified NAS Package. The suboption prompts you to
write one entry.
5 s (save): Converts a hibernation dump into a file. The file will be created in the
w (write): place where the command was issued unless customization is performed.
6 l: Creates a disk image file in the area specified by the command. This
subcommand is an emergency measure to save the hibernation dump when
the s (save) and w (write) subcommand cannot save the dump. *1
7 q (quit): Terminates the command.
*1: This l subcommand is provided as an emergency measure. Similar to the dd command,
the l subcommand writes the disk image in the hibernation dump to a file. Usually, you
would use the s or w subcommand to convert a hibernation dump to a file but if these
subcommands cannot convert the dump for some reason, as an emergency measure use
the l subcommand to save the hibernation dump. If you accidentally use the l
subcommand during maintenance procedures, press the Ctrl and C keys to cancel it.
NAS09-110
NAS09-120 DKC515I
Table 9.1-4 shows a command option that can be specified as a parameter in the saveto
command. The parameter i (initialize) is specified to initialize the partition for the hibernation
dump. Basically, the saveto –i command is executed automatically when the NAS OS is
installed for the first time. Therefore, maintenance personnel do not need to initialize the
partition for the hibernation dump. However, if the partition could not be initialized for some
reason, maintenance personnel must use the saveto –i command to initialize the partition
manually.
Table 9.1-4 Command Option Specified as a Parameter in the saveto Command

# Command option Description
1 i (initialize): Initializes the partition for the hibernation dump, for which the
correct magic number is not specified.
4. Transfer the hibernation dump to the maintenance terminal.

Use the ftp command to collect the dump onto the maintenance terminal. The file generated
by the conversion processing has the name dump.0. This is the only file to be transferred.
Since the size of the dump file will exceed 2 GB, make sure that the maintenance terminal is
able to receive a file of this size.
nas2q:/var/log/dump/work/0# ftp xx.xx.xx.xx (maintenance terminal)

Password:
230-
230-
230 User guest logged in.
ftp> bin
200 Type set to I.
ftp> mput dump.0
mput dump.0? y
150 Opening BINARY mode data connection for 'dump.0'.
ftp> bye
221 Goodbye.
NAS09-120
NAS09-130 DKC515I
5. Check the size of the dump file.

Confirm that the size of the dump file that has been transferred to the maintenance terminal via
ftp is equal to the size of the original one.
In the above step 4, the dump file is transferred to the direct directory /home/guest on the
maintenance terminal. Use the ls command to confirm the dump file on the maintenance
terminal.
enas-devel:/home/guest#ls –l
total 3605512
-rw-r--r-- 1 root root 3638165504 Aug 18 17:24 dump.0
The destination of the dump file is a shared partition that can be mounted by all NAS Packages
simultaneously. Note, however, that the file will probably be destroyed if multiple NAS
Packages mount the partition simultaneously. Basically, multiple NAS Packages must not
convert a dump into a file simultaneously. We recommend, however, that you make sure that
the sizes agree in order to confirm that the transfer finished successfully.
The dump that NAS OS produced remains on the disk, so that even if the file system has been
destroyed, you can use the saveto command again to obtain the dump that the NAS OS
produced. If, however, the file system has been destroyed, reconfirm the mount state of the
destination LU.
Note: Checking the activation of the dump analyzer:

To improve reliability, check the transferred dump if possible.
Try to activate the dump analyzer lcrash if it is provided on the maintenance terminal.
1. Enter /sbin/lcrash -n 0
2. Confirm that the lcrash prompt (>>) appears.
Depending on the settings, including the case in which lcrash is not provided, it is possible
that lcrash will fail to start. For details, contact the developers.
NAS09-130
NAS09-140 DKC515I
6. Unmount the error information LU.

Since the error information LU that is used as the spare destination of the dump needs to be
shared by all NAS Packages, delete the file and then unmount the error information LU
/dev/enassys/lu06p1 after collection processing with ftp has finished. Next, use the mount
command to make sure that /dev/enassys/lu06p1is not mounted.
nas2q:/var/log/hibernation# rm dump.0
nas2q:/var/log/hibernation# cd
nas2q:~# umount /dev/enassys/lu06p1
nas2q:~# mount
/dev/enassys/lu00p1 on / type hixfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
nas2q:~#
NAS09-140
NAS09-150 DKC515I
9.1.5 How to Obtain an LM Dump

Since all operations involved in obtaining an LM dump are done only for maintenance purposes,
they must be carried out via the CUI (Console User Interface). The LM dump is obtained by
LM dumps are memory dumps that are written on dedicated raw devices. They are used in
situations in which no hibernation dump can be performed. Normally, crash or hibernation dumps
are used as error information. When collecting LM dumps because of a developer's request,
however, it is necessary to perform the procedure that is explained below. Figure 9.1-3 shows the
flowchart for obtaining an LM dump, followed by a step-by-step description of the procedure.
Obtaining an LM dump
Log in to the failed NAS
Package or another NAS
Package.
The destination does not need to

be specified as the size of the
dump is as small as 12 MB.
Data is collected in the directory

Maintenance terminal: from which the command is
Collect the LM dump. entered.
Transfer the LM dump to the
Delete the LM dump.
End
Figure 9.1-3 Flowchart for Obtaining an LM Dump
NAS09-150
NAS09-160 DKC515I

If the failed NAS Package has restarted, use SSH to connect to that NAS Package. If the failed
NAS Package has not restarted, use SSH to connect to another NAS Package.
are required.

Password:
Passwd: ******
2. Collect the LM dump.

Enter the lmdump_save command to collect the dump.
Command syntax: lmdump_save entry size
Note: If you execute the lmdump_save command for multiple NAS Packages
simultaneously, it might not execute successfully. Make sure that the command is not being
executed for any other NAS Package, and then execute it for the desired NAS Package.
nas2q:/home/nasroot# lmdump_save 8
lmdump.8 generated.
nas2q:/home/nasroot# ls -l
total 4156
-rw-r--r-- 1 root root 12582912 Apr 6 02:12 lmdump.8
The first argument is an entry number. It specifies the number of the slot that has the failed
NAS Package. The slots are numbered from 1 to 8, starting at the leftmost slot. The second
argument is the size of the dump file specified in kilobytes. It is optional and may normally be
omitted. The default is 12 MB (12,288 KB), which is adequate for covering the written data.
Since the size of this dump is smaller than those of other types of dumps, the command may be
entered from any directory. The dump file is generated in the directory from which the
command is entered with a name of lmdump.n (n =1 to 8).
NAS09-160
NAS09-170 DKC515I
3. Transfer the dump to the maintenance terminal.

Use the ftp command to collect the dump onto the maintenance terminal.
nas2q:/home/nasroot# ftp xx.xx.xx.xx (maintenance terminal)

Password:
230-
230-
230 User mary logged in.
ftp> bin
200 Type set to I.
ftp> mput lmdump.8
mput lmdump.8? y
150 Opening BINARY mode data connection for 'lmdump.8'.
ftp> bye
221 Goodbye.
nas2q:/home/nasroot#.
4. Delete the LM dump in the NAS Package.

The last step is to delete the LM dump in the NAS Package.
nas2q:/home/nasroot# rm lmdump.8
NAS09-170
NAS09-180 DKC515I
9.1.6 How to Obtain an Event Trace

Since all operations involved in obtaining an event trace are done only for maintenance purposes,
they must be carried out via the CUI (Console User Interface). An event trace is obtained by
Normally, event trace information cannot be acquired directly by any NAS Package in operation.
The sole exception occurs when a slowdown takes place and the system allows accessing via SSH.
Figure 9.1-4 shows the flowchart of the procedure for obtaining an event trace, followed by a step-
by-step description of the procedure.
Obtaining an event trace
Maintenance terminal: Run only if a slowdown

Log in to the failed NAS Package. occurs.
Convert event trace data into a file.
Transfer event trace data (binary file) to the
Convert event trace data into text format.
Delete generated binary and text files.
End
Figure 9.1-4 Flowchart for Obtaining an Event Trace
Note: Stopping and restarting LKST: LKST is enabled when the NAS OS starts up. If you want to
stop and restart LKST for some reason, log in to a NAS Package, use the lkst stop command to
stop LKST, and use the lkst start command to restart LKST. An example is shown below.
nas2q:/home/nasroot# lkst stop

Stop LKST event tracing.
nas2q:/home/nasroot# lkst start
Start LKST event tracing.
For the login procedure, see step 1 in subsection 9.1.6
NAS09-180
NAS09-190 DKC515I

Use SSH to connect to the failed NAS Package.
are required.

Password:
Passwd: ******
2. Convert the event trace data into a file.

Enter the lkstbuf command to convert the trace data in memory into a file. This file is in
binary format and cannot be viewed as trace information.
Command syntax: lkstbuf read -f targetfile
Note: targetfile denotes the name of a binary file.
nas2q:/home/nasroot# lkstbuf read -f logfile
A file with a size of approximately 12 MB has been created. The size of the file is limited
unless you change the default.
nas2q:/home/nasroot# ls -l
total 12288
-rw-r--r-- 1 root root 12581629 Jun 10 18:40 logfile
NAS09-190
NAS09-200 DKC515I
3. Transfer the event trace to the maintenance terminal.

Use the ftp command to collect the output file onto the maintenance terminal.
nas2q:/home/nasroot# ftp xx.xx.xx.xx (maintenance terminal)

Password:
230-
230-
230 User mary logged in.
ftp> prompt
Interactive mode off.
ftp> bin
200 Type set to I.
ftp> mput outfile
local: outfile remote: outfile
150 Opening BINARY mode data connection for 'outfile'.
ftp> by
221 Goodbye.
NAS09-200
NAS09-210 DKC515I
4. Convert the event trace (binary file) to a text file.

Enter the lkstbuf print command to convert this binary file into text format. The results
are directed to the standard output by default, so they must be redirected into a file.
enas-devel:/home/guest# lkstbuf print -f logfile >outfile

enas-devel:/home/guest# ls -l
total 35476
-rw-r--r-- 1 root root 12581629 Jun 10 19:07 logfile
-rw-r--r-- 1 root root 23742752 Jun 10 19:07 outfile
A trace file of the format shown below will be generated.
enas-devel:/home/guest# vi output
Items displayed (example)
event_type=overwritten_record
cpu=00, pid=00000944
time= Sep 07 05:44:49.99328701 2002
arg1=0x00000036 0x00000000 : old arg1
arg2=0x00000000 0x00000000 : old arg2
arg3=0x00000000 0x00000000 : old arg3
arg4=0x00000030 0x00000000 : old event_type
event_type=system_call_exit
cpu=00, pid=00000944
time= Sep 07 05:44:49.99323694 2002
arg1=0x00000004 0x00000000 : call number
arg2=0x00000000 0x00000000 : return value(errno)
...
...
...
...
...
event_type=interrupt_bh_entry
cpu=00, pid=00000000
time= Sep 07 05:44:48.25912744 2002
arg1=0x00000000 0x00000000 : interrupt type(nr)
arg2=0xc011ca3c 0x00000000 : action address(bh_base)
event_type=overwritten_record
cpu=00, pid=00000000
time= Sep 07 05:44:48.25912496 2002
arg1=0xc0119730 0x00000000 : old arg1
arg2=0x00000000 0x00000000 : old arg2
arg3=0x00000000 0x00000000 : old arg3
arg4=0x00000012 0x00000000 : old event_type
(Omitted)
5. Delete the event trace on the NAS Package.

The last step is to delete the generated binary files.
nas2q:/home/nasroot# rm logfile
NAS09-210
NAS09-220 DKC515I
Blank Sheet
NAS09-220
NAS09-230 DKC515I
Blank Sheet
NAS09-230
NAS09-240 DKC515I
Blank Sheet
NAS09-240
NAS09-250 DKC515I
9.2 Appendix B Initializing Dump LUs
To recover from failure occurred in dump LUs, usually follow the instructions in Replacing Two
PDEVs (Dump LU) [NAS07-1220]. However, if restarting the NAS OS is impossible due to
operational circumstances, you must initialize the dump LUs by following the procedure described
in this section.
Since all operations involved in initializing a dump LU are done only for maintenance purposes, the
operations must be carried out via the CUI (Console User Interface). You can initialize a dump LU
by connecting a maintenance terminal (maintenance PC) to the data LAN and by using SSH from
that PC to access the NAS Package that is used by the failed dump LU.
Figure 9.2-1 shows a flowchart of the procedure for initializing a dump LU, followed by a step-by-
step description of the procedure.
Initializing the dump LU.
Log in to the NAS Package where the
disk failure occurred.
Initialize an LU that has recovered
from the disk failure to use the LU as
a dump LU.
Initialize the partition for the
hibernation dump.
End
Figure 9.2-1 Flowchart for Initializing a Dump LU
NAS09-250
NAS09-260 DKC515I

Use SSH to connect to the failed NAS Package.
To perform the processing described in this section, you must first change your access
are required.

Password:
Passwd: ******
2. Initialize an LU that has recovered from the disk failure to use it as a dump LU.
Enter the sfdisk command to create a partition for the hibernation dump.
Command syntax: sfdisk -uM /dev/enassys/lu01 < /root/dump.sfdisk
CAUTION
Make sure that you enter all the commands correctly. In particular, 1 (one) and l
(lowercase L) are easily mistaken so be careful not to mistype them. For example, the
command syntax above shows lu01 (LU one). If you type the command incorrectly,
important LUs might be destroyed by mistake.
NAS09-260
NAS09-270 DKC515I
The format shown below will be displayed.
nas2q:/home/nasroot# sfdisk /dev/enassys/lu01 < /root/dump.sfdisk

Checking that no-one is using this disk right now ...
Disk /dev/enassys/lu01: 897 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System

/dev/enassys/lu01p1 0+ 523 524- 4208998+ a0 IBM Thinkpad hibernation
/dev/enassys/lu01p2 524 537 14 112455 83 Linux
/dev/enassys/lu01p3 538 603 66 530145 83 Linux
/dev/enassys/lu01p4 0 - 0 0 0 Empty
New situation:
Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System

/dev/enassys/lu01p1 63 8418059 8417997 a0 IBM Thinkpad hibernation
/dev/enassys/lu01p2 8418060 8642969 224910 83 Linux
/dev/enassys/lu01p3 8642970 9703259 1060290 83 Linux
/dev/enassys/lu01p4 0 - 0 0 Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Successfully wrote the new partition table
Re-reading the partition table ...
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
3. Initialize the partition for the hibernation dump.

Enter the saveto command to initialize the partition for the hibernation dump.
Command syntax: saveto –i
The format shown below will be displayed.
nas2q:/home/nasroot# saveto -i
1 UNUSED - Fri May 30 23:06:46 2003
2 UNUSED
3 UNUSED - Fri May 23 10:01:47 2003
4 UNUSED - Wed May 28 11:53:00 2003
5 UNUSED - Sat May 31 15:44:13 2003
6 UNUSED
7 UNUSED - Mon May 19 21:43:39 2003
8 UNUSED - Thu Jun 5 21:49:58 2003
NAS09-270
NAS09-280 DKC515I
9.3 Appendix C How to Obtain Error Information When the NAS OS Has Not Started
9.3.1 Overview
Normally, downloading auto dump and a dump file for error information is performed with NAS
OS started. But, the situation might be possible that you cannot start NAS OS in particular
condition of the error. In this section, procedure to obtain the error information of the NAS Package
where the NAS OS has not started from other NAS Package where the NAS OS has started is
described.
9.3.2 Confirming that NAS OS is stopped
Confirm that NAS OS is stopped first. The procedure described here is premised on the situation
that the NAS OS of the target NAS Package is stopped. It is likely that the NAS OS LU will be
destroyed if the NAS OS of the target NAS Package is started. Therefore, make sure to reset CHA
(NAS Package) according to the procedure in subsection 3.5.9 Resetting CHA [NAS03-880].
9.3.3 How to Obtain an Auto Dump
To obtain an auto dump from the NAS Package where the NAS OS has not started, you should
obtain an auto dump from the NAS Package where the NAS OS has started beforehand. Then you
can obtain the auto dump via SVP. Figure 9.3-1 shows the flowchart for obtaining an auto dump,
followed by a step-by-step description of the procedure.
Obtaining an Auto dump
SVP:
Confirm that NAS OS is stopped.
NAS OS has started.
Specify the target NAS Package and
collect the Auto dump.
SVP:
Collect the Auto dump.
End
Figure 9.3-1 Flowchart for Obtaining an Auto Dump
NAS09-280
NAS09-290 DKC515I
1. Confirm that NAS OS is stopped

Confirm that NAS OS is stopped following the procedure shown in section 9.3.2 Confirming
that NAS OS is stopped [NAS03-280].
Use SSH to connect to the target NAS Package where the NAS OS has started.
are required.

RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Password:
Linux nas1e 2.4.17-enas0200-SI20K014 #1 Thu Oct 23 13:35:50 JST 2003 i686 unknown
nasroot@nas2q:~$(This prompt is an example.)
nasroot@nas2q:~$ su
Passwd: ******
3. Collect the auto dump in the target NAS Package.

Specify the target NAS Package and to collect the auto dump.
Note: The NAS Package location specified in the command is not case-sensitive. If you enter
incorrect figures, you must re-execute the chmod command to retry.
nas2q:/home/nasroot# cd /sbin
nas2q:/sbin# chmod o+x enas_autodump.sh
nas2q:/sbin# enas_autodump.sh CHA-1E (Specify the NAS Package location)
If you want to continue, input a displayed number.
0123456789 (Ten random figures will be displayed.)
input > 0123456789 (Specify the same figures displayed in the prior line.)
again > 0123456789 (Specify the same figures again.)
Success.
nas2q:/sbin#
4. Collect the auto dump.

In the ‘SVP’ window, click the Auto Dump button to collect the auto dump.
CAUTION
command syntax above shows lu01 (LU one).
NAS09-290
NAS09-300 DKC515I
9.3.4 How to Collect a Dump File

To collect a dump file from the NAS Package where the NAS OS has not started, you should obtain
a dump file from the NAS Package where the NAS OS has started beforehand. Then you can
download the dump file via SVP. Figure 9.3-2 shows the flowchart for collecting a dump file,
followed by a step-by-step description of the procedure.
Collecting a dump file
SVP:
Confirm that NAS OS is stopped.
NAS OS has started.
Specify the target NAS Package and
obtain the dump file.
NAS Setup on SVP:

Collect the dump file.
End
Figure 9.3-2 Flowchart for Collecting a Dump File
NAS09-300
NAS09-310 DKC515I
1. Confirm that NAS OS is stopped

Confirm that NAS OS is stopped following the procedure shown in section 9.3.2 Confirming
that NAS OS is stopped [NAS09-280].
Use SSH to connect to the target NAS Package where the NAS OS has started.
are required.

RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Password:
Linux nas1e 2.4.17-enas0200-SI20K014 #1 Thu Oct 23 13:35:50 JST 2003 i686 unknown
nasroot@nas2q:~$(This prompt is an example.)
nasroot@nas2q:~$ su
Passwd: ******
NAS09-310
NAS09-320 DKC515I
3. Obtain the dump file in the target NAS Package.

Specify the target NAS Package and to obtain the dump file.
Note: The NAS Package location specified in the command is not case-sensitive. If you enter
incorrect figures, you must re-execute the chmod command to retry.
nas2q:/home/nasroot# cd /sbin
nas2q:/sbin# chmod o+x enas_nasdump.sh
nas2q:/sbin# enas_nasdump.sh CHA-1E (Specify the NAS Package location)
If you want to continue, input a displayed number.
0123456789 (Ten random figures will be displayed.)
input > 0123456789 (Specify the same figures displayed in the prior line.)
again > 0123456789 (Specify the same figures again.)
Success.
nas2q:/sbin#
4. Collect the dump file.

Download the dump file following the procedure shown in section 3.5.15 Downloading Dump
Files [NAS03-1080]. Make sure that you select the correct NAS Package where you execute
the enas_autodump.sh on NAS Setup on SVP. Also, confirm that the NAS Package
location is contained in the filename displayed in the message from NAS Setup on SVP when
download is completed (in the example above, download is performed on 2Q, and the dump
filename to be displayed contains CHA-1E).
CAUTION
command syntax above shows lu01 (LU one).
NAS09-320
NAS09-330 DKC515I
9.4 Appendix D Setting NAS Time Zone

(1)
Change the mode to [Modify Mode] (CL).
(2)
Select (CL) [Install].
(3)
Select (CL) [Set Subsystem Time] in the
‘Install’ window.
(4)
Select (CL) [NAS Time Zone] in the ‘Set
Subsystem Time’ window, and then select
(CL) [OK].
NAS09-330
NAS09-340 DKC515I
(5)
The ‘TOD change (NAS Time Zone)’ window
appears.(The current NAS time zone is
displayed.)Select the desired NAS time zone
from the drop-down list and select (CL) [OK].
The details of the setting will be provided.
Please follow the instruction.
(6)
“The setting of NAS Time Zone is completed.”
is displayed.
Select (CL) the [OK] button.
(7)
Close the ‘Install’ window.
NAS09-340

22 Nas

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

22 Nas

Uploaded by

Copyright:

Available Formats

Hitachi Proprietary SC01486Z

NAS Software Section

NAS02-10 2. NAS Blade System Device Explanation

NAS03-10 3. NAS Installation

NAS03-290 3.5.4 Installing the NAS OS and Related Program Products

NAS04-10 4. NAS Hardware Replacement

NAS05-10 5. NAS Software FC

NAS06-10 6. NAS Configuration (Reconfiguration)

NAS07-10 7. NAS Troubleshooting

NAS07-500 7.5.9 RAID Failure (2 PDEVs: Error Information LUs)

NAS07-1010 7.7 NAS Hardware Replacement When a Failure Occurs

Table 1.1-1 Maintenance Tasks and Corresponding Reference Locations in this

2 Replacing - Replacing NAS Packages 4. NAS Hardware Replacement

(Continued from the previous page.)

The reference locations in other sections are as follows:

Table 1.1-2 Reference Locations in Other Sections

Table 1.1-3 Abbreviations for Software Products and Components

1.2 Related Manuals

Table 1.2-1 User's guide for disk subsystems

Table 1.2-2 User's guide for the NAS software products

1.3 Overview of Each Chapter

The chapters in this NAS Software Section are as follows:

Chapter 2. NAS Blade System Device Explanation

Chapter 3. NAS Installation

Two tables list the steps in the installation procedures:

Chapter 4. NAS Hardware Replacement

The area of a detailed flowchart is divided into three columns:

The following shows a sample description of a procedure.

<Sample Description of a Procedure>

User LU Command Device

Step Procedure Notes

Maintenance personnel System administrators NAS Blade system

Replacing the NAS package

Phone, E-mail: Phone, E-mail:

Phone, E-mail: Phone, E-mail:

Examples of the NAS conditions shown in procedures is below:

Chapter 5. NAS Software FC

Chapter 6. NAS Configuration (Reconfiguration)

Table 6.3-1 Types of Software Reconfiguration lists the classifications of software

Chapter 7. NAS Troubleshooting

Appendix B. Initializing Dump LUs explains how to initialize dump LUs.

2. NAS Blade System Device Explanation

2.2 NAS Blade System Hardware Configuration

Technical Support Maintenance server

NAS management console

Data & control LAN

NAS Package CL1-CHA NAS Package CL2-CHA

: Monitoring each other

Figure 2.2-1 Hardware Configuration of the NAS Blade System

2.3 NAS Blade System Software Configuration and Operating Environment

Maintenance servern Application server no

Web browser n Virus

NAS NAS NAS

ftp(S) n NAS Blade Manager

ftp(C) SNMP Agent XFS

SVP Web server NAS Data Control

RAID Driver Internode Comm

: Maintenance engineer : System administrator

Figure 2.3-1 Basic Configuration of the NAS Blade System

The NAS Blade system operation/management software consists of:

Table 2.3-1 List of NAS Servers and PCs

Table 2.3-2 lists the programs that make up the NAS.