× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IBM republished this with a text update, see in bold below.

I’m at VL910_135 FW910.30, so not impacted by this problem.
However, applying this firmware would still be DISRUPTIVE, implying cannot do concurrently, all LPARs must be down.
Am I reading this correctly?


Microcode Update for MTMs 9008-22L; 9009-22A; 9009-41A; 9009-42A; 9223-22H;...

Resending this subscription bulletin due to a text update (for FW910.xx levels to FW930.01 or later) - See in Bold Below
Updated microcode for Machine-Type Model: 9008-22L; 9009-22A; 9009-41A; 9009-42A; 9223-22H; 9223-42H
System Firmware Level: VL930_040
This package provides firmware for Power Systems L922 (9008-22L), Power System S922 (9009-22A), Power System S914 (9009-41A), Power System S924 (9009-42A), Power System H922 (9223-22H) and Power System H924 (9223-42H. ) servers only.
Note: This Disruptive Service Pack addresses the following HIPER issue:
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.

Paul


From: Steinmetz, Paul
Sent: Monday, June 03, 2019 9:03 AM
To: 'Midrange Systems Technical Discussion'
Subject: Updated microcode for Machine-Type Model: 9008-22L; 9009-22A; 9009-41A; 9009-42A; 9223-22H; 9223-42H - HIPER/Pervasive: DISRUPTIVE

Microcode Update for MTMs 9008-22L; 9009-22A; 9009-41A; 9009-42A; 9223-22H;...
Updated microcode for Machine-Type Model: 9008-22L; 9009-22A; 9009-41A; 9009-42A; 9223-22H; 9223-42H
System Firmware Level: VL930_040
This package provides firmware for Power Systems L922 (9008-22L), Power System S922 (9009-22A), Power System S914 (9009-41A), Power System S924 (9009-42A), Power System H922 (9223-22H) and Power System H924 (9223-42H. ) servers only.
Note: This Disruptive Service Pack addresses the following HIPER issue:
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 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.
Visit Fix Central <https://www-945.ibm.com/support/fixcentral/> for all the latest updates.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.