IBM Support

LI81677: UNDER CERTAIN CIRCUMSTANCES, USER-DEFINED POLICIES ERRONEOUSLY DO NOT MEET AVAILABILITY CRITERIA DUE TO INVALID PEERING DATA

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a gateway's apic-gw-service stops while in the process of
cleaning up another gateway's stopped apic-gw-service peering
data, the latter's peering data will not be removed. If this
includes user-defined policy data, the remaining gateways may
erroneously conclude that the policies are not in consensus and
will not advertise them to API Manager. In such cases, the
following error message will appear despite all active gateways
having the policies:

[apic-gw-service][error] Preconfigured
policy <POLICY_NAME> <POLICY_VERSION> (sha1: <POLICY_CHECKSUM>)
does not meet availability criteria and cannot be advertised to
the API Manager (event: consensus error).

Local fix

  • The workaround to recover from this error is to trigger a
Dynamic Reregistration and Reconfiguration (DRR) for the
affected gateway service.

Problem summary

  • In a cluster of API Gateways with preconfigured user-defined
policies, if multiple gateways' API Connect Gateway Services are
stopped (e.g., due to crashes or deliberately disabling the
service) within a narrow timing window, some erroneous peering
data could cause the cluster incorrectly conclude that certain
policies do not have consensus among the cluster.

Problem conclusion

  • Fix is targeted for version 10.0.1.1 and 2018.4.1.15

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    LI81677
    • 

  • Reported component name
    API CONNECT ENT
    • 

  • Reported component ID
    5725Z2201
    • 

  • Reported release
    18X
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2020-08-19
    • 

  • Closed date
    2020-12-10
    • 

  • Last modified date
    2020-12-10
    • 





    

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

    • 

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

    
IT34084
    

    • 



Fix information


    

  • Fixed component name
    API CONNECT ENT
    • 

  • Fixed component ID
    5725Z2201
    • 



Applicable component levels


    








      
              
                            

              

              [{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X"}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            11 December 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback