F2000 Installation & Configuration

1 – Install the F2000 Hardware

Step 2: Unpack the F2000

Complete the steps in this section to unpack the system and verify that all the components were included in the F2000 box.

Required tools

A set of box cutters is required to complete this procedure.

Unpack the system

Note: Make sure to retain all packing materials, as well as the documentation and other items included in the shipping box. The packaging materials must be used if the system is relocated.

Caution: Two people are needed to lift and move the F2000box. Use care to avoid injury.

To unpack the hardware:

Cut the plastic wrap that surrounds the outer box with a box cutter.

Cut the tape that is holding the box shut.

Open the top of the outer box.

The inside of the box includes two layers of packaging: a top layer that contains the Rail Kit Box and foam protection, and a bottom layer that contains the F2000 chassis. Additional items are tucked into the foam:

Item	Description
1	Rail Kit Box
2	Protective foam (power cables and additional items tucked into the foam).
3	F2000 chassis

Remove the Rail Kit Box.

Open the Rail Kit box and remove the rails and associated hardware. Set them aside.

Remove the protective foam from the top of the chassis.

Locate the F2000 Customer Site Configuration Data document and the Quantum F2000 Getting Started Guide and set them aside.

Remove the bag that contains Quantum bezel and associated hardware. Set the bag aside.

Remove the chassis from the outer box and place on an electrostatic discharge (ESD)-protected surface. The chassis is inside an ESD-safe bag:

10.

Remove the F2000 Customer Site Configuration Data USB Drive located in a USB port in Controller A (top) and set it aside.

11.

Remove the power cables from the protective foam. Set the power cables aside.

12.

Take inventory of all the components that have been unpacked, according to the following:

P	Component	Contents
	Rail Kit box	2 x rack rails. Accessory bag of 6 x black screws. Accessory bag of 8 x silver screw pins.
	F2000 chassis	Chassis with pre-installed PSUs, SSDs;redundant controllers.
	Power cables	2 x C13-C14 8 ft. power cables.
	Serial-to-USB cable	1 x 3.5 mm Serial to USB cable. Not used during the installation but must be kept on-site for maintenance and troubleshooting.
	Quantum bezel	1 x front bezel and 4 mounting post hardware.
	F2000 Customer Site Configuration Data document	1-page document that contains the F2000 MAC addresses and World Wide Port Names (WWPNs).
	F2000Customer Site Configuration Data USB Drive	USB stick installed in Controller A (top) USB port that includes a text file with the F2000 MAC addresses and WWPNs.
	Quantum F2000 Getting Started Guide	1-page, double-sided document that provides a high-level overview on how to get the system up and running.

Step 3: Install the F2000 into a rack

This section describes how to install the F2000 into a rack.

Note: The rails may need to be modified to fit differing types of racks. For example, video racks have round threaded holes and Telco racks have square non-threaded holes.

Required tools

A #2 Phillips screwdriver is required to install Phillips head screws for the rack rails.
A standard flat-head screwdriver is required to install flat head screws for the rack rails

Step 3 Install the Rails into the rack

The F2000 rack rails should be installed into the rack at the lowest possible U height to keep the load on the rack balanced.

To install the rack rails into a rack:

Locate the rack rails and the two bags of hardware that came in the Rail Kit box.
Determine if you will be installing the system in a rack with round holes or square holes:

Round-holed rack: Continue with Step 3.
Square-holed rack: Remove the 8 default silver screw pins from the rack rails and install the 8 larger silver screw pins that came in the accessory bag:

Item	Description
1	8 x large silver screw pins
2	Example silver screw pin location on a rack rail

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:

Identify the right rail, and line up the rail on the bottom 1U of the installation location.
Insert the rail’s silver screw pins into the round or square holes in rear rack post:

Item	Description
1	Silver screw pins inserted into rear rack post
2	Rear rack post

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

Align the front rail attachment with the same 1U space as the rear rail attachment.
Slide the front rail attachment to fit snugly up against the front rack post:

Insert the rail’s silver screw pins into the round or square holes in front rack post:

Item	Description
1	Silver screw pins inserted into front rack post
2	Front rack post

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

Using a #1 Phillips screwdriver, secure the rear rail attachment to the rack post using two black screws.
Repeat Step 3 through Step 11 to install the left rail.

Step 4: Cable the F2000

This section describes how to cable the F2000. Power cables and the CAT6A controller-to-controller Ethernet cable are provided with the F2000. Other cables, such as the 100 GbE Copper Direct Attach cables and FC cables, need to be available for the installation. These can be purchased separately or from Quantum.

Required tools

No tools are required to complete this procedure.

Cable the system

From the rear of the chassis, cable the F2000 by doing the following:

Verify the controller-to-controller interconnect cable is in place as shown below and push in the cable to ensure it is seated correctly. One end of the cable should be plugged in to Port 4 on Controller A and the other side to port 4 on Controller B:

Connect a CAT6A Ethernet cable to port 1 on Controller A (top):
Connect a second CAT6A Ethernet cable to port 1 on Controller B (bottom)

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

Connect the end of each CAT6A Ethernet cable to a network switch. This connection is for StorNext management of the system. It is not used for data traffic.

For FC models:

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 Controller A (top):

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

Connect the other end of up to 8 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 F2000. If connecting only 4 FC cables to the F2000, make sure to connect 1 cable to each FC card. At a minimum, at least 1 FC cable must be connected to Controller A (top) and 1 FC cable must be connected to Controller A (top) for the system to function properly.

For 100 GbE models:

Connect 2 customer-provided 100 GbE Copper Direct Attach cables to the 2 Ethernet ports in PCIe slot 1 in Controller A (top), and connect 2 customer-provided 100 GbE Copper Direct Attach cables to the 2 Ethernet ports in PCIe slot 1 in Controller B (bottom):

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

Connect the other end of the 100 GbE Copper Direct Attach cables to a 100 GbE network switch.

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

Find the two Quantum-provided power cables.
Connect one power cable to PSU A and the other cable to PSU B. Use the attached straps to secure the power cords to the chassis:

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

Connect the other end of the power cables to a primary and secondary AC power source.

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.

Locate the Quantum bezel and mounting post hardware that you previously set aside:

Secure the four mounting posts to the front of the F2000 chassis by hand tightening the two long mounting posts to the top two holes on each side of the chassis and the two short mounting posts to the bottom two holes on each side of the chassis:

Item	Description
1	Long mounting posts
2	Short mounting posts

Attach the Bezel to the four mounting posts at the front of the chassis.

3 – Configure the F2000

Step 1: Connect to the F2000

Connect to the configuration port on Controller A.

Using an Ethernet cable, connect the Ethernet port on a notebook computer to the configuration port (port 2) on Controller A (top):

Item	Description
1	Configuration port (port 2) on Controller A (top)

Enter IP address and subnet values for the connection using one of the following methods:

Step 2 (option 1): Configure Fibre Channel networks

Open a browser and navigate to the initial system configuration interface URL:
http://192.168.17.21/
The EULA (end-user license agreement) displays:
(click image to enlarge)
Installation steps:
There are 5 configuration steps for ethernet models: 1.) Approve License Agreement, 2.) Change Password, 3.) Configure Management Network, 4.) Configure Storage Network, and 5.) Confirm Settings:
Click AGREE to accept the EULA.
Enter a password for both New Password and Confirm Password.

(click image to enlarge)

Pro Tips!

Pro Tip #1: What rules are there for entering passwords?

There are rules around what can and cannot use when setting up your passwords. Password rules include:

Words you cannot use:
- "password" – upper, lower, or mixed case is not allowed
- "admin" – upper, lower, or mixed case is not allowed

Pro Tip #2: Can I see the passwords I just entered to verify what I typed before continuing?

Yes you can. Click the show/hide icon in the New Password and Confirm Password fields to verify the passwords you entered. If the passwords do not match, the NEXT option is not enabled, and you cannot proceed to the next step in the Setup Wizard until they both match.

In the example below, the Confirm Password show/hide icon was clicked, revealing the password. Since the New Password show/hide icon was not clicked, that password remains hidden:

Note: This password will be used for the root user account to access the F-Series UI.

Click NEXT to accept the password changes.
Configure the management IP addresses, depending on the boot protocol network type desired.
Option 1: Configure the system to use static IP addresses for the management network
1. Select Static for the Boot Protocol (item 1 above).
2. Enter a Hostname for Controller A (item 2 above).
3. Enter the DNS Domain Name (item 3 above; optional).
4. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 4 above).
5. Enter the IPv4 Address for the Controller A management network (item 5 above).
6. Enter the IP Netmask for the Controller A management network (item 6 above).
7. Enter the Default IP Gateway for the Controller A management network (item 7 above).
8. Select Static for the Boot Protocol (item 8 above).
9. Enter a Hostname for Controller B (item 9 above).
10. Enter the DNS Domain Name (item 10 above; optional).
11. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 11 above).
12. Enter the IPv4 Address for the Controller A management network (item 12 above).
13. Enter the IP Netmask for the Controller A management network (item 13 above).
14. Enter the Default IP Gateway for the Controller A management network (item 14 above).
15. Enter Primary DNS Server, if used (item 15 above; optional).
16. Click NEXT (item 16 above) to continue.
Option 2: Configure the system to use DHCP IP addresses for the management network

Click APPLY.

You will see the following F-Series UI feedback of configuration update progress:

You will see a note at the top of the screen, informing you that the settings will be applied to the system, and take approximately 60 seconds to complete:

For DHCP management network configurations, you will also see a note at the top of the screen informing you that DHCP configuration is in process, and to check the DHCP server in order to determine the IP addresses assigned to the system:

For Static management network configurations, you will see a note that the configuration has been successful:

For DHCP management network configurations, after the configuration settings have successfully been applied to the F2000, you will see a note at the top of the screen, informing you of this and a reminder to check the DHCP server in order to determine the IP addresses assigned to the system:

For DHCP configurations, determine DHCP IP addresses assigned to the system:
To determine the management IP addresses assigned by DHCP
You have three options (listed here from easiest to most difficult to perform) to determine the DHCP server-assigned IP addresses for the management ports:
(Option 1) Determine the DCHP addresses from the F2000's configuration/service port:
Since your network cable is already attached to the server's configuration/service port, open an ssh session using Terminal (on macOS), or Command Prompt (cmd.exe) or PuTTY (on Windows), and log in to the controller as the admin user and the password you just set for the admin user:
On a laptop, open a direct SSH or PuTTY connection to the controller's QBSP (Quantum Block Storage Platform) command line using the admin account and the management IP address or hostname.
Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):
#ssh admin@192.168.17.21
Enter "yes" to accept the ECDSA security key for this system connection when prompted:
The authenticity of host '192.168.17.21' 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 addding the security key to the list of known hosts.
Warning: Permanently added '192.168.17.21' (ECDSA) to the list of known hosts.
Enter the user name for the admin account you set during system configuration:
admin@192.168.17.21's password:
You should see the system connect to the CLI prompt for the system you connected to:
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.
192.168.17.21>
Enter the show_info command to see the currently assigned management IPv4 address on the controller:
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
To see the DHCP address assigned to Controller B, connect the network cable to the configuration port on Controller B:

Repeat the above steps for the other controller.
(Option 2) Determine the DCHP addresses from the DHCP server:
Retrieve the MAC addresses you set aside earlier (see Save the MAC addresses for later use in determining the DHCP-assigned IP addresses).
Log into the DHCP server.
Match the MAC address values you set aside with the IP addresses shown for those same MAC addresses on the DHCP server.
(Option 3) Determine the DCHP addresses from the F2000 using BMC or a crash cart:
Log in to one of the controllers using a physical console (via the BMC port [see the pullout tab on the system for the BMC username and password] or a crash cart attached to the USB and VGA ports on the system) as the admin user and the password you just set for the admin user.
Enter the command to see the currently assigned management IPv4 address on the controller:
show_info
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
Repeat these steps for the other controller.

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

Disconnect from the configuration port on rear of the F2000 and connect to the StorNext network.

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.

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.

Click Apply to confirm settings, then continue to Step 3: Verify IP addresses are functional.

Step 2 (option 2): Configure dedicated ethernet networks

Open a browser and navigate to the initial system configuration interface URL:
http://192.168.17.21/
The EULA (end-user license agreement) displays:
(click image to enlarge)
Installation steps:
There are 5 configuration steps for ethernet models: 1.) Approve License Agreement, 2.) Change Password, 3.) Configure Management Network, 4.) Configure Storage Network, and 5.) Confirm Settings:
Click AGREE to accept the EULA.
Enter a password for both New Password and Confirm Password.

(click image to enlarge)

Pro Tips!

Pro Tip #1: What rules are there for entering passwords?

There are rules around what can and cannot use when setting up your passwords. Password rules include:

Words you cannot use:
- "password" – upper, lower, or mixed case is not allowed
- "admin" – upper, lower, or mixed case is not allowed

Pro Tip #2: Can I see the passwords I just entered to verify what I typed before continuing?

In the example below, the Confirm Password show/hide icon was clicked, revealing the password. Since the New Password show/hide icon was not clicked, that password remains hidden:

Note: This password will be used for the root user account to access the F-Series UI.

Click NEXT to accept the password changes.
Configure the management IP addresses, depending on the boot protocol network type desired.
Option 1: Configure the system to use static IP addresses for the management network
1. Select Static for the Boot Protocol (item 1 above).
2. Enter a Hostname for Controller A (item 2 above).
3. Enter the DNS Domain Name (item 3 above; optional).
4. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 4 above).
5. Enter the IPv4 Address for the Controller A management network (item 5 above).
6. Enter the IP Netmask for the Controller A management network (item 6 above).
7. Enter the Default IP Gateway for the Controller A management network (item 7 above).
8. Select Static for the Boot Protocol (item 8 above).
9. Enter a Hostname for Controller B (item 9 above).
10. Enter the DNS Domain Name (item 10 above; optional).
11. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 11 above).
12. Enter the IPv4 Address for the Controller A management network (item 12 above).
13. Enter the IP Netmask for the Controller A management network (item 13 above).
14. Enter the Default IP Gateway for the Controller A management network (item 14 above).
15. Enter Primary DNS Server, if used (item 15 above; optional).
16. Click NEXT (item 16 above) to continue.
Option 2: Configure the system to use DHCP IP addresses for the management network

Click APPLY.

You will see the following F-Series UI feedback of configuration update progress:

You will see a note at the top of the screen, informing you that the settings will be applied to the system, and take approximately 60 seconds to complete:

For DHCP management network configurations, you will also see a note at the top of the screen informing you that DHCP configuration is in process, and to check the DHCP server in order to determine the IP addresses assigned to the system:

For Static management network configurations, you will see a note that the configuration has been successful:

For DHCP configurations, determine DHCP IP addresses assigned to the system:
To determine the management IP addresses assigned by DHCP
You have three options (listed here from easiest to most difficult to perform) to determine the DHCP server-assigned IP addresses for the management ports:
(Option 1) Determine the DCHP addresses from the F2000's configuration/service port:
Since your network cable is already attached to the server's configuration/service port, open an ssh session using Terminal (on macOS), or Command Prompt (cmd.exe) or PuTTY (on Windows), and log in to the controller as the admin user and the password you just set for the admin user:
On a laptop, open a direct SSH or PuTTY connection to the controller's QBSP (Quantum Block Storage Platform) command line using the admin account and the management IP address or hostname.
Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):
#ssh admin@192.168.17.21
Enter "yes" to accept the ECDSA security key for this system connection when prompted:
The authenticity of host '192.168.17.21' 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 addding the security key to the list of known hosts.
Warning: Permanently added '192.168.17.21' (ECDSA) to the list of known hosts.
Enter the user name for the admin account you set during system configuration:
admin@192.168.17.21's password:
You should see the system connect to the CLI prompt for the system you connected to:
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.
192.168.17.21>
Enter the show_info command to see the currently assigned management IPv4 address on the controller:
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
To see the DHCP address assigned to Controller B, connect the network cable to the configuration port on Controller B:

Repeat the above steps for the other controller.
(Option 2) Determine the DCHP addresses from the DHCP server:
Retrieve the MAC addresses you set aside earlier (see Save the MAC addresses for later use in determining the DHCP-assigned IP addresses).
Log into the DHCP server.
Match the MAC address values you set aside with the IP addresses shown for those same MAC addresses on the DHCP server.
(Option 3) Determine the DCHP addresses from the F2000 using BMC or a crash cart:
Log in to one of the controllers using a physical console (via the BMC port [see the pullout tab on the system for the BMC username and password] or a crash cart attached to the USB and VGA ports on the system) as the admin user and the password you just set for the admin user.
Enter the command to see the currently assigned management IPv4 address on the controller:
show_info
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
Repeat these steps for the other controller.

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

Disconnect from the configuration port on rear of the F2000 and connect to the StorNext network.

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.

Configure the dedicated Storage network:
Configure a dedicated storage network
The F2000 100 GbE model comes with two 100GbE ports on each controller. The recommended (and only supported) configuration for using all ports is to establish a dual-subnet storage network. If a single subnet is used, only one interface should be connected and configured.

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 those two ports to a maximum of 16 GB/sec. A single port (i.e., on a single-subnet configuration) is limited (by 100 Gbps Ethernet) to a maximum of 12.5 GB/sec.
Option 1: Configure a dedicated ethernet storage network with dual subnets
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.

Select the Dual-subnet option for Controller A (item 1 above).

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

Enter the IPv4 and Netmask network settings for the second subnet used for the storage network for Controller A (items 5-7 above).

Select the Dual-subnet option for Controller B (item 8 above).

Enter the IPv4 and Netmask network settings for the first subnet used for the storage network for Controller B (items 9-11 above).

Enter the IPv4 and Netmask network settings for the second subnet used for the storage network for Controller B (items 12-14 above).

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:

Click Next.

Click Apply to confirm your changes.

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

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

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.

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.
Option 2: Configure a dedicated ethernet storage network with a single subnet
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.

Select the Single-subnet option for Controller A (step1 above).

Enter the IPv4, Netmask, and MTU (if different from the default; steps 2-4 above) for the storage network .

Select the Single-subnet option for Controller B (step 5 above).

Enter the IPv4, Netmask, and MTU (if different from the default; steps 6-8 above) for the storage network for Controller B.

Click Next.

Click Apply to confirm your changes.

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

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

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.

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.

Continue to Step 3: Verify IP addresses are functional.

Step 2 (option 3): Configure converged/VLAN ethernet networks

Open a browser and navigate to the initial system configuration interface URL:
http://192.168.17.21/
The EULA (end-user license agreement) displays:
(click image to enlarge)
Installation steps:
There are 5 configuration steps for ethernet models: 1.) Approve License Agreement, 2.) Change Password, 3.) Configure Management Network, 4.) Configure Storage Network, and 5.) Confirm Settings:
Click AGREE to accept the EULA.
Enter a password for both New Password and Confirm Password.

(click image to enlarge)

Pro Tips!

Pro Tip #1: What rules are there for entering passwords?

There are rules around what can and cannot use when setting up your passwords. Password rules include:

Words you cannot use:
- "password" – upper, lower, or mixed case is not allowed
- "admin" – upper, lower, or mixed case is not allowed

Pro Tip #2: Can I see the passwords I just entered to verify what I typed before continuing?

In the example below, the Confirm Password show/hide icon was clicked, revealing the password. Since the New Password show/hide icon was not clicked, that password remains hidden:

Note: This password will be used for the root user account to access the F-Series UI.

Click NEXT to accept the password changes.
Configure the management IP addresses, depending on the boot protocol network type desired.
Option 1: Configure the system to use static IP addresses for the management network
1. Select Static for the Boot Protocol (item 1 above).
2. Enter a Hostname for Controller A (item 2 above).
3. Enter the DNS Domain Name (item 3 above; optional).
4. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 4 above).
5. Enter the IPv4 Address for the Controller A management network (item 5 above).
6. Enter the IP Netmask for the Controller A management network (item 6 above).
7. Enter the Default IP Gateway for the Controller A management network (item 7 above).
8. Select Static for the Boot Protocol (item 8 above).
9. Enter a Hostname for Controller B (item 9 above).
10. Enter the DNS Domain Name (item 10 above; optional).
11. Select a Maximum Transfer Unit (MTU) to use for the network (default is 1500; item 11 above).
12. Enter the IPv4 Address for the Controller A management network (item 12 above).
13. Enter the IP Netmask for the Controller A management network (item 13 above).
14. Enter the Default IP Gateway for the Controller A management network (item 14 above).
15. Enter Primary DNS Server, if used (item 15 above; optional).
16. Click NEXT (item 16 above) to continue.
Option 2: Configure the system to use DHCP IP addresses for the management network

Click APPLY.

You will see the following F-Series UI feedback of configuration update progress:

You will see a note at the top of the screen, informing you that the settings will be applied to the system, and take approximately 60 seconds to complete:

For DHCP management network configurations, you will also see a note at the top of the screen informing you that DHCP configuration is in process, and to check the DHCP server in order to determine the IP addresses assigned to the system:

For Static management network configurations, you will see a note that the configuration has been successful:

For DHCP configurations, determine DHCP IP addresses assigned to the system:
To determine the management IP addresses assigned by DHCP
You have three options (listed here from easiest to most difficult to perform) to determine the DHCP server-assigned IP addresses for the management ports:
(Option 1) Determine the DCHP addresses from the F2000's configuration/service port:
Since your network cable is already attached to the server's configuration/service port, open an ssh session using Terminal (on macOS), or Command Prompt (cmd.exe) or PuTTY (on Windows), and log in to the controller as the admin user and the password you just set for the admin user:
On a laptop, open a direct SSH or PuTTY connection to the controller's QBSP (Quantum Block Storage Platform) command line using the admin account and the management IP address or hostname.
Example (macOS Terminal, Linux or Unix command line, or Windows 10 command prompt):
#ssh admin@192.168.17.21
Enter "yes" to accept the ECDSA security key for this system connection when prompted:
The authenticity of host '192.168.17.21' 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 addding the security key to the list of known hosts.
Warning: Permanently added '192.168.17.21' (ECDSA) to the list of known hosts.
Enter the user name for the admin account you set during system configuration:
admin@192.168.17.21's password:
You should see the system connect to the CLI prompt for the system you connected to:
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.
192.168.17.21>
Enter the show_info command to see the currently assigned management IPv4 address on the controller:
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
To see the DHCP address assigned to Controller B, connect the network cable to the configuration port on Controller B:

Repeat the above steps for the other controller.
(Option 2) Determine the DCHP addresses from the DHCP server:
Retrieve the MAC addresses you set aside earlier (see Save the MAC addresses for later use in determining the DHCP-assigned IP addresses).
Log into the DHCP server.
Match the MAC address values you set aside with the IP addresses shown for those same MAC addresses on the DHCP server.
(Option 3) Determine the DCHP addresses from the F2000 using BMC or a crash cart:
Log in to one of the controllers using a physical console (via the BMC port [see the pullout tab on the system for the BMC username and password] or a crash cart attached to the USB and VGA ports on the system) as the admin user and the password you just set for the admin user.
Enter the command to see the currently assigned management IPv4 address on the controller:
show_info
The output includes the "Management IP" address assigned to this controller (shown in green for clarity):
f21-e5-a> show_info (HostOS): Management IP: 10.65.184.225 (HostOS): ClusterNet IP: 10.17.21.197 : BMC/IPMI IP: 10.65.164.130 Product Name=F2100 Serial Number=F1023CTH102AN0A900A Product Part Number=P2522 BuildDate=Wed Mar 2 19:52:51 CST 2022 VSVersion=2.0.0-Build89 BuildVSVersion=2.0.0-Build77 kernel=5.4.145-esos.prod InstallDate=Thu Mar 3 22:01:44 UTC 2022 HostOS=2.0.0-Build89 Memory Size=192 GB CPU Cores=40 Threads per core=2 CPU Model=Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz f21-e5-a>
Repeat these steps for the other controller.

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

Disconnect from the configuration port on rear of the F2000 and connect to the StorNext network.

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.

Select the Disable option (as shown above).

Click Next.
Click Apply to confirm your changes.

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

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

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.

Configure a converged/VLAN storage network

The F2000 100 GbE model comes with two 100GbE ports on each controller. The recommended (and only supported) configuration for using all ports is to establish a dual-subnet storage network. If a single subnet is used, only one interface should be connected and configured.

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 those two ports to a maximum of 16 GB/sec. A single port (i.e., on a single-subnet configuration) is limited (by 100 Gbps Ethernet) to a maximum of 12.5 GB/sec.

This section includes steps to configure for networks that will not be a 100% dedicated storage network. This is a complex configuration involving many additional steps, and is not supported by the F-Series UI, but rather requires manual configuration using more than one CLI (command-line interface).

Step A: Configure 100 GbE network IP addresses on both controllers

Once IPv4 addresses on a lossless channel have been established, iSCSI access to the F2000 must be enabled:

As manufactured, three IQNs are predefined per controller, one for SCSI command forwarding (i.e., non-optimal path), two for array access (one for each port). The former must not be changed; the latter must be bound to the chosen IP addresses.
Configuration must be done from the command line of the system.

For each controller, change the configuration of the iSCSI target driver:

Directly access the F2000 command line

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.

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

Log in to the command line:
Username: root (for tools like PuTTY)
Password: <password> (default password is "esos")

Edit the /etc/scst.conf file using vi:
Use vi to open the /etc/scst.conf file. Enter:
# vi /etc/scst.conf
Search for allowed_portal. Enter:
/allowed_portal

The section will look similar to the following. The IP address you will change in the next step is marked in bold green text:

Note: DO NOT change the allowed_portal for the 10.17.17.198 IP address. This is an internal addressed used by the controller, and SHOULD NOT be changed.

Note: Example shows LUNs 0-15. Only LUNs 0 and 1 would be displayed for 2 LUN systems; LUNs 2-15 would only be included for 16 LUN systems. As of the F2000 v1.1.5 release, new systems are pre-configured with 2 LUNs ONLY. Systems were pre-configured with 16 LUNs F2000 v1.1.2 or earlier.

...
TARGET_DRIVER iscsi {
        enabled 1

        TARGET internal_redirect {
                allowed_portal 10.17.21.198
                enabled 1
                forwarding 1
                rel_tgt_id 6

                GROUP all_devices {
                        LUN 0 dummy_dev
                        LUN 1 F2000_a4c778_08
                        LUN 2 F2000_a4c778_16
                        LUN 3 F2000_a4c778_06
                        LUN 4 F2000_a4c778_14
                        LUN 5 F2000_a4c778_04
                        LUN 6 F2000_a4c778_12
                        LUN 7 F2000_a4c778_02
                        LUN 8 F2000_a4c778_10

                        INITIATOR iqn.2005-03.org.open-iscsi:cdf0995d82a5
                }
        }

        TARGET iqn.2019-09.esos.node-a4c778-1:2d8f4 {
                QueuedCommands 128
                allowed_portal 192.168.1.50
                enabled 1
                rel_tgt_id 5

                GROUP default {
                        LUN 0 F2000_a4c778_01
                        LUN 1 F2000_a4c778_02
                        LUN 2 F2000_a4c778_03
                        LUN 3 F2000_a4c778_04
                        LUN 4 F2000_a4c778_05
                        LUN 5 F2000_a4c778_06
                        LUN 6 F2000_a4c778_07
                        LUN 7 F2000_a4c778_08
                        LUN 8 F2000_a4c778_09
                        LUN 9 F2000_a4c778_10
                        LUN 10 F2000_a4c778_11
                        LUN 11 F2000_a4c778_12
                        LUN 12 F2000_a4c778_13
                        LUN 13 F2000_a4c778_14
                        LUN 14 F2000_a4c778_15
                        LUN 15 F2000_a4c778_16

                        INITIATOR *
                }
        }

Use the Down Arrow key to move the cursor to the IPv4 address next to the second allowed_portal in this section, shown in green above.
Type i to enter the vi "INSERT" mode.
Position your cursor and change the IP to the IPv4 address to be used for the storage network. Example: 192.168.1.100.

Note: You can use the Up Arrow, Down Arrow, Right Arrow, and Left Arrow key to move the cursor as needed.

Type ESC to exit the vi "INSERT" mode.
Search for allowed_portal again by entering the following:
/allowed_portal

The section will look similar to the following. The IP address you will change in the next step is marked in bold green text:

...
        TARGET iqn.2019-09.esos.node-a4c778-1:af15d {
                QueuedCommands 128
                allowed_portal 192.168.2.51
                enabled 1
                rel_tgt_id 4

                GROUP default {
                        LUN 0 F2000_a4c778_01
                        LUN 1 F2000_a4c778_02
                        LUN 2 F2000_a4c778_03
                        LUN 3 F2000_a4c778_04
                        LUN 4 F2000_a4c778_05
                        LUN 5 F2000_a4c778_06
                        LUN 6 F2000_a4c778_07
                        LUN 7 F2000_a4c778_08
                        LUN 8 F2000_a4c778_09
                        LUN 9 F2000_a4c778_10
                        LUN 10 F2000_a4c778_11
                        LUN 11 F2000_a4c778_12
                        LUN 12 F2000_a4c778_13
                        LUN 13 F2000_a4c778_14
                        LUN 14 F2000_a4c778_15
                        LUN 15 F2000_a4c778_16

                        INITIATOR *
                }
        }
}

...

Use the Down Arrow key to move the cursor to the end of the “devices” section.
Type i to enter the vi "INSERT" mode.
Position your cursor and change the IP to the IPv4 address to be used for the storage network. Example: 192.168.2.100.

Note: You can use the Up Arrow, Down Arrow, Right Arrow, and Left Arrow key to move the cursor as needed.

Press ESC to exit INSERT mode.
Enter the following to save the file:
:wq!
Update the F2000 configuration. Enter:
# conf_sync.sh
Make the new F2000 configuration active. Enter:
# scstadmin -config /etc/scst.conf
Open a second SSH command line session for Controller B, and complete all the above steps to change the IPv4 addresses for Controller B.