HP StorageWorks 9100 HP StorageWorks 9100 Extreme Data Storage System release - Page 14

Replacing the HP ExDS9100cx I/O module.

Page 14 highlights

Issue Description 26253 The exdsmgr install update command requires full path names for the RPM files. Relative path names do not work. The error message is not very clear; when it cannot find the RPM, it displays a messages such as Error: Invalid flag (example.rpm) entered. Workaround: Specify full path names. 26339 In some configurations, power supply 3 and 6 are not connected to a power source. The exdsmgr syscheck command correctly ignoresthis situation. However, the LCD display on the front of the blade enclosure will show PSU3 and PSU6 as having an alarm. Workaround: You can ignore these errors or remove the PSUs or you can clear the errors by connecting all PDUs to a power source. 26465 Unexpected interconnect IP alert in non-standard management network configurations. In a non-standard configuration of the management network, you may get alerts such as: crit server[15742]: Interconnect IP not as expected, is: 10.129.69.1 should be: 10.129.5.1. Workaround: You can safely ignore these such alerts. However, do not ignore an alert where the IP address is 0.0.0.0 because this indicates the OA has lost its IP address. Size, used, available and other fields missing after filesystem is created.Size, used, available and other fields missing after filesystem is created.Size, used, available and other fields missing after filesystem is created. 27091 Used field incorrect if mx fs destroy command used. If the mx fs destroy command is used to delete a filesystem, the Used field as shown by the exdsmhr show lun command contains old data and might prevent you using those LUNs for a new filesystem. Workaround: Avoid using the mx fs destroy command. However, if you do use it, run the exdsmgr delete filesystem command to clean up the Used field as shown by the exdsmgr show lun command. 27678 A replacement SAS switch may not appear to work. The syscheck command will not tell you that the firmware is the wrong version; it may flag that it is different than the firmware on the other SAS switch. Workaround: Downgrade the firmware as described in the HP StorageWorks 9100 Extreme Data Storage System administration guide section "Replacing the SAS switch in Bay 3 or 4." 27678 Replacement ExDS9100cx I/O modules may have incompatible firmware. The firmware on a replacement I/O module may not be the same as the firmware on the other I/O modules. This is not a recommended configuration and may cause data corruption. Workaround: Always upgrade or downgrade the firmware on a new I/O module to the same version as the other I/O modules. This is described in the HP StorageWorks 9100 Extreme Data Storage System administration guide section "Replacing the HP ExDS9100cx I/O module." 28204 Size, Used, Available, and other fields missing after filesystem is created. When a filesystem is created, sometimes the exdsmgr show filesystem command does not show the Size, Used, Available, and other fields of the newly created filesystem. Workaround: Run the following command: # pdsh -a 'service somon_scripts restart' 14

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16

Description
Issue
The
exdsmgr install update
command requires full path names for the RPM files. Relative
path names do not work.
The error message is not very clear; when it cannot find the RPM, it displays a messages such as
Error: Invalid flag (example.rpm) entered
.
Workaround:
Specify full path names.
26253
In some configurations, power supply 3 and 6 are not connected to a power source.
The
exdsmgr syscheck
command correctly ignoresthis situation. However, the LCD display on
the front of the blade enclosure will show PSU3 and PSU6 as having an alarm.
Workaround:
You can ignore these errors or remove the PSUs or you can clear the errors by
connecting all PDUs to a power source.
26339
Unexpected interconnect IP alert in non-standard management network configurations.
In a non-standard configuration of the management network, you may get alerts such as:
crit
server[15742]: Interconnect IP not as expected, is: 10.129.69.1 should
be: 10.129.5.1
.
Workaround:
You can safely ignore these such alerts. However, do not ignore an alert where the
IP address is 0.0.0.0 because this indicates the OA has lost its IP address.
Size, used, available and other fields missing after filesystem is created.Size, used, available and
other fields missing after filesystem is created.Size, used, available and other fields missing after
filesystem is created.
26465
Used field incorrect if mx fs destroy command used.
If the
mx fs destroy
command is used to delete a filesystem, the Used field as shown by the
exdsmhr show lun
command contains old data and might prevent you using those LUNs for a
new filesystem.
Workaround:
Avoid using the
mx fs destroy
command. However, if you do use it, run the
exdsmgr delete filesystem
command to clean up the Used field as shown by the
exdsmgr
show lun
command.
27091
A replacement SAS switch may not appear to work.
The
syscheck
command will not tell you that the firmware is the wrong version; it may flag that it
is different than the firmware on the other SAS switch.
Workaround:
Downgrade the firmware as described in the
HP StorageWorks 9100 Extreme Data
Storage System administration guide
section
Replacing the SAS switch in Bay 3 or 4.
27678
Replacement ExDS9100cx I/O modules may have incompatible firmware.
The firmware on a replacement I/O module may not be the same as the firmware on the other I/O
modules. This is not a recommended configuration and may cause data corruption.
Workaround:
Always upgrade or downgrade the firmware on a new I/O module to the same
version as the other I/O modules. This is described in the
HP StorageWorks 9100 Extreme Data
Storage System administration guide
section
Replacing the HP ExDS9100cx I/O module.
27678
Size, Used, Available, and other fields missing after filesystem is created.
When a filesystem is created, sometimes the
exdsmgr show filesystem
command does not
show the Size, Used, Available, and other fields of the newly created filesystem.
Workaround:
Run the following command:
# pdsh -a 'service somon_scripts restart'
28204
14