IV31655: UA SNMP EMITTER DOCUMENTATION FOR INSTALL / CONFIGURATION

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Universal Agent SNMP Emitter does not emit TRAP due to Policy /
    Situation configuration issues.
    
    Tivoli Universal Agent User's Guide
      Introduction to the SNMP emitter
        Installing and integrating the SNMP emitter
          Installing the SNMP emitter
    
    Current information:
    ***
    To install the SNMP Emitter, complete the following steps:
    1. Install the Tivoli Universal Agent. The SNMP Emitter feature
    is fully integrated into the Tivoli Universal Agent
    installation, and the SNMP Emitter starts automatically when the
    Tivoli Universal Agent is started.
    2. The SNMP Emitter's catalog file kum.cat must be located in
    your hub Tivoli Enterprise Monitoring Server RKDSCATL directory.
    3. The SNMP Emitter's attribute file kum.atr must be located in
    your hub Tivoli Enterprise Monitoring Server ATTRLIB directory.
    If you have a z/OS-based Tivoli Enterprise Monitoring Server,
    then you need to install the KUMATR and KUMCAT files into your
    RKANDATV PDS.
    4. The SNMP Emitter's ODI file dockum must be located in your
    Tivoli Enterprise Portal Server \cnps or /cq/data directory.
    Note:
    There is no required connection or dependency between the SNMP
    Data Provider and the SNMP Emitter. You can use the SNMP Emitter
    without activating the SNMP Data Provider. In fact, do not start
    the SNMP Data Provider if you are not using any of its features
    because it requires more system overhead than other Tivoliᄅ
    Universal Agent data providers.
    ***
    Recommended clarified text:
    ****
    To install the SNMP Emitter, complete the following steps:
    1. Install the Tivoli Universal Agent. The SNMP Emitter feature
    is fully integrated into the Tivoli Universal Agent
    installation, and the SNMP Emitter starts automatically when the
    Tivoli Universal Agent is started.
    2. The SNMP Emitter's catalog file kum.cat must be located in
    RKDSCATL directory of your hub Tivoli Enterprise Monitoring
    Server. If the Universal Agent is configured to connect to a
    remote Tivoli Enterprise Monitoring Server (RTEMS) the kum.cat
    file mustalso be located in RKDSCATL directory of remote TEMS.
    3. The SNMP Emitter's attribute file kum.atr must be located in
    ATTRLIB directory of your hub Tivoli Enterprise Monitoring
    Server. If the Universal Agent is configured to connect to a
    remote Tivoli Enterprise Monitoring Server (RTEMS) the kum.atr
    file mustalso be located in ATTRLIB directory of remote TEMS.
     For distributed ITM deployments,  installing Universal Agent
    'Application Support' on hub TEMS
           [and remote TEMS, if applicable] will complete above
    described steps 2 and 3.
    
     Note:  If the Universal Agent is connecting to a z/OS-based
    Tivoli Enterprise Monitoring Server, then you need to install
    the KUMATR and KUMCAT files into your RKANDATV PDS. The
    following  steps must be manually performed.
    
                1.  Copy from  IBM\ITM\CNPS\RKDSCATL\kum.cat to
    RKANDATV(KUMCAT)
                    2.  Copy from  IBM\ITM\CNPS\cmsatr\kum.atr to
    RKANDATV(KUMATR)
                    3.  Recycle the TEMS started task on z/OS
    
    4. The SNMP Emitter's ODI file dockum must be located in your
    Tivoli Enterprise Portal Server \cnps or /cq/data directory.
    Installing Universal Agent 'Application Support' on TEPS will
    complete this step.
    ****
    
    Tivoli Universal Agent User's Guide under section:
     'Establishing SNMP emitter parameters'
    
    Current Information:
    ***
    4. Distribute the policy to a managed system that is of the same
    type as the
    managed system to which the policy's situation was distributed.
    For example, if
    the situation was for the Linux OS agent and was distributed to
    one of its
    related managed systems, then the policy needs to also be
    distributed to a
    managed system associated with the Linux OS agent.
    ***
    
    Recommended clarified text:
    ****
    4. Distribute the policy to a managed system that is of the same
    type as the
    managed system to which the policy's situation was distributed.
    For example, if
    the situation was for the Linux OS agent and was distributed to
    one of its
    related managed systems, then the policy needs to also be
    distributed to a
    managed system associated with the Linux OS agent.
    
    If the SNMP Emitter is not sending SNMP trap as expected when a
    policy's situation evaluates to true, review the TEMS logs for
    messages indicating problems with starting / validating the
    policy definition or situation.
    These messages will correspond to the policy NOT having been
    distributed to managed system of same type as the situation.
    ****
    
    Additional Keywords:
    Errors reported on Hub TEMS when situation and policy are not
    distributed to same managed system:
    
    Error: Missing situation <MVS1_MSU_1oalerta_trap>.
    Error: Failed to process situation formula rc <1145>
    error: build <1145>
    
    Errors reported on RTEMS running on z/OS when Universal Agent
    application support has not been configured:
    
    Invalid act type: /SNMP_Event/
    Act SNMP_Event3 has bad type string.
    Pcy <policy_name> rejected due to invalid def.
    

Local fix

Problem summary

  • Universal Agent SNMP Emitter does not emit TRAP due to Policy /
    Situation configuration issues.
    

Problem conclusion

  • The Tivoli Universal Agent User's Guide has been updated and
    will be available when the documentation is next refreshed
    (currently version 6.3).
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV31655

  • Reported component name

    UNIVERSAL AGENT

  • Reported component ID

    5724K1000

  • Reported release

    621

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-08

  • Closed date

    2012-12-03

  • Last modified date

    2013-07-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Universal Agent

Software version:

621

Reference #:

IV31655

Modified date:

2013-07-18

Translate my page

Machine Translation

Content navigation