Other Issues; Switch Issues - HP 8/20q Release Note

MSA1x00-specific issues
• MSA LUN name between Array Configuration Utility (ACU) and SSCM does not match: LUN names
created by the MSA ACU and the 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 the HP
•
StorageWorks SSCM has a memory leak that may increase over time when VDS operations are
exercised. To reclaim lost memory, close SSCM to unload the MSA hardware provider. Check
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 its HBA agent software is still busy.
Workaround: If this occurs, either re-launch 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 the Simple SAN
Connection Manager, SSCM remembers the password and will not prompt for one whenever 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: The 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

• The graphics for the MSA and EVA are not accurate: The storage subsystem graphics in the Manage
Storage Subsystem dialog box are meant only as an abstract representation of the MSA and EVA
storage subsystems and their enclosures and drives. The graphic images do not actually reflect
the physical layout of the subsystems.
• LUN multipath Information: A LUN's multipath information is available only if that LUN is presented
to the management host where 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 config-
uration 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.
• SSCM fails to start: If the user installs SSCM with the MSA only option and HP Command View
EVA is installed, the SSCM will be unable to start. The error RegOpenKeyEx failed with
error 2: The system cannot find the file specified is displayed when the user
attempts to start the SSCM.
6