Forum Discussion

VFB's avatar
VFB
Icon for Cirrus rankCirrus
Jan 04, 2018

Mirrored persistence not showing records on standby device

Hi all. Please take a look at this output and advise if there is anything missing as to why I am not able to see my mirrored persistence on the standby device.

 

ltm virtual vs_https_persist_RD2_rev1 { destination 10.50.0.8%2:https fallback-persistence persistence_test ip-protocol tcp mask 255.255.255.255 mirror enabled persist { cookie_test { default yes } } pool https_persist_RD2 profiles { http { } tcp { } } source 0.0.0.0%2/0 translate-address enabled translate-port enabled vs-index 57 }

 

application delivery
LTM

13 Replies

Sort By
  • VFB's avatar
    VFB
    Icon for Cirrus rankCirrus
    Jan 04, 2018

    Sorry, I don't know how to format the configs so they come out looking like from a terminal session. The how to format button doesn't give me much insight.

     

  • nitass_89166's avatar
    nitass_89166
    Icon for Noctilucent rankNoctilucent
    Jan 04, 2018

    why I am not able to see my mirrored persistence on the standby device.

     

    you mean persistence_test, don't you? if yes, can you post the persistence_test configuration here?

     

    by the way, you know that cookie persistence does not utilize persistence table since the persistent information is already in cookie value, don't you?

     

    • VFB's avatar
      VFB
      Icon for Cirrus rankCirrus
      Jan 05, 2018

      ltm persistence source-addr persistence_test { app-service none defaults-from source_addr hash-algorithm default map-proxies enabled mask none match-across-pools disabled match-across-services disabled match-across-virtuals disabled mirror enabled override-connection-limit disabled timeout 1800 }

       

    • nitass_89166's avatar
      nitass_89166
      Icon for Noctilucent rankNoctilucent
      Jan 05, 2018

      the configuration looks okay to me.

       

      is there anything else you may notice e.g. does persistence mirror work on other virtual servers, other route domains, etc?

       

    • VFB's avatar
      VFB
      Icon for Cirrus rankCirrus
      Jan 05, 2018

      I'm only running 1 RD (0) and running it on 1 VIP. In the primary I see 92, but the secondary I see 32 - as if it's not replicating all of them.

       

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jan 04, 2018

    why I am not able to see my mirrored persistence on the standby device.

     

    you mean persistence_test, don't you? if yes, can you post the persistence_test configuration here?

     

    by the way, you know that cookie persistence does not utilize persistence table since the persistent information is already in cookie value, don't you?

     

    • VFB's avatar
      VFB
      Icon for Cirrus rankCirrus
      Jan 05, 2018

      ltm persistence source-addr persistence_test { app-service none defaults-from source_addr hash-algorithm default map-proxies enabled mask none match-across-pools disabled match-across-services disabled match-across-virtuals disabled mirror enabled override-connection-limit disabled timeout 1800 }

       

    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      Jan 05, 2018

      the configuration looks okay to me.

       

      is there anything else you may notice e.g. does persistence mirror work on other virtual servers, other route domains, etc?

       

    • VFB's avatar
      VFB
      Icon for Cirrus rankCirrus
      Jan 05, 2018

      I'm only running 1 RD (0) and running it on 1 VIP. In the primary I see 92, but the secondary I see 32 - as if it's not replicating all of them.