Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

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

0
Rate this Question
Comments on this Question
Comment made 22-Dec-2016 by Patrik Jonsson 3488

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

/Patrik

0
Comment made 23-Dec-2016 by Peter Baumann 411

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

0
Comment made 29-Dec-2016 by Daniel W. 277

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?

0
Comment made 27-Jan-2017 by Eric Flores

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.

1

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I just opened Case C2316361, let's see if we find a solution...

0
Comments on this Answer
Comment made 18-Jan-2017 by Egor 0

Hi, I have also the same issue with 12.1.1HF2. Is there any process on case C2316361 or update for us please?

0
Comment made 18-Jan-2017 by Niels van Sluis 2573

Here same issue. I'm using BIG-IP 12.1.1 HF1.

0