HP 353803-B22 HP StorageWorks Simple SAN Connection Manager 2.20 release notes - Page 6

MSA1x00 issues • MSA LUN name between Array Configuration Utility (ACU) and SSCM does not match: LUN names created by the MSA ACU and SSCM do not match when displayed. The ACU LUN name is partly shown in SSCM as LUN identification. • MSA hardware provider memory leak: The HP MSA hardware provider installed with SSCM has a memory leak that may increase during VDS operations. To reclaim lost memory, close SSCM to unload the MSA hardware provider. See the HP website for updates to the HP MSA hardware provider. • Hosts connecting to MSA storage subsystems may not be discovered by SSCM during fabric changes: When MSA responds to a fabric event (such as zoning changes) the HBA agent software takes some time to discover the MSA storage subsystem. When the system is in this state, and SSCM is launched, it may not discover the host because the HBA agent software is still busy. Workaround: If this occurs, either relaunch SSCM after a few minutes or refresh the server list, and/or manually add the server. Switch issues • SSCM and switch passwords: If the switch password is set up or updated using SSCM, SSCM remembers the password and does not prompt for one when a switch operation is initiated. However, if you set up or change the password in another application (such as QuickTools), SSCM cannot retrieve the switch information when launched. SSCM shows the default generic switch name, and any switch operation that you request will prompt for the password. • SSCM shows switch zoning information as Unknown for vendor and device type: SSCM uses the switch zoning component Fibre Channel worldwide port name (WWPN) to match the vendor and device type. If the switch zoning is not WWPN based, it shows the information as Unknown in the Switch Zoning Information dialog box. Other issues • Graphics for the MSA and EVA are not accurate: The storage subsystem graphics in the Manage Storage Subsystem dialog box are intended as an abstract representation of the MSA and EVA storage subsystems and their enclosures and drives. The graphic images do not reflect the physical layout of the subsystems. • LUN multipath information: A LUN's multipath information is available only if the LUN is presented to the management host on which the VDS hardware provider and SSCM are installed and running. Workaround: To obtain multipath information for LUNs presented to other hosts, issue the hpdsm devices command from either the EVA DSM command line interface (CLI) or the MSA DSM CLI on that host. • To launch the EVA DSM, select Start > Programs > Hewlett-Packard > EVA DSM > HPDSM CLI. • To launch the MSA DSM, select Start > Programs > Hewlett-Packard > MSA DSM > HPDSM CLI. • SSCM startup: SSCM may take several minutes to start up. The size of your SAN and the configuration of your storage directly affects the startup time. SSCM uses an Ethernet broadcast mechanism to discover the hosts and their HBAs in the SAN. If there are a large number of hosts in the network responding to this broadcast, the host discovery process may take some time to complete. 6