Post-Deployment Tasks

1. Using the CLI on your system, execute the following command to mute mintd:

   /opt/quantum/mintd/mintd_control.py set --volume mute

2. Execute the following command to re-enable stats:

   /opt/quantum/mintd/mintd_control.py set --volume max

1. Execute the following command to disable mintd temporarily:

   /opt/quantum/python27/bin/supervisorctl stop mintd

2. Edit the following configuration file to turn the volume of mintd to mute. Add (or change) the volume key under the [graphite] section and set it to mute.

   /opt/quantum/mintd/etc/mintd.cfg

3. Execute the following command to enable mintd:

   /opt/quantum/python27/bin/supervisorctl start mintd

   Note: This setting persists until you change it manually either by reversing these steps, or by a feature in StorNext Connect that is not implemented yet.

1. Launch the Discover Components application.
   1. Click the Hamburger icon.
   2. Click Discover Components. The Discover page appears.
2. Click Add or update Connectors.
3. Review information in the Connector release and Connector action columns for each client to determine whether there are clients running outdated Connector versions.
4. Use the Connector action column to update the Connector on clients running outdated versions.
5. Follow the on-screen instructions to complete the action.
6. Repeat for all clients that need the Connector updated.
7. Return to the Discover Components application home page.
8. Click Rediscover to update system information.

1. In StorNext Connect:
   1. Click the Hamburger icon.
   2. Click Discover Components. The Discover page appears.
2. Click Add or update Connectors at the top of the screen to display the Discover > List Connectors page.
3. To install the Connector, perform one of the following:
   Install the Connector on a client system in the workspace (cluster)

   • Click the install link in the Connector action column for the client.

     Note: If you are not able to edit the IP address, then install the Connector using the step outlined in Install the Connector on a new client system.

   Install the Connector on a new client system

   • Click the Add a new host link.

     Note: This page provides instructions on how to install the Connector, add the clients (referred to as "hosts"), and mount volumes. The page instructions are not be visible after the "Install the Connector" step is complete. You should copy and paste these instructions in a file for reference.

4. Follow the on-screen instructions to install the Connector.

   

   Additional information

   • If DNS is not configured, use IP addresses—not hostnames—to identify clients.
   • If the environment comprises of StorNext systems where workspace/admin domain names have not been configured, make sure to select the workspace that owns the volumes (file systems) that the client will mount. This is the "default" workspace. If you select a different workspace, you will not be able to use StorNext Connect to manage the client.

   After the Connector is installed, you are returned to the Discover page.

5. Click Rediscover to update system information.
6. In the Monitor Performance application in StorNext Connect, verify the Connector is passing the client's statistics to the StorNext Connect system:
   1. Click Client view.
   2. Select the client in the Client list, and click Update.
   3. Confirm that the application displays the client's statistics.

StorNext Connect must know the root password of the client to "push" the Connector to a Linux client. StorNext Connect cannot push the Connector to gateway appliances (such as the Xcellis Workflow Extender or G300), because the root password is not generally known. To install the Connector on a gateway appliance, you must download the "offline" Discover content from the myStorNext website and transfer it to the gateway appliance.

Identify the Gateway Appliance OS and Create a Temp Directory

Begin by identifying the operating system (OS) of the gateway appliance and creating a temporary directory for the Connector package.

1. Open an SSH connection to the server node of the gateway appliance and use the IP address assigned to the node on the Management or LAN Client network, or the IP assigned to the Service Port, depending on your access method.

1. Log in to the command line using the following credentials:
   • User name: stornext
   • Password: <stornext user account password>

     Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

2. Enter sudo rootsh to gain root user access.
3. Enter the password for the stornext user account again.

4. Enter cvversions to show the StorNext client/server versions.

   Example

   [root@G300]# cvversions

   Server not installed.

    

   File System Client:

   Client Revision 5.4.0.1 Build 67222 Branch branches_5.4.0.1 BuildId E

   Built for Linux 2.6.32-71.el6.x86_64 x86_64

   Created on Thu Nov 10 19:56:38 MST 2016

   Built in /scm/nightly/VM-0-RedHat60AS-26x86-64-SP0/sn/buildinfo

    

   StorNext Gateway Agent:

   Agent Revision 5.4.0.1 Build 67222 Branch branches_5.4.0.1 BuildId E

   Built for Linux 2.6.32-71.el6.x86_64 x86_64

   Created on Thu Nov 10 19:56:38 MST 2016

   Built in /scm/nightly/VM-0-RedHat60AS-26x86-64-SP0/sn/buildinfo

    

   Host OS Version:

   Linux 2.6.32-504.16.2.el6.qtm.x86_64 #1 SMP Tue May 17 08:47:21 PDT 2016 x86_64

5. Note the OS information. (See the highlighted information in the example above.)

   Note: The gateway appliance OS is shown as a version of RedHat, since they're running a version of CentOS (which is based on the RedHat OS).

6. Enter mkdir /tmp/<directory name> to make a temporary directory for the Connector package.

   Example

   mkdir /tmp/client

7. Close the SSH session for the node.

Download the Connector Package and Transfer to the Gateway Appliance

Download the Connector package to a system with a connection to the gateway appliance and Internet connectivity. Then transfer the Connector package to the gateway appliance.

1. Log in to the myStorNext website (mystornext.quantum.com).
2. Click Software update downloads.
3. Click Discover content to download the file.
4. Unzip and extract the contents of the file. If you are using a Windows OS, you might need to download an application to "untar" the file. The contents will look something like the following example.

   

5. Identify the Connector package that matches the operating system of the gateway appliance. For example, snconnect_client-RedHat60AS_26x86_64-18-420-9a700f3.tar.gz.
6. Using Secure Copy Protocol (SCP), transfer the Connector package from your local, download directory to the remote, temporary directory you created on the gateway appliance.

   On a Windows OS, you can use WinSCP or similar Windows SCP client.

   On a Linux OS, you can use the command line. For example:

   scp /<path to the local Connector package>/snconnect_client-RedHat60AS_26x86_64-18-420-9a700f3.tar.gz stornext@<gateway_IP_address>:/tmp/client

Install the Connector Package on the Gateway Appliance

1. Open an SSH connection to the server node of the gateway appliance and use the IP address assigned to the node on the Management or LAN Client network, or the IP assigned to the Service Port, depending on your access method.

1. Log in to the command line using the following credentials:
   • User name: stornext
   • Password: <stornext user account password>

     Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

2. Enter sudo rootsh to gain root user access.
3. Enter the password for the stornext user account again.

4. Enter cd /tmp/<directory name> to change the current directory to the temporary directory where you transferred the Connector package.

   Example

   cd /tmp/client

5. Enter tar zxvf <Connector_package> to unzip and extract the Connector package contents.

   Example

   tar zxvf snconnect_client-RedHat60AS_26x86_64-18-420-9a700f3.tar.gz

6. Enter ./snconnect_client/install_connector.sh <Connect_system_metadata_IP> to execute the installation of the Connector.

   Example

   ./snconnect_client/install_connector.sh 192.168.1.3

   Note: 192.168.1.3 is an example only; use the metadata IP address assigned to the StorNext Connect system (MDC Node 2 of a dual-node appliance).

7. Close the SSH session for the node.

Rediscover and Verify the Connector Installation

1. In StorNext Connect, in the Discover Components app, click Rediscover to update system information.
2. In the Monitor Performance application in StorNext Connect, verify the Connector is passing the client's statistics to the StorNext Connect system:
   1. Click Client view.
   2. Select the client in the Client list, and click Update.
   3. Confirm that the application displays the client's statistics.

1. Move the StorNext Windows Connector package installer you downloaded from the myStorNext website to a location on the StorNext Windows client.
2. Right-click snconnect_client_[version]_x64.exe, and click Run as administrator to launch the installer.
3. Read the end-user license agreement (EULA), and then select the check box to indicate your agreement.
4. Click Install.
5. When prompted, enter the management network IP address of the StorNext Connect system (Node 2 of a dual-node appliance).

   Additional Information

   Although you can enter either the IP address or hostname, you should use the IP address to avoid potential issues with DNS hostname resolution.

   If the Connector is already installed and you are installing a newer version, the installer will automatically use the IP address entered when the Connector was first installed.

6. When the installer is complete, click Close. If the installer encounters an issue, it provides a log file.
7. In StorNext Connect, in the Discover Components app, click Rediscover to update system information.
8. In the Monitor Performance application in StorNext Connect, verify the Connector is passing the client's statistics to the StorNext Connect system:
   1. Click Client view.
   2. Select the client in the Client list, and click Update.
   3. Confirm that the application displays the client's statistics.
9. Repeat the steps for each StorNext Windows client in the environment.

The Connect Add-on for Xsan application is an Apple OS X daemon that samples the I/O statistics of Xsan-attached storage and forwards the statistics to the StorNext Connect system. It must be installed on Apple Xsan clients whose storage statistics you want to monitor through StorNext Connect.

Note: StorNext Connect cannot manage Apple Xsan clients or monitor other statistics for them, such as their health status. Additionally, StorNext Connect cannot monitor Xsan LAN clients.

The StorNext Connect Add-on for Xsan Product Tips document is included with the ConnectAddOnForXsan file, which must be downloaded from the myStorNext website (mystornext.quantum.com) if they have Apple Xsan clients whose storage statistics they want to monitor through StorNext Connect. The document includes information about the Connect Add-on for Xsan application, including how to install and configure it. The same information is included in this site. See About the StorNext Connect Add-On for Xsan.

Note: The Connect Add-on for Xsan will not install properly on the Apple Xsan client if an .authsecret file is in place. Check for the existence of the file /Library/Preferences/Xsan/.authsecret on Apple Xsan clients and /usr/cvfs/config/.authsecret on the Quantum appliance (both MDC nodes of a dual-node system). Remove the .authsecret file on all systems if that is allowable in the customer environment.