SharePoint iCall deployment

Hello Gurdip, I have been working on an unofficially supported iAPP that would solve this specific problem. Basically it packages up the SharePoint iCall script into an iAPP and makes all the variables editable through the iAPP question and answer format. There is still internal discussions about how to publish this and to ensure the iAPP goes through an internal peer review for major bugs and such. How soon are you looking to implement this?

 

Another note: You can also add icalls via tmsh directly. It tends to get a little complicated the longer the icall script is, however I can assist with tmsh syntax for the manual process if you need to test this iCall immediately. On other question for you...Are you deploying this against a pool managed by the Sharepoint(or HTTP) iApp with strict updates turned on?

 

Basic tmsh syntax inside the shell: "create /sys icall script icall_script_name" (When the next screen comes up input the sharepoint icall script in between the definition brackets. Couple things to note here is to make sure in your terminal window you are using to connect to big ip to make sure auto wrap is not on and scrollback is set to like 10000 lines to make sure characters don't get missed. Also if you still have issues then copy the icall script into a notepad and tab everything to the left.)

 

Let me know if you still run into issues!

 

I cannot seem to edit my existing answer... below is the information on how to create the handler.

 

Once you get the icall script into the system you then manage it via a handler to determine when and how it runs. The following tmsh command will create a periodic handler that runs at an interval of 15 seconds. "create /sys icall handler periodic icall_handler_name interval 15 script icall_script_name"

 

Output of icall scripts are sent to /var/tmp/scriptd.out (You can see errors as well as anything sent to stdout such as puts, etc...)

 

Hi James,

 

That sounds really good. I was looking to deploy this like last year but could not work out the steps lol.

 

I raised a case with F5 and they've given me this link:

 

https://devcentral.f5.com/articles/third-times-the-charm-big-ip-backups-simplified-with-icall

 

The .tcl file in the icall zip seems to be ready so I would need to upload it to the F5. Do I need to follow all the steps above? Also, are there are any relevant steps on how to upload? IE where to upload to, etc.

 

I am using the SharePoint iApp with strict updates disabled.

 

I'd be interested in testing the iApp in my F5 LTM Lab, you can email me - gurdipsira_1@yahoo.co.uk

 

Regards

 

The short answer is......yes, you need to run both of those commands. Basically it boils down to two things. 1) Run the command to create the icall "script" which contains the TCL code that will be executed. 2) Create the icall "handler" that will determine when to execute that script. Those two things are pretty straightforward. The problem tends to come when you are trying to import a icall that is very long and can be hard to actually get into the definition of the icall script easily. That is why I suggested a couple things to check before performing the copy and paste.

 

One final note: Depending on when you downloaded the icall script I would suggest downloading it again from the codeshare to ensure you have the latest version. https://devcentral.f5.com/codeshare/prioritize-sharepoint-nodes-on-reported-health