HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array Updating Product Software G - Page 22

Evaluating your configuration, The Best Practices and Recommendations window opens - reviews

Page 22 highlights

5. To review update recommendations for your switches and HBAs, select the applicable folder on the left side of the window. In Figure 5, it is the folder called MySwitchGroup. Look for the group name you created in step 2 of "Using SAN Visibility" (page 15) The Best Practices and Recommendations window opens (Figure 6 (page 22)). Figure 6 Sample SAN recommendations If the firmware or driver version recommended is later than what is currently running, ensure that you upgrade the appropriate switch or HBA. NOTE: After completing required upgrades, HP recommends that you create a new SAN Visibility report to verify that all upgrades were successful. Evaluating your configuration The following factors can affect the success of an online upgrade. Consider these factors when determining if an online upgrade is appropriate for your environment. • Queuing host I/O-After the upgrade, the array performs a resynchronization. During the resynchronization, host I/O is queued to the host, which can create a backlog of requests for processing when the array is able to respond. The resynchronization may take less than a minute, but the backlog of requests may take time to clear and some host I/O may experience timeouts. The HP recommended driver timeout values are 60 seconds. When an I/O timeout occurs, multipath drivers will typically retry the I/O request on the same path or an alternate path. There are operating system and HBA dependencies on these algorithms. The retry algorithms may extend the total amount of time that a host I/O will be allowed to complete successfully beyond the 60 second timeout values. Note that some applications may be more sensitive to I/O delays. • Processing host I/O during the upgrade-The upgrade competes with host requests that have a higher priority, which can affect the upgrade outcome. To ensure that host I/O from business 22 Pre-upgrade tasks

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

5.
To review update recommendations for your switches and HBAs, select the applicable folder
on the left side of the window. In Figure 5, it is the folder called MySwitchGroup. Look for the
group name you created in step 2 of
“Using SAN Visibility” (page 15)
The Best Practices and Recommendations window opens (
Figure 6 (page 22)
).
Figure 6 Sample SAN recommendations
If the firmware or driver version recommended is later than what is currently running, ensure
that you upgrade the appropriate switch or HBA.
NOTE:
After completing required upgrades, HP recommends that you create a new SAN Visibility
report to verify that all upgrades were successful.
Evaluating your configuration
The following factors can affect the success of an online upgrade. Consider these factors when
determining if an online upgrade is appropriate for your environment.
Queuing host I/O—After the upgrade, the array performs a resynchronization. During the
resynchronization, host I/O is queued to the host, which can create a backlog of requests for
processing when the array is able to respond. The resynchronization may take less than a
minute, but the backlog of requests may take time to clear and some host I/O may experience
timeouts. The HP recommended driver timeout values are 60 seconds. When an I/O timeout
occurs, multipath drivers will typically retry the I/O request on the same path or an alternate
path. There are operating system and HBA dependencies on these algorithms. The retry
algorithms may extend the total amount of time that a host I/O will be allowed to complete
successfully beyond the 60 second timeout values. Note that some applications may be more
sensitive to I/O delays.
Processing host I/O during the upgrade—The upgrade competes with host requests that have
a higher priority, which can affect the upgrade outcome. To ensure that host I/O from business
22
Pre-upgrade tasks