IBM DR550 User Manual

Download

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 1

IBM® System StorageTM DR550 V3.0

Installation, Setup, Operations, and

Problem Determination Guide

(P) IBM part number: 23R5892

*P23R5892*

(2P) EC Level: H81819

*2PH81819*

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 2

Table of Contents

INTRODUCTION............................................................................................................. 6

HARDWARE OVERVIEW............................................................................................... 7

IBM System P5 520...................................................................................................................................................7

Management Console ..............................................................................................................................................9

IBM TotalStorage DS4100 Midrange Disk System and IBM TotalStorage DS4000 EXP100...................9

IBM TotalStorage SAN Switch .............................................................................................................................10

Accessing the Switch(es).................................................................................................................................10

Dual Node Zoning – without Enhanced Remote Volume Mirroring ......................................................11

Single Node Zoning – without Enhanced Remote Volume Mirroring...................................................12

SOFTWARE OVERVIEW ............................................................................................. 14

High Availability Cluster Multi-Processing (HACMP) for AIX ......................................................................14

System Storage Archive Manager ......................................................................................................................14

System Storage Archive Manager API Client..............................................................................................15

DS4000 Storage Manager Version 9.12.65........................................................................................................15

Content Management Applications....................................................................................................................16

IBM DB2 Content Manager ..............................................................................................................................16

Other Management Applications....................................................................................................................16

DR550 OFFERINGS ..................................................................................................... 18

DR550 Single Node Components .......................................................................................................................18

DR550 Dual Node Components...........................................................................................................................21

DS4100 Logical Volume Configurations ...........................................................................................................25

AIX settings ..............................................................................................................................................................27

System Storage Archive Server Configuration ...............................................................................................28

System Storage Archive Manager Database and Logs ............................................................................28

System Storage Archive Manager Disk Storage Pool...............................................................................28

System Storage Archive Manager Storage Management Policy............................................................28

Automated System Storage Archive Manager Operations......................................................................28

Routine Operations for System Storage Archive Manager..........................................................................29

Monitoring the Database and Recovery Log Status .................................................................................29

Monitoring Disk Volumes.................................................................................................................................29

Monitoring the Results of Scheduled Operations .....................................................................................29

Installing and Setting Up System Storage Archive Manager API Clients.................................................29

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 3

INSTALLATION AND ACTIVATION............................................................................. 30

Safety Notices..........................................................................................................................................................30

Site Preparation and Planning.............................................................................................................................31

Unpacking and Installing the Rack(s)................................................................................................................32

Positioning the Rack .........................................................................................................................................32

Leveling the Rack...............................................................................................................................................32

Attaching the Rack to a Concrete Floor .......................................................................................................33

Attach the Rack to a Concrete Floor Beneath a Raised Floor................................................................36

Connecting the Racks in a Suite (applies only to dual node 89.6 TB Configuration) ......................38

Cabling between the Racks .............................................................................................................................40

Cabling to the customer’s Ethernet / IP Network ...........................................................................................41

Single Node Configurations.................................................................................................................................41

Dual Node Configurations ....................................................................................................................................43

Setting up the Management Console ................................................................................................................44

Userid and Password........................................................................................................................................44

Changing Server Names ..................................................................................................................................44

Connecting AC Power ...........................................................................................................................................47

Configuring the P5 520 Servers ..........................................................................................................................49

User Accounts ....................................................................................................................................................49

Connecting to Gigabit Ethernet (Fibre) Network .......................................................................................50

Connecting to a 10/100/1000 Mbps Ethernet (copper) Network.............................................................51

Procedure for Changing IP Address .............................................................................................................53

Configuring the Dual Node System (P5 520 Servers)....................................................................................55

Connecting to Gigabit Ethernet (Fibre) Network .......................................................................................56

Connecting to 10/100/1000 Ethernet (Copper) Network ...........................................................................58

HACMP Configuration ...........................................................................................................................................59

Procedures for Changing IP Addresses.......................................................................................................59

Cluster Snapshot........................................................................................................................................................72

REMOTE MIRRORING ................................................................................................. 74

Zoning diagrams (single and dual node)..................................................................................................................74

Setting up DR550 for remote mirroring.............................................................................................................77

Recovery from the primary failure......................................................................................................................78

Setting up DR550 for mirroring back to original site.....................................................................................80

OTHER INSTALLATION TOPICS ................................................................................ 81

Changing passwords.............................................................................................................................................81

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 4

HACMP Network Considerations........................................................................................................................85

HACMP Configuration in Switched Networks.............................................................................................85

Monitoring the HACMP Cluster ...........................................................................................................................86

Error Notification and Monitoring.......................................................................................................................86

HMC electronic problem reporting ................................................................................................................86

DS4000 SNMP and e-mail setup for error notification ..............................................................................94

DS4000 Service Alert.........................................................................................................................................99

Changing TSM HACMPADM password ...........................................................................................................103

Creating an AIX Recovery DVD .........................................................................................................................104

Creating a Root Volume Group Backup on DVD-RAM with Universal Disk Format .......................104

Recovering from a problem using the Recovery DVD ................................................................................106

Boot from the Recovery DVD........................................................................................................................106

Set and Verify Installation Settings .............................................................................................................107

Backing Up the DR550 Data ...............................................................................................................................108

OTHER INFORMATION.............................................................................................. 110

Environmental Specifications............................................................................................................................110

P5 520..................................................................................................................................................................110

DS4100................................................................................................................................................................110

DS4000 EXP100 ................................................................................................................................................111

SAN Switches – 2005-B16..............................................................................................................................111

7310-CR3 ............................................................................................................................................................111

7316-TF3 .............................................................................................................................................................112

7014-T00 Rack...................................................................................................................................................112

Lost Key Replacement.........................................................................................................................................113

COMPLEMENTARY PRODUCTS .............................................................................. 114

IBM Tape Solutions ..............................................................................................................................................114

Connecting Tape to the DR550.....................................................................................................................114

Single node tape attachment .............................................................................................................................114

Dual node tape attachment ................................................................................................................................115

Data Migration .......................................................................................................................................................116

PROBLEM DETERMINATION.................................................................................... 118

Gathering problem information from the user ..............................................................................................118

Additional sources of information ..........................................................................................................................121

Viewing the AIX runtime error log ....................................................................................................................122

Support Web Site ..................................................................................................................................................122

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 5

Placing a Service Call ..........................................................................................................................................122

DS4000 Service Alert Notification.....................................................................................................................124

REFERENCES............................................................................................................ 126

UPDATES TO THIS GUIDE........................................................................................ 128

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 6

Introduction

IBM® System StorageTM DR550, one of IBM’s Data Retention offerings, is an integrated offering for clients that need to retain and preserve electronic business records. The DR550 packages storage, server and software retention components into a lockable cabinet.

Integrating IBM System P5 servers (using POWER5™ processors) with IBM System Storage and TotalStorage products and IBM System Storage Archive Manager software, this system is designed to provide a central point of control to help manage growing compliance and data retention needs. The powerful system, which fits into a lockable cabinet, supports the ability to retain data and helps prevent tampering alteration. The system’s compact design can help with fast and easy deployment, and incorporates an open and flexible architecture.

To help clients better respond to changing business environments as they transform their infrastructure, the DR550 can be shipped with as few as 5.6 terabytes of physical capacity and can expand up to 89.6 terabytes, of physical capacity (equal to 89.6 million full-length novels) to help address massive data requirements.

The DR550 is available to be sold by IBM Business Partners certified on all of the solution components as well as by IBM Direct.

Innovative Technology

At the heart of the offering is IBM System Storage Archive Manager. This new industry changing software is designed to help customers protect the integrity of data as well as automatically enforce data retention policies. Using policy-based management, data can be stored indefinitely, can be expired based on a retention event, or have a predetermined expiration date. In addition, the retention enforcement feature may be applied to data using deletion hold and release interfaces which hold data for an indefinite period of time, regardless of the expiration date or defined event.

The policy software is also designed to prevent modifications or deletions after the data is stored. With support for open standards, the new technology is designed to provide customers flexibility to use a variety of content management or archive applications.

The System Storage Archive Manager is embedded on an IBM System P5 520 using POWER5+ processors. This entry-level server has many of the attributes of IBM’s high-end servers, representing outstanding technology advancements.

Tape storage can be critical for long-term data archiving, and IBM provides customers with a comprehensive range of tape solutions. The IBM System Storage DR550 supports IBM's TotalStorage Enterprise Tape Drive 3592, IBM System Storage TS1120 drive, and the IBM Linear Tape Open family of tape products. Write Once Read Many (WORM) cartridges are recommended due to the permanent nature of data stored with the DR550, it is strongly recommended that the 3592 with WORM cartridges be used to take advantage of tape media encoded to enforce nonrewrite and non-erase capability. This complementary capability will be of particular interest to customers that need to store large quantities of electronic records to meet regulatory and internal audit requirements.

The DR550 is available in two basic configurations: single node (one POWER5+ server) and dual node (two clustered POWER5+ servers).

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 7

Hardware Overview

The DR550 includes one or two IBM System P5 520 servers running AIX® 5.3. When configured with two 520 servers, the servers are setup in an HACMP™ 5.3 configuration. Both P5 520s have the same hardware configuration. When configured with one 520 server, no HACMP software is included.

IBM System P5 520

The IBM System P5 520 (referred to hereafter as the P5 520 when discussing the DR550) is a costeffective, high performance, space-efficient server that uses advanced IBM technology. The P5 520 uses the POWER5+ microprocessor, and is designed for use in LAN clustered environments.

The P5 520 is a member of the symmetric multiprocessing (SMP) UNIX servers from IBM. The P5 520 (product number 9131-52A) is a 4-EIA (4U), 19-inch rack-mounted server. The P5 520 is configured as a 2-core system with 1.9 GHz processors. The total system memory installed is 1024 MB.

The P5 520 includes six hot-plug PCI-X slots, an integrated dual channel Ultra320 SCSI controller, two 10/100/1000 Mbps integrated Ethernet controllers, and eight front-accessible disk bays supporting hot-swappable disks (two are populated with 36.4 GB Ultra3 10K RPM disk drives). These disk bays are designed to provide high system availability and growth by allowing the removal or addition of disk drives without disrupting service. The internal disk storage is configured as mirrored disk for high availability.

Figure 1: Front view of P5 520 server

In addition to the disk drives, there are also 3 media bays available.

• Media - dev0 – not used for DR550

• Media – dev1 – Slimline DVD-RAM (FC 1993)

• SCSI tape drive (not included)

From the back of the server, the following ports and slots are included.

PCI-X slots: The P5 520 provides multiple hot-plug PCI-X slots. The number and type of adapters installed is dependent on the configuration selected.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 8

ports

One short 64

bit 133 MHz (slot

Supply (Optional)

ports

The following adapters are installed.

• 3 – 2 Gigabit Fibre Channel PCI-X adapters (two for connections to the internal SAN for disk attachment and one for connection to the internal SAN for tape attachment) (FC 5716) – located in slots 1, 4, 5

• 1 – 10/100/1000 Mbps dual port Ethernet PCI adapter II (FC 1983 – TX version or FC 1984 – SX version) – located in slot 3

o Used for connection to the client network

• 1 – POWER GXT135P Graphics Accelerator with Digital support adapter (FC 1980) – located in slot 2

I/O ports: The P5 520 includes several native I/O ports as part of the basic configuration:

• 2 10/100/1000 Ethernet ports (for copper based connections)

o Both are used for connections to the DS4100 and used for management purposes

only (no changes should be made in these connections).

• 2 serial ports (RS232).

o These are not used with DR550.

• 2 USB ports

o One of these is used to connect to the keyboard and mouse – the other port is not

used

• 2 RIO ports

o These are not used by DR550

• 2 HMC (Hardware Management Console) ports

o One is used for connection to the HMC server in the rack

• 2 SPCN ports

o These are not used by DR550

Hot-plug

Hot-plug Power

GX Bus

Two HMC

ports*

Two

10/100/1000 Mbps

Ethernet ports

Two USB

2.0

Two System ports*

Six hot-plug PCI-X slots: Two long 64-bit 133 MHz (slots 5, 6) One short 64-bit 266 MHz (slot 4) Two short 32-bit 66 MHz (slots 2,3)

Two

SPCN

Figure 2: Back view of P5 520 server

The Converged Service Processor2 (CSP) is on a dedicated card plugged into the main system planar, which is designed to continuously monitor system operations, taking preventive or corrective actions to promote quick problem resolution and high system availability.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 9

Additional features are designed into pSeries servers to provide an extensive set of reliability, availability, and serviceability (RAS) features such as improved fault isolation, recovery from errors without stopping the system, avoidance of recurring failures, and predictive failure analysis.

Additional information on the P5 520 server is available at www.ibm.com/redbooks.

Management Console

Included in the DR550 is a set of integrated management components. This includes the Hardware Management Console (HMC) as well as a flat panel monitor, keyboard and mouse. The HMC (7310-CR3) is a dedicated rack-mounted workstation that allows the user to configure and manage call home support. The HMC has other capabilities (partitioning, Capacity on Demand) that are not used in the DR550. The HMC includes the management application used to setup call home. To help ensure console functionality, the HMC is not available as a general purpose computing resource. The HMC offers a service focal point for the 520 server(s) that are attached. It is connected to a dedicated port on the service processor of the POWER5 system via an Ethernet connection. Tools are included for problem determination and service support, such as call-home and error log notification, through the internet or via modem. The customer will need to supply the connection to the network or phone system. The HMC is connected to the keyboard, mouse and monitor installed in the rack.

The IBM 7316-TF3 is a rack-mounted flat panel console kit consisting of a 17 inch (337.9 mm x

270.3 mm) flat panel color monitor, rack keyboard tray, IBM travel keyboard (English only), and the Netbay LCM switch. This is packaged as a 1U kit and is mounted in the rack along with the other DR550 components. The Netbay LCM Switch is mounted in the same rack space, located behind the flat panel monitor. The IBM Travel Keyboard is configured for English. An integrated “mouse” is included in the keyboard. The HMC and the P5 520 servers are connected to the Netbay LCM switch so that the monitor and keyboard can access all three servers.

IBM TotalStorage DS4100 Midrange Disk System and IBM TotalStorage DS4000 EXP100

The DR550 includes one IBM TotalStorage DS4100 Midrange Disk System (hereafter referred to as the DS4100) in DR550 configurations of 44.8 TBs or less. With 89.6 TB configurations, two DS4100s are included. The disk capacity used by the DS4100(s) is provided by the IBM TotalStorage EXP100 (hereafter referred to as the EXP100). Each EXP100 enclosure packaged with the DR550 includes fourteen 400 GB Serial ATA (SATA) disk drive modules, offering 5.6 Terabytes (TB) of raw physical capacity.

The DS4100 is an affordable, scalable storage server for clustering applications such as the Data Retention application. Its modular architecture —which includes Dynamic Capacity Expansion and Dynamic Volume Expansion—is designed to support e-business on demand™ environments by helping to enable storage to grow as demands increase. Autonomic features such as online firmware upgrades also help enhance the system’s usability.

One DS4100 supports up to 44.8TB of Serial ATA physical disk storage capacity (seven EXP100 enclosures). Thus for 89.6 TB configurations of the DR550, dual DS4100s are provided, each capable of supporting up to 44.8 TBs of raw disk capacity. Note, the first rack holds the first 44.8 TB and the second rack holds the second 44.8 TB.

The DS4100 is designed to allow upgrades while keeping data intact, helping to minimize disruptions during upgrades. The DS4100 also supports online controller firmware upgrades, to help

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 10

provide high performance and functionality. Events such as upgrades to support the latest version of DS4000 Storage Manager can also often be executed without stopping operations.

IBM DS4100 Storage Server in the DR550 at a glance

Characteristics

Model 1724-100 RAID controller Dual active 2 GB RAID controllers Cache 512 MB total, battery-backed Host interface 4 - Fibre Channel (FC) Switched and FC Arbitrated Loop (FC-

AL) standard Drive interface Redundant 2 Gbps FC-AL connections EXP100 drives 400 GB 7200 RPM SATA disk drives EXP100 enclosures 14 400 GB SATA disk drive modules, offering up to 5.6

Terabytes (TB) of physical capacity per enclosure RAID Level 5 configured. RAID-10 can be configured at the

customer’s site using an optional IBM Services consultant Maximum drives supported 112 Serial ATA drives (using 8 EXP100 Expansion Units) per

DS4100 Fans Dual redundant, hot-swappable Management software IBM DS4000 Storage Manager version 9.12.65 (Special

version for exclusive use with DR550)

IBM TotalStorage SAN Switch

Two IBM TotalStorage SAN Fibre Channel Switches are used to interconnect both P5 520 servers with the DS4100s to create a SAN (dual node configurations). Tape attachment such as the 3592, TS1120 or LTO can be done using the additional ports on the switches. The switches (2005-B16) build two independent SANs, which are designed to be fully redundant for high availability. This implementation in the DR550 is designed to provide high performance, scalability, and high fault tolerance.

For the single node configurations, only one switch (2005-B16) included. This creates a single independent SAN and can be used for both disk and tape access.

The 2005-B16 is a 16-port, dual speed, auto-sensing fibre channel switch. Eight ports are populated with 2 gigabit shortwave transceivers when the DR550 is configured for single copy mode. Twelve ports are populated with 2 gigabit short wave tranceivers when the DR550 is configured for enhanced remote volume mirroring. This dual implementation is designed to provide a fault tolerant fabric topology, to help avoid single points of failure.

IBM SAN Fibre Channel Switch 2005-B16

Each switch in the DR550 comes pre-zoned by ports. Both switches are configured with distinct zones as illustrated below:

Accessing the Switch(es)

If you need to access the switch(es) to review the zoning information, error messages, or other information, you will need to connect Ethernet cables (provided by the customer) to the Ethernet port

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 11

on the switch. These cables would also need to be connected to the customer network. You can then access the switch using the IP address. The Userid is ADMIN and the password is PASSWORD. You should change this password to confirm with site security guidelines.

If you should need to review the configuration or zoning within the switches, the IP address for switch 1 is 192.168.1.31 and switch 2 (only installed in dual node configurations) is 192.168.1.32. These addresses should not be changed. To gain access to the switches via the IP network, you will need to provide Ethernet cables and ports on your existing Ethernet network. Once the connections have been made, then you can connect to the IP address and use the management tools provided by the switch.

Dual Node Zoning – without Enhanced Remote Volume Mirroring

Slot 5

0 2 3

2005-B16_2

2 3

Controller B1

Zone 1

Zone 2

Zone 3

DS4100_1

DS4100_2

0 2 3

2 3

2005-B16_1

Slot 4

Controller A1

Controller A2

Slot 1

Note: Zone 3 is configured for use with the tape (TS1120, TS3310, 358x, 3592 with WORM cartridges are recommended) - ports 5-7 are connected to the tape drives

Dual Node Zoning – with Enhanced Remote Volume Mirroring

Slot 4

Controller B2

Slot 1

Engine2Engine1 Slot 5

Zone 1

Zone 2

Zone 3

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 12

Engine1

Slot 5

Slot 4

Slot 1

Slot 5

2005-B16_1

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Not

Zoned

DS4100_1

DS4100_2

0 2

Controller A1

4 5 6 7

Controller A2

0 2

Controller B1

Connects to Switch in secondary DR550

Note: Zone 3 is configured for use with tape (TS1120, LTO Gen 3, or 3592 drives with WORM cartridges are recommended - ports 5-7 are available to connect to tape drives) Zones 4 & 5 are configured for use with data replication (DS4100 enhanced remote volume mirroring) Per IBM recommendations, the ports used to connect the switches are not included in the zones for remote mirroring

Single Node Zoning – without Enhanced Remote Volume Mirroring

Slot 4

4 5 6 7

Controller B2

Slot 1

Engine2

2005-B16_2

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Not

Zoned

Connects to Switch in secondary DR550

9131-52A

Slot 5

Slot 4

2005-B16

Zone 1

Zone 2

Zone 3

DS4100

0 2

Controller A1

Controller A2

Controller B1

Note: Zone 3 is configured for use with the tape (TS1120, TS3310, 358x, 3592 with WORM cartridges are recommended) - ports 5-7 are connected to the tape drives

Single Node Zoning – with Enhanced Remote Volume Mirroring

Slot 1

Controller B2

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 13

Switch Zoning when Remote Mirroring is installed (Factory Settings)

9131-52A

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Not

Zoned

DS4100

Slot 5

0 2

Controller A-1

4 5 6 7

Controller A-2

Slot 4

2005-B16

Controller B-1

Slot 1

Controller B-2

Connects to Switch in secondary DR550

These zoning configurations may be needed if you ever need to rezone the 2005-B16.

For more information, 2005-B16 data sheets can be downloaded from:

http://www-03.ibm.com/servers/storage/san/b_type/san16b-2/express/

Should one of the switches fail (dual node configurations only), the logical volumes within the DS4100 systems are available through the other controller and switch.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 14

Software Overview

High Availability Cluster Multi-Processing (HACMP) for AIX

The data retention application can be a business critical application. The DR550 can provide a high availability environment by leveraging the capabilities of AIX and High Availability Cluster Multi-Processing (HACMP) with dual P5 servers and redundant networks. This is referred to as the dual node configuration. IBM also offers a single node configuration that does not include HACMP.

HACMP is designed to maintain as operational applications such as System Storage Archive Manager if a component in a cluster node fails. In case of a component failure, HACMP is designed to move the application along with the resources from the active node to the standby (passive) node in the DR550.

Cluster Nodes

The two P5 520 servers running AIX with HACMP daemons are Server nodes that share resources—disks, volume groups, file systems, networks and network IP addresses.

In this HACMP cluster, the two cluster nodes communicate with each other over a private Ethernet IP network. If one of the network interface cards fails, HACMP is designed to preserve communication by transferring the traffic to another physical network interface card on the same node. If a “connection” to the node fails, HACMP is designed to transfer resources to backup node to which it has access.

In addition, heartbeats are sent between the nodes over the cluster networks to check on the health of the other cluster node. If the passive standby node detects no heartbeats from the active node, the active node is considered as failed and HACMP is designed to automatically transfer resources to the passive standby node.

Within the DR550 (dual node configuration only), HACMP is configured as follows:

• The clusters are setup in Hot Standby (active/passive) mode.

• The resource groups are setup in cascading mode.

• The volume group is setup in enhanced concurrent mode.

System Storage Archive Manager

IBM System Storage Archive Manager (this is the new name for Tivoli Storage Manager for Data Retention) is designed provide archive services and to prevent critical data from being erased or rewritten. This software can help address requirements defined by many regulatory agencies for retention and disposition of data. Key features include the following:

• Data retention protection This feature is designed to prevent deliberate or accidental deletion of data until its specified retention criterion is met. See “Data Retention Protection” for more information.

• Event-based retention policy - In some cases, retention must be based on an external event such as closing a brokerage account. System Storage Archive Manager supports event-based retention policy to allow data retention to be based on an event other than the storage of the data. See “Defining and Updating an Archive Copy Group” for more information. This feature must be enabled via the commands sent by the content management application.

• Deletion hold In order to ensure that records are not deleted when a regulatory retention period has lapsed but other requirements mandate that the records continue to be maintained, System Storage Archive Manager includes deletion hold. Using this feature will

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 15

help prevent stored data from being deleted until the hold is released. See “Deletion Hold” for more information. This feature must be enabled via the commands sent by the content management application.

• Data encryption - 144.8-bit Advanced Encryption Standard (AES) is now available for the

Archive API Client. Data can now be encrypted before transmitting to the DR550 and would then be stored on the disk/tape in an encrypted format.

While the software has been renamed, many of the supporting documents have not been renamed yet. You will see references to SSAM and TSM throughout this document. Overtime, the documentation will be updated to reflect the new naming conventions.

For more information on System Storage Archive Manager and, refer to the Tivoli Storage Manager for AIX Version 5.3 Administrator’s Guide, Administrator’s Reference and Quick Start manuals which can be found on the web at:

http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp?toc=/com.ibm.itstorage.doc/toc.xml

Select Storage Manager for Data Retention, and then Storage Manager for AIX Server and then the Administrator’s Guide

System Storage Archive Manager API Client

The System Storage Archive Manager API Client is used, in conjunction with System Storage Archive Manager server code, as the link to applications that produce or manage information to be stored, retrieved and retained. Content management applications, such as The IBM DB2® Content Manager, identify information to be retained. The content management application calls the System Storage Archive Manager (SSAM) archive API Client to store, retrieve and communicate retention criteria to the SSAM server. The SSAM API Client must be installed on the application or middleware server that is used to initiate requests to DR550. The application or middleware server must call the SSAM API to initiate a task within the DR550.

Some applications and middleware include the API client as part of their code. Others require it to be installed separately.

DS4000 Storage Manager Version 9.12.65

The DS4000 Storage Manager Version 9.12.65 software (hereafter referred to as Storage Manager) is only available as part of the DR550 and is not available for download from the web. This version has been enhanced to provide additional protection.

Storage Manager is designed to support centralized management of the DS4100s in the DR550. Storage Manager is designed to allow administrators to quickly configure and monitor storage from a Java™-based GUI interface. It is also designed to allow them to customize and change settings as well as configure new volumes, define mappings, handle routine maintenance and dynamically add new enclosures and capacity to existing volumes—without interrupting user access to data. Failover drivers, performance-tuning routines and cluster support are also standard features of Storage Manager.

Using the DS4000 Storage Manager, the DS4100 is partitioned into a single partition at the factory. As shown in later diagrams, the P5 520 servers are connected to the DS4100s via Ethernet cables. This connection is used to manage the DS4000. For the single node configuration, DS4000 Storage Manager runs in the P5 520 server. For the dual node configuration, DS4000 Storage Manager runs in both servers. Server #2 is used to manage DS4100 #1 and Server #1 is used to DS4100 #2 (if present in the configuration).

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 16

Note: only this special version of DS4000 Storage Manager should be used with the DR550. You should not use this version with other DS4000 or FAStT disk systems and should not replace this version with a standard version of DS4000 Storage Manager (even if a newer version is available).

Content Management Applications

For the DR550 to function within a customer IT environment, information appropriate to be retained must be identified and supplied to the DR550. This can be accomplished with a content management application. The content management application identifies information appropriate to be retained, and provides this information to the DR550 via the SSAM API Client.

IBM DB2 Content Manager

To assist customers in addressing needs for data retention, IBM delivers DB2 Content Manager along with business consulting services (as needed).

IBM® DB2® Content Manager provides a foundation for managing, accessing and integrating critical business information on demand. It lets you integrate all forms of content - document, web, image, rich media - across diverse business processes and applications, including Siebel, PeopleSoft and SAP. Content Manager integrates with existing hardware and software investments, both IBM and non-IBM, enabling customers to leverage common infrastructure, achieve a lower cost of ownership, and deliver new, powerful information and services to customers, partners and employees where and when needed. It is comprised of two core repository products that are integrated with System Storage Archive Manager for storage of documents into the DR550:

• DB2 Content Manager is optimized for large collections of large objects. It provides imaging, digital asset management, and web content management. When combined w/ DB2 Records Manager, it also provides a robust records retention repository for managing the retention of all enterprise documents.

• DB2 Content Manager OnDemand is optimized to manage very large collections of smaller objects such as statements and checks. It provides output and report management.

More information on the DB2 Content Manager portfolio of products can be found at the following web site: http://www-306.ibm.com/software/data/cm/

There are a number of applications that work with IBM Content Manager to deliver specific solutions. These applications are designed to use Content Manager functions and can send data to be stored in DR550.

IBM offers additional applications that are designed to work with the DR550 API. These include:

 IBM CommonStore for Exchange Server  IBM CommonStore for Lotus Domino  IBM CommonStore for SAP  IBM Content Manager for Message Monitoring and Retention (CM MMR) (with iLumin)  BRMS (iSeries) (also via IFS to BRMS)

Other Management Applications

You should consult with your application software vendor to determine if your applications support the DR550 API. A number of application providers have enhanced their software to include this support. The current list includes:

 AXS-One

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 17

 BrainTribe (formerly Comprendium)  Caminosoft  Ceyoniq  Easy Software  FIleNet  Hummingbird  Hyland Software (OnBase)  Hyperwave  IRIS Software (Documentum Connector)  MBS Technologies (iSeries Connector for IBM CM V5)  OpenText (formerly IXOS)  Princeton Softech Active Archive Solution for PeopleSoft; for Siebel; for Oracle  Saperion  SER Solutions  Symantec Enterprise Vault (formerly KVS)  Waters (Creon Labs, NuGenesis)  Windream  Zantaz

Only applications or middleware using the API can send data to DR550. Information regarding the System Storage Archive Manager API Client may be found at

xml.toc/doc.itstorage.ibm.com=/jsp?toc.index/tivihelp/infocenter/com.ibm.boulder.publib

Additional information on qualified ISVs may be found at http://www.ibm.com/storage/dr550

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 18

DR550 Offerings

DR550 is available in both single and dual node offerings. Each offering can also be customized to include support for tape, and the appropriate Ethernet connections.

DR550 Single Node Components

The single node DR550 offerings are built with the following components:

Quantity Key Hardware Components

1 7014 Model T00 RS/6000 System Rack 1 9131 Model 52A P5 520 1 1724-100 DS4100 Storage Server (includes 5.6 TB of disk capacity)

0-1 1710-10U DS4000 EXP100 Storage Expansion Unit (only installed in

11.2 TB configuration)

1 2005-B16 TotalStorage SAN Switch - with 8 shortwave transceivers

(there are 12 transceivers when enhanced RVM is included

in the order) 1 7310-CR3 eServer Hardware Management Console 1 7316-TF3 Flat Panel Monitor, Keyboard, and Mouse

The following list is a list of the actual features that are ordered for DR550 (11.2 TB). This list should not be modified in any way as part of the initial order. IBM’s eConfig tool should be used to review any changes in the official configurations. Other configurations are also available.

Product Description Qty

Management Console

7310-CR3 7310-CR3 Rack-mounted Hardware Management Console 1 0706 Integrate with IBM TotalStorage Storage DR550 1 0961 Hardware Management Console for POWER5 Licensed Machine Code 1 4651 Rack Indicator, Rack #1 1 6458 Power Cord (4M – 14Ft) 400V/14A, IEC320/C13, IEC320/C14 1 7801 Ethernet Cable, 6M, Hardware Management Console to System Unit 1 9300 Language Group, US English 1

7316-TF3 IBM 7316-TF3 Rack-Mounted Flat Panel Console Kit 1 0706 Integrate with IBM System Storage DR550 1 4202 Keyboard/Video/Mouse (LCM) Displays 1 4242 6 Foot Extender Cable for Displays 1 4269 USB Conversion Option 1 6350 Travel Keyboard, US English 1 9300 Language Group Specify – US English 1 9911 Power Cord (4M) All (Standard Cord) 1

5771-RS1 Initial Software Support 1 Year 1 0612 Per Processor Software Support 1 Year 1 7000 Agreement for MCRSA 1

DR550 Engine #1

9131-52A 9131 Model 52A 0706 Integrate with DR500 -- IBM TotalStorage 1 Retention Solution single node 1930 1024 MB (2X512MB) DIMMS, 276-PIN, 533 MHZ, 1 DDR-2 SDRAM

Description

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 19

1968 73.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 2 Assembly 1977 2 Gigabit Fibre Channel PCI-X Adapter 3 1980 POWER GXT135P Graphics Accelerator With 1 Digital Support 1983 IBM 2-Port 10/100/1000 Base-TX Ethernet 1 PCI-X Adapter 1993 IBM 4.7 GB IDE Slimline DVD-RAM Drive 1 5005 Software Preinstall 1 5159 AC Power Supply, 850 W 1 6458 Power Cable -- Drawer to IBM PDU, 14-foot, 1 250V/10A 6574 Ultra320 SCSI 4-Pack 1 7160 IBM Rack-mount Drawer Rail Kit 1 7190 IBM Rack-mount Drawer Bezel and Hardware 1 7320 One Processor Entitlement for Processor 2 Feature # 8330 7877 Media Backplane Card 1 8330 2-way 1.9 GHz POWER5 Processor Card, 36MB 1 L3 Cache 9300 Language Group Specify - US English 1

5608-ARM IBM System Storage Archive Manager 1 3868 Per Terabytes with 1 Year SW Maintenance 6

5608-AR2 TS - ARM, 1 Yr Maint 3908 Per Terabytes SW Maintenance No Charge Registration 6

5692-A5L System Software 1 0967 MEDIA 5765-G03 AIX V5.3 1 0968 Expansion pack 1 0970 AIX 5.3 Update CD 1 0975 Microcode Upd Files and Disc Tool v1.1 CD 1 1004 CD-ROM Process Charge 1 1403 Preinstall 64 bit Kernel 1 2924 English Language 1 3410 CD-ROM 1 5005 Preinstall 1 5924 English U/L SBCS Secondary Language 1

5765-G03 AIX V5 1 0034 Value Pak per Processor D5 AIX V5.3

5771-SWM Software Maintenance for AIX, 1 Year 1 0484 D5 1 Yr SWMA for AIX per Processor Reg/Ren

DS4100#1

1724-100 DS4100 Midrange Disk System 1 0707 Integrate with IBM System Storage DR550 1 2210 Short Wave SFP GBIC (LC) 2 4603 SATA 400GB/7200 Disk Drive Module 14 5605 LC-LC 5M Fibre Optic Cable 2

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 20

7711 DS4100 AIX Host Kit 1

EXP100#1

1710-10U DS4000 EXP100 Storage Expan 1 0707 Integrate with IBM System Storage DR550 1 2210 2 Gb Fibre Channel Short Wave GBIC 2 4603 SATA 400 GB/7200 Drive Module 14 5601 1M 50u Fiber Optic Cable (LC-LC) 2 9001 Attach to DS4100 1

Switch#1

2005-B16 IBM TotalStorage SAN Switch – 16 Port 1 0706 DR550 Integration 1 2414 4 Gb SW SFP Transceiver - 4 Pack 2 5605 Fibre Cable LC/LC 5m multimode 1

Rack 7014-T00 7014-T00 IBM RS/6000 Rack Model T00 1 0233 Rack Content Specify: 7316-TF3 - 1 EIA 1 0234 Rack Content Specify: 1710/10U - 3 EIA 1 0247 Rack Content Specify: 7310/CR2 - 1 EIA 1 0248 Rack Content Specify: 1 EIA 1 0254 Rack Content Specify: 1724/100 - 3 EIA 1 0257 Rack Content Specify: 9131-52A - 4 EIA 1 0706 DR550 Integration (single node) 1 6068 Front Door for 1.8 Meter Rack (Flat Black) 1 6098 Side Panel for 1.8 or 2.0 Meter Rack (Black) 2 6580 Optional Rack Security Kit 1 7188 Power Dist Unit-Side Mount, Universal UTG0247 Connector 1 9188 Power Dist Unit Specify - Base/Side Mount, Universal UTG0247 Connector 1 9300 US English Nomenclature 1 9800 United States/Canada Power Cord 1

The following table highlights the versions used in DR550.

Components Software or Firmware Levels

DS4100 NVSRAM: N1724F100R912V05

Appware: 06.12.16.00

Bootware: 06.12.16.00 DS4000 EXP100 ESM Firmware 9563 DS4000 Storage Manager Version 9.12.6500.00

Note: (this is a special version only available with DR550. It

is not specifically ordered, but included with the hardware) 2005-B16 Firmware 4.4.0e (or later) AIX 5.3 TL 04, with Atape driver 9.6.0.0 and Atldd 6.3.1.0 System Storage Archive

5.3.2.0 Manager System Storage Archive Manager Client

5.3 0.0

An integrated management console is part of the DR550 offering. An as option, limited function is available via a TTY type terminal (customer provided) such as a VT100 or an IBM 3151. The TTY terminal is connected to the P5 520 server(s) via the serial port on the front of the server. It is recommended that the integrated management console be used for all management activity.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 21

DR550 Dual Node Components

The dual node DR550 offerings are built with the following components:

Quantity Key Hardware Components

1 or 2 7014 Model T00 RS/6000 System Rack (2nd rack only included in 89.6 TB

configuration

2 9131 Model 52A P5 520

1 or 2 1724-100 DS4100 Storage Server (2nd DS4100 included in 89.6 TB

configuration)

0-14 1710-10U DS4000 EXP100 Storage Expansion Unit (1 included for

11.2 TB, 3 included for 14 TB, 7 included for 44.8 TB and 14 included for 89.6 TB configuration)

2 2005-B16 TotalStorage SAN Switch - with 8 shortwave transceivers

(there are 12 transceivers when configured for remote

mirroring) 1 7310-CR3 eServer Hardware Management Console 1 7316-TF3 Monitor, Keyboard, and Mouse

The following list is a list of the actual features that are ordered for DR550 (11.2 TB). This list should not be modified in any way as part of the initial order. IBM’s eConfig tool should be used to review the official configurations and any changes that have been implemented.

Product Description Qty

Management Console

7310-CR3 7310-CR3 Rack-mounted Hardware Management Console 1 0707 Integrate with IBM TotalStorage Storage DR550 1 0961 Hardware Management Console for POWER5 Licensed Machine Code 1 4651 Rack Indicator, Rack #1 1 6458 Power Cord (4M – 14Ft) 400V/14A, IEC320/C13, IEC320/C14 1 7801 Ethernet Cable, 6M, Hardware Management Console to System Unit 1 9300 Language Group, US English 1

7316-TF3 IBM 7316-TF3 Rack-Mounted Flat Panel Console Kit 1 0707 Integrate with IBM System Storage DR550 1 4202 Keyboard/Video/Mouse (LCM) Displays 1 4242 6 Foot Extender Cable for Displays 1 4269 USB Conversion Option 1 6350 Travel Keyboard, US English 1 9300 Language Group Specify – US English 1 9911 Power Cord (4M) All (Standard Cord) 1

5771-RS1 Initial Software Support 1 Year 1 0612 Per Processor Software Support 1 Year 1 7000 Agreement for MCRSA 1

DR550 Engine #1

9131-52A 9131 Model 52A 0706 Integrate with DR500 -- IBM TotalStorage 1 Retention Solution single node 1930 1024 MB (2X512MB) DIMMS, 276-PIN, 533 MHZ, 1 DDR-2 SDRAM 1968 73.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 2

Description

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 22

Assembly 1977 2 Gigabit Fibre Channel PCI-X Adapter 3 1980 POWER GXT135P Graphics Accelerator With 1 Digital Support 1983 IBM 2-Port 10/100/1000 Base-TX Ethernet 1 PCI-X Adapter 1993 IBM 4.7 GB IDE Slimline DVD-RAM Drive 1 5005 Software Preinstall 1 5159 AC Power Supply, 850 W 1 6458 Power Cable -- Drawer to IBM PDU, 14-foot, 1 250V/10A 6574 Ultra320 SCSI 4-Pack 1 7160 IBM Rack-mount Drawer Rail Kit 1 7190 IBM Rack-mount Drawer Bezel and Hardware 1 7320 One Processor Entitlement for Processor 2 Feature # 8330 7877 Media Backplane Card 1 8330 2-way 1.9 GHz POWER5 Processor Card, 36MB 1 L3 Cache 9300 Language Group Specify - US English 1

5608-ARM IBM System Storage Archive Manager 1 3868 Per Terabytes with 1 Year SW Maintenance 1

5608-AR2 TS - ARM, 1 Yr Maint 3908 Per Terabytes SW Maintenance No Charge Registration 1

5765-F62 HACMP V5 1 0001 Per Processor with 1 Year maintenance 1

5660-HMP HACMP Reg/Ren: 1Yr 1 0719 HACMP Base SW MAINT per proc 1Y Reg 1

5765-G03 AIX V5 1 0034 Value Pak per Processor D5 AIX V5.3

5771-SWM Software Maintenance for AIX, 1 Year 1 0484 D5 1 Yr SWMA for AIX per Processor Reg/Ren

DR550 Engine #2

9131-52A 9131 Model 52A

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 23

0706 Integrate with DR500 -- IBM TotalStorage 1 Retention Solution single node 1930 1024 MB (2X512MB) DIMMS, 276-PIN, 533 MHZ, 1 DDR-2 SDRAM 1968 73.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 2 Assembly 1977 2 Gigabit Fibre Channel PCI-X Adapter 3 1980 POWER GXT135P Graphics Accelerator With 1 Digital Support 1983 IBM 2-Port 10/100/1000 Base-TX Ethernet 1 PCI-X Adapter 1993 IBM 4.7 GB IDE Slimline DVD-RAM Drive 1 5005 Software Preinstall 1 5159 AC Power Supply, 850 W 1 6458 Power Cable -- Drawer to IBM PDU, 14-foot, 1 250V/10A 6574 Ultra320 SCSI 4-Pack 1 7160 IBM Rack-mount Drawer Rail Kit 1 7190 IBM Rack-mount Drawer Bezel and Hardware 1 7320 One Processor Entitlement for Processor 2 Feature # 8330 7877 Media Backplane Card 1 8330 2-way 1.9 GHz POWER5 Processor Card,36MB 1 L3 Cache 9300 Language Group Specify - US English 1

5765-G03 AIX V5 1 0034 Value Pak per Processor D5 AIX V5.3

5771-SWM Software Maintenance for AIX, 1 Year 1 0484 D5 1 Yr SWMA for AIX per Processor Reg/Ren

5765-F62 HACMP V5 1 0001 Per Processor with 1 Year maintenance 1

5660-HMP HACMP Reg/Ren: 1Yr 1 0719 HACMP Base SW MAINT per proc 1Y Reg 1

DS4100#1

1724-100 DS4100 Midrange Disk System 1 0707 Integrate with IBM System Storage DR550 1

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 24

2210 Short Wave SFP GBIC (LC) 2 4603 SATA 400GB/7200 Disk Drive Module 14 5605 LC-LC 5M Fibre Optic Cable 2 7711 DS4100 AIX Host Kit 1

EXP100#1

Switch#1

2005-B16 IBM TotalStorage SAN Switch – 16 Port 1 0707 DR550 Integration 1 2414 4 Gb SW SFP Transceiver - 4 Pack 2 5605 Fibre Cable LC/LC 5m multimode 3

Switch#2

2005-B16 IBM TotalStorage SAN Switch – 16 Port 1 0707 DR550 Integration 1 2414 4 Gb SW SFP Transceiver - 4 Pack 2 5605 Fibre Cable LC/LC 5m multimode 3

Rack 7014-T00 7014-T00 IBM RS/6000 Rack Model T00 1 0233 Rack Content Specify: 7316-TF3 - 1 EIA 1 0234 Rack Content Specify: 1710/10U - 3 EIA 1 0247 Rack Content Specify: 7310/CR2 - 1 EIA 1 0248 Rack Content Specify: 1 EIA 2 0254 Rack Content Specify: 1724/100 - 3 EIA 1 0257 Rack Content Specify: 9131-52A - 4 EIA 2 0707 DR550 Integration (dual node) 1 6068 Front Door for 1.8 Meter Rack (Flat Black) 1 6098 Side Panel for 1.8 or 2.0 Meter Rack (Black) 2 6580 Optional Rack Security Kit 1 7188 Power Dist Unit-Side Mount, Universal UTG0247 Connector 1 9188 Power Dist Unit Specify - Base/Side Mount, Universal UTG0247 Connector 1 9300 US English Nomenclature 1 9800 United States/Canada Power Cord 1

Other configurations are available, using different amounts of DS4000 EXP100 and DS4100.

The following table highlights the versions used in DR550.

Components Software or Firmware Levels

DS4100 NVSRAM: N1724F100R912V05

Appware: 06.12.16.00

Bootware: 06.12.16.00 DS4000 EXP100 ESM Firmware 9563 DS4000 Storage Manager Version 9.12.6500.00

Note: (this is a special version only available with DR550. It

is not specifically ordered, but included with the hardware)

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 25

2005-B16 Firmware 4.4.0e (or later) AIX 5.3 TL 04, with Atape driver 9.6.0.0 and Atldd 6.3.1.0 HACMP 5.3 + PTFs System Storage Archive

5.3.2.0 Manager System Storage Archive

5.3.0.0 Client

An integrated console is part of the DR550 offering. As an option, limited function is available via a TTY type terminal (customer provided) such as a VT100 or an IBM 3151. If this option is used, the TTY terminal is connected to the serial port on the front of the P5 520 server. It is recommended that the integrated management console be used for all management activity.

DS4100 Logical Volume Configurations

On the DR550, LUNs will be configured based on the total storage capacity ordered. All disk capacity is allocated for use by TSM. No disk capacity is set aside for other applications or servers. Below are the approximate LUN configurations set at the factory. The LUN id column shows the LUN id as seen from DS4000 Storage Manager. If you view the LUN id from AIX, it will be displayed as a hexadecimal address.

For 5.6 TB System (single or dual node configurations)

LUN size LUN ID Hdisk on AIX Logical Volume File System VG Name

2 GB 0 hdisk2 tsmappslv /tsm TSMApps

115 GB

300 GB 2035 GB 2035 GB

380* GB

1 2 3 4 5

For 11.2 TB System (single or dual node configurations)

LUN size LUN ID Hdisk on AIX Logical Volume File System VG Name

2 GB 0 hdisk2 tsmappslv /tsm TSMApps

115 GB

300 GB 2035 GB 2035 GB

380* GB 2035 GB 2035 GB

600* GB

1 2 3 4 5 6 7 8

For 22.4 TB System (dual node configurations only)

LUN size LUN ID Hdisk on AIX Logical Volume File System VG Name

2 GB 0 hdisk2 tsmappslv /tsm TSMApps

315 GB

900 GB 2035 GB 2035 GB

380* GB

2035 GB

1900* GB

2035 GB

1 2 3 4 5 6 7 9

hdisk3 hdisk4 hdisk5 tsmstglv1 hdisk6 tsmstglv2 hdisk7 tsmstglv3

hdisk3 hdisk4 hdisk5 tsmstglv1 hdisk6 tsmstglv2 hdisk7 tsmstglv3 hdisk8 tsmstglv4 hdisk9 tsmstglv5

hdisk10 tsmstglv6

hdisk3 hdisk4 hdisk5 tsmstglv1 hdisk6 tsmstglv2 hdisk7 tsmstglv3 hdisk8 tsmstglv4 hdisk9 tsmstglv5

hdisk10 tsmstglv6

tsmdblv tsmloglv /tsmDb /tsmLog TSMDbLogs

tsmdbbkuplv /tsmdbbkup TSMDbBkup

tsmdblv tsmloglv /tsmDb /tsmLog TSMDbLogs

tsmdbbkuplv /tsmdbbkup TSMDbBkup

tsmdblv tsmloglv /tsmDb /tsmLog TSMDbLogs

tsmdbbkuplv /tsmdbbkup TSMDbBkup

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 26

2035 GB

600* GB 2035 GB 2035 GB

600* GB

10 11 11 12 13

hdisk11 tsmstglv7 hdisk12 tsmstglv8 hdisk13 tsmstglv9 hdisk14 tsmstglv10 hdisk15 tsmstglv11

For 44.8TB System (dual node configurations only)

LUN size LUN ID Hdisk on AIX Logical Volume File System VG Name

2 GB 0 hdisk2 tsmappslv /tsm TSMApps

415 GB 1200 GB 2035 GB 2035 GB

280* GB

2035 GB

1600* GB

2035 GB 2035 GB

600* GB 2035 GB 2035 GB

600* GB

1 2 3 4 5 6 7 8

9 10 11 12 13 14 15 16 17 18 19 20 21 22

hdisk3 hdisk4 hdisk5 tsmstglv1 hdisk6 tsmstglv2 hdisk7 tsmstglv2 hdisk8 tsmstglv3

hdisk9 tsmstglv4 hdisk10 tsmstglv6 hdisk11 tsmstglv7 hdisk12 tsmstglv8 hdisk13 tsmstglv9 hdisk14 tsmstglv10 hdisk15 tsmstglv11 hdisk16 tsmstglv12 hdisk17 tsmstglv13 hdisk18 tsmstglv14 hdisk19 tsmstglv15 hdisk20 tsmstglv16 hdisk21 tsmstglv17 hdisk22 tsmstglv18 hdisk23 tsmstglv19 hdisk24 tsmstglv20

tsmdblv tsmloglv /tsmDb /tsmLog TSMDbLogs

tsmdbbkuplv /tsmdbbkup TSMDbBkup

For 89.6 TB System (dual node configurations only)

LUN size LUN ID Hdisk on AIX Logical Volume File System VG Name

2 GB 0 hdisk2 tsmappslv /tsm TSMApps

415 GB 1200 GB 2035 GB 2035 GB

280* GB 2035 GB 1600 GB 2035 GB 2035 GB

600* GB 2035 GB 2035 GB

1 2 3 4 4 5 6 8

9 10 11 12 13 14 15 16 17 18

hdisk3 hdisk4 hdisk5 tsmstglv1 hdisk6 tsmstglv2 hdisk7 tsmstglv3 hdisk8 tsmstglv4

hdisk9 tsmstglv5 hdisk10 tsmstglv6 hdisk11 tsmstglv7 hdisk12 tsmstglv8 hdisk13 tsmstglv9 hdisk14 tsmstglv10 hdisk15 tsmstglv11 hdisk16 tsmstglv12 hdisk17 tsmstglv13 hdisk18 tsmstglv14 hdisk19 tsmstglv15 hdisk20 tsmstglv16

tsmdblv tsmloglv /tsmDb /tsmLog TSMDbLogs

tsmdbbkuplv /tsmdbbkup TSMDbBkup

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 27

600* GB 2035 GB 2035 GB

600* GB

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

hdisk21 tsmstglv17 hdisk22 tsmstglv18 hdisk23 tsmstglv19 hdisk24 tsmstglv20 hdisk25 tsmstglv21 hdisk26 tsmstglv22 hdisk27 tsmstglv23 hdisk28 tsmstglv24 hdisk29 tsmstglv25 hdisk30 tsmstglv26 hdisk31 tsmstglv27 hdisk32 tsmstglv44.8 hdisk33 tsmstglv29 hdisk34 tsmstglv30 hdisk35 tsmstglv31 hdisk36 tsmstglv32 hdisk37 tsmstglv33 hdisk38 tsmstglv34 hdisk39 tsmstglv35 hdisk40 tsmstglv36 hdisk41 tsmstglv37 hdisk42 tsmstglv38 hdisk43 tsmstglv39 hdisk44 tsmstglv40 hdisk45 tsmstglv41 hdisk46 tsmstglv42 hdisk47 tsmstglv43 hdisk48 tsmstglv44

Note* the actual size of the last LUN in each disk drawer is an approximate value. The actual size may be slightly different from what is published.

Backup times for the SSAM data base will vary, depending on the used portion of the allocated space. As the data base fills up (could take years to do this, you should expect longer backup times.

AIX settings

The following has been setup for the AIX server(s)

• Paging space has been increased by 1536 MB. Now DR550 has a paging space of 1536 + 512 = 2048 MB paging space.

• Changed TCP parameter in AIX rfc1323 = 1 <==== the default value was 0.

In addition, FTP and Telnet services have been shut down. All other ports/sockets are blocked with the exception of those needed by AIX, HACMP and System Storage Archive Manager

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 28

System Storage Archive Server Configuration

The System Storage Archive Manager Server settings on the DR550 are (these settings are different than the default settings. Other parameters use the default settings.

ARCHIVERETENTIONPROTECTION ON TCPWINDOWSIZE 63 TCPNODELAY YES BUFFERPOOL 512000 SELFTUNEBUFPOOLSIZE NO TXNGRPMAX 512 COMMTIMEOUT 300 DBPAGE SHADOW YES MAX SESSIONS 100

The following files have been set at the factory:

1. Defined /tsm/files/devconfig (keeps System Storage Archive Manager device configuration

to help in rebuilding the System Storage Archive Manager server within DR550 in case of System Storage Archive Manager server loss).

2. Defined /tsm/files/volhist (keeps track of volumes used by System Storage Archive

Manager).

See the Tivoli Storage Manager for AIX Administrator’s Guide and Reference manuals for information on customizing these settings for your needs.

System Storage Archive Manager Database and Logs

For the DR550 configurations (5.6 TB and 11.2 TB), a 100 GB logical volume for the SSAM database and a 15 GB logical volume for the SSAM log have been preconfigured. For the 22.4 TB configuration, a 300 GB logical volume for the SSAM database and a 15 GB logical volume for the SSAM log has been preconfigured. For the 44.8 and 89.6 TB configurations, a 400 GB logical volume for the SSAM database and 15 GB logical volume for the SSAM log have been preconfigured. The System Storage Archive Manager database and log volumes are configured using DS4000 RAID5 storage. System Storage Archive Manager mirroring for the database and log volumes is not configured.

System Storage Archive Manager Disk Storage Pool

The DR550 has been preconfigured with a single disk storage pool (ARCHIVEPOOL). The raw logical volumes in the table above have been defined into the ARCHIVEPOOL.

System Storage Archive Manager Storage Management Policy

The DR550 default policy is defined (all are named STANDARD) and the Archive Copy Group in the STANDARD Management Class specifies the following:

Data is stored into ARCHIVEPOOL A chronological retention policy to retain the data for 365 days

See the Tivoli Storage Manager for AIX Administrator’s Reference, Guide, and Quick Start manual for more information on customizing the System Storage Archive Manager policy for your data environment.

Automated System Storage Archive Manager Operations

DR550 includes schedules used to automate System Storage Archive Manager server administrative commands. The schedules specify that the operations start and stop during defined time periods. You may want to change these start and stop windows to suit your situation. See the

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 29

TSM for AIX Administrator’s Guide and Reference manuals for help in modifying the administrative schedules.

Examples of schedules that are setup in the DR550 are:

 Backup of the System Storage Archive Manager database is scheduled to run daily at

8am.

 Maintain 3 copies of backup and delete older versions (scheduled a job to run daily at

23:59). Note: It is the responsibility of the customer to set up and verify schedules and database backups. You should verify that you have appropriate schedules in place to back up your database.

Routine Operations for System Storage Archive Manager

Monitoring the Database and Recovery Log Status

Monitor the System Storage Archive Manager database and recovery usage log to ensure that you have enough space available for efficient operation. You should pay particular attention to the maximum utilization percentage (%Util) for both. If more room is needed in that database or recovery log, shift resources by using the administrator functions outlined in the Tivoli Storage Manager for AIX Administrator’s Guide and Reference manuals.

Monitoring Disk Volumes

Monitor the status of the volumes for the Tivoli Storage database, recovery log, and the ARCHIVEPOOL storage pool. If any volumes have a status of Offline or Stale, you must determine why and correct the situation.

Monitoring the Results of Scheduled Operations

Monitor scheduled administrative to ensure that the schedules are running successfully. This is particularly relevant if you have set up scheduled backups of the database.

Installing and Setting Up System Storage Archive Manager API Clients

The DR550 storage interface is the System Storage Archive Manager API Client. You may need to install the System Storage Archive Manager API Client V5.2.2 or later on the server(s) that are sending data to the DR550. Your software vendor may offer specific recommendations for defining System Storage Archive Manager storage management policies, the System Storage Archive Manager client node names, and System Storage Archive Manager client Include-Exclude lists. You will also need to point to the network address of the DR550 in the System Storage Archive Manager Client Communications Options definition.

The following web based education is available from Tivoli and may be beneficial in providing more information on System Storage Archive Manager. The site for web based training for externals is

the Virtual Tivoli Skill Center- cgse1.cgselearning.com/tivoliskills

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 30

Installation and Activation

Safety Notices

A danger notice indicates the presence of a hazard that has the potential of causing death or serious injury. A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury. Note: For a translation of these notices, see System Unit Safety Information, order number SA23-

2652.

Electrical Safety

Observe the following safety instructions any time you are connecting or disconnecting devices attached to the workstation.

DANGER

• An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock.

• Before installing or removing signal cables, ensure that the power cables for the system unit and all attached devices are unplugged.

• When adding or removing any additional devices to or from the system, ensure that the power cables for those devices are unplugged before the signal cables are connected. If possible, disconnect all power cables from the existing system before you add a device.

• Use one hand, when possible, to connect or disconnect signal cables to prevent a possible shock from touching two surfaces with different electrical potentials.

• During an electrical storm, do not connect cables for display stations, printers, telephones, or station protectors for communications lines.

CAUTION: This product is equipped with a three-wire power cable and plug for the user’s safety. Use this power cable with a properly grounded electrical outlet to avoid electrical shock.

DANGER: To prevent electrical shock hazard, disconnect all power cables from the electrical outlet before relocating the system.

Laser Safety Information

CAUTION: This product contains a CD-ROM and a laser module on a PCI card, which are class 1

laser products.

Laser Compliance

All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with the IEC 825 (first edition 1984) as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information.

CAUTION: All IBM laser modules are designed so that there is never any human access to laser radiation above a class 1 level during normal operation, user maintenance, or prescribed service conditions. Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. Only trained service personnel should perform the inspection or repair of optical fiber cable assemblies and receptacles.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 31

Site Preparation and Planning

Before you install the IBM System Storage DR550 we recommend that you consider several things to avoid problems during the installation and configuration. The DR550 comes as an almost ready to use system with a complete assembled hardware in a rack (or two) and preconfigured software. Nevertheless we review some topics of importance when planning for the physical installation and configuration of the IBM System Storage DR550 within your environment.

Planning to be done is centered on integrating the rack(s) into the operational IT environment. The racks themselves are already assembled. To integrate the rack(s) into your environment you have to plan or validate the following:

• The size of the floor area required by the DR550 rack(s)

– Floor load capacity – Space needed for expansion – Service clearance – Check for potential clearance problems along the access route

• The power requirements

– Multiple 208 volt or 220 volt 30 amp (single phase) power service feeds

 2 feeds for 5.6, 11.2 and 22.4 TB configurations (both dual engine and single

engine configurations)

 4 feeds for 89.6 TB configurations

– Each feed of a pair are recommended to be on a different AC power feed for

increased availability

– Power cords are shipped with each rack

• Climate control is required (Environmental Class A)

• Cables and Connectors

– RJ-45 to 9-pin converter cable to administer from the front serial port of pSeries

(included) – this is an option that only offers limited functions

• The network environment

– IP addresses – Check for address conflicts before cabling to your network

The table below shows selected factory IP address settings and provides a column to enter the IP addresses to be used later when configuring the DR550. Other IP addresses within DR550 do not need to be changed.

Dual Node Configuration

IP Description IP Address from Factory IP Address in Network

drs_engine1_boot 192.168.1.21 drs_engine1_stdby 192.168.2.10 drs_engine2_boot 192.168.1.23 drs_engine2_stdby 192.168.2.11 drs_cluster_svc 192.168.1.22

Single Node Configuration

IP Description IP Address from Factory IP Address in Network

drs_engine 192.168.1.11

Refer to Configuring the System (P5 520 Servers) section for additional information on IP addresses used for the DR550.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 32

Unpacking and Installing the Rack(s)

The DR550 comes integrated into one or two 7014 racks (single node configurations and the 5.6,

11.2, 22.4 and 44.8 TB dual node configurations are always shipped in one rack, while the dual node 89.6 TB configuration ships in two racks). Unpack Instructions are located in the transparent sleeve on the exterior of the rack shipping carton. This provides the information necessary to unpack and remove the rack(s) from the palette. Shipped with each DR550 is a printed copy of the 7014 Series Model T00 and Model T42 System Rack Installation Guide (SA38-0641). This installation guide provides detailed instructions for positioning, leveling, powering up and checking out the DR550 racks. A subset of these instructions is contained within and will be sufficient for installing and setting up the DR550.

Positioning the Rack

After the rack has been placed into its location on the floor, lock each caster by tightening the locking screw. See the following illustration for the locking screw location. Remove all of the tape and packing materials from the rack.

1 Caster 2 Locking Screw

7014 Model T00 Positioning

Use the following to determine the next step:

• If the rack is being bolted to a concrete floor, go to “Attach the Rack to a Concrete Floor”.

• If the rack is being bolted to a concrete floor beneath a raised floor, go to “Attach the Rack to

a Concrete Floor Beneath a Raised Floor”

• If the rack is not being attached to the floor, go to “Level the Rack”

Leveling the Rack

To level the rack, do the following:

1. Loosen the jam nut on each leveling foot.

2. Rotate each leveling foot downward until it contacts the surface on which the rack is placed.

3. Adjust the leveling feet downward as needed until the rack is level. When the rack is level, tighten the jam nuts against the base.

1 Rack Front (base) 2 Leveling Foot (quantity 4) 3 Jam Nut (quantity 4)

7014 Model T00 Leveling

Attach the Stabilizers

Stabilizer plates are only used if you will not be bolting the rack to the floor. If you are going to bolt the rack to the floor, go to “Attach the Rack to a Concrete Floor”.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 33

CAUTION: The stabilizer must be firmly attached to the bottom rear of the rack to prevent the rack from turning over when the drawers are pulled out of the rack. Do not pull out or install any drawer or feature if the stabilizer is not attached to the rack.

To attach the stabilizers to the bottom of the rack, do the following:

1. Align the slots in the stabilizer with the mounting holes at the bottom front of the rack.

2. Install the two mounting screws.

3. Ensure that the base of the stabilizer rests firmly on the floor. Use the Allen wrench that was supplied with the rack to tighten the mounting screws alternately until they are tight.

4. To install the stabilizer on the rear of the rack, repeat sub steps 1 through 3.

5. Go to “Connect the Power Distribution System”

Attaching the Rack to a Concrete Floor

Obtain the services of a mechanical contractor to attach the rack-mounting plates to the concrete floor. The mechanical contractor needs to determine that the hardware being used to secure the rack-mounting plates to the concrete floor is sufficient to meet the requirements for the installation. To attach the rack to a concrete floor, do the following:

1. Put the rack in its predetermined location and tighten the locking screws on the casters.

2. If installed, remove the top, left and right trim panels. The trim panels are held in place with spring clips. See the illustration below.

3. Remove the front and rear doors. To remove a rack door, go to “Attaching Rack Doors”. After the rack doors have been removed, go to sub step 4. Note: Remember to have the door keys delivered to the appropriate persons.

4. Locate the hardware mounting kit and the two mounting plates. Refer to the following illustration when reviewing the contents of the hardware mounting kit. The mounting hardware kit contains the following:

a. 4 Rack-mounting bolts b. 4 Thin washers c. 8 Plastic isolator bushings d. 4 Thick washers e. 4 Spacer

Note: If you are installing an ac-powered rack, temporarily install the lower plastic isolator bushings to help you locate the rack mounting plate. After the mounting plate has been correctly located remove the lower plastic isolator bushings.

5. Position the two mounting plates in the approximate mounting location under the rack.

6. Create a rack-mounting bolt assembly by adding the following items, in the order listed, to each rack-mounting bolt

a. Thin flat washer b. Top plastic isolator bushing c. Thick flat washer

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 34

d. Spacer

667

1 T00 Rack Chassis 2 Rack-Mounting Bolt 3 Thin Washer 4 Top Plastic Isolator

Bushing 5 Spacer 6 Jam Nut

7 Leveling Foot

1 Rack Chassis 2 Top Trim Panel 3 Left Side Trim Panel 4 Right Side Trim Panel 5 Spring Clip

7. Insert a rack-mounting bolt assembly through each of the leveling feet.

8. Reposition the rack-mounting plates under the four rack-mounting bolts so that the mounting bolts are centered directly over the threaded bolt holes.

9. Turn the rack-mounting bolts 4 complete turns into the mounting plates threaded bolt holes.

10. Mark the floor around the edges of both rack-mounting plates.

1 Rack-Mounting Bolt

1 2

3 4

6 7

144

2 Thin Washer 3 Top Plastic Isolator Bushing 4 Thick Washer 5 Spacer 6 Jam Nut 7 Leveling Foot 8 Mounting Plate 9 Threaded Hole (Used to secure

the rack to mounting plate.)

10 Anchor Bolt Hole 11 Traced Pattern (Pattern to be

traced onto the floor using the

mounting plate as a template)

11. Mark the plate bolt-down holes that are accessible through the opening in the rear of the rack.

12. Remove the rack-mounting bolt assemblies.

13. If you are installing an ac-powered rack, remove the bottom isolator bushing from each of the leveling feet. If you are installing a dc-powered rack the bottom isolator bushings must remain installed in each of the leveling feet.

14. Remove the rack-mounting plates from the marked locations.

15. Loosen each of the locking screws on the casters.

16. Move the rack so that it is clear of both areas that were marked on the floor for the rackmounting plate locations.

17. Reposition the mounting plates within the marked areas.

18. Mark the floor at the center of all holes in both rack-mounting plates.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 35

19. Remove the two rack-mounting plates from the marked areas.

20. At the marked location of the threaded rack-mounting bolt holes, drill four clearance holes into the concrete floor. Each clearance hole should be approximately one inch deep. This allows the rack-mounting bolts enough room to protrude past the thickness of the mounting plate. Note: You must use a minimum of two anchor bolts for each rack-mounting plate to securely attach the plate to the concrete floor. Because some of the holes in each rack-mounting plate may align with concrete reinforcement rods embedded in the concrete, some of the rack-mounting plate holes may not be usable.

21. Select at least two suitable hole locations for each rack-mounting plate bolt. The selected locations should be as close to the threaded bolt holes as possible. Be sure that the holes selected at the rear of the rack are accessible. Drill holes at the selected locations into the concrete floor. Note: The size of the anchor bolts and concrete anchors must be determined by the mechanical contractor doing the installation.

22. Position the front-mounting plate over the concrete anchors.

23. Securely bolt the front rack-mounting plate to the concrete floor.

24. Position the rear-mounting plate over the concrete anchors.

25. Securely bolt the rear rack-mounting plate to the concrete floor. Note: The size of the anchor bolts and concrete anchors must be determined by the mechanical contractor doing the rack-mounting plate installation.

26. Position the rack over the rack-mounting plates.

27. Insert each of the rack-mounting bolts through a flat washer, a plastic isolator bushing and a thick washer, and through a leveling foot.

28. Align the four rack-mounting bolts with the four tapped holes in the two mounting plates and turn three to four rotations.

29. Tighten the locking screw on each caster.

30. Adjust the leveling feet downward as needed until the rack is level. When the rack is level, tighten the jam nuts against the base of the rack.

1 Rack Front (base) 2 Leveling Foot (quantity 4) 3 Jam Nut (quantity 4)

31. If you have multiple racks that are connected in a suite (bolted to each other), go to “Installing Multiple Racks Connected in a Suite”. Otherwise, torque the four bolts to 40-50 ftlbs (54-67 nm).

32. If you are not installing doors on your rack, install the top, left, and right trim panel.

33. Connect the power distribution system as described in “Connect the Power Distribution System”.

34. After all racks are bolted down, go to “Attaching Front or Rear AC Electrical Outlet”.

35. If you are not going to attach a front electrical outlet and you are installing rack doors, go to “Attaching Rack Doors”

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 36

Attach the Rack to a Concrete Floor Beneath a Raised Floor

To attach the rack to a concrete floor, do the following:

1. Put the rack in its predetermined location and tighten the locking screws on the casters.

2. If installed, remove the top, left and right trim panels. The trim panels are held in place with spring clips. See the following illustration.

3. If installed, remove the front and rear doors. To remove a rack door, go to “Attaching Rack Doors”. After the rack doors have been removed, go to the next sub step.

4. Remove the front and rear doors. To remove a rack door, go to “Attaching Rack Doors”. After the rack doors have been removed, go to sub step 4.

5. Locate the hardware mounting kit and the two mounting plates. Refer to the following illustration when reviewing the contents of the hardware mounting kit. The mounting hardware kit contains the following:

a. 4 Rack-mounting bolts b. 4 Thin washers c. 8 Plastic isolator bushings d. 4 Thick washers e. 4 Spacer

6. Position the two mounting plates in the approximate mounting location under the rack.

667

1 T00 Rack Chassis 2 Rack-Mounting Bolt 3 Thin Washer 4 Top Plastic Isolator

Bushing 5 Spacer 6 Jam Nut

7 Leveling Foot

1 Rack Chassis 2 Top Trim Panel 3 Left Side Trim Panel 4 Right Side Trim Panel 5 Spring Clip

7. Create a rack-mounting bolt assembly by adding the following items, in the order listed, to each rack-mounting bolt

a. Thin flat washer b. Top plastic isolator bushing c. Thick flat washer d. Spacer

8. Insert a rack-mounting bolt assembly through each of the leveling feet.

9. Reposition the rack-mounting plates under the four rack-mounting bolts so that the mounting bolts are centered directly over the threaded bolt holes.

10. Turn the rack-mounting bolts 4 complete turns into the mounting plates threaded bolt holes.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 37

11. Mark the floor around the edges of both rack-mounting plates.

12. Mark the plate bolt-down holes that are accessible through the opening in the rear of the rack.

13. Remove the rack-mounting bolt assemblies.

14. If you are installing an ac-powered rack, remove the bottom isolator bushing from each of the leveling feet. If you are installing a dc-powered rack the bottom isolator bushings must remain installed in each of the leveling feet.

15. Remove the rack-mounting plates from the marked locations.

16. Loosen each of the locking screws on the casters.

17. Move the rack so that it is clear of both areas that were marked on the floor for the rackmounting plate locations.

18. Reposition the mounting plates within the marked areas.

19. Mark the floor at the center of all holes in both rack-mounting plates.

20. Remove the two rack-mounting plates from the marked areas.

21. Drill two clearance holes on each end of each rack-mounting plate. The drilled holes should be approximately 1 inch deep. This will accommodate any rack-mounting bolt extending past the rack-mounting plate when securing the rack to the rack-mounting plate.

22. For each rack-mounting plate, select at least two suitable hole locations. Select the hole locations as close to the threaded hole areas as possible. Be sure the hole locations selected at the rear of the rack are accessible.

23. Drill pass-through holes in the raised-floor panel. The pass-through holes allow the anchorbolts to be inserted into the rack-mounting plate and pass through the raised floor panel to the concrete floor. Note: You must use a minimum of two anchor bolts for each rack-mounting plate to securely attach the rack-mounting plate through the raised-floor panel to the concrete floor. Because some of the holes in each rack-mounting plate may align with concrete reinforcement rods imbedded in the concrete, some of the rack-mounting plate holes may not be usable.

1 Rack-Mounting Bolt

1 2

3 4

6 7

144

2 Thin Washer 3 Top Plastic Isolator Bushing 4 Thick Washer 5 Spacer 6 Jam Nut 7 Leveling Foot 8 Mounting Plate 9 Threaded Hole (Used to secure

the rack to mounting plate.) 10 Anchor Bolt Hole 11 Traced Pattern (Pattern to be

traced onto the floor using the mounting plate as a template)

24. Transfer the locations of the anchor bolt holes (exclude the clearance holes drilled for the rack-mounting bolts) from the raised-floor panel to the concrete floor directly beneath, and mark the hole locations on the concrete floor.

25. Drill holes in the concrete floor to secure the anchor bolts.

26. Position the raised-panel floor back into position over the anchor bolt holes.

27. Position the front-mounting plate within the marked area on the raised-panel floor.

28. Using your anchor bolts, secure the front rack-mounting plate on top of the raised floor and through to the concrete floor.

29. Position the rear-mounting plate within the marked area on the raised-panel floor.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 38

30. Using your anchor bolts, secure the rear rack-mounting plate on top of the raised floor and through to the concrete floor.

31. Replace all raised panels that may have been removed when aligning and securing the anchor bolts to the concrete floor.

32. Align the rack over the front and rear-mounting plates.

33. Insert each of the rack-mounting bolts assemblies through a leveling foot.

34. Align the rack-mounting bolts with the threaded holes in each rack-mounting plate. Turn each rack-mounting bolt three to four rotations.

36. Tighten the locking screw on each caster.

37. Adjust the leveling feet downward as needed until the rack is level. When the rack is level, tighten the jam nuts against the base of the rack.

38. If you have multiple racks that are connected as a suite (bolted to each other), go to “Installing Multiple Racks Connected in a Suite”. Otherwise torque the four bolts to 40-50 ftlbs (54-67 nm).

39. If you are not installing doors on your rack, install the top, left, and right trim panel.

40. Connect the power distribution system as described in “Connect the Power Distribution System”

41. After the rack is bolted down and you are going to attach a front electrical outlet, go to “Attaching Front or Rear AC Electrical Outlet”.

42. If you are not going to attach a front electrical outlet and you are installing rack doors, go to “Attaching Rack Doors”.

Connecting the Racks in a Suite (applies only to dual node 89.6 TB Configuration)

If you are installing a suite of racks, do the following:

1. If they are installed, remove the side panels from each rack. To remove the side panels:

a. Lift the two panel-release tabs up. See the following illustration for the two panel

release tab locations.

b. Pull the panel up and away from the rack chassis. This motion will release the panel

from the two

2. Lower J brackets. Store the side panels away from the work area.

3. Remove the two Z brackets and the two J brackets. These brackets are used to hang the side panels. See the following illustration.

4. Stand facing the first rack and locate the right side.

5. Install a standoff in the upper-left corner and lower-right corner of the first rack. See the following illustration for standoff placement locations.

6. Locate the second rack’s left side.

7. Install a standoff in the upper-left corner and lower-right corner of the second rack.

8. Attach the long foam strip as shown in the following illustration. Position the racks together.

9. Align the standoff holes. To align the standoff holes, you may have to adjust the leveling feet.

10. Install a screw and washer in all four standoff hole positions, as shown in the following illustration, but do not tighten. After the racks are bolted together, level the racks.

11. Tighten the four screws in the standoff holes.

12. Install the trim pieces that fit between the front and back racks.

13. Install the trim piece that fits on top and between the racks.

14. Install rack filler panels above and below the installed system drawers. The filler panels cover and seal the open areas at the front of the rack(s). Note: All open areas located in the front of the rack must also be sealed to ensure that proper airflow within the rack is maintained.

15. Connect the cables that go between the racks.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 39

16. If you are bolting down the racks, go to either “Attach the Rack to a Concrete Floor” or “Attach the Rack to a Concrete Floor Beneath a Raised Floor“ as appropriate in the 7014

Series Model T00 and Model T42 System Rack Installation Guide – SA38-0641.

17. If the rack does not have a front door, install the top, left, and right trim panels on all racks. If your rack is configured with a front door, wait until you get to step eight before installing it.

18. If you are installing stabilizers, go to “Step 4. Attach the Stabilizers” in the 7014 Series Model T00 and Model T42 System Rack Installation Guide – SA38-0641.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 40

Cabling between the Racks

This section is only applicable to the dual node 89.6 TB configuration of the DR550. At 44.8 TBs of raw capacity, the first rack is fully populated. Thus to expand the storage capacity beyond 44.8 TBs, an additional rack is required. Cabling between the racks is accomplished with two LC-LC Fibre Channel Cables provided with the DR550 and two Ethernet crossover cables (also provided with the DR550). The cabling between the racks accomplishes two objectives:

• Connects the second DS4100 to the Fibre channel SAN switches (2005-H08s)

• Connects the second DS4100 to the Ethernet ports on the P5 520 server

To connect RACK1 with RACK2, the following four connections should be made:

Rack / EIA Device Connector Rack / EIA Device Connector

RACK2 / EIA1 DS4100_2

Host 1 RACK1 / EIA17 SAN Switch_1 Port_3

Ctrl_A

RACK2 / EIA1 DS4100_2

Host 1 RACK1 / EIA23 SAN Switch_2 Port_3

Ctrl_B

RACK2 / EIA1 DS4100_2

Ethernet RACK1 / EIA13

DR_Engine_1

Ethernet

Ctrl_A

RACK2 / EIA1 DS4100_2

Ethernet RACK1 / EIA13

DR_Engine_1

Ethernet

Ctrl_B

It is the customer’s responsibility to connect these cables. The following diagram

shows the required FC connections. Orange (dotted) cables represent fibre channels connections. The black (thin) connections have been done in manufacturing.

89.6 TB Rack FC Interconnections

EXP100_1,6

IN OUT

EXP100_1,5

EXP100_1,4

0 1 2 3 4 5 6 7

DRS_ Engine _2

0 1 2 3 4 5 6 7

DRS_ Engine _1

IN OUT

EXP100_1,3

EXP100_1,2

EXP100_1,1

OUT

IN OUT

IN O UT

IN OUT

7316-TF3

Switch_2

1 2 3 4 5 6

7310-CR 3

Switch_1

1 2 3 4 5 6

IN O UT

OUT

IN OUT

EXP100_2,7

EXP100_2,6

EXP100_2,5

EXP100_2,4

EXP100_2,3

EXP100_2,2

EXP100_2,1

OUT

IN OUT

IN O UT

OUT

DS4100_1

DS4100_2

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 41

The following diagram shows the required Ethernet connections (green solid lines) that must be done by the customer between the racks.

8 9 .6 T B R a c k E th e r n e t In te rc o n n e c tio n s

IN O U T

E XP 1 00 _ 1,6

IN O U T

E XP 1 00 _1 ,6

IN O U T

E XP 1 00 _ 1, 5

IN O U T

E XP 1 00 _ 1, 4

0 1 2 3 4 5 6 7

D R S _ E n gi ne _ 2

0 1 2 3 4 5 6 7

D R S _ E n gi ne _ 1

IN O U T

E XP 1 00 _ 1,3

E XP 1 00 _ 1,2

IN O U T

E XP 1 00 _ 1,1

D S4 1 00 _1

O U T

IN O U T

1 2 3 4 5 6

IN O U T

7 31 6 -T F3

S w itc h_ 2

7 31 0 -C R 3

S w itc h_ 1

O U T

IN O U T

E XP 1 00 _ 2,7

IN O U T

E XP 1 00 _ 2,6

IN O U T

E XP 1 00 _ 2,5

IN O U T

E XP 1 00 _ 2,4

IN O U T

E XP 1 00 _2 ,3

E XP 1 00 _ 2,2

IN O U T

E XP 1 00 _ 2, 1

D S4 1 00 _2

O U T

IN O U T

O U T

Cabling to the customer’s Ethernet / IP Network

The DR550 provides for connecting to the customers Ethernet network using either 10/100 copper connections or gigabit fibre connections. For DR550 single node configurations, only one Ethernet connection is needed. For DR550 dual node configurations, four Ethernet connections are required (this enables HACMP failover if network problems occur). For the dual node configurations, two connections should be made to each of two customer provided subnets. Typically, it is expected that the customer will connect the DR550 to their existing network, including existing customer provided Ethernet switches.

Single Node Configurations

The following diagrams show the connections from an Ethernet perspective. With only one processing node, there is only a single Ethernet connection to the existing network. The type of connection (copper or fiber optic) is based on the adapter in the DR550. This choice is made when the DR550 is ordered.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 42

S in g le N o d e

1 0 /1 0 0 / 1 0 0 0 ( C o p p e r ) E th e r n e t C o n n e c t iv it y

IB M s u p p lie d E t h e rn e t c ro s s o ve r c a b le s

D S 4 1 0 0

C tr lBC tr lA

P 5 5 2 0

S y s te m

b o a rd

H M C 1 H M C 2

1 0 /1 0 0/ 1 0 0 0 ( T 5 ) 1 0 /1 0 0/ 1 0 0 0 ( T 6 )

U S B 0 ( T 7)

U S B 1 (T 8 )

1 0 / 1 0 0 / 1 0 0 0 E N S w i t c h # 1

( c u s to m e r's n e tw o rk )

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

C u sto m e r su p p lie d E th e rn e t c a b le s

Slot 4 (DS4100)

- Slot 5 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

S in g le N o d e

G ig a b it ( F ib e r O p tic ) E t h e rn e t C o n n e c tiv ity

IB M s u p p lie d E t h e rn e t c ro s s o ve r c a b le s

D S 4 1 0 0

C tr lBC t rl A

P 5 5 2 0

S y s te m

b o a rd

H M C 1 H M C 2

1 0 / 1 0 0 /1 0 0 0 ( T 5 ) 1 0 / 1 0 0 /1 0 0 0 ( T 6 )

U S B 0 (T 7 )

U S B 1 ( T 8)

G i g a b i t E N S w i t c h # 1

( c u s to m e r's n e t w o rk )

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

C u sto m e r s u pp lie d E th e rn e t ca b le s

Slot 4 (DS4100)

- Slot 5 (DS4100)

PCI-X Adapter - Slot 3

2 Port Gigabit Ethernet SX

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 43

Dual Node Configurations

Boot is used to indicate the primary connection. There is one Ethernet connection from both engine_1 and engine_2. Standby is provided as a backup connection in the event of a network failure to provide an alternate network path.

The diagrams below show the connections to be made from each engine (P5 520) to the customer’s pair of 10/100 or gigabit Ethernet switches.

For connecting to a gigabit Ethernet network, the boot (primary) connections are made from the first port of the 2 Port Gigabit Ethernet SX PCI-X adapters in engine_1 and engine_2 to the customer’s gigabit Ethernet switch (Switch1) .Switch 1 will carry network traffic in a normal situations. The standby (backup) connections are made from the second port of the 2 Port Gigabit Ethernet SX PCIX Adapter installed on engine_1 and engine_2 to the customer’s gigabit Ethernet switch (Switch2). Switch2 will carry the network traffic to the DR550 when there is a network failure associated with connections to Switch1. All gigabit Ethernet connections are to use fiber optic cabling.

Dual Node

10/100/1000 (Copper) Ethernet Connectivity

IBM supplied Ethernet crossover cables

DS4100#2

P5 520 #1

System

board

HMC1 HMC2

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

HACMP boot connection

Customer supplied Ethernet cables

10/100/1000 EN Switch #1

CtrlBCtrlA

(in Rack B)

(DRS_Engine_1)

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

Slot 4 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

(customer's network)

DS4100#1

P5 520 #2

System

board

HMC1 HMC2

- Slot 5 (DS4100)

10/100/1000 (T5) 10/100/1000 (T6)

HACMP standby - customer supplied cables

(in Rack A)

(DRS_Engine_2)

USB0 (T7)

USB1 (T8)

HACMP boot connection

10/100/1000 EN Switch #2

(customer's network)

CtrlBCtrlA

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

Customer supplied Ethernet cables

Slot 4 (DS4100)

- Slot 5 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 44

Dual Node

Gigabit (Fiber Optic) Ethernet Connectivity

IBM supplied Ethernet crossover cables

DS4100#2

P5 520 #1

System

board

HMC1 HMC2

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

HACMP boot connection

Customer supplied Ethernet cables

CtrlBCtrlA

(in Rack B)

(DRS_Engine_1)

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

Slot 4 (DS4100)

PCI-X Adapter - Slot 3

2 Port Gigabit Ethernet SX

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

HACMP standby - customer supplied cables

Gigabit EN Switch #1

(customer's network)

CtrlBCtrlA

DS4100#1

P5 520 #2

System

board

HMC1 HMC2

- Slot 5 (DS4100)

10/100/1000 (T5) 10/100/1000 (T6)

(in Rack A)

(DRS_Engine_2)

USB0 (T7)

USB1 (T8)

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

HACMP boot connection Customer supplied

Ethernet cables

Slot 4 (DS4100)

PCI-X Adapter - Slot 3

2 Port Gigabit Ethernet SX

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

- Slot 5 (DS4100)

Gigabit EN Switch #2

(customer's network)

Setting up the Management Console

DR550 includes an integrated management console. This console is already connected to each of the P5 520 servers and to the HMC. Connections are made through the Netbay LCM (Local Console Manager). To interact with the system software interfaces or to run diagnostics from a DVD-RAM, it is necessary to use the integrated console.

Userid and Password

The userid for the HMC is HSCROOT with a password of ABC123. You should change this password as part of the initial installation. Please review your password requirements and create a password that is appropriate to your installation.

Changing Server Names

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 45

7316-TF3 FC 4269 ) - IBM

You may normally press either the Print Screen key or press the Control key twice to access the OSCAR® (On Screen Configuration and Activity Reporting) interface. To modify server names on OSCAR, press Print Screen and then click Setup – Names – Modify to access the screen that displays the old name and prompts you to add a new name. Enter a new server name and click OK in the Modify screen; then click OK again in the Names screen., If you do not do this the system will be in a suspended state until you press the Print Screen twice.

Using the Num Lock key and the keypad in OSCAR to soft switch to servers by port number will only work when you first set the Num Lock key for a server. For example, when you set Num Lock on server A, the soft switch to server B and then back to Server A, the LED light on your keyboard will be lit, but Num Lock will no longer be activated for Server A. You can resolve this by pressing Num Lock twice to reset, or avoid it by either using your mouse or the number set on the main part of your keyboard to switch to a different server.

The following diagrams show the connections made in the factory for the single node and dual node configurations.

Single Node - All Configurations

P5 520 (DRS_Engine)

System

board

Modular phone cable (IBM Supplied) plugged into right side phone jack in HMC and connected to analog phone jack (supplied by customer)

7310-CR3 HMC

7316-TF3 Console with

KVM switch (FC 4202)

and IBM supplied video,

keyboard and mouse

cables (FC 4242)

Ethernet Crossover cable - IBM Supplied

Standby

Netbay LCM

Cat 5 cable connected to CT2 Conversion Option cable (32P1637) connected

to Out port in HMC server IBM Supplied

HMC1 HMC2

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

Adapter - Slot 1

Adapter - Slot 2

2 Gb Fibre Channel

Pwr GXT135p Graphics

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

Cat 5 cable connected to USB Conversion Option cable (78P5833 -

Supplied

Adapter - Slot 4

Adapter - Slot 5

2 Gb Fibre channel

2 Gb Fibre Channel

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 46

Dual Node - All Configurations

Ethernet Crossover cables - IBM Supplied

System

board

HMC1 HMC2

10/100/1000 (T5) 10/100/1000 (T6)

USB1 (T7)

USB2 (T8)

P5 520 #2 (DRS_Engine_2)

Adapter - Slot 4

Adapter - Slot 5

2 Gb Fibre channel

Adapter - Slot 2

Pwr GXT135p Graphics

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel

TX PCI-X Adapter - Slot 3

P5 520 #1 (DRS_Engine_1)

System

board

HMC1 HMC2

10/100/1000 (T5) 10/100/1000 (T6)

USB1 (T7)

USB2 (T8)

Adapter - Slot 4

Adapter - Slot 5

2 Gb Fibre channel

Adapter - Slot 2

Pwr GXT135p Graphics

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel

TX PCI-X Adapter - Slot 3

Cat 5 cable connected to USB Conversion Option cable (p/n 78P5833 - 7316-TF3 FC 4269 ) IBM Supplied

7310-CR2 HMC

Standby

Cat 5 cable connected to USB Conversion Option cable (p/n 78P5833 - 7316-TF3 FC 4269 ) IBM Supplied

Netbay LCM

Modular phone cable (IBM supplied) plugged into right side phone jack in HMC and connected to analog phone jack (supplied by customer)

7316-TF3 Console with

KVM switch (FC 4202)

and IBM supplied video,

keyboard and mouse

cables (FC 4242)

Cat 5 cable connected to CT2 Conversion Option cable (p/n 32P1637) connected to Out port in HMC server IBM Supplied

As an option, you can attach an external monitor using the serial ports on the P5 520s. To interact with the system software interfaces or to run diagnostics from a DVD-RAM using an external device, you will need to do the following:

• Connect a terminal (or PC) to the serial port FS1 (on the front of the unit) using a null- modem cable (RJ45 to 9 pin Serial cable which is provided by IBM)

Your PC may need to use an emulator, such as HyperTerminal, often supplied with Windows family operating systems. Set the emulation mode to vt100 and use the following communication settings:

• 19200 baud

• 8 bit

• 1 stop bit

• No parity

• Xon/Xoff

The following procedure is to connect the ASCII (tty) terminal (or PC) to the P5 520 (this is provided as information only as it is recommended that you use the integrated console for all DR550 management activity:

1. Before doing this step, read and understand “Read the Safety Notices”.

2. This system drawer is equipped with serial port 1 located in the front (FS1) and rear (S1) of the system.

3. Use an RJ-45 to 9-pin serial null modem cable (IBM supplied) to connect to the front serial port FS1.

4. When using FS1, the rear serial port 1 is deactivated.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 47

5. Use a 9-pin to 9-pin serial converter cable (customer supplied) when connecting to the rear serial port 1.

An ASCII (tty) terminal must be used to configure both P5 520 servers. If you have a single terminal, you may connect it to one P5 520 and configure the server. Then connect it to the other P5 520 server and configure it. Thus only one terminal is needed as the console in setting up the DR550. For convenience, the front (FS1) serial port is often preferred.

Dual Node Configurations: Note that P5 520 engine_1 (also referred to as drs_engine_1) is located in Rack1 position 13. P5 520 engine_2 (also referred to as drs_engine_2) is located in Rack1 position 19. Also refer to the Cabling between the Racks section for an illustration of the location of engine_1 and engine_2. It is recommended that you disconnect the cable at the server side when the console is not in use.

Connecting AC Power

Check the AC Outlets

Refer to the 7014 Series Model T00 and Model T42 Installation Guide for additional information in the installation and setup of the 7014 Series Model T00 rack.

Before plugging the rack into the AC power source, do the following checks on the AC power source.

CAUTION: Do not touch the receptacle or the receptacle faceplate with anything other than your test probes before you have met the requirements in step 8.

1. Turn off the branch circuit breaker for the ac power outlet that the rack will plug into. To the circuit breaker switch, attach tag S229-0237, which reads “Do Not Operate”. Note: All measurements are made with the receptacle face plate in the normal installed position.

2. Some receptacles are enclosed in metal housings. For this type of receptacle, do the following:

a. Check for less than 1 volt from the receptacle case to any grounded metal structure

in the building, such as a raised-floor metal structure, water pipe, building steel, or similar structure.

b. Check for less than 1 volt from the receptacle ground pin to a grounded point in the

building. Note: If the receptacle case or face plate is painted, be sure the probe tip penetrates the paint and makes good electrical contact with the metal.

c. Check the resistance from the receptacle ground pin to the receptacle case. Check

resistance from the ground pin to the building ground. The readings should be less than 1.0 ohm, which indicates the presence of a continuous grounding conductor.

3. If any of the three checks made in sub step 2 are not correct, remove the power from the branch circuit and make the wiring corrections; then check the receptacle again. Note: Do not use a digital multi-meter to measure grounding resistance in the following steps.

4. Check for infinite resistance between the ground pin of the receptacle and each of the phase pins. This is a check for a wiring short to ground or a wiring reversal.

5. Check for infinite resistance between the phase pins. This is a check for a wiring short.

CAUTION: If the reading is other than infinity, do not proceed! Have the customer make necessary wiring connections before continuing. Do not turn on the branch circuit CB until all the above steps are satisfactorily completed.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 48

6. Turn on the branch circuit breaker. Measure for the appropriate voltages between phases. If no voltage is present on the receptacle case or grounded pin, the receptacle is safe to touch.

7. With an appropriate meter, verify that the voltage at the ac outlet is correct.

8. Verify that the grounding impedance is correct by using the ECOS 1020, 1023, B7106, C7106, or an appropriately approved ground-impedance tester.

Cabling AC

The DR550 rack(s) have sets of AC power rails (left and right) traversing vertically in the rear of the rack cabinet. Each rail in a set should be connected to a different AC power feed if that is available. This is to enhance the availability of the rack components. Each power source should be 220V or 200V single phase rated at 30 amps.

For the 5.6 and 11.2 TB configurations, there are two power rails. For the 22.4 and 44.8 TB offering, there are four power rails. For the 89.6 TB offering, there will be eight power rails, 4 per rack. Power cords are shipped with each rack (one per rail) to enable cabling to AC power above or below each rack. Power cords come with NEMA L6-30 connectors.

Each device in the rack is connected to the AC Power Rails. When shipped from the factory each component will have the AC power switch in the OFF position. The SAN Switch (one in the single node configuration or two in the dual node configuration) do not have an AC switch, and thus will be powered up as soon as the rails become energized.

Power on Sequence

The devices in the rack should be powered on in the following sequence:

1. SAN Switch(es) (Before proceeding to step 3, confirm that the SAN Switch(es) have completed their power on sequencing. This is indicated with a green light showing for power.)

2. DS4000 EXP100 Serial ATA drives (0 to 14 devices depending on the disk capacity installed)

3. DS4100 (single device except for 89.6 TB configurations which has two)

4. P5 520 #1 (located at EIA 13-16 in the rack)

5. P5 520 #2 (located at EIA 19-22 in the rack – this is only present in the dual node configurations)

Similarly, should power need to be shut down, the reverse of the power on sequence should be followed (once the applications and operating systems have been shutdown):

1. P5 520 #2 (located at EIA 19-22 in the rack – this is only present in the dual node configurations)

2. P5 520 #1 (located at EIA 13-16 in the rack)

3. DS4100 (single device except for 89.6 TB configurations which has two)

4. DS4000 EXP100 Serial ATA drives (0 to 14 devices depending on the disk capacity installed)

5. SAN Switch(es)

Connect the Drawer and Device Cables

The DR550 rack(s) are preconfigured at the factory with all drawers and device cables installed. To check out the system, refer to the RS/6000 and eServer pSeries Diagnostics Information for Multiple Bus Systems and follow the instructions in the installation checkout procedure.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 49

Configuring the P5 520 Servers

The P5 520 servers within the IBM TotalStorage Data Retention are shipped with particular AIX security settings. These settings will not allow remote administration tasks initiated via commands like telnet, remote shell (rsh), file transfer protocol (ftp) or similar. Therefore, you should use the integrated console for management activities. (You can use an ASCII (tty) terminal if needed – a connection must be established using the Serial Port 1 of each P5 520 server to administer (configure) the P5 520 server. Note that one ASCII terminal may be used by connecting to one server at a time. The procedure for physically attaching the ASCII (tty) terminal was addressed in the Installation and Activation section. The ASCII terminal, when attached to Serial Port 1, will be known in AIX as tty0.)

User Accounts

To provide a greater level of security, DR550 is setup with limited access. These restrictions are built into the DR550 as follows:

• Limited user definitions

• Limited access to commands from certain accounts

• No remote access with authority to make changes

User Accounts

The following user accounts have been created. Each has a specific role when using the DR550. Passwords should be changed in accordance with company policy and guidelines. To enhance security, certain user accounts do not have any change authority and other accounts can only be accessed from the integrated console. The following user accounts have been created, with the following roles and restrictions specified:

AIX

Account Roles Password set at Factory

dr550 Access via integrated console to P5 520 servers

(VTY 0) or via the serial port on the front of the P5 520 server (tty 0) – It is recommended that you use the integrated console no remote access Only user who can ‘su’ to root Home directory /home/dr550 Shell /bin/ksh

dr550adm Access via integrated console or from remote ASCII

terminal Home directory /home/dr550adm Shell - /bin/ksh

ibmce console access and remote access

home directory /home/ibmce shell - /bin/ksh

root no direct login

su allowed only from dr550 account Ability to view log files and perform SM Client tasks

dr550

dr550adm

ibmce

d3rv1sh – this password will need to be changed during the initial installation. It is initially setup to require a change at the initial login.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 50

System Storage Archive Manager

Account Roles Password set at Factory

hacmpadm System Storage Archive Manager ID for use with

HACMP scripts Has TSM operator authority Password set to not expire (you may still want to change it)

admin System Storage Archive Manager Administrator ID

Admin login and password is for all TSM administrative usage http;//<server ip / dns name>:1580

It is the customer’s responsibility to change the default passwords provided above and to record and protect the new passwords. Changing the password should be done during the initial installation. The password for root must be changed during the initial installation. Changing the password for the TSM hacmpadm userid will also require a change in one of the scripts provided (see Changing the TSM HACMPADM Password)

chang3Me

admin

Configuring the Single Node System (P5 520 Server)

The System Storage DR550 single node configuration consists of a single P5 520 server. No cluster configuration is included. It is important to understand how the single node configurations are built so you can make the proper changes to incorporate the DR550 in to your network.

DR550 has been configured at the factory with specific settings. Some of these will need to be changed. The setup process requires changing one IP address. The DR550 must have network access to the applications which create or manage data that is to be retained. The DR550 must be connected in to the customer’s IP network using the Ethernet adapter in slot 1 of the P5 520 server(s). This adapter can either be used to connect to a copper network (must order the TX adapter) or a fiber optic network (must order the SX adapter) as referenced earlier in this document.

Connecting to Gigabit Ethernet (Fibre) Network

The following diagram shows the network as configured at the factory. The IP address that must be changed for integration into the customer’s IP network is the address for the single P5 520 server. You do not need to configure any other addresses on the DR550.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 51

Single Node - SX adapter

IP Addresses

192.168.5.102

192.168.4.101

CtrlBCtrlA

DS4100

P5 520

System

board

HMC1 HMC2

Adapter - Slot 2

192.168.4.24

192.168.5.26

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

Slot 4 (DS4100)

- Slot 5 (DS4100)

PCI-X Adapter - Slot 3

2 Port Gigabit Ethernet SX

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

192.168.1.11

Gigabit EN Switch #1

(customer's network)

The following table shows the IP addresses associated with the server, storage and customer network. Please note that some addresses may need to be changed while others should not be changed.

IP Address IP Description Device Configuration Need?

DRS_Engine_1

192.168.1.11 drs_engine AIX To be changed

192.168.4.24 drs_engine_DS40001_ctrlA AIX Do not change

192.168.5.26 drs_engine_DS40001_ctrlB AIX Do not change

192.168.4.101 drs_DS40001_ctrlA DS4100 Do not change

192.168.5.102 drs_DS40001_ctrlB DS4100 Do not change

Preconfigured TCP/IP addresses for gigabit Ethernet networks

Connecting to a 10/100/1000 Mbps Ethernet (copper) Network

To connect to a 10/100/1000 Mbps Ethernet network (or 10/100 network), the following diagram shows how the DR550 is configured at the factory.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 52

Single Node - TX adapter

IP Addresses

192.168.5.102

192.168.4.101

CtrlBCtrlA

DS4100

P5 520

System

board

HMC1 HMC2

Adapter - Slot 2

192.168.4.24

192.168.5.26

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

Slot 4 (DS4100)

- Slot 5 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

192.168.1.11

Gigabit EN Switch #1

(customer's network)

The following table shows the IP addresses associated with the server, storage and customer network. Please note that some addresses may need to be changed while others should not be changed.

IP Address IP Description Device Configuration Need?

DRS_Engine_1

192.168.1.11 drs_engine AIX To be changed

192.168.4.24 drs_engine_DS40001_ctrlA AIX Do not change

192.168.5.26 drs_engine_DS40001_ctrlB AIX Do not change

192.168.4.101 drs_DS40001_ctrlA DS4100 Do not change

192.168.5.102 drs_DS40001_ctrlB DS4100 Do not change

Important: Make sure to use the correct adapter(s) and port(s) on the IBM eServer p5 520 server(s) when connecting to your network; check the interface(s) during configuration. Do not connect the IBM System Storage DR550 to your network if you already use the factory IP addresses for any other device within your network environment.

Preconfigured TCP/IP addresses for 10/100/1000t Ethernet networks

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 53

Procedure for Changing IP Address

To configure the DR550 for use within your network you must change one IP address from its factory setting. The change is made to the P5 520 server.

Important: Do not change the factory IP configuration for the DS4100 controllers or any IP address on the IBM TotalStorage SAN Switch B16.

The following table, which was also provided in the Site Preparation and Planning Section of this document, may be helpful in recording the IP addresses to be used in your operational environment.

IP Description IP Address from Factory IP Address in Network

drs_engine 192.168.1.11

There are different possible ways to change the IP settings. There are various AIX commands, which are available for these tasks. For convenience, we recommend that you use the System Management Interface Tool (SMIT) that is part of AIX. This is a quick and efficient tool, and in addition, the SMIT session is logged into a file (smit.log); the log file can be used to analyze a situation in case of problems.

Single node configuration steps

Most settings are done using the System Management Interface Tool (SMIT) of AIX. SMIT is an interactive interface application designed to simplify system management tasks. We start SMIT on the AIX command line prompt by typing smitty. The smitty command displays a hierarchy of menus that can lead to interactive dialogues. SMIT builds and runs commands as directed by the user.

Step 1 - Obtain 1 IP address from your network administrator

The first step is to set a new address in conformance with your network. You need to obtain one IP address from your network administrator. It is suggested that you create a table where you write the factory IP address and the actual IP address side by side as illustrated. The following steps include a sample address. Your address will most likely be different.

IP description AIX interface Factory IP

address

drs_engine en0 192.168.1.21

255.255.255.0

Step2 - Connect to drs_engine through the management console

1. Login to the IBM eServer p5 520 server drs_engine with user dr550 through the management console. Login DR550 Password xxxxxxx

2. Once successfully logged on as dr550, issue the AIX command su - root to switch to root. Now you have the necessary AIX system rights to change the network settings. Password xxxxxx

Step 3 - Edit the /etc/hosts file on drs_engine

Actual IP address

100.100.51.121

255.255.255.0

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 54

1. First of all create a copy of the /etc/hosts file that is shipped from factory (see Preconfigured

/etc/hosts file on drs_engine (excerpt)) with the AIX command cp /etc/hosts /etc/hosts.factory.

Preconfigured /etc/hosts file on drs_engine (excerpt)

127.0.0.1 loopback localhost # loopback (lo0) name/address

192.168.4.24 drs_engine2_FAStT1_ctrlA drs_engine

192.168.5.26 drs_engine2_FAStT1_ctrlB drs_engine

192.168.1.21 drs_engine

2. Open the /etc/hosts file with an editor of your choice, for instance use vi (AIX command to start vi

and open the file is vi /etc/hosts).

If you are not familiar with AIX editors, you may want to use xedit, an X-window based editor. For the latter, you first need to start an X-session. Start the X-session with the AIX command startx (see startx manpages for details for issuing man startx). Then open the /etc/hosts file with the AIX command xedit /etc/hosts, this will open a graphical editor session.

Scroll down to the appropriate line in the hosts file.

Change the preconfigured address according to the table you have prepared in Step 1. Only change this address, do not change addresses not listed in the table above, or any words in the /etc/hosts file.

Custom-made /etc/hosts file on drs_engine (excerpt)

127.0.0.1 loopback localhost # loopback (lo0) name/address

192.168.4.24 drs_engine2_FAStT1_ctrlA drs_engine

192.168.5.26 drs_engine2_FAStT1_ctrlB drs_engine

100.100.51.121 drs_engine (remember, this is a sample address – you will need to provide the

address provided by your network administrator)

3. Save the file and exit the editor by pressing Save and Close on the scroll bar.

Step 4 - Change the TCP/IP address for the interface en3

1. From the AIX command line start SMIT Change / Show Characteristics of a Network Interface

with the command smitty chinet.

2. Select the network interface you want to change, en0, until it is highlighted. Press Enter to

change. In the INTERNET ADDRESS (dotted decimal) field, type the new IP address that was provided by the network administrator (100.100.51.121 is our sample address). In the Network MASK (hexadecimal or dotted decimal) field, type the network mask 255.255.255.0 of the new network. Press Enter.

3. Check the result of the command at the COMMAND STATUS window of SMIT. The Command

field shows OK while the text below says en0 changed. Escape SMIT by pressing F10.

Step 5 - Verify the new IP address

From the AIX command line use the command ping for all the addresses, especially the new address, to verify their correct working.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 55

Ping xx.xx.xx.xx hit ctrl c to break out of the ping command

Step 6 - Edit the IBM System Storage Archive Manager client option file (dsm.sys)

You need to adjust the IBM Tivoli Storage Manager (ITSM) client system options file, so that the ITSM API or any ITSM client (dsmadmc) can find the IBM System Storage Archive Manager server.

On the p5 520 server, replace the value in the dsm.sys file for the tcpserveraddress with your new HACMP cluster service address. We recommend that you do NOT use a dot address, for instance

100.100.51.121, instead, use the TCP/IP domain name instead, that is drs_engine.

Tip: When using the TCP/IP domain name for the tcpserveraddress field in the IBM System Storage Archive Manager client system options file (dsm.sys), you do not need to change the value after a network reconfiguration. This is not true, when you use the dot address.

Step 7 - Logoff all sessions

After successful configuration you should exit all shells with the AIX command exit. Depending on the actual shells, you must type the exit command more than once. For example, enter exit one time to close the shell of root and one time to close the shell of dr550. Repeat it until you see the AIX login prompt on the management console session.

Configuring the Dual Node System (P5 520 Servers)

The System Storage DR550 dual node offering is composed of a two node cluster (using HACMP), in an active – passive mode. It has been configured for automatic failover with the primary node being drs_engine1. Once the primary node has been recovered, then fall back will occur automatically.

During the failover, the cluster will automatically move the resources, such as the physical disks, logical volumes, and file systems to the surviving node. System Storage Archive Manager will automatically start and allow for data access activities to continue. When the fall back occurs, the cluster will stop System Storage Archive Manager from running and start it on the primary node, along with all the other resources.

It is important to understand the network topology when configuring HACMP. For example, it is important to understand which IP addresses refer to the BOOT (PUBLIC or customers network) network, the SERVICE (or cluster IP Address) and the STANDBY (the customers IP address on a different subnet that will provide connectivity in the event of a failure of the BOOT IP address).

The DR550 has been configured at the factory with the fore mentioned IP addresses. The setup process requires changing five IP addresses to their network IP addresses on both nodes. At a minimum, three areas of the DR550 must be configured as a part of initial setup as follows:

1. IP Network Configuration - The DR550 must have IP network access to the applications which create the data to be retained. The DR550 must be connected into the customer’s IP network using:

a. four 10/100 copper Ethernet ports (links)

b. four gigabit fiber optic Ethernet ports (links) Each of these four ports must be configured with IP addresses consistent with the customer’s IP address schema.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 56

2. HACMP Reconfiguration – After the four IP addresses have been configured that are consistent with the customer’s IP address schema, HACMP must be reconfigured with these IP addresses specified.

3. Change /usr/tivoli/tsm/client/ba/bin/dsm.sys:

SErvername TSM COMMmethod TCPip TCPPort 1500

TCPServeraddress 192.168.1.22 <=== cluster ip

address or DNS host name

The following sections explain how to configure each of the above steps.

IP Network Address Configuration

The IBM System Storage DR550 can connect to a 10/100/1000 Mbps copper based Ethernet network, or 1000 Mbps (gigabit) fiber optic based Ethernet network. Setup and configuration for connecting to 10/100/1000 Mbps and the gigabit Ethernet networks is addressed in the following sections. There is one dual port network adapter in each P5 520 server. The IBM Dual Port Gigabit Ethernet-SX PCI-X Adapter or IBM Dual Port Base TX Ethernet adapter is found in the P5 520s (PCI-X slot 1). This adapter is used to connect to the customer’s Ethernet network.

To use the IBM System Storage DR550 you must change the IP network addresses set at the factory to conform to your IP network address schema. This results in one task: the setting of IP addresses for multiple adapters.

Connecting to Gigabit Ethernet (Fibre) Network

The following diagram shows the network as configured at the factory. The addresses that must be changed for integration into the customer’s IP network are stored on both P5 520 servers. Addresses for both nodes are stored on each server. You do not need to configure any other addresses on the DR550.

The following table shows the IP addresses associated with the servers, storage and customer network. Please note that some addresses may need to be changed while others should not be changed.

IP Address IP Description Device Configuration Need?

DRS_Engine_1

192.168.1.21 drs_engine1_boot AIX To be changed

192.168.2.10 drs_engine1_stdby AIX To be changed

192.168.1.22 drs_cluster_svc AIX / HACMP To be changed

192.168.3.10 drs_engine1_hrtbeat AIX / HACMP Do not change

192.168.4.23 drs_engine1_DS40002_ctrlA AIX Do not change

192.168.5.25 drs_engine1_DS40002_ctrlB AIX Do not change

192.168.4.103 drs_DS40002_ctrlA DS4100 Do not change

192.168.5.104 drs_DS40002_ctrlB DS4100 Do not change

DRS_Engine_2

192.168.1.23 drs_engine2_boot AIX To be changed

192.168.2.11 drs_engine2_stdby AIX To be changed

192.168.3.11 drs_engine2_hrtbeat AIX/HACMP Do not change

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 57

192.168.4.24 drs_engine2_DS40001_ctrlA AIX Do not change

192.168.5.26 drs_engine2_DS40001_ctrlB AIX Do not change

192.168.4.101 drs_DS40001_ctrlA DS4100 Do not change

192.168.5.102 drs_DS40001_ctrlB DS4100 Do not change

Preconfigured TCP/IP addresses for gigabit Ethernet networks

Dual Node

Gigabit (Fiber Optic) IP Addresses

192.168.5.104

192.168.4.103

CtrlBCtrlA

DS4100#2 (in Rack B)

P5 520 #1 (DRS_Engine_1)

System

board

HMC1 HMC2

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

192.168.1.21 HACMP boot

connection

Pwr GXT135p Graphics

192.168.4.23

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

192.168.5.25

Slot 4 (DS4100)

- Slot 5 (DS4100)

PCI-X Adapter - Slot 3

2 Port Gigabit Ethernet SX

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

192.168.2.11 HACMP standby connection

192.168.2.10 HACMP standby connection

192.168.5.26

Gigabit EN Switch #1

(customer's network)

192.168.5.102

192.168.4.101

DS4100#1 (in Rack A)

P5 520 #2 (DRS_Engine_2)

System

board

HMC1 HMC2

192.168.4.24

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

Gigabit EN Switch #2

(customer's network)

CtrlBCtrlA

2 Gb Fibre Channel

Adapter - Slot 2

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

2 Port Gigabit Ethernet SX

192.168.1.23 HACMP boot

connection

Slot 4 (DS4100)

- Slot 5 (DS4100)

PCI-X Adapter - Slot 3

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

To configure the DR550 for use within your network you have to change five IP addresses from their factory settings. The changes are made on each of the P5 520 servers. No changes are needed on the DS4100 or the 2005-B16.

The following table, which was also provided in the Site Preparation and Planning Section of this document, may be helpful in recording the IP addresses to be used in your operational environment.

IP Description IP Address from Factory IP Address in Network

drs_engine1_boot 192.168.1.21 drs_engine1_stdby 192.168.2.10 drs_engine2_boot 192.168.1.23 drs_engine2_stdby 192.168.2.11 drs_cluster_svc 192.168.1.22

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 58

Connecting to 10/100/1000 Ethernet (Copper) Network

The connection to the customer’s 10/100/1000 Mbps Ethernet (copper) network is provided by the IBM Dual Port Base TX Ethernet-PCI-X Adapter, located in PCI slot 1 (on the very left side) of each P5 520 server.

This is illustrated in the figure below. It is important not to change the IP addresses on the P5 520 servers for the attachment of the DS4100 servers nor change the IP addresses on the DS4100 storage servers.

Dual Node

10/100/1000 (Copper) IP Addresses

192.168.5.104

192.168.4.103

CtrlBCtrlA

DS4100#2 (in Rack B)

P5 520 #1 (DRS_Engine_1)

System

board

HMC1 HMC2

Adapter - Slot 2

192.168.5.25

10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

10/100/1000 (T5)

192.168.4.23

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

192.168.1.21 HACMP boot

connection

Pwr GXT135p Graphics

Slot 4 (DS4100)

- Slot 5 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

192.168.2.11 HACMP standby connection

192.168.2.10 HACMP standby connection

192.168.5.26

10/100/1000 EN Switch #1

(customer's network)

192.168.5.102

192.168.4.101

CtrlBCtrlA

DS4100#1 (in Rack A)

P5 520 #2 (DRS_Engine_2)

System

board

HMC1 HMC2

192.168.4.24

10/100/1000 (T5) 10/100/1000 (T6)

USB0 (T7)

USB1 (T8)

10/100/1000 EN Switch #2

(customer's network)

Adapter - Slot 2

2 Gb Fibre Channel

Adapter - Slot 1 (tape)

Pwr GXT135p Graphics

192.168.1.23 HACMP boot

connection

Slot 4 (DS4100)

- Slot 5 (DS4100)

TX PCI-X Adapter - Slot 3

2 Port 10/100/1000 Ethernet

2 Gb Fibre Channel Adapter

2 Gb Fibre channel Adapter -

The following table shows the IP addresses associated with the servers, storage and customer network. Please note that some addresses may need to be changed while others should not be changed.

IP Address IP Description Device Configuration Need?

DRS_Engine_1

192.168.1.21 drs_engine1_boot AIX To be changed

192.168.2.10 drs_engine1_stdby AIX To be changed

192.168.1.22 drs_cluster_svc AIX / HACMP To be changed

192.168.3.10 drs_engine1_hrtbeat AIX / HACMP Do not change

192.168.4.23 drs_engine1_DS40002_ctrlA AIX Do not change

192.168.5.25 drs_engine1_DS40002_ctrlB AIX Do not change

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 59

192.168.4.103 drs_DS40002_ctrlA DS4100 Do not change

192.168.5.104 drs_DS40002_ctrlB DS4100 Do not change

DRS_Engine_2

192.168.1.23 drs_engine2_boot AIX To be changed

192.168.2.11 drs_engine2_stdby AIX To be changed

192.168.3.11 drs_engine2_hrtbeat AIX / HACMP Do not change

192.168.4.24 drs_engine2_DS40001_ctrlA AIX Do not change

192.168.5.26 drs_engine2_DS40001_ctrlB AIX Do not change

192.168.4.101 drs_DS40001_ctrlA DS4100 Do not change

192.168.5.102 drs_DS40001_ctrlB DS4100 Do not change

Each connection should be to a different 10/100/1000 Ethernet switch, which are elements of the customer’s network. The reason to use different switches is to enhance network availability to the DR550. The boot network is the network for normal usage. The second network is the standby network which is used in case of problems with the boot network.

It is important not to change the TCP/IP addresses on the P5 520 servers for the attachment of the DS4100 servers nor change the TCP/IP addresses on the DS4100 storage servers.

Preconfigured TCP/IP addresses for 10/100/1000 Ethernet

HACMP Configuration

When changing the IP addresses, you should use the integrated console to make these changes. If the integrated console is not working, the serial port on the front of each P5 520 server is available for connection to a TTY terminal (provided by the customer). The console works best with a physical ASCII terminal such as IBM 3151 or vt100 or a PC workstation running a terminal emulator such as hyperterm, emulating vt100.

HACMP heartbeat information is exchanged between the two nodes through the host bus adapters (Ethernet) in slot 3 of the P5 520s. This connection is used to monitor the network and server, ensuring that a failure does not cause an interruption in data access.

The HACMP configuration needs to be modified when the solution is deployed in the customer environment. The boot and the standby addresses will have to be modified to be compatible with the customer subnet that they connect to. It is a best practice recommendation to have them (boot and

standby) on different subnets.

Procedures for Changing IP Addresses

To configure the DR550 for the use with your network you have to change five IP addresses from their factory settings. The changes are made on both P5 520 servers. No changes are needed on the DS4100 or the 2005-B16.

The following table, which was also provided in the Site Preparation and Planning Section of this document, may be helpful in recording the IP addresses to be used in your operational environment.

IP Description IP Address from Factory IP Address in Network

Drs_engine1_boot 192.168.1.21 Drs_engine1_stdby 192.168.2.10 Drs_engine2_boot 192.168.1.23 Drs_engine2_stdby 192.168.2.11 Drs_cluster_svc 192.168.1.22

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 60

Once the DR550 has been physically connected to the customer network, the following IP addresses need to be changed:

Using smit or smitty, the Ethernet devices that will be used for the BOOT IP address (i.e. en5 for 10/100, en1 for gigabit) and the STANDBY address (i.e. en3 for 10/100, en2 for gigabit) need to be changed. HACMP also requires changes to the configuration. HACMP configuration menu must be invoked through smit or smitty (Configure HACMP Communication Interface/Devices menu). Once the changes have been made to the HACMP configuration, the customer must perform the Extended Verification and Synchronization (smitty hacmp) to verify the changes.

The following sequence of steps assumes the utilization of SMIT:

Configuration steps detail

This section details and illustrates how to set up all five new IP addresses.

Usage of the name SMIT throughout this section refers to the tool and not to the command.

Step 1 - Obtain 5 applicable IP addresses from your network administrator

The first step is to set new addresses in conformance with your network and HACMP requirements. You need to obtain five IP addresses from your network administrator (four IP addresses will use physical network connections and one IP address will represent a virtual connection). We suggest that you create a table where you write the factory IP addresses and the actual IP addresses side by side. (This table includes sample addresses. You will need to use the addresses provided by your network administrator.)

IP description AIX interface Factory IP

Actual IP address

address

drs_engine1_boot en0 192.168.1.21

255.255.255.0

drs_engine1_stdby en1 192.168.2.10

255.255.255.0

drs_cluster_svc n/a 192.168.1.22

255.255.255.0

drs_engine2_boot en0 192.168.1.23

255.255.255.0

100.100.51.121

255.255.255.0

100.100.52.110

255.255.255.0

100.100.51.122

255.255.255.0

100.100.51.123

255.255.255.0

drs_engine2_stdby en1 192.168.2.11

255.255.255.0

100.100.52.111

255.255.255.0

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 61

Step 2 - Connect to drs_engine1 through the management console (Engine1)

1. From the integrated console, use the PRT Scr key to access the IBM eServer p5 520 server

drs_engine1. Hit Enter to see the login prompt. Login dr550 Password xxxxxx

2. Once successfully logged on as dr550, issue the AIX command su - root to switch to root. Now

you have the necessary AIX system rights to change the network settings and to reconfigure HACMP.

Step 3 - Stop HACMP (if necessary)

1. Check if HACMP is running or stopped with the AIX command lssrc -g cluster.

2. If it is running, stop HACMP on each node. It is assumed there is no data traffic when stopping,

since this is the implementation phase. It can take several minutes to stop HACMP. After HACMP is stopped, go on with the next step.

The following steps describe the procedure for stopping cluster services on a single node or on both nodes in the cluster by executing the C-SPOC /usr/es/sbin/cluster/sbin/cl_clstop command on one of the cluster nodes. When stopping multiple nodes, C-SPOC stops them sequentially, not in parallel. If any node specified to be stopped is inactive, the shutdown operation aborts.

Important: When stopping cluster services, minimize activity on the system. If the node you are stopping is currently providing highly available services, notify users of your intentions if their applications will be unavailable. Let them know when services will be restored.

1. Log in to any of the IBM eServer p5 520 servers; use dr550 and switch to root.

You can switch to root with the AIX command su - root.

2. On the AIX command line start SMIT by issuing the command smitty clstop

3. Use the default settings and change nothing when you want to stop only one of the nodes (the

one you are logged in) with a graceful shutdown mode.

Tip: Because the DR550 is running a two node HACMP cluster, to stop only one of the both nodes is not a usual task. To stop only one node is needed for maintenance tasks only. Hence the normal stopping procedure for HACMP in the DR550 always includes the stopping of both nodes.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 62

Use the F4 key in the Stop Cluster Services on these nodes field when you want to stop the cluster services on both nodes. A pop-up window (Stop Cluster Nodes on these nodes) appears. Select both nodes with the F7 key. Both nodes are marked in front of the line. Press Enter.

If you want to change the shutdown mode, press F4 in the appropriate line. A pop-up windows (Shutdown Mode) appears. Select the shutdown mode and press Enter.

The selected shutdown mode refers to the following types of shutdown:

– graceful: Shut down after the /usr/es/sbin/cluster/events/node_down_complete script is run on

the node to release its resources. The other cluster node does not take over the resources of the stopped node.

– takeover (graceful with takeover): Shut down after the

/usr/es/sbin/cluster/events/node_down_complete script runs to release its resources. The other node takes over the resources of the stopped node. You cannot shut down cluster services on the other cluster node if you select this type of shutdown.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 63

– forced: Shut down immediately. The node retains control of all its resources. You can use this

option to bring down a node while you perform maintenance or make a change to the cluster configuration such as adding a network interface. The node’s applications remain available, except for those that access enhanced concurrent mode volume groups (but without the services of HACMP for AIX daemons).

Important: It is very important that you only use forced shutdown on one cluster node at a time, and for as short a time as possible. When you need to stop cluster services for an extended period and on more than one cluster node, you should use one of the other options (either graceful or graceful with takeover).

4. Back on the Stop Cluster Services screen, check that the node or nodes are shown in the

appropriate line, make sure you specified the correct shutdown mode, and press Enter.

5. The system stops the cluster services on the nodes specified. SMIT displays a command status

window. It should display an OK message in the upper left corner. If not, you have to analyze the given messages at the same window, fix the problem, and start the process again.

If the stop operation fails, check the C-SPOC utility log file named /tmp/cspoc.log for error messages. This file contains the command execution status of the C-SPOC command executed on each cluster node.

6. Quit the SMIT session: Press F10 or ESC+0.

7. Verify on the AIX command line, that all HACMP services are stopped successful. Use the

command lssrc -g cluster. Typically, it will take a few minutes to stop the Cluster Manager (clstrmgrES). HACMP is stopped completely, when the lssrc -g cluster command returns with no services running.

Step 4 - Edit the /etc/hosts file on drs_engine1

1. First of all create a copy of the /etc/hosts file that is shipped from factory (see Preconfigured

/etc/hosts file on drs_engine1 and drs_engine2 (excerpt)) with the AIX command cp /etc/hosts

/etc/hosts.factory.

Preconfigured /etc/hosts file on drs_engine1 and drs_engine2 (excerpt)

127.0.0.1 loopback localhost # loopback (lo0) name/address

# # Engine 1 #

192.168.1.22 drs_cluster_svc

192.168.1.21 drs_engine1_boot drs_engine1 #en0

192.168.2.10 drs_engine1_stdby drs_engine1 #en1 # # Engine 2 #

192.168.1.23 drs_engine2_boot drs_engine2 #en0

192.168.2.11 drs_engine2_stdby #en1

192.168.4.24 drs_engine2_FAStT1_ctrlA #en2

192.168.5.26 drs_engine2_FAStT1_ctrlB #en3

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 64

2. Open the /etc/hosts file with an editor of your choice, for instance use vi (AIX command to start vi

and open the file is vi /etc/hosts).

If you are not familiar with AIX editors, it may be easier to use xedit, an X-window based editor. For the latter, you first need to start an X-session. Start the X-session with the AIX command startx (see startx manpages for details by issuing man startx). Then open the /etc/hosts file with the AIX command xedit /etc/hosts, this will open a graphical editor session.

Scroll down to the appropriate line in the hosts file

Change all of the preconfigured addresses according to the table you have prepared in Step 1 Ob. Only change these addresses, do not change addresses not listed in the table above, or any words in the /etc/hosts file. Change the addresses in all stanzas of the /etc/hosts file. That is, you have to change five addresses.

Custom-made /etc/hosts file on drs_engine1 and drs_engine2 (excerpt)

127.0.0.1 loopback localhost # loopback (lo0) name/address

# # Engine 1 #

100.100.51.122 drs_cluster_svc

100.100.51.121 drs_engine1_boot drs_engine1 #en0

100.100.52.110 drs_engine1_stdby drs_engine1 #en1 # # Engine 2 #

100.100.51.123 drs_engine2_boot drs_engine2 #en0

100.100.52.111 drs_engine2_stdby #en1

192.168.4.24 drs_engine2_FAStT1_ctrlA #en2

192.168.5.26 drs_engine2_FAStT1_ctrlB #en3

3. Save the file and exit the editor by pressing save and close on the scroll bar.

Step 5 - Change the TCP/IP addresses for the interfaces en2 and en3

1. From the AIX command line start SMIT Change / Show Characteristics of a Network Interface

with the command smitty chinet.

Select the first network interface you want to change, en2, until it is highlighted. Press Enter to change. In the INTERNET ADDRESS (dotted decimal) field, type the new IP address

100.100.52.110. In the Network MASK (hexadecimal or dotted decimal) field, type the network mask 255.255.255.0 of the new network. Press Enter.

Check the result of the command at the COMMAND STATUS window of SMIT. The Command field shows OK while the text below says en2 changed. Escape SMIT by pressing F10.

2. From the AIX command line start SMIT Change / Show Characteristics of a Network Interface

with the command smitty chinet.

Select the second network interface you want to change, for instance en3, until it is highlighted. Press Enter to change. In the INTERNET ADDRESS (dotted decimal) field, type the new IP

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 65

address 100.100.51.121. In the Network MASK (hexadecimal or dotted decimal) field, type the network mask 255.255.255.0 of the new network. Press Enter.

Check the result of the command at the COMMAND STATUS window of SMIT. The Command field shows OK while the text below says en3 changed. Escape SMIT by pressing F10.

Step 6 - Connect to drs_engine2 through the management console (Engine2)

1. Use the PrtSc key on the Keyboard Video Mouse (KVM) keyboard to reach the console. Select

drs-engine2 (or whatever name you are using). Login to the P5 520 with user dr550. . Hit Enter to get the login screen. Login dr550 Password xxxxxx

2. Once successfully logged on as dr550, issue the AIX command su - root to switch to root. Now

you have the necessary AIX system rights to change the network settings and to reconfigure HACMP. su – root Password xxxxxx

Step 7 - Edit the /etc/hosts file on drs_engine2

1. First of all create a copy of the /etc/hosts file that is shipped from factory with the AIX command

cp /etc/hosts /etc/hosts.factory.

2. Open the /etc/hosts file with an editor of your choice, for instance use vi (AIX command to start vi

and open the file is vi /etc/hosts).

If you are not familiar with AIX editors, we suppose you use xedit, an X-window based editor. For the latter, you first need to start an X-session. Start the X-session with the AIX command startx (see startx manpages for details by issuing man startx). Then open the /etc/hosts file with the AIX command xedit /etc/hosts, this will open a graphical editor session.

Change the all the preconfigured addresses according to the table you have prepared in Step1. Only change these addresses, do not change addresses not listed in the table above, or any words in the /etc/hosts file. Change the addresses in all stanzas of the /etc/hosts file. That is, you have to change five addresses.

3. Save the file and exit the editor by pressing Save and Close on the scroll bar.

Step 8 - Change the TCP/IP addresses for the interfaces en2 and en3

1. From the AIX command line start SMIT Change / Show Characteristics of a Network Interface

with the command smitty chinet.

Select the first network interface you want to change, for instance en2, until it is highlighted. Press Enter to change. In the INTERNET ADDRESS (dotted decimal) field, type the new IP address 100.100.52.111. In the Network MASK (hexadecimal or dotted decimal) field, type the network mask 255.255.255.0 of the new network. Press Enter.

Check the result of the command at the COMMAND STATUS window of SMIT. The Command field shows OK while the text below says en2 changed. Escape SMIT by pressing F10.

2. From the AIX command line start SMIT Change / Show Characteristics of a Network Interface

with the command smitty chinet.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 66

Select the second network interface you want to change, for instance en3, until it is highlighted. Press Enter to change. In the INTERNET ADDRESS (dotted decimal) field, type the new IP address 100.100.51.123. In the Network MASK (hexadecimal or dotted decimal) field, type the network mask 255.255.255.0 of the new network. Press Enter.

Check the result of the command at the COMMAND STATUS window of SMIT. The Command field shows OK while the text below says en3 changed. Escape SMIT by pressing F10.

Step 9 - Verify the new addresses are working

1. From the AIX command line use the command ping for all the addresses (except the cluster

service address) to verify they are working correctly. Because you are logged in to drs_engine2, start to ping on drs_engine2. See Ping command to verify IP addresses are working for the ping command and its results. Stop the ping command each time a result is displayed with the Ctrl+C key combination.

Ping command to verify IP addresses are working

# ping 100.100.51.123 PING 100.100.51.123: (100.100.51.123): 89.6 data bytes 64 bytes from 100.100.51.123: icmp_seq=0 ttl=255 time=0 ms 64 bytes from 100.100.51.123: icmp_seq=1 ttl=255 time=0 ms 64 bytes from 100.100.51.123: icmp_seq=2 ttl=255 time=0 ms ^C

----100.100.51.123 PING Statistics---3 packets transmitted, 3 packets received, 0% packet loss Round-trip min/avg/max = 0/0/0 ms

You should check all 4 addresses with the ping command.

1. Use the Keyboard Video Mouse (KVM) switch to go back to drs_engine1, that is, use the PrtSc

key and select drs_engine1 (or whatever name you are using). Since you never logged off from that engine, you do not need to identify yourself again. Use the ping command again to verify all addresses (except the cluster service address) are working correctly. Stop the ping command each time a result is displayed with the Ctrl+C key combination.

Important: Network connectivity is important for HACMP functionality. Verify network connectivity any time you make changes to the network interfaces or network environment.

Step 10 - Remove network from the HACMP cluster

Regardless on what engine you are, start the SMIT HACMP menus by typing smitty hacmp on an AIX command line.

1. Go to Extended Configuration -> Extended Topology Configuration -> Configure HACMP

Networks -> Remove a Network from the HACMP Cluster. In the Select a Network to Remove window, select net_ether_01 (make sure not to select net_ether_02, because this is the

HACMP heartbeat network) and press Enter.

2. In the ARE YOU SURE? window, press Enter to proceed. Check that the result is OK, press F3

twice.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 67

Step 11 - Define the new HACMP network

Still within the HACMP menus of SMIT, configure the new HACMP network for both nodes.

1. Go to Configure HACMP Nodes -> Change/Show a Node in the HACMP Cluster and select

node drs_engine1. Highlight the Communication Path to Node field and press F4 to select a new path for this node. From the list, select the new boot IP address drs_engine1_boot (100.100.51.121 – this is just an example, use the address you received from the network administrator) and press Enter. Press Enter again to change the path and verify the result is OK.

2. Press F3 twice. Go to Change/Show a Node in the HACMP Cluster again and select node

drs_engine2. Highlight the Communication Path to Node field (where the old value for the path is displayed) and press F4 to select a new path for this node. From the list, select the new boot IP address drs_engine2_boot (100.100.51.123) and press Enter. Press Enter again to change the path and verify the result is OK.

3. Step back by pressing F3 (should be four times), until you reach the Extended Configuration

window. Select Discover HACMP-related Information from Configured Nodes and verify the result is OK. Escape with F3.

4. Go to Extended Topology Configuration -> Configure HACMP Networks -> Add a Network

to the HACMP Cluster and select ether below the discovered IP-based network types stanza. In the Network Name field type net_ether_01 and verify that the correct netmask for your network is presented in the Netmask field. Change the Enable IP Address Takeover via IP Aliases field to No (you can use the Tab key or select with F4 key). Press Enter and verify the result is OK. Press the F3 key three times.

5. In the Extended Topology Configuration go to Configure HACMP Communication

Interfaces/Devices -> Add Communication Interfaces/Devices and select Add Discovered Communication Interface and Devices. Select Communication Interfaces. Select

net_ether_01 and press Enter.

In the list, scroll down and select the boot (en3) and standby (en2) interfaces for both nodes with the F7 key. Make sure you selected four interfaces in all. Press Enter and verify the result is OK. Use the F3 key three times.

Step 12 - Create the network resource cluster address within HACMP

1. Go to Extended Resource Configuration -> HACMP Extended Resources Configuration ->

Configure HACMP Service IP Labels/Addresses -> Add a Service IP Label/Address -> Configurable on Multiple Nodes, select net_ether_01 and press Enter.

2. In the IP Label/Address field, press F4. From the list, select drs_cluster_svc and press Enter.

Press Enter again to start the SMIT process and verify that the result is OK.

Step 13 - Add the new network resource to the HACMP resource group

1. Press F3 (normally five times) until you reach the Extended Configuration window. Go to

Extended Resource Configuration -> HACMP Extended Resource Group Configuration -> Change/Show Resources and Attributes for a Resource Group, select drs_450_rg and press Enter.

2. In the Service IP Label/Addresses field, press F4. Select drs_cluster_svc and press Enter.

Press Enter again to start the SMIT process and verify that the result is OK.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 68

Step 14 - Verify and synchronize the HACMP cluster

1. Use the F3 key (normally four times) to go back to the Extended Configuration window. Go to

Extended Verification and Synchronization and press Enter.

2. In the next window use the default settings and press Enter.

3. Check the SMIT result screen for an OK status and quit SMIT with the F10 key.

Step 15 - Start the HACMP cluster

Now that the configuration of the HACMP cluster is completed, the cluster can be started.

Whether you start it for the first time as would normally be the case after the procedure above, or as part of the normal operations of the DR550, the procedure is the same. The procedure is listed below.

The following steps describe the procedure for starting cluster services on a single node or both nodes in the cluster by executing the C-SPOC /usr/es/sbin/cluster/sbin/cl_rc.cluster command on one of the cluster nodes.

Tip: Because the DR550 is running a two node HACMP cluster, to start only one of the both nodes is not a usual task. To start only one node is needed for maintenance tasks only. Hence the normal starting procedure for HACMP in the DR550 always includes the starting of both nodes.

1. Log in to either of the P5 520 servers (such as drs_engine1). Login in a user dr550and switch to

root. You can switch to root with the AIX command su - root. Login dr550 Password xxxxxx su – root Password xxxxxx

2. On the AIX command line start SMIT by issuing the command smitty cl_admin.

3. Go to Manage HACMP Services -> Start Cluster Services and press Enter.

4. Use the default settings when you want to start only one of the both nodes (recommended for

maintenance tasks only). Press Enter.

Use the F4 key in Start Cluster Services on these nodes field when you want to start the cluster services on both nodes (recommended). A pop-up window (Start Cluster Nodes on these nodes) appears. Select both nodes with the F7 key. Both nodes are marked in front of their line. Press Enter.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 69

Back on the Start Cluster Services screen, check that both nodes are shown in the appropriate line and press Enter.

5. To start the cluster services may take a few minutes. Do not interrupt this process and wait for the OK

message at the end of the process.

6. When command execution completes, and HACMP Cluster Services are started on all nodes

specified; SMIT displays a command status window. It should display an OK message in the upper left corner. If not, you have to analyze the given messages at the same window, fix the problem, and start the process again.

If cluster services fail to start on any cluster node, check the C-SPOC utility log file named /tmp/cspoc.log for error messages. This file contains the command execution status of the CSPOC command executed on each cluster node.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 70

7. Go to System Management (C-SPOC) -> Manage HACMP Services -> Show Cluster Services

and press Enter.

8. Check the SMIT result screen. It should display an OK message in the upper left corner, and three

running cluster subsystems and their AIX process id (PID).

9. Quit the SMIT session: Press F10 or ESC+0.

Tip: The HACMP cluster will automatically start the IBM System Storage Archive Manager server. Depending on your DR550 configuration, it may take several minutes to start the ITSM server. So, if an ITSM login fails directly after HACMP start, try again later.

Step16 - Edit the IBM System Storage Archive Manager client option file (dsm.sys)

You need to adjust the IBM Tivoli Storage Manager (ITSM) client system options file, so that the ITSM API or any ITSM client (like dsmadmc) can find the IBM System Storage Archive Manager server.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 71

1. On the first IBM eServer p5 520 server drs_engine1, replace the value in the

/usr/tivoli/tsm/client/ba/bin/dsm.sys file for the tcpserveraddress with your new HACMP cluster service address. We recommend that you do NOT use a dot address, for instance

100.100.51.122 (if you must use an address, you should use the address provided by your network administrator), use the TCP/IP domain name instead, that is drs_service_svc.

To replace the value, use an editor of your choice, for instance use vi (AIX command to start vi and open the file is vi /usr/tivoli/tsm/client/ba/bin/dsm.sys).

If you are not familiar with AIX editors, you may want to use xedit, an X-window based editor. For the latter, you first need to start an X-session. Start the X-session with the AIX command startx (see startx manpages for details by issuing man startx). Then open the /usr/tivoli/tsm/client/ba/bin/dsm.sys file with the AIX command xedit /usr/tivoli/tsm/client/ba/bin/dsm.sys this will open a graphical editor session.

2. Save the file and exit the editor by using Save and Close on the scroll bar.

3. Connect to the IBM System Storage Archive Manager server from drs_engine1 with the

command dsmadmc. Login with the ITSM administrator admin and his password. Verify the connection with the ITSM command query session. Exit the administrative command line client with the ITSM command quit.

4. Switch to the second server, using the Prt Scr key. On the second P5 520 server drs_engine2,

replace the value in the /usr/tivoli/tsm/client/ba/bin/dsm.sys file for the tcpserveraddress with your new HACMP cluster service address. We recommend that you do NOT use a dot address, for instance 100.100.51.122 (if you must use an address, then use the address provided by the network administrator), use the TCP/IP domain name instead, that is drs_service_svc.

To replace the value, use an editor of your choice, for instance use vi (AIX command to start vi and open the file is vi /usr/tivoli/tsm/client/ba/bin/dsm.sys).

If you are not familiar with AIX editors, we suppose you use xedit, an X-window based editor. For the latter, you first need to start an X-session. Start the X-session with the AIX command startx (see startx manpages for details by issuing man startx). Then open the /usr/tivoli/tsm/client/ba/bin/dsm.sys file with the AIX command xedit /usr/tivoli/tsm/client/ba/bin/dsm.sys this will open a graphical editor session.

5. Save the file and exit the editor. In case you are running an X-session for your editor, quit the X-

session by pressing the Ctrl+Alt+Backspace key combination.

6. Connect to the IBM System Storage Archive Manager server from drs_engine2 with the

Step 17 - Logoff all sessions

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 72

After successful configuration you should exit all shells on both nodes with the AIX command exit. Depending on the actual shells, you must type the exit command more than once. For example, enter exit one time to close the shell of root and one time to close the shell of dr550. Repeat it until you see the AIX login prompt on both management console sessions.

Remember to close all sessions on both engine1 and engine2.

Cluster Snapshot

The cluster snapshot utility allows you to save to a file a record of all the data that defines a particular cluster configuration. This facility gives you the ability to recreate a particular cluster configuration—a process called applying a snapshot—provided the cluster is configured with the requisite hardware and software to support the configuration. In addition, a snapshot can provide useful information for troubleshooting cluster problems. Because the snapshots are simple ASCII files that can be sent via e-mail, they can make remote problem determination easier. Perform a cluster snapshot after changes have been made to the cluster configuration. I.e. TCP/IP changes to networks that are used by the cluster, or additional storage that is used by the cluster, etc.

It is good practice to create a cluster snapshot whenever changes have been made to the cluster. Only apply a cluster snapshot if you need to go back to a different cluster configuration.

Information Saved in a Cluster Snapshot

The primary information saved in a cluster snapshot is the data stored in the HACMP Configuration Database classes (such as HACMPcluster, HACMPnode, HACMPnetwork, HACMP daemons).This is the information used to recreate the cluster configuration when a cluster snapshot is applied.

The cluster snapshot does not save any user-customized scripts, applications, or other non-HACMP configuration parameters. For example, the names of application servers and the locations of their start and stop scripts are stored in the HACMP server Configuration Database object class. However, the scripts themselves as well as any applications they may call are not saved. If you

have not modified the DR550 with additional scripts, then it does not apply.

Creating (Adding) a Cluster Snapshot

You can initiate cluster snapshot creation from any cluster node. You can create a cluster snapshot on a running cluster. The cluster snapshot facility retrieves information from each node in the cluster. Accessibility to all nodes is required. The snapshot is stored on the local node. To create a cluster snapshot:

1. Enter smit hacmp

2. In SMIT, select HACMP Extended Configuration > Snapshot Configuration > Add a Cluster Snapshot and press Enter.

3. Enter any appropriate field values.

You have now created a cluster snapshot.

Applying a Cluster Snapshot

Applying a cluster snapshot overwrites the data in the existing HACMP Configuration Database classes on all nodes in the cluster with the new Configuration Database data contained in the snapshot. You can apply a cluster snapshot from any cluster node. Applying a cluster snapshot may affect HACMP Configuration Database objects and system files as well as user-defined files. If cluster services are inactive on all cluster nodes, applying the snapshot changes the

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 73

Configuration Database data stored in the system default configuration directory (DCD). If cluster services are active on the local node, applying a snapshot triggers a cluster-wide dynamic reconfiguration event. If the apply process fails or you want to go back to the previous configuration for any reason, you can re-apply an automatically saved configuration. To apply a cluster snapshot using SMIT, perform the following steps:

1. Enter smit hacmp

2. In SMIT, select HACMP Extended Configuration > Snapshot Configuration > Apply a Cluster Snapshot and press Enter. SMIT displays the Cluster Snapshot to Apply panel containing a list of all the cluster snapshots that exist in the directory specified by the SNAPSHOTPATH environment variable. 3. Select the cluster snapshot that you want to apply and press Enter. SMIT displays the Apply a Cluster

Snapshot panel.

Undoing an Applied Snapshot

Before the new configuration is applied, the cluster snapshot facility automatically saves the current configuration in a snapshot called ~snapshot.n.odm, where n is either 1, 2, or 3. The saved snapshots are cycled so that only three generations of snapshots exist. If the apply process fails or you want to go back to the previous configuration for any reason, you can re-apply the saved configuration.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 74

Remote Mirroring

DR550 now includes the option of replicating archive data from one DR550 to another. This replication is done between the DS4100 controller in the primary DR550 and the DS4100 controller in the secondary DR550. The replication is done synchronously, thus creating a real time copy in the secondary site. A failure in the primary site would allow the users to bring up the secondary site and continue with archiving. When ordering the replication option, several additions will be included in the DR550. The additions apply to both the primary DR550 and the secondary DR550. The additions include a larger switch (2005-B16 with 12 ports active instead of the 2005-B16 with 4 or 8 ports active), additional fibre channel cables, and the Enhanced Remote Volume Mirroring feature for the DS4100 controller (manufacturing will install and enable the premium keys required). Additional zoning will be setup for the larger switch.

Note: Data Replication using DS4100 Enhanced Remote Mirroring is only available for configurations ranging from 5.6 TB to 44.8 TB. No DS4100 based data replication is currently available for the 89.6 TB configurations or for configurations that extend beyond 44.8 TB.

Remote mirroring requires feature code 7355 to be installed on the DS4100 (disk controller). This is done in the factory. This feature enables the premium keys associated with remote mirroring.

Enabling remote mirroring requires some changes in the standard DR550. A larger switch is required (16 ports rather than 8 ports). Additional cabling is needed between the DS4100 controller and the switch. One of the switch ports must be designated at an e-port (ISL). All of these changes are done at the factory when the remote mirroring function is specified in the order.

Management Network Environment

It is mandatory, that the managing host (that is the host or workstation used to manage the Storage Server using the DS4000 Storage Manager software) can simultaneously access the primary and secondary Storage Server through the Ethernet (IP) network. In other words, make sure that Ethernet ports on each Storage Server are on the same subnet or part of a Virtual Private Network (VPN) connection.

Zoning diagrams (single and dual node)

For single node configurations, the SAN zoning will be setup in the factory as shown below. Please note that zone 2 is not used in a single node configuration. Zone 3 is for tape and should not be modified. Zones 4 & 5 are used for remote mirroring.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 75

Switch Zoning when Remote Mirroring is installed (Factory Settings)

Engine

DS4100_1

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Not

Zoned

Slot 5

Controller A-1

0 2

Note: Zone 3 is configured for use with tape (3592 with WORM cartridges are recommended - ports 5-7 are available to connect to tape drives) Zones 4 & 5 are configured for use with data replication (DS4100 enhanced remote volume mirroring) Per IBM recommendations, the ports used to connect the switches are not included in the zones for remote mirroring

Controller A-2

4 5 6 7

Slot 4

Controller B-1

2005_1 (RACK1 EIA 17)

Connects to Switch in secondary DR550

Controller B-2

Slot 1

For dual node configurations, the SAN zoning will be setup in the factory as shown below. Please note that zone 3 should only be used for tape. If no tape is attached, then the zone should not be modified. Zones 4 and 5 are used for remote mirroring.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 76

Switch Zoning when Remote Mirror is

installed up (Factory Settings)

Engine1

Engine2

DS4100_1

Not Zoned

e-port to connect to Switch in secondary DR550

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Slot 5

Controller A-1

0 2 3

2 3

10 11

2005_1 (RACK1 EIA 17)

Controller A-2

Slot 4

Controller B-1

0 2 3

2005_2 (RACK1 EIA 22)

2 3

Controller B-2

Slot 1

Zone 1

Zone 2

Zone 3

Zone 4

Zone 5

Not Zoned

e-port to connect to Switch in secondary DR550

NOTE: It is recommended to have a plan of action before installing and using RVM. Here are a couple of RVM related questions you may want to ask yourself before installing and using RVM. This list is just some examples and is not complete. Each administrator knows their systems and is encouraged to compile procedures related to their environment and RVM.

The DR550 is set to manual synchronization by default and should be left as is. As a system administrator you want to be able to tell it when to sync up to be able to control data integrity. Understanding which site is the primary and which is the secondary site is critical. How does it change in the event of replication disruption?

In the event that disruption in replication does occur at the primary site, does the secondary site become the permanent primary site?

Do you move to secondary site if disruption in replication does occur at primary site and when primary is fixed move everything back to primary?

Are backups being used at one or both sites?

Speed of replication depends on many factors, including replication settings, distance link between sites, speeds, etc. Daily updates to secondary site are fairly quick but a total resynchronization will take longer. Do you have an idea of these times?

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 77

Setting up DR550 for remote mirroring

Review the DS4000 redbook for remote mirroring setup. The redbook can be found at http://publib-

b.boulder.ibm.com/abstracts/sg247010.html?Open. Chapter 9 includes information on enhanced

remote mirroring. You will to need to set up remote mirroring for all logical volumes, including the TSM data base, log files and the entire TSM storage pool. Depending in the capacity, there could be as many as 22 volumes. All must be included in the mirrored set.

When remote mirroring is activated, data will be sent to the remote (secondary) DR550 via the SAN. The connection must be made between port 10 in the SAN switch (both switches is a dual node configuration) in the primary DR550 and port 10 in the SAN switch (both switches in a dual node configuration). This connection is shown in the diagrams below. Port 10 has been configured in the factory as an e-port or ISL port.

The cable or cables used between the primary and secondary sites are the responsibility of the user. IBM cabling guides provide the specs required for these cables.

Ethernet connection (for

management purposes)

2 (or 1 if single node – not

shown) SAN connections using Fiber-optic cables (up to 10km)

If you desire longer distance, you can implement extension technology such as that available from McData or similar vendors. This includes DWDM and CWDM technology. The distance can be extended up to 100 km. This technology is not included with DR550, but must be sourced from the appropriate vendor. When using Metro Mirror or Global Mirror over network technologies such as Fibre Channel, Ethernet/IP, ATM-OC3, and T1/T3, IBM supports the configuration with the expectation that the channel extension provider will provide support, service, and specify supported distances, line quality requirements and attachment capability. In other words, the network provider owns support for the network.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 78

management purposes

Ethernet Connection (for

2 (only 1 if single node) SAN connections using Fiber-optic cables and extension (DWDM or CWDM technology)

Recovery from the primary failure

To recover from a failure at the primary site, you will need to do the following steps at the secondary DR550.

For Single Node implementation (Assuming the AIX server within the secondary DR550 is operational):

Remember that the remote server is not configured to bring up the SSAM server automatically at boot time. If it does start automatically, then disable auto start of the SSAM

server using the following commands (execute ‘‘rmitab autoserv’’ command at AIX prompt as root id.) and disable varyon volume groups. (execute ‘‘chvg ---a’n’ <volume groupname> - for all volume groups except rootvg). --- this is still true for operational AIX just like one below….not to have

TSM up and VGs are down.

1. From the integrated consoles, logon to AIX using the DR550 userid

2. Switch to Root and enter the appropriate password

3. From Root, execute ‘‘cfgmgr’’

4. Enter the following commands

o varyonvg ---y TSMApps, hdisk2 o varyonvg ---y TSMDbLogs, hdisk3 o varyonvg ---y TSMDbBkup, hdisk4 o varyonvg ---y TSMStg hdisk5

5. Then issue the following mount commands

o mount /tsm, o mount /tsmDb, o mount /tsmLog, o mount /tsmdbbkup

6. Change directories using the following command: cd /usr/tivoli/tsm/server/bin

7. Issue the following command: nohup rc.adsmserv &

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 79

8. After a few minutes, log in to TSM using the ADMIN userid and check out TSM server and validate all information and data.

9. At the TSM prompt, the TSM administrator can run q lic, q dbvol, q loglov, q db, q log, q stat, q sys.

10. If needed, you will need to change the IP address within the application server (the server running some type of content management application) to point to the remote DR550.

For Single Node implementation (Assuming AIX server is down --- remember that remote server is not configured to bring up TSM server automatically at boot time. If it does start

automatically, then disable auto start of the SSAM server using the following commands (execute ‘‘rmitab autoserv’’ command at AIX prompt as root id.) and disable varyon volume groups (execute ‘‘chvg ---a’n’ <volume groupname> - for all volume groups except rootvg).

1. Start the server (power on) in the secondary DR550.

2. When the power up cycle is complete and AIX has completed its startup procedures, using the integrated console, logon to AIX using the DR550 userid

3. Switch to Root and enter the appropriate password

4. Enter the following commands

o varyonvg ---y TSMApps, hdisk2 o varyonvg ---y TSMDbLogs, hdisk3 o varyonvg ---y TSMDbBkup, hdisk4 o varyonvg ---y TSMStg hdisk5

5. Issue the following mount commands

o mount /tsm, o mount /tsmDb, o mount /tsmLog, o mount /tsmdbbkup

6. Change directories using the following command: cd /usr/tivoli/tsm/server/bin

7. Issue the following command: nohup rc.adsmserv &

8. After a few minutes, log in to SSAM using the ADMIN userid and check out the SSAM server and validate all information and data.

9. At the TSM prompt the TSM administrator can run q lic, q dbvol, q loglov, q db, q log, q stat, q sys.

10. If needed, you will need to change the IP address within the application server (the server running some type of content management application) to point to the remote DR550.

For Dual Node (HACMP) implementation (Assuming AIX servers are up and HACMP is not up

1. Using the integrated console, logon to both AIX servers. Use the DR550 userid for each server.

2. For each server, Switch to root using the appropriate password.

3. Execute ‘‘cfgmgr’’ on both nodes

4. Start HACMP services on both nodes using the following menu

o smitty hacmp o Select system management (C-SPOC) o Select Manage HACMP services o Select Start cluster services o Select both nodes of the 2nd entry of the screen ‘‘start cluster services on these

nodes….’’

5. This will bring up TSM as part of cluster services then Login to TSM (in 10 minutes) using the ADMIN userid and check out TSM server and validate all information and data.

6. At the TSM prompt the TSM administrator can run q lic, q dbvol, q loglov, q db, q log, q stat, q sys.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 80

7. If needed, you will need to change the IP address within the application server (the server running some type of content management application) to point to the remote DR550.

For Dual Node (HACMP) implementation (Assuming AIX servers are not operational):

1 Start the server (power on) in the secondary DR550. 2 When the power up cycle is complete and AIX has completed its startup procedures, using

the integrated console, logon to AIX using the DR550 userid

3 Switch to Root and enter the appropriate password 4 Start HACMP services on both nodes

o smitty hacmp o system management (C-SPOC) o manage HACMP services o start cluster services o select both nodes of the 2nd entry of the screen ‘‘start cluster services on these nodes….’’

5 This will bring up TSM as part of cluster services then Login (in approx. 10 minutes) as an

admin and check out TSM server and validate all information and data.

6 At the TSM prompt the TSM administrator can run q lic, q dbvol, q loglov, q db, q log, q stat,

q sys.

7 If needed, you will need to change the IP address within the application server (the server

running some type of content management application) to point to the remote DR550.

Setting up DR550 for mirroring back to original site

At this point in time you will have the DR550 operational at the secondary site. All new updates will be coming to this site. The decision that was made prior to this determines if the current secondary site becomes the new primary site or takes the role of the secondary site again once the issues are addressed at the original primary site and all current data is transferred to it.

Either way, you must now redo the Enhanced Volume Mirroring relationship (RVM). As mentioned in the above paragraph, all new data is currently being sent to the secondary site. To make sure that the data is not overwritten and that it is propagated to the other site correctly, you must now remove all RVM relationships from the storage systems. This can be done by just right clicking on any logical drive that is part of a mirror relationship. Select Remove Mirror Relationship -> Select All

-> Remove -> Yes. This will remove all the mirror relationships.

NOTE: You may receive an error if the other Storage Server is not operational. When it has finished, the storage server that has the newest data becomes the primary site (source) and the storage server that had technical issues becomes the secondary site (target).

Recreate the RVM relationship using the storage server with the newest data as the primary and the other storage server as the secondary. NOTE: MAKE SURE THAT YOU CREATE THE RELATIONSHIP CORRECTLY. THE STORAGE SERVER WITH THE NEWEST DATA IS NOW THE PRIMARY (SOURCE). Do this by following the same steps as you did to set up the remote volume mirroring relationship taking into consideration which storage server is now the primary and which is the secondary.

IBM System Storage DR550 Version 3.0 ------17 March 2006 Page 81

IBM DR550 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual