This document describes enhancements and bug fixes to the Hitachi Remote Ops Service Processor Agent through version D.3.

Bugs Fixed in this Version

• [385] FrontSvc.exe may be falsely flagged as a virus by various anti-virus suites.

Changes and Enhancements

• [386] Collects ORM information from VSP 5x00/5x00H systems.

Bugs Fixed in this Version

• [362] The Site Manager attempts to transport already transported and no longer existent SIMs.
• [363] The Site Manager drops a back's explicitly specified registration address.
• [364] Adding an FTP contact method attempted to add a dial-up contact method.
• [365] FFI parts file transfers were not logged in the transport logs.
• [366] IP addresses in AllConf01.csv were not masked if configured to do so for USP V and USP VM. This release addresses this issue and masks those IP addresses.
• [367] Remote microcode upgrade requests are lost upon stop of the front service.
• [368] Cancellation of remote microcode upgrade requests do not always signal an acknowledgement or failure of the cancellation.
• [369] Remoting failures between the front and back hang communication.
• [370] Remote microcode updates on VSP Fx00/Gx00 arrays prematurely signals a successful upgrade while the firmware update process is reading the configuration.

Changes and Enhancements

• [371] Rebrands to Hitachi Remote Ops Service Processor Agent. This affects install and startup menu locations.
• [372] Adds support for VSP 5x00/5x00H systems.
• [373] Supports remotely triggered transport of configuration and performance data.
• [374] Supports remotely triggered disabling of the Service Processor Agent and Site Manager.
• [375] OSS version information is collected on VSP Gx00 systems.
• [376] WMIC hard disk partition capacity information is collected.
• [377] Service Manager denotes between services in a stopped and disabled state.
• [378] SIM processing and transfer happens completely concurrent to any daily and dump transfer occurring at the same time.
• [379] Changes to SIM reporting configuration are logged.
• [380] CPU utilization is logged by a back before it prepares for daily call.
• [381] Cancellation requests for remote microcode updates are checked for and applied, if applicable, immediately upon receipt.
• [382] Cancellation requests for remote microcode updates queue up for later checking if the remote Site Manager or Service Processor Agent are busy and can't be immediately checked for matching requests.
• [383] Successful completion of a microcode update will automatically cancel any pending requests there were made before the application of new code.
• [384] Expands logging and polling responses for SIMs and remote operations.

Bugs Fixed in this Version

• [354] SIMs do not transport in version D.1 if the Enable SIM triggered AutoDump transfer option is unchecked.
• [355] Dumps that successfully transfer to Hitachi Vantara may retry to transfer the file and fail to send a transfer completion response.
• [356] On backs configured with an invalid Site Manager, dumps requested through the Service Manager fail to generate.
• [357] Remote microcode updates fail to send responses about success and completion when the front loses connectivity to the back.
• [358] Configured SOCKS proxies are ignored during HTTPS transfer.

Changes and Enhancements

• [359] Scheduling of remote microcode updates is now based on a server supplied time.
• [360] Hi-Track installs in the Hitachi Vantara subdirectory of the Program Files directory instead of Hitachi Data Systems subdirectory.
• [361] Hi-Track's start menu directory changed to Hitachi Vantara instead of Hitachi Data Systems.

Bugs Fixed in this Version

• [334] The Site Manager fetches the latest dump from a back, without verifying that the retrieved dump matches the requested dump.
• [335] During dumps or remote microcode updates, the Site Manager incorrectly logs that it cannot connect to a connected back.
• [336] Dump polling may send an erroneous Notified status before sending the correct Busy or Skipped status.
• [337] Dumps will continually reattempt to transfer after a successful transfer.
• [338] Remote microcode updates requests received at the same time as a dump request may fail to notify the back.
• [339] SIMs skip checking AutoDump triggers when occurring in quick succession.
• [340] A security issue related to LDAP authentication was resolved.
• [341] The HTA_DumpInterfaceReset.exe file has been removed. This file can sometimes cause a false positive anti-virus indication.
• [342] Out-of-date SVPMON performance data files persist from prior versions.

Changes and Enhancements

• [343] Upgrades Microsoft SQL Server Compact Edition 4.0 to Microsoft SQL Server Compact Edition 4.0 SP1.
• [344] Site Managers can now process multiple dumps simultaneously, with a limit of one dump per unique system being allowed during a single dump sequence.
• [345] Site Managers will attempt to re-connect with all backs before all daily call, dump, and remote microcode update attempts.
• [346] Adds a dump polling response for connect attempt failures during wait for dump.
• [347] Adds a dump polling response for dumps that don�t complete within the allowed time limit yet have not hit the connection failure limit.
• [348] IP Address information will be masked within an array�s back logs, CSV files, and Hi-Track.dat file, if the Site Manager it belongs to is configured to hide IP addresses.
• [349] IP Address information will be masked in the Site Manager�s logs if the Site Manager is configured to hide IP addresses.
• [350] IP Address information will be masked in the Service Manager�s logs if the Site Manager responsible for the device running Hi-Track is configured to hide IP addresses.
• [351] Updates references to RAID 800 and HM 800 to their marketing names.
• [352] Updates all UTC time references to GMT time references for consistency.
• [353] Adds the option to enable/disable SSL certificate validation for email notifications that use SSL.

Bugs Fixed in this Version

• [306] Some systems were not included in dump and/or microcode polling that were capable of centralized dumps or remote microcode updates.
• [307] Remote microcode updates would never start for any Site Manager that had multiple systems reporting to it.
• [308] If the system was already busy with a dump or a remote microcode update, and another remote microcode update was requested, the error message would incorrectly indicate that the system was busy sending configuration data to Hitachi Vantara.
• [309] If a microcode upgrade timed out, the Site Manager would send an error message for all systems reporting to it, instead of just the system where the remote microcode upgrade failed.
• [310] The new transport destinations usdenhtinet01.hds.com and usdenhtinet02.hds.com were mistakenly added to Site Managers running on systems with Windows Vista or 2008 installed, which do not support TLS 1.2.
• [311] A "Failed" status message would be incorrectly sent to Hitachi Vantara after the first and second microcode retry. The message will now only be sent after the third and final retry.
• [312] The Site Manager would, in some cases, stop monitoring the progress of an update on a system.
• [313] Disabling configuration data transfer to Hitachi Vantara did not disable performance data generation and transfer.
• [314] Disabling configuration data transfer to Hitachi Vantara resulted in unnecessary log messages about the disabled status.
• [315] The version of the SVP Agent running on each subsystem was not transmitted to Hitachi Vantara in the dump/microcode polling.
• [316] Incorrect log messages would be generated for any system that was not reachable from a Site Manager performing a microcode upgrade on any system.
• [317] Remote microcode updates would never start for a system that had an extended period of no network connectivity.
• [318] If an error occurred transferring dump files to the Site Manager from the system, the corrupted files would be transferred to Hitachi Vantara. The Site Manager will now retry the file transfer for a limited number of attempts.
• [319] It was possible to add the same IP address twice to the system list.
• [320] VSP G/F 1500/1000 HDP compression data and some VSP HDP data was not generated or transferred to Hitachi Vantara.
• [321] The format of the cache performance data did not indicate the overall performance statistics properly.
• [322] Remote microcode updates that had stalled were not aborted.
• [323] In some cases, an error connecting to any system from the Site Manager would result in the Site Manager being unable to perform dump and microcode upgrade polling to Hitachi Vantara.

Changes and Enhancements

• [323] SSL certificate validation will now be automatically enabled on upgrading to D.0. If the customer firewall will not permit SSL certificate validation and/or is configured to connect to the IP address of the transfer server rather than the domain name, SSL certificate validation will need to be manually disabled for each transport method as well as for dump/microcode polling. However, this is not recommended as SSL certificate validation is an important security measure that prevents impersonation of Hitachi Vantara web servers.
• [324] The distinction between a daily and a weekly call home to Hitachi Vantara has been removed since configuration data is now always transferred on a call home.
• [325] It is now possible to cancel microcode requests, as long as the update application process has not been started.
• [326] Certain outdated or corrupted performance data files will now automatically be deleted.
• [327] A maximum of 5 SIM-triggered auto dumps will be generated during a calendar day.
• [328] The MiscFront.dat data, containing additional data from the Site Manager, will now be transported with every subsystem connected to the Site Manager rather than just one of them.
• [329] The Site Manager will now collect the time zone information from the system it is installed on and include it in MiscFront.dat.
• [330] The Visual Studio 2015 C++ Redistributable is now included instead of the 2012 version.
• [331] The integrated nsoftware IPWorks! components have been upgraded from version 9.0 (SSL) to 2016 (regular).
• [332] Information on whether the SVP is in modify mode is now printed to the SVP Agent logs before a remote microcode upgrade.
• [333] An option to disable polling to Hitachi Vantara for dump requests and microcode updates was added to the Hi-Track Dump Interface accessible with a web browser.

Bugs Fixed in this Version

• [266] Extra "Periodic performance stat collection restarted" messages were included in the logs.
• [267] The cache rate in the LDEV.csv performance data was incorrect. Version C.F fixes this with the correct data in LDEV2.csv.
• [268] Some old performance data was not clearing out properly.
• [269] The automated cleanup of performance data was running every time performance data was generated.
• [270] A memory leak could occur when generating the configuration data for a daily transport.
• [271] If transfer of configuration data was disabled, the Transfer Now button would still transport configuration data to Hitachi Vantara.
• [272] If transfer of configuration data was disabled, an error message would appear in the logs repeatedly.
• [273] If the transfer of performance data from the SVP to a Site Manager failed, the Site Manager would skip transfer of any configuration data from another system.
• [274] The domain proxy name would not always be used when dump polling.
• [275] Outdated performance data and some dump files would be kept indefinitely until they could successfully be transferred to Hitachi Vantara.
• [276] If the PersistentData.xml file was corrupted, performance data would not properly generate.
• [277] There was a rare issue where HDP configuration data would not be properly generated if the SVP and DKC versions did not match.
• [278] Duplicate messages about the SVP Agent starting would sometimes appear in logs.
• [279] For HTTPS contact methods, the domain proxy field would always be enabled even when no proxy was configured.
• [280] A SVP Agent doing a daily transport and handling a SIM at the same time might result in the SIM data transport failing.
• [281] Systems with serial numbers starting with one or more zeros (including after the 4 or 2 prefix on VSP Gx00/Fx00 or HUS VM systems) were not properly supported. Version C.F fixes this bug, after it was partially fixed in C.E.
• [282] Dump file transports over 2 GB would fail. The transport destinations now enforce the size limit, which currently is around 4.29 GB.
• [283] The date widget in the web AutoDump interface would sometimes be cut off in Google Chrome.
• [284] Hi-Track.dat would not generate properly on some systems. Version C.F mitigates this bug by generating a version of the file with some data, but a fix to the Windows Registry must be applied to completely resolve this rare issue.
• [285] If one SVP connected to a Site Manager was nonresponsive, dump polling would not work for any SVP at that Site Manager.
• [286] Only the first 100 KB of the Site Manager logs would be transported to Hitachi Vantara if the Site Manager was on a customer-supplied platform. Version C.F fixes this bug by increasing the limit to 500 KB.
• [287] Proxy and proxy interface IPs were not obscured from the logs when the "Hide IP addresses" option was selected.

Changes and Enhancements

• [288] For VSP G1x00/F1500, VSP Gx00/Fx00, HUS VM, and VSP, remote microcode updates are now supported. The following microcode versions must already be installed to perform an upgrade: VSP G1x00/F1500: SVOS 7.3.1, 80-06-02-00/00-M132 or greater; VSP Gx00/Fx00: supported with a future release of microcode; HUS VM: 73-03-58-00/00-M082 or greater; VSP: 70-06-53-00/00-M281 or greater.
• [289] Performance data for VSP Gx00/Fx00 will now be generated and transported to Hitachi Vantara.
• [290] Dump polling now uses a different mechanism that will improve tracking of dumps and allow for polling for remote microcode updates.
• [291] Support for dial-up transport has been removed. Data must now be transferred to Hitachi Vantara over FTP, FTPS, or HTTPS.
• [292] For VSP Gx00/Fx00, if the option to send an email for SIM errors is enabled, an email will be also be sent for GUM communication failures
• [293] Support for the new transport destinations usdenhtinet01.hds.com and usdenhtinet02.hds.com have been added. These new destinations require support for TLS 1.2, which is not supported on Windows Vista and must be manually enabled on some Windows 7 systems.
• [294] The SVP Agent has been rebranded as a Hitachi Vantara application, to reflect the company name change.
• [295] The default dump and microcode update polling interval has been changed from every 180 seconds to every 300 seconds. Any value below 300 seconds will be ignored, and the site manager will poll every 300 seconds in this scenario.
• [296] All numerical references to subsystems now display the number in decimal rather than hexadecimal format.
• [297] The maximum daily log file size has increased to 10 MB.
• [298] The native .NET compression API is now used to handle ZIP files.
• [299] Dump polling processing will now time out after 10 minutes instead of 30 minutes.
• [300] For VSP Gx00/Fx00, the 1c0000 reference code will now generate an AutoDump.
• [301] The Service Provider field has been moved to the Site tab, and the Notification tab has been reorganized.
• [302] The two-hour timeout for requesting dumps has been removed. Dump requests received while a dump is generating will still be ignored.
• [303] Transport method and dump proxy settings will now use the same settings for each type of transport (FTP(S) and HTTP).
• [304] The reference code is added to the logs when transporting SIM data.
• [305] A new option has been added to send an email when a SVP connected to a Site Manager does not respond to communication after an hour.

Bug Fixes

• [237] Some dump polling failures that occur after dump polling successes go unlogged. Version C.E fixes this.
• [238] MiscFront.dat would always identify the first storage system as the site manager in the case that the site manager is a customer-supplied platform. Version C.E fixes this error.
• [239] An error occurred when an administrator on the dump web interface tried to delete itself. Version C.E no longer allows for an administrator to do this.
• [240] Rebooting the SVP during a dump request would result in a dump requested soon thereafter failing. Version C.E fixes this error.
• [241] Performance data generation would sometime stop if the data files were corrupted. Version C.E fixes this bug.
• [242] FFI parts files older than 72 hours were not actually deleted. Version C.E fixes this bug.
• [243] Systems with serial numbers starting with one or more zeros (including after the 4 or 2 prefix on VSP Gx00/Fx00 or HUS VM systems) are properly supported.
• [244] Systems with Windows 10 installed are now properly identified as such in Hi-Track data.
• [245] Systems that cannot support dump requests are no longer included in dump polling to HDS. This would include those with a SVP Agent version below C.7, or USP or NSC systems.
• [246] The Help button in the Service Manager did not work. Version C.E fixes this bug.
• [247] The log viewer window would sometimes stop responding. Version C.E fixes this bug.
• [248] A rare issue would sometimes occur where a daily transport and a SIM would conflict. Version C.E fixes this bug.
• [249] The batch dump report API function would fail if a FFI dump had ever been generated on the system. Version C.E fixes this bug.
• [250] After changing the dump polling proxy settings to or from SOCKS, or after receiving a dump request under SOCKS, the service manager would poll twice under both SOCKS and non-SOCKS proxy settings. Version C.E fixes this bug.
• [251] Centralized dump requests submitted with any blank fields would fail if the service manager used a SOCKS proxy. Version C.E fixes this bug.

Changes

• [252] Compression pool and virtual volume data is transported on VSP Gx00/Fx00 and G1x00/F1500 systems if the microcode installed is capable of generating this data.
• [253] The installed version of Microsoft IIS Express has been upgraded from 7.5 to 8.0. Customers who have IIS Express 10.0 installed will also be able to use it with the SVP Agent.
• [254] The self-signed SSL certificate for the web dump interface has been upgraded to support SHA-256.
• [255] A new listing of all the dump files that have been transferred to HDS has been added. It can be accessed by clicking "View Transported Dump Files" on the AutoDumps tab.
• [256] A new option to send an email whenever a dump request is received has been added under the Notifications tab.
• [257] A new option to send emails as plain text only has been added to the Notifications tab.
• [258] A new option to disable transport of Hi-Track data in the regular "call-home" process has been added. It is highly recommended that this data be allowed to transfer to HDS (and that this option is not used) for improved customer support.
• [259] The default dump polling interval has been changed from every 120 seconds to every 180 seconds. Any value below 180 seconds will be ignored, and the site manager will poll every 180 seconds in this scenario.
• [260] The serial number of the affected system is now included in a SIM notification email.
• [261] SIMs generated during a daily or weekly transport will now be transported immediately to HDS rather than at the end of the transport.
• [262] A storage system that can no longer initiate communication with the site manager will no longer transport Hi-Track environment data to HDS. A healthcheck case will be opened on Siebel so that the connection issue can be investigated.
• [263] The integrated nsoftware IPWorks! SSL components have been upgraded from version 8.0 to 9.0.
• [264] The "Trigger Dump For All Subsystems" button was removed from the Service Manager GUI.
• [265] Logging for AutoDump requests and polling has been improved.

Bug Fixes

• [228] The dump lockout prevented dumps from triggering more than every 12 hours instead of 2 hours. Version C.D fixes this.
• [229] The External LDEVs information (ExtLDEV2.dat) collected on VSP Gx00 systems is incomplete. Version C.D fixes this.

Changes

• [230] Collects the parts information from FFI dump files for the VSP systems running 70-06-22/01 microcode or higher.
• [231] Collects the parts information from FFI dump files for the HUS VM (HM700) systems running 73-03-40/00 microcode or higher.
• [232] Collects the parts information from FFI dump files for the HUS VM (HM710) systems running 75-03-40/00 microcode or higher.
• [233] Adds the options to skip the transfer of Config.zip.
• [234] Adds support for TLS 1.1 and TLS 1.2 for the Dump Interface on applicable OS levels.
• [235] Adds support for TLS 1.1 and TLS 1.2 for dump polling on applicable OS levels.
• [236] Adds support for TLS 1.1 and TLS 1.2 for HTTPS and FTPS transfer on applicable OS levels.

Bug Fixes

• [214] DAT file retries don't generate success or failure messages. Version C.C fixes this.
• [215] FMD dump types on VSP G1000s are broken. Version C.C fixes this.
• [216] HUS VM systems of type HM710 don't check for SIM triggered AutoDumps. Version C.C fixes this.
• [217] HTTP Contact Methods did not register changes to the Domain Authentication option or the value of the Domain if those were the only configuration options changed in the contact method. Version C.C fixes.
• [218] Installation on a non-English language Windows OS fails when the installer configures the Dump Interface. Version C.C fixes.

Changes

• [219] Added support for VSP Gx00 High model type (VSP G800).
• [220] Added support for SOCKS HTTP proxies for transport methods and dump polling.
• [221] Added System Memory Information collection for the VSP Gx00 system type.
• [222] Added the Monitor dump type for the VSP G1000 system type.
• [223] Added the FMD and Config dump types for the VSP Gx00 system type.
• [224] Collects ORM information from VSP G1000 systems running V03 microcode or higher.
• [225] Collects the parts information from FFI dump files for the VSP G1000 systems running V03 microcode or higher.
• [226] Collects performance data from VSP, HUS VM, and VSP G1000 system types.
• [227] Hi-Track checks the VSP Gx00 identifying registry key on every BackSvc start-up instead of checking only once at install.

Bug Fixes

• [213] The Hi-Track Site Manager does not properly carry over the proxy type configuration when upgraded to C.A.. As a result, Hi-Track does not correctly recognize the proxy configuration or changes made to it. Version C.B fixes this.

Bug Fixes

• [210] The Hi-Track Dump Interface runs when it shouldn't on systems configured only as a back. Version C.A fixes this.

Changes

• [211] Adds support for the VSP Gx00.
• [212] Collects Hi-Track configuration of agents configured only as a front.

Bug Fixes

• [199] AutoDump Polling Configuration Window Hangs on Close: The AutoDump Polling Configuration sub-window of the Hi-Track Service Manager may hang for a noticeable amount of time if the Apply or Close buttons are pressed immediately after the Test button has been pressed. Version C.9 fixes this.
• [200] Selected checkboxes reset after a few seconds on the AutoDump Web Interface's Home page. Version C.9 fixes this.
• [201] The OK button doesn't appear after adding or editing a Subsystem's IPv4 or IPv6 Registration Address. Version C.9 fixes this.
• [202] A changed IPv4 or IPv6 Registration Address requires a manual restart of the SVP Agent service in order to update the Site Manager with the changed address if the SVP Agent service is running when the change is made and already registered and connected to the Site Manager. Version C.9 fixes this.
• [203] FrontSvc.ConnectToBack error messages spam the Site Manager logs upon continued failure. Version C.9 fixes this.
• [204] FrontSvc.ConnectToBack exceptions hang dump and file transfers. Version C.9 fixes this.
• [205] The Resend SIMs option resends SIMs every other day rather than every day. Version C.9 fixes this defect.

Changes

• [206] Adds support for HUS VMs configured with a Dense-60 drive boxes.
• [207] Added a Validate SSL Certificate option for polling any configured servers for dump polling. This option is disabled by default and can be found in the Hi-Track Service Manager's AutoDump Polling Configuration sub-window.
• [208] Added an Interface Configuration dialog under the Hi-Track Service Manager's AutoDumps tab from which the admin password for the AutoDump Web Interface can be reset to the default value.
• [209] Collects Protection Level Information on VSPs.

Bug Fixes

• [183] SIM report failure: Hi-Track can fail to report SIMs under these specific conditions. 1) Both dialup and IP transport methods are configured. 2) The IP transport methods configured do not work. 3) The dialup method is listed at 1st (that is at the top of) in the contact methods list. Version C.8 fixes this.
• [184] VSP G1000 SVP Agent unexpected failure: The Hi-Track SVP Agent can unexpectedly shutdown and require restart on VSP G1000 systems on which 4 or more DKC batteries are configured. Version C.8 fixes this defect.
• [185] VSP G1000 BatteryLifeEach.Dat files are incomplete: The BatteryLifeEach.dat generated by Hi-Track SVP Agent on VSP G1000 systems is incomplete. Version C.8 fixes this.
• [186] SVP Agent fails to read microcode levels upon start-up. Version C.8 fixes this.
• [187] Unread microcode level restricts DAT File Generation for DAT files whose API is microcode level dependent. Version C.8 fixes this.
• [188] FTPS contact methods fail if the Transfer to HDS Only option is configured for it. Version C.8 fixes this.
• [189] Site Managers may register an incorrect IP address for SVP Agents on a different network if the IP address of the Site Manager starts with a different octet than the SVP Agent. This is not guaranteed to happen but may occur depending on the ordering of the SVP Agent's assigned IP addresses. Version C.8 fixes this.
• [190] The SVP Agent service runs when it shouldn't on non-subsystem machines. The service starts upon restart and cannot be stopped via the Service Manager because the UI control is not enabled. Version C.8 fixes this.
• [214] SIM triggered AutoDumps don't label the generated AutoDump with the triggering SIM code. Version C.8 fixes this.

Changes

• [191] VSP G1000 does not generate BatteryLife.dat due to dropped support.
• [192] SVP Agents may explicitly specify the IP address used to register with a Site Manager if the SVP Agent is not also a Site Manager.
• [193] Added IPv6 address support. Site Managers can be registered with IPv6 from an SVP Agent exactly as an IPv4 address would be registered. SVP Agents can define IPv6 addresses to use for registration from the Subsystems tab of the Hi-Track Service Manager if the SVP Agent is not also functioning as a Site Manager.
• [194] SIM triggered AutoDumps are now appended with _auto_SIMREF where SIMREF is the SIM reference that triggered the dump.
• [195] Added support for appending SR numbers to polling triggered AutoDumps.
• [196] Enhanced dump polling to better detail what stage of the dump process the Site Manager is on.
• [197] The Dump Interface now supports batched request.
• [198] Hi-Track is now FIPSs compliant and will run as intended on Windows operating systems with that FIPS compliance enabled.

Bug Fixes

• [172] IOException hangs Hi-Track transfer: An IOException during a transfer would cause the transfer process to hang until the Site Manager was restarted. Version C.7 fixes this.
• [173] SIM transport fails with incorrect contact method: The Site Manager may fail to transport a SIM on subsequent transfer attempts if the previous attempt failed due to an incorrectly setup contact method. Version C.7 fixes this.
• [174] HUS VM unable to determine the system type after install: The API used to generate BatteryLife.dat is not supported on the HUS VM systems. Version C.7 eliminates BatteryLife.dat generation for HUS VM systems.
• [175] The AutoDump Web Interface on Windows Server 2012 R2 or Windows 8.1: The AutoDump Web Interface component does not display on either Windows Server 2012 R2 or Windows 8.1. Version C.7 fixes this.
• [176] The AutoDump Web Interface error page: The error page for the AutoDump Web Interface does not display normally. Version C.7 fixes this.
• [182] VSP G1000 DAT generation halts on LuPath.dat: The SVP Agent hangs may hang on generation of LuPath.dat. Version C.7 fixes this.

Changes

• [177] VSPG1000 Support Added: VSPG1000 systems are officially supported in version C.7.
• [178] Collecting BatteryLifeEach Information: On HUS VM systems, Hi-Track uses an API to collect the life information of each battery.
• [179] Adding an SR to AutoDumps generated from the Web Interface: Users may now attach an SR number to an AutoDump request submitted by the AutoDump Web Interface.
• [180] Concurrent SIM transfer and AutoDump generation: AutoDump generation submitted by either the GUI or AutoDump Web Interface no longer blocks SIM transfer until the dump is generated.
• [181] The MakeHiTrackDb utility defaults: The MakeHiTrackDb utility now points towards default installation locations.

Bug Fixes

• [159] HUS VM SIM data corrupt: SIM messages transferred to Hi-Track from an HUS VM system with a serial number with leading zeros (after the leading "2" — i.e. "201234") were unreadable by the Hi-Track server. Version C.6 fixes this.
• [160] HUS VM unable to determine the system type after install: The SVP Agent for an HUS VM system is unable to determine the system type upon a fresh install. Version C.6 fixes this.
• [161] HiTrackLogs.zip fails to close: An open log file fails to zip during a transfer, causing the transfer to fail. Version C.6 fixes this.
• [162] SIMs Report When They Should Not: SIMs reported to the Hi-Track Center regardless of the front's "Report SIMs" setting. Version C.6 fixes this.
• [163] HUS VM SIM Emails Not Sent: SIMs reported to the Hi-Track Center were not emailed to their designated recipients. Version C.6 fixes this.
• [164] HUS VM Serial Truncation: The serial numbers of HUS VMs dropped the leading '2' after certain UI interactions. Version C.6 fixes this.
• [165] Duplicated localhost Subsystem Upon Install: The localhost subsystem entry is added twice to subsystems upon initial install. Occurs very rarely. Version C.6 fixes this.

Changes

• [166] Collecting DKU Type Information: On HUS VM systems, Hi-Track uses a new API to collect the life information of each battery.
• [167] Trigger AutoDumps from the Service Manager: AutoDumps can be generated and transferred to the Hi-Track Center from the Service Manager by either targeting a specific subsystem or all subsystems monitored by a Site Manager. This feature is supported on USP V/VM, VSP, and HUS VM.
• [168] Trigger AutoDumps from a Web Interface: AutoDumps can be generated and transferred to the Hi-Track Center from a web interface if this feature is enabled on the Site Manager's Service Manager. This feature is supported on USP V/VM, VSP, and HUS VM.
• [169] Trigger AutoDumps by SIM reference code: If enabled in the Service Manager, AutoDumps can be automatically generated and transferred to the Hi-Track Center if a reported SIM reference code matches one that's listed in the SIM AutoDump parameter file. This feature is supported on USP V/VM, VSP, and HUS VM.
• [170] Includes Pre-populated HTTPS, FTPS, and FTP Contact Methods in the "Add Contact" dialog for the Hi-Track Service Manager.
• [171] Changed Contact Method Passes to rotate through defined contact methods rather than try each method a specific number of times before moving on to another. Preference is given to IP transport methods and if these all fail within a timeout period then Dial-up transport methods are attempted. In addition, the default retries configuration parameters only apply to the dial-up transport methods. The IP transport methods are looped through where applicable until a transport timeout period elapses.

Bug Fixes

• [157] VSP systems failing daily transfers: Under some circumstances Hi-Track Agent version C.4 on VSP systems running some versions of V-04 microcode would crash during file generation and fail to transfer data files to the Hi-Track Center. Version C.5 fixes this problem.

• [158] Hi-Track Service Manager application prevents log off: Hi-Track Agent version C.4 installed on systems other than SVPs prevented the user from logging off of a console session unless the Service Manager application was closed. Version C.5 fixes this problem.

Bug Fixes

• [149] Dial-up incidental calls send wrong micro-code version for back systems: Under some circumstances a dial-up incidental call would report an incorrect microcode version for remote systems reporting a SIM. Hi-Track C.4 fixes this issue.

Changes

• [150] Support for HUS VM systems: Hi-Track was updated in C.4 to support HUS VM storage systems.
• [151] Collecting Storage System Data in XML format: on HUS VM systems or VSP systems with micro-code version 7004000000 and above, Hi-Track calls the appropriate API functions to collect storage configuration data such as package information as well as SSB and SIM data. Moreover, Hi-Track transports these new XML data files during the daily and weekly data transports.
• [152] Collecting Pool Information Ex2: On HUS VM systems or VSP systems with micro-code version 7004000000 and above, Hi-Track uses a new API to collect the �ex2� version of the HDP pool data.
• [153] Collecting License Information Ex: On HUS VM systems or VSP systems with micro-code version 7004000000 and above, Hi-Track uses a new API to collect the �ex� version of License data.
• [154] Collecting Each Battery Life Information: On HUS VM systems or VSP systems with micro-code version 7002500000 and above, Hi-Track uses a new API to collect the life information of each battery.
• [155] Additional information included in SIM notification emails: Additional information including error location and HDD serial number (when applicable) is now included in notification email messages if the system is configured for email notification.
• [156] Changed the Service Manager application to support minimize, restore, display in taskbar, and to not enforce an "always on top" window state.

Bug Fixes

• [147] SVP Agent Service (BackSvc.exe) consumes a high percentage of CPU time: In Hi-Track C.2, if the SVP agent service runs continuously for a long period of time, it would eventually uses near 100% of the CPU. As a result, the Hi-Track application may not be able to write to log files or transport data to the center. We have reports indicating that the issue has occurred as early as 30 days after starting the SVP agent service. Hi-Track C.3 fixes this.
• [148] Email Notification for Simultaneous SIMs: If simultaneous SIMs occur on an SVP, previous versions of Hi-Track may not send email notification for all of them. Hi-Track version C.3 was modified to send notification emails for all SIMs, including those that occur simultaneously.

Bug Fixes

• [136] Upgrading Hi-Track: When installing Hi-Track C.1 on a system that is running a previous version of Hi-Track, the C.1 installer incorrectly displays a message indicating that Hi-Track C.1 is already installed and prompts the end-user to either repair or remove Hi-Track. In C2, Removing the previous version of Hi-Track is part of the installation process and does not require user intervention.
• [137] SIMS Email Notification: Prior to version C.2, Hi-Track failed to send SIMS notification emails when deployed on a stand-alone system. Hi-Track C.2 fixes this.
• [138] SMTP authentication: In previous versions of Hi-Track, users could specify the email server username and password in the Notification tab but the Hi-Track application did not forward the authentication credentials to the SMTP mail server. Version C.2 correctly sets the username and password if the SMTP server requires authentication.
• [139] Site Manager Handle Count: if a dialup transport is defined as the only contact method and none of the dialup succeeds, the Hi-Track Site Manager consumes many file handles without releasing them. this is resolved in version C.2.
• [140] Proxy Server Domain Authentication: Hi-Track version C.2 was modified to support domain authentication for proxy servers.

Changes

• [141] Transporting Uncompleted SIMS: Hi-Track sends a list of uncompleted SIMs to the center during data transfer.
• [142] Manual Contact Method: Hi-Track C.2 introduces a new contact method called Manual that stores the collected data in the c:\HDS\FtpStage instead of sending it to the Hi-Track center.
• [143] Configurable SMTP Port: Allows users to specify the SMTP port for email event notification. The default port is 25.
• [144] HTTPS as Default Transport Method: Previous versions of Hi-Track were pre-configured with a dial-up transfer method. This has been changed in C.2 and Hi-Track displays a generic HTTPS connection as the preferred transfer method. As a result, �Answer incoming calls� and �Enable RAS dial-back� checkboxes are in the unchecked state by default.
• [145] Notification by SIM Severity: In version C.2, the Hi-Track application can be configured to send email notification based on the severity of SIMs.
• [146] Validating SSL Certificate: Previous versions of Hi-Track rejected SSL certificates that were signed by untrusted authorities. Therefore, it was not possible to employ the HTTPS method to transfer data to servers with self-signed SSL certificate. In version C.2, Hi-Track can be configured to skip the server certificate validation process and transfer data to any web server via HTTPS.

Bug Fixes

• [124] Collection of LUSE data: Prior to version C.1, Hi-Track did not completely retrieve the data about configured expanded LUSE. Version C.1 calls the appropriate APIs to collect all the LUSE information. It will gather the configured LUSE data on all the large RAID SVP types.
• [125] Log sizes grow unexpectedly: There was one report suggesting that the Hi-Track log file size becomes too large and takes all the C drive space. To prevent this rare incident from happening, Hi-Track was modified to check the log size before writing to it. In version C.1 or later, Hi-Track will overwrite the log file if the file size exceeds 2 megabytes.
• [126] Failing to FTPS to Solaris FTP Server: In rare occasions, Hi-Track reports an error when sending data via FTPS to Solaris FTP servers. Further investigation revealed that the error occurs on logoff event after data transfer is completed. Hi-Track version C.1 resolves this issue.
• [127] Stopping Site Manager Service: If there is no modem attached to the Hi-Track host system, the Site Manager Service cannot be correctly stopped as it is waiting for a reply from an absent modem. Hi-Track C.1 resolves this issue.
• [128] Reporting SSB data: Prior to version C.1, Hi-Track was not able to report all SSB data when the primary transfer protocol was HTTPS or FTP. This issue has been resolved in version C.1 and Hi-Track successfully transfers the SSB information to the center using HTTPS or FTP.
• [#] Standby SVP Agents don't switch to primary: For dual SVPs, when the primary SVP Agent fails, the standby SVP agent does not automatically switch to a primary. Switching requires manually restarting the standby SVP Agent's service. Hi-Track C.1 resolves this issue.

Changes

• [129] Support for VSP systems: VSP is the latest system of the large RAID family of HDS storage products. Hi-Track was updated in C.1 to fully support VSP storage systems.
• [130] Dial-up configuration on VSP: Hi-Track does not support dial-up data transfer or RAS dial-back by default on VSP storage systems as these systems do not have a built-in modem. However, users can optionally install one of the modems that is supported by Hi-Track (please refer to the Hi-Track help document for the list of Hi-Track approved modems). In version C.1, the Hi-Track Service Manager is able to detect whether the host platform is equipped with a modem. It allows dial-up data transfer and RAS dial-back only if finds a modem on the startup event.
• [131] Hi-Track Installation Location: In C.1, the Hi-Track installer will prompt the end-user to select a target installation directory. The default folder is �C:\Program Files\Hitachi Data Systems\Hi-Track\� for USP V/VM, NSC, and USP. For VSP, the default folder is �C:\Program Files (x86)\Hitachi Data Systems\Hi-Track.�
• [132] FTPS to non-HDS Centers: Prior to version C.1, Hi-Track was able to only transfer data securely to HDS centers. This restriction has been modified in version C.1 and Hi-Track can send data to any server using the FTPS transfer protocol. To use FTPS to send data to a non-HDS center, uncheck the box labeled Transfer to HDS only on the FTP Method Properties panel.
• [133] Collecting and Transporting csv.zip: If the appropriate command-line tool is installed on an SVP, Hi-Track will call it to collect the csv.zip data. Similar to dat.zip and config.zip, the csv.zip is stored in c:\hds and sent to the HDS center during data transfer.
• [134] SVP Agent Connectivity Test: In Hi-Track version B.D to C.0, any Vista computer failed the Ping portion of the SVP Agent Connectivity Test facility of the Hi-Track Service Manager. Hi-Track version C.1 was updated to resolve this problem.
• [135] Collection of SVP Antivirus data: Starting with version C.1, Hi-Track uses a different method to retrieve information from any antivirus installed on the host system. The new method works on all SVP types.

Bug Fixes

• [117] FCGS Symbolic data collection caused Hi-Track failures: Item #116 in version B.F was modified to only generate FCGS symbolic data if the USPV/VM subsystem is at or above the V04+1 microcode level. A workaround that was offered for this problem was to uncheck the box in the Service Manager program to disallow collection of FCGS data. If you cleared this checkbox to work around the problem, please replace the check in the checkbox after upgrading to C.0 and test a full transfer (including new file generation) to the Hi-Track Center. Watch both the Site Manager log and Agent log during file generation and transfer to ensure that it completes without errors.
• [118] Testing transfers in the Service Manager: If a user initiated a test Daily transfer in the Service Manager program and the day of the week was the same as the day of the week the system was configured to do weekly transfers, the call type would be changed to Weekly.
• [119] System Busy message: When attempting to initiate a data transfer to the Hi-Track Center while connected through a RAS session, the Hi-Track agent would respond that the system was busy regardless of the configured transport methods. Version C.0 will allow a transfer provided that the primary transport method is not dialup.

Changes

• [120] Collection of HDP data: A new API was added for USPV/VM systems to collect information about configured HDP pools and volume information. This API will be called and the data collected for systems running microcode versions V05 and above. This information is displayed on the Hi-Track web pages for USP V and USP VM systems configured with HDP pools and volumes.
• [121] FTP data transfers changed to PUT: For historical reasons, in the past FTP transfers to the Hi-Track Center have appended files to the Hi-Track FTP servers. With this version FTP transfers have been changed to uploads which will overwrite any existing files. This change will prevent misconfigured agents from causing problems with the Hi-Track FTP servers.
• [122] Installer change: A change was made to the agent bootstrap installer to automatically remove previous versions of the Hi-Track agent before installing a new version. This should result in a higher success rate for upgrade installs.
• [123] Return value from dialup command changed: The return value for a dialup Center command was changed in this version to acknowledge the command sent.