IBM Tivoli Monitoring: VIOS Premium Agent 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004

Downloadable files


Abstract

This is a cumulative interim fix for IBM Tivoli Monitoring: VIOS Premium Agent v6.2.2 Interim Feature 2.

Download Description

Copyright International Business Machines Corporation 2012.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: VIOS Premium Agent,
Version 6.2.2.2

Component ID: 5724C04VP

Interim Fix 0004, 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004

Date: December 6, 2012

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
---------------
APAR: IV28629
Abstract: PERFORMANCE IMPROVEMENT FOR LOGICAL VOLUME DATA
Additional information: The collection of logical volume data
might take longer than necessary. The time delay
increases as the number of disks increases.

APAR: IV29791
Abstract: DATA PROVIDER CORES ON ODM ERROR
Additional information: The aixDataProvider-61 process might core
dump after receiving an Object Database Manager (ODM)
error.
The <hostname>_px_aixDataProvider-61_<timestamp>_01.log
file might have one of these two sets of messages:

------------------------------------
dkstats.c,1928,"get_cu_adptr") Error in get_cu_adptr():
odm_get_list(): CFG_ODM_ACCESS.
dkstats.c,1929,"get_cu_adptr") Error : CFG_ODM_ACCESS.
dkstats.c,1936,"get_cu_adptr") Exit: 0xFFFFFFFF
dkstats.c,1485,"reset_tbl") Active RAS1 Classes: EVERYT EVERYE
EVERYU
dkstats.c,1485,"reset_tbl") Entry
------------------------------------

or this message, which might occur on systems that have disks that do
not store information in the ODM:

------------------------------------
CP8: goto loop1
iost_dkcnt: 43, last_dkstat[iost_dkcnt].diskname: [[,
dkstat[iost_dkcnt].diskname: 0<88>^?
======System configuration has changed=========
...
dkstats.c,2658,"updt_adptr_withpaths") Entry
dkstats.c,2679,"updt_adptr_withpaths") Error in
updt_adptr_withpaths():
odm_get_list(): 0519-100 libodm: Cannot open the object class
collection file.
Check path name and permissions.
------------------------------------

The core dump generates the following stack trace:

reset_tbl() at 0x10021808
resetclean() at 0x1002198c
reset() at 0x1002ad0c
get_diskstats() at 0x1003207c
adp_get_diskstats(0x2ff21804) at 0x10006ec0
dt_CollectDiskData(0x309e94b0, 0x308e1d48) at 0x100388a8
dt_CollectData(0x309e94b0, 0x308e1d48) at 0x1003d134
itmTranslator(0x0) at 0x1003debc
main(0x1, 0x2ff21b5c) at 0x100077d0

APAR: IV29796
Abstract: DATA PROVIDER CORES ON DKSTATS HEAP CORRUPTION
Additional information: The aixDataProvider-61 process might core
dump due to heap corruption when collecting disk data.
Due to the random nature of the heap corrpution, the
stack trace can vary, but some examples as seen in
errpt -a output are:

---
reallocat 9B0
get_disks 88C
adp_get_d 104
dt_Collec 10C
dt_Collec 298
itmTransl A40
main 434
__start 6C
---

---
get_disks 6C8
adp_get_d 104
dt_Collec 10C
dt_Collec 298
itmTransl A40
main 434
__start 6C
---

---
free_y 1C
free_comm B4
reset_fre 50
reset 14
get_disks D3C
adp_get_d 104
dt_Collec 10C
dt_Collec 298
itmTransl A40
main 434
---

---
calloc_co 70
allocate_ 548
get_disks 71C
adp_get_d 104
dt_Collec 10C
dt_Collec 298
itmTransl A40
main 434
__start 6C
---

---
rightmost C
free_y 654
free_comm B4
dt_Collec F44
dt_Collec 298
itmTransl A40
main 434
__start 6C
---

---
_cleanup_ 1C
pthread_c 2C
pthread_c 2C
odm_get_l 2FC
get_cpu_s 148
adp_get_c F0
dt_Collec 600
dt_Collec 1D0
itmTransl A40
main 434
---

APAR: IV32731
Abstract: DATA PROVIDER CORE ON VIOS 2.2.2.X AND AIX 6.1 TL8
Additional information: The aixDataProvider-61 process might core
on AIX 6.1 TL8, which is the underlying AIX for VIOS
2.2.2.x. The agent might display incorrect and
sometimes negative values in the CPU Details Per Process
view of the CPU Information workspace. The core might
occur when collecting data for the "CPU Details"
attribute group. The core dump stack might not be
consistent, but one example is:
---
realloc_y(??, ??, ??) at 0xd0126f00
realloc_common(??, ??) at 0xd0111bf4
reserve__Q2_3KQZ6StringFi(0x30b53180, 0x10e0) at 0x10047b5c
cp_SetAttributeValues(0x2ff21978, 0x20, 0x30b7efb8) at
0x10043d88
dt_SetAttrValues(0x2ff21978, 0x20, 0x30b7efb8) at 0x10038dec
dt_CollectCPUDetailData(0x308ccdd0, 0x30b7efb8) at 0x1003d7dc
dt_CollectData(0x308ccdd0, 0x30b7efb8) at 0x10040aac
itmTranslator(0x0) at 0x100418fc
main(0x1, 0x2ff21d5c) at 0x10007f58
---

2.2 Defects
---------------
Defect: 195854
Abstract: DEV: No mapping data if CEC name has a space
Additional information: If the CEC name contains a space character,
no data will be reported for "NPIV Mappings" and
"Storage Mappings" attribute groups.


2.3 Enhancements
------------------
None.

2.4 Superseded fixes
---------------------
6.2.2.2-TIV-ITM_VIOS_PREM-IF0003
6.2.2.2-TIV-ITM_VIOS_PREM-IF0002
6.2.2.2-TIV-ITM_VIOS_PREM-IF0001

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.2.2.2-TIV-ITM_VIOS_PREM-IF0003
----------------------------------
APAR: IV13745
Abstract: THE AIXDATAPROVIDER-61 PROCESS CORE DUMPS ON PROCESS WITH 511
CHARACTERS
Additional information: When viewing the Top Resources workspace,
the aixDataProvider process might core. This occurs if
there is a process and argument list whose total number of
characters is exactly 511 characters, above or below 511 will
not cause this problem.
The stack trace is as follows:
---
rightmost C
free_y 798
free_comm B4
BSS1_EndF 54
RAS1_Form 5C
RAS1_Even 170
dt_SetAtt 9C
dt_Collec 308
dt_Collec 16C
itmTransl 9D8
main 320
__start 6C
---

APAR: IV14496
Abstract: AIXDATAPROVIDER-61 CORE DUMP
Additional information: The aixDataProvider-61 might core with the
following stack trace when there is insufficient memory
on the system:
---
.() at 0xe060
itmTranslator(0x0) at 0x1003bc4c
main(0x1, 0x2ff21b78) at 0x1000781c
---

APAR: IV15383
Abstract: DELTA VALUES INCORRECTLY CALCULATED WHEN USING SCALE
Additional information: When using a Scale adjustment value, the
delta calculations are not calculated correctly. If
the attribute has no scale, the delta calculations are
correct. The resulting value may appear as -0.01 or
appear to be a random number. This APAR is required to
avoid problems with the enhancement described in the
2.3 Enhancements section below (defect 180676).

APAR: IV15774
Abstract: CORE DUMP AT CP_WAITFORREQUEST
Additional information: The aixDataProvider-61 process might core
with the following stack trace:
---
malloc_y 69C
malloc_y 6D4
malloc_co 2C
malloc D4
strdup@AF 20
cp_WaitFo 388
itmTransl 5C8
main 3B4
__start 6C
---

APAR: IV16625
Abstract: ENTITLEMENT CONSUMED PERCENT SHOWS ABNORMALLY HIGH VALUES
(200% AND ABOVE)
Additional information: In the LPAR Utilization view of the System
-- LPAR Information workspace, the "Entitlement Used Pct"
might display an incorrectly high value, sometimes over
200 percent.

APAR: IV18015
Abstract: AIXDATAPROVIDER-61 CORE DUMP WHEN DYNAMICALLY CHANGING THE
NUMBER OF TARGET DISKS
Additional information: The aixDataProvider-61 process might core
due to overbound memory access when the number of target
disks is dynamically changed. As a result, the Storage
Devices Utilization workspace does not display data in
the name field. The core dump stack trace might be any
of the following:
---
noname.strcpy() at 0x10007a84
get_diskstats(), line 626 in "dkStats.c"
adp_get_diskstats(vals = 0x2ff215c4), line 1364 in "aixDataProvider.c"
dt_CollectDiskData(ag = 0x304c5930, id = "93056"), line 1932 in
"aixTranslator.c"
dt_CollectData(ag = 0x304c5930, id = "93056"), line 1121 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
itmTranslator(arg = (nil)), line 842 in "aixTranslator.c"
main(argc = 1, argv = 0x2ff21c0c), line 1503 in "aixDataProvider.c"
---
malloc_y(0x3200, 0x0, 0xf07273a8, 0xf06bd098, 0x0, 0x10e6004b,
0x10e6004b, 0x30648f50) at 0xd01402b0
malloc_common@AF103_86(??) at 0xd012a448
malloc(??) at 0xd012a1f0
calloc_common(??, ??) at 0xd01298fc
dt_CollectSpmiData(ag = 0x302fb168, id = "93339"), line 1364 in
"aixTranslator.c"
dt_CollectData(ag = 0x302fb168, id = "93339"), line 1109 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
itmTranslator(arg = (nil)), line 842 in "aixTranslator.c"
main(argc = 1, argv = 0x2ff21cf4), line 1503 in "aixDataProvider.c"
---
noname.strcpy() at 0x10007a84
get_diskstats(), line 626 in "dkStats.c"
adp_get_diskstats(vals = 0x2ff215c4), line 1364 in
"aixDataProvider.c"
dt_CollectDiskData(ag = 0x30554960, id = "60518"), line 1932 in
"aixTranslator.c"
dt_CollectData(ag = 0x30554960, id = "60518"), line 1121 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), line 842 in
"aixTranslator.c"
itmTranslator(arg = (nil)), line 842 in "aixTranslator.c"
main(argc = 1, argv = 0x2ff21c0c), line 1503 in "aixDataProvider.c"
---

APAR: IV18081
Abstract: INCORRECT VALUE FOR THE ATTRIBUTE 'NUMBER OF HYPERVISOR
CALLS PER SEC' IN THE LOGICAL PARTITION VIEW.
Additional information: In the Logical Partition view of the System
-- LPAR Information workspace, the attribute "Number of
Hypervisor Calls Per Sec" shows the total number of calls
instead of the number of calls per second.

APAR: IV18372
Abstract: THE PHYSICAL CPU CONSUMPTION SHOWN BY THE LOGICAL
PARTITION AND CPU SUMMARY ARE DIFFERENT VALUES.
Additional information: If the same metric is collected in two
different attribute groups in less than 60 seconds, then
the values might be different and sometimes abnormally
high. This can affect the common metrics in the
"Logical Partition" attribute group and the "CPU Summary"
attribute group.

APAR: IV18613
Abstract: AIXDATAPROVIDER CORE DUMP WHILE COLLECTING DISK DATA
Additional information: While collecting disk data, the
aixDataProvider might core dump with the following trace
stack.

-----------------------------
rightmost(??, ??) at 0xd013dbec
free_y(??, ??) at 0xd013ed24
free_common(??) at 0xd0129a30
dt_CollectDiskData(ag = 0x3063b2e0, id = "306"), in "aixTranslator.c"
dt_CollectData(ag = 0x3063b2e0, id = "306"), in "aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), in "aixTranslator.c"
unnamed block in itmTranslator(arg = (nil)), in "aixTranslator.c"
itmTranslator(arg = (nil)), in "aixTranslator.c"
main(argc = 1, argv = 0x2ff21d3c), in "aixDataProvider.c"
-----------------------------

APAR: IV20342
Abstract: DATA PROVIDER EXITS WITH MALLOC FAILED MESSAGE
Additional information: The aixDataProvider-61 process exits due
to a malloc failure, and no data displays in the Tivoli
Enterprise Portal for this agent. The
<hostname>_va_aixDataProvider-61_<timestamp>_01.log will
have a the following message:
----------------------------------
aixtranslator.c,750,"itmTranslator") malloc failed..
----------------------------------

APAR: IV23091
Abstract: FIBRE CHANNEL ADAPTER STATISTICS INCORRECT
Additional information: In the Fibre Channel Statistics view of the
Storage--Fibre Channel workspace, the Input Bytes per
Second and Output Bytes per Second columns have incorrect
data, which is usually wrong by a factor of 10.

Defect: 182996
Abstract: aixDataProvider-61 hangs with no data
Additional information: The aixDataProvider-61 process might hang with
the following procstack:
---
---------- tid# 35782701 (pthread ID: 1) ----------
0xd04f974c _global_lock_common(??, ??, ??) + 0x48c
0xd0506f0c _mutex_lock(??, ??, ??) + 0x2ec
0xd12cd000 BSS1_GetLock(0x30877da8) + 0x68
0xd12de5d0 KBBRAFH(0x308843e8, 0x30cca680, 0x1) + 0xd0
0xd12d11a4 KBBSS_FlushBuffer(0x30cca658, 0x1) + 0xcc
0xd12da844 BSS1_EndFormat(0x30cca658) + 0x24
0xd12d1dd8 RAS1_Format(0x300020c8, 0x1ee, 0xd131b6e8, 0x2ff208b4) + 0x58
0xd12da27c RAS1_Event(0x300020c8, 0x1ee, 0x4, 0x14, 0x14, 0x2ff208f0, 0x1222002d, 0x30018f40) + 0x16c
0xd12d1c88 RAS1_Sync(0x300020c8) + 0x73c
0x10004c3c slice(0xe) + 0x5c
<signal>
0xd011fe04 write(??, ??, ??) + 0x1a4
0xd011dd4c _xwrite(??, ??, ??, ??) + 0x6c
0xd011dbe8 _xflsbuf(??) + 0xa8
0xd011d140 fflush_unlocked(??) + 0x780
0xd011e29c fflush(??) + 0x7c
0xd12de8ec KBBRAFH(0x30bb2078, 0x30cca303, 0x2) + 0x3ec
0xd12d11a4 KBBSS_FlushBuffer(0x30cca248, 0x1) + 0xcc
0xd12da844 BSS1_EndFormat(0x30cca248) + 0x24
0xd12d1dd8 RAS1_Format(0x30002050, 0x318, 0x3000271c, 0x2ff213c4) + 0x58
0xd12d1d3c RAS1_Printf(0x30002050, 0x318, 0x3000271c, 0x14, 0x2ff214b8, 0xa, 0xa, 0xf06cef1c) + 0x44
0x100014d8 start_script_feeds(0x5) + 0xcb8
0x10004178 execute_script(0x5, 0x2ff216d4, 0x2ff21694) + 0x158
0x10038798 dt_CollectScriptData(0x309cb600, 0x30b4d768) + 0xd8
0x1003d2f8 dt_CollectData(0x309cb600, 0x30b4d768) + 0x2f8
0x1003e01c itmTranslator(0x0) + 0xa3c
0x100079b0 main(0x1, 0x2ff219cc) + 0x430
0x10000168 __start() + 0x68
---------- tid# 16056475 (pthread ID: 406) ----------
0xd04f974c _global_lock_common(??, ??, ??) + 0x48c
0xd0506f0c _mutex_lock(??, ??, ??) + 0x2ec
0xd12cd000 BSS1_GetLock(0x30877da8) + 0x68
0xd12de5d0 KBBRAFH(0x30b4d548, 0x30ccaa90, 0x1) + 0xd0
0xd12d11a4 KBBSS_FlushBuffer(0x30ccaa68, 0x1) + 0xcc
0xd12da844 BSS1_EndFormat(0x30ccaa68) + 0x24
0xd12d1dd8 RAS1_Format(0x30001f38, 0x205, 0xd131b6b0, 0x30f47a54) + 0x58
0xd12da27c RAS1_Event(0x30001f38, 0x205, 0x0, 0xd0525000, 0x0, 0x10f5009b, 0x10f5009b, 0x0) + 0x16c
0x10005dac goScript(0x5) + 0xac
0xd04fad84 _pthread_body(??) + 0xe4
---
Data might not be displayed on the Tivoli Enterprise
Portal. If KBB_RAS1 is set to all, the last lines
in the <hostname>_va_aixDataProvider-61_<timestamp>_xx.log
might be similar to:
---
(4FB5B198.0016-1:aixdataprovider.c,408,"execute_script") Entry
(4FB5B198.0017-1:aixdataprovider.c,415,"execute_script")
+4FB5B198.0017
+4FB5B198.0017 execute_script: Time Thu May 17 22:19:04 2012 key<5>
(4FB5B198.0018-1:aixdataprovider.c,643,"start_script_feeds") Entry
(4FB5B198.0019-1:aixdataprovider.c,651,"start_script_feeds") TPT1 start_script_feed time = Thu May 17 22:19:04 2012 key =5
(4FB5B198.001A-1:aixdataprovider.c,654,"start_script_feeds") start_script_feeds: script = </opt/IBM/ITM/aix523/px/bin/aixDataProvider.pl Network_Adapters_Rates>
(4FB5B198.001B-1:aixdataprovider.c,675,"start_script_feeds") deltaTime = 80 delta_hmcTime = 1337307544, rwlock=0
(4FB5B198.001C-1:aixdataprovider.c,706,"start_script_feeds") TPT3 start_script_feed: key = 5 Script Active = 0 at Thu May 17 22:19:04 2012
(4FB5B198.001D-1:aixdataprovider.c,722,"start_script_feeds") start_script_feeds(): Acquired read lock in 0 attempts
(4FB5B198.001E-1:aixdataprovider.c,746,"start_script_feeds") TPT4 start_script_feed: Calling pthread_create Thu May 17 22:19:04 2012
(4FB5B198.001F-1:aixdataprovider.c,777,"start_script_feeds") Set scripts[5]->active to TRUE
(4FB5B198.0020-1:aixdataprovider.c,778,"start_script_feeds") start_script_feeds(): key: 5, got lock in 0 attempts
(4FB5B198.0021-1:aixdataprovider.c,792,"start_script_feeds") TPT5 start_script_feed: Setting Timer for 20 Thu May 17 22:19:04 2012
---

Defect: 182440
Abstract: Memory leak in aixDataProvider-61
Additional Information: The data provider leaks a small amount of
memory when collecting disk data and making ODM calls.

Defect: 183500 (179111)
Abstract: Memory Leak in Take Action Code
Additional Information: Take Action can leak a small amount of
memory in the kphagent process when the task name is
converted from UTF-8 to the local code page. This causes
memory to be allocated which is never freed.

Defect: 183653
Abstract: avgsqsz is 1/2 of the value reported iostat
Additional Information: On LPARs with multiple CPUs, the Service
Queue metric will be incorrect.


6.2.2.2-TIV-ITM_VIOS_PREM-IF0002
------------------------------------
APAR: IV09496
Abstract: THE AIX PREMIUM AGENT SHOWS JUNK VALUES FOR SYSTEM
SOFTWARE VERSION
Additional information: In the System Inventory workspace, the
System Software Version column might display an
incorrect version number, for example: ":5" or "oslevel".

APAR: IV10246
Abstract: DATA PROVIDER EXITS WITHOUT LOGGING MESSAGE TO THE LOG FILE
Additional information: If the aixDataProvider process exits due to
an SPMIinit failure, the data provider does not record a
log message specific for this failure. The
<hostname>_va_kvaagent_<timestamp>_<xx>.log file only has
the following generic message:
----------------------------------
The data provider process pid[56885260] "aixDataProvider" exited
with return code 8
------------------------------------

APAR: IV10612
Abstract: AIXDATAPROVIDER-61 CORE DUMP AT ATTACH_STATS
Additional information: The aixDataProvider process might core
dump with the following stack trace:
---
attach_stats()
vdev_stats()
get_diskstats()
adp_get_diskstats(vals = 0x2ff21724)
dt_CollectDiskData(ag = 0x30395e80, id = "37566")
dt_CollectData(ag = 0x30395e80, id = "37566")
itmTranslator(arg = (nil))
main(argc = 1, argv = 0x2ff21d68)
---

APAR: IV11050
Abstract: PHYSICAL VOLUME DATA INCORRECT IF THE NAME OF ONE PHYSCIAL
VOLUME IS A SUBSET OF ANOTHER. (EG. HDISK1 AND HDISK10)
Additional information: The Storage workspace might display
incorrect Physical Volume details if one physical volume
name is a subset of another, for example: "hdisk1" and
"hdisk10".

APAR: IV12058
Abstract: "PER PROCESS INFORMATION" VIEW SHOWS WRONG VALUES
FOR VOLUNTARY AND INVOLUNTARY CONTEXT SWITCHES PER SECOND.
Additional information: The Per Process Information view of the
Process workspace displays the wrong values for the
attributes "Voluntary Context Switches Per Second" and
"Involuntary Context Switches Per Second".

APAR: IV12272
Abstract: AIXDATAPROVIDER CORE DUMPS AT DT_COLLECTSPMIDATA
Additional information: The aixDataProvider process might core
dump with the following stack trace on a WLM-enabled
system:
---
dt_CollectSpmiData(0x3092eb48, 0x308a5138) at 0x1003a884
dt_CollectData(0x3092eb48, 0x308a5138) at 0x1003bf0c
itmTranslator(0x0) at 0x1003ccf4 main(0x1, 0x2ff21714) at 0x1000783c
---

6.2.2.2-TIV-ITM_VIOS_PREM-IF0001
------------------------------------
APAR: IV03076
Abstract: VIOS AGENT DOESN'T GATHER DISK INFO TIMELY
Additional information: Gathering file system metrics might time
out due to a thread scheduling problem. Situations
that monitor the file system metrics might delay in
reporting conditions such as file system full.

APAR: IV03890
Abstract: LOGICAL PARTITION PHYSICAL CONSUMPTION WILL SHOW THE
PHYSB FOR THAT LPAR
Additional information: The "Physical Consumption" attribute
is incorrect.

APAR: IV04033
Abstract: ERROR IN THE VALUE COLLECTED BY THE AGENT FOR AVG
SERVICE QUEUE SIZE
Additional information: The agent reports incorrect values for
the "Average Service Queue Size" attribute.

APAR: IV04043
Abstract: ERROR IN THE VALUE COLLECTED BY THE AGENT FOR SERVICE
QUEUE FULL/SEC
Additional information: The agent reports incorrect values for
the metric "Service Queue Full per Sec" attribute.

APAR: IV05224
Abstract: ITM SHOWS HIGH BANDWIDTH FOR 10 GIGABIT ETHERNET
Additional information: Stressing a 10 Gigabit ethernet adapter
to its maximum might result in the "Bandwidth
Utilization Percentage" attribute value displaying
greater than 100%.

APAR: IV06885
Abstract: VIOS AGENT TO SHOW PROPER ENTC VALUE FOR ALL CATEGORIES OF
LPARS
Additional information: The "Entitlement Used Pct" attribute
is incorrect for dedicated LPARs.

APAR: IV09281
Abstract: MEMORY LEAK IN DATA PROVIDER
Additional information: The aixDataProvider process allocates
memory without freeing it. The process might grow
by 56 KB per data request, which depends on how often
situation, historical data collection and Tivoli
Enterprise Portal requests are made.

APAR: IV09500
Abstract: DATA PROVIDER CORE DUMP ON VIOS WHEN CONFIGURING WITH NO
HMC USER NAME.
Additional information: The aixDataProvider process might core dump
under the following conditions:
- The VIOS Premium agent is on VIOS 2.2.1 or above.
- When running the "cfgsvc" command to configure the agent,
the managing_system parameter does not include an HMC userid
(that is, only the HMC hostname is provided).
- Starting the agent after the above configuration.
The core entry at the end of the "errpt -a" output is
similar to:
--
COME FROM ADDRESS REGISTER
strncpy 14
PROCESSOR ID
hw_fru_id: 0
hw_cpu_id: 2
ADDITIONAL INFORMATION
strncpy BC
getHMCadd 3EC
--
And the trace back is:
---------------------------
(dbx) where
strncpy() at 0x1001267c
getHMCaddressV6() at 0x1001f09c
gather_hmc_info(0x0) at 0x10025564
---------------------------

APAR: IV10196
Abstract: NETWORK INTERFACE RESOURCE VIEW NOT SHOWS NETWORK INTERFACES
IF THE INTERFACE IS IN DOWN STATE
Additional information: When a network interface is in a down state,
the Network Interface Resources view does not display the
row for the network interface.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: VIOS Premium Agent User's Guide, version 6.2.2.2.

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:

http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

IBM Tivoli Monitoring: VIOS Premium Agent, Version 6.2.2 Interim
Feature 2.

The above release is available in VIOS 2.2.1.0 and associated Fix
Pack 2.2.1.1 (Fix Pack 25). It is also included in VIOS 2.2.2.x.

See the Troubleshooting Wiki for details:

https://www.ibm.com/developerworks/wikis/display/tivolimonitoring/System+P+Agents

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.


4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004.README - This README file
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004.tar - Fix archive .tar format
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004.zip - Fix archive .zip format.

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file if
you are working in a Windows(R) environment.

The fix archive contains the following files:
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004/va_dd_062202004.xml
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004/va_dd.properties
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004/kva_aix523_tema_if0004.tar
- 6.2.2.2-TIV-ITM_VIOS_PREM-IF0004/kvaaix523.dsc


5.0 Installation instructions
==================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems.

Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. As the prime administrator of the Virtual I/O Server, run the
"oem_setup_env" command.

2. Transfer the archive file (6.2.2.2-TIV-ITM_VIOS_PREM-IF0004.tar)
to a temporary directory on the system that contains the
agent code to be updated. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this
directory.

3. Expand the archive file using the "tar" command on UNIX systems.
This step creates a directory structure that contains fixes for
all of the supported platforms.

4. Use the "itmpatch" command to install the fix for the operating
system for that agent. For more information on the "itmpatch"
command, see section 6.2.

On UNIX systems, if the fix was expanded to
<TEMP>/6.2.2.2-TIV-ITM_VIOS_PREM-IF0004, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.2-TIV-ITM_VIOS_PREM-IF0004/kva_aix523_tema_if0004.tar

5.3 Remote agent update
----------------------------
Remote deploy of the IBM Tivoli Monitoring: VIOS agent is not
supported, because the required IBM Tivoli Monitoring: Unix Agent
is not supported on VIOS.

5.4 Agent support update
------------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superseded fixes. No additional installation steps are required.


6.0 Additional installation information
========================

For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax:

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch


For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, this must include the drive
letter.


6.3 Verifying the update
----------------------------

1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t VA

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t VA

Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (VA), not three characters (KVA).

When the agent update is successful, the agent version is now:
06.22.02.04.


7.0 Known problems and workarounds
=========================
None.


8.0 Additional product information
======================
None.


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.

10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Other company, product, or service names may be trademarks or service
marks of others.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.

Prerequisites

IBM Tivoli Monitoring: VIOS Premium Agent, Version 6.2.2 Interim Feature 2

Installation Instructions

Please refer to the README contained in the Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.2.2-TIV-ITM_VIOS_PREM-IF0004 13 Dec 2012 English 5389002 FC

Product Alias/Synonym

VIOS agent
Monitoring Agent for System p
System p Agent

Problems (APARS) fixed
IV03076, IV03890, IV04033, IV04043, IV05224, IV06885, IV09281, IV09496, IV09500, IV10196, IV10246, IV10612, IV11050, IV12058, IV12272, IV13745, IV14496, IV15383, IV15774, IV16625, IV18015, IV18081, IV18372, IV18613, IV20342, IV23091, IV28629, IV29791, IV29796, IV32731

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Monitoring Version 6
ITM Agent System P V6

Software version:

6.2.2.2

Operating system(s):

AIX, AIX 64bit

Reference #:

4033861

Modified date:

2012-12-13

Translate my page

Machine Translation

Content navigation