HP 353803-B22 HP StorageWorks Simple SAN connection manager release notes (569 - Page 6

Refresh the Server List, IA64 BIOS update

Get HP 353803-B22 - StorageWorks Modular Smart Array 1000 SAN Starter PDF manuals and user guides
UPC - 808736781619
View all HP 353803-B22 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 6 highlights

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 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 you install SSCM with the MSA only option, and HP Command View EVA is installed, SSCM will fail to start. The error RegOpenKeyEx failed with error 2: The system cannot find the file specified is displayed when you attempt to start SSCM. Workaround: To correct this problem, reinstall SSCM and select the EVA only or the EVA and MSA option if an array is present in the configuration. If no EVA is present, remove the HP Command View EVA suite. • IA64 BIOS update: The HBA driver update feature for Windows on IA64 is not supported in SSCM. • Format drive message: During partition creation and formatting for LUNs for Windows Server 2008, a Windows Format Drive message is displayed to confirm formatting or cancel. Workaround: None. This message will not impact the operation, but a new confirmation window is displayed for each new partition. Click Cancel to close the window. • Server name changes: If the name or another attribute of a server being managed by SSCM is changed independent of SSCM, SSCM continues to display the original name, even after restarting. The server change is not detected until a Server Refresh is performed because SSCM matches up the HBA WWN with the saved server data. The saved server data is not updated until a new broadcast or FDMI refresh is performed. A server refresh is not performed on application startup or asynchronously while the application is open. Workaround: To see the new server name, use the Refresh the Server List option. • Creating partitions on the management station: Deleting LUNs presented to the management station may cause errors if new LUNs are created immediately after the old LUNs are deleted. The new LUNs may not be initialized and a drive letter not assigned. Workaround: Reboot the management station after deleting any LUNs that were presented to the management station. Then, perform the template deployment or creation of any new LUNs. 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
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 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 you install SSCM with the MSA only option, and HP Command View EVA
is installed, SSCM will fail to start. The error
RegOpenKeyEx failed with error 2: The
system cannot find the file specified
is displayed when you attempt to start SSCM.
Workaround:
To correct this problem, reinstall SSCM and select the EVA only or the EVA and
MSA option if an array is present in the configuration. If no EVA is present, remove the HP Com-
mand View EVA suite.
•
IA64 BIOS update:
The HBA driver update feature for Windows on IA64 is not supported in SSCM.
•
Format drive message:
During partition creation and formatting for LUNs for Windows Server
2008, a Windows
Format Drive
message is displayed to confirm formatting or cancel.
Workaround:
None. This message will not impact the operation, but a new confirmation window
is displayed for each new partition. Click
Cancel
to close the window.
•
Server name changes:
If the name or another attribute of a server being managed by SSCM is
changed independent of SSCM, SSCM continues to display the original name, even after restarting.
The server change is not detected until a
Server Refresh
is performed because SSCM matches
up the HBA WWN with the saved server data. The saved server data is not updated until a new
broadcast or FDMI refresh is performed. A server refresh is not performed on application startup
or asynchronously while the application is open.
Workaround:
To see the new server name, use the
Refresh the Server List
option.
•
Creating partitions on the management station:
Deleting LUNs presented to the management station
may cause errors if new LUNs are created immediately after the old LUNs are deleted. The new
LUNs may not be initialized and a drive letter not assigned.
Workaround:
Reboot the management station after deleting any LUNs that were presented to the
management station. Then, perform the template deployment or creation of any new LUNs.
6