Hi-Track Monitor Installation Guide

Copyright (c) 2001, 2007 - Hitachi Data Systems. All rights reserved.

Last Updated - Oct 16, 2007

• Forward
• Functional Overview
• Security
• Prerequisites
• Hi-Track Installation Instructions (with JRE)
• Starting and Running the Hi-Track Monitor
• Routine Running of the Hi-Track Monitor
• Uninstalling the Hi-Track Monitor
• Appendix A - HTTPS/FTP/Dialup Locations

Forward

• Storage
  • AMS/WMS/SMS
  • 9500V
  • 9200
  • Hitachi Content Archive Platform (HCAP)
  • High Performance NAS powered by BlueArc (BlueArc Titan)
  • Adic Tape Library
  • Netapp NAS
• Switches
  • Brocade
  • Cisco
  • Inrange
  • McData
  • Nishan

The normal distribution of the Hi-Track Monitor (IP0826-1) includes the Sun JRE (Java Runtime Environment) necessary to run the Hi-Track Monitor application. This distribution is to be used in locations that have no issue with export/import of the JRE from HDS based on export/import regulations of the specific locale and the USA. To perform this installation, follow the steps in the Hi-Track Installation Instructions (with JRE) section.

NOTE: These instructions apply to version 4.0 and higher of the Hi-Track Monitor.

Functional Overview

Purpose

Description

Security

• The Hi-Track Monitor program may be configured to communicate with the Hi-Track Center via either HTTPS or FTP over the public internet or via dialup through a modem and a phone line. Some customers prefer the HTTPS or FTP-SSL method for security while others prefer the dialup method for security.
• When configured to transfer to the Hi-Track Center via HTTPS over the public internet, the Hi-Track Monitor only sends data in an outbound direction (from the customer Lan to the public internet). The HTTPS traffic must all go through the customer firewall which allows the customer to place controls, limitations, and monitors at their firewall level. This includes limiting the destination location to strictly the one that Hi-Track needs to connect to and limiting the types of communications to only HTTPS originating on the inside of their firewall. The transferred data is encrypted when HTTPS is used.
• When configured to transfer to the Hi-Track Center via FTP over the public internet, the Hi-Track Monitor only performs FTP Put functions in an outbound direction (from the customer Lan to the public internet). It does not require FTP Puts inbound (from the public internet to the customer Lan) and doesn't perform FTP Gets. The FTP traffic must all go through the customer firewall which allows the customer to place controls, limitations, and monitors at their firewall level. This includes limiting the destination location to strictly the one that Hi-Track needs to connect to and limiting the types of communications to only FTP Puts originating on the inside of their firewall. Hi-Track supports both standard FTP and SSL FTP. When SSL FTP is selected as the transport method, the transferred data is encrypted.
• When configured to transfer to the Hi-Track Center via dialup through a modem and phone line, the connection being made by Hi-Track is always in an outbound direction to a specific phone number. Communications are performed using a unique proprietary communications protocol that's not compatible with any standard protocol such as tcpip, terminal emulations, telnet, etc. It's possible for a customer to disable autoanswer on the modem or through their switchboard if desired in order to inhibit inbound calls.
• The data the Hi-Track Monitor sends to the Hi-Track Center is maintenance related information that's not considered sensitive data. The data pertains to the current health of FRUs (field replacable units) such as power supplies, disk drives, fans, etc. and some basic configuration data such as microcode levels, etc. of the devices monitored.
• The Hi-Track Monitor system never accesses customer data stored on the monitored devices in any way.

Prerequisites

• The customer must supply a Windows XP Professional, Windows 2003 server, Windows 2000 Professional, Solaris 10, 9, or 8 workstation. For Windows, the recommended minimum system is a P4, 512M with CD-Rom (for loading the program). This workstation needs to run 24/7 in order to properly perform the Hi-Track function. Since potential device errors are detected by a poll from the Hi-Track monitor program to the device, the Hi-Track program would still be able to detect errors as soon as the Hi-Track program comes back up in the event the workstation was rebooted or the Hi-Track program was otherwise shutdown. It's possible that the workstation may be used for running other applications as long as the Hi-Track program is running concurrently.
• There must be TCP/IP LAN connectivity of the monitored device to the Hi-Track monitor workstation. The port normally used for AMS/WMS/SMS, 9500V, and 9200 devices is port 2000 so this port must not be blocked by a router between the Hi-Track Monitor and the device (note - the port number is configurable so it could be something other than 2000).
• If a fibre switch, Netapp, HCAP, or BlueArc device is to be monitored, it must be configured to allow SNMP Get funtions from the Hi-Track Monitor application. Use the documentation and configuration procedures for the particular switch to ensure the SNMP facility is set up properly. The community string (for SNMP v1/2) or User/Passowrd (for SNMP v3) in the Hi-Track Monitor will need to exactly match (including case sensitivity) the equivalent setup in the device. The SNMP v1/2 community string is "public" by default. The Cisco device and some other devices use SNMP v3. The HCAP device is configurable for either SNMP v1/2 or SNMP v3. The SNMP (161) port must be accessible since Hi-Track will perform SNMP Gets from this port of the monitored devices that use SNMP.
• If using the HTTPS data transfer mechanism, there must be connectivity for the HTTPS using the standard HTTPS port of 443. The customer's firewall must be configured to allow this type of protocol connection through the specified port range by the customer's network administrator if it isn't currently enabled. The customer may use an HTTPS proxy if desired. If an HTTPS proxy is used, the customer must supply the parameters to use with their particular proxy server if required.
• If using the FTP data transfer mechanism, there must be FTP Put/Append capability for passive FTP transfers using the standard FTP ports. The ports used are port 21 for non-SSL, 990 for SSL, ports 50000-50024 for the passive data connection. The FTP Puts and Appends are from the Hi-Track monitor workstation to the public internet. The customer's firewall must be configured to allow this type of protocol connection through the specified port range by the customer's network administrator if it isn't currently enabled. The FTP Put/Append needs to be enabled only in an outbound direction originating on the customer's LAN. Inbound FTP (originating outside the customer's LAN) is not required and should generally not be enabled since it might represent a security risk for the customer. The customer may use an FTP proxy if desired. If an FTP proxy is used, the customer must supply the parameters to use with their particular FTP proxy server as there are many possible configurations depending on the proxy software and how it's configured.
• If using the Dialup data transfer mechanism, a modem with a phone line connection installed in the workstation running the Hi-Track Monitor must be provided. Note - the following modems have been tested and are approved for use with the Hi-Track Monitor. It's possible that other modems might be used but they haven't been tested by the Hi-Track development group.
  • US Robotics Courier V.Everything
  • US Robotics Sportster 56K
  • MultiTech MultiModem
  • Xircom Cardbus Ethernet + Modem 56 PCMCIA Modem

Hi-Track Monitor Installation Instructions (with included JRE)

• Windows Installation
  1. Insert the Hi-Track monitor CD-Rom into the CD drive of the customer supplied workstation. The installation of the Hi-Track monitor should automatically start if the autorun function is enabled on the CD-Rom device otherwise, select Start->Run-> and browse to the htinst.exe program and run it.
  2. The installation program will start running. Follow the directions in the installation windows to install the Hi-Track Monitor. The installation program will install the program in \hds\hitdfmon by default. It's recommended to accept the default but it's possible to change the location of the program if desired. The program will be installed and started as a service.
  3. NOTE: In some cases there may be a problem performing the GUI installation due to the environment on the workstation (this occurs sometimes on the McData EFCM PC). If this happens, attempt to install by using the console installation by opening a command window, changing to the drive with the CD (ex. f:), and entering (without quotes) - "HTinst -i console".
• Solaris Installation
  1. Insert the Hi-Track Monitor CD-Rom into the CD drive of the customer supplied workstation. To start the installer for the Hi-Track Monitor application, run the HTinst.bin program (located on the CD in the solaris directory) either through a terminal window (sh HTinst.bin - note that Solaris is case-sensitive) or the GUI.
  2. The installation program will start running. Follow the directions in the installation windows to install the Hi-Track Monitor. It's recommended to accept the defaults but it's possible to change the location of the program if desired. The installation program will install the program in /usr/hds/hitdfmon by default and will setup the system to automatically start the Hi-Track monitor program whenever the workstation starts up (reboot). It does not automatically run the program after the installation completes. The program can be started by launching the rundfmon program with the start parameter (sh rundfmon start) located in the installation directory (/usr/hds/hitdfmon by default).
  3. NOTE 1: In some cases there may be a problem performing the GUI installation due to the environment on the workstation. If this happens, attempt to install by using the console installation by running (without quotes) - "sh HTinst.bin -i console".
  4. NOTE 2: In some cases there may be a problem performing either of the GUI or console installations due to the environment on the workstation. If this happens, attempt to install by using the tar file included on the CD by using the following procedure -
     1. Create the install directory - ex. /usr/hds
     2. Change directories to the new install directory
     3. Run the following: tar -xvf [tarFileName] (on the CD at /Solaris/tar/hitmon.tar). A new subdirectory named 'hitdfmon' is created in the specified directory
     4. Change directories to the newly created hitdfmon directory
     5. Run the following: sh setupservice [fullInstallDir] - ex. sh setupservice /usr/hds/hitdfmon

Starting and Operating the Hi-Track Monitor

Initial Running of the Hi-Track Monitor

1. Access the Hi-Track Monitor from a web browser by browsing to the ip address of the workstation and specifying port 6696 (the http port the Hi-Track monitor is using by default although it's configurable). For example, if the ip address of the workstation is 123.456.789.001, then browse to: http://123.456.789.001:6696. If using a browser on the same workstation as that running the monitor and if the workstation is configured to resolve localhost, it should be possible to access it by browsing to: http://localhost:6696. If unsuccessful at connecting to the monitor with the browser, check to make sure the Hi-Track Monitor program is running and that the browser proxy settings allow access to the workstation and that network connectivity exists. To check if the Hi-Track program is running on Windows, check that the "Hi-Track Monitor" service is running in Services' under the 'Control Panel'. To check if the Hi-Track program is running on Solaris, check if the process is running by issuing the command "ps -ef | grep hitdfmon".
2. After being presented with a page containing the Hitachi Data Systems logo and a login screen, login as an administrator by selecting 'administrator' from the list box then keying in the password. Note - the default password for both the administrator and monitor access levels is "hds" (without the quotes).
3. The first screen presented after logging in with the password is the About screen indicating the version of the program. Ensure that the expected version was installed. The screen has navigation buttons across the top of the screen labeled "Summary", "Configuration", etc. Use the buttons to navigate through the program. Click the "User Management" button to go to the User Management page.
4. The User Management page allows for entering and changing passwords used for logging onto the Hi-Track Monitor, for accessing SNMP devices, and for setting up a Proxy and SSL. This function is used to configure the user/password information required to access SNMP v3 devices such as Cisco and HCAP. It's also used to set up SNMP community strings to access devices such as Brocade, CNT/Inrange, McData, NetApp, and HCAP. The typical default SNMP community string of "public" is already configured so if that's the only one configured into the devices, no additional configuration is required on this page for those devices. The SSL security information should normally be left at its default value and not require any setting.
   • Changing the Hi-Track Monitor logon password
     • Select "Monitor User" from the security object listbox and click the adjacent "Refresh" button.
     • Select the Monitor User Type in the "Define Monitor User Types" table by selecting the appropriate radio button and then clicking the adjacent "Refresh" button.
     • Enter the desired password to use in the "Detail for Monitor User" table and click the adjacent "Refresh" button.
   • Setting the SNMP v3 user/password information (use for Cisco and optionally for HCAP)
     • Select "SNMP v3" from the security object listbox and click the adjacent "Refresh" button.
     • Enter an alias name in the box under "Security Name". This name is an alias that will be used to reference the security information to be added in the next step. This name can be anything such as "MyCisco", "CiscoA", CiscoB", "HDS", "HiTrack", etc. This is not necessarily the same as the user name that will be used for the device. After entering the name, click the adjacent "Refresh" button.
     • In the "Detail for SNMP v3" table at the bottom of the page, enter the Authorisation User and Authorisation Password to be associated with the name just entered in the previous step. The Authorisation User defaults to be the same as the Security Name but the Authorisation User may be changed here if needed. For example, if the Cisco devices have their SNMP v3 parameters configured with "administrator" as the authorisation user and "administrator123" as the authorisation password, then the following might be set in this table: Security Name: MyCisco, Authorisation User: administrator, Authorisation Password: administrator123. After entering the information, click the adjacent "Refresh" button.
   • Setting the SNMP community string information (use for Brocade, CNT/Inrange, McData, Netapp, and optionally HCAP).
     • Select "SNMP" from the security object listbox and click the adjacent "Refresh" button.
     • Enter an alias name in the box under "Security Name". This name is an alias that will be used to reference the security information to be added in the next step. This name can be anything such as "mySNMP", "BrocadeSNMP", "HDS", "HiTrack", etc. This is not necessarily the same as the user name that will be used for the device. After entering the name, click the adjacent "Refresh" button.
     • In the "Detail for SNMP Community" table at the bottom of the page, enter the Community ID to be associated with the name just entered in the previous step. The community ID defaults to be the same as the Security Name but the community ID may be changed here if needed. After entering the information, click the adjacent "Refresh" button.
   • Setting the Proxy information (only used if the customer requires going through a Tunnel or SOCKS proxy server for internet access)
   • Select "Proxy" from the security object listbox and click the adjacent "Refresh" button.
   • Enter an alias name in the box under "Security Name". This name is an alias that will be used to reference the security information to be added in the next step. This name can be anything such as "mySOCKS", "HDS", "HiTrack", HTTPS_Proxy, etc. After entering the name, click the adjacent "Refresh" button.
   • In the "Detail for Proxy" table at the bottom of the page, enter the security information associated with the Proxy server. This information must be provided by the customer. After entering the information, click the adjacent "Refresh" button.
   • Setting the SSL information (only used if the SSL FTP transport is to be used). NOTE: At this time, leave the SSL setting at its default values. No changes are necessary for SSL to function.
5. The Configuration page allows for entering and changing various configuration items relating to the Hi-Track monitor program. The configuration section consists of several pages selectable by clicking the navigation buttons labeled "Base", "Transport Agents", etc. that appear under the "Configuration" heading. The Base page is the first page presented when the configuration page was selected. It's recommended to leave most items at their default values but the following items are required to be set (click the "Submit" button after the modifications have been entered). When completed with the changes on each Configuration page, click the "Submit" button on the bottom of the page.
   • Base Configuration Page
     • SiteID: Enter the seven character SiteID for this site. It's important that the accurate SiteID is set. The SiteID is case sensitive. Make alpha characters upper case. Do not set an invalid SiteID in this location. The SiteID needs to be obtained from a customer service representative to ensure it's the correct SiteID for this location. Note: The SiteID entered in this location will be the default SiteID for devices yet to be configured. It's possible to override this default SiteID for a particular device by setting it on the configuration page for that device. If this default SiteID is changed at a later time, it will NOT affect devices already configured. Those devices already configured would need to have their SiteIDs changed individually if it's desired to change to the new value.
     • Report Communication Errors: The default option is to not report errors relating to communication errors between the monitor and the device. This is so that customer network errors don't result in unwanted case opening/notification. If it's desired to report these types of errors, enter a YES here. If it's desired that communication errors only send an email to the configured email destinations (see next step) but not the Hi-Track Center, enter 'Local'
     • Notify Users by eMAIL: The Hi-Track Monitor program can optionally send email notifications to a user defined list of email locations. The customer must supply the name or IP address of the sending mail server to use. Email locations to send the notification to are entered in the User List and are separated by a comma. Some customer mail servers won't allow an email to be sent unless the sender's email address is already known to it. In this case, set the "Sender's Email Address" area up with an email address that's known to the sending mail server. This address must be supplied by the customer. Click the adjacent "Submit" button to make the changes take effect. Click the "Test Email" button to have a test email sent to the locations just configured.
   • Transport Agents Configuration Page
   • If using the HTTPS data transfer mechanism - Enter the HTTPS parameters to allow the monitor program to access the Hi-Track HTTPS server at the Hi-Track center. Obtain the current HTTPS parameters from the Hi-Track Home Page. If a proxy will be used, consult with the customer network administrator to determine the proper HTTPS proxy setup. The Hi-Track HTTPS Server will use port 443 for the transport so the customer must make sure their firewall allows the data connection to function through this port.
     
   • Under the "Data Transfer Agents" heading, select "HTTPS" in the list box and click the "Create" button. The Configuration page will reappear with a detailed HTTPS configuration form at the bottom.
   • Enter the HTTPS Server to send the data to under "Server". This can be found in the appendix.
   • Select the ethernet interface to use for the HTTPS transport to the public internet under "Local Interface". If the workstation has multiple interfaces (multiple NIC cards installed), be certain to select the interface that has the access to the public internet. NOTE - If the customer makes later configuration changes to the workstation, it's possible it may affect the interfaces available and that this setting will need to be changed.
   • Enter the HTTPS port to use. This should normally be set to 443.
   • Enter the HTTPS user name under "UserName" (see appendix with user names).
   • Enter the HTTPS Password under "Password" (see appendix with passwords). Note - The password will need to be entered twice, once in each of the boxes adjacent to the "Password" line. Both of these passwords must match.
   • If the customer requires the use of a Tunnel or SOCKS proxy, select from the listbox the Proxy alias name that was previously configured in the "User Management" function.
   • Click the "Submit" button to make the changes take effect.
   • If using the FTP data transfer mechanism - Enter the FTP parameters to allow the monitor program to access the Hi-Track FTP server at the Hi-Track center. Obtain the current FTP parameters from the Hi-Track Home Page. If the customer requires that communications take place through an FTP Proxy, it may be possible to configure the Hi-Track Monitor to function through the proxy by manipulating the FTP location and FTP user name. An example FTP proxy setup for the customer Acme might be: FTP Location - ftp.acme.com, FTP User - [email protected], FTP Password - (normal password). If a proxy will be used, consult with the customer network administrator to determine the proper FTP setup. When the FTP conection is set to Passive, the Hi-Track FTP Server will use port 21 (non-SSL) or 990 (SSL) for the control connection and will use a port from the range of 50000-50024 for the data connection. The customer must make sure their firewall allows the data connection to function through this port range.
     It's recommended to test the connectivity of the workstation and the FTP parameters to use (especially if a proxy will be used) by opening a command window on the workstation and attempting to manually transfer a file by FTPing to the Hi-Track internet FTP server. If the FTP fails, troubleshoot the problem before attempting to get the Hi-Track Monitor to FTP. It may be necessary to have the customer's network person help with this troubleshooting since it's possible they have the path firewalled off or that they require specific procedures due to a proxy. Note - it won't be possible to perform this command line FTP test to the SSL FTP location. It's still suggested to attempt the FTP transfer test to the non-SSL location even if SSL will be used within the program.
   • Under the "Data Transfer Agents" heading, select "FTP" in the list box and click the "Create" button. The Configuration page will reappear with a detailed FTP configuration form at the bottom.
   • Enter the FTP Server to send the data to under "Server".
   • Select the ethernet interface to use for FTP'ing to the public internet under "Local Interface". If the workstation has multiple interfaces (multiple NIC cards installed), be certain to select the interface that has the access to the public internet. NOTE - If the customer makes later configuration changes to the workstation, it's possible it may affect the interfaces available and that this setting will need to be changed.
   • Enter the FTP port to use. This should be set to 21 for non-SSL FTP and to 990 for SSL FTP.
   • Enter the FTP user name under "UserName".
   • Enter the FTP Password under "Password". Note - The password will need to be entered twice, once in each of the boxes adjacent to the "Password" line. Both of these passwords must match.
   • If the customer requires the use of a Tunnel or SOCKS proxy, select from the listbox the Proxy alias name that was previously configured in the "User Management" function.
   • If SSL transport is to be used, select from the listbox the SSL alias name "HDS FTP".
   • Click the "Submit" button to make the changes take effect.
   • If using the Dialup data transfer mechanism - Enter the Dialup parameters to allow the monitor program to access the Hi-Track Center. Obtain the dialup number to use from the Hi-Track Home Page.
   • Under the "Data Transfer Agents" heading on the Configuration page, select "Dial Up" in the list box and click the "Create" button. The Configuration page will reappear with a detailed Dialup configuration form at the bottom.
   • Enter the Hi-Track center phone number to dial in the "Hi-Track Phone Number" box following the "ATDT". Example: "ATDT9,1-800-555-1212"
   • Select the "Local Comms Port" to use for dialing (ex. COM1 for Windows, /dev/term/a for Solaris). Normally this will have the correct port but may be adjusted if multiple ports exist and the wrong one appears.
   • The "DTE-DCE Baud Rate" should normally be left at the default (57600) but may be changed if desired. If communications are unreliable due to low quality phone lines, changing this speed to 9600 or 1200 may help for a more reliable connection but the transfer will take much longer.
   • The "Modem Initialization" contains a default string that works with the US Robotics and some other modems. If a different modem is used, it may be required to modify this string.
   • The "Call Termination" should be left at its default value (+++).
   • Leave the "Delete" box blank and leave the "Enabled" checkbox checked.
   • Click the "Submit" button to make the changes take effect.
   • Local TCP/IP Configuration Page
   • The HTTP/SNMP Service Ports may be changed if needed but generally the default values will be used.
   • The Local TCP/IP Interface may be changed if need be to match the interface (network) that the devices to be monitored are on. This generally only needs to be changed if the workstation has multiple NICs installed and the default selection is the wrong interface. If after completing the configuration of the Hi-Track Monitor it's unable to communicate with the devices, then this setting is likely pointing to the wrong interface and needs to be changed to the correct one.
   • Click the "Submit" button to make the changes take effect.
   • The Debug/Trace Configuration Page is used to increase the level of logging for troubleshooting problems. This page should generally be left at its default values unless a problem is encountered that requires an increased logging level.
   • The Timezone Configuration Page is used to change the timezone settings. This page should generally be left at its default values unless a problem is encountered with the timezone setting.
6. Click the Summary navigation button at the top of the page to go to the device summary page. Add items (AMS, 9500V, fibre switch, etc.) to monitor by clicking on the "Add a Device" hyperlink on the device summary page (this operation requires that the user be logged on as Administrator). After the "Add Device" page is presented, select either the "Storage Device" or "Fibre Channel" button depending on the device type (use the 'Fibre Channel' button for HCAP and HiPerf NAS BlueArc Titan) and then enter the details for the particular device to monitor. After entering the details, click the "Add" button to make the changes effective. Repeat this process by selecting the "Add a similar device" or "blank Add form" hyperlinks presented after the Add for each unit to be monitored. When done entering units, select the "Summary" navigation button to return to the device summary screen.
   
   • Name, Location: These are optional fields and are used only as a reference for conveniently identifying the particular unit on the device summary page and in the data sent to the Hi-Track center. They may be left blank if desired.
   • Serial Number: Leave this field blank for 9500V and 9200 and some switch devices since the serial number will automatically be sensed from the device later. It must be entered for the devices indicated in the note below the form.
   • Site ID: The default SiteID that was previously entered in the Basic Configuration page will appear here. If it's desired to have a different SiteID for this unit, overtype this SiteID with the particular one. Make certain that a valid SiteID exists in this field.
   • IP Address 1: This is a required field. Enter the IP address (or resolvable name) of the device to be monitored.
   • IP Address 2: This is an optional field. Enter the IP address of the second controller package in the AMS/WMS/SMS, 9500V or 9200 system to be monitored or for HCAP and some switches with multiple access points, the alternate path ip address. For the AMS/WMS, 9500V, 9200 devices it's possible to perform the Hi-Track functions by monitoring just a single controller package with the exception of the "Mate Controller Error" detection.
   • Local Interface: Select the appropriate ethernet interface to use to communicate with the device.
   • SNMP Access ID: This field is only for SNMP type devices. Enter the SNMP alias name from the droplist. These alias names are defined through the User Management function previously described.

Note 1:
The HCAP system may have multiple nodes as potential access points. It's recommended to configure two nodes into the 'Add a Device' entry box so that if one node fails Hi-Track will still be able to communicate through the other node. The status of all nodes is reported through each node so it's not necessary to have Hi-Track monitor through each node. An example would be that a 4 node system would have just two nodes configured as the ip addresses in the 'Add a Device' box for the HCAP system.
Note 2:
After adding items, wait a few minutes until the program has had a chance to communicate with the device to obtain the data before clicking on the device detail icon.
Note 3:
It's possible to import the items (AMS/WMS/SMS, 9500V, 9200, switch devices) to add from a comma delimited file (such as one created by Excel). This is useful if the Hi-Track Monitor will be connected to a large number of devices. The format of the comma delimited file has 13 columns separated by commas with a carriage return/Line feed at the end of the line. The columns consist of:

1. Device Name (free format text)
2. Device Location (free format text)
3. Device Serial Number (free format text - will be overridden for DF, Inrange and McData devices)
4. SiteID (7 character Hi-Track ID)
5. IP Address 1 (either dotted-decimal or name)
6. IP Address 2
7. (Leave blank - was SNMP Community ID in earlier versions)
8. Device Type (prefacing with NM denotes "Not Monitored"):
• 9200
• 9500
• 9580
• AMS/WMS/SMS
• Adic
• Archivas (for HCAP)
• Brocade
• Cisco
• Inrange
• McData
• McdEOS (for McData i10k)
• McdNishan (for McData 1620,2640)
• NetApp
• Titan (for BlueArc Titan NAS)
• fc (generic FibreChannel device)
• Software (for Hi-Command Device Manager)
9. Device Local Interface #1 (e.g. 'eth0')
10. Device Local Interface #2
11. (Leave blank - was SNMPv3 Authorization UserName in earlier versions)
12. (Leave blank - was SNMPv3 Authorization Password in earlier versions)
13. SNMP Security ID (The alias name defined for security attributes on User Management page)
To import the data, stop the Hi-Track Monitor program and then run the import program from the installation directory as follows:
• Windows: jre\bin\java -jar HiTrack.jar import commFileName
• Sun: sh rundfmon import commFileName
Where commFileName is the comma delimited file to import. After importing the file, restart the Hi-Track Monitor program. If switch/NAS type devices were defined with non-default alias names (other than 'public' for SNMP or any SNMPv3 device) then for a new Hi-Track Monitor install where the alias hasn't already been configured, the alias name will need to be configured in 'User Management' and the devices, which will appear in the 'Not Monitored' section, will need to have their 'Enabled' checkbox checked to allow them to be monitored.
It's possible to export the configuration from the Hi-Track Monitor to a comma delimited file by changing the import keyword to export. An export file (devices.export) is produced automatically about every 5 minutes.

Optional Setup Parameters

• By default, the Hi-Track Monitor stores its log files in the installation directory (hds\hitdfmon by default). It's possible to change this location by adding the following parameter in the HitDFmon.config file (restart the Hi-Track Monitor program after making this change):
  LogNameTemplate = dirName/HiTrack%Y%m%d.log (Use a forward slash in the path for Solaris and a back slash for Windows)
  Where dirName is the directory name. The %Y%m%d indicate to use YYYYmmdd in the log name.
• CR-LF (Carriage Return, Line Feed) characters may be defined in the following FTP fields: Host, UserId, Password and Account. The configuration parameter 'escapeCRLF' must be defined in the configuration file HitDFmon.config
  escapeCRLF = CRLF
  Note that any text string may be used to define the CR-LF sequence. The defined text string can then be used in the FTP fields (either in the configuration file, or in the HTML configuration pages) to include a CR-LF sequence.
  FTPhost = hostname1CRLFhostname2
  will send the following text when defining the remote FTP server
  hostname1
  hostname2
• A SOCKS-5 proxy may be defined via the configuration file HitDFmon.config, overriding all other SOCKS definitions for FTP transfers.
  FTPsoHost = socksHostName
  FTPsoPort = socksPortNumber
  Both parameters must be defined.
• A fixed Subject line for the emails sent by Hi-Track Monitor may be defined in the configuration file, HitDFmon.config:
  EmailSubject = subject line text for all emails
• It's possible to run two instances of the Hi-Track Monitor (HTM) on a single workstation however special accommodations must be made in order to do so. Typically this would only be done if the HTM is monitoring systems in both Europe and the rest of the world (ROW) and must therefore transport to two different locations. The HTTP port the HTM will respond to must be changed. If dialup transport is selected, each instance must be configured to use its own separate modem. When installed on Windows, the Windows Services must be changed to allow for two instances to run as a service. Use the following procedure for Windows systems (the example shows one instance for Europe and a second instance for ROW). Note: The parameters to the 'sc' command must be spelled correctly and there must be one blank space after the 'equals' sign for each parameter.
  • Install HTM to directory c:\HDS\Monitor\Europe
  • Open a command window to input the following commands (italicized)
  • sc stop HitDFmon
  • sc delete HitDFmon
  • sc create HTMEUR binPath= "C:\HDS\Monitor\Europe\HitDFmon.exe -zglaxservice HTMEUR" DisplayName= "Hi-Track Monitor Europe" start= auto
  • sc start HTMEUR
  • Open a browser (don't close the command window yet) and browse to the HTM (http://127.0.0.1:6696) and go to the Configuration->Local TCP/IP page and change the HTTP Service Port to a different number (example: 6697) and submit
  • In the command window, enter -
  • sc stop HTMEUR
  • sc start HTMEUR
  • Repeat the above process but replace 'Europe' and 'EUR' with 'ROW' and select a different HTTP port (example: 6698).

Routine Running of the Hi-Track Monitor

The Hi-Track monitor program should be running 24/7 to ensure that it will detect error conditions on the monitored devices and so that it can report to the Hi-Track center on a daily basis. Normally the program runs in the background (as a Windows Service or Solaris process) and no window is presented for the program. All interaction with the program is performed via web browser access to the monitor program. Through the browser interface one may set basic configuration items, add new or modify existing devices to monitor, view the status of each device, or view details of a device. A web browser anywhere on the customer's LAN that has TCP/IP connectivity to the workstation running the Hi-Track monitor can typically be used to interact with the program. It's possible to have multiple browsers from multiple locations access the Hi-Track monitor concurrently. The browser access has two operational levels based on the type of login used - Administrator and Monitor. The Administrator type is allowed to set or change basic configuration items and add/edit/delete devices to monitor. The Monitor type is not allowed to set or change program configuration items but can monitor device status and view device details. When a browser is displaying the device summary page, the page will update itself about every 60 seconds.

The top table on the device summary page displays a summary of the numbers of devices that are presently in a particular monitor category which includes devices exhibiting errors, devices that the monitor program is unable to communicate with, devices that are reporting okay and with no errors, devices not monitored due to user setting, and total devices configured for the monitor. The table contains checkboxes which determine what categories will be displayed in the tables that follow this summary table. The default is that all tables will be displayed (checkboxes checked).

Up to four tables will follow the summary table. The following tables are presented if any devices exist in the category:

• Device Error - This table displays devices which are exhibiting errors. The Status column will be red with a short summary of the error type.
• Communication Error - This table displays devices which the monitor program is unable to communicate with. The Status column will be in yellow. The communication error may be due to a network problem, ip address setup problem, or the device is powered off.
• Device Okay - This table displays devices that are reporting normally and exhibit no errors. The Status column will be green.
• Not Monitored - This table displays devices that the user specified to not monitor even though they're configured in the monitor. This is performed via a checkbox on the item setup. The Status column will be pale yellow. This option may be used to disable checking of the device when maintenance is being performed to the device or when a customer has the device temporarily unavailable.

• Item - Indicates the item number for the device according to the order in which the devices were entered. In administrator mode, the item number is hyperlinked and may be clicked to modify the device's monitor setup parameters and the Item heading is hyperlinked to allow for adding new devices when clicked. Note - It may take a few minutes for the data for a newly added device to be obtained before having valid detail data for the device.
• Name, Location - Indicates the name or location set when the device was added. This is for user reference only.
• Type - Indicates the type of device (DF Storage, Cisco, etc.).
• Model - Indicates the model number of the device (AMS, 9500V, etc.).
• Serial - Indicates the serial number of the device.
• Status - Indicates the error status of the device.
• Last Communication - Timestamp of the last time the monitor attempted to communicate with the device. This field is normally updated every few minutes.
• Site ID - Indicates the Site ID set for the device at the time it was added.
• IP Address 1 or 2 - Indicates the IP addresses that were set for the device when it was added.

In the Status column for a particular device, the 'D' icon may be clicked to display a page showing details of the device. The detail page includes a number of tables showing error status and configuration details for various functional components including drives, cache, power, fans, microcode levels, etc.

The Hi-Track monitor will send device data related to error and device configuration to the Hi-Track center when an error condition is detected and also on a daily basis.

Clicking the "Transport History" navigation button will present a page indicating the data transport activity of the Hi-Track Monitor. This can be useful for troubleshooting Hi-Track transport problems. This page also has a "Request Report" button at the bottom which will force a data transport to take place. This can be used to ensure the Hi-Track Monitor is set up properly to transport the data to the Hi-Track Center.

Note: For some program configuration changes, the program will indicate to restart the Monitor program. This is done by stopping then starting the "Hi-Track Monitor" service through the Windows Control Panel for Windows systems, or by running "sh rundfmon stop" followed by "sh rundfmon start" for Solaris systems.

Uninstalling the Hi-Track Monitor

1. Windows Uninstallation
   1. Stop the Hi-Track Monitor program, if running, by stopping the "Hi-Track Monitor" service through the Windows Control Panel.
   2. Select Add/Remove Programs under the Control Panel and remove the Hi-Track Monitor program. Note - not all items will be removed but will be removed in the next step.
   3. Delete the installation directory (\hds by default).
2. Solaris Uninstallation
   1. Stop the Hi-Track Monitor program, if running, by running "sh rundfmon stop" in the installation directory (/usr/hds/hitdfmon by default).
   2. Run "sh Uninstall_Hi-Track_Monitor" (for versions prior to 2.6, "sh Uninstall_HiTrackMonitor") in the /usr/hds/hitdfmon/UninstallerData (by default) directory.
   3. Delete the HDS directory where the Hi-Track monitor was installed. Empty it from the recycle bin if it's now present in the recycle bin.

Appendix A - HTTPS/FTP/Dialup Locations

• For partners - Configure the HTTPS, FTP, and/or dialup locations by following the appropriate procedures supplied by that particular partner. If the procedures are unavailable or are unclear, contact that partner's support group for guidance.