IBM TS7650G ProtecTIER Deduplication Gateway for ProtecTIER 3.4. irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6, PN 00VJ409, EC M13702 IBM

Transcription

1 IBM TS7650G ProtecTIER Deduplication Gateway for ProtecTIER 3.4 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6, PN 00VJ409, EC M13702 IBM

2 Edition notice This edition is the procedure to replace a 3958 DD3 server with a 3958 DD6 server, and applies only to ProtecTIER servers running ProtecTIER version 3.4 or higher. Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Figures v Tables vii Homologation Statement ix Chapter 1. Before installation Bill of materials to be installed Prerequisites to this procedure Installation time Special tools/materials required Chapter 2. ProtecTIER model upgrade DD3 to 3958 DD6 replacement... 5 Preparation to replace DD3 node B Verify mpath devices on the DD3 node B being replaced Stop the services on the DD3 node B being replaced and power off node B Preparation to replace DD3 node A Verify mpath devices on the DD3 node A being replaced Stop the services on the DD3 node A being replaced and power off node A Clustered Ethernet cabling removal Clustered and Standalone cable connections for the DD6 replacement server Remove and replace node A Remove the existing DD3 node A from the frame 15 Remove and replace node B Remove the existing DD3 node B from the frame 16 Install the DD6 chassis in the frame Power on and configure DD6 node A Verify mpath devices and Emulex ports on the DD6 node A Recover the configuration of DD6 node A Verify that services are UP on DD6 node A Configure DD6 node B Verify mpath devices and Emulex ports on the DD6 node B Recover the configuration of DD6 node B Verify that services are UP on DD6 nodes Configure the machine serial number for replaced servers Configure the machine serial number for replaced servers for node A Notices Index Copyright IBM Corp iii

4 iv irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

5 Figures 1. Ethernet switch and Ethernet connections for the DD3 server to be removed TSSC and customer Ethernet connections for the DD3 server to be removed VTL cluster configuration FSI configuration Frontend and backend connections Clustering, replication and customer network connections for cluster configurations Replication and customer network connections for standalone configurations Copyright IBM Corp v

6 vi irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

7 Tables 1. Roles and responsibilities Installation instructions and hardware Supported scenarios for the 3958 DD3 to 3958 DD6 replacement Copyright IBM Corp vii

8 viii irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

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

10 x irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

11 Chapter 1. Before installation Machines affected This document provides instructions for replacing a 3958 DD3 server with a 3958 DD6 server, and should not be in any way associated with procedures for 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 Verify that the server being replaced and the replacement server are running at least ProtecTIER V3.3.7 and the replacement server is running ProtecTIER V3.4. If it is necessary to install a later ProtecTIER version, use the procedure Chapter 2, ProtecTIER model upgrade DD3 to 3958 DD6 replacement, on page 5. Verify mpath devices on the DD3 server being replaced Stop the services on the DD3 server being replaced. Power off the node(s). In clustered configurations, there will be 2 nodes. Disconnect backend and front end cables from the DD3 server Disconnect the Replication and Customer network cables from the DD3 server Remove the connections to the TSSC Network switch Remove the connections to the Ethernet switch 1 and Ethernet switch 2 (in case of cluster configuration) Remove the connections to the WTI Network Power Switch (in case of cluster configuration) Remove the existing DD3 server from the frame Personnel performing the task IBM trained ProtecTIER specialist working together with the customer IBM lab-based services personnel IBM lab-based services personnel, or a trained ProtecTIER specialist working together with the customer IBM support services representative (SSR), or a trained ProtecTIER specialist working together with the customer IBM support services representative (SSR) IBM support services representative (SSR) IBM support services representative (SSR) IBM support services representative (SSR) IBM support services representative (SSR) IBM support services representative (SSR) Copyright IBM Corp

12 Table 1. Roles and responsibilities (continued) Task Install the DD6 server into the frame Verify mpath devices and Emulex ports on the newly-installed DD6 server Restore the existing PT configuration Register the new DD6 server. Personnel performing the task IBM support services representative (SSR) IBM lab-based services personnel IBM lab-based services personnel, or a trained ProtecTIER specialist working together with the customer IBM support services representative (SSR) This process is completed during the sales transactions. The serial numbers of the DD6 servers are entered into the RETAIN database. When a Software Call Home request is transmitted from the customer site, a PMR is created. The IBM support services representative (SSR) must enter the customer number into the system during RAS configuration, so that the customer number is transmitted with the Software Call Home request. Bill of materials to be installed Table 2. Installation instructions and hardware Bill of materials Quantity Comments DD6 Canisters 2 If the servers to be replaced are in a clustered configuration, two DD6 replacement canisters are required. If the servers to be replaced are in a stand-alone configuration, only one replacement canister is required. These canisters will be contained within an enclosure for either configuration, standalone or cluster. DD6 Rails 1 set(s) One set of DD6 rails are required for either stand-alone or clustered configurations. One set of DD6 rails is required for each enclosure. Prerequisites to this procedure The topics in this section provides requirements that must be met before replacing an existing 3958 DD3 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 a coordinator to plan for this RPQ and meet all prerequisites before IBM personnel come onsite. TSSC The TSSC console will no longer be required whenprotectier is installed in the new DD6 servers, it is the client s decision to reuse the console with other equipment, however support from ProtecTIER will not be provided for this. 2 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

13 Installation time Call Home function After the removal of the DD3 server or servers and replacement with the DD6 server or servers, call home function should be already configured. Run a test call home to verify it, if the test call home procedure fails 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) is available for this procedure. To connect a monitor to the DD6 server a micro HDMI to VGA converter is required. Note: The micro HDMI to VGA converter is not included and must be provided by the customer. Latest version of ProtecTIER code on DD6 only DD3 server is not supported in ProtecTIER V3.4. The DD3 server removal and DD6 server installation procedure does not require that both the replaced server and the replacement server are running ProtecTIER V3.4. For DD3 server it is necessary to upgrade at least to ProtecTIER V3.3.7, use the procedure in Chapter 2, ProtecTIER model upgrade DD3 to 3958 DD6 replacement, on page 5. This task is performed by 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 DD3 server being replaced will be removed from production and will not be supported. The entitlement for warranty and service for the replacement server is based on the unique serial number of the replacement server. If the system is owned by the Customer: Customers are not required to send the customer-owned servers back to IBM. However, IBM support liability for a replaced server terminates when the replacement server is powered up and functional. Although IBM cannot control a customer decision to utilize the server in other areas, or sell the server to a third party, IBM does not support such a decision, nor will IBM provide support for the server or any hardware connected thereto, or any software installed thereon, unless the customer establishes a new sales/support agreement for the replaced server. If the customer needs support for the replaced server, the customer should contact IBM sales representative to establish a new sales/support agreement. Note: The DD3 and DD6 servers exceed the weight requirements for 1 person. A minimum of 2 are required for this procedure. Removing the existing DD3 server or servers at the customer site, and replacing them with DD6 servers requires a full maintenance window. Allow extra time if the configuration at the customer site is clustered. Chapter 1. Before installation 3

14 Service action Nonconcurrent (FC 2732 or 2722) Estimated installation hours Estimated machine hours Estimated system hours 4.0 per node less than Number of SSRs Special tools/materials required v Phillips screwdriver #2 v Micro HDMI to VGA converter v External DVD reader v ProtecTIER V3.4 DVD for VTL only For VTL stand alone: IBM System Storage ProtecTIER Enterprise Edition Standalone V3.4 (EC M PN17R7264) For VTL cluster IBM System Storage ProtecTIER Enterprise Edition Cluster V3.4 (EC M 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 M PN00VJ404) For VTL cluster IBM System Storage ProtecTIER Enterprise Edition Cluster V3.4.1 (EC M PN00VJ405) For FSI IBM System Storage ProtecTIER Enterprise Edition Cluster V3.4.1 (EC M PN:00VJ405) 4 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

15 Chapter 2. ProtecTIER model upgrade DD3 to 3958 DD6 replacement Supported scenarios Table 3. Supported scenarios for the 3958 DD3 to 3958 DD6 replacement Conversion model (from - to) Application Single or cluster Hardware DD3 to DD6 VTL Single TS7650G DD3 to DD6 VTL Cluster TS7650G DD3 to DD6 FSI Single TS7650G Important considerations Storage backend zoning update It is very important to add the new World Wide Names (WWN) of the new Host Bus Adapters (HBA) of the new DD6 server to your Storage Area Network (SAN). The new WWNs must be attached to exactly the same logical units than the previous ProtecTIER servers, this way the existing repository is visible for the new DD6 server. This operation must be performed prior executing the server replace procedure, either by the client or by asking Lab Services to perform it. Cables and labels The labels on the DD3 server cables will not exactly match the labels provided on the DD6 server. If you are uncertain about cable placement on the DD6 server, please contact your next level of support. If the transition is unsuccessful If the transition from DD3 to DD6 is not successful, do not attempt to return to the previous configuration (the DD3 configuration) without assistance from IBM Support. The configuration changes initiated by the conversion alter the Ethernet assignments and they must be reconfigured manually. Do NOT plug the cables back into the DD3 server. Latest version of ProtecTIER code only on DD6 server The DD3 server is not supported in ProtecTIER V3.4. The DD3 server removal and DD6 server installation procedure does not require that both, the replaced server and the replacement server, are running ProtecTIER V3.4. Only the DD6 server must be running ProtecTIER 3.4, the DD3 server must be running at least ProtecTIER V If it is necessary to upgrade the DD3 server to V3.3.7, use the appropriate procedure. This task is performed by a trained ProtecTIER specialist (FTSS). Check the TS7600 Upgrade matrix for more information upgrading ProtecTIER. ( STLPPL_ent/com.ibm.storage.ts7600_upgrade.doc/ ts7600_upgradematrix.html) Copyright IBM Corp

16 If your system is running ProtecTIER version or Follow these steps 1. Upgrade to ProtecTIER V using the procedure in Upgrading from ProtecTIER version to Red Hat Linux version 5.6 and ProtecTIER 3.3.x in the following link STLPPL_ent/com.ibm.storage.ts7650_3-3.service.doc/ ts6750rug_upgrade_rh_pt_31.html Remember: It is not required for the DD3 server to be upgraded to ProtecTIER V3.4. (DD3 servers are not supported on ProtecTIER V3.4.) Preparation to replace DD3 node B Use the following procedures to prepare for replacing 3958 DD3 node B. Verify mpath devices on the DD3 node B being replaced 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 DD3 node A on page 8. About this task This task is performed by IBM lab-based services personnel. Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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 DD3 node B. 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 number must be displayed when you verify the mpath devices on the DD6. What to do next Proceed to Stop the services on the DD3 node B being replaced and power off node B. Stop the services on the DD3 node B being replaced and 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 DD3 node A on page 8. 6 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

17 About this task This task is performed by IBM lab-based services personnel, or a trained ProtecTIER specialist working together with the customer. Stopping these services avoids meta data corruption on the management file system of the repository (if the recognition procedure encounters unexpected issues). Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 2. From the ProtecTIER Service menu, select Manage ProtecTIER services (...). The system displays the Manage ProtecTIER services (...) menu: ProtecTIER Service Menu running on rasap 1 Manage ProtecTIER Services (...) 1) Display services status 2) Start all services 3) Stop all services 4) Stop ProtecTIER services only (including GFS) 5) Stop VTFD service only 6) Poweroff This Node 7) Reboot This Node B) Back E) Exit >>> Your choice? 3. From the Manage ProtecTIER Services (...) menu, select Stop all services. When the 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, then select Power off This Node. When the power off processes complete, the Power LED on the server's front panel blinks steadily. This indicates that the server is in standby node. Chapter DD3 to 3958 DD6 replacement 7

18 What to do next Proceed to Preparation to replace DD3 node A Preparation to replace DD3 node A Use the following procedures to prepare for replacing 3958 DD3 node A. Verify mpath devices on the DD3 node A being replaced Perform the following steps to verify mpath devices. Before you begin If you are working with a cluster configuration, the section Preparation to replace DD3 node B on page 6 must be completed before you continue. If you are working in a stand-alone configuration, proceed with the steps in this procedure. About this task This task is performed by IBM lab-based services personnel. Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 node A. 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 DD3 node A. 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 number must be displayed when you verify the mpath devices on the DD6. What to do next Proceed to Stop the services on the DD3 node A being replaced and power off node A. Stop the services on the DD3 node A being replaced and 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 replace DD3 node B on page 6 must be completed before you continue. If you are working in a stand-alone configuration, proceed with the steps in this procedure. About this task This task is performed by IBM lab-based services personnel, or a trained ProtecTIER specialist working together with the customer. Stopping these services avoids meta data corruption on the management file system of the repository (if the recognition procedure encounters unexpected issues). 8 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

19 Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 2. From the ProtecTIER Service menu, select Manage ProtecTIER services (...). The system displays the Manage ProtecTIER services (...) menu: ProtecTIER Service Menu running on rasap 1 Manage ProtecTIER Services (...) 1) Display services status 2) Start all services 3) Stop all services 4) Stop ProtecTIER services only (including GFS) 5) Stop VTFD service only 6) Poweroff This Node 7) Reboot This Node B) Back E) Exit >>> Your choice? 3. From the Manage ProtecTIER Services (...) menu, select Stop all services. When the 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, then select Power off This Node. When the power off processes complete, the Power LED on the server's front panel blinks steadily. This indicates that the server is in standby node. Clustered Ethernet cabling removal If a DD6 single node is replacing a DD3 single node, refer to the "Server A" portions of the figures. If this is a clustered configuration, verify that the existing cabling matches the appropriate diagram. Chapter DD3 to 3958 DD6 replacement 9

20 Ethernet switch and Ethernet connections for the DD3 server to be removed Figure 1. Ethernet switch and Ethernet connections for the DD3 server to be removed Callout R S U E1 E2 A V P Description Serial Connector SAS external connector USB Ethernet Ethernet RSA connection Video (VGA) connector Power 10 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

21 TSSC and customer Ethernet connections for the DD3 server to be removed Figure 2. TSSC and customer Ethernet connections for the DD3 server to be removed Important: Verify the cables are properly tagged before transitioning to the new node. Due to Ethernet reassigning, the current tags are no longer valid after the replacement, so current tagging is important for recognition purposes. Following the node replacement, mark the cables with their new tag positions in their new locations. This is very important for the Customer Network and Customer Replication cables. Note: If you are working with a stand-alone configuration, refer to the Server A portion of Figure 2. Callout R S U E1 E2 A Description Serial connector SAS external connector USB Ethernet Ethernet RSA connection Backend and frontend cable disconnections for the DD3 server If a DD6 single node is replacing a DD3 VTL single node, refer to the "Server A" portions of the figures. In case of replacing a DD3 FSI node refer to figure 4. Important: Verify the cables are properly tagged before transitioning to the new node. Current tagging is important for recognition purposes. Following the node replacement, 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 fiber connections. Chapter DD3 to 3958 DD6 replacement 11

22 Disconnect the fiber channel cables from the backend storage and from the host s frontend (in case of VTL configurations they will be fiber cables in case of FSI they will be Ethernet cables). These cables will be reconnected later in the replaced DD6 server. Figure 3. VTL cluster configuration Figure 4. FSI configuration Clustered and Standalone cable connections for the DD6 replacement server Backend and frontend connections for the DD6 replacement server With the DD6 server in place in the rack, proceed to connect the fiber channel cables used for the backend storage. For standalone configurations refer to the Server A portion of the figures 12 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

23 Figure 5. Frontend and backend connections Important: In case of FSI 10GB installations there will be only 2 available ports for frontend connections (hosts). Clustered Ethernet, replication network and customer cabling for the DD6 replacement server With the DD6 server in place in the rack, proceed to connect the cluster cables in the interface E0. Connect the customer network in the interface E3. In case of cluster configurations, the replication network will be connected in the interfaces E1 of each canister. In case of standalone configurations, the replication interfaces will be E0 and E1. Figure 6. Clustering, replication and customer network connections for cluster configurations Important: Verify the cables are properly tagged before transitioning to the new node. Due to Ethernet reassigning, the current tags are no longer valid after the replacement, so current tagging is important for recognition purposes. Following the node replacement, mark the cables with their new tag positions in their new locations. This is very important for the Customer Network and Customer Replication cables. Note: If you are working with a stand-alone configuration, refer to the Server A portion of Figure 2. Callout From On device To 1 Port E0, onboard Server A Port E0, on server B On device location Server A Chapter DD3 to 3958 DD6 replacement 13

24 Callout From On device To 2 Port E1, onboard Server A Replication network 3 Port E1, onboard Server B Replication network 4 Port E2, onboard Server A Customer network 5 Port E2, onboard Server B Customer network On device location Server A Server B Server A Server B Standalone replication network and customer cabling for the DD6 replaced server Figure 7. Replication and customer network connections for standalone configurations Callout From On device To 1 Port E0, onboard Server A Replication network 2 Port E1, onboard Server A Replication network 3 Port E2, onboard Server A Customer network On device location Server A Server A Server A Remove and replace node A Perform the following steps to remove and replace node A. Before you begin Perform the following procedures before you begin removing and replacing node A. 14 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

25 1. (For clustered configurations), Preparation to replace DD3 node B on page Preparation to replace DD3 node A on page 8 Important: When replacing a node in a cluster, it is necessary to power off the other nodes in the cluster before the replacement. However, the replacement steps for the server (using the menu actions) require the storage controllers to be powered on while the replacement sequence is initiated. Remove the existing DD3 node A from the frame Perform the following steps to remove the existing node A from the frame. Before you begin CAUTION: Make sure node(s) being replaced are powered off. About this task This task is performed by IBM support services representative (SSR). Procedure 1. Verify that the DD3 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 server from the rails. 3. Mark the locations of the rails on the frame. The rails on the DD6 server will mount to the frame using the same holes that the rails of the DD3 server used. Note: The rails for the DD3 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 DD3 rail system. 5. Remove the DD3 rails from the frame. What to do next Remove and replace node B v If this is a standalone configuration, proceed to Install the DD6 chassis in the frame on page 16. v If this is a cluster configuration, proceed to Remove the existing DD3 node B from the frame on page 16 Perform 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 DD6 chassis in the frame on page 16. If you are working with a clustered configuration perform the steps in the procedure Remove and replace node A on page 14 before you begin removing and replacing node B. Chapter DD3 to 3958 DD6 replacement 15

26 About this task Important: When replacing a node in a cluster, it is necessary to power off the other nodes in the cluster before the replacement. However, the replacement steps for the server (using the menu actions) require the storage controllers to be powered on while the replacement sequence is initiated. Remove the existing DD3 node B from the frame Perform the following steps to remove the existing node B from the frame. Before you begin CAUTION: Make sure the node(s) being replaced are powered off. Before you remove node B from the frame, be sure you have removed node A by following the steps to Remove the existing DD3 node B from the frame. About this task This task is performed by IBM support services representative (SSR). Procedure 1. Verify that the DD3 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 server from the rails. 4. Remove the rails and cable management trays that were attached to the DD3 rail system. 5. Remove the DD3 rails from the frame. What to do next v Proceed to Install the DD6 chassis in the frame. Install the DD6 chassis in the frame Perform 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 This task is performed by IBM support services representative (SSR). The DD6 servers are a 2U enclosure. Within this enclosure it can be 1 or 2 canisters, therefore it is not necessary to insert separately node A and node B in the frame, as already mentioned, both are contained within the 2U enclosure. 16 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

27 Procedure 1. 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 DD3 servers to the new DD6 server. Refer to the tables and diagrams in Clustered and Standalone cable connections for the DD6 replacement server on page 12 Attention: It is very important the new WWNs of the DD6 server are correctly added to the SAN network so they can be attachedto the same LUNs assigned previously to the replaced DD3 server. Power on and configure DD6 node A The topics in this section provide instructions to power on and configure the DD6 node A. Verify mpath devices and Emulex ports on the DD6 node A Perform the following steps to verify mpath devices and Emulex ports on the DD6 node A Before you begin Important: v Verify the SAN zoning for the storage with ProtecTIER back-end ports, and update if necessary. v Verify host mappings for storage LUNs, and update if necessary. About this task This task is performed by IBM lab-based services personnel. Procedure 1. 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 password prompt, type: ptadmin and press <Enter>. Important: To attach a monitor to the DD6 server a micro HDMI to VGA converter is necessary, this should be provided by the customer. 3. Verify how many mpath devices are on the newly-installed DD6 server by typing 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 DD6 as it displayed for the DD3. 4. Verify that the system recognizes all four Emulex ports by typing the following command at the command prompt: # lspci grep Emulex<Enter> The system displays the four Emulex ports (similar to the following information): Chapter DD3 to 3958 DD6 replacement 17

28 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, as follows # /usr/sbin/linlpcfg/linlpcfglistwwn grep -c WWNN <Enter> The system displays the World Wide Node Names (WWNNs) of the Emulex ports. If the system returns less than four WWNNs, reboot the system prior to replacement to recover all of the ports. Important: In VTL configurations the frontend and backend cards are both Emulex, 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 A Perform 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 storage controllers to be powered on while the replacement sequence is initiated. This task is performed by IBM lab-based services personnel or a trained ProtecTIER specialist working together with the customer. Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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: 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 2. From the ProtecTIER Service menu, select ProtecTIER Configuration (...). The ProtecTIER Configuration (...) menu is displayed: The ProtecTIER Configuration (...) menu is displayed: 18 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

29 ProtecTIER Service Menu running on rasap 1 ProtecTIER Configuration (...) 1) Configure ProtecTIER node 2) Recover Configuration for a replaced server 3) Configure machine serial number for a replaced server 4) Configure RAS 5) Update Time, Date, Timezone & Timeserver(s) 6) Scan storage interconnections 7) File systems Management (...) 8) Configure replication (...) 9) IP Network configuration (...) 10) Update Firmware (...) 11) Update the system s name 12) Validate configuration 13) Single Node - code upgrade 14) OS images Management (...) 15) Replace SAS drive B) Back E) Exit >>> Your choice? 3. Select Recover Configuration for a replaced server. Note: During a node replacement, when utilizing the menu operations for the conversion, the storage must remain up and operational. The node's configuration is resident inside the storage repository, and must be retrieved when the replacement option is requested by the menu operation. The system will prompt during the replacement, for verification of the model being replaced. This prompt will display the configuration that is stored for the model being replaced. If this is a cluster, and the companion node is not powered on, the system will offer the configuration options for both nodes, and you 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: Model: Application: replace TS7650G 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. Chapter DD3 to 3958 DD6 replacement 19

30 Stopping services, please wait Stopping 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 : 1 hostname : kokomo ip : Option 2 ************************************************** nodeid : 2 hostname : auburn ip : 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 interface DO NOT CHANGE THE DEFAULT IP ADDRESS. This will cause to lose the connection to the server. The system displays output similar to the following: Please enter the following balues for bmc: Application Interface bmc, IP Address [ ]: Application Interface bmc, Netmask [ ]: Application Interface bmc, Default Gateway [ ]: Restoring Frond End HBA WWN [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] WARNING: could not detect an active link for eth5 Restarting 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 seconds Testing 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 fencing validation ended replace ended successfully with warnings End Processing Procedure Successfully Press <Enter> to continue 20 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

31 What to do next 1. 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 A Perform 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 trained ProtecTIER specialist working together with the customer. Keep the DD6 node A in a powered on state. Use the following steps to make sure that all the services are UP on node A. Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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: 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 2. 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 status 2) Start all services 3) Stop all services 4) Stop ProtecTIER services only (including GFS) 5) Stop VTFD service only 6) Poweroff This Node 7) Reboot This Node B) Back E) Exit >>> Your choice? 3. From the ProtecTIER Services menu, select Display services status. The ProtecTIER Configuration (...) menu is displayed: 4. Verify that all services are UP. Chapter DD3 to 3958 DD6 replacement 21

32 If the services are not UP: Select Stop all services. Then restart the services, using the Start all services option. If they are still down, a reboot might be required to recover the services. If they remain down following the reboot (it might take several minutes following the reboot for all the services to restart), contact your next level of support. Restore and Backup There is a possibility that the working ports can switch status. (For instance, the UP ports might switch status to DOWN, and vice versa.) This indicates that the backup application is not accessing the frontend ports. If this occurs, restart the backup application and rescan the for the working ports. Rescanning for the ports will enable you to access the data. 5. When the services are UP on node A, verify the health status using 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 DD3 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: 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? b. From the ProtecTIER Service menu, select Health Monitoring (...). The system displays the Health Monitoring menu: ProtecTIER Service Menu running on rassmx Health Monitoring (...) 1) Display health summary for this node 2) Display detailed health for this node 3) Run a full check on this node 4) List open problems 5) Service Mode B) Back E) Exit >>> Your choice? c. Select Display health summary for this node. If the health status shows OK, proceed as instructed. If the health status is Degraded or Failed, select Display detailed health for this node, identify the failing component (or components), make the required corrections and recheck the health status. If you are unable to correct the failing condition, contact your next level of support. 22 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

33 What to do next Configure DD6 node B 1. If you are working with a stand-alone configuration, proceed to Configure the machine serial number for replaced servers on page If you are working with a cluster configuration, proceed to Configure DD6 node B The topics in this section provide instructions to power on and configure the DD6 node B. Verify mpath devices and Emulex ports on the DD6 node B Perform the following steps to verify mpath devices and Emulex ports on the DD6 node B Before you begin Important: v Verify the SAN zoning for the storage with ProtecTIER back-end ports, and update if necessary. v Verify host mappings for storage LUNs, and update if necessary. About this task This task is performed by IBM lab-based services personnel. Procedure 1. 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 is already turned on and in the login prompt. 2. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard 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 VGA converter is necessary, this should be provided by the customer. 3. Verify how many mpath devices are on the newly-installed DD6 server by typing 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 DD6 as it displayed for the DD3. 4. Verify that the system recognizes all four Emulex ports by typing the following command at the command prompt: # lspci grep Emulex<Enter> The system displays the four Emulex ports (similar to the following information): 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, as follows Chapter DD3 to 3958 DD6 replacement 23

34 # /usr/sbin/linlpcfg/linlpcfglistwwn grep -c WWNN <Enter> The system displays the World Wide Node Names (WWNNs) of the Emulex ports. If the system returns less than four WWNNs, reboot the system prior to replacement to recover all of the ports. Important: In VTL configurations the frontend and backend cards are both Emulex, 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 B Perform 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 storage controllers to be powered on while the replacement sequence is initiated. This task is performed by IBM lab-based services personnel or a trained ProtecTIER specialist working together with the customer. Procedure 1. If you have not already done so, log in to the ProtecTIER server by attaching a keyboard and monitor to the DD3 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 2. From the ProtecTIER Service menu, select ProtecTIER Configuration (...). The ProtecTIER Configuration (...) menu is displayed: The ProtecTIER Configuration (...) menu is displayed: 24 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

35 ProtecTIER Service Menu running on rasap 1 ProtecTIER Configuration (...) 1) Configure ProtecTIER node 2) Recover Configuration for a replaced server 3) Configure machine serial number for a replaced server 4) Configure RAS 5) Update Time, Date, Timezone & Timeserver(s) 6) Scan storage interconnections 7) File systems Management (...) 8) Configure replication (...) 9) IP Network configuration (...) 10) Update Firmware (...) 11) Update the system s name 12) Validate configuration 13) Single Node - code upgrade 14) OS images Management (...) 15) Replace SAS drive B) Back E) Exit >>> Your choice? 3. Select Recover Configuration for a replaced server. Note: During a node replacement, when utilizing the menu operations for the conversion, the storage must remain up and operational. The node's configuration is resident inside the storage repository, and must be retrieved when the replacement option is requested by the menu operation. The system will prompt during the replacement, for verification of the model being replaced. This prompt will display the configuration that is stored for the model being replaced. If this is a cluster, and the companion node is not powered on, the system will offer the configuration options for both nodes, and you 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: Model: Application: replace TS7650G 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. Chapter DD3 to 3958 DD6 replacement 25

36 Stopping services, please wait Stopping 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 : 1 hostname : auburn ip : Since there is only one pending node to replace, only one available option will be displayed, confirm it corresponds to node B. Type 1 and press <Enter> to continue. Important: If the node replace procedure is being performed via BMC interface DO NOT CHANGE THE DEFAULT IP ADDRESS. This will cause to lose the connection to the server. The system displays output similar to the following: Please enter the following balues for bmc: Application Interface bmc, IP Address [ ]: Application Interface bmc, Default Gateway [ ]: Application Interface bmc, Netmask [ ]: Restoring Frond End HBA WWN [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] WARNING: could not detect an active link for eth5 Restarting 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 seconds Testing 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 fencing validation ended replace 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 irpq 8B3667 Server Replacement 3958 DD3 with 3958 DD6

37 Verify that services are UP on DD6 nodes Perform 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 trained ProtecTIER specialist working together with the customer. Procedure 1. 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 by attaching a keyboard and monitor to the DD3 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 report 7) Generate a system view 8) Update ProtecTIER code 9) ProtecTIER Analysis (...) E) Exit >>> Your choice? 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 status 2) Start all services 3) Stop all services 4) Stop ProtecTIER services only (including GFS) 5) Stop VTFD service only 6) Poweroff This Node 7) Reboot This Node B) Back E) Exit >>> Your choice? c. From the ProtecTIER Services menu, select Display services status. The ProtecTIER 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 all services option. If they are still down, a reboot might be required to recover the services. If they remain down following the reboot (it might take several minutes following the reboot for all the services to restart), contact your next level of support. Chapter DD3 to 3958 DD6 replacement 27