CRU Instructions

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

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).

2. 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:
Example:

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.

3. Enter the password for the admin account:

admin@(IP or hostname)'s password:

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

Example:

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.0.0-Build89

For available commands and usage, type help.

(IP or hostname)>

1. On a laptop, SSH to or open a PuTTY connection to the controller command line. Access the CLI.

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

#ssh root@10.20.85.72

c:\>ssh root@10.20.85.72

2. Enter the password for the root user (default password is "esos").

Before you begin

Note: The controller IS hot-swappable. However, if possible, power off the controller with the failed component(s) to replace it.

Note: You will need access to the rear of the F2000 chassis to remove the controller.

Identify the controller:

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

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).

2. 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:
Example:

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.

3. Enter the password for the admin account:

admin@(IP or hostname)'s password:

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

Example:

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.0.0-Build89

For available commands and usage, type help.

(IP or hostname)>

2. Enter the power_off command:
(IP or hostname) power_off

If a confirmation prompt is displayed, enter the required confirmation text.

Your SSH or PuTTY console will lose connection to the server. You can exit your console utility. The controller will gracefully power off.

1. Label the cables so you know how to reconnect them later in this process.
2. Disconnect the cables from interface cards installed in the system:
3. Remove the controller-to-controller interconnect cable from the system as shown here:



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

4. Disconnect your the CAT6A Ethernet cable from the IPMI/BMC port on the controller, if necessary.

1. Unlatch the controller by pulling both of the handles out from the chassis (Controller B shown):



2. Remove the controller by grasping the edges of the controller and pulling it clear of the chassis:

1. Place the controller on an ESD-protected surface.

1. Locate the new controller and unpack it from the box, if necessary.
2. Label the replacement controller to distinguish it from the failed controller.
3. Place the new controller on an ESD-protected surface.

Note: Install the interface cards in the identical slot location they were in in the failed controller.

Required tools:

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

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. Locate the new controller and unpack it from the box, if necessary.
2. Place the new controller on an ESD-protected surface.
3. Remove the controller cover from the controller being replaced:
Remove the controller cover
1. Unlock the controller cover by pressing the two lock buttons and slide the cover towards the rear of the controller:

Note: If you are removing Controller B, note that this controller is inverted. You must turn the controller over to access the controller cover.



2. Remove the cover by lifting the cover off of the controller.
4. Remove the internal components needed for the new controller from the controller being replaced:
Remove the interface cards

Note: Pay special attention to the slot location for the cards being replaced. They MUST be installed in the same slot location in the replacement controller as they are in the current controller. You may wish to migrate the cards from the old controller and immediately install in to the new controller one card at a time to ensure the cards are installed into the correct slots.

1. Locate the PCIe bracket that contains the interface card.
2. If used, remove the SFPs from all cards and set them aside:



3. Remove the PCIe bracket by carefully pulling up on the sheet metal carrier and lifting it out of the controller:



4. Place the PCIe bracket on an ESD-protected surface:



Item	Description
1	PCIe bracket
2	Interface card (FC card shown in example)

5. Detach the interface card from the PCIe bracket by pulling the two components apart



Remove the M.2 Boot Drives
1. Press the M.2 boot drive release latch to unseat the drive:



2. Remove the drive from the drive slot by pulling it out of the connector.

Pro Tip! Note which M.2 slot the boot drives are located in, so you can replace them into the identical slot on the replacement controller's motherboard.



3. Repeat for the other M.2 boot drive.
5. Replace the cover on the controller being replaced:
Install the controller cover

1. Align the cover over the controller and slide it towards the front of the controller.
2. Verify the lock buttons on the cover have engaged and the cover is secure:



6. Remove the cover from the replacement controller:
Remove the controller cover
1. Unlock the controller cover by pressing the two lock buttons and slide the cover towards the rear of the controller:

Note: If you are removing Controller B, note that this controller is inverted. You must turn the controller over to access the controller cover.



2. Remove the cover by lifting the cover off of the controller.
7. Install the internal components into the replacement controller:
Install the M.2 Boot Drives
Note: Make sure you replace the M.2 boot drives into the identical slot on the replacement controller's motherboard that it was installed in on the faulty controller's motherboard.
1. Slide the card edge of the M.2 boot drive into the connector with even pressure, and the opposite end of the card edge into the release latch:



2. Make sure the M.2 boot drive is fully seated in the slot:



3. Repeat for the other M.2 boot drive.
Install the interface cards

Note: Replace the cards in the same slot location they were in the controller being replaced.

1. Locate the interface card (either the 100 GbE card or the 32 Gb FC card).
2. Attach the interface card to the PCIe bracket:



3. Insert the PCIe bracket and Interface card into the controller:



4. For cards using SFPs, install the SFPs into the SFP ports on all cards required:



8. Install the cover on the replacement controller:
To install the controller cover

1. Align the cover over the controller and slide it towards the front of the controller.
2. Verify the lock buttons on the cover have engaged and the cover is secure:

1. Orient the replacement controller by lining up the controller slot in the chassis.

Note: Controller B is installed with the top cover facing the top of the chassis. Controller A is inverted and installed with the top cover facing toward the bottom of the chassis.

2. Insert the controller into the chassis:
1. Carefully slide the controller into the slot with both latch handles in the open position until the latch handles begin to engage (Controller B shown):



2. Rotate the latch handles into the chassis until the are fully engaged:

1. From the rear of the chassis, connect the management connections using CAT6A Ethernet cables from the 10 GbE switch to the Port 1 10 GbE port on Controller A and to the Port 1 10 GbE port on Controller B:



Item	Description
1	Port 1 (10 GbE) on Controller A (top)
2	Port 1 (10 GbE) on Controller B (bottom)

2. Cable the storage network connections depending on what type of storage network you have:

Note: Important! Connect the cables to the ports they were originally connected to.

1. If the system contains 100 GbE cards, connect the 100 GbE Copper Direct Attach cables to the Ethernet ports on Controller A and Controller B:
Cable 100 GbE models

Connect F2000 100GbE cables

1. Connect up to 2 100 GbE Copper Direct Attach cables to the 100 Gb Eth ports in PCIe slot 1 in Controller A (top), and connect up to 2 100 GbE Copper Direct Attach cables to the 2 100 Gb Eth ports in PCIe slot 1 in Controller B (bottom):

Note: If you are not connecting all 4 100 Gb Eth ports, connect one of the ports in the card in both controllers.



Item	Description
1	Dual-port 100 Gb Eth card in PCI slot 1 in Controller A (top)
2	Dual-port 100 Gb Eth card in PCI slot 1 in Controller B (bottom)

2. Connect the other end of the 100 Gb Eth Copper Direct Attach cables to a 100 Gb Eth network switch.

Note: QSFP optical transceivers need to be used if the switch contains optical ports. QSFP optical transceivers ARE NOT supplied by Quantum.

2. If the system contains 32 Gb FC cards, connect the FC cables to the FC ports in PCIe slot 1 and PCIe slot 3 on Controller A and Controller B:
Cable FC models

Connect F2000 FC cables

1. Connect up to 8 FC cables to the ports on the 32 Gb FC cards located in PCIe slot 1 and PCIe slot 3 in Controller B (bottom) and PCIe slot 3 and PCIe slot 1 Controller A (top):

Note: For maximum performance, connect 8 FC cables from the FC ports on the system to the FC switch. If you are not connecting all 8 FC ports, connect an even number of ports to the card in each controller. Connect at least 1 FC cable to a FC card in Controller A (top), and at least 1 FC cable to the same FC card in Controller B (bottom) for the system to function properly. You must connect a minimum of 2 FC connections for both controllers (a minimum of 4 FC connections for the system).
The controllers are installed 180 degrees opposite each other, meaning the slots and the ports are opposite one another, as described in the table below.



Item	Description
1	Quad-port 32 Gb FC card in PCIe slot 1 in Controller A (top)
2	Quad-port 32 Gb FC card in PCIe slot 2 in Controller A (top)
3	Quad-port 32 Gb FC card in PCIe slot 3 in Controller B (bottom)
4	Quad-port 32 Gb FC card in PCIe slot 1 in Controller B (bottom)

2. Connect the other end of the FC cables to a 32 Gb FC switch.

Note: For maximum performance, connect 8 FC cables from the FC switch to the FC ports on the system. If connecting only 2 FC ports to the switch, make sure to connect 1 cable to each FC card. Connect a minimum of 1 FC cable to Controller A (top) and 1 FC cable to Controller B (bottom) for the system to function properly.

3. Connect one end of the short CAT6A Ethernet controller-to-controller interconnect cable to the Port 4 10 GbE port on Controller A and the other side to the Port 4 10 GbE port on Controller B:

Note: This cable connection is for controller-to-controller communication and must be in place before applying power to the system.



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

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.

• For systems configured using the qstorage commands in the Appliance Controller (which includes all systems that currently are, or were previously using F-Series 1.x software), you will use commands in the Appliance Controller software on a host system (for example: Xcellis Workflow Director) for this procedure.
• Replace a degraded data drive ONLY with an SSD data drive of the same capacity.

Data drive capacities

The F2000 contains 24 NVMe SSD data drives, with different storage capacities.

Capacity options:

• 1.92 TB
• 3.84 TB
• 7.68 TB

Once you've identified the faulty data drive:

1. Open the CONFIGURATION > Storage page on the F-Series UI.

2. In the lower portion of the screen, in the RAID Array section, click on the drive slot that corresponds to the faulty data drive:



3. In the top of the drive panel, click the 3 dot drop-down icon:



4. Click Detach Drive:



The drive will detach and be ready for replacement.

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

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).

2. 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:
Example:

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.

3. Enter the password for the admin account:

admin@(IP or hostname)'s password:

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

Example:

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.0.0-Build89

For available commands and usage, type help.

(IP or hostname)>

4. Enter:

detach_drive auto

The system identifies the degraded drive and detaches it. It returns the following message if the drive detachment was successful:

All degraded drives were successfully removed

If the drive has lost power or is missing, the system will return the following message:

No action taken for detach request

1. Log in to the Appliance Controller on the host system (Xcellis StorNext Appliance):
   1. Open an SSH connection using the sysadmin user account.
   2. At the password prompt, enter the sysadmin user's password. Example SSH connection to the host server:

   login as: sysadmin sysadmin@quantum's password: Last login: Fri Dec 7 13:37:11 2018 from eng.example.com Welcome to Quantum Xcellis Appliance Controller Console --------------------------------------------------- *** Type 'help' for a list of commands. Xcellis:xcellis1>

   Note: Refer to Access the Appliance Controller in the Appliance Controller Documentation Center (https://www.quantum.com/accdocs).

2. Enter the following command to detach the degraded drive from the system:

qstorage drive detach auto

The system identifies the degraded drive and detaches it. It returns the following message if the drive detachment was successful:

All degraded drives were successfully removed

If the drive has lost power or is missing, the system will return the following message:

No action taken for detach request

Keep the SSH connection to the Appliance Controller Console open because you will need when performing the Step 4: Install the data drive assembly procedure.

1. Remove the bezel from the front of the F2000, if needed.
2. Locate the degraded data drive using the drive slot location you determine in Step 1: Identify a degraded SSD:
1. Release the data drive assembly by pressing the latch release button on the drive carrier and lowering the drive carrier handle until it is fully open.

2. Pull the drive assembly out of the drive slot using the drive carrier handle.

3. Repeat for additional drives as needed.

1. Obtain the new data drive assembly and open its drive carrier handle by pressing the drive carrier latch release button.
2. Orient the data drive assembly so the drive carrier latch release button is on top. Then slowly slide the drive into the open drive slot using the drive carrier release until the drive release engages:

3. Seat the drive by pressing the drive carrier handle into the drive carrier until it clicks. This will allow the drive to make the connection with the connector on the drive board without causing damage:

4. Repeat for additional drives, if needed.

Note: When seating multiple data drives, wait 15 seconds between drive insertions.

1. Launch the Appliance Controller from your host system (Xcellis StorNext appliance), and attach the new drive to the system by running the following command:

qstorage drive attach auto

The system identifies the new drive and attaches it. It returns the following message if the drive attachment was successful:

All new drives were successfully added

After the drive is replaced and the qstorage drive attach auto command is run, rebuilds for the arrays occur in parallel.

2. Run the following command to show the status of the drive recovery operation:

qstorage show health

The system provides status of the recovery operation:

Rebuild process started:       ], "qsa_health": "degraded", "resync": { "finish": "145.4min", "operation": "recovery", "progress": "3.7%", <----- "resynced": 69356160, "speed": "205891K/sec", "total": 1866333184 } } } } }, "model": "F2000", "qsa_health_A": "degraded"

Note: The system may experience a minor performance impact and the drive will remain in a "degraded" state until the recovery operation completes.

3. Replace the bezel on the front of the system.

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

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).

2. 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:
Example:

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.

3. Enter the password for the admin account:

admin@(IP or hostname)'s password:

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

Example:

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.0.0-Build89

For available commands and usage, type help.

(IP or hostname)>

4. From the QBSP shell, run the command to clear the drive cache. Enter:
clear_qsa_cache
5. Enter the command to locate the data drive:
show_drive

If you do not see a missing drive from either controller, as in Example Output # 1, you are done.

Example Output #1 (no missing nvme drives from Controller A (Node 1 Path) or Controller B (Node 2 Path):

Drive ID       Node 1 Path  Node 2 Path  LED    Power  Serial
encl01_slot01  /dev/nvme0   /dev/nvme22  True   True   S6EYNA0R600020
encl01_slot02  /dev/nvme1   /dev/nvme23  False  True   S6EYNA0R600019
encl01_slot03  /dev/nvme2   /dev/nvme21  False  True   S6EYNA0R600017
encl01_slot04  /dev/nvme3   /dev/nvme20  False  True   S6EYNA0R600018
encl01_slot05  /dev/nvme4   /dev/nvme19  False  True   S6EYNA0R600015
encl01_slot06  /dev/nvme5   /dev/nvme18  False  True   S6EYNA0R700201
encl01_slot07  /dev/nvme6   /dev/nvme17  False  True   S6EYNA0R700203
encl01_slot08  /dev/nvme7   /dev/nvme16  False  True   S6EYNA0R600016
encl01_slot09  /dev/nvme8   /dev/nvme14  False  True   S6EYNA0R600013
encl01_slot10  /dev/nvme9   /dev/nvme15  False  True   S6EYNA0R700202
encl01_slot11  /dev/nvme10  /dev/nvme13  False  True   S6EYNA0R600021
encl01_slot12  /dev/nvme11  /dev/nvme12  False  True   S4YPNC0T100725
encl01_slot13  /dev/nvme12  /dev/nvme11  False  True   SDM000061BB2
encl01_slot14  /dev/nvme13  /dev/nvme10  False  True   SDM000060367
encl01_slot15  /dev/nvme14  /dev/nvme9   False  True   SDM000061B2D
encl01_slot16  /dev/nvme15  /dev/nvme8   False  True   SDM000061C0F
encl01_slot17  /dev/nvme16  /dev/nvme6   False  True   SDM00002BFBA
encl01_slot18  /dev/nvme17  /dev/nvme7   False  True   SDM000061BF8
encl01_slot19  /dev/nvme18  /dev/nvme5   False  True   SDM0000178C3
encl01_slot20  /dev/nvme19  /dev/nvme4   False  True   SDM000061BB4
encl01_slot21  /dev/nvme20  /dev/nvme3   False  True   SDM00005E7E9
encl01_slot22  /dev/nvme21  /dev/nvme2   False  True   SDM000060390
encl01_slot23  /dev/nvme22  /dev/nvme1   False  True   SDM000061B5F
encl01_slot24  /dev/nvme23  /dev/nvme0   False  True   SDM00002CE4D

Example Output #2 (missing nvme drive 9 in slot 15 on Controller B [Node 2 Path]):

Drive ID       Node 1 Path  Node 2 Path  LED    Power  Serial
encl01_slot01  /dev/nvme0   /dev/nvme22  True   True   S6EYNA0R600020
encl01_slot02  /dev/nvme1   /dev/nvme23  False  True   S6EYNA0R600019
encl01_slot03  /dev/nvme2   /dev/nvme21  False  True   S6EYNA0R600017
encl01_slot04  /dev/nvme3   /dev/nvme20  False  True   S6EYNA0R600018
encl01_slot05  /dev/nvme4   /dev/nvme19  False  True   S6EYNA0R600015
encl01_slot06  /dev/nvme5   /dev/nvme18  False  True   S6EYNA0R700201
encl01_slot07  /dev/nvme6   /dev/nvme17  False  True   S6EYNA0R700203
encl01_slot08  /dev/nvme7   /dev/nvme16  False  True   S6EYNA0R600016
encl01_slot09  /dev/nvme8   /dev/nvme14  False  True   S6EYNA0R600013
encl01_slot10  /dev/nvme9   /dev/nvme15  False  True   S6EYNA0R700202
encl01_slot11  /dev/nvme10  /dev/nvme13  False  True   S6EYNA0R600021
encl01_slot12  /dev/nvme11  /dev/nvme12  False  True   S4YPNC0T100725
encl01_slot13  /dev/nvme12  /dev/nvme11  False  True   SDM000061BB2
encl01_slot14  /dev/nvme13  /dev/nvme10  False  True   SDM000060367
encl01_slot15  /dev/nvme14               False  True   SDM000061B2D
encl01_slot16  /dev/nvme15  /dev/nvme8   False  True   SDM000061C0F
encl01_slot17  /dev/nvme16  /dev/nvme6   False  True   SDM00002BFBA
encl01_slot18  /dev/nvme17  /dev/nvme7   False  True   SDM000061BF8
encl01_slot19  /dev/nvme18  /dev/nvme5   False  True   SDM0000178C3
encl01_slot20  /dev/nvme19  /dev/nvme4   False  True   SDM000061BB4
encl01_slot21  /dev/nvme20  /dev/nvme3   False  True   SDM00005E7E9
encl01_slot22  /dev/nvme21  /dev/nvme2   False  True   SDM000060390
encl01_slot23  /dev/nvme22  /dev/nvme1   False  True   SDM000061B5F
encl01_slot24  /dev/nvme23  /dev/nvme0   False  True   SDM00002CE4D

If you do see one or more missing drive paths from either controller, as in Example Output #2, you will need to resolve this or the system will not function properly. Continue with the following steps:

6. Locate the drive (resolve this for the first drive before attempting to resolve for other drives) in the correct Controller. Notice in the output (in bold red) this is in the first system chassis/enclosure in slot 15 and is the nvme14 device, but is missing from Controller B (in the Node 2 Path column).

7. Remove the missing drive from the chassis:

   1. Remove the bezel from the front of the F2000, if needed.
   2. Locate the degraded data drive using the drive slot location you determine in Step 1: Identify a degraded SSD:
   1. Release the data drive assembly by pressing the latch release button on the drive carrier and lowering the drive carrier handle until it is fully open.
   
   2. Pull the drive assembly out of the drive slot using the drive carrier handle.
   
   3. Repeat for additional drives as needed.

8. Insert the drive slowly and make sure it is fully seated:

   Note: When seating multiple data drives, wait 15 seconds between drive insertions.

   1. Obtain the new data drive assembly and open its drive carrier handle by pressing the drive carrier latch release button.
   2. Orient the data drive assembly so the drive carrier latch release button is on top. Then slowly slide the drive into the open drive slot using the drive carrier release until the drive release engages:
   
   3. Seat the drive by pressing the drive carrier handle into the drive carrier until it clicks. This will allow the drive to make the connection with the connector on the drive board without causing damage:
   
   4. Repeat for additional drives, if needed.

   Note: When seating multiple data drives, wait 15 seconds between drive insertions.

9. Clear the drive cache. Enter:

clear_qsa_cache

10. Enter the command to locate the data drive:

show_drive

11. Review the output of the show_drive command, as explained above.

If drive paths are still missing from either controller (Node 1 or 2 Path), repeat Step 4 through Step 8 to re-seat those additional drives one at a time, and review if there are any drive paths still missing. Repeat as necessary. After 5 attempts, if the device paths are still not all present, do the following:

1. Stop I/O to all connected clients.
2. Cycle chassis power. Enter:
reboot
3. Wait for the system to reboot. After the system reboots, log back into the command line, and re-run Step 6 through Step 8 and verify the drive paths are all shown. At this point. there are two outcomes of the 12-drive pack upgrade:

• If all drive paths are shown for Controller A and Controller B the 12-drive pack upgrade was successful. Restore I/O to all previously-connected clients.

• If a chassis power cycle still does not resolve the issue, contact Quantum support for further instructions.

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.

At the rear of the F2000, locate the failed PSU by identifying the PSU with the illuminated amber PSU Fault LED:

Item	LED	Action
1	PSU Fault LED	Amber (solid): Fault, failure, or AC disconnection on PSU

1.

From the rear of the chassis, disconnect the power cord connected to the failed PSU.

a.

Detach the cable retention clip from the power cord:

b.

Remove the power cord by pulling firmly, but do not jerk it out of the unit.

2.

Remove the PSU from the chassis.

a.

Unlock the PSU by pressing down on the PSU release latch:

b.

Remove the PSU by pulling on the PSU handle until it is clear of the PSU bay:

Note: Do not pull on the gray PIB canister tab. The PIB canister should not be removed from the chassis unless it has been identified as a failed part.

1.

Install the PSU into the chassis.

a.

Orient the PSU so the PSU release latch is on top and the fan is on the bottom.

b.

Slide the PSU into the slot until it seats properly into the chassis:

c.

Plug the power cable into the receptacle at the back of the PSU.

d.

Loop the retention clip around the cable and pinch it until the clip catches and locks in place:

e.

Slide the retention clip forward until it stops near the cable connector. Doing this will ensure that the retention clip functions properly in the event the cable is yanked on for some reason:

2.

Verify the PSU is functional by identifying the PSU Fault LED is no longer indicating a fault. This is indicated by the PSU Fault LED illuminated green:

Item	LED	Action
1	PSU Fault LED	Green solid: Powered on, DC output OK

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.

After identifying the failed PIB canister, disconnect the power cord from the PSU that is connected to the PIB:

a.

Detach the cable retention clip from the power cord:

b.

Remove the power cord by pulling firmly, but do not jerk it out of the unit.

2.

Remove the PSU from the chassis.

a.

Unlock the PSU by pressing down on the PSU release latch:

b.

Remove the PSU by pulling on the PSU handle until it is clear of the PSU bay:

3.

Remove the PIB Canister:

a.

Locate the gray tab just below the location of the removed PSU.

b.

Grasp the gray tab firmly and carefully pull the PIB Canister until the card edge comes out of the midplane:

c.

Pull the PIB canister out from the chassis.

1.

Line up the PIB canister with the chassis PIB canister guide.

2.

Slowly slide the PIB Canister into the chassis until the card edge touches the midplane connector:

3.

Press the PIB canister into the midplane connector.

4.

Verify that the PIB canister is seated firmly.

5.

Install the PSU into the chassis:

a.

Orient the PSU so the PSU release latch is on top and the fan is on the bottom.

b.

Slide the PSU into the slot until it seats properly into the chassis:

c.

Plug the power cable into the receptacle at the back of the PSU.

d.

Loop the retention clip around the cable and pinch it until the clip catches and locks in place:

e.

Slide the retention clip forward until it stops near the cable connector. Doing this will ensure that the retention clip functions properly in the event the cable is yanked on for some reason:

Required tools:

#1 Phillips screwdriver

Laptop computer

Ethernet cable

Before you begin:

Note: This component is NOT hot-swappable. Be sure to stop all I/O from clients before powering down the F2000 to avoid data loss.

1. Connect to the IPMI/BMC port on Controller A and log in to the BMC Web UI:
Connect to the IPMI/BMC port

Use an Ethernet cable to connect a notebook computer to the IPMI/BMC port on one of the controllers:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

Configure laptop network settings for direct connections

Complete one of the following two procedures, depending on whether you are using a Windows or Mac notebook computer.

Configure the IPv4 network settings for the ethernet connection on the computer you will access the system directly from while connected to the Service Port, if the default IP address has not changed. If it has changed and the BMC/IPMI port you can skip this section and connect over your network using the IP address you configured for the BMC.

• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0

How to configure IPv4 for Mac

These steps 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.

   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.

5. Enter the IP address and subnet mask values (leave router blank):
• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0
• Router - blank

Example (Mojave)



6. Click Apply.
7. Close the Network dialog.

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

How to configure IPv4 For Windows

Keep in mind that the following steps may differ for your situation, depending on your version of Windows.

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:
   • IP Address - 192.168.17.10
   • Subnet Mask - 255.255.255.0
   • Gateway - blank
   
   
5. Click Close.

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

Log in to the BMC Web UI

1. On the notebook computer, open a supported Web browser and navigate to the IPMI/BMC by appending the IP address after https:// in your browser's address bar. For direct BMC connections where the IPMIBMC IP address has not changed, enter https://192.168.17.21 in the address box, and press Enter.

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

The Web UI Welcome to BMC dialog displays:



2. Log in to the BMC Web UI. The default credentials are:
• Username: admin (this is the default user name for older systems; could have been changed in the UI, so use that one if this was changed; for newer systems, use the user name found on the pullout tab of the system)
• Password: admin (use the BMC password; admin is the default password for older systems; this could have been changed in the UI, . Use the password found on the pullout tab of the system, if the password was not changed from the default, or use the one it was changed to in the F-Series UI (Newer systems [ONLY])

The BMC Web UI Dashboard displays:



2. On the BMC Web UI Dashboard, click Power Control on the left navigation:

The BMC Web UI Power Control page appears:



3. Select Power Off and click Perform Action.

A dialog window appears with the following question: “Are you sure to perform this operation?”

4. Click OK to power off the controllers.

The system displays the following message: “Performing Power Action, Please wait”

The Fault LED on the front of the system and on the rear of the selected controller turns on solid amber when the controller is powered off. The indicator on the rear of both controllers will turn solid amber when they are both powered off (example of rear of the system shows the power indicator on Controller B):

5. Disconnect the CAT6A Ethernet cable from the IPMI/BMC port on the controller.
6. Connect the Ethernet cable to the IPMI/BMC port on Controller B:



7. Repeat the steps in this section to power off Controller B.

1. At the rear of the system, locate the PSU A and PSU B receptacles:



Item	Description
1	Power supply unit (PSU) A
2	Power supply unit (PSU) B

2. Detach the cable retention clips from the power cables on PSU A and PSU B:



3. Remove the power cables by pulling them out of the PSU receptacles. Do not jerk the cables.
4. Disconnect the CAT6A Ethernet cables from the IPMI/BMC port on Controller A and Controller B:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

5. Label the cables so you know how to reconnect them later in this process. For example, the cable you disconnected from Port 1 in Controller A could be labeled “p1top”:
6. If the system contains 100 GbE cards, disconnect the 100 GbE Copper Direct Attach cables from the Ethernet ports in PCIe slot 1 on Controller A and in PCIe slot 1 on Controller B:



Item	Description
1	Controller A PCIe slot locations.
2	Controller B PCIe slot locations.

7. Remove the controller-to-controller interconnect cable from Controllers A and B as shown here:



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

8. Go to the front of the system and remove the front bezel by pulling it away from the system and set it aside:



9. Repeat the above steps for the other controller.

1.

Locate the black screws that are installed below the thumbscrews on the front of the chassis. There is one screw on each side of the chassis.

2.

Remove screws from the Rails using a #1 Phillips screwdriver:

3.

Locate the thumbscrews on both sides of the chassis.

4.

Loosen the thumbscrews by turning them counterclockwise until they are free of the rail connection:

Caution: Two people are needed to lift and move the (Undefined variable: F2000UserGuide.ProdcutName)chassis. Use care to avoid injury.

5.

Grasp the sheet metal brackets on either side of the front of the chassis and pull the chassis until it is free of the rack-mounted rails and place the system on an ESD-protected surface:

1.

Locate the black screws that are installed on the rear rail connections.

2.

Remove the screws from rails using a #1 Phillips screwdriver.

3.

Open the front latch by pulling the tab and rotating the latch open until it is at 90 degrees:

4.

Push the front rail connection out of the rack post:

5.

Carefully grasp the rail and open the rear latch by pulling the tab and rotating the latch open until it is at 90 degrees:

6.

Pull the rear rail connection free of the rack posts.

7.

Repeat the previous procedure to remove the remaining rail.

8.

Locate the new rack rails and identify the right rack rail.

9.

Open the front and rear latches of the rack rails by pulling the tab and rotating the latch open until it is at 90 degrees or greater:

10.

Identify the right rail, and line up the rail on the bottom 1U of the installation location.

11.

Place rear pins of the rail into rear rack post.

12.

Secure the rear rail attachment to the rear rack post by rotating the rear latch until it clips over the rear rack post:

13.

Align the front rail attachment with the same 1U space as the rear rail attachment.

14.

Slide the front rail attachment to fit snugly up against the front rack post:

15.

Secure the front rail attachment by rotating the front latch until it clips over the front rack post:

16.

Secure the rear rail attachment to the rack post using two screws.

17.

Repeat Step 11 through Step 16 to install the left rail.

1.

Line up the chassis with the rack-mounted rails and slide the chassis into the rack until the it is seated against the rack-mounted rails:

2.

At the front of the chassis, locate the thumbscrews on either side of the chassis.

3.

Tighten the thumbscrews by turning them clockwise until snug:

4.

Further secure the chassis by installing the provided black screws into the bottom holes:

 

 

 

 

1.

From the rear of the chassis, connect the appropriate CAT6A Ethernet cables from the 10 GbE switch to the 10 GbE (port 1) on Controller A and the 10 GbE (port 1) on Controller B:

2.

If the system contains 100 GbE cards, connect the 100 GbE Copper Direct Attach cables to the Ethernet ports in PCIe slot 1 on Controller A and Controller B:

3.

If the system contains 32 Gb FC cards, connect the FC cables to the FC ports in PCIe slot 1 and PCIe slot 3 on Controller A and Controller B (see figure above).

4.

Connect one end of the short CAT6A Ethernet controller-to-controller interconnect Ethernet cable to Port 4 on Controller A and the other side to port 4 on Controller B:

Note: This cable connection is for controller-to-controller communication and must be in place before applying power to the system.

5.

Connect one power cable to PSU A and the other cable to PSU B:

Note: Quantum recommends connecting each power cord to a separate AC circuit to ensure system availability in case of a power failure.\

The system will automatically start up about 20 seconds after power is applied. It will take a few minutes for the system to completely start up.

6.

Loop the retention clips around the power cables and pinch them until the clips catch and lock in place:

7.

Slide the retention clips forward until they stop near the cable connector. Doing this will ensure that the retention clips function properly in the event the cable is yanked:

1. Repeat the above steps for the other controller.

Once the controller is physically powered-on, from a notebook computer, access the BMC Web UI and log in.

1. In the BMC Web UI, click Sensor.
2. Verify that there are no failures reported.
3. Disconnect the CAT6A Ethernet cable from the IPMI/BMC port on Controller A.
4. Repeat the steps in this section on Controller B to verify Controller B is functioning properly.

1.

Locate the F2000 bezel:

2.

Attach the bezel to the four mounting posts at the front of the chassis:

Required tools:

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

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. Identify the controller that contains the failed interface card:



Item	Component
1	Controller A
2	Controller B

1. Access the BMC Web UI:
Connect to the IPMI/BMC port

Use an Ethernet cable to connect a notebook computer to the IPMI/BMC port on one of the controllers:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

Configure laptop network settings for direct connections

Complete one of the following two procedures, depending on whether you are using a Windows or Mac notebook computer.

Configure the IPv4 network settings for the ethernet connection on the computer you will access the system directly from while connected to the Service Port, if the default IP address has not changed. If it has changed and the BMC/IPMI port you can skip this section and connect over your network using the IP address you configured for the BMC.

• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0

How to configure IPv4 for Mac

These steps 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.

   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.

5. Enter the IP address and subnet mask values (leave router blank):
• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0
• Router - blank

Example (Mojave)



6. Click Apply.
7. Close the Network dialog.

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

How to configure IPv4 For Windows

Keep in mind that the following steps may differ for your situation, depending on your version of Windows.

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:
   • IP Address - 192.168.17.10
   • Subnet Mask - 255.255.255.0
   • Gateway - blank
   
   
5. Click Close.

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

Log in to the BMC Web UI

1. On the notebook computer, open a supported Web browser and navigate to the IPMI/BMC by appending the IP address after https:// in your browser's address bar. For direct BMC connections where the IPMIBMC IP address has not changed, enter https://192.168.17.21 in the address box, and press Enter.

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

The Web UI Welcome to BMC dialog displays:



2. Log in to the BMC Web UI. The default credentials are:
• Username: admin (this is the default user name for older systems; could have been changed in the UI, so use that one if this was changed; for newer systems, use the user name found on the pullout tab of the system)
• Password: admin (use the BMC password; admin is the default password for older systems; this could have been changed in the UI, . Use the password found on the pullout tab of the system, if the password was not changed from the default, or use the one it was changed to in the F-Series UI (Newer systems [ONLY])

The BMC Web UI Dashboard displays:



2. On the BMC Web UI Dashboard, click Power Control in the navigation menu:



The BMC Web UI Power Control page appears:



1. Select Power Off and click Perform Action.

A dialog window appears with the following question: “Are you sure to perform this operation?”

2. Click OK to power off the controllers.

The system displays the following message: “Performing Power Action, Please wait”

The Fault LED on the front of the system and on the rear of the selected controller turns on solid amber when the controller is powered off. The indicator on the rear of both controllers will turn solid amber when they are both powered off (example of rear of the system shows the power indicator on Controller B):

1. Disconnect the CAT6A Ethernet cables from Port 1 on the controller that contains the failed interface card:



Item	Description
1	Port 1 on Controller A
2	Port 1 on Controller B

2. Label the cables so you know how to reconnect them later in this process. For example, the cable you disconnected from Port 1 on Controller A could be labeled “p1top”.
3. If the system contains 100 GbE cards, disconnect the 100 GbE Copper Direct Attach cables from the Ethernet ports in PCIe slot 1 on the controller that contains the failed interface card. If the system contains 32 Gb FC cards, disconnect the FC cables from the FC ports in PCIe slot 1 and PCIe slot 3 on the controller that contains the failed interface card. For reference, here are the PCIe slot locations for both controllers.



Item	Description
1	Controller A PCIe slot locations.
2	Controller B PCIe slot locations.

4. Disconnect the CAT6A controller-to-controller interconnect Ethernet cable shown here that connects Port 4 on Controller A to port 4 on Controller B:



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

5. Disconnect the CAT6A Ethernet cable from the IPMI/BMC port on the controller.

1. Unlatch the controller by pulling both of the handles out from the chassis (Controller B shown):



2. Remove the controller by grasping the edges of the controller and pulling it clear of the chassis:

1. Unlock the controller cover by pressing the two lock buttons and slide the cover towards the rear of the controller:

Note: If you are removing Controller B, note that this controller is inverted. You must turn the controller over to access the controller cover.



2. Remove the cover by lifting the cover off of the controller.

1. Locate the PCIe bracket that contains the interface card.
2. If used, remove the SFPs from all cards and set them aside:



3. Remove the PCIe bracket by carefully pulling up on the sheet metal carrier and lifting it out of the controller:



4. Place the PCIe bracket on an ESD-protected surface:



Item	Description
1	PCIe bracket
2	Interface card (FC card shown in example)

5. Detach the interface card from the PCIe bracket by pulling the two components apart

1. Locate the interface card (either the 100 GbE card or the 32 Gb FC card).
2. Attach the interface card to the PCIe bracket:



3. Insert the PCIe bracket and Interface card into the controller:



4. For cards using SFPs, install the SFPs into the SFP ports on all cards required:

1. Align the cover over the controller and slide it towards the front of the controller.
2. Verify the lock buttons on the cover have engaged and the cover is secure:

1. Install the controller into the chassis.
1. From the rear of the chassis, line up the controller with the empty controller slot. Make sure that the controller is oriented correctly.

Note: Controller B is inverted and installed with the top cover facing toward the bottom of the chassis. Controller A is installed with the top cover facing the top of the chassis.

2. Carefully slide the controller into the slot with both latch handles in the open position until the latch handles begin to engage (Controller B shown):

Note: DO NOT engage the latch handles at this time. Engaging the latch handles applies power to the controller. First connect the controller-to-controller interconnect cable, and all other FC, 100 GbE and network cables.

1. Connect the short CAT6A controller-to-controller interconnect Ethernet cable to Port 4 on Controller A and the other side to port 4 on Controller B:

Note: This cable connection is for controller-to-controller communication and must be in place before applying power to the system.



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

Note: Verify that the short CAT6A Ethernet cable that connects Port 4 on Controller A to port 4 on Controller B (see figure above) is securely connected. This cable connection must be in place before applying power to the system.

2. Connect the appropriate CAT6A Ethernet cables to Port 1 on Controller A and Port 1 on Controller B:



Item	Description
1	Port 1 on Controller A
2	Port 1 on Controller B

3. If the system contains 100 GbE cards, connect the 100 GbE Copper Direct Attach cables to the Ethernet ports in PCIe slot 1 on the controller:



Item	Description
1	Controller A PCIe slot locations.
2	Controller B PCIe slot locations.

4. If the system contains 32 Gb FC cards, connect the FC cables to the FC ports in PCIe slot 1 and PCIe slot 3 on Controller A and Controller B (see figure above).

1. Rotate the latch handles into the controller until the are fully engaged (Controller B shown in the example below). This applies power to the controller. The controller will power itself on about 20 seconds after it is connected to power.

The F2000 VPI ethernet cards come pre-configured to operate in InfiniBand mode, although they support ethernet mode also. The F2000 was not originally configured with these cards configured for InfiniBand, and this is not supported on the F2000, 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:
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:
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.

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:

Applying... Done!
-I- Please reboot machine to load new configurations.

6. Enter the following to reboot the system:

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.

1. Using a CAT6A Ethernet cable, connect a notebook computer to the IPMI/BMC port on Controller A:



2. Access the BMC Web UI:

Connect to the IPMI/BMC port

Use an Ethernet cable to connect a notebook computer to the IPMI/BMC port on one of the controllers:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

Configure laptop network settings for direct connections

Complete one of the following two procedures, depending on whether you are using a Windows or Mac notebook computer.

Configure the IPv4 network settings for the ethernet connection on the computer you will access the system directly from while connected to the Service Port, if the default IP address has not changed. If it has changed and the BMC/IPMI port you can skip this section and connect over your network using the IP address you configured for the BMC.

• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0

How to configure IPv4 for Mac

These steps 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.

   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.

5. Enter the IP address and subnet mask values (leave router blank):
• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0
• Router - blank

Example (Mojave)



6. Click Apply.
7. Close the Network dialog.

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

How to configure IPv4 For Windows

Keep in mind that the following steps may differ for your situation, depending on your version of Windows.

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:
   • IP Address - 192.168.17.10
   • Subnet Mask - 255.255.255.0
   • Gateway - blank
   
   
5. Click Close.

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

Log in to the BMC Web UI

1. On the notebook computer, open a supported Web browser and navigate to the IPMI/BMC by appending the IP address after https:// in your browser's address bar. For direct BMC connections where the IPMIBMC IP address has not changed, enter https://192.168.17.21 in the address box, and press Enter.

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

The Web UI Welcome to BMC dialog displays:



2. Log in to the BMC Web UI. The default credentials are:
• Username: admin (this is the default user name for older systems; could have been changed in the UI, so use that one if this was changed; for newer systems, use the user name found on the pullout tab of the system)
• Password: admin (use the BMC password; admin is the default password for older systems; this could have been changed in the UI, . Use the password found on the pullout tab of the system, if the password was not changed from the default, or use the one it was changed to in the F-Series UI (Newer systems [ONLY])

The BMC Web UI Dashboard displays:



3. On the BMC Web UI, verify that the controller does not report any errors.
4. Disconnect the CAT6A Ethernet cable from the IPMI/BMC port on the controller.

Required tools:

• Laptop computer
• Ethernet cable

Before you begin:

Note: This component is NOT hot-swappable. Be sure to stop all I/O from clients before powering down the F2000 to avoid data loss.

There are five fan modules in each controller. Each fan module is comprised of two fans.

When a fan module fails and needs to be replaced, you need to identify which controller contains the failed fan module and locate the fan module within the controller.

You can identify which controller contains a failed fan module by viewing the Sensor Reading page in the BMC Web UI for both controllers.

The Sensor Reading page reports a State of Normal for all fans operating properly. In the Sensor Reading page example in , Fan0_STATUS and Fan1_STATUS report something other than Normal:

Fan0 and Fan1 comprise a single fan module. This fan module is located in fan slot 1. Fve fan slot locations within a controller along with the fan names that display in the BMC Web UI:

Item	Physical Fan Slot Location	Fan Names in BMC Web UI
1	Fan module 1 in fan slot 1	Fan0 and Fan1
2	Fan module 2 in fan slot 2	Fan2 and Fan3
3	Fan module 3 in fan slot 4	Fan4 and Fan5
4	Fan module 4 in fan slot 4	Fan6 and Fan7
5	Fan module 5 in fan slot 5	Fan8 and Fan9

To remove a failed fan module:

1. Identify the controller that contains the failed fan module:

a.

Connect the Ethernet cable to the IPMI/BMC port on the Controller A or Controller B:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

b.

Access the BMC Web UI:

Connect to the IPMI/BMC port

Use an Ethernet cable to connect a notebook computer to the IPMI/BMC port on one of the controllers:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

Configure laptop network settings for direct connections

Complete one of the following two procedures, depending on whether you are using a Windows or Mac notebook computer.

Configure the IPv4 network settings for the ethernet connection on the computer you will access the system directly from while connected to the Service Port, if the default IP address has not changed. If it has changed and the BMC/IPMI port you can skip this section and connect over your network using the IP address you configured for the BMC.

• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0

How to configure IPv4 for Mac

These steps 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.

   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.

5. Enter the IP address and subnet mask values (leave router blank):
• IP Address - 192.168.17.10
• Subnet Mask - 255.255.255.0
• Router - blank

Example (Mojave)



6. Click Apply.
7. Close the Network dialog.

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

How to configure IPv4 For Windows

Keep in mind that the following steps may differ for your situation, depending on your version of Windows.

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:
   • IP Address - 192.168.17.10
   • Subnet Mask - 255.255.255.0
   • Gateway - blank
   
   
5. Click Close.

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

Log in to the BMC Web UI

1. On the notebook computer, open a supported Web browser and navigate to the IPMI/BMC by appending the IP address after https:// in your browser's address bar. For direct BMC connections where the IPMIBMC IP address has not changed, enter https://192.168.17.21 in the address box, and press Enter.

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

The Web UI Welcome to BMC dialog displays:



2. Log in to the BMC Web UI. The default credentials are:
• Username: admin (this is the default user name for older systems; could have been changed in the UI, so use that one if this was changed; for newer systems, use the user name found on the pullout tab of the system)
• Password: admin (use the BMC password; admin is the default password for older systems; this could have been changed in the UI, . Use the password found on the pullout tab of the system, if the password was not changed from the default, or use the one it was changed to in the F-Series UI (Newer systems [ONLY])

The BMC Web UI Dashboard displays:



c.

On the BMC Web UI Dashboard, identify if the failed fan module is located in the controller.

d.

Do one of the following:

If the controller contains the failed fan module, continue with Step .

If the controller does not contain the failed fan module, repeat Step a through Step c to identify if the other controller contains the failed fan module.

4. On the BMC Web UI Dashboard, click Power Control in the navigation menu.

The BMC Web UI Power Control page appears:



5. Select Power Off and click Perform Action.

A dialog window appears with the following question: “Are you sure to perform this operation?”

6. Click OK to power off the controllers.

The system displays the following message: “Performing Power Action, Please wait”

The Fault LED on the front of the system and on the rear of the selected controller turns on solid amber when the controller is powered off. The indicator on the rear of both controllers will turn solid amber when they are both powered off (example of rear of the system shows the power indicator on Controller B):

7. Disconnect the CAT6A Ethernet cables from Port 1 on the controller that contains the failed fan:



Item	Description
1	Port 1 on Controller A
2	Port 1 on Controller B

8. Label the cables so you know how to reconnect them later in this process. For example, the cable you disconnected from Port 1 in the top controller could be labeled “p1top”.
9. If the system contains 100 GbE cards, disconnect the 100 GbE Copper Direct Attach cables from the Ethernet ports in PCIe slot 1 on the controller that contains the failed fan:



Item	Description
1	Controller A PCIe slot locations.
2	Controller B PCIe slot locations.

10. If the system contains 32 Gb FC cards, disconnect the FC cables from the FC ports in PCIe slot 1 and PCIe slot 3 on the controller that contains the failed fan module.
11. Disconnect the CAT6A controller-to-controller interconnect Ethernet cable shown here that connects Port 4 on Controller A to port 4 on Controller B:



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

12. Disconnect your the CAT6A Ethernet cable from the IPMI/BMC port on a controller, if necessary.
13. Unlatch the controller by pulling both of the handles out of the chassis:



14. Remove the controller by grasping the edges of the controller and pulling it clear of the chassis:



15. Set the controller on a ESD-protected surface.
16. Remove the controller cover.

Note: If you are removing Controller A, note that this controller is inverted. You must turn the controller over to access the controller cover.

a.

Unlock the controller cover by pressing the two lock buttons and slide the cover towards the rear of the controller:



b.

Remove the cover by lifting the cover off of the controller.

17. Identify the location of the failed fan.
18. Disconnect the fan cable from the connector:



Item	Description
1	Fan module connector (Fan module 1 shown in the example)
2	Fan module cable
3	Fan module installed in fan slot 1

19. Lift the fan module up and out from the fan slot using the fan handles:

To install a fan module:

1.

Insert the new fan module in to the fan slot.

2.

Connect the fan module cable to the fan connector:

3.

Install the controller cover:

a.

Align the cover over the controller and slide it towards the front of the controller.

b.

Verify the lock buttons on the cover have engaged and the cover is secure:

4.

Install the controller into the chassis:

a.

From the rear of the chassis, line up the controller with the empty controller slot. Make sure that the controller is oriented correctly.

Note: Controller A is inverted and installed with the top cover facing toward the bottom of the chassis. Controller B is installed with the top cover facing the top of the chassis.

b.

Carefully slide the controller into the slot with both latch handles in the open position until the latch handles begin to engage:

5.

For F2000 1.1, skip this step and continue to the next step. For F2000 1.0 and 1.0.1 ONLY, connect the short CAT6A Ethernet cable shown here that connects Port 4 on Controller A to port 4 on Controller B.:

Note: Verify that the CAT6A Ethernet cable that connects Port 4 on Controller A to port 4 on Controller B is securely connected. This cable connection must be in place before applying power to the system.

6.

Connect the appropriate CAT6A Ethernet cables to Port 1 on Controller A and Port 1 on Controller B:

7.

If the system contains 100 GbE cards, connect the 100 GbE Copper Direct Attach cables to the Ethernet ports in PCIe slot 1 on the controllers:

8.

If the system contains 32 Gb FC cards, connect the FC cables to the FC ports in PCIe slot 1 and PCIe slot 3 on Controller A and Controller B.

9.

Rotate the latch handles into the controller until the are fully engaged. This applies power to the system. The controller will power itself on about 20 seconds after it is connected to power:

Once the controller is physically powered-on, from a notebook computer, access the BMC Web UI and log in.

1. In the BMC Web UI, click Sensor.
2. Verify that the fan module fans show a State of Normal:

Required tools

#0 screwdriver

#1 Phillips screwdriver

Laptop computer

CAT6A Ethernet cable

Before you begin

Note: This component is NOT hot-swappable. Be sure to stop all I/O from clients before powering down the F2000 to avoid data loss.

Depending on whether you have 1.x software or 2.x software, do the following:

To disconnect the cables:

1. At the rear of the system, locate the PSU A and PSU B receptacles:



Item	Description
1	Power supply unit (PSU) A
2	Power supply unit (PSU) B

2. Detach the cable retention clips from the power cables on PSU A and PSU B:



3. Remove the power cables by pulling them out of the PSU receptacles. Do not jerk the cables.
4. Disconnect the CAT6A Ethernet cables from the IPMI/BMC port on Controller A and Controller B:



Item	Description
1	IPMI/BMC port on Controller A
2	IPMI/BMC port on Controller B

5. Label the cables so you know how to reconnect them later in this process. For example, the cable you disconnected from Port 1 in Controller A could be labeled “p1top”:
6. If the system contains 100 GbE cards, disconnect the 100 GbE Copper Direct Attach cables from the Ethernet ports in PCIe slot 1 on Controller A and in PCIe slot 1 on Controller B:



Item	Description
1	Controller A PCIe slot locations.
2	Controller B PCIe slot locations.

7. Remove the controller-to-controller interconnect cable from Controllers A and B as shown here:



Item	Description
1	Port 4 on Controller A
2	Port 4 on Controller B

8. Go to the front of the system and remove the front bezel by pulling it away from the system:

1.

Locate the black screws that are installed below the thumbscrews on the front of the chassis. There is one screw on each side of the chassis.

2.

Remove screws from the Rails using a #1 Phillips screwdriver:

3.

Locate the thumbscrews on both sides of the chassis.

4.

Loosen the thumbscrews by turning them counterclockwise until they are free of the rail connection:

Caution: Two people are needed to lift and move the (Undefined variable: F2000UserGuide.ProdcutName)chassis. Use care to avoid injury.

5.

Grasp the sheet metal brackets on either side of the front of the chassis and pull the chassis until it is free of the rack-mounted rails and place the system on an ESD-protected surface:

1. Locate the new chassis and unpack it from the box, if necessary.
2. Place the new chassis on an ESD-protected surface next to the failed chassis.

In the next procedure, you will move components from the failed chassis to the new chassis.

To remove components from the failed chassis and install in the new chassis:

1.

Line up the chassis with the rack-mounted rails and slide the chassis into the rack until the it is seated against the rack-mounted rails:

2.

At the front of the chassis, locate the thumbscrews on either side of the chassis.

3.

Tighten the thumbscrews by turning them clockwise until snug:

4.

Further secure the chassis by installing the provided black screws into the bottom holes:

 

 

 

 

1.

From the rear of the chassis, connect the appropriate CAT6A Ethernet cables from the 10 GbE switch to the 10 GbE (port 1) on Controller A and the 10 GbE (port 1) on Controller B:

2.

If the system contains 100 GbE cards, connect the 100 GbE Copper Direct Attach cables to the Ethernet ports in PCIe slot 1 on Controller A and Controller B:

3.

If the system contains 32 Gb FC cards, connect the FC cables to the FC ports in PCIe slot 1 and PCIe slot 3 on Controller A and Controller B (see figure above).

4.

Connect one end of the short CAT6A Ethernet controller-to-controller interconnect Ethernet cable to Port 4 on Controller A and the other side to port 4 on Controller B:

Note: This cable connection is for controller-to-controller communication and must be in place before applying power to the system.

5.

Connect one power cable to PSU A and the other cable to PSU B:

Note: Quantum recommends connecting each power cord to a separate AC circuit to ensure system availability in case of a power failure.\

The system will automatically start up about 20 seconds after power is applied. It will take a few minutes for the system to completely start up.

6.

Loop the retention clips around the power cables and pinch them until the clips catch and lock in place:

7.

Slide the retention clips forward until they stop near the cable connector. Doing this will ensure that the retention clips function properly in the event the cable is yanked:

To verify the system:

1.

Using a CAT6A Ethernet cable, connect a notebook computer to the IPMI/BMC port on Controller A:

2.

Access the BMC Web UI:

3.

On the BMC Web UI, verify that the controller does not report any errors.

4.

Disconnect the CAT6A Ethernet cable from the IPMI/BMC port on Controller A.

5.

Connect the CAT6A Ethernet cable to the IPMI/BMC port on Controller B:

6.

Repeat Step through Step to verify Controller B is functioning properly.

1.

Locate the F2000 bezel:

2.

Attach the bezel to the four mounting posts at the front of the chassis: