Known issues

This section details the known issues in version 2.3.0, along with possible workarounds (if workarounds are available).

Ticket ID Description
SCOM-238811 The detection of DS8000® storage systems stops if volumes on these systems have names with non-ASCII characters.

Currently there is no workaround or solution for this limitation (SCOM-238811).
SCOM-260923 In some cases, the monitoring host can not be discovered after a certain IBM® management pack is manually deleted and then and imported again.

To resolve this issue, delete the same management pack again and then import it again. Alternatively, you can shorten the management pack object discovery interval to 30 seconds or less (for more information, refer to the relevant Microsoft SCOM documentation).
SCOM-261133 After upgrading to the latest version by installing it over version 1.1.0, the configuration that was made with version 1.1.0 is no longer valid.

To resolve this issue, run the upgrade_config.cmd CLI utility after to the latest version is installed. For more information, refer to the user guide.
SCOM-261147 For SAN Volume Controller and Storwize® systems, the same event might be displayed several times under Events, each time with a different timestamp. This occurs if the event is reported by the storage system each time with an updated timestamp.

This is a design behaviour that might be changed in a future management pack version.

Currently there is no workaround or solution for this limitation (SCOM-261147).
SCOM-261151 Physical drives with an empty enclosure ID are not displayed for Storwize V3500 or Storwize V3700 systems.

Currently there is no workaround or solution for this limitation (SCOM-261151).
SCOM-261196 XIV® volume information is not updated after the volume is migrated to another storage pool.

To resolve this issue, remove the XIV storage system and then add it again by using the scomu.cmd utility.
SCOM-261197 Information regarding the relationship between FlashCopy® consistency group and FlashCopy mapping is not updated for Storwize systems.

Currently there is no workaround or solution for this limitation (SCOM-261197).
SCOM-261198 For IBM Flex System® systems, only the target volume is displayed in the FlashCopy mapping relationship list.

Currently there is no workaround or solution for this limitation (SCOM-261198).
SCOM-261200 The IBM Storage Management Pack only works when the SCOM Root Management Server (RMS) and SCOM agents reside in the same domain.

Currently there is no other workaround or solution for this limitation (SCOM-261200).
SCOM-261238 The digital signature cannot be verified in Windows 2008.
SCOM-261242 The status of the SAN Volume Controller iSCSI port or Storwize iSCSI port is incorrect if the port is configured and the state of the link is not active.