Patch: update-is931002 built on 3Nov15-17:13:08 Product: VTL v8.20 Build 9310 Areas Affected: FC Target, Replication, Tape, Performance, Email Alerts, CLI, Service, Auto-save Prerequisite: None Behavior: Interruptive; stops the server modules if running, copies binaries, and restarts the server modules; cannot be rolled back. Mandatory for: - All new installations - Next time maintenance is performed on existing installations - Servers experiencing issues related to affected areas FIXES: ------ FC Target: - Symptom: A Fibre Channel HP-UX client does not detect storage devices. - Cause: When VSA was enabled for an HP-UX client, an incorrect reply was sent for inquiry commands. - Resolution: Correct the inquiry command reply. - Severity: Medium - Files: fsqltgt2xxx.ko fsqltgt2xxx_mid.ko - References: TS90875 BZ33815 Replication: - Symptom: Replication of a deduplicated tape fails with a SCSI error. - Cause: Based on the amount of data on the primary tape, the replica tape required expansion but it failed due to an invalid check for a deduplicated tape in the End of Media condition. - Resolution: Change the logic to ensure expansion of the replica tape. - Severity: Medium - Files: tlecore.ko - References: TS90332 BZ34229 Tape: - Symptom: An error message is displayed on the console during tape migration with the force option even though the migration completes. - Cause: The return value of a function was not initialized correctly. - Resolution: Initialize the return value of the function. - Severity: Low - Files: ipstorcomm - References: TS86757 BZ33905 - Symptom: A utility used to move tapes from the vault to tape libraries takes a long time to complete. - Cause: There was a wait period of 30 seconds before attaching or detaching a tape. - Resolution: Reduce the wait period to one millisecond. - Severity: Low - Files: ipstorcomm - References: TS91220 BZ34021 - Symptom: Deduplication repository space reclamation fails on the replication target server with a missing hash error. - Cause: The deduplication repository was full on the replication target server when incoming replication was resolving a large tape for more than one hour; tape resolution failed and left an invalid folder. - Resolution: Abandon invalid folders generated after a failure. - Severity: Low - Files: sirreptargd - References: TS85134 BZ33758 - Symptom: The drive density code of an IBM 3580 LTO6 virtual drive assigned to an i Series client shows only Ultrium5 and not Ultrium6i. - Cause: Drive emulation did not fully match with the physical tape drive properties. - Resolution: Complete the return data for the tape Inquiry command. - Severity: Low - Files: tlecore.ko - References: TS90095 BZ33759 Performance: - Symptom: Importing a tape via Fibre Channel is slow. - Cause: The tape was exported using a block size larger than 64 KB and without 4-byte alignment. - Resolution: Correctly handle large unaligned blocks to prevent performance issue at the FC initiator level. - Severity: Low - Files: tlecore.ko - References: TS90741 TS102304 BZ34290 Email Alerts: - Symptom: Email Alerts are received for stopped modules on the standby node. - Cause: In an active-passive failover setup, the standby node was checking the status of modules unnecessarily. - Resolution: Skip the service status check on the standby node. - Severity: Low - Files: serverstatus.sh - References: TS90865 BZ33873 CLI: - Symptom: The CLI command 'createvirtualtape' does not create a numeric barcode for a tape when a barcode range is specified. - Cause: The CLI did not handle the case of a specific barcode range. - Resolution: Add logic to create a tape with a numeric barcode within a specific barcode range. - Severity: Low - Files: iscon isscon - References: TS90764 BZ33709 - Symptom: The CLI command 'getphysicaltapelist' does not show stacked tape information. - Cause: When there was an unoccupied physical slot before the one used for tape stacking, a wrong slot number was used to update the tape stacking information. - Resolution: Use the correct physical slot number to store tape stacking information. - Severity: Low - Files: tlecore.ko - References: TS103725 BZ34288 Service: - Symptom: Stopping services while I/O is occurring results in a kernel error. - Cause: An invalid memory location was accessed. - Resolution: Check memory locations before referring to them. - Severity: Low - Files: kipstor.ko - References: BZ34213 Auto-save: - Symptom: Performing an Auto-save operation of the server configuration to an FTP server displays an error in the system log. - Cause: There was a syntax error in the auto-save scripts. - Resolution: Fix the syntax error. - Severity: Low - Files: saveconfig_setup_sftp.pl saveconfig_setup.pl - References: TS104358 BZ34395