Forum Discussion

hewson_36165's avatar
hewson_36165
Icon for Nimbostratus rankNimbostratus
May 16, 2008

Expire certain RAM CACHE objects

Hello all,

 

 

I'm new to F5, actually using BIG-IP LTM with RAM Cache based on virtual server profile, and I would like to know if there is any way to refresh cache content for certain types o full virtual server.

 

 

For example: Can I refresh .css files on RAM Cache when some of our designer team make a change?
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    For 9.4(.2?)+:

    You can view the ramcache entries for an HTTP profile using this command:

    b profile http HTTP_PROFILE_NAME ramcache entry all

    You can delete all ramcache entries for an HTTP profile using:

    b profile http HTTP_PROFILE_NAME ramcache entry all delete

    You can view all ramcache entries for an HTTP profile with .gif in the URI using:

    b profile http HTTP_PROFILE_NAME ramcache entry uri .gif show

    You can delete all ramcache entries for an HTTP profile with .gif in the URI using:

    b profile http HTTP_PROFILE_NAME ramcache entry uri .gif delete

    You can delete all ramcache entries for an HTTP profile with .gif in the URI for a specific host name using:

    b profile http HTTP_PROFILE_NAME ramcache entry uri .gif host example.com show

    For more complete details on the ramcache options, you can run 'b profile http help' from the command line.

    Aaron
  • This syntax is wrong, at least for bigip v9.3.1

     

     

    b profile http PROFILE_NAME ramcache entry all (obviously doesn't remove anything)

     

     

    b profile http PROFILE_NAME ramcache entry all delete (syntax error)

     

     

    b profile http PROFILE_NAME ramcache entry delete all (syntax error)

     

     

    In the output of "b profile http help", I see no reference to a ramcache "delete" or "remove" or "clear" option. Another case of poor documentation, or limited functionality? Or another case of me missing something that's painfully obvious?
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    I think the RAM cache syntax has changed between LTM versions. The CLI guide for 9.3.x should have the relevant commands. Else, you can check the 'b profile http help' output for examples.

     

     

    Aaron
  • Hrm, I'm not sure how "ramcache entry all" would've/should've ever removed anything. Nonetheless...the magical syntax seems to be:

     

     

    b profile http PROFILE_NAME ramcache reset

     

     

    This does not appear to be anywhere in the output of "b profile http help", nor the CLI guide for 9.3 or 9.4, nor - as far as I can determine - anywhere searchable on AskF5.com.
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Hi pawlicja,

     

     

    You're entirely correct--I had quite a few errors in the above post. I edited it so the descriptions reflect the commands for 9.4(.2?) and later. As you state, the show commands wouldn't delete the RAM cache entries. And you can leave off the 'show' flag when displaying the ramcache entries.

     

     

    As the documentation (outside the limited 'b profile http help' info) is fairly lacking for pre-9.4.x ramcache commands, you could open a case with F5 and ask them to publish a solution with example commands.

     

     

    Aaron
  • When our apps people make a change we do this:

     

     

     

    b profile http PROFILE_NAME ramcache delete

     

     

    What is the difference between reset and delete?
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    I think reset and delete are used for the same functionality in different versions. If 'delete' deletes the cache entries for your version, then it's fine to use.

     

     

    Aaron
  • giltjr's avatar
    giltjr
    Icon for Nimbostratus rankNimbostratus
    hoolio is correct, reset and delete are the same function for different versions of LTM.

     

     

    If you use the same http profile for more than one host you can specify a host name:

     

     

    bp profile http ramcache entry uri / host delete

     

     

    This way you only get rid of the cached entries for a specific host name instead of every host that uses that profile. Of course you can also specify as much or as little of a uri as you want. Say the majority of java script file were updates that reside in a specific directory you could:

     

     

    bp profile http ramcache entry uri /app1/*.js host delete