with ibm corp. · dd5 (or dd4) server or servers at the customer site, and r eplacing them with dd6...

IBM TS7650G ProtecTIER Deduplication Gatewayfor ProtecTIER 3.4

iRPQ 8B3668 Server Replacement3958 DD5 (or DD4) with 3958DD6,PN 00VJ411, EC M13702

IBM

Edition notice

This edition is the procedure to replace a 3958 DD5 (or DD4) server with a 3958 DD6 server, and applies only toProtecTIER servers running ProtecTIER version 3.4 or higher.

© Copyright IBM Corporation 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Homologation Statement . . . . . . . ix

Chapter 1. Before installation . . . . . 1Bill of materials to be installed . . . . . . . . 2Prerequisites to this procedure . . . . . . . . 2Installation time . . . . . . . . . . . . . 3Special tools/materials required . . . . . . . . 4

Chapter 2. ProtecTIER model upgrade -3958 DD5 (or DD4) to 3958 DD6replacement . . . . . . . . . . . . . 5Preparation to replace DD5 (or DD4) node B . . . 6

Verify mpath devices on the DD5 (or DD4) node Bbeing replaced . . . . . . . . . . . . . 6Stop the services on the DD5 (or DD4) node Bbeing replaced and power off node B . . . . . 7

Preparation to replace DD5 (or DD4) node A . . . 8Verify mpath devices on the DD5 (or DD4) nodeA being replaced . . . . . . . . . . . . 8Stop the services on the DD5 (or DD4) node Abeing replaced and power off node A . . . . . 9

Clustered Ethernet cabling removal . . . . . . 10

Clustered and Standalone cable connections for theDD6 replacement server . . . . . . . . . . 14Remove and replace node A . . . . . . . . . 16

Remove the existing DD5 (or DD4) node A fromthe frame . . . . . . . . . . . . . . 16

Remove and replace node B . . . . . . . . . 17Remove the existing DD5 (or DD4) node B fromthe frame . . . . . . . . . . . . . . 17

Install the DD6 chassis in the frame . . . . . . 18Power on and configure DD6 node A. . . . . . 19

Verify mpath devices and Emulex ports on theDD6 node A . . . . . . . . . . . . . 19Recover the configuration of DD6 node A . . . 20Verify that services are UP on DD6 node A . . . 23

Configure DD6 node B . . . . . . . . . . 25Verify mpath devices and Emulex ports on theDD6 node B . . . . . . . . . . . . . 25Recover the configuration of DD6 node B . . . 26Verify that services are UP on DD6 nodes . . . 29

Configure the machine serial number for replacedservers . . . . . . . . . . . . . . . . 31

Configure the machine serial number forreplaced servers for node A . . . . . . . . 31

Notices . . . . . . . . . . . . . . 35

Index . . . . . . . . . . . . . . . 37

© Copyright IBM Corp. 2016 iii

iv iRPQ 8B3668 Server Replacement 3958 DD5 (or DD4)

Figures

1. Ethernet switch and Ethernet connections forthe DD5 (or DD4) server to be removed . . . 11

2. TSSC and customer Ethernet connections forthe DD5 (or DD4) server to be removed . . . 12

3. VTL cluster configuration . . . . . . . . 134. FSI configuration. . . . . . . . . . . 14

5. Frontend and backend connections. . . . . 146. Clustering, replication and customer network

connections for cluster configurations . . . . 157. Replication and customer network connections

for standalone configurations . . . . . . 16

© Copyright IBM Corp. 2016 v

vi iRPQ 8B3668 Server Replacement 3958 DD5 (or DD4)

Tables

1. Roles and responsibilities . . . . . . . . 12. Installation instructions and hardware . . . . 2

3. Supported scenarios for the 3958 DD5 (or DD4)to 3958 DD6 replacement . . . . . . . . 5

© Copyright IBM Corp. 2016 vii

viii iRPQ 8B3668 Server Replacement 3958 DD5 (or DD4)

Homologation Statement

Attention: This product may not be certified in your country for connection byany means whatsoever to interfaces of public telecommunications networks.Further certification may be required by law prior to making any such connection.Contact an IBM® representative or reseller if you have any questions.

© Copyright IBM Corp. 2016 ix

x iRPQ 8B3668 Server Replacement 3958 DD5 (or DD4)

Chapter 1. Before installation

Machines affected

This document provides instructions for replacing a 3958 DD5 (or DD4) serverwith a 3958 DD6 server, and should not be in any way associated with proceduresfor disaster recovery.

Concurrent ECs must be installed together

None

Companion ECs may be installed separately

None

Roles and responsibilities

Table 1. Roles and responsibilities

Task Personnel performing the task

Verify that the server being replaced and thereplacement server are running ProtecTIER®

V3.4. If it is necessary to install a laterProtecTIER version, use the procedureChapter 2, “ProtecTIER model upgrade -3958 DD5 (or DD4) to 3958 DD6replacement,” on page 5.

IBM trained ProtecTIER specialist workingtogether with the customer

Verify mpath devices on the DD5 (or DD4)server being replaced

IBM lab-based services personnel

Stop the services on the DD5 (or DD4)server being replaced.

IBM lab-based services personnel, or atrained ProtecTIER specialist workingtogether with the customer

Power off the node(s). In clusteredconfigurations, there will be 2 nodes.

IBM support services representative (SSR),or a trained ProtecTIER specialist workingtogether with the customer

Disconnect backend and front end cablesfrom the DD5 (or DD4) server

IBM support services representative (SSR)

Disconnect the Replication and Customernetwork cables from the DD5 (or DD4)server


Remove the connections to the TSSCNetwork switch


Remove the connections to the Ethernetswitch 1 and Ethernet switch 2 (in case ofcluster configuration)


Remove the connections to the WTINetwork Power Switch (in case of clusterconfiguration)


Remove the existing DD5 (or DD4) serverfrom the frame


© Copyright IBM Corp. 2016 1

Table 1. Roles and responsibilities (continued)

Task Personnel performing the task

Install the DD6 server into the frame IBM support services representative (SSR)

Verify mpath devices and Emulex ports onthe newly-installed DD6 server

IBM lab-based services personnel

Restore the existing ProtecTIERconfiguration

IBM lab-based services personnel, or atrained ProtecTIER specialist workingtogether with the customer

Register the new DD6 server. IBM support services representative (SSR)

This process is completed during the salestransactions. The serial numbers of the DD6servers are entered into the RETAINdatabase. When a Software Call Homerequest is transmitted from the customersite, a PMR is created. The IBM supportservices representative (SSR) must enter thecustomer number into the system duringRAS configuration, so that the customernumber is transmitted with the SoftwareCall Home request.

Bill of materials to be installedTable 2. Installation instructions and hardware

Bill ofmaterials Quantity Comments

DD6 Canisters 2 If the servers to be replaced are in a clusteredconfiguration, two DD6 replacement canisters arerequired. If the servers to be replaced are in astand-alone configuration, only one replacement canisteris required. These canisters will be contained within anenclosure for either configuration, standalone or cluster.

DD6 Rails 1 set(s) One set of DD6 rails are required for either a stand-aloneor clustered configuration. One set of rails is requiredper enclosure.

Prerequisites to this procedureThe topics in this section provides requirements that must be met before replacingan existing 3958 DD5 (or DD4) with a 3958 DD6.

A trained ProtecTIER specialist must coordinate and plan

It is required that the customer work with a trained ProtecTIER specialist as acoordinator to plan for this RPQ and meet all prerequisites before IBM personnelcome onsite.

TSSC

The TSSC console will no longer be required whenProtecTIER is installed in thenew DD6 servers, it is the client’s decision to reuse the console with otherequipment, however support from ProtecTIER will not be provided for this.

2 iRPQ 8B3668 Server Replacement 3958 DD5 (or DD4)

Call Home functionAfter the removal of the DD5 (or DD4) server or servers and replacementwith the DD6 server or servers, call home function should be alreadyconfigured. Run a test call home to verify it, if the test call home procedurefails please contact you next level of support for assistance.

USB keyboard and graphics capable monitor

Verify that a USB keyboard and graphics capable monitor (or KVM console) isavailable for this procedure. To connect a monitor to the DD6 server a microHDMI to VGA converter is required.

Note: The micro HDMI to VGA converter is not included and must be providedby the customer.

Latest version of ProtecTIER code on all servers

Upgrade all existing nodes to ProtecTIER V3.4. The DD5 (or DD4) server removaland DD6 server installation procedure requires that both the replaced server andthe replacement server are running ProtecTIER V3.4. If it is necessary to installProtecTIER V3.4, use the procedure in Chapter 2, “ProtecTIER model upgrade -3958 DD5 (or DD4) to 3958 DD6 replacement,” on page 5. This task is performedby a trained ProtecTIER specialist.

Dispensation of the replaced server

The replaced system, if owned by the customer, remains with that customer.However, the serial number of the DD5 (or DD4) server being replaced will beremoved from production and will not be supported. The entitlement forwarranty and service for the replacement server is based on the unique serialnumber of the replacement server.

If the system is owned by the Customer:Customers are not required to send the customer-owned servers back toIBM. However, IBM support liability for a replaced server terminates whenthe replacement server is powered up and functional. Although IBMcannot control a customer decision to utilize the server in other areas, orsell the server to a third party, IBM does not support such a decision, norwill IBM provide support for the server or any hardware connectedthereto, or any software installed thereon, unless the customer establishes anew sales/support agreement for the replaced server.

If the customer needs support for the replaced server, the customer should contactIBM sales representative to establish a new sales/support agreement.

Installation time

Note: The DD5 (or DD4) and DD6 servers exceed the weight requirements for 1person. A minimum of 2 are required for this procedure. Removing the existingDD5 (or DD4) server or servers at the customer site, and replacing them with DD6servers requires a full maintenance window. Allow extra time if the configurationat the customer site is clustered.

Chapter 1. Before installation 3

Service action

Estimatedinstallationhours

Estimatedmachine hours

Estimatedsystem hours Number of SSRs

Nonconcurrent(FC 2732 or2722)

4.0 per node less than 2 4-8 2

Special tools/materials requiredv Phillips screwdriver #2v Micro HDMI to VGA converterv External DVD readerv ProtecTIER V3.4 DVD for VTL only

For VTL stand alone:IBM System Storage® ProtecTIER Enterprise Edition Standalone V3.4 (ECM13665 - PN17R7264)

For VTL clusterIBM System Storage ProtecTIER Enterprise Edition Cluster V3.4 (ECM13665 - PN17R7269)

v ProtecTIER V3.4.1 or higher DVD for VTL and FSI

For VTL stand alone:IBM System Storage ProtecTIER Enterprise Edition Standalone V3.4.1(EC M13690 - PN00VJ404)

For VTL clusterIBM System Storage ProtecTIER Enterprise Edition Cluster V3.4.1 (ECM13690 - PN00VJ405)

For FSIIBM System Storage ProtecTIER Enterprise Edition Cluster V3.4.1 (ECM13690 - PN:00VJ405)


Chapter 2. ProtecTIER model upgrade - 3958 DD5 (or DD4) to3958 DD6 replacement

Supported scenarios

Table 3. Supported scenarios for the 3958 DD5 (or DD4) to 3958 DD6 replacement

Conversion model(from - to) Application Single or cluster Hardware

DD5 (or DD4) toDD6

VTL Single TS7650G

DD5 (or DD4) toDD6

VTL Cluster TS7650G

DD5 (or DD4) toDD6

FSI Single TS7650G

Important considerations

Storage backend zoning updateIt is very important to add the new World Wide Names (WWN) of thenew Host Bus Adapters (HBA) of the new DD6 server to your StorageArea Network (SAN). The new WWNs must be attached to exactly thesame logical units than the previous ProtecTIER servers, this way theexisting repository is visible for the new DD6 server. This operation mustbe performed prior executing the server replace procedure, either by theclient or by asking Lab Services to perform it.

Cables and labelsThe labels on the DD5 (or DD4) server cables will not exactly match thelabels provided on the DD6 server. If you are uncertain about cableplacement on the DD6 server, please contact your next level of support.

If the transition is unsuccessfulIf the transition from DD5 (or DD4) to DD6 is not successful, do notattempt to return to the previous configuration (the DD5 (or DD4)configuration) without assistance from IBM Support. The configurationchanges initiated by the conversion alter the Ethernet assignments andthey must be reconfigured manually. Do NOT plug the cables back intothe DD5 (or DD4) server.

Latest version of ProtecTIERThe DD5 (or DD4) server removal and DD6 server installation procedurerequires that both, the replaced server and the replacement server, arerunning ProtecTIER V3.4. If it is necessary to install ProtecTIER V3.4, usethe appropriate procedure. This task is performed by a trained ProtecTIERspecialist (FTSS).

Check the TS7600 Upgrade matrix for more information upgradingProtecTIER. (http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7600_upgrade.doc/ts7600_upgradematrix.html)


http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7600_upgrade.doc/ts7600_upgradematrix.html



If your system is running Follow these steps

ProtecTIER version 3.1.8 or3.1.9

1. Upgrade to ProtecTIER V3.3.7.0 using the procedure in“Upgrading from ProtecTIER version 3.1.8 to Red HatLinux version 5.6 and ProtecTIER 3.3.x” in the followinglink http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7650_3-3.service.doc/ts6750rug_upgrade_rh_pt_31.html

2. Upgrade to ProtecTIER V3.4 using the procedure in“Upgrading Red Hat Linux and ProtecTIER for serversat version 3.3.x” in the following linkhttp://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7650_3-4.service.doc/ts7650rug_upgrading_protectier_34.html?lang=en.Notice this upgrade requires also upgrading Red HatLinux to v5.11.

ProtecTIER version 3.3.x v Upgrade to ProtecTIER V3.4 using the procedure in“Upgrading Red Hat Linux and ProtecTIER for servers atversion 3.3.x” in the following link http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7650_3-4.service.doc/ts7650rug_upgrading_protectier_34.html?lang=en. Noticethis upgrade requires also upgrading Red Hat Linux tov5.11.

Preparation to replace DD5 (or DD4) node BUse the following procedures to prepare for replacing 3958 DD5 (or DD4) node B.

Verify mpath devices on the DD5 (or DD4) node B beingreplaced

Perform the following steps to verify mpath devices.

Before you begin

If you are working with a stand-alone configuration, skip this step and proceed to“Preparation to replace DD5 (or DD4) node A” on page 8.

About this task

This task is performed by IBM lab-based services personnel.

Procedure1. If you have not already done so, log in to the ProtecTIER server by attaching a

keyboard and monitor to the DD5 (or DD4) node B. At the login prompt, type:ptadmin and press <Enter>. At the password prompt, type: ptadmin <Enter>.

2. Verify how many mpath devices are being replaced on the DD5 (or DD4) nodeB. Type the following command at the command line prompt: # multipath -ll|grep mpath |wc -l <Enter>

Note: The system returns the number of mpath devices. This same numbermust be displayed when you verify the mpath devices on the DD6.


http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7650_3-3.service.doc/ts6750rug_upgrade_rh_pt_31.html



http://www.ibm.com/support/knowledgecenter/STLPPL_ent/com.ibm.storage.ts7650_3-4.service.doc/ts7650rug_upgrading_protectier_34.html?lang=en







What to do next

Proceed to “Stop the services on the DD5 (or DD4) node B being replaced andpower off node B.”

Stop the services on the DD5 (or DD4) node B being replacedand power off node B

Perform the following steps to verify stop services on the server.

Before you begin

If you are working with a stand-alone configuration, skip this step and proceed to“Preparation to replace DD5 (or DD4) node A” on page 8.

About this task

This task is performed by IBM lab-based services personnel, or a trainedProtecTIER specialist working together with the customer. Stopping theseservices avoids meta data corruption on the management file system of therepository (if the recognition procedure encounters unexpected issues).


keyboard and monitor to the DD5 (or DD4) node B. At the login prompt, type:ptconfig and press <Enter>. At the password prompt, type: ptconfig and press<Enter>. The system displays the ProtecTIER Service menu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rasap 1------------------------------------------------------------------------------

1) ProtecTIER Configuration (...)2) Manage ProtecTIER services (...)3) Health Monitoring (...)4) Problem Alerting (...)5) Version Information (...)6) Generate a service report7) Generate a system view8) Update ProtecTIER code9) ProtecTIER Analysis (...)

E) Exit------------------------------------------------------------------------------>>> Your choice?

2. From the ProtecTIER Service menu, select Manage ProtecTIER services (...).The system displays the Manage ProtecTIER services (...) menu:

Chapter 2. 3958 DD5 (or DD4) to 3958 DD6 replacement 7

------------------------------------------------------------------------------ProtecTIER Service Menu running on rasap 1

Manage ProtecTIER Services (...)------------------------------------------------------------------------------

1) Display services status2) Start all services3) Stop all services4) Stop ProtecTIER services only (including GFS)5) Stop VTFD service only6) Poweroff This Node7) Reboot This Node

B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. From the Manage ProtecTIER Services (...) menu, select Stop all services. Whenthe services are stopped, the system shows the following messages:

Stoppingptrasd [ Done ]Stoppingvtfd [ Done ]Stoppingptcluster [ Done ]

4. Press <Enter> to return to the Manage ProtecTIER Services (...) menu, thenselect Power off This Node. When the power off processes complete, thePower LED on the server's front panel blinks steadily. This indicates that theserver is in standby node.

What to do next

Proceed to “Preparation to replace DD5 (or DD4) node A”

Preparation to replace DD5 (or DD4) node AUse the following procedures to prepare for replacing 3958 DD5 (or DD4) node A.

Verify mpath devices on the DD5 (or DD4) node A beingreplaced

Perform the following steps to verify mpath devices.

Before you begin

If you are working with a cluster configuration, the section “Preparation to replaceDD5 (or DD4) node B” on page 6 must be completed before you continue. If youare working in a stand-alone configuration, proceed with the steps in thisprocedure.

About this task



keyboard and monitor to the DD5 (or DD4) node A. At the login prompt, type:ptconfig and press <Enter>. At the password prompt, type: ptconfig <Enter>.


2. Verify how many mpath devices are being replaced on the DD5 (or DD4) nodeA. Type the following command at the command line prompt: # multipath -ll|grep mpath |wc -l <Enter>

Note: The system returns the number of mpath devices. This same numbermust be displayed when you verify the mpath devices on the DD6.

What to do next

Proceed to “Stop the services on the DD5 (or DD4) node A being replaced andpower off node A.”

Stop the services on the DD5 (or DD4) node A being replacedand power off node A

Perform the following steps to verify stop services on the server.

Before you begin

If you are working with a cluster configuration, the section “Preparation to replaceDD5 (or DD4) node B” on page 6 must be completed before you continue. If youare working in a stand-alone configuration, proceed with the steps in thisprocedure.

About this task

This task is performed by IBM lab-based services personnel, or a trainedProtecTIER specialist working together with the customer. Stopping theseservices avoids meta data corruption on the management file system of therepository (if the recognition procedure encounters unexpected issues).






2. From the ProtecTIER Service menu, select Manage ProtecTIER services (...).The system displays the Manage ProtecTIER services (...) menu:





B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. From the Manage ProtecTIER Services (...) menu, select Stop all services. Whenthe services are stopped, the system shows the following messages:

Stoppingptrasd [ Done ]Stoppingvtfd [ Done ]Stoppingptcluster [ Done ]

4. Press <Enter> to return to the Manage ProtecTIER Services (...) menu, thenselect Power off This Node. When the power off processes complete, thePower LED on the server's front panel blinks steadily. This indicates that theserver is in standby node.

Clustered Ethernet cabling removalIf a DD6 single node is replacing a DD5 (or DD4) single node, refer to the "ServerA" portions of the figures. If this is a clustered configuration, verify that theexisting cabling matches the appropriate diagram.

Ethernet switch and Ethernet connections for the DD5 (or DD4)server to be removed


Callout On device location

▌1▐ Node A Customer Network

▌2▐ Clustering Server A

▌3▐ Clustering Server A

▌4▐ WTI Network Power Switch

▌5▐ Ethernet Switch 1 / Ethernet Switch 2

▌6▐ Node B Customer Network

▌7▐ Clustering Server B

▌8▐ Clustering Server B

▌19▐ Replication Network Server A

▌20▐ Replication Network Server A

▌26▐ Replication Network Server B

▌27▐ Replication Network Server B

▌30▐ Ethernet switch 1 / Ethernet switch 2

Figure 1. Ethernet switch and Ethernet connections for the DD5 (or DD4) server to be removed


TSSC and customer Ethernet connections for the DD5 (or DD4)server to be removed

Important: Verify the cables are properly tagged before transitioning to the newnode. Due to Ethernet reassigning, the current tags are no longer valid after thereplacement, so current tagging is important for recognition purposes. Followingthe node replacement, mark the cables with their new tag positions in their newlocations. This is very important for the Customer Network and CustomerReplication cables.

Note: If you are working with a stand-alone configuration, refer to the “Server A”portion of Figure 2.


▌9▐ TSSC

▌10▐ Customer Network

▌11▐ Server A RAS Network

▌12▐ Server B RAS Network

Figure 2. TSSC and customer Ethernet connections for the DD5 (or DD4) server to be removed



▌13▐ Server A IMM

▌14▐ Server B IMM

▌21▐ SC KVM

▌22▐ SC Server

▌23▐ Server A

▌24▐ SC KVM

▌25▐ Server B

Backend and frontend cable disconnections for the DD5 (or DD4)server

If a DD6 single node is replacing a DD5 (or DD4) VTL single node, refer to the"Server A" portions of the figures. In case of replacing a DD5 (or DD4) FSI noderefer to figure 4.

Important: Verify the cables are properly tagged before transitioning to the newnode. Current® tagging is important for recognition purposes. Following the nodereplacement, mark the cables with their new tag positions in their new locations.This is very important for the backend fiber connections and the host’s fiberconnections.

Disconnect the fiber channel cables from the backend storage and from the host’sfrontend (in case of VTL configurations they will be fiber cables in case of FSI theywill be Ethernet cables). These cables will be reconnected later in the replaced DD6server.

Figure 3. VTL cluster configuration


Clustered and Standalone cable connections for the DD6 replacementserver

Backend and frontend connections for the DD6 replacementserver

With the DD6 server in place in the rack, proceed to connect the fiber channelcables used for the backend storage. For standalone configurations refer to the“Server A” portion of the figures

Important: In case of FSI 10GB installations there will be only 2 available ports forfrontend connections (hosts).

Clustered Ethernet, replication network and customer cabling forthe DD6 replacement server

With the DD6 server in place in the rack, proceed to connect the cluster cables inthe interface E0. Connect the customer network in the interface E3. In case ofcluster configurations, the replication network will be connected in the interfacesE1 of each canister. In case of standalone configurations, the replication interfaceswill be E0 and E1.

Figure 4. FSI configuration

Figure 5. Frontend and backend connections


Important: Verify the cables are properly tagged before transitioning to the newnode. Due to Ethernet reassigning, the current tags are no longer valid after thereplacement, so current tagging is important for recognition purposes. Followingthe node replacement, mark the cables with their new tag positions in their newlocations. This is very important for the Customer Network and CustomerReplication cables.

Note: If you are working with a stand-alone configuration, refer to the “Server A”portion of Figure 2.

Callout From On device ToOn devicelocation

▌1▐ Port E0, onboard Server A Port E0, onserver B

Server A

▌2▐ Port E1, onboard Server A Replicationnetwork

Server A

▌3▐ Port E1, onboard Server B Replicationnetwork

Server B

▌4▐ Port E2, onboard Server A Customernetwork

Server A

▌5▐ Port E2, onboard Server B Customernetwork

Server B

Figure 6. Clustering, replication and customer network connections for cluster configurations


Standalone replication network and customer cabling for theDD6 replaced server

Callout From On device ToOn devicelocation


Server A


Server A

▌3▐ Port E2, onboard Server A Customernetwork

Server A

Remove and replace node APerform the following steps to remove and replace node A.

Before you begin

Perform the following procedures before you begin removing and replacing nodeA.1. (For clustered configurations), “Preparation to replace DD5 (or DD4) node B”

on page 6.2. “Preparation to replace DD5 (or DD4) node A” on page 8

Important: When replacing a node in a cluster, it is necessary to power off theother nodes in the cluster before the replacement. However, the replacement stepsfor the server (using the menu actions) require the storage controllers to bepowered on while the replacement sequence is initiated.

Remove the existing DD5 (or DD4) node A from the framePerform the following steps to remove the existing node A from the frame.

Figure 7. Replication and customer network connections for standalone configurations


Before you begin

CAUTION:Make sure node(s) being replaced is powered off.

About this task

This task is performed by IBM support services representative (SSR).

Procedure1. Verify that the DD5 (or DD4) node A cables are labeled, and disconnect them

from the rear of the server.2. Remove the existing server. Two people are required to lift the server from the

frame. Slide the blue tabs along the side of the rails forward, and lift the serverfrom the rails.

3. Mark the locations of the rails on the frame. The rails on the DD6 server willmount to the frame using the same holes that the rails of the DD5 (or DD4)server used.

Note: The rails for the DD5 (or DD4) are different than the rails for the DD6,and cannot be used for the DD6 server.

4. Remove the rails and cable management trays that were attached to the DD5(or DD4) rail system.

5. Remove the DD5 (or DD4) rails from the frame.

What to do nextv If this is a standalone configuration, proceed to “Install the DD6 chassis in the

frame” on page 18.v If this is a cluster configuration, proceed to “Remove and replace node B”

Remove and replace node BPerform the following steps to remove and replace node B.

Before you begin

If you are working with a stand-alone configuration, proceed to “Install the DD6chassis in the frame” on page 18.

If you are working with a clustered configuration perform the steps in theprocedure “Remove and replace node A” on page 16 before you begin removingand replacing node B.

About this task

Important: When replacing a node in a cluster, it is necessary to power off theother nodes in the cluster before the replacement. However, the replacement stepsfor the server (using the menu actions) require the storage controllers to bepowered on while the replacement sequence is initiated.

Remove the existing DD5 (or DD4) node B from the framePerform the following steps to remove the existing node B from the frame.


Before you begin

CAUTION:Make sure node(s) being replaced are powered off.

Before continuing with the steps in this procedure, be sure to perform the steps to“Remove and replace node A” on page 16.

About this task


Procedure1. Verify that the DD5 (or DD4) node B cables are labeled, and disconnect them

from the rear of the server.2. Place the server that is to be replaced into the service position (extended to the

front of the frame).3. Remove the existing server. Two people are required to lift the server from the

frame. Slide the blue tabs along the side of the rails forward, and lift the serverfrom the rails.

4. Remove the rails and cable management trays that were attached to the DD5(or DD4) rail system.

5. Remove the DD5 (or DD4) rails from the frame.

What to do nextv Proceed to “Install the DD6 chassis in the frame.”

Install the DD6 chassis in the framePerform the following steps to install the DD6 chassis in the frame.

Before you begin

CAUTION:Make sure the DD6 chassis is powered off.

About this task


The DD6 servers are a 2U enclosure. Within this enclosure it can be 1 or 2canisters, therefore it is not necessary to insert separately node A and node B in theframe, as already mentioned, both are contained within the 2U enclosure.

Procedure1. Insert the DD6 rail assemblies into the frame.2. Install the DD6 chassis by sliding it into the frame.3. Proceed to reconnect the required Ethernet / Fiber Channel cables previously

removed from the DD5 (or DD4) servers to the new DD6 server. Refer to thetables and diagrams in “Clustered and Standalone cable connections for theDD6 replacement server” on page 14


Attention: It is very important the new WWNs of the DD6 server arecorrectly added to the SAN network so they can be attachedto the same LUNsassigned previously to the replaced DD5 (or DD4) server.

Power on and configure DD6 node AThe topics in this section provide instructions to power on and configure the DD6node A.

Verify mpath devices and Emulex ports on the DD6 node APerform the following steps to verify mpath devices and Emulex ports on the DD6node A

Before you begin

Important:

v Verify the SAN zoning for the storage with ProtecTIER back-end ports, andupdate if necessary.

v Verify host mappings for storage LUNs, and update if necessary.

About this task


Procedure1. Power on the DD6 node A, until it displays the login prompt.2. Log in to the ProtecTIER server by attaching a keyboard and monitor to Node

A. At the login prompt, type: ptadmin and press <Enter>. At the passwordprompt, type: ptadmin and press <Enter>.

Important: To attach a monitor to the DD6 server a micro HDMI to VGAconverter is necessary, this should be provided by the customer.

3. Verify how many mpath devices are on the newly-installed DD6 server bytyping the following command at the command prompt:-ll |grep mpath |wc -l <Enter>

Note: The system must display the same mpath device numbers for the DD6as it displayed for the DD5 (or DD4).

4. Verify that the system recognizes all four Emulex ports by typing the followingcommand at the command prompt:# lspci|grep Emulex<Enter>

The system displays the four Emulex ports (similar to the followinginformation):10:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.2 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.3 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)

5. Verify the number of Emulex ports again using the linlpcfg command, asfollows# /usr/sbin/linlpcfg/linlpcfglistWWN|grep -c WWNN <Enter>


The system displays the World Wide Node Names (WWNNs) of the Emulexports. If the system returns less than four WWNNs, reboot the system prior toreplacement to recover all of the ports.

Important: In VTL configurations the frontend and backend cards are bothEmulex, the output of this command should return 8 ports.

What to do next

Proceed to “Recover the configuration of DD6 node A.”

Recover the configuration of DD6 node APerform the following steps to recover the configuration of the DD6 node A

About this task

The replacement steps for the server (using the menu actions) require the storagecontrollers to be powered on while the replacement sequence is initiated. This taskis performed by IBM lab-based services personnel or a trained ProtecTIERspecialist working together with the customer.


keyboard and monitor to the DD5 (or DD4) node A. At the login prompt, type:ptconfig and press <Enter>. At the password prompt, type: ptconfig and press<Enter>. The system displays the ProtecTIER Service menu:




2. From the ProtecTIER Service menu, select ProtecTIER Configuration (...). TheProtecTIER Configuration (...) menu is displayed: The ProtecTIER Configuration(...) menu is displayed:



ProtecTIER Configuration (...)------------------------------------------------------------------------------

1) Configure ProtecTIER node2) Recover Configuration for a replaced server3) Configure machine serial number for a replaced server4) Configure RAS5) Update Time, Date, Timezone & Timeserver(s)6) Scan storage interconnections7) File systems Management (...)8) Configure replication (...)9) IP Network configuration (...)

10) Update Firmware (...)11) Update the system’s name12) Validate configuration13) Single Node - code upgrade14) OS images Management (...)15) Replace SAS drive

B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. Select Recover Configuration for a replaced server.

Note: During a node replacement, when utilizing the menu operations for theconversion, the storage must remain up and operational. The node'sconfiguration is resident inside the storage repository, and must be retrievedwhen the replacement option is requested by the menu operation. The systemwill prompt during the replacement, for verification of the model beingreplaced. This prompt will display the configuration that is stored for themodel being replaced. If this is a cluster, and the companion node is notpowered on, the system will offer the configuration options for both nodes, andyou must select the one you are replacing (node A or node B).The system begins the processing procedure, and displays some output.

Begin Processing Procedure

About to execute:Operation: replaceModel: TS7650GApplication: VTL

Continue? (yes|no)

Note: On a replacement for an FSI application, the Application displays as FSI.4. Type yes and press <Enter> to continue.


Stopping services, please waitStopping Cluster Services [ Done ]Services stopped [ Done ]Checking conditions [ Done ]Checking BOM [ Done ]Checking NICs for Replication [ Done ]Checking repository [ Done ]Checking installed applications [ Done ]Checking local RAID [ Done ]Chcking conditions done

Checking live nodes [ Done ]Model <TS7650G>

Option 1***************************************************

nodeid : 1hostname : kokomoip : 9.11.200.175

Option 2**************************************************

nodeid : 2hostname : auburnip : 9.11.200.173

Select option:

5. Two available options will be displayed, type 1 and press <Enter> to continue,confirm it corresponds to node A.

Important: If the node replace procedure is being performed via BMC interfaceDO NOT CHANGE THE DEFAULT IP ADDRESS. This will cause to lose theconnection to the server.The system displays output similar to the following:

Please enter the following balues for bmc:Application Interface bmc, IP Address [192.168.10.163]:Application Interface bmc, Netmask [255.255.255.0]:Application Interface bmc, Default Gateway [192.168.10.1]:Restoring Frond End HBA WWN [ Done ]Configuring network [ Done ]Configuring Replication Network [ Done ]WARNING: could not detect an active link for eth5Restarting Network Service [ Done ]Stopping cluster [ Done ]Configuring cluster [ Done ]Starting cluster [ Done ]Installing NTP [ Done ]Mounting file systems [ Done ]Restoring node ID [ Done ]Starting VTFD [ Done ]Checking RAS Configuration [ Done ]Restoring RAS Configuration [ Done ]Collecting RAS Persistent configuration [ Done ]Running RAS Eth Agent [ Done ]validation will start in 10 secondsTesting customer netowrk connectivity [ Done ]Testing connectivity to the Default Gateway [ Done ]Getting number of nodes [ Done ]This is a 1 node cluster, will not test fencingvalidation endedreplace ended successfully with warnings

End Processing Procedure Successfully

Press <Enter> to continue


What to do next1. Use ProtecTIER Manager to make sure you can access node A.2. Proceed to “Verify that services are UP on DD6 node A”

Verify that services are UP on DD6 node APerform the following steps to recover the configuration of the DD6 node A

About this task

This task is performed by IBM lab-based services personnel or a trainedProtecTIER specialist working together with the customer.

Keep the DD6 node A in a powered on state. Use the following steps to make surethat all the services are UP on node A.


keyboard and monitor to the DD5 (or DD4) node A. At the login prompt, type:ptconfig and press <Enter>. At the password prompt, type: ptconfig and press<Enter>. The system displays the ProtecTIER Service menu:




2. From the ProtecTIER Service menu select Manage ProtecTIER services (...). Thesystem displays the ProtecTIER Services menu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rassm1



B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. From the ProtecTIER Services menu, select Display services status. TheProtecTIER Configuration (...) menu is displayed:

4. Verify that all services are UP.


If the services are not UP:Select Stop all services. Then restart the services, using the Start allservices option. If they are still down, a reboot might be required torecover the services. If they remain down following the reboot (it mighttake several minutes following the reboot for all the services to restart),contact your next level of support.

Restore and BackupThere is a possibility that the working ports can switch status. (Forinstance, the UP ports might switch status to DOWN, and vice versa.)This indicates that the backup application is not accessing the frontendports. If this occurs, restart the backup application and rescan the forthe working ports. Rescanning for the ports will enable you to accessthe data.

5. When the services are UP on node A, verify the health status of the node usingthe following procedure:a. If you have not already done so, log in to the ProtecTIER server by

attaching a keyboard and monitor to the DD5 (or DD4) node A. At the loginprompt, type: ptconfig and press <Enter>. At the password prompt, type:ptconfig and press <Enter>. The system displays the ProtecTIER Servicemenu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rasap 1------------------------------------------------------------------------------1) ProtecTIER Configuration (...)2) Manage ProtecTIER services (...)3) Health Monitoring (...)4) Problem Alerting (...)5) Version Information (...)6) Generate a service report7) Generate a system view8) Update ProtecTIER code9) ProtecTIER Analysis (...)


b. From the ProtecTIER Service menu, select Health Monitoring (...). Thesystem displays the Health Monitoring menu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rassmx

Health Monitoring (...)------------------------------------------------------------------------------1) Display health summary for this node2) Display detailed health for this node3) Run a full check on this node4) List open problems5) Service Mode

B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

c. Select Display health summary for this node.If the health status shows OK, proceed as instructed. If the health status isDegraded or Failed, select Display detailed health for this node, identify thefailing component (or components), make the required corrections andrecheck the health status. If you are unable to correct the failing condition,contact your next level of support.


What to do next1. If you are working with a stand-alone configuration, proceed to “Configure the

machine serial number for replaced servers” on page 312. If you are working with a cluster configuration, proceed to “Configure DD6

node B”

Configure DD6 node BThe topics in this section provide instructions to power on and configure the DD6node B.

Verify mpath devices and Emulex ports on the DD6 node BPerform the following steps to verify mpath devices and Emulex ports on the DD6node B

Before you begin

Important:

v Verify the SAN zoning for the storage with ProtecTIER back-end ports, andupdate if necessary.

v Verify host mappings for storage LUNs, and update if necessary.

About this task


Procedure1. Since node A and node B are part of the same chassis, both nodes should be

powered on. There is no need to turn on separately node B. Verify node B isalready turned on and in the login prompt.

2. If you have not already done so, log in to the ProtecTIER server by attaching akeyboard and monitor to Node B. At the login prompt, type: ptadmin and press<Enter>. At the password prompt, type: ptadmin and press <Enter>.Attention: To attach a monitor to the DD6 server a micro HDMI to VGAconverter is necessary, this should be provided by the customer.

3. Verify how many mpath devices are on the newly-installed DD6 server bytyping the following command at the command prompt:-ll |grep mpath |wc -l <Enter>

Note: The system must display the same mpath device numbers for the DD6as it displayed for the DD5 (or DD4).

4. Verify that the system recognizes all four Emulex ports by typing the followingcommand at the command prompt:# lspci|grep Emulex<Enter>

The system displays the four Emulex ports (similar to the followinginformation):10:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.2 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)10:00.3 Fibre Channel: Emulex Corporation Lancer-X: LightPulseFibre Channel Host Adapter (rev 30)

5. Verify the number of Emulex ports again using the linlpcfg command, asfollows


# /usr/sbin/linlpcfg/linlpcfglistWWN|grep -c WWNN <Enter>

The system displays the World Wide Node Names (WWNNs) of the Emulexports. If the system returns less than four WWNNs, reboot the system prior toreplacement to recover all of the ports.

Important: In VTL configurations the frontend and backend cards are bothEmulex, the output of this command should return 8 ports.

What to do next

Proceed to “Recover the configuration of DD6 node B.”

Recover the configuration of DD6 node BPerform the following steps to recover the configuration of the DD6 node B

About this task

The replacement steps for the server (using the menu actions) require the storagecontrollers to be powered on while the replacement sequence is initiated. This taskis performed by IBM lab-based services personnel or a trained ProtecTIERspecialist working together with the customer.












B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. Select Recover Configuration for a replaced server.

Note: During a node replacement, when utilizing the menu operations for theconversion, the storage must remain up and operational. The node'sconfiguration is resident inside the storage repository, and must be retrievedwhen the replacement option is requested by the menu operation. The systemwill prompt during the replacement, for verification of the model beingreplaced. This prompt will display the configuration that is stored for themodel being replaced. If this is a cluster, and the companion node is notpowered on, the system will offer the configuration options for both nodes, andyou must select the one you are replacing (node A or node B).The system begins the processing procedure, and displays some output.


About to execute:Operation: replaceModel: TS7650GApplication: VTL

Continue? (yes|no)

Note: On a replacement for an FSI application, the Application displays as FSI.4. Type yes and press <Enter> to continue.


Stopping services, please waitStopping Cluster Services [ Done ]Services stopped [ Done ]Checking conditions [ Done ]Checking BOM [ Done ]Checking NICs for Replication [ Done ]Checking repository [ Done ]Checking installed applications [ Done ]Checking local RAID [ Done ]Chcking conditions done

Checking live nodes [ Done ]Model <TS7650G>

Option 1***************************************************

nodeid : 1hostname : auburnip : 9.11.200.173

5. Since there is only one pending node to replace, only one available option willbe displayed, confirm it corresponds to node B. Type 1 and press <Enter> tocontinue.

Important: If the node replace procedure is being performed via BMC interfaceDO NOT CHANGE THE DEFAULT IP ADDRESS. This will cause to lose theconnection to the server.The system displays output similar to the following:

Please enter the following balues for bmc:Application Interface bmc, IP Address [192.168.10.164]:Application Interface bmc, Default Gateway [192.168.10.1]:Application Interface bmc, Netmask [255.255.255.0]:Restoring Frond End HBA WWN [ Done ]Configuring network [ Done ]Configuring Replication Network [ Done ]WARNING: could not detect an active link for eth5Restarting Network Service [ Done ]Stopping cluster [ Done ]Configuring cluster [ Done ]Starting cluster [ Done ]Installing NTP [ Done ]Mounting file systems [ Done ]Restoring node ID [ Done ]Starting VTFD [ Done ]Checking RAS Configuration [ Done ]Restoring RAS Configuration [ Done ]Collecting RAS Persistent configuration [ Done ]Running RAS Eth Agent [ Done ]validation will start in 10 secondsTesting customer netowrk connectivity [ Done ]Testing connectivity to the Default Gateway [ Done ]Getting number of nodes [ Done ]This is a 1 node cluster, will not test fencingvalidation endedreplace ended successfully with warnings

End Processing Procedure Successfully

Press <Enter> to continue

What to do next

Proceed to “Verify that services are UP on DD6 nodes” on page 29


Verify that services are UP on DD6 nodesPerform the following steps to recover the configuration of the DD6 nodes

About this task

This task is performed by IBM lab-based services personnel or a trainedProtecTIER specialist working together with the customer.

Procedure1. Use the following steps to verify that services are UP on node B:

a. If you have not already done so, log in to the ProtecTIER server byattaching a keyboard and monitor to the DD5 (or DD4) node B. At the loginprompt, type: ptconfig and press <Enter>. At the password prompt, type:ptconfig and press <Enter>. The system displays the ProtecTIER Servicemenu:



b. From the ProtecTIER Service menu select Manage ProtecTIER services (...).The system displays the ProtecTIER Services menu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rassm1

Manage ProtecTIER Services (...)------------------------------------------------------------------------------1) Display services status2) Start all services3) Stop all services4) Stop ProtecTIER services only (including GFS)5) Stop VTFD service only6) Poweroff This Node7) Reboot This Node

B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

c. From the ProtecTIER Services menu, select Display services status. TheProtecTIER Configuration (...) menu is displayed:

d. Verify that all services are UP.

If the services are not UP:Select Stop all services. Then restart the services, using the Start allservices option. If they are still down, a reboot might be required torecover the services. If they remain down following the reboot (itmight take several minutes following the reboot for all the servicesto restart), contact your next level of support.


Restore and BackupThere is a possibility that the working ports can switch status. (Forinstance, the UP ports might switch status to DOWN, and viceversa.) This indicates that the backup application is not accessingthe frontend ports. If this occurs, restart the backup application andrescan the for the working ports. Rescanning for the ports willenable you to access the data.

2. Once both the servers are up and running, use ProtecTIER Manager to makesure you can access both nodes.

Note: Once the DD6 node A reaches the command prompt, it might reboot theDD6 node B. It is possible that node A and node B reboot each other acouple(or more) times. After the nodes have finished rebooting, they will reachworking condition. It is important that neither of the servers are fenced.If eitherserver is fenced, log in to the server and perform the following steps:a. From the ProtecTIER Service Menu, select Manage ProtecTIER services (...).b. From the Manage ProtecTIER services (...) menu, select Stop all services.c. Then restart the services, using the Start all services services option. If

either server remains fenced, contact your next level of support.3. Use the following steps to make sure that all the services are UP on node A.

a. From the ProtecTIER Service Menu, select Manage ProtecTIER services (...).b. From the Manage ProtecTIER services (...) menu, select Display service

status.c. Verify that all services are UP.

If the services are not UP:Select Stop all services. Then restart the services, using the Start allservices option. If they are still down, a reboot might be required torecover the services. If they remain down following the reboot (itmight take several minutes following the reboot for all the servicesto restart), contact your next level of support.

Restore and BackupThere is a possibility that the working ports can switch status. (Forinstance, the UP ports might switch status to DOWN, and viceversa.) This indicates that the backup application is not accessingthe frontend ports. If this occurs, restart the backup application andrescan the for the working ports. Rescanning for the ports willenable you to access the data.

4. When the services are UP on both nodes, verify the health status of each nodeusing the following procedure:a. If you have not already done so, log in to the ProtecTIER server by

attaching a keyboard and monitor to the DD5 (or DD4) node A. At the loginprompt, type: ptconfig and press <Enter>. At the password prompt, type:ptconfig and press <Enter>. The system displays the ProtecTIER Servicemenu:




b. From the ProtecTIER Service menu, select Health Monitoring (...). Thesystem displays the Health Monitoring menu:

------------------------------------------------------------------------------ProtecTIER Service Menu running on rassmx

Health Monitoring (...)------------------------------------------------------------------------------1) Display health summary for this node2) Display detailed health for this node3) Run a full check on this node4) List open problems5) Service Mode

B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

c. Select Display health summary for this node.If the health status shows OK, proceed as instructed. If the health status isDegraded or Failed, select Display detailed health for this node, identify thefailing component (or components), make the required corrections andrecheck the health status. If you are unable to correct the failing condition,contact your next level of support.

d. Repeat steps a through c on node B.

What to do next1. Use ProtecTIER Manager to make sure you can access node B.2. Proceed to “Configure the machine serial number for replaced servers”

Configure the machine serial number for replaced serversThe following topics provide instructions to configure the machine serial numbersfor the servers that have been replaced.

Configure the machine serial number for replaced servers fornode A

Perform the following steps to configure the machine serial number for node Areplacement servers.


keyboard and monitor to the DD5 (or DD4) node A. At the login prompt, type:


ptconfig and press <Enter>. At the password prompt, type: ptconfig and press<Enter>. The system displays the ProtecTIER Service menu:









B) BackE) Exit

------------------------------------------------------------------------------>>> Your choice?

3. Select Configure machine serial number for a replaced server.4. Type the new serial number for the DD6 node A. The system begins the

processing procedure, and displays some output.


The current serial number on the VPD is [78XX##]Do you want to change the serial number on the VPD? (yes|no)Please enter a 7 alphanumeric string e.g. 5QR7Yt6:78IBM00Press <Enter> to continue

What to do next

If working with a standalone configurations the new DD6 replacement procedureis finished.


If working with cluster configurations repeat the steps for “Configure the machineserial number for replaced servers for node A” on page 31 in node B, using thesame serial number you configured in node A.

Important: The nodes within the enclosure will share the machine serial number.


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATIONS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have been


estimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.


Index


Readers’ Comments — We'd Like to Hear from You

IBM TS7650G ProtecTIER Deduplication GatewayiRPQ 8B3668 Server Replacement3958 DD5 (or DD4) with 3958DD6,PN 00VJ411, EC M13702for ProtecTIER 3.4

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send your comments via email to: [email protected]

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouIBM®

Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBMCorporationInformation Development, Dept. GZWA9000 S Rita RoadTucson, AZUSA 85744-0001

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

IBM®

Printed in USA

with ibm corp. · dd5 (or dd4) server or servers at the customer site, and r eplacing them with dd6...

Documents