APAR status
Closed as program error.
Error description
Custom configurations of Ping and Virtualcenter Sensor are not migrated. All default sensor configuration are removed and recreated during the upgrade process to FP1. But custom sensor configurations have to be migrated when the command migration.sh -sc is called. There is no information how (to which bundle version) configuration com.ibm.cdb.discover.sensor.net.ping_7.6.0 should be migrated. It causes the custom configuration to not be selected in any profile and the database contains custom configurations to sensors which do not exist.
Local fix
Before migrating to FP1 backup discovery profiles in use via api; ./api.sh -u administrator -p collation find --depth 3 "select * from DiscoveryProfile where name=='<name>'" after upgrade, run the above again and compare the results, especially in regards to the 'name' attribute which indicates which sensors are enabled. If the discovery profile points to an old OSGiPluginId you may need to re-create the profile. If a sensor is not running, check the 'type' column in the discovery profile vs the available plugin files in dist/osgi/plugin directory on the discovery server for that sensor. If the profile has the older one, re-create the profile. If the profile has the newer one, re-check the sensor to enable it(or un-check/re-check if already checked).
Problem summary
Custom configurations of Ping and Virtualcenter Sensor are not migrated. All default sensor configuration are removed and recreated during the upgrade process to FP1. But custom sensor configurations have to be migrated when the command migration.sh -sc is called. There is no information how (to which bundle version) configuration com.ibm.cdb.discover.sensor.net.ping_7.6.0 should be migrated. It causes the custom configuration to not be selected in any profile and the database contains custom configurations to sensors which do not exist.
Problem conclusion
The fix for this APAR is contained in the following maintenance packages: | Fix Pack | 7.3.0-TIV-ITADDM-FP0002
Temporary fix
Comments
APAR Information
APAR number
IV72909
Reported component name
APP DEPENDENCY
Reported component ID
5724N5500
Reported release
730
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-30
Closed date
2015-06-23
Last modified date
2015-06-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP DEPENDENCY
Fixed component ID
5724N5500
Applicable component levels
R730 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 June 2015