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 general diagnostic:
system internal diagnostics run-general-diagnostic
system internal diagnostics run-network-diagnostic
Run the networking diagnostic.
In case of a client connectivity problem, ask the client to repeat their attempt to connect to the FluidFS
cluster 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/
NetworkDiagnostic/
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-network-diagnostic [options]
Arguments
<ClientIP> IP address of
the client
Existing client
IP address in
IPv6 or IPv4
foromat
Argument Description Format
<Protocol> Client protocol Possible values
are SMB,, NFS
<ClientIP> IP address of
the client
Existing client
IP address in
IPv6 or IPv4
format
-
RepositoryType
<RepositoryTyp
e>
Type of
repository on
which to run
diagnostics
RepositoryType
can be
NAS_VOLUME
or FTP. If it is
NAS_VOLUME,
then the values
of
RepositoryVolu
<RepositoryTyp
e>
Type of
repository on
which to run
network
diagnostic
CLI Commands
255