HP StorageWorks 2/32 SAN switch 2/32, version 4.0.2b release notes - Page 32

Web Tools and Firmware Download, Troubleshooting the I2C Time-out message, Recommended Steps

Page 32 highlights

Known Issues Web Tools and Firmware Download Firmware download and activation involves multiple phases. When Web Tools reports that firmware download has completed successfully, this indicates that a basic sanity check, package retrieval, package unloading and verification was successful. NOTE: Web Tools currently forces a full package install. To perform an incremental upgrade, use the CLI. A reboot is required to activate the newly downloaded firmware. The reboot is done automatically from the Web Tools user perspective, and results in a loss of network connectivity with Web Tools. Web Tools screens continue to be visible during the reboot, but will not be available. Wait approximately 10 minutes to ensure all application windows are restored. If Web Tools fails to respond after 20 minutes, you may need to close all Web Tools applications windows and restart them, or contact the system administrator for network assistance. The SAN Switch 2/32 loss of network connectivity due to reboot is approximately 4 minutes if diagpost is disabled and 8 minutes if diagpost is enabled. Troubleshooting the I2C Time-out message If an "EM, I2C_TIMEOUT" message displays, then either the I2C bus experienced a fault (usually transient) or there is a hardware problem. Recommended Steps Use these steps to determine if there is a hardware problem. 1. Determine which component is indicated. The message provides the information as follows: I2C timed out: state 2. Check the LEDs on the related hardware component. 3. Enter the switchstatusshow, chassisshow, and sensorshow commands. 4. Take the appropriate action: NOTE: If the LEDs and command printouts indicate that all components are healthy, then it was a transient I2C bus fault, and no action is required. If one of the components appears to be faulted, try reseating the component. If it still appears to be faulty, replace the component. 32 SAN switch 2/32, version 4.0.2b release notes

  • 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

Known Issues
32
SAN switch 2/32, version 4.0.2b release notes
Web Tools and Firmware Download
Firmware download and activation involves multiple phases. When Web Tools reports
that firmware download has completed successfully, this indicates that a basic sanity
check, package retrieval, package unloading and verification was successful.
NOTE:
Web Tools currently forces a full package install. To perform an incremental upgrade,
use the CLI.
A reboot is required to activate the newly downloaded firmware. The reboot is done
automatically from the Web Tools user perspective, and results in a loss of network
connectivity with Web Tools. Web Tools screens continue to be visible during the
reboot, but will not be available. Wait approximately 10 minutes to ensure all
application windows are restored. If Web Tools fails to respond after 20 minutes, you
may need to close all Web Tools applications windows and restart them, or contact the
system administrator for network assistance. The SAN Switch 2/32 loss of network
connectivity due to reboot is approximately 4 minutes if
diagpost
is disabled and 8
minutes if
diagpost
is enabled.
Troubleshooting the I2C Time-out message
If an “
EM, I2C_TIMEOUT
” message displays, then either the I2C bus experienced a
fault (usually transient) or there is a hardware problem.
Recommended Steps
Use these steps to determine if there is a hardware problem.
1.
Determine which component is indicated. The message provides the information
as follows:
<fru_type> <unit> I2C timed out: state <curr_state>
2.
Check the LEDs on the related hardware component.
3.
Enter the
switchstatusshow, chassisshow
, and
sensorshow
commands.
4.
Take the appropriate action:
NOTE:
If the LEDs and command printouts indicate that all components are healthy, then it was
a transient I2C bus fault, and no action is required.
If one of the components appears to be faulted, try reseating the component. If it still
appears to be faulty, replace the component.