This guide will use the wizard to go through the configuration of a SAN. For each SAN required, repeat steps 2 to 5 of the Quick Start Wizard using the data from the initial configuration worksheet.
To view the related video, use the camera on your mobile device to scan this QR code, or click here to be taken to the video on this device.
In the SFSS Web UI, click Quick Start Wizard and in the 1. Modify MTU card, click Edit. This setting applies to all storage interfaces and is only set once.
Change the MTU to match the network settings. The default is 1500.
Note: In this example, the MTU value is set to 9000.
Note: MTU changes are only applied to storage interfaces after they have been applied to a CDC.
After the SFSS has rebooted, reopen the Quick Start wizard, and in the 2. Configure CDC Interface card, click Create/Edit.
To configure the interface, follow the steps below depending on whether SFSS is installed on ESXi or Linux.
For SFSS on ESXi, select an existing Interface and then click Edit. The VM adapters are assigned to the SFSS interfaces in the following order:
Table 37. ESXi Network Adapter to SFSS Interface correlation
ESXi Network Adapter
SFSS Interface
1
ens160 (Management)
2
ens192
3
ens224
4
ens256
5
ens161
6
ens193
7
ens225
8
ens257
9
ens162
10
ens194
In this example, ens192 is used for SAN A. If more than 10 interfaces are required, add a VLAN interface by clicking CREATE. VLAN interfaces are subinterfaces on virtual adapters. When a VLAN interface is created under a parent interface, the parent interface is disabled. To allow multiple VLANs on the Port Group of the parent interface, right click on the port group and then click Edit Settings > Security > Promiscuous Mode > Accept
.
Note: If you are unsure of which interface to configure in the SFSS UI, see the Identifying interfaces in SFSS on ESXi section for instructions on how to locate the interface in vSphere using the MAC address.
For SFSS on Linux, use the interfaces created in the Configure management IP address on SFSS KVM section of this guide. Compare the MAC addresses seen in the SFSS GUI with those in the Linux CLI to identify the bridge interface in SFSS.
Note: In Linux, ens2 was configured via CLI during deployment.
From the Interface Details screen, enter a name in the Name field. This example uses SAN-A in the Name field.
Click Next.
From the IPV4 Configuration screen, select Manual, enter a unique Address for the CDC instance, and a PrefixLength. This example uses 172.18.21.250 and 24.
Note: If any endpoints are not on the same subnet as the CDC interface, add static routes to those endpoints.
Click the Next.
Select an IPV6 configuration and click FINISH.
If using IPv6, configure IP details. Otherwise, disable the interface to avoid unwanted DHCP assignment.
The Quick Start Wizard reopens with a success message.
In the 3. Create CDC Instance card, click Create.
For the first CDC Instance ID, enter 1.
Select the interface created for SAN A. Click CREATE.
Note: This example uses ens192. The Discovery State and CDC State are enabled.
The Quick Start wizard reopens.
In the 4. Discover Endpoints card, click View. The CDC may take a few minutes to initialize after which it will announce its presence on the network. Endpoints capable of automated discovery will appear.
To see registered ESXi and Linux, see the Host tab. For PowerStore, see the Subsystem tab, and for PowerMax, see the DDC tab only. The following example shows ESXi and Linux hosts discovered and registered in the CDC. The following example shows PowerStore subsystems discovered and registered in the CDC. The following example shows a PowerMax DDC discovered and registered in the CDC.
Optionally, verify network connectivity by pinging NVMe/TCP SAN interfaces. Registration will fail if there is a connectivity issue. Endpoints will remain offline if there is an MTU mismatch.
If endpoints have not automatically discovered and registered with the CDC, ensure the following:
Ensure network connectivity has been verified using the steps below.
For endpoints on the same subnet as the CDC, ensure L2 multicast and port 5353 are not blocked on the network.
PowerMax DDCs are not listed in the DDC tab. SFSS supports endpoint registration through push and pull registrations. When the endpoint initiates the registration request with CDC, it is called a push registration. When CDC initiates the registration request, it is called a pull registration. PowerMax uses push registration, the result of which is that the CDC does not manage the DDC.
Ping from the hosts to the CDCs and subsystem interfaces. Specifying the source interface is not necessary as the host's routing table should choose the correct egress interface. The following command applies to ESXi and Linux hosts.
The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Apr 26 10:28:17 2022 /usr/bin/xauth: file /root/.Xauthority does not exist root@sfss:~# ping 172.18.21.191 -s 9000 root@sfss:~# ping 172.18.21.192 -s 9000