Hi,

Often, the processing order of the different classes inside a policy map is important. However, when a new class is added, it is placed at the end of the policy map. More severely, if you reload an configuration with the checkpoint rollback command, the classes inside the policy map won't keep their orinal order. The only way to fix the problem is then to remove all classes and to re-enter them using the "insert-before" statement.

My question is:

Why does not the ACE keep the original order when doing a checkpoint rollback ?  Is it a recognized issue in the ACE ?

Thank you

Yves

Here is for example a typical policy map in which the class order is crucial for the site to work :

policy-map type loadbalance http first-match L7_POLICY_ECOM_PROD_HTTP
  description *** Load balancing rule for PROD in http mode ***
  class L7_CLASS_REDIRECT_001
    serverfarm WEB_REDIRECT_001
  class L7_CLASS_REDIRECT_WEB
    serverfarm WEB_REDIRECT_FARM
  class L7_CLASS_ECOM_WEB1
    sticky-serverfarm ECOM_STICKY_WEB1_HTTP
    insert-http X-Forwarded-Proto header-value "%pd"
    insert-http X-Forwarded-For header-value "%is"
  class L7_CLASS_ECOM_WEB2
    sticky-serverfarm ECOM_STICKY_WEB2_HTTP
    insert-http X-Forwarded-For header-value "%is"
    insert-http X-Forwarded-Proto header-value "%pd"
  class L7_CLASS_ECOM_PROD_URL
    sticky-serverfarm ECOM_STICKY_PROD_HTTP
    insert-http X-Forwarded-Proto header-value "%pd"
    insert-http X-Forwarded-For header-value "%is"
  class L7_CLASS_ECOM_PROD_REFERER
    sticky-serverfarm ECOM_STICKY_PROD_HTTP
    insert-http X-Forwarded-Proto header-value "%pd"
    insert-http X-Forwarded-For header-value "%is"
  class L7_CLASS_ECOM_CATCH_ALL
    sticky-serverfarm ECOM_STICKY_WEB2_HTTP
    insert-http X-Forwarded-For header-value "%is"
    insert-http X-Forwarded-Proto header-value "%pd"