NetApp FAS storage Head Swap Procedure

INTRODUCTION

This document contains the verification checklists that document the Head Swap Procedure.

Current Serial Numbers:
700000293005 – WALLS1
700000293017 – WALLS2

New Serial Numbers:
700002090378 – new_WALLS1
700002090366 – new_WALLS2

Current SYSID
0151745322 – WALLS1
0151745252 – WALLS2

New SYSID
2016870400 – new_WALLS1
2016870518 – new_WALLS2

Current WALLS1
slot 1 OK: X2065A: PMC PM8001; PCI-E quad-port SAS (PM8003)
slot 2 OK: X2065A: PMC PM8001; PCI-E quad-port SAS (PM8003)
slot 3 OK: X1938A: Flash Cache 512 GB
slot 4 OK: X1107A: Chelsio S320E 2x10G NIC

Current WALLS2
sysconfig: slot 1 OK: X2065A: PMC PM8001; PCI-E quad-port SAS (PM8003)
sysconfig: slot 2 OK: X2065A: PMC PM8001; PCI-E quad-port SAS (PM8003)
sysconfig: slot 3 OK: X1938A: Flash Cache 512 GB
sysconfig: slot 4 OK: X1107A: Chelsio S320E 2x10G NIC

Current WALLS1
RLM Status
IP Address:         10.43.6.88
Netmask:            255.255.255.0
Gateway:            10.43.6.1

Current WALLS2
RLM Status
IP Address:         10.43.6.120
Netmask:            255.255.255.0
Gateway:            10.43.6.1

New Licenses
Heep a Copy of the new liceses

PRE UPGRADE PROCEDURE

Make a note of the following before performing Head swap activity

  1. Old Controllers Serial Numbers
  2. Old Controllers System ID
  3. New Controllers Serial Numbers
  4. New Controllers System ID
  5. Location of expansion modules (PCI, PCIe) cards on the old controllers
  6. Label the cables attached to the Old controller Heads
  7. Make a note of the Remote LAN Mode (RLM) or Service Processor (SP) IP addresses
  8. Serial connection with the controllers to view console messages
  9. Make a note of the licenses for the new systems
  10. Make sure the Network Adapters on new controllers match the location of old controller. If not, you have to modify /etc/rc file for making new ports active.

STEPS FOR HEAD SWAP NETAPP FAS STORAGE SYSTEM

Tools required before and after head-swap

  1. Grounding strap
  2. #2 Phillips screw driver

New FAS storage system Installation and Setup

  1. Power-on the new heads with a console; check the ontap version on new controller; it should match the current version on old controller. Depending upon that we can downgrade or upgrade the ontap version.
  2. Below steps are to be followed to upgrade ontap on new controller to match old controller.
  3. Download the ontap version from url:

http://www.now.netapp.com

  1. Take the backup of system files from old controller:

/etc/hosts
/etc/rc
/etc/cifs_homedir.cfg
/etc/exports
/etc/snapmirror.conf (only on destination filers)
/etc/resolv.conf
/etc/hosts.equiv
/etc/nsswitch.conf
/etc/quotas
/etc/usermap.cfg
/etc/tapeconfig

  1. Trigger an autosupport
  2. options autosupport.doit “Pre Head Swap”

  1. Disable the autosupport
  2. options autosupport.enable off

  1. Disable the cluster
  2. cf disable

  1. Keep the ontap software in the /etc/software directory
  2. Software install <ontap_software>
    Note* don’t run download command as yet
    Make sure the Network Adapters on new controllers match the location of old controller. If not, you have to modify /etc/rc file for making new ports active

  1. If snapmirror and snapvault relations exist on this system; update them on all the volumes before system shutdown. Follow the commands as below:
  2. HALT the system
  3. halt

  1. Power-down the controller head and then all the disk shelves one at a time.
  2. Remove the power cables, network cables and SAS cables form the old controller and
  3. Remove old controller from the rack unit and replace with new controller
    Mount and screw as required on the rack

  1. Attach the SAS cables to the disk shelves, network cables to network ports, power cords to PSU’s.
  2. Power-on the disk shelves one at a time (Wait for about 1 minute till all the disks are spun properly and green led’s are stable)
  3. Power-up new controller
  4. Hit control+C when asked for an option to enter into maintenance mode
  5. Select option 5
  6. Check whether all the disks are visible by the system; hit command:
  7. disk show -v

  1. Assign the disks to this controller
  2. disk show -v (keep a copy of all the disks for future reference)
    disk reassign -s <old_sysid> -d <new_sysid> or disk assign all (change the system ID’s)
    disk show -v

  1. Clear the mailbox by enterning the following commands:
  2. mailbox destroy local
    mailbox destroy partner

  1. Halt the system
  2. Halt

  1. On the loader prompt, verify date –u with another Controller in production
  2. Boot the system in normal mode
  3. bye or boot_ontap

  1. Once the system is booted; install the ontap
  2. download

  1. Reboot the system
  2. reboot

  1. Enable the cluster
  2. cf enable

  1. Verify the HA pair is setup correctly
  2. disk show –a (storage show disk –p will also tell if MPHA is enabled)

  1. Add the license for new controller
  2. License required for a-sis; nearstore_option; sv_ontap_sec

  1. Enable and Trigger an autosupport
  2. options autosupport.enable on
    options autosupport.doit “Post Head Swap”

  1. Perform SP Setup
  2. sp setup

Testing Plan:

  1. Connect to the etc directory on new controller via NFS or CIFS and browse the contents
  2. Connect to other CIFS or NFS shares on the new controller
  3. Run the snapvault/snapmirror update once the head swap is completed
  4. Restore a test file from volume/snapshot
  5. Check with network connectivity
  6. Check the ontap version; shelf firmware version

Backout procedure:

  1. Power-down new controller and attach old controller; recable old controller back to what it was
  2. Bring down the old controller to its cfe or loader prompt
  3. Swap the PCI/PCIe cards back
  4. Reboot the system

 

Leave a Reply

Your email address will not be published. Required fields are marked *