Data Analysis - HP AA-RS2WC-TE Installation Manual

Any kind of device could bind by PID. While the vast majority of devices do not
do so, each device should be evaluated prior to attempting an online update.
This is a non-comprehensive list of information to collect, which would be both
generally useful and relevant to the PID update process:
In addition to looking for information about the code revisions in use, look at the
way each device is used. Some device drivers do not automatically bind by PID,
but allow the operator to manually create a PID binding. For example, persistent
binding of PIDs to logical drives may be done in many HBA drivers. Make a list
of all devices which are configured this way. If manual PID binding has been
done, consider changing to WWN binding.
This is a non-comprehensive list of device types which may be manually
configured to bind by PID:

Data Analysis

Once you have collected the code versions of each device on the SAN, they must
be evaluated to find out if any of them automatically bind by PID. Do this in
cooperation with the support providers for each device on the SAN.
Some providers may simply be able to answer this question; in other cases, it may
be necessary to perform empirical testing. Most devices do not bind by PID when
running up-to-date drivers. However, some older driver versions may behave this
Core Switch 2/64 V4.1 Installation Guide
HBA driver versions
Fabric OS versions
RAID array microcode versions
SCSI bridge code versions
JBOD drive firmware versions
Multi-pathing software versions
HBA time-out values
Multi-pathing software time-out values
Kernel time-out values
HBA drivers (persistent binding)
RAID arrays (LUN access control)
SCSI bridges (LUN mapping)
Technical Specifications
187