iSCSI Configuration Troubleshooting

​

• Check the Nexfs logfile for "gfs_jsoniscsiloadconf, failed to parse iSCSI config JSON" error messages indicating the JSON configuration file is not malformed

​​

• Use an online JSON editor such as codebeautify to verify that the configuration file that fails to load is formatted as valid JSON

​

• Check the configuration has been loaded using nexfscli iscsi getconf

​

• View the configuration using tgtadm

​

•  Use iscsiadm to verify that an iSCSI target is available over the expected interface, for example, the following command shows that target 1 is available over the interface at 192.168.178.66:3260

​

# iscsiadm -m discovery -p 192.168.178.66 -t st

192.168.178.66:3260,1 iqn.2021-09.nexfs.com:nexfs01.itarget:1

​

• Using tgtadm check that targets are bound to the expected interfaces

​

• Make sure that the path specified for a LUN exists, Nexfs will automatically remove the configuration for a LUN if the path it points to does not exist

​

• Ensure that you have not included the nexfs fuse mountpoint prefix in the specified LUN path, the integrated iSCSI server has direct access to the nexfs storage pool and is not aware of the fuse mountpoint prefix

​

• Use the forum to ask the nexfs community for help

​

• Contact Nexustorage regarding possible paid per-incident support

​

​

​