HP 8/20q HP StorageWorks Simple SAN Connection Manager 2.10 release notes (569 - Page 5

EVA-specific issues - manual

Page 5 highlights

Workaround: Manually unmount the installation CD. For example, if the CD was auto-mounted in /media/HpInstallx.x, issue the following commands to remount the CD: # unmount /media/HpInstallx.x # mkdir -p /mnt/cdrom # mount /dev/cdrom /mnt/cdrom If the unmount command fails with a busy warning, make sure you have closed all applications and consoles that could be using the CD media. • On Microsoft Windows Server 2008 the MSA2000 uses the native Microsoft MPIO. Perform this procedure for all Windows 2008 systems in your SAN to configure MPIO. nl To activate MPIO: nl 1. Click Start > Settings > Control Panel. 2. Double-click the MPIO icon. 3. Select the second tab, Discover Multi-Paths. 4. The MSA2000 appears in the Others section in the Device Hardware ID. 5. The MSA2000 should appear as HP LOGICAL VOLUME. Select this entry and then click Add. • Windows Server 2008 upgrade issue: Performing an upgrade from a previous installation on the Windows Server 2008 will cause two components (MSA2000 MPIO and SES drivers) to fail to install. Workaround: These components are not needed by the Windows Server 2008. Please ignore the failure of those components during an upgrade from a previous version. EVA-specific issues • EVA configuration: The SSCM has the following restrictions when managing an EVA array: • Host definitions cannot be removed from the EVA by the SSCM. • Once a port (HBA) has been added to a host definition, the port cannot be removed by the SSCM. • HP Command View EVA offers great flexibility in how a user can configure an EVA. However, the SSCM may not operate as expected if an array was configured using HP Command View EVA. A user should use SSCM or HP Command View EVA to configure an array, but not both. NOTE: Using HP Command View EVA to delete unwanted entries in an array's configuration (such as a host or port that has been physically removed) is supported. • 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: EVA4400 is not discovered on the startup of SSCM. Workaround: If your SAN contains an EVA4400, ensure that all HP Command View installations within that SAN are running HP Command View 8.0 or later. HP StorageWorks Simple SAN Connection Manager 2.10 release notes 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8

Workaround:
Manually unmount the installation CD. For example, if the CD was auto-mounted in
/media/HpInstallx.x
, issue the following commands to remount the CD:
# unmount /media/HpInstallx.x
# mkdir —p /mnt/cdrom
# mount /dev/cdrom /mnt/cdrom
If the unmount command fails with a busy warning, make sure you have closed all applications
and consoles that could be using the CD media.
On Microsoft Windows Server 2008 the MSA2000 uses the native Microsoft MPIO. Perform this
procedure for all Windows 2008 systems in your SAN to configure MPIO.
nl
To activate MPIO:
nl
1.
Click
Start
>
Settings
>
Control Panel
.
2.
Double-click the MPIO icon.
3.
Select the second tab,
Discover Multi-Paths
.
4.
The MSA2000 appears in the
Others
section in the Device Hardware ID.
5.
The MSA2000 should appear as HP LOGICAL VOLUME. Select this entry and then click
Add
.
Windows Server 2008 upgrade issue:
Performing an upgrade from a previous installation on the
Windows Server 2008 will cause two components (MSA2000 MPIO and SES drivers) to fail to
install.
Workaround:
These components are not needed by the Windows Server 2008. Please ignore the
failure of those components during an upgrade from a previous version.
EVA-specific issues
EVA configuration:
The SSCM has the following restrictions when managing an EVA array:
Host definitions cannot be removed from the EVA by the SSCM.
Once a port (HBA) has been added to a host definition, the port cannot be removed by the
SSCM.
HP Command View EVA offers great flexibility in how a user can configure an EVA. However,
the SSCM may not operate as expected if an array was configured using HP Command View
EVA. A user should use SSCM or HP Command View EVA to configure an array, but not both.
NOTE:
Using HP Command View EVA to delete unwanted entries in an array's configuration (such as a
host or port that has been physically removed) is supported.
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:
EVA4400 is not discovered on the startup of SSCM.
Workaround:
If your SAN contains an EVA4400, ensure that all HP Command View installations
within that SAN are running HP Command View 8.0 or later.
HP StorageWorks Simple SAN Connection Manager 2.10 release notes
5