HP StoreEver Command View for Tape Libraries (CVTL) v. 3.7 and Interface Manager Firmware v I274 Release Notes

Upgrading Command View for Tape Libraries reports an error "Setup could not uninstall
CIMOM"
Symptom: Upgrading from any previous release of Command View for Tape Libraries to version 2.2
or above may report an error message when upgrading the HP SMI-S Tape Provider that reads "Setup
could not uninstall CIMOM". Clicking "OK" on this message continues with the upgrade and version
2.2 of Command View for Tape Libraries is correctly loaded. Any future attempt to uninstall Command
View for Tape Libraries also report this error. The HP SMI-S Tape Provider is still installed at the previous
version.
Workaround: Command View for Tape Libraries must be uninstalled before the full upgrade to 2.2
can succeed without errors. If you have already seen this error and have continued with the upgrade,
please take the following steps:
• Uninstall Command View for Tape Libraries through the "Add or Remove Programs" section of
your Control Panel. You will see the same error message when uninstalling - click "OK".
• Uninstall the "HP StorageWorks SMI-S CIMOM" program in the "Add or Remove Programs"
section of your Control Panel.
• Re-install the 2.2 version of Command View for Tape Libraries - this install should not report the
same error message.
Found in version: 2.2 (and above versions of 2.x)
Cannot communicate with Interface Manager after migrating to 2.x or after replacing
the Interface Manager card
Symptom: This issue can exhibit itself immediately after migrating to 2.x or after physically replacing
the Interface Manager card in 2.0 or higher on an ESL E-Series library. Command View for Tape
Libraries cannot communicate with the Interface Manager and attempting to telnet to the Interface
Manager card shows the message "Interface Manager Communication Failure" and will not allow
you to login.
Workaround: If you are running (or have just migrated to) I220 or higher of the Interface Manager
code, reboot the entire library. Those running I200 of the Interface Manager will need to place a
support call.
Found in version: 2.0 (and above)
Mapping an LTO4 drive defaults to using port 0 even when there is no cable on port 0
Symptom: When providing a host with access to an LTO4 drive, the default behavior is to allow access
on port 0 (port A on the drive) even though there is no cable connected on that port.
Workaround: If you wish to use port 1 (port B on the drive), enable custom mapping on the Secure
Manager page on the Configuration tab and edit the custom map for a particular host.
Found in version: 2.2 (and above)
Events found in the library logs cannot be found in the Interface Manager log
Symptom: Block of events showing up in the libraries log or on the front panel are missing from the
Interface Manager alert log. The alert log only holds 100 informational, 100 warning, and 100 critical
events from each device.
Workaround: None. It may seem like blocks of events are missing, however this is not necessarily the
case. Informational, warning, and critical events are all generated by the device at different rates.
Found in version: 2.0 (and above) and 1.82 (port 18098 is not required)
Removing drives or Interface Controllers leave the library in a Critical state
Symptom: If you remove any drives or Interface Controllers, the removed drives and Interface Controllers
show up in a Critical state. The status details complain about not being able to communicate with the
Workarounds 37