CRU Replacements

This section provides replacement procedures for supported H2000 CRUs (customer-replaceable units).

For replaceable items that are not CRUs, see FRU Replacements.

RAID/JBOD CRUs

Note: The CRUs in this section apply to both RAID and JBOD chassis.

Required tools

There are no tools required for this procedure

Before you begin

Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

  1. Push the bezel latch to the right.
  2. Remove the left side of the bezel from the left side of the chassis.
  3. Remove the right side of the bezel from the right side of the chassis, remove the bezel from the chassis, and release the bezel latch.

  1. Push the bezel latch to the right.
  2. Insert the right side of the bezel to the right side of the chassis.
  3. Insert the left side of the bezel to the left side of the chassis and release the latch.

After you've completed this section, the Bezel CRU replacement is complete.

Required tools

  • You will need system access from a browser to see the data status in the H-Series UI.
  • You will need a laptop to detach the drive from the RAID and reattach the drive to the RAID using the command-line.

Before you begin

Note: Mixing SED and non-SED drives is NOT supported.

Note: This procedure documents replacement of drives for systems WITH NO configured drive spares. For drive replacements with configured drive spares, see: .

Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

Take ESD precautions when performing this replacement

The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

Keep static-sensitive parts in their original shipping containers until ready for installation.

Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

  • Replace a failed SSD ONLY with a drive of the same capacity. Smaller-capacity drives are not compatible, and larger drives will only use the amount of data provisioned on the other drives in the array, so you will not be able to use the additional storage capacity of larger drives.

    • SSD Capacities

    The H2000 contains 12 or 24 drives (SSDs in 24-drive systems), with different storage capacities, depending on the specific model.

There are a few ways to determine if a drive has failed:

  • A failed data drive will display a solid red LED on the drive (front of the H2000 chassis):

    • (failed drive from 12-drive chassis)

    (failed drive from 24-drive chassis)

  • In the GUI, on the Health > System page, the Current Health pie chart will appear less than 100%:

  • In the GUI, on the Health > System page, under Components, the Storage Drives and SW RAID devices will show a status of "Degraded" along with a healthy percentage:

  • In the GUI, on the Health > Storage page, the chassis with the failed drive will show a degraded RAID or JBOD Array, and the state of the drive will also display a "degraded" drive in its drive slot:

    • (12-drive RAID array example)

  1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

    2. Use the admin user name and the password for the admin account on the system.

    Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

    #ssh admin@(IP or hostname)

Connect using a console session on a client that supports ssh (for example, PuTTY on Windows systems, the Windows command line on Windows 10 or later, or the Terminal on MacOS systems).

  1. The first time you log into the CLI, you will need to enter "yes" to accept the ECDSA security key for this system connection when prompted:

    2. The authenticity of host '10.65.184.225.mycompany.com' can't be established.

    ECDSA key fingerprint is SHA256:HDCZP/C3ZrIFWONrbl/9s/KCR8g/WXrOXe0V9qbiLbM.

    Are you sure you want to continue connecting (yes/no)? yes

    You should see a prompt adding the security key to the list of known hosts.

    Warning: Permanently added '10.65.184.225' (ECDSA) to the list of known hosts.

  2. Enter the password for the admin account:

    3. admin@(IP or hostname)'s password:

    The CLI prompt for the system you are connected to displays.

    Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

    Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

    One moment, loading command sets...

    Welcome to the QBSP shell! Software version: Quantum CSP 2.4.0-Build89

    For available commands and usage, type help.

    (IP or hostname)>

  1. Detach the failed drive(s) from the RAID. Enter:

    2. (IP or hostname) detach_drive auto

    This will automatically detect any failed members of the RAID and detach them.

  1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

    2. Use the admin user name and the password for the admin account on the system.

    Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

    #ssh admin@(IP or hostname)

  1. Detach the failed drive(s) from the RAID. Enter:

    2. [admin@h2000-2 ~]$ sudo qsacli --detach_drive auto

    This will automatically detect any failed members of the RAID and detach them.

  1. Remove the bezel from the front of the H2000, if necessary:
    1. Push the bezel latch to the right.
    2. Remove the left side of the bezel from the left side of the chassis.
    3. Remove the right side of the bezel from the right side of the chassis, remove the bezel from the chassis, and release the bezel latch.

  2. Press the latch key to release the tray handle (highlight in red):

    3. (12-Drive H2000)

    (24-Drive H2000)

  3. Pull the handle out (highlight in red):

    4. (12-Drive H2000)

    (24-Drive H2000)

  4. Pull the drive tray out from the slot by the handle:

    5. (12-Drive H2000)

    (24-Drive H2000)

  5. Repeat for additional drives, if needed.
  1. Install the replacement drive tray in the chassis in the reverse order it was removed in the previous section. Repeat for additional drive trays, if needed.
  2. Replace the bezel on the front of the H2000:
    1. Push the bezel latch to the right.
    2. Insert the right side of the bezel to the right side of the chassis.
    3. Insert the left side of the bezel to the left side of the chassis and release the latch.

  1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

    2. Use the admin user name and the password for the admin account on the system.

    Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

    #ssh admin@(IP or hostname)

Connect using a console session on a client that supports ssh (for example, PuTTY on Windows systems, the Windows command line on Windows 10 or later, or the Terminal on MacOS systems).

  1. The first time you log into the CLI, you will need to enter "yes" to accept the ECDSA security key for this system connection when prompted:

    2. The authenticity of host '10.65.184.225.mycompany.com' can't be established.

    ECDSA key fingerprint is SHA256:HDCZP/C3ZrIFWONrbl/9s/KCR8g/WXrOXe0V9qbiLbM.

    Are you sure you want to continue connecting (yes/no)? yes

    You should see a prompt adding the security key to the list of known hosts.

    Warning: Permanently added '10.65.184.225' (ECDSA) to the list of known hosts.

  2. Enter the password for the admin account:

    3. admin@(IP or hostname)'s password:

    The CLI prompt for the system you are connected to displays.

    Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

    Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

    One moment, loading command sets...

    Welcome to the QBSP shell! Software version: Quantum CSP 2.4.0-Build89

    For available commands and usage, type help.

    (IP or hostname)>

  1. Attach the new drive(s) to the RAID. Enter:

    2. (IP or hostname) attach_drive auto

  2. Close the SSH terminal session:

    3. (IP or hostname) exit

  1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

    2. Use the admin user name and the password for the admin account on the system.

    Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

    #ssh admin@(IP or hostname)

  1. Attach the new drive(s) to the RAID. Enter:

    2. [admin@hseries-2 ~]$ sudo qsacli --attach_drive auto

  2. Close the SSH terminal session:

    3. [admin@hseries-2 ~]$ exit

When the attach command is run, it automatically attaches, formats, partitions, and rebuilds all data drive(s) in the RAID (which includes reconstructing the degraded volume).

On the Health > Storage screen, the drive(s) being rebuilt/resynchronized will be orange (indicating a degraded state), but now you will see detail about the status of the rebuild process, as shown in the green box here (information about the drive "recovering"and "rebuilding", along with the percent complete, the synchronizing status, and time remaining are included as a reference for the state of the drive rebuild/resynch):

Note: You may have to click the refresh button in the upper-right hand corner of this screen to show the rebuild status (depending on your screen refresh interval).

After you've completed this section, the Data Drive CRU replacement is complete.

RAID-Only CRU

Note: The CRU in this section applies only to RAID chassis.

Required tools

There are no tools required for this component replacement.

Before you begin

Caution: While the H2000 RAID and JBOD PSUs (Power Supply Units) may look similar and are the same size, they are not compatible. DO NOT use a RAID PSU in a JBOD chassis, and DO NOT use a JBOD PSU in a RAID chassis.

Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

Take ESD precautions when performing this replacement

The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

Keep static-sensitive parts in their original shipping containers until ready for installation.

Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

  1. Locate the power supply module at the back of the unit; to determine the location of the PSU (for example, PSU 1 or PSU 2), see System Overview.
  2. Remove AC power cable from the PSU.
  3. Press the latch to the left with the thumb while pulling the PSU by the handle (red arrow below):

  4. Remove the PSU from the chassis:

  1. Insert the PSU into the slot and push it firmly until the latch clicks.
  2. Attach the AC power cable to the PSU:

(image shown is from a RAID array, JBOD power cords are in the same location)

After you've completed this section, the RAID PSU CRU replacement is complete.

Before you begin:

Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

Required tools:

  • #0 Phillips screwdriver
  • #2 Phillips screwdriver
  • Laptop computer
  • Ethernet cable

Take ESD precautions when performing this replacement

The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

Keep static-sensitive parts in their original shipping containers until ready for installation.

Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

  1. Identify the controller that contains the failed interface card:

    2. Item

    Component

    1

    Controller A
    2 Controller B
  1. Access the H-Series UI using the management address for the controller with the failed interface card.
  2. Power off the controller:

    3. Note: Do Not use the IPMI/BMC Web UI to power off the controller.

    Method 1: Controller power off

    Push and hold the power button on the front of the system for the desired controller. It will take 15-20 seconds until the controller is completely powered down:

    Method 2: Controller power off

    1. Log in to the CLI of your system:
      1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

        2. Use the admin user name and the password for the admin account on the system.

        Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

        #ssh admin@(IP or hostname)

      Connect using a console session on a client that supports ssh (for example, PuTTY on Windows systems, the Windows command line on Windows 10 or later, or the Terminal on MacOS systems).

      1. The first time you log into the CLI, you will need to enter "yes" to accept the ECDSA security key for this system connection when prompted:

        2. The authenticity of host '10.65.184.225.mycompany.com' can't be established.

        ECDSA key fingerprint is SHA256:HDCZP/C3ZrIFWONrbl/9s/KCR8g/WXrOXe0V9qbiLbM.

        Are you sure you want to continue connecting (yes/no)? yes

        You should see a prompt adding the security key to the list of known hosts.

        Warning: Permanently added '10.65.184.225' (ECDSA) to the list of known hosts.

      2. Enter the password for the admin account:

        3. admin@(IP or hostname)'s password:

        The CLI prompt for the system you are connected to displays.

        Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

        Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

        One moment, loading command sets...

        Welcome to the QBSP shell! Software version: Quantum CSP 2.4.0-Build89

        For available commands and usage, type help.

        (IP or hostname)>

    2. Enter the power_off command:

      3. (IP address or host name) > power_off

      Powering off this controller may disrupt I/O! Are you sure you want to continue (yes/no)? yes

      The system is going down for system halt NOW!

      Connection to (IP address or host name) closed.

    1. Log into and open the BMC Web UI, if you already have the IPMI cabled and configured for network access.
      1. On a laptop computer, open a supported web browser and enter the IP address for the BMC UI in the address box, and press Enter.

        2. For direct BMC/IPMI port connections ONLY, use https://192.168.17.1.

        Note: You must use “https://” the first time you access the BMC UI through the IPMI/BMC port.

        The log in dialog displays:

        (click image to enlarge)

      2. Log in to theBMC Web UI.

        Login credentials:

        • Username: ADMIN

        • Password: Use the password set for the BMC UI. For new systems not yet configured, or that have been re-imaged, reference the passwords for each node shown on the pullout tab located on the left rear corner of the H2000 chassis:

          • (click image to enlarge)

        The BMC UI displays:

        (click image to enlarge)

      If you do not currently have the IPMI configured on the network, and will access directly from the IPMI/BMC port:

      1. Connect a laptop to the IPMI/BMC port on one of the controllers:

        2. Item

        Description

        1

        IPMI/BMC port on Controller B

        2

        IPMI/BMC port on Controller A
      2. Access the IPMI/BMC using the IP address assigned to the IPMI/BMC port. To configure this address, see .
        Otherwise, to connect directly to the IPMI/BMC port on the back of the system for the first time (default IP address still assigned to this port), configure you laptop network settings. Complete one of the following two procedures, depending on whether you are using a Windows or Mac notebook computer:

        3. Configure the IPv4 network settings for the ethernet connection on the computer you will use to access the system while directly-connected to the IPMI/BMC port if the IP settings have not yet been changed.

        IPv4 network settings:

        • IP Address - 192.168.17.10
        • Subnet Mask - 255.255.255.0
        • Router (MacOS)/Gateway (Windows) - blank

        These steps apply to macOS Mojave. They may differ slightly for your version of macOS.

        1. Click an open area of the Mac desktop, and select Apple menu> System Preferences> Network or click the System Preferences icon from the Dock:

        2. Click the Network icon in System Preferences:

        3. Select the Ethernet connection being used.
        4. In the Configure IPv4 drop-down list, select Manually.

          5. Pro Tip!

          Quantum recommends that you record the settings in this dialog box before you change them. You can refer to this information later when you set the settings back to their original values — after you are finished using this network connection

        5. Enter the IP address and subnet mask values (leave router blank):

        IPv4 network settings:

        • IP Address - 192.168.17.10
        • Subnet Mask - 255.255.255.0
        • Router (MacOS)/Gateway (Windows) - blank

        Example (Mojave)

        1. Click Close.

          2. It may take a couple minutes to enable the network connection.

        1. Access the Network Connections dialog:
          • For Windows 10 (method 1), right-click the Start menu icon, click Network Connections and click Change Adapter Options in the right pane of the dialog.
          • For Windows 10 (method 2), open the Cortana search, and enter View network status and tasks, and click Change adapter settings in the left pane of the dialog.
          • From older Windows versions, click the Start menu, search for and open the View Network Connections dialog.
        2. Right-click the network connection that corresponds to the Ethernet port on the compute being used, something like Ethernet or Local Area Connection, and select Properties:

        3. From the list of connections, select Internet Protocol Version 4 (TCP/IPv4), and then click Properties to display the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box.

          Note: We recommend writing down the settings in this dialog box before you change them. You can refer to this information later when you set the settings back to their original values — after you are finished using this network connection.

        4. Click the Use the following IP address radio button, and enter the appropriate IP address and Subnet mask values (leave gateway blank) and click OK:

          IPv4 network settings:

          • IP Address - 192.168.17.10
          • Subnet Mask - 255.255.255.0
          • Router (MacOS)/Gateway (Windows) - blank

          Example:

          1. Click OK.
          2. Close the Network dialog.

            3. It may take a couple minutes to enable the network connection.

        1. On a laptop computer, open a supported web browser and enter the IP address for the BMC UI in the address box, and press Enter.

          2. For direct BMC/IPMI port connections ONLY, use https://192.168.17.1.

          Note: You must use “https://” the first time you access the BMC UI through the IPMI/BMC port.

          The log in dialog displays:

          (click image to enlarge)

        2. Log in to theBMC Web UI.

          Login credentials:

          • Username: ADMIN

          • Password: Use the password set for the BMC UI. For new systems not yet configured, or that have been re-imaged, reference the passwords for each node shown on the pullout tab located on the left rear corner of the H2000 chassis:

            • (click image to enlarge)

          The BMC UI displays:

          (click image to enlarge)

    2. On the IMPI/BMC Web UI main page, click Power Down in the Power Control section of the page (if power is currently On):

      3. This should perform a orderly (or graceful) power off of the system. The system status should change to "Host is currently off.":

      If you see an error message and the power is not off, or if you'd like to use an alternate method:

      1. Open the Remote Control > Power Control page:

      2. Click Power Off Server - Orderly Shutdown and then Perform Action:

        3. This should perform a orderly (or graceful) power off of the system. The system status should change to "Host is currently off.":

        If you see an error message and/or the power is not off, attempt to do an immediate server power down. Click Power Off Server -Immediate and then Perform Action:

        This should perform an immediate power off of the system. The system status should change to "Host is currently off.":

  1. Label which ports the cables are currently attached to on the controller, so you can later attach them to the same ports.

    Note: Label the cables being removed from the controller so it is easier to reconnect them when the controller is installed.

  2. Label all network, FC, and SAS (if JBOD is attached) cables before removing them, so they can be replaced into the same ports on the replacement controller.

  3. Remove all network, FC, and SAS (if JBOD is attached) cables from the rear of the controller.

    Note: Leave the power cables connected to the power supplies.

  1. At the rear of the chassis, locate the controller:

  2. Release the controller handle by loosening the thumb/phillips screws:

    3. Note: Examples in this section show Controller B being removed. The same process steps apply to Controller A.

  3. Pull the handles out, then downward:

  4. Pull the controller out by the handle while still pressing the latch.

    5. Note: When removing the controller, avoid bumping or detaching cables still attached to the controller . Carefully guide the cables attached to the controller out of the way.

  5. Place the controller on an electrostatic mat:

Note: If your system does not contain a PCIe card in a specific slot, then proceed to the removal procedure that applies to your system.

  1. Locate the Slot 1 card:

  2. Loosen the thumbscrew of the support bracket securing the slot 1 card to the controller:

  3. Remove the slot 1 card support bracket from the controller:

  4. If removable SFPs are installed in the card, remove these from the card since they may cause interference with card removal.

    5. Note: Label the SFP location in the card so you can install them into the same SFP slot in the card when the card is installed in the replacement controller.

  5. Slide the slot 1 card outside of the PCIe riser card’s slot and move it away from the back panel of the controller:

    6. Caution: If there are one or more cables that are routed over the top of the card, do not exert any pressure on them when removing the card from the slot or unseat the connector on the end of the cable harness. Try to maintain the cable routing as you remove the card and make a note of how this was routed so you route this the same way when re-installing the slot 1 card in the replacement controller.

  6. Lift the slot 1 card upward and remove from the controller:

  1. Replace the locking bracket back into the slot on the rear right-hand side of the controller.
  2. Replace the slot 1 PCIe interface card.

    3. Caution: If cables were routed over the top of the card on the failed controller, route the cables in the replacement controller in the same way they were routed prior to removing the card. Be careful not to exert too much force on these cables when replacing the card and ensure the connector on the end of the cable harness is not unseated during installation. Ensure the cables are pressed flat, so they don’t get caught when the controller is installed into the chassis, or rub between the board and the chassis (or Controller B for a Controller A replacement) once the controller is installed.

  3. Replace the slot 1 card support bracket, securing into place with the thumbscrew on the bracket.
  1. Locate the slot 2 card:

  2. Before you remove the card, locate and remove the card support bracket.

  3. Before you remove the card, locate and remove the SuperCap assembly.

  4. If removable SFPs are installed in the card, remove these from the card since they may cause interference with card removal.

    5. Note: Label the SFP location in the card so you can install them into the same SFP slot in the card when the card is installed again.

  5. Slide the card out of the PCIe riser card’s slot, and lift it upward to remove the card from the controller:

  1. Install the slot 2 PCIe interface card.

  2. Install the SuperCap assembly and lock it; verify there are no cables sticking out from the controller, specifically, SuperCap cables.

  3. Replace the slot 2 card support bracket, securing into place with the thumbscrew on the bracket. Verify it is not sticking up from the chassis.

  4. If removed, insert the SFPs into the same SFP slots where they were originally installed.

Before removing a card from slot 3:

  1. Locate the slot 3 card:

  2. Before you remove the card, locate and remove the card support bracket.

  3. Before you remove the card, locate and remove the SuperCap assembly.

  4. If removable SFPs are installed in the card, remove these from the card since they may cause interference with card removal.

    5. Note: Label the SFP location in the card so you can install them into the same SFP slot in the card when the card is installed again.

  5. Slide the card out of the PCIe riser card’s slot, and lift it upward to remove the card from the controller:

  1. Install the slot 3 PCIe interface card.

  2. Install the SuperCap assembly and lock it; verify there are no cables sticking out from the controller, specifically, SuperCap cables.

  3. Replace the slot 3 card support bracket, securing into place with the thumbscrew on the bracket. Verify it is not sticking up from the chassis.

  4. If removed, insert the SFPs into the same SFP slots where they were originally installed.

After installing the new card in slot 3:

  • Replace the slot 2 card (if used). See Install the new slot 2 interface card.
    1. Before you insert the controller into the chassis, verify the controller handles are pulled outward. Firmly slide the controller into the chassis.
    2. Push the controller handles upward to seat the controller firmly into the chassis mid-plane until it is fully-seated. Tighten the thumb/phillips screws on the controller handles to secure the controller in place in the chassis.

      3. The controller should start when it is seated correctly.

    3. Verify the controller is powered on. If the controller doesn't power on, press the power button on the left or right control panel on the front of the chassis that corresponds to the controller to power on.

      4. Note: Wait approximately 5-7 minutes for the controller to fully power on and boot.

    4. Verify if the NVD is healthy:

      1. Open a client terminal session on the controller you just inserted.
      2. Run the NVD status command:
        nvd_status

        3. If the NVD is fully healthy, it will display results similar to:

        Example output (NVD status - both NVD drives are healthy; status shown in green):

        If the NVDs in this controller are both healthy, repeat sub-step a through sub-step h on the other controller before you proceed to the next section.

        /dev/nvme2 is healthy (081321V1)
        /dev/nvme3 is healthy (081321V1)

        If the NVD is not fully healthy, it will display results similar to and you will need to continue with the following steps to fix this issue:

        Example output (NVD status - either one or both NVD drives is/are unhealthy; errors shown in red):

        If one or both of the NVDs in this controller are unhealthy, complete the rest of the sub-steps in this step.

        /dev/nvme2 is not healthy (081321V1)

        Remote NVD (01) is NOT enabled and ready

/dev/nvme3 is healthy (081321V1)
      3. Power off the controller with one or more failed NVDs.
      4. Push the powered-off controller handles down, and again remove it from the chassis.

        5. Wait for 5 minutes for the controller to cool down and the SuperCap to completely drain.

      5. Re-insert the controller into the chassis.
      6. Push the controller handles upward, making sure to fully-seat the controller in the chassis.
      7. After powering back up, check NVD status again according to the sub-steps in Step 3.
      8. Repeat sub-step a through sub-step f for the other controller node to make sure it sees both NVDs as well.

    • Connect all FC and/or Ethernet cables removed from the PCIe slots in the controller:

    1. Log in to the CLI of your system:

      1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

        2. Use the admin user name and the password for the admin account on the system.

        Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

        #ssh admin@(IP or hostname)

      Connect using a console session on a client that supports ssh (for example, PuTTY on Windows systems, the Windows command line on Windows 10 or later, or the Terminal on MacOS systems).

      1. The first time you log into the CLI, you will need to enter "yes" to accept the ECDSA security key for this system connection when prompted:

        2. The authenticity of host '10.65.184.225.mycompany.com' can't be established.

        ECDSA key fingerprint is SHA256:HDCZP/C3ZrIFWONrbl/9s/KCR8g/WXrOXe0V9qbiLbM.

        Are you sure you want to continue connecting (yes/no)? yes

        You should see a prompt adding the security key to the list of known hosts.

        Warning: Permanently added '10.65.184.225' (ECDSA) to the list of known hosts.

      2. Enter the password for the admin account:

        3. admin@(IP or hostname)'s password:

        The CLI prompt for the system you are connected to displays.

        Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

        Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

        One moment, loading command sets...

        Welcome to the QBSP shell! Software version: Quantum CSP 2.4.0-Build89

        For available commands and usage, type help.

        (IP or hostname)>

    2. Enter the fc_card_update command:

      (IP address or host name) > fc_card_update
       Hypervisor (d9c367-1)
   new target wwpns           old target wwpns

10:00:00:10:9b:cf:96:fa    10:00:00:10:9b:cf:95:f0
10:00:00:10:9b:cf:96:fb    10:00:00:10:9b:cf:95:f1
10:00:00:10:9b:cf:96:fc    10:00:00:10:9b:cf:95:f2
10:00:00:10:9b:cf:96:fd    10:00:00:10:9b:cf:95:f3

           Hypervisor (d9c367-2)
   new target wwpns           old target wwpns

10:00:00:10:9b:cf:96:96    10:00:00:10:9b:cf:96:0a
10:00:00:10:9b:cf:96:97    10:00:00:10:9b:cf:96:0b
10:00:00:10:9b:cf:96:98    10:00:00:10:9b:cf:96:0c
10:00:00:10:9b:cf:96:99    10:00:00:10:9b:cf:96:0d
10:00:00:10:9b:cf:96:0a    10:00:00:10:9b:cf:96:96
10:00:00:10:9b:cf:96:0b    10:00:00:10:9b:cf:96:97
10:00:00:10:9b:cf:96:0c    10:00:00:10:9b:cf:96:98
10:00:00:10:9b:cf:96:0d    10:00:00:10:9b:cf:96:99

Do you want to continue with reconfiguration?(y/n): y

Successfully updated /etc/scst.conf file

Updating /etc/scst.conf on peer node d9c367-2
Clearing failed statuses on the cluster
Successfully updated /etc/scst.conf file on peer node d9c367-2

NOTE: FC switch zoning may need to be updated for the new WWPNs

    3. Exit the SSH session:

      (IP address or host name) > exit

    Configure the FC Switch zone for the new FC card, and remove the WWPNs for the card being replaced. Make sure to zone the new FC card as the card being replaced. The WWPNs might come in the box for the replacement card, or they may display in the switch user interface.

    The H2000 VPI ethernet cards come pre-configured to operate in InfiniBand mode, although they support ethernet mode also. The H2000 was not originally configured with these cards configured for InfiniBand, and this is not supported on the H2000, the personality mode of the card must be changed from InfiniBand to Ethernet before using the system.

    1. Verify the link type (personality mode) of the Ethernet card. Enter:
      2. mstconfig query | grep LINK_TYPE

      Ouput:

               LINK_TYPE_P1IB(1)           
         LINK_TYPE_P2IB(1)

      Notice in the second column for both links, they are listed as IB (bold, green ), which means they are operating in Infiniband mode currently. (The following are shown in the output above: the port number [bold]; the personality "type" [bold, orange; type 1=Infiniband mode; personality type 2=Ethernet mode].)

    2. Verify the location of the configuration file used to change the personality mode:
      3. mstconfig query | grep -i device

      Output:

      Device #1:
Device type:    ConnectX5       
Device:         /sys/bus/pci/devices/0000:5e:00.0/config
    3. Use the config location from the example above (in green, bold) to change the personality type to Ethernet mode for both ports.

      4. Example:

      mstconfig -d /sys/bus/pci/devices/0000:5e:00.0/config set LINK_TYPE_P1=2 LINK_TYPE_P2=2

      In this example, we are setting the link type for port 1 (bold green) to type 2 (ethernet mode) and port 2 (bold, orange) to type 2 (ethernet mode).

      Output:

      Device #1:
----------
 
Device type:    ConnectX5       
Name:           N/A             
Description:    N/A             
Device:         /sys/bus/pci/devices/0000:5e:00.0/config
 
Configurations:                              Next Boot       New
         LINK_TYPE_P1                        IB(1)           ETH(2)          
         LINK_TYPE_P2                        IB(1)           ETH(2)          
 Apply new Configuration? (y/n) [n] :

      This shows that the new setting is set to ethernet mode for both ports "Eth (2)".

    4. Enter y to apply the configuration changes.
    5. You will see the following message:
      6. Applying... Done!
-I- Please reboot machine to load new configurations.
    6. Enter the following to reboot the system:
      7. reboot

      Output:

      Broadcast message from root@localhost (pts/1) (Thu Oct 17 18:54:51 2019):
 
The system is going down for reboot NOW!

      The system will reboot.

    Use one of the following methods to verify the interface card ports (from the replacement card) display in the respective PCI slot.

    Note: You must perform the interface card verification on the controller where you replaced the card, as both the H-Series UI and the CLI only display the information for the node you are logged in to.

    • Use the H-Series UI (user interface)

      1. Log in to the H-Series UI.

      2. On the top navigation menu, click Configuration.

      3. On the left navigation menu, click Interfaces. For example, the illustration below indicates there is an interface card in PCI slot two (2) that contains four (4) ports (s2p1, s2p2, s2p3, s2p4).

        Example (click to enlarge)

    • Use the CLI

      1. Log in to the CLI of your system.

        1. Open an SSH session using the management IP address or hostname of the controller using a Terminal/PuTTY client.

          2. Use the admin user name and the password for the admin account on the system.

          Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):

          #ssh admin@(IP or hostname)

        Connect using a console session on a client that supports ssh (for example, PuTTY on Windows systems, the Windows command line on Windows 10 or later, or the Terminal on MacOS systems).

        1. The first time you log into the CLI, you will need to enter "yes" to accept the ECDSA security key for this system connection when prompted:

          2. The authenticity of host '10.65.184.225.mycompany.com' can't be established.

          ECDSA key fingerprint is SHA256:HDCZP/C3ZrIFWONrbl/9s/KCR8g/WXrOXe0V9qbiLbM.

          Are you sure you want to continue connecting (yes/no)? yes

          You should see a prompt adding the security key to the list of known hosts.

          Warning: Permanently added '10.65.184.225' (ECDSA) to the list of known hosts.

        2. Enter the password for the admin account:

          3. admin@(IP or hostname)'s password:

          The CLI prompt for the system you are connected to displays.

          Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

          Last login: Thu Mar 10 10:07:51 2022 from 10.65.188.109

          One moment, loading command sets...

          Welcome to the QBSP shell! Software version: Quantum CSP 2.4.0-Build89

          For available commands and usage, type help.

          (IP or hostname)>

      2. Enter the show_cards -e command. For example, the output below indicates there is an interface card in PCI slot two (2) that contains four (4) ports.

        (IP address or host name) > show_cards -e
Slot Ports Description
1    0     Empty
2    4     Ethernet controller: Broadcom Inc. and subsidiaries Device 1751 (rev 11)
3    0     Empty

      3. Close the SSH terminal session:

        (IP address or host name) > exit

    After you've completed this section, the interface card replacement is complete.

    JBOD-Only CRUs

    Note: The CRUs in this section apply only to JBOD chassis.

    Required tools

    There are no tools required for this component replacement.

    Before you begin

    Caution: While the H2000 RAID and JBOD PSUs (Power Supply Units) may look similar and are the same size, they are not compatible. DO NOT use a RAID PSU in a JBOD chassis, and DO NOT use a JBOD PSU in a RAID chassis.

    Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

    Take ESD precautions when performing this replacement

    The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

    Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

    Keep static-sensitive parts in their original shipping containers until ready for installation.

    Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

    Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

    Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

    1. Locate the power supply module at the back of the unit; to determine the location of the PSU (for example, PSU 1 or PSU 2), see System Overview.
    2. Remove AC power cable from the PSU.
    3. Press the latch to the left with the thumb while pulling the PSU by the handle (red arrow below):

    4. Remove the PSU from the chassis:

    1. Insert the PSU into the slot and push it firmly until the latch clicks.
    2. Attach the AC power cable to the PSU:

    (image shown is from a RAID array, JBOD power cords are in the same location)

    After you've completed this section, the JBOD PSU CRU replacement is complete.

    Required tools

    There are no tools required for this component replacement.

    Before you begin

    Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

    Take ESD precautions when performing this replacement

    The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

    Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

    Keep static-sensitive parts in their original shipping containers until ready for installation.

    Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

    Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

    Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

    1. Press the latch key downward to release and unlatch fan module from its slot:

    2. Pull the fan module out by the handle and remove it from the chassis:

    Install the JBOD Fan Module in the chassis in the reverse order it was removed in the previous section.

    Note: Make sure the latch clicks when inserted into the enclosure

    After you've completed this section, the JBOD Fan Module CRU replacement is complete.

    Required tools

    There are no tools required for this component replacement.

    Before you begin

    Note: This component IS hot-swappable. You DO NOT need to stop all I/O from clients or remove power from both controllers to replace this component.

    Take ESD precautions when performing this replacement

    The chassis is designed to dissipate all electrostatic discharge (ESD) to the chassis base. Ensure that there is sufficient electrical and mechanical connection from the chassis base to the rack rails, and that the rack itself is tied to earth ground. The unit must be grounded in accordance with all local/regional and national electrical codes.

    Some components within the system contain static-sensitive parts. Precautions must be taken to ensure that the system is not exposed to ESD while handling components or servicing the unit. To avoid damaging these parts while performing maintenance procedures, always observe the following precautions:

    Keep static-sensitive parts in their original shipping containers until ready for installation.

    Do not place static-sensitive parts on a metal surface. Place them inside their protective shipping bag or on an anti-static mat.

    Wear anti-static wrist bands when unpacking and handling the units, and avoid touching connectors and other components.

    Dry climates and cold-weather heating environments have lower relative humidity and are more likely to produce static electricity.

    1. Remove any cables attached to the JBOD IOM.

      2. Note: Mark the port location before removing attached cables for re-attachment after the IOM is replaced.

    2. Press the latch key downward to release the handle:

    3. Pull the latch key handle outward:

    4. Pull the JBOD IOM from its slot:

    1. Install the JBOD IOM in the chassis in the reverse order it was removed in the previous section.
    2. Attach cables to the JBOD IOM in the same ports they were installed into previously in the failed JBOD IOM.

    After you've completed this section, the JBOD IOM CRU replacement is complete.