Reference Guide

4. Repeat Step 3 for additional client subnets.
For example:
networking subnets edit 10.10.76.0 255.255.252.0 -PrivateIPs
10.10.78.121,10.10.78.122,10.10.78.123,10.10.78.124 -PublicIPs
10.10.78.125,10.10.78.126
5. (iSCSI only) Configure additional IP addresses for the iSCSI SAN subnets.
hardware fabrics iscsi edit <name> -ControllersIPs <x.x.x.x>
For example:
hardware fabrics iscsi edit SANb -ControllersIPs
192.11.18.14,192.11.18.15,192.11.18.16,192.11.18.17
hardware fabrics iscsi edit SAN -ControllersIps
192.11.18.10,192.11.18.11,192.11.18.12,192.11.18.13
6. Add the NAS appliance.
hardware nas-appliances add-appliance <ApplianceServiceTag>
For example:
hardware nas-appliances add-appliance L846185
7. For iSCSI, the IQNs will have FluidFS NasControllerX in the name.
8. In the output of the following command, make sure Luns Accessibility shows Optimal from all NAS
controllers to all NAS volumes.
hardware storage-subsystem view
9. Perform an incremental format and join the new NAS appliance to the FluidFS cluster.
hardware nas-appliances join-appliance <ApplianceID>
For example:
hardware nas-appliances join-appliance 2
10. After the previous command completes, confirm that the NAS appliance Status is Optimal in the
output of the following command.
hardware nas-appliances status-list
245