Common Operations

This section describes how to perform common operations on the F2000, including configuring and changing configuration settings using the F-Series UI, The BMC Web User Interface (F-Series 1.x software only), or the QCSP/TUI (F-Series 1.x software only).

There are two options to restore power to a powered-off controller, depending on the current state of the controller and chassis power:

  • If the controller was powered off from the QBSP shell:
    1. Walk over to the controller in your facility.
    2. Determine which controller is currently powered off.
    3. Un-seat the controller that is currently powered off:

      4. Note: For this procedure, you do not have to fully remove the controller from the chassis. Move it out of the chassis just enough to unseat it from the midplane of the chassis.

      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:

    4. Re-seat the controller to re-establish power:

      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:

      The controller should power up again.

  • If BOTH controllers were powered down using the QBSP shell power_off command, and/or the power cords are not connected to the PSUs in rear of the chassis, plug in the power cords to the back of the chassis. Both controllers should power up again.

Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

  1. Access the BMC Web UI:

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

    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

    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.

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

    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.

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

    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.

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

      3. The BMC Web UI Power Control page appears:

    1. Select Power On and click Perform Action.

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

    2. Click OK to power on the controller.

      3. The Fault LED on the front of the system and on the rear of the selected controller will not be lit when the controller is powered on. The indicator on the rear of both controllers will be off when they are both powered on (example of rear of the system shows the power indicator on Controller B) and there are no fault conditions indicated:

      Item Description
      1 Power indicator: Green solid – power on
      2 Fault indicator: Off – no faults reported; normal operating condition
      3 Controller B: Off – no faults reported; normal operating condition
  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.

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

      For available commands and usage, type help.

      (IP or hostname)>

  2. Enter the power_off command:
    3. (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.

Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

  1. Access the BMC Web UI:

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

    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

    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.

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

    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.

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

    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.

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

      3. The BMC Web UI Power Control page appears:

    1. Select Power Off and click Perform Action.

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

    2. Click OK to power off the controllers.

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

Use this procedure to update the QBSP 2.x software.

Note: You must be running 2.0.2 or later software to use this process. Prior to 2.0.2, the Update Platform Software link and page was not available in the F-Series UI.

Use this procedure to update your F2000 software if your system HAS an active internet connection.

Note: You will update Controller A from the user interface on Controller B, and update Controller B from the user interface on Controller A.

Quantum recommends you update the system to the latest version of F2000 software. Note the following:

Update the software

  1. Verify which version of software is running on the system.
    1. Log in to the F-Series UI.
    2. Click the 3-dot icon on the upper right-hand corner of the CLUSTER page:

    3. Click About:

    4. View the "About" page and look for the software version currently running on the controllers:

    To update to a newer version the software:

  2. Click CONFIGURATION in the top navigation (item 1 above).
  3. Click Update Platform Software in the left navigation (item 2 above).
  4. Make sure the radio button next to Remote Repository in the Source section is selected (item 3 above).
  5. Click CHECK FOR UPDATE (item 4 above).

    6. You will see a confirmation that the system is checking the online repository for an update:

     

    If the latest version of the software is not currently installed, and an update is available from the online repository, you will see a confirmation that it can be updated, and the update version that is available for download to the system.

    Note: The UPDATE NOW button for the controller you are logged into will be grayed-out and not functional, while the controller you are not logged into will allow you to update it.

    If the latest software is installed, you will see an indication similar to one of the following messages, the UPDATE NOW button is gray (disabled). Skip the remainder of these update steps, since you cannot, and do not need to update the F2000 software.

  6. Click UPDATE NOW for the controller whose user interface you are NOT logged into:

    7. The software will download to the controller, and update the software.

    When the software is being updated, the metadata arrays on both boot drives are recovered. Because of this:

    1. Controller A UI will present degraded and rebuilding drive alert tickets similar to the following:

      2. These types of alerts are expected and can be ignored during the software update, and can be deleted after the update is complete.

    2. The Controller B UI will display degraded RAID device health similar to the following:

      3. The system should return to a healthy state after the software update is complete.

    3. Before the controllers have finished updating the F2000 software and rebuilding drives, you may not be able to log into the UI on either controller.

      4. Wait until the F2000 software update has finished, and log in again.

    Note: It may take up to 20 minutes to download the update file, so be patient while the software downloads.

    The F2000 software will begin the update process. While you will see the following confirmation indicating that the update was successful, it's just confirming that the update is valid and can begin. At this point, the update process is not 100% finished, see note below:

    Note: The update will reboot the controller, and will also require an additional 15-30 more minutes before the update of this controller can be initiated from the other controller's user interface. If you initiate an update before the first controller update is complete, that update will fail and you will see a failure notification.

    Once the update of the other controller is complete, it will take about 10 min for both controllers to sync.

  1. If you have not yet updated the controller you are logged into, launch the user interface of the other controller:

    2. To launch the Controller A user interface, when logged into the Controller B user interface, click this, in the panel for Controller A:

    To launch the Controller B user interface, when logged into the Controller A user interface, click this, in the panel for Controller B:

  2. Log in to the user interface of the other controller:

    1. Enter admin for the user, and the password for the admin user.

      2. Note: The admin user is currently the only user account in the F-Series UI.

    2. Click LOGIN.
  1. Complete steps 6-10 from the other controller to update this controller.

    2. The platform software update is complete.

  2. For F2000 storage configurations that use ATTO ThunderLink and PCIe FC adapters used on macOS clients, upgrade to 3.07MP firmware (released 08/11/2022; file size: 2.8 MB) or a later version for these adapters if you have not already done this. Download and update your macOS client sytems with this or later ATTO firmware before attempting to connect to F2000 storage.

Use this procedure to update your F2000 if your system DOES NOT HAVE an active internet connection.

Quantum recommends you update the system to the latest version of F2000 software. Note the following:

Note: You will update Controller A from the user interface on Controller B, and update Controller B from the user interface on Controller A.

Updates to QBSP 2.0.2 and later software are supported from:

  • F-Series 1.1.6
  • For earlier releases, see F2000 Service-platform Software UpdatesF1000 Service-platform Software Updates
    1. Verify which version of software is running on the system:
      1. Log in to the F-Series UI.
      2. Click the 3-dot icon on the upper right-hand corner of the CLUSTER page:

      3. Click About:

      4. View the "About" page and look for the software version currently running on the controllers:

      Leave your browser open.

      1. Open a browser tab.
      2. Navigate to the online form:

        3. https://mysoftware.quantum.com/forms/f2000

      3. Fill out the form and click Submit to access the software update downloads for your F2000.

      4. After you submit the form, you will receive an email with a link to the update download page for the F2000.

        5. The following is an example of the software download page, (update link highlighted):

        The following is an example of the software download page (conversion link highlighted):

    2. Download the F2000 update file:

      3. The file will be downloaded to the system your browser is running on. For updates from QBSP 2.x software, the file name will be similar to qcsp-2.xx-update.tar.

      Note: Download time depends on the speed of your internet connection, but the file size is about 2 GB.

    3. Transfer the file to both controllers:

      4. SCP the file to the system From the laptop you downloaded the file to, use SCP to copy the file to Controller A and Controller B. Use the management IP address of the controller, the admin user name, and the password for the admin account in the file transfer utility.

      Note: Use either a drag-and-drop SCP or FTP utility (like Transmit or Filezilla for MacOS, or WinSCP or Filezilla for Windows), or a command-line utility (like Terminal for MacOS, or the Windows 10 or later command prompt or PuTTYSCP.exe for Windows) to manually copy the files.

      1. Open a terminal window.
      2. scp the file from your local download location to the /mnt/data/scratch/ directory on Controller A.

        3. Example:

        scp qcsp-2.x-update.tar admin@10.20.223.218:/mnt/data/scratch/

      3. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):

        4. qcsp-2.x-update.tar    80%    651MB    482.0KB/s    05:27 ETA
      1. Open a Windows command prompt.
      2. scp the file from your local download location to the /mnt/data/scratch/ directory on Controller A.

        3. Example:

        C:\Users\<user name>\Downloads>scp qcsp-2.x-update.tar admin@10.20.223.218:/mnt/data/scratch/

      3. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):
        4. qcsp-2.x-update.tar    80%    651MB    482.0KB/s    05:27 ETA

    4. Log in to the F-Series UI:

      1. Enter admin for the user, and the password for the admin user.

        2. Note: The admin user is currently the only user account in the F-Series UI.

      2. Click LOGIN.

    5. From the browser for the F-Series UI on Controller Node A, click CONFIGURATION in the top navigation (item 1 above).
    6. Click Update Platform Software in the left navigation (item 2 above).
    7. Click the radio button next to Local File in the Source section (item 3 above).

    8. Enter the path and the complete file name in the Path field (item 1 above).

      9. Example:

      /mnt/data/scratch/qbsp-2.1.0-Build123-update.tar
    9. Click CHECK FOR UPDATE (item 2 above).
    10. Once the local update file is confirmed, click UPDATE NOW:

      The F2000 software will begin the update process. While you will see the following confirmation indicating that the update was successful, it's just confirming that the update is valid and can begin. At this point, the update process is not 100% finished, see note below:

      Note: The update will reboot the controller, and will also require an additional 15-30 more minutes before the update of this controller can be initiated from the other controller's user interface. If you initiate an update before the first controller update is complete, that update will fail and you will see a failure notification.

      Once the update of the other controller is complete, it will take about 10 min for both controllers to sync.

    1. If you have not yet updated the controller you are logged into, launch the user interface of the other controller:

      2. To launch the Controller A user interface, when logged into the Controller B user interface, click this, in the panel for Controller A:

      To launch the Controller B user interface, when logged into the Controller A user interface, click this, in the panel for Controller B:

    2. Log in to the user interface of the other controller:

      1. Enter admin for the user, and the password for the admin user.

        2. Note: The admin user is currently the only user account in the F-Series UI.

      2. Click LOGIN.

      Additional step is required when using the conversion file ONLY:

    1. Manually copy the file to controller you just updated one more time.
    2. Complete Step 4 through Step 10 to update the other controller.

      3. Wait for the software update to complete.

      When finished updating Controller Node A and Controller Node B, determine if you need to repeat this procedure to update to a more recent version of F2000 software. If your system is now running the latest software available, the F2000 software update is complete.

    3. For F2000 storage configurations that use ATTO ThunderLink and PCIe FC adapters used on macOS clients, upgrade to 3.07MP firmware (released 08/11/2022; file size: 2.8 MB) or a later version for these adapters if you have not already done this. Download and update your macOS client sytems with this or later ATTO firmware before attempting to connect to F2000 storage.

    F-Series 1.x software updates are not supported in the F-Series UI. For F2000 systems, the update from 1.x to QBSP 2.0.2 is a manual process. Contact your Quantum support or your Quantum Service Provider to schedule your update.

    1. Click CONFIGURATION in the top navigation menu.

      Click Management Networks in the left navigation menu:

      2. Fill out the remaining details shown here:

    2. Select Static for the Boot Protocol (item 1 above).
    3. Enter a Hostname for Controller A (item 2 above).
    4. Enter the DNS Domain Name (item 3 above; optional).
    5. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 4 above).
    6. Enter the IPv4 Address for the Controller A management network (item 5 above).
    7. Enter the IP Netmask for the Controller A management network (item 6 above).
    8. Enter the Default IP Gateway for the Controller A management network (item 7 above).
    9. Select Static for the Boot Protocol (item 8 above).
    10. Enter a Hostname for Controller B (item 9 above).
    11. Enter the DNS Domain Name (item 10 above; optional).
    12. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 11 above).
    13. Enter the IPv4 Address for the Controller A management network (item 12 above).
    14. Enter the IP Netmask for the Controller A management network (item 13 above).
    15. Enter the Default IP Gateway for the Controller A management network (item 14 above).
    16. Enter Primary DNS Server, if used (item 15 above; optional).
    17. Click Apply (item 16 above).
    18. Click NEXT (item 16 above) to continue.

      19. Note: There is a SKIP button at the bottom right of this page, if you will configure the management settings later.

    1. Click CONFIGURATION in the top navigation menu.
    2. Click Management Networks in the left navigation menu:

      3. Fill out the remaining details shown here:

    3. Select DHCP for the Boot Protocol (item 1 above).
    4. Enter a Hostname for Controller A (item 2 above).
    5. Enter the DNS Domain Name (item 3 above; optional).
    6. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 4 above).
    7. Select DHCP for the Boot Protocol (item 5 above).
    8. Enter a Hostname for Controller B (item 6 above).
    9. Enter the DNS Domain Name (item 7 above; optional).
    10. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 8 above).

      11. Note: The MAC Address for the controllers is pre-populated in the MAC Address fields, so there is nothing to enter there. These are also listed in the F2000 Customer Site Configuration Data document.

      Save the MAC addresses for both controllers for the management ports, as shown below in green. Note the controller they are assigned to, and set aside for future use.

      1. Copy the MAC addresses for both controllers for the management ports (Port 1) for use in configuring your switch, as shown below in green.

      2. On the DHCP server, register the MAC address for both controllers.

      Note: The last item in these columns is the Interface Name (not configurable), which is the slot/port name of the management connection on the system. m1p1 ("m1" = motherboard Eth connection; "p1" = logical port 1 on the motherboard) is the management connection shown.

    11. Click Apply (item 9 above).

    Caution: Quantum recommends leaving the storage configuration unchanged after initial configuration. ONLY change this if absolutely necessary (such as if settings change within your network ecosystem). The system was optimized during initial configuration for your network and storage environment. You could adversely affect efficiency of the system if these settings are changed incorrectly.

    For iSER configurations, if you will set up your system using a "global pause"-style configuration (and no VLANs) use this method to configure your storage network.

    The F2000 100 GbE model comes with two 100GbE ports on each controller. Because there is one card in each controller, this provides two ports per controller, or a total of four ports per system.

    Note: Quantum recommends (and only supports) configurations with at least two interfaces on each controller, as long as each uses a different subnet. This configuration creates a dual-subnet storage network. If you will using only two ports per controller, connect and configure one port from each card in both controllers. If a single subnet is used, only one interface should be connected and configured, but realize that performance is compromised in this configuration.

    The two ports on each controller's 100 GbE card use a PCIe gen 3 x16 connection to the host server. This connection limits the aggregate throughput of the two ports to a maximum of 16 GB/sec. A single port (i.e., on a single-subnet configuration) is limited (in a 100 Gbps Ethernet) to a maximum of 12.5 GB/sec.

    If you connected 2 cables to the 100 GbE card on each controller when cabling the F2000, then you will need to configure the system with dual subnets.

    1. Select the Dual-subnet option for Controller A (item 1 above).
    2. Enter the IPv4 and Netmask network settings for the first subnet to be used for the storage network for Controller A (items 2-5 above).
    3. Enter the IPv4 and Netmask network settings for the second subnet used for the storage network for Controller A (items 5-7 above).

    4. Select the Dual-subnet option for Controller B (item 8 above).
    5. Enter the IPv4 and Netmask network settings for the first subnet used for the storage network for Controller B (items 9-11 above).
    6. Enter the IPv4 and Netmask network settings for the second subnet used for the storage network for Controller B (items 12-14 above).

      7. When complete, the red bar indicating the required fields for Controller B goes away. The page should look like this when the entries are complete:

    1. Click Next.
    2. Click Apply to confirm your changes.

      3. The F-Series UI log in page will appear. You do not need to log in to the F-Series UI yet.

    3. Disconnect from the configuration port on rear of the F2000 and connect to the StorNext network, if desired.

      4. Note: You can continue system configuration from another location, provided the system is on a network you can connect to. Otherwise, you can continue configuration attached to the rear of the system.

    1. Change your computer's network settings to access the system from within the storage network:
      • For macOS systems, navigate to Apple menu > System Preferences> Network described earlier, select the Ethernet connection, and change the settings as needed in the Configure IPv4 dialog for the network.
      • For Windows systems, open the Adapter settings dialog described earlier, right-click the network connection that corresponds to the Ethernet port on your computer (for example, Ethernet), right-click Properties and change the settings as needed for Internet Protocol Version 4 (TCP/IPv4) for the network.

    If you connected 1 cable to the 100 GbE card on each controller when cabling the F2000, then you will need to configure the system with single subnets.

    1. Select the Single-subnet option for Controller A (step1 above).
    2. Enter the IPv4, Netmask, and MTU (if different from the default; steps 2-4 above) for the storage network .
    3. Select the Single-subnet option for Controller B (step 5 above).
    4. Enter the IPv4, Netmask, and MTU (if different from the default; steps 6-8 above) for the storage network for Controller B.
    1. Click Next.
    2. Click Apply to confirm your changes.

      3. The F-Series UI log in page will appear. You do not need to log in to the F-Series UI yet.

    3. Disconnect from the configuration port on rear of the F2000 and connect to the StorNext network, if desired.

      4. Note: You can continue system configuration from another location, provided the system is on a network you can connect to. Otherwise, you can continue configuration attached to the rear of the system.

    1. Change your computer's network settings to access the system from within the storage network:
      • For macOS systems, navigate to Apple menu > System Preferences> Network described earlier, select the Ethernet connection, and change the settings as needed in the Configure IPv4 dialog for the network.
      • For Windows systems, open the Adapter settings dialog described earlier, right-click the network connection that corresponds to the Ethernet port on your computer (for example, Ethernet), right-click Properties and change the settings as needed for Internet Protocol Version 4 (TCP/IPv4) for the network.
    1. Continue to Common Operations.

    Caution: Quantum recommends leaving the storage configuration unchanged after initial configuration. ONLY change this if absolutely necessary (such as if settings change within your network ecosystem). The system was optimized during initial configuration for your network and storage environment. You could adversely affect efficiency of the system if these settings are changed incorrectly.

    Caution: Once you have configured your system storage, changes to the storage configuration WILL DESTROY DATA in an active storage environment. Make sure you intend to change storage configuration and have backups of ANY CRITICAL DATA prior to making changes, if you have data that you need to keep on the system.

    1. Click CONFIGURATION in the top navigation menu.
    2. Click Storage in the left navigation menu:

    3. See the Storage Page Overview.
    1. Click CONFIGURATIONin the top navigation menu:
    2. Click SNMP in the left navigation menu:

    3. Click the gray (disabled) Enable SNMP toggle. It will turn blue (enabled).
    4. Enter the SNMP Community String. Default value is public.
    5. Enter the SNMP Trap Receiver if needed (optional). Default value is localhost.
    6. Enter the Port for the SNMP Trap Receiver. There is no default port value.
    7. Click Apply to confirm the change.

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    1. Select Miscellaneous in the left navigation menu.
    2. Select the SNMP tab.
    3. Click the gray (disabled) Enable SNMP toggle. It will turn blue (enabled).
    4. Enter the SNMP Community String. Default value is public.
    5. Enter the SNMP Trap Receiver if needed (optional). Default value is localhost.
    6. Enter the Port for the SNMP Trap Receiver. There is no default port value.
    7. Click Apply to confirm the change.
    1. Select Miscellaneous in the left navigation menu.
    2. Select the SNMP tab.
    3. Click the blue (enabled) SNMP toggle. It will turn gray (disabled).
    4. Click Apply to confirm the change.

    Before you begin

    If you don't currently have a CBA (Cloud-Based Analytics) account, you must create one before configuring CBA on your system for this feature to be functional. This is also a pre-requisite for the left navigation menu items under the Cloud-Based Analytics section of the PERFORMANCE page to be functional.

    If you do not already have a CBA account, request an account and verify your F2000 is listed in the CBA portal using these steps:

    1. Go to the CBA portal at https://insight.quantum.com.
    2. Click the "Request an Account" link:

      3. (click image to enlarge)

    3. Enter an Email address, Company name and Serial number for your F2000, then click the checkbox next to the text that states "I'm not a robot":

      4. (click image to enlarge)

    4. Quantum will send an email with a user name and password to log in to the CBA portal.
    5. Verify you can view the information for this F2000 within your solution view on the CBA portal at https://insight.quantum.com.

      6. Note: If your solution includes more than one device (such as additional F2000s or Xcellis Workflow Director systems) and you have already received credentials for one of the systems, you can add another device to your account. Send an email to DL-Insight-Admin@quantum.com with information about your additional systems, and the CBA team will add additional devices to the CBA portal view for your account.

    1. Click CONFIGURATION in the top navigation menu.
    2. Click CBA in the left navigation menu:

      3.  

    3. If disabled, click the gray (disabled) Enable Cloud-Based Analytics toggle:

      4. It will turn blue (enabled).

    4. If you will not configure a TLS/SSL Proxy, or enable remote access support, click APPLY here (as shown above), otherwise continue to the next step.

      5. If you will configure a TLS/SSL Proxy do the following:

    5. If disabled, click the gray (disabled) Enable TLS/SSL Proxy toggle (item 1 above).
    6. Enter an address for the Proxy Server, if using a TLS or SSL proxy (item 2 above).
    7. Enter the Port number for that proxy server (item 3 above).
    8. Enter the Proxy Username for the proxy server (item 4 above).
    9. Enter the Proxy Password for the proxy server (item 5 above).
    10. If you do not wish to provide remote access (remote desktop/SSH) access to the system for remote technical support, click Apply to confirm the change (item 6 above). Otherwise, continue to the next step.

      11. If you will configure remote access support do the following:

    11. If disabled, click the gray (disabled) Enable Remote Access Support toggle (item 1 above).
    12. Select one of the remote access choices provided (item 2 above):

    13. Change the number of hours to allow remote access to this system (0, or "Always" is the default; item 3 above).
    14. Click APPLY when all items on the Cloud-Based Analytics configuration page are complete.

      15. Note: The "TEST CBA CONNECTION" is only available once CBA has been enabled and the settings have been applied. The network connection to CBA will take a couple minutes to apply. Once the configuration has been applied, the "TEST CBA CONNECTION" button will be enabled and you can test the connection to the CBA web page (internet connection and firewall permissions required).

    1. Click CONFIGURATION in the top navigation menu.

    2. Select Miscellaneous in the left navigation menu (item 1 above).
    3. Select the CLOUD-BASED ANALYTICS tab (item 2 above).
    4. Click the gray (disabled) Enable Cloud-Based Analytics toggle (item 3 above). It will turn blue (enabled).
    5. Enter the Proxy Server name for the proxy server, if using an SSL proxy (item 4 above).
    6. Enter the Port number for that proxy server, if using an SSL proxy (item 5 above).
    7. Click Apply to confirm the change (item 6 above).
    1. Click CONFIGURATION in the top navigation menu.
    2. Click CBA in the left navigation menu:

    3. Click the blue (enabled) Enable Cloud-Based Analytics toggle to disable CBA:

    4. It will turn gray (disabled). Click Apply to confirm the change (item 4 above).

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    1. Select Miscellaneous in the left navigation menu (item 1 above).
    2. Select the CLOUD-BASED ANALYTICS tab (item 2 above).
    3. Click the blue (enabled) Enable Cloud-Based Analytics toggle to disable CBA (item 3 above). It will turn gray (disabled).
    4. Click Apply to confirm the change (item 4 above).

      Note: Quantum recommends using an NTP time server for time synchronization across your StorNext environment and hardware components.

    1. Click CONFIGURATION in the top navigation menu.
    2. Click Time in the left navigation menu:

      3. Configure the following settings:

    3. If disabled, click the Enable Network Time Protocol (NTP) slider (item 1 above; the slider will turn blue).
    4. Click Hostname (item 2a above) or IP Address (item 2b above) to enter the network information for your NTP server.
    5. Enter the hostname or IP address for the NTP Server (item 3 above).
    6. Enter the Timezone for the system (item 4 above).

      7. Note: Begin to type the information desired, and you will see similar available options for this setting.

    7. Click APPLY (item 5 above).

    Note: Quantum recommends using an NTP time server for time synchronization across your StorNext environment and hardware components.

    For systems that cannot use an NTP time server, you can configure time and date manually:

    1. Click CONFIGURATION in the top navigation menu.
    2. Click Time in the left navigation menu:

      3. Configure the following settings:

    3. If enabled (blue), click enable Network Time Protocol (NTP) slider (item 1 above; the slider will turn gray).
    4. Enter a Date for the system in the field using the syntax indicated (item 2 above).
    5. Enter a Time for the system in the field using the syntax indicated (item 3 above).
    6. Enter the Timezone for system in the field (item 4 above).

      7. Note: Begin to type the information desired, and you will see similar available options for this setting.

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    This allows you to set an NTP time server for the F2000.

    1. Select Miscellaneous in the left navigation menu (item 1 above).
    2. Select the NTP tab (item 2 above).
    3. Click the gray (disabled) Enable NTP toggle (item 3 above). It will turn blue (enabled).
    4. Enter an NTP Server address (item 4 above).

      5. Example (NTP server name):

      time.nist.gov

      Example (NTP server IP address):

      129.6.15.28

    5. Click Apply to confirm the change (item 5 above).

    Note: Quantum recommends using an NTP time server for time synchronization across your StorNext environment and hardware components.

    1. Click CONFIGURATION in the top navigation menu.
    2. Click Time in the left navigation menu:

    3. Click the blue Enable Network Time Protocol toggle:

      4. It will turn gray (disabled) It will also auto-populate the time currently in use from when NTP was enabled:

    4. Make any necessary changes to the manual date and time settings and click APPLY:

    1. Select Miscellaneous in the left navigation menu (item 1 above).
    2. Select the NTP tab (item 2 above).
    3. Click the blue (enabled) Enable NTP toggle (item 3 above). It will turn gray (disabled).
    4. Click Apply to confirm the change (item 4 above).

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    The BMC Web UI allows you to update the default admin user credentials and create additional users.

    To update the admin user account settings or create a new user:

    1. Access the BMC Web UI:

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click Settings from the left menu.

      3. The Settings page appears:

    3. Click User Management.

      4. The User Management Configuration page appears :

       

    4. Do one of the following:

      5. Click an existing user account card, such as admin, to update an existing account.

      Click an unassigned user card to create a new user account.

      The User Management Configuration page appears:

    5. Enter or update the following user account settings:

      6. Change Password: Select to change or enter a password. Selecting the setting enables the following:

      Password Size: Select either 16 bytes or 20 bytes.

      Password: Enter a new password for the account.

      Confirm: Re-enter the new password for the account to confirm.

      Enable User Access: Click to enable a specific privilege level for the user account.

      Privilege: Select from one of the following privilege levels:

      User

      Administrator

      Operator

      None

      Note: The Administrator privilege level allows the user access to all functions within the BMC Web UI. The other user privilege levels contain limitations to what functions and features can be accessed or configured.

      KVM Access: Enables remote KVM access for the user account.

      VMedia Access: Enables VMedia access for the user account.

      SNMP Access: Enables SNMP access for the user account. Selecting this setting enables the following:

      SNMP Access level: Select either Read Only or Write Only.

      SNMP Authentication Protocol: Select either SHA or MD5.

      SNMP Privacy Protocol: Select either DES or AES.

      Email Format: Select AMI-Format or FixedSubject-Format.

      Email ID: Enter an email ID.

      Existing SSH Key: Displays existing SSH Key.

      Upload SSH Key: Click the folder button to browse to the location of your SSH key file to upload.

    6. Click Save. The system saves the new or updated user account.

    You can now use the new or updated user account.

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    You may need to identify the F2000 when installed in a crowded data center rack. You can do this by turning on the blue Identify LED on the front of the chassis using the BMC Web UI.

    To turn on the blue Identify LED:

    1. Access the BMC Web UI:

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click Server Identify from the navigation menu.

      3. The Server Identify on Host Server page appears:

    3. Do one of the following:

      4. Select UID LED ON to turn on the Identify LED. This turns on the LED indefinitely.

      Select UID LED INTERVAL to turn on the Identify LED for a specific amount of time. Enter the amount of time you want the Identify LED to remain illuminated in the Server Identify Timeout <time> second(s) field. The default time is 15 seconds.

    4. Select Perform Action.

      5. The system displays a dialog window with the message “Are you sure to perform this operation?

    5. Click OK.
    6. Go to the front of the rack where the F2000 is installed and locate the F2000 with the illuminated blue Identify LED:

      7. Item

      LED

      Action

      1

      Identify

      • Off: Chassis is not being identified

      • Blue: Chassis is being identified
    7. If you turned on the Identify LED using the UID LED ON option, turn off the LED by selecting UID LED OFF.

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    If you see a Fault LED illuminated on the front of the F2000 or on the back of the F2000 on a particular controller, you can check the status of the controller sensors for information about a component failure.

    To check the status of controller sensors:

    1. Access the BMC Web UI:

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click Sensor from the navigation menu.

      3. The Server Reading page appears:

    3. Check the state of the components. The example above shows FAN0_STATUS and FAN1_STATUS with a state other than Normal, which indicates a problem with the fans.

    Note: This applies to FSeries 1.x software ONLY. This does not apply to QBSP 2.x software.

    You can view the inventory and status of the CPUs and DIMMs in a controller by viewing the System Inventory page.

    To check the status of controller sensors:

    1. Access the BMC Web UI:

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click System Inventory from the navigation menu.

      3. The System Inventory Information page appears. The Block Diagram view appears by default. There are four DIMMs installed in each controller. Populated DIMM slots are shown in green. CPUs are shown in yellow:

    3. Click on a CPU or DIMM component for more details about the component.
    4. Select Layout View to see the layout of the CPUs and DIMMs in the controller. There are four DIMMs installed in each controller. Populated DIMM slots are shown in green:

    5. Click on a CPU or DIMM component for more details about the component.

     

    If you contact Quantum Technical Support for help, they may request that you download and provide the IPMI Event Log for both F2000 controllers.

    To access and download the IMPI Event Log:

    1. Access the BMC Web UI:

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click Reports and Logs from the navigation menu.
    3. Click IPMI Event Log.

      4. The Event Log page appears:

    4. Use the following filters to filter the log data as needed:

      5. Filter by Date: allows you to select a start and end date for the log data.

      Filter by type: allows you to select All events or a specific type of event to report in the log data.

    5. Click Download Event Logs to download the log file.

      6. The IPMI Event Log will be named SELLog.txt.

    The Audit log can be used to troubleshoot the system by identifying who has accessed the BMC Web UI over a specific period of time. For example, each time a user logs into the BMC Web UI, the system saves the IP address, user account, login date/time, and logout date/time to the log.

    The Audit Log information is only viewable using the BMC Web UI and cannot be downloaded.

    To access and view the Audit Log:

    1. Access the BMC Web UI for a controller.

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

      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

      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.

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

      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.

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

      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.

        2. 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. From the BMC Web UI Dashboard, click Reports and Logs from the navigation menu.

      3. The Audit Log page appears:

    3. Use the Filter by Date to select a start and end date for the log data as necessary.

    If you contact Quantum Technical Support for help, they may request that you download and provide the Support Bundle for both F2000 controllers from the QCSP (Quantum Cloud Storage Platform) TUI.

    You will need the following tools to create and download an F2000 Support Bundle:

    PuTTY (or similar SSH tool)

    WinSCP (or similar tool)

    To create and download the Support Bundle:

    1. Access the QCSP TUI:
      1. On a laptop, open an SSH session to the command line of the controller with a CLI console or a tool like PuTTY (Windows) to the management IP address of the controller.

        2. Example management IP address:

        10.20.85.72

        Example (macOS terminal)

        #ssh root@10.20.85.72

        Example (Windows 10 command prompt)

        c:\>ssh root@10.20.85.72
      2. Log in to the command line:

        Username: root (for tools like PuTTY)

        Password: <password> (default password is "esos")

      3. Launch the Quantum Cloud Storage Platform TUI. Enter:

        4. /usr/local/bin/esos_tui

      The Quantum Cloud Storage Platform TUI screen appears:

    2. Press the i key to display the Interface menu:

    3. Use your Down Arrow key to select Support Bundle and press Enter.

      4. The system displays the Support Bundle screen:

    4. Write down the location of the support bundle.

      5. You need to use WinSCP, or similar tool, to transfer the support bundle file.

    5. Open WinSCP and complete the following fields:

      File protocol: SCP

      Host name: use the management IP address for the controller (Controller A or Controller B)

      User name: root

      Password:(the default password is “esos”. This should have been changed during the installation.

      Example: completed WinSCP Login screen:

    6. Click Login.

      7. Example: WinSCP screen:

    7. In the right pane of the WinSCP screen, click the Parent directory icon to get to the root-level directory folder:

    8. Click the /tmp folder.
    9. Identify the support bundle file. It will have a file name similar to esos_support_pkg-xxxxxxxxxx.tgz:

    10. Right-click on file name and select Download.

      11. The Download window appears:

    11. Browse to a location on your computer to save the file and click OK to transfer the file.

    You will need your F2000 system serial number when you contact Quantum Technical Support. Use one of the following methods to locate the system serial number:

    The system serial number is located on a pull-out tag on the front of the F2000 system on right side. You must remove the front bezel to access the pull-out tab:

    Item

    Component

    1

    Pull-out tag location on the front of the F2000

    The pull-out tag contains a label that includes the system serial number. The system serial number format will be similar to the following example: USWSJ00619OA0044.:

    To locate the system serial number in the F-Series UI:

    1. Click the UI Settings/HelpSystem Options icon (icon with 3 dots) in the upper right-hand corner of the interface:

    2. Click About:

      3. You will see the system Serial Numberserial number on the About page. The serial number is called Product Serial:

    • When a block storage controller is fenced F-Series UI will contain an error message across the top of the page similar to:

    • Determine if the controller is fenced from the CLI, as described here:
      1. On a laptop, open an SSH session to the command line of the controller with a CLI console or a tool like PuTTY (Windows) to the management IP address of the controller.

        2. Example management IP address:

        10.20.85.72

        Example (macOS terminal)

        # ssh root@10.20.85.72

        Example (Windows 10 command prompt)

        c:\>ssh root@10.20.85.72
      2. Log in to the command line:

        Username: root (for tools like PuTTY)

        Password: <password> (default password is "esos")

      1. Run the sbd_list.sh shell script:

        2. [root@F2000-23bf46-2 ~]# sbd_list.sh

        If the system is fenced, you will see results similar to:

        Device '/dev/disk/by-id/nvme-eui.0000000000000005000cca0b01d18a04':
0       f762a2-1        reset	node-f762a2-2
1       f762a2-2        clear

Device '/dev/disk/by-id/nvme-eui.0000000000000005000cca0b01e0ec04':
0       f762a2-1        reset	node-f762a2-2
1       f762a2-2        clear

Device '/dev/disk/by-id/nvme-eui.0000000000000005000cca0b01e0da84':
0       f762a2-1        reset	node-f762a2-2
1       f762a2-2        clear

        If any node is fenced, the state keyword “reset” will be shown in the third column (the second column shows the node names). The fourth column (right-most) shows the node that last wrote to that message block (In the case of the example above, “node-f762a2-2” is fenced).

    If not already connected, log in to the system (go to step 3 if you kept your PuTTY/Terminal session open):

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

      For available commands and usage, type help.

      (IP or hostname)>

    1. Enter:

      2. (IP or hostname)> sbd_unfence

    2. Enter:

      3. (IP or hostname)> cluster_start

    3. Exit the PuTTY/Terminal session:

      4. (IP or hostname)> exit

    If not already connected, log in to the system (go to step 3 if you kept your PuTTY/Terminal session open):

    1. On a laptop, open an SSH session to the command line of the controller with a CLI console or a tool like PuTTY (Windows) to the management IP address of the controller.

      2. Example management IP address:

      10.20.85.72

      Example (macOS terminal)

      # ssh root@10.20.85.72

      Example (Windows 10 command prompt)

      c:\>ssh root@10.20.85.72
    2. Log in to the command line:

      Username: root (for tools like PuTTY)

      Password: <password> (default password is "esos")

    1. Enter:

      2. [root@F2000-23bf46-2 ~]# sbd_unfence.sh

    2. Enter:

      3. [root@F2000-23bf46-2 ~]$ cluster_start.sh

    3. Exit the PuTTY/Terminal session:

      4. [admin@F2000-2 ~]$ exit

    Note: This only applies to F2100 systems that contain Emulex FC target ports.

    For Quantum F2100 Fibre Channel systems that use Emulex FC target adapters, to achieve maximum read I/O performance, Quantum recommends you zone each initiator port with only 1 target port from each controller, and then manually distribute the initiator/target port zoning by hand (such that not all the initiators use the same target ports). Quantum also recommends you keep like-speed initiator ports zoned to one set of target ports (for example, 16 Gb initiator ports are zoned only with target ports A, B, C, D and 32 Gb initiator ports are zoned only with target ports E, F, G, H, etc.) – keeping in mind the 1-to-1 zoning recommendation.