HP 8/20q HP StorageWorks Simple SAN Connection Manager 3.20 Release Notes (569 - Page 6
EVA issues, MSA1x00 issues, Switch issues
View all HP 8/20q manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 6 highlights
3. Select the second tab, Discover Multi-Paths. The MSA2000 should appear as HP LOGICAL VOLUME in the Others section in the Device Hardware ID. 4. Select the HP LOGICAL VOLUME entry, and then click Add. EVA issues • EVA configuration: SSCM has the following restrictions when managing an EVA array: • SSCM cannot remove host definitions from the EVA. • After adding a port to a host definition, SSCM cannot remove the port. • HP Command View EVA offers flexibility in the configuration of an EVA. However, SSCM may not operate as expected if an array was configured using HP Command View EVA. You can use either SSCM or HP Command View EVA to configure an array, but not both. Note that you can use HP Command View EVA to delete unwanted entries in an array's configuration (such as a host or port that has been physically removed). • EVA login account: If the EVA login user name is changed, use the HP VDS Configuration Utility for EVA to re-enter the new user name and password. This utility is installed with the EVA VDS hardware provider and can be launched from Start > Programs > Hewlett-Packard > Hardware Providers. • EVA4400 not discovered on startup: The EVA4400 is not discovered on startup of SSCM. Workaround: If your SAN contains an EVA4400, ensure that all HP Command view EVA installations in the SAN are running HP Command View EVA 8.0 or later. 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 6