IBM Netezza FDT Release 4.3.

FDT User’s Guide

Revised: Mar. 3, 2016

00X7003 Rev. 1.3

Note: Before using this information and the product that it supports, read the information in “Notices and Trademarks” on
page A-1.

© Copyright IBM Corporation 2015, 2016.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM
Corp.
 Contents

1 Before Installing FDT

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What’s Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Firmware Upgrade Time Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Identify Current Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Check FDT Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Check HPF Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Check NPS Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Check RHEL Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Determine the Active Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Check System Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Check Overall Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Check for Certain Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Check for other Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Check for Data Slice Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Check for Partition Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Update the HPF Release Prior to FDT Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2 Installing FDT
Install the FDT Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Core FDT and Service Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Hot Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Update NPS (if applicable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Time Estimation Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Power Cycle the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

3 Firmware Updates
Check the System Firmware Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Resolve sys_rev_check Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Host - All systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
RPC - N3001-002 and larger, N200x, and N1001. . . . . . . . . . . . . . . . . . . . . . . 3-5
MM - All systems (except N3001-001) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Gig Switch - All systems (except N3001-001) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

i
 SAS Switch - N1001 and 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Rack Switch Management - N3001-002 and larger, N200x, and N1001 . . . . . . . 3-6
Rack Switch Fabric - N3001-002 and larger, N200x, and N1001 . . . . . . . . . . . . 3-6
Chassis Power Supply - All systems (except N3001-001) . . . . . . . . . . . . . . . . . . 3-7
S-Blade - All systems (except N3001-001) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Storage Enclosure - N3001-002 and larger, N200x, and N1001 . . . . . . . . . . . . . 3-8
Storage Media - All systems (except N3001-001). . . . . . . . . . . . . . . . . . . . . . . . 3-8
Prepare the System for Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Transition an N3001/N200x/N1001 System to Maintenance Mode . . . . . . . . . . . 3-8
Prepare a Netezza 100 System for Firmware Updates . . . . . . . . . . . . . . . . . . . . 3-10
Install the Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Group 1 - AMM Firmware - All systems (except N3001-001). . . . . . . . . . . . . . . 3-11
Group 1 - S-Blade and HBA Firmware - All systems (except N3001-001) . . . . . . 3-13
Group 2 - GigSwitch Firmware - N3001-002 and larger, N200x, and N1001 . . . 3-17
Group 2 - Rack Management Switch Firmware - N3001-002+/N200x/N1001. . . 3-18
Group 2 - Rack Fabric Switch Firmware - N3001-002 +, N200x, and N1001. . . 3-19
Group 2 - PDU Firmware - N3001-002 and larger, N200x, and N1001 . . . . . . . 3-20
Group 3 - Disk Firmware - All systems (except N3001-001) . . . . . . . . . . . . . . . 3-21
Group 3 - ESM Firmware - N3001-002 and larger, N200x, and N1001 . . . . . . . 3-21
Group 4 - Host Firmware - All systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Power Cycle the SPAs and Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Verify the System Revision Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Restore the System to Normal Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Restore an N3001/N200x/N1001 System to Clustering Operations . . . . . . . . . . 3-31
Restore an IBM Netezza 100 System to Normal Operations . . . . . . . . . . . . . . . . 3-33

4 FDT Command Reference

firmware_updater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
firmware_updater Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

ii
 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
firmware_updater Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
firmware_updater RackFabSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
firmware_updater RackMgtSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
firmware_updater StorageEnclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
firmware_updater StorageMedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

iii
 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
storage_diags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
system_diags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
concheck Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
DataPathCheck Sample Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
sys_rev_check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
getservicedata.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

Appendix A: Notices and Trademarks

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Electronic Emission Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Regulatory and Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

iv
v
vi
 Preface
This guide includes a series of procedures you must follow to install, upgrade, and use FDT
on an IBM® PureData or Netezza appliance. Where possible, the procedures are listed in
the order in which you would perform them. Additionally, a chapter on command options is
included.

About This Guide

FDT User’s Guide is written for IBM support personnel and those authorized to repair any of
the IBM appliances. The procedures in this document assume the IBM appliance has been
previously installed and operational.

Topics See …

Requirements you must meet and procedures to per- “Before Installing FDT” on
form before installing FDT on an appliance. page 1-1

Procedures on how to install FDT on an appliance. “Installing FDT” on page 2-1

Procedures on how to upgrade firmware on an “Firmware Updates” on page 3-1

appliance.

Command reference for FDT. “FDT Command Reference” on

page 4-1

The Purpose of This Guide

FDT User’s Guide provides the procedures you must perform to upgrade FDT on an
appliance.

Symbols and Conventions

This guide uses the following typographical conventions:
 Italics for emphasis on terms and user-defined values such as user input
 Bold for command line input; for example, nzsystem stop

vii
If You Need Help
If you are having trouble using the IBM appliance, you should:
1. Retry the action, carefully following the instructions given for that task in the
documentation.
2. Go to the IBM Support Portal at: http://www.ibm.com/support. Log in using your IBM
ID and password. You can search the Support Portal for solutions. To submit a support
request, click the Service Requests & PMRs tab.
3. If you have an active service contract maintenance agreement with IBM, you can con-
tact customer support teams via telephone. For individual countries, visit the Technical
Support section of the IBM Directory of worldwide contacts
(http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html#phone).

Related Documentation
In addition to this FDT User’s Guide, every release of FDT includes Release Notes that are
available in the FDT package as well as on IBM Support Fix Central. The Release Notes
describe new features, fixed customer-reported issues, known issues, and sys_rev_check
versions.

Comments on the Documentation

We welcome any questions, comments, or suggestions that you have for the IBM Netezza
documentation. Please send us an e-mail message at [email protected]
and include the following information:
 The name and version of the manual that you are using
 Any comments that you have about the manual
 Your name, address, and phone number
We appreciate your comments on the documentation.

viii
 CHAPTER 1
Before Installing FDT
What’s in this chapter
 What’s New
 What’s Needed
 Identify Current Versions
 Determine the Active Host
 Check System Health
 Update the HPF Release Prior to FDT Installation

This chapter describes how to prepare the following appliances for an FDT upgrade:
 IBM PureData System for Analytics N3001
 IBM PureData System for Analytics N2001/N2002
 IBM PureData System for Analytics N1001 or IBM Netezza 1000
 IBM Netezza 100
Note: Throughout this guide, the IBM PureData System for Analytics N2001/N2002 is ref-
erenced as the N200x; the IBM PureData System for Analytics N1001 and IBM Netezza
1000 are referenced as the N1001.

Always refer to the Release Notes included with the FDT media to learn about what has
changed in this release as well as known issues that may affect firmware upgrades, and any
work-arounds for those issues. The Release Notes occasionally refer to RTC work items for
work-arounds, so a login to RTC is needed access the work items.

What’s New
FDT 4.3.1 introduces support for the N3001-001 appliance.
FDT 4.3 introduced updated firmware for the following components:
 S-Blades (HS22, HX5, and HS23)
 Hosts (HS22, x3650-M2, x3650-M3, x3650-M4, x3650-M4-HD, x3750-M4, x3750-
M4v2, x3850-X5)
 AMM
 BNT G8264 switch
 N3001-002 and larger chassis 10Gb Switch
 Hard disk drives

1-1
IBM Netezza FDT User’s Guide

FDT 4.3 introduced the following new features:

 --cfg option in sys_rev_check (ASU blade / host, host RAID)
 TMM FRU version query
 PSOC reporting in sys_rev_check
 SAS Backplane revision reporting in sys_rev_check
 Support for Lenovo branded Host Disks
 Logging timestamp updates
 FDT backup directory now /nzscratch
 An option to skip updating the Emulex driver during host firmware updates

What’s Needed
To complete all the tasks in this guide, the following items are required (available from IBM
Support Fix Central).
 The FDT 4.3.1 downloaded package or media
 If HPF or NPS needs to be updated, the downloaded package(s) or media for the
upgrade(s)

Prerequisites
The following table lists, by priority, the prerequisites of the FDT upgrade.
Table 1-1: Prerequisites to FDT Upgrade

Minimum N3001-002
Netezza 100 N1001 N2001 N2002 N3001-001
Requirement and larger

Physical access GigSwitch No

only*

User access root, nz

Check See “Check System Health” on page 1-5

system health

System state for nzstop maintenance mode**

firmware upgrades

FDT release 2.6.1 2.6.1 3.0.5.1 3.0.5.1 4.2.1 4.2.0.1

HPF release 5.3.3 5.3.3 5.3.4 5.3.4 5.4.1 5.4

NPS release 7.0.2 P6 7.0.2 P6 7.0.2 P6 7.0.4 P1 7.2.0.1 7.2.0.0 P1

RHEL release 5.8 5.8 6.2 6.4 6.5 6.5

* For IBM Netezza 100 systems, the process to update the GigSwitch firmware requires
media and physical access. You must provide physical access to the system and a KVM or
other connection to the system.
** Maintenance mode not required when firmware update performed through replacespu
(during S-Blade servicing).

1-2 00X7003 Rev.1.3

 What’s Needed

Full System Backup - As a best practice, you should perform a full system backup prior to
performing any upgrade procedures. This includes the database disk drives as well as the
host disk drives.
If upgrades to minimum levels are required, always upgrade in this order:
 HPF
 Host Management (minimum rev. 5.4)
 Service_tools
 FDT
 Netezza software
If you do not need to upgrade all of the components, keep the same order but omit the
component(s) not required.
You must be familiar with Linux commands such as tar and running scripts from a com-
mand prompt. To idle the system for maintenance, you must be familiar with commands
such as nzstop and nzstart, and also the heartbeat and DRBD management commands,
which are documented in the System Administrator’s Guide.

Firmware Upgrade Time Expectations

To estimate the time needed for firmware upgrades, the latest FDT software must first be
installed on the system, and then the latest version of sys_rev_check is run to identify the
modules needing update. This is described in “Time Estimation Check” on page 2-6.
For FDT v4.3, Host Firmware updates are required. Host firmware updates can take up to
three hours (to update both hosts).
To reduce the overall system impact to users,
 Use the nzhealthcheck, sys_rev_check, and nzhw -issues commands to identify certain
system and hardware issues and resolve them before you proceed to the firmware
upgrades (see “Check for other Hardware Issues” on page 1-7).
 Use the nzds -issues command to identify any data slice issues and resolve them
before you proceed to the firmware upgrades (see “Check for Data Slice Issues” on
page 1-7).
 Use the nzspupart -issues command to identify any partition issues and resolve them
before you proceed to the firmware upgrades (see “Check for Partition Issues” on
page 1-7).
 Perform the steps in “Install the FDT Components” on page 2-1 while the system is
online.
 Perform the steps in “Check the System Firmware Revisions” on page 3-1 while the
system is online.
Note: Some hardware replacement tasks can be performed while the system is online, but
others require system downtime.

If your system requires firmware updates, schedule a maintenance window where you can
take the system offline to perform the firmware updates. Users will be unable to access the
system for queries during the downtime.

00X7003 Rev.1.3 1-3

IBM Netezza FDT User’s Guide

Identify Current Versions

The following sections provide details on how to check the versions of software currently
installed on the appliance.

Check FDT Version

To check the FDT version:
[nz@nzhost1 ~] cat /opt/nz/fdt/version.txt
Example output for FDT version 4.3:
FDT 4.3
Build Number: 28609, Date 2014/08/17 15:00:06
Example output for FDT version without Hot Fixes:
FDT 4.3
Build Number: 28609, Date 2014/08/17 15:00:06
Example output for FDT version with Hot Fixes:
FDT 4.3
Build Number: 23456, Date: 2014/09/01 12:38:58
----------------------------------------------------------------------
INSTALL DATE COMPONENT BUNDLE NAME
----------------------------------------------------------------------
2014/09/07 13:20:58 StorageMedia storagemedia_hus723020als64_
firmware_20111203_092445.tar.gz
2014/09/10 12:55:15 StorageMedia storagemedia_st1000nm0001_
firmware_20130101_111413.tar.gz
2014/09/10 12:55:15 StorageMedia storagemedia_st31000424ss_
firmware_20130101_104833.tar.gz

Check HPF Version

To check the HPF version:
[root@host1 ~] cat /nzlocal/scripts/version.txt
Host Platform Configuration Version 5.4
2014-06-23.33556.hpf.rel-hpfConfig-5.4.cm.33556

Check NPS Version

To check the NPS version, as user nz:
[nz@host1 ~]$ nzrev
Release 7.2 [Build 36178]

Check RHEL Version

To check the RHEL version:
[nz@host1 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.5

Determine the Active Host

Throughout this guide you are directed to issue commands from the active host. To identify
the active host, use the following steps:
1. Issue the command:

1-4 00X7003 Rev.1.3

 Check System Health

[root@nzhost1 ~]# crm_mon -i3

2. Monitor crm_mon until the screen has output similar to the following:
============
Last updated: Tue Feb 25 13:11:49 2014
Current DC: host-2 (91305d9f-f41d-4336-997a-1519390396f4)
2 Nodes configured.
2 Resources configured.
============

Node: hostname-1 (e890696b-ab7b-42c0-9e91-4c1cdacbe3f9): online

Node: hostname-2 (72043b2e-9217-4666-be6f-79923aef2958): online
Resource Group: nps
drbd_exphome_device (heartbeat:drbddisk): Started hostname-1
drbd_nz_device (heartbeat:drbddisk): Started hostname-1
exphome_filesystem (heartbeat::ocf:Filesystem): Started hostname-1
nz_filesystem (heartbeat::ocf:Filesystem): Started hostname-1
fabric_ip (heartbeat::ocf:IPaddr): Started hostname-1
wall_ip (heartbeat::ocf:IPaddr): Started hostname-1
nzinit (lsb:nzinit): Started hostname-1
fencing_route_to_ha1 (stonith:apcmastersnmp): Started hostname-2
fencing_route_to_ha2 (stonith:apcmastersnmp): Started hostname-1
3. The line that includes nzinit list the active host, in this case listed as hostname-1.
4. Press Ctrl-C to exit crm_mon.

Check System Health

Prior to beginning the FDT upgrade procedure on an NPS system, the system must be in a
known healthy state. The following sections provide steps that ensure the system is healthy.
The system must be online to perform the steps in the following sections.

Check Overall Health

Follow these steps to check system health:
1. Log into the active host as the nz user.
2. Run the system revision check software:
[nz@host1 ~]$ nzhealthcheck
Example output:
******************************************************************
******************* System Health Check Report********************
******************************************************************
Report generation date: 2015-03-16 15:21:13
***************************** MINI SYSINFO************************
+ Product : IBM PureData System for Analytics N3001-010
+ Model : Q100_M
+ HPF : 5.4
+ FDT : 4.2.0.2
+ NPS : 7.2.0.4 [Build 43444]
+ NPS State : online
+ MTM(s) : 3567-EE9
+ NzId : NZ35112
+ NZ Owner : nz
+ OS : Red Hat Enterprise Linux Server release6.5(Santigo)

00X7003 Rev.1.3 1-5

IBM Netezza FDT User’s Guide

+ Kernel : 2.6.32-431.17.1.el6.x86_64
+ HealthCheck : 2.3.1.2 [20150311221708]
+ Hostname : NZ35112-H1
+ NPS Up Time: 3 days, 4 hrs, 4 mins, 43 secs
+ Host Up Time: rack1.host1 : 112 days 3 hours 48 minutes 10 seconds
+ Host Up Time: rack1.host2 : 103 days 1 hours 27 minutes 13 seconds
+ CallHome : No address information

Failures (2):
- Rule --+------ Issue ------+------ Component -----+- Severty --
SHC027 | Failed hardware | ...output omitted | Medium
SHC910 | Host disk's issue | rack1.host1.hos (...) |High|detected
- Rule --+------ Issue ------+------ Component -----+- Severty --

Report stored in /nz/kit.7.2.0.4.43444/log/nzhealthcheck/Netez-

zaSystem_Health_Check_Report_20150316_163718.txt
All done

Rules - Policy rules - in the Rule column of the output - are troubleshooting rules that
are used for automatic analysis of system health and for proposing a relevant solution.
These rules cover the most frequent issues that are experienced in the field. You can
view a complete list of rules in a PDF document that is located on your system in /nz/
kit/share/nzhealthcheck/rules-doc.pdf. Note: Rule evaluation depends on the platform,
so not all rules may be evaluated on your system. The rules-doc.pdf document provides
detailed information about which platforms are supported by particular rules.
All System Health Check rules provide problem description and advice. Some of them
involve complex logic, for example, identifying the correct disk/SPU/enclosure balance.
The rules may depend on one another.
All rules have severity assigned:
 High - Actionable issues that might be critical
 Medium - Actionable issues
 Low - The rules may help in problem investigation but they do not require immedi-
ate action

Check for Certain Hardware Issues

To check for hardware problems such as AMM internal issues, HBA issues, DIMM failures,
and CPU failures not found with other health check programs, run the current version of
sys_rev_check.

Run sys_rev_check
As user root, run sysrevcheck to verify that the system is configured correctly:
Change directory.
[root@host ~]# cd /opt/nz/fdt
Run the command:
[root@host ~]# ./sys_rev_check
This run of sys_rev_check is only to identify possible hardware issues. Results showing
firmware revisions, [PASS], [ABOVE], [PEND], or [BELOW], are to be ignored at this point.

1-6 00X7003 Rev.1.3

 Update the HPF Release Prior to FDT Installation

The [FAIL] status indicates that the system has a hardware issue that you need to investi-
gate and resolve before you update the firmware. If the sys_rev_check command displays a
[FAIL] message, review the /opt/nz/fdt/log/sysrev_check_yyyymmdd_hhmmss.txt log file to
identify the cause of the [FAIL] status.

Check for other Hardware Issues

Prior to installing any firmware updates, the system must be in a known healthy state.
Note: The nzhw -issues command does not detect certain hardware problems, such as
AMM internal issues, HBA issues, DIMM failures, and CPU failures. These issues should
have been previously identified with sys_rev_check.

Check for hardware issues:

1. As the nz user, issue the command:
[nz@host1 ~]$ nzhw -issues
2. If there are issues, they must be resolved before continuing.
Note: Some hardware replacement tasks can be performed while the system is online, but
others require system downtime.

Continue to the next section to check system date slice issues. See the Netezza System
Administrator’s Guide for information on the nzhw command.

Check for Data Slice Issues

Prior to installing any firmware updates, the system must be in a known healthy state.
Check for issues with:
1. As the nz user, issue the command:
[nz@host1 ~]$ nzds -issues
2. If there are data slice issues, they must be resolved before continuing.
See the System Administrator’s Guide for information on the nzds command.

Check for Partition Issues

Prior to installing any firmware updates, the system must be in a known healthy state.
Check for issues with:
1. As the nz user, issue the command:
[nz@host1 ~]$ nzspupart -issues
2. If there are partition issues, they must be resolved before continuing.
See the System Administrator’s Guide for information on the nzspupart command.

Update the HPF Release Prior to FDT Installation

Ensure that the minimum version of HPF is installed on the system, as described in
“Prerequisites.”
To check the versions of HPF:
1. Log in as user root.

00X7003 Rev.1.3 1-7

IBM Netezza FDT User’s Guide

2. Type:
[root@host1 ~]# cat /nzlocal/scripts/version.txt
Example output:
Host Platform Configuration Version 4.11
2011-03-14.16224.dev-hpfConfig-xs2.cm.16224
3. If the version of HPF installed on the system does not meet the minimum version,
upgrade HPF. Instructions for upgrading HPF can be found in the Release Notes docu-
ment contained within the new HPF bundle.

1-8 00X7003 Rev.1.3

 CHAPTER 2
Installing FDT
What’s in this chapter
 Install the FDT Components
 Update NPS (if applicable)
 Time Estimation Check
 Power Cycle the System

This chapter provides procedures needed to install FDT on an existing system.

Install the FDT Components

Follow these steps to install the FDT components on your system. You can perform these
procedures while the system is online and available to users.
The software installation process requires approximately 2.3 GB of disk space on the sys-
tem host. (For HA systems, this installation program adds the files to both hosts.) The
following procedure provides instructions for determining if your system has sufficient
space available.

There are three components of FDT 4.3:

 Core FDT (included in the FDT 4.3 fix pack on Fix Central)
 Service Tools (included in the FDT 4.3 fix pack on Fix Central)
 Hot Fixes (included in the interim fix on Fix Central, if available)
If you are installing core FDT 4.3 and Hot Fixes are available that apply to 4.3, we advise
that you install the core FDT, service tools, and the Hot Fix(es) in the same session before
updating firmware.

Core FDT and Service Tools

To install the core FDT and Service Tools software on the Netezza system, follow these
steps:
1. Log in to the active host as the root user.
2. Check for free disk space:
[root@host1 ~]# df -h /opt

2-1
IBM Netezza FDT User’s Guide

Example output:
Filesystem Size Used Avail Use% Mounted on
/dev/sda8 7.8G 2.5G 5.0G 33% /opt
If backups of FDT are present on the system, they are deleted during the installation,
creating additional free space: 600 MB for FDT 2.x, 1 GB for FDT 3.x, and 2 GB for
FDT 4.x. With the backups deleted, the system must have at least 2.3 GB available.
3. Perform one of the following steps depending upon whether you are installing from a
downloaded software image or from media:
 If you are installing the FDT software from a downloaded software kit:
a. Save the compressed FDT tar file (named fdt-4.3.tar.gz) and the install file
(named install) on host 1 in a /tmp directory such as /tmp/fdt.
b. Change to the directory where you saved the files, and then to the fdt directory.
 If you are installing the FDT software from media, place the media into the media
tray or USB port of the active host and type (commands vary according to system or
type of media):
[root@host1 ~]# mount /media/cdrecorder
or
[root@host1 ~]# mount /media/cdrom
or
[root@host1 ~]# mount /dev/sdb1 /mnt

Then change directory to the mounted media. Type:

[root@host1 ~]# cd /media/cdrecorder/fdt
or
[root@host1 ~]# cd /media/cdrom/fdt
or
[root@host1 ~]# cd /mnt/fdt
4. Enter the following command to install the FDT software on both hosts:
[root@host1 ~]# ./install
The installation command displays an error and exits if HPF Release 5.4 is not already
installed on the system. Sample output follows for an installation; note that the output
can vary in content for the platform and FDT release.
Staging FDT libraries, please wait ... done.
------------------------------------------------------------------
***** F D T v4.3 I N S T A L L E R *****
---------------------------SETUP----------------------------------
Now checking platform prerequisites [DONE]
Now checking local HPF version [DONE]
Now checking peer HPF version [DONE]
Now checking NPS version [DONE]
Now checking local lock file [DONE]
Now checking peer lock file [DONE]
Now creating the lock file [DONE]
Now creating lock on peer host [DONE]
----------------------------LOCAL HOST----------------------------
Now processing RPM requirements [DONE]
Now cleaning up backed-up FDT directories [PASS]
Now backing-up original FDT 4.3 installation [DONE]

2-2 00X7003 Rev.1.3

 Install the FDT Components

Now installing FDT 4.3 [DONE]

Now creating the lock file [DONE]
Now copying files and starting peer host install [DONE]
---------------------------PEER HOST------------------------------
Staging FDT libraries, please wait ... done.
Now processing RPM requirements [DONE]
Now cleaning up backed-up FDT directories [PASS]
Now backing-up original FDT 4.3 installation [DONE]
Now installing FDT 4.34.3 [DONE]
-----------------------------CLEANUP------------------------------
Now moving logs on peer host [DONE]
Now removing peer lock files [DONE]
Now moving logs on local host [DONE]
------------------------------SUMMARY-----------------------------
Final status [PASS]
Main log file - /opt/nz/fdt/log/install_20140110-102407.log
Prior FDT backup - /nzscratch/fdt_backup/fdt_20140110-102407
FDT installation - /opt/nz/fdt
------------------------------------------------------------------
The install script installs the FDT software in directory /opt/nz/fdt on both hosts. If a
previous version of FDT was installed on both hosts, the installation script creates a
backup copy of the previous firmware and service tools directories and saves it as a
date-stamped directory in the directory named /nzscratch/fdt_backup on both hosts.
Only one full backup is retained.
Each backup copy of a previous FDT 4.x release consumes approximately 2.25GB of space.
Do not delete these backup copies without consulting Support. They may be required for
future hardware and device troubleshooting.

5. Change directory:
[root@host1 ~]# cd /media/cdrom/service_tools
or
[root@host1 ~]# cd /media/cdrecorder/service_tools
or
[root@host1 ~]# cd /mnt/service_tools
or
If installing from a downloaded software kit, change to the directory where you saved
the files and then to the service_tools directory.
6. Enter the following command to install the service tools onto the Netezza active host:
[root@host1 ~]# ./install
7. If installing from disk media, type the commands:
[root@host1 ~]# cd
[root@host1 ~]# eject
8. Service Tools must be manually installed on the non-active host.
Log into the non-active host as the root user.
9. Do one of the following steps depending upon whether you are installing from the DVD
or from a downloaded software image:
 If you are installing the software from a downloaded software kit:

00X7003 Rev.1.3 2-3

IBM Netezza FDT User’s Guide

a. Save the compressed tar file and the install file (named install) on the host in a
/tmp directory such as /tmp/service_tools.
b. Change to the directory where you saved the files, and then to the service_tools
directory.
 If you are installing the software from the FDT DVD, place the media into the
media tray of the non-active host and type the following commands:
[root@host2 ~]# mount /media/cdrecorder
or
[root@host2 ~]# mount /media/cdrom
or
[root@host2 ~]# mount /dev/sdb1 /mnt
Then type:
[root@host2 ~]# cd /media/cdrecorder/service_tools
or
[root@host2 ~]# cd /media/cdrom/service_tools
or
[root@host2 ~]# cd /mnt/service_tools
10. Enter the following command to install the service tools onto the Netezza non-active
host:
[root@host2 ~]# ./install
11. If installing from disk media, type the commands:
[root@host2 ~]# cd
[root@host2 ~]# eject
12. Remove the media from the drive.

Hot Fixes
Downloads of independent component firmware packages are available from IBM Support
Fix Central. These packages allow for updating the firmware of individual components with-
out the need to download and install a complete core FDT package. Once the Hot Fix
package is downloaded and copied to a host server, it is installed using this process. After
installation, the firmware can be updated using the same firmware_updater process as if
the firmware was part of the core FDT package.
To install Hot Fix packages:
1. Download the interim fix package from IBM Support Fix Central.
2. Copy the package to portable media and then to the /tmp directory of the active host
server (or copy to the active host server over the network).
3. Unzip the package in the /tmp directory.
[root@host1 ~]# unzip package_name
For example:
[root@host1 ~]# unzip 1.0.0.1-IM-Netezza-FDT-IF71335
The output of the command lists the firmware packages in Hot Fix package.

2-4 00X7003 Rev.1.3

 Update NPS (if applicable)

4. To install the firmware package(s) (this does not mean that firmware is updated, only
loaded into the FDT directories), type the following commands and include the path-
names to all packages to be installed:
[root@host1 ~]# cd /opt/nz/fdt
[root@host1 ~]# ./firmware_updater --install-firmware <full
pathname to bundle(s)>
For example:
[root@host1 ~]# ./firmware_updater --install-firmware
/tmp/storagemedia_st1000nm001_firmware_20130101_111413.tar.gz
/tmp/storagemedia_st3100424SS_firmware_20130101_104833.tar.gz
Example output:
[root@host1 fdt]# ./firmware_updater --install-firmware /tmp/
storagemedia_st1000nm0001_firmware_20130101_111413.tar.gz /tmp/
storagemedia_st31000424ss_firmware_20130101_104833.tar.gz

--------------F I R M W A R E B U N D L E I N S T A L L---------------
INSTALL DATE COMPONENT BUNDLE NAME
2013/01/10 12:55:15 StorageMedia storagemedia_st1000nm0001_
firmware_20130101_111413.tar.gz
2013/01/10 12:55:15 StorageMedia storagemedia_st31000424ss_
firmware_20130101_104833.tar.gz
----------------------------------------------------------------------
Successfully added firmware to FDT.
To update firmware, run firmware_updater with the desired component to
update.
------------------------------------------------------------------
----
Note: If you later want to uninstall packages after they are installed, use the command
./firmware_updater --remove-firmware <bundle_name>

5. Run the command:

[root@host1 ~]# ./sys_rev_check
The output of the command shows if any firmware requires updating.

Update NPS (if applicable)

If the version of NPS on the system does not meet the minimum requirements (see “Pre-
requisites” on page 1-2), updates must be made at this time. Refer to the NPS upgrade
instructions for the release being installed.

00X7003 Rev.1.3 2-5

IBM Netezza FDT User’s Guide

Time Estimation Check

For the purpose of estimating how long an FDT upgrade will take, once the FDT software is
installed, run sys_rev_check to identify which firmware modules require updating.
Follow these steps to run the sys_rev_check utility:
1. Change to the directory that contains the system revision check software:
[root@host1 ~]# cd /opt/nz/fdt
2. Run the command:
[root@host1 ~]# ./sys_rev_check
To determine how much time the FDT firmware upgrade(s) will take, at this point you only
need to be concerned with results that show the [BELOW] status indication. The compo-
nent(s) with the [BELOW] status indication are the ones requiring firmware upgrade(s).
The following table outlines the estimated time requirements to update the firmware:
Table 2-1: Time Estimates of Firmware Upgrades

Firmware Time

AMM 60 minutes (up to 3 hours) to update the AMMs.

There are different procedures for updating the 100 systems.
S-Blade/HBA About 60 minutes per system; however, the update could take
as long as 2.5 hours on large multi-rack systems (if there are
delays while communicating with the hardware components).
GigSwitch About 30 minutes per system.
(To save time, switches can be updated in the same command
string used for AMMs) There are different procedures for
updating the 100 systems.

Rack The firmware update takes about 5 minutes per switch to

Management complete. The total time for the update must take into
Switch account the total number of switches.
Does not apply to a 100 system.
Rack The firmware update takes about 10 minutes per switch to
Fabric Switch complete.
Does not apply to a 100 system.

ESM On N3001/N200x/N1001, about 40 minutes per system.

Does not apply to a 100 system.

Disk - About 15 minutes per N200x system.

- About 30 minutes (up to 1 hour) per N1001 system.
- About 10 minutes per 100 system.

Host About 60 minutes per system; however, the update could take
as long as 90 minutes, depending on host NIC configuration.
NOTE: Host firmware updates are required for this release.
(One reboot required)

To know the approximate time for the full FDT upgrade, you need the results of running
sys_rev_check. Once results from running sys_rev_check are obtained and components
requiring updated are identified, use the following table to estimate the total update time.

2-6 00X7003 Rev.1.3

 Time Estimation Check

This version of FDT supports modular upgrades, allowing separate service windows for
updates, if necessary. Each group must be completed, at a minimum, within a service
window.
Table 2-2: Time Estimate Worksheet

Update Group Firmware Type System Update Time Comment

1 AMM All 60 minutes Single update

S-Blade and HBA All 60 minutes See Time Estimate in

Table 2-1.

Group UpdateTime =

2 GigSwitch All 30 minutes See Time Estimate in

Table 2-1.

Rack All (except 100) 5 minutes 1 switch

Management Switch 10 minutes 2 switches
15 minutes 3 switches

Rack All (except 100) 20 minutes 2 switches

Fabric Switch

PDU All (except 100) 15 minutes

Group UpdateTime =

3 ESM All
N200x/N1001 40 minutes

Disk All See Time Estimate in

N2001/N2002 15 minutes Table 2-1.
N1001/1000 30 minutes
100 10 minutes

Group UpdateTime =

4 Host All 90 minutes Reboot(s) required

Group UpdateTime =

Total UpdateTime =

During the scheduled service window, follow the steps in the “Prepare the System for Firm-
ware Updates” on page 3-8 section to transition the system into maintenance mode, then
proceed to the “Install the Firmware Updates” on page 3-11 section to perform the
upgrades that your system requires. Finally, the “Restore the System to Normal Operations”
on page 3-31 section describes how to return the system to normal operation and restore
user access.
If system power is interrupted during the FDT update process, the hardware may be left in
a state that prevents further FDT updates or normal operation. Do not power off or remove
any component of the appliance during the FDT update process unless instructed to do so.

00X7003 Rev.1.3 2-7

IBM Netezza FDT User’s Guide

Power Cycle the System

After installing the FDT software on an NPS system, and before checking the system soft-
ware revisions, you must power cycle the system to verify that all components are healthy
and respond to the power cycle:
1. Log into the Netezza active host as the nz user.
2. Check the state of the Netezza system:
[nz@hosthost1 ~]$ nzstate
System state is 'Online'.
3. If the system state is online, stop the system using the command:
[nz@host1 ~]$ nzstop
4. Wait for the system to stop using the command:
[nz@host1 ~]$ nzstate
System state is 'Stopped'.
5. Log in as root.
6. Power off the SPAs:
[root@host1 ~]# cd /nzlocal/scripts/rpc
[root@host1 ~]# ./spapwr.sh -off all
Sample output follows:
Host Platform Configuration Version 5.4
2014-05-19.17322.rel-hpfConfig-4.cm.17322
Power off SPA01 ... #blades=4, blades(1 3 9 11) .. finished.
Finished SPA power on/off.
7. Wait 30 seconds, then power on the SPAs:
[root@host1 ~]# /nzlocal/scripts/rpc/spapwr.sh -on all
Sample output follows:
-------------------------------------------------------------------
Host Platform Configuration Version 5.4
2014-05-19.17322.rel-hpfConfig-5.4.cm.17322
2014-05-26 14:56:11 EDT: rpc rack 1 lower right outlet 1 powered on.
2014-05-26 14:56:11 EDT: rpc rack 1 lower right outlet 5 powered on.
.
.
2014-05-26 14:56:15 EDT: rpc rack 1 lower left outlet 18 powered on.
2014-05-26 14:56:15 EDT: rpc rack 1 lower left outlet 21 powered on.
Power on SPA01 ... #blades=4, blades(1 3 9 11) .. finished.
Finished SPA power on/off.
8. As user nz, restart the Netezza system:
[nz@host1 ~]$ nzstart
9. Wait for the system to come online using the command:
[nz@host1 ~]$ nzstate
System state is 'Online'.
10. As the nz user, issue the command:
[nz@host1 ~]$ nzhw -issues
11. If there are issues, they must be resolved before continuing.

2-8 00X7003 Rev.1.3

 CHAPTER 3
Firmware Updates
What’s in this chapter
 Check the System Firmware Revisions
 Resolve sys_rev_check Issues
 Prepare the System for Firmware Updates
 Install the Firmware Updates
 Verify the System Revision Checks
 Restore the System to Normal Operations

This chapter provides procedures needed to make firmware updates on an existing system.

Check the System Firmware Revisions

The FDT distribution includes the system revision check (sys_rev_check) software utility
that you use to check the revisions of the firmware used by the hardware components. For
best results, perform this procedure while the system is online. The sys_rev_check utility
compares the current versions to a list of the latest known good versions. If the utility
reports any components that have an older version or incorrect versions of firmware, you
can use the update procedures in “Install the Firmware Updates” on page 3-11 to bring
those components up to the correct revision.
Note: The sys_rev_check command usually takes one to two minutes to complete.

Follow these steps to run the sys_rev_check utility:

1. Log into the active host (as the root or nz user).
Note: When running sys_rev_check while logged in as user nz, results for Host Rev
Check, Blade Hardware Check, Blade Ethernet Check, and Blade HBA Check are not
available.

2. Change to the directory that contains the system revision check software:
[root@host1 ~]# cd /opt/nz/fdt

3. Run the command:

[root@host1 ~]# ./sys_rev_check
The results for your system can vary by model and FDT revision; the utility reports warnings
and errors for any problems that it detects.

3-1
IBM Netezza FDT User’s Guide

 The [PASS] status indicates that the firmware is current and does not require an
update.
 The [BELOW] status indicates that the component is running an older version of firm-
ware than what is provided by this FDT bundle, and you should update the firmware for
that component.
 The [ABOVE] status indicates that the component is running a newer version of firm-
ware than what is provided by this FDT bundle. This is normally not an issue, but if an
unforeseen incompatibility is detected, it may necessitate downgrading the firmware to
the version provided in this FDT bundle. Only attempt a downgrade when directed to
do so by IBM Customer Support.
 The [PEND] status indicates that a version of firmware has been loaded onto the sys-
tem, but it is not active yet, pending a reboot of the system. The number of
components with firmware pending a reboot is noted in the next line of the sys_rev_
check output.
 The [FAIL] status indicates the system has a hardware issue that you need to investi-
gate and resolve before you update the firmware. If the sys_rev_check command
displays a FAIL message, review the /opt/nz/fdt/log/sys_rev_check.log file to identify the
cause of the FAIL status. For more information about sys_rev_check issues and their
meaning, see the section “Resolve sys_rev_check Issues” on page 3-4.
 A [WARN] here indicates a version of firmware that is below the required level, and
must be updated using FDT Support Tools, not the firmware_updater utility. Examine
the log file for details on the firmware component that requires updating.
A sample of sys_rev_check output follows. Output varies depending on system type and
components.
Note: On N3001-002 and larger systems, if FDT Support Tools has been used to update
the Blade Ethernet firmware on the HS23 blades, the BLADE ETHERNET CHECK status is
[FAIL] if the firmware is loaded but the blades have not been rebooted, or [ABOVE] if the
blades have been rebooted and the firmware enabled. The [ABOVE] status is expected and
acceptable.

Note: The IMM check on some hosts may indicate IMM_REV as missing / [FAIL] status.
This indicates that the IMM needs to be updated using firmware_updater host or firmware_
updater host --update-bmc.

[root@host1 ~]# ./sys_rev_check

----------------------------------------------------------------------
***** S Y S R E V C H E C K *****
FDT 4.3 - /opt/nz/fdt/log/sys_rev_check_yyyymmdd-hhmmss.log
--------------------------CHECKING SPU STATE--------------------------
Checking if the system is online [DONE]
------------------------------HOST CHECK------------------------------
ha1 [PASS]
ha2 [PASS]
------------------------------RPC CHECK-------------------------------
rpc1ur [PASS]
rpc1lr [PASS]
rpc1ul [PASS]
rpc1ll [PASS]
------------------------------MM CHECK--------------------------------
mm001 [PASS]
mm001alt [PASS]

3-2 00X7003 Rev.1.3

 Check the System Firmware Revisions

mm002 [PASS]
mm002alt [PASS]
----------------------------SPA GIG CHECK-----------------------------
gigsw01a [PASS]
gigsw01b [PASS]
gigsw02a [PASS]
gigsw02b [PASS]
----------------------------SPA SAS CHECK-----------------------------
sassw01a [PASS]
sassw01b [PASS]
sassw02a [PASS]
sassw02b [PASS]
------------------------RACK SWITCH MGT CHECK-------------------------
netswmgt01 [PASS]
------------------------RACK SWITCH FAB CHECK-------------------------
There are no FABRIC Switches installed
------------------------SPA POWER SUPPLY CHECK------------------------
SPA 01 [PASS]
SPA 02 [PASS]
-------------------------BLADE FIRMWARE CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-------------------------BLADE HARDWARE CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-------------------------BLADE ETHERNET CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
------------------------------HBA CHECK-------------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]

00X7003 Rev.1.3 3-3

IBM Netezza FDT User’s Guide

spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-----------------------STORAGE ENCLOSURE CHECK------------------------
SPA 01 Enclosure 1 [PASS]
SPA 01 Enclosure 2 [PASS]
SPA 01 Enclosure 3 [PASS]
SPA 01 Enclosure 4 [PASS]
SPA 02 Enclosure 1 [PASS]
SPA 02 Enclosure 2 [PASS]
SPA 02 Enclosure 3 [PASS]
SPA 02 Enclosure 4 [PASS]
--------------------------STORAGE MEDIA CHECK-------------------------
SPA 01 Enclosure 1 [PASS]
SPA 01 Enclosure 2 [PASS]
SPA 01 Enclosure 3 [PASS]
SPA 01 Enclosure 4 [PASS]
SPA 02 Enclosure 1 [PASS]
SPA 02 Enclosure 2 [PASS]
-------------------------------SUMMARY-------------------------------
Final status [PASS]
Total Failures 0
Total Revs Below 0
Total Rev Above 2
Main log file - /opt/nz/fdt/log/sys_rev_check_yyyymmdd-hhmmss.log
----------------------------------------------------------------------
If the final status of the sys_rev_check test is [PASS], all the firmware revisions have
“passed” and meet the latest criteria. Your system does not require any firmware updates
and you can skip the rest of this document.

Resolve sys_rev_check Issues

The sys_rev_check command examines the hardware of the system to evaluate whether
there are any firmware revision issues or hardware issues that you need to investigate on
your system. This section provides a closer look at sys_rev_check log file issues and how to
resolve them.
Conditions listed as [ABOVE] do not necessarily require corrective action.

Some of these issues are corrected using the procedures described in this guide; however,
some cases require Support assistance and/or physical access to the IBM Netezza system.
Contact IBM Netezza Support for issues relating to hardware problems and replacement, or
to upgrade procedures which are not documented in this guide.

You can review the final results log file to identify the cause of the non-PASS status for
components; the most common issues are a result of firmware that is below the minimum
required level.
Review the “Firmware Upgrade Time Expectations” on page 1-3 required for each type of
firmware update. Plan to schedule a service window when you can idle the system to
update the firmware. During the service window, use the next section, “Prepare the System
for Firmware Updates”, to begin the process to update the firmware.
Note: If the log file shows any hardware-related problems (indicated by [FAIL]), investigate
and fix those issues before you attempt to update the firmware, then re-run the sys_rev_
check command to obtain the latest status.

3-4 00X7003 Rev.1.3

 Resolve sys_rev_check Issues

The following sections describe how to resolve conditions in the sys_rev_check output.

Host - All systems

The Host firmware updates for FDT 4.3 replace the separate media in previous releases
that was required for host firmware updates, including the Emulex NIC driver and firmware
updates.
A [WARN] here indicates a version of firmware that is below the required level, and must be
updated using FDT Support Tools, not the firmware_updater utility. Examine the host log
file for details on the firmware component that requires updating.
A [BELOW] here indicates an older firmware version for at least one host component.
A [PEND] here indicates a new firmware version for at least one host component has been
loaded onto the system, but is not active yet, pending a system reboot.
A [FAIL] here indicates the system has a hardware issue that you need to investigate and
resolve before you update the firmware. Review the /opt/nz/fdt/log/sys_rev_check.log file to
identify the cause of the FAIL status. If the log file shows the disk as something other than
missing, the issue is that there is no firmware support available for the disk. If the disk is
reported as missing then there is an issue with the health of the disk or it’s simply not
installed/present or otherwise accessible. If all disks report missing, check the RAID firm-
ware for [PASS] or [BELOW] or missing and if not [PASS] then the RAID controller may be
the cause of disks shown as missing.
An [INFO] in the host log file indicates that sys_rev_check is not able to assess the current
firmware revision of the indicated component. As a result, the firmware of that host compo-
nent cannot be updated by FDT. In most cases, utilities available though Fix Central or
external or third party update utilities are required to update these components, which
include host disk drives, 1Gb NICs, Chelsio 10GB NICs, some Broadcom 1GB NICs for
some hosts (x3650-M1/M2/M3 and x3850-M2).
For FDT 4.3, host firmware updates are required, regardless of the output from sys_rev_
check.
See “Group 4 - Host Firmware - All systems” on page 3-22.
Note: When running sys_rev_check while logged in as user nz, results for Host Rev Check
are not available.

Note: The IMM check on some hosts may indicate IMM_REV as missing / [FAIL] status.
This indicates that the IMM needs to be updated using firmware_updater host of firmware_
updater host --update-bmc.

Note: On x3650-M1 (7979) and x3850-M2 (7233) hosts with NPS versions prior to 7.x,
sys_rev_check may indicate that RAID_FW component arcconf is not installed, with a
[WARN] status. This indicates that arcconf needs to be manually installed. A version of arc-
conf (and installation instructions) can be downloaded from the IBM Support Portal.

Note: The sys_rev_check output does not report on customer use PCI slots that may contain
networking cards added during or after system installation. For example, in hosts x3750-
M4 slots 1,2,3 are not reported, and in x3650-M4 slots 1,2,4 are not reported.

RPC - N3001-002 and larger, N200x, and N1001

A [BELOW] here indicates an older version of power controller firmware.

00X7003 Rev.1.3 3-5

IBM Netezza FDT User’s Guide

Use “Group 2 - PDU Firmware - N3001-002 and larger, N200x, and N1001” on
page 3-20.
Not applicable for Netezza 100 systems.

MM - All systems (except N3001-001)

[BELOW] here indicates an older version of chassis management module firmware.
See “Group 1 - AMM Firmware - All systems (except N3001-001)” on page 3-11.

Gig Switch - All systems (except N3001-001)

A [BELOW] here indicates an older version of chassis switch firmware.
Use “Group 2 - GigSwitch Firmware - N3001-002 and larger, N200x, and N1001.”

Note: For Netezza 100, see Replacement Procedures: IBM Netezza 100 Systems.
Note: On the N1001 and 100, there are two versions of BNT firmware supported for chas-
sis switches.
It is not possible to upgrade from the early version (5100) of BNT firmware to the lat-
est versions.
Field upgrades to the latest BNT firmware are supported only on the latest hardware. The
sys_rev_check utility identifies and passes both early and later versions of BNT firmware.

SAS Switch - N1001 and 100

A [BELOW] here indicates an older version of SAS switch firmware.
Note: There currently are no SAS firmware updates.

Rack Switch Management - N3001-002 and larger, N200x, and N1001

A [BELOW] here indicates an older version of management switch software
Use the update procedure described in “Group 2 - Rack Management Switch Firm-
ware - N3001-002+/N200x/N1001.”

Not applicable for Netezza 100 systems.

Note: On the N1001 there are two versions of BNT firmware supported for rack switches.
It is not possible to upgrade from the early version (1.1.1.5) of BNT firmware to the
latest versions.
Field upgrades to the latest BNT firmware is supported only on the latest hardware. The
sys_rev_check utility identifies and passes both early and later versions of BNT firmware.

Rack Switch Fabric - N3001-002 and larger, N200x, and N1001

A [BELOW] here indicates an older version of fabric switch software
Use the update procedure described in “Group 2 - Rack Fabric Switch Firmware -
N3001-002 +, N200x, and N1001.”

Not applicable for Netezza 100 systems.

Note: On the N1001 there are two versions of BNT firmware supported for rack switches.

3-6 00X7003 Rev.1.3

 Resolve sys_rev_check Issues

It is not possible to upgrade from the early version (1.1.1.5) of BNT firmware to the
latest versions.
Field upgrades to the latest BNT firmware is supported only on the latest hardware. The
sys_rev_check utility identifies and passes both early and later versions of BNT firmware.

Chassis Power Supply - All systems (except N3001-001)

A [FAIL] here indicates a hardware problem with a SPA chassis power supply.
Examine the log at /opt/nz/fdt/log/sys_rev_check_yyyymmdd-xxxxxx.log and contact Netezza
Support before taking any corrective action.

S-Blade - All systems (except N3001-001)

There are several S-Blade checks:
Note: When running sys_rev_check while logged in as user nz, results for Blade Hardware
Check, Blade Ethernet Check, and Blade HBA Check are not available.

SPU State
An issue here indicates that the remaining sections of sys_rev_check cannot be completed
without the system being online. Resolve any issues, bring the system online, and rerun
sys_rev_check to continue.

Firmware Check
A [BELOW] here indicates an older version of S-Blade firmware.
Use the procedure described in the “Group 1 - S-Blade and HBA Firmware - All systems
(except N3001-001)” on page 3-13 section of this document.

Hardware Check
A [FAIL] here indicates a hardware problem for an S-Blade; the S-Blade typically needs to
be replaced. Contact IBM Netezza Support for assistance with S-Blade hardware failures
and replacement.

Ethernet Check
A [BELOW] here indicates an older version of S-Blade Ethernet chip firmware.
Note: On N3001-002 and larger systems, if FDT Support Tools has been used to update
the Blade Ethernet firmware on the HS23 blades, the BLADE ETHERNET CHECK status is
[FAIL] if the firmware is loaded but the blades have not been rebooted, or [ABOVE] if the
blades have been rebooted and the firmware enabled. The [ABOVE] status is expected and
acceptable.

Use the procedure described in the “Group 1 - S-Blade and HBA Firmware - All systems
(except N3001-001)” section of this document.

HBA Check
A [BELOW] here indicates an older version of HBA firmware.
A [FAIL] here indicates that the HBA BIOS must be erased.

00X7003 Rev.1.3 3-7

IBM Netezza FDT User’s Guide

Storage Enclosure - N3001-002 and larger, N200x, and N1001

A [BELOW] here indicates an older version of ESM or RAID Controller firmware.
Use the procedure in the section “Group 3 - ESM Firmware - N3001-002 and larger,
N200x, and N1001.”
Note: For Netezza 100 systems, the process for updating the DSM firmware is described in
Chapter 6 of the System Configuration Guide: IBM Netezza 100 Systems.
Note: On occasion a false indication may occur with sys_rev_check indicating a Missing -
[FAIL] status.If this occurs, rerun sys_rev_check after waiting a few minutes, as the RAID
controller may require more time to respond.

Storage Media - All systems (except N3001-001)

A [BELOW] here indicates an older version of disk firmware.
An [ABOVE] here indicates disk firmware that is a later version than that expected by sys_
rev_check. Conditions listed as [ABOVE] do not necessarily require corrective action. Con-
sult with IBM Netezza Support before taking any action such as changing firmware
revisions.
If required, use the procedure described in the “Group 3 - Disk Firmware - All systems
(except N3001-001)” section of this document to update the firmware.

Prepare the System for Firmware Updates

This section describes how to "idle" the system so that you can safely update the firmware
of the components with the system offline.
 For Netezza 100 systems, which are single-host non-HA systems, stop the Netezza
software.
 For all other NPS systems, place the active host into Maintenance Mode.
The instructions that follow assume that Host 1 is the active host before and after stopping
heartbeat. If the active host in your system is Host 2 and you cannot migrate to Host 1,
keep in mind that instead of running commands on Host 1, you must run them on Host 2.

When you perform the steps in this section, the system will be unavailable to users until
after you upgrade the firmware and restore the system to normal operations.
Make sure that there are no hardware issues such as failed disks or S-Blades before you
begin. Use the nzhw -issues command to list any problems, and fix them before you
upgrade the firmware.

Transition an N3001/N200x/N1001 System to Maintenance Mode

This procedure uses the sample hostnames host1 to represent HA1 (usually the active host)
in the HA cluster, and host2 to represent the standby host. Since either host could serve as
the active host in a cluster, be sure to identify the current active and standby hosts in your
configuration and use those names for host1 and host2.
To transition the Netezza system into maintenance mode:

3-8 00X7003 Rev.1.3

 Prepare the System for Firmware Updates

1. Establish a new login session to the active host using its Host 1 IP address (not the
cluster IP address).
2. As user nz on the active host, stop the system:
[nz@host1 ~]S nzstop
Stopping High-Availability services:
[ OK ]

3. As root on Host 1, confirm that there are no /nz or /export/home connections using the
lsof command:
[root@host1 ~]# lsof /nz /export/home
If the command displays any open connections, the nz.heartbeat.sh command will not
be able to unmount the DRBD partitions. You must close the open connections using
the kill command.
4. As root on the standby host, stop Heartbeat:
[root@host2 ~]# service heartbeat stop
Stopping High-Availability services:
[ OK ]

5. As root on the active host, stop Heartbeat:

[root@host1 ~]# service heartbeat stop
Stopping High-Availability services:
[ OK ]
The command blocks until it completes successfully. It is important to wait and let the
command complete on both hosts. You can check /var/log/messages for status mes-
sages, or you can monitor progress in a separate terminal session using either of the
following commands:
[root@host1 ~]# tail -f /var/log/messages
[root@host1 ~]# crm_mon -i5

6. Run the following script in /nzlocal/scripts to make Host 1 ready for non-clustered
operations. The command prompts you for a confirmation to continue, shown as Enter
in the output.
[root@host1 ~]# /nzlocal/scripts/nz.non-heartbeat.sh
Example output:
---------------------------------------------------------------
Thu Jan 7 15:13:27 EST 2010

File systems and eth2 on this host are okay. Going on.
File systems and eth2 on other host are okay. Going on.
This script will configure Host 1 or 2 to own the shared disks and
own the fabric.

When complete, this script will have:

mounted /export/home and /nz
aliased 10.0.0.1 on eth2
run the rackenable script appropriate for this host
based on the last octet of eth2
being 2 for rack 1 or 3 for rack 2

To proceed, please hit enter. Otherwise, abort this.

00X7003 Rev.1.3 3-9

IBM Netezza FDT User’s Guide

Press Enter.
Okay, we are proceeding.
Thu Jan 7 15:13:29 EST 2010
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 16253924 935980 14478952 7% /
/dev/sda10 8123168 435272 7268604 6% /tmp
/dev/sda9 8123168 998808 6705068 13% /usr
/dev/sda8 8123168 211916 7491960 3% /var
/dev/sda7 8123168 500392 7203484 7% /opt
/dev/sda3 312925264 535788 296237324 1% /nzscratch
/dev/sda1 1019208 40192 926408 5% /boot
none 8704000 2228 8701772 1% /dev/shm
/dev/sda12 4061540 73940 3777956 2% /usr/local
/dev/drbd0 16387068 175972 15378660 2% /export/home
/dev/drbd1 309510044 5447740 288340020 2% /nz
Done mounting file systems
eth2:0 Link encap:Ethernet HWaddr 00:07:43:05:8E:26
inet addr:10.0.0.1 Bcast:10.0.15.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
Interrupt:122 Memory:c1fff000-c1ffffff

Done enabling IP alias

Running nz_dnsmasq: [ OK ]
nz_dnsmasq started.
Ready to use NPS in non-cluster environment
7. As root on Host 1, restart the NFS services using the following command:
[root@host1 ~]# service nfs restart

8. As the nz user on Host 1, confirm that the system is in the Stopped state as follows:
[nz@host1 ~]$ nzstate
System state is 'Stopped'.
Proceed to the steps in “Install the Firmware Updates” to perform any updates that are
required on your system.

Prepare a Netezza 100 System for Firmware Updates

If you are installing firmware updates on a Netezza 100 system, which is a single-host,
non-HA system, you stop the Netezza software using the nzstop command to prepare the
system for the upgrade.
1. Log into the Netezza 100 system as the nz user.
2. Stop the Netezza software:
[nz@host1 ~]$ nzstop
Proceed to the steps in “Install the Firmware Updates” to perform any updates that are
required on your system.

3-10 00X7003 Rev.1.3

 Install the Firmware Updates

Install the Firmware Updates

The following sections describe how to update the firmware on your system. This section
assumes that you have used the “Check the System Firmware Revisions” on page 3-1 pro-
cedure to confirm that a firmware update is required, and that the system is in
maintenance mode using the steps in “Prepare the System for Firmware Updates.”
If system power is interrupted during the FDT update process, the hardware may be left in
a state that prevents further FDT updates or normal operation. Do not power off or remove
any component of the Netezza appliance during the FDT update process unless instructed
to do so.

Note: When updating firmware remotely it is recommended to use a screen session. In the
event that a connection is lost, reconnecting is possible by re-initiation of the session.
To open a screen session:
[root@nzhost1 ~]# screen
To re-initiate a screen session:
[root@nzhost1 ~]# screen -r

Firmware updates are now arranged by groups, with the highest priority groups to be
updated first, followed by the lower priority groups, in order of their priority.
If necessary, firmware updates may be performed at separate times, as long as each group
is completed within the same service period, and the firmware updates are performed in
order of the group priority.
Table 3-1: Firmware Groups

Group Components

1 AMM primary, AMM secondary, and S-Blade/HBA

2 Chassis GigSwitches, Rack Management Switches, Rack Fab-

ric Switches, and PDUs

3 Disks and ESMs

4 Hosts

Group 1 - AMM Firmware - All systems (except N3001-001)

Follow the steps in this section to update the AMM firmware.

Update the AMM Firmware (N3001-002 and larger, N200x, and N1001)
Follow these steps to update the AMM firmware.
Note: The complete process takes about 60 minutes. This process updates the firmware
only on the primary AMM. The secondary AMM is updated by a background process. To
check on the progress of the second AMM, see “Check AMM Synchronization Status” on
page 3-14. The AMMs must be synchronized before updating the firmware on S-Blades.

As a best practice, the primary AMM in each SPA should be in slot 1.

00X7003 Rev.1.3 3-11

IBM Netezza FDT User’s Guide

1. Log into Host 1 of the Netezza system as the root user.

2. Change to the following directory:
[root@host1 ~]# cd /nzlocal/scripts/spa/
3. Run the following command to update the AMM firmware:
[root@host1 ~]# ./spaconfigure.sh -f only -components "mm[1]"
If you are prompted for a module user ID, specify USERID. The password is PASS-
W0RD (with a zero, not the letter O).
Sample output follows:
Please enter management module user ID
USERID
Please enter management module password
Please confirm management module password
Host Platform Configuration Version 4.13
2011-08-16.13623.dev-hpfConfig-4.cm.17322view
Mon Aug 22 11:50:25 EDT 2011: spaconfigure.sh -f only -components mm[1]
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
This may take from 1 to 50 minutes to run depending on options selected.
Caution! do not type <Ctrl-C> if you include firmware update.
All tasks run in background. You can monitor a subtask by
checking output in /tmp/spaconfigure/spaconfigure.<spaid>.log.
Waiting for 1 task ................................................
Waiting for 1 task ................................................
Waiting for 1 task ................................................
Waiting for 1 task ................................................
errCnt=0
Configure chassis SPA01, OK 2011-08-22 11:58:05.
SPA configuration Successful.
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
Verify that the SPA configuration was successful and the error count is 0 (in the line
errCnt=0). If necessary, view the spaconfigure log file in the directory /var/log/nz/spacon-
figure/ to troubleshoot errors, and re-run until spaconfigure is successful and no errors
occur.

4. On N3001/N200x systems, check that the chassis secondary gigswitches are reach-
able by the AMM:
[root@host1 ~]# /nzlocal/scripts/spa/spa_ping.sh
If a switch does not respond to the ping, reset the switch and the wait 5 minutes before
proceeding:
[root@host1 ~]# ssh mm00x 'reset -T switch[9]'
Where x is the SPA number.
If you have more firmware to update/upgrade, proceed to the next firmware update section.
Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Update the AMM Firmware (100)

Follow these steps to update the AMM firmware on IBM Netezza 100 systems.
Note: This process takes about 5 minutes to complete.

3-12 00X7003 Rev.1.3

 Install the Firmware Updates

1. Log into the host blade of the Netezza system as the root user.
2. Check the IP address configuration:
[root@host ~]# host -i ha1fabricright
Example output:
ha1fabricright has address 10.0.128.1
3. Change to the following directory:
[root@host ~]# cd /opt/nz/fdt/common/external/firmware/spa/mm
4. Log into the AMM using the following command:
[root@host ~]# ssh USERID@mm001
If you are prompted for a module user ID, specify USERID. The password is PASS-
W0RD (with a zero, not the letter O).
5. Run the following command to update the AMM firmware:
system> update -u tftp://xx.yy.128.1/opt/nz/fdt/common/external/
firmware/spa/mm/CNETCMUS.pkt -T system:mm[1]
Where xx.yy represent the first two octets obtained in step 2 (such as, 10.0).
Example output:
Starting flash packet preparation.
Update of Advanced Management Module firmware was successful.
The new firmware will become active after the next reset of the MM.
6. Run the following command:
system> reset -T mm[1]
7. Run the following command to close the session:
system> exit
8. Wait a few minutes and confirm that you can ping mm001:
[root@host ~]# ping mm001
PING mm001 (10.0.129.0) 56(84) bytes of data.
64 bytes from mm001 (10.0.129.0): icmp_seq=1 ttl=64 time=0.221 ms
64 bytes from mm001 (10.0.129.0): icmp_seq=2 ttl=64 time=0.219 ms
Press Cltr-C to exit the ping session.
If you have more firmware to update, proceed to the section pertaining to that firmware
update. Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Group 1 - S-Blade and HBA Firmware - All systems (except N3001-001)

If the sys_rev_check command reports a [BELOW] for:
 S-Blade revision check issue
 both an S-Blade and an HBA revision check issue
Use the firmware_updater Blade script.

00X7003 Rev.1.3 3-13

IBM Netezza FDT User’s Guide

Check AMM Synchronization Status

To perform a blade firmware update, the AMM firmware update, if performed, must be
complete. If the AMM revisions do not match, the blade update quits, but the AMM update
continues in the background to synchronize the AMMs. When the synchronization com-
pletes, you may update the blade firmware.
To determine the status of the synchronization:
1. Check the status of the primary AMM:
[root@host1 ~]# ssh mm0xx info -T mm[1]
where xx is the SPA number, and assuming the AMM in slot 1 is the primary AMM. If
the AMM in slot 2 is the primary AMM, change the command to:
[root@host1 ~]# ssh mm0xx info -T mm[2]
Example output for SPA02:
Name: mm002
UUID: 8E7D 8A59 55DA 11DE 93A6 001A 64DE 8476
Manufacturer: IBM (FOXC)
Manufacturer ID: 20301
Product ID: 65
Mach type/model: Advanced Management Module
Mach serial number: Not Available
Manuf date: 2409
Hardware rev: 4
Part no.: 39Y9659
FRU no.: 39Y9661
FRU serial no.: K1890 96B0ZE
CLEI: Not Available
AMM firmware
Build ID: BPET62S
File name: CNETCMUS.PKT
Rel date: 08/10/2012
Rev: 62
2. Check the status of the secondary AMM:
[root@host1 ~]# ssh mm0xx info -T mm[2]
where xx is the SPA number, and assuming the AMM in slot 2 is the secondary AMM. If
the AMM in slot 1 is the secondary AMM, change the command to:
[root@host1 ~]# ssh mm0xx info -T mm[1]
Example output:
Name: Standby MM
UUID: 9C0A DC23 2633 11E1 9C83 BC53 8971 A736
Manufacturer: IBM (WIST)
Manufacturer ID: 20301
Product ID: 65
Mach type/model: Advanced Management Module
Mach serial number: Not Available
Manuf date: 4911
Hardware rev: 20
Part no.: 68Y7058
FRU no.: 68Y7018
FRU serial no.: Y130UF1CB00B
CLEI: Not Available
AMM firmware
Build ID: BPET62O
File name: CNETCMUS.PKT

3-14 00X7003 Rev.1.3

 Install the Firmware Updates

Rel date: 03/10/2012

Rev: 62
Status: Update in progress (77% complete, 0:5 remaining)
Product Name: IBM Advance Management Module

The status is shown on the next to last line.

3. If the Status line shows Pending restart, issue the command to reset the AMM:
[root@host1 ~]# ssh mm0xx reset -standby -T mm[1]
where xx is the SPA number.
The reset of the AMM can take up to seven minutes.
4. When the Status line shows No update in progress, the secondary AMM has
completed the update. Rerun the firmware_updater that failed because of AMM
mismatch.

S-Blade update
Note: This process takes about 60 minutes to complete; however, it could take up to 2.5
hours if there are communication delays with the hardware.

Some notes about firmware_updater blade:

 The updater checks that blades are booted. If not, it waits until they are.
 The updater pre-tests NFS to avoid problems before the main update is started.
 The updater updates HBA and erases HBA BIOS.
 The updater assesses BMC health by attempting to communicate with it. If problems
are found, it can 1) restore ethernet-over-usb connectivity, and 2) issue a BMC reset
(but this is done only if needed). This is done both before and after update.
 The updater checks for an older version of firmware by comparing an AMM-based query
to a local blade-based query. If differences are found or there are communication
issues, all blades are automatically power-cycled at this stage, then re-queried.
 All of these tests have corresponding failure messages if they are not able to automati-
cally handle the situation. In most cases, --skip-bad-components continues operation
for all unaffected blades.
Note: If sys_rev_check is run immediately after running firmware_updater Blade, the out-
put of sys_rev_check indicates that the HBA was skipped. Wait 10 minutes after running
the updater before running sys_rev_check, so that the blade has time to fully boot.

1. Log into Host 1 as the root user.

2. Change to the directory that contains the firmware updater script:
[root@host1 ~]# cd /opt/nz/fdt

3. Run the updater script.

[root@host1 ~]# ./firmware_updater Blade
After target components are identified, you are prompted to continue the update.
A log file for the blade update is located at /opt/nz/fdt/log/blade.
Example output:
Now creating the lock file [DONE]

00X7003 Rev.1.3 3-15

IBM Netezza FDT User’s Guide

------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- B l a d e ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_20140128-154106.log
------------------------------SETUP-------------------------------
User will be prompted after prerequisites are checked.
Now checking that NPS is stopped [DONE]
Now checking for bootpsrv [DONE]
Now ensuring blades are booted [DONE]
Now preparing NFS for use [DONE]
Now testing NFS file transfer [DONE]
Now checking BMC health [DONE]
Now checking for stale revisions [DONE]
Now querying spus for info [DONE]
Now checking validity of spu detail [DONE]
Now gathering firmware details [DONE]
Now preparing for blade update [DONE]
------------------------TARGET COMPONENTS-------------------------
Blade BIOS will be updated on:
- SPA 3 : SLOTS 1, 3, 5, 7, 9, 11
- SPAS 1, 2, 4 : ALL SLOTS
Blade BMC will be updated on:
- SPA 3 : SLOTS 1, 3, 5, 7, 9, 11
- SPAS 1, 2, 4 : ALL SLOTS
Blade DIAG will be updated on:
- SPA 3 : SLOTS 1, 3, 5, 7, 9, 11
- SPAS 1, 2, 4 : ALL SLOTS
Blade HBA will be updated on:
- SPA 3 : SLOTS 1, 3, 5, 7, 9, 11
- SPAS 1, 2, 4 : ALL SLOTS
Press any key to continue or CTRL-C to cancel - 00:00 until auto-
resume.
-------------------------------UPDATE-----------------------------
Now copying firmware to NFS share [DONE]
Now evaluating completed BMC updates [PASS]
Now evaluating completed BIOS updates [PASS]
Now evaluating completed diag updates [PASS]
Now evaluating completed HBA updates [PASS]
Now completing firmware update [DONE]
Now checking BMC health [DONE]
Now rebooting blades [DONE]
Now waiting for blades to boot [DONE]
Now reloading AMM firmware info [DONE]
Now cleaning up [DONE]
Now removing the lock file [DONE]
------------------------------SUMMARY-----------------------------
Final Status [PASS]
Total Warnings 1
Main log file - /opt/nz/fdt/log/firmware_updater_20140128-
154106.log
------------------------------------------------------------------

The previous example shows a successful update. During operation, all blades are
updating asynchronously. Once every blade finishes any given subcomponent (for
example, BMC), it reports on that subcomponent for all targets, then moves on to wait-
ing for the next component. For example:

3-16 00X7003 Rev.1.3

 Install the Firmware Updates

-------------------------------UPDATE-----------------------------
Now copying firmware to NFS share [DONE]
Now evaluating completed BIOS updates [PASS]
Now updating firmware -- waiting on diag -- 00:37:07
The time-out is a worst-case value, and it counts down as the updates are running.
Any of the evaluating completed ______ lines can show [FAIL] if there are any
issues updating that subcomponent on any S-Blade.
After updates, S-Blades are automatically rebooted for changes to take effect. The
script waits for them long enough to query (about 6 minutes). At this point it instructs
the AMM to reload revision information. In the rare event that this step fails, an exam-
ple of the output:
Now reloading AMM firmware info [WARN]
These blades could not reload AMM firmware detail:
- SPA 3 : SLOTS 1, 3
Please manually reset AMMs to refresh stale firmware revs.
Now cleaning up [DONE]
If the reload fails, manually reset the AMM using system_diags Reset.
If failures are noted in updating Ethernet on some blades, rerun firmware_updater for those
blades.

Note: On N3001-002 and larger systems, if FDT Support Tools has been used to
update the Blade Ethernet firmware on the HS23 blades, the BLADE ETHERNET
CHECK status is [FAIL] if the firmware is loaded but the blades have not been
rebooted, or [ABOVE] if the blades have been rebooted and the firmware enabled. The
[ABOVE] status is expected and acceptable.

If the script is interrupted prior to completion, the lock file is not automatically removed.
Before running the script again, delete tool_running.lock in /opt/nz/fdt/var.

If during a blade firmware update you receive a message stating that the AMM firmware
revisions do not match and the update quits, use the procedure to “Check AMM Synchroni-
zation Status” on page 3-14.

If you have more firmware to update, proceed to the section pertaining to that firmware
update. Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Group 2 - GigSwitch Firmware - N3001-002 and larger, N200x, and N1001

Note: For Netezza 100, see Replacement Procedures: IBM Netezza 100 Systems.
Follow these steps to update the GigSwitch firmware on all GigSwitches in a Netezza
system.
N1001 systems require that the GigSwitch be re-seated after the firmware update, or that
the chassis be power-cycled, for the update to take effect.

Note: This process takes about 30 minutes per system to complete.

00X7003 Rev.1.3 3-17

IBM Netezza FDT User’s Guide

1. Log into Host 1 of the Netezza system as the root user.

2. Change to the following directory:
[root@host1 ~]# cd /nzlocal/scripts/spa/
3. Run the following command to update the switch firmware:
For the N1001:
[root@host1 ~]# ./spaconfigure.sh -n -f only -components “switch[1]
switch[2]”
For the N3001/N200x:
[root@host1 ~]# ./spaconfigure.sh -n -f only -components "switch[7]
switch[9]"
If you are prompted for a module user ID, specify USERID. The password is PASS-
W0RD (with a zero, not the letter O).
Sample output follows:
Please enter management module user ID
USERID
Please enter management module password
Please confirm management module password
Host Platform Configuration Version 4.8
2010-08-16.13623.dev-hpfConfig-xs2.cm.13623
Mon Aug 23 11:50:25 EDT 2010: spaconfigure.sh -f only -components switch
[x] switch[y]
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
This may take from 1 to 50 minutes to run depending on options selected.
Caution! do not type <Ctrl-C> if you include firmware update.
All tasks run in background. You can monitor a subtask by
checking output in /tmp/spaconfigure/spaconfigure.<spaid>.log.
Waiting for 1 task ................................................
Waiting for 1 task ................................................
Waiting for 1 task ................................................
Waiting for 1 task ................................................
errCnt=0
Configure chassis SPA01, OK 2010-08-23 11:58:05.
SPA configuration Successful.
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
4. Verify that the error count is 0 (in the line errCnt=0). If necessary, view the spaconfig-
ure log file in the directory /var/log/nz/spaconfigure/ to troubleshoot errors, and re-run
spaconfigure until no errors occur.
5. It the system being upgraded is an N1001, re-seat the gigswitches.
If you have more firmware to update, proceed to the section pertaining to that firmware
update. Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Group 2 - Rack Management Switch Firmware - N3001-002+/N200x/N1001

If the sys_rev_check command reports an issue in the rack management switch firmware,
follow these steps to update the firmware. If both of the rack switch firmware revision
checks passed, skip this section.

3-18 00X7003 Rev.1.3

 Install the Firmware Updates

Note: The firmware update takes about 5 minutes per switch to complete.

1. Log into Host 1 as the root user.

2. Change to the directory that contains the firmware updater script:
[root@host1 ~]# cd /opt/nz/fdt

3. Run the following command:

[root@host1 ~]# ./firmware_updater RackMgtSwitch
After target components are identified, you are prompted to continue the update.
Sample output follows:
Now creating the lock file ... [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- R a c k M g t S w i t c h ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
-------------------------------SETUP------------------------------
User will be prompted after prerequistes are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that local host is active (primary) [DONE]
Now checking that OS is stopped [DONE]
Now gathering firmware details [DONE]
Now checking that switches respond to ping [DONE]
Now preparing for switch firmware update [DONE]
-----------------------TARGET COMPONENTS--------------------------
These switches will be updated:
- ALL rack management switches in the system
----------------------------UPDATE--------------------------------
Now updating image1 firmware for switch netswmgt01 [DONE]
Now updating image2 firmware for switch netswmgt01 [DONE]
Now updating boot-image firmware for switch netswmgt01 [DONE]
Now rebooting switch netswmgt01 [DONE]
Now waiting for switch netswmgt01 to be ready [DONE]
Now checking switch firmware after update [DONE]
Now cleaning up [DONE]
Now removing the lock file [DONE]
------------------------------SUMMARY----------------------------
Final status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
------------------------------------------------------------------

If the script is interrupted prior to completion, the lock file is not automatically removed.
Before running the script again, delete tool_running.lock in /opt/nz/fdt/var.

Group 2 - Rack Fabric Switch Firmware - N3001-002 +, N200x, and N1001

If the sys_rev_check command reports an issue in the rack fabric switch firmware, follow
these steps to update the firmware. If both of the rack switch firmware revision checks
passed, skip this section.
Note: The firmware update takes about 10 minutes per switch to complete.

1. Log into Host 1 as the root user.

2. Change to the directory that contains the firmware updater script:
[root@host1 ~]# cd /opt/nz/fdt

00X7003 Rev.1.3 3-19

IBM Netezza FDT User’s Guide

3. Run the following command:

[root@host1 ~]# ./firmware_updater RackFabSwitch
After target components are identified, you are prompted to continue the update.
Sample output follows:
Now creating the lock file ... [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- R a c k F a b S w i t c h ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
-------------------------------SETUP------------------------------
User will be prompted after prerequistes are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that local host is active (primary) [DONE]
Now checking that OS is stopped [DONE]
Now gathering firmware details [DONE]
Now checking that switches respond to ping [DONE]
Now preparing for switch firmware update [DONE]
-----------------------TARGET COMPONENTS--------------------------
These switches will be updated:
- ALL rack fabric switches in the system
---------------------------UPDATE---------------------------------
Now updating image1 firmware for switch netswfab01a [DONE]
Now updating image2 firmware for switch netswfab01a [DONE]
Now updating boot-image firmware for switch netswfab01a [DONE]
Now rebooting switch netswfab0a1 [DONE]
Now updating image1 firmware for switch netswfab01b [DONE]
Now updating image2 firmware for switch netswfab01b [DONE]
Now updating boot-image firmware for switch netswfab01b [DONE]
Now rebooting switch netswfab01b [DONE]
Now waiting until switches are ready [DONE]
Now checking switch firmware after update [DONE]
Now cleaning up [DONE]
Now removing the lock file [DONE]
---------------------------SUMMARY--------------------------------
Final status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
------------------------------------------------------------------

If the script is interrupted prior to completion, the lock file is not automatically removed.
Before running the script again, delete tool_running.lock in /opt/nz/fdt/var.

Group 2 - PDU Firmware - N3001-002 and larger, N200x, and N1001

To update the firmware on the PDUs:
1. Log into the active host as the root user.
2. Type:
[root@host1 ~]# cd /nzlocal/scripts/rpc
[root@host1 ~]# ./rpcconfigure -f only -init no
3. When prompted for a password, type admin and press Enter.
When prompted a second time for a password, type admin and press Enter.

3-20 00X7003 Rev.1.3

 Install the Firmware Updates

Group 3 - Disk Firmware - All systems (except N3001-001)

If the sys_rev_check command reports a disk revision check:
 [BELOW], follow the steps in this section to update the disk firmware.
 [ABOVE], contact Netezza support
 [PASS], skip this section
1. Log into the Netezza system (Host 1) as the root user.
2. Change to the directory that contains the firmware updater script:
[root@host1 ~]# cd /opt/nz/fdt

3. Run the updater script:

[root@host1 ~]# ./firmware_updater StorageMedia
After target components are identified, you are prompted to continue the update.
Sample output follows:
Now creating the lock file ... [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- S t o r a g e M e d i a ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
-------------------------------SETUP------------------------------
User will be prompted after prerequistes are checked.
Now checking that local host is active (primary) [DONE]
Now checking for bootpsrv [DONE]
Now checking and preparing NFS [DONE]
Now checking NPS disk state [DONE]
Now power-cycling SPA 1 - (1 of 1) [DONE]
Now waiting for SPUs to be ready [DONE]
Now querying SPUs for disk details [DONE]
Now processing disk details [DONE]
Now gathering firmware details [DONE]
Now preparing for disk firmware update [DONE]
------------------------TARGET COMPONENTS-------------------------
These disks are below rev, and will be updated:
- SPA 1 : ENCL 1 : DISKS 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
- SPA 1 : ENCL 2 : DISKS 1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
------------------------------UPDATE------------------------------
Now updating disk firmware [DONE]
Now cleaning up [DONE]
Now removing the lock file [DONE]
-----------------------------SUMMARY------------------------------
Final status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
------------------------------------------------------------------
Now removing the lock file ... [DONE]
If you have more firmware to update, proceed to the section pertaining to that firmware
update. Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Group 3 - ESM Firmware - N3001-002 and larger, N200x, and N1001

If the sys_rev_check command reports an enclosure revision check issue, follow these steps
to update the ESM firmware. If the enclosure revision check passed, skip this section.
Note: This process takes about 40 minutes per system.

1. Log into either host as the root user.

00X7003 Rev.1.3 3-21

IBM Netezza FDT User’s Guide

2. Change to the directory that contains the firmware updater script:

[root@host1 ~]# cd /opt/nz/fdt
3. Run the updater script:
[root@host1 ~]# ./firmware_updater StorageEnclosure
After target components are identified, you are prompted to continue the update.
Sample output follows:
Now creating the lock file ... [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- S t o r a g e E n c l o s u r e ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_yyyymmdd-hhmmss.log
------------------------------SETUP-------------------------------
User will be prompted after prerequisites are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that local host is active (primary) [DONE]
Now checking that NPS is stopped [DONE]
Now checking for bootpsrv [DONE]
Now checking and preparing NFS [DONE]
Now power-cycling SPA 1 - (1 of 3) [DONE]
Now power-cycling SPA 2 - (2 of 3) [DONE]
Now power-cycling SPA 3 - (3 of 3) [DONE]
Now waiting for SPUs to be ready [DONE]
Now querying SPUs for enclosure details [DONE]
Now gathering firmware details [DONE]
Now preparing for enclosure firmware update [DONE]
---------------------------TARGET COMPONENTS----------------------
- ALL storage enclosures in the system
Press any key to continue or CTRL-C to cancel - 00:00 until auto-
resume.
---------------------------------UPDATE---------------------------
Now updating firmware on enclosure ESMs [DONE]
Now checking enclosure firmware after update [DONE]
Now cleaning up [DONE]
Now removing the lock file [DONE]
----------------------------------SUMMARY-------------------------
Final Status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_yyymmdd-hhmmss.log
Start time - Mon Nov 28 17:21:54 2011
End time - Mon Nov 28 17:41:46 2011
------------------------------------------------------------------
If the script is interrupted prior to completion, the lock file is not automatically removed.
Before running the script again, delete tool_running.lock in /opt/nz/fdt/var.

If you have more firmware to update, proceed to the section pertaining to that firmware
update. Otherwise, proceed to the steps in “Verify the System Revision Checks.”

Group 4 - Host Firmware - All systems

If the sys_rev_check command reports an issue in the Host firmware, follow these steps to
update the firmware. If both of the host firmware revision checks passed, skip this section.
A [WARN] status in the host log file indicates a version of firmware that is below the
required level, and must be updated using FDT Support Tools, not the firmware_updater
utility. Examine the host log file for details on the firmware component that requires
updating.

3-22 00X7003 Rev.1.3

 Install the Firmware Updates

An [INFO] status in the host log file from sys_rev_check indicates that is not able to assess
the current firmware revision of the indicated component and/or that the firmware of that
component cannot be updated by FDT.
 In the cases of PSoC and TMM firmware, updates are made using FDT Support Tools.
 In most other cases, utilities available though Fix Central or external or third party
update utilities are required to update these components, which include host disk
drives, Intel 1Gb NICs (reported by sys_rev_check as ETH_1GB_FW_2), Chelsio 10Gb
NICs, some Broadcom 1Gb NICs (reported by sys_rev_check as ETH_1GB_FW_1) for
some hosts (x3650-M1/M2/M3 and x3850-M2).
Note: The Host firmware update takes approximately 60 minutes to complete, depending
on how many firmware components require updates. The host servers are by default
updated in parallel.

When connecting remotely to hosts being updated, if updating or using IMM2 on the host,
the remote client must have IBM Java version 7 or later installed.

Key features of the host updates:

 Multiple runs may be necessary. Preliminary updates may be necessary for drivers or
minimum initial revisions (for example, RAID firmware requires multiple runs).
 HBA (Emulex fiber channel) update capability (not enabled by default). User must spe-
cifically request it using one of the HBA sub-commands. See Table 4-3 on page 4-6.
 No automatic reboots. A message informs the user to perform a manual reboot after the
update is complete (if necessary).
This updater supports 10 hosts:
 HS22
 x3650-M1
 x3650-M2
 x3650-M3
 x3650-M4
 x3750-M4
 x3750-M4-HD
 x3750-M4v2
 x3850-M2
 x3850-X5
There are host sub-components that cannot be updated:
 Any Intel Ethernet cards (reported by sys_rev_check as ETH_1GB_FW_2)
 Chelsio 10GB Ethernet cards
 x3650-M1 disk drives
Note: It is possible that a customer may be using an Emulex NIC as the system interface. If
that is the case, the network connection to the system may be lost during the update. It is
recommended to use a screen session in this case (see page 3-11).

To update the system hosts:

00X7003 Rev.1.3 3-23

IBM Netezza FDT User’s Guide

This procedure requires manual host reboot(s).

Customers participating in the Red Hat Enterprise Linux (RHEL) Yum Security Patching
Program for IBM PureData System for Analytics S100/N1000/N1001/N2001/N2001 need
to be aware that if the system being upgraded to FDT 4.3 has RHEL 5.11 or later, or RHEL
6.6 or later installed, unless supported kernels are installed, the command firmware_
updater Host --skip-driver-update must be used when updating host firmware. If a host
firmware update is attempted on a system with RHEL 5.11 or later, or 6.6 or later, that do
not have the specified kernels, if the '--skip-driver-update' option is not used, the update
fails. (This command option is not listed in the online help for FDT.)
Supported kernels:
- RHEL5.11: drbd-km-2.6.18_398.el5-8.4.4nz3a-4.x86_64.rpm
- RHEL6.6: drbd-km-2.6.32_504.el6.x86_64-8.4.4nz3a-4.el6.x86_64.rpm
- RHEL6.7: drbd-km-2.6.32_573.1.1.el6.x86_64-8.4.4nz3a-4.el6.x86_64.rpm

1. Log into HA1 as the root user.

2. Disable automatic startup of heartbeat services during system boot:
[root@host1 ~]# ssh ha2 "chkconfig heartbeat off"
[root@host1 ~]# chkconfig heartbeat off
3. Change to the directory that contains the firmware updater script:
[root@host1 ~]# cd /opt/nz/fdt

4. For Host firmware updates on systems in the Yum Security Patching Program with
RHEL 5.11 or later, or RHEL 6.7 or later installed, run the following command:
[root@host1 ~]# ./firmware_updater Host --skip-driver-update
For all other systems, run the following command:
[root@host1 ~]# ./firmware_updater Host
You are prompted to specify the BMC/IMM user ID and password:
Now creating the lock file [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- H o s t ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_20131204-091546.log
------------------------------------------------------------------
Specify BMC / IMM user id [enter for default] :
Specify BMC / IMM password [enter for default] :
Note: If the BMC/IMM user ID and password has been changed from the default,
type the user ID (and press Enter) and then type the password (and press Enter).

The script examines the first configurable user ID, and if it is not at the default value,
the script requires the correct user ID and password to continue. If the correct user
ID and password is not specified, the program exits and must be run again.
Otherwise, if the values are default, press Enter at each prompt to continue the
update.
After target components are identified, you are prompted to continue.

3-24 00X7003 Rev.1.3

 Install the Firmware Updates

5. At this point, if the Emulex driver requires updating, firmware_updater updates only
the Emulex driver. If the driver update is not indicated or required, skip to step 6 on
page 3-27.
Sample output for systems requiring Emulex driver updates follows:
------------------------------SETUP-------------------------------
User will be prompted after prerequisites are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that NPS is stopped [DONE]
Now preparing and testing file transfer [DONE]
Now testing BMC user [DONE]
Now testing BMC password [DONE]
Now querying nodes for info [DONE]
Now checking validity of host detail [DONE]
Now gathering firmware details [DONE]
Now preparing for host update [DONE]
------------------------TARGET COMPONENTS-------------------------
Host ETHERNET will be updated on:
- ALL hosts in the system
Emulex ethernet drivers need to be updated before firmware can be
updated.
This script will update Emulex ethernet drvers now.
After update, hosts MUST be rebooted. Then, please run this script
again.
Press any key to continue or CTRL-C to cancel - 00:00 until auto-
resume.
-----------------------------UPDATE-------------------------------
Now copying content to target hosts [DONE]
Now evaluating completed ETHERNET updates [PASS]
Now completing updates [DONE]
These hosts received updates that will not take effect until after
a reboot:
- ALL hosts in the system

They may show some revisions as below until this reboot is done.
Please manually reboot these hosts.

Now cleaning up [DONE]

Now removing the lock file [DONE]
-----------------------------SUMMARY------------------------------
Final Status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_20131204-
091546.log
------------------------------------------------------------------

Note that the output states that the hosts must be manually rebooted after the update.

Multiple preliminary update messages may display at the same time. For example, if an
Emulex driver update and RAID double-update are both needed, they are updated in
the first run.
Example output if a RAID double-update is needed (requiring a second manual reboot):
------------------------TARGET COMPONENTS-------------------------
Host RAID will be updated on:
- ALL hosts in the system

RAID firmware on these hosts does not meet minimum rev

requirements, and must be double-updated. This script will perform
the initial update now.

After update, hosts MUST be rebooted. Then, please run this script

00X7003 Rev.1.3 3-25

IBM Netezza FDT User’s Guide

again.

Press any key to continue or CTRL-C to cancel - 00:00 until auto-

resume.
------------------------------UPDATE------------------------------

Note that the output states that the hosts must be manually rebooted after the update and
then the update must be run again.

Note: If sys_rev_check is run prior to rebooting the host, a [PEND] status indicates a
new firmware version for the component has been loaded onto the system, but is not
active yet, pending a system reboot.

a. If the output from firmware_updater shows that a manual reboot is required, reboot
both hosts using the command:
[root@host ~]# ssh ha2 "shutdown -r now"; shutdown -r now
b. After the reboot, run the command:
[root@host1 ~]# /nzlocal/scripts/nz.non-heartbeat.sh
c. If instructed to run the script again, wait 15 minutes and then type:
[root@host1 ~]# ./firmware_updater Host
If you do not wait 15 minutes, the following output displays:
Now creating the lock file [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- H o s t ***
FDT 4.3 - /opt/nz/fdt/log/firmware_updater_20140210-143704.log
------------------------------------------------------------------
Specify BMC / IMM user id [enter for default] :
Specify BMC / IMM password [enter for default] :
------------------------------SETUP-------------------------------
User will be prompted after prerequisites are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that NPS is stopped [DONE]
Now preparing and testing file transfer [DONE]
Now testing BMC user [DONE]
Now testing BMC password [DONE]
Now querying nodes for info [DONE]
Now checking validity of host detail [FAIL]

Problems found for the following hosts. Will not continue.

- RACK 1 : HOST 1

Now cleaning up [DONE]

Now removing the lock file [DONE]
-----------------------------SUMMARY------------------------------
Final Status [FAIL]
Total Failures 1
Main log file - /opt/nz/fdt/log/firmware_updater_20140210-
143704.log
Start time - Mon Feb 10 14:37:04 2014
End time - Mon Feb 10 14:37:13 2014
------------------------------------------------------------------

3-26 00X7003 Rev.1.3

 Install the Firmware Updates

6. If no Emulex driver updates are required (or have been updated in a previous run),
firmware_updater updates host firmware.
Example output of an update not requiring Emulex driver update:
Now creating the lock file [DONE]
------------------------------------------------------------------
*** F I R M W A R E U P D A T E R -- H o s t ***
FDT 4.3 - /opt/nz/fdt/fdt/log/firmware_updater_20140131-172019.log
------------------------------------------------------------------
Specify BMC / IMM user id [enter for default] :
Specify BMC / IMM password [enter for default] :
------------------------------SETUP-------------------------------
User will be prompted after prerequisites are checked.
Now checking that cluster manager is stopped [DONE]
Now checking that NPS is stopped [DONE]
Now preparing and testing file transfer [DONE]
Now testing BMC user [DONE]
Now testing BMC password [DONE]
Now querying nodes for info [DONE]
Now checking validity of host detail [DONE]
Now gathering firmware details [DONE]
Now preparing for host update [DONE]
------------------------TARGET COMPONENTS-------------------------
Host BIOS will be updated on:
- ALL hosts in the system
Host BMC will be updated on:
- ALL hosts in the system
Host DIAG will be updated on:
- ALL hosts in the system
Host DISKS will be updated on:
- ALL hosts in the system
Host ETHERNET will be updated on:
- ALL hosts in the system
Host RAID will be updated on:
- ALL hosts in the system
------------------------------UPDATE------------------------------
Now copying content to target hosts [DONE]
Now evaluating completed BMC updates [PASS]
Now evaluating completed BIOS updates [PASS]
Now evaluating completed DIAG updates [PASS]
Now evaluating completed ETHERNET updates [PASS]
Now evaluating completed RAID updates [PASS]
Now evaluating completed DISKS updates [PASS]
Now completing updates [DONE]

These hosts received updates that will not take effect until after
a reboot:
- ALL hosts in the system

They may show some revisions as below until this reboot is done.
Please manually reboot these hosts.

Now cleaning up [DONE]

Now removing the lock file [DONE]
-----------------------------SUMMARY------------------------------
Final Status [PASS]
Main log file - /opt/nz/fdt/log/firmware_updater_20140131-

00X7003 Rev.1.3 3-27

IBM Netezza FDT User’s Guide

172019.log
------------------------------------------------------------------

If the output indicates that an RSA daemon is not installed, the daemon must be manually
installed. The package containing the daemon is ibm_svc_rsa2_hlp253a_linux_32-64.tgz
available from Fix Central (search on RSA II Linux Daemon). Copy the package into a tem-
porary directory, run tar -xzvf ibm_svc_rsa2_hlp253a_linux_32-64.tgz, and then run
./install.sh. Then run chkconfig ibmasm on and service ibmasm start. This needs to be per-
formed on both hosts. Run firmware_updater again to complete the firmware update.

Note that the output states that the hosts must be manually rebooted after the update.

7. If the output from firmware_updater indicates that a manual reboot is required, reboot
both hosts using the command:
[root@host ~]# ssh ha2 "shutdown -r now"; shutdown -r now

8. After the reboot, run the command:

[root@host1 ~]# /nzlocal/scripts/nz.non-heartbeat.sh
9. Re-enable automatic startup of heartbeat services during system boot:
[root@host1 ~]# chkconfig heartbeat on
[root@host1 ~]# chkconfig heartbeat --list
If the update script is interrupted prior to completion, the lock file is not automatically
removed. Before running the script again, delete tool_running.lock in /opt/nz/fdt/var.

Power Cycle the SPAs and Enclosures

After you have updated the system with the latest firmware revisions, power-cycle the SPAs
and disk enclosures. This process takes a six or seven minutes to complete for each SPA
and enclosure in the system.
To power cycle the SPAs and enclosures:
1. Log into the Netezza active host as the root user.
2. Change to the following directory:
[root@host1 ~]# cd /nzlocal/scripts/rpc
3. Run the spapwr.sh script to turn off the power as follows:
[root@host1 ~]# ./spapwr.sh -off all
4. Run the spapwr.sh script to turn on the power as follows:
[root@host1 ~]# ./spapwr.sh -on all
5. Proceed to the next section, “Verify the System Revision Checks.”

3-28 00X7003 Rev.1.3

 Verify the System Revision Checks

Verify the System Revision Checks

As a best practice, run the sys_rev_check command again to verify that you have success-
fully updated the firmware.
1. Log into the active Netezza host as user root.
2. Log in as the nz user to start the Netezza software:
[root@host1 ~]# su - nz
[nz@host1 ~]$ nzstart
Wait for a few minutes while the Netezza system transitions to the online state. You can
use the nzstate command to monitor the states until the command returns 'Online' and
then proceed to the next step.
3. Log out of nz and return to the root account.
4. Change directory:
[root@host1 ~]# cd /opt/nz/fdt
5. Run the sys_rev_check command. A sample command and its output follows:
[root@host1 ~]# ./sys_rev_check
----------------------------------------------------------------------
***** S Y S R E V C H E C K *****
FDT 4.3 - /opt/nz/fdt/log/sys_rev_check_yyyymmdd-hhmmss.log
--------------------------CHECKING SPU STATE--------------------------
Checking if the system is online
[DONE]
------------------------------HOST CHECK------------------------------
ha1 [PASS]
ha2 [PASS]

------------------------------RPC CHECK-------------------------------
rpc1ur [PASS]
rpc1lr [PASS]
rpc1ul [PASS]
rpc1ll [PASS]
------------------------------MM CHECK--------------------------------
mm001 [PASS]
mm001alt [PASS]
mm002 [PASS]
mm002alt [PASS]
-------------------------SPA GIG SWITCH CHECK-------------------------
gigsw01a [PASS]
gigsw01b [PASS]
gigsw02a [PASS]
gigsw02b [PASS]
-------------------------SPA SAS SWITCH CHECK-------------------------
sassw01a [PASS]
sassw01b [PASS]
sassw02a [PASS]
sassw02b [PASS]
------------------------RACK SWITCH MGT CHECK-------------------------
netswmgt01 [PASS]
------------------------RACK SWITCH FAB CHECK-------------------------
------------------------SPA POWER SUPPLY CHECK------------------------
SPA 01 [PASS]
SPA 02 [PASS]
-------------------------BLADE FIRMWARE CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]

00X7003 Rev.1.3 3-29

IBM Netezza FDT User’s Guide

spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-------------------------BLADE HARDWARE CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-------------------------BLADE ETHERNET CHECK-------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
------------------------------HBA CHECK-------------------------------
spu0101 [PASS]
spu0103 [PASS]
spu0105 [PASS]
spu0107 [PASS]
spu0109 [PASS]
spu0111 [PASS]
spu0201 [PASS]
spu0203 [PASS]
spu0205 [PASS]
spu0207 [PASS]
spu0209 [PASS]
spu0211 [PASS]
-----------------------STORAGE ENCLOSURE CHECK------------------------
SPA 01 Enclosure 1 [PASS]
SPA 01 Enclosure 2 [PASS]
SPA 01 Enclosure 3 [PASS]
SPA 01 Enclosure 4 [PASS]
SPA 02 Enclosure 1 [PASS]
SPA 02 Enclosure 2 [PASS]
SPA 02 Enclosure 3 [PASS]
SPA 02 Enclosure 4 [PASS]
--------------------------STORAGE MEDIA CHECK-------------------------
SPA 01 Enclosure 1 [PASS]
SPA 01 Enclosure 2 [PASS]
SPA 01 Enclosure 3 [PASS]
SPA 01 Enclosure 4 [PASS]
SPA 02 Enclosure 1 [PASS]
SPA 02 Enclosure 2 [PASS]
SPA 02 Enclosure 3 [PASS]
SPA 02 Enclosure 4 [PASS]
-------------------------------SUMMARY-------------------------------
Final status [PASS]
Total Failures 0
Total Revs Below 0

3-30 00X7003 Rev.1.3

 Restore the System to Normal Operations

Total Rev Above 0

Main log file - /opt/nz/fdt/log/sys_rev_check_yyyymmdd-hhmmss.log
----------------------------------------------------------------------
If the final status of the sys_rev_check script is [BELOW] or [FAIL], review the results file
and investigate the issue. Refer to the “Resolve sys_rev_check Issues”for more information
about the issues and possible resolutions. If the problems relate to firmware that is below
the minimum revision, stop the NPS software and return to the firmware update procedures
in this guide to perform (or repeat) the necessary updates. If you encounter other issues or
failures, contact IBM Netezza Support for assistance with troubleshooting the problems.

Note: On N3001-002 and larger systems, if FDT Support Tools has been used to update
the Blade Ethernet firmware on the HS23 blades, the BLADE ETHERNET CHECK status is
[FAIL] if the firmware is loaded but the blades have not been rebooted, or [ABOVE] if the
blades have been rebooted and the firmware enabled. The [ABOVE] status is expected and
acceptable.

If the sys_rev_check script passes, proceed to the next section, “Restore the System to
Normal Operations.”

Restore the System to Normal Operations

After you complete the firmware upgrades needed for your system, follow the steps in these
sections to restore your system to normal operations and make it available to users.

Restore an N3001/N200x/N1001 System to Clustering Operations

After you update the firmware, restore the cluster operations by following these steps:
1. As the nz user on Host 1, make sure that the Netezza software is stopped using the
nzstop command:
[nz@host1 ~]$ nzstop
NPS system is not running.
If NPS is running, this command stops it.
2. Log out as user nz and then log in as user root.
3. Make sure that Heartbeat is not running on either host. Use the service heartbeat stop
command first on host 2 and then on host 1 to stop Heartbeat if it is running.
4. As root on host 1, restart the NFS service:
[root@host1 ~]# service nfs restart
5. As root on host 1, confirm that there are no /nz or /export/home connections using the
lsof command:
[root@host1 ~]# lsof /nz /export/home
If the command displays any open connections, the nz.heartbeat.sh command will not
be able to unmount the DRBD partitions. You must close the open connections using
the kill command.
6. On host 1, run the following script in /nzlocal/scripts to make the Netezza system ready
for clustered operations. The command prompts you for a confirmation to continue,
shown as Enter in the output.

00X7003 Rev.1.3 3-31

IBM Netezza FDT User’s Guide

[root@host1 scripts]# /nzlocal/scripts/nz.heartbeat.sh

---------------------------------------------------------------
Thu Jan 7 15:14:32 EST 2010

This script will configure Host 1 or 2 to run in a cluster

When complete, this script will have:

unmounted /export/home and /nz
Disabling IP alias 10.0.0.1 from eth2

To proceed, please hit enter. Otherwise, abort this.

Press Enter.
Okay, we are proceeding.
Thu Jan 7 15:14:33 EST 2010
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 16253924 935980 14478952 7% /
/dev/sda10 8123168 435272 7268604 6% /tmp
/dev/sda9 8123168 998808 6705068 13% /usr
/dev/sda8 8123168 211928 7491948 3% /var
/dev/sda7 8123168 500544 7203332 7% /opt
/dev/sda3 312925264 535788 296237324 1% /nzscratch
/dev/sda1 1019208 40192 926408 5% /boot
none 8704000 2228 8701772 1% /dev/shm
/dev/sda12 4061540 73940 3777956 2% /usr/local
Done unmounting file systems
eth2:0 Link encap:Ethernet HWaddr 00:07:43:05:8E:26
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
Interrupt:122 Memory:c1fff000-c1ffffff

Done disabling IP alias

Shutting down dnsmasq: [ OK ]
nz_dnsmasq stopped.
Ready to use NPS in a cluster environment

7. As root on the active host, start Heartbeat:

[root@host1 ~]# service heartbeat start
Starting High-Availability services [ OK ]
8. As root on the standby host, start Heartbeat:
[root@host2 ~]# service heartbeat start
Starting High-Availability services [ OK ]
Note: It can take a few minutes for Heartbeat to start. You can watch the nps resource
group start and bring its services online using the crm_mon command:

Sample output follows. This command refreshes its display every five seconds. (Press
Control-C to exit the command after you confirm that the resource group elements have
started.)
[root@host1 ~]# crm_mon -i5
============
Last updated: Wed Sep 30 13:42:39 2009
2 Nodes configured.
3 Resources configured.
============
Node: host1 (key): online
Node: host2 (key): online
Resource Group: nps

3-32 00X7003 Rev.1.3

 Restore the System to Normal Operations

drbd_exphome_device (heartbeat:drbddisk): Started host1

drbd_nz_device (heartbeat:drbddisk): Started host1
exphome_filesystem (heartbeat::ocf:Filesystem): Started host1
nz_filesystem (heartbeat::ocf:Filesystem): Started host1
fabric_ip (heartbeat::ocf:IPaddr): Started host1
wall_ip (heartbeat::ocf:IPaddr): Started host1
nz_dnsmasq (lsb:nz_dnsmasq): Started host1
nzinit (lsb:nzinit): Started host1
fencing_route_to_ha1 (stonith:apcmaster): Started host2
fencing_route_to_ha2 (stonith:apcmaster): Started host1

When all of the services have started, the system has returned to normal Heartbeat and
DRBD status. The system automatically transitions to a start-up process, and enters
the Discovering state. Typically the system remains in the Discovering state for several
minutes as it examines and updates its topology, then it transitions to the Online state.
9. Confirm that the system is in the Online state as follows. As user nz, type the
command:
[nz@host1 ~]$ nzstate
System state is 'Online'.

Restore an IBM Netezza 100 System to Normal Operations

After you update the firmware, restore the cluster operations by following these steps:
1. Log into the Netezza 100 system as the nz user.
2. Start the Netezza software:
[nz@host ~]$ nzstart
The command may require a few minutes to complete and return the command
prompt.
3. Confirm that the system is in the Online state as follows:
[nz@host ~]$ nzstate
System state is 'Online'

00X7003 Rev.1.3 3-33

IBM Netezza FDT User’s Guide

3-34 00X7003 Rev.1.3

 CHAPTER 4
FDT Command Reference
What’s in this chapter
 firmware_updater
 firmware_updater Blade
 firmware_updater Host
 firmware_updater RackFabSwitch
 firmware_updater RackMgtSwitch
 firmware_updater StorageEnclosure
 firmware_updater StorageMedia
 storage_diags
 system_diags
 sys_rev_check
 getservicedata.pl

This chapter lists the options and capabilities of the firmware_updater component
commands.

4-1
IBM Netezza FDT User’s Guide

firmware_updater
Use this command to update firmware on a system component.
Run from the Netezza active host as the root user.

Syntax
The command has the following syntax:
firmware_updater [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater command requires one of the following options.
Table 4-1: firmware_updater Options

Input Description

COMPONENT [COMPONENT_OPTIONS] Execute a firmware update on the specified

COMPONENT

--list-components Lists supported COMPONENTS

--list-firmware Lists installed firmware bundles

--install-firmware <path> Installs component Hot Fix package

--remove-firmware <bundle_name> Removes a previously installed Hot Fix

package

--show-firmware-detail [options] Validate and show details about a firmware

bundle.
Options:
bundle_path - details of a bundle prior to
being installed.
bundle_name - details of an installed firm-
ware bundle.

-h --help Show help

-v[v] (Internal Netezza only) Verbose Mode

Description
firmware_updater is the base command used to update firmware on system components.

4-2 00X7003 Rev.1.3

 firmware_updater

Usage
The following provides some sample usage:
./firmware_updater Blade
Updates the firmware on all S-Blades in the system.

./firmware_updater -h
Shows help for the firmware_updater command.

./firmware_updater --remove-firmware storagemedia_st1000nm0001_

firmware_20130101_111413.tar.gz
Removes the installed Hot Fix bundle for disk drive firmware.

00X7003 Rev.1.3 4-3

IBM Netezza FDT User’s Guide

firmware_updater Blade
Use this command to update firmware on an S-Blade.
Run from the active host as the root user.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000, 100

Syntax
The command has the following syntax:
firmware_updater Blade [subcomponents] [targets] [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater Blade command has the following options.
Table 4-2: firmware_updater Blade Options

Input Description
Subcomponents (can be negated, such as --no-update-fpga)
--update-bmc Update BMC or IMM *
--update-bios Update BIOS or uEFI *
--update-diag Update diag or DSA *
--update-ethernet Update Ethernet adapters
--update-fpga Update on-board (non Netezza) FPGA (if
applicable)
--update-hba Update HBAs and erase their BIOS
Targets
--spa [‘n, n, n, n’][‘*’] Execute a firmware update on a specific SPA, or
NOTE: Asterisk (*) must be in quotes. SPAs
--slot n Execute a firmware update on specified slot in
SPA(s)
--alias ‘name’ [‘name, name, name’] Execute a firmware update on a specific SPU or
SPUs
* When using the --update-bmc, --update-bios, and/or --update-diag options, they must
be executed in sequence with bmc first, then bios, and diag last.

4-4 00X7003 Rev.1.3

 firmware_updater Blade

Table 4-2: firmware_updater Blade Options (continued)

Input Description
Options
--firmware BUNDLE Specify an alternative blade firmware bundle to
use
--skip-bad-components If some components cannot be processed, skip
them and continue
--skip-prompt Skips “press any key to continue” prompt
--skip-umask-check Skips umask settings check
--force Forces the firmware to be applied
(applies to all components except HBA)
--help | -h Show help
Advanced Options (not recommended)
--ignore-nps-state Ignores NPS state requirement
--hba-bios-only Erase HBA BIOS but do not change firmware
--hba-firmware-only Target HBA firmware but do not erase BIOS
--skip-mm-reload Skip AMM reload. User must manually reset
AMMs, or sys_rev_check does not show updates

Description
firmware_updater Blade is the command used to update firmware on an S-Blade.

Usage
The following provides some sample usage:
./firmware_updater Blade
Updates the firmware on all S-Blades in the system.

./firmware_updater Blade --spa '1, 3'

Updates the firmware on all S-Blades in SPA 1 and SPA 3.

./firmware_updater Blade --update-bios --update-bmc --spa '*' --slot 13

Target BIOS and BMC on the S-Blades in slot 13 of all SPAs.

./firmware_updater Blade --alias 'spu0209, spu0211'

Updates the firmware on the S-Blades in SPA2, slots 9 and 11.

./firmware_updater Blade --no-update-ethernet

Updates the firmware except Ethernet on all S-Blades.

00X7003 Rev.1.3 4-5

IBM Netezza FDT User’s Guide

firmware_updater Host
Use this command to update the firmware on a host server.
Run from the active host as the root user.

Applicable Systems
All

Syntax
The command has the following syntax:
firmware_updater Host [subcomponents] [targets] [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater Host command has the following command options.
Note: The recommended mode for this command is with no options.
Table 4-3: firmware_updater Host Command Options

Input Description

Subcomponents (can be negated, such as --no-update-bios)

--update-bmc Updates BMC or IMM *

--update-bios Updates BIOS or uEFI *

--update-diag Updates diag or DSA *

--update-disks Updates local disk drives

--update-ethernet Updates Ethernet adapters

--update-fpga Updates host FPGA (if applicable)

--update-raid Updates onboard RAID controller

Optional Subcomponents

--also-update-hba Update host HBAs in addition to other targets

--only-update-hba Update host HBAs and nothing else

* When using the --update-bmc, --update-bios, and/or --update-diag options, they must
be executed in sequence with bmc first, then bios, and diag last.

4-6 00X7003 Rev.1.3

 firmware_updater Host

Table 4-3: firmware_updater Host Command Options (continued)

Input Description

Targets

--alias name [ha1, ha2] Execute a firmware update on a specific node

Options

--firmware BUNDLE Specify an alternative host firmware bundle to use

--skip-prompt Skips “press any key to continue” prompt

--ignore-nps-state Ignores NPS state requirements (NPS systems)

--skip-bad-components If some components cannot be processed, skip

them and continue

--skip-bmc-login-test Skip BMC/IMM login test

--skip-umask-check skip umask settings check

--skip-driver-update skip updating Emulex Ethernet and/or HBA driver

--force Update regardless of current version

(applies to all components except RAID)

--help | -h Show help

Description
firmware_updater Host is the command used to update the firmware on host servers.
Note: The recommended mode for this command is with no options.

Usage
The following provides some sample usage:
./firmware_updater Host
Updates the firmware on both hosts in the system.

./firmware_updater Host --alias 'ha1'

Updates the firmware only on host 1.

./firmware_updater Host --no-update-disks

Updates everything EXCEPT disks.

./firmware_updater Host --also-update-hba

Updates host HBAs in addition to other targets.

00X7003 Rev.1.3 4-7

IBM Netezza FDT User’s Guide

firmware_updater RackFabSwitch
Use this command to update the firmware on a rack fabric switch.
Run from the active host as the root user.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000

Syntax
The command has the following syntax:
firmware_updater RackFabSwitch [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater RackFabSwitch command has the following options.
Table 4-4: firmware_updater RackFabSwitch Options

Option Description

--alias name [, name, name, name] Execute a firmware update on a specific switch or
switches

--firmware BUNDLE Specify an alternative rack fabric switch firmware

bundle to use

--skip-prompt Skips “press any key to continue” prompt

--skip-rev-check Skips automated sys_rev_check steps to save

time

--skip-bad-components If some components cannot be processed, skip

them and continue

--skip-umask-check Skips umask settings check

--force Update regardless of current version

(may not be possible in all cases)

--help | -h Show help

Description
firmware_updater RackFabSwtch is the command used to update the firmware on a rack
fabric switch.

4-8 00X7003 Rev.1.3

 firmware_updater RackFabSwitch

Usage
The following provides some sample usage:
./firmware_updater RackFabSwitch
Updates the firmware on all rack fabric switches in the system.

./firmware_updater RackFabSwitch --alias 'netswfab02a'

Updates the firmware only on rack fabric switch netswfab02, controller a.

00X7003 Rev.1.3 4-9

IBM Netezza FDT User’s Guide

firmware_updater RackMgtSwitch
Use this command to update the firmware on a rack management switch.
Run from the active host as the root user.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000

Syntax
The command has the following syntax:
firmware_updater RackMgtSwitch [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater RackMgtSwitch command has the following options.
Table 4-5: firmware_updater RackMgtSwitch Options

Option Description

--alias name [, name, name, name] Execute a firmware update on a specific switch or
switches

--firmware BUNDLE Specify an alternative rack fabric switch firmware

bundle to use

--skip-prompt Skips “press any key to continue” prompt

--skip-rev-check Skips automated sys_rev_check steps to save

time

--skip-bad-components If some components cannot be processed, skip

them and continue

--skip-umask-check Skips umask settings check

--force Update regardless of current version

(may not be possible in all cases)

--help | -h Show help

Description
firmware_updater RackMgtSwitch is the command used to update the firmware on a rack
management switch.

4-10 00X7003 Rev.1.3

 firmware_updater RackMgtSwitch

Usage
The following provides some sample usage:
./firmware_updater RackMgtSwitch
Updates the firmware on all rack management switches in the system.

./firmware_updater RackMgtSwitch --alias 'netswmgt02'

Updates the firmware only on rack management switch netswmgt02.

00X7003 Rev.1.3 4-11

IBM Netezza FDT User’s Guide

firmware_updater StorageEnclosure
Use this command to update firmware on a disk storage enclosure.
Run from the active host as the root user.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000

Syntax
The command has the following syntax:
firmware_updater StorageEnclosure [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater StorageEnclosure command has the following options.
Table 4-6: firmware_updater StorageEnclosure Options

Option Description

--spa n [--encl n] Execute a firmware update on a specific SPA, specific

enclosure

--firmware BUNDLE Specify an alternative storage enclosure firmware bundle to

use. May be specified more than once, or comma sepa-
rated. If you wish to use globs (*), surround BUNDLE in
quotes

--ignore-nps-state Ignores NPS state requirements

--skip-power-cycle Does NOT power cycle SPAs before update

--skip-bad-components If some components cannot be processed, skip them and

continue

--skip-prompt Skips “press any key to continue” prompt

--skip-rev-check Skips automated sys_rev_check steps to save time

--skip-umask-check Skips umask settings check

--force Forces firmware to be updated, even if already up to date.

--help | -h Show help

4-12 00X7003 Rev.1.3

 firmware_updater StorageEnclosure

Description
firmware_updater StorageEnclosure is the command used to update firmware on a disk
storage enclosure.

Usage
The following provides some sample usage:
./firmware_updater StorageEnclosure
Update firmware on all disk storage enclosures in the system.

./firmware_updater StorageEnclosure --spa 2 encl 2

Update firmware on disk storage enclosure in SPA2, enclosure 2.

00X7003 Rev.1.3 4-13

IBM Netezza FDT User’s Guide

firmware_updater StorageMedia
Use this command to update firmware on a disk drive.
Run from the active host as the root user.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000, 100

Syntax
The command has the following syntax:
firmware_updater StorageMedia [options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The firmware_updater StorageMedia command has the following options.
Table 4-7: firmware_updater StorageMedia Options

Option Description

--spa n [--encl n [--disk n]] Execute a firmware update on a specific SPA, spe-
cific enclosure, specific disk

--firmware BUNDLE Specify an alternative firmware bundle to use.

May be specified more than once, or comma sepa-
rated. If you wish to use globs (*), surround
BUNDLE in quotes.

--ignore-nps-state Ignores NPS state requirements

--force Forces firmware to be updated, even if already up

to date.

--skip-power-cycle Does NOT power cycle SPAs before erase

--skip-bad-components If some components cannot be processed, skip

them and continue

--skip-prompt Skips “press any key to continue” prompt

--skip-rev-check Skips automated sys_rev_check steps to save time

--skip-umask-check Skips umask settings check

--help | -h Show help

4-14 00X7003 Rev.1.3

 firmware_updater StorageMedia

Description
The firmware_updater StorageMedia command is used to update firmware on a disk drive.

Usage
The following provides some sample usage:
./firmware_updater StorageMedia
Update firmware on all disk drives in the system.

./firmware_updater StorageMedia --spa 2 --encl 2 --disk9

Update firmware on disk storage enclosure in SPA2, enclosure 2, disk 9.

00X7003 Rev.1.3 4-15

IBM Netezza FDT User’s Guide

storage_diags
Use this command to check the condition of the storage subsystem.
Run from the Netezza active host as the root user.
Note: You must run storage_diags Aburn while logged in as user nz.

Note: You can run storage_diags Smart while logged in as user nz.

Applicable Systems
N3001-002 and larger, N2001/N2002

Syntax
The command has the following syntax:
storage_diags input_option [component_options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/storage_diags_yyyymmdd-xxxxxx.log

Options
The storage_diags command requires one of the following options.
Table 4-8: storage_diags Options

Input Description
Smart [--spa n | --encl n Gets the Smart status.
| --disk n | --suppress] --spa [1-x] number of SPAs or a single SPA
--encl [1-12] number of the enclosures
--disk [1-24] - select a single disk, range, subset, or all in
target enclosure
--suppress - suppress screen output and create log file in
/opt/nz/fdt/log/SmartResults
Aburn [--time] [--email] Run a data test using NPS
--time; a value range for how long aburn runs
(Default = 2 hours) [optional]
--email; an email address to load into nzevent [optional]
--list-components A list of components that this script supports
-v -v adds simple debug messages
-vv adds detailed debug information (for support purposes)
--help | -h Show help

Description
The storage_diags checks the condition of the storage subsystem.

Usage
The following provides sample usage:

4-16 00X7003 Rev.1.3

 storage_diags

./storage_diags Smart
Gets Smart status of the entire storage subsystem.

00X7003 Rev.1.3 4-17

IBM Netezza FDT User’s Guide

system_diags
Use this command to reset specified components, or to power cycle S-Blades and Disk
Enclosures.
Run from the Netezza active host as the root user.

Applicable Systems
All

Syntax
The command has the following syntax:
system_diags input_option [component_options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/firmware_updater_yyyymmdd-xxxxxx.log

Options
The system_diags command requires one of the following options.
Table 4-9: system_diags Options

Option Description

Concheck Checks the Connectivity of all the non-power cables

Options:
--help : concheck help
--uut=<name> : unit group to test mgt_switch, disk, imm,
fab_switch, host, node, rpc
--encl=<num> : specify enclosure to test
--rack=<num> : rack(s) test
--host=<num> : host(s) to test
--rpc=<name> : RPC(s) test
--switch=<name> : test switch(es)
--dump : Dump debug data if any

4-18 00X7003 Rev.1.3

 system_diags

Table 4-9: system_diags Options (continued)

Option Description

RPCCheck Checks the connections from the PDUs to the hardware

Options:
--help : rpccheck help
--uut=<name> : specify unit to test fab_switch, host,
disk_enclosure
--encl=<num> : specify enclosure to test
--host=<name> : specify host to test--rack=<num> : specify rack to
test
--switch=<name> : specify switch to test
--encl-check-spu : enables non-visual check of enclosure power
using SPU in-band SAS
--encl-check-esm : enables non-visual check of enclosure power
using telnet into enclosure

DataPathCheck Options:
Checks the SAS cabling connections between the disk enclosures
and the H-Chassis SAS switches or DACs, and the backplane con-
nections between the SPUs and the SAS switches
--help : datapathcheck help
--rack=<num> : specify rack to test
--encl=<num> : specify disk enclosure to test
--skip-cabling-check : bypass the cabling connection test
--extended-cabling-check : verify connection by cycling cable PHYs
--skip-health-check : bypass the PHY health test
--skip-bad-components : ignore failed SPUs
--skip-power-cycle : DO NOT power cycle SPUs before running test
--enclosure-id-check : check the enclosure IDs only and DO NOT
power cycle SPUs
--disk-disparity-check : check for disparity errors on disks

PowerCycle Power cycles the S-Blades and Disk Enclosures

Options:
--continue-on-error : Does not stop power cycling until the number
of power cycles is reached
--no-nps-check : does not check if the S-Blade fully boots the NPS
image
--power-cycles n : Runs the specified number of power cycles
(minimum is 1, default is 5)

00X7003 Rev.1.3 4-19

IBM Netezza FDT User’s Guide

Table 4-9: system_diags Options (continued)

Option Description

Reset Resets the specified component(s).

Options:
(--component or --alias required)
--component [mm, mmalt, gigsw, sassw, blade-bmc]
--spa n : resets component in a specific SPA (default is all)
(used with --component option)
--alias ‘name’ : resets one specific component
(does not accept --spa option)
--skip-wait : command doesn’t wait for the component to boot
--skip-nps-state-check : skip the NPS state check (NOT
RECOMMENDED)
--skip-cluster-check : skip the cluster state check (DO NOT SKIP
CLUSTER CHECK WITH 'gigsw.' THIS COULD CAUSE
HOSTS MAJOR ISSUES)

--list-components A list of components that this script supports

-v -v adds simple debug messages

-vv adds detailed debug information (for support purposes)

--help | -h Show help

Description
The system_diags checks the condition of system connections, or resets components.

Usage
The following provides sample usage:
./system_diags RPCCheck
Tests the power connections of the system.

./system_diags Reset --component=mm

Resets all Primary AMMs in all SPAs, then waits until they have all booted.

./system_diags Reset --component=mmalt --spa 2

Resets the Secondary AMM in SPA 2, then waits until it has booted.

./system_diags Reset --alias 'mm001'

Resets the Primary AMM in SPA 1, then waits until it has booted (you may not use
the --spa option with the --alias option).

./system_diags Reset --component 'mm' --skip-wait

Resets all Primary AMMs in all SPAs, then does not wait until they have booted.

./system_diags Reset --alias'mm001' --skip-wait

Resets the Primary AMM in SPA 1, then does not wait until it has booted.

4-20 00X7003 Rev.1.3

 system_diags

./system_diags Reset --component 'sassw'

Resets all SAS switches in all SPAs, then waits until they have all booted.

./system_diags Reset --component 'sassw' --spa 3 --skip-wait

Resets both SAS switches in SPA 3, then does not wait until they have booted.

./system_diags Reset --component 'blade-bmc'

Resets the IMM or BMC on all the S-Blade in the system.

./system_diags Reset --alias 'spu0205'

Resets the IMM or BMC on the S-Blade in slot 5 of SPA2.

./system_diags Reset --alias 'sassw02a'

Resets SAS switch a in SPA 2, then waits until it has booted (you may not use the
--spa option with the --alias option).

concheck Sample Output

Example of concheck:
START: Running ./system_diags concheck
Now creating the lock file [DONE]
----------------------------------------------------------------------
***** S Y S T E M D I A G S *****
FDT 4.3 - /opt/nz/fdt/log/system_diags_20131123-175325.log
------------------------------CONCHECK--------------------------------
Now checking the state of the system [PASS]
--------------------- Rack 1 -------------------
----------- Rack 1 RPC Network Connection Test -----------
RPC rpc1ll RPC Lower Left > Mgt Switch netswmgt01 port 1 [PASS]
RPC rpc1lr RPC Lower Right > Mgt Switch netswmgt01 port 25 [PASS]
RPC rpc1ul RPC Upper Left > Mgt Switch netswmgt01 port 2 [PASS]
RPC rpc1ur RPC Upper Right > Mgt Switch netswmgt01 port 26 [PASS]
----------- Rack 1 Disk Enclosure Network Connection Test -----------
JBOD spade0101 EXP2524 esma > Mgt Switch netswmgt01 port 7 [PASS]
JBOD spade0102 EXP2524 esma > Mgt Switch netswmgt01 port 31 [PASS]
JBOD spade0103 EXP2524 esma > Mgt Switch netswmgt01 port 8 [PASS]
JBOD spade0104 EXP2524 esma > Mgt Switch netswmgt01 port 32 [PASS]
JBOD spade0105 EXP2524 esma > Mgt Switch netswmgt01 port 9 [PASS]
JBOD spade0106 EXP2524 esma > Mgt Switch netswmgt01 port 33 [PASS]
----------- Rack 1 Host Bonded Networks Connection Test -----------
Host ha1 Mgt bond0 eth0 > Mgt Switch Port 3 [PASS]
Host ha1 Mgt bond0 eth7 > Mgt Switch Port 27 [PASS]
Host ha1 DRBD bond1 eth3 eth5 > Host ha2 bond1 eth3 eth5 [PASS]
Host ha1 10GigEth bond2 eth2 > Chassis gigsw01a Port 1 (145)[PASS]
Host ha1 10GigEth bond2 eth4 > Chassis gigsw01b Port 1 (209)[PASS]
Host ha2 Mgt bond0 eth0 > Mgt Switch Port 4 [PASS]
Host ha2 Mgt bond0 eth7 > Mgt Switch Port 28 [PASS]
Host ha2 DRBD bond1 eth3 eth5 > Host ha1 bond1 eth3 eth5 [PASS]
Host ha2 10GigEth bond2 eth2 > Chassis gigsw01a Port 2 (146)[PASS]
Host ha2 10GigEth bond2 eth4 > Chassis gigsw01b Port 2 (210)[PASS]
----------- Rack 1 SPA MM Connection Test -----------
MM mm001 BladeCenter-H > Mgt Switch netswmgt01 port 5 [PASS]
MM mm001alt BladeCenter-H > Mgt Switch netswmgt01 port 29 [PASS]
----------- Rack 1 SPA Gig Switch Connection Test -----------
Rack 1 SPA Gig Switch gigsw01a 5 (149) <-> gigsw01b 5 (213) [PASS]
Rack 1 SPA Gig Switch gigsw01a 6 (150) <-> gigsw01b 6 (214) [PASS]
Rack 1 SPA Gig Switch gigsw01a 7 (151) <-> gigsw01b 7 (215) [PASS]
Rack 1 SPA Gig Switch gigsw01a 8 (152) <-> gigsw01b 8 (216) [PASS]
Rack 1 SPA Gig Switch gigsw01a 9 (153) <-> gigsw01b 9 (217) [PASS]

00X7003 Rev.1.3 4-21

IBM Netezza FDT User’s Guide

Rack 1 SPA Gig Switch gigsw01a 10 (154) <-> gigsw01b 10 (218)[PASS]

Rack 1 SPA Gig Switch gigsw01b 5 (213) <-> gigsw01a 5 (149) [PASS]
Rack 1 SPA Gig Switch gigsw01b 6 (214) <-> gigsw01a 6 (150) [PASS]
Rack 1 SPA Gig Switch gigsw01b 7 (215) <-> gigsw01a 7 (151) [PASS]
Rack 1 SPA Gig Switch gigsw01b 8 (216) <-> gigsw01a 8 (152) [PASS]
Rack 1 SPA Gig Switch gigsw01b 9 (217) <-> gigsw01a 9 (153) [PASS]
Rack 1 SPA Gig Switch gigsw01b 10 (218) <-> gigsw01a 10 (154)[PASS]
----------- Rack 1 Mgt Switch <-> Mgt Switch Test -----------
Now removing the lock file [DONE]
-------------------------------SUMMARY--------------------------------
Final Status [PASS]
Main log file - /opt/nz/fdt/log/system_diags_20120523-175325.log
Start time - Nov May 23 17:53:25 2013
End time - Nov May 23 17:55:55 2013
----------------------------------------------------------------------

4-22 00X7003 Rev.1.3

 system_diags

DataPathCheck Sample Output

Example of DataPathCheck (on an N200x):
START: Running ./system_diags DataPathCheck
Now creating the lock file [DONE]
----------------------------------------------------------------------
***** S Y S T E M D I A G S *****
FDT 4.3 - /opt/nz/fdt/log/system_diags_20321125-083108.log
----------------------------DataPathCheck-----------------------------
Now checking the state of the system [DONE]
Starting the bootpsrv [DONE]
Now powering cycling SPAs [DONE]
Waiting for Blades to pxe boot [DONE]
Waiting for Blades to complete boot [DONE]
--------------------------------Rack 1--------------------------------
----------- Disk Enclosure Phy Health Test -----------
Rack 1 EXP2524 1 spade0101 Disk Enclosure 1 [PASS]
Rack 1 EXP2524 2 spade0102 Disk Enclosure 2 [PASS]
Rack 1 EXP2524 3 spade0103 Disk Enclosure 3 [PASS]
Rack 1 EXP2524 4 spade0104 Disk Enclosure 4 [PASS]
Rack 1 EXP2524 5 spade0105 Disk Enclosure 5 [PASS]
Rack 1 EXP2524 6 spade0106 Disk Enclosure 6 [PASS]
----------- Disk Enclosure External Connection Test -----------
Rack 1 EXP2524 1 spade0101 Disk Enclosure 1 [PASS]
Rack 1 EXP2524 2 spade0102 Disk Enclosure 2 [PASS]
Rack 1 EXP2524 3 spade0103 Disk Enclosure 3 [PASS]
Rack 1 EXP2524 4 spade0104 Disk Enclosure 4 [PASS]
Rack 1 EXP2524 5 spade0105 Disk Enclosure 5 [PASS]
Rack 1 EXP2524 6 spade0106 Disk Enclosure 6 [PASS]
Clearing PHY errors from ESM external connections [DONE]
Now removing the lock file [DONE]
-------------------------------SUMMARY--------------------------------
Final Status [PASS]
Main log file - /opt/nz/fdt/log/system_diags_20120525-083108.log
Start time - Fri Nov 25 08:31:08 2013
End time - Fri Nov 25 09:19:07 2013
----------------------------------------------------------------------

00X7003 Rev.1.3 4-23

IBM Netezza FDT User’s Guide

Troubleshooting N1001
To assist in determining failure indications of DataPathCheck, the SAS cabling of each rack
within the N1001 runs from:
 SPA1 Chassis SAS Switch (upper, slot 3) ports 1 through 4 to Left ESMs, JBOD 1-4
 SPA1 Chassis SAS Switch (lower, slot 4) ports 1 through 4 to Right ESMs, JBOD 1-4
 SPA2 Chassis SAS Switch (upper, slot 3) ports 1 through 4 to Left ESMs, JBOD 5-8
 SPA2 Chassis SAS Switch (lower, slot 4) ports 1 through 4 to Right ESMs, JBOD 5-8

Example 1:
Symptom: Failures are indicated on the diagnostic output:
SPA 1 Enclosure E1 [FAIL]
Enclosure E1 Left Side SAS Address Mismatch
Action to take:
Note that the location of the failure is identified by:
SPA (SPA 1 in the example)
Disk Enclosure (E1 - in the example)
ESM (Left in the example)

 Reseat the cable at the indicated ESM.

Example 2: Another example of a failure:

Symptom: Failures are indicated on the diagnostic output:
Testing SAS Switch sassw01a PHYs [FAIL]
Only 24 of 28 sas port phys report normal
Failed: Connection between sassw01a and Enclosure 1
Failed: Connection between sassw01a and Enclosure 1
Failed: Connection between sassw01a and Enclosure 1
Failed: Connection between sassw01a and Enclosure 1

Action to take:
Note that the location of the failure is identified by:
SAS Switch (sassw01a in the example)
Disk Enclosure (E1 - in the example)
 Reseat the cables at the indicated SAS switch and ESMs.

In the following illustration, the associated port on the Chassis SAS switches are shown,
where applicable.

4-24 00X7003 Rev.1.3

 system_diags

Figure 4-1: N1001 SAS Cabling

00X7003 Rev.1.3 4-25

IBM Netezza FDT User’s Guide

Troubleshooting N200x/N3001-002 and larger

If DataPathCheck indicates a problem with SAS cabling, the first step is to reseat the SAS
cables at both ends - DAC and ESM - and then re-run DataPathCheck.
To assist in determining failure indications of DataPathCheck, the following failure exam-
ples and illustrations show details of the SAS cabling within the N200x/N3001 racks.
The cabling runs from:
 DAC to ESM
 ESM to ESM

Example 1:
Symptom: Failures are indicated on the diagnostic output:
Rack 1 EXP2524 1 spade0101 Disk Enclosure 1 [FAIL]
Failed: Link not present spade0101[ESM-R Right Conn (in-2)]
PHY-24 esm_side-right
Action to take:
Note that the location of the failure is identified by:
Rack (rack 1 in the example)
Disk Enclosure (enclosure 1 in the example)
ESM (Right in the example)
Connector (IN-2 in the example)

 Reseat the cable at the indicated ESM.

Example 2: Another example of a failure:

Symptom: Failures are indicated on the diagnostic output:
Rack 1, top half [FAIL]
Failed: spu0109 [spu0109 Port 2 (2nd connector from top)] to spade0104
[ESM-L Middle Conn (in-1)]
Failed: spu0111 [spu0111 Port 2 (2nd connector from top)] to spade0105
[ESM-L Middle Conn (in-1)]
Action to take:
Note that the location of the failure is identified by:
Rack (rack 1 in the example)
SPUs (SPA 01, slots 9 and 11 in the example)
DAC ports (2nd connector from top (on both DACs) in the example)
ESM (Left in the example, SPA 01, Disk Enclosures 4 and 5)
Connector (IN-1 in the example, middle connector)

 Reseat the cables at the indicated SPUs and ESMs.

4-26 00X7003 Rev.1.3

 system_diags

Example 3: A third example of a failure:

Symptom: It appears that the SAS cables on DAC2 (bottom DAC) are either not connected
on the SPU or at the ESM end. Note that both failures involve spu0103: Port 3
and Port 4.

---------------Disk Enclosure External Connection Test----------------

Rack 1 EXP2524 1 spade0101 Disk Enclosure 1 [FAIL]
Missing connection from spu0103 Port 3 (3rd connector from top) to
spade0101 ESM-L Left Conn (out)

Rack 1 EXP2524 2 spade0102 Disk Enclosure 2 [FAIL]

Missing connection from spu0103 Port 4 (bottom connector) to spade0102
ESM-L Left Conn (out)
Action to take:
1. Reseat both ends of the cables.
2. If the cables are properly seated, the bottom DAC may have failed. To check the DAC,
log into the S-Blade and run an lspci command:
[root@nzhost ~]# ssh spu0103
root@spu0103's password:
Last login: Thu Jun 4 08:21:47 2015 from npshost
IBM Netezza -- NPS SPU 4.0
(C) Copyright IBM Corp. 2006, 2011 All Rights Reserved.
BusyBox v1.20.2 (2014-07-15 10:43:42 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

spu0103# lspci | grep SAS

23:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
29:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

If both SAS controllers are listed in the output from the lspci command (in this exam-
ple, both controllers are listed: 23:00.0 and 29:0.0), then you have a cable connection
issue.
If only one SAS controller is listed, than the DAC that is not listed has failed.

00X7003 Rev.1.3 4-27

IBM Netezza FDT User’s Guide

In the following illustrations, the associated port on the S-Blade/DAC is shown, where
applicable.

Figure 4-2: Half-Rack SAS Cabling

4-28 00X7003 Rev.1.3

 system_diags

Figure 4-3: Full-Rack SAS Cabling

00X7003 Rev.1.3 4-29

IBM Netezza FDT User’s Guide

sys_rev_check
Use this utility to check the firmware versions of the system components. To avoid compo-
nents receiving a [SKIPPED] status, use this utility while the system is online, or offline
with bootpsrv running (use the command /nz/kit/sbin/bootpsrv to start bootpsrv).
Run from the active host (as the root or nz user).
Note: When running sys_rev_check while logged in as user nz, results for Host are not
available.

Applicable Systems
All

Syntax
The command has the following syntax:
sys_rev_check input_option [component_options]

Location
/opt/nz/fdt
Log file location: /opt/nz/fdt/log/sys_rev_check_yyyymmdd-xxxxxx.log

Options
The sys_rev_check command accepts the following options.
Table 4-10: sys_rev_check Options

Option Description
Checks ASU settings [default off]
--list-components A list of components that this script supports
--list-revisions A list of all revisions carried by FDT
Host Identifies firmware and hardware of hosts
Options:
--ha1 : checks only HA1 [default both]
--ha2 : checks only HA2 [default both]
--cfg : checks ASU and RAID settings [default off]

RPC Identifies firmware

Options:
--rack : checks only a specific rack [default all]
--alias : checks only a specific rpc

MM Identifies firmware versions and slot locations of SPA Man-

agement Modules
Options:
--spa : checks only a specific spa [default all]
--alias : checks only a specific MM

4-30 00X7003 Rev.1.3

 sys_rev_check

Table 4-10: sys_rev_check Options (continued)

Option Description
SpaGigSwitch Identifies firmware versions of SPA gigabit switches
Options:
--spa : checks only a specific spa [default all]
--alias : checks only a specific GigSwitch

SpaSasSwitch Identifies firmware versions of SPA SAS switches

Options:
(N1001/100 only) ---spa n : checks only a specific spa [default all]
--alias sassw00[a|b]: checks only a specific SasSwitch

RackMgtSwitch Identifies firmware versions of rack mount mgt switches

Options:
--alias : checks only a specific Rack Mgt switch

RackFabSwitch Identifies firmware versions of rack mount fab switches

Options:
--alias : checks only a specific Rack Fab switch

PowerCheck Checks for correct hardware of SPA chassis power supplies

Options:
--spa : checks only a specific spa [default all]

Blade Identifies firmware versions and check for correct hardware of

S-Blades
Options:
--firmware : checks only the firmware [default on]
--hardware : checks only for correct hardware [default on]
--ethernet : checks only ethernet chipset firmware [default on]
--hba : checks only the HBAs [default on]
--spa : checks only a specific spa [default all]
--slot : checks only a specific slot [default all]
--alias : checks only a specific spu [default off]
--cfg : checks ASU settings [default off]

StorageEnclosure Identifies firmware versions of storage enclosures

Options:
--spa : checks only a specific spa [default all]
--encl : checks only a specific encl [default all]

StorageMedia Identifies firmware versions of storage media

Options:
--spa : checks only a specific spa [default all]
--encl : checks only a specific encl [default all]
--disk : checks only a specific disk [default all]

-v -v adds simple debug messages

-vv adds detailed debug information (for support purposes)
--help | -h Show help

00X7003 Rev.1.3 4-31

IBM Netezza FDT User’s Guide

Note: The following options (valid in previous FDT releases) are no longer supported from
the CLI:

hba - must now be specified as Blade --hba

bladefirmware - must now be specified as Blade --firmware

Description
The sys_rev_check command checks the firmware or hardware versions of system
components.
The log output of sys_rev_check includes details of supported versions of hardware, drivers,
and firmware and provides details of discovered versions of hardware, drivers, and firmware
in the system. The following table lists the components checked.
Table 4-11: sys_rev_check Components

Host Blade Other

Disks (Model and FW) HBA (Rev, Diag, BIOS) RPC

10Gb (FW and Driver) 1Gb AMM

IMM (ID and Rev) IMM (ID and Rev) SPA Gig Sw

ASU (cfg) pDSA (ID and Rev) SPA SAS Sw

pDSA (ID and Rev) Processor (Model, Speed, Rev) Rack Mgt Sw

Processor (Model, Qty) uEFI (ID and Rev) Rack Fab Sw

uEFI (ID and Rev) Memory (Qty and Type) SPA Power Supply

Memory (Qty and Type) RAID (cfg) Storage Encl (ESM FW)

FPGA (ID and Rev) Storage Media (Model, FW)

RAID (FW and cfg)

SAS BP

PSoC (INFO)

TMM - RAID Flash (INFO)

Customer Adds (INFO)

Usage
The following provides sample usage:
./sys_rev_check
Checks the firmware versions of all the components of the system.

./sys_rev_check mm

4-32 00X7003 Rev.1.3

 sys_rev_check

Checks the firmware versions and slot locations of all AMMs in the system.

./sys_rev_check Blade --hba --spa 2

Checks the firmware versions and BIOS erase of the HBAs in SPA 2.

00X7003 Rev.1.3 4-33

IBM Netezza FDT User’s Guide

getservicedata.pl
This script collects Management Module service data from one AMM and S-Blades (does
not apply to HS21) within a specified chassis.

Applicable Systems
N3001-002 and larger, N2001/N2002, N1001, 1000

Syntax
The command has the following syntax:
getservicedata.pl AMM_id [blade_list] [--dir=<target_dir>]

Location
/opt/nz/service_tools/getservicedata
Log file location (default, if other target directory not specified): /tmp/getservicedata

Options
The getservicedata.pl tool requires one of the following options.
Table 4-12: getservicedata.pl Options

Option Description

AMM_id The ID of the AMM

blade_list The slot number(s) of the S-Blades from

which to collect the IMM logs

--dir=<target_dir> Defines location for log file; directory is cre-

ated if it doesn’t exist

--help | -h Show help

Description
This script may be executed multiple times at once, to collect logs across multiple SPAs
(chassis).
The recommended practice is to run each execution of the script in a separate window,
however the script can also be executed several times in the background.
Each executing copy creates a unique temp directory to hold all log files, and each creates
a uniquely named tarball upon completion.
All screen output is logged to a unique time stamped file in the target directory using the
naming format, getservicedata_DDMMMYYYY_hhmmss.log.
The specified target directory will be created if it does not exist. If no target is specified,
the default path of '/tmp/getservicedata' is used.

4-34 00X7003 Rev.1.3

 getservicedata.pl

Usage
The following provides some sample usage:
./getservicedata.pl mm001 1,3,5
Collects logs from the active AMM on SPA1 along with IMM logs from the three
S-Blades in slots numbered 1,3,5 and place service data output in target directory
/var/log.
./getservicedata.pl mm001 all
Collects IMM logs from all the SPUs in a fully populated SPA.
./getservicedata.pl mm001
Collects only AMM logs.

./getservicedata.pl mm001 --dir=/var/log

Collects IMM logs from all the SPUs in a fully populated SPA and places the log file in the
target directory. The directory is created if it doesn’t exist.

00X7003 Rev.1.3 4-35

IBM Netezza FDT User’s Guide

4-36 00X7003 Rev.1.3

 APPENDIX A
Notices and Trademarks
What’s in this appendix
 Notices
 Trademarks
 Electronic Emission Notices
 Regulatory and Compliance

This section describes some important notices, trademarks, and compliance information.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other
countries. Consult your local IBM representative for information on the products and ser-
vices currently available in your area. Any reference to an IBM product, program, or service
is not intended to state or imply that only that IBM product, program, or service may be
used. Any functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's responsibility
to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not grant you any license to these
patents. You can send license inquiries, in writing, to: This information was developed for
products and services offered in the U.S.A.
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellec-
tual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where
such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE

A-1
IBM Netezza FDT User’s Guide

IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR

A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied war-
ranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in new edi-
tions of the publication. IBM may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only
and do not in any manner serve as an endorsement of those Web sites. The materials at
those Web sites are not part of the materials for this IBM product and use of those Web
sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropri-
ate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs and
other programs (including this one) and (ii) the mutual use of the information which has
been exchanged, should contact:
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including
in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it
are provided by IBM under terms of the IBM Customer Agreement, IBM International Pro-
gram License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment.
Therefore, the results obtained in other operating environments may vary significantly.
Some measurements may have been made on development-level systems and there is no
guarantee that these measurements will be the same on generally available systems. Fur-
thermore, some measurements may have been estimated through extrapolation. Actual
results may vary. Users of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from the suppliers of those prod-
ucts, their published announcements or other publicly available sources. IBM has not
tested those products and cannot confirm the accuracy of performance, compatibility or
any other claims related to non-IBM products. Questions on the capabilities of non-IBM
products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or with-
drawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to
change without notice. Dealer prices may vary.
This information contains examples of data and reports used in daily business operations.
To illustrate them as completely as possible, the examples include the names of individu-
als, companies, brands, and products. All of these names are fictitious and any similarity to
the names and addresses used by an actual business enterprise is entirely coincidental.

A-2 00X7003 Rev.1.3

 Trademarks

COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate
programming techniques on various operating platforms. You may copy, modify, and distrib-
ute these sample programs in any form without payment to IBM, for the purposes of
developing, using, marketing or distributing application programs conforming to the appli-
cation programming interface for the operating platform for which the sample programs are
written. These examples have not been thoroughly tested under all conditions. IBM, there-
fore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must include a
copyright notice as follows:
© your company name) (year). Portions of this code are derived from IBM Corp. Sample
Programs.
© Copyright IBM Corp. _enter the year or years_.
If you are viewing this information softcopy, the photographs and color illustrations may not
appear.

Trademarks
IBM, the IBM logo, ibm.com and Netezza are trademarks or registered trademarks of Inter-
national Business Machines Corporation in the United States, other countries, or both. If
these and other IBM trademarked terms are marked on their first occurrence in this infor-
mation with a trademark symbol (® or ™), these symbols indicate U.S. registered or
common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current
list of IBM trademarks is available on the Web at “Copyright and trademark information” at
ibm.com/legal/copytrade.shtml.
Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/
or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corpo-
ration in the United States, other countries, or both.
NEC is a registered trademark of NEC Corporation.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.
Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and/or
other countries.
D-CC, D-C++, Diab+, FastJ, pSOS+, SingleStep, Tornado, VxWorks, Wind River, and the
Wind River logo are trademarks, registered trademarks, or service marks of Wind River Sys-
tems, Inc. Tornado patent pending.
APC and the APC logo are trademarks or registered trademarks of American Power Conver-
sion Corporation.
Other company, product or service names may be trademarks or service marks of others.

00X7003 Rev.1.3 A-3

IBM Netezza FDT User’s Guide

Electronic Emission Notices

When you attach a monitor to the equipment, you must use the designated monitor cable
and any interference suppression devices that are supplied with the monitor.

Federal Communications Commission (FCC) Statement

Note: This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide
reasonable protection against harmful interference when the equipment is operated in a
commercial environment. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential
area is likely to cause harmful interference, in which case the user will be required to cor-
rect the interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC
emission limits. IBM is not responsible for any radio or television interference caused by
using other than recommended cables and connectors or by unauthorized changes or mod-
ifications to this equipment. Unauthorized changes or modifications could void the user's
authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following
two conditions: (1) this device may not cause harmful interference, and (2) this device
must accept any interference received, including interference that might cause undesired
operation.

Industry Canada Class A Emission Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d'Industrie Canada

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

Australia and New Zealand Class A Statement

Attention: This is a Class A product. In a domestic environment this product may cause
radio interference in which case the user may be required to take adequate measures.

European Union EMC Directive Conformance Statement

This product is in conformity with the protection requirements of EU Council Directive
2004/108/EC on the approximation of the laws of the Member States relating to electro-
magnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the
protection requirements resulting from a nonrecommended modification of the product,
including the fitting of non-IBM option cards.
Attention: This is an EN 55022 Class A product. In a domestic environment this product
may cause radio interference in which case the user may be required to take adequate
measures.
Responsible manufacturer:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900

A-4 00X7003 Rev.1.3

 Electronic Emission Notices

European Community contact:

IBM Technical Regulations, Department M456
IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: [email protected]

Germany Class A Statement

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur Elektro-
magnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur
Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-
Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu instal-
lieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel
angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der
Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw. wenn
Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/einge-
baut werden.
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:
“Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbere-
ich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber verlangt werden,
angemessene Maßnahmen zu ergreifen und dafür aufzukommen.”

Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit von
Geräten (EMVG)”. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundes-
republik Deutschland.

Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Geräten
(EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konfor-
mitätszeichen - CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland
Technical Regulations, Department M456
IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: [email protected]
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.

00X7003 Rev.1.3 A-5

IBM Netezza FDT User’s Guide

Japan VCCI Class A Statement

This is a Class A product based on the standard of the Voluntary Control Council for Inter-
ference (VCCI). If this equipment is used in a domestic environment, radio interference
may occur, in which case the user may be required to take corrective actions.

Japan Electronics and Information Technology Industries Association (JEITA) Statement

Japan Electronics and Information Technology Industries Association (JEITA) Confirmed

Harmonics Guidelines (products less than or equal to 20 A per phase)

Japan Electronics and Information Technology Industries Association (JEITA) Statement

Japan Electronics and Information Technology Industries Association (JEITA) Confirmed

Harmonics Guidelines (products greater than 20 A per phase)

Korea Communications Commission (KCC) Statement

This is electromagnetic wave compatibility equipment for business (Type A). Sellers and
users need to pay attention to it. This is for any areas other than home.

Russia Electromagnetic Interference (EMI) Class A Statement

People's Republic of China Class A Electronic Emission Statement

A-6 00X7003 Rev.1.3

 Regulatory and Compliance

Taiwan Class A Compliance Statement

Regulatory and Compliance

Regulatory Notices
Install the NPS system in a restricted-access location. Ensure that only those trained to
operate or service the equipment have physical access to it. Install each AC power outlet
near the NPS rack that plugs into it, and keep it freely accessible.
Provide approved circuit breakers on all power sources.
Product may be powered by redundant power sources. Disconnect ALL power sources
before servicing.
High leakage current. Earth connection essential before connecting supply. Courant de
fuite élevé. Raccordement à la terre indispensable avant le raccordement au réseau.
Homologation Statement
This product may not be certified in your country for connection by any means whatsoever
to interfaces of public telecommunications networks.
Further certification may be required by law prior to making any such connection. Contact
an IBM representative or reseller for any questions.

00X7003 Rev.1.3 A-7

IBM Netezza FDT User’s Guide

A-8 00X7003 Rev.1.3