Netezza System Configuration Guide Ha Xs

-

System Configuration GuideforSingle Rack 1000-Series Systems(x3650 M3 Hosts)Revised: June 17, 2011

D20524-3 Rev. 3.0

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

© Copyright IBM Corporation 2001-2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Preface

1 Configuring The Host ComputersHardware and Media Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Configuring the Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Update Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Setting Up Host 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Setting Up Host 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

2 Installing the Operating SystemInstalling the Operating System Onto Host 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing Host 1 Platform Support Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Installing the Base Host Support Software for Host 1 . . . . . . . . . . . . . . . . . . . . . 2-2

Finishing the Host Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Installing the Operating System Onto Host 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Installing Host 2 Platform Support Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Installing the Base Host Support Software for Host 2 . . . . . . . . . . . . . . . . . . . . . 2-6

Finishing the Host Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

3 Configuring The PDUs, Switches, and the Cluster ManagerWhat You Need Before Starting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Configuring ssh for Each Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Install Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuring the Management Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuring the Power Distribution Units (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Updating the PDU Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Configuring the PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Testing the PDUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Configuring the Chassis Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Component Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Restoring Serial Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Configuring the Cluster Manager for Hosts 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Checking Port and Switch Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Configuring Switch Ports and Checking Wiring . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Checking Power Connections and Firmware Revisions . . . . . . . . . . . . . . . . . . . . . . . 3-10

i

4 Installing The NPS SoftwareInstalling NPS Software on Both Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Setting Up to Install the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Installing the Host Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Configuring a Modem and Email Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuring a Serial Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Error Reporting Through Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

5 Initializing and Testing The System FabricUpdating System Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Configure the heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Update the Management and Fabric Switch Firmware . . . . . . . . . . . . . . . . . . . . . 5-1

Install Database Accelerator Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Update the Chassis Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Check the Firmware Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Run nzupgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Run the Power Cycle Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Start the bootp Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Set the Enclosure IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Update the ESM Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Erase the HBA BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Update the Disk Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Running Diagnostic Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Run the Disk SmartSuite Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Stop the bootp Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Run the S-Blade Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Start the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Check Firmware Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Run the Physical Port Evaluation (aBurn) Check. . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Run the testSuite diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Reinitialize the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Testing the System Fabric and Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Testing Host 1 as Master of System Fabric and Shared Disks. . . . . . . . . . . . . . . . 5-8

Testing Host 2 as Master of System Fabric and Shared Disks. . . . . . . . . . . . . . . . 5-8

Bringing Up the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

ii

Appendix A: Reference MaterialsSystem Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

IBM x3650 M3 Host Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Ethernet Switch Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

PDU Power Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

SAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11

Shutting Down and Bringing Up a IBM Netezza 1000-Series System . . . . . . . . . . . . A-12

Shutting Down a IBM Netezza 1000-Series System . . . . . . . . . . . . . . . . . . . . . A-12

Bringing Up a IBM Netezza 1000-Series System . . . . . . . . . . . . . . . . . . . . . . . A-12

Appendix B: Configurable IPHardware and Media Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

IP Configuration Procedure for Internal Components . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Run nzupgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

IP Configuration Procedure for External Network Connections . . . . . . . . . . . . . . . . . . B-6

Preparing to Change IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Changing the IP Address Associated with the Host Name . . . . . . . . . . . . . . . . . . B-7

Changing the Floating IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Changing the Host Name and DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13

Appendix C: IMM Configuration

Appendix D: PDU Firmware Update ProcedurePrerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

IP Address Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Firmware Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Appendix E: Configuration Command Referencedrbd_config.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

heartbeat_config.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

heartbeat_admin.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

netswmgtConfig.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

rpcconfigure -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

rpcverify -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

sshconfigure -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5

spa_init.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5

spaconfigure.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5

spapwr.sh -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6

swsupport -h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7

iii

Appendix F: Notices and TrademarksNotices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3

Open Source Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4

Regulatory and Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-6

iv

Table 1-1: Media Needed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Table 1-2: Hardware Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-3: Host Name and IP Addresses Needed . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-4: Example IMM Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Table 3-1: Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Table A-1: IBM x3650 M3 Host Network Connections . . . . . . . . . . . . . . . . . . . A-2

Table D-1: PDU IP Address Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Rev. 1-v

1-vi Rev.

PrefaceThis guide includes a series of procedures you must follow to fully configure any IBM Netezza Single Rack 1000-Series system. Where possible, the procedures are listed in the order in which you would perform them.

About This Guide

The System Configuration Guide for Single Rack 1000-Series Systems is written for IBM Netezza personnel and those authorized to configure any of the IBM Netezza 1000-Series systems. The procedures in this document assume the following:

You have the IBM Netezza system racks set-up and properly cabled.

All IBM Netezza system components have been previously installed.

The Purpose of This Guide

The System Configuration Guide for Single Rack 1000-Series Systems was written to pro-vide those procedures you must perform to fully configure an IBM Netezza system.

Topics See …

Configuring the host computers. This section includes information on configuring the hosts at initial boot.

“Configuring The Host Computers” on page 1-1

Installing the Operating System. This section covers installing the operating system and sup-port software.

“Installing the Operating System” on page 2-1

Configuring the PDUs, switches, and cluster manager. The section also includes such tasks as checking port and switch connections, and configuring ssh for each host.

“Configuring The PDUs, Switches, and the Cluster Manager” on page 3-1

Installing the NPS software. The section includes installing the NPS software and config-uring a modem for each host.

“Installing The Netezza Software” on page 4-1

Testing the system fabric and shared disks. The section includes bringing up the IBM Netezza system in a clustered environment.

“Initializing and Testing The System Fabric” on page 5-1

A listing of reference materials, such as network and power connections.

“Reference Materials” on page A-1

vii

Symbols and Conventions

This guide uses the following typographical conventions:

Numbered steps for procedures

Bulleted lists for topics

Italics for terms, and user-defined variables such as file names

bold for command line input and system output examples

If You Need Help

If you are having trouble using the Netezza appliance, you should:

1. Retry the action, carefully following the instructions given for that task in the documentation.

2. Go to the Netezza Knowledge Base at https://knowledge.netezza.com. Enter your sup-port username and password. You can search the knowledge base or the latest updates to the product documentation. Click Netezza HelpDesk to submit a support request.

3. If you are unable to access the Netezza Knowledge Base, you can also contact Netezza Support at the following telephone numbers:

North American Toll-Free: +1.877.810.4441

United Kingdom Free-Phone: +0.800.032.8382

International Direct: +1.508.620.2281

Refer to your Netezza maintenance agreement for details about your support plan choices and coverage.

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

C H A P T E R 1
Configuring The Host Computers
What’s in this chapterHardware and Media Needed

Configuring the Hosts

The first task once the system is properly set-up is to configure its host computers.

Review the list of requirements in the next section and make sure that you have access to all items listed. Then go to the section entitled “Configuring the Hosts” on page 1-3 and follow the procedures there.

Hardware and Media Needed

The following tables list the items and the information needed to complete the configura-tion of the host computers.

Fill in Table 1-3 with the values relevant for your installation. Since this information is site-specific, consult with your System Administrator if you have questions concerning these values.

Table 1-1: Media Needed

Item Title

1 DVD Red Hat 5.5 Installation

1 DVD RHEL 5.5 Manufacturing Update

1 DVD Netezza Firmware/Diagnostics/Tools

1 DVD Netezza Host Platform Configuration

1 CD Netezza Server Software

1 DVD IBM Host Management

1 DVD IBM Host Firmware 36xx

1-1

System Configuration Guide for Single-Rack 1000-Series Systems (x3650 M3 Host)

Table 1-2: Hardware Needed

Item Description

Laptop Computer

A laptop running Microsoft Windows XP (SP3) with Internet Explorer (7.0) is needed for configuring RSA II email notification.

Mouse USB mouse for configuring the disk array

Cables You should have the following cables available to you:

• APC PDU serial cable, DB9 M/F, 10’ (21594).

• BNT switch serial cable, DB9F to mini-USB (IBM FRX0510)

• Host-to-AMM serial cable

• Serial cable, RJ11 to DB9 (21551).

• Extension cable, RJ11 (21552).

• Ethernet cable, RJ45 to RJ45.

Table 1-3: Host Name and IP Addresses Needed

Item Value (Fill in with site-specific values)

Host 1 name ________________________________________

Host 2 name ________________________________________

Cluster alias ________________________________________

Host 1 IP address ________________________________________

Host 2 IP address ________________________________________

Host 1 IMM IP address ________________________________________

Host 2 IMM IP address ________________________________________

Gateway IP address ________________________________________

Subnet mask ________________________________________

1-2 D20524-3 Rev.3.0



To setup the hosts, you must

update the firmware on each host,

configure the disk array on each host,

set the IMM (Integrated Management Module) network addresses on each host, and

configure the Power Restore Policy on each host.

Update Firmware

1. Move to the KVM for Host 1 (the upper host).

2. Place the IBM Host Firmware 36xx DVD into the CD/DVD drive.

3. Cycle the power (green button on lower front of the Host) to reboot the host.

The system begins to boot from the DVD.

Result: The system boots into the ToolCenter application, inventories the firmware on the host and displays a summary. This may take several minutes.

4. When the summary screen appears, choose Select All (Shift-S) from the menu at the bottom of the screen.

5. With all updates selected (marked with an asterisk [*] ), choose Apply All Selected (Shift-A) from the menu at the bottom of the screen.

Note: You have 60 seconds to complete this step before the utility automatically starts the update.

Note: The update will fail for components not installed in the system. This is normal and is only cause for alarm if the component is, in fact, installed and was not detected. In this case, troubleshoot the failed component and rerun the firmware update.

6. When the update has completed, type ‘q‘ to exit the firmware update utility.

7. The Host 1 firmware has been updated. Remove the DVD from the drive.

8. Move to Host 2 and repeat this procedure to update the firmware on Host 2.

Setting Up Host 1The sections that follow contain procedures for configuring the disk array, Integrated Man-agement Module (IMM) setup and setting the Power Restore policy.

Configuring the Disk Array Perform the steps in this procedure to configure the disk array on the host.

Note: Shortly after powering up the host in step 1 below, you will be prompted to press “^H for WebBIOS”. You should be prepared for this message and act promptly to avoid the need to reboot.

1. Power up Host 1

D20524-3 Rev.3.0 1-3


2. Press CTRL-H when prompted by the system.

3. You are presented with the Adapter Selection screen.

Select the radio button for Adapter 0 and click on the Start button.

4. The opening screen for the RAID BIOS Configuration Utility appears.

From the menu pane on the left side of the screen, click on the Scan Devices item.

5. The host scans the disk array and any additional drives are added to the Physical View on this screen. There should be a total of seven (7) disk drives listed.

From the menu pane on the left side of the screen, click on the Configuration Wizard menu item.

6. The first screen of the Configuration Utility is displayed:

Select the Clear Configuration option and click on the Next button.

7. You are asked to confirm your choice:

Click the Yes button to confirm the choice to clear any existing configuration.

8. You are returned to the Physical View screen. You should see seven (7) drives located in slots 0 through 6. Each drive should be “Unconfigured Good”. If this is not the case, then you must troubleshoot the problem with the disk drives and restart the RAID configuration procedure from the beginning.

From the menu pane on the left side of the screen, click on the Configuration Wizard menu item.

9. You are presented with configuration options again:

Select the New Configuration option and click on the Next button.

10. You are again asked to confirm your choice:

Click the Yes button to confirm the choice to clear the configuration.

11. The resulting screen allows you to choose how you want to perform the configuration:

Select Manual Configuration and then click the button labeled Next.

12. The Drive Group Definition screen appears:

Perform the following steps to define the Drive Groups:

Define Drive Group0

a. In the left pane, hold down the CTRL key and click on Backplane to de-select the top line.

b. Also in the left pane, select the first two (2) drives (Slot 0 and Slot 1) by holding down the CTRL key and clicking on each disk.

c. Click the Add to Array button to move the selected drives to the right pane. These drives will be in Drive Group0.

d. Click on the Accept DG button to accept this Drive Group (Drive Group0).

1-4 D20524-3 Rev.3.0


Define Drive Group1


b. Select the next two (2) drives (Slot 2 and Slot 3) by holding down the CTRL key and clicking on each disk.

c. In the right pane, click on Drive Group1.

d. Click the Add to Array button to move the selected drives to the right pane. These drives will be in Drive Group1.

e. Click on the Accept DG button to accept this Drive Group (Drive Group1).

Define Drive Group2


b. Select the next two (2) drives (Slot 4 and Slot 5) by holding down the CTRL key and clicking on each disk.

c. In the right pane, click on Drive Group2.

d. Click the Add to Array button to move the selected drives to the right pane. These drives will be in Drive Group2.

e. Click on the Accept DG button to accept this Drive Group (Drive Group2).

The result should look like Figure 1-1.

Figure 1-1: Drive Group Definition Screen

D20524-3 Rev.3.0 1-5


13. Click the Next button to get to the Span Definition screen.

14. The Span Definition screen is displayed.

Select Drive Group0 from the drop-down menu in the left pane and click the Add to SPAN button to move the array to the right pane.

15. Drive Group0 is moved to the right pane.

16. Select Drive Group1 from the drop-down menu in the left pane and click the Add to SPAN button to move the array to the right pane.


18. Select Drive Group2 from the drop-down menu in the left pane and click the Add to SPAN button to move the array to the right pane.


20. Click on the Next button.

21. The Virtual Drive Definition screen is displayed (Figure 1-2).

Figure 1-2: Virtual Drive Definition Screen

1-6 D20524-3 Rev.3.0


22. Select the following values for the fields on this screen.

23. Click the Accept button.

24. You are asked to confirm your selection of Always Write Back.

Click the Yes button.

25. The Virtual Drive Definition Screen appears.

Click the Next button.

Note: When this screen appears, all the fields will display their default values. This is expected. None of the fields should be changed in this step

26. The Config Wizard Preview screen appears.

Click the Accept button.

27. You will be prompted to save the configuration.

Click the button labeled Yes.

28. You are asked to confirm that you want to initialize the array:


29. The Virtual Drives screen appears.

Click the button labeled Home.

30. You are returned to the main screen of the BIOS Configuration Utility:

Click on the unconfigured drive at the bottom of the list.

31. The Properties screen for the unconfigured drive appears.

Select Make Global HSP, click on the Go button and then click Home.

32. You are returned to the main RAID BIOS Configuration screen.

Click the Exit menu item in the pane on the left side of the screen.

Field Value

RAID Level RAID 10

Strip Size 256 KB

Access Policy RW

Read Policy Normal

Write Policy Always Write Back

IO Policy Cached

Drive Cache NoChange

Disable BGI No

Select Size Use the value for R10 in Figure 1-2

D20524-3 Rev.3.0 1-7


33. The screen that is displayed asks you to confirm.


34. You are prompted to reboot the system:

Press CTRL-ALT-DEL to reboot the system.

The disk array on Host 1 is now configured.

Proceed directly to “Integrated Management Module (IMM) IP Address Setup”.

Be prepared to press the F1 key after the host reboots. You will receive a prompt on the screen as the host boots up.

Integrated Management Module (IMM) IP Address SetupPerform the steps in this procedure to define the IP address for the host’s Integrated Man-agement Module (IMM).

1. Press the F1 key when prompted. The prompt screen will look similar to Figure 1-3.

Figure 1-3: Initial BIOS Screen

2. You are presented with the System Configuration and Boot Management menu.

Select System Settings and press the Enter key.

1-8 D20524-3 Rev.3.0


3. On the System Settings screen that appears, use the arrow keys to highlight the line that says Integrated Management Module, and press the Enter key.

4. On the Integrated Management Module screen that appears, use the arrow keys to highlight the line that says Network Configuration, and press the Enter key.

5. For each of the fields on this screen, enter the values that are appropriate for your site (refer to the information that you wrote down in Table 1-3 on page 1-2). Use the UP and Down arrows to move between fields. Use the Left and Right arrows to navigate within a field or to select from several different options.

6. Use the arrow keys to highlight the line that says Save Network Settings, and press the Enter key.

7. You are informed that the “Network settings have been saved successfully” and to “Press Y to reset the IMM now.”

Press the Y key and then press the Enter key.

8. Press the Esc key twice to return to the System Settings menu.

Note: It may take several moments before the IMM resets and you are returned to the System Settings menu. Be patient.

The IMM IP Address Setup for Host 1 is complete..

Table 1-4: Example IMM Settings

Setting Value

Network Interface Port Shared

DHCP Control Static IP

IMM IP Address For these three parameters, use the values that are correct for your site. Refer to Table 1-3 on page 1-2

Subnet Mask

Default Gateway

IP6 Enable

D20524-3 Rev.3.0 1-9


Power Restore Policy SetupPerform the steps in this procedure to define host’s Power Restore policy.

1. At the System Settings menu, use the arrow keys to highlight the Power menu item and press the Enter key.

2. On the screen that appears, use the arrow keys to highlight the line that says Power Restore Policy, and press the Enter key.

3. From the pop-up menu, select Always On and press the Enter key.

Note: If the IMM has not completed resetting (see the previous procedure), the Power Restore Policy will display ‘unknown’. If this happens, press the Esc key to go back one screen, wait a few moments and try again.

4. Press the Esc key twice to return to the System Configuration and Boot Management screen.

5. Use the arrow keys to highlight the line that says Save Settings, and press the Enter key.

6. Highlight the line that says Exit Setup, and press the Enter key.

7. You are asked to confirm that you want to exit the Setup Utility.

Setting Up Host 2The procedure for configuring Host 2 is identical to the preceding procedure for Host 1.

Host 2 Disk Array SetupTo setup the array on Host 2, move to the KVM for Host 2 and perform each of the steps in “Configuring the Disk Array” on page 1-3.

Host 2 Integrated Management Module (IMM) IP Address SetupTo setup the Integrated Management Module (IMM) on Host 2, move to the KVM on Host 2 and perform each of the steps in “Integrated Management Module (IMM) IP Address Setup” on page 1-8.

Host 2 Power Restore Policy SetupTo setup the Power Restore Policy on Host 2, move to the KVM on Host 2 and perform each of the steps in “Power Restore Policy Setup” on page 1-10.

1-10 D20524-3 Rev.3.0

C H A P T E R 2
Installing the Operating System
What’s in this chapterInstalling the Operating System Onto Host 1

Installing Host 1 Platform Support Software

Installing the Operating System Onto Host 2


This chapter provides instructions for installing the Linux operating system and the host support software onto each of the hosts in the system.


Perform the following to install the operating system. It is assumed that you have finished the procedures in Chapter 1.

1. Press the Power button to apply power to the system.

2. Insert the DVD for the Red Hat Linux 5.5 Installation.

3. The host computer boots from the DVD and gives the following prompt:

boot:

Note: After the prompt, you have one minute to enter the command given in step 4.

4. Type the following:

ha1

5. Press Enter.

Note: If, after pressing Enter, the system asks permission to create new partitions for sda, select yes.

The system may display the following message:

Partition table on device sda was unreadable. To create new partitions, it must be initialized causing the loss of ALL DATA on this drive.

This operation will override any previous installation choices about which drives to ignore

Would you like to initialize this drive, erasing ALL data?

If it does, use the tab key to select Yes, then press Enter to accept.

2-1


Results:

The install program formats all the file systems' partitions. Depending on the amount of disk space, this could take up to twenty minutes.

Once the formatting finishes, the install program installs the operating system and other materials from the DVD.

6. Press the eject button on the drive to eject the DVD.

7. Click Reboot icon.

Results: The system reboots.

The Linux installation on Host 1 is complete.

8. Proceed with, “Installing Host 1 Platform Support Software”.


This procedure consists of the following sub-procedures:

Note: You must perform these procedures in the sequence in which they are presented.

1. Install the base host support software.

2. Finish the host updates.

3. Install the NPS Host Health Drivers.

Installing the Base Host Support Software for Host 1Perform the following to begin installing the Linux updates and configuration files.

1. Logon as root.

Note: Use the password netezza.

2. Place the Netezza Host Platform Configuration DVD into the CD/DVD drive on Host 1.

3. Issue the following command to mount the DVD, and then press Enter:

mount /media/cdrom

4. Issue the following command, and then press Enter:

cd /media/cdrom/scripts


./swsupport -ha1 Result: The system asks for confirmation that this is Host 1.

6. Press Enter, When the system prompts, enter the IBM Netezza model number.

The console lists all possible model numbers, as the configuration script is used for all. It is crucial that you enter the correct model number. If you enter an incorrect model, you will need to repeat configuration of your IBM Netezza system.

2-2 D20524-3 Rev.3.0


Result: The system begins installing the Linux updates and additional system configu-ration files.

Note: If the system responds with a “model check” prompt, check that the model is correct and accept the default “yes.” If the system prompts you for a network shutdown, type “yes.”

7. When the system prompts as follows, enter and re-enter the hostname.

Note: Use the fully qualified hostname that IBM Netezza has provided.

Enter host name for Host 1: <nps-host-name>

Re-enter host name for Host 1: <nps-host-name>

8. When the system prompts, enter IP address information. A sample of the IP address portion of the script follows.

What follows is an example. Be sure to use your specific host IP address rather than the address given in the sample.

IP address is of form a.b.c.d. example: 172.16.0.1 (class B subnet)DO NOT type leading 0s such as 172.016.000.001

Enter host IP for host 1: 192.168.22.54<Enter>IP address is of form a.b.c.d. example: 172.16.0.1 (class B subnet)DO NOT type leading 0s such as 172.016.000.001

Confirm host IP for host 1: [192.168.22.54]<Enter>IP mask is of form a.b.c.d. example: 255.255.0.0 (class B subnet)DO NOT type leading 0s such as 255.255.000.000

Enter IP mask for host 1: 255.255.0.0<Enter>IP mask is of form a.b.c.d. example: 255.255.0.0 (class B subnet)DO NOT type leading 0s such as 255.255.000.000

Confirm IP mask for host 1: [255.255.0.0]<Enter>

Installation and configuration continues to completion. This may take several minutes.

When the system finishes, it displays the following messages:

Automatic install finished.Type cd, eject, and reboot for install changes to take effect.

9. As requested in the messages, enter the following.

cd <enter>

eject <enter>

reboot <enter>

Result: The system reboots.

D20524-3 Rev.3.0 2-3


Finishing the Host UpdatesPerform the following to finish installing the Linux updates and configuration files.

1. Login as root.


/nzlocal/scripts/cfgethnzm

Note: You may safely ignore any warning messages about bond0 being in use.

3. Insert the disk labeled RHEL5.5 Manufacturing Update into the drive and mount it:

mount /media/cdrom

4. Change directory to /media/cdrom/U5_manu_pkg_update

cd /media/cdrom/U5_manu_pkg_update

5. Run the script to update the packages:

./packageupdate.sh

6. Verify the install:

./test_pkg_upgrade.sh

7. Change directory and eject the disk:

cd <enter>

eject <enter>

8. Set the date and time (in 24-hour format):

date MMDDhhmmYYYY

where MM is the month, DD is the day, hh is the hour, mm is minutes and YYYY is year.

9. Insert the DVD labeled IBM Host Management into the CD/DVD drive and mount it:

mount /media/cdrom

10. Change directories:

cd /media/cdrom

11. Type the following command to begin the auto install. Installation typically finishes within 5 - 7 minutes; wait for installation to complete before proceeding to the next steps.

./ibmHealthInstall.sh

Note: You will receive an error message if the installer detects an unsupported version of the Linux kernel.

Result:The system installs the Host Management software and automatically reboots when it is finished.

12. Push the eject button on the front of the CD/DVD drive to eject the DVD.

13. When the system has rebooted, login as root.

2-4 D20524-3 Rev.3.0



Perform the following to install the operating system. It is assumed that you have finished the procedures in Chapter 1.

1. Press the Power button to apply power to the system.

2. Insert the DVD for the Red Hat Linux 5.5 Installation.

3. The host computer boots from the DVD and prompts:

boot:

4. Type the following:

ha2

5. Press Enter.

Note: If, after pressing Enter, the system asks permission to create new partitions for sda, select yes.

The system may display the following message:

Partition table on device sda was unreadable. To create new partitions, it must be initialized causing the loss of ALL DATA on this drive.

This operation will override any previous installation choices about which drives to ignore

Would you like to initialize this drive, erasing ALL data?

If it does, press Enter to accept.

Results:

The install program formats all the file systems' partitions. Depending on the amount of disk space, this could take up to twenty minutes.

Once the formatting finishes, the install program installs the operating system and other materials from the DVD.

6. Press the eject button on the drive to eject the DVD.

7. Click the Reboot icon.


8. Proceed with, “Installing Host 2 Platform Support Software”.

D20524-3 Rev.3.0 2-5




Note: You must perform these procedures in the sequence in which they are presented.

1. Install the base host support software.

2. Finish the host updates

3. Install the NPS Host Health Drivers.

Installing the Base Host Support Software for Host 2Perform the following to begin installing the Linux updates and configuration files.

1. Logon as root.

Note: Use the password netezza.

2. Place the Netezza Host Platform Configuration DVD into the CD/DVD drive on Host 2.

3. Issue the following command to mount the DVD, and then press Enter:

mount /media/cdrom


cd /media/cdrom/scripts


./swsupport -ha2 Result: The system asks for confirmation that this is Host 2.

6. Press Enter When the system prompts, enter the IBM Netezza model number.

The console lists all possible model numbers, as the configuration script is used for all. It is crucial that you enter the correct model number. If you enter an incorrect model, you will need to repeat configuration of your IBM Netezza system.

Result: The system installs Linux updates and additional system configuration files.

Note: If the system responds with a “model check” prompt, check that the model is correct and accept the default “yes.”

7. When the system prompts as follows, enter and re-enter the hostname.

Note: Use the fully qualified hostname that IBM Netezza has provided.

Enter host name for Host 2: <nps-host-name>

Re-enter host name for Host 2: <nps-host-name>

2-6 D20524-3 Rev.3.0


8. When the system prompts, enter IP address information. A sample of IP address por-tion of the script follows.

What follows is a sample. Be sure to use your specific host IP address rather than the address given in the sample.

IP address is of form a.b.c.d. example: 172.16.0.1 (class B subnet)DO NOT type leading 0s such as 172.016.000.001

Enter host IP for host 2: 192.168.22.54<Enter>IP address is of form a.b.c.d. example: 172.16.0.1 (class B subnet)DO NOT type leading 0s such as 172.016.000.001

Confirm host IP for host 2: [192.168.22.54]<Enter>IP mask is of form a.b.c.d. example: 255.255.0.0 (class B subnet)DO NOT type leading 0s such as 255.255.000.000

Enter IP mask for host 2: 255.255.0.0<Enter>IP mask is of form a.b.c.d. example: 255.255.0.0 (class B subnet)DO NOT type leading 0s such as 255.255.000.000

Confirm IP mask for host 2: [255.255.0.0]<Enter>

Installation continues to completion. This could take up to several minutes.

When the system finishes, it displays the following messages:

Automatic install finished.Type cd, eject, and reboot for install changes to take effect.

9. As requested in the messages, enter the following.

cd <enter>

eject <enter>

reboot <enter>


Finishing the Host UpdatesPerform the following to finish installing the Linux updates and configuration files.

1. Login as root.


/nzlocal/scripts/cfgethnzm

Note: You may safely ignore any warning messages about bond0 being in use.

3. Insert the disk labeled RHEL5.5 Manufacturing Update into the drive and mount it:

mount /media/cdrom

4. Change directory to /media/cdrom/U5_manu_pkg_update

cd /media/cdrom/U5_manu_pkg_update

5. Run the script to update the packages:

./packageupdate.sh

D20524-3 Rev.3.0 2-7


6. Verify the install:

./test_pkg_upgrade.sh

7. Change directory and eject the disk:

cd <enter>

eject <enter>

8. Set the date and time (in 24-hour format):

date MMDDhhmmYYYY

where MM is the month, DD is the day, hh is the hour, mm is minutes and YYYY is year.

9. Insert the DVD labeled IBM Host Management into the CD/DVD drive and mount the drive:

mount /media/cdrom


cd /media/cdrom

11. Type the following command to begin the auto install. Installation typically finishes within 5 - 7 minutes; wait for installation to complete before proceeding to the next steps.

./ibmHealthInstall.sh

Note: You will receive an error message if the installer detects an unsupported version of the Linux kernel.

Result:The system installs the Host Management software and automatically reboots when it is finished.


13. When the system has rebooted, login as root.

2-8 D20524-3 Rev.3.0

C H A P T E R 3
Configuring The PDUs, Switches, and the Cluster Manager
What’s in this chapterWhat You Need Before Starting

Configuring ssh for Each Host

Configuring the Power Distribution Units (PDUs)

Configuring the Chassis Components

Restoring Serial Port Settings

Checking Port and Switch Connections

Checking Power Connections and Firmware Revisions

Configuring the Cluster Manager for Hosts 1 and 2

The procedures in this section allow you to configure the PDUs, the chassis components and the rack-mounted ethernet switch. This part assumes that you have properly cabled the switch, the PDUs, and the hosts. There is a checking procedure later in this document that requires that the devices first be physically configured correctly. (See also, Checking Port and Switch Connections, for more information on checking the cabling.)

What You Need Before Starting

Before you start to configure the PDUs, the chassis components and the rack-mounted eth-ernet switch, you should have the following items and information at hand.

Table 3-1 lists the cables that are necessary to complete the configuration of the PDUs and switches.

Table 3-1: Cables

Description Part Number Comments

APC Serial Cable APC 940-0144 DB-9F to RJ12(RJ11) cable

BNT Serial Cable BNT BMM-00063-00 DB-9F to mini-USB

AMM Serial Cable

3-1


Configuring ssh for Each Host

Perform the following to configure ssh for each host. Before performing this procedure, ensure that you are logged on to both hosts.

1. From the Host 1 keyboard, enter the following and press Enter:

/nzlocal/scripts/sshconfigure -ha1

Result: The system responds with a prompt:

This script will configure ssh for Host 1 in an HA configuration. Continue?

This step configures ssh for Host 1 in an HA configuration.

2. Press Enter.

Note: Ignore warning messages.

Result: The system completes the script actions and displays:

Automatic install finished.

This step confirms that you wish to run the script for ssh configuration.

3. Switch to using the Host 2 keyboard.


/nzlocal/scripts/sshconfigure -ha2

Result: The system responds with a prompt:

This script will configure ssh for Host 2 in an HA configuration. Continue?

This step configures ssh for Host 2 in an HA configuration.

5. Press Enter.

Note: Ignore warning messages.

Result: The system completes the script actions and displays:

Automatic install finished.

This step confirms that you wish to run the script for ssh configuration.

6. Switch to using the Host 1 keyboard.

7. Test entries from the Host 1 keyboard.

ssh ha2

ssh ha1

exit

exit

Note that this step should work without error.

3-2 D20524-3 Rev.3.0

Install Firmware

Install Firmware

Perform the following steps to install the firmware:

Note: This procedure should be performed from Host 1 (ha1) only.

1. From Host 1, login as root

2. Insert the Netezza Firmware/Diagnostics/Tools DVD into the drive and mount it:

mount /media/cdrom

3. Change directory to /media/cdrom/firmware

cd /media/cdrom/firmware

4. Run the firmware installation script:

./install_firmware.pl -ignore

Note: This may take several minutes to complete.


cd


Configuring the Management Switch

Configuration of the rack-mounted management switch requires you to physically access the switch. During the configuration process you will be asked to connect a serial cable (IBM FRX0510) between the switch and the host, and then disconnect the cable when you are done.

1. Make sure that you are logged in as root

2. From the console connected to ha1, change directory:

cd /nzlocal/scripts/rpc

3. Run the script (use of serial port by minicom):

./siominicom.sh

4. Change directory:

cd /nzlocal/scripts

5. Type the following command to begin the switch configuration:

./netswmgtConfig.sh

Result:You are prompted for a password. Type admin and press the Enter key.

6. You are prompted to connect a serial cable between ha1 and the management switch.

The cable (BNT P/N: BMM-00063-00) should be connected from the serial port at the rear of ha1 to the mini-USB connector on the front of the G8000 management switch, Refer to Figure 3-1 for the location of the mini-USB connector on the G8000 switch.

D20524-3 Rev.3.0 3-3


Figure 3-1: Front of G8000 Management Switch

Note: The configuration proceeds with little indication that it is progressing. Be patient and wait for the command line prompt. This indicates that the script has completed.

Note: If the configuration should fail, you must first correct the problem and then reset the switch. This can be accomplished by simultaneously unplugging both power cords from their outlets on the PDU. IF the cords cannot be accessed, waiting approximately 10 minutes will cause the switch to timeout. Then you may return to step 5 and re-run the configuration script.

RS-232 port

3-4 D20524-3 Rev.3.0



This section provides details for configuring the Power Distribution Units (PDUs).

If you need to see the layout for physically connecting the switches, refer to Appendix A, “Reference Materials.”.

Note: You may see references to “RPCs” in configuration scripts and files. The term “RPC” is a holdover from earlier Netezza models and is functionally equivalent to the current PDU.

Before you begin the configuration procedures, you must ensure that the host and PDUs are connected properly to the rack-mounted switch, and that the PDUs are powered up. If you have not yet checked the physical connections, review the diagrams provided in Appendix A. Ports that are not included in the diagrams are empty and must remain empty in order for the configuration to complete successfully.

Updating the PDU FirmwareThe PDU firmware is automatically updated when the rpcconfigure script is executed in the following section. If the PDU firmware needs to be manually updated for any reason, refer to Appendix D, “PDU Firmware Update Procedure,” for instructions on updating the PDU firmware.

Configuring the PDUsWhen you use the rpcconfigure command to configure all power switches in a new system, in most cases you do not use any optional command switches.

Perform the following to configure one or more PDUs.

1. Unplug all APC PDU Ethernet cables. Connect each one immediately before you con-figure that switch. (Once you have configured a switch, leave it connected.)



3. From Host 1, run the script:

./rpcconfigure

Result: The system begins the configuration. Based on the model you are configuring, respond accordingly to the system prompts.

When you are asked for a password, type admin and press the Enter key.

Note: If you receive a message indicating that rpcmac.in was not found, press the Enter key to continue.

Note: Within the script that follows, as the system configures each PDU, you are asked to wait one minute for configuration to complete. In some cases, the script may time out, but you may need to wait up to ten minutes for the system to display the time-out signal. Once you receive the time-out signal, you need to restart the script.

D20524-3 Rev.3.0 3-5


Example: (actual output may differ)

The MODEL will be determined then the script will interactively guide the user to connect the host serial port to one of the RPC serial ports. The RPC will then be configured. Finally, the configuration will be verified via the network port.

Plan to use model number: P50. Okay? [yes] <Enter>

Please un-plug all Ethernet cables from all remote power switches.

Hit <enter> key when done. <Enter>

(Some console output has been removed for clarity)

Checking extra or missing connections. Please wait......

Finished RPC configure.

4. Unplug both ends of the APC serial cable.

Note: The APC Serial cable is an RJ11 to DB9 cable (21551).

Note: The -r option, when used with rpcconfigure, “resets” the PDU. It should rarely be necessary to use this command option. When you use the -r option with a PDU, all PDU settings are reset to factory settings.

Testing the PDUsPerform the following to test the PDUs.


./rpcconfigure -c -F -n

When you are prompted for a password, type admin and press the Enter key.

2. Check the console for errors.

Note: The script prompts to correct a problem if the PDU has been misconfigured. It errors out if the PDU cannot be reached.


/nzlocal/scripts/rpcverify

4. Check the console for errors.

3-6 D20524-3 Rev.3.0



The following sections describe the procedure for configuring the chassis components.

Component LocationsFigure 3-2 is a view of the the rear of a 1000-12 rack, showing the location of the Advanced Management Modules (AMM) and the SAS Connectivity Modules (SCM).

Figure 3-2: Rear of Rack

AMM 1

AMM 2

SCM 2

SCM 1

AMM 3

AMM 4

SCM 4

SCM 3

Chassis 1I/O Bay 4

Port 1

Chassis 1I/O Bay 3

Port 1

Chassis 1I/O Bay 4

Port 2

Chassis 1I/O Bay 3

Port 2

Chassis 1I/O Bay 4

Port 3

Chassis 1I/O Bay 3Port 31

Chassis 1I/O Bay 4

Port4

Chassis 1I/O Bay 3

Port 4

Chassis 2I/O Bay 4

Port 1

Chassis 2I/O Bay 3

Port 1

Chassis 2I/O Bay 4

Port 2

Chassis 2I/O Bay 3

Port 2

Chassis 2I/O Bay 4

Port 3

Chassis 2I/O Bay 3

Port 3

Chassis 2I/O Bay 4

Port 4

Chassis 2I/O Bay 3

Port 4

1 2 3 4 5 6 7 8

JBOD 1L

JBOD 2L

JBOD 3L

JBOD 4L

JBOD 5L

JBOD 6L

JBOD 7L

JBOD 8L

1 2 3 4 5 6 7 8

JBOD 1R

JBOD 2R

JBOD 3R

JBOD 4R

JBOD 5R

JBOD 6R

JBOD 7R

JBOD 8R

12

34

56

78

Sw

itch

RH

ost 1

RH

ost 2

R

12

34

56

78

KV

MS

witc

hL

Ho

st 1

LH

ost 2

L

1

2

3

4

SAS

1

2

3

4

SAS

1

2

3

4

SAS

1

2

3

4

SAS

D20524-3 Rev.3.0 3-7


Configuration ProcedureTo configure the AMMs and other chassis components, perform the following procedure.

Note: You will need a DB9-to-RJ45 serial cable. This will be connected from the DB9 serial port on the host to the RJ45 serial port on the AMM (the top-most port). Refer to Figure 3-2 on page 3-7 for the location of the IMMs.

1. Make sure that you are logged in as root


cd /nzlocal/scripts/spa

3. Type the following command to initialize the chassis components:

./spa_init.sh

Result:The script begins to initialize the components in the chassis.

Follow the instructions on the console. If you are asked for a username and password, use the following values:

username: USERID

password: PASSW0RD [Note the numeral 0 (zero)]

4. When initialization is finished (console displays the command line prompt), type the following command to begin the chassis configuration:

./spaconfigure.sh

Result:The configuration script begins to configure the components in the chassis. When the configuration process requires an action to be performed, you receive instructions on the console. If you are asked for a username and password, use the following values:

username: USERID

password: PASSW0RD [Note the numeral 0 (zero)]

Note: Logs can be found at /var/log/spaconfigure

Restoring Serial Port SettingsAfter you have configured the RPCs and switches, perform the following to restore the serial port settings.

1. From Host 1, change directories:


2. Run the script (use of serial port by modem):

./siomodem.sh

3-8 D20524-3 Rev.3.0



This procedure configures the cluster manager.

drbd_config.sh is used to initialize the shared storage space for the cluster.

The cluster manager has an IP alias address separate from the host IP address. By default, the service IP address is obtained by adding three to the value of the last octet in the address of the machine that is connected to the customer’s network (e.g. 192.168.21.178 becomes 192.168.21.181).

Note: The host IP address is taken from the system command hostname. The hostname command output matches entries in /etc/hosts file. If you change the host ip address, you must change the corresponding entries in the /etc/hosts.

Perform the following to configure the cluster manager for Hosts 1 and 2.

1. From the ha1 keyboard, change to the following directory:

cd /nzlocal/scripts

2. From ha1, type the following and press Enter:

./drbd_config.sh

You are warned about the consequences of this command and asked to confirm. You must type YES (all uppercase) in order for the command to be executed.

This command will erase all data on /nz and /export/home. It is intended for initial configu-ration only!

Note: You need only execute this command from ha1. The script configures the drbd software on both hosts.

Result: Partitions are formatted on ha1 and ha2. It may take several minutes for this step to complete.

D20524-3 Rev.3.0 3-9


Checking Port and Switch Connections

Use the procedures in this section to configure ports and check port and switch connections.

Configuring Switch Ports and Checking WiringPerform the following to configure switch ports and check wiring on Host 1.

1. From Host 1, change directories:

cd /nzlocal/scripts/diag_xs2

2. From Host 1, enter the following and press Enter:

./concheck.pl

Note: The script concheck.pl should only be run from Host 1.

Result: The system responds with instructions for checking port connections. Follow the instructions.

This step checks each port connection and responds with an OK as each connection is confirmed. This could take a significant amount of time.

Note: If the system displays the following message, you must first shut down cluster services using the service heartbeat stop command.

Cluster Services are Running and Must Be Stopped. Exiting

Checking Power Connections and Firmware Revisions

Do the following to check the power connections to all PDUs:


./RPCcheck.pl

Note: The script RPCcheck.pl should only be run from Host 1.

2. Follow the instructions the system displays for checking the port connections.

Note: Port connections are checked and ‘OK’ is printed as connections are confirmed.

If the script detects an error, it will pause and ask if you wish to continue. Note that the script will time out if you do not respond within 20 seconds.

3-10 D20524-3 Rev.3.0

C H A P T E R 4
Installing The NPS Software
What’s in this chapterInstalling NPS Software on Both Hosts

Configuring a Modem and Email Notification

Error Reporting Through Email

Install the NPS software using the procedures that follow.

Installing NPS Software on Both Hosts


Setting Up to Install the Software

Installing the Host Software

Setting Up to Install the SoftwareTo set-up for host software installation, perform the following procedure from Host 1.

1. Logon to Host 1 as root.

2. Change directory to /nzlocal/scripts:

cd /nzlocal/scripts

3. To put the host in non-heartbeat mode, type:

./nz.non-heartbeat.sh

When you are prompted to proceed, press the Enter key.

4. If you are installing from CD, place the Netezza Server Software CD into the CD-ROM drive and issue the mount command to mount the CD:

mount /media/cdrom

5. Change to the directory where the install kit resides using one of the following com-mands: /

If you downloaded the software: cd /tmp/x.x.x/pkg_kit

If you are using CDs: cd /media/cdrom

6. Run the unpack script using the following command:

./unpack

4-1


7. If you did not specify a directory using the install-dir command line argument, the script prompts you to specify a location for the upgrade files. The default is /nz.

The command creates the destination directory type.release in the specified location, and unpacks the software files in that directory. The script displays information about the installation and includes a progress bar.

Sample command output follows:

$ ./unpack

------------------------------------------------------------------....... Performance Server -- NPS Operating System 5.0.0 Copyright 2002-2008 ....... Corporation. All rights reserved.------------------------------------------------------------------

Validating package checksum ... ok

Where should the NPS Operating System be unpacked? [/nz]<Enter>

0% 25% 50% 75% 100%|||||||||||||||||||||||||||||||||||||||||||||||||||

You can check the system to prepare for an upgrade with:/nz/kit.5.0.0/sbin/nzupgrade check

You can start the upgrade (which also checks the system) with:/nz/kit.5.0.0/sbin/nzupgrade upgrade

Unpacking complete.

The script advises you to run nzupgrade check to confirm the operational status and overall health of the system. This is not necessary if this is a first time installation.

Note: Do not start the upgrade yet. This will be done in the following section.

8. Type cd

9. Issue the command eject.

Note: This command unmounts the CD-ROM drive and ejects the CD.

Remove the Netezza Server Software CD.

Installing the Host SoftwareYou use the nzupgrade command to install the NPS software.

To install the NPS software using the interactive process:

1. Change to the directory where the NPS software has been unpacked with a command similar to the following:

cd /nz/kit.x.x.x/sbin

2. Run the following command:

./nzupgrade -T hostprep upgrade

If you are prompted for an account to run the NPS software from, type nz.

Type y when you are prompted to continue.

4-2 D20524-3 Rev.3.0



This section describes how you configure a serial modem and set-up email notification.

Configuring a Serial ModemYou perform this procedure once for Host 1 and once for Host 2.

1. Login as root.

2. Issue the following command:

/nzlocal/scripts/configModem.sh

3. Once the command finishes executing, the modem is configured.

Note: The modem might not answer incoming calls until the system is rebooted.

Error Reporting Through EmailThe subsections that follow describe how to set-up email error reporting.

Configuring IMM Email NotificationTo configure the IBM IMM (Integrated Management Module) to send email alerts, refer to Appendix C, “IMM Configuration.”

Cluster ManagerEdit or create the file /nzlocal/maillist on both hosts so that they read as follows (only add bold lines). Note that you can overwrite this read-only file if you are logged on as root.

#

#Email notification list for the cluster manager problems

#

#Enter email addresses of mail recipients under the TO entry, one to a line

#

#Enter email address of from email address (if a non-default is desired)

#under the FROM entry

#

TO:

[email protected]

[email protected]

FROM:

[email protected]

D20524-3 Rev.3.0 4-3


4-4 D20524-3 Rev.3.0

C H A P T E R 5
Initializing and Testing The System Fabric
What’s in this chapterUpdating System Firmware

Running Diagnostic Suites

Testing the System Fabric and Shared Disks

Bringing Up the Cluster

Perform the procedures in this section to update the system firmaware and to test both hosts as master of system fabric and shared disks.

Updating System Firmware

Perform the steps in the following sections to update the system firmware.

Note: Make sure that you are logged in as root

If the system is not in non-heartbeat mode, type the following from the Host 1 keyboard:

/nzlocal/scripts/nz.non-heartbeat.sh

Configure the heartbeatFrom ha1, type the following commands, pressing Enter after each one:

cd /nzlocal/scripts

./heartbeat_config.sh

You are warned about the consequences of this command and asked to confirm. You must type YES (all uppercase) in order for the command to be executed.

Note: You need only execute this command from ha1. The script configures the heartbeat software on both hosts.

Update the Management and Fabric Switch FirmwareFollow these steps to update the management switch firmware:

1. Change directory to /opt/Netezza/FW/PSeries/Rackswitch/G8000:

cd /opt/Netezza/FW/PSeries/Rackswitch/G8000

2. To update the firmware on the management switch, run the following command:

./bnt_upgrade.pl

5-1


Install Database Accelerator BoardsAttach the Database Accelerator boards (Baleen boards) to the S-Blades.

Update the Chassis FirmwareFollow these steps to update the chassis firmware:

1. Change directory to /opt/ibm/rapidflash/scripts/

cd /opt/ibm/rapidflash/scripts/

2. To start the firmware update, type:

./update

Check the Firmware RevisionsFollow these steps to check the firmware revisions:

1. Logon as root

2. Use sys-revcheck to check the firmware revisions:

a. Change directory to /opt/Netezza/FW/PSeries/sysrev-check/SysRevCheck

cd /opt/Netezza/FW/PSeries/sysrev-check/SysRevCheck

b. Run the command:

./sysrev_check.pl

Review the information on the screen to insure that the firmware revisions are updated. You should see a line similar to the following:

---------------------FINAL STATUS----------------------------

Final status of test run [PASS]

5-2 D20524-3 Rev.3.0

Updating System Firmware

Run nzupgradeRun the nzupgrade command:


cd /nz/kit.x.x.x/sbin


./nzupgrade upgrade


Type y when you are prompted to continue.

Verify that the system returns a message indicating that the upgrade was successful. If you receive a message that says that the upgrade was unsuccessful, you must correct the problem before the installation can continue. Contact Netezza support if necessary.

Run the Power Cycle TestRun the power cycle test to confirm that all S-blades boot up:

1. Insert the Netezza Firmware/Diagnostics/Tools DVD into the drive and mount it:

mount /media/cdrom

2. Change to the /diags/system_diags directory:

cd /media/cdrom/diags/system_diags

3. Copy the tarball to the /tmp directory:

cp power_cycle_x.x.x.x.tar /tmp/

4. Change to the /tmp directory:

cd /tmp

5. Untar the tarball:

ctar xvof power_cycle_x.x.x.x.tar

6. Change to the /power_cycle directory:

cd power_cycle

7. Run the power_cycle script:

./power_cycle.pl

Start the bootp ServerThe bootp server must be running for some of the subsequent procedures.

1. Open another process window and issue the following command to make sure that the bootp server is started:

cd /nz/kit.x.x.x/sbin/

./bootpsrv

Note: Leave this process running until you are instructed otherwise.

2. Return to the original process window and verify that the S-blades are reachable:

/nzlocal/scripts/pingspu.sh

D20524-3 Rev.3.0 5-3


Set the Enclosure IDsAs the root user, run the following command to set the enclosure IDs

/nz/kit/bin/adm/encl_setIds

Check the log to be sure that this step was successful.

Note: The logfile for this operation can be found at: /tmp/iocheck

Update the ESM FirmwareFollow these steps to update the ESM firmware:

1. Change to /opt/Netezza/FW/PSeries/Enclosure/esm_firmware_updater:

cd /opt/Netezza/FW/PSeries/Enclosure/esm_firmware_updater

2. Run the firmware updater:

./encl_update.pl -ignore

Erase the HBA BIOSFollow these steps to erase the HBA BIOS:

1. Make sure you are logged into host 1 as root .

2. Change to the directory that contains the HBA BIOS tool:

cd /opt/Netezza/FW/PSeries/spa/blade/hba_bios_tool

3. Run the HBA erase script:

./hba_tool.pl

Update the Disk FirmwareFollow these steps to update the disk firmware:

1. Change directory to /opt/Netezza/FW/PSeries/Disks/disk_firmware:

cd /opt/Netezza/FW/PSeries/Disks/disk_firmware

2. Run the firmware updater:

./disk_firmware_updater.pl

5-4 D20524-3 Rev.3.0



Perform the steps in the following sections to run the various diagnostic tests.

Run the Disk SmartSuite DiagnosticsFollow these steps to run the SmartSuite diagnostics:

1. Copy the diagnostics tarball from the DVD to the /tmp directory:

cp /media/cdrom/diags/diskdiags/smartSuite_x.x.x.tar /tmp

2. Change directory to /tmp:

cd /tmp


tar xvf smartSuite_x.x.x.tar

4. Change directory to /tmp/smartSuite:

cd /tmp/smartSuite

5. Run the diagnostic suite :

./smartSuite.pl

Stop the bootp ServerReturn to the other process window and type Ctrl-C to stop the bootp server. You may close this process window.

Run the S-Blade DiagnosticsFollow these steps to run the S-Blade diagnostics:

1. Return to the original process window and change directory to the /media/cdrom/diags/xdiags directory:

cd /media/cdrom/diags/xdiags/

2. Run the installation script:

./install.sh

3. Change directory to /nz/diagskit/rel_x_x:

cd /nz/diagskit/rel_x_x

4. Get the diagnostic tools help screen:

./spugang.pl –h

5. Run the diagnostic suite:

./spugang.pl

6. Exit when all SPUs report their status as PASSED:

<Ctrl-C>

Note: If the spugang.pl script has been run, you must go through the complete pro-cedure in “Start the System” on page 5-6 before you can go back and re-run any of the scripts on page 5-1 through page 5-5.

D20524-3 Rev.3.0 5-5


Start the SystemFollow these steps to start the system:

1. Logon as nz using the password nz.

2. Initialize the system:

nzinitsystem -reinit

3. Start the system:

nzstart -newSystem -v

Note: This may take up to 10 minutes to complete.

Note: If nzstart fails, debug and correct the problem. Then perform the following step before you attempt to restart the system with the above nzstart command.

Initialize the system:


This may take up to 10 minutes to complete.

4. Wait for the system software to start.

Type nzstate to determine if the system software has started yet.

5. Logon as root.

Check Firmware RevisionsCheck the firmware revisions again. This is necessary because some components can only be checked with the system software started.

1. Logon as root using the password netezza.

2. Change directory to /opt/Netezza/FW/PSeries/sysrev-check/SysRevCheck

cd /opt/Netezza/FW/PSeries/sysrev-check/SysRevCheck

3. Run the command:

./sysrev_check.pl

You should review the information on the screen to insure that the firmware revisions are updated.

Run the Physical Port Evaluation (aBurn) CheckFollow these steps to run the aBurn physical port evaluation test:

1. Login as root

2. Copy the tarball from the DVD to the /tmp directory:

cp /media/cdrom/diags/diskdiags/aBurnV2_x.x.x.tar /tmp

3. Become the nz user:

su - nz


cd /tmp

5-6 D20524-3 Rev.3.0


5. Untar the tarball that you copied in step 2:

tar xvof aBurnV2_x.x.x.tar

6. Change directory to /aBurnV2:

cd aBurnV2

7. Run the diagnostic:

./run_aburn.pl

Result: The diagnostic utility creates a logfile in the /tmp/aBurnV2 directory with a name similar to:

aBurn_log_file_Apr_5_11:38:46_2010.txt

8. Open this logfile in a text editor and examine the contents for errors.

9. Type the following command:

nzstop

Run the testSuite diagnosticsFollow these steps to run the testSuite diagnostics:

1. Make sure that the Netezza Firmware/Diagnostics/Tools DVD is in the drive and mounted.

2. Copy the diagnostics tarball from the DVD to the /tmp directory:

cp /media/cdrom/diags/diskdiags/testSuite_x.x.x.tar /tmp


cd /tmp


tar xvf testSuite_x.x.x.tar

5. Change directory to /testSuite:

cd ./testSuite

6. Run the diagnostics :

./testSuite.pl

Reinitialize the SystemFollow these steps to reinitialize the system:

1. Logon as nz using the password nz.

2. Initialize the system:



3. Start the system:

nzstart -newSystem -v


D20524-3 Rev.3.0 5-7


Testing the System Fabric and Shared Disks

You test Host 1 first, followed by a test of Host 2.

Note: If, during the system fabric and shared disk tests, you receive an error message indi-cating that /nz could not be unmounted, you must kill the process that is holding the /nz process and then retry the command that failed.

Testing Host 1 as Master of System Fabric and Shared DisksPerform the following to test Host 1 as master of system fabric and shared disks.

1. When the system software has started, type the following command and press Enter:

nzstop

2. Login as root.

3. From Host 1 enter the following and press Enter.

/nzlocal/scripts/nz.heartbeat.sh

This step removes Host 1 as the master of the internal fabric and shared disks.

4. Press Enter to proceed.

Result: The system displays, "Ready to use NPS in a cluster environment"

Testing Host 2 as Master of System Fabric and Shared DisksPerform the following to test Host 2 as master of system fabric and shared disks.

1. From Host 2, enter the following and press Enter.

/nzlocal/scripts/nz.non-heartbeat.sh

Result: Press enter at the prompt that asks if you wish to proceed.

This step makes Host 2 the master of the internal fabric and shared disks.

2. Logon as nz

3. Start the system software.

nzstart

4. Verify that the system is online:

nzstate

5. Stop the system software:

nzstop

6. To return to root, type:

exit


/nzlocal/scripts/nz.heartbeat.sh

This step removes Host 2 as the master of the internal fabric and shared disks.

8. The system then asks if you wish to proceed. Press Enter when you receive this prompt:

To proceed, please hit enter... <Enter>

5-8 D20524-3 Rev.3.0



This section discusses what to do to start the system software.


service heartbeat start

This step starts the cluster manager on Host 1.


ssh ha2 'service heartbeat start'



crm_mon -i5

Result: When the cluster manager comes up and is ready, status appears as follows.

Node: nps61074 (e890696b-ab7b-42c0-9e91-4c1cdacbe3f9): onlineNode: nps61068 (72043b2e-9217-4666-be6f-79923aef2958): online

Resource Group: npsdrbd_exphome_device(heartbeat:drbddisk): Started nps61074drbd_nz_device(heartbeat:drbddisk): Started nps61074exphome_filesystem(heartbeat::ocf:Filesystem): Started nps61074nz_filesystem (heartbeat::ocf:Filesystem): Started nps61074fabric_ip (heartbeat::ocf:IPaddr): Started nps61074wall_ip (heartbeat::ocf:IPaddr): Started nps61074nzinit (lsb:nzinit): Stopped (unmanaged) nps61074

fencing_route_to_ha1(stonith:apcmaster): Started nps61074fencing_route_to_ha2(stonith:apcmaster): Started nps61068

This command verifies that the cluster manager comes up.

4. From Host 1, press CTRL+C to break out of crm_mon.

5. Perform the following to test the cluster managers.

a. From the Host 1 keyboard, enter the following and press Enter:

stonith -t apcmastersnmp ipaddr=10.0.128.31 port=161 community=private -T reset <hostname of ha2>

Note: Wait for Host 2 to reboot before continuing.

This step powers Host 2 off and then on. It also verifies that cluster communication is valid and that the power control software is in place.

b. Switch to using the Host 2 keyboard.

c. From Host 2, enter the following and press Enter:

stonith -t apcmastersnmp ipaddr=10.0.128.31 port=161 community=private -T reset <hostname of ha1>

Note: Wait for Host 1 to reboot before continuing.

This step powers Host 1 off and then on. It also verifies that cluster communication is valid and that the power control software is in place.

D20524-3 Rev.3.0 5-9


6. Type:

crm_mon -i5

and wait until the cluster manager is up and both hosts are online. (Refer to the exam-ple in step 3)

7. Type the following command from either host to make Heartbeat aware of the newly installed system software:

/nzlocal/scripts/heartbeat_admin.sh --enable-nps

At this point, heartbeat will attempt to bring the system software up. Confirm that all resources start - it may take a few minutes:

crm_mon -i5

Press CTRL-C to return to a command prompt.

8. Verify that the system is online.

9. To relocate the active system software, wait until the system is online and then, from ha1, enter the following command and press Enter:

/nzlocal/scripts/heartbeat_admin.sh --migrate

Result: The system displays:

"Migrating the NPS resource group from <current active host> to <current standby host>....."

and then, after a few minutes:

"done."

10. You have completed the configuration procedures.

5-10 D20524-3 Rev.3.0

A P P E N D I X A
Reference Materials
What’s in this appendixSystem Reference

Shutting Down and Bringing Up a IBM Netezza 1000-Series System

This appendix provides reference material specific to each model in the IBM Netezza 1000-Series product line.

The material in this appendix is organized by model number, with each model having its own section. Within each section you will find information on:

Connections from the host servers to the ethernet switch

Port assignments for the rack-mounted ethernet switch

SAS cabling between the disk arrays and the chassis-mounted SAS Connectivity Mod-ules (SCM)

Power cabling between the APC power distribution units and the other components in the system

In addition, a section is included that contains instructions on bringing up and gracefully shutting down an IBM Netezza 1000-Series system.

A-1


System Reference

The following sections provide reference information for the IBM Netezza 1000-Series models. It includes network and power connections between the major components in the system.

Note: The information in this section pertains to the x3650 M3 hosts that began being used in systems early in 2011. Refer to an earlier revision of this manual for information on the previous generation of x3650 hosts.

IBM x3650 M3 Host ConnectionsTable A-1 lists connections to the IBM hosts in the 1000-3, 1000-6 and 1000-12 models.

Figure A-1: Rear of Host (x3650 M3)

Table A-1: IBM x3650 M3 Host Network Connections

Host Port Destination Port (Host 1) Destination Port (Host 2)

PCI Slot 1 Port 1 Chassis 1, I/O Bay 1, Port 1 Chassis 1, I/O Bay 2, Port 1

Port 2 — —

PCI Slot 4 Port 1 Enet Switch, Port 3 Enet Switch, Port 4

Port 2 Enet Switch, Port 27 Enet Switch, Port 28

Port 3 — —

Port 4 — —

LOM Port 1 External Network External Network

LOM Port 2 Host 2, LOM Port 2 Host 1, LOM Port 2

LOM Port 3 Host 2, LOM Port 3 Host 1, LOM Port 3

LOM Port 4 — —

USB1 KVM, Port 1 KVM, Port 2

PCI Slot 4

LOM 4

LOM 3

LOM 2

LOM 1

System Management(IMM)

PCI Slot 1Port 2

Port 2

Port 4

Port 1Port 1

Port 3

USB 1Video Serial

A-2 D20524-3 Rev.3.0

System Reference

Ethernet Switch ConnectionsFigure A-2 shows the port assignments for connections to the rack-mounted ethernet switch in the 1000-3 system.

Figure A-2: Model 1000-3 Ethernet Switch Port Assignments

Figure A-3 shows the port assignments for connections to the rack-mounted ethernet switch in the 1000-6 system.


Figure A-4 shows the port assignments for connections to the rack-mounted ethernet switch in the 1000-12 system.


1

2

3

4

5

6

7

8

9

10

RPC Left RPC Right

Host 1, Slot 4, Port 1 Host 1, Slot 4, Port 2

Chassis 1, AMM 1 Chassis 1, AMM 2

Host 2, Slot 4, Port 1


Service 10.0.131.253/255.255.252.0

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

1

2

3

4

5

6

7

8

9

10

RPC LL 1 RPC LR 1



RPC UL 1

RPC UR 1



11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

Service 10.0.131.253/255.255.252.0

1

2

3

4

5

6

7

8

9

10

RPC LL 1 RPC LR 1



RPC UL 1

RPC UR 1Host 2, Slot 4, Port 1

Host 2, Slot 4, Port 2Chassis 2, AMM 1

Chassis 2, AMM 2

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

Service 10.0.131.253/255.255.252.0

D20524-3 Rev.3.0 A-3


PDU Power Connections

Model 1000-3There is only one type of Power Distribution Unit (PDU) in the 1000-3 cabinet. These con-trolled PDUs are mounted on either side of the cabinet. They control power to the disk arrays, the system chassis, the hosts, the kvm, and the management switch. The right PDU controls power to the power supplies on the right side (as viewed from rear) of each compo-nent, while the left PDU controls the power supplies on the left side of each component.

Power connections for controlled PDU:

B1

B1

B2

B2

12

34

56

7

12

34

56

7

91

011

12

13

14

15

91

011

12

13

14

15

17

18

19

20

21

22

23

17

18

19

20

21

22

23

8 8

16

16

24

24

Seria

l Port

Reset

—O

K—

Wa

rnin

g

—O

ve

rloa

dT

OTA

L

B1

B2

Amps

Amps

Sta

tus

Lin

k - R

x/T

x10/1

00

Pre

ss to

sele

ct b

ank.

Pre

ss a

nd h

old

to in

vert d

ispla

y

Seria

l Port

Reset

—O

K—

Wa

rnin

g

—O

ve

rloa

dT

OTA

L

B1

B2

Amps

Amps

Sta

tus

Lin

k - R

x/T

x10/1

00

Pre

ss to

sele

ct b

ank.

Pre

ss a

nd h

old

to in

vert d

ispla

y

Seria

l Port

Re

se

t

—O

K—

Warn

ing

—O

verlo

ad

TO

TA

L

B1

B2

Amps

Amps

Sta

tus

Lin

k - R

x/T

x10/1

00

Pre

ss to

se

lect b

an

k.

Pre

ss a

nd

ho

ldto

inve

rt dis

pla

y

Chassis 1, Fan L Chassis 1, Fan RSerial

Port

Chassis 1, PS 3/4 L Chassis 1, PS 3/4 R

Chassis 1, PS 1/2 L Chassis 1, PS 1/2 R

Host 1, Left PS Host 1, Right PS

JBOD 1, Left PS JBOD 1, Right PS

Host 2, Left PS Host 2, Right PS

JBOD 2, Left PS JBOD 2, Right PS

KVMSwitch, Left PS Switch, Right PS

A-4 D20524-3 Rev.3.0

System Reference

Model 1000-6 There are three sets of Power Distribution Units (PDUs) in the cabinet. They are:

Upper PDUs - These are at the top of the cabinet, directly above the disk arrays. They are mounted horizontally, one above the other.

Lower PDUs - The lower PDUs are mounted vertically on either side of the rack, approx-imately midway between the top and bottom of the rack.

Note: Although these PDUs are located in the middle of the rack, they are referred to as the lower PDUs. This is an important distinction and should be kept in mind when the PDUs are configured with the rpcconfigure script.

Uncontrolled PDUs - The PDUs located lowest in the rack are not under control of the host computers. They are mounted vertically on either side of the rack.

The following sections describe the connections to each PDU in the rack.

Upper PDUs The PDUs in the upper part of the cabinet control power to the disk arrays. The top PDU controls power to the right side (as viewed from rear) of each disk array, while the bottom PDU controls the power supplies on the left side of each disk array.

Power connections for upper PDUs:

1 2 3 4 5 6 7 8

JBOD 1L

JBOD 2L

JBOD 3L

JBOD 4L

1 2 3 4 5 6 7 8

JBOD 1R

JBOD 2R

JBOD 3R

JBOD 4R

Ethernet SwitchPort 26


D20524-3 Rev.3.0 A-5


Lower PDUs The lower PDUs (located in the middle of the rack) provide remotely switched power to the host computers and the KVM.

Power connections for lower PDUs:1

23

45

67

8

Ho

st 1

RH

ost 2

R

12

34

56

78

KV

MH

ost 1

LH

ost 2

L



A-6 D20524-3 Rev.3.0

System Reference

Uncontrolled PDUs The uncontrolled PDUs are mounted vertically at the bottom of the rack. These PDUs are not remotely switched, simply distributing power to the upper and lower remotely switched PDUs, as well as the chassis.

Power connections for uncontrolled PDUs:

Chassis 11/2 L

RPCLR

RPCLL

Chassis 13/4 R

Chassis 13/4 L

Chassis 11/2 R

Mgmt Sw 1R

RPCUR

RPCUL

Chassis 1Fan R

Chassis 1Fan L

Mgmt Sw 1L

Note:

These outlets are locatedon the opposite side of thePDU.

D20524-3 Rev.3.0 A-7


Model 1000-12There are three sets of Power Distribution Units (PDUs) in the cabinet. They are:

Upper PDUs - These are at the top of the cabinet, directly above the disk arrays. They are mounted horizontally, one above the other.

Lower PDUs - The lower PDUs are mounted vertically on either side of the rack, approx-imately midway between the top and bottom of the rack.

Note: Although these PDUs are located in the middle of the rack, they are referred to as the lower PDUs. This is an important distinction and should be kept in mind when the PDUs are configured with the rpcconfigure script.

Bottom/Main/Uncontrolled PDUs - The PDUs located lowest in the rack are not under control of the host computers. They are mounted vertically on either side of the rack.

The following sections describe the connections to each PDU in the rack.

Upper PDUs The PDUs in the upper part of the cabinet control power to the disk arrays. The top PDU controls power to the right side (as viewed from rear) of each disk array, while the bottom PDU controls the power supplies on the left side of each disk array.

Power connections for upper PDUs:

1 2 3 4 5 6 7 8

JBOD 1L

JBOD 2L

JBOD 3L

JBOD 4L

JBOD 5L

JBOD 6L

JBOD 7L

JBOD 8L

1 2 3 4 5 6 7 8

JBOD 1R

JBOD 2R

JBOD 3R

JBOD 4R

JBOD 5R

JBOD 6R

JBOD 7R

JBOD 8R



A-8 D20524-3 Rev.3.0

System Reference

Lower PDUs The lower PDUs (located in the middle of the rack) provide remotely switched power to the host computers, the rack-mounted ethernet switch and the KVM.

Power connections for lower PDUs:

12

34

56

78

Ho

st 1

RH

ost 2

R

12

34

56

78

KV

MH

ost 1

LH

ost 2

L



D20524-3 Rev.3.0 A-9


Uncontrolled PDUs The uncontrolled PDUs are mounted vertically at the bottom of the rack. These PDUs are not remotely switched, simply distributing power to the upper and lower remotely switched PDUs, as well as the chassis.

Power connections for uncontrolled PDUs:

Chassis 21/2 L

Chassis 11/2 L

RPCLR

RPCLL

Chassis 23/4 R

Chassis 13/4 R

Chassis 23/4 L

Chassis 13/4 L

Chassis 21/2 R

Chassis 11/2 R

Mgmt Sw 1R

RPCUR

RPCUL

Chassis 2Fan R

Chassis 1Fan R

Chassis 2Fan L

Chassis 1Fan L

Mgmt Sw 1L

Note:

These outlets are locatedon the opposite side of thePDU.

A-10 D20524-3 Rev.3.0

System Reference

SAS ConnectionsThe following diagram shows the connections between the JBOD chassis and the corre-ponding ports in the I/O bays of the system chassis.

Model JBODs in System

1000-3 JBOD 1 and JBOD 2

1000- 6 JBOD 1 through JBOD 4

1000-12 JBOD 1 through JBOD 8

















1

2

3

4

5

6

7

8

1000-3

1000-6

1000-1

2

D20524-3 Rev.3.0 A-11



The following sections describe the procedure for shutting down and bringing up a IBM Netezza 1000-Series system.

Shutting Down a IBM Netezza 1000-Series SystemPerform the following procedure to shut down a IBM Netezza 1000-Series system.

1. Identify the active host in the cluster, which is the host where the nps resource group is running:

[root@nzhost1 ~]# crm_resource -r nps -W

crm_resource[5377]: 2009/06/07_10:13:12 info: Invoked: crm_resource -r nps -Wresource nps is running on: nzhost1

2. Log in as root to the standby host (nzhost2 in this example) and run the following com-mand to stop heartbeat:

[root@nzhost2 ~]# service heartbeat stop

3. Log in as root to the active host (nzhost1 in this example) and run the following com-mand to stop heartbeat:

[root@nzhost1 ~]# service heartbeat stop

4. Log in as root to the standby host (nzhost2 in this example) and run the following com-mand to shut down the host:

[root@nzhost2 ~]# shutdown -h now

5. Log in as root to the active host and run the following command to shut down the host:

[root@nzhost1 ~]# shutdown -h now

6. Wait until you see the power lights on both hosts shut off.

7. Do one of the following steps depending upon which model you have:

For a 1000-6 or a 1000-12, pull out the 9 breaker pins on both the left and right lower PDUs. (Repeat these steps for each rack of the system.)

For a 1000-3 model, use a small tool such as a pocket screwdriver to open the two breaker switches on both the left and right PDUs.

8. Disconnect the main input power cables (two per rack) from the data center power drops. (As a best practice, do not disconnect the power cords from the plug/connector on the PDUs in the rack; instead, disconnect them from the power drops outside the rack.)

Bringing Up a IBM Netezza 1000-Series SystemPerform the following to bring a IBM Netezza 1000-Series system up.

1. Make sure that the two main power cables are connected to the data center drops; there are two power cables for each rack of the system.

A-12 D20524-3 Rev.3.0


2. Do one of the following steps depending upon which model you have:

For a 1000-6 or a 1000-12, push in the 9 breaker pins on both the left and right lower PDUs. (Repeat these steps for each rack of the system.)

For a 1000-3 model, close the two breaker switches on both the left and right PDUs.

3. Press the power button on both host servers and wait for the servers to start. This pro-cess can take a few minutes.

4. Log in as root to one of the hosts and confirm that the NPS software has started as follows:

a. Run the crm_mon command to obtain the cluster status:

[root@nzhost1 ~]# crm_mon -i5============Last updated: Tue Jun 2 11:46:43 2009Current DC: nzhost1 (key)2 Nodes configured.3 Resources configured.============Node: nzhost1 (key): onlineNode: nzhost2 (key): onlineResource Group: nps

drbd_exphome_device (heartbeat:drbddisk): Started nzhost1drbd_nz_device (heartbeat:drbddisk): Started nzhost1exphome_filesystem (heartbeat::ocf:Filesystem): Started nzhost1nz_filesystem (heartbeat::ocf:Filesystem): Started nzhost1fabric_ip (heartbeat::ocf:IPaddr): Started nzhost1wall_ip (heartbeat::ocf:IPaddr): Started nzhost1nz_dnsmasq (lsb:nz_dnsmasq): Started nzhost1nzinit (lsb:nzinit): Started nzhost1

fencing_route_to_ha1 (stonith:apcmaster): Started nzhost2fencing_route_to_ha2 (stonith:apcmaster): Started nzhost1

b. Identify the active host in the cluster, which is the host where the nps resource group is running:

[root@nzhost1 ~]# crm_resource -r nps -W

crm_resource[5377]: 2009/06/01_10:13:12 info: Invoked: crm_resource -r nps -Wresource nps is running on: nzhost1

c. Log in as nz and verify that the server is online:

[nz@nzhost1 ~]$ nzstateSystem state is 'Online'.

D20524-3 Rev.3.0 A-13


A-14 D20524-3 Rev.3.0

A P P E N D I X B
Configurable IP
What’s in this appendixIP Configuration Procedure for Internal Components

IP Configuration Procedure for External Network Connections

This chapter explains how to configure the base IP address of the 1000-Series appliance’s internal network.

Hardware and Media Needed

The following list includes the items needed to complete the configuration procedures in this appendix:

Ethernet Cable - RJ-45 to RJ-45

IP Configuration Procedure for Internal Components

The IP configuration procedure changes the IP address of each addressable component that comprise an IBM Netezza 1000-Series appliance.

The system’s internal network uses a default base IP address of 10.0.x.x. If this conflicts with an IP address already in use at your site, use the following procedure to change the system’s internal base IP address.

Before You StartBefore you begin the internal IP configuration, you must ensure that the system is prepared:

1. (This step is optional) Ensure that all communication paths are intact.

a. Logon as root.

b. Check the cluster state:

crm_mon -i5

(described in “Checking Port and Switch Connections” on page 3-10)

If both hosts are online and all services in the nps resource group are started, then the cluster is up.

If the cluster is down, go directly to step f.

If the cluster is up, shutdown the standby node first.

B-1


c. Determine the active and standby nodes:

/usr/sbin/crm_resource -r nps -W

The active node is listed, so the standby node is the one that is not listed

d. To shutdown the standby node, go to the KVM on the standby node and type:

/sbin/service heartbeat stop

Wait until the standby node is down before proceeding.

Note: If you wish to monitor the state of the nodes, you can open another window (ALT-F2) and run the command crm_mon -i5.

e. When the standby node is down, go to the KVM on the active node and type:


Note: Wait until the active node is down before proceeding. Use separate terminal instance with the crm_mon -i5 command to monitor the state of the active node.

f. From Host 1, change directories:

cd /nzlocal/scripts/diag_xs2

g. Type the following:

./concheck.pl

Note: The script concheck.pl should only be run from Host 1.

Result: This step checks each port connection and responds with a PASS or FAIL as each connection is confirmed.

If an error is encountered, the system responds with instructions for checking port connections. Follow the instructions.

h. Upon successful completion, restart the cluster services.

From the Host 1 keyboard, type the following and press Enterservice heartbeat start


i. From the Host 1 keyboard, type the following and press Enter:



Note: This may take up to three minutes to complete.

2. Verify that both nodes (hosts) are online. From Host 1, type the following and press Enter:

crm_mon -i5

B-2 D20524-3 Rev.3.0


Result: When the cluster manager comes up and is ready, status appears as follows: Refresh in 3s...

============Last updated: Fri Aug 6 15:37:08 2010Current DC: p100-9e-d (56ff70b1-446f-4699-b45a-174482727bb6)2 Nodes configured.3 Resources configured.============

Node: p100-10e-d (56ff70b1-446f-4699-b45a-174482727bb6): onlineNode: p100-9e-d (ee2bdb46-0d6c-427c-8b2e-0c9505643be3): online

Resource Group: npsdrbd_exphome_device(heartbeat:drbddisk): Started p100-9e-d

drbd_nz_device (heartbeat:drbddisk): Started p100-9e-dexphome_filesystem(heartbeat::ocf:Filesystem):Started p100-9e-dnz_filesystem (heartbeat::ocf:Filesystem): Started p100-9e-dfabric_ip(heartbeat::ocf:IPaddr): Started p100-9e-dwall_ip(heartbeat::ocf:IPaddr): Started p100-9e-dnz_dnsmasq(lsb:nz_dnsmasq): Started p100-9e-dnzinit (lsb:nzinit): Started p100-9e-d

fencing_route_to_ha1 (stonith:apcmastersnmp): Started p100-10e-dfencing_route_to_ha2 (stonith:apcmastersnmp): Started p100-9e-dThis command verifies that the cluster manager comes up.

3. From Host 1, press CTRL+C to break out of crm_mon.

4. Ensure that Host 1 is the active host. Type the command:

/usr/sbin/crm_resource -r nps -W

The output of the command is:

running on <hostname>

If HA1 is not the active host, migrate the system as instructed in step 9 on page 5-10.

5. Physically disconnect HA1 from the external network.

This ensures that no other users can login during the configuration process.

6. Type the command:

who

to make sure that there are no instances of the user nz logged in.

If the user nz is logged in, the procedure will fail.

7. You must edit the file that contains references to external nameservers.

a. From either host, type the command:

service nzresolv update

D20524-3 Rev.3.0 B-3


b. An editor opens the file /etc/resolv.conf. Comment out each line that references an external nameserver by placing a # symbol at the beginning of the line.

For example:

search company.comsearch domain.comnameserver 192.168.0.1nameserver 192.168.0.2

becomes:

search company.comsearch domain.com#nameserver 192.168.0.1#nameserver 192.168.0.2

c. Save and close the file.

The file is modified for both hosts when you save the changes.

8. Perform the following procedure to configure the internal base IP address for the IBM Netezza 1000-Series appliance,

Configuration Procedure1. From the KVM on ha1, log into ha1 (Host 1) as root (the default password is netezza).

2. Run the internal IP configuration script:

/nzlocal/scripts/configip_NPS -to X Y

for example:

/nzlocal/scripts/configip_NPS -to 123 0

where X Y are the upper octets of the new internal IP subnet.

Result:As the script runs, you are prompted to remove the external network cables.

Note: Remove the external network cables from HA1 and HA2.

As the script runs, you may be prompted for the following information:

The SPA user id and password. The default is:

user id: Administrator

password: Admin

The network management switch password. The default is:

Password: admin

Note: Ignore warnings regarding “shutdown NFS service” or “Sync with time server.”

Note: If the script halts before it completes, re-run the command in step 2.

3. Re-edit the file that you edited in step b on page B-4:



B-4 D20524-3 Rev.3.0


b. An editor opens the file /etc/resolv.conf. Delete the # symbol previously placed at the beginning of the lines.

For example:

search company.comsearch domain.com#nameserver 192.168.0.1#nameserver 192.168.0.2

becomes:

search company.comsearch domain.comnameserver 192.168.0.1nameserver 192.168.0.2

c. Save and close the file.

The file is modified for both hosts when you save the changes.

4. Reconnect the external network cables to HA1 and HA2.

Run nzupgradeAfter you run the configip script, you must perform an nzupgrade:

1. Make sure that you are logged on to ha1 (Host 1) as root.


cd /nz/kit/sbin


./nzupgrade -r upgrade


The command starts the installation process. It stops the system and uses the kit files in the /nz/kit area to install the NPS software. The command also updates the catalog.

If nzupgrade does not complete, re-run the command.

D20524-3 Rev.3.0 B-5



1000-Series systems ship with four pre-configured IP addresses per host machine. Each host machine receives an IP address for external network connections, and an additional IP address is pre-configured for the cluster service.

The pre-configured IP addresses use either the 192.168.x.x or 172.16-31.x.x private IP address space.

You may find it necessary to assign different IP addresses to fit your IT environment. This document discusses a method to reconfigure these IP addresses.

Note: The procedure to change the cluster manager IP address changed in NPS 3.0.2. You no longer need to and must not edit the cluconfig.script and cluadmin.script.

Preparing to Change IP AddressesYou should set aside eight IP addresses within your network infrastructure as follows:

To take advantage of automatic IP address assignment, you need four consecutive IP addresses set aside for host 1.

IBM Netezza recommends that four consecutive IP addresses be set aside for each host. Reserving the IP addresses allows you better flexibility in future upgrades.

Otherwise, a minimum of two IP addresses for each of the hosts (four total) and one for the cluster service.

A Gigabit Ethernet port is also dedicated for the host external connections associated with the host name.

The cluster service IP shares the same physical port with the host named port. The cluster service also shares the internal logical port assigned to the nzfabric.

Note: Since the cluster service may migrate between host #1 and #2, the IP addresses for host 1, host 2 and the cluster service must be within the same IP subnet. However, if you installed additional Ethernet ports and you want to use these ports for the cluster service, they can be under different networks as long as both hosts have these additional Ethernet ports connected to the same subnet.

The default IP configuration for the cluster service is the host IP + 3.

For example, if your host is named NPS23040 as shipped from factory, and the host IP is pre-configured as 172.16.23.40, then the email server IP would be configured at factory to be 172.16.23.41. The cluster service IP would be 172.16.23.43 and 10.0.0.1 (from the "nzfabric IP" value in the file /etc/hosts). Host 2, then, might be named NPS23044 with a host IP of 172.16.23.44 and an email server IP of 172.16.23.45.

The following sections assume you have set aside these new class B IP addresses for the system in a typical private network.

Note: You may need to obtain the IP addresses, net mask, and broadcast values from your network administrator.

B-6 D20524-3 Rev.3.0


Changing the IP Address Associated with the Host NameThe system relies on the following values:

The command /bin/hostname must return the correct host name value.

The IP address associated with the host name must be maintained in the /etc/hosts

The IP address associated with the nzfabric must be correct in /etc/hosts

The IP addresses associated with the host name and nzfabric are in IPv4 format.

If these values are not correct, some scripts will not work correctly. System scripts do not use NIS, DNS or LDAP services to do name/IP lookup.

Perform the following procedure to reconfigure your host IP.

Note: This procedure assumes that you are changing the IP addresses for both hosts, and provides instruction for changing the addresses for both hosts.

1. Logon as root.

2. The heartbeat must be stopped before editing any files.

To check the cluster state, type:

crm_mon -i5

If both hosts are online and all services in the nps resource group are started, then the cluster is up.

If the cluster is down, go directly to step 3.

If the cluster is up, shutdown the standby node first:

a. Determine the active and standby nodes:

crm_resource -r nps -W

The active node will be listed, so the standby node is the one that is not listed

b. To shutdown the standby node, go to the KVM on the standby node and type:


Wait until the standby node is down before proceeding.

Note: If you wish to monitor the state of the nodes, you can open another window (ALT-F2) and run the command crm_mon -i5 in that window. This is optional.

c. When the standby node is down, go to the KVM on the active node and type:


Note: Wait until the active node is down before proceeding. Use separate terminal instance with the crm_mon -i5 command to monitor the state of the active node.

3. Move to the KVM on ha1 and edit the following files on host 1:

Note: The IP address (IPADDRESS) referred to in step b and step c, is specific to the host. The address for host 1 will be different from the address for host 2.

a. Edit the file /etc/sysconfig/network

Change:

GATEWAY=172.30.22.1

Note: The value given here is an example. Ask your network administrator for the correct value for GATEWAY.

D20524-3 Rev.3.0 B-7


b. Edit the appropriate ethernet configuration file in etc/sysconfig/network-scripts/

Edit /etc/sysconfig/network-scripts/ifcfg-eth8Change:

IPADDR=172.30.22.60NETMASK=255.255.0.0

If you see NETWORK= parameter, set it to the correct value; otherwise, do not enter this value.

c. Edit /etc/hosts.

Find the entry associated with the host name and IP address. You may see lines similar to these:

"# do not change the following entries"

"172.16.23.40 nps23040.netezza.com nps23040"

…

Change the line:

"172.16.23.40 nps23040.netezza.com nps23040"

to

"172.30.22.60 nps23040.netezza.com nps23040".

4. Now move to the KVM on ha2 and again perform the procedure in step 3. This time you will be editing the files on host 2.

Note: Be sure to use the IP address for host 2 when you edit the files on host 2.

5. At the command prompt, enter this command:

/sbin/service network restart

6. Move to the KVM on ha1 and issue the same command again:

/sbin/service network restart

7. Try to ping other machines in the network.

Note: If this machine is connected to the house network, you should be able to ping other machines in the network by IP address. If you can not ping other hosts, you need to review your work so far and make corrections before you move on.

8. From the KVM on ha1, enter the following and press Enter:



9. Also from the KVM on ha1, enter the following and press Enter:



10. From ha1, enter the following and press Enter:

crm_mon -i5

Result: When the cluster manager comes up and is ready, status appears as follows. Make sure that nzinit has started before you proceed. (This could take about one minute.)

B-8 D20524-3 Rev.3.0


Node: nps61074 (e890696b-ab7b-42c0-9e91-4c1cdacbe3f9): onlineNode: nps61068 (72043b2e-9217-4666-be6f-79923aef2958): online

Resource Group: npsdrbd_exphome_device(heartbeat:drbddisk): Started nps61074drbd_nz_device(heartbeat:drbddisk): Started nps61074exphome_filesystem(heartbeat::ocf:Filesystem): Started nps61074nz_filesystem (heartbeat::ocf:Filesystem): Started nps61074fabric_ip (heartbeat::ocf:IPaddr): Started nps61074wall_ip (heartbeat::ocf:IPaddr): Started nps61074nzinit (lsb:nzinit): Started nps61074

fencing_route_to_ha1(stonith:apcmaster): Started nps61074fencing_route_to_ha2(stonith:apcmaster): Started nps61068

This command verifies that the cluster manager comes up.

11. From ha1, press CTRL+C to break out of crm_mon.

Changing the Floating IP AddressThe floating IP address is used by the system as the single address for external network connection. This IP address is capable of pointing to either host, whichever is active. It has also been called the Cluster Service IP dress, the ODBC IP address, and the NPS IP address.

Ensure that you have performed the previous procedures for changing the IP address asso-ciated with the host name.

You should have set aside four consecutive IP addresses for Host 1 (for example: 172.30.22.60 - 172.30.22.63).

If you wish to use your own cluster service IP address, refer to “Using Your Own Floating IP Address” on page B-10.

Using the Default Floating IP AddressIf you can take the default IP assignments, perform the following steps:

1. Verify that the DRBD and heartbeat services are running on both hosts:

a. From the KVM on ha1, type:

service heartbeat status

ssh ha2 'service heartbeat status'

If the heartbeat service is not running, start it on both hosts by typing the following two commands from the KVM on ha1:



b. From the KVM on ha1, type:

service drbd status

ssh ha2 'service drbd status'

If the DRBD service is not running, start it by typing the following commands from ha1:

service drbd start

ssh ha2 'service drbd start'

D20524-3 Rev.3.0 B-9



a. Type the following command:

crm_resource -r nps -p target_role -v stopped

b. Enter the command:

crm_mon -i5

Note: Wait until all resources have stopped before proceeding.

c. Enter Ctrl-C to quit crm_mon command.

3. Enter the following command:

/nzlocal/scripts/heartbeat_admin.sh --change-wall-ip

Note: The floating IP is assigned the address 172.20.22.63. This IP address is obtained by using the output of hostname command to scan /etc/hosts for the host IP. The script then adds 3 to the last octet of the IP address associated with the host name (172.20.22.60) to form the cluster service IP address. If the last octet of your host IP address is greater than 252, the resulting address will be invalid.

4. Restart the heartbeat on both hosts:

service heartbeat restart

Note: The heartbeat service must be restarted on both hosts. Do not continue until this step is complete.

5. Bring the system back up:

crm_resource -r nps -p target_role -v started

Monitor crm_mon -i5 to watch until every resource in the nps resource group has been started on one of the two hosts. It may take a few minutes.

Using Your Own Floating IP AddressYou can select your own IP address or device for the floating IP. You need to enter your own IP address if you did not set aside a block of 4 consecutive IP addresses for your system's host 1. In the following cases, you also need to enter your own IP address:

If the last octet of your host 1 IP address is greater than 251. The script is not smart enough to jump to the next valid IP even if you use class A or B IP.

If you added additional Ethernet ports to the hosts and you want to access your system through different ports.

If you do not take the default IP address assignment, you need to make sure the IP address you selected is within the same subnet reachable from both host 1 and 2 Ethernet ports. To assign your own IP address or device, use the heartbeat_admin.sh script. Use the following parameters with this command:

Note: The script does limited checks on IP address format (IPv4) and consistency between all three parameters. The script fails if the address format is incorrect. If you omit the -dev parameter, the cluster manager uses the default value for the specific model.

B-10 D20524-3 Rev.3.0


To use your own custom floating IP address, perform the following steps:





If the heartbeat service is not running on both hosts, start it on both hosts by typing the following two commands from the KVM on ha1:




service drbd status


If the DRBD service is not running on both hosts, start it on both hosts by typing the following commands from ha1:

service drbd start



a. Type the following command:


b. Enter the command:

crm_mon -i5

Note: Wait until all resources have stopped before proceeding.

c. Enter Ctrl-C to quit crm_mon command.

3. Enter the following command, inserting your values for the --ip, --mask, and --dev switches:

/nzlocal/scripts/heartbeat_admin.sh --change-wall-ip --ip <your.custom.ip.address> --mask <# of mask bits> --dev <device name>

Note: The --mask switch specifies the number of bits in the mask. The following table shows how the number of bits equates to an address mask in octet form:

--mask parameter (# bits)

Address Mask

0 0.0.0.01 128.0.0.02 192.0.0.03 224.0.0.04 240.0.0.05 248.0.0.06 252.0.0.07 254.0.0.0

D20524-3 Rev.3.0 B-11


For example:

To use a custom IP address, type (all on one line):/nzlocal/scripts/heartbeat_admin.sh --change-wall-ip --ip 172.30.22.62 --mask 24

To use just a custom network device:

/nzlocal/scripts/heartbeat_admin.sh --change-wall-ip --dev eth4

To use both a custom network device and custom IP address:

/nzlocal/scripts/heartbeat_admin.sh --change-wall-ip --ip 172.30.22.62 --mask 24 --dev eth4

4. Restart the heartbeat on both hosts:

service heartbeat restart

Note: The heartbeat service must be restarted on both hosts. Do not continue until this step is complete.

8 255.0.0.09 255.128.0.0

10 255.192.0.011 255.224.0.012 255.240.0.013 255.248.0.014 255.252.0.015 255.254.0.016 255.255.0.017 255.255.128.018 255.255.192.019 255.255.224.020 255.255.240.021 255.255.248.022 255.255.252.023 255.255.254.024 255.255.255.025 255.255.255.12826 255.255.255.19227 255.255.255.22428 255.255.255.24029 255.255.255.24830 255.255.255.25231 255.255.255.25432 255.255.255.255

--mask parameter (# bits)

Address Mask

B-12 D20524-3 Rev.3.0


5. Bring the system software back up:



Wait until crm_mon -i5 shows the nps resource group started on a host.

Changing the Host Name and DNSTo change the host name:









service drbd status


If the DRBD service is not running, start it by typing the following commands from ha1:

service drbd start


2. Go to the KVM on ha1 and login as root.

3. Shut down the system software on one host only. From the KVM on ha1 type:


Monitor crm_mon -i5 to watch until every resource in the nps resource group has been stopped. It may take a few minutes.

4. Stop the DRBD service on ha1.

From the KVM on ha1 type:

service drbd stop

5. Stop the DRBD service on ha2.

From the KVM on ha2 type:

service drbd stop

6. The hostname command is used to change the hostname on each system. Do this on each host:

hostname <new hostname>

Host names are case-sensitive. During this procedure you are required to type the new hostname in several places. You must type the new host name exactly the same way each time that you enter it. If you do not enter it the same way, the system will fail to restart properly.

D20524-3 Rev.3.0 B-13


7. Edit the network configuration on each host, replacing the old hostname with the new hostname:

vi /etc/sysconfig/network

Change the line that reads HOSTNAME=<old hostname>.

8. Edit the hosts file on each host:

vi /etc/hosts

Find the line that begins with an IP address and contains the hostname and domain. Change the old hostname to the new hostname in both places in this line

For example:

Change:

198.162.70.182 oldhost oldhost.mydomain.com

to:

198.162.70.182 newhost newhost.mydomain.com

9. If your site uses Domain Name Service (DNS):



b. An editor opens the file /etc/resolv.conf.

c. Replace every occurrence of "netezza.com" with "xyzcorp.com". For example, if you see a line "search netezza.com", change it to "search xyzcorp.com".

d. Insert the line "nameserver 172.30.0.xxx". Delete nameserver lines with IP addresses that are no longer valid.

e. If your NPS server machine is connected to a network using NIS, NIS+ or LDAP name lookup services, consult with your network administrator for required changes.

f. Save and close the file.

g. Try pinging other machines in the network by name.

Note: If the ping fails, you need to review your work so far and make corrections before you move on. You may need to ask the local network administrator for help.

10. Reconfigure the PDUs with the new hostname:

Note: Run this command on one host only!

/nzlocal/scripts/rpc/rpcconfigure -c -F

Note: If the system requests a password for netswmgt01, the password is admin

B-14 D20524-3 Rev.3.0


11. Update DRBD configuration:


/nzlocal/scripts/drbd_config.sh --config-only

It is essential that the --config-only option is included in this command. Failure to include this option may result in the /nz partition being reformatted.

12. Update Heartbeat configuration:


/nzlocal/scripts/heartbeat_admin.sh --change-hostname

13. Reboot both hosts. When they come back up, verify that the new hostnames are cor-rect. If not, stop here and repeat this procedure.

14. Logon to either host as root.

15. Verify that the heartbeat service is running on both hosts.

From the KVM on ha1, type:






16. Wait until the heartbeat service has started on both hosts before continuing.

crm_mon -i5

Note: Monitor the status on both hosts.

17. Bring the system software back up:



D20524-3 Rev.3.0 B-15


B-16 D20524-3 Rev.3.0

A P P E N D I X C
IMM Configuration
1. Configure the laptop so that its IP address is on the same subnet as the IMM. See the section titled “Integrated Management Module (IMM) IP Address Setup” on page 1-19 for the IP address of the IMM.

2. Using an ethernet cable, connect the laptop’s ethernet port to the same network that the host server is connected to.

3. Open web browser and navigate to the IP address that you defined for the IMM module in Chapter 1.

4. A login screen appears:

5. At the login screen, enter the User Name and Password and then click the OK button.

User Name: USERID

Password: PASSW0RD

Note: The ‘0’ in PASSW0RD is a zero, not the letter ‘O’.

C-1


6. The Welcome screen appears.

Click on the Continue button.

7. You are presented with the System Status page

Click on the Alerts menu item in the pane at the left side of the window.

C-2 D20524-3 Rev.3.0

8. You will see a list of all the defined and undefined alert recipients:

Click on one of the empty slots in the list to add a user.

9. The screen that appears allows you to define a Remote Alert Recipient.

Enter the pertinent information and click the Save button.

10. You are returned to the Remote Alert Recipients screen.

Click on the System Settings menu item in the pane at the left side of the window.

D20524-3 Rev.3.0 C-3


11. The System Settings screen appears.

Click on the link that says Set IMM Date and Time.

12. On the screen that appears, enter the Date and Time, and the address of an NTP server (if desired).

Click the Save button.

13. You are returned to the System Settings Screen.

Click on the Login Profiles menu item in the pane at the left side of the window.

C-4 D20524-3 Rev.3.0

14. The Login Profiles screen appears.

Complete the Global Login Settings on this page. You can also add additional users if you desire.

Click the Save button when you are finished.

15. Click on the Network Protocols menu item in the pane at the left side of the window.

16. You are presented with the Network Protocols configuration screen.

Scroll down to the Simple Mail Transfer Protocol (SMTP) section, and enter the IP address for your SMTP server.

When you are finished, click the Save button.

D20524-3 Rev.3.0 C-5


17. Click on the Restart IMM menu item in the pane at the left side of the window.

Configuration of the IMM is complete.

C-6 D20524-3 Rev.3.0

A P P E N D I X D
PDU Firmware Update Procedure
What’s in this appendixIP Address Assignment

Firmware Update

This chapter explains how to update the firmware on the controllable APC PDUs used in the TwinFin system.

Prerequisites

Before you begin, you will need the following:

RJ-11 to DB-9 cable (PN 21551)

Netezza Firmware/Diagnostics/Tools DVD

IP Address Assignment

Follow the steps below to configure each RPC for network connectivity. (Steps are repeated for each RPC.)

1. Connect the RJ-11 to DB-9 cable from the Host 1 serial port to the RJ-11 jack on the first PDU.

2. From the Host 1 keyboard, type:

minicom gig

3. Press the Enter key two times. This starts the session with the PDU.

4. Login to the PDU using the following username and password:

username: apcpassword: apc

5. At the menu, type 2 to select network and press the Enter key.

6. Select 1 for TCP/IP

7. Select 4 for boot mode

D-1


8. Select 4 to enable manual configuration of the IP address

Setting to manual enables static configuration of IP addresses.

9. Set the PDU’s IP Address, Subnet Mask, and Gateway address according to Table D-1 below. These addresses are dependent on the particular PDU that you are currently connected to.

Note: If you are updating firmware on the PDUs in a 1000-3, use the values for rpc1lr (lower right) and rpc1ll (lower left) from Table D-1 below.

10. Press the ESC key two times.

11. Press 4 to logout.

12. Disconnect the cable from the PDU and connect it to the next PDU to be configured.

13. Perform step 3 through step 12 for each of the remaining PDUs.

14. When all of the PDUs have been configured, press CTRL+A

15. Press the Z key.

16. Press the X key.

17. Press the Enter key to exit the minicom utility.

18. Disconnect both ends of the RJ-11 to DB-9 cable.

All of the PDUs are now configured with IP addresses.

Continue with the firmware update procedure below.

Table D-1: PDU IP Address Assignments

PDU IP Subnet Gateway

Upper Right (rpc1ur) 10.0.128.32 255.255.252.0 10.0.128.32

Upper Left (rpc1ul) 10.0.128.132 255.255.252.0 10.0.128.32

Lower Right (rpc1lr) 10.0.128.31 255.255.252.0 10.0.128.32

Lower Left (rpc1ll) 10.0.128.131 255.255.252.0 10.0.128.32

D-2 D20524-3 Rev.3.0

Firmware Update

Firmware Update

Perform the following procedure to update the firmware on the PDUs.

Note: The firmware revision on the PDU may be higher than the revision that you are updat-ing to. This is to be expected. Continue to update the PDUs with the revision that is specified in this procedure.

1. Copy the firmware tarball to Host 1 and untar it:

a. Insert and mount the Netezza Firmware/Diagnostics/Tools DVD:

mount /media/cdrom

b. Change directories:

cd /media/cdrom/firmware

c. Copy the tarball to /tmp:

cp apcFirmware-x-x.tgz /tmp

d. Change directories:

cd /tmp

e. Untar the tarball:

tar xvzof apcFirmware-x.x.tgz

f. Change directories:

cd ./APC

2. To perform the update, type the following command and press the Enter key:

./upgradeAPC.sh -ip rpc1xx -aos 356 -rpdu 355

where xx is the designation for the PDU that you are updating (see Table D-1 above)

3. Repeat step 2 above, using the appropriate PDU name (rpc1xx) for each of the remain-ing PDUs.

4. When each of the PDUs have been updated, initiate a telnet session to each PDU to verify that the firmware update was succesful. An example follows:

Example:

[root@P50-19E-D /]# telnet rpc1ul

Trying 10.0.128.132...

Connected to rpc1ul (10.0.128.132).Escape character is '^]'.

User Name : apcPassword : ***

American Power Conversion Network Management Card AOS v3.5.6

(c) Copyright 2007 All Rights ReservedRack PDU APP v3.5.5

The firmware update is complete.

D20524-3 Rev.3.0 D-3


D-4 D20524-3 Rev.3.0

A P P E N D I X E
Configuration Command Reference
What’s in this appendixswsupport -h

netswmgtConfig.sh -h

rpcconfigure -h

spapwr.sh -h

spa_init.sh -h

spaconfigure.sh -h

drbd_config.sh -h

heartbeat_config.sh -h

heartbeat_admin.sh -h

sshconfigure -h

This chapter contains reference material on the scripts/commands used in the configura-tion of the system.

drbd_config.sh -h

Usage: drbd_config.sh [--no-format | --config-only]

This script will setup DRBD shared partitions for heartbeat and NPS use. It is

intended for initial setup, or to start with a clean slate. Run from HA1 only!

WARNING: RUNNING THIS SCRIPT WITH DEFAULT OPTIONS WILL COMPLETELY DESTROY ANY AND ALL DATA ON /nz AND /export/home!

Options:

--no-format: Creates fresh DRBD config, but does not format drive. Does

create metadata. ONLY FOR MANUFACTURING GHOST INSTALLS!

--config-only: Do not format or create metadata. Will only re-create

configuration files.

E-1


heartbeat_config.sh -h

Usage: heartbeat_config.sh [--ip WALL_IP_ADDR --mask WALL_IP_NETMASK] [--dev WALL_IP_DEV]

This script will setup the heartbeat cluster manager. Intended for initial

setup, or to start with a clean slate. Run from HA1 only!

The "Wall IP" is the external IP address that will always access the active

host (it is moved during failovers). If the Wall IP information is not

specified, it is automatically determined by taking HA1's external IP + 3.

Optional arguments:

--ip: Manually specify the "Wall IP" address (IPv4: #.#.#.#).

--mask: Manually specify the ip's netmask (#.#.#.#). Required if --ip is used.

--dev: Manually specify the ip's device. If no ip/mask is given, they are

automatically determined as described above.

WARNING: RUNNING THIS SCRIPT WILL DESTROY ANY EXISTING HEARTBEAT CONFIGURATION!

heartbeat_admin.sh -h

Usage: heartbeat_admin.sh --change-hostname

heartbeat_admin.sh --change-fabric-ip

heartbeat_admin.sh --change-wall-ip [--ip ip --mask netmask] [--dev device]

heartbeat_admin.sh --enable-nps

heartbeat_admin.sh --migrate

This script is used for Heartbeat administration tasks. It may be run from

either host, regardless of who is active.

Note that for all tasks, the Heartbeat service should be running on both hosts!

E-2 D20524-3 Rev.3.0


Modes:

For these change modes, stop the NPS resource group before using this script.

--change-hostname: If the hostnames on the system were changed from initial

installation, run this mode to update Heartbeat.

--change-fabric-ip: If the fabric network was changed, run this mode to

update Heartbeat.

--change-wall-ip: If the external network was changed, run this mode to

update Heartbeat. The ip and netmask are optional, but must

be specified together when used. The external network device

is also optional. Note that if the ip is not specified, it

will be automatically determined by adding 3 to the last

octet of host 1's external ip address.

For these modes, the NPS resource group should already be running.

--enable-nps: Instruct Heartbeat to manage NPS software. This should be done

once after NPS is initially installed.

--migrate : Migrate (failover) to the other node.


Usage: netswmgtConfig.sh [-h] <options>

Options:

[(-s (n|all) | -from n)] NETSWMGT n or all NETSWMGTs in the system. default=all

-password optional, serial connection password

-h show this usage

Internal Options:

-v verbose mode

-t trace mode

D20524-3 Rev.3.0 E-3


rpcconfigure -h

Usage: rpcconfigure [-h] <options>

This script will configure all APC/PDU and BayTech RPCs for n-series, z-series,

HA, 10K and TwinFin systems.

Options:

-h show this usage

-m maintenance mode

-c correct/verify that rpc's are properly configured

-F force correction without prompting for the -c option

-f (yes|no|only) optional, load firmware:

yes=include firmware; no=do not include firmware; only=load firmware only

-fdir optional, firmware root directory

-r reset a rpc or APC/PDU network to factory default

-s Use serial cable, this is the default

-nos Do not force serial cable, ask me for APC mac addresses

-p n Print n copies of label, not supported with -offline

-offline Do offline maintenance. Used with -m

-buildmap Build a new port map. Used with -c

-password optional, management network switch password for connection check

-n Start a new session

Optional mac address input file for unattended configuration:

Full path name: /tmp/<hostname>-rpcmac.in

Format: <RPC_NAME_IN_ETC_HOSTS>,<MAC_ADDRESS>[,(APC|RPC)]

rpcverify -h

Usage: /nzlocal/scripts/rpcverify [-h | -q]

Options:

-h show this usage

-q quiet mode- nothing written to stdout

E-4 D20524-3 Rev.3.0

sshconfigure -h

sshconfigure -h

Usage: sshconfigure [-h] <options>

Options:

-h show this usage

-HA1 install version for host 1 in an HA configuration


Internal Options:

-init initialize hosts file and flexlm for internal use

-v verbose mode

-t trace mode

spa_init.sh -h

Usage: spa_init.sh [-h] <options>

Options:

[(-s (n|all) | -from n)] SPA n or all SPAs in the system. default=all

-uid optional, user ID to log in to spa

-password optional, password of the supplied uid

-c|--clear optional, reset to factory default where function is supported

-h show this usage

Internal Options:

-v verbose mode

-t trace mode

spaconfigure.sh -h

Usage: spaconfigure.sh [-h] <options>

Options:

[(-s (n|all) | -from n)] SPA n or all SPAs in the system. default=all

-uid optional, user ID to log in to spa

D20524-3 Rev.3.0 E-5


-password optional, password of the supplied uid

-f (yes|no|only) optional, load firmware:

yes=include firmware; no=do not include firmware; only=load firmware only

-components "space separated component names" optional,

valid for IBM Blade Center: mm[1] switch[1] switch[2] switch[3] switch[4]

-R optional, use reset switch to clear AMM config and set defaut IP

-fdir optional, firmware root directory

-h show this usage

Internal Options:

-v verbose mode

-t trace mode

spapwr.sh -h

Usage: spapwr.sh [-h] <options>

Options:

-h show this usage

-j N target JBOD N in SPA spanum only, N=([digit]+|all)

-on 1 -j 1 truns on JBOD #1 in SPA #1

-off all -j 1 truns off JBOD #1 in every SPA

-noj exclude JBOD as targets, target SPU blades only.

-off N [(l|r) [rack]] turn off SPA N [(l|r) [rack]], if N is all then do all

-on N [(l|r) [rack]] turn on SPA N [(l|r) [rack]], if N is all then do all

-off N [-rpcid rpc([0-9]+)[(u|l)](r|l)], turn off socket N on rpcid, N=([digit]+|all)

-on N [-rpcid rpc([0-9]+)[(u|l)](r|l)], turn on socket N on rpcid, N=([digit]+|all)

Internal Options:

-v verbose mode

-t trace mode

-notitle do not print title lines.

E-6 D20524-3 Rev.3.0

swsupport -h

swsupport -h

Usage: swsupport [-h] <options>

Options:

-h show this usage



-STD install version for host in a standard Sparrow configuration

-host which cpu/host to install (default is DL585 - if -host is missing

DL585 is installed. For DL380 must have -c DL380.)

Developer Options:

-rev nps rev to install (current default is 2_2_1)

-b base directory to use. default is /

-c dir use dir instead of /media/cdrom for scripts

-v verbose mode

-t trace mode

D20524-3 Rev.3.0 E-7


E-8 D20524-3 Rev.3.0

A P P E N D I X F
Notices and Trademarks
What’s in this appendixNotices

Trademarks

Open Source Notifications

Regulatory and Compliance

This information was developed for products and services offered in the U.S.A.

Notices

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:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 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

F-1


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 Corporation26 Forest StreetMarlborough, MA 01752 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.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

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.

F-2 D20524-3 Rev.3.0

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 dis-tribute 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. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample 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_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

Netezza, the Netezza logo, the circle-N logo, TwinFin, Skimmer, Snippet Blades, S-Blades, NPS, Snippet, Snippet Processing Unit, SPU, Snippet Processing Array, SPA, Performance Server, Netezza Performance Server, Asymmetric Massively Parallel Processing, AMPP, Intelligent Query Streaming and other marks are trademarks or registered trademarks of Netezza Corporation, an IBM Company, in the United States and/or other countries. All rights reserved.

The following terms are trademarks or registered trademarks of other companies:

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 Corp-pration 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.

D20524-3 Rev.3.0 F-3


APC and the APC logo are trademarks or registered trademarks of American Power Conver-sion Corporation.

All document files and software of the above named third-party suppliers are provided "as is" and may contain deficiencies. Netezza and its suppliers disclaim all warranties of any kind, express or implied, including, without limitation, those of merchantability, fitness for a particular purpose, and non infringement.

In no event will Netezza or its suppliers be liable for indirect, incidental, consequential, special, or economic damages (including lost business profits, business interruption, loss or damage of data, and the like), or the use or inability to use the above-named third-party products, even if Netezza or its suppliers have been advised of the possibility of such damages.

Other company, product or service names may be trademarks or service marks of others.


PostgreSQL

Portions of this publication were derived from PostgreSQL documentation. For those por-tions of the documentation that were derived originally from PostgreSQL documentation, and only for those portions, the following applies:

PostgreSQL is copyright © 1996-2001 by the PostgreSQL global development group and is distributed under the terms of the license of the University of California below.

Postgres95 is copyright © 1994-5 by the Regents of the University of California.

Permission to use, copy, modify, and distribute this documentation for any purpose, with-out fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

In no event shall the University of California be liable to any party for direct, indirect, spe-cial, incidental, or consequential damages, including lost profits, arising out of the use of this documentation, even if the University of California has been advised of the possibility of such damage.

The University of California specifically disclaims any warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The doc-umentation provided hereunder is on an "as-is" basis, and the University of California has no obligations to provide maintenance, support, updates, enhancements, or modifications.

ICU Library

The Netezza implementation of the ICU library is an adaptation of an open source library Copyright (c) 1995-2003 International Business Machines Corporation and others.

ICU License - ICU 1.8.1 and laterCOPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2003 International Business Machines Corporation and othersAll rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software

F-4 D20524-3 Rev.3.0


is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANT-ABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLI-GENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

ODBC Driver

The Netezza implementation of the ODBC driver is an adaptation of an open source driver, Copyright © 2000, 2001, Great Bridge LLC. The source code for this driver and the object code of any Netezza software that links with it are available upon request to [email protected]

Botan License

Copyright (C) 1999-2008 Jack Lloyd

2001 Peter J Jones2004-2007 Justin Karneges2005 Matthew Gregan2005-2006 Matt Johnston2006 Luca Piccarreta2007 Yves Jerschow2007-2008 FlexSecure GmbH2007-2008 Technische Universitat Darmstadt2007-2008 Falko Strenzke2007-2008 Martin Doering2007 Manuel Hartl2007 Christoph Ludwig2007 Patrick Sona

All rights reserved.

Redistribution and use in source and binary forms, for any use, with or without modifica-tion, of Botan (http://botan.randombit.net/license.html) is permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of condi-tions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials pro-vided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRAN-TIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED.

D20524-3 Rev.3.0 F-5


IN NO EVENT SHALL THE AUTHOR(S) OR CONTRIBUTOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAM-AGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOW-EVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.


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 30A 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

Attention: This product is not intended to be connected directly or indirectly by any means whatsoever to interfaces of public telecommunications networks, neither to be used in a Public Services Network.

FCC - Industry Canada Statement

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 reason-able 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 users will be required to correct the interference at their own expense.

This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

WEEE

Netezza Corporation is committed to meeting the requirements of the European Union (EU) Waste Electrical and Electronic Equipment (WEEE) Directive. This Directive requires pro-ducers of electrical and electronic equipment to finance the takeback, for reuse or recycling, of their products placed on the EU market after August 13, 2005.

CE Statement (Europe)

This product complies with the European Low Voltage Directive 73/23/EEC and EMC Direc-tive 89/336/EEC as amended by European Directive 93/68/EEC.

F-6 D20524-3 Rev.3.0


Warning: 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.

VCCI Statement

この装置は、情報処埋装置等電波障害自主規制協議会　（VCCI）の基準に基づくクラス A 情報技術装置です。この装置を家庭環境で使用すると電波妨害を引き起越すことがあります。この場合には使用者が適切な対策を講ずるう要求されることがあります。

D20524-3 Rev.3.0 F-7


F-8 D20524-3 Rev.3.0

Date post:	26-Oct-2015
Category:	Documents
Upload:	irshadsk
View:	359 times
Download:	53 times

Netezza System Configuration Guide Ha Xs

Documents