VL930
For Impact, Severity and other Firmware definitions, Please
refer to the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/webapp/set2/sas/f/power5cm/home.html#termdefs
The
complete Firmware Fix History for
this
Release Level can be
reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/VL-Firmware-Hist.html
|
VL930_101_040 / FW930.20
02/27/20 |
Impact:
Availability Severity: HIPER
New features and functions
- Support was added
for real-time data capture for PCIe3 expansion drawer (#EMX0) cable
card connection data via resource dump selector on the HMC or in ASMI
on the service processor. Using the resource selector string of
"xmfr -dumpccdata" will non-disruptively generate an RSCDUMP type of
dump file that has the current cable card data, including data from
cables and the retimers.
- Improvements to link stack algorithms.
System firmware changes that affect all systems
- HIPER/Pervasive:
A problem was fixed for a possible system crash and HMC "Incomplete"
state when a logical partition (LPAR) power off after a dynamic LPAR
(DLPAR) operation fails for a PCIe adapter. This scenario is
likely to occur during concurrent maintenance of PCIe adapters or for
#EMX0 components such as PCIe3 Cable adapters, Active Optical or copper
cables, fanout modules, chassis management cards, or midplanes.
The DLPAR fail can leave page table mappings active for the adapter,
causing the problems on the power down of the LPAR. If the system
does not crash, the DLPAR will fail if it is retried until a platform
IPL is performed.
- HIPER/Pervasive:
A problem was fixed for an HMC "Incomplete" state for a system after
the HMC user password is changed with ASMI on the service
processor. This problem can occur if the HMC password is changed
on the service processor but not also on the HMC, and a reset of the
service processor happens. With the fix, the HMC will get the
needed "failed authentication" error so that the user knows to update
the old password on the HMC.
- DEFERRED: A
problem was fixed
for a processor core failure with SRCs B150BA3C and BC8A090F logged
that deconfigures the entire processor for the current IPL. A
re-IPL
of the system will recover the lost processor with only the bad core
guarded.
- A problem was fixed for certain SR-IOV adapters that can
have an adapter reset after a mailbox command timeout error.
This fix updates the adapter firmware to 11.2.211.39 for the
following Feature Codes and CCINs: #EN15/EN16 with CCIN 2CE3,
#EN17/EN18 with CCIN 2CE4, #EN0H/EN0J with CCIN 2B93, #EN0M/EN0N with
CCIN 2CC0, #EN0K/EN0L with CCIN 2CC1, #EL56/EL38 with CCIN 2B93, and
#EL57/EL3C with CCIN 2CC1.
The SR-IOV adapter firmware level update for the shared-mode adapters
happens under user control to prevent unexpected temporary outages on
the adapters. A system reboot will update all SR-IOV shared-mode
adapters with the new firmware level. In addition, when an
adapter is first set to SR-IOV shared mode, the adapter firmware is
updated to the latest level available with the system firmware (and it
is also updated automatically during maintenance operations, such as
when the adapter is stopped or replaced). And lastly, selective
manual updates of the SR-IOV adapters can be performed using the
Hardware Management Console (HMC). To selectively update the
adapter firmware, follow the steps given at the IBM Knowledge Center
for using HMC to make the updates: https://www.ibm.com/support/knowledgecenter/en/POWER9/p9efd/p9efd_updating_sriov_firmware.htm.
Note: Adapters that are capable of running in SR-IOV mode, but are
currently running in dedicated mode and assigned to a partition, can be
updated concurrently either by the OS that owns the adapter or the
managing HMC (if OS is AIX or VIOS and RMC is running).
- A problem was fixed for an SR-IOV adapter failure with
B400FFxx errors logged when moving the adapter to shared mode.
This is an infrequent race condition where the adapter is not yet ready
for commands and it can also occur during EEH error recovery for the
adapter. This affects the SR-IOV adapters with the following
feature codes and CCINs: #EC2R/EC2S with CCIN 58FA;
#EC2T/EC2U with CCIN 58FB; #EC3L/EC3M with CCIN 2CEC; and #EC66/EC67
with CCIN 2CF3.
- A problem was fixed for an IPL failure with the following
possible SRCs logged: 11007611, 110076x1, 1100D00C, and
110015xx. The service processor may reset/reload for this
intermittent error and end up in the termination state.
- A problem was fixed for the location code of the Removable
EXchange (RDX) docking station being incorrectly reported as
P1-P3. The correct location code is Un-P3. This problem pertains
only to the S914 (9009-41A), S924 (9009-42A) and the H924 (9223-42H)
models. Please refer to the following IBM Knowledge Center
article for more information on the location codes: https://www.ibm.com/support/knowledgecenter/9009-42A/p9ecs/p9ecs_914_924_loccodes.htm
- A problem was fixed for delayed interrupts on a Power9
system following a Live Partition Mobility operation from a Power7 or
Power8 system. The delayed interrupts could cause device
time-outs, program dispatching delays, or other device problems on the
target Power9 system.
- A problem was fixed for processor cores not being able to
be used by dedicated processor partitions if they were DLPAR removed
from a dedicated processor partition. This error can occur if
there was a firmware assisted dump or a Live Partition Mobility (LPM)
operation after the DLPAR of the processor. A re-IPL of the
system will recover the processor cores.
- A problem was fixed for a B7006A96 fanout module FPGA
corruption error that can occur in unsupported PCIe3 expansion
drawer(#EMX0) configurations that mix an enhanced PCIe3 fanout module
(#EMXH) in the same drawer with legacy PCIe3 fanout modules (#EMXF,
#EMXG, #ELMF, or #ELMG). This causes the FPGA on the enhanced
#EMXH to be updated with the legacy firmware and it becomes a
non-working and unusable fanout module. With the fix, the
unsupported #EMX0 configurations are detected and handled gracefully
without harm to the FPGA on the enhanced fanout modules.
- A problem was fixed for lost interrupts that could cause
device time-outs or delays in dispatching a program process. This
can occur during memory operations that require a memory relocation for
any partition such as mirrored memory defragmentation done by the HMC
optmem command, or memory guarding that happens as part of memory error
recovery during normal operations of the system.
- A problem was fixed for extraneous informational logging of
SRC B7006A10 ("Insufficient SR-IOV resources available") with a 1306
PRC. This SRC is logged whenever an SR-IOV adapter is moved from
dedicated mode to shared mode. This SRC with the 1306 PRC should
be ignored as no action is needed and there is no issue with SR-IOV
resources.
- A problem was fixed for a hypervisor error during system
shutdown where a B7000602 SRC is logged and the system may also briefly
go "Incomplete" on the HMC but the shutdown is successful. The
system will power back on with no problems so the SRC can be ignored if
it occurred during a shutdown.
- A problem was fixed for possible dispatching delays for
partitions running in POWER8, POWER9_base or POWER9 processor
compatibility mode.
- A problem was fixed for extraneous B400FF01 and B400FF02
SRCs logged when moving cables on SR-IOV adapters. This is an
infrequent error that can occur if the HMC performance monitor is
running at the same time the cables are moved. These SRCs can be
ignored when accompanied by cable movement.
System firmware changes that affect certain systems
- DEFERRED: For
systems using the Feature Code #EPIM 8-core processor, a problem was
fixed for a slightly degraded UtlraTurbo maximum frequency
(approximately 3% less) compared to what is expected for this processor
chip. The fix requires new Workload Optimized Frequency (WOF)
tables for the processor, so the system must be re-IPLed for the
installed fix to be active. The WOF UltraTurbo maximum frequency
can only be achieved when turning cores off or operating below the 50%
workload capacity of the system.
- On systems with an IBM i partition, a problem was fixed
that occurs after a Live Partition Mobility (LPM) of an IBM i partition
that may cause issues including dispatching delays and the inability to
do further LPM operations of that partition. The frequency of
this problem is rare. A partition encountering this error can be
recovered with a reboot of the partition.
- On systems with an IBM i partition, a problem was fixed for
a D-mode IPL failure when using a USB DVD drive in an IBM 7226
multimedia storage enclosure. Error logs with SRC BA16010E,
B2003110, and/or B200308C can occur. As a circumvention, an
external DVD drive can be used for the D-mode IPL.
|
VL930_093_040 / FW930.11
12/11/19 |
Impact:
Availability Severity: SPE
New features and functions
- Support was added for a new 11-core POWER9 DD2.21 processor
module
with Feature Code #EP1H and CCIN 5C60. This support pertains only
to
the IBM Power System S924 (9009-42A) model.
- Support was added
to allow processor modules to have two different CCINs for modules in
the same system. This is needed to allow DD2.21 modules to
co-exist
with DD2.3 modules in DD2.2 mode.
System firmware changes that
affect all systems
- DEFERRED:
PARTITION_DEFERRED: A
problem was fixed for vHMC having no useable local graphics console
when installed on FW930.00 and later partitions.
- A problem was fixed for an IPMI
core dump and SRC B181720D logged, causing the service processor to
reset due to a low memory condition. The memory loss is triggered
by
frequently using the ipmitool to read the network configuration.
The
service processor recovers from this error but if three of these errors
occur within a 15 minute time span, the service processor will go to a
failed hung state with SRC B1817212 logged. Should a service
processor
hang occur, OS workloads will continue to run but it will not be
possible for the HMC to interact with the partitions. This
service
processor hung state can be recovered by doing a re-IPL of the system
with a scheduled outage.
- A problem was fixed for the
Advanced
System Management Interface (ASMI) menu for "PCIe Hardware
Topology/Reset link" showing the wrong value. This value is
always
wrong without the fix.
- A problem was fixed for PLL unlock
error
with SRC B124E504 causing a secondary error of PRD Internal
Firmware
Software Fault with SRC B181E580 and incorrect FRU call outs.
- A problem was fixed for an
initialization
failure of certain SR-IOV adapter ports during its boot, causing a
B400FF02 SRC to be logged. This is a rare problem and it recovers
automatically by the reboot of the adapter on the error. This
problem
affects the SR-IOV adapters with the following feature codes and CCINs:
#EC2R/EC2S with CCIN 58FA; #EC2T/EC2U with CCIN 58FB;
#EC3L/EC3M with
CCIN 2CEC; and #EC66/EC67 with CCIN 2CF3.
- A problem was fixed for the SR-IOV
Virtual
Functions (VFs) when the multi-cast promiscuous flag has been turned on
for the VF. Without the fix, the VF device driver sometimes
may
erroneously fault when it senses that the multi-cast promiscuous mode
had not been achieved although it had been requested.
- A problem was fixed for SR-IOV adapters to
provide a consistent Informational message level for cable plugging
issues. For transceivers not plugged on certain SR-IOV adapters,
an
unrecoverable error (UE) SRC B400FF03 was changed to an Informational
message logged. This affects the SR-IOV adapters with the
following
feature codes and CCINs: #EC2R/EC2S with CCIN 58FA; #EC2T/EC2U
with
CCIN 58FB; #EC3L/EC3M with CCIN 2CEC; and #EC66/EC67 with
CCIN 2CF3.
For copper cables unplugged on certain SR-IOV adapters, a missing
message was replaced with an Informational message logged. This
affects the SR-IOV adapters with the following feature codes and CCINs:
#EN17/EN18 with CCIN 2CE4, #EN0K/EN0L with CCIN 2CC1, and #EL57/EL3C
with CCIN 2CC1.
- A problem was fixed for
incorrect DIMM callouts
for DIMM over-temperature errors. The error log for the DIMM over
temperature will have incorrect FRU callouts, either calling out the
wrong DIMM or the wrong DIMM controller memory buffer.
- A problem was fixed
for an
Operations Panel hang after using it set LAN Console as the console
type for several iterations. After several iterations, the
operations
panel may hang with "Function 41" displayed on the operations
panel. A
hot unplug and plug of the operations panel can be used to recover it
from the hang.
- A problem was fixed for shared
processor
pools where uncapped shared processor partitions placed in a pool may
not be able to consume all available processor cycles. The
problem may
occur when the sum of the allocated processing units for the pool
member partitions equals the maximum processing units of the pool.
- A problem was fixed for
Novalink failing to activate partitions that have names with character
lengths near the maximum allowed character length. This problem
can be
circumvented by changing the partition name to have 32 characters or
less.
- A problem was fixed where a Linux or AIX partition type was
incorrectly reported as unknown. Symptoms include: IBM Cloud
Management Console (CMC) not being able to determine the RPA partition
type (Linux/AIX) for partitions that are not active; and HMC attempts
to dynamically add CPU to Linux partitions may fail with a HSCL1528
error message stating that there are not enough Integrated Facility for
Linux ( IFL) cores for the operation.
- A problem was fixed for a hypervisor
hang
that can occur on the target side when doing a Live Partition Mobility
(LPM) migration from a system that does not support encryption and
compression of LPM data. If the hang occurs, the HMC will go to
an
"Incomplete" state for the target system. The problem is rare
because
the data from the source partition must be in a very specific pattern
to cause the failure. When the failure occurs, a B182951C will be
logged on the target (destination) system and the HMC for the source
partition will issue the following message: "HSCLA318 The
migration
command issued to the destination management console failed with the
following error: HSCLA228 The requested operation cannot be performed
because the managed system <system identifier> is not in the
Standby or Operating state.". To recover, the target system must
be
re-IPLed.
- A problem was fixed for performance
collection tools not collecting data for event-based options.
This fix
pertains to perfpmr and tprof on AIX, and Performance Explorer (PEX) on
IBM i.
- A problem was fixed a Live
Partition
Mobility (LPM) migration of a large memory partition to a target system
that causes the target system to crash and for the HMC to go to the
"Incomplete" state. For servers with the default LMB size
(256MB), if
the partition is >=16TB and if the desired memory is different than
the maximum memory, LPM may fail on the target system. Servers
with
LMB sizes less than the default could hit this problem with smaller
memory partition sizes. A circumvention to the problem is to set
the
desired and maximum memory to the same value for the large memory
partition that is to be migrated.
- A problem was fixed for certain
SR-IOV adapters with the following issues:
1) If the SR-IOV logical port's VLAN ID (PVID) is modified while the
logical port is configured, the adapter will use an incorrect PVID for
the Virtual Function (VF). This problem is rare because most
users do
not change the PVID once the logical port is configured, so they will
not have the problem.
2) Adapters with an SRC of B400FF02 logged.
This fix updates the adapter firmware to 11.2.211.38 for the
following
Feature Codes and CCINs: #EN15/EN16 with CCIN 2CE3, #EN17/EN18
with
CCIN 2CE4, #EN0H/EN0J with CCIN 2B93, #EN0M/EN0N with CCIN 2CC0,
#EN0K/EN0L with CCIN 2CC1, #EL56/EL38 with CCIN 2B93, and #EL57/EL3C
with CCIN 2CC1.
The SR-IOV adapter firmware level update for the shared-mode adapters
happens under user control to prevent unexpected temporary outages on
the adapters. A system reboot will update all SR-IOV shared-mode
adapters with the new firmware level. In addition, when an
adapter is
first set to SR-IOV shared mode, the adapter firmware is updated to the
latest level available with the system firmware (and it is also updated
automatically during maintenance operations, such as when the adapter
is stopped or replaced). And lastly, selective manual updates of
the
SR-IOV adapters can be performed using the Hardware Management Console
(HMC). To selectively update the adapter firmware, follow the
steps
given at the IBM Knowledge Center for using HMC to make the
updates: https://www.ibm.com/support/knowledgecenter/en/POWER9/p9efd/p9efd_updating_sriov_firmware.htm.
Note: Adapters that are capable of running in SR-IOV mode, but are
currently running in dedicated mode and assigned to a partition, can be
updated concurrently either by the OS that owns the adapter or the
managing HMC (if OS is AIX or VIOS and RMC is running).
- A problem was fixed for certain SR-IOV adapters where after
some error conditions the adapter may hang with no messages or error
recovery. This is a rare problem for certain severe adapter
errors. This problem affects the SR-IOV adapters with the
following feature codes: #EC66/EC67 with CCIN 2CF3.
This problem can be recovered by removing the adapter from SR-IOV mode
and putting it back in SR-IOV mode, or the system can be re-IPLed.
- A problem was fixed for an
initialization
failure of certain SR-IOV adapters when changed into SR-IOV mode.
This
is an infrequent problem that most likely can occur following a
concurrent firmware update when the adapter also needs to be updated.
This problem affects the SR-IOV adapter with the following feature
codes and CCINs: #EC2R/EC2S with CCIN 58FA; #EC2T/EC2U with CCIN
58FB; #EC3L/EC3M with CCIN 2CEC; and #EC66/EC67 with CCIN
2CF3. This
problem can be recovered by removing the adapter from SR-IOV mode and
putting it back in SR-IOV mode, or the system can be re-IPLed.
- A problem was fixed for a false
memory
error that can be logged during the IPL with SRC BC70E540 with the
description "mcb(n0p0c1) (MCBISTFIR[12]) WAT_DEBUG_ATTN" but with no
hardware call outs. This error log can be ignored.
- A problem was fixed for an IPL
failure
after installing DIMMs of different sizes, causing memory access
errors. Without the fix, the memory configuration should be
restored
to only use DIMMs of the same size.
- A problem was fixed for a memory
DIMM
plugging rule violation that causes the IPL to terminate with an error
log with RC_GET_MEM_VPD_UNSUPPORTED_CONFIG IPL that calls out the
memory port but has no DIMM call outs and no DIMM deconfigurations are
done. With the fix, the DIMMs that violate the plugging rules
will be
deconfigured and the IPL will complete. Without the fix, the
memory
configuration should be restored to the prior working configuration to
allow the IPL to be successful.
- A problem was fixed for a B7006A22 Recoverable Error for
the enhanced PCIe3 expansion drawer (#EMX0) I/O drawer with fanout PCIe
Six Slot Fan Out modules (#EMXH) installed. This can occur up to two
hours after an IPL from power off. This can be a frequent
occurrence on an IPL for systems that have the PCIe Six Slot Fan Out
module (#EMXH). The error is automatically recovered at the
hypervisor level. If an LPAR fails to start after this error, a
restart of the LPAR is needed.
- A problem was fixed for degraded memory
bandwidth on systems with memory that had been dynamically repaired
with symbols to mark the bad bits.
- A problem was fixed for
an
intermittent IPMI core dump on the service processor. This occurs
only
rarely when multiple IPMI sessions are starting and cleaning up at the
same time. A new IPMI session can fail initialization when one of
its
session objects is inadvertently cleaned up. The circumvention is
to
retry the IPMI command that failed.
- A problem was fixed for
an
intermittent IPL failure with SRC B181E540 logged with fault signature
" ex(n2p1c0) (L2FIR[13]) NCU Powerbus data timeout". No FRU is
called
out. The error may be ignored since the automatic re-IPL is
successful. The error occurs very infrequently. This is the
second
iteration of the fix that has been released. Expedient routing of
the
Powerbus interrupts did not occur in all cases in the prior fix, so the
timeout problem was still occurring.
System firmware changes that
affect certain systems
- On systems with PCIe3
expansion
drawers(feature code #EMX0), a problem was fixed for a concurrent
exchange of a PCIe expansion drawer cable card, although successful,
leaves the fault LED turned on.
- On systems with 16GB huge-pages, a
problem was fixed for certain SR-IOV adapters with all or nearly all
memory assigned to them preventing a system IPL. This affects the
SR-IOV adapters with the following feature codes and CCINs: #EC2R/EC2S
with CCIN 58FA; #EC2T/EC2U with CCIN 58FB; #EC3L/EC3M with
CCIN
2CEC; and #EC66/EC67 with CCIN 2CF3. The problem can be
circumvented
by powering off the system and turning off all the huge-page
allocations.
- On systems running IBM i
partitions, a
problem was fixed for a NVME (Non-Volatile Memory Express) device load
source not being found for an IBM i boot partition. This can
occur on
a system with multiple load source candidates when the needed load
source is not the first entry in the namespace ID list. This
problem
can be circumvented by directing the System License Internal Code
(SLIC) Bootloader to a specific namespace and bypassing a search.
- On systems with IBM i
partitions, a
problem was fixed for Live Partition Mobility (LPM) migrations that
could have incorrect hardware resource information (related to VPD) in
the target partition if a failover had occurred for the source
partition during the migration. This failover would have to occur
during the Suspended state of the migration, which only lasts about a
second, so this should be rare. With the fix, at a minimum, the
migration error will be detected to abort the migration so it can be
restarted. And at a later IBMi OS level, the fix will allow the
migration to complete even though the failover has occurred during the
Suspended state of the migration.
- On systems running IBM i partitions,
a
problem was fixed for IBM i collection services that may produce
incorrect instruction count results.
- On systems running IBM i partitions,
a
performance improvement was made for the cache memory management of
workloads that utilize heavy I/O operations.
- On systems with IBM i partitions, a
rare
problem was fixed for an intermittent failure of a DLPAR remove of an
adapter. In most cases, a retry of the operation will be
successful.
- On systems with IBM i partitions, a
problem was fixed that was allowing V7R1 to boot on or be
migrated to
POWER9 servers. As documented in the System Software maps for IBM
i
(https://www-01.ibm.com/support/docview.wss?uid=ssm1platformibmi),
V7R1
IBM i software is not supported on POWER9 servers.
- On systems with IBM i partitions, a
problem was fixed for a LPAR restart error after a DLPAR of an active
adapter was performed and the LPAR was shut down. A reboot of the
system will recover the LPAR so it will start.
|
VL930_068_040 / FW930.03
08/22/19 |
Impact:
Data
Severity: HIPER
New features and functions
- Support was added
for processor module DD2.3 with CCIN 5C41 but all processor modules in
the system must have the same CCIN. These new processor modules
cannot be mixed with DD2.21 processor modules with CCIN 5C25
until service pack level FW930.10.
System firmware changes that affect all systems
- HIPER/Pervasive:
A change was made to fix an intermittent
processor anomaly that may result in issues such as operating system or
hypervisor termination, application segmentation fault, hang, or
undetected data corruption. The only issues observed to date have
been operating system or hypervisor terminations.
- A problem was fixed for a very intermittent partition error
when using Live Partition Mobility (LPM) or concurrent firmware
update. For a mobility operation, the issue can result in a
partition crash if the mobility target system is FW930.00, FW930.01 or
FW930.02. For a code update operation, the partition may
hang. The recovery is to reboot the partition after the crash or
hang.
System firmware changes that affect certain systems
- DEFERRED:
HIPER/Pervasive: A change was made to address a
problem causing SAS bus errors and failed/degraded SAS paths with SRCs
or SRNs such as these logged: 57D83400, 2D36-3109, 57D84040, 2D36-4040,
57D84060, 2D36-4060, 57D84061, 2D36-4061, 57D88130, 2D36-FFFE,
xxxxFFFE, xxxx-FFFE, xxxx4061 and xxxx-4061. These errors
occur intermittently for hard drives and solid state drives installed
in the two high-performance DASD backplanes (feature codes #EJ1M and
#EJ1D). This problem pertains to the 9009-41A, 9009-42A, and
9223-42H models only. Without the change, the circumvention
is to replace the affected DASD backplane.
|
VL930_048_040 / FW930.02
06/28/19 |
Impact:
Availability Severity: SPE
System firmware changes that
affect all systems
- A problem was fixed for a bad link for the PCIe3 expansion
drawer (#EMX0) I/O drawer with the clock enhancement causing a system
failure with B700F103. This error could occur during an IPL or a
concurrent add of the link hardware.
- A problem was fixed for On-Chip Controller (OCC) power
capping operation time-outs with SRC B1112AD3 that caused the system to
enter safe mode, resulting in reduced performance. The problem
only occurred when the system was running with high power consumption,
requiring the need for OCC power capping.
- A problem was fixed for the "PCIe Topology " option to get
cable information in the HMC or ASMI that was returning the wrong cable
part numbers if the PCIe3 expansion drawer (#EMX0) I/O drawer
clock enhancement was configured. If cables with the incorrect
part numbers are used for an enhanced PCIe3 expansion drawer
configuration, the hypervisor will log a B7006A20 with PRC 4152
indicating an invalid configuration - https://www.ibm.com/support/knowledgecenter/9080-M9S/p9eai/B7006A20.htm.
- A problem was fixed for a drift in the system time (time
lags and the clock runs slower than the true value of time) that occurs
when the system is powered off to the service processor standby
state. To recover from this problem, the system time must be
manually corrected using the Advanced System Management Interface
(ASMI) before powering on the system. The time lag increases in
proportion to the duration of time that the system is powered off.
|
VL930_040_040 / FW930.01
05/31/19 |
Impact:
Availability Severity: HIPER
System firmware changes that
affect certain systems
- HIPER/Pervasive:
DISRUPTIVE: For systems at VL930_035 (FW930.00) with LPARs
using a VIOS for virtual adapters or using VIOS Shared Storage Pool
(SSP) clusters, a problem was fixed for a possible network hang in the
LPAR after upgrading from FW910.XX to FW930.00. Systems with IBM
i partitons and HSM may see extraneous resources, with the old ones
non-reporting. With the problem, the I/O adapter port location
code names had changed from that used for the FW910 release, and this
difference in the naming convention prevents the VIOS virtual adapters
from working in some cases. For example, NPIV (N_PORT ID
Virtualization) Fibre Channel (FC) adapters fail to work because of the
I/O mappings are different. With the fix, the I/O adapter
location code naming convention reverts back to that used for
FW910. There could be other impacts not described
here to operating system views of IO devices and IBM strongly
recommends that customers at FW930.00 update to this new level or
higher. Customers upgrading from FW910.xx levels to FW930.01 or
later are not affected by this problem.
The following is an example of the original location code format and
the problem version of the location code name (notice that "001" was
replaced by "ND1"):
Original format: "fcs0 U78D2.001.WZS000W-P1-C6 Available 01-00 8Gb PCI
Express Dual Port FC Adapter (df1000f114108a03)"
Problem format: "fcs0 U78D2.ND1.WZS000W-P1-C6 Available 01-00 8Gb PCI
Express Dual Port FC Adapter (df1000f114108a03)"
If you have a FW930.00 (VL930_035) installed, please follow the steps
outlined in the "Important Information applicable only for systems at
VL930_035 (FW930.00) with VIOS partitions or IBM i HSM" section
of the README.
|
VL930_035_035 / FW930.00
05/17/19 |
Impact:
New
Severity: New
All features and fixes from the FW910.30 service pack (and below) are
included in this release.
New Features and Functions
- Support was added to allow the FPGA soft error checking on
the PCIe I/O expansion drawer (#EMX0) to be disabled with the help of
IBM support using the hypervisor "xmsvc" macro. This new setting
will persist until it it is changed by the user or IBM support.
The effect of disabling FPGA soft error checking is to eliminate the
FPGA soft error recovery which causes a recoverable PCIe adapter
outage. Some of the soft errors will be hidden by this change but
others may have unpredictable results, so this should be done only
under guidance of IBM support.
- Support for the PCIe3 expansion drawer (#EMX0) I/O
drawer clock enhancement so that a reset of the drawer does not affect
the reference clock to the adapters so the PCIe lanes for the PCIe
adapters can keep running through an I/O drawer FPGA reset. To
use this support, new cable cards, fanout modules, and optical cables
are needed after this support is installed: PCIe Six Slot Fan out
module(#EMXH) - only allowed to be connected to converter adapter cable
card; PCIe X16 to CXP Optical or CU converter adapter for the
expansion drawer (#EJ1R); and new AOC cables with feature/part number
of #ECCR/78P6567, #ECCX/78P6568, #ECCY/78P6569, and #ECCZ/78P6570.
These parts cannot be install concurrently, so a scheduled outage is
needed to complete the migration.
- Support added for RDMA Over Converged Ethernet (RoCE) for
SR-IOV adapters.
- Support added for SMS menu to enhance the I/O
information option to have "vscsi" and "network" options. The
information shown for "vscsi" devices is similar to that provided for
SAS and Fibre Channel devices. The "network" option provides
connectivity information for the adapter ports and shows which can be
used for network boots and installs.
- Support for an IBM i system with a SAN boot feature code
that can be ordered without an internal DASD backplane, SAS cables, or
SAS adapters.
- Support added to allow integrated USB ports to be
disabled. This is available via an Advanced System Management
Interface (ASMI) menu option: "System Configuration ->
Security -> USB Policy". The USB disable policy, if selected,
does not apply to pluggable USB adapters plugged into PCIe slots such
as the 4-Port USB adapter (#EC45/#EC46), which are always enabled.
System firmware changes that
affect all systems
- A problem was fixed for a system
IPLing with an invalid time set on the service processor that causes
partitions to be reset to the Epoch date of 01/01/1970. With the
fix,
on the IPL, the hypervisor logs a B700120x when the service processor
real time clock is found to be invalid and halts the IPL to allow the
time and date to be corrected by the user. The Advanced System
Management Interface (ASMI) can be used to correct the time and date on
the service processor. On the next IPL, if the time and date have
not
been corrected, the hypervisor will log a SRC B7001224 (indicating the
user was warned on the last IPL) but allow the partitions to start, but
the time and date will be set to the Epoch value.
|