Release Notes

ManualsBrandsHP ManualsSoftwareHP Surestore SAN Manager LM Software

J6100-96021 SAN Manager LM Release Notes Page 1 of 7

SAN Manager LM 1.2 for Windows NT

Release Notes

OFTWARE

OMPATIBILITY

SAN Manager LM is compatible with Windows NT 4.0 with Service Pack 4 or later. However, due to the

limitations discussed in the first paragraph under Known Issues on page 3, HP recommends Service Pack

6a.

ARDWARE

OMPATIBILITY

With the release of version 1.2, SAN Manager LM now supports the following hardware:

RAIDs

– EMC Symmetrix 3000 Devices (SCSI)

– HP SureStore E Disk Array XP256 (SCSI)

Note

EMC Symmetrix 3000 (SCSI) devices and XP256 (SCSI) devices are only compatible

with SAN Manager LM when they are configured with a Crossroads bridge and

QLogic HBAs.

– HP SureStore E Disk System FC60 with version 7.02.27.01 or later of the RDAC driver

UALIFIED

HBA

The following HBAs are the only HBAs that are qualified for use with SAN Manager LM on Windows NT

hosts:

– QLogic QLA2100 and QLA2200 with the HP SAN Manager LM QLogic HBA driver

Note

For an up-to-date list of the HBAs and drivers that are qualified for use with SAN

Manager LM, visit HP’s Customer Care website. For more information about the

Customer Care website, see the

Obtaining Free HP Product Information

document that is included in your SAN Manager LM box.

New In This Release

Summary of content (7 pages)

PAGE 1
h SAN Manager LM 1.2 for Windows NT Release Notes New In This Release SOFTWARE COMPATIBILITY SAN Manager LM is compatible with Windows NT 4.0 with Service Pack 4 or later. However, due to the limitations discussed in the first paragraph under Known Issues on page 3, HP recommends Service Pack 6a. HARDWARE COMPATIBILITY With the release of version 1.
PAGE 2
QLogic HBA Issues – The BIOS must be disabled on the HBA. Failure to disable the BIOS can result in unstable operation and compromised storage. – The HP SAN Manager LM QLogic HBA driver (trqladrv.sys) does not support hot-plugging. You cannot insert an HBA card into a computer that is powered on.
PAGE 3
Silent Install – A hands-off (automated) method for installing SAN Manager LM is available to reduce installation time on multiple hosts. Command-line flags and an install text file control the silent installation process. Database Wizard – A database wizard has been added to guide administrators through the SAN Manager LM database creation process. Remove License – Reconfiguration of multiple SANs has been simplified by the remove license feature.
PAGE 4
h • The database restoration section on page 124 of the Administrator’s Guide incorrectly states that you can restore a database without unassigning devices that are assigned to hosts that are shut down. In order to protect against unintended multiple-writer situations, you must unassign all of the devices from hosts and share groups in your SAN database. For some SANs, you may have to shut down hosts in order to unassign devices.
PAGE 5
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.
PAGE 6
h • HP has observed some problems in large SAN configurations with HP NetServers that are running HP’s TopTools device management software. Two SNMP agents that are included with TopTools (symsnmp.dll and symtrap.dll) may prevent the SNMP service from loading on NetServers that are connected to SANs with large numbers of attached LUNs. The failure occurs because these agents can only store information about a limited number of LUNs per SCSI/RAID host bus adapter.
PAGE 7
h Windows NT Domain Issues The intent of SAN Manager LM is that the SAN should parallel the Windows NT domain. The SAN Manager LM design reflects this in the following ways: • Administration groups are selected from domain groups. • Host names are discovered by enumerating machines in the domain.