Hi! Thank you for your answer. For the moment, we need a simplified solution and we don't need to link the exported info from F5 into the cmdb. We would just need to export the data either in a csv or in an html file (or in another way) in order to have the global info visible. Then when we would have visibility of the necessary info, that would be sufficient and we can inport data in the cmdb manually then.
The best example I can think is that, if a server has a problem, we need now to do the whole troubleshooting on F5 manually to find in which pool it belongs, then where is this pool used, in which VIP, if there is an irule impacting applications etc etc. On the other hand, if we could generate quickly a report, it would be much faster to track the impacted resources and see this info, even for people who are not familia with the F5.
So a file export with custom fileds could do the job (in this case we would need to corralate info inside iRules with info from LTM VIP, pools etc).
Thank you again for your help
Kind regards,
Yiannis