Installation guide

StorageWorks Secure Path for Windows NT
3–4 123995–002 EK–WNTMP–MH. D01
3.4 Examine the Current Configuration
The next step is to ensure that the existing single path configuration conforms to Secure
Path requirements. The requirements are as follows:
Existing storage infrastructure must be robust –
a) Verify that there is a serial connection to the storage subsystem and that you can
communicate to it via SWCC or the CLI.
b) Launch the NT event log viewer and check to see that HSZdisk is installed and that it
reports the expected number of logical units.
c) Check the NT event log viewer and determine that there are no error events reported
by the host adapter or HSZdisk.
d) Verify that the Windows NT system (boot) disk is not part of the storage subsystem.
e) Verify that none of the LUNs are partitioned by the storage controller hardware.
f) Verify that none of the NT volume sets use software RAID or use extended volumes.
g) Verify that the server has the TCP/IP protocol installed and that the server is
available on the network by pinging it.
h) Verify, for Alpha servers only, that FX!32 is not installed or is disabled.
3.5 Prepare the RAID Array for Secure Path Operation
The procedures to prepare your RAID Array for a Secure Path environment (described in
this section), depend upon whether you are converting an existing RAID Array to Secure
Path operation or are installing a brand new subsystem.
WARNING
If you currently have a RAID Array in a production
environment, which is being converted to Secure Path
operation, make sure that all users have logged off the
server and that all I/O to the RAID subsystem has ceased
before proceeding.