Loading...

Network: Tools

Table of Contents

Verifying Network Connectivity and Performance

You can verify the network connectivity and performance by using the following tools:

Changing the Network Password

The ChangeNetworkPwd tool allows you to change the network password of one or more clients with a stronger password in order to increase the security of your network.

Follow these steps to update the network password:

  1. On the CommServe computer, change to the software installation base directory for the instance to test:

    cd software_installation_path/Base

  2. Run the ChangeNetworkPwd command:

    ChangeNetworkPwd [-listAllWeak | -updateAllWeak | clientName] -vm instance_name

    where:

    • -listAllWeak is the option to list all the clients that need a stronger password.
    • -updateAllWeak is the option to update all the clients in the CommServe instance that need a stronger password.
    • clientName is the name of one client to update the password on.
    • (Optional) -vm is the name of the instance where the CommServe software is running. If not specified, Instance001 is used.

    For example, this command will update the password for client1:

    ChangeNetworkPwd client1 -vm instance002

  3. The password is updated for the client.
  4. To verify the operation, change to the software_installation_path\Log Files folder and review the ChangeNetworkPwd.log file.

Testing Firewall Connectivity

On a remote UNIX client, you can use the cvfwc_ping command to determine whether the CommServe computer can communicate with the client through the client's firewall.

 cvfwc_ping attempts to establish a connection to a remote client computer through the client's firewall.

  1. Change to the base installation directory:

    cd software_installation_path\Base

  2. Run the cvfwc_ping command:
  3. cvfwc_ping [-inst instance_name] [-cn client_name] [-timeout secs] remote_cname remote_host [remote_port]

    Where:

    • (Optional) -inst, together with -cn, specifies the local context (the instance name) of the CommCell program to run. If omitted, the first available instance in the registry, or the content of the GALAXY_INST variable (if set), is used.
    • (Optional) -cn, together with -inst, specifies the local context (the client name) of the CommCell program to run. If omitted, the first available virtual client in the registry, or the content of the GALAXY_CNAME variable (if set), is used.
    • (Optional) -timeout is the number of seconds after which the command stops trying to establish a connection with the remote computer.
    • remote_cname is the remote computer's client name.
    • remote_host is the remote computer's hostname.
    • (Optional) remote_port gives the port to send the request to. If not specified, the request is sent to port 8400.

Example:

cvfwc_ping -inst Instance001 -cn qm10v-ora1 qm10v-cs qm10v-cs.qm.lab 8402

Command return:

  • If a connection to the remote host is successful, the command returns "Successfully connected", and a return code of 0.
  • If the connection fails, the command returns an error message, and a return code of 1.

Collecting Network Diagnostic Data

SnapProtect software provides the CvDiagnostics function for collecting useful troubleshooting data for a SnapProtect instance. You should use CvDiagnostics when the client does not have network connectivity to the CommServe host and sendlog fails to run.

CvDiagnostics Output

The output from CvDiagnostics is a compressed archive file in 7-Zip format. It provides copies of the secure transport certificates, log files and other data for a SnapProtect instance on the computer you are logged on to. You can view the contents of the archive with any tool that supports the .7z archive file format. The log files in the archive can be opened and viewed using GxTail. Bear in mind that these files, even compressed, can be quite large, depending on factors such as how much activity has been logged on your CommServe host, and the data collection options you select.

Available Methods

The software provides two ways to collect this diagnostic data: through the Process Manager, and from the command line. Both methods save the results into a compressed archive file in .7z format, but the Process Manager method, while making it easier to collect the diagnostic data, does not provide some options that the command-line methods provide, such as omitting certificates and logs, and verifying connectivity.

Process Manager Procedure

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Troubleshooting tab.
  4. In the Collect Diagnostic Data area, for Output Folder, click the browse button, , then navigate to the directory where you want to save the diagnostic data archive file. There is no default location, so you cannot proceed without providing this.
  5. Click Collect. A console window opens to show progress. Depending on your particular CommServe instance, collection of the data and production of the archive could take a few minutes.
  6. Click OK to acknowledge and close the Success message.

Windows Command-Line Procedure

  1. Change to the base installation directory:

    cd software_installation_path\Base

  2. Run the CvDiagnostics command:
  3. CvDiagnostics [-h] [-vm instance_name] [-nocertificates] [-nologs] [-r remote_machine_list] -output output_directory

    Where:

    • (Optional) -h displays the command usage information.
    • (Optional) -vm specifies the local context (the instance name) of the CommCell program to run. If you don't specify this option, this is taken from the QiNetixVM file.
    • (Optional) -nocertificates omits the Certificates folder and its contents.
    • (Optional) -nologs omits the Log Files folder and all of its contents. Log files can be very large; use this option when you do not need log contents for troubleshooting.
    • (Optional) -r verifies connectivity between the computer on which the command is run and all the remote clients you specify in remote_machine_list. For remote_machine_list entries:
      • Use each client's fully-qualified domain name or its IP address.
      • (Optional) Add a port number in standard format (client:port). 8400 is used if you don't enter one.
      • Use commas to separate multiple clients, and insert no spaces.
    • -output specifies the folder into which the new diagnostic files archive will be placed. The name for the archive file is CvDiagnostics.7z.

UNIX Command-Line Procedure

  1. Change to the base installation directory:

    cd software_installation_path\Base

  2. Run the CvDiagnostics command:
  3. CvDiagnostics [-h] -vm instance_name [-nocertificates] [-nologs] [-r remote_machine_list] -output output_directory

    Where:

    • (Optional) -h displays the command usage information.
    • -vm specifies the local context (the instance name) of the CommCell program to run.
    • (Optional) -nocertificates omits the Certificates folder and its contents.
    • (Optional) -nologs omits the Log Files folder and all of its contents. Log files can be very large; use this option when you do not need log contents for troubleshooting.
    • (Optional) -r verifies connectivity between the computer on which the command is run and all the remote clients you specify in remote_machine_list. For remote_machine_list entries:
      • Use each client's fully-qualified domain name or its IP address.
      • (Optional) Add a port number in standard format (client:port). 8400 is used if you don't enter one.
      • Use commas to separate multiple clients, and insert no spaces.
    • -output specifies the folder into which the new diagnostic files archive will be placed. The name for the archive file is CvDiagnostics.7z.