Release Notes

J6100-96021 SAN Manager LM Release Notes Page 5 of 7
h
•
HP has observed some problems such as data loss and data corruption when hot-swapping Fibre
Channel JBOD (Just a Bunch of Disks) drives attached to a Fibre Channel switch. To avoid potential
problems, this situation should be avoided.
•
Only one instance of the SAN Manager LM application should be running before and during the database
creation procedure. Once the database is created, the application contains a lock that prevents multiple
instances of the application from running simultaneously. Before the initial creation of the database or
during a database re-creation, this safeguard does not work.
•
“Lost delayed write” errors could indicate a high error rate on the network hardware. If “lost delayed
write” errors occur, run hardware/software diagnostics on the network hardware.
•
Windows NT’s SCSIPORT driver does not reliably discover logical units with LUNs greater than 7.
Normally, SCSIPORT only supports logical units with LUN numbers from 0 to 7. The ability to access
LUNs greater than 7 by setting the LargeLuns registry key was added to SCSIPORT in Service Pack 4.
The scanning logic for this added functionality does not operate properly in certain environments. If you
experience problems when using LUNs greater than 7, try to reorder the hardware in your SAN by
swapping port connections between devices.
•
A Fibre Channel disk cannot be used as a boot disk with SAN Manager LM.
•
When running SAN Manager LM on a SAN that does not yet have a database, and you have a RAID that
you want to use for database storage, you must configure the RAID on a machine that does not have SAN
Manager LM installed. This step is required because you cannot create a database on RAID storage until
after the RAID is configured, but a RAID array cannot be discovered and assigned to a SAN Manager LM
host until a database has been created.
•
For any non-disk device that is assigned to a Windows NT host, ensure that software on the Windows NT
host is not using the device before attempting to unassign the device. For all non-disk devices, SAN
Manager LM will not prevent you from unassigning the device, even if it is in use. If a device that is in use
is unassigned, I/O to the device will fail.
•
The SCSI Adapters control panel can only list 32 devices per adapter. If an adapter has more attached
devices than the control panel can list, the adapter will disappear from the adapters list in the control
panel. This does not prevent you from using assigned storage.
•
If the 32 device per adapter limit in the SCSI Adapters control panel is reached, none of the attached tape
devices will be listed in the Tape Devices control panel. This limitation may prevent you from configuring
tape device drivers.
•
If a device has been removed (turned off, unplugged, etc.), and shortly afterwards you use SAN Manager
LM’s Scan for Devices command, the device scan may take a few minutes to finish. During this time,
SAN Manager LM is waiting for the newly missing device to come back online.