I know approximately nothing about SAN storage, but...
> When I check the configure guide of OpenVMS Cluster , and find when
> using SAN storage, the LUN is used as boot disk of the boot server or
> quorum disk, none LUNs are used for data storage resource.
Perhaps that's because the boot disk has some special complications
(like how to specify it to the console firmware), so it needs more
explanation.
> Could you please tell me if OpenVMS Cluster can use SAN storage system
> as data resource LUN?
If a VMS system can boot from such a disk device, then it certainly
could use one for general data storage.
> If it can, how to configure it?
I assume that if the SAN system presents a disk device to the VMS
system, then the usual INITIALIZE and MOUNT commands would make that
device available to users. I'd guess that whatever one does on the SAN
system for a boot disk would also apply to a non-boot disk. On the VMS
side, once the SAN disk device is visible, you'd need to do the same
things as with any locally attached non-system disk.
help initialize
help mount
For a system (boot) disk, the VMS installation procdure does the
INITIALIZE operation, and the boot procedure does the MOUNT. For a
non-system disk, the INITIALIZE operation is normally done (once)
manually by the system administrator, and the MOUNT is incorporated in
the system start-up scripts(s), like, say,
SYS$MANAGER:SYSTARTUP_VMS.COM.
For a disk device which is shared among multiple systems, that
ALLOCLASS stuff is used to ensure that everyone uses the same device
name for a particular device. (Otherwise, you can expect data
corruption.)
