Forum Discussion

Peter_Baumann_5's avatar
Peter_Baumann_5
Icon for Nimbostratus rankNimbostratus
Dec 22, 2016

iRules LX config sync in cluster with workspaces, how?

Hi all, A customer of us is using with success the iRules LX and he likes it very much to do some REST-API security. Now he has a iRules LX workspace which is located in the path /var/ilx/workspaces. He is using a Big-IP cluster and is doing a config sync to the standby node. Unfortunately the iRules LX workspaces are not synced to the other machine... BigIP Version is v12.1.1.

 

Since I couldn't find any information about iRules LX and clustering I ask it here: How should we proceed when the active cluster member is down and the created iRules LX?

 

Many thanks for an answer.

 

Peter

 

application delivery
BIG-IP
cluster
iRulesLX

6 Replies

Sort By
  • Patrik_Jonsson's avatar
    Patrik_Jonsson
    Icon for MVP rankMVP
    Dec 23, 2016

    Interesting! I will follow this one. Please add which version you're running? Could be important.

     

    /Patrik

     

  • Peter_Baumann_5's avatar
    Peter_Baumann_5
    Icon for Nimbostratus rankNimbostratus
    Dec 23, 2016

    Hi Patrik, I updated the question with the version. It is v12.1.1. In my lab I have v12.1.2, same problem.

     

  • Daniel_W_'s avatar
    Daniel_W_
    Icon for Cirrus rankCirrus
    Dec 29, 2016

    I have the same issue, just tested with 12.1.2. Are there any news on that or do we need to open a support case?

     

  • Eric_Flores_131's avatar
    Eric_Flores_131
    Icon for Cirrostratus rankCirrostratus
    Jan 27, 2017

    Hi Peter, This is intended behavior of iRules LX. Only the active plugins are sync'ed across clusters. The workspaces are not.

     

    iRules LX was designed with DevOps teams in mind and the workspace was intended for active code development that would not be done on a production device.

     

  • Peter_Baumann's avatar
    Peter_Baumann
    Icon for Cirrostratus rankCirrostratus
    May 14, 2018

    Answering my own question:

     

    The same behavior is still in v13.1.x. But it is no problem to export and import the workspace to the other cluster member.

     

    It seems that it is not supported as @Eric Flores has explained above.