Forum Discussion

Cory_Blankenshi's avatar
Cory_Blankenshi
Icon for Altostratus rankAltostratus
Jan 29, 2018

Possible/Known Issues Upgrading BIG-IP From 12.1.2 to 13.1

Hi all,

 

Has anyone had any functional issues going from version 12.1.2 to version 13.1.0.2 after the upgrade? We haven't pushed the update to our production environment and I wanted to know if anyone saw any impact to existing functionality after going to the latest version. I haven't seen any thus far, but I thought I would throw this out to the community and see what experiences people had to date.

 

Thanks!

 

BIG-IP
security

4 Replies

Sort By
  • Stanislas_Piro2's avatar
    Stanislas_Piro2
    Icon for Cumulonimbus rankCumulonimbus
    Jan 29, 2018

    The issue I discovered and is confirmed after reading the release Note is :

     

    688911-1 : LTM Policy GUI incorrectly shows conditions with datagroups

     

    Component: TMOS

     

    Symptoms:

     

    LTM Policy GUI defaults to using datagroups and overrides previous values in a rule when editing a policy rule since datagroups are introduced in the policy rule.

     

    Conditions:

     

    The user is editing a policy rule

     

    Impact:

     

    The previous values used in a rule will be overridden by the datagroup

     

    Workaround:

     

    The user can use TMSH to modify the rule.

     

  • ictjl's avatar
    ictjl
    Icon for Altocumulus rankAltocumulus
    Feb 15, 2018

    We just had to boot back into our 12.1.2 HF2 boot location from the 13.1.0.2 location because of performance problems in our pre-production environment. Could just be something with our environment, but we went from 5 second page load times to 4-8 minute. Booting back into 12.1.2 resolved all issues. I'm guessing it's some new 13.1 default that we need to identify. Still assessing though.

     

    Please post anything you learn from the upgrade.

     

  • Cory_Blankenshi's avatar
    Cory_Blankenshi
    Icon for Altostratus rankAltostratus
    Feb 15, 2018

    When you find the root cause, can you add the resolution to the thread? I'll do the same if we hit the same problem.

     

    Thanks!