PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV64677 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
Unable to read from the filesystem which is freezed by following command: chfs -a freeze=<timeout> /<mount point> After issuing the above command on a filesystem, It is suppose to be read only during this time and allow reads. Writes will be blocked and that should be expected behavior. Instead, during the timeout period the filesystem will block for both reads and writes. This problem can be seen only on AIX 7.1 TL03, AIX 6.1 TL09 and above After fix reads should work during freeze.
PTF: U856867
Fileset: bos.mp64.7.1.3.2
APAR: IV64677 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
Unable to read from the filesystem which is freezed by following command: chfs -a freeze=<timeout> /<mount point> After issuing the above command on a filesystem, It is suppose to be read only during this time and allow reads. Writes will be blocked and that should be expected behavior. Instead, during the timeout period the filesystem will block for both reads and writes. This problem can be seen only on AIX 7.1 TL03, AIX 6.1 TL09 and above After fix reads should work during freeze.
PTF: U855416
Fileset: bos.mp64.7.1.3.1
APAR: IV64677 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
Unable to read from the filesystem which is freezed by following command: chfs -a freeze=<timeout> /<mount point> After issuing the above command on a filesystem, It is suppose to be read only during this time and allow reads. Writes will be blocked and that should be expected behavior. Instead, during the timeout period the filesystem will block for both reads and writes. This problem can be seen only on AIX 7.1 TL03, AIX 6.1 TL09 and above After fix reads should work during freeze.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV64526 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
The alt_disk_install (and other file system related
commands) may fail with "File table overflow"
errors. The errors continue until the system
is rebooted or the inode cache is increased:
...
Creating /alt_inst/var file system.
mount: /dev/alt_hd2 on /alt_inst/usr: File table overflow
0505-121 alt_disk_install: Error.
Cleaning up.
Could not load program grep:
Dependent module /usr/lib/libc.a(shr.o)
could not be loaded.
Could not load module /usr/lib/libc.a(shr.o).
System error: File table overflow
This problem may also just cause the system to slow
down, with perfpmr showing the iAlloc kernel function
is taking a lot of CPU time.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV64139 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
System crash when reading from a directory
PTF: U859009
Fileset: devices.common.IBM.scsi.rte.7.1.3.15
APAR: IV63986 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
#cfgmgr -vl hdiskX
Method error (/usr/lib/methods/cfgscsidisk -l hdiskX ):
0514-091 Device does not have a Copy Relation
Identifier.
PTF: U859042
Fileset: bos.pmapi.pmsvcs.7.1.3.15
APAR: IV63655 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
System crashes with the stack like these: [00023900]abend_trap+000000 () [0010B0C8]xmdbg_error+000088 (??, ??, ??, ??) [0010A4B8]xmdbg_do_xmfree_record+0005F8 (F1000A020374A100, F1000A01C0000000, F1000A01C00C0D20, 0000436000004360, F0000000300193C0) [0010C914]xmfree+000354 (??, ??) [0610CD0C]pm_get_process_data+00032C (??, ??, ??, ??, ??, ??, ??) [00003934]mfspurr_sc_flih01+000170 () [kdb_get_virtual_memory] no real storage @ FFFFFFFFFFFF2C0 [9000000008B64F4]09000000008B64F4 () [kdb_read_mem] no real storage @ FFFFFFFFFFF8F80 pvthread+00BB00 STACK: [0612BAC4]pm_cb_get_process_data@AF135_13+000164 (0000000000000000, 00000000000000C0, 0000000000000002, 00000000000000B8, 0000000000000000, F1000100E2EAB058 [??]) [000F8488]pm_serialize_update_context@AF113_5+0000A8 (??, ??, ??, ??) [00014F50].kernel_add_gate_cstack+000030 () [06123E18]pm_get_process_data+000278 (??, ??, ??, ??, ??, ??, ??) [00003938]mfspurr_sc_flih01+000174 () [kdb_get_virtual_memory] no real storage @ FFFFFFFFFFFF200 [9000000008BDDF4]09000000008BDDF4 () [kdb_read_mem] no real storage @ FFFFFFFFFFF8F80
PTF: U854682
Fileset: bos.pmapi.pmsvcs.7.1.3.0
APAR: IV63655 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
System crashes with the stack like these: [00023900]abend_trap+000000 () [0010B0C8]xmdbg_error+000088 (??, ??, ??, ??) [0010A4B8]xmdbg_do_xmfree_record+0005F8 (F1000A020374A100, F1000A01C0000000, F1000A01C00C0D20, 0000436000004360, F0000000300193C0) [0010C914]xmfree+000354 (??, ??) [0610CD0C]pm_get_process_data+00032C (??, ??, ??, ??, ??, ??, ??) [00003934]mfspurr_sc_flih01+000170 () [kdb_get_virtual_memory] no real storage @ FFFFFFFFFFFF2C0 [9000000008B64F4]09000000008B64F4 () [kdb_read_mem] no real storage @ FFFFFFFFFFF8F80 pvthread+00BB00 STACK: [0612BAC4]pm_cb_get_process_data@AF135_13+000164 (0000000000000000, 00000000000000C0, 0000000000000002, 00000000000000B8, 0000000000000000, F1000100E2EAB058 [??]) [000F8488]pm_serialize_update_context@AF113_5+0000A8 (??, ??, ??, ??) [00014F50].kernel_add_gate_cstack+000030 () [06123E18]pm_get_process_data+000278 (??, ??, ??, ??, ??, ??, ??) [00003938]mfspurr_sc_flih01+000174 () [kdb_get_virtual_memory] no real storage @ FFFFFFFFFFFF200 [9000000008BDDF4]09000000008BDDF4 () [kdb_read_mem] no real storage @ FFFFFFFFFFF8F80
PTF: U858980
Fileset: bos.rte.libc.7.1.3.15
APAR: IV63606 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
getconf DISK_SIZE shows wrong disk size for large disks such as 10TB , for example: # getconf DISK_SIZE /dev/hdiskxx 1048576 while the correct output should be 10485760
PTF: U858977
Fileset: bos.adt.prof.7.1.3.15
APAR: IV63606 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
getconf DISK_SIZE shows wrong disk size for large disks such as 10TB , for example: # getconf DISK_SIZE /dev/hdiskxx 1048576 while the correct output should be 10485760
PTF: U859827
Fileset: bos.rte.printers.7.1.3.15
APAR: IV63587 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
In 7.1 TL3, you may experience corruption of /etc/qconfig when adding or removing print queues, especiall on a more active system with several print queues defined and printers.
PTF: U859717
Fileset: printers.rte.7.1.3.15
APAR: IV63587 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
In 7.1 TL3, you may experience corruption of /etc/qconfig when adding or removing print queues, especiall on a more active system with several print queues defined and printers.
PTF: U860801
Fileset: devices.chrp.base.diag.7.1.3.16
APAR: IV63381 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
Diagnostics fails to identify SAS devices in certain SES.
PTF: U854767
Fileset: devices.chrp.base.diag.7.1.3.0
APAR: IV63381 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
Diagnostics fails to identify SAS devices in certain SES.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV63379 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
System crash with following stack trace CPU 5 CSA F00000002FF47600 at time of crash, error code for LEDs: 70000000 pvthread+01A300 STACK: 00009958 .simple_unlock_mem+000040 () 004730FC aha_thread_queue+0000DC (??) 00472FE0 aha_queue+000020 () 003C2AD8 procentry+000038 (??, ??, ??, ??) kdb_read_mem no real storage @ FFFFFFFFFFF61A0
PTF: U859460
Fileset: bos.aixpert.cmds.7.1.3.15
APAR: IV63187 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
When applying the "hls_ipsecpermit" (included in the High Security Level) and the HMC IP address is found, aixpert should allow all communications to/from HMC only, but due to an invalid filter mask, it let other IP source address full access to any opened port on VIOS.
PTF: U854787
Fileset: bos.aixpert.cmds.7.1.3.0
APAR: IV63187 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
When applying the "hls_ipsecpermit" (included in the High Security Level) and the HMC IP address is found, aixpert should allow all communications to/from HMC only, but due to an invalid filter mask, it let other IP source address full access to any opened port on VIOS.
PTF: U859733
Fileset: bos.rte.shell.7.1.3.15
APAR: IV62912 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U859729
Fileset: bos.64bit.7.1.3.15
APAR: IV62912 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U858983
Fileset: bos.rte.control.7.1.3.15
APAR: IV62912 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U858980
Fileset: bos.rte.libc.7.1.3.15
APAR: IV62912 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U858977
Fileset: bos.adt.prof.7.1.3.15
APAR: IV62912 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U854784
Fileset: bos.rte.control.7.1.3.0
APAR: IV62912 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U854724
Fileset: bos.rte.shell.7.1.3.0
APAR: IV62912 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U854706
Fileset: bos.64bit.7.1.3.0
APAR: IV62912 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U853796
Fileset: bos.adt.prof.7.1.3.0
APAR: IV62912 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U853776
Fileset: bos.rte.libc.7.1.3.0
APAR: IV62912 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fopen tries to open file in incorrect mode due to reading the type argument beyond the string boundaries.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV62820 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U859900
Fileset: bos.adt.include.7.1.3.2
APAR: IV62820 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U859042
Fileset: bos.pmapi.pmsvcs.7.1.3.15
APAR: IV62820 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U859031
Fileset: bos.adt.include.7.1.3.15
APAR: IV62820 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U856867
Fileset: bos.mp64.7.1.3.2
APAR: IV62820 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U856850
Fileset: bos.adt.include.7.1.3.1
APAR: IV62820 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U855416
Fileset: bos.mp64.7.1.3.1
APAR: IV62820 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U854682
Fileset: bos.pmapi.pmsvcs.7.1.3.0
APAR: IV62820 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
May cause application data corruption and core dumps when using vector operations inside of a transaction. This can only occur on Power8 systems running in Power8 mode.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV62605 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
Running 'ls | more' and doing Ctrl+C is not killing process with name 'more'.
PTF: U860797
Fileset: bos.net.tcp.client.7.1.3.16
APAR: IV62443 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
The system crashes with a stack trace similar to pvthread+090000 STACK: [046B9938]udp_input0+001178 (0000000000000000, FFFFFFFFFFFFFFE4,000000000000001C, 0000000000000000 [??]) [046BB688]udp_input1+000068 (F1000E0001D9C800, 0000001400000014,0000000000000000) [0461C370]ipintr_noqueue_post_fw+0008B0 (F1000A038A9013F8, F1000E0001D9C800,F1000815B07389C0) [0461D6C0]ipintr_noqueue+000120 (??, ??, ??) while processing a multicast packet.
PTF: U859901
Fileset: bos.net.tcp.client.7.1.3.2
APAR: IV62443 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
The system crashes with a stack trace similar to pvthread+090000 STACK: [046B9938]udp_input0+001178 (0000000000000000, FFFFFFFFFFFFFFE4,000000000000001C, 0000000000000000 [??]) [046BB688]udp_input1+000068 (F1000E0001D9C800, 0000001400000014,0000000000000000) [0461C370]ipintr_noqueue_post_fw+0008B0 (F1000A038A9013F8, F1000E0001D9C800,F1000815B07389C0) [0461D6C0]ipintr_noqueue+000120 (??, ??, ??) while processing a multicast packet.
PTF: U855417
Fileset: bos.net.tcp.client.7.1.3.1
APAR: IV62443 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
The system crashes with a stack trace similar to pvthread+090000 STACK: [046B9938]udp_input0+001178 (0000000000000000, FFFFFFFFFFFFFFE4,000000000000001C, 0000000000000000 [??]) [046BB688]udp_input1+000068 (F1000E0001D9C800, 0000001400000014,0000000000000000) [0461C370]ipintr_noqueue_post_fw+0008B0 (F1000A038A9013F8, F1000E0001D9C800,F1000815B07389C0) [0461D6C0]ipintr_noqueue+000120 (??, ??, ??) while processing a multicast packet.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV62371 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
#ioo -r -o iodone_distr_disable=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead ioo display it's value as #ioo -o iodone_distr_disable iodone_distr_disable = 0 similarly the tunable vmm_klock_mode: #vmo -r -o vmm_klock_mode=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead vmo display it's value as 0 #vmo -o vmm_klock_mode vmm_klock_mode = 0
PTF: U856867
Fileset: bos.mp64.7.1.3.2
APAR: IV62371 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
#ioo -r -o iodone_distr_disable=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead ioo display it's value as #ioo -o iodone_distr_disable iodone_distr_disable = 0 similarly the tunable vmm_klock_mode: #vmo -r -o vmm_klock_mode=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead vmo display it's value as 0 #vmo -o vmm_klock_mode vmm_klock_mode = 0
PTF: U855416
Fileset: bos.mp64.7.1.3.1
APAR: IV62371 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
#ioo -r -o iodone_distr_disable=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead ioo display it's value as #ioo -o iodone_distr_disable iodone_distr_disable = 0 similarly the tunable vmm_klock_mode: #vmo -r -o vmm_klock_mode=1 after setting the value using above command and after the reboot, it suppose to set the value to 1, instead vmo display it's value as 0 #vmo -o vmm_klock_mode vmm_klock_mode = 0
PTF: U860797
Fileset: bos.net.tcp.client.7.1.3.16
APAR: IV62382 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
AIX does not drop the RST if it is outside the acceptable TCP window. This results in connection closure on aix side resulting in abnormal tcp connection termination. This problem occurs if APAR IV42131 is installed and ONLY if the firewall resets the connection.
PTF: U859901
Fileset: bos.net.tcp.client.7.1.3.2
APAR: IV62382 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
AIX does not drop the RST if it is outside the acceptable TCP window. This results in connection closure on aix side resulting in abnormal tcp connection termination. This problem occurs if APAR IV42131 is installed and ONLY if the firewall resets the connection.
PTF: U855417
Fileset: bos.net.tcp.client.7.1.3.1
APAR: IV62382 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
AIX does not drop the RST if it is outside the acceptable TCP window. This results in connection closure on aix side resulting in abnormal tcp connection termination. This problem occurs if APAR IV42131 is installed and ONLY if the firewall resets the connection.
PTF: U858999
Fileset: bos.sysmgt.nim.client.7.1.3.15
APAR: IV62199 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
When performing a nimadm operation on a nimsh client, the following error may occur during initialization: Initializing the NIM master. Initializing NIM client <client_hostname>. <client_hostname>: Connection refused 0505-159 nimadm: WARNING, unexpected result from remote command to <client_hostname>. 0505-153 nimadm: Unable to execute remote client commands. Cleaning up alt_disk_migration on the NIM master. The problem is caused when there is a client defined on the NIM master that has an invalid if1 attribute. The invalid client definition could be for any client defined on the NIM master. Usually this will take the form of an invalid hostname, which is the second field in the if1 attribute. For example: # lsnim -a if1 kintarobso kintarobso: if1 = <network> <hostname> <MAC address> 0
PTF: U858995
Fileset: bos.sysmgt.nim.spot.7.1.3.15
APAR: IV62199 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
When performing a nimadm operation on a nimsh client, the following error may occur during initialization: Initializing the NIM master. Initializing NIM client <client_hostname>. <client_hostname>: Connection refused 0505-159 nimadm: WARNING, unexpected result from remote command to <client_hostname>. 0505-153 nimadm: Unable to execute remote client commands. Cleaning up alt_disk_migration on the NIM master. The problem is caused when there is a client defined on the NIM master that has an invalid if1 attribute. The invalid client definition could be for any client defined on the NIM master. Usually this will take the form of an invalid hostname, which is the second field in the if1 attribute. For example: # lsnim -a if1 kintarobso kintarobso: if1 = <network> <hostname> <MAC address> 0
PTF: U859038
Fileset: bos.sysmgt.quota.7.1.3.15
APAR: IV62156 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
Shows wrong grace period
PTF: U859454
Fileset: bos.rte.commands.7.1.3.15
APAR: IV62042 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
The mv command uses a fixed 128k transfer buffer even if the filesystem uses a larger then 128k blocksize. This results into slower file moves of large files on non JFS2 filesystems which utilize a blocksize larger then 128k.
PTF: U839033
Fileset: bos.rte.commands.7.1.3.0
APAR: IV62042 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
The mv command uses a fixed 128k transfer buffer even if the filesystem uses a larger then 128k blocksize. This results into slower file moves of large files on non JFS2 filesystems which utilize a blocksize larger then 128k.
PTF: U860793
Fileset: bos.mp64.7.1.3.16
APAR: IV61487 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
System will generate a fault
PTF: U856867
Fileset: bos.mp64.7.1.3.2
APAR: IV61487 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
System will generate a fault
PTF: U855416
Fileset: bos.mp64.7.1.3.1
APAR: IV61487 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
System will generate a fault
PTF: U859462
Fileset: bos.adt.base.7.1.3.15
APAR: IV61235 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
If the input to the assembler is the single instruction, "sync", the assembler core dumps
PTF: U853784
Fileset: bos.adt.base.7.1.3.0
APAR: IV61235 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
If the input to the assembler is the single instruction, "sync", the assembler core dumps
PTF: U858997
Fileset: perfagent.tools.7.1.3.15
APAR: IV61116 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
topas -C reports shared partitions as dedicated partitions & all the data is zero
PTF: U852813
Fileset: perfagent.tools.7.1.3.0
APAR: IV61116 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
topas -C reports shared partitions as dedicated partitions & all the data is zero
PTF: U859721
Fileset: bos.perf.libperfstat.7.1.3.15
APAR: IV61054 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
rmdev -Rdl <fcadapter> fails when removing an unused
port.
When customer tried to remove the adapter command returns
a busy status though the adapter is not used.
# rmdev -Rdl fcs1
fcnet1 deleted
sfwcomm1 deleted
Method error (/usr/lib/methods/ucfgdevice):
0514-062 Cannot perform the requested function
because the
specified device is busy.
(1) root @ moon9: 7.1.0.0: /
# rmdev -Rdl fscsi1
Method error (/usr/lib/methods/ucfgdevice):
0514-062 Cannot perform the requested function
because the
specified device is busy.
PTF: U854703
Fileset: bos.perf.libperfstat.7.1.3.0
APAR: IV61054 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
rmdev -Rdl <fcadapter> fails when removing an unused
port.
When customer tried to remove the adapter command returns
a busy status though the adapter is not used.
# rmdev -Rdl fcs1
fcnet1 deleted
sfwcomm1 deleted
Method error (/usr/lib/methods/ucfgdevice):
0514-062 Cannot perform the requested function
because the
specified device is busy.
(1) root @ moon9: 7.1.0.0: /
# rmdev -Rdl fscsi1
Method error (/usr/lib/methods/ucfgdevice):
0514-062 Cannot perform the requested function
because the
specified device is busy.
PTF: U858988
Fileset: devices.common.IBM.fc.rte.7.1.3.15
APAR: IV61025 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
fcstat from an npiv client always displays seconds since last reset to be 0.
PTF: U854684
Fileset: devices.common.IBM.fc.rte.7.1.3.0
APAR: IV61025 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
fcstat from an npiv client always displays seconds since last reset to be 0.
PTF: U858997
Fileset: perfagent.tools.7.1.3.15
APAR: IV60941 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
topasrec CEC recording stops after few intervals (after an hour and 15 minutes). It typically displays the message "Monitored count consistently zero for 5 iterations. So exiting!" And topas -C reports shared partitions as dedicated partitions & all the data is zero. Topas CEC Monitor Interval: 10 Fri May 9 05:12:09 2014 Partitions Memory (GB) Processors Shr: 16 Mon:37.0 InUse:19.0 Shr: 11 PSz: 26 Don: 0.0 Shr_PhysB 0.08 Ded: 28 Avl: - Ded: 0 APP: 0.0 Stl: 0.0 Ded_PhysB 0.00 Host OS Mod Mem InU Lp Us Sy Wa Id PhysB Vcsw Ent %EntC PhI pmem -------------------------------------shared-------------- ----------------------- pure8 A71 U-d 0.5 0.5 8 0 0 0 99 0.01 276 0.20 2.9 0 - pure28 A61 U-d 2.0 1.5 8 0 0 0 99 0.01 186 0.20 2.8 0 - pure25 A71 U-d 2.0 1.4 8 0 0 0 99 0.01 188 0.20 2.6 0 - pure14 A71 Ued 2.0 1.3 8 0 0 0 99 0.00 164 0.70 0.7 0 - pure39 A61 U-d 1.0 0.9 8 0 0 0 99 0.00 187 0.20 2.2 0 - pure38 A61 U-d 1.5 0.8 8 0 0 0 99 0.00 179 0.20 2.1 0 - ic38 A61 U-d 2.0 1.5 8 0 0 0 99 0.00 164 1.00 0.4 0 - Host OS Mod Mem InU Lp Us Sy Wa Id PhysB Vcsw %istl %bstl ------------------------------------dedicated------------ ----------------------- pure17 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure9 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure7 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure22 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure19 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure5 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure33 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure13 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure32 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure10 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure26 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure11 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - -
PTF: U852813
Fileset: perfagent.tools.7.1.3.0
APAR: IV60941 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
topasrec CEC recording stops after few intervals (after an hour and 15 minutes). It typically displays the message "Monitored count consistently zero for 5 iterations. So exiting!" And topas -C reports shared partitions as dedicated partitions & all the data is zero. Topas CEC Monitor Interval: 10 Fri May 9 05:12:09 2014 Partitions Memory (GB) Processors Shr: 16 Mon:37.0 InUse:19.0 Shr: 11 PSz: 26 Don: 0.0 Shr_PhysB 0.08 Ded: 28 Avl: - Ded: 0 APP: 0.0 Stl: 0.0 Ded_PhysB 0.00 Host OS Mod Mem InU Lp Us Sy Wa Id PhysB Vcsw Ent %EntC PhI pmem -------------------------------------shared-------------- ----------------------- pure8 A71 U-d 0.5 0.5 8 0 0 0 99 0.01 276 0.20 2.9 0 - pure28 A61 U-d 2.0 1.5 8 0 0 0 99 0.01 186 0.20 2.8 0 - pure25 A71 U-d 2.0 1.4 8 0 0 0 99 0.01 188 0.20 2.6 0 - pure14 A71 Ued 2.0 1.3 8 0 0 0 99 0.00 164 0.70 0.7 0 - pure39 A61 U-d 1.0 0.9 8 0 0 0 99 0.00 187 0.20 2.2 0 - pure38 A61 U-d 1.5 0.8 8 0 0 0 99 0.00 179 0.20 2.1 0 - ic38 A61 U-d 2.0 1.5 8 0 0 0 99 0.00 164 1.00 0.4 0 - Host OS Mod Mem InU Lp Us Sy Wa Id PhysB Vcsw %istl %bstl ------------------------------------dedicated------------ ----------------------- pure17 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure9 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure7 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure22 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure19 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure5 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure33 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure13 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure32 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure10 A71 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure26 A61 -d 0.0 0.0 0 0 0 0 0 0.00 0 - - pure11 A53 -d 0.0 0.0 0 0 0 0 0 0.00 0 - -
PTF: U860797
Fileset: bos.net.tcp.client.7.1.3.16
APAR: IV60776 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
The command "ifconfig enN netmask a.b.c.d alias e.f.g.h" does not add a new alias but modifies an existing entry.
PTF: U859901
Fileset: bos.net.tcp.client.7.1.3.2
APAR: IV60776 reported against fix pack: 7100-03-02-1412
Fix available in fixpack: 7100-03-04-1441
The command "ifconfig enN netmask a.b.c.d alias e.f.g.h" does not add a new alias but modifies an existing entry.
PTF: U855417
Fileset: bos.net.tcp.client.7.1.3.1
APAR: IV60776 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
The command "ifconfig enN netmask a.b.c.d alias e.f.g.h" does not add a new alias but modifies an existing entry.
PTF: U859005
Fileset: bos.rte.lvm.7.1.3.15
APAR: IV59159 reported against fix pack: 7100-03-03-1415
Fix not yet available
When chvg -G is run on a concurrent volume group, it throws the below error entries in errlog. IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION CAD234BE 0220223414 U H LVDD QUORUM LOST, VOLUME GROUP CLOSING F7DDA124 0220223414 U H LVDD PHYSICAL VOLUME DECLARED MISSING
PTF: U853814
Fileset: bos.rte.lvm.7.1.3.0
APAR: IV59159 reported against fix pack: 7100-03
Fix not yet available
When chvg -G is run on a concurrent volume group, it throws the below error entries in errlog. IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION CAD234BE 0220223414 U H LVDD QUORUM LOST, VOLUME GROUP CLOSING F7DDA124 0220223414 U H LVDD PHYSICAL VOLUME DECLARED MISSING
PTF: U860800
Fileset: devices.chrp.pci.rte.7.1.3.16
APAR: IV59156 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
Device can go offline while error should have been recovered
PTF: U859002
Fileset: bos.rte.bosinst.7.1.3.15
APAR: IV60682 reported against fix pack: 7100-03-03-1415
Fix available in fixpack: 7100-03-04-1441
When customer is trying to run multibos setup he gets the following message: # multibos -sXt ... Creating standby BOS logical volume bos_hd5 Creating standby BOS logical volume bos_hd4 Creating standby BOS logical volume bos_hd2 Creating standby BOS logical volume bos_hd9var multibos: 0645-007 ATTENTION: mb_set_lvfstag() returned an unexpected result. multibos: 0565-003 Error creating logical volumes. multibos: 0565-035 Error setting up standby BOS.
PTF: U856969
Fileset: bos.rte.bosinst.7.1.3.0
APAR: IV60682 reported against fix pack: 7100-03
Fix available in fixpack: 7100-03-04-1441
When customer is trying to run multibos setup he gets the following message: # multibos -sXt ... Creating standby BOS logical volume bos_hd5 Creating standby BOS logical volume bos_hd4 Creating standby BOS logical volume bos_hd2 Creating standby BOS logical volume bos_hd9var multibos: 0645-007 ATTENTION: mb_set_lvfstag() returned an unexpected result. multibos: 0565-003 Error creating logical volumes. multibos: 0565-035 Error setting up standby BOS.
