PACKAGE: Update Release 3.1.3.30
IOSLEVEL: 3.1.3.30
VIOS level is |
The AIX level of the NIM Master
level must be equal to or higher than |
Update Release 3.1.3.30 |
AIX
7200-05-05 |
Please refer to the VIOS Maintenance Strategy here
for more details regarding the change to the VIOS release numbering scheme.
Be sure to heed all minimum space requirements before
installing.
Review the list of fixes included in Update Release 3.1.3.30
To take full advantage of all the functions available
in the VIOS, it may be necessary to be at the latest system firmware level. If
a system firmware update is necessary, it is recommended that the firmware be
updated before you update the VIOS to Update Release 3.1.3.30.
Microcode or system firmware
downloads for Power Systems
If the VIOS being updated has filesets installed from
the VIOS Expansion Pack, be sure to update those filesets with the latest VIOS
Expansion Pack if updates are available.
Update Release 3.1.3.30
updates your VIOS partition to ioslevel 3.1.3.30.
To determine if Update Release 3.1.3.30
is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release 3.1.3.30
is installed, the command output is 3.1.3.30.
For Customers Using Third Party
Java-based Software
This only applies to customers who both use third
party Java based software and have run updateios -remove_outdated_filesets to
remove Java 7 from their system.
To prevent errant behavior when editing customer’s /etc/environment file,
updateios does not make changes to that file when run. If a customer is using
software that depends on using Java and having the path to it in your PATH
environment variable, the following edit should be made to allow programs that
use the PATH environment variable to locate Java 8.
In
the /etc/environment file, customers should see:
PATH=[various
directories]:/usr/java7_64/jre/bin:/usr/java7_64/bin
To
address a potential issue with Java-dependent third-party software, this should
be converted to:
PATH=[various
directories]:/usr/java8_64/jre/bin:/usr/java8_64/bin
VIOS 3.1.3.30 includes the
following features, added in VIOS 3.1.3.10:
LU Rename Support Added for
Shared Storage Pool (SSP)
Support has been added to allow users to rename their
LUs. This operation can be performed via the new flag, [-modify], added
to the lu command in ioscli.
The ability to convert LUs from the thin provisioned
to thick provisioned dynamically has been added. Performed via the new [-modify]
flag added to the lu command in ioscli, this feature allows users to
preallocate storage for existing LUs, rather than being forced to continue to
rely on the just-in-time provisioning after the LU has been created.
Note: This feature currently only
allows for unmapped LUs to have their provisioning changed to thick. An
enhancement for this feature is in development that will allow users to thicken
mapped LUs and will be added in a future release.
VIOSBR Multiple Network
Interface Support for SSP
In earlier VIOS releases where multiple network
interfaces were supported, VIOS Backup and Restore did not fully support the
feature. This meant that when an SSP Cluster was restored from a backup, any
network interfaces that were being used other than the primary had to be added
back manually. In this release, the restore operation will now restore all
network interfaces.
Other Noteworthy Changes
· SSP
IO performance improvements are available for fast SSD and NVMe storage.
· The
SSP and Change Management databases have been upgraded from Postgres 10 to
Postgres 13, a change that brings with it all the improvements to Postgres that
have been added in versions 11, 12, and 13.
Note: In order to move an
existing SSP Cluster to Postgres 13, a rolling upgrade must complete first. A
prerequisite for the rolling upgrade to occur is that all nodes in the cluster
be at version 3.1.3.30 or later.
VIOS 3.1.3.30 can run on any of the following Power
Systems:
POWER 8 or later.
The following requirements and limitations apply to Shared Storage Pool
(SSP) features and any associated virtual storage enhancements.
Software Installation
SSP Configuration
Feature |
Min |
Max |
Number of VIOS
Nodes in Cluster |
1 |
16* |
Number of
Physical Disks in Pool |
1 |
1024 |
Number of
Virtual Disks (LUs) Mappings in Pool |
1 |
8192 |
Number of
Client LPARs per VIOS node |
1 |
250* |
Capacity
of Physical Disks in Pool |
10GB |
16TB |
Storage Capacity
of Storage Pool |
10GB |
512TB |
Capacity
of a Virtual Disk (LU) in Pool |
1GB |
4TB |
Number of
Repository Disks |
1 |
1 |
Capacity
of Repository Disk |
512MB |
1016GB |
Number of
Client LPARs per Cluster |
1 |
2000 |
Prerequisites for expanded support:
Here are the new maximum values for each of these
configuration options, if the associated hardware specification has been met:
Feature |
Default
Max |
High
Spec Max |
Number of
VIOS Nodes in Cluster |
16 |
24 |
Number of
Client LPARs per VIOS node |
250 |
400 |
Network Configuration
Storage Configuration
Shared Storage Pool capabilities and limitations
Please ensure that your rootvg contains at
least 30 GB and that there is at least 4GB free space before you attempt to update to
Update Release 3.1.3.30. Run the lsvg
rootvg command, and then ensure
there is enough free space.
Example:
$ lsvg rootvg |
|
|
|
VOLUME GROUP: |
rootvg |
VG IDENTIFIER: |
00f6004600004c000000014306a3db3d |
VG STATE: |
active |
PP SIZE: |
64 megabyte(s) |
VG PERMISSION: |
read/write |
TOTAL PPs: |
511 (32704 megabytes) |
MAX LVs: |
256 |
FREE PPs: |
64 (4096 megabytes) |
LVs: |
14 |
USED PPs: |
447 (28608 megabytes) |
OPEN LVs: |
12 |
QUORUM: |
2 (Enabled) |
TOTAL PVs: |
1 |
VG DESCRIPTORS: |
2 |
STALE PVs: |
0 |
STALE PPs: |
0 |
ACTIVE PVs: |
1 |
AUTO ON: |
yes |
MAX PPs per VG: |
32512 |
|
|
MAX PPs per PV: |
1016 |
MAX PVs: |
32 |
LTG size (Dynamic): |
256 kilobyte(s) |
AUTO SYNC: |
no |
HOT SPARE: |
no |
BB POLICY: |
relocatable |
PV RESTRICTION: |
none |
INFINITE RETRY: |
no |
A single, merged
lpp_source is not supported for VIOS that uses SDDPCM. However, if you use
SDDPCM, you can still enable a single boot update by using the alternate method
described at the following location:
SDD and SDDPCM migration
procedures when migrating VIOS from version 1.x to version 2.x
Virtual I/O Server support for Power Systems
VIOS Update
Release 3.1.3.30 may be applied directly to any VIOS at level 3.1.0.00.
The VIOS must
first be upgraded to 3.1.0.00 before the 3.1.3.30 update can be applied. To learn more about how to do that, please
read the information provided here.
Warning: The
update may fail if there is a loaded media repository.
To check for a
loaded media repository, and then unload it, follow these steps.
1. To check for loaded images, run the following command:
$ lsvopt
The Media column lists any loaded media.
2. To unload media images, run the following commands on all Virtual Target
Devices that have loaded images.
$ unloadopt
-vtd <file-backed_virtual_optical_device >
3. To verify that all media are unloaded, run the following command again.
$ lsvopt
The command output should show No
Media for all VTDs.
The Virtual I/O
Server (VIOS) Version 2.2.2.1 or later, supports rolling updates for SSP
clusters. The VIOS can be updated to Update Release 3.1.3.30 using rolling
updates.
Non-disruptive
rolling updated to VIOS 3.1 requires all SSP nodes to be at VIOS 2.2.6.31 or
later. See detailed instructions in the VIOS 3.1 documentation
The rolling updates
enhancement allows the user to apply Update Release 3.1.3.30 to the VIOS
logical partitions in the cluster individually without causing an outage in the
entire cluster. The updated VIOS logical partitions cannot use the new SSP
capabilities until all VIOS logical partitions in the cluster are updated.
To upgrade the
VIOS logical partitions to use the new SSP capabilities, ensure that the
following conditions are met:
·
All VIOS logical partitions must have
VIOS Update Release version 2.2.6.31 or later installed.
·
All VIOS logical partitions must be
running. If any VIOS logical partition in the cluster is not running, the
cluster cannot be upgraded to use the new SSP capabilities.
Instructions: Verify
the cluster is running at the same level as your node.
1. Run the following command:
$ cluster -status -verbose
2. Check the Node Upgrade Status field, and you should see one of the
following terms:
UP_LEVEL: This means that the software level of the logical partition is higher
than the software level the cluster is running at.
ON_LEVEL: This means the software level of the logical partition and the
cluster are the same.
There is now a
method to verify the VIOS update files before installation. This process
requires access to openssl by the 'padmin' User, which can be accomplished by
creating a link.
Instructions: Verifying VIOS update files.
To verify the VIOS
update files, follow these steps:
1. $ oem_setup_env
2. Create a link to openssl
# ln
-s /usr/bin/openssl /usr/ios/utils/openssl
3.
Verify the link to openssl was created
# ls
-alL /usr/bin/openssl /usr/ios/utils/openssl
4.
Verify that both files display similar
owner and size
5. # exit
Use one of the
following methods to install the latest VIOS Service Release. As with all
maintenance, you should create a VIOS backup before making changes.
If you are running
a Shared Storage Pool configuration, you must follow the steps in Migrate Shared Storage Pool Configuration.
Note:
While running 'updateios' in the following steps, you may see accessauth messages, but these messages can safely be
ignored.
Version Specific Warning: Version 3.1.1.30 or earlier, Version 3.1.2.10 or earlier
When updating to VIOS 3.1.3.30 from some earlier versions of VIOS 3.1.X.X, it
is possible to encounter the following error:
installp: The installp command has been updated.
Reinvoking installp
to process the
remaining items.
Unable to set up
Trusted Execution environment for Installation to proceed.
0503-430
installp: Either there is an installp
process currently running or there is a previously failed installation.
Wait for the
process to complete or run installp -C to cleanup a failed installation.
To
remedy this issue, once updateios stops running, run updateios -commit and then
rerun the update.
Warning: If VIOS rules
have been deployed.
During update, there have been occasional issues with VIOS Rules files getting
overwritten and/or system settings getting reset to their default values.
To ensure that this doesn’t affect you, we
recommend making a backup of the current rules file. This file is located here:
/home/padmin/rules/vios_current_rules.xml
First, to capture your current system settings, run this command:
$ rules
-o capture
Then, either copy the file to a backup
location, or save off a list of your current rules:
$ rules -o list > rules_list.txt
After this is complete, proceed to update
as normal. When your update is complete,
check your current rules and ensure that they still match what is desired. If not, either overwrite the original rules
file with your backup, or proceed to use the ‘rules -o modify’ and/or ‘rules -o
add’ commands to change the rules to match what is in your backup file.
Finally, if you’ve failed to back up your
rules, and are not sure what the rules should be, you can deploy the
recommended VIOS rules by using the following command:
$ rules -o deploy -d
Then, if you wish to copy these new VIOS
recommended rules to your current rules file, just run:
$ rules -o capture
Note: This will
overwrite any customized rules in the current rules file.
Applying Updates
Warning:
If the target node
to be updated is part of a redundant VIOS pair, the VIOS partner node must be
fully operational before beginning to update the target node.
Note:
For VIOS nodes that
are part of an SSP cluster, the partner node must be shown in 'cluster -status ' output as having a cluster status of
OK and a pool status of OK. If the target node is updated before its VIOS
partner is fully operational, client LPARs may crash.
Instructions: Applying updates to a VIOS.
2. Using ftp, transfer the update file(s) to the directory you created.
To apply updates from a remotely mounted file system, and the remote file
system is to be mounted read-only, follow the steps:
The update release
can be burned onto a CD by using the ISO image file(s). To apply updates from
the CD/DVD drive, follow the steps:
$ shutdown
-restart
Note: If shutdown –restart command failed, run swrole –PAdmin for padmin to set authorization and
establish access to the shutdown command properly.
$ clstartstop
-start -n <cluster_name >
-m <hostname >
$ ioslevel
Instructions: Checking for an incomplete installation caused by a loaded media
repository.
After installing
an Update Release, you can use this method to determine if you have encountered
the problem of a loaded media library.
Check the Media
Repository by running this command:
$ lsrep
If the command
reports: "Unable to retrieve repository data due to incomplete repository
structure," then you have likely encountered this problem during the
installation. The media images have not been lost and are still present in the
file system of the virtual media library.
Running the lsvopt command should show the media images.
Instructions: Recovering from an incomplete installation
caused by a loaded media repository.
To recover from this
type of installation failure, unload any media repository images, and then
reinstall the ios.cli.rte package. Follow these steps:
1. Unload any media images
$ unloadopt
-vtd <file-backed_virtual_optical_device>
2. Reinstall the ios.cli.rte fileset by running the following
commands.
To escape the
restricted shell:
$ oem_setup_env
To install the failed fileset:
# installp
–Or –agX ios.cli.rte –d <device/directory >
To return to the restricted
shell:
# exit
3. Restart the VIOS.
$ shutdown
–restart
4. Verify that the Media Repository is operational by running this command:
$ lsrep
This release also contains all the fixes
for every previous version of 3.1.3.X. To see the previous release’s fixes,
please go here.
The
list of new fixes included in 3.1.3.30.
APAR |
Description |
IJ33830 |
NO LDAP
DEFAULT USER COULD CAUSE ISSUES WITH LOGIN OR CACHE |
IJ43189 |
0590-102
INCORRECT PROFILE - UPDATEIOS FROM 3.1.3.14 TO 3.1.3. |
IJ35810 |
Install
images for devices.ethernet.sha |
IJ36153 |
MEMORY
LEAKS IN EFS CODE |
IJ37822 |
REMOVING
EMC FILESETS MAY LEAVE ENTRIES IN DEFAULT RULES FILE |
IJ38044 |
VIOS
SSP MAY BECOME UNRESPONSIVE WITH LU/CLONE REMOVE |
IJ38240 |
MULTIBYTE
CHARACTER HANDLING IS INCORRECT WHEN LANG IS CHANGED I |
IJ38304 |
LOGINRESTRICTIONS
COULD FAIL WITH COMPLEX SYSTEM GRAMMAR |
IJ38788 |
RAS
REGISTRATION FAILED, RASCB POINTS TO RAS_BLOCK_INVALID |
IJ38838 |
CAA
node crash on NODE ADD |
IJ38922 |
IPL_VARYON
BOOT HANGS AT LED 551 FOR VERY LONG TIME |
IJ39138 |
no
accepting value of minus |
IJ39339 |
CAA
LACP handling for high load |
IJ39375 |
VIOSMGR
CORE DUMPS WHILE GATHERING QUERY_FC_PORTS ODM DATA |
IJ39451 |
C_Encrypt()
returns CKR_DATA_INVALID for CKM_RSA_X_509 |
IJ39579 |
SSP
DISK VALIDATION FAILURE MAY AFFECT POOLFS ON ALL NODES |
IJ39720 |
VIOGETPGDBVERSION
CALLS VIOREADENTIREFILE BUT DOESNT FREE ALLOC |
IJ39759 |
AUDIT
SHUTDOWN CRASH WITH MODS IS ENABLED |
IJ39876 |
A
potential security issue exists |
IJ40126 |
FC5899
MUSENT64.KDB MISSING ENTRIES IN TSD |
IJ40248 |
WRITESRV
IS STUCK CONSUMING CPU OR CORE DUMPS |
IJ40276 |
VIOSBR:
COPY BACKUP XML FILE WHEN INTEGRITY XML CHECK FAIL |
IJ40276 |
VIOSBR:
COPY BACKUP XML FILE WHEN INTEGRITY XML CHECK FAIL |
IJ40281 |
LKU:
DUPLICATE IP ERRORS |
IJ40283 |
LKU:
SURROGATE CRASHING DURING NFS SWAP DEVICE CREATION |
IJ40735 |
TRCUPDATE
CAN FAIL WHEN UPDATING TO GPFS 5.1 |
IJ40737 |
FCSTAT
FOR CVFCDD ADAPTERS SHOWS SECONDS SINCE LAST RESET=0 |
IJ40771 |
Crash
in dtSplitPage when zombie deletes EA file |
IJ40865 |
LSGROUP
MAY NOT RESOLVE NESTED GROUPS FOR AD |
IJ40872 |
LPM
VALIDATION PROCESS MAY TAKE LONG TO COMPLETE |
IJ40912 |
NIM
SAVEVG OR MKSYSB ESTIMATED SIZE COMPUTATION CAN BE WRONG |
IJ40943 |
SRC_TRYX,
SRC_RSTRT ERRLOG ENTRIES WITH ASO IN VIOS ENVIRONMENT |
IJ40952 |
A
potential security issue exists |
IJ41092 |
Crash
on p10 AIX LPAR testing Oracle RAC |
IJ41139 |
DNS
forwarders - cache poisoning vulnerability |
IJ41144 |
lpar
crashed @gids_ok+000060 |
IJ41259 |
ERRPT
SEA HA STATE TRANSITION MESSAGES SAY "NONE" |
IJ41330 |
vlan
devices may fail to get the updated link status |
IJ41419 |
PASSWORD
HISTORY CHECK NOT WORKING WITH PREFIX_DOLLAR |
IJ41478 |
KSH93
HANG WHEN RECEIVING SIGIO |
IJ41498 |
HIt
crash with xml variation test run on 72X |
IJ41501 |
memory
leak in socket structures |
IJ41535 |
Create MAX_WQ_THREADS
in URH and CACHE ASYNC. |
IJ41666 |
A
potential security issue exists |
IJ41685 |
A
potential security issue exists |
IJ41812 |
SNMP
DAEMONS ARE NOT STARTED AFTER LIVEUPDATE |
IJ42009 |
vfchost
state is defined |
IJ42233 |
A potential
security issue exists |
IJ42233 |
A
potential security issue exists |
IJ42312 |
Disk
elevator queue performance tweak |
IJ42663 |
VNIC
CLIENT: DSI IF PROCESSING IOCTL DURING VNICSERVER FAILOVER |
IJ43181 |
CHFS -N
SETS NODENAME ON JFS2 FILESYSTEM |
IJ43182 |
LDAP
FAILED TO SEARCH NETGROUP CN=) ERROR |
IJ43183 |
GSSD /
KRB5 MEMORY LEAKS |
IJ43184 |
MPSTAT
-S DOESN'T DISPLAY TOTAL PROC USAGE WITH DEDICATED CPU |
IJ43187 |
NFS4
MOUNT FAILS WITH NETAPP SERVER DUE TO SUPPATTR_EXCLCREAT |
IJ43190 |
motd
may not update properly after running rulescfgset |
IJ43191 |
wwpn
for fcs1 id is always showing "00000000 |
IJ43192 |
Cluster/SSP
data are not updating in SSP GET call |
IJ43193 |
IPRA.$_config_args
core dump during COMMIT_LVL script |
IJ43195 |
Abend_trap
in tstart with IPSec filter enabled |
IJ43196 |
bos.perf.pmaix
update has empty pmperfrec |
IJ43197 |
garbled
title in ICON Editor |
IJ43198 |
VIOS
SSP pool deadlock with expel and pool event monitoring |
IJ43200 |
MFS
resign while backing out add disk after error |
IJ43202 |
migratable
Status in nmon |
IJ43204 |
CAA
TIMERS MAY CAUSE ABEND DURING SHUTDOWN |
IJ43207 |
TCP/UDP
apps may not work with IPsec IPv6 TCP/UDP tunnels |
IJ43208 |
lpar
crashed @___memmove64+000088 |
IJ43208 |
lpar
crashed @___memmove64+000088 |
IJ43209 |
system
crash when using ipv6 |
IJ43210 |
Mismatch
in SSP cluster info between SSP PCM Prefere |
IJ43211 |
Timing
issue - ICMP unreachable might crash the system |
IJ43212 |
A
potential security issue exists |
IJ43213 |
lpar
got hung @ipoll_wait_test+000000 |
IJ43214 |
ASO
Increase domain consumption threshold |
IJ43215 |
dnssec-keygen
can not load translation message for usage |
IJ43216 |
lpar
crashed @unlock_enable_mem+0001C4 |
IJ43217 |
A
potential security issue exists |
IJ43218 |
X11
Buffer Overflow(AIX Penetration Test) |
IJ43222 |
VIOS
crashed during disconnect with active cmds |
IJ43223 |
NEED TO
ADD 'DISK/FCP/POWERSTORE' TO THIS EMCODMTABLE[] |
IJ43224 |
SLOW
NPIV I/O RESPONSE ON AIX LPAR BACKED BY QLOGIC HBA |
IJ43225 |
FCSTAT
REPORTS INVALID NO COMMAND RESOURCE COUNT |
IJ43226 |
Node is
unable to elect due to error querying CAA. |
IJ43227 |
Add
wprotected field to SCSI disk kdb output |
IJ43228 |
Issue
in getting port from DB when user passes FC port |
IJ43230 |
crash @
vfc_npiv_query_channels_resp+0002C0 |
IJ43231 |
Firmware
update of FCNVMe capable FC HBA causes errlog entry |
IJ43232 |
Inquiry
83 retried too many times when LUN is unmapped |
IJ43233 |
Cluster
-create or election fails on a node. |
IJ43234 |
Disks
fail to cfg with cfg_vfc core in clnt |
IJ43235 |
Add
flexctl support to Marvell FC adapter driver |
IJ43236 |
LPM can
fail under certain rare conditions |
IJ43237 |
System
may hang in certain error conditions |
IJ43238 |
System
crash at scsidisk_d_q_cmd with EEH reset |
IJ43240 |
Remove
stale entry in ODM vscsi adapter attribute "rw_timeout" |
IJ43241 |
aix
npiv clnt crash@emfsc_strategy_sanity() |
IJ43242 |
iSCSI
disk close hangs |
IJ43243 |
Core
dumps within viodTrace() in vio_daemon. |
IJ43246 |
ssp lu
remove command may succeed when supposed to fail. |
IJ43247 |
Unconfigure
of vfchost adapter may fail after SRR |
IJ43248 |
System
crash observed microcode with EEH |
IJ43249 |
Request
to have optics FRU information added to Diagnostic |
IJ43252 |
Async
adapter diagnostics cause INTRPPC_ERR/ExIntrFlih in errlog |
IJ43262 |
SAVEBASE
CAN HANG WHEN AIX_STDBUFSZ IS SET |
IJ43264 |
sec_open()
failed on NFS files some times. |
IJ43265 |
A
potential security issue exists |
IJ43266 |
SYSTEM
CRASH IN VNC_PURGE() WITH SKEY EXCEPTION |
IJ43267 |
VSCR
register not context managed by facility_enable |
IJ43269 |
Crash
in remove_child_sibling_link due to Data Storage Interrupt |
IJ43270 |
Errors
shrinkfs/reclaimfs error path |
IJ43272 |
Slow
shrinkfs and defragfs performance |
IJ43273 |
System
crashed at groupsetfree |
IJ43274 |
Crash
in iKill while deleting a zombie file |
IJ43276 |
lpar
got hung @krlock_confer_norestart |
IJ43279 |
m_pullup
infinite loop when len = MHLEN and mbuf has M_EXT |
IJ43281 |
A
potential security issue exists |
IJ43282 |
ostd_mem_expand
needs to check for proper context |
IJ43283 |
Trying
to bind an invalid socket might result in system crash |
IJ43284 |
A
potential security issue exists |
IJ43286 |
A
potential security issue exists |
IJ43287 |
Add
check in gil thread |
IJ43288 |
A
potential security issue exists |
IJ43289 |
A
potential security issue exists |
IJ43290 |
A
potential security issue exists |
IJ43291 |
A
potential security issue exists |
IJ43292 |
A
potential security issue exists |
IJ43293 |
A
potential security issue exists |
IJ43294 |
A
potential security issue exists |
IJ43300 |
System
crash observed while microcode with EEH |
IJ43301 |
EEH PERM
Error while Restarting prevents moving to Dead state |
IJ43304 |
libviocmnotify.a
entry missing in TSD on vios |
IJ43311 |
ADD
"DELAY_LOG" ODM ATTRIBUTE TO ETHCHANDD |
IJ43312 |
AIXIF_ARP_DUP_ADDR
ERROR IN ETHERCHANNEL TEAMING MODE |
IJ43313 |
CONVERSION
OF VEA TO VNIC IN NIB CAN RESULT IN 0950-022 |
IJ43314 |
A
potential security issue exists |
IJ43315 |
IN6_IS_ADDR_V4COMPAT
returning wrong result |
IJ43318 |
renamed
cmvtscsi didnt restore, |
IJ43319 |
Crash
observed while HTX and OFED test |
IJ43323 |
Add more
netstat options to snap tcpip data collection |
IJ43350 |
SYSTEM
CRASH WHEN USNIG ISO IMAGE MOUNTED WITH LOOPMOUNT CDRFS |
IJ43351 |
SORT
0653-650 CANNOT LOCATE THE TEMPORARY DIRECTORY OR /TMP |
IJ43352 |
restore
may not extract file archived by file system |
IJ43353 |
EMGR_CHECK_IFIXES
SCRIPT HAS WRONG FLRT_HOST AND DOWNLOAD FILE |
IJ43354 |
VIOSBR
restore failed after rebooted |
IJ43355 |
udfcreate
not failing for 4K blocksize devices |
IJ43356 |
chvg -g
fails with unclear message when PVs have grown in size |
IJ43358 |
A
potential security issue exists |
IJ43521 |
DBN
failover failing when vio_daemon down but pool, CAA still up |
IJ43522 |
vioservice
fails to query all requested info for partition query |
IJ43523 |
list
partition attribute query may fail |
IJ43526 |
CRASH
IN NFSV4 WITH MALFORMED REPLY |
IJ43532 |
06G To
address single mnt pt limitation |
IJ43533 |
Cache
start taking long time in scalable environment. |
IJ43535 |
mkvdev
command to map a disk may take more time |
IJ43536 |
incorrect
host_id when lpar number value 0xa-0xf |
IJ43537 |
SYSTEM
MAY CRASH WHEN MANY IO DRIVERS ARE INVOLVED IN IO PATH |
IJ43809 |
secldapclntd
daemon dumping core |
IJ43812 |
VMRM
SRC_START error entries flooding the error log. |
IJ43975 |
LPAR
crashed at facility_enable() during LPM |
IJ43979 |
SYSTEM
CRASH IN RTFREE_NOLOCK |
IJ44137 |
LPM
failed in 26th loop with HSCLA319 error |