Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
When changing firmware
Because each firmware revision contains new features, some configuration settings are not retained
when earlier firmware versions are loaded. HP recommends against downgrading firmware unless
instructed to do so by an HP Support engineer. Always verify configuration settings after installing
firmware.
Failover license names change
As of June 10, 2014 the control path failover and data path failover licenses have new product names.
The product numbers remain the same. The appearance in the RMI and behavior of the licenses within
the library remain the same. Each license, regardless of the name, supports both advanced path
failover and basic path failover with 4.30 and later firmware versions.
Table 1 Failover license names
SKU Number
License name before June 10, 2014
License name as of June 10, 2014
TC359A
HP StoreEver MSL6480 Control path failover License HP MSL6480 High Availability Control Path Failover
License
TC359AAE
HP StoreEver MSL6480 Control path failover
HP MSL6480 High Availability Control Path Failover
E-License
License
TC360A
HP StoreEver MSL6480 Data path failover License
HP MSL6480 High Availability Data Path Failover
License
TC360AAE
HP StoreEver MSL6480 Data path failover E-License HP MSL6480 High Availability Data Path Failover
E-License
Fixes
•
Resolved a case where the RMI would log out with a disconnect error when using specific browsers.
•
Upgraded the Bash protocal version to address “ShellShock” vulnerabilities.
Known issues and workarounds
•
Issue: After upgrading to 4.30 or later firmware from 4.10 or an earlier firmware version, the
library or drive encryption settings may not remain configured as expected.
Workaround: After upgrading the library firmware, verify that the encryption configuration settings
(Configuration > Encryption) are correct and that the Drive Encryption status (Status > Security)
shows the expected encryption enabled state. If the encryption configuration setting or drive
encryption status is incorrect, reconfigure the encryption settings.
•
Issue: Pulling on the magazine handle while the library is unlocking the magazine can damage
the library.
Workaround: When opening a magazine, wait until the OCP or RMI says that the magazine is
unlocked before attempting to remove it.
•
Issue: A cartridge is left in a drive during Data Verification operations.
Issue: Tape Assure Advanced does not display the entire bar code.
Workaround: Check the length of the bar code on the cartridge. When using library firmware
4.50 and earlier versions, Data Verification and Tape Assure Advanced do not support bar codes
with more than 12 total characters (including the media ID).
•
Issue: When using SNMPv1 or v2 with 4.40 or 4.50 library firmware, configuring the community
string to a value other than the default of “public” does not take effect.
Workaround: SNMP must be restarted on the library before the new community string will take
effect.
4
Fixes
...