 |
≫ |
|
|
|
パッチ名: PHSS_36128
パッチ摘要: 11.31 rx4640 システム、BMCおよびMPファームウェアパッチ
作成日: 07/03/12
公開日: 07/04/25
ハードウェアプラットフォームおよびOSリリース:
11.31
現象:
PHSS_36128:
システムファームウェア04.21(最新リリース)で修正した不具合:
----------------------------------------------------------
- ネットワーク経由でのOpenVMSのブート時に、EFI_ASSERT_ERRORが起きるこ
とがありました。
- 以前のバージョンでは、Intel GigE EFIドライバ3.0.13がインストールさ
れているシステム上で、クライアントの完全なIPアドレス情報を指定して
DBprofileを実行すると、"Directed LAN boot"が失敗し、次のようなメッ
セージが表示されることがありました。
"PXE-E18: Timeout. Server did not respond."
- "lanboot select directed boot"が失敗した後"lanboot select"を実行す
ると、トラップが起きることがありました。
- 以前のバージョンでは、15個以上のfsデバイスが表示可能な場合に、EFI
Shellがパス変数を定義できないことがありました。必要な場合には、EFI
パス変数を縮小して、"set : path variable truncated"というメッセージ
を表示するようにコードを修正しました。
- 以前のバージョンでは、EFI Fast Initializationが"enabled"の場合、
レガシーEFI Boot Manager Menu内の"Add a Boot Option"/"Boot from a
File"メニューに、使用可能なデバイスが一部しか表示されないことがあり
ました。
- 以前のバージョンでは、AD139A 1.6GHz/18MBまたはAD268A 1.6GHz/24MBデ
ュアルコアプロセッサモジュールを搭載したシステムが正常にリブートさ
れても、システムフォルトLEDが不正に赤色点滅のままになることがありま
した。
BMCファームウェア04.05(最新リリース)で修正した不具合:
-----------------------------------------------------
- MPの"RB"コマンドを使ってBMCをリセットすると、システムLEDが不正にオ
フになることがありました。
- オペレーティングシステムとBMC間のトランザクションを処理するバスがハ
ングしたようになることがありました。HP-UXのEMS(Event Monitoring
Service)はこのバスを使ってBMSからシステムイベントログ情報を取得しま
すが、この問題が起きると、EMSが次のようなメッセージをsyslogに記録す
ることがありました。
"vmunix: ipmi_wd_heartbeat(): timer not refreshed."
- 以前のバージョンでは、BMCパスワードを設定したり、NVRAMからのパスワ
ードの読み取りエラーが起きたりすると、デフォルトのEFI Shellアクセス
がAdminモードになることがありました。NVRAMパスワードの読み取りエラ
ーの場合にだけユーザーアクセスを許可するように、デフォルトのアクセ
スを変更しました。
当社は、今後とも、高品質の製品をお客様に提供するための努力を続けて参り
ます。その一環として、このファームウェアリリースでは、性能と信頼性を向
上させるためのいくつかの改善を行いました。
問題点の説明:
PHSS_36128:
- 上記の"現象"セクションを参照。
-----------------------------------------------------------------------------
Patch Name: PHSS_36128
Patch Description: 11.31 rx4640 System, BMC and MP Firmware Patch
Creation Date: 07/03/12
Post Date: 07/04/25
Hardware Platforms - OS Releases:
11.31
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release firmware
Path Name: /hp-ux_patches/11.X/PHSS_36128
Symptoms:
PHSS_36128:
The following fixes appear in System firmware 04.21
(Current Release):
------------------------------------------------------------
- Corrected an issue that may result in an EFI_ASSERT_ERROR
occurring during an OpenVMS network boot.
- In previous versions Directed LAN boot may fail with a
"PXE-E18: Timeout. Server did not respond." message if
the DBprofile fully specifies the client IP address
information on systems with Intel GigE EFI driver 3.0.13.
- Corrected an issue that may result in a trap during a
lanboot select following a failed lanboot select directed
boot attempt.
- In previous versions the EFI Shell may fail to define
the path variable when 15 or more fs devices are visible.
The EFI path variable will now be truncated, when
necessary, with a "set : path variable truncated"
message.
- In previous versions the legacy EFI Boot Manager Menu may
not show all available devices at the 'Add a Boot Option'
and 'Boot from a File" menus when EFI Fast Initialization
is enabled.
- In previous versions the System Fault LED may incorrectly
remain flashing red after a successful system reboot when
AD139A 1.6GHz/18MB or AD268A 1.6GHz/24MB dual-core
processor modules are installed.
The following fixes appear in BMC firmware 04.05 (Current
Release):
------------------------------------------------------------
- Corrected an issue where the System LED may incorrectly
turn off when the BMC is reset via the MP 'RB' command
- Corrected an issue where the bus that handles
transactions between the Operating System and the BMC may
appear to hang. The Event Monitoring Service (EMS) in
HP-UX uses this bus to get system event log information
from the BMC, upon this issue EMS may report the
following message in the syslog: "vmunix:
ipmi_wd_heartbeat(): timer not refreshed."
- Previous versions may default EFI Shell access to Admin
mode when a BMC password is set and a password read from
NVRAM fails. The default access has now been changed to
only allow user access upon an NVRAM password read
failure.
Hewlett-Packard continually strives to provide customers
with the highest quality of products. To meet this goal,
several minor performance and reliability improvements have
been identified that Hewlett-Packard has included in this
firmware release.
Defect Description:
PHSS_36128:
- See Symptoms
Enhancement:
No
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
/usr/conf/OSIFU/updatebootsequence
/usr/conf/OSIFU/efi8xxfl.efi
/usr/conf/OSIFU/lsiscsi.rom
/usr/conf/OSIFU/sysupdate.efi
/usr/conf/OSIFU/shellenv.efi
/usr/conf/OSIFU/fwupdate.efi
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
/usr/conf/OSIFU/updatebootsequence:
None
/usr/conf/OSIFU/efi8xxfl.efi:
None
/usr/conf/OSIFU/lsiscsi.rom:
None
/usr/conf/OSIFU/sysupdate.efi:
sysupdate.efi version 20060830.017
localtime.c 7.57
asctime.c 7.7
/usr/conf/OSIFU/shellenv.efi:
None
/usr/conf/OSIFU/fwupdate.efi:
asctime.c 7.7
localtime.c 7.57
FWEUPDATE.EFI 0.90
Revision E.03.30 Oct 27 2006,13:43:15
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
261107441 50136 /usr/conf/OSIFU/updatebootsequence
3882913678 134656 /usr/conf/OSIFU/efi8xxfl.efi
1758945560 90112 /usr/conf/OSIFU/lsiscsi.rom
2972935001 605184 /usr/conf/OSIFU/sysupdate.efi
1526003380 703488 /usr/conf/OSIFU/shellenv.efi
450672558 9954304 /usr/conf/OSIFU/fwupdate.efi
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
rx4640
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 5820 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_36128
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_36128.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_36128. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_36128.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHSS_36128.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_36128.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. This patch will only install and update the firmware on
rx4640 systems.
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by using the touch(1) command to create the file
'/tmp/force_patch_install' before installing the patch.
This may be useful when creating a 'golden' archive image
for Ignite-UX that may be used on several different
hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
2. If this patch is uninstalled it will not
uninstall/downgrade the firmware installed by the patch
and the firmware installed by the patch will remain
loaded after the patch is removed.
3. The firmware update is accomplished by temporarily
altering the boot sequence. To identify the disk, the
patch assumes that the primary boot disk is the first
disk listed in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
4. It is recommended that the firmware update is performed
outside of an OS install, update-UX, or Dynamic Root Disk
session. If a firmware update is performed, it will be
excluded from installation to ensure that OS install,
update-UX, or DRD is fully functional.
5. The firmware update will be excluded from installation
if the firmware versions in the patch are the same or older
than the ones the system is running on. This will ensure
that no un-necessary system reboot occurs.
6. Any newer firmware versions on the system can be
downgraded with firmware in this patch by using the
command "touch /tmp/force_patch_install" before
installing the patch. If there are any newer firmware
patches installed on the system that supersede this
firmware patch, the newer firmware patches must be removed
with the SD command swremove in order to install this
downgrade firmware patch.
7. The firmware update will be excluded from installation
if the autoboot flag is not set. This is to ensure that the
end-to-end firmware update process goes smoothly without
user intervention once the patch installation is started.
Please use the setboot(1M) command to set the autoboot
flag on prior to installing the patch.
8. The firmware update will be excluded from installation
if the system has an Administrator password set. If this
password is set, it must be cleared by connecting to the
Management Processor and running the BP command from
the Command Menu prior to installing the patch.
9. Do not attempt to update firmware on the Management
Processor via the network while installing this patch.
10. Prior to updating the iLO MP firmware a MP reset
needs to occur via the "XD -R" command in order to free up
enough contiguous memory.
11. System firmware versions 02.13 and later require Dual
Hot Plug Controller (DHPC) firmware revision 1.1 or later
to correct an issue with certain paired PCI-66 cards in a
shared slot. To determine DHPC revision, type 'info
chiprev' at the EFI Shell. If the revision is 0100, DHPC
firmware should be upgraded. This firmware can be
downloaded from http://www.hp.com/support/itaniumservers.
12. System firmware versions 03.11 and later require
revision 01.03.01.00 or later U160 SCSI EFI Boot Services
Driver for A6828A, A6829A, A8686A, A7059A, and A7060A U160
SCSI PCI cards. Revision 01.04.01.00 is contained in this
package. Only servers with a U160 SCSI Driver less than
01.03.01.00 will be updated to 01.04.01.00 using this
package.
13. If the currently installed MP firmware revision is
E.03.13 or later, the MP firmware update will fail if the
"Allow MP Firmware upgrade via PCI" option is Disabled in
the MP Security Options menu. To update the firmware using
this package, enable this option in the Login Options
sub-menu of the MP Security Options menu.
14. CAUTION: Depending upon the currently installed MP
firmware, interim upgrades to previous revisions of MP
firmware may be required in order to upgrade to iLO MP
firmware revision E.03.30.
This system firmware update will be aborted if the current
MP firmware revision present on the system is less than
E.02.29. In order to upgrade system firmware using this
package, first upgrade the MP firmware to E.02.29. Please
follow the upgrade requirements below:
1 - If the currently installed MP firmware is older
than E.02.10 then updating to MP firmware revision
E.02.26 requires updating to MP E.02.10 first.
2 - Upgrades to MP firmware revision E.02.29 will
require updating to MP firmware revision E.02.26
first.
3 - MP firmware must be at or upgraded to revision
E.02.29 prior to upgrading to iLO MP revision
E.03.30.
15. DETERMINING CURRENT VERSION:
The current version of firmware installed on the
system can be determined by executing the
swinstall(1M) command with the -p (preview)
command-line option. Or alternatively, the MP CM
SYSREV command can be used as shown below:
1 - Establish a telnet session with the iLO
Management Processor.
2 - Logon to the iLO Management Processor using the
Admin password.
3 - Type CM to enter the Command Menu.
4 - Type SYSREV to display system revision information.
The following should be displayed if the current
firmware is installed:
Current firmware revisions
MP FW : E.03.30
BMC FW : 04.05
EFI FW : 05.48
System FW : 04.21
5 - If the System firmware revision is less than 04.21,
if the BMC firmware revision is less than 04.05 or
if the iLO MP firmware revision is less than E.03.30
then firmware should be updated.
|
