Reference Guide

Argument Description Format
-RepositoryPath
<RepositoryPath>
Path of the repository on which
to run diagnostics
If it is FTP, the diagnostics should
be transferred from the cluster
via ftp under ftp://
(UserName)@(ClusterVIP):44421/
diagnostics/archive/.
Example
Run the client connectivity diagnostic for an SMB client with the IP address 172.22.69.18:
CLI> system internal diagnostics run-client-connectivity-diagnostic
172.22.69.18 SMB
system internal diagnostics run-file-system-diagnostic
Run the core file-system diagnostic.
If the problem occurs only while certain activity is running against the FluidFS cluster, retry after the
diagnostic is run. The diagnostic files should be downloaded by FTP from the following directory:
ftp://<FluidFS_administrator_user_name>@<client_VIP_or_name>:44421/diagnostic/archive/
FileSystemDiagnostic/
NOTE: FTP is enabled by default on the FluidFS cluster. However, if FTP has been disabled, see
system internal security FTP configuration enable to reenable FTP before using this
command.
Format
system internal diagnostics run-file-system-diagnostic
Arguments
Argument Description Format
<ClientIP> IP address of the client Existing client IP address in IPv6
or IPv4 format
<Protocol> Client protocol Possible values are SMB,, NFS
-RepositoryType
<RepositoryType>
Type of repository on which to
run diagnostics
RepositoryType can be
NAS_VOLUME or FTP. If it is
NAS_VOLUME, then the values of
RepositoryVolume and
RepositoryPath determine where
the files will be stored. The files
can then be accessed by a share
or export to the volume.
-RepositoryVolume
<RepositoryVolume>
Volume on the repository on
which to run diagnostics
CLI Commands
253