IBM Support

IV59320: FTO MAY NOT SYNCHRONIZE ACCESS LIST RECORDS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • *************START OF APAR OPEN TEMPLATE *********************
    
    * Please open an apar with the following severity and
    information:     *
    *
           *
    APAR Type:            Field
    Approver Initials:    RB
    Severity:             3
    Reported Release:     623
    Compid:               5724C04MS Tivoli Enterprise Management
    Server
    
    
    PROBLEM DESCRIPTION:
    The MIRROR may not always synchronize an access list
    distribution when the HUB or MIRROR have a group distribution
    and a direct distribution for the same situation to endpoint.
    This can result in either the HUB or the MIRROR having
    distributions that do not exist on the peer. It can also result
    in removed distributions reappearing after FTO failovers.
    
    RECREATE INSTRUCTIONS:
    
    1. Start a HUB, MIRROR and agent
    2. Create situation sit-A
    3. Create a direct distribution from sit-A to the agent
    4. Check the MIRROR with the SQL below and you will see the
    direct distribution.
    5. Create a group. Include sit-A and include the agent in the
    group distribution.
    6. Check the MIRROR again and you will see the distribution
    still exists but the timestamp has changed.
    7. Stop the agent.
    8. Remove the offline agent.
    9. If you check the MIRROR logs, you will find that the request
    to delete the direct distribution was rejects because of the
    timestampin the record.
    10. Running the SQL below continues to show the distribution in
    the access list.
    
    SELECT NODEL, LOCFLAG, LSTDATE,  OBJCLASS,  OBJNAME
    FROM O4SRV.TOBJACCL WHERE  SYSTEM.PARMA("QIBNODE",
    "QOMEGAVIEW", 32) AND
       SYSTEM.PARMA("FILTER","DIRECTDIST",10) AND
       OBJNAME = "sit-A" AND
       OBJCLASS = "5140";
    
    LOCAL FIX:
    Remove the distribution manually using the following SQL:
    
    DELETE FROM O4SRV.TOBJACCL WHERE OBJNAME='sit-A'
        AND NODEL='agent-name';
    
    Submit the SQL to whichever HUB has the unwanted distribution.
    
    ************** END OF APAR OPEN TEMPLATE **********************
    

Local fix

  • Remove the distribution manually using the following SQL:
    
    DELETE FROM O4SRV.TOBJACCL WHERE OBJNAME='sit-A'
        AND NODEL='agent-name';
    
    Submit the SQL to whichever HUB has the unwanted distribution.
    

Problem summary

  • Access List discrepancies between hub monitoring server and
    mirror monitoring server.
    
    
    Contents of the access list table can get out of sync between
    the hub monitoring server and the mirror monitoring server .
    The problem occurs when deleting a endpoint that has direct
    distributions with overlapping group distributions.  This may
    leave orphaned access list records at the mirror monitoring
    server. The orphaned access list records can make their way back
    to the hub monitoring server during fail over operations.  The
    orphaned access list records are typically harmless, though can
    become relevant if the endpoint re-registers.
    

Problem conclusion

  • The product has been modified to remove the access list records
    at the mirror monitoring server when an endpoint is removed and
    overlapping direct distributions and group distributions exist.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0003
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV59320

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-16

  • Closed date

    2014-07-22

  • Last modified date

    2014-08-08

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

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

    OA45675

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R630 PSY

       UP



Document information

More support for: IBM Tivoli Monitoring V6
ITM Tivoli Enterprise Mgmt Server V6

Software version: 623

Reference #: IV59320

Modified date: 08 August 2014