VERITAS Volume Manager 3.5 Hardware Notes (June 2002)

Hardware Notes 7

BETA 19 July 2002 Hardware Requirements

◆ EMC Symmetrix usersmust programtheir disk arrays in the Common SerialNumber

Mode before installing the Volume Manager package.

◆ The minimum level of microcode on the EMC Symmetrix should be:

- 5265 or 5266 for Sym-4 on models 3330, 3430, and 3700

- 5265 or 5266 for Sym-4.8 on models 3630, 3830, and 3930

- 5566 for Sym-5 on models 8130, 8430, and 8730

◆ The Common Serial Number Mode should be enabledforallchannelsthatparticipate

in the DMP. This is done at installation time in the Symmetrix conﬁguration by the

EMC Customer Engineer.

◆ Ultra SCSI and fast-wide differential (FWD) SCSI support hasbeen testedontheEMC

OSD (Open System Director) controller.

See your sales representative for further updates on hardware support.

DMP and EMC PowerPath Exclusive Use Support

Note VxVM is not supported with versions of EMC PowerPath earlier than 2.1.

If you use EMC’s PowerPath 2.1 with EMC Symmetrix disk arrays, EMC PowerPath

intercepts the I/O from VERITAS Dynamic Multipathing (DMP) just before it reaches the

SCSI subsystem, and manages it from that point through the SCSI subsystem to the EMC

disk array(s).

In this release, it is not possible to have DMP exclusively manage some LUNs and EMC

PowerPath exclusively manage others on the same EMC Symmetrix disk array(s).

DMP and EMC PowerPath can coexist. Therefore, there is no need to disable either DMP

or EMC PowerPath when VxVM 3.5 for HP-UX is installed on the same host as EMC

PowerPath.

DMP and HP FC10 Disk System Support

Because ofthe way LUNs are distributedacross controllers byHP-UX, the enable/disable

controller featureof VxVM does not functionas expected for the following conﬁgurations

of FC10 disk systems:

◆ multiple daisy chained FC10 disk systems connected to a single host

◆ multiple FC10 disk systems connected to a single host through a hub

If the vxdmpadm disable ctlr=ctlr_name command is used for the above

conﬁgurations to disable I/O through a particular controller, I/O can be stopped through

paths that were not intended by the user.