Dell PowerVault NX3600 - Manual (Page 244)

8. After the previous command completes, configure the iSCSI IP addresses.
To configure iSCSI IP addresses run the following command:
hardware fabrics iSCSI add
For example:
hardware fabrics iSCSI add eth30 255.255.0.0 192.11.18.10,192.11.18.11
(This adds the first SAN subnet containing all the eth30 ports.)
hardware fabrics iSCSI-portals add-IPv4
For example:
hardware fabrics iSCSI-portals add-IPv4 192.11.18.6 "MD-1"
(This points the FluidFS cluster to the PowerVault iSCSI Control Port.)
9. On the MD system, create the volumes, server objects, and mappings for the FluidFS cluster.
10. Rescan to find the volumes.
hardware storage-subsystem rescan
11. Show the volumes and make sure that you see all of the volumes you expect to see.
hardware storage-subsystem view
12. Create the NAS pool.
hardware storage-subsystem create-NAS-pool
13. After the previous command completes, set the flag to show that the setup completed.
system internal system-configuration-state installation-finished
14. Accept the EULA (End User License Agreement).
system software-updates approve-eula
15. Set the support user password.
system internal security support-access change-password -Password
16. Change the Administrator password.
access-control local-users change-password Administrator -Password
Adding a NAS Appliance to a FluidFS Cluster Using the CLI
Use this procedure to add a NAS appliance to a FluidFS cluster using the CLI. The recommended way to
add a NAS appliance is to use the FluidFS NAS Manager WebUI. This procedure should be performed only
by Dell Technical Support Services.
1. Log on to the CLI of the existing FluidFS cluster (do not log on to the new NAS appliance) as
described on Accessing the CLI.
2. Determine the network ID of the existing client subnets for use in Step 3.
networking subnets list
3. Configure the client VIPs (PrivateIPs) and an IP address for each NAS controller that you are adding
(PublicIPs). Dell recommends adding at least one client VIP per NAS controller.
networking subnets edit -PrivateIPs
PublicIPs
For example:
networking subnets edit 192.10.0.0 255.255.0.0 -PrivateIPs
192.10.18.38,192.10.18.39,192.10.18.40,192.10.18.41 -PublicIPs
192.10.18.42,192.10.18.43
244