Forum Discussion

JoergK's avatar
JoergK
Icon for Nimbostratus rankNimbostratus
Aug 22, 2019
Solved

tmsh or bash command to kill all access policy sessions in apm module

Hi,

we are running two Big IP 5250 with APM module. Sometimes we need to kill all APM sessions. Today we do that by going to Access Policy -> Manage Sessions, select the existing sessions and kill them by pushing the button 'Kill Selected Sessions'.

 

Is there a way to kill all sessions via tmsh or bash command? Could someone provide an example on how to do that?

 

Best regards,

Joerg

  • Yes, like this:

    [root@big-ip:Active:Standalone] config # /usr/bin/sessiondump --delete all
    Succesfully deleted 2 sessions
    [root@bigip:Active:Standalone] config #

5 Replies

  • Yes, like this:

    [root@big-ip:Active:Standalone] config # /usr/bin/sessiondump --delete all
    Succesfully deleted 2 sessions
    [root@bigip:Active:Standalone] config #
  • JoergK's avatar
    JoergK
    Icon for Nimbostratus rankNimbostratus

    Hi,

    Thanks for your quick answer. Looks promising.

     

    I have some trouble finding a manpage or some documentation other than the short help output of the command. Are there any additional resources on this command?

  • JoergK's avatar
    JoergK
    Icon for Nimbostratus rankNimbostratus

    Hi,

    At first I would like to thank you Dave for sharing the manual page. It is not much but better than nothing.

    I have used the following command in version 12.1.3.7 some times and it worked as expected. All sessions were killed.

    /usr/bin/sessiondump --delete all

    Yesterday I used it the first time in version 14.1.0.6 and got to following output:

    user@bi5050:Active:In Sync] ~ # /usr/bin/sessiondump --delete all 
    Couldn't delete session master key
    Succesfully deleted 4803 sessions
    Failures on 1 sessions
    user@bi5050:Active:In Sync] ~ #

    What is the session master key? Could anybody explain it, please?

    • Dave_W's avatar
      Dave_W
      Icon for Employee rankEmployee

      Hello JoergK, I believe that sometimes sessions can get in a "stuck" state and this might explain the error. Also this could perhaps be related to HA sync timing. Of course I am speculating here.