Fixes are available
APAR status
Closed as program error.
Error description
The basic problem is that "itmcmd manage" provides for more function than "itmcmd config -A" with respect to agentless monitors. The GUI path provides for specific SNMP settings for each managed system where the CLI path only provides for these settings at the instance level. In the reported case, the user employed the GUI to create an instance with two managed systems each with their own SNMP community names. After the instance is created, the user employed the CLI to update the configuration for the instance. After using the CLI, the SNMP community names for the managed systems are no longer in the configuration. The same problem occurs for other values such as the SNMP port. The CLI simply does not provide for the user to enter or edit any SNMP settings that are specific to the managed system. Worse, if the settings have been defined by the GUI, the CLI path removes them. Detailed Recreation Procedure: a) Install "Agentless Monitoring for Linux Operating Systems" b) itmcmd manage - select "Agentless Monitoring for Linux Operating Systems" - right click - select "Configure" c) Click "Add Instance" - provide an instance name, click "OK" - define a managed system within the intance, giving its own SNMP port and SNMP community - specify no TEMS connection (not needed) - click "OK" d) cat $CANDLEHOME/config/*_<instance>.cfg - note SNMP port and SNMP community within managed system section e) itmcmd config -A r4 - specify same instance as step c - edit settings == 1/yes - take defaults for everything to "Edit 'Remove System Details' settings"... specify 2/no for that f) cat $CANDLEHOME/config/*_<instance>.cfg - note SNMP port and SNMP community missing from managed system section
Local fix
Problem summary
The "itmcmd manage" provides for more function than "itmcmd config -A" with respect to agentless monitors. The GUI path provides for specific SNMP settings for each managed system where the CLI path only provides for these settings at the instance level. After using the CLI, the SNMP community names for the managed systems are no longer in the configuration. The same problem occurs for other values such as the SNMP port. The CLI simply does not provide the option for the user to enter or edit any SNMP settings that are specific to the managed system. Furthermore, if the settings have been defined by the GUI, the CLI path removes them.
Problem conclusion
It was necessary to implement the function in CLI equivalent to the GUI, the CLI needs to provide for specific SNMP settings for each managed system. We also need to keep those settings defined by the GUI when executing the "itmcmd config -A" command. The fix for this APAR is included in the following maintenance vehicle: | interim fix | 6.2.1-TIV-ITM-FP0003
Temporary fix
Comments
APAR Information
APAR number
IZ57725
Reported component name
OMEG DIST INSTA
Reported component ID
5608A41CI
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-10
Closed date
2010-04-26
Last modified date
2010-07-22
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
OMEG DIST INSTA
Fixed component ID
5608A41CI
Applicable component levels
R621 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 November 2022