Table of Contents
Advertisement
If you use one of the first two options, the procedures should again be validated in
the test environment. Some multipathing software installations handle fabric
failover gracefully and quickly. There are quite a few variables which affect this,
including but not limited to:
If the behavior of multi-pathing software in the SAN is not well understood, a test
should be run to determine this as well. For installations where the multi-pathing
software does handle switchover automatically and seamlessly, the update process
is greatly simplified.
Update Plan Creation
The specific procedures used to update to the new PID format varies on a
site-by-site basis. However, there are general guidelines for the update process
options. These guidelines are provided to give SAN administrators a starting point
for creating site-specific procedures, not to be the complete procedures
themselves.
The online update process is only intended for use in uptime-critical dual-fabric
environments, with multi-pathing software. If dual-fabrics are not in place, there
are a number of routine maintenance scenarios which require scheduled
downtime, the core PID migration process being only one example. High-uptime
environments should always use a redundant fabric SAN architecture.
Online Update Plans
The general format for an online update plan is as follows:
1. Backup all data. Verify backups.
2. Verify that I/O continues over the other fabric.
3. Disable all switches one at a time in the fabric to be updated.
4. Verify that I/O continues over the other fabric after each switch disable.
5. Change the PID format on each switch in the fabric as described in the section
6. One at a time, reenable the switches in the updated fabric.
7. In a core/edge network, enable the core switches first.
Core Switch 2/64 V4.1 Installation Guide
HBA time-out values
Multipathing software time-out values
Kernel time-out values
Detailed Procedures
on page 191.
Technical Specifications
189
Advertisement
Table of Contents
