P740在线升级微码问题。
我想问一下P740怎么在线升级微码。目前微码是AL730_060，想升级到AL730_099。升级的是小版本，是不是可以通过HMC在不停止P740分区的情况下升级微码呢？
之前没有通过HMC在线升级过受管系统的微码，想问一下怎么操作，谢谢。
如果能在线升级微码，那么升级之后在不重新启动机器的情况下，新升级的微码是否起作用呢？
之前没有通过HMC在线升级过受管系统的微码，想问一下怎么操作，谢谢。
如果能在线升级微码，那么升级之后在不重新启动机器的情况下，新升级的微码是否起作用呢？
8同行回答
Power7 Entry Systems Firmware
Applies to: 8202-E4B, 8205-E6B, 8231-E2B, 8233-E8B, 8236-E8C, 8492-DW2 and 8493-SV2
This document provides information about the installation of Licensed Machine or Licensed Internal Code, which is sometimes referred to generically as microcode or firmware.
Contents
1.0 Systems Affected
1.1 Minimum HMC Code Level
1.2 Minimum SDMC Code Level
2.0 Important Information
3.0 Firmware Information and Description
4.0 How to Determine Currently Installed Firmware Level
5.0 Downloading the Firmware Package
6.0 Installing the Firmware
7.0 Firmware History
8.0 Change History Revised (01/28/13)
1.0 Systems Affected
This package provides firmware for Power 710 (8231-E2B), Power 730 (8231-E2B), Power 720 (8202-E4B), Power 740 (8205-E6B, 8492-DW2 and 8493-SV2), Power 750 (8233-E8B) and Power 755 (8236-E8C) servers only.
The firmware level in this package is:
AL730_099
1.1 Minimum HMC Code Level
This section is intended to describe the "Minimum HMC Code Level" required by the System Firmware to complete the firmware installation process. When installing the System Firmware, the HMC level must be equal to or higher than the "Minimum HMC Code Level" before starting the system firmware update. If the HMC managing the server targeted for the System Firmware update is running a code level lower than the "Minimum HMC Code Level" the firmware update will not proceed.
The Minimum HMC Code level for this firmware is: HMC V7 R7.3.0 (PTF MH01255 or MH01256) with PTF MH01257 (Mandatory efix).
Although the Minimum HMC Code level for this firmware is listed above, HMC level V7 R7.3.0 with PTF MH01313 (Service Pack 4) and PTF MH01320 (Fix for V7R7.3.4), or higher is suggested for this firmware level.
For information concerning HMC releases and the latest PTFs, go to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
For specific fix level information on key components of IBM Power Systems running the AIX, IBM i and Linux operating systems, we suggest using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
NOTE: You must be logged in as hscroot in order for the firmware installation to complete correctly.
1.2 Minimum SDMC Code Level
This section is intended to describe the "Minimum Systems Director Management Console (SDMC) Code Level" required by the System Firmware to complete the firmware installation process. When installing the System Firmware, the SDMC level must be equal to or higher than the "Minimum SDMC Code Level" before starting the system firmware update. If the SDMC managing the server targeted for the System Firmware update is running a code level lower than the "Minimum SDMC Code Level" the firmware update will not proceed.
The Minimum SDMC Code level for this firmware is: SDMC V6 R7.3.0 with Mandatory PTF MF53082.
Although the Minimum SDMC Code level for this firmware is listed above, SDMC level V6.730 SP2 (MF54510), or higher is suggested for this firmware level.
For information concerning SDMC releases and the latest PTFs, go to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
For specific fix level information on key components of IBM Power Systems running the AIX, IBM i and Linux operating systems, we suggest using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
2.0 Important Information
Downgrading firmware from any given release level to an earlier release level is not recommended.
If you feel that it is necessary to downgrade the firmware on your system to an earlier release level, please contact your next level of support.
IPv6 Support and Limitations
IPv6 (Internet Protocol version 6) is supported in the System Management Services (SMS) in this level of system firmware. There are several limitations that should be considered.
When configuring a network interface card (NIC) for remote IPL, only the most recently configured protocol (IPv4 or IPv6) is retained. For example, if the network interface card was previously configured with IPv4 information and is now being configured with IPv6 information, the IPv4 configuration information is discarded.
A single network interface card may only be chosen once for the boot device list. In other words, the interface cannot be configured for the IPv6 protocol and for the IPv4 protocol at the same time.
Concurrent Firmware Updates
Concurrent system firmware update is only supported on HMC or SDMC - Managed Systems only.
Changes to DIMM VPD reported under FW Release AL730, for select DIMMs
After installation of AL730 firmware, select DIMMs may display VPD information that does not match the attached FRU label. The FRU number displayed may differ from the FRU number printed on the DIMM label.
This change would not apply when the server is running an earlier supported release of system firmware (ex. AL710, or AL720).
Changes in VPD (Vital Product Data) May be Reported for Feature Codes 4526, 4529, and 4528
Feature Code Supported
Systems Description DIMM FRU Label Under FW Release AL730,
VPD is displayed as the following
FRU Number CCIN FRU Number CCIN
4526 8202-E4B
8205-E6B
8231-E2B
8233-E8B
8236-E8C
8492-DW2
8493-SV2
4GB Memory DIMM
77P8784
31C5
78P0554
31F3
4529 8202-E4B
8205-E6B
8492-DW2
8493-SV2
8GB Memory DIMM
77P8919
31D2
78P0555
31F4
4528 8233-E8B
8236-E8C
16GB Memory DIMM
77P8633 31C9 78P0639 31F5
Note: This change does not apply to all DIMMs with the FRU numbers listed above, only a sub-set of DIMMs will report changes in VPD information. The change in displayed VPD information has no functional impact and does not affect the operation or reliability of the associated memory DIMMs, it simply reports select DIMMs with new VPD information as a means of differentiating their capabilities to service providers. Future service actions should be placed using the displayed VPD information, as logged by diagnostic and service related software, and not against the FRU number printed on the DIMM FRU label.
Memory Considerations for Firmware Upgrades
Firmware Release Level upgrades and Service Pack updates may consume additional system memory.
Server firmware requires memory to support the logical partitions on the server. The amount of memory required by the server firmware varies according to several factors.
Factors influencing server firmware memory requirements include the following:
Number of logical partitions
Partition environments of the logical partitions
Number of physical and virtual I/O devices used by the logical partitions
Maximum memory values given to the logical partitions
Generally, you can estimate the amount of memory required by server firmware to be approximately 8% of the system installed memory. The actual amount required will generally be less than 8%. However, there are some server models that require an absolute minimum amount of memory for server firmware, regardless of the previously mentioned considerations.
Additional information can be found at:
http://publib.boulder.ibm.com/in ... iphatlparmemory.htm
3.0 Firmware Information and Description
Use the following examples as a reference to determine whether your installation will be concurrent or disruptive.
For systems that are not managed by an HMC or SDMC, the installation of system firmware is always disruptive.
Note: The concurrent levels of system firmware may, on occasion, contain fixes that are known as Deferred and/or Partition-Deferred. Deferred fixes can be installed concurrently, but will not be activated until the next IPL. Partition-Deferred fixes can be installed concurrently, but will not be activated until a partition reactivate is performed. Deferred and/or Partition-Deferred fixes, if any, will be identified in the "Firmware Update Descriptions" table of this document. For these types of fixes (Deferred and/or Partition-Deferred) within a service pack, only the fixes in the service pack which cannot be concurrently activated are deferred.
Note: The file names and service pack levels used in the following examples are for clarification only, and are not necessarily levels that have been, or will be released.
System firmware file naming convention:
01ALXXX_YYY_ZZZ
XXX is the release level
YYY is the service pack level
ZZZ is the last disruptive service pack level
NOTE: Values of service pack and last disruptive service pack level (YYY and ZZZ) are only unique within a release level (XXX). For example, 01AL720_067_045 and 01AL740_067_053 are different service packs.
An installation is disruptive if:
The release levels (XXX) are different.
Example: Currently installed release is AL710, new release is AL720
The service pack level (YYY) and the last disruptive service pack level (ZZZ) are the same.
Example: AL720_120_120 is disruptive, no matter what level of AL720 is currently installed on the system
The service pack level (YYY) currently installed on the system is lower than the last disruptive service pack level (ZZZ) of the service pack to be installed.
Example: Currently installed service pack is AL720_120_120 and new service pack is AL720_152_130
An installation is concurrent if:
The release level (XXX) is the same, and
The service pack level (YYY) currently installed on the system is the same or higher than the last disruptive service pack level (ZZZ) of the service pack to be installed.
Example: Currently installed service pack is AL720_126_120, new service pack is AL720_143_120.
Firmware Information and Update Description
Filename Size Checksum
01AL730_099_035.rpm 34963657 60282
Note: The Checksum can be found by running the AIX sum command against the rpm file (only the first 5 digits are listed).
ie: sum 01AL730_099_035.rpm
AL730
For Impact, Severity and other Firmware definitions, Please refer to the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/we ... /home.html#termdefs
The complete Firmware Fix History for this Release Level can be reviewed at the following url:
http://download.boulder.ibm.com/ ... -Firmware-Hist.html收起
Applies to: 8202-E4B, 8205-E6B, 8231-E2B, 8233-E8B, 8236-E8C, 8492-DW2 and 8493-SV2
This document provides information about the installation of Licensed Machine or Licensed Internal Code, which is sometimes referred to generically as microcode or firmware.
Contents
1.0 Systems Affected
1.1 Minimum HMC Code Level
1.2 Minimum SDMC Code Level
2.0 Important Information
3.0 Firmware Information and Description
4.0 How to Determine Currently Installed Firmware Level
5.0 Downloading the Firmware Package
6.0 Installing the Firmware
7.0 Firmware History
8.0 Change History Revised (01/28/13)
1.0 Systems Affected
This package provides firmware for Power 710 (8231-E2B), Power 730 (8231-E2B), Power 720 (8202-E4B), Power 740 (8205-E6B, 8492-DW2 and 8493-SV2), Power 750 (8233-E8B) and Power 755 (8236-E8C) servers only.
The firmware level in this package is:
AL730_099
1.1 Minimum HMC Code Level
This section is intended to describe the "Minimum HMC Code Level" required by the System Firmware to complete the firmware installation process. When installing the System Firmware, the HMC level must be equal to or higher than the "Minimum HMC Code Level" before starting the system firmware update. If the HMC managing the server targeted for the System Firmware update is running a code level lower than the "Minimum HMC Code Level" the firmware update will not proceed.
The Minimum HMC Code level for this firmware is: HMC V7 R7.3.0 (PTF MH01255 or MH01256) with PTF MH01257 (Mandatory efix).
Although the Minimum HMC Code level for this firmware is listed above, HMC level V7 R7.3.0 with PTF MH01313 (Service Pack 4) and PTF MH01320 (Fix for V7R7.3.4), or higher is suggested for this firmware level.
For information concerning HMC releases and the latest PTFs, go to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
For specific fix level information on key components of IBM Power Systems running the AIX, IBM i and Linux operating systems, we suggest using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
NOTE: You must be logged in as hscroot in order for the firmware installation to complete correctly.
1.2 Minimum SDMC Code Level
This section is intended to describe the "Minimum Systems Director Management Console (SDMC) Code Level" required by the System Firmware to complete the firmware installation process. When installing the System Firmware, the SDMC level must be equal to or higher than the "Minimum SDMC Code Level" before starting the system firmware update. If the SDMC managing the server targeted for the System Firmware update is running a code level lower than the "Minimum SDMC Code Level" the firmware update will not proceed.
The Minimum SDMC Code level for this firmware is: SDMC V6 R7.3.0 with Mandatory PTF MF53082.
Although the Minimum SDMC Code level for this firmware is listed above, SDMC level V6.730 SP2 (MF54510), or higher is suggested for this firmware level.
For information concerning SDMC releases and the latest PTFs, go to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
For specific fix level information on key components of IBM Power Systems running the AIX, IBM i and Linux operating systems, we suggest using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
2.0 Important Information
Downgrading firmware from any given release level to an earlier release level is not recommended.
If you feel that it is necessary to downgrade the firmware on your system to an earlier release level, please contact your next level of support.
IPv6 Support and Limitations
IPv6 (Internet Protocol version 6) is supported in the System Management Services (SMS) in this level of system firmware. There are several limitations that should be considered.
When configuring a network interface card (NIC) for remote IPL, only the most recently configured protocol (IPv4 or IPv6) is retained. For example, if the network interface card was previously configured with IPv4 information and is now being configured with IPv6 information, the IPv4 configuration information is discarded.
A single network interface card may only be chosen once for the boot device list. In other words, the interface cannot be configured for the IPv6 protocol and for the IPv4 protocol at the same time.
Concurrent Firmware Updates
Concurrent system firmware update is only supported on HMC or SDMC - Managed Systems only.
Changes to DIMM VPD reported under FW Release AL730, for select DIMMs
After installation of AL730 firmware, select DIMMs may display VPD information that does not match the attached FRU label. The FRU number displayed may differ from the FRU number printed on the DIMM label.
This change would not apply when the server is running an earlier supported release of system firmware (ex. AL710, or AL720).
Changes in VPD (Vital Product Data) May be Reported for Feature Codes 4526, 4529, and 4528
Feature Code Supported
Systems Description DIMM FRU Label Under FW Release AL730,
VPD is displayed as the following
FRU Number CCIN FRU Number CCIN
4526 8202-E4B
8205-E6B
8231-E2B
8233-E8B
8236-E8C
8492-DW2
8493-SV2
4GB Memory DIMM
77P8784
31C5
78P0554
31F3
4529 8202-E4B
8205-E6B
8492-DW2
8493-SV2
8GB Memory DIMM
77P8919
31D2
78P0555
31F4
4528 8233-E8B
8236-E8C
16GB Memory DIMM
77P8633 31C9 78P0639 31F5
Note: This change does not apply to all DIMMs with the FRU numbers listed above, only a sub-set of DIMMs will report changes in VPD information. The change in displayed VPD information has no functional impact and does not affect the operation or reliability of the associated memory DIMMs, it simply reports select DIMMs with new VPD information as a means of differentiating their capabilities to service providers. Future service actions should be placed using the displayed VPD information, as logged by diagnostic and service related software, and not against the FRU number printed on the DIMM FRU label.
Memory Considerations for Firmware Upgrades
Firmware Release Level upgrades and Service Pack updates may consume additional system memory.
Server firmware requires memory to support the logical partitions on the server. The amount of memory required by the server firmware varies according to several factors.
Factors influencing server firmware memory requirements include the following:
Number of logical partitions
Partition environments of the logical partitions
Number of physical and virtual I/O devices used by the logical partitions
Maximum memory values given to the logical partitions
Generally, you can estimate the amount of memory required by server firmware to be approximately 8% of the system installed memory. The actual amount required will generally be less than 8%. However, there are some server models that require an absolute minimum amount of memory for server firmware, regardless of the previously mentioned considerations.
Additional information can be found at:
http://publib.boulder.ibm.com/in ... iphatlparmemory.htm
3.0 Firmware Information and Description
Use the following examples as a reference to determine whether your installation will be concurrent or disruptive.
For systems that are not managed by an HMC or SDMC, the installation of system firmware is always disruptive.
Note: The concurrent levels of system firmware may, on occasion, contain fixes that are known as Deferred and/or Partition-Deferred. Deferred fixes can be installed concurrently, but will not be activated until the next IPL. Partition-Deferred fixes can be installed concurrently, but will not be activated until a partition reactivate is performed. Deferred and/or Partition-Deferred fixes, if any, will be identified in the "Firmware Update Descriptions" table of this document. For these types of fixes (Deferred and/or Partition-Deferred) within a service pack, only the fixes in the service pack which cannot be concurrently activated are deferred.
Note: The file names and service pack levels used in the following examples are for clarification only, and are not necessarily levels that have been, or will be released.
System firmware file naming convention:
01ALXXX_YYY_ZZZ
XXX is the release level
YYY is the service pack level
ZZZ is the last disruptive service pack level
NOTE: Values of service pack and last disruptive service pack level (YYY and ZZZ) are only unique within a release level (XXX). For example, 01AL720_067_045 and 01AL740_067_053 are different service packs.
An installation is disruptive if:
The release levels (XXX) are different.
Example: Currently installed release is AL710, new release is AL720
The service pack level (YYY) and the last disruptive service pack level (ZZZ) are the same.
Example: AL720_120_120 is disruptive, no matter what level of AL720 is currently installed on the system
The service pack level (YYY) currently installed on the system is lower than the last disruptive service pack level (ZZZ) of the service pack to be installed.
Example: Currently installed service pack is AL720_120_120 and new service pack is AL720_152_130
An installation is concurrent if:
The release level (XXX) is the same, and
The service pack level (YYY) currently installed on the system is the same or higher than the last disruptive service pack level (ZZZ) of the service pack to be installed.
Example: Currently installed service pack is AL720_126_120, new service pack is AL720_143_120.
Firmware Information and Update Description
Filename Size Checksum
01AL730_099_035.rpm 34963657 60282
Note: The Checksum can be found by running the AIX sum command against the rpm file (only the first 5 digits are listed).
ie: sum 01AL730_099_035.rpm
AL730
For Impact, Severity and other Firmware definitions, Please refer to the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/we ... /home.html#termdefs
The complete Firmware Fix History for this Release Level can be reviewed at the following url:
http://download.boulder.ibm.com/ ... -Firmware-Hist.html收起
浏览4722