Table of Contents
Advertisement
Bringing Devices Online
Update Phase
This section includes the update information:
Online Update
Provided that careful planning, testing, and general due-diligence has been
performed, it should be safe to update the core PID format parameter in a live,
production environment.This requires dual fabrics with multi-pathing software.
Create a detailed update plan. Guidelines are provided above. Schedule a time for
the update when the least critical traffic is running. This is a best practice for any
kind of online add, move, change, upgrade, or update. At very least, it is a good
Core Switch 2/64 V4.1 Installation Guide
Bring the devices online in the order appropriate to the SAN. This usually
involves starting up the storage arrays first, and the hosts last.
For any devices manually bound by PID, bring the device back online, but do
not start applications. Update their bindings and reboot again if necessary.
This may involve changing them to the new PIDs, or may (preferably) involve
changing to WWN binding.
For any devices automatically bound by PID, reboot the device to rebuild the
device tree. (Some operating systems require a special command to do this,
for example, boot -r command in Sun Solaris systems)
For devices that do not bind by PID or have had their PID binding updated,
bring them back up and resume I/O.
— Verify that all I/O has resumed correctly.
— Migrating from manual PID binding (such as persistent binding on an
HBA) to manual WWN binding and/or upgrading drivers to versions that
do not bind by PID can often be done before setting the core PID format.
This can be advantageous, as it prevents the update process from having
as many variables.
Online
Update, page 191
Offline
Update, page 192
Hybrid
Update, page 192
Detailed
Procedures, page 193
Technical Specifications
191
Advertisement
Table of Contents
