Skip to main content
E-Series Systems

Add a second canister in E4000

Contributors netapp-ivanad
PDFs

You can add a second controller canister in the E4000 array.

About this task

Add a second controller canister to the simplex version of a E4012 controller shelf. This procedure is also referred to as a simplex-to-duplex conversion, which is an online procedure. You can access data on the storage array while you perform this procedure.

Before you begin

Make sure you have the following:

  • A new controller canister with the same part number as the currently installed controller canister. (See step 1 to verify the part number.)

  • An ESD wristband, or take other antistatic precautions.

  • A #1 Phillips screwdriver.

  • Labels to identify the new cables. For information about compatible hardware, refer to the NetApp Interoperability Matrix or the NetApp Hardware Universe.

  • All cables, transceivers, switches, and host bus adapters (HBAs) needed to connect the new controller ports.

  • A management station with a browser that can access SANtricity System Manager for the controller. (To open the System Manager interface, point the browser to the controller’s domain name or IP address.)

Step 1: Verify the new controller’s part number

Confirm that the new controller has the same part number as the currently installed controller.

Steps

  1. Unpack the new controller canister, and set it on a flat, static-free surface. Save all packing materials to use when shipping the failed controller canister.

  2. Locate the MAC address and FRU part number labels on the back of the controller canister.

  3. From SANtricity System Manager, locate the replacement part number for the installed controller canister.

    1. Select Hardware.

    2. Locate the controller shelf, which is marked with the controller icon.

    3. Click the controller icon Gif of controller icon.

    4. Select the controller, and click Next.

    5. On the Base tab, make a note of the Replacement Part Number for the controller.

  4. Confirm that the replacement part number for the installed controller is the same as the FRU part number for the new controller.

    Caution Possible loss of data access — If the two part numbers are not the same, do not attempt this procedure. The presence of mismatched controllers will cause the new controller to lock down when you bring it online.

  5. Back up the storage array’s configuration database using SANtricity System Manager.

    If a problem occurs when you remove a controller, you can use the saved file to restore your configuration. The system will save the current state of the RAID configuration database, which includes all data for volume groups and disk pools on the controller. Do the following from System Manager:

    1. Select Support › Support Center › Diagnostics.

    2. Select Collect Configuration Data.

    3. Click Collect.

      The file is saved in the Downloads folder for your browser with the name configurationData- <arrayName>-<dateTime>.7z.

Step 2: Install host interface card

If the currently installed controller includes a host interface card (HIC), you must install the same model of HIC in the second controller canister.

Steps

  1. Unpack the new HIC, and confirm it is the identical to the existing HIC.

    Caution Possible loss of data access: The HICs installed in the two controller canisters must be identical. If the replacement HIC is not identical to the HIC you are replacing, do not attempt this procedure. The presence of mismatched HICs will cause the new controller to lock down when it comes online.

  2. Remove the HIC card bezel by sliding it straight out from the controller module.

  3. Take the HIC card and align it with the socket on the motherboard.

  4. Gently push down on the card to seat it in the socket.

  5. Tighten the three thumbscrews.

    Caution Be careful not to over tighten the screws, as that may result in damage to the HIC card.

  6. Reinstall the HIC card bezel.

Step 3: Collect support data

Collect support data before and after replacing a component to ensure you can send a full set of logs to technical support in case the replacement does not resolve the problem.

Steps

  1. From the Home page of SANtricity System Manager, ensure that the storage array has Optimal status.

    If the status is not Optimal, use the Recovery Guru or contact technical support to resolve the problem. Do not continue with this procedure.

  2. Collect support data for your storage array using SANtricity System Manager.

    1. Select Support › Support Center › Diagnostics.

    2. Select Collect Support Data.

    3. Click Collect.

      The file is saved in the Downloads folder for your browser with the name, support-data.7z.

  3. Ensure that no I/O operations are occurring between the storage array and all connected hosts. For example, you can perform these steps:

    • Stop all processes that involve the LUNs mapped from the storage to the hosts.

    • Ensure that no applications are writing data to any LUNs mapped from the storage to the hosts.

    • Unmount all file systems associated with volumes on the array.

      Note The exact steps to stop host I/O operations depend on the host operating system and the configuration, which are beyond the scope of these instructions. If you are not sure how to stop host I/O operations in your environment, consider shutting down the host.
      Caution Possible data loss — If you continue this procedure while I/O operations are occurring, you might lose data.

Step 4: Change configuration to duplex

Before adding a second controller to the controller shelf, you must change the configuration to duplex by installing a new NVSRAM file and using the command line interface to set the storage array to duplex. The duplex version of the NVSRAM file is included with the download file for SANtricity OS Software (controller firmware).

Steps

  1. Download the latest NVSRAM file from the NetApp Support site to your management client.

    1. From SANtricity System Manager, select Support › Upgrade Center. In the area labeled “SANtricity OS Software upgrade,” click NetApp SANtricity OS Downloads.

    2. From the NetApp Support site, select E-Series SANtricity OS Controller software.

    3. Follow the online instructions to select the version of NVSRAM you want to install, and then complete the file download. Be sure to select the duplex version of the NVSRAM (the file has “D” near the end of its name).

      The file name will be similar to: N290X-830834-D01.dlp

  2. Upgrade the files using SANtricity System Manager.

    Caution Risk of data loss or risk of damage to the storage array — Do not make changes to the storage array while the upgrade is occurring. Maintain power to the storage array.

    You can cancel the operation during the pre-upgrade health check, but not during transferring or activating.

    • From SANtricity System Manager:

      1. Under SANtricity OS Software upgrade, click Begin Upgrade.

      2. Next to Select Controller NVSRAM file, click Browse, and then select the NVSRAM file you downloaded.

      3. Click Start, and then confirm that you want to perform the operation.

        The upgrade begins and the following occurs:

        • The pre-upgrade health check begins. If the pre-upgrade health check fails, use the Recovery Guru or contact technical support to resolve the problem.

        • The controller files are transferred and activated. The time required depends on your storage array configuration.

        • The controller reboots automatically to apply the new settings.

    • Alternatively, you can use the following CLI command to perform the upgrade:

      download storageArray NVSRAM file="filename" healthCheckMelOverride=FALSE;

      In this command, filename is the file path and the file name for duplex version of the Controller NVSRAM file (the file with “D” in its name). Enclose the file path and the file name in double quotation marks (" "). For example:

      file="C:\downloads\N290X-830834-D01.dlp"

  3. (Optional) To see a list of what was upgraded, click Save Log.

    The file is saved in the Downloads folder for your browser with the name, latest-upgrade-log-timestamp.txt.

    • After upgrading controller NVSRAM, verify the following in SANtricity System Manager:

      • Go to the Hardware page, and verify that all components appear.

      • Go to the Software and Firmware Inventory dialog box (go to Support › Upgrade Center, and then click the link for Software and Firmware Inventory). Verify the new software and firmware versions.

    • When you upgrade controller NVSRAM, any custom settings that you have applied to the existing NVSRAM are lost during the process of activation. You must apply the custom settings to the NVSRAM again after the process of activation is complete.

  4. Change the storage array setting to duplex using CLI commands. To use CLI, you can open a command prompt if you downloaded the CLI package.

    • From a command prompt:

      1. Use the following command to switch the array from simplex to duplex:

        set storageArray redundancyMode=duplex;

      2. Use the following command to reset the controller.

        reset controller [a];

After the controller reboots, an “alternate controller missing” error message is displayed. This message indicates that controller A has been successfully converted to duplex mode. This message persists until you install the second controller and connect the host cables.

Step 5: Remove the controller blank

Remove the controller blank before you install the second controller. A controller blank is installed in controller shelves that have only one controller.

Steps

  1. Squeeze the latch on the cam handle for the controller blank until it releases, and then open the cam handle to the right.

  2. Slide the blank controller canister out of the shelf and set it aside.

    When you remove the controller blank, a flap swings into place to block the empty bay.

Step 6: Install the second controller canister

Install a second controller canister to change a simplex configuration to a duplex configuration.

  1. Turn the controller canister over, so that the removable cover faces down.

  2. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.

  3. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.

    Note Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors. The controller begins to boot as soon as it is seated in the chassis.

  4. If you have not already done so, reinstall the cable management device.

  5. Bind the cables to the cable management device with the hook and loop strap.

Step 7: Complete adding a second controller

Complete the process of adding a second controller by confirming that it is working correctly, reinstall the duplex NVSRAM file, distribute volumes between the controllers, and collect support data.

Steps

  1. Place controller online.

    1. In System Manager, navigate to the Hardware page.

    2. Select Show back of controller.

    3. Select the replaced controller.

    4. Select Place online from the drop-down list.

  2. As the controller boots, check the controller LEDs.

    When communication with the other controller is reestablished:

    • The amber Attention LED remains on.

    • The Host Link LEDs might be on, blinking, or off, depending on the host interface.

  3. Update the array’s settings from simplex to duplex with the following CLI command:

    set storageArray redundancyMode=duplex;

  4. When the controller is back online, confirm that its status is Optimal and check the controller shelf's Attention LEDs.

    If the status is not Optimal or if any of the Attention LEDs are on, confirm that all cables are correctly seated, and check that the controller canister is installed correctly. If necessary, remove and reinstall the controller canister.

    Note If you cannot resolve the problem, contact technical support.

  5. Reinstall the duplex version of the NVSRAM file using SANtricity System Manager.

    This step ensures that both controllers have an identical version of this file.

    Caution Risk of data loss or risk of damage to the storage array — Do not make changes to the storage array while the upgrade is occurring. Maintain power to the storage array.
    Note You must install SANtricity OS software when you install a new NVSRAM file using SANtricity System Manager. If you already have the latest version of SANtricity OS software, you must reinstall that version.

    1. Click Hardware › Support › Upgrade Center to ensure that the latest version of SANtricity OS is installed. As needed, install the latest version.

    2. In System Manager, go to the Upgrade Center.

    3. Under SANtricity OS Software upgrade, click Begin Upgrade.

    4. Click Browse, and select the SANtricity OS software file.

    5. Click Browse, and select the Controller NVSRAM file.

    6. Click Start, and confirm that you want to perform the operation.

      The transfer of control operation begins.

  6. After the controllers reboot, optionally distribute volumes between controller A and the new controller B.

    1. Select Storage › Volumes.

    2. From the All Volumes tab, select More › Change Ownership.

    3. Type the following command in the text box: change ownership

      The Change Ownership button is enabled.

    4. For each volume you want to redistribute, select Controller B from the Preferred Owner list.

    5. Click Change Ownership.

      When the process is complete, the Change Volume Ownership dialog shows the new values for Preferred Owner and Current Owner.

  7. Collect support data for your storage array using SANtricity System Manager.

    1. Select Support › Support Center › Diagnostics.

    2. Click Collect.

      The file is saved in the Downloads folder for your browser with the name, support-data.7z.

What's next?

The process for adding a second controller is complete. You can resume normal operations.